Universal data management (UDM) network element equipment fault detection method, device and electronic equipment
By setting up a routing proxy node between the MME network element device and the UDM network element device and setting the granularity based on the number of failures, the fault detection problem caused by network complexity is solved, and the cost efficiency balance and accurate detection are achieved.
Patent Information
- Application Number
- CN202210908125.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-29
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-07-29
AI Technical Summary
When 5G users are attached to the 4G network, the interconnection of MME network element devices and UDM network element devices leads to complexity of the network, making it difficult to take into account the cost and efficiency of fault detection.
By setting up a routing proxy node between the MME network element device and the UDM network element device, and setting the granularity corresponding to the home network identification code based on the number of failures that the target UDM network element device has not received to respond to the user request, the failure detection is performed. .
It reduces the cost of fault detection, ensures the efficiency of fault detection, and does not require additional network management equipment to accurately and promptly detect the status of UDM network element equipment.
Smart Images

Figure CN115278744B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and specifically to a method, device and electronic equipment for detecting faults of universal data management (UDM) network element equipment. Background Art
[0002] In the deployment of 4G / 5G core networks, when 5G users attach to the 4G network, the MME network element device and the UDM network element device communicate with each other through the S6a interface to complete authentication authorization, location update, etc. This feature will lead to the complexity of the network, which will bring various difficulties to the MME network element device for fault detection of the UDM network element device, making it difficult to balance the cost and efficiency of the UDM network element device fault detection. Summary of the invention
[0003] One purpose of the present application is to provide a data processing method, device, electronic device and storage medium, which reduce the cost of fault detection while ensuring the efficiency of fault detection.
[0004] According to one aspect of an embodiment of the present application, a universal data management (UDM) network element device fault detection method is disclosed, which is applied to a mobility association entity (MME) network element device. The method includes:
[0005] In response to a user request of an access user, sending the user request to a routing proxy node;
[0006] 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;
[0007] Setting the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request;
[0008] Based on the granularity, fault detection is performed on the target UDM network element device.
[0009] According to one aspect of an embodiment of the present application, a universal data management (UDM) network element device fault detection device is disclosed, which is provided in a mobility association entity (MME) network element device, and the device includes:
[0010] a sending module, configured to respond to a user request of an access user and send the user request to a routing proxy node;
[0011] a forwarding module configured to forward 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;
[0012] A granularity module configured to set the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request;
[0013] The detection module is configured to perform fault detection on the target UDM network element device based on the granularity.
[0014] According to one aspect of an embodiment of the present application, an electronic device is disclosed, comprising: a memory storing computer-readable instructions; and a processor reading the computer-readable instructions stored in the memory to execute any one of the methods described in the above claims.
[0015] According to one aspect of an embodiment of the present application, a computer program medium is disclosed, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the method described in any one of the above claims.
[0016] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the above various optional implementations.
[0017] In the embodiment of the present application, by setting a routing proxy node between the MME network element device and the UDM network element device, and transferring through the routing proxy node, the network complexity between the MME network element device and the UDM network element device can be reduced when the 5G user is attached to the 4G network. In addition, by setting the granularity corresponding to the home network identification code based on the number of failures of not receiving the response of the target UDM network element device to the user request, and performing fault detection on the target UDM network element device based on the granularity, the MME network element device only needs to manage the association between the home network identification code and the UDM network element device to detect the status of the UDM network element device, and there is no need to set up additional network management equipment between the MME network element device and the UDM network element device, which reduces the cost of fault detection while ensuring the efficiency of fault detection.
[0018] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0019] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] 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.
[0021] Figure 1 A flowchart of a universal data management (UDM) network element device fault detection method according to an embodiment of the present application is shown.
[0022] Figure 2 A schematic diagram of UDM network element device fault detection according to an embodiment of the present application is shown.
[0023] Figure 3 A schematic diagram of UDM network element device fault detection according to an embodiment of the present application is shown.
[0024] Figure 4 A block diagram of a device for detecting faults of UDM network element equipment using data management according to an embodiment of the present application is shown.
[0025] Figure 5 A hardware diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0026] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these example embodiments are provided so that the description of the present application will be more comprehensive and complete and the concepts of the example embodiments will be fully conveyed to those skilled in the art. The accompanying drawings are only schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted.
[0027] In addition, the described features, structures or characteristics may be combined in one or more example embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the example embodiments of the present application. However, those skilled in the art will appreciate that the technical solution of the present application may be practiced while omitting one or more of the specific details, or other methods, components, steps, etc. may be adopted. In other cases, known structures, methods, implementations or operations are not shown or described in detail to avoid obscuring the present application and making the various aspects of the present application obscure.
[0028] Some of the blocks shown in the accompanying drawings are functional entities that do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0029] The present application provides a method for detecting faults in a unified data management (UDM) network element device, which is applied to a mobility management entity (MME) network element device in a 5G application scenario to detect whether a fault occurs in the UDM network element device.
[0030] Figure 1 The flowchart of the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application is shown. The execution subject of the method is an MME network element device. The method includes:
[0031] Step S110: In response to a user request of an access user, the user request is sent to a routing proxy node;
[0032] Step S120: forwarding the user request to the target UDM network element device through the routing proxy node, wherein the target UDM network element device is associated with the home network identification code of the access user;
[0033] Step S130: setting the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request;
[0034] Step S140: Perform fault detection on the target UDM network element device based on the granularity.
[0035] Specifically, when a 5G user is attached to a 4G network, the MME network element device and the UDM network element device communicate with each other through the S6a interface to complete authentication authorization, location update, etc. Since the MME network element device and the UDM network elements in each region are directly interconnected through the S6a interface, the network will be too complex and difficult to manage. Therefore, 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.
[0036] After the user accesses the MME network element device, the user request is sent to the MME network element device. The MME network element device responds to the user request of the accessed user and sends the user request to the DRA. Then the DRA forwards the user request to the target UDM network element device associated with the home network identity HNI (Home Network Identity) of the accessed user. The home network identity is used to identify the network to which the corresponding user belongs. In addition, different home network identities are associated with different UDM network element devices, so the home network identity provides the MME with the ability to identify and detect the status of the UDM network element device during the interaction with the UDM network element device.
[0037] The embodiment of the present application reduces the network complexity between the MME network element device and the UDM network element device when the 5G user is attached to the 4G network through the DRA transfer. But at the same time, there is a new problem: under the setting of DRA transfer, since the MME network element device and the target UDM network element device communicate indirectly, the MME network element device cannot sense whether the target UDM network element device is in a normal state or in a faulty state. When the target UDM network element device fails, the MME network element device will continue to send requests to the DRA to send user requests to the target UDM network element device, but will not receive a normal response, resulting in a large increase in invalid information in the network.
[0038] Since the MME network element device cannot sense whether the target UDM network element device is in a normal state or a faulty state under the setting of DRA forwarding, in the embodiment of the present application, after sending the user request to DRA, the MME network element device monitors the number of failures of not receiving the response of the target UDM network element device to the user request. Then, based on the number of failures monitored, the granularity corresponding to the home network identification code is set. Among them, the granularity is used to describe the number of times the UDM network element device associated with it, that is, the target UDM network element device, has not responded to the user request forwarded by the DRA.
[0039] The larger the granularity, the more times the target UDM network element device fails to respond to the user request forwarded by the DRA, and the greater the possibility that the target UDM network element device fails; conversely, the smaller the granularity, the fewer times the target UDM network element device fails to respond to the user request forwarded by the DRA, and the smaller the possibility that the target UDM network element device fails. Therefore, in the embodiment of the present 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, thereby ensuring the efficiency of fault detection.
[0040] It can be seen that in the embodiment of the present application, by setting a routing proxy node between the MME network element device and the UDM network element device and transferring through the routing proxy node, the network complexity between the MME network element device and the UDM network element device can be reduced when the 5G user is attached to the 4G network. In addition, by setting the granularity corresponding to the home network identification code based on the number of failures of not receiving the response of the target UDM network element device to the user request, and performing fault detection on the target UDM network element device based on the granularity, the MME network element device only needs to manage the association between the home network identification code and the UDM network element device to detect the status of the UDM network element device, and there is no need to set up additional network management equipment between the MME network element device and the UDM network element device, which reduces the cost of fault detection while ensuring the efficiency of fault detection.
[0041] In one embodiment, the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application further includes:
[0042] Obtain the International Mobile Subscriber Identity (IMSI) number segment of the access user;
[0043] The home network identifier is extracted from the IMSI number segment.
[0044] In this embodiment, after the user accesses the MME network element device, the MME network element device obtains the International Mobile Subscriber Identity (IMSI) number segment of the corresponding accessed user. The IMSI number segment is a non-repeated identification code in the cellular network used to distinguish different users in the cellular network. Generally, the user equipment stores the IMSI number segment in a 64-bit field and sends it to the MME network element device.
[0045] After the MME network element device obtains the IMSI number segment of the access user, it extracts the home network identifier HNI from it.
[0046] In one embodiment, the granularity corresponding to the home network identification code is set based on the number of failures of not receiving a response from the target UDM network element device to the user request, including:
[0047] Based on the failure event of not receiving the response made by the target UDM network element device to the user request and the success event of receiving the response made by the target UDM network element device to the user request, obtaining the number of consecutive failures of the target UDM network element device within a preset time period;
[0048] Set the number of consecutive failures as granularity.
[0049] In this embodiment, the MME network element device monitors the failure event of not receiving the response made by the target UDM network element device to the user request, and monitors the success event of receiving the response made by the target UDM network element device to the user request. Then, based on the monitored failure events and success events, the number of consecutive failures within a preset time period is determined.
[0050] Optionally, the monitored failure events and success events both have time information. According to the time information corresponding to the events, the failure events and success events are sorted, and then the continuous failure events within the preset time period can be screened out according to the event sequence, so as to determine the number of continuous failures within the preset time period. Then, the determined number of continuous failures is set as the granularity corresponding to the home network identification code.
[0051] Optionally, monitoring failure events and success events within a preset time period are monitored. In this process, each time a failure event is detected, the number of consecutive failures is increased by one; a success event indicates that the number of consecutive failures stops increasing. That is, once a success event is detected, the number of consecutive failures stops increasing.
[0052] In this embodiment, the reason why the number of consecutive failures is set as the granularity for fault detection is that when the target UDM network element device does not respond to the user request, it does not necessarily mean that the target UDM network element device has failed. This situation occurs occasionally, mostly due to communication quality or other factors; the continuous occurrence of this situation can more effectively indicate that the target UDM network element device has failed. Therefore, the MME network element device sets the number of consecutive failures as the granularity for fault detection, thereby improving the accuracy of fault detection.
[0053] In one embodiment, the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application further includes:
[0054] When a success event is detected within the preset time period, the number of consecutive failures is reset to 0.
[0055] In this embodiment, once the MME network element device detects a success event within a preset time period, the accumulated number of consecutive failures is reset to 0. In this embodiment, after the accumulated number of consecutive failures is reset to 0, if a failure event is detected again, the number of consecutive failures is accumulated again from 0.
[0056] For example: the preset time period is [t1, t2] with a duration of T.
[0057] At time t1, the number of consecutive failures is set to 0. That is, the granularity corresponding to the home network identification code is set to 0.
[0058] Starting from time t1, with 0 as the starting point, every time a failure event is detected in which a response to a user request from the target UDM network element device corresponding to the home network identification code is not received, the number of consecutive failures / granularity is increased by one.
[0059] At time t3, a successful event of receiving a response from the target UDM network element device corresponding to the home network identification code to the user request is detected, and the number of consecutive failures / granularity is reset to 0. Wherein, time t3 is between time t1 and time t2.
[0060] Continuing from time t3, the number of consecutive failures / granularity starts again from 0, and the number of consecutive failures / granularity is increased by one every time a failure event is detected in which a response to a user request from the target UDM network element device corresponding to the home network identification code is not received.
[0061] This logic is continuously executed until time t2, when the current stage of processing is temporarily completed.
[0062] In one embodiment, the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application further includes:
[0063] When a success event is detected within the preset time period, the preset time period is reset and the number of consecutive failures is reset to 0.
[0064] In this embodiment, once the MME network element device detects a success event within the preset time period, it resets the accumulated number of consecutive failures to 0 and also resets the preset time period. Resetting the preset time period refers to resetting the start time of the preset time period and maintaining the duration of the preset time period unchanged.
[0065] For example: the preset time period is [t1, t2] with a duration of T.
[0066] At time t1, the number of consecutive failures is set to 0. That is, the granularity corresponding to the home network identification code is set to 0.
[0067] Starting from time t1, with 0 as the starting point, every time a failure event is detected in which a response to a user request from the target UDM network element device corresponding to the home network identification code is not received, the number of consecutive failures is increased by one. That is, the granularity is increased by one.
[0068] At time t3, a successful event of receiving a response from the target UDM network element device corresponding to the home network identification code to the user request is detected, the number of consecutive failures / granularity is reset to 0, and the preset time period is reset to [t3, t4] with a duration of T. Among them, time t3 is between time t1 and time t2, and time t2 is between time t3 and time t4.
[0069] Starting from time t3, the number of consecutive failures / granularity starts again from 0, and the number of consecutive failures / granularity is increased by one every time a failure event is detected in which a response to a user request from the target UDM network element device corresponding to the home network identification code is not received.
[0070] This logic is continuously executed. If the number of consecutive failures / granularity and the preset time period are not reset again, the current stage of processing is temporarily completed until time t4.
[0071] In one embodiment, the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application further includes:
[0072] At the end of the preset time period, the preset time period is reset and the number of consecutive failures is reset to 0.
[0073] In this embodiment, once the MME network element device detects that the preset time period has ended, the preset time period is reset and the accumulated number of consecutive failures is reset to zero.
[0074] For example: the preset time period is [t1, t2] with a duration of T.
[0075] In the process from time t1 to time t2, the number of consecutive failures is accumulated and reset according to the detected failure events and success events, and the granularity corresponding to the home network identification code is updated in real time according to the number of consecutive failures.
[0076] At time t2, no matter what the specific value of the number of consecutive failures / granularity is, and whether the number of consecutive failures / granularity has been reset, the number of consecutive failures / granularity is reset to 0, and the preset time period is reset to [t2, t3] with a duration of T.
[0077] In the process from time t2 to time t3, the number of consecutive failures is accumulated and reset according to the detected failure events and success events, and the granularity corresponding to the home network identification code is updated in real time according to the number of consecutive failures.
[0078] In one embodiment, fault detection is performed on a target UDM network element device based on granularity, including:
[0079] When the granularity is greater than a preset threshold, the target UDM network element device is determined to be in a fault state;
[0080] When the granularity is less than or equal to a preset threshold, the target UDM network element device is determined to be in a normal state.
[0081] In this embodiment, the MME network element device presets a threshold value for the granularity, and determines whether the target UDM network element device is faulty or not according to the relative size between the granularity and the preset threshold value.
[0082] 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. When the granularity corresponding to the home network identification code is less than or equal to the preset threshold, the target UDM network element device associated with the home network identification code is determined to be in a normal state.
[0083] In one embodiment, the universal data management (UDM) network element device fault detection method provided in the embodiment of the present application further includes:
[0084] Acquire a secondary UDM network element device, wherein the secondary UDM network element device is associated with a home network identification code, and a priority of the secondary UDM network element device is lower than a priority of the target UDM network element device;
[0085] After confirming that the target UDM network element device is in a faulty state, the routing agent node is instructed to forward the user request to the secondary UDM network element device.
[0086] In this embodiment, the home network identification code is associated with multiple UDM network element devices, and these 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 with the highest priority. That is, in general, the target UDM network element device is the UDM network element device with the highest priority.
[0087] After confirming that the target UDM network element device is in a faulty state, the MME network element device instructs the DRA to forward the user request to a secondary UDM network element device with a lower priority than the target UDM network element device to avoid sending a large number of invalid messages due to the failure of the UDM network element device.
[0088] In one embodiment, after discovering a faulty UDM network element device, the MME network element device notifies other MME network element devices of information about the faulty UDM network element device, thereby preventing other MME network element devices from sending information to the faulty UDM network element device and reducing the occurrence of overall network authentication failures.
[0089] Figure 2 and Figure 3 A schematic diagram of UDM network element device fault detection in an embodiment of the present application is shown.
[0090] See also Figure 2 and Figure 3 In one embodiment, a routing DRA is deployed between an MME network element device and a UDM network element device. In response to a user request of an access user, the MME network element device sends the user request to the DRA. 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 of the access user. Different UDM network element devices are set with different priorities. Generally, the user request is forwarded to the UDM network element device with the highest priority.
[0091] The MME network element device maintains a cache table as shown in the figure. The cache table records the priority, granularity and status of the UDM network element devices associated with different home network identification codes. Among them, 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 identification code is greater than or equal to 5, the status of the UDM network element device associated with the home network identification code is changed from normal to faulty.
[0092] Specifically, for any specific home network identification code, within a preset time period of duration T, the granularity of the associated UDM network element device is first set to 0. The failure event of not receiving a response from the target UDM network element device to the user request within the preset time period is monitored, the number of consecutive failures is confirmed, and the number of consecutive failures is used as the granularity. Once a successful event of receiving a response from the target UDM network element device to the user request is detected, the number of consecutive failures / granularity is reset to 0.
[0093] When the granularity of the home network identification code reaches 5, it is confirmed that the UDM network element device associated therewith has failed, and its status is changed from normal to failed.
[0094] Figure 4 A block diagram of a universal data management (UDM) network element device fault detection device according to an embodiment of the present application is shown. The device is provided in a mobility association entity (MME) network element device, and the device includes:
[0095] a sending module, configured to respond to a user request of an access user and send the user request to a routing proxy node;
[0096] a forwarding module configured to forward 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;
[0097] A granularity module configured to set the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request;
[0098] The detection module is configured to perform fault detection on the target UDM network element device based on the granularity.
[0099] In an exemplary embodiment of the present application, the device is configured as follows:
[0100] Obtain the IMSI number segment of the access user;
[0101] The home network identification code is extracted from the IMSI number segment.
[0102] In an exemplary embodiment of the present application, the device is configured as follows:
[0103] Based on a failure event of not receiving a response from the target UDM network element device to the user request and a success event of receiving a response from the target UDM network element device to the user request, obtaining a number of consecutive failures of the target UDM network element device within a preset time period;
[0104] The number of consecutive failures is set as the granularity.
[0105] In an exemplary embodiment of the present application, the device is configured as follows:
[0106] When the success event is detected within the preset time period, the number of consecutive failures is reset to 0.
[0107] In an exemplary embodiment of the present application, the device is configured as follows:
[0108] At the end of the preset time period, the preset time period is reset, and the number of consecutive failures is reset to 0.
[0109] In an exemplary embodiment of the present application, the device is configured as follows:
[0110] When the granularity is greater than a preset threshold, determining the target UDM network element device as a fault state;
[0111] When the granularity is less than or equal to the preset threshold, the target UDM network element device is determined to be in a normal state.
[0112] In an exemplary embodiment of the present application, the device is configured as follows:
[0113] Acquire a secondary UDM network element device, wherein the secondary UDM network element device is associated with the home network identification code, and a priority of the secondary UDM network element device is lower than a priority of the target UDM network element device;
[0114] After confirming that the target UDM network element device is in a fault state, instruct the routing agent node to forward the user request to the secondary UDM network element device.
[0115] Reference below Figure 5 The electronic device 30 according to the embodiment of the present application is described. Figure 5 The electronic device 30 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0116] like Figure 5 As shown, the electronic device 30 is in the form of a general computing device. The components of the electronic device 30 may include but are not limited to: at least one processing unit 310, at least one storage unit 320, and a bus 330 connecting different system components (including the storage unit 320 and the processing unit 310).
[0117] The storage unit stores program codes, which can be executed by the processing unit 310, so that the processing unit 310 performs the steps according to various exemplary embodiments of the present invention described in the description of the exemplary method described above in this specification. For example, the processing unit 310 can perform the following steps: Figure 1 The steps shown in .
[0118] The storage unit 320 may include a readable medium in the form of a volatile storage unit, 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 .
[0119] 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 may include an implementation of a network environment.
[0120] Bus 330 may represent 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.
[0121] The electronic device 30 may also communicate with one or more external devices 400 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 30, and / or may communicate with any device that enables the electronic device 30 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 350. The input / output (I / O) interface 350 is connected to a display unit 340. Furthermore, the electronic device 30 may also 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 a network adapter 360. As shown, the network adapter 360 communicates with other modules of the electronic device 30 via a bus 330. It should be understood that, although not shown in the figure, 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.
[0122] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods 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 flash drive, a mobile 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 terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.
[0123] In an exemplary embodiment of the present application, a computer-readable storage medium is further provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the method described in the above method embodiment.
[0124] According to one embodiment of the present application, a program product for implementing the method in the above method embodiment is also provided, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited to this. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.
[0125] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.
[0126] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0127] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
[0128] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages such as JAVA, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a 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 type 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).
[0129] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.
[0130] In addition, although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.
[0131] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods 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 flash drive, a mobile 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 implementation methods of the present application.
[0132] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the appended claims.
Claims
1. A method for detecting faults in a universal data management (UDM) network element device, characterized in that: Applied to a mobility association entity MME network element device, the method includes: In response to a user request of an access user, sending the user request to a routing proxy 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 the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request; Based on the granularity, performing fault detection on the target UDM network element device; The granularity corresponding to the home network identification code is set based on the number of failures of not receiving a response from the target UDM network element device to the user request, including: obtaining the number of consecutive failures of the target UDM network element device within a preset time period based on a failure event of not receiving a response from the target UDM network element device to the user request and a success event of receiving a response from the target UDM network element device to the user request; and setting the number of consecutive failures to the granularity.
2. The method according to claim 1, characterized in that The method further comprises: Obtain the International Mobile Subscriber Identity (IMSI) number segment of the access user; The home network identification code is extracted from the IMSI number segment.
3. The method according to claim 1, characterized in that The method further comprises: When the success event is detected within the preset time period, the number of consecutive failures is reset to 0.
4. The method according to claim 1, characterized in that: The method further comprises: At the end of the preset time period, the preset time period is reset, and the number of consecutive failures is reset to 0.
5. The method according to claim 1, characterized in that Based on the granularity, fault detection is performed on the target UDM network element device, including: When the granularity is greater than a preset threshold, determining the target UDM network element device as a fault state; When the granularity is less than or equal to the preset threshold, the target UDM network element device is determined to be in a normal state.
6. The method according to claim 1, characterized in that The method further comprises: Acquire a secondary UDM network element device, wherein the secondary UDM network element device is associated with the home network identification code, and a priority of the secondary UDM network element device is lower than a priority of the target UDM network element device; After confirming that the target UDM network element device is in a fault state, instruct the routing agent node to forward the user request to the secondary UDM network element device.
7. A universal data management (UDM) network element equipment fault detection device, characterized in that: The device is provided in a mobility association entity MME network element device, and the device includes: a sending module, configured to respond to a user request of an access user and send the user request to a routing proxy node; a forwarding module configured to forward 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; A granularity module configured to set the granularity corresponding to the home network identification code based on the number of failures of not receiving a response from the target UDM network element device to the user request; A detection module configured to perform fault detection on the target UDM network element device based on the granularity; The granularity corresponding to the home network identification code is set based on the number of failures of not receiving a response from the target UDM network element device to the user request, including: obtaining the number of consecutive failures of the target UDM network element device within a preset time period based on a failure event of not receiving a response from the target UDM network element device to the user request and a success event of receiving a response from the target UDM network element device to the user request; and setting the number of consecutive failures to the granularity.
8. An electronic device, characterized in that: include: a memory storing computer-readable instructions; The processor reads the computer readable instructions stored in the memory to execute the method according to any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that: Computer readable instructions are stored thereon, and when the computer readable instructions are executed by a processor of a computer, the computer is caused to execute the method of any one of claims 1-6.
