throbber
BLUETOOTH DOC
`Prepared
`Car Working Group
`
`
`
`Approved
`Date / Year-Month-Day
`Adopted
`2005-11-25
`e-mail address
`car-feedback@bluetooth.org
`
`Revision
`V10r00
`
`Document No
`HFP1.5_SPEC
`N.B.
`
`
`HANDS-FREE PROFILE 1.5
`
`Abstract
`
`The Hands-Free Profile (HFP) 1.5 specification defines the minimum
`set of functions such that a Mobile Phone can be used in conjunction
`with a Hands-Free device (e.g. installed in the car or represented by
`a wearable device such as a headset), with a Bluetooth® Link
`providing a wireless means for both remote control of the Mobile
`Phone by the Hands-Free device and voice connections between the
`Mobile Phone and the Hands-Free device.
`
`Compliance with this specification assures interoperability between a
`Bluetooth enabled Hands-Free device and any Bluetooth equipped
`Mobile Phone supporting this profile.
`
`
`
`
`
`Ex. 1028
`Page 01 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 2 of 93
`
`Revision History
`Comments
`Revision Number Date
`01-01-2912-11-2003 Hands-Free Profile 0.50 published1st draft for SubWG12
`RC10.50
`Review
`22-11-200403-14-03 CR document derived from FIPD07r04Additional
`comments from BTI/BQRB reviews
`Editing for Prototyping Specification standards
`Incorporated Prototyping Specifications
`Errata and corrections from IOP.
`
`16-02-2005
`19-03-2005
`22-04-2005
`
`RC21.00m VD
`
`D10r08
`D12r00
`D12r01
`
`D12r02
`
`D15r03
`
`D15r04
`D15r05
`D15r06
`
`D15r07
`
`D15r08
`D15r09
`D15r09
`
`D15r10-11
`
`D15r12
`D15r13
`V10r00
`
`28-04-2005
`
`13-05-2005
`
`27-05-2005
`07-06-2005
`07-18-2005
`
`08-01-2005
`
`09/02/2005
`09/22/2005
`09/26/2005
`
`10/04/2005
`
`10/05/2005
`10/07/2005
`11/25/2005
`
`HFP 1.0 Errata- 13, 261, 317, 549, 550, 575, 586, 635,
`706, 731, 746
`Correct formatting problems and comments from review.
`
`Errata 819, 820, 821, 822
`Edits from BARB Review. Errata 823.
`
`Changes from BARB review. Editorial changes for
`language and readability.
`Comments from BTI/BARB review.
`
`Comments from BTI review.
`Comments from BTI review
`
`Add 3GPP 27.07 version and remove reference to Call
`Waiting for AT+CHUP
`BTI Comments
`
`Editorial changes
`Prepare for publication
`Adopted by the Bluetooth Board of Directors
`
`25 November 2005
`
`Ex. 1028
`Page 02 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 3 of 93
`
`Contributors
`Name
`Aaron WEINFIELD
`Basam MASRI
`Don LIECHTY
`
`Stephen RAXTER
`Vartika AGARWAL
`Leonard HINDS
`
`Burch SEYMOUR
`Stephane BOUET
`Jamie MCHARDY
`Jurgen SCHNITZLER
`
`Guillaume POUJADE
`Dmitri TOROPOV
`Erwin WEINANS
`
`Tim REILLY
`Akira MIYAJIMA
`Ryan BRUNER
`
`Scott WALSH
`Patrick CLAUBERG
`Neil MACMULLEN
`
`Michael BUNTSCHECK
`Florencio CEBALLOS
`Bill BERNARD
`
`
`
`Company
`Denso
`Denso
`Extended Systems
`
`Johnson Controls
`Motorola
`Motorola
`
`Motorola
`Nissan
`Nokia
`Nokia
`
`Parrot
`Siemens
`Sony Ericsson
`
`Stonestreet One
`Toyota
`Visteon
`
`Plantronics
`Nokia
`CSR
`
`BMS
`Visteon
`Visteon
`
`25 November 2005
`
`Ex. 1028
`Page 03 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 4 of 93
`
`Disclaimer and Copyright Notice
`The copyright in this specification is owned by the Promoter Members of Bluetooth® Special Interest
`Group (SIG), Inc. (“Bluetooth SIG”). Use of these specifications and any related intellectual property
`(collectively, the “Specification”), is governed by the Promoters Membership Agreement among the
`Promoter Members and Bluetooth SIG (the “Promoters Agreement”), certain membership agreements
`between Bluetooth SIG and its Adopter and Associate Members (the “Membership Agreements”) and the
`Bluetooth Specification Early Adopters Agreements (1.2 Early Adopters Agreements) among Early
`Adopter members of the unincorporated Bluetooth SIG and the Promoter Members (the “Early Adopters
`Agreement”). Certain rights and obligations of the Promoter Members under the Early Adopters
`Agreements have been assigned to Bluetooth SIG by the Promoter Members.
`
`Use of the Specification by anyone who is not a member of Bluetooth SIG or a party to an Early Adopters
`Agreement (each such person or party, a “Member”), is prohibited. The legal rights and obligations of
`each Member are governed by their applicable Membership Agreement, Early Adopters Agreement or
`Promoters Agreement. No license, express or implied, by estoppel or otherwise, to any intellectual
`property rights are granted herein.
`
`Any use of the Specification not in compliance with the terms of the applicable Membership Agreement,
`Early Adopters Agreement or Promoters Agreement is prohibited and any such prohibited use may result
`in termination of the applicable Membership Agreement or Early Adopters Agreement and other liability
`permitted by the applicable agreement or by applicable law to Bluetooth SIG or any of its members for
`patent, copyright and/or trademark infringement.
`
`THE SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING
`ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR
`PURPOSE, SATISFACTORY QUALITY, OR REASONABLE SKILL OR CARE, OR ANY WARRANTY
`ARISING OUT OF ANY COURSE OF DEALING, USAGE, TRADE PRACTICE, PROPOSAL,
`SPECIFICATION OR SAMPLE.
`
`Each Member hereby acknowledges that products equipped with the Bluetooth technology ("Bluetooth
`products") may be subject to various regulatory controls under the laws and regulations of various
`governments worldwide. Such laws and regulatory controls may govern, among other things, the
`combination, operation, use, implementation and distribution of Bluetooth products. Examples of such
`laws and regulatory controls include, but are not limited to, airline regulatory controls, telecommunications
`regulations, technology transfer controls and health and safety regulations. Each Member is solely
`responsible for the compliance by their Bluetooth Products with any such laws and regulations and for
`obtaining any and all required authorizations, permits, or licenses for their Bluetooth products related to
`such regulations within the applicable jurisdictions. Each Member acknowledges that nothing in the
`Specification provides any information or assistance in connection with securing such compliance,
`authorizations or licenses. NOTHING IN THE SPECIFICATION CREATES ANY WARRANTIES,
`EITHER EXPRESS OR IMPLIED, REGARDING SUCH LAWS OR REGULATIONS.
`
`ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHTS OR FOR
`NONCOMPLIANCE WITH LAWS, RELATING TO USE OF THE SPECIFICATION IS EXPRESSLY DISCLAIMED. BY USE OF
`THE SPECIFICATION, EACH MEMBER EXPRESSLY WAIVES ANY CLAIM AGAINST BLUETOOTH SIG AND ITS PROMOTER
`MEMBERS RELATED TO USE OF THE SPECIFICATION.
`
`Bluetooth SIG reserve the right to adopt any changes or alterations to the Specification as it deems
`necessary or appropriate.
`
`Copyright © 2001, 2002, 2003, 2004, 2005. Bluetooth SIG Inc. All copyrights in the Bluetooth
`Specifications themselves are owned by Agere Systems Inc., Ericsson Technology Licensing AB, IBM
`Corporation, Intel Corporation, Microsoft Corporation, Motorola, Inc., Nokia Mobile Phones and Toshiba
`Corporation. *Other third-party brands and names are the property of their respective owners.
`
`25 November 2005
`
`Ex. 1028
`Page 04 of 93
`
`

`

`2
`
`3
`4
`
`4.1
`4.2
`
`Page 5 of 93
`
`1.1
`1.2
`1.3
`
`2.1
`2.2
`2.3
`2.4
`2.5
`
`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`Contents
`1
`Introduction ...................................................................................................................................... 7
`Scope......................................................................................................................................... 7
`Profile Dependencies ................................................................................................................ 8
`Symbols and Conventions......................................................................................................... 8
`1.3.1 Requirement Status Symbols ............................................................................................. 8
`1.3.2 Naming Conventions........................................................................................................... 9
`1.3.3 Signaling Diagram Conventions........................................................................................ 10
`Profile Overview ............................................................................................................................. 11
`Protocol Stack.......................................................................................................................... 11
`Configuration and Roles .......................................................................................................... 11
`User Requirements and Scenarios ......................................................................................... 12
`Profile Fundamentals............................................................................................................... 12
`Conformance ........................................................................................................................... 13
`Application layer............................................................................................................................. 14
`Hands-Free Control Interoperability Requirements ....................................................................... 17
`Introduction.............................................................................................................................. 17
`Service Level Connection Establishment ................................................................................ 17
`4.2.1 Service Level Connection Initialization ............................................................................. 17
`4.2.2 Link Loss Recovery........................................................................................................... 20
`Service Level Connection Release ......................................................................................... 20
`4.3
`Transfer of Registration Status................................................................................................ 21
`4.4
`Transfer of Signal Strength Indication ..................................................................................... 21
`4.5
`Transfer of Roaming Status Indication .................................................................................... 22
`4.6
`Transfer of Battery Level Indication of AG .............................................................................. 23
`4.7
`Query Operator Selection........................................................................................................ 23
`4.8
`Report Extended Audio Gateway Error Results Code ............................................................ 24
`4.9
`Transfer of Call, Call Setup and Held Call Status ................................................................... 25
`4.10
`Audio Connection Setup.......................................................................................................... 25
`4.11
`Audio Connection Release...................................................................................................... 26
`4.12
`Answer an Incoming Call......................................................................................................... 27
`4.13
`4.13.1 Answer Incoming Call from the HF – In-Band Ringing ..................................................... 27
`4.13.2 Answer Incoming Call from the HF – No In-Band Ringing................................................ 28
`4.13.3 Answer Incoming Call from the AG................................................................................... 29
`4.13.4 Change the In-Band Ring Tone Setting............................................................................ 30
`4.14 Reject an Incoming Call........................................................................................................... 31
`4.14.1 Reject an Incoming Call from the HF................................................................................ 31
`4.14.2 Rejection/Interruption of an Incoming Call in the AG........................................................ 32
`4.15
`Terminate a Call Process ........................................................................................................ 33
`4.15.1 Terminate a Call Process from the HF.............................................................................. 33
`4.15.2 Terminate a Call Process from the AG ............................................................................. 33
`4.16
`Audio Connection Transfer Towards the HF........................................................................... 34
`4.17
`Audio Connection Transfer Towards the AG........................................................................... 35
`4.18
`Place a Call With the Phone Number Supplied by the HF ...................................................... 36
`4.19 Memory Dialing from the HF.................................................................................................... 37
`4.20
`Last Number Re-Dial from the HF........................................................................................... 38
`4.21 Call Waiting Notification Activation.......................................................................................... 40
`4.22
`Three Way Call Handling......................................................................................................... 41
`4.22.1 Three Way Calling—Call Waiting Notification................................................................... 43
`4.22.2 Three Way Calls – Third Party Call Placed from the HF .................................................. 44
`4.23 Calling Line Identification (CLI) Notification............................................................................. 45
`4.24
`The HF Requests Turning Off the AG’s EC and NR ............................................................... 45
`4.25
`Voice Recognition Activation................................................................................................... 46
`4.25.1 Voice Recognition Activation – HF Initiated...................................................................... 47
`4.25.2 Voice Recognition Activation – AG Initiated ..................................................................... 48
`
`25 November 2005
`
`Ex. 1028
`Page 05 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`4.25.3 Voice Recognition Deactivation ........................................................................................ 48
`4.26
`Attach a Phone Number to a Voice Tag.................................................................................. 49
`4.27
`Transmit DTMF Codes ............................................................................................................ 50
`4.28 Remote Audio Volume Control................................................................................................ 50
`4.28.1 Audio Volume Control ....................................................................................................... 50
`4.28.2 Volume Level Synchronization.......................................................................................... 51
`4.29 Response and Hold ................................................................................................................. 53
`4.29.1 Query Response and Hold Status .................................................................................... 53
`4.29.2 Put an Incoming Call on Hold from HF ............................................................................. 54
`4.29.3 Put an Incoming Call on Hold from AG............................................................................. 55
`4.29.4 Accept a Held Incoming Call from HF............................................................................... 56
`4.29.5 Accept a Held Incoming Call from AG .............................................................................. 57
`4.29.6 Reject a Held Incoming Call from HF................................................................................ 57
`4.29.7 Reject a Held Incoming Call from AG ............................................................................... 58
`4.29.8 Held Incoming Call Terminated by Caller ......................................................................... 60
`4.30
`Subscriber Number Information............................................................................................... 61
`4.31
`Enhanced Call Status Indications............................................................................................ 62
`4.31.1 Query List of Current Calls in AG...................................................................................... 62
`4.31.2 Indication of Status for Held Calls..................................................................................... 62
`4.32
`Enhanced Call Control Mechanisms ....................................................................................... 65
`4.32.1 Release Specified Call Index ............................................................................................ 65
`4.32.2 Private Consultation Mode................................................................................................ 66
`4.33
`AT Command and Results Codes........................................................................................... 66
`4.33.1 General ............................................................................................................................. 66
`4.33.2 AT Capabilities Re-Used from GSM 07.07 and 3GPP 27.007 ......................................... 67
`4.33.3 Bluetooth Defined AT Capabilities .................................................................................... 75
`Serial Port Profile ........................................................................................................................... 81
`RFCOMM Interoperability Requirements ................................................................................ 81
`L2CAP Interoperability Requirements ..................................................................................... 81
`SDP Interoperability Requirements ......................................................................................... 81
`5.3.1
`Interaction with Hands-Free Profile Rev 0.96 Implementations ....................................... 84
`Link Manager (LM) Interoperability Requirements .................................................................. 84
`Link Control (LC) Interoperability Requirements ..................................................................... 85
`5.5.1 Class of Device ................................................................................................................. 85
`Synchronous Connection Interoperability Requirements ........................................................ 86
`Generic Access Profile................................................................................................................... 88
`Modes ...................................................................................................................................... 88
`Security Aspects...................................................................................................................... 88
`Idle Mode Procedures ............................................................................................................. 88
`References..................................................................................................................................... 89
`List of Acronyms and Abbreviations............................................................................................... 90
`List of Figures................................................................................................................................. 91
`List of Tables.................................................................................................................................. 93
`
`5.1
`5.2
`5.3
`5.4
`5.5
`5.6
`6.1
`6.2
`6.3
`
`Page 6 of 93
`
`25 November 2005
`
`5
`
`6
`
`7
`8
`9
`10
`
`
`Ex. 1028
`Page 06 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 7 of 93
`
`1 Introduction
`1.1 Scope
`This document defines the protocols and procedures that shall be used by devices
`implementing the Hands-Free Profile. The most common examples of such devices are
`in-car Hands-Free units used together with cellular phones, or wearable wireless
`headsets.
`The profile defines how two devices supporting the Hands-Free Profile shall interact
`with each other on a point-to-point basis.
`An implementation of the Hands-Free Profile typically enables a headset, or an
`embedded Hands-Free unit to connect, wirelessly, to a cellular phone for the purposes
`of acting as the cellular phone’s audio input and output mechanism and allowing typical
`telephony functions to be performed without access to the actual phone.
`
`25 November 2005
`
`Ex. 1028
`Page 07 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 8 of 93
`
`1.2 Profile Dependencies
`In Figure 1.1, the Bluetooth profile structure and the dependencies of the profiles are
`depicted. A profile is dependent upon another profile if it re-uses parts of that profile, by
`explicitly referencing it. Dependency is illustrated in the figure below.
`
`
`Generic Access Profile
`
`TCS Binary based profiles
`Cordless
`Telephony Profile
`
`Intercom Profile
`
`Service Discovery
`Application Profile
`
`Serial Port Profile
`
`Dial-up Networking
`Profile
`
`Fax Profile
`
`Headset Profile
`
`Generic Object Exchange
`Profile
`
`File Transfer
`Profile
`
`Object Push Profile
`
`Synchronization
`Profile
`
`Hands-Free Profile
`
`SIM Access Profile
`
`
`
`Figure 1.1: Bluetooth Profiles
`As indicated in the figure, the Hands-Free Profile is dependent upon both the Serial Port
`Profile [5] and the Generic Access Profile [4]. Details are provided in Sections 5 (Serial
`Port Profile) and 6 (Generic Access Profile).
`1.3 Symbols and Conventions
`1.3.1 Requirement Status Symbols
`In this document, the following symbols are used:
`"M" for mandatory to support
`•
`•
`"O" for optional to support
`•
`"X" for excluded (used for capabilities that may be supported by the device, but the
`Hands-Free Profile shall not use these capabilities)
`
`25 November 2005
`
`Ex. 1028
`Page 08 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 9 of 93
`
`"C" for conditional to support
`•
`"N/A" for not applicable (in the given context this capability is not defined)
`•
`Some capabilities or features (identified as “X”), mandated according to the relevant
`Bluetooth specifications, are excluded with respect to this profile because they may
`degrade the operation of devices in the particular use case. Therefore, features or
`capabilities labeled “X” shall never be activated while operating in a use case where
`they are labeled as such.
`
`1.3.2 Naming Conventions
`In this document, the following naming conventions are used:
`• Where “Core Specification” is said it refers to the Bluetooth Core Specification 1.1 or
`later adopted by the Bluetooth® SIG.
`• Where “LMP link” is said, it means a Link Manager (LM) level link over which only
`Link Manager Protocol (LMP) commands are conveyed.
`• Where “RFCOMM connection” is said, it means the presence of a virtual serial port
`as specified in [5].
`• Where “Service Level Connection” is said, it means a synchronized high-level
`protocol connection involving a portion of the protocol stack. In this specific case, it
`refers to the presence of a RFCOMM connection, and assumes that the HF has
`synchronized itself to the state of the AG using the specified Service Level
`Connection initialization procedure.
`• Where “Service Level Connection initialization” is said, it means the execution of the
`set of AT commands and responses specified by the profile necessary to
`synchronize the state of the HF with that of the AG.
`• Where “Service Level Connection establishment” is said, it means the combined
`process of establishing the RFCOMM connection, as well as the necessary device
`synchronization using Service Level Connection initialization.
`• Where “Synchronous Connection” is said, it means a SCO or eSCO logical link
`intended for supporting a full duplex Audio Connection.
`• Where “Audio Connection” is said, it means a Synchronous Connection including the
`means to provide a complete audio path between two devices assuming roles within
`this profile.
`• Where “incoming call” is said, it means a call connection in the direction “Phone
`Network=>AG”, such that it is initiated by the Network to which the AG is attached.
`• Where ‘outgoing call’ is said, it means a call connection in the direction ”AG=>Phone
`Network”, such that it is initiated by the AG towards the Network to which it is
`attached.
`
`25 November 2005
`
`Ex. 1028
`Page 09 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 10 of 93
`
`1.3.3 Signaling Diagram Conventions
`The signaling diagrams in this specification are informative only. Within the diagrams,
`the following conventions are used to describe procedures:
`
`A
`
`B
`
`Mandatory signal sent by A
`
`Optional signal sent by B
`
`Mandatory procedure initiated by B
`
`Optional procedure initiated by A
`
`Mandatory procedure initiated by either A or B
`
`Optional procedure initiated by either A or B
`
`Current state/condition
`
`Optional state/condition
`
`Figure 1.2: Conventions used in signaling diagrams
`
`
`
`
`
`
`25 November 2005
`
`Ex. 1028
`Page 10 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 11 of 93
`
`2 Profile Overview
`2.1 Protocol Stack
`The figure below shows the protocols and entities used in this profile.
`Application
`Application
`(Audio port emulation)
`(Audio driver)
`
`Hands-Free control
`
`Hands-Free control
`
`RFCOMM
`
`SDP
`
`RFCOMM
`
`SDP
`
`LMP
`
`L2CAP
`
`LMP
`
`L2CAP
`
`Baseband
`
`Baseband
`
`
`
`Hands-Free side
`
`Audio Gateway side
`Figure 2.1: Protocol stack
`The Baseband, LMP and L2CAP are the OSI layer 1 and 2 Bluetooth protocols.
`RFCOMM is the Bluetooth serial port emulation entity. SDP is the Bluetooth Service
`Discovery Protocol. See [1] for more details on these topics.
`Compatibility to v1.1 or later Core Specification is required.
`Hands-Free control is the entity responsible for Hands-Free unit specific control
`signaling; this signaling is AT command based.
`Although not shown in the model above, it is assumed by this profile that Hands-Free
`Control has access to some lower layer procedures (for example, Synchronous
`Connection establishment).
`The audio port emulation layer shown in Figure 2.1 is the entity emulating the audio port
`on the Audio Gateway, and the audio driver is the driver software in the Hands-Free
`unit.
`For the shaded protocols/entities in Figure 2.1, the Serial Port Profile [5] is used as the
`base standard. For these protocols, all mandatory requirements stated in the Serial Port
`Profile apply except in those cases where this specification explicitly states deviations.
`2.2 Configuration and Roles
`Figure 2.2 below shows typical configurations of devices for which the Hands-Free
`Profile is applicable:
`
`25 November 2005
`
`Ex. 1028
`Page 11 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`
`Simple Headset
`
`Page 12 of 93
`
`Bluetooth
`Connection
`
`OR
`
`Cellular
`Connection
`
`Public
`Wireless
`Network
`
`Hands-Free
`unit installed
`in the car
`
`
`
`Figure 2.2: Typical Hands-Free Use
`The following roles are defined for this profile:
`Audio Gateway (AG) – This is the device that is the gateway of the audio, both for
`input and output. Typical devices acting as Audio Gateways are cellular phones.
`Hands-Free unit (HF) – This is the device acting as the Audio Gateway’s remote audio
`input and output mechanism. It also provides some remote control means.
`These terms are used in the rest of this document to designate these roles.
`2.3 User Requirements and Scenarios
`The following rules apply to this profile:
`a) The profile states the mandatory and optional features when the “Hands-Free
`Profile” is active in the Audio Gateway and the Hands-Free unit.
`b) The profile mandates the usage of CVSD for transmission of audio (over the
`Bluetooth link). The resulting audio is monophonic, with a quality that, under normal
`circumstances, does not have perceived audio degradation.
`c) Between the Hands-Free unit and the Audio Gateway, only one Audio Connection
`per Service Level Connection at a time is supported.
`d) Both the Audio Gateway and the Hands-Free unit may initiate Audio Connection
`establishment and release. Valid speech data shall exist on the Synchronous
`Connection in both directions after the Audio Connection is established.
`e) Whenever an “Audio Connection” exists, a related “Service Level Connection” shall
`also exist.
`f) The presence of a “Service Level Connection” shall not imply that an “Audio
`Connection” exists. Releasing a “Service Level Connection” shall also release any
`existing “Audio Connection” related to it.
`2.4 Profile Fundamentals
`Baseband authentication and encryption is optional for both the Hands-Free unit and
`the Audio Gateway. If both devices support authentication and encryption, the
`application on either device may require its use.
`
`25 November 2005
`
`Ex. 1028
`Page 12 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 13 of 93
`
`A Hands-Free unit may be able to use the services of the Audio Gateway without the
`creation of a secure connection. It is implementation specific whether the Hands-Free
`unit provides or supports security enforcement for the user.
`Whenever baseband authentication and/or encryption is used, the two devices shall
`create a secure connection using the GAP authentication procedure as described in
`Section 5.1 of the Generic Access Profile [4]. This procedure may include entering a
`Bluetooth PIN code and creation of proper link keys. In cases when the UI of the Hands-
`Free unit is limited, a fixed Bluetooth PIN code may be used during the GAP
`authentication procedure.
`If a LMP link is not already established between the Hands-Free unit and the Audio
`Gateway, the LMP link shall be set up before any other procedure is performed.
`There are no fixed master of slave roles in the profile.
`The Audio Gateway and Hand-Free unit provide serial port emulation. For the serial port
`emulation, RFCOMM (see [1]) is used. The serial port emulation is used to transport the
`user data including modem control signals and AT command from the Hands-Free unit
`to the Audio Gateway. The AT commands are parsed by the Audio Gateway and
`responses are sent to the Hands-Free unit via the Bluetooth serial port connection.
`2.5 Conformance
`If conformance to this profile is claimed, all capabilities indicated as mandatory for this
`profile shall be supported in the specified manner (process mandatory). This also
`applies for all optional and conditional capabilities for which support is indicated. All
`mandatory, optional and conditional capabilities, for which support is indicated, are
`subject to verification as part of the Bluetooth Qualification Program.
`
`25 November 2005
`
`Ex. 1028
`Page 13 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Hands-Free Profile (HFP) 1.5
`
`Page 14 of 93
`
`3 Application layer
`This section describes the feature requirements for units complying with Hands-Free
`Profile.
`Table 3.1 below shows the feature requirements for this profile.
`
`Feature
`Support in HF
`1.
`Connection management
`M
`M(note 1)
`2.
`Phone status information
`M
`M
`M
`M
`
`Support in AG
`M
`M
`
`M
`M
`O
`M
`
`M
`M
`M
`
`M
`M
`O(note 3)
`M
`O
`O
`
`O
`M
`O
`
`O
`M
`M
`
`3.
`4
`5.
`6.
`
`7.
`8.
`9.
`
`10.
`11.
`12.
`
`13.
`14.
`15.
`
`16.
`17.
`18.
`
`Audio Connection handling
`Accept an incoming voice call
`Reject an incoming voice call
`Terminate a call
`
`Audio Connection transfer during an ongoing call
`Place a call with a phone number supplied by the HF
`Place a call using memory dialing
`
`M
`O
`O
`
`Place a call to the last number dialed
`Call waiting notification
`Three way calling
`
`Calling Line Identification (CLI)
`Echo canceling (EC) and noise reduction (NR)
`Voice recognition activation
`
`Attach a Phone number to a voice tag
`Ability to transmit DTMF codes
`Remote audio volume control
`
`Respond and Hold
`19.
`Subscriber Number Information
`20.
`21a. Enhanced Call St

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket