Cleaning robot event reporting method and system and cleaning robot

Abstract

The invention provides an event reporting method and system for a cleaning robot and the cleaning robot, and the method comprises the steps: responding to the triggering of a target event of the cleaning robot, and determining a target display platform corresponding to the target event according to the type of the target event; wherein the event information of the cleaning robot has multiple display platforms, and each display platform corresponds to users with different roles in the operation and maintenance work of the cleaning robot; and reporting the target event to the target display platform so as to display event information of the target event to a target user through the target display platform. Therefore, pertinence and effectiveness of event reporting can be improved, and the problem that roles receive irrelevant event information and the meaning of the event information cannot be clarified is avoided.

Description

Technical Field

[0001] This application relates to the field of robotics technology, and in particular to an event reporting method, system, and cleaning robot for a cleaning robot. Background Technology

[0002] Commercial cleaning robots are now widely used in large public places such as shopping malls, schools, hospitals, and hotels. Daily operation of commercial cleaning robots requires human maintenance. For example, if they are trapped, have low power, are full of sewage, or have empty clean water, maintenance personnel need to operate the robot to ensure it continues to function normally.

[0003] However, currently, various events generated during the operation of commercial robots are difficult to report to maintenance personnel in a timely and accurate manner. For example, some personnel do not receive event information, while others receive too much irrelevant event information and cannot understand the meaning of the event information. This leads to the inability to perform maintenance operations on the cleaning robot in a timely and correct manner, thus affecting the cleaning efficiency of the cleaning robot. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide an event reporting method, system and cleaning robot for cleaning robots, so as to solve the problem that it is difficult to report various events generated by commercial robots during operation to maintenance personnel in a timely and accurate manner.

[0005] This application provides an event reporting method for a cleaning robot, the method comprising: In response to the triggering of a target event by the cleaning robot, the target display platform corresponding to the target event is determined according to the type of the target event; wherein, the event information of the cleaning robot has multiple display platforms, and each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot; The target event is reported to the target display platform so that the event information of the target event can be displayed to the target user through the target display platform.

[0006] Furthermore, the demonstration platform includes: a cloud platform, a body application installed on the cleaning robot body, and a remote application installed on a terminal device that communicates with the cleaning robot. The cloud platform users include R&D and after-sales personnel from the manufacturer of the cleaning robot, the main application users include on-site operators in the working environment of the cleaning robot, and the remote application users include management personnel with management functions over the on-site operators.

[0007] Furthermore, determining the target display platform corresponding to the target event based on the type of the target event includes: Based on the type of the target event, find the pre-configured mapping relationship between the event type and the display platform, and determine the target display platform; The steps for configuring the mapping relationship include: Determine the meaning of each event that the cleaning robot can trigger during operation, and define the attribute information of each event; wherein, the attribute information includes at least one of the following: the event display platform, the role of the user authorized to receive the event, and the severity of the event; The events are categorized based on their attribute information, and the corresponding display platform for each type of event is determined to obtain the mapping relationship.

[0008] Furthermore, the event types include: notification, statistical, status, reminder, potential hazard, problem, and malfunction. Notification events refer to routine notifications that do not require processing; statistical events refer to alarm information that requires no processing and is only of concern to R&D personnel; status events refer to the routine states of the cleaning robot during operation that on-site operators can handle independently without guidance; reminder events refer to abnormal states of the cleaning robot during operation that on-site operators can handle independently with guidance; potential hazard events refer to events that do not affect the use of the cleaning robot but pose a potential hazard to its operation; problem events refer to issues that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel, which need to be resolved by on-site operators; and malfunction events refer to malfunctions that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel. The display platforms for notification events include the cloud platform and the remote application; the display platforms for statistical events include the cloud platform; the display platforms for status events include the cloud platform, the entity application, and the remote application; the display platforms for reminder events include the cloud platform, the entity application, and the remote application; the display platforms for potential incidents include the cloud platform and the entity application; the display platforms for problem events include the cloud platform, the entity application, and the remote application; and the display platforms for fault events include the cloud platform, the entity application, and the remote application.

[0009] Furthermore, the method also includes: Configure the display method for each type of event on each corresponding display platform, so as to display the event information of each type of event to the target user on the corresponding target display platform in accordance with the display method.

