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

2 Abstract This version contains the updates discussed in architecture ad hoc discussions. This contribution proposes P System Architecture It describes logical entities and their interfaces to enable coexistence on TVWS Three deployment examples are described Ruuska (Nokia), Tran (NICT) 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 Ruuska (Nokia), Tran (NICT) et al

4 Coexistence Discovery and Information Server
System Architecture Logical entities Coexistence Manager Coexistence Enabler Coexistence Discovery and Information Server Interfaces Interface A Interface B1 Interface B2 Interface B3 Interface C Interface D External element TVWS database TVBD network or device Operator management entity (OME) Scope Interface C Coexistence Discovery and Information Server TVWS Database Interface C Interface B2 Coexistence Manager Interface B3 Coexistence Manager Operator Management Entity Interface D Interface B1 Coexistence Enabler Interface A TVBD network or device Ruuska (Nokia), Tran (NICT) 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 Discovery and Information Server (CDIS) Ruuska (Nokia), Tran (NICT) et al

6 Logical Entities Coexistence Enabler (CE)
Functions related to the functional role of the entity Request and obtain information, required for coexistence, from TVBD network or device Translate reconfiguration request/commands and control information received from the CM into TVBD-specific reconfiguration requests/commands and sends them to the TVBD network or device. Ruuska (Nokia), Tran (NICT) et al

7 Logical Entities Coexistence manager (CM)
Functions related to the functional role of the entity Discovery of other CMs To solve coexistence problems between the TVBD networks they serve Coexistence decision making This includes generating and providing corresponding coexistence requests/commands and control information to CE(s) Support exchange of information required for coexistence among CMs. This may include hierarchical and/or peer-to peer decision making capabilities in CM deployments Assist network operators in management related to TVWS coexistence. Ruuska (Nokia), Tran (NICT) et al

8 Logical Entities Coexistence Discovery and Information Server (CDIS)
Functions related to the functional role of the entity Support discovery of CMs Facilitates opening interfaces between CMs Collect, aggregate, and provide information facilitating coexistence This includes data storage, data processing, etc Ruuska (Nokia), Tran (NICT) et al

9 Logical Interfaces 802.19.1 defines three groups of logical 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 Different interfaces in each group are distinguished by their usage, types of information exchanged, and underlying protocols Ruuska (Nokia), Tran (NICT) et al

10 Logical Interface A Interface between CE and TVBD network or device
From TVBD network or device to CE Old: Information required for coexistence New: Information requested for coexistence New: Configuration/information requests for coexistence From CE to TVBD network or device Reconfiguration requests/commands and control information (corresponding to coexistence requests/commands and control information received from CM) Requests/commands related to control of measurements performed by TVBD network or device Ruuska (Nokia), Tran (NICT) et al

11 Logical Interface B1 Interface between CE and CM From CE to CM
Information required for coexistence (information obtained from TVBD network or device) From CM to CE Coexistence requests/commands and control information Ruuska (Nokia), Tran (NICT) et al

12 Logical Interface B2 Interface between CM and CDIS From CM to CDIS
Information required for discovery (obtained by this CM) Information required for coexistence (obtained by this CM) From CDIS to CM Information required for discovery (obtained by other CMs) Information required for coexistence (obtained by other CMs) Ruuska (Nokia), Tran (NICT) et al

13 Logical Interface B3 Interface between CM and CM From CM to CM
Information and messages required for discovery and coexistence Ruuska (Nokia), Tran (NICT) et al

14 Logical Interface C Interface between CM/CDIS and TVWS DB
From TVWS DB to CM/CDIS Information required for coexistence (information on available TV channels) Ruuska (Nokia), Tran (NICT) et al

15 Logical Interface D Interface between CM and OME From OME to CM:
Network operator related information e.g. spectrum policy/limitations concerning operator networks. Ruuska (Nokia), Tran (NICT) et al

16 Illustration of System Architecture
To illustrate the proposed System Architecture, three 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 Different and independently operated TVBD networks or devices in large-scale metropolitan area Distributed coexistence approach Deployment examples may be added as an appendix in SDD Ruuska (Nokia), Tran (NICT) et al

17 Deployment scenario 1 CDB OME TVWS DB CM TVBD CE TVBD CE TVBD network
Ruuska (Nokia), Tran (NICT) et al

18 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 Ruuska (Nokia), Tran (NICT) et al

19 Deployment scenario 2 TVWS DB CDB TVBD CE CM TVBD CE CM TVBD network
Ruuska (Nokia), Tran (NICT) et al

20 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 may not be connected to TVWS BD (e.g. in sensing only device) Ruuska (Nokia), Tran (NICT) et al

21 Deployment scenario 3 TVWS DB CM TVBD network cluster CDB TVBD CE CM
Ruuska (Nokia), Tran (NICT) et al

22 Deployment scenario 3 Different and independently operated TVBD networks or devices in large-scale metropolitan area: Distributed coexistence approach These networks are grouped into clusters where each cluster contains two or more networks Two coexistence problems exist in this scenario Coexistence problem between individual networks within each cluster due to the interference caused by adjacent networks (Intra-cluster) Coexistence problem between clusters due to the aggregated interference of each cluster (inter-cluster) The embedded CMs for decision making provide coexistence decision towards solving the “intra-cluster” coexistence problem The central CM provides coexistence decision to solve the “inter-cluster” coexistence problem Based on the previous decisions central CM provides coexistence guidelines, policies, or commands to embedded CMs Ruuska (Nokia), Tran (NICT) et al

23 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 Three illustrative examples were given Ruuska (Nokia), Tran (NICT) et al


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

Similar presentations


Ads by Google