huawei technologies co., ltd. · huawei technologies co., ltd. huawei technologies co., ... lte...

www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD., Proprietary

*


Multiple 5G slices concurrently operated on the same infrastructure – with different distribution of control and user plane

2. Dedicated Functions at Cloud Edge Requires security, latency and reliability. (distributed control and user plane)

1. Centralized + Distributed Fully fledged functions distributed across network.

Ref: NGMN 5G White Paper

3. Basic centralized CP, distributed UP Basic control plane and user plane capabilities, no mobility. (central control and distributed user plane)


Personalized applications in cloudlet require low latency (<10 ms), high reliability, mobility support:

- Cognitive assistance (e.g., wearable cognitive devices for healthcare, Google glass, Olympus mobile eye trek) Ref: The case for VM-based Cloudlets in Mobile Computing, IEEE Pervasive Computing.

- V2V (Vehicle-to-vehicle) and V2I (Vehicle-to-infrastructure)

USER DRIVEN


Flatter (tier 2 and 3) Internet Peering Lower Transit cost (#1 for Tier 2 ISP) End user experience, latency (#1 for content providers) Control over routing, redundancy (#1 for Yahoo, NetFlix)

Consolidated fixed-mobile Data Centers Orange NG-POP plans to have common data centers for Fixed and mobile networks. Session continuity between fixed/mobile sessions.

Operator requirements for DC consolidation, and flatter peering by ISPs.

NETWORK DRIVEN


[Ref: 4G Americas Recommendations on 5G Requirements and Solutions]

Flexible mobility means that there may be a range of options based on device type, application, application context or statically configured. Flexible mobility consists of managing mobility and tracking/reachability to save power. Examples with Idle mode mobility on a per-device basis, and active mode mobility on a per-application basis is shown below:


Signaling, data traffic

Signaling and data traffic is growing exponentially. Variety of applications including those with low delay bound, high bandwidth in future. In the future, OTT players will form symbiotic relationship with carriers via dynamic SLA offerings

Future core Network should design for massive signaling, low latency and data demand.

0

2

4

6

8

10

12

14

2012 2013 2014 2015 2016

Traffic (Exabytes)

Signaling (100 Trillion msg)

References: Cisco VNC – Data traffic Growth Oracle – LTE Signaling Traffic Growth

Revenue growth will come from exposing network analytics to OTT players

Signaling will growth faster

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&uact=8&docid=I8GH0CuAdzL5oM&tbnid=-N_UZJUDbFfU7M:&ved=0CAUQjRw&url=http://www.covaligroup.com/blog/bid/93742/BIG-DATA-DATA-ANALYTICS-HELPING-COMPANIES-HELP-THEMSELVES&ei=6YjiU-OyGdXZoASY6IGYCw&bvm=bv.72676100,d.cGU&psig=AFQjCNEhZnN8cUsJXLEl4YX2Hh7_bvjfww&ust=1407441473153897

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&uact=8&docid=fSTg_Ioqrl64rM&tbnid=J6RA5n9b7cn00M:&ved=0CAUQjRw&url=http://www.creativeit.ch/en/services/web-applications/&ei=rYDiU5WzFIn2oASnsYKwAg&bvm=bv.72676100,d.cGU&psig=AFQjCNERsTDzu7hr_fjDDQ7EfXNfMO4fTA&ust=1407439058969788


IT Cloud Carrier Cloud


DB AAA

PCRF

IP Network

Mobile Core Data Svc

Diameter Network

Data Center Data center

Regional Network

Charging Analytics

DB

HSS

Mobile Core - CP

Mobile Core - UP

MM/SM

Auth API

SDN-C

Mobile Core Data Service DB


Mobile Core - CP

Mobile Core - UP

MM/SM

Auth ---

SDN-C

Dense Radio Network: Macro/small cells

Flexible Mobile Core Distribution: clustered, elastic sites with NFV/SDN 1. centralized + distributed (UP/CP) 2. dedicated functions at cloud edge (UP/CP) 3. Centralized CP, distributed UP.

Mobile core Data Service (MDS): Data tier that is loosely coupled to mobile core functions and to network services/apps like billing, analytics.

SDN based Transport Plane: white box traffic forwarding, stateful function are handled with in-switch autonomous functions and flexible service chaining

Next Gen Session and Mobility Management: support for varying levels of mobility and state transfers, transactions, QoS, low latency, high reliability. SDN Network

SORC SORC SORC

SWITCH SWITCH

APP

APP


DB AAA

PCRF

IP Network

Mobile Core Data Service

Diameter Network

Charging Analytics

DB

HSS

Mobile Core - CP

Mobile Core - UP

MM/SM

Auth API

SDN-C



Mobile Core - CP

Mobile Core - UP

MM/SM

Auth ---

SDN-C

SDN Network

SORC SORC SORC

REGION

METROPLEX

LOCALITY

SWITCH

SWITCH

Multiple 5G slices operating concurrently A) Central CP, Central UP

- NGMN Slice 1: smartphone B) Edge CP, Edge UP

- NGMN Slice 1: smartphone, Slice 2: V2V C) Central CP, Edge UP

