5G Wireline - Technology Challenges / Standards and Relationship to Open Source May 25 th Peter Ashwood-Smith.

Size: px

Start display at page:

Download "5G Wireline - Technology Challenges / Standards and Relationship to Open Source May 25 th Peter Ashwood-Smith."

Clifton Golden
6 years ago
Views:

1 5G Wireline - Technology Challenges / Standards and Relationship to Open Source May 25 th 2016 eter shwood-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!

2 Some Major Drivers for the 5G wireline architecture End to end virtualization obvious operational savings for tidal effects Cloud RN opex/capex savings, CoM, C, 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 RT s/cores etc rather than a one size fits all allows ultra low delay etc. RTS. 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 vec, 5G-acketCore [slice], MEC + some of RT Better operations/mgmt, more Cloud-Style, auto problem detect/fix etc.

3 few key wireline standardization issues Fronthaul Fronthaul ties CRN to ntennas, major downstream effects. o 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 DS and all of MEC MEC ETSI approach ridged. ny F any CU + RT (merge into NFV?) Orchestration does not exist yet.. Understand T&T to build in-house o Danger of orchestration/mgmt duplication (virtual/physical) Softwarization high level programming model, profiles, scripts, end to end O&M need cloud like approach. Continuous test/repair not just report.

4 Slicing from UE perspective Interesting options for slicing with respect to the UE s / Things ndroid and IOS will need to be extended to support Overlap possible ) Thing Thing Thing Thing Thing OS OS OS OS OS IOT etc.. One Thing = 1 Slice One Thing = N-Slices 1 OS = 1 Slice 1 pp = 1 Slice One Thing = N-Slices 1 OS = N Slices 1 pp = N Slices 4 N I addresses. Baby VM, Container, pps isolated. dd capacity, different QOS per. 1 I address

5 5G concept of an end to end Slice Network erspective ntennas Fronthaul CRN fabric CRN CU/S/W RT Numerology Back Haul Core CU/S/W U = Σ U If U is the set of all resource sets { ntennas, Fronthaul,..} then Slice S i is a set of resource subsets taken from resource sets { ntenna, Fronthaul } There are a nearly infinite number of possible slices S * U ntennas Fronthaul CRN fabric CRN CU/MEM RT Numerology Back Haul Core CU/MEM S i = Σ

6 Slices can overlap in some elements (some subsets are full) ntennas Fronthaul CRN fabric CRN CU/S/W RT Numerology Back Haul Core CU/S/W U = Σ = S i Non physical isolation in the shared /overlapping elements Isolation is in frequency/time/direction or statistical Isolation is physical in time(otn), frequency(λ), space(fiber/server) hysical Isolation = S j = S k

7 Controller/Orchestrator Hierarchy likely most control is of Open Source origin METRO N/W CONTROLLER C-RN INSTNCE SLICE CONTROLLER MSTER SLICE CONTROLLER D-RN CONTROLLER C-RN INSTNCE SLICE CONTROLLER C-RN INSTNCE SLICE CONTROLLER UE SLICE? FH SLICE IDC SLICE CRN FBRIC CRN SERVER CRN SERVER CRN FBRIC IDC SLICE FH SLICE Mm & uwave UE SLICE? DC CONTROLLER DWDM DWDM RT / RT/ / MEC R T /MEC RT/ RT/MEC Idle/off Fabric Control Idle/off Idle/off Server Control DC OD DC OD RT / RT/ / MEC /MEC RT/ RT/MEC Idle/off R T mmwave mmwave mmwave ON I o <anything> mmwave nalog D-RN RT

Complete Open Source 4G end to end for FG-IMT-2020 OC

source EC Open source HSS Soon to include Open NFV, Open

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

9 ITU-T 5G wireline FG-IMT-2020 hase 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 I; Network architecture refinement; Fixed mobile convergence; Network slicing for front haul/back haul; New traffic models and associated QoS and OM aspects applicable to IMT-2020 architecture. Four meetings in 2016 Seoul and Beijing completed. Outputs : Draft recommendations to accelerate process in SG13 in Outputs B: roof of concept of softwarization, working with open source orchestrator (three teams currently planning this Japan, Ottawa and California (I))

10 Thank You

5G Network Control in ITU-T SG13: perspective and challenges

ITU-T Workshop on "Control plane of IMT-2020 and emerging networks. Current issues and the way forward" Geneva, Switzerland, 15 November 2017 5G Network Control in ITU-T SG13: perspective and challenges