Datasets:
kkboy1
/
LeAudio

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
112
operation which informs a commander that any preset command sent t o one hearing aid can
be locally relayed to the other member of the set which is described in sections
of has
the other enhancement in hap is the option to include the immediate alert service hap
this allows a device which doe s not support an audio stream to provide an alert to
the hearing aid which it can render as an alert to the user no specific use cases are defined
but it is suggested that manufacturers might want to include this capability in products such
as doorbell s or microwave ovens to help inform hearing aid wearers of something they need
to respond to
the aim of the hap requirements is to support all of the use cases envisaged for hearing aids
which are illustrated in figure
figure the four main use cases for hap showing the roles used in each
as many of the hearing aid use cases will involve the user hearing the ambient sound as well
as the received bluetooth le a udio stream it is expected that devices will favour the use of
low latency qos modes to help ensure low latency there is a requirement that all devices
chapter top level bluetooth le audio profiles
in the ha role shall support a presentation delay value of ms for receive and transmit for
low latency qos modes
a final nuance in the hea ring access profile is a set of requirements in section which
dictate link layer setting when the hauc is using a ms isochronous interval and the
hearing aid does not support the reception of ms lc codec frames it is expected that
this will b e an edge case in situations where a hearing aid has a minimal lc implementation
as support for ms codec frames is not mandated and where an initiator is forced to use a
ms interval because of timing limitations of its other peripheral devices wh ich cannot
accommodate the preferred ms interval in this case the scheduler should ensure the
selection of the specified parameters for isoal to avoid segmentation of sdus and a
potential increase in the frame loss rate it is anticipated that initia tors will move to the
optimum ms transport interval as bluetooth le audio becomes common hence this is a
short term fix
all haucs has and habs must support the m phy although its use is not mandated
it is highly recommended to conserve airtime an d hence battery life
tmap the telephony and media audio profile
like hap the tmap profile is predominantly a list of additional requirements beyond those
mandated in bap and cap to emulate the use cases of the hfp and adp profile s tmap
does not introduce any new behaviour or characteristics so incorporates a minimal tmas
section within tmap
because it is bundling both telephony and media applications into one document tmap feels
like a por tmanteau profile where implementers have a wide ranging ability to pick and choose
what they support this can lead to some oddities as many of its features are optional in
theory depending on what you pick it is possible to make a tmap compliant de vice which
supports telephone calls but does no t support music and vice versa thats a logical
consequence of bundling so many different use cases together it makes sense that a soundbar
or speaker doesnt support telephony but that means that headph ones dont need to support
telephony either instead it is up to the implementer to choose the features and roles which
are appropriate and let market darwinism take care of any inauspicious choices
to try and prevent any surprises the tmas element of tmap includes a tmap role
characteristic tmap which exposes the specific roles which a device supports this
allows acceptors to determine the roles that an initiator supports which is required for some
use cases which brings us to the roles tma p does not define any new roles for a
commander but defines three pairs of roles for an initiator and an acceptor
section tmap the telephony and media audio profile
telephony roles call gateway and call terminal
for telephony tmap defines a call gateway cg and call terminal ct role the call
gateway is the device which connects to the telephony network such as a phone tablet or
pc and is an initiator a call terminal is typically a headset but can also be an extension
speaker or a microphone for a conference phone some common configurations are shown
in figure
figure typical configurations for the cg and ct roles
devices supporting the cg and ct roles must support the higher codec settings of khz
sampling at both ms and ms frame rates and from bap with the low
latency settings these correspond to the same audio quality as the superwideband evs
speech codec that the gpp speci fies for g phones ensuring no loss of quality from local
microphone to remote headset and vice versa
a cg must support the ccp server role but does not mandate any further features above
those mandated in ccp
media player roles unicast media sender and unicast media
receiver
media player use cases employ the unicast media sender ums and unicast media receiver
umr roles the unicast media sender is the initiator which is the audi o source and the
unicast media receiver an acceptor typical configurations are shown in figure
figure typical tmap unicast media applications
chap ter top level bluetooth le audio profiles
for unicast media tmap pushes up the audio quality requiring a unicast media receiver to
support all six of the khz sampling codec configurations form to unicast media
sources must support the co dec setting and at least one of the or settings all
tmap roles must support the m phy which will almost certainly be necessary to find
enough airtime for these configurations although support for these qos configurations is
required it is up to the application to decide how it configures the ases it can decide to use
lower values for ums the khz sampling rates remain optional although it is unlikely that
an acceptor would not support them a user is unlikely to hear the difference between
and khz so the choice of setting is largely a marketing decision
tmap does not mandate the support of any context type other than unspecified if a
unicast media receiver wants to reject an y attempt to establish a stream from a call gate way
it should support ringtone but set it to not available
tmap increases the requirement for media control by mandating support for play and pause
opcodes a ums must also support the media control point characteristic
broadcast media roles broadcast media sender and broadcast
media receiver
the final two set s of roles in tmap are the broadcast media sender and broadcast media
receiver roles unsurprisingly t hese are designed for broadcast applications within tmap
they are generally envisaged to be personal applications where higher audio quality is requi red
but may also be used in public broadcast applications such as cinemas typical use cases are
shown in figure
figure typical use cases for the broadcast media sender and receiver roles
tmap adds very few requirements on top of bap and cap for the broadcast roles it