Unified Data Channel Design for URLLC Insertion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile communication systems face challenges in efficiently managing data channels, particularly in accommodating ultra-reliable low latency communications (URLLC) within the existing framework of enhanced mobile broadband (eMBB) transmissions.
Innovation Solution
The implementation of a unified architecture for uplink and downlink data channels in 5G systems, utilizing information-carrying filler bits, variable signal processing chains, and hybrid beamforming to support URLLC data insertion and traffic prioritization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If URLLC data is inserted into ongoing eMBB transmissions, then latency is reduced and reliability is improved, but resource allocation complexity and interference management become more difficult
Solution Approach 1:
The system segments the shared data channel into different resource regions (time-frequency resources) that can be dynamically allocated to either eMBB or URLLC traffic. This segmentation allows independent management of different traffic types while sharing the same physical channel, reducing the complexity of coordinating resource allocation between the two traffic types.
Solution Approach 2:
The patent implements dynamic resource allocation where the network can flexibly switch between eMBB and URLLC transmissions based on traffic demands. The system dynamically adjusts the resource allocation, modulation and coding schemes, and transmission parameters in real-time, allowing efficient accommodation of both traffic types without requiring fixed, complex pre-configuration.
2Loss of time
If URLLC traffic takes over resources allocated for eMBB traffic, then URLLC latency is reduced, but eMBB throughput and quality may deteriorate
Solution Approach 1:
The system performs preliminary actions by pre-configuring resource regions and transmission parameters that can be quickly activated for URLLC traffic when needed. The network prepares multiple candidate resource allocations and transmission schemes in advance, allowing rapid switching to URLLC mode without complex real-time calculations, thus reducing URLLC latency while maintaining eMBB service quality through pre-planned resource protection mechanisms.
Solution Approach 2:
The patent utilizes parameter changes by dynamically adjusting transmission parameters such as modulation order, coding rate, and resource allocation patterns based on traffic type. When URLLC traffic arrives, the system changes parameters to favor low-latency transmission while maintaining sufficient resources for eMBB through adaptive parameter selection, rather than fixed parameter assignments.
3Adaptability or versatility
If a unified architecture is used for uplink and downlink data channels, then system complexity is reduced and versatility is improved, but specific optimization for different traffic types becomes more challenging
Solution Approach 1:
The patent implements a unified data channel architecture where the same physical channel (PDSCH/PUSCH) serves multiple functions for both eMBB and URLLC traffic. The unified channel supports different transmission modes, resource allocation patterns, and parameter configurations through a single versatile framework, reducing the need for separate dedicated channels for each traffic type while maintaining the ability to optimize for specific traffic requirements through configurable parameters.
Data Source
AI summary
Systems, methods and instrumentalities are disclosed for decoding data. For example, it may be determined, in a current slot, whether data received in a previous slot is decoded successfully. The data received in the previous slot may be included in a Physical Downlink Shared Channel (PDSCH). If the data received in the previous slot is not decoded successfully, preemptive multiplexing information may be detected in a first search space. The data received in the previous slot may be decoded, for example, using detected preemptive multiplexing information. The preemptive multiplexing information may be of a current slot. The preemptive multiplexing information may be comprised in a first DCI. A second search space of the current slot may be searched. For example, the second search space may be searched for a second DCI. The first DCI and the second DCI may be different.