Process processing method and device for cleaning equipment, medium and cleaning equipment

By employing a custom communication library and monitoring scripts in the cleaning equipment to detect process crashes and restart and reconnect the process, the problem of low efficiency in traditional cleaning equipment is solved, achieving stability and high efficiency in inter-process communication.

CN117472602BActive Publication Date: 2026-11-10DREAM INNOVATION TECH (SUZHOU) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210858040.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-20
Publication Date
2026-11-10
Estimated Expiration
2042-07-20

AI Technical Summary

Technical Problem

Traditional cleaning equipment has low cleaning efficiency, mainly because it cannot detect and recover in time when the process crashes, resulting in a decrease in overall operating efficiency.

Method used

Inter-process shared memory communication is implemented through a custom communication library. During the operation of the cleaning device, a monitoring script is used to detect crashes, restart crashed processes, and reconnect to the processes through the custom communication library to restore communication.

Benefits of technology

It improves the cleaning efficiency of cleaning equipment, ensures that the cleaning work of other functional nodes is not affected, and timely detection and recovery of inter-process communication avoids coupling effects, thereby improving the stability and efficiency of operation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117472602B_ABST
    Figure CN117472602B_ABST
Patent Text Reader

Abstract

The application discloses a process processing method and device of a cleaning device, a medium and the cleaning device. The method comprises the following steps: in the running process of the cleaning device, a monitoring script is used to detect the collapse of multiple processes distributed in function nodes of the cleaning device; the multiple processes communicate with each other based on a shared memory using a custom communication library; the custom communication library is a shared memory communication library developed by custom adaptation to the running platform of the cleaning device; in the case that a collapsed process is detected, the collapsed process is restarted; after the process is restarted, the restarted process is reconnected through the custom communication library, so that the restarted process realizes subsequent inter-process communication based on the shared memory.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of intelligent device technology, specifically relating to process processing methods, devices, media, and cleaning equipment for cleaning equipment. Background Technology

[0002] With the rapid development of science and technology, various intelligent devices have emerged, bringing great convenience to people's lives and work. Cleaning equipment is one such very important type of intelligent device; people only need to run the cleaning equipment, and it can automatically perform cleaning tasks.

[0003] In traditional methods, a process is started every time the cleaning equipment runs, and all subsequent processing involved in the operation of the cleaning equipment is handled by this process, resulting in relatively low cleaning efficiency. Therefore, there is an urgent need to propose a solution to the problem of low cleaning efficiency in traditional methods. Summary of the Invention

[0004] Therefore, the technical problem to be solved by this application is how to improve the cleaning efficiency of cleaning equipment.

[0005] To solve the above-mentioned technical problems, this application provides a process processing method for cleaning equipment, including:

[0006] During the operation of the cleaning equipment, a monitoring script is used to detect crashes in multiple processes distributed across the functional nodes of the cleaning equipment. These multiple processes communicate with each other using shared memory based on a custom communication library. The custom communication library is a custom-developed shared memory communication library adapted to the operating platform of the cleaning equipment.

[0007] If a crashed process is detected, restart the crashed process;

[0008] After the process restarts, the restarted process is reconnected through the custom communication library, so that the restarted process can carry out subsequent inter-process communication based on the shared memory.

[0009] Optionally, in the above-mentioned process handling method for cleaning equipment, the step of performing crash detection on multiple processes distributed across the functional nodes of the cleaning equipment via a monitoring script during the operation of the cleaning equipment includes:

[0010] A target time interval is determined to trigger crash detection; the target time interval is determined based on the crash tolerance information of the cleaning equipment; the crash tolerance information is information characterizing the crash tolerance capability of the cleaning equipment.

[0011] During the operation of the cleaning equipment, the monitoring script is executed according to the target time interval to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment.

[0012] Optionally, in the above-mentioned process handling method for cleaning equipment, the crash tolerance information includes the current crash tolerance duration; the determination of the target time interval for triggering crash detection includes:

[0013] During the operation of the cleaning equipment, the current functional node information corresponding to each of the multiple processes is determined; the current functional node information is the relevant information of the functional node currently being executed by each process; the current functional node information is included in the crash tolerance information;

[0014] Based on the current functional node information, determine the current crash tolerance time of the cleaning equipment;

[0015] The target time interval is determined based on the current crash tolerance duration.

[0016] Optionally, in the above process handling method for cleaning equipment, determining the current crash tolerance time of the cleaning equipment based on the current functional node information includes:

[0017] Based on the current functional node information corresponding to each of the multiple processes, determine the current crash tolerance sub-duration of each process;

[0018] The current crash tolerance duration of the cleaning equipment is determined based on the crash tolerance duration corresponding to each process.

[0019] Optionally, in the above-mentioned process handling method for cleaning equipment, the step of performing crash detection on multiple processes distributed across the functional nodes of the cleaning equipment through a monitoring script during the operation of the cleaning equipment includes at least one of the following processing steps:

[0020] During the operation of the cleaning equipment, the process identifiers of the multiple processes are queried through a monitoring script; based on the query results, the processes that have crashed are detected.

[0021] During the operation of the cleaning equipment, a monitoring script sends probe messages to the multiple processes respectively. Based on the response results of the multiple processes to the probe messages, the process that has crashed is detected.

[0022] Optionally, in the above-mentioned process handling method for cleaning equipment, the step of reconnecting the restarted process through the custom communication library after the process restarts, so that the restarted process can realize subsequent inter-process communication based on the shared memory, includes:

[0023] After the process restarts, the preset function in the custom communication library is called to rewrite the shared memory communication information of the restarted process into the shared memory, so that the restarted process can realize subsequent inter-process communication based on the shared memory.

