Fault determination method and device, electronic equipment and storage medium

Abstract

The invention provides a fault determination method and device, electronic equipment and a storage medium, relates to the technical field of communication, and solves the technical problem of network fault misjudgment or missed judgment caused by non-uniform network fault judgment modes in related technologies. The method comprises the following steps: acquiring an identification feature of at least one heartbeat message transmitted by a target device, wherein the identification feature is a content added by the target device in the heartbeat message; determining the transmission state of the heartbeat message based on the identification feature of the heartbeat message; and based on the transmission state of the heartbeat message, determining whether a target network has a fault, the target network being a network to which the target device belongs.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault determination method, device, electronic device and storage medium. Background Art

[0002] At present, there are several ways to determine whether a network has a fault: First, when the network function repository function (NRF) detects that a network element has a fault, it can send a fault status notification to other network elements to notify other network elements of the fault status of the network element, thereby determining that the network has a fault. Second, a network element can determine that the other network element has a fault based on the response status code and error code sent by the other network element, thereby determining that the network has a fault.

[0003] However, in the above methods, the methods for determining network failures are not uniform, and the determination results generated by different channels and different methods may be inconsistent, which may cause misjudgment or omission of network failures. Summary of the invention

[0004] The present application provides a fault determination method, device, electronic device and storage medium, which solves the technical problem that the method for determining network faults in the related art is not unified, resulting in misjudgment or omission of network faults.

[0005] In a first aspect, the present application provides a fault determination method, comprising: obtaining an identification feature of at least one heartbeat message transmitted by a target device, the identification feature being content added by the target device in the heartbeat message; based on the identification feature of the heartbeat message, determining a transmission status of the heartbeat message; based on the transmission status of the heartbeat message, determining whether there is a fault in a target network, the target network being a network to which the target device belongs.

[0006] In a second aspect, the present application provides a fault determination device, including: an acquisition module and a determination module;

[0007] The acquisition module is used to obtain the identification feature of at least one heartbeat message transmitted by the target device, and the identification feature is the content added by the target device in the heartbeat message; the determination module is used to determine the transmission status of the heartbeat message based on the identification feature of the heartbeat message; the determination module is also used to determine whether there is a fault in the target network based on the transmission status of the heartbeat message, and the target network is the network to which the target device belongs.

[0008] In a third aspect, the present application provides an electronic device, comprising: a processor and a memory configured to store processor executable instructions; wherein the processor is configured to execute the instructions to implement any one of the optional fault determination methods in the first aspect above.

[0009] In a fourth aspect, the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions in the computer-readable storage medium are executed by an electronic device, the electronic device is enabled to execute any one of the optional fault determination methods in the first aspect described above.

[0010] The fault determination method, device, electronic device and storage medium provided by the present application can enable the electronic device to obtain the identification feature of at least one heartbeat message transmitted by the target device. Since the identification feature is the content added by the target device in the heartbeat message, the electronic device can accurately and effectively determine the transmission status of the heartbeat message based on the identification feature, specifically whether it is abnormal or normal. Afterwards, the electronic device can determine whether there is a fault in the target network (i.e., the network to which the target device belongs) based on the transmission status of the heartbeat message. In the present application, the electronic device can determine whether there is a fault in the network based on a unified method by using the heartbeat message as a means of monitoring the network quality, and can avoid misjudgment / omission of network faults, thereby achieving healthy operation of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.

[0012] Figure 1 A schematic diagram of a network architecture of a 5G communication system provided in an embodiment of the present application;

[0013] Figure 2 A schematic diagram of a network architecture of a fault determination system provided in an embodiment of the present application;

[0014] Figure 3 A flowchart of a fault determination method provided in an embodiment of the present application;

[0015] Figure 4 A flowchart of another fault determination method provided in an embodiment of the present application;

[0016] Figure 5 A flowchart of another fault determination method provided in an embodiment of the present application;

