- •TABLE OF CONTENTS
- •1.1 Motivation
- •1.2 Design Goals
- •1.3 Objective of the Specification
- •1.4 Scope of the Document
- •1.5 USB Product Compliance
- •1.6 Document Organization
- •2.1 Terms
- •2.2 Conventions:
- •2.3 References
- •3.1 USB System Description
- •3.1.1 Topology
- •3.1.1.1 USB Host
- •3.1.1.2 Wireless USB Devices
- •3.2 Physical Interface
- •3.3 Power Management
- •3.4 Bus Protocol
- •3.5 Robustness
- •3.5.1 Error Handling
- •3.6 Security
- •3.7 System Configuration
- •3.7.1 Attachment of Wireless USB Devices
- •3.7.2 Removal of Wireless USB Devices
- •3.7.3 Bus Enumeration
- •3.8 Data Flow Types
- •3.9 Wireless USB Devices
- •3.9.1 Device Characterizations
- •3.9.2 Devices and MAC Layer
- •3.10 Wireless USB Host: Hardware and Software
- •4.1 Implementer Viewpoints
- •4.2 Communications Topology
- •4.2.1 Physical Topology
- •4.3 Wireless USB Communication Flows
- •4.3.1 Wireless USB Channel Time
- •4.3.2 MMC Transmission Accuracy
- •4.3.3 USB Time across Device Wire Adapters
- •4.3.5 Device Endpoints
- •4.3.6 Wireless USB Information Exchange Methods
- •4.3.7 Device Perspective
- •4.3.7.1 Self Beaconing Devices
- •4.3.7.2 Directed Beaconing Devices
- •4.3.7.3 Non Beaconing Devices
- •4.3.7.4 Selecting A Wireless USB Host
- •4.3.8 Host Perspective
- •4.3.8.1 MAC Layer Compliant Device
- •4.3.8.2 Wireless USB Host
- •4.3.8.3 Host System Management
- •4.3.8.5 Other Host Considerations
- •4.4 Data Transfers
- •4.4.1 Burst Mode Data Phase
- •4.5 Bulk Transfers
- •4.5.1 Bulk Transfer Packet Size and Signaling Rate Constraints
- •4.5.2 Bulk Transfer Channel Access Constraints
- •4.5.3 Bulk Transfer Data Sequences
- •4.6 Interrupt Transfers
- •4.6.1 Low Power Interrupt IN
- •4.6.2 Interrupt Transfer Packet Size and Signaling Rate Constraints
- •4.6.3 Interrupt Transfer Channel Access Constraints
- •4.6.4 Interrupt Transfer Data Sequences
- •4.7 Isochronous Transfers
- •4.7.1 Isochronous Transfer Packet Size and Signaling Rate Constraints
- •4.7.2 Isochronous Transfer Channel Access Constraints
- •4.7.3 Isochronous Transfer Data Sequences
- •4.7.4 Isochronous Endpoint Host System Admission Decisions
- •4.7.5 Isochronous Data Discards and Use of Isochronous Packet Discard IE
- •4.8 Control Transfers
- •4.8.1 Control Transfer Packet Size and Signaling Rate Constraints
- •4.8.2 Control Transfer Channel Access Constraints
- •4.8.3 Control Transfer Data Sequences
- •4.8.4 Data Loopback Commands
- •4.9 Device Notifications
- •4.10 Media Reliability Considerations
- •4.10.1 Transmit Power Control
- •4.10.2 Adjustments to Data Phase Packet Payload Sizes
- •4.10.3 Adjustments to Transmit Bit Rate
- •4.10.4 Changing PHY Channel
- •4.10.5 Host Schedule Control
- •4.10.6 Dynamic Bandwidth Interface Control
- •4.11 Special Considerations for Isochronous Transfers
- •4.11.1 Summary Of Key Features Of USB Wired Isochrony
- •4.11.1.1 Wireless Service Intervals
- •4.11.2 UWB Media Characteristics
- •4.11.2.1 Superframe Layout
- •4.11.2.2 Worst Case Superframe Layout – Service Interval Bounds.
- •4.11.2.3 Wireless Packet Error Rates
- •4.11.3 Wireless USB Isochronous Transfer Level Protocol
- •4.11.4 Wireless USB Isochronous IN Example
- •4.11.5 Wireless USB Isochronous OUT Example
- •4.11.6 Choosing an Isochronous IN or Isochronous OUT Endpoint Buffer Size
- •4.11.7 Isochronous OUT endpoint receiver implementation options
- •4.11.7.1 Presentation Time aware implementation
- •4.11.7.2 Presentation time aware implementation with “false” acknowledgement
- •4.11.7.3 Presentation time unaware implementations
- •4.11.8 Synchronization
- •4.11.8.1 Synchronizing a Stream Start Time
- •4.11.9 Error Handling Details
- •4.11.9.1 Reporting Data Discarded At the Transmitter
- •4.11.9.2 Discarding Data during A Burst
- •4.11.9.3 Application Handling of Discards
- •4.12 Device Reset
- •4.13 Connection Process
- •4.13.1 Reconnection Process
- •4.14 Disconnect
- •4.15 Security Mechanisms
- •4.15.1 Connection Lifetime
- •4.15.2 Host Security Considerations
- •4.15.2.1 CHID Selection
- •4.15.2.2 CDID Selection
- •4.16 Wireless USB Power Management
- •4.16.1 Device Power Management
- •4.16.1.1 Device Sleep
- •4.16.1.2 Device Wakeup
- •4.16.2 Host Power Management
- •4.16.2.1 Channel Stop
- •4.16.2.2 Remote Wakeup
- •4.16.2.3 Channel Start
- •4.17 Dual Role Devices (DRD)
- •4.17.2 Pairing P2P-DRD to establish reverse link
- •5.1 Packet Formats
- •5.2 Wireless USB Transaction Groups
- •5.2.1 Wireless USB Channel Time Allocation Information Elements
- •5.3 Transaction Group Timing Constraints
- •5.3.1 Streaming-Mode Inter-packet Constraints for the PHY
- •5.3.2 Protocol Synchronization
- •5.4 Data Burst Synchronization and Retry
- •5.5 Wireless USB Transactions
- •5.5.1 Isochronous Transactions
- •5.5.2 Control Transfers
- •5.5.3 Device Notifications
- •5.5.4 Flow Control
- •6.1 Introduction
- •6.1.1 Goal of USB Security
- •6.1.2 Security and USB
- •6.2 Overview
- •6.2.1 Base of Trust
- •6.2.2 Preserve the Nature of the USB Device Model
- •6.2.3 Implementation of Security Extensions
- •6.2.4 Encryption Methods
- •6.2.5 Message Format
- •6.2.6 Encryption Keys
- •6.2.6.1 Master Keys
- •6.2.6.2 Session Keys
- •6.2.7 Correct key determination
- •6.2.8 Replay Prevention
- •6.2.9 Secure Packet Reception
- •6.2.10 General Connection Model
- •6.2.10.1 Connection Context
- •6.2.10.2 Connection Lifetime
- •6.2.10.3 New Connection
- •6.2.10.4 Connection
- •6.2.10.5 Reconnection
- •6.2.10.6 Revocation
- •6.2.10.8 Diagnostic Support
- •6.2.10.9 Mutual Authentication
- •6.2.11 Key Management
- •6.2.11.1 PTK Management
- •6.2.11.2 GTK Management
- •6.3 Association and Authentication
- •6.3.1 Connection and Reconnection Requests
- •6.3.2 Authentication
- •6.3.2.1 Authentication Related Device Capabilities
- •6.3.2.2 Ceremonies
- •6.4.1 CCM nonce Construction
- •6.4.2 l(m) and l(a) Calculation
- •6.4.3 Counter-mode Bx Blocks
- •6.4.4 Encryption Ax Blocks
- •6.5.1 Key Derivation
- •6.5.2 Out-of-band MIC Generation
- •6.5.3 Example Random Number Generation
- •7.1 Wireless USB Device States
- •7.1.1 UnConnected
- •7.1.2 UnAuthenticated
- •7.1.3 Authenticated
- •7.1.4 Reconnecting
- •7.2 Generic Wireless USB Device Operations
- •7.3 Standard Wireless USB Device Requests
- •7.3.1 Wireless USB Extensions to Standard Requests
- •7.3.1.1 Clear Feature
- •7.3.1.2 Get Status
- •7.3.1.3 Set Address
- •7.3.1.4 Set Feature
- •7.3.1.5 Set Interface DS
- •7.3.1.6 Set WUSB Data
- •7.3.1.7 Data Loopback Write
- •7.3.1.8 DATA Loopback Read
- •7.3.2 Security-related Requests
- •7.3.2.1 Get Security Descriptor
- •7.3.2.2 Set Encryption
- •7.3.2.3 Get Encryption
- •7.3.2.4 Key Management
- •7.3.2.6 Set Security Data
- •7.3.2.7 Get Security Data
- •7.4 Standard Wireless USB Descriptors
- •7.4.1 Device Level Descriptors
- •7.4.1.1 Wireless USB Device Capabilities – UWB
- •7.4.2 Configuration
- •7.4.3 Endpoint
- •7.4.4 Wireless USB Endpoint Companion
- •7.4.5 Security-Related Descriptors
- •7.4.5.1 Security Descriptor
- •7.4.5.2 Key Descriptor
- •7.5 Wireless USB Channel Information Elements
- •7.5.1 Wireless USB Connect Acknowledge IE
- •7.5.2 Wireless USB Host Information IE
- •7.5.3 Wireless USB Channel Change Announcement IE
- •7.5.4 Wireless USB Device Disconnect IE
- •7.5.5 Wireless USB Host Disconnect IE
- •7.5.6 Wireless USB Release Channel IE
- •7.5.7 Wireless USB Work IE
- •7.5.8 Wireless USB Channel Stop IE
- •7.5.9 Wireless USB Device Keepalive IE
- •7.5.10 Wireless USB Isochronous Packet Discard IE
- •7.5.11 Wireless USB Reset Device IE
- •7.5.12 Wireless USB Transmit Packet Adjustment IE
- •7.6 Device Notifications
- •7.6.1 Device Connect (DN_Connect)
- •7.6.1.1 Connect Request
- •7.6.1.2 Reconnect Request
- •7.6.2 Device Disconnect (DN_Disconnect)
- •7.6.3 Device Endpoints Ready (DN_EPRdy)
- •7.6.4 Device MAS Availability Changed (DN_MASAvailChanged)
- •7.6.5 Device Sleep (DN_Sleep)
- •7.6.6 Remote Wakeup (DN_RemoteWakeup)
- •7.6.7 Device Alive (DN_Alive)
- •8.1 Operational Model
- •8.1.1 Functional Characteristics
- •8.1.2 Data Transfer Interface
- •8.1.3 Remote Pipe
- •8.1.4 Wire Adapter Functional Blocks
- •8.1.5 Downstream Port(s)
- •8.1.6 Upstream Port
- •8.1.7 Downstream Host Controller
- •8.1.8 Upstream Endpoint Controller
- •8.1.9 Remote Pipe Controller
- •8.1.9.1 RPipe Descriptor
- •8.1.9.2 Bulk OUT Overview
- •8.1.9.3 Bulk IN Overview
- •8.1.9.4 Control Transfer Overview
- •8.1.9.5 Interrupt Transfer Overview
- •8.1.9.6 Isochronous Transfer Overview
- •8.1.10 Suspend and Resume
- •8.1.10.1 DWA Suspend and Resume
- •8.1.10.2 HWA Suspend and Resume
- •8.1.11 Reset Behavior
- •8.1.12 Device Control
- •8.1.13 Buffer Configuration
- •8.2 Descriptors
- •8.3 Requests
- •8.3.1 Wire Adapter Class-Specific Requests
- •8.3.1.1 Abort RPipe
- •8.3.1.2 Clear RPipe Feature
- •8.3.1.3 Clear Wire Adapter Feature
- •8.3.1.4 Get RPipe Descriptor
- •8.3.1.5 Get RPipe Status
- •8.3.1.6 Get Wire Adapter Status
- •8.3.1.7 Set RPipe Descriptor
- •8.3.1.8 Set RPipe Feature
- •8.3.1.9 Set Wire Adapter Feature
- •8.3.1.10 Reset RPipe
- •8.3.2 Notification Information
- •8.3.3 Transfer Requests
- •8.3.3.1 Control Transfers
- •8.3.3.2 Bulk and Interrupt Transfers
- •8.3.3.3 Transfer Completion Notification
- •8.3.3.4 Transfer Result
- •8.3.3.5 Abort Transfer
- •8.4 DWA Interfaces, Descriptors and Control
- •8.4.1 DWA Isochronous Streaming Interface
- •8.4.2 DWA Isochronous Streaming Overview
- •8.4.3 DWA Descriptors
- •8.4.3.1 Device Descriptor
- •8.4.3.2 Binary Device Object (BOS) Descriptor
- •8.4.3.3 Configuration Descriptor
- •8.4.3.4 Security Descriptors
- •8.4.3.5 Interface Association Descriptor
- •8.4.3.6 Data Transfer Interface Descriptor
- •8.4.3.7 Wire Adapter Class Descriptor
- •8.4.3.8 Notification Endpoint Descriptor
- •8.4.3.9 Notification Endpoint Companion Descriptor
- •8.4.3.10 Data Transfer Write Endpoint Descriptor
- •8.4.3.11 Data Transfer Write Endpoint Companion Descriptor
- •8.4.3.12 Data Transfer Read Endpoint Descriptor
- •8.4.3.13 Data Transfer Read Endpoint Companion Descriptor
- •8.4.3.14 Isochronous Streaming Interface Descriptor
- •8.4.3.15 Isochronous Streaming OUT Endpoint Descriptor
- •8.4.3.16 Isochronous Streaming OUT Endpoint Companion Descriptor
- •8.4.3.17 Isochronous Streaming IN Endpoint Descriptor
- •8.4.3.18 Isochronous Streaming IN Endpoint Companion Descriptor
- •8.4.3.19 Wire Adapter RPipe Descriptor
- •8.4.4 DWA Specific Requests
- •8.4.4.1 Clear Port Feature
- •8.4.4.2 Get Port Status
- •8.4.4.3 Set Isochronous Endpoint Attributes
- •8.4.4.4 Set Port Feature
- •8.4.5 DWA Notification Information
- •8.4.5.1 Remote Wake
- •8.4.5.2 Port Status Change
- •8.4.6 DWA Isochronous Transfers
- •8.4.6.1 DWA Isochronous OUT Responsibilities
- •8.4.6.2 DWA Isochronous IN Responsibilities
- •8.5 HWA Interfaces, Descriptors and Control
- •8.5.1 HWA Isochronous Streaming Overview
- •8.5.2 HWA Descriptors
- •8.5.2.1 Device Descriptor
- •8.5.2.2 Device_Qualifier Descriptor
- •8.5.2.3 Configuration Descriptor
- •8.5.2.4 Other_Speed_Configuration Descriptor
- •8.5.2.5 Security Descriptors
- •8.5.2.6 Data Transfer Interface Descriptor
- •8.5.2.7 Wire Adapter Class Descriptor
- •8.5.2.8 Notification Endpoint Descriptor
- •8.5.2.9 Data Transfer Write Endpoint Descriptor
- •8.5.2.10 Data Transfer Read Endpoint Descriptor
- •8.5.2.11 Wire Adapter RPipe Descriptor
- •8.5.3 HWA Specific Requests
- •8.5.3.2 Get BPST Adjustment
- •8.5.3.3 Get BPST Time
- •8.5.3.4 Get WUSB Time
- •8.5.3.5 Remove MMC IE
- •8.5.3.6 Set Device Encryption
- •8.5.3.7 Set Device Info
- •8.5.3.8 Set Device Key
- •8.5.3.9 Set Group Key
- •8.5.3.10 Set Num DNTS Slots
- •8.5.3.11 Set WUSB Cluster ID
- •8.5.3.12 Set WUSB MAS
- •8.5.3.13 Set WUSB Stream Index
- •8.5.3.14 WUSB Channel Stop
- •8.5.4 HWA Notification Information
- •8.5.4.1 BPST Adjustment Change
- •8.5.4.2 DN Received Notification
- •8.5.5 HWA Isochronous Transfers
- •8.5.5.1 HWA Isochronous OUT Responsibilities
- •8.5.5.2 HWA Isochronous IN Responsibilities
- •8.5.5.3 HWA Isochronous Transfer Completion
- •8.6 Radio Control Interface
- •8.6.1 Radio Control Descriptors
- •8.6.1.1 Radio Control Interface Descriptor
- •8.6.1.2 Radio Control Interface Class Descriptor
- •8.6.1.3 Radio Control Interrupt Endpoint Descriptor
- •8.6.2 Radio Control Command
- •8.6.2.1 Channel Change
- •8.6.2.2 Device Address Management
- •8.6.2.4 Reset
- •8.6.2.5 Scan
- •8.6.2.6 Set Beacon Filter
- •8.6.2.9 Set Notification Filter
- •8.6.2.10 Set TX Power
- •8.6.2.11 Sleep
- •8.6.2.12 Start Beaconing
- •8.6.2.13 Stop Beaconing
- •8.6.3 Radio Control Notifications
- •8.6.3.1 Application-specific Probe IE Received Notification
- •8.6.3.2 Beacon Received Notification
- •8.6.3.3 Beacon Size Notification
- •8.6.3.4 BPOIE Change Notification
- •8.6.3.5 BP Slot Change Notification
- •8.6.3.6 BP Switch IE Received Notification
- •8.6.3.7 Device Address Conflict Notification
- •8.6.3.8 DRP Availability Changed Notification
- •8.6.3.9 DRP Notification
- •A.1 Key Derivation
- •A.2 Handshake MIC calculation
- •A.3 Secure MMC (EO = payload length)
- •A.4 Data IN from device (EO = 2)
- •B.1 Descriptors for DWA
- •B.2 Descriptors for HWA
Chapter 8 |
|
Wire Adapter |
Wireless Universal Serial Bus Specification, Revision 1.0 |
8.6.2.9 Set Notification Filter
This command instructs the device to filter one or more notifications. The RCCB for this command is given below.
Table 8-87. Set Notification Filter RCCB
Offset |
Field |
Size |
Value |
|
|
|
Description |
|
|
|
|
|
|||
0 |
bCommandType |
1 |
0 |
GENERAL Command Type |
|||
|
|
|
|
|
|||
1 |
wCommand |
2 |
24 |
SET_NOTIFICATION_FILTER Command |
|||
3 |
bCommandContext |
1 |
Number |
Host assigned ID for this command. |
|||
|
|
|
|
Valid values are 1 through FEH. |
|||
|
|
|
|
|
|||
4 |
wNotification |
2 |
Bitmap |
Each bit in this bitmap identifies the notification to be |
|||
|
|
|
|
filtered. If a bit is set then that notification must not be sent |
|||
|
|
|
|
to the host. |
|
||
|
|
|
|
|
Bit |
|
Notification |
|
|
|
|
|
0 |
|
AS_PROBE_IE_RECEIVED |
|
|
|
|
|
1 |
|
BEACON_RECEIVED |
|
|
|
|
|
2 |
|
BEACON_SIZE_CHANGE |
|
|
|
|
|
3 |
|
BPOIE_CHANGE |
|
|
|
|
|
4 |
|
BP_SLOT_CHANGE |
|
|
|
|
|
5 |
|
BP_SWITCH_IE_RECEIVED |
|
|
|
|
|
6 |
|
DEV_ADDR_CONFLICT |
|
|
|
|
|
7 |
|
DRP_AVAILABITY_CHANGE |
|
|
|
|
. |
8 |
. |
DRP |
|
|
|
|
. |
15:9 . |
Reserved |
|
|
|
|
|
|
|||
6 |
bEnableState |
1 |
Number |
Specifies whether to enable or disable the filter. |
|||
|
|
|
|
|
Value |
|
Description |
|
|
|
|
|
0 |
|
Filter DISABLED |
|
|
|
|
|
|
|
Filter is disabled. This is the default filter |
|
|
|
|
|
|
|
state on power up or after a RESET |
|
|
|
|
|
|
|
command completes successfully. |
|
|
|
|
|
1 |
|
Filter ENABLED |
|
|
|
|
|
|
|
|
The device will confirm the result of the set notification filter operation by sending back an RCEB on the Radio Control Interrupt Endpoint. The RCEB for this command is given below.
Table 8-88. Set Notification Filter RCEB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bEventType |
1 |
0 |
GENERAL Event Type |
|
|
|
|
|
1 |
wEvent |
2 |
24 |
Result of SET_NOTIFICATION_FILTER Command |
|
|
|
|
|
3 |
bEventContext |
1 |
Number |
This should match the bCommandContext in the |
|
|
|
|
RCCB. |
|
|
|
|
|
4 |
bResultCode |
1 |
Number |
Indicates the completion status of the command. |
|
|
|
|
See Table 8-69 for a list of result codes. |
|
|
|
|
|
268
Chapter 8 |
|
Wire Adapter |
Wireless Universal Serial Bus Specification, Revision 1.0 |
8.6.2.10Set TX Power
This command is used to set the default transmit power for transmissions by this device. The RCCB for this command is given below.
Table 8-89. Set TX Power RCCB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bCommandType |
1 |
0 |
GENERAL Command Type |
|
|
|
|
|
1 |
wCommand |
2 |
25 |
SET_TX_POWER Command |
3 |
bCommandContext |
1 |
Number |
Host assigned ID for this command. |
|
|
|
|
Valid values are 1 through FEH. |
|
|
|
|
|
4 |
bPowerLevel |
1 |
Number |
Value indicating the number of steps below the highest |
|
|
|
|
power level that must be used. |
|
|
|
|
|
If the power level for transmission of a packet is not set by other means, then the device must use the power level specified in bPowerLevel to transmit that packet.
The default state on power up or after a RESET command completes successfully is the highest power level.
The RCEB for this command is given in Table 8-90.
Table 8-90. Set TX Power RCEB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bEventType |
1 |
0 |
GENERAL Event Type |
|
|
|
|
|
1 |
wEvent |
2 |
25 |
Result of SET_TX_POWER Command |
|
|
|
|
|
3 |
bEventContext |
1 |
Number |
This should match the bCommandContext in the RCCB. |
|
|
|
|
|
4 |
bResultCode |
1 |
Number |
Indicates the completion status of the command. See |
|
|
|
|
Table 8-69 for a list of result codes. |
|
|
|
|
|
8.6.2.11Sleep
On reception of this command the device will start hibernation after transmitting the Hibernation Mode IE in its beacons for the specified number of times if the device is not enabled for remote wake. If it is enabled for remote wake then it keeps sending beacons in every superframe. In the latter case, the device will wake up the host (if the host is sleeping) if it needs to send a notification that is not filtered.
The RCCB for this command is given below.
Table 8-91. Sleep RCCB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bCommandType |
1 |
0 |
GENERAL Command Type |
|
|
|
|
|
1 |
wCommand |
2 |
26 |
SLEEP Command |
|
|
|
|
|
3 |
bCommandContext |
1 |
Number |
Host assigned ID for this command. |
|
|
|
|
Valid values are 1 through FEH. |
|
|
|
|
|
4 |
bHibernationCount |
1 |
Number |
Number of superframes until the device begins |
|
|
|
|
hibernation. This field is only valid when remote wake is |
|
|
|
|
disabled on the device. |
|
|
|
|
|
6 |
bHibernationDuration |
1 |
Number |
Number of superframes for which the device intends to |
|
|
|
|
hibernate. This field is only valid when remote wake is |
|
|
|
|
disabled on the device. |
269
Chapter 8 |
|
Wire Adapter |
Wireless Universal Serial Bus Specification, Revision 1.0 |
If the remote wake is disabled on the device, it will begin hibernation after transmitting a number of beacons including Hibernation Mode IE. The Hibernation Countdown field in this IE is set to the bHibernationCount for the first beacon and must be decremented by one for each superframe. After sending a beacon with its Hibernation Countdown set to a zero, the device stops sending beacons and begins hibernation. The Hibernation Duration field in this IE must be set to the value specified by the bHibernationDuration field. The device will stay in hibernation during the specified period, but it is not required to wake up by itself after the specified hibernation period. The host is responsible for waking up the device and requesting it to restart beaconing.
If remote wake is enabled on the device, it must keep sending beacons in every superframe. Before executing this command, the host must specify a set of IEs that the device must send. When the device detects a wake event, e.g. DRP conflict, and the event notification is required by the notification filter (see Section 8.6.2.9), it must wake up the host (if it’s sleeping) and send the notification to the host.
The RCEB for this command is given in Table 8-92.
Table 8-92. Sleep RCEB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bEventType |
1 |
0 |
GENERAL Event Type |
|
|
|
|
|
1 |
wEvent |
2 |
26 |
Result of SLEEP Command |
3 |
bEventContext |
1 |
Number |
This should match the bCommandContext in the RCCB. |
|
|
|
|
|
4 |
bResultCode |
1 |
Number |
Indicates the completion status of the command. See |
|
|
|
|
Table 8-69 for a list of result codes. |
|
|
|
|
|
The bResultCode field indicates whether the sleep operation was successful. If a sleep is not succeeding, it is a vendor specific decision when to time out the operation and return failure.
8.6.2.12Start Beaconing
This command instructs the device to begin beaconing on the specified channel.
The RCCB for this command is given below.
Table 8-93. Start Beaconing RCCB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bCommandType |
1 |
0 |
GENERAL Command Type |
|
|
|
|
|
1 |
wCommand |
2 |
27 |
START_BEACONING Command |
|
|
|
|
|
3 |
bCommandContext |
1 |
Number |
Host assigned ID for this command. |
|
|
|
|
Valid values are 1 through FEH. |
|
|
|
|
|
4 |
wBPSTOffset |
2 |
Number |
The offset of a received beacon relative to the BPST of |
|
|
|
|
the device measured in microseconds. |
6 |
bChannelNumber |
1 |
Number |
The physical channel on which beaconing is to occur. The |
|
|
|
|
encoding of the channel number is specified in Table |
|
|
|
|
5-12. |
|
|
|
|
|
The bChannelNumber field value is the physical layer channel on which beaconing will begin. The device must join the beacon group that is identified by wBPSTOffset. The value in wBPSTOffset must be a value that was returned in a Beacon Received notification, see Section 8.6.3.1.
If the device is currently beaconing, then the device’s response to this command is undefined.
If the host did not receive any Beacon Received notifications, then the host must set wBPSTOffset to zero and the device must start beaconing as soon as possible and establish a beacon group.
270
Chapter 8 |
|
Wire Adapter |
Wireless Universal Serial Bus Specification, Revision 1.0 |
The device will confirm that the first beacon has been successfully transmitted or that the operation has failed by sending back an RCEB on the Radio Control Interrupt Endpoint. If the device successfully starts beaconing then it must listen to all the beacons during its beacon period and return any beacon received notifications that are not filtered to the host. In addition the Superframe Time Counter (STC), see Section 8.6.2.4 must be adjusted so that the zero of the STC corresponds to the new BPST.
The RCEB for this command is given in Table 8-94.
Table 8-94. Start Beaconing RCEB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bEventType |
1 |
0 |
GENERAL Event Type |
|
|
|
|
|
1 |
wEvent |
2 |
27 |
Result of START_BEACONING Command |
|
|
|
|
|
3 |
bEventContext |
1 |
Number |
This should match the bCommandContext in the |
|
|
|
|
RCCB. |
|
|
|
|
|
4 |
bResultCode |
1 |
Number |
Indicates the completion status of the command. |
|
|
|
|
See Table 8-69 for a list of result codes. |
|
|
|
|
|
The bResultCode field indicates whether beacons have begun to be successfully transmitted. If an operation to start beaconing is not succeeding, it is a vendor specific decision when to time out the operation and return failure.
8.6.2.13Stop Beaconing
This command instructs the device to stop beaconing.
The RCCB for this command is given below.
Table 8-95. Stop Beaconing RCCB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bCommandType |
1 |
0 |
GENERAL Command Type |
|
|
|
|
|
1 |
wCommand |
2 |
28 |
STOP_BEACONING Command |
|
|
|
|
|
3 |
bCommandContext |
1 |
Number |
Host assigned ID for this command. |
|
|
|
|
Valid values are 1 through FFH. |
|
|
|
|
|
This command is sent by the host software to stop beaconing that was started with the Start Beaconing command.
The device will confirm that beaconing has been stopped by sending back an RCEB on the Radio Control Interrupt Endpoint. The RCEB for this command is given below.
Table 8-96. Stop Beaconing RCEB
Offset |
Field |
Size |
Value |
Description |
|
|
|
|
|
0 |
bEventType |
1 |
0 |
GENERAL Event Type |
|
|
|
|
|
1 |
wEvent |
2 |
28 |
Result of STOP_BEACONING Command |
|
|
|
|
|
3 |
bEventContext |
1 |
Number |
This should match the bCommandContext in the |
|
|
|
|
RCCB. |
4 |
bResultCode |
1 |
Number |
Indicates the completion status of the command. |
|
|
|
|
See Table 8-69 for a list of result codes. |
|
|
|
|
|
The bResultCode field indicates whether the beaconing operation successfully stopped. A beacon period must have passed without a beacon being transmitted for the confirmation to complete successfully. If ending beaconing is not succeeding, it is a vendor specific decision when to time out the operation and return failure. The STC will revert back to a free running timer until the device starts beaconing again.
271