[0024] The shared memory communication information is the information required for communication using the shared memory.

[0025] Optionally, the process handling method of the above-mentioned cleaning equipment further includes:

[0026] Determine the functional nodes allocated in the crashed process;

[0027] If there are multiple assigned functional nodes, retrieve historical process crash records;

[0028] Analyze historical process crash records to predict problematic functional nodes from multiple assigned functional nodes; the problematic functional node is the functional node that is predicted and located as the cause of the crash.

[0029] This application also provides a process processing apparatus for cleaning equipment, comprising:

[0030] The crash detection module is used to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment during its operation via a monitoring script. These multiple processes communicate with each other using shared memory based on a custom communication library. The custom communication library is a custom-developed shared memory communication library adapted to the operating platform of the cleaning equipment.

[0031] The process restart module is used to restart the crashed process when the crash detection module detects a crashed process; after the process is restarted, the restarted process is reconnected through the custom communication library so that the restarted process can carry out subsequent inter-process communication based on the shared memory.

[0032] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the process processing method for the cleaning equipment provided in the above aspects.

[0033] This application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the process processing method for the cleaning equipment provided in the above aspects.

[0034] This application also provides a cleaning device, including a memory and a processor, wherein the memory stores a computer program, characterized in that the processor executes the computer program to implement the steps in the process processing method of the cleaning device provided above.

[0035] The technical solution provided in this application has the following advantages:

[0036] By distributing the functional nodes of the cleaning equipment across multiple processes, and using a custom-developed shared-memory communication library adapted to the cleaning equipment's operating platform—a custom communication library—communication between these processes is achieved. This ensures that even if some processes crash, the cleaning work of other functional nodes remains unaffected, improving cleaning efficiency to some extent. Furthermore, by using monitoring scripts to detect crashes in the distributed processes, crashed processes can be detected and restarted promptly. After restarting, the custom communication library reconnects the restarted process, ensuring subsequent inter-process communication and further enhancing cleaning efficiency. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0038] Figure 1 This is a flowchart illustrating a process handling method for a cleaning device in one embodiment of this application;

[0039] Figure 2 This is a schematic diagram illustrating the principle of determining the target time interval in one embodiment of this application;

[0040] Figure 3 This is a schematic diagram illustrating the principle of problem localization in one embodiment of this application;

[0041] Figure 4 This is a flowchart illustrating the process handling method of a cleaning device in another embodiment of this application;

[0042] Figure 5 This is a structural block diagram of the process processing device of a cleaning equipment in one embodiment of this application;

[0043] Figure 6 This is a structural block diagram of the process processing device of the cleaning equipment in another embodiment of this application;

[0044] Figure 7This is a diagram showing the internal structure of a cleaning device in one embodiment of this application. Detailed Implementation

[0045] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. The application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0046] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0047] In one embodiment, such as Figure 1 As shown, a process handling method for a cleaning device is provided. Taking the application of this method to a cleaning device as an example, the method includes the following steps:

[0048] Step 102: During the operation of the cleaning equipment, a monitoring script is used to detect crashes in multiple processes distributed across the functional nodes of the cleaning equipment; the multiple processes communicate with each other using shared memory based on a custom communication library.

[0049] The cleaning equipment mentioned here refers to intelligent devices that automatically perform cleaning tasks. That is, the cleaning equipment possesses its own computing capabilities, enabling it to automatically perform cleaning tasks through calculation and analysis after operation. It should be noted that the automatic performance of cleaning tasks mentioned in this application can include fully automatic or semi-automatic performance.

[0050] In some embodiments, the cleaning equipment may be a robotic vacuum cleaner or a public cleaning device. That is, the cleaning equipment is not limited to robotic vacuum cleaners used in smart home devices, but may also be large-scale intelligent devices used to autonomously perform cleaning tasks in public places. This application does not limit the specific form of the cleaning equipment; any device capable of autonomously performing cleaning tasks can fall within the scope of the cleaning equipment in this application.

[0051] The custom communication library is a custom-developed shared-memory communication library adapted to the operating platform of the cleaning equipment. It is understood that the operating platform of the cleaning equipment differs from that of traditional terminals. For example, the cleaning equipment has its own operating system and runtime environment, which are different from those of traditional terminals. Therefore, the custom communication library differs from the shared-memory communication libraries of traditional terminals; it is a shared-memory communication library independently developed by the inventors of this application specifically for cleaning equipment and adapted to its operating platform. Traditional terminals can be mobile phones, PCs, or smart wearable devices, etc.

[0052] It should be noted that the custom communication library in this application differs from the shared memory communication library of traditional terminals in the following two aspects: First, the custom communication library in this application is strongly related to the cleaning equipment, focusing primarily on implementing the relevant functions and requirements of the cleaning equipment itself. Compared to the shared memory communication library of traditional terminals, it has much less additional compatibility information and is much smaller, thus making it faster and more efficient to use. Second, compared to the shared memory communication library of traditional terminals, the custom communication library in this application not only includes information related to memory sharing but also includes a series of specific function sets. These specific function sets are custom-defined to implement certain processes involved in the operation of the cleaning equipment. The following sections will explain these two differences in detail.

[0053] Regarding the first difference, it's understandable that traditional terminal shared memory communication libraries are general-purpose communication libraries used to implement memory sharing. Therefore, they require compatibility with many aspects, such as additional services and cross-channel compatibility information. This results in large shared memory communication libraries for traditional terminals, leading to inefficiency and slowness, and failing to meet the real-time requirements of intelligent cleaning equipment like robotic vacuum cleaners. In contrast, the custom communication library proposed in this application does not require compatibility with additional services or cross-channel information, making it much smaller and faster to use, thus meeting the real-time and rapid response requirements of cleaning equipment.

