Closed zxzxwu closed 4 months ago
Great plan. I'm all for splitting the effort into incremental (and/or parallel) steps. As long as we make it clear that the entire LE audio support will be in flux for a while, and highly experimental (the APIs defined along the way are likely to change as we build this up).
It seems like CSIP/CAP might not be necessary when only single device is present?
As https://github.com/google/bumble/pull/308 has been a little bit big, so I am going to list some roadmap here.
Scope
The initial implementation will focus on the Unicast Server role defined in Basic Audio Profile 2.1.1 due to its relative ease of implementation and critical role in testing. This initial phase will be limited to single-device (BR/EDR TWS-like) use cases. Following the successful completion of the single-instance implementation, we may expand the scope to include multi-instance support.
Unicast Client and Broadcast roles are not in the scope.
Roadmap
There might be some PRs:
By the end of 2023, I think at least General, CAP and CSIP are not too difficult to complete.
BAP might have some progress in the December, but CIS integration will take a longer time. If there cannot be an overall solution, at least we can provide an example Unicast server built on a naive structure.