AMF-Triggered UE Feature Validation for 5G Compliance Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the 5G system, there are no mechanisms for the 5G core network to detect whether a user equipment (UE) is non-compliant, i.e., not fully supporting mandatory or indicating incorrect support for optional features, leading to unexpected network behavior.
Innovation Solution
The proposed solution involves network validation of UE compliance through an access and mobility management function (AMF) or UE-initiated procedures using extensible authentication protocol (EAP) and user equipment certification validation (UCV) to verify the UE's support for system features, with the AMF sending triggers and receiving validation results to enable or disable features accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the network assumes UE supports mandatory features without validation, then the network procedure is simple, but non-compliant UEs may cause unexpected network behavior
Solution Approach 1:
The patent applies preliminary action by performing UE compliance validation before allowing the UE to access network features. The AMF triggers validation procedures (such as EAP authentication or UCV server validation) prior to feature enablement, ensuring the UE truly supports mandatory features before the network assumes compliance. This prevents non-compliant UEs from causing unexpected network behavior while maintaining a manageable validation process.
2Reliability
If the network validates UE compliance before enabling features, then UE compliance is reliably detected, but the validation procedure increases network complexity
Solution Approach 1:
The patent uses intermediary validation mechanisms including EAP authentication servers and UCV (UE Certification Validation) servers as mediators between the AMF and the UE compliance check. These intermediaries handle the complex validation logic externally, allowing the AMF to trigger validation without implementing all validation logic itself. This reduces the AMF's operational complexity while maintaining reliable compliance detection through specialized validation servers.
3Loss of information
If UEs indicate support for optional features without validation, then the network can know UE capability, but non-compliant UEs may still cause unexpected behavior
Solution Approach 1:
The patent implements feedback mechanisms where the network validates UE compliance indicators against actual UE capability through validation procedures. The AMF receives capability indications from the UE, triggers validation (such as EAP challenge-response or UCV server verification), and uses the validation result as feedback to determine whether to enable the indicated feature. This feedback loop ensures that only compliant UEs with accurate capability declarations can access features, preventing unexpected behavior while maintaining accurate capability information.
Data Source
AI summary
Methods and devices are disclosed for validating that a WTRU supports the use of network system features. In one example an AMF receives, from a WTRU, a registration request message indicating the WTRU intends to use a system feature of the network. The AMF sends a registration accept message to the WTRU indicating the system feature is supported by the network and the WTRU may use the feature on a condition the network validates the WTRU supports the system feature. A system feature validation trigger is sent for the WTRU to perform a system feature validation procedure with a user equipment certification validation (UCV) Server. The AMF receives, from the UCV Server, a validation result of the procedure indicating the WTRU is validated or not validated to use the system feature. The AMF sends the WTRU, a configuration update message based on the received validation result message.