CN114928832B

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

Info

Publication number: CN114928832B
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: 2023-07-21
Anticipated expiration: 2042-05-16
Also published as: CN114928832A

Abstract

The application provides a fault service processing method, a device, an electronic device 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 user data stored in the first home subscriber server to UDM1 to obtain UDM1 user data when a service is upgraded, and the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating first user data stored in the second home subscriber server to UDM2 when the user service is upgraded to obtain UDM2 user data; if the UDM1 user data is obtained, synchronizing the UDM1 user data to the HSS2; if the UDM1 fails, the first service of the HSS1 is routed to the HSS2 based on the interconnection link, and the first service is processed 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 re-creating HSS user data when the UDM fails, and realize the rapid recovery of failure service.

Description

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

Technical Field

The present disclosure relates to communication technologies, and in particular, to a fault service processing method, a device, an electronic apparatus, and a computer readable medium.

Background

In the early stage of 5G (5th Generation Mobile Communication Technology,5G) operation, the overall operation risk of the 5G core network (5G core,5 gc) is relatively large, and especially, the unified data management (Unified Data Management, UDM) network element carrying a large amount of user data, once the UDM fails, the service scope and the extent of the influence are very large.

According to the existing UDM escape scheme, after the escape is determined to be started by virtue of a UDM fault, user data is exported by utilizing a backup server of the UDM user data, then user data to be recovered is compiled and an instruction script for creating the user data is executed on an HSS according to a user data instruction of a home location register (Home Subscriber Server, HSS), so that the recovery of a user basic service in the HSS is realized.

Therefore, how to implement the UDM failure, to quickly rollback the UDM user data to the HSS user data is a current urgent problem to be solved.

Disclosure of Invention

The application provides a fault service processing method, a 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 of recreating HSS user data when a current UDM fails.

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

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 user data stored in the first home subscriber server to UDM1 to obtain UDM1 user data when a service is upgraded, and the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating first user data stored in the second home subscriber server to UDM2 when the user service is upgraded to obtain UDM2 user data;

if the UDM1 user data is obtained, synchronizing the UDM1 user data to the HSS2;

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

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

if the UDM2 user data is obtained, synchronizing the UDM2 user data to the HSS1; 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 based on the UDM2 user data in the HSS 1.

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

the routing priority of the interconnection link is preset, and the routing priority is lower than the routing priority between the front-end FEs of all HSS1 in the HSS1, the data routing priority between the HSS1 and the corresponding UDM1, the routing priority between the front-end FEs of all 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 the first service based on the UDM1 user data in HSS2, comprising: the first service is processed in the HSS2 based on the preprocessed UDM1 user data.

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:

preprocessing UDM2 user data in HSS 1;

processing the second service based on the UDM2 user data in HSS1, comprising: the second service is processed in the HSS1 based on the preprocessed 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:

based on the obtained UDM1 user data, an IMSI1 list is established;

the preprocessing of the UDM1 user data in the HSS2 includes:

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

generating a user deleting script and/or a user creating script based on the IMSI list to be deleted and/or the IMSI1 list 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 second key KI2 information, and after obtaining the UDM1 user data, the method further includes:

based on the obtained UDM2 user data, an IMSI2 list is established;

the preprocessing of the UDM2 user data in the HSS2 includes:

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

generating a user deleting script and/or a user creating script based on the IMS2 list to be deleted and/or the IMSI2 list to be created and the 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, the synchronizing the UDM1 user data to the 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, the synchronizing the UDM2 user data to the 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 fault service processing apparatus, 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 user data stored in the first home subscriber server to UDM1 to obtain UDM1 user data during service upgrade, the second home subscriber server corresponds to a second unified data management network UDM2 and is configured to migrate first user data stored in the second home subscriber server to UDM2 during user service upgrade to obtain UDM2 user data,

a first synchronization module configured to synchronize UDM1 user data to HSS2 when the UDM1 user data is obtained;

a first failure handling module arranged to route, upon failure of the UDM1, first traffic of the HSS1 to the HSS2 based on the interconnect link and to process the first traffic in the HSS2 based on the UDM1 user data.

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

The memory stores computer-executable instructions;

and the processor executes the computer-executed 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 that, when executed by a processor, are configured to implement the fault business method.

