ETSI TS 122 104 V16.5.0 (2020-09)

5G; Service requirements for cyber-physical control applications in vertical domains (3GPP TS 22.104 version 16.5.0 Release 16)

DTS/TSGS-0122104vg50

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 14-Sep-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
Service requirements for cyber-physical control applications in
vertical domains
(3GPP TS 22.104 version 16.5.0 Release 16)

3GPP TS 22.104 version 16.5.0 Release 16 1 ETSI TS 122 104 V16.5.0 (2020-09)

Reference
DTS/TSGS-0122104vg50
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

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

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 2 ETSI TS 122 104 V16.5.0 (2020-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 3 ETSI TS 122 104 V16.5.0 (2020-09)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Overview . 9
4.1 Introduction . 9
4.2 Activity patterns in automation . 10
4.3 Communication attributes . 10
4.4 Control systems and related communication patterns . 10
4.5 Implications for 5G systems . 11
5 Performance requirements . 11
5.1 Overview . 11
5.2 Periodic deterministic communication . 12
5.3 Aperiodic deterministic communication . 15
5.4 Non-deterministic communication . 16
5.5 Mixed traffic . 17
5.6 Clock synchronisation requirements . 18
5.6.0 Description . 18
5.6.1 Clock synchronisation service level requirements . 18
5.6.2 Clock synchronisation service performance requirements . 19
5.7 Positioning performance requirements . 19
6 Ethernet applications . 20
Annex A (informative): Summary of service performance requirements . 22
A.1 About the vertical domains addressed in this Annex . 22
A.2 Factories of the Future . 22
A.2.1 Overview . 22
A.2.2 Factory automation . 23
A.2.2.1 Motion control . 23
A.2.2.2 Control-to-control communication . 25
A.2.2.3 Mobile robots . 25
A.2.3 Process automation . 27
A.2.3.1 Closed-loop control. 27
A.2.3.2 Process monitoring . 27
A.2.3.3 Plant asset management . 28
A.2.4 Human machine interfaces . 29
A.2.4.1 Mobile control panels . 29
A.2.4.2 Augmented reality . 31
A.2.5 Monitoring and maintenance . 31
A.2.5.1 Remote access and maintenance . 31
A.3 (void) . 33
A.4 Electric-power distribution . 33
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 4 ETSI TS 122 104 V16.5.0 (2020-09)
A.4.1 Overview . 33
A.4.2 Primary frequency control . 33
A.4.3 Distributed voltage control . 34
A.4.4 Distributed automated switching for isolation and service restoration . 34
A.4.5 Smart grid millisecond-level precise load control . 36
A.5 Central power generation . 37
A.5.1 Overview . 37
A.5.2 Wind power plant network . 37
Annex B (informative): Communication service errors . 38
B.1 Introduction . 38
B.2 Corruption . 38
B.3 Unintended repetition . 38
B.4 Incorrect sequence . 38
B.5 Loss . 39
B.6 Unacceptable deviation from target end-to-end latency . 39
B.7 Masquerade . 39
B.8 Insertion . 39
B.9 Addressing . 39
Annex C (informative): Characterising communication services . 40
C.1 Modelling of communication in automation . 40
C.1.1 Area of consideration . 40
C.1.2 Logical link . 41
C.1.2.1 Nature and function . 41
C.1.2.2 Message transformation . 42
C.1.2.3 Communication device . 42
C.1.2.4 Communication system . 42
C.2 Communication service description . 43
C.2.1 Overview . 43
C.2.2 Characteristic parameters . 43
C.2.3 Influence quantities . 45
C.3 Up time and up state vs. down state and down time . 46
C.4 Timeliness as an attribute for timing accuracy . 47
C.4.1 Overview . 47
C.4.2 Network latency requirement formulated by use of timeliness . 48
C.4.3 Timeliness . 48
C.4.4 Deviation . 48
C.4.5 Earliness . 49
C.4.6 Lateness . 50
C.4.7 Conclusion . 50
C.5 Communication service terminology w.r.t. 5G network and vertical applications . 50
Annex D (informative): 5G in industrial automation: different and multiple time domains for
synchronization . 53
D.1 Description . 53
D.2 Merging of working clock domains . 54
D.3 Time synchronization with 5G networks . 55
Annex E (informative): Change history . 56
History . 57

ETSI
3GPP TS 22.104 version 16.5.0 Release 16 5 ETSI TS 122 104 V16.5.0 (2020-09)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document addresses a challenging class of vertical applications, namely cyber-physical control applications,
which require very high levels of communication service availability, and some of them also require very low end-to-
end latencies.
Real-time Ethernet is one of the established wireline communication technologies for cyber-physical control
applications, and this specification identifies requirements that 5G systems must meet to support real-time Ethernet.
The present document provides new Stage 1 requirements based on the input from relevant stakeholders of the
respective vertical domains.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 6 ETSI TS 122 104 V16.5.0 (2020-09)
1 Scope
The present document provides Stage 1 normative service requirements for 5G systems, in particular service
requirements for cyber-physical control applications in vertical domains. In the context of the present document, cyber-
physical systems are to be understood as systems that include engineered, interacting networks of physical and
computational components; control applications are to be understood as applications that control physical processes.
Communication services supporting cyber-physical control applications need to be ultra-reliable and, in some cases, the
end-to-end latency must be very low. Communication for cyber-physical control applications supports operation in
various vertical domains, for instance industrial automation and energy automation.
The aspects addressed in the present document include:
- end-to-end service performance requirements and network performance requirements related to these end-to-end
service performance requirements;
- support for LAN-type services specific to industrial/high performance use cases. Related Ethernet functionalities
include, for example, those in IEEE 802.1Qbv.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system".
[3] IEC 61784-3: "Industrial communication networks – profiles – part 3: functional fieldbuses –
general rules and profile definitions".
[4] BZKI, "Aspects of dependability assessment in ZDKI", June 2017.
[5] BZKI, "Requirement Profiles in ZDKI", 2017.
[6] IEC 61158: "Industrial communication networks – fieldbus specification", 2014.
[7] IEC 61907, "Communication network dependability engineering".
[8] Richard C. Dorf and Robert H. Bishop, "Modern Control Systems", Pearson, Harlow, 13th
Edition, 2017.
[9] Ernie Hayden, Michael Assante, and Tim Conway, "An Abbreviated History of Automation &
Industrial Controls Systems and Cybersecurity", SANS Institute, https://ics.sans.org/media/An-
Abbreviated-History-of-Automation-and-ICS-Cybersecurity.pdf {accessed: 2017-05-23}, 2014.
[10] IEC 61512 "Batch control - Part 1: Models and terminology".
[11] RESERVE project, Deliverable D1.3, ICT Requirements,
http://www.re-serve.eu/files/reserve/Content/Deliverables/D1.3.pdf, September 2017.
[12] RESERVE project, Deliverable D1.2, Energy System Requirements
http://www.re-serve.eu/files/reserve/Content/Deliverables/D1.2.pdf, September 2017.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 7 ETSI TS 122 104 V16.5.0 (2020-09)
[13] G. Garner, "Designing Last Mile Communications Infrastructures for Intelligent Utility Networks
(Smart Grids)", IBM Australia Limited, 2010.
[14] B. Al-Omar, B., A. R. Al-Ali, R. Ahmed, and T. Landolsi, "Role of Information and
Communication Technologies in the Smart Grid", Journal of Emerging Trends in Computing and
Information Sciences, Vol. 3, pp. 707-716, 2015.
[15] H. Kagermann, W. Wahlster, and J. Helbig, "Recommendations for implementing the strategic
initiative INDUSTRIE 4.0", Final report of the Industrie 4.0 working group, acatech – National
Academy of Science and Engineering, Munich, April 2013.
[16] IEC 62443-3-2: "Security for industrial automation and control systems - Part 3-2: Security risk
assessment and system design", in progress.
[17] IEC 62657-2: "Industrial communication networks - Wireless communication networks - Part 2:
Coexistence management", 2017.
[18] IEC 62657-1: "Industrial communication networks – Wireless communication networks – Part 1:
Wireless communication requirements and spectrum considerations".
[19] IEEE Std 802.1Q "Media Access Control (MAC) Bridges and Virtual Bridge Local Area
Networks".
NOTE: IEEE Std 802.1Qbv-2015 "Enhancements for Scheduled Traffic" has been included into
IEEE Std 802.1Q-2018.
[20] IEEE, Use Cases IEC/IEEE 60802, 2018.
[21] "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-
Sensitive Applications in Bridged Local Area Networks--Corrigendum 1: Technical and Editorial
Corrections," IEEE Std 802.1AS-2011/Cor 1-2013 (Corrigendum to IEEE Std 802.1AS-2011), pp.
1-128, Sept 2013.
[22] "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-
Sensitive Applications," IEEE Std 802.1AS-Rev/D7.3, pp. 1-502, August 2018.
[23] 3GPP TS 22.289: "Mobile Communication System for Railways".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
characteristic parameter: numerical value that can be used for characterising the dynamic behaviour of
communication functionality from an application point of view.
clock synchronicity: the maximum allowed time offset within a synchronisation domain between the sync master and
any sync device .
NOTE 1: Clock synchronicity (or synchronicity) is used as KPI of clock synchronisation services.
NOTE 1A: Clock synchronicity is also referred to as clock (or time) synchronization precision.
clock synchronisation service: the service to align otherwise independent user-specific UE clocks.
communication service availability: percentage value of the amount of time the end-to-end communication service is
delivered according to an agreed QoS, divided by the amount of time the system is expected to deliver the end-to-end
service according to the specification in a specific area.
NOTE 2: The end point in "end-to-end" is assumed to be the communication service interface.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 8 ETSI TS 122 104 V16.5.0 (2020-09)
NOTE 3: The communication service is considered unavailable if it does not meet the pertinent QoS requirements.
If availability is one of these requirements, the following rule applies: the system is considered
unavailable if an expected message is not received within a specified time, which, at minimum, is the sum
of maximum allowed end-to-end latency and survival time.
NOTE 4: This definition was taken from TS 22.261 [2].
communication service reliability: ability of the communication service to perform as required for a given time
interval, under given conditions.
NOTE 5: Given conditions would include aspects that affect reliability, such as: mode of operation, stress levels,
and environmental conditions.
NOTE 6: Reliability may be quantified using appropriate measures such as mean time between failures, or the
probability of no failure within a specified period of time.
NOTE 7: This definition is based on IEC 61907 [7].
end-to-end latency: the time that takes to transfer a given piece of information from a source to a destination, measured
at the communication interface, from the moment it is transmitted by the source to the moment it is successfully
received at the destination.
NOTE 8: This definition was taken from TS 22.261 [2].
error: discrepancy between a computed, observed or measured value or condition and the true, specified or
theoretically correct value or condition.
NOTE 9: taken from IEC 61784-3 [3].
factory automation: automation application in industrial automation branches typically with discrete characteristics of
the application to be automated with specific requirements for determinism, low latency, reliability, redundancy, cyber
security, and functional safety.
NOTE 10: Low latency typically means below 10 ms delivery time.
NOTE 11: This definition is taken from IEC 62657-1 [18].
global clock: a user-specific synchronization clock set to a reference timescale such as the International Atomic Time.
influence quantity: quantity not essential for the performance of an item but affecting its performance.
process automation: automation application in industrial automation branches typically with continuous characteristics
of the application to be automated with specific requirements for determinism, reliability, redundancy, cyber security,
and functional safety.
NOTE 12: This definition is taken from IEC 62657-1 [18].
service area: geographic region where a 3GPP communication service is accessible.
NOTE 13: The service area can be indoors.
NOTE 14: For some deployments, e.g., in process industry, the vertical dimension of the service area can be
considerable.
NOTE 15: This definition was taken from TS 22.261 [2].
survival time: the time that an application consuming a communication service may continue without an anticipated
message.
sync device: device that synchronizes itself to the master clock of the synchronization domain.
sync master: device serving as the master clock of the synchronization domain.
transfer interval: time difference between two consecutive transfers of application data from an application via the
service interface to 3GPP system.
NOTE 16: This definition is based on subclause 3.1.85 in IEC 62657-2 [17].
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 9 ETSI TS 122 104 V16.5.0 (2020-09)
user experienced data rate: the minimum data rate required to achieve a sufficient quality experience, with the
exception of scenario for broadcast like services where the given value is the maximum that is needed.
NOTE 17: This definition was taken from TS 22.261 [2].
vertical domain: an industry or group of enterprises in which similar products or services are developed, produced, and
provided.
working clock: a user-specific synchronization clock for a localized set of UEs collaborating on a specific task or work
function.
3.2 Symbols
For the purposes of the present document, the following symbols apply:

3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
CSIF Communication Service Interface
EPON Ethernet Passive Optical Network
FIFO First In, First Out
GOOSE Generic Object-Oriented Substation Event
HCL Higher Communication Layer
HMI Human Machine Interface
IMU Inertial Measurement Unit
LCL Lower Communication Layer
PMU Phasor Measurement Unit
4 Overview
4.1 Introduction
For the purpose of this document, a vertical domain is a particular industry or group of enterprises in which similar
products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or
systems in vertical domains by automatic means. The main control functions of automated control systems include
taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to
avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.
In the context of this document, cyber-physical systems are referred to as systems that include engineered, interacting
networks of physical and computational components. Cyber-physical control applications are to be understood as
applications that control physical processes. Cyber-physical control applications in automation follow certain activity
patterns, which are open-loop control, closed-loop control, sequence control, and batch control (see Clause 4.2).
Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a
high communication service availability, and often require low or (in some cases) very low end-to-end latency.
Communication in automation in vertical domains follows certain communication patterns. The most well-known is
periodic deterministic communication, others are aperiodic deterministic communication and non-deterministic
communication (see Clause 4.3).
Communication for cyber-physical control applications supports operation in various vertical domains, for instance
industrial automation and energy automation. This document addresses service requirements for cyber-physical control
applications and supporting communication services from the vertical domains of factories of the future (smart
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 10 ETSI TS 122 104 V16.5.0 (2020-09)
manufacturing), electric power distribution, and central power generation. Service requirements for cyber-physical
control applications and supporting communication services for rail-bound mass transit are addressed in TS 22.289 [23].
4.2 Activity patterns in automation
Open-loop control: The salient aspect of open-loop control is the lack of feedback from the output to the control; when
providing commands to an actuator, it is assumed that the output of the influenced process is predetermined and within
an acceptable range. This kind of control loop works if the influences of the environment on process and actuator are
negligible. Also, this kind of control is applied in case unwanted output can be tolerated [8].
Closed-loop control: Closed-loop control enables the manipulation of processes even if the environment influences the
process or the performance of the actuator changes over time. This type of control is realised by sensing the process
output and by feeding these measurements back into a controller [8].
Sequence control: Sequence control may either step through a fixed sequence or employ logic that performs different
actions based on various system states and system input [8]. Sequence control can be seen as an extension of both open-
loop and closed-loop control, but instead of achieving only one output instance, an entire sequence of output instances
can be produced [9].
Batch control: Batch processes lead to the production of finite quantities of material (batches) by subjecting input
materials to a defined order of processing actions by use of one or more pieces of equipment [10].
4.3 Communication attributes
Communication in automation can be characterised by two main attributes: periodicity and determinism.
Periodicity means that a transmission interval is repeated. For example, a transmission occurs every 15 ms. Reasons for
a periodical transmission can be the periodic update of a position or the repeated monitoring of a characteristic
parameter. Most periodic intervals in communication for automation are rather short. The transmission is started once
and continuous unless a stop command is provided.
An aperiodic transmission is, for example, a transmission which is triggered instantaneously by an event, i.e., events are
the trigger of the transmission. Events are defined by the control system or by the user. Example events are:
- Process events: events that come from the process when thresholds are exceeded or fallen below, e.g.,
temperature, pressure, level, etc.
- Diagnostic events: events that indicate malfunctions of an automation device or module, e.g., power supply
defective; short circuit; too high temperature; etc.
- Maintenance events: events based on information that indicates necessary maintenance work to prevent the
failure of an automation device.
Most events, and especially alarms, are confirmed. In this context, alarms are messages that inform a controller or
operator that an event has occurred, e.g., an equipment malfunction, process deviation, or other abnormal condition
requiring a response. The receipt of the alarm is acknowledged usually within a short time period by the application that
received the alarm. If no acknowledgment is received from the target application after a preset time, the so-called
monitoring time, the alarm is sent again after a preset time or some failure response action is started.
Determinism refers to whether the delay between transmission of a message and receipt of the message at the
destination address is stable (within bounds). Usually, communication is called deterministic if it is bounded by a given
threshold for the latency/transmission time. In case of a periodic transmission, the variation of the interval is bounded.
4.4 Control systems and related communication patterns
There are preferences in the mapping between the type of control and the communication pattern. Open-loop control is
characterised by one or many messages sent to an actuator. These can be sent in a periodic or an aperiodic pattern.
However, the communication means used need to be deterministic since typically an activity response from the receiver
and/or the receiving application is expected.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 11 ETSI TS 122 104 V16.5.0 (2020-09)
Closed-loop control produces both periodic and aperiodic communication patterns. Closed-loop control is often used for
the control of continuous processes with tight time-control limits, e.g., the control of a printing press. In this case, one
typically relies on periodic communication patterns. Note that in both the aperiodic and periodic case, the
communication needs to be deterministic.
Logging of device states, measurements, etc. for maintenance purposes and such typically entails aperiodic
communication patterns. In case the transmitted logging information can be time-stamped by the respective function,
determinism is often not mandatory.
In practice, vertical communication networks serve a large number of applications exhibiting a wide range of
communication requirements. In order to facilitate efficient modelling of the communication network during
engineering and for reducing the complexity of network optimisation, traffic classes or communication patterns have
been identified [6]. There are three typical traffic classes or communication patterns in industrial environments [6], i.e.,
- deterministic periodic communication: periodic communication with stringent requirements on timeliness of the
transmission.
- deterministic aperiodic communication: communication without a preset sending time. Typical activity patterns
for which this kind of communication is suitable are event-driven actions.
- non-deterministic communication: subsumes all other types of traffic, including periodic non-real time and
aperiodic non-real time traffic. Periodicity is irrelevant in case the communication is not time-critical.
Some communication services exhibit traffic patterns that cannot be assigned to one of the above communication
patterns exclusively (mixed traffic).
4.5 Implications for 5G systems
In order to be suitable for automation in vertical domains, 5G systems need to be dependable and flexible to meet
specific KPIs to serve specific applications and use cases. They need to come with the system properties of reliability,
availability, maintainability, safety, and integrity. What particular requirements each property needs to meet depends on
the particularities of the domain and the use case. The requirements in this document provide various sets of
performance criteria that need to be met to satisfactorily support different use cases of cyber-physical control
applications used by various vertical markets.
5 Performance requirements
5.1 Overview
There are two fundamental perspectives concerning dependable communication in 5G systems: the end-to-end
perspective of the communication services and the network perspective (see Figure 5.1-1).
distri buted
5G Service Performance Requirements
distri buted
a u to ma ti o n
a u to ma ti o n
application
application
CSIF CSIF
5G System
Communication Service
CSIF – Communication Service Interface between distributed automation application/function and 5G system

Figure 5.1-1: Network perspective of 5G system
The Communication Service in Figure 5.1-1 may be implemented as a logical communication link between a UE on
one side and a network server on the other side, or between a UE on one side and a UE on the other side.
ETSI
3GPP TS 22.104 version 16.5.0 Release 16 12 ETSI TS 122 104 V16.5.0 (2020-09)
In some cases, a local approach (e.g. network edge) is preferred for the communication service on the network side in
order to reduce the latency, to increase communication service availability, or to keep sensitive data in a non-public
network on the factory site.
The tables in Clauses 5.2 through 5.5 below provide sets of requirements, where periodicity and determinism are critical
to meeting cyber-physical control application needs in various vertical scenarios. While many use cases have similar
KPI values, the important distinction is that in order to meet the needs of different verticals and different uses, the 5G
system will need to be sufficiently flexible to allow deployment configurations that can meet the different sets of KPIs
specific to each use.
Communication service availability is considered an important service performance requirement for cyber-physical
applications, especially for applications with deterministic traffic. The communication service availability depends on
the latency and reliability (in the context of network layer packet transmissions, as defined in TS 22.261 [2]) of the
logical communication link, as well as the survival time of the cyber-physical application (see Annex C.3 for further
details on these relations).
The communication service reliability requirements also depend on the operation characteristics of the corresponding
cyber-physical applications. Typically, the communication services critical for the automation application also come
with stringent communication service reliability requirements. Note that the communication service reliability
requirement has no direct relationship with the communication service availability requirement.
The "# of UEs" in the tables in clauses 5.2 to 5.5 is intended to give an indication of the UE density that would need to
be served within a given service area (e.g. to understand the kind of capacity demand it puts on the 5G system).
Clock synchronisation is needed in many "vertical" use cases. The requirements and tables in Clause 5.6 provide
specific criteria for managing time sensitive communications in an industrial environment.
High accuracy positioning is becoming essential for Factories of the Future. The
...