Dual registration processing method, communication device, and storage medium

Abstract

The present application provides a dual registration processing method, a communication device, and a storage medium. The dual registration processing method applied to a first network element comprises: acquiring registration behavior information of a terminal; and determining, on the basis of the registration behavior information, whether a registration request message sent to a second network element carries a dual registration indication, wherein the first network element and the second network element are located in a same first mobile network.

Description

Dual registration processing method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a dual registration processing method, communication equipment, and storage medium. Background Art

[0002] After 5G network deployment, operators will still be unable to break away from 4G networks for a long time. Especially in the early stages of 5G network deployment, when full network coverage is not possible, 5G and 4G interoperability (Evolved Packet System Interworking, EPS Interworking) is essential. To ensure Internet Protocol (IP) continuity when user equipment (UE) moves between 4G and 5G networks, the UE's Public Data Network (PDN) connection in the 4G network and the Protocol Data Unit (PDU) session in the 5G network need to be anchored to the same IP session management entity (corresponding to the PGW-C in 4G and the SMF in 5G). This requires the Packet Data Network Gateway Control Plane (PGW-C) and Session Management Function (SMF) to be deployed in a unified manner (i.e., combined PGW-C + SMF). Similarly, there are requirements for unified deployment of the HSS of the 4G network and the Unified Data Management function (UDM) of the 5G network, or the implementation of an information exchange interface between the HSS and UDM. To ensure service continuity when the UE moves between 4G and 5G networks, the UE can use single registration mode or dual registration mode. In dual registration mode, when the UE moves from 4G to 5G, the network needs to avoid mistakenly detaching the UE from the 4G network.

[0003] Summary of the Invention

[0004] In view of this, embodiments of the present application provide a dual registration processing method, a communication device, and a storage medium, which effectively avoid erroneously triggering a deregistration process in a dual registration mode.

[0005] An embodiment of the present application provides a dual registration processing method, applied to a first network element, including:

[0006] Get the terminal's registration behavior information;

[0007] determining, according to the registration behavior information, whether the registration request message sent to the second network element carries a dual registration indication;

[0008] The first network element and the second network element are located in the same first mobile network.

[0009] An embodiment of the present application provides a dual registration processing method, which is applied to a second network element, including:

[0010] receiving a registration request message sent by the first network element;

[0011] determining whether to send a deregistration message to a third network element according to the terminal context information stored in the second network element and the registration request message;

[0012] The first network element and the second network element are located in the same first mobile network.

[0013] An embodiment of the present application provides a communication device, comprising: a memory, and one or more processors;

[0014] The memory is configured to store one or more programs;

[0015] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

[0016] An embodiment of the present application provides a storage medium storing a computer program. When the computer program is executed by a processor, the method described in any one of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a system architecture diagram of 5G and 4G network interoperability provided by related art;

[0018] FIG2 is a flowchart of a UE initiating initial registration when moving from a 4G network to a 5G network in a single registration mode provided by the related art;

[0019] FIG3 is a flowchart of a UE initiating initial registration from a 4G network to a 5G network in a dual registration mode provided by the related art;

[0020] FIG4 is a flowchart of a dual registration processing method provided in an embodiment of the present application;

[0021] FIG5 is a flowchart of another dual registration processing method provided in an embodiment of the present application;

[0022] FIG6 is a flowchart of a dual registration mode and a registration update under the same AMF provided in an embodiment of the present application;

[0023] FIG7 is a flowchart of another dual registration mode and registration update under the same AMF provided in an embodiment of the present application;

[0024] FIG8 is a flowchart of a registration update in a dual registration mode and when moving across AMFs in an idle state, provided by an embodiment of the present application;

[0025] FIG9 is a flowchart of a registration update in a dual registration mode and when moving across AMFs in a connected state, provided by an embodiment of the present application;

[0026] FIG10 is a structural block diagram of a dual registration processing device provided in an embodiment of the present application;

[0027] FIG11 is a structural block diagram of another dual registration processing device provided in an embodiment of the present application;

[0028] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The following describes the present application in conjunction with the accompanying drawings. The examples are only used to explain the present application and are not used to limit the scope of the present application.

[0030] To ensure service continuity when UE moves between 4G and 5G networks, and based on the capabilities of the operator's network, two EPS interoperability modes are proposed: EPS interoperability mode with N26 interface and EPS interoperability mode without N26 interface.

[0031] In the interoperability mode with the N26 interface, the Mobility Management Entity (MME) of the 4G network and the Access and Mobility Function (AMF) of the 5G network can implement the exchange of UE context through the N26 interface, so that the handover process can be used to achieve service continuity when the UE moves between the 4G and 5G networks.

[0032] In interoperability mode without the N26 interface, the N26 interface is not implemented between the MME of the 4G network and the AMF of the 5G network, making it impossible to use the handover process to achieve service continuity when the UE moves between the 4G and 5G networks. In this case, service continuity can only be guaranteed by re-registering the UE after moving from the 4G network to the 5G network, and vice versa.

[0033] In EPS interoperability mode without the N26 interface, the UE can register with the network in either single registration mode or dual registration mode, depending on the UE's capabilities. In single registration mode, the UE can only register with either the 4G or 5G network at the same time; in dual registration mode, the UE can register with both the 4G and 5G networks at the same time.

[0034] For dual registration mode, when the UE moves from 4G to 5G, the network needs to avoid mistakenly detaching (deregistering) the UE from the 4G network.

[0035] For example, a UE operates in dual registration mode. The UE first attaches (registers) to the 4G network. The MME initiates an MME registration (i.e., performs a Location Update) procedure with the HSS to register the UE's registration information with the 4G network. The HSS stores the UE's registration context information with the 4G network. Subsequently, the UE moves to the 5G network. The AMF performs an AMF registration procedure with the UDM to register the UE's registration information with the 5G network. The UDM stores the UE's registration context information with the 5G network. As a result, the UE is simultaneously registered with both the 4G and 5G networks. Specifically, after the UE moves to the 5G network, when initiating Initial Registration, it provides the AMF with its registration status on the 4G (i.e., EPS) network. The AMF then carries a Dual Registration Flag when performing AMF registration with the UDM. Upon receiving the Dual Registration Flag, the UDM avoids sending a Deregistration Notification to the MME (via the HSS), thereby preventing the MME from detaching (deregistering) the UE from the 4G (EPS) network.

[0036] However, if the UE subsequently initiates a Registration Update in the 5G network, the UE will not carry the registration status in the 4G (EPS) network again, and the AMF will not carry the dual registration indication when performing AMF registration with the UDM, which may trigger the UDM to trigger the MME deregistration process via the HSS, causing the UE to deregister from the 4G network. The same situation may also occur when the UE moves to a new AMF in the idle state and initiates a Registration Update, or when the UE moves to another AMF in the connected state and triggers a handover. In this case, the target AMF cannot obtain the UE's registration status in 4G (that is, the UE's registration status in the EPS network), and will not provide the dual registration indication to the UDM, which will also erroneously trigger the MME deregistration process, causing the UE to deregister from the 4G network.