According to the fault service processing method, the fault service processing device, the electronic equipment and the computer readable storage medium, 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 user data stored in the first home subscriber server to the UDM1 during service upgrading to obtain UDM1 user data, the second home subscriber server corresponds to a second unified data management network UDM2 and is used for migrating the first user data stored in the second home subscriber server to the UDM2 during user service upgrading to obtain UDM2 user data, when UDM1 user data is obtained, the UDM1 user data is synchronized to the HSS2, when the UDM1 fails, the first service of the HSS1 is routed to the HSS2 based on the interconnection link, and the first service is processed in the HSS2 based on the UDM1 user data. According to the method, through the mode of carrying out the cross backup of the UDM1 user data between the HSS1 and the HSS2, when the UDM1 fails, the HSS2 which backs up the UDM1 user data is utilized to quickly call 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 application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic diagram of a business escape scheme in the related art;

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

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

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

fig. 5 is a 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 device 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.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

In order to facilitate the clear description of the technical solutions of the embodiments of the present application, the following simply describes some terms and techniques related to the embodiments of the present application:

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

5GC: the 5G core network is the core of the 5G mobile network, which establishes a reliable, secure network connection for end users and provides access to their 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 as cloud native, meaning that they are independent of the underlying cloud infrastructure, enabling higher deployment agility and flexibility.

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

The HSS supports a main user database of IP multimedia subsystem (IP Multimedia Subsystem, IMS) network entities for handling calls/sessions, which contains user profiles, performs authentication and authorization of users, and may provide information about the physical location of users, which is similar to the gsmhomelocalregister. The entities in communication with the HSS are an application server (Application Server, AS) and a call session control function server (Call Session Control Function, CSCF), wherein the application server hosts and performs services within the IMS environment. The user profile contains information about the current user-typically the service-call Session control function (S-CSCF) will download and use this file when the user 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, unified user center database), is responsible for storing user data, providing user data addition, deletion, update and query services, and providing effective data support for the FEs. The FE is responsible for signaling access and business logic processing, obtaining data services from the BE.

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

NFV (Network Functions Virtualization) network function virtualization is a concept of network architecture (network architecture), and the functions of the network node hierarchy are divided into several functional blocks by using a virtualization technology, and the functional blocks are implemented in a software manner, and are not limited to a hardware architecture.

VNF (Virtual Network Feature): the virtualized network functions, including the VNF network functions and the EMS element management system, configure and manage the functions of the VNF. In general, the EMS and the VNF are in one-to-one correspondence, and it can be understood that the VNF is a virtual network function unit in the NFV architecture. NFV is a technique of virtualizing network functions, and for example, functions of a conventional communication network may be implemented by a virtualization technique in the IT field. A VNF may be understood as an individual network element that is virtualized out.

DRA (Diameter Routing Agent): and the routing agent node and the DRA node are responsible for the translation and transfer of the LTE (Long Term Evolution ) Diameter signaling destination address, and realize authentication, location updating and charging management of the LTE user.

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

Map (Management Autonomy Platform): an automatic generation system of a management application platform, which is 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 in the DC1 (Dual Connectivity) switching center, and is typically located in a provincial city, where devices classified into several levels typically operate one-to-two simultaneously with one primary and one backup for the conversion and processing of provincial inter-level traffic.

SFTP (Secure File Transfer Protocol): is a Secure file transfer protocol, is a Secure Shell (SSH) inclusive protocol, that is, SFTP can be used as long as the sshd remote connection server is started, without additional installation, and its default port is 22 as with SSH. SFTP ensures the security of transmitted files by using encryption/decryption technology, so that the transmission efficiency of SFTP is lower than that of common file transfer protocol FTP, but the security of SFTP is higher than that of FTP, so that SFTP is generally used in scenes with higher security requirements such as reports, statements, and the like.

PGW (PDN GateWay): a network packet data network gateway provides session management and bearer control, data forwarding, IP address allocation, etc. for the user.

IMSI (International Mobile Subscriber Identity): the international mobile subscriber identity is an identity that is used to distinguish between different subscribers in a cellular network and is not repeated in all cellular networks. The handset sends the IMSI to the network in a 64-bit field. The IMSI can be used to query the home location register (HLR, home Location Register) or visitor location register (VLR, visitor Location Register) for subscriber information. To avoid the listener identifying and tracking a particular subscriber, in most cases the communication between the handset and the network uses a randomly generated temporary mobile subscriber identity (TMSI, temporary Mobile Subscriber Identity) instead of the IMSI.

