Registration removing method and related device

Abstract

The invention discloses a de-registration method and a related device, an interoperation interface is arranged between a first network and a second network, the first network receives a target de-registration event message pushed by the second network through the interoperation interface, and the target de-registration event message is de-registered according to target key information in the target de-registration event message. And sending a registration termination request to a target control node corresponding to the target terminal device, so that the target terminal device completes registration removal in the first network. Therefore, according to the embodiment of the invention, the interoperation interface is arranged between the first network and the second network, so that communication between the first network and the second network is realized on the basis of not adding hardware or reconstructing a network element; meanwhile, the first network subscribes to the de-registration event in the second network through the target subscription request, so that state-level synchronization can be realized, the probability of occurrence of a resource hanging problem caused by inconsistent de-registration states between the first network and the second network is reduced, and the overall performance of the network and the user experience are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a deregistration method and related device. BACKGROUND

[0002] With the rapid development of communication technology, new technologies and network architectures are constantly emerging to meet the growing demand of users and diversified business scenarios. Among them, IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) and 5GC are two different network domains, each with unique functions and characteristics. 5G core network (5GC) as a key component of 5G network, undertakes the important task of providing high-speed, low-latency, large-capacity communication services for users. At the same time, the IP multimedia subsystem (IMS) also plays an indispensable role in the communication network, which supports a variety of multimedia services such as voice calls, video calls, instant messages, etc., providing users with a rich communication experience.

[0003] In actual communication scenarios, users may need to seamlessly switch and work between the two domains to achieve various complex business functions. For example, when a user is making a voice call, he may need to switch from a 5G network to a Wi-Fi network during movement, which requires effective coordination between IMS and 5GC to ensure the continuity and quality of the call.

[0004] However, in related technologies, there are still some problems in the cross-domain coordination between IMS and 5GC. For example, if the deregistration state of 5GC cannot be synchronized to the IMS domain in time, it may cause the IMS domain resources to hang up, thereby affecting the overall performance of the network and user experience. SUMMARY

[0005] Based on the above problems, the present application provides a deregistration method and related device, aiming to solve the problem of IMS resource hanging up and improve the overall performance of the network and user experience.

[0006] The embodiments of the present application disclose the following technical solutions:

[0007] In a first aspect, the embodiments of the present application provide a deregistration method, which can be applied to a first network, and an interoperation interface is set between the first network and a second network, comprising:

[0008] receive, through the interoperation interface, a target deregistration event message pushed by the second network; wherein the target deregistration event message is a deregistration event message pushed to the first network in response to a target subscription request in a case that a target deregistration event is detected in the second network; the target subscription request represents a request for pushing the deregistration event message to the first network when the deregistration event occurs in the second network; and the target subscription request is sent by the first network to the second network through the interoperation interface;

[0009] send, according to the target key information in the target deregistration event message, a registration termination request to a target control node corresponding to the target terminal device, so as to complete deregistration of the target terminal device in the first network.

[0010] With reference to the first aspect, as a possible implementation manner, before receiving, through the interoperation interface, the target deregistration event message pushed by the second network, the method further includes:

[0011] obtaining a unique identifier of the target terminal device;

[0012] determining the target subscription request according to the unique identifier;

[0013] sending, through the interoperation interface, the target subscription request to the second network; wherein the second network is configured to process the target subscription request and send a processing result to the first network through the interoperation interface.

[0014] With reference to the first aspect, as a possible implementation manner, a service interface is further arranged between the first network and the second network; and the obtaining of the unique identifier of the target terminal device includes:

[0015] obtaining, through the service interface, the unique identifier of the target terminal device from the second network.

[0016] With reference to the first aspect, as a possible implementation manner, the sending of the registration termination request to the target terminal device according to the target key information in the target deregistration event message includes:

[0017] parsing the target deregistration event message to obtain a target identifier; wherein the target identifier represents a first identifier of the target terminal device in the second network and a second identifier of the target terminal device in the first network;

[0018] determining a target address corresponding to the target control node according to the first identifier;

[0019] sending the registration termination request to the target address according to the second identifier.

[0020] With reference to the first aspect, as a possible implementation manner, after receiving the registration termination request, the method further includes:

[0021] releasing target resources of the target terminal device in the first network according to the registration termination request, so that the target terminal device completes de-registration in the first network.

[0022] With reference to the first aspect, as a possible implementation manner, after the target resources are released, the method further includes:

[0023] updating a local state of the target terminal device in the first network in response to a target message, wherein the target message indicates that the release of the target resources is completed.

[0024] In the second aspect, an embodiment of the present application provides a de-registration method, which can be applied to a second network, and an interoperation interface is arranged between the second network and a first network, and the method comprises the following steps:

[0025] in a case where a target de-registration event is detected, pushing, in response to a target subscription request, a target de-registration event message to the first network through the interoperation interface;

[0026] wherein the target subscription request indicates a request of pushing a de-registration event message to the first network when a de-registration event occurs in the second network; and the target subscription request is sent by the first network to the second network through the interoperation interface.

[0027] wherein the target de-registration event message is used for sending a registration termination request to a target control node corresponding to the target terminal device through the first network according to target key information in the target de-registration event message, so that the target terminal device completes de-registration in the first network.

[0028] In the third aspect, an embodiment of the present application provides a de-registration device, which can be applied to a first network, and an interoperation interface is arranged between the first network and a second network, and the device comprises the following steps:

[0029] an obtaining unit, configured to receive a target de-registration event message pushed by the second network through the interoperation interface; wherein the target de-registration event message is a de-registration event message pushed to the first network in response to a target subscription request in a case where a target de-registration event is detected in the second network; the target subscription request indicates a request of pushing a de-registration event message to the first network when a de-registration event occurs in the second network; and the target subscription request is sent by the first network to the second network through the interoperation interface.