[0017] Figure 6 A flowchart of another fault determination method provided in an embodiment of the present application;

[0018] Figure 7 A flowchart of another fault determination method provided in an embodiment of the present application;

[0019] Figure 8 A flowchart of another fault determination method provided in an embodiment of the present application;

[0020] Fig. 9 A schematic diagram of a scenario for network disaster recovery provided in an embodiment of the present application;

[0021] Fig.10 A schematic diagram of a safety protection scenario provided in an embodiment of the present application;

[0022] Fig.11 A schematic diagram of the structure of a fault determination device provided in an embodiment of the present application;

[0023] Fig.12 A schematic diagram of the structure of another fault determination device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] The fault determination method, device, electronic device and storage medium provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0025] The terms "first" and "second" in the specification and drawings of this application are used to distinguish different objects rather than to describe the specific order of the objects. For example, the first heartbeat message and the second heartbeat message are used to distinguish different heartbeat messages rather than to describe the specific order of the heartbeat messages.

[0026] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0027] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0028] The term "and / or" used in the present application includes using either or both methods at the same time.

[0029] In the description of the present application, unless otherwise specified, “plurality” means two or more.

[0030] Based on the description in the background technology, since the determination method of network faults in the related technology is not unified, the determination results generated by different channels and different methods may be inconsistent, which may cause misjudgment or missed judgment of network faults. Based on this, the embodiment of the present application provides a fault determination method, device, electronic device and storage medium. The electronic device uses the heartbeat message as a means of monitoring the network quality, and can determine whether there is a fault in the network in a unified manner, which can avoid misjudgment / missed judgment of network faults, thereby achieving healthy operation of the network.

[0031] The fault determination method, device, electronic device, and storage medium provided in the embodiments of the present application can be applied to a wireless communication system. For example, taking a 5G communication system as an example, Figure 1 A network architecture diagram of a 5G communication system provided in an embodiment of the present application, wherein the 5G communication system may include a user equipment (UE) 101, a radio access network (RAN) device or an access network (AN) device 102, a user plane function (UPF) 103, an access and mobility management function (AMF) 104, a session management function (SMF) 105, a policy control function (PCF) 106, an authentication server function (AUSF) 107, an NRF 108, an application function (AF) 109, a capability exposure function (NEF) 110, a unified data management (UDM) 111, and a network slice selection function (NSSF) 112, etc. UE 101 accesses the 5G network (that is, it is understood that UE 101 accesses the 5G system that can provide the 5G network) and establishes a session with the network. Then UE 101 can communicate with the function serving UE 101 (such as UPF 103, AMF 104, etc.) through (R)AN device 102. Generally, in actual applications, the connection between the above-mentioned devices or service functions can be a wireless connection or a wired connection. In order to conveniently and intuitively represent the connection relationship between the various devices, Figure 1 The implementation diagram is shown in FIG.

[0032] Among them, the (R)AN device 102 is used for UE 101 to access the network, and the (R)AN device 102 may include a base station, an evolved node base station (eNB), a next generation node basestation (gNB), a new radio base station (new radio eNB), a macro base station, a micro base station, a high-frequency base station or a transmission and reception point (TRP), a non-third generation partnership project (3GPP) access network (such as WiFi) and / or a non-3GPP interworking function (N3IWF) and other devices.

[0033] UPF 103: used to handle events related to the user plane, such as transmitting or routing data packets, detecting data packets, reporting traffic, processing quality of service (QoS), legal monitoring, storing downlink data packets, etc. In the embodiment of the present application, UPF 103 is used to receive heartbeat messages sent by UE 101 and servers included in the external data network.

[0034] AMF 104: used for connection management, mobility relations, registration management, access authentication and authorization, reachability management, and security context management.

[0035] SMF 105: used for session management (such as session establishment, modification and release), selection and control of UPF 103, selection of service and session continuity mode, and roaming services.

[0036] PCF 106: used to formulate policies, provide policy control services, and obtain contract information related to policy decisions.