[0054] Regarding the second difference, it's understandable that traditional terminal shared memory communication libraries only possess basic communication functions for implementing memory sharing, and cannot handle the crash and restart of the cleaning device process as described in this application. For example, after a process crashes and restarts, the custom communication library of this application can be used to reconnect the restarted process. Specifically, traditional terminal shared memory communication libraries only possess basic general-purpose functions for implementing memory sharing, and lack the specific functions custom-designed for cleaning devices as described in this application. For instance, they lack the specific function for reconnecting a restarted process as described in this application. Therefore, compared to traditional terminal shared memory communication libraries, the custom communication library of this application possesses more functions beyond memory sharing, representing a completely new communication library.

[0055] The operation of cleaning equipment involves multiple functional nodes, such as a central platform node and a radar planning node. This application distributes these functional nodes across multiple processes, with each process running one or more functional nodes. For example, the central platform node can be distributed into a separate process, the radar planning node into another, and the remaining functional nodes into the same process. Distributing the cleaning equipment's functional nodes across different processes allows the resource usage of each process to directly reflect the resource consumption of the functional nodes. When a process crashes, it's easy to pinpoint which functional nodes are malfunctioning, facilitating troubleshooting.

[0056] Based on the custom communication library of this application, multiple processes distributed across functional nodes can use shared memory for inter-process communication, instead of confining all functional nodes involved in the operation of the cleaning device to a single process. It should be noted that, as analyzed above, traditional terminal shared memory communication libraries are not suitable for the usage scenarios of cleaning devices. The inventors of this application have creatively applied shared memory technology to the intelligent operation scenario of cleaning devices by developing a completely new custom communication library adapted to cleaning devices. Based on this custom communication library, multi-process communication can be achieved in the cleaning device, and specific processing beyond memory sharing can also be implemented during the operation of the cleaning device.

[0057] Specifically, the cleaning equipment is equipped with a monitoring program for process crash monitoring. This monitoring program can use monitoring scripts to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment; that is, it detects whether any processes have crashed through the monitoring scripts. It should be noted that the monitoring program and monitoring scripts in the various embodiments of this application are used to detect the running status of processes and do not involve monitoring related to user privacy. In some embodiments, the cleaning equipment can periodically trigger the execution of the monitoring script to perform crash detection on multiple processes at preset fixed time intervals. For example, a preset fixed time interval of 3 seconds is used to check for crashed processes every 3 seconds.

[0058] In other embodiments, the cleaning device can also dynamically analyze the target time interval matching the current operating phase based on the operating information of the current operating phase, and trigger the execution of a monitoring script for crash detection based on the target time interval. It is understood that dynamically analyzing a suitable target time interval matching the current operating phase to trigger crash detection is more accurate and has strong applicability.

[0059] Step 104: If a crashed process is detected, restart the crashed process.

[0060] Specifically, cleaning equipment can use monitoring scripts to detect the online status of each process across multiple processes, and based on the online status of each process, detect whether any processes have crashed. It can be understood that online status refers to whether a process is online.

[0061] In some embodiments, the cleaning device can determine the online status of each process based on an online process list. For example, if there are three processes p1, p2, and p3, the monitoring script will query them at target time intervals to confirm whether p1, p2, and p3 are still online.

[0062] In other embodiments, the cleaning device can send probe messages to multiple processes separately via a monitoring script to detect the online status of each process. In still other embodiments, the cleaning device can also add corresponding status flags for each process and determine the online status of each process by querying the status flags of each process via the monitoring script. Status flags can include flags indicating online status and flags indicating offline status.

[0063] Step 106: After the process restarts, the restarted process is reconnected through a custom communication library so that the restarted process can achieve subsequent inter-process communication based on shared memory.

[0064] Specifically, the custom communication library includes pre-defined functions for enabling process reconnection. After a crashed process is restarted, the cleaning device can use these functions to reconnect the restarted process. This means that once the restarted process is back online, other running processes will know it has resumed normal operation and can restore communication with it. Consequently, the restarted process can then resume inter-process communication with other processes based on shared memory.

[0065] Understandably, if no crashing process is detected, the cleaning equipment can continue to perform crash detection on multiple processes distributed across the functional nodes through monitoring scripts.

[0066] The process handling method described above for the cleaning equipment distributes the functional nodes of the cleaning equipment across multiple processes. A custom-developed shared-memory communication library—a custom communication library—adapted to the operating platform of the cleaning equipment, enables communication between these processes. This ensures that even if some processes crash, the cleaning-related work of other functional nodes remains unaffected, improving cleaning efficiency to some extent. Furthermore, by monitoring scripts to detect crashes in the distributed processes, crashed processes can be detected and restarted promptly. After restarting, the custom communication library reconnects the restarted process, ensuring subsequent inter-process communication and quickly restoring the normal operation of the cleaning equipment, further enhancing cleaning efficiency.

[0067] Secondly, this application uses a monitoring script to implement process crash detection and restart. That is, crash detection and restart are implemented through a script, which is independent of the process and not coupled, thus avoiding the adverse effects of coupling to a certain extent.

[0068] Furthermore, this application proactively detects crashes through a monitoring script, rather than passively capturing crash signals. Passively capturing crash signals usually fails to capture them, making it impossible to detect the crashing process in a timely or accurate manner. This application proactively detects crashes through a monitoring script, enabling more proactive and timely detection of process crashes. This allows for the timely restarting of the crashed process to ensure the normal operation of the cleaning equipment. Moreover, since the crashed process can be started in a timely manner, it also avoids other processes occupying the memory of the crashed process.

