OmniRAN SoA and Gap Analysis Date: [2013-05-14] Authors: NameAffiliationPhone Antonio de la Juan Carlos

Slides:



Advertisements
Similar presentations
(omniran TG) Short introduction into OmniRAN P802.1CF Date: Authors: NameAffiliationPhone Max RiegelNokia.
Advertisements

Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran IEEE 802 Enhanced Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Considerations for MIS framework to cooperate with SDN Date Submitted: July 11th,
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Use cases of MIS framework to cooperate with SDN wireless access networks Date.
OmniRAN-15-00xx WLAN as a Component (WaaC) Date: xx Authors: NameAffiliationPhone Yonggang FangZTETX Bo SunZTE He HuangZTE Notice:
OmniRAN – 3GPP SaMOG Document Number: IEEE Shet
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Discussion on IEEE metrics guidelines Document Number: IEEE R0 Date Submitted: Source: Antonio BovoVoice:
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 CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 9 Virtual Trunking Protocol.
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.
WiFi Privacy network experiment at IEEE 802 Berlin Plenary and IETF92 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IETF NETEXT Overview and Relationship with c Date Submitted: March 16, 2010.
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
Omniran CF00 1 Some Detailed Information for Network Reference Model Date: [ ] Authors: NameAffiliationPhone Su YiFujitsu R&D.
IEEE MEDIA INDEPENDENT HANDOVER DCN: MISU-OpenFlow_PoA Title: OpenFlow PoA proposal for SDN use case Date Submitted: March 20, 2014.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran IEEE 802 OmniRAN EC SG Results and Outlook Date: Authors: NameAffiliationPhone Max RiegelNSN
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 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN CF00 1 IEEE 802 omniRAN Network Reference Model Amendment Date: Authors: NameAffiliationPhone Yonggang
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Mobility Management with Multi-Carrier Support in IEEE m Document Number: S802.16m-08/144 Date Submitted: Source: Kelvin
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Use cases of MIS framework to cooperate with SDN wireless access networks Date.
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
OmniRAN omniRAN Network Function Virtualization Date: Authors: NameAffiliationPhone Yonggang FangZTETX Zhendong.
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
Network instantiation
IEEE 802 OmniRAN Study Group: SDN Use Case
omniRAN Network Function Virtualization
Network reference model for access network virtualization
WLAN as a Component (WaaC)
Network Virtualization
An SDN-based approach for OmniRAN
Transmission Modes for Multi-Radio Access in Hierarchical Networks
SDN Functional Decomposition
omniRAN Network Function Virtualization
IEEE 802 Scope of OmniRAN Abstract
An SDN-based approach for OmniRAN Reference Point mapping
[place document title here]
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
Presentation transcript:

OmniRAN SoA and Gap Analysis Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos 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. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Abstract This presentation explain the key concepts on the protocols related to current OmniRAN activities and performs a GAP analysis of missing functionality.

OmniRAN SoA and Gap Analysis OmniRAN contribution

Protocols studied and perspective This presentation focuses on configuration protocols related to OmniRAN from an SDN point of view We have split the analysis in two main areas: – Interface configuration protocols: Used to configure Radio + MAC parameters in the actual Point of Attachment CAPWAP/SNMP – Forwarding path configuration protocols: Used to configure data and control paths between Access Network and Internet GWs (Generic Backhauling/Core) MVRP/OpenFlow

CAPWAP Control And Provisioning of Wireless Access Points (RFC5415, binding for RFC5416) CAPWAP is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points This protocol differentiates between data traffic and control traffic Only the control messages are transmitted in a secured tunnel

SNMP Simple Network Management Protocol (RFC3410) SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (and sometimes set) by managing applications

MVRP Multiple VLAN Registration Protocol (IEEE 802.1ak) – Replaces GARP VLAN Registration Protocol (GVRP) defined in IEEE 802.1Q-2005 Within a layer 2 network, MVRP provides a method to dynamically share VLAN information and configure the needed VLANs – Example: in order to add a switch port to a VLAN, only the end port, or the VLAN-supporting network device connected to the switch port, needs to be reconfigured, and all necessary VLAN trunks are dynamically created on the other MVRP-enabled switches

