5G Slicing Introduction

- The 1st 5G E2E Slicing for Commercialization

1
End to End 5G Network Slicing Booth Design

5G E2E Slicing Name Plate

5G

ZTE Demo with PON

2
Networking of E2E 5G Slicing
5G Core
HD Video AS Center DC

Back Haul Back Haul

Back Haul

Edge DC CDN/UPF/OLT Edge DC CDN/UPF Edge DC CDN/UPF

Front Haul Front Haul

eMBB Slice eMBB Slice uRLLC Slice
PON 5G 5G

RF DU RF DU

Fixed Line CPE 5G CPE 5G CPE

3
 Part 1 – Overview of Main Screen

E2E Orchestration Dash board with Tuning Panel

(Wireless/Bearer/Fixed/VAS Centralized KPI Control

4
Step 1.1 – Overview of Carrier DevOps Builder

•Health Status: whole status evaluated include 4-level alarm

•Application: mature template, easy for design; APP status includes VNF/PNF/NS
•Virtualized Resources: vCPU/Storage/Network Bandwidth
5 •Physical Resource: Server/Network/Storage
Step 1.2 - Overview of Carrier DevOps Builder

•Geographical Mode: easy for monitor the DC status deployed all around world
•Health Status/Application/Virtualized Resource/ Physical Resource
6
Step 2 – Template-Based, Drag & Drop Design

7
Step 3 – Auto Sandbox Test

8
Step 4 – One Key Deployment

9
 Part 2 – eMBB Slice with Big Video

10
eMBB Slice : HD Video Play

2K HD Camera

PON Access
eMBB Video
Slice Server
5G Access 6*2k HD Video Channel
+2 Live Video Channel

iPad Video Control

DevOps

Touch
Screen

11
eMBB Slice Control
Mode 1 :
2 Video in 5G / 2 Video in PON

Mode 2 :
Mode 0 : No Video
4 Video in 5G / 4 Video in PON

Mode 3 :
6 Video in 5G / 6 Video in PON

Auto Mode:
1->2->3->4->4->3->2->1
Simulate user behaviors
12
 eMBB Slice Introduction

Press the button changes to mode 0.

All 12 iPADs on the tree will display
ZTE static logo.

 Convergent access including fixed line and 5G

 6 iPADs above access the network by 5G CPE connect with edge DC by Front
Haul. 6 iPAD access the network by PON.
 They both connect to the center DC by Back Haul.
Now we can simulate the user behavior by iPAD, to demonstrate the network
13
slicing can be adjusted intelligently.
Step1 – Mode 1: 4 iPAD Play HD Video

There are 4 users watching HD videos. The customer will

see the data traffic from DevOps Builder Screen, the service
is running normally.
14
Step2 – Mode 2: 8 iPAD Play HD Video

As the subscribers quantity increases, the system will detect automatically, and assign more
resources by slice elasticity to meet the requirement of services. But the network bandwidth
is not enough, MANO will send command of bandwidth increasing to SDN-C. The video will
display
15
mosaic in a few seconds and then recover to the normal state
Step3 – Mode 3: 12 iPAD Play HD Video

In the peak hour, the subscribers will increase continuously. And we can see 4 iPAD are
playing the same channel. The system will detect the network bandwidth is not enough, and
generate system alarm. By intelligent analysis, the system will trigger the CDN to move from
center DC to the edge DC. We can see the bandwidth is reduced, and alarm is cleared. The
video
16 will display mosaic in a few seconds and then recover to the normal state.
Summary

Based on big data and AI analysis, ZTE DevOps Builder analyzes the
network service and KPI automatically, and adjusts/optimizes the whole
network end to end. It improves the operation efficiency, user
experience, reduces operation cost, and realizes intelligent E2E
operation.

17
 Part 3 – Low Latency Slice for Robots Dance

18
Low Latency Scenario: Robot Dancing
A ms delay 2A ms delay 7A ms delay

Relay Relay Relay

Network
Slice

Adjust Slice Latency

DevOps

8 robots simulate industry control scenarios, which are controlled serially:

First robot dances, and then this robot relays this command to the second robot through the network slice, etc.
So the time of last robot dancing is slower than the first robot by 7*Time delay of the network slice.

19
Step 1 – Adjust Latency to 200ms in Dashboard Control Panel

According to the different service scenarios, the operator will guarantee the SLA according to the different
requirements. For some scenarios which are not time –delay sensitive, we can reduce the time delay of the
network by the dashboard
RAN: not Optimized
Core: UPF is up to central data center.
Bearer: transmission distance is longer(2000Km)
20
Main Screen: Topology and Latency is Changed

E2E Latency is
increased to 20ms
UPF up to center DC
21
Result: Robots dance out of sync

22
Step 2 – Adjust Latency to 1ms in Dashboard Control Panel 　

The system will dispatch time latency requirement according to preset policy to RAN, Core, and Bearer network.
RAN: Deep Optimized for low latency
Core: UPF is down to edge Data center.
Bearer: optimize network topology, reduce the transmission distance and routing hops (0 Km)
23
Main Screen: Topology and Latency is Changed

UPF down to Edge DC

E2E Latency is
reduced to 1ms

24
Result: Robots dance simultaneously

Now the network time delay is 1ms (5G requirement) , we can see these robot dance together

25
Summary

The Operators can assign the network resources more flexible, to meet
different requirements of industry (connected car, IoT) services, and
innovate more value to realize digital transformation.

26