CN114423074A

CN114423074A - Communication method and device

Info

Publication number: CN114423074A
Application number: CN202011175696.3A
Authority: CN
Inventors: 朱强华; 于游洋; 吴问付
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-10-28
Filing date: 2020-10-28
Publication date: 2022-04-29

Abstract

The application relates to a communication method and device. The method comprises the steps that first core network equipment in a first network receives a first request message from second core network equipment, the first request message is used for the second core network equipment to request to provide service for terminal equipment, and the first request message comprises an initial registration type and information of SNPN accessed by the terminal equipment. The first core network device determines that the terminal device has registered with the first network through the SNPN. The first core network device sends a first response message to the second core network device, wherein the first response message comprises a failure result indication, or comprises a registration context of the terminal device, or comprises indication information used for indicating that the terminal device is registered to the first network through the SNPN. By the method provided by the embodiment of the application, the redundant registration process of the terminal equipment is reduced, and the resource consumed in the subsequent process is also reduced because the terminal equipment does not need to perform the registration process.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.

Background

A non-public network (NPN) is a non-public fifth generation mobile communication technology (5G) network, and the NPN may be implemented depending on support of a Public Land Mobile Network (PLMN) or may be implemented independently of support of the PLMN. For example, a stand alone SNPN (SNPN) in the NPN can be implemented without depending on the support of the PLMN.

At present, the SNPN can interwork with the PLMN through a non-3GPP interworking function (N3 IWF) architecture. For example, the terminal device may register to SNPN, and within SNPN, the terminal device may select N3IWF within PLMN, so as to access PLMN through N3IWF, and then register within PLMN, that is, the terminal device may access N3IWF of PLMN through SNPN, so as to complete registration with PLMN. In addition, besides the N3IWF framework, the terminal device may also implement the interworking between the SNPN and the PLMN in a roaming manner. For example, a terminal device subscribed to a PLMN may select a corresponding SNPN using a PLMN subscription configuration and register with the PLMN through an access SNPN.

It can be seen that the terminal device may register to the PLMN in two ways, which may be a case that the terminal device may register to the PLMN in an N3IWF way after registering to the PLMN in a roaming way when accessing the SNPN, which is equivalent to that the terminal device registers to the PLMN twice through the SNPN. After the terminal equipment is registered to the PLMN through the roaming mode, if the terminal equipment is registered to the PLMN through other modes, the redundant registration process is realized, and the registration through the N3IWF mode has more complex flow and needs to consume more resources.

Disclosure of Invention

The embodiment of the application provides a communication method and device, which are used for saving resources consumed by redundant subscription of terminal equipment.

In a first aspect, a first communication method is provided, where the method is performed by a first core network device or a chip capable of implementing functions of the first core network device. In the 5G system, the first core network device is, for example, a UDM. The method comprises the following steps: a first core network device in a first network receives a first request message from a second core network device, where the first request message is used for the second core network device to request to provide a service for a terminal device, the first request message includes an initial registration type and information of a non-public network to which the terminal device accesses, the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device, and the first network is a home network of the terminal device; the first core network device determines that the terminal device has registered with the first network through the non-public network; the first core network device sends a first response message to a second core network device, wherein the first response message comprises a failure result indication, or comprises the registration context of the terminal device, or comprises indication information used for indicating that the terminal device is registered to the first network through the non-public network.

In the embodiment of the present application, the first network is, for example, a PLMN, or a non-public network, or may be another network. The non-public network is for example SNPN. The first core network device receives a request message from a terminal device requesting registration to the first network through the SNPN. If the terminal device is determined to be registered to the first network through the SNPN, the first core network device rejects the registration of the terminal device, or the first core network device sends registration context or indication information of the terminal device to the second core network device, so that the second core network device can reject the registration of the terminal device. By the method, the redundant registration process of the terminal equipment is reduced, and the resource consumed in the subsequent process is also reduced because the terminal equipment does not need to perform the registration process.

In an alternative implementation, the information of the non-public network includes an identification of the non-public network, and/or a non-public network access mode indication.

The SNPN information includes, for example, an identification of the SNPN, or an SNPN access mode indication, or an identification of the SNPN and an SNPN access mode indication.

In an optional implementation, the method further includes: the first core network device receives a second request message from a third core network device, where the second request message is used for the third core network device to request a service to be provided for a terminal device, and the second request message includes information of the non-public network; the first core network equipment records the registration context of the terminal equipment, and the registration context of the terminal equipment comprises the information of the non-public network; and the first core network device sends a second response message to the third core network device, where the second response message is used to indicate that the third core network device is successfully registered to provide service for the terminal device.

This is the last registration procedure of the terminal device, i.e. the registration by which the terminal device has registered with the first network. In the registration process, the first core network device may record the SNPN information of the terminal device, so that if the terminal device subsequently registers to the first network again through the SNPN, the first core network device may reject the registration of the terminal device.

In an optional implementation manner, the determining, by the first core network device, that the terminal device has registered to the first network through the non-public network includes:

and the first core network equipment determines that the terminal equipment is registered to the first network through the non-public network according to the initial registration type, the information of the non-public network and the recorded registration context of the terminal equipment.

The initial registration type indicates that the terminal device is registered for the first time, and the first core network device records the registration context of the last registration of the terminal device, if the first request message includes the SNPN corresponding to the SNPN information. The SNPN corresponding to the SNPN information included in the registration context of the terminal device recorded by the first core network device is the same SNPN, and the first core network device may determine that the terminal device has registered in the first network through the SNPN. Through the record of the first core network device, the first core network device can compare the SNPN registered by the terminal device twice, so that the double registration of the terminal device is rejected.

In an optional implementation manner, the first response message further includes a cause value, and the cause value is used for indicating that the terminal device is registered to the first network through the non-public network.

If the first response message includes the failure result indication, the first response message may further include a cause value, so that the second core network device makes it clear why the first core network device rejects the registration.

In an optional implementation, the method further includes: the first core network equipment deletes the registration context of the second core network equipment corresponding to the non-public network; or, the first core network device receives a fourth request message from the second core network device, where the fourth request message is used to request the first core network device to de-register the registration of the second core network device in the first core network device, and the first core network device deletes the registration context of the second core network device corresponding to the non-public network.

If the first core network device rejects the current registration of the terminal device, the first core network device may delete the registration context of the second core network device corresponding to the SNPN by itself, that is, the first core network device deletes the information of the second core network device corresponding to the current registration. Or, if the second core network device rejects the current registration of the terminal device, which is equivalent to that the first core network device has no decision right, the second core network device may request, through the fourth request message, the first core network device to deregister the registration of the second core network device in the first core network device, and then the first core network device may delete the registration context of the second core network device corresponding to the SNPN. Therefore, no matter whether the first core network device can decide to reject the registration of the terminal device or not, the first core network device can delete the registration context corresponding to the SNPN of the second core network device, so that the storage space of the first core network device is saved, and the first core network device is prevented from storing error information.

In a second aspect, a second communication method is provided, which is performed by a second core network device, or a chip capable of implementing the functions of the second core network device, for example. In the 5G system, the second core network device is, for example, an AMF. The method comprises the following steps: a second core network device in a first network receives a third request message from a terminal device through a first network device, wherein the third request message is used for the terminal device to request to register to the first network, and the first network is a home network of the terminal device; the second core network equipment acquires the information of the non-public network accessed by the terminal equipment; the second core network device sends a first request message to a first core network device, where the first request message is used for the second core network device to request to provide a service for the terminal device, the first request message includes an initial registration type and information of the non-public network, and the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device; the second core network device receives a first response message from a first core network device, wherein the first response message comprises a failure result indication, or comprises a registration context of the terminal device, or comprises indication information used for indicating that the terminal device is registered to the first network through the non-public network; and the second core network equipment sends a third response message, wherein the third response message is used for rejecting the registration of the terminal equipment.

In an optional implementation manner, the obtaining, by the second core network device, information of a non-public network to which the terminal device accesses includes: the second core network device obtains the information of the non-public network from the third request message; or, the second core network device receives information of the non-public network from the first network device. The first network device is, for example, an N3IWF, or may be another network device.

The terminal device may include the SNPN information in the third request message, and the second core network device may obtain the SNPN information from the third request message, which is relatively simple in obtaining manner. Or, the N3IWF may determine the SNPN information and send the SNPN information to the second core network device, so that the terminal device does not need to determine the SNPN information, and the message sent by the terminal device to the N3IWF does not need to include the SNPN information, which is beneficial to saving signaling overhead.

In an optional implementation manner, the third response message further includes a cause value, and the cause value is used for indicating that the terminal device is registered to the first network through the non-public network.

In an optional implementation, the method further includes: the second core network device sends a fourth request message to the first core network device, where the fourth request message is used to request the first core network device to de-register the registration of the second core network device in the first core network device.

In an optional implementation manner, before the second core network device sends the third response message, the method further includes: and the second core network equipment determines to reject the registration of the terminal equipment according to the first response message.

With regard to the technical effects brought about by the second aspect or various alternative embodiments, reference may be made to the introduction of the technical effects of the first aspect or the respective embodiments.

In a third aspect, a third communication method is provided, which is performed by, for example, a first core network device or a chip capable of implementing a function of the first core network device. In the 5G system, the first core network device is, for example, a UDM. The method comprises the following steps: a first core network device in a first network receives a first request message from a second core network device, wherein the first request message is used for the second core network device to request to provide service for a terminal device, and the first request message also comprises a mobile registration type and information of a second non-public network, the mobile registration type is used for indicating that the first request message is a registration request triggered by the terminal device due to movement, and the first network is a home network of the terminal device; and the first core network equipment sends a first response message to the second core network equipment, wherein the first response message is used for indicating the second core network equipment to be successfully registered to provide service for the terminal equipment.

In the embodiment of the application, in a scenario that the terminal device is allowed to move from the first non-public network to the second non-public network, the first network can accept registration of the terminal device in the first network through the second non-public network, so that the terminal device can normally work.

In an optional implementation, the method further includes: and the first core network equipment deregisters the registration of the terminal equipment in the first network through the first non-public network.

The first core network device may deregister the registration of the terminal device in the first network through the first SNPN, because the first core network device accepts the registration of the terminal device in the first network through the second SNPN, so as to avoid that the terminal device registers in the first network twice.

In an optional implementation manner, the deregistration of the terminal device in the first network through the first non-public network by the first core network device includes: the first core network equipment deletes the registration context of a third core network equipment corresponding to the first non-public network; or, the first core network device receives a second request message from the second core network device, where the second request message is used to instruct de-registration of the terminal device in the first network through the first non-public network, and the first core network device deletes the registration context of the third core network device corresponding to the first non-public network.

