CN109451577B

CN109451577B - Network communication method and equipment

Info

Publication number: CN109451577B
Application number: CN201710757293.1A
Authority: CN
Inventors: 李永翠; 李岩; 李欢; 唐廷芳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-08-29
Filing date: 2017-08-29
Publication date: 2020-08-07
Anticipated expiration: 2037-08-29
Also published as: WO2019041897A1; CN109451577A

Abstract

In the scheme, under the condition that a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device or the UDM entity can determine that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN when the terminal device accesses the two P L MNs and the access types are different, so that the UDM entity can not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also can not register the first AMF entity, thereby realizing double registration of the first AMF entity and the second AMF entity.

Description

Network communication method and equipment

Technical Field

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

Background

Currently, when a terminal device accesses a public land mobile network (P L MN), it needs to perform network registration with a core network for the P L MN in the following manner:

an access and mobility management function (AMF) entity in a core network, which is responsible for mobility management of the terminal device, performs network registration to a Unified Data Management (UDM) entity through a location management procedure (location management procedure), thereby notifying the UDM of information of the AMF entity. And after the AMF entity is registered with the UDM entity, the UDM maintains the information of the AMF entity aiming at the terminal equipment.

Therefore, when a terminal device accesses a P L MN through a first AMF entity by using an access technology of a first access type (e.g., the 3rd generation partnership project (3 GPP) access type), the UDM stores information of the first AMF entity responsible for mobility management of the terminal device, and when the terminal device accesses the P L MN and accesses a P L MN through a second AMF entity by using an access technology of a second access type (e.g., non-3GPP access), the UDM entity replaces the information of the first AMF entity with information of the second AMF entity.

With the development of terminal device communication technology, currently, many terminal devices (e.g., smartphones, tablets (pads), etc.) have dual connection capabilities, that is, access technologies adopting 3GPP access types and non-3GPP access types are supported to access P L MN., however, in a conventional network registration process, a UDM entity in a core network can only store information of an AMF entity responsible for mobility management of the terminal device for one terminal device.

Disclosure of Invention

The application provides a network communication method and equipment, which are used for solving the problem that a UDM entity cannot guarantee that two AMF entities which are in charge of mobility management of the same terminal equipment are successfully registered in a network at the same time.

In a first aspect, an embodiment of the present application provides a network communication method, which may include the following steps:

the method comprises the steps that a terminal device obtains a first access type of a first access technology adopted when accessing a first public continental mobile network P L MN and a second access type of a second access technology adopted when accessing a second P L MN, wherein the first P L MN is a P L MN which is accessed by the terminal device, the second P L MN is a P L MN which is accessed by the terminal device, the first access type is a third generation partnership project (3 GPP) access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type, and then when the terminal device determines that the second access type is different from the first access type, a first registration instruction is sent to a Unified Data Management (UDM) entity to instruct the UDM entity to reserve registration information of the first access and a mobility management function (AMF) entity, wherein the first AMF entity is responsible for mobility management when the terminal device accesses the first P L MN.

By the above method, when a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device may determine that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN when access types to which access technologies adopted when the terminal device accesses the two P L MNs are different, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also may not deregister the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

In one possible design, the terminal device further needs to determine that the identity of the second P L MN is different from the identity of the first P L MN before the terminal device sends the first registration indication to the UDM entity.

In the mobile communication system, when the identifier of the first P L MN is different from the identifier of the second P L MN, and the second access type is different from the first access type, the AMF entity responsible for mobility management when the terminal device accesses P L MN through the 3GPP access type must be different from the AMF entity responsible for mobility management when the terminal device accesses P L MN through the non-3GPP access type, so that, by this design, the terminal device instructs the UDM entity to retain the registration information of the first AMF, i.e., to not register the first AMF, in case that the second access type is different from the first access type and the identifier of the second P L MN is different from the identifier of the first P L MN, after the UDM entity successfully registers the second AMF entity, the UDM entity can simultaneously retain the registration information of the two AMF entities responsible for mobility management of the same terminal device, and the terminal device can simultaneously adopt two different access technologies L corresponding to the two AMF entities.

In one possible design, before the terminal device sends the first registration indication to the UDM entity, the terminal device further needs to determine that the terminal device has dual connectivity capability, where the dual connectivity capability is used to indicate that the terminal device supports access to the P L MN using two access types of access technologies simultaneously.

If the terminal device has dual connectivity, the terminal device may access P L MN. using two access technologies of two access types at the same time, so that, by the design, after determining that the terminal device has dual connectivity, the terminal device instructs the UDM entity not to de-register the first AMF entity, and after registering the second AMF entity, the UDM entity may simultaneously store registration information of two AMF entities responsible for mobility management of the same terminal device, and the terminal device may access P L MN using two access technologies of two access types.

In one possible design, the dual connectivity capability may also indicate that the terminal device supports access to two different P L MNs using two access types of access technologies simultaneously.

In one possible design, the terminal device may acquire the second access type by:

the first mode is as follows: the terminal equipment sends a request carrying the position information of the terminal equipment to an ANDSF entity;

the ANDSF entity provides the terminal equipment with information of access networks which can be used nearby the terminal equipment (including an access technology adopted by the terminal equipment to access the access network and/or an access type of the access technology) according to an operator policy;

the terminal device may determine the second access type according to information of the access network provided by the ANDSF entity. For example, after the terminal device determines an access technology adopted by the terminal device to access the access network, the second access type to which the access technology belongs is determined according to a corresponding relationship between the access type and the access technology contained in the access technology.

The second mode is as follows: the terminal equipment selects target access network equipment with high signal transmission efficiency by measuring signals sent by received 3GPP access network equipment and signals sent by non-3GPP access network equipment;

the terminal equipment determines an access technology used by the target access network equipment so as to determine a second access type to which the access technology belongs; or the terminal device determines the second access type corresponding to the target access network device.

By this design, the terminal device may determine the second access type.

In one possible design, the terminal device determines the second access type when accessing the second P L MN by any of the above-mentioned methods, and then stores the second P L MN and the second access type, and accordingly, the terminal device may determine the first access type when accessing the first P L MN by any of the above-mentioned methods, and stores the first P L MN and the first access type.

In one possible design, the terminal device may send the first registration indication to the UDM entity through a second AMF entity, where the second AMF entity is responsible for mobility management when the terminal device accesses the second P L MN.

In one possible design, the first registration indication sent by the terminal device to the UDM entity through the second AMF entity may also inform the UDM entity to register with the second AMF entity.

By this design, the UDM entity may also register (store the registration information of) the second AMF entity after receiving the first registration indication sent by the second AMF entity.

In one possible design, the terminal device sends a second registration indication to the UDM entity when determining at least one of: the terminal device does not have dual connection capability; the second access type is the same as the first access type;

wherein the second registration indication is used to instruct the UDM entity to deregister with the first AMF entity, and the dual connectivity capability is used to indicate that the terminal device supports access to the P L MN by using two access types of access technologies simultaneously.

In the case that a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device determines that the condition for sending a first registration indication is not satisfied currently, then sends a second registration indication to the UDM entity, and notifies the UDM entity to deregister a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN.

In one possible design, a second registration indication is sent to the UDM entity when the terminal device determines at least one of that the terminal device does not have dual connectivity capability, that the second access type is the same as the first access type, that the identity of the second P L MN is the same as the identity of the first P L MN;

In one possible design, the second registration indication is further used to trigger the UDM entity to notify a first session management function, SMF, entity to release the session of the terminal device (e.g., send a session release notification message to the first SMF entity), where the first SMF entity is responsible for session management when the terminal device accesses the first P L MN.

Through the design, the UDM entity can not only register the first AMF entity, but also release the session of the terminal equipment, so that the signaling overhead brought by the session maintenance of the first SMF entity is reduced.

In one possible design, when the terminal device determines that the second access type is different from the first access type, the terminal device may determine whether to send the second registration indication to the UDM entity by:

when the priority of the first P L MN is lower than a set P L MN priority threshold, the terminal equipment decides to send the second registration indication to the UDM entity;

when the priority of the session is lower than a set session priority threshold, the terminal equipment decides to send the second registration instruction to the UDM entity;

and when the priority of the service is lower than a set service priority threshold, the terminal equipment decides to send the second registration instruction to the UDM entity.

Therefore, when the terminal device adopts the scheme provided by the first mode, the terminal device can ensure that the high-priority P L MN is normally accessed through the comparison of the priority of the P L MN and the priority threshold of the P L MN, when the terminal device adopts the scheme provided by the second mode, the terminal device can ensure that the high-priority session is normally performed through the comparison of the priority of the session and the priority threshold of the session, and when the terminal device adopts the scheme provided by the third mode, the terminal device can ensure that the high-priority service is normally performed through the comparison of the priority of the service and the priority threshold of the service.

In a possible design, the terminal device may send the second registration indication to the UDM entity through the second AMF entity, for example, the terminal device may carry the second registration indication in an RRC message or a registration request, and send the second registration indication to the second AMF entity through the access network device, and the second AMF entity sends the second registration indication to the UDM entity by carrying the second registration indication in an update location request. In this way, the terminal device may successfully send the second registration indication to the UDM entity.

In one possible design, the second registration indication sent by the terminal device to the UDM entity through the second AMF entity may also inform the UDM entity to register with the second AMF entity.

By this design, the UDM entity may also register (store the registration information of) the second AMF entity after receiving the second registration indication sent by the second AMF entity.

In one possible design, when the terminal device determines that a target access type identical to the second access type exists in the first access type, sending a third registration indication to the UDM entity, where the third registration indication is used to indicate that the UDM entity deregisters a target AMF entity, and the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN accessed by the terminal device using an access technology belonging to the target access type.