[0037] AUSF 107: used to interact with UDM 111 to obtain user information and perform authentication-related functions, such as generating intermediate keys.

[0038] NRF 108: Network Function Profile for service discovery, maintaining available network function instances and the services supported by those network functions.

[0039] AF 109: interacts with the 3GPP core network to provide services or servers. For example, it can interact with NEF 110.

[0040] NEF 110: securely opens various services and capabilities provided by 3GPP network functions (including content opening or opening to third parties, etc.), converts or translates information interacting with AF 109 and information interacting with internal network functions, such as AF service identification and content 5G core network information (such as network slice selection assistance information, etc.).

[0041] UDM 111: Processes authentication information in 3GPP authentication and key negotiation mechanisms, handles user identity information, access authorization, registration and mobility management, contract management, short message management, etc.

[0042] NSSF 112: used to select a set of network slices for UE 101, determine network slice selection protocol information, and determine the AMF set serving UE 101 (AMF set refers to a collection of multiple AMFs that can serve UE 101).

[0043] Optionally, in an embodiment of the present application, each of the above-mentioned functional modules (i.e., UPF 103, AMF 104, SMF 105, PCF 106, AUSF 107, NRF 108, AF 109, NEF 110, UDM 111 and NSSF 112) can be integrated on the server to realize its functions.

[0044] Combined with the above 5G communication system architecture, Figure 2 As shown, the embodiment of the present application can deploy the electronic device 201 between the UPF 103 and the external data network (specifically, it can be a location close to the UPF 103).

[0045] Specifically, the electronic device 201 can obtain the identification characteristics of at least one heartbeat message transmitted by the target device (including UE 101 and a server included in the external data network), and determine the transmission status of the heartbeat message based on the identification characteristics of the heartbeat message, thereby determining whether there is a fault in the target network (i.e., the network to which the target device belongs).

[0046] Optionally, Figure 2 The functions of UE 101, (R)AN device 102, UPF 103, AMF 104, SMF 105, PCF 106, UDM 111 and external data network shown in the figure are the same as or similar to those described in the above embodiments and will not be repeated here.

[0047] Exemplarily, the electronic device that executes the fault determination method provided in the embodiment of the present application may be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, and a cellular phone, a personal digital assistant (PDA), an augmented reality (AR)\virtual reality (VR) device, and the embodiment of the present application does not impose any special restrictions on the specific form of the electronic device. It can interact with the user through one or more methods such as a keyboard, a touchpad, a touch screen, a remote control, voice interaction, or a handwriting device.

[0048] Optionally, the above-mentioned electronic device can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, network acceleration services (content delivery network, CDN), as well as big data and artificial intelligence platforms.

[0049] In the related art, whether there is a fault in the network can be determined through the following implementation methods.

[0050] In one implementation, it can be based on the form of NRF status notification. This implementation is applicable to direct connection networking, single channel per carrier (SCPC) networking and other modes. Specifically, AMF and SMF can subscribe to UDM status change notifications from NRF. When NRF detects that the UDM status changes from a normal state to a fault state, it triggers a fault status notification to inform AMF and SMF of the current UDM status.

[0051] Among them, AMF and SMF have the same fault detection mechanism. The following takes AMF as an example. Figure 3 As shown, including S301-S303.

[0052] S301. AMF subscribes to UDM status change notification from NRF.

[0053] S302: NRF detects that the UDM is in a fault state.

[0054] S303. NRF sends a fault status notification to AMF.

[0055] The fault status notification is used to notify the UDM that it is currently in a fault state.

[0056] In another implementation, it can be based on the form of local network function (NF) status detection. This implementation is only applicable to the direct connection networking mode. By periodically sending a hypertext transfer protocol (HTTP) Internet packet detector (PING) detection message to the target NF, it is confirmed whether the target NF is normal.

[0057] The specific implementation can be as follows Figure 4 As shown, including S401-S402.