[0010] Furthermore, the method also includes: the cleaning robot providing a first graphical user interface for the main body application via a body display screen; the main body application displaying event information of the target event on the first graphical user interface in a display manner corresponding to the type of the target event; the display manner including at least one of the following: displaying alarm information entries, displaying status pop-ups, and displaying fault information records on the first graphical user interface; the alarm information entries presenting processing prompts corresponding to the type of the target event, and the fault information records presenting detailed information about the target event; Status events are displayed in various ways, including displaying a status pop-up window; alert events are displayed in various ways, including displaying alarm information entries; potential hazard events are displayed in various ways, including displaying fault information records; problem events are displayed in various ways, including displaying alarm information entries and fault information records; and fault events are displayed in various ways, including displaying alarm information entries and fault information records.

[0011] Furthermore, the event information of the target event is displayed to the target user through the target display platform, including: For the status pop-up window, the status pop-up window corresponding to the target event is displayed on the first graphical user interface; in response to the triggering operation of the confirmation control in the status pop-up window, the status pop-up window is canceled from display. For the alarm information entry, the alarm information entry corresponding to the target event is displayed on the first graphical user interface, wherein the visual display parameters of the alarm information entry correspond to the severity of the target event; For the fault information record, in response to the selection operation of the view control in the alarm information entry, the fault information record is displayed.

[0012] Furthermore, the reminder events can be divided into: fault assistance sub-events, task self-check sub-events, and consumable maintenance sub-events; The fault assistance sub-category events include: charging abnormality, cleaning robot unable to move, negative pressure abnormality, and elevator control-related alarms; Task self-check sub-events include: dust bag not installed properly, cleaning robot needs to be unlocked, handle not lowered, dust mop not installed, and battery level below preset value; Consumable maintenance subcategories include: tangled or stuck foreign objects in the roller brush, abnormal suction, HEPA filter blockage, sensors requiring wiping, and dust bag reaching its maximum capacity.

[0013] This application embodiment also provides an event reporting system for a cleaning robot, the system including a cleaning robot and multiple display platforms; each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot; The cleaning robot, in response to the triggering of a target event, determines the target display platform corresponding to the target event based on the type of the target event, and reports the target event to the target display platform; The target display platform displays event information about the target event to the target user.

[0014] This application embodiment also provides a cleaning robot, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the cleaning robot is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the event reporting method for the cleaning robot described above are performed.

[0015] The embodiments of this application have the following beneficial technical effects: Based on the type of target event triggered by the cleaning robot, the corresponding target display platform is determined for event reporting. Each display platform corresponds to a user with different roles in the operation and maintenance of the cleaning robot, so that only the role that is concerned about this type of event can receive the event information. This improves the relevance and effectiveness of event reporting and avoids the problem of roles receiving irrelevant event information and not understanding the meaning of the event information.

[0016] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart of an event reporting method for a cleaning robot provided in an embodiment of this application is shown; Figures 2(a) to 2(e) show schematic diagrams of the first graphical user interface provided in the embodiments of this application; Figure 3 A schematic diagram of the structure of a cleaning robot provided in an embodiment of this application is shown. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. Based on the embodiments of this application, every other embodiment obtained by those skilled in the art without inventive effort falls within the scope of protection of this application.

[0020] Research has shown that commercial cleaning robots are now widely used in large public places such as shopping malls, schools, hospitals, and hotels. These robots offer various dry and wet cleaning modes, including washing, mopping, sweeping, and dusting, and are equipped with corresponding cleaning components for each mode. These components include rollers, side brushes, water pumps, squeegees, fans, clean and dirty water tanks, batteries, displays, and control panels. Daily operation of commercial cleaning robots requires human maintenance. For example, if the robot is trapped, has low power, is full of dirty water, or empty of clean water, maintenance personnel need to operate it to ensure its continued normal operation.

[0021] However, currently, various events generated during the operation of commercial robots are difficult to report to maintenance personnel in a timely and accurate manner. For example, some personnel do not receive event information, while others receive too much irrelevant event information and cannot understand the meaning of the event information. This leads to the inability to perform maintenance operations on the cleaning robot in a timely and correct manner, thus affecting the cleaning efficiency of the cleaning robot.

[0022] Based on this, this application provides an event reporting method for cleaning robots to solve the problem that various events generated by commercial robots during operation are difficult to report to maintenance personnel in a timely and accurate manner.

[0023] The event reporting method in this application embodiment can be executed directly by the robot (such as by the controller in the robot body) or by a controller independent of the robot (such as a cloud server).

[0024] Please see Figure 1 , Figure 1 This is a flowchart illustrating an event reporting method for a cleaning robot provided in an embodiment of this application. Figure 1 As shown in the embodiments of this application, the event reporting method includes: S101. In response to the triggering of a target event by the cleaning robot, determine the target display platform corresponding to the target event based on the type of the target event.

[0025] In this step, a mapping relationship between the event types of the cleaning robot and the display platforms can be pre-configured. The event information of the cleaning robot has multiple display platforms, with each event corresponding to at least one display platform. Therefore, when a target event is triggered, the display platform corresponding to the type of the target event can be found based on this mapping relationship and selected as the target display platform.

[0026] In this embodiment of the application, each display platform corresponds to a user with different roles in the operation and maintenance of the cleaning robot. Users can use the corresponding display platform and receive information through the display platform according to their different roles in the operation and maintenance of the cleaning robot.

[0027] S102. The target event is reported to the target display platform so as to display the event information of the target event to the target user through the target display platform.

[0028] In this step, the target event is reported to the target display platform. The reported data includes at least the type of the target event, and may also include other records of the target event, such as the time of occurrence, location of occurrence, and event description. The reported data for the same event may differ for different display platforms, and users with different roles are allowed to configure the reported data for each type of event required by their respective display platforms. Afterwards, the target display platform displays the event information of the target event to the target user based on the received reported data.

[0029] This ensures that users on the platform receive information about the events they are interested in, and that the information contains only the reported data that users are interested in. This further improves the relevance and effectiveness of event reporting, prevents roles from receiving irrelevant event information, and reduces interference from redundant information.

[0030] In this embodiment, a corresponding target display platform is determined based on the type of target event triggered by the cleaning robot for event reporting. Each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot, ensuring that only the role concerned with this type of event receives the event information. This improves the relevance and effectiveness of event reporting, preventing roles from receiving irrelevant event information and failing to understand its meaning. Indirectly, roles concerned with this type of event can take appropriate action after receiving the event information, helping to ensure the working efficiency of the cleaning robot.

[0031] The implementation details of the event reporting method provided in the embodiments of this application will be described below.

[0032] In one example, in step S101, when the execution subject of the event reporting method is the controller on the cleaning robot body, the controller can determine the different events triggered based on the various sensors installed on the robot body, and find the mapping relationship between the pre-configured event type and the display platform according to the type of the triggered target event, and determine the target display platform.

[0033] The steps for configuring the mapping relationship include: Step 1: Determine the meaning of each event that the cleaning robot can trigger during operation, and define the attribute information of each event.

[0034] The attribute information includes at least one of the following: the event display platform, the role of the user authorized to receive the event, and the severity of the event.

[0035] In this step, developers configure a standardized set of event metadata for each triggered event, including the event's ID, code, name, and meaning. The event meaning includes a description of the phenomenon occurring to the robot and the required handling methods. Therefore, based on the event meaning, the roles that need to understand and handle the event can be determined, i.e., the roles of users authorized to receive the event and the corresponding event display platforms can be identified. Based on the event meaning, the severity of the event can also be determined.

[0036] Step 2: Classify events according to their attribute information and determine the display platform corresponding to each type of event to obtain the mapping relationship.

[0037] In this step, events that are displayed on the same platform or have the same receiving role and are of similar severity can be grouped into one category, and the event type can be configured to correspond to the display platform. The mapping relationship can be configured in this way.

[0038] In this way, the anomaly reporting in this embodiment of the application classifies the message type in a more detailed manner according to the reporting platform, information receiving role, and severity, so that all kinds of events that may occur during robot operation have a clear corresponding receiving role, and can be reported to maintenance personnel in a timely and accurate manner after being triggered.

[0039] In one example, the demonstration platform includes: a cloud platform, a body application installed on the cleaning robot body, and a remote application installed on a terminal device that communicates with the cleaning robot.

[0040] When the robot acts as the executor, the robot's processor can communicate with the cloud platform to report target events to the cloud platform; report target events to the body application installed in the processor or the body application installed in other body controllers connected to the processor; and the processor can communicate with a remote server to report target events to the remote application installed on the terminal device through the remote server.

[0041] The cloud platform users include R&D and after-sales personnel from the manufacturer of the cleaning robot, the main application users include on-site operators in the working environment of the cleaning robot, and the remote application users include management personnel with management functions over the on-site operators.

[0042] The cloud platform allows manufacturers' R&D and after-sales personnel to aggregate target events generated during the operation of various cleaning robots. This aggregated data helps guide product iteration and improvement. Furthermore, when after-sales personnel receive a problem with a specific cleaning robot, they can retrieve relevant data from the cloud platform based on the robot's identification code to pinpoint the cause of the malfunction and, combined with historical handling methods for other cleaning robots, provide an effective solution. Field operators, typically performing maintenance on the cleaning robots within their designated work environment (e.g., cleaners in a venue), report target events to the robot's application. This allows field operators to be aware of event occurrences in real time and address them promptly. Management personnel, such as logistics supervisors, often do not work in the robot's operational environment. Therefore, remote applications allow them to promptly understand event occurrences and coordinate with field operators for appropriate responses.

[0043] Thus, this embodiment of the application configures a corresponding display platform for each role based on the work characteristics of different roles in the operation and maintenance of cleaning robots, which can improve the effectiveness of event reporting and help the operation and maintenance work proceed smoothly.

[0044] In this application embodiment, the types of events may include: notification, statistics, status, reminder, potential problems, issues, and faults.

[0045] Among them, notification events refer to routine notifications that do not require processing, such as task start and task end; statistical events refer to alarm information that does not require processing and is only of concern to R&D personnel, such as temporary obstacles and escape behavior; status events refer to routine states during the operation of the cleaning robot that can be handled independently by on-site operators without guidance, such as low battery and empty water supply; reminder events refer to abnormal states during the operation of the cleaning robot that can be handled independently by on-site operators with guidance, such as dust bag not installed properly, laser stains needing to be wiped, robot stuck on virtual wall and needing to be manually pushed to an open space; hazard events refer to events that do not affect the use of the cleaning robot but pose a hazard to its operation, such as no IMU data; problem events refer to issues that affect the use of the cleaning robot that require on-site operators to resolve under the manufacturer's manual guidance, such as motor overload and positioning loss; and fault events refer to faults that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel, such as short circuit in the driver and disconnection of the driver.

[0046] Accordingly, the display platforms for notification events include the cloud platform and the remote application; the display platforms for statistical events include the cloud platform; the display platforms for status events include the cloud platform, the entity application, and the remote application; the display platforms for reminder events include the cloud platform, the entity application, and the remote application; the display platforms for potential incidents include the cloud platform and the entity application; the display platforms for problem events include the cloud platform, the entity application, and the remote application; and the display platforms for fault events include the cloud platform, the entity application, and the remote application.

[0047] In this way, the embodiments of this application have made a more detailed classification of the types of events that can be triggered by the cleaning robot, and configured a display platform corresponding to each type of event, so that only the roles that are interested in the event messages can receive the information through the display platform, making the reporting of messages more targeted and reducing the interference of irrelevant information.

[0048] More specifically, the reminder events can be divided into: fault assistance sub-events, task self-check sub-events, and consumable maintenance sub-events.

[0049] The fault assistance sub-category events include: charging abnormality, cleaning robot unable to move, negative pressure abnormality, and elevator control related alarms; the task self-check sub-category events include: dust bag not installed properly, cleaning robot needs to be unlocked, handrail not lowered, dust pusher not installed, and battery level lower than preset value; the consumable maintenance sub-category events include: roller brush has tangled or stuck foreign objects, suction abnormality, HEPA filter blockage, sensor needs to be wiped, and dust bag capacity reaches the upper limit.

[0050] Different events are configured with different triggering and self-recovery logics. When the triggering logic of an event is met, the event is triggered, and the corresponding target display platform is determined based on the event type and reported. The event information is then displayed to the target user through the target display platform. When the self-recovery logic of the event is met, the target display platform cancels the display of the event information, and the display disappears.

[0051] Furthermore, the event reporting method in this application embodiment also includes: Configure the display method for each type of event on each corresponding display platform, so as to display the event information of each type of event to the target user on the corresponding target display platform in accordance with the display method.

[0052] Thus, considering that users of different display platforms have different usage habits and work characteristics, the embodiments of this application can configure the display methods of different display platforms separately, which can improve the user experience and enable users to understand the event in a timely manner. In addition, different display methods can be configured for different types of events, so that users can visually understand some information about the event and distinguish the event type through the display platform.

[0053] In one possible implementation, for the main body application, the cleaning robot provides a first graphical user interface for the main body application via a body display screen. The main body application displays event information of the target event in the first graphical user interface in a display manner corresponding to the type of the target event.

[0054] Among them, the body display screen refers to the display screen mounted on the robot body, which can generally be set in a position such as the robot head that is easy for humans to observe and operate; the graphical user interface is an interface display format for human-computer communication, which allows users to use input devices such as mouse, keyboard and / or game controller to manipulate icons, logos or menu options on the screen, and also allows users to perform touch operations on the touch screen to manipulate icons or menu options on the screen to select commands, start programs or perform other tasks.

[0055] The display method on the main application includes at least one of the following: displaying alarm information entries, displaying status pop-ups, and displaying fault information records on the first graphical user interface; the status pop-ups present the current status of the robot related to the event; the alarm information entries present processing prompts corresponding to the type of the target event, and the fault information records present detailed information about the target event.

[0056] Corresponding to the examples above, the display methods for status events include displaying a status pop-up window; the display methods for alert events include displaying alarm information entries; the display methods for potential hazard events include displaying fault information records; the display methods for problem events include displaying both alarm information entries and fault information records; and the display methods for fault events include displaying both alarm information entries and fault information records. Additionally, the display method may also include thumbnail icons displayed in the status drop-down menu of the first graphical user interface.

[0057] In this way, on-site operators can intuitively understand different aspects of each type of event through the display on the first graphical user interface. Furthermore, the display method is related to the severity and urgency of the event. For example, for more serious and urgent problem events and fault events, the display method includes showing alarm information entries and fault information records; while the display method for regular status events includes showing status pop-ups.

[0058] Please refer to Figures 2(a) to 2(e), which are schematic diagrams of the first graphical user interface provided in the embodiments of this application.

[0059] In one possible implementation, step S102 involves displaying the event information of the target event to the target user through the target display platform, including: For the status pop-up window, the status pop-up window corresponding to the target event is displayed on the first graphical user interface; in response to the triggering operation of the confirmation control in the status pop-up window, the status pop-up window is canceled.

[0060] As shown in Figure 2(a), for status events, a corresponding status pop-up window a2 appears on the first graphical user interface a1 to visually display the specific event content, such as low battery, full clean water tank, and empty wastewater tank. On-site operators can perform corresponding maintenance operations on the cleaning robot based on the prompts in the status pop-up window a2; and can cancel the display of the status pop-up window a2 by clicking the confirmation control a3.

[0061] For each alarm information entry, the alarm information entry corresponding to the target event is displayed on the first graphical user interface.

[0062] The visual display parameters of the alarm information entries correspond to the severity of the target event. These parameters may include one or more of the following: display size, display pattern, display shape, display color, display transparency, display line type, and display line width. For example, the higher the severity of the event, the more vibrant the display color of the alarm information entry, allowing on-site operators to immediately identify the severity of the alarm. Furthermore, when there are multiple alarm information entries of the same type, they are displayed as a single entry.

[0063] As shown in Figure 2(b), for reminder events, alarm information entry b1 displays "The robot needs your assistance," which is displayed in a relaxed manner and can be in blue.

[0064] As shown in Figure 2(c), for problem-related events, alarm information entry b1 displays "The robot has a minor problem," which makes the operator slightly nervous, and the color can be dark yellow.

