Alarm method, alarm system and electronic device

Abstract

The application provides an alarm method, an alarm system and an electronic device. The alarm method is applied to a host and includes the following steps: acquiring image data of a work scene; performing abnormal event identification on the image data, and generating alarm information if an abnormal event is identified; and sending the alarm information to a target slave machine in a plurality of slave machines through a long-distance radio (LoRa) communication mode, so that the target slave machine performs alarm based on the alarm information. The technical scheme of the application can realize abnormal alarm in a long-distance, large-range and complex work scene.

Description

Technical Field

[0001] This application relates to the field of security monitoring technology, specifically to an alarm method, alarm system, and electronic equipment. Background Technology

[0002] In industrial safety, smart city, and smart construction site scenarios, monitoring of the work environment is necessary to identify and issue alerts for abnormal events. Therefore, alarm technology, as a core means of ensuring workplace safety, can be used to identify abnormal events and issue alerts, preventing safety accidents in a timely manner. However, existing alarm technologies struggle to provide abnormal alerts in complex, long-distance, and large-scale work environments. Summary of the Invention

[0003] In view of this, embodiments of this application provide an alarm method, alarm system and electronic device, which can realize abnormal alarms in complex operating scenarios over long distances and large areas.

[0004] In a first aspect, embodiments of this application provide an alarm method applied to a host, comprising: acquiring image data of a work scene; identifying abnormal events in the image data; generating alarm information if an abnormal event is identified; and sending the alarm information to a target slave among multiple slaves via long-range radio LoRa communication, so that the target slave can issue an alarm based on the alarm information.

[0005] This application provides an alarm method that acquires image data of a work scene, identifies abnormal events in the image data, generates alarm information upon detection of an abnormal event, and transmits the alarm information to a target slave device among multiple slave devices via long-range LoRa radio communication. The target slave device then issues an alarm based on the alarm information. This application's solution effectively utilizes the advantages of LoRa communication—long distance, strong penetration, and wide coverage—by introducing long-range LoRa radio communication between the master and slave devices, thereby achieving abnormal alarms in complex, long-distance, and large-scale work scenarios and improving the timeliness of abnormal alarms.

[0006] Secondly, embodiments of this application provide an alarm method applied to a slave device, comprising: receiving alarm information from a master device via long-range LoRa radio communication, wherein the alarm information is obtained by the master device from abnormal event identification of image data of the work scene; and issuing an alarm based on the alarm information.

[0007] In one embodiment, the alarm method further includes: uploading second operating status information of the slave device to the host device at a second preset frequency, wherein the second operating status information is used to characterize whether there is an abnormality in the slave device, so that the host device can upload the second operating status information to the remote management platform.

[0008] This application provides an alarm method that receives alarm information from a host device via long-range LoRa radio communication and issues an alarm based on the alarm information. By introducing long-range LoRa radio communication between the host and slave devices, the advantages of LoRa communication—long communication distance, strong penetration capability, and wide coverage—are effectively utilized, thereby enabling abnormal alarms in complex operating scenarios over long distances and large areas.

[0009] Thirdly, embodiments of this application provide an alarm method applied to a remote management platform, comprising: receiving a device control command sent by a user and sending the device control command to a host, the device control command being used to configure at least one of the following: host parameters, adding information of a slave device connected to the host, and deleting information of a slave device connected to the host; if no response information is received from the host, resending the device control command to the host or issuing an error message; receiving first operating status information sent by the host and determining whether the host has an abnormality based on the first operating status information, or receiving second operating status information sent by the host and determining whether a slave device connected to the host has an abnormality based on the second operating status information; issuing a host device abnormality alarm if the host has an abnormality, and issuing a slave device abnormality alarm if a slave device has an abnormality.

[0010] In one embodiment, the alarm method further includes: when neither the host nor the slave is abnormal and an alarm message sent by the host is received, obtaining image data from a remote file server based on the alarm message to issue an alarm, wherein the alarm message is obtained by the host based on the image data for abnormal event identification, and the image data is image data about the work scene obtained by the host.

[0011] Fourthly, embodiments of this application provide an alarm system, including a host and multiple slave devices, wherein the host is used to: acquire image data of the work scene; identify abnormal events in the image data, and generate alarm information if an abnormal event is identified; and send the alarm information to a target slave device among the multiple slave devices via long-range radio LoRa communication; the target slave device is used to issue an alarm based on the alarm information.

[0012] In one embodiment, the alarm system further includes a remote file server and a remote management platform. The host is also used to: upload image data to the remote file server for storage when an abnormal event is detected, and upload alarm information to the remote management platform so that the remote management platform can obtain image data from the remote file server based on the alarm information to issue an alarm.

[0013] This application provides an alarm system that acquires image data of a work scene, identifies abnormal events in the image data, generates alarm information upon detection of an abnormal event, and transmits the alarm information to a target slave device among multiple slave devices via long-range LoRa radio communication, enabling the target slave device to issue an alarm based on the alarm information. By introducing long-range LoRa radio communication between the master and slave devices, the advantages of LoRa communication—long communication distance, strong penetration capability, and wide coverage—are effectively utilized, thereby achieving abnormal alarms in complex work scenarios involving long distances and large areas.

[0014] Fifthly, embodiments of this application provide an alarm device, including: an acquisition module for acquiring image data of a work scene; a generation module for identifying abnormal events in the image data, and generating alarm information if an abnormal event is identified; and a first transmission module for transmitting the alarm information to a target slave device among multiple slave devices via long-range LoRa radio communication, so that the target slave device can issue an alarm based on the alarm information.

[0015] Sixthly, embodiments of this application provide an electronic device, including: a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the alarm methods described in the first, second, third, and fourth aspects.

[0016] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program for executing the alarm methods described in the first, second, third, and fourth aspects.

[0017] Eighthly, embodiments of this application provide a computer program product, which includes a computer program. When the computer program is executed by the processor of a computer device, it enables the computer device to execute the alarm methods described in the first, second, third, and fourth aspects.

[0018] Ninthly, embodiments of this application provide a chip, including: a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the alarm methods described in the first, second, third, and fourth aspects.

[0019] This application provides an alarm method, alarm system, and electronic device. By acquiring image data of a work scene, the system identifies abnormal events in the image data. Upon identifying an abnormal event, an alarm message is generated. This alarm message is then transmitted to a target slave device among multiple slave devices via long-range LoRa radio communication, allowing the target slave device to issue an alarm based on the alarm message. This application's solution effectively utilizes the advantages of LoRa communication—long communication distance, strong penetration, and wide coverage—by introducing long-range LoRa radio communication between the master and slave devices. This enables abnormal alarms in complex, long-distance, and large-scale work scenarios, improving the timeliness of abnormal alarms. Attached Figure Description