OpenFlow Described by the OpenFlow specification ( w-spec-v1.1.0.pdf) Southbound interface that enables the configuration of switches and the creation of isolated virtual networks sharing the same physical resources It works by creating entries in flow tables, each entry is able to modify the switching of specific packets and the packet itself

Comparison of CAPWAP and SNMP CAPWAPSNMP Centralized/distributedCentralized Access Controller manages the networkCentralized Network Management System manages the network Control/Data separation It can work in several modes, local and split MAC. In local MAC the WTP can send packets directly using bridging or encapsulate packets to AC. In split MAC several MAC operations are performed by the AC, data packets are encapsulated to the AC. CAPWAP only provides radio configuration to WTPs, it does not handle the forwarding configuration between AC and WTP (supports L2 and L3). Only considers control path, it does not handle at all or controls the data path Handling of user data / forwarding path It handles user data. There are deployment options where the WTP does not send all data to AC but typically it is used in a mode of operation that encapsulates all traffic to AC No Configuration parametersIt can configure most of MIB parameters of the defined bindings It can configure all parameters on the latest MIB for each technology Configuration target (supported RAT) Different technologies supported by specific technology bindings. Currently only WLAN truly supported Any technology with MIB QoS Supports configuring and defining QoS configuration for packets and how to handle that in WTP. Also supports certain configuration in the MN (802.11e) Supports QoS related actions in MIB User subscription managementAuthentication can be performed in AC and shared across all WTPsNo Support of fast handover configuration (same as before - related to R4) Authentication can be made available at WTPs before handover, reducing HO timeNo Support of latest features Missing latest features, e.g n. Protocol does not allow flexibility for adding new parameters dynamically Yes Transport protocolUDP, UDP-lite, DTLSUDP, TCP MN configurationPartial Secure control planeYesOnly in SNMPv3 (current version) Firmware update capableYesNo Link configuration (terminal and backhaul) No Spectrum agility configurationNo WTP: Wireless Transmission Point AC: Access Controller MIB: Management Information Base

Comparison MVRP and OpenFlow MVRPOpenFlow Control Path Mechanism for distributing the VLAN tags associated to a L2 network. Bridges configured with the tags are able to distribute and form a consistent VLAN network across multiple bridges. Centralized control path enables the configuration of the different elements in the network. The controller can be associated with any switch supporting OpenFlow and the configuration protocol requires L3 transport Data PathData path is based on L2 VLAN switching Data path can be modified and configured, based on template matching of packets and switching Split control/dataNoYes Configuration target L2 switches and IEEE 802 nodes supporting IEEE 802.1Q and IEEE 802.1ak Switches supporting OpenFlow specification Heterogeneous Technologies 802 nodes supporting 802.1Q and 802.1ak Only OpenFlow switches at the moment, some APs also supporting the specification (e.g. OpenWRT) Centralized/Distributed Distributed. Limited centralized operation is possible when some proprietary extensions are used Controller runs centralized, although it can be distributed Packet matching ruleL2 headers only (e.g. VLAN tag/MAC) Mostly all header fields up to the IPv4/6 header and transport protocol, no tunneling analysis supported (e.g., GTP) Dynamic configuration Dynamic creation/configuration of VLANs (e.g. upon user’s arrival) seems not supported Dynamic modification of the rules is possible Modification of packetsVLAN tags only Yes. MAC address, VLAN ID, priority, MPLS parameters, IP addresses, ToS, DS, TTL, transport ports, etc Configuration of RadioNo Transport protocolUses transport over L2 (does not use IP)TCP/TLS Data StatisticsNo Yes. Number of packets, bytes, etc matching, dropping, errors, queue Dynamic actionsNo Dynamic actions over the packet and over the flow tables. Drop, modify other actions, etc Radio StatisticsNo

Scenario

Configuration of links from backhaul/core to terminal Dynamic creation of data paths with dynamic reconfiguration and mapping to the terminal

GAP analysis Currently the following missing functionalities have been identified: – Configuration of heterogeneous IEEE 802 Links, including radio parameters (e.g. R1) – Creation of data paths across 802 links (i.e. R3 provisioning) Configuration of end to end QoS characteristics per flow – Mapping of user’s traffic to data paths across heterogeneous backhaul/core technologies (e.g. R2) – Mobility support (e.g. R4 context transfer) – User plane management of the multiple-interfaced MN Generic 802-based logical interface to present to IP