Network registration method and device

Abstract

The invention provides a network registration method and a network registration device, which are used for solving the problem of communication abnormity when terminal equipment registers in a 3GPP network and non-3GPP access in an INS scene. According to the application, for a scene that the first terminal is registered on the non-3GPP access side after being registered on the 3GPP network, registration of the first terminal on the non-3GPP access side is refused or delayed, so that one AMF is responsible for mobility registration of the first terminal, protocol requirements are met, and user experience is improved. In addition, the problem that two AMFs are responsible for mobility registration of the first terminal due to the fact that 3GPP registration of the first terminal cannot be switched to the AMF selected by non-3GPP registration can be avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a network registration method and device. Background Art

[0002] Wireless access network sharing means that different operators share the wireless access network in the mobile network, so that different operators can jointly bear the construction costs of the wireless access network. At the same time, some operators can use the wireless access network of other operators in areas where they do not have their own wireless access network by sharing the wireless access network, thereby making up for the network coverage of these operators in the area.

[0003] At present, an indirect network sharing mode (INS) is proposed. In this sharing mode, there are two types of operators, namely hosting operators (HOSTING OPERATOR) and participating operators (PARTICAPTING OPERATOR). Among them, the HOSTING OPERATOR is an operator that has an interface with the wireless access network and directly interacts with signaling, that is, an operator that provides the wireless access network. The PARTICAPTING OPERATOR is an operator that uses the wireless access network of the HOSTING OPERATOR but has no interface with the wireless access network. The wireless access network broadcasts its public land mobile network (PLMN) number (that is, the PLMN number of the HOSTING OPERATOR) and the PLMN number of the PATICIPATING OPERATOR over the air interface. The terminal can select the PLMN of the HOSTING OPERATOR or the PLMN of the PARTICIPATING OPERATOR as the PLMN to access. In this scenario, the access and mobility management function (AMF) network element belongs to the HOSTING OPERATOR, but it is also assigned a globally unique AMF identifier (GUAMI) containing the PARTICIPATING OPERATOR PLMN information. When the terminal selects the PARTICIPATING OPERATOR's PLMN and initiates registration, the HOSTING OPERATOR's AMF network element assigns the terminal a globally unique temporary UE identity (GUTI) containing the PARTICIPATING OPERATOR's PLMN information.

[0004] The terminal can register on the 3rd generation partnership project (3GPP) network, that is, register on the air interface, and register on the non-3GPP access side (such as wireless local area network (WIFI)). Since the terminal that has signed a contract with the PATICIPATING OPERATOR selects the non-3GPP access gateway belonging to the PATICIPATING OPERATOR when registering on the non-3GPP access side, and the AMF belonging to the HOSTING OPERATOR is responsible for managing the terminal's mobility registration when the terminal registers on the 3GPP network. However, since there is no interface between the non-3GPP access gateway of the PATICIPATING OPERATOR and the AMF network element of the HOSTING OPERATOR, the terminal will access the same PLMN but select different AMFs, which will cause communication abnormalities. Summary of the invention

[0005] The present application provides a network registration method and apparatus for solving the problem of abnormal communication when a terminal device is registered in a 3GPP network and a non-3GPP access in an INS scenario.

[0006] In a first aspect, a network registration method is provided, the execution subject of the method may be a unified data management network element or a chip, a chip system or a circuit for a unified data management network element, and the method may be implemented by the following steps: receiving a first message, the first message being used to request a first terminal to register to a non-3GPP access side through a first mobility management function network element. When it is determined that the first mobility management function network element and a second mobility management function network element corresponding to the first terminal in a 3GPP network are in the same PLMN, and the non-3GPP access network element and the second mobility management function network element cannot be interconnected, a second message is sent, the second message being used to reject the first terminal from registering to the non-3GPP access side through the first mobility management function network element.

[0007] The present application aims at a scenario in which a first terminal registers on a non-3GPP access side after having registered on a 3GPP network. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, the present application achieves the goal of having one mobility management function network element be responsible for the mobility registration of the first terminal in the same PLMN, which complies with the protocol requirements and can also avoid problems caused by the existence of two mobility management function network elements in the same PLMN being responsible for the mobility registration of the first terminal, such as the first terminal being unable to receive mobile terminated (MT) data packets.

[0008] In a possible design, the first message is a registration request message, and the second message is a registration response message.

[0009] In one possible design, determining that the non-3GPP access network element and the second mobility management function network element cannot be interconnected includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0010] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element. The above design is helpful to avoid the problem caused by the 3GPP registration of the first terminal being unable to switch to the mobility management function network element selected by the non-3GPP registration.

[0011] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element includes: determining that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PARTICIPATING OPERATOR for the non-direct sharing area. The above design can improve the accuracy of the judgment.

[0012] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network. The above design is helpful to avoid the problem caused by the 3GPP registration of the first terminal being unable to switch to the mobility management function network element selected by the non-3GPP registration.

[0013] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network includes: determining that the service network information registered by the first terminal in the 3GPP network is the public land mobile network PLMN information of the first operator, and the first operator is the HOSTING OPERATOR. The above design can improve the accuracy of the judgment.

[0014] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: receiving a third message, the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, the third message carries first information, wherein the first information indicates that the second mobility management function network element belongs to the HOSTING OPERATOR, or the first information indicates that the second mobility management function network element is located in a non-direct network sharing area. The above design can reduce processing overhead by displaying the indication.

[0015] In one possible design, determining that the first mobility management function network element and the second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN includes: if the PLMN information carried by the GUAMI of the second mobility management function network element is the same as the PLMN information carried by the GUAMI of the first mobility management function network element, determining that the first mobility management function network element and the second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0016] In one possible design, before sending the second message, the method further includes: determining that the first mobility management function network element and the second mobility management function network element are from a home PLMN; or determining that the first mobility management function network element and the second mobility management function network element are from an equivalent home PLMN. The above design is conducive to the communication of the terminal in the INS scenario.

[0017] In a possible design, before sending the second message, the method further includes: determining that the home network of the first terminal supports indirect network sharing. The above design is conducive to saving processing overhead of the unified data management network element.

[0018] In a possible design, the second message carries a first cause value, and the first cause value is used to indicate that the first terminal is not allowed to register with the first mobility management function network element and the second mobility management function network element at the same time. The above design is conducive to network management.

[0019] In a second aspect, a network registration method is provided, the execution subject of the method may be a mobility management function network element or a chip, a chip system or a circuit for a mobility management function network element, and the method may be implemented through the following steps: sending a first message, the first message being used to request a first terminal to register with a non-3GPP access side through a first mobility management function network element; receiving a second message, the second message being used to reject the first terminal from registering with a non-3GPP access side through a first mobility management function network element, the second message carrying a first reason value, the first reason value being used to indicate that the first terminal is not allowed to register with both the first mobility management function network element and the second mobility management function network element at the same time; sending a fourth message, the fourth message being used to indicate that the first terminal cannot register with a non-3GPP in a current area, or the fourth message instructs the first terminal to postpone registration with a non-3GPP.

[0020] The present application aims at a scenario in which a first terminal registers on a non-3GPP access side after having registered on a 3GPP network. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, the present application achieves the goal of having one mobility management function network element be responsible for the mobility registration of the first terminal in the same PLMN, which complies with the protocol requirements and can also avoid the problems caused by the existence of two mobility management function network elements in the same PLMN being responsible for the mobility registration of the first terminal, for example, the first terminal cannot receive mobile terminated (MT) data packets.

[0021] Furthermore, by sending a cause value to the mobility management function network element selected by the non-3GPP registration to indicate the cause of rejection, network management is facilitated.

[0022] In a possible design, the fourth message indicates that the first terminal postpones the registration time in the non-3GPP. The above design is conducive to the communication of the first terminal in the non-3GPP access side.

[0023] According to a third aspect, a network registration method is provided, wherein the executing subject of the method may be a unified data management network element or a chip, a chip system or a circuit for a unified data management network element, and the method may be implemented through the following steps: receiving a first message, wherein the first message is used to request that a first mobility management function network element registered by a first terminal in a non-3GPP access side be updated to a second mobility management function network element; and when it is determined that the non-3GPP access network element and the second mobility management function network element cannot be interconnected, sending a first message, wherein the first message is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0024] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The unified data management network element can timely release the context information of the first terminal in the non-3GPP interworking function network element by instructing the non-3GPPP access side to delete the context information of the first terminal, thereby saving the resources of the non-3GPP interworking function network element. In addition, by timely releasing the context information of the first terminal in the non-3GPP interworking function network element, the first terminal can be released to an idle state on the non-3GPP access side in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0025] In one possible design, determining that the non-3GPP access network element and the second mobility management function network element cannot be interconnected includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0026] In one possible design, the first mobility management function network element and the second mobility management function network element are located in the same PLMN.

[0027] In a possible design, sending the first information includes: sending a second message, the second message instructing the first mobility management function network element to deregister, and the second message carries the first information. The above design can release the context information of the first terminal on the non-3GPP access side in a timely manner.

[0028] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element. The above design is helpful to avoid the problem caused by the 3GPP registration of the first terminal being unable to switch to the mobility management function network element selected by the non-3GPP registration.

[0029] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element includes: determining that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PARTICIPATING OPERATOR for the non-direct sharing area. The above design can improve the accuracy of the judgment.

[0030] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network. The above design is helpful to avoid the problem caused by the 3GPP registration of the first terminal being unable to switch to the mobility management function network element selected by the non-3GPP registration.

[0031] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network includes: determining that the service network information registered by the first terminal in the 3GPP network is the public land mobile network PLMN information of the first operator, and the first operator is the HOSTING OPERATOR. The above design can improve the accuracy of the judgment.

[0032] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: receiving a third message, the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, the third message carries second information, wherein the second information indicates that the second mobility management function network element belongs to the HOSTING OPERATOR, or the second information indicates that the second mobility management function network element is located in a non-direct network sharing area. The above design can reduce processing overhead by displaying the indication.

[0033] In a fourth aspect, a network registration method is provided. The executor of the method may be a mobility management function network element or a chip, a chip system or a circuit used for a mobility management function network element. The method may be implemented through the following steps: receiving first information, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal; and sending third information, the third information being used to instruct the non-3GPP intercommunication function network element to delete the context information of the first terminal.

[0034] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The unified data management network element instructs the non-3GPPP access side to delete the context information of the first terminal, so that the context information of the first terminal in the non-3GPP interworking function network element can be released in time, thereby saving the resources of the non-3GPP interworking function network element. In addition, by releasing the context information of the first terminal in the non-3GPP interworking function network element in time, the first terminal can be released to an idle state on the non-3GPP access side in time, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0035] In a possible design, before sending the third information, the method further includes: determining whether context information of the first terminal exists on the non-3GPP interworking function network element. The above design can save signaling overhead.

[0036] In one possible design, receiving the first information includes: receiving a second message, the second message instructing the first mobility management function network element to deregister, and the second message carrying the first information. The above design can release the context information of the first terminal on the non-3GPP access side in a timely manner.

[0037] In a fifth aspect, a network registration method is provided, wherein the execution subject of the method may be a mobility management function network element or a chip, a chip system or a circuit for a mobility management function network element, and the method may be implemented through the following steps: receiving a first message, wherein the first message is used to request the first terminal to register with the non-3GPP access side of the first PLMN through the first mobility management function network element; determining that the first terminal has registered with the 3GPP network of the first PLMN through the second mobility management function network element; determining that the non-3GPP access network element and the second mobility management function network element cannot be interconnected; and sending a second message, wherein the second message is used to indicate that the first terminal cannot register with the non-3GPP in the current area, or the second message indicates that the first terminal postpones registration with the non-3GPP.

[0038] The present application aims at a scenario in which a first terminal registers on a non-3GPP access side after having registered on a 3GPP network. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, one mobility management function network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements and can also avoid problems caused by the existence of two mobility management function network elements responsible for the mobility registration of the first terminal in the same PLMN, for example, the first terminal cannot receive MT data packets, etc.

[0039] In one possible design, determining that the non-3GPP access network element and the second mobility management function network element cannot be interconnected includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0040] In one possible design, the first message carries the GUTI allocated by the second mobility management function network element to the first terminal when the first terminal accesses the 3GPP network; determining that the first terminal has registered with the 3GPP network of the first PLMN through the second mobility management function network element includes: determining, based on the GUTI, that the first terminal has registered with the 3GPP network of the first PLMN through the second mobility management function network element.

[0041] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element. The above design is helpful to avoid the problem caused by the 3GPP registration of the first terminal being unable to switch to the mobility management function network element selected by the non-3GPP registration.

