RAN Node Identity Disambiguation via Standardized I-RNTI Profiles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current 5G RAN architecture faces challenges in disambiguating the source gNB identity from the I-RNTI signaled by UE during RRC resume, especially across different vendor boundaries, due to the lack of standardized structure in I-RNTI, leading to interoperability issues between gNBs from different vendors.
Innovation Solution
A method is introduced to determine and transmit Local Node Identifiers between neighboring network nodes, including an I-RNTI profile and a Local Node Identifier, to standardize the structure of I-RNTI and enable flexible length selection, allowing accurate identification of the RAN node hosting the UE context in RRC Inactive state, even across different vendor networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a standardized structure for I-RNTI is not implemented, then each vendor can use proprietary mechanisms to resolve I-RNTI, but inter-vendor interoperability fails at gNB boundaries
Solution Approach 1:
The patent applies parameter changes by modifying the I-RNTI structure to include a standardized Local Node ID field with specific bit allocation. The I-RNTI is restructured as: 10 bits for Local Node ID, 10 bits for UE Context ID, and 20 bits for gNB ID (for full I-RNTI). This parameter standardization enables reliable inter-vendor interoperability while maintaining manageable complexity through defined bit fields and encoding rules.
2Adaptability or versatility
If fixed-length Local Node ID is used in I-RNTI, then disambiguation is simplified, but flexibility in node identification is reduced
Solution Approach 1:
The patent implements dynamics by allowing the Local Node ID length to be configurable rather than fixed. The system can adapt the Local Node ID length based on network requirements, with the remaining bits allocated to UE Context ID. This dynamic allocation provides flexibility in adapting to different network scenarios while the standardized structure maintains manageable disambiguation complexity through clear bit field definitions.
3Ease of manufacture
If proprietary I-RNTI resolution mechanisms are used, then vendor-specific implementations work, but inter-vendor compatibility is lost
Solution Approach 1:
The patent applies universality by creating a standardized I-RNTI structure that works across all vendors while allowing optional proprietary extensions. The core structure with defined bit fields for Local Node ID, UE Context ID, and gNB ID provides a universal baseline that ensures inter-vendor interoperability. Vendors can implement this standardized structure and optionally add proprietary resolution mechanisms on top, maintaining both ease of implementation and cross-vendor compatibility.
Data Source
AI summary
A method performed by a first network node includes determining one or more Local node Identifiers. The method includes transmitting the one or more Local node Identifiers to a second network node neighboring the first network node, each of the one or more Local node Identifiers including: an Inactive-Radio Network Temporary Identifier, I-RNTI, profile valid for the first network node and associated with a full I-RNTI; and/or an I-RNTI profile valid for the first network node and associated with a short I-RNTI. The method includes transmitting a radio resource control, RRC, release message with suspend configuration to a user equipment, to transition the user equipment to RRC Inactive, the RRC release message including a Local node Identifier for the first network node and a UE context identifier.