CN114928832A

CN114928832A - Fault service processing method and device, electronic equipment and computer readable medium

Info

Publication number: CN114928832A
Application number: CN202210528700.2A
Authority: CN
Inventors: 孟涛; 种琳; 熊靓
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-05-16
Filing date: 2022-05-16
Publication date: 2022-08-19
Anticipated expiration: 2042-05-16
Also published as: CN114928832B

Abstract

The application provides a fault service processing method, a fault service processing device, electronic equipment and a computer readable medium, wherein the method comprises the following steps: an interconnection link is added between a first home subscriber server HSS1 and a second home subscriber server HSS2, wherein the first home subscriber server corresponds to a first unified data management network element UDM1 and is used for migrating first subscriber data stored in the first home subscriber server to the UDM1 during service upgrade to obtain UDM1 subscriber data, and the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating the first subscriber data stored in the second home subscriber server to the UDM2 during service upgrade to obtain UDM2 subscriber data; if the UDM1 user data is obtained, synchronizing the UDM1 user data to the HSS 2; and if the UDM1 fails, routing the first service of the HSS1 to the HSS2 based on the interconnection link, and processing the first service in the HSS2 based on the UDM1 user data. The method and the device can solve the problems of long time, low efficiency and the like of reestablishing the HSS user data when the UDM fails, and realize the quick recovery of the failure service.

Description

Fault business processing method and device, electronic equipment and computer readable medium

Technical Field

The present application relates to communications technologies, and in particular, to a method and an apparatus for processing a fault service, an electronic device, and a computer-readable medium.

Background

In the initial stage of 5G (5th Generation Mobile Communication Technology, 5G) operation, the total operation risk of the 5G Core network (5G Core, 5GC) is relatively high, especially for Unified Data Management (UDM) network elements carrying a large amount of user Data, and once the UDM fails, the range and degree of the affected service are very large.

In the existing UDM escape scheme, after the UDM fault is determined to enable escape, user data is exported by using a backup Server of the UDM user data, the user data to be restored is compiled into an instruction script for creating the user data according to a user data instruction of a Home location register (HSS), and then the instruction script is executed on the HSS to realize the restoration of a user basic service in the HSS.

Therefore, how to quickly rollback UDM user data to HSS user data when UDM fails is an urgent problem to be solved at present.

Disclosure of Invention

The application provides a fault service processing method, a fault service processing device, electronic equipment and a computer readable storage medium, which are used for solving the technical problems of long time, low efficiency and the like for recreating HSS user data when the existing UDM fails.

In a first aspect, the present application provides a method for processing a fault service, including:

an interconnection link is added between a first home subscriber server HSS1 and a second home subscriber server HSS2, the first home subscriber server corresponds to a first unified data management network element UDM1 and is used for migrating first subscriber data stored in the first home subscriber server to UDM1 during service upgrade to obtain UDM1 subscriber data, and the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating the first subscriber data stored in the second home subscriber server to UDM2 during user service upgrade to obtain UDM2 subscriber data;

if the UDM1 user data is obtained, synchronizing the UDM1 user data to the HSS 2;

if the UDM1 fails, routing a first service of the HSS1 to the HSS2 based on the interlink, and processing the first service in the HSS2 based on the UDM1 user data.

In one embodiment, after adding the interconnect link between the first home subscriber server HSS1 and the second home subscriber server HSS2, the method further comprises:

if the UDM2 user data is obtained, synchronizing the UDM2 user data to the HSS 1; and if the UDM2 fails, routing a second service of the HSS2 to the HSS1 based on the interconnection link, and processing the second service in the HSS1 based on the UDM2 user data.

In one embodiment, the interconnect link is a Diameter protocol based link.

and presetting the routing priority of the interconnection link, wherein the routing priority is lower than the routing priority among the front end FEs of the HSS1 in the HSS1, the data routing priority between the HSS1 and the corresponding UDM1, the routing priority among the front end FEs of the HSS2 in the HSS2 and the data routing priority between the HSS2 and the corresponding UDM 2.

In one embodiment, after synchronizing the UDM1 user data to HSS2 and before routing the first traffic of HSS1 to HSS2 based on the interconnect link, further comprising:

preprocessing UDM1 user data in HSS 2;

processing, in the HSS2, the first service based on the UDM1 user data, including: processing said first service based on pre-processed UDM1 user data in HSS 2.

In one embodiment, after synchronizing the UDM2 user data to the HSS1 and before routing the second traffic of the HSS2 to the HSS1 based on the interconnect link, further comprising:

pre-processing UDM2 user data in HSS 1;

processing, in HSS1, the second service based on the UDM2 user data, including: processing said second service in the HSS1 based on the pre-processed UDM2 user data.

In one embodiment, the UDM1 user data includes a first international mobile subscriber identity IMSI1 and first key KI1 information, and after obtaining the UDM1 user data, the method further includes:

establishing an IMSI1 list based on the obtained UDM1 user data;

the preprocessing of UDM1 user data in HSS2, including:

comparing the change condition of the IMSI1 list in the HSS2 according to a preset period, and generating an IMSI1 list needing to be deleted and/or an IMSI1 list needing to be created based on a comparison result;