The MSISDN (Mobile Subscriber International ISDN/PSTN number), ISDN (Integrated Service Digital Network) is the integrated services digital network, and the MSISDN refers to the number that a calling subscriber needs to dial in order to call a mobile subscriber, and acts as a fixed network PSTN (Public Switched Telephone Network, public switched telephone network number), which is the only number that can identify the mobile subscriber in the public switched telephone network numbering plan.

KI (Key identifier) the key, also called the handset authentication key, is the key that encrypts the data transfer between the SIM (Subscriber Identity Module ) card and the operator.

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

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

In the initial application process of new technologies such as NFV architecture of the 5G core network, there are many unknown defects and risks in planning, designing and deploying levels such as hardware servers, virtualization layers and VNFs, and in addition, the DC architecture relatively concentrated in deployment regions causes the fault risk to be relatively prominent, so that the overall operation risk of the 5G core network is relatively large at the present stage, especially the UDM network element carrying a large amount of user data, and once the fault occurs, the affected service range and degree are very large.

In the related art, the escape scheme established by each operator aiming at the UDM fault condition is that after the UDM fault is determined, the UDM user data is re-created in the HSS, so that the escape time is too long, and the user service cannot be recovered in a short time. Taking an example of a UDM failure that has recently occurred in a certain operator in the country, it takes approximately 2 hours to bring back 2.7 ten thousand important user data to the HSS.

Taking the network architecture of the Hunan area as an example, two sets of HSS exist in the Hunan existing network, namely HSS20 and HSS21, and two sets of UDM, namely UDM800 and UDM801; the HSS20 corresponds to the UDM800 and covers long sand (except 15X/185), yiyang, zhou, hengyang, xiangtan and Yongzhou city numbers; HSS21 corresponds to UDM801 and covers Changsha 15X/185, kanjia, shouyang, yueyang, changde, huai, queen, zhang Jianjia and Jijijijidi city numbers. After upgrading the 5G service, the user migrates from the corresponding HSS to the UDM.

Referring to fig. 1, the service switching situation of the existing network is that the user service of the registration section under UDM800 is routed to HSSFE20, and after FE to BE (ONE-NDS) inquires that the user does not exist, the service Retry is sent to UDM800; the user service of the registering section under the UDM801 is routed to the HSSFE21, and after the FE to BE (ONE-NDS) inquires that the user does not exist, the service is Retry to the UDM801; the Diameter service is switched through a direct connection port of the HSS FE and the UDM FE; MAP traffic is diverted through HSTP.

As shown in fig. 1, the existing network original escape scheme is that the UDM800 uploads user information to the wheatstate cloud every day, and the ONE-NDS20 INS downloads user data from the wheatstate cloud and generates a current day escape script; the UDM801 generates an escape script every day and uploads the escape script to the Huizhou cloud, and the ONE-NDS21 INS downloads the escape script from the Huizhou cloud and stores the escape script; after the escape is started, the ONE-NDS INS transmits an 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, in the embodiment of the present application, a cross backup manner of UDM and HSS on user data is adopted, 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 UDM fails, no user needs to be temporarily created during emergency escape, and through a cross backup mechanism of the UDM and the HSS, in the cross backup mechanism of the embodiment of the present application, under normal circumstances that no failure occurs, the HSS does not store corresponding UDM user data, but stores user data of other UDMs, after the DRA routes to a certain set of HSS corresponding to the HSS, the set of HSS does not contain corresponding UDM user data, and still forwards to the UDM for connection, so that 5G user connection is not affected, and under emergency circumstances that failure occurs, the backup user data in the call access HSS can be greatly shortened by modifying simple routing parameters, and the escape duration can be restored within ten minutes.

