Non-Public Network Registration via Trusted Non-3GPP Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies limit terminals to accessing non-public networks only via 3GPP base stations, necessitating alternative access methods for certain scenarios.
Innovation Solution
A registration method and apparatus that allows terminals to access non-public networks through trusted non-3GPP access networks (TNAN), involving the exchange of identifiers and registration types between terminals, TNAN, and access and mobility management functions (AMF) to facilitate registration without relying on 3GPP networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If terminals access non-public networks via 3GPP base stations, then network access reliability is improved, but access flexibility and alternative access capability deteriorate
Solution Approach 1:
The patent segments the network access path into multiple independent routes: 3GPP access (via base stations) and non-3GPP access (via trusted non-3GPP access networks). This segmentation allows terminals to choose different access paths based on specific requirements, maintaining reliability through the established 3GPP path while gaining flexibility through alternative non-3GPP paths.
Solution Approach 2:
The patent introduces a trusted non-3GPP access network as an intermediary between the terminal and the 5G core network. This intermediary provides an alternative access route that maintains security and reliability while enabling flexible access scenarios where direct 3GPP access is unavailable or suboptimal.
2Loss of information
If terminals send complete registration information via non-3GPP access, then registration completeness is improved, but communication overhead and processing complexity worsen
Solution Approach 1:
The patent applies preliminary action by having the AMF pre-generate and store mapping relationships between second identifiers (authenticating identifiers) and keys before the terminal needs registration. When registration occurs, the TNAN can directly use these pre-established mappings to authenticate the terminal and derive keys without complex real-time computations, ensuring complete registration information exchange while reducing processing complexity.
Solution Approach 2:
The system enables self-service authentication where the TNAN autonomously authenticates the terminal using the second identifier and pre-stored mapping relationships, and automatically derives the corresponding keys without requiring intensive real-time verification from other network elements. This self-service mechanism reduces overall processing complexity while maintaining registration completeness.
Data Source
AI summary
A registration method includes sending, by a terminal, a first identifier of the terminal, a registration type and an identifier of a non-public network to be registered to a trusted non-3rd generation partnership project access network (TNAN). A registration method includes: receiving, by a TNAN, a first identifier of a terminal, a registration type and an identifier of a non-public network to be registered sent by the terminal; and sending, by the TNAN, a registration request to an access and mobility management function (AMF), in which, the registration request includes the first identifier, the registration type, and the identifier of the non-public network to be registered. A registration method includes receiving, by an AMF, a registration request sent by a TNAN, in which the registration request includes a first identifier, a registration type, and an identifier of a non-public network to which the terminal is to be registered.