FCC Logo - Return to the FCC Home Page
Office of Engineering and Technology

  


Publication Number: 848637 Rule Parts: 15E Publication Date: 01/10/2014
Keyword: UNII Client Device without Radar Detection, DFS Test Report, Section 15E, 15.407, FCC 06-96,

First Category: Unlicensed Service Rules and Procedures
Second Category: UNII devices- 15.401

Question:  

What additional Form 731 filing information, not specified in Section 8 (DFS Test Report Guidelines) in MO&O FCC 06-96 (DFS Order), is required in order for a DFS device to be approved as a UNII client device without radar detection capability operating in the 5.25 - 5.35 GHz and 5.45 - 5.725 GHz bands?




Answer:  

Devices to be approved as UNII client devices without radar detection capability must be compliant with all the general requirements of clients as specified in Section 15.202, in addition to the appropriate technical requirements of Part 15E. According to the requirements of Section 15.202, a client device must rely on a master device to initiate a network. This requires that such a client device cannot initiate, or be configured to initiate, any transmissions including transmissions from probes, beacons or support ad-hoc modes (or other peer to peer modes) of operation without permission from an approved master device with radar detection capability. This places certain restrictions on such devices, for example:

(a) The operation of a client device as a Group Owner for Wi-Fi Direct or TDLS in the UNII bands is limited; only where it is either communicating with a device approved as a master according to the requirements of Section 15.202 or if the device is operating under control of an approved master. In the case of device using IEEE 802.11 protocols, the device does not have to be associated with a master, but it must be listening to a master device on the same channel and must move channels when the master announces a channel move command.

(b) Client devices cannot operate in Wi-Fi ?hotspot? modes. Devices with ?hotspot? capabilities must have DFS and radar detection capabilities.

(c) See KDB Publication 594280 for further information and other considerations for client devices with software configurations...

The following information should be included in the test report;

i. A complete test report for a client device without radar detection as described in Section 8 (DFS Test Report Guidelines) in the DFS Order (FCC 06-96) (see also KDB Publication 905462)

ยท Special case for IEEE 802.11ac clients operating with 80 MHz BW modes: Client devices with 80 MHz BW mode can be tested with an approved master operating in 40 MHz BW mode. Test procedures for client devices s with 80 + 80 MHz and 160 MHz BW modes must be approved using permit-but-ask (PBA) procedures (KDB Publication 388624). This is an interim solution until a few IEEE 802.11ac master devices with the various BW modes are approved.

ii. A test report attachment for the client operating in an associated mode as discussed in (a) above that includes documentation for the following:

a. Test results demonstrating an associated client link is established with the master on a test frequency; if a client device operates in a ?listen only? mode to a master without formally ?associating? with it the test report must include tests for such modes;

b. The devices must be tested with a master device operating in the same band and operation modes.

c. If two client devices can communicate directly with each other while maintaining an association with a master or if the client operates on a frequency band while ?listening? to a master, such modes must be tested with the master device active.

d. The client and DFS-certified master device are associated, and a movie can be streamed as specified in the DFS Order for a non-occupancy period test

e. The test frequency has been monitored to ensure no transmission of any type has occurred for 30 minutes. Note: If the client moves with the master, the device is considered compliant if nothing appears in the client non-occupancy period test. For devices that shut down (rather than moving channels), no beacons should appear.

f. An analyzer plot that contains a single 30-minute sweep on the original channel

iii. A complete User?s Manual and/or Professional Installers Manual. If the manual is not complete, upload an initial manual and later an updated User?s Manual exhibit.

iv. A Statement of Conformity for the Client in Non-Associated mode is required. The Form 731 application must include a Cover Letter Attachment stating that the client software and associated drivers will not initiate any transmission on DFS frequencies without initiation by a master. This includes restriction on transmissions for beacons and support for ad-hoc peer-to- peer modes.

v. A channel/frequency plan for the device showing the channels that have active scanning or passive scanning. Active scanning is where the device can transmit a probe (beacon) and passive scanning is where the device can listen only without probes.

vi. For client devices that have software configuration control to operate in different modes (active scanning in some and passive scanning in others) or in different bands (devices with multiple equipment classes or those that operate on non-DFS frequencies), or modular devices that configure the modes of operations through software; the applicant must provide in the equipment authorization application a software and operations description that discuss how the software and / or hardware is implemented to ensure that proper operations modes cannot be modified by an end user or an installer. Also, include an attestation that the device complies with the requirements for software configuration control as discussed in KDB # 594280.


 



Please use the Submit Inquiry link at www.fcc.gov/labhelp to send any comments or suggestions for this site

Skip FCC Footer and Contact InfoFederal Communications Commission
445 12th Street, SW
Washington, DC 20554
More FCC Contact Information...
Phone:  888-CALL-FCC (225-5322)
TTY:  888-TELL-FCC (835-5322)
Fax:  202-418-0232
E-mail:  fccinfo@fcc.gov
- Privacy Policy
- Web Policies & Notices
- Customer Service Standards
- Freedom of Information Act