[0020] Figure 1 The diagram shown is a schematic representation of the system architecture of an alarm system provided in an exemplary embodiment of this application.

[0021] Figure 2 The diagram shown is a flowchart of an alarm method provided in an exemplary embodiment of this application.

[0022] Figure 3 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application.

[0023] Figure 4 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application.

[0024] Figure 5 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application.

[0025] Figure 6 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application.

[0026] Figure 7 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application.

[0027] Figure 8 The diagram shown is a structural schematic of an alarm device provided in an exemplary embodiment of this application.

[0028] Figure 9 The diagram shown is a structural schematic of an alarm device provided in an exemplary embodiment of this application.

[0029] Figure 10 The diagram shown is a structural schematic of an alarm device provided in an exemplary embodiment of this application.

[0030] Figure 11 The diagram shown is a block diagram of an electronic device for performing an alarm method according to an exemplary embodiment of this application. Detailed Implementation

[0031] 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. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0032] Exemplary System This application provides an alarm system comprising a host and multiple slave devices. The host is used to: acquire image data of a work scene; identify abnormal events in the image data; generate alarm information if an abnormal event is identified; and send the alarm information to a target slave device among the multiple slave devices via long-range LoRa radio communication. The target slave device is used to issue an alarm based on the alarm information.

[0033] Specifically, the host may include a core control device or computing unit capable of performing image data processing, abnormal event recognition, and alarm information generation and distribution. For example, the host may be an industrial control computer with image recognition software installed, an embedded edge computing device, or a network video recorder with data processing capabilities.

[0034] Specifically, slave devices can include terminal equipment distributed across various areas of the work environment, used to receive alarm information from the host and execute local alarm output. For example, slave devices may include, but are not limited to, alarm terminals (such as computers, embedded computing devices, etc.) integrating a LoRa wireless module and an alarm device. The main function of the slave device is to respond to alarm information and drive the integrated alarm device to issue an alarm. Furthermore, alarm devices may include speakers, light-emitting diode (LED) displays, audible and visual alarms, etc.

[0035] Specifically, the relevant content regarding the operation scenario, image data, abnormal event recognition, alarm information, long-distance LoRa radio communication, and target slave device can be found in the relevant descriptions in the following embodiments. To avoid repetition, they will not be repeated here.

[0036] Furthermore, the alarm system also includes a remote file server and a remote management platform. The host is also used to: upload image data to the remote file server for storage when an abnormal event is detected, and upload alarm information to the remote management platform so that the remote management platform can obtain image data from the remote file server based on the alarm information to issue an alarm.

[0037] Specifically, a remote file server can include storage devices for storing media data and logs related to alarm events. For example, types of remote file servers can include File Transfer Protocol (FTP) servers, cloud storage services, Network Attached Storage (NAS), etc. Furthermore, a remote file server can store image data, video clips, or other evidence files to support event review and analysis. Even further, the host can upload image data to the remote file server via Ethernet, Wi-Fi, cellular mobile communication, long-range LoRa radio communication, etc.

[0038] Specifically, a remote management platform can include a server system capable of receiving alarm information, sending configuration commands, and monitoring device status. For example, the types of remote management platforms can include Internet of Things (IoT) platforms, cloud servers, and management software interfaces. Furthermore, the remote management platform can allow remote configuration of host parameters, management of slave device lists, and viewing of alarm logs and operational status. Even further, the host can upload alarm information to the remote management platform via Ethernet, Wi-Fi, cellular mobile communication, or long-range LoRa wireless communication.

[0039] Specifically, the remote management platform can obtain image data from a remote file server via Ethernet, Wireless Fidelity (Wi-Fi), cellular mobile communication, or long-range LoRa radio communication.

[0040] Specifically, the remote management platform generates alarms by retrieving image data from a remote file server based on alarm information. This can include: the remote management platform parsing the received alarm information, extracting information such as event type, occurrence time, and occurrence location, retrieving the image data corresponding to the alarm information from the remote file server, and displaying the image data, event type, occurrence time, and occurrence location corresponding to the alarm information. For example, the remote management platform can display the image data corresponding to the alarm information on a monitor. Furthermore, the remote management platform can also display at least one of the following on the monitor: the event type, occurrence time, and occurrence location corresponding to the alarm information.

[0041] Figure 1 The diagram shown is a schematic representation of the system architecture of an alarm system provided in an exemplary embodiment of this application. Figure 1 As shown, the alarm system 100 may include a host 110, multiple slave units 120, a remote file server 130, a remote management platform 140, and an image acquisition device 150. The slave units 120 are equipped with alarm devices.

[0042] In one example, the slave device 120 can upload its second operating status information to the host device 110 via long-distance LoRa radio communication at a second preset frequency. The second operating status information is used to characterize whether the slave device 120 is abnormal.

[0043] Furthermore, the host 110 can receive the second operating status information uploaded by the slave 120 via long-distance LoRa radio communication, and upload the parameters of the host 110, the first operating status information of the host 110, and the second operating status information of the slave 120 to the remote management platform 140 according to the first preset frequency. The first operating status information is used to characterize whether the host 110 has any abnormalities.

[0044] Furthermore, the remote management platform 140 can receive parameters of the host 110, the first operating status information of the host 110, and the second operating status information of the slave 120 sent by the host 110. Based on the first operating status information, it can determine whether the host 110 has any abnormality, and based on the second operating status information, it can determine whether the slave 120 has any abnormality.

[0045] Furthermore, the remote management platform 140 can issue a host device abnormality alarm when the host 110 is abnormal, and issue a slave device abnormality alarm when the slave device 120 is abnormal, so that operators can understand the device status of the host and slave devices.

[0046] Furthermore, the image acquisition device 150 can acquire image data and send the image data to the host 110.

[0047] Furthermore, the host 110 can identify abnormal events in the image data. If an abnormal event is identified, an alarm message is generated and sent to the remote management platform 140. The alarm message is then sent to the slave 120 via long-distance LoRa radio communication, and the image data is transmitted to the remote file server 130 for storage.

[0048] Furthermore, the slave device 120 can receive alarm information from the host device 110 via long-distance LoRa radio communication and drive the alarm device to issue an alarm based on the alarm information.

[0049] Furthermore, the remote management platform 140 can receive alarm information from the host 110 and obtain image data from the remote file server 130 to issue an alarm when neither the host 110 nor the slave 120 is abnormal.

[0050] Furthermore, the remote management platform 140 can receive device control commands sent by the user and send the device control commands to the host 110. The device control commands are used to configure at least one of the following: parameters of the host 110, information of adding slave devices 120 that are connected to the host 110, and information of deleting slave devices 120 that are connected to the host 110.

