UE Equivalent SNPN Management for 5G Mobility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a lack of discussion and disclosure regarding mobility improvements for Stand-alone Non-Public Networks (SNPN) in existing 5G system architectures, specifically regarding equivalent SNPN concepts.
Innovation Solution
The introduction of an equivalent SNPN concept in User Equipment (UE) that involves deleting Single Network Slice Selection Assistance Information (S-NSSAI) from the pending NSSAI stored in the UE when new allowed Network Slice Selection Assistance Information (NSSAI) is received for a current Stand-alone Non-Public Network (SNPN) or its equivalent, enhancing mobility and service continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the UE stores all received NSSAI information including equivalent SNPN in the pending NSSAI, then the UE can maintain comprehensive network slice information, but the mobility management complexity increases and service continuity cannot be ensured
Solution Approach 1:
The patent extracts and removes S-NSSAIs from the pending NSSAI when receiving new allowed NSSAI for current SNPN or equivalent SNPN. This extraction mechanism resolves the contradiction by selectively removing redundant information (S-NSSAIs that should not be pending) while maintaining necessary network slice information, thereby reducing management complexity without losing essential data.
Solution Approach 2:
The patent changes the state of S-NSSAIs from 'pending' to 'allowed' or 'rejected' based on the received NSSAI information. This parameter change approach allows the UE to dynamically update the status of network slice information, resolving the contradiction by ensuring only relevant S-NSSAIs remain in pending state while others are properly transitioned to their final states.
2Stability of the object's composition
If the UE does not delete S-NSSAIs from pending NSSAI when receiving new allowed NSSAI, then existing network slice information is preserved, but service continuity is disrupted and mobility is impaired
Solution Approach 1:
The patent performs preliminary deletion of S-NSSAIs from the pending NSSAI before finalizing the network slice selection. This preliminary action ensures that outdated or redundant S-NSSAIs are removed in advance, preventing service continuity disruptions during mobility events while maintaining stable network slice information composition.
Solution Approach 2:
The patent implements a feedback mechanism where the UE updates the pending NSSAI based on the received allowed NSSAI information. This feedback loop allows the UE to continuously monitor and adjust the network slice information, ensuring service continuity is maintained while preserving stable information composition through iterative updates.
3Ease of manufacture
If the UE manages NSSAI without equivalent SNPN concept, then the current system architecture is maintained, but mobility improvement and service continuity cannot be achieved
Solution Approach 1:
The patent extends the existing SNPN concept to include equivalent SNPN, making the network slice management mechanism universally applicable to both current and equivalent networks. This multi-functionality approach allows the same UE logic to handle both SNPN and equivalent SNPN cases, improving mobility management efficiency without requiring separate handling mechanisms that would complicate the architecture.
Solution Approach 2:
The patent introduces dynamic behavior to the UE's NSSAI management by enabling it to automatically detect and respond to equivalent SNPN conditions. This dynamic approach allows the UE to adapt its behavior based on the network state, improving mobility management efficiency while maintaining architectural simplicity through automated, state-driven decisions.
Data Source
AI summary
By introducing a concept such as an equivalent SNPN, mobility can be improved, service continuity can be improved, NSSAI can be appropriately managed, and an equivalent SNPN list can be appropriately managed. In a case that roaming is not performed and a UE receives a new allowed NSSAI for a current SNPN, the UE deletes one or more S-NSSAIs included in a new allowed NSSAI for the current SNPN and/or its equivalent SNPN from a pending NSSAI stored in the UE.