[0030] a sending unit, configured to send a registration termination request to a target control node corresponding to the target terminal device according to target key information in the target de-registration event message, so that the target terminal device completes de-registration in the first network.

[0031] In the fourth aspect, an embodiment of the present application provides a de-registration device, which can be applied to a second network, and an interoperation interface is arranged between the second network and a first network, and the device comprises the following steps:

[0032] The pushing unit is configured to, in response to the target subscription request, push, to the first network, a target deregistration event message via the interoperation interface, in a case where the target deregistration event is detected.

[0033] The target subscription request is a request for pushing, to the first network, a deregistration event message in a case where the deregistration event occurs in the second network.

[0034] The target deregistration event message is configured to send, to a target control node corresponding to the target terminal device via the first network, a registration termination request according to target key information in the target deregistration event message, so as to complete deregistration of the target terminal device in the first network.

[0035] In a fifth aspect, an embodiment of the present application provides a control device, including a processor and a memory, the memory is used to store programs, instructions or codes, and the processor is used to execute the programs, instructions or codes in the memory to complete the deregistration method in the first aspect or the second aspect.

[0036] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is loaded by a processor to execute the deregistration method in the first aspect or the second aspect.

[0037] Advantages:

[0038] The deregistration method provided by the embodiment of the present application can be applied to the first network, an interoperation interface is arranged between the first network and the second network, the first network receives a target deregistration event message pushed by the second network via the interoperation interface, sends a registration termination request to a target control node corresponding to a target terminal device according to target key information in the target deregistration event message, so as to complete deregistration of the target terminal device in the first network. The target deregistration event message is a deregistration event message pushed to the first network in response to a target subscription request in a case where the target deregistration event is detected in the second network. The target subscription request is a request for pushing, to the first network, a deregistration event message in a case where the deregistration event occurs in the second network. The target subscription request is sent by the first network to the second network via the interoperation interface.

[0039] Thus, by setting the interoperation interface between the first network and the second network, the embodiment of the present application realizes the communication between the first network and the second network without adding new hardware or reconstructing network elements; meanwhile, by subscribing to the deregistration event in the second network through the target subscription request of the first network, the state-level synchronization can be realized, the probability of the resource hanging problem caused by the inconsistency of the deregistration state between the first network and the second network is reduced, and the overall performance and user experience of the network are improved. BRIEF DESCRIPTION OF DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0041] Figure 1 A schematic diagram of an IMS and 5GC communication structure provided by an embodiment of the present application;

[0042] Figure 2 A flowchart of a deregistration method provided by an embodiment of the present application;

[0043] Figure 3 A flowchart of another deregistration method provided by an embodiment of the present application;

[0044] Figure 4 A schematic diagram of a deregistration process provided by an embodiment of the present application;

[0045] Figure 5 A structural schematic diagram of a deregistration device provided by an embodiment of the present application;

[0046] Figure 6 A structural schematic diagram of another deregistration device provided by an embodiment of the present application;

[0047] Figure 7 A structural schematic diagram of a control device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0048] As described above, in the related art, there are still some problems in the cross-domain cooperation of IMS and 5GC. As an example, the deregistration mechanism of the IMS domain relies on two triggering modes, one is the active triggering of the target terminal device, and the other is the timeout triggering of the IMS domain.

[0049] The target terminal device initiatively triggering refers to that when the target terminal device initiatively initiates a de-registration operation, the target terminal device needs to send a SIP BYE message to a P-CSCF (Proxy Call Session Control Function, which is the first contact point of the target terminal device accessing an IMS network). After the SIP BYE message is transmitted through the network, the S-CSCF (Serving Call Session Control Function, which is responsible for processing session control and services of the target terminal device) notifies the HSS (Home Subscriber Server, which stores important information such as user subscription data) to delete the registration context information of the target terminal device, and the de-registration is completed.

[0050] However, if the target terminal device has an abnormal situation, such as sudden power failure, network disconnection, etc., which leads to the SIP signaling cannot be normally sent, the mechanism of the target terminal device initiatively triggering the de-registration may fail.

[0051] The IMS domain timeout triggering refers to that the HSS detects the SIP registration validity period (for example, the default setting is 3600 seconds) of the target terminal device. If the SIP registration validity period exceeds the time limit, the HSS determines that the target terminal device is offline, and then sends an RTR (Registration Termination Request) to the S-CSCF to release the related network resources.

[0052] However, the mechanism of the IMS domain timeout triggering has obvious delay. Before the timeout, although the target terminal device may have actually been offline, the related resources of the IMS domain are still in the "hanging" state, which occupies the network resources and affects the overall capacity of the network.

[0053] Therefore, the embodiments of the present application provide a de-registration method and related apparatus. The method can be applied to a first network, and an interoperation interface is arranged between the first network and a second network. The first network receives a target de-registration event message pushed by the second network through the interoperation interface, and sends a registration termination request to a target control node corresponding to a target terminal device according to target key information in the target de-registration event message, so as to complete the de-registration of the target terminal device in the first network. The target de-registration event message is a de-registration event message pushed by the second network to the first network in response to a target subscription request in a case that the second network detects a target de-registration event. The target subscription request represents a request of pushing the de-registration event message to the first network in a case that the second network has the de-registration event. The target subscription request is sent by the first network to the second network through the interoperation interface.

