IEEE 802 omniRAN R9c Reference Point

Slides:



Advertisements
Similar presentations
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Advertisements

OmniRAN-15-00xx WLAN as a Component (WaaC) Date: xx Authors: NameAffiliationPhone Yonggang FangZTETX Bo SunZTE He HuangZTE Notice:
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Omniran CF00 1 P802.1CF NRM Discussions Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN IEEE 802 OmniRAN Recommended Practice ToC Proposal Date: Authors: NameAffiliationPhone Yonggang
OmniRAN CF00 1 IEEE 802 omniRAN Network Reference Model Amendment Date: Authors: NameAffiliationPhone Yonggang
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
OmniRAN omniRAN Network Function Virtualization Date: Authors: NameAffiliationPhone Yonggang FangZTETX Zhendong.
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Ambiguities Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
P802.1CF Information Model Structure
Progressing OmniRAN Abstract
Network instantiation
P802.1CF Information Model Structure
P802.1CF NRM Mapping to real networks
P802.1CF User Service Information Model
Information Model Structure
omniRAN Virtual Access Network Instantiation
P802.1CF architectural considerations for EM and NM
Model for Accounting and Monitoring
[Insert Document Title Here]
omniRAN Network Function Virtualization
P802.1CF Information Model Structure
P802.1CF NRM Refinements Abstract
P802.1CF NRM Discussions Abstract
Network reference model for access network virtualization
Chapter 7.1 Restructuring Proposal
WLAN as a Component (WaaC)
802.1CF-D1.0 WG ballot comment remedies
802.1CF-D1.0 WG ballot comment remedies
Date: < yyyy-mm-dd >
Investigation Report on
Information Model for AN Setup
Information Model Structure
Information Model Structure
P802.1CF D1.0 Figure Proposals Abstract
Network instantiation
Brief Introduction to OmniRAN P802.1CF
SDN Functional Decomposition
P802.1CF architectural considerations for EM and NM
Terminology clean-up User/Subscriber
Information Model Structure
Terminology clean-up User/Subscriber
P802.1CF Information Model Structure
P802.1CF operational models
omniRAN Network Function Virtualization
P802.1CF D1.0 Figure Proposals Abstract
P802.1CF NRM Refinements Abstract
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
Mapping of QoS Related Parameters
P802.1CF NRM Refinements Abstract
Information Model for AN Setup
Working Group Treasurer’s Report - Session #100
An SDN-based approach for OmniRAN Reference Point mapping
[place document title here]
802.1CF ToC Refinements Abstract
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
Metrology SG Closing Report – Session #81 - DRAFT
Working Group Treasurer’s Report - Session #106
Working Group Treasurer’s Report - Session #108
Working Group Treasurer’s Report - Session #110
IEEE 802 RAN Recommended Practice ToC Proposal
Presentation transcript:

IEEE 802 omniRAN R9c Reference Point Date: 2014-03-xx Authors: Name Affiliation Phone Email Yonggang Fang ZTE yfang@ztetx.com Bo Sun sun.bo1@zte.com.cn He Huang Huang.he@zte.com.cn Notice: This document represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on contributors, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy <http://standards.ieee.org/IPR/copyrightpolicy.html>. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. Abstract This contribution discusses and suggests the reference point R9c of IEEE 802 based RAN architecture for shared access in Recommended Practice document.

Background and Issues Reference Points (R9c) Represents the external interface between ANC and CIS which is used for the ANC to query the Authorized Shared Access information on particular location and receive the instruction from the CIS. CIS may locate at different place in NRM, depending on the implementation: Co-located with RAN, or CN. But the current omniRAN NRM contains only one option. In addition, CIS also needs to be authenticated before ANC acquires and uses the authorized shared access information.

Current omniRAN Reference Model Terminal Interface R1 Coordination and Information Service R2 R8c AN Ctrl TE Ctrl Subscription Core Network R3d R3s CNI Ctrl R3c Access Network NA Backhaul R6d R6c R7c R9c

Proposal of modified NRM R9c R9c could be the interface between CIS and AN Ctrl (ANC), or CIS and CNI Ctrl (CNC) R9c (CIS-ANC or CIS-CNC) contains same protocols CIS CIS is a database used to store the information of authorized shared access. It also provides the function of mutual authentication with ANC or CNC.

Proposal of modified NRM CNI Ctrl CNI Ctrl has an interface to Subscription Service (SS) to acquire subscriber’s information during the user authentication, authorization and datapath establishment. CNI Ctrl has an interface (R9c) to CIS to access the authorized shared access information on the particular location and radio channel. CNI Ctrl has an interface (R3c) to ANC to control the operation of CN for user’s datapath establishment, teardown, or relocation.

Proposal omniRAN Reference Model Terminal Interface R1 Coordination and Information Service R2 R8c AN Ctrl TE Ctrl Subscription Core Network R3d R3s CNI Ctrl R3c Access Network NA Backhaul R6d R6c R7c R9c

Backup IEEE 802.19.1 Co-existence architecture for shared access