[0037] Figure 1 is a system architecture diagram for 5G and 4G network interoperability, as provided by related technologies. As shown in Figure 1, in the above system architecture, the 4G network includes the following network functions: 4G Radio Access Network (RAN), MME, Serving Gateway (SGW), Packet Data Network Gateway (PGW), and Home Subscriber Server (HSS).

[0038] 4G RAN: In a 4G network, RAN can be an eNB.

[0039] The MME includes the following functions: registration management, PDN connection management, reachability management, and mobility management. This function also performs access authentication and access authorization.

[0040] The SGW provides the user plane access point closest to the wireless base station in mobility management and is located in the service network.

[0041] PGW includes PGW-C and Packet Data Network Gateway-User Plane (PGW-U), which serves as the user plane anchor point for mobility management. It includes the following functions: allocating IP addresses, packet routing and forwarding, traffic usage reporting, user plane QoS processing, downlink packet buffering, and downlink data notification triggering.

[0042] The HSS provides various subscription data of the UE, such as to the MME for access and mobility management. The HSS also processes location updates from the MME to record the UE's serving MME.

[0043] The 5G network part includes the following network functions: 5G RAN, AMF, Session Management Function (SMF), User Plane Function (UPF) and UDM.

[0044] 5G RAN: In 5G networks, RAN is gNB, which is the NR base station.

[0045] The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. This function also performs access authentication and access authorization. The AMF is a network access server (NAS) security terminal that relays the Session Management Non-Access Stratum (SM NAS) between the UE and the SMF.

[0046] The SMF includes the following functions: session establishment, modification and release, UE IP address allocation and management (including optional authorization function), UP function selection and control, downlink data notification, etc. The SMF controls the UPF through N4 association.

[0047] The UPF includes the following functions: allocation of IP addresses, packet routing and forwarding, traffic usage reporting, QoS processing for the user plane, downlink packet buffering, and anchor point for downlink data notification triggering.

[0048] UDM provides various subscription data of UE, such as provided to AMF for access and mobility management, or provided to SMF for PDU session management, etc. UDM also handles AMF registration from AMF to record the serving AMF of UE, or handles SMF registration from SMF to record PDU session information, etc.

[0049] Figure 2 is a flowchart of a UE initiating initial registration when it moves from a 4G network to a 5G network in single registration mode, as provided by related art. In this process, since the UE is in single registration mode, after the UE moves to the 5G network, no UE registration status in the EPS is provided when initiating initial registration, thereby triggering the UDM (via the HSS) to send a deregistration notification to the MME, causing the UE to detach from the 4G network. As shown in Figure 2, the process includes the following steps:

[0050] S210: Initiate an attachment request.

[0051] The UE is located under 4G network coverage and initiates an Attach Request to the AMF.

[0052] S220. The MME sends a location update request to the HSS.

[0053] The MME sends a Location Update Request to the HSS. Typically, the request message carries key information such as UE ID and MME ID.

[0054] S230. The HSS returns a location update response to the MME.

[0055] The HSS returns a Location Update Response to the MME. If the HSS accepts the Location Update Request sent by the MME, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the request message sent by the MME and carries a failed processing indication in the response message.

[0056] S240. The MME returns an attach response to the UE.

[0057] The MME returns an Attach Response to the UE. If the MME receives a successful processing indication from the HSS, the MME returns an Attach Accepted response to the UE. Otherwise, the MME returns an Attach Reject response to the UE.

[0058] S250: Store the UE context.

[0059] After S230 , if the HSS successfully processes the location update request of the MME, the HSS locally stores the UE context, which includes key information such as the UE ID and the MME ID.

[0060] S260, move to 5G network.

[0061] After S210-S250, the UE successfully attaches (registers) to the 4G network. Thereafter, the UE moves to the 5G network coverage.

[0062] S270. The UE initiates a registration request to the AMF.

[0063] The UE initiates a Registration Request to the AMF and sets the Registration Type to Initial Registration. In this process, if the UE is in single registration mode, the Registration Request sent to the AMF does not include the UE's registration status in the EPS.

[0064] S280. AMF sends an AMF registration request to UDM.

[0065] AMF sends an AMF Registration Request to UDM, that is, AMF executes the Nudm_UECM_Registration service call request provided by UDM. Specifically, in this step, when AMF calls the UDM service, the request message carries key information such as UE identifier (UE ID), AMF instance identifier (AMF Instance ID), global AMF identifier (GUAMI), and radio access technology type (RAT Type). Since the UE did not indicate its 4G status information (i.e., registration status in 4G) to AMF in the aforementioned steps, the AMF will not carry a dual registration flag in the request message in this step.

[0066] S290. UDM returns an AMF registration response to AMF.

[0067] The UDM returns an AMF Registration Response to the AMF, i.e., the UDM returns a response to the Nudm_UECM_Registration service call. If the UDM accepts the AMF Registration Request, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the AMF Registration Request and carries a failure processing indication in the response message.

[0068] S2100. The AMF returns a registration response to the UE.

[0069] The AMF returns a Registration Response to the UE. If the AMF receives a successful processing indication from the UDM, the AMF returns a Registration Accepted response to the UE. Otherwise, the AMF returns a Registration Reject response to the UE.

[0070] S2110. Store UE context.

[0071] After S290, if the UDM successfully processes the AMF registration request, the UDM locally stores the UE context, including key information such as the UE ID, AMF Instance ID, GUAMI, and RAT Type. If the UDM and HSS are deployed together, the UDM and HSS share the UE context. If the UDM and HSS are deployed separately, the UDM may push relevant information to the HSS.

[0072] S2120. UDM sends a deregistration notification to MME via HSS.

[0073] After S270-S2110, the UE successfully registers with the 5G network. Because the UDM does not receive the dual registration indication (drFlag), the UDM sends a deregistration notification to the MME via the HSS. If the UDM and HSS are deployed together, the UDM directly triggers the HSS to send a deregistration notification to the MME. If the UDM and HSS are deployed separately, the UDM triggers the HSS to send a deregistration notification to the MME via the service-based interface between the HSS and UDM.

[0074] S2130: Detach the UE.

[0075] After receiving the deregistration notification, the MME starts a detach process, i.e., a deregistration process, to detach (deregister) the UE from the 4G network.

[0076] In one embodiment, FIG3 is a flowchart of a UE initiating initial registration when it moves from a 4G network to a 5G network in a dual registration mode provided by the relevant technology. Different from the process of initiating initial registration in the single registration mode shown in FIG2 , in the dual registration mode, after the UE moves to the 5G network, when sending an initial registration (Initial Registration) request to the AMF, it carries UE status information, and indicates the UE's registration status in the EPS in the UE status information (i.e., it carries the UE State information element and is set to EMM-REGISTERED), so that when the AMF sends the AMF registration request to the UDM, it further carries a dual registration indication (dual registration flag, i.e., drFlag). When the UDM receives the dual registration indication, it will avoid sending a deregistration notification to the MME (via the HSS), thereby avoiding erroneously detaching (deregistering) the UE from the 4G (EPS), and ultimately achieving the purpose of dual registration of the UE in the 4G and 5G networks. As shown in FIG3 , the following steps are included:

[0077] S310: Initiate an attachment request.

[0078] The UE is located under 4G network coverage and initiates an Attach Request to the AMF.

[0079] S320. The MME sends a location update request to the HSS.

[0080] The MME sends a Location Update Request to the HSS. Typically, the request message carries key information such as UE ID and MME ID.

[0081] S330. The HSS returns a location update response to the MME.

[0082] The HSS returns a Location Update Response to the MME. If the HSS accepts the Location Update Request sent by the MME, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the request message sent by the MME and carries a failed processing indication in the response message.

[0083] S340: The MME returns an attach response to the UE.

[0084] The MME returns an Attach Response to the UE. If the MME receives a successful processing indication from the HSS, the MME returns an Attach Accepted response to the UE. Otherwise, the MME returns an Attach Reject response to the UE.

[0085] S350: Store the UE context.

[0086] After S230 , if the HSS successfully processes the location update request of the MME, the HSS locally stores the UE context, which includes key information such as the UE ID and the MME ID.

[0087] S360, move to 5G network.

[0088] After S210-S250, the UE successfully attaches (registers) to the 4G network. Thereafter, the UE moves to the 5G network coverage.

[0089] S370. The UE initiates a registration request to the AMF (carrying UE status information and registration type is initial registration).

[0090] The UE initiates a Registration Request to the AMF and sets the registration type to Initial Registration. In this process, since the UE operates in dual registration mode, the Registration Request sent to the AMF includes UE status information and indicates the UE's registration status in the EPS (i.e., it carries UE State information and sets its value to EMM-REGISTERED), indicating that the UE has registered in the 4G network.

[0091] S380. AMF sends an AMF registration request (carrying a dual registration flag, i.e., drFlag) to UDM.

[0092] AMF sends an AMF Registration Request to UDM, that is, AMF executes the Nudm_UECM_Registration service call request provided by UDM. Specifically, in this step, when AMF calls the UDM service, the request message carries key information such as UE identity (UE ID), AMF instance identity (AMF Instance ID), global AMF identity (GUAMI), and radio access technology type (RAT Type). In this process, when AMF calls the UDM service, the request message also carries additional dual registration indication (drFlag), whose value is set to True, to indicate that the UE is in dual registration mode and the UE is attached (registered) in the 4G network.

[0093] S390. UDM returns an AMF registration response to AMF.

[0094] The UDM returns an AMF Registration Response to the AMF, i.e., the UDM returns a response to the Nudm_UECM_Registration service call. If the UDM accepts the AMF Registration Request, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the AMF Registration Request and carries a failure processing indication in the response message.

[0095] S3100. AMF returns a registration response to the UE.

[0096] The AMF returns a Registration Response to the UE. If the AMF receives a successful processing indication from the UDM, the AMF returns a Registration Accepted response to the UE. Otherwise, the AMF returns a Registration Reject response to the UE.

[0097] S3110. Store UE context.

[0098] After S390, if the UDM successfully processes the AMF registration request from the AMF, the UDM locally stores the UE context, including key information such as UE ID, AMF Instance ID, GUAMI, and RAT Type. If the UDM and HSS are deployed together, the UDM and HSS share the UE context. If the UDM and HSS are not deployed together, the UDM may push relevant information to the HSS. In this process, the UDM locally stores the UE context and also obtains the dual registration indication (drFlag).

[0099] Different from the process in Figure 2, in the process shown in Figure 3, steps 12 to 13 in Figure 2 are not triggered. When the UDM receives the dual registration indication from the AMF, the UDM does not send a deregistration notification to the MME via the HSS. Consequently, the MME does not initiate the deregistration process, and the UE does not detach (deregister) from the 4G network.

[0100] The processes shown in Figures 2 and 3 above consider the case where the UE moves to the 5G network and performs initial registration, but do not consider the case where the UE subsequently performs a registration update. Similarly, if the UE initiates a registration update after moving to a new AMF in the idle state, or triggers a handover after moving to a new AMF in the connected state, the new AMF cannot obtain the UE's registration status in the EPS and thus cannot provide the dual registration indication (drFlag) to the UDM. As a result, the UDM will erroneously send a deregistration notification to the MME (via the HSS), causing the UE to be detached (deregistered) in the 4G network, resulting in an error.

[0101] In order to avoid erroneously triggering MME deregistration in dual registration mode, the present application discloses a dual registration processing method, which enables the UDM to correctly handle the dual registration mode and avoid triggering the MME deregistration process.

[0102] In one embodiment, Figure 4 is a flowchart of a dual registration processing method provided in an embodiment of the present application. This embodiment is used to prevent the MME from erroneously triggering deregistration in dual registration mode. This embodiment can be performed by a first network element. Exemplarily, the first network element can be an AMF. As shown in Figure 4, this embodiment includes steps S410-S420.

[0103] S410: Acquire registration behavior information of the terminal.

[0104] S420: Determine, based on the registration behavior information, whether the registration request message sent to the second network element carries a dual registration indication.

[0105] The first network element and the second network element are located in the same first mobile network. In an embodiment, after the terminal successfully performs initial registration in the first mobile network, the first network element can obtain the terminal's registration behavior information from the terminal context information stored in the first network element, or can obtain the terminal's registration behavior information from the terminal context information stored in other first network elements. Then, the first network element can determine whether the registration request message sent to the second network element carries a dual registration indication based on the registration behavior information. If the registration request message carries a dual registration indication, the second network element determines that the terminal is still in dual registration mode based on the dual registration indication, and avoids sending a deregistration notification to the third network element, thereby preventing the terminal from detaching from the second mobile network.

[0106] In one embodiment, the dual registration processing method applied to a first network element further includes: storing the registration behavior information in the terminal context information of the first network element. When the first network element obtains the registration behavior information from another first network element, the first network element needs to store the obtained registration behavior information in its own terminal context information.

[0107] In one embodiment, obtaining registration behavior information of a terminal includes: receiving terminal context information sent by another first network element; and obtaining the registration behavior information of the terminal from the terminal context information. In dual registration mode, after a terminal successfully completes initial registration in a first mobile network, if it moves across a first network element, the terminal needs to initiate a registration update process to the new first network element. In this case, the first network element acts as a target end, and the other first network element acts as a source end. Accordingly, the first network element acting as the target end receives the terminal context information sent by the other first network element acting as the source end, and obtains the registration behavior information of the terminal from the terminal context information.

[0108] In one embodiment, obtaining the registration behavior information of the terminal includes: receiving an initial registration request sent by the terminal carrying terminal status information; and generating the registration behavior information of the terminal according to the terminal status information.