[0054] Thus, this embodiment enables communication between the first and second networks by setting up an interoperability interface between them without adding hardware or reconstructing network elements. At the same time, by having the first network subscribe to deregistration events in the second network through a target subscription request, state-level synchronization can be achieved, reducing the probability of resource hang-ups caused by inconsistencies in deregistration states between the first and second networks, thereby improving overall network performance and user experience.

[0055] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0056] The collection and processing of relevant data (including but not limited to experimental data, test data, simulation data, user data, etc.) involved in this application shall strictly comply with the requirements of national laws and regulations when applied in the following embodiments, obtain the informed consent or separate consent of the subject obtaining the data information, and carry out data use and processing within the scope of laws and regulations and the authorization of the subject.

[0057] To facilitate the explanation of the application scenarios in the next embodiment, we will first introduce one possible application scenario in the embodiments of this application.

[0058] Combination Figure 1 As shown, this application uses IMS as the first network and 5GC as the second network as an example for illustration. In a 5G communication network, 5GC is responsible for the access management, session management, and unified management of user data of the target terminal device, while the IMS domain focuses on providing IP multimedia services (such as voice and video calls). The two need to achieve the coordination of user status and data through interoperability between core network elements.

[0059] Among them, UDM, as the core user data management network element of 5GC, stores the core network subscription data and registration status of the target terminal equipment; HSS, as the core user data network element of IMS domain, manages the IMS subscription data, registration context and S-CSCF (Service Call Session Control Function) allocation information of the target terminal equipment. The interoperability of the two is the key to realizing cross-domain collaboration.

[0060] To achieve communication between 5GC and IMS, according to the 3GPP TS 23.632 definition, the interoperability between UDM and HSS is implemented through a two-layer architecture of reference points and service interfaces, such as... Figure 1 As shown.

[0061] The NU1 reference point means a direct interoperation channel between the UDM and the HSS for implementing cross-domain state synchronization, and bears the functions of bidirectional interaction of "state notification" and "service calling". In the embodiment of the application, the HSS initiates a core network deregistration event subscription request (i.e. a target subscription request) to the UDM through the NU1 reference point, and the UDM pushes a target terminal device core network deregistration notification to the HSS through the NU1 reference point.

[0062] The NU2 reference point means an interaction channel between the HSS and the 5GS-UDR (5G system user data repository), and is used for the HSS to obtain 5G core network subscription data (such as the SUPI and IMSI mapping relationship, core network service permission, etc.) of a target terminal device. In the embodiment of the application, the HSS can obtain the unique identifier (such as the SUPI) of the target terminal device from the 5GS-UDR through the NU2 reference point before initiating the event subscription, so as to ensure the accuracy of the user identity of the subscription request.

[0063] The Nudm interface (i.e. an interoperation interface) means a service interface provided by the UDM to external network elements (including the HSS), complies with the 3GPP TS 29.503 "Unified Data Management Services" specification, and supports sub-services such as "event exposure (EventExposure)" and "user context management (UECM)". In the embodiment of the application, the Nudm_EventExposure sub-service can be used for the HSS to subscribe to a target terminal device core network deregistration event, and for the UDM to push the event notification to the HSS.

[0064] The Nhss interface (i.e. a service interface) means a service interface provided by the HSS to external network elements (including the UDM), and supports the UDM to obtain IMS subscription data (such as the public identifier SIPURI and IMS service permission, etc.) of a target terminal device. In the embodiment of the application, when pushing the deregistration event, if the UDM needs to supplement the IMS identity information of the target terminal device, the UDM can query the user public identifier from the HSS through the Nhss interface, so as to ensure the completeness of the notification information.

[0065] Referring to Figure 2 , the figure is a flowchart of a deregistration method provided by the embodiment of the application.

[0066] In combination with Figure 2 , the deregistration method provided by the embodiment of the application can be applied to a first network, an interoperation interface is arranged between the first network and a second network, and the method comprises the following steps:

[0067] S21: receiving a target deregistration event message pushed by the second network through the interoperation interface.

[0068] The target deregistration event message is a message pushed to the first network in response to a target subscription request when the second network detects a target deregistration event. It should be understood that when the second network detects that a target terminal device has deregistered (i.e., a target deregistration event), it will push a message containing target deregistration event information to the first network based on the previously received target subscription request. The target deregistration event message is used to inform the first network that a target terminal device has deregistered on the second network, requiring the first network to take appropriate action.

[0069] A target subscription request represents a request to push a deregistration event message to the first network when a deregistration event occurs in the second network. The target subscription request is sent from the first network to the second network via an interoperability interface. It should be understood that the target subscription request is a request sent from the first network to the second network, primarily requesting the second network to push a deregistration event message to the first network when a deregistration event occurs in its own network.

[0070] The target terminal device refers to the target terminal device that has experienced a deregistration event or needs to perform a deregistration operation. It may be a device with communication functions such as a mobile phone or tablet computer, and no specific limitation is made here.

[0071] S22: Based on the target key information in the target deregistration event message, send a registration termination request to the target control node corresponding to the target terminal device so that the target terminal device can complete deregistration in the first network.

[0072] The target control node refers to the node in the first network that is responsible for managing the registration status of target terminal devices, controlling their access and deregistration, etc.

[0073] A registration termination request is a request used to cause the target control node to perform a deregistration operation.

[0074] It should be understood that, in the embodiments of this application, by setting up an interoperability interface between the first network and the second network, communication between the first network and the second network can be realized without adding hardware or reconstructing network elements; at the same time, by having the first network subscribe to the deregistration event in the second network through a target subscription request, state-level synchronization can be achieved, reducing the probability of resource deadlock caused by the inconsistency of the deregistration state between the first network and the second network, and improving the overall network performance and user experience.

