WO2021233340A1

WO2021233340A1 - Network registration method and apparatus

Info

Publication number: WO2021233340A1
Application number: PCT/CN2021/094613
Authority: WO
Inventors: 朱浩仁; 诸华林
Original assignee: 华为技术有限公司
Priority date: 2020-05-22
Filing date: 2021-05-19
Publication date: 2021-11-25
Also published as: CN113727342B; CN113727342A

Abstract

The present application provides a network registration method and apparatus. The method comprises: a terminal device obtains information of the terminal device on a temporary private network and online subscription information of the terminal device on a target private network, and a network device updates the information of the terminal device on the temporary private network in response to the reception of an online subscription update request sent from the terminal device, wherein the online subscription update request comprises the online subscription information of the terminal device on the target private network. In the network registration method provided in the present application, when the temporary private network initially registered by the terminal device and the target private network for the terminal device are the same network, the network registration method can improve the efficiency of the terminal device accessing the target private network.

Description

Method and device for network registration

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on May 22, 2020, the application number is 202010443482.3, and the application name is "Method and Apparatus for Online Registration", the entire content of which is incorporated into this application by reference.

Technical field

This application relates to the field of communications, and more specifically, to a method and device for network registration.

Background technique

In the wireless communication process, registration management is used for registration and de-registration between terminal devices and the network, and establish user context on the network. The UE must first register with the network if it wants to obtain the services provided by the network.

In the prior art, the process of a terminal device accessing a target private network is that the terminal device uses the default credential information assigned to the terminal device by the temporary private network, and obtains the online contract information of the terminal device on the target private network through the temporary private network. The terminal device can access the target private network after initial registration in the target private network according to the online contract information of the target private network. Among them, the temporary private network can obtain the online contract information of the terminal device on the target private network through a third-party platform.

Based on the above solution, when the temporary private network initially registered by the terminal device and the target private network of the terminal device are the same network, or the temporary private network initially registered by the terminal device is in the list of target private networks accessible by the terminal device In one case, after the terminal device initiates registration with the temporary private network, it also needs to initiate the initial registration with the target private network again, which results in delay and low access efficiency when the terminal device accesses the target private network.

Summary of the invention

This application provides a method and device for network registration. The method for network registration is applied in a scenario where a terminal device accesses a target private network. In the case that the temporary private network initially registered by the terminal device and the target private network of the terminal device are the same network, the network registration method can improve the efficiency of the terminal device accessing the target private network.

In the first aspect, a method for network registration is provided, and the method includes:

The access and mobility management function AMF network element obtains the information of the terminal device in the temporary private network. The AMF network element is the network element in the temporary private network. The information of the terminal device in the temporary private network includes the terminal device in the temporary private network. Context in the private network;

The AMF network element receives an online subscription update request sent from the terminal device, where the online subscription update request includes online subscription information of the terminal device on the target private network;

The AMF network element updates the information of the terminal device according to the online subscription information of the target private network.

In the method for network registration provided by the embodiments of this application, when the temporary private network initially registered by the terminal device and the target private network of the terminal device are the same network, the temporary private network is based on the obtained terminal device’s information and terminal information on the temporary private network. The online subscription information of the device on the target private network and the online subscription update request sent by the terminal device triggers the update of the terminal device’s temporary private network information, which avoids the need for the terminal device in the prior art to send to the target private network again. The registration process effectively improves the efficiency of terminal equipment accessing the target private network.

With reference to the first aspect, in some implementation manners of the first aspect, the updating the information of the terminal device includes:

The AMF network element updates the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, where the information of the terminal device in the target private network includes that the terminal device is in the target private network In the context.

With reference to the first aspect, in some implementation manners of the first aspect, the online subscription update request is carried in a non-access stratum NAS message.

Based on the above solution, the online subscription update request is carried in a NAS message, and the NAS message interaction does not depend on a certain registration process and can be initiated at any time.

With reference to the first aspect, in some implementations of the first aspect, the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.

The context of the terminal device in the temporary private network includes the identification information of the terminal device in the temporary private network. It should be understood that the context of the terminal device in the temporary private network also includes a context (for example, a subscription context, a security context) distinguished by the identification information of the terminal device in the temporary private network.

Exemplarily, the identification information of the terminal device in the temporary private network #1 is identification information A, and in the temporary private network #1, the contexts distinguished by the identification information A are the contracting context A and the security context A, respectively. In this case, the context of the terminal device in the temporary private network #1 includes: identification information A, subscription context A, and security context A.

With reference to the first aspect, in some implementation manners of the first aspect, the online subscription information of the target private network includes identification information of the terminal device in the target private network.

With reference to the first aspect, in some implementations of the first aspect, the online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used for Instruct the AMF network element to update the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes that the terminal device is in the target private network The context.

With reference to the first aspect, in some implementations of the first aspect, before the AMF network element updates the temporary private network information according to the online subscription information of the target private network, the method further includes:

The AMF network element receives an online subscription notification message sent from a third-party platform, where the online subscription notification message includes identification information of the terminal device in the temporary private network;

The AMF network element sends second indication information to the terminal device according to the online subscription notification message, where the second indication information is used to trigger an update of the information of the terminal device.

With reference to the first aspect, in some implementation manners of the first aspect, the second indication information is carried in a NAS message.

Based on the above solution, the network side can display the trigger update, and the UE side does not need to determine whether the identification information of the temporary private network and the target private network are the same according to the acquired identification information of the temporary private network and the identification information of the target private network.

Combined with the first aspect, in some implementations of the first aspect,

The AMF network element sends an authentication request message to the unified data management UDM network element. The UDM network element is a network element in the temporary private network. The authentication request message is used to instruct the UDM network element to authenticate the terminal device. The authentication request message includes the identification information of the terminal device in the target private network;

The AMF network element receives an authentication request response message sent by the UDM network element, where the authentication request response message is used to indicate that the authentication is performed successfully;

The AMF network element sends an acquisition request message to the UDM network element, where the acquisition request message is used to request subscription information of the terminal device in the target private network;

The AMF network element receives the subscription information of the terminal device in the target private network sent by the UDM network element;

The AMF network element updates the information of the terminal device according to the subscription information of the terminal device in the target private network.

As an implementation manner, the AMF sends the first acquisition request message to the UDM. It can be understood that the AMF can send the first acquisition request message to the UDM through the authentication service function AUSF. Specifically, the AMF sends the first acquisition request message to the AUSF, and after the AUSF receives the first acquisition request message, the AUSF sends the first acquisition request message to the UDM.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes:

The AMF network element instructs the UDM network element to delete the information of the terminal device in the temporary private network.

In the second aspect, a method for network registration is provided, and the method includes:

The terminal device obtains the information of the terminal device in the temporary private network and the online subscription information of the terminal device in the target private network, and the information of the terminal device in the temporary private network includes the context of the terminal device in the temporary private network;

The terminal device sends an online subscription update request to the access and mobility management function AMF network element. The online subscription update request includes the online subscription information of the terminal device on the target private network, and the online subscription update request is used to trigger the terminal device Update of the information.

With reference to the second aspect, in some implementation manners of the second aspect, the update of the information of the terminal device includes:

The information of the terminal device in the temporary private network is updated to the information of the terminal device in the target private network, where the information of the terminal device in the target private network includes the context of the terminal device in the target private network.

With reference to the second aspect, in some implementation manners of the second aspect, the online subscription update request is carried in a non-access stratum NAS message.

With reference to the second aspect, in some implementations of the second aspect, the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.

With reference to the second aspect, in some implementation manners of the second aspect, the online subscription information of the target private network includes identification information of the terminal device in the target private network.

With reference to the second aspect, in some implementations of the second aspect, the online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used for Instruct the AMF network element to update the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes that the terminal device is in the target private network The context.

With reference to the second aspect, in some implementations of the second aspect, the terminal device sends an online subscription update request to the access and mobility management function AMF network element, including:

The terminal device determines that the identification information of the terminal device in the temporary private network is the same as the identification information of the terminal device in the target private network;

The terminal device sends the online subscription update request to the AMF network element.

Based on the above solution, the terminal device side can determine whether to trigger the update according to the acquired identification information of the terminal device on the temporary private network and the identification information of the terminal device on the target private network.

With reference to the second aspect, in some implementations of the second aspect, before the terminal device sends an online subscription update request to the access and mobility management function AMF network element, the method further includes:

The terminal device receives second indication information sent by the AMF network element, where the second indication information is used to trigger an update of the terminal device information.

With reference to the second aspect, in some implementation manners of the second aspect, the second indication information is carried in a NAS message.

In a third aspect, a device for network registration is provided. The device for network registration includes a processor for implementing any of the methods described in the first aspect.

Optionally, in some implementation manners, the device for network registration may further include a transceiver for implementing any of the methods described in the first aspect.

Optionally, in some implementation manners, the network registration device may further include a memory for storing instructions.

In a fourth aspect, a device for network registration is provided. The device for network registration includes a processor for implementing any of the methods described in the second aspect.

Optionally, in some implementation manners, the device for network registration may further include a transceiver for implementing any of the methods described in the second aspect.

In a fifth aspect, a communication device is provided, and the communication device is configured to execute the first aspect and the method in any one of the possible implementation manners of the first aspect.