[0109] In one embodiment, the registration behavior information of the terminal is generated based on the terminal status information, including: extracting the registration status of the terminal in the second mobile network from the terminal status information; generating the registration behavior information of the terminal based on the registration status of the terminal in the second mobile network and the support status of the first type of network interoperability mode.

[0110] In one embodiment, the first type of network interoperability mode is used to indicate an interoperability mode in which the terminal does not have an N26 interface between the second mobile network and the first mobile network, the second mobile network is a 4G network, and the first mobile network is a 5G network. In one example, the registration status of the terminal in the second mobile network includes: registered; unregistered. The support status of the first type of network interoperability mode is used to characterize whether the network capability of the first mobile network supports EPS interoperability without an N26 interface. In an embodiment, the first network element can determine whether the registration behavior information of the terminal includes a dual registration indication based on the registration status of the terminal in the second mobile network and the support status of the first type of network interoperability mode.

[0111] In one embodiment, generating registration behavior information of the terminal according to the registration status of the terminal in the second mobile network and the support status of the first type of network interoperability mode includes:

[0112] If the registration status of the terminal on the second mobile network is registered and the first network element supports the first type of network interoperability mode, a corresponding dual registration indication is generated. If the registration status of the terminal on the second mobile network is indicated as registered in the initial registration request of the terminal, the first network element determines that the network capability of the first mobile network supports EPS interoperability without an N26 interface, and the first mobile network initiates EPS interoperability without an N26 interface, the first network element generates a corresponding dual registration indication, i.e., sets the dual registration indication to True.

[0113] In one embodiment, the registration behavior information includes at least one of the following: a registration status of the terminal in the second mobile network; and a dual registration indication.

[0114] In one embodiment, determining, based on the registration behavior information, whether the registration request message sent to the second network element carries a dual registration indication includes:

[0115] When the registration behavior information includes the registration status of the terminal in the second mobile network, the registration status of the terminal in the second mobile network is registered, and the first network element supports the first type of network interoperability mode, sending a registration request message carrying a dual registration indication to the second network element; or

[0116] If the registration behavior information includes a dual registration indication, a registration request message carrying the dual registration indication is sent to the second network element. In one example, if the registration behavior information includes a dual registration indication, the first network element may directly send a registration request message carrying the dual registration indication to the second network element. In one example, if the registration behavior information includes the registration status of the terminal in the second mobile network, the registration status of the terminal in the second mobile network is registered, and the first mobile network where the first network element is located supports and enables EPS interoperability without an N26 interface, the first network element generates a corresponding dual registration indication and carries the dual registration indication in a registration request message and sends it to the second network element.

[0117] In one embodiment, Figure 5 is a flowchart of another dual registration processing method provided by an embodiment of the present application. This embodiment is used to prevent the MME from erroneously triggering deregistration in dual registration mode. This embodiment can be performed by a second network element. Exemplarily, the second network element can be a UDM. As shown in Figure 5, this embodiment includes S510-S520.

[0118] S510: Receive a registration request message sent by a first network element.

[0119] S520: Determine whether to send a deregistration message to a third network element according to the terminal context information and the registration request message stored in the second network element.

[0120] In one embodiment, determining whether to send a deregistration message to a third network element based on the terminal context information and the registration request stored by the second network element includes:

[0121] If the registration request message sent by the first network element does not include a dual registration indication, and the terminal context information stored by the second network element includes a dual registration indication, not sending a deregistration message to the third network element;

[0122] Alternatively, when the registration request message sent by the first network element includes a dual registration indication, no deregistration message is sent to the third network element.

[0123] It should be noted that for the explanation of parameters such as terminal context information and registration request message involved in the dual registration processing method applied to the second network element, please refer to the description of the corresponding parameters in the dual registration processing method applied to the first network element above, and will not be repeated here.

[0124] In the embodiments shown in Figures 6-9 below, the dual registration process is described by taking the first network element as an AMF, the second network element as a UDM, the third network element as an MME, the second mobile network as a 4G network, and the first mobile network as a 5G network as examples. It should be noted that in the registration update process when moving between AMFs in the idle state, or the handover process when moving between AMFs in the connected state, AMF2 serves as the target end, which can also be called the new AMF; AMF1 serves as the source end.

[0125] In one embodiment, Figure 6 is a flowchart of a dual registration mode and a registration update under the same AMF provided in an embodiment of the present application. As shown in Figure 6, the process of initiating a registration update under the same AMF after the UE successfully initially registers with 5G in dual registration mode is described.

[0126] In this process, after the UE successfully performs the initial registration to 5G, the UE initiates the registration update process under the same AMF. The UDM determines and avoids sending the deregistration notification to the MME (via the HSS) based on the dual registration indication (drFlag) saved in the UE context.

[0127] This embodiment includes the following steps:

[0128] S610: Initiate an attachment request.

[0129] The UE is located under 4G network coverage and initiates an Attach Request to the AMF.

[0130] S620. The MME sends a location update request to the HSS.

[0131] The MME sends a Location Update Request to the HSS. Typically, the request message carries key information such as UE ID and MME ID.

[0132] S630: The HSS returns a location update response to the MME.

[0133] The HSS returns a Location Update Response to the MME. If the HSS accepts the Location Update Request sent by the MME, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the request message sent by the MME and carries a failed processing indication in the response message.

[0134] S640: The MME returns an attach response to the UE.

[0135] The MME returns an Attach Response to the UE. If the MME receives a successful processing indication from the HSS, the MME returns an Attach Accepted response to the UE. Otherwise, the MME returns an Attach Reject response to the UE.

[0136] S650: Store the UE context.

[0137] After S630, if the HSS successfully processes the location update request of the MME, the HSS locally stores the UE context, including key information such as the UE ID and the MME ID.

[0138] S660, move to 5G network.

[0139] After S610-S650, the UE successfully attaches (registers) to the 4G network. Thereafter, the UE moves to the 5G network coverage.

[0140] S670. The UE initiates a registration request to the AMF (carrying UE status information and registration type as initial registration).

[0141] The UE initiates a Registration Request to the AMF and sets the registration type to Initial Registration. In this process, since the UE operates in dual registration mode, the Registration Request sent to the AMF includes UE status information and indicates the UE's registration status in the EPS (i.e., it carries UE State information and sets its value to EMM-REGISTERED), indicating that the UE has registered in the 4G network.

[0142] S680. AMF sends an AMF registration request (carrying drFlag) to UDM.

[0143] AMF sends an AMF Registration Request to UDM, that is, AMF executes the Nudm_UECM_Registration service call request provided by UDM. Specifically, in this step, when AMF calls the UDM service, the request message carries key information such as UE identity (UE ID), AMF instance identity (AMF Instance ID), global AMF identity (GUAMI), and radio access technology type (RAT Type). In this process, when AMF calls the UDM service, the request message also carries additional dual registration indication (drFlag), whose value is set to True to indicate that the UE is in dual registration mode and the UE is attached (registered) in the 4G network.

