flexible air interface for scalable service delivery...

Call: H2020-ICT-2014-2

Project reference: 671660

Project Name:

Flexible Air iNTerfAce for Scalable service delivery wiThin wIreless Communication networks of the 5th Generation (FANTASTIC-5G)

Internal Report IR2.1

Use cases, KPIs and requirements

Date of delivery: 01/10/2015 Version: 1.8.0

Start date of project: 01/07/2015 Duration: 24 months

Document properties:

Document Number: IR2.1

Document Title: Use cases, KPIs and requirements

Editor(s): Davide Sorbara, Marco Caretti (Telecom Italia S.p.A.)

Authors: Davide Sorbara (Telecom Italia S.p.A.), Marco Caretti (Telecom Italia S.p.A.), Martin Schubert (Huawei Technologies Duesseldorf GmbH), Andreas Georgakopoulos (WINGS ICT Solutions)

Contractual Date of Delivery: 01/10/2015

Dissemination level: CO1

Status: Final

Version: 1.8.0

File Name: FANTASTIC-5G_IR2 1_v1 8

Abstract

5G will have to cope with a high degree of heterogeneity in terms of (core) services: 1-mobile

broadband, 2-massive machine and 3-mission critical communications, 4-broad-/multicast services

and 5-vehicular communications. Consequently, diverse and often contradicting Key Performance

Indicators (KPIs) need to be supported, such as high capacity/user-rates, low latency, ubiquitous

coverage, high mobility, massive number of devices, high reliability/availability or low

complexity/energy consumption.

This Internal Report defines the 5G use cases and the corresponding KPIs and requirements, in order

to provide guidelines as a reference to all Work Packages for their activities, in the framework of the

FANTASTIC-5G project.

The aforementioned five core services are combined into several use cases with their own KPIs and

requirements. The downselection of the most representative and challenging use cases is performed

via an agreed set of criteria, formulated in a way that ensures that those uses case can be successfully

enabled in 5G systems that operate below 6 GHz. Moreover, the selected use cases will be accurately

evaluated through system level simulations.

The NGMN, 3GPP, METIS and METIS II frameworks are taken into account in the overall use case’

identification and selection process as well as in the corresponding KPIs and requirements definition.

Keywords

5G, flexibility, scalability, mobile broadband, massive machine communications, mission critical

communications, broadcast, multicast, vehicle, scenario, core service, composite service, use case,

KPI, requirement, user experience, system performance, data rate, bandwidth, data throughput,

capacity, latency, coverage, mobility, device, reliability, availability, complexity, energy, selection.

1 CO = Confidential, only members of the consortium (including the Commission Services)

PU = Public

FANTASTIC-5G Internal Report IR2.1

Dissemination level: Confidential / 67

Executive Summary

5G will have to cope with a high degree of heterogeneity in terms of services, device classes,

deployment types, environments and mobility levels.

FANTASTIC-5G will design the air interface of the 5G cellular networks for below 6 GHz with

the main objective of leading the definition of the next generation air interface below 6 GHz in

standardization.

FANTASTIC-5G advocates a single air interface for 5G, which is flexible, versatile, scalable

and efficient in order to address the requirements of the beyond 2020 era. These requirements

concern a wide variety of aspects ranging from ubiquitous low-cost integrated access to high-

rate services/applications, to energy consumption, as well as the massive number of connected

devices with very different characteristics.

This document defines the use cases, Key Performance Indicators (KPIs) and corresponding

requirements, in order to provide guidelines as a reference to all Work Packages for their

activities, in the framework of FANTASTIC-5G.

The five core services of the project, i.e.:

1. Mobile BroadBand (MBB)

2. Massive Machine Communications (MMC)

3. Mission Critical Communications (MCC)

4. Broadcast/Multicast Services (BMS)

5. Vehicle-to-vehicle and vehicle-to-infrastructure communications (V2X)

are combined to form several use cases with their own KPIs and requirements, and the

downselection of the most representative and challenging use cases are performed via an agreed

set of criteria.

The KPIs, i.e.:

KPI 0: User experienced data rate

KPI 1: Traffic density

KPI 2: Latency

KPI 3: Coverage

KPI 4: Mobility

KPI 5: Connection density

KPI 6: Reliability/availability

KPI 7: Complexity reduction

KPI 8: Energy efficiency

and the corresponding requirements are then defined for all the selected use cases:

Use Case 1: 50 Mbps everywhere

Use Case 2: High speed train

Use Case 3: Sensor networks

Use Case 4: Tactile Internet

Use Case 5: Automatic traffic control / driving

Use Case 6: Broadcast like services: Local, Regional, National

Use Case 7: Dense urban society below 6GHz

The NGMN, 3GPP, METIS and METIS II frameworks are taken into account in the overall use

case identification and selection process as well as in the corresponding KPIs and requirements

definitions.



Table of Contents

List of Figures .............................................................................................................................. 5

List of Tables ............................................................................................................................... 6

List of Acronyms and Abbreviations ......................................................................................... 7

1 Introduction......................................................................................................................... 10 1.1 Overall 5G vision ......................................................................................................... 10

1.1.1 Overview of trends enabling cellular technology ................................................... 10

1.2 Objective of the document ........................................................................................... 13

1.3 Structure of the document ............................................................................................ 13

1.4 Terminology ................................................................................................................ 13

1.5 Methodology ................................................................................................................ 14

2 Scenarios, core services, composite services, KPIs and requirements ........................... 15 2.1 KPIs and requirement levels for each core service ...................................................... 15

2.1.1 Core services ........................................................................................................... 16

2.1.2 KPIs associated to the core services ....................................................................... 17

2.1.3 Requirement levels for the KPIs associated to the core services ............................ 18

2.2 Composite services mapping to use cases ................................................................... 19

2.2.1 Composite services mapping to NGMN use cases ................................................. 20

2.2.2 Composite services mapping to 3GPP SMARTER SI use cases ............................ 25

2.2.3 Composite services mapping to METIS and METIS II use cases .......................... 27

2.2.4 Use cases (i.e. composite services) list coming from mapping to NGMN,

3GPP SMARTER SI, METIS and METIS II use cases ......................................... 30

3 Selected use cases with the associated KPIs and requirements ...................................... 33 3.1 Use cases ( composite services) selection .................................................................... 33

3.2 Overview on KPIs and corresponding requirements for all the selected use cases ..... 35

3.2.1 Use case 1: 50 Mbps everywhere ........................................................................... 36

3.2.2 Use case 2: High speed train ................................................................................... 40

3.2.3 Use case 3: Sensor networks ................................................................................... 44

3.2.4 Use case 4: Tactile Internet ..................................................................................... 49

3.2.5 Use case 5: Automatic traffic control / driving ....................................................... 53

3.2.6 Use case 6: Broadcast like services: Local, Regional, National ............................. 58

3.2.7 Use case 7: Dense urban society below 6GHz ....................................................... 62

4 Conclusions .......................................................................................................................... 66

5 References ............................................................................................................................ 67



List of Figures

Figure 1-1: Growth of mobile data traffic (source ITU radio communications group, Oct. 2014)

..................................................................................................................................................... 11

Figure 1-2: From trends to the FANTASTIC-5G objectives (the first 4 technical ones) ............. 12

Figure 2-1: Core services and related KPIs with different requirement levels ........................... 19

Figure 2-2: 5G Use Case Families and related examples – NGMN Source [NGM15] .............. 20

Figure 2-3: Use Case Categories and Use Cases definition – NGMN Source [NGM15] ........... 21



List of Tables

Table 2-1: User Experience KPIs and Requirements – NGMN Source [NGM15] ..................... 22

Table 2-2: System Performance KPIs and Requirements – NGMN Source [NGM15] ............... 23

Table 2-3: Relationship between NGMN use cases and FANTASTIC-5G core services ............ 24

Table 2-4: Relationship between SMARTER use cases and NGMN use cases ........................... 26

Table 2-5: Relationship between METIS / METIS II use cases and NGMN use cases ............... 29

Table 2-6: List of the overall potential FANTASTIC-5G use cases and mapping to the

FANTASTIC-5G core services .................................................................................................... 31

Table 3-1: Use case 1: 50 Mbps everywhere – requirements definition ..................................... 37

Table 3-2: Use case 2: High speed train – requirements definition ............................................ 41

Table 3-3: Use case 3: Sensor networks – requirements definition ............................................ 45

Table 3-4: Use case 4: Tactile Internet – requirements definition .............................................. 50

Table 3-5: Use case 5: Automatic traffic control / driving – requirements definition ................ 54

Table 3-6: Use case 6: Broadcast like services: Local, Regional, National – requirements

definition ..................................................................................................................................... 59

Table 3-7: Use case 7: Dense urban society below 6GHz .......................................................... 62



List of Acronyms and Abbreviations

2G 2nd

Generation

3D 3 Dimensions

3G 3rd

Generation

3GPP 3rd

Generation Partnership Project

4G 4th

Generation

5G 5th

Generation

ACK ACKnowledgement

ADWICS Advanced Wireless Communications Study Committee

AI Air Interface

ARIB Association of Radio Industries and Businesses, Japan

ARPU Average Revenue Per User

ARQ Automatic Repeat reQuest

BMS Broadcast/Multicast Service

BMSC Broadcast/Multicast Service Centre

C Cooperative

C-ITS

CIoT

Cooperative Intelligent Transportation Systems

Cellular IoT

CN Core Network

CO COnfidential

CP Control Plane

D Deliverable

D2D Device-to-Device

DCM DoCoMo

DL DownLink

E2E End-to-End

EC European Commission

EDGE Enhanced Data rates for Global Evolution

EMF Electro-Magnetic Field

EPS Evolved Packet System

ERC European Research Centre

ETSI European Telecommunications Standards Institute

FANTASTIC-

5G

Flexible Air iNTerfAce for Scalable service delivery wiThin wIreless Communication

networks of the 5th

Generation

FS Feasibility Study

GERAN GSM/EDGE Radio Access Network

GP GERAN Plenary

GSM Global System for Mobile communications



GSMA GSM Association

H2020 Horizon 2020

HARQ Hybrid ARQ

HD High Definition

HQ HeadQuarters

ICT Information and Communication Technologies

IDATE Institut de L'audiovisuel et des Télécommunications en Europe

IMT International Mobile Telecommunications

IoT Internet of Things

IP Internet Protocol

IR Internal Report

ITRI Industrial Technology Research Institute, Taiwan

ITS Intelligent Transportation Systems

ITU International Telecommunication Union

KPI Key Performance Indicator

KTH Kungliga Tekniska Högskolan

LC Low Complexity

LTE Long Term Evolution

LTE-A

M2M

LTE-Advanced

Machine-to-Machine

MAC Medium Access Control

MBB Mobile BroadBand

MBMS Multimedia Broadcast/Multicast Services

MCC Mission Critical Communications

MCL Maximum Coupling Loss

METIS Mobile and wireless communications Enablers for the Twenty-twenty Information Society

MIMO Multiple-Input Multiple-Output

MMC Massive Machine Communications

MNO Mobile Network Operator

MTC Machine Type Communications

NACK Negative ACKnowledgement

NGMN Next Generation Mobile Network

P2M Point-to-Multi-point

P2P Person-to-Person or Point-to-Point

PHY PHYsical layer

PPP Public Private Partnership

PU PUblic

QoE Quality of Experience

QoS Quality of Service



R Radiocommunication Study Groups or Release or Report

R&D Research and Development

RAN Radio Access Network

RAT Radio Access Technology

Rel Release

RP RAN Plenary

RRM Radio Resource Management

RX Reception

SA Services and System Aspects

SFN Single Frequency Network

SI Study Item

SID Service Integration Driver or Study Item Description

SINR Signal-to-Interference+Noise Ratio

