5g Network Programmability For Mission Critical Applications
5g Network Programmability For Mission Critical Applications
ERICSSON
TECHNOLOGY
Scania
command
Data traffic center
prioritization interface Remote
driver
(5G) core
network
Internet
Ericsson test
Scania bus network at Scania
test track Control plane
User plane Prioritized video traffic
User plane Prioritized control traffic
User plane Non-prioritized traffic
(e.g. mobile broadband, infotainment)
5G NETWORK
PROGRAMMABILITY
✱ 5G NETWORK PROGRAMMABILITY
5G network
programmability FOR MISSION-CRITICAL APPLICATIONS
R AFIA INAM , A key differentiator of 5G systems from a unique and personalized experience.
ATHANASIOS previous generations will be a higher degree A number of use cases in mission-critical
K AR APANTEL AKIS, of programmability. Instead of a one-size-fits- scenarios can benefit from QoS programmability
LEO N ID M O KRUSH IN , because a cellular network’s connectivity
all mobile broadband service, 5G will provide
ELENA FERSMAN requirements – including latency, throughput,
the flexibility to tailor QoS to connectivity
service lifetime and cost – vary widely across
services to meet the demands of enterprise
different use cases. To support them all, we have
customers. This enables a new range of developed an application programming interface
mission-critical use cases, such as those (API) that allows third parties to specify and
involving connected cars, manufacturing request network QoS. We have also demonstrated
robots, remote surgery equipment, precision the usefulness of this API on a test mobile network
agriculture equipment, and so on. using a transport-related use case.
As part of this use case, we have been collaborating
■ Network programmability can support rapid with commercial vehicle manufacturer Scania to
deployment of new use cases by combining develop the QoS requirements for teleoperation.
cloud-based services with mobile network Teleoperation is the remote operation of an
infrastructure and taking advantage of new levels autonomous vehicle by a human operator in cases
of flexibility. Further, network programmability will where the vehicle encounters a situation that the
enable a greater number of enterprise customers to autonomous system cannot overcome by itself (a
use such services, and consumers will benefit from road obstacle or malfunction, for example).
support the volume and diversity of use cases Figure 2 illustrates the architecture of the system
with the current network management approach. on which we have implemented the API. In addition
They need a different means of managing the to deploying a standard EPC and LTE band-40 RAN,
network to stay competitive. In our view, an AF is deployed on an OpenStack-managed cloud.
developing an API is the logical first step toward This application functionality allows third parties
exposing a programmable network to the industry to set up QoS for their UEs through an API.
verticals. This approach will result in a solution that The AF consists of the following components:
is more responsive than rigid commercial offerings, a knowledge base module, an API endpoint module
such as preconfigured subscription packages. and a transformer.
Scania
command
Data traffic center
prioritization interface Remote
driver
(5G) core
network
Internet
Ericsson test
Scania bus network at Scania
test track Control plane
User plane Prioritized video traffic
User plane Prioritized control traffic
User plane Non-prioritized traffic
(e.g. mobile broadband, infotainment)
pertains to a characterization of the traffic in terms concept document, while each specific enterprise
of required throughput for both “uplink” and has more than one document. For example, in our
“downlink,” the former being data traffic case, there is an “automotive/teleoperation”
transmitted from the agent and the latter being the document. However, other documents for
opposite. Optionally, descriptors may also contain automotive can also exist, such as “automotive/
the type of data packets exchanged (for example, autonomous drive” or “automotive/remote fleet
UDP/IP or TCP/IP), as well as potentially the port management.” Because the data is stored as linked
or port range. For example, in the case of data, concepts from one domain concept document
“vehicle_control_traffic,” the data traffic can be reused in another.
descriptor identifies an uplink bandwidth
of 1Mbps and a downlink bandwidth of 1Kbps. API endpoint module
A combination of agents, QCIs and their This module composes API specifications from
associated data traffic descriptors are stored every domain concept document in the knowledge
in the knowledge base as a domain concept base. This API specification is RESTful, uses
document. Every use case has its own domain symmetric encryption (HTTPS) and can be called
HSS
S6a
MME
S1-MME S1-MME
eNB eNB
S1-U S1-U
SGW
Uu Uu S5/S8 Uu Uu
UE UE PGW Gx SAPC UE UE
EPC
Rx
Transformer
Knowledge
base
Domain Generic API
semantics call
API endpoint
Domain
knowledge
definition
AF
Ericsson
research
cloud QoS setup
Third party
from any third party. These API calls get translated specified in 3GPP TS 29.214. The Rx requests are
into generic concept calls that are subsequently sent directly to the PCRF node in order to set up
sent to the transformer module. Note that, in the “EPS bearer” (in other words, the data tunnel
addition to an API call for setup of specialized QoS, with the requested QoS). As is the case with the
there is another API call for teardown of this QoS. endpoint module, the transformer module can also
For example, when a vehicle is decommissioned translate a teardown request to an Rx request to
or does not need to be teleoperated, there can be revert to the lowest-priority default bearer
a call to tear down the QoS tunnel, so network (in most cases, QCI9).
resources can be allocated to UEs in other vehicles
or devices. Figure 3 provides an overview of
domain-specific and generic requests.
CONCEPTS FROM
ONE DOMAIN CONCEPT
Transformer module
The transformer module translates generic requests
DOCUMENT CAN BE REUSED
for QoS to Rx AAR requests, as these requests are IN ANOTHER
100.000
Color interpretation
<= 0.08% packet loss: unnoticeable in video
10.000
>0.08 – 0.5%: ghosting effect
5.086253 0.5% – 1%: artificial movement/dropped frames
1% – 5%: long pauses
1.3418724 5%+ impossible to follow
1.000
0.100
Percentage of packets lost
0.010
2Mbps 3Mbps 6Mbps 2Mbps 3Mbps 6Mbps 2Mbps 3Mbps 6Mbps 2Mbps 3Mbps 6Mbps 2Mbps 3Mbps 6Mbps 2Mbps 3Mbps 6Mbps
video video video video video video video video video video video video video video video video video video
0.001
No background traffic Some background traffic Extreme background traffic No background traffic Some background traffic Extreme background traffic
(0 Mbps) (4.2Mbps) (8.55Mbps) (0 Mbps) (4.2Mbps) (8.55Mbps)
QCI9 QCI5
Figure 4 Packet loss (in percentage of total packets) in best effort (QCIŁ9) and prioritized (QCI5) bearers
References
1. IEEE, International Conference on Intelligent Transportation Systems (November 2016) – Feasibility
Assessment to Realise Vehicle Teleoperation using Cellular Networks – Rafia Inam, Nicolas Schrammar, Keven
Wang, Athanasios Karapantelakis, Leonid Mokrushin, Aneta Vulgarakis Feljan and Elena Fersman, available at:
http://ieeexplore.ieee.org/document/7795920/
2. IEEE, International Conference on Future Internet of Things and Cloud (August 2016) – DevOps for IoT
Applications Using Cellular Networks and Cloud – Athanasios Karapantelakis, Hongxin Liang, Keven Wang,
Konstantinos Vandikas, Rafia Inam, Elena Fersman, Ignacio Mulas-Viela, Nicolas Seyvet and Vasileios
Giannokostas, available at: http://ieeexplore.ieee.org/document/7575883/
3. Ericsson Mobility Report, Improving Public Transport with 5G, November 2015, available at: https://www.
ericsson.com/res/docs/2015/mobility-report/emr-nov-2015-improving-public-transport-with-5g.pdf
4. IEEE, Conference on Emerging Technologies and Factory Automation (September 2015) – Towards automated
service-oriented lifecycle management for 5G networks (Best Paper) – Rafia Inam, Athanasios Karapantelakis,
Konstantinos Vandikas, Leonid Mokrushin, Aneta Vulgarakis Feljan, and Elena Fersman, available at: http://
ieeexplore.ieee.org/document/7301660/
ISSN 0014-0171
284 23-3306 | Uen