Datasets:
kkboy1
/
LeAudio

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
112
sduinterval
framing
phy
maxsdu
retransmissionnumber
maxtransportlatency
presentationdelay value which the acceptor will use for rendering or capture
table parameters returned by an acceptor after receiving a config qos opcode x
repeating the obvious once again t he initiator should step through each state for all of the
ases it intends to use on all of the acceptors before proceeding to the next state ie it takes
them all to the codec configured state then all to the qos configured state etc thats purely
common sense because the initiator needs to obtain information from all of them to ensure
that it sets configuration parameters for the ases that work across all of the acceptors
however just to be sure cap mandates it
if multiple acceptors or ases dont provide a consistent set of parameters the initiator can
repeat each step of the config and qos configuration process for one or more o f them
including going back from the qos configured state to the codec configured state however
the expectation is that this procedure would normally be a single step process which is
performed once only for each set of ases as its more efficient if it keeps all of the state
changes in sync so the process steps are
the initiator sends a command with target values and explicit values for multiple
ases
the acceptor confirms the new state for all of those ases which may include a
failure code by notifying its ase control point characteristic
the acceptor separately notifies its preferred values for each ase using ase
characteristics this is the point where it state s what has been configured and its
preferences for the next configuratio n step
at any point the initiator can check an individual ase characteristic the parameters will
indicate the state of the ase along with values that are relevant to that state if an initiator
reads an aseid in the idle state the only informati on it will receive is the aseid and an
asestate value of indicating the idle state the most common reason for reading an ase
characteristic is to confirm a previous ase control point operation when an expected
notification has not been received
section configuring an ase and a cig
when the initiators host sent the hci le set cig parameters command to its controller
it moved the cig to its configured state the initiators host can still modify the properties
of a cis or add further cises to the cig at this point by resending an h ci le set cig
parameters command for specific cises using its array structure if it does it will need to
update the relevant ases using the config qos command by writing to the ase using the
array capability of the ase control point characteristic
once all of the ases are in the qos configured state and the cig is configured we can start
to enable the audio streams
enabling an ase and a cig
having configured all of the ases the initiator will have all of the information it needs to
instruct its cont roller to enable the cig and constituent cises the acceptors host knows
the main parameters of the isochronous channels although some values are still provisional
as the actual rtn value will depend on the scheduling if the controller is also having to
support other wireless connections it may decide to compromise to allocate airtime between
the different and set a lower value than its host requested at the point that each cis is
established the settings will be configured at the link layer level and notified to the respective
hosts of the initiator and each acceptor
the initiator can now invoke the enabling an ase procedure defined in bap by writing
to each accepto rs ase control point characteristic with the opcode set to x enable
using the parameters shown in table from this point the initiator cannot change the
cig cis or ase configurations with the exception of the audio stream metadata
parameter description
number of ases total number of ases to be enabled i
aseid i the specific ases which are being enabled
metadata length i length of metadata for ase i
metadata i ltv formatted metadata this is most commonly the
streamingaudiocontexts and ccidlist ltv
structures but can include other ltv structures
table state specific parameters for the enabling operation opcode x table of ascs
cap mandates that the metadata in the enabling operation includes the
streamingaudiocontexts with the correct values set for each unicast audio stream if
there is a content control procedure associated with the audio stream then the metadata in
the enabling command must also include the ccidlist ltv structure cap
each acceptor will notify its ase control point characteristic move its ases to the enabling
state then in turn notify the ase characteristic for each of the ases specified in the ase
control point command returning their cig and cis ids along with any metadata written
chapter setting up unicast a udio streams
by the initiator as shown in table
parameter value
cigid values set by the initiator in its previous config qos
operation
cisid
metadata length if there is no metadata for this ase
metadata ltv structures for the sink or source ase
table additional parameters for the ase characteristic when in the enabling streaming and disabling states
the metadata values for an ase can only be set or updated by the initiator an acceptor
cannot make changes to these even if it is acting as the audio source an acceptor can
update its availableaudiocontexts value at any point but these do not appear in the ase
metadata nor do they result in the termination of a current stream any change i n the
availableaudiocontexts is only used for subseque nt connection attempts
now that the ases are in their enabling state it is time to enable the required cises and
couple them to the ases remember from chapter that not every configured cis included
in the cig needs to be established as an initiato r can configure cises which it can swap in
and out as its demands change the initiator enables the cises it requires by invoking the
connected isochronous stream central establishment procedure from the core vol part
c section the link laye r will generate a cisrequest to the acceptor which
establish es the cis using the isochronous stream peripheral establishment procedure from
the core vol part c section at this point the initiator will start transmitting
packets with zero length pdus if it is a bidirectional cis both sink and source ases need
to be established
there is a condition on the behaviour of the ase at this point which implementors need to
be aware of if the cis existed before the enabling operation the tran sition from the enabling
state to the streaming state is not notified instead the acceptor autonomously transitions
the ase to its streaming state without the need for the initiator to write the streaming
command this is most likely to occur if the a cceptor is reusing an existing configuration and