1 / 12

Examples of deployment scenarios

Examples of deployment scenarios. Authors:. Date: 2010-MM-DD.

nancy
Download Presentation

Examples of deployment scenarios

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. Examples of deployment scenarios Authors: Date: 2010-MM-DD 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. Päivi Ruuska, Nokia

  2. Abstract • In this presentation a few possible coexistence deployment examples for proposed 802.19.1 system architecture (DCN46) are presented. • Coexisting TVWS networks may be using different technologies and have different ranges. • In these deployment examples one device in a TVBD network is compliant with 802.19.1 system, e.g. AP, BS, or a device in a mesh network. A cloud presents a TVBD network. Päivi Ruuska, Nokia

  3. Proposed 802.19.1 system architecture (for reminder) 802.19.1 Scope Interface D Coexistence Database TVWS Database Interface B2 Interface C Interface B3 Coexistence Manager Coexistence Manager Operator Management Entity Interface E Interface B1 Coexistence Enabler Interface A TVBD network or device • Logical entities • Coexistence Manager • Coexistence Enabler • Coexistence Database • Interfaces • Interface A • Interface B1 • Interface B2 • Interface B3 • Interface C • Interface D • Interface E • External element • TVWS database • TVBD network or device • Operator management entity (OME)

  4. Why we believe 802.19.1 is needed? • Problem: Multiple spectrum users (TVBD networks) use same frequencies, at the same time, in the same area. • TV WS is new unlicensed band • Available for multiple technologies. • Available for various network deployers. • No legacy secondary systems = > possible to introduce coexistence mechanisms before coexistence problems are an issue. • Why to implement and use 802.19.1? • benefits be should be clear for manufacturers. • easy & low cost to implement and use. => introduce simple mechanisms applicable for unlicensed use to improve local coexistence, “enhanced listen-before-talk” . Päivi Ruuska, Nokia

  5. How to provide coexistence between the secondary spectrum users? • We have proposed a Coexistence Manager to solve coexistence problems of TVBD networks it serves based on rules, limitations and available information of other secondary users. • Available information: from CE, other CMs which serve neighboring TVBD networks, and CDB. • CDB helps to discover if possible coexistence problem exists, i.e. other TVBD networks operating in the same area. • Rules/limitations: included in system and from external entities (TVBD DB, OME). Päivi Ruuska, Nokia

  6. Summary of proposed 802.19.1 entities CM – Coexistence Manager CE – Coexistence Enabler CDB – Coexistence Database • Implements decisions in TVBD network. • Configures TVDB operational parameters according CM decisions. • Collects information from TVBD network/device e.g. radio environment and resource needs of the network. • Resides in a TVBD device. • Solves coexistence problems. • Makes decisions on operational parameters of TVBD network/s it serves. • Exchanges information/ commands with other CMs to solve the coexistence conflicts of the TVDB networks they serve. • Information for decision making from CE, CDB, and external entities (e.g. TVWS DB and OME). • Resides in a TVDB device or in network. • Stores information to assist CM in decision making. • Discovery information - enables CM to discover possible coexistence conflicts, and the CMs with which problems can be solved. • CMs register information of TVWS networks they serve. • Possible statistics of the spectrum use… • CDB may connect to external elements (e.g. TVWS DB) to collect information. In the following pictures this interface is not visible. • Resides in network. Päivi Ruuska, Nokia

  7. Summary of 802.19.1 external elements TVWS Database (TVWS DB) Operator management entity (OME) Possible operator provided information (e.g. operator related policies/ limitations) to CMs which manage operator networks. This is not provided for all networks. Similar external entity may also provide local regulations etc. • Provides a list of available channels at a requested location. Päivi Ruuska, Nokia

  8. Example 1: all networks in the area are “independent” Connections Internal: -CM connects to its CE. -CM connects to CDB for discovery information. -CM connects to other CMs which are managing networks using the same resources (=same frequencies at the same time, in the same area) as the network CM serves. External: -CM connects to TVWS DB for available channel information. (-CM managing operator networks connects to possible OME for operator provided information.) Connection between CMs to solve coexistence conflicts of their networks Connection between different entities. TVWS DB CDB TVBD device TVBD device TVBD device TVBD device TVBD device TVBD device CM CM CM CM CM CM CE CE CE CE CE CE TVBD network 5 TVBD network 1 TVBD network 6 TVBD network 2 TVBD network 3 TVBD network 4 Slide 8 Slide 8 Slide 8 Päivi Ruuska, Nokia Päivi Ruuska, Nokia

  9. Example 2: all networks in the area are “centrally managed” by one entity. Connections Internal: -CM connects to its CEs. -CM connects to CDB for discovery information. => No conflicting networks managed by other CMs in the area. External: -CM connects to TVWS DB for available channel information. -CM connects to OME if managing operator networks. Connection between CMs to solve coexistence conflicts of their networks TVBD device TVBD device TVBD device TVBD device TVBD device TVBD device CE CE CE CE CE CE Connection between different entities. OME TVWS DB CM CDB TVBD network 5 TVBD network 1 TVBD network 6 TVBD network 2 TVBD network 3 TVBD network 4 Slide 9 Slide 9 Slide 9 Päivi Ruuska, Nokia Päivi Ruuska, Nokia

  10. Example 3: some networks in the area are “independent” and some “centrally managed”. Connections Internal: -CM connects to its CEs. -CM connects to CDB for discovery information. -CM connects to other CMs which are managing networks using the same resources as the networks CM serves. External: -CM connects to TVWS DB for available channel information. -CM managing operator networks connects to possible OME for operator provided information. Connection between CMs to solve coexistence conflicts of their networks TVBD device TVBD device TVBD device CE CE CE Connection between different entities. TVWS DB CDB OME TVBD device TVBD device TVBD device CM CM CM CE CE CE “Independent” 5 “Independent” 1 CM “Managed” 6 “Independent” 2 “Managed” 3 “Managed” 4 Slide 10 Slide 10 Slide 10 Päivi Ruuska, Nokia Päivi Ruuska, Nokia

  11. Example 4: All networks in the area are “centrally managed” but by different CMs. Connection between CMs to solve coexistence conflicts of their networks TVBD device TVBD device TVBD device TVBD device CE CE CE CE Connection between different entities. Connections Same as in example 3 TVWS DB CDB OME TVBD device TVBD device CM CM CE CE “Managed” 5 “Managed” 1 “Managed” 6 “Managed” 2 “Managed” 3 “Managed” 4 Slide 11 Slide 11 Slide 11 Päivi Ruuska, Nokia Päivi Ruuska, Nokia

  12. Summary • This presentation presents some deployment examples for proposed 802.19.1 architecture. Päivi Ruuska, Nokia

More Related