[0075] Based on the deregistration method provided in the above embodiments, in one possible implementation, before receiving the target deregistration event message pushed by the second network through the interoperability interface, the method further includes:

[0076] A1: Obtain the unique identifier of the target terminal device.

[0077] A unique identifier refers to a unique mark used to represent a target terminal device. It should be understood that since a communication network may include multiple target terminal devices, different target terminal devices may deregister at the same time, but the resources corresponding to different target terminal devices are different. Therefore, in order to avoid confusion, this application embodiment can accurately locate the target terminal device that has deregistered in the communication network by obtaining a unique identifier.

[0078] In one possible implementation, a service interface is also set up between the first network and the second network; correspondingly, the unique identifier of the target terminal device can be obtained from the second network through the service interface.

[0079] A2: Determine the target subscription request based on the unique identifier.

[0080] A target subscription request is essentially a specific information format. It contains information such as the type of event the second network needs to pay attention to (i.e., the event to register) and the identifier of the target terminal device. The second network can use the target subscription request to know under what circumstances (and for which target terminal device) to push a message to the first network.

[0081] As an example, suppose the first network (IMS) generates a subscription request message based on the phone's SUPI, which explicitly states that "when the phone corresponding to this SUPI experiences a deregistration event on 5GC (second network), please push a relevant notification to IMS."

[0082] A3: Send the target subscription request to the second network via the interoperability interface.

[0083] The second network is used to process the target subscription request and send the processing result to the first network through an interoperability interface.

