CN115278744A

CN115278744A - Universal Data Management (UDM) network element equipment fault detection method and device and electronic equipment

Info

Publication number: CN115278744A
Application number: CN202210908125.9A
Authority: CN
Inventors: 胡家元; 李文云; 李建钊; 高敏; 朱华虹
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-07-29
Filing date: 2022-07-29
Publication date: 2022-11-01

Abstract

The application provides a method and a device for detecting faults of Universal Data Management (UDM) network element equipment and electronic equipment, wherein the method comprises the following steps: responding to a user request of an access user, and sending the user request to a routing agent node; forwarding the user request to a target UDM network element device through the routing agent node, wherein the target UDM network element device is associated with a home network identification code of the access user; setting granularity corresponding to the home network identification code based on the failure times of not receiving the response of the target UDM network element equipment to the user request; and based on the granularity, carrying out fault detection on the target UDM network element equipment. According to the embodiment of the application, the fault detection cost is reduced, and meanwhile, the fault detection efficiency is guaranteed.

Description

Universal Data Management (UDM) network element equipment fault detection method and device and electronic equipment

Technical Field

The application relates to the field of communication, in particular to a Universal Data Management (UDM) network element equipment fault detection method and device and electronic equipment.

Background

In 4G/5G core network deployment, when a 5G user is attached to a 4G network, the MME network element equipment and the UDM network element equipment perform interconnection communication through an S6a interface to complete authentication authorization, location update and the like. The characteristic can cause the complication of the network, thereby bringing various difficulties for fault detection of the MME network element equipment to the UDM network element equipment, and leading the fault detection of the UDM network element equipment to be difficult to consider both cost and efficiency.

Disclosure of Invention

An object of the present application is to provide a data processing method, an apparatus, an electronic device, and a storage medium, which reduce the cost of fault detection and ensure the efficiency of fault detection.

According to an aspect of the embodiments of the present application, a method for detecting a fault of a universal data management UDM network element device is disclosed, which is applied to a mobility associated entity MME network element device, and the method includes:

responding to a user request of an access user, and sending the user request to a routing agent node;

forwarding the user request to a target UDM network element device through the routing agent node, wherein the target UDM network element device is associated with a home network identification code of the access user;

setting granularity corresponding to the home network identification code based on the failure times of not receiving the response of the target UDM network element equipment to the user request;

and based on the granularity, carrying out fault detection on the target UDM network element equipment.

According to an aspect of the embodiments of the present application, a universal data management UDM network element device fault detection apparatus is disclosed, which is provided in a mobility associated entity MME network element device, and the apparatus includes:

the routing agent node comprises a sending module, a routing agent node and a routing agent module, wherein the sending module is configured to respond to a user request of an access user and send the user request to the routing agent node;

a forwarding module configured to forward the user request to a target UDM network element device via the routing agent node, wherein the target UDM network element device is associated with a home network identifier of the access user;

a granularity module configured to set a granularity corresponding to the home network identifier based on a failure number of times of not receiving a response of the target UDM network element device to the user request;

and the detection module is configured to detect the fault of the target UDM network element equipment based on the granularity.

According to an aspect of an embodiment of the present application, an electronic device is disclosed, including: a memory storing computer readable instructions; a processor reading computer readable instructions stored by the memory to perform the method of any of the preceding claims.

According to an aspect of embodiments of the present application, a computer program medium is disclosed, having computer readable instructions stored thereon, which, when executed by a processor of a computer, cause the computer to perform the method of any of the preceding claims.

According to an aspect of embodiments herein, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations described above.

In the embodiment of the application, the routing agent node is arranged between the MME network element device and the UDM network element device, and the switching is performed through the routing agent node, so that the network complexity between the MME network element device and the UDM network element device when a 5G user is attached to a 4G network can be reduced. And the granularity corresponding to the home network identification code is set based on the failure times of the target UDM network element equipment which does not receive the response to the user request, and the fault detection is carried out on the target UDM network element equipment based on the granularity, so that the MME network element equipment can detect the state of the UDM network element equipment only by managing the incidence relation between the home network identification code and the UDM network element equipment, and no additional network management equipment is required to be arranged between the MME network element equipment and the UDM network element equipment, thereby reducing the fault detection cost and ensuring the fault detection efficiency.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

Fig. 1 shows a flowchart of a method for detecting a failure of a universal data management UDM network element device according to an embodiment of the present application.

Figure 2 shows a schematic diagram of UDM network element device failure detection according to an embodiment of the present application.

Figure 3 shows a schematic diagram of UDM network element device failure detection according to an embodiment of the present application.

Fig. 4 shows a block diagram of an apparatus for fault detection of a data management UDM network element device according to an embodiment of the present application.

FIG. 5 illustrates an electronic device hardware diagram according to one embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these example embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The drawings are merely schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. In the following description, numerous specific details are provided to give a thorough understanding of example embodiments of the present application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, steps, and so forth. In other instances, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The application provides a Universal Data Management (UDM) network element equipment fault detection method, which is applied to Mobility Management Entity (MME) network element equipment in a 5G application scene and is used for detecting whether the UDM network element equipment has faults or not.

Fig. 1 shows a flowchart of a method for detecting a failure of a universal data management UDM network element device according to an embodiment of the present application, where an execution subject of the method is an MME network element device, and the method includes:

step S110, responding to a user request of an access user, and sending the user request to a routing agent node;

step S120, the user request is forwarded to target UDM network element equipment through a routing agent node, wherein the target UDM network element equipment is associated with the home network identification code of the access user;

step S130, setting granularity corresponding to the home network identification code based on the failure times of not receiving the response of the target UDM network element equipment to the user request;

and step S140, based on the granularity, carrying out fault detection on the target UDM network element equipment.

Specifically, when the 5G user is attached to the 4G network, the MME network element device and the UDM network element device perform interconnection communication through an S6a interface, thereby completing authentication authorization, location update, and the like. Because direct and full interconnection between the MME network element device and the UDM network element of each region through the S6a interface may cause the network to be too complex and difficult to manage, in the embodiment of the present application, a Routing Agent node DRA (Diameter Routing Agent) is deployed between the MME network element device and the UDM network element device.

And after the user accesses the MME network element equipment, sending a user request to the MME network element equipment. And the MME network element equipment responds to the user request of the access user and sends the user request to the DRA. And then the DRA forwards the user request to a target UDM Network element device associated with the Home Network identification code according to the Home Network identification code HNI (Home Network Identity) of the access user. The home network identification code is used to identify the network to which the corresponding user belongs. And different home network identification codes are associated with different UDM network element devices, so that the home network identification codes provide the MME with the capability of identifying and detecting the state of the UDM network element devices in the interaction process with the UDM network element devices.

According to the embodiment of the application, the network complexity between the MME network element equipment and the UDM network element equipment when the 5G user is attached to the 4G network is reduced through the switching of the DRA. But simultaneously has a new problem: under the setting of DRA switching, because the MME network element device is in indirect communication with the target UDM network element device, the MME network element device cannot perceive whether the target UDM network element device is in a normal state or a failure state. When the target UDM network element device fails, the MME network element device may continuously send a request for sending a user request to the target UDM network element device to the DRA, but cannot receive a normal response, thereby causing a large increase in invalid information in the network.

Because the MME network element device cannot perceive whether the target UDM network element device is in a normal state or a fault state under the setting of DRA handover, in this embodiment of the application, after the MME network element device sends the user request to the DRA, it monitors the number of failure times that the target UDM network element device does not receive a response to the user request. And then setting the granularity corresponding to the home network identification code based on the monitored failure times. Wherein the granularity is used to describe the number of times that the UDM network element device associated with the granularity, i.e. the target UDM network element device, does not respond to the user request forwarded by the DRA.

The larger the granularity is, the more times that the target UDM network element equipment does not respond to the user request forwarded by the DRA is, the higher the possibility that the target UDM network element equipment fails is; conversely, the smaller the granularity is, the smaller the number of times that the target UDM network element device does not respond to the user request forwarded by the DRA is, and the smaller the possibility that the target UDM network element device fails. Therefore, in the embodiment of the application, the MME network element device can accurately and timely perform fault detection on the target UDM network element device based on the granularity corresponding to the home network identification code, and the efficiency of fault detection is ensured.

Therefore, in the embodiment of the application, by setting the routing proxy node between the MME network element device and the UDM network element device and performing switching through the routing proxy node, the network complexity between the MME network element device and the UDM network element device can be reduced when a 5G user is attached to a 4G network. And the granularity corresponding to the home network identification code is set based on the failure times of the target UDM network element equipment which does not receive the response to the user request, and the fault detection is carried out on the target UDM network element equipment based on the granularity, so that the MME network element equipment can detect the state of the UDM network element equipment only by managing the incidence relation between the home network identification code and the UDM network element equipment, and no additional network management equipment is required to be arranged between the MME network element equipment and the UDM network element equipment, thereby reducing the fault detection cost and ensuring the fault detection efficiency.