[0069] In some embodiments, step 102, during the operation of the cleaning equipment, involves performing crash detection on multiple processes distributed across the functional nodes of the cleaning equipment using a monitoring script. This includes: determining a target time interval for triggering crash detection; the target time interval is determined based on the crash tolerance information of the cleaning equipment; and during the operation of the cleaning equipment, triggering the execution of a monitoring script according to the target time interval to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment.

[0070] Among them, the collapse tolerance information is information that characterizes the collapse tolerance of the cleaning equipment.

[0071] In some embodiments, crash tolerance information can be used to characterize the critical point of the cleaning equipment's crash tolerance capability, that is, to characterize the maximum degree of crash that the cleaning equipment can withstand throughout its operation. In this case, the crash tolerance information is a crash tolerance information used for overall analysis, regardless of the operational phase. The crash tolerance information may include at least one of the following: overall system resource information or maximum crash tolerance information for each process. Maximum crash tolerance information characterizes the maximum crash tolerance capability of a process, that is, the maximum degree of crash that the process can withstand.

[0072] It is understandable that the maximum crash tolerance information of each process can be used to analyze the maximum degree of crash that the cleaning equipment can withstand during its entire operation. Specifically, the minimum value can be selected from the maximum crash tolerance information corresponding to multiple processes as the crash tolerance information for the overall analysis of the cleaning equipment. Based on the crash tolerance information, the maximum degree of crash that the cleaning equipment can withstand during its entire operation can be analyzed to determine a target time interval. For example, if the maximum crash tolerance information of three processes is that they can withstand a 2-second crash, a 3-second crash, and a 5-second crash, respectively, then the minimum value—the ability to withstand a 2-second crash—is selected as the crash tolerance information for the overall analysis. In this way, the determined target time interval can at least meet the crash detection requirements of the process that can withstand a 2-second crash. Subsequently, throughout the entire operation of the cleaning equipment, a monitoring script can be triggered and executed at a fixed target time interval to perform crash detection on the multiple processes distributed across the functional nodes of the cleaning equipment.

[0073] In other embodiments, the crash tolerance information can also be used to characterize the crash tolerance capability of the cleaning equipment in the current operating phase; that is, the crash tolerance information can be the crash tolerance information of the cleaning equipment in the current operating phase. It is understood that the entire operation process of the cleaning equipment involves multiple phases, and the currently operating phase is the current operating phase.

[0074] Therefore, in each current operating phase, the crash tolerance information of the cleaning equipment can be determined to identify a target time interval matching the current operating phase. Then, within the current operating phase, a monitoring script can be triggered to execute according to the target time interval, thereby performing crash detection on multiple processes distributed across the functional nodes of the cleaning equipment. In this way, the cleaning equipment can have a matching target time interval to trigger the execution of the monitoring script in different operating phases, thus achieving dynamic determination of the target time interval and dynamic crash detection.

[0075] In some embodiments, when the crash tolerance information is the crash tolerance information for the current operating phase, the crash tolerance information may include at least one of the following operating-related information: current system resource usage information of the cleaning device or current functional node information. Current system resource usage information refers to the system resource usage information of the cleaning device during the current operating phase. Current functional node information refers to the relevant information of the functional nodes executed by the cleaning device in the current (i.e., current operating phase).

[0076] It is understandable that the appropriate selection of the time interval is crucial in script polling. If the time interval is set too large, it may fail to detect crashed processes in a timely manner, thus affecting the normal operation of the cleaning equipment. If the time interval is set too small, it may lead to excessively frequent polling, resulting in unnecessary consumption of system resources. Therefore, in the above embodiments of this application, the target time interval is determined based on the crash tolerance information of the cleaning equipment. This target time interval is specified with the crash tolerance information of the cleaning equipment in mind, making it more reasonable. Thus, it can both ensure timely detection of crashed processes and reduce unnecessary polling to a certain extent, thereby reducing system resource consumption.

[0077] In some embodiments, determining the target time interval for triggering crash detection includes: during the operation of the cleaning equipment, determining the current functional node information corresponding to each process among multiple processes; the current functional node information is the relevant information of the functional node currently being executed by each process; determining the current crash tolerance duration of the cleaning equipment based on the current functional node information; and determining the target time interval based on the current crash tolerance duration.

[0078] It is understandable that the current functional node information is a type of crash tolerance information. The current crash tolerance duration refers to the crash duration that the cleaning equipment can withstand during the current operational phase. The currently executed functional node refers to the functional node executed during the current operational phase.

[0079] Specifically, during the operation of the cleaning equipment, the multiple processes distributed across the functional nodes of the cleaning equipment run concurrently. Therefore, the cleaning equipment can determine the relevant information of the functional nodes executed in the current running phase of each process, obtaining the current functional node information corresponding to each process. Based on the current functional node information corresponding to each process, the cleaning equipment can determine the current crash tolerance duration of the entire cleaning equipment in the current running phase. Furthermore, based on the current crash tolerance duration, the cleaning equipment can determine the target time interval that matches the current running phase.

[0080] In some embodiments, the cleaning device can comprehensively predict the crash tolerance level by integrating the current functional node information corresponding to each process, thereby determining the current crash tolerance duration of the entire cleaning device in the current operating phase. Specifically, the cleaning device can extract features from the current functional node information corresponding to each process, normalize the extracted features, concatenate the normalized features, and make an overall prediction based on the concatenated features to determine the current crash tolerance duration of the entire cleaning device in the current operating phase. It can be understood that the current crash tolerance duration predicted by integrating the features from the current functional node information of each process is equivalent to a prediction result obtained by referring to the current functional node information of each process. Therefore, it is relatively comprehensive and accurate, accurately reflecting the crash detection requirements of each process. Furthermore, the target time interval determined based on this current crash tolerance duration can also meet the crash detection requirements of each process in the current operating phase.

