Linux-based edge device remote management monitoring system and method
By introducing multiple monitoring nodes and main monitoring node backup mechanisms into the remote management monitoring system of edge devices, combining virtualization technology and WebSocket connection, the problems of low efficiency of edge device management and monitoring and inconvenient failover in the existing technology are solved, and the problem of inconvenient failure in the existing technology is realized. Efficient, flexible and reliable monitoring and management.
Patent Information
- Application Number
- CN202411437822.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-15
- Publication Date
- 2024-11-12
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing remote management monitoring system for edge devices has problems such as low monitoring efficiency, slow response speed, lack of effective failover mechanism and resource management flexibility during large-scale deployment, making it difficult to meet the needs of real-time and reliability.
A remote management monitoring system for edge devices based on Linux is designed, including at least one edge management node, multiple monitoring nodes and at least one main monitoring node. The monitoring node realizes hardware direct access through the virtual host. The main monitoring node has a backup mechanism and passes through WebSocket connections perform continuous two-way data transmission and dynamically adjust edge device configuration.
It realizes efficient management and monitoring of edge devices, improves system flexibility and response speed, ensures automation and real-time performance of monitoring processes, and provides a reliable failover mechanism when the main monitoring node fails, improving monitoring tasks reasonable allocation and execution efficiency.
Smart Images