It should be noted that the device in the foregoing embodiment may be a network device, or may be a chip applied to the network device or other combination devices or components that can realize the functions of the foregoing network device. When the communication device is a network device, the transceiver unit may be a transmitter and a receiver, or an integrated transceiver, which may include an antenna and a radio frequency circuit, and the processing unit may be a processor, such as a baseband chip. When the device is a component with the above-mentioned network device function, the transceiver unit may be a radio frequency unit, and the processing module may be a processor. When the device is a chip system, the transceiver unit may be an input/output interface of the chip system, and the processing module may be a processor of the chip system, such as a central processing unit (CPU).

In a sixth aspect, a communication device is provided, and the communication device is configured to execute each module or unit of the method in the second aspect and any one of the possible implementation manners of the second aspect.

It should be noted that the device in the foregoing embodiment may be a terminal device, or may be a chip applied to a terminal device, or other combination devices, components, etc. that can realize the functions of the foregoing terminal device. When the communication device is a terminal device, the transmitting module may be a transmitter, which may include an antenna and radio frequency circuit, etc., the receiving module may be a receiver, which may include an antenna and radio frequency circuit, etc., and the processing module may be a processor, such as a baseband chip. When the device is a component with the above-mentioned terminal device function, the sending module may be a radio frequency unit, and the processing module may be a processor. When the device is a chip system, the sending module may be an output interface of the chip system, and the processing module may be a processor of the chip system, such as a central processing unit (CPU).

In a seventh aspect, a network device or other combination device, component, etc. that can realize the functions of the network device described above is provided, including a memory and a processor. This memory is used to store instructions. The processor is configured to execute the instruction, so that the terminal device executes the method provided in the first aspect.

In an eighth aspect, a terminal device or other combination device, component, etc. that can realize the functions of the above-mentioned terminal device is provided, including a memory and a processor. This memory is used to store instructions. The processor is configured to execute the instructions, so that the terminal device executes the method provided in the above second aspect.

In a ninth aspect, a communication device is provided. The communication device includes a processor, for example, used in a wireless communication device to implement the function or method involved in the first aspect. The communication device may be, for example, a chip system. . In a feasible implementation manner, the chip system further includes a memory for storing program instructions and data necessary to realize the functions of the method provided in the first aspect.

In a tenth aspect, a communication device is provided. The communication device includes a processor, for example, used in a wireless communication device to implement the function or method involved in the second aspect. The communication device may be, for example, a chip system. . In a feasible implementation manner, the chip system further includes a memory, which is used to store program instructions and data necessary to realize the functions of the method provided in the second aspect.

The chip system in the above aspect may be a system on chip (SOC), or a baseband chip, etc., where the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem, and an interface module.

In an eleventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a network device, cause the network device to execute the method provided in the first aspect.

In a twelfth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a terminal device, cause the terminal device to execute the method provided in the second aspect.

In a thirteenth aspect, a computer program product containing instructions is provided, which when running on a network device, causes the network device to execute the method provided in the first aspect.

In a fourteenth aspect, a computer program product containing instructions is provided, which when running on a terminal device, causes the terminal device to execute the communication method provided in the second aspect.

In a fifteenth aspect, a network device is provided, which includes a module for executing the method provided in the first aspect.

In a sixteenth aspect, a terminal device is provided, which includes a module for executing the method provided in the second aspect.

In a seventeenth aspect, a communication system is provided, including the aforementioned terminal device and network device.

Description of the drawings

Fig. 1 is a network architecture suitable for an embodiment of the present application.

Fig. 2 is another network architecture applicable to the embodiment of the present application.

FIG. 3 is a schematic flowchart of a method 300 for network registration provided by an embodiment of the present application.

FIG. 4 is a schematic flowchart of a method 400 for network registration according to an embodiment of the present application.

FIG. 5 is a schematic flowchart of a method 500 for network registration according to an embodiment of the present application.

FIG. 6 is a schematic flowchart of a method 600 for network registration according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of a method 700 for network registration according to an embodiment of the present application.

FIG. 8 is a schematic diagram of a network registration apparatus 800 provided by an embodiment of the present application.

FIG. 9 is a schematic diagram of a network registration apparatus 900 provided by an embodiment of the present application.

FIG. 10 is a schematic diagram of a network registration device 1000 provided by an embodiment of the present application.

FIG. 11 is a schematic diagram of a network registration device 1100 provided by an embodiment of the present application.

FIG. 12 is a schematic structural diagram of a user equipment 20 applicable to an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings. Obviously, the described embodiments are a part of the embodiments of the present application, rather than all the embodiments.

Figure 1 shows a network architecture applicable to the embodiments of the present application.

As shown in Figure 1, each part involved in the network architecture will be described separately below.

1. Terminal device 110: It can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices with wireless communication functions, as well as various forms of terminals or devices, mobile stations (mobile stations, MS), User equipment (UE), soft terminals, etc., such as water meters, electricity meters, sensors, etc.

Exemplarily, the terminal device in the embodiment of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, and a terminal device. , Wireless communication equipment, user agent or user device. The user equipment can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and wireless communication. Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, user equipment in the future 5G network or future evolution of the public land mobile network (PLMN) The user equipment or the user equipment in the future Internet of Vehicles, etc., are not limited in this embodiment of the present application. The terminal device in the embodiment of the present application may also be a device installed or installed in the above-mentioned various devices, such as a chip and/or a circuit structure.

As an example and not a limitation, in the embodiments of the present application, wearable devices can also be referred to as wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.

In addition, in the embodiments of the present application, the terminal device may also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the development of information technology in the future. Its main technical feature is to pass items through communication technology. Connect with the network to realize the intelligent network of human-machine interconnection and interconnection of things. In the embodiment of the present application, the IOT technology can achieve massive connections, deep coverage, and power saving of the terminal through, for example, narrowband (NB) technology. In addition, in the embodiments of this application, the terminal equipment may also include sensors such as smart printers, train detectors, gas stations, etc. The main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from access network equipment, and Send electromagnetic waves to transmit uplink data to the access network equipment.

2. (Radio access network, (R)AN) 120: used to provide network access for authorized terminal equipment in a specific area, and can use different quality transmissions according to the level of terminal equipment and service requirements. tunnel.

(R)AN can manage wireless resources, provide access services for terminal equipment, and complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network. (R)AN can include base stations in traditional networks, or other A network element or entity that can implement the access network function.

Exemplarily, the access network device in the embodiment of the present application may be any communication device with a wireless transceiving function that is used to communicate with a terminal device. The access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), node B (Node B, NB), base station controller (base first) AMFtion controller, BSC), base transceiver station (base transceiver first AMFtion, BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (wireless fidelity, WIFI) system access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., also It can be 5G, such as NR, gNB in the system, or transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system, or it can also constitute gNB Or a network node of a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions. The DU is responsible for processing the physical layer protocol and real-time services, and realizes the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU+AAU. It is understandable that the access network device may be a device including one or more of the CU node, the DU node, and the AAU node. In addition, the CU can be divided into access network equipment in the access network (radio access network, RAN), or the CU can be divided into access network equipment in the core network (core network, CN). This application does not Make a limit.

3. User plane network element 130: used for packet routing and forwarding and quality of service (QoS) processing of user plane data, etc.

In a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In the future communication system, the user plane network element may still be a UPF network element, or may also have other names, which is not limited in this application.

4. Data network network element 140: used to provide a network for transmitting data.

In a 5G communication system, the data network element may be a data network (DN) network element. In the future communication system, the data network network element may still be a DN network element, or may also have other names, which is not limited in this application.

5. Access management network element 150: Mainly used for mobility management and access management, etc., and can be used to implement other functions other than session management in the mobility management entity (mobility management entity, MME) function, for example, legal Monitoring and access authorization/authentication functions.

In a 5G communication system, the access management network element may be an access and mobility management function (AMF). In the future communication system, the access management network element may still be AMF, or may also have other names, which is not limited by this application.

6. Session management network element 160: Mainly used for session management, terminal device Internet Protocol (IP) address allocation and management, selection of end points that can manage user plane functions, policy control and charging function interfaces, and downlink Data notification, etc.

In a 5G communication system, the session management network element may be a session management function (session management function, SMF) network element. In the future communication system, the session management network element may still be an SMF network element, or may also have other names, which is not limited in this application.

7. Policy control network element 170: a unified policy framework used to guide network behavior, and provide policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).

In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. In a 5G communication system, the policy control network element may be a policy control function (PCF) network element. In the future communication system, the policy control network element may still be a PCF network element, or may also have other names, which is not limited in this application.

8. Authentication server 180: used for authentication services, generating keys to realize two-way authentication for terminal devices, and supporting a unified authentication framework.

In a 5G communication system, the authentication server may be an authentication server function (authentication server function, AUSF) network element. In the future communication system, the authentication server function network element may still be an AUSF network element, or may also have other names, which is not limited by this application.

9. Data management network element 190: used to process terminal device identification, access authentication, registration, and mobility management, etc.

In a 5G communication system, the data management network element may be a unified data management (UDM) network element; in a 4G communication system, the data management network element may be a home subscriber server (HSS) network In the future communication system, the unified data management can still be a UDM network element, or it can have other names, which is not limited in this application.

10. Application network element 1100: used for data routing affected by applications, access to network open function network elements, and interaction with the policy framework for policy control, etc.

In a 5G communication system, the application network element may be an application function (AF) network element. In the future communication system, the application network element may still be an AF network element, or may also have other names, which is not limited by this application.

11. Network slice selection network element 1200: used to implement access mapping between terminal devices and network slices, and provide appropriate network slice access for terminal devices.

