Access Gateway Relocation for Slice-Compatible UE Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G networks face challenges in efficiently relocating access gateways during UE registration, particularly when the initially selected interworking function cannot support the network slices allowed for the user equipment, leading to incomplete or unsuccessful registration processes.
Innovation Solution
The proposed solution involves initiating a relocation command from the AMF to switch from an unsuitable interworking function to a suitable one, ensuring secure connectivity and completing the registration process via the new interworking function, using security keys and IPsec SA establishment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the initially selected interworking function is used for UE registration, then the registration process can be initiated, but the registration cannot be completed successfully when the interworking function does not support the required network slices
Solution Approach 1:
The AMF performs preliminary verification of network slice support capabilities before finalizing the interworking function selection for UE registration. This preliminary check prevents selecting an unsuitable interworking function, ensuring registration can proceed to completion without needing relocation.
Solution Approach 2:
The AMF acts as an intermediary between the UE and the interworking function, managing the relocation process when slice support is insufficient. The AMF coordinates the transition by selecting alternative interworking functions and managing the handover of registration context, ensuring seamless relocation.
2Adaptability or versatility
If a relocation command is sent from AMF to switch interworking functions, then suitable network slice support can be achieved, but additional signaling and processing steps are required
Solution Approach 1:
The AMF pre-identifies and pre-selects alternative interworking functions that support the required network slices before relocation is needed. This preliminary preparation reduces the time required during actual relocation, as the alternative is already identified and ready for immediate handover.
Solution Approach 2:
The system implements feedback mechanisms where the AMF receives status information about interworking function capabilities and UE registration progress. This feedback enables the AMF to make informed decisions about when relocation is necessary and to select the most appropriate alternative interworking function, optimizing the relocation process.
3Reliability
If connectivity with the target TNGF is not supported, then relocation cannot be completed, but the system must handle this failure case gracefully
Solution Approach 1:
The system performs preliminary connectivity verification between the AMF and the target TNGF before initiating UE registration relocation. This advance check ensures that the target TNGF is reachable and capable of accepting the relocated registration, preventing failed relocation attempts and improving overall reliability.
Solution Approach 2:
The system prepares backup alternative interworking functions in advance, creating a chain of fallback options. If the primary target TNGF is unavailable or unsupported, the system can seamlessly transition to the next alternative, cushioning against relocation failures and maintaining high reliability without requiring complex real-time decision-making.
Data Source
AI summary
Apparatuses, methods, and systems are disclosed for relocating an access gateway during UE registration. One apparatus includes an interface that communicates with a remote unit and with a plurality of network functions in a mobile communication network. The apparatus includes a processor that initiates registration of the remote unit with the mobile communication network and receives a relocation command from an AMF while the registration is ongoing, the relocation command containing an address of a first TNGF and a first security key. If connectivity with the first TNGF is supported, then the processor sends a first request to the first TNGF, the first request containing a remote unit identity and an AMF identity. However, if connectivity with the first TNGF is not supported, then the processor sends a relocation reject message to the AMF.