SMARTER Study on New Services and Markets Technology Enablers

SNR Signal-to-Noise Ratio

SP SA Plenary

TC Test Case

TR Technical Report

TS Technical Specification

TSG Technical Specification Group

TX Transmission

UC Use Case

UDN Ultra-Dense Networks

UE User Equipment

UL UpLink

uMTC Ultra-reliable and low-latency MTC

UoM Units of Measurement

UP User Plane

UPV Universitat Politecnica de Valencia

V2D Vehicular-to-Device

V2I Vehicle-to-Infrastructure

V2P Vehicle-to-Person

V2V Vehicle-to-Vehicle

V2X Vehicle-to-anything

VoIP Voice over IP

VRU Vulnerable Road User

WI Work Item

WID Work Item Description

WP Work Package or Working Party



1 Introduction

5G will have to cope with a high degree of heterogeneity in terms of services, device classes,

deployment types, environments and mobility levels.

FANTASTIC-5G will develop a new multi-service Air Interface (AI) operating below 6 GHz

through a modular design. To allow the system to adapt to the anticipated heterogeneity, the

pursued properties are: flexibility, scalability, versatility, efficiency and future-proofness. The

work will also include intense validation and system level simulations.

This document defines the use cases, KPIs and corresponding requirements, in order to provide

guidelines as a reference to all Work Packages for their activities, in the framework of the

FANTASTIC-5G project.

The NGMN, 3GPP, METIS and METIS II frameworks are taken into account in the overall use

case identification and selection process as well as in the corresponding KPIs and requirements

definitions.

1.1 Overall 5G vision

5G communications are expected to be characterized by numerous devices and networks that

are foreseen to be interconnected while traffic demand will continuously rise compared to the

current levels. Heterogeneity will also be a feature of the emerging wireless world as mixed

usage of cells of various sizes with different characteristics and technologies are necessary in

order to meet 5G requirements for increased capacity and increased performance with reduced

delay [ARI14], [GSM14], [5GP15].

The 5G vision of the FANTASTIC-5G project is based on a framework that is related to the

topic Future Internet in the Horizon 2020 Work Programme 2014-2015. The project addresses

the call ICT 14-2014: Advanced 5G Network Infrastructure for the Future Internet, and hence

adopts the corresponding requirements for the 5G system, such as 1000 times higher mobile

data volume per geographical area; 10 to 100 times higher number of connected devices and 10

to 100 times higher typical user data rate. Moreover, 10 times lower energy consumption, 5

times reduced end-to-end latency as well as ubiquitous 5G access including in low density areas

are considered.

Framed in this context, FANTASTIC-5G is pursuing the development of a highly flexible,

versatile and scalable air interface for the forecasted multitude of service classes and device

types with reasonable complexity and the highest efficiency for frequency bands below 6 GHz.

The new air interface will meet the requirements on the identified service KPIs with increased

flexibility, reliability, future-proofness as well as complexity reduction and energy efficiency.

Towards this end, a set of five core services are defined in FANTASTIC-5G as the backbone of

the future 5G service ecosystem: 1-Mobile BroadBand (MBB), 2-Massive Machine (MMC) and

3-Mission Critical Communications (MCC), 4-Broad-/Multicast Services (BMS) and 5-

Vehicular communications (V2X).

1.1.1 Overview of trends enabling cellular technology

Cellular technology has been renewed about every decade since the introduction of GSM, which

can be considered as the main representative of the 2nd

Generation (2G) cellular technology. In

the 1990s, GSM became widespread and offered voice services all around the globe. With the

rising success of the World Wide Web, data services became the key driver for the next

generation of cellular technology. Around 2000, the introduction of the 3rd

Generation (3G)

cellular technology enabled the rapid growth of mobile data services. Around 2010, the

introduction of 4G (LTE - Long Term Evolution) has brought major improvements to wireless



broadband access to Internet services. The next generation (5G) is expected to arrive around

2020. FANTASTIC-5G is a timely proposal set out to design the 5G air interface and prepare

inputs for standardization whose time-frame is expected to start during the project lifetime.

There are five trends which are pushing the limits of 4G, pointing towards a need for the 5th

generation cellular technology:

Trend 1 – Increase in capacity: The demand for wireless data is predicted to increase

significantly, resulting in 1000 times higher mobile data volumes and 10-100 times

higher end user data rates, as depicted in Figure 1-1.

Trend 2 – Increase in the number of connected devices: The number of connected

devices is predicted to increase by a factor of 10-100, which means that up to 300,000

devices need to be served per access point.

Trend 3 – Increase in reliability: Wireless connectivity will be applied to new use cases

that require extremely reliable connections (typically 99.999% availability and

reliability) and mission-critical communications, such as vehicle-to-vehicle

coordination, critical control of the power grid, etc.

Trend 4 – Decrease in latency: Remote presence and tactile Internet impose stringent

latency constraints on the end-to-end connection, including the wireless part. Forecasts

indicate that the latency should be decreased by a factor of 5 in order to enable such

services.

Trend 5 – Increase in efficiency: Efficiency in terms of resource utilization (e.g.

energy, spectrum) is becoming more and more pronounced. It is seen as an

indispensable ingredient for a healthy/sustainable ICT market/business and

environment.

Figure 1-1: Growth of mobile data traffic (source ITU radio communications group, Oct. 2014)

The challenge for 5G is therefore not only to increase the user rates or the capacity (as has been

so far for the former generations), but also to master the wide variety of requirements/conditions

as observed via the above trends. Consequently there is a need to work towards a new 5G air

interface that will offer much more than just a faster variant of 4G. FANTASTIC-5G undertakes

such a work for frequencies below 6 GHz.



Driven by the above trends, FANTASTIC-5G sets out a vision on the 5G air interface with the

following key characteristics:

1. flexibility to support the broad class of services with their associated (broad class) of KPIs;

2. scalability to support the high number of devices;

3. versatility to support the diverse device types and traffic/transmission characteristics;

4. efficiency to support the requirements on energy consumption and resource utilisation;

5. future-proofness to support easy integration of new features.

In order to bring this vision into reality, FANTASTIC-5G identified high level measurable

objectives to be achieved (the first 4 technical ones being shown also in Figure 1-2):

Objective 1: To develop a highly flexible, versatile and scalable air interface to enable

the in-band coexistence of highly differing services, device types and

traffic/transmission characteristics;

Objective 2: To design an air interface enabling ubiquitous coverage and high capacity

where and when required;

Objective 3: To develop an air interface being highly efficient in terms of energy and

resource consumption;

Objective 4: To render 5G more future-proof than former generations through easier

introduction of new features;

Objective 5: To evaluate and validate the developed concepts by means of system level

simulations and hardware proof of concepts for selected components;

Objective 6: To build up consensus on reasonable options for 5G standardization

among the major industrial partners of the project that are also voting members in 3GPP

and to push the innovations of the project for standardization (through study items).

Figure 1-2: From trends to the FANTASTIC-5G objectives (the first 4 technical ones)



1.1.2 Enabling solutions and technologies

FANTASTIC-5G will partly build on the technical components developed in the FP7-projects

METIS (Mobile and wireless communications Enablers for Twenty-twenty (2020) Information

Society) and 5GNOW (5th Generation Non-Orthogonal Waveforms for Asynchronous

Signalling), which had the objective of developing fundamentally new technical solutions for

global mobile and wireless communication in the year 2020. A compact summary of METIS

technology components is given in Annex B of Deliverable 6.5 [METIS15-D65].

In addition, FANTASTIC-5G will consider the state-of-art summarized, e.g. by white papers

[5GP15], [4GA14], [5GFK15], [ARI14] and others.

1.2 Objective of the document

The objective of the document is to define the use cases, the KPIs and the corresponding

requirements used as a reference in the framework of the FANTASTIC-5G project.

The combination of the core services into several use cases with their own KPIs and

requirements, and the downselection of the most representative and challenging use cases are

performed via an agreed set of criteria.

The NGMN, 3GPP, METIS and METIS II frameworks are taken into account in the

identification process of the overall use cases.

This internal report will serve as a reference for all work packages. It will provide guidelines for

the development of technical solutions, simulations and demonstrations.

1.3 Structure of the document

The document first reports the used terminology (Sect. 1.4) and describes the methodology used

for downselecting the most representative and challenging use cases (Sect. 1.5).

Sect. 2 introduces the KPIs and requirement levels for each core service (Sect. 2.1), derives the

composite services by making the link between the composite services and the use cases coming

from NGMN (Sect. 2.2.1), 3GPP SMARTER SI (Sect. 2.2.2) and METIS/METIS II (Sect.

2.2.3). The summary of all the potential use cases to be considered by FANTASTIC-5G are

listed in Sect. 2.2.4.

Sect. 3.1 applies the selection process to the list of all the potential use cases as per the

methodology described in Sect. 1.5. The KPIs and corresponding requirements for all the

selected use cases are then defined in Sect. 3.2.

Finally Sect. 4 reports the conclusions, highlighting guidelines to all work packages using this

Internal Report as a reference for their activities.

1.4 Terminology

The following definitions apply in this document and in all the future Deliverables and Internal

Reports of the project that use this Internal Report as a reference for their activities:

Core service: a service able to encompass, group and identify more services presenting

similar characteristics in terms of KPIs and requirements and their relative importance, but

not (necessarily) the same absolute (range of) values of the corresponding requirements. In

this document and in the framework of the project the words “core service” and “service”

are used interchangeably. In the project, 5 core services are identified and described in Sect.

2.1.1.



Composite service: a single core service or a combination of two or more core services

denoting a real-life use case. The composite services inherit the KPIs of the core services

that compose them. In this document and in the framework of the project the words

“composite service” and “use case” are used interchangeably. The variety of possible

composite services is identified and described in Sect. 2.2 and the composite services

selected in the project are identified and described in Sect. 3.1, following the criteria based

on the selection process highlighted in Sect. 1.5.

KPI: a key performance indicator is identified, described and associated in relation to the 5

core services defined in the project. For each core service a KPI presents a primary,

secondary or tertiary requirement level, depending on its relevance with respect to that core

service. At the core service level the importance of a KPI is denoted in relative terms, whilst

for each composite service any KPI leads to absolute (range of) values of the corresponding

requirements. The KPIs for each core service are identified and described in Sect. 2.1.2 in

relative terms, whilst the KPIs for the selected composite services are identified and

described in Sect. 3.2 in absolute terms.

Requirement: for each core service a requirement denotes a relative importance level for a

given KPI, whilst for any selected composite service it is described by absolute (range of)

values derived from a given KPI. The higher the relative requirement level of the

corresponding KPI on a per core service basis, the more challenging the corresponding

absolute (range of) values and therefore the requirement itself for that KPI on a per

composite service basis. The requirements for each core service are identified and described

in Sect. 2.1.3 in relative terms for any KPI, whilst the requirements for the selected

composite services are identified and described in Sect. 3.2 in absolute terms for any

corresponding inherited KPI.

1.5 Methodology

The trends described in Sect. 1.1.1 facilitate new services with diverse application areas, e.g.

connected devices, vehicle-to-vehicle coordination, critical control of the power grid, remote

presence, tactile Internet, and more. These services can be grouped into the following 5 core

services:

1. Mobile BroadBand (MBB)

2. Massive Machine Communications (MMC)

3. Mission Critical Communications (MCC)

4. Broadcast/Multicast Services (BMS)

5. Vehicle-to-vehicle and vehicle-to-infrastructure communications (V2X).

In the framework of the 5 core services identified in the project and described in Sect. 2.1.1, 9

KPIs are introduced and highlighted in Sect. 2.1.2 and the corresponding requirement levels are

shown in Sect. 2.1.3.

The five core services compose the use cases with their own KPIs and requirements, either as a

single core service or as the combination of two (or more) core services leading to composite

