Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 22.104  Word version:  18.2.0

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

 

6  Ethernet applicationsWord‑p. 29

6.1  Description

This section lists the requirements applicable to the 5G system for supporting cyber-physical applications using Ethernet.
For requirements pertaining to common, fundamental Ethernet transport requirements, and any requirements necessary to support the 5G LAN-type service, see Clause 6.24 in TS 22.261.

6.2  Requirements

For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links and other ethernet transports such as wired and optical (EPON.)
For infrastructure dedicated to high performance Ethernet applications, the accuracy of clock synchronisation should be better than 1μs.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support enhancements for time-sensitive networking as defined by IEEE 802.1Q, e.g. time-aware scheduling with absolute cyclic time boundaries defined by IEEE 802.1Qbv [19], for 5G-based Ethernet links with PDU sessions type Ethernet.
For infrastructure dedicated to high performance Ethernet applications, absolute cyclic time boundaries shall be configurable for flows in DL direction and UL direction.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support coexistence of hard-RT traffic following a time-aware schedule and lower priority traffic. The lower priority traffic cannot have a performance degrading impact on the hard-RT traffic.
The Ethernet transport service shall support routing based on information extracted from the Ethernet header information created based on IEEE 802.1Qbv.
Up

7  Direct device connection for cyber-physical control applications |R17|

7.1  Description

This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless direct device connection.

7.2  Requirements

7.2.1  General

The 5G system shall allow UEs to use direct device connection when the UEs are not served by a RAN.
The 5G system shall be able to support direct device connection between UEs in close proximity using spectrum different than the spectrum being used for the 5GC-based communication.
The 5G system shall be able to support direct device connection for 5G LAN-type private communication.
The 5G system shall be able to support multicast communication between the UEs within the group of UEs using direct device connection .
Up

7.2.2  Network performanceWord‑p. 30

The 5G system shall be able to support direct device connection between a group of UEs for periodic deterministic communication (both unicast and multicast) with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
The 5G system shall be able to support mobility of the group of UEs using direct device connections with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
The 5G system shall be able to support direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs up to 50 m distance.
Up

7.2.3  Clock synchronization

7.2.3.1  Description |R18|

This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for direct device connection, building on the description already provided in Clause 5.6.0.

7.2.3.2  Clock synchronization requirements |R18|

The 5G system shall be able to support clock synchronization (working clock domain) between the UEs within the group of UEs using direct device connection ProSe communication.
The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile) or 5G sync domain-based clock synchronization among the group of UEs using direct device connection.
The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs in the group of UEs using direct device connection.
The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using direct device connection.
The 5G system using direct device connection shall support one or multiple time domains (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile or 5G sync domain configuration).
The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs within the group of UEs connected by direct device connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22], IEEE Std 1588 [28], or 5G sync domain.
For direct device connection, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 7.2.3.2-1. In this case, the sync master and sync device are located at or connected to two UEs which are connected via direct device connection.
Number of devices in one communication group for clock synchronization 5GS synchronicity budget requirement (note 1) Service area (note 2) Scenario
2 to 16≤ 900 ns10 m x 10 m x 5 m;
50 m x 5 m x 5 m
Cooperative carrying - fragile work pieces; (clause A.2.2.5)
2 to 16≤ 900 ns10 m x 10 m x 5 m;
50 m x 5 m x 5 m
Cooperative carrying - elastic work pieces; (clause A.2.2.5)
NOTE 1:
5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For direct device connection, the ingress is one UE and the egress the other directly connected UE.
NOTE 2:
Service Area for direct device connections between UEs (length x width x height). The group of UEs with direct device connections might move throughout the whole factory site (up to several km²).
Up

7.2.4  Service ContinuityWord‑p. 31

The 5G system shall be able to minimize service disruption for a group of UEs using direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying, when the group moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers).

7.2.5  Direct device connection via UE to UE relay

The 5G system shall be able to support direct device connection via an UE to UE relay with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs out of transmission range of each other.

8  Indirect network connection for cyber-physical control applications |R18|

8.1  Description

This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless indirect network connection.

8.2  Requirements

8.2.1  General

The 5G system shall be able to support multicast communication between the UEs within the group of UEs using indirect network connection.

8.2.2  Communication via indirect network connection

The 5G system shall be able to provide service to an out-of-coverage UE via indirect network connection using one relay UE while meeting the performance requirements specified for the process automation use cases in Table 5.2-1 (related to Annex A.2.3.1 and A.2.3.2).

8.2.3  Clock synchronizationWord‑p. 32

8.2.3.1  Description

This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for indirect network connection, building on the description already provided in Clause 5.6.0.

8.2.3.2  Clock synchronization requirements

The 5G system shall be able to support clock synchronization (working clock domain) for UEs using indirect network connection.
The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile) or 5G sync domain-based clock synchronization for UEs using indirect network connection.
The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs using indirect network connection.
The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using indirect network connection.
The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs connected by indirect network connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile or 5G sync domain.
For indirect network connection between UEs using one UE-to-network relay, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 8.2.3.2-1.
Number of devices in one communication group for clock synchronization UE density [UE / m²] 5GS synchronicity budget requirement (note 1) Service area (note 2) Scenario
10 to 20 UEs-< 1 ms≤ 100 m x 100 m x 50 mProcess automation - closed loop control (clause A.2.3.1)
≤ 10,000 to 100,000-≤ 1 ms≤ 10 km x 10 km x 50 mProcess and asset monitoring (clause A.2.3.2)
NOTE 1:
5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For indirect network connection, 3 cases are considered:
  1. If the path of clock synchronization messages is between device and network side, ingress and egress of the 5G system are the remote UE and the corresponding UPF on the network side.
  2. If ingress and egress of the 5G system are at the device side, the 5G synchronicity budget is the time error between the involved remote UE and the 5G sync master.
  3. If the sync master is inside the 5G system, the 5G synchronicity budget ingress is the sync master in the 5G system and egress is the remote UE.
NOTE 2:
Service Area for indirect network connections between UEs (length x width x height).
Up

8.2.4  Service Continuity

The 5G system shall be able to minimize service disruption for a UE using indirect network connection with respective service performance requirements in Table 5.2-1 related to process automation, when the UE moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers).

9  Recovery of infrastructure for electrical distribution |R18|Word‑p. 33

9.1  Description

The robustness of the infrastructure for electrical power distribution may depend upon the possibility to operate telecommunication networks even during an energy system incident, in which electricity cannot be delivered to some network operator facilities. Through coordination between the network operator and the energy system operator, increases in the ability to recover the energy system operation can be achieved.

9.2  Requirements

Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the ability of the MNO's infrastructure to continue operation despite a lack of electrical supply service, specifying which physical regions would be affected in terms of physical topology and the remaining time in which operation is possible.
Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can, in the event of an energy distribution system service interruption, communicate the energy distribution system recovery status in terms of location and time table to the MNO.
Up

Up   Top   ToC