Figure CN118945150A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of remote management and monitoring of edge computing service systems, and more specifically, to a Linux-based edge device remote management and monitoring system and method. Background Art
[0002] With the rapid development of the Internet of Things and cloud computing technologies, more and more devices are deployed at the edge of the network, forming an edge computing service system. These edge devices are usually distributed in a wide range of geographical locations, performing preliminary processing and analysis of data to reduce latency and network load. However, due to the large number and wide distribution of edge devices, effective management and monitoring of them has become a major challenge. Existing remote management and monitoring systems often rely on centralized architectures, which may lead to inefficient monitoring and slow response when dealing with a large number of distributed devices.
[0003] Existing technologies usually use a single monitoring node for device monitoring, which may be feasible when the number of devices is small, but in the case of large-scale deployment, a single monitoring node can easily become a performance bottleneck and cannot meet the requirements of real-time performance and reliability. In addition, when a monitoring node fails, the lack of an effective failover mechanism may cause the entire monitoring system to be interrupted. In terms of hardware resource management, existing technologies often lack flexibility and it is difficult to dynamically adjust the configuration of edge devices according to the needs of monitoring tasks.
[0004] In the process of implementing the embodiments of the present invention, the inventors found that there are at least the following problems or defects in the prior art: first, there is a lack of a system architecture that can adapt to the needs of large-scale distributed edge device monitoring; second, the existing monitoring system lacks an effective backup and recovery mechanism when the monitoring node fails; finally, the existing system lacks flexibility in resource management and cannot dynamically adjust the configuration of the edge device according to the needs of the actual monitoring task. Summary of the invention
[0005] The present invention provides a Linux-based edge device remote management and monitoring system and method.
[0006] In a first aspect of the present invention, a Linux-based edge device remote management and monitoring system is provided, comprising: At least one edge management node, multiple monitoring nodes, and at least one main monitoring node; wherein the monitoring node monitors the edge device nodes in the edge computing service system according to the monitoring command received from the main monitoring node, and returns the monitoring result to the main monitoring node; the main monitoring node is used to send monitoring commands to the monitoring nodes, collect the monitoring results returned by each monitoring node, and display them to the administrator; The edge management node is used to provide management functions, including: creating or deleting the edge device node, the main monitoring node, and the monitoring node; dynamically adjusting the configuration of the edge device node, and performing continuous two-way data transmission through a WebSocket connection.
[0007] Furthermore, it also includes at least one slave monitoring node, which is a backup of the master monitoring node. When the master monitoring node fails, the slave monitoring node works instead of the master monitoring node.
[0008] Furthermore, the monitoring node is implemented using a virtual host, the edge device node has at least one corresponding monitoring node, and the monitoring node can achieve hardware pass-through through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through.
[0009] Furthermore, the master monitoring node sends a monitoring command to the monitoring node according to the monitoring task table, and the master monitoring node selects a monitoring node to which a monitoring command needs to be sent from the multiple monitoring nodes according to the monitoring node status table; wherein the monitoring task table includes the ID of the edge device node to be monitored, the monitoring type, the edge device access information, the monitoring task start time, whether it is a repeated monitoring task identifier, and the monitoring task cycle; The monitoring node status table records which of the three states the monitoring node is in: idle, busy, or faulty.
[0010] Furthermore, the slave monitoring node periodically sends a response request to the master monitoring node. When the master monitoring node has no response for more than a certain period of time, the slave monitoring node notifies the edge management node; the edge management node deletes the master monitoring node, and promotes the slave monitoring node to the master monitoring node, and finally creates a new slave monitoring node as a backup.
[0011] In a second aspect of the present invention, a Linux-based edge device remote management and monitoring method is provided, comprising: Step 1: The main monitoring node queries the monitoring task table to obtain the monitoring task; Step 2: The master monitoring node checks the monitoring node status table, and selects a monitoring node that can meet the monitoring task and has an "idle" status from the monitoring node status table according to the requirements of the monitoring task; Step 3, the main monitoring node sends a monitoring command to the idle monitoring node obtained in step 2) according to the monitoring task; Step 4: After receiving the monitoring command, the idle monitoring node returns the status "busy" to the main monitoring node and starts the monitoring process; Step 5: The monitoring node returns monitoring data during the monitoring process until the termination condition of the monitoring task is met; Step 6: The monitoring node returns the information that the monitoring task is completed to the main control node, and the main control node changes the status of these nodes to "idle" in the monitoring node status table.
[0012] Furthermore, before the step 1, the step of adding a monitoring task to the monitoring task table is also included, and the step includes: when a new monitoring task is to be established for a newly created or existing edge device node, a monitoring task is generated according to the type of the edge device node and the monitoring frequency set by the administrator, and the monitoring task is added to the monitoring task table.
[0013] Furthermore, the method also includes the step of performing redundant replacement of a faulty monitoring node when a monitoring node fails; the step includes: the main monitoring node sets the status of the faulty monitoring node to "failure", then searches the monitoring node status table, selects a replacement monitoring node from the remaining monitoring nodes with a status of "idle", and sends a monitoring command to the replacement monitoring node, which executes the monitoring process.
[0014] Furthermore, the method also includes a step of adjusting the performance of the edge device node according to the monitoring result; the step includes: Step 101, the main monitoring node checks whether the monitoring result meets the user's requirements, and if not, executes the next step; Step 102, check whether automatic adjustment is set, if yes, proceed to the next step, otherwise, end the operation after issuing a warning message; Step 103: The main monitoring node calculates the configuration of the edge device node that is suitable for the current task, and then notifies the edge management node of the calculation result; Step 104: After receiving the new configuration information, the edge device node reconfigures its own resources according to the information, including CPU pass-through, display pass-through, COM serial port pass-through, and USB pass-through.
[0015] Furthermore, the edge management node communicates with the client machine via a WebSocket connection to implement the functions of the server accepting the connection and the client initiating the request. The edge management node can send the image file to the client machine, and the client machine can receive and initialize the image to create and manage virtual machine instances; the edge management node can be operated through the management platform Web interface, including sending images, transmitting images, sending restore instructions, and transmitting restore instructions; The edge device remote management and monitoring system supports virtualization technology through the IXDOM_VIRT kernel module, including hardware pass-through technology and virtualization technology.
[0016] The above-mentioned embodiments according to the present invention have at least the following beneficial effects: the system described in the present invention can realize efficient management and monitoring of edge device nodes in the edge computing service system by setting at least one edge management node and multiple monitoring nodes. The edge management node can create or delete edge device nodes, main monitoring nodes and monitoring nodes, dynamically adjust the configuration of edge device nodes, and perform continuous two-way data transmission through WebSocket connection, which can improve the flexibility and response speed of the system. At the same time, the monitoring node monitors the edge device node according to the monitoring command received from the main monitoring node, and returns the monitoring results to the main monitoring node, making the monitoring process more automated and real-time.
[0017] In addition, the system also includes a slave monitoring node as a backup for the main monitoring node. When the main monitoring node fails, the slave monitoring node can immediately replace the main monitoring node to work, which can improve the reliability of the system. The monitoring node is implemented using a virtual host, and hardware pass-through is achieved through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through, which can improve the accuracy and efficiency of monitoring. The main monitoring node sends monitoring commands to the monitoring node according to the monitoring task table, and selects the monitoring node to which the monitoring command needs to be sent according to the monitoring node status table, which can ensure the reasonable allocation and execution of monitoring tasks. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The above and other objects, features and advantages of the exemplary embodiments of the present invention will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present invention are shown in an exemplary and non-limiting manner, in which: Figure 1 A schematic diagram of the structure of a Linux-based edge device remote management and monitoring system provided by an embodiment of the present invention; Figure 2 A flowchart of a Linux-based edge device remote management and monitoring method provided by an embodiment of the present invention; Figure 3 The schematic diagram schematically shows the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0019] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present invention more thorough and complete, and to fully convey the scope of the present invention to those skilled in the art.
[0020] Those skilled in the art know that the embodiments of the present invention can be implemented as a system, device, apparatus, method or computer program product. Therefore, the present invention can be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.
[0021] It should be noted that any number of elements in the drawings is for illustration rather than limitation, and any naming is only for distinction and does not have any limiting meaning.
[0022] Reference below Figure 1 , Figure 1 A schematic diagram of a process flow of a Linux-based edge device remote management and monitoring system provided by an embodiment of the present invention. Figure 1 As shown, a Linux-based edge device remote management and monitoring system 100 includes: At least one edge management node 101, multiple monitoring nodes 102, and at least one master monitoring node 103; The monitoring node monitors the edge device nodes in the edge computing service system according to the monitoring command received from the main monitoring node, and returns the monitoring result to the main monitoring node; the main monitoring node is used to send monitoring commands to the monitoring nodes, collect the monitoring results returned by each monitoring node, and display them to the administrator; The edge management node is used to provide management functions, including: creating or deleting the edge device node, the main monitoring node, and the monitoring node; dynamically adjusting the configuration of the edge device node, and performing continuous two-way data transmission through a WebSocket connection.
[0023] It should be noted that the system includes at least one edge management node and multiple monitoring nodes, which are used to monitor and manage edge device nodes in the edge computing service system. The edge management node is responsible for providing management functions, including creating or deleting edge device nodes, main monitoring nodes and monitoring nodes, and dynamically adjusting the configuration of edge device nodes. The monitoring node monitors the edge device nodes according to the monitoring commands sent by the main monitoring node, and returns the monitoring results to the main monitoring node.
[0024] Specifically, edge management nodes can be one or more physical servers or virtual machines that run management software, can process requests from the main monitoring node, and perform corresponding management operations. Monitoring nodes can also be physical devices or virtual machines that run monitoring software, can perform monitoring tasks and collect data. Edge device nodes can be various types of edge computing devices, such as routers, sensors, cameras, etc.
[0025] Preferably, the edge management node can automate the management process by configuring management policies. For example, a scheduled task can be set to check the status of edge device nodes and automatically adjust the configuration when an anomaly is detected. Monitoring nodes can collect data in a polling or event-driven manner to reduce the impact on the performance of edge device nodes. In addition, the system can also support continuous two-way data transmission through WebSocket connections to achieve real-time monitoring and rapid response.
[0026] In some embodiments, at least one slave monitoring node is further included, and the slave monitoring node is a backup of the master monitoring node. When the master monitoring node fails, the slave monitoring node replaces the master monitoring node to work.
[0027] It should be noted that the system includes at least one slave monitoring node as a backup of the master monitoring node to ensure that when the master monitoring node fails, the system can seamlessly switch to the slave monitoring node to continue to perform monitoring tasks.
[0028] Specifically, the slave monitoring node can be a physical server or virtual machine of the same or different type as the master monitoring node, which runs the same monitoring software as the master monitoring node. The slave monitoring node needs to keep in sync with the master monitoring node so that it can immediately take over the monitoring task when the master monitoring node fails.
[0029] Furthermore, the slave monitoring node can periodically send heartbeat signals to the master monitoring node to confirm the status of the master monitoring node. The slave monitoring node can be configured to automatically take over the monitoring task when the master monitoring node fails, or manually switch according to the administrator's instructions. To achieve this, the system can set up a fault detection mechanism, such as timeout detection or anomaly detection, to determine whether the master monitoring node has failed.
[0030] Specifically, the slave monitoring node can be configured to automatically notify the administrator after taking over the monitoring task for further processing. It is also possible to consider setting up multiple slave monitoring nodes to achieve load balancing and further redundancy.
[0031] In some embodiments, the monitoring node is implemented using a virtual host, the edge device node has at least one corresponding monitoring node, and the monitoring node can achieve hardware pass-through through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through.
[0032] It should be noted that the monitoring node is implemented using a virtual host and hardware pass-through is achieved through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through.
[0033] Specifically, a virtual host can be a virtual machine or container created using virtualization technology, which runs on a physical server but appears as an independent computing environment. IXDOM_VIRT virtualization technology is a technology that allows virtual machines to directly access physical hardware, which can reduce the performance overhead caused by virtualization.
[0034] More specifically, CPU passthrough means that the virtual machine can directly use CPU resources like a physical machine, display passthrough allows the virtual machine to directly access the display, COM serial port passthrough and USB passthrough allow the virtual machine to directly access serial port devices and USB devices respectively.
[0035] Preferably, the virtualization configuration of the monitoring node can be adjusted according to the hardware and monitoring requirements of the edge device node. For example, one or more virtual CPU cores can be allocated to each edge device node, an appropriate memory size can be allocated, and pass-through hardware resources can be configured as needed.
[0036] Furthermore, the virtualization management software can be set to regularly check the performance and resource usage of the virtual machines to ensure efficient execution of the monitoring task. Alternative solutions include using different virtualization technologies, such as KVM or Xen, or adjusting the configuration of the virtual machines according to the specific needs of the monitoring task.
[0037] In some embodiments, the master monitoring node sends a monitoring command to the monitoring node according to the monitoring task table, and the master monitoring node selects a monitoring node to which a monitoring command needs to be sent from the multiple monitoring nodes according to the monitoring node status table; wherein the monitoring task table includes the ID of the edge device node to be monitored, the monitoring type, the edge device access information, the monitoring task start time, whether it is a repeated monitoring task identifier, and the monitoring task cycle; The monitoring node status table records which of the three states the monitoring node is in: idle, busy, or faulty.
[0038] It should be noted that the master monitoring node sends monitoring commands to the monitoring nodes according to the monitoring task table, and selects the monitoring nodes to which the monitoring commands need to be sent from multiple monitoring nodes according to the monitoring node status table. This mechanism allows the master monitoring node to selectively assign tasks based on the specific requirements of the monitoring tasks and the current status of the monitoring nodes.
[0039] Specifically, the monitoring task table is a database or file that records the detailed information of the monitoring tasks that need to be executed, including the ID of the edge device node to be monitored, the monitoring type, the edge device access information, the monitoring task start time, whether it is a repeated monitoring task identifier, the monitoring task cycle, etc.
[0040] More specifically, the monitoring node status table records the current status of each monitoring node, such as idle, busy, or faulty. This information can help the master monitoring node decide which monitoring node to assign the monitoring task to.
[0041] Preferably, the master monitoring node can use intelligent algorithms to optimize the distribution of monitoring tasks. For example, a load balancing algorithm can be used to ensure that the workload of the monitoring nodes is evenly distributed, or a prediction algorithm can be used to predict future monitoring needs and allocate tasks in advance accordingly.
[0042] Furthermore, the master monitoring node can set thresholds to automatically trigger the task reallocation mechanism when the status of the monitoring node becomes busy or faulty. Alternatives include using different task allocation strategies, such as polling or priority scheduling, or allocating tasks based on the performance and geographical location of the monitoring node.
[0043] In some embodiments, the slave monitoring node periodically sends a response request to the master monitoring node. When the master monitoring node has no response for more than a certain period of time, the slave monitoring node notifies the edge management node; the edge management node deletes the master monitoring node, and promotes the slave monitoring node to the master monitoring node, and finally creates a new slave monitoring node as a backup.
[0044] It should be noted that the slave monitoring node periodically sends a response request to the master monitoring node. When the master monitoring node does not respond for a certain period of time, the slave monitoring node notifies the edge management node.
[0045] Specifically, the slave monitoring node can be configured to periodically send heartbeat signals or response requests to the master monitoring node. These signals can be simple network requests, such as ICMP echo request ping or more complex protocol messages.
[0046] More specifically, if the master monitoring node does not respond within a preset time, the slave monitoring node will consider that the master monitoring node has failed. The certain time can be from a few seconds to a few minutes, depending on the sensitivity requirements of the system for fault detection.
[0047] Preferably, after detecting that the master monitoring node is unresponsive, the slave monitoring node can perform a series of failover operations. First, it can send a failure notification to the edge management node, which can then execute a failure recovery strategy, such as automatically deleting the failed master monitoring node and removing it from the system. Then, the slave monitoring node can be promoted to the master monitoring node and take over the monitoring task.
[0048] Furthermore, the system can automatically create a new slave monitoring node to ensure that there is always a backup node ready to take over. This process can be automatic or semi-automatic, requiring confirmation from an administrator. Alternatives include using different failure detection and recovery mechanisms, such as detection algorithms based on different types of network failures, or introducing more manual intervention steps in the failover process.
[0049] The above-mentioned embodiments of the present invention have the following beneficial effects: The edge device remote management and monitoring system of the present invention can monitor and manage edge device nodes in the edge computing service system. By setting at least one edge management node and multiple monitoring nodes, the system can achieve comprehensive monitoring of edge device nodes. The monitoring node operates according to the monitoring command sent by the main monitoring node and feeds back the results to the main monitoring node. The administrator can make decisions based on the results displayed by the main monitoring node. Such a design can improve the real-time and accuracy of monitoring.
[0050] In addition, the system also includes at least one slave monitoring node as a backup for the main monitoring node. When the main monitoring node fails, the slave monitoring node can immediately take over the work to ensure that the continuity of monitoring is not interrupted. The monitoring node is implemented using a virtual host, and hardware pass-through is achieved through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through. Such technical applications can improve the flexibility and efficiency of monitoring. The main monitoring node sends monitoring commands based on the monitoring task table and the monitoring node status table to ensure the reasonable allocation and execution of monitoring tasks, which can improve the monitoring capabilities and management efficiency of the entire system.
[0051] like Figure 2 As shown, in some embodiments, a Linux-based edge device remote management and monitoring method 200 includes: Step 1: The main monitoring node queries the monitoring task table to obtain the monitoring task; Step 2: The master monitoring node checks the monitoring node status table, and selects a monitoring node that can meet the monitoring task and has an "idle" status from the monitoring node status table according to the requirements of the monitoring task; Step 3, the main monitoring node sends a monitoring command to the idle monitoring node obtained in step 2) according to the monitoring task; Step 4: After receiving the monitoring command, the idle monitoring node returns a busy state to the main monitoring node and starts the monitoring process; Step 5: The monitoring node returns monitoring data during the monitoring process until the termination condition of the monitoring task is met; Step 6: The monitoring node returns the information that the monitoring task is completed to the main control node, and the main control node changes the status of these nodes to "idle" in the monitoring node status table.
[0052] It is understandable that the modules recorded in the Linux-based edge device remote management and monitoring method 200 are similar to those in the reference Figure 1 Therefore, the operations, features and beneficial effects described above for the remote management and monitoring system for edge devices based on Linux are also applicable to the remote management and monitoring method 200 for edge devices based on Linux and the modules contained therein, and will not be repeated here.
[0053] In some embodiments, before step 1, the step of adding a monitoring task to the monitoring task table is also included, and the step includes: when a new monitoring task is to be established for a newly created or existing edge device node, a monitoring task is generated according to the type of the edge device node and the monitoring frequency set by the administrator, and the monitoring task is added to the monitoring task table.
[0054] It should be noted that the step of adding monitoring tasks to the monitoring task table is a key step in the system implementation process. This step involves setting up new monitoring tasks for newly created or existing edge device nodes, and generating monitoring tasks based on the type of edge device nodes and the monitoring frequency set by the administrator.
[0055] Specifically, the process of adding a monitoring task includes determining the parameters of the monitoring task, such as the monitored edge device node ID, monitoring type, such as performance monitoring, security monitoring, etc., edge device access information, such as IP address, port number, etc., monitoring task start time, whether it is a repeated monitoring task identifier, and monitoring task cycle.
[0056] Furthermore, these parameters can be configured according to the characteristics of the edge device nodes and the needs of the administrator. For example, for devices that require real-time monitoring, a shorter monitoring period can be set; while for devices that require periodic inspection, a longer monitoring period can be set.
[0057] Preferably, the process of adding monitoring tasks can be performed through a graphical user interface GUI or a command line interface CLI to facilitate administrator operation. The system can provide a user-friendly interface to allow administrators to easily input parameters of monitoring tasks and add them to the monitoring task table.
[0058] More specifically, the system can also provide templates or preset monitoring tasks to speed up the task adding process. Alternatives include using automated scripts or API calls to add monitoring tasks in batches, or dynamically generating monitoring tasks based on real-time performance data from edge devices.
[0059] In some embodiments, the method also includes the step of performing a redundant replacement for a faulty monitoring node when a monitoring node fails; the step includes: the main monitoring node sets the status of the faulty monitoring node to faulty, then searches the monitoring node status table, selects a replacement monitoring node from the remaining monitoring nodes that are idle, and sends a monitoring command to the replacement monitoring node, which executes the monitoring process.
[0060] Specifically, the redundant replacement step of the faulty monitoring node involves setting the status of the faulty monitoring node to faulty, and then searching the remaining monitoring nodes with idle status from the monitoring node status table. This process requires defining the specific fault type and fault detection mechanism of the faulty monitoring node, as well as how to feed back the fault information to the main monitoring node. For example, the fault type includes network failure, hardware failure or software failure, and the fault detection mechanism includes heartbeat detection, abnormal log analysis or performance indicator monitoring.
[0061] Preferably, the redundant replacement of the faulty monitoring node can be implemented by an automated script or a fault recovery module within the monitoring system. The automated script can be automatically executed when a fault is detected, and the fault recovery module can be integrated into the monitoring system to monitor the status of the monitoring node in real time and automatically perform redundant replacement when a fault is detected.
[0062] Furthermore, the system can be configured with a fault notification mechanism to notify the administrator of fault information and recovery operations via email, SMS or system logs. Alternative solutions include manually replacing the faulty monitoring node or introducing more manual review steps during the redundant replacement process to ensure the accuracy of the replacement operation.
[0063] In some embodiments, the method further includes a step of adjusting the performance of the edge device node according to the monitoring result; the step includes: Step 101, the main monitoring node checks whether the monitoring result meets the user's requirements, and if not, executes the next step; Step 102, check whether automatic adjustment is set, if yes, proceed to the next step, otherwise, end the operation after issuing a warning message; Step 103: The main monitoring node calculates the configuration of the edge device node that is suitable for the current task, and then notifies the edge management node of the calculation result; Step 104: After receiving the new configuration information, the edge device node reconfigures its own resources according to the information, including CPU pass-through, display pass-through, COM serial port pass-through, and USB pass-through.
[0064] It should be noted that the method includes a step of adjusting the performance of the edge device node according to the monitoring results. This step allows the system to dynamically adjust the configuration of the edge device node according to real-time data and preset performance indicators to meet changing needs.
[0065] Specifically, the performance adjustment step involves the main monitoring node checking whether the monitoring results meet the user's needs. If not, proceed to the next step. Check whether automatic adjustment is set. If so, continue to execute; if not, issue a warning message and end the operation. The main monitoring node calculates the configuration of the edge device node that is suitable for the current task, and then notifies the edge management node of the calculation result. After receiving the new configuration information, the edge device node reconfigures its own resources according to the information, including CPU pass-through, display pass-through, COM serial port pass-through, and USB pass-through.
[0066] Preferably, performance adjustment can include adjusting resource allocation of edge device nodes, such as CPU frequency, memory allocation, storage space allocation, etc. In addition, the system can be configured with multiple performance indicator thresholds, and when the monitoring results show that the performance of the edge device node is lower or higher than these thresholds, the performance adjustment is automatically triggered. Alternative solutions include using machine learning algorithms to predict performance requirements and make resource adjustments in advance based on the predicted results, or allowing administrators to manually intervene in the adjustment process to respond to specific business needs or special situations.
[0067] In some embodiments, the edge management node communicates with the client machine via a WebSocket connection to implement the functions of the server accepting connections and the client initiating requests. The edge management node can send the image file to the client machine, and the client machine can receive and initialize the image to create and manage virtual machine instances; the edge management node can be operated through the management platform Web interface, including sending images, transmitting images, sending restore instructions, and transmitting restore instructions; The edge device remote management and monitoring system supports virtualization technology through the IXDOM_VIRT kernel module, including hardware pass-through technology and virtualization technology.
[0068] It should be noted that the edge management node communicates with the client machine through a WebSocket connection to realize the functions of the server accepting connections and the client initiating requests. This real-time two-way communication mechanism enables the edge management node to quickly respond to client requests and send image files to the client machine. The client machine can receive and initialize the image to create and manage virtual machine instances.
[0069] Specifically, a WebSocket connection is a protocol for full-duplex communication over a single TCP connection. It allows the server to actively send messages to the client without the client initiating a request again. The edge management node can use the WebSocket connection to send operating system images, applications, or other necessary files. After receiving these images, the client machine can use virtualization technologies such as KVM, Xen, or VMware to initialize and manage virtual machine instances.
[0070] Preferably, the edge management node can be operated through the management platform web interface, including issuing images, transmitting images, sending restore instructions, and transmitting restore instructions. This provides a user-friendly interface that allows administrators to easily manage edge devices. In addition, the system can support virtualization technology through the IXDOM_VIRT kernel module, including hardware pass-through technology and virtualization technology, to improve resource utilization efficiency and system flexibility. Alternative solutions include using other communication protocols such as HTTP / 2 or gRPC, or using different virtualization technologies such as containerization technology to achieve resource isolation and management.
[0071] Reference below Figure 3 , which shows a schematic diagram of a structure 300 of an electronic device suitable for implementing some embodiments of the present invention. The electronic devices in some embodiments of the present invention may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 3 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0072] like Figure 3As shown, the electronic device 300 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 to a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.
[0073] Typically, the following devices may be connected to the I / O interface 305: an input device 306 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 307 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 308 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 309. The communication device 309 may allow the electronic device 300 to communicate with other devices wirelessly or by wire to exchange data. Figure 3 The electronic device 300 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 3 Each block shown in the figure may represent one device, or may represent multiple devices as required.
[0074] Furthermore, the storage medium of the embodiment of the present application stores program instructions that can implement all the above methods, wherein the program instructions can be stored in the above storage medium in the form of a software product, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or terminal devices such as a computer, a server, a mobile phone, and a tablet.
[0075] The above descriptions are only some preferred embodiments of the present invention and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present invention is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present invention.
Claims
1. A Linux-based edge device remote management and monitoring system for monitoring an edge computing service system including edge device nodes; characterized in that: include At least one edge management node, multiple monitoring nodes, and at least one main monitoring node; wherein the monitoring node monitors the edge device nodes in the edge computing service system according to the monitoring command received from the main monitoring node, and returns the monitoring result to the main monitoring node; the main monitoring node is used to send monitoring commands to the monitoring nodes, collect the monitoring results returned by each monitoring node, and display them to the administrator; The edge management node is used to provide management functions, including: creating or deleting the edge device node, the main monitoring node, and the monitoring node; dynamically adjusting the configuration of the edge device node, and performing continuous two-way data transmission through a WebSocket connection.
2. The edge device remote management and monitoring system according to claim 1, characterized in that: It also includes at least one slave monitoring node, which is a backup of the master monitoring node. When the master monitoring node fails, the slave monitoring node works instead of the master monitoring node.
3. The edge device remote management and monitoring system according to claim 1 or 2, characterized in that: The monitoring node is implemented using a virtual host, the edge device node has at least one corresponding monitoring node, and the monitoring node can achieve hardware pass-through through IXDOM_VIRT virtualization technology, including CPU pass-through, display pass-through, COM serial port pass-through and USB pass-through.
4. The edge device remote management and monitoring system according to claim 1 or 2, characterized in that: The master monitoring node sends a monitoring command to the monitoring node according to the monitoring task table, and the master monitoring node selects a monitoring node to which a monitoring command needs to be sent from the multiple monitoring nodes according to the monitoring node status table; wherein the monitoring task table includes the ID of the edge device node to be monitored, the monitoring type, the edge device access information, the monitoring task start time, whether it is a repeated monitoring task identifier, and the monitoring task cycle; The monitoring node status table records which of the three states the monitoring node is in: idle, busy, or faulty.
5. The edge device remote management and monitoring system according to claim 2, characterized in that: The slave monitoring node periodically sends a response request to the master monitoring node. When the master monitoring node does not respond for a certain period of time, the slave monitoring node notifies the edge management node. The edge management node deletes the master monitoring node, promotes the slave monitoring node to the master monitoring node, and finally creates a new slave monitoring node as a backup.
6. A Linux-based edge device remote management and monitoring method applied to claims 1-5, comprising: Step 1: The main monitoring node queries the monitoring task table to obtain the monitoring task; Step 2: the master monitoring node checks the monitoring node status table, and selects a monitoring node that can meet the monitoring task and has an "idle" status from the monitoring node status table according to the requirements of the monitoring task; Step 3, the main monitoring node sends a monitoring command to the idle monitoring node obtained in step 2) according to the monitoring task; Step 4: After receiving the monitoring command, the idle monitoring node returns the status "busy" to the main monitoring node and starts the monitoring process; Step 5: The monitoring node returns monitoring data during the monitoring process until the termination condition of the monitoring task is met; Step 6: The monitoring node returns the information that the monitoring task is completed to the main control node, and the main control node changes the status of these nodes to "idle" in the monitoring node status table.
7. The edge device remote management and monitoring method according to claim 6, characterized in that: Before step 1, the step of adding a monitoring task to the monitoring task table is also included, and the step includes: when a new monitoring task is to be established for a newly created or existing edge device node, a monitoring task is generated according to the type of the edge device node and the monitoring frequency set by the administrator, and the monitoring task is added to the monitoring task table.
8. The edge device remote management and monitoring method according to claim 6, characterized in that: The method also includes the step of performing a redundant replacement on a faulty monitoring node when a monitoring node fails; the step includes: the main monitoring node sets the status of the faulty monitoring node to "failure", then searches the monitoring node status table, selects a replacement monitoring node from the remaining monitoring nodes with a status of "idle", and sends a monitoring command to the replacement monitoring node, which executes the monitoring process.
9. The edge device remote management and monitoring method according to claim 6, characterized in that: The method also includes a step of adjusting the performance of the edge device node according to the monitoring result; the step includes: Step 101, the main monitoring node checks whether the monitoring result meets the user's requirements, and if not, executes the next step; Step 102, check whether automatic adjustment is set, if yes, proceed to the next step, otherwise, end the operation after issuing a warning message; Step 103: The main monitoring node calculates the configuration of the edge device node that is suitable for the current task, and then notifies the edge management node of the calculation result; Step 104: After receiving the new configuration information, the edge device node reconfigures its own resources according to the information, including CPU pass-through, display pass-through, COM serial port pass-through, and USB pass-through.
10. The edge device remote management and monitoring method according to claim 6, characterized in that: The edge management node communicates with the client machine through a WebSocket connection to realize the functions of the server accepting the connection and the client initiating the request. The edge management node can send the image file to the client machine, and the client machine can receive and initialize the image to create and manage virtual machine instances; The edge management node can be operated through the management platform Web interface, including issuing images, transmitting images, sending restore instructions, and transmitting restore instructions; The edge device remote management and monitoring system supports virtualization technology through the IXDOM_VIRT kernel module, including hardware pass-through technology and virtualization technology.
Citation Information
Patent Citations
Cloud computing service monitoring system and method thereof
CN102882909A
Hardware acceleration equipment mounting method and cloud platform
CN111240800A
Monitoring method and system for multi-node edge computing equipment
CN112596893A
Unified policy management system with integrated policy enforcer
EP1143665A2