In a 5G communication system, the application network element may be a network slice selection function (NSSF) network element. In the future communication system, the application network element may still be an NSSF network element, or may also have other names, which is not limited by this application.

It should also be understood that FIG. 1 is just an example and does not constitute any limitation to the protection scope of the present application. The method for registration provided by the embodiment of the present application may also involve a network element not shown in FIG. 1. For example, the method for registration provided by the embodiment of the present application also relates to a network storage network element, wherein It is used to maintain real-time information of all network functions and services in the network.

In a 5G communication system, the network storage network element may be a network repository function (NRF) network element. In the future communication system, the network storage network element may still be an NRF network element, or may also have other names, which are not limited by this application.

It is understandable that the aforementioned network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform). For the convenience of description, in the follow-up of this application, the access management network element is the AMF, the data management network element is the UDM network element, the session management network element is the SMF network element, and the user plane network element is the UPF network element.

Further, the AMF network element is abbreviated as AMF, the UDM network element is abbreviated as UDM, the SMF network element is abbreviated as SMF, and the UPF network element is abbreviated as UPF. That is, the AMF described later in this application can be replaced with an access management network element, UDM can be replaced with a data management network element, SMF can be replaced with a session management network element, and UPF can be replaced with a user plane network element.

For convenience of description, in the embodiments of the present application, the device is an AMF entity and a UDM entity as examples to describe the method for registration. For the implementation method of the device being a chip in the AMF entity and a chip in the UDM entity, please refer to the device The specific descriptions of the AMF entity and UDM entity are respectively, and the introduction will not be repeated.

In the network architecture shown in Figure 1, the terminal equipment is connected to the AMF through the N1 interface, the RAN is connected to the AMF through the N2 interface, and the RAN is connected to the UPF through the N3 interface. The UPFs are connected through the N9 interface, and the UPFs are interconnected through the N6 interface DN. SMF controls UPF through the N4 interface. AMF interfaces with SMF through N11 interface. AMF obtains terminal equipment subscription data from the UDM unit through the N8 interface, and SMF obtains terminal equipment subscription data from the UDM unit through the N10 interface.

It should be understood that the foregoing network architecture applied to the embodiments of the present application is only an example, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can implement the functions of the foregoing various network elements is applicable to the present application. Application examples.

For example, in some network architectures, network function network element entities such as AMF, SMF network elements, PCF network elements, BSF network elements, and UDM network elements are all called network function (NF) network elements; or In some network architectures, a collection of network elements such as AMF, SMF network elements, PCF network elements, BSF network elements, UDM network elements, etc. can all be called control plane function network elements.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (time division duplex) , TDD) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system, new wireless (new) radio, NR) or future networks, etc. The 5G mobile communication system described in this application includes 5G mobile communication systems with non-independent networking (non-first AMFndalone, NSA) or independent networking (first AMFndalone, SA) 5G mobile communication system. The technical solution provided in this application can also be applied to future communication systems, such as the sixth-generation mobile communication system. The communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, and a device-to-device (D2D) communication system. Internet of Things (IoT) communication system or other communication systems.

In the embodiment of the present application, the terminal device or the access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Moreover, the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided in accordance with the embodiments of the application. For example, the execution subject of the method provided in this embodiment of the present application may be a terminal device or an access network device, or a functional module in the terminal device or the access network device that can call and execute the program.

In addition, various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

The embodiments of this application mainly involve UE, (R)AN, AMF, SMF, AUSF, and UDM in the network architecture shown in FIG. 1.

Figure 2 shows another network architecture applicable to the embodiments of the present application.

As shown in FIG. 2, the network architecture includes a provisioning server (PS) 210, a device 220 that provides target subscription information, a default credential server (DCS) 230, a terminal device 240, and a temporary private network 250.

Hereinafter, each part included in the network architecture will be described.

The PS 210 is used to obtain the target contract information of the terminal device 240.

In the embodiment of this application, the owner of PS 210 is not limited.

As an implementation manner, the PS 210 may belong to the target private network.

As another implementation manner, the PS 210 may belong to a private network that provides online subscription services.

As yet another implementation manner, the PS 210 may belong to a third-party platform.

In the embodiment of this application, the specific deployment location of the PS 210 is not limited.

For example, when the PS 210 can belong to the target private network, the PS 210 can be deployed in the PCF of the target private network. Alternatively, when the PS 210 can belong to the target private network, the PS 210 can also be deployed in the UDM of the target private network. Or, when the PS 210 can belong to the target private network, the PS 210 can also be deployed as a new functional network element.

The device 220 for providing target subscription information is configured to provide the terminal device 240 with target subscription information, where the target subscription information is the subscription information for the terminal device 240 to request access to the target private network.

In this embodiment of the present application, the owner of the device 220 that provides target subscription information is not limited.

As an implementation manner, the device 220 for providing target subscription information may belong to the target private network.

As another implementation manner, the device 220 for providing target subscription information may belong to a private network that provides online subscription services.

As yet another implementation manner, the device 220 for providing target contract information may belong to a third-party platform.

The DCS 230 is used to authenticate the request of the terminal device 240. After the terminal device 240 is authenticated by the DCS 230, the terminal device 240 can use a restricted user plane connection or control plane channel to obtain target subscription information from the PS 210.

The terminal device 240 is used to request to obtain target subscription information.

Specifically, the terminal device 240 performs initial registration in the temporary private network and obtains default credential information. The terminal device uses the default credential information to perform authentication in the DCS 230. After the terminal device 240 is authenticated by the DCS 230, the terminal device 240 can obtain the target contract information from the temporary private network. After acquiring the target contract information, the terminal device 240 de-registration from the temporary private network 250, and uses the target contract information to register with the target private network.

The temporary private network 250 is used to obtain target contract information from the PS 210.

Among them, the temporary private network 250 includes (R)AN, AMF, SMF, AUSF, and UDM network elements in the network architecture of FIG.

In the embodiment of this application, the type of temporary private network is not specifically limited.

For example, the temporary private network may be a non-public network and there are two types: standalone NPN (standalone npn, SNPN) network. Alternatively, the temporary private network may be a non-independent network integrated NPN network (PNI-NPN).

It should be understood that FIG. 2 is only a schematic diagram of a network architecture to help those skilled in the art understand the method of the present application, and is not a limitation on the network architecture that can apply the technical solution of the present application.

Hereinafter, the method of network registration provided by the present application will be described in detail with reference to FIG. 3 to FIG. 7.

FIG. 3 shows a schematic flowchart of a method 300 for network registration provided by an embodiment of the present application. It should be understood that FIG. 3 is only for illustration and does not constitute any limitation to the present application.

As shown in FIG. 3, the method 300 includes step 310 to step 330, and these steps are described in detail below.

It should be noted that the temporary private network in Figure 3 includes AMF, SMF, AUSF, and UDM in the system architecture shown in Figure 1. In other words, the AMF, SMF, AUSF, and UDM appearing below are all network elements in the same temporary private network.

It should also be understood that the method executed by the AMF as the execution body in FIG. 3 may also be executed by other network elements. In FIG. 3, only the AMF is the execution body for introduction.

Step 310: Obtain the information of the terminal device on the temporary private network and the online contract information of the terminal device on the target private network.

Specifically, step 310 includes step 310a and step 310b.

In step 310a, the terminal device obtains the information of the terminal device on the temporary private network and the online contract information of the terminal device on the target private network. It can be understood that the terminal device obtains the information of the terminal device on the temporary private network and the terminal device from the temporary private network. Online signing information on the target private network,

In step 310b, the temporary private network obtains the information of the terminal device on the temporary private network and the online contract information of the terminal device on the target private network. The private network obtains the online contract information of the terminal device on the target private network. In the embodiment of the present application, the information of the terminal device in the temporary private network includes the context of the terminal device in the temporary private network.

The context of the terminal device in the temporary private network includes the identification information of the terminal device in the temporary private network. It should be understood that the context of the terminal device in the temporary private network also includes the context (e.g., subscription context, security context) distinguished by the identification information of the terminal device in the temporary private network.

Wherein, the online contract information of the terminal device in the target private network includes the identification information of the terminal device in the target private network.

In the embodiments of the present application, acquiring information about the terminal device in the temporary private network can be understood as the information acquired by the network side (for example, AMF and/or UDM) during the initial registration process of the terminal device in the temporary private network.

In the embodiment of this application, the online contract information of the terminal device on the target private network is obtained. It can be understood that after the terminal device performs the initial registration in the temporary private network, the terminal device obtains the target private network’s information from the PS through the temporary private network. Online signing information.

Specifically, the terminal device uses the credential information/certificate information (for example, the default SUPI) to perform initial registration in the temporary private network, and the terminal device also carries instruction information, which is used to instruct the terminal device to obtain the terminal device’s access to the target private network. After the temporary private network obtains the online contract information of the target private network from the PS according to the instruction information, the temporary private network sends the online contract information to the terminal device.

Optionally, in some implementation manners, the online subscription information of the terminal device on the target private network may also include the terminal device target private network identification list, credential information/certificate information, configuration information (for example, DNN, URSP, etc.). Wherein, the target private network identifier list of the terminal device is a list of network identifiers of the target private network that the terminal device can access.

In the embodiment of the present application, the manner in which the PS obtains the online subscription information of the terminal device on the target private network is not specifically limited.

