Device management method and apparatus, electronic apparatus, and storage medium

Abstract

The present application relates to a device management method and apparatus, an electronic apparatus, and a storage medium. The device management method comprises: in response to a device state acquisition request initiated by a management terminal, determining a first service node, wherein the first service node is an on-line service node in a central cache area; determining first device state information of the first service node, and distributing the device state acquisition request to a second service node, wherein the second service node is determined by the first service node; acquiring second device state information of the second service node and returning target device state information comprising the first device state information and the second device state information to the management terminal. By means of the present application, the requirements of large-scale device state management are met.

Description

A device management method, apparatus, electronic device, and storage medium Technical Field

[0001] This application relates to the field of computer technology, and in particular to a device management method, apparatus, electronic device, and storage medium. Background Technology

[0002] In a device access gateway system, device status monitoring is crucial, especially in a distributed mode, where accurate statistics on the online and offline status of devices are of great significance. The statistical methods for device status in a distributed mode involve multiple technical aspects, including the total number of offline devices, the number of devices connected to each node, the number of connections for different device types, and updates to device status when a gateway node malfunctions. This is one of the key technologies for ensuring the stable operation of the device access gateway system.

[0003] However, in existing device management processes, a maximum device access limit is typically set for each node. A management service is added before the gateway cluster to manage the number of devices connected to each gateway node and to allocate gateway node information when adding new devices. With the expansion of the Internet of Things (IoT) and the dramatic increase in the number of devices, higher demands are placed on device status management and monitoring. Existing methods may no longer meet the needs of large-scale device management.

[0004] There is currently no effective solution to the problem that related technologies cannot meet the needs of large-scale equipment status management. Summary of the Invention

[0005] This embodiment provides a device management method, apparatus, electronic device, and storage medium to address the problem that related technologies cannot meet the needs of large-scale device status management.

[0006] Firstly, this embodiment provides a device management method, the method comprising:

[0007] In response to a device status acquisition request initiated by the management terminal, a first service node is determined; the first service node is an online service node connected to the central cache.

[0008] The first device status information of the first service node is determined, and the device status acquisition request is distributed to the second service node; the second service node is determined by the first service node.

[0009] Obtain the second device status information of the second service node; return the target device status information, including the first device status information and the second device status information, to the management terminal.

[0010] In some embodiments, the central cache is connected to multiple service nodes;

[0011] The step of determining the first service node in response to a device status acquisition request includes:

[0012] Synchronize the node status of multiple service nodes to the central cache area;

[0013] In response to the device status acquisition request, obtain the online service node connected to the central cache.

[0014] Based on the preset request strategy, the first service node among the online service nodes is determined.

[0015] In some embodiments, distributing the device status acquisition request to the second service node includes:

[0016] The online service nodes other than the first service node are identified as the first requesting nodes;

[0017] Determine whether the first node to be requested has responded to the device status acquisition request;

[0018] According to the preset request strategy, the online service node that has not responded to the device status request in the first request node is determined as the second service node;

[0019] The device status acquisition request is distributed to the second service node.

[0020] In some embodiments, determining whether the first node to be requested has responded to the device status acquisition request includes:

[0021] Obtain the link identifier carried in the device status acquisition request;

[0022] Obtain the cached data in the node to be requested, and determine whether the first node to be requested has received the link identifier based on the cached data.

[0023] In some embodiments, after obtaining the second device status information of the second service node, the method further includes:

[0024] A second node to be requested is determined, which includes online service nodes other than the first service node and the second service node;

[0025] According to the preset request strategy, a third service node is determined from the second requesting nodes that have not responded to the device status acquisition request.

[0026] The device status acquisition request is distributed to the third service node.

[0027] In some embodiments, the method further includes:

[0028] The device status acquisition request carries target device status information; the target device status information includes the status information of the online service node that has completed the request.

[0029] In some embodiments, the method further includes:

[0030] When the number of nodes of the second service node is zero, it stops responding to the device status acquisition request.

[0031] Secondly, this embodiment provides a device management apparatus, which includes: a service node determination module and a device information acquisition module;

[0032] The service node determination module is used to determine a first service node in response to a device status acquisition request initiated by the management terminal; the first service node is an online service node connected to the central cache; it is also used to determine the first device status information of the first service node and distribute the device status acquisition request to a second service node; the second service node is determined by the first service node.

