Network registration method and apparatus

Abstract

Provided in the present application are a network registration method and apparatus, which are used for solving the problem of a communication abnormality when a terminal device performs registration in a 3GPP network and on a non-3GPP access side in an INS scenario. In the present application, for a scenario in which a first terminal performs registration in a 3GPP network and then performs registration on a non-3GPP access side, the registration of the first terminal on the non-3GPP access side is rejected or delayed, so that a single AMF is responsible for mobility registration of the first terminal, which meets protocol requirements, and can also avoid a problem caused by two AMFs being simultaneously responsible for mobility registration of the first terminal due to it being impossible to switch 3GPP registration of the first terminal to an AMF selected for non-3GPP registration.

Description

A network registration method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510051702.0, filed on January 13, 2025, entitled "A Method and Apparatus for Online Registration", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a network registration method and apparatus. Background Technology

[0004] Wireless access network (WLAN) sharing refers to different mobile network operators sharing the WLAN's wireless access network, allowing them to share the construction costs. Additionally, in areas where operators lack their own WLANs, sharing WLANs allows them to utilize other operators' WLANs, thus supplementing their network coverage in those areas.

[0005] A proposed indirect network sharing (INS) model involves two types of operators: hosting operators and participating operators. Hosting operators are those that interface with the radio access network and directly exchange signaling signals; they provide the radio access network. Participating operators are those that use the radio access network provided by the hosting operator but do not interface with it. The radio access network broadcasts its own public land mobile network (PLMN) number (i.e., the hosting operator's PLMN number) and the participating operator's PLMN number over the air interface. Terminals can choose either the hosting operator's PLMN or the participating operator's PLMN as their access PLMN. 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 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.

[0006] Terminals can register on both the 3rd Generation Partnership Project (3GPP) network (over-the-air registration) and non-3GPP access networks (e.g., Wi-Fi). When a terminal registered with a PATICIPATING OPERATOR registers on the non-3GPP access side, it selects a non-3GPP access gateway belonging to that PATICIPATING OPERATOR. However, when registering on the 3GPP network, the AMF (Active Mobile Provider) belonging to the HOSTING OPERATOR manages the terminal's mobility registration. But because there is no interface between the PATICIPATING OPERATOR's non-3GPP access gateway and the HOSTING OPERATOR's AMF, terminals may access the same PLMN but select different AMFs, leading to communication anomalies. Summary of the Invention

[0007] This application provides a network registration method and apparatus to solve the problem of communication anomalies when terminal devices register in INS scenarios on 3GPP networks and non-3GPP access networks.

[0008] Firstly, a network registration method is provided. The executing entity of this method can be a unified data management network element or a chip, chip system, or circuit used in the unified data management network element. This method can be implemented through the following steps: receiving a first message, which requests a first terminal to register with a non-3GPP access side through a first mobility management function network element. If 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, and the non-3GPP access network element and the second mobility management function network element cannot interconnect, a second message is sent, which rejects the first terminal's registration with the non-3GPP access side through the first mobility management function network element.

[0009] This application addresses scenarios where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or postponing the first terminal's registration on the non-3GPP access side, it enables a single mobility management function (MMU) network element to handle the first terminal's mobility registration within the same PLMN. This complies with protocol requirements and avoids problems caused by having two MMU network elements handling the first terminal's mobility registration simultaneously within the same PLMN, such as the first terminal being unable to receive mobile terminated (MT) data packets.

[0010] In one possible design, the first message is a registration request message. The second message is a registration response message.

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

[0012] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: determining that the second MMU network element belongs to the HOSTING OPERATOR based on its GUAMI. This design helps avoid the problem caused by the first terminal's inability to switch from 3GPP registration to a non-3GPP registered mobility management function network element.

[0013] In one possible design, determining whether a second mobility management function (MMS) network element belongs to a hosting operator based on its GUAMI includes: determining that the GUAMI of the second MMS network element belongs to a specific value range, where the specific value range is assigned by the hosting operator to a non-directly shared area. This design can improve the accuracy of the determination.

[0014] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: determining that the second MMU network element belongs to the HOSTING OPERATOR based on the serving network information registered by the first terminal in the 3GPP network. This design helps avoid the problem caused by the first terminal's inability to switch from 3GPP registration to a non-3GPP registered MMU network element.

[0015] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the serving network information registered by the first terminal in the 3GPP network includes: determining that the serving network information registered by the first terminal in the 3GPP network is the Public Land Mobile Network (PLMN) information of the first operator, and that the first operator is the HOSTING OPERATOR. This design can improve the accuracy of the determination.

[0016] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: receiving a third message, the third message being used to request the first terminal to register with the 3GPP network through the second MMU network element, the third message carrying first information, wherein the first information indicates that the second MMU network element belongs to the HOSTING OPERATOR, or, the first information indicates that the second MMU network element is located in a non-directly shared network area. This design, by using explicit indication, can reduce processing overhead.

[0017] In one possible design, determining that the first mobility management function (MMU) network element and the second mobility management function (MMU) 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 (MMU) network element is the same as the PLMN information carried by the GUAMI of the first mobility management function (MMU) network element, then determining that the first mobility management function (MMU) network element and the second mobility management function (MMU) network element corresponding to the first terminal in the 3GPP network are in the same PLMN.

[0018] In one possible design, before sending the second message, the method further includes: determining that the first mobility management function (MMU) element and the second MMU element originate from a home PLMN; or, determining that the first MMU element and the second MMU element originate from an equivalent home PLMN. This design is beneficial for terminal communication in INS scenarios.

[0019] In one possible design, before sending the second message, the method further includes determining whether the home network of the first terminal supports indirect network sharing. This design helps to reduce the processing overhead of the unified data management network element.

[0020] In one possible design, the second message carries a first reason value, which indicates that the first terminal is not allowed to simultaneously register with both the first mobility management function (MMU) element and the second MMU element. This design is beneficial for network management.

[0021] Secondly, a network registration method is provided. The execution entity of this method can be a mobility management function (MMU) network element or a chip, chip system, or circuit used in the MMU network element. This method can be implemented through the following steps: sending a first message, which requests a first terminal to register with a non-3GPP access side through a first MMU network element; receiving a second message, which rejects the first terminal's registration with a non-3GPP access side through the first MMU network element, the second message carrying a first reason value, which indicates that the first terminal is not allowed to register with both the first and second MMU network elements simultaneously; and sending a fourth message, which indicates that the first terminal cannot register with a non-3GPP network element in the current area, or that the fourth message indicates that the first terminal should postpone its registration with a non-3GPP network element.

[0022] This application addresses scenarios where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or postponing the first terminal's registration on the non-3GPP access side, it enables a single mobility management function (MMU) network element to handle the first terminal's mobility registration within the same PLMN. This complies with protocol requirements and avoids problems caused by having two MMU network elements handling the first terminal's mobility registration simultaneously within the same PLMN, such as the first terminal being unable to receive mobile terminated (MT) data packets.

[0023] Furthermore, sending a reason value to a non-3GPP registered mobility management function network element to indicate the reason for the rejection facilitates network management.

[0024] In one possible design, the fourth message instructs the first terminal to postpone its registration with non-3GPP services. This design is advantageous for the first terminal's communication on non-3GPP access sides.

[0025] Thirdly, a network registration method is provided. The execution subject of this method can be a unified data management network element or a chip, chip system, or circuit used for the unified data management network element. This method can be implemented through the following steps: receiving a first message, the first message being 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 a second mobility management function network element; and, if it is determined that the non-3GPP access network element and the second mobility management function network element cannot be interconnected, sending first information, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0026] This application addresses the scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The unified data management network element instructs the non-3GPP access side to delete the first terminal's context information, thereby promptly releasing the first terminal's context information in the non-3GPP interoperability network element and saving resources. Furthermore, by promptly releasing the first terminal's context information in the non-3GPP interoperability network element, the first terminal can be promptly released to an idle state on the non-3GPP access side, thus preventing communication anomalies on the non-3GPP access side.

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

[0028] 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.

[0029] In one possible design, sending the first information includes sending a second message, which instructs the first mobility management function (MLM) network element to register. The second message carries the first information. This design allows for the timely release of the context information of the first terminal on the non-3GPP access side.

[0030] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: determining that the second MMU network element belongs to the HOSTING OPERATOR based on its GUAMI. This design helps avoid the problem caused by the first terminal's inability to switch from 3GPP registration to a non-3GPP registered mobility management function network element.

[0031] In one possible design, determining whether a second mobility management function (MMS) network element belongs to a hosting operator based on its GUAMI includes: determining that the GUAMI of the second MMS network element belongs to a specific value range, where the specific value range is assigned by the hosting operator to a non-directly shared area. This design can improve the accuracy of the determination.

[0032] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: determining that the second MMU network element belongs to the HOSTING OPERATOR based on the serving network information registered by the first terminal in the 3GPP network. This design helps avoid the problem caused by the first terminal's inability to switch from 3GPP registration to a non-3GPP registered MMU network element.

[0033] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR based on the serving network information registered by the first terminal in the 3GPP network includes: determining that the serving network information registered by the first terminal in the 3GPP network is the Public Land Mobile Network (PLMN) information of the first operator, and that the first operator is the HOSTING OPERATOR. This design can improve the accuracy of the determination.