generating a user deletion script and/or a user creation script based on the IMSI list needing to be deleted and/or the IMSI1 list needing to be created and the corresponding KI1 information;

and executing the user deleting script and/or the user creating script to obtain the preprocessed UDM1 user data.

In one embodiment, the UDM2 user data includes a second international mobile subscriber identity IMSI2 and a second key KI2, and after obtaining the UDM1 user data, the method further includes:

establishing an IMSI2 list based on the obtained UDM2 user data;

the preprocessing of UDM2 user data in HSS2, comprising:

comparing the change condition of the IMSI2 list in the HSS2 according to a preset period, and generating an IMSI2 list needing to be deleted and/or an IMSI2 list needing to be created based on a comparison result;

generating a user deletion script and/or a user creation script based on the IMS2 list to be deleted and/or the IMSI2 list to be created and corresponding KI2 information;

and executing the user deleting script and/or the user creating script to obtain the preprocessed UDM2 user data.

In one embodiment, said synchronizing said UDM1 user data to HSS2 comprises:

uploading UDM1 user data to a cloud platform; and synchronizing UDM1 user data to HSS2 based on the cloud platform.

In one embodiment, said synchronizing said UDM2 user data to HSS1 comprises:

uploading UDM2 user data to a cloud platform; and synchronizing UDM2 user data to HSS1 based on the cloud platform.

In a second aspect, the present application provides a device for processing a failure service, including:

an interconnection module, configured to add an interconnection link between a first home subscriber server HSS1 and a second home subscriber server HSS2, where the first home subscriber server corresponds to a first unified data management network element UDM1, and is configured to migrate first subscriber data stored in the first home subscriber server to the UDM1 to obtain UDM1 subscriber data when a service is upgraded, and the second home subscriber server corresponds to a second unified data management network UDM2, and is configured to migrate the first subscriber data stored in the second home subscriber server to the UDM2 to obtain UDM2 subscriber data when the service is upgraded,

a first synchronization module configured to synchronize UDM1 user data to HSS2 upon obtaining UDM1 user data;

a first failure handling module arranged to route first traffic of the HSS1 to the HSS2 based on the interlink and to handle the first traffic in the HSS2 based on the UDM1 user data, when the UDM1 fails.

In a third aspect, the present application provides an electronic device, comprising: a processor and a memory;

the memory stores computer execution instructions;

the processor executes the computer execution instructions stored in the memory, so that the electronic equipment executes the fault service processing method.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, are used to implement the fault service method.

According to the fault service processing method, device, electronic device and computer readable storage medium provided by the application, by adding an interconnect link between a first home subscriber server HSS1, corresponding to a first uniform data management network element UDM1, the second home subscriber server is used for migrating the first user data stored in the service upgrade to the UDM1 to obtain UDM1 user data, the second home subscriber server corresponds to a second unified data management network UDM2, for migrating the first user data stored in the user service upgrading to the UDM2 to obtain the UDM2 user data, upon obtaining UDM1 user data, synchronizing said UDM1 user data to HSS2, and when the UDM1 fails, routing a first service of the HSS1 to the HSS2 based on the interconnection link, and processing the first service in the HSS2 based on the UDM1 user data. According to the method, through the mode of carrying out cross backup on the UDM1 user data between the HSS1 and the HSS2, when the UDM1 fails, the HSS2 which backs up the UDM1 user data is used for quickly calling the corresponding UDMI user data recovery service, so that the problems of long time, low efficiency and the like of reestablishing the HSS user data when the UDM fails are solved, and the quick recovery of the failure service is realized.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic view illustrating a related art escape scenario;

FIG. 2 is a diagram of one possible network architecture according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a user data synchronization method according to an embodiment of the present application;

fig. 4 is a schematic flowchart of another user data synchronization method according to an embodiment of the present application;

fig. 5 is a schematic flowchart of another user data synchronization method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a user data synchronization apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a user data synchronization system according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

In order to facilitate clear description of the technical solutions of the embodiments of the present application, some terms and techniques referred to in the embodiments of the present application are briefly described below:

5G SA (5G Standalone): the 5G independent networking is a type of 5G networking, and in the SA independent networking mode, a user (5G terminal) accesses a 5G base station and a 5G core network, so that the advantageous characteristics of 5G, such as ultra-low delay and the like, can be better exerted.

5 GC: the 5G core network is the core of the 5G mobile network and establishes a reliable, secure network connection for the end user and provides access to its services. The core domain handles various basic functions in the mobile network, such as connectivity and mobility management, authentication and authorization, user data management and policy management, etc. The 5G core network functions are completely software based and designed to be cloud-native, which means that they are independent of the underlying cloud infrastructure, enabling greater deployment agility and flexibility.

HSS: the Home subscriber server is a server for storing subscriber subscription information, is evolution and upgrade of a Home Location Register (HLR) of a 2G/3G network element, and is mainly responsible for managing subscriber subscription data and Location information of a mobile subscriber. The HSS is used in the 4G network and stores the user subscription data and 4G location information related to the user 4G.

The HSS supports a primary user database of an IP Multimedia Subsystem (IMS) network entity for handling calls/sessions, which contains user profiles, performs authentication and authorization of users, and may provide information about the physical location of users, similar to the gsm Multimedia location register. Entities in communication with the HSS are an Application Server (AS) that hosts and executes services in the IMS environment, and a Call Session Control Function (CSCF). The subscriber profile contains information about the current subscriber-typically a service-Call Session Control Function (S-CSCF) will download and use this file when the subscriber registers with the network.

The HSS comprises a Front End (FE) and a Back End (BE), wherein the Front End realizes the separation of user data and service logic processing; the backend, i.e., the USCDB (Unified Subscriber Center DataBase), is responsible for storing user data, providing services for adding, deleting, updating, and querying user data, and providing effective data support for the FE. The FE is responsible for signaling access and service logic processing, and obtains data services from the BE.

UDM, unified data management network element, used for 3GPP AKA authentication, user identification, access authorization, registration, mobile, subscription, short message management, etc. Applied to 5G networks, which are similar to the HSS for 4G.

Network Functions virtualization (nfv), which is a concept of network architecture, uses virtualization technology to divide a network node level function into several functional blocks, which are implemented in a software manner, respectively, and are not limited to a hardware architecture.

VNF (virtual Network feature): the virtualized network function, including a VNF network function and an EMS unit management system, configures and manages functions of the VNF. Generally, EMS and VNF are in one-to-one correspondence, and it can be understood that VNF is a virtual network function unit in NFV architecture. NFV is a technology for virtualizing network functions, and functions of a conventional communication network can be realized by virtualization technology in the IT field, for example. The VNF can be understood as an individual network element that is virtualized.

Dra (diameter Routing agent): the routing agent node and the DRA node are responsible for translation and switching of a Diameter signaling destination address of LTE (Long Term Evolution), and authentication, position updating and charging management of an LTE user are realized.

ONE-NDS (ONE-Network Directory Server): a unified network database, i.e. a database backend, can BE understood as a collection of all BEs.

Map (management Autonom platform): an automatic generation system of a management application platform, also called a management autonomous platform, belongs to one of enterprise management autonomous platforms.

HSTP (high Signal Transfer Point): the high-level signaling transfer point, HSTP, is located at the location of a DC1(Dual Connectivity) switching center, and is generally located in a provincial city of a province, wherein a pair of two devices, which are divided into several levels, generally operate simultaneously, one master and the other for the conversion and processing of traffic between provinces.

SFTP (secure File Transfer protocol): the file transfer protocol is a Secure file transfer protocol and is a Secure Shell (SSH) embedded protocol, that is, SFTP can be used as long as sshd remote connection server is started, no additional installation is required, and its default port is 22 as in SSH. SFTP guarantees security of a transmission file by using an encryption/decryption technique, so the transmission efficiency of SFTP is lower than that of ordinary file transfer protocol FTP, but the security of SFTP is higher than that of FTP, so SFTP is generally used in a scenario with high security requirements, such as a report, a statement, and the like.

Pgw (pdn gateway): the network packet data network gateway provides session management and bearer control, data forwarding, IP address allocation and the like for users.

Imsi (international Mobile Subscriber identity): an international mobile subscriber identity is an identity that does not repeat in all cellular networks, used to distinguish between different users in the cellular networks. The handset sends the IMSI to the network in a 64-bit field. The IMSI may be used to query a subscriber for information in a Home Location Register (HLR) or a Visitor Location Register (VLR). In order to avoid the listener identifying and tracking a particular Subscriber, most communications between the handset and the network use a randomly generated Temporary Mobile Subscriber Identity (TMSI) instead of the IMSI.

MSISDN (Mobile Subscriber International ISDN/PSTN number), ISDN (integrated Service Digital Network), is an integrated services Digital Network, and MSISDN refers to a number that a calling Subscriber needs to dial to call a Mobile Subscriber, and is used as a fixed Network PSTN (Public Switched Telephone Network number) and is a number that can uniquely identify a Mobile Subscriber in a Public Telephone Network switching Network numbering plan.

Ki (key identifier), a secret key, also called a mobile phone authentication key, is a secret key for encrypted data transmission between a SIM (Subscriber Identity Module) card and an operator.

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.

With the continuous development of the fifth generation communication technology, the 5G SA service is rapidly developed, the 5GC is used in large-scale business, the 4G user upgrades the 5G service in large scale, and the user data is also migrated from the home location register HSS of the 4G to the unified data management network element UDM of the 5G.

In the initial application process of new technologies such as the NFV architecture of the 5G core network, there are many unknown defects and risks in the planning, design and deployment of the hardware server, the virtualization layer, the VNF and other hierarchies, and in addition, the failure risk is also relatively prominent due to the relatively centralized DC architecture in the deployment region, so at the present stage, the overall operation risk of the 5G core network is relatively large, and in particular, once a fault occurs in the UDM network element that carries a large amount of user data, the range and degree of the affected service are very large.

In the related art, each operator formulates an escape scheme aiming at a UDM fault situation, and after the UDM fault is determined, UDM user data is re-created in an HSS, so that the time consumed for escaping is too long, and a user service cannot be recovered in a short time. Taking a UDM failure occurring in a certain operator in the country in the near future as an example, 2.7 ten thousand important user data are locally returned to the HSS after 2 hours.