services reported in Sect. 2.2.

The downselection of the most representative and challenging use cases is performed via an

agreed set of criteria, formulated in a way that ensures that those uses cases can be successfully

enabled in 5G systems that operate below 6 GHz. Moreover, the selected use cases will be

accurately evaluated through system level simulations.

The NGMN, 3GPP and METIS / METIS II frameworks are taken into account in the overall use

case identification and in the selection process as well as in the corresponding KPIs and

requirements.

The agreed set of criteria for selecting the use cases is as follows:



1. select use cases not covered by LTE and LTE-Advanced or even earlier RATs;

2. select use cases not covered by higher frequencies (e.g. above 6 GHz) RATs;

3. select use cases that encompass and are more demanding than other use cases (in terms of

KPIs and corresponding requirements) composed by the same core services;

4. select use cases that are more representative of an NGMN use case category2;

5. select uses cases collecting more preferences among operators (e.g. because of being able

to address new services and/or markets and therefore expected to be more successful);

6. select use cases whereby simulations can be carried out with the simulators made available

in the framework of the project;

7. select use cases in line with the ongoing activity in 3GPP (in order to be able to contribute

first to the feasibility study and then to the normative work in 3GPP).

The outcome of the above selection process of the use cases identified in Sect. 2.2 is the list of

the selected use cases reported in Sect. 3.1.

The KPIs and corresponding requirements for all the selected use cases are described in Sect.

3.2.

2 Scenarios, core services, composite services, KPIs and requirements

The 5 core services introduced in Sec. 1.5, the 9 KPIs and the corresponding relative

requirement levels (in terms of their relevance) are described in Sects. 2.1.1, 2.1.2 and 2.1.3,

respectively.

Based on the above components, various possible use cases (as core or composite services) are

identified and described in Sects. 2.2.1, 2.2.2 and 2.2.3, taking into account the NGMN, 3GPP

and METIS / METIS II frameworks, respectively.

Sect. 2.2.4 reports the list of all the possible use cases derived by the above analysis: the list is

further subject to selection performed in Sect. 3.1, following the criteria-based selection process

described in Sect. 1.5.

2.1 KPIs and requirement levels for each core service

This Section introduces the 5 core services (Sect. 2.1.1) defined in the framework of the project

and considered to be able to encompass, group and identify more services presenting similar

characteristics in terms of KPIs, requirements and their relative importance. The group of use

cases identified by the same core service can have different absolute (range of) values of the

corresponding requirements. For this reason the use cases need to be identified (Sect. 2.2) and

selected (Sect. 3.1).

The 9 KPIs associated to the 5 core services are defined (Sect. 2.1.2) and split between User

Experience KPIs and System Performance KPIs, highlighting their differences on one side and

the need to meet both categories on the other side, in order to provide efficient and successful

services from the perspective of MNOs and the users, respectively.

2 For each NGMN use case category, one set of requirements values is given, which is representative of the extreme

use cases in the category. As a result, satisfying the requirements of a category leads to satisfying the requirements

of all the use cases in this category. More details are provided in Sect. 2.2.1.



The relative requirement levels for the 9 KPIs associated to the 5 core services are identified

(Sect. 2.1.3), pointing out the differences between the “relative” requirement level for a KPI

associated to a core service and the “absolute” requirement for a KPI associated to a use case.

These differences therefore lead to the need of defining “absolute” requirements for the KPIs

associated to all the selected use cases (Sect. 3.2).

2.1.1 Core services

In this document and in the framework of the project the following 5 core services are defined:

1. Mobile BroadBand (MBB): 5G will have to support mobile broadband connections as of

today, but with increased capacity, efficiency and data transmission rates. Typical use cases

corresponding to MBB are multimedia streaming, combinational services including Voice

over IP (VoIP) as one of the services, internet browsing, videoconferencing, file downloads

and uploads to the cloud, some gaming services, etc.

2. Massive Machine Communications (MMC): MMC can be considered as one part of

Machine Type Communications (MTC) [22.368], [23.888], [36.888], [45.820], [GP-

150354], [RP-141660]. In MMC there is a massive amount of sensors/meters/actuators that

are deployed anywhere in the landscape (e.g. fire sensors in areas with high danger of forest

fires, sensors for water quality inspection/management, smoke alarm detectors, power

failure notifications, tamper notifications, actuators to control access, temperature, lighting

in buildings or traffic lights in the context of smart cities, etc.) and that need to access the

wireless network. In most of the cases, MMC traffic involves relatively small packets per

connection and therefore requires low throughput per device. In addition, a typical

characteristic of MMC is that the sensors must be robust, simple (i.e. low-cost), able to

operate on substantially long battery lives and reachable in challenging coverage conditions,

e.g. indoor and basements. Today, this is also known as “low-end Internet of Things (IoT)”.

Typical use cases corresponding to MMC are smart metering, natural ecosystem

monitoring, remote maintenance/control, fleet/parcel tracking/tracing, etc.

3. Mission Critical Communications (MCC): MCC includes another type of MTC which

implies a wireless connectivity, where sensor messages need to be transmitted between the

respective communication partners while satisfying one or several of the following: very

low response times, very high reliability and very high availability. Typical use cases of

MCC are private safety and security applications (e.g. video surveillance and intrusion

detection), vital sign monitoring, factory automation, etc. It has to be noted that MCC also

addresses person-to-person (P2P) communications in the framework of e.g. natural disasters

and public safety.

4. Broadcast/Multicast Services (BMS): BMS involves simultaneous content delivery in a

“one-to-many” or “many-to-many” mode. Efficient integration of BMS into 5G will render

valuable spectrum resources available for other (unicast) services. Typical examples of

BMS are not only the well-known mobile TV and digital radio cases, but also

software/firmware updates/downloads; targeted use cases could be “Stadium 2.0” dedicated

coverage or “Smart Cities” (e.g. digital signage). In the specific case of multimedia content

delivery, BMS is known as Multimedia Broadcast /Multicast Service (MBMS).

5. Vehicle-to-vehicle and vehicle-to-infrastructure communications (V2X): V2X implies

direct wireless connectivity either between vehicles (Vehicle-to-Vehicle, V2V) or between

vehicles and the roadside/beyond (Vehicle-to-Infrastructure, V2I) [RP-151109]. Today, also

known as Intelligent Transportation Systems (ITS), V2X consists of use cases where other 4

core services (MBB, MMC, MCC and BMS) involve nodes with high speeds. Typical

examples are road safety (e.g. collision avoidance) which is the combination of V2X with

MCC, pay-as-you-drive which is the combination of V2X with MMC and infotainment

which is the combination of V2X with BMS and/or MBB.



2.1.2 KPIs associated to the core services

In relation to the above 5 core services, the main 9 KPIs for 5G are identified hereafter:

KPI 0: User experienced data rate

KPI 1: Traffic density (to achieve high system capacity)

KPI 2: Latency

KPI 3: Coverage (to provide ubiquitous access)

KPI 4: Mobility

KPI 5: Connection density

KPI 6: Reliability/availability

KPI 7: Complexity reduction

KPI 8: Energy efficiency

The above KPIs can be classified in 2 categories:

User Experience KPIs: 0, 2, 33, 4, 6

System Performance KPIs: 1, 3, 5, 7, 8

The User Experience KPIs directly impact the QoS and the overall QoE for the user of a given

service, whilst the System Performance KPIs mostly relate to the service delivery efficiency

from the mobile network operator’s (MNO’s) perspective.

Both categories are equally important, as the following statements show. Failing to meet the

User Experience KPIs leads to lack of customers for delivering a service (i.e. meeting the

System Performance KPIs), even though the service is delivered efficiently. Failing to meet the

System Performance KPIs leads to lack of MNOs providing a service despite meeting users’

expectations (i.e. meeting the User Experience KPIs).

Even though many KPIs are self-explanatory, nevertheless some of them may need further

clarifications. The explanations for those KPIs that need further clarifications can be found

below:

KPI 0: the data rate experienced by the user directly relates to the bandwidth allocated to

the service. In most cases, the allocated service bandwidth is shared with other users,

depending on the traffic load, and the fraction of the actually allocated bandwidth is

evaluated on average over the entire service duration rather than instantaneously. It is

worthwhile noting that it is meaningful to consider KPI 0 in conjunction with other KPIs,

e.g. KPI 1, KPI 4 and KPI5, due to the trade-offs between them. The actual (range of)

values of the corresponding requirement are expected to strongly depend on the specific use

case at hand.

KPI 2: Latency is defined as in the NGMN white paper [NGM15]. We differentiate

between E2E latency (more related to the user experience) and the User Plane Latency

(more related to the air interface design).

o E2E Latency: Measures the duration between the transmission of a small data

packet from the application layer at the source node and the successful reception at

the application layer at the destination node plus the equivalent time needed to carry

the response back (if foreseen).

3 Even if KPI3 is considered a System Performance KPI, it could be considered a User Experience KPI as well since

it is a crucial element which impacts both aspects.



o User Plane Latency: Measures the time it takes to transfer a small data packet from

user terminal to the Layer 2 / Layer 3 interface of the 5G system destination node,

plus the equivalent time needed to carry the response back.

Note that the focus of FANTASTIC-5G will be the 5G air interface latency, which is the

transmission duration of a small data packet between two 5G radio nodes (terminals, base

stations, relays, sensors etc.) and which relates to the User Plane Latency described above.

KPI 3: coverage may be defined in terms of the reachable area/distance around/from the

transmitter(s) where an adequate sensitivity level is still available, in order to guarantee that

the wanted signal is received above or at least at the reference sensitivity level of the

receiver (it applies both on the uplink and on the downlink). Depending on the considered

core service, like e.g. MMC, coverage may also be defined as the Maximum Coupling Loss

(MCL) allowed both on the uplink and on the downlink (assuming the minimum), in terms

of the difference between the transmit power of the transmitter and the reference sensitivity

level of the receiver (taking into account the thermal noise density, the receiver noise figure,

the interference margin, the occupied channel bandwidth, the required SINR and the

receiver processing gain).

KPI 6: availability may be assumed to be equal to (1 – service blocking probability), where

service blocking probability is due to lack of enough resources to access, grant, and provide

the service, even in case of adequate coverage. Additionally, reliability may be assumed

equal to (1 – service dropping rate4), where service dropping may occur e.g., in case of quite

severe multiple interferers received together with the wanted signal, even in case of

adequate coverage. Depending on the considered core service, reliability may also be

defined as the probability of transferring a given payload and receiving the corresponding

acknowledgement with maximum required error rates and with a given latency requirement.

KPI 7 and 8: These two KPIs will be assessed in comparison with current standards. The

estimated complexity and energy consumption should be comparable to today’s

metropolitan deployments. Keeping the energy consumption constant while improving the

system performance implies the need for a better energy efficiency.

It is worthwhile noting that the above definitions still allow for evaluating the KPIs via

simulations carried out with the simulators made available in the framework of the project,

which is also one of the criteria highlighted in Sect 1.5 to select the use cases.

2.1.3 Requirement levels for the KPIs associated to the core services

The primary, secondary and tertiary requirement levels for the above listed KPIs are shown in

Figure 2-1for each core service.

4 Service dropping rate is linked to the degradation of the quality of service due to the erroneous reception (of

packets/frames/symbols/bits).



KPI 0 KPI 1 KPI 2 KPI 3 KPI 4 KPI 5 KPI 6 KPI 7 KPI 8

Core Service User rate Throughput Latency Coverage Mobility C.Density Rel-Avai Complex Energy

MBB

MMC

MCC

BMS

V2X

Requirem lev Primary Secondary Tertiary

Figure 2-1: Core services and related KPIs with different requirement levels

As highlighted in Sect. 1.4, the higher the relative requirement level of the corresponding KPI