[0034] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: receiving a third message, which requests the first terminal to register with the 3GPP network through the second MMU network element. The third message carries second information, wherein the second information indicates that the second MMU network element belongs to the HOSTING OPERATOR, or that the second MMU network element is located in a non-directly shared network area. This design, by using explicit indication, can reduce processing overhead.

[0035] Fourthly, a network registration method is provided. The execution subject of this method can be a mobility management function network element or a chip, chip system, or circuit used for a mobility management function network element. This method can be implemented through the following steps: receiving first information, the first information being used to instruct a non-3GPP access side to delete the context information of a first terminal; and sending third information, the third information being used to instruct a non-3GPP interoperability function network element to delete the context information of the first terminal.

[0036] This application addresses the scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. By having a unified data management network element instruct the non-3GPP access side to delete the first terminal's context information, the application promptly releases the first terminal's context information from the non-3GPP interoperability network element, thus saving resources. Furthermore, by promptly releasing the first terminal's context information from the non-3GPP interoperability network element, the first terminal can be promptly released to an idle state on the non-3GPP access side, thereby preventing communication anomalies on the non-3GPP access side.

[0037] In one possible design, before sending the third information, the method further includes determining the context information of the presence of the first terminal on a non-3GPP interoperability network element. This design can save signaling overhead.

[0038] In one possible design, receiving the first information includes receiving a second message, which instructs a first mobility management function (MLM) network element to register. The second message carries the first information. This design allows for the timely release of context information from the first terminal on the non-3GPP access side.

[0039] Fifthly, a network registration method is provided. The execution entity of this method may be a mobility management function (MMU) network element or a chip, chip system, or circuit used for the MMU network element. This method can be implemented through the following steps: receiving a first message, the first message being used to request a first terminal to register with the non-3GPP access side of a first PLMN through a first MMU network element; determining that the first terminal has already registered with the 3GPP network of the first PLMN through a second MMU network element; determining that the non-3GPP access network element and the second MMU network element cannot interconnect; sending a second message, the second message being used to indicate that the first terminal cannot register in the non-3GPP area in the current area, or, the second message instructing the first terminal to postpone registration in the non-3GPP area.

[0040] This application addresses scenarios where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or postponing the first terminal's registration on the non-3GPP access side, it enables a single mobility management function (MMU) network element to handle the first terminal's mobility registration, which complies with protocol requirements. It also avoids problems caused by two MMU network elements simultaneously handling the first terminal's mobility registration in the same PLMN, such as the first terminal being unable to receive MT data packets.

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

[0042] In one possible design, the first message carries the GUTI allocated to the first terminal by the second mobility management function network element 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 that the first terminal has registered with the 3GPP network of the first PLMN through the second mobility management function network element based on the GUTI.

[0043] In one possible design, determining that the second mobility management function (MMU) network element belongs to the HOSTING OPERATOR includes: determining that the second MMU network element belongs to the HOSTING OPERATOR based on its GUAMI. This design helps avoid the problem caused by the first terminal's inability to switch from 3GPP registration to a non-3GPP registered mobility management function network element.

[0044] In one possible design, determining whether a second mobility management function (MMS) network element belongs to a hosting operator based on its GUAMI includes: determining that the GUAMI of the second MMS network element belongs to a specific value range, where the specific value range is assigned by the hosting operator to a non-directly shared area. This design can improve the accuracy of the determination.

[0045] In one possible design, determining that the second mobility management function network element belongs to the HOSTING OPERATOR includes: receiving first information indicating that the second mobility management function network element belongs to the HOSTING OPERATOR. This design reduces processing complexity.

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

[0047] In one possible design, before sending the second message, the method further includes determining whether the home network of the first terminal supports indirect network sharing. This design helps to reduce processing overhead.

[0048] In one possible design, the second message instructs the first terminal to postpone its registration time on a non-3GPP access side. This design is advantageous for the first terminal's communication on non-3GPP access sides.

[0049] Sixthly, a network registration method is provided. The execution subject of this method may be a mobility management function network element or a chip, chip system, or circuit used for a mobility management function network element. This method can be implemented through the following steps: receiving a third message, the third message being used to request the migration of the context information of a first terminal to a first mobility management function network element; sending a fourth message, the fourth message carrying the context information of the first terminal and first information, the first information being used to indicate that a second mobility management function network element belongs to a HOSTING OPERATOR.

[0050] This application addresses the scenario where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By having a second mobility management function (MMU) network element indicate to the first MMU network element that the second MMU network element is a HOSTING OPERATOR, it facilitates rejecting or delaying the first terminal's registration on the non-3GPP access side. This allows a single MMU network element to handle the first terminal's mobility registration, complying with protocol requirements. Furthermore, it avoids problems arising from having two MMU network elements simultaneously handling the first terminal's mobility registration within the same PLMN, such as the first terminal being unable to receive MT data packets.

[0051] In a seventh aspect, a network registration method is provided. The execution entity of this method may be a mobility management function (MMU) network element or a chip, chip system, or circuit used for the MMU network element. The method can be implemented through the following steps: receiving a first message, the first message being used to request a first terminal to register with a 3GPP network through a second MMU network element, the first message carrying a GUTI allocated to the first terminal by the first MMU network element when the first terminal registers with a non-3GPP access side; determining the first MMU network element based on the GUTI; if the non-3GPP access network element and the second MMU network element cannot interconnect, sending first information to the first MMU network element, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0052] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The mobility management function (MMS) network element on the non-3GPP access side receives an instruction to delete the first terminal's context information, thereby promptly releasing the first terminal's context information from the non-3GPP interoperability network element and conserving its resources. Furthermore, by promptly releasing the first terminal's context information from the non-3GPP interoperability network element, the first terminal can be promptly released to an idle state, thus preventing communication anomalies on the non-3GPP access side.

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

[0054] 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, the second message carrying the first information.

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

[0056] 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 instructs the first terminal to register in the 3GPP network, or the first information instructs the deletion of the context information of the first terminal in the non-3GPP access side.

[0057] 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. This design helps reduce processing overhead.

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

[0059] Eighthly, a network registration method is provided. The execution entity of the method may be a mobility management function network element or a chip, chip system, or circuit used in a mobility management function network element. The method can be implemented through the following steps: receiving a second message, the second message being used to request the migration of the context of a first terminal to a second mobility management function network element; determining to delete the context information of the first terminal in a non-3GPP interoperability network element; and sending a second message to the non-3GPP interoperability network element, the second message being used to instruct the non-3GPP interoperability network element to delete the context information of the first terminal.

[0060] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The mobility management function (MMS) network element on the non-3GPP access side instructs the non-3GPP access side to delete the first terminal's context information. This promptly releases the first terminal's context information from the non-3GPP interoperability network element, thus saving resources. Furthermore, by promptly releasing the first terminal's context information from the non-3GPP interoperability network element, the first terminal can be promptly released to an idle state on the non-3GPP access side, thereby preventing communication anomalies on the non-3GPP access side.

[0061] In one possible design, determining the context information of a first terminal in a non-3GPP interoperability network element to delete the context information of the first terminal 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.

[0062] In one possible design, receiving the first information includes: a second message carrying the first information, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0063] 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, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal.

[0064] 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 instructs the first terminal to register in the 3GPP network, or the first information instructs the deletion of the context information of the first terminal in the non-3GPP access side.

[0065] In one possible design, determining the context information of the first terminal in the non-3GPP interoperability function network element to be deleted includes: determining that the non-3GPP access network element and the second mobility management function network element cannot interconnect.

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

[0067] 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 GUAMI of the second mobility management function network element.

[0068] 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, which is allocated by the PARTICIPATING OPERATOR for non-directly shared areas.

[0069] Ninthly, this application also provides a communication device, which is a unified data management network element or a chip within a unified data management network element. This communication device has the function of implementing any of the methods provided in the first or third aspect above. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0070] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the terminal device described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as mobility management function network elements, for example, the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

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

[0072] In one possible design, the communication device includes a processing unit (or processing module) and a communication unit (or communication module). These units can perform the corresponding functions in the above method examples, as described in the methods provided in the first or third aspects, and will not be repeated here.

[0073] Tenthly, this application also provides a communication device, which is a mobility management function (MMU) network element or a chip within a MMU network element. This communication device has the function of implementing any of the methods provided in any of the second, fourth to eighth aspects described above. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the aforementioned functions.

[0074] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the network device described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as unified data management network elements and access network equipment, for example, the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

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

[0076] In one possible design, the communication device includes a processing unit (or processing module) and a communication unit (or communication module). These units can perform the corresponding functions in the above method examples, as described in the methods provided in any of the second, fourth to eighth aspects, which will not be repeated here.

[0077] Eleventhly, a communication device is provided, including a processor and an interface circuit. The interface circuit is 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 is used to implement the methods of the first or third aspect and any possible design through logic circuits or execution code instructions.

[0078] In a twelfth aspect, a communication device is provided, including a processor and an interface circuit. The interface circuit is configured 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 is configured to implement any one of the aforementioned second, fourth to eighth aspects and any possible design methods through logic circuits or execution code instructions.

[0079] In a thirteenth aspect, a computer-readable storage medium is provided that stores a computer program or instructions which, when executed by a processor, implement the methods of any of the first to eighth aspects and any possible designs described above.

[0080] In a fourteenth aspect, a computer program product storing instructions is provided, which, when executed by a processor, implements any of the first to eighth aspects and any possible design methods described above.

[0081] In a fifteenth aspect, a chip system is provided, comprising a processor and potentially a memory, for implementing the methods of any of the first to eighth aspects and any possible designs described above. The chip system may be composed of chips or may include chips and other discrete devices.

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

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

[0084] Eighteenth aspect, a communication system is provided, the system comprising the apparatus of the fifth aspect (such as a first mobility management function network element) and the apparatus of the sixth aspect (such as a second mobility management function network element).

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

[0086] The technical effects that can be achieved by any of the technical solutions in aspects nine through nineteen above can be described with reference to the technical effects that can be achieved by the technical solution in aspect one above, and the repeated parts will not be repeated. Attached Figure Description

[0087] Figure 1 is a schematic diagram of a GUTI provided in an embodiment of this application;

[0088] Figure 2 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0089] Figure 3 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0090] Figure 4 is a schematic diagram of an indirect network sharing provided in an embodiment of this application;

[0091] Figure 5 is a flowchart illustrating a network registration method provided in an embodiment of this application;

[0092] Figure 6 is a schematic diagram of a network registration process provided in an embodiment of this application;

[0093] Figure 7 is a flowchart illustrating a network registration method provided in an embodiment of this application;

[0094] Figure 8 is a schematic diagram of a network registration process provided in an embodiment of this application;

[0095] Figure 9 is a flowchart illustrating a network registration method provided in an embodiment of this application;

[0096] Figure 10 is a schematic diagram of a network registration process provided in an embodiment of this application;

[0097] Figure 11 is a flowchart illustrating a network registration method provided in an embodiment of this application;

[0098] Figure 12 is a schematic diagram of a network registration process provided in an embodiment of this application;

[0099] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0100] Figure 14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0101] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0102] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0103] I. 5G Globally Unique Temporary UE Identity (5G-GUTI)

[0104] The 5G-GUTI serves as a temporary identifier for the terminal in 5G, uniquely assigned by the AMF. Like other temporary IDs, it has a validity period and a corresponding valid registration area. When the validity period expires, the terminal needs to initiate a network update request, i.e., request the network to reassign the 5G-GUTI. Alternatively, when the terminal moves to a different registration area, i.e., moves out of the current valid registration area (e.g., between different AMFs), a new temporary identifier will be assigned, as shown in Figure 1. Its structure is as follows:

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

[0106] 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 whether the terminal previously used the AMF based on GUAMI: whether it is itself or someone else.

[0107] GUAMI also consists of two parts: the Public Land Mobile Network (PLMN) and the AMF Identifier. The PLMN consists of the Mobile Country Code (MCC) and the Mobile Network Code (MNC). The AMF Identifier consists of three parts: the AMF Region ID (ARI), the AMF Set ID (ASI), and the AMF Pointer (AP).

[0108] II. PLMN

[0109] In daily life, mobile operators providing network services to terminals typically use PLMNs for identification. A PLMN is a network established and operated by a government or its approved operators for the purpose of providing terrestrial mobile communication services to the public. Different PLMN networks can be distinguished using different PLMN identifications (IDs). A PLMN identification consists of a mobile country code (MCC) and a mobile net code (MNC). The MCC uniquely indicates the mobile user's country of origin; for example, China's MCC is 460. The MNC uniquely indicates the network within that country; for example, China Mobile's MNC is 00, and China Unicom's MNC is 01.

[0110] When a terminal accesses an access network device, it needs to select a network; this network selection process is called PLMN selection. PLMN selection can be performed as follows:

[0111] In step A1, the terminal's access stratum (AS) scans all new radio (NR) bands and radio frequency (RF) channels to discover available PLMNs. The terminal then identifies the cell with the best reference signal received power (RSRP) for each frequency point and reads the cell's system information block 1 (SIB1) to obtain the PLMN ID.

[0112] A2, the terminal's AS reports the PLMN list to the terminal's non-access stratum (NAS). The PLMN list includes the PLMN IDs obtained by the terminal's AS.

[0113] 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.

[0114] When a terminal selects a PLMN, the PLMN it searches for can be: a registered PLMN (RPLMN), which is a PLMN that the terminal registered before it was powered off or disconnected from the network; an equivalent PLMN (EPLMN), which is a PLMN with the same priority as the PLMN currently selected by the terminal; a home PLMN (HPLMN), whose identifier is stored in the subscriber identity module (SIM) card, and each SIM card has only one HPLMN; or an equivalent HPLMN (EHPLMN), which is a PLMN with the same priority as the HPLMN.

[0115] A4. After selecting a PLMN ID, the terminal's NAS can provide the terminal's AS with an EPLMN list and forbidden tracking areas (forbidden TAs) based on the selected PLMN ID. The terminal's AS can then perform cell selection and reselection based on the EPLMN list and the forbidden TAs.

[0116] For a single terminal, it is typically necessary to maintain several different types of PLMN lists, and each list can contain multiple PLMNs.

[0117] (1) RPLMN (Registered PLMN): The PLMN that has been registered. This is the PLMN that the terminal registered before it was last powered off or disconnected from the network. This parameter is stored in the terminal's memory.

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

[0119] (3) EHPLMN (Equivalent Home PLMN): A PLMN that is on par with the terminal HPLMN.

[0120] (4) HPLMN (Home PLMN): The PLMN to which the terminal user is located. That is to say, 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 they are located.

[0121] (5) VPLMN (Visited PLMN): This is the visited PLMN accessed by the end user when roaming. Its PLMN is not completely the same as the MCC and MNC of the IMSI stored in the SIM card, that is, the user is roaming.

[0122] III. Hosting Operator

[0123] A hosting operator is an operator that has an interface with the radio access network and directly engages in signaling interaction; that is, an operator that provides the radio access network.

[0124] IV. Participating Operators

[0125] A PARTICAPTING OPERATOR is a wireless access network that uses a HOSTING OPERATOR, but is not an interface with the wireless access network.

[0126] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

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

[0128] It should be noted that in this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

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

[0130] The preceding text introduced some of the terms used in the embodiments of this application. The following text describes the architecture of the network system to which the method provided in this application is applied.

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

[0132] Figure 2 shows a schematic diagram of a fifth-generation (5G) network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 2 can include three parts: the UE (User Equipment) part, the data network (DN), and the operator network part. The functions of some of these network elements are briefly described below.

[0133] The operator network may include, but is not limited to, one or more of the following network elements: network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, network exposure function (NEF) network elements, network repository function (NRF) network elements, access and mobility management function (AMF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, session management function (SMF) network elements, access network (AN) or radio access network (RAN), and user plane function (UPF) network elements. The portion of the operator network excluding the radio access network portion can be referred to as the core network portion. In one possible implementation, the operator network may also include application function (AF) network elements.

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

[0135] The aforementioned terminals can establish connections with the operator's network through interfaces provided by the operator's network (such as N1), and use data and / or voice services provided by the operator's network. The terminals can also access the DN (Network Provider) through the operator's network, and use operator services deployed on the DN, and / or services provided by third parties. These third parties can be service providers outside of the operator's network and the terminal, and can provide the terminal with other data and / or voice services. The specific form of these third parties can be determined based on the actual application scenario and is not limited here.

[0136] RAN (Radio Access Network) is the radio access network of a carrier network, serving as a bridging system between service nodes and terminals within the carrier network. For a terminal to access the carrier network, it first passes through the RAN, and then connects to service nodes in the carrier network via the RAN. RAN equipment is a device that provides wireless communication capabilities to terminals; RAN equipment is also known as access network equipment. RAN equipment includes, but is not limited to: next-generation base stations (g node B, gNB) in 5G, evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.

[0137] The AMF (Access and Mobility Management) network element primarily performs functions such as mobility management and access authentication / authorization. Additionally, it is responsible for transmitting user policies between the UE and the PCF (Programmable Component Function). In future communications, the access and mobility management function network element may still be an AMF network element, or may have other names; this application does not impose any limitations.

[0138] The SMF network element primarily performs functions such as session management, execution of control policies issued by the PCF, selection of the UPF, and allocation of Internet Protocol (IP) addresses to the UE. In future communications, the session management function network element may still be an SMF network element, or may have other names; this application does not impose any restrictions.

[0139] UPF network elements, serving as interfaces with the data network, perform functions such as user plane data forwarding, session / flow-based billing and statistics, and bandwidth limiting. In future communications, user plane function network elements may still be UPF network elements or have other names; this application does not impose any restrictions.

[0140] UDM network elements are primarily responsible for managing subscription data and user access authorization. In future communications, user plane function network elements may still be UDM network elements, or may have other names; this application does not impose any restrictions.

[0141] The NSSF network element is primarily responsible for managing information related to network slicing.

[0142] NEF network elements are primarily used to support the opening of capabilities and events.

[0143] AF (Application Provider) network elements primarily convey application-side requests to the network side, such as Quality of Service (QoS) requirements or user state event subscriptions. AF can be a third-party functional entity or an application service deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service.

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

[0145] NRF network elements can be used to provide network element discovery functionality, providing 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, updates, deregistration, and network element status subscription and push.

[0146] AUSF network element: mainly responsible for authenticating users to determine whether to allow users or devices to access the network.

[0147] A Domain Provider (DN) is a network located outside of the carrier's network. A carrier's network can connect to multiple DNs, and various services can be deployed on a DN, providing data and / or voice services to terminals. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminals, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminals, accessing information and data resources within the company's internal office network.

[0148] In Figure 2, Nnssf, Nausf, Nnef, Nnrf, NAMF network elements, Npcf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and are not limited here.

[0149] 5GC supports access to non-3GPP networks. Terminals can access 5GC through non-3GPP access gateways such as the non-3GPP interworking function (N3IWF) and the next-generation packet data gateway (ngPDG). Taking the N3IWF as an example of a non-3GPP access gateway, its 5G network architecture is shown in Figure 3. In Figure 3, the access network includes the 3GPP access network and the non-3GPP access network. Access devices in the 3GPP access network can be called radio access network (RAN) devices. 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 N3IWF devices can include, for example, routers.

[0150] The functions of the network elements shown in Figure 3 can be found in the descriptions of the corresponding network elements in Figure 2, and will not be repeated here. The main difference between Figure 3 and Figure 2 is that the interfaces between the network elements in Figure 3 are point-to-point interfaces, while the interfaces between the network elements in Figure 2 are service-oriented interfaces.

[0151] In Figure 3, N1, N2, N3, N4, N6, N11, NWu, Y1, and Y2 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and are not limited here.

[0152] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0153] The technical background involved in the embodiments of this application is described below.

[0154] Wireless access network (WLAN) sharing refers to different mobile network operators sharing the WLAN's wireless access network, allowing them to share the construction costs. Additionally, in areas where operators lack their own WLANs, sharing WLANs allows them to utilize other operators' WLANs, thus supplementing their network coverage in those areas.

[0155] A proposed indirect network sharing (INS) mode involves two types of operators: hosting operators and participating operators. As shown in Figure 4, the radio access network broadcasts its own public land mobile network (PLMN) number (i.e., the hosting operator's PLMN number) and the participating operator's PLMN number over the air interface. Terminals can choose either the hosting operator's PLMN or the participating operator's PLMN as their access PLMN.

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

[0157] In an INS scenario, the shared RAN can broadcast an HPLMN ID, an EHPLMN ID, or other PLMN IDs according to the protocol between operators. When the broadcast PLMN ID is an HPLMN or an EHPLMN, the terminal can register on the 3GPP network (i.e., the NR air interface) and on the non-3GPP access side (e.g., mobile hotspot (Wi-Fi)). If the terminal is a subscriber to a PARTICIPATING OPERATOR, two scenarios, A and B, will occur:

[0158] Scenario A, 3GPP registration first: When the terminal device accesses the 3GPP network, it selects either the HPLMN or EHPLMN ID based on the PLMN ID number broadcast over the air interface and initiates registration to the HPLMN / EHPLMN network. At this time, the NG-RAN of the shared area selects the AMF (assumed to be AMF1) of the HOSTING OPERATOR PLMN. After successful registration, AMF1 assigns a GUTI to the terminal, which will contain the selected PLMN information, i.e., HPLMN or EHPLMN information. When this terminal subsequently chooses to 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 point, two scenarios, A-1 and A-2, may occur:

[0159] A-1, the N3IWF is located within the HOSTING OPERATOR PLMN area, but it belongs to the HPLMN / EHPLMN operator, i.e., the PARTICAPTING OPERATOR. Normally, there is no interface between the PARTICAPTING OPERATOR's N3IWF and the HOSTING OPERATOR's AMF. Therefore, when a terminal registers on the non-3GPP access side, the N3IWF will reselect an AMF from the PARTICAPTING OPERATOR (let's assume AMF2) for the terminal. The registration message will then be processed by AMF2.

[0160] A-2, N3IWF is located within the Participation G PLMN area. N3IWF belongs to the HPLMN / EHPLMN operator, i.e., the Participating Operator. At this time, N3IWF has an interface with the AMF of its home network (i.e., the Participating Operator), but no interface with the AMF of the Hosting Operator. Consequently, the GUTI previously assigned after successful registration on the 3GPP network will not be able to find the same AMF on the non-3GPP access side (because the GUTI belongs to the AMF within the Hosting Operator's area). Therefore, N3IWF will reselect an AMF (let's assume AMF2). The registration message will then be processed by AMF2.

[0161] The above processing method results in two registered AMF network elements within the same PLMN (HPLMN / EHPLMN) scenario, namely AMF1 / AMF2 responsible for managing terminal mobility registration. However, the current protocol stipulates that within the same PLMN, after a terminal registers on a 3GPP network or a non-3GPP network, except in very rare special scenarios (such as the brief period after a user moves from an Evolved Packet System (EPS) network to a 5G system (5GS) network and registers across radio access technologies (RATs), it can only use the same AMF. Therefore, the aforementioned behavior of terminal devices registering on both the 3GPP network and the non-3GPP access side in the INS scenario does not comply with the protocol. This will also lead to other problems, such as the inability to forward mobile terminated (MT) data when the terminal is in a non-3GPP idle state.

[0162] Scenario B, Non-3GPP Registration First: Assuming the terminal has already registered on the non-3GPP access side, the N3IWF of the HPLMN / EHPLMN operator will select the AMF (assumed to be AMF2) of the PARTICAPTING OPERATOR. Subsequently, it registers on the 3GPP network. Since the 3GPP network uses a shared RAN, the NG-RAN of the shared area selects the AMF (assumed to be AMF1) of the HOSTING OPERATOR PLMN during the terminal's 3GPP network registration. At this point, the AMF1 selected by the 3GPP network needs to notify the N3IWF to switch the connection from AMF2 to AMF1. However, since 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 cannot notify the N3IWF to switch the connection. Therefore, if the terminal is in a connected state in the non-3GPP network at this time and has a context, the terminal's context will be suspended on the N3IWF and cannot be released.

[0163] Based on this, embodiments of this application provide a network registration method and apparatus to solve the problem of communication anomalies when terminal devices register in INS scenarios on 3GPP networks and non-3GPP access networks. The method and apparatus are based on the same concept, and since the principles by which the method and apparatus solve the problem are similar, the implementations of the apparatus and method can be mutually referred to, and repeated details will not be elaborated further.

[0164] It should be noted that the naming of each message / information in this application is only illustrative and limits the names of each message / information.

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

[0166] Furthermore, this embodiment of the application uses N3IWF as an example of a non-3GPP access network element. In specific implementations, N3IWF can also be replaced by other non-3GPP access network elements, such as TNGF or W-AGF.

[0167] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0168] Example 1:

[0169] Figure 5 shows a flowchart of a network registration method provided in an embodiment of this application.

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

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

[0172] Optionally, prior to S501, the first terminal can register with the 3GPP network through the second AMF network element.

[0173] 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.

[0174] The first AMF network element and the second AMF network element are not the same AMF network element.

[0175] 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 the equivalent home PLMN.

[0176] 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.

[0177] For example, a UDM network element can obtain the GUAMI of the first AMF network element through a registration request from the first AMF network element (i.e., the first message mentioned above). For instance, the first message carries the GUAMI of the first AMF network element.

[0178] UDM network elements can obtain the GUAMI of the first AMF network element through a registration request from the second AMF network element (i.e., a third message used to request 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.

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

[0180] In one possible implementation, the UDM network element can determine whether 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 falls within 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 assigned by the PATRICIPATING OPERATOR for the non-directly shared area. For instance, the AMF Identifier carried by the GUAMI of the second AMF network element can be assigned by the second operator for the non-directly shared network area.

[0181] For example, the method by which the UDM network element obtains the GUAMI of the second AMF network element can be referred to the relevant description in S502 above, and will not be repeated here.

[0182] In another possible implementation, the UDM network element can 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 can determine that the second AMF network element belongs to the HOSTING OPERATOR and the first operator is the HOSTING OPERATOR.

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

[0184] In another possible implementation, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the indication information carried in the registration request of the second AMF network element (i.e., the third message mentioned above). For example, the third message carries 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.

[0185] As an optional approach, the UDM network element may execute S502 and S503 as described above if it is determined that the home network of the first terminal supports indirect network sharing.

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

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

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

[0189] Optionally, after receiving the second message, the first AMF network element can send a fourth message to the N3IWF network element. This fourth message indicates that the first terminal cannot register in a non-3GPP area, or it indicates that the first terminal should postpone its registration in a non-3GPP area. Furthermore, if the fourth message indicates that the first terminal should postpone its registration in a non-3GPP area, it can also indicate the time for the postponement.

[0190] This application addresses the scenario where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or delaying the first terminal's registration on the non-3GPP access side, it enables a single AMF network element to handle the first terminal's mobility registration, which complies with protocol requirements. It also avoids the problems caused by two AMF network elements simultaneously handling the first terminal's mobility registration on the same PLMN, as described in Scenario A above, such as the first terminal being unable to receive MT data packets.

[0191] To facilitate understanding of the scheme, the following explanation uses the example of the first operator being the HOSTING OPERATOR and the second operator being the PARTICAPTING OPERATOR to illustrate the registration process of the first terminal in the INS area.

[0192] As shown in Figure 6, the registration process of the first terminal in the INS region may include:

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

[0194] 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).

[0195] S602, the first terminal sends a registration request message 1 to the access network device.

[0196] Registration Request Message 1 is used to request registration on the 3GPP network.

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

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

[0199] Registration request message 2 is used to request the first terminal to register on the 3GPP network. Optionally, registration request message 2 may carry the HPLMN / EHPLMN selected by the first terminal, i.e., the HPLMN / EHPLMN of the second operator.

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

[0201] Registration request message 3 is used to request the first terminal to register with the 3GPP network through the second AMF network element. Registration request message 3 here is the same as the third message mentioned earlier.

[0202] Optionally, 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 on the 3GPP network is the PLMN information of the first operator.

[0203] Optionally, the aforementioned AMF Identifier may be assigned by a second operator for areas that are not directly network-shared.

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

[0205] The response message of registration request message 3 is used to confirm that the first terminal has registered with the 3GPP network through the second AMF network element.

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

[0207] The response message to registration request message 2 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message to registration request message 2 may carry the GUTI assigned to the first terminal by the second AMF network element. This 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>.

[0208] S607, the access network device sends a response message of registration request message 1 to the first terminal.

[0209] The response message to Registration Request Message 1 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message to Registration Request Message 1 may carry the GUTI assigned to the first terminal by the second AMF network element.

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

[0211] Registration request message 4 is used to request registration on a non-3GPP access side. Registration request message 4 may carry the GUTI allocated to the first terminal by the second AMF network element.

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

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

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

[0215] 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 re-selects an AMF network element belonging to the second operator (i.e., the first AMF network element) for registration.

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

[0217] Registration request message 6 is used to request the first terminal to register with a non-3GPP access side through the first AMF network element. Optionally, registration request message 6 may carry the GUAMI of the first AMF network element. The GUAMI of the first 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 first AMF network element> = <PLMN of the second operator, i.e., HPLMN / EHPLMN> <AMF Identifier of the first AMF network element>. Here, registration message 6 is the same as the first message mentioned above.

[0218] S611, the UDM network element determines whether to allow the first terminal to register on a non-3GPP access side.

[0219] Optionally, the UDM network element can determine whether to disallow the first terminal from registering on a non-3GPP access side by meeting the following two conditions:

[0220] 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.

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

[0222] For specific details, please refer to the relevant descriptions in S502 and S503 above; they will not be elaborated here.

[0223] Optionally, the UDM network element can 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 outside of 3GPP. Therefore, it is determined that the first terminal is not allowed to register on the non-3GPP access side.

[0224] Optionally, the UDM network element can also determine that the following conditions are met: 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 the equivalent home PLMN. Therefore, it is determined that the first terminal is not allowed to register on a non-3GPP access side.

[0225] In one possible implementation, the UDM network element can execute S611 if it is determined that the home network of the first terminal supports indirect network sharing.

[0226] In one possible implementation, if a terminal attempts to be served by 3GPP access via indirect network sharing, where the shared RAN broadcasts an HPLMN (or EHPLMN) ID, and through 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 with a UDM network element due to the terminal's registration via non-3GPP access, the UDM network element checks whether a different AMF network element with the same PLMN ID has already registered with the UDM network element via 3GPP access. If an AMF network element with the same PLMN ID is registered on the UDM network element for 3GPP access, and the UDM network element determines, based on an implementation mechanism (e.g., a specific GUAMI range), that the AMF network element is in the managed operator's PLMN, then the UDM network element refuses to register the AMF network element for non-3GPP access. Based on the rejection received from the UDM network element, the AMF network element can refuse terminal registration via non-3GPP access with a backoff timer. This allows a single AMF network element to handle the mobility registration of the first terminal, complying with protocol requirements. It also avoids the problem described in Scenario A above, where the first terminal's 3GPP registration cannot switch to the AMF network element selected for non-3GPP registration, resulting in two AMF network elements simultaneously handling the first terminal's mobility registration. For example, after the first terminal registers on a non-3GPP access side, it cannot switch to the AMF network element selected for non-3GPP registration due to the first terminal's 3GPP registration, causing the first terminal to be unable to receive MT data packets.

[0227] In this scenario, if the above conditions that disallow the first terminal to register on a non-3GPP access side are met, then S612 is executed.

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

[0229] The response message to registration request message 6 is used to refuse the first terminal's registration to a non-3GPP access side through the first AMF network element. This response message to registration request message 6 is the second message mentioned earlier.

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

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

[0232] The response message to registration request message 5 indicates that the first terminal cannot register in a non-3GPP area in the current region, or it indicates that the first terminal should postpone its registration in a non-3GPP area. The response message to registration request message 5 is the same as the fourth message mentioned earlier.

[0233] Furthermore, if the response message of registration request message 5 instructs the first terminal to postpone registration in non-3GPP, the response message of registration request message 5 can also instruct the first terminal to postpone the registration time in non-3GPP.

[0234] Optionally, the response message of registration request message 5 may utilize 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 to postpone registration in non-3GPP.

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

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

[0237] Furthermore, if the response message of registration request message 4 instructs the first terminal to postpone registration in non-3GPP, the response message of registration request message 4 can also instruct the first terminal to postpone the registration time in non-3GPP.

[0238] Optionally, the response message to registration request message 4 may carry the registration reason value from the response message to registration request message 5.

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

[0240] This application addresses the scenario where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or delaying the first terminal's registration on the non-3GPP access side, it enables a single AMF network element to handle the first terminal's mobility registration, which complies with protocol requirements. It also avoids the problems caused by two AMF network elements simultaneously handling the first terminal's mobility registration on the same PLMN, as described in Scenario A above, such as the first terminal being unable to receive MT data packets.

[0241] Example 2:

[0242] Figure 7 shows a flowchart of another network registration method provided in an embodiment of this application.

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

[0244] 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 AMF network element.

[0245] Optionally, prior to S701, the first terminal could register with the 3GPP network via the second AMF network element.

[0246] 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.

[0247] In one possible implementation, since the first terminal registers with the 3GPP network, the second AMF network element assigns a GUTI to the first terminal when it accesses the 3GPP network. This GUTI can be carried in the first message, allowing the first AMF network element to 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.

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

[0249] In one possible implementation, the first AMF network element can determine whether 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 falls within 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 assigned by the PARTICIPATING OPERATOR for non-directly shared areas. For instance, the AMF Identifier carried by the GUAMI of the second AMF network element can be assigned by a second operator for non-directly shared network areas.

[0250] For example, the first AMF network element can obtain the GUAMI of the second AMF network element through the GUTI carried in the first message.

[0251] In another possible implementation, the second AMF network element can send first information to the first AMF network element, indicating that the second AMF network element belongs to the HOSTING OPERATOR. Thus, the first AMF network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the first information.

[0252] For example, the first AMF network element can send a third message to the second AMF network element, which requests 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, which carries the context information of the first terminal and the first information.

[0253] As an alternative, the first AMF network element may execute S702 and S703 as described above if it is determined that the home network of the first terminal supports indirect network sharing.

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

[0255] The second message is used to indicate that the first terminal cannot register in a non-3GPP area in the current region, or the second message indicates that the first terminal should postpone its registration in a non-3GPP area.

[0256] Furthermore, if the second message instructs the first terminal to postpone its registration with non-3GPP, the second message can also instruct the first terminal to postpone the time of its registration with non-3GPP.

[0257] This application addresses the scenario where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or delaying the first terminal's registration on the non-3GPP access side, it enables a single AMF network element to handle the first terminal's mobility registration, which complies with protocol requirements. It also avoids the problems caused by two AMF network elements simultaneously handling the first terminal's mobility registration on the same PLMN, as described in Scenario A above, such as the first terminal being unable to receive MT data packets.

[0258] To facilitate understanding of the scheme, the following explanation uses the example of the first operator being the HOSTING OPERATOR and the second operator being the PARTICAPTING OPERATOR to illustrate the registration process of the first terminal in the INS area.

[0259] As shown in Figure 8, the registration process of the first terminal in the INS region may include:

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

[0261] The broadcast PLMN information 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).

[0262] S802, the first terminal sends a registration request message 1 to the access network device.

[0263] Registration Request Message 1 is used to request registration on the 3GPP network.

[0264] Optionally, assuming 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, i.e., the HPLMN / EHPLMN of the second operator.

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

[0266] Registration request message 2 is used to request the first terminal to register on the 3GPP network. Optionally, registration request message 2 may carry the HPLMN / EHPLMN selected by the first terminal, i.e., the PLMN of the second operator.

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

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

[0269] Optionally, 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 on the 3GPP network is the PLMN information of the first operator.

[0270] Optionally, the aforementioned AMF Identifier may be assigned by a second operator for areas that are not directly network-shared.

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

[0272] The response message of registration request message 3 is used to confirm that the first terminal has registered with the 3GPP network through the second AMF network element.

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

[0274] The response message of registration request message 2 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message of registration request message 2 may carry the GUTI assigned to the first terminal by the second AMF network element, 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>.

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

[0276] The response message to Registration Request Message 1 is used to confirm the registration of the first terminal in the 3GPP network. Optionally, the response message to Registration Request Message 1 may carry the GUTI assigned to the first terminal by the second AMF network element.

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

[0278] Registration request message 4 is used to request registration on a non-3GPP access side. Registration request message 4 may carry the GUTI allocated to the first terminal by the second AMF network element.

[0279] When the first terminal registers its N3IWF network element on a non-3GPP access side, the N3IWF network element belongs to the second operator.

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

[0281] Registration request message 5 is used to request the first terminal to register on a non-3GPP access side. Optionally, registration request message 5 may carry the GUTI allocated to the first terminal by the second AMF network element. Here, registration request message 5 is the same as the first message mentioned above.

[0282] 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 re-selects an AMF network element belonging to the second operator (i.e., the first AMF network element) for registration.

[0283] S810, the first AMF network element determines whether the first terminal is allowed to register on a non-3GPP access side.

[0284] For example, the first AMF network element may disallow the first terminal from registering with non-3GPP networks if the following conditions are met:

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

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

[0287] For the specific method, please refer to the relevant descriptions in the previous S702 and S703, and no further elaboration will be provided here.

[0288] In a possible implementation, the first AMF network element may execute S810 when it determines that the home network of the first terminal supports non-direct network sharing.

[0289] In this scenario, if the condition of not allowing the first terminal to register on the non-3GPP access side is met, then S811 is executed.

[0290] S811: The first AMF network element sends a response message to the registration request message 5 to the N3IWF network element.

[0291] Among them, the response message to the registration request message 5 is used to indicate that the first terminal cannot register on the non-3GPP in the current area, or the response message to the registration request message 5 indicates that the first terminal delays registering on the non-3GPP. Here, the response message to the registration request message 5 is the second message mentioned above.

[0292] Furthermore, if the response message to the registration request message 5 indicates that the first terminal delays registering on the non-3GPP, the response message to the registration request message 5 may also indicate the time for the first terminal to delay registering on the non-3GPP.

[0293] Optionally, the response message to the registration request message 5 may use the existing registration cause value of the first AMF network element to indicate that the first terminal cannot register on the NON-3GPP in the current area, or delays registering on the non-3GPP.

[0294] S812: The N3IWF network element sends a response message to the registration request message 4 to the first terminal.

[0295] Among them, the response message to the registration request message 4 is used to indicate that the first terminal cannot register on the non-3GPP in the current area, or the response message to the registration request message 4 indicates that the first terminal delays registering on the non-3GPP.

[0296] Furthermore, if the response message to the registration request message 4 indicates that the first terminal delays registering on the non-3GPP, the response message to the registration request message 4 may also indicate the time for the first terminal to delay registering on the non-3GPP.

[0297] Optionally, the response message to registration request message 4 may carry the registration reason value from the response message to registration request message 5.

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

[0299] This application addresses the scenario where a first terminal has already registered on a 3GPP network and then registers on a non-3GPP access side. By rejecting or delaying the first terminal's registration on the non-3GPP access side, it enables a single AMF network element to handle the first terminal's mobility registration, which complies with protocol requirements. It also avoids the problems caused by two AMF network elements simultaneously handling the first terminal's mobility registration on the same PLMN, as described in Scenario A above, such as the first terminal being unable to receive MT data packets.

[0300] Example 3:

[0301] Figure 9 shows a flowchart of a network registration method provided in an embodiment of this application.

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

[0303] The second message is used to request the context migration of the first terminal to the second AMF network element. Optionally, the second message may carry the GUAMI of the second AMF network element.

[0304] Optionally, the second AMF network element can send a second message triggered by the first message. The first message requests the first terminal to register with the 3GPP network through the second AMF network element, and carries the GUTI allocated to the first terminal by the first AMF network element when the first terminal registers with a non-3GPP access side.

[0305] Optionally, prior to S901, the first terminal can register with a 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 can register with a non-3GPP access side through the first AMF network element.

[0306] In one exemplary embodiment, the first AMF network element belongs to the PARTICAPTING OPERATOR, and the second AMF network element belongs to the HOSTING OPERATOR.

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

[0308] In one possible implementation, if the second AMF network element is a HOSTING OPERATOR, the second AMF network element can send first information to the first AMF network element. This first information instructs the non-3GPP access side to delete the context information of the first terminal. Therefore, the first AMF network element can determine to delete the context information of the non-3GPP access side's first terminal based on the first information sent by the second AMF network element.

[0309] For example, the first information can indirectly instruct the non-3GPP access side to delete the first terminal's context information by instructing the first terminal to register on the 3GPP network. Alternatively, the first information can also directly instruct the deletion of the first terminal's context information on the non-3GPP access side.

[0310] The following describes two methods for the second AMF network element to send the first information.

[0311] In one approach, the second AMF network element can send the first information when requesting context information from the first AMF network element. For example, the first information can be carried in the second message mentioned above.

[0312] In method two, the second AMF network element can obtain the context information of the first terminal and determine that the first terminal has registered on a non-3GPP access side based on the context information. Optionally, after the first terminal is in a connected state on the non-3GPP access side, it sends a first message 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, the third message carrying the context information of the first terminal. The second AMF network element determines that the first terminal has 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 on the non-3GPP access side, it sends a fourth message to the first AMF network element, the fourth message being used to confirm that it has received the context information of the first terminal from the first AMF network element, and the fourth message carrying the first information.

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

[0314] 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.

[0315] As an optional approach, in the above implementation, the second AMF network element can determine the first AMF network element based on 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 assigned to the first terminal by the first AMF network element when the first terminal registers with a non-3GPP access side.

[0316] In another possible implementation, the first AMF network element can determine the deletion of the context information of the first terminal in the N3IWF network element by determining that the second AMF network element belongs to the HOSTING OPERATOR.

[0317] 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 instance, if the GUAMI of the second AMF network element falls within 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 assigned by the PARTICIPATING Operator for non-directly shared areas. For example, the AMF Identifier carried by the GUAMI of the second AMF network element can be assigned by a second operator for non-directly shared network areas.

[0318] For example, the first AMF network element can obtain the GUAMI of the second AMF network element through the second message.

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

[0320] The second information is used to instruct non-3GPP interoperability network elements to delete the context information of the first terminal.

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

[0322] 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 the idle state.

[0323] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The AMF network element on the non-3GPP access side receives an instruction to delete the first terminal's context information, thereby promptly releasing the first terminal's context information in the N3IWF network element and conserving N3IWF network element resources. Furthermore, by promptly releasing the first terminal's context information in the N3IWF network element, the first terminal can be promptly released to an idle state, thus preventing communication anomalies on the non-3GPP access side.

[0324] To facilitate understanding of the scheme, the following explanation uses the example of the first operator being the HOSTING OPERATOR and the second operator being the PARTICAPTING OPERATOR to illustrate the registration process of the first terminal in the INS area.

[0325] As shown in Figure 10, the registration process of the first terminal in the INS region may include:

[0326] S1001, the access network device broadcasts PLMN information.

[0327] The broadcast PLMN information 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).

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

[0329] Among them, registration request message 1 is used to request registration on a non-3GPP access side.

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

[0331] When the first terminal registers its N3IWF network element on a non-3GPP access side, the N3IWF network element belongs to the second operator.

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

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

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

[0335] Registration request message 3 is used to request the first terminal to register with a non-3GPP access side through the first AMF network element. Optionally, registration request message 3 may carry the GUAMI of the first AMF network element. The GUAMI of the first AMF network element carries the HPLMN / EHPLMN selected by the first terminal, i.e., the PLMN of the second operator. For example, <GUAMI of the first AMF network element> = <PLMN of the second operator, i.e., HPLMN / EHPLMN> <AMF Identifier of the first AMF network element>.

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

[0337] The response message of registration request message 3 is used to confirm that the first terminal has registered with the non-3GPP access side through the first AMF network element.

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

[0339] The response message to registration request message 2 is used to confirm the registration of the first terminal on a non-3GPP access side. Optionally, the response message to registration request message 2 may carry the GUTI assigned to the first terminal by the first AMF network element, 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>. This GUTI points to the first AMF network element of the second operator.

[0340] Optionally, the aforementioned AMF Identifier may be assigned by a second operator for areas that are not directly network-shared.

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

[0342] The response message to Registration Request Message 1 is used to confirm the registration of the first terminal on a non-3GPP access side. Optionally, the response message to Registration Request Message 1 may carry the GUTI assigned to the first terminal by the first AMF network element.

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

[0344] Registration request message 4 is used to request registration on the 3GPP network. Registration request message 4 may carry the GUTI assigned to the first terminal by the first AMF network element.

[0345] The first terminal selects the same PLMN (i.e., the PLMN of the second operator, or HPLMN / EHPLMN) to initiate registration on the 3GPP network.

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

[0347] Registration request message 5 is used to request the first terminal to register on the 3GPP network. Optionally, registration request message 5 may carry the GUTI assigned to the first terminal by the first AMF network element. Here, registration request message 5 is the same as the first message mentioned above.

[0348] Since the GUTI carried in 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 re-selects an AMF network element belonging to the first operator (i.e., the second AMF network element) for registration.

[0349] 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.

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

[0351] The context request message is used to request context information from the first terminal. This context request message is the second message mentioned earlier.

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

[0353] The response message to the context request message carries the response message of the context request message. Here, the response message to the context request message is the third message mentioned earlier.

[0354] Optionally, the second AMF network element can also send a registration status update message to the first AMF network element. This registration status update message is used to confirm receipt / update of the first terminal's context information. This registration status update message is the fourth message mentioned earlier.

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

[0356] The specific method by which the first AMF network element determines the deletion of the context information of the first terminal in the N3IWF network element can be found in the relevant description of S902, and will not be repeated here.

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

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

[0359] Optionally, the first AMF network element can delete the context information of the first terminal.

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

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

[0362] 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 the idle state.

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

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

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

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

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

[0368] It should be noted that steps S1001~S1008, S1010~1011, and S1015~S1017 are optional.

[0369] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The AMF network element on the non-3GPP access side instructs the non-3GPP access side to delete the first terminal's context information, thereby promptly releasing the first terminal's context information in the N3IWF network element and conserving N3IWF network element resources. Furthermore, by promptly releasing the first terminal's context information in the N3IWF network element, the first terminal can be promptly released to an idle state, thus preventing communication anomalies on the non-3GPP access side.

[0370] Example 4:

[0371] Figure 11 is a flowchart illustrating a network registration method provided in an embodiment of this application.

[0372] S1101, the second AMF network element sends a first message. Correspondingly, the UDM network element receives the first message, which 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.

[0373] As an example, the first AMF network element and the second AMF network element are located in the same PLMN.

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

[0375] In one possible implementation, before S1101, the second AMF network element can 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.

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

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

[0378] In one possible implementation, the UDM network element can determine whether 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 falls within 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 assigned by the PARTICIPATING OPERATOR for the non-directly shared area. For instance, the AMF Identifier carried by the GUAMI of the second AMF network element can be assigned by the second operator for the non-directly shared network area.

[0379] For example, a UDM network element can obtain the GUAMI of a second AMF network element through a registration request from the second AMF network element (i.e., the third message mentioned above). For instance, the third message carries the GUAMI of the second AMF network element.

[0380] In another possible implementation, the UDM network element can 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 can determine that the second AMF network element belongs to the HOSTING OPERATOR and the first operator is the HOSTING OPERATOR.

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

[0382] In another possible implementation, the UDM network element can determine that the second AMF network element belongs to the HOSTING OPERATOR based on the indication information carried in the registration request of the second AMF network element (i.e., the third message mentioned above). For example, the third message carries 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.

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

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

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

[0386] In one possible implementation, the UDM network element can send the first information via a second message, wherein the second message instructs the first AMF network element to register.

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

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

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

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

[0391] 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 the idle state.

[0392] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The UDM network element instructs the non-3GPP access side to delete the first terminal's context information, thereby promptly releasing the first terminal's context information in the N3IWF network element and conserving N3IWF network element resources. Furthermore, by promptly releasing the first terminal's context information in the N3IWF network element, the first terminal can be promptly released to an idle state, thus preventing communication anomalies on the non-3GPP access side.

[0393] To facilitate understanding of the scheme, the following explanation uses the example of the first operator being the HOSTING OPERATOR and the second operator being the PARTICAPTING OPERATOR to illustrate the registration process of the first terminal in the INS area.

[0394] As shown in Figure 12, the registration process of the first terminal in the INS region may include:

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

[0396] 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).

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

[0398] Among them, registration request message 1 is used to request registration on a non-3GPP access side.

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

[0400] When the first terminal registers its N3IWF network element on a non-3GPP access side, the N3IWF network element belongs to the second operator.

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

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

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

[0404] Registration request message 3 is used to request the first terminal to register with a non-3GPP access side through the first AMF network element. Optionally, registration request message 3 may carry the GUAMI of the first AMF network element. The GUAMI of the first AMF network element carries the HPLMN / EHPLMN selected by the first terminal, i.e., the HPLMN / EHPLMN of the second operator. For example, <GUAMI of the first AMF network element> = <PLMN of the second operator, i.e., HPLMN / EHPLMN> <AMF Identifier of the first AMF network element>.

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

[0406] The response message of registration request message 3 is used to confirm that the first terminal has registered with the non-3GPP access side through the first AMF network element.

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

[0408] The response message to registration request message 2 is used to confirm the registration of the first terminal on a non-3GPP access side. Optionally, the response message to registration request message 2 may carry the GUTI assigned to the first terminal by the first AMF network element. This 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>. This GUTI points to the first AMF network element of the second operator.

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

[0410] The response message to Registration Request Message 1 is used to confirm the registration of the first terminal on a non-3GPP access side. Optionally, the response message to Registration Request Message 1 may carry the GUTI assigned to the first terminal by the first AMF network element.

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

[0412] Registration request message 4 is used to request registration on the 3GPP network. Registration request message 4 may carry the GUTI assigned to the first terminal by the first AMF network element.

[0413] The first terminal selects the same PLMN (i.e., the PLMN of the second operator, or HPLMN / EHPLMN) to initiate registration on the 3GPP network.

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

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

[0416] Since the GUTI carried in 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 re-selects an AMF network element belonging to the first operator (i.e., the second AMF network element) for registration.

[0417] 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.

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

[0419] The context request message is used to request context information from the first terminal.

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

[0421] The response message of the context request message carries the response message of the context request message.

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

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

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

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

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

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

[0428] Registration request message 7 is used to request the updating of the AMF network element registered by the first terminal in the non-3GPP access side to the second AMF network element. Here, registration request message 7 is the same as the first message mentioned above.

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

[0430] Optionally, the UDM network element can determine whether to disallow the first terminal from registering on a non-3GPP access side by confirming that the following two conditions are met:

[0431] 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.

[0432] Condition B: The second AMF network element belongs to the HOSTING OPERATOR. For details, please refer to the relevant description in S1102 above; it will not be elaborated upon here.

[0433] Optionally, when the UDM network element determines that the first terminal is not allowed to register on a non-3GPP access side, it can 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.

[0434] Optionally, when the UDM network element determines that the first terminal is not allowed to register on a 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 come from the home PLMN, or the first AMF network element and the second AMF network element come from the equivalent home PLMN.

[0435] In one possible implementation, the UDM network element can execute S1215 if it determines that the home network of the first terminal supports indirect network sharing.

[0436] In one possible implementation, if a terminal attempts to be served by 3GPP access via indirect network sharing, where the shared RAN broadcasts the HPLMN (or EHPLMN) ID, and accesses via a non-3GPP network with the same HPLMN or EHPLMN ID, the registration process is as follows: When a new AMF network element in the managed operator receives a terminal registration via 3GPP access, the new AMF network element can check whether the terminal previously registered in the same PLMN via 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 with 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. This allows for the timely release of the context information of the first terminal in the N3IWF network element, thereby saving N3IWF network element resources. Furthermore, 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 the idle state in a timely manner, thereby avoiding communication abnormalities of the first terminal on the non-3GPP access side.

[0437] 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 conditions for allowing the first terminal to register on the non-3GPP access side are met, that is, the registration of the second AMF network element on the non-3GPP access side is allowed, so S1216 is executed.

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

[0439] The "go-register" message instructs the first AMF network element to register. Optionally, the "go-register" message may carry first information. Here, the "go-register" message is the second message mentioned earlier.

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

[0441] Optionally, the first AMF network element can send a response message to the UDM network element for the deregistration message. The response message for the deregistration message is used to confirm that the first AMF network element has deregistered.

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

[0443] 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, i.e., step S1217.

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

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

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

[0447] 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 the idle state.

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

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

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

[0451] S1222, the access network device sends a response message to the first terminal, which is the registration request message 4.

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

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

[0454] This application addresses a scenario where a first terminal has already registered on a non-3GPP access side and then registers on a 3GPP network. The UDM network element instructs the non-3GPP access side to delete the first terminal's context information, thereby promptly releasing the first terminal's context information in the N3IWF network element and conserving N3IWF network element resources. Furthermore, by promptly releasing the first terminal's context information in the N3IWF network element, the first terminal can be promptly released to an idle state, thus preventing communication anomalies on the non-3GPP access side.

[0455] Based on the same inventive concept as the method embodiment, this application provides a communication device, the structure of which can be as shown in FIG13, including a communication unit 701 and a processing unit 702.

[0456] In one embodiment, the communication device can specifically be used to implement the method executed by the UDM network element in the embodiment of FIG5. The device can be the UDM network element itself, or a chip or chipset within the UDM network element, or a part of the chip used to execute the relevant method function. Specifically, the communication unit 701 is used to receive a first message, which requests the first terminal to register with a non-3GPP access side through a 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 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 second message, which rejects the first terminal's registration with a non-3GPP access side through the first mobility management function network element.

[0457] For example, the processing unit 702 is specifically configured to: determine that the second mobility management function network element belongs to the HOSTING OPERATOR based on the globally unique mobility management function identifier (GUAMI) of the second mobility management function network element.

[0458] For example, when processing unit 702 determines 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, it is specifically used to: determine that the GUAMI of the second mobility management function network element belongs to a specific value range, wherein the specific value range is allocated by the PATRICIPATING OPERATOR for a non-directly shared area.

[0459] For example, the processing unit 702 is specifically used to: 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.

[0460] For example, when 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.

[0461] For example, the processing unit 702 is specifically configured to: receive a third message through the communication unit 701, the third message being used to request the first terminal to register with the 3GPP network through the second mobility management function network element, the third message carrying 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.

[0462] For example, the processing unit 702 is specifically configured 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.

[0463] Optionally, the processing unit 702 is further configured 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 come from a home PLMN; or, determine that the first mobility management function network element and the second mobility management function network element come from an equivalent home PLMN.

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

[0465] In one embodiment, the communication device can specifically be used to implement the method executed by the UDM network element in the embodiment of FIG11. The device can be the UDM network element itself, or a chip or chipset within the UDM network element, or a part of the chip that performs the relevant method function. Specifically, the communication unit 701 is used to receive a first message requesting that the first mobility management function network element registered by the first terminal in the non-3GPP access side be updated to a 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 first information, which instructs the non-3GPP access side to delete the context information of the first terminal.

[0466] For example, the communication unit 701 is specifically used to: send a second message, the second message instructing the first mobility management function network element to register, the second message carrying the first information.

[0467] For example, the processing unit 702 is specifically configured to: determine that the second mobility management function network element belongs to the HOSTING OPERATOR based on the globally unique mobility management function identifier (GUAMI) of the second mobility management function network element.

[0468] For example, when processing unit 702 determines 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, it is specifically used to: determine that the GUAMI of the second mobility management function network element belongs to a specific value range, wherein the specific value range is allocated by the PATRICIPATING OPERATOR for a non-directly shared area.

[0469] For example, the processing unit 702 is specifically used to: 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.

[0470] For example, when 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.

[0471] For example, the processing unit 702 is specifically configured to: receive a third message through the communication unit 701, the third message being used to request the first terminal to register with the 3GPP network through the second mobility management function network element, the third message carrying 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.

[0472] In one embodiment, the communication device can specifically be used to implement the method executed by the first AMF network element in the embodiment of FIG11. The device can be the first AMF network element itself, or a chip or chipset within the first AMF network element, or a part of a chip for executing related method functions. Specifically, the processing unit 702 is configured to receive first information via the communication unit 701, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal; and to send third information via the communication unit 701, the third information being used to instruct the non-3GPP interoperability network element to delete the context information of the first terminal.

[0473] Optionally, the processing unit 702 is further configured to determine, before sending the third information through the communication unit 701, the existence of the first terminal's context information on the non-3GPP interoperability network element.

[0474] Optionally, when the processing unit 702 receives the first information through the communication unit 701, it is specifically used to: receive a second message through the communication unit 701, wherein the second message instructs the first mobility management function network element to register, and the second message carries the first information.

[0475] The module division in this application embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules. It is understood that the functions or implementations of the modules in the embodiments of this application can be further described in the relevant descriptions of the method embodiments.

[0476] In one possible embodiment, the communication device can be as shown in FIG14. This device can be a communication equipment or a chip within a communication equipment, wherein the communication equipment can be the terminal device or the network device described in the above embodiments. The device includes a processor 801 and a communication interface 802, and may also include a memory 803. 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.

[0477] The processor 801 can be a CPU, a digital processing unit, or something similar. The communication interface 802 can be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device also includes a memory 803 for storing the program executed by the processor 801. The memory 803 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory 803 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited to this.

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

[0479] This application embodiment does not limit the specific connection medium between the communication interface 802, processor 801, and memory 803. In Figure 14, the memory 803, processor 801, and communication interface 802 are connected via a bus 804, which is represented by a thick line. The connection methods between other components are only illustrative and not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used in Figure 14, but this does not indicate that there is only one bus or one type of bus.

[0480] This application also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0481] This application also provides a communication system, including a communication device for implementing the UDM network element function in the embodiment of FIG5 and a communication device for implementing the first AMF network element function in the embodiment of FIG5.

[0482] This application also provides a communication system, including a communication device for implementing the second AMF network element function in the embodiment of FIG7 and a communication device for implementing the first AMF network element function in the embodiment of FIG7.

[0483] This application also provides a communication system, including a communication device for implementing the second AMF network element function in the embodiment of FIG9 and a communication device for implementing the first AMF network element function in the embodiment of FIG9.

[0484] This application also provides a communication system, including a communication device for implementing the UDM network element function in the embodiment of FIG11 and a communication device for implementing the first AMF network element function in the embodiment of FIG11.

[0485] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0486] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0487] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0488] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0489] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.< / mnc> < / mcc> < / guami> < / guami>

Claims

1. A network registration method, characterized in that, include: Receive a first message, the first message being used to request the first terminal to register with a non-3GPP access side through a 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 public land mobile network (PLMN). It is determined that the second mobility management function network element belongs to the hosting operator; A second message is sent, which is used to refuse the first terminal from registering to a non-3GPP access side through the first mobility management function network element.

2. The method as described in claim 1, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: Based on 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 as described in claim 2, characterized in that, Based on the 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, including: The GUAMI of the second mobility management function network element is determined to belong to a specific value range, which is allocated by the participating operator PATRICIPATING OPERATOR for non-directly shared areas.

4. The method as described in claim 1, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: Based on the service network information registered by the first terminal in the 3GPP network, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR.

5. The method as described in claim 4, characterized in that, Based on the service network information registered by the first terminal in the 3GPP network, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR, including: The service network information registered by the first terminal in the 3GPP network is determined to be the public land mobile network (PLMN) information of the first operator, and the first operator is the HOSTING OPERATOR.

6. The method as described in claim 1, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: A third message is received, which is used to request the first terminal to register with 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.

7. The method according to any one of claims 1-6, characterized in that, The step of 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, 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-7, characterized in that, Before sending the second message, the method further includes: It is determined that the first mobility management function network element and the second mobility management function network element come from the home PLMN; Alternatively, it can be determined that the first mobility management function network element and the second mobility management function network element originate from an equivalent home PLMN.

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

10. The method according to any one of claims 1-9, characterized in that, The second message carries a first reason value, which indicates 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.

11. A network registration method, characterized in that, include: Receive a first message, the first message being 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; It is determined that the second mobility management function network element belongs to the hosting operator; Send a first message, which instructs the non-3GPP access side to delete the context information of the first terminal.

12. The method as described in 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 as described in claim 11 or 12, characterized in that, The sending of the first information includes: A second message is sent, which instructs the first mobility management function network element to register, and the second message carries the first information.

14. The method according to any one of claims 11-13, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: Based on 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 as described in claim 14, characterized in that, Based on the 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, including: The GUAMI of the second mobility management function network element is determined to belong to a specific value range, which is allocated by the participating operator PATRICIPATING OPERATOR for non-directly shared areas.

16. The method according to any one of claims 11-13, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: Based on the service network information registered by the first terminal in the 3GPP network, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR.

17. The method as described in claim 16, characterized in that, Based on the service network information registered by the first terminal in the 3GPP network, it is determined that the second mobility management function network element belongs to the HOSTING OPERATOR, including: The service network information registered by the first terminal in the 3GPP network is determined to be 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-13, characterized in that, The determination that the second mobility management function network element belongs to the HOSTING OPERATOR includes: A third message is received, which is used to request the first terminal to register with 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.

19. A network registration method, characterized in that, include: Receive first information, the first information being used to instruct the non-3GPP access side to delete the context information of the first terminal; A third message is sent, which instructs the non-3GPP interoperability network element to delete the context information of the first terminal.

20. The method as described in claim 19, characterized in that, Before sending the third information, the method further includes: It is determined that the context information of the first terminal exists on the non-3GPP interoperability network element.

21. The method as described in claim 19 or 20, characterized in that, The receiving of the first information includes: A second message is received, which instructs the first mobility management function network element to register, and the second message carries the first information.

22. A communication device, characterized in that, It includes a processor and a memory, the memory being used to store program instructions, the processor executing the program instructions causing the method as claimed in any one of claims 1-10 to be executed, or the method as claimed in any one of claims 11-18 to be executed.

23. A communication device, characterized in that, It includes a processor and a memory, the memory being used to store program instructions, the processor causing the method as described in any one of claims 19-21 to be executed when the program instructions are executed.

24. A computer-readable storage medium, characterized in that, The computer storage medium stores computer-readable instructions that, when executed on a communication device, cause the method described in any one of claims 1-10 to be performed, or the method described in any one of claims 11-18 to be performed, or the method described in any one of claims 19-21 to be performed.

25. A computer program product, characterized in that, When the computer program product is run on the device, it causes the device to perform the method according to any one of claims 1-10, or the method according to any one of claims 11-18, or the method according to any one of claims 19-21.

26. A communication device, characterized in that, It includes units or modules for performing the method as described in any one of claims 1-10, or units or modules for performing the method as described in any one of claims 11-18.

27. A communication device, characterized in that, Includes units or modules for performing the method as described in any one of claims 19-21.

28. A chip, characterized in that, The chip is coupled to a memory for reading and executing program instructions stored in the memory to implement the method as described in any one of claims 1-10, or to implement the method as described in any one of claims 11-18.

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

Images