[0081] In other embodiments, the cleaning device can also analyze the current functional node information corresponding to each process, and then combine the analysis results of the crash detection requirements of each process to determine the current crash tolerance time of the cleaning device.

[0082] It's understandable that the cleaning equipment can directly use the current crash tolerance duration as the target time interval. Alternatively, the cleaning equipment can multiply the current crash tolerance duration by a preset duration adjustment parameter to obtain the target time interval.

[0083] In the above embodiments, the current crash tolerance time of the cleaning equipment is determined based on the current functional node information corresponding to each process in multiple processes; and the target time interval is determined based on the current crash tolerance time. That is, the most suitable target time interval that best matches the current operating stage can be dynamically determined based on the current functional node information to trigger the monitoring script for crash detection, further improving applicability and rationality, thereby reducing unnecessary resource waste and triggering crash detection in a timely manner.

[0084] In some embodiments, determining the current crash tolerance duration of the cleaning device based on the current functional node information includes: determining the current crash tolerance sub-duration of each process based on the current functional node information of each process in the multiple processes; and determining the current crash tolerance duration of the cleaning device based on the current crash tolerance sub-duration of each process.

[0085] The crash tolerance duration for each process is the maximum crash duration that each process can withstand during its current running phase.

[0086] Specifically, the cleaning equipment can analyze the current functional node information corresponding to each process and perform crash detection requirement analysis on each process to determine the current crash tolerance sub-duration for each process. It can be understood that the current crash tolerance sub-duration for each process can reflect the crash detection requirements of each process to some extent. The cleaning equipment can comprehensively consider the current crash tolerance sub-durations of each process to determine the current crash tolerance duration of the cleaning equipment.

[0087] In some embodiments, a corresponding preset crash tolerance time is pre-set for each functional node. The cleaning device can find the corresponding preset crash tolerance time according to the current functional node information of each process, and obtain the current crash tolerance sub-time corresponding to each process.

[0088] In some embodiments, the cleaning device can select the minimum value from the current crash tolerance sub-durations corresponding to each process to obtain the minimum crash tolerance sub-duration, and then determine the current crash tolerance duration of the cleaning device based on the minimum crash tolerance sub-duration. Specifically, the cleaning device can directly use the minimum crash tolerance sub-duration as the current crash tolerance duration of the cleaning device, or the cleaning device can multiply the minimum crash tolerance duration by a preset adjustment coefficient to obtain the current crash tolerance duration of the cleaning device. This application does not limit how the target time interval is obtained based on the minimum crash tolerance duration.

[0089] In other embodiments, the cleaning device may also perform a weighted summation of the current crash tolerance sub-durations corresponding to each process to obtain the current crash tolerance duration of the cleaning device.

[0090] To facilitate understanding, we will now combine... Figure 2 Let's illustrate with examples. Figure 2 This is a schematic diagram illustrating the principle of determining a target time interval in one embodiment. (Refer to...) Figure 2Functional nodes 1 and 2 are assigned to process p1, functional nodes 3 and 4 to process p2, and functional nodes 5 and 6 are assigned to process p3. Assuming the current execution is in the first running phase, during this phase, process p1 executes to functional node 1, process p2 executes to functional node 3, and process p3 executes to functional node 5. Therefore, based on the determined crash tolerance sub-durations for each of functional nodes 1, 3, and 5, the current crash tolerance duration of the cleaning equipment in the first running phase can be determined, thus establishing a target time interval of 3 seconds to match the first running phase. Therefore, in the first running phase, a monitoring script can be triggered every 3 seconds to perform crash detection. If subsequent execution reaches the second running phase (i.e., the second running phase becomes the current running phase), and within this phase, process p1 executes to functional node 2, process p2 executes to functional node 4, and process p3 executes to functional node 6, then the current crash tolerance duration of the cleaning equipment in the second running phase can be determined based on the crash tolerance sub-durations corresponding to functional nodes 2, 4, and 6. This allows for the determination of a target time interval of 5 seconds that matches the second running phase. Therefore, in the second running phase, a monitoring script can be triggered every 5 seconds to perform crash detection. This dynamically determines a reasonable target time interval that matches each running phase.

[0091] In the above embodiments, based on the current functional node information corresponding to each process in multiple processes, the current crash tolerance sub-duration of each process can be accurately analyzed. Furthermore, by combining the current crash tolerance sub-duration of each process, the current crash tolerance duration of the cleaning equipment can be accurately determined. Thus, the target time interval can be accurately and reasonably determined.

[0092] In some embodiments, during the operation of the cleaning equipment, a monitoring script is used to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment, including at least one of the following processes: during the operation of the cleaning equipment, the monitoring script queries the process identifiers of multiple processes; based on the query results, the crashed processes among the multiple processes are detected; during the operation of the cleaning equipment, the monitoring script sends probe messages to multiple processes respectively, and based on the response results of the multiple processes to the probe messages, the crashed processes among the multiple processes are detected.

[0093] In some embodiments, if a process is online, its process ID is recorded and can be queried. Therefore, the cleaning device can query the process IDs of multiple processes distributed to the functional node using a monitoring script. For example, the cleaning device can query the process IDs of multiple processes from the online process list. If the process ID is found, it means that the process corresponding to the queried process ID is online and has not crashed. If the process ID is not found, it means that the process corresponding to the unqueried process ID is offline and has crashed.

[0094] To make it easier to understand, let's illustrate with an example. Suppose there are three processes, p1, p2, and p3. The monitoring script will periodically check if it can find the identifiers for p1, p2, and p3 according to a target time interval. If it can find p1 and p2, but not p3, it can be determined that p3 has crashed, while p1 and p2 are running normally.

