Terminal Abnormality Repair Method, Device, System, Storage Medium and Electronic Device

Abstract

The present invention relates to a method, device, system, storage medium and electronic device for repairing terminal anomalies. According to the status information of each gateway node in the gateway cluster, it is determined that the gateway service status of the first gateway node is abnormal. When the gateway service status of the first gateway node is abnormal, the number information of the terminal devices connected to the first gateway node is obtained from a preset database according to the first node identifier of the first gateway node, and the reconnection time required for the terminal devices to reconnect to the second gateway node is determined. After the reconnection time, it is further determined whether there are terminal devices with abnormal connection status according to the connection status of the terminal devices after reconnection, avoiding inaccurate detection of the terminal connection status caused by gateway anomalies and affecting the operation of normal services. At the same time, by repairing the terminal devices with abnormal status after reconnection, the terminal devices with abnormal connection are accurately identified, and the repair efficiency of the terminal devices is improved.

Description

Technical Field

[0001] The present invention relates to the field of terminal connection, and in particular, to a method, apparatus, system, storage medium, and electronic device for repairing terminal anomalies. Background Art

[0002] In the prior art, in order to ensure the confidentiality of software development, a gateway is usually used as a relay to implement the docking between the service end and the terminal. The gateway receives the TCP connection application of the terminal and reports the connection status to the service end. The service end receives the terminal status message and processes it. When the terminal connection is abnormal, the gateway reports it to the service end in time to repair the terminal. However, when the gateway is abnormal, it is easy to cause inaccurate detection of the terminal connection status and affect the normal operation of the service end. Summary of the Invention

[0003] Embodiments of the present application provide a method, apparatus, system, storage medium, and electronic device for repairing terminal anomalies, which can timely detect the gateway status and repair the abnormal terminal devices in time. The technical solutions are as follows:

[0004] In a first aspect, embodiments of the present application provide a method for repairing terminal anomalies, including the following steps:

[0005] Obtain the status information of each gateway node in the gateway cluster; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; the status information of the gateway node is used to indicate whether the gateway service status of the gateway node is abnormal;

[0006] If the gateway service status of the first gateway node is abnormal, obtain the first node identifier of the first gateway node;

[0007] According to the first node identifier, obtain the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtain the reconnection time required for the terminal devices to reconnect to the second gateway node according to the quantity information;

[0008] After the reconnection time, obtain the connection status information of the reconnected terminal devices. If there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

[0009] In a second aspect, embodiments of the present application provide a device for repairing terminal anomalies, including:

[0010] A gateway status acquisition module, configured to acquire the status information of each gateway node in a gateway cluster; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; the status information of the gateway node is used to determine whether the gateway service status of the gateway node is abnormal;

[0011] A first node identifier acquisition module, configured to acquire a first node identifier of the first gateway node if the gateway service status of the first gateway node is abnormal;

[0012] A reconnection time acquisition module, configured to acquire the quantity information of the terminal devices connected to the first gateway node from a preset database according to the first node identifier, and acquire the reconnection time required for the terminal devices to reconnect to the second gateway node according to the quantity information;

[0013] A repair module, configured to acquire the connection status information of the reconnected terminal devices after the reconnection time, and if there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

[0014] In a third aspect, an embodiment of the present application provides a service system, including a gateway cluster, a monitoring module, and at least one terminal device; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device;

[0015] The monitoring module acquires the status information of each gateway node in the gateway cluster, and when the gateway service status of the first gateway node is abnormal, acquires the first node identifier of the first gateway node; according to the first node identifier, acquires the quantity information of the terminal devices connected to the first gateway node from a preset database, and acquires the reconnection time required for the terminal devices to reconnect to the second gateway node according to the quantity information; after the reconnection time, acquires the connection status information of the reconnected terminal devices, and if there are terminal devices with abnormal connection status, repairs the terminal devices with abnormal connection status.

[0016] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the terminal exception repair method described in any one of the above are implemented.

[0017] In a fifth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, and when the processor executes the computer program, the steps of the terminal exception repair method described in any one of the above are implemented.

[0018] In an embodiment of the present application, based on the status information of each gateway node in the gateway cluster, it is determined that the gateway service status of the first gateway node is abnormal. When the gateway service status of the first gateway node is abnormal, the number information of the terminal devices connected to the first gateway node is obtained from a preset database according to the first node identifier of the first gateway node, and the reconnection time required for the terminal devices to reconnect to the second gateway node is determined. After the reconnection time, whether there are terminal devices with abnormal connection status is determined according to the connection status of the reconnected terminal devices, avoiding inaccurate detection of the terminal connection status caused by gateway abnormalities and affecting the operation of normal services. At the same time, by repairing the terminal devices with abnormal status after reconnection, the terminal devices with abnormal connection are accurately identified, and the repair efficiency of the terminal devices is improved.

[0019] For better understanding and implementation, the present invention will be described in detail below with reference to the accompanying drawings. Brief Description of the Drawings

[0020] Figure 1 Schematic diagram of an application scenario of a terminal exception repair method according to an embodiment of the present invention;

[0021] Figure 2 Flowchart of a terminal exception repair method according to an embodiment of the present invention;

[0022] Figure 3 Schematic diagram of the structure of a terminal exception repair device according to an embodiment of the present invention;

[0023] Figure 4 Schematic diagram of the structure of a service system according to an embodiment of the present invention;

[0024] Figure 5 Schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Detailed Embodiments

[0025] To make the objectives, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

[0026] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts belong to the scope of protection of the embodiments of the present application.

[0027] The terms used in the embodiments of the present application are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present application. The singular forms "a", "the", and "said" used in the embodiments of the present application and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0028] When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims. In the description of the present application, it should be understood that the terms "first", "second", "third", etc. are used only to distinguish similar objects and do not have to be used to describe a specific order or sequence, nor can they be construed as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to specific circumstances.

[0029] In addition, in the description of the present application, unless otherwise specified, "a number of" means two or more. "And / or" describes the relationship between associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0030] Those skilled in the art can understand that the "client", "terminal", and "terminal device" used in this application include both devices with a wireless signal receiver that only has the ability to receive and no transmission ability, and devices with receiving and transmitting hardware that have the receiving and transmitting hardware capable of two-way communication on a two-way communication link. Such devices may include: cellular or other communication devices such as personal computers, tablet computers, etc., which have a single-line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service), which can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant), which may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar, and / or GPS (Global Positioning System) receiver; conventional laptop and / or palm computers or other devices, which are conventional laptop and / or palm computers or other devices with and / or including a radio frequency receiver. The "client", "terminal", and "terminal device" used here can be portable, transportable, installed in a vehicle (air, sea, and / or land), or suitable for and / or configured to operate locally, and / or operate in a distributed manner at any other location on the earth and / or in space. The "client", "terminal", and "terminal device" used here can also be a communication terminal, an Internet access terminal, a music / video playback terminal, for example, it can be a PDA, MID (Mobile Internet Device), and / or a mobile phone with music / video playback function, or can also be a smart TV, a set-top box, etc.

[0031] Please refer to Figure 1 , Figure 1 which is a schematic diagram of a service system provided for an embodiment of this application. The service system includes a gateway cluster 100, a terminal device 200, and a service end 300; among them, the terminal device 200 and the service end 300 can perform data interaction through the gateway cluster 100.

[0032] The gateway cluster 100 may include multiple gateway nodes, where each gateway node is connected to at least one terminal device 200. The gateway cluster 100 is used to dock with the terminal devices, and the terminal devices can access the service background through the gateway service of the gateway nodes. The TCP connection of the terminal devices terminates at the gateway cluster, thereby ensuring the security of the service system. During this process, the connection status of the terminal device 200 is maintained by the gateway cluster 100. When the connection status of the terminal device 200 changes, the gateway cluster 100 generates a connection status message and sends it to the service end 300.

[0033] The terminal device 200 may be the end where the user to be served by this service system is located. The terminal device 200 may be electronic devices such as a smart phone, a smart interactive tablet, and a personal computer.

[0034] The service end 300 can receive the connection status message of the terminal device 200 forwarded by the gateway cluster and perform corresponding service processing. For example, it can determine whether the terminal device 200 is powered on according to the connection status of each terminal device 200, and display the power-on and power-off status of each terminal device.

[0035] However, in the above process, when a gateway node fails, such as exiting the gateway service, at this time, if a terminal device shuts down, the gateway cluster 100 will not be able to notify the service end 300 in time, resulting in the status of the terminal device displayed by the service end being inconsistent with the actual status of the terminal device, affecting the normal operation of the corresponding service of the service end 300.

[0036] In the prior art, when it is necessary to confirm whether a terminal device is abnormally connected, usually a detection tool is used to load and traverse all terminal devices, and the terminal devices are used to send connection requests to the gateway nodes. Whether the terminal device is abnormally connected is determined according to whether the gateway nodes respond, and the abnormally connected terminal devices are repaired.

[0037] However, the above confirmation process often needs to be triggered manually, and the repair work lags behind the user's perception, affecting the user experience; moreover, each service needs to develop its own detection tool, which has a high cost, and the method of batch detection is likely to cause a large performance overhead to the gateway cluster.

[0038] Therefore, in view of the above problems, as Figure 1 shown, the embodiment of the present application provides a method for repairing terminal anomalies, including the following steps:

[0039] S101: Obtain the status information of each gateway node in the gateway cluster;

[0040] The gateway cluster can include one or more gateway nodes, where the gateway nodes can be used to provide network connection services for terminal devices. The gateway cluster can be used to obtain the connection status information of the terminal devices, generate a notification message, and send it to the service end, so that the service end can display the connection status of the terminal devices according to the notification message, thereby facilitating the service end to execute corresponding service functions according to the connection status of the terminal devices.

[0041] In an embodiment of the present application, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device;

[0042] The status information is used to determine the gateway service status of the gateway node, where the gateway service status can include normal operation, exiting the gateway service, or heartbeat timeout.

[0043] Specifically, Zookeeper can be used to establish connections with each gateway node in the gateway cluster, monitor the status of each gateway node in real time, and obtain the status information of each gateway node; Zookeeper is a distributed and open-source program coordination service, which can be used to provide functions such as configuration management, naming service, distributed lock, and cluster management. In an embodiment of the present application, Zookeeper is used to dynamically sense the status of each gateway node in the gateway cluster to implement the management of the gateway cluster.

[0044] Among them, the status information is used to determine whether the gateway service status of the gateway node is abnormal, and the gateway service status can include normal operation, exiting the gateway service, or heartbeat timeout.

[0045] In one embodiment, after obtaining the status information of each gateway node in the gateway cluster, the following steps are further included:

[0046] If the status information of the first gateway node is the status of exiting the gateway service, it is determined that the gateway service status of the first gateway node is abnormal.

[0047] After the communication connection between the gateway node and the terminal device is successful, network anomalies may occur, such as network jitter, congestion, and network disconnection. However, the gateway node and the terminal device cannot know that there is a current network anomaly, which results in that although the two ends still maintain a connection state, they actually cannot communicate effectively, which not only affects data transmission but also occupies communication resources. Therefore, in the prior art, a heartbeat mechanism is usually introduced to periodically send heartbeat messages between the gateway node and the terminal device. For example, the terminal device sends a heartbeat message 1 to the gateway node. If the network is good, the gateway node will quickly send back a heartbeat message 2 to the terminal device. If the terminal device does not receive the heartbeat feedback from the gateway node within the threshold time, that is, the heartbeat times out, it is considered that the communication connection is unavailable.

[0048] When the status information of the first gateway node indicates a heartbeat timeout, a secondary detection can be performed on it to further determine whether the gateway service status of the first gateway node is abnormal. Specifically, after obtaining the status information of each gateway node in the gateway cluster, the following steps are further included:

[0049] If the status information of the first gateway node indicates a heartbeat timeout status, use multiple network nodes to initiate a connection request to the first gateway node. If all the multiple network nodes fail to connect, confirm that the gateway service status of the first gateway node is abnormal.

[0050] Among them, there is at least one network node. For example, there can be 3 network nodes; the multiple network nodes can be multiple network nodes with different network paths. Specifically, the multiple network nodes can be multiple slave nodes in a certain cluster.

[0051] Initiating a connection request to the first gateway node can be sending a ping command to the first network node. The ping command can be used to detect the network connectivity and analyze the network speed. In the embodiments of the present application, by receiving the data returned by the first gateway node according to the ping command, it is determined whether the gateway service status of the first gateway node is abnormal.

[0052] In the embodiments of the present application, using multiple network nodes with different network paths to confirm whether the gateway service status of the first gateway node is abnormal can avoid misjudging the gateway service status of the first gateway node due to abnormal individual network paths, affecting the operation of normal services, and improving the detection efficiency.

[0053] S102: If the gateway service status of the first gateway node is abnormal, obtain the first node identifier of the first gateway node;

[0054] Specifically, when the gateway service status of the first gateway node is to exit the gateway service, it is determined that the gateway service status of the first gateway node is abnormal.

[0055] The first node identifier is the identifier corresponding to the first gateway node in the gateway cluster, and can be used to determine the first gateway node from the gateway cluster. In one embodiment, the first node identifier can be the ID of the first gateway node.

[0056] S103: According to the first node identifier, obtain the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtain the reconnection time required for the terminal devices to reconnect to the second gateway node according to the quantity information;

[0057] The preset database stores information such as multiple node identifiers and the quantity and device models of the terminal devices connected to the gateway nodes corresponding to the node identifiers.

[0058] The quantity information is used to determine the quantity of terminal devices connected to the first gateway node.

[0059] The reconnection time is the time required for all terminal devices connected to the first gateway node to be connected to the second gateway node. The reconnection time can be determined according to the quantity of terminal devices connected to the first gateway node and / or the time when the gateway node exits the gateway service.

[0060] S104: After the reconnection time, obtain the connection status information of the reconnected terminal devices. If there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

[0061] Specifically, a timer with a corresponding duration can be generated according to the reconnection time. After confirming that the gateway service status of the first gateway node is abnormal, trigger this timer to start timing. The timing duration is the reconnection time required for the terminal devices to reconnect to the second gateway node. During this reconnection time, do not repair the gateway node with abnormal gateway service status until all terminal devices connected to the first gateway node are connected to the second gateway node.

[0062] After the reconnection time, the connection status information of the reconnected terminal devices can be obtained by using the second gateway node. Among them, the connection status information can include information such as the ID, type, address, ID of the access service, identifier of the access service, status of the terminal device, and update time of the terminal device.

[0063] For the terminal devices that are still abnormal after reconnection, determine that the terminal devices are abnormal and repair the abnormal terminal devices.

[0064] When repairing the terminal devices with abnormal connection status, the abnormal information and device information such as the connection port of the terminal device can be obtained, and a preset repair program can be automatically executed to perform repair operations on the terminal device. Or, in another embodiment, the steps of repairing the terminal devices with abnormal connection status specifically include:

[0065] Obtain the device information of the terminal devices with abnormal connection status, generate an abnormal notification message and send it to the service end, so that the service end repairs the terminal devices with abnormal connection status according to the abnormal notification message.

[0066] When the service end receives the abnormal notification message, it can automatically execute a preset repair program to perform repair operations on the terminal device, or it can also be used to prompt the user with a prompt message for repairing the terminal device with abnormal connection status. Among them, the prompt message can include the device information and abnormal information of the terminal device with abnormal connection status to prompt the user to repair it in time and improve the user experience.

[0067] By waiting for all terminal devices to be connected to the second gateway node before repairing the terminal devices with abnormal connection status, it is possible to avoid affecting the fault judgment of terminal devices due to abnormal gateway node status and improve the efficiency of repairing abnormal terminal devices.

[0068] In an embodiment of the present application, according to the status information of each gateway node in the gateway cluster, it is determined that the gateway service status of the first gateway node is abnormal. When the gateway service status of the first gateway node is abnormal, the quantity information of the terminal devices connected to the first gateway node is obtained from a preset database according to the first node identifier of the first gateway node, and the reconnection time required for the terminal devices to reconnect to the second gateway node is determined. After the reconnection time, it is further determined whether there are terminal devices with abnormal connection status according to the connection status of the terminal devices after reconnection, so as to avoid inaccurate detection of the terminal connection status caused by gateway abnormalities and affect the operation of normal services. At the same time, by repairing the terminal devices with abnormal status after reconnection, the terminal devices with abnormal connection are accurately identified, and the repair efficiency of terminal devices is improved.

