5G-RG Authentication Key Selection for AUN3 Device Capability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems face challenges in ensuring secure communication between an authenticable non-3rd generation partnership project (AUN3) device and a 5G residential gateway (5G-RG) due to the need for generating a correct key based on whether the AUN3 device supports a 5G key hierarchy, which is not reliably determined.
Innovation Solution
A communication method where a terminal device reports its support for a first key hierarchy through a response message, enabling the network to select appropriate key derivation methods, and the 5G-RG generates keys accordingly to enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the terminal device does not report key hierarchy support status, then the communication protocol remains simple, but the key generation may be incorrect leading to security failures
Solution Approach 1:
The terminal device performs preliminary action by reporting its key hierarchy support status capability before the actual key generation process. This capability indication is included in the registration request or authentication message, allowing the network side to determine the appropriate key derivation method in advance, ensuring correct key generation without requiring complex trial-and-error procedures.
2Reliability
If the terminal device reports key hierarchy support status, then the key generation correctness is improved, but the signaling overhead increases
Solution Approach 1:
The capability indication information is merged with existing registration request messages or authentication messages that are already transmitted during the connection establishment process. By combining the capability indication with these necessary signaling messages, the patent avoids adding separate dedicated signaling exchanges, thereby improving key generation correctness while minimizing the increase in signaling overhead.
3Reliability
If different key derivation methods are used for different devices, then security is improved, but the system complexity increases
Solution Approach 1:
The system implements dynamic key derivation method selection based on the terminal device's reported capability. The network side determines the appropriate key derivation method (5G key hierarchy or non-5G key hierarchy) in real-time according to each device's characteristics, rather than using a fixed method for all devices. This dynamic adaptation ensures optimal security for each device type while maintaining system flexibility.
Solution Approach 2:
The patent changes the key derivation parameters (specifically the key hierarchy structure) based on the terminal device's capability. When the terminal supports 5G key hierarchy, the system uses 5G-specific key derivation parameters; when it doesn't support, the system switches to non-5G key derivation parameters. This parameter change approach allows the system to maintain security while adapting to different device capabilities without requiring fundamentally different system architectures.
Data Source
AI summary
Embodiments of this application provide a communication method that may include receiving an authentication request message configured to request an authentication network element to perform authentication on a terminal device. Sending an obtaining request message including an identifier of the terminal device and configured for requesting to obtain an authentication vector for the authentication. Receiving an obtaining response message including the authentication vector. Performing the authentication on the terminal device based on the authentication vector. Sending an authentication response message configured to indicate that the authentication succeeds and including a key. For the terminal device not configured to support a first key hierarchy, the key being an MSK key, the obtaining response message including indication information configured to indicate that the terminal device is not configured to support the first key hierarchy, in response to the indication information, generating the MSK key based on another key hierarchy.