Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 22.104  Word version:  19.1.0

Top   Top   Up   Prev   Next
0f…   4…   5…   5.3…   6…   A…   A.2.2…   A.2.2.4…   A.2.3…   A.4…   A.4.4…   A.4.4.3…   A.4.5…   A.4.8…   A.5…   A.6…   B…   C…   C.3   C.4…   C.5   D…   E…

 

5  Performance requirementsp. 12

5.1  Overviewp. 12

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).
Reproduction of 3GPP TS 22.104, Fig. 5.1-1: Network perspective of 5G system
Up
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.
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) 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.
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 reason for this is that tracking of mobile devices as well as mobile assets is becoming increasingly important in improving processes and increasing flexibility in industrial environments, Clause 5.7 provides positioning requirements for horizontal and vertical accuracy, availability, heading, latency and UE speed in an industrial use case scenario.
An example of the relationship between reliability (in the context of network layer packet transmissions, as defined in TS 22.261), survival time and communication service availability of a logical communication link is illustrated in the following Table 5.1-1. This is done for a special case where packet errors are uncorrelated, which in many cases is an unrealistic assumption.
Communication service availability Reliability (as defined in TS 22.261) 1 - p
99.999 9 %99.9 %
99.999 999 %99.99 %
99.999 999 99 %99.999 %
99.999 999 999 9 %99.999 9 %
99.999 999 999 999 %99.999 99 %
Up

5.2  Periodic deterministic communicationp. 14

