DAPS Handover Random Access Logging and Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP RRC technical specifications do not clearly define how a UE should handle multiple random access procedures during a Dual Active Protocol Stack (DAPS) handover, leading to ambiguity in logging RLF or SHR reports.
Innovation Solution
The UE determines the content of reports to be sent to the network after executing a DAPS handover, including decisions on whether to log information from the first or second random access procedure, or both, based on 3GPP specifications or network configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE logs multiple random access procedures during DAPS handover, then the network can optimize handover performance, but the report complexity and processing overhead increase
Solution Approach 1:
The patent segments the random access procedure information into distinct fields within the RLF report structure. Each random access attempt (first and second RACH procedures) is recorded with separate parameters including preamble ID, time stamp, and outcome status. This segmentation allows the network to process specific failure points without being overwhelmed by a monolithic complex report structure.
Solution Approach 2:
Instead of having the network request specific detailed information about each random access attempt, the patent inverts the approach by having the UE proactively log and report all relevant random access procedure information in a structured format. This inversion reduces back-and-forth signaling complexity and allows the network to receive comprehensive data for optimization purposes.
2Loss of information
If the UE includes detailed random access information in reports, then the network can identify failure causes, but the message size and transmission overhead increase
Solution Approach 1:
The patent extracts only the essential and most relevant parameters from the complete random access procedure data for inclusion in the RLF report. Specifically, it extracts key fields such as preamble ID, time stamp, and outcome status for each random access attempt, while omitting less critical detailed information. This extraction approach ensures that the network receives sufficient data to identify failure causes without being burdened by excessive data volume.
3Loss of information
If the UE logs both first and second RACH procedures, then complete handover information is captured, but the processing time and memory usage increase
Solution Approach 1:
The patent implements preliminary logging of random access procedure information during the handover execution itself. The UE maintains a structured buffer that automatically records each random access attempt's key parameters (preamble ID, time stamp, outcome) as they occur during the DAPS handover process. This preliminary action ensures that when the RLF report needs to be generated, the data is already organized and ready, significantly reducing the processing time required at report generation while maintaining complete information capture.
Data Source
AI summary
A communication device of a communications network can perform a dual active protocol stack (“DAPS”) handover (“HO”) from a source cell associated with a first network node of the communications network to a target cell associated with a second network node of the communications network. Performing the DAPS HO can include performing a first random access (“RA”) procedure with the source cell and performing a second RA procedure with the target cell. The communication device can determine RA content to include in a report associated with the DAPS HO. The communication device can transmit the report to a third network node of the communications network toward a target cell.