[0051] Furthermore, the host 110 can receive device control commands, execute operations corresponding to the device control commands, and send response information to the remote management platform 140.

[0052] Furthermore, if the remote management platform 140 does not receive a response, it will resend the device control command to the host 110 or issue an error message.

[0053] It should be understood that the above application scenario examples are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited thereto. Rather, the embodiments of this application can be applied to any applicable scenario.

[0054] Exemplary methods Figure 2 The diagram shown is a flowchart illustrating an exemplary embodiment of the alarm method provided in this application. This method is applied to a host. Figure 2 As shown, the alarm method may include the following:

[0055] 210: Obtain image data of the work scene.

[0056] In one embodiment, the work scenario may include a work area that requires safety monitoring. Further, the types of work scenarios may include wide-area or complex work scenarios requiring safety monitoring, such as industrial safety (e.g., factory buildings, warehouses, etc.), smart cities (e.g., transportation hubs, public squares, etc.), and smart construction sites (e.g., construction sites, tunnel engineering areas).

[0057] In one embodiment, image data may include visual information collected from the work scene, and the image data can be used for anomaly identification. Further, the type of image data may include video streams, still images, thermal images, etc. For example, the image data of the work scene may be manually collected and uploaded to the host's database; manual collection may include workers using handheld cameras. As another example, image data may be acquired through cameras, surveillance cameras, or other image acquisition devices and transmitted to the host in digital format. Furthermore, the image data of the work scene can be extracted from the host's database.

[0058] 220: Perform anomaly event identification on image data. If an anomaly event is identified, generate an alarm message.

[0059] In one embodiment, an anomalous event may include specific behaviors or states related to worker safety regulations, identified through image detection. For example, when the work scenario is a factory building, an anomalous event may include flames or smoke in the building, or personnel intrusion into the building. As another example, when the work scenario is a construction site, an anomalous event may include workers not wearing safety helmets, workers not wearing reflective vests, or workers smoking.

[0060] In one embodiment, anomalous events can be identified based on a deep learning model, such as a convolutional neural network or other suitable network. The host can load a pre-trained anomalous event recognition model, i.e., a deep learning model (such as YOLO or SSD series), and perform inference on the input image data to determine whether an anomalous event exists in the image.

[0061] In another embodiment, abnormal event identification of image data can be performed using identification methods based on traditional image processing techniques (such as background subtraction combined with morphological operations to detect region intrusion), identification methods based on feature template matching, or behavior judgment methods based on multi-frame optical flow analysis.

[0062] In one embodiment, alarm information may include a digital message or instruction generated in response to a detected abnormal event to trigger an alarm action. For example, alarm information may include a structured data packet containing fields such as event type, time of occurrence, and location of occurrence. As another example, alarm information may include control instructions in a specific format that can be parsed and executed by the slave device.

[0063] In one embodiment, the host's built-in AI chip can run a lightweight YOLOv5 model. This model is trained to detect targets such as "safety helmets," "reflective vests," "faces," and "cigarettes." When the model infers from the image data, if the confidence score for "safety helmets" is lower than a preset threshold (e.g., 0.6) while the confidence score for "faces" is high, it is determined as an "not wearing a safety helmet" abnormal event. Subsequently, the host generates an alarm message, which may include the following fields: event type (e.g., "not wearing a safety helmet"), event occurrence time (e.g., "2023-10-27 14:30:05"), associated device or region identifier (ID), and optional event confidence score.

[0064] 230: The alarm information is sent to the target slave among multiple slaves via long-range LoRa radio communication, so that the target slave can issue an alarm based on the alarm information.

[0065] In one embodiment, the long-range LoRa wireless communication method (hereinafter referred to as LoRa communication method) may include a low-power, long-range wireless communication method based on spread spectrum modulation technology. Typical characteristics of LoRa communication method include high receiver sensitivity, strong anti-interference capability, and low power consumption operation. Further, LoRa communication method may include wireless data transmission following the Long Range Wide Area Network (LoRaWAN) protocol or employing a proprietary LoRa modulation protocol. Further still, the "long-range" characteristic of LoRa communication method may refer to a communication distance of not less than 1 kilometer in an urban environment and not less than 3 kilometers in an open environment under line-of-sight conditions.

[0066] In one embodiment, the target slave device may include one of a plurality of slave devices. Sending alarm information to the target slave device may include sending the alarm information from the host to this single slave device via long-range LoRa radio communication. In another embodiment, the target slave device may include all of the plurality of slave devices. Sending alarm information to the target slave device may include sending the alarm information from the host to all of the plurality of slave devices via long-range LoRa radio communication. In yet another embodiment, the target slave device may include a group of slave devices (i.e., including at least two slave devices, but not all of them). Sending alarm information to the target slave device may include sending the alarm information from the host to this group of slave devices via long-range LoRa radio communication via multicast.

[0067] In one embodiment, the target slave device triggers an alarm based on alarm information, which may include: the target slave device parsing the received alarm information, extracting key information such as event type and time, and then driving the corresponding alarm device to execute the alarm according to the type of alarm device integrated into it. Further, the type of alarm device integrated into the target slave device may include at least one of a speaker, an LED display screen, an audible and visual alarm, etc. For example, when the type of alarm device integrated into the target slave device includes a speaker, the speaker can play a pre-recorded voice alarm. As another example, when the type of alarm device integrated into the target slave device includes an LED display screen, the LED display screen can scroll alarm text for text alarm. Yet another example, when the type of alarm device integrated into the target slave device includes an audible and visual alarm, the audible and visual alarm can emit an audible and visual alarm, such as flashing lights and a high-decibel siren. Exemplarily, different alarm information may correspond to different voice alarms, text alarms, or audible and visual alarms.

[0068] In one embodiment, any one of the target slave devices can integrate one or more alarm devices of the same type. For example, any one of the target slave devices can integrate a speaker, or any one of the target slave devices can integrate multiple speakers. In another embodiment, any one of the target slave devices can integrate multiple alarm devices of different types. For example, any one of the target slave devices can integrate a speaker, an LED display, and an audible and visual alarm. Furthermore, the number of multiple alarm devices of different types can be one or more, for example, any one of the target slave devices can integrate one speaker, two LED displays, and three audible and visual alarms.

[0069] This application provides an alarm method that acquires image data of a work scene, identifies abnormal events in the image data, generates alarm information upon detection of an abnormal event, and sends the alarm information to a target slave device among multiple slave devices via long-range LoRa radio communication, enabling the target slave device to issue an alarm based on the alarm information. This application's solution effectively utilizes the advantages of LoRa communication—long communication distance, strong penetration, and wide coverage—by introducing long-range LoRa radio communication between the master and slave devices, thereby achieving abnormal alarms in complex, long-distance, and large-scale work scenarios and improving the timeliness of abnormal alarms.

[0070] According to one embodiment of this application, the alarm method further includes: if an abnormal event is detected, uploading image data to a remote file server for storage, and uploading alarm information to a remote management platform, so that the remote management platform can obtain image data from the remote file server based on the alarm information to issue an alarm.

[0071] In one embodiment, the remote file server, remote management platform, uploading image data to the remote file server, uploading image data to the remote management platform, obtaining image data from the remote file server, and issuing alarms based on alarm information obtained from the remote file server can be found in the relevant descriptions in the above system embodiments. To avoid repetition, they will not be repeated here.

[0072] In this embodiment, upon detecting an abnormal event, image data is uploaded to a remote file server for storage, and alarm information is uploaded to a remote management platform. By establishing a communication connection with the remote file server and triggering image data upload upon detecting an abnormal event, traceable visual evidence of the scene is preserved for each alarm. This allows remote administrators to easily verify and trace event details afterward, improving the effectiveness and convenience of alarm management. Furthermore, by establishing a communication connection with the remote management platform and uploading alarm information to the platform upon detecting an abnormal event, the platform can issue alarms, enabling real-time perception and visualization of alarm events. This allows managers to intuitively understand the scene situation remotely, improving the timeliness of alarm response and remote control capabilities.

[0073] According to one embodiment of this application, multiple slave devices are responsible for the operation management of different areas in the operation scenario. Image acquisition devices are set up in different areas. Sending alarm information to a target slave device among the multiple slave devices includes sending alarm information to a target slave device among the multiple slave devices that corresponds to the target image acquisition device. The target image acquisition device is set up in the area where the target slave device is located and is used to collect image data.

[0074] In one embodiment, the target image acquisition device is located in the area where the target slave device is located, and is used to acquire image data upon which the anomaly event was identified. Furthermore, the type of target image acquisition device may include a surveillance camera, a video camera, a mobile phone with a camera function, etc.

[0075] In one embodiment, a mapping relationship can be established between image acquisition devices, regions, and alarm units (slave units). Further, an association table can be pre-configured, recording the ID (or location identifier) ​​of each image acquisition device and the region it is responsible for monitoring, as well as the IDs of one or more slave units deployed within that region and responsible for alarming events in that region. When the host runs the identification algorithm, it can determine which image acquisition device (i.e., the target image acquisition device) the currently processed image data originates from. Once an anomaly is identified, the host queries the aforementioned mapping table to find the list of slave units associated with the target image acquisition device (i.e., the target slave unit for this alarm), and then sends the alarm information to the target slave unit.

[0076] In this embodiment, multiple slave devices are responsible for operation management in different areas of the work scenario. Image acquisition devices are installed in each area, and alarm information can be sent to the target slave device corresponding to the target image acquisition device. By establishing a mapping relationship between the image acquisition device and the slave devices, and selecting the corresponding target slave device based on the source device of the image data used for identification, it is ensured that alarm information can be accurately and directly sent to the specific slave device associated with the area where the abnormal event occurred. This effectively avoids false alarms and interference from irrelevant areas, improving the targeting and effectiveness of alarms.

[0077] According to one embodiment of this application, the alarm method further includes: receiving a device control command from a remote management platform, the device control command being used to configure at least one of the following: parameters of the host, information of adding a slave device connected to the host, and information of deleting a slave device connected to the host; responding to the device control command, performing an operation corresponding to the device control command, and sending response information to the remote management platform; and uploading the parameters of the host, the first operating status information of the host, and the second operating status information of each of the multiple slave devices to the remote management platform at a first preset frequency, the first operating status information being used to characterize whether the host has an abnormality, and the second operating status information being used to characterize whether the slave device has an abnormality.

[0078] In one embodiment, the device control command may include instructions for configuring at least one of the following: host parameters, information on adding a slave device to communicate with the host, and information on deleting a slave device from communication with the host. Further, the device control command may be issued in JavaScript Object Notation (JSON) format via protocols such as Message Queuing Telemetry Transport (MQTT), Hypertext Transfer Protocol (HTTP), or WebSocket. For example, host parameters may include image recognition thresholds, alarm sensitivity, camera IP address, LoRa communication channel, etc. When the device control command is used to configure host parameters, the host can respond to the device control command and configure its own parameters. For example, the information of a slave device that communicates with the host may include the slave device's identifier, communication address, etc. When a device control command is used to add information about a slave device that communicates with the host, the host can respond to the device control command and add the information about the slave device that communicates with the host, thereby establishing a communication connection between the host and the slave device. Alternatively, when a device control command is used to delete information about a slave device that communicates with the host, the host can respond to the device control command and delete the information about the slave device that communicates with the host, thereby disconnecting the communication connection between the host and the slave device.

[0079] In one embodiment, the host can receive device control commands from a remote management platform via Ethernet, Wi-Fi, cellular mobile communication, long-range LoRa radio communication, or other means.

[0080] In one embodiment, the response information may include information indicating that the host has received and successfully executed the device control command. Furthermore, the host may send the response information to the remote management platform via Ethernet, Wi-Fi, cellular mobile communication, long-range LoRa radio communication, or other methods.

[0081] In one embodiment, the host can upload its parameters, first operating status information, and second operating status information of each of the multiple slave devices to the remote management platform via Ethernet, Wi-Fi, cellular mobile communication, or LoRa long-range wireless communication. Furthermore, the first preset frequency can be predetermined based on actual needs; for example, the first preset frequency may include once per minute, once every two minutes, once every three minutes, etc.

[0082] In one embodiment, the first operating status information may include information characterizing various operating parameters of the host. For example, the first operating status information may include at least one of the following: the host's central processing unit (CPU) temperature, the host's remaining disk space, the host's identification process, etc.

[0083] In one embodiment, the second operating status information may include information characterizing various operating parameters of the slave device. For example, the second operating status information may include at least one of the following: the slave device's battery level, the status of the alarm device integrated in the slave device (whether it is faulty), the communication status between the slave device and the master device (connected or disconnected), etc.

[0084] In one embodiment, whether the host is abnormal may include at least one of the following: whether the host's CPU temperature is too high, whether the host's remaining disk space is insufficient, or whether the host's identification process has crashed.

[0085] In one embodiment, whether the slave device is abnormal may include at least one of the following: whether the slave device's battery power is too low, whether the alarm device integrated in the slave device is faulty, or whether the slave device's communication is lost.

[0086] In this embodiment, the system receives device control commands from a remote management platform, responds to the commands by executing corresponding operations, and sends response information to the remote management platform. At a first preset frequency, it uploads the host's parameters, the host's first operating status information, and the second operating status information of each of the multiple slave devices to the remote management platform. By setting up a remote management platform capable of communicating with the host and defining a mechanism for receiving configuration commands and reporting status, remote centralized monitoring, configuration, and management of the host and the distributed slave devices are achieved, significantly reducing the need for on-site manual intervention and maintenance costs for system maintenance.

[0087] According to one embodiment of this application, abnormal events include at least one of the following: personnel in the work environment are not wearing safety helmets, personnel in the work environment are not wearing reflective vests, and personnel in the work environment are smoking.

[0088] In one embodiment, the anomaly event recognition model can be trained to detect at least one of the following anomaly events: whether a person in the work environment is not wearing a safety helmet, whether a person in the work environment is not wearing a reflective vest, or whether a person in the work environment is smoking. For example, for static protective equipment such as "safety helmets" and "reflective vests," the anomaly event recognition model can be used to identify the human body area and equipment area in the image, and determine whether they are being worn by judging their spatial overlap relationship (e.g., whether the helmet is above the head). As another example, for dynamic behaviors such as "smoking," object detection (identifying cigarettes and handheld objects) and keypoint detection (the positional relationship between hands and mouth) can be combined for analysis.

[0089] In this embodiment, by configuring the host to identify specific abnormal events such as personnel not wearing safety helmets, not wearing reflective vests, or smoking, the system can automatically identify a variety of common and critical safety violations in the work scenario, effectively expanding the system's automated monitoring capabilities and improving the comprehensiveness and efficiency of safety supervision.

[0090] Figure 3 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application. Figure 3 The example is Figure 2 Examples of the embodiments are provided below; to avoid repetition, the similarities can be referred to the descriptions in the above embodiments, and will not be repeated here. For example... Figure 3 As shown, the alarm method may include the following:

[0091] 310: The host power-on and initializes, establishes connections between the host and slave devices, the remote management platform, and the image acquisition device, and uploads the host parameters, the host's first operating status information, and the second operating status information of each of the multiple slave devices to the remote management platform according to the first preset frequency.

[0092] Specifically, the relevant contents of the host, slave, remote management platform, image acquisition device, first preset frequency, host parameters, host first operating status information, and second operating status information of each slave among multiple slaves can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0093] Specifically, establishing connections between the host and slave devices, the remote management platform, and the image acquisition device can include: after the host is powered on, it broadcasts a pairing request via LoRa communication, receives responses from the slave devices, and establishes wireless communication links with each slave device; the host sends a registration request to the remote management platform via a network communication protocol to establish a network connection with the remote management platform; and the host establishes a connection with the image acquisition device via a local area network protocol to obtain image data access permissions.

[0094] 320: The host acquires image data collected by the image acquisition device and performs abnormal event identification on the image data.

[0095] Specifically, the relevant content regarding image data and abnormal event recognition can be found in the descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0096] 330: If an abnormal event is detected, the host generates an alarm message, sends the alarm message to the target slave among multiple slaves and the remote management platform, and uploads the image data to the remote file server for storage.

[0097] Specifically, the alarm information, sending the alarm information to the target slave among multiple slaves, sending the alarm information to the remote management platform, and uploading the image data to the remote file server for storage can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0098] Figure 4 The diagram shown is a flowchart illustrating an alarm method provided in another exemplary embodiment of this application, which is applied to a slave device. Figure 4 As shown, the alarm method may include the following:

[0099] 410: Receive alarm information from the host via long-distance LoRa radio communication. The alarm information is obtained by the host through abnormal event identification of image data of the work scene.

[0100] Specifically, the relevant content regarding long-distance LoRa radio communication method, host, alarm information, operating scenarios, image data, and abnormal events can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0101] 420: Issue an alarm based on alarm information.

[0102] Specifically, the relevant content regarding alarms based on alarm information can be found in the descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0103] This application provides an alarm method that receives alarm information from a host device via long-range LoRa radio communication and issues an alarm based on the alarm information. This solution effectively utilizes the advantages of LoRa communication—long distance, strong penetration, and wide coverage—by introducing long-range LoRa radio communication between the host and slave devices. This enables abnormal alarms in complex, long-distance, and large-scale operational scenarios, improving the timeliness of abnormal alarms.

[0104] According to one embodiment of this application, the alarm method further includes: uploading second operating status information of the slave device to the host device at a second preset frequency, wherein the second operating status information is used to characterize whether there is an abnormality in the slave device, so that the host device can upload the second operating status information to the remote management platform.

[0105] Specifically, the second preset frequency can be predetermined based on actual needs. For example, the second preset frequency may include once every minute, once every two minutes, once every three minutes, etc.

[0106] Specifically, the slave device can upload secondary operating status information to the host device via Ethernet, Wi-Fi, cellular mobile communication, long-range radio LoRa communication, etc.

[0107] Specifically, the relevant content regarding the second operating status information, whether the slave device has any abnormalities, and the master device uploading the second operating status information to the remote management platform can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0108] In this embodiment, the slave device's second operating status information is uploaded to the host device at a second preset frequency. By periodically uploading the second operating status information to the host device through a reporting mechanism, the host device can easily upload the second operating status information to the remote management platform. This allows the host device and the remote management platform to promptly perceive the operating status of each distributed alarm unit, facilitating early warning and maintenance in case of equipment failure or abnormality, and improving the maintainability and operational reliability of the entire alarm system.

[0109] Figure 5 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application. Figure 5 The example is Figure 4 Examples of the embodiments are provided below; to avoid repetition, the similarities can be referred to the descriptions in the above embodiments, and will not be repeated here. For example... Figure 5 As shown, the alarm method may include the following:

[0110] 510: The slave device powers on and initializes, establishes a connection between the slave and the master, and uploads the slave's second operating status information to the master according to the second preset frequency.

[0111] Specifically, the details regarding establishing the connection between the slave and master devices, the second preset frequency, and the second operating status information of the slave device can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0112] 520: If the slave device receives an alarm message sent by the master device, it parses the alarm message and drives the corresponding alarm device to execute the alarm according to the type of alarm device integrated in the slave device.

[0113] Specifically, the alarm information and the relevant content regarding driving the corresponding alarm device to execute the alarm according to the type of alarm device integrated in the slave device can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0114] Figure 6 The diagram shown is a flowchart illustrating an alarm method provided in another exemplary embodiment of this application, which is applied to a remote management platform. Figure 6 As shown, the alarm method may include the following:

[0115] 610: Receive device control commands sent by the user and send the device control commands to the host. The device control commands are used to configure at least one of the following: host parameters, information of adding slave devices that communicate with the host, and information of deleting slave devices that communicate with the host.

