1 / 9

Interfacing the White Space Database

Interfacing the White Space Database. Authors:. Date: 11/3/2010.

elkan
Download Presentation

Interfacing the White Space Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interfacing the White Space Database Authors: Date:11/3/2010 Notice:This document has been prepared to assist IEEE 802.19. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Jesse Caulfield, Key Bridge Global LLC

  2. Abstract FCC Rules envision eight unique database communications, two of which are relevant for devices. Here we survey all eight types, detail the “channel-list” communications, and discuss current thinking on data exchange and security frameworks. Jesse Caulfield, Key Bridge Global LLC

  3. A High-Level White Space Database CM/CDIS Jesse Caulfield, Key Bridge Global LLC

  4. 47 CFR § 15.715 (e) TV bands database administrator. • Required Services • Shall provide accurate lists of available channels to fixed and personal/portable TVBDs …. • Optional Services • [May] allow prospective operators of TV bands devices to query the database …. TV Bands Database Services Jesse Caulfield, Key Bridge Global LLC

  5. A common query and response message format is required. Messages should lend themselves to simple machine parsing, storage, search and retrieval. Messages should be human readable, self-explanatory and contextually complete (atomic). Messages should contain a globally unique identifying information (i.e. a serial number) and a time stamp. IEEE 802.22 proposed an message structure that may be acceptable if extended. Interface C: Information Exchange Jesse Caulfield, Key Bridge Global LLC

  6. Must also agree on a data and encoding strategy Extending the 802.22 Message Structure Jesse Caulfield, Key Bridge Global LLC

  7. FCC Rules do not prescribe a security implementation. Rather, the rules require that: • Information is protected from modification (data encryption) • Parties are identified (mutual authentication) • Two primary security methods are presently under consideration: • Transport security • IPSEC or TLS tunnels with mutual authentication • Message security • XML encryption via WS-Security • Both using digital certificates and PKI Interface C: Security Framework Jesse Caulfield, Key Bridge Global LLC

  8. In 802.19 context, CDIS may exist outside a TV Band Device (e.g. deployment case 1). • This is allowed. • May employ “Interface C” or, more likely, a Non-TVBD interface. • If CDIS is decoupled from a transmitter, CDIS may freely query a White Space database according to any desired parameter, including: • Geographic location • Time (past, present, future) • Device type (e.g. Fixed, Mode II, Mode II-Mobile, Mode I) • Device configuration (e.g. various antenna heights) • Security framework is not required • Subject to each administrator’s availability and commercial policies • Note: no scenarios allow a TVBD to not query a Database prior to transmitting or to transmit on a channel not identified by the Database Non-TVBD Information Exchange Jesse Caulfield, Key Bridge Global LLC

  9. References • 47 CFR PART 15 Subpart H - Television Band Devices • http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=94e8103abff7a1d088b158e90946cbf4&rgn=div6&view=text&node=47:1.0.1.1.14.8&idno=47 • (Note: Does not reflect final Memorandum & Order) • IEEE 802.22 Working Group on Wireless Regional Area Networks • http://www.ieee802.org/22/ • WS-Security • http://www.oasis-open.org/committees/wss • The National Marine Electronics Association (NMEA) NMEA 0183 Standard • http://www.nmea.org Jesse Caulfield, Key Bridge Global LLC

More Related