Terminal Device Uplink Resource Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G communications systems, there is a conflict between the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH) when they overlap in time domain, particularly when a scheduling request (SR) is triggered by a terminal device, leading to inefficiencies in resource allocation and increased latency for ultra-reliable and low-latency communications (URLLC) services.
Innovation Solution
The terminal device prioritizes the scheduling request by associating different logical channels with specific SR configurations and resource requirements, allowing it to send the PUCCH while avoiding overlap with the PUSCH, ensuring that the SR is transmitted on a separate resource occasion if necessary, and dynamically or pre-configured scheduling is used to allocate resources effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the terminal device sends both PUCCH carrying SR and PUSCH carrying eMBB data simultaneously, then resource utilization is maximized, but resource conflict occurs and URLLC latency increases
Solution Approach 1:
The patent segments the uplink transmission by separating PUCCH and PUSCH into different time resources. When URLLC data arrives and triggers an SR, the terminal device sends the SR on PUCCH first, then sends eMBB data on PUSCH in a subsequent time slot, avoiding simultaneous transmission conflicts while maintaining high resource utilization.
Solution Approach 2:
The patent implements dynamic resource allocation where the terminal device adapts its transmission strategy based on service type. For URLLC services, the device prioritizes low-latency transmission by sending SR immediately on PUCCH. For eMBB services, the device uses scheduled PUSCH resources. This dynamic adaptation resolves the contradiction between resource utilization and latency.
2Loss of time
If the terminal device prioritizes PUCCH carrying SR for URLLC, then URLLC latency is reduced, but eMBB data transmission is delayed
Solution Approach 1:
The patent allows temporary discarding of eMBB data transmission when URLLC SR needs immediate sending. The eMBB data is not lost but rescheduled for transmission in subsequent PUSCH opportunities, ensuring URLLC latency requirements are met while eventually delivering eMBB data with acceptable delay.
Solution Approach 2:
The patent uses feedback mechanisms where the network device receives the SR on PUCCH, recognizes the URLLC service requirement, and provides appropriate uplink grants for both the URLLC data and the pending eMBB data. This feedback loop ensures that prioritizing URLLC does not permanently harm eMBB throughput.
Data Source
Figure 1~2(c)
Figure 3~4a
Figure 4b~5
AI summary
This application provides a communications method and apparatus that are relate to the field of communications technologies. The method includes: triggering, by a terminal device, a scheduling request SR; if a PUCCH carrying the SR and a PUSCH carrying a first data packet overlap in time domain of a first uplink resource, obtaining a processing status of the PUSCH on the first uplink resource; and sending, based on the processing status of the PUSCH on the first uplink resource, the PUCCH or the PUSCH on an overlapping time domain resource. According to the foregoing method, when the PUCCH carrying the SR and the PUSCH overlap in time domain of the first uplink resource, the terminal device considers the processing status of the PUSCH on the first uplink resource, and may determine, based on the processing status of the PUSCH on the first uplink resource, to send the PUCCH or the PUSCH on the overlapping time domain resource. This ensures efficiency of sending the uplink information on the overlapping time domain resource.