UE CAG Configuration Updates After NPN Access Denial

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

User Equipment (UE) faces challenges in autonomously updating Closed Access Group (CAG) related configurations when accessing Non-Public Networks (NPNs) for localized services, particularly when access is denied or validity/restriction criteria are not met, leading to inefficient network selection and access control.

Innovation Solution

A method for UE to autonomously update CAG configurations upon receiving a downlink NAS message, including adding, deleting, or maintaining CAG-IDs based on validity or restriction information, ensuring compliant network access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If UE autonomously updates CAG configuration based on access denial, then network access control compliance is improved, but device complexity increases

Engineering Contradiction:
Improvenetwork access control complianceVSAvoidconfiguration update mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The UE autonomously updates its own CAG configuration based on access denial information received from the network, without requiring manual intervention or complex network-controlled updates. The device self-manages the configuration by adding, deleting, or modifying CAG-IDs based on the received access control information.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The network provides feedback to the UE through DL NAS messages containing access denial information when the UE attempts to access a CAG cell without proper authorization. The UE uses this feedback to automatically update its CAG configuration, ensuring compliance with network access control policies.

Inventive Principle:
Principle #23Feedback

2Speed

If UE attempts to access CAG cells without configuration validation, then network selection speed is improved, but access control reliability deteriorates

Engineering Contradiction:
Improvenetwork selection speedVSAvoidaccess control compliance
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The UE performs preliminary validation of CAG configuration by checking whether CAG-IDs in its configuration match the CAG-IDs of available CAG cells before attempting access. This preliminary check prevents unauthorized access attempts and ensures compliance with access control policies while maintaining efficient network selection.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If UE maintains comprehensive CAG configuration information, then access control precision is improved, but information storage requirements increase

Engineering Contradiction:
Improveaccess control precisionVSAvoidconfiguration data volume
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The UE maintains CAG configuration information in a structured format where each CAG-ID is associated with specific PLMN identifiers and access control parameters. This organized approach stores only the necessary configuration data for each CAG cell, avoiding redundant information while maintaining precise access control capabilities.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12418859B2UE auto update cag configuration when accessing pni-npn as hosting network for localized services
Publication Date: 2025.09.16 MEDIATEK INC
  • US12418859B2 patent drawing
  • US12418859B2 patent drawing
  • US12418859B2 patent drawing

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.