BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 801 of 1082
`
`HCI UART Transport Layer
`
`4 ERROR RECOVERY
`
`If the Host or the Host Controller lose synchronization in the communication
`over RS232, then a reset is needed. A loss of synchronization means that an
`incorrect HCI packet indicator has been detected, or that the length field in an
`HCI packet is out of range.
`
`If the UART synchronization is lost in the communication from Host to Host
`Controller. then the Host Controller shall send a Hardware Error Event to tell
`
`the Host about the synchronization error. The Host Controller will then expect
`to receive an HCl_Reset command from the Host in order to perform a reset.
`The Host Controller will also use the HCl_Reset command in the byte stream
`from Host to Host Controller to re-synchronize.
`
`If the UART synchronization is lost in the communication from Host Controller
`to Host, then the Host Shall send the HCl_Reset command in order to reset the
`Host Controller. The Host shall then re-synchronize by looking for the HCI
`Command Complete event for the HCl_Reset command in the byte stream
`from Host Controller to Host.
`
`See “Host =If3o:‘=t.roElsr le'2tarfar;e F:.=r:r:tionat 53;;e=;‘;ifi{:ati(_m"' ore
`commands and HCI events.
`
`:31? for HCI
`
`Error Recovery
`
`29 November 1999
`
`AFFLT0294029
`
`Samsung Ex. 1119 p. 801
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 802 of1082
`
`HC! UART Transport Layer
`
`29 November 1999
`
`Error Recovery
`
`AFFLT0294030
`
`Samsung Ex. 1119 p. 802
`
`