The following describes the technical scheme of the present application in detail. Embodiments of the present application may be combined with each other and may not be described in detail in some embodiments for the same or similar concepts or processes. 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 the embodiment of the present application, where the embodiment is illustrated in 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 illustrated in a wheatstone cloud, where the HSS20 server includes an HSS20 front end—an HSS FE20 and an HSS20 back end-ONE-NDS 20, and the HSS21 server includes an HSS21 front end-HSS FE21 and an HSS21 back end-ONE-NDS 21; the network elements of UDM800 include UDM800 front end-UDM 800FE and UDM800 back end-UDM 800BE, unlike the prior art, in the network architecture of the embodiment of the present application, an interconnected data transmission link is established between HSS20 and HSS21, so that data synchronization can BE performed between HSS FE20 and HSS FE21 through the data transmission link, and in terms of user data, a cross backup mode in which HSS20 BE (i.e., ONE-NDS 20) is used to store UDM801 and HSS21 BE (i.e., ONE-NDS 21) is used to store UDM 800. The user data is created in advance in BE and can BE updated daily according to the user information of the UDM, that is, ONE-NDS20 stores HSS20 own user and UDM801 user data, ONE-NDS21 stores HSS21 own user and UDM800 user data.

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

Referring to fig. 3, fig. 3 is a flowchart of 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 user data stored in the first home subscriber server to UDM1 to obtain UDM1 user 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 first user data stored in the second home subscriber server to UDM2 when a user service is upgraded to obtain UDM2 user data.

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

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

The Diameter protocol is used as the next generation AAA protocol standard by the IETF (The Internet Engineering Task Force, internet engineering task force) AAA working group. Diameter protocols include basic protocols, NAS (Network Attached Server, network access service) protocols, EAP (Extensible Authentication Protocol, extended authentication) protocols, MIP (Mobile IP) protocols, CMS (Cryptographic Message Synta, cipher message syntax) protocols, and the like. The Diameter protocol supports authentication, authorization and accounting for mobile IP, NAS requests and mobile agents, and is implemented similarly to RADIUS (Remote Authentication Dial In User Service, remote subscriber dial-in service), also using the AVP protocol.

In this embodiment, by adding the Diameter protocol-based interconnection transmission between the HSS1 and the HSS2, efficient service switching between the HSS1 and the HSS2 can be achieved.

In one embodiment, to reduce the impact of the interlink on the HSS1 and the HSS2 under normal conditions, so as to ensure the normal processing flow of the service under normal conditions, after adding the interlink between the first home subscriber server HSS1 and the second home subscriber server HSS2, the method further includes the following steps:

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 HSS FE through the interconnection link, so as to achieve continuity of the service. That is, the interconnection link of the present embodiment is only enabled when a service failure occurs, and in a normal case, corresponding user data can be queried by using between HSS FEs, or service routing is implemented between the HSS FEs and the UDM FEs.

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

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

Compared with the related art, in the case of a UDM1 failure, the UDM1 user data is re-created in the HSS1, and because of the huge amount of data, a lot of time is required to create the data, and the user traffic cannot be recovered in a short time. In order to solve this technical problem, the present embodiment uses 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 to the HSS2, when the UDM1 fails, the user data does not need to be created again in the HSS1, the HSS2 already synchronizes the corresponding UDM user data, and by switching to the HSS2, the failure service of the UDM1 is quickly recovered by using the corresponding UDM1 user data in the HSS2.

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

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

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

In this embodiment, when the UDM fails, the service is quickly switched based on the interconnection link, and under normal conditions, the service of the lower number segment of the UDM800 is routed to the HSS20 FE first, and because the user data of the UDM800 is not stored on the HSS20 BE, the service is still routed to the UDM800 FE for connection normally; the situation is similar for UDM 801. The method is the same as before the optimization, and has no influence on the existing service.

Referring to fig. 4, fig. 4 is a schematic flow chart 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 UDM2 by adopting the same cross backup manner for UDM corresponding to another set of HSS, so as to implement fast recovery of fault service of UDM2, specifically, after adding an interconnection link between the first home subscriber server HSS1 and the second home subscriber server HSS2 (step S301), the method further includes the following steps S401 and S402.

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

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

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 that of synchronizing the UDM1 user data to the HSS2 and performing service continuity in the HSS2 in the above embodiment, and will not be repeated here.

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