on a per core service basis, the more challenging the corresponding absolute (range of) values

and consequently the requirement itself for that KPI is.

It is also worthwhile noting that the same “relative” requirement level corresponding to a given

KPI for more than one core service (e.g. KPI 3 being primary for all the 5 core services) may

still lead to quite different “absolute” (range of) values when the requirements corresponding to

that KPI apply to different use cases. For instance, in the MMC core service, the coverage KPI 3

may lead to require an “absolute” 20 dB extra-coverage in case of a specific use case (e.g. smart

meters in basements), compared to a “normal” coverage required for the other core services,

even though the same primary “relative” requirement level still applies to all. Furthermore,

sometimes, a different definition of the KPI may apply on a per core service basis, e.g. in case

of KPI 3 and MMC, as described in Sect. 2.1.2.

2.2 Composite services mapping to use cases

A composite service is a combination of two or more core services or a single core service

denoting a real-life use case.

The composite services inherit the KPIs of the core services that compose them (in case some of

the use cases may be mapped onto a single core service, the overall KPI assignment procedure

is simpler).

In this document and in the framework of the project the words “composite service” and “use

case” are used interchangeably.

The variety of possible composite services is identified and described in the following Sections,

taking into account the NGMN, 3GPP and METIS / METIS II frameworks.

Sect. 2.2.1 shows the composite services mapping to NGMN use cases.

Sect. 2.2.2 shows the composite services mapping to 3GPP SMARTER SI use cases.

Sect. 2.2.3 shows the composite services mapping to METIS and METIS II use cases.

Sect. 2.2.4 lists the use cases coming from the above 3 mappings and will be further subject to

the use case selection (in Sect. 3.1), on the basis of the criteria described in Sect. 1.5.



2.2.1 Composite services mapping to NGMN use cases5

NGMN has developed 24 Use Cases for 5G [NGM15] as representative examples, which are

grouped into 8 Use Case Families. The use cases and the use case families serve as inputs for

setting the requirements and defining the building blocks of the 5G architecture. The use cases

are not meant to be exhaustive, but rather to be treated as a tool to ensure that the level of

flexibility required in 5G is well captured. Figure 2-2 shows the 8 use case families with one

example use case given for each family.

Figure 2-2: 5G Use Case Families and related examples – NGMN Source [NGM15]6

The 5G use cases demand for very diverse and sometimes extreme requirements. It is

anticipated that a single solution to satisfy all the extreme requirements at the same time may

lead to over-specification and high cost, unless a versatile framework is offered to the network

operator as proposed by FANTASTIC-5G project. Nevertheless, several use cases are

anticipated to be active concurrently in the same operator network, thus requiring a high degree

of flexibility and scalability of the 5G network.

In order to reflect their use case dependency, the requirements are specified according to the 14

Use Case Categories defined in Figure 2-3. For each use case category, one set of requirement

values is given, which is representative of the extreme (i.e. most demanding) use cases in the

category. As a result, satisfying the requirements of a category leads to satisfying the

requirements of all the use cases in this category.

5 The text contained in this section is derived from [NGM15], sections 3.2.1 and 4. Some modifications have been

applied to adapt the text to the present paragraph and consider the correct use cases number contained in NGMN

white paper.

6 Figure 2-2: Photos: © Shutterstock.com/ Leigh Prather, Alexey Stiop, SOMMAI, Syda Productions, flydragon,

BackgroundStore, Ortodox, tovovan



Figure 2-3: Use Case Categories and Use Cases definition – NGMN Source [NGM15]

It is important to note that the NGMN requirements are based on the operators’ vision of 5G in

2020 as well as beyond 2020. As such, not all the requirements will need to be satisfied in 2020.

Nevertheless, the 5G technology baseline should be designed so that it allows all these

requirements to be satisfied at some point in or beyond 2020. The exact requirements set for the

first release of 5G (addressing deployments around 2020) will be the subject of a further

prioritization exercise for NGMN operators in close cooperation with industry.

Recall that the selection criterion 5 from Sect. 1.5 refers to the selection of uses cases collecting

more preferences among operators, e.g. because of being able to address new services and/or

markets and therefore expected to be more successful. This selection criterion is therefore in

line with the above statement coming from the NGMN Alliance.

As stated above, the KPIs and the corresponding requirements are defined per NGMN use case

category.

The NGMN KPIs are split in:

User Experience KPIs: User Experienced Data Rate (KPI 0), E2E Latency (KPI 2),

Mobility (KPI 4), Reliability/Availability (KPI 6);

System Performance KPIs: Traffic Density (KPI 1), Coverage (KPI 3), Connection

Density (KPI 5), Complexity Reduction (KPI 7), Energy Efficiency (KPI 8).

1

2

3

4

5

67

8

9

10

11

12

13

14



where the corresponding KPIs identified in FANTASTIC-5G are reported in brackets.

Table 2-1 reports the User Experience KPIs and the corresponding absolute requirements per

NGMN use case category.

Table 2-1: User Experience KPIs and Requirements – NGMN Source [NGM15]

Table 2-2 reports the System Performance KPIs and the corresponding absolute requirements

per NGMN use case category.



Table 2-2: System Performance KPIs and Requirements – NGMN Source [NGM15]

In order to achieve a composite services mapping to NGMN use cases, a viable way forward

seems to be that of defining any NGMN use case as a combination of more core services or as a

single core service denoting a real-life use case.

Table 2-3 reports the above mentioned composite services mapping to NGMN use cases, in

terms of relationship between NGMN use cases and FANTASTIC-5G core services.



Table 2-3: Relationship between NGMN use cases and FANTASTIC-5G core services

From the above table it can be seen that 20 NGMN use cases may be mapped onto a single

FANTASTIC-5G core service, whilst four NGMN use cases may be represented as a

combination of just two FANTASTIC-5G core services.

This is a quite remarkable simplification, in terms of the overall KPIs assignment and

corresponding requirements definition procedure, for any composite service corresponding to an

NGMN use case.

Moreover, the above in turn implies a further simplification in terms of the simulations to be

carried out by the simulators made available in the framework of the project, as per step 6 in the

criteria based selection process of the composite services in Sect. 1.5.

It is also worthwhile noting that all the NGMN use cases belonging to a given NGMN category

may be mapped to the same FANTASTIC-5G core service(s), with the only exception of the

“automatic traffic control/driving” use case, which is mapped to V2X besides being mapped to

MCC in the “ultra-high reliability and ultra-low latency” NGMN category.

This implies that the selection process of the composite services allows for selection of just one

NGMN use case per NGMN category, i.e. the use case that is more representative of an NGMN

use case category, as per step 4 of the selection process in Sect. 1.5.

This mapping also allows to select use cases that encompass and are more demanding than other

use cases (in terms of KPIs and corresponding requirements) composed by the same core

services, as per step 3 of the same selection process. This is quite in line with the NGMN

process, whereby for each use case category, one set of requirements values is given, which is

representative of the extreme use cases in the category.

The 24 NGMN use cases are included in the composite service list reported in Sect. 2.2.4,

encompassing also the use cases coming from mapping to 3GPP SMARTER SI use cases (Sect.

2.2.2) and the use cases coming from mapping to METIS and METIS II use cases (Sect. 2.2.3).



2.2.2 Composite services mapping to 3GPP SMARTER SI use cases

The Feasibility Study on New Services and Markets Technology Enablers (FS_SMARTER)

carried out by 3GPP SA1 aims to identify the market segments and verticals whose needs

should be met by 3GPP, and to develop the use cases and requirements that the 3GPP eco-

system would need to support in the future [SP-150142], [S1-151623].

The use cases and high level requirements in the framework of SMARTER are sourced from

existing work such as the 4G Americas’ Recommendations on 5G Requirements and Solutions

[4GA14], Chinese IMT-2020 (5G) Promotion Association’s 5G Vision and Requirements White

Paper [CPA14], ITU-R WP5D’s IMT Vision – Framework and overall objectives of the future

development of IMT for 2020 and beyond [ITU15], the 5G Forum of Korea’s 5G Vision,

Requirements, and Enabling Technologies White Paper [5GFK15] and the NGMN 5G White

Paper [NGM15].

The focus of this work is on the use cases and corresponding requirements that cannot be met

with the Evolved Packet System (EPS). This target is in line with step 1 of the selection process

of the use cases described in Sect. 1.5, whereby the selected use cases shall not be covered by

LTE and LTE-Advanced or even earlier RATs.

Taking into account the 3GPP work on 5G use cases and requirements with SMARTER also

allows for meeting step 7 of the above selection process, i.e. selecting use cases in line with the

ongoing activity in 3GPP. This is done in order to be able to contribute first to the feasibility

study and then to the normative work in 3GPP (SA as well as RAN).

Nevertheless, SMARTER also includes analysis on which legacy services and requirements

from the existing 3GPP systems need to be included and whether or not fallback mechanisms to

them need to be developed.

The expected SMARTER work flow is as follows:

Step 1: Develop several use cases covering various scenarios and identify the related high-

level potential requirements;

Step 2: Identify and group together the use cases with common characteristics;

Step 3: Select a few, e.g. 3-4, use cases (or groups of use cases with common

characteristics) for further development;

Step 4: Start new individual study items as a building block for each use case or group of

use cases identified in Step 3 to further develop the use cases and their potential

requirements, and capture the desired system requirements and capabilities that apply across

the different verticals. This is essentially a horizontal view of the potential requirements to

complement the vertical use cases;

Step 5: On completion of the study items in Step 4, review and consolidate the resulting

potential requirements from all of them, and return to Step 3 for the next Phase of

SMARTER.

It is expected to start normative work on completed study items after Step 5.

The target for Step 3 for Phase 1 is October 2015.

The target for Step 5 for Phase 1 is March 2016.

Each Phase of SMARTER needs to be compatible and consistent with the previous Phase.

So far (as of September 2015) 20 SMARTER use cases have been identified as highlighted in

Table 2-4.



Table 2-4: Relationship between SMARTER use cases and NGMN use cases

No. SMARTER use cases NGMN u.c.

1 Ultra Reliable Communications 17 - 22

2 Network Slicing -

3 Lifeline communications / natural disaster 16

4 Migration of services from earlier generations -

5 Mobile Broadband for indoor scenario 4

6 Mobile broadband for hotspots scenario: Dense Urban Area scenario 3

7 On-demand networking 5

8 Flexible application traffic routing -

9 Flexibility & Scalability -

10 Mobile broadband services with seamless wide-area coverage 2, 5 - 8

11 Virtual Presence 4

12 Connectivity for drones 22

13 Industrial Control 15, 18

14 Tactile Internet 15

15 Localized real-time control 18

16 Coexistence with legacy systems -

17 Extreme real-time communications and the tactile internet 15

18 Remote Control 19, 22

19 Light weight device configuration 13

20 Wide area sensor monitoring and event driven alarms 13 - 14

From the above table it can be seen that 15 SMARTER use cases may be addressed by the

corresponding NGMN use cases, whose numbering refers to the NGMN use cases’ list reported

in Table 2-3, starting from use case 1 (Pervasive video) up to use case 24 (Broadcast like

services: Local, Regional, National).

The remaining five SMARTER use cases (highlighted in yellow in Table 2-4.) are not covered

by any NGMN use case. Those five use cases may be characterized in two ways. On one hand,

some of them are related to the legacy services provided by earlier generations / legacy systems

(such as SMARTER use cases 4 and 16) and are therefore not considered in the framework of

FANTASTIC-5G, as per step 1 of the selection process described in Sect. 1.5. On the other

hand, some others are addressing functional characteristics of the overall air interface, such as

flexibility and scalability, network architecture (network slicing) and flexible application traffic

routing (such as SMARTER use cases 2, 8 and 9). In this way, they do not directly map to

