Oct. 2010
doc.: IEEE 802.19-10/151r0
Interfacing the White Space Database
Date: 11/3/2010
Authors:
Name
Jesse Caulfield
Company
Address
Phone
email
Key Bridge Global
LLC
1600 Tysons Blvd., Suite
450
703 414 3500
jesse.caulfield@keybridge
global.com
McLean, VA 22102
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.
Submission
Slide 1
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
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.
Submission
Slide 2
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
A High-Level White Space Database
CM/CDIS
FCC Resources and
Functions
White Space Database
Database Clients
Network Nodes
TVBD Mode I
Channel Inquiry
Oversight, Reporting
& Enforcement
proprietary
“Interface C”
TVBD
Channel Query
Protected
Transmitters
internal
tbd (new)
TV Band Device
Identity Verification
Equipment
Authentication
internal
proprietary
Protected Services
Records Management
proprietary
Protected Services
Voluntary Registration
proprietary
Other White Space
Databases
Submission
Slide 3
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
TV Bands Database Services
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 ….
Submission
Slide 4
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
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 802.22 proposed an message structure that may
be acceptable if extended.
Submission
Slide 5
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
Extending the 802.22 Message Structure
802.22 Query
Device Type
Device ID
Serial Number
Device Location
Timestamp
802.22 Response
White Space Query
Device ID
Serial Number
Device Flag
# of Available Channels
Channel List
For avail. channels:
Channel #
Max ERP
Device ID
Serial Number
Timestamp
Device Location
Optional
Device Type
Antenna Height
Channel Number
Account Number
Availability Schedule
Timestamp
White Space Response
Message Serial #
Timestamp
Device ID
Serial Number
Device Location
Channel List
For: 0 to Max value
Channel Code
Optional
Error Codes List
Max ERP
Notes
• Must also agree on a data and encoding strategy
Submission
Slide 6
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
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
Submission
Slide 7
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
Non-TVBD Information Exchange
•
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
Submission
Slide 8
Jesse Caulfield, Key Bridge Global LLC
Oct. 2010
doc.: IEEE 802.19-10/151r0
References
•
47 CFR PART 15 Subpart H - Television Band Devices
– http://ecfr.gpoaccess.gov/cgi/t/text/textidx?c=ecfr&sid=94e8103abff7a1d088b158e90946cbf4&rgn=div6&view=text&nod
e=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
Submission
Slide 9
Jesse Caulfield, Key Bridge Global LLC