Referring to fig. 5, fig. 5 is a schematic flow chart of a further processing method of a fault service provided in the embodiment of the present application, where, based on the above embodiment, considering that the amount of UDM user data is huge, the present embodiment may not be able to be directly used in HSS, in order to facilitate efficient use of the UDM user data in HSS, the present embodiment pre-processes the UDM user data after the UDM data synchronization is completed by the corresponding HSS, and when a fault service occurs, the service may be continued directly based on the pre-processed UDM data to further improve service recovery efficiency, specifically, after synchronizing the UDM1 user data to HSS2 (step S302), and before routing the first service of HSS1 to HSS2 based on the interconnection link (step S303), the following step S501 is included, and step S303 is further divided into step S303a.

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

Specifically, the UDM1 user data includes the first international mobile subscriber identity IMSI1 and the first key KI1 information, and in some embodiments, MSISDN, VLR address, and other information. Since the daily UDM user data may change, in order to ensure that service recovery is performed for the latest UDM user data when a fault service is generated, in this embodiment, the preprocessing efficiency of the UDM user data is improved by establishing an IMSI1 list and performing user deletion and/or user script creation according to the list, and specifically the method further includes the following steps: based on the obtained UDM1 user data, an IMSI1 list is established.

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

a. comparing the changing condition of the IMSI1 list according to a preset period, and generating the IMSI1 list to be deleted and/or the IMSI1 list to be created based on the comparison result.

b. And generating a user deleting script and/or a user creating 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 may take a day as a unit, for example, obtain daily user data of the UDM from the wheatstone cloud, where the daily user data includes IMSI, MSISDN, KI, VLR address information, process the UDM user data, generate a current day IMSI list and a VLR address import script, compare the current day IMSI list with a previous day IMSI list, and generate an IMSI list to be deleted and a user IMSI list to be created.

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 to execute, and an execution result is waited for, so as to obtain an execution result file, wherein the execution result file is preprocessed UDM1 user data, and the preprocessed UDM1 user data can be directly used at the HSS 2.

Further, the same method is adopted for the user data of the UDM2 in this embodiment to improve the failure service recovery efficiency of the UDM2, specifically, after synchronizing the user data of the UDM1 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:

Preprocessing UDM2 user data in HSS 1;

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

based on the obtained UDM2 user data, an IMSI2 list is established;

the preprocessing of the UDM2 user data comprises the following steps:

comparing the changing condition of the IMSI2 list according to a preset period, and generating the IMSI2 list to be deleted and/or the IMSI2 list to be created based on the 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 that of preprocessing the UDM1 user data in the HSS2, and will not be described herein.

In order to verify the effectiveness of the fault service processing method used in the embodiment, the time-consuming comparison is performed on the fault service processing method and the existing service escape method, and the conclusion is that the daily escape script before the optimization is stored in ONE-NDS21, and the time-consuming time of operating the script creation user is about 1 hour per million users, calculated by the current UDM801 account opening user is 2.5 hours; ON the other hand, after the fault service is optimized according to the present embodiment, the user updates to ON2-NDS20 (created) every day, and modifies the front end pointing direction of HSS21 during escape, so that the front end of UDM801 user Lu Youzhi HSS20 is continuous, which takes only about 15 minutes.

The embodiment of the application correspondingly further provides a fault service processing device, as shown in fig. 6, where 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, the first home subscriber server corresponding to a first unified data management network element UDM1 for migrating first user data stored therein to UDM1 during service upgrade to obtain UDM1 user data, the second home subscriber server corresponding to a second unified data management network UDM2 for migrating first user data stored therein to UDM2 during user service upgrade to obtain UDM2 user data,

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

a first failure handling module 63 arranged to route first traffic of HSS1 to HSS2 based on the interconnect link upon a failure of UDM1 and to process the first traffic in HSS2 based on the UDM1 user data.

In one embodiment, the apparatus further comprises:

a second synchronization module configured to synchronize UDM2 user data to HSS1 when the UDM2 user data is obtained; the method comprises the steps of,

And a second failure handling module configured to route a second traffic of the HSS2 to the HSS1 based on the interconnect link when the UDM2 fails, and to process the second traffic in the HSS1 based on the UDM2 user data.

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

In one embodiment, the apparatus further comprises:

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

In one embodiment, the apparatus further comprises:

a first preprocessing module configured to preprocess UDM1 user data in the HSS 2;

the first fault handling module includes: a first processing unit arranged to process said first traffic in the HSS2 based on the preprocessed UDM1 user data.