FANTASTIC-5G composite services, but can rather be considered as being triggered by the

composite services that have otherwise been identified.



2.2.3 Composite services mapping to METIS and METIS II use cases

METIS first introduced 12 Test Cases (TC), where a test case is a practical aspect formulated

from end-users’ perspective and contains a set of assumptions, constraints and requirements.

These test cases were selected such that they essentially sample the space of future applications,

implying that some of them have applications that traditionally have not been considered within

studies of telecommunication systems (as of April 2013).

The 12 test cases are the following ones [MET13-D11]:

TC1: Virtual reality office

TC2: Dense urban information society

TC3: Shopping mall

TC4: Stadium

TC5: Teleprotection in smart grid network

TC6: Traffic jam

TC7: Blind spots

TC8: Real-time remote computing for mobile terminals

TC9: Open air festival

TC10: Emergency communications

TC11: Massive deployment of sensors and actuators

TC12: Traffic efficiency and safety

Subsequently, METIS introduced 9 use cases, that are not visible in [MET13-D11], but that still

should be highlighted due to recent technology trends and future projections (as of April 2015).

The 9 use cases are the following ones [MET15-D15]:

UC1: Gaming

UC2: Marathon

UC3: Media on demand

UC4: Unmanned aerial vehicles

UC5: Remote tactile interaction

UC6: eHealth

UC7: Ultra-low cost 5G network

UC8: Remote car sensing and control

UC9: Forest industry on remote control

As of September 2015, METIS II has set priorities7 on the above overall 21 use cases (renaming

the test cases as use cases) for TC1 (same requirements as defined in METIS), TC2 (updated

METIS requirements to ensure that indoor is included with NGMN requirements of more than

7 Priorities have been set so far (as of September 2015) by 12 METIS II partners on the ground of METIS use cases +

UC22: Orange, TI, Nokia, ITRI, UPV, DT, Huawei ERC, Ericsson, Huawei HQ, KTH, DCM, IDATE.



300 Mbps for 95% of users), TC11 (same requirements as defined in METIS) and TC12

(updated METIS requirements to ensure that low latency extends to V2I, so that solutions can

help for other uMTC8), and has introduced one more use case [MET215-R11]:

UC22: Broadband access everywhere

focusing on coverage in rural and suburban areas with NGMN requirements of 50Mbps+ in DL

and 25 Mbps+ in UL. Table 2-5 shows the relationship between METIS / METIS II use cases

and NGMN use cases.

8.uMTC (Ultra-reliable Machine-Type Communications) maps to MCC in FANTASTIC-5G.



Table 2-5: Relationship between METIS / METIS II use cases and NGMN use cases

No. METIS / METIS II use cases NGMN u.c.

1 Virtual reality office 4

2 Dense urban information society 3

3 Shopping mall 3, 5

4 Stadium 5

5 Teleprotection in smart grid network 13

6 Traffic jam 2

7 Blind spots 7

8 Real-time remote computing for mobile terminals 8, 10

9 Open air festival 5

10 Emergency communications 16

11 Massive deployment of sensors and actuators 13

12 Traffic efficiency and safety 17

13 Gaming 2, 15

14 Marathon 2, 5, 12

15 Media on demand 1, 4

16 Unmanned aerial vehicles 18, 22

17 Remote tactile interaction 15, 19, 20

18 eHealth 20

19 Ultra-low cost 5G network 7

20 Remote car sensing and control 10, 13, 17, 19

21 Forest industry on remote control 19

22 Broadband access everywhere 6

METIS II priorities

From the above table it can be seen that all the 22 METIS / METIS II use cases may be

addressed by corresponding NGMN use cases, whose numbering refers to the NGMN use case

list reported in Table 2-3, starting from 1 – Pervasive video up to 24 – Broadcast like services:

Local, Regional, National.

It is anyway worthwhile noting that the METIS II so far (as of September 2015) has set

priorities correspond to the following NGMN use cases:

NGMN UC3: Dense urban society

NGMN UC4: Smart Office

NGMN UC6: 50 Mbps everywhere

NGMN UC13: Sensor networks



NGMN UC17: Automatic traffic control / driving

2.2.4 Use cases (i.e. composite services) list coming from mapping to NGMN, 3GPP SMARTER SI, METIS and METIS II use cases

Based on the analysis performed and the outcome from Sects. 2.2.1, 2.2.2 and 2.2.3, it can be

derived that the FANTASTIC-5G use cases may be described by the 24 NGMN use cases (Sect.

2.2.1), encompassing also the use cases coming from 3GPP SMARTER SI (Sect. 2.2.2) and the

use cases coming from METIS and METIS II (Sect. 2.2.3), on the ground of the information

available as of September 2015.

Table 2-6 reports the overall potential FANTASTIC-5G use cases, as well as their mapping to

FANTASTIC-5G core services. Note that this exhaustive list will further be subject to selection

(Sect. 3.1), following the selection process described in Sect. 1.5.

We note that, the NGMN use case “Dense urban society” has been modified to “Dense urban

society below 6GHz”. This modification is justified by FANTASTIC-5G’s focus on lower

frequencies. Our analysis has showed a relevance of this use case, especially for the frequency

range between 3 and 6 GHz. One important challenge for the FANTASTIC-5G air interface will

be the boosting of capacity, and it is expected that dense urban deployments will play an

important role in achieving this goal. Therefore we have adapted this use case to the particular

focus of FANTASTIC-5G. Lower carrier frequency implies lower bandwidth and thus reduced

user experienced throughput requirements. As a consequence, we have reduced the NGMN

requirement of 300 Mbps to 50 Mbps.

Although the FANTASTIC-5G use cases are identified in this IR taking into account other

sources such as NGMN, SMARTER and METIS/METIS-II, the project will continue to monitor

these (and other) sources during the lifetime of the project and may consider additional newly

emerging use cases in case deemed important/necessary.



Table 2-6: List of the overall potential FANTASTIC-5G use cases and mapping to the FANTASTIC-5G core services9

FANTASTIC-5G Core Services

NGMN Categories FANTASTIC-5G Use Cases MBB MMC MCC BMS V2X

Broadband access in dense area

1. Pervasive video X

2. Operator cloud services X

3. Dense urban society below 6GHz X

Indoor ultra-high broadband access 4. Smart Office X

Broadband access in a crowd 5. HD video/photo sharing in stadium/open-air gathering X

50+ Mbps everywhere 6. 50 Mbps everywhere X

Ultra low-cost broadband access for low ARPU areas 7. Ultra-low cost networks X

Mobile broadband in vehicles

8. High speed train X X

9. Moving Hot Spots X X

10. Remote computing X X

Airplanes connectivity 11. 3D Connectivity: Aircrafts X

Massive low-cost/long-range/low-power MTC 12. Smart wearables (clothes) X

13. Sensor networks X

Broadband MTC 14. Mobile video surveillance X

9 The FANTASTIC-5G use cases may be described by the NGMN use cases belonging to the NGMN categories - [NGM15]



Ultra low latency 15. Tactile Internet X

Resilience and traffic surge 16. Natural disaster X

Ultra-high reliability & Ultra-low latency

17. Automatic traffic control/driving X X

18. Collaborative robots X

19. Remote object manipulation – Remote surgery X

Ultra-high availability and reliability

20. eHealth: Extreme Life Critical X

21. Public Safety X

22. 3D Connectivity: Drones X

Broadcast like services 23. News and Information X

24. Broadcast like services: Local, Regional, National X



3 Selected use cases with the associated KPIs and requirements

The list of the overall FANTASTIC-5G use cases identified in Sect. 2.2.4 needs to be reduced to

a number of selected use cases to be carefully evaluated in the framework of the project (for

instance, through system level simulations).

The selection process described in Sect. 1.5 is applied in Sect. 3.1 and leads to a selection of 7

use cases, whose requirements corresponding to the defined KPIs are specified in Sect. 3.2, in

terms of absolute (range of) values and units of measurement.

3.1 Use cases ( composite services) selection

The selection criteria applied to the use cases identified in Sect. 2.2.4 have already been detailed

in Sect. 1.5, showing the overall methodology followed in this document.

The application of the above selection criteria to the above identified use cases (referred to as

UC in the following, in conjunction with the numbering 1 - 24 reported in Table 2-6) leads to

the following subsequent steps:

Step 1: select use cases not covered by LTE and LTE-Advanced or even earlier RATs

UC23 is already covered by LTE and LTE-Advanced, based on a Single Frequency Network

(SFN) mode of operation, whilst UC24 requires high flexibility and scalability implying new

components to be included, compared to the available ones in LTE and LTE-Advanced. In fact,

as described in [NGMN2015] while personalization of communication will lead to a reducing

demand for legacy broadcast as deployed today, e.g. linear TV, the fully mobile and connected

society will nonetheless need efficient distribution of information from one source to many

destinations. These services may distribute content as done today (typically only downlink), but

also provide a feedback channel (uplink) for interactive services or acknowledgement

information. Both, real-time or non-real time services should be possible and can have a wide

distribution or focused in smaller regions.

Following this consideration, UC23 is ruled out.

Step 2: select use cases not covered by higher frequencies (e.g. above 6 GHz) RATs

In case of higher frequencies RATs (e.g. above 6 GHz), multiple RATs with potentially

different air interfaces could complement each other for providing broadband access in dense

areas. This approach allows for multiple RATs with complementing use cases, which could be

used to provide capacity and high data rates in dense urban areas, as well as indoors, to support

the mobile broadband use case categories.

Since the higher frequencies RATs are not envisaged in FANTASTIC-5G, use cases relying on

these RATs are not considered to be covered in the framework of the project. We therefore

consider the use cases addressed by lower frequencies RATs (below 6 GHz) which target to

provide broadband access in dense areas. Considering the use case “Dense urban society” as the

most representative of the category “Broadband Access in dense areas”, we have chosen to

modify it to fit to the scope of FANTASTIC-5G and define the use case “Dense urban society

below 6GHz”. As already stated above, this use case is deemed important to boost capacity in

5G and is relevant for 5G broadband services, particularly for the frequency range between 3

and 6 GHz.

Following these considerations, UC1, UC2, UC4, UC5 are ruled out.



Step 3: select use cases that encompass and are more demanding than other use cases (in

terms of KPIs and corresponding requirements) composed by the same core services

In the framework of the MBB core service, UC6 is more demanding than UC7, in terms of

almost all the KPIs (ranging from KPI 0 to KPI 6, with the only exceptions of KPI 7 and KPI 8)

and corresponding requirements. Nevertheless, since KPI7 and KPI8 are important metrics for

MNOs, we will pay special attention to those KPIs while working on UC6.

In the framework of the MBB + V2X core services, UC8 may be considered more demanding

than UC9 and UC10, in terms of at least KPI 3 and KPI 4 which are crucial KPIs in case of

vehicular applications.

From the V2X core service perspective, UC8 is more demanding than UC11 since besides KPI

3 and KPI 4 (crucial in case of vehicular applications), constraints coming from mobile

broadband applications need to be considered at the same time and may be challenged and

jeopardized by coverage and mobility.

In the framework of the MMC core service, UC13 is more demanding than UC12, in terms of

KPI 3, KPI 5, KPI 7 and KPI 8, crucial in case of massive low-cost/long-range/low-power

MTC.

In the framework of the MCC core service, UC15 is more demanding than UC14, in terms of

KPI 2, KPI 3 and KPI 6 which are crucial KPIs in case of mission critical communications.

From the MCC core service perspective, UC17 is more demanding than UC16, UC18, UC19,

UC20, UC21 and UC22 since, besides KPI 2, KPI 3 and KPI 6 (crucial in case of mission

critical communications), KPI 4 has to be taken into account at the same time and mobility

usually poses remarkable challenges on meeting requirements for coverage and

reliability/availability.

