TW201626324A - Equipment and warning event process method for smart community and system thereof - Google Patents

Abstract

The invention discloses an equipment and warning event process method applied to smart community, which is an integration method for each sub-system management rule in the smart society, especially for the application of the equipment and warning events. The smart community comprises sub-systems of different companies and types, for example, access systems, energy saving systems or image monitor system, etc. The sub-systems have management rules of respective equipment and warning events. The flexibility of interfacing can be enhanced by integrating these management rules without losing operation features of each sub-system. This invention comprises: integration manner of equipment management rules, integration manner of warning event management rule and abnormal monitor manner of sub-system equipment and warning event. The integration of equipment management rule is to establish mapping correlation between rear end management platform of smart community and equipment management rules of the sub-system to achieve management for warning event management level. The abnormal monitor manner of sub-system equipment and warning event is that the rear management platform of smart community can determine whether or not the function of equipment and warning event of the sub-system is abnormal according to the management rules of the sub-system so as to enhance the credibility of error determination.

Description

Intelligent community equipment and alarm event processing method and system thereof

The invention relates to a device and alarm event processing method applied to a smart community, in particular to the integration of a management layer of a smart community back-end management platform and a subsystem, and is applied to equipment and alarm event management rules.

The management of equipment and alarm events is a common problem in system services. For example, the image monitoring system needs to manage the camera equipment, and when a suspicious person is detected, or the camera fails, an alarm event message can be sent to inform the manager. However, different vendors or different systems have different management rules for devices and alarm events, such as the update frequency of device status, several levels of alarm event levels, and alarm event level representation symbols, etc., for different subsystems in the smart community. In this case, the integration complexity is very high, and the responsible vendors of the subsystems often need to be modified. The common integration method is to set a unified specification for the smart community platform system, and through the network interface, for example: Web Services, the subsystem transmits the device and alarm event data to the smart community platform, and the upper intelligent community platform if the alarm event message is important. It is divided into 5 levels. If the subsystem is divided into 7 levels, the subsystem needs to perform the conversion action in accordance with this unified specification. The parameters of the equipment and alarm events related to the subsystem may change frequently. In order to meet the new requirements, the transmission interface of the upper-layer smart community platform system has to be changed or modified. If the upper-layer smart community platform system changes the interface specifications, other interfaces Subsystems may all need to be modified. In addition, the users of the upper-level smart community platform often want to know the rules of the subsystems because of the customer's changing needs. For example, the graphic control screen of the smart community platform needs to be able to instantly display the status of the living room light of the smart home system, and then it is necessary to know the state change. The method is active notification, passive notification or notification every few seconds. In addition, in the integrated system, when the central management platform is interfaced with other subsystems, it is often impossible to judge whether the subsystem is abnormal. For example, the fire protection system transmits 60 times of the smoke detector to the smart community platform within 1 minute, in a short time. It is normal to transmit a lot of times. Sometimes you need to ask the manager or engineer of the fire protection system. Different equipments have different characteristics and it is difficult to check them one by one. Because the above-mentioned prior art technologies are integrated in a unified specification, the characteristics and management methods of different systems are not fully considered, resulting in poor scalability and usability of the smart community platform. When the rules change, the system needs to be modified, resulting in waste of manpower and material resources. .

In view of the shortcomings derived from the above-mentioned conventional methods, the inventor of the present invention has improved and innovated, and after years of painstaking research, he finally succeeded in researching and developing the equipment and alarm event processing methods and systems of the smart community.

The main purpose of the present invention is to provide a device and alarm event processing method applied to a smart community, which refers to a management rule of equipment and alarm events in the back-end management platform and the management subsystem of the smart community, and a smart community back-end management platform. After receiving the management rules uploaded by the subsystem, the management rules of the smart community back-end management platform can establish a mapping relationship with the management rules of the subsystem, so that the smart community back-end management platform can effectively manage the subsystem equipment and alarm events.

The second purpose of the present invention is that the smart community back-end management platform can more accurately determine whether the subsystem has an abnormality according to the management rules of the subsystem to increase system security.

Another object of the present invention is that when the device and alarm event management rules of the smart community back-end management platform or subsystem are changed, the smart community back-end management platform and subsystem do not need engineers to modify the system program source code, and reduce Labor costs.

A further object of the present invention is that after the smart community back-end management platform receives the subsystem device and alarm event management rules, the smart community back-end management platform can flexibly apply the management rules of the subsystem to make the device and alarm events more usable. .

