ETSI GS MEC-IEG 004 V1.1.1 (2015-11)

Mobile-Edge Computing (MEC); Service Scenarios

DGS/MEC-IEG004

General Information

• Status: Published
• Publication Date: 05-Nov-2015
• Technical Committee: MEC IEG - Industry Enabling Group
• Current Stage: 12 - Completion
• Due Date: 16-Nov-2015
• Completion Date: 06-Nov-2015

Standards Content (Sample)

ETSI GS MEC-IEG 004 V1.1.1 (2015-11)






GROUP SPECIFICATION
Mobile-Edge Computing (MEC);
Service Scenarios
Disclaimer
This document has been produced and approved by the Mobile-Edge Computing (MEC) ETSI Industry Specification Group
(ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

---------------------- Page: 1 ----------------------
2 ETSI GS MEC-IEG 004 V1.1.1 (2015-11)



Reference
DGS/MEC-IEG004
Keywords

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS MEC-IEG 004 V1.1.1 (2015-11)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 6
4 Service scenarios . 6
4.1 Intelligent video acceleration service scenario . 6
4.1.1 Description of scenario . 6
4.1.2 Motivation. 6
4.1.3 Problem statement . 6
4.1.4 Relation to MEC . 6
4.2 Video stream analysis service scenario . 7
4.2.1 Description of scenario . 7
4.2.2 Motivation. 7
4.2.3 Problem statement . 7
4.2.4 Relation to MEC . 7
4.3 Augmented reality service scenario . 8
4.3.1 Description of scenario . 8
4.3.2 Motivation. 8
4.3.3 Problem statement . 8
4.3.4 Relation to MEC . 8
4.4 Assistance for intensive computation . 9
4.4.1 Description of scenario . 9
4.4.2 Motivation. 9
4.4.3 Problem statement . 9
4.4.4 Relation to MEC . 9
4.5 Enterprise deployment of MEC . 10
4.5.1 Description of scenario . 10
4.5.2 Motivation. 10
4.5.3 Problem statement . 10
4.5.4 Relation to MEC . 10
4.6 Connected vehicles . 11
4.6.1 Description of scenario . 11
4.6.2 Motivation. 11
4.6.3 Problem statement . 11
4.6.4 Relation to MEC . 12
4.7 IoT gateway service scenario . 12
4.7.1 Description of scenario . 12
4.7.2 Motivation. 12
4.7.3 Problem statement . 13
4.7.4 Relationship to MEC . 13
Annex A (informative): Authors & contributors . 14
Annex B (informative): Bibliography . 15
History . 16

ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS MEC-IEG 004 V1.1.1 (2015-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile-Edge
Computing (MEC).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Mobile-Edge Computing provides IT service environment and cloud-computing capabilities within the Radio Access
Network (RAN) in close proximity to mobile device. MEC aims to reduce latency, ensure highly efficient network
operation, service delivery and ultimate personal experience. The term "Edge" in this context means the radio base
station itself (eNodeB, RNC, etc.), and servers within the radio network (e.g. at "aggregation points"). The presence of
MEC server at the edge of the RAN allows exposure to real-time radio and network information (such as subscriber
location, cell load, etc.) that can be leveraged by applications and services to offer context-related services; these
services are capable of differentiating the mobile broadband experience.
The Mobile-Edge Computing environment creates a new value chain and an energized ecosystem, which in turn can
create new opportunities for mobile operators, application and content providers whilst enabling them to play
complementary and profitable roles. Based on innovation and business value, this value chain will allow all players to
benefit from greater cooperation and better monetize the mobile broadband experience.
Mobile Operators can open up the radio network edge to third-party partners, allowing them to rapidly deploy
innovative applications and services towards mobile subscribers, enterprises and other vertical segments.
For application developers and content providers, the RAN edge offers a service environment with ultra-low latency
and high bandwidth as well as direct access to real-time radio and network information. Mobile-Edge Computing allows
content, services and applications to be accelerated, increasing responsiveness from the edge. The customer experience
can be proactively maintained through efficient network and service operations, based on insight into the radio and
network conditions.
Network vendors and technology providers can provide RAN equipment and base stations enhanced with cloud-
computing capabilities, by offering more powerful and flexible network elements able to satisfy the increasing needs of
the communication world.
The goal of the present document is to describe some service scenarios that can be delivered through the use of Mobile-
Edge Computing. These serve as examples of how MEC can stimulate innovative services and applications that would
create a better quality of experience for the end user. MEC will enable a large number of new kinds of applications and
services for multiple sectors (such as consumer, enterprise, health, etc.).

ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS MEC-IEG 004 V1.1.1 (2015-11)
1 Scope
The present document introduces a number of service scenarios that would benefit from the introduction of Mobile-
Edge Computing (MEC) technology. Mobile-Edge Computing enhances the Mobile Access Network with MEC servers
that enable applications to run in the mobile edge. Due to the proximity of the server into the Access network, there is a
latency reduction of delivering such applications or services. Such applications can expose information that can be used
to optimize the network and services, reduce latency, and support creating personalized and contextualized services.
Moreover, new and innovative analytics services enable the operator to monitor usage and service quality. Internet of
Things (IOT) applications or enterprise communications can benefit greatly from MEC, as it allows service delivery in
close proximity to the actual terminal devices.
The focus of the present document is to introduce or provide a non-exhaustive set of service scenarios. It is not the
intent nor does the present document provide any requirements.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
analytics: processing which makes use of data to provide actions, insights and/or inference
augmented reality: live direct or indirect view of a physical, real-world environment whose elements are enhanced, or
supplemented, by computer-generated sensory
Internet of Things (IoT): device, machine or entity connected to any other device, machine or entity through a
network
ETSI

---------------------- Page: 5 ----------------------
6 ETSI GS MEC-IEG 004 V1.1.1 (2015-11)
vehicle: human transport including automobile, car, truck, plane, train, motorcycle
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
DSRC Dedicated Short Range Communications
IoT Internet of Things
IP-PBX Internet Protocol Private Branch Exchange
LAN Local Area Network
LTE Long Term Evolution
MEC Mobile-Edge Computing
PBX Private Branch Exchange
QoE Quality of Experience
RAN Radio Access Network
RNC Radio Network Controller
TCP Transmission Control Protocol
WLAN Wireless Local Area Network
4 Service scenarios
4.1 Intelligent video acceleration service scenario
4.1.1 Description of scenario
Eliminating mobile content delivery inefficiencies by guiding sources as to real-time network capacity.
A Radio Analytics application located at the RAN provides the video server with an indication on the throughput
estimated to be available at the radio downlink interface. The information can be used to assist TCP congestion control
decisions and also to ensure that the application-level coding matches the estimated capacity at the radio downlink.
4.1.2 Motivation
Improve the end user's Quality of Experience (QoE) by reducing the content's time-to-start as well as video-stall
occurrences, and guarantee maximum utilization of the radio network's resources.
4.1.3 Problem statement
The behaviour of the Transmission Control Protocol (TCP), which assumes that network congestion is the primary
cause for packet loss and high delay, can lead to the inefficient use of a cellular network's resources and degrade
application performance and user experience.
The root cause for this inefficiency lies in the fact that TCP has difficulty adapting to rapidly varying network
conditions. In cellular networks, the bandwidth available for end devices can vary by an order of magnitude within a
...