CN114423074A - A communication method and device - Google Patents

Abstract

The present application relates to a communication method and device. The first core network device in the first network receives the first request message from the second core network device, the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message includes the initial registration type and Information about the SNPN accessed by the terminal device. 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, where the first response message includes a failure result indication, or includes a registration context of the terminal device, or includes a message indicating that the terminal device has registered with the first network through the SNPN instruction information. The method provided by the embodiment of the present application reduces the redundant registration process of the terminal device, and because the terminal device does not need to perform this registration process, the resources consumed in the subsequent process are also reduced.

Description

A communication method and device

technical field

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

Background technique

Non-public network (NPN) is a non-public fifth generation mobile communication technology (the 5th generation, 5G) network, NPN can rely on the support of public land mobile network (PLMN) to achieve , or can be implemented without relying on PLMN support. For example, an independent SNPN (standalone NPN, SNPN) in the NPN can be implemented without relying on the support of the PLMN.

Currently, the SNPN can communicate with the PLMN through a non-3GPP interworking function (N3IWF) architecture. For example, the terminal device can register to the SNPN, and in the SNPN, the terminal device can select the N3IWF in the PLMN, so as to access the PLMN through the N3IWF, and then register in the PLMN, that is, the terminal device can access the N3IWF of the PLMN through the SNPN, thus completing the Registration with PLMN. In addition, in addition to the N3IWF architecture, the terminal equipment can also realize the intercommunication between the SNPN and the PLMN through roaming. For example, a terminal device subscribed to a PLMN can use the PLMN subscription configuration to select a corresponding SNPN, and register with the PLMN by accessing the SNPN.

It can be seen that the terminal device can register to the PLMN in two ways. There may be a situation. When the terminal device accesses the SNPN, it can register to the PLMN by roaming, and then register to the PLMN by N3IWF, which is equivalent to the terminal device. Register twice with PLMN via SNPN. After the terminal device registers to the PLMN through roaming, if it registers to the PLMN through other methods, it is a redundant registration process, and the registration through the N3IWF method is complicated and requires more resources.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a communication method and apparatus, which are used to save resources consumed by redundant subscription of terminal equipment.

In a first aspect, a first communication method is provided, and the method is, for example, executed by a first core network device, or executed by 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 includes: a first core network device in the first network receives a first request message from a second core network device, where the first request message is used by the second core network device to request to provide a service for a terminal device, and the The first request message includes the initial registration type and the information of the non-public network accessed by the terminal device, 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 request message is an initial registration request of the terminal device. A network is the 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 reports to the second core network The device sends a first response message, where the first response message includes a failure result indication, or includes the registration context of the terminal device, or includes a message indicating that the terminal device has registered to the first through the non-public network Network instructions.

In this embodiment of the present application, the first network is, for example, a PLMN, or a non-public network, or other networks. A non-public network is, for example, an SNPN. The first core network device receives the request message from the terminal device, the terminal device requests to register with the first network through the SNPN. If it is determined that the terminal device has registered with the first network through the SNPN, the first core network device will reject the current registration of the terminal device, or the first core network device will send the registration context of the terminal device to the second core network device or indication information, so that the second core network device can reject the current registration of the terminal device. In this way, the redundant registration process of the terminal device is reduced, and since the terminal device does not need to perform this registration process, the resources consumed in the subsequent process are also reduced.

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

The SNPN information includes, for example, an SNPN identifier, or an SNPN access mode indication, or an SNPN identifier and an SNPN access mode indication.

In an optional implementation manner, the method further includes: receiving, by the first core network device, a second request message from a third core network device, where the second request message is used for the third core network device The device requests to provide services for the terminal device, and the second request message includes the information of the non-public network; the first core network device records the registration context of the terminal device, and the registration context of the terminal device includes the non-public network. information of the 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 as the terminal Equipment provides services.

This is the last registration process of the terminal device, that is, through this registration, the terminal device has been registered to the first network. During the registration process, the first core network device can record the SNPN information of the terminal device, so that if the terminal device subsequently registers to the first network through the SNPN again, the first core network device can reject the registration of the terminal device.

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

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

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 SNPN information included in the first request message corresponds to the SNPN. 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, then the first core network device can determine that the terminal device has registered to the first core network device through the SNPN. a network. Through the records of the first core network device, the first core network device can be enabled to compare the SNPNs registered twice by the terminal device, thereby rejecting the dual registration of the terminal device.

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

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

In an optional implementation manner, the method further includes: deleting, by the first core network device, a registration context of the second core network device corresponding to the non-public network; or, the first core network device The 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 The registration is performed to de-register, 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 second core network device Information corresponding to this registration. Or, if the second core network device rejects the current registration of the terminal device, which means that the first core network device has no decision-making power, then the second core network device can request the first core network device to register the second core network device through the fourth request message. If the registration of the core network device in the first core network device is de-registered, the first core network device may delete the registration context of the second core network device corresponding to the SNPN. In this way, regardless of whether the first core network device can decide to reject the registration of the terminal device, the first core network device can delete the registration context of the second core network device corresponding to the SNPN, so as to save the storage space of the first core network device, and also It is avoided that the first core network device stores erroneous information.

In a second aspect, a second communication method is provided, and the method is executed by, for example, a second core network device, or a chip capable of implementing functions of the second core network device. In the 5G system, the second core network device is, for example, an AMF. The method includes: a second core network device in the first network receives a third request message from a terminal device through the first network device, where the third request message is used by the terminal device to request to register with the first network, The first network is the home network of the terminal device; the second core network device obtains information about the non-public network accessed by the terminal device; the second core network device sends the first core network device to the first core network device. a request message, the first request message is used by the second core network device to request to provide services for the terminal device, the first request message includes the initial registration type and the information of the non-public network, the initial The 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 the first core network device, where the first response message includes a failure result Indicate, or include the registration context of the terminal device, or include indication information for indicating that the terminal device has registered with the first network through the non-public network; the second core network device sends a third response message, the third response message is used to reject the registration of the terminal device.

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

In an optional implementation manner, the obtaining, by the second core network device, the information of the non-public network accessed by the terminal device includes: obtaining, by the second core network device, the information from the third request message. information of the non-public network; or, the second core network device receives the information of the non-public network from the first network device. The first network device is, for example, the N3IWF, or other network devices.

The terminal device can include the SNPN information in the third request message, and the second core network device can obtain the SNPN information from the third request message, and the acquisition method is relatively simple. Alternatively, the SNPN information can also be determined by the N3IWF and sent to the second core network device, then the terminal device does not need to determine the SNPN information, then the message sent by the terminal device to the N3IWF does not need to include the SNPN information, which helps save signaling overhead. .

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

In an optional implementation manner, 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 The core network device deregisters 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: the second core network device determines to reject the terminal according to the first response message Device registration.

Regarding the technical effects brought about by the second aspect or various optional embodiments, reference may be made to the introduction to the technical effects of the first aspect or corresponding embodiments.

In a third aspect, a third communication method is provided, and the method is performed by, for example, 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 includes: 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 by the second core network device to request to provide a service for a terminal device, and The first request message also includes information about a mobile registration type and 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 a terminal device due to movement, and the first network is the home network of the terminal device; the first core network device sends a first response message to the second core network device, where the first response message is used to instruct the second core network device to successfully register to provide the terminal device Serve.

In this embodiment of the present application, in a scenario where a terminal device is allowed to move from a first non-public network to a second non-public network, the first network can accept the terminal device's registration in the first network through the second non-public network, so that the terminal device can be registered in the first network through the second non-public network. works fine.

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

Since the first core network device has accepted the registration of the terminal device in the first network through the second SNPN, it can deregister the terminal device in the first network through the first SNPN, so as to prevent the terminal device from registering twice in the first network. .

In an optional implementation manner, the first core network device deregisters the registration of the terminal device in the first network through the first non-public network, including: deleting the first core network device The third core network device corresponds to the registration context of 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 for Instructing to de-register the 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 can 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 third core network device. The network device corresponds to the information registered this time. Or, if the second core network device accepts the current registration of the terminal device, which means that the first core network device has no decision-making power, then the second core network device can request the first core network device to request the third If the registration of the core network device in the first network is de-registered, the first core network device may delete the registration context of the third core network device corresponding to the first SNPN. In this way, regardless of whether the first core network device can decide to reject the registration of the terminal device, the first core network device can delete the registration context of the third core network device corresponding to the first SNPN, so as to save the storage space of the first core network device, It also prevents the first core network device from storing erroneous information, and also avoids double registration of the terminal device in the first network.

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

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

In an optional implementation manner, the method further includes: receiving, by the first core network device, a second request message from the third core network device, where the second request message is used for the third The core network device requests to provide services for the terminal device, and the second request message includes the information of the first non-public network; the first core network device records the registration context of the terminal device, the registration context of the terminal device including 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 instruct the third core network device Successfully registered to provide services for the terminal device.

This is the last registration process of the terminal device, that is, through this registration, the terminal device is registered to the first network through the first SNPN. During the registration process, the first core network device can record the information of the first SNPN, so that the first core network device can subsequently determine whether to accept the re-registration after the terminal device moves.

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

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

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

The first response message can indicate that the PLMN AMF has successfully registered to provide services for the UE. An indication method is an 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 can be Implicitly instructs the second core network device to successfully register to provide services for the terminal device. Alternatively, another indication method is an explicit indication. The first core network device may also carry indication information in the first response message, and the indication information may indicate that the terminal device has registered with the first network through the second SNPN, or indicate The second core network device is successfully registered to provide services for the terminal device. The information amount of the indication information is small, which can save signaling overhead.

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:

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

The first core network device determines that the terminal device is registered after moving according to the mobile registration type. However, 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. The first core network device can determine that the terminal device is registered through another SNPN after moving. to the first network, so the first core network device can determine that the second core network device has successfully registered to provide services for the terminal device, so that the terminal device can work normally after moving.

In a fourth aspect, a fourth communication method is provided, and the method is performed by, for example, a second core network device, or a chip capable of implementing functions of the second core network device. In the 5G system, the second core network device is, for example, an AMF. The method includes: a second core network device in the first network receives a third request message from a terminal device through the first network device, where the third request message is used by the terminal device to request to register with the first network, 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 registration request of the terminal device. home network; the second core network device sends a first request message to the first core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, the first request message The request message includes the mobile registration type and information of the 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 the The second core network device successfully registers to provide services for the terminal device; the second core network device sends a third response message to the terminal device, where the third response message is used to instruct the terminal device to successfully register with the terminal device. Describe the first network.

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

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

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

In an optional implementation manner, the method further includes: the second core network device sends a second request message to the first core network device, where the second request message is used to indicate that the terminal The device is deregistered through the registration of the first non-public network with the first network.

Regarding the technical effects brought by the fourth aspect or various optional embodiments, reference may be made to the introduction to the technical effects of the third aspect or corresponding embodiments.

In a fifth aspect, a fifth communication method is provided, and the method is executed by, for example, a first network device, or a chip capable of implementing functions of the first network device. In the 5G system, the first network device is, for example, the N3IWF. The method includes: a first network device in a first network receives a fourth request message from a terminal device, where the fourth request message is used by the terminal device to request to register with a first network, where the first network is the the home network of the terminal device; the first network device determines the information of the non-public network accessed by the terminal device; the first network device sends the information of the non-public network to the second core network device.

The SNPN information can be determined by the N3IWF and sent to the second core network device, then the terminal device does not need to determine the SNPN information, then the fourth request message sent by the terminal device to the N3IWF does not need to include the SNPN information, which helps to save signaling overhead .

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

For example, the corresponding relationship between the SNPN and the tunnel is pre-configured (or stipulated by the protocol), or the tunnel is, for example, the tunnel between the terminal device and the N3IWF, or the tunnel between the SNPN UPF and the N3IWF. It is also known to the device or UPF, eg SNPN corresponds to tunnel one-to-one. Then, when the UE sends the fourth request message, or when the UPF forwards the fourth request message of the terminal device, it can select the tunnel corresponding to the SNPN accessed by the terminal device to send, then the N3IWF can receive the fourth request message according to the tunnel. Determine the information of the SNPN accessed by the terminal device. For another example, the correspondence between the SNPN and the IP addresses of the SNPN UPF is pre-configured (or specified by the protocol), for example, the SNPN and the IP addresses of the 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 information of the fourth accessed SNPN according to the detected IP address of the SNP NUPF. For another example, the corresponding relationship between the SNPN and the N3IWF is pre-configured (or stipulated by the protocol), and the corresponding relationship is also known to the terminal device, for example, the SNPN and the N3IWF ID have a one-to-one correspondence. Then, when the terminal device sends the fourth request message, it can select the N3IWF corresponding to the SNPN accessed by the terminal device. If the corresponding N3IWF receives the fourth request message from the terminal device, it can determine that the SNPN accessed by the terminal device is The SNPN corresponding to the N3IWF. Alternatively, in addition to the above manner, the N3IWF may also determine the SNPN information in other manners, which are not limited in this embodiment of the present application.

In a sixth aspect, a communication apparatus is provided. 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 function of implementing each embodiment of any one of the first aspect, the second aspect, the third aspect, the fourth aspect, or the fifth aspect. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a seventh aspect, a communication apparatus is provided, including a processor and a communication interface. Optionally, a memory may also be included, or the communication device may not include a memory, and the memory may be located outside the communication device. The memory is used to store a computer program, and when the communication device runs, the processor executes the computer program stored in the memory, so that the communication device executes the first aspect or any optional implementation manner of the first aspect. The method executed by the first core network device, or to cause the apparatus to execute the method executed by the second core network device in the second aspect or any optional implementation manner of the second aspect, or to cause the device to execute the method. The apparatus executes the method executed by the first core network device in the third aspect or any optional implementation manner of the third aspect, or causes the apparatus to execute the fourth aspect or the fourth aspect. The method described by the second core network device in the selected embodiment, or the apparatus is made to perform the method described by the first network device in any optional embodiment of the fifth aspect or the fifth aspect.

In an eighth aspect, a first communication system is provided, where the first communication system includes the communication apparatus described in the sixth aspect (performing the method described in the first aspect or various optional implementation manners of the first aspect) or the seventh aspect The communication apparatus described in the aspect (executing the method described in the first aspect or various optional implementation manners of the first aspect), including the communication apparatus described in the sixth aspect (executing the second aspect or various optional implementation manners of the second aspect) the method described in the optional embodiment) or the communication device described in the seventh aspect (executing the method described in the second aspect or various optional embodiments of the second aspect), and, including the method described in the sixth aspect The communication apparatus described in the fifth aspect (performing the method described in the fifth aspect or various optional implementation manners of the fifth aspect) or the communication apparatus described in the seventh aspect (performing the fifth aspect or various optional implementation manners of the fifth aspect) method described in the method).

In a ninth aspect, a second communication system is provided, and the second communication system includes the communication apparatus described in the sixth aspect (performing the method described in the third aspect or various optional implementation manners of the third aspect) or the seventh aspect The communication apparatus described in the aspect (performing the method described in the third aspect or various optional implementation manners of the third aspect), including the communication apparatus described in the sixth aspect (performing the fourth aspect or various optional implementation manners of the fourth aspect) the method described in the optional embodiment) or the communication device described in the seventh aspect (executing the method described in the fourth aspect or various optional embodiments of the fourth aspect), and, including the method described in the sixth aspect The communication apparatus described in the fifth aspect (performing the method described in the fifth aspect or various optional implementation manners of the fifth aspect) or the communication apparatus described in the seventh aspect (performing the fifth aspect or various optional implementation manners of the fifth aspect) method described in the method).

In a tenth aspect, a computer-readable storage medium is provided, where the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer is made to execute the first aspect or any one of the above The method described in the alternative embodiment.

In an eleventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute the second aspect or any one of the above method described in an alternative embodiment.

In a twelfth aspect, a computer-readable storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer is made to execute the third aspect or any one of the above method described in an alternative embodiment.

In a thirteenth aspect, a computer-readable storage medium is provided, where the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer is made to execute the fourth aspect or any one of the above method described in an alternative embodiment.

In a fourteenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute the fifth aspect or any one of the above method described in an alternative embodiment.

A fifteenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute any one of the above-mentioned first aspect or method described in an alternative embodiment.

A sixteenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute any one of the above-mentioned second aspect or method described in an alternative embodiment.

A seventeenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, when the computer program is run on a computer, the computer is made to execute any one of the third aspect or the above method described in an alternative embodiment.

An eighteenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute any one of the fourth aspect or the above method described in an alternative embodiment.

A nineteenth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute any one of the above-mentioned fifth aspect or method described in an alternative embodiment.

The method provided by the embodiment of the present application reduces the redundant registration process of the terminal device, and because the terminal device does not need to perform this registration process, the resources consumed in the subsequent process are also reduced.

Description of drawings

Fig. 1 is a kind of schematic diagram of 5G communication system architecture;

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

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

Fig. 3B is a kind of schematic diagram of UE accessing SNPN;

Fig. 4A is a kind of schematic diagram that realizes SNPN and PLMN intercommunication through N3IWF;

Fig. 4B is a kind of schematic diagram that realizes SNPN and PLMN intercommunication through roaming framework;

Fig. 5 is a kind of schematic diagram that PLMN may support UE to register through different ways;

6 is a flowchart of a first communication method provided by an embodiment of the present application;

7 is a flowchart of a second communication method provided by an embodiment of the present application;

Fig. 8 is a kind of schematic diagram that UE may register to PLMN again after moving;

9 is a flowchart of a third communication method provided by an embodiment of the present application;

10 is a flowchart of a fourth communication method provided by an embodiment of the present application;

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

FIG. 12 is a schematic diagram of still another apparatus provided by an embodiment of the present application.

Detailed ways

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

Hereinafter, some terms in the embodiments of the present application will be explained, so as to facilitate the understanding of those skilled in the art.

In this embodiment of the present application, a terminal device is a device with a wireless transceiver function, which may be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a wireless device (for example, a communication module or a wireless device) built into the above-mentioned device. system-on-chip, etc.). The terminal device is used to connect people, things, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), vehicle-to-everything (vehicle to everything, V2X), machine-to-machine/machine-type communications (M2M/MTC), Internet of things (Internet of things, IoT), virtual reality (virtual reality, VR), augmented reality (augmented reality, AR), industrial control (industrial control), unmanned driving (self driving), telemedicine (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation, smart city (smart city), drones, robots and other terminal equipment. The terminal equipment may sometimes be referred to as user equipment (UE), a terminal, an access station, a UE station, a remote station, a wireless communication device, a user equipment, or the like. The device is described by taking the UE as an example.

The network devices in the embodiments of the present application include, for example, access network devices and/or core network devices. The access network device is a device with a wireless transceiver function, and is used to communicate with the terminal device. The access network equipment includes but is not limited to the base station (BTS, Node B, eNodeB/eNB, or gNodeB/gNB), the transmission reception point (TRP), the base station of the subsequent evolution of 3GPP, the wireless Access nodes, wireless relay nodes, wireless backhaul nodes, etc. in a true (wirelessfidelity, WiFi) system. The base station may be: a macro base station, a micro base station, a pico base station, a small base station, a relay station, and the like. Multiple base stations may support the aforementioned networks of the same access technology, or may support the aforementioned networks of different access technologies. A base station may contain one or more co-sited or non-co-sited transmission reception points. The network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario. The network device can also be a server, a wearable device, or a vehicle-mounted device. For example, a network device in a vehicle to everything (V2X) technology may be a road side unit (RSU). The following description will be given by taking 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 may be base stations of different types. The base station can communicate with the terminal equipment, and can also communicate with the terminal equipment through the relay station. A terminal device can communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and charging. The names of devices implementing core network functions in systems with different access technologies may be different, which are not limited in this application. Taking the 5G system as an example, the core network equipment includes: access and mobility management function (AMF), unified data management (unified data management, UDM), or user plane function (userplane function, UPF), etc. .

In this embodiment of the present application, the apparatus for implementing the function of the network device may be the network device, or may be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device. In the technical solutions provided by the embodiments of the present application, the technical solutions provided by the embodiments of the present application are described by taking the device for realizing the function of the network device being a network device as an example.

In this application, the number of nouns, unless otherwise specified, means "singular nouns or plural nouns", ie "one or more". "At least one" means one or more, and "plurality" means two or more. "And/or", which describes the relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, it can indicate that A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship. For example, A/B, means: A or B. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one of a, b, or c, means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.

Currently, mobile networks accessible to the UE include 2G, 3G, and 4G networks, and these networks provide service data transmission channels for the UE's call service, video service, and web page service. However, the explosive development of new services such as the Internet of Vehicles, virtual reality, mobile office, and the Internet of Things requires mobile networks to provide fiber-like access rates, a "zero" latency experience, and the ability to connect hundreds of billions of devices. Consistent services in multiple scenarios such as traffic density, ultra-high connection density, and ultra-high mobility, intelligent optimization of services and user perception, and over 100 times higher energy efficiency and over 100 times lower bit cost are the weaknesses of traditional networks. It cannot escort the rapid development of future business.

The 5G communication system architecture formulated by the 3rd Generation Partnership Project (3GPP) standard has four components, as shown in Figure 1. FIG. 1 includes a 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 the abbreviation of the next generation (ie 5G) mobile communication system architecture, which consists of UE, AN, Core and data network. Among them, UE, AN, and Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In Figure 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 the portal for mobile users to interact with the network, and can provide basic computing capabilities, storage capabilities, display service windows to users, and accept user operation inputs. The NextGen UE will use the new air interface technology to establish a signal connection and a data connection with the AN, thereby transmitting control signals and service data to the mobile network.

The AN is similar to the base station in the traditional network. It is deployed close to the UE to provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different quality to transmit user data according to the user's level and service requirements. The AN can manage its own resources, utilize them reasonably, provide access services for the UE on demand, and is responsible for forwarding control signals and user data between the UE and the core network.

The Core may include multiple network elements, which are responsible for maintaining subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE. When the UE is attached, it provides network access authentication for the UE; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE; When detaching, it releases network resources for the UE; when the UE has service data, it provides data routing functions for the UE, such as forwarding uplink data to the data network; or receives the downlink data of the UE from the data network, forwards it to the AN, and sends it to the UE .

A data network is a network that provides business services to users. The data network may include a plurality of application servers, and the application servers are used to provide services for corresponding applications. The client of the application is generally installed in the UE, and the server of the application (that is, the application server) is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by operators, such as the Internet, or a private network jointly deployed by operators, such as providing an IP multimedia network subsystem (IP multimedia core network subsystem, IMS) service network.

Please refer to FIG. 2 below, which further refines the core network of the 5G network architecture on the basis of FIG. 1 . The core network user plane includes UPF; the core network control plane includes authentication server function (AUSF), AMF, session management function (SMF), network slice selection function (NSSF), Network exposure function (NEF), NF repository function (NRF), UDM, policy control function (PCF), and application function (AF), etc. The core network control plane adopts a service-oriented architecture, and the interaction between the network elements of the control plane adopts the method of service invocation to replace the point-to-point communication method in the traditional architecture. In the service-based architecture, a control plane network element will open services to other control plane network elements for other control plane network elements to call; in point-to-point communication, there will be a set of specific messages on the communication interface between control plane network elements. It can only be used by the control plane NEs at both ends of the interface during communication.

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

UPF performs user data packet forwarding according to the routing rules of SMF, such as sending uplink data to DN or other UPFs, and forwarding downlink data to other UPFs or RANs.

AUSF, which performs security authentication of the UE.

AMF, access management and mobility management of UE. Responsible for UE state maintenance, UE reachability management, non-mobility management (MM) and non-access-stratum (NAS) message forwarding, session management (session management, SM) N2 messages 's forwarding.

SMF, UE session management, allocates resources for UE sessions and releases resources. The resources include session quality of service (QoS), session paths, and forwarding rules.

NSSF, selects network slice for UE.

NEF opens network functions to third parties in the form of northbound application programming interface (API) interfaces.

NRF provides other network elements with the storage function and selection function of network function entity information.

UDM, user subscription context management.

PCF, User Policy Management.

AF, Application Management.

Next, the concept of NPN is introduced.

NPN is a non-public 5G network. NPN can be implemented by relying on the support of PLMN. The NPN implemented by relying on the support of PLMN is called public network integrated NPN (PNI-NPN, public network integrated NPN); or, NPN can also be implemented without The network function implementation that depends on the PLMN, and the NPN that does not depend on the support of the PLMN is called SNPN.

PNI-NPN can be implemented using network slices in PLMN or a proprietary data network name (DNN). In order to prevent unauthorized UEs from attempting to access and select PNI-NPN, PNI-NPN additionally uses a closed access group (CAG) function. Some UEs that are allowed to access PNI-NPN can be configured with available CAG ID and CAG indication. The CAG indication can indicate that the UE is only allowed to access 5GS through the CAG cell, and the UE's subscription data stored in UDM will also include the CAG available to the UE. ID and CAG indication. The CAG cell will broadcast the CAG ID supported by the cell, and the UE determines whether the UE can access the cell according to the received CAGID.

Please refer to FIG. 3A , which is a schematic diagram of UE accessing PNI-NPN. FIG. 3A includes two base stations, wherein the cell provided by base station A is a CAG cell, and the CAG cell delivers PLMNID A and CAG ID X through a system information block (system information block, SIB). The cell provided by the base station B does not belong to the PNI-NPN, that is, it is not a CAG cell. The cell delivers the PLMN ID A through the SIB, but does not deliver the CAG ID. For example, if UE1 is configured with CAG ID X, UE1 can access base station A and base station B as well. For example, if UE2 is configured with CAG ID X and CAG indication, UE2 can access base station A but cannot access base station B. For example, UE3 is not configured with CAG ID and CAG indication, that is, UE3 is not allowed to access 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 the PLMN network. The SNPN is identified by PLMN ID+network identifier (NID), where the PLMN ID may be an inherent value reserved by a third-party operator, or may be a specific value of the PLMN operator deploying the SNPN. In the SNPN, a cell belonging to the SNPN broadcasts the PLMN ID+NID, and the UE selects a cell according to the broadcast information and the network selection information configured for the UE. 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 different from the PLMN ID and/or NID broadcast by the cell, the UE will not access the cell.

Please refer to FIG. 3B , which is a schematic diagram of UE accessing the SNPN. Wherein, the non-public network ID=N in FIG. 3B indicates that the ID of the non-public network is N. For example, the base station belonging to the SNPN broadcasts the PLMN ID+NID, and the network selection information of the UE4 includes the PLMN ID+NID, and the UE4 can access the base station.

Currently, SNPN can communicate with PLMN through N3IWF architecture. As shown in Figure 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; the UE uses the PLMN public network subscription to select the PLMN ID, select the PLMN N3IWF, and use the SNPN network The PDU session establishes a connection with the PLMN N3IWF to access the PLMNN3IWF, and then performs non-3GPP access registration in the PLMN network through the N3IWF. In FIG. 4A, SNPN 3GPP access (SNPN 3GPP access) means that the UE accesses the SNPN through the 3GPP technology at the air interface. Nwu of PLMN (Nwu for PLMN) means that the UE accesses the PLMN using the Nwu interface between the UE and the N3IWF of the PLMN. N1 (N1 for PLMN) of the PLMN is an interface between the UE and the PLMNAMF, indicating that the UE sends information to the PLMN AMF using the N1 interface between the UE and the PLMN AMF. N1 of NPN (N1 for NPN) is the interface between the UE and the SNPN AMF, indicating that the UE sends information to the SNPN AMF using the N1 interface between the UE and the SNPN AMF.

In addition to realizing the intercommunication between SNPN and PLMN through the N3IWF architecture, it also supports the interworking between SNPN and PLMN through the roaming architecture. Figure 4B shows the roaming architecture, the UE subscribes to the PLMN, the UE uses the public network subscription of the SNPN to select the SNPN ID, and uses the public network to subscribe to access the SNPN, and registers in the PLMN through the SNPN. PDU session is established within. The SNPN determines the roaming mode of the PDU session according to the public network subscription of the UE. The roaming mode is, for example, a local break out (LBO) mode or a home routed (HR) mode. The part to the right of the vertical line in the middle in FIG. 4B belongs to the PLMN, and the part to the left of the vertical line belongs to the SNPN. In this way, the UE registers with the 3GPP access mode in the PLMN through the SNPN.

It can be known from the above introduction that the PLMN can support interworking with the SNPN in the manner of FIG. 4A or FIG. 4B at the same time. As shown in Figure 5, PLMN1 supports intercommunication with SNPN1 in roaming mode, and also supports intercommunication with SNPN1 in N3IWF mode. For example, the UE uses the subscription of PLMN1 to register to PLMN1 by roaming in SNPN1, that is, as shown in FIG. 5 , the UE uses the subscription of PLMN1 to pass the security edge protection proxy (SEPP)/cross-PLMN user plane in SNPN1 A security gateway (inter PLMN UP security, IPUPS) registers with PLMN1. In the future, the UE may also register with the PLMN1 again by using the N3IWF through the SNPN1. However, after the UE registers to PLMN1 through roaming, if it registers to PLMN1 through other methods, it is a redundant registration process, and the process of registering through N3IWF is more complicated and requires more resources. Moreover, by using the N3IWF method, it is impossible to control the services of the UE, which will result in waste of private network resources and loss of control over 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 of the present application, the first core network device receives a request message from a terminal device, where the terminal device requests to register with the first network through the SNPN. If it is determined that the terminal device has been registered to the first network through the SNPN, the first core network device will reject the current registration of the terminal device, thereby reducing the redundant registration process of the terminal device, and because the terminal device does not need to perform the current registration process , which can prevent the UE from abusing private network resources or prevent the UE from accessing public network services.

The technical solutions provided in the embodiments of this application can be applied to a 5G system, such as an NR system, or can also be applied to a next-generation mobile communication system or other similar communication systems, which are not specifically limited.

The methods provided by the embodiments of the present application are described below with reference to the accompanying drawings.

An 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 introducing the various embodiments herein, the application to the network architecture shown in FIG. 5 is taken as an example.

For ease of introduction, in the various embodiments to be introduced below, the method is performed by a network device and a terminal device as an example. The UE described in the various embodiments herein is the UE in the network architecture shown in FIG. 5 . The first network described in the various embodiments herein is the home network of the UE, such as PLMN 1 in the architecture shown in FIG. 5 , or the first network may also be an SNPN, such as another SNPN different from SNPN 1 . Various embodiments of the application mainly take an example that the first network is a PLMN. The 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. The first core network device is, for example, the UDM in the PLMN1 in the architecture shown in FIG. is UDM; the second core network device is, for example, the AMF in PLMN1 in the architecture shown in FIG. 5 , which can be referred to as PLMN AMF; the third core network device is, for example, the AMF in SNPN1 in the architecture shown in FIG. 5 , which can be referred to as SNPN AMF; the first network device is, for example, the N3IWF in the PLMN1 in the architecture shown in FIG. 5 , which may be referred to as N3IWF for short.

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

The registration request message 1 may include a subscription concealed identifier (SUCI) or a subscription permanent identifier (SUPI) of the UE, and may also include an initial registration type. The initial registration type may indicate that the current registration of the UE is the first registration or the initial registration.

In addition, the SNPN RAN can also send the SNPN ID to the SNPN AMF, and the SNPN AMF receives the SNPN identifier from the SNPN RAN. The SNPN is the SNPN where the UE is currently located. The SNPN ID includes, for example, the PLMN ID and the NID.

S602. The SNPN AMF sends a Nudm_UECM_Registration request message to the UDM, and the UDM receives the Nudm_UECM_Registration request message from the SNPNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 2, or a second request message.

The registration request message 2 may include the SUPI of the UE, the initial registration type, the ID of the SNPN AMF, and the 3GPP access type. In addition, the registration request message 2 may also include SNPN information, for example, the SNPN information includes an SNPN identifier, or an SNPN access mode (SNPN access mode) indication, or an SNPN identifier and an SNPN access mode indication. The SNPN access mode indication may instruct the UE to enable the SNPN access mode and access the SNPN through the Uu air interface. That is, the SNPN AMF can send the information of the SNPN currently accessed by the UE to the UDM.

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

The SNPN AMF context of the UE may also be referred to as the registration context of the UE for short. The registration context of the UE includes the information of the SNPN, and may include information such as the ID of the SNPN AMF and the 3GPP access type. If the UDM detects that the UE is in an AMF context of a non-3GPP access type within another SNPN, that is, the UE is moving from another SNPN to the current SNPN, the UDM may The AMF context is de-registered, that is, the UDM deletes the AMF context of the non-3GPP access type, or it is understood that the UDM can de-register the registration of the UE in other SNPNs.

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 Nudm_UECM_Registration response message may also be referred to as a registration response message 2, or a response message to the registration request message 2, or a second response message. The registration response message 2 may indicate that the SNPN AMF is successfully registered to serve 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 it from other registration response messages, for example, the registration response message is called a registration response message 1, or a response message called a registration request message 1. The registration response message 1 may indicate that the UE is successfully registered with the PLMN.

After performing S601 to S605, the UE registers to the PLMN in a roaming manner by accessing SNPN1. After receiving the registration response message 1, the UE may establish a PDU session in the SNPN1 to perform corresponding services.

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 N3IWF. The registration request message may be used for the UE to request registration to the PLMN. It can be seen that after the UE registers to the PLMN through roaming, it 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 N3IWF.

The UE first establishes an IPsec connection with the N3IWF through the PDU session established in the SNPN, 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 an N2 message to the PLMN AMF, and the N2 message carries the registration request Request message 3. For example, the N2 message may also be called a third request message, or a 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 the initial registration type. In addition, the N2 message may also include the PLMN ID.

Optionally, the registration request message 3 may also include the information of the SNPN, then the UE sends the SNPN information to the PLMN AMF through the registration request message 3, without the need for the PLMN AMF to obtain the SNPN information through other means, which is conducive to simplifying registration process.

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

There are different ways for N3IWF to determine SNPN information. For example, the corresponding relationship between the SNPN and the tunnel is pre-configured (or, the protocol specifies), or the corresponding relationship between the SNPN ID and the tunnel is pre-configured (or, the protocol specifies), such as the tunnel between the UE and the N3IWF. The tunnel between the SNPNs, or the tunnels between the SNPN UPF and the N3IWF, the corresponding relationship is also known to the UE or the UPF, for example, the SNPN IDs correspond to the tunnels 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, it can select the tunnel corresponding to the SNPN accessed by the UE to send, and the N3IWF can determine the tunnel according to the tunnel that receives the registration request message 3. Information about the SNPN accessed by the UE.

For another example, the corresponding relationship between the SNPN and the IP addresses of the SNPN UPF is pre-configured (or, the protocol specifies), or in other words, the corresponding relationship between the SNPN ID and the IP address of the SNPN UPF is pre-configured (or, the protocol specifies) , for example, the SNPNID corresponds to the IP address of the SNPN UPF one-to-one. Then, when the N3IWF receives the registration request message 3 from the SNPN UPF, it can determine the information of the SNPN accessed by the UE according to the detected IP address of the SNPN UPF.

For another example, the corresponding relationship between the SNPN and the N3IWF is pre-configured (or, the protocol specifies), or in other words, the corresponding relationship between the SNPN ID and the N3IWF ID is pre-configured (or, the protocol specifies), and the corresponding relationship is used by the UE. It is also known, for example, the SNPN ID corresponds to the N3IWF ID one-to-one. Then, when the UE sends the registration request message 3, it can select the N3IWF corresponding to the SNPN accessed by the UE. 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 corresponding N3IWF. SNPN.

The above methods are just examples, and the N3IWF may also determine the information of the SNPN through other methods, which are not limited in this embodiment of the present application.

S607: 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 PLMNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 5, or a first request message.

The registration request message 5 may be used by the PLMN AMF to request to serve the UE. The registration request message 5 may include the SUPI of the UE, the initial registration type, and include the PLMN AMF ID and the non-3GPP access type. In addition, the registration request message 5 may further include the information of the SNPN, that is, the PLMN AMF may send the obtained information of the SNPN to the UDM.

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

The UDM can obtain the information of the SNPN included in the registration request message 5 . In addition, the UDM may also query the recorded registration context of the UE, that is, query the SNPN AMF context of the UE. If the SNPN AMF context of the UE includes the SNPN information and the initial registration type, and the SNPN and the SNPN corresponding to the SNPN information included in the registration request message 5 are the same SNPN, the UDM can determine that the UE has registered with the SNPN through the SNPN. PLMN. In order to avoid the behavior that the UE performs multiple registrations in the same PLMN, the UDM determines to reject the registration request for the PLMN AMF to serve the UE, that is, determines 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 Nudm_UECM_Registration response message may also be referred to as the registration response message 3, or the response message of the registration request message 5, or the first response message.

The registration response message 3 may include a failure result indication, which may indicate that the registration request for the PLMNAMF to serve the UE is rejected. Optionally, the registration response message 3 may further include a cause value, which may indicate a reason for refusing registration, for example, the reason indicated by the cause value is that the UE has registered with the PLMN through the 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 rejection message may also be called a registration response message 4, or a third response message, or a response message called a registration request message 3, or a response to a registration request message 4 (ie, the N2 message in S606). information.

The registration reject message may include a cause value that indicates the cause that the UE has registered with the PLMN via the SNPN. After the UE receives the registration rejection message, it can no longer request to register with the PLMN by means of the N3IWF.

In the embodiment of this application, the UDM can record the information of the SNPN that the UE accesses when the UE performs the first 3GPP registration in the PLMN through the SNPN, so that when the UE performs the second non-3GPP registration in the PLMN through the SNPN, the UDM can reject the UE non-3GPP registration to avoid the UE re-registering to the PLMN through the same SNPN. In this way, the resources consumed by the second registration process of the UE can be saved. Moreover, since the UE can no longer register to the PLMN through the N3IWF, the control of the UE accessing the public network service through the SNPN is realized.

In the following, an embodiment of the present application provides a second communication method. Please refer to FIG. 7 , which is a flowchart of the method.

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

For more content of S701, reference may be made to the introduction to S601 in the embodiment shown in FIG. 6 .

S702. The SNPN AMF sends a Nudm_UECM_Registration request message to the UDM, and the UDM receives the Nudm_UECM_Registration request message from the SNPNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 2, or a second request message.

For more content of S702, reference may be made to the introduction to S602 in the embodiment shown in FIG. 6 .

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

For more content of S703, reference may be made to the introduction to 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 Nudm_UECM_Registration response message may also be referred to as a registration response message 2, or a response message to the registration request message 2, or a second response message. The registration response message 2 may indicate that the SNPN AMF is successfully registered to serve 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 it from other registration response messages, for example, the registration response message is called a registration response message 1, or a response message called a registration request message 1. The registration response message 1 may indicate that the UE is successfully registered with the PLMN.

For more content of S705, reference may be made to the introduction to 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 N3IWF. The registration request message may be used for the UE to request registration to the PLMN. It can be seen that after the UE registers to the PLMN through roaming, it 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 N3IWF.

The UE first establishes an IPsec connection with the N3IWF through the PDU session established in the SNPN, 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 an N2 message to the PLMN AMF, and the N2 message carries the registration request Request message 3. For example, the N2 message may also be called a third request message, or a registration request message 4 . The registration request message 3 may also be referred to as a fourth request message.

For more content of S706, reference may be made to the introduction to 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 PLMNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 5, or a first request message.

For more content of S707, reference may be made to the introduction to 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 can obtain the information of the SNPN included in the registration request message 5 . In addition, the UDM may also query the recorded registration context of the UE, that is, query the SNPN AMF context of the UE. If the SNPN AMF context of the UE includes the SNPN information and the initial registration type, and the SNPN and the SNPN corresponding to the SNPN information included in the registration request message 5 are the same SNPN, the UDM can determine that the UE has registered with the SNPN through the SNPN. PLMN.

S709: 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 Nudm_UECM_Registration response message may also be referred to as the registration response message 3, or the response message of the registration request message 5, or the 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 UE's registration context (ie, the UE's SNPN AMF context), including the UE's registration context, which is equivalent to implicitly indicating 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 the SNPN. For example, the registration response message 3 includes indication information, which may indicate that the UE has registered with the PLMN through the SNPN. Compared with the registration context of the UE, the information amount of the indication information is small, which helps to reduce signaling overhead.

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