Therefore, the scheme can ensure that two AMF entities in charge of the same terminal equipment can be successfully registered in the UDM entity at the same time, thereby avoiding the frequent network registration process initiation of the terminal equipment, reducing unnecessary signaling and improving the network access performance and the service performance of the terminal equipment.

In one possible design, the third registration indication is further used to trigger the UDM entity to notify a target SMF entity to release the session of the terminal device (e.g., send a session release notification message to the target SMF entity), where the target SMF entity is responsible for session management when the terminal device accesses the target P L MN.

Through the design, the UDM entity can not only register the target AMF entity, but also release the session of the terminal equipment, so that the signaling overhead brought by the maintenance of the session by the target SMF entity is reduced.

In a possible design, the terminal device may send the third registration indication to the UDM entity through the second AMF entity, for example, the terminal device may carry the third registration indication in an RRC message or a registration request, and send the third registration indication to the second AMF entity through the access network device, and the second AMF entity sends the third registration indication to the UDM entity by carrying the third registration indication in an update location request. In this way, the terminal device may successfully send a third registration indication to the UDM entity.

In one possible design, the third registration indication sent by the terminal device to the UDM entity through the second AMF entity may further inform the UDM entity to register with the second AMF entity.

By this design, the UDM entity may also register with the second AMF entity after receiving the third registration indication sent by the second AMF entity.

In a second aspect, an embodiment of the present application further provides a network communication method, where the method includes the following steps:

the method comprises the steps that a Unified Data Management (UDM) entity receives a first registration indication from a terminal device, wherein the first registration indication is used for indicating that the UDM entity reserves registration information of a first access and mobility management function (AMF) entity, the first AMF entity is responsible for mobility management when the terminal device accesses a first public continental mobile network (P L MN), and the first P L MN is a P L MN which the terminal device has accessed;

the UDM entity retains registration information of the first AMF entity according to the first registration indication.

In one possible design, the terminal device does not need to judge whether the terminal device has dual-connection capability before sending the first registration indication in the mobile communication system, in this case, the UDM entity determines that the terminal device has dual-connection capability before retaining the registration information of the second AMF entity according to the first registration indication, wherein the dual-connection capability is used for indicating that the terminal device supports accessing to the P L MN by adopting two access types of access technologies simultaneously.

In this way, the UDM entity may not only not perform de-registration on the first AMF entity but also perform registration on a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN under the condition that the terminal device has dual connectivity capability, thereby implementing dual registration of the first AMF entity and the second AMF entity.

In one possible design, the UDM entity may determine whether the terminal device has dual connectivity capability through connection capability indication information received from the terminal device.

By this design, the UDM entity can determine whether the terminal device has dual connectivity capability.

In one possible design, the UDM entity receives the first registration indication sent by the terminal device forwarded by the second AMF entity, where the second AMF entity is responsible for mobility management when the terminal device accesses the second P L MN.

In one possible design, the first registration indication may also inform the UDM entity to register with the second AMF entity.

By means of the design, after receiving the first registration instruction, the UDM entity may not only retain the registration information of the first AMF entity, but also register the second AMF entity.

In a third aspect, an embodiment of the present application further provides a network communication method, where the method includes the following steps:

firstly, a Unified Data Management (UDM) entity acquires a first access type of a first access technology adopted when a terminal device accesses a first public continental mobile network (P L MN) and a second access type of a second access technology adopted when the terminal device accesses a second P L MN, wherein the first P L MN is a P L MN which is accessed by the terminal device, the second P L MN is a P L MN to be accessed by the terminal device, the first access type is a third generation partnership project (3 GPP) access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type, and then when the UDM entity determines that the terminal device has dual-connection capability which is different from the first access type, the registration information of a first access and mobility management function AMF entity is reserved, wherein the first AMF entity is responsible for mobility management when the terminal device accesses the first P L MN, and the dual-terminal connection capability is used for representing that the terminal device simultaneously adopts two access technologies of the P L access technology.

By the method, under the condition that a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the UDM entity can determine that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN when the terminal device accesses the two P L MNs and the access types of the access technologies adopted when the terminal device accesses the two P L MNs are different, so that the UDM entity can not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also can not register the first AMF entity, thereby realizing double registration of the first AMF entity and the second AMF entity.

In one possible design, the UDM entity may obtain the second access type by, but is not limited to:

the first mode is as follows: the UDM entity may receive the second access type sent by the terminal device, where the second access type is determined by the terminal device.

In a second way, the UDM entity may receive the second access type sent by a second AMF entity, where the second AMF entity is responsible for mobility management when the terminal device accesses the second P L MN.

In the above manner, the UDM entity may determine the second access type when the terminal device is to access the second P L MN.

In one possible design, the UDM entity may store the second P L MN and the second access type after determining the second access type when the terminal device is to access the second P L MN by any of the above-mentioned manners, and accordingly, the UDM entity may also determine the first access type and store the first P L MN and the first access type when the terminal device is to access the first P L MN by any of the above-mentioned manners.

In one possible design, the UDM entity may also determine that the identity of the second P L MN is different from the identity of the first P L MN before the UDM entity retains the registration information of the first AMF entity.

In the mobile communication system, when the identifier of the first P L MN is different from the identifier of the second P L MN, and the second access type is different from the first access type, the AMF entity responsible for mobility management when the terminal device accesses the P L MN through the 3GPP access type and the AMF entity responsible for mobility management when the terminal device accesses the P L MN through the non-3GPP access type must be different from each other, so that, by the implementation, the UDM entity retains the registration information of the first AMF entity, i.e., does not register the first AMF, when it is determined that the second access type is different from the first access type, and the identifier of the second P L MN is different from the identifier of the first P L MN, and the terminal device has dual connectivity capability, so that, after the UDM entity successfully registers the second AMF entity, the UDM entity can simultaneously store the registration information of the two AMF entities responsible for management of the same terminal device, and the two registration technologies of the two AMF entities are respectively implemented through the two access technologies of the two access technologies, namely, the two access technologies of the registration entity and the two access technologies of the two access technologies are respectively L.

In one possible design, the first AMF entity is deregistered when the UDM entity determines at least one of: the terminal device does not have dual connection capability; the second access type is the same as the first access type.

Through the above design, the UDM entity can deregister the first AMF entity, i.e. delete the registration information of the first AMF entity in the UDM entity, so that the scheme can release the storage space occupied by the registration information of the first AMF entity in the UDM entity, and in addition, since the first AMF entity also deletes the context of the terminal device correspondingly in the process of deregistering the first AMF entity, the scheme can further release the storage space occupied by the context of the terminal device in the first AMF entity.

In one possible design, the first AMF entity is deregistered when the UDM entity determines at least one of that the terminal device does not have dual connectivity capability, that the second access type is the same as the first access type, and that the identity of the second P L MN is the same as the identity of the first P L MN.

In a possible design, the UDM entity may determine whether the terminal device has dual connectivity capability through the connectivity indication information reported by the terminal device.

In one possible design, the UDM entity notifies a first session management function, SMF, entity to release the session of the terminal device (e.g., sends a session release notification message to the first SMF entity), where the first SMF is responsible for session management when the terminal device accesses the first P L MN.

In one possible design, when the UDM entity determines that the identity of the first P L MN is different from the identity of the second P L MN, and the first access type is different from the second access type, it determines that the first AMF entity needs to be deregistered, and deregisters the first AMF entity.

Optionally, the UDM entity may determine that the first AMF entity needs to be deregistered by:

when the priority of the first P L MN is lower than a set P L MN priority threshold, the UDM determines that the first AMF entity needs to register;

when the priority of the session is lower than a set session priority threshold, the UDM determines that the first AMF entity needs to be registered;

and thirdly, the UDM entity determines the priority of the service established when the terminal equipment accesses the first P L MN, and when the priority of the service is lower than a set service priority threshold, the UDM determines that the first AMF entity needs to be unregistered.

Thus, when the UDM entity adopts the scheme provided by the first mode, the UDM entity can ensure that the P L MN with high priority is normally accessed through the comparison of the priority of the P L MN with the priority threshold of the P L MN, when the UDM entity adopts the scheme provided by the second mode, the UDM entity can ensure that the session with high priority is normally carried out through the comparison of the priority of the session with the priority threshold of the session, and when the UDM entity adopts the scheme provided by the third mode, the UDM entity can ensure that the service with high priority is normally carried out through the comparison of the priority of the service with the priority threshold of the service.

In one possible design, when the UDM entity determines that a target access type identical to the second access type exists in the first access type, deregistering a target AMF entity;

the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN accessed by the terminal device using an access technology belonging to the target access type.

Through the above design, when the terminal device has accessed the P L MN by using the access technologies corresponding to the two access types, if the terminal device needs to continue accessing the P L MN by using the access technology corresponding to one of the access types, the UDM entity deregisters the target AMF entity, so that, after the UDM entity successfully registers the second AMF entity, the UDM entity can ensure that the terminal device can simultaneously access the P L MN by using the access technologies of the two access types, that is, the UDM stores the registration information of the two AMF entities responsible for mobility management when the terminal device accesses the P L MN by using the access technologies of the two access types.

In one possible design, the UDM entity notifies the target SMF entity to release the session of the terminal device after determining to deregister the target AMF entity, where the target SMF entity is responsible for session management when the terminal device accesses the target P L MN.

In a fourth aspect, embodiments of the present application provide a terminal device, including means or units for performing the steps of the first aspect.

