Enabling signal and enablement Month Year doc.: IEEE 802.11-yy/xxxxr0 September 2010 Enabling signal and enablement Date: 2010-09-01 Authors: Peter Ecclesine, Cisco John Doe, Some Company

Abstract FCC Master and Client devices Month Year doc.: IEEE 802.11-yy/xxxxr0 September 2010 Abstract FCC Master and Client devices FCC TVBD Client devices are required to remain under control of a Master device 802.11 Enabling signals 802.11 Enablement 802.11 Dependent STA operation CID 58, 65 proposed comment resolutions Peter Ecclesine, Cisco John Doe, Some Company

FCC Master and Client devices September 2010 FCC Master and Client devices FCC rules specify radio behavior and operator conduct FCC Part 15 rules are for devices that can be operated without an individual license (license-exempt devices) FCC makes distinctions for outdoor/indoor operation and master/client operation, but the definitions are in legal terms, not engineering terms The master/client definitions (15.202, next slide) are to allow radios that tune many frequencies to be certified by the FCC for client operation in the USA. The TVWS rules include these master/client device functions Peter Ecclesine, Cisco

47 CFR Part 15.202 Subpart C—Intentional Radiators 15.202 Certified operating frequency range. Client devices that operate in a master/client network may be certified if they have the capability of operating outside permissible part 15 frequency bands, provided they operate on only permissible part 15 frequencies under the control of the master device with which they communicate. Master devices marketed within the United States must be limited to operation on permissible part 15 frequencies. Client devices that can also act as master devices must meet the requirements of a master device. For the purposes of this section, a master device is defined as a device operating in a mode in which it has the capability to transmit without receiving an enabling signal. In this mode it is able to select a channel and initiate a network by sending enabling signals to other devices. A network always has at least one device operating in master mode. A client device is defined as a device operating in a mode in which the transmissions of the device are under control of the master. A device in client mode is not able to initiate a network.

47 CFR Part 15.703 Subpart H—Television Band Devices 15.703 Definitions (b) Client device. A TVBD operating in client mode. (c) Client mode. An operating mode in which the transmissions of the TVBD, including frequencies of operation, are under control of the master device. A device in client mode is not able to initiate a network. (f) Master device. A TVBD operating in master mode. (g) Master mode. An operating mode in which the TVBD has the capability to transmit without receiving an enabling signal. The TVBD is able to select a channel itself based on a list provided by the database and initiate a network by sending enabling signals to other devices. A network always has at least one device operating in master mode. (o) Television band device (TVBD). Intentional radiators operating on available channels in the broadcast television frequency bands at 54–60 MHz, 76–88 MHz, 174–216 MHz, 470–608 MHz and 614–698 MHz.

September 2010 FCC TVBD Client devices are required to remain under control of a master device Client mode - An operating mode in which the transmissions of the TVBD, including frequencies of operation, are under control of the master device. In a master/client network, a network specification can require that a master device be informed of any changes in client device frequency, transmit power, transmit channel bandwidth, or location. In a master/client network, a network specification can require that a client device continue to receive an enabling signal or cease transmission. Peter Ecclesine, Cisco

September 2010 802.11 Enabling Signals In a master/client network, an enabling signal is defined by the network specification In IEEE Std 802.11y-2008, an enabling signal is defined as “The enabling signal sent by an enabling STA is either a Beacon frame or a Probe Response frame with the RegLoc DSE bit set to 1 in the DSE Registered Location element.” [mb D5.0 8.4.2.54, 22 octets] In IEEE 802.11af D0.05, “the enabling signal is received directly from an enabling STA or a dependent AP, and is a Beacon frame or Probe Response frame containing an Advertising Protocol element [11u D11.0 7.3.2.90, .91, 3+4+2 octets] with an Advertising Protocol tuple whose Advertisement Protocol ID is set to the value of Registered Location Query Protocol specified in Table 8-43bl, indicating that enablement in TVWS is possible.” Peter Ecclesine, Cisco

September 2010 802.11 Enablement In a master/client network, enablement is defined by the network specification In REVmb D5.0, enablement is defined in 10.12.2 Enablement and deenablement The concept of an Enabling STA is lightly specified to the extent that it receives and sends messages using Public Action frames or in an unspecified manner. The Enabling STA is the source of DSE Enablement response, DSE Deenablement request, DSE Measurement request and DSE Power constraint messages. The concept of a Dependent AP is lightly specified to the extent that it relays Public Action frames in an unspecified manner. The Dependent AP can source DSE Registered Location Announcement, Extended Channel Switch Announcement, DSE Measurement request, DSE Measurement report and DSE Power constraint messages. Peter Ecclesine, Cisco

802.11 Dependent STA operation(1) September 2010 802.11 Dependent STA operation(1) In REVmb D5.0, Dependent STA operation is specified in 10.12.5 Dependent STA operation with DSE A dependent STA that is not enabled shall not transmit, except to attain enablement with an enabling STA, unless such action is mandated to be allowed in the regulatory domain (e.g., emergency services). A dependent STA shall not attempt enablement with an enabling STA unless the enabling STA is transmitting [an Enabling Signal]. The dependent STA shall send a Public Action DSE Registered Location Announcement frame to the broadcast address whenever [it has transmitted xxx times] A dependent STA that has not attained enablement shall not transmit beyond [32 seconds] measured from the time of the first PHY-TXSTART.request primitive, while attempting to attain enablement. Then if it is not enabled, it shall not transmit for [512 seconds] before it can again attempt to attain enablement. Peter Ecclesine, Cisco