As an implementation manner, the PS can obtain the online subscription information of the terminal device on the target private network through the target private network of the terminal device.

As another implementation manner, the PS can obtain the online contract information of the terminal device on the target private network through other private networks that can provide the online contract information of the target private network.

Exemplarily, the target private network of the terminal device is private network A, and private network B may provide the online contract information of the terminal device in the target private network A. In this case, the PS can obtain the online contract information of the terminal device on the target private network from the private network B.

As yet another implementation manner, the PS can obtain the online contract information of the terminal device on the target private network through a third party. For example, the third party may be a platform that provides online subscription information of terminal devices on the target private network.

In the embodiment of the present application, the manner in which the identification information of the terminal device is expressed is not specifically limited.

For example, in the (4th generation, 4G) communication protocol, the new identification information of the terminal device and/or the new identification information of the terminal device may be International Mobile Subscriber Identity (IMSI).

For example, in the 5G communication protocol, the new identification information of the terminal device and/or the new identification information of the terminal device may be a subscription permanent identifier (SUPI). Alternatively, in the 5G communication protocol, the new identification information of the terminal device and/or the new identification information of the terminal device may be a subscription concealed identifier (SUCI).

In the embodiment of this application, the type of temporary private network is not specifically limited. For example, the temporary private network may be an SNPN type private network. Or, the temporary private network may be a PNI-NPN type private network.

Step 320: The terminal device sends an online subscription update request to the temporary private network.

Wherein, the online subscription update request includes the online subscription information of the terminal device in the target private network, where the online subscription information of the target private network includes the identification information of the terminal device in the target private network.

Optionally, in some implementations, the online subscription update request is carried in a non-access stratum (NAS) message. Among them, the NAS message exchange does not depend on a certain registration process and can be initiated at any time. For example, the NAS message may be a N1NAS message.

Optionally, in some embodiments, the online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network. The first indication information is used to instruct the AMF to place the terminal device in the temporary private network. The information of is updated to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes the context of the terminal device in the target private network.

The first indication information is used to instruct the AMF to update the information of the terminal device in the temporary private network to the information of the terminal device in the target private network. For example, the first indication information is used to instruct the AMF to update the identification information of the terminal device of the terminal device in the temporary private network to the identification information of the terminal device of the terminal device in the target private network. For example, the first indication information is used to instruct the AMF to update the contract context of the terminal device in the temporary private network to the contract context of the terminal device in the target private network. For example, the first indication information is used to instruct the AMF to update the security context of the terminal device in the temporary private network to the security context of the terminal device in the target private network.

The context of the terminal device in the target private network includes the identification information of the terminal device in the target private network. It should be understood that the context of the terminal device in the target private network also includes a context (for example, a subscription context, a security context) distinguished by the identification information of the terminal device in the target private network.

Exemplarily, the identification information of the terminal device in the target private network #1 is identification information A, and in the target private network #1, the contexts distinguished by the identification information A are the contracting context A and the security context A, respectively. In this case, the context of the terminal device in the target private network #1 includes: identification information A, subscription context A, and security context A.

In the embodiment of the present application, the method of triggering the information update of the temporary private network is not specifically limited.

As an implementation, the information update of the temporary private network can be triggered by the terminal device, as follows:

Before the terminal device sends an online subscription update request to the temporary private network, it also includes:

The terminal device determines that the identification information of the terminal device on the temporary private network is the same as the identification information of the terminal device on the target private network;

The terminal device sends an online subscription update request to the AMF.

Where the terminal device sends an online subscription update request to the AMF, it can be understood that the terminal device triggers the network side to update the temporary private network information. In other words, when the terminal device determines that the terminal device’s identification information on the temporary private network is the same as the terminal device’s identification information on the target private network, the terminal device triggers the network side to update the temporary private network by sending an online subscription update request to the AMF. information.

Among them, the terminal device can obtain the identification information of the terminal device on the temporary private network through the broadcast information of the temporary private network.

In the embodiment of the present application, whether the temporary private network and the target private network are the same network can be determined through the network identifier.

Exemplarily, taking SNPN as an example, an SNPN network can be determined by a PLMN ID and a network identifier (network identifier, NID). Therefore, an SNPN network identifier can be formed by using PLMN ID+NID. That is to say, it can be determined whether the SNPN network is the same network according to the PLMN ID+NID.

Exemplarily, taking PNI-NPN as an example, a PNI-NPN network can be determined by PLMN ID and network identifier (cell access group identifier, CAG ID), so a PNI-NPN network can be formed by using PLMN ID + CAG ID Of the logo. That is to say, whether the PNI-NPN network is the same network can be determined according to the PLMN ID+CAG ID.

Based on the solution triggered by the terminal device side, the terminal device side can determine whether to trigger the information update of the temporary private network according to the identification information of the terminal device on the temporary private network and the identification information of the terminal device on the target private network.

As another implementation method, the information update of the temporary private network can be triggered through the network side, as follows:

Before AMF updates the temporary private network information based on the online contract information of the target private network, the method also includes:

AMF receives the online subscription notification message sent from the third-party platform, and the online subscription notification message includes the identification information of the terminal device in the temporary private network;

The AMF sends second indication information to the terminal device according to the online subscription notification message, and the second indication information is used to indicate that the information of the terminal device is triggered to be updated.

That is, after the terminal device receives the second indication information sent by the network-side AMF, the terminal device sends an online subscription update request to the AMF.

Wherein, the second indication information is carried by a non-access stratum NAS message. As an implementation manner, the second indication information can be obtained in the following manner:

After the PS completes the update according to the acquired target subscription information of the terminal device, the PS sends the second indication information to the AMF, or the PS sends the second indication information to the AMF through the NEF. After receiving the second indication information, the AMF sends the second indication information to the terminal device through the N1NAS message.

Among them, the third-party platform is a platform that can provide the contract information of the terminal device in the target private network. For example, the third-party platform may be PS (see Figure 2).

Based on the display and triggering scheme on the network side, the terminal device side does not need to obtain the identification information of the terminal device on the temporary private network and the identification information of the terminal device on the target private network.

In the embodiment of the present application, there is no specific limitation on the registration update method that triggers the network side to update the information of the temporary private network.

As an implementation manner, the mobile registration update or periodic registration update can be used to trigger the network side to update the information of the temporary private network.

As another implementation manner, the online subscription registration update can be used to trigger the network side to update the information of the terminal device in the temporary private network.

It should be understood that the online subscription registration update process is a newly defined registration process for this application, which is different from the registration process in the prior art (for example, initial registration, mobility registration, periodic registration or emergency registration) .

As yet another implementation manner, the online subscription information update can be used to trigger the network side to update the information of the terminal device in the temporary private network.

It should be understood that the online subscription information can be carried and sent to the network side by an independent NAS message (for example, a N1NAS message), and the independent NAS message interaction does not depend on a certain registration process and can be initiated at any time.

Step 330: The temporary private network updates the information of the terminal device according to the online subscription information of the target private network.

In the embodiment of the present application, updating the information of the terminal device includes: the AMF network element updates the information of the terminal device in the temporary private network to the information of the terminal device in the target private network. Wherein, the information of the terminal device in the target private network includes the context of the terminal device in the target private network.

In the embodiment of this application, the temporary private network updates the information of the temporary private network according to the online subscription information of the target private network. According to the online subscription information of the terminal device on the target private network carried in the online subscription update request, the temporary private network information is updated.

In the embodiment of this application, it further includes:

The AMF network element sends an authentication request message to the unified data management UDM network element. The UDM network element is a network element in a temporary private network. The authentication request message is used to instruct the UDM network element to authenticate the terminal device. The authentication request message includes the terminal device's Identification information in the target private network;

The AMF network element receives the authentication request response message sent by the UDM network element, and the authentication request response message is used to indicate that the authentication process is executed successfully;

The AMF network element sends an acquisition request message to the UDM network element, and the acquisition request message is used to request the subscription information of the terminal device in the target private network;

The AMF network element receives the signing information of the terminal device in the target private network sent by the UDM network element;

The AMF network element updates the information of the terminal device according to the contract information of the terminal device in the target private network.

Among them, the AMF network element is also used to instruct the UDM network element to delete the information of the terminal device in the temporary private network.

As an implementation manner, the AMF sends an acquisition request message to the UDM. It can be understood that the AMF can send an acquisition request message to the UDM through the AUSF. Specifically, the AMF sends the acquisition request message to the AUSF, and after the AUSF receives the acquisition request message, the AUSF sends the acquisition request message to the UDM.

In the embodiment of the present application, the method for UDM to authenticate the terminal device is not specifically limited.

Specifically, the authentication can be understood as an authentication and security process for the terminal device.

For example, UDM can perform authentication and security procedures for terminal devices according to the EAP-AKA' authentication method. Alternatively, UDM can perform authentication and security procedures for terminal devices according to the 5G AKA authentication method.

Among them, the authentication process can trigger the re-authentication of the terminal device according to the authentication function of the process described in section 6.1.3.1 of 3GPP TS 33.501. Alternatively, the authentication process can trigger the re-authentication of the terminal device according to the authentication function performed in the process described in section 6.1.3.2 of 3GPP TS 33.501.

Optionally, in some implementation manners, when the terminal device performs initial registration, the temporary private network and the target private network are not the same network, the temporary private network may also trigger a network update or notify the terminal device to trigger a network update.

As an implementation method, take SNPN as an example to introduce.