If the first core network device determines to accept the current registration of the terminal device, the first core network device may delete the registration context of the third core network device corresponding to the first SNPN by itself, that is, the first core network device deletes the information of the third core network device corresponding to the current registration. Or, if the second core network device accepts the current registration of the terminal device, which is equivalent to that the first core network device has no decision right, the second core network device may request, through the second request message, the first core network device to perform de-registration on the registration of the third core network device in the first network, and then the first core network device may delete the registration context of the third core network device corresponding to the first SNPN. Therefore, whether the first core network device can decide to reject the registration of the terminal device or not, the first core network device can delete the registration context of the third core network device corresponding to the first SNPN, so that the storage space of the first core network device is saved, the first core network device is prevented from storing error information, and the terminal device is prevented from double registration in the first network.

In an alternative implementation, the information of the second non-public network includes an identity of the second non-public network, and/or a non-public network access mode indication.

The information of the second SNPN comprises, for example, an identification of the second SNPN, or a second SNPN access mode indication, or both an identification of the second SNPN and a second SNPN access mode indication.

In an optional implementation, the method further includes: the first core network device receives a second request message from the third core network device, where the second request message is used for the third core network device to request to provide a service for a terminal device, and the second request message includes information of the first non-public network; the first core network device records the registration context of the terminal device, and the registration context of the terminal device comprises the information of the first non-public network; and the first core network device sends a second response message to the third core network device, where the second response message is used to indicate that the third core network device is successfully registered to provide service for the terminal device.

This is the last registration procedure of the terminal device, i.e. the terminal device is registered with the first network via the first SNPN by this registration. In the registration process, the first core network device may record the information of the first SNPN, so that the first core network device may subsequently determine whether to accept re-registration after the terminal device moves.

In an alternative implementation, the information of the first non-public network includes an identity of the first non-public network, and/or a non-public network access mode indication.

The information of the first SNPN comprises, for example, an identification of the first SNPN, or a first SNPN access mode indication, or both an identification of the first SNPN and a first SNPN access mode indication.

In an optional implementation manner, the first response message includes a registration context of the terminal device.

The first response message may indicate that the PLMN AMF successfully registers to provide the service for the UE, and one indication manner is implicit indication, for example, the first core network device carries the registration context of the terminal device in the first response message, and the registration context of the terminal device may implicitly indicate that the second core network device successfully registers to provide the service for the terminal device. Or, another indication manner is an explicit indication, the first core network device may also carry indication information in the first response message, where the indication information may indicate that the terminal device has registered to the first network through the second SNPN, or indicate that the second core network device successfully registers to provide a service for the terminal device. The information quantity of the indication information is small, and signaling overhead can be saved.

In an optional implementation manner, before the first core network device sends the first response message to the second core network device, the method further includes:

and the first core network equipment determines that the second core network equipment is successfully registered to provide service for the terminal equipment according to the mobile registration type, the information of the second non-public network and the recorded registration context of the terminal equipment.

And the first core network equipment determines the terminal equipment as the registration after the movement according to the mobile registration type. And the second SNPN and the first SNPN corresponding to the information of the first SNPN included in the registration context of the terminal device are not the same SNPN, and the first core network device can determine that the terminal device is registered to the first network through another SNPN after moving, so that the first core network device can determine that the second core network device is successfully registered to provide service for the terminal device, and the terminal device can normally work after moving.

In a fourth aspect, a fourth communication method is provided, which is performed by, for example, the second core network device or a chip capable of implementing the function of the second core network device. In the 5G system, the second core network device is, for example, an AMF. The method comprises the following steps: a second core network device in a first network receives a third request message from a terminal device through a first network device, wherein the third request message is used for the terminal device to request registration to the first network, the third request message further comprises a mobile registration type, the mobile registration type is used for indicating that the third request message is a registration request triggered by the terminal device due to movement, and the first network is a home network of the terminal device; the second core network device sends a first request message to a first core network device, wherein the first request message is used for the second core network device to request to provide service for the terminal device, and the first request message comprises the mobile registration type and information of a second non-public network; the second core network device receives a first response message from the first core network device, where the first response message is used to indicate that the second core network device is successfully registered to provide service for the terminal device; and the second core network equipment sends a third response message to the terminal equipment, wherein the third response message is used for indicating that the terminal equipment is successfully registered to the first network.

In an optional implementation manner, before the second core network device sends the third response message to the terminal device, the method further includes: and the second core network equipment determines that the terminal equipment is successfully registered to the first network according to the mobile registration type, the information of the second non-public network and the registration context of the terminal equipment.

In an optional implementation, the method further includes: and the second core network equipment sends a second request message to the first core network equipment, wherein the second request message is used for indicating that the terminal equipment is unregistered with the first network through the first non-public network.

With regard to the technical effects brought about by the fourth aspect or the various alternative embodiments, reference may be made to the introduction of the technical effects of the third aspect or the respective embodiments.

In a fifth aspect, a fifth communication method is provided, which is performed, for example, by a first network device or by a chip capable of implementing the functionality of the first network device. In a 5G system, the first network device is, for example, an N3 IWF. The method comprises the following steps: a first network device in a first network receives a fourth request message from a terminal device, wherein the fourth request message is used for the terminal device to request to register to the first network, and the first network is a home network of the terminal device; the first network equipment determines the information of a non-public network accessed by the terminal equipment; and the first network equipment sends the information of the non-public network to second core network equipment.

The information of the SNPN can be determined by the N3IWF and sent to the second core network device, so that the terminal device does not need to determine the information of the SNPN, and the fourth request message sent by the terminal device to the N3IWF does not need to include the information of the SNPN, which is beneficial to saving signaling overhead.

In an optional implementation manner, the determining, by the first network device, information of a non-public network to which the terminal device accesses includes: the first network equipment determines the information of the non-public network accessed by the terminal equipment according to the corresponding relation between the non-public network and the tunnel or the IP address; or, the first network device determines the information of the non-public network accessed by the terminal device according to the corresponding relationship between the non-public network and the first network device.

For example, the correspondence between SNPN and tunnel, or tunnel between terminal device and N3IWF, or tunnel between SNPN UPF and N3IWF, is configured (or protocol specified) in advance, and is also known to terminal device or UPF, for example, SNPN and tunnel one-to-one correspondence. Then, when the UE sends the fourth request message or the UPF forwards the fourth request message of the terminal device, the UE may select a tunnel corresponding to the SNPN accessed by the terminal device to send, and then the N3IWF may determine the SNPN information accessed by the terminal device according to the tunnel receiving the fourth request message. For another example, the correspondence between the IP addresses of SNPN and SNPN UPF is configured (or defined by the protocol), for example, the IP addresses of SNPN and SNPN UPF are in one-to-one correspondence. Then, when the N3IWF receives the fourth request message from the SNPN UPF, it can determine the SNPN information of the fourth access based on the detected IP address of the SNPN UPF. As another example, a correspondence relationship between SNPN and N3IWF, which is also known to the terminal device, is configured (or protocol-specified) in advance, for example, SNPN and N3IWF ID are in one-to-one correspondence. Then the terminal device may select the N3IWF corresponding to the SNPN accessed by the terminal device when sending the fourth request message, and if the corresponding N3IWF receives the fourth request message from the terminal device, it may be determined that the SNPN accessed by the terminal device is the SNPN corresponding to the N3 IWF. Alternatively, the N3IWF may determine the SNPN information in other ways besides the above way, and the embodiment of the present application is not limited.

In a sixth aspect, a communication apparatus is provided, where the communication apparatus may be a first core network device, a second core network device, or a first network device, or the communication apparatus may also be a chip. The communication device has the functionality to implement the embodiments of any of the first, second, third, fourth, or fifth aspects described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventh aspect, a communication device is provided that includes a processor and a communication interface. Optionally, a memory may also be included, or the communication device may not include a memory, which may be external to the communication device. The memory is for storing a computer program, the processor executes the computer program stored by the memory when the communication device is running, such that the communication apparatus performs the method as performed by the first core network device in the first aspect or any of the optional embodiments of the first aspect, or to cause the apparatus to perform a method as performed by the second core network device in any of the optional embodiments of the second aspect or the second aspect as described above, or to cause the apparatus to perform the method as performed by the first core network device in any of the optional embodiments of the third aspect or the third aspect as described above, or to cause the apparatus to perform the method as described in the fourth aspect or any of the alternative embodiments of the fourth aspect by the second core network device, or to cause the apparatus to perform a method as described by the first network device in any of the optional embodiments of the fifth aspect or the fifth aspect above.

In an eighth aspect, there is provided a first communication system comprising the communication apparatus of the sixth aspect (performing the method of the first aspect or the various alternative embodiments of the first aspect) or the communication apparatus of the seventh aspect (performing the method of the first aspect or the various alternative embodiments of the first aspect), comprising the communication apparatus of the sixth aspect (performing the method of the second aspect or the various alternative embodiments of the second aspect) or the communication apparatus of the seventh aspect (performing the method of the second aspect or the various alternative embodiments of the second aspect), and comprising a communication apparatus according to the sixth aspect (performing the method according to the fifth aspect or the various alternative embodiments of the fifth aspect) or a communication apparatus according to the seventh aspect (performing the method according to the fifth aspect or the various alternative embodiments of the fifth aspect).

In a ninth aspect, there is provided a second communication system comprising the communication apparatus of the sixth aspect (performing the method of the third aspect or the various alternative embodiments of the third aspect) or the communication apparatus of the seventh aspect (performing the method of the third aspect or the various alternative embodiments of the third aspect), comprising the communication apparatus of the sixth aspect (performing the method of the fourth aspect or the various alternative embodiments of the fourth aspect) or the communication apparatus of the seventh aspect (performing the method of the fourth aspect or the various alternative embodiments of the fourth aspect), and comprising a communication apparatus according to the sixth aspect (performing the method according to the fifth aspect or the various alternative embodiments of the fifth aspect) or a communication apparatus according to the seventh aspect (performing the method according to the fifth aspect or the various alternative embodiments of the fifth aspect).

A tenth aspect provides a computer-readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the alternative embodiments described above.

In an eleventh aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the second aspect or any one of the alternative embodiments described above.

In a twelfth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the third aspect or any one of the alternative embodiments described above.

In a thirteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the fourth aspect or any one of the alternative embodiments described above.

In a fourteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the fifth aspect or any one of the alternative embodiments.

In a fifteenth aspect, there is provided a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the alternative embodiments described above.

In a sixteenth aspect, there is provided a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the second aspect or any one of the alternative embodiments described above.