[0084] It should be understood that after receiving the target subscription request from the first network, the second network will parse and process it. This processing may include, but is not limited to, verifying the validity of the request and checking whether it can fulfill the subscription request (e.g., whether it has the ability to monitor the target terminal device's deregistration event). After processing, the second network will generate a processing result and send it back to the first network through an interoperability interface. The processing result can be a successful subscription, indicating that the second network will push a message when a deregistration event occurs as requested; or a subscription failure with a reason for failure, such as the target terminal device not existing in the second network.

[0085] It should be understood that, in the embodiments of this application, the target subscription request is sent to the second network through the interoperability interface so as to establish a communication link between the first network and the second network regarding deregistration event notification. This enables the second network to push relevant messages to the first network according to the agreement represented by the target subscription request when it detects the deregistration event of the target terminal device, thereby realizing cross-network information interaction and collaborative work.

[0086] Based on the registration removal method provided in the above embodiments, in one possible implementation, step S21 may include:

[0087] B1: Parse the target's registration event message to obtain the target identifier.

[0088] The target identifier represents a first identifier of the target terminal device in the second network and a second identifier of the target terminal device in the first network. The first identifier represents a unique identifier of the target terminal device in the second network, used to distinguish it from other target terminal devices. For example, the first identifier can be SUPI, used for core domain authentication. The second identifier refers to a unique identifier of the target terminal device in the first network. For example, the second identifier can be SIPURI.

[0089] It should be understood that by obtaining the unique identifier of the target terminal device in the first network and the second network, the target terminal device and its related resources can be accurately processed in the first network or the second network, thus ensuring the uniqueness of the target terminal device's identity.

[0090] B2: Determine the target address corresponding to the target control node based on the first identifier.

[0091] The target address refers to the unique address of the target control node in the first network.

[0092] It should be understood that locating the unique address (i.e., the target address) of the target control node in the first network that can process the relevant resources of the target terminal device through the first identifier is beneficial for the second network to quickly locate the target control node in the first network that can perform the relevant operation when the target terminal device undergoes a deregistration operation, and to use the target control node to process the relevant resources of the target terminal device, thereby improving the response speed.

[0093] B3: Send a registration termination request to the target address based on the second identifier.

[0094] It should be understood that, since the representation of the target terminal device differs in different networks, after the first network receives the target deregistration event message and determines the target address, it can send a registration termination request to the target address by combining the second identifier of the target terminal device in its own network, thus preserving the original context of the core network deregistration and facilitating accurate processing by the IMS domain.

[0095] Based on the deregistration method provided in the above embodiments, in one possible implementation, after receiving the registration termination request, the method further includes: releasing the target resources of the target terminal device in the first network according to the registration termination request, so that the target terminal device can complete the deregistration in the first network.

[0096] Target resources refer to the resources of the target terminal device in the first network related to the deregistration operation.

[0097] It should be understood that by releasing the target resources, zombie sessions can be prevented from occupying network resources and system capacity can be increased; at the same time, by releasing the target resources, active sessions can be forcibly terminated, avoiding inconsistencies in user states (such as the core network having deregistered but the IMS session still being alive).

[0098] In one possible implementation, after releasing the target resource, the method further includes: updating the local state of the target terminal device in the first network in response to the target message.

[0099] The target message indicates that the target resource has been released.

[0100] It should be understood that by updating the local status of the target terminal device, the accuracy of HSS as an authoritative data source can be ensured, and a reliable status benchmark can be provided for subsequent user re-registration or cross-domain switching.

[0101] Based on the registration removal method provided in the above embodiments, combined with Figure 3 As shown in the embodiments of this application, a deregistration method is also provided. This method is applied to a second network, and an interoperability interface is set between the second network and the first network, including:

[0102] S31: Upon detecting a target deregistration event, in response to a target subscription request, push a target deregistration event message to the first network via the interoperability interface.

[0103] The target subscription request is a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent from the first network to the second network through an interoperability interface.

[0104] The target deregistration event message is used to send a registration termination request to the target control node corresponding to the target terminal device through the first network based on the target key information in the target deregistration event message, so that the target terminal device can complete deregistration on the first network.

[0105] In one possible implementation, before pushing the target to register the event message to the first network via the interoperability interface, the following is also included:

[0106] The target subscription request is received from the first network via the interoperability interface; wherein the target subscription request is determined based on the unique identifier of the target terminal device.

[0107] The target subscription request is processed, and the processing result is sent to the first network through the interoperability interface.

[0108] In one possible implementation, a service interface is also set up between the first network and the second network; through the service interface, the first network obtains the unique identifier of the target terminal device from the second network.

[0109] It should be understood that, in the embodiments of this application, by setting up an interoperability interface between the first network and the second network, communication between the first network and the second network can be realized without adding hardware or reconstructing network elements; at the same time, by having the first network subscribe to the deregistration event in the second network through a target subscription request, state-level synchronization can be achieved, reducing the probability of resource deadlock caused by the inconsistency of the deregistration state between the first network and the second network, and improving the overall network performance and user experience.

[0110] Based on the registration removal method provided in the above embodiments, combined with Figure 4 As shown, this application embodiment also provides a registration removal process, combined with Figure 1 The network structure of IMS (first network) and 5GC (second network) is shown below. The following describes a registration-free interaction process between IMS and 5GC provided by an embodiment of this application.

[0111] It should be understood that the embodiments of this application are based on the interoperability interface between UDM and HSS (NU1 reference point + Nudm_EventExposure service) to build a cross-domain collaborative mechanism of "core network deregistration event subscription - notification - IMS deregistration trigger".

[0112] Interface extension refers to adding the "CORE_NETWORK_DEREGISTRATION" event type to the "EventType" enumeration of the Nudm_EventExposure service defined in 3GPP TS 29.503, used to identify "the target terminal device has completed core network deregistration". As an example, based on 3GPP TS 29.503, the "EventType" enumeration value of the Nudm_EventExposure service is extended to add a core network deregistration event type, as defined in the table below:

[0113] Table 1: EventType Values:

[0114]

[0115] It should be understood that by adding this event type, UDM can clearly identify and handle situations where the target terminal device has completed core network deregistration, providing a basis for subsequent subscription and notification mechanisms.

[0116] The subscription mechanism refers to the HSS acting as a service consumer, calling the UDM's Nudm_EventExposure service through the NU1 reference point to subscribe to the target terminal device's "CORE_NETWORK_DEREGISTRATION" event.

[0117] It should be understood that by subscribing to this event, HSS can receive timely notifications when the target terminal device completes core network deregistration, thereby taking appropriate measures.

[0118] Event detection and notification refers to the UDM detecting the registration of the target terminal device's core network through the Nudm_UECM_Deregister request initiated by the AMF, triggering an event notification, and pushing a notification message containing "user identifier, reason for deregistration, and timestamp" to the HSS through the NU1 reference point.

[0119] Event detection refers to the UDM detecting the core network deregistration event (i.e., the target deregistration event message) of the target terminal device by receiving the Nudm_UECM_Deregister request initiated by the AMF.

[0120] Event notification refers to the UDM triggering the event notification mechanism once an event is detected, pushing a notification message containing key information such as "user identifier, reason for deregistration, and timestamp" to HSSs that have subscribed to the event through the NU1 reference point (i.e., the target deregistration event message).

[0121] It should be understood that by promptly notifying the HSS, the UDM ensures that the IMS domain can remain synchronized with the core network deregistration events, providing a basis for subsequent IMS deregistration triggering.

[0122] IMS deregistration triggering refers to the HSS receiving a notification and sending an RTR request to the S-CSCF to which the target terminal device belongs, triggering the deletion of the IMS domain registration context and release of resources, and synchronously updating the local user status.

[0123] Receiving notification means that HSS receives the deregistration event notification message pushed by UDM.

[0124] Triggering an RTR request (i.e., a registration termination request) means that the HSS sends an RTR (Register Termination Request) request to the S-CSCF to which the target terminal device belongs, based on the information in the notification message.

[0125] Deleting the registration context means that after receiving an RTR request, the S-CSCF deletes the IMS domain registration context associated with the target terminal device and releases the related resources.

[0126] Updating the local user status means that the HSS also updates the local user status to reflect the deregistration status of the target terminal device in the IMS domain.

[0127] It should be understood that by triggering the IMS deregistration process, the consistency of user status between the IMS domain and the core network is ensured, thereby improving the efficiency and accuracy of network management.

[0128] Based on the above explanation, the registration removal process provided in this application embodiment can be as follows:

[0129] Step 1: HSS registers events with the UDM core network (based on the Nudm_EventExposure service).

[0130] HSS obtains the unique identifier of the target terminal device: HSS calls the Nudr_DataRepository service of 5GS-UDR through the NU2 reference point to query the mapping relationship between the SUPI (5G user permanent identifier) ​​and IMSI of the target terminal device to ensure that the identity of the subscribing user is unique;

[0131] Initiating a subscription request: The HSS, acting as a service consumer, sends a Nudm_EventExposure_Subscribe request (i.e., a target subscription request) to the UDM through the NU1 reference point. The request parameters include:

[0132] Event Type: CORE_NETWORK_DEREGISTRATION;

[0133] User ID: SUPI (e.g., imsi-460011234567890);

[0134] Notification Address: The URL of the HSS event receiving endpoint (e.g., https: / / hss.example.com / nudm / ee / notify).

[0135] Subscription expiry time: 86,400 seconds by default (configurable);

[0136] UDM responds to subscription requests: After verifying the validity of the user identifier (by querying the HSS via the Nhss interface to confirm that the target terminal device has enabled IMS service), the UDM generates a unique subscription ID and returns a subscription response to the HSS through the NU1 reference point. The response content (i.e., the processing result) includes:

[0137] Result Indication: SUCCESS (subscription successful) / INVALID_USER (invalid user);

[0138] Subscription ID: e.g., sub-123456789 (used for subsequent notification association);

[0139] Subscription expiry time: Same as the subscription request.

[0140] It should be understood that obtaining the unique identifier of the target terminal device through HSS ensures that the identity of the subscribing user is unique and accurate, avoiding subscription errors due to identifier confusion; initiating a subscription request allows the UDM to indicate to the HSS that it wishes to subscribe to the core network of the specific target terminal device to register events, so that timely notifications can be obtained when events occur; and the UDM's response to the subscription request informs the HSS of the processing result of the subscription request and provides the subscription ID required for subsequent notification association.

[0141] In this embodiment, SUPI-IMSI mapping query and IMS service pre-verification ensure that the subscriber's identity is unique and the service is valid, avoiding wasted resources due to invalid subscriptions; configurable subscription validity period and unique subscription ID (SubscriptionID) enable flexible management and support dynamic adjustment of the audit cycle; a two-way communication mechanism based on 3GPP standard authentication ensures the security of HSS and UDM interaction and provides a reliable foundation for subsequent cross-domain event linkage.

[0142] Step 2: AMF detects the core network to register and notifies UDM (based on Nudm_UECM service).

[0143] AMF triggers deregistration: When the AMF detects a deregistration event in the core network of the target terminal device (such as the UE actively powering off and sending a Detach Request, or TAU (Tracking Area Update) timeout), it generates a deregistration reason code (01 = UE actively initiated, 03 = network timeout).

[0144] It should be understood that registration is triggered through AMF so that when the target terminal device attempts to register with the core network, AMF needs to detect this in a timely manner and generate the corresponding registration reason code.

[0145] AMF calls UDM to register the service: AMF sends a Nudm_UECM_Deregister request to UDM through the Nudm_UECM service, with parameters including:

[0146] User Identifier (SUPI): Target terminal device SUPI;

[0147] Deregistration Cause Code: 01 / 03;

[0148] Deregistration Timestamp: The time the event occurred.

[0149] It should be understood that the AMF calls the UDM to register the service so that the UDM can be informed of the deregistration information of the target terminal device, so that the UDM can update local data and perform subsequent processing.

[0150] UDM confirms registration: After deleting the core network registration context (such as AMF identifier and session binding information) of the local target terminal device and updating the 5GS-UDR data, the UDM sends a confirmation message to the AMF confirming registration with the core network. The message includes:

[0151] Result identifier: SUCCESS (Core network resources released successfully);

[0152] Reason for registration: Same as AMF request.

[0153] It should be understood that the deregistration confirmation via UDM is used to inform the AMF that the release of core network resources has been completed, ensuring that both parties have consistent processing status for the deregistration event.

[0154] In this embodiment, the reasons for deregistration (UE-initiated / network timeout) are finely distinguished to provide context for subsequent UDM processing; UDM synchronously updates 5GS-UDR data to ensure the consistency of network resource status; the low-latency synchronization confirmation mechanism avoids AMF blocking, ensures service continuity in scenarios such as core network switching and shutdown, and meets 3GPP requirements for signaling processing efficiency.

[0155] Step 3: UDM pushes core network registration event notifications to HSS (based on Nudm_EventExposure service).

[0156] UDM triggers event notification: After the UDM completes the core network deregistration process, it detects that the event has been subscribed to by the HSS (by matching the Subscription ID in Phase 1) and generates an event notification message.

[0157] It should be understood that event notifications are triggered via UDM so that, based on previous HSS subscription requests, a corresponding event notification message is generated after the core network registration event is detected.

[0158] UDM push notification: UDM sends a Nudm_EventExposure_Notify request to the HSS notification address via the NU1 reference point, with parameters including:

[0159] Subscription ID: sub-123456789 (associated with the subscription in step 1);

[0160] User Identifier: SUPI+IMS Public Identifier (SIPURI, obtained from HSS via the Nhss interface, such as sip:user123@example.com).

[0161] Event type: CORE_NETWORK_DEREGISTRATION;

[0162] Go to registration details: Reason code (01 / 03), timestamp.

[0163] It should be understood that UDM push notifications are used to push detailed information about the core network deregistration event to the HSS, so that the HSS can trigger the subsequent IMS deregistration process.

[0164] HSS Confirmation of Receipt: After verifying the validity of the subscription ID and parsing the notification parameters, the HSS returns a notification receipt confirmation to the UDM, which includes:

[0165] Result identifier: RECEIVED (Received, ready to trigger IMS to register);

[0166] Processing status: PENDING (Pending IMS registration).

[0167] It should be understood that receiving the notification via HSS is to inform the UDM that the notification has been received and to indicate that preparations are being made to trigger IMS registration.

[0168] In this embodiment, cross-domain identifier association (SUPI+SIPURI) ensures that RTR messages are accurately routed to the target S-CSCF; subscription ID verification and asynchronous confirmation mechanism (PENDING state) prevent notification forgery and duplicate pushes; detailed timestamps and deregistration reason records provide high-precision audit data for billing and fault location, supporting operators to quickly troubleshoot anomalies.

[0169] Step 4: HSS sends an RTR request to S-CSCF, triggering IMS to register.

[0170] HSS queries S-CSCF allocation information: HSS queries the local "user-S-CSCF" association record to obtain the S-CSCF address to which the target terminal device currently belongs (e.g., scscf1.example.com).

[0171] It should be understood that by querying the S-CSCF allocation information through HSS, the S-CSCF address to which the target terminal device currently belongs can be determined, so that an RTR request can be sent to it.

[0172] HSS sends an RTR request: The HSS sends an RTR (Registration Termination Request) message to the target S-CSCF, with parameters including:

[0173] User public identifier: SIPURI (sip:user123@example.com);

[0174] Register a trigger source: CORE_NETWORK (identifies that it is triggered by a core network event);

[0175] Session Release Indication: TRUE (requires S-CSCF to release all IMS sessions on the target terminal device).

[0176] It should be understood that an RTR request is sent via HSS to request S-CSCF to release the IMS registration context and all IMS sessions of the target terminal device.

[0177] S-CSCF releases IMS resources: The S-CSCF deletes the target terminal device's IMS registration context (such as P-CSCF address, session binding information), terminates all active multimedia sessions, and returns an RTA (Registration Termination Answer) message to the HSS, the content of which includes:

[0178] Result identifier: SUCCESS (IMS resource release completed);

[0179] Release details: Number of sessions released, timestamp.

[0180] It should be understood that releasing IMS resources through S-CSCF allows the release of IMS-related resources of the target terminal device according to the request of HSS, ensuring that the state of the IMS domain is consistent with that of the core network.

[0181] In this embodiment, by forcibly releasing all IMS sessions, vulnerabilities caused by IMS session remnants after the core network deregisters are avoided; the local S-CSCF address cache is dynamically queried to reduce DNS query latency; and the RTA response feedback on the number of released sessions helps the HSS locate anomalies of unterminated sessions, ensuring that resources are completely released.

[0182] Step 5: HSS updates local IMS registration status

[0183] After receiving the RTA response from the S-CSCF, the HSS performs a local state update:

[0184] Clear the "User-S-CSCF" associated record;

[0185] The target terminal device's IMS registration status is marked as "Unregistered".

[0186] Record the timestamp of IMS registration completion for subsequent auditing and troubleshooting.

[0187] It should be understood that updating the local IMS registration status through HSS ensures that the user IMS registration status stored locally by HSS is consistent with the actual situation, facilitating subsequent management and querying.

[0188] In this embodiment, the accuracy of HSS as an authoritative data source is maintained by clearing the "User-S-CSCF" associated record and marking it as "unregistered"; the timestamp record supports tracing the user's online time and unregistration history, meeting compliance audit requirements; the state machine design provides an extended foundation for subsequent user re-registration or prepaid control and other businesses.

[0189] Based on the deregistration method provided in the above embodiments, see [link to relevant documentation]. Figure 5 This application also provides a schematic diagram of the structure of a deregistration device.

[0190] Combination Figure 5 As shown, the deregistration device 50 provided in this embodiment is applied to a first network, and an interoperability interface is set between the first network and a second network, including:

[0191] The acquisition unit 51 is used to receive a target deregistration event message pushed by the second network through an interoperability interface; wherein, the target deregistration event message is a deregistration event message pushed to the first network in response to a target subscription request when the second network detects a target deregistration event; the target subscription request is a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent by the first network to the second network through the interoperability interface;

[0192] The sending unit 52 is used to send a registration termination request to the target control node corresponding to the target terminal device based on the target key information in the target deregistration event message, so that the target terminal device can complete deregistration in the first network.

[0193] As one possible implementation, before obtaining unit 51, a determining unit is also included, used for:

[0194] Obtain the unique identifier of the target terminal device;

[0195] The target subscription request is determined based on a unique identifier;

[0196] The target subscription request is sent to the second network through the interoperability interface; the second network processes the target subscription request and sends the processing result to the first network through the interoperability interface.

[0197] As one possible implementation, a service interface is also provided between the first network and the second network; the determining unit is used for:

[0198] The unique identifier of the target terminal device is obtained from the second network through a service-oriented interface.

[0199] As one possible implementation, the sending unit 52 is used for:

[0200] The target deregistration event message is parsed to obtain the target identifier; wherein, the target identifier represents the first identifier of the target terminal device in the second network and the second identifier of the target terminal device in the first network;

[0201] The target address corresponding to the target control node is determined based on the first identifier;

[0202] A registration termination request is sent to the target address based on the second identifier.

[0203] As one possible implementation, after receiving the registration termination request, the sending unit 52 is further configured to:

[0204] Release the target resources of the target terminal device in the first network according to the registration termination request, so that the target terminal device can complete the deregistration in the first network.

[0205] As one possible implementation, after releasing the target resource, the sending unit 52 is further configured to:

[0206] In response to the target message, the local state of the target terminal device in the first network is updated; wherein, the target message indicates that the release of the target resource is complete.

[0207] It should be noted that the deregistration device provided in this application embodiment has the same beneficial effects as the deregistration method provided in the above embodiments, and therefore will not be described again.

[0208] Based on the deregistration method provided in the above embodiments, see [link to relevant documentation]. Figure 6 This application also provides a schematic diagram of the structure of a deregistration device.

[0209] Combination Figure 6 As shown, the deregistration device 60 provided in this embodiment is applied to a second network, and an interoperability interface is set between the second network and the first network, including:

[0210] Push unit 61 is used to push a target deregistration event message to the first network through an interoperability interface in response to a target subscription request when a target deregistration event is detected.

[0211] The target subscription request is represented as a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent from the first network to the second network through an interoperability interface.

[0212] The target deregistration event message is used to send a registration termination request to the target control node corresponding to the target terminal device through the first network based on the target key information in the target deregistration event message, so that the target terminal device can complete deregistration on the first network.

[0213] In one possible implementation, before pushing the target to register the event message to the first network via the interoperability interface, the system further includes: a receiving unit, configured to:

[0214] The target subscription request is received from the first network via the interoperability interface; wherein the target subscription request is determined based on the unique identifier of the target terminal device.

[0215] The target subscription request is processed, and the processing result is sent to the first network through the interoperability interface.

[0216] In one possible implementation, a service interface is also provided between the first network and the second network; a receiving unit is used for the first network to obtain the unique identifier of the target terminal device from the second network through the service interface.

[0217] It should be noted that the deregistration device provided in this application embodiment has the same beneficial effects as the deregistration method provided in the above embodiments, and therefore will not be described again.

[0218] In one possible implementation, see Figure 7 The figure is a schematic diagram of a control device provided in an embodiment of this application.

[0219] The control device may include a memory 711 and a processor 712. For example... Figure 7 As shown, the memory can be random access memory (RAM), flash memory, read-only memory (ROM), EPROM, non-volatile read-only memory (Electronic Programmable ROM), registers, hard disks, removable disks, etc.

[0220] The memory 711 can store computer instructions. When the computer instructions stored in the memory 711 are executed by the processor 712, the processor 712 can be used to perform a deregistration method. The memory 711 can also store data.

[0221] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape) or a semiconductor medium (e.g., solid-state disk (SSD)).

