Multi-TRP PUSCH Redundancy with Back-to-Back URLLC Transmissions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication technologies face challenges in meeting the strict reliability and latency requirements of Ultra-Reliable Low-Latency Communication (URLLC) due to scheduling restrictions that prevent simultaneous or back-to-back transmissions of physical uplink shared channels (PUSCH), especially in multi-transmission/reception point (TRP) scenarios, which are crucial for applications like vehicles and robots operating in factory plants.
Innovation Solution
Allowing URLLC back-to-back (re)transmissions on PUSCH and configuring them to be TRP-cycled, enabling simultaneous transmission of PUSCHs from multiple wireless device panels with different redundancy versions, thereby addressing both reliability and reduced latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If scheduling restrictions are applied to prevent simultaneous PUSCH transmissions, then transmission conflicts are avoided, but reliability and latency performance deteriorate
Solution Approach 1:
The patent segments the uplink transmission system by introducing separate scheduling mechanisms for different TRPs. Each TRP has its own scheduling entity that independently manages PUSCH transmissions, allowing simultaneous transmissions without mutual interference. This segmentation resolves the contradiction by enabling higher reliability through parallel transmissions while managing scheduling complexity through distributed control.
Solution Approach 2:
The patent transitions from time-domain sequential transmission to spatial-domain parallel transmission by utilizing multiple TRPs. Instead of avoiding conflicts through time separation, the system uses spatial separation across different transmission points to enable simultaneous PUSCH transmissions, thereby improving reliability without significant increase in scheduling complexity.
2Loss of time
If back-to-back PUSCH transmissions are allowed, then latency is reduced, but transmission conflicts and interference increase
Solution Approach 1:
The patent segments the transmission schedule by allowing different PUSCH transmissions to occur simultaneously at different TRPs. Each TRP operates independently with its own timing, enabling back-to-back transmissions without mutual interference. This resolves the latency reduction goal while controlling interference through spatial segmentation.
Solution Approach 2:
The patent introduces TRP-specific scheduling entities as intermediaries that coordinate transmissions. Each scheduling entity acts as a mediator between the source and destination, managing timing and resources to enable back-to-back transmissions while preventing harmful interference through localized control.
3Reliability
If multi-TRP redundancy is implemented, then reliability is improved, but system complexity increases
Solution Approach 1:
The patent segments the reliability function across multiple independent TRPs, each handling a portion of the transmission load. This distribution improves reliability through redundancy while managing system complexity by dividing the overall transmission task into manageable independent units, each with its own scheduling entity.
Solution Approach 2:
The patent implements universal scheduling entities that can manage multiple TRPs. Each scheduling entity is designed with multi-functionality to handle both initial transmissions and retransmissions across different TRPs, improving reliability while controlling complexity through standardized, reusable scheduling components.
Data Source
AI summary
A method, system and apparatus are disclosed. According to one aspect of the disclosure, a network node configured to communicate with a wireless device is provided. The network node includes processing circuitry configured to: cause a first physical downlink control channel, PDCCH, transmission starting at a first symbol and cause a second PDCCH transmission starting at a second symbol where the first PDCCH transmission is configured to schedule a first physical uplink shared channel, PUSCH, transmission ending at a third symbol for a transport block and the second PDCCH transmission configured to schedule a second PUSCH transmission starting at a fourth symbol for the transport block, where the second symbol occurs before the third symbol, the third symbol occurs later in time than the first symbol and the fourth symbol occurs later in time than that second symbol.