HARQ Process Management with ID Mapping for Sidelink Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communication systems supporting sidelink, uplink, and downlink transmissions, the lack of a common base station to manage hybrid automatic repeat request (HARQ) processes between transmitting and receiving terminals leads to potential errors and interference when incorrect HARQ process IDs are set, especially in mode 2 resource allocation where terminals autonomously manage resources.
Innovation Solution
A method and apparatus for managing HARQ processes that involve receiving and mapping HARQ process IDs through a control channel, generating new IDs when necessary, and transmitting full or release signals to ensure efficient use of HARQ processes across uplink, downlink, and sidelink transmissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If terminals autonomously manage HARQ processes in mode 2 resource allocation, then resource allocation flexibility is improved, but HARQ process management reliability deteriorates due to lack of centralized coordination
Solution Approach 1:
The patent segments HARQ process management by introducing separate management mechanisms for different transmission types (UL, DL, SL) with distinct data source IDs. Each transmission type maintains its own HARQ process space, allowing autonomous terminal management in SL while preserving centralized control in UL/DL, thus resolving the contradiction between flexibility and reliability.
Solution Approach 2:
The patent introduces an intermediary mapping mechanism (HARQ process ID mapping table) that translates between original HARQ process IDs and mapped HARQ process IDs. This intermediary layer enables autonomous terminals to manage SL HARQ processes independently while preventing conflicts with UL/DL processes, maintaining both flexibility and reliability.
2Productivity
If HARQ process IDs are shared between UL and SL transmissions, then resource utilization efficiency is improved, but transmission reliability deteriorates due to potential ID conflicts
Solution Approach 1:
The patent applies local quality by introducing data source ID-specific HARQ process management. Different data source IDs (g-B-0 for UL, g-B-1 for DL, g-B-2 for SL) have dedicated HARQ process ID spaces and mapping tables. This allows efficient resource utilization through ID reuse across different sources while maintaining transmission reliability through isolated management.
Solution Approach 2:
The patent adds a new dimension (data source ID) to HARQ process management, transforming the traditional single-dimension HARQ ID space into a multi-dimensional space. This allows the same HARQ process ID to be used across different transmission types without conflict, improving resource utilization while maintaining reliability through dimensional separation.
3Measurement precision
If a mapping table for HARQ process IDs is maintained at each terminal, then HARQ process accuracy is improved, but device complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-configuring mapping tables at each terminal before SL communication begins. The mapping between data source IDs and HARQ process ID spaces is established in advance, allowing accurate HARQ process identification without real-time complex calculations, thus improving accuracy while limiting complexity growth.
Data Source
AI summary
A method for managing HARQ processes in a terminal of a mobile communication system supporting uplink, downlink, and sidelink transmission is provided. The method for managing HARQ processes includes: receiving a data source ID and a HARQ process ID set to at least one of the uplink, downlink, and sidelink transmission through a control channel; searching a new HARQ process ID mapped corresponding to the combination of the data source ID and the HARQ process ID with reference to the HARQ process table; and operating a HARQ process corresponding to the new HARQ process ID.