[0222] This application also provides a readable storage medium for storing the methods provided in the above embodiments. Examples include random access memory (RAM), flash memory, read-only memory (ROM), EPROM, non-volatile read-only memory (EPROM), registers, hard disks, removable disks, or any other form of storage medium in the art.

[0223] In the embodiments of this application, the terms "first" and "second" (if they exist) are used only as name identifiers and do not represent the order of first and second.

[0224] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. Regarding the methods disclosed in the embodiments, since they correspond to the product embodiments disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the description of the product embodiments.

[0225] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for deregistering, characterized in that, The method is applied to a first network, and an interoperability interface is established between the first network and a second network, including: The interoperability interface receives a target deregistration event message pushed by the second network; wherein, the target deregistration event message is a deregistration event message pushed to the first network in response to a target subscription request when the second network detects a target deregistration event; the target subscription request is a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent by the first network to the second network through the interoperability interface. Based on the target key information in the target deregistration event message, a registration termination request is sent to the target control node corresponding to the target terminal device, so that the target terminal device can complete deregistration in the first network.

2. The deregistration method according to claim 1, characterized in that, Before receiving the target registration event message pushed by the second network through the interoperability interface, the process also includes: Obtain the unique identifier of the target terminal device; The target subscription request is determined based on the unique identifier; The target subscription request is sent to the second network through the interoperability interface; wherein the second network processes the target subscription request and sends the processing result to the first network through the interoperability interface.