[0042] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element includes: determining that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PARTICIPATING OPERATOR for the non-direct sharing area. The above design can improve the accuracy of the judgment.

[0043] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: receiving first information, where the first information indicates that the second mobility management function network element belongs to the HOSTING OPERATOR. The above design can reduce processing complexity.

[0044] In one possible design, receiving the first information includes: sending a third message, the third message is used to request the context information of the first terminal from the second mobility management function network element; receiving a fourth message, the fourth message carries the context information of the first terminal and the first information.

[0045] In a possible design, before sending the second message, the method further includes: determining that the home network of the first terminal supports indirect network sharing. The above design is conducive to saving processing overhead.

[0046] In a possible design, the second message indicates that the first terminal postpones the registration time in the non-3GPP. The above design is conducive to the communication of the first terminal in the non-3GPP access side.

[0047] In a sixth aspect, a network registration method is provided, wherein the executing subject of the method may be a mobility management function network element or a chip, a chip system or a circuit for a mobility management function network element, and the method may be implemented through the following steps: receiving a third message, wherein the third message is used to request that the context information of the first terminal be migrated to the first mobility management function network element; and sending a fourth message, wherein the fourth message carries the context information of the first terminal and the first information, wherein the first information is used to indicate that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0048] The present application aims at the scenario in which the first terminal registers on the non-3GPP access side after having registered on the 3GPP network. The second mobility management function network element indicates to the first mobility management function network element that the second mobility management function network element belongs to the HOSTING OPERATOR, which is conducive to rejecting or postponing the registration of the first terminal on the non-3GPP access side, thereby realizing that one mobility management function network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements and can also avoid the problems caused by the existence of two mobility management function network elements responsible for the mobility registration of the first terminal in the same PLMN, for example, the first terminal cannot receive MT data packets, etc.

[0049] In the seventh aspect, a network registration method is provided, the execution subject of the method can be a mobility management function network element or a chip, a chip system or a circuit used for a mobility management function network element, and the method can be implemented through the following steps: receiving a first message, the first message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, the first message carries the GUTI allocated by the first mobility management function network element to the first terminal when the first terminal registers to the non-3GPP access side; determining the first mobility management function network element according to the GUTI; if the non-3GPP access network element and the second mobility management function network element cannot be interconnected, sending a first message to the first mobility management function network element, the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0050] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The mobility management function network element on the non-3GPP access side can timely release the context information of the first terminal in the non-3GPP interworking function network element by receiving an instruction to delete the context information of the first terminal on the non-3GPP access side, thereby saving the resources of the non-3GPP interworking function network element. In addition, by timely releasing the context information of the first terminal in the non-3GPP interworking function network element, the first terminal can be released to an idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0051] In one possible design, the non-3GPP access network element and the second mobility management function network element cannot be interconnected, including: the second mobility management function network element belongs to the HOSTING OPERATOR.

[0052] In one possible design, sending first information to a first mobility management function network element includes: sending a second message to the first mobility management function network element, the second message being used to request context information of the first terminal from the first mobility management function network element, and the second message carrying the first information.

[0053] In one possible design, sending first information to a first mobility management function network element includes: sending a second message, the second message is used to request context information of the first terminal from the first mobility management function network element; receiving a third message, the third message carries the context information of the first terminal; determining, based on the context information of the first terminal, that the first terminal has been registered on the non-3GPP access side and that the first terminal is in a connected state on the non-3GPP access side; sending a fourth message, the fourth message is used to confirm that the context information of the first terminal in the first mobility management function network element has been received / updated, and the fourth message carries the first information.

[0054] In one possible design, the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal, including: the first information indicates that the first terminal is registered in the 3GPP network, or the first information indicates deletion of the context information of the first terminal on the non-3GPP access side.

[0055] In one possible design, before sending the first information to the first mobility management function network element, the method further includes: determining that the home network of the first terminal supports indirect network sharing. The above design is conducive to reducing processing overhead.

[0056] In one possible design, before sending the first information to the first mobility management function network element, the method also includes: determining that the first mobility management function network element belongs to a PARTICAPTING OPERATOR.

[0057] In an eighth aspect, a network registration method is provided, wherein the executing subject of the method may be a mobility management function network element or a chip, a chip system or a circuit for a mobility management function network element, and the method may be implemented through the following steps: receiving a second message, the second message being used to request that the context of the first terminal be migrated to a second mobility management function network element; determining to delete the context information of the first terminal in the non-3GPP interoperability function network element; and sending a second message to the non-3GPP interoperability function network element, the second information being used to instruct the non-3GPP interoperability function network element to delete the context information of the first terminal.

[0058] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The mobility management function network element on the non-3GPP access side can timely release the context information of the first terminal in the non-3GPP interworking function network element by instructing the non-3GPP access side to delete the context information of the first terminal, thereby saving the resources of the non-3GPP interworking function network element. In addition, by timely releasing the context information of the first terminal in the non-3GPP interworking function network element, the first terminal can be released to an idle state on the non-3GPP access side in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0059] In one possible design, determining to delete context information of a first terminal in a non-3rd Generation Partnership Project 3GPP interworking function network element includes: receiving first information, wherein the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0060] In one possible design, receiving the first information includes: the second message carries the first information, and the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0061] In one possible design, receiving the first information includes: sending a third message, the third message carrying context information of the first terminal; receiving a fourth message, the fourth message being used to confirm that the context information of the first terminal in the first mobility management function network element has been received / updated, the fourth message carrying the first information, and the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0062] In one possible design, the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal, including: the first information indicates that the first terminal is registered in the 3GPP network, or the first information indicates deletion of the context information of the first terminal on the non-3GPP access side.

[0063] In one possible design, determining to delete context information of a first terminal in a non-3GPP interworking function network element includes: determining that the non-3GPP access network element cannot be interconnected with a second mobility management function network element.

[0064] In one possible design, determining that the non-3GPP access network element and the second mobility management function network element cannot be interconnected includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0065] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: determining that the second mobility management function network element belongs to the HOSTING OPERATOR according to the GUAMI of the second mobility management function network element.

[0066] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the GUAMI of the second mobility management function network element includes: determining that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PARTICIPATING OPERATOR for the non-directly shared area.

[0067] In a ninth aspect, the present application further provides a communication device, wherein the device is a unified data management network element or a chip in a unified data management network element. The communication device has the function of implementing any of the methods provided in the first aspect or the third aspect above. The communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0068] In one possible design, the communication device includes: a processor, which is configured to support the communication device to perform the corresponding functions of the terminal device in the method shown above. The communication device may also include a memory, which can be coupled to the processor and stores the necessary program instructions and data of the communication device. Optionally, the communication device also includes an interface circuit, which is used to support communication between the communication device and a device such as a mobility management function network element, such as the transmission and reception of data or signals. Exemplarily, the communication interface can be a transceiver, circuit, bus, module or other type of communication interface.

[0069] In one possible design, the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0070] In one possible design, the structure of the communication device includes a processing unit (or processing module) and a communication unit (or communication module), which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in the first aspect or the third aspect, which will not be repeated here.

[0071] In a tenth aspect, the present application further provides a communication device, wherein the device is a mobility management function network element or a chip in a mobility management function network element. The communication device has the function of implementing any method provided in any of the second aspect, the fourth aspect to the eighth aspect. The communication device can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0072] In one possible design, the communication device includes: a processor, which is configured to support the communication device to perform the corresponding functions of the network device in the method shown above. The communication device may also include a memory, which can be coupled to the processor and stores the necessary program instructions and data for the communication device. Optionally, the communication device also includes an interface circuit, which is used to support communication between the communication device and a unified data management network element, an access network device, and other devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface can be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.

[0073] In one possible design, the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0074] In one possible design, the structure of the communication device includes a processing unit (or processing module) and a communication unit (or communication module), which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in any one of the second aspect and the fourth aspect to the eighth aspect, which will not be repeated here.

[0075] In the eleventh aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being used to implement the methods in the aforementioned first aspect or third aspect and any possible design through logic circuits or execution code instructions.

[0076] In the twelfth aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being used to implement the method in any one of the second aspect, fourth aspect to eighth aspect and any possible design through logic circuits or execution code instructions.

[0077] In the thirteenth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the method in any one of the first to eighth aspects and any possible design is implemented.

[0078] In a fourteenth aspect, a computer program product storing instructions is provided, which, when executed by a processor, implements the method in any one of the first to eighth aspects and any possible design.

[0079] In a fifteenth aspect, a chip system is provided, the chip system includes a processor and may also include a memory, for implementing the method in any aspect of the first to eighth aspects and any possible design. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0080] In the sixteenth aspect, a communication system is provided, the system comprising the device described in the first aspect (such as a unified data management network element) and the device described in the second aspect (such as a mobility management function network element).

[0081] In the seventeenth aspect, a communication system is provided, the system comprising the device described in the third aspect (such as a unified data management network element) and the device described in the fourth aspect (such as a mobility management function network element).

[0082] In the eighteenth aspect, a communication system is provided, the system comprising the device described in the fifth aspect (such as the first mobility management function network element) and the device described in the sixth aspect (such as the second mobility management function network element).

[0083] In the nineteenth aspect, a communication system is provided, the system comprising the device described in the fifth aspect (such as the second mobility management function network element) and the device described in the sixth aspect (such as the first mobility management function network element).

[0084] The technical effects that can be achieved by the technical solutions of any of the ninth to nineteenth aspects mentioned above can be described with reference to the technical effects that can be achieved by the technical solutions of the first aspect mentioned above, and the repeated parts will not be repeated. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 A schematic diagram of a GUTI provided in an embodiment of the present application;

[0086] Figure 2 A schematic diagram of a network architecture provided for an embodiment of the present application;

[0087] Figure 3 A schematic diagram of a network architecture provided for an embodiment of the present application;

[0088] Figure 4 A schematic diagram of indirect network sharing provided in an embodiment of the present application;

[0089] Figure 5 A flowchart of a network registration method provided in an embodiment of the present application;

[0090] Figure 6 A schematic diagram of a network registration process provided in an embodiment of the present application;

[0091] Figure 7 A flowchart of a network registration method provided in an embodiment of the present application;

[0092] Figure 8 A schematic diagram of a network registration process provided in an embodiment of the present application;

[0093] Fig. 9A flowchart of a network registration method provided in an embodiment of the present application;

[0094] Fig.10 A schematic diagram of a network registration process provided in an embodiment of the present application;

[0095] Fig.11 A flowchart of a network registration method provided in an embodiment of the present application;

[0096] Fig.12 A schematic diagram of a network registration process provided in an embodiment of the present application;

[0097] Fig.13 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0098] Fig.14 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0099] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0100] Below, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0101] 1. 5G globally unique temporary UE identity (5G-GUTI)

[0102] 5G-GUTI is a temporary identifier of the terminal in 5G, which is uniquely assigned by AMF. Like other temporary IDs, it has a validity period and a related registration validity area. When the validity period expires, the terminal needs to initiate a network update, that is, request the network to reallocate 5G-GUTI, or when the terminal moves to a different registration area, that is, moves out of the current valid registration area, such as moving between different AMFs, a new temporary identifier will be assigned. Figure 1 As shown, its structure is as follows:

[0103] <5G-GUTI>= <guami><5G-TMSI>, where <guami> ＝ <mcc> <mnc><AMF Identifier>,<AMF Identifier> =<AMF Region ID><AMF Set ID><AMF Pointer> .

[0104] The entire 5G-GUTI is divided into two parts: the globally unique AMF identifier (GUAMI) and the 5G-TMSI. GUAMI is used to uniquely identify the AMF, so that the AMF can determine the AMF used by the terminal before based on the GUAMI: whether it is itself or someone else.

[0105] GUAMI also consists of two parts: public land mobile network (PLMN) and AMF identifier (AMF Identifier). Among them, PLMN is composed of mobile country code (MCC) and mobile network code (MNC). AMF Identifier is composed of three parts, namely AMF region ID (ARI), AMF set ID (ASI) and AMF network element identifier (AMFpointer, AP).

[0106] 2. PLMN

[0107] In daily life, mobile operators that provide network services to terminals are generally identified by PLMN. PLMN is a network established and operated by the government or its approved operators for the purpose of providing land mobile communication services to the public. Different PLMN networks can be distinguished by different PLMN identifications (IDs). The PLMN identification consists of a mobile country code (MCC) and a mobile network code (MNC). Among them, MCC uniquely indicates the country to which the mobile user belongs, for example, China's MCC is 460. MNC uniquely indicates the network in the country, for example, China Mobile's MNC is 00, and China Unicom's MNC is 01.

[0108] When a terminal accesses an access network device, it needs to select a network. The process of selecting a network is called PLMN selection. PLMN selection can be as follows:

[0109] A1, the access stratum (AS) of the terminal scans all radio frequency (RF) channels of the new radio (NR) band according to its own capabilities to find available PLMNs. The terminal will find the cell with the best reference signal received power (RSRP) in each frequency point and then read the system information block 1 (SIB1) of the cell to obtain the PLMN ID.

[0110] A2: The AS of the terminal reports a PLMN list to the non-access stratum (NAS) of the terminal. The PLMN list includes the PLMN ID obtained by the AS of the terminal.

[0111] A3: After receiving the PLMN list reported by the AS of the terminal, the NAS of the terminal will select one of the PLMN IDs as the PLMN used by the terminal.

[0112] When the terminal selects a PLMN, the searched PLMN can be: a registered PLMN (RPLMN), where RPLMN is the PLMN registered by the terminal before it was previously shut down or disconnected from the network; an equivalent PLMN (EPLMN), where EPLMN is a PLMN with the same priority as the PLMN currently selected by the terminal; a home PLMN (HPLMN), where the identifier of the HPLMN is stored in the subscriber identity module (SIM) card, and each SIM card has only one HPLMN; an equivalent HPLMN (EHPLMN), which is a PLMN with the same priority as the HPLMN.

[0113] A4, after selecting the PLMN ID, the NAS of the terminal can provide the AS of the terminal with the EPLMN list and the forbidden tracking area (forbidden TA) according to the selected PLMN ID. The AS of the terminal can perform cell selection and reselection according to the EPLMN list and the forbidden TA.

[0114] For a terminal, it is usually necessary to maintain several different types of PLMN lists, and each list may contain multiple PLMNs.

[0115] (1)RPLMN (Registered PLMN): Registered PLMN. It is the PLMN that the terminal registered before it was last turned off or disconnected from the network. This parameter is stored in the terminal's memory.

[0116] (2) EPLMN (Equivalent PLMN): a PLMN that is equal to the PLMN currently selected by the terminal and has the same priority.

[0117] (3) EHPLMN (Equivalent Home PLMN): a PLMN that is on an equal footing with the terminal HPLMN.

[0118] (4) HPLMN (Home PLMN): The PLMN to which the terminal user belongs. That is, the MCC and MNC contained in the IMSI number on the terminal USIM card are consistent with the MCC and MNC on the HPLMN. For any user, there is only one PLMN to which he belongs.

[0119] (5) VPLMN (Visited PLMN): The PLMN visited by the terminal user when roaming. Its PLMN is not exactly the same as the MCC and MNC of the IMSI stored in the SIM card, which means that the user is roaming.

[0120] 3. Hosting Operator

[0121] A HOSTING OPERATOR is an operator that has an interface with the wireless access network and directly interacts with the network through signaling, that is, an operator that provides the wireless access network.

[0122] 4. Participating Operator

[0123] A PARTICAPTING OPERATOR is an operator that uses the HOSTING OPERATOR's radio access network but has no interface with the radio access network.

[0124] In the embodiments of the present application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B may be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c may represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c may be single or plural.

[0125] Also, unless otherwise specified, ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority or importance of multiple objects.

[0126] It should be noted that in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0127] The terms "including" and "having" and any variations thereof mentioned in the following description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0128] The foregoing text introduces some of the terms involved in the embodiments of the present application. The following text introduces the architecture of the network system to which the method provided by the present application is applied.

[0129] The network registration method provided in this application can be applied to various communication systems, for example, the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), long term evolution (LTE), fifth generation (5G) communication system, LTE and 5G hybrid architecture, 5G new radio (NR) system and future communication network, etc. The communication system described in this application can also be a machine to machine (M2M) network, a non-terrestrial network (NTN) network or other network.

[0130] like Figure 2 , which is a schematic diagram of the fifth generation (5G) network architecture based on a service-oriented architecture. Figure 2 The 5G network architecture shown may include three parts, namely, the UE part, the data network (DN) and the operator network part. The functions of some network elements are briefly introduced below.

[0131] Among them, the operator network may include but is not limited to one or more of the following network elements: network slice selection function (NSSF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, network storage function (NRF) network element, access and mobility management function (AMF) network element, policy control function (PCF) network element, unified data management (UDM) network element, session management function (SMF) network element, access network (AN) or radio access network (RAN), and user plane function (UPF) network element. In the above-mentioned operator network, the part other than the radio access network part can be called the core network part. In a possible implementation method, the operator network also includes an application function (AF) network element.

[0132] A terminal is a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal can be a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a user equipment (UE), a terminal adapted to the Internet of Things (IoT) (such as a terminal in a smart factory, a terminal in the smart manufacturing industry, etc.), a terminal supporting sparklink short-range communication technology, etc.

[0133] The above-mentioned terminal can establish a connection with the operator network through the interface provided by the operator network (such as N1, etc.), and use the data and / or voice services provided by the operator network. The terminal can also access the DN through the operator network, use the operator services deployed on the DN, and / or services provided by a third party. Among them, the above-mentioned third party may be a service provider other than the operator network and the terminal, and can provide other data and / or voice services to the terminal. Among them, the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.

[0134] RAN is the wireless access network of the operator network and the bridge system between the service node and the terminal in the operator network. To access the operator network, the terminal must first pass through RAN and then connect to the service node of the operator network through RAN. RAN equipment is a device that provides wireless communication functions for the terminal. RAN equipment is also called access network equipment. RAN equipment includes but is not limited to: next-generation base stations (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node ​​B, NB), base station controller (basestation controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.

[0135] The AMF network element mainly performs functions such as mobility management and access authentication / authorization. In addition, it is also responsible for transmitting user policies between UE and PCF. In future communications, the access and mobility management function network element can still be the AMF network element, or have other names, which is not limited in this application.

[0136] The SMF network element mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and allocation of UE Internet Protocol (IP) addresses. In future communications, the session management function network element may still be an SMF network element or have other names, which are not limited in this application.

[0137] The UPF network element, as an interface with the data network, completes functions such as user plane data forwarding, session / flow-level billing statistics, bandwidth limitation, etc. In future communications, the user plane function network element may still be a UPF network element, or have other names, which are not limited in this application.

[0138] The UDM network element is mainly responsible for managing subscription data, user access authorization, etc. In future communications, the user plane function network element may still be a UDM network element, or have other names, which are not limited in this application.

[0139] NSSF network element is mainly responsible for managing information related to network slicing.

[0140] NEF network element is mainly used to support the opening of capabilities and events.

[0141] The AF network element mainly transmits the requirements of the application side to the network side, such as Quality of Service (QoS) requirements or user status event subscriptions. The AF can be a third-party functional entity or an application service deployed by an operator, such as the IP Multimedia Subsystem (IMS) voice call service.

[0142] The PCF network element is mainly responsible for policy control functions such as billing for sessions and service data flow levels, QoS bandwidth guarantee and mobility management, and UE policy decision-making. In this architecture, the PCFs connected to the AMF network element and the SMF network element correspond to AMPCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively, and may not be the same PCF entity in actual deployment scenarios.

[0143] NRF network elements can be used to provide network element discovery functions and provide network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push.

[0144] AUSF network element: Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.

[0145] DN is a network outside the operator network. The operator network can access multiple DNs. Multiple services can be deployed on DN, which can provide data and / or voice services to terminals. For example, DN is the private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminals. The control server of the sensors is deployed in DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminals. The employees' mobile phones or computers can access information, data resources, etc. on the company's internal office network.

[0146] Figure 2 Among them, Nnssf, Nausf, Nnef, Nnrf, NAMF network element, Npcf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3GPP standard protocol and are not limited here.

[0147] 5GC supports access to non-3GPP networks. Terminals can access 5GC through non-3GPP access gateways such as non-3GPP interworking function (N3IWF) and next generation packet data gateway (ngPDG). Taking N3IWF as an example, the 5G network architecture is as follows: Figure 3 shown. Figure 3 In the present invention, the access network includes a 3GPP access network and a non-3GPP access network. The access equipment in the 3GPP access network can be called a radio access network (RAN) equipment. N3IWF is a non-3GPP access gateway. The non-3GPP access network can include, for example, a wireless local area network (WLAN) access network, and the N3IWF equipment can include, for example, a router, etc.

[0148] like Figure 3 For an introduction to the functions of the network elements shown, please refer to Figure 2 The introduction of the functions of the corresponding network elements will not be repeated here. Figure 3 and Figure 2 The main differences are: Figure 3 The interfaces between the network elements in a network are point-to-point interfaces. Figure 2 The interfaces between the various network elements in the network are service-oriented interfaces.

[0149] Figure 3 Among them, N1, N2, N3, N4, N6, N11, NWu, Y1, and Y2 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3GPP standard protocol and are not limited here.

[0150] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0151] The following introduces the technical background involved in the embodiments of the present application.

[0152] Wireless access network sharing means that different operators share the wireless access network in the mobile network, so that different operators can jointly bear the construction costs of the wireless access network. At the same time, some operators can use the wireless access network of other operators in areas where they do not have their own wireless access network by sharing the wireless access network, thereby making up for the network coverage of these operators in the area.

[0153] At present, an indirect network sharing model (INS) is proposed. In this sharing model, there are two types of operators, namely hosting operators and participating operators. Figure 4 As shown, the wireless access network broadcasts its own public land mobile network (PLMN) number (i.e., the PLMN number of the HOSTING OPERATOR) and the PLMN number of the PATICIPATING OPERATOR in the air interface. The terminal can select the PLMN of the HOSTING OPERATOR or the PLMN of the PARTICIPATING OPERATOR as the PLMN to access.

[0154] In this scenario, the AMF network element belongs to the HOSTING OPERATOR, but it is also assigned a GUAMI containing the PARTICIPATING OPERATOR PLMN information. When the terminal selects the PARTICIPATING OPERATOR's PLMN and initiates registration, the HOSTING OPERATOR's AMF network element assigns a GUTI containing the PARTICIPATING OPERATOR's PLMN information to the terminal based on the PARTICIPATING OPERATOR's PLMN selected by the user.

[0155] In the INS scenario, the shared RAN can broadcast the HPLMN ID or EHPLMN ID or other PLMN ID according to the agreement between operators. When the broadcast PLMN ID is HPLMN or EHPLMN, the terminal can register on the 3GPP network, that is, register on the NR air interface, and register on the non-3GPP access side (such as mobile hotspot (WIFI)). If the terminal is a subscriber of the PARTICIPATING OPERATOR, the following two scenarios will appear: Scenario A and Scenario B:

[0156] Scenario A, 3GPP registration first: When the terminal device accesses the 3GPP network, it selects the HPLMN or EHPLMN ID according to the PLMN ID number broadcast by the air interface, and initiates registration with the HPLMN / EHPLMN network. At this time, the NG-RAN in the shared area selects the AMF (assuming it is AMF1) in the HOSTING OPERATOR PLMN. After successful registration, AMF1 assigns a GUTI to the terminal, and the GUTI will contain the selected PLMN information, that is, the HPLMN or EHPLMN information. When this terminal chooses to subsequently register on the non-3GPP access side, on the non-3GPP access side, the terminal selects the N3IWEF of the HPLMN / EHPLMN and initiates user registration on the non-3GPP access side. At this time, two scenarios, A-1 and A-2, may occur:

[0157] A-1, N3IWF is in the HOSTING OPERATOR PLMN area, but N3IWF belongs to the HPLMN / EHPLMN operator, that is, the PARTICAPTING OPERATOR. Normally, there is no interface between the N3IWF of the PARTICIPATING OPERATOR and the AMF of the HOSTING OPERATOR. Therefore, when the terminal registers on the non-3GPP access side, the N3IWF will re-select an AMF of the PARTICIPATING OPERATOR for the terminal (assuming it is AMF2). The registration message will then be processed by AMF2.

[0158] A-2, N3IWF is in the PARTICIPATIONG PLMN area. N3IWF belongs to the HPLMN / EHPLMN operator, also known as the PARTICAPTING OPERATOR. At this time, there is an interface between N3IWF and the AMF of the home network (also known as the PARTICAPTING OPERATOR), but there is no interface between N3IWF and the AMF of the HOSTING OPERATOR. As a result, the terminal will not be able to find the same AMF on the non-3GPP access side using the GUTI previously allocated after a successful registration in the 3GPP network (because the GUTI belongs to the AMF in the HOSTINGOPERATOR area). Therefore, N3IWF will reselect an AMF (assumed to be AMF2). The registration message will then be processed by AMF2.

[0159] After processing in the above manner, there will be two registered AMF network elements in the same PLMN, namely the HPLMN / EHPLMN scenario, namely AMF1 / AMF2 is responsible for managing the mobility registration of the terminal. However, the protocol currently stipulates that in the same PLMN, after the terminal registers in the 3GPP network or non-3GPP network, except for very few special scenarios (such as the short period of time after the user moves from the evolved packet system (EPS) network to the 5G system (5G system, 5GS) network across radio access technology (radio access technology, RAT) registration), it can only use the same AMF. Therefore, the above-mentioned behavior of the terminal device registering in the 3GPP network and the non-3GPP access side in the INS scenario does not comply with the protocol regulations. This will also lead to some other problems. For example, when the terminal is in a non-3GPP idle state, the terminal's mobile terminated (MT) data will not be forwarded.

[0160] Scenario B, non-3GPP registration first: Assuming that the terminal has registered on the non-3GPP access side, the N3IWF of the HPLMN / EHPLMN operator will select the AMF of the PARTICAPTING OPERATOR (assuming AMF2). Then register in the 3GPP network. Since the 3GPP network uses a shared RAN, the NG-RAN in the shared area selects the AMF in the HOSTINGOPERATOR PLMN (assuming AMF1) when the terminal registers in the 3GPP network. At this time, the AMF1 selected by the 3GPP network needs to notify the N3IWF to switch the connection from AMF2 to AMF1. However, since the AMF1 of the 3GPP network is in the HOSTING OPERATOR, there is a possibility that there is no interface between it and the N3IWF in the PARTICAPTING OPERATOR. Therefore, it is impossible to notify the N3IWF to switch the connection. Therefore, if the terminal is in a connected state in the non-3GPP at this time and there is a context, the context of the terminal will be suspended on the N3IWF and cannot be released.

[0161] Based on this, the embodiment of the present application provides a network registration method and device for solving the problem of abnormal communication when a terminal device is registered in a 3GPP network and a non-3GPP access in an INS scenario. The method and the device are based on the same concept. Since the principles of solving the problem by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0162] It should be noted that the naming of each message / information in this application is only for illustration and limits the name of each message / information.