[0116] Specifically, the remote management platform can receive device control commands sent by users via Ethernet, Wi-Fi, cellular mobile communication, long-range LoRa radio communication, and other methods.

[0117] Specifically, the relevant content regarding device control commands, host parameters, information on adding slave devices that communicate with the host, and information on deleting slave devices that communicate with the host can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0118] 620: If no response is received from the host, the device control command is resent to the host, or an error message is issued.

[0119] Specifically, the relevant content of the response information can be found in the relevant descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0120] Specifically, the error message may include information indicating that the host has not received the device control command or has failed to execute the device control command. Furthermore, the remote management platform can display this error message on the display interface. Even further, after sending the device control command to the host, the remote management platform can start a timer to wait for the host's response. If no response is received from the host within a preset timeout period (e.g., 10 seconds), the device control command will be resent to the host, or an error message will be issued.

[0121] 630: Receive the first operating status information sent by the host, and determine whether the host has any abnormalities based on the first operating status information; or receive the second operating status information sent by the host, and determine whether the slave device communicating with the host has any abnormalities based on the second operating status information.

[0122] Specifically, the remote management platform can analyze the first operating status information and determine whether the host is abnormal based on the analysis results. For example, when the first operating status information includes the host's CPU temperature, the remote management platform can compare the host's CPU temperature with a preset temperature threshold. If the host's CPU temperature is greater than or equal to the preset temperature threshold, it is determined that the host's CPU temperature is too high (i.e., the host is abnormal); if the host's CPU temperature is less than the preset temperature threshold, it is determined that the host's CPU temperature is not too high (i.e., the host is not abnormal). As another example, when the first operating status information includes the host's remaining disk space, the remote management platform can compare the host's remaining disk space with a preset space threshold. If the host's remaining disk space is less than or equal to the preset space threshold, it is determined that the host's remaining disk space is insufficient (i.e., the host is abnormal); if the host's remaining disk space is greater than the preset space threshold, it is determined that the host's remaining disk space is sufficient (i.e., the host is not abnormal). Furthermore, when the first operating status information includes the host's identification process, if the identification process uploaded by the host multiple times is the same, it is determined that the host's identification process has crashed (i.e., the host is abnormal); if the identification process uploaded by the host multiple times is different, it is determined that the host's identification process has not crashed (i.e., the host is not abnormal).

[0123] Specifically, the remote management platform can analyze the second operating status information and determine whether the slave device is abnormal based on the analysis results. For example, when the second operating status information includes the slave device's battery level, the remote management platform can compare the slave device's battery level with a preset battery level threshold. If the slave device's battery level is less than or equal to the preset battery level threshold, it is determined that the slave device's battery level is too low (i.e., the slave device is abnormal); if the slave device's battery level is greater than the preset battery level threshold, it is determined that the slave device's battery level is sufficient (i.e., the slave device is not abnormal). As another example, when the second operating status information includes the communication status between the slave device and the master device, if the communication status between the slave device and the master device is "disconnected," it is determined that the slave device's communication is lost (i.e., the slave device is abnormal); if the communication status between the slave device and the master device is "connected," it is determined that the slave device's communication is not lost (i.e., the slave device is not abnormal).

[0124] 640: Issue a host device fault alarm if the host device is faulty, and issue a slave device fault alarm if the slave device is faulty.

[0125] Specifically, issuing alarms for abnormal host devices can include highlighting the abnormal host's ID in red on the platform interface, sending emails, SMS messages, or push notifications to mobile applications (Apps) indicating that the host is abnormal.

[0126] Specifically, issuing alarms for abnormal slave devices can include highlighting the abnormal slave device's ID in red on the platform interface, sending emails, SMS messages, or push notifications to the mobile app indicating that the slave device is abnormal, etc.

[0127] This application provides an alarm method that receives device control commands sent by a user and sends them to a host. If no response is received from the host, the device control commands are resent to the host or an error message is issued. The method also receives first operating status information from the host and determines whether the host is malfunctioning based on this information, or receives second operating status information from the host and determines whether a slave device connected to the host is malfunctioning based on this information. If the host is malfunctioning, a host device malfunction alarm is issued; if a slave device is malfunctioning, a slave device malfunction alarm is issued. By receiving and forwarding device control commands, monitoring device operating status, and issuing malfunction alarms, remote unified management and real-time status monitoring of both host and slave devices are achieved. This improves the convenience and reliability of system operation and maintenance, enables timely detection of device faults and notification of management personnel, and ensures the stable operation of the alarm system.

[0128] According to one embodiment of this application, the alarm method further includes: when neither the host nor the slave is abnormal and an alarm message sent by the host is received, obtaining image data from a remote file server based on the alarm message to issue an alarm, wherein the alarm message is obtained by the host based on the image data for abnormal event identification, and the image data is image data about the work scene obtained by the host.

[0129] Specifically, if it is determined that the master device is not abnormal and the slave device is not abnormal, then neither the master device nor the slave device is abnormal.

[0130] Specifically, the alarm information, the acquisition of image data from the remote file server based on the alarm information for alarm purposes, image data, abnormal events, and work scenarios can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0131] In this embodiment, when neither the host nor the slave device is malfunctioning and an alarm message is received from the host, image data is retrieved from a remote file server based on the alarm message to trigger an alarm. By establishing a mechanism that triggers the retrieval of corresponding image data from a remote file server based on the alarm message after confirming normal device operation, the linkage between alarm information and on-site image data is achieved. This enhances the intuitiveness and credibility of the alarm, allowing managers to simultaneously view the on-site footage upon receiving an alarm, quickly assess the severity of the situation, and take appropriate measures.

[0132] Figure 7 The diagram shown is a flowchart of an alarm method provided in another exemplary embodiment of this application. Figure 7 The example is Figure 6 Examples of the embodiments are provided below; to avoid repetition, the similarities can be referred to the descriptions in the above embodiments, and will not be repeated here. For example... Figure 7 As shown, the alarm method may include the following:

[0133] 710: The remote management platform powers on and initializes, registering the host and slave devices to the remote management platform.

[0134] Specifically, the registration of the host and slave devices to the remote management platform can include: after the host is powered on, it sends a registration request to the remote management platform through a preset network communication protocol. The registration request carries the host identifier, host model, and software version information. After receiving the registration request, the remote management platform verifies the legality of the host identifier. If the verification is successful, it creates a device file for the host and records the host's basic information and online status.

