BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 199 of 440
`
`Headset Profile
`
`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 capabilities, and optional and conditional capabilities
`for which support is indicated, are subject to verification as part of the
`Bluetooth certification program.
`
`Profile Overview
`
`1 December 1999
`
`AFFLT0294509
`
`Samsung Ex. 1119 p. 1281
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Headset Profile
`
`3 APPLICATION LAYER
`
`page 200 of440
`
`Bluetooth-
`
`This section describes the feature requirements on units complying with the
`Headset profile.
`
`'i'abie
`
`shows the feature requirements made by this profile.
`
`1.
`
`Incoming audio connection
`
`M
`
`M
`
`Outgoing audio connection
`
`Audio connection transfer
`
`Remote audio volume control
`
`Table 3.1: Appiication iayer procedures
`
`In the table above, incoming and outgoing shall be interpreted from the head-
`set (HS) point of view.
`
`maps each feature to the procedures used for that feature. All proce-
`Tabie
`dures are mandatory if the feature is supported.
`
`Feature
`
`Procedure
`
`Incoming audio connection
`
`Incoming audio connection establishment
`
`Audio connection release
`
`Outgoing audio connection
`
`Outgoing audio connection establishment
`Audio connection release
`
`Audio connection transfer
`
`Audio connection transfer
`
`Remote audio volume controi
`
`Remote audio volume control
`
`Table 3. 2: Appiication iayer feature to procedure mapping
`
`1 December 1999
`
`Application layer
`
`AFFLT029451 0
`
`Samsung Ex. 1119 p. 1282
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 201 of 440
`
`Headset Prof.-'ie
`
`4 HEADSET CONTROL INTEROPERABILITY
`
`REQUIREMENTS
`
`4.1
`
`INTRODUCTION
`
`The interoperability requirements for the Headset Control entity are completely
`contained in this chapter. 3et:tien 4.2 until At-.6 specify the requirements for the
`procedures directly relating to the application layer features.
`
`Eestion 4.?’ specifies the AT commands and results codes used for signalling
`purposes.
`
`Setttlon ztfs specifies how the layers beneath the Headset Control entity are
`used to establish and release a connection.
`
`4.2 INCOMING AUDIO CONNECTION
`
`Upon an internal or user generated event, the AG will initiate connection estab-
`lishment (see Seotien 4.8), and once the connection is established, will send
`an unsolicited result code RING to alert the user. The RING may be repeated
`for as tong as the connection establishment is pending.
`
`Optionally, the AG may provide an in-band ringing tone‘. In this case, first SCO
`link establishment takes place.
`
`1. The in-band ringing tone is used to alert the user in the headset earpiece when the user is
`wearing the headset on his head.
`
`Headset Control Interoperability Requirements
`
`1 December 1999
`
`AFFLT029451 1
`
`Samsung Ex. 1119 p. 1283
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 202 of440
`
`Headset Profile
`
`Bluetooth-
`
`'[.-':scr Inlti.':li:d action
`
`.-’\'l'-{'I(l’l)
`
`establishlltmt will :1!
`lens-1 he csiahlisiicd Ell
`
`Figure 4.1:
`
`incoming audio connection establishment
`
`The user accepts the incoming audio connection by pressing the button on the
`headset. By doing this, the HS will send the AT+CKPD command {see Sesiicra
`-1%.?) to the AG, whereupon the AG establishes the SCO link (if not already
`established).
`
`4.3 OUTGOING AUDIO CONNECTION
`
`An outgoing audio connection is initiated on the HS by pushing the button. The
`HS will initiate connection establishment (see 8ec‘:Eo:'i 11.8), and will send the
`AT+CKPD command to the AG. Further internal actions may be needed on the
`AG to internally establish andior route an audio stream to the H82.
`
`The AG is responsible for establishing the SCO link.
`
`2. For a cellular phone a cellular call may need to be established, eg. using lasl dialled num-
`ber, pre-programmed number. Fora personal computer this e.g. relates to playing a wav file,
`or audio CD.
`
`1 December 1999 Headset Control Interoperability Requirements
`
`AFFLT029451 2
`
`Samsung Ex. 1119 p. 1284
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 203 of 440
`
`Headset Prof.-'ie
`
`lfscr inutuaaeat -.1i_-tum
`
`Figure 4.2: Outgoing audio connection estabiishment
`
`4.4 AUDIO CONNECTION RELEASE
`
`A call can be terminated either on the H3 or on the AG. On the HS based upon
`the button being pushed, on the AG based upon internal actions or user inter-
`vention.
`
`HS
`
`L".-‘Cr Inltlillcd action
`
`T’ ,.\'r - (‘K pr)
`
`Figure 4.3: Audio connection reiease — HS initiated
`
`Headset Control Interoperability Requirements
`
`1 December 1999
`
`AFFLT029451 3
`
`Samsung Ex. 1119 p. 1285
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 204 of440
`
`Headset Profiie
`
`lnlcnml C\1.‘l1l uscr 1'niti::lcnJ .':<:tIo11
`
`Figure 4.4: Audio connection reiease — AG initiated
`
`Irrespective of the initiating side, the AG is responsible for releasing the con-
`nection (see Se-stéon 4.8).
`
`4.5 AUDIO CONNECTION TRANSFER
`
`An audio connection can be transferred from AG to H8 or from HS to AG. The
`
`connection is transferred to the device initiating the transfer.
`
`4.5.1 Audio connection transfer from AG to HS
`
`The audio connection transfer from AG to H8 is initiated by a user action on the
`HS side, which results in an AT+CKPD command being sent to the AG.
`
`L'scr inili:nc1.| zvclion
`
`Culutcution cstziblisitlmnt
`
`Figure 4. 5: Audio connection transfer from AG to H8
`
`1 December 1999 Headset Control Interoperability Requirements
`
`AFFLT0294514
`
`Samsung Ex. 1119 p. 1286
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 205 of 440
`
`Headset Prof.-'ie
`
`4.5.2 Audio connection transfer from HS to AG
`
`The audio connection transfer from HS to AG is initiated by a user action on the
`AG.
`
`L'5c1' 1mti.::Icd ncuon
`
`Figure 4.5: Audio connection transfer from HS to AG
`
`4.6 REMOTE AUDIO VOLUME CONTROL
`
`The AG can control the gain of the microphone and speaker of the HS by send-
`ing unsolicited result codes +VGM and +VGS respectively. There is no limit to
`the amount and order of result codes. as long as there is an active audio con-
`nection ongoing. When supporting the remote audio volume control, an imple-
`mentation is not mandated to support both the control of the microphone
`volume and speaker volume.
`
`sch microphulic gum
`
`sci spunkcr gmn
`
`Figure 4. 7: Audio volume controi — example How
`
`Headset Control Interoperability Requirements
`
`1 December 1999
`
`AFFLT029451 5
`
`Samsung Ex. 1119 p. 1287
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 206 of440
`
`Headset Profile
`
`Bluetooth-
`
`Both the speaker and microphone gain are represented as parameter to the
`+VGS and +VG M, on a scale from 0 to 15. The values are absolute values,
`
`relating to a particular (implementation-dependent) volume level controlled by
`the H8.
`
`The HS may store the VGS and VGM settings at connection release, to restore
`the volume levels at the next connection establishment. At connection estab-
`
`lishment, the HS shall inform the AG of the (restored) volume levels using the
`AT commands +VGS and +VGM. In case local means are implemented on the
`HS to control the volume levels, the HS shall also use the AT commands -I-VGS
`and +VGlvt to inform the AG of any changes in the volume levels.
`
`|.nc:a| mznon to snl
`spt::||s::r \.'01Ii|I11i.'
`
`:\'1" \-Ti-S ' 1‘
`
`Figure 4.8: Volume level synchronlzaflon — example flow
`
`1 December 1999 Headset Control Interoperability Requirements
`
`AFFLT029451 6
`
`Samsung Ex. 1119 p. 1288
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 207 of 440
`
`Headset Profile
`
`4.7 AT COMMANDS AND RESULT CODES
`
`4.7.1 General
`
`For the exchange of the commands and unsolicited results codes, the format.
`syntax and procedures of V.250 it; apply, with the exception that only one com-
`mand (or unsolicited result code) per command line needs to be expected.
`
`The headset profile uses a subset of AT commands and result codes from
`existing standards. These are listed in Sectiort ti-.?‘..23. For those AT commands
`and result codes where no existing commands applied, 53st.-ties“: at-.?.3 defines
`additional ones.
`
`4.7.2 AT capabilities re-used from V.250 and GSM 07.07
`
`The mandatory set of AT commands and unsolicited result codes are indicated
`in Table #1.? below.
`
`AT capability
`
`Description
`
`The Incoming call indication of V.250 [t‘_;. Section 6.3.4.
`
`The keypad control command of GSM TS 07.0? £23. Section 8.7. For
`<keys>, the value of 200 indicates the Button on the headset being
`pushed. The <iime> and <pause> parameters have no meaning in the
`headset profile.
`
`Table 4.1: Mandatory AT capabilities
`
`4.7.3 Bluetooth-defined AT capabilities
`
`Optionally, the AT capabilities as indicated in Tania 4.2 may be supported.
`
`AT capability Syntax
`
`Description
`
`Microphone
`gain
`
`+VGM=<gain
`2-
`
`Speaker gain
`
`Unsolicited result code issued by the AG
`to set the microphone gain of the HS.
`<galn> is an unsigned octet. relating to a
`particular (implementation-dependent)
`volume level controlled by the HS.
`
`Unsolicited result code issued by the AG
`to set the speaker gain of the HS. <gain>
`is an unsigned octet, relating to a particu-
`lar (implementation-dependent) volume
`level controlled by the HS.
`
`Values
`
`<gain>: 0-15
`
`<gain>: 0-15
`
`Table 4. 2: Optional AT capabilities
`
`Headset Control Interoperability Requirements
`
`1 December 1999
`
`AFFLT029451 7
`
`Samsung Ex. 1119 p. 1289
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Headset Profile
`
`AT capability
`
`Description
`
`Microphone
`gain level
`report
`
`Command issued by the HS to report the
`current microphone gain level setting to
`the AG. <gain> is an unsigned octet.
`relating to a particular (implementation-
`dependent) volume level controlled by the
`HS.
`
`page 208 of440
`
`Bluetooth-
`
`<gain>: 0-15
`
`Speaker gain
`level indica-
`lion report
`
`+VGS=<gain> Command issued by the HS to report the
`current speaker gain level setting to the
`AG. <gain> is an unsigned octet. relating
`to a particular {implementation-depem
`dent) volume level controlled by the HS.
`
`<gain>: 0-15
`
`Table 4.2: Optional AT capabilities
`
`4.8 LOWER LAYER HANDLING
`
`This section describes how the layers below the Headset Control entity are
`used to establish and release a connection.$.ecti-on 4.8.? describes how con-
`
`4.8.2
`nections are handled when the PARK mode is not supported.
`describes how connections are handled when the PARK mode is supported.
`
`4.8.1 Connection handling without PARK mode
`
`4.8.1.1 Connection establishment
`
`Both the HS and the AG can initiate connection establishment. If there is no
`
`RFCOMM session between the AG and the HS, the initiating device shall first
`initialize RFCOM M. Connection establishment shall be performed as described
`in Election ‘.13 of GAP and :"Se:';iion 3 of SPP.
`
`4.8.1.2 Connection release
`
`When the audio connection is released, the connection may be released as
`well. The AG always initiates connection release.
`
`4.8.2 Connection handling with PARK mode
`
`4.8. 2.1 Connection establishment
`
`If the PARK mode is supported, the connection is established once (e.g. on the
`first request for an audio connection). Later, when an audio connection is
`required. the parked device is unparked. In this section, for correct interpreta-
`tion of the flows given in Section 4.2 to 4.6, the connection establishment is
`referred to as initial connection establishment, whereas the unparking is
`referred to as connection establishment.
`
`1 December 1999 Headset Control Interoperability Requirements
`
`AFFLT029451 B
`
`Samsung Ex. 1119 p. 1290
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 209 of 440
`
`Headset Protite
`
`initiai connection establishment shall be performed as described in Section ‘?.3
`of GAP and Section 3 of SPP. Both sides may initiate the initial connection
`establishment. After initial connection establishment, the park mode is acti-
`vated.
`
`In i:i§Lt!’é3 4.9 the behavior is described in case an audio connection needs to
`be established — the parked device will be unparked. The unpark can be initi-
`ated from either side, depending where the request for an audio connection
`originated. If the PARK mode is used, neither RFCOMM DLCs nor the LZCAP
`channel is released.
`
`HS(AG)
`
`'_
`
`' AG(HS)
`
`Figure 4. 9: Connection estabtishment ~ Unparking a parked device
`
`4. 8.2. 2 Connection reiease
`
`When the audio connection is released, the connection is parked again, as
`indicated in Figure 4.10.
`
`l HS(AG)
`
`l a
`
`Figure 4.10: Connection retease - Parking
`
`When the audio connection is released, the complete connection may alterna-
`tively be released. The AG always initiates connection release.
`
`Headset Control Interoperability Requirements
`
`1 December 1999
`
`AFFLT029451 9
`
`Samsung Ex. 1119 p. 1291
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Headset Profile
`
`5 SERIAL PORT PROFILE
`
`page 210 of440
`
`Bluetooth-
`
`This profile requires compliance with the S:-3-rial Port Profile. The following text
`together with the associated sub-clauses defines the requirements with regard
`to this profile, in addition to the requirements as defined in the E:'5er'iet Paar? Pa)-
`‘file.
`
`As with the headset profile, both the AG and the HS can initiate connection
`establishment. For the purposes of reading the E3e:‘:=al Port .”=-"-‘r‘c.=t'Elr:, both the AG
`and the HS can assume the roie of Device A and B.
`
`5.1 RFCOMM INTEROPERABILITY REQUIREMENTS
`
`For the RFCOMM layer, no additions to the requirements as stated in the Serial
`Port Profile Section -5‘: shall apply.
`
`5.2 LZCAP INTEROPERABILITY REQUIREMENTS
`
`For the LZCAP layer, no additions to the requirements as stated in the Serial
`Port Profile Section 5 shall apply.
`
`1 December 1999
`
`Serial Port Profile
`
`AFFLT0294520
`
`Samsung Ex. 1119 p. 1292
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 211 of 440
`
`Headset Profile
`
`5.3 SDP INTEROPERABILITY REQUIREMENTS
`
`This profile defines following service records for the headset and the audio
`gateway respectively.
`
`The codes assigned to the mnemonics used in the Value column as well as the
`codes assigned to the attribute identifiers (if not specifically mentioned in the
`AttrID column) can be found in the Bluetooth Assigned Numbers section.
`
`we
`
`Ser\riceC|ass|DLisl
`
`Serviceclassfl
`
`Ser\riceC|ass1
`
`Protoco!DescriptorList
`
`Protocolfl
`
`Protocol1
`
`Protocol
`
`Specific
`Paramelerfl
`
`BluetoothProfiie
`
`DescriplorList
`
`Profileo
`
`Paramo
`
`Ser\riceName
`
`Remote audio
`volume control
`
`Supported
`Profiles
`
`Profile
`Version
`
`Display-
`abie Text
`name
`
`Headset
`
`M0133‘
`
`Service-
`provider
`defined
`
`TruelFa|se
`
`Table 5.1: Service Record for Headset
`
`*.
`
`Indicating version 1.0
`
`Serial Port Profile
`
`1 December 1999
`
`AFFLT0294521
`
`Samsung Ex. 1119 p. 1293
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 212of440
`
`Headset Profile
`
`{E
`ServiceClass iD List
`M
`
`Serviceclasso
`
`ServiceC|ass1
`
`ProtooolDescriptorList
`
`Protocolt)
`
`Protoco|1
`
`Protocol
`
`Specific
`Parametero
`
`B|uetoothProfile
`Descriptorldst
`
`Profilet}
`
`Pararnfl
`
`ServiceName
`
`UUID
`
`Headset
`
`M
`
`UUID
`
`Generic
`Audio
`
`L2CAP
`
`RF COM M
`
`N=server
`
`channel #
`
`'
`
`Supported
`Profile
`
`UUID
`
`Headset
`
`Profile
`Version
`
`Display-
`able Text
`name
`
`Uint16
`
`0,0100‘
`
`String
`
`Service-
`provider
`defined
`
`Tabie 5.2: Service Record for the Audio Gateway
`w
`
`.
`
`Indicating version 1.0
`
`5.4 LINK MANAGER (LM) INTEROPERABILITY
`REQUIREMENTS
`
`In addition to the requirements for the Link Manager as stated in the
`Port
`on page 165, this profile mandates support for SCO links, in both
`the HS and AG.
`
`1 December 1999
`
`Serial Port Profile
`
`AFFLT0294522
`
`Samsung Ex. 1119 p. 1294
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 213 of 440
`
`Headset Profiie
`
`5.5 LINK CONTROL (LC) INTEROPERABILITY
`REQUIREMENTS
`
`In the table below, changes to the support status as listed in the Serial Port
`Profile, Section 8, "i‘a‘cie 8.1 on page 38:: are listed.
`
`|
`
`Inquiry
`
`Inquiry scan
`
`Paging
`
`Page scan
`
`Type R0
`
`Type R1
`
`Type R2
`
`Voice codec
`
`CVSD
`
`Tabie 5.3: LC capabilities
`
`5.5.1 Class of Device
`
`A device which is active in the HS role shall, in the Class of Device field:
`
`1. Set the bit ‘Audio’ in the Service Class field
`
`2. Indicate ‘Audio’ as Major Device ciass
`
`3. Indicate “Headset" as the Minor Device class
`
`An inquiring AG may use this to filter the inquiry responses.
`
`Serial Port Profile
`
`1 December 1999
`
`AFFLT0294523
`
`Samsung Ex. 1119 p. 1295
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Headset Profile
`
`6 GENERIC ACCESS PROFILE
`
`page 214 of440
`
`Bluetooth-
`
`This section defines the support requirements for the capabilities as defined in
`G:-znesréc .9-X(:(;:ess Profile.
`
`6.1 MODES
`
`The table shows the support status for Modes within this profile.
`
`1
`
`Discoverability modes
`
`Non-discoverable mode
`
`Limited discoverable mode
`
`General discoverable mode
`
`Connectabllity modes
`Non-connectable mode
`
`Connectable mode
`
`Pairing modes
`
`Non-pairable mode
`
`Palrable mode
`
`Table 6.1: Modes
`
`6.2 SECURITY ASPECTS
`
`No changes to the requirements as stated in the Generic Access Profile.
`
`6.3 IDLE MODE PROCEDURES
`
`The table shows the support status for Idle mode procedures within this profile.
`
`Procedure
`
`General Enquiry
`
`Limited inquiry
`
`Name discovery
`
`Device discovery
`
`Bonding
`
`Support in HS
`
`Support in AG
`
`NJA
`
`NIA
`
`NIA
`
`NIA
`
`M
`
`0
`
`0
`
`O
`
`M (Note 1)
`
`M {Note 1}
`
`Note 1: Mandatory for the AG to support initiation of bonding. and forthe HS to accept bond-
`ing.
`
`Table 6.2:
`
`idle mode procedures
`
`214
`
`1 December 1999
`
`Generic Access Profile
`
`AFFLT0294524
`
`Samsung Ex. 1119 p. 1296
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 215 of 440
`
`Headset Profile
`
`7 REFERENCES
`
`[1]
`
`[2]
`
`International Telecommunication Union, "ITU-T Recommendation V.250”
`
`ETS 300 916 (GSM 07.07) version 5.6.0
`
`References
`
`1 December 1999
`
`AFFLT0294525
`
`Samsung Ex. 1119 p. 1297
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Headset Profile
`
`8 LIST OF FIGURES
`
`page 216 of 440
`
`Bluetooth.
`
`Figure 1.1: Biueteoih Frames ................................................................... ..1€~}3
`
`Figure 1.2: Arrows used in signaiiing diagrams ....................................... .. 195
`Figure 23?:
`Pretoco! rrsczaiei .................
`................................................... .. ‘E96
`
`‘E9?’
`Figure 2.2: Headset prefiie. examgzée wiih ceiiuiar phone
`Figure 2.3: Headset pr'efi§e. exammie wiih szaersenai cea'r*:_:m¥.:=.>r ................. ..1¥.??
`
`F-'§\;ure 4.1:
`
`inceming aasdie mzwnecitit:-n estehiésiwment ............................. .. 202
`
`Figure #2: Guigeing audie (;cmne£:t§en estahiishmen? ............................. .293
`
`Figure 4.3: Audie oonnectécm reiease
`
`inmates‘
`
`Figure :1-.ré'. Audio co:1nect§o::.r'eEease — AC5
`
`Figure 4.5: Audit: a2c:+.r~=nec€icsn
`
`transfer‘ from AG te HS .............................. .. 2-54
`
`Figure 4.6‘. Audie r:c:.n.nec%.ir:rntranssferfromH3110
`
`Figure 4.7: Audio Vx’35Ui":"=-I-3 -1-antmi
`
`exemg".-ie {F
`
`‘N
`
`Figure 4.8: Votume !:=3v's3E syncivonizatéon
`
`exampie flow
`
`266
`
`E’-égure 4.9:
`
`C<3=“mec:ti0:'1. esiabiishmeni Unparking :3 gzarked device ....... ..f:‘=I)9
`
`Figure 4.10: C<.2rmec:tic:.-2 release ~-
`
`1 December 1999
`
`List of Figures
`
`AFFLT0294526
`
`Samsung Ex. 1119 p. 1298
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Headset Proffle
`
`9 LIST OF TABLES
`
`page 217 of 440
`
`Bluetouth.
`
`Tabie :
`
`"fame 3.2:
`
`Tame 4.1:
`
`Tabée 4.2:
`
`Tebie 5.1:
`
`T:-ibis:
`
`Tabis: 5.3:
`
`"fasbie Sf:
`
`Tabie
`
`A_;>;.=iEcat§cm §a§,«‘ez- pa'oce::'ures .................................................. ..2€}(}
`K-\p;:iEc:atic3n Sayer femur:-3 to §}F{3€:E3{Zii§E‘£-:- mapping; ..................... ..2{3f3
`
`;*~..'§ar:cz'r.—2ir_:wr AT cagaabiiizies ...................................................... ..2£‘:?’
`
`Opiionai AT c:a_n2a‘:3%ii%Ees .......................................................... .29?
`Service Rem-rd for
`
`Se:-«ice §'%s:carr_i fa“.-r
`
`Auréio Gateway ..................................
`
`...........................
`LC capaiuiiities ..........................................
`Mczdes .................................................................................... ..2’§4
`
`iciée made pr'oceCSu:'es ............................................................ ..2’¥4
`
`List of Tables
`
`1 December 1999
`
`AFFLT0294527
`
`Samsung Ex. 1119 p. 1299
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 218 of-440
`
`Headset Profile
`
`1 December 1999
`
`List 01 Tabtes
`
`AFFLT029452B
`
`Samsung Ex. 1119 p. 1300
`
`

`
`iUP NETWORKING PROFILE
`
`This rofile iflefines the requirements for
`Blueoth d
`ices necessary for the support
`of th Dial-u Networking use case. The
`requ ‘* ement are expressed in terms of end-
`user-§servic$, and by defining the features
`S
`andfproced res that are required for interoper-
`abiiity bet een Bluetooth devices in the Dial-
`iJi§'Netwo§(ing use case.
`.3.3»
`if
`
`AFFLT0294529
`
`Samsung Ex. 1119 p. 1301
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 220 of-440
`
`Dial-up Networking F‘-‘rofr'J'e
`
`1 December 1999
`
`AFFLT0294530
`
`Samsung Ex. 1119 p. 1302
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 221 of 440
`
`Dial-up Networking Profile
`
`CONTENTS
`
`imrcsziuctim ................................................................................ ......223
`
`1.’!
`1.12
`
`1.3
`
`Biuetooth Profiie Structure......._......._..........._......._..........._.......223
`
`Symimis and c<:r1v'ent§t:ns
`1.3.‘!
`ReqL:iremen§. siatus syrnbczis .....................................
`
`1.3.2
`€.C-3.3
`
`Signaiiing diagram sconventions.................................._225
`Notation for ténmrs and counters
`
`Prcsfiie
`
`C0nf:gL:r'ati0ns and mies
`
`..
`
`User requirézments and sscamarios
`Profék-2 fuaxdazneaatais .............................................................. .229
`
`Ccmtarmance ......................................................................... .2253
`
`2.3
`2.4
`
`2.5
`
`Appiicatien iayezr ............................................................................ "239
`3.1
`Service overview .................................................................... ...23{}
`3.2
`Data calls ............................................................................... ..2.’3{‘:
`
`3.3
`
`.’3.¢’§~
`
`Fax
`
`\!oica=: caiis .............................................................................. ..23€}
`
`fiiaiiéng and Csmtroi intemgzerabififiy fiaquirements ................... "231
`4.1
`A?" comrrzand sei Lssseci ........................................................... .23?
`
`Command syntax ...................................................... "231
`4.11
`61.1.2 Commanzfi ................................................................ IIQSE
`
`4.1.3
`
`Re::~;=..=E*.
`
`Caii progress audio
`
`Escape sequence .................................................................. "234
`
`4.23
`
`4.3
`
`Sariai Part Frame interogzerahfiiity Rezguirements
`
`5.1
`
`5.2
`
`5.3
`
`5.4
`
`5.5
`
`RFCOMM §r'm'«;roperahiiE2.y Fe.er.;ués'emer:ts........,........................
`
`.
`
`E..2C.ri\P Enterogrerabéiity Ra’-aqtafirementsa .................................... .335
`
`EDP interaperabiiity
`
`Link Manager (i..¥s»‘E) interspwabiiity Requirements ................. .238
`
`Link Com.-"vi {LC} EnietUper.a.biEity Requirerm:-rxis .................... .213?
`5.5.1
`Ciass of Device
`
`Gesmris: «Access Pmfiie Entammrahiiéty Requirenyents .............. "238
`modes .................................................................................... .233
`
`Seam-ity
`idie macie procedures
`
`1 December 1999
`
`AFFLTO294531
`
`Samsung Ex. 1119 p. 1303
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 222 of440
`
`Dial-up Networking Profile
`
`'2’
`
`List :3? Figures.
`
`LES? :3? T323263
`
`Bluetooth-
`
`1 December 1999
`
`AFFLT0294532
`
`Samsung Ex. 1119 p. 1304
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 223 of 440
`
`Dial-up Networking Profile
`
`1
`
`INTRODUCTION
`
`1.1 SCOPE
`
`The Dial-up Networking Profile defines the protocols and procedures that shall
`be used by devices implementing the usage model called ‘Internet Bridge‘ (see
`Bluetooth SIG MRD). The most common examples of such devices are
`modems and cellular phones.
`
`The scenarios covered by this profile are the following:
`
`- Usage of a cellular phone or modem by a computer as a wireless modem for
`connecting to a dial-up internet access server, or using other dial-up ser-
`vices
`
`Usage of a cellular phone or modem by a computer to receive data cells
`
`1.2 BLUETOOTH PROFILE STRUCTURE
`
`In Figure ‘tit. the Bluetooth profile structure and the dependencies of the pro-
`files are depicted. A profile is dependent upon another profile if it re-uses parts
`of that profile, by implicitly or explicitly referencing it. Dependency is illustrated
`in the figure: a profile has dependencies on the profi|e(s) in which it is
`contained — directly and indirectly.
`
`l...._§.E.*_.'_':‘!§'l?’i"'_$‘??i‘.l. 1."‘."'.‘§?*-“'35
`..
`Intercom Profile
`
`5
`
`Dial-up Networking
`Profile
`
`G
`.0b.
`Pforfigc
`lee
`
`te h
`Kc ange
`
`File Transfer
`Profile
`
`Object Push Profile
`
`S
`
`h
`
`_
`
`t.
`
`.&.2.:":.-9 --'99;--_.'e: . :
`
`LAN Access Profile
`
`:e>_:e..e.'e.'e'
`
`Figure 1.1: Bluetooth Profiles
`
`Introduction
`
`1 December 1999
`
`AFFLT0294533
`
`Samsung Ex. 1119 p. 1305
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Dial-up Networking Profile
`
`1.3 SYMBOLS AND CONVENTIONS
`
`1.3.1 Requirement status symbols
`
`In this document, the following symbols are used:
`
`page 224 of 440
`
`Bluetooth-
`
`‘M’ for mandatory to support (used for capabilities that shall be used in the
`profile);
`
`‘O’ for optional to support (used for capabilities that can be used in the profile);
`
`‘C’ for conditional support (used for capabilities that will be used in case a
`certain other capability is supported);
`
`‘X‘ for excluded (used for capabilities that may be supported by the unit but
`which shall never be used in the profile);
`
`‘NRA’ for not applicable (in the given context it is impossible to use this
`capability).
`
`Some excluded capabilities are capabilities that, according to the relevant
`Bluetooth specification, are mandatory. These are features that may degrade
`operation of devices following this profile. Therefore, these features shall never
`be activated while a unit is operating as a unit within this profile.
`
`1 December 1999
`
`lnlroduction
`
`AFFLT0294534
`
`Samsung Ex. 1119 p. 1306
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 225 of 440
`
`Dial-up Networking Profile
`
`1.3.2 Signalling diagram conventions
`
`The following arrows are used in diagrams describing procedures:
`
`(PROC4)
`
`i'l'.'.|Df"1I"“|'§\
`
`-A
`
`{MSG3)
`as
`
`i’l\l1.‘-'«‘f'-‘.A‘i
`
`A
`
`Table 1.1: Arrows used in signaii.-‘ng diagrams
`
`In the table above, the following cases are shown: PROC1 is a sub-procedure
`initiated by B. PROC2 is a sub-procedure initiated by A. PROC3 is a sub-
`procedure where the initiating side is undefined (may be both A and B).
`PROC4 indicates an optional sub-procedure initiated by A, and PROC5 indi-
`cates an optional sub-procedure initiated by B.
`
`MSG1 is a message sent from B to A. MSG2 is a message sent from A to B.
`MSG3 indicates an optional message from A to B, and MSG4 indicates an
`optional message from B to A.
`
`1.3.3 Notation for timers and counters
`
`'Fmers and counters may be introduced specific to this profile. To distinguish
`them from timers (counters) used in the Bluetooth protocol specifications and
`other profiles, these timers (counters) are named in the following format:
`‘TDNFHHUI ('NDN,:nnn').
`
`Introduction
`
`1 December 1999
`
`AFFLT0294535
`
`Samsung Ex. 1119 p. 1307
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Dial-up Networking Profile
`
`2 PROFILE OVERVIEW
`
`2.1 PROFILE STACK
`
`page 226 of 440
`
`Bluetooth.
`
`The figure below shows the protocols and entities used in this profile.
`
`Application
`
`(Modem emulation)
`
`flab
`
`Application
`
`(Modem driver)
`
`Dialling and control 4%) Dialling and control
`
`GT9
`
`<l
`
`i>
`
`<l—|>
`
`Gateway side
`
`Data terminal side
`
`Figure 2.1: Protocol model‘
`
`The Baseband. LMP and L2CAP are the OSI layer 1 and 2 Bluetooth protocols.
`RI‘-‘COMM is the Bluetooth adaptation of GSM TS 07.10 {S}, used for providing
`serial pott emulation. SDP is the Bluetooth Service Discovery Protocol. Dialling
`and control (see Section at) is the commands and procedures used for auto-
`matic dialling and control over the asynchronous serial link provided by the
`lower layers.
`
`The modem emulation layer shown in Figasre 2.1 is the entity emulating the
`modem, and the modem driver is the driver software in the data terminal.
`
`For the shaded protocolsientities in t“-“-égurc-:- 2?, The Seréal Port Profits is used
`as base standard. For these protocols, all requirements stated in Serial Port
`Profile apply, except in those cases where this profile explicitly states devia-
`tions.
`
`Note: Although not shown in the model above, it is assumed by this profile that
`the application layer has access to some lower layer procedures (for example
`SCO link establishment).
`
`1 December 1999
`
`Profile overview
`
`AFFLT0294536
`
`Samsung Ex. 1119 p. 1308
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 227 of 440
`
`Dial-up Networking Profile
`
`2.2 CONFIGURATIONS AND ROLES
`
`The figures below show two typical configurations of devices for this profile:
`
`Cellular phone
`
`Figure 2.2: Dial-up Networking profile, example with cellular phone
`
`Figure 2.3: Dial-up Networking profile, example with modern
`
`The following roles are defined for this profile:
`
`Gateway (GW) — This is the device that provides access to the public network.
`Typical devices acting as gateways are cellular phones and modems.
`
`Data Terminal (DT) — This is the device that uses the dial-up services of the
`gateway. Typical devices acting as data terminals are laptops and desktop
`PCs.
`
`In the rest of this document, these terms are only used to designate these
`roles.
`
`For purposes of mapping the Dial-up Networking profile to the conventional
`modern system architecture. the GW is considered Data Circuit Endpoint
`(DCE), and the DT is considered Data Terminal Endpoint (DTE).
`
`Profile overview
`
`1 December 1999
`
`AFFLT0294537
`
`Samsung Ex. 1119 p. 1309
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Dial-up Networking Profile
`
`page 228 of440
`
`Bluetooth-
`
`2.3 USER REQUIREMENTS AND SCENARIOS
`
`The scenarios covered by this profile are the following:
`
`- Usage of a GW by a DT as a wireless modem for connecting to a dial-up
`internet access server or using other dial-up services
`
`- Usage of a GW by a DT to receive data calls
`
`The following restrictions apply to this profile:
`
`a) The modem is not required to be able to report andfor discriminate
`between different call types for incoming calls.
`
`b) This profile requires support for one-slot packets only. This means
`that this profile ensures that data rates up to 128 kbps can be
`used. Support for higher rates are optional.
`
`0) Only one call at a time is supported.
`
`d) The profile only supports point-to-point configurations.
`
`e) There is no way defined in this profile to discriminate between two
`SCO channels originating from the same device. It is therefore
`manufacturer—specific as to how to deal with the situation where
`there are multiple applications requiring the use of multiple SCO
`channels originating from the same device.
`
`Before a cellphone or modem can be used with a PClLaptop for
`the first time, an initialization procedure must be performed. This
`typically involves manually activating initialization support, and
`entering a PIN code on the PC!Laptop keyboard (see Generic
`Acrcress Profile for more details). This procedure may have to be
`repeated under certain circumstances.
`
`g) This profile does not support multiple instances of its
`implementation in the same device.
`
`Security is ensured by authenticating the other party upon connection estab-
`lishrnent, and by encrypting all user data. The baseband and LMP mechanisms
`for authentication and encryption are used.
`
`1 December 1999
`
`Profile overview
`
`AFFLT029453B
`
`Samsung Ex. 1119 p. 1310
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 229 of 440
`
`Dial-up Networking Profile
`
`2.4 PROFILE FUNDAMENTALS
`
`Before a DT can use the services of a GW for the first time, the two devices
`have to initialize. Initialization includes exchanging a PIN code, creation of link
`keys and service discovery.
`
`A link has to be established before calls can be initiated or received. This
`
`requires paging of the other device. Link establishment is always initiated by
`the DT.
`
`There are no fixed masterislave roles.
`
`The GW and DT provide serial port emulation. For the serial port emulation, the
`serial port profile (see Sr-aria: Fiort Profile) is used. The serial port emulation is
`used to transport the user data, modem control signals and AT commands
`between the GW and the DT. AT-commands are parsed by the GW and
`responses are sent to the DT.
`
`An SCO link is used to transport audio.
`
`For security purposes, authentication is used, and all user data is encrypted.
`For this, the basebandz'LMP mechanisms are used.
`
`2.5 CONFORMANCE
`
`If conformance to this profile is claimed, all capabilities indicated 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
`indica