5G - Connectivity Platform of the 2020s - Georg Mayer Atsushi Minokuchi 3GPP CT Vice Chairman
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
5G – Connectivity Platform of the 2020s
© 3GPP 2012
Georg Mayer Atsushi Minokuchi
3GPP CT Chairman 3GPP CT Vice Chairman
Huawei NTT DOCOMO
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 1
5G – a Flexible Enabler
New Stakeholders … … require a flexible enabler platform
› Critical Communications (MCC) › Exposure of Core capabilities to 3rd parties
› Internet of Things (IoT) › On-demand resource allocation – local and end-2-end
› Tactile Internet, Ultra-HD Media › Core Architecture needs to be service centric
› Automotive (e.g. 5GAA, AECC), › Guarantee certain capabilities exclusively
© 3GPP 2012
› Railways (e.g. UIC), Maritime › Ultra low latency & high reliability
› Autonomous Systems (robots, drones, …)
› Smart Cities, Smart Factories (e.g. 5G-ACIA), …
› Water & Energy Providers,
› Broadcast Agencies,
› Satellites, …
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 2Software & Service Centric Transformation
One CoreNetwork fits all Open & Flexible Enabler
Telecom Operators Multiple Stakeholders 4G
Phones Things
© 3GPP 2012
Procedures Services
Static Topology On-demand Resources
Dedicated Hardware Orchestrated Resources
• Network Function Virtualization
• Single Network Slice
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 35G Landscape
Smart City Automotive
Healthcare
Factory Agriculture
Control
A P I
Internet
NB-IoT
© 3GPP 2012 Enterprise
LTE
H
A R D
W A R E
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 45G – Core Technologies
Virtualization (NFV) – de-couple logical function from hardware
Slicing – logical end-2-end networks tailed to customer needs
Edge Computing (MEC) – resources where they needed (URLLC)
Orchestration – programmable flexibility
© 3GPP 2012 (SON)
Exposure (API) – 3rd party access to 5G services
Service Based Architecture (SBA) – stateless, open, flexible
Harmonized Protocols & Access Agnostic – generic solutions
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 5Integration 3
Technology Integration
› 5G unifies state-of-the-art techs to the single worldwide connectivity platform
Integration into the Infrastructure of the 2020s
› The new techs in the 5G Core are already widely used in many industries
© 3GPP 2012
› 5G speaks the language of the vertical industries
Integration of Vertical Services
› Variety of verticals will communicate via same communication techs
› 5G enables communication between different services
› 5G offers deep-integration of cross-industry services
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 6C-plane features - SBA (1/6)
1. SBA (Service Based Architecture)
Objective: to adopt the state of the art technologies from Web and Cloud area, to improve the process of development and
operation, to engage relevant engineers into the industry.
Outcome: R15 established the base of SBA. R15 defined each NF as a combination of mono-functional NF services. NFs
provide and consume services to and from each other using a unified protocol. Stateless NF was specified for AMF.
Progress: R16 might treat NF service as the main granularity and make other NFs stateless.
© 3GPP
The 2012
scope of SBA Each Namf… is an NF service. AMF is an
NF.
Nudm
UDM AMF
Npcf Namf_Communication UDSF
PCF UDR Namf
Namf_EventExposure
Nnef Nudr
NEF Namf_MT
Namf_Location
Conceptually, the
same as UDC of EPC
Stateless
(separation of process and storage）
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 7C-plane features - SBA (2/6)
2. SBI (Service Based Interface)
Objective: to adopt widely-used Web protocols, to bridge a gap to the development.
Outcome: R15 adopted HTTP/2, JSON, taking a RESTful approach in general. R15 adopted OpenAPI 3.0.0 and decided to
create YAML format files as a part of specification.
Progress: R16 considers QUIC.
R15 3GPP specific aspects R16 (under consideration)
JSON • R15 added a custom HTTP header
© 3GPP 2012for JSON
message priority.
HTTP/2 • Based on R15, NF service consumer may
provide an identity that indicates itself in the
TLS message body, in case NF service producer HTTP/QUIC
subsequently consumes NF service(s) which
TCP the NF service consumer can provide.
IP IP
L2 L2
5GC uses HTTP instead of GTP-C and Diameter in EPC.
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 8C-plane features - SBA (3/6)
3. SF (Service Framework)
Objective: to allow quick creation and deletion of NF service instances, which is a fundamental nature of the Cloud
technology.
Outcome: R15 specified NRF. NRF copes with NF’s registration and discovery.
Progress: R16 is studying from a perspective that (i) NF service is targeted, (ii) the business logic of NF service itself does not
engage in registration and discovery, and (iii) open source software can be used as an implementation option instead of
NRF.
© 3GPP 2012 R16 (an example)
R15
e.g. open source e.g. open source
software software
NRF NRF
Instance creation
Registration Discovery of and management
target NF
Health-
check NF NF service Information for
NF NF
target discovery
Agent
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 9C-plane features - SBA (4/6)
4. Stickiness control
Objective: to ensure continuity of the state-full process, while load-balancing among a group of NF service instances.
Outcome: R15 conceptually introduced between RAN and AMF. (R15 allowed multiple TNL associations between RAN and
AMF, and separated TNL association and UE’s NGAP association.)
Progress: R16 is studying for combinations between NF services in SBA.
R15 R16 (an example)
© 3GPP 2012
(A UDSF covers UDSF UDSF UDSF
an AMF set)
Instance of Instance of
AMF Namf… Nsmf…
RAN Process can continue when
the context is found.
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 10C-plane features - SBA (5/6)
5. Unified data base
Objective: to specify a unified data base with a data model.
Outcome: R15 achieved this goal and introduced UDR. For UDSF, the data model was left to implementation due to
emphasis on performance.
Progress: -
R15
© 3GPP 2012
Nudm
UDM AMF
Npcf Namf_Communication UDSF
PCF UDR Namf
Namf_EventExposure
Nnef Nudr
NEF Namf_MT
Namf_Location
Specified to the Data model is left to
data model implementation
In EPC, data bases were not clearly separated from functions responsible for processing. UDC of EPC did not specify a data model.
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 11C-plane features - SBA (6/6)
6. Start to enrich northbound APIs
Objective: to enrich northbound APIs to enhance collaboration with 3rd parties and verticals.
Outcome: R15 specified NEF and added an API to allow AF to influence on traffic routing e.g. to MEC. The interface is the
same as internal SBIs except that HTTP/1.1 is mandatory.
Progress: R16 is making IoT related APIs at least comparable to those of EPC SCEF. Other works might add APIs.
R15
© 3GPP 2012
JSON
Supported procedures
HTTP/1.1 or HTTP/2
• Monitoring
TLS • Device Triggering
• Resource management of Background The same
Data Transfer
TCP as EPC
• CP Parameters Provisioning
• PFD Management
IP New to
• Traffic Influence
5GC
L2
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 12C-plane features - CP/UP
7. The same interface between CP and UP
Objective: -
Outcome: R15 slightly modified the interface between SGW-C/PGW-C and SGW-U/PGW-U and uses it for N4.
Progress: R16 might consider HTTP-based N4.
R15
© 3GPP 2012
PFCP
UDP
IP
L2
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 13U-plane features
8. Ethernet PDU Session type
Objective: to allow a flexible setup of the industrial Ethernet utilizing 5GC and NR, in order to cater to vertical’s needs and to
create a new business opportunity.
Outcome: R15 added Ethernet frame as a PDU session type. Packet filters can be created based on e.g. MAC address and
VID. QoS can be differentiated based on those.
Progress: R16 is studying this use case extensively.
Envisaged future use case
© 3GPP 2012
(Features are to be enhanced to realize this scenario.)
QoS
Ethernet packet filter
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 14Summary
5G integrates well-accepted technologies to a enabler platform
Many of these technologies are based on existing open standards and have
been successfully deployed by businesses of all sizes
This is a chance for 5G to become the universal harmonization and
integration platform for services of very different kinds of stakeholders
© 3GPP 2012
3GPP CT has taken great efforts to make 5G an open, future-proof and
flexilbe enabler platform by basing the system on state-of-the art
technologies such as virtualization, open APIs and edge computing.
3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 15Thank You! © 3GPP 2012 Georg Mayer Atsushi Minokuchi 3GPP CT Chairman 3GPP CT Vice Chairman Huawei Technologies NTT DOCOMO georg.mayer.huawei@gmx.com minokuchi@nttdocomo.com +43 699 1900 5758 +81 46 840 3245 http://www.3gpp.org 3GPP Summit in CEATEC2018 - Makuhari, Japan, October 17, 2018 © 3GPP 2018 16
You can also read