3. The deregistration method according to claim 2, characterized in that, A service interface is also provided between the first network and the second network; obtaining the unique identifier of the target terminal device includes: The unique identifier of the target terminal device is obtained from the second network through the service interface.

4. The deregistration method according to claim 1, characterized in that, The step of sending a registration termination request to the target terminal device based on the target key information in the registration event message includes: The target deregistration event message is parsed to obtain the target identifier; wherein, the target identifier represents the first identifier of the target terminal device in the second network and the second identifier of the target terminal device in the first network; The target address corresponding to the target control node is determined based on the first identifier; The registration termination request is sent to the target address based on the second identifier.

5. The deregistration method according to claim 1, characterized in that, After receiving the registration termination request, the process also includes: Release the target resources of the target terminal device in the first network according to the registration termination request, so that the target terminal device can complete the deregistration in the first network.

6. The deregistration method according to claim 5, characterized in that, After releasing the target resource, the following is also included: In response to the target message, the local state of the target terminal device in the first network is updated; wherein the target message indicates that the target resource release is complete.

7. A method for deregistering, characterized in that, The method is applied to a second network, wherein an interoperability interface is established between the second network and the first network, including: Upon detecting a target deregistration event, in response to a target subscription request, a target deregistration event message is pushed to the first network via the interoperability interface; The target subscription request is defined as a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent by the first network to the second network through the interoperability interface. The target deregistration event message is used to send a registration termination request to the target control node corresponding to the target terminal device through the first network based on the target key information in the target deregistration event message, so that the target terminal device can complete deregistration on the first network.

