doc.: IEEE /151r0 Submission Oct Jesse Caulfield, Key Bridge Global LLCSlide 1 Interfacing the White Space Database Notice: This document has been prepared to assist IEEE 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. Date: 11/3/2010 Authors:

doc.: IEEE /151r0 Submission Oct Jesse Caulfield, Key Bridge Global LLCSlide 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.

doc.: IEEE /151r0 Submission Oct Jesse Caulfield, Key Bridge Global LLCSlide 3 A High-Level White Space Database CM/CDIS

doc.: IEEE /151r0 Submission TV Bands Database Services 47 CFR § (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 …. Oct Jesse Caulfield, Key Bridge Global LLCSlide 4

doc.: IEEE /151r0 Submission Interface C: Information Exchange 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 proposed an message structure that may be acceptable if extended. Oct Jesse Caulfield, Key Bridge Global LLCSlide 5

doc.: IEEE /151r0 Submission Extending the Message Structure Must also agree on a data and encoding strategy Oct Jesse Caulfield, Key Bridge Global LLCSlide 6

doc.: IEEE /151r0 Submission Interface C: Security Framework 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 Oct Jesse Caulfield, Key Bridge Global LLCSlide 7

doc.: IEEE /151r0 Submission Non-TVBD Information Exchange In 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 Oct Jesse Caulfield, Key Bridge Global LLCSlide 8

doc.: IEEE /151r0 Submission Oct Jesse Caulfield, Key Bridge Global LLCSlide 9 References 47 CFR PART 15 Subpart H - Television Band Devices – idx?c=ecfr&sid=94e8103abff7a1d088b158e90946cbf4&rgn=div6&view=text&nod e=47: &idno=47http://ecfr.gpoaccess.gov/cgi/t/text/text- idx?c=ecfr&sid=94e8103abff7a1d088b158e90946cbf4&rgn=div6&view=text&nod e=47: &idno=47 –(Note: Does not reflect final Memorandum & Order) IEEE Working Group on Wireless Regional Area Networks – WS-Security – The National Marine Electronics Association (NMEA) NMEA 0183 Standard –