An SDN-based approach for OmniRAN Reference Point mapping Date: [2013-04-11] Authors: Name Affiliation Phone Email Antonio de la Oliva UC3M +34657079687 aoliva@it.uc3m.es Juan Carlos Zúñiga InterDigital j.c.zuniga@ieee.org Charles Perkins Futurewei 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 extends SDN use case with the mapping to OMNIRAN Reference Points.

An SDN-based approach for OmniRAN Reference Point Mapping OmniRAN use case contribution

Heterogeneous Networking w/ OmniRAN

Reference Model for OMNIRAN over SDN sdf sdf Access Core Op A Terminal Core Op B Internet Access Access Core Op C Access Infrastructure Operators Traditional Operators

Reference Model (Access Infrastructure operator with data and control split) sdf Access Access Backhaul Access Access Access Access SDN Controller AAA Access Infrastructure Operators Access Infrastructure Operators Data path Control path

Reference Points R1: Access link, technology specific R2: User & terminal authentication, subscription & terminal management All these operations are provided through a separated control path. Required signaling is forwarded to the corresponding operator. R3: Authorization, service management, user data connection, mobility support, accounting, location This reference point is composed of control and data paths. Control needs to impact data path for e.g., mobility, and configure accordingly the access network (e.g., ACLs). Possible extension of SDN concepts for configuration of access network. R4: Inter-access network coordination and cooperation, fast inter-technology handover SDN based forwarding state between different RANs R5: Inter-operator roaming control interface Inter-operator roaming plus access infrastructure sharing.

R1 sdf Access Core Op A Backhaul Terminal R1 Core Op B Internet Access Access SDN Controller AAA Core Op C Traditional Operators Access Infrastructure Operators R1: Access link SDN based interaction between infrastructure and wireless link

R2 sdf R2 R2: Control path only Access Backhaul Terminal Access Access Core Op A Backhaul Terminal Core Op B Internet Access R2 Access SDN Controller AAA Core Op C Traditional Operators Access Infrastructure Operators R2: Control path only

R3 sdf Access Core Op A Backhaul Terminal Core Op B Internet Access R3 Access SDN Controller AAA Core Op C Traditional Operators Access Infrastructure Operators R3: Data (e.g., mobility) and Control (e.g., configuration) path

R4 sdf R4 R4: Data (e.g., fast handover) and Control (e.g., ICI) path Access Core Op A Backhaul R4 Terminal Core Op B Internet Access ICI: Inter-cell interference Access SDN Controller AAA Core Op C Traditional Operators Access Infrastructure Operators R4: Data (e.g., fast handover) and Control (e.g., ICI) path

R5 sdf R5 R5 R5: Data path: Roaming between operators Access Core Op A Backhaul R5 Terminal Core Op B Internet Access R5 Access SDN Controller AAA Core Op C Traditional Operators Access Infrastructure Operators R5: Data path: Roaming between operators Control path: Roaming between operator + infrastructure sharing

Reference Points R1: Access link, technology specific R2: User & terminal authentication, subscription & terminal management This reference point can be implemented as a control path up to an AAA server provided by the Access operator. Then the signaling is forwarded to the appropriate AAA server of the corresponding operator R3: Authorization, service management, user data connection, mobility support, accounting, location This reference point can be implemented based on a SDN controller. The SDN controller can configure the underlying network so the user is authorized (adding MAC to APs), managing mobility (reconfiguring forwarding path per user), accounting (counters per forwarding table).. R3 can also be extended for supporting configuration of the RAN R4: Inter-access network coordination and cooperation, fast inter-technology handover SDN based forwarding state between different RANs R5: Inter-operator roaming control interface Inter-operator roaming plus access infrastructure sharing.