[0163] In this application, "registering on the 3GPP network" can also be described as "registering on the network through 3GPP access technology". Similarly, "registering on the non-3GPP access side" can also be described as "registering on the network through non-3GPP access technology".

[0164] In addition, in the embodiment of the present application, the access network element on the non-3GPP access side is taken as N3IWF as an example. In a specific implementation, N3IWF can also be replaced by other non-3GPP access network elements, such as TNGF or W-AGF.

[0165] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0166] Embodiment 1:

[0167] like Figure 5 The figure is a flow chart of a network registration method provided in an embodiment of the present application.

[0168] S501, a first AMF network element sends a first message. Correspondingly, a UDM network element receives the first message.

[0169] Among them, the first message is used to request the first terminal to register to the non-3GPP access side through the first AMF network element.

[0170] Optionally, before S501, the first terminal may register with the 3GPP network through the second AMF network element.

[0171] S502, the UDM network element determines that the first AMF network element and the second AMF network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0172] Among them, the first AMF network element and the second AMF network element are not the same AMF network element.

[0173] Optionally, the first AMF network element and the second AMF network element come from the home PLMN, or the first AMF network element and the second AMF network element come from an equivalent home PLMN.

[0174] In one possible implementation, if the PLMN information carried by the GUAMI of the second AMF network element is the same as the PLMN information carried by the GUAMI of the first AMF network element, the UDM network element can determine that the first AMF network element and the second AMF network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0175] Exemplarily, the UDM network element can obtain the GUAMI of the first AMF network element through the registration request of the first AMF network element (ie, the first message mentioned above). For example, the first message carries the GUAMI of the first AMF network element.

[0176] The UDM network element can obtain the GUAMI of the first AMF network element through the registration request of the second AMF network element (i.e., the third message for requesting the first terminal to register with the 3GPP network through the second AMF network element). For example, the third message carries the GUAMI of the second AMF network element.

[0177] S503, the UDM network element determines that the second AMF network element belongs to the HOSTING OPERATOR.

[0178] In one possible implementation, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the GUAMI of the second AMF network element. For example, if the GUAMI of the second AMF network element belongs to a specific value range, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR, where the specific value range is allocated by the PATRICIPATING OPERATOR for the non-direct shared area. For example, the AMF Identifier carried by the GUAMI of the second AMF network element can be allocated by the second operator for the non-direct network shared area.

[0179] Exemplarily, the way in which the UDM network element obtains the GUAMI of the second AMF network element can refer to the relevant description of S502 above, which will not be repeated here.

[0180] In another possible implementation, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network. For example, if the service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR, and the first operator is the HOSTING OPERATOR.

[0181] Exemplarily, the UDM network element can obtain the service network information registered by the first terminal in the 3GPP network through the registration request (i.e., the third message above) of the second AMF network element. For example, the third message carries the service network information registered by the first terminal in the 3GPP network.

[0182] In another possible implementation, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR based on the indication information carried by the registration request of the second AMF network element (i.e., the third message in the previous text). For example, the third message carries the first information, wherein the first information indicates that the second AMF network element belongs to the HOSTING OPERATOR, or the first information indicates that the second AMF network element is located in a non-direct network sharing area.

[0183] As an optional manner, the UDM network element may execute the above S502 and S503 when it is determined that the home network of the first terminal supports indirect network sharing.

[0184] S504, the UDM network element sends a second message. Correspondingly, the first AMF network element receives the second message.

[0185] The second message is used to reject the first terminal from registering to the non-3GPP access side through the first AMF network element.

[0186] Optionally, the second message may carry a first cause value, where the first cause value is used to indicate that the first terminal is not allowed to register with the first AMF network element and the second AMF network element at the same time.

[0187] Optionally, after receiving the second message, the first AMF network element may send a fourth message to the N3IWF network element, wherein the fourth message is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the fourth message indicates that the first terminal postpones registration in the non-3GPP. Further, if the fourth message indicates that the first terminal postpones registration in the non-3GPP, the fourth message may also indicate the time for the first terminal to postpone registration in the non-3GPP.

[0188] This application is aimed at the scenario where the first terminal has registered in the 3GPP network and then registers on the non-3GPP access side. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, one AMF network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements. It can also avoid the problems caused by the existence of two AMF network elements in the same PLMN responsible for the mobility registration of the first terminal as described in the previous scenario A, for example, the first terminal cannot receive MT data packets, etc.

[0189] To facilitate understanding of the solution, the registration process of the first terminal in the INS area is described below by taking the first operator as the HOSTING OPERATOR and the second operator as the PARTICAPTING OPERATOR as an example.

[0190] like Figure 6 As shown, the registration process of the first terminal in the INS area may include:

[0191] S601, the access network device broadcasts PLMN information.

[0192] Since the second AMF network element is an AMF network element belonging to the HOSTING OPERATOR in the INS area, the PLMN information broadcast by the second AMF network element includes the PLMN information of the HOSTING OPERATOR (i.e., the PLMN information of the first operator) and the PLMN information of the PARTICAPTING OPERATOR (i.e., the PLMN information of the second operator).

[0193] S602: The first terminal sends a registration request message 1 to the access network device.

[0194] The registration request message 1 is used to request registration in the 3GPP network.

[0195] Optionally, assuming that the first terminal selects the PLMN of the second operator, that is, HPLMN / EHPLMN, the registration request message 1 carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator, that is, HPLMN / EHPLMN.

[0196] S603, the access network device sends a registration request message 2 to the second AMF network element.

[0197] The registration request message 2 is used to request the first terminal to register in the 3GPP network. Optionally, the registration request message 2 may carry the HPLMN / EHPLMN selected by the first terminal, that is, the HPLMN / EHPLMN of the second operator.

[0198] S604, the second AMF network element sends a registration request message 3 to the UDM network element.

[0199] Among them, the registration request message 3 is used to request the first terminal to register with the 3GPP network through the second AMF network element. Here, the registration request message 3 is the third message in the above text.

[0200] Optionally, the registration request message 3 may carry one or more of the following: the GUAMI of the second AMF network element, and the service network information registered by the first terminal in the 3GPP network. The GUAMI of the second AMF network element carries the HPLMN / EHPLMN selected by the first terminal, i.e., the PLMN of the second operator, i.e., HPLMN / EHPLMN, for example, <GUAMI of the second AMF network element> = <PLMN of the second operator, i.e., HPLMN / EHPLMN><AMF Identifier> The service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator.

[0201] Optionally, the above-mentioned AMF Identifier can be allocated by the second operator for the non-direct network sharing area.

[0202] S605, the UDM network element sends a response message of the registration request message 3 to the second AMF network element.

[0203] Among them, the response message of the registration request message 3 is used to confirm that the first terminal is registered to the 3GPP network through the second AMF network element.

[0204] S606, the second AMF network element sends a response message to the registration request message 2 to the access network device.

[0205] The response message of the registration request message 2 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 2 may carry the GUTI allocated by the second AMF network element to the first terminal, wherein the GUTI may carry the GUAMI of the second AMF network element, for example, <GUTI of the first terminal> = <GUAMI of the second AMF network element><5G-TMSI> = <PLMN of the second operator, i.e., HPLMN / EHPLMN><AMF Identifier> <5G-TMSI>.

[0206] S607: The access network device sends a response message to the registration request message 1 to the first terminal.

[0207] The response message of the registration request message 1 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 1 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0208] S608, the first terminal sends a registration request message 4 to the N3IWF network element.

[0209] Among them, the registration request message 4 is used to request registration on the non-3GPP access side. The registration request message 4 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0210] Since the first terminal selected the PLMN of the second operator, i.e., HPLMN / EHPLMN, when registering in the 3GPP network, the first terminal initiated registration on the non-3GPP access side in the same PLMN (i.e., the PLMN of the second operator, i.e., HPLMN / EHPLMN). Therefore, the N3IWF network element registered by the first terminal when registering on the non-3GPP access side belongs to the second operator.

[0211] S609, the N3IWF network element sends a registration request message 5 to the first AMF network element.

[0212] The registration request message 5 is used to request the first terminal to register on the non-3GPP access side. Optionally, the registration request message 5 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0213] Since the N3IWF network element belongs to the second operator, and the GUTI carried in the registration request message 4 points to the second AMF network element of the first operator, there is no connection between the N3IWF network element and the second AMF network element. Therefore, the N3IWF network element reselects an AMF network element belonging to the second operator (i.e., the first AMF network element) for registration.

[0214] S610, the first AMF network element sends a registration request message 6 to the UDM network element.

[0215] Among them, the registration request message 6 is used to request the first terminal to register to the non-3GPP access side through the first AMF network element. Optionally, the registration request message 6 can carry the GUAMI of the first AMF network element. Among them, the GUAMI of the first AMF network element carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator, that is, HPLMN / EHPLMN, for example, <GUAMI of the first AMF network element> = <PLMN of the second operator, that is, HPLMN / EHPLMN><AMF Identifier of the first AMF network element>. The registration message 6 here is the first message mentioned above.

[0216] S611: The UDM network element determines whether to allow the first terminal to register on the non-3GPP access side.

[0217] Optionally, the UDM network element may determine that the first terminal is not allowed to register on the non-3GPP access side by satisfying the following two conditions:

[0218] Condition A: The first AMF network element and the second AMF network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0219] Condition B: the second AMF network element belongs to the HOSTING OPERATOR.

[0220] The specific method can refer to the related description of S502 and S503 above, which will not be elaborated here.

[0221] Optionally, the UDM network element may also determine that the following condition is met: the AMF network element registered by the first terminal in 3GPP is different from the AMF network element registered in non-3GPP, thereby determining that the first terminal is not allowed to register on the non-3GPP access side.

[0222] Optionally, the UDM network element may also determine that the following conditions are met: the first AMF network element and the second AMF network element are from the home PLMN, or the first AMF network element and the second AMF network element are from an equivalent home PLMN. Thus, it is determined that the first terminal is not allowed to register on the non-3GPP access side.

[0223] In a possible implementation manner, the UDM network element may execute S611 when it is determined that the home network of the first terminal supports indirect network sharing.

