{"id":22914,"date":"2023-10-04T19:31:51","date_gmt":"2023-10-04T19:31:51","guid":{"rendered":"https:\/\/www.5gworldpro.com\/?p=22914"},"modified":"2023-10-04T19:31:51","modified_gmt":"2023-10-04T19:31:51","slug":"how-is-5g-urllc-defined-and-what-are-related-technologies","status":"publish","type":"post","link":"https:\/\/new.5gworldpro.com\/?p=22914","title":{"rendered":"How Is 5G URLLC defined and what are related technologies ?"},"content":{"rendered":"

5G defines three application scenarios: enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and ultra-reliable low-latency communication (URLLC).<\/p>\n

URLLC delivers communications with ultra-low latency and ultra-high reliability, and can meet network requirements of some latency-sensitive, reliability-stringent services, such as autonomous driving, smart manufacturing, remote diagnostics, augmented reality (AR)\/virtual reality (VR), and high-definition (HD) videos.\u00a0URLLC is involved in end-to-end (E2E) transmission procedures across the core network, transport network, and RAN.<\/p>\n

Moreover, multiple network deployment solutions are available to suit different industries and applications.<\/p>\n

The URLLC technologies applied on the RAN side and typical network deployment solutions will be discussed.<\/p>\n

3GPP TS 22.261 defines the requirements of different services for communication latency and reliability on the RAN side.\u00a0Table 2-1<\/a>\u00a0illustrates such requirements of some services. For example, remote shopping\/education-specific services require the E2E latency of 10\u201320 ms, jitter of 5 ms, and reliability of 99.9%, whereas real-time control services require the E2E latency of 1 ms or less, jitter of 1 \u03bcs, and reliability of 99.9999%.<\/p>\n

\n

Table 2-1<\/span>\u00a0Latency requirements of various services<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Scenario<\/p>\n<\/th>\n

\n

Application<\/p>\n<\/th>\n

\n

E2E Latency<\/p>\n<\/th>\n

\n

Jitter<\/p>\n<\/th>\n

\n

Reliability Requirement<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n

Autonomous driving<\/p>\n<\/td>\n

\n

Coordinated control – platooning<\/p>\n<\/td>\n

\n

< 3 ms<\/p>\n<\/td>\n

\n

1 \u03bcs<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Cooperative manoeuvres (collision avoidance\/lane change)<\/p>\n<\/td>\n

\n

< 10 ms<\/p>\n<\/td>\n

\n

1 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Sensor information sharing<\/p>\n<\/td>\n

\n

< 50 ms<\/p>\n<\/td>\n

\n

20 ms<\/p>\n<\/td>\n

\n

99.99%<\/p>\n<\/td>\n<\/tr>\n

\n

Remote vehicle operation<\/p>\n<\/td>\n

\n

10\u201330 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Dynamic HD map update<\/p>\n<\/td>\n

\n

~100 ms<\/p>\n<\/td>\n

\n

20 ms<\/p>\n<\/td>\n

\n

99.9%<\/p>\n<\/td>\n<\/tr>\n

\n

VR\/AR<\/p>\n<\/td>\n

\n

VR remote motion control (surgery\/drone)<\/p>\n<\/td>\n

\n

10\u201320 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

VR 360 live event streaming<\/p>\n<\/td>\n

\n

10\u201320 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.99%<\/p>\n<\/td>\n<\/tr>\n

\n

VR collaborative game<\/p>\n<\/td>\n

\n

10\u201320 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.99%<\/p>\n<\/td>\n<\/tr>\n

\n

VR remote shopping\/education<\/p>\n<\/td>\n

\n

10\u201320 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9%<\/p>\n<\/td>\n<\/tr>\n

\n

AR (game\/navigation)<\/p>\n<\/td>\n

\n

20 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9%<\/p>\n<\/td>\n<\/tr>\n

\n

Smart grid<\/p>\n<\/td>\n

\n

High-voltage power distribution<\/p>\n<\/td>\n

\n

< 5 ms<\/p>\n<\/td>\n

\n

1 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Medium-voltage power distribution<\/p>\n<\/td>\n

\n

25 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9%<\/p>\n<\/td>\n<\/tr>\n

\n

Factory automation<\/p>\n<\/td>\n

\n

Real-time motion control<\/p>\n<\/td>\n

\n

\u2264 1 ms<\/p>\n<\/td>\n

\n

1 \u03bcs<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Discrete automation (vehicles, etc.)<\/p>\n<\/td>\n

\n

10 ms<\/p>\n<\/td>\n

\n

100 \u03bcs<\/p>\n<\/td>\n

\n

99.99%<\/p>\n<\/td>\n<\/tr>\n

\n

Production automation (remote control)<\/p>\n<\/td>\n

\n

50 ms<\/p>\n<\/td>\n

\n

20 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Production automation (monitoring)<\/p>\n<\/td>\n

\n

50 ms<\/p>\n<\/td>\n

\n

20 ms<\/p>\n<\/td>\n

\n

99.9%<\/p>\n<\/td>\n<\/tr>\n

\n

Healthcare & safety, smart city, and drone<\/p>\n<\/td>\n

\n

Real-time command and control for remote surgery<\/p>\n<\/td>\n

\n

10 ms<\/p>\n<\/td>\n

\n

1 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Intelligent transport systems – infrastructure backhaul<\/p>\n<\/td>\n

\n

10 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n

\n

Time critical sensing and feedback for smart cities (such as traffic lights)<\/p>\n<\/td>\n

\n

30 ms<\/p>\n<\/td>\n

\n

5 ms<\/p>\n<\/td>\n

\n

99.99%<\/p>\n<\/td>\n<\/tr>\n

\n

Remote drone operation<\/p>\n<\/td>\n

\n

10\u201330 ms<\/p>\n<\/td>\n

\n

1 ms<\/p>\n<\/td>\n

\n

99.9999%<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

 <\/p>\n

\n
\n

3GPP TR 38.913 defines target values for the communication latency and reliability on the RAN side in URLLC scenarios.<\/p>\n

Table below<\/span>\u00a0Target values for RAN-side latency and reliability in 5G URLLC scenarios<\/span><\/div>\n
\n\n\n\n\n\n\n
\n

Indicator<\/p>\n<\/th>\n

\n

Definition in 3GPP Specifications<\/p>\n<\/th>\n

\n

Target Value<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n

User-plane latency<\/p>\n<\/td>\n

\n

User-plane latency refers to the time it takes to successfully deliver an application layer packet\/message from the radio protocol layer 2\/3 SDU ingress point to the radio protocol layer 2\/3 SDU egress point via the radio interface in both uplink and downlink directions.<\/p>\n<\/td>\n

\n

Downlink: 0.5 ms<\/p>\n

Uplink: 0.5 ms<\/p>\n<\/td>\n<\/tr>\n

\n

Reliability<\/p>\n<\/td>\n

\n

Reliability is evaluated against the probability that a specific number of bytes will be transmitted successfully within a specific delay. The delay refers to the time required for delivering a small data packet from the radio protocol layer 2\/3 SDU ingress point to the radio protocol layer 2\/3 SDU egress point via the radio interface at specific channel quality (for example, a coverage edge).<\/p>\n<\/td>\n

\n

99.999% (32 bytes@1 ms)<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

<\/div>\n<\/div>\n<\/div>\n
\n

How to Evaluate URLLC Indicators?<\/a><\/h1>\n
\n

The previous section defines two URLLC indicators: latency and reliability. In real-world communications, the latency on the RAN side and reliability are evaluated as follows:<\/p>\n