`
`AFFLT0294031
`
` UETOOTH TEST MODE
`
`2E
`
`.
`
`This : c-cum%ntdescribesthetestmode for
`low-level functionality tests of
`hard are a _
`Blu ' ooth d vices. The test mode includes
`trarfimittersiests (packets with constant bit
`pafierns) gfid loop back tests.
`.a/
`
`Samsung Ex. 1119 p. 803
`
`

`
`
`
`
`
`AFFLT0294032
`
`Samsung Ex. 1119 p. 804
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 805 of 1082
`
`Bluetoath Test Mode
`
`CONTENTS
`
`Qereerai fiascrigztiam . ...................................................................... "896
`
`1.2
`
`Aciévatior:
`
`‘fest Scenarics ................................................................................ "883
`
`2.1
`
`Transmitter Test ..................................................................... ..8<}8
`2.1.1
`F’ac§<etFormat ........................................................... .398
`
`2.1.2
`
`F‘seu<1'c:r'a—mci:3m Esequerace ......................................... .8‘! 0
`
`2.1.3
`2.1.43
`
`Reduceci Hogspirzg Sequence
`ilcntmi of T!'&!":‘$?‘I‘sii Parameters ................................ .61?
`
`2.1.5
`
`Power Centre! ............................................................ ..812
`
`2.3.6
`
`Switch between different a'~"reqa.aency Setisngs
`
`2.2 Lo{)pBack
`
`fiuiiézze cs? Propeseci LMP Messages ............................................ ..8'$?'
`
`Refers-zncea ...................................................................................... "819
`
`29 November 1999
`
`AFFLT0294033
`
`Samsung Ex. 1119 p. 805
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 806 of1082
`
`Biuetooth Test Mode
`
`Bluetooth-
`
`1 GENERAL DESCRIPTION
`
`The test mode supports testing of the Bluetooth transmitter and receiver. It is
`intended mainly for certificationicompliance testing of the radio and baseband
`layer, and may also be used for regulatory approval or in-production and after-
`sales testing.
`
`A device in test mode must not support normal operation. For security reasons
`the test mode is designed such that it offers no benefit to the user. Therefore.
`no data output or acceptance on a HW or SW interface is allowed.
`
`1.1 TEST SETUP
`
`The setup consists of a device under test (DUT) and a tester. Optionally. addi-
`tional measurement equipment may be used.
`
`Control commands
`......._._.._._...._:_’.
`Test data
`
`Device under
`Test
`
`Local activationienabling
`
`,r—_;=Edi:i3rEI_ _'
`| Measurement
`Eq ui pment
`
`Figure 1.1: Setup for Test Mode
`
`Tester and DUT form a piconet where the tester acts as master and has full
`control over the test procedure. The DUT acts as slave.
`
`The control is done via the air interface using LMP commands (see Section 3
`on page 83?’ and "‘t..in§< tviana-gar P:'otc.r;ol" on
`185). Hardware interfaces
`to the DUT may exist. but are not subject to standardization.
`
`The test mode is a special state of the Bluetooth model. For security and type
`approval reasons, a device in test mode may not support normal operation.
`When the DUT leaves the test mode it enters the standby state. After power-off
`the Bluetooth device must return to standby state.
`
`29 November 1999
`
`General Description
`
`AFFLT0294034
`
`Samsung Ex. 1119 p. 806
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 807 of 1082
`
`Bluetooth Test Mode
`
`1.2 ACTIVATION
`
`The activation may be carried out locaily (via a HW or SW interface), or using
`the air interface.
`
`- For activation over the air interface, entering the test mode must be locally
`enabled for security and type approval reasons. The implementation of this
`local enabling is not subject to standardization.
`The tester sends an LMP command that forces the DUT to enter test mode.
`
`The DUT terminates all normal operation before entering the test mode.
`
`The DUT shall return an LMP_Accepted on reception of an activation com-
`mand. LMP_Not_Accepted shall be returned if the DUT is not locally
`enabled.
`
`If the activation is performed locally using a HW or SW interface, the DUT
`terminates all normal operation before entering the test mode.
`
`Until a connection to the tester exists, the device shall perform page scan
`and inquiry scan. Extended scan activity is recommended.
`
`1.3 CONTROL
`
`Control and configuration is performed using special LMP commands (see
`Section 3 on page 83?). These commands must be rejected if the Bluetooth
`device is not in test mode. in this case, an LMP_not_accepted is returned. The
`DUT shall return an LMP_accepted on reception of a control command when in
`test mode.
`
`A Bluetooth device in test mode must ignore all LMP commands not related to
`control of the test mode. LMP commands dealing with power control and the
`request for LMP features (LlvlP_features_req) are allowed in test mode; the
`normal procedures are also used to test the adaptive power control.
`
`The DUT can be commanded to leave the test mode by an Llv1P_Detach com-
`mand or by sending an LM P_test_contro| command with test scenario set to
`‘exit test mode’.
`
`General Description
`
`29 November 1999
`
`AFFLT0294035
`
`Samsung Ex. 1119 p. 807
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Biuetooth Test Mode
`
`2 TEST SCENARIOS
`
`2.1 TRANSMITTER TEST
`
`page 808 of 1082
`
`Bluetooth-
`
`The Bluetooth device transmits a constant bit pattern. This pattern is transmit-
`ted periodically with packets aligned to the slave TX timing of the piconet
`formed by tester and DUT. The same test packet is repeated for each transmis-
`sion.
`
`The transmitter test is started when the master sends the first POLL packet. In
`non-hopping mode agreed frequency is used for this POLL packet.
`
`The tester transmits at his TX slots (control commands or POLL packets). The
`slave starts burst transmission in the following slave TX slot. The masters poll-
`ing interval is fixed and defined beforehand. The device under test may trans-
`mit its burst according to the normal timing even if no packet from the tester
`was received.
`
`The burst length may exceed the length of a one slot packet. In this case the
`tester may take the next free master TX slot for polling. The timing is illustrated
`in Fig=..sre
`
`Burst Length
`
`Test Packet
`
`Burst Length
`POLL «a»
`
`Master TX I SiaveT>(
`
`Master TX I 5laveTX
`
`I
`Master TX I S|aveT>(
`
`Figure 2.1: Timing for Transmitter Test
`
`2.1.1 Packet Format
`
`The test packet is a normal Bluetooth packet, see Figure
`itself see below.
`
`For the payload
`
`29 November 1999
`
`Test Scenarios
`
`AFFLT0294036
`
`Samsung Ex. 1119 p. 808
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 809 of 1082
`
`Bluetooth Test Mode
`
`Bluetouth.
`
`ACL Packet
`
`(with CRC)
`
`AUX1 Packet
`
`SCO Packet
`
`Figure 2.2: General Format of TX Packet
`
`During configuration the tester defines:
`
`-
`
`the packet type to be used
`
`- payload length
`
`For the payload length, the restrictions from the baseband specification apply
`(see "‘E3aset.>and f3pecification" on
`33.). In case of AOL packets the pay-
`load structure defined in the baseband specification is preserved as well, see
`§‘§guz'e-
`
`For the transmitter test mode, only packets without FEC should be used; i.e.
`HV3, DH1, DH3, DH5and AUX1 packets. Support of packet type is only manda-
`tory up to the longest implemented packet type.
`
`In transmitter test mode, the packets exchanged between tester and DUT are
`not scrambled with the whitening sequence. Whitening is turned off when the
`DUT has accepted to enter the transmitter test mode, and is turned on when
`the DUT has accepted to exit the transmitter test mode, see Fig-..tre 2.3.1
`
`1. Note: implementations must ensure that retransmtsslons of the LMP_Accepted messages
`use the same whitening status.
`
`Test Scenarios
`
`29 November 1999
`
`AFFLT0294037
`
`Samsung Ex. 1119 p. 809
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 810 of1082
`
`Biuetooth Test Mode
`
`TESTER
`
`Bluetooth-
`
`L.MF‘.4.?$L9°"".°'
`{Enter Transmitter Test
`
`LMP_accepted
`
`Wh“e”i”9 9”
`
`LMP_test_oontrol
`{Exit Transmitter Test
`
`Whitening on
`
`Figure 2.3: Use of whitening in Transmitter mode
`
`2.1.2 Pseudorandom Sequence
`
`In case of pseudorandom bit sequence, the same sequence of bits is used for
`each transmission (i.e. the packet is repeated, see above). A PRBS—9
`Sequence2 is used, see {2} and E3}.
`
`The properties of this sequence are as follows (see 333). The sequence may be
`generated in a nine-stage shift register whose 5th and 9th stage outputs are
`added in a modulo-two addition stage (see E‘~"igure 2.4), and the result is fed
`back to the input of the first stage. The sequence begins with the first ONE of 9
`consecutive ONES; i.e. the shift register is initialized with nine ones.
`
`- Number of shift register stages:
`
`9
`
`- Length of pseudo-random sequence: 29-1 = 511 bits
`
`- Longest sequence of zeros:
`
`8 (non-inverted signal)
`
`Figure 2.4.’ Linear Feedback Shift Register for Generation of the PRBS sequence
`
`2. Some uncertainties about Japanese regulatory requirements have been reported. It neces-
`sary for regulatory type approval in Japan. some features might be added; eg. a longer PN
`sequence.
`
`81 0
`
`29 November 1999
`
`Test Scenarios
`
`AFFLT0294038
`
`Samsung Ex. 1119 p. 810
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 811 of 1082
`
`Bluetooth Test Mode
`
`2.1.3 Reduced Hopping Sequence
`
`To support quick testing of the radio over the complete frequency range, a
`reduced hopping mode is defined. Implementation of this mode is optional for
`Bluetooth devices and modules.
`
`Reduced hopping uses only five frequencies, on which a sequential hopping is
`done (channels 0, 23, 46, 69 and 93 are used3), see i—"'ag=.,:r£-3 2.5.
`
`Channel
`
`CLKQM mod 5 =
`
`Figure 2.5: Reduced hopping scheme
`
`The timing is based on the Bluetooth clock of the tester. The value of CLK274
`
`(i.e. not using CLKO, representing half slots) modulo 5 is used to determine the
`transmit frequency.
`
`2.1.4 Control of Transmit Parameters
`
`The following parameters can be set to configure the transmitter test:
`
`1. Bit pattern:
`- Constant zero
`- Constant one
`
`- Alternating 1010...‘
`0 Alternating 1111 0000 1111 0000...‘
`- Pseudorandom bit pattern
`- Transmission off
`
`. Frequency selection:
`a Single frequency
`o Hopping Europei'USA
`- Hopping Japan
`- Hopping France
`0 Hopping Spain
`o Reduced Hopping (implementation in Bluetooth devices and modules is
`optional)
`
`3. TX frequency
`o k=>f:= (2402 + k) MHz
`
`. The range is chosen to test the whole frequency range, which covers the normal 79
`channels, as well as Spanish. French and Japanese hopping schemes. The frequency
`assignment rule is the same as for the fixed TX frequency: f = (2402 + K) MHZ.
`. It is recommended that the sequence starts with a one‘. but. as this is irrelevant for measure-
`ments. it is also allowed to start with a zero.
`
`Test Scenarios
`
`29 November 1999
`
`AFFLT0294039
`
`Samsung Ex. 1119 p. 811
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Biuetooth Test Mode
`
`page 812 of1082
`
`Bluetooth-
`
`4. Defautt poll period in TDD frames (n * 1.25 ms)
`
`5. Packet Type
`
`6. Length of Test Sequence (user data of packet definition in Beseband Speci-
`fication” on page 33.)
`
`2.1.5 Power Control
`
`If adaptive power control is tested, the normal LMP commands will be used.
`The DUT starts to transmit at the maximum power and reducesiincreases its
`power by one step on every command received.
`
`2.1.6 Switch between different Frequency Settings
`
`A change in the frequency selection becomes effective when the LMP proce-
`dure is completed:
`
`The tester switches to a new frequency or hopping pattern after the
`LM P_Accepted message has been received.
`
`The DUT switches after the LMP_accepted message has been sent.
`
`Note: Loss of the LMP_/iccepted packet wiii eventuaiiy lead to a toss of
`frequency synchronization that cannot be recovered. Similar prob.-‘ems occur in
`normai operation, when the hopping pattern changes.
`
`2.2 LOOPBACK TEST
`
`The device under test receives normal baseband packets. The received pack-
`ets are decoded in the DUT, and the payload is sent back using the same
`packet type. The return packet is sent back in either the TX slot directly follow-
`ing the transmission of the tester, or it is delayed and sent back in the slot after
`the next transmission of the tester (See F“igs_sre 2.?” to Figttre 2.9 an page 8'15}.
`
`Alternatively, it is possible to implement a delayed loopback instead. Then the
`return packet is delayed to the following TX slot. There is no signalling to deter-
`mine or control the mode. The device behavior must be fixed or adjusted by
`other means, but must not change randomly.
`
`The tester can select, whether whitening is on or off. This setting holds for both
`up- and downlink. For switching the whitening status, the same rules as in Sec-
`tion
`on page 808 (Figure 3-3.3) appiy.
`
`The foilowing rules apply (for illustration see Figure
`
`on
`
`«'1-):
`
`- Clearly, if the synch word was not detected, there will be no reply.
`
`-
`
`If the header error check (H EC) fails, the DUT replies with a NULL packet
`with the ARON bit set to NAK. It is not mandatory to return a NULL packet in
`this case; the DUT may send nothing.
`
`29 November 1999
`
`Test Scenarios
`
`AFFLT0294040
`
`Samsung Ex. 1119 p. 812
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 813 of 1082
`
`Bluetaath Test Mode
`
`If the packet contains an LMP message relating to the control of the test
`mode this command is executed and the packet is not returned, though ACK
`or NAK is still returned as usual procedure. Other LMP commands are
`ignored and no packet is returned.
`
`The payload FEC is decoded and the payload is coded again for transmis-
`sion. This allows testing of the FEC handling. If the pure bit error rate shall
`be determined the tester chooses a packet type without FEC.
`
`The CRC is evaluated. In case of a failure, the payload is returned with
`ARON = NAK. The CRC for the return packet is calculated for the returned
`payioad .
`
`-
`
`If the CRC fails the number of bytes as indicated in the (possibly erroneous)
`payload header shall be looped back.
`
`Test Scenarios
`
`29 November 1999
`
`AFFLT0294041
`
`Samsung Ex. 1119 p. 813
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 814 of1082
`
`Biuetooth Test Mode
`
`Receive Path:
`
`Synch found
`
`Decode Header
`
`Packet type
`without FEC
`
`'
`
`‘
`
`Build NULL
`+ ARQN = NAK
`
`Packet type
`without CRC
`
`ARQN = ACK
`
`ARON = NAK
`
`LMP message
`
`Execute LMP
`Command
`
`Transmit Path:
`
`Build Packet
`(incl. ARON)
`
`Figure 2.6: DUT Packet Handling in Loop Back Test
`
`29 November 1999
`
`Test Scenarios
`
`AFFLT0294042
`
`Samsung Ex. 1119 p. 814
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 815 of 1082
`
`Btuetaath Test Mode
`
`The timing for normal and delayed loopback is illustrated in 1”-‘ig.}=u:re 2.? to Féggure
`2.9:
`
`Payload
`
`ARON
`
`TX Packet
`
`RX Packet
`
`TX Packet
`
`Master TX
`
`' Slave TX
`
`Master TX
`
`' Slave TX
`
`Master TX
`
`' Slave TX
`
`fime
`
`Figure 2. 7: Paytoad & ARON handiing in norrnai toopback.
`
`Master TX
`
`' Slave TX
`
`Master TX
`
`' Slave TX
`
`Master TX
`
`. Slave TX
`
`Master TX
`
`' Slave TX
`
`Master TX
`
`' Slave TX
`
`time
`
`Figure 2.9: Payload 8 ARQN handting in detayed ioopback - end.
`
`The whitening is performed in the same way as it is used in normal active
`mode.
`
`The following parameters can be set to configure the loop back test:
`
`1. Packet C|a5s5
`- ACL Packets
`0 SCO Packets
`
`0 ACL Packets without whitening
`o SCO Packets without whitening
`
`5. This is included because. in the future, the packet type numbering may not remain
`unambiguous.
`
`Test Scenarios
`
`29 November 1999
`
`AFFLT0294043
`
`Samsung Ex. 1119 p. 815
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 816 of1082
`
`Biuetooth Test Mode
`
`2. Frequency Selection
`- Single frequency (independent for RX and TX)
`0 Hopping EuropeiUSA
`- Hopping Japan
`0 Hopping France
`0 Hopping Spain
`- Hopping reduced (optional)
`
`Hopping reduced uses oniy five frequencies on which a sequentiei hopping is
`done on (channei: 0, 23, 46, 69 and 93 is used).
`
`3. Power level: (To be used according radio specification requirements)
`- power control or fixed TX power
`
`The switch of the frequency setting is done exactly as for the transmitter test
`(see Sectiet: 2.1% on page 8113).
`
`29 November 1999
`
`Test Scenarios
`
`AFFLT0294-044
`
`Samsung Ex. 1119 p. 816
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Bluetooth Test Mode
`
`page 817 of 1082
`
`Bluetooth.
`
`3 OUTLINE OF PROPOSED LMP MESSAGES
`
`‘Fabio 3.‘: lists all LMP messages used for test mode (see Link Manager Proto-
`col, Sieotiori E5 on page 23?‘).
`
`PDU
`number
`
`Possible
`Direction
`
`LMP PDU
`
`LM F’_te sl_a ctivate
`
`LM P_test_co ntrol
`
`test scenario
`
`hopping mode
`TX frequency
`RX frequency
`power control mode
`poll period
`packet type
`length of test data
`
`<.DOO"-s.IO')U‘I-h(JI\J
`
`LM P_deta ch
`
`LM P_a cce pted
`
`LM P_n ot_ac cepted
`
`Test scenario
`
`Hopping mode
`
`0 Pause {TX ofi}
`1 Transmitter test — 0 pattern
`2 Transmitter test — 1 pattern
`3 Transmitter test — 1010 pattern
`4 Pseudorandom bit sequence
`5 Closed Loop Back - ACL packets
`6 Closed Loop Back ~ SCO packets
`7 AC]. Packets without whitening
`8 SCO Packets without whitening
`9 Transmitter test — 1111 0000 pattern
`10-254 reserved
`255 Exit Test Mode
`
`0 RXITX on single frequency
`1 Hopping Europe;‘USA
`2 Hopping Japan
`3 Hopping France
`4 Hopping Spain
`5 Reduced Hopping {optional}
`6-255 reserved
`
`TX frequency (for DUT)
`
`1‘: [2402 + k] MHz
`
`Table 3.2: Parameters used in L.-‘l/.'P_ Test_Controi PDU
`
`Outline of Proposed LMP Messages
`
`29 November 1999
`
`AFFLT0294045
`
`Samsung Ex. 1119 p. 817
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 818 of1082
`
`Biuetooth Test Mode
`
`Name
`
`Detailed
`
`RX frequency (for DUT)
`
`Power control mode
`
`Poll period
`
`Packet type
`
`length of test sequence
`(=length of user data in
`Brizsriiiaanrti S;>ei:i€ir;a--
`tirl.
`)
`
`’
`
`'
`
`‘
`
`f = [2402 + k] MHZ
`
`0 fixed TX output power
`1 adaptive power control
`
`numbering as in packet header.
`see Baseriaria Specificaticc
`
`unsigned binary number
`
`Table 3.2: Parameters used in i_MP_ Test_Controi PDU
`
`The control PDU is used for both transmitter and loop back tests. The following
`restrictions apply for the parameter settings:
`
`Parameter
`
`TX frequency
`
`RX frequency
`
`Poll period
`
`Restrictions
`Transmitter Test
`
`Restrictions
`Loopback Test
`
`0 5 k s 93
`
`0 E k 3 93
`
`same as TX frequency
`
`0 5 K S 93
`
`not applicable {set to 0)
`
`Length of test sequence
`
`depends on packet type:
`
`not applicable {set to 0)
`
`DH1: 3 28 byte
`DH3:s 181 byte
`
`DH5: 5 339 byte
`
`AUX1: s 29 Byte
`HV3: = 30 byte
`
`Table 3.3: Restrictions for Parameters used in LMP__ Test; Control’ PDU
`
`29 November 1999
`
`Outline of Proposed LMP Messages
`
`AFFLT0294046
`
`Samsung Ex. 1119 p. 818
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 819 of 1082
`
`Bluetooth Test Mode
`
`4 REFERENCES
`
`Bluetooth.
`
`[1] Biuetooth Link Manager Protocol.
`
`[2]
`
`[3]
`
`CCITT Recommendation 0.153 (1992), Basic parameters for the mea»
`surement of error performance at bit rates below the primary rate.
`
`ITU-T Recommendation 0.150 (1996), General requirements for instru-
`mentation for performance measurements on digital transmission equip-
`ment.
`
`Bluetooth Baseband Specification.
`
`29 November 1999
`
`AFFLT0294047
`
`Samsung Ex. 1119 p. 819
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 820 of1082
`
`Biuetooth Test Mode
`
`29 November 1999
`
`References
`
`AFFLT0294-043
`
`Samsung Ex. 1119 p. 820
`
`

`
`
`
`ETOOTH COMPLIANCE
`REQUIREMENTS
`
`nt specifies the requirements for
`mpliance.
`
`AFFLT0294049
`
`Samsung Ex. 1119 p. 821
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 822 of1082
`
`Biuetooth Compfiance Requirements
`
`29 November ‘[999
`
`AFFLT0294050
`
`Samsung Ex. 1119 p. 822
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 823 of 1082
`
`Bluetoath Compfiance Requirements
`
`CONTENTS
`
`Scene .............................................................................................. "$25
`
`‘farms umd ..................................................................................... "825
`
`Legai aspects
`
`The vaiue of the fifiuatomth Eranci ...................................
`
`........... "823
`
`The Eiuetoasth quaiifficatfian gcsmgram ........................................... H836
`
`Siuastszzath Eicense requirements far pm€;§§3£:t5S ..................
`
`...... "832
`
`6.1
`
`Biuesootfx radio iéniv: :‘equé:‘ernents ........................................... .832
`
`Requi:'e:1'1ent descrigsiion ........................................... . .832
`
`6.1.1
`6.1.2
`
`Bitméoath §'§é'{3FC-CO§ requirements
`
`Biueioeth prufiie requirements
`
`6.3.‘?
`8.3.2
`
`R€:?»1‘;‘x.Ei.“..-‘:§‘f‘:8.*:E descrigsiéon
`Quaiificatécm ............................................................... .334
`
`Btu-eiooth infrarmatiorw reqzxir'errsenL~':: ...........
`
`.......................... iI83'£
`
`$.41
`8.4.2
`
`Requirement description
`Quaiificaticzn ...................................
`
`......................... .334
`
`Re-zzuirements on Eiueteoth accessary pmciucts .................... "834
`
`Definition ca?‘ ‘Biueto:3t?: accessory prr:sducts’................5:§3
`6.5.2. Qtsaiificatiun ....................................
`.......................... .334
`
`Ffieapguiaements on E§$L5E”:!0Dfi'1 c<3mpm':enis ............................... “E5134
`
`8.6.‘!
`
`ffiefiniiiesn «.'.>f Eiueiooth comp-onen";$"
`
`5.6.2
`
`Re-::;uia'-:—:mer:§ descrig:-Sion
`Quaiificatéen ............................................................... .335:
`
`fiiuetaoth iicanse prcvisiens far earfiy products ......................... “SEE
`
`29 November 1 999
`
`AFFLT0294051
`
`Samsung Ex. 1119 p. 823
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 824 of1082
`
`Bruefooth Compfiance Requirements
`
`3
`
`fiiuetooth Brand License gznrovéséoms for speciafl gtrmtsfiucts &
`marketing ................................................................
`....................M83?
`
`8.‘!
`
`E;‘a£uet{.>0th Deve§0§3meném0§s and
`8.1.1
`{J-e:finitim*. of ‘aiuetoath Ceveioganaené $0953
`and demos‘
`
`8.1.2
`8.1.3
`
`Requiremezrzt des<:ri:.:>iEo.r*:
`Quatéficatiorr
`
`83?
`
`Mar'ket§r:3 ......................................
`
`........................................ ..83?
`
`Recornmendafiicans cnncerniag izifomaatien aimut a §:nr:3dut:t‘s
`fiiuataoth cagsahiiities .................................................................... "838
`
`Quafiity management, mnffiguration management am; versiam
`centre? ............................................................................................. ..33§
`
`Amzszndix A »» Exampie cf a *‘Eiuatanth Capabiiéiy fitatemsmt”
`
`8&0
`
`Agzpsandix B ~ Niarketirzg names mi aiuetxsoth gzmffiies
`
`29 November 1999
`
`AFFLT0294052
`
`Samsung Ex. 1119 p. 824
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 825 of 1082
`
`Bluetooth Compliance Requirements
`
`1 SCOPE
`
`The Bluetooth Promoters and the Bluetooth Adopters have signed the Promot-
`ers‘ Agreement and the Adopters’ Agreement respectively. These agreements
`grant Promoters and Adopters a Bluetooth license for “products which comply
`with the Specification“.
`
`This document specifies the requirements which must be met by a Promoter or
`Adopter to demonstrate that a particular product does “comply with the Specifi-
`cation", thereby qualifying that particular product to be subject to the rights
`extended by the Promoters‘ and Adopters’ Agreements respectively.
`
`The Bluetooth Qualification Program is the process by which a Promoter or an
`Adopter demonstrates that a particular product meets the requirements speci-
`fied herein. This document provides an overview of the requirements and the
`Bluetooth Qualification Program. Further details are available through the
`Bluetooth Web site.
`
`Regulatory requirements and governmental type approval requirements are
`outside the scope of this document.
`
`29 November 1 999
`
`AFFLT0294053
`
`Samsung Ex. 1119 p. 825
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Bluetooth Compliance Requirements
`
`2 TERMS USED
`
`page 826 of 1082
`
`Bluetooth-
`
`Bluetooth Trademark —As defined in the Promoters‘ Agreement and the
`Adapters’ Agreement.
`
`Bluetooth Brand — Covers all the brand elements specified in the "The Blue-
`tooth Brand Book". Equal to the Bluetooth Trademark.
`
`Bluetooth Logo or Logo —the brand element referred to as the ‘figure mark’ in
`the ‘The Bluetooth Brand Book‘.
`
`Bluetooth l_icense— all the rights, defined in the Promoters’ and Adopters'
`Agreements respectively, that are granted by compliance with the specification,
`i.e. the Bluetooth Patent License and the Bluetooth Brand License.
`
`Bluetooth Patent License — the applicable parts of the Bluetooth license con-
`sisting of patent rights or parts thereof as defined in the Promoters‘ and
`Adopters' Agreements respectively.
`
`Bluetooth Brand License — the applicable parts of the Bluetooth license con-
`sisting of trademark rights as defined in the Promoters‘ and Adopters’ Agree-
`ments respectively.
`
`Protocol specification — defines the communication between two peer devices
`at a certain layer.
`
`Profile spa-cification— defines the usage of (parts of) the protocol stack for a
`certain Bluetooth usage model.
`
`Bluetooth qualification process — the rules and procedures by which the manu-
`facturer demonstrates compliance to the Bluetooth specification.
`
`Bluetooth qualification program — the implementation of the Bluetooth qualifica-
`tion process.
`
`Bluetooth Qualification Review Board (BQRB)— responsible for managing,
`reviewing and improving the Bluetooth qualification program. The original
`Bluetooth SIG companies will appoint BQRB initial members.
`
`Bluetooth Qualification Test Facility (BQ TF) — a test facility that is officially
`authorized by BQRB to test Bluetooth products.
`
`Bluetooth Qualification Body (BQB)— a specific person authorized by the
`BQRB to be responsible for checking declarations and documents against
`requirements. reviewing product test reports, and listing products on the official
`database of Bluetooth qualified products.
`
`Bluetooth Qualification Administrator (BQA) — a person responsible for admin-
`istering the Bluetooth Qualification Program on behalf of BQRB.
`
`29 November 1999
`
`AFFLT0294054
`
`Samsung Ex. 1119 p. 826
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 827 of 1082
`
`Bluetooth Compfiance Requirements
`
`fmpiementarfon Conformance Statement (ICS)— a document that the manufac-
`turer attaches to the product when submitting it for qualification. It specifies all
`the implemented Bluetooth capabilities in detail.
`
`Biuetooth Fellow/1doprer— equal to Bluetooth Promoters + Bluetooth Adopt-
`ers.
`
`Terms used
`
`29 November 1999
`
`AFFLT0294055
`
`Samsung Ex. 1119 p. 827
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Bluetooth Compliance Requfremen rs
`
`3 LEGAL ASPECTS
`
`page 828 of 1082
`
`Bluetooth-
`
`Rules and guidelines on how to use the Bluetooth Brand elements are stated in
`the document “'T'rae Bluetooth Brand frock" which is available on the Bluetooth
`Web site.
`
`The Bluetooth Specification has been created. according to our best knowl-
`edge, to meet regulatory requirements worldwide. Regulatory certification as
`such is not a part of the Bluetooth qualification requirements, yet it is a require-
`ment in all markets. It is the sole responsibility of each manufacturer to ensure
`that their products have all necessary regulatory approvals for the markets
`where their product(s) are intended to be sold or used.
`
`A product must complete Bluetooth Qualification to meet the requirements for
`"complying with the Specification". The Bluetooth license granted by the Pro-
`moters‘ and Adopters’ Agreements respectively is valid only for qualified prod-
`ucts and is not transferable to other products.
`
`In this document, the ‘Bluetooth license’ is sometimes divided into the ‘Blue-
`
`tooth patent license’ and the ‘Bluetooth brand license’ for practical reasons.
`These terms correspond, respectively, to the terms ‘necessary claims‘ and
`‘trademark’ in the Promoters’ and Adopters' Agreements respectively.
`
`Sanctions will be invoked against any company responsible for producing or
`trading (a) products containing elements of the Bluetooth Interface, as defined
`in the Bluetooth Promoters’ Agreement and Adopters' Agreement respectively,
`that do not comply with the Specification, or (b) products containing elements
`of the Bluetooth Interface that have not completed Bluetooth Qualification.
`
`The Bluetooth SIG reserves the right to define a process for adding new Blue-
`tooth profiles after the release of the Specification 1.0.
`
`A Bluetooth brand license is granted by Ericsson to all Fellow Adopters for the
`use of the trademark in connection with products complying with the Specifica-
`tion.
`
`Ericsson further provides Fellow Adopters a limited indemnity for costs and
`expenses incurred by the Fellow Adopter based upon the use of the trade mark
`within countries where Ericsson has registered the trademark. Ericsson does
`not take upon itself any liability regarding product, whether such liability is
`based on damages caused by the product for persons or property, or defects in
`the product itself.
`
`29 November 1999
`
`Legal aspects
`
`AFFLT0294056
`
`Samsung Ex. 1119 p. 828
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 829 of 1082
`
`Bluetooth Compliance Requirements
`
`4 THE VALUE OF THE BLUETOOTH BRAND
`
`The purpose of this document is to define the requirements for Bluetooth com-
`pliance This has been done while bearing the basic Bluetooth philosophy in
`mind:
`
`"Wireless Connections Made Easy"
`
`Examples of important end-user experiences are:
`
`- Reliable high-quality radio links.
`
`-
`
`Interoperability between products of any brands,
`
`- Easily understood product capabilities.
`
`A reliable radio link experience depends upon all products demonstrating com-
`pliance with the Bluetooth radio link performance specifications. Interoperability
`is achieved by protocol and profile implementation conformance. Ease of use
`depends upon clear, consistent documentation of Bluetooth capabilities in
`product literature. All these elements are addressed in the requirements for
`Bluetooth compliance.
`
`The value of the Bluetooth Brand
`
`29 November 1999
`
`AFFLT0294057
`
`Samsung Ex. 1119 p. 829
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 830 of1082
`
`Biuetooth Compliance Requirements
`
`Bluetooth-
`
`5 THE BLUETOOTH QUALIFICATION PROGRAM
`
`This paragraph specifies the framework of the Bluetooth qualification program
`that a Bluetooth qualification applicant must perform. When completed, the full
`Bluetooth qualification program will be published at the Bluetooth web site.
`
`The Bluetooth qualification program (‘Program’) establishes the rules and pro-
`cedures by which the manufacturer demonstrates compliance to the Bluetooth
`specifications, and the process by which the Bluetooth license may be used by
`product manufacturers and distributors.
`
`The Program defines the following entities:
`
`- Bluetooth Quaiification Review Board (BQRB) — responsible for managing,
`reviewing and improving the Bluetooth qualification program. The original
`Bluetooth SIG companies will appoint BQRB initial members.
`
`Biuetooth Qualification Administrator (BOA) — responsible for administering
`the Bluetooth Qualification Program on behalf of BQRB.
`
`Bluetooth Qualification Test Facihty (BO TF) ~ a test faciiity that is officially
`authorized by BQRB to test Bluetooth products.
`
`Biuetooth Quaiification Body (808) — a specific person authorized by the
`BQRB to be responsible for checking declarations and documents against
`requirements, reviewing product test reports, and listing products on the off-
`cial database of Bluetooth qualified products.
`
`Functions and relationships are illustrated in Figure :3. '3.
`
`Declarations and
`documentation
`reviewed
`
`Qualified
`Products
`List
`
`Fellow Adopter ;
`(Manufacturer) _
`
`D°C”m“3"L°'
`plmed “Pm
`web 5'!“
`
`BQTF and B08
`nB1(:T:ea:;jfi||i:?E% may be in-house
`Y
`functions
`
`Test report
`checked by
`BOB
`
`Qualification
`Program
`Documents
`
`Figure 5.1: Biuetooth Quaiification Process
`
`29 Ncvember19Q9
`
`The Bluetooth qualificat