802.11 Dependent STA operation(2) September 2010 802.11 Dependent STA operation(2) A dependent STA shall return a DSE measurement report in response to a DSE measurement request if the request is received from the AP with which it is associated or the enabling STA with which it last attempted enablement and the ResponderSTAAddress field matches its own IEEE MAC address.<>The Measurement Report Mode field of a frame that is sent in response to a DSE Measurement Request frame shall not contain a value of 1 for the Incapable subfield and shall not contain a value of 1 for the Refused subfield of the Measurement Report Mode field of the DSE measurement report. A dependent STA receiving an Extended Channel Switch action frame from the enabling STA with which it last attempted enablement or an ECS element from the AP with which it is associated shall perform the ECS procedure (see 10.10.3 (Selecting and advertising a new channel and/or operating class)). An enabled dependent STA shall cease transmission within [60 seconds] if it has not received [an Enabling Signal]. It shall then change its enablement state with the enabling STA to unenabled and set all fields of its DSE Registered Location element body (see 7.3.2.52) to 0. Peter Ecclesine, Cisco

Mapping 802.11 Enablement into TVWS(1) September 2010 Mapping 802.11 Enablement into TVWS(1) FCC requires a master/client network specification as a basis to test and approve client devices and master devices. The geographic coordinates of a fixed TVBD shall be determined to an accuracy of +/- 50 meters by either an incorporated geo-location capability or a professional installer. In the case of professional installation, the party who registers the fixed TVBD in the database will be responsible for assuring the accuracy of the entered coordinates. All master devices must tell the database their location to within 50 meters. Fixed and Mode II TVBDs shall not transmit unless they receive, from the TV bands database, a list of available channels. Peter Ecclesine, Cisco

Mapping 802.11 Enablement into TVWS(2) September 2010 Mapping 802.11 Enablement into TVWS(2) FCC Fixed can be either Enabling STA or Dependent STA or neither FCC Personal/portable can be either Enabling STA or Dependent STA or neither 802.11 Enabling STA is an AP and FCC Master device 802.11 Dependent STA that is not an AP is an FCC Client device There are several possibilities for AP operation – see next slide Peter Ecclesine, Cisco

Mapping 802.11 Enablement into TVWS(3) September 2010 Mapping 802.11 Enablement into TVWS(3) Where an 802.11 AP is FCC certified as a Master device, and its location is known to an Enabling STA, can it operate as a Client device and send an Enabling Signal under control of an Enabling STA if such operation is described in master/client network specification? Where an 802.11 AP is FCC certified as a Master device, and its location is known to an Enabling STA, can it operate as a Client device and form a network under control of an Enabling STA if such operation is described in master/client network specification? Peter Ecclesine, Cisco

Mapping 802.11 Enablement into TVWS(4) September 2010 Mapping 802.11 Enablement into TVWS(4) Where an 802.11 AP is FCC certified as a Master device, can it’s functions use an external geo-location server for providing the database its FCC Identifier (as required by § 2.926 of this chapter), serial number as assigned by the manufacturer, and the device’s geographic coordinates (latitude and longitude (NAD 83) accurate to +/- 50 meters) if such operation is described in master/client network specification?? Where an 802.11 AP is FCC certified as a Master device, can it’s Authentication server provide identity and location services if such operation is described in master/client network specification? Peter Ecclesine, Cisco

CID 58 proposed resolution September 2010 CID 58 proposed resolution CID 58: Definition for "Enabling Signal" is missing. There has been no definition as such even inside clause 11.11 of 802.11y on what could be considered as an enabling signal itself, but text description within 11.11.4 and 11.11.5 indicates that "DSE Registered Location" element in any frame with RegLoc DSE bit set to 1 is the main qualifier to be an enabling signal. Since it is used in several places, it is good to have a clear definition for this. Proposed Resolution: Agree in Principle, 11-10/737r3 Approved in July 2010, provides clear definition of Enabling Signal for each appropriate Annex E band. No changes required. Peter Ecclesine, Cisco

CID 65 proposed resolution September 2010 CID 65 proposed resolution CID 65: (on PICS) considering a WLAN BSS where an AP provides enabling signal to non-AP STAs (dependent or client STAs), and already they work under control of AP, there are no additional regulatory requirements that these client STAs need to do DSE enablement procedure to operate in TVWS band. Proposed change: clarify. Discussion: With 802.11af D0.04, the baseline shifted to REVmb, and the removal of all regulatory requirements from our baseline. Regarding 11af PICS item WS3.1, References 10.12.5, Annex D, Annex E.2.4: as discussed in 11-10/996 slides 9 and 10, clause 10.12.5 specifies many non-regulatory requirements that dependent STAs must meet, in addition to all regulatory requirements. Proposed Resolution: Agree in Principle, Approved Draft D0.03 changed the TGaf baseline to REVmb, and removed the specification of regulatory requirements from the baseline and amendment. No changes required. Peter Ecclesine, Cisco

References 47 C.F.R 15 Radio Frequency Devices IEEE Std 802.11y-2008 September 2010 References 47 C.F.R 15 Radio Frequency Devices IEEE Std 802.11y-2008 Draft P802.11REVmb_D5.0.pdf Draft P802.11u_D11.0.pdf Draft P802.11af_D0.05.pdf Peter Ecclesine, Cisco