[0224] In one possible implementation, if the terminal attempts to be served by 3GPP access through non-direct network sharing, where the shared RAN broadcasts the HPLMN (or EHPLMN) ID, and through a non-3GPP access with the same HPLMN or EHPLMN ID, the registration process is as follows: When a new AMF network element in the HPLMN (or EHPLMN) registers to the UDM network element due to the terminal registering through a non-3GPP access, the UDM network element checks whether a different AMF network element with the same PLMN ID has been registered to the UDM network element through a 3GPP access. If there is an AMF network element with the same PLMN ID registered on the UDM network element for 3GPP access, and the UDM network element determines that the AMF network element is in the PLMN of the hosting operator based on the implementation mechanism (such as a special GUAMI range), the UDM network element refuses to register the AMF network element for the non-3GPP access. Based on the rejection received from the UDM network element, the AMF network element may refuse the terminal registration through a non-3GPP access with a backoff timer. This enables one AMF network element to be responsible for the mobility registration of the first terminal, which complies with the protocol requirements. It can also avoid the problem described in the previous scenario A that the 3GPP registration of the first terminal cannot be switched to the AMF network element selected by the non-3GPP registration, resulting in the existence of two AMF network elements responsible for the mobility registration of the first terminal. For example, after the first terminal registers on the non-3GPP access side, the 3GPP registration of the first terminal cannot be switched to the AMF network element selected by the non-3GPP registration, resulting in the first terminal being unable to receive MT data packets, etc.

[0225] In this scenario, if the above-mentioned condition that the first terminal is not allowed to register on the non-3GPP access side is met, S612 is executed.

[0226] S612, the UDM network element sends a response message of the registration request message 6 to the first AMF network element.

[0227] The response message of the registration request message 6 is used to reject the first terminal from registering to the non-3GPP access side through the first AMF network element. The response message of the registration request message 6 is the second message mentioned above.

[0228] Optionally, the response message of the registration request message 6 may carry a first cause value, where the first cause value is used to indicate that the first terminal is not allowed to register with the first AMF network element and the second AMF network element at the same time.

[0229] S613, the first AMF network element sends a response message of the registration request message 5 to the N3IWF network element.

[0230] The response message of the registration request message 5 is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the response message of the registration request message 5 indicates that the first terminal postpones the registration in the non-3GPP. The response message of the registration request message 5 is the fourth message above.

[0231] Further, if the response message to the registration request message 5 indicates that the first terminal postpones the registration in the non-3GPP, the response message to the registration request message 5 may also indicate the time for the first terminal to postpone the registration in the non-3GPP.

[0232] Optionally, the response message of the registration request message 5 can use the existing registration reason value of the first AMF network element to indicate that the first terminal cannot register in NON-3GPP in the current area, or postpone the registration in non-3GPP.

[0233] S614, the N3IWF network element sends a response message of the registration request message 4 to the first terminal.

[0234] The response message of the registration request message 4 is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the response message of the registration request message 4 indicates that the first terminal postpones registration in the non-3GPP.

[0235] Further, if the response message of the registration request message 4 indicates that the first terminal postpones the registration in the non-3GPP, the response message of the registration request message 4 may also indicate the time for the first terminal to postpone the registration in the non-3GPP.

[0236] Optionally, the response message of the registration request message 4 may carry the registration reason value in the response message of the registration request message 5.

[0237] It should be noted that S601 to S609, S613, and S614 are optional steps.

[0238] This application is aimed at the scenario where the first terminal has registered in the 3GPP network and then registers on the non-3GPP access side. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, one AMF network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements. It can also avoid the problems caused by the existence of two AMF network elements in the same PLMN responsible for the mobility registration of the first terminal as described in the previous scenario A, for example, the first terminal cannot receive MT data packets, etc.

[0239] Embodiment 2:

[0240] like Figure 7 , which is a flow chart of another network registration method provided in an embodiment of the present application.

[0241] S701, the N3IWF network element sends a first message. Correspondingly, the first AMF network element receives the first message.

[0242] The first message is used to request the first terminal to register to the non-3GPP access side of the first PLMN through the first AMF network element.

[0243] Optionally, before S701, the first terminal may register with the 3GPP network through the second AMF network element.

[0244] S702, the first AMF network element determines that the first terminal has registered with the 3GPP network of the first PLMN through the second AMF network element.

[0245] In one possible implementation, since the first terminal is registered in the 3GPP network, the second AMF network element allocates a GUTI to the first terminal when the first terminal accesses the 3GPP network. The first message may carry the GUTI, so that the first AMF network element may determine, based on the GUTI, that the first terminal has registered with the 3GPP network of the first PLMN through the second AMF network element.

[0246] S703, the first AMF network element determines that the second AMF network element belongs to the HOSTING OPERATOR.

[0247] In one possible implementation, the first AMF network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the GUAMI of the second AMF network element. For example, if the GUAMI of the second AMF network element belongs to a specific value range, the first AMF network element can determine that the second AMF network element belongs to the HOSTING OPERATOR, where the specific value range is allocated by the PARTICIPATINGOPERATOR for the non-direct sharing area. For example, the AMFIdentifier carried by the GUAMI of the second AMF network element can be allocated by the second operator for the non-direct network sharing area.

[0248] Exemplarily, the first AMF network element can obtain the GUAMI of the second AMF network element through the GUTI carried by the first message.

[0249] In another possible implementation, the second AMF network element may send first information to the first AMF network element, and the first information indicates that the second AMF network element belongs to the HOSTING OPERATOR. Thus, the first AMF network element may determine that the second AMF network element belongs to the HOSTING OPERATOR based on the first information.

[0250] For example, the first AMF network element may send a third message to the second AMF network element, where the third message is used to request the context information of the first terminal from the second AMF network element. The second AMF network element sends a fourth message to the first AMF network element, where the fourth message carries the context information of the first terminal and the first information.

[0251] As an optional method, the first AMF network element may execute the above S702 and S703 when determining that the home network of the first terminal supports indirect network sharing.

[0252] S704, the first AMF network element sends a second message. Correspondingly, the N3IWF network element receives the second message.

[0253] The second message is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the second message indicates that the first terminal postpones registering in the non-3GPP.

[0254] Further, if the second message instructs the first terminal to postpone registration in the non-3GPP, the second message may also indicate a time for the first terminal to postpone registration in the non-3GPP.

[0255] This application is aimed at the scenario where the first terminal has registered in the 3GPP network and then registers on the non-3GPP access side. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, one AMF network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements. It can also avoid the problems caused by the existence of two AMF network elements in the same PLMN responsible for the mobility registration of the first terminal as described in the previous scenario A, for example, the first terminal cannot receive MT data packets, etc.

[0256] To facilitate understanding of the solution, the registration process of the first terminal in the INS area is described below by taking the first operator as the HOSTING OPERATOR and the second operator as the PARTICAPTING OPERATOR as an example.

[0257] like Figure 8 As shown, the registration process of the first terminal in the INS area may include:

[0258] S801, the access network device broadcasts PLMN information.

[0259] The broadcasted PLMN information includes the PLMN information of the HOSTING OPERATOR (ie, the PLMN information of the first operator) and the PLMN information of the PARTICAPTING OPERATOR (ie, the PLMN information of the second operator).

[0260] S802: The first terminal sends a registration request message 1 to the access network device.

[0261] The registration request message 1 is used to request registration in the 3GPP network.

[0262] Optionally, assuming that the first terminal selects the HPLMN / EHPLMN of the second operator, the registration request message 1 carries the HPLMN / EHPLMN selected by the first terminal, that is, the HPLMN / EHPLMN of the second operator.

[0263] S803, the access network device sends a registration request message 2 to the second AMF network element.

[0264] The registration request message 2 is used to request the first terminal to register in the 3GPP network. Optionally, the registration request message 2 may carry the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator.

[0265] S804, the second AMF network element sends a registration request message 3 to the UDM network element.

[0266] Among them, the registration request message 3 is used to request the first terminal to register to the 3GPP network through the second AMF network element.

[0267] Optionally, the registration request message 3 may carry one or more of the following: the GUAMI of the second AMF network element, and the service network information registered by the first terminal in the 3GPP network. The GUAMI of the second AMF network element carries the HPLMN / EHPLMN selected by the first terminal, i.e., the PLMN of the second operator, i.e., HPLMN / EHPLMN, for example, <GUAMI of the second AMF network element> = <PLMN of the second operator, i.e., HPLMN / EHPLMN><AMF Identifier> The service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator.

[0268] Optionally, the above-mentioned AMF Identifier can be allocated by the second operator for the non-direct network sharing area.

[0269] S805, the UDM network element sends a response message of the registration request message 3 to the second AMF network element.

[0270] Among them, the response message of the registration request message 3 is used to confirm that the first terminal is registered to the 3GPP network through the second AMF network element.

[0271] S806, the second AMF network element sends a response message to the registration request message 2 to the access network device.

[0272] Among them, the response message of the registration request message 2 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 2 may carry the GUTI allocated by the second AMF network element to the first terminal, wherein the GUTI may carry the GUAMI of the second AMF network element, for example, <GUTI of the first terminal> = <GUAMI of the second AMF network element><5G-TMSI> = <PLMN of the second operator, i.e. HPLMN / EHPLMN><AMF Identifier of the second AMF network element><5G-TMSI>.

[0273] S807, the access network device sends a response message to the registration request message 1 to the first terminal.

[0274] The response message of the registration request message 1 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 1 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0275] S808, the first terminal sends a registration request message 4 to the N3IWF network element.

[0276] Among them, the registration request message 4 is used to request registration on the non-3GPP access side. The registration request message 4 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0277] The N3IWF network element registered by the first terminal when registering on the non-3GPP access side belongs to the second operator.

[0278] S809, N3IWF network element sends a registration request message 5 to the first AMF network element.

[0279] Among them, the registration request message 5 is used to request the first terminal to register on the non-3GPP access side. Optionally, the registration request message 5 can carry the GUTI allocated by the second AMF network element to the first terminal. Here, the registration request message 5 is the first message mentioned above.

[0280] Since the N3IWF network element belongs to the second operator, and the GUTI carried in the registration request message 4 points to the second AMF network element of the first operator, there is no connection between the N3IWF network element and the second AMF network element. Therefore, the N3IWF network element reselects an AMF network element belonging to the second operator (i.e., the first AMF network element) for registration.

[0281] S810, the first AMF network element determines whether to allow the first terminal to register on the non-3GPP access side.

[0282] For example, the first AMF network element may not allow the first terminal to register in non-3GPP when determining that the following conditions are met:

[0283] Condition A: The first terminal has registered with the 3GPP network of the first PLMN through the second AMF network element.

[0284] Condition B: the second AMF network element belongs to the HOSTING OPERATOR.

[0285] The specific method can refer to the relevant description of S702 and S703 above, which will not be elaborated here.

[0286] In one possible implementation, the first AMF network element may execute S810 when determining that the home network of the first terminal supports indirect network sharing.

[0287] In this scenario, if the above-mentioned condition that the first terminal is not allowed to register on the non-3GPP access side is met, S811 is executed.

[0288] S811, the first AMF network element sends a response message of the registration request message 5 to the N3IWF network element.

[0289] The response message of the registration request message 5 is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the response message of the registration request message 5 indicates that the first terminal postpones the registration in the non-3GPP. The response message of the registration request message 5 is the second message mentioned above.

[0290] Further, if the response message to the registration request message 5 indicates that the first terminal postpones the registration in the non-3GPP, the response message to the registration request message 5 may also indicate the time for the first terminal to postpone the registration in the non-3GPP.

[0291] Optionally, the response message of the registration request message 5 can use the existing registration reason value of the first AMF network element to indicate that the first terminal cannot register in NON-3GPP in the current area, or postpone the registration in non-3GPP.

[0292] S812, the N3IWF network element sends a response message of the registration request message 4 to the first terminal.

[0293] The response message of the registration request message 4 is used to indicate that the first terminal cannot register in the non-3GPP in the current area, or the response message of the registration request message 4 indicates that the first terminal postpones registration in the non-3GPP.

[0294] Further, if the response message of the registration request message 4 indicates that the first terminal postpones the registration in the non-3GPP, the response message of the registration request message 4 may also indicate the time for the first terminal to postpone the registration in the non-3GPP.

[0295] Optionally, the response message of the registration request message 4 may carry the registration reason value in the response message of the registration request message 5.

[0296] It should be noted that S801 to S808 and S812 are optional steps.

[0297] This application is aimed at the scenario where the first terminal has registered in the 3GPP network and then registers on the non-3GPP access side. By rejecting or postponing the registration of the first terminal on the non-3GPP access side, one AMF network element is responsible for the mobility registration of the first terminal, which complies with the protocol requirements. It can also avoid the problems caused by the existence of two AMF network elements in the same PLMN responsible for the mobility registration of the first terminal as described in the previous scenario A, for example, the first terminal cannot receive MT data packets, etc.

[0298] Embodiment three:

[0299] like Fig. 9 The figure is a flow chart of a network registration method provided in an embodiment of the present application.

[0300] S901, the second AMF network element sends a second message. Correspondingly, the first AMF network element receives the second message.

[0301] The second message is used to request that the context of the first terminal be migrated to the second AMF network element. Optionally, the second message may carry the GUAMI of the second AMF network element.