[0135] Specifically, the slave device registration to the remote management platform can include: after the slave device is powered on, it sends a registration request to the host device via LoRa communication. The registration request carries the slave device identification number and the type of alarm device mounted on the slave device. The host device forwards the slave device's registration request to the remote management platform. After receiving the registration request, the remote management platform verifies the legality of the slave device identification number. If the verification is successful, a device file is created for the slave device, and the affiliation relationship between the slave device and the host device is recorded.

[0136] 720: Receive the first operating status information and the second operating status information sent by the host according to the first preset frequency.

[0137] Specifically, the relevant content of the first preset frequency, the first operating status information, and the second operating status information can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0138] 730: Based on the first operating status information, determine whether the host has any abnormality. Based on the second operating status information, determine whether the slave has any abnormality. If the host has any abnormality and / or the slave has any abnormality, proceed to step 740. If the host does not have any abnormality and the slave does not have any abnormality, the remote management platform continues to execute other appropriate steps, such as step 780.

[0139] Specifically, the relevant content on determining whether the host has any abnormalities based on the first operating status information can be found in the relevant descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0140] 740: Issues a master device malfunction alarm and / or a slave device malfunction warning.

[0141] Specifically, the relevant content of the host device abnormal alarm can be found in the relevant description in the above embodiments, and will not be repeated here to avoid repetition.

[0142] Specifically, the relevant content on determining whether the slave device has any abnormalities based on the second operating status information can be found in the relevant descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0143] Specifically, the relevant content of the slave device abnormal alarm can be found in the relevant description in the above embodiments, and will not be repeated here to avoid repetition.

[0144] 750: Receives device control commands sent by the user and sends the device control commands to the host.

[0145] Specifically, the relevant content of the device control commands can be found in the descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0146] 760: Determine whether a response message has been received from the host. If no response message has been received from the host, proceed to step 770. If a response message has been received from the host, the remote management platform continues to execute other appropriate steps.

[0147] Specifically, the relevant content of the response information can be found in the relevant descriptions in the above embodiments, and will not be repeated here to avoid repetition.

[0148] 770: Resend the device control command to the host, or issue an error message.

[0149] Specifically, the relevant content of the error message can be found in the relevant description in the above embodiments, and will not be repeated here to avoid repetition.

[0150] 780: Receive alarm information uploaded by the host, and retrieve image data from the remote file server based on the alarm information to trigger an alarm.

[0151] Specifically, the alarm information and the relevant content of obtaining image data from the remote file server based on the alarm information for alarm purposes can be found in the relevant descriptions in the above embodiments. To avoid repetition, they will not be repeated here.

[0152] It should be understood that the execution order of the above steps can be adjusted according to the actual situation. For example, step 780 can be executed simultaneously with step 720, or after step 720, or at other appropriate times.

[0153] Exemplary device Figure 8 The diagram shown is a structural schematic of an alarm device provided in an exemplary embodiment of this application. This alarm device can be applied to electronic devices. Figure 8 As shown, the alarm device 800 includes: an acquisition module 810, a generation module 820, and a first sending module 830.

[0154] The acquisition module 810 is used to acquire image data of the work scene. The generation module 820 is used to identify abnormal events in the image data, and if an abnormal event is identified, an alarm message is generated. The first sending module 830 is used to send the alarm message to a target slave device among multiple slave devices via long-range LoRa radio communication, so that the target slave device can issue an alarm based on the alarm message.

[0155] This application provides an alarm device that acquires image data of a work scene, identifies abnormal events in the image data, generates alarm information upon detection of an abnormal event, and transmits the alarm information to a target slave device among multiple slave devices via long-range LoRa radio communication, enabling the target slave device to issue an alarm based on the alarm information. This application's solution effectively utilizes the advantages of LoRa communication—long communication distance, strong penetration, and wide coverage—by introducing long-range LoRa radio communication between the master and slave devices, thereby achieving abnormal alarms in complex, long-distance, and large-scale work scenarios and improving the timeliness of abnormal alarms.

[0156] According to one embodiment of this application, the alarm device 800 further includes a first upload module 840. The first upload module 880 is used to upload image data to a remote file server for storage if an abnormal event is detected, and to upload alarm information to a remote management platform so that the remote management platform can obtain image data from the remote file server based on the alarm information to issue an alarm.

[0157] According to one embodiment of this application, multiple slave devices are responsible for the operation management of different areas in the operation scenario. Image acquisition devices are set up in different areas. The first sending module 830 is used to send alarm information to the target slave device that corresponds to the target image acquisition device among the multiple slave devices. The target image acquisition device is set in the area where the target slave device is located and is used to collect image data.

[0158] According to one embodiment of this application, the alarm device 800 further includes a receiving and executing module 850, which is used to receive device control instructions from a remote management platform. The device control instructions are used to configure at least one of the following: parameters of the host, information of adding a slave device that communicates with the host, and information of deleting a slave device that communicates with the host; in response to the device control instructions, the device 850 performs the operation corresponding to the device control instructions and sends response information to the remote management platform.

[0159] According to one embodiment of this application, the first upload module 840 is further configured to upload the host parameters, the host's first operating status information, and the second operating status information of each of the multiple slave devices to the remote management platform at a first preset frequency. The first operating status information is used to indicate whether the host has any abnormalities, and the second operating status information is used to indicate whether the slave devices have any abnormalities.

[0160] According to one embodiment of this application, abnormal events include at least one of the following: personnel in the work environment are not wearing safety helmets, personnel in the work environment are not wearing reflective vests, and personnel in the work environment are smoking.

[0161] It should be understood that the operations and functions of the acquisition module 810, generation module 820, first sending module 830, first uploading module 840, and receiving and execution module 850 in the above embodiments can be referred to the above. Figure 2 or Figure 3 To avoid repetition, the description of the alarm method provided in the embodiments will not be repeated here.

[0162] Figure 9 The diagram shown is a structural schematic of an alarm device provided in another exemplary embodiment of this application, which can be applied to electronic devices. Figure 9 As shown, the alarm device 900 includes: a receiving module 910 and a first alarm module 920.

[0163] The receiving module 910 is used to receive alarm information from the host via long-range LoRa radio communication. The alarm information is obtained by the host through abnormal event identification of image data of the work scene. The first alarm module 920 is used to issue an alarm based on the alarm information.

[0164] According to one embodiment of this application, the alarm device 900 further includes a second upload module 930, which is used to upload the second operating status information of the slave device to the host device at a second preset frequency. The second operating status information is used to indicate whether there is an abnormality in the slave device, so that the host device can upload the second operating status information to the remote management platform.

[0165] It should be understood that the operation and function of the receiving module 910, the first alarm module 920, and the second uploading module 930 in the above embodiments can be referred to the above. Figure 4 or Figure 5 To avoid repetition, the description of the alarm method provided in the embodiments will not be repeated here.