Following these considerations, UC7, UC9, UC10, UC11, UC12, UC14, UC16, UC18, UC19,

UC20, UC21, UC22 are ruled out.

Step 4: select use cases that are more representative of an NGMN use case category

The selection performed at Step 3 leads to select use cases that also meet the criterion reported

in Step 4. This allows for stating that FANTASTIC-5G use case selection is not dependent on

the NGMN use case categories, but still leads to achieve the same outcome as if the NGMN

categories had been taken into account in the overall selection process.

Step 5: select uses cases collecting more preferences among operators (e.g. because of

being able to address new services and/or markets and therefore expected to be more

successful)

The above selection steps have already led to a reduced number of selected use cases that can be

considered for evaluation in the framework of the project, without any need to further down-

select the remaining use cases.

Step 6: select use cases whereby simulations can be carried out with the simulators made

available in the framework of the project

At this stage it is considered that the use cases selected so far (UC3, UC6, UC8, UC13, UC15,

UC17, UC24) allow for carrying out simulations with the simulators made available in the

framework of the project, since the above use cases are either single core services or a

combination of just 2 core services with KPIs that can be calculated through appropriate models

within the simulators.

Step 7: select use cases in line with the ongoing activity in 3GPP (in order to be able to

contribute first to the feasibility study and then to the normative work in 3GPP)

As already highlighted in Sect. 2.2.2, the use cases considered in the 3GPP SMARTER SI can

be mapped to the above 24 use cases, with the only exception of 5 SMARTER use cases. These



use cases are not considered in the framework of FANTASTIC-5G or are not directly

identifying FANTASTIC-5G use cases, but rather being triggered by the use cases otherwise

identified.

The above implies that this step does not require for further down-selecting the remaining use

cases.

Based on the overall criteria, the resulting selected use cases for FANTASTIC-5G are UC3,

UC6, UC8, UC13, UC15, UC17, UC24 (now referred to as Use Case 1 - 7):

Use Case 1: 50 Mbps everywhere MBB

Use Case 2: High speed train MBB + V2X

Use Case 3: Sensor networks MMC

Use Case 4: Tactile Internet MCC

Use Case 5: Automatic traffic control / driving MCC + V2X

Use Case 6: Broadcast like services: Local, Regional, National BMS

Use Case 7: Dense urban society below 6GHz MBB

It is worthwhile noting that the above 7 selected use cases represent all the core services either

as a single core service (MBB, MMC, MCC, BMS) or as a combination of 2 core services (V2X

in conjunction with either MBB or MCC).

It is also important to highlight that the priorities set so far (as of September 2015) by METIS II

are mostly taken into account by the above list of FANTASTIC-5G selected use cases, in terms

of UC6, UC13, UC17. Note that UC4 cannot be taken into account, since we consider that it is a

use case typically covered (also) by higher frequencies RATs, which are not envisaged in

FANTASTIC-5G.

3.2 Overview on KPIs and corresponding requirements for all the selected use cases

For any KPI defined for each core service composing a composite service, the actual values are

dependent on the selected use case and represent a use case category requirement, as per steps 3

and 4 of the criteria based selection process described in Sect. 1.5.

The following Sects. 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6 and 3.2.7 report the following

information for the 7 selected use cases listed in Sect. 3.1:

use case description;

combination of the core services;

KPI 0 - 8 (split between User Experience KPIs and System Performance KPIs);

definition of the KPIs;

relative requirement levels (inherited by the core service(s)): primary, secondary or tertiary

as a relative importance level (referred to as Req. Lev.);

requirements definition: absolute (range of) values;

units of measurement (UoM);

notes.



3.2.1 Use case 1: 50 Mbps everywhere

Use case description:

The demand for very high data rate Internet access at any time and at any place is constantly increasing. The ubiquitous capacity demands of future users will be

challenging to satisfy in areas with sparse network infrastructure, such as scarcely populated areas, rural and even suburban areas.

While cell densification is promising for boosting the capacity in future urban environment with higher frequencies RATs, wide coverage solutions as well as

flexible, energy and cost efficient solutions must be developed in future wireless communication systems to provide ubiquitous coverage in suburban and more or

less remote rural areas.

Therefore, the seamless wide-area coverage scenario aims at providing seamless service to users.

In the mobile and connected society, the increasing need to provide access to broadband service everywhere (including the more challenging situations in terms

of coverage, from urban to suburban and rural areas) implies that a consistent user experience, with respect to throughput, needs a minimum data rate guaranteed

everywhere, with requirements of 50 Mbps in DL and 25 Mbps in UL, meant as the minimum user data rate and not a single user’s theoretical peak rate.

Furthermore, it is emphasized that this user data rate has to be consistently delivered across the coverage area, i.e. even at cell edges.

The target value of 50 Mbps everywhere is meant to be indicative, depending upon the evolution of 5G technology, which would cost-effectively support these

figures. Both infrastructural and end user energy consumption should be minimized. Network cost including infrastructural equipment, site rental, energy

consumption, and so on, is expected to be reduced by 50%.

A diversity of services should be supported, such as file downloading and video streaming.

Combination of the core services: MBB



Table 3-1: Use case 1: 50 Mbps everywhere – requirements definition

Use case 1: 50 Mbps everywhere

KPI no. KPI definition Req. Lev. Requirement definition UoM Notes

User Exp.

KPI 0

User experienced data rate

50 Mbps (DL), 25 Mbps (UL)

Mbps

From a user experience point of

view, data rate requirements are

expressed in terms of user

experienced data rate, measured in

bit/s at the application layer 10

. The

required user experienced data rate

should be available in at least 95%

of the locations (including at the

cell-edge) for at least 95% of the

time within the considered

environment.

Syst. Perf.

KPI 1

Traffic Density

Suburban : DL : 20 Gbps/km2

Suburban : UL : 10 Gbps/km2

Rural : DL : 5 Gbps/km2

Rural : UL : 2.5 Gbps/km2

Gbps/km2

Traffic density is the total expected

traffic volume per area which takes

into account both the user

experienced data rate (KPI0) and

also the connection density (KPI5).

From a user experience point of

view, latency is the End-To-End

(E2E) latency, which is defined as

the duration between the

10 However, since FANTASTIC-5G focuses on layers 1 and 2, data rates will be evaluated at the MAC layer. It is important to note that the requirement values are not the peak values, but typical

user experienced data rates which depend on factors such as the allocated bandwidth, user traffic distribution and characteristics etc. The requirement values are considered from a user experience

point of view, taking into account typical MBB applications foreseen for 5G (e.g. multimedia-type).



User Exp. KPI 2 Latency 10 ms ms transmission of a small data packet

from the application layer at the

source node and the successful

reception at the application layer at

the destination node plus the

equivalent time needed to carry the

response back (if foreseen) 11

.

Syst. Perf.

KPI 3

Coverage

99.999% of the area where the service is

provided

%

The wanted signal needs to be

received everywhere, above or at

least at the reference sensitivity

level of the receiver (it applies both

on the uplink and on the

downlink), in order to guarantee

the required minimum user data

rate.

User Exp. KPI 4 Mobility 0 - 120 km/h km/h

Syst. Perf. KPI 5 Connection density Suburban: 400 users/km

2

Rural: 100 users/km2

Users/km2

Reliability may be assumed equal

to (1–service dropping rate), where

service dropping may occur e.g. in

case of quite severe multiple

interferers received together with

the wanted signal, even in case of

adequate coverage. Depending on

the considered service, reliability

11 Since the focus/scope of FANTASTIC-5G is the air interface layers 1 and 2, air interface latency at the MAC layer will be evaluated.



User Exp. KPI 6 Reliability/availability Reliability: 95%

Availability: 99% % may be defined as the probability

of correctly transferring a given

payload and correctly receiving

ACK within a 10 ms latency.

Non availability may occur due to

lack of coverage. But this is

reflected by KPI 3. Therefore we

consider that availability may be

assumed equal to (1–service

blocking probability), where

service blocking probability is due

to lack of enough resources to

access, grant and provide the

service, even in case of adequate

coverage.

Syst. Perf. KPI 7 Complexity reduction

50% % Reduction percentage compared to

legacy networks complexity.

Syst. Perf. KPI 8 Energy efficiency

50% % Reduction percentage compared to

legacy networks energy

consumption.

Req. Lev. Primary Secondary Tertiary



3.2.2 Use case 2: High speed train


While travelling, passengers will use high quality mobile Internet for information, interaction, entertainment or work. Examples are watching a HD movie,

interacting with social clouds, gaming online, accessing company systems or having a video conference.

Moreover, the evolution of remote services allows not only the storage of data on a common entity, e.g. a server in the Internet, but also the remote execution of

applications, e.g. office applications. This means that a terminal, e.g. a netbook, can shift complex processing tasks to a remote server, whereas the terminal itself

only serves as a user interface and therefore can relieve its own local processor units. The advantage of these systems lies in the fact that remote applications and

services can easily and centrally be maintained and updated without user interaction. Moreover, the data and applications are accessible to all users regardless of

the terminal processing capabilities.

Beyond 2020 people will not only use remote services in stationary or slow-mobility scenarios, e.g. in the office, but also on-the-go at higher speeds (e.g. up to a

range of 350 - 500 km/h) such as on their way to work while using public transport or even high speed trains.

In such a case users may currently experience a limited QoS level due to failures of mobility management, insufficient antenna capabilities and the penetration

loss introduced by the train (advanced antenna systems at the roof of the train and relay nodes allow for overcoming the problems of the penetration loss). The

quality degradation becomes more severe especially in both rural and mountain areas, where the wireless infrastructure is sparsely populated and the path loss

becomes large.

This makes it very difficult to deploy real-time remote services such as data storage and processing with an acceptable QoE on trains that move at high speeds,

still providing seamless services to the users.

In order to meet the QoS and QoE demands of such services in such challenging circumstances (i.e. high speeds and sparsely deployed geographical areas), new

technology solutions must be developed (like short flexible frame numerologies, support for high Doppler in waveform design and advanced multi-cell Radio

Resource Management – RRM - solutions).

Combination of the core services: MBB + V2X



Table 3-2: Use case 2: High speed train – requirements definition

Use case 2: High speed train


User Exp.

KPI 0



Mbps

Data rate requirements are



bit/s at the application layer. The






environment.

Syst. Perf. KPI 1 Traffic density DL : 100 Gbps/km

2

UL : 50 Gbps/km2

Gbps/km2






User Exp.

KPI 2

Latency

10 ms

ms

The E2E latency is the latency

perceived by the end user and

measures the duration of the time

interval between the transmission

of a small data packet from the

application layer at the source node

and the successful reception at the

application layer at the destination

node plus the equivalent time

needed to carry the response back.



Syst. Perf.

KPI 3

Coverage


provided

%

The transmitted signal needs to be

received above or at least at the

reference sensitivity level of the

receiver (it applies both on the

uplink and on the downlink), in

order to guarantee the required

minimum user data rate.


Syst. Perf. KPI 5 Connection density 2000 users/km

2

(500 active users per train x 4 trains) Users/km

2

Source: NGMN white paper.

User Exp.

KPI 6

Reliability/availability

Reliability: 95%

Availability: 99%

%









may be defined as the probability




Availability may be assumed equal

to (1–service blocking probability),

where service blocking probability

is due to lack of enough resources

to access, grant and provide the


coverage.




- - Same complexity as of today on

both the infrastructure side and the

device side.

Syst. Perf.

KPI 8

Energy efficiency

25%

%

Reduction percentage compared to

legacy networks and devices

energy consumption.

Low-energy operation of all radio

nodes is expected due to energy

cost and EMF reasons.

Reduced battery consumption on

the device side.




3.2.3 Use case 3: Sensor networks


Small sensors and actuators may be mounted onto stationary or movable objects and enable a wide range of applications connected to monitoring, alerting or

