Presentation is loading. Please wait.

Presentation is loading. Please wait.

Examples of deployment scenarios

Published byRafe Wiggins Modified over 5 years ago

Similar presentations

Presentation on theme: "Examples of deployment scenarios"— Presentation transcript:

1 Examples of deployment scenarios
Month Year doc.: IEEE yy/xxxxr0 March 2010 Examples of deployment scenarios Date: 2010-MM-DD Authors: 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. Päivi Ruuska, Nokia John Doe, Some Company

2 Month Year doc.: IEEE yy/xxxxr0 Abstract In this presentation a few possible coexistence deployment examples for proposed 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 system, e.g. AP, BS, or a device in a mesh network. A cloud presents a TVBD network. Päivi Ruuska, Nokia John Doe, Some Company

3 Proposed 802.19.1 system architecture (for reminder)
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) Scope Interface D Coexistence Database TVWS Database Interface C Interface B2 Coexistence Manager Interface B3 Coexistence Manager Operator Management Entity Interface E Interface B1 Coexistence Enabler Interface A TVBD network or device

4 Why we believe 802.19.1 is needed?
Month Year doc.: IEEE yy/xxxxr0 Why we believe 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 ? 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” . Clear benefits: mechanisms which would help to solve problems which a system will have even when no other systems, e.g. hidden node. Päivi Ruuska, Nokia John Doe, Some Company

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
CE – Coexistence Enabler CM – Coexistence Manager 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) Provides a list of available channels at a requested location. 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. 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 CE CM TVBD device CE CM TVBD network 5 TVBD device CE CM TVBD network 1 TVBD device CE CM TVBD device CE CM TVBD device CE CM 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 OME Connection between different entities. TVWS DB CM CDB TVBD device CE TVBD device CE TVBD network 5 TVBD network 1 TVBD device CE TVBD device CE TVBD device CE TVBD device CE 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 Connection between different entities. TVWS DB CDB OME “Independent” 5 TVBD device CE CM TVBD device CE CM TVBD device CE “Independent” 1 TVBD device CE CM TVBD device CE CM TVBD device CE “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 Connections Same as in example 3 Connection between different entities. TVWS DB CDB OME “Managed” 5 “Managed” 1 TVBD device CE TVBD device CE TVBD device CE TVBD device CE CM TVBD device CE TVBD device CE CM “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 architecture. Päivi Ruuska, Nokia

Download ppt "Examples of deployment scenarios"

Similar presentations

Doc.: IEEE 802.19-09/0046r0 Submission July 2009 Ari Ahtiainen, NokiaSlide 1 A Cooperation Mechanism for Coexistence between Secondary User Networks on.

Doc.: IEEE /0046r0 Submission July 2009 Ari Ahtiainen, NokiaSlide 1 A Cooperation Mechanism for Coexistence between Secondary User Networks on.
Doc.: IEEE 802.19-10/0165r1 SubmissionPäivi Ruuska, NokiaSlide 1 Implementation aspects of a 802.19.1 coexistence system Notice: This document has been.

Doc.: IEEE /0165r1 SubmissionPäivi Ruuska, NokiaSlide 1 Implementation aspects of a coexistence system Notice: This document has been.
Doc.: IEEE 802.19-09-0061-00-tvws Submission September 2009 Stanislav Filin et al, NICTSlide 1 Comments to WS coexistence draft PAR Notice: This document.

Doc.: IEEE tvws Submission September 2009 Stanislav Filin et al, NICTSlide 1 Comments to WS coexistence draft PAR Notice: This document.
Submission doc.: IEEE 802.19-15/0010r0 January 2015 Sho Furuichi, SonySlide 1 Coexistence Scenario and Use Cases Date: 2015-01-13 Authors: Notice: This.

Submission doc.: IEEE /0010r0 January 2015 Sho Furuichi, SonySlide 1 Coexistence Scenario and Use Cases Date: Authors: Notice: This.
Submission doc.: IEEE 802.19-15/XXXXr0 Month Year John Doe, Some CompanySlide 1 Insert Presentation Title Here Date: YYYY-MM-DD Authors: Notice: This document.

Submission doc.: IEEE /XXXXr0 Month Year John Doe, Some CompanySlide 1 Insert Presentation Title Here Date: YYYY-MM-DD Authors: Notice: This document.
Submission doc.: IEEE 802.19-15/0032r0 April 2015 Sho Furuichi, SonySlide 1 The new coexistence use cases for IEEE 802.19.1 Date: 2015-04-08 Authors: Notice:

Submission doc.: IEEE /0032r0 April 2015 Sho Furuichi, SonySlide 1 The new coexistence use cases for IEEE Date: Authors: Notice:
Doc.: IEEE 802.19-12/0021r0 Submission May 2012 Mika Kasslin, NokiaSlide 1 Coexistence system in a cognitive radio testbed Notice: This document has been.