[0058] S401. AMF sends an HTTP PING detection request to UDM.

[0059] S402: If the number of times that AMF waits for the HTTP PING response exceeds the threshold, it is determined that the UDM is in a fault state.

[0060] In another implementation, based on the form of response status code and error code, specifically, a certain network element can determine that other network elements have faults based on the response status code and error code sent by other network elements, thereby determining that a network fault exists.

[0061] The implementation method can be as follows Figure 5 As shown, it includes S501-S502.

[0062] S501. AMF sends a service request message to UDM.

[0063] S502. When UDM detects that UDM is currently in a faulty state, it sends a service failure response to AMF.

[0064] The service failure response includes a response status code and an error code. The AMF may determine that the UMD has a fault based on the response status code and the error code.

[0065] Based on this, the embodiment of the present application provides a fault determination method, such as Figure 6 As shown, the fault determination method includes S601-S603.

[0066] S601. Obtain identification features of at least one heartbeat message transmitted by a target device.

[0067] The identification feature is the content added by the target device in the heartbeat message.

[0068] It should be understood that the target device is the UE and / or a server in an external data network, and the server is a server corresponding to an application (or mobile software application, APP for short) installed in the UE.

[0069] Specifically, the UE (specifically, the application in the UE) can send a heartbeat message to the UPF via the (R)AN device (such as a base station), and then the UPF can send the heartbeat message to the server corresponding to the application.

[0070] Correspondingly, the server may also send a heartbeat message to the UPF, and then the UPF may send the heartbeat message to the UE via the (R)AN device.

[0071] Optionally, the at least one heartbeat message may come from multiple target devices or multiple accounts. The embodiment of the present application does not specifically limit the number of target devices transmitting at least one heartbeat message and the number of accounts with the at least one heartbeat message.

[0072] It is understandable that after receiving / obtaining the media packet, UPF can determine whether the media packet is a heartbeat message. If the media packet is a heartbeat message, UPF copies the heartbeat message and sends it to the electronic device, so that the electronic device can obtain the heartbeat message.

[0073] Optionally, after obtaining the media packet, UPF can perform deep packet inspection (DPI) on the media packet. If it is detected that the media packet includes a specific field (such as heart beat) or the name of the media packet is a heartbeat message / heartbeat message, UPF can determine that the media packet is a heartbeat message.

[0074] In an embodiment of the present application, after receiving the heartbeat message of a certain APP, UPF caches and copies it while forwarding it to the server corresponding to the APP normally, so as not to affect the normal communication and detection between the APP and the server.

[0075] S602: Determine the transmission status of the heartbeat message based on the identification feature of the heartbeat message.

[0076] The transmission status includes an abnormal status and a normal status.

[0077] Optionally, after receiving the heartbeat message, the UPF may also add the identification feature to the heartbeat message, and package and send it to the electronic device at preset intervals, so that the electronic device can obtain the identification feature of at least one of the above heartbeat messages.

[0078] Optionally, the above identification feature may include at least one of the following: a timestamp when the target device transmits the heartbeat message, an account identifier in the heartbeat message, an application identifier in the heartbeat message, and a sequence number in the heartbeat message.

[0079] S603: Determine whether there is a fault in the target network based on the transmission status of the heartbeat message.

[0080] The target network is the network to which the target device belongs.

[0081] In an optional implementation, when the transmission status of the heartbeat message is abnormal, the electronic device may determine that a fault exists in the target network.

[0082] In another optional implementation, when the transmission status of the heartbeat message is normal, the electronic device can determine that there is no fault in the target network.

