Datasets:
kkboy1
/
LeAudio

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
112
tmas telephony and media audio service tee mas
vocs volume offset control service vocks
table pronunciation guide for bluetooth le audio acronyms
initialisms
the rest are simply pronounced as the individual letters that make up the abbreviation eg
ccp is pronounced see see pee and lc is el see three
the most common initialis ms in bluetooth le audio are acl ad ascs bmr bms
bredr ccid ccp cg css ct ctkd ea ft gmcs gss gtbs ha hci ia
iac ias ina p irc irk lc mcp mcs mtu nse pa pba pbk pbp pbs pdu
pto rfu rtn sdp sdu tbs ui umr ums uuid vcp and vcs these are all
explained in the glossary
irregul ar pronunciations
oob is an oddity as it is always spoken in full ie out of band although the abbreviation is
generally used in text
section talking about bluetooth le audio
ooo
that was a whistle stop tour through the main parts of the generic audio framework we
will see even more specifications appear in gaf in the future but for now the ones described
above emulate and expand on the audio functionality that bluetooth has today with the classic
audio profiles
in the remainder of the book well see how baps bap bass as cs and pacs form the
core of everything that you do with bluetooth le audio the other specifications add
usability and functionality while cap glues it all together as a first step well look at some
of the new concepts which have been necessary to address the bluetooth le audio
requirements
chapter new concepts in bluetooth le audio
chapter new concepts in bluetooth le audio
to provide designers with the flexibility they need the new bluetooth le audio specifications
have introduced some important new concepts in this chapter well look at wh at they do
and why they are needed because these features are closely integrated into the specifications
some of the descriptions below will become clearer as we dive down into the detail of the
core and the gaf however its useful to introduce them at this stage as they pervade much
of what follows
multi profile by design
as weve seen one of the challenges faced by bluetooth classic audio has been the multi
profile issue where users change between streaming music making phone calls and using
voice recognition as the complexity of audio use cases continues to increase th at problem
wont improve the two successful classic bluetooth audio profiles hands free profile
hfp and music streaming adp were designed at a time where users were assumed to use
one or the other starting new independent sessions as they moved from phone calls to music
it soon became apparent that these wer e not independent functions but that phone users
would expect one use case to interrupt the other over the years the industry has developed
rules and methods to address this problem culminating in the publication of the multi profile
specification mp s in which essentially collects sets of rules for common transitions
between these profiles
the multi profile specification is not particularly flexible and didnt foresee the emergence of
new use cases such as voice recognition voice assistants and interruptions from gps satnavs
nor are the underlying specifications particularly versatile although hfp has gone through
multiple versions and spawned around twenty complementary specifications addressing
specific aspects of car to phone interacti on it still struggles to keep up with non cellular voip
telephony applications neither it nor adp have sufficiently addressed the changing nature
of audio where users connect to multiple different audio sources during the course of a day
and might also own multiple different headsets and earbuds
from the start bluetooth le audio was developed with the philosophy that it would support
multi profile by design it recognised that users might have multiple headsets and audio
sources constantly cha nging connections in an ad hoc manner the addition of broadcast
audio makes this even more important as the projected uptake of broadcast in venues shops
leisure facilities and travel would extend the number of different connections a user is likely
to make each day it was obviously going to be important to provide tools to make the user
experience seamless
the audio sink led journey
alongside these demands came a realization that the phone would not necessarily remain the
centre of the audio universe which had been a tacit assumption throughout the evolution of
section terminology
the bluetooth classic audio specif ications as an increasing number of different audio
sources became available it was important to consider how a user would conne ct their earbuds
or hearing aids through the course of the day this turned the perceived view of a phone
centric audio world on its head replacing it with the concept of an audio sink led journey
its an approach where the phone is no longer the arbiter of what you listen to instead it
assumes that users are increasingly likely to wear a pair of hearing aids or earbuds throughout
the day constantly changing their audio source it may start wit h an alarm clock followed by
asking your voice assistant to turn your radio on information from a bus stop voice control
for your computer receiving phone calls interruptions from the doorbell and relaxing in front
of the tv when you get home until t he microwave tells you that your dinner is ready this
conceptual turnaround regarding who is in control takes a lot from the experience of hearing
aid wearers who typically wear their hearing aids for most of the day for a large part of that
time th e hearing aid works without any bluetooth link just listening to and reinforcing the
sound around the wearer but the wearer can connect it to a wide number of infrastructure
audio sources supermarket checkout machines public transport information th eatres and
auditoria and tvs as well as phones and music players if they support bluetooth classic
audio its functionality that many more consumers are likely to use once it becomes widely
available
phones will of course remain a major source of au dio but increasingly so are pcs laptops
tvs tablets hi fi and voice assistants theyre also being joined by a range of smart home
devices from doorbells to ovens at the same time consumers are buying more headsets its
not uncommon for someone to own a pair of sleep buds a set of earbuds a pair of stereo
headphones and a soundbar or bluetooth speakers as the potential combinations multiply
its vital that the user interfaces can accommodate this range of different connections and the
trans itions between them
terminology
different parts of the bluetooth le audio specifications use different names for the
transmitting and receiving devices and what they do each specification refers to these as
roles so by the time weve gone from the core to a top level profile we will have accumulated
at least four different roles for each device there is a very good reason for this as each step
up the stack results in more specificity within those roles with the result that devices can
implement spec ific combinations to fulfil a targeted function but they can get confusing