1. OmniRAN-13-0067-0000 1 IEEE 802 OmniRAN Architecture Proposal Date: 2013-09-16 Authors: NameAffiliationPhoneEmail Yonggang FangZTETXyfang@ztetx.com Bo SunZTE sun.bo1@zte.com.cn ZhiQiang HanZTEhan.zhiqiang@zte.com.cn 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 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: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Abstract This contribution suggests to separate different planes in reference points to support various use case aspects in OmniRAN to foster interoperability and integration into unified common network infrastructures.

2. OmniRAN-13-0067-0000 2 IEEE 802 ARCHITECTURE IEEE 802 OmniRAN Architecture

3. OmniRAN-13-0067-0000 3 Background Use Cases for OmniRAN –Cellular offload in hotspot [1] [2] –SDN: support multiple service networks through sharing access network [3] –SON: self configuration and optimization for radio network [4] To extend this concept, Software Defined Radio (SDR) could provide more flexibility for radio networks.

4. OmniRAN-13-0067-0000 4 Background 3GPP Trusted WLAN Access Use Case AN R1 R3 Station R2 Core Internet

5. OmniRAN-13-0067-0000 5 Background SDN based Omni RAN Use Case Station Internet Core Network(s) Core Operator C Access Network Backhaul SDN Controller AN 3 Access Abstraction Multiple Cores sharing Access Network Access Abstraction Data and Control plane separation Central control R1 R3 R2 AAA Core Operator B Core Operator A Access Abstraction AN 1 AN 2 R4 R5 Access Abstractio n Backhaul Abstraction

6. OmniRAN-13-0067-0000 6 OmniRAN Architecture OmniRAN Involves –Different network entities in AN and Cores Access GW, SDN Controller, PDN WG, AAA, etc –Data link is not in Access Abstraction, but The data plane protocol GRE, GTP is mentioned in Gap #1 [5]. Backhaul (data link) is controlled by the SDN controller –Although protocols are grouped in the same reference point, they have different functionalities, and used for interfaces to different network entities. OmniRAN needs –differentiate functionalities in reference points for easy understanding

7. OmniRAN-13-0067-0000 7 OmniRAN Architecture Suggest to separate into three planes –Data Plane Functionalities: carrying, sequencing, tunneling, forwarding the user data traffic between the Core network, AN and Stations –Control Plane Functionalities: service management, user traffic connection setup, mobility management, accounting management, etc. –Management Plane Functionalities: carrying signals used for authenticating, controlling and managing the OmniRAN infrastructure (AP); Support configuration for SDR/SDN.

8. OmniRAN-13-0067-0000 8 OmniRAN Architecture and Reference Points A reference point contains interfaces for different planes Core R1 R3 R4 R5 STA R2 Core R4-D Data Plane Control Plane Data Plane Control Plane AN Transport R4-C R3-D Data Plane Control Plane Management Plane Data Plane Control Plane Management Plane AccessCore Transport R3-C R3-M Internet AN

9. OmniRAN-13-0067-0000 9 OmniRAN Reference Points Reference Points denote the interconnections between functional entities of an access network, i.e.: –R1 between station and access network: Access link, technology specific –R2 between station and core network: User & device authentication, subscription & device management –R3 between the access network and the core network: R3-M: support functions of access point authorization, configuration and SDN/SDR management. R3-C: support control functions of service management, user data connection setup and release, mobility management, accounting management, and location management R3-D: support user data forwarding, encryption, tunneling etc. –R4 between access networks: R4-D: support user data forwarding, bi-casting, encryption, etc R4-C: Inter-access network coordination and cooperation, fast intra-technology or inter-technology handover. –R5 between core networks to enable co-use of access networks: Inter-operator roaming control interface

10. OmniRAN-13-0067-0000 10 OmniRAN Protocol Stacks OmniRAN Data Plane Protocol Stack Medium Data Link Physical IPv4/6 Application Data Link Physical Data Link Physical L1 L2 IPv4/6 Application Medium Data Link Physical IP/UDP L1/L2 IP/UDP L1/L2 L2 L1 STAAPWAGPDN-GWAPP-SVR Core R2 R1R3 OmniRAN Architecture AN STA GW tunnel WLAN STA Core Service GTP-U ? ?