In the case where the O-SNPN and T-SNPN that the terminal device accesses are not in the same network, after the O-SNPN subscription update is completed, the O-SNPN can notify the (R)AN to trigger the network update or notify the terminal device to trigger the network update.

Specifically, in SNPN, O-SNPN notifies (R)AN to trigger network update or notifies terminal equipment to trigger network update, including the following two ways:

Method 1: O-SNPN obtains new mobility restrictions (MR) information of the terminal equipment, where MR is part of the contract context. After the RAN receives the MR, it can switch the terminal equipment to a suitable network. As an implementation manner, in the case that the current network does not meet the MR, one can be reselected from the network that meets the MR.

Method 2: After O-SNPN obtains the new MR of the terminal device, the terminal device will actively switch to the appropriate target network after receiving it.

In SNPN, when the O-SNPN and T-SNPN that the terminal device accesses are not the same network, after the O-SNPN contract update is completed, O-SNPN can notify the (R)AN to trigger the network update or notify the terminal device to trigger the network renew.

It should be noted that the network update in the SNPN scenario can be performed after UDM performs network authentication and security procedures. Alternatively, the network update in the SNPN scenario can also be performed before the AMF updates the context.

As another implementation manner, PNI-NPN is taken as an example for introduction.

Specifically, in PNI-NPN, O-PNI-NPN notifies (R)AN to trigger network update or notifies terminal equipment to trigger network update, including the following two methods:

Method 1: O-PNI-NPN obtains the new MR of the terminal equipment. After the RAN receives the MR, it judges whether the current network is in the CAG List according to the information of the closed access group list (cell access group list, CAG List). If If not, switch the terminal device to an available CAG network (included in the CAG List).

Method 2: After the O-PNI-NPN obtains the new MR of the terminal device, the terminal device determines whether the current network is in the CAG List according to the CAG List information after receiving the new MR. If it is determined that the current network is not in the CAG List, then Actively switch to an available CAG network (included in the CAG List).

It should be noted that the network update in the PNI-NPN scenario can be performed after the terminal device's temporary private network and the target private network are not the same network. Alternatively, the network update in the PNI-NPN scenario can also be performed before the terminal device sends the non-initial registration request message to the AMF.

The network registration method provided by the embodiments of this application is in the case where the temporary private network initially registered by the terminal device and the target private network of the terminal device are the same network, or when the temporary private network is the target private network accessible by the terminal device In the case of one in the list, the temporary private network triggers the terminal device’s online subscription information based on the acquired terminal device’s information on the temporary private network and the terminal device’s online subscription information on the target private network, as well as the online subscription update request sent by the terminal device. The information of the temporary private network is updated to avoid the need for the terminal device to register with the target private network again in the prior art, thereby effectively improving the efficiency of the terminal device accessing the target private network. In addition, in the case that the temporary private network and the target private network are not the same network, the temporary private network can also trigger a network update or notify a terminal device to trigger a network update.

For ease of understanding, the following takes the temporary private network and the target private network as both SNPN and the terminal device as the UE as an example, and the specific embodiments of the network registration provided by the present application will be introduced with reference to Figs. 4-7. It should be understood that the methods shown in FIGS. 4 to 7 are merely illustrative, and do not constitute any limitation to the present application. For example, the methods corresponding to Figures 4 to 7 are also applicable to scenarios where both the temporary private network and the target private network are PNI-NPN. Specifically, in the scenario where the temporary private network and the target private network are both PNI-NPN, the network identification (PLMN ID+NID) of SNPN in Figures 4 to 7 should be replaced with the network identification of PNI-NPN (PLMN ID) +CAG ID).

FIG. 4 shows a schematic flowchart of a method 400 for network registration provided by an embodiment of the present application.

As shown in FIG. 4, the method 400 includes steps 410 to 450, which are described in detail below.

It should be noted that T-SNPN/T-SNPNS is used to provide the UE’s target subscription information, T-SNPN/T-SNPNS can be the UE’s target private network, and T-SNPN/T-SNPNS can also be the target of the UE. Other private networks for subscription information, T-SNPN/T-SNPNS may also be a third-party platform that can provide UE's target subscription information.

Step 410: Obtain the information of the temporary private network and the online subscription information of the target private network.

Specifically, the information of the temporary private network includes the context acquired by the UE in the O-SNPN. For example, the UE's subscription context and/or security context in O-SNPN.

Specifically, the online subscription information of the target private network includes the identification information of the UE in the T-SNPN. For example, the IMSI can be used to represent the identification information of the UE in the T-SNPN.

In the embodiments of the present application, acquiring the information of the temporary private network can be understood as the information acquired by the network side (for example, AMF and/or UDM) during the initial registration process of the UE in the O-SNPN.

In the embodiment of the present application, acquiring the online subscription information of the target private network can be understood as the online subscription information of the target private network obtained by the UE from the PS through the O-SNPN after the UE performs initial registration in the O-SNPN.

Optionally, in some embodiments, the online subscription information of the target private network may also include a UE target private network identification list, credential information/certificate information, configuration information (for example, DNN, URSP, etc.). Among them, the UE target private network identifier list is a list of T-SNPN network identifiers that the UE can access.

Step 420: The UE determines whether O-SNPN and T-SNPN are the same network.

It should be noted that before the UE determines whether the O-SNPN and T-SNPN are the same network, it also includes: the UE obtains the identification information of the temporary private network (PLMN ID+NID) and the identification information of the target private network (PLMN ID+NID) ). That is, after the UE obtains the identification information of the temporary private network and the identification information of the target private network, the UE determines whether the O-SNPN and the T-SNPN are the same network.

In the embodiment of this application, the UE determines whether O-SNPN and T-SNPN are the same network, including:

O-SNPN identification information (PLMN ID+NID) is the same as T-SNPN identification information (PLMN ID+NID), or O-SNPN identification information (PLMN ID+NID) is included in the T-SNPN identification list In the case of, determine that O-SNPN and T-SNPN are the same network; otherwise, determine that O-SNPN and T-SNPN are different networks. Among them, the UE can obtain the identification information (PLMN ID+NID) of the O-SNPN that the UE accesses according to the broadcast information of the O-SNPN.

In the case where O-SNPN and T-SNPN are the same network, step 421 is executed.

In step 421, when O-SNPN and T-SNPN are in the same network, a mobility registration update or periodic registration update is triggered.

Specifically, the UE triggers mobility registration update or periodic registration update, refer to step 422 to step 450 below.

Step 422, the UE sends a registration request #1 to the (R)AN.

The registration request #1 includes at least UE identification information #1, and the UE identification information #1 is the identification information of the UE in the target private network. For example, SUCI or SUPI can be used to represent the identification information of the UE in the target private network.

Optionally, in some implementation manners, the registration request #1 further includes indication information #1 and/or UE identification information #2.

Wherein, the indication information #1 is used to indicate to update various contexts distinguished by the UE identity, such as security context and contract context. That is to say, the indication information #1 is used to indicate that the context of the UE in the temporary private network is updated to the context of the UE in the target private network. Specifically, the indication information #1 is used to indicate that the UE identification information #2 is updated to the UE. Identification information #1. It should be noted that the indication information #1 can be carried by a newly defined field, or the indication information #1 can be carried by an existing field in the multiplexing network.

Among them, UE identification information #2 is the identification information of the UE in the temporary private network. For example, UE identification information #2 may be SUCI. For example, UE identification information #2 may also be SUPI. For example, the UE identification information #2 may also be PEI.

It should be noted that UE identification information #1 and UE identification information #2 are identification information allocated by different private networks.

Exemplarily, UE identification information #1 is identification information allocated by private network A, and UE identification information #2 is identification information allocated by private network B.

It should also be understood that when UE identification information #1 and UE identification information #2 are identification information allocated by the same private network, UE identification information #1 and UE identification information #2 may also be different.

Step 423, the RAN sends a registration request #1 to the AMF.

Step 424, trigger the AMF to re-execute the authentication and security process.

As an implementation manner, in the case that the registration request #1 only includes the UE identification information #1, the UE identification information #1 is used to trigger the AMF to re-execute the authentication and security procedures.

As another implementation manner, when the registration request #1 includes the first indication information and the UE identification information #1, the first indication information is used to trigger the AMF to re-execute the authentication and security process.

Specifically, the AMF can trigger the re-authentication of the UE by triggering the Nausf_UEAuthentication service, the Nudm_UEAuthentication service, and the authentication function according to the procedures described in 3GPP TS 33.501 section 6.1.3.1 or section 6.1.3.2. For the specific re-execution of the authentication and security process, see step 425 to step 427 below.

Step 425: AMF sends authentication request #1 to AUSF.

Wherein, the authentication request #1 carries UE identification information #1 (for example, SUCI/SUPI).

As an implementation, AMF can use the service-oriented interface Nausf_UEAuthentication_Authenticate to send authentication request message #1 to AUSF.

Step 426: AUSF sends an authentication acquisition request #1 to UDM.

Wherein, the authentication acquisition request #1 carries UE identification information #1 (for example, SUCI/SUPI).

As an implementation manner, AUSF can use the service-oriented interface Nudm_UEAuthentication_Get to send authentication acquisition request #1 to UDM.

In step 430, the UDM determines the authentication method and executes the authentication process.

The authentication method can be EAP-AKA’, or the authentication method can be 5G AKA.

