text stringlengths 1 112 |
|---|
the lock as it can prevent other commanders or initiators accessing the acceptors when a |
a firmware update is considered to be the start of a new life |
section cap the common audio profile |
client no longer needs exclusive access it should release the lock |
the rank is a value that is normally assigned at manufacture to provide a unique number to |
each m ember of the coordinated set it doesnt imply any priority but is a unique positive |
integer within the coordinated set which is used to ensure that all client s apply their |
operations to the members of the set in the same order rank is used in the ord ered access |
procedure in csip this states that when applying a lock for any reason clients should start |
with the set member that it knows to have the lowest rank and then work up through the other |
members of the coordinated set in ascending numeric orde r of rank that prevents a race |
condition where two different client s apply a lock to different set members at the same time |
the rank values are normally set during manufacture |
the ordered access procedure is also used by cap as a precursor to runnin g any cap |
procedure it checks whether any acceptor is locked and only continues with the cap |
procedure once it has determined that none of the set members have a lock set it then |
applies the cap procedure to each acceptor in order of increasing rank |
cap the common audio profile |
as i said above cap can be considered as the recipe book for all of bluetooth le audio |
bringing together all of the other specifications into five main sets of procedures which defin e |
the way that everything works top level profiles like hap tmap and pbp then refer to |
these cap procedures adding additional requirements for their specific use cases |
cap is where the initiator acceptor and comman der roles that im using throughout this |
book are defined whilst only the initiator and acceptor can be involved in audio streams |
cap describes how all three of these roles can include a range of components from the other |
generic audio framework specifications these are listed in the matrix of table which |
shows mandatory optional conditional and excluded requirements conditional features |
are normally mandated for specific combinations of other features and require that a role |
supports at least one of a number of optional components excluded combinations are not |
allowed the full details of all of the se combinations can be found in table of cap |
boxes with a dash are features which could be implemented in a device but are outside the |
scope of the cap procedures |
role |
component acceptor initiator commander |
bap broadcast assistant x o c |
bap scan delegator c x c |
vcp volume controller x c |
vcp volume renderer o x x |
chapter cap and csips |
role |
component acceptor initiator commander |
micp microphone controller x c |
micp microphone device o x x |
ccp call control server x o x |
ccp call control client o x |
mcp media control server x o x |
csip set coordinator x c m |
csip set member c x x |
m mandatory o optional c conditional x excluded not |
relevant to this profile |
table component support requirements for cap roles see table of cap for individual conditions |
cap procedures for unicast stream management |
the cap procedures for managing streams can be grouped into three categories the first is |
a set of three procedures for unicast streams which are largely self explanatory |
unicast audio start procedure |
unicast audio update procedure |
unicast a udio stop procedure |
these procedures involve both the initiator and the acceptor as setting up each unicast |
stream uses command and response sequences |
cap procedures for broadcast stream transmission |
the second set o f three procedures is for broadcast streams |
broadcast audio start procedure |
broadcast audio update procedure |
broadcast audio stop procedure |
the broadcast audio start stop and update procedures are only used by the initiator as that |
is set up unilaterally with no knowledge of whether any acceptors are present |
section cap the common audio pro file |
cap procedures for broadcast stream reception |
to complement the broadcast procedures for the initiator the third set of stream management |
procedures is for acceptors that want to acquire the broadcast audio streams giving us two |
procedures |
broadcast audio reception start procedure |
broadcast audio reception ending procedure |
there is no broadcast audio update procedure for the acceptor as an acceptor is a passive |
entity in broadcast which only consumes the audio stream it cannot do anything to update |
the content of the broadcast streams hence there is no update procedure for broadcast audio |
reception |
cap procedures for stream handover |
cap includes two procedures specifically for a stream handover where an initiator wants to |
transition between transmitting unicast and broadcast audio streams and vice versa these |
are the |
unicast to broadcast audio handover procedure and the |
broadcast to unicast audio handover procedure |
these are very important as they describe the audio sharing use case where a user can |
transition from liste ning to a private stream from their phone or music source to sharing it |
with friends by converting it to broadcast although the transmission topology changes |
between cig to big the original initiator retains control of the audio s tream and the user s |
acceptors |
the reason for the importance of the handover procedures is that most initiators and |
acceptors do not have the resources to handle concurrent unicast and broadcast streams for |
the h igh reliability qos settings there simply isnt enough airtime to do both that means |
that an initiator usually needs to stop its unicast stream before staring the broadcast stream |
even for a khz sampling rate to ensure continuity for the primary user ie the one who |
is sharing their audio with their friends the initiator has to apply the same context type s to |
the new stream in most cases the primary user with the audio source will want to continue |
to control the stream so although the audio stream is now broadcast they will keep their |
acl link up and a ssociate the new broadcast audio stream with the same content control |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.