[0144] S690. UDM returns an AMF registration response to AMF.

[0145] The UDM returns an AMF Registration Response to the AMF, i.e., the UDM returns a response to the Nudm_UECM_Registration service call. If the UDM accepts the AMF Registration Request, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the AMF Registration Request and carries a failure processing indication in the response message.

[0146] S6100. AMF returns a registration response to the UE.

[0147] The AMF returns a Registration Response to the UE. If the AMF receives a successful processing indication from the UDM, the AMF returns a Registration Accepted response to the UE. Otherwise, the AMF returns a Registration Reject response to the UE.

[0148] S6110. Store UE context.

[0149] After S690, if the UDM successfully processes the AMF registration request from the AMF, the UDM locally stores the UE context, including key information such as UE ID, AMF Instance ID, GUAMI, and RAT Type. If the UDM and HSS are deployed together, the UDM and HSS share the UE context. If the UDM and HSS are not deployed together, the UDM may push relevant information to the HSS. In this process, the UDM locally stores the UE context and also obtains the dual registration indication (drFlag).

[0150] S6120. The UE periodically initiates registration update.

[0151] The UE enters the idle state and periodically initiates a registration update.

[0152] S6130. The UE sends a registration request to the AMF (registration type is periodic registration update).

[0153] The UE sends a Registration Request to the AMF, setting the registration type to Periodic Registration Updating. In this step, the UE does not carry the UE's registration status in the EPS as in the initial Registration Request.

[0154] S6140. AMF sends an AMF registration request to UDM.

[0155] Different from the above S680, the AMF sends an AMF Registration Request to the UDM. Since the AMF does not obtain the UE's registration status in the EPS from the UE, the AMF does not carry the dual registration indication (drFlag) in this message.

[0156] S6150. UDM returns an AMF registration response to AMF.

[0157] Similar to S690 above, UDM returns an AMF Registration Response to AMF.

[0158] S6160. AMF returns a registration response to the UE.

[0159] The AMF returns a registration response (Registration Response) to the UE.

[0160] S6170: Determine whether to send a deregistration notification.

[0161] The UDM determines that the UE is still in dual registration mode based on the dual registration indication (drFlag) stored in the UE registration context, and needs to avoid sending a deregistration notification to the MME (via the HSS).

[0162] S6180: Do not send a deregistration notification to the MME.

[0163] Similar to the process in FIG3 , the UDM does not send a deregistration notification to the MME (via the HSS), so that the UE does not detach (deregister) from 4G.

[0164] In one embodiment, Figure 7 is a flowchart of another dual registration mode and registration update under the same AMF provided in an embodiment of the present application. As shown in Figure 7, the process of initiating a registration update under the same AMF after the dual registration mode UE successfully initially registers with 5G is described.

[0165] In this process, after the UE successfully performs the initial registration to 5G, the AMF saves the UE registration behavior information (including at least one of the following: UE registration status in EPS, dual registration indication (drFlag)) in the UE context. Subsequently, when the UE initiates the registration update process under the same AMF, the AMF uses the saved UE registration behavior information to decide whether to carry the dual registration indication (drFlag) when initiating the AMF registration request to the UDM.

[0166] This embodiment includes the following steps:

[0167] S710: Initiate an attachment request.

[0168] S720. The MME sends a location update request to the HSS.

[0169] S730. The HSS returns a location update response to the MME.

[0170] S740: The MME returns an attach response to the UE.

[0171] S750: Store the UE context.

[0172] S760, move to 5G network.

[0173] S770. The UE initiates a registration request to the AMF (carrying UE status information and registration type is initial registration).

[0174] S780. AMF sends an AMF registration request (carrying drFlag) to UDM.

[0175] S790. UDM returns an AMF registration response to AMF.

[0176] It should be noted that the implementation steps of S710-S790 are the same as those of S610-S690 in the above embodiment, and will not be repeated here.

[0177] S7100. Store UE registration behavior information.

[0178] The AMF stores the UE registration behavior information in the UE context. The UE Registration Behavior Info includes at least one of the following information: the UE's registration status in the EPS (EMM Registration Status) and the dual registration indication (drFlag). The UE's registration status in the EPS is obtained by the AMF from the UE's initial registration request. The dual registration indication (drFlag) is generated by the AMF using the following information: the UE's status in the EPS, the network's interoperability capabilities for EPS without the N26 interface, and the operator's policy. Specifically, the judgment of the AMF may be that if the UE indicates in the initial registration request that the UE's registration status in the EPS is registered (that is, it carries the UE Status IE and is set to EMM-REGISTERED), and the AMF determines that the network supports EPS interoperation without the N26 interface (that is, the network has the capability of EPS interoperation without the N26 interface, and the network currently enables EPS interoperation without the N26 interface), then the AMF can generate a dual registration indication (drFlag) based on the above information, specifically setting the dual registration indication (drFlag) to True.

[0179] S7110. AMF returns a registration response to the UE.

[0180] S7120. Store UE context.

[0181] S7130. The UE periodically initiates registration updates.

[0182] S7140. The UE sends a registration request to the AMF (registration type is periodic registration update).

[0183] It should be noted that the implementation steps of S7110-S7140 are the same as those of S6100-S6130 in the above embodiment, and will not be repeated here.

[0184] S7150. Generate a dual registration indication.

[0185] After receiving the registration update request from the UE, the AMF determines, based on the UE registration behavior information stored in the UE context, that a dual registration indication (drFlag) must be carried in the AMF registration request sent to the UDM. Specifically, the AMF may make the determination based on one of the following information in the stored UE registration behavior information: the UE's registration status in the EPS; or the dual registration indication (drFlag). Specifically, if the UE registration behavior information only contains the UE's registration status in the EPS, the AMF may generate the dual registration indication (drFlag) as in S7100. If the UE registration behavior information contains the dual registration indication (drFlag), the AMF may directly use this dual registration indication.

[0186] S7160. AMF sends an AMF registration request (carrying drFlag) to UDM.

[0187] As in S780 above, AMF sends an AMF Registration Request to UDM, carrying a dual registration indication.

[0188] S7170. UDM returns an AMF registration response to AMF.

[0189] Similar to S790 above, UDM returns an AMF Registration Response to AMF.

[0190] S7180. AMF returns a registration update response to the UE.

[0191] The AMF returns a Registration Update Response to the UE.

[0192] S7190: Do not send a deregistration notification to the MME.

[0193] Similar to the process in FIG3 , the UDM does not send a deregistration notification to the MME (via the HSS), so that the UE does not detach (deregister) from 4G.

[0194] In one embodiment, Figure 8 is a flowchart of a registration update in a dual registration mode and when moving across AMFs in idle state provided by an embodiment of the present application. As shown in Figure 8, it describes the process of initiating a registration update from a UE in dual registration mode to a new AMF when moving across AMFs after the UE successfully initially registers with 5G.