The authentication process can trigger the re-authentication of the UE according to the authentication function of the process described in section 6.1.3.1 of 3GPP TS 33.501. Alternatively, the authentication process can trigger the re-authentication of the UE according to the authentication function performed in the process described in section 6.1.3.2 of 3GPP TS 33.501.

In the embodiment of this application, after the AMF confirms that the UDM re-authentication is successful, the method further includes:

AMF uses UE identification information #1 to obtain target subscription information from UDM, and AMF generates a new subscription context based on the target subscription information. The new subscription context is the context of the UE in the target private network;

The AMF sends indication information to the UDM, and the indication information is used to instruct the UDM to delete the context of the UE in the temporary private network (for example, the network element information registered in the UDM during temporary registration).

AMF can use the service interface Nudm_SDM_Get to retrieve the contract context from UDM. Specifically, AMF sends a request to UDM. The request needs to carry new UE identification information (UE identification information #1), old UE identification information (UE identification information #2), and special instructions, which are used to indicate UDM Delete the old context (for example, the network element information registered in UDM during temporary registration). After receiving the request, the UDM deletes the old context according to the indication and the old UE identification, and returns a new subscription context based on the new UE identification information (UE identification information #1). Specifically, for the process of the AMF acquiring the new contract context, refer to step 441 to step 444 below.

In step 441, the AMF sends an acquisition request #1 to the UDM.

The acquisition request #1 includes UE identification information #1 and UE identification information #2.

Optionally, in some implementation manners, the acquisition request #1 may further include indication information #2, and the indication information #2 is used to instruct the UDM to delete the context of the UE in the temporary private network according to the UE identification information #2. For example, indication information #2 instructs UDM to delete the network element information registered in UDM during temporary registration.

As an implementation manner, AMF can use the servicing interface Nudm_SDM_Get to send get request #1 to UDM.

Wherein, the AMF sends the acquisition request #1 to the UDM, which can be understood as the AMF can send the acquisition request #1 to the UDM through the AUSF. Specifically, the AMF sends the acquisition request #1 to the AUSF, and after the AUSF receives the acquisition request #1, the AUSF sends the acquisition request #1 to the UDM.

Step 442: UDM deletes the context of the UE in the temporary private network, and obtains target subscription information.

Among them, the target subscription information is the subscription information of the UE in the target private network.

UDM deletes the context of the UE in the temporary private network. It can be understood that the UDM deletes the context acquired by the UE in the temporary private network in the UDM according to the UE identification information #2 included in the acquisition request #1.

As an implementation manner, the UDM can directly delete the context acquired by the UE in the temporary private network in the UDM according to the acquired UE identification information #2.

As another implementation manner, the UDM can also delete the context acquired by the UE in the temporary private network in the UDM according to the instruction information #2.

The UDM obtains the target subscription information, which can be understood as the UDM obtains the target subscription information according to the UE identification information #1.

In step 443, the UDM sends an acquisition response #1 to the AMF.

Wherein, the acquisition response #1 includes target contract information.

In step 444, after the AMF notifies the SMF to release the restricted session according to the registration request #1, the AMF deletes the context of the UE in the temporary private network, and completes the new subscription/security update.

Specifically, the AMF generates a new security context and a new contract context according to the target contract information carried in the received acquisition response #1, and completes the new contract and security update.

Optionally, in some embodiments, when there is no restricted session in the AMF, the AMF generates a new security context and a new subscription context based on the target subscription information carried in the received acquisition response #1, and completes the new subscription. And security updates.

In step 450, the UE registration update is completed.

The UE registration update is completed, and the process is that the AMF sends a registration response message (registration response) to the UE, and the UE replies with a registration complete message to the network.

Compared with the prior art, the network registration method 400 provided in the embodiment of the present application can update the UE identification information (for example, SUPI), security context, and subscription context during mobility registration or periodic registration.

FIG. 5 shows a schematic flowchart of a method 500 for network registration according to an embodiment of the present application.

As shown in FIG. 5, the method 500 includes steps 510 to 550, which are described in detail below.

Step 510: Obtain the information of the temporary private network and the online subscription information of the target private network.

The method of obtaining the online subscription information of the target private network in step 510 is the same as the method of obtaining the online subscription information of the target private network in step 410, and will not be described in detail here.

In step 520, the UE determines whether O-SNPN and T-SNPN are the same network.

The method of step 520 is the same as the method of step 420, and will not be described in detail here.

In the case that O-SNPN and T-SNPN are the same network, step 521 is executed.

In step 521, when O-SNPN and T-SNPN are in the same network, the UE triggers an online subscription registration update.

Wherein, the online subscription registration update is used to instruct the network side to update identification information (for example, the identification information of the UE in the temporary private network) and various contexts (for example, the subscription context and security context of the UE in the temporary private network).

Specifically, for the online contract registration update process, refer to step 522 to step 550 below.

Step 522: The UE sends a registration request #1 to the (R)AN.

In step 523, the RAN sends a registration request #1 to the AMF.

Step 524: Trigger the AMF to re-execute the authentication and security procedures.

Specifically, the AMF is triggered to re-execute the authentication and security process according to the type of online contract and registration.

Step 525: AMF sends authentication request #1 to AUSF.

Step 526: AUSF sends an authentication acquisition request #1 to UDM.

In step 530, the UDM determines the authentication method and executes the authentication process.

Step 541: AMF sends an acquisition request #1 to UDM.

Step 542: The UDM deletes the context of the UE in the temporary private network, and obtains target subscription information.

In step 543, the UDM sends an acquisition response #1 to the AMF.

The above-mentioned method from step 525 to step 543 is the same as the method from step 425 to step 443 respectively, and will not be described in detail here.

In step 544, after the AMF notifies the SMF to release the restricted session according to the online subscription registration type, the AMF deletes the context of the UE in the temporary private network, and completes the new subscription and security update.

In step 550, the UE registration update is completed.

Compared with the prior art, the network registration method 500 provided in the embodiment of the present application can update the UE identification information (for example, SUPI), the security context, and the subscription context during the non-initial registration process. Compared with the method 400, the method 500 for network registration provided in the embodiment of the present application defines a new registration update process, which can update the UE identification information (for example, SUPI), the security context, and the contract context.

FIG. 6 shows a schematic flowchart of a method 600 for network registration provided by an embodiment of the present application.

As shown in FIG. 6, the method 600 includes steps 610 to 656, and these steps are described in detail below.

Step 610: Obtain the information of the temporary private network and the online subscription information of the target private network.

The method of obtaining the online subscription information of the target private network in step 610 is the same as the method of obtaining the online subscription information of the target private network in step 410, and will not be described in detail here.

In step 620, the UE determines whether O-SNPN and T-SNPN are the same network.

The method of step 620 is the same as the method of step 420, and will not be described in detail here.

In step 621, when O-SNPN and T-SNPN are in the same network, the UE triggers an update of online subscription information.

Specifically, for the online subscription information update process, refer to step 622 to step 656 below.

Step 622: The UE sends an online subscription update request #1 to the (R)AN.

In the embodiment of the present application, the online subscription update request #1 is carried by an independent NAS message (for example, a N1NAS message). The NAS message interaction does not depend on a certain registration process and can be initiated at any time.

Wherein, the online subscription update request #1 includes UE identification information #1, and UE identification information #1 is the identification information of the UE in the target private network. For example, SUCI or SUPI can be used to represent the identification information of the UE in the target private network.

Optionally, in some implementation manners, the online subscription update request #1 further includes indication information #1 and/or UE identification information #2.

Among them, the indication information #1 is used to indicate that the context of the UE in the temporary private network is updated to the context of the UE in the target private network. Specifically, the indication information #1 is used to indicate that the UE identification information #2 is updated to the UE identification information. #1. It should be noted that the indication information #1 can be carried by a newly defined field, or the indication information #1 can be carried by an existing field in the multiplexing network.

Step 623: The RAN sends an online subscription update request #1 to the AMF.

In step 624, the AMF triggers the re-execution of the authentication and security process according to the online subscription update request #1.

Step 625: AMF sends authentication request #1 to AUSF.

Step 626: AUSF sends an authentication acquisition request #1 to UDM.

In step 630, the UDM determines the authentication method and executes the authentication process.

In step 651, the AMF sends an acquisition request #1 to the UDM.

In step 652, the UDM deletes the context of the UE in the temporary private network and obtains new subscription information.

In step 653, the UDM sends an acquisition response #1 to the AMF.

The above-mentioned method from step 625 to step 653 is the same as the method from step 425 to step 453 respectively, and will not be described in detail here.

In step 654, after the AMF notifies the SMF to release the restricted session according to the online subscription update request #1, the AMF deletes the old context and completes the new subscription and security update.

In step 645, the AMF sends an online subscription update response #1 to the (R)AN.

Step 656: (R)AN sends an online subscription update response #1 to the UE.

After the UE receives the online subscription update response #1, the UE replies to the network with a registration completion message.

The method 600 for network registration provided in the embodiment of the present application uses an independent NAS interaction process to enable a UE device to update UE identification information (such as SUPI), security context, and subscription context at any time.

FIG. 7 shows a schematic flowchart of a method 700 for network registration provided by an embodiment of the present application.

As shown in FIG. 7, the method 700 includes steps 710 to 740, and these steps are described in detail below.

Step 710: Obtain the information of the temporary private network and the online subscription information of the target private network.

Wherein, the method of step 710 is the same as the method of step 410, and will not be described in detail here.

Step 720: The PS sends online subscription notification information #1 to the AMF.

The online subscription notification information #1 includes the identification information of the UE in the temporary private network (for example, IMSI/GPSI). It should be understood that the temporary private network is the network where the UE performs the initial registration.

As an implementation manner, the PS can directly send the online subscription notification information #1 to the AMF, as shown in FIG. 7.

As another implementation manner, the PS can also indirectly send the online contract notification information #1 to the AMF through the network exposure function (NEF).

In step 730, the AMF sends a NAS message to the UE.

Among them, the NAS message is used to indicate the trigger to update the context of the UE in the temporary private network and the identification information of the UE in the temporary private network. For example, the NAS message may be an N1 mode NAS message.

The AMF sends the NAS message to the UE. It can be understood that after the AMF receives the online subscription notification information #1 sent by the PS, the AMF sends the NAS message to the UE according to the online subscription information #1.

After the UE receives the NAS message (e.g., N1NAS) sent by the AMF on the downlink, it updates the UE’s identification information in the temporary private network (e.g. SUPI) and the UE’s context in the temporary private network (e.g., Security context and contract context).

In step 740, the NAS message triggers the update of the identification information of the UE in the temporary private network and the context of the UE in the temporary private network.

In the embodiment of this application, the NAS message triggers the update of the UE's identification information in the temporary private network and the context of the UE in the temporary private network, including the following three methods:

Manner 1: Perform step 423 to step 450 in method 400.

For steps 423 to 450, refer to the method 400, which will not be described in detail here.

Manner 2: Perform step 523 to step 550 in method 500.

For step 523 to step 550, refer to method 500, which will not be described in detail here.

Manner 3: Perform step 623 to step 656 in method 600.

For step 623 to step 656, refer to method 600, which will not be described in detail here.

In the method 700 for network registration provided in the embodiment of the present application, after the network-side PS completes the update according to the acquired target subscription information of the UE, the PS can actively notify the AMF to trigger the update of the UE's identification information, security context, and subscription context. After the AMF receives the trigger message sent by the PS, the AMF can actively trigger the update of the UE's identification information in the temporary private network and the context of the UE in the temporary private network through the NAS message. Compared with the method 400, the method 500, and the method 600, the method provided in the embodiment of the present application avoids the complicated judgment process on the UE side. For example, the UE side does not need to determine whether O-SNPN and T-SNPN are the same network.

Optionally, in some implementation manners, in the method 400, method 500, and method 600 provided in the embodiments of the present application, in the case where the O-SNPN and T-SNPN initially registered by the UE are not in the same network, the O-SNPN contracts After the update is completed, the O-SNPN can notify the (R)AN to trigger the network update or notify the UE to trigger the network update. The update process may be specifically performed after step 430 of the method 400, after step 530 of the method 500, or after step 630 of the method 600. Alternatively, the update process may be specifically performed after step 443 of the method 400, after step 543 of the method 500, or after step 653 of the method 600.

As an implementation manner, in SNPN, O-SNPN notifies (R)AN to trigger network update or notifies UE to trigger network update, including the following two methods:

Method 1: O-SNPN obtains new mobility restrictions (MR) of the UE device, where MR is part of the contract context. After the RAN receives the MR, it can switch the UE to a suitable network. As an implementation manner, in the case that the current network does not meet the MR, one is reselected from the network that meets the MR.

Manner 2: After the O-SNPN obtains the new MR of the UE device, the UE actively switches to a suitable target network after receiving the new MR.

In PNI-NPN, when the UE’s O-PNI-NPN and T-PNI-NPN are not in the same network, after the O-PNI-NPN subscription update is completed, the O-PNI-NPN can notify the (R)AN to trigger the network Update or notify UE to trigger network update. The update process may specifically be performed after step 420 of the method 400, after step 520 of the method 500, or after step 620 of the method 600. Alternatively, the update process may be specifically performed before step 422 of the method 400, before step 522 of the method 500, or before step 622 of the method 600.

As another implementation manner, in PNI-NPN, O-PNI-NPN notifies (R)AN to trigger network update or notifies UE to trigger network update, including the following two methods:

Method 1: The O-PNI-NPN obtains the new MR of the UE device. After the RAN receives the MR, it judges whether the current network is in the CAG List according to the CAG List information. If not, the UE is switched to an available CAG network (including In the CAG List).

Method 2: After the O-PNI-NPN obtains the new MR of the UE device, after the UE receives the new MR, it judges whether the current network is in the CAG List according to the CAG List information. If it is judged that the current network is not in the CAG List, take the initiative Switch to an available CAG network (included in the CAG List).

Above, the network registration method provided by the embodiment of the present application is described in detail with reference to FIG. 3 to FIG. 7. In the following, in conjunction with FIG. 8 to FIG. 12, the apparatus and equipment suitable for network registration in the embodiments of the present application will be introduced.

In this embodiment of the application, the network registration device should include a processing unit. The network registered device may be the AMF mentioned above. The network registered device may also be the AMF chip mentioned above. The device for network registration may also be other network elements mentioned above, for example, UDM.

Optionally, in some implementation manners, the device for network registration may further include a transceiver unit.

In the following, with reference to FIG. 8, the network registration device includes a transceiver unit, a processing unit, and a storage unit as an example for introduction.

FIG. 8 shows a schematic structural diagram of a network registration apparatus 800 provided by an embodiment of the present application.

As shown in FIG. 8, the device 800 includes: a transceiver unit 810 and a processing unit 820.

The processing unit 820 is configured to obtain information about the terminal device in the temporary private network, where the information about the terminal device in the temporary private network includes the context of the terminal device in the temporary private network;

The transceiver unit 810 is configured to receive an online subscription update request sent from the terminal device, where the online subscription update request includes online subscription information of the terminal device on the target private network;

The processing unit 820 is further configured to update the information of the terminal device according to the online subscription information of the target private network.

Optionally, in some embodiments, the processing unit 820 is further configured to update the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, where the terminal device is in the target private network. The information in the private network includes the context of the terminal device in the target private network.

Optionally, in some embodiments, the online subscription update request is carried in a non-access stratum NAS message.

Optionally, in some embodiments, the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.

Optionally, in some embodiments, the online subscription information of the target private network includes identification information of the terminal device in the target private network.

Optionally, in some embodiments, the online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used to indicate the network registration device The information of the terminal device in the temporary private network is updated to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes the context of the terminal device in the target private network.

Optionally, in some embodiments,

The transceiver unit 810 is further configured to receive an online contract notification message sent from a third-party platform, where the online contract notification message includes identification information of the terminal device in the temporary private network;

The processing unit 820 is further configured to send second instruction information to the terminal device according to the online subscription notification message, where the second instruction information is used to trigger an update of the terminal device information.

Optionally, in some embodiments, the second indication information is carried in a NAS message.

Optionally, in some embodiments, the transceiver unit 810 is further configured to:

Send an authentication request message to a unified data management UDM network element, the UDM network element is a network element in the temporary private network, the authentication request message is used to instruct the UDM network element to authenticate the terminal device, and the authentication request message includes Identification information of the terminal device in the target private network;

Receiving an authentication request response message sent by the UDM network element, where the authentication request response message is used to indicate that the authentication is performed successfully;

Sending an acquisition request message to the UDM network element, where the acquisition request message is used to request subscription information of the terminal device in the target private network;

Receiving the subscription information of the terminal device in the target private network sent by the UDM network element;

The processing unit 820 is further configured to update the information of the terminal device according to the contract information of the terminal device in the target private network.

Optionally, in some embodiments, the processing unit 820 is further configured to instruct the UDM network element to delete the information of the terminal device in the temporary private network.

In this embodiment of the application, the network registration device should include a processing unit. The network registration device may be the terminal device mentioned above.

In the following, with reference to FIG. 9, the network registration device includes a transceiver unit, a processing unit, and a storage unit as an example for introduction. FIG. 9 shows a schematic structural diagram of a network registration apparatus 900 provided by an embodiment of the present application.

As shown in FIG. 9, the device 900 includes: a transceiver unit 910 and a processing unit 920.

The processing unit 920 is configured to obtain information about the terminal device in the temporary private network and the online subscription information of the terminal device in the target private network. The information about the terminal device in the temporary private network includes the context of the terminal device in the temporary private network. ；

The transceiver unit 910 is configured to send an online subscription update request by a network device. The online subscription update request includes online subscription information of the terminal device on the target private network, and the online subscription update request is used to trigger an update of the terminal device information.

Optionally, in some implementation manners, the processing unit 920 is further configured to update the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, where the terminal device is in the target private network. The information in the private network includes the context of the terminal device in the target private network.

Optionally, in some implementation manners, the online subscription update request is carried in a non-access stratum NAS message.

Optionally, in some implementation manners, the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.

Optionally, in some implementation manners, the online subscription information of the target private network includes identification information of the terminal device in the target private network.

Optionally, in some implementation manners, the online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used to instruct the network device to The information of the terminal device in the temporary private network is updated to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes the context of the terminal device in the target private network.

Optionally, in some implementation manners, the processing unit 920 is further configured to: the identification information of the terminal device on the temporary private network is the same as the identification information of the terminal device on the target private network;

The transceiver unit 910 is further configured to send the online subscription update request to the network device.

Optionally, in some implementations,

The transceiving unit 910 is further configured to receive second indication information sent by the network device, where the second indication information is used to trigger an update of the terminal device information.

Optionally, in some implementation manners, the second indication information is carried in a NAS message.

Optionally, in some implementation manners, the network device is an AMF.

In this embodiment of the present application, the network registered device should include a processor. The device registered on the network can be the AMF mentioned above. The device registered by the network can also be the AMF chip mentioned above. The network device may also be other network elements mentioned above, for example, UDM.

Optionally, in some implementation manners, the network-registered device may also include a transceiver.

Optionally, in some implementation manners, the network-registered device may further include a memory.

In the following, with reference to FIG. 10, the network registered device including a transceiver, a processor, and a memory is taken as an example for introduction.

FIG. 10 shows a schematic structural diagram of a network registration device 1000 provided by an embodiment of the present application. As shown in FIG. 10, the device 1000 includes: a transceiver 1010, a processor 1020, and a memory 1030. Among them, the transceiver 1010, the processor 1020, and the memory 1030 communicate with each other through internal connection paths to transfer control and/or data signals. The memory 1030 is used to store computer programs, and the processor 1010 is used to call from the memory 1030. And run the computer program to control the transceiver 1020 to send and receive signals.

Specifically, the function of the transceiver 1010 corresponds to the specific function of the transceiver unit 810 shown in FIG. 8, and will not be repeated here.

Specifically, the function of the processor 1020 corresponds to the specific function of the processing unit 820 shown in FIG. 8, and details are not described herein again.

In this embodiment of the present application, the network registered device should include a processor. The device registered on the network may be any one of the terminal devices described above.

In the following, with reference to FIG. 11, the description will be given by taking a network registered device including a transceiver, a processor, and a memory as an example.

FIG. 11 shows a schematic structural diagram of a network registration device 1000 provided by an embodiment of the present application.

As shown in FIG. 11, the device 1100 includes: a transceiver 1110, a processor 1120, and a memory 1130. Among them, the transceiver 1110, the processor 1120, and the memory 1130 communicate with each other through internal connection paths to transfer control and/or data signals. The memory 1130 is used to store computer programs, and the processor 1110 is used to call from the memory 1130. And run the computer program to control the transceiver 1120 to send and receive signals.

Specifically, the function of the transceiver 1110 corresponds to the specific function of the transceiver unit 910 shown in FIG. 9, and will not be repeated here.

Specifically, the function of the processor 1120 corresponds to the specific function of the processing unit 920 shown in FIG. 9, and details are not described herein again.

FIG. 12 shows a schematic structural diagram of a terminal device 20 applicable to an embodiment of the present application. The terminal device 20 can be applied to the system shown in FIG. 1. For ease of description, FIG. 12 only shows the main components of the terminal device. As shown in FIG. 12, the terminal device 20 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is used to control the antenna and the input and output devices to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory to execute the terminal device in the method for mobile registration proposed in this application. Corresponding process and/or operation. I won't repeat them here.

Those skilled in the art can understand that, for ease of description, FIG. 12 only shows a memory and a processor. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiment of the present application.

It should be understood that the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), and application-specific integrated circuits. (application specific integrated circuit, ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (DRAM). Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc), SSD)) etc.