actuating. Possible applications are

monitoring of materials, structures and critical components, such as buildings, applications connected to agriculture or accident prevention via

notification of material faults,

gas, water, energy metering for applications linked to utilities,

pollution, temperature, humidity, noise monitoring,

power failure notifications, tamper notifications, theft notification, smoke detectors, fire detectors, motion sensors and vibration sensors.

Furthermore, portable objects may be equipped with tiny tags for the purpose of tracking the location of the objects or monitoring their usage or environment.

The devices typically need only to transmit data occasionally, e.g. in the order of every minute, hour or week. However, the devices may need to be able to issue

an alert. The devices may further be used to enable remote actuating, e.g. in the context of smart cities to dynamically adapt traffic flows, access or lighting, or in

the context of connected buildings to control access, temperature, lighting.

The devices’ notifications are expected to be sent on the uplink either periodically or event-triggered or triggered by DL messages, with or without

acknowledgements on the downlink from the network, depending on the type of application.

The net payload for such applications is typically small, in the order of 20 to 125 bytes per message or even more in some special cases, and the latency

requirements are often moderate, in the range of a few seconds, leading to low throughput requirements due to sporadic small packet transmissions. These devices

need to be energy efficient, low cost, provide coverage extension and they can be used in quantities of tens of billions.

In terms of energy, they may rely either on tiny batteries (with lifetime up to 10 years) or possibly on solar energy or acceleration as an energy source (for object

tracking devices); hence the overall power dissipation has to be extremely minimized.

In terms of cost, a sensor device must have a significantly lower cost than a regular handset device, i.e. not more than a few euros for the radio part of the sensor.

In terms of coverage extension, they may require 20 dB extra-coverage compared to the coverage provided by legacy systems (but still achieved with the existing

network infrastructure), in order to cope with indoor location and deep building penetration loss (e.g. in case of placement in basements) and with packaging (e.g.

in case of metal boxes).



Combination of the core services: MMC

Table 3-3: Use case 3: Sensor networks – requirements definition

Use case 3: Sensor networks

KPI no. KPI definition Req.

Lev.

Requirement definition UoM Notes

User Exp.

KPI 0


Not critical

160 bps - 1 Mbps

(mostly UL biased)

Mbps










environment.

Syst. Perf.

KPI 1

Traffic density

Not critical

UL : 100 Mbps/km2

Mbps/km2

(Ultra-)low data rate per device,

small net payload (in the order of

20 to 125 bytes per message or

even more in some special cases)

and asynchronous devices lead to

non-critical traffic density.

User Exp.

KPI 2

Latency

Not critical

10 s

s



measures the duration between the

transmission of a small data packet








response back.

Syst. Perf.

KPI 3

Coverage

20 dB more than legacy systems

coverage (both UL and DL) with 100%

coverage as a baseline

dB

Coverage may be defined as the

Maximum Coupling Loss (MCL)

allowed both on the uplink and on

the downlink (assuming the

minimum), in terms of the

difference between the transmit

power of the transmitter and the


receiver (taking into account the

thermal noise density, the receiver

noise figure, the interference

margin, the occupied channel

bandwidth, the required SINR and

the receiver processing gain).

User Exp.

KPI 4

Mobility

Not critical (almost stationary)

95% of the devices: 0 km/h

5% of the devices: 0 - 120 km/h

km/h

The majority of the devices is

expected to be stationary. In case

of tracking purposes the mobile

speed is expected to be in the range

0 - 120 km/h.

Syst. Perf.

KPI 5

Connection density

Up to 600,000 devices / km2

Devices/km2

Around 60,000 devices / km2 are

expected to be supported by

Cellular IoT solutions currently

being standardized within 3GPP.

FANTASTIC-5G will provide 10

times to 100 times higher

connection density. In case of just

10 times, this leads to 600,000



devices / km2.

User Exp.

KPI 6


Not critical to be met due to

sporadic traffic, small payload per

message, (ultra-)low data rate per

device, asynchronous devices

Reliability: 95%

Availability: 99%

%

Reliability may be defined as the

probability of correctly transferring

a given payload and correctly

receiving ACK within the required

latency (if foreseen).







coverage.

Syst. Perf.

KPI 7

Complexity reduction

Devices: 90%

%


legacy devices complexity.

A sensor device must have a

significantly lower cost than a

regular handset device, i.e. not

more than a few euros for the radio

part of the sensor.

The infrastructure cost is expected

to be kept on the same level as

today.

Syst. Perf.

KPI 8

Energy efficiency

10-year device’s battery lifetime

years

The device’s battery lifetime is

requested to be at least 10 years

with battery capacity of 5 Watt-

hours, since it may equal the

device lifetime itself, in case of

disposable devices placed in

deeply indoor locations with e.g.

metal boxes packaging, making the



battery replacement a quite

uncomfortable and expensive

procedure.

No specific constraints for the

infrastructure.




3.2.4 Use case 4: Tactile Internet


Tactile interaction refers to a system where humans will wirelessly control real and virtual objects. Tactile interaction typically requires a tactile control signal

and audio and/or visual feedback. Tactile Internet makes the cellular network an extension of our human sensory and neural system.

One application falling into this category is the use of software running in the cloud in a way that the user, interacting with environment, does not perceive any

difference between local and remote content.

With the advent of improved tele-control techniques and assisted manipulation of objects, several industries have benefited from the possibility to perform

manipulations in remote and secure places instead of in-situ. 5G can provide reliable connectivity in ultra-low latency conditions for remote tactile interaction in

applications such as assembly lines, manufacturing environments, remote surgery, remote driving, remote flying of unmanned vehicles, remote augmented

reality, etc.

Since trying to perform these manipulations remotely can be extremely challenging, because tactile interaction is only perceived as natural when the delay

between the tactile senses and the associated result is in the ms range, then:

E2E latency should not exceed 1 ms (therefore a high responsiveness, in terms of real-time reaction, is to be expected from the radio interface as well as the

network nodes involved);

reliability is a critical factor in all cases, as performance must not be compromised irrespective of the channel conditions;

security is also important, since the connection must remain intact and secure, without the possibility for outsiders to block, modify or steal the connection

itself.

Remote tactile interaction would be essentially unidirectional and asymmetric (from the remote tactile center to the object being manipulated), but bidirectional

links can also be foreseen in cases where a strong feedback is required (e.g. by means of a high-resolution camera located next to the object) or in remote

augmented reality.

Combination of the core services: MCC



Table 3-4: Use case 4: Tactile Internet – requirements definition

Use case 4: Tactile Internet


User Exp.

KPI 0



Mbps










environment.

Syst. Perf. KPI 1 Traffic density Potentially high

Tbps/km2






User Exp.

KPI 2

Latency

≤ 1 ms

ms










response back.



Syst. Perf.

KPI 3

Coverage


provided

%

The transmitted signal needs to be







rate.


Syst. Perf. KPI 5 Connection density Not critical Users/km2

User Exp.

KPI 6


Reliability: 99.999%

Availability: 99.999%

%












ACK within at most 1 ms latency.







coverage.

Syst. Perf. KPI 7 Complexity reduction Not critical - Complexity reduction not required.



Syst. Perf. KPI 8 Energy efficiency Not critical - Energy efficiency is not required.




3.2.5 Use case 5: Automatic traffic control / driving


In the coming years advanced safety applications will appear to mitigate and avoid the road accidents, to improve traffic efficiency, and to support the mobility of

emergency vehicles.

In that respect, Cooperative Intelligent Transportation Systems (C-ITS) can address problems like traffic jams, increased travel time, fuel consumption, and

increased pollution. Cooperative active safety systems can warn drivers of dangerous situations and even intervene through automatic braking or steering helping

the driver to avoid an accident.

Cooperative driving applications, such as platooning (road trains) and highly automated driving car can reduce travel time, fuel consumption, and CO2 emissions

and also increase road safety and traffic efficiency. In a platoon, vehicles drive close to each other, with an inter-vehicle distance of 3 to 5 meters, in an

autonomous manner. In particular, the lateral and longitudinal position of a vehicle in a platoon is controlled by collecting information about the state of other

vehicles (e.g. position, velocity and acceleration) through communications. Such a cooperative automation system requires high reliable communication and the

capability for vehicles to receive and process co-operative awareness messages with other involved vehicles within very short delays (in the order of 1 ms).

Information exchange among vehicles will enable the provision of safety hints to the driver or warnings about the road status, e.g. constructions, weather

conditions, and road hazards.

Moreover, not only cooperation between vehicles or between vehicles and infrastructure is required, but also the cooperation between vehicles and vulnerable

road users (VRUs), e.g. pedestrians and cyclists (V2P), through their mobile devices, such as smartphone and tablets, will be an important key element to

improve traffic safety (whereby dangerous situation with VRUs can be avoided by means of Vehicular-to-Device (V2D) communications).

C-ITS systems rely on timely and reliable exchange of information. Common to most applications are real-time requirements and strict requirements on reliability

and availability, especially when considering high mobility and large message sizes.

In D2D communications the support of ultra-reliable and low latency communications, while leveraging the varying degrees of network assistance, is introduced

in localized scenarios with focus on public security, emergency and vehicular communications; D2D group call communications, where any member of a

multicast group may be at the same time the transmitter and the receiver of information, lead to a “many-to-many” mode, besides the well known “one-to-many”

Combination of the core services: MCC + V2X



Table 3-5: Use case 5: Automatic traffic control / driving – requirements definition

Use case 5: Automatic traffic control / driving

KPI no. KPI definition Req.

Lev.

Requirement definition UoM Notes

User Exp.

KPI 0


DL: 50 kbps - 10 Mbps

UL: ~ 50 bps - 10 Mbps

Mbps










environment.

Syst. Perf. KPI 1 Traffic density DL: 30 Gbps/km

2

UL: 30 Gbps/km2

Gbps/km2

Considered the worst case of

Connection density for Traffic

density computation

User Exp.

KPI 2

Latency

1 ms-10ms

ms










response back.

1ms latency is required for



cooperative maneuver planning,

which cannot be covered by

802.11p but there are scenarios

where 50ms is sufficient, for

example intersection collision

warning.

In D2D communications the

support of low latency

communications, while leveraging

the varying degrees of network

assistance, is introduced in

localized scenarios with focus on

public security, emergency and

vehicular communications

Syst. Perf.

KPI 3

Coverage


provided

%

The wanted signal needs to be







rate. Out of coverage scenarios can

be considered as well for some

applications.

User Exp.

KPI 4

Mobility

Highway: 250 (abs.) - (500) (rel.) km/h

Rural: 120 (abs.) - 240 (rel.) km/h

Urban: 60 (abs.) - 120 (rel.) km/h

VRUs: 3 - 30 km/h

km/h

Abs. : absolute speed.

Rel. : relative speed between the

vehicles.

VRUs : Vulnerable Road Users:

3 km/h : pedestrian

30 km/h: bicycle



Syst. Perf. KPI 5 Connection density Urban: 3000 devices/km²

Suburban: 2000 devices/km²

Rural: 1000 devices/km²

Devices/km2 Three different values are

considered for different scenarios,

based on EAB members input.

User Exp.

KPI 6


Reliability: 99.999%


%












ACK within the required latency.

In D2D communications the

support of ultra-reliable

communications, while leveraging

the varying degrees of network

assistance, is introduced in

localized scenarios with focus on

public security, emergency and

vehicular communications.







coverage.



Syst. Perf.

KPI 7

Complexity reduction

-

-

The cost of V2X infrastructure

should not exceed the cost of

traditional cellular modems.

The cost of V2X devices/chipsets

should not exceed the cost of

traditional terminals/chipsets.

Syst. Perf.

KPI 8

Energy efficiency

25%

%



energy consumption.




Energy consumption needs to be