The invention provides a device and alarm event processing method applied to a smart community, which is developed by a smart community and a smart building back end management platform, including an integrated method of device management rules and an integrated method of alarm event management rules. And subsystem equipment and alarm event anomaly monitoring methods three parts. The integration method of equipment management rules refers to the management rules of the smart community back-end management platform immediately after the smart community back-end management platform receives the device management rules uploaded by the subsystem, so that the smart community back-end relationship is established. The management platform can effectively manage the equipment of the subsystem according to the management rules of the subsystem.

The integration method of the alarm event management rules refers to the intelligent event back-end management platform receiving the alarm event management rules uploaded by the subsystem, and the management rules of the smart community back-end management platform immediately establish a mapping relationship with the subsystem alarm event management rules, so that the wisdom The community back-end management platform can effectively manage the alarm events of the subsystem according to the management rules of the subsystem.

Subsystem equipment and alarm event anomaly monitoring method refers to the basis The management rules of the system determine whether the device and alarm event functions of the subsystem are abnormal.

The invention provides a smart community device and alarm event processing method and system thereof, and has the following advantages when compared with other conventional technologies:

1. A device and alarm event processing method applied to a smart community, wherein the device management rule integration method can perform device management in a manner of integrating management rules, and can improve device management of the subsystem of the smart community back-end management platform degree.

2. The device and the alarm event processing method applied to the smart community, wherein the integrated method of the alarm event management rule can perform the alarm event management by integrating the management rules, and can improve the smart community back-end management platform to the subsystem. The alarm event management level.

3. A device and alarm event processing method applied to a smart community according to the present invention, wherein the subsystem abnormality monitoring method can accurately determine whether the device and the alarm event function of the subsystem are normal according to the management rules of the subsystem. Improve usability and credibility.

100‧‧‧Smart Community Backend Management Platform

110‧‧‧Management Rule Cache Module

120‧‧‧Management Rules Monitoring Module

130‧‧‧Management Rules Control Module

200‧‧‧ subsystem

210‧‧‧Subsystem A

211‧‧‧Device Management Rules

212‧‧‧ Alarm Event Management Rules

220‧‧‧Subsystem B

221‧‧‧Device Management Rules

222‧‧‧ Alarm Event Management Rules

230‧‧‧ device

A‧‧‧Device Management Rule Tree

B‧‧‧Alarm Event Management Rule Tree

Please refer to the detailed description of the present invention and its accompanying drawings, which can further understand the technical content of the present invention and its effect. The related drawings are: FIG. 1 is a method and system for processing equipment and alarm events of the smart community of the present invention. Schematic diagram of the system architecture; FIG. 2 is a schematic diagram of the method for integrating the device and alarm event processing method of the smart community of the present invention and the device management rule of the system; FIG. 3 is a schematic diagram of the device and alarm event processing method of the smart community of the present invention and the alarm event of the system thereof Schematic diagram of the integration method of management rules; 4 is a flow chart of the device and alarm event processing method of the smart community of the present invention and a subsystem abnormality monitoring method thereof in the device management process; FIG. 5 is a schematic diagram of the device and alarm event processing method of the smart community and the subsystem of the system thereof. The monitoring method is a processing flow chart for alarm event management.

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The present invention is further described with reference to the accompanying drawings. Please refer to FIG. 1 , which is a schematic diagram of a system architecture of a device and an alarm event processing method and a system thereof according to the smart community, which is mainly composed of a smart community backend management platform 100 and a sub-system. The system 200 is composed of a smart community back-end management platform 100, which has the ability to manage the rule data processing capability and provide the interface to the subsystem 200, and is connected to the subsystem 200 through the network, and the wisdom The community backend management platform 100 includes a management rule cache module 110, a management rule monitoring module 120, and a management rule control module 130. The management rule cache module 110 mainly temporarily stores management rules of the smart community management platform and subsystems. The management rule monitoring module 120 is mainly responsible for monitoring whether the device data or the alarm event data uploaded by the subsystem meets the management rule. The management rule monitoring module 130 mainly provides an interface between the HTTP or TCP/IP interface and the subsystem, and receives the After the management rules of the subsystem, the data is parsed, and the parsed management rules are placed in the management rule cache module 110.

A subsystem 200 refers to one or several heterogeneous subsystems, such as subsystem A 210, subsystem B 220, and device management rules included in subsystem A 210 Then, the 211 and the alarm event management rule 212, the subsystem B 220 includes the device management rule 221 and the alarm event management rule 222, and the subsystem 2 needs to upload the device management rule (211, 221) and the alarm event management rule (212, 222) to The management rule monitoring module 130 of the smart community backend management platform 100 can then upload device data or alarm event data.