In an embodiment, the method for detecting a failure of a universal data management UDM network element device provided in the embodiment of the present application further includes:

obtaining an International Mobile Subscriber Identity (IMSI) number segment of an access subscriber;

and extracting the home network identification code from the IMSI number segment.

In this embodiment, after a user accesses an MME network element device, the MME network element device obtains an International Mobile Subscriber Identity (IMSI) (International Mobile Subscriber Identity) number segment corresponding to the access user. The IMSI number field is an identifier that does not repeat in the cellular network and is used to distinguish different users in the cellular network. In general, the ue stores the IMSI number segment in a 64-bit field and sends the field to the MME network element device.

And after obtaining the IMSI number section of the access user, the MME network element equipment extracts the home network identification code HNI from the IMSI number section.

In an embodiment, the setting the granularity corresponding to the home network identifier based on the number of failures of not receiving a response of the target UDM network element device to the user request includes:

acquiring the continuous failure times of the target UDM network element equipment in a preset time period based on the failure event that the response of the target UDM network element equipment to the user request is not received and the success event that the response of the target UDM network element equipment to the user request is received;

the number of consecutive failures was set to the granularity.

In this embodiment, the MME network element device monitors a failure event in which the target UDM network element device does not receive a response to the user request, and monitors a success event in which the target UDM network element device receives a response to the user request. And determining the number of continuous failures within a preset time period based on the monitored failure events and success events.

Optionally, both the monitored failure event and success event have time information. According to the time information corresponding to the events, the failure events and the success events are sequenced, and then continuous failure events in a preset time period can be screened out according to the sequence of the events, so that the continuous failure times in the preset time period are determined. And further setting the determined continuous failure times as the granularity corresponding to the home network identification code.

Optionally, monitoring failure events and success events within a preset time period is performed. In the process, each time a failure event is monitored, the continuous failure times are increased by one; a success event marks the stop growth of the number of consecutive failures. I.e. the increase of the number of consecutive failures is stopped as soon as a success event is detected.

In this embodiment, the reason why the number of consecutive failures is set as the granularity for detecting the failure is that when the target UDM network element device does not respond to the user request, it is not necessarily able to indicate that the target UDM network element device has a failure. This happens occasionally, mostly due to communication quality or other factors; this situation continues to be the more powerful one to specify that the target UDM network element device has failed. Therefore, the MME network element equipment sets the continuous failure times as the granularity for fault detection, and the accuracy of fault detection is improved.

when a success event is detected within a preset time period, the number of consecutive failures is reset to 0.

In this embodiment, once the MME network element device detects a success event within a preset time period, the number of accumulated consecutive failures is reset to 0. In this embodiment, after the accumulated consecutive failure times are reset to 0, if a failure event is detected again, the consecutive failure times are accumulated again from 0.

For example: the preset time period is [ T1, T2] with the duration of T.

At time t1, the number of consecutive failures is set to 0. That is, the granularity corresponding to the home network identifier is set to 0.

And starting from the time t1, and adding one to the continuous failure times/granularity when detecting a failure event which does not receive a response of the target UDM network element equipment corresponding to the home network identification code aiming at the user request, by taking 0 as a starting point.

And at the time of t3, detecting a success event of receiving a response of the target UDM network element equipment corresponding to the home network identification code aiming at the user request, and resetting the continuous failure times/granularity to 0. Wherein the time t3 is between the time t1 and the time t 2.

And continuing starting from the moment t3, starting from the condition that the continuous failure times/granularity is 0 again, and adding one to the continuous failure times/granularity when detecting that the failure event corresponding to the target UDM network element equipment corresponding to the home network identification code and responding to the user request is not received.

According to the logic, the current stage processing is temporarily finished until the time t 2.

and when a success event is detected in the preset time period, resetting the preset time period and resetting the continuous failure times to 0.

In this embodiment, once the MME network element device detects a success event within a preset time period, the MME network element device resets the accumulated consecutive failure times to 0, and also resets the preset time period. The resetting of the preset time period refers to resetting the starting time of the preset time period and keeping the duration of the preset time period unchanged.

For example: the preset time period is [ T1, T2] with the duration of T.

And starting from the time t1, and adding one to the continuous failure times when detecting that the failure event corresponding to the target UDM network element equipment corresponding to the home network identification code and responding to the user request is not received by taking 0 as a starting point. I.e. the particle size is increased by one.

At the time of T3, detecting that a success event in response to the user request by the target UDM network element device corresponding to the home network identifier is received, resetting the number of continuous failures/granularity to 0, and resetting the preset time period to T [ T3, T4] with the duration of T. The time t3 is between the time t1 and the time t2, and the time t2 is between the time t3 and the time t 4.

And starting from the moment t3, starting from the condition that the continuous failure times/granularity are 0 again, and adding one to the continuous failure times/granularity when detecting that the failure event corresponding to the target UDM network element equipment corresponding to the home network identification code and aiming at the user request is not received.

According to the continuous execution of the logic, if the continuous failure times/granularity and the reset of the preset time period do not occur again in the midway, the current stage processing is temporarily finished until the time t 4.

and resetting the preset time period and the continuous failure times to 0 when the preset time period is over.

In this embodiment, once the MME network element device monitors that the preset time period ends, the preset time period is reset, and the accumulated consecutive failure times are reset to 0.

For example: the preset time period is [ T1, T2] with the duration T.

And in the process from the time t1 to the time t2, accumulating and resetting the continuous failure times according to the detected failure event and success event, and updating the granularity corresponding to the home network identification code in real time according to the continuous failure times.

At the time T2, regardless of the specific value of the number of continuous failures/the granularity, regardless of whether the number of continuous failures/the granularity is reset, the number of continuous failures/the granularity is reset to 0, and the preset time period is reset to [ T2, T3] with the duration T.

And in the process from the time t2 to the time t3, accumulating and resetting the continuous failure times according to the detected failure events and success events, and updating the granularity corresponding to the home network identification code in real time according to the continuous failure times.

In an embodiment, performing fault detection on a target UDM network element device based on granularity includes:

when the granularity is larger than a preset threshold value, determining the target UDM network element equipment as a fault state;

and when the granularity is less than or equal to a preset threshold value, determining the target UDM network element equipment to be in a normal state.

In this embodiment, the MME network element device determines whether the target UDM network element device fails according to a relative size between the granularity and a preset threshold, where the threshold is preset for the granularity.

Specifically, when the granularity corresponding to the home network identification code is greater than a preset threshold, the target UDM network element device associated with the home network identification code is determined to be in a fault state. And when the granularity corresponding to the home network identification code is less than or equal to a preset threshold value, determining the target UDM network element equipment associated with the home network identification code as a normal state.

acquiring secondary UDM network element equipment, wherein the secondary UDM network element equipment is associated with a home network identification code, and the priority of the secondary UDM network element equipment is lower than that of target UDM network element equipment;

and after the target UDM network element equipment is confirmed to be in a fault state, indicating the routing agent node to forward the user request to the secondary UDM network element equipment.

In this embodiment, the home network identifier is associated with a plurality of UDM network element devices, and the UDM network element devices have different priorities. Preferably, the MME network element device preferentially instructs the DRA to forward the user request to the UDM network element device of the highest priority. That is, in general, the target UDM network element device is the highest priority UDM network element device.

And after confirming that the target UDM network element equipment is in a fault state, the MME network element equipment indicates the DRA to forward the user request to secondary UDM network element equipment with the priority lower than that of the target UDM network element equipment, so that the problem that a large number of invalid messages are sent due to the fault of the UDM network element equipment is solved.

In an embodiment, after discovering the failed UDM network element device, the MME network element device notifies other MME network element devices of information about the failed UDM network element device, thereby preventing the other MME network element devices from sending information to the failed UDM network element device, and reducing occurrence of failure of overall authentication of the network.

Fig. 2 and fig. 3 show schematic diagrams of UDM network element device failure detection in an embodiment of the present application.

Referring to fig. 2 and 3, in an embodiment, a routing DRA is deployed between an MME network element device and a UDM network element device. And the MME network element equipment responds to the user request of the access user and sends the user request to the DRA. And the DRA forwards the user request to the target UDM network element equipment associated with the home network identification code according to the home network identification code of the access user. Different UDM network element devices are set with different priorities, and generally, a user request is preferentially forwarded to the UDM network element device with the highest priority.

The MME network element device maintains a cache table as shown. The cache table records the priority, granularity and state of the UDM network element equipment associated with different home network identification codes. Wherein, the threshold value set for the granularity corresponding to the home network identification code is 5. That is, once the granularity of the UDM network element device associated with a certain home network identifier is greater than or equal to 5, the state of the UDM network element device associated with the home network identifier is modified from normal to failure.