Doc.: IEEE /0021r0 Submission May 2012 Mika Kasslin, NokiaSlide 1 Coexistence system in a cognitive radio testbed Notice: This document has been.
Doc.: IEEE 802.19-10/0104r0 Submission July 2010 Alex Reznik, et. al. (InterDigital)Slide 1 Channel Selection Support in TVWS Date: 2010-07-14 Authors:

Doc.: IEEE /0104r0 Submission July 2010 Alex Reznik, et. al. (InterDigital)Slide 1 Channel Selection Support in TVWS Date: Authors:
Doc.: IEEE 802.11-10/0262r1 Submission March 2010 Ha-Nguyen Tran et al., NICTSlide 1 Requirements and Amendment Regarding TVWS Database Access Notice:

Doc.: IEEE /0262r1 Submission March 2010 Ha-Nguyen Tran et al., NICTSlide 1 Requirements and Amendment Regarding TVWS Database Access Notice:
Doc.: IEEE 802.15-11/0287r0 Submission March 2011 Slide 1Hyunduk Kang, et al, ETRI 802.19.1 Overview and Issues Notice: This document has been prepared.

Doc.: IEEE /0287r0 Submission March 2011 Slide 1Hyunduk Kang, et al, ETRI Overview and Issues Notice: This document has been prepared.
Doc.: IEEE 802.19-11/0002r1 Submission January 2011 Päivi Ruuska, NokiaSlide 1 Neighbor Setting Procedures Notice: This document has been prepared to assist.

Doc.: IEEE /0002r1 Submission January 2011 Päivi Ruuska, NokiaSlide 1 Neighbor Setting Procedures Notice: This document has been prepared to assist.
Submission doc.: IEEE 802.19-15/0097r0 November 2015 Sho Furuichi, SonySlide 1 Information exchange between independent IEEE 802.19.1 systems Date: 2015-11-xx.

Submission doc.: IEEE /0097r0 November 2015 Sho Furuichi, SonySlide 1 Information exchange between independent IEEE systems Date: xx.
Doc.: IEEE 802.19-11/0061r0 Submission June 2011 Mika Kasslin, NokiaSlide 1 Discovery system overview Notice: This document has been prepared to assist.

Doc.: IEEE /0061r0 Submission June 2011 Mika Kasslin, NokiaSlide 1 Discovery system overview Notice: This document has been prepared to assist.
Submission doc.: IEEE 802.19-16/0011r2 January 2016 Sho Furuichi, SonySlide 1 System architecture for information exchange between independent IEEE 802.19.1.

Submission doc.: IEEE /0011r2 January 2016 Sho Furuichi, SonySlide 1 System architecture for information exchange between independent IEEE
Doc.: IEEE 802.19-10/41r0 SubmissionSlide 1 P802.19.1 System Architecture Notice: This document has been prepared to assist IEEE 802.19. It is offered.

Doc.: IEEE /41r0 SubmissionSlide 1 P System Architecture Notice: This document has been prepared to assist IEEE It is offered.
Doc.: IEEE 802.19-10/20rev0 SubmissionSlide 1 P802.19.1 Assumptions and Architecture Notice: This document has been prepared to assist IEEE 802.19. It.

Doc.: IEEE /20rev0 SubmissionSlide 1 P Assumptions and Architecture Notice: This document has been prepared to assist IEEE It.
Doc.: IEEE 802.19-12/0013r0 Submission January 2012 Mika Kasslin, NokiaSlide 1 Motivation for Monitor WSO Notice: This document has been prepared to assist.

Doc.: IEEE /0013r0 Submission January 2012 Mika Kasslin, NokiaSlide 1 Motivation for Monitor WSO Notice: This document has been prepared to assist.
Doc.: IEEE 802.19-10/129r0 Submission September 2010 Junho Jo/Jihyun Lee, LG ElectronicsSlide 1 IEEE 802.19.1 System description Notice: This document.

Doc.: IEEE /129r0 Submission September 2010 Junho Jo/Jihyun Lee, LG ElectronicsSlide 1 IEEE System description Notice: This document.
Submission doc.: IEEE 802.19-16/0015r0 January 2016 Sho Furuichi, SonySlide 1 Proposal for CM discovery/selection/ association as CE operation Date: 2016-01-19.

Submission doc.: IEEE /0015r0 January 2016 Sho Furuichi, SonySlide 1 Proposal for CM discovery/selection/ association as CE operation Date:
Doc.: IEEE 802.19-10/0037r0 Submission February 2010 Joe Kwak (InterDigital)Slide 1 TVWS Architecture for SDD Date: 2010-02-25 Authors: Notice: This document.

Doc.: IEEE /0037r0 Submission February 2010 Joe Kwak (InterDigital)Slide 1 TVWS Architecture for SDD Date: Authors: Notice: This document.

Similar presentations

Ads by Google