[0033] The device information acquisition module is used to acquire the second device status information of the second service node; and return the target device status information, including the first device status information and the second device status information, to the management terminal.

[0034] Thirdly, this embodiment provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the device management method described in the first aspect above.

[0035] Fourthly, this embodiment provides a storage medium storing a computer program that, when executed by a processor, implements the device management method described in the first aspect above.

[0036] Compared with related technologies, the device management method, apparatus, electronic device, and storage medium provided in this embodiment, in response to a device status acquisition request initiated by a management terminal, determines a first service node and acquires the device status information of the first service node; then, based on the first service node, it acquires the online service nodes connected in the central cache, and among multiple online service nodes, it acquires a second service node, and then acquires the device status information of the second service node, returning the device status information to the management terminal. This avoids acquiring the device status information of multiple nodes through the server of the central cache, thereby avoiding the problem of being unable to manage the status of multiple devices when there are a large number of devices. This application determines other online service nodes through service nodes, and then determines the device status information accessed by the service nodes, meeting the needs of large-scale device status management.

[0037] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0038] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0039] Figure 1 is a hardware structure block diagram of the terminal of the device management method provided in the embodiment of this application;

[0040] Figure 2 is a flowchart of the device management method provided in an embodiment of this application;

[0041] Figure 3 is a system schematic diagram of the device status statistics method provided in this specific embodiment;

[0042] Figure 4 is a flowchart of the statistical method for device status in a distributed mode provided in this specific embodiment;

[0043] Figure 5 is a structural block diagram of the device management device provided in an embodiment of this application. Detailed Implementation

[0044] To better understand the purpose, technical solution, and advantages of this application, the application is described and illustrated below in conjunction with the accompanying drawings and embodiments.

[0045] Unless otherwise defined, the technical or scientific terms used in this application shall have the general meaning as understood by one of ordinary skill in the art to which this application pertains. Words such as “a,” “an,” “an,” “the,” “the,” and “these,” used in this application, do not indicate quantitative limitation and may be singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps or modules (units) is not limited to the listed steps or modules (units) but may include steps or modules (units) not listed, or may include other steps or modules (units) inherent to such processes, methods, products, or devices. The terms “connected,” “linked,” and “coupled,” used in this application, are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. The term “multiple” used in this application refers to two or more. The "and / or" operator describes the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: A alone, A and B simultaneously, and B alone. Typically, the character " / " indicates that the objects before and after it are in an "or" relationship. The terms "first," "second," and "third," etc., used in this application are merely for distinguishing similar objects and do not represent a specific ordering of the objects.

[0046] The method embodiments provided in this example can be executed in a terminal, computer, or similar computing device. For example, running on a terminal, FIG1 is a hardware structure block diagram of the terminal of the device management method provided in this application embodiment. As shown in FIG1, the terminal may include one or more (only one is shown in FIG1) processors 102 and a memory 104 for storing data, wherein the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA. The terminal may also include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that the structure shown in FIG1 is only illustrative and does not limit the structure of the terminal. For example, the terminal may also include more or fewer components than shown in FIG1, or have a different configuration than shown in FIG1.

[0047] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the device management method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0048] The transmission device 106 is used to receive or send data via a network. This network includes a wireless network provided by the terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 can be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0049] In a device access gateway system, device status monitoring is crucial, especially in a distributed mode, where accurate statistics on the online and offline status of devices are of great significance. This mainly includes the following aspects:

[0050] Device offline count: Accurate total number of connected devices and total number of online devices are crucial for device management within the service cluster.

[0051] Online device count per node: Once a device actively registers with a service node, all subsequent device operations require communication with that service node. However, there is a limit to the number of devices that can connect to each service node. Therefore, it's necessary to be aware of the real-time number of connected devices on each service node to achieve load balancing across the service cluster. Specifically, actively registered devices proactively initiate registration with the service. After successful registration, the service internally maintains a handle belonging to that device, which the device uses to perform various subsequent functional interactions with the service.

[0052] Access Count for Different Device Types: There are various types of devices, requiring statistical analysis of the access count for each type. For example, video surveillance equipment is mainly divided into IPCs (IP Cameras, Network Cameras) and NVRs (Network Video Recorders). An NVR can support multiple channels. An IPC consists of a network encoding module and an analog camera, representing a new generation of cameras combining traditional cameras with network technology. An NVR is the store-and-forward component of a network video surveillance system, working in conjunction with video encoders or network cameras to record, store, and forward video. Different types of devices have varying resource consumption on service nodes. Therefore, each service node must not only be aware of the number of devices connected to the current node but also the number of IPCs and NVRs connected to it.

[0053] Device status updates when a gateway node fails: When a service node fails, devices connected to that service node will re-register and re-establish connections with other nodes. During this time, device offline notifications sent by the devices to the failed service node will not be detected by the service cluster. Furthermore, in some cases, devices may not re-register with other service nodes, resulting in persistent connection failures. In this scenario, it is necessary to accurately count the real-time number of connected devices on each service node to facilitate monitoring of service node failures.

[0054] In summary, the statistical method for device status in a distributed mode involves multiple technical aspects, such as the total number of offline devices, the number of devices connected to each node, the number of connections for different device types, and the updating of device status when the gateway node is abnormal. It is one of the important technologies to ensure the stable operation of the device access gateway system.

[0055] Currently, the common approach for actively registered device access gateways is to set a maximum device access limit for each node. A management service is added before the gateway cluster to manage the number of devices connected to each gateway node and to allocate gateway node information when new devices are added. However, with the expansion of the Internet of Things (IoT) and the dramatic increase in the number of devices, higher demands are placed on device status management and monitoring, and existing methods may not be able to meet the needs of large-scale device management. Furthermore, when a gateway node fails, crashes, or scales down, the current common central caching solution requires processing the data of the abnormal node in the cache upon detection of an anomaly, which introduces latency and status errors.

[0056] Therefore, this embodiment provides a device management method to accurately count the device status of each service node in the event of gateway service node failure or scaling down in large-scale device cluster management. Figure 2 is a flowchart of the device management method provided in this embodiment. As shown in Figure 2, the process includes the following steps:

[0057] Step S210: In response to the device status acquisition request initiated by the management terminal, determine the first service node; the first service node is the online service node connected to the central cache.

[0058] When the management terminal initiates a device status acquisition request to the processor, the processor acquires the request. The management terminal can be a client that needs to manage devices or a server that needs to acquire device status; no specific limitation is made here. The processor includes the aforementioned gateway system. The central cache is connected to multiple service nodes, which can be online or offline, depending on the actual processing situation. Subsequently, based on the device status acquisition request, the processor first determines the online service nodes connected to the central cache; then, it randomly requests any one of the online service nodes, i.e., the first service node. Each online service node maintains its online service node information in the central cache through node heartbeats, and each online service node can also obtain information about other online service nodes from the central cache.

[0059] Step S220: Determine the first device status information of the first service node and distribute the device status acquisition request to the second service node; the second service node is determined by the first service node.

[0060] The processor, after determining the first service node, acquires the status information of the first device connected to the first service node. This first device status information includes the status information of all devices connected to the first service node. Each device connects to the corresponding service node via a device access module and subsequently interacts with that service node continuously. Once connected, the device's status is updated in real-time to the device status data maintained by the service node, synchronizing the device's status information to the service node in real time. After determining the first service node, the processor controls it to distribute device status acquisition requests to second service nodes. Specifically, it identifies unrequested service nodes among all online service nodes and randomly selects multiple second service nodes from among these unrequested nodes. This distribution process is then recursively repeated until a device status acquisition request is distributed to all unrequested online service nodes. When a device status acquisition request is distributed to a second service node, it carries the first device status information from the first service node.

[0061] Step S230: Obtain the second device status information of the second service node; return the target device status information, including the first device status information and the second device status information, to the management terminal.

[0062] Specifically, the processor obtains the second device status information of the devices connected to the second service node, and returns the target device status information, including the first device status information and the second device status information, to the management terminal to obtain the device status information of all devices connected to the online service node.

[0063] Through the above steps, a first service node is determined based on the device status acquisition request, and the device status information of the first service node is obtained. Subsequently, based on the first service node, online service nodes connected to the central cache are obtained, and a second service node is obtained from among multiple online service nodes. The device status information of the second service node is then obtained and returned to the management terminal. This avoids obtaining device status information from multiple nodes through the central cache server, thus preventing the inability to manage the status of multiple devices when there are a large number of devices. This application determines other online service nodes through the service node, and then determines the device status information connected to the service node, meeting the needs of large-scale device status management.