Specifically, for any specific home network identifier, in a preset time period with a time length of T, the granularity of the UDM network element device associated therewith is set to 0. And monitoring failure events which do not receive the response of the target UDM network element equipment to the user request in the preset time period, confirming the continuous failure times, and taking the continuous failure times as granularity. And once a success event responding to the user request by the target UDM network element equipment is detected and the continuous failure times/granularity is reset to 0.

And when the granularity of the home network identification code reaches 5, confirming that the UDM network element equipment associated with the home network identification code has a fault, and modifying the state of the UDM network element equipment from normal to fault.

Fig. 4 is a block diagram illustrating an apparatus for detecting a failure of a universal data management UDM network element device according to an embodiment of the present application, where the apparatus is disposed in a mobility associated entity MME network element device, and the apparatus includes:

the sending module is configured to respond to a user request of an access user and send the user request to the routing agent node;

In an exemplary embodiment of the present application, the apparatus is configured to:

acquiring an International Mobile Subscriber Identity (IMSI) number segment of the access subscriber;

and setting the continuous failure times as the granularity.

and resetting the continuous failure times to 0 when the success event is detected in the preset time period.

and resetting the preset time period and resetting the continuous failure times to 0 when the preset time period is ended.

and when the granularity is smaller than or equal to the preset threshold, determining the target UDM network element equipment to be in a normal state.

acquiring secondary UDM network element equipment, wherein the secondary UDM network element equipment is associated with the home network identification code, and the priority of the secondary UDM network element equipment is lower than that of the target UDM network element equipment;

An electronic device 30 according to an embodiment of the present application is described below with reference to fig. 5. The electronic device 30 shown in fig. 5 is only an example, and should not bring any limitation to the functions and the application range of the embodiment of the present application.

As shown in fig. 5, the electronic device 30 is in the form of a general purpose computing device. The components of the electronic device 30 may include, but are not limited to: the at least one processing unit 310, the at least one memory unit 320, and a bus 330 that couples various system components including the memory unit 320 and the processing unit 310.

Wherein the storage unit stores program code executable by the processing unit 310 to cause the processing unit 310 to perform steps according to various exemplary embodiments of the present invention described in the description part of the above exemplary methods of the present specification. For example, the processing unit 310 may perform various steps as shown in fig. 1.

The storage unit 320 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM) 3201 and/or a cache memory unit 3202, and may further include a read only memory unit (ROM) 3203.

The storage unit 320 may also include a program/utility 3204 having a set (at least one) of program modules 3205, such program modules 3205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 330 may be one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 30 may also communicate with one or more external devices 400 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 30, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 30 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 350. An input/output (I/O) interface 350 is connected to the display unit 340. Also, the electronic device 30 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 360. As shown, the network adapter 360 communicates with the other modules of the electronic device 30 over the bus 330. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 30, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, to name a few.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, and may also be implemented by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present application.

In an exemplary embodiment of the present application, there is also provided a computer-readable storage medium having stored thereon computer-readable instructions which, when executed by a processor of a computer, cause the computer to perform the method described in the above method embodiment section.

According to an embodiment of the present application, there is also provided a program product for implementing the method in the above method embodiment, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as JAVA, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Moreover, although the steps of the methods herein are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken into multiple step executions, etc.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

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.

Claims

1. A Universal Data Management (UDM) network element equipment fault detection method is applied to mobility associated entity (MME) network element equipment, and comprises the following steps:

2. The method of claim 1, further comprising:

obtaining an International Mobile Subscriber Identity (IMSI) number segment of the access subscriber;

3. The method of claim 1, wherein setting the granularity corresponding to the home network identifier based on a number of failures in which no response is received from the target UDM network element device to the user request comprises:

and setting the continuous failure times as the granularity.

4. The method of claim 3, further comprising:

5. The method of claim 3, further comprising:

6. The method of claim 1, wherein performing fault detection on the target UDM network element device based on the granularity comprises:

7. The method of claim 1, further comprising:

8. A universal data management UDM network element equipment fault detection device is characterized in that the device is arranged on mobility associated entity MME network element equipment, and the device comprises:

9. An electronic device, comprising:

a memory storing computer readable instructions;

a processor that reads computer readable instructions stored by the memory to perform the method of any of claims 1-7.

10. A computer-readable storage medium having computer-readable instructions stored thereon which, when executed by a processor of a computer, cause the computer to perform the method of any of claims 1-7.