PUSCH Msg3 Repetition Configuration for URLLC Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the New Radio (NR) system, there is a need to improve the transmission reliability of the third message (Msg3) during the four-step random access process, particularly for ultra-reliable and low latency communication (URLLC) services, where repeated transmission of uplink data is essential but not effectively managed.
Innovation Solution
A method where a terminal device determines the number of repeated transmission times for the Physical Uplink Shared Channel (PUSCH) based on public configuration information or a time domain resource allocation list, and a network device configures this information to ensure reliable transmission of Msg3, using PUSCH common configuration information or time domain resource allocation lists to schedule appropriate repetitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If repeated transmission of PUSCH is used to improve transmission reliability, then transmission reliability is improved, but transmission latency increases
Solution Approach 1:
The patent applies dynamics by making the number of PUSCH repetitions configurable and adaptable to different service requirements. The network device can dynamically adjust the repetition count based on service type (e.g., URLLC vs. eMBB), channel conditions, and traffic characteristics, allowing the system to optimize between reliability and latency trade-offs for different scenarios
Solution Approach 2:
The patent implements parameter changes by introducing configurable parameters for PUSCH repetition transmission, including the number of repetitions, time domain resource allocation, and mapping types. These parameters can be adjusted to change the transmission characteristics, enabling the system to achieve high reliability when needed while maintaining low latency when conditions permit
2Reliability
If the number of PUSCH repetitions is increased to ensure Msg3 delivery, then transmission reliability is improved, but resource consumption increases
Solution Approach 1:
The patent applies partial action by transmitting PUSCH repetitions only when necessary for reliable delivery. The system uses configured parameters to determine the appropriate number of repetitions, avoiding excessive transmissions when channel conditions are good or when the message is already successfully delivered, thus conserving uplink resources while ensuring reliability when needed
3Reliability
If PUSCH repetition transmission is configured for all random access scenarios, then transmission reliability is improved, but device complexity increases
Solution Approach 1:
The patent implements universality by creating a unified configuration mechanism that can handle different random access scenarios (contention-based and contention-free) and different service types (URLLC and eMBB) through a single set of configurable parameters. This multi-functional approach allows the same PUSCH repetition mechanism to serve multiple purposes without requiring separate complex configurations for each scenario
Data Source
AI summary
A method for transmitting a data channel, a terminal device and a network device. The method comprises: a terminal device determines information about the number of repeated transmissions of a physical uplink shared channel (PUSCH) according to the PUSCH public configuration information or a time domain resource allocation list, wherein the PUSCH is used for carrying a third message in the random access process.