2 is a schematic diagram of a method for integrating device management rules of a device and an alarm event processing method applied to a smart community according to the present invention, and an XML format of a management rule of a subsystem A device management rule 211 and a subsystem B device management rule 221 The subsystem can also be uploaded to the smart community back-end management platform through the JSON format or the webpage filling method. After the management rule control module 130 parses the device management rules of the subsystem, it becomes the device management rule tree A and the device management rule. The node names of the tree view A are mapped to the tags of the XML content. There are <Device> and <Status> in the <DeviceRule>. There are devices and states in the table device management rules, and one or several <Category in <Device> >, the representative device 230 (shown in Figure 1) has multiple categories, <Category> has <Name>, <Frequency>, and <UpdateMode>, representing the name of the device type, updating the status frequency (in seconds), updating Mode (subsystem active device status upload or smart community backend management platform queries the subsystem), <Status> has <ON>, <OFF> and <STOP>, which means that the device status is turned on, off and stopped. The value represented by the device, for example, in the case of the subsystem A device management rule 211, there are two devices, Reed and Camera. The Reed device updates the state every 60 seconds, and is uploaded by the subsystem to the smart community back-end management platform, Camera. Then, when the state is triggered, the state is transmitted, and the subsystem is uploaded to the smart community back-end management platform. In the device state of subsystem A, 1 table is opened, 0 table is closed, and 2 tables are stopped. In the subsystem B device management rule 32, there are two devices, SmokeDetector and CODetector, and SmokeDetector device. The status is updated every 60 seconds, and is uploaded by the subsystem to the smart community back-end management platform. The CODetector is 120 updated once, and the smart community back-end management platform queries the subsystem, and the device management rule 221 of the subsystem B, The 100 table is open, the 1 table is closed, and there is no definition of stop. The device management rule tree A contains the device management rules of all the smart community back-end management platforms and subsystems. For the state representative values, the ON, OFF, and STOP of the smart community back-end management platforms are respectively turned on, off, and stopped. Subsystem A is 1, 0, 2, and subsystem B is 100, 1, no definition. When the device management rule tree 4 is established, the state representative value of the subsystem will become the representative value of the smart community back-end management platform. For example, under the node of ON, the leaf is the subsystem A, and the subsystem. 100 of B. Later, when the subsystem transfer device status comes up, the above node is found according to the leaf to identify the status of the subsystem. In addition, the subsystem device type is also stored under the node of the Category. When the subsystem transmits the device data, the smart community back-end management platform queries whether there is a device type under the node. In addition, the management rule cache module stored in the smart community, for the device type with higher update frequency, when the device status data is transmitted, can be directly transferred to the cache memory without first writing the database to improve the system. efficacy.

Please refer to FIG. 3 , which is a schematic diagram of an integrated method of an alarm event management rule applied to a smart community device and an alarm event processing method according to the present invention. As can be seen from the figure, 212 and 222 are examples of the management rule XML format of subsystem A and subsystem B respectively. The subsystem can also be uploaded to the smart community back-end management platform through JSON format or webpage filling mode, and the control rule control module is adopted. After the alarm event management rule of the parsing subsystem is 130, it becomes the alarm event management rule tree B, and the node name of the alarm event management rule tree B is mapped with the label of the XML content, and <AlertRule> has <Alert> , <Handle> And <Level>, the table alarm event management rules have alarm, processing and level information, <Alert> has one or several <Category>, table alarm events have multiple categories, <Category> has <Name>, < Notify>, the name of the alarm event type, the alarm event mode (SMS or E-mail), <Sustain>, <End>, the representative value of the table alarm event processing duration and end, <Level> <Warning>, <Low>, <Medium>, <High>, <Critical>, the table alarm event level has 5 levels according to severity, <Warning> is the lightest, <Critical> is the most serious, for example: with subsystem A The alarm event management rule 212 has two alarm events: ReedException and CameraException. When a ReedException alarm event occurs, an SMS notification will be sent to notify the relevant personnel. CameraException is to send an E-mail, and the processing representative value of the subsystem A is 0. The alarm event is continuously sent. The alarm event of the 1 table has ended. The alarm event level of subsystem A is only 0, 1, 2 and 3 levels. The 0 table is the lightest and the 2 table is the most serious. It is the mapping rule to the alarm event. 5 levels, so 1 is mapped to <Low> and <Medium>, 2 is mapped to <High> and <Critical>, in the case of the subsystem B alarm event management rule 222, there are two alarm events: SmokeDetectorException and CODetectorException. When an alarm event occurs, the SMS is sent to notify the relevant personnel, and the processing value of the subsystem B is represented. In the middle, the S table continuously sends alarm events, the E table alarm event has ended, and the subsystem B alarm event level is divided into a~j total 10 levels, the a table is the lightest, the j table is the most serious, and the mapping to the alarm event management There are 5 levels of rules, so a and b are mapped to <Warning>, c and d are mapped to <Low>, e and f are mapped to <Medium>, and g and h are mapped to <High>, i, j. Map to <Critical>. The alarm event management rule tree diagram 6 contains alarm event management rules for all subsystems and is stored in the management rule cache module of the smart community. When the alarm event management rule tree diagram 6 is established, the representative value of the subsystem becomes a smart community. The leaf of the representative value of the end management platform, for example, under the node of Level's Warning, the leaf is the 0 of the subsystem A, and the a and b of the subsystem B. Later, when the subsystem sends an alarm event, the above node is found according to the leaf to identify the state of the subsystem. In addition, the subsystem alarm event type is also stored under the node of the Category. When the subsystem transmits the alarm event data, the smart community back-end management platform queries the node for the type of the alarm event.

Please refer to FIG. 4 , which is a flow chart of equipment monitoring of a subsystem abnormality monitoring method applied to a smart community device and an alarm event processing method according to the present invention. As can be seen from the figure, the steps of the intelligent community back-end management platform to monitor whether the device is abnormal or not are as follows: Step 1: The S401 subsystem uploads the device management rules to the smart community back-end management platform, and the management rules include the device type and name. , update the status frequency, update mode and status representative value, etc.; Step 2: S402 intelligent community back-end management platform management rule control module analysis management rule, after the analysis, S403 establishes the device management rule tree, and stores the management rule fast Take the module; Step 3, S404 subsystem uploads device data, such as: lamp, reed switch, camera, etc., equipment data includes location, unique identification code, description, type, etc.; Step 4, S405 management rule monitoring module inspection equipment Data, according to the rules of the device management rule tree, check whether the device S406 meets the management rules, if not, the S412 notifies the subsystem, and ends, if yes, the S407 stores the device data to manage the device; Step 5, the S408 subsystem uploads the device Status data or smart community back-end management platform to query device status, device status Including the unique Identification code, on or off, etc., for example: subsystem A transmits the status of Reed every 60 seconds, the status value is 0, the table transmits the status of Reed off every 60 seconds, and subsystem B transmits the status of SmokeDetector every 120 seconds, the status value is 100, the table transmits the SmokeDetector open state every 120; Step 6: The S409 management rule monitoring module checks the device data, and whether the S410 meets the management rules, for example, whether the frequency is consistent, whether the status value can be recognized, etc., if not, the S412 notifies the subsystem. And ending, if yes, S411 updates the device status, and ends, and when the update frequency of the device status is too different from the rule of the device management rule tree, or the cumulative discrepancy is up to a certain number of times, the subsystem can be determined as a subsystem. abnormal.

Please refer to FIG. 5 , which is a flowchart of an alarm event monitoring method for a subsystem abnormality monitoring method applied to a smart community device and an alarm event processing method according to the present invention. It can be seen from the figure that the operation steps of the intelligent community back-end management platform to monitor whether the alarm event is abnormal is: Step 1: The S501 subsystem uploads the alarm event management rule to the smart community back-end management platform, and the management rule includes the alarm event. Type, name, notification mode, processing status representative value, alarm event level representative value, etc.; Step 2: S502 intelligent community back-end management platform management rule control module analysis management rule, after the analysis, S503 establishes an alarm event management rule tree, And stored in the management rule cache module; step 3, the S504 subsystem uploads alarm event data, the alarm event data includes location, unique identification code, description, type, processing status, source, level, etc., for example: subsystem A transmits an alarm Event, etc. Level 1 is a ReedException, and the processing status is 0. Step 4: The S505 management rule monitoring module checks the alarm event data, and the management rule monitoring module checks whether the alarm event S506 meets the management rule according to the rule of the alarm event management rule tree. If there is no, S507 notifies the subsystem and ends. If yes, the S508 management rule control module stores the alarm event data and ends. If the cumulative discrepancy is up to a certain number of times, it can be determined that the subsystem is abnormal.

The detailed description of the present invention is intended to be illustrative of a preferred embodiment of the invention, and is not intended to limit the scope of the invention. The patent scope of this case.

To sum up, this case is not only innovative in terms of technical thinking, but also has many of the above-mentioned functions that are not in the traditional methods of the past. It has fully complied with the statutory invention patent requirements of novelty and progressiveness, and applied for it according to law. Approved this invention patent application, in order to invent invention, to the sense of virtue.

100‧‧‧Smart Community Backend Management Platform

110‧‧‧Management Rule Cache Module

120‧‧‧Management Rules Monitoring Module

130‧‧‧Management Rules Control Module

200‧‧‧ subsystem

210‧‧‧Subsystem A

211‧‧‧Device Management Rules

212‧‧‧ Alarm Event Management Rules

220‧‧‧Subsystem B

221‧‧‧Device Management Rules

222‧‧‧ Alarm Event Management Rules

230‧‧‧ device

Claims (8)

A smart community device and alarm event processing system is composed of a smart community back-end management platform and subsystems, and mainly includes: a smart community back-end management platform, which has management rule data processing and provides interface and subsystem interface. And through the network and the subsystem, it further comprises a management rule cache module, a management rule monitoring module and a management rule control module; the subsystem is one or a plurality of heterogeneous subsystems, wherein the other The subsystem A and the subsystem B are included, and the other one of the subsystem A and the subsystem B has a device management rule and an alarm event management rule. For example, the device and alarm event processing system of the smart community described in claim 1 is the management rule cache module, which is a temporary management rule of the smart community management platform and the subsystem. For example, the device and alarm event processing system of the smart community described in the first application of the patent scope, wherein the management rule monitoring module is responsible for monitoring whether the device data or alarm event data uploaded by the subsystem meets the management rules. The device and alarm event processing system of the smart community as described in claim 1, wherein the management rule control module provides an interface between the HTTP or TCP/IP interface and the subsystem, and receives the management of the subsystem. The data is parsed after the rule, and the management rules after the analysis are placed in the management rule cache module. A device and alarm event processing method for a smart community, comprising: A. device management rules, which refer to integration of a smart community back-end management platform and subsystems on device management rules, and the subsystem uploads the device management rules to the smart community After the back-end management platform, that is, with the smart community The management rules of the back-end management platform are associated with each other, and a device management rule tree is established, so that the smart community back-end management platform can manage the devices of the subsystem according to the device management rules of the subsystem; B. alarm event management rules, Refers to the integration of the smart community back-end management platform and the subsystem on the alarm event management rules. After the subsystem uploads the alarm event management rules to the smart community back-end management platform, it is managed with the smart community back-end management platform. Rule association mapping, alarm event management rule tree is established, and then the smart community back-end management platform can manage the alarm events of the subsystem according to the alarm event management rules of the subsystem; C. Subsystem equipment and alarm event abnormal monitoring, refers to Use the management rules of the subsystem to monitor whether the equipment of the subsystem is abnormal. For example, in the smart community device and alarm event processing method described in claim 5, wherein the subsystem device and the alarm event are abnormally monitored, the processing steps include: Step 1: The subsystem uploads the device management rule to the smart community. The back-end management platform; step 2: the management rule control module of the smart community back-end management platform parses the management rule, and establishes a device management rule tree; step 3, the subsystem uploads device data, and the smart community back-end management platform The device management rule tree checks whether the device data conforms to the rule, and if not, notifies the subsystem, and if so, manages the device; step 4, the subsystem uploads the device status data or the smart community backend management platform to the child The system queries the device status, and the smart community backend management platform checks the device according to the device management rule tree. Whether the device status, frequency, etc. meet the rules, if not, notify the subsystem, if yes, update the device status and end; step 5, the device data of the subsystem and the device status data do not match the rules of a certain number of times, It is considered that the subsystem is abnormal. For example, in the smart community device and alarm event processing method described in claim 5, wherein the subsystem device and the alarm event abnormal monitoring refer to using the management rules of the subsystem to monitor whether the alarm event of the subsystem is abnormal. The steps include: Step 1: The subsystem uploads an alarm event management rule to the smart community back-end management platform; Step 2: After the management rule control module of the smart community back-end management platform parses the management rule, establish an alarm event management Rule tree; Step 3: The subsystem uploads an alarm, and the smart community back-end management platform checks whether the alarm event data meets the rule according to the alarm event management rule tree, and if not, notifies the subsystem, and if so, stores the alarm Event; Step 4: If the rule of the alarm event accumulates a certain number of times does not match, it is regarded as a subsystem exception. For example, the smart community back-end management platform described in claim 7 is a computer server having data storage, data processing, and the child server. The system interfaces and exchanges data.