In a fifth aspect, embodiments of the present application provide a UDM entity, including a unit or means for performing the steps of the second aspect above.

In a sixth aspect, embodiments of the present application further provide a UDM entity, including a unit or means for performing the steps of the above third aspect.

In a seventh aspect, the present application provides a terminal device comprising at least one processing element and at least one memory element, wherein the at least one memory element is configured to store programs and data, and the at least one processing element is configured to perform the method provided in the first aspect of the present application.

In an eighth aspect, the present application provides a UDM entity comprising at least one processing element and at least one memory element, wherein the at least one memory element is configured to store programs and data, and wherein the at least one processing element is configured to perform the method provided in the second or third aspect of the present application.

In a ninth aspect, this embodiment of the present application further provides a computer storage medium, where a software program is stored, and the software program, when read and executed by one or more processors, may implement the method provided in the first aspect to the third aspect, or any one of the aspects.

In a tenth aspect, embodiments of the present application further provide a computer program product containing instructions, which when executed on a computer, cause the computer to perform the method of the above aspects.

In an eleventh aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a terminal device or a UDM entity to implement the functions recited in the foregoing aspects. In one possible design, the system-on-chip further includes a memory for storing necessary program instructions and data for the terminal device or the UDM entity. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

In the solution provided in this application, when a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device or the UDM entity may determine that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN when an access type to which an access technology adopted when the terminal device accesses the two P L MNs is different, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also may not de-register the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

Drawings

Fig. 1 is a diagram illustrating an architecture of a mobile communication system according to an embodiment of the present application;

fig. 2 is a flowchart of a network registration method according to an embodiment of the present application;

fig. 3 is a flowchart of a network deregistration method according to an embodiment of the present application;

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

fig. 5 is a flowchart of a second network communication method according to an embodiment of the present application;

fig. 6 is a structural diagram of a first terminal device according to an embodiment of the present application;

fig. 7 is a structural diagram of a UDM entity according to an embodiment of the present application;

fig. 8 is a structural diagram of a second UDM entity provided in an embodiment of the present application;

fig. 9 is a structural diagram of a second terminal device according to an embodiment of the present application;

fig. 10 is a structural diagram of a third UDM entity according to an embodiment of the present application.

Detailed Description

The application provides a network communication method and equipment, which are used for realizing that two AMF entities in charge of the same terminal equipment can be successfully registered in a UDM entity at the same time. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

In the solution provided in the embodiment of the present application, when a terminal device has accessed to a first P L MN and is to be accessed to a second P L MN, the terminal device or the UDM entity may determine that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses to the above two P L MNs when access types to which access technologies adopted by the terminal device are different, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses to the second P L MN, but also may not de-register the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

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

1) A terminal device, also known as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user. For example, the terminal device includes a handheld device, an in-vehicle device, and the like having a wireless connection function. Currently, the terminal device may be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (smart security), a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like.

2) Each P L MN has a unique identifier for identifying the P L MN, and the identifiers of different P L MNs are different.

In order to distinguish the P L MN accessed by the terminal device from the P L MN to be accessed, in the present application, a first P L0 MN and a second P L1 MN are named respectively, where the first P L MN is the P L MN accessed by the terminal device, and certainly, the number of the P L MN accessed by the terminal device may be one or multiple, which is not limited in this application, and the second P L MN is the P L MN to be accessed by the terminal device, since the terminal device is generally accessed to one P L MN at a time when accessing the P L MN, in the present application, the description is given by taking the number of the second P L MN as an example.

3) The access types can be distinguished according to the types of the wireless access networks. The wireless access network comprises a 3GPP access network and a non-3GPP access network, and correspondingly, the access types comprise a 3GPP access type and a non-3GPP access type.

The terminal device may access the P L MN. through an access technology corresponding to a 3GPP access type, for example, the access technology corresponding to the 3GPP access type includes a Universal Mobile Telecommunications System (UMTS) terrestrial radio access Network (UTRAN) access technology, or an evolved UTRAN (E-UTRAN) access technology, etc.;

the terminal device may access the P L MN. through AN access technology corresponding to a non-3GPP access type, for example, the access technology corresponding to the non-3GPP access type includes a wireless local access Network (W L AN) access technology, a Worldwide Interoperability for Microwave Access (WIMAX) access technology, and the like.

4) The first access type is an access type of a first access technology adopted when the terminal equipment accesses the first P L MN.

Since the number of the first P L MN may be one or multiple, when the number of the first P L MN is multiple, the first access technology that may be adopted when the terminal device accesses each first P L MN is also different, and further, the access type to which each first access technology belongs may also be different, and therefore, the number of the first access types may be two.

For example, the terminal device may access P L MN 1 by using AN E-UTRAN access technology, and may access the P L MN 1 again by using a W L AN access technology without disconnecting the P L MN 1.

In summary, the number of the access types included in the first access type may be one or two, that is, the first access type includes a 3GPP access type and/or a non-3GPP access type.

5) Generally, the terminal device generally adopts an access technology every time the terminal device accesses a P L MN, and therefore the second access type includes one access type, namely the second access type is a 3GPP access type or a non-3GPP access type.

Since the first access type includes one or two access types and the second access type includes one access type, the first access types each include one access type in the scenario (for example, the second access type is different from or the same as the first access type) in which the second access type is compared with the first access type. For example, this can be done according to the following principle:

for example, when the first access type is a 3GPP access type and the second access type is a 3GPP access type, the second access type is the same as the first access type. And when the first access type is a non-3GPP access type and the second access type is a non-3GPP access type, the second access type is the same as the first access type.

For another example, when the first access type is a 3GPP access type and the second access type is a non-3GPP access type, the second access type is different from the first access type. The first access type is a non-3GPP access type, and the second access type is different from the first access type when the second access type is a 3GPP access type.

When two access types are included in the first access type, the first access type and the second access type are not in a comparative relationship but in an inclusion relationship.

For example, when the first access type includes a 3GPP access type and a non-3GPP access type, and the second access type is a 3GPP access type, it can be derived that: the first access type has an access type identical to the second access type.

6) Dual connectivity, indicating that the terminal device supports access to P L MN. using both access types of access technologies, e.g. the dual connectivity of the terminal device is set by the manufacturer of the terminal device and may not be set by the user.

7) The registration information of the AMF entity stored in the UDM may include at least one of an identifier of the AMF entity, an identifier of a P L MN accessed by a terminal device responsible for the AMF entity, an identifier of the terminal device, and an access type to which an access technology adopted when the terminal device accesses the P L MN.

8) "and/or" describe the association relationship of the associated objects, indicating that there may be three relationships, e.g., a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the present application, the plural number means two or more.

In addition, it is to be understood that the terms first, second, etc. in the description of the present application are used for distinguishing between the descriptions and not necessarily for describing a sequential or chronological order.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 1 shows an architecture of a possible mobile communication system to which the network communication method provided in the embodiment of the present application is applied. Referring to fig. 1, the mobile communication system includes a radio access network and a core network. The radio access network comprises two types: a 3GPP access network 101 and a non-3GPP access network 102.

The radio access network is configured to provide a service related to radio access for the terminal device 109. Wherein the content of the first and second substances,

the 3GPP access network 101 may include: universal Mobile Telecommunications System (UMTS) terrestrial radio access network (UTRAN), evolved-UTRAN (E-UTRAN), or the like;

the non-3GPP access network 102 may comprise a W L AN or WIMAX network, or the like.

Since the radio access network in the mobile communication system includes the above two types, the terminal device 109 may select the 3GPP access network 101 and/or the non-3GPP access network 102 to provide a radio access service for the terminal device, which is not limited in this application.

In addition, the radio access network includes an access network device therein, and is used for communicating with the accessed terminal device 109.

The access network device in the 3GPP access network 101 may be referred to as a 3GPP access network device, or a base station, for example: a gbb, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), and the like.

The access network devices in the non-3GPP access network 102 may be referred to as non-3GPP access network devices, or Access Points (APs), for example: a wireless fidelity (Wifi) AP, a WIMAX AP, and the like.

The core network is configured to access the terminal device 109 to a Data Network (DN) 108 that can implement a service of the terminal device 109. Two types of network elements are included in the core network: a control plane network element and a user plane network element. The control plane network element is used for realizing functions of session management, access and mobility management, or policy control and the like; the user plane network element is configured to forward user plane data of the terminal device 109.

Optionally, the control plane network element may include, but is not limited to, the following network elements according to different implemented logical functions: an AMF entity 103, a Session Management Function (SMF) entity 104, a UDM entity 105, and a non-3GPP interworking function (N3 IWF) entity 106, as shown.

The AMF entity 103 is responsible for authentication of the terminal device 109, mobility management when accessing a network, and the like;

the SMF entity 104 is responsible for session management, such as session creation, modification, deletion, and selection of a user plane network element.

The UDM entity 105 is configured to manage subscription data of the terminal device 109 and registration information related to the terminal device 109, and is responsible for policy control decision and other functions.

An N3IWF entity 106, configured to provide an interworking function for a terminal device 109, so that the terminal device 109 may access the core network through the non-3GPP access network 102.

Optionally, the user plane network element, also called a User Plane Function (UPF) entity 107, is mainly responsible for processing user plane data of the terminal device 109, such as forwarding, charging, and the like.

A Data Network (DN) 108, which provides Service to the terminal device 109 by performing data transmission with the terminal device 109, where the DN may be a PDN network, such as the Internet (Internet), an IP Multimedia Service (IMS) network, and the like.

In addition, in the mobile communication system, the terminal device 109, the radio access network, each network element in the core network, and the DN108 are connected through corresponding interfaces, as shown in fig. 1, which is not described herein again.

It should be noted that, in the embodiment of the present application, a distribution form of each functional entity in the control plane network element is not limited, and optionally, the control plane network element may also include other functional entities that can be formed after any multiple network elements are fused, for example, a functional entity having two functions of session management and policy control, or a functional entity having three functions of session management, access and mobility management and policy control, and the like.

In the mobile communication system shown in fig. 1, the terminal device may complete the registration of the UDM entity with the AMF entity through a network registration procedure shown in fig. 2, and the access P L MN. is shown in fig. 2, where the network registration procedure includes:

s201, the terminal device needs to realize a certain service or connect DN by accessing P L MN, or when the terminal device is started, it sends Radio Resource Control (RRC) message carrying radio parameters and registration request to the access network device to start the network registration process.

Optionally, the wireless parameters include an identifier of the terminal device (e.g., a user permanent identifier (SUPI), or a user temporary identifier (subscriber temporary identifier)), and an identifier of the P L MN.

Optionally, the registration request also includes the terminal device identifier and the identifier of the P L MN.

Optionally, in the radio parameters and the registration request, the identity of the P L MN may be included in the terminal device identity.

The terminal device identifier may be carried in information sent in a subsequent step to identify that the step is performed for the terminal device.

S202: after receiving the RRC message, the access network equipment acquires the radio parameters and the registration request carried in the RRC message; and the access network equipment selects an AMF entity for providing mobility management for the terminal equipment according to the wireless parameters.

S203: and the access network equipment sends an N2 message carrying the N2 parameter and the registration request to the AMF entity. The N2 parameter includes a location of the terminal device and an access type to which an access technology adopted by the terminal device belongs.

S204, the AMF entity acquires the registration information after receiving the N2 message, and sends an update position request (update L update request) carrying the registration information to the UDM entity according to the registration request in the N2 message.

Optionally, the registration information includes at least one of the terminal device identifier, the identifier of the AMF entity, the identifier of the P L MN, and the access type.

S205: and after receiving the position updating request, the UDM entity stores the registration information.

S206: the UDM entity sends an update location response (update location response) to the AMF entity to notify the AMF entity that the UDM entity successfully registers with the AMF entity.

Optionally, the updated location response carries subscription data of the terminal device. In this way, the AMF entity may store the subscription data of the terminal device after receiving the update location response.

S207: and the AMF entity sends a registration accept (registration accept) message to the terminal equipment through the access network equipment so as to inform the terminal equipment of successful registration to the network.

S208: and the terminal equipment sends a registration completion (registration complete) message to the AMF entity through the access network equipment so as to inform the AMF entity that the network registration process is finished.

In the mobile communication system, the terminal device may complete de-registration of the UDM entity with the AMF entity responsible for mobility management of the terminal device through a network de-registration procedure shown in fig. 3. Referring to fig. 3, the network de-registration process includes:

s301: the UDM entity sends a cancel location request (cancel location request) carrying the terminal device identifier to the AMF entity that needs to be unregistered.

S302: and after receiving the position canceling request, the AMF entity deletes the context of the terminal equipment. The context of the terminal device comprises at least one of the terminal device identification, the subscription data of the terminal device and the registration area of the terminal device.

When the terminal equipment has session connection, the AMF entity also starts a session flow for releasing the terminal equipment (initiates a notification to an SMF entity in charge of session management of the terminal equipment so as to trigger the SMF entity to initiate the session flow for releasing).

S303: the AMF entity sends a cancel location response (cancel location response) to the UDM entity to inform the UDM entity that the AMF entity can be unregistered.

S304: and the UDM entity deletes the registration information of the AMF entity to finish the de-registration of the AMF entity.

It should be noted that, in the embodiment of the present application, the communication method provided in the embodiment of the present application may be completed through the above procedure.

In the method, a terminal device may determine, according to a logical judgment, whether a UDM entity needs to deregister with a first AMF entity, where the first AMF entity is responsible for mobility management when the terminal device accesses an accessed first P L MN, and referring to fig. 4, the flow of the method includes:

s401, the terminal equipment obtains a first access type of a first access technology adopted when accessing a first P L MN and a second access type of a second access technology adopted when accessing a second P L MN.

The first P L MN is a P L MN to which the terminal device has access, the second P L MN is a P L MN to which the terminal device is to be accessed, the first access type is a 3GPP access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type.

Alternatively, the terminal device may select the second P L MN. through an automatic network selection mode, and the second P L MN may be a registered P L0 MN (registered P L1 MN, RP L2 MN), a P L4 MN (equivalent P L5 MN, EP L6 MN) equivalent to a currently selected P L3 MN, a P L7 MN (home P L8 MN, HP L9 MN) to which a Universal Subscriber Identity Module (USIM) card installed in the terminal device belongs, a P L MN (equivalent HP L, EHP L MN) equivalent to an HP L MN, a P L MN stored in a P L MN list in the USIM card, or a P L MN stored in a P L MN list set by an operator in the USIM card, which is not limited in this application.

Optionally, the terminal device may obtain the second access type by:

the first mode is as follows:

the terminal equipment sends a request carrying position information of the terminal equipment to an Access Network Discovery and Selection Function (ANDSF) entity in the mobile communication system;

the ANDSF entity provides information of access networks which can be used nearby the terminal equipment (including access technologies adopted by the terminal equipment to access the access networks and/or access types of the access technologies) to the terminal equipment according to operator policies;

the terminal device may determine the second access type according to information of an access network provided by the ANDSF entity. For example, after the terminal device determines an access technology adopted by the terminal device to access the access network, the second access type to which the access technology belongs is determined according to a corresponding relationship between the access type and the access technology contained in the access technology.

The second mode is as follows:

the terminal equipment selects target access network equipment with high signal transmission efficiency by measuring the received signals sent by the 3GPP access network equipment and the signals sent by the non-3GPP access network equipment;

Correspondingly, the terminal device may also determine the first access type by using any of the above manners when the terminal device is to access the first P L MN, and store the first P L MN and the first access type.

According to the difference in the number of the access types included in the first access type and the difference in the relationship between the first access type and the second access type, the following mutually independent scenarios are included in the embodiment of the present application. The method provided by the embodiment of the application can comprise a method executed under any scene. Wherein, the first scenario, the second scenario and the third scenario are all under the condition that the first access type comprises one access type. Scenario four is when two access types are included in the first access type.

Scene one:

s402a, when the terminal device determines that the second access type is different from the first access type, sending a first registration indication to a UDM entity, wherein the first registration indication is used for indicating the UDM entity to reserve registration information of a first AMF entity, and the first AMF entity is responsible for mobility management when the terminal device accesses the first P L MN.

Through S402a, in a case where the terminal device accesses the same P L MN through two access types, or in a case where the terminal device accesses different P L MNs through two access types, respectively, the terminal device may instruct the UDM entity to retain the registration information of the first AMF entity.

Optionally, the terminal device may send the first registration indication to the UDM entity by:

and the terminal equipment sends the first registration indication to the UDM entity through the second AMF entity, wherein the second AMF entity is responsible for mobility management when the terminal equipment accesses the second P L MN.

Optionally, the first registration instruction sent by the second AMF entity to the UDM entity may further notify the UDM entity to register the second AMF entity.

Optionally, the terminal device may send the first registration indication to the UDM entity through a network registration procedure shown in fig. 2 (where the AMF entity shown in fig. 2 is a second AMF entity in this embodiment of the present application). For example, in S201, the first registration indication may be carried in the RRC message or the registration request; in S203, the first registration instruction may be carried in the N2 message or the registration request; in S204, the first registration indication may be carried in the update location request.

By the method, the first registration instruction not only indicates that the UDM entity does not perform deregistration on the first AMF entity, but also triggers the UDM entity to perform registration on the second AMF entity through a process of sending the first registration instruction.

In the mobile communication system, when the terminal device accesses the same P L MN through access technologies corresponding to two different access types, the AMF entity responsible for mobility management when the terminal device accesses the P L MN through the 3GPP access type may be a different AMF entity from the AMF responsible for mobility management when the terminal device accesses the P L MN through the non-3GPP access type, so that, through the above step S402a, the terminal device, when determining that the second access type is different from the first access type, instructs the UDM entity to retain registration information of the first AMF, that is, does not de-register the first AMF, so that, after the UDM entity successfully registers the second AMF entity, the UDM entity may simultaneously store registration information of two AMF entities responsible for mobility management of the same terminal device, and the terminal device may implement simultaneous adoption of access technologies corresponding to two different access types, and access the P L MN. through the two AMF entities, in addition, the scheme may avoid initiation of the terminal device of a frequent signaling procedure, and reduce unnecessary network signaling overhead.

Optionally, in a first possible implementation manner, before the terminal device sends the first registration instruction, the method further includes:

the terminal device determines that the identity of the second P L MN is different from the identity of the first P L MN.

In the mobile communication system, when the identifier of the first P L MN is different from the identifier of the second P L MN, and the second access type is different from the first access type, the AMF entity responsible for mobility management when the terminal device accesses P L MN through the 3GPP access type and the AMF entity responsible for mobility management when the terminal device accesses P L MN through the non-3GPP access type are necessarily different AMF entities, so that, by this implementation, the terminal device instructs the UDM entity to retain the registration information of the first AMF, i.e., to not register the first AMF, in case that the second access type is different from the first access type and the identifier of the second P L MN is different from the identifier of the first P L MN, after the UDM entity successfully registers the second AMF entity, the UDM entity can simultaneously retain the registration information of the two AMF entities responsible for mobility management of the same terminal device, and the terminal device can simultaneously adopt two different registration techniques and avoid unnecessary initiation of the additional amp signaling procedures L MN..