minimized and to not exceed that

of conventional non-V2X devices,

since V2X devices mainly depend

on battery power supply.




3.2.6 Use case 6: Broadcast like services: Local, Regional, National


While personalization of communication leads to a reduced demand for legacy broadcast as deployed today, e.g. TV, the fully mobile and connected society will

nonetheless need efficient distribution of information from one source to many destinations. These services may distribute contents as done today (typically only

downlink), but also provide a feedback channel (uplink) for interactive services or acknowledgement information. Both real-time and non-real time services are

possible. Furthermore, such services are well suited to accommodate the needs of vertical industries. These services are characterized by having a wide

distribution which can be either geo-location focused or address-space focused (many end-users).

Local services will be active at a cell (compound) level with a reach of for example 1 to 20 km. Typical scenarios include stadium services, advertisements,

voucher delivery, festivals, fairs, and congress/convention. Local emergency services can exploit such capabilities to search for missing people or in the

prevention or response to crime (e.g. theft).

Broadcast-like services with a regional reach will be required, for example within 1 to 100 km. A typical scenario includes communication of traffic jam

information. Regional emergency warnings can include disaster warnings. Unlike the legacy broadcast service, the feedback channel can be used to track delivery

of the warning message to all or selected parties.

National or even continental/world-reach services are interesting as a substitute or complementary to broadcast services for radio or television. Also vertical

industries will benefit from national broadcast like services to upgrade/distribution of firmware. The automotive industry may leverage the acknowledgement

broadcast capability to mitigate the need for recall campaigns. This requires software patches to be delivered in large scale and successful updates to be

confirmed and documented via the feedback channel.

The demand for the delivery of video content over cellular networks is rapidly increasing and is seen as one of the most data-hungry services in future networks.

It is therefore foreseen a very significant amount of shared content in 5G networks. Since the wireless medium is by nature a shared one, its full potential can only

be exploited by incorporating broadcast and multicast mechanisms at the PHY layer of the air interface.

Combination of the core services: BMS



Table 3-6: Use case 6: Broadcast like services: Local, Regional, National – requirements definition

Use case 6: Broadcast like services: Local, Regional, National


User Exp.

KPI 0


200 Mbps (DL), 0.5 Mbps (UL)

Mbps










environment.

Syst. Perf.

KPI 1

Traffic density

DL : 200 Mbps

UL : 0.5 Mbps

Mbps

The data throughput corresponds to

the user experienced data rate,

since it is independent from the

connection density in a given area,

due to the usage of shared

resources.

User Exp.

KPI 2

Latency

< 100 ms

ms






source node (e.g. BMSC) and the

successful reception at the

application layer at the destination

node (e.g. user’s device display)

plus the equivalent time needed to



carry the feedback / ACK back (if

foreseen).

Syst. Perf.

KPI 3

Coverage


provided

%

Everywhere the wanted signal

needs to be received above or at


level of the receiver (it applies

above all on the downlink and,

whenever a feedback / ACK is

foreseen, also on the uplink), in



User Exp.

KPI 4

Mobility

Not critical (majority is stationary)

65% of the devices: 0 km/h



km/h

The majority of the devices (65%)

is expected to be stationary. The

remaining 35% is expected to

experience a mobile speed in the

range 0 - 120 km/h (aboard cars –

30%) or in the range 0 - 500 km/h

(on trains – 5%).

Syst. Perf.

KPI 5

Connection density

Broadcast service: Not critical

Multicast service: It depends on the

technology, in order to select the

connection density to be used as a

threshold above which to establish an

MBMS session and under which to

establish p2p connections

devices

The number of users potentially

involved in a multicast MBMS

session is expected to be important

and a devices’ counting procedure

is therefore useful before starting

the MBMS session, in order to

decide whether and which type of

radio resources to allocate for that

session in case of multicast mode

(i.e. either p2p or p2m connection).

In the framework of a broadcast

“one-to-many” service, reliability



User Exp.

KPI 6


Reliability: Not critical (for a broadcast

“one-to-many” service)


%

is not requested and therefore is

not critical, since there is not any

possibility to guarantee reliability

of a specific connection between

the transmitter (e.g. BMSC) and a

single receiver (e.g. user’s device).




is expected to be equal to 0, due to

the usage of shared resources,

expected to be always available.


- - Same complexity as of today on

both the infrastructure side and the

device side.

Syst. Perf.

KPI 8

Energy efficiency

25%

%



energy consumption.




Reduced battery consumption on

the device side.




3.2.7 Use case 7: Dense urban society below 6GHz


This use case focuses on urban outdoor (e.g. including streets, urban roads etc.) and indoor (e.g., including shopping malls, train stations etc.) environments

where a lot of users gather per km2. Such a use case would be needed to satisfy demanding requirements for the provisioning of applications such as multimedia

streaming with high demand in terms of traffic. In order to meet the 5G requirements, as listed in Table 3-7, resource utilization needs to be significantly

improved due to bandwidth limitations below 6 GHz. This can be realized by e.g. introducing massive MIMO, small-cells and non-orthogonal access. This

extreme resource reuse requires an increased level of coordination and effective interference management in order to improve the overall network efficiency.

Additionally, integration of moving users/devices (slow-to-moderate vehicle speeds), i.e. public transport or cars, needs to be supported.

In this use case, primary KPIs are user experienced data rate; traffic density; latency; coverage and mobility. Secondary KPIs are the connection density,

reliability/availability; complexity reduction; energy efficiency. Note that although the connection density is a tertiary KPI for the MBB core service (and that the

use cases inherit the relative requirement levels from the core services that compose them), it is considered as a secondary KPI for this use case. This exception is

due to the obvious challenge in terms of the high traffic demand in a dense urban scenario, which translates into a high number of connection requests.

It should also be noted that due to the scope of FANTASTIC-5G, this use case focuses explicitly on bands below 6GHz.

Combination of the core services: MBB

Table 3-7: Use case 7: Dense urban society below 6GHz

Use case 7: Dense urban society below 6GHz


User Exp. KPI 0 User experienced data rate

50 Mbps (DL), 25 Mbps (UL) Mbps Following METIS (defined for



outdoor, see D1.1)










environment.

Syst. Perf. KPI 1 Traffic density

125 [Gbps/ km2] (DL)

62.5 Gbps/km2 Mbps/km

2

From NGMN white paper,

“Broadband access in dense

areas”)

User Exp. KPI 2 Latency

10ms ms The E2E latency is the latency









response back.

Syst. Perf. KPI 3 Coverage


provided

% The wanted signal needs to be

received above or at least at the


receiver (it applies both on the

uplink and on the downlink), in





User Exp. KPI 4 Mobility On demand, 0-100 km/h

km/h

From NGMN white paper,

“Broadband access in dense

areas”)

Syst. Perf. KPI 5 Connection density 200-2500/km

2

users/km2

Total device density is

2000~25,000 / km2, a 10% activity

factor is assumed (cf. NGMN

white paper)

User Exp. KPI 6 Reliability/availability 95% % Following METIS (defined for

outdoor, see D1.1)



















coverage.




Comparable to today -

Syst. Perf. KPI 8 Energy efficiency The network energy consumption should

be comparable to the energy

consumption of today’s metropolitan

deployments, despite the drastically

increased amount of traffic.

% Following METIS (defined for

outdoor, see D1.1)




4 Conclusions

The outcome of this document is a list of 7 selected use cases resulting from a selection process

based on an agreed set of criteria.

For any of the selected use cases, the KPIs and corresponding requirements are defined.

The selected use cases encompass the overall (combination of) core services on the ground of

the above mentioned criteria and are therefore expected to provide guidelines to all work

packages using IR2.1 as a reference for their activities.

Specifically, for any of the 7 selected use cases the following information has been provided:

use case description;

combination of the core services;

KPI 0 - 8 (split between User Experience KPIs and System Performance KPIs);

definition of the KPIs;

relative requirements levels (inherited by the core service(s)): primary, secondary or tertiary

as a relative importance;

requirements definition: absolute (range of) values;

units of measurement;

notes.

It is then considered that the selected use cases allow for carrying out simulations with the

simulators made available in the framework of the project, since the above use cases are based

on either single core service or a combination of just 2 core services.

It is worthwhile noting that the 7 selected use cases represent all the core services either as a

single core service (MBB, MMC, MCC, BMS) or as a combination of 2 core services (V2X in

conjunction with either MBB or MCC).

As a final note, the priorities set as of September 2015 by METIS II are taken into account by

the list of the selected use cases, in terms of an air interface below 6 GHz such as envisaged in

the framework of FANTASTIC-5G. It is important to underline that the requirements presented

in this document are high-level requirements, which will be refined in line with the definition of

the deployment scenarios where our proposed technology components will be evaluated through

simulations. It should also be kept in mind that the effective values of 5G requirements will be

determined by ITU in the IMT 2020 framework.



5 References

[22.368] 3GPP TS 22.368, “Service requirements for Machine-Type Communications

(MTC); Stage 1 (Release 13)”, December 2014

[23.888] 3GPP TR 23.888, “System improvements for Machine-Type

Communications (MTC) (Release 11)”, September 2012

[36.888] 3GPP TR 36.888, “Study on provision of low-cost Machine-Type

Communications (MTC) User Equipments (UEs) based on LTE (Release

12)”, June 2013

[45.820] 3GPP TR 45.820, “Cellular System Support for Ultra Low Complexity and

Low Throughput Internet of Things (Release 13)”, June 2015

[4GA14] 4G Americas, “4G Americas' Recommendations on 5G Requirements and

Solutions”, October 2014

[5GFK15] 5G Forum of Korea, “5G Vision, Requirements, and Enabling Technologies

White Paper”, March 2015

[5GP15] 5G-PPP (Infrastructure Association), "5G Vision", February 2015

[ARI14] ARIB 2020 and Beyond Ad Hoc Group (ADWICS), “Mobile

Communications Systems for 2020 and beyond” White Paper, version 1.0.0

October 8, 2014

[CPA14] Chinese IMT-2020 (5G) Promotion Association, “5G Vision and

Requirements White Paper", May 2014

[GP-150354] 3GPP TSG GERAN: Study Item – GP-150354, " Cellular System Support

for Ultra Low Complexity and Low Throughput Internet of Things",

FS_IoT_LC

[GSM14] GSMA, “Understanding 5G: perspectives on future technological

advancements in mobile”, December 2014

[ITU15] ITU-R WP5D, IMT Vision – “Framework and overall objectives of the

future development of IMT for 2020 and beyond”

[MET13-D11] METIS, Deliverable D1.1 “Scenarios, requirements and KPIs for 5G mobile

and wireless system”, April 2013

[MET15-D15] METIS, Deliverable D1.5 “Updated scenarios, requirements and KPIs for

5G mobile and wireless system with recommendations for future

investigations”, April 2015

[METIS15-D65] METIS Deliverable 6.5. “Report on simulation results and evaluations”

[MET215-R11] METIS II, Report R1.1 “Scenarios, Requirements, Test Cases”, September

2015

[NGM15] NGMN Alliance, “NGMN 5G White Paper” - v1.0, 17th February, 2015

[RP-141660] 3GPP TSG RAN: Work Item – RP-141660, "Further LTE Physical Layer

Enhancements for MTC"

[RP-151109] 3GPP TSG RAN: Study Item – RP-151109, “Feasibility Study on LTE-

based V2X Services”

[S1-151623] 3GPP TSG SA1: S1-151623, 3GPP TR 22.891 v0.1.1 – “Feasibility Study

on New Services and Markets Technology Enablers; Stage 1 (Release 14)”

[SP-150142] 3GPP TSG SA: Study Item – SP-150142, “Study on New Services and

Markets Technology Enablers (SMARTER)”

flexible air interface for scalable service delivery...

Documents