In one embodiment, the apparatus further comprises:

a second preprocessing module configured to preprocess UDM2 user data in the HSS 1;

The second fault handling module includes: a second processing unit arranged to process said second traffic in the HSS1 based on the preprocessed UDM2 user data.

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

a first list establishing module configured to establish an IMSI1 list based on the obtained UDM1 user data;

the first preprocessing module comprises:

the first generation unit is arranged for comparing the changing condition of the IMSI1 list in the HSS2 according to a preset period, and generating the IMSI1 list to be deleted and/or the IMSI1 list to be created based on the comparison result;

the second generation unit is configured 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;

and the first execution unit is used for executing the user deletion script and/or the user creation script to obtain preprocessed UDM1 user data.

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

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

the second preprocessing module comprises:

the third generation unit is arranged for comparing the changing condition of the IMSI2 list in the HSS1 according to a preset period, and generating the IMSI2 list to be deleted and/or the IMSI2 list to be created based on the comparison result;

a fourth generating unit, configured to generate 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 the corresponding KI2 information;

and the second execution unit is used for executing the user deleting script and/or the user creating script to obtain the 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 a cloud platform; and synchronizing UDM2 user data to HSS1 based on the cloud platform.

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

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

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

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

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

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

In this embodiment, a cross backup architecture design is adopted, and the cross backup architecture of the HSS and the UDM can save UDM user data for implementing HSS synchronization, and in an emergency situation, the user service is quickly restored from the HSS, and the HSS can be supported to forward with the corresponding UDM in connection under normal conditions, so as to ensure normal connection of the 5G user. The HSS and UDM synchronous software development and deployment-user data synchronous system, the software accesses the UDM data backup cloud server, compares and identifies the change condition of the user data, and synchronously writes the change into the HSS to ensure that the HSS emergency backup data is consistent with the UDM data. In addition, the system can synchronously save the VLR GT (VLR Global title) data of the user, and can efficiently restore the VLR GT data on the HSS when in emergency, thereby ensuring that the user call can be continued normally.

In addition, because the system overhead is relatively large, the emergency escape user data on the HSS may not include the Voice over Long-Term Evolution (lte) Voice service, and the embodiment adopts an instruction for starting the transit function of the VoLTE CSCF in emergency, so that the CSCF can implement that after receiving an error (for example, the error code 5001) which does not exist in the return user when the LIR (Local Internet Registry, the common ground registration authority) queries the HSS, the CSCF does not release the call, but routes the call to the MGCF (Media Gateway Control Function, the media gateway control function) for connection, thereby ensuring that the escape user can succeed in connection.

The embodiment of the application correspondingly further provides an electronic device, as shown in fig. 8, including: a processor 81 and a memory 82;

the memory 82 stores computer-executable instructions;

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

The embodiment of the application correspondingly provides a computer readable storage medium, wherein computer execution instructions are stored in the computer readable storage medium, and the computer execution instructions are used for realizing the fault business method when being executed by a processor.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the 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 cooperatively by several physical components. 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 both 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 known to those skilled 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 be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, 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.

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 application 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 application 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 is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method for processing fault service, comprising:

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

after adding the interconnection link between the first home subscriber server HSS1 and the second home subscriber server HSS2, it further includes:

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

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

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

preprocessing UDM1 user data in HSS 2;

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

preprocessing UDM2 user data in HSS 1;

6. The method of claim 4, wherein the UDM1 user data includes a first international mobile subscriber identity IMSI1 and first key KI1 information, and wherein after obtaining the UDM1 user data, the method further comprises:

Based on the obtained UDM1 user data, an IMSI1 list is established;

the preprocessing of the UDM1 user data in the HSS2 includes:

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

based on the obtained UDM2 user data, an IMSI2 list is established;

the preprocessing of the UDM2 user data in the HSS1 includes:

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

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

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

10. A fault service handling apparatus, the apparatus comprising:

a first failure handling module arranged to route a first traffic of HSS1 to HSS2 based on the interconnect link when UDM1 fails, and to process the first traffic in HSS2 based on the UDM1 user data;

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

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory to cause the electronic device to perform the fault business processing method of any one of claims 1-9.

12. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to implement the fault business method of any of claims 1-9.