Optionally, in a second possible implementation manner, before the terminal device sends the first registration instruction, it is further required to determine that the following condition is satisfied:

the terminal device determines that the terminal device has dual connection capability, wherein the dual connection capability is used for indicating that the terminal device supports access to a P L MN by adopting two access technologies of two access types simultaneously.

Further, the dual connectivity capability may also indicate that the terminal device supports access to two different P L MNs using two access types of access technologies simultaneously.

Wherein whether the terminal device has dual connectivity capability may be preconfigured. Therefore, the terminal device can acquire the configuration information of the terminal device and determine whether the terminal device has the dual connection capability.

If the terminal device has dual connectivity, the terminal device may access P L MN. using two access technologies at the same time, and thus, in this implementation manner, after determining that the terminal device has dual connectivity, the terminal device instructs the UDM entity not to de-register the first AMF entity, and after registering the second AMF entity, the UDM entity may simultaneously store registration information of two AMF entities responsible for mobility management of the same terminal device, and the terminal device may access P L MN using two access technologies.

S403 a: and after the UDM entity receives the first registration instruction from the terminal equipment, the UDM entity reserves the registration information of the first AMF entity according to the first registration instruction.

Optionally, the terminal device may further notify the UDM entity to register the second AMF entity, where the first registration instruction is sent to the UDM entity by the second AMF entity. Therefore, the UDM entity may further register the second AMF entity (store the registration information of the second AMF entity) after receiving the first registration indication sent by the second AMF entity.

Optionally, in the mobile communication system, the terminal device may adopt the second implementation manner, that is, when the terminal device determines that the terminal device has the dual connectivity capability, the terminal device sends the first registration instruction again, so that after receiving the first registration instruction, the UDM entity may not need to determine whether the terminal device has the dual connectivity capability again, and may directly retain the registration information of the first AMF entity.

Optionally, in the mobile communication system, the terminal device may not adopt the second implementation manner described above, that is, the terminal device does not need to determine whether itself has dual connectivity capability before sending the first registration instruction, in this case, before performing S402a, according to the first registration instruction, the UDM entity retains the registration information of the first AMF entity, and further includes the following steps:

and the UDM entity determines that the terminal equipment has double connection capability.

For example, the terminal device may send, through a network registration procedure as shown in fig. 2 (where the AMF entity shown in fig. 2 is a second AMF entity in this embodiment), connection capability indication information to the UDM entity, where the connection capability indication information is used to indicate whether the terminal device has dual connection capabilities. For example, in S201, the connection capability indication information may be carried in the RRC message or the registration request. In S203, the connection capability indication information may be carried in the N2 message or the registration request. In S204, the connection capability indication information may be carried in the update location request. And after acquiring the connection capability indication information sent by the terminal equipment, the UDM entity can determine whether the terminal equipment has dual connection capability according to the connection capability indication information.

In this way, the UDM entity may not only perform de-registration on the first AMF entity but also perform registration on a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN when the terminal device has dual connectivity capability, thereby implementing dual registration of the first AMF entity and the second AMF entity.

In the first scenario of this application, in a case where a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device may determine, when access types to which access technologies adopted when the terminal device accesses the two P L MNs are different, that the UDM entity still retains registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also may not deregister the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

Scene two:

s402 b: and when the terminal equipment determines that at least one of the following conditions is met, sending a second registration indication to the UDM entity. Wherein the second registration indication is used to instruct the UDM entity to deregister the first AMF entity.

Optionally, the condition includes at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type.

Optionally, the conditions include the following three:

sending a second registration indication to the UDM entity when the terminal device determines at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

the identity of the second P L MN is the same as the identity of the first P L MN.

The terminal device can only access the newly requested second P L MN even if the terminal device sends the first registration indication to the UDM entity when the terminal device does not have the dual connection capability, so that the registration information of the first AMF entity retained by the UDM entity and the context of the terminal device maintained in the first AMF entity occupy the storage space of the UDM entity and the first AMF entity, and the first AMF entity needs to maintain the context of the terminal device.

S403 b: and after receiving the second registration instruction from the terminal equipment, the UDM entity performs deregistration on the first AMF entity.

Through the above steps, the UDM entity may deregister the first AMF entity, that is, delete the registration information of the first AMF entity in the UDM entity, so that the scheme may release the storage space occupied by the registration information of the first AMF entity in the UDM entity; in addition, since the first AMF entity also deletes the context of the terminal device correspondingly in the process of deregistering the first AMF entity, the scheme may further release the storage space occupied by the context of the terminal device in the first AMF entity. In summary, the method may avoid waste of storage spaces in the UDM entity and the first AMF entity, and avoid signaling overhead caused by the first AMF entity for maintaining the context of the terminal device.

Optionally, the second registration instruction is further configured to trigger the UDM entity to notify a first SMF entity to release the session of the terminal device, where the first SMF entity is responsible for session management when the terminal device accesses the first P L MN.

Optionally, after receiving the second registration instruction, the UDM entity sends a session release notification message to the first SMF entity to notify the first SMF entity to release the session of the terminal device.

In the scheme of scenario two in the embodiment of the present application, when a terminal device has accessed to a first P L MN and is to be accessed to a second P L MN, the terminal device determines that a condition for sending a first registration instruction is not satisfied currently, and then sends a second registration instruction to the UDM entity, and notifies the UDM entity to perform de-registration on a first AMF entity in charge of mobility management when the terminal device accesses to the first P L MN.

It should be noted that, in the scenario one and the scenario two, the UDM entity may determine whether the terminal device has dual connectivity capability through the connectivity indication information reported by the terminal device.

Scene three:

s402 c: and when the terminal equipment determines that the second access type is different from the first access type, sending a second registration indication to the UDM entity.

Optionally, the terminal device may determine whether to send the second registration instruction to the UDM entity by:

when the priority of the first P L MN is lower than a set P L MN priority threshold, the terminal equipment decides to send the second registration instruction to the UDM entity;

and the terminal equipment determines the priority of the service established when the terminal equipment is accessed to the first P L MN, and determines to send the second registration instruction to the UDM entity when the priority of the service is lower than a set service priority threshold.

Thus, when the terminal equipment adopts the scheme provided by the first mode, the terminal equipment can ensure that the P L MN with high priority is normally accessed through the comparison of the priority of the P L MN with the priority threshold of the P L MN, when the terminal equipment adopts the scheme provided by the second mode, the terminal equipment can ensure that the session with high priority is normally carried out through the comparison of the priority of the session with the priority threshold of the session, and when the terminal equipment adopts the scheme provided by the third mode, the terminal equipment can ensure that the service with high priority is normally carried out through the comparison of the priority of the service with the priority threshold of the service.

S403 c: and after receiving the second registration instruction from the terminal equipment, the UDM entity performs deregistration on the first AMF entity.

Optionally, in scenario two and scenario three, the terminal device may send the second registration indication to the UDM entity through the second AMF entity. The second registration indication may also inform the UDM entity to register the second AMF entity. In this way, after receiving the second registration instruction, the UDM entity may perform registration on the second AMF entity as well as deregistration on the first AMF entity.

Optionally, similar to the function and operation of the second registration indication in scenario two, in addition, the second registration indication in scenario three may also be used to trigger the UDM entity to notify the first SMF entity to release the session of the terminal device.

It should be noted that, in scenario two and scenario three, the terminal device may also send the second registration indication to the UDM entity through a network registration procedure shown in fig. 2 (where the AMF entity shown in fig. 2 is the second AMF entity in this embodiment of the present application). For example, in S201, the second registration indication may be carried in the RRC message or the registration request; in S203, the second registration instruction may be carried in the N2 message or the registration request; in S204, the second registration indication may be carried in the update location request.

In addition, by the above method, the second registration instruction not only indicates that the UDM entity deregisters the first AMF entity, but also triggers the UDM entity to register the second AMF entity through a process of sending the second registration instruction.

In addition, it should be noted that, in scenario two and scenario three of the present application, the UDM entity may complete the deregistration of the first AMF entity through a network deregistration process as shown in fig. 3 (where the AMF entity shown in fig. 3 is the first AMF entity in the present application), and for a specific process, reference may be made to the above description of each step in fig. 3, which is not described herein again.

Scene four:

s402d, when the terminal device determines that a target access type which is the same as the second access type exists in the first access type, sending a third registration indication to the UDM entity, wherein the third registration indication is used for indicating the UDM entity to perform de-registration on a target AMF entity, the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN accessed by the terminal device by adopting an access technology belonging to the target access type.

Optionally, the third registration instruction may further notify the UDM entity to register the second AMF entity. In this way, after receiving the third registration instruction, the UDM entity may perform registration to the second AMF entity as well as deregister the target AMF entity. Optionally, the terminal device may send the third registration indication to the UDM entity through the second AMF entity.

Optionally, the terminal device may also send the third registration instruction to the UDM entity through a network registration procedure shown in fig. 2 (where the AMF entity shown in fig. 2 is a second AMF entity in this embodiment of the present application). For example, in S201, the third registration indication may be carried in the RRC message or the registration request; in S203, the third registration instruction may be carried in the N2 message or the registration request; in S204, the third registration indication may be carried in the update location request.

Through the method, the third registration instruction not only indicates that the UDM entity deregisters the target AMF entity, but also triggers the UDM entity to register the second AMF entity through a process of sending the third registration instruction.