Taking the network architecture in the Hunan area as an example, two HSS exist in the Hunan existing network, namely HSS20 and HSS21, and two UDMs, namely UDM800 and UDM 801; wherein, HSS20 corresponds to UDM800, and covers Changsha (15X/185), Yiyang, Chenzhou, Hengyang, Hunan Tan, and Yongzhou city number; HSS21 corresponds to UDM801, and covers Changsha 15X/185, Changzhou, Shaoyang, Yueyang, changde, Huaishi, Louyou, Zhang Jiajiu, Ji shou city number. After the 5G service is upgraded, the user is moved to the UDM from the corresponding HSS.

Combining the current network service switching situation with the figure 1, routing the user service in the registration section under the UDM800 to the HSSFE20, and after the FE to the BE (ONE-NDS) queries that the user does not exist, sending the service Retry to the UDM 800; a registered user service under the UDM801 is routed to HSSFE21, and after an FE (user equipment-object name) to BE (on-NDS) inquires that a user does not exist, the service Retry is sent to the UDM 801; the Diameter service is switched through a direct connection interface of the HSS FE and the UDM FE; the MAP traffic is forwarded via HSTP.

As shown in fig. 1, in the existing network original escape scheme, the UDM800 uploads user information to the huizhou cloud every day, and the ONE-NDS20 INS downloads user data from the huizhou cloud and generates a current-day escape script; the UDM801 generates escape scripts every day and uploads the escape scripts to the Huizhou cloud, and the ONE-NDS21 INS downloads the escape scripts from the Huizhou cloud and stores the escape scripts; after the escape is started, the ONE-NDS INS sends the escape script SFTP to the PGW of the ONE-NDS, the PGW starts to create the UDM user in the ONE-NDS, in the process, the HSS FE can inquire the UDM user data from the ONE-NDS, and the service is not switched to the UDM any more.

In view of this, the embodiment of the present application adopts a cross backup manner of UDMs and HSS on user data, that is, multiple sets of UDM user data are cross backed up to multiple sets of HSS, so that the HSS stores user data of other UDMs when the UDMs do not fail, and does not need to temporarily create users during emergency escape, but passes through a cross backup mechanism of the UDMs and the HSS, and for the cross backup mechanism of the embodiment of the present application, in a normal case where the UDMs do not fail, because the HSS does not store corresponding UDM user data but stores user data of other UDMs, after a DRA is routed to a corresponding set of HSS, the set of HSS does not contain corresponding UDM user data, and is still forwarded to the UDMs for connection, so that 5G user connection is not affected, and in an emergency case where a failure occurs, a call can access the backup user data in the HSS by a simple routing parameter modification, the escape time is greatly shortened, and the service of the user 2/3/4G can be recovered in only ten minutes and a few minutes.

The technical solution of the present application is explained in detail below. Embodiments of the present application may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a possible network architecture diagram provided in an embodiment of the present application, where the embodiment is exemplified by fig. 2 and includes an HSS20 server, an HSS21 server, a UDM800 network element, a UDM801 network element, and a cloud platform, and the embodiment is exemplified by a heyowa cloud, where the HSS20 server includes an HSS20 front end — an HSS FE20 and an HSS20 back end — ONE-NDS20, and the HSS21 server includes an HSS21 front end — an HSS FE21 and an HSS21 back end — ONE-NDS 21; different from the prior art, in the network architecture of the embodiment of the present application, an interconnected data transmission link is established between the HSS20 and the HSS21, so that data synchronization can BE performed between the HSS FE20 and the HSS FE21 through the data transmission link, and in terms of user data, an HSS20 BE (i.e., ONE-NDS20) is used to store the UDM801, and an HSS21 BE (i.e., ONE-NDS21) is used to store the cross-backup mode of the UDM 800. User data is created in the BE in advance and can BE updated daily according to the user information of the UDM, that is, the ONE-NDS20 stores the HSS20 user and UDM801 user data, and the ONE-NDS21 stores the HSS21 user and UDM800 user data.

The scenario diagram of the present application is briefly described above, and the method provided by the embodiment of the present application is described in detail below by taking the HSS20 or HSS21 applied in fig. 2 as an example.

Referring to fig. 3, fig. 3 is a flowchart illustrating a user data synchronization method according to an embodiment of the present application, where the method includes steps S301 to S304.

Step S301, an interconnection link is added between a first home subscriber server HSS1 and a second home subscriber server HSS2, where the first home subscriber server corresponds to a first unified data management network element UDM1, and is configured to migrate first subscriber data stored in the first home subscriber server to the UDM1 to obtain UDM1 subscriber data when a service is upgraded, and the second home subscriber server corresponds to a second unified data management network UDM2, and is configured to migrate the first subscriber data stored in the second home subscriber server to the UDM2 to obtain UDM2 subscriber data when the service is upgraded.

In this embodiment, an interconnection link, that is, an interconnection between the front-end interfaces of the HSS1 and the HSS2 can be implemented, and when a fault occurs, a service can be forwarded from the interface to the interconnection link, for example, when the UDM800 fails, the service is forwarded from the HSS20 front end to the HSS21 front end, and vice versa.