[0069] In one embodiment, the terminal abnormality repair method of the present application can be applied to a monitoring module. The monitoring module can subscribe to the status information of each gateway node through a zookeeper cluster. When the monitoring module discovers that the status of a gateway node is abnormal, it executes the above steps S102 - S104 to obtain the terminal devices with abnormal connection status and perform repairs.

[0070] The monitoring module may include a main node and multiple slave nodes connected to the main node. Among them, the main node can be used to execute the terminal abnormality repair method of the present application. When the obtained status information of the first gateway node is a heartbeat timeout status, the slave nodes of the monitoring module have different network paths and can be used as the above network nodes to initiate a connection request to the first gateway node, so as to implement a secondary detection of the gateway service status of the first gateway node and improve the accuracy of judging the gateway heartbeat timeout abnormality.

[0071] Generally, since the terminal devices are connected to the gateway cluster through TCP long connections, but the TCP connection status of the terminals needs to be notified to the upper-layer service end by the gateway cluster. For example, when a certain terminal device is powered on and connected to the gateway node through TCP, the gateway cluster then tells the upper-layer service end about the connection status of this terminal device.

[0072] When the terminal device shuts down, the TCP connection between the terminal device and the gateway node is disconnected, and the gateway cluster can notify the upper-layer service end. However, if the gateway node exits the gateway service, at this time, the TCP connection of the terminal device will also be disconnected, but the gateway cluster cannot notify the service end in time. At this time, the monitoring module can obtain the terminal status of the previous gateway and generate a disconnection notice of the terminal device to report to the service end, so that the service end can promptly display the connection status of the terminal to the user and perform repairs in a timely manner. Therefore, in one embodiment, before obtaining the status information of each gateway node in the gateway cluster, it further includes:

[0073] Receiving the connection status information of the at least one terminal device sent by the gateway cluster and storing it in a preset database;

[0074] The step of obtaining the connection status information of the at least one terminal device specifically includes:

[0075] Reading the connection status information of the at least one terminal device stored in the preset database.

[0076] Among them, the connection status information may include information such as the ID, type, address, ID of the access service, identifier of the access service, status of the terminal device, and update time of the terminal device.

[0077] When the gateway node is abnormal, the connection status information of at least one terminal device stored in the database can be read to generate the connection status information of the terminal device to the service end. The service end does not need to care whether the connection status information is generated by the gateway cluster or the monitoring module, and the service end does not need to make any changes. It can still display the connection status of the terminal according to the usual process and repair the terminal device with abnormal connection, improving the service processing efficiency of the service end.

[0078] As Figure 3 shown, the present application also provides a terminal exception repair device, including:

[0079] A gateway status acquisition module 401, configured to acquire the status information of each gateway node in the gateway cluster; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; the status information of the gateway node is used to determine whether the gateway service status of the gateway node is abnormal;

[0080] A first node identifier acquisition module 402, configured to acquire the first node identifier of the first gateway node if the gateway service status of the first gateway node is abnormal;

[0081] The reconnect time acquisition module 403 is configured to obtain, according to the first node identifier, the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtain the reconnect time required for the terminal devices to reconnect to the second gateway node according to the quantity information;

[0082] The repair module 404 is configured to, after the reconnect time, obtain the connection status information of the reconnected terminal devices, and if there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

[0083] It should be noted that when the terminal exception repair device provided in the above embodiment executes the terminal exception repair method, only the above-mentioned division of each functional module is used for illustration. In actual application, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the terminal exception repair device and the terminal exception repair method provided in the above embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment and will not be elaborated here.

[0084] As Figure 4 shown, an embodiment of the present application further provides a service system, including a gateway cluster 501, a monitoring module 503, and at least one terminal device 502;

[0085] Wherein, the gateway cluster 501 includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device 502;

[0086] The monitoring module 503 obtains the status information of each gateway node in the gateway cluster 501. When the gateway service status of the first gateway node is abnormal, it obtains the first node identifier of the first gateway node; according to the first node identifier, it obtains the quantity information of the terminal devices 502 connected to the first gateway node from a preset database, and obtains the reconnect time required for the terminal devices 502 to reconnect to the second gateway node according to the quantity information; after the reconnect time, it obtains the connection status information of the reconnected terminal devices 502, and if there are terminal devices 502 with abnormal connection status, it repairs the terminal devices 502 with abnormal connection status.

[0087] In one embodiment, the service system further includes a service end 504;

[0088] The gateway cluster 501 obtains the connection status information of the terminal devices 502 connected to each gateway node and sends it to the service end 504;

[0089] The service end 504 displays the connection status of the terminal devices 502 connected to each network gateway node according to the connection status information of the terminal devices 502 connected to each network gateway node.

[0090] The service system according to the embodiment of the present application can be used to execute the terminal exception repair method of the present application. For details not disclosed in this embodiment, please refer to the method embodiment of the present application.

[0091] This embodiment provides an electronic device, which can be used to execute all or part of the steps of the terminal exception repair method according to the embodiment of the present application. For details not disclosed in this embodiment, please refer to the method embodiment of the present application.

[0092] Please refer to Figure 5 , Figure 5 FIG. is a schematic structural diagram of the electronic device provided by the embodiment of the present application. The electronic device 600 can be, but is not limited to, a combination of one or more of various servers, personal computers, laptop computers, smart phones, tablet computers, and other devices.

[0093] In a preferred embodiment of the present application, the electronic device 600 includes a memory 601, at least one processor 602, at least one communication bus 603, and a transceiver 604.

[0094] Those skilled in the art should understand that Figure 5 the structure of the electronic device shown does not constitute a limitation on the embodiment of the present application. It can be a bus structure or a star structure. The electronic device 600 may further include more or fewer other hardware or software than shown in the figure, or different component arrangements.

[0095] In some embodiments, the electronic device 600 is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits, programmable gate arrays, digital processors, and embedded devices, etc. The electronic device 600 may further include a client device, and the client device includes, but is not limited to, any electronic product that can perform human-computer interaction with the client through a keyboard, mouse, remote control, touchpad, or voice control device, etc. For example, a personal computer, a tablet computer, a smart phone, a digital camera, etc.

[0096] It should be noted that the electronic device 600 is only an example, and other existing or future possible electronic products that can be adapted to the present application should also be included in the protection scope of the present application and are included herein by reference.

[0097] In some embodiments, a computer program is stored in the memory 601, and when the computer program is executed by the at least one processor 602, all or part of the steps in the terminal exception repair method according to the embodiments are implemented. The memory 601 includes a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically-erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc memories, magnetic disk memories, tape memories, or any other computer-readable medium capable of carrying or storing data.

[0098] In some embodiments, the at least one processor 602 is the control core of the electronic device 600, connecting various components of the entire electronic device 600 through various interfaces and lines, and by running or executing programs or modules stored in the memory 601, and invoking data stored in the memory 601, to perform various functions of the electronic device 600 and process data. For example, when the at least one processor 602 executes the computer program stored in the memory, all or part of the steps of the terminal exception repair method described in the embodiments of the present application are implemented; or all or part of the functions of the terminal exception repair device are implemented. The at least one processor 602 may be composed of integrated circuits. For example, it may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits with the same or different functions packaged, including a combination of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips, etc.

[0099] In some embodiments, the at least one communication bus 603 is configured to implement connection communication between the memory 601 and the at least one processor 602, etc.

[0100] The electronic device 600 may further include various sensors, a Bluetooth module, a Wi-Fi module, etc., which will not be elaborated here.

[0101] This embodiment provides a computer-readable storage medium, on which a computer program is stored. The instructions are adapted to be loaded and executed by a processor to perform the terminal exception repair method of the embodiments of the present application. For the specific execution process, reference can be made to the specific description of the method embodiments, which will not be elaborated here.

[0102] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are only illustrative. The components 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 to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present application. Those of ordinary skill in the art can understand and implement it without creative efforts.