[0302] Optionally, the second AMF network element may send a second message triggered by the first message, wherein the first message is used to request the first terminal to register with the 3GPP network through the second AMF network element, and the first message carries the GUTI allocated by the first AMF network element to the first terminal when the first terminal registers with the non-3GPP access side.

[0303] Optionally, before S901, the first terminal may register with the non-3GPP access side through the first AMF network element. In one example, before requesting to register with the 3GPP network through the second AMF network element, the first terminal may register with the non-3GPP access side through the first AMF network element.

[0304] In an exemplary description, the first AMF network element belongs to the PARTICAPTING OPERATOR, and the second AMF network element belongs to the HOSTING OPERATOR.

[0305] S902, the first AMF network element determines to delete the context information of the first terminal in the N3IWF network element.

[0306] In a possible implementation, if the second AMF network element belongs to the HOSTING OPERATOR, the second AMF network element may send a first message to the first AMF network element, where the first message is used to instruct the non-3GPP access side to delete the context information of the first terminal. Thus, the first AMF network element may determine to delete the context information of the first terminal on the non-3GPP access side according to the first information sent by the second AMF network element.

[0307] Exemplarily, the first information may indirectly instruct the non-3GPP access side to delete the context information of the first terminal by instructing the first terminal to register in the 3GPP network. Alternatively, the first information may directly instruct to delete the context information of the first terminal in the non-3GPP access side.

[0308] The following introduces two ways in which the second AMF network element sends the first information.

[0309] Method 1: The second AMF network element may send the first information when requesting the context information of the first terminal from the first AMF network element. For example, the second message may carry the first information.

[0310] Method 2: The second AMF network element can obtain the context information of the first terminal, and determine that the first terminal has been registered on the non-3GPP access side based on the context information of the first terminal. Optionally, after the first terminal is in a connected state in the non-3GPP access side, it sends the first information to the first AMF network element. For example, after receiving the second message, the first AMF network element sends a third message to the second AMF network element, and the third message carries the context information of the first terminal. The second AMF network element determines that the first terminal has been registered on the non-3GPP access side based on the context information of the first terminal. Optionally, when the first terminal is in a connected state in the non-3GPP access side, it sends a fourth message to the first AMF network element, and the fourth message is used to confirm that the context information of the first terminal in the first AMF network element has been received, and the fourth message carries the first information.

[0311] In one possible implementation, the second AMF network element may send the first information to the first AMF network element when it is determined that the home network of the first terminal supports indirect network sharing.

[0312] Optionally, before sending the first information to the first AMF network element, the second AMF network element may also determine that the first AMF network element belongs to the PARTICAPTING OPERATOR.

[0313] As an optional solution, in the above implementation, the second AMF network element can determine the first AMF network element according to the GUTI carried in the first message after receiving the first message from the access network device. The first message is used to request the first terminal to register with the 3GPP network through the second AMF network element, and the first message carries the GUTI allocated by the first AMF network element to the first terminal when the first terminal registers with the non-3GPP access side.

[0314] In another possible implementation, the first AMF network element can determine to delete the context information of the first terminal in the N3IWF network element by determining that the second AMF network element belongs to the HOSTINGOPERATOR.

[0315] For example, the first AMF network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the GUAMI of the second AMF network element. For example, if the GUAMI of the second AMF network element belongs to a specific value range, the first AMF network element can determine that the second AMF network element belongs to the HOSTING OPERATOR, where the specific value range is allocated by the PARTICIPATING OPERATOR for the non-direct sharing area. For example, the AMF Identifier carried by the GUAMI of the second AMF network element can be allocated by the second operator for the non-direct network sharing area.

[0316] Exemplarily, the first AMF network element can obtain the GUAMI of the second AMF network element through the second message.

[0317] S903, the first AMF network element sends the second information. Correspondingly, the N3IWF network element receives the second information.

[0318] The second information is used to instruct the non-3GPP interworking function network element to delete the context information of the first terminal.

[0319] S904, N3IWF deletes the context information of the first terminal.

[0320] Since the context information of the first terminal on the N3IWF network element is deleted, the connection state of the first terminal on the non-3GPP access side changes to an idle state.

[0321] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The AMF network element on the non-3GPP access side can release the context information of the first terminal in the N3IWF network element in a timely manner by receiving an instruction to delete the context information of the first terminal on the non-3GPP access side, thereby saving the resources of the N3IWF network element. In addition, by releasing the context information of the first terminal in the N3IWF network element in a timely manner, the first terminal can be released to an idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0322] To facilitate understanding of the solution, the registration process of the first terminal in the INS area is described below by taking the first operator as the HOSTING OPERATOR and the second operator as the PARTICAPTING OPERATOR as an example.

[0323] like Fig.10 As shown, the registration process of the first terminal in the INS area may include:

[0324] S1001, access network equipment broadcasts PLMN information.

[0325] The broadcasted PLMN information includes the PLMN information of the HOSTING OPERATOR (ie, the PLMN information of the first operator) and the PLMN information of the PARTICAPTING OPERATOR (ie, the PLMN information of the second operator).

[0326] S1002, the first terminal sends a registration request message 1 to the N3IWF network element.

[0327] The registration request message 1 is used to request registration on the non-3GPP access side.

[0328] Optionally, assuming that the first terminal selects the PLMN of the second operator, that is, HPLMN / EHPLMN, the registration request message 1 carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator.

[0329] The N3IWF network element registered by the first terminal when registering on the non-3GPP access side belongs to the second operator.

[0330] S1003, N3IWF network element sends registration request message 2 to the first AMF network element.

[0331] The registration request message 2 is used to request the first terminal to register on the non-3GPP access side. Optionally, the registration request message 2 carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator.

[0332] S1004, the first AMF network element sends a registration request message 3 to the UDM network element.

[0333] Among them, the registration request message 3 is used to request the first terminal to register to the non-3GPP access side through the first AMF network element. Optionally, the registration request message 3 can carry the GUAMI of the first AMF network element. Among them, the GUAMI of the first AMF network element carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator, for example, <GUAMI of the first AMF network element> = <PLMN of the second operator, that is, HPLMN / EHPLMN><AMF Identifier of the first AMF network element>.

[0334] S1005, the UDM network element sends a response message of the registration request message 3 to the first AMF network element.

[0335] Among them, the response message of the registration request message 3 is used to confirm that the first terminal is registered to the non-3GPP access side through the first AMF network element.

[0336] S1006, the first AMF network element sends a response message of the registration request message 2 to the N3IWF network element.

[0337] The response message of the registration request message 2 is used to confirm the registration of the first terminal on the non-3GPP access side. Optionally, the response message of the registration request message 2 may carry the GUTI allocated by the first AMF network element to the first terminal, wherein the GUTI may carry the GUAMI of the first AMF network element, for example, <GUTI of the first terminal> = <GUAMI of the first AMF network element><5G-TMSI> = <PLMN of the second operator, i.e., HPLMN / EHPLMN><AMF Identifier> <5G-TMSI>. The GUTI points to the first AMF network element of the second operator.

[0338] Optionally, the above-mentioned AMF Identifier can be allocated by the second operator for the non-direct network sharing area.

[0339] S1007, the N3IWF network element sends a response message of the registration request message 1 to the first terminal.

[0340] The response message of the registration request message 1 is used to confirm the registration of the first terminal on the non-3GPP access side. Optionally, the response message of the registration request message 1 may carry the GUTI allocated by the first AMF network element to the first terminal.

[0341] S1008, the first terminal sends a registration request message 4 to the access network device.

[0342] The registration request message 4 is used to request registration in the 3GPP network. The registration request message 4 may carry the GUTI allocated by the first AMF network element to the first terminal.

[0343] The first terminal selects the same PLMN (ie, the PLMN of the second operator, ie, HPLMN / EHPLMN) to initiate registration in the 3GPP network.

[0344] S1009, the access network device sends a registration request message 5 to the second AMF network element.

[0345] Among them, the registration request message 5 is used to request the first terminal to register in the 3GPP network. Optionally, the registration request message 5 can carry the GUTI allocated by the first AMF network element to the first terminal. Here, the registration request message 5 is the first message mentioned above.

[0346] Since the GUTI carried by the registration request message 4 points to the first AMF network element of the second operator, and the first terminal is in a non-direct network sharing area, the access network device reselects an AMF network element belonging to the first operator (i.e., the second AMF network element) for registration.

[0347] The second AMF network element triggers the migration of the context information of the first terminal from the first AMF network element to the second AMF network element.

[0348] S1010, the second AMF network element sends a context request message to the first AMF network element.

[0349] The context request message is used to request the context information of the first terminal. The context request message here is the second message mentioned above.

[0350] S1011, the first AMF network element sends a response message to the context request message to the second AMF network element.

[0351] The response message to the context request message carries the response message to the context request message, and the response message to the context request message is the third message mentioned above.

[0352] Optionally, the second AMF network element may also send a registration status update message to the first AMF network element. The registration status update message is used to confirm receipt / update of context information of the first terminal. The registration status update message here is the fourth message above.

[0353] S1012, the first AMF network element determines to delete the context information of the first terminal in the N3IWF network element.

[0354] Among them, the specific way in which the first AMF network element determines to delete the context information of the first terminal in the N3IWF network element can be found in the relevant instructions of S902, which will not be repeated here.

[0355] S1013, the first AMF network element sends the second information to the N3IWF network element.

[0356] The second information is used to instruct the N3IWF network element to delete the context information of the first terminal.

[0357] Optionally, the first AMF network element may delete the context information of the first terminal.

[0358] S1014, the N3IWF network element deletes the context information of the first terminal.

[0359] It should be noted that the present application does not limit the execution order of S1012 to S1014 and S1011.

[0360] Since the context information of the first terminal on the N3IWF network element is deleted, the connection state of the first terminal on the non-3GPP access side changes to an idle state.

[0361] S1015, the second AMF network element allocates a GUTI to the first terminal.

[0362] S1016, the second AMF network element sends a response message to the registration request message 5 to the access network device.

[0363] The response message of the registration request message 5 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 5 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0364] S1017, the access network device sends a response message of the registration request message 4 to the first terminal.

[0365] The response message of the registration request message 4 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 4 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0366] It should be noted that S1001 to S1008, S1010 to S1011, and S1015 to S1017 are optional steps.

[0367] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The AMF network element on the non-3GPP access side can release the context information of the first terminal in the N3IWF network element in a timely manner by instructing the non-3GPP access side to delete the context information of the first terminal, thereby saving the resources of the N3IWF network element. In addition, by releasing the context information of the first terminal in the N3IWF network element in a timely manner, the first terminal can be released to an idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0368] Embodiment 4:

[0369] like Fig.11 The figure is a flow chart of a network registration method provided in an embodiment of the present application.

[0370] S1101, the second AMF network element sends a first message. Correspondingly, the UDM network element receives the first message, and the first message is used to request that the first AMF network element registered by the first terminal in the non-3GPP access side be updated to the second AMF network element.

[0371] As an exemplary illustration, the first AMF network element and the second AMF network element are located in the same PLMN.

[0372] Optionally, the second AMF network element may obtain the context information of the first terminal from the first AMF network element and then send the first message.

[0373] In one possible implementation, before S1101, the second AMF network element may send a third message to the UDM network element, wherein the third message is used to request the first terminal to register with the 3GPP network through the second AMF network element.

[0374] As a possible scenario, before the second AMF network element sends the third message, the first terminal has registered with the non-3GPP access side through the first AMF.

[0375] S1102, the UDM network element determines that the second AMF network element belongs to the HOSTING OPERATOR.

[0376] In one possible implementation, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the GUAMI of the second AMF network element. For example, if the GUAMI of the second AMF network element belongs to a specific value range, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR, where the specific value range is allocated by the PARTICIPATING OPERATOR for the non-direct sharing area. For example, the AMF Identifier carried by the GUAMI of the second AMF network element can be allocated by the second operator for the non-direct network sharing area.

[0377] Exemplarily, the UDM network element can obtain the GUAMI of the second AMF network element through the registration request of the second AMF network element (ie, the third message above). For example, the third message carries the GUAMI of the second AMF network element.

[0378] In another possible implementation, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network. For example, if the service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR, and the first operator is the HOSTING OPERATOR.

[0379] Exemplarily, the UDM network element can obtain the service network information registered by the first terminal in the 3GPP network through the registration request (i.e., the third message above) of the second AMF network element. For example, the third message carries the service network information registered by the first terminal in the 3GPP network.

[0380] In another possible implementation, the UDM network element may determine that the second AMF network element belongs to the HOSTING OPERATOR based on the indication information carried by the registration request of the second AMF network element (i.e., the third message in the previous text). For example, the third message carries the second information, wherein the second information indicates that the second AMF network element belongs to the HOSTING OPERATOR, or the second information indicates that the second AMF network element is located in a non-direct network sharing area.