8. A deregistration device, characterized in that, The device is applied to a first network, and an interoperability interface is provided between the first network and a second network, including: The acquisition unit is configured to receive a target deregistration event message pushed by the second network through the interoperability interface; wherein, the target deregistration event message is a deregistration event message pushed to the first network in response to a target subscription request when the second network detects a target deregistration event; the target subscription request is a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent by the first network to the second network through the interoperability interface; The sending unit is used to send a registration termination request to the target control node corresponding to the target terminal device based on the target key information in the target registration event message, so that the target terminal device can complete deregistration in the first network.

9. A deregistration device, characterized in that, The device is applied to a second network, and an interoperability interface is provided between the second network and the first network, including: The push unit is used to push a target deregistration event message to the first network through the interoperability interface in response to a target subscription request when a target deregistration event is detected. The target subscription request is defined as a request to push a deregistration event message to the first network when a deregistration event occurs in the second network; the target subscription request is sent by the first network to the second network through the interoperability interface. The target deregistration event message is used to send a registration termination request to the target control node corresponding to the target terminal device through the first network based on the target key information in the target deregistration event message, so that the target terminal device can complete deregistration on the first network.

10. A computer-readable storage medium, characterized in that, The system contains a computer program that is loaded by a processor to execute the deregistration method as described in any one of claims 1-7.

Images