5G STANDARDS LANDSCAPE

ISSUES IN REALIZATION OF PRACTICAL 5G DEPLOYMENT

TSDSI-5GIA-BIF WORKSHOP
05 FEB 2019

1
Satish Jamadagni
 5G BROADBAND SERVICE – WHAT'S HAPPENING

2
5G to home – eMBMS as cable replacement?

Home Access is the key to 5G success

5G Small cells/CPEs are key to 5G success

eMBMS into homes

5G to home – where is the 5G small cell definition?

3GPP 5G Architecture

NFV Architectural Framework

VNF VNF
Lower EMS for gNB EMS for 5GC
PHY, RF RLC, MAC,
Upper PHY SWA-4
SWA-4
PNF SWA-1 VNF SWA-4
SON, RRM,RRC,
gNB-RU gNB-DU xAP,SDAP, PDCP
NFV
Femto Cell SWA-1 MANO
VNF VNF
SWA-1 gNB-CU SWA-1 AMF/UPF/SMF
PNF
gNB-DU
Femto Cell MAC, NFVI
RLC,
PHY, RF
CLOUD
 Backhaul key to Small cell success

3GPP is working on IAB and 5G NR for 60Ghz – both have to come together

LTE Small cells deployments were limited due to

the availability of viable backhaul. The same issue
Will come in the way of 5G small cell deployments

One of the key technologies that will overcome this is

The IAB (Integrated Access Backhaul) work item in
3GPP.

IAB will enable flexible backhauling

Backhaul key to Small cell success (ORAN ??)
Private networks – Vertical industry opportunity

A need for “Private Network” specifications

for India specific spectrum scenarios
 VIRTUALIZATION – WHAT'S HAPPENING

8
Mapping ETSI MANO Framework to 5G

Enabling easy end to end orchestration is key to the success of

NFV/SDN
 BOTH RAN & CORE NETWORKS WILL BE
VIRTUALISED IN 5G NETWORKS
Flexible cloud-based applications and
services with network slices allocated
based on application type
Cloud-based O&M And OSS Virtual Virtual Virtual
Virtualised Mobile Core implemented as
Controlling cloud-based and App 1 App 1 App 1
virtual network functions on carrier-grade
hardware-based legacy
Cloud-based Network Core cloud infrastructure
infrastructure

O&M and OSS Carrier-grade cloud infrastructure coupling

SDN capabilities for robust IaaS/PaaS
services

Virtual RAN with

• LTE-Adv / 5G
Legacy RAN

• LWA/LAA based on physical hardware

Micro cell Small cell WiFi coexisting with virtual RAN
• New spectrum bands
Baseband Server Pool Legacy Network infrastructure
• New access technologies
• Split protocol architecture Early NFV deployments will be laying the
technology foundation for 5G and an investment to
LTE 5G-NR Wi-Fi mmWave
ensure readiness at technology maturity
Network Slicing – A tool to realize orchestration

Network slicing allows operators to open their infrastructure platform to concurrent

deployment of multiple logical self contained networks, orchestrated in different ways
according to their specific service requirements; such network slices are then (temporarily)
owned by tenants.
As these tenants have control over multiple layers, i.e. the physical layer, the virtualization
layer, and the service layer, of a 5G infrastructure, they are also called verticals: That is,
they integrate the 5G infrastructure vertically

NFV system implementations transfer existing monolithic applications to big virtual machine
appliances, each representing a single Virtual Network Function (VNF). Multiple VNFs are
then chained together using a Service Function Chain, which determines how packets are
forwarded from one VNF to another, to constitute a Network Service.
 Orchestration and MANO

The immaturity of MANO standards continues to come in the way of NFV implementation.

Complexity of integrating NFV components for effective deployment of MANO will continue
to be a challenge.

MANO standards have been evolving significantly, ONAP has gained momentum following
AT&T's contribution of its Enhanced Control, Orchestration Management and Policy code
(ECOMP). STILL ISSUES ABOUND
Key issues in realizing NFV/SDN

Element
Management
Virtualization and orchestration - Open Source
efforts

Too many open source projects out there

Among the main areas that are being developed by the open source groups, the following are still OPEN:

Policy-based resource management, analytics for visibility and orchestration, service verification with
regards to security and resiliency.
ONAP - Open Networking Automation Platform

The goal of ONAP is to provide the capabilities needed to orchestrate and manage the full
lifecycle of NFV deployments, provide the ability to deploy virtual network functions (VNFs)
in an automated manner

For NFV deployments to move beyond single-function virtualization to broad-scale NFV

architecture. These will require multivendor interoperability, performance at scale and

sophisticated orchestration.

Key for adoption is the integration of virtual functions with operations and business support
systems (OSS/BSS).