[0095] In other embodiments, the cleaning device can also send probe messages to multiple processes via a monitoring script. If a response message is received from a process in response to the probe message, it indicates that the process has not crashed. If no response message is received from a process, it indicates that the process has not responded to the probe message, and it can be determined that the process has crashed. For example, if probe messages are sent to processes p1, p2, and p3 respectively, and response messages are received from p1 and p2 but not from p3, it indicates that p1 and p2 are communicating normally and are considered normal operating processes, while p3 is unable to communicate normally and is considered a crashed process.

[0096] It is understood that the cleaning equipment can perform either of the two crash detection methods mentioned above, or it can perform both crash detection methods in parallel. That is, it can detect the crashed process by querying the process identifier and by sending probe messages.

[0097] If the two crash detection methods described above are executed in parallel, the process that has crashed can be ultimately determined based on the results of both methods. Specifically, for each process, if both crash detection methods determine that the process has crashed, then the process has been definitively identified as crashed. If only one crash detection method determines that the process has crashed, then the process can be either not considered a crashed process or a second crash detection can be performed on that process, for example, by re-executing at least one of the aforementioned crash detection methods to determine the final detection result. It can be understood that combining the two crash detection methods and performing a second crash detection significantly improves the accuracy of crash detection.

[0098] In the above embodiments, the monitoring script can conveniently and accurately detect crashed processes by querying process identifiers or sending probe information.

[0099] In some embodiments, after a process restarts, the restarted process is reconnected through a custom communication library so that the restarted process can perform subsequent inter-process communication based on shared memory. This includes: after the process restarts, calling a preset function in the custom communication library to rewrite the shared memory communication information of the restarted process into shared memory so that the restarted process can perform subsequent inter-process communication based on shared memory.

[0100] Among them, shared memory communication information is the information required for communication using shared memory, that is, the information required for processes to use shared memory for inter-process communication.

[0101] The default function in the custom communication library is a custom function designed to enable process reconnection. In other words, this default function is a specific function used to implement process reconnection.

[0102] Specifically, after a process restarts, the cleaning device can call a preset function in a custom communication library to rewrite the shared memory communication information of the restarted process into shared memory. In this way, other normally running processes of the cleaning device can recognize that the restarted process has occurred based on the written shared memory communication information and resume communication with it, thus enabling subsequent inter-process communication based on shared memory.

[0103] In some embodiments, shared memory communication information may include the process identifier of the restarted process.

[0104] In other embodiments, in addition to including the process identifier of the restarted process, the shared memory communication information may also include at least one of the shared memory address used by the restarted process or the shared memory address that the process can receive.

[0105] In the above embodiments, by calling the preset function in the custom communication library, the restarted process can be conveniently and efficiently resume using shared memory, thereby facilitating the restoration of inter-process communication and improving cleaning efficiency.

[0106] In some embodiments, the method further includes: determining the functional nodes assigned in the crashed process; if there are multiple assigned functional nodes, obtaining historical process crash records; analyzing the historical process crash records to predict the problematic functional node from the multiple assigned functional nodes; the problematic functional node is the functional node that is predicted and located as the cause of the crash in the process.

[0107] It's understandable that the functional nodes of a cleaning device can be distributed across multiple processes, with each process potentially assigned one or more functional nodes. Therefore, if a process assigned only one functional node crashes, the cause can be directly identified as a problem with that functional node. In other words, the problematic functional node can be directly identified as the one causing the crash. This allows for a very convenient and rapid determination of the cause of the crash.

[0108] If multiple nodes are allocated to a process that crashes, the cleaning device can access historical process crash records. These records are the relevant information for processes that have already crashed. The cleaning device can analyze these historical crash records to predict the problematic functional node from among the multiple allocated functional nodes.

[0109] To facilitate understanding, we will now combine... Figure 3 Let's illustrate with examples. Figure 3 A schematic diagram illustrating the principle of problem localization in one embodiment. (Refer to...) Figure 3 The middle platform functional node 1 is assigned to process p1, the radar planning functional node 2 is assigned to process p2, and functional nodes 3 and 4 are assigned together to process p3. If process p1 crashes, it can be directly located that the problem was caused by a problem with the middle platform functional node 1. If process p3 crashes, historical process crash records can be analyzed to easily identify the functional node that ultimately caused the crash from functional nodes 3 and 4.

[0110] In some embodiments, the cleaning device can analyze historical process crash records to obtain at least one common problem function node. A common problem function node is a function node that typically causes problems. Then, the assigned multiple function nodes are compared with the identified common problem function nodes, and the function node that matches the identified common problem function node is selected as the problem function node that caused the current process crash.

[0111] In other embodiments, the cleaning device can also predict the probability of each functional node in the crashing process causing a crash based on historical crash records, and determine the final problematic functional node from multiple functional nodes in the crashing process based on the predicted probability. Specifically, the cleaning device can analyze the characteristics of historical crash processes that have experienced crashes based on historical crash records, and obtain information about each functional node in the crashing process to analyze the characteristics of each functional node in the crashing process. It can then calculate the feature similarity between the characteristics of the historical crash process and the characteristics of each functional node in the crashing process, and determine the probability of each functional node in the crashing process causing a crash based on the calculated feature similarity. The probability of causing a crash is positively correlated with the magnitude of the feature similarity; that is, the higher the feature similarity between each functional node in the crashing process and the historical crash process, the greater the probability of causing a crash, and vice versa.