[0064] In some embodiments, the central cache is connected to multiple service nodes; in step S210, in response to a device status acquisition request, determining the first service node includes: synchronizing the node status of multiple service nodes to the central cache; in response to a device status acquisition request, acquiring the online service nodes connected to the central cache, and determining the first service node among the online service nodes according to a preset request strategy.

[0065] The central cache connects to multiple service nodes, and these service nodes are connected to multiple devices. The node status of these service nodes is synchronized to the central cache. Specifically, node status includes online and offline. When a service node comes online, its online status is synchronized to the central cache; when a service node goes offline, its offline status is synchronized to the central cache. Upon receiving a device status retrieval request, the central cache retrieves the online service nodes connected to it and determines the first service node among them. If there is only one online service node, it is directly designated as the first service node. If there are multiple online service nodes, a preset request strategy determines the first service node. Further, the preset request strategy can be simple random sampling, random number table method, stratified sampling method, random number decision method, etc., and is not specifically limited here. Preferably, the number of first service nodes is set to one.

[0066] The central cache provided in the above embodiment is connected to multiple service nodes, and multiple service nodes are connected to multiple devices. By obtaining the online service nodes connected to the central cache, the first service node among the online service nodes is determined. This is beneficial for distributing device status acquisition requests to other online service nodes based on the first service node, and for directly obtaining the accessed device status information from the service nodes, without having to synchronize the device status information to the central cache, thereby improving the efficiency and reliability of large-scale device management.

[0067] In some embodiments, step S220, distributing the device status acquisition request to the second service node, includes:

[0068] Step S221: Identify the online service nodes other than the first service node as the first request node; determine whether the first request node has responded to the device status acquisition request.

[0069] Further, determining whether the first node to be requested has responded to the device status acquisition request includes: acquiring the link identifier carried in the device status acquisition request; acquiring the cached data in the node to be requested, and determining whether the first node to be requested has received the link identifier based on the cached data.

[0070] Once the first service node is determined, all online service nodes connected to the central cache, excluding the first service node, are designated as the first requesting nodes. Then, a second service node distributing the device status acquisition request is identified from among these first requesting nodes. Subsequently, it is determined whether the first requesting node has received a device status acquisition request, i.e., by obtaining the link identifier carried in the device status acquisition request and checking whether the cached data in the requesting node includes the link identifier, thereby determining whether the first requesting node has responded to the device status acquisition request.

[0071] Step S222: According to the preset request strategy, the online service node that has not responded to the device status request in the first request node is identified as the second service node; the device status acquisition request is distributed to the second service node.

[0072] Specifically, according to the preset request strategy, namely the random selection method in the aforementioned embodiments, a second service node is determined from the first request node, and the device status acquisition request is distributed to the second service node.

[0073] Through the above steps, the processor randomly determines multiple second service nodes from the first unrequested nodes, and then distributes the device status acquisition request to the second service nodes, thereby avoiding the repeated distribution of the device status acquisition request to multiple service nodes, which helps to improve the efficiency of acquiring device status.

[0074] In some embodiments, after obtaining the second device status information of the second service node in step S230, the method further includes: determining a second request node, which includes online service nodes other than the first and second service nodes; determining a third service node among the second request nodes that have not responded to the device status acquisition request according to a preset request strategy; and distributing the device status acquisition request to the third service node.

[0075] When the number of first and second service nodes is less than the number of online service nodes, request distribution needs to be performed again. The second request node is obtained from the online service nodes, that is, the node from which the request needs to be distributed. Then, according to the preset request strategy, the third service node is determined from the second request node, and the device status acquisition request is distributed to the third service node to obtain the device status information of the third service node.

[0076] The above scheme distributes device status acquisition requests to all online service nodes connected to the central cache, thereby improving the completeness of device status acquisition.

[0077] In some embodiments, the device status acquisition request carries target device status information; the target device status information includes the status information of the online service node that has completed the request.

[0078] In the process of distributing device status retrieval requests, the device status retrieval request carries all device status information of the completed requests, thereby avoiding the need to retrieve device status information from the central cache and reducing the processing burden of the central cache.

[0079] In some embodiments, the device management method further includes: stopping responding to device status acquisition requests when the number of nodes of the second service node is zero.

[0080] When the number of nodes in the second service node is zero, that is, when the total number of nodes in the first and second service nodes is equal to the number of online service nodes, it means that the device status information of all online service nodes has been obtained. At this time, there is no need to respond to the device status acquisition request, thus saving processing resources.

