SimpleCore: an appeal for less complex core networks...2016/04/06 · Demo setup • Smartphone, 3...

Copyright © 2016 DOCOMO Communications Laboratories Europe GmbH

SimpleCore: an appeal for less complex core networks

5G PPP – 1st 5G Architecture WorkshopApril 6th, 2016

Handle with care© 2016 DOCOMO Communications Laboratories Europe GmbH All rights reserved•Unauthorized photocopy/replication and removal from company premises are prohibited•Appropriate disposal by security BOX/shredder

Copyright © 2016 DOCOMO Communications Laboratories Europe GmbH 2

Motivation: Need for a paradigm shift due to business and technical situation

Observation: for a large fraction of traffic• Best effort is good enough • Mobility support is not needed (no IP address preservation needed)

: 2019 traffic prediction

20% others

80% video

: traffic consumption

70-80% indoor

20-30% outside

Video works well with “best effort”and changing IPs (buffering, DASH, …)

Indoor traffic: low/no mobility (nomadic behavior)


EmailHTTP

Problem statement

More than best effort*

Video streaming Twitter

*IP level QoS, traffic differentiation, mobility support

eNB

LTE

S-GW

P-GW

PCRF

MME

HSS

OCSOFCS

Ext. IP Net

X2

S1 -US1 -MME

S5/S8

S11

S6a

S10

Gxc

Rx

Gx

SGi

Gz

Gy

A lot of applications work well with a best effort, no mobility support model

However, the mobile network applies a “one size fits all” solution. Every packet stream gets mechanisms for • Traffic differentiation (bearers)• Mobility support (stable IP address)• … even if not needed!

Problem statement How to support “best effort, no mobility traffic” (like HTTP, DASH video, email) more efficiently than with current EPC:• Less overhead in data plane processing• Less signaling effort

Best effort


10.1.2.213 10.1.7.5410.1.1.39

SimpleCore concept

eNB

LTE

X2

SGi

SimpleCore• Topologically correct IP for UE IP packets can be routed

• eNB change IP address changes

eNB eNB… eNB eNB…10.1.1.x 10.1.2.x 10.1.7.x 10.1.9.x

10.1.1.39 10.1.2.213 10.1.7.54 10.1.9.119

“Peering router”

PDN

SGi

Service Provider (SP)

router

10.*.*.* -> DCM

PDN

10.1.*.* -> A

10.2.*.* -> B

AB

D E

10.1.1.* -> D

10.1.2.* -> D

10.1.7.* -> E

10.1.9.* -> E

10.1.2.174 10.1.7.37


Best effort slice

AAAeNB

User B

• Related use cases are– “Broadband access in dense areas/everywhere”, “Massive IoT” (NGMN 5G White Paper)– “Mobility on demand”, “SMARTER Service Continuity” (3GPP SMARTER)

• Related technologies are– Network Functions Virtualization (as standardized in ETSI NFV)– Network slicing (3GPP SMARTER TR22.891; 3GPP FS_NextGen TR 23.799)

• Such technologies, e.g. allow for providing – a basic service that is connectionless, best effort and without support for node mobility– extended capabilities if explicitly requested by an application

5G and Standardization

User A

Video, http

Carrier-grade slice

PGWSGW

MMEeNB

https, vpn, …

AAA


Mobility-needed/mobility-less application in parallel

*example only (for “more than best effort”)

UE applicationbehaviour time

Internet surfing

Voice call*

timeConnectedEPC +

SIPTO

SIPTO

EPC-ATTACH

timeBest effortSimpleCore

SimpleCore-ATTACH EPC-ATTACH* EPC-DETACH*

e.g. API call on UE

“Better than best effort”

“EPC bearer on demand”


GCM: google TM cloud messaging

• Client App seems to hold connection to GCM connection server

• Client identification via unique ID assigned in registration with GCM

• Messages are sent to unique ID

APNs: TM Push Notification service

• Client App seems to hold a connection to APNs server

• Client identification via device token

• Messages are pushed via Apple’s own servers to client

• Works via WiFi and cellular

Experimentation: IP push protocols

Unique ID of client App

IP address changes are no problem


Demo setup

• Smartphone, 3 WIFI APs

• Chat-bot regularly sends messages to smartphone via Google HangoutsTM

Experimentation: Google HangoutsTM

Cloud

Time:17:16:43

Time:17:17:18Time:

17:17:02

AP1 AP3AP2

IP address changes are no problem andmessages are received in a timely manner


• Demo setup: Smartphone, 3 WIFI APs

– Smartphone changes access point every 5 seconds

IP address changes are no problem and no stalling was observed

Experimentation: DASH video

Video Seg 4 - 6

Access Point 1

Access Point 3

Access Point 2

Wifi

Android smartphone

Cellular NW A

Cellular NW B

Cellular NW C

Internet

Cellular Internet

Video server

0

20000

40000

60000

80000

100000

120000

140000

0 25 50 75

Vid

eo

Po

siti

on

[m

s]Session time [s]

Buffer Status during video streaming

Playout PositionBuffer PositionAP Change 1und1AP Change EUL1AP Change EUL2


Today's mobile core networks are highly complex due to backwards compatibility and the requirement to always deliver the best possible service

4G core network provides mobility support and QoS to all traffic

Traffic intensive applications (>80% of traffic) like video / web surfing can handle node mobility at application layer and anyway traverse the best effort Internet

Such applications (70% of traffic) are mainly consumed indoors, by quasi-static users

Technologies like network slicing and virtualization allow to adapt to such properties

- Slice with extended capabilities like mobility support

- Default basic slice is connectionless, best-effort, no mobility network

"SimpleCore" provides a solution for such basic slice using a hierarchical IP address assignment, where a UE’s IP address will change when doing handover between eNBs

Experiments with push notifications and video streaming provided promising results

Conclusion

Copyright © 2016 DOCOMO Communications Laboratories Europe GmbH

DOCOMO Communications Laboratories Europe GmbHLandsberger Strasse 312 – 80687 Munich, GermanyPhone: +49 (89) 56824-0 | www.docomolab-euro.com

Dr. Wolfgang Kiess [email protected]. Gerald Kunzmann [email protected] Dr. Srisakul Thakolsri [email protected]

SimpleCore: an appeal for less complex core networks...2016/04/06 · Demo setup • Smartphone, 3...

Documents

Transcript of SimpleCore: an appeal for less complex core networks...2016/04/06 · Demo setup • Smartphone, 3...