11. OmniRAN-13-0067-0000 11 OmniRAN Protocol Stacks OmniRAN Control Plane Protocol Stack Medium Data Link Physical C-Signal Data Link Physical Data Link Physical Medium Data Link Physical IP/UDP L1/L2 IP/UDP L1/L2 L2 L1 STAAPWACCTRLAPP-SVR Core R2 R1R3 OmniRAN Architecture AN STA GW tunnel ?? C-Signal WLAN STA Core Service GTP-C

12. OmniRAN-13-0067-0000 12 OmniRAN Protocol Stacks OmniRAN Management Plane Protocol Stack Medium Data Link Physical Data Link Physical Data Link Physical Medium Data Link Physical IP/UDP L1/L2 IP/UDP L1/L2 L2 L1 STAAPWAMMNGRAPP-SVR Core R2 R1R3 OmniRAN Architecture AN STA GW tunnel ?? M-Signal WLAN STA Core Service GTP-?

13. OmniRAN-13-0067-0000 13 Cellular Offload Case in OmniRAN Core 1 R1 S2a R4 R5 STA AP is a trusted access point WAG inside of WG is a trusted WLAN gateway which is connected to PDN Gateway through GTP tunnel based S2a interfaces defined by 3GPP. Connection to the Access Network through R3-D is is per station based. WAC inside of WG is a control entity that controls the R3-D setup over R3-C interface to AP. R2 is a reference point for the interface between STA and AAA through AP and WAG. R2 Core 2 R3-D R3-C WAG STa WAC WG AP

14. OmniRAN-13-0067-0000 14 Cellular Offload in OmniRAN (Example1) STAAPWAGPDN-GWAAA Proxy Scan & selection EAP Authentication (R2) Create Session Request (S2a) Authentication and Authorization (STa) Create Session Response (S2a) Update Session Info GTP Tunnel L2 to GTP Forwarding (R3-D ) GTP with L2 Mapping (R3-C) L2 Attach Trigger (R2) EAP and L2 Attach Completion (R2) CoreOmniRAN WAMWAC

15. OmniRAN-13-0067-0000 15 Cellular Offload in OmniRAN (Example2) STAAPWAGPDN-GWAAA Proxy Create Session Request (S2a) Create Session Response (S2a) Update Session Info GTP Tunnel L2 to GTP Forwarding (R3-D ) GTP with L2 Mapping (R3-C) CoreOmniRAN WAMWAC GTP/PMIP Tunneling Scan and selection Handover Request (R2) Handover Reply (R2) EAP Authentication (R2)Authentication and Authorization (STa)

16. OmniRAN-13-0067-0000 16 SDN/SDR Networks in OmniRAN Core 1 R1 R3 R4 R5 STA AP is a trusted access point. WAG is an trusted access gateway, WAM is SDN/SDR control functions to manage the data links of TWAG. The SDN/SDR management system (server) in the Core transmits configuration and control information to WAM to manage SDR based access points, and SDN based backhaul links over R3-M. R2 Core 2 R3-M WG R3-M ? Access Abstraction WAMWAG AP

17. OmniRAN-13-0067-0000 17 SDN/SDR Networks in OmniRAN STAAPPDN-GWSDN/SDR SERVER SDN/SDR Authentication (R3-M)SDN/SDR AP Authentication SDN/SDR AP Configuraiton CoreOmniRAN SDN/SDR Configuration (R3-M) SDN/SDR Authorization (R3-M)SDN/SDR AP Authorization WAGWAMWAC

18. OmniRAN-13-0067-0000 18 References 1.omniran-13-0032-05-0000-ieee-802-scope- of-omniran 2.omniran-13-0019-02-0000-omniran-wi-fi- hotspot-use-case 3.omniran-13-0029-01-0000-sdn-use-case- requirements 4.omniran-13-0042-00-0000-orchestration-of- son-features-for-wifi-offloading-using- network-empowerment-mechanisms 5.omniran-13-0048-04-0000-omniran-ecsg- results-and-outlook

19. OmniRAN-13-0067-0000 19 Thanks

20. OmniRAN-13-0067-0000 20 Backup 1.3GPP 23.402 Interworking Protocol Stack