hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.6.1 AR/VR
|
Audio-visual interaction is characterised by a human being interacting with the environment or people, or controlling a UE, and relying on audio-visual feedback. In the use cases like VR and interactive conversation the latency requirements include the latencies at the application layer (e.g. codecs), which could be specified outside of 3GPP.
To support VR environments with low motion-to-photon capabilities, the 5G system shall support:
- motion-to-photon latency in the range of 7 ms to 15ms while maintaining the required resolution of up to 8k giving user data rate of up to [1Gbit/s] and
- motion-to-sound delay of [< 20 ms].
NOTE: The motion-to-photon latency is defined as the latency between the physical movement of a user's head and the updated picture in the VR headset. The motion-to-sound latency is the latency between the physical movement of a user's head and updated sound waves from a head mounted speaker reaching their ears.
To support interactive task completion during voice conversation, the 5G system shall support low-delay speech coding for interactive conversational services (100 ms, one-way mouth-to-ear).
Due to the separate handling of the audio and video component, the 5G system will have to cater for the VR audio-video synchronisation in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). To support VR environments the 5G system shall support audio-video synchronisation thresholds:
- in the range of [125 ms to 5 ms] for audio delayed and
- in the range of [45 ms to 5 ms] for audio advanced.
The 5G system shall support service continuity for AR/VR to support immersive user experience under high UE mobility.
When it comes to implementation of applications containing AR/VR components, the requirements on the 5G network could depend on architectural choices implementing these services. Note 3 in table 7.1-1 above gives an example on such dependences for a VR application in a 5G system. Table 7.6.1-1 below illustrates additional use cases and provides more corresponding requirements on the 5G system.
- Cloud/Edge/Split Rendering – Cloud/Edge/Split Rendering is characterised by the transition and exchange of the rendering data between the rendering server and device.
- Gaming or Training Data Exchanging – This use case is characterised by the exchange of the gaming or training service data between two 5G connected AR/VR devices.
- Consume VR content via tethered VR headset – This use case involves a tethered VR headset receiving VR content via a connected UE; this approach alleviates some of the computation complexity required at the VR headset, by allowing some or all decoding functionality to run locally at the connected UE. The requirements in the table below refer to the direct wireless link between the tethered VR headset and the corresponding connected UE.
Table 7.6.1-1 KPI Table for additional high data rate and low latency service
Use Cases
Characteristic parameter (KPI)
Influence quantity
Max allowed end-to-end latency
Service bit rate: user-experienced data rate
Reliability
# of UEs
UE Speed
Service Area
(note 2)
Cloud/Edge/Split Rendering
(note 1)
5 ms (i.e. UL+DL between UE and the interface to data network) (note 4)
0,1 to [1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to120 frames per second content.
99,99 % in uplink and 99,9 % in downlink (note 4)
-
Stationary or Pedestrian (note 7)
Countrywide
Gaming or Interactive Data Exchanging
(note 3)
10ms (note 4)
0,1 to [1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to120 frames per second content.
99,99 % (note 4)
≤ [10]
Stationary or Pedestrian (note 7)
20 m x 10 m; in one vehicle (up to 120 km/h) and in one train (up to 500 km/h)
Consumption of VR content via tethered VR headset
(note 6)
[5 to 10] ms
(note 5)
0,1 to [10] Gbit/s
(note 5)
[99,99 %]
-
Stationary or Pedestrian
-
NOTE 1: Unless otherwise specified, all communication via wireless link is between UEs and network node (UE to network node and/or network node to UE) rather than direct wireless links (UE to UE).
NOTE 2: Length x width (x height).
NOTE 3: Communication includes direct wireless links (UE to UE).
NOTE 4: Latency and reliability KPIs can vary based on specific use case/architecture, e.g. for cloud/edge/split rendering, and can be represented by a range of values.
NOTE 5: The decoding capability in the VR headset and the encoding/decoding complexity/time of the stream will set the required bit rate and latency over the direct wireless link between the tethered VR headset and its connected UE, bit rate from 100 Mbit/s to [10] Gbit/s and latency from 5 ms to 10 ms.
NOTE 6: The performance requirement is valid for the direct wireless link between the tethered VR headset and its connected UE.
NOTE 7: Similar user-experienced data rates may be achievable also at higher UE speeds. [50]
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.7 KPIs for UE to network relaying in 5G system
|
In several scenarios, it can be beneficial to relay communication between one UE and the network via one or more other UEs. The functional requirements related to relaying can be found in clause 6.9.2. Performance requirements for relaying in different scenarios can be found in table 7.7-1.
Table 7.7-1: Key Performance for UE to network relaying
Scenario
Max. data rate (DL)
Max. data rate (UL)
End-to-end latency
(note 7)
Area traffic capacity
(DL)
Area traffic capacity
(UL)
Area user density
Area
Range of a single hop
(note 8)
Estimated number of hops
InHome Scenario
(note 1)
1 Gbit/s
500 Mbit/s
10 ms
5 Gbit/s/ home
2 Gbit/s /home
50 devices /house
10 m x 10m – 3 floors
10 m indoor
2 to 3
Factory Sensors
(note 2)
100 kbit/s
5 Mbit/s
50 ms to 1 s
1 Gbit/s /factory
50 Gbit/s /factory
10000 devices /factory
100 m x 100 m
30 m indoor / metallic
2 to 3
Smart Metering
(note 3)
100 bytes / 15 mins
100 bytes / 15 mins
10 s
200 x 100 bytes / 15 mins /hectare
200 x 100 bytes / 15 mins /hectare
200 devices /hectare
100 m x 100 m
> 100 m indoor / deep indoor
2 to 5
Containers
(note 4)
100 bytes / 15 mins
100 bytes / 15 mins
10 s
15000 x 100 bytes / 15 mins /ship
15000 x 100 bytes / 15 mins /ship
15000 containers /ship
400 m x 60 m x 40 m
> 100 m indoor / outdoor / metallic
3 to 9
Freight Wagons
100 bytes / 15 mins
100 bytes / 15 mins
10 s
200 x 100 bytes / 15 mins /train
200 x 100 bytes / 15 mins /train
120 wagons /train
1 km
> 100 m outdoor / tunnel
10 to 15
Public Safety
(note 5)
12 Mbit/s
12 Mbit/s
30 ms
20 Mbit/s /building
40 Mbit/s /building
30
devices
/building
100 m x 100 m – 3 floors
> 50 m indoor (floor or stairwell)
2 to 4
Wearables
(note 6)
10 Mbit/s
10 Mbit/s
10 ms
20 Mbit/s per 100 m2
20 Mbit/s per 100 m2
10 wearables per 100 m2
10 m x 10 m
10 m indoor / outdoor
1 to 2
NOTE 1: Area traffic capacity is determined by high bandwidth consuming devices (e.g. ultra HD TVs, VR headsets), the number of devices has been calculated assuming a family of 4 members.
NOTE 2: Highest data rate assumes audio sensors with sampling rate of 192 kHz and 24 bits sample size.
NOTE 3: Three meters (gas, water, electricity) per house, medium density of 50 to 70 houses per hectare.
NOTE 4: A large containership with a mix of 20 foot and 40 foot containers is assumed.
NOTE 5: A mix of MCPTT, MCVideo, and MCData is assumed. Average 3 devices per firefighter / police officer, of which one video device. Area traffic based on 1080 p, 60 fps is 12 Mbit/s video, with an activity factor of 30% in uplink (30% of devices transmit simultaneously at high bitrate) and 15% in downlink.
NOTE 6: Communication for wearables is relayed via a UE. This relay UE can use a further relay UE.
NOTE 7: End-to-end latency implies that all hops are included.
NOTE 8: 'Metallic' implies an environment with a lot of metal obstructions (e.g. machinery, containers). 'Deep indoor' implies that there can be concrete walls / floors between the devices.
NOTE 9: All the values in this table are example values and not strict requirements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.8 KPIs for 5G Timing Resiliency
|
The 5G system shall be able to support a holdover time capability with timing resiliency performance requirements defined in table 7.8-1.
Table 7.8-1: Timing resiliency performance requirements for 5G System
Use case
Holdover time (note 3)
Sync target
Sync accuracy
Service area
Mobility
Remarks
Power grid (5G network)
Up to 24 hour
UTC (note 1)
<250 ns to1000 ns (note2)
< 20 km2
low
When 5G System provides direct PTP Grandmaster capability to sub-stations
Power grid (time synchronization device)
>5 s
UTC (note 1)
<250 ns to1000 ns (note2)
< 20 km2
low
When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability at sub-stations)
NOTE 1: A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device will provide PPS output which can be used for measuring the difference.
NOTE 2: Different accuracy measurements are based on different configurations needed to support the underlying requirements from IEC 61850-9-3 [32]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment.
NOTE 3: This requirement will vary based on deployment options.
Table 7.8-2: Timing resiliency accuracy KPIs for members or participants of a trading venue [35]
Type of trading activity
Maximum divergence from UTC
Granularity of the timestamp (note 1)
Activity using high frequency algorithmic trading technique
100 µs
≤1 µs
Activity on voice trading systems
1 s
≤1 s
Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading
1 s
≤1 s
Activity of concluding negotiated transactions
1 s
≤1 s
Any other trading activity
1 ms
≤1 ms
NOTE 1: Only relevant for the case where the time synchronization assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.9 KPIs for ranging based services
|
In several scenarios, it can be beneficial to determine the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. The functional requirements related to ranging based services can be found in clause 6.37. Performance requirements for ranging based services in different scenarios can be found in table 7.9-1.
Key performance indicators and key attributes for ranging are defined as follows:
- Ranging accuracy: describes the absolute value of the deviation of the measured distance and/or direction between two UEs to the true distance and/or direction value.
- Confidence level: describes the percentage of all the possible measured distance and/or direction that can be expected to include the true distance and/or direction considering the ranging accuracy.
- Effective ranging distance: the largest distance between the UE who initiates the ranging and target UEs in the ranging operation.
- Line-of-sight (LOS) Environment: the environment between the UE who initiates the ranging and target UEs, such as LOS and non-LOS (NLOS).
- Coverage: type of radio coverage conditions of the UEs who are involved in ranging, such as in coverage (IC), partial coverage (PC) and out of coverage (OOC). See also figure 6.37.1-1.
NOTE: If using licensed spectrum, ranging is only permitted in network coverage under the full control of the operator who provides the coverage, except for public safety networks with dedicated spectrum where ranging might be allowed out of coverage or in partial coverage as well.
- Relative UE velocity: the target UE can be either static or mobile relative to the UE who initiates the ranging. In the latter, the attribute shall also provide some elements about its motion, e.g. maximum speed, trajectory.
- Availability: percentage value of the amount of time when a ranging system is able to provide the required ranging-related data within the performance targets or requirements divided by the amount of time the system is expected to provide the ranging service in a targeted service area.
- Latency: time elapsed between the event that triggers the determination of the ranging-related data and the availability of the ranging-related data at the ranging system interface.
- Ranging interval: time difference between two consecutive ranging operations.
Table 7.9-1: Performance requirements for ranging based services
Ranging scenario
Ranging Accuracy
(95 % confidence level)
Availability
Latency
10ms
50ms
50ms
Effective ranging distance
Coverage
NLOS/LOS
Relative UE velocity
Ranging interval
Number of concurrent ranging operation for a UE
Number of concurrent ranging operation in an area
Distance Accuracy
Direction Accuracy
Smart TV Remoter
10cm up to 3 meter separation
±2° horizontal direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-60°) to (+60°);
±2° Elevation direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-45°) to (+45°)
99 %
50ms
10m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
50ms
-
-
Picture and video sharing based on Ranging results
10cm
2°
99 %
50ms
10m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
50ms
-
-
Distance based smart device control
10cm
-
99 %
100ms
20m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
50ms
20
-
Smart Vehicle Key
10 cm
-
99 %
50ms
30m
IC/PC/OOC
LOS
Static/ Moving
(<2m/s)
25ms
-
50UEs/
(104m2)
Touchless Self-checkout Machine Control
10cm
-
99%
150ms
1m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
100ms
-
=
Hands Free Access
10cm
-
99 %
500ms
10 m
IC/PC/OOC
LOS
Static/ Moving
(1 m/s)
50ms
-
20 UEs/3.14*100m2
Smart Transportation Metro/Bus Validation
10cm
-
99 %
-
2m
IC/PC/OOC
LOS
Static/ Moving
(3km/h)
50ms
20
100 in the area of 8 m2
Ranging of UE’s in front of vending machine
20cm
10°
-
1s
5m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
50ms
-
10
Finding Items in a supermarket
50 cm
5 degree
95 %
-
100m
IC/PC/OOC
LOS
Static/ Moving
(<1m/s)
250ms
-
100 UEs/
(3.14*104m2)
distance based intelligent perception for public safety
50cm
-
99 %
-
20m
IC/PC/OOC
LOS
Static/ Moving
(<20km/h)
-
100
-
Long Distance Search
20m
5°
99 %
-
100m-1km
IC/PC/OOC
LOS
Static/ Moving
(up to 10m/s)
5s
-
-
Long range approximate location
[10m]
±[12.5°]
99 %
-
500m
IC/PC/OOC
LOS
Static/ Moving
(<10m/s)
-
1
[50]UEs/
(104m2)
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.10 KPIs for AI/ML model transfer in 5GS
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.10.1 KPI requirement for direct network connection
|
The 5G system shall support split AI/ML inference between UE and Network Server/Application function with performance requirements as given in Table 7.10.1-1.
Table 7.10.1-1 KPI Table of split AI/ML inference between UE and Network Server/Application function
Uplink KPI
Downlink KPI
Remarks
Max allowed UL end-to-end latency
Experienced data rate
Payload size
Communication service availability
Reliability
Max allowed DL end-to-end latency
Experienced data rate
Payload size
Reliability
15 ms
144 Mbit/s
0.27 MByte
99.999 %
99.9 %
99.999 %
Split AI/ML image recognition
100 ms
1.5 Mbit/s
100 ms
150 Mbit/s
1.5 MByte/frame
Enhanced media recognition
4.7 Mbit/s
12 ms
320 Mbit/s
40 kByte
Split control for robotics
NOTE 1: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
The 5G system shall support AI/ML model downloading with performance requirements as given in Table 7.10.1-2.
Table 7.10.1-2 KPI Table of AI/ML model downloading
Max allowed DL end-to-end latency
Experienced data rate
(DL)
Model size
Communication service availability
Reliability
User density
# of downloaded AI/ML models
Remarks
1s
1.1Gbit/s
138MByte
99.999 %
99.9% for data transmission of model weight factors; 99.999% for data transmission of model topology
AI/ML model distribution for image recognition
1s
640Mbit/s
80MByte
99.999 %
AI/ML model distribution for speech recognition
1s
512Mbit/s(see note 1)
64MByte
Parallel download of up to 50 AI/ML models
Real time media editing with on-board AI inference
1s
536MByte
up to 5000~ 10000/km2 in an urban area
AI model management as a Service
1s
22Mbit/s
2.4MByte
99.999 %
AI/ML based Automotive Networked Systems
1s
500MByte
Shared AI/ML model monitoring
3s
450Mbit/s
170MByte
Media quality enhancement
NOTE 1: 512Mbit/s concerns AI/ML models having a payload size below 64 MB. TBD for larger payload sizes.
NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
The 5G system shall support Federated Learning between UE and Network Server/Application function with performance requirements as given in Table 7.10.1-3.
Table 7.10.1-3: KPI Table of Federated Learning between UE and Network Server/Application function
Max allowed DL or UL end-to-end latency
DL experienced data rate
UL experienced data rate
DL packet size
UL packet size
Communication service availability
Remarks
1s
1.0Gbit/s
1.0Gbit/s
132MByte
132MByte
Uncompressed Federated Learning for image recognition
1s
80.88Mbit/s
80.88Mbit/s
10Mbyte
10Mbyte
TBD
Compressed Federated Learning for image/video processing
1s
TBD
TBD
10MByte
10MByte
Data Transfer Disturbance in Multi-agent multi-device ML Operations
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.10.2 KPI requirement for direct device connection
|
The 5G system shall support split AI/ML inference between AI/ML endpoints by leveraging direct device connection with performance requirements as given in Table 7.10.2-1.
Table 7.10.2-1 KPI Table of Split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection
Max allowed end-to-end latency (NOTE 1)
Payload size (Intermediate data size)
(NOTE 1)
Experienced data rate
(NOTE 1)
Service area dimension
Communication service availability
(NOTE 1)
Reliability
(NOTE 1)
Remarks
10–100 ms
≤ 1.5 Mbyte for each frame
≤ 720 Mbps
Proximity-based work task offloading for Remote driving, AR displaying/gaming, remote-controlled robotics, video recognition and One-shot object recognition
10 ms
≤ 1.6 MByte
(8 bits data format)
≤ 1.28 Gbps
900 m2
(30 m x 30 m)
99.999 %
99.99 %
Local AI/ML model split on factory robots
10 ms
≤ 6.4 Mbyte
(32 bits data format)
≤ 1.5 Gbps
Local AI/ML model split on factory robots
NOTE 1: The KPIs in the table apply to UL data transmission in case of indirect network connection.
The 5G system shall support AI/ML model/data distribution and sharing by leveraging direct device connection with performance requirements as given in Table 7.10.2-2.
Table 7.10.2-2 KPI Table of AI/ML model/data distribution and sharing by leveraging direct device connection
Max allowed end-to-end latency
(NOTE 1)
Experienced data rate
(NOTE 1)
Payload size
(NOTE 1)
Communication service availability
(NOTE 1)
Remark
1s
≤ 1.92 Gbit/s
≤ 240 MByte
99.9 %
AI Model Transfer Management through Direct Device Connection
3s
≤ 81.33 Mbyte/s
≤ 244 MByte
-
transfer learning for trajectory prediction
NOTE 1: The KPIs in the table apply to data transmission using direct device connection.
NOTE 2: The AI/ML model data distribution is for a specific application service
The 5G system shall support AI/ML model/data distribution and sharing by leveraging direct device connection with performance requirements as given in Table 7.10.2-3.
Table 7.10.2-3 KPI Table of Distributed/Federated Learning by leveraging direct device connection
Payload size
(NOTE 1)
Maximum latency
(NOTE 1)
Experienced data rate
(NOTE 1)
Reliability
(NOTE 1)
Remark
132 MByte
2-3 s
≤ 528 Mbit/s
Direct device connection assisted Federated Learning (Uncompressed model)
Asynchronous Federated Learning via direct device connection
≤ 50 MByte
1 s
≤ 220 Mbit/s
99.99%
NOTE 1: The KPIs in the table apply to both UL and DL data transmission in case of indirect network connection.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.11 KPIs for tactile and multi-modal communication service
|
The 5G system shall support tactile and multi-modal communication services with the following KPIs.
Table 7.11-1: Multi-modal communication service performance requirements
Use Cases
Characteristic parameter (KPI)
Influence quantity
Remarks
Max allowed end-to-end latency
Service bit rate: user-experienced data rate
Reliability
Message size (byte)
UE Speed
Service Area
Immersive multi-modal VR (UL: device application sever)
5 ms
(note 2)
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding)
[40]
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
More DoFs can be supported by the haptic device
Stationary or Pedestrian
typically
< 100 km2
(note 5)
Haptic feedback
5 ms
< 1Mbit/s
99.99%
[40]
1500
Stationary or Pedestrian
typically
< 100 km2
(note 5)
Sensing information e.g. position and view information generated by the VR glasses
Immersive multi-modal VR (DL: application sever device)
10 ms
(note1)
1-100 Mbit/s
99.9%
[40]
1500
Stationary or Pedestrian
typically
< 100 km2
(note 5)
Video
10 ms
5-512 kbit/s
99.9%
[40]
50
Stationary or Pedestrian
typically
< 100 km2
(note 5)
Audio
5 ms
(note 2)
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding)
[40]
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
Stationary or Pedestrian
typically
< 100 km2
(note 5)
Haptic feedback
Remote control robot
1-20ms
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
99.999%
[40]
2-8 (1 DoF)
high-dynamic (≤ 50 km/h)
≤ 1 km2
Haptic feedback
20-100ms
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
99.999%
[40]
2-8 (1 DoF)
Stationary or Pedestrian
≤ 1 km2
Haptic feedback
5 ms
1-100 Mbit/s
99.999%
[40]
1500
Stationary or Pedestrian
≤ 1 km2
Video
5 ms
5-512 kbit/s
99.9%
[40]
50-100
Stationary or Pedestrian
≤ 1 km2
Audio
5 ms
< 1Mbit/s
99.999%
[40]
-
Stationary or Pedestrian
≤ 1 km2
Sensor information
Skillset sharing low- dynamic robotics
(including teleoperation) Controller to controlee
5-10ms
0.8 - 200 kbit/s (with compression)
99,999%
[40][45]
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
Stationary or Pedestrian
100 km2
Haptic
(position, velocity)
Skillset sharing low- dynamic robotics
(including teleoperation)
Controlee to controller
5-10ms
0.8 - 200 kbit/s (with compression)
99,999%
[40][45]
1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800
Stationary or Pedestrian
100 km2
Haptic feedback
10ms
1-100 Mbit/s
99,999%
[40] [45]
1500
Stationary or Pedestrian
100 km2
Video
10ms
5-512 kbit/s
99,9%
[40] [45]
50
Stationary or Pedestrian
100 km2
Audio
Skillset sharing Highly dynamic/ mobile robotics
Controller to controlee
1-5ms
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
99,999% (with compression)
99,9% (w/o compression)
[40] [45]
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
high-dynamic
4 km2
Haptic
(position, velocity)
Skillset sharing Highly dynamic/ mobile robotics
Controlee to controller
1-5ms
0.8 - 200 kbit/s
99,999% (with compression)
99,9% (w/o compression)
[40] [45]
1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800
high-dynamic
4 km2
Haptic feedback
1-10ms
1-10 Mbit/s
99,999%
[40] [45]
2000-4000
high-dynamic
4 km2
Video
1-10ms
100-500 kbit/s
99,9%
[40] [45]
100
high-dynamic
4 km2
Audio
Immersive multi-modal navigation applications
Remote Site Local Site (DL)
50 ms [39]
16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding)
99.999 %
[40]
1 DoF: 2 to 8
10 DoF: 20 to 80
100 DoF: 200 to 800
Stationary or Pedestrian
≤ 100 km2
( note 5)
Haptic feedback
<400 ms [39]
1-100 Mbit/s
99.999 %
[40]
1500
Stationary/ or Pedestrian,
≤ 100 km2
(note 5)
Video
<150 ms [39]
5-512 kbit/s
99.9 %
[40]
50
Stationary or Pedestrian
≤ 100 km2
(note 5)
Audio
<300 ms
600 Mbit/s
99.9 %
[40]
1500
Stationary or Pedestrian
≤ 100 km2
(note 5)
VR
Immersive multi-modal navigation applications Local Site Remote Site (UL)
<300 ms
12 kbit/s [26]
99.999 %
[40]
1500
Stationary or Pedestrian
≤ 100 km2
(note 5)
Biometric / Affective
<400 ms [39]
1-100 Mbit/s
99.999 %
[40]
1500
Workers: Stationary/ or Pedestrian, UAV: [30-300mph]
≤ 100 km2
(note 5)
Video
<150 ms [39]
5-512 kbit/s
99.9 %
[40]
50
Stationary or Pedestrian
≤ 100 km2
(note 5)
Audio
<300 ms
600 Mbit/s
99.9 %
[40]
1500
Stationary or Pedestrian
≤ 100 km2
(note 5)
VR
NOTE 1: Motion-to-photon delay (the time difference between the user’s motion and corresponding change of the video image on display) is less than 20 ms, and the communication latency for transferring the packets of one audio-visual media is less than 10 ms, e.g. the packets corresponding to one video/audio frame are transferred to the devices within 10 ms.
NOTE 2: According to IEEE 1918.1 [40] as for haptic feedback, the latency is less than 25 ms for accurately completing haptic operations. As rendering and hardware introduce some delay, the communication delay for haptic modality can be reasonably less than 5 ms, i.e. the packets related to one haptic feedback are transferred to the devices within 10 ms.
NOTE 3: Haptic feedback is typically haptic signal, such as force level, torque level, vibration and texture.
NOTE 4: The latency requirements are expected to be satisfied even when multimodal communication for skillset sharing is via indirect network connection (i.e., relayed by one UE to network relay).
NOTE 5: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.12 KPIs for direct device connection for Public Safety
|
The functional requirements related to relaying of traffic between two Public Safety UEs using direct device connection via one or more ProSe UE-to-UE relay(s) can be found in clause 6.9.3. Performance requirements for relaying in different scenarios can be found in table 7.12-1.
Table 7.12-1: Key Performance for UE to UE relaying for Public Safety
Scenario
Max. data rate
(note 1)
End-to-end latency
(note 3)
Area traffic capacity
Area user density
Area
Range of a single hop
Estimated number of hops
Public Safety
(note 2)
12 Mbit/s
125 ms
40 Mbit/s /5000m2
30
devices
/10000m2
10,000 m2
> 50 m
2 to 6
NOTE 1: The maximum data rate applies for both the traffic transmitted from the UE and received by the UE
NOTE 2: A mix of MCPTT, MCVideo, and MCData is assumed. Average 3 devices per firefighter / police officer, of which one video device. Area traffic based on 1080 p, 60 fps is 12 Mbit/s video, with an activity factor of 30% transmit from the UE (30% of devices transmit simultaneously at high bitrate) and 15% received by the UE.
NOTE 3: End-to-end latency implies that all hops are included.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.13 KPIs for energy-related characteristics exposure
|
The functional requirements related to exposing network energy-related characteristics can be found in clause 6.15a.5.
Exposing carbon equivalent emissions at subscriber level can rely on but does not imply any real-time collection, monitoring or exact subscriber-specific measurements or calculations. It can be provided by means of attribution based on a combination of statistics, computations and estimates as accurate as possible, e.g. based on subscriber’s data volume and operator’s carbon intensity to provide the communication service, which can be collected from external sources. Hence the accuracy of the exposed information depends on this input.
Deriving and providing such information too frequently to many users may consume network energy. Hence, the following KPIs have been defined as a compromise to achieve specific use cases whilst trying to minimize their energy impact.
Table 7.13-1 defines the performance requirements related to the exposure of network energy-related characteristics such as energy consumption and carbon emissions depending on the target use case and associated intended impact.
• To contribute to the comprehensive energy consumption and CO2e transparency in the end-to-end service chain (including both 3GPP and non-3GPP related providers), it is important that the frequency of such indications is meaningful to the user during a session of the communication service (e.g. not more frequently than once per minute when using a video streaming application). Such information may impact the behavior of users during their current session.
• To empower mobile subscribers (individuals and companies) to contribute to overall energy and carbon footprint reduction by understanding the carbon equivalent emissions resulting from their use of the communication service, it is important to provide periodic information (e.g. per day over a month period), although such reports may only impact the behavior of users during future sessions.
Table 7.13-1: Performance requirements for energy-related characteristics exposure
Characteristic parameter (KPI)
Information
Use Cases
System Granularity
Time Granularity
Time Range
Obtainment (informative)
Carbon emissions (e.g. in kg of CO2e)
Subscriber’s carbon footprint information exposure to 3rd party. (NOTE 1)
UE
Day
Month
Calculation (e.g. average or statistical model) based on attribution of network energy consumption, carbon intensity and/or renewable energy ratio.
Energy Consumption and CO2e transparency in the end-to-end service chain (NOTE 2)
Service data flow
Minute
Session duration
Energy consumption (e.g. in kWh)
Energy Consumption and CO2e transparency in the end-to-end service chain (NOTE 2)
Service data flow
Minute
Session duration
Calculation of network energy consumption based on attribution e.g. measurements, service settings, external information and models.
NOTE 1: Such indication should be meaningful to the user to raise awareness on a monthly reporting basis or to incentivize the service consumer (out of scope of 3GPP).
NOTE 2: Frequency of such indications should be meaningful to the user during the communication service (e.g. video streaming application).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8 Security
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.1 Description
|
IoT introduces new UEs with different life cycles, including IoT devices with no user interface (e.g. embedded sensors), long life spans during which an IoT device can change ownership several times (e.g. consumer goods), and which cannot be pre-provisioned (e.g. consumer goods). These drive a need for secure mechanisms to dynamically establish or refresh credentials and subscriptions. New access technologies, including licensed and unlicensed, 3GPP and non-3GPP, drive a need for access-independent security that is seamlessly available while the IoT device is active. High-end smartphones, UAVs, and factory automation drive a need for protection against theft and fraud. A high level of 5G security is essential for critical communication, e.g. in industrial automation, industrial IoT, and the Smart Grid. Expansion into enterprise, vehicular, medical, and public safety markets drive a need for increased end user privacy protection. 5G security addresses all of these new needs while continuing to provide security consistent with prior 3GPP systems.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.2 General
|
The 5G system shall support a secure mechanism to store cached data.
The 5G system shall support a secure mechanism to access a content caching application.
The 5G system shall support a secure mechanism to access a service or an application in an operator's Service Hosting Environment.
The 5G system shall enable support of an access-independent security framework.
The 5G system shall support a mechanism for the operator to authorize subscribers of other PLMNs to receive temporary service (e.g. mission critical services).
The 5G system shall be able to provide temporary service for authorized users without access to their home network (e.g. IOPS, mission critical services).
The 5G system shall allow the operator to authorize a third-party to create, modify and delete network slices, subject to an agreement between the third-party and the network operator.
Based on operator policy, a 5G network shall provide suitable means to allow a trusted and authorized third-party to create and modify network slices used for the third-party with appropriate security policies (e.g. user data privacy handling, slices isolation, enhanced logging).
The 5G system shall support a secure mechanism to protect relayed data from being intercepted by a relay UE.
Subject to HPLMN policy as well as its service and operational needs, any USIM able to access EPS instead of a 5G USIM may be used to authenticate a user in a 5G system to access supported services according to the user subscription.
The 5G system shall provide integrity protection and confidentiality for communications between authorized UEs using a 5G LAN-type service.
The 5G LAN-VN shall be able to verify the identity of a UE requesting to join a specific private communication.
The 5G system shall provide suitable means to allow the use of a trusted third-party provided encryption between any UE served by a private slice and a core network entity in that private slice.
The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a private slice and a core network entity in that private slice.
The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a non-public network and a core network entity in that non-public network.
The 5G system shall enable a PLMN to host an NPN without compromising the security of that PLMN.
NOTE: Dedicated network entities of NPN can be deployed in customer premises that are outside the control of the PLMN operator.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.3 Authentication
|
The 5G system shall support an efficient means to authenticate a user to an IoT device (e.g. biometrics).
The 5G system shall be able to support authentication over a non-3GPP access technology using 3GPP credentials.
The 5G system shall support operator-controlled alternative authentication methods (i.e. alternative to AKA) with different types of credentials for network access for IoT devices in isolated deployment scenarios (e.g. for industrial automation).
The 5G system shall support a suitable framework (e.g. EAP) allowing alternative (e.g. to AKA) authentication methods with non-3GPP identities and credentials to be used for UE network access authentication in non-public networks.
NOTE: Non-public networks can use 3GPP authentication methods, identities, and credentials for a UE to access network. Non-public networks are also allowed to utilize non-AKA based authentication methods such as provided by the EAP framework, for which the credentials can be stored in the ME.
Subject to an agreement between an MNO and a 3rd party, the 5G system shall support a mechanism for the PLMN to authenticate and authorize UEs for access to both a hosted non-public network and private slice(s) of the PLMN associated with the hosted non-public network.
The 5G network shall support a 3GPP supported mechanism to authenticate legacy non-3GPP devices for 5G LAN-VN access.
The 5G system shall support a mechanism for the non-public network to authenticate and authorize UEs for access to network slices of that non-public network.
The 5G system shall enable an NPN to be able to request a third-party service provider to perform NPN access network authentication of a UE based on non-3GPP identities and credentials supplied by the third-party service provider.
The 5G system shall enable an NPN to be able to request a PLMN to perform NPN access network authentication of a UE based on 3GPP identities and credentials supplied by the PLMN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.4 Authorization
|
The 5G system shall allow the operator to authorize an IoT device to use one or more 5G system features that are restricted to IoT devices.
The 5G system shall allow the operator to authorize /de-authorize UEs for using 5G LAN-type service.
NOTE: When a UE is de-authorized from using 5G LAN-type service, it is removed from all 5G LAN-VNs.
Based on operator policy, before establishing a direct device connection using a non-3GPP access technology, IoT devices may use 3GPP credentials to determine if they are authorized to engage in direct device connection.
Based on operator policy, the 5G system shall provide a means to verify whether a UE is authorized to use prioritized network access for a specific service.
A 5G system with satellite access supporting S&F Satellite operation shall be able to support mechanisms to authorize a UE to use the S&F satellite operation.
A 5G system with satellite access shall be able to support mechanisms to authorize the UE-Satellite-UE communication, based on e.g., location information and subscription.
NOTE: UEs can use satellite access directly or via a relay UE (using satellite access assuming that the 5G system with satellite access is authorized to assign spectrum resources for the communication between remote UE and relay UE).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.5 Identity management
|
The 5G system shall provide a mechanism for an operator to allow access from a UE using a temporary identifier that hides its subscriber identity.
The 5G system shall provide a mechanism for an operator to allow access from a UE connected in an indirect network connection using a temporary identifier that hides its subscriber identity.
The HPLMN shall be able to associate a temporary identifier to a UE's subscriber identity.
The 5G system shall be able to protect subscriber identity and other user identifying information from passive attacks.
Subject to regional or national regulatory requirements, the 5G system shall be able to protect subscriber identity and other user identifying information from active attacks.
The 5G system shall be able to allow the equipment identifier to be collected by legitimate entity regardless of UE's user interface, when required.
The 5G system shall be able to support identification of subscriptions independently of identification of equipment.
The 5G system shall support a secure mechanism to collect system information while ensuring end-user and application privacy (e.g. application level information is not to be related to an individual user identity or subscriber identity and UE information is not to be related to an individual subscriber identity).
Subject to regional or national regulatory requirements, the 5G system shall be able to provide the 5G positioning services while ensuring the protection of the privacy of the UE's user or owner, including the respect of his consent to the positioning services.
NOTE 1: this includes the ability for the 5G system to provide the positioning services on demand without having to track continuously the position of the involved UE.
NOTE 2: the respect of the user's consent to some positioning services could abide by different rules in case of emergency (for example, rules that would also receive consent from the user, but well before the emergency occurs).
For a private network using 5G technology, the 5G system shall support network access using identities, credentials, and authentication methods provided and managed by a third-party and supported by 3GPP.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.6 Regulatory
|
The 5G system shall support regional or national regulatory requirements for all supported access networks.
The 5G system shall support Lawful Interception, subject to regional or national regulatory requirements.
A 5G satellite access network connected to 5G core networks in multiple countries shall be able to meet the corresponding regulatory requirements from these countries (e.g. Lawful Interception).
A 5G system shall support regulatory requirements for 5G LAN-type services.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.7 Fraud protection
|
Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to disable from normal operation of a UE reported as stolen.
Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to re-enable a recovered stolen UE to normal operation.
The 5G system shall be able to protect user location information from passive attacks.
Subject to regional or national regulatory requirements, the 5G system shall be able to protect user location information from active attacks.
Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to protect the production of the user location information and user positioning-related data against tampering and spoofing.
Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to detect tampering and spoofing attempts on the production of the user location information and the user position-related data.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.8 Resource efficiency
|
The 5G system shall minimize security signalling overhead without compromising the security level of the 3GPP system.
The 5G system shall support an efficient secure mechanism to transmit the same data (e.g. service provisioning multiple sensors) to multiple UEs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.9 Data security and privacy
|
The 5G system shall support data integrity protection and confidentiality methods that serve URLLC, high data rates and energy constrained devices.
The 5G system shall support a mechanism to verify the integrity of a message as well as the authenticity of the sender of the message.
The 5G system shall support encryption for URLLC services within the requested end-to-end latency.
Subject to regulatory requirements, the 5G system shall enable an MNO to provide end-to-end integrity protection, confidentiality, and protection against replay attacks between a UE and third-party application server, such that the 3GPP network is not able to intercept or modify the data transferred between a UE and third-party application server.
Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support data integrity verification service to assure the integrity of the data exchanged between the 5G network and a third-party service provider.
NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE.
Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support confidentiality to prevent exposure of data exchanged between the 5G network and a third party service provider.
NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE.
Subject to operator’s policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to preserve security of the data stored and forwarded.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
8.10 5G Timing Resiliency
|
The 5G system shall support a mechanism to verify authorization of a 3rd party application to use 5G timing resiliency.
The 5G system shall support a mechanism to monitor and verify authenticity of the timing source, where supported by the time source.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9 Charging aspects
|
9.0 Introduction
This clause addresses the charging aspects of the different services/features described in the present document. Functional service requirements for the respective services/features can be found in the subclauses with the respective titles under clause 6.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.1 General
|
The following set of requirements complement the requirements listed in 3GPP TS 22.115 [11]. The requirements apply for both home and roaming cases.
The 5G core network shall support collection of all charging information on either a network or a slice basis.
The 5G core network shall support collection of charging information for alternative authentication mechanisms.
The 5G core network shall support collection of charging information associated with each serving MNO when multi-network connectivity is used under the control of the home operator.
The 5G core network shall support charging for services/applications in an operator’s Service Hosting Environment.
The 5G core network shall support charging for content delivered from a content caching application.
The 5G core network shall support collection of charging information based on the access type (e.g. 3GPP, non-3GPP, satellite access).
The 5G core network shall support collection of charging information based on the slice that the UE accesses.
The 5G system shall be able to generate charging information regarding the used radio resources e.g. used frequency bands.
The 5G core network shall support collection of charging information based on the capacity and performance metrics.
The 5G system shall be able to support an indirect network connection even when the UE is in E-UTRAN or NG-RAN coverage.
The 5G system shall be able to support mechanisms to differentiate charging information for traffic carried over satellite backhaul.
For service function chaining (see clause 10) the collection of charging information associated to the use of service functions and the chain of service functions requested by third parties shall be supported.
The 5G system shall be able to support collection of charging information for a group of UEs, e.g. UEs of a AI/ML FL group.
The 5G system shall be able to support charging mechanism for multiple UE exchange data for the same service using the direct device connection.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.2 5G LAN-type service
|
A 5G core network shall support collection of charging information for a 5G LAN-type service based on resource usage (e.g. licensed or unlicensed spectrum, QoS, applications).
The 5G core network shall support collection of charging information for a 5G LAN-type service when a UE joins or leaves a specific private communication.
The 5G core network shall support collection of charging information for a 5G LAN-type service for both home and roaming UEs based on the UE’s HPLMN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.3 5G Timing Resiliency
|
The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage).
The 5G system shall be able to collect charging information per UE for use of a timing source (e.g., start/stop time and source used by a UE, timing source used by UE, holdover capability).
The 5G system shall be able to collect charging information on 5G system timing resiliency (e.g., resiliency KPIs, holdover capability, number of UEs using a certain timing source).
The 5G system shall be able to collect charging information per application using 5G timing resiliency, including 3rd party application, (e.g., timing resiliency KPIs, holdover capability, number of UEs using a certain timing source).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.4 Satellite Access
|
In a 5G system with satellite access, charging data records associated with satellite access(es) shall include the location of the associated UE(s) with satellite access.
NOTE: The precision of the location of the UE can be based on the capabilities of the UE or of the network.
A 5G system with satellite access supporting S&F Satellite operation shall be able to collect charging information per UE or per application (e.g., number of UEs, data volume, duration, involved satellites).
A 5G system with satellite access shall be able to collect charging information for a UE registered to a HPLMN or a VPLMN, for UE-Satellite-UE communication.
A 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to collect and distinguish charging information related to user data traffic across satellites with different orbit types having different characteristics (e.g., LEO, MEO, GEO).
The 5G system with satellite access supporting connectivity over multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to collect and distinguish charging information related to the different satellite access traffic carried via a mobile base station relay.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.5 Energy efficiency as a Service Criteria
|
Charging requirements for "Energy efficiency as a Service Criteria" can be found in clauses 6.15a2, 6.15a3 and 6.15a6 of this document.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.6 NG-RAN Sharing
|
The 5G core network shall be able to support collection of charging information associated with a UE accessing a Shared NG-RAN using Indirect Network Sharing, which refers to the resource usage of hosting operator’s core network.
NOTE: When Shared NG-RAN is a shared satellite NG-RAN, the charging information can include the information specific to the shared satellite NG-RAN, e.g. the location of UE, involved satellites.
The 5G network shall be able to collect charging information for a UE accessing a Shared NG-RAN using Indirect Network Sharing in Disaster Condition.
9.7 Minimization of Service Interruption
3GPP system shall be able to collect charging information for a Disaster Inbound Roamer with information about the applied disaster condition.
9.8 Personal IoT Networks and Customer Premises Networks
Charging requirements for "Personal IoT Networks and Customer Premises Networks" can be found in clause 6.38.2.8 of this document.
9.9 AI/ML model transfer in 5GS
The 5G system shall be able to support charging mechanisms for multiple UEs exchanging data for the same service using the direct device connection (e.g. for AI-ML applications).
9.10 Providing Access to Local Services
Charging requirements for "Providing Access to Local Services" can be found in clause 6.41.2.8 of this document.
9.11 Mobile base station relays
Charging requirements for "Mobile base station relays" can be found in clause 6.42.2 of this document.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.12 5G wireless sensing service
|
Charging requirements for "5G wireless sensing" can be found in clause 5.25 of 3GPP TS 22.137 [51].
9.13 Ambient power-enabled IoT
Charging requirements for "Ambient power-enabled IoT" can be found in clause 5.25 of 3GPP TS 22.369 [52].
9.14 Mobile Metaverse Services
Charging requirements for "Mobile Metaverse Services" can be found in clause 8 of 3GPP TS 22.156 [53].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
9.15 Traffic steering and switching over two 3GPP access networks
|
Subject to HPLMN policy and network control, the 5G system shall be able to collect charging information related to traffic steering and/or switching of a DualSteer device’s user data across two 3GPP access networks.
NOTE: Charging information should be collected for both 3GPP access networks; in case the two 3GPP access networks belong to different PLMNs, or a PLMN and NPN, a proper business/roaming agreement among network operators is assumed.
Annex A (informative):
Void
Annex B (informative):
Void
Annex C (informative):
Relation of communication service availability and reliability
NOTE: The content of this annex was moved to annex F of TS 22.104 [21].
Annex D (informative):
Critical-communication use cases
D.1 Factory automation – motion control
D.1.0 General
Factory automation requires communications for closed-loop control applications. Examples for such applications are motion control of robots, machine tools, as well as packaging and printing machines. All other factory automation applications are addressed in Annex D.2.
The corresponding industrial communication solutions are referred to as fieldbuses. The pertinent standard suite is IEC 61158. Note that clock synchronization is an integral part of fieldbuses that support motion control use cases.
In motion control applications, a controller interacts with a large number of sensors and actuators (e.g. up to 100) that are integrated in a manufacturing unit. The resulting sensor/actuator density is often very high (up to 1 m-3). Many such manufacturing units have to be supported within close proximity within a factory (e.g. up to 100 in automobile assembly line production).
In a closed-loop control application, the controller periodically submits instructions to a set of sensor/actuator devices, which return a response within a so-called cycle time. The messages, which are referred to as telegrams, are typically small (≤ 56 bytes). The cycle time can be as low as 2 ms, setting stringent end-to-end latency constraints on telegram forwarding (≤ 1 ms). Additional constraints on isochronous telegram delivery add tight constraints on the lateness (1 s), and the communication service has also to be highly available (99,9999%).
Multi-robot cooperation is a case in closed-loop control, where a group of robots collaborate to conduct an action, for example, symmetrical welding of a car body to minimize deformation. This requires isochronous operation between all robots. For multi-robot cooperation, the lateness (1 µs) is to be interpreted as the lateness among the command messages of a control event to the group robots.
To meet the stringent requirements of closed-loop factory automation, the following considerations have to be taken:
- Limitation to short-range communications.
- Use of direct device connection between the controller and actuators.
- Allocation of licensed spectrum. Licensed spectrum can further be used as a complement to unlicensed spectrum, e.g. to enhance reliability.
- Reservation of dedicated radio interface resources for each link.
- Combination of multiple diversity techniques to approach the high reliability target within stringent end-to-end latency constraints (example: frequency, antenna and various forms of spatial diversity, e.g. via relaying)
- Utilizing OTA time synchronization to satisfy latency-variation constraints for isochronous operation.
A typical industrial closed-loop motion control application is based on individual control events. Each closed-loop control event consists of a downlink transaction followed by a synchronous uplink transaction, both of which are executed within a cycle time. Control events within a manufacturing unit might need to occur isochronously. Factory automation considers application layer transaction cycles between controller devices and sensor/actuator devices. Each transaction cycle consists of (1) a command sent by the controller to the sensor/actuator (downlink), (2) application-layer processing on the sensor/actuator device, and (3) a subsequent response by the sensor/actuator to the controller (uplink). Cycle time includes the entire transaction from the transmission of a command by the controller to the reception of a response by the controller. It includes all lower layer processes and latencies on the radio interface as well the application-layer processing time on the sensor/actuator.
Figure D.1.0-1: Communication path for isochronous control cycles within factory units. Step 1 (red): controller requests sensor data (or an actuator to conduct actuation) from the sensor/actuator (S/A). Step 2 (blue): sensor sends measurement information (or acknowledges actuation) to controller.
Figure D.1.0-1 depicts how communication can occur in factory automation. In this use case, communication is confined to local controller-to-sensor/actuator interaction within each manufacturing unit. Repeaters can provide spatial diversity to enhance reliability.
D.1.1 Service area and connection density
The maximum service volume in motion control is currently set by hoisting solutions, i.e. cranes, and by the manipulation of large machine components, e.g. propeller blades of wind-energy generators. Cranes can be rather wide and quite high above the shop floor, even within a factory hall. In addition, they typically travel along an entire factory hall.
An approximate dimension of the service area is 100 x 100 x 30 m.
Note that production cells are commonly much smaller (< 10 x 10 x 3 m). There are typically about 10 motion-control connections in a production cell, which results in a connection density of up to 105 km-2.
D.1.2 Security
Network access and authorization in an industrial factory deployment is typically provided and managed by the factory owner with its ID management, authentication, confidentiality and integrity.
Note that motion control telegrams usually are not encrypted due to stringent cycle time requirements.
A comprehensive security framework for factories has been described in IEC 62443.
D.2 Factory automation – other use cases
D.2.0 General
Factory automation encompasses all types of production that result in discrete products: cars, chocolate bars, etc. Automation that addresses the control of flows and chemical reactions is referred to as process automation (see clause D.3). Discrete automation requires communications for supervisory and open-loop control applications, as well as process monitoring and tracking of operations inside an industrial plant. In these applications, a large number of sensors, which are distributed over the plant, forward measurement data to process controllers on a periodic or event-driven base. Traditionally, wireline field bus technologies have been used to interconnect sensors and control equipment. Due to the sizable extension of a plant (up to10 km2), the large number of sensors, rotary joints, and the high deployment complexity of wired infrastructure, wireless solutions have made inroads into industrial process automation.
The related use cases require support of a large number of sensor devices per plant, as well as high communication service availability (99,99%). Furthermore, power consumption is relevant since some sensor devices are battery-powered with a targeted battery lifetime of several years (while providing measurement updates every few seconds). Range also becomes a critical factor due to the low transmit power levels of the sensors, the large size of the plant, and the high-reliability requirements on transport. End-to-end latency requirements typically range between 10 ms and 1 s. User-experienced data rates can be rather low since each transaction typically comprises less than 256 bytes. However, there has been a shift from field busses featuring somewhat modest data rates (~ 2 Mbit/s) to those with higher data rates (~ 10 Mbit/s) due to the increasing number of distributed applications and "data-hungry" applications. An example for the latter is the visual control of production processes. For this application, the user experienced data rate is typically around 10 Mbit/s and the transmitted packets are much larger than what was stated earlier.
Existing wireless technologies for factory automation rely on unlicensed bands. Communication is therefore vulnerable to interference caused by other technologies (e.g. WLAN). With the stringent requirements on transport reliability, such interference is detrimental to proper operation.
The use of licensed spectrum could overcome the vulnerability to same-band interference and therefore enable higher reliability. Utilization of licensed spectrum can be confined to those events where high interference bursts in unlicensed bands jeopardizes communication service availability and end-to-end latency constraints. This allows sharing the licensed spectrum between process automation and conventional mobile services.
Multi-hop topologies can provide range extension and mesh topologies can increase reliability through path redundancy. Clock synchronization will be highly beneficial since it enables more power-efficient sensor operation and mesh forwarding.
The corresponding industrial communication solutions are referred to as fieldbuses. The related standard suite is IEC 61158.
A typical discrete automation application supports downstream and upstream data flows between process controllers and sensors/actuators. The communication consists of individual transactions. The process controller resides in the plant network. This network interconnects via base stations to the wireless (mesh-) network which hosts the sensor/actuator devices. Typically, each transaction uses less than 256 bytes. An example of a controller-initiated transaction service flow is:
1. The process controller requests sensor data (or an actuator to conduct actuation). The request is forwarded via the plant network and the wireless network to the sensors/actuators.
2. The sensors/actuators process the request and send a replay in upstream direction to the controller. This reply can contain an acknowledgement or a measurement reading.
An example of a sensor/actuator device-initiated transaction service flow:
1. The sensor sends a measurement reading to the process controller. The request is forwarded via the wireless (mesh) network and the plant network.
2. The process controller can send an acknowledgement in opposite direction.
For both controller- and sensor/actuator-initiated service flows, upstream and downstream transactions can occur asynchronously.
Figure D.2.0-1 depicts how communication can occur in discrete automation. In this use case, communication runs between process controller and sensor/actuator device via the plant network and the wireless (mesh) network. The wireless (mesh) network can also support access for handheld devices for supervisory control or process monitoring purposes.
Figure D.2.0-1: Communication path for service flows between process controllers and sensor/actuator devices. Left-hand side: Step 1 (red) – the sensor/actuator (S/A) sends measurement report autonomously, Step 2 (blue) controller acknowledges. Right-hand side: Step 1 (red) - controller requests sensor data (or an actuator to conduct actuation), Step 2 (blue): S/A sends measurement information (or acknowledges actuation) to controller.
D.2.1 Service area and connection density
Factory halls can be rather large and even quite high. We set the upper limit at 1000 x 1000 x 30 m. Note that the connection density might vary quite a bit throughout factory halls. The density is, for instance, much higher along an assembly line than in an overflow buffer. Also, the density usually increases towards the factory floor. Typically, there is at least one connection per 10 m2, which results in a connection density of up to 105 km-2.
D.2.2 Security
Network access and authorization in an industrial factory deployment is typically provided and managed by the factory owner with its ID management, authentication, confidentiality and integrity.
A comprehensive security framework for factories has been described in IEC 62443.
D.3 Process automation
D.3.0 General
Process automation has much in common with factory automation (see clause D.2). Instead of discrete products (cars, chocolate bars, etc.), process automation addresses the production of bulk products such as petrol and reactive gases. In contrast to factory automation, motion control is of limited or no importance. Typical end-to-end latencies are 50 ms. User-experienced data rates, communication service availability, and connection density vary noticeably between applications. Below, we describe one emerging use case (remote control via mobile computational units, clause D.3.1) and a contemporary use case (monitoring, clause D.3.2).
Note that automation fieldbuses (see clause D.2.0) are also used in process automation.
D.3.1 Remote control
Some of the interactions within a plant are conducted by automated control applications similar to those described in clause D.2. Here too, sensor output is requested in a cyclic fashion, and actuator commands are sent via the communication network between a controller and the actuator. Furthermore, there is an emerging need for the control of the plant by personnel on location. Typically, monitoring and managing of distributed control systems takes place in a dedicated control room.
Staff deployment to the plant itself occurs, for instance, during construction and commissioning of a plant and in the start-up phase of the processes. In this scenario, the locally deployed staff taps into the same real-time data as provided to the control room. These remote applications require high data rates (~ 100 Mbit/s) since the staff on location needs to view inaccessible locations with high definition (e.g. emergency valves) and since their colleagues in the control room benefit from high-definition footage from body cameras (HD or even 4K).
For both kinds of applications, a very high communication service availability is needed (99,9999%). Typically, only a few control loops are fully automated and only handful of control personnel is deployed on location, so that the connection density is rather modest (~ 1000 km-2).
D.3.2 Process and asset monitoring
The monitoring of states, e.g. the level of the liquid of process reactors, is a paramount task in process automation. Due to the ever-changing states, measurement data is either pulled or pushed from the sensors in a cyclic manner. Some sensors are more conveniently accessed via wireless links, and monitoring of these sensors via handheld terminals, e.g. during maintenance, is also on the rise. This kind of application entails rather modest user experienced data rates (~ 1 Mbit/s), and since this kind of data is "only" an indicator for, e.g., what process should be stopped in order to avoid an overflow, and not for automated control loops, the requirement on communication service availability is comparably low (99,9%). Note that emergency valves and such are typically operated locally and do not rely on communication networks. However, many sensors are deployed in chemical plants etc., so that connection density can readily reach 10 000 km-2.
D.3.3 Service area
While, for instance, chemical plants and refineries can span over several square kilometres, the dedicated control rooms are typically only responsible for a subset of that area. Such subsets are often referred to as plants, and their typical size is 300 m x 300 m x 50 m.
D.4 Electric-power distribution and smart grid
D.4.0 General
In TS 22.104 [21] clause A.4, typical electric power distribution and smart grid use cases have been introduced. Here just give some examples.
D.4.1 Medium voltage
D.4.1.0 Overview
An energy-automation domain that now has standards based support by mobile-network technology is the backhaul electricity grid, i.e. the part of the distribution grid between primary substations (high voltage medium voltage) and secondary substations (medium voltage low voltage), and other smart grid services. In figure D.4.1.0-1 we depict a medium-voltage ring together with energy-automation use cases that either are already deployed or are anticipated within the near future.
Figure D.4.1.0-1: Functional, topological sketch of a medium-voltage ring. AMI: advanced metering infrastructure; CB: circuit breaker; DMS: distribution management system; FISR: fault isolation and system restoration; HEM: home energy manager; PQ: power quality; RMU: ring main unit.
The primary substation and the secondary substations are supervised and controlled by a distribution-management system (DMS). If energy-automation devices in the medium-voltage power line ring need to communicate with each other and /or the DMS, a wireless backhaul network needs to be present (orange "cloud" in figure D.4.1.0-1).
A majority of applications in electricity distribution adhere to the communication standard IEC 60870-5-104. However, its modern "cousin" IEC 61850 experiences rapidly increasing popularity. The communication requirements for IEC 61850 applications can be found in EC 61850-90-4. Communication in wide-area networks is described in IEC 61850-90-12.
Usually, power line ring structures have to be open in order to avoid a power-imbalance in the ring (green dot in figure D.4.1.0 1). Examples for energy-automation that already is implemented in medium-voltage grids (albeit in low numbers) are power-quality measurements and the measurement of secondary-substation parameters (temperature, power load, etc.) [13]. Other use cases are demand response and the control of distributed, renewable energy resources (e.g. photovoltaics).
A use case that could also be realised in the future is fault isolation and system restoration (FISR). FISR automates the management of faults in the distribution grid. It supports the localization of the fault, the isolation of the fault, and the restoration of the power delivery. For this kind of automation, the pertinent sensors and actuators broadcast telegrams about their states (e.g., "emergency closer idle") and about actions (e.g., "activating closer") into the backhaul network. This information is used by the ring main units (RMUs) as input for their decision algorithms. We illustrate this use of automation telegrams for an automated FISR event in figure D.4.1.0-1. Let us assume the distribution lines are cut at the location indicated by the bolt of lightning in the figure. In that case, the RMUs between the bolt and the green load switch (open) will be without power. The RMUs next to the "bolt" automatically open their load switches after having sensed the loss of electric connectivity between them. They both broadcast these actions into the backhaul network. Typically, these telegrams are repeated many times while the time between adjacent telegrams increases exponentially. This communication patterns leads to sudden, distributed surges in the consumed communication bandwidth. After the RMUs next to the "bolt" have opened their switch, the RMU that so far has kept the power line ring open (green dot in figure D.4.1.0-1) closes the load switch. This event too is broadcasted into the backhaul network. The typical maximum end-to-end latency for this kind of broadcast is 25 ms with a peak experienced data rate of 10 Mbit/s. Note that the distribution system typically subscribes to telegrams from all RMUs in order to keep abreast with the happenings in the distribution grid.
Automatic fault handling in the distribution grid shortens outage time and offloads the operators in the distribution control centre for more complicated situations. Therefore, automated FISR can help to improve performance indexes like System Average Interruption Duration Index and System Average Interruption Frequency Index.
Automation telegrams are typically distributed via domain multicast. As explained above, the related communication pattern can be "bursty", i.e. only few automation telegrams are sent when the distribution network operates nominally (~ 1 kbit/s), but, for instance, a disruption in the power line triggers a short-lived avalanche of telegrams from related applications in the ring (≥ 1 Mbit/s).
D.4.1.1 Service area and connection density
Service coverage is only required along the medium-voltage line. In Europe, the line often forms a loop (see figure D.4.1.0-1), while deployments in other countries, e.g. the USA, tend to extend linearly over distances up to ~ 100 km. The vertical dimension of the poles in a medium voltages line is typically less than 40 m. Especially in urban areas, the number of ring main units can be rather large (> 10 km-2), and the number of connections to each ring main unit is expected to increase swiftly once economical, suitable wireless connectivity becomes available. We predict connection densities of up to 1.000 km-2.
D.4.1.2 Security
Due to its central role in virtually every country on earth, electricity distribution is heavily regulated. Security assessments for, e.g. deployments in North America, need to adhere to the NERC CIP suite [14]. Technical implementations are described in standard suites such as IEC 62351.
D.4.2 High voltage
D.4.2.0 Overview
In order to avoid region- or even nation-wide power outages, wide-area power system protection is on the rise. "When a major power system disturbance occurs, protection and control actions are required to stop the power system degradation, restore the system to a normal state, and minimize the impact of the disturbance. The present control actions are not designed for a fast-developing disturbance and can be too slow. Local protection systems are not able to consider the overall system, which can be affected by the disturbance. Wide area disturbance protection is a concept of using system-wide information and sending selected local information to a remote location to counteract propagation of the major disturbances in the power system." [15]. Protection actions include, "among others, changes in demand (e.g. load shedding), changes in generation or system configuration to maintain system stability or integrity and specific actions to maintain or restore acceptable voltage levels." [16]. One specific application is phasor measurement for the stabilisation of the alternating-current phase in a transport network. For this, the voltage phase is measured locally and sent to a remote-control centre. There, this information is processed, and automated actions are triggered. One action can be the submission of telegrams to power plants, instructing them to either accelerate or deaccelerate their power generators in order to keep the voltage phase in the transport network stable. A comprehensive overview of this topic can be found elsewhere in the literature [17].
This kind of automation requires very low end-to-end latencies (5 ms) [16] and―due to its critical importance for the operation of society―a very high communication service availability (99,9999%).
D.4.2.1 Service area and connection density
As is the case for medium-voltage distribution networks (see Annex D.4.1), connectivity in high-voltage automation has to be provided mainly along the power line. The distances to be covered can be substantial (hundreds of kilometres in rural settings), while shorter links are prevalent in metropolitan areas. The number of connections in wide-area power system protection is rather low; but―due to the sliver-shaped service area―the connection density can be rather high (1000 km-2).
D.4.2.2 Security
Due to its central role in virtually every country on earth, electricity distribution is heavily regulated. Security assessments for, e.g. deployments in North America, need to adhere to the NERC CIP suite [14]. Technical implementations are described in standard suites such as IEC 62351.
D.5 Intelligent transport systems – infrastructure backhaul
D.5.0 General
Intelligent Transport Systems (ITS) embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public. Over recent years, the emphasis in intelligent vehicle research has turned to co-operative systems, in which the traffic participants (vehicles, bicycles, pedestrians, etc.) communicate with each other and/or with the infrastructure.
Cooperative ITS is the term used to describe technology that allows vehicles to become connected to each other, and to the infrastructure and other parts of the transport network. In addition to what drivers can immediately see around them, and what vehicle sensors can detect, all parts of the transport system will increasingly be able to share information to improve decision making. Thus, this technology can improve road safety through avoiding collisions, but also assist in reducing congestion and improving traffic flows, and reduce environmental impacts. Once the basic technology is in place as a platform, an array of applications can be developed.
Cooperative ITS can greatly increase the quality and reliability of information available about vehicles, their location and the road environment. In the future, cars will know the location of road works and the switching phases of traffic lights ahead, and they will be able to react accordingly. This will make for safer and more convenient travel and faster arrival at the destination. On-board driver assistance, coupled with two-way communication between vehicles and between vehicles and road infrastructure, can help drivers to better control their vehicle and hence have positive effects in terms of safety and traffic efficiency. An important role in this plays the so-called road side units (RSUs). Vehicles can also function as sensors reporting weather and road conditions including incidents. In this way, cars can be used as information sources for high-quality information services.
RSUs are connected to the traffic control centre for management and control purposes. They broadcast, e.g., traffic light information (RSU vehicle) and traffic information from the traffic-control centre (TCC) via the RSU to the vehicles (TCC RSU vehicle). RSUs also collect vehicle probe data for the traffic control centre (vehicle RSU TCC). For reliable distribution of data, low-latency and high-capacity connections between RSUs (e.g. traffic lights, traffic signs, etc.) and the TCC are required. This type of application comes with rather tight end-to-end latency requirements for the communication service between RSU and TCC (10 ms), since relayed data needs to be processed in the TCC and, if needed, the results are forwarded to neighbouring RSUs. Also, the availability of the communication service has to be very high (99,9999%) in order to compete with existing wired technology and in order to justify the costly deployment and maintenance of RSUs. Furthermore, due to considerably large aggregation areas (see clause D.5.1), considerable amounts of data need to be backhauled to the TCC (up to 10 Mbit/s per RSU).
D.5.1 Service area and connection density
It is relatively hard to provide estimates for the service area dimension. One reason is that it depends on the placement of the base station relative to the RSUs. Also, the RSUs can, in principle, act as relay nodes for each other. The service area dimension stated in table 7.2.3.2-1 indicates the size of the typical data collection area of an RSU (2 km along a road), from which the minimum spacing of RSUs can be inferred. The connection density can be quite high in case data is relayed between RSUs, i.e. along the road (1000 km-2).
Annex E (informative):
(void)
Annex F (informative):
QoS Monitoring
F.1 QoS monitoring for assurance
This Clause discusses how QoS monitoring information can be used for assurance purposes. For background information on assurance see [19] and appendix A.3 in [20].
Assurance consists of four major steps (see Figure F.1-1 and [18]):
• Customer's QoS requirements
These state the level of quality required by the customer of a service. This information is divulged to the provider.
• Service provider's offerings of QoS (or planned/targeted QoS)
This is a statement of the level of quality expected to be offered to the customer by the service provider.
• QoS achieved/delivered
This is the level of quality achieved and delivered to the customer. Monitoring information is divulged to the customer.
• Customer rating of QoS
The customer can compare the QoS achieved by the provider with the QoS requirements (see above) and its own experience of the QoS. This is a crucial step for establishing assurance about the fulfillment of the customer's requirements.
Figure F.1-1: QoS assurance by use of QoS monitoring information
NOTE: This Figure is based on the trust model in reference [18].
The start time and the duration of the QoS monitoring is specified in the parameter observation time interval, which is exchanged between the customer, for instance an application consuming a communication service, and the provider (for instance a private 5G network providing a communication service). The observation time interval is the time interval during which a series of measurements is conducted. In the context of QoS monitoring, these are the measurements necessary for assessing the QoS of communication services, for instance the measurement of end-to-end latencies.
Examples of parameters to be monitored by the provider are given in annex C in reference [36].
F.2 Network Diagnostics
Network diagnostics helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient performance parameters that characterize the quality of the network connection. This includes data of the physical connection as well as of logical links and sub-networks. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems. Network diagnostic should be able to:
- be proactive (to early detect failures) and not only reactive (to deal with faults that have already occurred).
- accurately differentiate malfunctions/failures and evaluate their impact on the service/network.
- provide clear explanations about what happened.
- suggest corrective actions, and possibly perform them automatically.
Furthermore, specific connectivity information is also of interest as well as usage information (e.g. traffic load) of the node (e.g. RAN).
Network diagnostic information needs to be generated automatically and, in case of a hosted or virtual network deployment, be made available to the tenant of the network via a suitable API.
Annex G (informative):
Asset Tracking use cases
G.1 Asset Tracking
Every organisation owns assets (e.g. machines, medical devices, containers, pallets, trolleys). These assets are often not stationary: they are transported all over the world by different kinds of vehicles; and the assets are also moved inside various kinds of buildings.
The ownership of assets can change many times during the life-cycle of the asset as different stakeholders take possession of the assets and pass them on to other stakeholders along the supply chain and value chain.
So, many stakeholders want to track their assets anytime and anywhere (indoor & outdoor) in a global and multi-modal context (e.g. sea, air, road, rail).
The asset tracking topic implies more than just knowing the location of an asset. Asset tracking includes real time and/or time-stamped monitoring of several asset-related properties depending on the asset and its content (e.g. condition of the asset and changes, environmental factors – temperature, mechanical shock).
The 5G system provides the capability to better support asset tracking in all its aspects in particular in term of coverage (need to support full coverage: e.g. indoor / urban / rural / harsh environments / metallic obstructions on land, sea) with the support of terrestrial and non- terrestrial network as well as use of relays when necessary and in term of energy efficiency (15 to 20 years’ lifetime of an asset tracking device without changing the battery or the UE).
G.2 Battery life expectancy and message size to support example use cases for asset tracking
For asset tracking it is important to be able to have the asset on the field during a period corresponding to the life of the asset without changing the UE or the battery of the UE.
The battery life expectancy, message size and device density values required to support the potential opportunities in various asset tracking use cases are summarised in table G.2-1
Table G.2-1: Battery life expectancy and message size to support example use cases for asset tracking
Scenario
Battery Life
Expectancy
(note 1)
Typical Message size
Maximum
Message size
Typical Frequency
(number of messages per day)
Typical
Battery
Capacity
Device density
1
Containers
(note 2)
12 years
200 bytes
2500 bytes
24
21,6 Wh
1,4 devices / m3
2
Wagons
20 years
200 bytes
2500 bytes
24
36 Wh
0,3 devices / m2
3
Pallets
7 years
300 bytes
300 bytes
24
12 Wh
4 devices/ m2
NOTE 1: Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
NOTE 2: A large containership with a mix of 20 ft and 40 ft containers is assumed.
NOTE 3: All the values in this table are targeted values and not strict requirements.
Annex H (informative):
Interworking between Network Operators and Application Providers for localized services
This clause illustrates examples of scenarios applicable for interworking between hosting network operators (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers:
• Hosting network operator owns the 5G network which provides access and IP connectivity to serving UEs.
• Network operator owned application layer entities, e.g., including Service Hosting Environment, or IMS network.
• Application platforms in third party domain can be owned by third party application/service providers, or home/other network operators.
• The Application platforms could be application servers (e.g., Video on Demand Server, Cloud gaming server, etc.), 3rd party software development platforms, and third party/operator Service Hosting Environments.
The following figures show the collaborative relationship in three domains including network operators providing access and IP connectivity, network operators providing services via IMS/application platforms, and application/service providers providing services via application platforms or applications. The dashed line between visited hosting network operator and Home network operator is based on service level localized service agreement and the horizontal line represents the demarcation between the network operator domains and the 3rd party domain. In an operator network, the application layer entities can include IMS network, Application platforms, and API Gateway for third party applications developed using APIs (e.g., REST, GSMA OneAPI).
Figure H-1 provides the home operator owned/collaborative interworking scenarios where traffic is routed to home network operator and applications are delivered by the home operator via interworking agreements between network operators.
Figure H-1: Home Operator owned/collaborative interworking scenario Home Routed
NOTE: The other network operators and service/application operators in 3rd party domain provides collaborative services in application platforms to Home operator. The arrow solid line represents the traffics routed over domains within home operator network while the arrow dash lines represent the traffics routed over domains outside of home operator network.
Figure H-2 provides hosting network operator owned and collaborative interworking scenarios between visited hosting network operator and operators in 3rd party domains where traffic is routed to application from the hosting network to 1) hosting network owned application platforms, 2) collaborative home network owned application platforms, and 3) third parties via interworking agreements between visited hosting network operator and home/other network operators, and between hosting network operator and other application/service providers.
Figure H-2: Hosting Network Operator owned/collaborative interworking scenario Local Breakout
NOTE: The other network operators and application/service operators in 3rd party domain provides collaborative services in application platform to hosting network operator and/or home network operator. The arrow solid lines represent the traffics routed over domains within hosting network while the arrow dash lines represent the traffics routed over domains outside of hosting operator network.
Other interworking scenarios are not excluded.
Annex I (informative):
Indirect Network Sharing of NG-RAN Sharing
This annex clarifies scenarios applicable for Indirect Network Sharing between a Shared NG-RAN and the corresponding participating operator's core network as alternatives for operators who intend to deploy a NG Radio Access Network. Examples of such scenarios include wide-range coverage of rural areas, long-distance road coverage, compatibility with existing networks, service consistency, cooperation with diverse networks, considering different operators' strategies, commercial agreements, and specific rules/legislation in different countries.
Two or more operators have deployed or plan to deploy 5G access networks and core networks with MOCN. The challenge for the network operators is the maintenance generated by the interconnection (e.g., number of network interfaces) between the shared RAN and two or more core networks, especially for a large number of shared base stations. For these reasons, it is valuable to introduce a newly supported network sharing scenario as the operators' agreement.
In case of Indirect Network Sharing, the communication between the Shared NG-RAN and the Participating Operator’s core network happens via a number of inter-operator interfaces that are independent of the actual number of base stations at the Hosting NG-RAN Operator.
There is an agreement between all the operators to work together and build a shared network together cover the entire country, utilizing the different operator’s allocated spectrum appropriately in different parts of the coverage area (for example, Low Traffic Areas and High Traffic Areas). Multiple operators share one NG-RAN, but their 5GCs are independent. UEs access their subscribed PLMN services and/or subscribed services, including Hosted Services, provided by their participating operators respectively, when entering the Shared NG-RAN.
The following figures illustrate the example in which Indirect Network Sharing is realized via routing through the Hosting Operator’s core network.
- The Hosting NG-RAN Operator 1, as illustrated below, can share its NG-RAN with the participating operators with or without direct connections between the shared access and the core networks of the participating operators.
- The Participating NG-RAN Operators 2 and 3, using shared NG-RAN resources provided by the Hosting NG-RAN Operator, e.g., within a specific 5G frequency band or within a specific area, when the Shared NG-RAN does not have direct connections between the shared access and the core networks of the Participating NG-RAN Operators 2 and 3.
- The Participating NG-RAN Operator 4, using shared NG-RAN resources provided by the Hosting NG-RAN Operator, with direct connections between the shared NG-RAN and the core networks of the participating operator, is in a MOCN arrangement.
Figure I-1: Different options both direct and indirect connections between the Shared NG-RAN and the core networks of the participating operators.
Figure I-2: Indirect Network Sharing scenario involving core network of Hosting NG-RAN Operator between the Shared NG-RAN and the core networks of the participating operators.
The network sharing partners can set a specific sharing allocation model for the network sharing method they are using. The collection of charging information associated with the sharing method that the UE accesses with can be possible. It is also necessary to understand the charging information between the networks of both parties, e.g., the number of the users, and how long users using a certain shared network method will take. This information is also needed when users use the participating operator's hosted services they have subscribed to and their flexible charging via Shared NG-RAN.
Annex J (informative):
Store and Forward Satellite operation
The Store and Forward Satellite operation in a 5G system with satellite access is intended to provide some level of communication service for UEs under satellite coverage with intermittent/temporary satellite connectivity (e.g. when the satellite is not connected via a feeder link or via ISL to the ground network) for delay-tolerant communication service.
An example of "S&F Satellite operation" is illustrated in Figure J-1, in contrast to what could be considered the current assumption for the "normal/default Satellite operation" of a 5G system with satellite access.
As shown in Figure J-1:
• Under "normal/default Satellite operation" mode, signalling and data traffic exchange between a UE with satellite access and the remote ground network requires the service and feeder links to be active simultaneously, so that, at the time that the UE interacts over the service link with the satellite, there is a continuous end-to-end connectivity path between the UE, the satellite and the ground network.
- In contrast, under "S&F Satellite operation" mode, the end-to-end exchange of signalling/data traffic is now handled as a combination of two steps not concurrent in time (Step A and B in Figure J-1). In Step A, signalling/data exchange between the UE and the satellite takes place, without the satellite being simultaneously connected to the ground network (i.e. the satellite is able to operate the service link without an active feeder link connection). In Step B, connectivity between the satellite and the ground network is established so that communication between the satellite and the ground network can take place. So, the satellite moves from being connected to the UE in step A to being connected to the ground network in step B.
"Normal/default Satellite operation" mode
"S&F Satellite operation" mode
Figure J-1: Illustration of "normal/default operation" and "S&F Satellite operation" modes in a 5G system with satellite access.
The concept of "S&F" service is widely used in the fields of delay-tolerant networking and disruption-tolerant networking. In 3GPP context, a service that could be assimilated to an S&F service is SMS, for which there is no need to have an end-to-end connectivity between the end-points (e.g. an end-point can be a UE and the other an application server) but only between the end-points and the SMSC which acts as an intermediate node in charge of storing and relying.
The support of S&F Satellite operation is especially suited for the delivery of delay-tolerant/non-real-time IoT satellite services with NGSO satellites.
Annex K (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2016-12
SA#75
SP-170156
-
-
-
Skeleton
0.1.0
2017-03
SA#75
SP-170156
-
-
-
Agreements in SA1#75: S1-162342, S1-162305, S1-162480, S1-162345, S1-162481, S1-162471, S1-162313, S1-162347, S1-162486, S1-162349, S1-162546, S1-162322, S1-162323, S1-162450, S1-162547, S1-162548, S1-162549, S1-162492, S1-162550, S1-162520, S1-162485, S1-162517, S1-162551, S1-162505. And rapporteur's clean-up.
0.1.1
Agreements in SA1#76: S1-163412, S1-163445, S1-163446, S1-163256, S1-163070, S1-163415, S1-163258, S1-163293, S1-163260, S1-163416, S1-163296, S1-163264, S1-163265, S1-163266, S1-163267, S1-163268, S1-163297, S1-163298, S1-163417, S1-163418, S1-163299, S1-163274, S1-163275, S1-163277, S1-163278, S1-163280, S1-163448, S1-163421, S1-163029, S1-163112, S1-163285, S1-163286, S1-163287, S1-163422, S1-163289, S1-163382, S1-163132, and rapporteur's clean-up.
0.2.0
2017-03
SA#75
SP-170156
-
-
-
MCC Clean-up for presentation to SA for information
1.0.0
2017-03
SA#75
SP-170156
-
-
-
Agreements in SA1#76bis: S1-170198, S1-170199, S1-170335, S1-170201, S1-170008, S1-170207, S1-170106, S1-170338, S1-170092, S1-170339, S1-170212, S1-170340, S1-170341, S1-170014, S1-170217, S1-170218, S1-170219, S1-170131, S1-170342, S1-170314, S1-170224, S1-170206, S1-170090, S1-170225, S1-170226, S1-170343, S1-170228, S1-170229, S1-170230, S1-170232, S1-170122, S1-170042, S1-170234, S1-170345, S1-170364, S1-170236, S1-170347, S1-170220, S1-170239, S1-170243, S1-170209, S1-170365, S1-170245, S1-170048, and rapporteur's clean-up.
1.1.0
2017-02
SA1#77
Agreements in SA1#77: S1-171400, S1-171401, S1-171430, S1-171141, S1-171252, S1-171253, S1-171256, S1-171257, S1-171258, S1-171143, S1-171259, S1-171431, S1-171149, S1-171261, S1-171144, S1-171263, S1-171297, S1-171290, S1-171266, S1-171154, S1-171267, S1-171268, S1-171269, S1-171073, S1-171291, S1-171150, S1-171272, S1-171151, S1-171152, S1-171273, S1-171188, S1-171153, S1-171155, S1-171283, S1-171274, S1-171277, S1-171278, S1-171393, S1-171399, S1-171156, S1-171060, S1-171069, S1-171180, S1-171284, S1-171285, S1-171140, S1-171286, S1-171288, S1-171398, S1-171292, S1-171435, and rapporteur's clean-up.
1.2.0
2017-03
SA#75
SP-170156
-
-
-
Presentation for approval
2.0.0
2017-03
SA#75
-
Raised to v.15.0.0 following SA’s approval
15.0.0
Change history
TSG SA#
SA Doc.
SA1 Doc
Spec
CR
Rev
Rel
Cat
Subject/Comment
Old
New
WI
SP-76
SP-170443
S1-172288
22.261
0017
3
Rel-15
B
Addition of requirement on charging for the tenant of the slice
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172286
22.261
0016
3
Rel-15
B
Addition of requirement on maintaining user experience when UE performs handover
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172270
22.261
0022
2
Rel-15
F
Alignment of network slicing requirements
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172283
22.261
0011
3
Rel-15
F
Clarification on removal of network function
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172279
22.261
0021
3
Rel-15
F
Clarifications on network slicing
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172257
22.261
0020
1
Rel-15
F
Clean-up of requirements on network slice scaling
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172262
22.261
0025
1
Rel-15
F
Correction on '8 securtiy'
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172012
22.261
0001
Rel-15
F
CR to 22.261 Correction of the references for eV2X TS
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172285
22.261
0015
4
Rel-15
F
Efficient User Plane
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172280
22.261
0012
3
Rel-15
C
Exposure of QoE capability
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172256
22.261
0023
1
Rel-15
C
Maintaining a session whose priority changes in real time
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172261
22.261
0027
1
Rel-15
B
parallel transfer of multiple multicast/broadcast user services to a UE
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172277
22.261
0002
3
Rel-15
F
Replacement of 5G-RAN with NG-RAN
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172278
22.261
0006
2
Rel-15
F
Update service continuity definition
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172404
22.261
0007
4
Rel-15
C
Updates to network slice assignment in TS 22.261
15.0.0
15.1.0
SMARTER
SP-76
SP-170443
S1-172287
Request in CR 0031r1 to raise this spec to v.16.0.0 without CR0031r1 but with all other CRs
15.1.0
16.0.0
-
SP-77
SP-170699
S1-173544
22.261
0032
2
Rel-16
F
Requirement for audio video sync timing for audio-visual interaction.
16.0.0
16.1.0
TEI15
SP-77
SP-170692
S1-173459
22.261
0046
Rel-16
A
Correction on security requirement for relayed data protection
16.0.0
16.1.0
MONASTERY
SP-77
SP-170692
S1-173461
22.261
0048
Rel-16
A
Correction on regulatory requirement for all access technologies
16.0.0
16.1.0
MONASTERY
SP-77
SP-170692
S1-173463
22.261
0049
Rel-16
A
Update TS number of eV2X specification
16.0.0
16.1.0
MONASTERY
SP-77
SP-170692
S1-173549
22.261
0051
Rel-16
A
Clarification on access control requirement
16.0.0
16.1.0
SMARTER
SP-78
SP-170989
S1-174564
22.261
0068
1
Rel-16
F
Provide a more realistic KPI value for Virtual Reality
16.1.0
16.2.0
TEI16
SP-78
SP-170987
S1-174620
22.261
0069
Rel-16
A
Clarification of unified access control requirements
16.1.0
16.2.0
SMARTER
SP-79
SP-180129
S1-180598
22.261
0079
2
Rel-16
A
Clarification of 5GC requirements
16.2.0
16.3.0
SMARTER
SP-79
SP-180130
S1-180496
22.261
0077
1
Rel-16
A
Alignment of normative and descriptive clauses for Unified Access Control regarding operator defined Access Identities
16.2.0
16.3.0
SMARTER
SP-79
SP-180130
S1-180527
22.261
0088
Rel-16
A
Clarification of access Identity in unified access control
16.2.0
16.3.0
SMARTER
SP-79
SP-180130
S1-180529
22.261
0089
Rel-16
A
Clarification of Messaging in Unified Access Control (UAC)
16.2.0
16.3.0
SMARTER
SP-79
SP-180131
S1-180194
22.261
0085
Rel-16
A
Clarification of latency requirements
16.2.0
16.3.0
SMARTER
SP-79
SP-180213
fromS1-180611
22.261
0086
3
Rel-16
A
Support Legacy USIM in 5G
16.2.0
16.3.0
SMARTER
SP-79
SP-180224
fromS1-180503
22.261
0075
4
Rel-16
B
Support of Voice Service Continuity from 5G system to UTRAN CS
16.2.0
16.3.0
5GVSC
SP-79
SP-180140
S1-180624
22.261
0090
Rel-16
F
Release 15 alignment on the KPIs for URLLC
16.2.0
16.3.0
SMARTER_Ph2
SP-79
SP-180142
S1-180596
22.261
0081
2
Rel-16
B
5G Requirements to Prevent a Single Service (e.g. Emergency) from Monopolizing Network Resources
16.2.0
16.3.0
SMARTER
SP-80
SP-180312
S1-181389
22.261
0095
1
Rel-16
F
Positioning Part align with Rel-15 structure
16.3.0
16.4.0
SMARTER_Ph2
SP-80
SP-180312
S1-181740
22.261
0103
3
Rel-16
F
Clarifications on communication service availability and reliability
16.3.0
16.4.0
SMARTER_Ph2
SP-80
SP-180314
S1-181714
22.261
0097
3
Rel-16
B
QoS Monitoring
16.3.0
16.4.0
QoS_MON
SP-80
SP-180318
S1-181659
22.261
0253
Rel-16
B
Inter-RAT Mobility requirement for realtime service
16.3.0
16.4.0
MOBRT
SP-80
SP-180320
S1-181547
22.261
0101
3
Rel-16
B
Inclusion of ethernet transport services in TS 22.261
16.3.0
16.4.0
5GLAN
SP-80
SP-180325
S1-181671
22.261
0098
3
Rel-16
B
Policy delivery to UE for background data transfer
16.3.0
16.4.0
PDBDT
SP-80
SP-180464
S1-181719
22.261
0254
1
Rel-16
B
IMS and Network Slicing
16.3.0
16.4.0
enIMS
SP-81
SP-180752
S1-182662
22.261
0268
2
Rel-16
A
Clarification to Delay Tolerant
16.4.0
16.5.0
SMARTER
SP-81
SP-180752
S1-182674
22.261
0289
2
Rel-16
A
Clarify the method of configuring the UE to use Access Identity 1 and Access Identity 2
16.4.0
16.5.0
SMARTER
SP-81
SP-180752
S1-182758
22.261
0297
1
Rel-16
A
Support for use of licensed and unlicensed bands
16.4.0
16.5.0
SMARTER
SP-81
SP-180754
S1-182438
22.261
0283
1
Rel-16
A
Addition of new Access category for 'MO signalling on RRC level resulting from other than paging'- Mirror CR
16.4.0
16.5.0
TEI15
SP-81
SP-180788
-
22.261
0280
3
Rel-16
C
Updates to QoS Monitoring Description
16.4.0
16.5.0
QoS_MON
SP-81
SP-180789
-
22.261
0292
4
Rel-16
C
Addition of Informative Annex for QoS Monitoring
16.4.0
16.5.0
QoS_MON
SP-81
SP-180763
S1-182677
22.261
0278
3
Rel-16
B
Network service exposure requirements
16.4.0
16.5.0
cyberCAV
SP-81
SP-180763
S1-182685
22.261
0295
1
Rel-16
B
Ethernet support in TS 22.261
16.4.0
16.5.0
cyberCAV
SP-81
SP-180763
S1-182756
22.261
0286
3
Rel-16
B
Non-public network requirements
16.4.0
16.5.0
cyberCAV
SP-81
SP-180764
S1-182009
22.261
0255
Rel-16
B
Performance requirements for 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182016
22.261
0261
Rel-16
B
NG-RAN sharing for 5G satellite access network
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182385
22.261
0264
1
Rel-16
B
Satellite links between radio access network and core network
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182590
22.261
0263
2
Rel-16
B
Regulatory and charging aspects related to 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182602
22.261
0256
1
Rel-16
B
Multiple access requirements related to 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182605
22.261
0259
2
Rel-16
B
Efficient user plane aspects of 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182606
22.261
0260
2
Rel-16
B
Mobility management related requirements for 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182607
22.261
0262
1
Rel-16
B
QoS control aspects of 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182619
22.261
0265
1
Rel-16
B
Broadcast and multicast via satellite access networks
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182720
22.261
0258
2
Rel-16
B
Efficient delivery of content using 5G satellite access network
16.4.0
16.5.0
5GSAT
SP-81
SP-180764
S1-182725
22.261
0257
3
Rel-16
B
Connectivity aspects of 5G satellite access
16.4.0
16.5.0
5GSAT
SP-81
SP-180765
S1-182585
22.261
0269
2
Rel-16
B
KPIs for horizontal and vertical positioning service levels in clause 7.3.2
16.4.0
16.5.0
5G_HYPOS
SP-81
SP-180765
S1-182586
22.261
0270
2
Rel-16
B
Other KPIS for 5G positioning services
16.4.0
16.5.0
5G_HYPOS
SP-81
SP-180765
S1-182587
22.261
0271
2
Rel-16
B
Security requirements for 5G positioning services
16.4.0
16.5.0
5G_HYPOS
SP-81
SP-180765
S1-182588
22.261
0272
2
Rel-16
C
Update description (clause 7.3.1) of 5G positioning services
16.4.0
16.5.0
5G_HYPOS
SP-81
SP-180769
S1-182769
22.261
0273
3
Rel-16
F
Clarification for Inter-RAT Mobility requirement for realtime service
16.4.0
16.5.0
MOBRT
SP-81
SP-180770
S1-182395
22.261
0276
1
Rel-16
B
5GLAN Requirements
16.4.0
16.5.0
5GLAN
SP-81
SP-180770
S1-182702
22.261
0275
2
Rel-16
B
5GLAN charging requirements
16.4.0
16.5.0
5GLAN
SP-81
SP-180770
S1-182755
22.261
0274
3
Rel-16
B
5GLAN security requirements
16.4.0
16.5.0
5GLAN
SP-81
SP-180774
S1-182771
22.261
0281
2
Rel-16
B
Enhanced network slice requirements based on business role models
16.4.0
16.5.0
BRMNS
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2018-12
SP-82
SP-181007
0331
2
B
Functional requirements for 5G positioning services (clause 6)
16.6.0
2018-12
SP-82
SP-181007
0309
2
F
Termnology correction for positioning-related tables in 7.3.2
16.6.0
2018-12
SP-82
SP-181007
0308
3
D
Clarification on positioning-related descriptions in 7.3.1
16.6.0
2018-12
SP-82
SP-181007
0330
2
C
Clarification of requirement on energy per fix in clause 7.3.2.3
16.6.0
2018-12
SP-82
SP-181008
0340
C
Update of 5GLAN – Indirect Communication Mode
16.6.0
2018-12
SP-82
SP-181008
0319
2
F
Clarification on Ethernet transport services
16.6.0
2018-12
SP-82
SP-181008
0334
2
C
Addittion to definition on private communication
16.6.0
2018-12
SP-82
SP-181008
0335
2
C
Update of 5GLAN - General
16.6.0
2018-12
SP-82
SP-181008
0336
2
C
Update of 5G LAN - virtual network (5G LAN-VN).
16.6.0
2018-12
SP-82
SP-181008
0341
1
C
Update of 5GLAN – Service exposure
16.6.0
2018-12
SP-82
SP-181008
0337
3
C
Update of 5GLAN - Creation and management
16.6.0
2018-12
SP-82
SP-181008
0342
2
C
Update of 5GLAN – Security
16.6.0
2018-12
SP-82
SP-181008
0339
4
C
Update of 5GLAN – Discovery
16.6.0
2018-12
SP-82
SP-181008
0338
5
C
Update of 5GLAN – Privacy
16.6.0
2018-12
SP-82
SP-181008
0316
4
B
5GLAN requirements about enabling disabling UE from 5G-LAN based on location
16.6.0
2018-12
SP-82
SP-181128
0298
2
F
Corrections on requirements for SAT
16.6.0
2018-12
SP-82
SP-181011
0310
2
B
Enhanced network slice requirements based on business role models
16.6.0
2018-12
SP-82
SP-181011
0299
3
F
Correction to BRMNS requirements
16.6.0
2018-12
SP-82
SP-181005
0329
B
Introduction of cyberCAV
16.6.0
2018-12
SP-82
SP-181005
0311
2
B
Support for security requirements based on FS_CAV
16.6.0
2018-12
SP-82
SP-181005
0315
2
F
Replacing private network with non-public network
16.6.0
2018-12
SP-82
SP-181005
0333
2
B
cyberCAV - network interaction requirement for uninterrupted real-time video
16.6.0
2018-12
SP-82
SP-181129
0303
1
B
MSGin5G requirements on the 5G system
16.6.0
2018-12
SP-82
SP-181003
0343
2
C
Update to Annex F for Network Diagnostics
16.6.0
2018-12
SP-82
SP-180997
0348
1
F
Minor correction to URLLC clause
16.6.0
2018-12
SP-82
SP-181002
0313
F
Editorial correction in header
16.6.0
2018-12
SP-82
SP-181002
0312
2
F
Clause 7.2 alignment with other Rel-16 WIDs
16.6.0
2018-12
SP-82
SP-181002
0349
2
D
Move of KPIs for wireless RSU-TCC backhaul to 7.2.3
16.6.0
2019-03
SA#83
SP-190080
0354
F
Correction to the definition of communication service availability
16.7.0
2019-03
SA#83
SP-190080
0355
2
F
Clarifications of bulk authentication
16.7.0
2019-03
SA#83
SP-190082
0351
1
F
Clarification for 5GLAN requirements
16.7.0
2019-03
SA#83
SP-190080
0352
1
F
Update the Annex D in TS 22.261 to align the references
16.7.0
2019-03
SA#83
SP-190080
0353
1
D
Editorial clean-up of TS 22.261
16.7.0
2019-06
SA#84
SP-190302
0363
3
F
National or regional regulatory requirements for satellite access
16.8.0
2019-06
SA#84
SP-190298
0361
D
Editorial clean-up of TS 22.261
16.8.0
2019-06
SA#84
SP-190298
0359
2
D
Changing ‘authorized user’ to ‘authorized entity’ in requirements where an end user is not involved
16.8.0
2019-06
SA#84
SP-190298
0360
2
F
Abbreviations of TS 22.261
16.8.0
2019-06
SA#84
SP-190298
0362
2
F
Addition of selection Relay requirements to 22.261
16.8.0
2019-09
SA#85
SP-190803
0397
1
F
Modification of positioning service and high accuracy positioning
16.9.0
2019-09
SA#85
SP-190812
0392
3
C
Definition of absolute and relative positioning
16.9.0
2019-09
SA#85
SP-190798
0380
D
Editorial corrections of TS 22.261
16.9.0
2019-09
SA#85
SP-190798
0367
1
F
Clarification of dynamic policy control requirements
16.9.0
2019-09
SA#85
SP-190798
0368
2
F
Clarification of geographic constraint on a network slice
16.9.0
2019-09
SA#85
SP-190798
0383
2
F
Clarify requirements for bulk IoT operation and authentication
16.9.0
2019-09
SA#85
SP-190798
0399
3
F
Clarifications for KPIs on Low latency and high reliability scenarios
16.9.0
2019-09
SA#85
SP-190807
0371
1
B
Addition of security requirements for critical medical applications
17.0.0
2019-09
SA#85
SP-190807
0372
1
B
Addition of medical telemetry requirements
17.0.0
2019-09
SA#85
SP-190821
0381
2
B
Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode
17.0.0
2019-09
SA#85
SP-190817
0390
4
B
22.261 - Asset Tracking Description and Requirements
17.0.0
2019-09
SA#85
SP-190815
0365
2
B
Introduction of Minimization of Service Interruption (MINT)
17.0.0
2019-09
SA#85
SP-190817
0391
4
B
KPIs for Asset Tracking in 5G system
17.0.0
2019-09
SA#85
SP-190809
0382
2
B
General description for UAV aspects
17.0.0
2019-09
SA#85
SP-190812
0394
2
B
eCAV – further 5G service requirements for network operation and management
17.0.0
2019-09
SA#85
SP-190805
0377
1
B
Service hosting environment aspects of interactive service
17.0.0
2019-09
SA#85
SP-190805
0375
3
B
Performance requirements of interactive service
17.0.0
2019-09
SA#85
SP-190808
0386
1
B
Connectivity models description section updated.
17.0.0
2019-09
SA#85
SP-190808
0387
1
B
Connectivity models new functional requirements
17.0.0
2019-09
SA#85
SP-190808
0388
1
B
KPIs for UE to network relaying in 5G system
17.0.0
2019-10
-
-
-
-
-
Adding missing carriage return between the last sentence of clause 6.31.2.1 and clause 6.31.2.2, also at the end of 6.31.2.2 before 6.31.2.3
17.0.1
2019-12
SA#86
SP-191010
0418
1
A
UAC for NB-IOT
17.1.0
2019-12
SA#86
SP-191010
0432
1
A
Clarifications and updates on the description of positioning use cases in Annex B and Annex E
17.1.0
2019-12
SA#86
SP-191012
0411
1
A
Unified Access Control for IMS registration related signalling
17.1.0
2019-12
SA#86
SP-191014
0403
4
B
CR for group communication in 5G system
17.1.0
2019-12
SA#86
SP-191014
0405
2
B
Tethered VR requirement for 5G
17.1.0
2019-12
SA#86
SP-191014
0413
2
F
Update of NCIS KPI requirements
17.1.0
2019-12
SA#86
SP-191016
0420
3
B
Addition of AVProd introduction in 22.261
17.1.0
2019-12
SA#86
SP-191020
0426
C
Updating integrity protection requirement based on consolidated CMED requirements
17.1.0
2019-12
SA#86
SP-191020
0416
2
B
Addition of general section 6.x for CMED
17.1.0
2019-12
SA#86
SP-191023
0422
1
B
Establishment of an indirect network connection
17.1.0
2019-12
SA#86
SP-191023
0421
3
C
Clarification of requirements
17.1.0
2019-12
SA#86
SP-191028
0430
3
B
Operator provided end-to-end security for factory networks
17.1.0
2019-12
SA#86
SP-191032
0378
4
B
On Access control for MINT
17.1.0
2019-12
SA#86
SP-191034
0384
7
B
Broadcast / multicast requirements supporting Mission Critical Services in 5G
17.1.0
2019-12
SA#86
SP-191035
0425
2
B
Supporting IMS emergency for NPN
17.1.0
2019-12
SA#86
SP-191036
0412
1
F
Clarify requirements for bulk IoT authentication
17.1.0
2019-12
SA#86
SP-191036
0423
2
D
Editorial changes and corrections
17.1.0
2019-12
SA#86
SP-191036
0419
2
C
VR requirement for 5G
17.1.0
2020-03
SA#87
SP-200122
0436
1
A
Manual CAG selection clarification
17.2.0
2020-07
SA#88e
SP-200563
0454
A
correction to access control for NB-IoT
17.3.0
2020-07
SA#88e
SP-200565
0442
1
D
Addition of generic 5G requirements for VIAPA
17.3.0
2020-07
SA#88e
SP-200569
0428
4
B
Performance requirements for satellite access
17.3.0
2020-09
SA#89e
SP-200784
0456
1
A
Addition of Human Readable Network Name
17.4.0
2020-09
SA#89e
SP-200889
0462
2
D
Quality improvement of TS 22.261 (R17) – editorial modifications
17.4.0
2020-09
SA#89e
SP-200818
0472
1
B
Addition of requirements on Subscriber-aware Northbound API access
18.0.0
2020-12
SA#90e
SP-201029
482
1
A
Quality improvement of TS 22.261
18.1.0
2020-12
SA#90e
SP-201029
480
1
A
Correction of Access Identities Table in clause 6.22.2.2
18.1.0
2020-12
SA#90e
SP-201025
489
1
A
Clarification of a steering of roaming requirement
18.1.0
2020-12
SA#90e
SP-201140
0478
3
B
Service requirements for enhancing service function chaining support by 5G network
18.1.0
2021-01
-
CR 478r3 was meant to add one clause and its subclauses under section 6 and not to add a new section 10. This is corrected here.
18.1.1
2021-03
SA#91e
SP-210199
504
1
C
Clarification to KPIs for a 5G system with satellite access
18.2.0
2021-03
SA#91e
SP-210215
496
1
B
update of CR of Addition of requirements on Data integrity in 5G
18.2.0
2021-03
SA#91e
SP-210198
500
1
A
Modification of requirements for network slice constraints
18.2.0
2021-06
SA#92e
SP-210498
0528
1
A
Clarification for Congestion Avoidance for MINT
18.3.0
2021-06
SA#92e
SP-210502
0524
1
A
Editorial correction for network capability exposure and abbreviation
18.3.0
2021-06
SA#92e
SP-210564
531
A
Quality improvement - clarification of QoS-monitoring requirement
18.3.0
2021-06
SA#92e
SP-210564
530
1
A
Quality improvement - updating the definition of communication service availability
18.3.0
2021-06
SA#92e
SP-210565
508
1
D
Quality improvement - update of Annex C
18.3.0
2021-06
SA#92e
SP-210565
512
1
D
Quality improvement - update of annex D
18.3.0
2021-06
SA#92e
SP-210565
513
1
D
Quality improvement - update of clause F.1
18.3.0
2021-06
SA#92e
SP-210565
514
1
D
Quality improvement - voiding annex A and B
18.3.0
2021-06
SA#92e
SP-210516
0505
1
B
New service requirements for EASNS
18.3.0
2021-06
SA#92e
SP-210517
0507
1
B
5G timing resiliency
18.3.0
2021-06
SA#92e
SP-210518
0506
1
B
Adding High-level and Performance Requirements for Ranging
18.3.0
2021-06
SA#92e
SP-210524
0515
C
Clarification of LPHAP requirements
18.3.0
2021-06
SA#92e
SP-210524
0526
D
Alignment of positioning power consumption aspects between 22.261 and 22.104
18.3.0
2021-06
SA#92e
SP-210529
0525
1
B
Requirements for satellite backhaul
18.3.0
2021-09
SA#93e
SP-211039
0518
3
F
Clarification of NPN in 22.261
18.4.0
2021-09
SA#93e
SP-211069
0519
2
B
Update to KPIs to 5G system with satellite access for support control and/or video surveillance
18.4.0
2021-09
SA#93e
SP-211063
0533
1
B
5G LAN related rquirements from FS_Resident (Pirates)
18.4.0
2021-09
SA#93e
SP-211063
0534
C
Application Server related requirements from FS_Resident (pirates)
18.4.0
2021-09
SA#93e
SP-211063
0535
1
B
Pirates definitions and abbreviations
18.4.0
2021-09
SA#93e
SP-211063
0536
1
B
Pirates general introduction
18.4.0
2021-09
SA#93e
SP-211063
0539
1
B
Pirates requirements
18.4.0
2021-09
SA#93e
SP-211038
0541
1
A
EXPOSE: editorial improvement of a QoS monitoring requirement
18.4.0
2021-09
SA#93e
SP-211071
0542
1
B
EXPOSE: addition to QoS monitoring requirements
18.4.0
2021-09
SA#93e
SP-211071
0543
1
F
EXPOSE: correction of a QoS monitoring requirement
18.4.0
2021-09
SA#93e
SP-211071
0544
1
B
EXPOSE: addition of position accuracy
18.4.0
2021-09
SA#93e
SP-211039
0546
1
D
Miscellaneous corrections from CR implementation
18.4.0
2021-09
SA#93e
SP-211070
0547
1
B
Introduction of Smart Energy Infrastructure Requirements
18.4.0
2021-09
SA#93e
SP-211060
0549
1
B
Evolution of IMS Multimedia Telephony Service
18.4.0
2021-09
SA#93e
SP-211070
0550
1
B
Introduce of Smart Grid service
18.4.0
2021-09
SA#93e
SP-211062
0551
1
B
Adding requirements for AMMT
18.4.0
2021-09
SA#93e
SP-211062
0552
1
B
CR22.261v18.3.0 Adding performance requirements for AMMT
18.4.0
2021-09
SA#93e
SP-211030
0557
1
A
Correction to Reliabilty definition
18.4.0
2021-09
SA#93e
SP-211032
0559
1
A
Removal of user intervention on services exempted from release due to SOR
18.4.0
2021-09
SA#93e
SP-211064
0560
1
B
Introducing PALS Normative Requirements
18.4.0
2021-09
SA#93e
SP-211039
0564
1
B
Support multiple non-public networks access and corresponding simultaneous services for a UE
18.4.0
2021-09
SA#93e
SP-211070
0565
B
Addition of requirements for Confidentiality in 5GS (SEI)
18.4.0
2021-09
SA#93e
SP-211096
0567
1
D
Editorial corrections for references, abbreviations and clauses 6.36, 8.10 and 9.3
18.4.0
2021-09
SA#93e
SP-211066
0568
1
B
Introduction of VMR requirements
18.4.0
2021-09
SA#93e
SP-211096
0571
1
A
Correction of 'air interface' terminology
18.4.0
2021-09
SA#93e
SP-211096
0576
1
A
UAS terminology alignment
18.4.0
2021-09
SA#93e
SP-211070
0577
2
B
Inclusion of Smart Energy Infrastructure Requirements
18.4.0
2021-12
SP-94
SP-211495
0582
A
Editorial corrections to clause 6.23.2 (QoS monitoring)
18.5.0
2021-12
SP-94
SP-211488
0583
1
F
Correction of network condition change per UE
18.5.0
2021-12
SP-94
SP-211500
0587
1
A
Clarification of NPN in 22.261
18.5.0
2021-12
SP-94
SP-211493
0588
F
Adding Informative Annex for PALS
18.5.0
2021-12
SP-94
SP-211497
0590
1
D
Alignment with new added smart grid
18.5.0
2021-12
SP-94
SP-211501
0593
1
A
Clarification to NPN requirements on USIM and multiple subscriptions
18.5.0
2021-12
SP-94
SP-211488
0597
1
B
Adding requirement of FL for AMMT
18.5.0
2021-12
SP-94
SP-211488
0598
1
F
Adding definition of terminology for AMMT
18.5.0
2021-12
SP-94
SP-211494
0599
1
B
Update the general section of PIRates
18.5.0
2021-12
SP-94
SP-211494
0600
1
B
Update the gateways section of PIRates
18.5.0
2021-12
SP-94
SP-211494
0602
1
C
Update the discovery section of PIRates
18.5.0
2021-12
SP-94
SP-211494
0604
1
C
Update the creation and management section of PIRates
18.5.0
2021-12
SP-94
SP-211494
0605
1
F
Correction on the definition of PIN and PIN Element
18.5.0
2021-12
SP-94
SP-211494
0607
F
Correction for 5G-RG
18.5.0
2021-12
SP-94
SP-211494
0610
1
B
Pirates general introduction missing background text
18.5.0
2021-12
SP-94
SP-211498
0611
2
B
TACMM CR Introduction of text for Tactile and multi-modal communication service
18.5.0
2021-12
SP-94
SP-211493
0614
1
F
Clarification of Service Providers for PALS
18.5.0
2021-12
SP-94
SP-211502
0619
F
CR adding NPN clarification plus editorials
18.5.0
2021-12
SP-94
SP-211494
0622
2
B
Adding leftover PIN requirement to normative spec
18.5.0
2021-12
SP-94
SP-211494
0623
2
F
Replacing undefined term PIN User
18.5.0
2021-12
SP-94
SP-211494
0624
2
F
Clarifying Lawful Intercept requirements
18.5.0
2021-12
SP-94
SP-211500
0626
A
NPN support for positioning service requirement
18.5.0
2021-12
SP-94
SP-211493
0627
1
B
Addition of PALs requirement for manual selection
18.5.0
2021-12
SP-94
SP-211499
0628
1
A
Clarification of NPN in 22.261
18.5.0
2021-12
SP-94
SP-211488
0629
B
Update to charging requirements for AMMT
18.5.0
2022-03
SP#95e
SP-220080
0633
1
F
Clarification of KPI in TS22.261 clause 7.10 for AMMT use case
18.6.0
2022-03
SP#95e
SP-220080
0634
1
F
Clarification of 5GC assistance for FL member selection
18.6.0
2022-03
SP#95e
SP-220080
0630
1
F
Clarification of terminology for localized services
18.6.0
2022-03
SP#95e
SP-220080
0631
1
F
Correction to CPN Requirements
18.6.0
2022-03
SP#95e
SP-220081
0636
A
Clarification of SoR requirements
18.6.0
2022-03
SP#95e
SP-220082
0632
1
F
Update the use of may and can for quality improvement
18.6.0
2022-06
-
-
-
-
-
Carriage return that was missing just before 6.41.1 has been introduced
18.6.1
2022-09
SA#97
SP-220932
649
1
A
Add requirements on maximum capacity of network slicing
18.7.0
2022-09
SA#97
SP-220933
653
1
D
Clean-up of the references for quality improvement
18.7.0
2022-09
SA#97
SP-220942
639
3
B
Interworking of Non-3GPP Digital Terrestrial Broadcast Networks with 5GS Multicast/Broadcast Services
19.0.0
2022-09
SA#97
SP-220944
651
2
B
Add requirements on multi-path relay UEs
19.0.0
2022-09
SA#97
SP-221001
645
2
B
Add requirements on Minimization of Service Interruption During Core Network Failure
19.0.0
2022-12
SA#98
SP-221259
0665
1
A
Editorial Corrections to TS 22.261 on PALS
19.1.0
2022-12
SA#98
SP-221259
0666
1
D
Editorial Corrections to Annexes in TS 22.261
19.1.0
2022-12
SA#98
SP-221264
0647
5
B
New requirements for QoS monitoring
19.1.0
2023-03
SA#99
SP-230234
0677
3
B
Supporting UE Mobility for XR service
19.2.0
2023-03
SA#99
SP-230232
0668
3
B
Roaming Value-Added Services
19.2.0
2023-03
SA#99
SP-230216
0674
1
A
Corrections to PALS
19.2.0
2023-03
SA#99
SP-230215
0670
1
A
Miscellaneous corrections to Ranging
19.2.0
2023-06
SA#100
SP-230527
0685
2
A
Clarification on AI-ML KPIs
19.3.0
2023-06
SA#100
SP-230533
0682
2
B
Add Indirect Network Sharing to TS 22.261
19.3.0
2023-06
SA#100
SP-230533
0684
1
B
Add definitions for Indirect Network Sharing
19.3.0
2023-06
SA#100
SP-230522
0681
4
B
UE-to-UE Multi-hop relay requirements for mission critical communications
19.3.0
2023-06
SA#100
SP-230524
0688
4
B
Add requirements on NPN security considerations
19.3.0
2023-09
SA#101
SP-231024
0713
1
B
Adding functional requirements of AIML-Ph2
19.4.0
2023-09
SA#101
SP-231024
0714
1
B
Adding KPIs for AIML-Ph2
19.4.0
2023-09
SA#101
SP-231020
0696
5
B
General and charging requirements to NetShare
19.4.0
2023-09
SA#101
SP-231026
0700
1
B
Add Security and Charging aspects for Satellite in TS 22.261
19.4.0
2023-09
SA#101
SP-231026
0697
2
B
New section for Satellite access in 22261
19.4.0
2023-09
SA#101
SP-231038
0716
2
B
Additional requirements for selecting and/or changing the user plane paths based on the usage information of the Service Hosting Environment
19.4.0
2023-09
SA#101
SP-231030
0717
3
B
Adding energy efficiency as service criteria with agreed consolidation
19.4.0
2023-09
SA#101
SP-231036
0709
3
B
Add requirements on supporting local traffic routing for UEs with multiple accesses to 5G
19.4.0
2023-09
SA#101
SP-231039
0719
3
B
Supporting UE Mobility for XR service
19.4.0
2023-09
SA#101
SP-231174
728
2
A
Roaming service providers enablement in 5G
19.4.0
2023-12
SA#102
SP-231394
0754
1
A
Correction of requirement in subclause 6.3 (Multiple access technologies)
19.5.0
2023-12
SA#102
SP-231397
0735
2
B
General description for 5G wireless sensing service
19.5.0
2023-12
SA#102
SP-231401
0748
1
D
CR on Indirect Network Sharing cleanup
19.5.0
2023-12
SA#102
SP-231401
0738
2
B
KPI Requirements for UE to UE Relay
19.5.0
2023-12
SA#102
SP-231402
0712
3
B
TS.22.261_Adding clause for Ambient IoT
19.5.0
2023-12
SA#102
SP-231406
0755
2
B
Introduction of Mobile Metaverse Services
19.5.0
2023-12
SA#102
SP-231408
0745
2
F
TS.22.261_Updating of functional requirements
19.5.0
2023-12
SA#102
SP-231409
0747
3
B
Add remaining consolidated requirements of Satellite Access
19.5.0
2023-12
SA#102
SP-231411
0739
3
B
DualSteer Normative requirements
19.5.0
2023-12
SA#102
SP-231414
0742
1
F
Update EE related terms in section 3.1
19.5.0
2023-12
SA#102
SP-231414
0741
2
B
Energy Efficiency as a Service Criteria requirements update with newly agreed CPRs
19.5.0
2023-12
SA#102
SP-231414
0740
3
B
Energy Efficiency as a Service Criteria requirements update with agreed CPRs
19.5.0
2024-03
SA#103
SP-240202
0781
C
Support for Multiple Spanning Tree Protocol
19.6.0
2024-03
SA#103
SP-240202
0761
1
F
Correction of AI/ML KPI requirements for direct network connection
19.6.0
2024-03
SA#103
SP-240202
0762
1
F
TS.22.261_Updating of functional requirements
19.6.0
2024-03
SA#103
SP-240197
0776
2
B
Add requirements for Interconnect of SNPN in 22.261
19.6.0
2024-03
SA#103
SP-240202
0767
4
D
DualSteer requirement updating
19.6.0
2024-03
SA#103
SP-240202
0763
3
F
Exemption of Priority Services (e.g., MPS) from Energy Limitation Controls
19.6.0
2024-06
SA#104
SP-240785
0785
D
removing duplicated reference to TS22.369 (Ambient IoT) in TS 22.261
19.7.0
2024-06
SA#104
SP-240794
0791
2
B
Monitoring of signalling traffic in 5G
19.7.0
2024-09
SA#105
SP-241145
0792
2
F
Clarifications on IMS provision to disaster inbound roamers
19.8.0
2024-09
SA#105
SP-241145
0794
3
F
Correction to the requirements of Indirect Network Sharing
19.8.0
2024-09
SA#105
SP-241145
0796
1
D
Addressing editorial errors
19.8.0
2024-09
SA#105
SP-241142
0795
2
B
New requirements for satellite access network sharing via Indirect Network Sharing
20.0.0
2024-09
SA#105
SP-241415
0797
8
B
Combined QoS configuration and monitoring
20.0.0
2024-09
SA#105
SP-241142
0801
2
B
22.261CR New features of NetShare for Disaster Condition
20.0.0
2024-09
SA#105
SP-241142
0804
3
B
Requirements on legacy residential gateway supporting 5G LAN-type service
20.0.0
2024-09
SA#105
SP-241142
0805
4
B
Clarifying the support of eRG
20.0.0
2024-09
SA#105
SP-241142
0806
4
B
Add new service requirements for exposing VN information and capability to authorized third party
20.0.0
2024-12
SA#106
SP-241765
0814
2
C
Additional requirements on QoS management for VMR backhaul change
20.1.0
2024-12
SA#106
SP-241760
0821
2
A
Correction on the propagation delay via satellite
20.1.0
2025-03
SA#107
SP-250268
0829
A
Support for diverse device types
20.2.0
2025-03
SA#107
SP-250301
0825
1
B
Resilient Notification Service for 5G Satellite access.
20.2.0
2025-03
SA#107
SP-250301
0835
1
B
Broadcast Service with satellite access for unregistered UEs
20.2.0
2025-03
SA#107
SP-250301
0832
2
B
Addition of normative input based on FS_EnergyServ_Ph2
20.2.0
2025-03
SA#107
SP-250301
0830
2
C
Requirements for enhanced positioning using satellite access
20.2.0
2025-03
SA#107
SP-250301
0817
2
B
Enhancements for IMS-based GEO Global Call Services
20.2.0
2025-06
SA#108
SP-250625
0844
1
A
Correct the definition of 5G LAN-type service
20.3.0
2025-06
SA#108
SP-250626
0836
1
C
Further consolidation of requirements on service adjustments based on energy-related characteristics
20.3.0
2025-06
SA#108
SP-250626
0839
1
B
Addition of normative inputs based on FS_5GSAT_Ph4
20.3.0
2025-09
SA#109
SP-251234
0851
3
A
Ordering Charging Requirements in TS 22.261
20.4.0
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
1 Scope
|
This Technical Specification defines the stage one description of the Public Warning System (PWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
The scope of this TS covers the core requirements for the PWS that are sufficient to provide a complete service. This TS also covers subsystem additional requirements for the Earthquake and Tsunami Warning System (ETWS), the Commercial Mobile Alert System (CMAS), EU-ALERT, and Korean Public Alert System (KPAS).
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of PWS, ETWS, and or CMAS, EU-ALERT, and KPAS. PWS, ETWS, CMAS, EU-ALERT, and KPAS deployment depends on operator decision or national regulations.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
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] FCC 08-99: "Federal Communications Commission First Report and Order In the Matter of The Commercial Mobile Alert System"; April 9, 2008.
[2] FCC 08-164: "Federal Communications Commission Second Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System"; July 8, 2008.
[3] FCC 08-184: "Federal Communications Commission Third Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System"; August 7, 2008.
[4] J-STD-100: "Joint ATIS/TIA-CMAS Mobile Device Behavior Specification"; January 30, 2009.
[5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[6] ETSI TS 102 900: "European Public Warning System (EU-ALERT) using the Cell Broadcast Service".
[7] TTA TTAK.KO-06.0263:"Requirements and Message Format for Korean Public Alert System over Mobile Network".
[8] FCC 16-127, Federal Communications Commission Report and Order and Further Notice of Proposed Rulemaking In the Matter of Wireless Emergency Alerts Amendments to Part 11 of the Commission’s Rules Regarding the Emergency Alert System; September 29, 2016.
[9] 3GPP TS 23.038; "Alphabets and language-specific information"
[10] FCC 18-4, Federal Communications Commission Second Report and Order and Second Order on Reconsideration In the Matter of Wireless Emergency Alerts and Amendments to Part 11 of the Commission’s Rules Regarding the Emergency Alert System; January 30, 2018
[11] 3GPP TS 22.071: “Location Services (LCS); Service description; Stage 1”
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
3 Definitions and abbreviations
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5].
Commercial Mobile Alert System (aka, Wireless Emergency Alert): Public Warning System that delivers Warning Notifications provided by Warning Notification Providers to CMAS capable PWS-UEs. CMAS defines the following classes of Warning Notifications: Presidential, Imminent Threat, Public Safety, Child Abduction Emergency, and State/Local WEA Test.
Earthquake and Tsunami Warning System: Public Warning System that delivers Warning Notifications specific to Earthquake and Tsunami provided by Warning Notification Providers to the UEs which have the capability of receiving Primary and Secondary Warning Notifications within Notification Areas through the 3GPP network
Notification Area: area where Warning Notifications are broadcast. This is an area that closely approximates the geographical information provided by the Warning Notification Provider
PWS-UE: User Equipment (UE) which has the capability of receiving Warning Notifications within Notification Areas through the 3GPP network and conforms to the behaviour specific to the PWS service such as dedicated alerting indication and display of the Warning Notification upon reception
ePWS-UE: User Equipment (UE) that supports the ePWS functionality
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [5]
CBC Cell Broadcast Centre
CBE Cell Broadcast Entity
CBS Cell Broadcast Service
CMAS Commercial Mobile Alert System
EOC Emergency Operations Center
ETWS Earthquake and Tsunami Warning System
KPAS Korean Public Alert System
PWS Public Warning System
WEA Wireless Emergency Alert
ePWS enhancements of Public Warning System
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4 General PWS Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.1 Background
|
Recently there has been an interest to ensure that the public has the capability to receive timely and accurate alerts, warnings and critical information regarding disasters and other emergencies irrespective of what communications technologies they use. As has been learned from disasters such as earthquakes, tsunamis, hurricanes and wild fires; such a capability is essential to enable the public to take appropriate action to protect their families and themselves from serious injury, or loss of life or property.
This interest to enhance the reliability, resiliency, and security of Warning Notifications to the public by providing a mechanism to distribute Warning Notifications over 3GPP systems is the impetus for this Public Warning System Technical Specification.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.2 High level general requirements for Warning Notification delivery
|
The following list gives the high level general requirements for Warning Notification delivery:
- PWS shall be able to broadcast Warning Notifications to multiple users simultaneously with no acknowledgement required.
- PWS shall be able to support concurrent broadcast of multiple Warning Notifications.
- Warning Notifications shall be broadcast to a Notification Area which is based on the geographical information as specified by the Warning Notification Provider.
- PWS capable UEs (PWS-UE) in idle mode shall be capable of receiving broadcasted Warning Notifications.
NOTE 1: A bandwidth reduced low complexity UE, an NB-IoT UE or a UE supporting eDRX does not necessarily meet all requirements for PWS, including ETWS, CMAS, EU-Alert and KPAS
- PWS shall only be required to broadcast Warning Notifications in languages as prescribed by regulatory requirements.
- Warning Notifications are processed by PWS on a first in, first out basis, subject to regulatory requirements.
- Reception and presentation of Warning Notifications to the user shall not pre-empt an active voice or data session.
- Warning Notifications shall be limited to those emergencies where life or property is at imminent risk, and some responsive action should be taken.
NOTE 2: This requirement does not prohibit the use of the operator’s network (i.e. broadcast technology) implemented for Warning Notifications to be used for commercial services.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.3 Warning Notification Content
|
PWS shall not modify or translate the Warning Notification content specified by the Warning Notification Provider.
It is expected that Warning Notifications would likely include the following five elements:
- Event Description
- Area Affected
- Recommended Action
- Expiration Time (with time zone)
- Sending Agency
Additional elements may be present, based on regulatory requirements.
There is a concern that URLs or telephone numbers in a Warning Notification could exacerbate wireless network congestion at a time when network traffic is already dramatically increasing as individuals contact police, fire, and rescue personnel, as well as their loved ones. Therefore, Warning Notifications should not contain anything that would drive immediate and debilitating traffic loads into the PLMN (i.e., URLs or dialable numbers) unless required by regional regulation.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.4 Granularity of the distribution
|
Requirements for the granularity of the distribution of Warning Notifications include:
- Based on the geographical information indicated by the Warning Notification Provider, it shall be possible for the PLMN operators to define the Notification Area based on their network configuration of the area coverage such as distribution of cells, Node Bs, RNCs, etc.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.5 Support of Warning Notification Providers
|
PLMN operators shall, at a minimum, be able to support the following functionalities through interaction with Warning Notification Providers:
- Activation of Warning Notification delivery
It shall be possible for multiple Warning Notifications to be activated concurrently from one or more Warning Notification Providers.
- Cancellation of Warning Notification delivery
A cancellation is a command from the Warning Notification Provider to stop dissemination of a specific Warning Notification.
- Updating of Warning Notification delivery
Warning Notification Providers update a previous Warning Notification to provide new instructions/information to the PLMN operator. When the Warning Notification Provider updates a previous Warning Notification they provide an identifier that allows the PLMN operator to associate the updated Warning Notification with the previous Warning Notification.
Additional functionality may be required based on regulatory or operator policy requirements.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.6 PWS-UE Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.6.1 General Requirements
|
PWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
There shall be no requirement for language translation in the operator’s network or the UE.
It shall be possible for the Warning Notification to be displayed on the PWS-UE upon reception and without any user interaction.
It shall be possible for users to configure the behavior of a PWS-UE with regard to Warning Notification alerting and should allow at least volume adjustment.
The PWS-UE shall support a dedicated alerting indication (audio attention signal and a dedicated vibration cadence) and be distinct from any other device alerts and restricted to use for Warning Notification purposes. The User Interface shall support the ability for the user to suppress the dedicated audio attention signal and/or the dedicated vibration cadence when a Warning Notification is received.
The alerting indication for a specific Warning Notification shall continue until suppressed by users' manual operation (e.g. by pushing keys). The frequency and duration of the continued alerting indication is mobile device implementation specific. This shall not suppress the alerting indication for subsequent Warning Notifications.
The PWS-UE shall automatically suppress duplicate notifications. A duplicate is a repetition of a previous notification as determined by unique parameters.
The PWS-UE shall not support any capabilities to forward received Warning Notifications, to reply to received Warning Notifications, or to copy and paste the content of Warning Notifications.
PWS-UEs should have the ability to present previously displayed Warning Notifications if requested by the user.
- PWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.6.2 Support of non-Warning Notification capable UEs
|
Support of non-Warning Notification capable UEs is subject to regulatory requirements and/or operator's policy.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.6.3 Battery Life of PWS-UE
|
Battery life of the PWS-UE shall not be significantly reduced by PWS.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.6.4 Enabling and disabling of Warning Notifications
|
The PWS-UE shall be configured to receive all Warning Notifications.
It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select PWS-UE enabling/disabling options via the User Interface to disable, or later enable, the PWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
Where regional or national regulations allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications in the HPLMN and in PLMNs equivalent to it, by means of a setting on the USIM.
Where regional or national regulations pertaining to a VPLMN allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications that are received whilst in this VPLMN, by means of a setting on the USIM, when the integrity of Warning Notifications in this VPLMN is known by the HPLMN operator to be compromised. This setting need not distinguish VPLMNs.
Subject to regional or national regulations, a PWS-UE in limited service state shall be able to receive and display Warning Notifications.
NOTE 1: Non-existing or empty USIM data files results in all Warning Notifications being presented to the PWS application.
NOTE 2: (void).
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.7 Roaming Requirements
|
It shall be possible for PWS-UEs that are enabled for Warning Notifications in the HPLMN to receive Warning Notifications from the VPLMN supporting PWS when roaming.
A PWS-UE that does not support the PWS requirements of the VPLMN’s PWS service may not receive Warning Notifications from that VPLMN.
Note: See section 4.9 for roaming impacts to PWS due to regional regulatory requirements.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.8 Security Requirements
|
Security requirements are as follows:
- PWS shall only broadcast Warning Notifications that come from an authenticated authorized source.
The following requirements only apply when not roaming internationally:
- When required by regional or national regulations, the integrity of the Warning Notification shall be protected. If no such regulatory requirement exists, there shall be no integrity protection of Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
- When required by regional or national regulations, the PWS shall protect against false Warning Notification messages. If no such regulatory requirement exists, there shall be no protection against false Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
Note 1: These requirements are subject to regulatory policies.
NOTE 2: The authentication and authorisation of the source are outside the scope of 3GPP Specifications.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
4.9 Regulatory Requirements
|
The PWS offered by a PLMN may be subject to PWS regional regulatory requirements and thus, the PWS offered may differ from PLMN to PLMN as well as from region to region within a PLMN.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5 Earthquake and Tsunami Warning System
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5.1 Background
|
Warning Notifications are expected to be delivered to the users while satisfying the following requirements:
- Quick Warning Notification delivery after the occurrence of Earthquake or Tsunami.
Earthquake and Tsunami propagate very fast. The duration time between the actual occurrence of the disaster and its arrival is very short. The order of the duration time is around seconds or minutes at most. Therefore the Warning Notifications shall be delivered quickly to the users in the emergency impacted area so that they could take any actions to escape from danger.
- Accurate Warning Notification delivery.
Warning Notification delivery urges the users to take the actions such as evacuation. Therefore, the Warning Notification shall be delivered to the users accurately in the Notification Area and the content of Warning Notification should be understandable for many types of users (i.e. impaired persons, foreigners).
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5.2 Duration of delivery time
|
Duration of the delivery time for PLMN operators is the time from the receipt of the Warning Notification by the PLMN operator, i.e. the edge of the 3GPP network, to the time that the Warning Notification is successfully delivered to the UEs.
Provisioning of delivery of Primary and Secondary Notification may be required:
- Primary Notification shall be delivered within 4 seconds to the UE in the Notification Area even under congestion situation.
- Secondary Notification is delivered to the users in the Notification Area even under congestion situation.
Note 1: UEs that are out of coverage or switched off are not considered in the requirements.
Note 2: Secondary Notification may not always be generated as it depends on the Warning Notification Provider’s policy.
Note 3: Primary Notification may not always be generated (i.e. the warning may start with a Secondary Notification).
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5.3 Information element and volume
|
The following are the requirements from the perspective of information element and amount of data.
Both Primary and Secondary Notification shall:
- support at least 2 types of emergency events, which are Earthquake and Tsunami;
- be able to indicate the preferred UE behaviours when receiving Warning Notification, (e.g. whether to display text in the foreground, whether to ring a buzzer, whether to vibrate);
- be distinguishable from notifications generated for the purpose of testing, training and other notification services;
- be sent in an optimized type and amount of data, for example, a text with a certain length, by considering the delivery platforms for ETWS.
Primary Notification shall:
- convey data which is small enough to be sent quickly on the network.
- convey small amount of data to indicate the imminent occurrence of Earthquake and Tsunami, etc.
Secondary Notification may:
- convey a large amount of data in order to deliver text, audio to instruct what to do / where to get help, graphical data such as a map indicating the route from present position to evacuation site, time table of food distribution.
Note: The amount of data to be sent within a Primary Notification would be a few bytes to achieve quick information delivery.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5.4 Priority
|
Requirements from the perspective of priority are as follows:
- Primary Notification has higher priority than Secondary Notification.
- Notifications shall be able to be sequenced by the PLMN according to priority of notification in case that Primary Notification and Secondary Notification should exist at the same time in PLMN.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
5.5 Roaming users
|
Upon receiving Primary Notification which includes small amount of data to indicate the imminent occurrence of an Earthquake and/or Tsunami, the UE shall display the Warning Notification in a way that is easy to understand by the user, such as an icon or picture.
Note: It is expected that that the Warning Notification Provider will send the Warning Notification in the languages in common use in the specific area or in such a way that the Warning Notification can reasonably be understood.
5.6 Additional PWS Requirements Specific to ETWS
Subject to local/regional regulatory requirements, in addition to ETWS Primary and Secondary Notifications, ETWS shall be able to support broadcasting Warning Notification Area(s). This requirement applies to Satellite E-UTRAN and Satellite NG-RAN.
Subject to local/regional regulatory requirements, an ETWS-capable UE shall present the received ETWS Notification(s) (Primary or Secondary) if there is a corresponding Warning Notification Area(s) and if the ETWS-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if an ETWS-capable UE is unable to or fails to determine its location, the ETWS-capable UE shall present the ETWS Notification(s) (Primary or Secondary) to the user.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
6 CMAS Specific Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
6.1 Introduction to CMAS
|
The Warning Alert and Response Network (WARN) Act was passed by the United States Congress in September 2006 and was signed into law on October 13, 2006, known then as CMAS. CMAS was later renamed as Wireless Emergency Alert (WEA).
The Federal Communication Commission (FCC) released several Report and Order rulings for the Commercial Mobile Alert System. [1], [2], [3], [8] and [10].
As a result of these legislative and regulatory actions the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) agreed to develop ATIS and TIA standards to support the deployment of CMAS. This standard is listed in Clause 2.
The scope of these specifications includes the support of Commercial Mobile Alert System (CMAS) alert message via the GSM/UMTS Cell Broadcast functionality and warning message delivery via E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN. These specifications cover the mapping of CMAS messages onto the 3GPP-defined Cell Broadcast functionality and warning message delivery functionality, as well as the CMAS application layer functionality from the reception of the CMAS alert message from the Warning Notification Provider to the point of reception by the CMAS capable mobile device.
The CMAS functionality does not require modifications to the 3GPP-defined cell broadcast functionality.
The following functional reference model is based on the diagram from Section III.B.10 of the FCC First Report and Order for the Commercial Mobile Alert System, FCC 08-99 [1]:
Figure 6.1-1: CMAS Reference Architecture
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
6.2 Additional PWS Requirements Specific to CMAS
|
In addition to the General Requirements specified in Clause 4, the following requirements are specified for the deployment of CMAS. These CMAS specific requirements are based on the FCC Report and Orders listed in clause 6.1 and further specified in [4].
Warning Notifications shall support up to 360 characters of GSM 7 bit Default Alphabet [9] for E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN.
The following classes of Warning Notifications shall be supported: Presidential, Imminent Threat, Public Safety, Child Abduction Emergency (e.g. AMBER), and State/Local WEA Test.
When a Presidential Warning Notification is received, it shall always be presented to the user whenever Cell Broadcast Service via GSM, UMTS or warning notification delivery via E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN is enabled on the UE.
If the Presidential Warning Notification is received in English, then it shall be displayed by the UE. If the Presidential Warning Notification is received in a language other than English, then it shall only be displayed by the UE if the User has selected that language.
A CMAS-capable User Interface (UI) shall support the ability for the user to opt-out of only the Imminent Threat, Public Safety and Child Abduction Emergency Warning Notifications. A CMAS-capable User Interface (UI) shall support the ability for the user to opt-in to the State/Local WEA Test notification.
If the User has opted out of a Warning Notification class, then the Warning Notification for that class shall not be displayed by the UE.
If the User has not opted out of a Warning Notification class, then any Warning Notifications for that class received in English shall be displayed by the UE. This also applies to Warning Notifications received in any additional languages that may be selected by the User.
Warning Notifications may contain URLs and/or phone numbers.
A CMAS-capable User Interface (UI) shall support the ability (e.g., a “click” touch input) for the user to navigate to the URL or initiate a voice call to the phone number which may be included in the Warning Notification [8].
The PLMN broadcasting CMAS Warning Notifications shall also broadcast corresponding CMAS Warning Notification Area(s) when the CMAS Warning Notification is required to adhere to the maximum 0,1 of a mile CMAS Warning Notification Area(s) overshooting as specified in [10]. This requirement applies only to LTE and NR accesses.
A CMAS-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding CMAS Warning Notification Area(s) in order to minimize overloading network LCS resources.
Subject to opt-out and opt-in settings described above, a CMAS-capable UE shall present the CMAS Warning Notification sent if there is a corresponding CMAS Warning Notification Area(s) and if the CMAS-capable UE is able to determine that its location is within the corresponding CMAS Warning Notification Area(s). Otherwise, if a CMAS-capable UE is unable to or fails to determine its location, the CMAS-capable UE shall present the Warning Notification to the user.
A CMAS-capable UE shall store presented Warning Notifications for at least 24 hours unless explicitly deleted by the user.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
7 EU-ALERT Specific Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
7.1 Introduction to EU-ALERT
|
The generic name for the European Public Warning System is EU-ALERT. The letters EU will be replaced by characters identifying a particular country (e.g. NL-ALERT signifying the Netherlands, UK-ALERT signifying the United Kingdom). Such a strategy will allow each country to configure their own Public Warning System to meet their specific national requirements whilst adhering to a common core specification.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
7.2 Additional PWS Requirements Specific to EU-ALERT
|
In addition to the General Requirements specified in Clause 4, the following requirements are specified for the deployment of EU-ALERT. These EU-ALERT specific requirements are further specified in ETSI TS 102 900 [6].
EU-ALERT shall support three types of Warning Notifications: Alert messages to warn citizens of an imminent emergency situation, Advisory messages of lesser urgency, and Amber alerts.
The Alert messages shall be supported with three levels of severity. EU-Alert level 1 shall have no opt-out; levels 2 and 3 shall allow opt-out by the user. All levels of EU-ALERT messages shall be associated with a dedicated alerting indication.
NOTE: EU-Alert level 1 is compatible with the Presidential Alert in CMAS. EU-Alert level 2 is compatible with CMAS Extreme Alerts and EU-Alert level 3 is compatible with CMAS Severe Alert.
The Advisory messages have only one level. Advisory messages shall not be associated with any dedicated alerting indication.
Depending on national requirements, Amber alerts may need to be broadcast as part of the EU-ALERT service. Amber alerts shall not be associated with any dedicated alerting indication.
EU-ALERT shall support Warning Notifications in various languages. To support international roaming, it is expected that countries adopting EU-ALERT use the same Message Identifier for Warning Notifications in the local language. If Warning Notifications are broadcast in other languages besides the local language, then the Message Identifier for such Warning Notifications are expected to be the same across the countries adopting EU-ALERT.
EU-ALERT shall be supported on GERAN, UTRAN, E-UTRAN, Satellite E-UTRAN, NG-RAN , and Satellite NG-RAN.
EU-ALERT shall support that the PLMN broadcasting EU-ALERT Warning Notifications also broadcasts corresponding Warning Notification Area(s). This requirement applies only to E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN.
A EU-ALERT-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding Warning Notification Area(s) in order to minimize overloading network LCS resources.
Subject to opt-out and opt-in settings described above, a EU-ALERT-capable UE shall present the EU-ALERT Warning Notification sent if there is a corresponding Warning Notification Area(s) and if the EU-ALERT-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if a EU-ALERT-capable UE is unable to or fails to determine its location, the EU-ALERT-capable UE shall present the EU-ALERT Warning Notification to the user.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
8 Korean Public Alert System specific Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
8.1 Introduction to Korean Public Alert System
|
Telecommunications Technology Association (TTA) has specified a Korean Public Alert System (KPAS) which is based on PWS in [7]. That specification includes the support of Korean Public Alert System (KPAS) messages via the LTE Warning Message Delivery functionality. The Korean Public Alert System (KPAS) specification [7] also specifies application layer functionality to handle the transmission of CBS data from CBE to CBC and support for transmission of the same public alert message to UEs belonging to different mobile network operators in Republic of Korea. The specification requires that the system supporting Korean Public Alert System (KPAS) shall transmit the public alert message with high priority in order to provide up-to-date information on emergency situations. (e.g. In Tsunami situation, it is recommended to deliver message between CBC and UE in several seconds.).
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
8.2 Additional PWS Requirements Specific to Korean Public Alert System (KPAS)
|
In addition to the General Requirements specified in Clause 4, the following requirements are specified for the Korean Public Alert System (KPAS) [7]:
- Two classes of Warning Notification shall be supported; class 0 & class 1.
- The classes are differentiated per opt-out function. Class 0 shall have no opt-out and class 1 shall allow opt-out by the user.
Different types of Warning Notification shall be supported: Extreme Emergency, Emergency, Public Safety, and Amber. The Extreme Emergency type Warning Notifications are defined as class 0 and the other types are defined as class 1.
The characteristics of the Warning Notification shall follow the requirements specified in clause 4.
The current implementation requirement is for the message of up to 90 characters text. In addition, Warning Notifications using the UCS2 coding scheme [9] shall support up to 157 characters and Warning Notifications using the GSM 7 bit Default Alphabet coding scheme [9] shall support up to 360 characters from LTE onwards.
KPAS shall support Warning Notifications in various languages. If a Warning Notification is received in a language other than Korean, then it shall only be displayed by the UE if the user has selected that language.
A PWS-UE shall display Warning Notifications whose first texts are dedicated words when a PWS-UE receives Warning Notifications in other languages than Korean.
NOTE 1: Dedicated words are specified in the regulations of Korean Ministry of Interior and Safety.
A PWS-UE in KPAS shall support two dedicated alerting indication (audio attention signals).
NOTE 2: Two dedicated audio attention signals are specified in the regulations of Korean Ministry of Interior and Safety.
Warning Notifications may contain URLs and/or phone numbers. A UE shall allow the user to navigate to the URL or initiate a voice call to the phone number which may be included in the Warning Notification.
KPAS shall support that the PLMN broadcasting KPAS Warning Notifications also broadcasts corresponding Warning Notification Area(s).
A KPAS-capable UE shall utilize UE-Based Location Calculation (see 3GPP TS 22.071 [11]) to determine whether it is located within the corresponding Warning Notification Area(s) in order to minimize overloading network LCS resources.
Subject to opt-out and opt-in settings described above, a KPAS-capable UE shall present the KPAS Warning Notification sent if there is a corresponding Warning Notification Area(s) and if the KPAS-capable UE is able to determine that its location is within the corresponding Warning Notification Area(s). Otherwise, if a KPAS-capable UE is unable to or fails to determine its location, the KPAS-capable UE shall present the KPAS Warning Notification to the user.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9 Enhancements of Public Warning System (ePWS)
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.1 Service description
|
Requirements specified in the clause 9 do not apply for US WEA and Japan ETWS.
Enhancements of Public Warning System (ePWS) define behaviours for UEs with no user interface or with a user interface that is incapable of displaying text-based Warning Notifications when receiving a Warning Notification.
In addition, enhancements of Public Warning System (ePWS) is intended to improve the comprehension of a Warning Notification to the following categories of users:
- Users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies; and
- Users who are not fluent in the language of the Warning Notifications.
Requirements defined for PWS-UEs in clause 4 are applicable for ePWS-UEs unless dedicated ePWS-UE requirements described in clause 9 supersede them. Specifically, roaming requirements specified in clause 4.7 and security requirements specified in clause 4.8 are applicable for ePWS-UEs.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.2 General Requirements
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.2.1 ePWS Requirements
|
ePWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
There shall be no requirement for language translation in the operator’s network or the UE.
It shall be possible for the Warning Notification to be presented on the ePWS-UE upon reception and without any user interaction.
It shall be possible for users to configure the behavior of an ePWS-UE with regard to Warning Notification alerting and should allow at least volume adjustment if an ePWS-UE supports the alerting sound.
ePWS-UEs should have the ability to present previously displayed Warning Notifications if requested by the user.
- ePWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.2.2 Battery Life of ePWS-UE
|
Battery life of the ePWS-UE shall not be significantly reduced by ePWS.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.2.3 Enabling and disabling of Warning Notifications
|
The ePWS-UE shall be configured to receive all Warning Notifications.
It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select ePWS-UE enabling/disabling options via the user interface to disable, or later enable, the ePWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
Where regional or national regulations allow, the HPLMN operator shall be able to instruct the ePWS-UE to ignore all Warning Notifications in the HPLMN and in PLMNs equivalent to it, by means of a setting on the USIM.
Where regional or national regulations pertaining to a VPLMN allow, the HPLMN operator shall be able to instruct the ePWS-UE to ignore all Warning Notifications that are received whilst in this VPLMN, by means of a setting on the USIM, when the integrity of Warning Notifications in this VPLMN is known by the HPLMN operator to be compromised. This setting need not distinguish VPLMNs.
Subject to regional or national regulations, a ePWS-UE in limited service state shall be able to receive and present Warning Notifications.
NOTE : Non-existing or empty USIM data files results in all Warning Notifications being presented to the ePWS application.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.3 Requirements for 3GPP system supporting ePWS-UEs
|
The 3GPP system shall allow the content of a Warning Notification to include information that can be mapped to an event or a disaster and is identifiable by the ePWS-UEs.
NOTE: The information included in the content of a Warning Notification may be an identifier of an event or a disaster.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.4 Requirements for ePWS-UE incapable of displaying text based Warning Notification
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.4.1 Requirements for ePWS-UE with no user interface
|
ePWS-UEs with no user interface shall be able to receive a Warning Notification broadcast from the 3GPP network.
Subject to the intended function of the ePWS-UE (e.g. IoT) which has no user interface and regional regulatory requirements, the ePWS-UE may either:
1. Ignore Warning Notification; or
2. Take actions consistent with the ePWS-UE function (e.g. IoT) in response to specific Warning Notifications based on the content of the Warning Notification, e.g. shut down machinery or trigger a building alarm system.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.4.2 Requirements for ePWS-UE with a user interface incapable of displaying text based Warning Notification
|
The ePWS-UE with a user interface that is not capable of displaying a text-based content shall be able to support the reception of a Warning Notification broadcast from the 3GPP network and shall be able to support the extraction of the information on the type of a notified event or disaster from the received Warning Notification.
NOTE: The information extractable from the received Warning Notification may be an identifier of an event or a disaster.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
9.5 Requirements for the improvement of understanding the Warning Notification
|
The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able to support the reception of a Warning Notification broadcast from the 3GPP network.
The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able to support the extraction of any information on the type of a PWS notified event or disaster from the received Warning Notification
The ePWS-UE with a user interface providing accessibility extensions to mobile users with disabilities shall support the presentation of the information that improves the comprehension of Warning Notification by the accessibility extensions.
NOTE: Subject to regional regulatory requirements the ePWS-UE may use alternative alerting modes for user alerting consistent with ePWS-UE accessibility extensions and based on the content of the Warning Notification.
A PWS-UE may support the extraction and presentation of information representing a disaster or an event identifiable by Warning Notifications.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
10 Relay of Warning Notification
| |
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
10.1 Service description
|
Requirements specified in the clause 10 do not apply for US WEA and Japan ETWS.
3GPP system specified the relay functionality that is useful to extend the coverage supported by 3GPP system. With the relay functionality, PWS-UEs and ePWS-UEs that play the role of a relay UE or a remote UE conform to behaviours specified in the clause 10 when receiving a Warning Notification via the relay functionality.
|
76497c4a116dff37bcff12fd2a06a91d
|
22.268
|
10.2 Requirements for the relay functionality
|
A remote ePWS-UE and a remote PWS-UE shall be able to support the reception of a Warning Notification that is transmitted from an UE that supports the relay functionality. A remote ePWS-UE and a remote PWS-UE shall be able to automatically suppress duplicated notifications. A duplicate is a repetition of a same notification as determined by unique parameters. A remote ePWS-UE and a remote PWS-UE receiving a Warning Notification transmitted via an UE that supports the relay functionality shall behave in the same fashion as if it received the message directly from a 3GPP network. An UE that supports the relay functionality shall unconditionally forward the Warning Notification broadcast received from the network. Annex A (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New WI SP-42 SP-080788 S1-084395 22.268 - - Rel-9 - One-step-approved by SA#42 1.0.1 9.0.0 PWS SP-43 SP-090085 S1-090201 22.268 0001 1 Rel-9 D Fix for a note that is floating out of context 9.0.0 9.1.0 PWS-S1 SP-43 SP-090085 S1-090202 22.268 0002 1 Rel-9 F Proposal to solve conflicting requirements 9.0.0 9.1.0 PWS-S1 SP-43 SP-090085 S1-090203 22.268 0004 1 Rel-9 F Regulatory Requirements Pertaining to Roaming 9.0.0 9.1.0 PWS-S1 SP-43 SP-090085 S1-090204 22.268 0005 - Rel-9 F Removal of "subject to regulatory requirements" from PWS-UE requirements 9.0.0 9.1.0 PWS-S1 SP-43 ETSI clean-up: apply correct style and layout 9.0.0 9.1.0 - SP-44 SP-090375 S1-091398 22.268 0006 1 Rel-9 F Update Reference [4] 9.1.0 9.2.0 PWS SP-44 SP-090375 S1-091397 22.268 0007 1 Rel-9 F CR 22.268 Clarify Requirements for Handling of Concurrent PWS Warning Notifications 9.1.0 9.2.0 PWS SP-44 - - - - - - - Re-introduction of the figure in 6.1 which disappeared for some obscure reason 9.2.0 9.2.1 - - LTE logo changed into LTE Advanced logo 11.0.0 11.0.1 - SP-51 SP-110172 S1-110022 22.268 0010 - Rel-11 F RAT support for EU-Alert 11.0.0 11.1.0 TEI11 SP-53 SP-110574 S1-112405 22.268 0017 4 Rel-11 A Korean Public Alert System specific requirements 11.1.0 11.2.0 TEI10 SP-54 SP-110872 S1-113239r 22.268 0019 2 Rel-11 A Updates on Korean Public Alert System specific requirements 11.2.0 11.3.0 TEI10 SP-54 SP-110813 S1-113441 22.268 0020 2 Rel-11 C CMAS messages in Multiple Languages 11.2.0 11.3.0 TEI11 SP-55 SP-120172 S1-120341r 22.268 0027 6 Rel-11 A PWS Security requirement correction 11.3.0 11.4.0 PWS SP-55 SP-120185 S1-120338r 22.268 0024 7 Rel-11 B Disabling receipt of PWS messages 11.3.0 11.4.0 TEI11 SP-57 SP-120529 S1-122082 22.268 0037 - Rel-12 B Introduction of PWS Security requirements 11.4.0 12.0.0 PWS_Sec SP-58 SP-120870 S1-124468 22.268 0040 2 Rel-12 F Clarification of conditions of PWS Security requirements 12.0.0 12.1.0 PWS_Sec SP-60 SP-130196 S1-133290 22.268 0045 2 Rel-12 F CR on Rel-11 alignment regarding disabling and enabling of PWS Notifications 12.1.0 12.2.0 TEI12 SP-60 SP-130196 S1-133292 22.268 0046 1 Rel-12 C CR regarding PWS integrity protection when roaming internationally 12.1.0 12.2.0 TEI12 SP-70 SP-150748 S1-154480 22.268 0047 1 Rel-13 F A bandwidth reduced low complexity UE or a UE supporting eDRX may not support PWS 12.2.0 13.0.0 TEI13 SP-75 - - - - - - - Updated to Rel-14 by MCC 13.0.0 14.0.0 SP-76 SP-170441 S1-172424 22.268 0048 2 Rel-14 F Alignment of 3GPP PWS specifications to recent FCC WEA/CMAS regulation changes 14.0.0 14.1.0 TEI14 - - - - - - - - Creation of v.15.0.0 identical to v.14.1.0 because of the CRs approved at SP#79 raising the spec from v.14 to v.16 14.1.0 15.0.0 - SP-79 SP-180135 S1-180584 22.268 0052 2 Rel-16 B Requirements for 3GPP system supporting ePWS-UEs 15.0.0 16.0.0 ePWS SP-79 SP-180135 S1-180585 22.268 0049 4 Rel-16 B Definition of ePWS-UE and abbreviation of ePWS 15.0.0 16.0.0 ePWS SP-79 SP-180135 S1-180586 22.268 0051 3 Rel-16 B Background of ePWS-UE requirements 15.0.0 16.0.0 ePWS SP-79 SP-180135 S1-180587 22.268 0053 3 Rel-16 B Requirements for ePWS-UE with different or no user interface or with different roles 15.0.0 16.0.0 ePWS SP-79 SP-180135 S1-180588 22.268 0054 2 Rel-16 B Requirements for the improvement of understanding the PWS message 15.0.0 16.0.0 ePWS SP-79 SP-180135 S1-180589 22.268 0055 3 Rel-16 B Addition of NOTE in legacy requirements for the improvement of understanding the PWS message 15.0.0 16.0.0 ePWS SP-80 SP-180308 S1-181564 22.268 0059 1 Rel-16 A Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes 16.0.0 16.1.0 TEI15 SP-81 SP-180754 S1-182440 22.268 0061 2 Rel-16 A Additional requirements in KPAS 16.1.0 16.2.0 TEI15 SP-81 SP-180756 S1-182235 22.268 0062 Rel-16 B EU-alert applicability for 5G 16.1.0 16.2.0 TEI16 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2019-06 SA#84 SP-190301 0063 2 F CR 22.268-0063 Roaming requirements and security requirements for ePWS-UEs 16.3.0 2020-09 SA#89e SP-200785 64 1 F R16 CR to TS22.268 for Requirement alignment for Relay 16.4.0 2022-03 Identical to v.16.4.0 Creation of v.7.0.0 as to be able to implement CR 0068r2 (SP-220355) that goes from v.16.4.0 to v.18.0.0 17.0.0 2022-03 SP#95e SP-220355 0068 2 B Device based geo-fencing for EU-alert 18.0.0 2022-06 SA#96 SP-220432 0074 F Re-introducing relay requirements for public warning services 18.1.0 2022-06 SA#96 SP-220434 0072 1 B Alignment of KPAS requirements 18.1.0 2022-12 SA#98 SP-221262 0077 2 C Corrections of message length and coding for KPAS services 18.2.0 2023-06 SA#100 SP-230534 0078 1 F Corrections of scope and reference including editorial fixes 18.3.0 2023-06 SA#100 SP-230534 0079 1 B UE based geo-fencing requirements for KPAS 18.3.0 2024-12 SA#106 SP-241762 0084 2 F Warning notification with geofencing for ETWS over satellite access 19.0.0 2024-12 SA#106 SP-241762 0085 2 F PWS for IoT NTN 19.0.0
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
1 Scope
|
The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service as specified in 3GPP TS 22.179 [1], MCVideo Service as specified in 3GPP TS 22.281 [2], and MCData Service as specified in 3GPP TS 22.282 [3]. The mission critical services can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
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 TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[2] 3GPP TS 22.281: "Mission Critical Video services".
[3] 3GPP TS 22.282: "Mission Critical Data services".
[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6] 3GPP TS 22.468: "Group Communication System Enablers for LTE (GCSE_LTE) ".
[7] 3GPP TS 22.011: "Service accessibility".
[8] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
[9] ISBN 2-7461-1832-4: “UIC Project EIRENE System Requirements Specification”.
[10] ETSI EN 301 515 V3.0.0 (2018-03): “Global System for Mobile communication (GSM); Requirements for GSM operation on railways”.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
3 Definitions and abbreviations
| |
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [4] 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 [4].
Affiliated MCX Service Group Member: An MCX Service Group Member who has indicated an interest in participating in communications of the group, has been accepted by the MCX Service, and is prepared to receive and/or transmit Group Communications from/to the particular MCX Group.
Air ground air Communication: A communication (point-to-point or group) between at least one MCX User located on the ground and one or more MCX Users in helicopter(s) or aircraft while not on the ground, but in flight (in the air).
Broadcast Group Communication: A group communication where the initiating MCX User expects no response from the other MCX Users, so that when the user’s transmission is complete, so is the communication.
Group Communication: A one-to-many or many-to-many communication using an MCX Service.
In-progress Emergency: An emergency condition that has been accepted by the MCX Service, but has not yet been cancelled.
Late Entry: An Affiliated MCX Service Group Member joins in an in progress MCX Service Group Communication.
Location: The current position and, if available, information about the instantaneous velocity and direction of the MCX UE, and other attributes, e.g., a label indicating a geographic area in which the MCX UE is located.
NOTE 1: The terms "Location” and “Location information” can be used interchangeably.
MCX Service Ad hoc Group Communication: The combining of a multiplicity of MCX Users into a group for the duration of a communication and when the communication is terminated the group no longer exists.
MCX Service Ad hoc Group Emergency Alert: The combining of a multiplicity of MCX Users into a group for sending an emergency alert.
MCX Service Administrator: An individual authorized to control MCX parameters for an organization including, for example, user and group definitions, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
MCX Service Emergency Alert: A notification from the MCX UE to the MCX Service that the MCX User has an emergency condition.
MCX Service Emergency State: A heightened condition of alarm for an MCX User indicating a need for immediate assistance due to a personal life-threatening situation.
MCX Service Emergency Group Communication: An urgent MCX Service group communication initiated by a MCX user when there is the potential of immediate death or serious injury.
MCX Service Group: A defined set of MCX Users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions).
MCX Service Group Communication: A group communication for a particular MCX Service.
MCX Service Group Member: An MCX User authorized, upon successful affiliation, to participate in Group Communications of a particular MCX Group.
MCX Service Imminent Peril Group Communication: An urgent MCX Service Group Communication initiated by an MCX user when there is a potential of death or serious injury, but is less critical than an MCX Service Emergency Group Communication.
MCX Service User Profile: The set of information associated to an MCX User that allows that user to employ the MCX Service in a given role and/or from a given MCX UE.
MCX UE: A UE that can be used to participate in MCX Services.
MCX User: A user of MCX Service, who can use an MCX UE to participate in MCX Services.
Mission Critical: Quality or characteristic of a communication activity, application, service or device, that requires low setup and transfer latency, high availability and reliability, ability to handle large numbers of users and devices, strong security and priority and pre-emption handling.
Mission Critical Applications: Generic communication applications with mission critical characteristics, traditionally encompassing push-to-talk voice (MCPTT), real-time video (MCVideo) and real-time data (MCData).
NOTE 2: The short name, MCX, is used instead, with X standing for PTT, Video or Data
Mission Critical Organization: An end-user organization that includes MCX Users and/or MCX UEs, and can include MCX Service Administrators, and can be organized hierarchically with administrative control delegated within the organization or to an outside entity.
Mission Critical Service: Communication service providing enabling capabilities for Mission Critical Applications that are provided to end users from Mission Critical Organizations or other businesses and organizations (e.g., utilities, railways).
NOTE 3: The short name, MCX Service, can be used instead.
Participant: An MCX User who is currently receiving and/or transmitting in a Group Communication or a Private Communication.
Participant type: Functional category of the Participant (e.g., first responder, second responder, dispatch, dispatch supervisor), typically defined by the MCX Service Administrators.
Private Communication: A one-to-one communication between a pair of users using an MCX Service.
Selected MCX Service Group: An MCX Service Group that a particular Affiliated MCX Service Group Member uses for transmission.
Transmitting MCX Service Group Member: An Affiliated MCX Service Group Member who is currently transmitting in a Group Communication to a Selected MCX Service Group.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [4] 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 [4].
MCCoRe Mission Critical Services Common Requirements
MCData Mission Critical Data
MCPTT Mission Critical Push To Talk
MCVideo Mission Critical Video
MCX Mission Critical X, with X = PTT or X= Video or X= Data
MCX Service Mission Critical Service
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
4 Overview
| |
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
4.1 Rationale for MCCoRe
|
Further development of mission critical services beyond Mission Critical Push To Talk (MCPTT), such as Mission Critical Video (MCVideo) and Mission Critical Data (MCData), created an opportunity to re-use base functionality documented in the Stage 1 requirements for MCPTT. For example, the ability to communicate mission critical information to groups of users is a common need regardless of service type. Wherever originating MCPTT requirements were found to be in common with other mission critical services, those requirements were moved to this Technical Specification (3GPP TS 22.280). Each requirement that was moved has been voided in 3GPP TS 22.179, and an informative annex has been created at the end of that specification documenting the location of the originating 3GPP TS 22.179 requirement in the present document.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
4.2 MCCoRe creation process
|
The creation of 3GPP TS 22.280 followed a thorough analysis by mission critical application stakeholders of all the requirements in 3GPP TS 22.179, TR 22.879, and TR 22.880. Each set of requirements was evaluated, requirement-by-requirement, to determine if any one requirement was applicable to another service (MCPTT, MCVideo, or MCData). If anyone requirement was shared between two or more services, it was designated as a Mission Critical Services Common Requirements (MCCoRe) requirement and placed into this technical specification. At the end of this specification, there are sets of normative annexes that enumerate each requirement in the present document that is applicable to the given scope for the annex. For instance, one annex covers MCPTT, and there is a comprehensive table that lists every requirement that follows in clauses 5-9 that are applicable to MCPTT.
In the present document the term, MCX Service, is used to mean any mission critical service and when applied in requirements it means any mission critical service that is identified in the normative annexes as applying to the requirement in question. When the term, MCX Service, is used multiple times in a single requirement it means the same MCX Service except in the case of the inter service interworking in clause 8. Therefore, other than requirements in the inter services interworking clause, all requirements in the present document are single service requirements.
In principle, a mission critical group could use multiple services. At any time during a mission critical group communication, a group of mission critical users can, subject to permissions and availability of services and capable UEs, start or stop using any one or more instantiation(s) of any of the MCX services. In the text of the specification for each individual service, the group is considered to use the services of that individual type, and consequently is called MCPTT Group, MCVideo Group, MCData Group, or generically, MCX Service Group. Referring to a group as an individual service group is for writing simple requirements purposes, and does not mean that the group cannot actively use other services. See sub-clause 8.4 for more information.
The grouping and consolidation of common requirements shared by multiple mission critical applications is not to be construed as a statement or requirement of architectural design, impacting entities and interfaces. It is for downstream working groups to determine whether they can:
a) create generic MCX Service functionality that can be re-used by all Mission Critical Applications virtually unmodified;
b) extend and/or customize common MCX Services, if they determine that a Mission Critical Application has special needs, or
c) define separate support for Mission Critical Applications if they determine that they are so specialized that they cannot take advantage of a common MCX Service.
5 MCX Service requirements common for on the network and off the network
5.1 General Group Communications requirements
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.1 General aspects
|
[R-5.1.1-001] The MCX Service shall allow an MCX User utilizing one or more MCX UE(s), concurrently, to sign-in and receive service on each of the MCX UE(s).
[R-5.1.1-002] The MCX Service shall provide a mechanism by which an MCX UE makes a MCX Service group transmission to any MCX Service Group(s) for which the current MCX User is authorized.
NOTE: For off-network use, only group members with MCX UEs within communication range receive the transmission.
[R-5.1.1-003] The MCX Service shall be able to notify the Affiliated MCX Service Group Members when the group communication is set up (e.g., this can be provided as an audible tone on the MCX UE).
[R-5.1.1-004] The MCX Service shall provide a mechanism to disable notifications (e.g., audible tone) on an MCX UE when receiving normal MCX Service Group Communications (not MCX Service Emergency or Imminent Peril Communications).
[R-5.1.1-005] At any moment in time in an MCX Service Group communication, only one Participant type shall be used per Participant.
[R-5.1.1-006] The MCX Service shall provide a mechanism for a dispatcher or authorized user to configure which content source shall be able to transmit the content to an MCX Service Group (e.g. video cameras near an incident).
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.2 Group/status information
|
[R-5.1.2-001] The MCX Service shall provide a mechanism by which an MCX Service UE determines in which of the MCX Service Groups for which it is authorized there is an on-going MCX Service Group Communication.
[R-5.1.2-002] The MCX Service shall provide a mechanism by which an authorized MCX User determines in which MCX Service Groups there is an on-going MCX Service Group Communication.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.3 Group configuration
|
[R-5.1.3-001] The MCX Service shall allow the MCX Service Administrator to restrict who can be a member of specific MCX Service Groups, so that those MCX Service Groups shall be inaccessible to other users, including dispatchers or supervisors.
[R-5.1.3-002] The MCX Service shall enable a properly provisioned and authorized MCX UE operating on the network to receive its application layer level parameters (e.g., MCX Service Group ID, group keys) necessary for initiating and participating in Selected MCX Service Group and Private Communications at a future time, while off the network.
NOTE: This is a "run-time" requirement applicable to an already configured MCX UE, when MCX Service Groups and/or MCX Users, in addition to what was already configured, need to participate in future off-network communications.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.4 Identification
|
[R-5.1.4-001] The MCX Service shall support identifiers using character sets for international languages specified via configuration.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.5 Membership/affiliation
|
[R-5.1.5-001] The MCX Service shall provide a mechanism by which an MCX User determines the currently defined MCX Service Groups for which the MCX User is authorized.
[R-5.1.5-002] The MCX Service shall provide a mechanism by which an MCX UE determines the currently defined MCX Service Groups for which it is authorized.
[R-5.1.5-003] The MCX Service shall support an MCX User's ability to affiliate to one or more MCX Service Groups.
[R-5.1.5-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to limit the total number (Nc2) of MCX Service Groups that an MCX User can be affiliated to simultaneously.
[R-5.1.5-005] An MCX User may simultaneously be an MCX Service Group Member of one or more MCX Service Groups.
[R-5.1.5-006] The MCX Service shall provide a mechanism for an MCX Service Group Member to select zero or one Selected MCX Service Group.
[R-5.1.5-007] The MCX Service shall require that MCX Users affiliate with MCX Service Groups prior to participation in the communications of those groups.
[R-5.1.5-008] An MCX User shall be able to affiliate with a multiplicity of MCX Service Groups, subject to restrictions configured by the MCX Service Administrator.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.6 Group Communication administration
|
[R-5.1.6-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for MCX Service Group Communications for MCX Users within their authority.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.7 Prioritization
|
[R-5.1.7-001] The MCX Service shall provide a mechanism to organize MCX Service Groups into a hierarchy(ies).
[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.8 Charging requirements for MCX Service
|
[R-5.1.8-001] The MCX Service shall support charging for MCX Service Group Communications.
[R-5.1.8-002] Void
[R-5.1.8-003] The MCX Service shall support time-of-day sensitive charging based on actual resource utilization, provided QoS and provided priority.
[R-5.1.8-004] The MCX Service shall generate charging data that identifies the device(s) involved in a communication.
[R-5.1.8-005] The MCX Service shall support confidentiality of the charging between the service provider and the network operator.
[R-5.1.8-006] The MCX Service shall support confidentiality of the identity of the Mission Critical Organization.
[R-5.1.8-007] The MCX Service shall support reconciliation of the charging records between the service provider and the network operator.
[R-5.1.8-008] The MCX Service shall support offline charging.
[R-5.1.8-009] The MCX Service shall support online charging.
[R-5.1.8-010] The MCX Service shall be able to generate charging data for on-network mode.
[R-5.1.8-011] The MCX Service shall be able to generate charging data for off-network mode.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.1.9 MCX Service Emergency Alert triggered by Location
|
[R-5.1.9-001] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be triggered when an MCX UE moves into a predefined area.
[R-5.1.9-002] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be cancelled when the MCX UE moves out of a predefined area or to remain active until cancelled by the MCX User.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.2 Broadcast Group
| |
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.2.1 General Broadcast Group Communication
|
[R-5.2.1-001] The MCX Service shall support Broadcast Group Communications within that MCX Service from authorized MCX Service Group Members as determined by the MCX Service Administrator.
[R-5.2.1-002] The MCX Service shall only allow the initiating MCX Service Group Member to transmit on a Broadcast Group Communication, unless overridden (e.g., by a supervisor).
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.2.2 Group-Broadcast Group (e.g., announcement group)
|
[R-5.2.2-001] The MCX Service shall provide for the creation of Group-Broadcast Groups within that MCX Service with up to Bc1 levels of group hierarchy.
[R-5.2.2-002] The MCX Service shall be configurable to create a Group-Broadcast Group from one or more Group-Broadcast Groups within that MCX Service with any other non-Broadcast Group from the same MCX Service.
[R-5.2.2-003] The MCX Service shall enable an MCX Service Administrator to create a Group-Broadcast Group.
[R-5.2.2-004] A Broadcast Group Communication transmitted on a Group-Broadcast Group shall have priority over Group Communications on its subordinate groups from the same MCX Service.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.2.3 User-Broadcast Group (e.g., System Communication)
|
[R-5.2.3-001] The MCX Service shall provide for the creation of User-Broadcast Groups within that MCX Service with up to Bc2 levels of user hierarchy.
[R-5.2.3-002] A Broadcast Group Communication transmitted on a User-Broadcast Group shall have priority over Group Communications from the same MCX Service involving users within the user hierarchy.
|
38055db1edaa9b8bf534dbc753cc4ba8
|
22.280
|
5.3 Late communication entry
|
[R-5.3-001] The MCX Service shall provide a mechanism by which an Affiliated MCX Service Group Member can join an on-going MCX Service Group Communication.
[R-5.3-002] The MCX Service shall provide the identities of the transmitting MCX Service Group Member, and of the MCX Service Group and, if available, the aliases of the transmitting MCX Service Group Member and the identity of the Mission Critical Organization to the MCX UEs that enter the communication late.
[R-5.3-003] The MCX Service shall provide the transmitting MCX Service Group Member's Location information to MCX UEs that are late entering a communication in progress, subject to permissions.
[R-5.3-004] If an MCX Service Group Communication proceeds without all Affiliated MCX Service Group Members (e.g., due to one or more members being temporarily out of coverage during the communication setup or in one or more higher priority communications), the MCX Service shall attempt to add those affiliated members as the communication proceeds and they become available.
[R-5.3-005] If during an on-going MCX Service Group Communication, additional MCX Service Group Members affiliate with the MCX Service Group, the MCX Service shall add those members to the Group Communication.
[R-5.3-006] When the late entry user(s) become(s) member of the Group communication, all participants may be notified about the late entry member joining the Group communication.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.