[0083] In an embodiment of the present application, the electronic device can obtain the identification feature of at least one heartbeat message transmitted by the target device. Since the identification feature is the content added by the target device in the heartbeat message, the electronic device can accurately and effectively determine the transmission status of the heartbeat message based on the identification feature, specifically whether it is abnormal or normal. Afterwards, the electronic device can determine whether there is a fault in the target network (i.e., the network to which the target device belongs) based on the transmission status of the heartbeat message. In an embodiment of the present application, the electronic device can determine whether there is a fault in the network based on a unified method by using the heartbeat message as a means of monitoring the network quality, which can avoid misjudgment / omission of network faults, thereby achieving healthy operation of the network.

[0084] In an implementation of the embodiment of the present application, the identification feature includes a timestamp of the target device transmitting the heartbeat message. The above-mentioned determination of the transmission status of the heartbeat message based on the identification feature of the heartbeat message specifically includes step A.

[0085] Step A: When no response message corresponding to the heartbeat message is received before the target time, it is determined that the transmission state of the heartbeat message is abnormal.

[0086] The target time is a time interval threshold after the above timestamp.

[0087] It should be understood that when a response message corresponding to a heartbeat message is not received before the target time, it indicates that the heartbeat message has timed out or no reply has been received. At this time, the electronic device can easily and quickly determine that the transmission status of the heartbeat message is abnormal.

[0088] It can be understood that the above-mentioned time threshold is a period (for example, 30 minutes) negotiated between the UE (or client) and the server (or service end), and can be included in the heartbeat message.

[0089] Optionally, when a response message corresponding to the heartbeat message is received before the target time, the electronic device can determine that the transmission status of the heartbeat message is normal.

[0090] In another implementation of the embodiment of the present application, the identification feature includes an account identification and an application identification in the heartbeat message. The above-mentioned determination of the transmission status of the heartbeat message based on the identification feature of the heartbeat message specifically includes step B.

[0091] Step B: When the number of the second heartbeat messages is greater than or equal to the number threshold, determine that the transmission status of the first heartbeat message and the second heartbeat message is abnormal.

[0092] The first heartbeat message and the second heartbeat message are any two heartbeat messages in the at least one heartbeat message, and the account identifier and application identifier of the second heartbeat message are the same as those of the first heartbeat message.

[0093] It should be understood that the account identifier and application identifier of the second heartbeat message are the same as those of the first heartbeat message, indicating that the sending device (such as UE) of the second heartbeat message is the same as the sending device of the first heartbeat message, and the receiving device (such as a server) of the second heartbeat message is the same as the receiving device of the first heartbeat message.

[0094] When the number of second heartbeat messages is greater than or equal to the quantity threshold, it means that the UE or server has sent a large number of retransmission messages, which can also be understood as a large number of retransmissions of heartbeat messages. At this time, the electronic device can determine that the transmission status of these retransmitted heartbeat messages (including the first heartbeat message and the second heartbeat message) is abnormal.

[0095] Optionally, when the number of the second heartbeat messages is less than the above-mentioned number threshold, the electronic device may determine that the transmission status of the first heartbeat message and the second heartbeat message is normal.

[0096] In another implementation of the embodiment of the present application, the identification feature includes a sequence number in the heartbeat message. The above-mentioned determination of the transmission status of the heartbeat message based on the identification feature of the heartbeat message specifically includes step C.

[0097] Step C: when the sequence number included in the response message corresponding to the received heartbeat message is different from the sequence number of the heartbeat message, it is determined that the transmission status of the heartbeat message is abnormal.

[0098] It should be understood that the heartbeat message sent by the target device will carry a sequence number, and the response message received after sending the heartbeat message will also carry a sequence number, and the two sequence numbers should be the same. When the sequence number included in the response message corresponding to the received heartbeat message is different from the sequence number of the heartbeat message, it means that the sequence number of the heartbeat message during transmission is disordered, that is, the electronic device can determine that the transmission state of the heartbeat message is abnormal.

[0099] Optionally, when the sequence number included in the received response message corresponding to the heartbeat message is the same as the sequence number of the heartbeat message, the electronic device can determine that the transmission status of the heartbeat message is normal.

[0100] Combination Figure 6 ,like Figure 7 As shown, the above-mentioned determination of whether there is a fault in the target network based on the transmission status of the heartbeat message may specifically include S6031-S6033.

[0101] S6031. Determine a first quantity and a second quantity.

[0102] The first number is the number of the at least one heartbeat message, and the second number is the number of the at least one heartbeat message whose transmission status is abnormal.

[0103] S6032: Determine the ratio between the second number and the first number as the probability that a fault exists in the target network.

[0104] S6033: When the probability that a fault exists in the target network is greater than or equal to the probability threshold, determine that a fault exists in the target network.

[0105] Exemplarily, assuming that the first number is 100 and the second number is 80, the electronic device can determine that the probability of a target network failure is 80%. Also assuming that the probability threshold is 60%, the electronic device can determine that the target network failure exists.

[0106] Combination Figure 6 ,like Figure 8 As shown, after determining whether there is a fault in the target network based on the transmission status of the heartbeat message, the fault determination method provided in the embodiment of the present application also includes S604-S606.

[0107] S604: When a fault occurs in the target network, a offline notification message is sent to the UPF in the target network.

[0108] The offline notification message includes the account identifier of the target account and the application identifier of the target application, and the offline notification message is used to notify the UPF to instruct the target account to suspend the use of the target application.

[0109] It should be understood that the UPF instructing the target account to suspend the use of the target application specifically instructs the target account (or the UE corresponding to the target account) to be forcibly offline.

[0110] S605: When the target heartbeat message is received within the target duration, it is determined that a media plane network element in the target network has a fault.

[0111] The target heartbeat message includes the account identifier of the target account and the application identifier of the target application.

[0112] It can be understood that when a target heartbeat message is received in the target market, it means that the target account (or the UE corresponding to the target account) is successfully registered and a heartbeat message is sent to the UPF again. At this time, the electronic device can determine that there is a fault in the media plane network element in the target network.

[0113] Optionally, the media plane network element may include UPF and SMF, etc.

[0114] S606: When the target heartbeat message is not received within the target time period, it is determined that a control plane network element in the target network is faulty.

[0115] In an embodiment of the present application, when the target heartbeat message is not received within the target time length, it means that the target account (or the UE corresponding to the target account) cannot be re-registered and send a heartbeat message to the UPF. At this time, the electronic device can determine that there is a fault in the control plane network element in the target network.

[0116] Optionally, the control plane network element may include AMF, etc.

[0117] In an optional implementation, when the target heartbeat message is not received within the target time period, the electronic device may also determine that a fault exists in the (R)AN device (or base station) in the target network.

[0118] In the embodiment of the present application, when the electronic device determines that a network element in the target network fails or a link is interrupted, a specific technology may be selected for processing, which may specifically include network disaster recovery technology and security protection technology.

[0119] In some embodiments, Fig. 9 As shown, when an AMF (such as AMF 905) fails, the surrounding network elements (UDM 901, PCF 902, SMF 903 and (R)AN equipment 904) can select other AMFs (such as AMF 906 or AMF 907) to continue business processing.

[0120] Optionally, different AMFs may belong to different data centers (DCs).

[0121] In other embodiments, Fig.10 As shown, NF 1002 can receive the inbound message sent by the inbound network element 1001, send a pass response to the inbound network element 1001, send a rejection response to the inbound network element 1001, and discard the inbound message through the inbound signaling overload control. NF 1002 can also send a pass message to the outbound network element 1003, cache the inbound message sent by the network element 1001, and discard the inbound message through the outbound signaling overload control.

[0122] It should be understood that the above-mentioned inbound signaling overload control and outbound signaling overload control both belong to overload control strategies in security protection technology.

[0123] Optionally, the inbound network element may be a (R)AN device, and the outbound network element may be a charging gateway (CG).