[0195] In this process, when the target AMF (i.e., AMF2) receives the registration request, the target AMF obtains the UE context from the source AMF (i.e., AMF1), which contains the UE registration behavior information (at least one of the following: UE registration status in EPS, dual registration indication (drFlag)). The target AMF uses the stored UE registration behavior information to decide whether to carry the dual registration indication (drFlag) when initiating an AMF registration request to the UDM.

[0196] This embodiment includes the following steps:

[0197] S810: Initiate an attachment request.

[0198] S820. The MME sends a location update request to the HSS.

[0199] S830. The HSS returns a location update response to the MME.

[0200] S840: The MME returns an attach response to the UE.

[0201] S850: Store the UE context.

[0202] S860, move to 5G network.

[0203] S870. The UE initiates a registration request to AMF1 (carrying UE status information and registration type is initial registration).

[0204] S880. AMF1 sends an AMF registration request (carrying drFlag) to UDM.

[0205] S890. UDM returns an AMF registration response to AMF1.

[0206] S8100. Store UE registration behavior information.

[0207] The AMF saves the UE registration behavior information in the UE context. The UE registration behavior information (UE Registration Behavior Info) includes at least one of the following information: the UE's registration status in the EPS (EMM Registration Status) and the dual registration indication (drFlag). The UE's registration status in the EPS is obtained by the AMF from the UE's initial registration request. The dual registration indication (drFlag) is generated by the AMF based on the following information: the UE's status information in the EPS, the network's interoperability capability for EPS without the N26 interface, and the operator's policy. Specifically, the AMF's judgment may be that if the UE indicates in the initial registration request that the UE's registration status in the EPS is registered (i.e., it carries the UE Status IE and is set to EMM-REGISTERED), and the AMF determines that the network capability supports EPS interoperability without the N26 interface, and the network currently enables EPS interoperability without the N26 interface, then the AMF may generate the dual registration indication (drFlag) based on the information, specifically setting the dual registration indication (drFlag) to True.

[0208] S8110. AMF1 returns a registration response to the UE.

[0209] S8120. Store the UE context.

[0210] After S890, if the UDM successfully processes the AMF registration request from the AMF, the UDM locally stores the UE context, including key information such as the UE ID, AMF Instance ID, GUAMI, and RAT Type. If the UDM and HSS are deployed together, the UDM and HSS share the UE context. If the UDM and HSS are deployed separately, the UDM may push relevant information to the HSS. In this process, the UDM locally stores the UE context, including the dual registration indication (drFlag).

[0211] It should be noted that the implementation process of S810-S8120 in this embodiment is the same as that of S710-S7120 in Figure 7, and will not be repeated here. Compared with S310-S3110 in Figure 3, Figure 8 is the same as Figure 7, and the AMF needs to execute S8100 after S890.

[0212] S8130. The UE moves to a new AMF.

[0213] In the idle state, the UE moves to the service area of ​​the new AMF and initiates a registration update (Registration Update) to the new AMF (i.e. AMF2).

[0214] S8140. The UE sends a registration request to AMF2 (registration type is mobility registration update).

[0215] The UE sends a Registration Request to AMF2 with the Registration Type set to Mobility Registration Update. In this step, the UE does not carry the UE's registration status in the EPS as in the initial Registration Request.

[0216] S8150. AMF2 sends a UE context request to AMF1.

[0217] AMF2 sends a UE Context Request to AMF1.

[0218] S8160. AMF1 returns a UE context response (carrying registration behavior information) to AMF2.

[0219] AMF1 returns a UE Context Response to AMF2, where the UE context includes UE Registration Behavior Info, which carries at least one of the following information: UE registration status (EMM Registration Status) in EPS and dual registration indication (drFlag). AMF2 locally stores the UE context received from AMF1, including the UE registration behavior information.

[0220] S8170: Determine whether to carry a dual registration indication.

[0221] Based on the UE context information received from AMF1, AMF2 determines whether the dual registration indicator (drFlag) must be included in the AMF registration request sent to the UDM. Specifically, AMF2 can make this determination based on one of the following information in the received UE registration behavior information: the UE's registration status in the EPS (EMM Registration Status) and the dual registration indicator (drFlag). Specifically, the determination method of AMF2 is similar to S7150 in Figure 7.

[0222] S8180. AMF2 sends an AMF registration request (carrying drFlag) to UDM.

[0223] As in S880 above, AMF2 sends an AMF Registration Request to UDM, carrying a dual registration indication.

[0224] S8190. UDM returns an AMF registration response to AMF2.

[0225] Similar to S890 above, UDM returns an AMF Registration Response to AMF2.

[0226] S8200. AMF2 returns a registration response to the UE.

[0227] AMF2 returns a registration response (Registration Response) to the UE.

[0228] S8210: Do not send a deregistration notification to the MME.

[0229] Similar to the process in FIG3 , the UDM does not send a deregistration notification to the MME (via the HSS), so that the UE does not detach (deregister) from 4G.

[0230] In one embodiment, FIG9 is a flowchart of a registration update in a dual registration mode and when moving across AMFs in a connected state, provided by an embodiment of the present application. As shown in FIG9 , the process of triggering an inter-AMF handover when a dual registration mode UE moves across AMFs after successfully initially registering in 5G is described.

[0231] In this process, when the target AMF (i.e., AMF2) receives the registration request, the target AMF obtains the UE context from the source AMF (i.e., AMF1), which contains the UE registration behavior information (at least one of the following: UE registration status in EPS, dual registration indication (drFlag)). The target AMF uses the stored UE registration behavior information to decide whether to carry the dual registration indication (drFlag) when initiating an AMF registration request to the UDM.

[0232] This embodiment includes the following steps:

[0233] S910: Initiate an attachment request.

[0234] S920. The MME sends a location update request to the HSS.

[0235] S930. The HSS returns a location update response to the MME.

[0236] S940: The MME returns an attach response to the UE.

[0237] S950: Store the UE context.

[0238] S960, move to 5G network.

[0239] It should be noted that the implementation process of S910-S960 is the same as the implementation process of S610-S660 described above, and will not be repeated here.

[0240] S970. The UE initiates a registration request (carrying UE status information) to AMF1.

[0241] The UE initiates a Registration Request to the AMF and sets the registration type to Initial Registration. In this process, since the UE operates in dual registration mode, the Registration Request sent to the AMF includes UE status information and indicates the UE's registration status in the EPS (i.e., it carries UE State information and sets its value to EMM-REGISTERED), indicating that the UE has registered in the 4G network.

[0242] S980. AMF1 sends an AMF registration request (carrying drFlag) to UDM.