Many service providers would combine ONAP architecture with OpenDaylight, OpenStack
and Open Platform for NFV (OPNFV) for comprehensive open source NFV architecture.
The key question is HOW.
Multi Vendor Hybrid Virtual Network
Environments

Key gaps in managing multi-vendor hybrid virtual network environments, includes the lack
of:
1. A single Service Orchestration Manager (SOM) product to support multi-domain service
orchestration; Centralized policy management and enforcement
2. Dynamic inventory management, to provide real-time visibility into the network and IT
3. Cross-domain Orchestration. Typically, orchestrators focus on their own contained domain—such as
content delivery networks (CDNs), mobile backhaul, IP VPNs, and so on. For NFV/SDN to reach its
full potential, orchestration will need to break down these silos and happen across these domains.
There currently is no master “orchestrator of orchestrators” capability built into a single piece of
software that has an end-to-end view of the network.

4. Immature / lack of standards: Though groups such as the Open Networking Foundation (ONF), MEF,
TMForum, ETSI, and others each have done significant work to push standards closer to completion,
managing Hybrid deployments is still a key concern of service providers that needs to be addressed.
5G + NFV/SDN (5G PPP Architecture)

End to End orchestration is still THE key issue

 KEY ISSUES IN STANDARDIZATION

18
 List of Key Open Issues
Guaranteeing quality-of-service
Achieving a given quality-of-service in an NFV environment
Network Virtualization is changing the way the
with virtualized and distributed computing, storage and
telecommunications sector will deploy, extend and
networking functions is more challenging than providing the
operate their networks. The networks interconnecting
equivalent in discrete non-virtualized components. NFV has
the functions that compose a network service are
very strict requirements posed in terms of performance,
fundamentally affected in the way they route, process
stability and consistency. Although there are some tools and
and control traffic (i.e. network virtualization).
mechanisms to improve this, such as Enhanced Performance
Awareness (EPA), Single Root I/O Virtualization (SR-IOV),
Non-Uniform Memory Access (NUMA), Data Plane
Development Kit (DPDK), etc, these are still unsolved
Metrics for NFV characterization
challenges.
Another relevant aspect is the need for tools for diagnostics and measurement suited
for NFV. There is a pressing need to define metrics and associated protocols to
measure the performance of NFV. Specifically, since NFV is based on the concept of
taking centralized functions and evolving it to highly distributed SW functions, there is
a commensurate need to fully understand and measure the baseline performance of
Predictive analysis
such systems.
On top of diagnostic tools that enable an assessment of the QoS, predictive
analyses are required to react before anomalies occur. Due to the SW
Portability characteristics of VNFs, a reliable diagnosis framework could potentially
Portability in NFV refers to the ability to run a given VNF on multiple NFVIs, enable the prevention of issues by a proper diagnosis and then a reaction in
that is, guaranteeing that the VNF would be able to perform its functions with terms of acting on the potentially impacted service (e.g., migration to a
a high and predictable performance given that a set of requirements on the different compute node, scaling in/out, up/down, etc).
NFVI resources is met. Therefore, portability is a key feature that, if fully
enabled, would contribute to making the NFV environment achieve a better
reliability than a traditional system.
 List of Key Open Issues

Service Composition Separation of control concerns

Current network services deployed by operators often NFV environments offer two possible levels of SDN
involve the composition of several individual functions control. One level is the need for controlling the NFVI to
(such as packet filtering, deep packet inspection, load provide connectivity end-to-end among VNFs or among
balancing). These services are typically implemented by VNFs and PNFs (Physical Network Functions).
the ordered combination of a number of service A second level is the control and configuration of the
functions and is called a Service Function Chain (SFC) VNFs
themselves (in other words, the configuration of the
There are however many research challenges in this network service implemented by those VNFs), taking
area, as for example the ones related to composition advantage of the programmability brought by SDN. Both
mechanisms and algorithms to enable load balancing control concerns are separated in nature.
and improve reliability. The SFC working group is However, interaction between both could be expected in
working on an architecture for service function chaining order to optimize, scale or influence each other. Clear
[RFC7665] that includes the necessary protocols or mechanisms for such interaction are needed
protocol extensions to convey the Service Function
Chain and Service Function Path information to nodes
that are involved in the implementation of service
functions and Service Function Chains, as well as Network Function placement
mechanisms for steering traffic through service functions. Network function placement is a problem in any kind of network
telecommunications infrastructure. Moreover, the increased degree
of freedom added by network virtualization makes this problem even
more important, and also harder to tackle. Deciding where to place
virtual network functions is a resource allocation problem which
needs to (or may) take into consideration quite a few aspects:
resiliency, (anti-)affinity, security, privacy, energy efficiency, etc.
SUMMARY

5G Service – what are they?

Network Virtualization - Specification immaturity: Specification still evolving in IETF, ETSI

and 3GPP

Massive IOT, Edge Services………..take a guess

THANK YOU