For example, when the first access type includes a 3GPP access type and a non-3GPP access type, and the second access type includes a 3GPP access type, the target P L MN is a P L MN accessed by the terminal device in the first P L MN by using an access technology belonging to the 3GPP access type, and the target AMF entity is responsible for mobility management when the terminal device accesses the target P L MN.

S403 d: and after receiving the third registration instruction from the terminal equipment, the UDM entity performs deregistration on the target AMF entity.

Optionally, the third registration indication is further used to trigger the UDM entity to notify a target SMF entity to release the session of the terminal device, where the target SMF entity is responsible for session management when the terminal device accesses the target P L MN.

Optionally, the UDM entity may use a network deregistration process shown in fig. 3 (where the AMF entity shown in fig. 3 is the target AMF entity in this embodiment of the present application), to complete deregistration of the target AMF entity, and for a specific process, reference may be made to the above description of each step in fig. 3, which is not described herein again.

In the scenario of the fourth aspect of the present application, when the terminal device has accessed to the P L MN by using the access technologies corresponding to the two access types, if the terminal device needs to continue to access to the P L MN by using the access technology corresponding to one of the access types, the terminal device may notify the UDM entity of deregistration of the target AMF entity through the third registration instruction.

In the method, the UDM entity may decide whether to de-register itself with a first AMF entity according to a logical judgment, wherein the first AMF entity is responsible for mobility management when the terminal device accesses an accessed first P L MN, and referring to fig. 5, the flow of the method includes:

s501, the UDM entity obtains a first access type of a first access technology adopted when the terminal equipment accesses a first P L MN and a second access type of a second access technology adopted when the terminal equipment accesses a second P L MN.

Optionally, the UDM entity may obtain the second access type, but is not limited to the following:

the first mode is as follows: the UDM entity may receive the second access type sent by the terminal device, where the second access type is determined by the terminal device. For example, the terminal device may acquire the second access type in two ways in the embodiment shown in fig. 4. Optionally, the terminal device may send the second access type to the UDM entity through S201 to S204 in a network registration procedure shown in fig. 2.

In a second manner, the UDM entity may receive the second access type sent by a second AMF entity, where the second AMF entity is responsible for mobility management when the terminal device accesses the second P L MN, for example, the second AMF entity may carry the second access type in the update location request and send the update location request to the UDM entity when the second AMF entity is in S204 in the network registration procedure shown in fig. 2.

Optionally, in the second manner, the second AMF may determine a second access technology used when the terminal device accesses the second P L MN, and determine the second access type to which the second access technology belongs.

Correspondingly, the UDM entity may also determine the first access type by using any of the above manners when the terminal device is to access the first P L MN, and store the first P L MN and the first access type.

Scene one:

s502, 502a, when the UDM entity determines that the terminal device has dual connection capability and the second access type is different from the first access type, the registration information of an AMF (mobility management function) entity with a first access and mobility management function is reserved, wherein the AMF entity is responsible for mobility management when the terminal device accesses the first P L MN, and the dual connection capability is used for indicating that the terminal device supports accessing to the P L MN by adopting access technologies of the two access types at the same time.

Through S502a, in a case where the terminal device accesses the same P L MN through two access types, or in a case where the terminal device accesses different P L MNs through two access types, respectively, the UDM entity may retain the registration information of the first AMF entity.

If the terminal device has dual connectivity, the terminal device may access P L MN. using two access technologies at the same time, and thus, in this implementation manner, the UDM entity does not deregister the first AMF entity after determining that the terminal device has dual connectivity, and after registering the second AMF entity, the UDM entity may simultaneously store registration information of two AMF entities responsible for mobility management of the same terminal device, and the terminal device may access P L MN using two access technologies.

In the mobile communication system, when the terminal device accesses the same P L MN through access technologies corresponding to two different access types, an AMF entity responsible for mobility management when the terminal device accesses the P L MN through a 3GPP access type may be a different AMF entity from an AMF entity responsible for mobility management when the terminal device accesses the P L MN through a non-3GPP access type, and therefore, through the step S502a, the UDM entity may retain registration information of the first AMF entity, that is, may not register the first AMF entity, when it is determined that the second access type is different from the first access type and the terminal device has a dual connectivity capability.

In one possible implementation manner, before the UDM entity retains the registration information of the first AMF entity, the method further includes:

the UDM entity determines that the identity of the second P L MN is different from the identity of the first P L MN.

In the mobile communication system, when the identifier of the first P L MN is different from the identifier of the second P L MN, and the second access type is different from the first access type, the AMF entity responsible for mobility management when the terminal device accesses P L MN through the 3GPP access type and the AMF entity responsible for mobility management when the terminal device accesses P L MN through the non-3GPP access type are necessarily different AMF entities, so that, by this implementation, the UDM entity retains the registration information of the first AMF entity, i.e., does not register the first AMF entity, when it is determined that the second access type is different from the first access type and the identifier of the second P L MN is different from the identifier of the first P L MN and the terminal device has dual connectivity capability, so that, after the UDM entity successfully registers the second AMF entity, the UDM entity can simultaneously store the registration information of the two AMF entities of the same terminal device, and the registration overhead of the terminal device can be reduced by adopting two additional registration techniques L MN. corresponding to avoid the additional registration of the two AMF entities.

In the foregoing manner, the UDM entity may acquire the identifier of the second P L MN in the following manner:

optionally, the terminal device may send the identifier of the second P L MN to the UDM entity through S201 to S204 in the network registration procedure shown in fig. 2.

In a second manner, the UDM entity may receive the identifier of the second P L MN sent by the second AMF entity, for example, the second AMF entity may send the identifier of the second P L MN to the UDM entity in the update location request when the second AMF entity is in S204 of the network registration procedure shown in fig. 2.

Correspondingly, when the terminal device is to access the first P L MN, the UDM entity may also determine the identifier of the first P L MN in any of the above manners, and store the identifier of the first P L MN.

In the first scenario of the present application, in a situation where a terminal device has access to a first P L MN and is to be accessed to a second P L MN, the UDM entity may determine that the terminal device has dual connectivity capability, and when the access types of the access technologies adopted when the terminal device accesses to the two P L MNs are different, it is determined that the UDM entity still maintains registration information of a first AMF entity responsible for mobility management when the terminal device accesses to the first P L MN, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses to the second P L MN, but also may not register the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

Scene two:

s502 b: deregistering the first AMF entity when the UDM entity determines that either of the following conditions is met.

Optionally, the condition includes at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type.

Optionally, the conditions include at least one of the following three:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

The terminal device can only access the newly requested second P L MN even if the UDM entity retains the registration information of the first AMF entity when the terminal device does not have the dual connection capability, so that the registration information of the first AMF entity retained by the UDM entity and the context of the terminal device maintained in the first AMF entity occupy the storage space of the UDM entity and the first AMF entity, and the context of the terminal device needs to be maintained by the first AMF entity.

In the solution of scenario two in the embodiment of the present application, when a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the UDM entity determines that a condition for retaining registration information of a first AMF entity is not satisfied currently, and then the UDM entity performs de-registration on the first AMF entity.

It should be noted that, in the scenario one and the scenario two, the UDM entity may determine whether the terminal device has dual connectivity capability through the connectivity indication information reported by the terminal device. For example, the terminal device may send, through a network registration procedure as shown in fig. 2 (where the AMF entity shown in fig. 2 is a second AMF entity in this embodiment), connection capability indication information to the UDM entity, where the connection capability indication information is used to indicate whether the terminal device has dual connection capabilities. For example, in S201, the connection capability indication information may be carried in the RRC message or the registration request. In S203, the connection capability indication information may be carried in the N2 message or the registration request. In S204, the connection capability indication information may be carried in the update location request. And after acquiring the connection capability indication information sent by the terminal equipment, the UDM entity can determine whether the terminal equipment has dual connection capability according to the connection capability indication information.

Scene three:

s502c, when the UDM entity determines that the identification of the first P L MN is different from the identification of the second P L MN and the first access type is different from the second access type, determining that the first AMF entity needs to be unregistered, and performing unregistration on the first AMF entity.

when the priority of the first P L MN is lower than a set P L MN priority threshold, the UDM determines that the first AMF entity needs to be unregistered;

when the priority of the session is lower than a set session priority threshold, the UDM determines that the first AMF entity needs to be unregistered;

and thirdly, the UDM entity determines the priority of the service established when the terminal equipment is accessed to the first P L MN, and determines that the first AMF entity needs to be unregistered when the priority of the service is lower than a set service priority threshold.

Optionally, in a second scenario and a third scenario of the embodiment of the present application, in a case that the UDM entity determines to deregister the first AMF entity, the UDM entity may further notify a first SMF entity to release the session of the terminal device, where the first SMF is responsible for session management when the terminal device accesses the first P L MN.

Scene four:

s502 d: and when the UDM entity determines that the target access type which is the same as the second access type exists in the first access type, performing de-registration on the target AMF entity.

The target AMF entity is responsible for mobility management when the terminal equipment accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN accessed by the terminal equipment by adopting an access technology belonging to the target access type.

Optionally, after determining to deregister the target AMF entity, the UDM entity notifies the target SMF entity to release the session of the terminal device, where the target SMF entity is responsible for session management when the terminal device accesses the target P L MN.

In the scenario four of the present application, when the terminal device has accessed to the P L MN using the access technologies corresponding to two access types, if the terminal device needs to continue to access to the P L MN using the access technology corresponding to one of the access types, the UDM entity deregisters the target AMF entity.

Based on the above embodiments, the present application further provides a terminal device, where the terminal device is configured to implement the network communication method shown in fig. 4, and may execute the method steps executed by the terminal device in the method. Referring to fig. 6, the terminal device 600 includes: an acquisition unit 601 and a processing unit 602, wherein,