In a specific implementation, the interconnection link added between HSS1 and HSS2 is a Diameter protocol based link.

The Diameter protocol is used as The AAA protocol standard of The next generation by AAA working group of IETF (The Internet Engineering Task Force). The Diameter Protocol includes a basic Protocol, an NAS (Network access service) Protocol, an Extensible Authentication Protocol (EAP), a Mobile IP (Mobile IP) Protocol, a CMS (Cryptographic Message syntax) Protocol, and the like. The Diameter protocol supports Authentication, authorization and accounting work of mobile IP, NAS request and mobile agent, and the realization of the protocol is similar to RADIUS (Remote Authentication Dial In User Service) and also adopts AVP protocol.

By adding Diameter protocol-based interconnection transmission between the HSS1 and the HSS2, the embodiment can realize efficient service switching between the HSS1 and the HSS 2.

In one embodiment, in order to reduce the influence of the interconnection link on the HSS1 and the HSS2 under normal conditions to guarantee the normal processing flow of the service under normal conditions, the method further includes the following steps after adding the interconnection link between the first home subscriber server HSS1 and the second home subscriber server HSS 2:

the routing priority of the interconnection link is preset, and is lower than the routing priority between the front-end FEs of the HSS1 in the HSS1, the data routing priority between the HSS1 and the corresponding UDM1, the routing priority between the front-end FEs of the HSS2 in the HSS2, and the data routing priority between the HSS2 and the corresponding UDM 2.

In this embodiment, by setting the routing priority, only when the HSS FE fails to query the user and the UDM FE route is not reachable, the service is routed to another set of HSS FE through the interconnection link, so as to implement service continuity. That is to say, the interconnection link in this embodiment is enabled only when a service failure occurs, and under a normal condition, the HSS FEs may be used to query corresponding user data, or service routing is implemented between the HSS FE and the UDM FE.

Step S302, if the UDM1 user data is obtained, synchronizing the UDM1 user data to the HSS 2.

Illustratively, an HSS20 BE is adopted to store the UDM801, and an HSS21 BE is adopted to store the UDM800 in a cross backup mode. User data is created in the BE in advance and updated daily according to the user information of the UDM. Namely, the ONE-NDS20 stores HSS20 own user and UDM801 user data, and the ONE-NDS21 stores HSS21 own user and UDM800 user data.

Compared with the related art, in the case of UDM1 failure, the UDM1 user data is re-created in the HSS1, and due to the huge data volume, the creation of data consumes a lot of time, and the user service cannot be recovered in a short time. In order to solve the technical problem, according to the present embodiment, by using the original data storage capability of the HSS2, when a user migrates to the UDM1 in the HSS1 and generates UDM1 data, the data of the UDM1 is synchronized into the HSS2, when a UDM1 fails, it is not necessary to create user data in the HSS1 again, the HSS2 has synchronized corresponding UDM user data, and the user data is switched to the HSS2, so that the failed service of the UDM1 is quickly recovered in the HSS2 by using the corresponding UDM1 user data.

In a specific embodiment, the synchronizing data by using a cloud platform to improve the efficiency of data synchronization, where the synchronizing the UDM1 user data to the HSS2 (step S302) includes:

In this embodiment, the cloud platform adopts a hezhou cloud, and the UDM801 BE generates UDM801 user data and/or the UDM800BE generates UDM800 user data, and then the data is uploaded to the hezhou cloud, and then synchronized to the corresponding HSS FE20 and HSS FE21 from the hezhou cloud.

Step S303, if the UDM1 fails, routing a first service of the HSS1 to the HSS2 based on the interconnection link, and processing the first service in the HSS2 based on the UDM1 user data.

In this embodiment, when the UDM fails, the service is quickly switched over based on the interconnection link, and under a normal condition, the service of the lower number segment of the UDM800 is routed to the HSS20 FE first, and because the HSS20 BE does not store the user data of the UDM800, the service is still routed to the UDM800FE normally and then connected; the UDM801 case is similar. The method is the same as the method before optimization, and has no influence on the existing service.

Referring to fig. 4, fig. 4 is a schematic flow diagram of another fault service processing provided in the embodiment of the present application, based on the above embodiment, the present embodiment synchronizes user data of a UDM2 in a same cross backup manner for a UDM corresponding to another set of HSS to implement fast recovery of a fault service of the UDM2, and specifically, after an interconnection link is added between the first home subscriber server HSS1 and the second home subscriber server HSS2 (step S301), the present embodiment further includes the following step S401 and step S402.

Step S401, if the UDM2 user data is obtained, synchronizing the UDM2 user data to the HSS 1;

step S402, if the UDM2 fails, routing a second service of the HSS2 to the HSS1 based on the interconnection link, and processing the second service in the HSS1 based on the UDM2 user data.

It should be noted that the principle of synchronizing the UDM2 user data to the HSS1 and performing service continuity in the HSS1 is the same as the principle of synchronizing the UDM1 user data to the HSS2 and performing service continuity in the HSS2 in the above embodiment, and is not described again here.

In a specific embodiment, the synchronization between data is implemented by using a cloud platform to improve the synchronization efficiency of the data, and the synchronizing the UDM2 user data to the HSS1 (step S401) includes the following steps:

In this embodiment, the cloud platform adopts a huizhou cloud, and the UDM801 BE generates UDM801 user data and/or the UDM800BE generates UDM800 user data, and then the data is uploaded to the huizhou cloud, and then synchronized to the corresponding HSS FE20 and HSS FE21 from the huizhou cloud.

Referring to fig. 5, fig. 5 is a schematic flow diagram of another method for processing a failed service provided in the embodiment of the present application, based on the above embodiment, in this embodiment, in consideration that the UDM user data has a huge amount and may not be directly used in an HSS, so as to facilitate efficient use of the UDM user data in the HSS, after completing synchronization of the UDM data, the embodiment may first pre-process the UDM user data in the corresponding HSS, and when a failed service occurs, the embodiment may directly continue a service based on the pre-processed UDM data, so as to further improve service recovery efficiency, specifically, after synchronizing the UDM1 user data to the HSS2 (step S302), and before routing a first service of the HSS1 to the HSS2 based on the interconnection link (step S303), the method includes the following step S501, and further divides the step S303 into step S303 a.

Step S501, preprocessing UDM1 user data in HSS 2; step S303a, if the UDM1 fails, routing the first service of the HSS1 to the HSS2 based on the interconnection link, and processing the first service in the HSS2 based on the preprocessed UDM1 user data.

Specifically, the UDM1 user data includes a first international mobile subscriber identity IMSI1 and a first key KI1, and in some embodiments, further includes information such as an MSISDN, a VLR address, and the like. Since the UDM user data may change every day, in order to ensure that the service is recovered for the latest UDM user data when a failure service occurs, the present embodiment improves the efficiency of preprocessing the UDM user data by establishing an IMSI1 list and deleting and/or creating a user script according to the list, and specifically, the method further includes the following steps: based on the obtained UDM1 user data, a list of IMSIs 1 is established.

The preprocessing of the UDM1 user data in the HSS2 (step S501) specifically includes the following steps a-c:

a. and comparing the change conditions of the IMSI1 list according to a preset period, and generating an IMSI1 list needing to be deleted and/or an IMSI1 list needing to be created based on the comparison result.

b. And generating a user deletion script and/or a user creation script based on the IMSI list to be deleted and/or the IMSI1 list to be created and the corresponding KI1 information.

The preset period can take days as units, illustratively, UDM daily user data including information such as IMSI, MSISDN, KI, VLR addresses and the like are obtained from the huizhou cloud, the UDM user data is processed, a current-day IMSI list and a VLR address import script are generated, the current-day IMSI list and a previous-day IMSI list are compared, and an IMSI list to be deleted and a user IMSI list to be created are generated.

c. And executing the user deleting script and/or the user creating script to obtain the preprocessed UDM1 user data.

Specifically, the user data change script is uploaded to the PGW for execution, an execution result is waited for, and an execution result file is obtained, where the execution result file is preprocessed UDM1 user data, and the preprocessed UDM1 user data can be directly used in the HSS 2.

Further, the same method is adopted for the user data of the UDM2 in this embodiment, so as to improve the efficiency of recovering the failed service of the UDM2, and specifically, after synchronizing the UDM1 user data to the HSS1 (step S401), and before routing the second service of the HSS2 to the HSS1 based on the interconnection link (step S402), the method further includes the following steps:

pre-processing UDM2 user data in HSS 1;

processing, in the HSS1, the second service based on the UDM2 user data, including: processing said second service in the HSS1 based on the pre-processed UDM2 user data.

Further, the UDM2 user data includes a second international mobile subscriber identity IMSI2 and a second key KI2 information, and the method further includes:

establishing an IMSI2 list based on the obtained UDM2 user data;

the preprocessing of the UDM2 user data includes:

comparing the change conditions of the IMSI2 list according to a preset period, and generating an IMSI2 list needing to be deleted and/or an IMSI2 list needing to be created based on a comparison result;

It should be noted that, in this embodiment, the principle of preprocessing the UDM2 user data in the HSS1 is the same as the principle of preprocessing the UDM1 user data in the HSS2, and details are not described here.

In order to verify the effectiveness of the fault service processing method used in this embodiment, time consumption comparison is performed between the fault service processing method and the existing service escape method, and the conclusion is that before optimization, an escape script is stored in ONE-NDS21 every day, when escape is performed, script creation users are operated, the time consumption is about 1 hour per million users, and 2.5 hours are required for calculation by the current UDM801 account opening user; after performing fault service optimization based ON this embodiment, the user updates to ON2-NDS20 (created) every day, modifies the HSS21 front end pointer during escape, and continues the UDM801 user pointer HSS20 front end, which takes only about 15 minutes.

Correspondingly, an embodiment of the present application further provides a device for processing a fault service, where as shown in fig. 6, the device includes:

an interconnection module 61, configured to add an interconnection link between a first home subscriber server HSS1 and a second home subscriber server HSS2, where the first home subscriber server corresponds to a first unified data management network element UDM1, and is configured to migrate first subscriber data stored in the first home subscriber server to the UDM1 to obtain UDM1 subscriber data when a service is upgraded, and the second home subscriber server corresponds to a second unified data management network UDM2, and is configured to migrate the first subscriber data stored in the second home subscriber server to the UDM2 to obtain UDM2 subscriber data when the user service is upgraded,

