BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 861 of 1082
`
`Host Controiier interface Functional Specification
`
`uetooth.
`
`4.7.41 Host_Buffer_Size
`
`Parameters
`
`HCl_Host_B uffer_Size
`
`Host_AC L_ Data_Pa cket_ Length .
`
`Host_SCO_Data_Pa cl<et_Length.
`
`Host_Tota|_N u m_AC L_Data_ Pac kets,
`
`Host_Tota|_N u m_SC O_Data_Pac kets
`
`Description:
`
`The Host_Buffer_Si2e command is used by the Host to notify the Host Control-
`ler about the maximum size of the data portion of HCI ACL and SCO Data
`Packets sent from the Host Controller to the Host. The Host Controller will seg-
`ment the data to be transmitted from the Host Controller to the Host according
`to these sizes, so that the HCI Data Packets will contain data with up to these
`sizes. The Host_Buffer_Size command also notifies the Host Controtler about
`the total number of HCI ACL and SCO Data Packets that can be stored in the
`data buffers of the Host. If flow control from the Host Controller to the Host is
`
`turned off, and the Host_Buffer_Size command has not been issued by the
`Host, this means that the Host Controller will send HCI Data Packets to the
`
`Host with any lengths the Host Controller wants to use. and it is assumed that
`the data buffer sizes of the Host are unlimited. If flow control from the Host con-
`
`troller to the Host is turned on. the Host_Buffer_Size command must after a
`power-on or a reset always be sent by the Host before the first
`Host_Number_Of_Comp|eted_Packets command is sent.
`
`(The ESet_“_t-tost“_Controiierwffowt-tcst‘__F1cwwCar:te'oi command is used to turn
`flow control on or off.) The Host_ACL_Data_Packet_Length command param-
`eter will be used to determine the size of the LZCAP segments contained in
`ACL Data Packets, which are transferred from the Host Controller to the Host.
`
`The Host_SCO_Data_Packet_Length command parameter is used to deter-
`mine the maximum size of HCI SCO Data Packets. Both the Host and the Host
`
`Controller must support command and event packets. where the data portion
`(excluding header) contained in the packets is 255 bytes in size.
`
`The Host_Total_Num_ACL_Data_Packets command parameter contains the
`total number of HCI ACL Data Packets that can be stored in the data buffers of
`the Host. The Host Controller will determine how the buffers are to be divided
`
`between difierent Connection Handles. The Host_Tota|_Num_SCO_Data_
`Packets command parameter gives the same information for HCI SCO Data
`Packets.
`
`Note: the Host_ACL_Data_Packet_Length and Host_SCO_Data_Packet_
`Length command parameters do not include the length of the HCI Data Packet
`headen
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293889
`
`Samsung Ex. 1019 p. 661
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Controiter interface Functional Specification
`
`Command Parameters:
`
`page 662 of 3882
`
`Bluetooth-
`
`Host_A Ci___Data_Packet_t_ength:
`
`Size: 2 Bytes
`
`Parameter Description
`
`Maximum length (in bytes) of the data portion of each HCI ACL Data
`Packet that the Host is able to accept.
`
`Host_SCO_Data_F’acket_i_ength.'
`
`Size: 1 Byte
`
`Parameter Description
`
`Maximum length (in bytes) of the data portion of each HCI SCO Data
`Packet that the Host is able to accept.
`
`Host_ Totai_Num_A Ci__Data_Packets:
`
`Size: 2 Bytes
`
`Parameter Description
`
`Total number of HCI ACL Data Packets that can be stored in the data
`buffers of the Host.
`
`Host_ Tota.-'_Num_SCO_Data_F-'ackets:
`
`Size: 2 Bytes
`
`Parameter Description
`
`Total number of HCI SCO Data Packets that can be stored in the data
`buffers of the Host.
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Host_Buffer_Size command succeeded.
`
`Size: 1 Byte
`
`0x01-OXFF
`
`Host_Buffer_Size command faited. See Tataie
`Error Codes.
`
`on cage "M5 for list of
`
`Event(s) generated (unless masked away):
`
`When the Host_Buffer_Size command has completed, a Command Complete
`event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293890
`
`Samsung Ex. 1019 p. 662
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 863 of 1082
`
`Host Controiier interface Functional Specification
`
`uetooth.
`
`4.7.42 Host_Number_Of_Comp|eted_Packets
`
`Command
`
`Command Parameters
`
`RemmParameters
`
`HCl_Host_Number_0f_
`Comp|eted_Packets
`
`0x0035 Number_0f_Hand|es.Connection_
`Handlem
`Host_Num_Of_Comp|eted_Pacl(ets [i]
`
`Description:
`
`The Host_Number_Of_Comp|eted_Packets command is used by the Host to
`indicate to the Host Controller the number of HCI Data Packets that have been
`
`completed for each Connection Handle since the previous Host_Number_Of_
`Comp|eted_Buffers command was sent to the Host Controiler. This means that
`the corresponding buffer space has been freed in the Host. Based on this infor-
`mation, and the Host_Tota|_Num__ACL_Data__Packets and HostflTotal_Num_
`SCO_Data_Packets command parameters of the Host_Buffer_Size command,
`the Host Controller can determine for which Connection Handles the following
`HCI Data Packets should be sent to the Host. The command should only be
`issued by the Host if flow control in the direction from the Host Controller to the
`Host is on and there is at least one connection. or if the Host Controller is in
`local loopback mode. Otherwise, the command will be ignored by the Host
`Controller. While the Host has HCI Data Packets in its buffers. it must keep
`sending the Host_Number_Of_Comp|eted_Packets command to the Host
`Controller at least periodically, until itfinally reports that all buffer space in the
`Host used by ACL Data Packets has been freed. The rate with which this com-
`mand is sent is manufacturer specific.
`
`(The S3et___i~lost____Conts'c:lis:'____To____%-tcst____Flow____Control command is used to turn
`flow control on or off.) If flow control from the Host controller to the Host is
`turned on. the l-lost_Buffer_Size command must after a power-on or a reset
`always be sent by the Host before the first
`Host_Number_0f_Comp|eteci_Packets command is sent.
`Note: the Host_Number_Of_Comp|eted_Packets command is a special com-
`mand En the sense that no event is normally generated after the command has
`completed. The command may be sent at any time by the Host when there is at
`least one connection, or if the Host Controller is in local loopback mode inde-
`pendent of other commands. The normal flow control for commands is not
`used for the Host_Number_Of_Comp|eted_Packets command.
`
`|
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293891
`
`Samsung Ex. 1019 p. 663
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Controiier interface Functionat Specification
`
`Command Parameters:
`
`n
`page 684 of tut-32
`
`Bluetooth-
`
`Number_Of_Handles:
`
`Size: 1 Byte
`
`Parameter Description
`
`The number of Connection Handles and Host_Num_Of_Completed_Packets
`parameters pairs contained in this command.
`
`Range: 0-255
`
`Connection_Hano‘ie[i].' Size: Number_ Of_Hano'ies*2 Bytes (12 Bits meaningful)
`
`Parameter Description
`
`Connection Handle
`
`Range: UXUUUU-UXUEFF {UXUFUU - 0x0FFF Reserved for future use}
`
`Host_Num_OLCompieted_Packets [i]:
`
`Size: Number_Of_Handles * 2 Bytes
`
`Parameter Description
`
`N = UXXXXX
`
`The number of HCI Data Packets that have been completed for the asso-
`ciated Connection Handle since the previous time the event was returned.
`
`Range for N: UXUUUU-OXFFFF
`
`Return Parameters:
`
`None.
`
`Event(s) generated (unless masked away):
`
`Normally, no event is generated after the Host_Number_Of_Comp|eted_
`Packets command has completed. However. if the Host_Number_Of_
`Comp|eted_Packets command contains one or more invalid parameters, the
`Host Controller will return a Command Complete event with a failure status
`indicating the Invalid HCI Command Parameters error code. The Host may
`send the Host_Nurnber_Of_Completed_Packets command at any time when
`there is at least one connection, or if the Host Controller is in local loopback
`mode. The normal flow control for commands is not used for this command.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293892
`
`Samsung Ex. 1019 p. 664
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Host Controiier interface Functional Specification
`
`4.7.43 Read_Link_Supervision_Timeout
`
`page 865 of 1082
`
`Bluetooth.
`
`Command
`
`command
`Parameters
`
`Return Parameters
`
`HCl_Read_Link_Supervision_
`Timeout
`
`Connecticn_HandEe
`
`Status,
`Connection Handle
`
`Link_Supervision_
`Timeout
`
`Description:
`
`This command will read the value for the Link_Supervision_'Fmeout parameter
`for the device. The Link_Supervisicn_Timeout parameter is used by the master
`or slave Bluetooth device to monitor link loss. If, for any reason. no Baseband
`packets are received from that Connection Handle for a duration longer than
`the Link_Supervision_Timeout, the connection is disconnected. The same
`timeout value is used for both S00 and ACL connections for the device speci-
`fied by the Connection Handle.
`Note: the C0nnection_Hand|e used for this command must be the ACL con-
`nection to the appropriate device. This command will set the Link_Supervision_
`'|"|meout values for other SCO Connection_Hand|e to that device.
`
`Note: Setting the Link_Supervision_'Fmeout to No Link_Supervision_Timeout
`(OXOOOO) will disable the Link_Supervision_Timeout check for the specified
`Connection Handle. This makes it unnecessary for the master of the piconet to
`unpark and then park each Bluetooth Device every -40 seconds. By using the
`No Link_Supervision_‘Fmeout setting, the scalability of the Park mode is not
`limited.
`
`Command Parameters:
`
`Connection_i-iandie:
`
`Size: 2 Bytes (‘i2 Bits meaningfui)
`
`Parameter Description
`
`Specifies which Connection Handles Link Supervision Timeout value is to
`be read.
`
`Range: OXDOOO-OXDEFF (OXOFOO - UXDFFF Reserved for future use}
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Read_Link_Supervision_Timeout command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Read__Lin|<_SupervisionWTimeout command failed. See Yabie
`'.?’zi:": for list of Error Codes.
`
`ore page
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293893
`
`Samsung Ex. 1019 p. 665
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 666 of 3082
`
`Host Coniroiier interface Funciionai Specification
`
`Bluetooth-
`
`Conneci‘ion_Handie:
`
`Size: 2 Bytes (12 Bits meaningfui)
`
`Parameter Description
`
`Specifies which Connection Hand|e‘s Link Supervision '|'1meout vaiue was
`read.
`
`Range: UXUUUU-UXOEFF {OXOFUU - UXUFFF Reserved for future use)
`
`i_ini<_Supervision_ Timeout:
` Parameter Description
`OXOODO
`No Link_Super\iision_Timeout.
`N 2 DXXXXX
`Measured in Number of Baseband slots
`
`Size: 2 Bytes
`
`Lini<_Supervision_Tirneoui = N * 0.625 msec(1 Baseband slot)
`Range for N: UXUUU1 — 0xFFFF
`
`‘Fme Range: 0.625ms - 40.9 sec
`
`Event(s) generated (unless masked away):
`
`When the Read_Link_Supervision_Timeout command has completed, a Com-
`mand Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293894
`
`Samsung Ex. 1019 p. 666
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 867 of 1082
`
`Host Controiier interface Functional Specification
`
`4.7.44 Write Link_Supervision_Timeout
`
`Bluetooth.
`
`Command
`
`Command Parameters Return Parameters
`
`HCl_Write_Link_Supervision_
`Timeout
`
`Connectlon_Handle.
`
`Status .
`
`Link_Supervision_
`Timeout
`
`Con r1ection_Har1dIe
`
`Description:
`
`This command will write the value for the Link_Supervision_Timeout parameter
`for the device. The Lini<_Supervision_Timeout parameter is used by the master
`or slave Bluetooth device to monitor kink loss. If. for any reason. no Baseband
`packets are received from that Connection_Hand|e for a duration longer than
`the Lini<_Supervision_Timeout, the connection is disconnected. The same
`timeout value is used for both SCO and AOL connections for the device speci-
`fied by the Connection_Hand|e.
`Note: the Connection_Hand|e used for this command must be the ACL con-
`nection to the appropriate device. This command will set the Link_Supervision_
`Timeout values for other SCO C0nnection_Hand|e to that device.
`Note: Setting the l_ink_Supervision_Trmeout parameter to No Link_
`Supervision_Timeout (0x0{}00) will disable the Link_Supervision_Timeout
`check for the specified Connection Handle. This makes it unnecessary for the
`master of the piconet to unpark and then park each Bluetooth Device every
`-40 seconds. By using the No Linl<_Supervision_'|'Imeout setting, the scalabil-
`ity of the Park mode is not limited.
`
`Command Parameters:
`
`Connection_Handie.'
`
`Size: 2 Bytes (12 Bits meaningful‘)
`
`Value
`
`UXXXXX
`
`i Parameter Description
`
`Specifies which Connection Handie‘s Link Supervision Timeout value is to
`be written.
`
`Range: OXUUUU-UXUEFF (UXUFUU - UXCIFFF Reserved for future use}
`
`i_ini<_Supervision_ Timeout.‘
`
`Size.‘ 2 Bytes
`
`Value
`
`OXUUOU
`
`Parameter Description
`
`No Linl<_Su pervisionwTi meout.
`
`N = UXXXXX
`
`Measured in Number of Elaseband slots
`
`Link_Supervislon_Timeout = N*0.625 msec (1 Baseband slot}
`
`Range for N: OXUUU1 - OXFFFF
`
`Time Range: 0.625ms -40.9 sec
`Default: N = OXTDOO
`
`Link_Supervision_Tlmeout = 20 sec
`
`HCI Commands
`
`29 November ‘T999
`
`AFFLT0293895
`
`Samsung Ex. 1019 p. 667
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Controiier interface Functionai Specification
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Write_Lini<_Supervision_Timeout command succeeded.
`
`page 668 of ms:
`
`Bluetooth-
`
`Size.‘ 1' Byte
`
`0x01-0xFF
`
`Write_Lini<_Supervisicn_Timecut command failed. See ‘E’.-2si:>{e
`Mfii for list of Error Codes.
`
`.1 on page
`
`Connection_Handie.'
`
`Size: 2 Bytes (12 Bits meaningful)
`
`Value
`
`Parameter Description
`
`Specifies which Connection Handle‘s Link Supervision Timeout value was
`written.
`
`Range: UXUUUU-UXOEFF (OXOFUU - UXOFFF Reserved for future use}
`
`Event(s) generated (unless masked away):
`
`When the Write_Link_Supervision_Timeout command has completed, a
`Command Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293896
`
`Samsung Ex. 1019 p. 668
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 669 of 1082
`
`Host Coniroiier interface Functional Specification
`
`uetooth.
`
`4.7.45 Read_Number_Of_Supported_|AC
`
`command
`
`OCF
`
`Command
`Parameters
`
`Return
`Parameters
`
`HCl_Read_Number_0f_Supported_IAC
`
`0xO038
`
`Status,
`
`Num_Support_|AC
`
`Description:
`
`This command will read the value for the number of Inquiry Access Codes
`(IAC) that the local Biuetooth device can simultaneous listen for during an
`inquiry Scan. All Bluetooth devices are required to support at least one IAC,
`the General inquiry Access Code (GIAC or UIAC), but some Bluetooth devices
`support additional IACs.
`
`Command Parameters:
`
`None
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Read_Number_Of_Supported_|AC command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Read_Number_Of_Supported_|AC command failed. See 'i'aoi-a 6.1 as
`‘€413 for list of Error Codes.
`
`Num_Sup,oon‘_iAC
`
`Size: 1 Byte
`
`Parameter Description
`
`Specifies the number of Supported [AC that the local Bluetooth device can
`simultaneous listen for during an Inquiry Scan.
`
`Range: 0x01-0x40
`
`Event(s) generated (unless masked away):
`
`When the Read_Number_Of_Supported_lAC command has Completed, a
`Command Complete event will be generated.
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293897
`
`Samsung Ex. 1019 p. 669
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 870 of 3082
`
`Host Controiier interface Functions! Specification
`
`Bluetooth-
`
`4.7.46 Read_Current_iAC_LAP
`
`HC|_Read_Current_lAC_LAP
`
`0x0039
`
`Command Parameters Return Parameters
`
`Status.
`
`N u m_Cu rre nt_lAC,
`
`EAC_LAP[i]
`
`Description:
`
`This command reads the LAP(s) used to create the Inquiry Access Codes
`(IAC) that the local Bluetooth device is simultaneously scanning for during
`Inquiry Scans. All Bluetooth devices are required to support at least one IAC
`(GIAC or UIAC). Some Bluetooth devices support additional |ACs.
`
`Command Parameters:
`
`None
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`- Read_Current_lAC_LAP comma nd succeeded.
`
`Size: 1 Byte
`
`OX0‘!-OXFF
`
`Read_Current_|AC_LAP command failed. See ‘="a§>Ee 8.1 -an ;:)23§;E: "F45": for
`list of Error Codes.
`
`Num_ Cun‘ent_
`
`Size: 1 Byte
`
`Parameter Description
`
`Specifies the number of |ACs which are currently in use by the local Blue-
`tooth device to simultaneously listen for during an Inquiry Scan.
`
`Range: 0x01-Bx-40
`
`iAC_i_AP[r]
`
`Size: 3 Bytes * Num_Curren1‘__iAC
`
`Value
`
`Parameter Description
`
`OXXXXXXX
`
`LAPS used to create the IAC which is currently in use by the local Blue-
`tooth device to simultaneously listen for during an Inquiry Scan.
`
`Range: 0x9E8B00-0x9E8B3F
`
`Event(s) generated (unless masked away):
`
`When the Read_Current_|AC_LAP command has completed, a Command
`Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT029389B
`
`Samsung Ex. 1019 p. 670
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Host Coniroiier interface Functional Specification
`
`4.7.47 Write_Current_|AC_LAP
`
`page 671 of 1082
`
`Bluetooth.
`
`Command
`
`Command Parameters
`
`Return Parameters
`
`HCl_Write_Current_lAC_LAP
`
`Ux003A Num_Current_lAC,
`
`Status
`
`IAC_LAP[i]
`
`Description:
`
`This command writes the LAP(s) used to create the Inquiry Access Codes
`(IAC) that the local Bluetooth device is simultaneously scanning for during
`Inquiry Scans. All Bluetooth devices are required to support at least one IAC
`(GIAC or UIAC). Some Bluetooth devices support additional lACs. Therefore,
`the LAP used to create the GIAC or UIAC must be among the |AC_LAP param-
`eters of this command.
`
`Note: this command writes over the current lACs used by the Bluetooth device.
`If the value of the NumCurrent|AC is more than the number of supported lACs,
`then only the first, X Inquiry Access Codes (where X equals the number of sup-
`ported IACs) will be stored without any error.
`
`Command Parameters:
`
`Num__Current_iAC
`
`Size: 1 Byte
`
`Parameter Description
`
`Specifies the number of IACs which are currently in use by the local Blue-
`tooth device to simultaneously listen for during an Inquiry Scan.
`
`Range: 0x01-0x40
`
`iA C_i_AP[r]
`
`Size: 3 Bytes * Num_Current_iAC
`
`Parameter Description
`
`OXXXXXXX
`
`LAP(s) used to create IAC which is currently in use by the locai Bluetooth
`device to simultaneously listen for during an Inquiry Scan.
`
`Range: 0x9E8BO0-0x9E8B3F.
`
`The GIAC is the default IAC to be used. If additional lACs are supported,
`additional default IAC will be determined by the manufacturer.
`
`HCI Commands
`
`29 November ‘I999
`
`AFFLT0293899
`
`Samsung Ex. 1019 p. 671
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Conrrofler Interface Functfona! Specification
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Write_Current_1AC_"LAP command succeeded.
`
`page 872 of 38532
`
`Bluetooth-
`
`Size: 1 Byte
`
`0x01-OXFF
`
`WriXe_Current_iAC_LAP command failed. See ‘§'saai:>Ee $3,? at‘.-E‘: gzeagqe ?e"rf‘> for
`Iist of Error Codes.
`
`Event(s) generated (unless masked away):
`
`When the Write_Current_lAC_LAP command has completed, a Command
`Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293900
`
`Samsung Ex. 1019 p. 672
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Host Controiier interface Functional Specification
`
`4.7.48 Read_Page_Scan_Period_Mode
`
`page 673 of 1082
`
`Bluetooth.
`
`HCl_Read_Page_Scan_Pericd_
`Mme
`
`0x003B
`
`Status.
`Page_Scan_Period_Mode
`
`Parameters
`
`Description:
`
`This command is used to read the mandatory Page_Scan_Period_Mode of the
`local Bluetooth device. Every time an inquiry response message is sent, the
`Bluetooth device will start a timer (T_mandatory_pscan), the value of which is
`dependent on the Page_Scan_Period_Mode. As long as this timer has not
`expired, the Bluetooth device will use the Page_Scan_Period_Mode for all fol-
`lowing page scans.
`Note: the timer T_mandatory__pscan will be reset at each new inquiry
`response. For details see the “Baset3and Sfipeciiisatiorr‘ on page 33. (Keyword:
`SP«Mode, FHS-Packet, T_mandatory_pscan, lnquiry~Response).
`
`After transmitting one or more inquiry response (FHS) packets as a result of
`the inquiry scan process, the local Bluetooth device is allowed to enter the
`page scan state using mandatory page scan mode regardless of the setting of
`the Scan_Enab|e parameter.
`
`Command Parameters:
`
`None
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`OXD1 -DXFF
`
`Size: 1 Byte
`
`Parameter Description
`
`Read_Page_Sca n_Period_Mode command succeeded.
`
`Read_Page_Scan_Pericd_Mode command failed. See Tat.«ia =3/I =:i.r~. page
`‘M5 for list of Error Codes.
`
`Page_Scan_F’eriod_ Mode:
`
`Size: 1 Byte
`
`Parameter Description
`
`0x00
`
`0x01
`
`0x02
`
`0x03-OXFF
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293901
`
`Samsung Ex. 1019 p. 673
`
`

`
`BLUETOOTH SPECEFICATION Version 1.0 8
`
`page 874 of 3332
`
`Host Conrrofler Interface Functfona! Specification
`
`uetooth-
`
`Event(s) generated (unless masked away):
`
`When the Read_Page_Scan_Period_Mode command has completed, a Com-
`mand Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293902
`
`Samsung Ex. 1019 p. 674
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Host Coniroiier interface Functional Specification
`
`4.7.49 Write_Page_Scan_Period_Mode
`
`page 675 of 1082
`
`Bluetooth.
`
`Command
`
`Command Parameters
`
`Return Parameters
`
`HCl_Write_Page_Scan_P Ux003C
`eriod_Mode
`
`Page_Scan_Period_Mode
`
`Status
`
`Description:
`
`This command is used to write the mandatory Page_Scan_Period_Mode of the
`local Biuetooth device. Every time an inquiry response message is sent, the
`Bluetooth device will start a timer (T_mandatory_pscan), the value of which is
`dependent on the Page_Scan_Period_Mode. As long as this timer has not
`expired, the Bluetooth device will use the Page_Scan_Period_Mode for all fol-
`lowing page scans.
`Note: the timer T_mandatory_pscan will be reset at each new inquiry
`response. For details see the “i’E~asa'oanri ESp=.‘-:cEficatir.=n"‘ on page 33. (Keyword:
`SP-Mode, FHS-Packet, T_rnandatory_pscan, Inquiry-Response).
`
`After transmitting one or more inquiry response (FHS) packets as a result of
`the inquiry scan process, the local Bluetooth device is allowed to enter the
`page scan state using mandatory page scan mode regardless of the setting of
`the SCan_Enab|e parameter.
`
`Command Parameters:
`
`Page_Scan_Period_ Mode:
`
`Size: 1' Byte
`
`Parameter Description
`
`P0. Default.
`
`P1
`
`P2
`
`0x00
`
`0x0‘!
`
`0x02
`
`UXD3-OXFF
`
`Return Parameters:
`
`Status.‘
`
`Value
`
`0x00
`
`Parameter Description
`
`Write_Page_Scan__Period_Mode command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Write_Page_Scan_Period_Mode command failed. See ‘Janie 6.1 on page
`'i'4EE- for list of Error Codes.
`
`Event(s) generated (unless masked away):
`
`When the Write_Page_Scan_Period_Mode command has completed, a
`Command Complete event will be generated.
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293903
`
`Samsung Ex. 1019 p. 675
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Controiier interface Functionai Specification
`
`4.7.50 Read_Page_Scan_Mode
`
`page 876 of ms:
`
`Bluetooth-
`
`HC|_Read_Page_Scan_Mode
`
`Elx003D
`
`Status.
`
`Page_Scan_Mode
`
`Parameters
`
`Description:
`
`This command is used to read the default page scan mode of the local
`Bluetooth device. The Page_Scan_Mode parameter indicates the page scan
`mode that is used for default page scan. Currently one mandatory page scan
`mode and three optional page scan modes are defined. Following an inquiry
`response, if the Baseband timer T_mandatory_pscan has not expired, the
`mandatory page scan mode must be applied. For details see the "E3aset)anti
`Specificatien‘ on page 33 (Keyword: Page-Scan-Mode, FHS-Packet,
`T_mandatory_pscan)
`
`Command Parameters:
`
`None
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Read_Page_Scan_Mode command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Read__Page_Scan,_Mode command failed. See 'i'at.~§e 6.1
`list of Error Codes.
`
`page '?'cii*3 for
`
`Size: 1 Byte
`
`Page_Scan_Mode.'
`Parameter Description
`Mandatory Page Scan Mode
`
`0x00
`
`0x01
`
`0x02
`
`0x03
`
`Optional Page Scan Mode I
`
`Optional Page Scan Mode II
`
`Optional Page Scan Mode Ill
`
`0X04-UXFF
`
`Reserved
`
`Event(s) generated (unless masked away):
`
`When the Read_Page_Scan_Mode command has completed, a Command
`Complete event will be generated.
`
`676
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293904
`
`Samsung Ex. 1019 p. 676
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 677 of 1082
`
`Host Controiier interface Functional Specification
`
`uetooth.
`
`4.7.51 Write_Page_Scan_Mode
`
`Command
`
`OCF
`
`Command Parameters
`
`Rem mParameters
`
`HCl_Write_Pag e_S ca n_M ode
`
`Page_Sca n_Mode
`
`Description:
`
`This command is used to write the default page scan mode of the local
`Bluetooth device. The Page_Scan_Mode parameter indicates the page scan
`mode that is used for the default page scan. Currently, one mandatory page
`scan mode and three optional page scan modes are defined. Following an
`inquiry response, if the Baseband timer T_mandatory_pscan has not expired,
`the mandatory page scan mode must be applied. For details see the "Base-
`bartd Specifi<:aiéce'a" on page
`(Keyword: Page-Scan-Mode, FHS-Packet,
`T_mandatory_pscan).
`
`Command Parameters:
`
`Page_Scan_Moo‘e:
`
`Size: 1 Byte
`
`0x00
`
`0x01
`
`0x02
`
`0x03
`
`Parameter Description
`
`Mandatory Page Scan Mode. Default.
`
`Optional Page Scan Mode I
`
`Optional Page Scan Mode ll
`
`Optional Page Scan Mode l||
`
`UX04-UXFF
`
`Reserved.
`
`Return Parameters:
`
`Status:
`
`Value
`
`0x00
`
`Parameter Description
`
`Write_Page_Scan_Mocle command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Wrile_Page_Scan_Mode command failed. See ?'a§:ete 6.’! on
`list of Error Codes.
`
`‘ms for
`
`Event(s) generated (unless masked away):
`
`When the Write_Page_Scan_Mode command has completed, a Command
`Complete event will be generated.
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293905
`
`Samsung Ex. 1019 p. 677
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Coniroiier interface Functional Specification
`
`4.8 INFORMATIONAL PARAMETERS
`
`page 878 of 3082
`
`Bluetooth-
`
`The Informational Parameters are fixed by the manufacturer of the Bluetooth
`hardware. These parameters provide information about the Bluetooth device
`and the capabilities of the Host Controller, Link Manager, and Baseband. The
`host device cannot modify any of these parameters. For Informational Parame-
`ters Commands, the OGF is defined as 0x04
`
`E-”<ead__i_-3 c2a«E_Ver'sion__i nfc rmaiion
`
`t‘~ieao‘__L.ooal,__Eéuoportaofeatures
`
`Rea~'£_E3L€'t'er_Si2e
`
`Reac2___t‘Iouotry___i.'2ode
`
`i".eeo___E3{}___.«?«1Z)éI3R.
`
`commandsummaw
`The Rea d_t_or;ai_‘v'e rséo n__E n to rm-atitniz command
`will read the values for the version information for
`the local Bluetooth device.
`
`The Reati___§._oca!____Su:}porte<i,_Eeatajres comma rid
`requests a list of the supported features for the
`local device.
`
`The Head_-‘_-‘=:.r.‘fer_ oommand returns the size
`of the HCI buffers. These buffers are used by the
`Host Controller to buffer data that is to be transmit-
`ted.
`
`The REE2a£‘§___COtJ?}‘i?f,{___Cf)tie command will read the
`value for the Country Code status parameter. The
`Country Code defines which range of frequency
`band of the lSM 2.4 GHz band will be used by the
`device.
`
`The Re.-as-.“J____i-3ij3__i\i3§§}R command will read the vaiue
`for the BD_ADDR parameter. The BD_ADDR is a
`48-bit unique identifier for a Bluetooth device.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293906
`
`Samsung Ex. 1019 p. 678
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 679 of 1082
`
`Host Contrciier interface Functional Specification
`
`uetooth.
`
`4.8.1 Read_LocaI_\iersion_Information
`
`Command
`
`Command
`Parameters
`
`Return Parameters
`
`HCl_Read_Loca|_Version_
`Information
`
`0310001
`
`Status,
`HCI Version.
`
`HCI Revision,
`
`LMP Version,
`
`Manufacturer_Name,
`LMP Subversion
`
`Description:
`
`This command will read the values for the version information for the local
`
`Bluetooth device. The version information consists of two parameters: the ver-
`sion and revision parameters.
`
`The version parameter defines the major hardware version of the Bluetooth
`hardware. The version parameter only changes when new versions of the
`Bluetooth hardware are produced for new Bluetooth SIG specifications. The
`version parameter is controlled by the SIG.
`
`The revision parameter should be controlled by the manufacturer and should
`be changed as needed. The lv1anufacturer_Name parameter indicates the
`manufacturer of the local Bluetooth module as specified by the LMP definition
`of this parameter. The subversion parameter should be controlled by the manu-
`facturer and should be changed as needed. The subversion parameter defines
`the various revisions that each version of the Bluetooth hardware will go
`through as design processes change and errors are fixed. This allows the soft-
`ware to determine what Bluetooth hardware is being used, and to work around
`various bugs in the hardware if necessary.
`
`Command Parameters:
`
`None.
`
`Return Parameters:
`
`Status.‘
`
`Value
`
`0x00
`
`Parameter Description
`
`Read_Loca|_Version_|nformation command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Read__Lccal__Version_|nforrnaticn command failed. See Tame 3. on page
`‘£45 for list of Error Codes.
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293907
`
`Samsung Ex. 1019 p. 679
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 680 of 3082
`
`Host Controiier interface Functicnai Specification
`
`HCi_ Version:
`
`Bluetooth-
`
`Size: 1 Byte
`
`Parameter Description
`
`Version of the Current HCI in the Bluetooth hardware.
`
`0x00: Bluetooth HCI Specification 1.0
`0x01-OXFF: Reserved
`
`HCi_Revision.'
`
`Size: 2 Bytes
`
`Parameter Description
`
`Revision of the Current HCL in the Bluetoolh hardware.
`
`i_MP_ Version:
`
`Size: 1 Byte
`
`Parameter Description
`
`Version of the Current LMP in the Bluetooth Hardware, see Tania
`page 23-1 in the Link Manager Protocoi for assigned values (VersNr).
`
`on
`
`Manufacrurer_Name:
`
`Size: 2 Bytes
`
`Value
`
`Parameter Description
`
`up
`Manufacturer Name of the Bluetooth Hardware. see Tania 5.2. on page
`45'! in the Link Manager Protocol for assigned values (Compid).
`
`i_MP_Subversion:
`
`Size: 2 Bytes
`
`Parameter Description
`
`Subversion ofthe Current LMP in the Bluetooth Hardware, see ‘facts E5-.2
`page 231'
`in the Link Manager Protocol tor assigned values (SubVersNr}.
`
`Event(s) generated (unless masked away):
`
`When the Read_Loca|_Version_lnformation command has completed, a
`Command Complete event will be generated.
`
`29 November 1999
`
`HCI Commands
`
`AFFLT0293908
`
`Samsung Ex. 1019 p. 680
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 881 of 1082
`
`Host Coniroiier interface Functional Specification
`
`uetooth.
`
`4.8.2 Read_LocaI_Supportecl_Features
`
`Command
`
`OCF
`
`command
`Parameters
`
`Return Parameters
`
`HCl_Read_Loca|_Supported_Features
`
`0x0003
`
`Status.
`
`LM P_Features
`
`Description:
`
`This command requests a list of the supported features for the local device.
`This command will return a list of the LMP features. For details see “§_ie"‘:i< §\i?.an--
`
`ages‘ .F3*rc'tcco§"" en {sage 38%}.
`
`Command Parameters:
`
`None.
`
`Return Parameters:
`
`Status.‘
`
`Value
`
`0x00
`
`Parameter Description
`
`Read_Loca|_Supported_Features command succeeded.
`
`Size: 1 Byte
`
`0x01-0xFF
`
`Read_LocaLSupported_Features command failed. See T:-Tthiis :1‘: an
`g:-age: 1'45 for list of Error Codes.
`
`i_MP__Fearures:
`
`Size: 8 Bytes
`
`Parameter Description
`
`OXXXXXXXXX
`XXXXXXXX
`
`Bit Mask List of LMP features. For details see "Link Mariaeger P:"otcr;c%" an
`
`Event(s) generated (unless masked away):
`
`When the Read_Loca|_Supported_Features command has completed, a
`Command Complete event will be generated.
`
`HCI Commands
`
`29 November 1999
`
`AFFLT0293909
`
`Samsung Ex. 1019 p. 681
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Host Controiier interface Functions.‘ Specification
`
`4.8.3 Read_Buffer_Size
`
`page 882 of 3882
`
`Bluetooth-
`
`Parameters
`
`HC|_Read_Buffer_Size
`
`0x0005
`
`Status.
`
`H C_AC L_D ata_Pac l<et_Le ngth.
`
`HC_SCO_Data_ Pa cl<et_Le ngth, HC_
`
`To ta l_N um_AC L_ Data_Pa ckets,
`
`H CWTota|_N um_SC O_Data_Packets
`
`Description:
`
`The Read_Buffer_Size command is used to read the maximum size of the data
`portion of HCI AOL and SCO Data Packets sent from the Host to the Host Con-
`troller. The Host will segment the data to be transmitted from the Host to the
`Host Controtler according to these sizes, so that the HCI Data Packets will con-
`tain data with up to these sizes. The Read_Bufier_Size command also returns
`the total number of HCI ACE. and SCO Data Packets that can be stored in the
`
`data buffers of the Host Controller. The Read_Buffer_Size command must be
`issued by the Host before it sends any data to the Host Controller.
`
`The HC_ACL_Data_Packet_Length return parameter will be used to determine
`the size of the L2CAP segments contained in ACL Data Packets, which are
`transferred from the Host to the Host Controller to be broken up into baseband
`packets by the Link Manager. The HC_SCO_Data__Packet_Length return
`parameter is used to determine the maximum size of HCI SCO Data Packets.
`Both the Host and the Host Controller must support command and event pack-
`ets. where the data portion (exctuding header) contained in the packets is 255
`bytes in size. The HC_Tota|_Num_ACL_Data_Packets return parameter con-
`tains the total number of HCI ACL Data Packets that can be stored in the data
`buffers of the Host Controller. The Host will determine how the buffers are to be
`divided between different Connection Handles. The
`
`HC_Tota|_Num_SCO_Data_
`Packets return parameter gives the same informati