[0081] The present embodiment will be described and explained below through specific examples.

[0082] In this embodiment, each service node maintains its own device access information; each service node maintains a heartbeat with the central cache or central management service, and the service node goes offline if the heartbeat is lost. Each service node can obtain information on all currently online nodes. When a device status acquisition request is sent to any service node, that service node not only obtains its own device status information, but also simultaneously obtains the device status information of multiple other online service nodes. Each service node recursively goes through the above process until it obtains data from all online service nodes.

[0083] Figure 3 is a system schematic diagram of the device status statistics method provided in this specific embodiment. Referring to Figure 3, the system includes: a central cache, multiple service nodes, and multiple devices; wherein, each service node includes a device status statistics module, a node status maintenance module, and a device access module, and the node status maintenance modules of the multiple service nodes are connected to the central cache. Multiple devices access the service nodes through the device access modules; here, the devices are set as cameras, but can also be other devices that require status monitoring. When the device status statistics module in service node 1 receives a device status statistics request sent by the management terminal, it obtains the node's own status data and distributes the request to service node n. Service node 1 connects to multiple devices such as device 1, device 2... device n; service node n connects to multiple devices such as device 4, device 5... device n.

[0084] Furthermore, the device connects to a service node via the device access module and will continuously interact with that node. After connection, the device updates its status to the device status data maintained by the service node. Each service node maintains its own node status information in the central cache via node heartbeat. Each service node can obtain information on all currently online service nodes from the central cache. When a device status statistics request is received, it randomly requests a service node, which obtains its own device status data and distributes the request to other online service nodes to obtain their device status data. Finally, the device status data of all online nodes is aggregated and returned. When distributing requests, it obtains information on all currently unrequested nodes, randomly selects multiple nodes to request, and obtains the request results for each. The central cache here is the central cache area in the aforementioned embodiment; service node 1 is the first service node in the aforementioned embodiment, and service node n is the second service node in the aforementioned embodiment.

[0085] Figure 4 is a flowchart of the device status statistics method in a distributed mode provided in this specific embodiment. As shown in Figure 4, the device status statistics method includes the following steps:

[0086] S101, when the management terminal requests device status statistics, it will request any gateway service node. Specifically, the device status statistics request will carry or generate a globally unique link ID. A service node receives the device status statistics request. Specifically, the link ID here is the link identifier in the aforementioned embodiment. The device status statistics request is the device status acquisition request in the aforementioned embodiment.

[0087] S102: Upon receiving a request, each service node checks its local cache to determine if the link ID for this request has already been used to initiate a request, thus filtering duplicate requests. If it is a duplicate request, the current request is terminated. If this is the first time a request has been made to this node, the link ID is added to the service node's local cache, with the cache duration equal to the request timeout by default.

[0088] S103, the service node obtains device status data from its own cache. Specifically, it obtains the total number of devices from each manufacturer and model connected to each node, the number of online devices, and other information, and simultaneously distributes requests.

[0089] S104, perform request distribution. Before distribution, obtain all currently active service nodes from the central cache, and the requested node information carried in the device status statistics request, thereby obtaining the active nodes that have not yet been requested, namely the first and second requested nodes in the aforementioned embodiment. Randomly select multiple requested nodes, namely the second service node in the aforementioned embodiment (the number of requested nodes can be adjusted through configuration). If the number of requested nodes is 0, distribution stops; if the number of requested nodes is greater than 0, assemble the request data and distribute the request, that is, request the device status data of other service nodes and obtain the device status data results.

[0090] S105, the device status statistics obtained in step S103 and step S104 are summarized and returned. The summarized device status statistics are the target device status information in the aforementioned embodiment.

[0091] It should be noted that the steps shown in the above process or in the flowchart of the accompanying figures can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0092] This embodiment also provides a device management apparatus for implementing the above embodiments and preferred embodiments; details already described will not be repeated. The terms "module," "unit," "subunit," etc., used below refer to combinations of software and / or hardware that perform a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0093] Figure 5 is a structural block diagram of the device management device provided in the embodiment of this application. As shown in Figure 5, the device includes: a service node determination module 10 and a device information acquisition module 20.

[0094] The service node determination module 10 is used to determine a first service node in response to a device status acquisition request initiated by the management terminal; the first service node is an online service node in the central cache area; it is also used to determine the first device status information of the first service node and distribute the device status acquisition request to a second service node; the second service node is determined by the first service node.