a first synchronization module 62 arranged to synchronize UDM1 user data to HSS2 when UDM1 user data is obtained;

a first failure handling module 63 arranged to route first traffic of the HSS1 to the HSS2 based on the interlink and to handle the first traffic in the HSS2 based on the UDM1 user data, when the UDM1 fails.

In one embodiment, the apparatus further comprises:

a second synchronization module configured to synchronize UDM2 user data to HSS1 upon obtaining UDM2 user data; and (c) a second step of,

a second failure handling module configured to route a second service of the HSS2 to the HSS1 based on the interlink and to handle the second service in the HSS1 based on the UDM2 user data, when the UDM2 fails.

In one embodiment, the interconnect link is a Diameter protocol based link.

In one embodiment, the apparatus further comprises:

a priority setting module configured to preset a routing priority of the interlink, the routing priority being lower than a routing priority between the HSS1 front end FEs in the HSS1, a data routing priority between the HSS1 and the corresponding UDM1, a routing priority between the HSS2 front end FEs in the HSS2, and a data routing priority between the HSS2 and the corresponding UDM 2.

In one embodiment, the apparatus further comprises:

a first pre-processing module arranged to pre-process UDM1 user data in HSS 2;

the first fault handling module comprises: a first processing unit arranged to process said first service based on pre-processed UDM1 user data in HSS 2.

In one embodiment, the apparatus further comprises:

a second pre-processing module arranged to pre-process UDM2 user data in HSS 1;

the second fault handling module comprises: a second processing unit arranged to process said second service based on the pre-processed UDM2 user data in the HSS 1.

In one embodiment, the UDM1 user data includes a first international mobile subscriber identity IMSI1 and first key KI1 information, and the apparatus further includes:

a first list establishing module configured to establish a list of IMSIs 1 based on the obtained UDM1 user data;

the first pre-processing module comprises:

the first generating unit is arranged to compare the change condition of the IMSI1 list in the HSS2 according to a preset period, and generate an IMSI1 list to be deleted and/or an IMSI1 list to be created based on a comparison result;

the second generation unit is arranged to generate a user deletion script and/or a user creation script based on the IMSI list to be deleted and/or the IMSI1 list to be created and the corresponding KI1 information;

a first execution unit arranged to execute the user delete script and/or the user create script resulting in preprocessed UDM1 user data.

In one embodiment, the UDM2 user data includes a second international mobile subscriber identity IMSI2 and second key KI2 information, and the apparatus further comprises:

a second list establishing module configured to establish an IMSI2 list based on the obtained UDM2 user data;

the second pre-processing module comprises:

a third generating unit, configured to compare, in the HSS1, the change condition of the IMSI2 list according to a preset period, and generate, based on a comparison result, an IMSI2 list that needs to be deleted and/or an IMSI2 list that needs to be created;

the fourth generation unit is arranged to generate a user deletion script and/or a user creation script based on the IMS2 list needing to be deleted and/or the IMSI2 list needing to be created and the corresponding KI2 information;

a second execution unit configured to execute the user delete script and/or the user create script, resulting in preprocessed UDM2 user data.

In one embodiment, the first synchronization module is specifically configured to upload UDM1 user data to a cloud platform; and synchronizing UDM1 user data to HSS2 based on the cloud platform.

In one embodiment, the second synchronization module is specifically configured to upload UDM2 user data to the cloud platform; and synchronizing UDM2 user data to HSS1 based on the cloud platform.

In an implementation manner, a user data synchronization system may also be developed to implement daily user data synchronization, which may be deployed at the HSS backend, and cross-update changes of UDM user data to DHLR (service correspondence: HSS20-UDM800, HSS21-UDM 801; user data backup relationship: HSS20 backup UDM801, HSS21 backup UDM800) daily. The user data synchronization system is divided into five modules, as shown in fig. 7, including an SFTP interaction module, a user data preprocessing module, a user number comparison module, and a user data change script generation module, which may correspond to the first preprocessing module and the second preprocessing module in the embodiment of the present application.

SFTP interaction module: acquiring daily backup data of the UDM from Huizhou cloud, wherein the daily backup data comprises information such as IMSI, MSISDN, KI and VLR addresses;

the user data preprocessing module: processing UDM backup data, and generating an IMSI list and a VLR address import script on the same day;

the user number comparison module: comparing the IMSI list of the current day with the IMSI list of the previous day to generate an IMSI list needing to be deleted and a user IMSI list needing to be created;

the user data change script generation module: and generating a user data deletion script and a user data creation script according to the IMSI list to be deleted, the user IMSI list to be created and KI information in the UDM backup data.

The user data change script execution module: and uploading the user data change script to a PGW for execution, waiting for an execution result, and acquiring an execution result file.