The network-side equipment in the above-mentioned device embodiments corresponds to the terminal equipment and the network-side equipment or terminal equipment in the method embodiments, and the corresponding modules or units execute the corresponding steps, for example, the communication unit (transceiver) performs the receiving in the method embodiments. Or the sending step, other steps except sending and receiving can be executed by the processing unit (processor). For the functions of specific units, refer to the corresponding method embodiments. Among them, there may be one or more processors.

The terms "component", "module", "system", etc. used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, the component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor. Through the illustration, both the application running on the computing device and the computing device can be components. One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed between two or more computers. In addition, these components can be executed from various computer readable media having various data structures stored thereon. The component can be based on, for example, a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

In addition, the term "and/or" in this application is only an association relationship that describes associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean that A alone exists, and both A and B exist. , There are three cases of B alone. In addition, the character "/" in this document generally means that the associated objects before and after are in an "or" relationship; the term "at least one" in this application can mean "one" and "two or more", for example, A At least one of, B and C can mean: A alone exists, B alone exists, C alone exists, A and B exist alone, A and C exist at the same time, C and B exist at the same time, A and B and C exist at the same time, this Seven situations.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for network registration, characterized in that the method includes:

Access and mobility management function AMF network element obtains the information of the terminal equipment in the temporary private network, the AMF network element is the network element in the temporary private network, and the information of the terminal equipment in the temporary private network includes the terminal The context of the device in the temporary private network;

