Intra-UE Multiplexing Configuration for Overlapping Uplink Channels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems, particularly in 5G NR, overlapping uplink channels with different priorities often result in collisions, leading to inefficient communication as lower priority transmissions are dropped to prioritize higher priority ones, causing latency and inefficiency due to retransmissions and complex scheduling.
Innovation Solution
The implementation of a method where a UE receives an RRC message indicating whether to use intra-UE prioritization or intra-UE multiplexing for overlapping uplink channels, allowing dynamic configuration to resolve collisions by either dropping lower priority channels or multiplexing them, reducing overhead and complexity in scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If intra-UE prioritization is used for overlapping uplink channels, then higher priority transmissions are ensured, but lower priority transmissions are dropped causing latency and retransmissions
Solution Approach 1:
The patent implements dynamic switching between intra-UE prioritization and intra-UE multiplexing modes based on real-time channel conditions and traffic characteristics. The UE can adaptively select the appropriate collision resolution strategy, allowing lower priority transmissions to be multiplexed when conditions permit, thereby reducing latency while maintaining reliability for high priority traffic when needed.
Solution Approach 2:
The system changes the operational parameters of uplink channel handling by introducing configurable priority levels and dynamic mode selection between prioritization and multiplexing. This allows the network to adjust the behavior of UE in different scenarios, optimizing the balance between reliability and latency based on traffic requirements.
2Reliability
If intra-UE prioritization is used for overlapping uplink channels, then higher priority channels are transmitted, but scheduling complexity increases due to collision resolution requirements
Solution Approach 1:
The UE autonomously determines and resolves collisions between overlapping uplink channels based on pre-configured priority rules and the selected mode (prioritization or multiplexing). This self-service mechanism eliminates the need for complex network-side scheduling intervention, reducing overall scheduling complexity while ensuring priority channels are transmitted reliably.
Solution Approach 2:
The network pre-configures the UE with priority levels and collision resolution modes before uplink transmissions occur. This preliminary configuration allows the UE to automatically resolve collisions without real-time network intervention, simplifying the scheduling process while maintaining priority assurance.
3Adaptability or versatility
If dynamic indication between intra-UE multiplexing and intra-UE prioritization is implemented, then scheduling flexibility is improved, but signaling overhead increases
Solution Approach 1:
Instead of providing continuous dynamic indications for every uplink transmission, the system uses partial action by implementing semi-static configuration with occasional dynamic updates only when mode changes are needed. This reduces signaling overhead while maintaining the flexibility to switch between multiplexing and prioritization modes when required.
Data Source
AI summary
A UE receives radio resource control (RRC) message indicating a semi-static configuration for the UE for one of: intra-UE prioritization for overlapping uplink channels of different priorities or intra-UE multiplexing for the overlapping uplink channels of the different priorities. The UE determines between the intra-UE prioritization or the intra-UE multiplexing for a set of overlapping uplink channels of the different priorities based, at least in part, on the RRC message and transmits an uplink transmission including one or more of the set of overlapping uplink channels based, at least in part, on the semi-static configuration in the RRC message.