5G Wireline - Technology Challenges / Standards and Relationship to Open Source May 25th 2016 Peter Ashwood-Smith peter.ashwoodsmith@huawei.com Disclaimer: This presentation represents the author’s personal opinions, no official position is implied by the contents of this presentation. It’s still a long way to 2020!

Some Major Drivers for the 5G wireline architecture End to end virtualization – obvious operational savings for “tidal” effects Cloud RAN – opex/capex savings, CoMP, CA, cell edge interference, migration, performance. Mobile Edge Computing – operators low delay advantage over the OTTs. Fixed Mobile Convergence – access side also looking for virtualization savings too… can they be combined? Slicing – differences between RAT’s/CORES etc rather than a one size fits all allows ultra low delay etc. RATS. SDN and Orchestration – hard to implement all of above with distributed protocols and too complex for manual operation. NFV – use of general purpose compute as much as possible (but not everywhere) 4G vEPC, 5G-PacketCore[slice], … MEC + some of RAT Better operations/mgmt, more Cloud-Style, auto problem detect/fix etc. We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end.

A few key wireline standardization issues Fronthaul – Fronthaul ties CRAN to Antennas, major downstream effects. Is it sliced, where, how.. Backhaul/IDC – latency, jitter, loss at packet layer, flexible data paths NFV – concept needs to be made broader. Cover some of DSP and all of MEC MEC – ETSI approach ridged. Any F any CPU + RAT (merge into NFV?) Orchestration – does not exist yet .. Understand AT&T to build in-house Danger of orchestration/mgmt duplication (virtual/physical) Softwarization – high level programming model, profiles, scripts, end to end OA&M – need “cloud like” approach. Continuous test/repair not just report. We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end.

Slicing from UE perspective Interesting options for slicing with respect to the UE’s / “Things” Android and IOS will need to be extended to support Overlap possible )))) OS A P P Thing )))) OS A P P Thing )))) OS Thing Thing )))) OS Thing A P P A P P A P P A P P We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end. One Thing = 1 Slice One Thing = N-Slices 1 OS = 1 Slice 1 App = 1 Slice One Thing = N-Slices 1 OS = N Slices 1 App = N Slices IOT etc. . N IP addresses. Baby VM, Container, Apps isolated. Add capacity, different QOS per APP. 1 IP address

5G concept of an end to end “Slice” Network Perspective + U = Antennas Fronthaul CRAN fabric CRAN CPU/S/W RAT Numerology Back Haul Core CPU/S/W S If U is the set of all resource sets { Antennas, Fronthaul , ..} then Slice Si is a set of resource subsets taken from resource sets { Antenna, Fronthaul } There are a nearly infinite number of possible slices | S* | U U We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end. + Si = Antennas Fronthaul CRAN fabric CRAN CPU/MEM RAT Numerology Back Haul Core CPU/MEM 1010101 S

Slices can overlap in some elements (some subsets are full) + U = Antennas Fronthaul CRAN fabric CRAN CPU/S/W RAT Numerology Back Haul Core CPU/S/W S = Si Non physical isolation in the shared /overlapping elements Isolation is in frequency/time/direction or statistical Isolation is physical in time(OTN), frequency(l), space(fiber/server) = Sj We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end. = Sk Physical Isolation

Controller/Orchestrator Hierarchy likely most control is of Open Source origin MASTER SLICE CONTROLLER C-RAN INSTANCE SLICE CONTROLLER METRO N/W CONTROLLER C-RAN INSTANCE SLICE CONTROLLER D-RAN CONTROLLER C-RAN INSTANCE SLICE CONTROLLER UE SLICE CTRL? FH SLICE CTRL IDC SLICE CTRL CRAN FABRIC CTRL CRAN SERVER CTRL CRAN SERVER CTRL CRAN FABRIC CTRL IDC SLICE CTRL FH SLICE CTRL Mm & uWave CTRL UE SLICE CTRL? DWDM )))) RAT / CN RAT/ CN RAT RAT/MEC CN / MEC CN/MEC Idle/off 400 GE DC CONTROLLER Fabric Control Server Control 400 GE CN Idle/off RAT / CN mmWave CN Idle/off RAT/ CN u CN / MEC ((( )))) We expect to see SDN and Transport SDN play important roles in the integration of the various networks under one orchestration umbrella. T-SDN can be used to control the microwave links between antenna sites, likewise T-SDN can be used to control the metro network where the front-haul and back-haul wire-line is executed. SDN again plays a role managing the network and servers that resides in the data center where the NFV functions and/or C-RAN functions execute. Various applications/services can reside on top of the 5G orchestration system which provide them with an unprecedented flexibility to operate on the entire 5G network end to end and if suitable hooks are provided into the C-RAN functions and the EPC functions the 5G applications can co-ordinate all the behavior of their slice of a 5G network end to end. RAT CN/MEC mmWave RAT/ CN mmWave RAT/MEC DC POD Idle/off )))) DC POD )))) ((( mm PON IP o <anything> mmWave )))) D-RAN Analog RAT

Complete Open Source 4G – end to end for FG-IMT-2020 POC experiments. Android based phone. Linux based eNodeB Linux based EPC Linux based HSS Docker/Containers/VM/OpenStack Open source eNodeB Gnu Radio Open source EPC Open source HSS Soon to include Open NFV, Open Daylight, ONOS (TSDN) And Likely Open-O = 100’s of millions of lines of code!!! Could 5G be > 90% code from open source origins?

ITU-T 5G wireline FG-IMT-2020 Phase II (2016) Renewed end of 2015 for all of 2016 New Terms of Reference as follows: Demonstrations or prototyping with other groups (e.g., with open source community); Network softwarization and ICN; Network architecture refinement; Fixed mobile convergence; Network slicing for front haul/back haul; New traffic models and associated QoS and OAM aspects applicable to IMT-2020 architecture. Four meetings in 2016 – Seoul and Berlin completed. Outputs A: Draft recommendations to accelerate process in SG13 in 2017. Outputs B: Proof of concept of softwarization, working with open source orchestrator (three teams currently planning this Japan, Ottawa and California (ICN)

Thank You