UE CAG Configuration Updates for PNI-NPN Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in enabling user equipment (UE) to autonomously update Closed Access Group (CAG) configurations when accessing Public Network Integrated Non-Public Networks (PNI-NPN) for localized services, as current methods do not effectively manage access control and network slicing to prevent unauthorized access.
Innovation Solution
A method for UE to autonomously update CAG-related configurations by processing downlink NAS messages, including adding, deleting, or maintaining CAG identifiers based on validity and restriction information, ensuring compliant access to CAG cells within the PLMN.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If UE autonomously updates CAG configuration by processing downlink NAS messages, then access control efficiency is improved and unauthorized access is prevented, but device complexity increases due to additional configuration management functions
Solution Approach 1:
The UE autonomously updates its own CAG configuration by processing downlink NAS messages received from the network. The device independently determines whether to add, delete, or keep CAG identifiers based on validity and restriction information in the messages, without requiring manual configuration or complex network-controlled updates, thus improving access control efficiency while keeping device complexity manageable
Solution Approach 2:
The UE pre-configures CAG identifiers in its configuration list before attempting network access. By having CAG configuration information ready in advance based on received downlink NAS messages, the UE can quickly determine access eligibility without real-time configuration delays, improving access control speed and efficiency
2Reliability
If UE dynamically updates CAG configurations to prevent unauthorized access, then network security is improved, but loss of time occurs due to configuration processing and access verification
Solution Approach 1:
The UE receives and processes downlink NAS messages in advance to build and maintain a CAG configuration list before actual network access attempts. By having CAG identifiers and their validity/restriction information prepared beforehand, the UE can perform rapid access verification without time-consuming configuration processing during critical access moments, thus improving network security while minimizing time loss
3Reliability
If UE maintains strict CAG access control for PNI-NPN, then unauthorized access is prevented, but ease of operation decreases due to limited network access flexibility
Solution Approach 1:
The UE dynamically manages its CAG configuration by adding, deleting, or retaining CAG identifiers based on validity and restriction information received in downlink NAS messages. This dynamic approach allows the UE to adapt its access control list in real-time, maintaining strict security for authorized networks while automatically adjusting to changing network conditions and user permissions, thus balancing security with operational flexibility
Solution Approach 2:
The UE uses feedback from downlink NAS messages containing validity and restriction information to automatically update its CAG configuration. The network provides feedback about which CAG identifiers are currently valid and accessible, and the UE adjusts its access control accordingly, maintaining security while simplifying operation as users don't need to manually manage complex access rules
Data Source
AI summary
A method of UE autonomously updating a CAG related configuration upon receiving a downlink NAS message is provided. If a CAG-ID is included in an allowed CAG-IDs list of the CAG related configuration and is supported by a CAG cell in a PLMN, then UE may attempt to access the CAG cell in the PLMN. If the access is denied, e.g., UE receives a DL NAS message with a cause value, then UE needs to update the CAG related configuration. If the CAG-ID is not associated with any validity or restriction information, then the CAG-ID should be deleted from the CAG related configuration. If the CAG-ID is associated with validity or restriction information and corresponding validity or restriction criteria are not met, then the CAG-ID should not be deleted from the CAG related configuration.