[0095] The device information acquisition module 20 is used to acquire the second device status information of the second service node; and return the target device status information, including the first device status information and the second device status information, to the management terminal.

[0096] It should be noted that the above modules can be functional modules or program modules, and can be implemented through software or hardware. For modules implemented through hardware, the above modules can reside in the same processor; or the above modules can be located in different processors in any combination.

[0097] This embodiment also provides an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0098] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0099] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0100] S1, in response to the device status acquisition request initiated by the management terminal, determines the first service node; the first service node is the online service node in the central cache area.

[0101] S2, determine the first device status information of the first service node, and distribute the device status acquisition request to the second service node; the second service node is determined by the first service node.

[0102] S3, obtain the second device status information of the second service node; return the target device status information, including the first device status information and the second device status information, to the management terminal.

[0103] It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated in this embodiment.

[0104] Furthermore, in conjunction with the device management methods provided in the above embodiments, this embodiment can also provide a storage medium for implementation. The storage medium stores a computer program; when executed by a processor, the computer program implements any of the device management methods described in the above embodiments.

[0105] It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. All other embodiments derived by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.

[0106] Obviously, the accompanying drawings are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar situations based on these drawings without any creative effort. Furthermore, it is understood that although the work done in this development process may be complex and lengthy, for those skilled in the art, certain design, manufacturing, or production modifications made based on the technical content disclosed in this application are merely conventional technical means and should not be considered as insufficient disclosure of this application.

[0107] The term "embodiment" in this application refers to a specific feature, structure, or characteristic described in connection with an embodiment that may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily imply the same embodiment, nor does it imply that it is mutually exclusive with or independent of other embodiments. It will be clearly or implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0108] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of patent protection. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the appended claims.

Claims

1. A method for managing equipment, characterized in that, The method includes: In response to a device status acquisition request initiated by the management terminal, a first service node is determined; the first service node is an online service node connected to the central cache. The first device status information of the first service node is determined, and the device status acquisition request is distributed to the second service node; the second service node is determined by the first service node. Obtain the second device status information of the second service node; return the target device status information, including the first device status information and the second device status information, to the management terminal.

2. The equipment management method according to claim 1, characterized in that, The central cache area is connected to multiple service nodes; The step of determining the first service node in response to a device status acquisition request includes: Synchronize the node status of multiple service nodes to the central cache area; In response to the device status acquisition request, obtain the online service node connected to the central cache. Based on the preset request strategy, the first service node among the online service nodes is determined.

3. The equipment management method according to claim 1, characterized in that, The process of distributing the device status acquisition request to the second service node includes: The online service nodes other than the first service node are identified as the first requesting nodes; Determine whether the first node to be requested has responded to the device status acquisition request; According to the preset request strategy, the online service node that has not responded to the device status request in the first request node is determined as the second service node; The device status acquisition request is distributed to the second service node.

4. The equipment management method according to claim 3, characterized in that, The step of determining whether the first node to be requested has responded to the device status acquisition request includes: Obtain the link identifier carried in the device status acquisition request; Obtain the cached data in the node to be requested, and determine whether the first node to be requested has received the link identifier based on the cached data.

5. The equipment management method according to claim 1, characterized in that, After obtaining the second device status information of the second service node, the process further includes: A second node to be requested is determined, which includes online service nodes other than the first service node and the second service node; According to the preset request strategy, a third service node is determined from the second requesting nodes that have not responded to the device status acquisition request. The device status acquisition request is distributed to the third service node.

6. The equipment management method according to claim 1, characterized in that, The method further includes: The device status acquisition request carries target device status information; the target device status information includes the status information of the online service node that has completed the request.

7. The equipment management method according to claim 1, characterized in that, The method further includes: When the number of nodes of the second service node is zero, it stops responding to the device status acquisition request.

8. An equipment management device, characterized in that, The device includes: a service node determination module and a device information acquisition module; The service node determination module is used to determine a first service node in response to a device status acquisition request initiated by the management terminal; the first service node is an online service node connected to the central cache; it is also used to determine the first device status information of the first service node and distribute the device status acquisition request to a second service node; the second service node is determined by the first service node. The device information acquisition module is used to acquire the second device status information of the second service node; and return the target device status information, including the first device status information and the second device status information, to the management terminal.

9. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the device management method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the device management method according to any one of claims 1 to 7.

Images