A seventeenth aspect provides a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the third aspect or any one of the alternative embodiments above.

In an eighteenth aspect, there is provided a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the fourth aspect or any one of the alternative embodiments described above.

A nineteenth aspect provides a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the fifth aspect or any one of the alternative embodiments described above.

By the method provided by the embodiment of the application, the redundant registration process of the terminal equipment is reduced, and the resource consumed in the subsequent process is also reduced because the terminal equipment does not need to perform the registration process.

Drawings

FIG. 1 is a diagram of a 5G communication system architecture;

FIG. 2 is a more detailed diagram of a 5G communication system architecture;

FIG. 3A is a diagram of a UE accessing a PNI-NPN;

fig. 3B is a diagram illustrating the UE accessing SNPN;

fig. 4A is a schematic diagram of the implementation of SNPN interworking with PLMN by N3 IWF;

fig. 4B is a diagram illustrating the interworking between SNPN and PLMN via a roaming architecture;

fig. 5 is a diagram illustrating a PLMN may support UE registration in different ways;

fig. 6 is a flowchart of a first communication method according to an embodiment of the present application;

fig. 7 is a flowchart of a second communication method provided in the embodiment of the present application;

FIG. 8 is a diagram illustrating a UE that may re-register with a PLMN after moving;

fig. 9 is a flowchart of a third communication method provided in the embodiment of the present application;

fig. 10 is a flowchart of a fourth communication method provided in the embodiment of the present application;

FIG. 11 is a schematic view of an apparatus provided in an embodiment of the present application;

fig. 12 is a schematic view of another apparatus provided in the present application.

Detailed Description

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

Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

In the embodiment of the present application, the terminal device is a device having a wireless transceiving function, and may be a fixed device, a mobile device, a handheld device, a wearable device, an in-vehicle device, or a wireless apparatus (e.g., a communication module or a chip system) built in the above device. The terminal device is used for connecting people, objects, machines and the like, and can be widely used in various scenes, such as but not limited to the following scenes: cellular communication, device-to-device communication (D2D), vehicle-to-all (V2X), machine-to-machine/machine-type communication (M2M/MTC), internet of things (IoT), Virtual Reality (VR), Augmented Reality (AR), industrial control (industrial control), unmanned driving (self driving), remote medical (remote medical), smart grid (smart grid), smart furniture, smart office, smart wearing, smart transportation, smart city (smart city), unmanned aerial vehicle, robot, etc. scenarios. The terminal device may sometimes be referred to as a User Equipment (UE), a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment, and for convenience of description, the terminal device is described as an example of the UE in this embodiment of the present application.

The network device in the embodiment of the present application includes, for example, an access network device and/or a core network device. The access network equipment is equipment with a wireless transceiving function and is used for communicating with the terminal equipment. The access network device includes, but is not limited to, a base station (BTS, Node B, eNodeB/eNB, or gbnodeb/gNB) in the above communication system, a Transmission Reception Point (TRP), a base station for subsequent evolution of 3GPP, an access Node in a wireless fidelity (WiFi) system, a wireless relay Node, a wireless backhaul Node, and the like. The base station may be: macro base stations, micro base stations, pico base stations, small stations, relay stations, etc. Multiple base stations may support the same access technology network as mentioned above, or may support different access technologies networks as mentioned above. A base station may include one or more co-sited or non-co-sited transmission receiving points. The network device may also be a wireless controller, a Centralized Unit (CU), and/or a Distributed Unit (DU) in a Cloud Radio Access Network (CRAN) scenario. The network device may also be a server, a wearable device, or a vehicle mounted device, etc. For example, the network device in vehicle to everything (V2X) technology may be a Road Side Unit (RSU). The following description will take the access network device as a base station as an example. The multiple network devices in the communication system may be base stations of the same type or different types. The base station may communicate with the terminal device, and may also communicate with the terminal device through the relay station. A terminal device may communicate with multiple base stations in different access technologies. The core network equipment is used for realizing the functions of mobile management, data processing, session management, policy, charging and the like. The names of devices implementing the core network function in systems with different access technologies may be different, and this application does not limit this. Taking a 5G system as an example, the core network device includes: access and mobility management function (AMF), Unified Data Management (UDM), or User Plane Function (UPF), etc.

In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device, or may be an apparatus capable of supporting the network device to implement the function, for example, a system on chip, and the apparatus may be installed in the network device. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a network device is taken as an example of a network device, and the technical solution provided in the embodiment of the present application is described.

In this application, the number of nouns means "singular nouns or plural nouns" or "one or more" unless otherwise specified. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. For example, A/B, represents: a or B. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, represents: a, b, c, a and b, a and c, b and c, or a and b and c, wherein a, b and c can be single or multiple.

Currently, mobile networks accessible to the UE include 2G, 3G, and 4G networks, which provide a service data transmission channel for a call service, a video service, a web service, and the like of the UE. However, the explosive development of new services such as internet of vehicles, virtual reality, mobile office, internet of things and the like requires that a mobile network provides an optical fiber-like access rate, the use experience of zero time delay, the connection capability of billions of devices, the consistent service of multiple scenes such as ultrahigh flow density, ultrahigh connection number density and ultrahigh mobility, the intelligent optimization of service and user perception, the energy efficiency improvement of more than one hundred times and the bit cost reduction of more than one hundred times, which are soft ribs of the traditional network, cannot protect the driving for the high-speed development of future services.

The 5G communication system architecture specified by the 3th generation partnership project (3 GPP) standard has four components, which can be referred to in fig. 1. Fig. 1 includes a next generation ue (next generation ue), a next generation (radio) access network (R) AN, a next generation core network (core), and a data network (data network). NextGen (or NG) is a short for next generation (i.e., 5G) mobile communication system architecture, consisting of UE, AN, Core and data network. The UE, the AN, and the Core are main components constituting the architecture, and logically they may be divided into two parts, i.e., a user plane and a control plane, where the control plane is responsible for management of the mobile network and the user plane is responsible for transmission of service data. In fig. 1, the NG2 reference point is located between the AN control plane and the Core control plane, the NG3 reference point is located between the AN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

The UE is an entrance for interaction between a mobile user and a network, and can provide basic computing capacity and storage capacity, display a service window for the user and accept operation input of the user. The NextGen UE will use the new air interface technology to establish signal connection and data connection with the AN, thereby transmitting control signals and service data to the mobile network.

The AN, similar to a base station in a conventional network, is deployed at a location close to the UE, provides a network access function for authorized users in a specific area, and can determine transmission tunnels of different qualities according to user levels, service requirements, and the like to transmit user data. The AN can manage the resources of the AN, reasonably utilize the resources, provide access services for the UE as required, and is responsible for forwarding control signals and user data between the UE and the core network.

The Core may include a plurality of network elements, and the network elements are responsible for maintaining subscription data of the mobile network, managing network elements of the mobile network, and providing functions of session management, mobility management, policy management, security authentication, and the like for the UE. When the UE is attached, network access authentication is provided for the UE; when the UE has a service request, network resources are distributed to the UE; updating network resources for the UE when the UE moves; when the UE is idle, a fast recovery mechanism is provided for the UE; when UE is detached, releasing network resources for the UE; when the UE has service data, providing a data routing function for the UE, such as forwarding uplink data to a data network; or receiving downlink data of the UE from the data network, forwarding the downlink data to the AN, and then sending the downlink data to the UE.

A data network is a network that provides business services to users. The data network may comprise a plurality of application servers for serving respective applications. The client of the application is typically installed in the UE and the server of the application (i.e. the application server) is located within the data network. The data network may be a private network, such as a local area network, or may also be an external network not controlled by the operator, such as the internet (internet), or may also be a private network co-deployed by the operator, such as a network providing an IP multimedia network subsystem (IMS) service.

Referring to fig. 2, a core network of the 5G network architecture is further detailed on the basis of fig. 1. Wherein, the core network user plane comprises UPF; the core network control plane includes an authentication server function (AUSF), an AMF, a Session Management Function (SMF), a Network Slice Selection Function (NSSF), a network open function (NEF), a network function repository function (NF, NRF), an UDM, a Policy Control Function (PCF), an Application Function (AF), and the like. The core network control plane adopts a service architecture, and the interaction between the control plane network elements adopts a service calling mode to replace a point-to-point communication mode in the traditional architecture. In a service architecture, one control plane network element opens a service to other control plane network elements for the other control plane network elements to call; in point-to-point communication, a communication interface between control plane network elements has a set of specific messages, which can only be used by the control plane network elements at both ends of the interface during communication.

The functions of the network elements in the core network are introduced as follows:

and the UPF performs user data packet forwarding according to the routing rule of the SMF, for example, the uplink data is sent to the DN or other UPFs, and the downlink data is forwarded to other UPFs or RANs.

AUSF, performing security authentication of the UE.

AMF, access management and mobility management of UE. The method is responsible for state maintenance of the UE, reachability management of the UE, forwarding of non-Mobility Management (MM) non-access-stratum (NAS) messages, and forwarding of Session Management (SM) N2 messages.

SMF, UE conversation management, distributing resource for UE conversation and releasing resource. The resources include quality of service (QoS) of the session, session path, forwarding rules, etc.

NSSF, network slice selection for UE.

NEF, which opens network functions to third parties in the form of an Application Programming Interface (API) interface.

NRF, providing storage function and selection function of network function entity information for other network elements.

UDM, user subscription context management.

PCF, user policy management.

AF, application management.

Next, the NPN concept is described.

The NPN is a non-public 5G network, and the NPN can be implemented depending on the support of the PLMN, and the NPN implemented depending on the support of the PLMN is called a public network integrated NPN (PNI-NPN); alternatively, the NPN may be implemented independently of the network function of the PLMN, and the NPN implemented independently of the support of the PLMN is referred to as SNPN.

The PNI-NPN may be implemented using a network slice in the PLMN or a proprietary Data Network Name (DNN). In order to prevent unauthorized UEs from attempting to access and select the PNI-NPN, the PNI-NPN additionally uses a Closed Access Group (CAG) function. Some UEs allowed to access the PNI-NPN may be configured with available CAG ID and CAG indication, which may indicate that the UE is allowed to access 5GS only through a CAG cell, and the subscription data of the UE stored by the UDM may also include the CAG ID and CAG indication available to the UE. The CAG cell broadcasts the CAG ID supported by the cell, and the UE determines whether the UE can access the cell according to the received CAG ID.