an obtaining unit 601, configured to obtain a first access type to which a first access technology adopted when a first P L MN is accessed belongs and a second access type to which a second access technology adopted when a second P L MN is accessed belongs, where the first P L MN is a P L MN to which the terminal device 600 has been accessed, the second P L MN is a P L MN to which the terminal device 600 is to be accessed, the first access type is a 3GPP access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

a processing unit 602, configured to send a first registration indication to the UDM entity when it is determined that the second access type is different from the first access type, where the first registration indication is used to indicate that the UDM entity reserves registration information of a first access and mobility management function, AMF, entity, and the first AMF entity is responsible for mobility management when the terminal device 600 accesses the first P L MN.

Optionally, the processing unit 602 is further configured to:

determining that the identity of the second P L MN is different from the identity of the first P L MN prior to sending the first registration indication to the UDM entity.

Optionally, the processing unit 602 is further configured to:

before sending the first registration indication to the UDM entity, determining that the terminal device 600 has dual connectivity capability, where the dual connectivity capability is used to indicate that the terminal device 600 supports access to a P L MN by using two access types simultaneously.

Optionally, the processing unit 602 is further configured to:

sending a second registration indication to the UDM entity when at least one of:

the terminal device 600 does not have dual connectivity;

the second access type is the same as the first access type;

the second registration indication is used to instruct the UDM entity to deregister the first AMF entity, and the dual connectivity capability is used to indicate that the terminal device 600 supports access to a P L MN by using two access technologies simultaneously.

Optionally, the processing unit 602 is further configured to:

the terminal device 600 does not have dual connectivity;

the second access type is the same as the first access type;

the identity of the second P L MN is the same as the identity of the first P L MN;

Optionally, the second registration instruction is further configured to trigger the UDM entity to notify a first session management function, SMF, entity to release the session of the terminal device 600, where the first SMF entity is responsible for session management when the terminal device 600 accesses the first P L MN.

Optionally, the processing unit 602 is further configured to:

when it is determined that a target access type which is the same as the second access type exists in the first access type, sending a third registration indication to the UDM entity, where the third registration indication is used to indicate that the UDM entity deregisters a target AMF entity, the target AMF entity is responsible for mobility management when the terminal device 600 accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN which is accessed by the terminal device 600 by using an access technology belonging to the target access type.

The embodiment of the application provides a terminal device, when the terminal device has accessed to a first P L MN and is to be accessed to a second P L MN, the terminal device may determine that the UDM entity still retains the registration information of a first AMF entity responsible for mobility management when the terminal device accesses to the first P L MN when the access types to which the access technologies adopted when the terminal device accesses to the two P L MNs are different, so that the UDM entity may not only register a second AMF entity responsible for mobility management when the terminal device accesses to the second P L MN, but also may not register the first AMF entity, thereby implementing dual registration of the first AMF entity and the second AMF entity.

Based on the above embodiments, the present application further provides a UDM entity, where the UDM entity is configured to implement the network communication method shown in fig. 4, and may perform method steps performed by the UDM entity in the method. Referring to fig. 7, the UDM entity 700 includes: a receiving unit 701 and a processing unit 702, wherein,

a receiving unit 701, configured to receive a first registration indication from a terminal device, where the first registration indication is used to indicate that the UDM entity 700 reserves registration information of a first access and mobility management function, AMF, entity, and the first AMF entity is responsible for mobility management when the terminal device accesses a first P L MN, where the first P L MN is a P L MN to which the terminal device has accessed;

a processing unit 702, configured to reserve registration information of the first AMF entity according to the first registration indication.

Optionally, the processing unit 702 is further configured to:

before the registration information of the second AMF entity is reserved according to the first registration indication, determining that the terminal equipment has dual-connection capability, wherein the dual-connection capability is used for indicating that the terminal equipment supports accessing to a P L MN by adopting two access types of access technologies at the same time.

Optionally, the receiving unit 701 is further configured to receive a second registration instruction sent by the terminal device, where the second registration instruction is used to instruct the UDM entity 700 to perform de-registration on the first AMF entity;

the processing unit 702 is further configured to perform de-registration on the first AMF entity according to the second registration indication.

Optionally, the receiving unit 701 is further configured to receive a third registration instruction sent by the terminal device;

the third registration instruction is used to instruct the UDM entity 700 to perform de-registration on a target AMF entity, where the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, the target P L MN is a P L MN that the terminal device accesses by using an access technology belonging to the target access type, the target access type is an access type that is the same as a second access type in a first access type, the first access type is an access type to which an access technology adopted when the terminal device accesses the first P L MN belongs, the second access type is an access type to which an access technology adopted when the terminal device accesses the second P L MN, the second P L is a P L MN to be accessed by the terminal device, the first access type is a 3GPP access type or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

the processing unit 702 is further configured to perform de-registration on the target AMF entity according to the third registration instruction.

The embodiment of the application provides a UDM entity, under the condition that a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device can decide that the UDM entity still retains the registration information of a first AMF entity in charge of mobility management when the terminal device accesses the first P L MN when the terminal device has accessed the two P L MNs, and after receiving the first registration instruction, the UDM entity retains the registration information of the first AMF entity, so that the UDM entity can not only register a second AMF entity in charge of mobility management when the terminal device accesses the second P L MN, but also can not deregister the first AMF entity, thereby realizing the dual registration of the first AMF entity and the second AMF entity.

Based on the above embodiments, the present application further provides a UDM entity, where the UDM entity is configured to implement the network communication method shown in fig. 5, and may perform method steps performed by the UDM entity in the method. Referring to fig. 8, the UDM entity 800 includes: an acquisition unit 801 and a processing unit 802, wherein,

an obtaining unit 801, configured to obtain a first access type to which a first access technology adopted when a terminal device accesses a first public continental mobile network P L MN belongs and a second access type to which a second access technology adopted when the terminal device accesses a second P L MN belongs, where the first P L MN is a P L MN to which the terminal device has accessed, the second P L MN is a P L MN to which the terminal device is to be accessed, the first access type is a third generation partnership project 3GPP access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

a processing unit 802, configured to, when it is determined that the terminal device has a dual connectivity capability and the second access type is different from the first access type, retain registration information of a first access and mobility management function, AMF, entity, where the first AMF entity is responsible for mobility management when the terminal device accesses the first P L MN, and the dual connectivity capability is used to indicate that the terminal device supports access to a P L MN by using an access technology of two access types at the same time.

Optionally, the processing unit 802 is further configured to:

determining that the identity of the second P L MN is different from the identity of the first P L MN before retaining registration information of the first AMF entity.

Optionally, the processing unit 802 is further configured to:

deregistering the first AMF entity when at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type.

Optionally, the processing unit 802 is further configured to:

deregistering the first AMF entity when at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

Optionally, the processing unit 802 is further configured to:

and informing a first Session Management Function (SMF) entity to release the session of the terminal equipment, wherein the first SMF is responsible for session management when the terminal equipment accesses the first P L MN.

Optionally, the processing unit 802 is further configured to:

when determining that the target access type which is the same as the second access type exists in the first access type, performing de-registration on the target AMF entity;

The embodiment of the application provides a UDM entity, under the condition that a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the UDM entity can determine that the terminal device has double connection capability, and when the terminal device accesses the two P L MNs, the access type of the access technology adopted is different, the UDM entity still keeps the registration information of a first AMF entity responsible for mobility management when the terminal device accesses the first P L MN, so that the UDM entity can not only register a second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also can not register the first AMF entity, thereby realizing double registration of the first AMF entity and the second AMF entity.

It should be noted that, the division of the modules in the embodiments of the present application is schematic, and is only a logical function division, and in actual implementation, there may be another division manner, and in addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or may exist alone physically, or two or more units are integrated in one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Based on the above embodiments, the present application further provides a terminal device, which is applied in the mobile communication system shown in fig. 1, is used for implementing the network communication method shown in fig. 4, and has the function of the terminal device 600 shown in fig. 6. Referring to fig. 9, the terminal apparatus 900 includes: a transceiver 901, a processor 902, and a memory 903. Wherein, the transceiver 901, the processor 902 and the memory 903 are connected to each other.

Optionally, the transceiver 901, the processor 902 and the memory 903 are connected to each other through a bus 904. The bus 904 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 9, but this does not indicate only one bus or one type of bus.

The transceiver 901 is configured to receive and transmit data, so as to implement communication with other devices in the mobile communication system.

The processor 902 is configured to implement the network communication method provided in the embodiment shown in fig. 4, which may specifically refer to the description in the foregoing embodiment, and details are not described here again.

The memory 903 is used for storing program instructions and the like. In particular, the program instructions may include program code comprising computer operational instructions. The memory 903 may include Random Access Memory (RAM) and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 902 executes the program instructions stored in the memory 903 to implement the above functions, thereby implementing the network communication method provided by the above embodiments.

Based on the above embodiments, the present application further provides a UDM entity, which is applied in the mobile communication system shown in fig. 1, is used for implementing the network communication method shown in fig. 4 or fig. 5, and has the functions of the UDM entity 600 shown in fig. 6 or the UDM entity 700 shown in fig. 7. Referring to fig. 10, the UDM entity 1000 includes: a transceiver 1001, a processor 1002, and a memory 1003. The communication interface 1001, the processor 1002, and the memory 1003 are connected to each other.

Optionally, the communication interface 1001, the processor 1002, and the memory 1003 are connected to each other through a bus 1004. The bus 1004 may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus.

