BLUETOOTH SPECIFICATION Version 1.0 8
`
`Synchronization Profiie
`
`page 404 of 440
`
`Bluetooth-
`
`5 IRMC SYNCHRONIZATION REQUIREMENTS
`
`The |rMC specification 113:1 specifies lrMC Synchronization, which is utilized by
`this profile. The sections of the lrMC specification, with which this profile
`complies. are defined in 'i"a:cle 5.1.
`
`Chapter Name
`
`informative
`Sections
`
`Mandatory
`Sections
`
`Optional
`Sections
`
`Not
`
`Applicable
`Sections
`
`Introduction
`
`All
`
`|rMC Framework
`
`2.1-3, 2.5.1,
`and 2.8-7
`
`Data Transmis-
`sions Services
`
`OBEX Informa-
`tion Access and
`
`Indexing
`
`Synchronization
`
`Device Informa-
`tion
`
`Phone Book
`
`Calendar
`
`Messaging
`
`2.8.1-2,
`2.8.4, and
`2.9 (except
`2.9.2}
`
`3.1
`
`4.1.2,4.2-3,
`4.6, and 4.8
`
`5.2-6(except
`5.5.3), and
`5.8
`
`6.1-2
`
`7.3, 7.5,
`7.7.1, 7.7.3,
`7.7.5, 7.8.1,
`and 7.8.2
`
`8.3.8.5,
`8.8.1, 8.6.3,
`8.8.5, and
`8.7
`
`9.3, 9.5.
`9.8.1, 9.8.3,
`9.8.8, and
`99-10
`
`10.3,10.5,
`10.6.1.
`10.8.3,
`10.8.5, and
`10.7
`
`Tabie 5. ‘i :
`
`irMC Specification Dependencies
`
`1 December 1999
`
`|rMC Synchronization Requirements
`
`AFFLT0294714
`
`Samsung Ex. 1019 p. 1486
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 405 of 440
`
`Synchronization Profits
`
`Informative M3nd3t°"3‘
`Sections
`sections‘
`
`Not
`Applicable
`Sections
`
`Cail Control
`
`Audio
`
`|rMC Applications
`IAS Entry and
`Service Hint Bit
`
`Tabte 5.1:
`
`ir.-WC Specification Dependencies
`
`*. Some of these sections may not be mandatory if the applications do not support all of
`the applications classes
`
`This profile does not mandate that the functionality of |rMC level 1 must be sup-
`ported for the different personal data objects ( vcard, vcal, vmessage and
`vnote), although the |rMC specification requires its support. However, it is
`worth mentioning that the Push command of IrMC requires the Ieve|1 function-
`ality for a text message. Thus, the lrMC client must be able to receive this com-
`mand into its lnbox and the lrMC server must be able to send this command. if
`
`support for the Sync Command feature is claimed. For Bluetooth. the object
`push functionality and requirements are defined in the Object Push profile.
`
`lrMC Synchronization Requirements
`
`1 December 1999
`
`AFFLT029471 5
`
`Samsung Ex. 1019 p. 1487
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 406 of440
`
`Synchronization Profiie
`
`6 OBEX
`
`Bluetooth-
`
`6.1 OBEX OPERATIONS USED
`
`'i'ahie {Ski shows the OBEX operations which are required in the Synchroniza-
`tion profile.
`
`no.
`
`Ability to Send
`
`Ability to Respond
`
`lrMC
`Server‘
`
`|rMC
`C||ent*
`
`Connect
`
`Disconnect
`
`Put
`
`Ge!
`
`Tabie 6.1: OBEX Operations
`
`5*!
`
`refer to the Sync Command feature for which
`The columns marked with
`support in the lrMC Server is optional.
`
`6.2 OBEX HEADERS
`
`'i'ebie 6.2 shows the specified OBEX headers which are required in the
`Synchronization profile.
`
`OBEX Headers
`
`|rMC Client
`
`|riVlC Server
`
`Cou nt
`
`Name
`
`Type
`
`Length
`
`Time
`
`Description
`
`Target
`
`Tabie 6. 2: OBEX Headers
`
`1 December 1999
`
`AFFLT029471 6
`
`Samsung Ex. 1019 p. 1488
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Synchronization Profiie
`
`page 407 of 440
`
`Bluetooth.
`
`Header
`No.
`
`OBEX Headers
`
`irtiilc Client
`
`|rMC Server
`
`XEEEEZEEO
`
`XEZEEEZEO
`
`HTTP
`
`Body
`
`End of Body
`
`Who
`
`Connection [[3
`
`Authenticate Challenge
`
`Authenticate Response
`
`Application Parameters
`
`Object Class
`
`8 9 1
`
`0
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`Tabie 6.2: OBEX Headers
`
`6.3 INITIALIZATION OF OBEX
`
`OBEX authentication must be supported by the devices implementing the Syn-
`chronization profile. The initialization procedure for OBEX is defined in Sectitan
`in GOEP {E}.
`
`6.4 ESTABLISHMENT OF OBEX SESSION
`
`The Target header must be used when the IrMC client establishes the connec-
`tion (See Sectton
`in GOEP {2§). The Target header value is ’lRMC-SYNC’.
`
`6.5 PUSHING DATA
`
`See f:‘:=5,=c;*.ér3:". 5.5 in GOEP
`
`6.6 PULLING DATA
`
`See Section 5.6 in GOEP
`
`6.7 DISCONNECTION
`
`See Eiectic-o 5'33’ in GOEP
`
`1 December 1999
`
`AFFLT029471 7
`
`Samsung Ex. 1019 p. 1489
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 408 of440
`
`Synchronization Profiie
`
`7 SERVICE DISCOVERY
`
`7.1 SD SERVICE RECORDS
`
`There are two separate services related to the Synchronization profile. The first
`is the actual synchronization server (i.e. IrMC server), and the second is the
`sync command server (i.e. lrMC Client).
`
`7.1.1 Synchronization Service
`
`In this case, the service is the IrMC server. The following information (i.e.
`service records) must be put into the SDDEI.
`,
`.
`
`Item
`
`Definition:
`
`Type’!
`Size:
`
`Value?
`
`Service Class ID
`List
`
`Service Class
`#0
`
`PFOIOCCH DQSCFIDIDF
`list
`
`Protocol ID #0
`
`Protocol ID #1
`
`| Param #0
`l Protocol ID #2
`Service name
`
`CHANNEL
`
`'
`
`Displayable
`Text name
`
`|rMCSync
`
`LZCAP
`
`RFCOMM
`
`Varies
`OBEX
`Varies
`
`Blue-toolhProfiIeDe— Supported
`scriptorList
`profiles and
`versions
`
`Profile #0
`
`UUID
`
`|rMCSync
`
`Version #0
`
`Uint16
`
`Varies
`
`Supported Data
`Stores List
`
`Data Ele-
`merit
`Sequence
`of U|nt8
`
`Data stores
`may be
`phonebook.
`calendar,
`notes, and
`messages.
`
`Data stores:
`0x01 =
`Phonebook
`0x03 = Cal-
`endar
`0105 =
`Notes
`0106 = Mes-
`sages
`
`Tabie ?.‘i: Synchronization Service Record
`
`*. Values that are of the type UUID are defined in the Assigned Numbers specification [15].
`
`‘I December 1999
`
`Servicetlisoovery
`
`AFFLT029471 8
`
`Samsung Ex. 1019 p. 1490
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 409 of 440
`
`Synchronization Profiie
`
`7.1.2 Sync Command Service
`
`The Sync Command service is used for initiating the synchronization from the
`lrMC server device. The following service records must be put into the SDDB
`by the application which provides this service.
`
`Service Class ED List
`
`Service Class #0
`
`Protocol Descriptor list
`
`Protocol ID #0
`
`Protocol ID #1
`
`| Param #0
`1 Protocol ID #2
`Service name
`
`Definition:
`
`CHANNEL
`
`'
`
`Displayable
`Text name
`
`Eiluatooth Profile De-
`scr1'ptorList
`
`Supported
`profiles and
`versions
`
`Profile #0
`
`Version #0
`
`|rMCSync-
`Command
`
`LZCAP
`
`RFCOMM
`
`Varies
`OBEX
`Varies
`
`IrMCSync
`
`Varies
`
`Table 7.2: Sync Command Sen/roe Record
`*. Values that are of the type UUID are defined in the Assigned Numbers specification
`[1
`
`Service Discovery
`
`1 December 1999
`
`AFFLT029471 9
`
`Samsung Ex. 1019 p. 1491
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Synchronization Profiie
`
`7.2 SDP PROTOCOL DATA UNITS
`
`page 410 of440
`
`Bluetooth-
`
`Tehie ?’.E‘: shows the specified SDP PDUS (Protocol Data Units) which are
`required in the Synchronization profile.
`
`Ability to Send
`
`Ability to Retrieve
`
`|rMC
`Client
`
`lrMC
`Sewer
`
`PDU
`I10.
`
`SDP PDU
`
`SdpErrorResponse
`
`SdpServiceSearchAttribute-
`Request
`
`Sdpse rvicesea rch Attribute-
`Response
`
`Tebie 7.3: SDP PDUS
`
`The PDUS marked with ‘*' refer to the Sync Command feature, of which the
`support in the lrMC Server is optional.
`
`1 December 1999
`
`Servicetlisoovery
`
`AFFLT0294720
`
`Samsung Ex. 1019 p. 1492
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Synchronization Profiie
`
`8 REFERENCES
`
`8.1
`
`NORMATIVE REFERENCES
`
`page 411 of 440
`
`Bluetooth
`
`[1 ]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[5]
`
`[7]
`
`[3]
`
`[9]
`
`Bluetooth Special Interest Group, |rDA Interoperability.
`
`Bluetooth Special Interest Group, Generic Object Exchange Profile.
`
`Bluetooth Special Interest Group, File Transfer Profile.
`
`Bluetooth Special interest Group, Object Push Profile.
`
`Bluetooth Special Interest Group, Baseband Specification.
`
`Bluetooth Special Interest Group, LMP Specification.
`
`Bluetooth Special Interest Group, L2CAP Specification.
`
`Bluetooth Special Interest Group, RFCOMM with TS 07.10.
`
`ETSI, TS 07.10, Version 6.3.0.
`
`[1 0]
`
`Biuetooth Special interest Group, SDP Specification.
`
`[1 1 ]
`
`[12]
`
`[13]
`
`[14]
`
`Infrared Data Association, lrDA Object Exchange Protocol (IIOBEX) with
`Published Errata, Version 1.2, April 1999.
`
`Infrared Data Association, lrMC (Ir Mobile Communications) Specification
`with Published Errata, Version 1.1, February 1999.
`
`The Internet Mail Consortium, vCard — The Electronic Business Card
`
`Exchange Format, Version 2.1, September 1996.
`
`The Internet Mail Consortium, vCa|endar — The Electronic Calendaring
`and Scheduling Exchange Format, Version 1.0, September 1998.
`
`[15]
`
`Bluetooth Special Interest Group, Bluetooth Assigned Numbers.
`
`[15]
`
`Biuetooth Special Interest Group, Bluetooth Generic Access Profile
`Specification.
`
`References
`
`1 December 1999
`
`AFFLT0294721
`
`Samsung Ex. 1019 p. 1493
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 4120f-440
`
`Synchronization Profife
`
`1 December 1999
`
`References
`
`AFFLT0294722
`
`Samsung Ex. 1019 p. 1494
`
`

`
`REVISION HISTORY
`
`AFFLT0294723
`
`Samsung Ex. 1019 p. 1495
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 414 of 440
`
`Revision History
`
`1 December 1999
`
`AFFLT0294724
`
`Samsung Ex. 1019 p. 1496
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 415 of 440
`
`Revision History
`
`REVISION HISTORY
`
`Part K:1
`
`Generic Access Profile
`
`Rev Date
`1.0
`June
`
`‘Comments
`Released for final review.
`
`Release for sign-off.
`Updated based on received comments.
`Final updated version.
`1.0 Draft
`
`Revised from a iinguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`20"?
`1999
`
`Dec
`151
`1999
`
`Part K:2
`
`Service Discovery Application Profile
`Rev l Date
`i Comments
`1.0
`June
`- Aligned with GAP whenever necessary.
`20"‘
`- Emphasized that SDAP can be used as the basis for the service
`1999
`discovery portion of other profiles.
`Added section 5.1 with SDP PDU exchange examples.
`Emphasized that normal operation requires a LocDev to initiate and
`terminate LZCAP connections for SDP.
`1.0 Draft
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These oorrections and clarifications are marked with oorrection bars.
`
`1 December 1999
`
`AFFLT0294725
`
`Samsung Ex. 1019 p. 1497
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 416 of 440
`
`Revision History
`
`Part K:3
`
`Cordless Telephony Profile
`
`Comments
`
`-
`
`Ftf preversion. some editorial updates and minor content changes -
`number of TLS 8 -> 7. Master-Slave Switch made conditional,
`restrictions in digits for Ca||ed&Ca||ing party |Es. updates to CoD and
`SDP sections.
`
`Updates after ftf. Added feature "Register recall". removed feature
`"service call" and redefined "lvlulti-terminal support" to reflect decisions
`on WUG status. Added description of Register recall to section 4.3.
`Removed emergency. service and ad-hoc call classes. Added descrip-
`tion of piconet handling to 4.1.2. Updated and reworked SDP record.
`Additions to contributor list. Figure in section 8.2 removed. "Status"
`chapter removed. Added remark on security with respect to LZCAP
`connectionless. Editorial updates to section 4.4.
`Updates to incorporate GAP and editorial guidelines for the
`specification
`Errors in tables 3 and 4 and section 4.2.
`1.0 Drafl
`
`Dec
`181
`1999
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been Included.
`These corrections and clarifications are marked with oorrection bars.
`
`Part K:4
`
`Intercom Profile
`
`Comments
`
`Update after F2F. incorporating technical issues only.
`Editorial improvements.
`Replaced bonding with authentication in Section 2.4.
`Corrected references to LMP.
`
`Removed PSM field from service record. and rephrased opening
`statement of SDP section.
`
`Added chapter on GAP interoperability requirements.
`Final GAP alignment.
`Mandated call confirmation as SETUP confirmation.
`1.0 Draft
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been Included.
`These corrections and clarifications are marked with correction bars.
`
`1 December 1999
`
`AFFLT0294726
`
`Samsung Ex. 1019 p. 1498
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 417 of 440
`
`Revision History
`
`Part K:5
`
`Serial Port Profile
`
`Comments
`
`Bluetooth.
`
`Added more details on application layer procedures (chapter 3). First
`alignment with Generic Access Profile.
`Added requirements on SDP procedures. More alignment with GAP.
`Corrected some typos. Removed section 5.3.3 (Link Power Mode in
`LZCAP}. Removed "Management entity" throughout document.
`1.0 Draft
`
`Dec
`151
`1999
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`Part K:6
`
`Headset Profile
`
`Rev Date
`
`Comments
`
`1.0
`
`June
`20th
`1999
`
`- Update after F2F. incorporating outstanding issues as discussed
`(volume control and synchronisation, added AT command +VGS and
`+\/GM, extended audio connection transfer description. authentication!
`encryption optional to use. status change of outgoing audio connection,
`service record updated) and various editorial issues (amongst others
`update of contributors list). Removed status and history section.
`Remote audio volume control: replaced may's with shells to make it
`more consistent (if Remote audio volume control is supported. the entire
`procedure shall be supported as specified}.
`SDP - removed PSM for RFCOMM. added misplaced server channel.
`1.0 Draft
`
`1.0B
`
`Dec
`151
`1999
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`Part K17
`
`Dial-up Networking Profile
`
`Rev Date
`
`Comments
`
`1.0
`
`June
`
`20”‘
`1999
`
`- Some SDP values filled in, CoD updated after assigned numbers doc.
`
`- Updates after Tampere ftf: SDP record updated and reworked.
`Removed table from chapter 5.1 (now in RFCOMM). Updated
`contributors list. Figure removed from section 5.5.1.
`Added profile structure section. Alignment with GAP (section 6) added.
`1.0 Draft
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`1 December 1999
`
`AFFLT0294727
`
`Samsung Ex. 1019 p. 1499
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Revision History
`
`Part K:8
`
`Fax Profile
`
`Comments
`
`page 418 of 440
`
`Bluetooth.
`
`Replaced bonding with authentication in Section 2.4.
`Corrected references to LM P.
`
`removed PSM field from service record, and rephrased opening
`statement of SDP section.
`
`Added chapter on GAP interoperability requirements.
`Updated Figure 1. Service discovery Profile to Service Discovery
`Application Profile.
`Removed "ME" block from both sides of figure 2.
`Removed paragraph discussing "ME" in section 2.1.
`Renamed Section Heading 4 From Dialling and Control to Dialling and
`Control Interoperability requirements.
`Re-worded section 4.1.2.
`Removed the words "the" and "section" from the last sentence in section
`5.3, paragraph 2.
`Removed section 5.6.
`
`Aligned section 6 with new changes from Dialup networking profile.
`1.0 Draft
`
`Dec
`1st
`1999
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`Part K:9
`
`LAN Access Profile
`
`Rev Date
`
`Comments
`
`1.0
`
`June
`2091
`1999
`
`Updated Service records in line with "best practice".
`Removed Security section.
`Editorial changes in Section 4.1.
`Editorial changes in Section 5.1.
`Editorial changes in Section 11.2.
`1.0 Draft
`
`Revised from a linguistic point of view.
`
`1 December 1999
`
`AFFLT0294728
`
`Samsung Ex. 1019 p. 1500
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 419 of 440
`
`Revision History
`
`Part K:10
`
`Generic Object Exchange Profile
`
`Rev Date
`
`Comments
`
`- Updated Chapter 1.2 and added reference to GAP regarding link and
`channel establishment.
`
`Removed the security statement from the Profile fundamentals chapter.
`clarified the use of the limited discoverable mode in the Inquiry and
`Inquiry Scan chapter, and added the GAP requirement chapter.
`Changed the 'initialization' wording to ‘bonding’. added some
`cross~references. and included the errata for |rOBEX in the reference
`list.
`
`Management entity removed and the fall back procedure added if the
`Limited Inquiry procedure is supported.
`Clarified that the fall back to the General inquiry is mandatory if Limited
`Inquiry is used.
`Editorial changes and Chapter 7.3.1 (Bonding) updated to describe the
`result of Bonding.
`1.0 Draft
`
`Revised from a linguistic point of view.
`
`1.0
`
`June
`20th
`
`1999
`
`1 .0B
`
`Dec
`1st
`1999
`
`Part K:11
`
`Object Push Profile
`
`Rev Date
`
`Comments
`
`1.0
`
`June
`20th
`1999
`
`- Removed PSM from SDP record. Updated text in Profile Structure 1.2.
`GAP alignment in Profile Fundamentals.
`Editorial.
`
`Renamed Initialization to Bonding.
`Removed the ME section and references to ME. Stated in profile funda-
`mentals that bonding is mandatory to support and optional to use.
`Removed "Notation for timers and counters". Changed wording in appli-
`cation procedure for object push feature. Minor update of SDP record.
`Changed recommended inquiry procedure in chapter 3 to reference to
`the GOEP.
`1.0 Draft
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These oorrections and clarifications are marked with correction bars.
`
`1 December 1999
`
`AFFLT0294729
`
`Samsung Ex. 1019 p. 1501
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 420 of 440
`
`Revision History
`
`Part K:12
`
`File Transfer Profile
`
`Comments
`
`SDP table changes. addition of references to doc [16}.
`More SDP table changes, alignment with GAP. contributors update, and
`copyright notice.
`Editorial and reference corrections.
`1.0 Drafi
`
`Revised from a linguistic point of view.
`
`Dec
`1st
`1 999
`
`Part K:13
`
`Synchronization Profile
`
`Rev Date
`
`Comments
`
`1.0
`
`June
`
`299"
`1999
`
`- Updated service records. lrMC chapter updated.
`
`- Chapter 1.2 updated, profile fundamentals clarified. recommended
`inquiry procedure added into Chapter 3 and service records updated.
`Security issues clarified in Profile Fundamentals chapter and some
`editorial changes.
`Change the ‘Initialization’ wording to ‘Bonding’. updated
`cross-references. and editorial changes.
`Remove Management entity, removed statement that lrMC client must
`initiate the link establishment when bonding is not performed, and
`added a reference to the inquiry procedures of GOEP.
`Editorial changes.
`1.0 Drafl
`
`Revised from a linguistic point of view.
`Errata items previously published on the web has been included.
`These corrections and clarifications are marked with correction bars.
`
`1 December 1999
`
`AFFLT0294730
`
`Samsung Ex. 1019 p. 1502
`
`

`
`CONTRIBUTORS
`
`AFFLT0294731
`
`Samsung Ex. 1019 p. 1503
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 422 of 440
`
`Contributors
`
`0
`
`1 December 1999
`
`AFFLT0294732
`
`Samsung Ex. 1019 p. 1504
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 423 of 440
`
`Contributors
`
`CONTRIBUTORS
`
`Part K:1
`
`Generic Access Profile
`
`Patric Lind (editor)
`
`3 Ericsson Mobile Communications AB
`
`Ericsson Mobiie Communications AB
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Motorola
`
`IBM
`
`Elg. Johannes
`
`Johan Sorensen
`
`Erik Slottboom
`
`Thomas Muller
`
`Stephane Bouet
`
`Martin Rater
`
`Brian Redding
`
`Chatschik Bisdikian
`
`Ken Morley
`
`Jon Inouye
`
`Part K:2
`
`Service Discovery Application Profile
`
`Elg. Johannes
`
`Ericsson Mobile Communications AB
`
`Bisdikian, Chatschik (editor)
`
`Miller. Brent
`
`Mulier, Thomas
`
`Pascoe, Robert A.
`
`IBM Corporation
`
`IBM Corporation
`
`Nokia
`
`XtraWorX
`
`1 December 1999
`
`AFFLT0294733
`
`Samsung Ex. 1019 p. 1505
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 424 of 440
`
`Contributors
`
`Part K:3
`
`0 h-
`
`Cordless Telephony Profile
`
`Olof Dellien (editor)
`
`Erik Slotboom
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`Gert-jan van Lieshout
`
`Ericsson Mobile Communications AB
`
`Martin Roter
`
`Christian Zechlin
`
`Ken Morley
`
`Richard Shaw
`
`Brian Redding
`
`Alex Feinman
`
`Sridhar Rajagopal
`
`Ramu Ramakesavan
`
`Jun'lchi Yoshizawa
`
`Part K:4
`
`Intercom Profile
`
`Erik Slotboom (editor)
`
`Olof Dellien
`
`Gert-jan van Lieshout
`
`Richard Shaw
`
`Ken Morley
`
`Shridar Rajagopal
`
`Ramu Ramakeshavan
`
`Brian Redding
`
`Thomas Miiller
`
`Christian Zechlin
`
`Jun‘ichi Yoshizawa
`
`Part K:5
`
`Serial Port Profile
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`BCOM
`
`3COM
`
`Motorola
`
`Motorola
`
`Intel Corporation
`
`Intel Corporation
`
`Toshiba
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`3COM
`
`3COM
`
`Intel Corporation
`
`Intel Corporation
`
`Motorola
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Toshiba
`
`Johan Sorensen (editor)
`
`Ericsson Mobile Communications AB
`
`Oiof Dellien
`
`Riku Mettéiléi
`
`Ericsson Mobile Communications AB
`
`Nokia Mobiie Phones
`
`‘I December 1999
`
`AFFLT0294734
`
`Samsung Ex. 1019 p. 1506
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 425 of 440
`
`Contributors
`
`Part K:6
`
`Headset Profile
`
`Richard Shaw
`3Com
`
`Ken Morley
`
`3Com
`
`Erik Slotboom (editor)
`
`Ericsson Mobile Communications AB
`
`Olof Dellien
`
`Bailey Cross
`
`Shridar Rajagopal
`
`Brian Redding
`
`Alex Feinman
`
`Thomas Miiller
`
`Christian Zeohlin
`
`Martin Roter
`
`Ericsson Mobile Communications AB
`
`Intel Corporation
`
`Intel Corporation
`
`Motorola
`
`Motorola
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Jun‘iohi Yoshizawa
`
`Toshiba
`
`Part K:7
`
`Dia|—up Networking Profile
`
`Olof Dellien (editor)
`
`Erik Slotboom
`
`Riku Mettala
`
`Martin Rotor
`
`Christian Zechlin
`
`Ken Morley
`
`Richard Shaw
`
`Brian Redding
`
`Alex Feinman
`
`Sridhar Rajagopal
`
`Jun'ichi Yoshizawa
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`SCOM
`
`3COM
`
`Motorola
`
`Motorola
`
`Intel Corporation
`
`Toshiba
`
`1 December 1999
`
`AFFLT0294735
`
`Samsung Ex. 1019 p. 1507
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 426 of 440
`
`Bluetooth-
`
`BCOM
`
`BCOM
`
`Ericsson Mobile Communications ABn
`
`Ericsson Mobile Communications AB
`
`Ericsson Mobile Communications AB
`
`Contributors
`
`Part K:8
`
`Fax Profile
`
`Richard Shaw (editor)
`
`Ken Morley
`
`Oiof Dellien
`
`Erik Slotboom
`
`Gert-jan van Lieshout
`Riku Mettala
`
`Christian Zechlin
`
`Thomas Muller
`
`Martin Roter
`
`Sridhar Rajagopal
`
`Ramu Ramakeshavan
`
`Brian Redding
`
`Alex Feinman
`
`Jun’ichi Yoshizawa
`
`Part K:9
`
`LAN Access Profile
`
`Jon Burgess
`
`Paul J Moran (editor)
`
`Phil Crooks
`
`Johan Sorensen
`
`Chatschik Bisdikian
`
`Marcia Peters
`
`Pravin Bhagwat
`
`Kris Fleming
`
`Michael Camp
`
`Shaun Astarabadi
`
`Yosuke Tajlka
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Intel Corporation
`
`Intel Corporatio
`
`Motorola
`
`Motorola
`
`Toshiba
`
`SCOM
`
`3COM
`
`SCOM
`
`Ericsson Mobile Communications AB
`
`IBM Corporation
`
`IBM Corporation
`
`JBM Corporation
`
`Intel Corporation
`
`Nokia Mobile Phone
`
`Toshiba Corporation
`
`Toshiba Corporation
`
`1 December 1999
`
`AFFLT0294736
`
`Samsung Ex. 1019 p. 1508
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Contributors
`
`page 427 of 440
`
`Bluetooth.
`
`Part K:10
`Generic Object Exchange Profilee
`David Kammer
`SCOM
`
`Patrik Olsson
`
`Davld Suvak
`
`Apratim Purakayastha
`
`Aron Walker
`
`Jon Inouye
`
`Stephane Bouet
`
`Riku Mettala (editor)
`
`James Scales
`
`Sieve Rybicki
`
`Shaun Astarabadi
`
`Katsuhiro Kinoshita
`
`Part K:11
`
`Object Push Profile
`David Kammer
`
`Patrik Olsson (editor)
`
`David Suvak
`
`Apratim Purakayastha
`
`Aron Walker
`
`Jon Inouye
`
`Stephane Bouet
`
`Riku Metlalé
`
`James Scales
`
`Steve Rybicki
`
`Shaun Astarabadi
`
`Katsuhiro Kinoshita
`
`Ericsson Mobile Communications AB
`
`Extended Systems
`
`IBM Corporation
`
`IBM Corporation
`
`Intel Corporation
`
`Nokia Mobile Phones
`
`Nokia Mobile Phone
`
`Nokia Mobile Phone
`
`Puma Technology
`
`Toshiba Corporation
`
`Toshiba Corporation
`
`3Com
`
`Ericsson Mobile Communications AB
`
`Counterpoint Systems Foundry
`
`IBM Corporation
`
`IBM Corporation
`
`Intel Corporation
`
`Nokia Mobile Phones
`
`Nokia Mobile Phone
`
`Nokia Mobile Phones
`
`Puma Technology
`
`Toshiba Corporation
`
`Toshiba Corporation
`
`1 December 1999
`
`AFFLT0294737
`
`Samsung Ex. 1019 p. 1509
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 428 of 440
`
`Contributors
`
`Part K:12
`
`File Transfer Profile
`
`Shaun Astarabadi (editor)
`
`Toshiba Corporation
`
`0 h-
`
`David Suvak
`
`Patrik Olsson
`
`Apratim Purakayastha
`
`Aron Walker
`
`Jon lnouye
`
`Stephane Bouet
`
`Riku Mettala
`
`James Scales
`
`Steve Rybicki
`
`Katsuhiro Kinoshita
`
`Extended Systems
`
`Ericsson Mobile Communications AB
`
`IBM Corporation
`
`SBM Corporation
`
`Intel Corporation
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Nokia Mobile Phones
`
`Puma Technology
`
`Toshiba Corporation
`
`Part K:13
`
`Synchronization Profile
`David Kammer
`
`BCOM
`
`Patrik Olsson
`
`David Suval:
`
`Brent Miller
`
`Apratim Purakayastha
`
`Aron Walker
`
`Jon lnouye
`
`Stephane Bouet
`
`Riku Mettala (editor)
`
`James Scales
`
`Steve Rvbicki
`
`Shaun Astarabadi
`
`Katsuhiro Kinoshita
`
`Ericsson Mobile Communication AB
`
`Extended Systems
`
`IBM Corporation
`
`IBM Corporation
`
`IBM Corporatio
`
`Intel Corporation
`
`Nokia Mobile Phones
`
`Nokia Mobile Phone
`
`Nokia Mobile Phone
`
`Puma Technology
`
`Toshiba Corporation
`
`Toshiba Corporation
`
`The Bluetooth Specification was compiled and edited by Dan Sijnnerstam,
`Pa t‘Ei£?‘i§C§ Eiosninurtioatictn AB.
`
`1 December 1999
`
`AFFLT0294738
`
`Samsung Ex. 1019 p. 1510
`
`

`
`ACRONYMS
`
`BBREVIATIONS
`
`AFFLT0294739
`
`Samsung Ex. 1019 p. 1511
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 430 of 440
`
`Acronyms and Abbreviations
`
`1 December 1999
`
`AFFLT0294740
`
`Samsung Ex. 1019 p. 1512
`
`

`
`AFFLT0294741
`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 431 of 440
`
`Acronyms and Abbreviations
`
`LIST OF ACRONYMS AND ABBREVIATIONS
`
`Abbreviation or Acronym Meaning
`
`Asynchronous Connectionless
`
`Audio Gateway
`Access Point
`
`Baseband
`
`AG
`AP
`
`§ B
`
`B
`
`BD_ADDR
`
`Bluetooth Device Address
`
`Call Control
`
`Ccnnectionless
`
`Connection-oriented
`
`Class Of Device
`
`Cordless Telephony Profile
`
`Device Access Code
`
`Dedicated inquiry Access Code
`Data Terminal
`
`Data Terminal
`
`Frequency Hopping Synchronization
`
`Generic Access Profile
`
`General Inquiry Access Code
`
`Group Management
`
`Generic Object Exchange Profile
`
`Gateway
`
`Host Controller Interface
`
`Headset
`
`1 December 1999
`
`2 C
`
`C
`
`CL
`
`CO
`
`Samsung Ex. 1019 p. 1513
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 432 of 440
`
`Acronyms and Abbreviations
`
`Internet Protocol
`
`Internet Protocol exchange
`
`Infrared Data Association
`
`Ir Mobile Communications
`
`Logical Link Control And Adaptation
`
`Logical Link Control And Adaptation Protocol
`
`Local Area Network
`
`LAN Access Point
`
`Link Controller
`
`Limited Inquiry Access Code
`
`Link Manager
`
`Link Manager Protocol
`
`Local Device
`
`Management Entity
`
`Mobility Management
`
`Message Sequence Chart
`
`Maximum Transmission Unit
`
`Object Exchange Protocol
`
`Personal Computer
`
`Personal Digital Assistant
`
`Protocol Data Unit
`
`Personal information Management
`
`Point-to-Point Protocol
`
`Public Switched Telephone Network
`
`Quality Of Service
`
`1 December 1999
`
`AFFLT0294742
`
`Samsung Ex. 1019 p. 1514
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Acronyms and Abbreviations
`
`page 433 of 440
`
`Bluetooth.
`
`Remote Device
`
`Serial Cable Emulation Protocol
`
`Service Discovery
`
`Service Discovery Database
`
`Service Discovery Protocol
`
`Serial Port
`
`Special Interest Group
`
`3 R
`
`emDev
`
`RFCOMM
`
`§ S
`
`D
`
`SIG
`
`SrvDscApp
`
`Service Discovery Application
`
`I
`
`Transport Control Protocol
`
`Telephony Control Specification
`
`Terminal
`
`Terminal Originating A Call
`
`Terminal Terminating A Call
`
`User Datagram Protocol
`
`User Interface
`
`Unlimited Inquiry Access Code
`
`Universally Unique Identifier
`
`Wireless User Group
`
`1 December 1999
`
`AFFLT0294743
`
`Samsung Ex. 1019 p. 1515
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 434 of 440
`
`Acronyms and Abbreviations
`
`1 December 1999
`
`AFFLT0294744
`
`Samsung Ex. 1019 p. 1516
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Biuetooth Host Controiier interface Functionai Specification
`
`page 435
`
`Bluetooth.
`
`INDEX
`-.\‘€~.‘-.‘¢~}\‘<.'\N‘v>-3\‘<7~.\‘s\\‘<7~.‘s'vN\‘v>\\'\3~.\"s\\'\\\'§\\'\#\\\}\‘s\¥.‘-t|#\\'k\‘s\\‘s'\3\\’\\‘s\}\‘s'\}s'vN\‘v7\\‘<>\\‘<7\\V?!‘\\}¢3\V¢\VQ\V§\\‘N¢\V¢.‘h\\*\‘¢\VQ\V¢\V~\V¢¢¢§\‘¢A\\\\‘¢A\‘¢§\\“¢\V€\\V\V§A\‘N¢D\\\3\WA\*\\\\\\\V¢\\\\VD¢¢3\‘¢\\\‘¢A\‘¢3\‘¢3¢
`
`Connectable device 53
`Connectable mode 31
`Connection establishment 5%
`connection establishment 5:»
`
`Connection ID PS5, 3T6
`Connection Management -3 0&1
`Content Formats 3-rt-1
`content formats 3:34
`
`Cordless Telephony profile ice
`
`D D
`
`ata Access Points fiat)
`Data calls 23{.‘:
`data link connection 1'35;
`Data Terminal 22:’. 25.35. 2172
`DCE 17::
`
`Default Get Object 34;;
`Device discovery 54
`Dial-up Networking 2.2.‘;
`Direct Cable Connection 29:2
`Discoverabie device 5313
`discoverable mode 25%
`DT 453‘:
`DTE 1?‘?
`
`DTMF signalling 105
`
`‘E135. "355
`
`E e
`
`ncryption 1}’:—'_.,
`
`F F
`
`ax profile ma
`Fax service 35::
`
`File Browsing UUID 235
`File Transfer 35'-‘vi
`File Transfer mode 36.?
`
`File Transfer profile 36!}
`flow control 1'38
`flush timeout 186}
`
`G G
`
`ateway ‘l C-4. 222?. $351}
`General Discoverable its?’
`
`general discoverable mod 31
`general inquir 3:’
`General Inquiry procedure 185
`General Sync mode .’3:“.+%
`Generic Object Exchange profile 3::-E-, 369. :-39:?
`
`1 December 1999
`
`435
`
`AFFLT0294745
`
`Numerics
`3-in-1 phone ‘:03
`
`A a
`
`daptation layer “J8
`Assigned Numbers 383
`AT command set 3331. 254
`Audio connection transfer
`
`Audio Gateway ‘HE?’
`Authentication 54
`authentication 33. H3. ‘.?5
`
`Automatic Synchronization -:05?
`
`B B
`
`luetcoth Bonding 42
`Bluetooth channel establishment 48
`Bluetooth connection establishmen 5-it
`Bluetccth Device Address :35
`Bluetooth Device Class 2?
`
`Bluetooth Device Discovery 41
`Bluetooth Device Inquiry 3?. 39
`Bluetooth Device Name 26
`
`Bluetooih Device Name Discovery
`Bluetooth Device Type 2:‘?
`Bluetccth link establishment-E5
`
`Bluetooth Passkey 2i-3
`Bluetooth Service Type 2?‘
`bondable mode 3:!
`
`-1» ‘rs
`
`Bonding 5.5.
`bonding 42
`browsing firs’.
`Business Card Exchange 346
`Business Card Exchange function 34:}
`Business Card Pull if-etfi
`Business Card Pull function 340
`
`CC
`
`alendar 34::
`
`Calendar application M33
`Call information 105. 14?
`
`Calling line identification presentation 1«:_'=r3
`Channel establishment 53::
`channel establishment 48
`Class of Device -1855
`Client 310
`CLIP ‘.-Gt}
`
`Samsung Ex. 1019 p. 1517
`
`

`
`AFFLT0294746
`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Bluetooth Host Controller interface Functional Specification
`
`page436
`
`Bluetooth.
`
`name discovery 4%
`non-bendable mode 32
`non-oonnectable mode 3‘.
`non-discoverable mode 29
`
`non-pairable mode {:12
`Notes 345
`
`Notes application .293
`
`0O
`
`BEX Iii,‘-5
`
`OB EX authentication 3153. 36.35, §?*.‘. -=
`OBEX Connect 3'26
`OBEX connection .'3I’—"3
`OBEX Headers .”.=4.F3
`OBEX headers 11453. taxis
`
`“
`
`OBEX operation 3”»-S
`OBEX Operations I-.'«*iE-3
`OBEX operations iieiti
`Object Exchange mode 34%)
`Object Push 3.‘3«s. 34-‘.
`Object Push function 343
`On hook ‘:61’, M?
`Outgoing audio oonnection 20};
`Outgoing external call 10?‘
`owner’s business card 34:3
`
`P p
`
`aging I85
`pairable mode 32
`Phone Book 34::
`
`Phone Book application 4:33
`PM 392
`
`Post-dialling ‘EL’?
`PPP 25.59, 28‘.
`Push C“ei'it3$‘3
`Push Server .'-339
`
`PUT-operation 321
`
`0 Q
`
`uality of Service 13:2:
`
`R R
`
`egister recall :0?
`Remote audio volume control :-IGF-
`Remote Line Status indication command 2'75
`
`Remote Port Negotiation Command ire
`RFCOMM Server channel ‘I ‘M
`RFCOMM session ii’-at
`
`RS232 control signalling 1:12
`RS232 control signals ‘-.'.-"8
`
`‘I December 1999
`
`GET—operation
`GOEP 23-551.392-'1
`GW 'i[Erl
`
`H H
`
`eadset ‘.9’:
`Headset Control sea
`
`I I
`
`ncoming audio connection 2-.‘.=€
`Incoming external call we
`initialisation ins
`
`Initialization Sync mode 3:-as
`inquiry 1.59.3
`inquiry scan 1'35
`Intercom ‘-.4.’-3
`
`Intercom call 10?‘, '54?
`Internet Bridge 223
`IP 268%
`IPX 265:1
`lrMC Client 35>?
`IrMC Server 353-?
`
`IrMC specification 404
`IRl'vIC_SYNC zit}?
`
`LL
`
`AN Access 259
`LAN Access Point 2'i’i
`
`atency ‘:8?
`egacy applications 1?-5. 175
`Limited Discoverable 38?‘
`Limited discoverable mode 182:‘-
`imited discoverable mode :36
`
`imited inquiry
`Link 52
`Link establishments:
`ink establishment 45
`ink level authentication 3:335
`
`ow power mode ‘l}’5
`
`MM
`
`E 432
`
`Messaging 344
`Messaging application 403
`Modem Status Command ‘E78
`MTU sizes $9.8
`
`Muiti-terminal support ‘iii?’
`
`N N
`
`ame discovery :34
`
`Samsung Ex. 1019 p. 1518
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Bluetooth Host Controller interface Functional Specification
`
`page437
`
`uetooth.
`
`S S
`
`DP database 1?‘?-
`
`security features i ?‘3
`security mode 3-I-at
`serial port -2'?-1»
`Server 319-
`Service Class ID fr»:-,
`service record 181
`
`Sync Command 4:‘;-2
`Synchronization 39-;
`Synchronization profile (+92
`
`T T
`
`arget header 3:’.'3
`Terminal ‘=:;--4
`TL 134
`
`U
`
`Vv
`
`irtual serial cable 1‘.-‘F3
`
`virtual serial port 1:':':
`
`W w
`
`all<ie~ta|l<ie ‘I43
`Wide Area Networks 2-15
`
`1 December 1999
`
`AFFLT0294747
`
`Samsung Ex. 1019 p. 1519
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 438 of 440
`
`Bluetooth.
`
`1 December 1999
`
`AFFLT0294'/48
`
`Samsung Ex. 1019 p. 1520
`
`

`
`
`
`
`
`AFFLT0294749
`
`Samsung Ex. 1019 p. 1521
`
`

`
`Samsung Ex. 1019 p. 1522