[0124] The embodiment of the present application can divide the functional modules of the electronic device etc. according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0125] In the case of dividing each functional module into corresponding functional modules, Fig.11 A possible structural diagram of the fault determination device involved in the above embodiment is shown. Fig.11 As shown, the fault determination device 110 may include: an acquisition module 1101 and a determination module 1102 .

[0126] The acquisition module 1101 is used to acquire an identification feature of at least one heartbeat message transmitted by a target device, where the identification feature is content added by the target device in the heartbeat message.

[0127] The determination module 1102 is used to determine the transmission status of the heartbeat message based on the identification feature of the heartbeat message.

[0128] The determination module 1102 is further configured to determine whether a target network has a fault based on the transmission status of the heartbeat message, where the target network is the network to which the target device belongs.

[0129] Optionally, the above identification feature includes a timestamp when the target device transmits the heartbeat message.

[0130] The determination module 1102 is specifically configured to determine that the transmission status of the heartbeat message is abnormal when no response message corresponding to the heartbeat message is received before a target time, and the target time is a time after the timestamp by a time interval threshold.

[0131] Optionally, the above identification features include an account identifier and an application identifier in the heartbeat message.

[0132] Determination module 1102 is specifically used to determine that the transmission status of the first heartbeat message and the second heartbeat message is abnormal when the number of second heartbeat messages is greater than or equal to a quantity threshold, the first heartbeat message and the second heartbeat message are any two heartbeat messages among the at least one heartbeat message, and the account identifier and application identifier of the second heartbeat message are the same as those of the first heartbeat message.

[0133] Optionally, the above identification feature includes a sequence number in the heartbeat message.

[0134] The determination module 1102 is specifically configured to determine that the transmission status of the heartbeat message is abnormal when the sequence number included in the received response message corresponding to the heartbeat message is different from the sequence number in the heartbeat message.

[0135] Optionally, the determination module 1102 is specifically used to determine a first quantity and a second quantity, the first quantity being the quantity of the at least one heartbeat message, and the second quantity being the quantity of the at least one heartbeat message whose transmission status is abnormal.

[0136] The determination module 1102 is further specifically configured to determine the ratio between the second number and the first number as the probability that a fault exists in the target network.

[0137] The determination module 1102 is further specifically configured to determine that a fault exists in the target network when the probability is greater than or equal to a probability threshold.

[0138] Optionally, the fault determination device 110 further includes a sending module 1103 .

[0139] The sending module 1103 is used to send an offline notification message to the UPF in the target network when a fault occurs in the target network. The offline notification message includes the account identifier of the target account and the application identifier of the target application. The offline notification message is used to notify the UPF to instruct the target account to suspend the use of the target application.

[0140] The determination module 1102 is further configured to determine that a media plane network element in the target network has a fault when a target heartbeat message is received within a target duration, wherein the target heartbeat message includes an account identifier of the target account and an application identifier of the target application.

[0141] The determination module 1102 is further configured to determine that a control plane network element in the target network has a fault when the target heartbeat message is not received within the target time period.

[0142] In the case of an integrated unit, Fig.12 FIG. 1 is a schematic diagram showing a possible structure of the fault determination device involved in the above embodiment. Fig.12 As shown, the fault determination device 120 may include: a processing module 1201 and a communication module 1202. The processing module 1201 may be used to control and manage the actions of the fault determination device 120. The communication module 1202 may be used to support the communication between the fault determination device 120 and other entities. Fig.12 As shown, the fault determination device 120 may further include a storage module 1203 for storing program codes and data of the fault determination device 120 .

[0143] The processing module 1201 may be a processor or a controller. The communication module 1202 may be a transceiver, a transceiver circuit or a communication interface, etc. The storage module 1203 may be a memory.

[0144] When the processing module 1201 is a processor, the communication module 1202 is a transceiver, and the storage module 1203 is a memory, the processor, the transceiver, and the memory may be connected via a bus. The bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc.