[0166] Figure 10 The diagram shown is a structural schematic of an alarm device provided in another exemplary embodiment of this application, which can be applied to electronic devices. Figure 10 As shown, the alarm device 1000 includes: a second sending module 1010, a third sending module 1020, a judgment module 1030, and a second alarm module 1040.

[0167] The second sending module 1010 is used to receive device control commands sent by the user and send the device control commands to the host. The device control commands are used to configure at least one of the following: host parameters, information on adding a slave device connected to the host, and information on deleting a slave device connected to the host. The third sending module 1020 is used to resend the device control commands to the host or issue an error message if no response is received from the host. The judgment module 1030 is used to receive first operating status information sent by the host and, based on the first operating status information, determine whether the host has an abnormality, or to receive second operating status information sent by the host and, based on the second operating status information, determine whether a slave device connected to the host has an abnormality. The second alarm module 1040 is used to issue a host device abnormality alarm if the host has an abnormality, and to issue a slave device abnormality alarm if a slave device has an abnormality.

[0168] According to one embodiment of this application, the alarm device 1000 further includes a third alarm module 1050. The third alarm module 1050 is used to issue an alarm based on the alarm information obtained from the remote file server when there is no abnormality in either the host or the slave and the alarm information sent by the host is received. The alarm information is obtained by the host based on the image data to identify abnormal events, and the image data is image data about the work scene obtained by the host.

[0169] It should be understood that the operation and function of the second sending module 1010, the third sending module 1020, the judgment module 1030, the second alarm module 1040, and the third alarm module 1050 in the above embodiments can be referred to the above. Figure 6 or Figure 7 To avoid repetition, the description of the alarm method provided in the embodiments will not be repeated here.

[0170] Figure 11 The diagram shown is a block diagram of an electronic device 1100 for performing an alarm method according to an exemplary embodiment of this application. Specifically, the electronic device 1100 may be a server, a control device (such as a host or slave), a server interacting with the control device, a controller, or other devices.

[0171] Reference Figure 11 The electronic device 1100 includes a processing component 1110, which further includes one or more processors, and memory resources represented by memory 1120 for storing instructions, such as application programs, that can be executed by the processing component 1110. The application programs stored in memory 1120 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1110 is configured to execute instructions to perform the aforementioned alarm methods.

[0172] Electronic device 1100 may also include a power supply component configured to perform power management of electronic device 1100, a wired or wireless network interface configured to connect electronic device 1100 to a network, and an input / output (I / O) interface. Electronic device 1100 can be operated based on an operating system stored in memory 1120, such as Windows Server. TM macOS X TM Unix TM Linux TM FreeBSD TM Or similar.

[0173] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the processor of the electronic device 1100, enables the electronic device 1100 to perform an alarm method.

[0174] A computer program product includes a computer program that, when executed by a processor of a computer device, enables the computer device to perform the alarm method provided in any of the above embodiments.

[0175] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here.

[0176] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0177] 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.

[0178] 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. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0179] 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.

[0180] 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.

[0181] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a 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 part 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 of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program verification codes, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0182] It should be noted that in the description of this application, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0183] 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. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0184] The above are merely preferred embodiments of this application and are not intended to limit this application. Any modifications or equivalent substitutions made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An alarm method, characterized in that, The method is applied to a host, and the method includes: Acquire image data of the work scene; The image data is subjected to anomaly event identification. If an anomaly event is identified, an alarm message is generated. The alarm information is sent to a target slave device among multiple slave devices via long-range LoRa radio communication, so that the target slave device can issue an alarm based on the alarm information.

2. The method according to claim 1, characterized in that, The method further includes: If the abnormal event is detected, the image data is uploaded to a remote file server for storage, and the alarm information is uploaded to a remote management platform so that the remote management platform can obtain the image data from the remote file server based on the alarm information and issue an alarm.

3. The method according to claim 1, characterized in that, The multiple slave devices are each responsible for operation management in different areas of the operation scenario. Each of these different areas is equipped with an image acquisition device. Sending the alarm information to the target slave among multiple slave devices includes: The alarm information is sent to the target slave device, which is located in the area where the target slave device is located, and is used to collect the image data.

4. The method according to claim 1, characterized in that, The method further includes: Receive device control instructions from a remote management platform, the device control instructions being used to configure at least one of the following: parameters of the host, information of adding a slave device that is connected to the host, and information of deleting a slave device that is connected to the host. In response to the device control command, perform the operation corresponding to the device control command and send response information to the remote management platform; According to a first preset frequency, the parameters of the host, the first operating status information of the host, and the second operating status information of each of the plurality of slave devices are uploaded to the remote management platform. The first operating status information is used to characterize whether the host has any abnormality, and the second operating status information is used to characterize whether the slave device has any abnormality.

5. The method according to any one of claims 1 to 4, characterized in that, The abnormal event includes at least one of the following: personnel in the work scene are not wearing safety helmets, personnel in the work scene are not wearing reflective vests, and personnel in the work scene are smoking.

6. An alarm method, characterized in that, The method is applied to a slave device, and the method includes: Alarm information is received from the host via long-distance LoRa radio communication. The alarm information is obtained by the host through abnormal event identification of image data of the work scene. An alarm is issued based on the alarm information.

7. An alarm method, characterized in that, The method is applied to a remote management platform, and the method includes: The system receives device control commands sent by the user and sends the device control commands to the host. The device control commands are used to configure at least one of the following: parameters of the host, information of adding slave devices that are connected to the host, and information of deleting slave devices that are connected to the host. If no response is received from the host, the device control command is resent to the host, or an error message is issued. The system receives first operating status information sent by the host and determines whether the host is abnormal based on the first operating status information; or it receives second operating status information sent by the host and determines whether the slave device communicating with the host is abnormal based on the second operating status information. If the host device malfunctions, a host device malfunction alarm will be issued; if the slave device malfunctions, a slave device malfunction alarm will be issued.

8. An alarm system, characterized in that, Includes the master unit and multiple slave units. The host is used to: acquire image data of the work scene; identify abnormal events in the image data; generate alarm information if an abnormal event is identified; and send the alarm information to a target slave among multiple slaves via long-distance LoRa radio communication. The target slave device is used to generate an alarm based on the alarm information.

9. The system according to claim 8, characterized in that, It also includes remote file servers and remote management platforms. The host is further configured to: upon detecting the abnormal event, upload the image data to the remote file server for storage, and upload the alarm information to the remote management platform, so that the remote management platform can obtain the image data from the remote file server based on the alarm information and issue an alarm.

10. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions. The processor is used to execute the alarm method according to any one of claims 1 to 7.

Images