[0065] As shown in Figure 2(d), for problem-related events, alarm information entry b1 displays "Robot malfunction, please contact the administrator," which makes the operator pay more attention, and the color can be red.

[0066] For the fault information record, in response to the selection operation of the view control in the alarm information entry, the fault information record is displayed.

[0067] As shown in Figures 2(b) to (d), each alarm information entry has a "View Details" control b2. Clicking this control b2 will redirect to the fault information record shown in Figure 2(e), displaying detailed fault information. For example, the fault record displays the number of anomalies to be repaired and the basic information (serial number, name, and time) of each anomaly. Clicking on each anomaly to be repaired allows you to view more specific anomaly information, and it also supports manual completion of each anomaly after repair is finished.

[0068] Considering that on-site operators are generally responsible for performing routine maintenance operations and have limited ability to identify and process fault information, this embodiment prioritizes displaying alarm information entries, allowing users to immediately identify the severity of the alarm through visual effects and reducing unnecessary anxiety; detailed fault information records are only displayed after the alarm is triggered. This hierarchical display method avoids the problem of on-site operators receiving too many alarm messages at once without understanding the alarm content.

[0069] This application provides an event reporting method for a cleaning robot. The method determines the corresponding target display platform for event reporting based on the type of target event triggered in the cleaning robot. Each display platform corresponds to a user with different roles in the operation and maintenance of the cleaning robot, so that only the role that is concerned about this type of event can receive the event information. This improves the relevance and effectiveness of event reporting and avoids the role receiving irrelevant event information and being unable to understand the meaning of the event information.

[0070] Based on the same inventive concept, this application also provides an event reporting system for a cleaning robot. The system includes a cleaning robot and multiple display platforms; each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot. The cleaning robot, in response to the triggering of a target event, determines the target display platform corresponding to the target event based on the type of the target event, and reports the target event to the target display platform; The target display platform displays event information about the target event to the target user.

[0071] Furthermore, the demonstration platform includes: a cloud platform, a body application installed on the cleaning robot body, and a remote application installed on a terminal device that communicates with the cleaning robot. The cloud platform users include R&D and after-sales personnel from the manufacturer of the cleaning robot, the main application users include on-site operators in the working environment of the cleaning robot, and the remote application users include management personnel with management functions over the on-site operators.

[0072] Furthermore, the cleaning robot determines the target display platform corresponding to the target event based on the type of the target event, including: Based on the type of the target event, find the pre-configured mapping relationship between the event type and the display platform, and determine the target display platform; The steps for configuring the mapping relationship include: Determine the meaning of each event that the cleaning robot can trigger during operation, and define the attribute information of each event; wherein, the attribute information includes at least one of the following: the event display platform, the role of the user authorized to receive the event, and the severity of the event; The events are categorized based on their attribute information, and the corresponding display platform for each type of event is determined to obtain the mapping relationship.

[0073] Furthermore, the event types include: notification, statistical, status, reminder, potential hazard, problem, and malfunction. Notification events refer to routine notifications that do not require processing; statistical events refer to alarm information that requires no processing and is only of concern to R&D personnel; status events refer to the routine states of the cleaning robot during operation that on-site operators can handle independently without guidance; reminder events refer to abnormal states of the cleaning robot during operation that on-site operators can handle independently with guidance; potential hazard events refer to events that do not affect the use of the cleaning robot but pose a potential hazard to its operation; problem events refer to issues that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel, which need to be resolved by on-site operators; and malfunction events refer to malfunctions that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel. The display platforms for notification events include the cloud platform and the remote application; the display platforms for statistical events include the cloud platform; the display platforms for status events include the cloud platform, the entity application, and the remote application; the display platforms for reminder events include the cloud platform, the entity application, and the remote application; the display platforms for potential incidents include the cloud platform and the entity application; the display platforms for problem events include the cloud platform, the entity application, and the remote application; and the display platforms for fault events include the cloud platform, the entity application, and the remote application.

[0074] Furthermore, the display platform is also configured with a display method for each type of event on the corresponding display platform, so as to display the event information of each type of event to the target user in accordance with the display method.

[0075] Furthermore, the cleaning robot provides a first graphical user interface for the main body application via a display screen on its body; the main body application displays event information of the target event on the first graphical user interface in a display manner corresponding to the type of the target event; the display manner includes at least one of the following: displaying alarm information entries, displaying status pop-ups, and displaying fault information records on the first graphical user interface; the alarm information entries present processing prompts corresponding to the type of the target event, and the fault information records present detailed information about the target event; Status events are displayed in various ways, including displaying a status pop-up window; alert events are displayed in various ways, including displaying alarm information entries; potential hazard events are displayed in various ways, including displaying fault information records; problem events are displayed in various ways, including displaying alarm information entries and fault information records; and fault events are displayed in various ways, including displaying alarm information entries and fault information records.

[0076] Furthermore, the cleaning robot displays event information about the target event to the target user through the target display platform, including: For the status pop-up window, the status pop-up window corresponding to the target event is displayed on the first graphical user interface; in response to the triggering operation of the confirmation control in the status pop-up window, the status pop-up window is canceled from display. For the alarm information entry, the alarm information entry corresponding to the target event is displayed on the first graphical user interface, wherein the visual display parameters of the alarm information entry correspond to the severity of the target event; For the fault information record, in response to the selection operation of the view control in the alarm information entry, the fault information record is displayed.

[0077] Furthermore, the reminder events can be divided into: fault assistance sub-events, task self-check sub-events, and consumable maintenance sub-events; The fault assistance sub-category events include: charging abnormality, cleaning robot unable to move, negative pressure abnormality, and elevator control-related alarms; Task self-check sub-events include: dust bag not installed properly, cleaning robot needs to be unlocked, handle not lowered, dust mop not installed, and battery level below preset value; Consumable maintenance subcategories include: tangled or stuck foreign objects in the roller brush, abnormal suction, HEPA filter blockage, sensors requiring wiping, and dust bag reaching its maximum capacity.

[0078] It should be noted that the cleaning robot can perform any step of the event reporting method in the above method embodiments. For specific implementation, please refer to the method embodiments. Since the principle of the event reporting system in this application embodiment is similar to the event reporting method of the cleaning robot in the above application embodiment, the implementation of the system can refer to the implementation of the method. Repeated parts will not be described again.

[0079] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of a cleaning robot provided in an embodiment of this application. Figure 3 As shown, the cleaning robot 300 includes a processor 310, a memory 320, and a bus 330.

[0080] The memory 320 stores machine-readable instructions that can be executed by the processor 310. When the cleaning robot 300 is running, the processor 310 and the memory 320 communicate through the bus 330. When the machine-readable instructions are executed by the processor 310, the steps of the event reporting method of the cleaning robot as described in the above method embodiment can be executed. For specific implementation details, please refer to the method embodiment, which will not be repeated here.

[0081] This application also provides a computer-readable storage medium storing a computer program. When the computer program is run by a processor, it can execute the steps of the event reporting method for the cleaning robot as described in the above method embodiments. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0082] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0083] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

[0085] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0086] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0087] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An event reporting method for a cleaning robot, characterized in that, The method includes: In response to the triggering of a target event by the cleaning robot, the target display platform corresponding to the target event is determined according to the type of the target event; wherein, the event information of the cleaning robot has multiple display platforms, and each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot; The target event is reported to the target display platform so that the event information of the target event can be displayed to the target user through the target display platform.

2. The method according to claim 1, characterized in that, The demonstration platform includes: a cloud platform, a body application installed on the cleaning robot, and a remote application installed on a terminal device that communicates with the cleaning robot. The cloud platform users include R&D and after-sales personnel from the manufacturer of the cleaning robot, the main application users include on-site operators in the working environment of the cleaning robot, and the remote application users include management personnel with management functions over the on-site operators.

3. The method according to claim 1, characterized in that, Determining the target display platform corresponding to the target event based on the type of the target event includes: Based on the type of the target event, find the pre-configured mapping relationship between the event type and the display platform, and determine the target display platform; The steps for configuring the mapping relationship include: Determine the meaning of each event that the cleaning robot can trigger during operation, and define the attribute information of each event; wherein, the attribute information includes at least one of the following: the event display platform, the role of the user authorized to receive the event, and the severity of the event; The events are categorized based on their attribute information, and the corresponding display platform for each type of event is determined to obtain the mapping relationship.

4. The method according to claim 2, characterized in that, Event types include: notification, statistics, status, reminder, potential hazard, problem, and malfunction. Notification events are routine notifications that require no action. Statistical events are alarm messages that require no action and are only of concern to R&D personnel. Status events are routine states of the cleaning robot during operation that can be handled independently by on-site operators without guidance. Reminder events are abnormal states of the cleaning robot during operation that can be handled independently by on-site operators with guidance. Potential hazard events are events that do not affect the use of the cleaning robot but pose a potential hazard to its operation. Problem events are issues that affect the use of the cleaning robot and require on-site manual guidance from the manufacturer to resolve. Malfunction events are malfunctions that affect the use of the cleaning robot and require on-site resolution by manufacturer personnel. The display platforms for notification events include the cloud platform and the remote application; the display platforms for statistical events include the cloud platform; the display platforms for status events include the cloud platform, the entity application, and the remote application; the display platforms for reminder events include the cloud platform, the entity application, and the remote application; the display platforms for potential incidents include the cloud platform and the entity application; the display platforms for problem events include the cloud platform, the entity application, and the remote application; and the display platforms for fault events include the cloud platform, the entity application, and the remote application.

5. The method according to claim 4, characterized in that, The method further includes: Configure the display method for each type of event on each corresponding display platform, so as to display the event information of each type of event to the target user on the corresponding target display platform in accordance with the display method.

6. The method according to claim 4 or 5, characterized in that, The method further includes: the cleaning robot providing a first graphical user interface for the main body application via a body display screen; the main body application displaying event information of the target event on the first graphical user interface in a display manner corresponding to the type of the target event; the display manner including at least one of the following: displaying alarm information entries, displaying status pop-ups, and displaying fault information records on the first graphical user interface; the alarm information entries presenting processing prompts corresponding to the type of the target event, and the fault information records presenting detailed information about the target event; Status events are displayed in various ways, including displaying a status pop-up window; alert events are displayed in various ways, including displaying alarm information entries; potential hazard events are displayed in various ways, including displaying fault information records; problem events are displayed in various ways, including displaying alarm information entries and fault information records; and fault events are displayed in various ways, including displaying alarm information entries and fault information records.

7. The method according to claim 6, characterized in that, The target display platform displays event information about the target event to the target user, including: For the status pop-up window, the status pop-up window corresponding to the target event is displayed on the first graphical user interface; in response to the triggering operation of the confirmation control in the status pop-up window, the status pop-up window is canceled from display. For the alarm information entry, the alarm information entry corresponding to the target event is displayed on the first graphical user interface, wherein the visual display parameters of the alarm information entry correspond to the severity of the target event; For the fault information record, in response to the selection operation of the view control in the alarm information entry, the fault information record is displayed.

8. The method according to claim 4, characterized in that, The reminder events can be divided into: fault assistance sub-events, task self-check sub-events, and consumable maintenance sub-events; The fault assistance sub-category events include: charging abnormality, cleaning robot unable to move, negative pressure abnormality, and elevator control-related alarms; Task self-check sub-events include: dust bag not installed properly, cleaning robot needs to be unlocked, handle not lowered, dust mop not installed, and battery level below preset value; Consumable maintenance subcategories include: tangled or stuck foreign objects in the roller brush, abnormal suction, HEPA filter blockage, sensors requiring wiping, and dust bag reaching its maximum capacity.

9. An event reporting system for a cleaning robot, characterized in that, The system includes a cleaning robot and multiple display platforms; each display platform corresponds to a user with a different role in the operation and maintenance of the cleaning robot. The cleaning robot, in response to the triggering of a target event, determines the target display platform corresponding to the target event based on the type of the target event, and reports the target event to the target display platform; The target display platform displays event information about the target event to the target user.

10. A cleaning robot, characterized in that, include: The system includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the cleaning robot is running, the processor communicates with the memory via the bus. The machine-readable instructions are executed by the processor to perform the steps of the event reporting method for the cleaning robot as described in any one of claims 1 to 8.

Images