Enhanced support of industrial IoT in the 5G system

In Release 17, the 5G System expands the support for Time Synchronization and Time Sensitive communications for any application.

The 5G System architecture enables any Application Function (AF) – in the same or different trust domain – to provide its requirements for QoS, traffic characteristics for QoS scheduling optimization, time synchronization activation and deactivation.

If the AF is in a different trust domain from the 5G System, then it provides input via exposure framework, NEF API. If the AF is in the same trust domain as the 5G System, then it provides input directly via the Time Sensitive communication Time Synchronization function (TSCTSF).

The Functional Architecture is shown in the figure below:

Time synchronization
The figure below depicts the two main synchronization methods supported: the 5GS synchronization and the (g)PTP domain synchronization.

• 5G Clock synchronization: Used for NG RAN synchronization and also distributed to the UE. 5G Clock synchronization over the radio interface towards the UE is specified in TS 38.331.
• (g)PTP synchronization: Provides time synchronization service to (g)PTP network. This process follows the standards IEEE Std 802.1AS or IEEE 1588 operation.

The two synchronization processes can be considered independent from each other and the gNB only needs to be synchronized to the 5G Grand Master (GM) clock.

In order to support (g)PtP time synchronization, the 5G System operates in any of the following modes:

• as time-aware system (IEEE Std 802.1AS).
• as Boundary Clock (IEEE Std 1588).
• as peer-to-peer Transparent Clock (IEEE Std 1588).
• as end-to-end Transparent Clock (IEEE Std 1588).

The 5GS shall be modelled as an IEEE Std 802.1AS or IEEE Std 1588 compliant entity based on the above configuration. The TTs located at the edge of the 5G system (i.e. device side DS-TT and network side NW-TT) are responsible for fulfilling functionalities related to IEEE Std 802.1AS or IEEE Std 1588.

The 5G System is provisioned by the profiles supported by 3GPP specifications that include: Default PTP Profile, IEEE Std 802.1AS PTP profile for transport of timing as defined in IEEE Std 802.1AS, SMPTE Profile for use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications.

Furthermore, (g)PtP time synchronization is supported for the scenarios when Grand Master clock is behind the UE (uplink time sync, UE – UE time sync) and behind the network (down link time sync).

The ability for the AF to influence activation of 5G reference time distribution to the UE(s) along with time synchronization error budget (based on the accuracy needed for the application) has also been introduced.

Time sensitive communication QoS
TSC Assistance Information (TSCAI) describes traffic characteristics that may be provided for use by the gNB, to allow more efficiently scheduled radio resources for periodic traffic and applying to PDU session type Ethernet and IP.

TSCAI describes TSC traffic characteristics for use in the 5G System. The knowledge of TSC traffic pattern is useful for 5G-AN to allow it to more efficiently schedule periodic and deterministic traffic flows either via Configured Grants, Semi-Persistent Scheduling or with Dynamic Grants.

5GS determines TSC Assistance Container based on information provided by an AF/NEF and may provide it to PCF for IP type and Ethernet type PDU sessions.

The AF may provide the traffic pattern parameters such as Burst Arrival Time with reference to the ingress port, Periodicity, Flow Direction, Survival Time and Time domain to the NEF. The NEF forwards the received traffic pattern parameters to TSCTSF.

The AF trusted by the operator can be allowed to provide such traffic pattern parameters to TSCTSF directly. The TSCTSF is responsible for determining and forwarding these traffic pattern parameters in TSC Assistance Container to the SMF (via PCF).

Survival Time was also introduced as part of TSCAI in order for the AF to provide the time period an application can survive without any burst. It refers to the time that an application consuming a communication service may continue without an anticipated message. Maximum number of messages (message is equivalent to a burst) or in terms of time units. Single burst is expected within a single time period referred to as the periodicity.

TSC Assistance Information (TSCAI)

CT Bureau