BLUETOOTH SPECIFICATION Version 1.0 B
`
`Dial-up Networking Profile
`
`5.3 IDLE MODE PROCEDURES
`
`page 239 of 440
`
`Bluetooth
`
`The table shows the support status for Idle mode procedures within this profile
`
`Support in GW
`
`M (Note 1)
`
`General inquiry
`
`Limited inquiry
`
`Name discovery
`
`Device discovery
`
`Bonding
`Note 1: See section 6.3.1
`
`Table 6.3:
`
`idie mode procedures
`
`6.3.1 Bonding
`
`it is mandatory for the DT to support initiation of bonding, and for the GW to
`accept bonding.
`
`Generic Access Profile Interoperability Requirements 1 December 1999
`
`AFFLT0294549
`
`Samsung Ex. 1019 p. 1321
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 240 of440
`
`Dial-up Networking Profile
`
`7 REFERENCES
`
`[1] Bluetooth Baseband specificationt
`
`[2] Bluetooth Link Manager Protocol
`
`[3] Bluetooth Logical Link Control and Adaptation Protocol Specification
`
`[4]
`
`RFCOMM with TS 07.10
`
`[5] TS 101 369 (GSM 07.10) version 6.1.0
`
`[6]
`
`International Telecommunication Union. "lTU-T Recommendation V.250"
`
`[Y] Bluetooth Service Discovery Protocol
`
`[8]
`
`John Webb. "Bluetooth SIG MRD", version 1.0 Draft
`
`[9] Bluetooth Serial Port Profile
`
`[10] ETS 300 916 (GSM 07.07) version 5.6.0
`
`[11] Bluetooth Fax Profile
`
`[12] Bluetooth Assigned Numbers
`
`1 December 1999
`
`References
`
`AFFLT0294550
`
`Samsung Ex. 1019 p. 1322
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Dial-up Networking Profile
`
`8 LIST OF FIGURES
`
`page 241 of 440
`
`Bluetooth.
`
`érigure ‘iii:
`Siégure 2.1:
`
`Biueteoth Pmfiies ................................................................... .223
`
`§1’rc»toc:eE medei ...........................
`
`.........................................
`
`:"—‘s'gu:'e 2.2:
`
`Diai--up Nei\r¢orki.r:g; profiie. exanzpie with ceiiaziar pfzrsne ........ .22?‘
`
`iliguye 2.3:
`
`D§aE—u_:3 Nerworkiw profiie. e><a=.m.p§e with madam .................. .22?’
`
`List of Figures
`
`1 December 1999
`
`AFFLT0294551
`
`Samsung Ex. 1019 p. 1323
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 242 0f4-40
`
`Dial-up Networking Profile
`
`9 LIST OF TABLES
`
`Tame 1.1:
`Tabie.-3
`Tabte 4.1:
`
`Tabie 4.2:
`Tabie 5.1:
`
`Arrows user} in signaiiing diagrz-z:1*::«: .......................................
`Appiication éayer _;2rc2ceadures3 ................................................. ..
`Re-qu§rer_i .=;:3.mn'7anr_is .............................................................. ..
`
`Requireci resuit codes ............................................................ ..
`ESs3r\:E(:§.-t Saiabase Entries
`
`Tahis: 5.2:
`Tani:-: 6.1:
`
`E3aseaband:‘E..{3 capabiiéfies ...................................................... ..
`ivmcies ..........................................
`....................................... ..
`
`Tabie 6.2:
`
`3GPC1J§'§..}v’I:.‘i8p8Ct-E‘: .................................................................... ..
`
`":"ai:3Ee
`
`icfie mode proceumes ............................................................
`
`1 December 1999
`
`List of Tables
`
`AFFLT0294552
`
`Samsung Ex. 1019 p. 1324
`
`

`
`FAX PROFILE
`
`s
`éi
`
`This rofile §efines the requirements for
`Blueoth cl
`ices necessary for the support
`of th -.1 Fax u e case. The requirements are
`expr ssed irg terms of end-user services, and
`by dgfining fhe features and procedures that
`are jequire _ for interoperability between
`Bl:fetooth§ evices in the Fax use case.
`
`_:8
`
`'
`
`AFFLT0294553
`
`Samsung Ex. 1019 p. 1325
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 244 of-440
`
`Fax Profile
`
`1 December 1999
`
`AFFLT0294554
`
`Samsung Ex. 1019 p. 1326
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`F"""’”"°”’°
`
`CONTENTS
`
`page 245 of 440
`
`Bluetouth.
`
`imrcsziuctim ......................
`
`.................
`
`.........................
`
`....... ......24$
`
`1.’!
`
`1.12
`
`1.3
`
`Profiia £’Jeper2de.=‘=Ci3s ............................................................. .246
`
`Symimis and <;::rw's.>.nt§:;n.<s........................................................24?
`1.3.‘!
`ReqL:iremen§. siatus syrnbczis ..................................... .24?
`
`1.3.2
`
`Signaiiing diagram sconventions...................................248
`
`Prafiie overview... .......................
`
`..............................
`
`................ ...2«<E-§
`
`2.2
`
`2.4
`
`2.5
`
`C0r:f§gL:rati:.:.r1s and raises ........................................................ .258
`User requirernents and scenariass .......................................... .25“!
`Profiize fursdamentais .............................................................. .251
`
`Confarmance
`
`................................ ......253
`Amsiiazatimn Layer ......................................
`3.’:
`Service overview .................................................................... ..2:’§3
`
`3.2
`
`3.3
`
`3.4
`
`Data caiis ............................................................................... ..2E:3
`
`Fax service .............................................................................. .253
`
`Voice caiis .............................................................................. ..§-253
`
`ilfiaiiingg and Centre! intemgxerabiiity Requiremrmts .........
`4.1
`.»5.'f'cor?1mand set used
`
`......... ..2£°>»$
`
`4.1.1
`
`Comman.-3! syntax. ‘Prutocois sand Rs-ssuit Cofie:~:..........254
`
`4.12
`
`Fax Service Ciass seieciion prcicedura.........-\,...........25«'2~
`
`4.2
`
`Caii progress audio feeciback ................................................. ..2-55
`
`Sariai Port Pmfiie
`
`‘.1
`
`R$5'{3C>M?v1EnteroperabiiityRequirements...........................,.....2Ei"
`
`E_2<i3AF’ ir>.ierc.-;3erab-ééiiy Requirements .................................... ..25f:3
`SDF’ !r1ier'r3per'abi!E’ty Requérernerxts ........................................ ..2€*3
`
`E__ir‘.§-: Mai1agar(LM_‘, Entera{.:erabiEity F§’3qL.:irements5 ...................
`
`Uni: Contra! {LC} iwzeroperabiiiiy Requirements ....................
`5.5.1
`Ciass of Eievice usage ............................................... .258
`
`Generic Accass Pmfiie éntercparabiiity Requirements
`6.1 Medea
`
`5.2
`8.3
`
`Securfiy
`idfie mode prooeiiures ............................................................ ..25{}
`$3.13.‘?
`§3c>m"£én§; ..................................................................... "260
`
`Lgst :3?
`
`L25: af iaisias
`
`1 December 1999
`
`AFFLTD294555
`
`Samsung Ex. 1019 p. 1327
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 246 of440
`
`Fax Profile
`
`1
`
`INTRODUCTION
`
`1.1 SCOPE
`
`Bluetooth-
`
`The Fax profile defines the protocols and procedures that shall be used by
`devices implementing the fax part of the usage model called ‘Data Access
`Points. Wide Area Networks’ (see Bluetooth SIG MRD).
`
`A Bluetooth cellular phone or modem may be by a computer as a wireless fax
`modem to send or receive a fax message.
`
`1.2 PROFILE DEPENDENCIES
`
`In §5i§t.t§"¥:3 1.1. 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 profile(s) in which it is con-
`tained ~ directly and indirectly.
`
`C0fC"e5S
`Telephony Profile
`
`H:
`
`Intercom Profile
`
`'
`3 Dial-up Networking
`= Profile
`
`_ " '
`Fax Profile
`
`'
`b‘
`E
`h
`gfcrffizco ‘act X6 ange
`
`File Transfer
`Profile
`
`I Headset Profile
`
`Object Push Profle
`
`_
`_-
`. LAN Access Profile
`
`Synchronization
`Profile
`
`Figure 1.1: Bluetooth Profiles
`
`As indicated in the figure, the Fax profile is dependent upon both the Serial
`Port Profile and the Generic access profile — details are provided in Section
`Sen-"at Port Frofiie on page 258 and Section 6 Generic Access Profile E?te‘::'{)f;;:e‘='-»
`at>iEity' Requ':r'ements on page 259.
`
`1 December 1999
`
`introduction
`
`AFFLT0294556
`
`Samsung Ex. 1019 p. 1328
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`’”""’“”"°”"*
`
`1.3 SYMBOLS AND CONVENTIONS
`
`1.3.1 Requirement status symbols
`
`In this document, the following symbols are used:
`
`page 247 of 440
`
`Bluetooth.
`
`-
`
`-
`
`-
`
`‘M’ for mandatory to support
`
`‘O’ for optional to support
`
`‘X’ for excluded (used for capabilities that may be supported by the unit but
`which shall never be used in the use case)
`
`‘C‘ for conditional to support
`
`‘NIA’ 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 in this use case. Therefore, these features shall never be
`activated while a unit is operating as a unit within this use case.
`
`Within the scope of this Fax profile, the expression ‘Fax class" is used as a
`shortcut to ‘facsimile service class" as defined by {:2}. I3}, {'4} and {4}. This is not
`to be confused with Bluetooth service class.
`
`Introduction
`
`1 December 1999
`
`AFFLT0294557
`
`Samsung Ex. 1019 p. 1329
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Fax Profile
`
`1.3.2 Signaliing diagram conventions
`
`page 248 of 440
`
`Bluetooth.
`
`The following arrows are used in diagrams describing procedures:
`
`3-’(::miamr_v sign.-:1 senl by .-\
`
`Opuonnl slgnal 5I|:l1l by B
`
`.\-'I:md.':lnry proccdtlrd: II1:llIill|‘l'lI by T1
`
`Optional pmocdun: 'm.'ilintcd by A
`
`Lt’
`
`.\.{:1.nd:mJr_v pmucdun: initiated by cithrr A or I3
`
`l"‘~..~.
`\‘I
`_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __I
`Optional pmccdurc imlmml by clthcr.-\ or}!
`
`‘
`
`Figure 1-2 Arrows used in signafling diagrams
`
`1 December 1999
`
`inlroduction
`
`AFFLT0294558
`
`Samsung Ex. 1019 p. 1330
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`’”""’“°"°”’e
`
`2 PROFILE OVERVIEW
`
`2.1 PROFILE STACK
`
`page 249 of 440
`
`Bluetooth.
`
`The figure below shows the protocols and entities used in this profile.
`
`Application
`
`(Modem emulation)
`
`Application
`
`(Modem driver)
`
`Dialling and control
`
`Dialling and control
`
`Gateway side
`
`Data terminal side
`
`Figure 2. 1: Protocol model
`
`The Baseband, LMP and LZCAF’ are the OSI layer 1 and 2 Bluetooth protocols.
`RFCOMM is the Bluetooth adaptation of GSM TS 07.10 it}, used for providing
`serial port emulation. SDP is the Bluetooth Service Discovery Protocol. Dialling
`and control (see Section at) defines the commands and procedures used for
`automatic dialling and control over the asynchronous serial link provided by the
`lower layers.
`
`The modem emulation layer shown in Figure 2.‘? is the entity emulating the
`modem, and the modem driver is the driver software in the data terminal.
`
`For the shaded protocolslentities in a'~'-‘igure 2.3, The Eseréal Port §3’ror“aie 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).
`
`Profile overview
`
`1 December 1999
`
`AFFLT0294559
`
`Samsung Ex. 1019 p. 1331
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Fax Profile
`
`2.2 CONFIGURATIONS AND ROLES
`
`page 250 of440
`
`Bluetooth-
`
`The figures below show two typical configurations of devices for this profile:
`
`Cellular phone
`
`Figure 2.2: Fax profile, example with cellular phone
`
`PC
`
`Figure 2.3: Fax profile, example with modem
`
`The foilowing roles are defined for this profile:
`
`Gateway (GW) — This is the device that provides facsimile services. Typical
`devices acting as gateway are cellular phones and modems.
`
`Data Terminal (DT) — This is the device that uses the facsimile 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 Fax profile to the conventional modem system
`architecture, the GW is considered Data Circuit Endpoint (DCE), and the DT is
`considered Data Terminal Endpoint (DTE).
`
`1 December 1999
`
`Profile overview
`
`AFFLT0294560
`
`Samsung Ex. 1019 p. 1332
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Fax Profile
`
`page 251 of 440
`
`Bluetooth.
`
`2.3 USER REQUIREMENTS AND SCENARIOS
`
`The Fax profile defines the usage ofa GW by a DT as a wireless modem to
`send or receive fax messages
`
`The following restrictions apply to this profile:
`
`a) The GW (cellphone or modem) is not required to be able to report
`andlor 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.
`
`c) Only one call at a time is supported.
`
`d) The profile only supports point-to-point configurations.
`
`e) Since in this profile there is no way defined to discriminate
`between 2 SCO channels originating from the same device, it is
`manufacturer specific as to deal with the situation where there are
`multiple applications requiring the use of multiple SCO channels
`originating from the same device.
`
`f) This profile does not support multiple instances of its
`implementation in the same device.
`
`2.4 PROFILE FUNDAMENTALS
`
`Here is a brief summary of the interactions that take place when a DT wants to
`use the facsimile services of a GW.
`
`1. If the DT does not have the Biuetooth Address of the GW, the DT has to
`obtain the address; e.g. using the Device discovery procedure. see Section
`of Generic Access profile.
`
`. The Fax profile mandates the use of a secure connection through the
`authentication procedure (see Sec:tit.=n 5.1 of Generic Access profile), and
`encryption of all user data through the baseband 2' LMP encryption mecha-
`nisms (see Section 8 of the Generic Access profile).
`
`. Link establishment is always initiated by the DT.
`
`. There are no fixed master I slave roles.
`
`. The fax call is established.
`
`. The (BW and DT provide serial port emulation. For the serial port emulation,
`the serial port profile (see Serial Port F-‘ro‘file) is used. The serial port emula-
`tion is used to transport the user data, modem control signals and AT com-
`mands between the GW and the DT. AT-commands are parsed by the GW
`and responses are sent to the DT.
`
`7. An optional SCO link may be used to transport fax audio feedback.
`
`. After the fax call has been cleared, the channel and link will be released as
`well.
`
`Profile overview
`
`1 December 1999
`
`AFFLT0294561
`
`Samsung Ex. 1019 p. 1333
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Fax Profile
`
`2.5 CONFORMANCE
`
`page 252 of440
`
`Bluetooth-
`
`When conformance to this profile is claimed, all capabilities indicated manda-
`tory 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 condi-
`tional capabilities, for which support is indicated, are subject to verification as
`part of the Blueiooth certification program.
`
`1 December 1999
`
`Profile overview
`
`AFFLT0294562
`
`Samsung Ex. 1019 p. 1334
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Fax Profile
`
`3 APPLICATION LAYER
`
`page 253 of 440
`
`Bluetooth.
`
`This section describes the service requirements on units active in the Fax
`profile.
`
`3.1 SERVICE OVERVIEW
`
`Tabie 331. shows the required services:
`
`—
`
`RE
`
`5.
`
`Voice call
`
`R
`NIA
`
`NIA
`
`Table 3.1: Application layer procedures
`
`3.2 DATA CALLS
`
`The support of data calls is not covered by this profile.
`Refer to Eiiai--up féetvsiorking Profits.
`
`3.3 FAX SERVICE
`
`At least one of the following fax classes of service is mandatory for both the
`GW and the paired DT (see E3ec;tioa"= 4.1.2):
`
`Fax Class 1 TIA-578-A 523 and ITU T3‘! {4}
`
`Fax Class 2.0 TIA-592 {3‘gand ITU T.32
`
`Fax Service Class 2 — No industry standard exists (manufacturer specific).
`
`Optionally, audio feedback may be provided (see Section 4.2).
`
`The GW shall emulate a modem connected via a serial port. The ffieriai Port
`Fro-fiie is used for RS-232 emulation, and RFCOMM running on top of the
`serial port profile provides the modem emulation.
`
`3.4 VOICE CALLS
`
`The support of voice calls is not covered by this profile. Refer to Ct:-rdtess Teta-
`phony Wernféie.
`
`Application layer
`
`1 December 1999
`
`AFFLT0294563
`
`Samsung Ex. 1019 p. 1335
`
`

`
`BLUETOOTH SPECEFICATION Version 1.0 8
`
`Fax Profile
`
`page 254 of 440
`
`Bluetooth-
`
`4 DIALLING AND CONTROL INTEROPERABILITY
`
`REQUIREMENTS
`
`4.1 AT COMMAND SET USED
`
`To guarantee that basicfunctionality can always be provided, it is required that
`a GW device supports the commands and responses as defined in the sup-
`ported fax class of service(s):
`
`Fax Class 1 TIA-578-A :2; and nu T.31 gag
`
`Fax Class 2.0 TIA-592
`
`1 and no T.32 {5}
`
`Fax Service Class 2 — No industry standard exists (manufacturer specific).
`
`4.1.1 Command syntax, Protocols and Result Codes
`
`Refer to each specific implemented fax service class document for a descrip-
`tion of the required commands, protocols and result codes.
`
`4.1.2 Fax Service Class selection procedure
`
`This profile does not require a specific service class of fax. This profile
`supports 2 standards-based fax ‘classes’ — fax class 1 12}, {tit and fax class 2.0
`[33, {5} ~ and a third manufacturer-specific pseudo-standard. fax class 2 (no
`industry reference standard exists).
`
`The DT shall check the GW SDP or perform an 'AT+FCLASS” command to dis-
`cover the fax class of service(s) supported by the GW.
`
`Bluetooth devices implementing this profile must support a minimum of one fax
`service class, but may support any or all fax services classes.
`
`1 December 1999
`
`Dialling and Control interoperability
`
`AFFLT0294564
`
`Samsung Ex. 1019 p. 1336
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 255 of 440
`
`Fax Profile
`
`Bluetooth.
`
`4.2 CALL PROGRESS AUDIO FEEDBACK
`
`The GW or DT may optionally be able to provide audio feedback during call
`establishment. This clause applies only to gatewaysidata terminals that are
`able to provide audio feedback.
`
`SCO links are used to transport the digitized audio over the Bluetooth link. The
`GW shall take all initiatives for SCO link establishment. The setting of the M
`parameter (see {E}, Section 6.3.14) controls whether the GW provides audio
`feedback.
`
`lfa GW provides audio feedback for a call, the GW shall use the ‘initiate SCO
`link’ procedure (see Link Manager protocoi) to establish the audio link when the
`DCE goes off-hook.
`
`Depending on the setting of the M parameter, the GW releases the audio link
`when the DCE has detected a carrier or when the DOE goes on-hook. The
`‘remove SCO link’ procedure (see [Link Manager pro1oco|]) shall be used for
`audio link release.
`
`if SCO link establishment fails, the call establishment shall proceed without the
`audio feedback.
`
`This profile assumes that the DT is not active in any other profile that uses
`SCO links while it is operating in the Fax profile. Therefore, behavior is
`not defined for a situation where multiple SCO links are established simulta-
`neously.
`
`Dialling and Control Interoperability Requirements 1 December 1999
`
`AFFLT0294565
`
`Samsung Ex. 1019 p. 1337
`
`

`
`BLUETOOTH SPECEFICATION Version 1.0 8
`
`Fax Profile
`
`5 SERIAL PORT PROFILE
`
`page 258 of440
`
`Bluetooth-
`
`This profile requires compliance to the Serial Port Profit:-3. For the purposes of
`reading the Serial Port Profile. the GW shall always be considered to be Device
`B and the DT shall always be considered to be Device A.
`
`The following text together with the associated sub-clauses define the require-
`ments with regards to this profile in addition to the requirements defined in the
`Serial Port Profile.
`
`5.1 RFCOMM INTEROPERABILITY REQUIREMENTS
`
`For RFCOMM, no additions to the requirements stated in ffierial Part Prrssiéie
`apply.
`
`5.2 LZCAP INTEROPERABILITY REQUIREMENTS
`
`For the LZCAP layer, no additions to the requirements stated in Serial Port Pro-
`file apply.
`
`5.3 SDP INTEROPERABILITY REQUIREMENTS
`
`Table 532 lists all entries in the SDP database of the GW defined by this profile.
`The ‘Status’ column indicates whether the presence of this field is mandatory
`or optional.
`
`The codes assigned to the mnemonics used in the ‘Value’ column and the
`codes assigned to the attribute identifiers can be found in Bluetooth Assigned
`Numbers.
`
`Item
`
`Defln ltion:
`
`Service Class ID List
`
`Service Class #0
`
`Service Class #1
`
`Protocol Descriptor List
`
`Protocol #0
`
`Protocol #1
`
`Parameter for Protocol #1
`
`LZCAP
`
`RFCOMM
`
`N = server
`channel #
`
`Table 5.1: Service Database Entries
`
`256
`
`1 December 1999
`
`Serial Port Profile
`
`AFFLT0294566
`
`Samsung Ex. 1019 p. 1338
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`’”""’“”"°”"*
`
`Item
`
`page 257 of 440
`
`Bluetooth.
`
`Service Name
`
`Displayabie
`Text name
`
`Service-provider
`defined
`
`TruefFaise
`
`TruefFaise
`
`TruefFaise
`
`TruetFaise
`
`Audio Feedback Support
`
`Fax Class 1 Support
`
`Fax Class 2.0 Support
`
`Fax Class 2 Support
`
`BluetoothProfiie Descrip-
`torList
`
`Profiie #0
`
`Parameter for Profile #0
`
`Table 5.1: Service Database Entries
`
`*. Indicating version 1.0
`
`5.4 LINK MANAGER (LM) INTEROPERABILITY
`REQUIREMENTS
`
`in addition to the requirements for the Link Manager as stated in the
`§3’r3rt §'—‘rofiEe" on page
`this profile requires support for SCO links. in both
`the (SW and DT. The support is conditional upon the ability to provide audio
`feedback."
`
`Serial Port Profile
`
`1 December 1999
`
`AFFLT0294567
`
`Samsung Ex. 1019 p. 1339
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Fax Profile
`
`page 258 of440
`
`Bluetooth-
`
`5.5 LINK CONTROL (LC) INTEROPERABILITY
`REQUIREMENTS
`
`In the table below. all LC capabilities required by this profile are listed.
`
`Capabilities
`
`Support in
`base-band
`
`GW
`
`DT
`
`Packet types1
`
`Voice codec
`
`CVSD
`
`C1: The support for this capability is mandatory for gateways that are able to provide audio
`feed back to the DT.
`
`C2: The support for this capability is mandatory for data terminals that are able to provide
`audio feedback to the user.
`
`Table 5.2: Baseband/LC capabilities
`
`5.5.1 Class of Device usage
`
`A device which is active in the GW role of the Fax profile shall, in the Class of
`Device field:
`
`1. Set the ‘Telephony’ bit in the Service Class field (see Bluetooth Assigned
`Numbers)
`
`2. Indicate ‘Phone’ as Major Device class (see Bluetooth Assigned
`Numbers)
`
`This may be used by an inquiring device to filter the inquiry responses.
`
`1 December 1999
`
`Serial Port Profile
`
`AFFLT029456B
`
`Samsung Ex. 1019 p. 1340
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`’”""’“”"°”"*
`
`page 259 of 440
`
`Bluetooth.
`
`6 GENERIC ACCESS PROFILE INTEROPERABILITY
`
`REQUIREMENTS
`
`This profile requires compliance to the Gt-:-merit: i’-‘ac-cess Profiie.
`
`This section defines the support requirements with regards to procedures and
`capabilities defined in Generic Access Profiie.
`
`6.1 MODES
`
`The table shows the support status for Modes within this profile.
`
`Procedu re
`
`Discoverability modes
`
`Non-discoverable mode
`
`Limited discoverable mode
`
`General discoverabie mode
`
`Connectability modes
`
`Nomconneciable mode
`
`Connectable mode
`
`Pairing modes
`
`Non-pairable mode
`
`Pairable mode
`
`Table 6.1: Modes
`
`Generic Access Profile Interoperability Requirements 1 December 1999
`
`AFFLT0294569
`
`Samsung Ex. 1019 p. 1341
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 260 of440
`
`Fax Profiie
`
`6.2 secunnv ASPECTS
`
`Bluetooth-
`
`The table shows the support status for Security aspects within this profile.
`
`Support in
`DT
`
`Support in
`Gw
`
`M
`
`M
`
`Procedure
`
`Authentication
`
`Security modes
`
`Security mode 1
`
`Security mode 2
`
`Security mode 3
`
`C1: Support for at least one of the security modes 2 and 3 is mandatory
`
`Tabie 6.2: Security aspects
`
`8.3 IDLE MODE PROCEDURES
`
`The table shows the support status for Idle mode procedures within this profile.
`
`Procedure
`
`Generai inquiry
`
`Limited inquiry
`
`Name discovery
`
`Device discovery
`
`Bonding
`
`Note 1: See section 5.3.1
`
`Tabie 6.3:
`
`idle mode procedures
`
`6.3.1 Bonding
`
`Support in DT
`
`Support in GW
`
`M
`
`O
`0
`
`0
`
`M
`
`NIA
`
`NIA
`
`NIA
`
`MFA
`
`M (Note 1)
`
`It is mandatory for the DT to support initiation of bonding, and for the GW to
`accept bonding.
`
`1 December 1999
`
`Generic Access Profiie Interoperability
`
`AFFLT0294570
`
`Samsung Ex. 1019 p. 1342
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 261 of 440
`
`Fax Profile
`
`7 REFERENCES
`
`Bluetooth.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`TS 101 369 (GSM 07.10) version 6.1.0
`
`TIA~578-A Facsimile Digital Interface. Asynchronous Facsimile DCE Con~
`troi Standard, Service Class 1
`
`TIA-592 Facsimile Digital Interface. Asynchronous Facsimile DCE Control
`Standard, Service Class 2
`
`ITU T.31 Asynchronous Facsimile DCE Control —- Service Class 1
`
`ITU T.32 Asynchronous Facsimile DCE Control — Service Class 2
`
`International Telecommunication Union, "lTU-T Recommendation V.250"
`
`References
`
`1 December 1999
`
`AFFLT0294571
`
`Samsung Ex. 1019 p. 1343
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`""“”"°”’°
`
`8 LIST OF FIGURES
`
`page 262 of440
`
`Bluetooth-
`
`Figure: 15%:
`Fégurs-3 23%:
`
`Figure 2.2:
`
`Eiueicaaaiia Prczfsies ................................................................... ..2-E5
`Prctocoi mcaciei ....................................................................... ..2~’f=9
`
`;J.:':3s":'$e, e:s:am_r;§e with (;e§iL:E;«13'_I3§".=r.}.r‘=£-3 ................................ .. 250
`
`Figure 2.3:
`
`;-"-ax ;.=r‘o:"'i$e, examsie with modem .......................................... “E50
`
`1 December 1999
`
`List of Figures
`
`AFFLT0294572
`
`Samsung Ex. 1019 p. 1344
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Fax Profile
`
`9 LIST OF TABLES
`
`page 263 of 440
`
`Bluetooth.
`
`Tabée 3.1:
`
`Tabie
`
`Tahie 5.2:
`
`Tabée 6.1:
`
`“é's.-me 8.2:
`
`Ta-ibis: 6.3:
`
`A_;>;.=iEcat§=:.=n Sayer ps'oce::'urs=:s ..................................................
`Service Database Entries
`
`256
`
`Ea;~3e;*;3r:c3.fL{3 capabiiitieax .......................................................
`Macias .................................................................................... ..
`
`-=
`
`idisv,» !'E'1i'3fi6:;"J!‘:'}Cu§ii!‘*.~“3:3 ............................................................ ..
`
`-
`
`List of Tables
`
`1 December 1999
`
`AFFLT0294573
`
`Samsung Ex. 1019 p. 1345
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 264 of-440
`
`Fax Profile
`
`1 December 1999
`
`List of Tabtes
`
`AFFLT0294574
`
`Samsung Ex. 1019 p. 1346
`
`

`
`ACCESS PROFILE
`
`This ocum§nt is a LAN Access Profile for
`Blueoth d
`ices. Firstly, this profile defines
`L: |ueto%‘i1-enabled devices can access
`
`the rvicessof a LAN using PPP. Secondly,
`this jarofile sfihows how the same PPP mecha-
`nis@s are fed to form a network consisting
`ofjfiuo Blue" ooth-enabled devices.
`§s
`,6‘
`é’-’
`
`AFFLT0294575
`
`Samsung Ex. 1019 p. 1347
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 266 of-440
`
`LAN Access Profile
`
`1 December 1999
`
`AFFLT0294576
`
`Samsung Ex. 1019 p. 1348
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 267 of 440
`
`LAN Access Profiie
`
`CONTENTS
`
`immsziuction ..........................................
`
`................................... ......2fi$
`
`1.’!
`
`1.12
`
`1.13
`
`Scope
`
`Prufiie ifieperéderzciss ............................................................. ..f»37G
`
`Symimis and c<:rwe:3t§t;nss ..
`
`.. .
`
`.. ....27{}
`
`Frame mrenréew ..........
`
`................................................................. ...??1
`
`2.1
`
`2.2
`2.3
`2.4
`
`2.5
`
`F-*r:‘,-ta:-co! stack
`
`Gonféguratiarzs and raises
`User r'equi:‘ernents arid sceruartos ...................................... .._...2?’2
`Profile E-Lmciamaratais .............................................................. ..27’4
`
`Conforrnance: ......................................................................... ..2?<$
`
`Lfiserinterfaceasgcsects .......
`
`.............................
`
`......
`
`............. .....2?‘5
`
`6.; Genefic
`
`Add:£é0rtaiE'-kzrarreeters ............................................................ ..f»3?'e"
`
`Agzpiication iayer
`4.1
`in§t§aEi2:.a!:.i:.m of i..AN Accesss Point service: .............................. ..2.?8
`
`c3».2
`
`#3
`
`4.4
`4.5
`
`S*"'$-"‘*.°"-§"?3“
`
`(J1-J1}:-CAJ!‘h3*w*
`
`Efiémtdown of Le‘-'\§\3 Acctass Point ass.-r\;éce=3 ................................. ..2?E«}
`
`Establish LAN iionrzeciion
`
`LGSELAN
`L‘i5c0rr.r‘=e<;H_AN Cormectior:..........._........................................280
`
`inétiaéize PP? .......................................................................... .28‘?
`Shutdown PPP ....................................................................... .282
`
`E-Lstabiish E3’¥«"’§=’ Connection ..................................................... .282
`
`i3is(:c3rmect ;=>i‘—‘:"->
`Auztixenticatiorw
`
`Smvica Discuvery
`"M
`85.}? service rec-ords
`
`kink
`9.?
`
`Link
`
`Profsie Errors .......................................................................... .2893
`
`1 December 1999
`
`AFFLTD294577
`
`Samsung Ex. 1019 p. 1349
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 268 0f44-0
`
`LAN Access Profile
`
`11
`
`Management Entity Wecefiures
`13.1
`
`11.1.1 No resp0a':ses tat: inquiry
`
`11.1.2 Hm‘:-3:~3pc}n.setc :3-aging .............................................. .292
`
`11.2 Maxinwm Nurrsberafusers .................................................... ‘U292
`
`APPENWX A {kzécrmative}: ‘fimere anti caunters ......................... "293
`
`AFPENWX 8 {Nmrmaiive}: fuiicrosoft Wirsdews ........................... ..29¢3»
`
`13.‘:
`
`E3-‘(S-2-PC configuration ........................................................... ..2Si=1
`
`.i31.¥’PEE§i3iX C {infnrmative}: intemet Presmmafi {SP} ...................... ".295
`$4.?
`imrxterfaces ........................................................................... .395
`14.1.1 in=terfac.e
`
`14.1.2 in*.'er§ace
`
`14,2 Tm EPCP
`14.2.1
`EPCF’ ilanrsacfiien
`
`M~.2.2 ii” Address A¥EoCatEon
`
`14.2.3 DNS and NBNS
`
`1-4.2.4 NetB§Of:“= over E?-‘
`
`L53? ef figures ................................................................................ ..2$'?
`
`his? :3? Tabiee .................................................................................. "298
`
`References ...................................................................................... . . 2%
`
`$1‘! Nerrraetive :‘efe:'err::es
`
`17.3 inferrnative references ........................................................... ...?".S.¥Q
`
`1 December 1999
`
`AFFLTD294-578
`
`Samsung Ex. 1019 p. 1350
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 269 of 440
`
`LAN Access Profile
`
`1
`
`INTRODUCTION
`
`1.1 SCOPE
`
`This profile defines LAN Access using PPP over RFCOM M. There may be
`other means of LAN Access in the future.
`
`- PPP is a widely deployed means of allowing access to networks.
`PPP provides authentication, encryption, data compression and multi-
`protocol facilities. PPP over RFCOMM has been chosen as a means of pro-
`viding LAN Access for Bluetooth devices because of the large installed base
`of devices equipped with PPP software.
`
`It is recognized that PPP is capable of supporting various networking proto-
`cols (e.g. IP, IPX, etc.). This profile does not mandate the use of any particu-
`lar protocol. However, since IP is recognized as the most important protocol
`used in today's networks, additional IP-related information is provided in an
`appendix. The use of these other PPP protocols is not discussed.
`
`This profile does not deal with conferencing, LAN emulation, ad-hoc net-
`working or any other means of providing LAN Access. These functions are,
`or may be, dealt with in other Bluetooth profiles.
`
`This profile defines how PPP networking is supported in the following situa-
`tions.
`
`a) LAN Access for a single Bluetooth device.
`
`b) LAN Access for multiple Bluetooth devices.
`
`c) PC to PC (using PPP networking over serial cable emulation).
`
`Introduction
`
`1 December 1999
`
`AFFLT0294579
`
`Samsung Ex. 1019 p. 1351
`
`

`
`BLUETOOTH SPECEFICATION Version 1.0 8
`
`page 270 of440
`
`LAN Access Profile
`
`1.2 PROFILE DEPENDENCIES
`
`In =~’3iggLss'e 1.1, the Bluetooth profile structure and the dependencies of the
`profiles are depicted. A profile does have dependencies — direct and indirect —
`on the profi|e(s) within which it is contained. as illustrated in the figure.
`In particular, this LAN Access profile is dependent on the Serial Port and
`Generic Access profiles.
`
`Service Discovery
`;== Profile
`
`.'F_(§$gl3_lN-‘baaed.Profi|e
`_ Cord|essTeIephony
`"= Profile
`
`::
`
`' "at" Port Profile
`
`j Dial-up Networking
`1 Profile
`
`_
`'
`Fax PI'DfllE
`
`'
`
`'
`
`'
`
`'
`
`"
`
`; Headset Profile
`
`I
`_
`:_ LAN Access Profile
`
`Z;
`.j
`
`.;
`
`_
`';
`
`File Transfer
`Profile
`
`._; Object Push Profile
`
`Hf Synchronization
`Profile
`
`Z
`:
`
`Z:
`
`If
`
`Figure 1.1: Bluetooth Profiles
`
`1.3 SYMBOLS AND CONVENTIONS
`
`This profile uses the symbols and conventions specified in Section 1.2 of the
`| Generic Access Profile {E3}.
`
`1 December 1999
`
`introduction
`
`AFFLT02945B0
`
`Samsung Ex. 1019 p. 1352
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 271 of 440
`
`LAN Access Profile
`
`2 PROFILE OVERVIEW
`
`2.1 PROTOCOL STACK
`
`The figure below shows the protocols and entities used in this profile.
`
`Data Terminal
`
`LAN Access Point
`
`Figure 2.1: Protocol Stack
`
`PPP is the IETF Point-to-Point Protocol [$3. PPP-Networking is the means of
`taking IP packets toffrom the PPP layer and placing them onto the LAN. This
`mechanism is not defined by this profile but is a well-understood feature of
`Remote Access Server products.
`
`The Baseband it}, LMP {2} and LZCAP [33 are the OSI layer 1 and 2 Bluetooth