Please refer to fig. 3A, which illustrates a UE accessing a PNI-NPN. Fig. 3A includes two base stations, wherein a cell provided by the base station a is a CAG cell, and the CAG cell issues a PLMN ID a and a CAG ID X through a System Information Block (SIB). The cell provided by the base station B does not belong to PNI-NPN, namely is not a CAG cell, and the cell issues the PLMN ID A through SIB, but does not issue the CAG ID. For example, UE1 is configured with CAG ID X, then UE1 can access base station a as well as base station B. For example, UE2 is configured with CAG ID X and CAG indication, then UE2 can access base station a and not base station B. For example, UE3 is not configured with CAG ID and CAG indication, i.e., UE3 does not allow access to PNI-NPN, then UE3 cannot access base station a, but UE3 can access base station B.

SNPN is deployed independently and does not depend on PLMN network. The SNPN is identified using a PLMN ID + Network Identifier (NID), where the PLMN ID may be an inherent value reserved by a third party operator or a specific value of a PLMN operator deploying the SNPN. In the SNPN, a cell belonging to the SNPN broadcasts a PLMN ID + NID, the UE selects a cell according to the broadcast information and network selection information configured for the UE, and the network selection information configured for the UE may include the PLMN ID + NID. For example, if the UE determines that the configured network selection information is not the same as the PLMN ID and/or NID broadcast by the cell, the UE will not access the cell.

Please refer to fig. 3B, which illustrates an access of SNPN by a UE. Note that the non-public network ID in fig. 3B is N, which indicates that the ID of the non-public network is N. For example, a base station belonging to SNPN broadcasts PLMN ID + NID, and the network selection information of the UE4 includes the PLMN ID + NID, then the UE4 can access the base station.

Currently, SNPN can interwork with PLMNs through N3IWF architecture. As shown in fig. 4A, the UE uses the SNPN private network subscription to select the SNPN ID, and accesses the SNPN base station to perform 3GPP registration in the SNPN network; UE uses public network contract of PLMN to select PLMN ID, selects PLMN N3IWF, establishes connection with PLMN N3IWF through PDU conversation in SNPN network to access PLMN N3IWF, and then carries out registration in non-3GPP access mode in PLMN network through N3 IWF. In fig. 4A, SNPN 3GPP access (SNPN 3GPP access) indicates that the UE accesses the SNPN over 3GPP technology at the air interface. Nwu (nwu for PLMN) of the PLMN means that the UE accesses the PLMN using Nwu interface between the UE and N3IWF of the PLMN. N1 of the PLMN (N1 for PLMN) is an interface between the UE and the PLMN AMF, indicating that the UE sends information to the PLMN AMF using the N1 interface between the UE and the PLMN AMF. The NPN N1(N1 for NPN) is an interface between the UE and the SNPN AMF, indicating that the UE transmits information to the SNPN AMF using an N1 interface between the UE and the SNPN AMF.

Besides the interworking between SNPN and PLMN is realized through N3IWF architecture, the interworking between SNPN and PLMN is also currently supported through roaming architecture. As shown in fig. 4B, in the roaming architecture, the UE signs up on the PLMN, selects the SNPN ID using the public network subscription of the PLMN within the coverage of the SNPN, accesses the SNPN using the public network subscription, registers on the PLMN through the SNPN, and then may establish a PDU session within the SNPN. The SNPN determines a roaming mode of the PDU session, such as a Local Breakout Out (LBO) mode or a Home Routed (HR) mode, according to the public network subscription of the UE. In fig. 4B, the part to the right of the middle vertical line belongs to PLMN, and the part to the left of the vertical line belongs to SNPN. In this way, the UE performs 3GPP access registration with the PLMN through SNPN.

As can be seen from the above description, the PLMN can simultaneously support interworking with SNPN in the manner of fig. 4A or fig. 4B. As shown in fig. 5, PLMN1 supports interworking with SNPN1 using a roaming scheme and also supports interworking with SNPN1 using an N3IWF scheme. For example, the UE is registered to the PLMN1 through roaming at SNPN1 using subscription of PLMN1, that is, as shown in fig. 5, the UE is registered to the PLMN1 within SNPN1 through Security Edge Protection Proxy (SEPP)/inter PLMN user plane security gateway (IPUPS) using subscription of PLMN 1. And subsequently, the UE may also re-register with the PLMN1 by way of the SNPN1 using N3 IWF. After the UE is registered to the PLMN1 in the roaming manner, if the UE is registered to the PLMN1 in another manner, the process is a redundant registration process, and the registration in the N3IWF manner is complex, and requires a lot of resources. Moreover, the use of the N3IWF may not control the service of the UE, which may cause the waste of private network resources and may also lose control of the service access of the UE.

In view of this, the technical solutions of the embodiments of the present application are provided. In this embodiment, a first core network device receives a request message from a terminal device, and the terminal device requests to register to a first network through an SNPN. If the terminal equipment is determined to be registered to the first network through the SNPN, the first core network equipment rejects the registration of the terminal equipment, so that the redundant registration process of the terminal equipment is reduced, and the terminal equipment does not need to perform the registration process, so that the UE can be prevented from abusing private network resources or accessing public network services.

The technical solution provided in the embodiment of the present application may be applied to a 5G system, such as an NR system, or may also be applied to a next generation mobile communication system or other similar communication systems, which is not limited specifically.

The method provided by the embodiment of the application is described below with reference to the accompanying drawings.

The embodiment of the present application provides a first communication method, please refer to fig. 6, which is a flowchart of the method. It should be noted that, when various embodiments are described herein, the network architecture shown in fig. 5 is taken as an example.

For convenience of introduction, in the embodiments to be described below, the method is performed as an example by a network device and a terminal device. The UE according to various embodiments herein is a UE in the network architecture shown in fig. 5. The first network described in the embodiments herein is a home network of the UE, for example, PLMN1 in the architecture shown in fig. 5, or the first network may also be an SNPN, for example, another SNPN different from SNPN1, and the embodiments herein mainly take the case that the first network is a PLMN as an example. Various embodiments herein relate to a first core network device, a second core network device, a third core network device, and a first network device, for example, a UDM in PLMN1 in the architecture shown in fig. 5, which may be abbreviated as UDM; the second core network device is, for example, an AMF in the PLMN1 in the architecture shown in fig. 5, which may be referred to as a PLMN AMF for short; the third core network device is, for example, an AMF in the SNPN1 in the architecture shown in fig. 5, which may be referred to as SNPN AMF for short; the first network device is, for example, an N3IWF, which may be referred to as N3IWF for short, in the PLMN1 in the architecture shown in fig. 5.

S601, UE sends a registration request message to SNPN AMF, and SNPN AMF receives the registration request message from UE. To distinguish from other registration request messages, the registration request message is referred to as registration request message 1, for example.

In the registration request message 1, a subscription hidden identifier (SUCI) or a subscription permanent identifier (SUPI) of the UE may be included, and an initial registration type may also be included. The initial registration type may indicate that this registration of the UE is a first registration or an initial registration.

In addition, the SNPN RAN may also transmit an SNPN ID to the SNPN AMF, which receives an SNPN identification, such as an SNPN identity number (ID), from the SNPN RAN, or other information indicating the SNPN. The SNPN is the SNPN where the UE is currently located. The SNPN ID includes, for example, a PLMN ID and a NID.

S602, SNPN AMF sends Nudm _ UECM _ Registration request message to UDM, and UDM receives Nudm _ UECM _ Registration request message from SNPN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 2, or as a second request message.

In the registration request message 2, the SUPI of the UE, the initial registration type, the ID of the SNPN AMF, and the 3GPP access type (3GPP access type) may be included. In addition, the registration request message 2 may further include SNPN information, which includes, for example, an SNPN identifier, or an SNPN access mode (SNPN access mode) indication, or both an SNPN identifier and an SNPN access mode indication. The SNPN access mode indication may indicate that the UE enables the SNPN access mode, and accesses the SNPN through the Uu air interface. That is, the SNPN AMF may transmit information of the SNPN currently accessed by the UE to the UDM.

S603, the UDM records the SNPN AMF context of the UE.

Herein, the SNPN AMF context of the UE may also be referred to as a registration context of the UE for short. The registration context of the UE includes information of SNPN and may include information of ID of SNPN AMF and 3GPP access type. If the UDM detects that the UE has an AMF context of a non-3GPP access type in another SNPN, i.e. the UE moves from another SNPN to the current SNPN, the UDM may de-register the AMF context of the non-3GPP access type in the other SNPN, i.e. the UDM deletes the AMF context of the non-3GPP access type, or it is understood that the UDM may de-register the UE with the other SNPN.

S604, the UDM sends a Nudm _ UECM _ Registration response message to the SNPN AMF, and the SNPN AMF receives the Nudm _ UECM _ Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 2, or a response message referred to as a Registration request message 2, or a second response message. The registration response message 2 may indicate that the SNPN AMF successfully registered to provide service for the UE.

S605, the SNPN AMF sends a registration response message to the UE, and the UE receives the registration response message from the SNPN AMF. In order to distinguish from other registration response messages, the registration response message is referred to as registration response message 1, or a response message referred to as registration request message 1, for example. The registration response message 1 may indicate that the UE successfully registered with the PLMN.

After performing S601 to S605, the UE is roaming registered with the PLMN by accessing the SNPN 1. After receiving the registration response message 1, the UE may establish a PDU session at SNPN1 to perform a corresponding service.

S606, the UE sends a registration request message to the PLMN AMF through the N3IWF, and the PLMN AMF receives the registration request message from the UE through the N3 IWF. The registration request message may be for the UE to request registration with the PLMN. It can be seen that after the UE is registered to the PLMN in the roaming manner, the UE can establish a connection to the PLMN N3IWF through the PDU session of SNPN1, and then request to register to the PLMN again in the N3 IWF.

The UE establishes IPsec connection with N3IWF through PDU session established in SNPN, and then sends registration request message 3 to N3IWF through the IPsec connection, after N3IWF receives the registration request message 3, N2 message is sent to PLMN AMF, and N2 message carries the registration request message 3. For example, the N2 message may also be referred to as a third request message, or registration request message 4. In addition, the registration request message 3 may also be referred to as a fourth request message. The registration request message 3 may include the SUPI or SUCI of the UE and include an initial registration type. In addition, the N2 message may also include a PLMN ID.

Optionally, the registration request message 3 may further include the SNPN information, so that the UE sends the SNPN information to the PLMN AMF through the registration request message 3, and the PLMN AMF is not required to obtain the SNPN information through other approaches, which is beneficial to simplifying the registration process.

