Presentation is loading. Please wait.

Presentation is loading. Please wait.

P System Architecture Date: Authors: March 2010

Similar presentations


Presentation on theme: "P System Architecture Date: Authors: March 2010"— Presentation transcript:

1 P802.19.1 System Architecture Date: 12-03-2010 Authors: March 2010
Month Year doc.: IEEE yy/xxxxr0 March 2010 P System Architecture Date: Authors: Name Company Address Phone Aziz Rahman NICT 3-4, Hikarino-oka, Yokosuka, Kanagawa, Japan, Päivi Ruuska Nokia Itämerenkatu 11-13, Helsinki, Finland Ha Nguyen Tran Mika Kasslin Stanislav Filin Juha Salokannel Chen Sun Yohannes D. Alemseged Gabriel Villardi Tuncer Baykas Hiroshi Harada 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. Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al Chen SUN, NICT

2 Abstract This contribution proposes P802.19.1 System Architecture
It describes logical entities and their interfaces to enable coexistence on TVWS Two illustrative deployment examples are described Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

3 Acronyms Used in the Presentation
AP Access Point CDB Coexistence Database CE Coexistence Enabler CM Coexistence Manager TVBD Television Band Device WS White Space OME Operator Management Entity Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

4 System Architecture Logical entities Interfaces External element
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 Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

5 Logical Entities 802.19.1 logical entity
IEEE logical entity is defined by its functional role(s) and interfaces with other IEEE logical entities and with external elements Three types of logical entities are defined Coexistence Enabler (CE) Coexistence Manager (CM) Coexistence Database (CDB) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

6 Logical Entities Coexistence Enabler (CE)
Functions related to the functional role of the entity Obtain information, required for coexistence, from TVBD network or device This includes configuration and control of measurements performed by TVBD network or device Provide reconfiguration commands and control information, corresponding to coexisting decisions received from CM, to TVBD network or device Functions related to the interfaces of the entity Obtain information required for coexistence from TVBD network or device (interface A) Provide information required for coexistence to CM (interface B1) information obtained from TVBD network or device Obtain coexistence commands and control information from CM (interface B1) Provide reconfiguration commands and control information to TVBD network or device (interface A) commands and control information corresponding to coexisting commands and control information received from CM Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

7 Logical Entities Coexistence manager (CM)
Functions related to the functional role of the entity Coexistence decision making. This includes generating and providing corresponding coexistence commands and control information to CE(s) Discovery of other CMs To solve coexistence problems between the TVBD networks they serve Supporting exchange of information required for coexistence among CMs. Assist network operators in management related to TVWS coexistence. Functions related to the interfaces of the entity Provide information required for discovery to CDB, i.e. registration in CDB (interface B2) Obtain information required for discovery from CDB (interface B2) Obtain information required for coexistence from CE (information obtained by CE from TVBD network or device) (interface B1) Provide information facilitating coexistence to CDB (information received from CE(s)) (interface B2) Obtain information facilitating coexistence from CDB (e.g. information provided to CDB by other CMs) (interface B2) Obtain information required for coexistence from TVWS DB (information on available TV channels) (interface C1) Receive network operator spectrum policy from OME (interface E) Provide coexistence commands and control information to CE (interface B1) Exchange information and control messages required for coexistence with other CM(s) (interface B3) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

8 Logical Entities Coexistence Database (CDB)
Functions related to the functional role of the entity Support discovery of CMs by each other Facilitates opening interface between CMs which need to exchange information due CEs they serve Contain information facilitating coexistence and provide it to CM This includes data storage, data processing, etc Functions related to the interfaces of the entity Provide information required for discovery to CM (interface B2) Obtain information required for discovery from CM (registration information) (interface B2) Obtain information required for coexistence from TVWS DB (information on available TV channels) (interface D) Obtain information facilitating coexistence from CM (information provided to CM by CE(s)) (interface B2) Provide information facilitating coexistence to CM (e.g. information provided to CDB by other CMs) (interface B2) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

9 Interfaces 802.19.1 defines three groups of interfaces
Interface between entities Interface B1 Interface B2 Interface B3 Interface between an entity and TVWS network/devices Interface A Interface between entities and TVWS database or OME Interface C Interface D Interface E Different interfaces in each group are distinguished by their usage, types of information exchanged, and underlying protocols Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

10 Interfaces Interface between entity and TVBD network or device A: CE-TVBD network or device From TVBD network or device to CE Information required for coexistence From CE to TVBD network or device Reconfiguration commands and control information (corresponding to coexistence commands and control information received from CM) Commands related to control of measurements performed by TVBD network or device Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

11 Interfaces Interface between 802.19.1 entities B1: CE-CM From CE to CM
Information required for coexistence (information obtained from TVBD network or device) From CM to CE Coexistence commands and control information Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

12 Interfaces Interface between 802.19.1 entities B2: CM-CDB
From CM to CDB Information required for discovery (obtained by this CM) Information required for coexistence (obtained by this CM) From CDB to CM Information required for discovery (obtained by other CMs) Information required for coexistence (obtained by other CMs) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

13 Interfaces Interface between 802.19.1 entities B3: CM-CM
Between different CMs Information and messages required for discovery and coexistence Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

14 Interfaces Interface between 802.19.1 entities and TVWS DB or OME
C: CM-TVWS DB From TVWS DB to CM Information required for coexistence (information on available TV channels) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

15 Interfaces Interface between 802.19.1 entities and TVWS DB or OME
D: CDB-TVWS DB From TVWS DB to CDB Information required for coexistence (information on available TV channels) Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

16 Interfaces Interface between 802.19.1 entities and TVWS DB or OME
E: CM-OME From OME to CM: Network operator related information e.g. spectrum policy/limitations concerning operator networks. Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

17 Illustration of System Architecture
To illustrate the proposed System Architecture, two deployment scenarios are presented Different TVBD networks operated by one operator Centralized coexistence approach Different and independently operated TVBD networks or devices (operated by users or some local operators) Autonomous coexistence approach Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

18 Deployment scenario 1 CDB OME TVWS DB CM TVBD CE TVBD CE TVBD network
Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

19 Deployment scenario 1 Different TVBD networks operated by one operator: Centralized coexistence approach One CM is managing many CEs (i.e. TVBD networks or devices) CM is placed outside the TVBD devices and network OME provides coexistence policy to CM to assist TVDB devices or networks CDB helps CM in discovering other CM managing TVBD devices/networks in the area Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

20 Deployment Scenario 2 TVWS DB CBD TVBD CE CM TVBD CE CM TVBD network
Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

21 Deployment scenario 2 Different and independently operated TVBD networks or devices (operated by users or some local operators): Autonomous coexistence approach CM is placed inside the TVBD devices CDB helps CM discovering other CM managing TVBD devices/networks in the area All CMs are connected to CDB, but all CMs are not connected to TVWS BD Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al

22 Summary This contribution proposed high level system architecture for SDD It described logical entities and their interfaces to provide coexistence for TVBD networks and devices The architecture supports various coexistence deployments scenarios Two illustrative examples were given Aziz Rahman (NICT), Päivi Ruuska (Nokia) et al


Download ppt "P System Architecture Date: Authors: March 2010"

Similar presentations


Ads by Google