[0381] As an optional manner, the UDM network element may execute the above S1102 when it is determined that the home network of the first terminal supports indirect network sharing.

[0382] S1103, the UDM network element sends the first information. Correspondingly, the first AMF network element receives the first information.

[0383] The first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0384] In one possible implementation, the UDM network element may send the first information through a second message, wherein the second message instructs the first AMF network element to register.

[0385] S1104, the first AMF network element sends the third information. Correspondingly, the N3IWF network element receives the third information.

[0386] The third information is used to instruct the N3IWF network element to delete the context information of the first terminal.

[0387] Optionally, the first AMF network element may send third information to the N3IWF network element if it is determined that the N3IWF network element has context information of the first terminal.

[0388] S1105, the N3IWF network element deletes the context information of the first terminal.

[0389] Since the context information of the first terminal on the N3IWF network element is deleted, the connection state of the first terminal on the non-3GPP access side changes to an idle state.

[0390] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The UDM network element can timely release the context information of the first terminal in the N3IWF network element by instructing the non-3GPP access side to delete the context information of the first terminal, thereby saving the resources of the N3IWF network element. In addition, by timely releasing the context information of the first terminal in the N3IWF network element, the first terminal can be released to an idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0391] To facilitate understanding of the solution, the registration process of the first terminal in the INS area is described below by taking the first operator as the HOSTING OPERATOR and the second operator as the PARTICAPTING OPERATOR as an example.

[0392] like Fig.12 As shown, the registration process of the first terminal in the INS area may include:

[0393] S1201, the access network device broadcasts PLMN information.

[0394] Since the second AMF network element is an AMF network element belonging to the HOSTING OPERATOR in the INS area, the PLMN information broadcast by the second AMF network element includes the PLMN information of the HOSTING OPERATOR (i.e., the PLMN information of the first operator) and the PLMN information of the PARTICAPTING OPERATOR (i.e., the PLMN information of the second operator).

[0395] S1202, the first terminal sends a registration request message 1 to the N3IWF network element.

[0396] The registration request message 1 is used to request registration on the non-3GPP access side.

[0397] Optionally, assuming that the first terminal selects the PLMN of the second operator, that is, HPLMN / EHPLMN, the registration request message 1 carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator.

[0398] The N3IWF network element registered by the first terminal when registering on the non-3GPP access side belongs to the second operator.

[0399] S1203, N3IWF network element sends registration request message 2 to the first AMF network element.

[0400] The registration request message 2 is used to request the first terminal to register on the non-3GPP access side. Optionally, the registration request message 2 carries the HPLMN / EHPLMN selected by the first terminal, that is, the PLMN of the second operator.

[0401] S1204, the first AMF network element sends a registration request message 3 to the UDM network element.

[0402] Among them, the registration request message 3 is used to request the first terminal to register to the non-3GPP access side through the first AMF network element. Optionally, the registration request message 3 can carry the GUAMI of the first AMF network element. Among them, the GUAMI of the first AMF network element carries the HPLMN / EHPLMN selected by the first terminal, that is, the HPLMN / EHPLMN of the second operator, for example, <GUAMI of the first AMF network element> = <PLMN of the second operator, that is, HPLMN / EHPLMN><AMF Identifier of the first AMF network element>.

[0403] S1205, the UDM network element sends a response message of the registration request message 3 to the first AMF network element.

[0404] Among them, the response message of the registration request message 3 is used to confirm that the first terminal is registered to the non-3GPP access side through the first AMF network element.

[0405] S1206, the first AMF network element sends a response message of the registration request message 2 to the N3IWF network element.

[0406] Among them, the response message of the registration request message 2 is used to confirm the registration of the first terminal on the non-3GPP access side. Optionally, the response message of the registration request message 2 may carry the GUTI allocated by the first AMF network element to the first terminal, wherein the GUTI may carry the GUAMI of the first AMF network element, for example, <GUTI of the first terminal> = <GUAMI of the first AMF network element><5G-TMSI> = <PLMN of the second operator, i.e. HPLMN / EHPLMN><AMF Identifier of the first AMF network element><5G-TMSI>. The GUTI points to the first AMF network element of the second operator.

[0407] S1207, the N3IWF network element sends a response message of the registration request message 1 to the first terminal.

[0408] The response message of the registration request message 1 is used to confirm the registration of the first terminal on the non-3GPP access side. Optionally, the response message of the registration request message 1 may carry the GUTI allocated by the first AMF network element to the first terminal.

[0409] S1208, the first terminal sends a registration request message 4 to the access network device.

[0410] The registration request message 4 is used to request registration in the 3GPP network. The registration request message 4 may carry the GUTI allocated by the first AMF network element to the first terminal.

[0411] The first terminal selects the same PLMN (ie, the PLMN of the second operator, ie, HPLMN / EHPLMN) to initiate registration in the 3GPP network.

[0412] S1209, the access network device sends a registration request message 5 to the second AMF network element.

[0413] The registration request message 5 is used to request the first terminal to register in the 3GPP network. Optionally, the registration request message 5 may carry the GUTI allocated by the first AMF network element to the first terminal.

[0414] Since the GUTI carried by the registration request message 4 points to the first AMF network element of the second operator, and the first terminal is in a non-direct network sharing area, the access network device reselects an AMF network element belonging to the first operator (i.e., the second AMF network element) for registration.

[0415] The second AMF network element triggers the migration of the context information of the first terminal from the first AMF network element to the second AMF network element.

[0416] S1210, the second AMF network element sends a context request message to the first AMF network element.

[0417] The context request message is used to request context information of the first terminal.

[0418] S1211, the first AMF network element sends a response message to the context request message to the second AMF network element.

[0419] The response message to the context request message carries the response message to the context request message.

[0420] S1212, the second AMF network element sends a registration status update message to the first AMF network element.

[0421] The registration status update message is used to confirm receipt / update of the context information of the first terminal.

[0422] S1213, the second AMF network element sends a registration request message 6 to the UDM network element.

[0423] Among them, the registration request message 6 is used to request the first terminal to register to the 3GPP network through the AMF network element.

[0424] Optionally, the UDM network element may send a response message of the registration request message 6 to the second AMF network element.

[0425] S1214, the second AMF network element sends a registration request message 7 to the UDM network element.

[0426] Among them, the registration request message 7 is used to request that the AMF network element registered by the first terminal in the non-3GPP access side be updated to the second AMF network element. Here, the registration request message 7 is the first message in the previous text.

[0427] S1215: The UDM network element determines whether to allow the first terminal to update (or register) on the non-3GPP access side.

[0428] Optionally, the UDM network element may determine that the first terminal is not allowed to register on the non-3GPP access side by determining that the following two conditions are met:

[0429] Condition A: The first AMF network element and the second AMF network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0430] Condition B: The second AMF network element belongs to the HOSTING OPERATOR. The specific method can be found in the relevant description of S1102 above, which will not be described in detail here.

[0431] Optionally, when the UDM network element determines that the first terminal is not allowed to register on the non-3GPP access side, it can also determine that the following conditions are met: the AMF network element registered by the first terminal in 3GPP is different from the AMF network element registered in the non-3GPP.

[0432] Optionally, when the UDM network element determines that the first terminal is not allowed to register on the non-3GPP access side, it can also determine that the following conditions are met: the first AMF network element and the second AMF network element are from the home PLMN, or the first AMF network element and the second AMF network element are from an equivalent home PLMN.

[0433] In a possible implementation manner, the UDM network element may execute S1215 when determining that the home network of the first terminal supports indirect network sharing.

[0434] In one possible implementation, if the terminal attempts to be served by 3GPP access through non-direct network sharing, where the RAN broadcast HPLMN (or EHPLMN) ID is shared, and through non-3GPP access with the same HPLMN or EHPLMN ID, the registration process is as follows: When the new AMF network element in the hosting operator receives the terminal registration through 3GPP access, the new AMF network element can check whether the terminal was previously registered in the same PLMN through non-3GPP access, and whether the N3IWF / TNGF / W-AGF network element information is included in the retrieved terminal context. If so, the new AMF network element registers itself to the UDM network element for non-3GPP access, but does not update the terminal context on the N3IWF / TNGF / W-AGF network element. The old AMF network element releases the terminal context at the N3IWF / TNGF / W-AGF network element according to the deregistration notification from the UDM network element. Thereby, the context information of the first terminal in the N3IWF network element can be released in time, thereby saving the resources of the N3IWF network element. Furthermore, by timely releasing the context information of the first terminal in the N3IWF network element, the first terminal can be released to the idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0435] In this scenario, since the AMF network element registered by the first terminal on the non-3GPP access side is updated to the second AMF network element, the above-mentioned conditions for allowing the first terminal to register on the non-3GPP access side are met, that is, the second AMF network element is allowed to register on the non-3GPP access side, then S1216 is executed.

[0436] S1216, the UDM network element sends a registration message to the first AMF network element.

[0437] The deregistration message is used to instruct the first AMF network element to deregister. Optionally, the deregistration message may carry the first information. The deregistration message here is the second message mentioned above.

[0438] S1217, the first AMF network element deletes the context information of the first terminal.

[0439] Optionally, the first AMF network element may send a response message to the deregistration message to the UDM network element, where the response message to the deregistration message is used to confirm that the first AMF network element has been deregistered.

[0440] Optionally, the UDM network element may send a response message to the registration request message 7 to the second AMF network element, wherein the response message to the registration request message 7 is used to confirm the registration of the second AMF network element on the non-3GPP access side.

[0441] If the first AMF network element is connected to the N3IWF network element, that is, the first terminal is in a connected state on the non-3GPP access side, the first AMF network element instructs the N3IWF network element to delete the context information of the first terminal, that is, step S1217.

[0442] S1218, the first AMF network element sends the third information to the N3IWF network element.

[0443] The third information is used to instruct the N3IWF network element to delete the context information of the first terminal.

[0444] S1219, the N3IWF network element deletes the context information of the first terminal.

[0445] Since the context information of the first terminal on the N3IWF network element is deleted, the connection state of the first terminal on the non-3GPP access side changes to an idle state.

[0446] S1220, the second AMF network element allocates a GUTI to the first terminal.

[0447] S1221, the second AMF network element sends a response message to the registration request message 5 to the access network device.

[0448] The response message of the registration request message 5 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 5 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0449] S1222, the access network device sends a response message of the registration request message 4 to the first terminal.

[0450] The response message of the registration request message 4 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of the registration request message 4 may carry the GUTI allocated by the second AMF network element to the first terminal.

[0451] It should be noted that S1201 to S1213, S1217, and S1220 to S1222 are optional steps.

[0452] This application is aimed at the scenario where the first terminal is registered on the non-3GPP access side and then registered on the 3GPP network. The UDM network element can timely release the context information of the first terminal in the N3IWF network element by instructing the non-3GPP access side to delete the context information of the first terminal, thereby saving the resources of the N3IWF network element. In addition, by timely releasing the context information of the first terminal in the N3IWF network element, the first terminal can be released to an idle state in a timely manner, thereby avoiding communication anomalies of the first terminal on the non-3GPP access side.

[0453] Based on the same inventive concept as the method embodiment, the present application embodiment provides a communication device, the structure of which can be as follows: Fig.13 As shown, it includes a communication unit 701 and a processing unit 702.

[0454] In one embodiment, the communication device can be used to implement Figure 5 In the embodiment of the method executed by the UDM network element, the device may be the UDM network element itself, or a chip or chipset in the UDM network element or a part of the chip for executing the function of the related method. Among them, the communication unit 701 is used to receive a first message, and the first message is used to request the first terminal to register to the non-3GPP access side through the first mobility management function network element. The processing unit 702 is used to determine that the first mobility management function network element and the second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN; and, determine that the second mobility management function network element belongs to the HOSTING OPERATOR; the communication unit 701 is also used to send a second message, and the second message is used to refuse the first terminal to register to the non-3GPP access side through the first mobility management function network element.

[0455] Exemplarily, the processing unit 702 is specifically configured to: determine, according to a globally unique mobility management function identifier GUAMI of the second mobility management function network element, that the second mobility management function network element belongs to a HOSTING OPERATOR.

[0456] Exemplarily, the processing unit 702, when determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the GUAMI of the second mobility management function network element, is specifically used to: determine that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PATRICIPATING OPERATOR for a non-direct shared area.

[0457] Exemplarily, the processing unit 702 is specifically configured to: determine, according to the service network information registered by the first terminal in the 3GPP network, that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0458] Exemplarily, when the processing unit 702 determines that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network, it is specifically used to: determine that the service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator, and the first operator is the HOSTING OPERATOR.