Alternatively, the registration request message 3 does not include the SNPN information, and the PLMN AMF may obtain the SNPN information from the N3 IWF. For example, the N3IWF determines the SNPN information accessed by the UE and transmits the SNPN information to the PLMN AMF through an N2 message, so that the PLMN AMF receives the SNPN information from the N3 IWF. In this way, the UE does not need to carry SNPN information in the registration request message 3, and the information amount of the registration request message 3 can be reduced.

The N3IWF may determine the SNPN information in different ways. For example, the correspondence between SNPN and tunnel, or the correspondence between SNPN ID and tunnel, for example, the tunnel between UE and N3IWF, or the tunnel between SNPN UPF and N3IWF, is pre-configured (or protocol-specified), which is also known to UE or UPF, for example, SNPN ID and tunnel one-to-one. Then when the UE sends the registration request message 3, or when the UPF forwards the registration request message 3 of the UE, the N3IWF may select the tunnel corresponding to the SNPN accessed by the UE to send, and according to the tunnel receiving the registration request message 3, the N3IWF may determine the SNPN information accessed by the UE.

For another example, a correspondence relationship between the IP addresses of SNPN and SNPN UPF is configured (or defined) in advance, or a correspondence relationship between the IP addresses of SNPN ID and SNPN UPF is configured (or defined) in advance, for example, the SNPN ID and the IP address of SNPN UPF are in one-to-one correspondence. Then, when the N3IWF receives the registration request message 3 from the SNPN UPF, it can determine the SNPN information accessed by the UE according to the detected IP address of the SNPN UPF.

As another example, a correspondence relationship between SNPN and N3IWF is pre-configured (or protocol-specified), or a correspondence relationship between SNPN ID and N3IWF ID is pre-configured (or protocol-specified), which is also known to the UE, for example, SNPN ID and N3IWF ID are one-to-one. Then the UE may select the N3IWF corresponding to the SNPN accessed by the UE when sending the registration request message 3, and if the corresponding N3IWF receives the registration request message 3 from the UE, it can determine that the SNPN accessed by the UE is the SNPN corresponding to the N3 IWF.

As the above several ways are only examples, the N3IWF may also determine the SNPN information by other ways, which is not limited in this embodiment of the present application.

S607, the PLMN AMF sends a numm UECM Registration request message to the UDM, and the UDM receives the numm UECM Registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 5, or as a first request message.

The registration request message 5 may be used for PLMN AMF requesting to provide service to the UE. The registration request message 5 may include the SUPI of the UE, the initial registration type, and PLMN AMF ID and the non-3GPP access type. In addition, the registration request message 5 may also include information of SNPN, i.e. the PLMN AMF may send the obtained information of SNPN to the UDM.

S608, the UDM determines that the UE has registered with the PLMN through the SNPN.

The UDM may obtain information of the SNPN comprised by the registration request message 5. In addition, the UDM may also query the registered context of the UE that is recorded, i.e. query the SNPN AMF context of the UE. If the SNPN AMF context of the UE includes the information of the SNPN and the initial registration type, and the SNPN corresponding to the information of the SNPN included in the registration request message 5 is the same SNPN, the UDM may determine that the UE has registered to the PLMN through the SNPN. To avoid the UE performing multiple registrations on the same PLMN, the UDM determines to reject the registration request served by the PLMN AMF for the UE, i.e. to reject the registration requested by the registration request message 5.

S609, the UDM sends a Nudm _ UECM _ Registration response message to the PLMN AMF, and the PLMN AMF receives the Nudm _ UECM _ Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 3, or a response message referred to as a Registration request message 5, or a first response message.

The registration response message 3 may include a failure result indication, which may indicate a rejection of the registration request by the PLMN AMF to serve the UE. Optionally, the registration response message 3 may further include a cause value, which may indicate a reason for rejecting the registration, for example, the reason indicated by the cause value is that the UE has registered to the PLMN through SNPN.

S610, the PLMN AMF sends a registration rejection message to the UE, and the UE receives the registration rejection message from the PLMN AMF. The registration reject message may also be referred to as registration response message 4, or as a third response message, or as a response message of registration request message 3, or as a response message of registration request message 4 (i.e., N2 message in S606).

The registration reject message may include a cause value indicating a cause that the UE has registered with the PLMN through SNPN. After receiving the registration reject message, the UE may no longer request registration to the PLMN by means of the N3 IWF.

In the embodiment of the application, the UDM may record the SNPN information accessed by the UE when the UE performs the first 3GPP registration on the PLMN through the SNPN, so that the UDM may reject the non-3GPP registration of the UE when the UE performs the second non-3GPP registration on the PLMN through the SNPN, and prevent the UE from registering on the PLMN again through the same SNPN. Therefore, the resource consumed by the second registration process of the UE can be saved. And because the UE can not be registered to the PLMN through the N3IWF mode, the control of the UE accessing the public network service through the SNPN is realized.

Next, a second communication method is provided in the embodiment of the present application, please refer to fig. 7, which is a flowchart of the method.

S701, UE sends a registration request message to SNPN AMF, and SNPN AMF receives the registration request message from UE. To distinguish from other registration request messages, the registration request message is referred to as registration request message 1, for example.

For more about S701, reference may be made to the description of S601 in the embodiment shown in fig. 6.

S702, SNPN AMF sends Nudm _ UECM _ Registration request message to UDM, and UDM receives Nudm _ UECM _ Registration request message from SNPN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 2, or as a second request message.

For more about S702, reference may be made to the description of S602 in the embodiment shown in fig. 6.

S703, the UDM records SNPN AMF context of the UE.

For more about S703, reference may be made to the description of S603 in the embodiment shown in fig. 6.

S704, the UDM sends a Nudm _ UECM _ Registration response message to the SNPN AMF, and the SNPN AMF receives the Nudm _ UECM _ Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 2, or a response message referred to as a Registration request message 2, or a second response message. The registration response message 2 may indicate that the SNPN AMF successfully registered to provide service for the UE.

S705, the SNPN AMF sends a registration response message to the UE, and the UE receives the registration response message from the SNPN AMF. In order to distinguish from other registration response messages, the registration response message is referred to as registration response message 1, or a response message referred to as registration request message 1, for example. The registration response message 1 may indicate that the UE successfully registered with the PLMN.

For more about S705, reference may be made to the description of S605 in the embodiment shown in fig. 6.

S706, the UE sends a registration request message to the PLMN AMF through the N3IWF, and the PLMN AMF receives the registration request message from the UE through the N3 IWF. The registration request message may be for the UE to request registration with the PLMN. It can be seen that after the UE is registered to the PLMN in a roaming manner, the UE can establish a connection to the PLMN N3IWF through the PDU session of SNPN1, and then request to register to the PLMN again through the N3 IWF.

The UE establishes IPsec connection with N3IWF through PDU session established in SNPN, and then sends registration request message 3 to N3IWF through the IPsec connection, after N3IWF receives the registration request message 3, N2 message is sent to PLMN AMF, and N2 message carries the registration request message 3. For example, the N2 message may also be referred to as a third request message, or registration request message 4. The registration request message 3 may also be referred to as a fourth request message.

For more about S706, reference may be made to the description of S606 in the embodiment shown in fig. 6.

S707, the PLMN AMF sends a Nudm _ UECM _ Registration request message to the UDM, and the UDM receives the Nudm _ UECM _ Registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 5, or as a first request message.

For more about S707, reference may be made to the description of S607 in the embodiment shown in fig. 6.

S708, the UDM determines that the UE has registered with the PLMN through the SNPN.

The UDM may obtain information of the SNPN comprised by the registration request message 5. In addition, the UDM may also query the registered context of the UE that is recorded, i.e. query the SNPN AMF context of the UE. If the SNPN AMF context of the UE includes the information of the SNPN and the initial registration type, and the SNPN corresponding to the information of the SNPN included in the registration request message 5 is the same SNPN, the UDM may determine that the UE has registered to the PLMN through the SNPN.

S709, the UDM sends a numdm _ UECM _ Registration response message to the PLMN AMF, and the PLMN AMF receives the numdm _ UECM _ Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 3, or a response message referred to as a Registration request message 5, or a first response message.

The registration response message 3 may implicitly indicate that the UE has registered with the current PLMN through the SNPN. For example, the registration response message 3 includes the registration context of the UE (i.e., the SNPN AMF context of the UE), which is equivalent to an implicit indication that the UE has registered with the PLMN through the SNPN.

Alternatively, the registration response message 3 may also explicitly indicate that the UE has registered with the current PLMN through SNPN. For example, the registration response message 3 includes indication information that may indicate that the UE has registered with the PLMN through SNPN. Compared with the registration context of the UE, the amount of the indication information is smaller, which helps to reduce signaling overhead.

S710, the PLMN AMF determines to reject the registration request of the UE.

After receiving the registration response message 3, the PLMN AMF may determine to reject the non-3GPP registration of the UE this time. For example, the PLMN AMF may determine to reject the registration of the UE according to the SNPN information, the initial registration type, and the registration context of the UE; alternatively, if the registration response message 3 includes the indication information, the PLMN AMF may determine that the UE has already registered to the current PLMN through the SNPN according to the indication information, thereby rejecting the registration of the UE.

S711, the PLMN AMF sends a numm _ UECM _ registration request message to the UDM, and the UDM receives the numm _ UECM _ registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ registration request message is also referred to as a de-registration request message, or a fourth request message.

The deregistration request message may be used to request the UDM to deregister the PLMN AMF with the UDM. That is, the PLMN AMF sends a registration request message 5 to the UDM in S707, and the deregistration request message is used to deregister the registration of the PLMN AMF. In the embodiment of the present application, the PLMN AMF decides to reject the registration request of the UE, but not the UDM decides to reject the registration request of the UE, so that the UDM may not actively perform de-registration for the registration of the PLMN AMF in the UDM. Thus, the PLMN AMF may also request the UDM to de-register for registration of the PLMN AMF with the UDM if it rejects the registration request of the UE. The fourth request message may include a PLMN ID, a PLMN AMF ID, a SUPI of the UE, and an N3GPP Access Type.

S712, the UDM deletes the registration context corresponding to the SNPN from the context of the UE by the PLMN AMF. I.e. the UDM de-registers this registration of the PLMN AMF.

S713, the PLMN AMF sends a registration rejection message to the UE, and the UE receives the registration rejection message from the PLMN AMF. The registration reject message may also be referred to as registration response message 4, or as a third response message, or as a response message of registration request message 3, or as a response message of registration request message 4 (i.e., N2 message in S706).

The registration response message 4 may include a cause value indicating the reason that the UE has registered with the PLMN through SNPN. After receiving the registration reject message, the UE may no longer request registration to the PLMN by means of the N3 IWF.

