White Spaces Requirements Discussion Paul A. Lambert July 24, 2011
Some Requirement Areas for PAWS Protocol (versus device centric or FCC centric Requirements) Multiple Regulatory Authority Support Device Naming (by Multiple Authorities) Device Type Device Unique Id Band / Device Mode / Operating Class Naming (Names associated with Rules from an Authority) Naming of Device Operation Type ( within a set of Rules from an Authority) Example, specific spectral mask
Multiple Regulatory Authority Support The PAWS protocols must support multiple regulatory authorities. FCC is just one authority, KCC, China, Military are other examples Rules and band / channel definitions come from a Regulatory Authority Naming of Device Types, Rule Sets/Bands, etc must be rooted in Regulatory Authority Names of Regulatory Authorities do not necessarily map to countries or regions E.g. ITU Region 1 Registration of names / ids is required for Regulatory Authorities Regulatory Authority Geolocation Database (GBD) White Spaces Device (WSD)
Device Naming (bymultiple Authorities) PAWS protocol must support naming of devices by multiple Regulatory Authorities. Name spaces are typically given to a vendor Type names correspond to a certified class of devices (e.g. a particular cell phone) A hierarchical approach allows multiple authorities E.g. FCC XYZCORP123 KCC LGEEEE5QWX
Band / Device Mode / Operating Class Naming PAWS protocol must support naming of sets of rules from Regulatory Authorities Spectrum usage depends on rules from authority Channels are an artifact of rules Rules / bands / channels / power / adjacent interference are all shared knowledge between Regulatory Authority and WS Device that can be named Example FCC:TVWS_Fixed FCC:TVWS_Microphone
Naming of Device Operation Type PAWS protocol may support naming device operating characteristics OFCOM may allow support for different operating powers based on a particular devices specific characteristics Spectral mask determines adjacent interference
BACKUP SLIDES ON FCC
TV Band Device (TVBD) FCC Defined Device Types
TVBD Geolocation Scenarios Fixed-to-Fixed Geo-location or professional installer Secure access to TVB Database with device Id 4W max power (EIRP) Fixed Fixed Fixed Mode II GPS Fixed-toPortable Geo-location +/- 50m, check every 60 seconds Secure access to TVB Database with device Id 100mW power, 40mW when adjacent to incumbent TV channels useable: 21-36, 38-51 (470-692 Mhz) Secure access to TVB Database with device Id Mode I Mode II GPS Mode I Portable-to-Portable Mode II device MUST access database Initiates network on open channel Beacons indicate channel availability to Mode I
FCC Ruling the Good, the Bad and the Ugly gy What s Good Removed mandatory sensing (very good) Reduced protective zone for microphones from 1Km to 400m (good) Will add transmitters in Mexico and Canada to database (very good for San Diego) What s Bad 72.8 Spectral mask for adjacent emissions is too restrictive Personal/Portable devices must check location every 60 seconds What s Ugly Dedicated two channels for microphones (bad for urban area use) Limited antenna height site above ground (bad for rural use) All database access must be secure (yet to be determined what this means) Max power does not increase when adjacent channels are combined
DTV Spectral Mask Is it possible to use DTV as a reference for an appropriate spectral mask? Illustration from DTV Tutorial
Super Wi Fi Use Case TVWS extends Wi-Fi into new spectrum with better coverage TVWS has superior propagation and extends the reach of wireless networks and it enables: Wireless networking with longer range TVWS Wi-Fi network can be established with fewer APs / Repeaters TVWS Wi-Fi as a supplement to current Wi-Fi, can fill the coverage holes that are not covered by current twifi Wi-Fi. TV White Spaces delivers ~4x the range and ~10 x total area compared to 2.4 GHz