After the PLMN AMF receives the registration response message 3, it can determine to reject the current non-3GPP registration of the UE. For example, the PLMN AMF can determine to reject the current registration of the UE according to the SNPN information, the initial registration type and the registration context of the UE; or, if the registration response message 3 includes indication information, the PLMN AMF can determine the UE according to the indication information. The current PLMN has been registered through the SNPN, so the current registration of the UE is rejected.

S711. The PLMN AMF sends a Nudm_UECM_DeRegistration request message to the UDM, and the UDM receives the Nudm_UECM_DeRegistration request message from the PLMN AMF. For simplicity, the Nudm_UECM_DeRegistration request message is also referred to as a deregistration request message, or a fourth request message.

The Deregistration Request message may be used to request the UDM to deregister the registration of the PLMN AMF in the UDM. That is, the PLMNAMF sends the registration request message 5 to the UDM in S707, and the de-registration request message is used to de-register the current registration of the PLMN AMF. In the embodiment of the present application, the PLMN AMF decides to reject the UE's registration request, rather than the UDM decides to reject the UE's registration request, and the UDM may not take the initiative to de-register the PLMN AMF's registration in the UDM. Therefore, if the PLMNAMF rejects the registration request of the UE, the PLMN AMF may also request the UDM to de-register the registration of the PLMN AMF in the UDM. The fourth request message may include the PLMN ID, the PLMN AMF ID, the SUPI of the UE, and the N3GPP AccessType.

