BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 86 of €882
`
`Baseband Specification
`
`3.4 BITSTREAM paocesses
`
`Bluetooth-
`
`Before the user information is sent over the air interface, several bit manipula-
`tions are performed in the transmitter to increase reliability and security. To the
`packet header, an HEC is added, the header bits are scrambled with a whiten-
`ing word, and FEC coding is applied. In the receiver, the inverse processes are
`carried out. Figure 8.3 an page SE3 shows the processes carried out for the
`packet header both at the transmit and the receive side. All header bit pro-
`cesses are mandatory.
`
`TX header
`
`(LSB first)
`
`HEC generation
`
`FEC encoding
`
`RF interface
`
`Figure 8.3: Header bit processes.
`
`For the payload, similar processes are performed. It depends on the packet
`type, which processes are carried out. i-"igure 8.4 can page
`shows the pro-
`cesses that may be carried out on the payload. In addition to the processes
`defined for the packet header, encryption can be applied on the payload. Only
`whitening and de-whitening, as explained in fie-::t§<3n ‘i or: page ‘F9, are manda-
`tory for every payload; all other processes are optional and depend on the
`packet type and the mode enabied. In Fég=..=re 8.4 an
`E36, optional pro-
`cesses are indicated by dashed blocks.
`
`I
`TX payIoad—:-‘CRO generation'—3-E encryption
`(1.53 firsl)
`'
`
`RF Interface
`
`5
`RX payIoad«u:—‘ CRC checking E-z—:
`
`1
`
`decryption
`._ .. .. . .. I
`
`1 1 — — 1 1
`:
`decoding
`.. _. .. ._ .. I
`
`Figure 8.4: Payload bit processes.
`
`29 November 1999
`
`Trar:smitiReceive Routines
`
`AFFLT0293314
`
`Samsung Ex. 1019 p. 86
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 87 of 1082
`
`Baseband Specification
`
`9 TRANSMITIRECEIVE TIMING
`
`The Bluetooth transceiver applies a time-division duplex (TDD) scheme. This
`means that it altemately transmits and receives in a synchronous manner. It
`depends on the mode of the Bluetooth unit what the exact timing of the TDD
`scheme is. In the normal connection mode, the master transmission shat! always
`start at even numbered time siots (master Ci_K1=0) and the stave transmission
`shaft always start at odd numbered time slots (master Ci_K1=1). Due to packet
`types that cover more than a single slot, master transmission may continue in odd
`numbered slots and slave transmission may oontinue in even numbered slots.
`
`All timing diagrams shown in this chapter are based on the signals as present at
`the antenna. The term "exact" when used to describe timing refers to an ideal
`transmission or reception and neglects timing jitter and clock frequency imperfec-
`tions.
`
`The average timing of master packet transmission must not drift faster than
`20 ppm relative to the ideal slot timing of 625 ps. The instantaneous timing
`must not deviate more than 1 ps from the average timing. Thus, the absolute
`
`packet transmission timing I‘. of slot boundary .r’( must fulfill the equation:
`A
`
`F‘. = [Z0 iu’,.}T__V Ijk i oITsct,
`
`i=l
`
`(l-ZQ I)
`
`where TN is the nominal slot length (625 ps). I‘. denotesjitter (|;‘,_,| 5 I ps) at
`
`slot boundary ii’, and, dk, denotes the drift (ldkl 5 20 ppm) within slot i(. The jit-
`ter and drift may vary arbitrarily within the given limits for every slot, while “off-
`set" is an arbitrary but fixed constant. For hold. park and sniff mode the drift
`and jitter parameters as described in Link Mae-tsger F*i‘(}tCs-::£3i Eisction 3.9 on
`page
`apply.
`
`9.1 MASTERISLAVE TIMING SYNCHRONIZATION
`
`The piconet is synchronized by the system clock of the master. The master never
`adjusts its system ctock during the existence of the piconet: it keeps an exact inter-
`val of Mx625 us (where M is an even. positive integer larger than 0) between con-
`secutive transmissions. The slaves adapt their native clocks with a timing offset in
`order to match the master clock. This offset is updated each time a packet is
`received from the master: by comparing the exact RX timing of the received packet
`with the estimated RX timing, the staves correct the offset for any timing misalign-
`ments. Note that the slave RX timing can be corrected with any packet sent in the
`master-to-slave slot, since only the channei access code is required to synchronize
`the slave.
`
`The slave TX timing shall be based on the most recent slave RX timing. The RX
`timing is based on the latest successful trigger during a master-to-slave slot. For
`ACL links. this trigger must have occurred in the master-to-slave siot directly pre-
`
`TransmitiReceive 1”iming
`
`29 November 1999
`
`8?
`
`AFFLT0293315
`
`Samsung Ex. 1019 p. 87
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 88 of
`
`Baseband Specification
`
`Bluetooth-
`
`ceding the current slave transmission; for SCO links, the trigger may have
`occurred several master-to-slave slots before since a slave is allowed to send an
`
`SCO packet even if no packet was received in the preceding master-to-slave slot.
`The slave shall be able to receive the packets and adjust the RX timing as long as
`the timing mismatch remains within the ill} us uncertainty window.
`
`The master TX timing is strictly related to the master c|ock.The master shall keep
`an exact interval of Mx1250 us (where M is a positive integer larger than 0)
`between the start of successive transmissions; the RX timing is based on this TX
`timing with a shift of exactly Nx625 us (where N is an odd. positive integer larger
`than 0). During the master RX cycle, the master will also use the $101.1 uncertainty
`window to allow for slave misalignments. The master will adjust the RX processing
`of the considered packet accordingly, but will not adjust its RXITX timing for the fol-
`lowing TX and RX cycles.
`
`Timing behaviour may differ slightly depending on the current state of the unit.
`The different states are described in the next sections.
`
`9.2 CONNECTION STATE
`
`In the connection mode, the Bluetooth transceiver transmits and receives alter-
`
`on page 89. In the figures,
`$3 er: page 88 and Fig_3:_ire
`nately, see
`only single-slot packets are shown as an example. Depending on the type and
`the payload length, the packet size can be up to 366 ps. Each RX and TX
`transmission is at a different hop frequency. For multi-slot packets. several
`slots are covered by the same packet, and the hop frequency used in the first
`slot will be used throughout the transmission.
`
`RX slat
`
`hop g{2m+‘l)
`
`TX slot
`
`hop g{2m+2)
`
`5
`
`E
`
`t‘lCl|.rs
`
`Figure 9.1.’ RX/TX cycle of Bluetooth master transceiver in normal mode for single-slot
`packets.
`
`29 November 1999
`
`TransmitiReceiva ‘liming
`
`AFFLT0293316
`
`Samsung Ex. 1019 p. 88
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Baseband Specification
`
`page 89 of 1082
`
`Bluetooth
`
`TX slut
`
`hop g[2m+'i)
`
`RX slot
`
`h op g(2m + 2}
`
`Figure 9.2: RX’/TX cycie of Biueroofh siave transceiver in nonnai mode for single-siof packets.
`
`The master TX/RX timing is shown in Figure 9.1 on page SE5. In figures 9.1
`through 9.6, f(k) is used for the frequencies of the page hopping sequence and
`f(k) denotes the corresponding page response sequence frequencies. The
`channel hopping frequencies are indicated by g(m). After transmission, a return
`packet is expected Nx625 ps after the start of the TX burst where N is an odd,
`positive integer. N depends on the type of the transmitted packet. To allow for
`some time slipping, an uncertainty window is defined around the exact receive
`timing. During normal operation, the window length is 20 ps, which allows the
`RX burst to arrive up to 10 1.15 too early or 10 ps too late. During the beginning
`of the RX cycle, the access correlator searches for the correct channel access
`code over the uncertainty window. If no trigger event occurs, the receiver goes
`to sleep until the next RX event. If in the course of the search, it becomes
`apparent that the correlation output will never exceed the final threshold, the
`receiver may go to sleep earlier. If a trigger event does occur, the receiver
`remains open to receive the rest of the packet.
`
`The current master transmission is based on the previous master transmission:
`it is scheduled |Vlx1250ps after the start of the previous master TX burst where
`M depends on the transmitted and received packet type. Note that the master
`TX timing is not affected by time drifts in the slave(s). If no transmission takes
`place during a number of consecutive slots, the master will take the TX timing
`of the latest TX burst as reference.
`
`The s|ave's transmission is scheduled Nx625ps after the start of the s|ave's RX
`burst. If the slaves RX timing drifts, so will its TX timing. If no reception takes
`place during a number of consecutive slots, the slave will take the RX timing of
`the latest RX burst as reference.
`
`TransmitiReceive 1”iming
`
`29 November 1999
`
`AFFLT0293317
`
`Samsung Ex. 1019 p. 89
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Baseband Specification
`
`9.3 RETURN FROM HOLD MODE
`
`page 90 of
`
`Bluetooth-
`
`In the connection state, the Bluetooth unit can be placed in a hold mode, see
`Section ‘$9.85 on page ‘H2. In the hold mode, a Bluetooth transceiver neither
`transmits nor receives information. When returning to the normal operation
`after a hold mode in a slave Bluetooth unit, the slave must listen for the master
`before it may send information. In that case, the search window in the slave
`unit may be increased from ill} us to a larger value X us as illustrated in §i‘ig-are
`on
`90. Note that only RX hop frequencies are used: the hop fre-
`quency used in the master-to—s|ave (RX) slot is also used in the uncertainty
`window extended into the preceding time interval normally used for the slave-
`to-master (TX) slot.
`
`If the search window exceeds 625 us, consecutive windows shall not be cen-
`tered at the start of RX hops g(2m), g(2m+2),
`g(2m+2i) (where ‘i’ is an inte-
`ger), but at g(2m), g(2m+4),
`g(2m+4i), or even at g(2m), g(2m+6],
`...g(2m+6i) etc. to avoid overlapping search windows. The RX hop frequencies
`used shall correspond to the RX slot numbers.
`
`It is recommended that single slot packets are used upon return from hold to
`minimize the synchronization time, especially after long hold periods that
`require search windows exceeding 625 us.
`
`Estimated start of master TX
`
`hop g[2m+2}
`
`Figure 9.3: RX timing of stave returning from hoid state.
`
`9.4 PARK MODE WAKE-UP
`
`The park mode is similar to the hold mode. A parked slave periodically wakes
`up to listen to beacons from the master and to re-synchronize its clock offset.
`As in the return from hold mode. a parked slave when waking up may increase
`the search window from ill) us to a larger value X us as illustrated in Figure
`3.24: on :3-age tit‘).
`
`29 November 1999
`
`TransmitiReceivs ‘firming
`
`AFFLT029331B
`
`Samsung Ex. 1019 p. 90
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 91 of 1082
`
`Baseband Specification
`
`9.5 PAGE STATE
`
`In the page state. the master transmits the device access code (ID packet) cor-
`responding to the stave to be connected, rapidly on a large number of different
`hop frequencies. Since the ID packet is a very short packet, the hop rate can
`be increased from 1600 hopsis to 3200 hopsis. In a single TX slot interval, the
`paging master transmits on two different hop frequencies. In a single RX slot
`interval, the paging transceiver listens on two different hop frequencies; see
`Figgtire
`on page at. During the TX slot, the paging unit sends an ID packet
`at the TX hop frequencies f(k) and iik-I-1). In the RX slot, it listens for a
`response on the corresponding RX hop frequencies f’(k) and f’(k+1). The lis-
`tening periods are exactly timed 625 ps after the corresponding paging pack-
`ets, and include a iii} ps uncertainty window.
`
`TX slot
`
`RX slot
`
`TX slot
`
`I I
`
`I
`hcip rm
`
`hop f{k+1)
`
`hop f‘(k+1]
`
`he
`
`EI
`I
`
`E6Bps
`
`E...............
`
`
`
`E'.'.'.'.'.‘ZZ'.'.'.‘2I'.'.'.'
`
`f(k+2)
`
`hop f(k+3}
`
`____;D_____
`
`Figure 9.4: RX/TX cycie of Biuetooth transceiver in PAGE mode.
`
`9.6 FHS PACKET
`
`At connection setup and during a master-slave switch, an FHS packet is trans-
`ferred from the master to the slave. This packet will establish the timing and
`frequency synchronization (see also Section -4.4.1.4 on page 58). After the
`slave unit has received the page message, it will return a response message
`which again consists of the ID packet and follows exactly 625 ps after the
`receipt of the page message. The master will send the FHS packet in the TX
`slot following the RX slot in which it received the slave response, according the
`RXJTX timing of the master. The time difference between the response and
`FHS message will depend on the timing of the page message the slave
`received. In Figure 54.5 an 5.:-age $32, the slave receives the paging message
`sent first in the master-to-slave slot. It will then respond with an ID packet in
`the first half of the slave-to-master slot. The timing of the FHS packet is based
`on the timing of the page message sent first in the preceding master-to-slave
`slot: there is an exact 1250 ps deiay between the first page message and the
`FHS packet. The packet is sent at the hop frequency f(k+1) which is the hop
`frequency foilowing the hop frequency f(ir) the page message was received in.
`In Ftgtire $3.8 on
`{$2, the slave receives the paging message sent sec-
`ondly in the master-to-slave slot. It will then respond with an ID packet in the
`
`TransmiUReceive 1”iming
`
`29 November ‘I999
`
`AFFLT0293319
`
`Samsung Ex. 1019 p. 91
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 92 of ‘I832
`
`Baseband Specification
`
`Bluetooth-
`
`second half of the slave-to-master slot exactly 625 as after the receipt of the
`page message. The timing of the FHS packet is still based on the timing of the
`page message sent first in the preceding master-to-slave slot: there is an
`exact 1250 3.13 delay between the firs’: page message and the FHS packet. The
`packet is sent at the hop frequency f(k+2) which is the hop frequency following
`the hop frequency f(i<+1) the page message was received in.
`
`mater-to-slave slot
`
`hop f[k+1}
`
`I
`I
`l
`
`mfp me)
`I
`
`I
`I
`I
`
`ho]: t‘{k}
`II
`
`slave-to-I11asler slat
`
`rnasIer—loalave slot
`
`hop 'f[k+1}
`
`Figure 9.5: Timing of FHS packet on successfui page in first haif sioi‘.
`
`master-to-slave slot
`
`I
`I
`I
`
`hclp ttk}
`I
`
`hop flk-I-1}:
`
`;I
`
`E68115
`
`I
`I
`I
`
`niup rm
`II
`
`slave-to-master slot
`
`master-to-slave slot
`
`hop f‘(K+1}
`
`hop rII<+2}
`
`_________E__.I______________3:1 ii
`
`Figure 9.6: Timing of FHS packet on successiui page in second haif sic.-t.
`
`29 November 1999
`
`TransmitiReceive '|'im‘Ing
`
`AFFLT0293320
`
`Samsung Ex. 1019 p. 92
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 93 of 1082
`
`Base-band Specification
`
`The stave will adjust its RXITX timing according to the reception of the FHS
`packet (and not according to the reception of the page message). That is, the
`second response message that acknowledges the reception ofthe FHS packet
`is transmitted 625 ps after the start of the FHS packet.
`
`9.7 MULTI-SLAVE OPERATION
`
`As was mentioned in the beginning of this chapter, the master always starts the
`transmission in the even-numbered slots whereas the slaves start their trans-
`
`mission in the odd-numbered slots. This means that the timing of the master
`and the s|ave(s) is shifted by one slot (625 us), see F5-gore
`on page 933.
`
`Only the slave that is addressed by its AM_ADDR can return a packet in the
`next slave-to-master slot. If no valid AM_ADDR is received, the slave may only
`respond if it concerns its reserved SCO slave-to-master slot. In case of a
`broadcast message, no slave is allowed to return a packet (an exception is
`found in the access window for access requests in the park mode, see é3e=:;i§o:'i
`t{}.E3.»'i- on page TE5).
`
`Figure 9. 7.’ RX/TX timing in muiti-stave configuration
`
`TransmiUReceive filming
`
`29 November 1999
`
`AFFLT0293321
`
`Samsung Ex. 1019 p. 93
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Baseband Specification
`
`29 November 1999
`
`Transmitmeceive '|'|ming
`
`AFFLT0293322
`
`Samsung Ex. 1019 p. 94
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 95 of 1082
`
`Base-band Specification
`
`10 CHAN N EL CONTROL
`
`10.1 SCOPE
`
`This section describes how the channel of a piconet is established and how
`units can be added to and released from the piconet. Several states of opera-
`tion of the Bluetooth units are defined to support these functions. In addition,
`the operation of severai piconets sharing the same area, the so-called scatter-
`net, is discussed. A special section is attributed to the Bluetooth clock which
`plays a major role in the FH synchronization.
`
`10.2 MASTER-SLAVE DEFINITION
`
`The channel in the pioonet is characterized entirely by the master of the picc-
`net. The Bluetooth device address (BD_ADDR) of the master determines the
`FH hopping sequence and the channel access code; the system clock of the
`master determines the phase in the hopping sequence and sets the timing. In
`addition, the master controls the traffic on the channel by a polling scheme.
`
`By definition, the master is represented by the Bluetooth unit that initiates the
`connection (to one or more slave units). Note that the names ‘master' and
`‘slave’ only refer to the protocol on the channel: the Bluetooth units themselves
`are identical; that is, any unit can become a master of a piconet. Once a picc-
`net has been established, master-slave roles can be exchanged. This is
`described in more detail in ffisctiort 13.9.3 on
`‘€23.
`
`10.3 BLUETOOTH CLOCK
`
`Every Bluetooth unit has an internal system clock which determines the timing
`and hopping of the transceiver. The Bluetooth clock is derived from a free run-
`ning native clock which is never adjusted and is never turned off. For synchro-
`nization with other units, only offsets are used that, added to the native clock,
`provide temporary Bluetooth clocks which are mutually synchronized. It should
`be noted that the Bluetooth clock has no relation to the time of day; it can there-
`fore be initialized at any value. The Bluetooth clock provides the heart beat of
`the Bluetooth transceiver. Its resolution is at least half the TX or RX slot length,
`or 312.5 us. The clock has a cycle of about a day. If the clock is implemented
`with a counter, a 28-bit counter is required that wraps around at 223-1. The LSB
`ticks in units of 312.5 us, giving a clock rate of 3.2 kHz.
`
`The timing and the frequency hopping on the channet of a piconet is deter-
`mined by the Bluetooth clock of the master. When the piconet is established,
`the master ciock is communicated to the slaves. Each slave adds an offset to
`
`its native clock to be synchronized to the master clock. Since the clocks are
`free-running, the offsets have to be updated reguiarly.
`
`Channel Control
`
`29 November 1999
`
`AFFLT0293323
`
`Samsung Ex. 1019 p. 95
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 96 of €882
`
`Baseband Specification
`
`Bluetooth-
`
`The clock determines critical periods and triggers the events in the Bluetooth
`receiver. Four periods are important in the Bluetooth system: 312.5 us, 625 ps,
`1.25 ms, and 1.28 s; these periods correspond to the timer bits CLK0, CLK1,
`
`CLK2, and CLK12, respectively, see
`
`‘t{3.‘i -on page 95. Master-to-slave
`
`transmission starts at the even-numbered slots when CLK0 and CLK1 are both
`zero.
`
`IEIEIEIEIIIHIIHEIIIEI
`
`Figure 10.1: Biuetooth ciock.
`
`In the different modes and states a Bluetooth unit can reside in, the clock has
`
`different appearances:
`
`- CLKN
`
`- CLKE
`
`native ctock
`
`estimated clock
`
`- CLK
`
`master clock
`
`CLKN is the free-running native clock and is the reference to all other clock
`appearances. In states with high activity, the native clock is driven by the refer-
`ence crystal oscillator with worst case accuracy of +i-20ppm. In the low power
`states, like STANDBY, HOLD, PARK, the native clock may be driven by a low
`power oscillator (LPO) with relaxed accuracy (+i-250ppm).
`
`CLKE and CLK are derived from the reference CLKN by adding an offset.
`CLKE is a clock estimate a paging unit makes of the native clock of the recipi-
`ent; i.e. an offset is added to the CLKN of the pager to approximate the CLKN
`of the recipient, see f~"ig=.sre “l=’.':.:l_* on page ‘Eu’. By using the CLKN of the recipi-
`ent, the pager speeds up the connection establishment.
`
`CLK is the master clock of the piconet. It is used for all timing and scheduling
`activities in the piconet. All Bluetooth devices use the CLK to schedule their
`transmission and reception. The CLK is derived from the native clock CLKN by
`adding an offset, see 5-Tigture 30.3 on page 9?‘. The offset is zero for the master
`since CLK is identical to its own native clock CLKN. Each slave adds an appro-
`priate offset to its CLKN such that the CLK corresponds to the CLKN of the
`master. Although all CLKNS in the Bluetooth devices run at the same nominal
`rate, mutual drift causes inaccuracies in CLK. Therefore, the offsets in the
`
`slaves must be regulariy updated such that CLK is approximately CLKN of the
`master.
`
`29 November 1999
`
`Channei Control
`
`AFFLT0293324
`
`Samsung Ex. 1019 p. 96
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Baseband Specification
`
`page 97 of 1082
`
`Bluetooth.
`
`CLKE = CLKN (recipient)
`
`Estimated offset
`
`Figure 10.2.’ Derivation of CLKE
`
`CLKN(master)
`
`CLK
`
`CLKN{s|a\re)
`
`Figure 10.3.’ Derivation of CLK in master (a) and in slave (b).
`
`10.4 OVERVIEW OF STATES
`
`3‘-':gure 153.4 or: sage 98 shows a state diagram illustrating the different states
`used in the Bluetooth link controller. There are two major states: STANDBY
`and CONNECTION; in addition, there are seven substates. page, page scan,
`inquiry, inquiry scan, master response, slave response, and inquiry
`response. The substates are interim states that are used to add new slaves to
`a piconet. To move from one state to the other, either commands from the Blue-
`tooth link manager are used, or internal signals in the link controller are used
`(such as the trigger signal from the correlator and the timeout signals).
`
`Channel Control
`
`29 November 1999
`
`AFFLT0293325
`
`Samsung Ex. 1019 p. 97
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 98 of €882
`
`Baseband Specification
`
`Bluetooth-
`
`master
`response
`
`slave
`response
`
`inq u iry
`response
`
`Figure 10.4: State diagram of Biuetooth iink controller.
`
`10.5 STANDBY STATE
`
`The STANDBY state is the default state in the Bluetooth unit. In this state, the
`
`Bluetooth unit is in a low-power mode. Only the native clock is running at the
`accuracy of the LPO (or better).
`
`The controller may leave the STANDBY state to scan for page or inquiry mes-
`sages, or to page or inquiry itself. When responding to a page message, the
`unit will not return to the STANDBY state but enter the CONNECTION state as
`
`a slave. When carrying out a successful page attempt, the unit will enter the
`CONNECTION state as a master. The intervals with which Scan activities can
`
`be carried out are discussed in Siersti-on.
`Gt‘:
`1033.
`
`on page
`
`and 53s::tir:an 1G.?‘.2
`
`29 November 1999
`
`Channel Control
`
`AFFLT0293326
`
`Samsung Ex. 1019 p. 98
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 99 of 1082
`
`Baseband Specification
`
`10.6 ACCESS PROCEDURES
`
`10.6.1 General
`
`In order to establish new connections the procedures inquiry and paging are
`used. The inquiry procedure enables a unit to discover which units are in
`range, and what their device addresses and ciocks are. With the paging proce-
`dure, an actual connection can be established. Only the Bluetooth device
`address is required to set up a connection. Knowledge about the clock will
`accelerate the setup procedure. A unit that establishes a connection will carry
`out a page procedure and will automatically be the master of the connection.
`
`In the paging and inquiry procedures, the device access code (DAC) and the
`inquiry access code (IAC) are used, respectively. A unit in the page scan or
`inquiry scan substate correlates against these respective access codes with a
`matching correlator.
`
`For the paging process, several paging schemes can be applied. There is one
`mandatory paging scheme which has to be supported by each Bluetooth
`device. This mandatory scheme is used when units meet for the first time, and
`in case the paging process directly follows the inquiry process. Two units, once
`connected using a mandatory pagingiscanning scheme, may agree on an
`optional paging.-‘scanning scheme. Optional paging schemes are discussed in
`“Ap;.ien~:ii.x \«’ii''’ on page
`In the current chapter, only the mandatory paging
`scheme is considered.
`
`10.6.2 Page scan
`
`In the page scan substate, a unit listens for its own device access code for the
`duration of the scan window Tw page Scan. During the scan window, the unit lis-
`tens at a single hop frequency, its correlator matched to its device access
`code. The scan window shall be long enough to completely scan 16 page fre-
`quencies.
`
`When a unit enters the page scan substate, it selects the scan frequency
`according to the page hopping sequence corresponding to this unit, see Sec-
`tion ’i’i.3.'i on page ‘$35. This is a 32-hop sequence (or a 16-hop sequence in
`case ofa reduced-hop system) in which each hop frequency is unique. The
`page hopping sequence is determined by the unit's Bluetooth device address
`(BD_ADDR). The phase in the sequence is determined by CLKN1542 of the
`
`unit’s native clock (CLKN1542 in case of a reduced-hop system); that is, every
`1.288 a different frequency is selected.
`
`If the correlator exceeds the trigger threshold during the page scan, the unit
`will enter the slave response substate, which is described in E3-:-ectitsn t{}.£:i.4t.1
`on page ‘€055.
`
`Channel Control
`
`29 November 1999
`
`AFFLT0293327
`
`Samsung Ex. 1019 p. 99
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 100 of
`
`Baseband Specification
`
`Bluetooth-
`
`The page scan substate can be entered from the STANDBY state or the CON-
`NECTION state. in the STANDBY state, no connection has been established
`
`and the unit can use all the capacity to carry out the page scan. Before enter-
`ing the page scan substate from the CONNECTION state, the unit preferably
`reserves as much capacity for scanning. If desired, the unit may place ACL
`connections in the HOLD mode or even use the PARK mode. see Siection
`
`‘$08.3 on page we and Eéscticn 38.8.4 on page ‘t’ti:'s. SCO connections are
`preferably not interrupted by the page scan. In this case, the page scan may
`be interrupted by the reserved SCO slots which have higher priority than the
`page scan. SCO packets should be used requiring the least amount of capac—
`ity (HV3 packets). The scan window shall be increased to minimize the setup
`delay. If one SCO link is present using HV3 packets and T3C0=6 slots, a total
`
`scan window Tw page scan of at least 36 slots (22.5ms) is recommended; if two
`SCO links are present using HV3 packets and T3CO=6 slots, a total scan win-
`dow of at least 54 slots (33.75ms) is recommended.
`
`The scan interval Tpage Scan is defined as the interval between the beginnings
`of two consecutive page scans. A distinction is made between the case where
`the scan interval is equal to the scan window Tw page scan (continuous scan),
`the scan interval is maximal 1.283, or the scan interval is maximal 2.563. These
`
`three cases determine the behavior of the paging unit; that is, whether the pag~
`ing unit shall use R0, R1 or R2, see also Secténn ’il}.§.3 en page 101.
`Tatsie €03?
`illustrates the relationship between Tpage Scan and modes R0, R1
`and R2. Although scanning in the R0 mode is continuous, the scanning may be
`interrupted by for example reserved SCO slots. The scan interval information is
`included in the SR field in the FHS packet.
`
`29 November 1999
`
`Channsf Control
`
`AFFLT029332B
`
`Samsung Ex. 1019 p. 100
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 101 of 1082
`
`Baseband Specification
`
`During page scan the Bluetooth unit may choose to use an optional scanning
`scheme. (An exception is the page scan after returning an inquiry response
`message. See Section ‘i0.?’.»=i on page ttt for details.)
`
`1-page scan
`contin uous
`
`s 1 .285
`
`5 2.565
`
`Table 10. 1: Reiarionship between scan interval, (rain repetition, and paging modes R0, R’! and R2.
`
`10.6.3 Page
`
`The page substate is used by the master (source) to activate and connect to a
`slave (destination) which periodically wakes up in the page scan substate. The
`master tries to capture the slave by repeatedly transmitting the s|ave's device
`access code (DAG) in different hop channels. Since the Bluetooth clocks of the
`master and the slave are not synchronized, the master does not know exactly
`when the stave wakes up and on which hop frequency. Therefore, it transmits a
`train of identical DACs at different hop frequencies, and listens in between the
`transmit intervals until it receives a response from the slave.
`
`The page procedure in the master consists of a number of steps. First, the
`s|ave's device address is used to determine the page hopping sequence, see
`Section 11
`on page ‘:35. This is the sequence the master will use to reach
`the slave. For the phase in the sequence, the master uses an estimate of the
`s|ave's clock. This estimate can for example be derived from timing information
`that was exchanged during the last encounter with this particular device (which
`could have acted as a master at that time), or from an inquiry procedure. With
`this estimate CLKE of the s|ave's Bluetooth clock, the master can predict when
`the slave wakes up and on which hop channel.
`
`The estimate of the Bluetooth clock in the slave can be completely wrong.
`Although the master and the slave use the same hopping sequence, they use
`different phases in the sequence and will never meet each other. To compen-
`sate for the clock drifts, the master will send its page message during a short
`time interval on a number of wake-up frequencies. It will in fact transmit also on
`hop frequenciesjust before and after the current, predicted hop frequency.
`During each TX slot, the master sequentially transmits on two different hop fre-
`quencies. Since the page message is the ID packet which is only 68 bits in
`length, there is ample of time (224.5 ps minimal) to switch the synthesizer. In
`the following RX slot, the receiver will listen sequentially to two corresponding
`RX hops for ID packet. The RX hops are selected according to the
`page_response hopping sequence. The page_response hopping sequence is
`strictly related to the page hopping sequence; that is: for each page hop there
`is a corresponding page_response hop. The RXiTX timing in the page sub-
`
`Channel Control
`
`29 November 1999
`
`AFFLT0293329
`
`Samsung Ex. 1019 p. 101
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 102 of
`
`Baseband Specification
`
`Bluetooth-
`
`state has been described in Section 9, see also Figure 9.4 on page 91. In the
`next TX slot, it will transmit on two hop frequencies different from the former
`ones. The synthesizer hop rate is increased to 3200 hopsis.
`
`A distinction must be made between the 79-hop systems and the 23-hop sys-
`tems. First the 79-hop systems are considered. With the increased hopping
`rate as described above, the transmitter can cover 16 different hop frequencies
`in 16 slots or 10 ms. The page hopping sequence is divided over two paging
`trains A and B of 16 frequencies. Train A includes the 18 hop frequencies sur-
`rounding the current, predicted hop frequency f(k}, where k is determined by
`the clock estimate CLKE1342. So the first train consists of hops
`
`f(k-8), f(k-?),...,f(k)....,f(k+7)
`
`When the difference between the Bluetooth clocks of the master and the slave
`
`is between ~8x1.28 s and +7x1.28 s, one of the frequencies used by the master
`will be the hop frequency the siave will listen to. However, since the master
`does not know when the slave will enter the page scan substate, he has to
`repeat this train A Npage times or until a response is obtained. If the slave scan
`interval corresponds to R1, the repetition number is at least 128; if the slave
`scan interval corresponds to R2, the repetition number is at least 256.
`Note that CLKE1542 changes every 1.28 s; therefore, every 1.28 s, the trains
`will include different frequencies of the page hopping set.
`
`When the difference between the Bluetooth clocks of the master and the slave
`
`is less than -8x1.28 s or larger than +7x1.28 s, more distant hops must be
`probed. Since in total, there are only 32 dedicated wake-up hops, the more dis-
`tant hops are the remaining hops not being probed yet. The remaining 16 hops
`are used to form the new 10 ms train B. The second train consists of hops
`
`f(k-16), f(k-15),....f(k-9),f(k+8)...,f(k+15)
`
`Train B is repeated for Npage times. If still no response is obtained, the first train
`A is tried again Npage times. Alternate use of train A and train B is continued
`until a response is received or the timeout pageTO is exceeded. If during one
`of the listening occasions, a response is returned by the slave, the master unit
`enters the master response substate.
`
`The description for paging and page scan procedures given here has been tai-
`Iored towards the 79-hop systems used in the US and Europe. For the 23-hop
`systems as used in Japan and