In the embodiment of the application, the UDM may record SNPN information accessed by the UE when the UE performs the first 3GPP registration on the PLMN through the SNPN, so that the UDM may send corresponding information to the PLMN AMF when the UE performs the second non-3GPP registration on the PLMN through the SNPN, and the PLMN AMF may reject the non-3GPP registration of the UE, thereby preventing the UE from registering on the PLMN again through the same SNPN. Therefore, the resource consumed by the second registration process of the UE can be saved. And because the UE can not register to the PLMN through the N3IWF mode, the control of the UE accessing the public network service through the SNPN is realized.

Next, another problem is considered. As shown in fig. 8, PLMN1 supports interworking with SNPN1 using roaming. For example, the UE is roaming registered with PLMN1 at SNPN1 using the subscription of PLMN 1. And subsequently, the UE may move, e.g., the UE moves to SNPN 2. After the UE moves to SNPN2, the UE may access SNPN2 and request registration to the PLMN through the N3IWF because the UE is also a subscriber to SNPN 2. At this time, if the PLMN rejects the registration of the UE because the UE has previously registered to the PLMN through SNPN1, the UE may not operate normally. Therefore, the embodiment of the present application proposes that, in a case where the UE moves, the PLMN should not reject the re-registration process of the UE. The solutions provided in the embodiments of the present application are described below by corresponding embodiments.

The third communication method is provided in the embodiment of the present application, please refer to fig. 9, which is a flowchart of the method.

First, the UE uses the PLMN subscription to register to the PLMN in a roaming manner in the SNPN1, and for this part, reference may be made to the related descriptions of S601 to S605 in the embodiment shown in fig. 6. After registration, the UE moves to a second SNPN, such as SNPN2 shown in fig. 8.

S901, the UE registers with SNPN2 using SNPN2 signup. The process of registering the UE to the SNPN2 is not described in detail.

S902, the UE establishes a PDU session in SNPN2, which is not described herein again.

S903, UE sends registration request message to PLMN AMF through N3IWF, PLMN AMF receives registration request message from UE through N3 IWF. The registration request message may be for the UE to request registration with the PLMN. It can be seen that the UE can access the new SNPN after moving, and then request to register to the PLMN again through the PLMN N3 IWF.

The UE establishes IPsec connection with the N3IWF through a PDU session established in SNPN2, and then sends a registration request message 3 to the N3IWF through the IPsec connection, after receiving the registration request message 3, the N3IWF sends a N2 message to PLMN AMF, and the N2 message carries the registration request message 3. For example, the registration request message 3 may also be referred to as a third request message, or as a registration request message 4. The registration request message 3 may include SUPI or SUCI of the UE and include a mobile registration type (mobility registration type). In addition, the N2 message may also include a PLMN ID. The mobile registration type may indicate that the registration request message 3 is a registration request triggered by the UE moving, or that the current registration is triggered by the UE moving.

Optionally, the registration request message 3 may also include information of SNPN 2. The UE sends the information of SNPN2 to the PLMN AMF through the registration request message 3, and the PLMN AMF does not need to obtain the information of SNPN2 through other ways, which is beneficial to simplifying the registration process.

Alternatively, the registration request message 3 does not include the information of SNPN2, and the PLMN AMF may obtain the information of SNPN2 from the N3 IWF. For example, the N3IWF determines information of SNPN2 accessed by the UE and transmits the information of SNPN2 to the PLMN AMF through an N2 message, so that the PLMN AMF receives the information of SNPN2 from the N3 IWF. In this way, the UE does not need to carry the SNPN2 information in the registration request message 3, and the information amount of the registration request message 3 can be reduced.

For more details about S903, for example, how the N3IWF determines the information of SNPN2, reference may be made to the description of S606 in the embodiment shown in fig. 6.

S904, the PLMN AMF sends a numdm _ UECM _ Registration request message to the UDM, which receives the numdm _ UECM _ Registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 5, or as a first request message.

The registration request message 5 may be used for PLMN AMF requesting to provide service to the UE. The registration request message 5 may include the SUPI of the UE and include PLMN AMF ID and the non-3GPP access type. In addition, the registration request message 5 may also include information of SNPN2 and the mobile registration type.

S905, the UDM determines to receive the PLMN AMF to provide service for the UE.

The UDM determines that the UE is a post-mobility registration based on the mobile registration type. And the UDM determines that the UE was last registered to the PLMN through SNPN1 according to the information of SNPN2 and the recorded SNPN AMF context of the UE, the UDM determines to accept the PLMN AMF to provide service to the UE.

In addition, since the UDM accepts the PLMN AMF to serve the UE, the UDM may deregister the UE with the PLMN via SNPN1 to avoid the UE registering twice in the PLMN. For example, the UDM deletes the registration context corresponding to SNPN1 for AMF in SNPN1, i.e. deletes the context information of SNPN1AMF from the context of the UE, thereby implementing de-registration of the UE with the registration of SNPN1 on the PLMN.

S906, the UDM sends a numdm _ UECM _ Registration response message to the PLMN AMF, which receives the numdm _ UECM _ Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 3, or a response message referred to as a Registration request message 5, or a first response message. The first response message may indicate that the PLMN AMF successfully registered to provide service for the UE.

S907, the PLMN AMF sends a registration response message to the UE, and the UE receives the registration response message from the PLMN AMF. This registration response message may also be referred to as registration response message 4, or as a third response message, or as a response message of registration request message 3, or as a response message of registration request message 4 (i.e., N2 message in S903). The registration response message 4 may indicate that the UE successfully registered with the PLMN, i.e., that the UE successfully registered with the PLMN through SNPN 2.

In the embodiment of the application, in a scenario that the UE is allowed to move from SNPN1 to SNPN2, the PLMN can accept non-3GPP registration of the UE on the PLMN through SNPN2, so that the UE can work normally. And the UE may be deregistered with the 3GPP registration of the PLMN via SNPN1 to avoid the UE registering twice within the PLMN.

Next, a fourth communication method is provided in the present embodiment, please refer to fig. 10, which is a flowchart of the method.

S1001, the UE registers with SNPN2 using SNPN2 signature. The process of registering the UE to the SNPN2 is not described in detail.

S1002, the UE establishes a PDU session in SNPN2, which is not described herein.

S1003, UE sends a registration request message to PLMN AMF through N3IWF, and PLMN AMF receives the registration request message from UE through N3 IWF. The registration request message may be for the UE to request registration with the PLMN. It can be seen that the UE can access the new SNPN after moving, and then request to register to the PLMN again through the PLMN N3 IWF.

For more of S1003, reference may be made to the description for S903 in the embodiment shown in fig. 9.

S1004, the PLMN AMF sends a numm _ UECM _ Registration request message to the UDM, and the UDM receives the numm _ UECM _ Registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ Registration request message may also be referred to as a Registration request message 5, or as a first request message.

For more about S1004, reference may be made to the description of S904 in the embodiment shown in fig. 9.

S1005, the UDM sends a numm UECM Registration response message to the PLMN AMF, and the PLMN AMF receives the numm UECM Registration response message from the UDM. For simplicity, the numm UECM Registration response message may also be referred to as a Registration response message 3, or a response message referred to as a Registration request message 5, or a first response message. The first response message may indicate that the PLMN AMF successfully registered to provide service for the UE. The UDM determines that the UE is registered after moving according to the mobile registration type, and determines that the UE is registered to the PLMN through SNPN1 last time according to the information of SNPN2 and the recorded SNPN AMF context of the UE, then the UDM determines to accept the PLMN AMF to serve the UE, and carries the registration context of the UE (i.e., the SNPN AMF context of the UE) in the first response message, and the registration context of the UE may implicitly indicate that the PLMN AMF is successfully registered to serve the UE; or the UDM may also carry indication information in the first response message, where the indication information may indicate that the UE has registered to the PLMN through SNPN, or indicate that the PLMN AMF successfully registers to provide a service for the UE.

S1006, the PLMN AMF determines to accept the registration of the UE this time.

The PLMN AMF determines that the UE is a post-mobility registration according to the mobile registration type. And the PLMN AMF determines to accept the registration of the UE on the PLMN this time according to the information of the SNPN2, the mobile registration type and the registration context of the UE in the first response message.

S1007, the PLMN AMF sends a numm _ UECM _ registration request message to the UDM, and the UDM receives the numm _ UECM _ registration request message from the PLMN AMF. For simplicity, the numm _ UECM _ registration request message is also referred to as a de-registration request message, or a second request message.

The deregistration request message may request (or, stated differently, indicate) deregistration of the UE for registration within the PLMN via SNPN 1. In the embodiment shown in fig. 9, it is determined by the UDM to accept the PLMN AMF to serve the UE accessing SNPN2, so the UDM can de-register the registration of SNPN1AMF by itself without PLMN AMF notification. In the embodiment of the application, the PLMN AMF determines to accept the registration of the UE on the PLMN through accessing the SNPN2, so the PLMN AMF may also request the UDM to perform de-registration on the registration of the SNPN1 AMF. The de-registration request message may include a PLMN ID, a PLMN AMF ID, a SUPI of the UE, and a 3GPP Access Type.

S1008, UDM deletes the registration context corresponding to SNPN1 for AMF within SNPN 1. Illustratively, the UDM removes the context information of the SNPN1AMF from the context of the UE, thereby enabling de-registration of the UE with registration of the PLMN through the SNPN 1.

S1009, the PLMN AMF sends a registration response message to the UE, and the UE receives the registration response message from the PLMN AMF. The registration response message may also be referred to as registration response message 4, or as a third response message, or as a response message of registration request message 3, or as a response message of registration request message 4 (i.e., N2 message in S1003). The registration response message 4 may indicate that the UE successfully registered with the PLMN, i.e., that the UE successfully registered with the PLMN through SNPN 2.

Based on the same inventive concept, as shown in fig. 11, a schematic diagram of an apparatus provided by the present application is shown, where the apparatus may be a first core network device, a second core network device, a first network device, or a chip. When the apparatus is a first core network device or chip, the apparatus 1100 may be configured to perform the operations performed by the PLMN UDM in the embodiment shown in fig. 6, the embodiment shown in fig. 7, the embodiment shown in fig. 9, or the embodiment shown in fig. 10. When the apparatus is a second core network device or chip, the apparatus 1100 may be used to perform the operations performed by the PLMN AMF in the embodiment shown in fig. 6, the embodiment shown in fig. 7, the embodiment shown in fig. 9, or the embodiment shown in fig. 10. When the apparatus is a first network device or chip, the apparatus 1100 may be used to perform the operations performed by the N3IWF in the embodiment shown in fig. 6, the embodiment shown in fig. 7, the embodiment shown in fig. 9, or the embodiment shown in fig. 10.

