1 / 41

Coexistence in the TV White Space

Coexistence in the TV White Space. Authors:. Date: 2010-07-12. Disclaimer.

gilmorer
Download Presentation

Coexistence in the TV White Space

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. Coexistence in the TV White Space Authors: Date: 2010-07-12 Steve Shellhammer, Qualcomm

  2. Disclaimer • “At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE.” • IEEE-SA Standards Board Operation Manual (subclause 5.9.3) Steve Shellhammer, Qualcomm

  3. Tutorial Outline • Introduction • Brief overview of FCC rules • Standards activities in TVWS • Need for Coexistence • The Coexistence Problem • TVWS Use Cases • IEEE 802.19.1 Project • Project Title, Scope and Purpose • Project Timeline • System Design Document • Possible Coexistence Solutions • Leverage incumbent protection mechanisms for TVWS coexistence • Modify network/device parameters to improve coexistence Steve Shellhammer, Qualcomm

  4. FCC Rules on TVWS • In November 2008 the FCC issued a Report and Order (R&O) on unlicensed wireless use of unused TV channels, called TV white space (TVWS) • A number of petitions for reconsiderations were filed and the FCC still needs to respond to the petitions. Current forecasts are for the FCC to respond by the end this year. • In any given location in the US there are a number of TV channels unused by the broadcast industry. The number varies significantly from location to location • Each channel is 6 MHz wide • Channels are in the VHF and UHF frequency bands • Details in a subsequent slide • FCC defines two classes of TVWS devices • Fixed • Portable Steve Shellhammer, Qualcomm

  5. FCC Rules on TVWS Permissible TV Channels Steve Shellhammer, Qualcomm

  6. FCC Rules on TVWS • Fixed devices use outdoor antenna • Between 10 and 30 meters above ground • Permitted TX Power • Fixed – 30 dBm with up to 6 dBi antenna gain • Portable – 20 dBm with no antenna gain • Adjacent TV Channels • Fixed – Not permitted • Portable – Reduce power to 16 dBm • Strict Out-of-band Emissions • Classes of Portable Devices • Mode I – Client • Mode II – Access Point Steve Shellhammer, Qualcomm

  7. FCC Rules on TVWS • Geo-location & Database access • Must be supported in both Fixed and Portable Mode II devices • Accuracy of 50 meters • FCC will certify the official databases • Spectrum Sensing • ATSC and NTSC TV signals • Wireless microphones • Sensing down to -114 dBm (approx -15 dB SNR) • Will consider “sensing-only” devices but with much more stringent testing required Steve Shellhammer, Qualcomm

  8. Non-US TVWS Rules • Other regulatory regions are also preparing TVWS rules • Some of the regulatory regions working on TVWS rules include • Canada • United Kingdom • Singapore • Nederland Antilles • Finland • The rules in these regions are likely to have some similarities with the US rules but will likely not be exactly the same • In other parts of the world the TV channel bandwidths are 6, 7 and 8 MHz. So TVWS support for these different bandwidth is expected Steve Shellhammer, Qualcomm

  9. TVWS Related Standard Projects Steve Shellhammer, Qualcomm

  10. TVWS Related Standard Projects Steve Shellhammer, Qualcomm

  11. Coexistence in TVWS: What is it? • TVWS presents a complex regulatory environment • Licensed devices: allowed to use the spectrum whenever, following appropriate rules • Unlicensed devices: permitted to use the spectrum when it is not occupied by licensed devices • Licensed and unlicensed devices do not coexist • Licensed devices make no special allowances for unlicensed devices • Unlicensed device must “protect” licensed operation by regulation • Protection of licensed devices is a medium access problem • Thou shall not access access spectrum when these guys are around Alex Reznik (InterDigital)

  12. Coexistence in TVWS: So what is it then? • Coexistence happens between peers • In TVWS, these are unlicensed devices and networks • Not mandated by regulations • Impetus must come from mutual benefit consideration: higher spectrum efficiency for all involved • Why do they need to coexist • Once available channels are known, the various networks and users need to decide – who goes where • This cannot be static – channel availability will change • Who specifies how this can be done • Some (not all) standards specify how different networks using same technology coexist • 802.11, 802.15 do this • Do they do it well?? • Some standards don’t even do that • cellular standards do not specify how different operators use the same spectrum • No MAC/PHY standard specifies how other MAC/PHY standards should behave • Nor should one MAC/PHY do it – it would rule over all the others • This void is filled by standards such as 802.19.1 in TVWS Alex Reznik (InterDigital)

  13. The Coexistence Problem: #1 “… you know you could help me out here. If you are on WiFi, if you could just get off…” “… we figured out why my demo crashed. Because there are 570 WiFi base stations operating in this room…” Steve Jobs see e.g. http://www.youtube.com/watch?v=yoqh27E6OuU So many talkers … … and no common language to discuss sharing Alex Reznik (InterDigital)

  14. The Coexistence Problem: #2 • So little spectrum … • So many ways to use it … 802.22 802.11 Bluetooth Bluetooth 802.11 802.11 802.11 Alex Reznik (InterDigital) • How we addressed in ISM bands • “Smart hopping” by Bluetooth • More robust (lower) bit rate by WiFi • “Autonomous” approaches may not work in TVWS • Much larger dynamic range in power (4W / 100 mW / 50mW / 40mW) • Potentially incompatible medium access techniques

  15. The Coexistence Problem :#3 Source: Mishra and Sahai, IEEE Comm. Letters, 2009 Source: Gerami, Mandayam, Greenstein. Report by Winlab, Rutgers U., 2010 Few people – many channels … Many people – few channel … Alex Reznik (InterDigital)

  16. Operation in TV Bands: Why Deal With the Headache? • TV Band Spectrum presents unique opportunities and possibilities • Potentially a lot of spectrum • But availability not guaranteed • Excellent propagation characteristics • Cover large distances • Penetrate walls, obstacles • So what could this be used for • Find additional bandwidth for data networks (in those areas where TV channels are many) • Offload to free up valuable (licensed) spectrum • Quick and cheap network deployment: cover a large area with few access points and little planning • Cheap spectrum for applications requiring only intermittent communication Alex Reznik (InterDigital)

  17. Example Use Case 1:Rural/Suburban Home/Small Office Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010 Alex Reznik (InterDigital)

  18. Example Use Case 1: Rural/Suburban Home/Small Office Alex Reznik (InterDigital) • Potential Uses • Device-to-Device (Machine-to-Machine) • WLAN Access • Backhaul • Cellular offload • Characteristics • Single operator controls much of the network and controls the space • Limited interference from like networks • Requires high data rates/no critical usage applications • Is this a good fit for white spaces • Yes, if the channels are available • Yes, if the operator (home owner) can automate the channel selection and coexistence of the various technologies he owns

  19. Example Use Case 2: Apartment Source: Paine et. al., IEEE doc. 802.19-09/26r4, Whitespace Coexistence Use Cases, 07/2009 • Similar usage to the home use case, but very different environment • Multiple operators • Each resident operates own network • No incentive to cooperate/coordinate • WWAN network may be overlayed into this space • Little spatial separation between the operators • Lots of networks crammed into a small spaces • Opens the possibility of the iPhone4 demo problem • Is this a good fit for white spaces • Maybe – but the inter-network coexistence problem will definitely need to be solved. Alex Reznik (InterDigital)

  20. Example Use Case 3: Utility Grid Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010 Alex Reznik (InterDigital)

  21. Example Use Case 3: Utility Grid • Potential uses • Collection of metered data • Reporting of aggregated data over the backhaul • SCADA support • Characteristics • Relative low-rate, can deal with intermittent outages • Single network operator, but spanning a large distance • High likelihood of interference with different network – this interference varies in nature and spectral location throughout the network • Is this a good fit for white spaces? • Absolutely • Covers large areas • Meters may need to penetrate obstacles • Requires only intermittent connectivity Alex Reznik (InterDigital)

  22. Example Use Case 4: Public Safety Source: Sum et. al., IEEE doc. Scc41-ws-radio-10/5r0, IEEE SCC41 Ad Hoc on WS Radio Usage Models, 04/2010 Alex Reznik (InterDigital)

  23. Example Use Case 4: Public Safety • Potential Usage • Rapid deployment of emergency personnel networks • Inter-personnel communication • Network backhaul • Communication to the main office • Characteristics • High-rate data rate services • Multi-media and conversational services • Creating an “instant network” where there was none • Is this a good match for white spaces • Yes, IF spectrum can be found, need to have backup plans. • Yes: need to create a network with few APs and no ability to plan • Yes: need penetration through obstacles • Yes: need the reach the main office Alex Reznik (InterDigital)

  24. 802.19.1 PAR • Title: IEEE 802 …Part 19: TV White Space Coexistence Methods • Scope: The standard specifies radio technology independent methods for coexistence among dissimilar or independently operated TV Band Device (TVBD) networks and dissimilar TV Band Devices. • Purpose: The purpose of the standard is to enable the family of IEEE 802 Wireless Standards to most effectively use TV White Spaceby providing standard coexistence methods among dissimilar or independently operated TVBD networks and dissimilar TVBDs. This standard addresses coexistence for IEEE 802 networks and devices and will also be useful for non IEEE 802 networks and TVBDs. • Study Group was established in March 2009. • The PAR was approved by Nescom in December 2009 and task group has been established. Tuncer Baykas, NICT

  25. 802.19 TG1 Timeline • Contribution • A submission on an issue relevant to the task group that may be in Powerpoint format. Contributions are expected to be submitted on issues that contributors are planning to submit as proposals later on in the draft development process. • Proposal • A submission that provides a solution proposal to a clause as defined in the System Design Document. The proposal shall include a document in Microsoft Word format that contains draft normative text proposal for a clause. • September 2010: System description • September 2010: The 802.19.1 reference model • September 2010-November 2010: Procedures and protocols • September 2010-November 2010: Coexistence mechanisms and algorithms Tuncer Baykas, NICT

  26. System Design Document • 802.19.1 created system design document to assist standardization process. • It provides, • System Requirements (What is expected from 802.19.1 system?) • 802.19.1 System Architecture (How 802.19.1 will provide coexistence?) • SDD does not put any limitation on future contributions and proposals. • http://ieee802.org/19/pub/TG1.html Tuncer Baykas, NICT

  27. 802.19.1 Architecture Logical Entities What is expected from 802.19.1 system? Requirement 4 (Communication) 802.19.1 system shall be able to provide reconfiguration requests and/or commands as well as corresponding control information to 802.19.1 compliant TVBD networks and devices to implement TVWS coexistence decisions. Requirement 1 (Discovery) 802.19.1 system shall enable discovery for 802.19.1 compliant TVBD networks and devices. Requirement 2 (Communication) 802.19.1 system shall be able to obtain and update information required for TVWS coexistence. Requirement 3 (Communication) 802.19.1 system shall have means to exchange obtained information. Tuncer Baykas, NICT

  28. 802.19.1 Architecture Logical Entities What is expected from 802.19.1 system? Requirement 8 (General) 802.19.1 system shall support appropriate security mechanisms. This shall include user/device authentication, integrity and confidentiality of open exchanges, and data privacy and policy correctness attestation and enforcement. Requirement 9 (General) 802.19.1 system shall utilize a set of mechanisms to achieve coexistence of TVBD networks and devices. Requirement 5 (Algorithm) 802.19.1 system shall analyze obtained information. Requirement 6 (Algorithm) 802.19.1 system shall be capable of making TVWS coexistence decisions. Requirement 7 (Algorithm) 802.19.1 system shall support different topologies of decision making for TVWS coexistence (e.g. centralized, distributed and autonomous). Tuncer Baykas, NICT

  29. 802.19.1 Architecture Tuncer Baykas, NICT

  30. TVWS Database Provides list of channels occupied by primary users. TV Band Device or TV Band Device Network Unlicensed operation in the broadcast television spectrum at locations where that spectrum is not being used by licensed services. Operator Management Entity Provides operator provided information such as policies/ limitations. Entities communicating with the 802.19.1 system Tuncer Baykas, NICT

  31. Coexistence Enabler Communication between Coexistence Manager and TVBD network or device Obtaining information, required for coexistence, from TVBD network or device Translating reconfiguration requests/commands and control information received from the Coexistence Manager into TVBD-specific reconfiguration requests/ commands Coexistence Manager Coexistence decision making This includes generating and providing corresponding coexistence requests/commands and control information to Coexistence Enabler(s) Discovery of and communication with other Coexistence Managers Assist network operators in management related to TVWS coexistence Coexistence Discovery and Information Server Providing coexistence related information to Coexistence Managers Supporting discovery of Coexistence Managers and opening interfaces between Coexistence Managers Collecting, aggregating information related to TVWS coexistence. Coexistence Discovery and Information Server may connect to TVWS database to obtain primary users information. Entities belonging to 802.19.1 System Tuncer Baykas, NICT

  32. Deployment of Entities Coexistence Enabler (CE) CEs can be deployed inside TV Band Devices or Network. CoexistenceManager (CM) CMs can be deployed inside the TV Band Device or Network. Also CMs can be deployed outside TV Band Networks. Coexistence Discovery and Information Server (CDIS) CDISs can be deployed outside TV Band Networks. Tuncer Baykas, NICT

  33. Possible Approach • TVBD networks and devices have mechanisms that are designed for e.g. interference management purposes • CM and CE can and should use those mechanisms for coexistence purposes • 802.19.1 builds upon existing mechanisms in the radio systems and has control functions for that purpose Mika Kasslin, Nokia

  34. Possible Control Parameters • Possible reconfiguration parameters in the TVBD networks • Operating channel • Maximum transmit power • Modulation and coding rate • Bandwidth • OFDMA uplink client sub-band • Transmit scheduling • CSMA parameters • Transmit duty cycle limit • Antenna configurations Mika Kasslin, Nokia

  35. Possible Control Functions • CM’s tool box in coexistence management comprises of tools in three main domains that form the main control functions • Time domain control • Recommendations, commands related to e.g. Transmit scheduling, Transmit duty cycle limit, Modulation and coding rate • Frequency domain control • Recommendations, commands related to e.g. Operating channel, Bandwidth, OFDMA uplink client sub-band • Spatial control • Recommendations, commands related to e.g. Antenna configuration, Maximum transmit power • The 802.19.1 system uses those tools to configure TVBD operations Mika Kasslin, Nokia

  36. Possible Decision Making Topologies • Not sure whether we can rely on one decision making model that can be applied in all the situations and deployments • We need to be prepared to provide means for all three topologies • Centralized • One CM serves all the neighboring networks and provides coexistence services for them • Distributed • Neighboring networks are served by different CMs • Autonomous • Information related to coexistence management is exchanged but that’s all Mika Kasslin, Nokia

  37. Possible Decision Making Topologies (cont.) • All the topologies have common solution elements • Information exchange between entities is needed • We need to provide security and trust • The few main differences are • Is there information exchange between CMs? • In centralized case the CMs have less need if any to exchange information while in the other two cases it is essential for the CMs to exchange information about environment, resource usage, etc. • What is the role of CM? • Centralized and Distributed • CMs are true coexistence managers that run coexistence control functions • In a distributed case the CM may have power over a CM of a neighboring network • Distributed vs. Autonomous • In autonomous case the CM may be only facilitating communication between CEs Mika Kasslin, Nokia

  38. Guiding Questions for the System Development • CE as defined in the SDD • Request and obtain information, required for coexistence, from TVBD network or device • What information we need from TVBD networks and devices? • How do we get the information? • Translate reconfiguration requests/commands and control information received from the CM into TVBD-specific reconfiguration requests/commands and send them to the TVBD network or device • What are the possible coexistence mechanisms? • How they are used in various TVBD networks? • How do we interface to various TVBD networks? Mika Kasslin, Nokia

  39. Guiding Questions for the System Development (cont.) • CM as defined in the SDD • Coexistence decision making • What are the control functions? • What’s needed to support different decision making topologies? • Support exchange of information required for coexistence among CMs • How to exchange coexistence information between decision making entities? Mika Kasslin, Nokia

  40. Workshop Coexistence for TVWS Free Workshop on Friday 1:00PM to 6:00PM Open to all Industry centric participants Outside 802 speakers and panelists 4 presentations and 3 Panels Open periods for discussion and Q&A Agenda available at: http://ieee802.org/19/pub/workshop.html Tuncer Baykas, NICT

  41. 802.19 TG1 Timeline Deadline for proposal intentions is 29th of August 2010 for September proposals. For details please check: Call for Proposals 802.19-10/0057r2 Tuncer Baykas, NICT

More Related