[0459] Exemplarily, the processing unit 702 is specifically used to: receive a third message through the communication unit 701, the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, and the third message carries first information, wherein the first information indicates that the second mobility management function network element belongs to the HOSTINGOPERATOR, or the first information indicates that the second mobility management function network element is located in a non-direct network sharing area.

[0460] Exemplarily, the processing unit 702 is specifically used to: if the PLMN information carried by the GUAMI of the second mobility management function network element is the same as the PLMN information carried by the GUAMI of the first mobility management function network element, determine that the first mobility management function network element and the second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0461] Optionally, the processing unit 702 is further used to determine, before the communication unit 701 sends the second message, that the first mobility management function network element and the second mobility management function network element are from a home PLMN; or, to determine that the first mobility management function network element and the second mobility management function network element are from an equivalent home PLMN.

[0462] Optionally, the processing unit 702 is further configured to determine, before the communication unit 701 sends the second message, whether the home network of the first terminal supports indirect network sharing.

[0463] In one embodiment, the communication device can be used to implement Fig.11 In the embodiment of the method executed by the UDM network element, the device can be the UDM network element itself, or it can be a chip or chipset in the UDM network element or a part of the chip used to execute the function of the relevant method. Among them, the communication unit 701 is used to receive a first message, and the first message is used to request that the first mobility management function network element registered by the first terminal in the non-3GPP access side be updated to the second mobility management function network element; the processing unit 702 is used to determine that the second mobility management function network element belongs to the HOSTING OPERATOR; the communication unit 701 is also used to send a first message, and the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0464] Exemplarily, the communication unit 701 is specifically used to: send a second message, where the second message instructs the first mobility management function network element to deregister, and the second message carries the first information.

[0465] Exemplarily, the processing unit 702 is specifically configured to: determine, according to a globally unique mobility management function identifier GUAMI of the second mobility management function network element, that the second mobility management function network element belongs to a HOSTING OPERATOR.

[0466] Exemplarily, the processing unit 702, when determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the GUAMI of the second mobility management function network element, is specifically used to: determine that the GUAMI of the second mobility management function network element belongs to a specific value range, and the specific value range is allocated by the PATRICIPATING OPERATOR for a non-direct shared area.

[0467] Exemplarily, the processing unit 702 is specifically configured to: determine, according to the service network information registered by the first terminal in the 3GPP network, that the second mobility management function network element belongs to the HOSTING OPERATOR.

[0468] Exemplarily, when the processing unit 702 determines that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network, it is specifically used to: determine that the service network information registered by the first terminal in the 3GPP network is the PLMN information of the first operator, and the first operator is the HOSTING OPERATOR.

[0469] Exemplarily, the processing unit 702 is specifically used to: receive a third message through the communication unit 701, the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, and the third message carries second information, wherein the second information indicates that the second mobility management function network element belongs to the HOSTINGOPERATOR, or the second information indicates that the second mobility management function network element is located in a non-direct network sharing area.

[0470] In one embodiment, the communication device can be used to implement Fig.11 In the embodiment of the method executed by the first AMF network element, the device can be the first AMF network element itself, or it can be a chip or chipset in the first AMF network element or a part of the chip used to execute the function of the relevant method. Among them, the processing unit 702 is used to receive first information through the communication unit 701, and the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal; and send third information through the communication unit 701, and the third information is used to instruct the non-3GPP interworking function network element to delete the context information of the first terminal.

[0471] Optionally, the processing unit 702 is further configured to determine, before sending the third information through the communication unit 701, whether the context information of the first terminal exists on the non-3GPP interworking function network element.

[0472] Optionally, when receiving the first information through the communication unit 701, the processing unit 702 is specifically used to: receive a second message through the communication unit 701, the second message instructing the first mobility management function network element to deregister, and the second message carries the first information.

[0473] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. It is understood that the functions or implementations of each module in the embodiments of the present application may further refer to the relevant description of the method embodiment.

[0474] In one possible approach, the communication device may be as follows Fig.14 As shown, the device can be a communication device or a chip in a communication device, wherein the communication device can be a terminal device in the above embodiment or a network device in the above embodiment. The device includes a processor 801 and a communication interface 802, and can also include a memory 803. Among them, the processing unit 702 can be the processor 801. The communication unit 701 can be the communication interface 802. Optionally, the processor 801 and the memory 803 can also be integrated together.

[0475] The processor 801 may be a CPU, or a digital processing unit, etc. The communication interface 802 may be a transceiver, or an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device further includes: a memory 803 for storing programs executed by the processor 801. The memory 803 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory 803 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0476] The processor 801 is used to execute the program code stored in the memory 803, specifically to execute the actions of the processing unit 702, which will not be described in detail in this application. The communication interface 802 is specifically used to execute the actions of the communication unit 701, which will not be described in detail in this application.

[0477] The specific connection medium between the communication interface 802, the processor 801 and the memory 803 is not limited in the embodiment of the present application. Fig.14 In the embodiment, the memory 803, the processor 801 and the communication interface 802 are connected via a bus 804. Fig.14 The connections between other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.14 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0478] An embodiment of the present application also provides a computer-readable storage medium for storing computer software instructions required to be executed by the above-mentioned processor, which includes a program required to be executed by the above-mentioned processor.

[0479] The present application also provides a communication system, including a Figure 5 The communication device and the communication device for realizing the UDM network element function in the embodiment Figure 5 A communication device having the function of the first AMF network element in an embodiment.

[0480] The present application also provides a communication system, including a Figure 7 A communication device for implementing a second AMF network element function in an embodiment Figure 7 A communication device having the function of the first AMF network element in an embodiment.

[0481] The present application also provides a communication system, including a Fig. 9 A communication device for implementing a second AMF network element function in an embodiment Fig. 9 A communication device having the function of the first AMF network element in an embodiment.

[0482] The present application also provides a communication system, including a Fig.11 The communication device and the communication device for realizing the UDM network element function in the embodiment Fig.11 A communication device having the function of the first AMF network element in an embodiment.

[0483] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0484] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0485] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0486] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0487] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.< / mnc> < / mcc> < / guami> < / guami>

Claims

1. A network registration method, characterized in that: include: receiving a first message, wherein the first message is used to request the first terminal to register with a non-third generation partnership project 3GPP access side through a first mobility management function network element; Determining that the first mobility management function network element and a second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same public land mobile network PLMN; Determining that the second mobility management function network element belongs to a hosting operator HOSTING OPERATOR; Send a second message, where the second message is used to reject the first terminal from registering to the non-3GPP access side through the first mobility management function network element.

2. The method according to claim 1, characterized in that The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: According to the globally unique mobility management function identifier GUAMI of the second mobility management function network element, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR.

3. The method according to claim 2, characterized in that Determining, according to the GUAMI of the second mobility management function network element, that the second mobility management function network element belongs to a HOSTING OPERATOR includes: It is determined that the GUAMI of the second mobility management function network element belongs to a specific value range, where the specific value range is allocated by the participating operator PATRICIPATING OPERATOR for the indirect sharing area.

4. The method according to claim 1, characterized in that The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: Determine that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network.

5. The method according to claim 4, characterized in that Determining, according to the service network information registered by the first terminal in the 3GPP network, that the second mobility management function network element belongs to a HOSTING OPERATOR, includes: It is determined that the service network information registered by the first terminal in the 3GPP network is the public land mobile network PLMN information of the first operator, and the first operator is the HOSTING OPERATOR.

6. The method according to claim 1, characterized in that The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: Receive a third message, where the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, and the third message carries first information, where the first information indicates that the second mobility management function network element belongs to the HOSTING OPERATOR, or the first information indicates that the second mobility management function network element is located in a non-direct network sharing area.

7. The method according to any one of claims 1 to 6, characterized in that: The determining that the first mobility management function network element and a second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN includes: If the PLMN information carried by the GUAMI of the second mobility management function network element is the same as the PLMN information carried by the GUAMI of the first mobility management function network element, it is determined that the first mobility management function network element and the second mobility management function network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

8. The method according to any one of claims 1 to 7, characterized in that: Before sending the second message, the method further includes: Determining that the first mobility management function network element and the second mobility management function network element are from a home PLMN; Alternatively, it is determined that the first mobility management function network element and the second mobility management function network element are from an equivalent home PLMN.

9. The method according to any one of claims 1 to 8, characterized in that Before sending the second message, the method further includes: It is determined that the home network of the first terminal supports indirect network sharing.

10. The method according to any one of claims 1 to 9, characterized in that: The second message carries a first cause value, where the first cause value is used to indicate that the first terminal is not allowed to register with the first mobility management function network element and the second mobility management function network element at the same time.

11. A network registration method, characterized in that: include: receiving a first message, wherein the first message is used to request that a first mobility management function network element registered by the first terminal in a non-third generation partnership project 3GPP access side be updated to a second mobility management function network element; Determining that the second mobility management function network element belongs to a hosting operator HOSTING OPERATOR; Sending first information, where the first information is used to instruct the non-3GPP access side to delete the context information of the first terminal.

12. The method according to claim 11, characterized in that The first mobility management function network element and the second mobility management function network element are located in the same PLMN.

13. The method according to claim 11 or 12, characterized in that: The sending of the first information includes: A second message is sent, where the second message instructs the first mobility management function network element to deregister, and the second message carries the first information.

14. The method according to any one of claims 11 to 13, characterized in that: The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: According to the globally unique mobility management function identifier GUAMI of the second mobility management function network element, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR.

15. The method according to claim 14, characterized in that Determining, according to the GUAMI of the second mobility management function network element, that the second mobility management function network element belongs to a HOSTING OPERATOR includes: It is determined that the GUAMI of the second mobility management function network element belongs to a specific value range, where the specific value range is allocated by the participating operator PATRICIPATING OPERATOR for the indirect sharing area.

16. The method according to any one of claims 11 to 13, characterized in that: The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: Determine that the second mobility management function network element belongs to the HOSTING OPERATOR based on the service network information registered by the first terminal in the 3GPP network.

17. The method according to claim 16, characterized in that Determining, according to the service network information registered by the first terminal in the 3GPP network, that the second mobility management function network element belongs to a HOSTING OPERATOR, includes: It is determined that the service network information registered by the first terminal in the 3GPP network is the public land mobile network PLMN information of the first operator, and the first operator is the HOSTING OPERATOR.

18. The method according to any one of claims 11 to 13, characterized in that: The determining that the second mobility management function network element belongs to a HOSTING OPERATOR includes: Receive a third message, where the third message is used to request the first terminal to register to the 3GPP network through the second mobility management function network element, and the third message carries second information, where the second information indicates that the second mobility management function network element belongs to the HOSTING OPERATOR, or the second information indicates that the second mobility management function network element is located in a non-direct network sharing area.

19. A network registration method, characterized in that: include: receiving first information, where the first information is used to instruct a non-3rd Generation Partnership Project 3GPP access side to delete context information of a first terminal; Sending third information, where the third information is used to instruct the non-3GPP interworking function network element to delete the context information of the first terminal.

20. The method of claim 19, wherein: Before sending the third information, the method further includes: Determine that context information of the first terminal exists on a non-3GPP interworking function network element.

21. The method according to claim 19 or 20, characterized in that The receiving of the first information comprises: A second message is received, where the second message instructs the first mobility management function network element to deregister, and the second message carries the first information.

22. A communication device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program instructions, and when the processor executes the program instructions, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 18 is executed.

23. A communication device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program instructions, and when the processor executes the program instructions, the method according to any one of claims 19 to 21 is executed.

24. A computer-readable storage medium, characterized in that: The computer storage medium stores computer-readable instructions, and when the computer-readable instructions are executed on the communication device, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 18 is executed, or the method according to any one of claims 19 to 21 is executed.

25. A computer program product, characterized in that When the computer program product runs on a device, the device is enabled to execute the method according to any one of claims 1 to 10, the method according to any one of claims 11 to 18, or the method according to any one of claims 19 to 21.

26. A communication device, characterized in that: The method comprises a unit or module for executing the method according to any one of claims 1 to 10, or comprises a unit or module for executing the method according to any one of claims 11 to 18.

27. A communication device, characterized in that: The method comprises a unit or a module for executing the method according to any one of claims 19 to 21.

28. A chip, characterized in that: The chip is coupled to the memory and is used to read and execute program instructions stored in the memory to implement the method as claimed in any one of claims 1 to 10, or to implement the method as claimed in any one of claims 11 to 18.

29. A chip, characterized in that: The chip is coupled to a memory and is used to read and execute program instructions stored in the memory to implement the method as described in any one of claims 19-21.

Images