[0103] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0104] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the specified functions in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0105] The above are only the embodiments of the present application and are not used to limit the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for repairing terminal anomalies, characterized in that, Including the following steps: Obtain the status information of each gateway node in the gateway cluster; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; the status information of the gateway node is used to determine whether the gateway service status of the gateway node is abnormal; If the gateway service status of the first gateway node is abnormal, obtain the first node identifier of the first gateway node; According to the first node identifier, obtain the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtain the reconnection time required for all terminal devices to reconnect to the second gateway node according to the quantity information; After the reconnection time, obtain the connection status information of the reconnected terminal devices. If there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

2. The terminal exception repair method according to claim 1, wherein After obtaining the status information of each gateway node in the gateway cluster, the following steps are further included: If the status information of the first gateway node is the gateway service exit status, determine that the gateway service status of the first gateway node is abnormal.

3. The terminal exception repair method according to claim 1, wherein, After obtaining the status information of each gateway node in the gateway cluster, the following steps are further included: If the status information of the first gateway node is the heartbeat timeout status, use multiple network nodes to initiate connection requests to the first gateway node. If all the multiple network nodes fail to connect, confirm that the gateway service status of the first gateway node is abnormal.

4. The terminal exception repair method according to claim 1, characterized in that After obtaining the first node identifier of the first gateway node, the following steps are further included: Obtain the connection status information of the at least one terminal device, generate a notification message and send it to the service end, so that the service end can display the connection status of the terminal device according to the notification message.

5. The terminal exception repair method according to claim 4, wherein, Before obtaining the status information of each gateway node in the gateway cluster, it further includes: Receive the connection status information of the at least one terminal device sent by the gateway cluster and store it in a preset database; The step of obtaining the connection status information of the at least one terminal device specifically includes: Read the connection status information of the at least one terminal device stored in the preset database.

6. The terminal exception repair method according to claim 1, wherein The step of repairing the terminal device with abnormal connection status specifically includes: Obtain the device information of the terminal device with abnormal connection status, generate an abnormal notification message and send it to the service end, so that the service end can repair the terminal device with abnormal connection status according to the abnormal notification message.

7. A terminal abnormal repair device, characterized in that, Including: A gateway status acquisition module, configured to obtain the status information of each gateway node in the gateway cluster; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; the status information of the gateway node is used to determine whether the gateway service status of the gateway node is abnormal; A first node identifier acquisition module, configured to obtain the first node identifier of the first gateway node if the gateway service status of the first gateway node is abnormal; A reconnect time acquisition module, configured to obtain, according to the first node identifier, the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtain the reconnect time required for all terminal devices to reconnect to the second gateway node according to the quantity information; A repair module, configured to, after the reconnect time, obtain the connection status information of the terminal devices after reconnection, and if there are terminal devices with abnormal connection status, repair the terminal devices with abnormal connection status.

8. A service system, characterized in that, It includes a gateway cluster, a monitoring module and at least one terminal device; wherein, the gateway cluster includes at least a first gateway node and a second gateway node, and the first gateway node is connected to at least one terminal device; The monitoring module obtains the status information of each gateway node in the gateway cluster. When the gateway service status of the first gateway node is abnormal, it obtains the first node identifier of the first gateway node; according to the first node identifier, it obtains the quantity information of the terminal devices connected to the first gateway node from a preset database, and obtains the reconnect time required for all terminal devices to reconnect to the second gateway node according to the quantity information; after the reconnect time, it obtains the connection status information of the terminal devices after reconnection, and if there are terminal devices with abnormal connection status, repairs the terminal devices with abnormal connection status.

9. The service system according to claim 8, wherein It further includes a service end; The gateway cluster obtains the connection status information of the terminal devices connected to each gateway node and sends it to the service end; The service end displays the connection status of the terminal devices connected to each gateway node according to the connection status information of the terminal devices connected to each gateway node.

10. A computer-readable storage medium storing a computer program thereon, characterized in that: When the computer program is executed by a processor, it implements the steps of the terminal exception repair method described in any one of claims 1-6.

11. An electronic device, characterized in that: It includes a memory, a processor and a computer program stored in the memory and executable by the processor. When the processor executes the computer program, it implements the steps of the terminal exception repair method described in any one of claims 1-6.

Images