S712, the UDM deletes the registration context of the PLMN AMF corresponding to the SNPN from the context of the UE. That is, the UDM de-registers the current 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 rejection message may also be called a registration response message 4, or a third response message, or a response message called a registration request message 3, or a response to a registration request message 4 (ie, the N2 message in S706). information.

The registration response message 4 may include a cause value that indicates the cause that the UE has registered with the PLMN through the SNPN. After the UE receives the registration rejection message, it can no longer request to register with the PLMN by means of the N3IWF.

In the embodiment of this application, the UDM can record the information of the SNPN accessed by the UE when the UE performs the first 3GPP registration in the PLMN through the SNPN, so that when the UE performs the second non-3GPP registration in the PLMN through the SNPN, the UDM can record the corresponding SNPN information. The information is sent to the PLMN AMF, so that the PLMN AMF can reject the non-3GPP registration of the UE and prevent the UE from re-registering to the PLMN through the same SNPN. In this way, the resources consumed by the second registration process of the UE can be saved. Moreover, since the UE can no longer register to the PLMN through the N3IWF, the control of the UE accessing the public network service through the SNPN is realized.

Next, consider another question. As shown in Figure 8, PLMN1 supports interworking with SNPN1 using roaming mode. For example, the UE uses the subscription of PLMN1 to register with PLMN1 in SNPN1 by roaming. Then, the UE may move, for example, the UE moves to SNPN2. After the UE moves to the SNPN2, since the UE is also a subscriber of the SNPN2, the UE can access the SNPN2 and request to register with the PLMN through the N3IWF. At this time, if the PLMN rejects the current registration of the UE because the UE has previously registered to the PLMN through SNPN1, the UE may not work normally. Therefore, the embodiment of the present application proposes that when the UE moves, the PLMN should not reject the re-registration process of the UE. The solutions provided by the embodiments of the present application are described below through corresponding embodiments.