[0243] AMF1 sends an AMF Registration Request to UDM, that is, AMF executes the Nudm_UECM_Registration service call request provided by UDM. Specifically, in this step, when AMF calls the UDM service, the request message carries key information such as UE identity (UE ID), AMF instance identity (AMF Instance ID), global AMF identity (GUAMI), and radio access technology type (RAT Type). In this process, when AMF calls the UDM service, the request message also carries additional dual registration indication (drFlag), whose value is set to True to indicate that the UE is in dual registration mode and that the UE is attached (registered) in the 4G network.

[0244] S990. UDM returns an AMF registration response to AMF1.

[0245] The UDM returns an AMF Registration Response to the AMF, i.e., the UDM returns a response to the Nudm_UECM_Registration service call. If the UDM accepts the AMF Registration Request, the UDM carries a successful processing indication in the response message. Otherwise, the HSS rejects the AMF Registration Request and carries a failure processing indication in the response message.

[0246] S9100. Store UE registration behavior information.

[0247] The AMF saves the UE registration behavior information in the UE context. The UE registration behavior information (UE Registration Behavior Info) includes at least one of the following information: the UE's registration status in the EPS (EMM Registration Status) and the dual registration indication (drFlag). The UE's registration status in the EPS is obtained by the AMF from the UE's initial registration request. The dual registration indication (drFlag) is generated by the AMF based on the following information: the UE's status information in the EPS, the network's interoperability capability for EPS without the N26 interface, and the operator's policy. Specifically, the AMF's judgment may be that if the UE indicates in the initial registration request that the UE's registration status in the EPS is registered (i.e., it carries the UE Status IE and is set to EMM-REGISTERED), and the AMF determines that the network capability supports EPS interoperability without the N26 interface, and the network currently enables EPS interoperability without the N26 interface, then the AMF may generate the dual registration indication (drFlag) based on the information, specifically setting the dual registration indication (drFlag) to True.

[0248] S9110. AMF1 returns a registration response to the UE.

[0249] S9120. Store the UE context.

[0250] After S990, if the UDM successfully processes the AMF registration request from the AMF, the UDM locally stores the UE context, including key information such as the UE ID, AMF Instance ID, GUAMI, and RAT Type. If the UDM and HSS are deployed together, the UDM and HSS share the UE context. If the UDM and HSS are not deployed together, the UDM may push relevant information to the HSS. In this process, the UDM locally stores the UE context, including the dual registration indication (drFlag).

[0251] S910-S9120 in this embodiment are the same as S710-S7120 in Figure 7. Compared with steps S310-S3110 in Figure 3, Figure 9 is the same as Figure 7, and the AMF needs to execute S9100 after S990.

[0252] S9130. The UE moves to a new AMF.

[0253] In the connected state, when the UE moves to a new AMF service area, a handover process will be triggered.

[0254] S9140. RAN triggers a handover process to the new AMF (i.e., AMF2).

[0255] The RAN triggers a handover procedure (Handover) to the new AMF (i.e., AMF2).

[0256] S9150. AMF2 sends a UE context request to AMF1.

[0257] AMF2 sends a UE Context Request to AMF1.

[0258] S9160. AMF1 returns a UE context response (carrying registration behavior information) to AMF2.

[0259] AMF1 returns a UE Context Response to AMF2, where the UE context includes UE Registration Behavior Info, which carries at least one of the following information: UE registration status (EMM Registration Status) in EPS and dual registration indication (drFlag). AMF2 locally stores the UE context received from AMF1, including the UE registration behavior information.

[0260] S9170: Determine whether to carry a dual registration indication.

[0261] Based on the UE context information received from AMF1, AMF2 determines whether the AMF registration request sent to the UDM must carry a dual registration indicator (drFlag). Specifically, AMF2 can make this determination based on one of the following information in the received UE registration behavior information: the UE's registration status in the EPS (EMM Registration Status) and the dual registration indicator (drFlag). Specifically, the AMF2 determination method is similar to S7150 in Figure 7.

[0262] S9180. AMF2 sends an AMF registration request (carrying drFlag) to UDM.

[0263] As in S980 above, AMF2 sends an AMF Registration Request to UDM, carrying a dual registration indication.

[0264] S9190. UDM returns an AMF registration response to AMF2.

[0265] Similar to S990 above, UDM returns an AMF Registration Response to AMF2.

[0266] S9140-S9190 are the same as S8140-S8190 in Figure 8. AMF2 obtains the UE context from AMF1, which includes the UE registration behavior information (UE Registration Behavior Info). AMF2 uses this information to determine whether the dual registration indication (drFlag) must be carried in the AMF registration request sent to the UDM, and operates accordingly.

[0267] S9200 and AMF2 continue to execute the subsequent handover process (Handover).

[0268] S9210: Do not send a deregistration notification to the MME.

[0269] Similar to the process in FIG3 , the UDM does not send a deregistration notification to the MME (via the HSS), so that the UE does not detach (deregister) from 4G.

[0270] In one embodiment, FIG10 is a block diagram of a dual registration processing apparatus provided in an embodiment of the present application. This embodiment is applied to a first network element. As shown in FIG10 , the dual registration apparatus in this embodiment includes: an acquisition module 1010 and a determination module 1020.

[0271] The acquisition module 1010 is configured to acquire registration behavior information of the terminal.

[0272] The determining module 1020 is configured to determine whether the registration request message sent to the second network element carries a dual registration indication according to the registration behavior information;

[0273] The first network element and the second network element are located in the same first mobile network.

[0274] In one embodiment, the dual registration processing apparatus applied to the first network element further includes:

[0275] The storage module is configured to store the registration behavior information in the terminal context information of the first network element.

[0276] In one embodiment, the acquisition module 1010 includes:

[0277] a receiving unit configured to receive terminal context information sent by another first network element;

[0278] The acquiring unit is configured to acquire the registration behavior information of the terminal from the terminal context information.

[0279] In one embodiment, the acquisition module 1010 includes:

[0280] The receiving unit is further configured to receive an initial registration request carrying terminal status information sent by the terminal;

[0281] The generating unit is configured to generate registration behavior information of the terminal according to the terminal status information.

[0282] In one embodiment, the generating unit includes:

[0283] an extracting subunit, configured to extract a registration status of the terminal in the second mobile network from the terminal status information;

[0284] The generating subunit is configured to generate registration behavior information of the terminal according to a registration state of the terminal in the second mobile network and a support status of the first type of network interoperability mode.

[0285] In one embodiment, the first type of network interoperability mode is used to indicate an interoperability mode of the terminal without an N26 interface between the second mobile network and the first mobile network, the second mobile network is a 4G network, and the first mobile network is a 5G network.

[0286] In one embodiment, the generating subunit is further configured to: generate a corresponding dual registration indication when the registration status of the terminal in the second mobile network is registered and the first network element supports the first type of network interoperability mode.

[0287] In one embodiment, the registration behavior information includes at least one of the following: a registration status of the terminal in the second mobile network; and a dual registration indication.

[0288] In one embodiment, the determination module 1020 is further configured to:

[0289] When the registration behavior information includes the registration status of the terminal in the second mobile network, the registration status of the terminal in the second mobile network is registered, and the first network element supports the first type of network interoperability mode, sending a registration request message carrying a dual registration indication to the second network element; or

[0290] In a case where the registration behavior information includes a dual registration indication, a registration request message carrying the dual registration indication is sent to the second network element.

[0291] The dual registration processing apparatus provided in this embodiment is configured to implement the dual registration processing method applied to the first network element in the embodiment shown in FIG4 . The implementation principle and technical effects of the dual registration processing apparatus provided in this embodiment are similar and will not be described in detail here.

[0292] In one embodiment, FIG11 is a block diagram of another dual registration processing apparatus provided by an embodiment of the present application. This embodiment is applied to a second network element. As shown in FIG11 , the dual registration apparatus in this embodiment includes: a receiving module 1110 and a determining module 1120.

[0293] The receiving module 1110 is configured to receive a registration request message sent by the first network element;

[0294] The determining module 1120 is configured to determine whether to send a deregistration message to the third network element based on the terminal context information and the registration request stored in the second network element;

[0295] The first network element and the second network element are located in the same first mobile network.

[0296] In one embodiment, the determination module 1120 is further configured to:

[0297] If the registration request message sent by the first network element does not include a dual registration indication, and the terminal context information stored by the second network element includes a dual registration indication, not sending a deregistration message to the third network element;

[0298] Alternatively, when the registration request message sent by the first network element includes a dual registration indication, no deregistration message is sent to the third network element.

[0299] The dual registration processing apparatus provided in this embodiment is configured to implement the dual registration processing method applied to the second network element in the embodiment shown in FIG5 . The implementation principle and technical effects of the dual registration processing apparatus provided in this embodiment are similar and will not be described in detail here.

[0300] In one embodiment, Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 12, the device provided in the present application includes: a processor 1210, a memory 1220, and a communication module 1230. The number of processors 1210 in the device can be one or more, and Figure 12 uses one processor 1210 as an example. The number of memories 1220 in the device can be one or more, and Figure 12 uses one memory 1220 as an example. The processor 1210, memory 1220, and communication module 1230 of the device can be connected via a bus or other means, and Figure 12 uses connection via a bus as an example. In this embodiment, the device can be a first network element or a second network element.

[0301] Memory 1220, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device of any embodiment of the present application (for example, the acquisition module 1010 and determination module 1020 in the dual registration processing device applied to the first network element). Memory 1220 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data generated based on the use of the device. Furthermore, memory 1220 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some examples, memory 1220 may further include memory remotely located relative to processor 1210, and such remote memory may be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. Communication module 1230 is configured to implement communication interaction processes between multiple communication devices.

[0302] In the case where the communication device is a first network element, the device provided above can be configured to execute the dual registration processing method applied to the first network element provided in any of the above embodiments, and have corresponding functions and effects.

[0303] In the case where the communication device is a second network element, the above-provided device may be configured to execute the dual registration processing method applied to the second network element provided in any of the above-mentioned embodiments, and have corresponding functions and effects.

[0304] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to perform a dual registration processing method applied to a first network element. The method includes: obtaining registration behavior information of a terminal; determining whether a registration request message sent to a second network element carries a dual registration indication based on the registration behavior information; wherein the first network element and the second network element are located in the same first mobile network.

[0305] An embodiment of the present application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a dual registration processing method applied to a second network element, the method comprising: receiving a registration request message sent by a first network element; determining whether to send a deregistration message to a third network element based on terminal context information and the registration request message stored in the second network element; wherein the first network element and the second network element are located in the same first mobile network.

[0306] It will be appreciated by those skilled in the art that the term user equipment encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a car-mounted mobile station.

[0307] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0308] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0309] The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. A computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital versatile discs (DVD) or compact disks (CD)), etc. Computer-readable media may include non-transient storage media. A data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and a processor based on a multi-core processor architecture.

[0310] The above are merely optional embodiments of the present application and are not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A dual registration processing method, applied to a first network element, comprising: Get the terminal's registration behavior information; determining, according to the registration behavior information, whether the registration request message sent to the second network element carries a dual registration indication; The first network element and the second network element are located in the same first mobile network.

2. The method according to claim 1, further comprising: The registration behavior information is stored in the terminal context information of the first network element.

3. The method according to claim 1, wherein The obtaining of the registration behavior information of the terminal includes: receiving terminal context information sent by another first network element; The registration behavior information of the terminal is obtained from the terminal context information.

4. The method according to claim 1, wherein The obtaining of the registration behavior information of the terminal includes: Receiving an initial registration request sent by a terminal carrying terminal status information; The registration behavior information of the terminal is generated according to the terminal status information.

5. The method according to claim 4, wherein Generating the registration behavior information of the terminal according to the terminal status information includes: extracting a registration status of the terminal in the second mobile network from the terminal status information; Registration behavior information of the terminal is generated according to the registration status of the terminal in the second mobile network and the support status of the first type of network interoperability mode.

6. The method according to claim 5, wherein: The first type of network interoperability mode is used to indicate an interoperability mode of the terminal without an N26 interface between the second mobile network and the first mobile network, the second mobile network is a 4G network, and the first mobile network is a 5G network.

7. The method according to claim 5, wherein: The generating, according to the registration status of the terminal in the second mobile network and the support status of the first type of network interoperability mode, the registration behavior information of the terminal includes: In a case where the registration status of the terminal in the second mobile network is registered and the first mobile network supports a first type of network interoperability mode, a corresponding dual registration indication is generated.

8. The method according to any one of claims 1 to 3, wherein: The registration behavior information includes at least one of the following: a registration status of the terminal in the second mobile network; and a dual registration indication.

9. The method according to claim 8, wherein The determining, according to the registration behavior information, whether the registration request message sent to the second network element carries a dual registration indication includes: When the registration behavior information includes the registration status of the terminal in the second mobile network, the registration status of the terminal in the second mobile network is registered, and the first mobile network supports the first type of network interoperability mode, sending a registration request message carrying a dual registration indication to the second network element; or In a case where the registration behavior information includes a dual registration indication, a registration request message carrying the dual registration indication is sent to the second network element.

10. A dual registration processing method, applied to a second network element, comprising: receiving a registration request message sent by the first network element; determining whether to send a deregistration message to a third network element according to the terminal context information stored in the second network element and the registration request message; The first network element and the second network element are located in the same first mobile network.

11. The method according to claim 10, wherein: The determining, according to the terminal context information stored in the second network element and the registration request, whether to send a deregistration message to the third network element includes: If the registration request message sent by the first network element does not include a dual registration indication, and the terminal context information stored by the second network element includes a dual registration indication, not sending a deregistration message to the third network element; Alternatively, when the registration request message sent by the first network element includes a dual registration indication, no deregistration message is sent to the third network element.

12. A communication device comprising: memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9 or 10 to 11.

13. A storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 9 or 10 to 11.

Images