The apparatus 1100 includes at least one processor 1101, a communication link 1102, and at least one communication interface 1104. As an alternative embodiment, the apparatus 1100 may further include a memory 1103. The memory 1103 is indicated by a dashed box in fig. 11 because it is not a functional module that is necessarily included, but only an optionally included functional module.

The processor 1101 may comprise a general purpose Central Processing Unit (CPU), microprocessor, Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to control the execution of programs in accordance with the teachings of the present application.

The communication link 1102 may include a path for communicating information between the aforementioned components.

Communication interface 1104, which may be any transceiver or other communication device for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), wired access network, etc.

The memory 1103 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 1103 may be separate and coupled to the processor 1101 by a communication line 1102. Alternatively, the memory 1103 may be integrated with the processor 1101.

The memory 1103 is used for storing computer-executable instructions for executing the embodiments of the present application, and is controlled by the processor 1101. The processor 1101 is configured to execute computer-executable instructions stored in the memory 1103, so as to implement the communication method provided by the above-mentioned embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 1101 may include one or more CPUs such as CPU0 and CPU1 in fig. 11 for one embodiment.

In particular implementations, apparatus 1100 may include multiple processors, such as processor 1101 and processor 1108 of FIG. 11, for example, as an example. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

When the apparatus shown in fig. 11 is a chip, for example, the apparatus may be a chip of a first core network device, a chip of a second core network device, or a chip of a first network device, and the chip includes a processor 1101 (which may also include the processor 1108), a communication line 1102, a memory 1103, and a communication interface 1104. In particular, communication interface 1104 may be an input interface, pin or circuit, or the like. The memory 1103 may be a register, cache, or the like. The processor 1101 and the processor 1108 may be a general purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of programs for the communication method of any of the embodiments described above.

In the embodiment of the present application, functional modules of the apparatus may be divided according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. For example, in the case of dividing each functional module by corresponding functions, fig. 12 shows a schematic diagram of an apparatus 1200, where the apparatus may be a first core network device, or a second core network device, or a first network device, or a chip in the first core network device, or a chip in the second core network device, or a chip in the first network device in the foregoing embodiment. The apparatus 1200 includes a transmitting unit 1201, a processing unit 1202, and a receiving unit 1203.

In an embodiment, when the apparatus 1200 is the first core network device or the chip of the first core network device in the above-described embodiment shown in fig. 6 or the embodiment shown in fig. 7, then:

a receiving unit 1203, configured to receive a first request message from a second core network device, where the first request message is used for the second core network device to request to provide a service for a terminal device, where the first request message includes an initial registration type and information of a non-public network to which the terminal device accesses, where the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device, and the apparatus 1200 is located in a first network, where the first network is a home network of the terminal device;

a processing unit 1202 for determining that the terminal device has registered with the first network through the non-public network;

a sending unit 1201, configured to send a first response message to a second core network device, where the first response message includes a failure result indication, or includes a registration context of the terminal device, or includes indication information used to indicate that the terminal device has registered to the first network through the non-public network.

As an optional implementation, the information of the non-public network includes an identification of the non-public network, and/or a non-public network access mode indication.

As an optional implementation manner, the receiving unit 1203 is configured to receive a second request message from a third core network device, where the second request message is used for the third core network device to request to provide a service for a terminal device, and the second request message includes information of the non-public network. A processing unit 1202, configured to record a registration context of the terminal device, where the registration context of the terminal device includes information of the non-public network, and a sending unit 1201, configured to send a second response message to the third core network device, where the second response message is used to indicate that the third core network device is successfully registered to provide a service for the terminal device.

As an optional implementation, the processing unit 1202 is configured to determine that the terminal device has registered to the first network through the non-public network by: and determining that the terminal equipment is registered to the first network through the non-public network according to the initial registration type, the information of the non-public network and the recorded registration context of the terminal equipment.

As an optional implementation manner, the first response message further includes a cause value, and the cause value is used for indicating that the terminal device has registered to the first network through the non-public network.

As an optional implementation manner, the processing unit 1202 is further configured to delete the registration context of the second core network device corresponding to the non-public network; or, the receiving unit 1203 is further configured to receive a fourth request message from the second core network device, where the fourth request message is used to request the apparatus 1200 to perform de-registration on the registration of the second core network device in the apparatus 1200, and the processing unit 1202 is further used to delete the registration context of the second core network device corresponding to the non-public network.

In an embodiment, when the apparatus 1200 is the second core network device or the chip of the second core network device in the above-described embodiment shown in fig. 6 or the embodiment shown in fig. 7, then:

a receiving unit 1203, configured to receive, by a first network device, a third request message from a terminal device, where the third request message is used for the terminal device to request to register to the first network, and the apparatus 1200 is located in the first network, where the first network is a home network of the terminal device;

a processing unit 1202, configured to obtain information of a non-public network accessed by the terminal device;

a sending unit 1201, configured to send a first request message to a first core network device, where the first request message is used for the apparatus 1200 to request to provide a service for the terminal device, and the first request message includes an initial registration type and information of the non-public network, and the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device;

a receiving unit 1203, further configured to receive a first response message from a first core network device, where the first response message includes a failure result indication, or includes a registration context of the terminal device, or includes indication information used to indicate that the terminal device has registered to the first network through the non-public network;

a sending unit 1201, further configured to send a third response message, where the third response message is used to reject registration of the terminal device.

As an optional implementation manner, the processing unit 1202 is configured to obtain information of a non-public network accessed by the terminal device, including: obtaining information of the non-public network from the third request message; alternatively, information of the non-public network from the first network device is received by the receiving unit 1203.

As an optional implementation manner, the third response message further includes a cause value, and the cause value is used to indicate that the terminal device has registered to the first network through the non-public network.

As an optional implementation manner, the sending unit 1201 is further configured to send a fourth request message to the first core network device, where the fourth request message is used to request the first core network device to perform de-registration on the registration of the apparatus 1200 in the first core network device.

As an optional implementation manner, before the sending unit 1201 sends the third response message, the processing unit 1202 is further configured to determine to reject registration of the terminal device according to the first response message.

In an embodiment, when the apparatus 1200 is the first core network device or the chip of the first core network device in the above-described embodiment shown in fig. 9 or the embodiment shown in fig. 10, then:

a receiving unit 1203, configured to receive a first request message from a second core network device, where the first request message is used for the second core network device to request to provide a service for a terminal device, and the first request message further includes a mobile registration type and information of a second non-public network, where the mobile registration type is used to indicate that the first request message is a registration request triggered by the terminal device due to movement, the apparatus 1200 is located in a first network, and the first network is a home network of the terminal device;

a sending unit 1201, configured to send a first response message to the second core network device, where the first response message is used to indicate that the second core network device is successfully registered to provide a service for the terminal device.

As an optional implementation manner, the processing unit 1202 is configured to perform deregistration on registration of the terminal device in the first network through the first non-public network.

As an optional implementation manner, the processing unit 1202 is configured to perform deregistration on registration of the terminal device in the first network through the first non-public network by: deleting a registration context of a third core network device corresponding to the first non-public network; or, a second request message from the second core network device is received by the receiving unit 1203, where the second request message is used to instruct to deregister the terminal device in the first network through the first non-public network, and delete the registration context of the third core network device corresponding to the first non-public network.

As an optional implementation, the information of the second non-public network includes an identifier of the second non-public network, and/or a non-public network access mode indication.

As an optional implementation manner, the receiving unit 1203 is further configured to receive a second request message from the third core network device, where the second request message is used for the third core network device to request to provide a service for a terminal device, and the second request message includes information of the first non-public network; a processing unit 1202, further configured to record a registration context of the terminal device, where the registration context of the terminal device includes information of the first non-public network; and a sending unit 1201, further configured to send a second response message to the third core network device, where the second response message is used to indicate that the third core network device is successfully registered to provide a service for the terminal device.

As an optional implementation, the information of the first non-public network includes an identifier of the first non-public network, and/or a non-public network access mode indication.

As an optional implementation manner, the first response message includes a registration context of the terminal device.

As an optional implementation manner, the processing unit 1202 is further configured to determine, before the sending unit 1201 sends the first response message to the second core network device, that the second core network device is successfully registered to provide a service for the terminal device according to the mobile registration type, the information of the second non-public network, and the recorded registration context of the terminal device.

In an embodiment, when the apparatus 1200 is the second core network device or the chip of the second core network device in the above-described embodiment shown in fig. 9 or the embodiment shown in fig. 10, then:

a receiving unit 1203, configured to receive, by a first network device, a third request message from a terminal device, where the third request message is used for the terminal device to request registration to the first network, and the third request message further includes a mobile registration type, where the mobile registration type is used to indicate that the third request message is a registration request triggered by the terminal device due to movement, and the first network is a home network of the terminal device;

a sending unit 1201, configured to send a first request message to a first core network device, where the first request message is used for the apparatus 1200 to request to provide a service for the terminal device, and the first request message includes the mobile registration type and information of a second non-public network;

a receiving unit 1203, further configured to receive a first response message from the first core network device, where the first response message is used to indicate that the apparatus 1200 is successfully registered to provide a service for the terminal device;

a sending unit 1201, configured to send a third response message to the terminal device, where the third response message is used to indicate that the terminal device successfully registers to the first network.

As an optional implementation manner, the first response message further includes a registration context of the terminal device.

As an optional implementation manner, the processing unit 1202 is further configured to determine that the terminal device successfully registers to the first network according to the mobile registration type, the information of the second non-public network, and the registration context of the terminal device before the sending unit 1201 sends the third response message to the terminal device.

As an optional implementation manner, the sending unit 1201 is further configured to send a second request message to the first core network device, where the second request message is used to instruct to deregister the terminal device in the first network through the first non-public network.

In one embodiment, when the apparatus 1200 is the chip of the first network device of the above-described embodiment shown in fig. 6, embodiment shown in fig. 7, embodiment shown in fig. 9, or embodiment shown in fig. 10, then:

a receiving unit 1203, configured to receive a fourth request message from a terminal device, where the fourth request message is used for the terminal device to request to register to a first network, and the apparatus 1200 is located in the first network, where the first network is a home network of the terminal device;

a processing unit 1202, configured to determine information of a non-public network accessed by the terminal device;

a sending unit 1201, configured to send the information of the non-public network to a second core network device.

As an optional implementation manner, the processing unit 1202 is configured to determine information of a non-public network accessed by the terminal device, and determine the information of the non-public network accessed by the terminal device according to a correspondence between the non-public network and a tunnel or an IP address; or, determining the information of the non-public network accessed by the terminal device according to the corresponding relation between the non-public network and the first network device.