The communication interface 1001 is used for receiving and transmitting data, and implementing communication with other devices in the mobile communication system.

The processor 1002 is configured to implement the network communication method provided in the embodiment shown in fig. 4 or fig. 5, which may specifically refer to the description in the foregoing embodiment, and details are not described here again.

The memory 1003 is used for storing program instructions and the like. In particular, the program instructions may include program code comprising computer operational instructions. The memory 1003 may comprise RAM and may also include non-volatile memory, such as at least one disk memory. The processor 1002 executes the program instructions stored in the memory 1003 to implement the above functions, thereby implementing the network communication method provided by the above embodiments.

To sum up, the embodiment of the present application provides a network communication method and device, in the method, when a terminal device has accessed a first P L MN and is to be accessed to a second P L MN, the terminal device or the UDM entity may determine that, when the access types of the access technologies adopted when the terminal device accesses the two P L MNs are different, the UDM entity still retains the registration information of the first AMF entity responsible for mobility management when the terminal device accesses the first P L MN, so that the UDM entity may not only register the second AMF entity responsible for mobility management when the terminal device accesses the second P L MN, but also may not deregister the first AMF entity, thereby implementing the dual registration of the first AMF entity and the second AMF entity.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A network communication method, comprising:

the method comprises the steps that a terminal device obtains a first access type of a first access technology adopted when accessing a first public continental mobile network P L MN and a second access type of a second access technology adopted when accessing a second P L MN, wherein the first P L MN is a P L MN which is accessed by the terminal device, the second P L MN is a P L MN which is to be accessed by the terminal device, the first access type is a third generation partnership project (3 GPP) access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

when the terminal equipment determines that the second access type is different from the first access type, sending a first registration indication to a Unified Data Management (UDM) entity, wherein the first registration indication is used for indicating the UDM entity to reserve registration information of a first access and mobility management function (AMF) entity, and the first AMF entity is responsible for mobility management when the terminal equipment accesses the first P L MN.

2. The method of claim 1, wherein prior to the terminal device sending the first registration indication to the UDM entity, further comprising:

3. The method of claim 1, wherein prior to the terminal device sending the first registration indication to the UDM entity, further comprising:

4. The method of claim 1, wherein the method further comprises:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

the second registration indication is used for indicating the UDM entity to deregister the first AMF entity, and the dual connectivity capability is used for indicating that the terminal device supports access to a P L MN by using two access technologies simultaneously.

5. The method of claim 2, wherein the method further comprises:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

6. The method of claim 4, wherein the second registration indication is further used to trigger the UDM entity to notify a first Session management function, SMF, entity to release the session for the terminal device, wherein the first SMF entity is responsible for session management when the terminal device accesses the first P L MN.

7. The method of any one of claims 1-6, further comprising:

when the terminal device determines that a target access type which is the same as the second access type exists in the first access type, sending a third registration indication to the UDM entity, where the third registration indication is used to indicate the UDM entity to de-register a target AMF entity, where the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN which is accessed by the terminal device by using an access technology belonging to the target access type.

8. A network communication method, comprising:

a Unified Data Management (UDM) entity receives a first registration instruction from a terminal device, wherein the first registration instruction is used for instructing the UDM entity to reserve registration information of a first access and mobility management function (AMF) entity, the first AMF entity is responsible for mobility management when the terminal device accesses a first public land mobile network (P L MN), and the first P L MN is a P L MN which the terminal device has accessed;

and the UDM entity reserves the registration information of the first AMF entity according to the first registration instruction.

9. The method of claim 8, wherein before the UDM entity retains the registration information of the first AMF entity according to the first registration indication, the method further comprises:

and the UDM entity determines that the terminal equipment has dual-connection capability, wherein the dual-connection capability is used for indicating that the terminal equipment supports accessing to a P L MN by adopting two access technologies of two access types simultaneously.

10. A network communication method, comprising:

a Unified Data Management (UDM) entity acquires a first access type of a first access technology adopted when a terminal device is accessed to a first public continental mobile network (P L MN) and a second access type of a second access technology adopted when the terminal device is accessed to a second P L MN, wherein the first P L MN is a P L MN which is accessed by the terminal device, the second P L MN is a P L MN to be accessed by the terminal device, the first access type is a third generation partnership project (3 GPP) access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

when the UDM entity determines that the terminal equipment has dual-connection capability and the second access type is different from the first access type, the registration information of an AMF (mobility management function) entity with a first access and a mobility management function is reserved, wherein the AMF entity is in charge of mobility management when the terminal equipment accesses the first P L MN, and the dual-connection capability is used for indicating that the terminal equipment supports access technology adopting two access types simultaneously to access the P L MN.

11. The method of claim 10, wherein before the UDM entity retains the registration information of the first AMF entity, the method further comprises:

12. The method of claim 10, wherein the method further comprises:

deregistering the first AMF entity when the UDM entity determines at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type.

13. The method of claim 11, wherein the method further comprises:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

14. The method of claim 12, wherein the method further comprises:

and the UDM entity informs a first Session Management Function (SMF) entity to release the session of the terminal equipment, wherein the first SMF entity is responsible for session management when the terminal equipment accesses the first P L MN.

15. The method of any one of claims 10-14, further comprising:

when the UDM entity determines that a target access type which is the same as the second access type exists in the first access type, performing deregistration on a target AMF entity;

16. A terminal device, comprising:

an obtaining unit, configured to obtain a first access type to which a first access technology adopted when accessing a first public continental mobile network P L MN belongs and a second access type to which a second access technology adopted when accessing a second P L MN belongs, where the first P L MN is a P L MN to which the terminal device has accessed, the second P L MN is a P L MN to which the terminal device is to be accessed, the first access type is a third generation partnership project 3GPP access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

and the processing unit is configured to send a first registration indication to a Unified Data Management (UDM) entity when it is determined that the second access type is different from the first access type, where the first registration indication is used to indicate that the UDM entity reserves registration information of a first access and mobility management function (AMF) entity, and the first AMF entity is responsible for mobility management when the terminal device accesses the first P L MN.

17. The terminal device of claim 16, wherein the processing unit is further configured to:

18. The terminal device of claim 16, wherein the processing unit is further configured to:

before sending the first registration indication to the UDM entity, determining that the terminal device has dual connectivity capability, where the dual connectivity capability is used to indicate that the terminal device supports accessing a P L MN by using two access types of access technologies simultaneously.

19. The terminal device of claim 16, wherein the processing unit is further configured to:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

20. The terminal device of claim 17, wherein the processing unit is further configured to:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

21. The terminal device of claim 19, wherein the second registration indication is further used to trigger the UDM entity to notify a first session management function, SMF, entity to release the session for the terminal device, wherein the first SMF entity is responsible for session management when the terminal device accesses the first P L MN.

22. The terminal device of any of claims 16-21, wherein the processing unit is further configured to:

when it is determined that a target access type which is the same as the second access type exists in the first access type, sending a third registration indication to the UDM entity, where the third registration indication is used to indicate that the UDM entity deregisters a target AMF entity, the target AMF entity is responsible for mobility management when the terminal device accesses a target P L MN in the first P L MN, and the target P L MN is a P L MN which is accessed by the terminal device by using an access technology belonging to the target access type.

23. A unified data management, UDM, entity, comprising:

a receiving unit, configured to receive a first registration indication from a terminal device, where the first registration indication is used to indicate that a UDM entity retains registration information of an AMF (mobility management function) entity, the AMF entity is responsible for mobility management when the terminal device accesses a P L MN, and the P L MN is a P L MN to which the terminal device has accessed;

and the processing unit is used for reserving the registration information of the first AMF entity according to the first registration instruction.

24. The UDM entity according to claim 23, wherein the processing unit is further configured to:

before the registration information of the first AMF entity is reserved according to the first registration indication, determining that the terminal equipment has dual-connection capability, wherein the dual-connection capability is used for indicating that the terminal equipment supports accessing to a P L MN by adopting two access types of access technologies at the same time.

25. A unified data management, UDM, entity, comprising:

an obtaining unit, configured to obtain a first access type to which a first access technology adopted when a terminal device accesses a first public continental mobile network P L MN belongs and a second access type to which a second access technology adopted when the terminal device accesses a second P L MN belongs, where the first P L MN is a P L MN to which the terminal device has accessed, the second P L MN is a P L MN to which the terminal device is to be accessed, the first access type is a third generation partnership project 3GPP access type and/or a non-3GPP access type, and the second access type is a 3GPP access type or a non-3GPP access type;

and the processing unit is used for reserving registration information of a first access and mobility management function (AMF) entity when the terminal equipment is determined to have dual-connection capability and the second access type is different from the first access type, wherein the first AMF entity is responsible for mobility management when the terminal equipment accesses the first P L MN, and the dual-connection capability is used for indicating that the terminal equipment supports access technology adopting two access types simultaneously to access the P L MN.

26. The UDM entity according to claim 25, wherein the processing unit is further configured to:

27. The UDM entity according to claim 25, wherein the processing unit is further configured to:

deregistering the first AMF entity when at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type.

28. The UDM entity according to claim 26, wherein the processing unit is further configured to:

deregistering the first AMF entity when at least one of:

the terminal equipment does not have double connection capability;

the second access type is the same as the first access type;

29. The UDM entity of claim 27, wherein the processing unit is further configured to:

and informing a first Session Management Function (SMF) entity to release the session of the terminal equipment, wherein the first SMF entity is responsible for session management when the terminal equipment accesses the first P L MN.

30. The UDM entity according to any of claims 25-29, wherein the processing unit is further configured to: