Equipment monitoring processing method and device, storage medium and electronic equipment

Abstract

The invention discloses an equipment monitoring processing method and device, a storage medium and electronic device.The method comprises the steps that target electronic fence information input by a user side in an equipment monitoring interface is obtained, and a target electronic fence is started based on the target electronic fence information; and performing fence equipment state monitoring processing based on the target electronic fence to obtain an equipment transaction monitoring data table, performing equipment monitoring inspection processing on the target Internet of Things equipment based on the equipment transaction monitoring data table to obtain equipment monitoring transaction information, and outputting the equipment monitoring transaction information to a user side.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a device monitoring and processing method, apparatus, storage medium, and electronic device. Background Art

[0002] With the rapid development of the Internet of Things (IoT), the management and monitoring of IoT device transactions are becoming increasingly complex. Large-scale device deployments and diverse application scenarios present numerous challenges, especially given the varying levels of assurance required for different IoT device transaction scenarios. Therefore, device monitoring requires refined and layered approaches. These include ensuring accurate device location, efficient device monitoring, and the need for rapid response based on real-time device data. Summary of the Invention

[0003] This specification provides a device monitoring and processing method, apparatus, storage medium, and electronic device. The technical solution is as follows:

[0004] In a first aspect, this specification provides a device monitoring processing method, the method comprising:

[0005] Acquire target electronic fence information input by the user terminal on the device monitoring interface, and activate the target electronic fence based on the target electronic fence information;

[0006] Performing fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table;

[0007] Based on the device processing transaction monitoring data table, device monitoring and inspection processing is performed on the target Internet of Things device to obtain device monitoring transaction information, and the device monitoring transaction information is output to the user end.

[0008] In a second aspect, this specification provides a device monitoring and processing apparatus, the apparatus comprising:

[0009] A fence determination module is used to obtain target electronic fence information input by the user terminal on the device monitoring interface and activate the target electronic fence based on the target electronic fence information;

[0010] A monitoring processing module, configured to perform fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table;

[0011] An information output module is used to perform device monitoring and inspection processing on the target Internet of Things device based on the device processing transaction monitoring data table to obtain device monitoring transaction information, and output the device monitoring transaction information to the user end.

[0012] In a third aspect, the present specification provides a computer storage medium storing at least one instruction, wherein the instruction is suitable for being loaded by a processor and executing the method steps of one or more embodiments of the present specification.

[0013] In a fourth aspect, the present specification provides a computer program product, wherein the computer program product stores at least one instruction, wherein the instruction is suitable for being loaded by a processor and executing the method steps of one or more embodiments of the present specification.

[0014] In a fifth aspect, this specification provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps of one or more embodiments of this specification.

[0015] The beneficial effects of the technical solutions provided by some embodiments of this specification include at least:

[0016] In one or more embodiments of this specification, the service platform obtains target electronic fence information entered by a user on the device monitoring interface and activates the target electronic fence based on the target electronic fence information, effectively achieving flexible and precise zoning for different monitoring needs, ensuring that device monitoring can meet diverse security requirements in different scenarios. Then, based on the target electronic fence, the service platform performs fence device status monitoring to generate a device transaction monitoring data table. The system can accurately track the real-time status of the device and promptly process the data, addressing the real-time and accuracy limitations of the device monitoring process, making it particularly suitable for large-scale device monitoring scenarios. Furthermore, based on the device transaction monitoring data table, the service platform performs device monitoring inspections on the target IoT device to obtain device monitoring transaction information, which is then output to the user. This not only improves device inspection efficiency but also enhances the real-time nature of fault response, ensuring rapid response and efficient management in complex application scenarios. Overall, while ensuring monitoring accuracy, it significantly improves monitoring efficiency, automation, and device management response speed, enabling convenient and intelligent implementation of positioning and status monitoring in large-scale device management. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 This is a scenario diagram of a device monitoring and processing system provided in this manual;

[0019] Figure 2 This is a flow chart of a device monitoring processing method provided in this manual;

[0020] Figure 3 This is an interface for setting up electronic fences in the device monitoring interface provided in this manual;

[0021] Figure 4 This is a schematic diagram of the interface of a newly added electronic fence provided in this manual;

[0022] Figure 5 This is a scene diagram of the coordinate picker dialog box setting provided in this manual;

[0023] Figure 6 This is a schematic diagram of an electronic fence information display interface provided in this manual;

[0024] Figure 7 This is a schematic diagram of an interface for displaying device monitoring transaction information provided in this manual;

[0025] Figure 8 This is a flowchart of a target electronic fence processing provided in this manual;

[0026] Figure 9 This is a flow chart of the collection of equipment transaction monitoring data tables provided in this manual;

[0027] Figure 10 This is a flowchart of determining a target fence device monitoring list provided in this manual;

[0028] Figure 11 This is a structural diagram of a device monitoring and processing device provided in this manual;

[0029] Figure 12 This is a structural diagram of an electronic device provided in this manual. DETAILED DESCRIPTION

[0030] The following will clearly and completely describe the technical solutions in this specification in conjunction with the accompanying drawings. Obviously, the embodiments described are only some of the embodiments in this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this specification.

[0031] In the description of this specification, it should be understood that the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In the description of this specification, it should be noted that, unless otherwise expressly specified and limited, "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in this specification can be understood according to the specific circumstances. In addition, in the description of this specification, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0032] In related technologies, IoT device monitoring requires refinement and tiered approaches. These include ensuring accurate device location, efficient device monitoring, and the need for rapid response based on real-time device data. IoT device monitoring typically involves a diverse set of scenarios, integrating both software and hardware. Different application scenarios require varying levels of security, necessitating refined and tiered monitoring. While daily platform-based IoT device monitoring only requires focusing on the version dimension, IoT device monitoring in key scenarios like the Forbidden City, parks, the Bund, the Asian Games, and concerts requires focusing on individual device security.

[0033] For regionalized IOT device monitoring, each time an IOT device monitoring and assurance project is launched, it is usually faced with the problem of how to solve the efficiency problem of large-scale IOT device positioning and status monitoring as the number of IOT devices increases and the scale of the monitoring area expands, as well as how to ensure the real-time processing of device monitoring data, while realizing automated inspection and user feedback mechanisms, so as to output the monitoring transaction information of the device to the user end in a timely manner, and improve the efficiency of device management and fault response. This is still a problem that needs to be solved urgently. The device monitoring processing method shown in one or more embodiments of this specification can solve or even improve all or part of the above problems.

[0034] The present specification is described in detail below with reference to specific embodiments.

[0035] See Figure 1 , is a schematic diagram of a device monitoring and processing system provided in this specification. Figure 1 As shown, the device monitoring processing system may include at least a client cluster and a service platform 100 .

[0036] The client cluster may include at least one client, such as Figure 1 As shown, it specifically includes client 1 corresponding to user 1, client 2 corresponding to user 2, ..., client n corresponding to user n, where n is an integer greater than 0.

[0037] Each client in the client cluster can be an electronic device with communication capabilities, including but not limited to wearable devices, handheld devices, personal computers, tablet computers, in-vehicle devices, smartphones, computing devices, or other processing devices connected to a wireless modem. Electronic devices may be called different names in different networks, such as user equipment, access terminals, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, electronic devices, wireless communication devices, user agents or user devices, cellular phones, cordless phones, personal digital assistants (PDAs), and electronic devices in 5G networks or future evolution networks.

[0038] The service platform 100 can be a separate server device, such as a rack-mounted, blade, tower, or cabinet-mounted server device, or a workstation, mainframe computer, or other hardware device with strong computing capabilities; it can also be a server cluster composed of multiple servers. The servers in the service cluster can be symmetrically composed, wherein each server has equivalent functions and status in the transaction link, and each server can provide services to the outside world independently. The independent service can be understood as not requiring the assistance of other servers.

[0039] In one or more embodiments of the present specification, the service platform 100 may establish a communication connection with at least one client in the client cluster, and complete data interaction during the device monitoring process based on the communication connection.

[0040] It should be noted that the service platform 100 and at least one client in the client cluster establish a communication connection through a network for interactive communication, wherein the network can be a wireless network or a wired network, the wireless network includes but is not limited to a cellular network, a wireless local area network, an infrared network or a Bluetooth network, and the wired network includes but is not limited to Ethernet, a universal serial bus (USB) or a controller area network. In one or more embodiments of the specification, technologies and / or formats including Hypertext Markup Language (HTML) and Extensible Markup Language (XML) are used to represent data exchanged over the network (such as a target compressed package). In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), and Internet Protocol Security (IPsec) can also be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above-mentioned data communication technologies.

[0041] The device monitoring and processing system embodiments provided in this specification share the same concept as the device monitoring and processing methods described in one or more embodiments. The execution entity corresponding to the device monitoring and processing methods described in one or more embodiments of this specification can be the aforementioned service platform 100; the execution entity corresponding to the device monitoring and processing methods described in one or more embodiments of this specification can also be the electronic device corresponding to the client, depending on the actual application environment. The implementation process of the device monitoring and processing system embodiments can be found in the following method embodiments and will not be further described here.

[0042] based on Figure 1 The scene diagram shown is a detailed introduction to the device monitoring processing method provided by one or more embodiments of this specification.

[0043] See Figure 2 , provides a flow chart of a device monitoring processing method for one or more embodiments of this specification. This method can be implemented using a computer program and run on a device monitoring processing device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone tool application. The device monitoring processing device can be a service platform.

[0044] Specifically, the device monitoring processing method includes:

[0045] S102: Acquire target electronic fence information input by the user terminal on the device monitoring interface, and activate the target electronic fence based on the target electronic fence information;

[0046] Target geofence: A geofence is a virtual boundary based on geographic location, used to define a fenced area. Any IoT device within the fenced area will trigger a corresponding event or action. The target geofence is a user-defined monitoring area in the platform transaction system and can be any shape (such as circular, rectangular, polygonal, etc.).

[0047] Device monitoring interface: The device monitoring interface refers to the interface through which users interact with the platform transaction system. Users can input relevant information about device monitoring through the user terminal, set the device's monitoring area, device status and behavior, etc.

[0048] Illustratively, a user enters or selects target geo-fence information in the device monitoring interface via a user terminal, such as selecting a geographic location, setting the fence area's boundaries, or adjusting the fence area's shape. Based on the user-entered target geo-fence information, the system generates and sets a virtual target geo-fence area and activates a pre-set IoT device transaction monitoring mechanism for that target geo-fence area. The pre-set IoT device transaction monitoring mechanism is designed based on actual application scenarios and is not specifically defined here.

[0049] Schematically, the service platform activates the target electronic fence and begins to monitor the status changes of IoT devices and IoT device transaction status information in the area in real time.

[0050] For example, Figure 3 As shown, Figure 3 This is a schematic diagram of the electronic fence setting interface in the device monitoring interface. After the user triggers the IOT electronic fence in the device monitoring interface through the user terminal, it will be displayed as follows Figure 3 The interface of the electronic fence displaying the coordinates of the circled area shown in the figure is used to operate the "add electronic fence" option. The user terminal can further input the "target electronic fence information" by triggering the "add electronic fence" option. For further example, please refer to Figure 4 , Figure 4 This is a schematic diagram of the interface for adding an electronic fence. After the user triggers the "Add Electronic Fence" option, the following is displayed: Figure 4 The interface shown in the pop-up window is Figure 4Enter the "target electronic fence information" in the window interface shown, which may include the project name, electronic fence name, and electronic fence coordinates (a project may include multiple electronic fences, such as a sports event that includes multiple venues); when entering the electronic fence coordinates, the user can click Figure 4 The "coordinate picker button" shown in the figure, the service platform pops up the coordinate picker dialog box through the user end, such as Figure 5 As shown, Figure 5 It is a scene diagram of the coordinate picker dialog box setting. The user Figure 5 Enter the location of the area to be monitored in the search box shown, click the "Search" option, the location marker on the map will automatically move to the center point and obtain its latitude and longitude coordinates, then click the "Outline Area" button, the user can outline the polygonal area to be monitored around the center point coordinates (such as Figure 5 After the graphics are drawn, the electronic fence information dialog box will be returned (allowing the user to modify the radius, longitude and latitude coordinates as needed). Figure 6 As shown, Figure 6 It is a schematic diagram of the interface displaying electronic fence information. The user triggers the "Confirm" button on the device monitoring interface to complete the target electronic fence information input on the device monitoring interface. At this time, the service platform can obtain the target electronic fence information input on the device monitoring interface on the user side.

[0051] S104: performing fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table;

[0052] Fence device status monitoring: This refers to real-time monitoring of device status changes within the area defined by the target geo-fence. For example, when a device enters or leaves the fenced area, the system records the device's status and takes appropriate action (such as issuing an alarm, recording the location, and device status).

[0053] Device Transaction Monitoring Data Table: This table records the various behaviors and states of devices within the geo-fence area. It contains real-time data about the device, including status changes, alarm information, geographic location, and operation time.

[0054] Illustratively, after activating a target geo-fence, the service platform system will monitor the transaction status of IoT devices within the target geo-fence area in real time. These IoT devices may include information such as device location, power-on status, device attributes, device status, and associated device transaction information (e.g., device flow, device transactions, etc.). The system records this information in a device transaction monitoring data table. This table is updated in real time to ensure the integrity and timeliness of each monitored item.

[0055] S106: Performing device monitoring and inspection processing on the target IoT device based on the device processing transaction monitoring data table to obtain device monitoring transaction information, and outputting the device monitoring transaction information to the user terminal.

[0056] Device monitoring and inspection: Device monitoring and inspection refers to the system's regular or irregular checks on device status and the status of related transactions based on device monitoring data. The inspection process may include checking the device's health, performance, location, and related transaction status to ensure that it is operating as expected.

[0057] Equipment monitoring transaction information: Equipment monitoring transaction information refers to the data generated by processing the corresponding transaction monitoring dimension based on the recorded equipment processing transaction monitoring data table during the equipment monitoring process according to the preset transaction monitoring dimension calculation logic; optionally, for example, equipment monitoring transaction information may include: overview information of the overall situation (dimension) of periodic data, stability (dimension) information, equipment transaction and equipment anomaly (dimension) information, time-consuming experience (dimension) information, regional equipment addition and deletion changes (dimension) information, transaction indicator (dimension) information, transaction system technical indicator (dimension) information, etc.

[0058] Optionally, the user side can be notified later through information output display methods such as data dashboard display and group broadcast, showing the overall situation of a certain period to the user. Device monitoring transaction information can include offline transaction data, mainly including stability data of various IoT devices, time-consuming experience data, transaction and abnormal indicator statistics, etc.

[0059] In a feasible implementation, the device monitoring inspection process for the target IoT device based on the device processing transaction monitoring data table is performed to obtain the device monitoring transaction information, which can be performed in the following manner:

[0060] S2: Calculating reference transaction monitoring indicator data based on the device processing transaction monitoring data table according to preset transaction monitoring dimension logic;

[0061] Transaction monitoring dimension logic refers to the logical paradigm for calculating and evaluating various types of information recorded in the device transaction monitoring data table according to certain preset dimensions or standards. These dimensions may include: overall cycle data status (dimension), stability (dimension), device transactions and device anomalies (dimension), time consumption experience (dimension), regional device addition and deletion changes (dimension), transaction metrics (dimension), transaction system technical indicators (dimension), and so on.

[0062] Reference transaction monitoring indicator data: Various indicator data calculated from device monitoring data based on preset dimensional logic, typically used to analyze device operating status, performance, and health. Reference transaction monitoring indicator data can include: overview information (dimensions) of overall cycle data, stability information (dimensions), device transactions and device anomalies (dimensions), time consumption experience (dimensions), regional device addition and deletion changes (dimensions), transaction indicator (dimensions), transaction system technical indicator (dimensions), and more.

[0063] In principle, the system sets a series of dimension standards based on transaction monitoring requirements and transaction monitoring goals to obtain multiple preset transaction monitoring dimension logics, and then uses the preset transaction monitoring dimension logics to perform logical calculations on the data in the device transaction monitoring data table to obtain reference transaction monitoring indicator data.

[0064] S4: Generate device monitoring transaction information based on the reference transaction monitoring indicator data using a preset device monitoring inspection template.

[0065] Device monitoring inspection templates are predefined templates or rules that guide the device inspection process. Inspection templates can be formatted based on factors such as device type, device status requirements, and transaction requirements. Reference transaction monitoring indicator data is aggregated according to the device monitoring inspection templates to generate device monitoring transaction information. Optionally, multiple device monitoring inspection templates can be used, each aggregating one or more reference transaction monitoring indicator data.

[0066] Equipment monitoring transaction information: refers to the event or status information recorded during the equipment monitoring process obtained by summarizing the reference transaction monitoring indicator data according to the equipment monitoring inspection template.

[0067] Schematically, by calculating multiple reference transaction monitoring indicator data, the system can conduct a detailed assessment of the monitoring status of IoT devices within the perimeter. This reference transaction monitoring indicator data provides the basis for the inspection process. Device monitoring inspection templates are then applied. These templates use the reference transaction monitoring indicator data to generate corresponding monitoring transaction information based on the device type and transaction requirements. Inspection templates define device inspection standards, inspection items, and alarm rules.

[0068] For example, Figure 7 As shown, Figure 7 It is a schematic diagram of the interface displaying equipment monitoring transaction information. Figure 7 The device monitoring transaction information is displayed to the user end for the IOT device client. The device monitoring transaction information includes monthly data summary information, stability index information, device transaction and device abnormality statistics, time-consuming experience data information, regional device increase and decrease change detection information, etc. The user end can trigger the "time-consuming experience data" item and then display Figure 7 The time-consuming experience data is shown on the right.

[0069] In this specification, the service platform obtains target geo-fence information entered by the user on the device monitoring interface and activates the target geo-fence based on this information. This effectively enables flexible and precise zoning for different monitoring needs, ensuring that device monitoring can meet diverse security requirements in different scenarios. The system then monitors the status of the fence device based on the target geo-fence to generate a device transaction monitoring data table. This allows the system to accurately track the real-time status of the device and promptly process the data, addressing the real-time and accuracy limitations of the device monitoring process, making it particularly suitable for large-scale device monitoring scenarios. Furthermore, based on the device transaction monitoring data table, the system performs device monitoring inspections on the target IoT device to obtain device monitoring transaction information, which is then output to the user. This not only improves device inspection efficiency but also enhances the real-time nature of fault response, ensuring rapid response and efficient management in complex application scenarios. Overall, while ensuring monitoring accuracy, the system significantly improves monitoring efficiency, automation, and device management response speed, enabling convenient and intelligent positioning and status monitoring for large-scale device management.

[0070] Optional, see Figure 8 , Figure 8 This is a flowchart of a target electronic fence processing method proposed in one or more embodiments of this specification. Specifically, the following methods can be used to obtain the target electronic fence information input by the user terminal in the device monitoring interface and activate the target electronic fence based on the target electronic fence information:

[0071] S202: Displaying a device monitoring interface to the user terminal and obtaining a target area location input by the user terminal on the device monitoring interface;

[0072] Device monitoring interface: This refers to the graphical user interface in the system that allows users to set up and manage device monitoring. Users can use this interface to perform operations such as device location and monitoring area selection.

[0073] Target Area Location: This refers to the area location entered or selected by the user in the device monitoring interface. It is usually a geographic location that represents the target location that the user wants to monitor.

[0074] Schematically, the system presents the user with a device monitoring interface where they enter or select the location of the target area. This can be done by manually entering a place name, selecting a location on a map, or searching for an address. The user-entered target area location will serve as the basis for subsequent fence placement, and the system will convert this location into corresponding geographic coordinates, which will serve as the center of the target area.

[0075] For example, the user Figure 5 In the device monitoring interface shown, enter "Chengdu No. 7 Middle School August 1st School" as the target area. The system automatically obtains the "Chengdu No. 7 Middle School August 1st School" in the shopping mall and provides basic location data for subsequent electronic fence creation.

[0076] S204: Displaying a local selected area map corresponding to the target area position, or displaying a local selected area map corresponding to the target area position and a reference fence polygon area;

[0077] Local selection area map: The system recommends displaying a map view of the target area location based on the target area location on the device monitoring interface. Users can further select the monitored area based on this view.

[0078] Reference Fence Polygon Area: The reference area is typically a standard fence area recommended by the system based on the target area location entered by the user. It can represent some common surveillance areas, such as shopping malls and conference centers. The system can provide users with a reference fence to help users more easily set the target fence and save fence selection paths.

[0079] In a feasible implementation, the system only displays a partial map of the target area location to help users intuitively see the geographical distribution of the location;

[0080] In a feasible embodiment, in addition to displaying a local map of the target area location, the system may also determine a recommended reference fence polygonal area from the local selected area map and then display it;

[0081] In a feasible implementation manner, the display of the local selected area map corresponding to the target area location and the reference fence polygon area may be performed in the following manner:

[0082] Step A2: determining a local selection area map corresponding to the target area location, and obtaining a set of candidate IoT devices in the local selection area map based on a preset reference radius with the target area location as a reference;

[0083] Preset reference radius: refers to a predetermined radius assigned by the system to the target area based on its location, used to determine the monitoring range of the area. For example, if the target area is a shopping mall entrance, the preset reference radius may be 100 meters or 500 meters;

[0084] Candidate IoT device set: a set of IoT devices within a preset reference radius. These devices are located in the target area and meet the monitoring requirements.

[0085] Schematically, the system generates a local map view of the target area based on the location of the target area and a preset reference radius. The map will include geographic information about the target area and its surroundings, and display possible device locations within the area.

[0086] Then, based on this reference radius, the system screens a set of candidate IoT devices located near the target area. These devices may include smart sensors, access control devices, cameras, etc., and are displayed on the map for further selection by the user.

[0087] Example: Suppose the user selects the entrance of a shopping mall as the target area location. Based on the latitude and longitude of the mall and the preset 200-meter reference radius, the system determines all IoT devices (such as access control, surveillance cameras, sensors, etc.) within 200 meters around the mall as a set of candidate devices, and displays these devices on the local map.

[0088] Step A4: Determine the device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information corresponding to the candidate IoT device set;

[0089] Device spatiotemporal distribution information: refers to the distribution of IoT devices in a specific time and space. For example, the location and movement trajectory of IoT devices within a certain period of time.

[0090] Device behavior information: refers to the behavioral data generated by IoT devices during operation, such as switch status, activity records, fault records, etc.

[0091] Historical device alarm and fault information: fault records, alarm information, or performance anomaly data that have occurred in the history of IoT devices.

[0092] Schematically, based on a set of candidate devices, the system collects and analyzes the spatiotemporal distribution of these IoT devices, including their location, distribution density, and activity patterns within the target area. Simultaneously, the system also collects behavioral information about these IoT devices, such as whether they are online, operating properly, and whether they have triggered alarms. The system also reviews historical alarm and fault information for these IoT devices, including past fault records and abnormal alarms, as a crucial reference for device health.

[0093] Step A6: Determine a candidate device weight vector corresponding to each candidate IoT device in the candidate IoT device set using the electronic fence processing model based on the device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information; spatially cluster the candidate IoT devices based on the candidate device weight vector to obtain a primary device cluster; and determine a reference fence polygon area corresponding to the primary device cluster;

[0094] Geo-fence processing large model: This model is derived by adapting the basic large language model (LLM) to the geo-fence scenario. It is used to analyze device data and draw conclusions. For example, it can predict abnormal device behavior based on historical data or predict future device behavior based on its location and status. Optional basic large language models include but are not limited to the GPT system large model, the Tongyi Qianwen series large model, and the Deep Search system large model.

[0095] Candidate device weight vector: A weight value is calculated for each candidate device based on its spatiotemporal distribution information, behavior information, and historical fault information, indicating the importance and risk level of the candidate device within the monitoring area.

[0096] Spatial clustering: Devices are grouped into clusters based on their location, status, behavior, and other characteristics, typically using clustering algorithms (such as DBSCAN and K-means). The clustered device clusters help locate concentrated or important areas of devices.

[0097] Primary device cluster: After spatial clustering, the cluster containing the most important devices is obtained, usually referring to the area with the densest and most critical equipment.

[0098] Reference Fence Polygon: This is a specific fenced area for device monitoring, determined based on the distribution of the primary device cluster. This area is typically polygonal in shape, allowing for flexible adaptation to varying device distribution and monitoring requirements.

[0099] Schematically, the device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information corresponding to the candidate IoT device set are input into the electronic fence processing model. The electronic fence processing model calculates a candidate device weight vector for each candidate IoT device in the candidate IoT device set, indicating the priority and importance of the device. Devices with higher weights may be important devices. Spatial clustering is performed on each candidate IoT device based on the candidate device weight vector. During the spatial clustering process, devices with similar locations and similar status are divided into the same device cluster. The purpose of clustering is to identify the concentrated distribution areas of devices in the region. Then, a main device cluster is determined from multiple device clusters based on the device distribution, and the reference fence polygon area corresponding to the main device cluster is determined; the reference fence polygon area may usually contain the intersection of multiple device clusters or the place where key devices are concentrated, which is used for monitoring and management.

[0100] Step A8: Displaying a local selected area map corresponding to the target area location and a reference fence polygon area.

[0101] In this manual, through steps A2-A8, the system intelligently determines and displays precise device monitoring areas based on the target area location and device distribution. First, the system selects a set of candidate devices using a reference radius and device location. Then, based on their spatiotemporal distribution, behavior, and historical data, the system calculates device weights and performs spatial clustering to ultimately determine the most appropriate reference fence polygon area. This process not only improves device monitoring accuracy but also provides users with a visual and intelligent way to select device monitoring areas.

[0102] S206: monitoring the user terminal's area selection operation on the local selection area map, determining electronic fence area information based on the area selection operation, and obtaining fence item attribute information input by the user terminal;

[0103] Area selection: This refers to the process of selecting and defining an electronic fence area using a mouse or touch screen on the local selection area map on the device monitoring interface. Typically, users define the fence area by drawing an area on the map or selecting a shape such as a polygon or circle.

[0104] Fence project attribute information: refers to the relevant configuration or attributes of the fence area, such as fence name, monitoring target, security level, whether an alarm is required, etc.

[0105] Schematically, the system monitors user actions on a local selection area map. Users can define or adjust the shape and size of the geo-fence by dragging and clicking with the mouse. The system updates the geo-fence area information in real time. When selecting an area, users can also enter the project attributes of the fence, such as the fence name, monitoring target (e.g., device type), security level, and alarm rules. The system can then generate the final fence project configuration based on this information.

[0106] S208: Determine a target electronic fence based on the electronic fence area information and the fence item attribute information, and activate the target electronic fence.

[0107] Start target geo-fence: After all target geo-fences are set up, the system starts the geo-fence according to the defined fence area and attributes and begins to monitor the device status in the area in real time.

[0108] Schematically, the target geo-fence configuration is determined based on geo-fence area information (e.g., shape, location, etc.) and fence item attributes (e.g., name, alarm rules, etc.). The system then activates the target geo-fence and begins monitoring devices within that area. Once activated, the target geo-fence tracks device status in real time, records device entry and exit, and triggers corresponding events based on the configured alarm rules.

[0109] In this manual, the above method effectively helps users define and activate target geo-fences. First, the system displays the device monitoring interface and obtains the area information entered by the user. It then provides a local map view and reference fences to help users define the monitoring area. Users circle the fenced area and enter relevant attributes. Finally, the system uses this information to determine and activate the target geo-fence, beginning real-time monitoring of device status. This process ensures accurate and real-time device monitoring, providing flexible configuration and efficient monitoring capabilities, especially for complex areas and large-scale devices.

[0110] Optional, see Figure 9 , Figure 9 This is a flow chart of collecting a device transaction monitoring data table proposed in one or more embodiments of this specification. Specifically, the following method can be used to obtain the device transaction monitoring data table by performing fence device status monitoring based on the target electronic fence:

[0111] S3002: Obtain a target fence device monitoring list corresponding to the target electronic fence;

[0112] Target Fence Device Monitoring List: This refers to the list of devices within the target geo-fence area. This list includes all devices within the fence that need to be monitored, such as cameras, access control systems, sensors, and other IoT devices.

[0113] S3004: Based on the target fence device monitoring list, device transaction meta-information of the target fence device is collected and processed to obtain a device transaction monitoring data table.

[0114] Device transaction meta-information: This refers to data describing device transaction information, including transaction event information, device attribute information, and operation log information. This information includes device status changes, device-triggered alarms, device failures, and device-related transaction status information. Transaction meta-information is typically based on key data items in device monitoring data tables, such as device location information, startup information, device attribute information, device status information, and associated device transaction information (e.g., device flow and transaction information).

[0115] Device Transaction Monitoring Data Table: This table records all key events generated by the device during monitoring. This data table includes device status information, operation records, fault logs, alarm information, etc., and is mainly used for device management, fault diagnosis, performance analysis, etc.

[0116] Schematically, by obtaining device information from the target fence device monitoring list, metadata related to device status changes in each list is collected. For example, whether the device is online, whether an alarm has been triggered, whether a fault has occurred, etc. The system may monitor device status changes in real time and record these events in the device transaction monitoring data table.

[0117] In this document, through steps S3002-S3004, the system identifies devices to be monitored based on the target geo-fence and collects detailed monitoring data based on these devices. First, all relevant devices within the target fence area are obtained to generate a device monitoring list. Then, based on this list, transaction metadata for each device is collected to generate a monitoring data table containing device status, events, alarms, and other information. This process ensures comprehensive and accurate device monitoring and provides complete data support for subsequent device management, status analysis, and fault response.

[0118] Optional, see Figure 10 , Figure 10 This is a flowchart of determining the target fence device monitoring list proposed in one or more embodiments of this specification. For details, please refer to the following method:

[0119] S4002: Obtain target fence geo-hash data corresponding to the target electronic fence, and perform coarse recall processing based on the target fence geo-hash data to obtain a coarse recall device set, wherein the target fence geo-hash data is obtained based on fence geographic information of the target electronic fence after geo-hash encoding;

[0120] Coarse recall device set: This refers to the device set obtained by preliminary screening of the target area through geo-hash coding. These devices are located within the approximate range of the target geo-fence area, but may still require further refined screening.

[0121] Geohashing: Converts geographic coordinates (latitude, longitude) into a short encoded string for gridding regions and device filtering.

[0122] Indicatively, the system pre-encodes the geographic location information of each IoT device into a device geographic hash string using a hash coding method;

[0123] In actual applications, the system hashes the geographic location information of the target electronic fence into one or more fence network hash strings as the target fence geographic hash data, and then filters out the devices located in the target electronic fence from the device geographic hash string of each IOT device in the IoT device database based on the obtained target fence geographic hash data. The geographic hash values of these devices will be approximately matched with the hash value of the target fence, and the IOT devices corresponding to the matched device geographic hash values will be recorded in the coarse recall device set, so as to quickly determine whether the device is in the target electronic fence area.

[0124] In a feasible implementation, the coarse recall processing based on the target fence geohash data to obtain the coarse recall device set may be performed in the following manner:

[0125] Target prefix hash data corresponding to the target fence geo-hash data is determined, and hash matching processing is performed on device geo-hash data of the Internet of Things device based on the target prefix hash data to obtain a coarse recalled device set.

[0126] in:

[0127] Target prefix hash data: This refers to a hash prefix extracted from the target fence's geohash data. It represents the approximate scope or location of the fenced area. Prefix hash data is typically a rough representation of the target area and is used to quickly filter devices within the area.

[0128] Device geohash data of IoT devices: refers to the data obtained by converting the geographic location (latitude and longitude) of each IoT device through geohash encoding. It is usually a unique hash value used to represent the location of the device in geographic space.

[0129] Hash matching: This process quickly filters devices by comparing the target prefix hash data with the prefix portion of the device's geohash data. Hash matching enables efficient location matching, quickly locating devices within the target fenced area.

[0130] Schematically, the system performs geo-hash encoding on the geographic information (such as longitude and latitude) of the target fence area to obtain the hash value of the target fence. Then, the system extracts the prefix part based on the hash value, usually selecting the first preset number of characters as the prefix hash data, which represents the approximate range of the target fence area. The prefix hash data of the target fence is prefix-matched with the device geographic hash data of all devices. Devices that match the same or similar prefixes will be selected as coarse recall devices. Based on the results of the hash match, the system filters out all devices located in the target fence area and groups them into a coarse recall device set. These devices meet the preliminary geographic area screening conditions and can be further refined later.

[0131] In this document, a hash matching method is used in practice to compare direct geolocation matching, enabling the system to quickly identify IoT devices within the approximate range of a target fenced area. This method efficiently matches the target fence's geohash data with the device's geohash data, ensuring rapid device location during initial screening. This reduces the computational complexity of direct geolocation matching and provides foundational data for subsequent refined recall. This prefix hash-based screening method is highly efficient and accurate, making it particularly suitable for monitoring and managing large-scale IoT devices.

[0132] S4004: Determining reference polygonal area selection information based on the target electronic fence, and performing a first fine recall process on the coarsely recalled device set based on the reference polygonal area selection information to obtain a first recalled device set; and determining reference circular area selection information based on the target electronic fence, and performing a second fine recall process on the coarsely recalled device set based on the reference circular area selection information to obtain a second recalled device set;

[0133] Reference polygonal area selection information: This refers to the monitoring area defined based on the polygonal form of the target geo-fence area. Polygonal fence areas can represent irregular geographic areas and are often used to handle complex monitoring scenarios.

[0134] First fine recall: Based on the reference polygon area selection information, the rough recall device set is accurately screened to ensure that the IoT device is located within the target polygon area.

[0135] Schematically, the system generates a reference polygonal area based on the definition of the target electronic fence (such as the area shape and boundaries set by the user). The reference polygonal area is usually determined based on the location of the device and the geometric shape of the target fence. The polygonal area accurately describes the monitoring area of the target electronic fence and is particularly suitable for monitoring areas with complex shapes. By applying the point-in-polygon algorithm to the coarse recall device set (for example, the ray method: emit a ray from the device position in any direction, and count the number of intersections between the ray and the polygon edge. If the number of intersections is odd, the device is inside the polygon; if it is even, the device is outside the polygon), the system can accurately determine which devices are located in the polygonal area of the target fence, and record the device in the first recall device set when it is within the polygonal area of the target fence.

[0136] Reference circular area selection information: This refers to taking the maximum value of the target geo-fence's endpoints and the fence center as the circular area selection radius, and defining the monitoring area based on the circular area selection radius and the fence center point.

[0137] Second precision recall (based on circular area selection information): Based on the reference circular area of the target geo-fence, the system screens out devices within the circular area by calculating whether the distance between the device and the area's center point is less than or equal to the circular area selection radius (using the Haversine formula or the Euclidean distance formula). This process accurately screens eligible devices and removes those outside the monitoring range.

[0138] In a feasible implementation manner, performing the first fine recall process on the coarsely recalled device set based on the reference polygon selection information to obtain the first recalled device set may refer to the following method:

[0139] Step B2: obtaining the geographical locations of multiple polygon corner points corresponding to the reference polygon circled information, and determining the target polygon geographical area based on the geographical locations of the polygon corner points;

[0140] Polygon corner geographic location: The latitude and longitude coordinates of each corner point of the target geo-fence.

[0141] Target polygon geographic area: A specific geographic area determined based on the geographic location of the reference polygon corner points, representing the range monitored by the target electronic fence.

[0142] Step B4: Determine the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set, perform regional device location matching processing on the coarse recall device geographic location based on the target polygonal geographical area to obtain a first regional recall device location set, and determine the first recall device set corresponding to the first regional recall device location set.

[0143] Regional device location matching processing: refers to the process of matching the geographic location of the coarse recall device with the target polygonal geographic area, recording the device location within the target polygonal geographic area into the first regional recall device location set, and then determining the recall device corresponding to each location in the first regional recall device location set, thereby obtaining the first recall device set.

[0144] In a feasible implementation, the determining of the reference circular area selection information based on the target electronic fence and the performing of the second fine recall processing on the coarse recalled device set based on the reference circular area selection information to obtain the second recalled device set may be performed in the following manner:

[0145] Step C2: Obtaining the geographic locations of multiple polygon corner points and the center point of the fence corresponding to the target electronic fence, taking the reference distances between the geographic locations of the polygon corner points and the geographic location of the fence center point, selecting the maximum reference distance from the reference distances as a circular selection recall radius, and taking the geographic location of the fence center point and the circular selection recall radius as reference circular area selection information;

[0146] Reference distance: This refers to the distance from the center point of the fence to the corner point of the polygon. By calculating these distances, you can understand the size of the fence area and help determine the appropriate circle selection recall radius.

[0147] Circular Recall Radius: The radius calculated based on the reference distance is used to determine a circular area that will be used as the monitoring range for fine recall screening.

[0148] Reference circular area selection information: circular monitoring area information defined by the fence center point and circular selection recall radius.

[0149] Schematically, the system obtains the geographic locations of multiple polygon corner points and the center point of the target fence area. By calculating the distances between the fence center point and the polygon corner points, a list of reference distances is generated. The maximum reference distance among all reference distances is selected as the circular selection and recall radius. The system uses the geographic location of the fence center point and the calculated circular selection and recall radius as reference circular area selection information for subsequent device screening and fine recall processing.

[0150] Step C4: Determine the target circular geographic recall area based on the reference circular selection information, determine the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set, perform regional device location matching processing on the coarse recall device geographic location based on the target circular geographic recall area to obtain a second regional recall device location set, and determine the second recall device set corresponding to the second regional recall device location set.

[0151] Regional device location matching: This process matches the geographic location of the coarsely recalled device with the target circular geographic recall area to ensure the device is located within the circular area. The distance between the device and the center of the circle is typically calculated using the Haversine formula or Euclidean distance.

[0152] Second area recall device location set: After fine recall processing, the determined device set is completely located in the target circular area.

[0153] Second recalled device set: A device set formed by screening devices that meet the monitoring conditions from the second area recalled device location set.

[0154] Schematically, the system constructs a target circular geographic recall area based on the reference circular area selection information determined in the previous step. The system determines whether the device is located in the target circular area based on the geographic location of the rough recalled device. After regional device location matching processing, the system filters out the devices located in the target circular area to form a second recall device set.

[0155] For example, let's assume the system has calculated a circular area with a radius of 300 meters for a shopping mall. The system uses the Haversine formula to calculate the distance between each coarse recall device (such as the mall's access control system, sensors, and surveillance cameras) and the mall center to ensure that the device is within the 300-meter radius. If the device is within this circular area, the system will add it to the second recall device set.

[0156] Through this approach, the system can refine the coarse recall device set based on the reference circular area selection information of the target geo-fence, obtaining a set of devices that meet the location conditions of the target circular area. First, by calculating and determining the radius and center point of the reference circular area, the system creates a precise circular monitoring area. Then, by matching each device's geographic location, the system selects devices within this circular area, ultimately generating a second recall device set. This process ensures precise device positioning and efficient screening, adapting to different regional monitoring needs.

[0157] S4006: Merge the first recalled device set and the second recalled device set to obtain a target fence device monitoring list corresponding to the target electronic fence.

[0158] Target Fence Device Monitoring List: The final device monitoring list contains all devices that meet the target geo-fence area (whether polygonal or circular).

[0159] Schematically, the first recalled device set (based on polygonal areas) and the second recalled device set (based on circular areas) are first merged. When fusing the device sets, the system will deduplicate the devices based on their unique identifiers (such as device IDs or serial numbers). Since a device may be selected in both the first and second recall steps, the deduplication operation ensures that each device appears only once in the final device monitoring list. The deduplicated device set is the final target fence device monitoring list. This list includes all devices that meet the requirements of the target electronic fence, and the system can perform further device monitoring, fault detection, alarm processing, and other operations based on this list.

[0160] In this specification, through steps S4002-S4006, a comprehensive screening process from coarse recall to fine recall of the target electronic fence is implemented, significantly improving the efficiency and accuracy of device monitoring. First, a coarse recall is performed based on geographic hash data to quickly screen out devices located in the target area; then, two rounds of fine recall are performed by referring to polygonal and circular areas to ensure that the devices strictly meet the regional boundary requirements. Finally, the system merges the finely recalled device set, removes duplicate data, and generates the final device monitoring list. This process not only improves the accuracy of device screening, but also optimizes the efficiency of large-scale device monitoring, ensures the comprehensiveness, accuracy, and real-time nature of device monitoring, and meets the needs of different monitoring area shapes and sizes.

[0161] The following will be combined Figure 11 , the equipment monitoring and processing device provided in this manual is introduced in detail. It should be noted that, Figure 11 The equipment monitoring processing device shown is used to execute the Figures 1 to 10 For the convenience of explanation, only the parts related to this specification are shown. For the specific technical details not disclosed, please refer to this specification. Figures 1 to 10 The embodiment shown.

[0162] See Figure 11 , which shows a schematic diagram of the structure of the device monitoring processing device of this specification. The device monitoring processing device 1 can be implemented as all or part of the device through software, hardware, or a combination of both. According to some embodiments, the device monitoring processing device 1 includes a fence determination module 11, a monitoring processing module 12, and an information output module 13, which are specifically used to:

[0163] The fence determination module 11 is used to obtain the target electronic fence information input by the user terminal in the device monitoring interface, and activate the target electronic fence based on the target electronic fence information;

[0164] A monitoring processing module 12 is configured to perform fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table;

[0165] The information output module 13 is configured to perform device monitoring and inspection processing on the target IoT device based on the device processing transaction monitoring data table to obtain device monitoring transaction information, and output the device monitoring transaction information to the user terminal.

[0166] Optionally, the step of obtaining target electronic fence information input by the user terminal on the device monitoring interface and activating the target electronic fence based on the target electronic fence information includes:

[0167] Displaying a device monitoring interface to a user terminal and obtaining a target area location input by the user terminal on the device monitoring interface;

[0168] Displaying a local selected area map corresponding to the target area location, or displaying a local selected area map corresponding to the target area location and a reference fence polygon area;

[0169] monitoring an area selection operation performed by the user terminal on the local selection area map, determining electronic fence area information based on the area selection operation, and obtaining fence item attribute information input by the user terminal;

[0170] A target electronic fence is determined based on the electronic fence area information and the fence item attribute information, and the target electronic fence is activated.

[0171] Optionally, the display of the local selected area map corresponding to the target area location and the reference fence polygon area includes:

[0172] Determine a local selection area map corresponding to the target area location, and obtain a set of candidate IoT devices in the local selection area map based on a preset reference radius with the target area location as a reference;

[0173] Determine device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information corresponding to the candidate IoT device set;

[0174] Based on the device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information, a candidate device weight vector corresponding to each candidate IoT device in a candidate IoT device set is determined using an electronic fence processing large model; spatially clustering each candidate IoT device based on the candidate device weight vector to obtain a primary device cluster; and determining a reference fence polygon area corresponding to the primary device cluster.

[0175] A local selected area map corresponding to the target area location and a reference fence polygon area are displayed.

[0176] Optionally, the fence device status monitoring process based on the target electronic fence is performed to obtain a device transaction monitoring data table, including:

[0177] Obtain a target fence device monitoring list corresponding to the target electronic fence;

[0178] Based on the target fence device monitoring list, device transaction meta information of the target fence device is collected and processed to obtain a device transaction monitoring data table.

[0179] Optionally, the method further includes:

[0180] Obtaining target fence geo-hash data corresponding to the target electronic fence, and performing coarse recall processing based on the target fence geo-hash data to obtain a coarse recall device set, wherein the target fence geo-hash data is obtained based on fence geographic information of the target electronic fence after geo-hash encoding;

[0181] Determining reference polygonal area selection information based on the target electronic fence, and performing a first fine recall process on the coarsely recalled device set based on the reference polygonal area selection information to obtain a first recalled device set; and determining reference circular area selection information based on the target electronic fence, and performing a second fine recall process on the coarsely recalled device set based on the reference circular area selection information to obtain a second recalled device set;

[0182] The first recalled device set and the second recalled device set are merged to obtain a target fence device monitoring list corresponding to the target electronic fence.

[0183] Optionally, performing coarse recall processing based on the target fence geohash data to obtain a coarse recall device set includes:

[0184] Target prefix hash data corresponding to the target fence geo-hash data is determined, and hash matching processing is performed on device geo-hash data of the Internet of Things device based on the target prefix hash data to obtain a coarse recalled device set.

[0185] Optionally, performing a first fine recall process on the coarsely recalled device set based on the reference polygon circle selection information to obtain a first recalled device set includes:

[0186] Acquire the geographical locations of multiple polygon corner points corresponding to the reference polygon circled information, and determine the target polygon geographical area based on the geographical locations of the polygon corner points;

[0187] Determine the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set, perform regional device location matching processing on the coarse recall device geographic location based on the target polygonal geographical area to obtain a first regional recall device location set, and determine the first recall device set corresponding to the first regional recall device location set.

[0188] Optionally, determining reference circular area selection information based on the target electronic fence, and performing a second fine recall process on the coarsely recalled device set based on the reference circular area selection information to obtain a second recalled device set includes:

[0189] Obtaining a plurality of polygon corner point geographic locations and a fence center point geographic location corresponding to the target electronic fence, taking reference distances between the polygon corner point geographic locations and the fence center point geographic location, selecting a maximum reference distance from the reference distances as a circular selection recall radius, and taking the fence center point geographic location and the circular selection recall radius as reference circular area selection information;

[0190] Based on the reference circular selection information, a target circular geographic recall area is determined, and the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set is determined. Based on the target circular geographic recall area, regional device location matching processing is performed on the coarse recall device geographic location to obtain a second regional recall device location set, and a second recall device set corresponding to the second regional recall device location set is determined.

[0191] Optionally, performing device monitoring inspection processing on the target IoT device based on the device processing transaction monitoring data table to obtain device monitoring transaction information includes:

[0192] Calculate reference transaction monitoring indicator data based on the device processing transaction monitoring data table according to preset transaction monitoring dimension logic;

[0193] Based on the reference transaction monitoring indicator data, a preset equipment monitoring inspection template is used to generate equipment monitoring transaction information.

[0194] It should be noted that the device monitoring processing apparatus provided in the above embodiment, when executing the device monitoring processing method, only uses the division of the above-mentioned functional modules as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the device monitoring processing apparatus provided in the above embodiment and the device monitoring processing method embodiment are based on the same concept. The implementation process is detailed in the method embodiment and will not be repeated here.

[0195] The above serial numbers in this specification are for description only and do not represent the advantages or disadvantages of the embodiments.

[0196] This specification also provides a computer storage medium, which can store multiple instructions, which are suitable for being loaded and executed by a processor as described above. Figures 1 to 10 The device monitoring processing method of the embodiment shown in the figure can be found in the specific execution process. Figures 1 to 10 The detailed description of the illustrated embodiment will not be repeated here.

[0197] This specification also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figures 1 to 10 The device monitoring processing method of the embodiment shown in the figure can be found in the specific execution process. Figures 1 to 10 The detailed description of the illustrated embodiment will not be repeated here.

[0198] Please refer to Figure 12 , which is a block diagram of the structure of an electronic device provided in an embodiment of this specification. The electronic device described in this specification may include one or more of the following components: a processor 1010, a memory 1020, an input device 1030, an output device 1040, and a bus 1050. The processor 1010, memory 1020, input device 1030, and output device 1040 may be connected via a bus 1050.

[0199] The processor 1010 may include one or more processing cores. The processor 1010 utilizes various interfaces and circuits to connect various components within the electronic device. It executes instructions, programs, code sets, or instruction sets stored in the memory 1020, as well as accesses data stored in the memory 1020, to perform various functions of the electronic device and process data. Optionally, the processor 1010 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 1010 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem handles wireless communications. It is understood that the modem may not be integrated into the processor 1010 and may be implemented separately via a communications chip.

[0200] The memory 1020 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 1020 includes a non-transitory computer-readable storage medium. The memory 1020 may be used to store instructions, programs, codes, code sets, or instruction sets.

[0201] The input device 1030 is used to receive input commands or data and includes, but is not limited to, a keyboard, mouse, camera, microphone, or touch-screen device. The output device 1040 is used to output commands or data and includes, but is not limited to, a display device and a speaker. In the embodiments of this specification, the input device 1030 may be a temperature sensor for obtaining the operating temperature of the electronic device. The output device 1040 may be a speaker for outputting audio signals.

[0202] In addition, those skilled in the art will understand that the structures of the electronic devices shown in the above figures do not limit the electronic devices. The electronic devices may include more or fewer components than shown, or may combine certain components or arrange the components differently. For example, the electronic devices may also include radio frequency circuits, input units, sensors, audio circuits, wireless fidelity (WIFI) modules, power supplies, Bluetooth modules, and other components, which are not described in detail here.

[0203] In the embodiments of this specification, the execution entity of each step can be the electronic device described above. Optionally, the execution entity of each step is the operating system of the electronic device. The operating system can be Android, iOS, or other operating systems, and this embodiment of this specification does not limit this.

[0204] exist Figure 12 In the electronic device, the processor 1010 can be used to call the program stored in the memory 1020 and execute it to implement the device monitoring processing method as described in the various method embodiments of this specification.

[0205] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory, or a random access memory.

[0206] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, storage, and display, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the target electronic fence information and device transaction monitoring data tables mentioned in this specification are all obtained with full authorization.

[0207] The above disclosure is only a preferred embodiment of this specification, and certainly cannot be used to limit the scope of rights of this specification. Therefore, equivalent changes made according to the claims of this specification are still within the scope covered by this specification.

Claims

1. A device monitoring processing method, the method comprising: Acquire target electronic fence information input by the user terminal on the device monitoring interface, and activate the target electronic fence based on the target electronic fence information; Performing fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table; Based on the device processing transaction monitoring data table, device monitoring and inspection processing is performed on the target Internet of Things device to obtain device monitoring transaction information, and the device monitoring transaction information is output to the user end.

2. The method according to claim 1, wherein obtaining target electronic fence information input by the user terminal on the device monitoring interface and activating the target electronic fence based on the target electronic fence information comprises: Displaying a device monitoring interface to a user terminal and obtaining a target area location input by the user terminal on the device monitoring interface; Displaying a local selected area map corresponding to the target area location, or displaying a local selected area map corresponding to the target area location and a reference fence polygon area; monitoring an area selection operation performed by the user terminal on the local selection area map, determining electronic fence area information based on the area selection operation, and obtaining fence item attribute information input by the user terminal; A target electronic fence is determined based on the electronic fence area information and the fence item attribute information, and the target electronic fence is activated.

3. The method according to claim 2, wherein the displaying of the local selected area map corresponding to the target area location and the reference fence polygon area comprises: Determine a local selection area map corresponding to the target area location, and obtain a set of candidate IoT devices in the local selection area map based on a preset reference radius with the target area location as a reference; Determine device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information corresponding to the candidate IoT device set; Based on the device spatiotemporal distribution information, device behavior information, and historical device alarm and fault information, a candidate device weight vector corresponding to each candidate IoT device in a candidate IoT device set is determined using an electronic fence processing large model; spatially clustering each candidate IoT device based on the candidate device weight vector to obtain a primary device cluster; and determining a reference fence polygon area corresponding to the primary device cluster. A local selected area map corresponding to the target area location and a reference fence polygon area are displayed.

4. The method according to claim 1, wherein the step of performing fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table comprises: Obtain a target fence device monitoring list corresponding to the target electronic fence; Based on the target fence device monitoring list, device transaction meta information of the target fence device is collected and processed to obtain a device transaction monitoring data table.

5. The method according to claim 4, further comprising: Obtaining target fence geo-hash data corresponding to the target electronic fence, and performing coarse recall processing based on the target fence geo-hash data to obtain a coarse recall device set, wherein the target fence geo-hash data is obtained based on fence geographic information of the target electronic fence after geo-hash encoding; Determining reference polygonal area selection information based on the target electronic fence, and performing a first fine recall process on the coarsely recalled device set based on the reference polygonal area selection information to obtain a first recalled device set; and determining reference circular area selection information based on the target electronic fence, and performing a second fine recall process on the coarsely recalled device set based on the reference circular area selection information to obtain a second recalled device set; The first recalled device set and the second recalled device set are merged to obtain a target fence device monitoring list corresponding to the target electronic fence.

6. The method according to claim 5, wherein the step of performing a coarse recall process based on the target fence geohash data to obtain a coarse recall device set comprises: Target prefix hash data corresponding to the target fence geo-hash data is determined, and hash matching processing is performed on device geo-hash data of the Internet of Things device based on the target prefix hash data to obtain a coarse recalled device set.

7. The method according to claim 5, wherein performing a first fine recall process on the coarsely recalled device set based on the reference polygon selection information to obtain a first recalled device set comprises: Acquire the geographical locations of multiple polygon corner points corresponding to the reference polygon circled information, and determine the target polygon geographical area based on the geographical locations of the polygon corner points; Determine the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set, perform regional device location matching processing on the coarse recall device geographic location based on the target polygonal geographical area to obtain a first regional recall device location set, and determine the first recall device set corresponding to the first regional recall device location set.

8. The method according to claim 5, wherein determining reference circular area selection information based on the target electronic fence, and performing a second fine recall process on the coarsely recalled device set based on the reference circular area selection information to obtain a second recalled device set, comprises: Obtaining a plurality of polygon corner point geographic locations and a fence center point geographic location corresponding to the target electronic fence, taking reference distances between the polygon corner point geographic locations and the fence center point geographic location, selecting a maximum reference distance from the reference distances as a circular selection recall radius, and taking the fence center point geographic location and the circular selection recall radius as reference circular area selection information; Based on the reference circular selection information, a target circular geographic recall area is determined, and the coarse recall device geographic location corresponding to the coarse recall device in the coarse recall device set is determined. Based on the target circular geographic recall area, regional device location matching processing is performed on the coarse recall device geographic location to obtain a second regional recall device location set, and a second recall device set corresponding to the second regional recall device location set is determined.

9. The method according to claim 1, wherein performing device monitoring inspection processing on the target IoT device based on the device processing transaction monitoring data table to obtain device monitoring transaction information comprises: Calculate reference transaction monitoring indicator data based on the device processing transaction monitoring data table according to preset transaction monitoring dimension logic; Based on the reference transaction monitoring indicator data, a preset equipment monitoring inspection template is used to generate equipment monitoring transaction information.

10. A device monitoring and processing apparatus, comprising: A fence determination module is used to obtain target electronic fence information input by the user terminal on the device monitoring interface and activate the target electronic fence based on the target electronic fence information; A monitoring processing module, configured to perform fence device status monitoring processing based on the target electronic fence to obtain a device transaction monitoring data table; An information output module is used to perform device monitoring and inspection processing on the target Internet of Things device based on the device processing transaction monitoring data table to obtain device monitoring transaction information, and output the device monitoring transaction information to the user end.

11. A computer storage medium storing a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 9.

12. A computer program product, the computer program product storing at least one instruction, wherein the at least one instruction is loaded by a processor and executes the method steps according to any one of claims 1 to 9.

13. An electronic device comprising: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps according to any one of claims 1 to 9.

Images