This embodiment of the present application provides a third communication method. Please refer to FIG. 9 , which is a flowchart of the method.

First, the UE subscribes using the PLMN, and registers with the PLMN in the SNPN1 by means of roaming. For this part of the content, please refer to the relevant introductions of S601 to S605 in the embodiment shown in FIG. 6 . After registration, the UE moves to the second SNPN, for example, the second SNPN is SNPN2 shown in FIG. 8 .

S901, the UE uses the SNPN2 subscription to register in the SNPN2. The process of the UE registering with the SNPN2 will not be repeated.

S902, the UE establishes a PDU session in the SNPN2, which is not repeated here.

S903, 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 N3IWF. The registration request message may be used for the UE to request registration to the PLMN. It can be seen that after the UE moves, it can access the new SNPN again, and then requests to register to the PLMN again through the PLMN N3IWF.

The UE first establishes an IPsec connection with the N3IWF through the 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 an N2 message to the PLMN AMF, and the N2 message carries the registration request Request message 3. For example, the registration request message 3 may also be called the third request message, or the registration request message 4 . The registration request message 3 may include the SUPI or SUCI of the UE, and include the mobility registration type. In addition, the N2 message may also include the PLMN ID. The mobile registration type may indicate that the registration request message 3 is a registration request triggered by the UE's movement, or indicate that the current registration is a registration triggered by the UE's movement.

Optionally, the registration request message 3 may further include information of the SNPN2. Then, the UE sends the SNPN2 information to the PLMN AMF through the registration request message 3, and the PLMN AMF does not need to obtain the SNPN2 information through other channels, which is beneficial to simplify the registration process.

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

For more content of S903, such as how the N3IWF determines the information of SNPN2, etc., please refer to the introduction to S606 in the embodiment shown in FIG. 6 .

S904, 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 PLMNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 5, or a first request message.

The registration request message 5 may be used by the PLMN AMF to request to serve the UE. The registration request message 5 may include the SUPI of the UE, as well as the PLMN AMF ID and the non-3GPP access type. In addition, the registration request message 5 may further include the information of the SNPN2 and the mobile registration type.

S905, the UDM determines to accept the PLMN AMF to provide services for the UE.

The UDM determines that the UE is registered after moving according to the mobile registration type. And the UDM determines that the UE 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 PLMNAMF to provide services for the UE.

In addition, since the UDM accepts the PLMN AMF to provide services for the UE, the UDM can de-register the UE in the PLMN through the SNPN1 to avoid the UE from registering twice in the PLMN. For example, UDM deletes the AMF in SNPN1 corresponding to the registration context of SNPN1, that is, deletes the context information of SNPN1 AMF from the context of the UE, so as to realize de-registration of the UE through the registration of SNPN1 in the PLMN.

S906, 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 Nudm_UECM_Registration response message may also be referred to as the registration response message 3, or the response message of the registration request message 5, or the first response message. The first response message may indicate that the PLMN AMF is successfully registered to serve 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. The registration response message may also be called a registration response message 4, or a third response message, or a response message called a registration request message 3, or a response to a registration request message 4 (ie, the N2 message in S903). information. The registration response message 4 may indicate that the UE is successfully registered with the PLMN, that is, the UE is successfully registered with the PLMN through the SNPN2.

In the embodiment of this application, in the scenario where the UE moves from SNPN1 to SNPN2, the PLMN can accept the non-3GPP registration of the UE in the PLMN through SNPN2, so that the UE can work normally. Moreover, it is possible to de-register the UE's 3GPP registration in the PLMN through SNPN1 to avoid the UE registering twice in the PLMN.

Next, an embodiment of the present application provides a fourth communication method. Please refer to FIG. 10 , which is a flowchart of the method.

First, the UE UE subscribes to the PLMN, and registers to the PLMN in the SNPN1 by roaming. For this part, please refer to the related introductions of S601 to S605 in the embodiment shown in FIG. 6 . After registration, the UE moves to the second SNPN, for example, the second SNPN is SNPN2 shown in FIG. 8 .

S1001, the UE uses the SNPN2 subscription to register in the SNPN2. The process of the UE registering with the SNPN2 will not be repeated.

S1002 , the UE establishes a PDU session in the SNPN2, which is not repeated here.

S1003, 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 N3IWF. The registration request message may be used for the UE to request registration to the PLMN. It can be seen that after the UE moves, it can access the new SNPN again, and then requests to register to the PLMN again through the PLMN N3IWF.

For more content of S1003, reference may be made to the introduction to S903 in the embodiment shown in FIG. 9 .

S1004, 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 PLMNAMF. For simplicity, the Nudm_UECM_Registration request message may also be referred to as a registration request message 5, or a first request message.

For more content of S1004, reference may be made to the introduction to S904 in the embodiment shown in FIG. 9 .

S1005, 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 Nudm_UECM_Registration response message may also be referred to as the registration response message 3, or the response message of the registration request message 5, or the first response message. The first response message may indicate that the PLMN AMF is successfully registered to serve the UE. The UDM determines that the UE is registered after moving according to the mobile registration type, and the UDM determines that the UE 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 provide services for the UE , and the first response message carries the UE's registration context (that is, the UE's SNPN AMF context), the UE's registration context can implicitly indicate that the PLMN AMF successfully registers to provide services for the UE; or the UDM can also be in the first response. The message carries indication information, which may indicate that the UE has registered with the PLMN through the SNPN, or that the PLMN AMF has successfully registered to provide services for the UE.

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

The PLMN AMF determines that the UE is registered after moving according to the mobile registration type. Moreover, the PLMN AMF determines to accept the registration of the UE in 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 Nudm_UECM_DeRegistration request message to the UDM, and the UDM receives the Nudm_UECM_DeRegistration request message from the PLMN AMF. For simplicity, the Nudm_UECM_DeRegistration request message is also referred to as a deregistration request message, or a second request message.

The de-registration request message may request (or in other words, indicate) de-registration of the UE's registration in the PLMN through SNPN1. In the embodiment shown in FIG. 9 , the UDM determines to accept the PLMN AMF to provide services for the UE accessing SNPN2, so the UDM can de-register the registration of the SNPN1 AMF by itself without PLMN AMF notification. In the embodiment of the present application, the PLMN AMF determines to accept the registration of the UE in the PLMN by accessing the SNPN2, so the PLMN AMF may also request the UDM to de-register the registration of the SNPN1 AMF. The deregistration request message may include PLMN ID, PLMN AMF ID, SUPI of the UE, and 3GPP Access Type.