[0145] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0146] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0147] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0148] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0149] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing a computer program instruction on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or may contain one or more servers, data centers and other data storage devices that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0150] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A fault determination method, characterized in that: The method comprises: Acquire an identification feature of at least one heartbeat message transmitted by a target device, where the identification feature is content added by the target device to the heartbeat message; Based on the identification feature of the heartbeat message, determining the transmission status of the heartbeat message; Based on the transmission status of the heartbeat message, it is determined whether a target network has a fault, the target network being a network to which the target device belongs.

2. The fault determination method according to claim 1, characterized in that: The identification feature includes a timestamp when the target device transmits the heartbeat message, and determining the transmission status of the heartbeat message based on the identification feature of the heartbeat message includes: When a response message corresponding to the heartbeat message is not received before a target time, it is determined that the transmission state of the heartbeat message is abnormal, and the target time is a time after the timestamp by a time interval threshold.

3. The fault determination method according to claim 1, characterized in that: The identification feature includes an account identifier and an application identifier in the heartbeat message, and determining the transmission status of the heartbeat message based on the identification feature of the heartbeat message includes: When the number of second heartbeat messages is greater than or equal to the quantity threshold, it is determined that the transmission status of the first heartbeat message and the second heartbeat message is abnormal, the first heartbeat message and the second heartbeat message are any two heartbeat messages among the at least one heartbeat message, and the account identifier and application identifier of the second heartbeat message are the same as those of the first heartbeat message.

4. The fault determination method according to claim 1, characterized in that: The identification feature includes a sequence number in the heartbeat message, and determining the transmission status of the heartbeat message based on the identification feature of the heartbeat message includes: When the sequence number included in the received response message corresponding to the heartbeat message is different from the sequence number in the heartbeat message, it is determined that the transmission status of the heartbeat message is abnormal.

5. The fault determination method according to any one of claims 1 to 4, characterized in that: The determining whether the target network has a fault based on the transmission status of the heartbeat message includes: Determine a first quantity and a second quantity, wherein the first quantity is the quantity of the at least one heartbeat message, and the second quantity is the quantity of the at least one heartbeat message in which the transmission status is abnormal; Determine the ratio between the second number and the first number as the probability that the target network has a fault; When the probability is greater than or equal to a probability threshold, it is determined that a fault exists in the target network.

6. The fault determination method according to any one of claims 1 to 4, characterized in that: The method further comprises: When the target network has a fault, sending an offline notification message to a user plane function UPF in the target network, wherein the offline notification message includes an account identifier of the target account and an application identifier of the target application, and the offline notification message is used to notify the UPF to instruct the target account to suspend the use of the target application; When a target heartbeat message is received within a target duration, it is determined that a media plane network element in the target network has a fault, the target heartbeat message including an account identifier of the target account and an application identifier of the target application; When the target heartbeat message is not received within the target time period, it is determined that a control plane network element in the target network has a fault.

7. A fault determination device, characterized in that: include: Get module and determine module; The acquisition module is used to acquire an identification feature of at least one heartbeat message transmitted by the target device, where the identification feature is content added by the target device to the heartbeat message; The determining module is used to determine the transmission status of the heartbeat message based on the identification feature of the heartbeat message; The determination module is further used to determine whether a target network has a fault based on the transmission status of the heartbeat message, and the target network is a network to which the target device belongs.

8. The fault determination device according to claim 7, characterized in that: The identification feature includes a timestamp of the target device transmitting the heartbeat message; The determination module is specifically used to determine that the transmission status of the heartbeat message is abnormal when a response message corresponding to the heartbeat message is not received before a target time, and the target time is a time after the timestamp by a time interval threshold.

9. An electronic device, characterized in that: The electronic device comprises: processor; a memory configured to store instructions executable by the processor; The processor is configured to execute the instructions to implement the fault determination method according to any one of claims 1 to 5.

10. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instructions in the computer-readable storage medium are executed by an electronic device, the electronic device is enabled to execute the fault determination method according to any one of claims 1 to 5.

Images