In the embodiment, by adopting a cross backup architecture design, the cross backup architecture of the HSS and the UDM can synchronously store the UDM user data for the HSS, quickly recover the user service from the HSS under an emergency condition, support the forwarding of the HSS and the corresponding UDM under a normal condition and ensure the normal connection of a 5G user. HSS and UDM synchronization software development and deployment-a user data synchronization system, wherein the software accesses a UDM data backup cloud server, compares and identifies the change condition of user data, and synchronously writes the change into the HSS to ensure that HSS emergency backup data is consistent with the UDM data. In addition, the system can also synchronously store the data of the user VLR GT (VLR Global title, VLR Global title code), and efficiently recover the data of the VLR GT on the HSS in emergency, thereby ensuring that the user call can be normally continued.

In addition, considering that the overhead to the system is relatively large, the emergency escape user data on the HSS may not include a Voice over Long-Term Evolution (VoLTE) Voice service, and therefore, in this embodiment, by using an instruction to start a transit Function of the VoLTE CSCF during an emergency, it may be implemented that, after receiving an error (for example, the error code 5001) that does not exist in the returned user when the LIR (Local Internet Registry) queries the HSS, the CSCF does not release the call, but routes the call to the MGCF (Media Gateway Control Function) for connection, so as to ensure that the escape user can successfully connect.

Correspondingly, an electronic device is also provided in an embodiment of the present application, as shown in fig. 8, including: a processor 81 and a memory 82;

the memory 82 stores computer-executable instructions;

the processor 81 executes the computer-executable instructions stored in the memory 82, so that the electronic device executes the fault service processing method.

The embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the fault service method.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method for processing a fault service is characterized by comprising the following steps:

an interconnection link is added between a first home subscriber server HSS1 and a second home subscriber server HSS2, wherein the first home subscriber server corresponds to a first unified data management network element UDM1 and is used for migrating first subscriber data stored in the first home subscriber server to the UDM1 during service upgrade to obtain UDM1 subscriber data, and the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating the first subscriber data stored in the second home subscriber server to the UDM2 during service upgrade to obtain UDM2 subscriber data;

and if the UDM1 fails, routing the first service of the HSS1 to the HSS2 based on the interconnection link, and processing the first service in the HSS2 based on the UDM1 user data.

2. The method of claim 1, further comprising, after adding an interconnect link between the first home subscriber server HSS1 and the second home subscriber server HSS 2:

if the UDM2 user data is obtained, synchronizing the UDM2 user data to the HSS 1; and if the UDM2 fails, routing a second service of the HSS2 to the HSS1 based on the interlink, and processing the second service in the HSS1 based on the UDM2 user data.

3. The method of claim 1 wherein the interconnect link is a Diameter protocol based link.

4. The method of claim 1, further comprising, after adding an interconnection link between the first home server HSS1 and the second home server HSS 2:

5. The method of claim 1, further comprising, after synchronizing the UDM1 user data to HSS2 and before routing first traffic of HSS1 to HSS2 based on the interconnect link:

preprocessing UDM1 user data in HSS 2;

processing, in the HSS2, the first service based on the UDM1 user data, including: the first service is processed in HSS2 based on the preprocessed UDM1 user data.

6. The method of claim 2, further comprising, after synchronizing UDM2 user data to HSS1 and before routing second traffic of HSS2 to HSS1 based on the interconnect link:

pre-processing UDM2 user data in HSS 1;

7. The method according to claim 5, wherein the UDM1 user data includes a first International Mobile Subscriber Identity (IMSI) 1 and a first key KI1 information, and wherein after obtaining the UDM1 user data, the method further comprises:

establishing an IMSI1 list based on the obtained UDM1 user data;

the preprocessing of UDM1 user data in HSS2, comprising:

generating a user deletion script and/or a user creation script based on the IMSI list to be deleted and/or the IMSI1 list to be created and corresponding KI1 information;

8. The method of claim 6, wherein the UDM2 user data includes a second international mobile subscriber identity IMSI2 and a second key KI2 information, and wherein after obtaining UDM2 user data, the method further comprises:

establishing an IMSI2 list based on the obtained UDM2 user data;

the preprocessing of UDM2 user data in HSS1, comprising:

comparing the change condition of the IMSI2 list in the HSS1 according to a preset period, and generating an IMSI2 list needing to be deleted and/or an IMSI2 list needing to be created based on a comparison result;

9. The method of claim 1, wherein the synchronizing the UDM1 user data to the HSS2 comprises:

10. The method of claim 2, wherein the synchronizing the UDM2 user data to the HSS1 comprises:

11. A fault traffic handling apparatus, characterized in that the apparatus comprises:

an interconnection module, configured to add an interconnection link between a first home subscriber server HSS1 and a second home subscriber server HSS2, where the first home subscriber server corresponds to a first unified data management network element UDM1, and is configured to migrate first user data stored in the first home subscriber server to the UDM1 during service upgrade to obtain UDM1 user data, and the second home subscriber server corresponds to a second unified data management network UDM2, and is configured to migrate the first user data stored in the second home subscriber server to the UDM2 during service upgrade to obtain UDM2 user data,

12. An electronic device, comprising: a processor and a memory;

the memory stores computer execution instructions;

the processor executes the computer-executable instructions stored by the memory to cause the electronic device to perform the method of fault traffic handling of any of claims 1-10.

13. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the fault service method of any one of claims 1-10.