S1008, the UDM deletes the registration context of the AMF in the SNPN1 corresponding to the SNPN1. Exemplarily, the UDM deletes the context information of the SNPN1 AMF from the context of the UE, thereby realizing de-registration of the UE through the registration of the SNPN1 in the PLMN.

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 called a registration response message 4, or a third response message, or a response message called a registration request message 3, or a response to a registration request message 4 (ie, the N2 message in S1003). information. The registration response message 4 may indicate that the UE is successfully registered with the PLMN, that is, the UE is successfully registered with the PLMN through the SNPN2.

In the embodiment of this application, in the scenario where the UE moves from SNPN1 to SNPN2, the PLMN can accept the non-3GPP registration of the UE in the PLMN through SNPN2, so that the UE can work normally. Moreover, it is possible to de-register the UE's 3GPP registration in the PLMN through SNPN1 to avoid the UE registering twice in the PLMN.

Based on the same inventive concept, as shown in FIG. 11 , which is a schematic diagram of an apparatus provided in the present application, 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 the first core network device or chip, the apparatus 1100 can be used to execute 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 Operations performed by PLMN UDM in . When the apparatus is a second core network device or chip, the apparatus 1100 can be used to execute 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 . Operations performed by the PLMN AMF in . When the apparatus is a first network device or chip, the apparatus 1100 can be used to execute 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 . Operations performed by the N3IWF.

The apparatus 1100 includes at least one processor 1101 , a communication line 1102 , and at least one communication interface 1104 . As an optional implementation manner, the apparatus 1100 may further include a memory 1103 . Since the memory 1103 is not an essential function module but an optional function module, it is represented by a dotted box in FIG. 11 .

The processor 1101 may include a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the programs of the present application. circuit.

Communication line 1102 may include a path to communicate information between the components described above.

Communication interface 1104, using any transceiver-like device, for communicating with other devices or communication networks, such as Ethernet, radio access networks (RAN), wireless local area networks (WLAN), wired access network, etc.

Memory 1103 may be read-only memory (ROM) or other type of static storage device that can store static information and instructions, random access memory (RAM), or other type of static storage device that can store information and instructions It can also be 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 discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being stored by a computer any other medium taken, but not limited to this. The memory 1103 may exist independently, and is connected to the processor 1101 through the communication line 1102 . Alternatively, the memory 1103 can also be integrated with the processor 1101 .

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

Optionally, the computer-executed instructions in the embodiment of the present application may also be referred to as application code, which is not specifically limited in the embodiment of the present application.

In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11 .

In a specific implementation, as an embodiment, the apparatus 1100 may include multiple processors, such as the processor 1101 and the processor 1108 in FIG. 11 . Each of these processors can 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 (eg, computer program instructions).

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

In this embodiment of the present application, the device may be divided into functional modules according to the foregoing method examples. 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 above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. For example, in the case where each functional module is divided according to each function, FIG. 12 shows a schematic diagram of an apparatus, and the apparatus 1200 may be the first core network device involved in the above embodiment, or the device in the above embodiment. The second core network device involved is either the first network device involved in the above embodiment, or a chip in the first core network device, or a chip in the second core network device, or the first network device in the chip. The apparatus 1200 includes a sending unit 1201 , a processing unit 1202 and a receiving unit 1203 .

In one embodiment, when the apparatus 1200 is the first core network device or the chip of the first core network device of the 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 the second core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message includes initial registration type and information of the non-public network accessed by the terminal device, the initial registration type is used to indicate that the first request message is the initial registration request of the terminal device, the apparatus 1200 is located in the first network, the first request message is a network is the home network of the terminal device;

a processing unit 1202, configured to determine that the terminal device has registered with the first network through the non-public network;

The sending unit 1201 is configured to send a first response message to the 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 a message indicating that the terminal device has passed the Indication information that the non-public network is registered with the first network.

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

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 by the third core network device to request to provide a service for the terminal device, The second request message includes information of the non-public network. The processing unit 1202 is configured to record the registration context of the terminal device, the registration context of the terminal device includes the information of the non-public network, and the sending unit 1201 is configured to send the second core network device to the third core network device. A response message, where the second response message is used to instruct the third core network device to successfully register to provide services for the terminal device.

As an optional implementation manner, the processing unit 1202 is configured to determine that the terminal device has been registered to the first network through the non-public network in the following manner: according to the initial registration type, the The information and the recorded registration context of the terminal device determine that the terminal device has registered with the first network through the non-public network.

As an optional implementation manner, the first response message further includes a cause value, where the cause value is used to indicate that the terminal device has registered with 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 data from the second core network device. a fourth request message of the core network device, where the fourth request message is used to request the apparatus 1200 to de-register the registration of the second core network device in the apparatus 1200, and the processing unit 1202 is further configured to delete the The second core network device corresponds to the registration context of the non-public network.

In one embodiment, when the apparatus 1200 is the second core network device or the chip of the second core network device of the embodiment shown in FIG. 6 or the embodiment shown in FIG. 7 , then:

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

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

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

The receiving unit 1203 is further configured to receive a first response message from the 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 a message for indicating the terminal device Indication information that has been registered with the first network through the non-public network;

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

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

As an optional implementation manner, the processing unit 1202 is configured to obtain the information of the non-public network accessed by the terminal device in the following manner, including: obtaining the information of the non-public network from the third request message; Or, the 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, where the cause value is used to indicate that the terminal device has registered with 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 The registration in the first core network device is de-registered.

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 the registration of the terminal device according to the first response message.

In one embodiment, when the apparatus 1200 is the first core network device or the chip of the first core network device of the 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 the second core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message further includes The mobile registration type and the information of the second non-public network, the mobile registration type is used to indicate that the first request message is a registration request triggered by the terminal equipment due to movement, the apparatus 1200 is located in the first network, and the first network is the home network of the terminal device;

The sending unit 1201 is configured to send a first response message to the second core network device, where the first response message is used to instruct the second core network device to successfully register to provide services for the terminal device.

As an optional implementation manner, the processing unit 1202 is configured to de-register the 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 de-register the registration of the terminal device with the first network through the first non-public network in the following manner: deleting the third core network device corresponding to the the registration context of the first non-public network; or, receiving a second request message from the second core network device through the receiving unit 1203, where the second request message is used to instruct the terminal device to pass the first non-public network De-registration is performed in the registration of the first network, and the registration context of the third core network device corresponding to the first non-public network is deleted.

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

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 a terminal device providing a service, the second request message includes information of the first non-public network; the processing unit 1202 is further configured to record a registration context of the terminal device, where the registration context of the terminal device includes the first non-public network network information; and the sending unit 1201 is 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 as the terminal device Provide services.

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

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

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

In one embodiment, when the apparatus 1200 is the second core network device or the chip of the second core network device of the embodiment shown in FIG. 9 or the embodiment shown in FIG. 10 , then:

A receiving unit 1203, configured to receive a third request message from the terminal device through the first network device, where the third request message is used by the terminal device to request to register with 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 the home network of the terminal device;

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

The receiving unit 1203 is further configured to receive a first response message from the first core network device, where the first response message is used to instruct the apparatus 1200 to successfully register to provide services for the terminal device;

The sending unit 1201 is further configured to send a third response message to the terminal device, where the third response message is used to instruct the terminal device to successfully register with the first network.

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

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

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

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 the terminal device to pass the first non-public network The registration at the first network is de-registered.

In one embodiment, when the apparatus 1200 is the chip of the first network device of 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 ,but:

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

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

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

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

It should be understood that the apparatus 1200 may be used to implement the steps performed by the first core network device, the second core network device, or the first network device in the method of the embodiment of the present application, and the relevant features can be referred to the above, which will not be repeated here. .

Specifically, the functions/implementation process 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 the computer execution instructions stored in the memory 1103 . Alternatively, the function/implementation process of the processing unit 1202 in FIG. 12 can be implemented by the processor 1101 in FIG. 11 calling the computer-executed instructions stored in the memory 1103, and the functions/implementation of the sending unit 1201 and the receiving unit 1203 in FIG. 12 The process may be implemented through the communication interface 1104 in FIG. 11 .