Periodic deterministic communication is periodic with stringent requirements on timeliness and availability of the communication service. A transmission occurs every transfer interval. A description of periodic deterministic communication can be found in Clause 4.3 and Clause 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.2-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.2-1 can be found in Annex C.
The 5G system shall be able to provide periodic deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.2-1.
Process and asset monitoring using industrial wireless sensors is a special case of periodic deterministic communication with more relaxed requirements on timeliness and availability. These use cases put a slightly different set of requirements on the 5G system due to the specific constraints of industrial wireless sensors. These requirements for individual logical communication links are listed in Table 5.2-2 and additional information on the underlying use cases can be found in Annex A.
Smart-Grid use case information can be found in Annex A.
Characteristic parameter Influence quantity Remarks
Communi­cation service availa­bility: target value (note 1) Communi­cation service relia­bility: mean time between failures End-to-end latency: maximum (note 2) (note 12a) Service bit rate: user expe­rienced data rate (note 12a) Message size [byte] (note 12a) Transfer interval: target value (note 12a) Survival time (note 12a) UE speed (note 13) # of UEs Service area (note 3)
99.999 % to 99.999 99 %~ 10 years< transfer interval value50500 μs500 μs≤ 75 km/h≤ 2050 m x 10 m x 10 mMotion control (clause A.2.2.1)
9.999 9 % to 99.999 999 %~ 10 years< transfer interval value401 ms1 ms≤ 75 km/h≤ 5050 m x 10 m x 10 mMotion control (clause A.2.2.1)
99.999 9 % to 99.999 999 %~ 10 years< transfer interval value202 ms2 ms≤ 75 km/h≤ 10050 m x 10 m x 10 mMotion control (clause A.2.2.1)
99.999 9 %< 5 ms1 kbit/s (steady state)
1.5 Mbit/s (fault case)
< 1,500< 60 s (steady state)
≥ 1 ms (fault case)
transfer intervalstationary2030 km x 20 kmElectrical Distribution - Distributed automated switching for isolation and service restoration (clause A.4.4); (note 5)
99.999 9 % to 99.999 999 %~ 10 years< transfer interval value1 k≤ 10 ms10 ms5 to 10100 m x 30 m x 10 mControl-to-control in motion control (clause A.2.2.2); (note 9)
99.999 9 % to 99.999 999 %~ 10 years< transfer interval value (note 5)50 Mbit/s≤ 1 ms3 x transfer intervalstationary2 to 5100 m x 30 m x 10 mWired-2-wireless 100 Mbit/s link replacement (clause A.2.2.4)
99.999 9 % to 99.999 999 %~ 10 years< transfer interval value (note 5)250 Mbit/s≤ 1 ms3 x transfer intervalstationary2 to 5100 m x 30 m x 10 mWired-2-wireless 1 Gbit/s link replacement (clause A.2.2.4)
99.999 9 % to 99.999 999 %~ 10 years< transfer interval value1 k≤ 50 ms50 ms5 to 101,000 m x 30 m x 10 mControl-to-control in motion control (clause A.2.2.2); (note 9)
> 99.999 9 %~ 10 years< transfer interval value40 to 2501 ms to 50 ms (note 6) (note 7)transfer interval value≤ 50 km/h≤ 2,000≤ 1 km²Mobile robots (clause A.2.2.3)
99.999 9 % to 99.999 999 %~ 1 month< transfer interval value40 to 2504 ms to 8 ms (note 7)transfer interval value< 8 km/h (linear movement)TBD50 m x 10 m x 4 mMobile control panels - remote control of e.g. assembly robots, milling machines (clause A.2.4.1); (note 9)
99.999 999 %1 day< 8 ms (note 14)250 kbit/s40 to 2508 ms16 msquasi-static; up to 10 km/h2 or more30 m x 30 mMobile Operation Panel: Emergency stop (connectivity availability) (clause A.2.4.1A)
99.999 99 %1 day< 10 ms (note 14)< 1 Mbit/s< 102410 ms~10 msquasi-static; up to 10 km/h2 or more30 m x 30 mMobile Operation Panel: Safety data stream (clause A.2.4.1A)
99.999 999 %1 day10 ms to 100 ms (note 14)10 kbit/s10 to 10010 ms to 100 mstransfer intervalstationary2 or more100 m² to 2,000 m²Mobile Operation Panel: Control to visualization (clause A.2.4.1A)
99.999 999 %1 day< 1 ms (note 14)12 Mbit/s to 16 Mbit/s10 to 1001 ms~1 msstationary2 or more100 m²Mobile Operation Panel: Motion control (clause A.2.4.1A)
99.999 999 %1 day< 2 ms (note 14)16 kbit/s (UL) 2 Mbit/s (DL)502 ms~2 msstationary2 or more100 m²Mobile Operation Panel: Haptic feedback data stream (clause A.2.4.1A)
99.999 9 % to 99.999 999 %~ 1 year< transfer interval40 to 250< 12 ms (note 7)12 ms< 8 km/h (linear movement)TBDtypically 40 m x 60 m; maximum 200 m x 300 mMobile control panels -remote control of e.g. mobile cranes, mobile pumps, fixed portal cranes (clause A.2.4.1); (note 9)
99.999 9 % to 99.999 999 %≥ 1 year< transfer interval value20≥ 10 ms (note 8)0typically stationarytypically 10 to 20typically ≤ 100 m x 100 m x 50 mProcess automation - closed loop control (clause A.2.3.1)
99.999 %TBD~ 50 ms~ 100~ 50 msTBDstationary≤ 100,000several km² up to 100,000 km²Primary frequency control (clause A.4.2); (note 9)
99.999 %TBD~ 100 ms~ 100~ 200 msTBDstationary≤ 100,000several km² up to 100,000 km²Distributed Voltage Control (clause A.4.3) (note 9)
> 99.999 9 %~ 1 year< transfer interval value15 k to 250 k10 ms to 100 ms (note 7)transfer interval value≤ 50 km/h≤ 2,000≤ 1 km²Mobile robots - video-operated remote control (clause A.2.2.3)
> 99.999 9 %~ 1 year< transfer interval value40 to 25040 ms to 500 ms (note 7)transfer interval value≤ 50 km/h≤ 2,000≤ 1 km²Mobile robots (clause A.2.2.3)
99.99 %≥ 1 week< transfer interval value20 to 255100 ms to 60 s (note 7)≥ 3 x transfer interval valuetypically stationary≤ 10,000 to 100,000≤ 10 km x 10 km x 50 mPlant asset management (clause A.2.3.3)
> 99.999 999 %>10 years< 2 ms2 Mbit/s to 16 Mbit/s250 to 2,0001 mstransfer interval valueStationary1< 100 m²Robotic Aided Surgery (clause A.6.2)
> 99.999 9%>1 year< 20 ms2 Mbit/s to 16 Mbit/s250 to 2,0001 mstransfer interval valueStationary2 per 1,000 km²< 400 km (note 12)Robotic Aided Surgery (clause A.6.2)
> 99.999 %>> 1 month (< 1 year)< 20 ms2 Mbit/s to 16 Mbit/s801 mstransfer interval valueStationary20 per 100 km²< 50 km (note 12)Robotic Aided Diagnosis (clause A.6.3)
99.999 9 % to 99.999 999 %~ 10 years< 0,5 x transfer interval2,5 Mbit/s250
500 with localisation information
> 5 ms
> 2.5 ms
> 1.7 ms
(note 10)
0 transfer interval 2 x transfer interval (note 10)≤ 6 km/h (linear movement)2 to 810 m x 10 m x 5 m; 50 m x 5 m x 5 m (note 11)Cooperative carrying - fragile work pieces; (ProSe communi­cation) (clause A.2.2.5)
99.999 9 % to 99.999 999 %~ 10 years< 0.5 x transfer interval2.5 Mbit/s250
500 with localisation information
> 5 ms
>2,5 ms
>1,7 ms
(note 10)
0 transfer interval 2 x transfer interval (note 10)≤ 12 km/h (linear movement)2 to 810 m x 10 m x 5 m; 50 m x 5 m x 5 m (note 11)Cooperative carrying - elastic work pieces; (ProSe communi­cation) (clause A.2.2.5)
> 99.9 % DL: < 10 ms
UL: < 10 ms
UL: > 16 Mbit/s (urban), 640 Mbit/s (rural)
DL: > 100 kbit/s
(note 15)
UL: 800 kbyteUL: 10 ms > 10/km² (urban),
> 100/km² (rural)
(note 16)
Distributed energy storage - moni­toring (clause A.4.6)
> 99.9 % DL: < 10 ms
UL: < 1 s
UL: > 128 kbit/s (urban), 10.4 Mbit/s (rural)
DL: > 100 kbit/s
(note 15)
UL: 1.3 Mbyte
DL: > 100 kbyte
UL: 1000 ms > 10/km² (urban),
> 100/km² (rural)
(note 16)
Distri­buted energy storage - data collec­tion (clause A.4.6)
> 99.99 %General infor­mation data collec­tion: < 3 s
(note 17)
UL: < 2 Mbit/s
DL: < 1 Mbit/s
< 10,000/km² (note 18)Advanced metering (clause A.4.7)
99.999 %< 10 ms2 Mbit/s to 10 Mbit/s normal: 1 s;
fault: 2 ms
(note 24)
54/km² (note 19),
78/km² (note 20)
Intelligent distributed feeder automation (clause A.4.4.3)
> 99.99 %10 ms, 100 ms, 3 s (note 22)> 2 Mbit/s (note 21) 500 in the service area (note 23)Communi­cation distance is from 100 m to 500 m, outdoor, indoor / deep indoorSmart distri­bution -trans­former terminal (clause A.4.8)
99.999 %5 ms, 10 ms, 15 ms (note 25)1.2 Mbit/s to 2.5 Mbit/s< 245 byte ≤ 1 ms
≤ 2 ms
(note 26)
≤ 100/km²several km²High speed current diffe­rential protec­tion (note 12a) (clause A.4.4.4)
99.999 9 %3 ms5.4 Mbit/s140 byte≤ 1 msstationaryDistri­buted Energy Resources (DER) and micro-grids (clause A.4.9)
99.999 9 %100 ms (note 12a and note 5)< 1 kbit/s per DERstationaryEnsuring uninter­rupted communi­cation service availa­bility during emer­gencies (clause A.4.10)
NOTE 1:
One or more retransmissions of network layer packets may take place in order to satisfy the communi­cation service availability requirement.
NOTE 2:
Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
NOTE 3:
Length x width (x height).
NOTE 4:
(void)
NOTE 5:
Communication includes two wireless links (UE to UE).
NOTE 6:
This covers different transfer intervals for different similar use cases with target values of 1 ms, 1 ms to 10 ms, and 10 ms to 50 ms.
NOTE 7:
The transfer interval deviates around its target value by < ±25 %.
NOTE 8:
The transfer interval deviates around its target value by < ±5 %.
NOTE 9:
Communication may include two wireless links (UE to UE).
NOTE 10:
The first value is the application requirement, the other values are the requirement with multiple transmission of the same information (two or three times, respectively).
NOTE 11:
Service Area for direct communication between UEs. The group of UEs with direct communication might move throughout the whole factory site (up to several km²).
NOTE 12:
Maximum straight-line distance between UEs.
NOTE 12a:
It applies to both UL and DL unless stated otherwise.
NOTE 13:
It applies to both linear movement and rotation unless stated otherwise.
NOTE 14:
The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
NOTE 15:
Service bit rate for one energy storage station.
NOTE 16:
Activity storage nodes/km2. This value is used for deducing the data volume in an area that features multiple energy storage stations. The data volume can be calculated with the following formula (current service bit rate per storage station) x (activity storage nodes/km2) + (video service bit rate per storage station) x (activity storage nodes/km2).
NOTE 17:
One-way delay from 5G IoT device to backend system. The distance between the two is below 40 km (city range).
NOTE 18:
Typical connection density in today's city environment. With the evolution from centralised meters to socket meters in the home, the connection density is expected to increase 5 to 10 times.
NOTE 19:
When the distributed terminals are deployed along an overhead line, there are about 54 terminals per square kilometre.
NOTE 20:
When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals per square kilometre.
NOTE 21:
Service bit rate of the smart metering application between the smart distribution transformer terminal and the energy end equipment. Once there are multiple smart grid applications, the required service bit rate will be higher.
NOTE 22:
The end-to-end latency depends on the applications supported by the smart distribution transformer terminal. The lower the end-to-end latency, the more applications can be supported.
NOTE 23:
The service area is circular with a radius between 100 m and 500 m (0.031 km2 to 0.79 km2).
NOTE 24:
During the normal working phase of the feeder system, the heartbeat packet is transmitted periodically with a 1 s transfer interval. When a fault occurs, the heartbeat is sent with a 2 ms transfer interval.
NOTE 25:
The maximum allowed delay between two protection relays would be between 5 ms and 10 ms, depending on the voltage (see IEC 61850-90-1 for more details [aa]). For some legacy systems, the end-to-end latency is usually set to 15 ms.
NOTE 26:
For a sampling rate of 600 Hz, the transfer interval is 1.7 ms. For 1200 Hz, the transfer interval is 0.83 ms.
 