It should be understood that the apparatus 1200 may be used to implement the steps executed by the first core network device, the second core network device, or the first network device in the method according to the embodiment of the present application, and related features may refer to the foregoing description, which is not described herein again.

Specifically, the functions/implementation procedures of the sending unit 1201, the receiving unit 1203 and the processing unit 1202 in fig. 12 can be implemented by the processor 1101 in fig. 11 calling a computer stored in the memory 1103 to execute instructions. Alternatively, the function/implementation procedure of the processing unit 1202 in fig. 12 may be implemented by the processor 1101 in fig. 11 calling a computer executing instruction stored in the memory 1103, and the function/implementation procedures of the transmitting unit 1201 and the receiving unit 1203 in fig. 12 may be implemented by the communication interface 1104 in fig. 11.

Alternatively, when the apparatus 1100 is a chip or a circuit, the functions/implementation processes of the transmitting unit 1201 and the receiving unit 1203 may also be implemented by pins or circuits in the apparatus 1100. Alternatively, when the apparatus 1100 is a chip, the memory 1103 may be a storage unit within the chip, such as a register, a cache, and the like. Of course, when the apparatus 1100 is a first core network device, such as the UDM in the foregoing embodiment, the memory 1103 may also be a storage unit located outside the chip in the first core network device, which is not specifically limited in this embodiment of the present application. When the apparatus 1100 is a second core network device, the memory 1103 may also be a storage unit located outside the chip in the second core network device, which is not specifically limited in this embodiment of the present application. When the apparatus 1100 is a first network device, the memory 1103 may also be a storage unit located outside the chip in the first network device, which is not specifically limited in this embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The various illustrative logical units and circuits described in this embodiment of the application may be implemented or operated by general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

The steps of a method or algorithm described in the embodiments herein may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software cells may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be disposed in a terminal device. In the alternative, the processor and the storage medium may reside as discrete components in a terminal device.

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 the flowchart flow or flows and/or block diagram block or blocks.

Although the embodiments of the present application have been described in conjunction with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made thereto without departing from the spirit and scope of the embodiments of the present application. Accordingly, the present embodiments and figures are merely illustrative of the present embodiments as defined by the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present embodiments. It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the embodiments of the present application and their equivalents, the embodiments of the present application are intended to include such modifications and variations as well.

Claims

1. A method of communication, comprising:

a first core network device in a first network receives a first request message from a second core network device, where the first request message is used for the second core network device to request to provide a service for a terminal device, the first request message includes an initial registration type and information of a non-public network to which the terminal device accesses, the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device, and the first network is a home network of the terminal device;

the first core network device determines that the terminal device has registered with the first network through the non-public network;

the first core network device sends a first response message to a second core network device, wherein the first response message comprises a failure result indication, or comprises the registration context of the terminal device, or comprises indication information used for indicating that the terminal device is registered to the first network through the non-public network.

2. The method according to claim 1, wherein the information of the non-public network comprises an identification of the non-public network and/or a non-public network access mode indication.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the first core network device receives a second request message from a third core network device, where the second request message is used for the third core network device to request a service to be provided for a terminal device, and the second request message includes information of the non-public network;

the first core network equipment records the registration context of the terminal equipment, and the registration context of the terminal equipment comprises the information of the non-public network; and the number of the first and second groups,

and the first core network device sends a second response message to the third core network device, wherein the second response message is used for indicating that the third core network device is successfully registered to provide service for the terminal device.

4. The method of claim 3, wherein the first core network device determining that the terminal device has registered with the first network through the non-public network comprises:

5. A method according to any of claims 1 to 4, wherein the first response message further comprises a cause value indicating that the terminal device has registered with the first network via the non-public network.

6. The method according to any one of claims 1 to 5, further comprising:

the first core network equipment deletes the registration context of the second core network equipment corresponding to the non-public network; or the like, or, alternatively,

the first core network device receives a fourth request message from the second core network device, where the fourth request message is used to request the first core network device to de-register the registration of the second core network device in the first core network device;

and the first core network equipment deletes the registration context of the second core network equipment corresponding to the non-public network.

7. A method of communication, comprising:

a second core network device in a first network receives a third request message from a terminal device through a first network device, wherein the third request message is used for the terminal device to request to register to the first network, and the first network is a home network of the terminal device;

the second core network equipment acquires the information of the non-public network accessed by the terminal equipment;

the second core network device sends a first request message to a first core network device, where the first request message is used for the second core network device to request to provide a service for the terminal device, the first request message includes an initial registration type and information of the non-public network, and the initial registration type is used to indicate that the first request message is an initial registration request of the terminal device;

the second core network device receives a first response message from a first core network device, wherein the first response message comprises a failure result indication, or comprises a registration context of the terminal device, or comprises indication information used for indicating that the terminal device is registered to the first network through the non-public network;

and the second core network equipment sends a third response message, wherein the third response message is used for rejecting the registration of the terminal equipment.

8. The method according to claim 7, wherein the information of the non-public network comprises an identification of the non-public network and/or a non-public network access mode indication.

9. The method according to claim 7 or 8, wherein the obtaining, by the second core network device, information of a non-public network to which the terminal device accesses includes:

the second core network device obtains the information of the non-public network from the third request message; or the like, or, alternatively,

the second core network device receives information of the non-public network from the first network device.

10. The method according to any of claims 7 to 9, wherein the third response message further comprises a cause value indicating that the terminal device has registered with the first network via the non-public network.

11. The method according to any one of claims 7 to 10, further comprising:

the second core network device sends a fourth request message to the first core network device, where the fourth request message is used to request the first core network device to de-register the registration of the second core network device in the first core network device.

12. The method according to any of claims 7 to 11, wherein before the second core network device sends the third response message, the method further comprises:

and the second core network equipment determines to reject the registration of the terminal equipment according to the first response message.

13. A method of communication, comprising:

a first core network device in a first network receives a first request message from a second core network device, wherein the first request message is used for the second core network device to request to provide service for a terminal device, and the first request message also comprises a mobile registration type and information of a second non-public network, the mobile registration type is used for indicating that the first request message is a registration request triggered by the terminal device due to movement, and the first network is a home network of the terminal device;

and the first core network equipment sends a first response message to the second core network equipment, wherein the first response message is used for indicating the second core network equipment to be successfully registered to provide service for the terminal equipment.

14. The method of claim 13, further comprising:

and the first core network equipment deregisters the registration of the terminal equipment in the first network through the first non-public network.

15. The method of claim 14, wherein the first core network device deregisters the terminal device from registration with the first network via the first non-public network, comprising:

the first core network equipment deletes the registration context of a third core network equipment corresponding to the first non-public network; or the like, or, alternatively,

the first core network device receives a second request message from the second core network device, wherein the second request message is used for indicating that the terminal device is unregistered with the first network through a first non-public network;

and the first core network equipment deletes the registration context of the third core network equipment corresponding to the first non-public network.

16. The method according to any of claims 13 to 15, wherein the information of the second non-public network comprises an identity of the second non-public network and/or a non-public network access mode indication.

17. The method according to claim 14 or 15, characterized in that the method further comprises:

the first core network device receives a second request message from the third core network device, where the second request message is used for the third core network device to request to provide a service for a terminal device, and the second request message includes information of the first non-public network;

the first core network device records the registration context of the terminal device, and the registration context of the terminal device comprises the information of the first non-public network; and the number of the first and second groups,

18. The method according to claim 14, 15 or 17, wherein the information of the first non-public network comprises an identity of the first non-public network, and/or a non-public network access mode indication.

19. The method of claim 13, wherein the first response message comprises a registration context of the terminal device.

20. The method according to any one of claims 13 to 19, further comprising, before the first core network device sends the first response message to the second core network device:

21. A method of communication, comprising:

a second core network device in a first network receives a third request message from a terminal device through a first network device, wherein the third request message is used for the terminal device to request registration to the first network, the third request message further comprises a mobile registration type, the mobile registration type is used for indicating that the third request message is a registration request triggered by the terminal device due to movement, and the first network is a home network of the terminal device;

the second core network device sends a first request message to a first core network device, wherein the first request message is used for the second core network device to request to provide service for the terminal device, and the first request message comprises the mobile registration type and information of a second non-public network;

the second core network device receives a first response message from the first core network device, where the first response message is used to indicate that the second core network device is successfully registered to provide service for the terminal device;

and the second core network equipment sends a third response message to the terminal equipment, wherein the third response message is used for indicating that the terminal equipment is successfully registered to the first network.

22. The method according to claim 21, wherein the information of the second non-public network comprises an identity of the second non-public network, and/or a non-public network access mode indication.

23. The method according to claim 21 or 22, characterized in that the first response message further comprises a registration context of the terminal device.

24. The method of claim 23, wherein before the second core network device sends the third response message to the terminal device, the method further comprises:

and the second core network equipment determines that the terminal equipment is successfully registered to the first network according to the mobile registration type, the information of the second non-public network and the registration context of the terminal equipment.

25. The method according to claim 23 or 24, further comprising:

and the second core network equipment sends a second request message to the first core network equipment, wherein the second request message is used for indicating that the terminal equipment is unregistered with the first network through the first non-public network.

26. A method of communication, comprising:

a first network device in a first network receives a fourth request message from a terminal device, wherein the fourth request message is used for the terminal device to request to register to the first network, and the first network is a home network of the terminal device;

the first network equipment determines the information of a non-public network accessed by the terminal equipment;

and the first network equipment sends the information of the non-public network to second core network equipment.

27. The method of claim 26, wherein the determining, by the first network device, information of a non-public network to which the terminal device accesses comprises:

the first network equipment determines the information of the non-public network accessed by the terminal equipment according to the corresponding relation between the non-public network and the tunnel or the IP address; or the like, or, alternatively,

and the first network equipment determines the information of the non-public network accessed by the terminal equipment according to the corresponding relation between the non-public network and the first network equipment.

28. A communication device comprising a processor and a memory; the memory is for storing one or more computer programs that, when executed, cause the method of any of claims 1-6 to be performed, or cause the method of any of claims 7-12 to be performed, or cause the method of any of claims 13-20 to be performed, or cause the method of any of claims 21-25 to be performed, or cause the method of any of claims 26-27 to be performed.

29. A computer-readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6, or causes the computer to perform the method of any one of claims 7 to 12, or causes the computer to perform the method of any one of claims 13 to 20, or causes the computer to perform the method of any one of claims 21 to 25, or causes the computer to perform the method of any one of claims 26 to 27.