Optionally, when the device 1100 is a chip or a circuit, the functions/implementation process of the sending unit 1201 and the receiving unit 1203 may also be realized by pins or circuits in the device 1100 . Optionally, when the apparatus 1100 is a chip, the memory 1103 may be a storage unit in the chip, such as a register, a cache, and the like. Of course, when the device 1100 is the first core network device, such as the UDM in the above-mentioned 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 the 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 the 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-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can 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 the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

The various illustrative logic units and circuits described in the embodiments of this application may be implemented by general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gates A field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions. A general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.

The steps of the method or algorithm described in the embodiments of this application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. A software unit may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. Illustratively, a storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium may be provided in the ASIC, and the ASIC may be provided in the terminal device. Alternatively, the processor and the storage medium may also be provided in different components in the terminal device.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

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 may be made without departing from the spirit and scope of the embodiments of the present application. Accordingly, the embodiments of the present application and the accompanying drawings are merely exemplary illustrations of the embodiments of the present application defined by the appended claims, and are deemed to have covered any and all modifications, changes, combinations or equivalents within the scope of the embodiments of the present application thing. Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. In this way, if these 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 technical equivalents, the embodiments of the present application are also intended to include these modifications and variations.

Claims (29)

1. a communication method, is characterized in that, comprises: The first core network device in the first network receives a first request message from the second core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request The message includes the initial registration type and information of the non-public network accessed by the terminal device, the initial registration type is used to indicate that the first request message is the initial registration request of the terminal device, and the first network is the the home network of the terminal equipment; 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 the second core network device, where the first response message includes a failure result indication, or includes the registration context of the terminal device, or includes a message indicating that the terminal device has Indication information for registering with 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 identifier of the non-public network and/or an indication of an access mode of the non-public network. 3 . 3. The method according to claim 1 or 2, wherein the method further comprises: The first core network device receives a second request message from the third core network device, the second request message is used by the third core network device to request to provide services for the terminal device, and the second request message includes all the information on non-public networks; the first core network device records the registration context of the terminal device, where the registration context of the terminal device includes 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 instruct the third core network device to successfully register to provide services for the terminal device. 4 . The method according to claim 3 , wherein determining, by the first core network device, that the terminal device has registered with the first network through the non-public network, comprising: 4 . The first core network device determines, according to the initial registration type, the information of the non-public network, and the recorded registration context of the terminal device, that the terminal device has registered with the first device through the non-public network. network. The method according to any one of claims 1 to 4, wherein the first response message further comprises a cause value, and the cause value is used to indicate that the terminal device has registered through the non-public network to the first network. 6. The method according to any one of claims 1 to 5, wherein the method further comprises: The first core network device deletes the registration context of the second core network device 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 request the second core network device A registration in a core network device is de-registered; The first core network device deletes the registration context of the second core network device corresponding to the non-public network. 7. A communication method, characterized in that, comprising: The second core network device in the first network receives a third request message from the terminal device through the first network device, where the third request message is used by the terminal device to request to register with the first network, and the first The network is the home network of the terminal device; obtaining, by the second core network device, information of the non-public network accessed by the terminal device; The second core network device sends a first request message to the first core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message includes an initial registration type and information of the non-public network, where 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 the first core network device, where the first response message includes a failure result indication, or includes the registration context of the terminal device, or includes instructions for indicating the terminal device Indication information that has been registered with the first network through the non-public network; The second core network device sends a third response message, where the third response message is used to reject the registration of the terminal device. 8. The method according to claim 7, wherein the information of the non-public network comprises an identifier of the non-public network, and/or an indication of an access mode of the non-public network. 9. The method according to claim 7 or 8, wherein the second core network device obtains the information of the non-public network accessed by the terminal device, comprising: 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 the information of the non-public network from the first network device. The method according to any one of claims 7 to 9, wherein the third response message further comprises a cause value, and the cause value is used to indicate that the terminal device has registered through the non-public network to the first network. 11. The method according to any one of claims 7 to 10, wherein the method further comprises: 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 The registration in the core network device is de-registered. The method according to any one of claims 7 to 11, wherein before the second core network device sends the third response message, the method further comprises: The second core network device determines to reject the registration of the terminal device according to the first response message. 13. A communication method, comprising: The first core network device in the first network receives a first request message from the second core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message is The request message also includes information of a mobile registration type and 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 a terminal device due to movement, and the first network is the terminal the home network of the device; The first core network device sends a first response message to the second core network device, where the first response message is used to instruct the second core network device to successfully register to provide services for the terminal device. 14. The method of claim 13, wherein the method further comprises: The first core network device deregisters the registration of the terminal device in the first network through the first non-public network. 15 . The method according to claim 14 , wherein the first core network device deregisters the registration of the terminal device in the first network through the first non-public network, comprising: 15 . The first core network device deletes the registration context of the third core network device 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 the terminal device to register with the first network through the first non-public network de-register; The first core network device deletes the registration context of the third core network device corresponding to the first non-public network. The method according to any one of claims 13 to 15, wherein the information of the second non-public network comprises an identifier of the second non-public network, and/or a non-public network access mode instruct. 17. The method according to claim 14 or 15, wherein 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 by the third core network device to request to provide services for the terminal device, and the second request message including information about the first non-public network; the first core network device records a registration context of the terminal device, where the registration context of the terminal device includes 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 instruct the third core network device to successfully register to provide services for the terminal device. The method according to claim 14, 15 or 17, wherein the information of the first non-public network comprises an identifier of the first non-public network, and/or an indication of a non-public network access mode . 19. The method of claim 13, wherein the first response message includes a registration context of the terminal device. The method according to any one of claims 13 to 19, wherein before the first core network device sends the first response message to the second core network device, the method further comprises: The first core network device determines, according to the mobile registration type, the information of the second non-public network, and the recorded registration context of the terminal device, that the second core network device is successfully registered to provide services for the terminal device. 21. A communication method, comprising: The second core network device in the first network receives a third request message from the terminal device through the first network device, where the third request message is used by the terminal device to request to register with the first network, the third request message The 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 the home network of the terminal device; The second core network device sends a first request message to the first core network device, where the first request message is used by the second core network device to request to provide services for the terminal device, and the first request message includes the mobile registration type and the information of the second non-public network; receiving, by the second core network device, a first response message from the first core network device, where the first response message is used to instruct the second core network device to successfully register to provide services for the terminal device; The second core network device sends a third response message to the terminal device, where the third response message is used to instruct the terminal device to successfully register with the first network. 22. The method according to claim 21, wherein the information of the second non-public network comprises an identifier of the second non-public network, and/or an indication of a non-public network access mode. 23. The method according to claim 21 or 22, wherein the first response message further comprises a registration context of the terminal device. 24. The method according to claim 23, wherein before the second core network device sends a third response message to the terminal device, the method further comprises: The second core network device determines that the terminal device successfully registers with 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. 25. The method according to claim 23 or 24, wherein the method further comprises: The second core network device sends a second request message to the first core network device, where the second request message is used to instruct the terminal device to register with the first network through the first non-public network. to register. 26. A communication method, comprising: The first network device in the first network receives a fourth request message from the terminal device, where the fourth request message is used by the terminal device to request to register with the first network, where the first network is the home of the terminal device network; The first network device determines the information of the non-public network accessed by the terminal device; The first network device sends the information of the non-public network to the second core network device. 27. The method according to claim 26, wherein the determining, by the first network device, the information of the non-public network accessed by the terminal device comprises: The first network device determines the information of the non-public network accessed by the terminal device according to the correspondence between the non-public network and the tunnel or IP address; or, The first network device determines the information of the non-public network accessed by the terminal device according to the correspondence between the non-public network and the first network device. 28. A communication device, characterized in that it comprises a processor and a memory; the memory is used to store one or more computer programs, when the one or more computer programs are executed, such that as claimed in claims 1 to 6 The method of any one of the claims is performed, or the method of any one of claims 7 to 12 is performed, or the method of any one of claims 13 to 20 is performed, or A method as claimed in any of claims 21-25 is caused to be performed, or a method as claimed in any of claims 26-27 is caused to be performed. 29. A computer-readable storage medium, characterized in that, the computer-readable storage medium is used for storing a computer program, and when the computer program is run on a computer, the computer is made to execute the method according to claims 1 to 6 any one of the methods, or causing the computer to execute the method according to any one of claims 7 to 12, or causing the computer to execute the method according to any one of claims 13 to 20, Or cause the computer to execute the method according to any one of claims 21-25, or cause the computer to execute the method according to any one of claims 26-27.

Images