SDN Functional Decomposition

Slides:



Advertisements
Similar presentations
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
Advertisements

Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
Logical Interface Overview Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital Notice:
Privecsg ‹#› IEEE 802 Privacy concerns about 802c PAR Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZunigaInterDigital.
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
P802.1CF Information Model Structure
Comparison Between and af
Progressing OmniRAN Abstract
802.1CF perspective on planned Industry Connections activity
Network instantiation
P802.1CF Information Model Structure
Relation between information modeling and network operation
P802.1CF NRM Mapping to real networks
P802.1CF User Service Information Model
Information Model Structure
omniRAN Virtual Access Network Instantiation
YANG Data Model for FDM Abstract
P802.1CF architectural considerations for EM and NM
Model for Accounting and Monitoring
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
An SDN-based approach for OmniRAN
Information Model for AN Setup
Information Model Structure
P802.1CF D1.0 Figure Proposals Abstract
Network instantiation
Brief Introduction to OmniRAN P802.1CF
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
Key concepts of authorization, QoS, and policy control
IEEE 802 omniRAN R9c Reference Point
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
Privacy Recommendation PAR Proposal
Information Model for AN Setup
An SDN-based approach for OmniRAN Reference Point mapping
January 2013 Summary Report for OmniRAN EC SG
[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
IEEE 802 RAN Recommended Practice ToC Proposal
Presentation transcript:

SDN Functional Decomposition omniran-15-0019-00-CF00 Date: 2015-01-15 Authors: Name Affiliation Phone Email Antonio de la Oliva University Carlos III of Madrid aoliva@it.uc3m.es Juan Carlos Zuniga InterDigital j.c.zuniga@ieee.org Luis Miguel Contreras Telefonica   luismiguel.contrerasmurillo@telefonica.com Notice: This document does not represent the agreed view of the OmniRAN EC SG. It 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 the contributor, 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 presentation accompanies the text to be included in the SDN chapter, presented in DCN XX.

Use cases Setup of interfaces and nodes Detection of node attachment SDN control configuration Short time scale configuration Long time scale configuration Detection of node attachment How do we know a new terminal (non controlled) is attached to a network? Path Establishment Path Tear Down Path Maintenance Path relocation Configuration of connection between the Core Network and the Access Network (TBD) Affecting the behavior of Coordination and Information System (TBD) Event handling (TBD) Statistic gathering (TBD)

Functional Requirements Support of a control connection between the different data path elements and the controller Support for data path elements with heterogeneous technology interfaces Support of communication mechanisms between the terminal and the controller Support of per packet matching, forwarding rules and actions in the data path element Support of state recording in the data path elements Support of security associations between the controller and the data path elements (including terminal) Support of security associations between controllers belonging to the AN and CN, which communicate Support of security associations between AN controllers and CIS servers

SDN specific attributes Abstract parameters Supported Rates TxPower, TxPower levels supported Operational Frequency Statistics: Tx error, Rx error, Number of stations Terminal Configuration Terminal Controller: LIST of control capabilities LIST of interfaces and their capabilities LIST of protocols to manage interfaces E.g., interface X supports CAPWAP+OF Interface LIST of parameters to be configured Technology specific: e.g., BSSID to connect to, RTS Threshold, Short retry, long retry, fragmentation threshold, Tx/Rx MSDU lifetime, enable Block Ack, etc. Security parameters (technology dependent)

SDN specific attributes Access Network Configuration Configuration of interfaces Abstract parameters LIST of parameters to be configured Technology specific: e.g., BSSID, RTS Threshold, Short retry, long retry, fragmentation threshold, Tx/Rx MSDU lifetime, enable Block Ack, etc. Technology specific security parameters: WPA/WPA2/WEP, parameters for key management, etc. Queue configuration: Capacity, max number packets, rate limitation Configuration of nodes Parameters to configure the connection to controller: Protocol+port Credentials Output physical port to use to connect to controller ID Configuration of data path ports VLAN configuration Number of tables

SDN specific attributes Data path Establishment Matching rule and actions Matching rule definition and associated actions Triggering technology specific features Type for feature E.g., send 802.11v frame, configure 802.11aa groupcast mode Content of feature E.g., BSS to attach to, groupcast mode, concealment address, stations to be added Interacting with CIS Parameters to enable the communication Protocol to be used, credentials Adding/removing/modifying information at the CIS CIS specific E.g., IE elements to add to ANQP Communication between CN and AN TBD Event handling Statistic gathering

SDN basic functions There is a description of the functions for most of the functions composing the use cases Not completed yet

Detailed procedures Need advise here, shall I assume any SDN protocol? How do we present the detailed operation without going into the details of protocols out of scope?