Dual Active Protocol Stack for Concurrent RACH Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G mobile communication systems are limited in handling multiple Random Access Channel (RACH) procedures simultaneously, leading to delayed critical services and user experience issues due to restrictions on concurrent RACH operations in User Equipment (UE) devices.
Innovation Solution
The implementation of a Dual Active Protocol Stack (DAPS) capability in User Equipment (UE) allows for the simultaneous handling of multiple RACH procedures by enabling a secondary stack to perform RACH operations concurrently with the primary stack, enabling the UE to connect to multiple cells or beams simultaneously and reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a single RACH procedure is handled at a time in UE, then device complexity is reduced, but service latency increases and critical services are delayed
Solution Approach 1:
The protocol stack is segmented into a primary stack and a secondary stack, allowing independent handling of multiple RACH procedures. The primary stack manages initial access and control plane functions, while the secondary stack handles user plane data transmission, enabling parallel RACH operations without increasing overall system complexity.
Solution Approach 2:
The patent introduces a vertical dimension to the protocol architecture by adding a secondary protocol stack that operates alongside the primary stack. This dimensional expansion allows simultaneous RACH procedures on different stacks, transforming a sequential single-stack limitation into a parallel multi-stack capability.
2Productivity
If multiple RACH procedures are handled simultaneously in a single protocol stack, then service latency is reduced, but protocol complexity and resource conflicts increase
Solution Approach 1:
The protocol stack is segmented into a primary stack and a secondary stack, allowing independent handling of multiple RACH procedures. The primary stack manages initial access and control plane functions, while the secondary stack handles user plane data transmission, enabling parallel RACH operations without increasing overall system complexity.
Solution Approach 2:
The secondary protocol stack is designed with multi-functionality, capable of handling both control plane and user plane RACH procedures. This universal design allows the secondary stack to independently manage RACH operations for multiple services simultaneously, increasing throughput while maintaining manageable complexity through standardized handling procedures.
3Reliability
If a single protocol stack is used for all RACH procedures, then resource management is simplified, but critical services are delayed when RACH procedures conflict
Solution Approach 1:
The protocol stack is segmented into a primary stack and a secondary stack, allowing independent handling of multiple RACH procedures. The primary stack manages initial access and control plane functions, while the secondary stack handles user plane data transmission, enabling parallel RACH operations without increasing overall system complexity.
Solution Approach 2:
The secondary protocol stack acts as an intermediary layer that mediates between multiple RACH procedures and the network. It provides a buffer and coordination mechanism, allowing critical services to be prioritized and handled independently without being blocked by non-critical RACH operations on the primary stack.
Data Source
AI summary
The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system is provided. The method includes detecting triggering of a first random access channel (RACH) procedure running on a primary stack at the UE upon detection of a RACH trigger condition on the primary stack, while the UE is connected to at least one cell, detecting triggering of a second RACH procedure while the first RACH procedure is ongoing in the UE, wherein the second RACH procedure is different from the first RACH procedure, enabling a dual active protocol stack (DAPS) capability to initiate a secondary stack for handling the second RACH procedure, performing the first RACH procedure on the primary stack and the second RACH procedure on the secondary stack, simultaneously, and disabling the secondary stack upon successful completion of the second RACH procedure.