- NGMN Slice 3: IoT

APP

APP


DB AAA

PCRF

IP Network


Diameter Network

Charging Analytics

DB

HSS

Mobile Core - CP

Mobile Core - UP

MM/SM

Auth API

SDN-C



Mobile Core - CP

Mobile Core - UP

MM/SM

Auth ---

SDN-C

SORC

REGION

METROPLEX

LOCALITY SWITCH

SWITCH

APP

APP

Radio + Mobile Core in a DC Support for a combined mobile

/radio site while also supporting mobile core slice that is centralized.

DC Network


Mobile Core - CP

Mobile Core - UP

MM/SM

Auth API

SDN-C

SORC

SWITCH

DC Network


PGW

SGW SGW

MME

Backhaul network

eNB eNB eNB eNB

DB AAA

PCRF

IP Network


Charging Analytics

DB

HSS

Mobile Core - CP

Mobile Core - UP

MM/SM

Auth API

SDN-C



Mobile Core - CP

Mobile Core - UP

MM/SM

Auth ---

SDN-C

SDN Network

SORC SORC SORC

SWITCH

SWITCH

APP


DB AAA

PCRF

IP Network

Mobile Core Data Svc

Diameter Network

Data Center Data center

Regional Network

Charging Analytics

DB

HSS

Mobile Core - CP

Mobile Core - UP

Auth

SDN-C



Mobile Core - CP

Mobile Core - UP

MM/SM

Auth ---

SDN-C

Dense Radio Network: Macro/small cells

SDN Network

SORC SORC SORC

SWITCH SWITCH

Data synchronization in Mobile Core:

– Subscriber data: (read heavy) relatively infrequent updates. Use mobile core signaling to resolve stale/out-of-sync data

– MM/SM context data: (write heavy) frequent updates and routing depends on it. May require locking for maintaining consistency.

– Accounting /charging data: (write heavy) high volume of data. Out-of-sync data can resolved by application (without locking).

Why do we need a distributed data layer ?

– Distributed data service layer that can be evolved, scaled and deployed independently of control.

– Decoupled operation: need to operate in the presence of intermittent wide area network/server failures.

– Latency of accessing remote database is avoided.

– Capability to expose network services

MM/SM MM/SM

Subscriber Data Acct/Charging Data MM/SM Data


MME

GW PCRF

SDN-C

MME

PCRF SDN-C

GW

GW

GW mgmt

DNS SDN-C

DB-H

IoT

SWITCH(GW)

DB-H SDN-C

MM/SM

Auth SDN-C

MDS

MM/SM mgmt

MDS

DB-H

DNS coord

MME

GW PCRF

SDN-C

MME

PCRF SDN-C

GW

GW

GW mgmt

DNS

IP Network SDN

Backhaul

DB-H SDN-C

MM/SM

Auth SDN-C

MDS

MM/SM mgmt

MDS

DB-H

DNS coord

IP Network Backhaul/

S1 SWITCH(GW) SWITCH(GW)

Realize “gateway” functionality with distributed resources: - Multiple controllers in peered and/or hierarchical mode - Forwarding elements that host stateful functions - Service chaining and in-switch autonomous functions - Core forwarding plane fns buffering, paging, mobility management, metering, charging. - Dynamic local measurement services, state monitoring and data aggregation Support for computing services at the Edge (e.g., MEC): - Containerization, pooling of edge cloud resources - Dynamic provisioning across core and edge cloud resources

- Few networking abstractions - limited to “ports”. - limited support for geographic distribution of net

functions - sub-optimal routing path for network flows - low throughput and high latency.

IT to CARRIER

Carrier Cloudlets

SDN-C

DB-H

IoT

SWITCH(GW)

Carrier Cloud DCs IT Cloud DCs

Fast path support for low latency and/or high throughput applications.


ARNO (June ’15) Brahmaputra (Feb. ’16) Release C Release D

- L2/L3 VPN with multi-tenancy

- Resource scheduling, reservation - SLA provisioning - Fault management - Service assurance - Multi-site support - Simple SFC/VNFFG - ONOS integration with

ONOSFW SBI/NBI - Basic policy support

- Dynamic SFC/VNFFG - Edge computing - Edge storage - Policy based slicing - Containerization - Advanced resource

scheduling, reservation - Fault management, high

availability, service assurance

- IPv6 for flattening networks

OpenStack + ODL Fixed Network Config. Build & CI for OPNFV release

OpenStack + ODL + ONOS + OC Cluster Level Config. Lab Ready

Dynamic Policy VM + Container Support Fixed Network Ready

- Control and data plane function hosting on forwarding elements

- MANO for Edge Cloud, Cloud, Inter and Intra Cloud/Edge Cloud

- Distributed Data Services - Mobile network

abstractions - Dynamic policy mapping

based on context & state - SON support - Control delegation

Low Latency + High Throughput Hosting Mobile Network Ready IoT/MTC Ready

Light Blue text = work not yet started in OPNFV

huawei technologies co., ltd. · huawei technologies co., ltd. huawei technologies co., ... lte...

Documents