[0112] In the above embodiments, when there are multiple functional nodes assigned in the crashed process, the problematic functional node can be accurately predicted from the multiple assigned functional nodes by analyzing historical process crash records, thereby quickly and accurately determining the cause of the crash.

[0113] like Figure 4 As shown, in another embodiment, a process processing method for a cleaning device is provided, also illustrated using an application to a cleaning device as an example. Specifically, it includes the following steps:

[0114] Step 402: During the operation of the cleaning equipment, determine the current functional node information corresponding to each process in multiple processes.

[0115] Step 404: Determine the current crash tolerance sub-duration for each process based on the current functional node information corresponding to each process in the multiple processes.

[0116] Step 406: Determine the current crash tolerance duration of the cleaning equipment based on the current crash tolerance duration of each process.

[0117] Step 408: Determine the target time interval that matches the current running phase based on the current crash tolerance duration.

[0118] Step 410: Trigger the execution of the monitoring script at the target time interval to query the process identifiers of multiple processes; detect the crashed processes among the multiple processes based on the query results; or, send probe messages to multiple processes respectively through the monitoring script, and detect the crashed processes among the multiple processes based on the response results of the multiple processes to the probe messages.

[0119] Step 412: If a crashed process is detected, restart the crashed process; after the process restarts, call the preset function in the custom communication library to rewrite the shared memory communication information of the restarted process into the shared memory, so that the restarted process can realize subsequent inter-process communication based on the shared memory.

[0120] Step 414: Determine the functional nodes assigned to the crashed process. If there are multiple assigned functional nodes, proceed to step 416; if there is only one assigned functional node, proceed to step 418.

[0121] Step 416: Obtain historical process crash records; analyze historical process crash records to predict problematic functional nodes from the multiple allocated functional nodes.

[0122] Step 418: Identify the functional node assigned to the crashed process as the problematic functional node.

[0123] The process handling method described above for the cleaning equipment distributes the functional nodes of the cleaning equipment across multiple processes. A custom-developed shared-memory communication library—a custom communication library—adapted to the operating platform of the cleaning equipment, enables communication between these processes. This ensures that even if some processes crash, the cleaning-related work of other functional nodes remains unaffected, improving cleaning efficiency to some extent. Furthermore, by monitoring scripts to detect crashes in the distributed processes, crashed processes can be detected and restarted promptly. After restarting, the custom communication library reconnects the restarted process, ensuring subsequent inter-process communication and quickly restoring the normal operation of the cleaning equipment, further enhancing cleaning efficiency.

[0124] Furthermore, it can dynamically determine the target time interval based on the current functional node information, thereby triggering monitoring scripts for crash detection more accurately and reasonably, ensuring both the timeliness of crash detection and reducing unnecessary waste of system resources. In addition, it can quickly and accurately identify problematic functional nodes, that is, quickly and accurately determine the cause of the crash.

[0125] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0126] Based on the same inventive concept, this application also provides a process processing apparatus for implementing the process processing method of the cleaning equipment described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more process processing apparatus embodiments of the cleaning equipment provided below can be found in the limitations of the process processing method of the cleaning equipment described above, and will not be repeated here.

[0127] In one embodiment, such as Figure 5 As shown, a process processing device for a cleaning device is provided, including: a crash detection module 502 and a process restart module 504, wherein:

[0128] The crash detection module 502 is used to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment during operation by monitoring scripts. The multiple processes communicate with each other using shared memory based on a custom communication library. The custom communication library is a custom-developed shared memory communication library adapted to the operating platform of the cleaning equipment.

[0129] The process restart module 504 is used to restart the crashed process when the crash detection module 502 detects a crashed process. After the process is restarted, the restarted process is reconnected through a custom communication library so that the restarted process can realize subsequent inter-process communication based on shared memory.

[0130] In some embodiments, the crash detection module 502 is specifically used to determine a target time interval for triggering crash detection; the target time interval is determined based on the crash tolerance information of the cleaning equipment; the crash tolerance information is information characterizing the crash tolerance capability of the cleaning equipment; during the operation of the cleaning equipment, a monitoring script is triggered to be executed according to the target time interval to perform crash detection on multiple processes distributed among the functional nodes of the cleaning equipment.

[0131] In some embodiments, the crash detection module 502 is specifically used to determine the current functional node information corresponding to each process in multiple processes during the operation of the cleaning equipment; the current functional node information is the relevant information of the functional node currently being executed by each process; the current functional node information is included in the crash tolerance information; the current crash tolerance duration of the cleaning equipment is determined based on the current functional node information; and the target time interval is determined based on the current crash tolerance duration.

[0132] In some embodiments, the crash detection module 502 is specifically used to determine the current crash tolerance sub-duration of each process based on the current functional node information of each process in the multiple processes; and to determine the current crash tolerance duration of the cleaning equipment based on the current crash tolerance sub-duration of each process.

[0133] In some embodiments, the crash detection module 502 is specifically used to query the process identifiers of multiple processes through a monitoring script during the operation of the cleaning equipment; detect the crashed process among the multiple processes based on the query results; and / or, during the operation of the cleaning equipment, send probe messages to multiple processes respectively through a monitoring script, and detect the crashed process among the multiple processes based on the response results of the multiple processes to the probe messages.

[0134] In some embodiments, the process restart module 504 is specifically used to call a preset function in a custom communication library after the process restarts, and rewrite the shared memory communication information of the restarted process into the shared memory, so that the restarted process can realize subsequent inter-process communication based on the shared memory; wherein, the shared memory communication information is the information required for communication using shared memory.

[0135] like Figure 6 As shown, in some embodiments, the device further includes:

[0136] Problem localization module 506 is used to determine the functional nodes assigned in the crashed process; when there are multiple assigned functional nodes, it obtains historical process crash records; it analyzes the historical process crash records to predict the problem functional node from the multiple assigned functional nodes; the problem functional node is the functional node that is predicted and located as the cause of the crash.

[0137] The process processing device of the aforementioned cleaning equipment distributes the functional nodes of the cleaning equipment across multiple processes. A custom-developed shared-memory communication library—a custom communication library—adapted to the operating platform of the cleaning equipment, enables communication between these processes. This ensures that even if some processes crash, the cleaning-related work of other functional nodes remains unaffected, improving cleaning efficiency to some extent. Furthermore, by monitoring scripts to detect crashes in the distributed processes, crashed processes can be detected and restarted promptly. After restarting, the custom communication library reconnects the restarted process, ensuring subsequent inter-process communication and quickly restoring the normal operation of the cleaning equipment, further enhancing cleaning efficiency.

[0138] Each module in the process processing device of the aforementioned cleaning equipment can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the cleaning equipment in hardware form or independent of it, or stored in the memory of the cleaning equipment in software form, so that the processor can call and execute the operations corresponding to each module.

[0139] In one embodiment, a cleaning device is provided, the internal structure of which can be shown in the following diagram. Figure 7 As shown, the cleaning device includes a processor, memory, input / output interfaces, and a communication interface. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a process handling method for the cleaning device.

[0140] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the cleaning equipment to which the present application is applied. Specific cleaning equipment may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0141] In one embodiment, a cleaning device is provided, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the methods provided in the embodiments of this application.

[0142] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the methods provided in the embodiments of this application.

[0143] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the methods provided in the embodiments of this application.

[0144] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0145] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0146] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0147] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. 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 protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A process handling method for a cleaning device, comprising: During the operation of the cleaning equipment, a monitoring script is used to detect crashes in multiple processes distributed across the functional nodes of the cleaning equipment. The central functional node, radar planning functional node, and other functional nodes of the cleaning equipment are distributed in different processes. The multiple processes communicate with each other using shared memory based on a custom communication library. The custom communication library is a custom-developed shared memory communication library adapted to the operating system and running environment of the cleaning equipment. The custom communication library is equipped with custom preset function functions for implementing process reconnection. If a crashed process is detected, restart the crashed process; After the crashed process restarts, the preset function in the custom communication library is called. The preset function rewrites the shared memory communication information of the restarted process into the shared memory, so that other normally running processes can determine that the crashed process has restarted based on the shared memory communication information and resume communication with the restarted process. This allows the restarted process to achieve subsequent inter-process communication based on the shared memory.

2. The method according to claim 1, characterized in that, The process of detecting crashes in multiple processes distributed across the functional nodes of the cleaning equipment during its operation, via a monitoring script, includes: A target time interval is determined to trigger crash detection; the target time interval is determined based on the crash tolerance information of the cleaning equipment; the crash tolerance information is information characterizing the crash tolerance capability of the cleaning equipment. During the operation of the cleaning equipment, the monitoring script is executed according to the target time interval to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment.

3. The method according to claim 2, characterized in that, The target time interval for triggering crash detection includes: During the operation of the cleaning equipment, the current functional node information corresponding to each of the multiple processes is determined; the current functional node information is the relevant information of the functional node currently being executed by each process; the current functional node information is included in the crash tolerance information; Based on the current functional node information, determine the current crash tolerance time of the cleaning equipment; The target time interval is determined based on the current crash tolerance duration.

4. The method according to claim 3, characterized in that, The step of determining the current crash tolerance time of the cleaning equipment based on the current functional node information includes: Based on the current functional node information corresponding to each of the multiple processes, determine the current crash tolerance sub-duration of each process; The current crash tolerance duration of the cleaning equipment is determined based on the crash tolerance duration corresponding to each process.

5. The method according to claim 1, characterized in that, During the operation of the cleaning equipment, a monitoring script is used to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment, including at least one of the following processing methods: During the operation of the cleaning equipment, the process identifiers of the multiple processes are queried through a monitoring script; based on the query results, the processes that have crashed are detected. During the operation of the cleaning equipment, a monitoring script sends probe messages to the multiple processes respectively. Based on the response results of the multiple processes to the probe messages, the process that has crashed is detected.

6. The method according to claim 1, characterized in that, The shared memory communication information is the information required for communication using the shared memory.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Determine the functional nodes allocated in the crashed process; If there are multiple assigned functional nodes, retrieve historical process crash records; Analyze historical process crash records to predict problematic functional nodes from multiple assigned functional nodes; the problematic functional node is the functional node that is predicted and located as the cause of the crash.

8. A process processing device for a cleaning equipment, characterized in that, The device includes: The crash detection module is used to perform crash detection on multiple processes distributed across the functional nodes of the cleaning equipment during its operation via a monitoring script. The cleaning equipment's platform functional nodes, radar planning functional nodes, and other functional nodes are distributed across different processes, and these multiple processes communicate with each other using shared memory based on a custom communication library. The custom communication library is a custom-developed shared memory communication library adapted to the cleaning equipment's dedicated operating system and runtime environment, and it is equipped with custom preset function functions for enabling process reconnection. The process restart module is used to restart the crashed process when the crash detection module detects a crash. After the crashed process restarts, it calls the preset function in the custom communication library to rewrite the shared memory communication information of the restarted process into the shared memory. This allows other normally running processes to determine that the crashed process has restarted based on the shared memory communication information and resume communication with the restarted process. This enables the restarted process to perform subsequent inter-process communication based on the shared memory.

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

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A cleaning device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Program running monitoring method and device, terminal and storage medium

    CN113407414A

  • Real-time database fault recovery method and system, storage medium and server

    CN113986594A