Business disaster tolerance processing method and device and electronic equipment
By receiving query request messages on the user information sharing platform and providing user registration information, the service transmission problem caused by HSS failure in the IMS domain is solved, and the reliability of the network is improved.
Patent Information
- Application Number
- CN202411159439.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-22
- Publication Date
- 2024-11-22
AI Technical Summary
In the Internet Protocol Multimedia Subsystem (IMS) domain, when the home user server (HSS) corresponding to the target network element fails, the service cannot be transmitted normally, affecting the user's hosted service.
The user information sharing platform receives the query request message sent by the target network element, determines the user registration information in the pre-stored data according to the request type, and sends it to the target network element, so that it can transmit business according to the user registration information.
In the case of HSS failure, by providing user registration information, ensure that the service transmission process is not affected and the reliability of the IMS network is improved.
Smart Images

Figure CN119011370A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a service disaster recovery processing method, device and electronic equipment. Background Art
[0002] In the current technical solution, after the user completes the initial registration in the Internet Protocol Multimedia Subsystem (IMS) domain, before the next registration refresh, if both the primary Home Subscriber Server (HSS) and the disaster recovery HSS fail, the user cannot be called in the IMS domain. After the periodic refresh registration timer times out, the user fails to register in the IMS domain due to the failure of interaction with the HSS, and the user's calling and called services in the IMS domain are affected. That is, if the HSS corresponding to the target network element fails, the services of the target network element cannot be transmitted normally. Summary of the invention
[0003] The purpose of the embodiments of the present application is to provide a service disaster recovery processing method, device and electronic device, which can solve the problem that the service of the target network element cannot be transmitted normally when the HSS corresponding to the target network element fails.
[0004] In a first aspect, an embodiment of the present application provides a service disaster recovery processing method, which is applied to a user information sharing platform, and the method includes:
[0005] Receiving a query request message sent by a target network element, wherein the query request message is sent by the target network element when it is determined that a home subscriber server HSS corresponding to the target network element fails;
[0006] Determining, according to the request type of the query request message, user registration information corresponding to the request type in pre-stored data;
[0007] The user registration information is sent to the target network element, so that the target network element performs service transmission according to the user registration information.
[0008] In a second aspect, an embodiment of the present application provides another service disaster recovery processing method, which is applied to a network element. The method includes:
[0009] When determining that the corresponding home subscriber server HSS fails, a query request message is sent to the user information sharing platform.
[0010] Receiving the user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message;
[0011] Business transmission is performed according to the user registration information.
[0012] In a third aspect, an embodiment of the present application provides a service disaster recovery processing device, which is applied to a user information sharing platform, and the device includes:
[0013] A first receiving module, configured to receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it is determined that a home subscriber server HSS corresponding to the target network element fails;
[0014] A determination module, configured to determine user registration information corresponding to the request type in pre-stored data according to the request type of the query request message;
[0015] The first sending module is used to send the user registration information to the target network element, so that the target network element performs service transmission according to the user registration information.
[0016] In a fourth aspect, an embodiment of the present application provides another service disaster recovery processing device, which is applied to a network element, and the device includes:
[0017] The second sending module is used to send a query request message to the user information sharing platform when it is determined that the corresponding home subscriber server HSS fails.
[0018] A second receiving module, configured to receive the user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message;
[0019] The transmission module is used to perform service transmission according to the user registration information.
[0020] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.
[0021] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.
[0022] In the seventh aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.
[0023] In an eighth aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the first aspect or the second aspect.
[0024] In an embodiment of the present application, the user information sharing platform can receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it determines that the corresponding home user server HSS is faulty, and then determines the user registration information corresponding to the request type in the pre-stored data according to the request type of the query request message; finally, the user registration information is sent to the target network element so that the target network element transmits services according to the user registration information. In the event that the HSS corresponding to the target network element fails, the user information sharing platform sends the user registration information corresponding to the target network element to the target network element so that the target network element transmits services according to the user registration information, thereby ensuring that the service transmission process is not affected and improving the reliability of the IMS network. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 A schematic diagram showing initial user registration provided by an embodiment of the present application is shown;
[0026] Figure 2 A schematic diagram showing user logout provided by an embodiment of the present application;
[0027] Figure 3 A schematic diagram showing a process of a VoLTE user calling a registered VoLTE user provided in an embodiment of the present application;
[0028] Figure 4 A schematic diagram showing a process of a VoLTE user calling an unregistered VoLTE user provided in an embodiment of the present application;
[0029] Figure 5 A schematic diagram showing a process flow of a service disaster recovery processing method provided by an embodiment of the present application;
[0030] Figure 6 A schematic diagram showing a process flow of another service disaster recovery processing method provided by an embodiment of the present application;
[0031] Figure 7 A schematic diagram showing a process flow of user update provided by an embodiment of the present application is shown;
[0032] Figure 8 A schematic diagram showing the structure of a service disaster recovery processing device provided in an embodiment of the present application is shown;
[0033] Fig. 9 A schematic diagram showing the structure of another service disaster recovery processing device provided in an embodiment of the present application is shown;
[0034] Fig.10 A structural block diagram of an electronic device provided by an exemplary embodiment of the present application is shown;
[0035] Fig.11 A structural block diagram of another electronic device provided by an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION
[0036] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0037] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0038] In the related technologies, with the development of mobile communication technology, traditional voice communication services can no longer meet people's communication requirements. People are in urgent need of experiencing new media services. This multimedia communication is not just simple audio and video communication, but also includes instant messaging, same-site browsing, collaborative work, streaming media and other services, especially the integration of new communication methods and traditional voice communication services. Based on the trend of Internet and telecommunication network integration, the 3rd Generation Partnership Project (3GPP) introduced the IMS, a full Internet Protocol (IP) service network architecture, on the basis of the packet bearer network. The goal of IMS is to provide multimedia communication experience according to personalized user data, shield user access methods, control the degree of openness of service capabilities, and provide multimedia communication experience.
[0039] The most important functional entities in IMS are the Call Session Control Function (CSCF) and the Home Subscriber Server. There are three types of CSCF: Serving-Call Session Control Function (S-CSCF), Proxy-Call Session Control Function (P-CSCF), and Interrogating-Call Session Control Function (I-CSCF).
[0040] P-CSCF provides an access point for all terminals. Signaling of all types of terminal devices must pass through P-CSCF, which converts it into Session Initiation Protocol (SIP) signaling to access the IMS network.
[0041] I-CSCF is actually the first access point of the local network. It is responsible for transferring the call request to the appropriate S-CSCF. It will ask the HSS which S-CSCF is suitable to serve the call, and then transfer the call to the S-CSCF.
[0042] S-CSCF provides users with services requested by users, such as helping users find called users. It will obtain user configuration information from HSS, know what services the user has subscribed to, and then access the corresponding application server (AS) to let AS provide specific services. It is only a service locator, not a provider. An IMS network allows multiple S-CSCFs, each with different capabilities. HSS will assign the appropriate S-CSCF to the user based on the user's configuration information.
[0043] PSBC is a network element that integrates Session Border Controller (SBC), P-CSCF, Access Transfer Control Functionality (ATCF), and ATGW (Access Transfer Gateway). It connects the IMS core network / soft switch network with the external user access area, completes the service access of IMS / soft switch users, realizes the interoperability of user services in different network environments, and ensures the security of IMS / soft switch networks.
[0044] Figure 1This is the initial registration process for users in the IMS domain. After the user completes the initial registration, the User Equipment (UE) can initiate a refresh registration process at fixed intervals according to the instructions of the network. The user refresh registration process involves interaction with the HSS, so after all HSS failures, the user refresh registration process fails, resulting in the user's registration failure in the IMS domain. PSBC, S-CSCF and AS will delete the saved user registration information. The user is not registered in the IMS network, and the user cannot page the user or initiate a call in the IMS network.
[0045] Figure 2 This is the deregistration process for users in the IMS domain.
[0046] Figure 3 The present invention is a flowchart of a Voice over Long-Term Evolution (VoLTE) user calling a registered VoLTE user, including the called process after the user activates the IMS service and completes the registration in the IMS domain.
[0047] Step 1-7: The user initiates a call in the IMS domain. The INVITE message can be sent to the S-CSCF via the PSBC. After the S-CSCF triggers the AS in sequence according to the calling party's contract, the INVITE message is sent back to the S-CSCF. The S-CSCF can query the telephone number mapping domain name system (E.164 Number URI Mapping Domain Name System, ENUMDNS), and send the INVITE message to the called side I-CSCF based on the returned Session Initiation Protocol Uniform Resource Identifier (SIP_URI), Service Locator (SRV) query and address (A) query results.
[0048] Steps 8-10: The I-CSCF sends a Location-Info-Request (LIR) message to the converged HSS / Home Location Register (HLR), requesting the name of the S-CSCF currently providing services to the user. The converged HSS / HLR returns a Location-Info-Answer (LIA) message, providing the server address of the S-CSCF. The I-CSCF routes the call to the S-CSCF.
[0049] Steps 11-16: S-CSCF triggers the called party's AS (including the called party's Service Centralization and Continuity Application Server (SCC AS)) in sequence according to the saved IFC / SIFC subscription data of the registered called user. The called party's SCC AS performs called domain selection: if the user resides in the 4 / 5G network, the called VoLTE user is connected in the IMS domain. SCC AS sends the INVITE message back to S-CSCF, and S-CSCF sends the INVITE message to the called UE through PSBC.
[0050] Figure 4 The flowchart is a VoLTE user calling an unregistered VoLTE user (residing in the circuit domain), including the called process when the user is not registered in the IMS domain.
[0051] Step 1-7: The user initiates a call in the IMS domain, and the INVITE message is sent to the S-CSCF via the PSBC. The S-CSCF triggers the AS in sequence according to the calling party's subscription, and the INVITE message is sent back to the S-CSCF. The S-CSCF queries ENUMDNS and sends the INVITE message to the I-CSCF on the called side based on the returned SIP_URI, SRV query and A query results.
[0052] Steps 8-10: The I-CSCF sends an LIR message to the converged HSS / HLR, requesting the name of the S-CSCF currently providing services to the user. The converged HSS / HLR queries the local database and finds that the user is not registered, and returns the capability set that the user has subscribed to. The I-CSCF randomly selects an S-CSCF based on the capability set. The I-CSCF routes the call to the S-CSCF.
[0053] Steps 11-12: The S-CSCF obtains the called party's IFC / SIFC subscription data from the converged HSS / HLR.
[0054] Steps 13-20: S-CSCF triggers the called party's AS (including the called party's SCC AS) in sequence according to the called party's IFC / SIFC. The called party's SCC AS performs called domain selection: it queries whether the user resides in the 2 / 3G network, and the SCC AS sends the INVITE message back to the S-CSCF. The S-CSCF sends the call to the called UE via the circuit domain network through the Media Gateway Control Function (MGCF) + IP Multimedia Gateway (IM-MGW).
[0055] exist Figure 3 Step 8 and Step 12, Figure 4 In steps 8, 11 and 14, after I-CSCF, S-CSCF and AS send LIR, Server-Assignment-Request (SAR) and User-Data-Request (UDR) messages to HSS, if no response message from HSS is received before the response timer expires, they send a disconnect message to the exchange to release the call.
[0056] The following describes in detail the business disaster recovery processing method provided by the embodiment of the present application through specific embodiments and application scenarios in conjunction with the accompanying drawings.
[0057] Figure 5 A service disaster recovery processing method provided by an exemplary embodiment of the present application is shown, which is applied to a user information sharing platform. Figure 5 As shown, the method mainly includes the following steps:
[0058] S501: Receive a query request message sent by a target network element.
[0059] The query request message is sent by the target network element when it is determined that the home subscriber server HSS corresponding to the target network element fails.
[0060] In an embodiment of the present application, the user information sharing platform may receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it is determined that the HSS corresponding to it is faulty.
[0061] In an optional implementation manner, before receiving the query request message sent by the target network element, the method further includes:
[0062] Receiving a data synchronization request sent by a target network element, and determining a type of the data synchronization request, wherein the type of the data synchronization request includes at least one of the following: registration, deregistration, and call;
[0063] In the case where the data synchronization request type is registration, adding the registration information stored by the target network element to the pre-stored data, and updating the registration status corresponding to the target network element to registered;
[0064] In the case where the data synchronization request type is deregistration, deleting the network element information related to the registration information stored in the target network element in the pre-stored data, and updating the registration status corresponding to the target network element to unregistered;
[0065] In the case where the data synchronization request type is a call, the registration information stored in the target network element is updated to the pre-stored data, and the registration status corresponding to the target network element is updated to unregistered. In the above optional implementation, before receiving the query request message sent by the target network element, the user information sharing platform can receive a data synchronization request sent by the target network element, and determine the type of the data synchronization request, and update the pre-stored data of the user information sharing platform according to the type of the data synchronization request. Optionally, the type of the data synchronization request includes at least one of the following: registration, deregistration, call.
[0066] When the type of data synchronization request is registration, the user information sharing platform can add the registration information stored in the target network element to the pre-stored data and update the registration status to registered. Figure 1 In the registration process of the user in the IMS domain, after the S-CSCF receives the Server-Assignment-Answer (SAA) response message from the HSS in step 17, it will synchronize the user registration information to the user information sharing platform. After receiving the data synchronization request sent by the S-CSCF, the user information sharing platform can add the registration information stored by the S-CSCF to the pre-stored data and update the registration status to registered, wherein the registration information stored by the S-CSCF includes the IMS Private Identity (IMPI), the IMS Public Identity (IMPU), the HSS host name, the registered PSBC, the registered S-CSCF, the registered AS, the capability set and the initial filter criterion (IFC) / shared IFC sets (SIFC). In the related art, IMPI is the private identity of the IMS user, which is used to identify the UE and corresponds to the UE one by one; IMPU is the public identity of the IMS user, which is a symbol used to identify each other's communication, equivalent to a telephone number. In the IMS domain, control and services are separated. The S-CSCF controls the call session. The service logic is implemented by the AS. The basic configuration information of the user is stored in the HSS, which includes the user's initial filtering criteria (IFC), which is mainly composed of the AS name and the corresponding triggering conditions. The S-CSCF triggers the service in the AS through the IFC. During the IMS user registration process, the IFC is downloaded from the HSS to the S-CSCF. During the IMS user registration and session process, if the triggering conditions of the IFC in the S-CSCF are met, the S-CSCF will trigger the service to the corresponding AS. According to the operator configuration, the S-CSCF can also perform a translation of the shared IFC set into a set of initial filtering criteria.
[0067] When the data synchronization request type is deregistration, the user information sharing platform may delete the network element information related to the registration information stored in the target network element in the pre-stored data and update the registration status to unregistered; Figure 2 In the schematic diagram of the deregistration process of the user in the IMS domain, in step 6 of the deregistration process, when the S-CSCF receives the SAA response message from the HSS, the user status information can be synchronized to the user information platform.
[0068] After receiving the deregistration request sent by the S-CSCF, the user information sharing platform can delete the network element information (registered PSBC, registered S-CSCF, registered AS) related to the registration information stored in the S-CSCF in the pre-stored data and update the user's registration status to unregistered.
[0069] In the case where the data synchronization request type is a call, the user information sharing platform can update the registration information stored in the target network element to the pre-stored data. It should be noted that when the call indicates that the called user is not registered for the service, that is, when the user information sharing platform receives the data synchronization request type of a call, the user associated with the target network element is not registered in the IMS domain. The target network elements related to the call are I-CSCF and S-CSCF.
[0070] exist Figure 4 After the user shown activates the IMS service, in the unregistered calling and called process in the IMS domain, in step 9, after the I-CSCF receives the Location Information Answer (LIA) message returned by the HSS, it can extract the capability set information in the LIA message and synchronize the capability set information to the user information sharing platform. When the user information sharing platform receives the data synchronization request sent by the I-CSCF, it can update the registration information stored in the I-CSCF to the pre-stored data. The registration information stored in the I-CSCF includes IMPI, IMPU, HSS host name, and capability set. The user information sharing platform can also add the user's registration status to unregistered.
[0071] exist Figure 4 In step 12, after receiving the SAA message returned by the HSS, the S-CSCF can extract the IFC / SIFC information in the SAA message and synchronize the IFC / SIFC information to the user information sharing platform. After receiving the data synchronization request sent by the S-CSCF, the user information sharing platform can update the registration information stored in the S-CSCF to the pre-stored data, IMPI, IMPU, HSS host name, IFC / SIFC. The user information sharing platform can also increase the user's registration status to unregistered.
[0072] In summary, after receiving a data synchronization request, the user information sharing platform first determines the type of data synchronization request. The defined request types are divided into three types: registration, deregistration, and call. Registration means that after the user completes the initial registration, the S-CSCF synchronizes data with the user information sharing platform; deregistration means that after the user deregisters from the IMS network, the S-CSCF synchronizes data with the user information sharing platform. Calling means that when the user is called and the service is unregistered, the I-CSCF and S-CSCF synchronize data with the user information sharing platform. The user information sharing platform can add or update existing records according to the type of data synchronization request. See the table below for details.
[0073] Table 1 User information sharing platform record field update process
[0074]
[0075] S502: Determine, according to the request type of the query request message, user registration information corresponding to the request type in pre-stored data.
[0076] In the embodiment of the present application, the user information sharing platform can determine the user registration information corresponding to the request type in the pre-stored data according to the request type of the query request message sent by the target network element.
[0077] In an optional implementation manner, the target network element includes at least one of the following: an inquiry call session control entity I-CSCF, a serving call session control entity S-CSCF, and an application server AS.
[0078] In an optional implementation, the determining of the user registration information corresponding to the request type in the pre-stored data according to the request type of the query request message includes: determining the user capability set information corresponding to the LIR message in the pre-stored data according to the location information request LIR message sent by the I-CSCF. In an embodiment of the present application, the user information sharing platform can query the local database (pre-stored data) according to the LIR query request message sent by the I-CSCF to check whether there is a record corresponding to the called side user related to the I-CSCF (with registration related information or call related information). If it does not exist, return failure. If it does exist, perform the following processing in sequence: If there is an HSS host name and registered S-CSCF information, return the HSS host name and S-CSCF information (the called side user is registered). If the S-CSCF information does not exist, but the HSS host name and capability set exist (the called side user is not registered but has called), return the HSS host name and capability set. If both the S-CSCF information and the capability set do not exist, return failure. In an embodiment of the present application, the capability set information includes the HSS host name and S-CSCF information, or the capability set information includes the HSS host name and capability set, which helps the I-CSCF determine the S-CSCF required for service transmission.
[0079] And / or, according to the server assignment request SAR message sent by the S-CSCF, determine the user contract information corresponding to the SAR message in the pre-stored data. The user information sharing platform can query the local database based on the SAR information sent by the S-CSCF to see whether there is a record corresponding to the called side user related to the S-CSCF. If there is no record corresponding to the user, or there is a record but the contract field corresponding to the record is empty, failure is returned. If there is a record and the contract information is not empty, the IFC / SIFC contract information is returned.
[0080] And / or, according to the user data request UDR message sent by the AS, determine the server information corresponding to the UDR message in the pre-stored data. The user information sharing platform can query the local database according to the UDR message sent by the AS to check whether there is a record corresponding to the called user related to the AS. If the record exists and the HSS information is not empty, the HSS information is returned. If the record does not exist, or the record exists but the HSS information is empty, a failure is returned.
[0081] S503: Send the user registration information to the target network element, so that the target network element performs service transmission according to the user registration information.
[0082] In an embodiment of the present application, the user information sharing platform may send the user registration information to the target network element, so that the target network element performs service transmission according to the user registration information.
[0083] Optionally, when the target network element is an I-CSCF, the user information sharing platform sends a LIA message to the I-CSCF, wherein the LIA message includes the HSS host name and registered S-CSCF information or the LIA information includes the HSS host name and a capability set; when the target network element is an S-CSCF, the user information sharing platform sends an SAA message to the S-CSCF, wherein the SAA information includes IFC / SIFC signing information; when the target network element is an AS, the user information sharing platform sends a UDA message to the AS, wherein the UDA information includes HSS information.
[0084] In an embodiment of the present application, the user information sharing platform can receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it determines that the HSS corresponding to it is faulty, and then determines the user registration information corresponding to the request type in the pre-stored data according to the request type of the query request message; finally, the user registration information is sent to the target network element so that the target network element transmits services according to the user registration information. In the event that the HSS corresponding to the target network element fails, the user information sharing platform sends the user registration information corresponding to the target network element to the target network element so that the target network element transmits services according to the user registration information, thereby ensuring that the service transmission process is not affected and improving the reliability of the IMS network.
[0085] Figure 6 Another service disaster recovery processing method provided by an exemplary embodiment of the present application is shown, which is applied to a network element. Figure 6 As shown, the method mainly includes the following steps:
[0086] S601: Send a query request message to the user information sharing platform when it is determined that the corresponding HSS is faulty.
[0087] In an embodiment of the present application, the network element may send a query request message to the user information sharing platform when determining that the HSS corresponding to it is faulty.
[0088] Optionally, different network elements send different query request messages to the user information sharing platform. The I-CSCF can send an LIR message to the user information sharing platform to obtain the HSS host name and registered S-CSCF information or LIA information including the HSS host name and capability set; the S-CSCF can send a SAR message to the user information sharing platform to obtain IFC / SIFC signing information; the AS can send an UDR message to the user information sharing platform to obtain HSS information.
[0089] In an optional implementation manner, the determining a corresponding home subscriber server HSS failure includes:
[0090] Send a query request message to the corresponding HSS;
[0091] If the user registration information returned by the HSS is not received within a predetermined time, determining that the HSS is faulty;
[0092] and / or,
[0093] The HSS is queried in a pre-acquired local HSS fault list, and when it is determined that the HSS is stored in the local HSS fault list, the HSS fault is determined.
[0094] In the above optional implementation, the network element can send a query request message to the corresponding HSS, that is, the I-CSCF, S-CSCF and AS can send LIR, SAR and UDR messages to the HSS. If the response message of the HSS is not received before the response timer times out, the HSS fault can be determined; the network element can also query the HSS in the pre-acquired local HSS fault list. If the HSS is stored in the local HSS fault list, the HSS fault can also be determined. In an embodiment of the present application, after the I-CSCF, S-CSCF and AS send LIR, SAR and UDR messages to the HSS, if the response message of the HSS is not received before the response timer times out, a periodic selection (OPTION) detection for the HSS can be initiated. If it is determined that the other party is unreachable, the HSS is considered to be faulty and the HSS is added to the local HSS fault list. After the HSS is added to the local HSS fault list, if it is subsequently detected that the HSS is reachable, the HSS is deleted from the local HSS fault list and the OPTION detection for the HSS is stopped. CSCF, S-CSCF and AS can query the HSS in the local HSS fault list.
[0095] In an optional implementation, the network element sends a data synchronization request to the user information sharing platform so that the network element synchronizes the stored registration information to the user information sharing platform. There are three types of data synchronization requests: registration, deregistration, and call.
[0096] exist Figure 1 In the initial registration process shown, after the initial registration process is completed, the PSBC, S-CSCF and AS can respectively save the user's registration information. Figure 1 After the S-CSCF receives the SAA response message from the HSS in step 17 and the AS receives the SNA response message from the HSS in step 20, the S-CSCF and AS record the HSS host name corresponding to the user when saving the user information. At the same time, the S-CSCF synchronizes the relevant information of the user to the user information sharing platform (sends a data synchronization request of type registration to the user information sharing platform). The requesting network element is the S-CSCF, the request type is registration, and the synchronization fields include IMPI, IMPU, HSS host name, registered PSBC, registered S-CSCF, registered AS, capability set, and IFC / SIFC.
[0097] Figure 2 In the sixth step of the deregistration process of the user in the IMS domain shown in the figure, after the S-CSCF receives the SAA response message from the HSS, the S-CSCF can set the user's registration status in the HSS to "unregistered", and the S-CSCF also synchronizes the user status information to the user information platform (sends a data synchronization request of type deregistration to the user information sharing platform). The requesting network element is the S-CSCF, the request type is deregistration, and it carries the user's IMPI and IMPU information.
[0098] exist Figure 4 Step 9: After receiving the LIA message returned by HSS, I-CSCF extracts the capability set information in the LIA message and synchronizes the capability set information to the user information platform (sends a data synchronization request of type call to the user information sharing platform). The requesting network element is I-CSCF, the request type is call, and it carries information such as user IMPI, IMPU, HSS and capability set. Figure 5 Step 12. After receiving the SAR message returned by HSS, S-CSCF extracts the IFC / SIFC information in the SAR message and synchronizes the IFC / SIFC information to the user information platform (sends a data synchronization request of type call to the user information sharing platform: the requesting network element is S-CSCF, the request type is call, and it carries user IMPI, IMPU, HSS and IFC / SIFC information).
[0099] In an optional implementation, the network element receives a refresh registration request sent by the UE when determining that the corresponding HSS is faulty, directly replies that the refresh registration is successful, and retains the user's registration information. After the user completes the initial registration, the UE initiates a refresh registration process at a fixed time interval according to the network's instructions. The refresh registration process is as follows: Figure 7In the embodiment of the present application, after the I-CSCF detects the HSS failure, the proxy reply function for the refresh registration request can be started, that is, after the I-CSCF receives the refresh registration request forwarded by the PSBC, it directly replies that the refresh registration is successful, omitting Figure 7 Steps 3-14 of the refresh registration process. In the improved refresh registration process, PSBC is not aware of HSS failure, so the user registration information on PSBC always exists. When I-CSCF detects that HSS is restored, it disables the proxy reply function for refresh registration request.
[0100] For registered users on the S-CSCF, when the refresh registration timer times out and no refresh registration request initiated by the terminal is received, if the HSS in the user registration information is in the local HSS fault list, the user's registration information will be retained; if the HSS in the user registration information is not in the local HSS fault list, the current process will be followed and the S-CSCF will delete the locally stored user registration information.
[0101] For registered users on the AS, when the refresh registration timer times out and no refresh registration request initiated by the terminal is received, if the HSS in the user registration information is in the local HSS fault list, the user's registration information is retained; if the HSS in the user registration information is not in the local HSS fault list, the current process is followed and the AS deletes the locally stored user registration information.
[0102] S602: Receive the user registration information returned by the user information sharing platform.
[0103] The user registration information is determined by the user information sharing platform according to the request type of the query request message.
[0104] In an embodiment of the present application, the network element may receive user registration information returned by the user information sharing platform.
[0105] Optionally, the I-CSCF receives a LIA message sent by the user information sharing platform, wherein the LIA message includes the HSS host name and registered S-CSCF information or the LIA information includes the HSS host name and capability set; the S-CSCF receives a SAA message sent by the user information sharing platform to the S-CSCF, wherein the SAA information includes IFC / SIFC signing information; the AS receives a User Data Answer (UDA) message sent by the user information sharing platform to the AS, wherein the UDA information includes HSS information.
[0106] S603: Perform service transmission according to the user registration information.
[0107] In an embodiment of the present application, the network element can transmit services according to user registration information.
[0108] Optionally, after the I-CSCF obtains the capability set information corresponding to the called party, it can send an INVITE message to the S-CSCF registered by the user or select an S-CSCF in the received capability set and send the INVITE message to the S-CSCF. After the S-CSCF obtains the IFC / SIFC contract data, it can trigger the AS in sequence according to the IFC / SIFC. The AS can query the local HSS fault list based on the HSS information in the returned UDA message. If there are records in the local HSS fault list, the default domain is selected in the CS domain, and an INVITE message is constructed to reply to the S-CSCF. If there are no records in the local HSS fault list, it is processed according to the existing process.
[0109] Optionally, if the AS selects the CS domain as the default domain, the called number in the INVITE message that the AS replies to the S-CSCF can be "RN+original number". Among them, the routing number (Router Number, RN) is used to represent the operator network. That is, the S-CSCF fails to query ENUMDNS based on "RN+original number", and routes the call to the MGCF / Gateway Mobile Switching Center (GMSC). The MGCF / GMSC deletes RN and continues the subsequent process. The called number in the INVITE message that the AS replies to the S-CSCF can also remain unchanged, and a domain selection identifier (such as "TADS ID:cs") is added to the INVITE message. The S-CSCF network element routes the call to the MGCF / GMSC based on the identifier and then performs subsequent process processing.
[0110] In an embodiment of the present application, a network element can send a query request message to a user information sharing platform when determining that the HSS corresponding to it is faulty, and receive user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message; and finally, the service is transmitted according to the user registration information. In the case of a failure of the HSS corresponding to the network element, the network element can obtain the relevant information required for service transmission through the user information sharing platform, ensuring that the service transmission of the network element is not affected, and improving the reliability of the IMS network.
[0111] In the embodiment of the present application, after both the primary HSS and the disaster recovery HSS fail, the calling process is not affected because the user registration information on the PSBC, S-CSCF and AS exists and the calling process does not involve interaction with the HSS.
[0112] In the called process in the embodiment of the present application, the processing process of each network element is as follows:
[0113] (I) Internal processing flow of I-CSCF on the called side
[0114] When the I-CSCF on the called side receives an INVITE request, it can process it in the following two ways.
[0115] Method 1: The I-CSCF on the called side receives the INVITE request and checks the local fault HSS list. If the list is not empty, it sends a LIR message to the user information sharing platform to obtain the HSS host name and registered S-CSCF information corresponding to the called party. If the obtained HSS host name is in the local HSS fault list, the INVITE message is sent to the S-CSCF registered by the user. If the obtained HSS host name is not in the local HSS fault list or the local fault HSS list is empty, the I-CSCF processes it according to the normal process and sends a LIR message to the HSS.
[0116] Method 2: The I-CSCF on the called side receives the INVITE request and sends a LIR request to the HSS to obtain the S-CSCF information registered by the user according to the existing process. If the LIA message can be replied normally, it means that the HSS is normal and continues to process according to the existing process. If the LIA response is not received after the response timer times out, it is considered that the HSS is faulty, and a LIR message is sent to the user information sharing platform to obtain the HSS host name and registered S-CSCF information corresponding to the called party, and the INVITE message is sent to the S-CSCF registered by the user.
[0117] (II) Internal Processing Flow of the S-CSCF on the Called Side
[0118] The called S-CSCF receives the INVITE request, queries the local database to obtain user information, and performs different logical processing according to the post-registration status and whether the HSS to which it belongs is faulty.
[0119] (1) If the user has registered, follow the existing process to proceed. That is, trigger the AS in sequence according to the IFC / SIFC saved when the user registered.
[0120] (2) If the user is not registered, the S-CSCF can handle it in two ways.
[0121] Method 1: If the user is not registered, S-CSCF sends a SAR message to the user information sharing platform to obtain the IFC / SIFC contract data. After the user information platform returns the SAA message, it queries whether the HSS in the SAA is in the local HSS fault list. If not, it sends a SAR message to the HSS according to the normal process. If the HSS is in the local HSS fault list, the AS is triggered in sequence according to the returned IFC / SIFC.
[0122] Method 2: If the user is not registered, S-CSCF sends a SAR message to HSS according to the existing process to obtain IFC / SIFC subscription data. If it can reply to the SAA message normally, it means that HSS is normal and continues to process according to the existing process. If the SAA response is not received after the response timer times out, it is considered that HSS is faulty. S-CSCF sends a SAR message to the user information sharing platform to obtain IFC / SIFC subscription data. S-CSCF triggers AS in sequence according to the IFC / SIFC in the returned SAA message.
[0123] (III) Internal processing flow of the called side AS
[0124] The called AS receives the INVITE request, queries the local database to obtain user information, and performs different logical processing according to the user registration status and whether the HSS to which it belongs is faulty.
[0125] (1) If the user has registered and the HSS corresponding to the user registration information is not in the local HSS fault list, or the local HSS fault list is empty, follow the existing process for subsequent processing.
[0126] (2) If the user has registered and the HSS corresponding to the user registration information is in the local HSS fault list, the call for this user will no longer interact with the HSS. The default domain is selected in the IMS domain, and the INVITE message is directly replied to the S-CSCF for subsequent processes.
[0127] (3) If the user is not registered, AS can handle it in the following two ways.
[0128] Method 1: If the user is not registered, the AS sends a UDR query message to the user information sharing platform, and queries the local HSS fault list based on the HSS information in the returned UDA message. If there is a record in the local HSS fault list, the default domain is selected in the CS domain, and an INVITE message is constructed to reply to the S-CSCF. If there is no record in the local HSS fault list, it is processed according to the existing process.
[0129] Method 2: If the user is not registered, the AS sends a UDR message to the HSS according to the existing process. If the AS can reply to the UDA message normally, it means that the HSS is normal and continues to process according to the existing process. If the UDA response is not received after the response timer times out, the HSS is considered to be faulty, the user domain is selected as the CS domain by default, and an INVITE message is constructed to reply to the S-CSCF.
[0130] The business disaster recovery processing method provided in the embodiment of the present application can be executed by a business disaster recovery processing DeviceIn the embodiment of the present application, a service disaster recovery processing device executing a service disaster recovery processing method is taken as an example to illustrate the service disaster recovery processing device provided by the embodiment of the present application.
[0131] Figure 8 A schematic diagram of the structure of a business disaster recovery processing device provided by an exemplary embodiment of the present application is shown. The business disaster recovery processing device can implement the following Figure 5 In the illustrated embodiment, all or part of the contents, the service disaster recovery processing device includes: a first receiving module 801 , a determining module 802 , and a first sending module 803 .
[0132] In an embodiment of the present application, a first receiving module 801 is used to receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it determines that its corresponding home user server HSS has a fault; a determination module 802 is used to determine, according to the request type of the query request message, user registration information corresponding to the request type in the pre-stored data; and a first sending module 803 is used to send the user registration information to the target network element so that the target network element performs service transmission according to the user registration information.
[0133] Optionally, the target network element includes at least one of the following: an inquiry call session control entity I-CSCF, a service call session control entity S-CSCF, an application server AS;
[0134] Optionally, when the determination module 802 is used to determine the user registration information corresponding to the request type in the pre-stored data according to the request type of the query request message, it is specifically used to:
[0135] The determining, according to the request type of the query request message, user registration information corresponding to the request type in pre-stored data includes:
[0136] Determine, according to the location information request LIR message sent by the I-CSCF, the user capability set information corresponding to the LIR message in the pre-stored data;
[0137] and / or,
[0138] Determine, according to the server assignment request SAR message sent by the S-CSCF, user subscription information corresponding to the SAR message in the pre-stored data;
[0139] and / or,
[0140] According to the user data request UDR message sent by the AS, the server information corresponding to the UDR message in the pre-stored data is determined.
[0141] Optionally, the first receiving module 801 is further configured to receive a data synchronization request sent by a target network element, and determine a type of the data synchronization request, wherein the type of the data synchronization request includes at least one of the following: registration, deregistration, and call;
[0142] In the case where the data synchronization request type is registration, adding the registration information stored by the target network element to the pre-stored data, and updating the registration status corresponding to the target network element to registered;
[0143] In the case where the data synchronization request type is deregistration, deleting the network element information related to the registration information stored in the target network element in the pre-stored data, and updating the registration status corresponding to the target network element to unregistered;
[0144] In the case where the data synchronization request type is a call, the registration information stored in the target network element is updated to the pre-stored data, and the registration status corresponding to the target network element is updated to unregistered.
[0145] The service disaster recovery processing device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than the terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a palmtop computer, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobilepersonal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0146] The service disaster recovery processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0147] The service disaster recovery processing device provided in the embodiment of the present application can achieve Figure 5To avoid repetition, the various processes implemented by the method embodiment are not described here.
[0148] Fig. 9 A schematic diagram of the structure of another service disaster recovery processing device provided by an exemplary embodiment of the present application is shown. The service disaster recovery processing device can implement the following Figure 6 In the illustrated embodiment, all or part of the contents, the service disaster recovery processing device includes: a second sending module 901 , a second receiving module 902 and a transmission module 903 .
[0149] In an embodiment of the present application, a second sending module 901 is used to send a query request message to a user information sharing platform when it is determined that the corresponding home user server HSS has a fault. A second receiving module 902 is used to receive the user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message; a transmission module 903 is used to perform service transmission according to the user registration information.
[0150] Optionally, the second sending module 901 is further configured to determine a corresponding home subscriber server HSS failure, specifically configured to:
[0151] Send a query request message to the corresponding HSS;
[0152] If the user registration information returned by the HSS is not received within a predetermined time, determining that the HSS is faulty;
[0153] and / or,
[0154] The HSS is queried in a pre-acquired local HSS fault list, and when it is determined that the HSS is stored in the local HSS fault list, the HSS fault is determined.
[0155] The service disaster recovery processing device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than the terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a palmtop computer, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobilepersonal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0156] The service disaster recovery processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0157] The service disaster recovery processing device provided in the embodiment of the present application can achieve Figure 6 To avoid repetition, the various processes implemented by the method embodiment are not described here.
[0158] Alternatively, if Fig.10 As shown, the embodiment of the present application also provides an electronic device 1000, including a processor 1001 and a memory 1002, the memory 1002 stores a program or instruction that can be run on the processor 1001, and the program or instruction is executed by the processor 1001 to implement the above Figure 5 The business disaster recovery processing method shown or Figure 6 The various steps of the method embodiment of the business disaster recovery processing method shown can achieve the same technical effect. To avoid repetition, they will not be described here.
[0159] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.
[0160] Fig.11FIG. 1 is a block diagram of another electronic device 1100 according to an exemplary embodiment of the present application. The electronic device 1100 may be implemented as a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart watch, a TV, etc. The electronic device 1100 may also be called a user device, a portable terminal, a laptop terminal, a desktop terminal, etc.
[0161] Typically, the electronic device 1100 includes a processor 1101 and a memory 1102 .
[0162] The processor 1101 may include one or more processing cores, such as a 4-core processor, a 10-core processor, etc. The processor 1101 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1101 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1101 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1101 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.
[0163] The memory 1102 may include one or more computer-readable storage media, which may be non-transitory. The memory 1102 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1102 is used to store at least one instruction, which is executed by the processor 1101 to implement the above-mentioned method embodiment shown in the present application. Figure 5 The business disaster recovery processing method shown or Figure 6 All or part of the steps in the business disaster recovery processing method shown.
[0164] In some embodiments, the electronic device 1100 may further optionally include: a peripheral device interface 1103 and at least one peripheral device. The processor 1101, the memory 1102 and the peripheral device interface 1103 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1103 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1104, a display screen 1105, a camera assembly 1106, an audio circuit 1107 and a power supply 1108.
[0165] In some embodiments, the electronic device 1100 further includes one or more sensors 1109 , including but not limited to: an acceleration sensor 1110 , a gyroscope sensor 1111 , a pressure sensor 1112 , an optical sensor 1113 , and a proximity sensor 1114 .
[0166] Those skilled in the art will understand that Fig.11 The structure shown in the figure does not constitute a limitation on the electronic device 1100, and may include more or less components than those shown in the figure, or combine certain components, or adopt a different component arrangement.
[0167] The embodiment of the present application also provides a computer-readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by a processor, the above Figure 5 The business disaster recovery processing method shown or Figure 6 The various processes of the business disaster recovery processing method shown in the figure can achieve the same technical effect. To avoid repetition, they will not be described here.
[0168] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
[0169] The present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 5 The business disaster recovery processing method shown or Figure 6 The various processes of the business disaster recovery processing method shown in the figure can achieve the same technical effect. To avoid repetition, they will not be described here.
[0170] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0171] The present application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the above Figure 5 The business disaster recovery processing method shown or Figure 6 The various processes of the business disaster recovery processing method shown in the figure can achieve the same technical effect. To avoid repetition, they will not be described here.
[0172] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0173] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0174] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A business disaster recovery processing method, applied to a user information sharing platform, characterized in that: include: Receiving a query request message sent by a target network element, wherein the query request message is sent by the target network element when it is determined that a home subscriber server HSS corresponding to the target network element fails; Determining, according to the request type of the query request message, user registration information corresponding to the request type in pre-stored data; The user registration information is sent to the target network element, so that the target network element performs service transmission according to the user registration information.
2. The method according to claim 1, characterized in that: The target network element includes at least one of the following: an inquiry call session control entity I-CSCF, a service call session control entity S-CSCF, and an application server AS; The determining, according to the request type of the query request message, user registration information corresponding to the request type in pre-stored data includes: Determine, according to the location information request LIR message sent by the I-CSCF, user capability set information corresponding to the LIR message in the pre-stored data; and / or, Determine, according to the server assignment request SAR message sent by the S-CSCF, user subscription information corresponding to the SAR message in the pre-stored data; and / or, According to the user data request UDR message sent by the AS, the server information corresponding to the UDR message in the pre-stored data is determined.
3. The method according to claim 1, characterized in that Before receiving the query request message sent by the target network element, the method further includes: receiving a data synchronization request sent by the target network element, and determining a type of the data synchronization request, wherein the type of the data synchronization request includes at least one of the following: registration, deregistration, and call; In the case where the data synchronization request type is registration, adding the registration information stored by the target network element to the pre-stored data, and updating the registration status corresponding to the target network element to registered; In the case where the data synchronization request type is deregistration, deleting the network element information related to the registration information stored in the target network element in the pre-stored data, and updating the registration status corresponding to the target network element to unregistered; In a case where the data synchronization request type is a call, the registration information stored in the target network element is updated to the pre-stored data, and the registration status corresponding to the target network element is updated to unregistered.
4. A service disaster recovery processing method, applied to a network element, characterized in that: include: Sending a query request message to the user information sharing platform when determining that the corresponding home subscriber server HSS is faulty; Receiving the user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message; Business transmission is performed according to the user registration information.
5. The method according to claim 4, characterized in that The determining of a corresponding home subscriber server HSS failure includes: Send a query request message to the corresponding HSS; If the user registration information returned by the HSS is not received within a predetermined time, determining that the HSS is faulty; and / or, The HSS is queried in a pre-acquired local HSS fault list, and when it is determined that the HSS is stored in the local HSS fault list, the HSS fault is determined.
6. A business disaster recovery processing device, applied to a user information sharing platform, characterized in that: include: A first receiving module, configured to receive a query request message sent by a target network element, wherein the query request message is sent by the target network element when it is determined that a home subscriber server HSS corresponding to the target network element fails; A determination module, configured to determine user registration information corresponding to the request type in pre-stored data according to the request type of the query request message; The first sending module is used to send the user registration information to the target network element, so that the target network element performs service transmission according to the user registration information.
7. A service disaster recovery processing device, applied to a network element, characterized in that: include: The second sending module is used to send a query request message to the user information sharing platform when it is determined that the corresponding home subscriber server HSS fails. A second receiving module, configured to receive the user registration information returned by the user information sharing platform, wherein the user registration information is determined by the user information sharing platform according to the request type of the query request message; The transmission module is used to perform service transmission according to the user registration information.
8. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the business disaster recovery processing method as described in any one of claims 1 to 3 or the business disaster recovery processing method as described in any one of claims 4 to 5 are implemented.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the business disaster recovery processing method as described in any one of claims 1 to 3 or the business disaster recovery processing method as described in any one of claims 4 to 5 are implemented.
10. A computer program product, characterized in that The computer program product stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the business disaster recovery processing method as described in any one of claims 1 to 3 or the business disaster recovery processing method as described in any one of claims 4 to 5 are implemented.
Citation Information
Patent Citations
Method and device for realizing Internet protocol multi-media sub-system disaster tolerance
CN101170553A
Information query method and device, medium and equipment
CN117675767A
HSS (home subscriber server) full-resistance IMS (IP multimedia subsystem) domain disaster recovery method, device and equipment and storage medium
CN117675768A
Data processing method and device
CN117812619A
A method and apparatus for operation and management, a method and server for determining service operation validity
WO2007121672A1
