Uplink Channel Multiplexing With Service-Specific HARQ-ACK Timelines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing uplink channel multiplexing mechanisms in Release 15 (R15) and Release 16 (R16) fail to adequately address the processing timeline and latency requirements for intra-UE multiplexing of Enhanced Mobile Broadband (eMBB) and Ultra-reliable and Low Latency Communications (URLLC) services, leading to errors and unsatisfied latency and reliability requirements for URLLC HARQ-ACK.
Innovation Solution
A method for uplink channel multiplexing that determines separate processing timelines for different services, removes PUCCH resources not satisfying these timelines, and codes different uplink services accordingly to avoid errors and meet latency and reliability requirements, improving system spectral efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single processing timeline is used for multiplexing eMBB and URLLC services, then the multiplexing mechanism is simple, but the processing timeline cannot be satisfied for both services simultaneously
Solution Approach 1:
The patent segments the processing timeline into service-specific timelines: one for eMBB services and another for URLLC services. Each service type has its own processing requirements and timeline constraints, allowing independent optimization without interference. This segmentation resolves the contradiction by enabling each service to meet its processing timeline requirements while maintaining manageable complexity through structured separation.
Solution Approach 2:
The patent introduces dynamic resource allocation and timeline adjustment mechanisms that adapt to different service requirements. The system can dynamically select appropriate processing timelines based on service type, priority, and current resource availability, allowing the multiplexing mechanism to flexibly satisfy both eMBB and URLLC processing requirements without requiring a completely rigid or overly complex fixed structure.
2Productivity
If eMBB HARQ-ACK and URLLC HARQ-ACK are multiplexed according to R15 rules, then resource utilization is improved, but URLLC latency and reliability requirements cannot be satisfied
Solution Approach 1:
The patent applies local quality by assigning different processing priorities and timeline constraints to different service types within the same multiplexing framework. URLLC HARQ-ACK is assigned stricter latency constraints and higher priority processing, while eMBB HARQ-ACK allows more flexible timing. This localized differentiation enables both services to coexist with appropriate quality of service, maintaining resource utilization while satisfying URLLC requirements.
Solution Approach 2:
The patent implements preliminary action by pre-configuring service-specific processing timelines and priority rules before multiplexing occurs. The system预先 establishes separate processing requirements for eMBB and URLLC services, allowing the multiplexing mechanism to proactively allocate resources and schedule transmissions in advance, ensuring URLLC latency requirements are met while maintaining efficient resource utilization.
3Device complexity
If the processing timeline is determined by the earliest PUCCH or PUSCH, then the multiplexing rule is simple, but error situations occur when URLLC requires shorter processing time
Solution Approach 1:
The patent transforms the static single-timeline rule into a dynamic multi-timeline system that adapts to service requirements. Instead of always using the earliest PUCCH/PUSCH timing, the system dynamically selects appropriate processing timelines based on service type, allowing URLLC to use shorter processing timelines when needed while eMBB uses standard timelines, maintaining reliability without excessive complexity.
Solution Approach 2:
The patent changes the processing timeline parameter from a single fixed value to multiple service-specific values. By introducing service-type-dependent timeline parameters, the system can adjust processing requirements according to whether the traffic is eMBB or URLLC, preventing error situations while keeping the determination rule manageable through parameterized configuration.
Data Source
AI summary
Embodiments of the present application provide an uplink channel multiplexing method and device, and a terminal. The method comprises: when a terminal needs to transmit a plurality of overlapping physical uplink control channels (PUCCHs) and/or physical uplink shared channels (PUSCHs) on the same time slot or sub slot, if one of the PUCCH transmissions or PUSCH transmissions corresponds to the format of downlink control information (DCI) detected by the terminal, the terminal expects that a start symbol S0 of the earliest PUCCH or PUSCH in the overlapping PUCCHs and/or PUSCHs satisfies a first condition. The solution of the present application can avoid the case of an error and the case that a base station cannot control a terminal, satisfies latency and reliability requirements of a URLLC service, and improves system spectral efficiency.