The AMF network element receives an online subscription update request sent from the terminal device, where the online subscription update request includes online subscription information of the terminal device on the target private network;

The AMF network element updates the information of the terminal device according to the online subscription information of the target private network.
The method according to claim 1, wherein the updating the information of the terminal device comprises:

The AMF network element updates the information of the terminal device in the temporary private network to the information of the terminal device in the target private network, wherein the information of the terminal device in the target private network includes the terminal The context of the device in the target private network.
The method according to claim 1 or 2, wherein the online subscription update request is carried in a non-access stratum NAS message.
The method according to any one of claims 1 to 3, wherein the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.
The method according to any one of claims 1-4, characterized in that,

The online subscription information of the target private network includes identification information of the terminal device in the target private network.
The method according to any one of claims 1-5, characterized in that,

The online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used to instruct the AMF network element to place the terminal device on the temporary private network. The information in the temporary private network is updated to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes the context of the terminal device in the target private network.
The method according to any one of claims 1-6, wherein before the AMF network element updates the information of the temporary private network according to the online subscription information of the target private network, the method further include:

The AMF network element receives an online subscription notification message sent from a third-party platform, where the online subscription notification message includes identification information of the terminal device in the temporary private network;

The AMF network element sends second indication information to the terminal device according to the online subscription notification message, where the second indication information is used to trigger an update of the information of the terminal device.
The method according to claim 7, wherein the second indication information is carried by a NAS message.
The method according to any one of claims 1-8, wherein the method further comprises:

The AMF network element sends an authentication request message to a unified data management UDM network element, where the UDM network element is a network element in the temporary private network, and the authentication request message is used to instruct the UDM network element to contact the terminal The device performs authentication, and the authentication request message includes identification information of the terminal device in the target private network;

The AMF network element receives an authentication request response message sent by the UDM network element, where the authentication request response message is used to indicate that the authentication is performed successfully;

Sending, by the AMF network element, an acquisition request message to the UDM network element, where the acquisition request message is used to request subscription information of the terminal device in the target private network;

Receiving, by the AMF network element, the subscription information of the terminal device in the target private network sent by the UDM network element;

The AMF network element updates the information of the terminal device according to the subscription information of the terminal device in the target private network.
The method according to claim 9, wherein the method further comprises:

The AMF network element instructs the UDM network element to delete the information of the terminal device in the temporary private network.
A method for network registration, characterized in that the method includes:

The terminal device obtains the information of the terminal device in the temporary private network and the online contract information of the terminal device in the target private network. The information of the terminal device in the temporary private network includes the information of the terminal device in the temporary private network. Context

The terminal device sends an online subscription update request to the access and mobility management function AMF network element, the online subscription update request includes the online subscription information of the terminal device on the target private network, and the online subscription update request is used To trigger the update of the information of the terminal device.
The method according to claim 11, wherein the updating of the information of the terminal device comprises:

The information of the terminal device in the temporary private network is updated to the information of the terminal device in the target private network, wherein the information of the terminal device in the target private network includes the information of the terminal device in the target private network. The context in the private network.
The method according to claim 11 or 12, wherein the online subscription update request is carried in a non-access stratum NAS message.
The method according to any one of claims 11-13, wherein the context of the terminal device in the temporary private network includes identification information of the terminal device in the temporary private network.
The method according to any one of claims 11-14, characterized in that,

The online subscription information of the target private network includes identification information of the terminal device in the target private network.
The method according to any one of claims 11-15, wherein:

The online subscription update request further includes first indication information and/or identification information of the terminal device in the temporary private network, and the first indication information is used to instruct the AMF network element to place the terminal device on the temporary private network. The information in the temporary private network is updated to the information of the terminal device in the target private network, and the information of the terminal device in the target private network includes the context of the terminal device in the target private network.
The method according to any one of claims 11-16, wherein the terminal device sending an online subscription update request to an access and mobility management function AMF network element comprises:

Determining, by the terminal device, that the identification information of the terminal device on the temporary private network is the same as the identification information of the terminal device on the target private network;

The terminal device sends the online subscription update request to the AMF network element.
The method according to any one of claims 11-17, wherein before the terminal device sends an online subscription update request to an access and mobility management function AMF network element, the method further comprises:

The terminal device receives second indication information sent by the AMF network element, where the second indication information is used to trigger an update of the terminal device information.
The method according to claim 18, wherein the second indication information is carried by a NAS message.
A communication device, characterized in that it comprises at least one processor, the at least one processor is configured to couple with a memory, read and execute instructions in the memory, so as to implement any one of claims 1-10 Methods.
A communication device, characterized in that it comprises at least one processor, the at least one processor is configured to be coupled with a memory, read and execute instructions in the memory, so as to implement any one of claims 11-19 Methods.
A computer-readable storage medium, characterized by comprising instructions, which when run on a computer, causes the computer to execute the method according to any one of claims 1-10 or any one of claims 11-19.
A communication system, characterized in that it comprises:

The communication device according to claim 20 and the communication device according to claim 21.