Characteristic parameter Influence quantity Remarks
Communi­cation service avail­ability: target value Communi­cation service reli­ability: mean time between failure End-to-end latency (note 6) Transfer interval (note 1) (note 7) Service bit rate: user expe­rienced data rate (note 2) (note 7) Battery lifetime [year] (note 3) Message Size [byte] (note 7) Survival time (note 7) UE speed UE density [UE / m²] Range [m] (note 4)
99.99 %≥ 1 week< 100 ms100 ms to 60 s≤ 1 Mbit/s≥ 520 (note 5)3 x transfer intervalstationaryUp to 1< 500Process monitoring, e.g. temperature sensor (clause A.2.3.2)
99.99 %≥ 1 week< 100 ms≤ 1 s≤ 200 kbit/s≥ 525 k3 x transfer intervalstationaryUp to 0.05< 500Asset monitoring, e.g. vibration sensor (clause A.2.3.2)
99.99 %≥ 1 week< 100 ms≤ 1 s≤ 2 Mbit/s≥ 5250 k3 x transfer intervalstationaryUp to 0.05< 500Asset monitoring, e.g. thermal camera (clause A.2.3.2)
NOTE 1:
The transfer interval deviates around its target value by < ± 25 %.
NOTE 2:
The traffic is predominantly mobile originated.
NOTE 3:
Industrial sensors can use a wide variety of batteries depending on the use case, but in general they are highly constrained in terms of battery size.
NOTE 4:
Distance between the gNB and the UE.
NOTE 5:
The application-level messages in this use case are typically transferred over Ethernet. For small messages, the minimum Ethernet frame size of 64 bytes applies and dictates the minimum size of the PDU sent over the air interface.
NOTE 6:
It applies to both UL and DL unless stated otherwise.
NOTE 7:
It applies to UL.
Up

Up   Top   ToC