CN108306911B - Internet of things event monitoring method and equipment - Google Patents
Internet of things event monitoring method and equipment Download PDFInfo
- Publication number
- CN108306911B CN108306911B CN201710022268.9A CN201710022268A CN108306911B CN 108306911 B CN108306911 B CN 108306911B CN 201710022268 A CN201710022268 A CN 201710022268A CN 108306911 B CN108306911 B CN 108306911B
- Authority
- CN
- China
- Prior art keywords
- data stream
- event
- monitoring
- equipment
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
Abstract
The invention discloses an event monitoring method for the Internet of things, which comprises the following steps: determining that the attribute of the received data stream is matched with the set business logic relationship; monitoring the data stream, and reporting the current event of the data stream when monitoring that the current event of the data stream meets a set event trigger strategy; wherein the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams. The invention also discloses an event monitoring device of the Internet of things.
Description
Technical Field
The invention relates to a monitoring technology in the field of Internet of things, in particular to an Internet of things event monitoring method and equipment.
Background
In the field of internet of things, a large number of types of hardware equipment are widely applied to the fields of smart homes, internet of vehicles, industrial production, smart cities, electric power, safety monitoring and the like, and the real-time monitoring and abnormal event management of the data of the hardware equipment are also one of important ways for data value mining while the corresponding data are acquired by the hardware equipment for storage and data analysis. The state data of the hardware devices in the internet of things is usually generated in real time in the form of data Stream (Stream), and in some cases even at high speed, because the data is difficult to store completely, an event management mechanism is required to filter and process the data so as to provide support for scientific decision.
In the prior art, when monitoring events of the internet of things, the prior art mainly has the following defects: the prior art scheme can only monitor a certain data stream of a single hardware device, such as a sensor or intelligent hardware, and cannot support real-time monitoring of multiple data streams of multiple devices of the same type; the method can not support monitoring of events such as single threshold, interval threshold, multiple thresholds, data fluctuation and the like of data flow, so that monitoring in the Internet of things is single and lacks flexibility. In addition, the prior art can only create events through a management interface, so that the creation of the events lacks flexibility and extensibility.
Disclosure of Invention
In view of this, embodiments of the present invention are expected to provide a method and a device for monitoring events of the internet of things, which can provide richer monitoring for the internet of things.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
the embodiment of the invention provides an event monitoring method for the Internet of things, which comprises the following steps:
determining that the attribute of the received data stream is matched with the set business logic relationship;
monitoring the data stream, and reporting the current event of the data stream when monitoring that the current event of the data stream meets a set event trigger strategy;
wherein the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams.
In the above scheme, the event trigger policy includes a correspondence between an event trigger condition and a service logic relationship;
the monitoring that the current event of the data stream meets the set event trigger strategy comprises the following steps: and monitoring the current event of the data stream and meeting the event trigger condition corresponding to the business logic relation matched with the data stream.
In the above solution, the setting of the service logic relationship includes:
setting a corresponding relation between the equipment identification and the data stream identification; alternatively, the first and second electrodes may be,
setting a range identifier as a whole network identifier; alternatively, the first and second electrodes may be,
setting an equipment identifier; alternatively, the first and second electrodes may be,
a data flow identification or group flow identification is set.
In the above scheme, the determining that the attribute of the received data stream matches the set service logic relationship includes:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
In the foregoing solution, the reporting the current event of the data stream includes:
and taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through a HyperText Transfer Protocol (HTTP) message.
In the above scheme, the method further comprises:
and when the equipment or the data stream is deleted, setting the event trigger strategy corresponding to the equipment or the data stream to be invalid.
The embodiment of the invention also provides an event monitoring device of the internet of things, which comprises: a recognition matching module and a monitoring module, wherein,
the identification matching module is used for determining that the attribute of the received data stream is matched with the set business logic relationship;
the monitoring module is used for monitoring the data stream and reporting the current event of the data stream when monitoring that the current event of the data stream meets a set event trigger strategy;
wherein the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams.
In the above scheme, the event trigger policy includes a correspondence between an event trigger condition and a service logic relationship;
the monitoring module is specifically configured to monitor a current event of the data stream and meet an event trigger condition corresponding to the service logic relationship matched with the data stream.
In the foregoing solution, the device further includes a service logic relationship setting module, where the service logic relationship setting module is configured to:
setting a corresponding relation between the equipment identification and the data stream identification; alternatively, the first and second electrodes may be,
setting a range identifier as a whole network identifier; alternatively, the first and second electrodes may be,
setting an equipment identifier; alternatively, the first and second electrodes may be,
a data flow identification or group flow identification is set.
In the foregoing solution, the identification matching module is specifically configured to:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
In the foregoing solution, the monitoring module is specifically configured to:
and taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through an HTTP message.
In the above scheme, the device further comprises a deletion module,
and the deleting module is used for setting the event trigger strategy corresponding to the equipment or the data stream to be invalid when the equipment or the data stream is deleted.
The embodiment of the invention provides an event monitoring method and equipment for the Internet of things, which comprises the steps of establishing a business logic relationship for at least one piece of equipment; the at least one device includes, but is not limited to, a sensor and/or an intelligent hardware device; creating an event trigger policy; and executing the event triggering strategy. Therefore, real-time monitoring of data streams of a plurality of devices in the Internet of things can be implemented according to the created event trigger strategy.
The embodiment of the invention can directly realize the simultaneous monitoring of a plurality of data streams of a plurality of devices of the existing Internet of things on the basis of not increasing the cost of the devices, and can support the monitoring of single digital threshold, interval threshold, multi-threshold, data fluctuation and other events in the data streams on the basis of the event triggering strategy; accurate monitoring can be achieved through the setting of the event triggering strategy without being limited in a specific network, and the method is simple and convenient to achieve, flexible and various and wider in application range; and the use of the monitored equipment is not influenced.
Drawings
Fig. 1 is a schematic view of an implementation flow of event monitoring of the internet of things in the embodiment of the present invention;
fig. 2 is a schematic diagram of a composition of an event monitoring device of the internet of things in the embodiment of the invention;
FIG. 3 is a flowchart illustrating a thermostat device management implementation according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating an implementation of management of multiple temperature/humidity sensor devices according to a second embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.
In the embodiment of the invention, the attribute of a received data stream is determined to be matched with a set service logic relationship, the data stream is monitored, and when the current event of the data stream is monitored to meet a set event trigger strategy, the current event of the data stream is reported; the business logic relationship may include: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams.
Fig. 1 is a schematic view of an implementation process of event monitoring of the internet of things in the embodiment of the present invention, and as shown in fig. 1, the implementation process of event monitoring of the internet of things in the present invention includes the following steps:
step 101: determining that the attribute of the received data stream is matched with the set business logic relationship;
wherein the business logic relationship may include: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams.
Here, the device may be various types of hardware devices such as a sensor, an intelligent hardware device, and the like; the devices involved in a business logic relationship may be of the same type or of different types.
The service logic relationship is set according to the data stream to be monitored or the device corresponding to the data stream to be monitored, and specifically, the service logic relationship may be a correspondence between a device identifier (dev _ ids) and a data stream identifier (ds _ id), so that the device to which the data stream to be monitored belongs can be clearly embodied through the correspondence; if the data streams of all the devices need to be monitored, in order to reduce the set input operation and facilitate the setting of the business logic relationship, a range identifier, such as a master, can also be directly added in the business logic relationship to be a whole network identifier, thereby indicating that the devices and the specific data streams do not need to be distinguished, and the data streams of all the devices need to be monitored without being set one by one. If all data streams under a certain device need to be monitored, namely, the device mode is specified, only the device identifier needs to be set.
The service logic relationship may also be to monitor data streams with the same characteristics in each device as needed, and since the data streams with the same characteristics in different devices may use the same data stream identifier, the service logic relationship may also specifically be to set the data stream identifier.
In addition, a plurality of data flows can also be monitored based on the same event trigger policy, so that the data flows can be bound together and identified by the set group flow identifier (ds _ uuids), and therefore, the setting of the service logic relationship can be the set group flow identifier.
The determining that the attribute of the received data stream matches the set business logic relationship includes:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
Therefore, the technical scheme of the invention can support the real-time monitoring of multiple data streams under multiple devices.
Step 102: monitoring the data stream, and monitoring that a current event of the data stream meets a set event trigger strategy;
the event trigger strategy comprises one or more event trigger conditions, and if the event trigger strategy comprises a plurality of event trigger conditions, the event trigger strategy comprises the corresponding relation between the event trigger conditions and the business logic relation. The monitoring that the current event of the data stream meets the set event trigger strategy comprises the following steps: and monitoring the current event of the data stream and meeting the event trigger condition corresponding to the business logic relation matched with the data stream.
Here, the setting of the event trigger policy may be implemented based on a RESTful API and/or a Web visualization interface.
The event trigger strategy comprises the following steps: policy name, event trigger condition, and corresponding business logic relationship. The event trigger condition comprises one of: critical condition judgment type, inout type, exp type, frezen type, change type and live type. In practical application, the type is a critical condition judgment type, and specifically, when >, <, >, or ═ is included, the triggering threshold value is a numerical value, and when the numerical value of the data stream is greater than, less than, or equal to a set numerical value for the first time, the event triggering condition is satisfied; when the type is inout, the triggering threshold is set as a closed interval, and the event triggering condition is met when the value of the data stream enters or leaves the closed interval for the first time; when the type is exp, a conditional expression indicating that the trigger threshold is set to a character string type, and when the trigger threshold satisfies a plurality of conditions, an event trigger condition is satisfied; when the type is change, the trigger threshold value is not required to be transmitted, and when the uploaded value is changed, the event trigger condition is met; when the type is a FROZEN, the triggering threshold value is a numerical value, the event triggering condition is met when the data are not reported within a specified number of seconds, and meanwhile, the data flow meeting the event triggering condition enters a FROZEN state; when the type is live, it indicates that the trigger threshold is not to be transmitted, and when the data stream meeting the event trigger condition receives the reported data point in the frozen state, the event trigger condition is met.
The event-triggered policy further comprises: reporting a strategy; the reporting strategy comprises the following steps: the HTTP message content comprises an equipment identifier and a data stream identifier, and is used for identifying the data stream which currently meets the event trigger strategy; also included is a current event of the data stream being monitored. If different events are processed by different event processing servers, the reporting strategy also comprises the address of the event processing server.
As can be seen from the above description, the technical solution described in the present invention is flexible and various in monitoring data streams.
Step 103: and reporting the current event of the data stream.
Reporting a current event of the data stream, including: taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through an HTTP message;
when the reporting policy in the event triggering policy includes an address of an event processing server, the sending to the event processing server via the HTTP message includes: and sending the information to an event processing server corresponding to the address of the event processing server through an HTTP message.
In practical applications, when a device or a data stream is deleted, an event trigger policy corresponding to the device or the data stream will fail, and therefore, the method further includes: and when the equipment or the data stream is deleted, setting the event trigger strategy corresponding to the equipment or the data stream to be invalid.
The above processing can be completed by a server in the internet of things.
Fig. 2 is a schematic diagram of a composition of an event monitoring device of the internet of things in the embodiment of the present invention, and as shown in fig. 2, the composition of the event monitoring device of the internet of things in the embodiment of the present invention includes the following modules: a matching module 201, a monitoring module 202 are identified, wherein,
an identification matching module 201, configured to determine that an attribute of a received data stream matches a set service logic relationship;
a monitoring module 202, configured to monitor the data stream, and report a current event of the data stream when it is monitored that the current event of the data stream meets a set event trigger policy;
wherein the business logic relationship comprises: the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or multiple data streams.
Here, the device may be various types of hardware devices such as a sensor, an intelligent hardware device, and the like; the devices involved in a business logic relationship may be of the same type or of different types.
In practical application, the device further includes a service logic relationship setting module, where the service logic relationship setting module is configured to:
setting a corresponding relation between the equipment identification and the data stream identification; alternatively, the first and second electrodes may be,
setting a range identifier as a whole network identifier; alternatively, the first and second electrodes may be,
setting an equipment identifier; alternatively, the first and second electrodes may be,
a data flow identification or group flow identification is set.
The service logic relationship is set by the service logic relationship setting module according to the data stream to be monitored or the device corresponding to the data stream to be monitored, and specifically, the service logic relationship setting module sets the corresponding relationship between the device identifier (dev _ ids) and the data stream identifier (ds _ id), so that the device to which the data stream to be monitored by the monitoring module 202 belongs and the user to which the device belongs can be clearly embodied through the corresponding relationship; if the monitoring module 202 is required to monitor the data streams of all the devices, in order to reduce the set input operation and facilitate the setting of the business logic relationship, the business logic relationship setting module may also directly add a range identifier, such as a master, to the business logic relationship, thereby indicating that the devices and the specific data streams do not need to be distinguished, and the data streams of all the devices need to be monitored without being set one by one. If all data streams under a certain device need to be monitored, namely, the device mode is specified, the service logic relationship setting module only needs to set the device identifier.
The service logic relationship may also be that the monitoring module 202 monitors data streams with the same characteristics in each device as needed, and since the data streams with the same characteristics in different devices may use the same data stream identifier, the service logic relationship setting module may specifically set the data stream identifier.
In addition, since the monitoring module 202 may also monitor a plurality of data flows based on the same event trigger policy, these data flows may be bound together and identified by the group flow identifier (ds _ uuids) set by the service logical relationship setting module, and thus, the setting of the service logical relationship may be the group flow identifier set by the service logical relationship setting module.
The identification matching module 201 is specifically configured to:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
Therefore, the technical scheme of the invention can support the real-time monitoring of multiple data streams under multiple devices.
In actual use, the event trigger policy contains one or more event trigger conditions, and if the event trigger policy contains a plurality of event trigger conditions, the event trigger policy includes a correspondence between the event trigger conditions and the business logic relationship. The monitoring module 202 is specifically configured to: and monitoring the current event of the data stream and meeting the event trigger condition corresponding to the business logic relation matched with the data stream.
Here, the setting of the event trigger policy may be implemented based on a RESTful API and/or a Web visualization interface.
The event trigger strategy comprises the following steps: policy name, event trigger condition, and corresponding business logic relationship. The event trigger condition comprises one of: critical condition judgment type, inout type, exp type, frezen type, change type and live type. In practical application, the type is a critical condition judgment type, and specifically, when >, <, >, or ═ is included, it indicates that the trigger threshold is a numerical value, and the event trigger condition is satisfied when the numerical value of the data stream monitored by the monitoring module 202 is greater than, less than, or equal to the set numerical value for the first time; when the type is inout, it indicates that the trigger threshold is set to be a closed interval, and when the value of the data stream monitored by the monitoring module 202 first enters or leaves the closed interval, the event trigger condition is satisfied; when the type is exp, a conditional expression indicating that the trigger threshold is set to a character string type, and when the trigger threshold satisfies a plurality of conditions, an event trigger condition is satisfied; when the type is change, the trigger threshold value is not required to be transmitted, and when the uploaded value is changed, the event trigger condition is met; when the type is a FROZEN, the triggering threshold value is a numerical value, the event triggering condition is met when the data are not reported within a specified number of seconds, and meanwhile, the data flow meeting the event triggering condition enters a FROZEN state; when the type is live, it indicates that the trigger threshold is not to be transmitted, and when the data stream meeting the event trigger condition receives the reported data point in the frozen state, the event trigger condition is met.
The event-triggered policy further comprises: the monitoring module 202 reports a policy; the reporting of the policy by the monitoring module 202 includes: the HTTP message content comprises an equipment identifier and a data stream identifier, and is used for identifying the data stream which currently meets the event trigger strategy; but also the current events of the data stream monitored by the monitoring module 202. If different events are processed by different event processing servers, the reporting policy of the monitoring module 202 further includes an event processing server address.
As can be seen from the above description, the technical solution described in the present invention is flexible and various in monitoring data streams.
In practical applications, the monitoring module 202 is specifically configured to: taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through a hyper HTTP message;
when the reporting policy in the event trigger policy includes an address of an event processing server, the monitoring module 202 is specifically configured to: and sending the information to an event processing server corresponding to the address of the event processing server through an HTTP message.
In practical application, the device further comprises a deletion module, and the deletion module is used for setting an event trigger policy corresponding to the device or the data stream to be invalid when the device or the data stream is deleted; specifically, when the deletion module deletes a device or a data stream, an event trigger policy corresponding to the device or the data stream will fail.
The above processing can be completed by a server in the internet of things.
Fig. 3 is a flowchart illustrating an implementation process of thermostat device management according to a first embodiment of the present invention, and as shown in fig. 3, the implementation process of the thermostat device management according to the first embodiment of the present invention includes the following steps:
step 301: setting a business logic relationship of the thermostat;
here, the constant temperature device has established a TCP connection, and can upload data streams through GPRS \ WIFI \ wired network and other modes. Setting a business logic relationship for the thermostat includes: the method comprises the following steps that A, a thermostat name A and an energy consumption data stream a corresponding to the thermostat A are obtained;
step 302: setting an event trigger strategy of the thermostat;
here, the event triggering strategy of the thermostat is set through a Web visual interface: when the energy consumption value is larger than 50, an alarm is triggered. The specific setting content of the event trigger policy comprises the following steps: policy name — event 1; control Range-A; data stream name-a; triggering condition-current energy consumption of selected energy consumption data stream > 50; URL Address-event processing Server Address, http:// 192.168.21.145/;
step 303: monitoring a data stream of the thermostat;
and monitoring the energy consumption data stream a of the thermostat A according to a set event triggering strategy of the thermostat A, determining that an abnormal event occurs when the energy consumption value of the energy consumption data stream a is greater than 50, triggering an HTTP message, and sending the content of the abnormal event to an event processing server with an address of HTTP://192.168.21.145 through the HTTP message.
Fig. 4 is a flowchart illustrating an implementation process of managing a plurality of temperature and humidity sensor devices according to a second embodiment of the present invention, where as shown in fig. 4, the implementation process of managing a plurality of temperature and humidity sensor devices according to the second embodiment of the present invention includes the following steps:
step 401: setting a business logic relation of a plurality of temperature and humidity sensors;
here, the temperature and humidity sensors arranged at different places are connected with each other through a TCP, and data streams can be uploaded through GPRS \ WIFI \ wired network and other modes. Setting a business logic relationship for a plurality of temperature and humidity sensors comprises: the method comprises the following steps that three temperature and humidity sensors are set, wherein the names of devices are respectively A, B, C, the data of the three temperature and humidity sensors relate to temperature and humidity, temperature data streams are set for the devices respectively, and humidity data streams are humidity;
step 402: setting event trigger strategies of a plurality of temperature and humidity sensors;
here, according to the HTTP message format, directly editing commands by adopting a RESTful API method to complete setting of event trigger strategies of three temperature sensors, wherein the editing commands support a JSON format;
wherein the event triggering policy may be any one of the following examples:
1. monitoring a single data stream, monitoring the value change of the humidity data stream of the equipment A, and sending an alarm when the humidity value is less than or equal to 33;
2. monitoring data of multiple data streams under one device, monitoring a temperature data stream and a humidity data stream of a device B, and triggering an alarm when a temperature value is greater than 30 and a humidity value is less than 33;
3. monitoring data with the same name for multiple device data streams, the device A, B, C has the same temperature data stream: temperature, which monitors the temperature data flow of the device A, B, C at the same time, and triggers an alarm when the temperature value is greater than 30;
step 403: monitoring data streams of a plurality of temperature and humidity sensors;
here, the temperature data stream of the temperature sensor A, B, C is monitored according to the set event trigger policy of the temperature sensor A, B, C, and when the monitored value satisfies the trigger condition, transmission of an HTTP message is triggered, and the content of the abnormal event is transmitted to the event processing server addressed to HTTP:// 192.168.21.145/via the HTTP message.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (10)
1. An event monitoring method for the Internet of things is characterized by comprising the following steps:
determining that the attribute of the received data stream is matched with the set business logic relationship;
monitoring the data stream, and reporting the current event of the data stream when monitoring that the current event of the data stream meets a set event trigger strategy;
wherein the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or the data stream is multiple;
the event trigger strategy comprises a corresponding relation between an event trigger condition and a business logic relation;
the monitoring that the current event of the data stream meets the set event trigger strategy comprises the following steps: and monitoring that the current event of the data stream meets an event trigger condition corresponding to the business logic relation matched with the data stream.
2. The method for monitoring events of the internet of things as claimed in claim 1, wherein the setting of the business logic relationship comprises:
setting a corresponding relation between the equipment identification and the data stream identification; alternatively, the first and second electrodes may be,
setting a range identifier as a whole network identifier; alternatively, the first and second electrodes may be,
setting an equipment identifier; alternatively, the first and second electrodes may be,
a data flow identification or group flow identification is set.
3. The method for monitoring events of the internet of things as claimed in claim 2, wherein the determining that the attributes of the received data stream match the set business logic relationship comprises:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
4. The method for monitoring events of the internet of things as claimed in claim 1, wherein the reporting the current event of the data stream comprises:
and taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through a hypertext transfer protocol (HTTP) message.
5. The Internet of things event monitoring method according to any one of claims 1 to 4, further comprising:
and when the equipment or the data stream is deleted, setting the event trigger strategy corresponding to the equipment or the data stream to be invalid.
6. An event monitoring device of the internet of things, comprising: a recognition matching module and a monitoring module, wherein,
the identification matching module is used for determining that the attribute of the received data stream is matched with the set business logic relationship;
the monitoring module is used for monitoring the data stream and reporting the current event of the data stream when monitoring that the current event of the data stream meets a set event trigger strategy;
wherein the business logic relationship comprises: a plurality of data streams corresponding to one device; or the number of the devices is multiple, and the number of the data streams corresponding to each device is at least one; or the data stream is multiple;
the event trigger strategy comprises a corresponding relation between an event trigger condition and a business logic relation;
the monitoring module is specifically configured to monitor a current event of the data stream and meet an event trigger condition corresponding to the service logic relationship matched with the data stream.
7. The apparatus according to claim 6, wherein the apparatus further comprises a business logic relationship setting module, and the business logic relationship setting module is configured to:
setting a corresponding relation between the equipment identification and the data stream identification; alternatively, the first and second electrodes may be,
setting a range identifier as a whole network identifier; alternatively, the first and second electrodes may be,
setting an equipment identifier; alternatively, the first and second electrodes may be,
a data flow identification or group flow identification is set.
8. The device of claim 6, wherein the identification matching module is specifically configured to:
determining equipment corresponding to the received data stream, and determining that the equipment identifier of the equipment and the data stream identifier of the data stream meet the corresponding relation between the equipment identifier and the data stream identifier in the service logic relation; alternatively, the first and second electrodes may be,
and determining the data flow identification or the group flow identification of the received data flow, and determining that the data flow identification or the group flow identification is consistent with the data flow identification or the group flow identification in the service logic relationship.
9. The device of claim 6, wherein the monitoring module is specifically configured to:
and taking the current event of the data stream as an abnormal event, and sending the abnormal event to an event processing server through a hypertext transfer protocol (HTTP) message.
10. The apparatus according to any one of claims 6-9, further comprising a deletion module,
and the deleting module is used for setting the event trigger strategy corresponding to the equipment or the data stream to be invalid when the equipment or the data stream is deleted.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710022268.9A CN108306911B (en) | 2017-01-12 | 2017-01-12 | Internet of things event monitoring method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710022268.9A CN108306911B (en) | 2017-01-12 | 2017-01-12 | Internet of things event monitoring method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108306911A CN108306911A (en) | 2018-07-20 |
| CN108306911B true CN108306911B (en) | 2020-12-29 |
Family
ID=62871845
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710022268.9A Active CN108306911B (en) | 2017-01-12 | 2017-01-12 | Internet of things event monitoring method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108306911B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10380348B2 (en) | 2016-11-21 | 2019-08-13 | ZingBox, Inc. | IoT device risk assessment |
| US11070568B2 (en) | 2017-09-27 | 2021-07-20 | Palo Alto Networks, Inc. | IoT device management visualization |
| EP3808052A4 (en) | 2018-06-18 | 2022-03-02 | Palo Alto Networks, Inc. | Pattern match-based detection in iot security |
| EP3847571A4 (en) * | 2018-09-04 | 2022-06-01 | Palo Alto Networks, Inc. | Iot application learning |
| US11451571B2 (en) | 2018-12-12 | 2022-09-20 | Palo Alto Networks, Inc. | IoT device risk assessment and scoring |
| US11689573B2 (en) | 2018-12-31 | 2023-06-27 | Palo Alto Networks, Inc. | Multi-layered policy management |
| US11115799B1 (en) | 2020-06-01 | 2021-09-07 | Palo Alto Networks, Inc. | IoT device discovery and identification |
| CN113114985B (en) * | 2021-03-31 | 2022-07-26 | 联想(北京)有限公司 | Information processing method and information processing device |
| CN116527446B (en) * | 2023-02-01 | 2023-09-08 | 合沃物联技术（南京）有限公司 | Edge rule engine method based on industrial Internet of things gateway |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102006204A (en) * | 2010-12-09 | 2011-04-06 | 广东高新兴通信股份有限公司 | Distributed resolution system and method for monitoring data stream in real time |
| CN102571429A (en) * | 2012-01-05 | 2012-07-11 | 重庆市电力公司电力科学研究院 | Object-oriented intelligent power distribution communication business analyzing method and corresponding device |
| CN105706469A (en) * | 2013-09-13 | 2016-06-22 | 沃达方Ip许可有限公司 | Managing machine to machine devices |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102264056B (en) * | 2010-05-28 | 2014-03-05 | 华为技术有限公司 | Strategy control method, system and relevant device |
-
2017
- 2017-01-12 CN CN201710022268.9A patent/CN108306911B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102006204A (en) * | 2010-12-09 | 2011-04-06 | 广东高新兴通信股份有限公司 | Distributed resolution system and method for monitoring data stream in real time |
| CN102571429A (en) * | 2012-01-05 | 2012-07-11 | 重庆市电力公司电力科学研究院 | Object-oriented intelligent power distribution communication business analyzing method and corresponding device |
| CN105706469A (en) * | 2013-09-13 | 2016-06-22 | 沃达方Ip许可有限公司 | Managing machine to machine devices |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108306911A (en) | 2018-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108306911B (en) | Internet of things event monitoring method and equipment | |
| US20200229033A1 (en) | Method and system for group communication, group server, and group member device | |
| CN107864063B (en) | Abnormity monitoring method and device and electronic equipment | |
| KR20200033090A (en) | An apparatus for network monitoring and method thereof, and system | |
| KR102076862B1 (en) | Network performance indicator visualization method and apparatus, and system | |
| CN104731690B (en) | Adaptive metrology collection, storage and warning threshold | |
| WO2015141220A1 (en) | Information processing device and monitoring method | |
| US20160142493A1 (en) | Sensor data collection system | |
| CN103152352A (en) | Perfect information security and forensics monitoring method and system based on cloud computing environment | |
| DE112013007104B4 (en) | Monitoring system, building management device, monitoring method and program | |
| KR20190088342A (en) | Network performance diagnosis method and apparatus, and system | |
| CN101094389B (en) | Method for downloading video, video server, and monitoring center system | |
| CN105471932A (en) | Front-end application monitoring method, front-end application and front-end application monitoring system | |
| CN106936621A (en) | A kind of work order storm control method, apparatus and system | |
| CN103440190A (en) | Equipment failure warning method, device and CIM system | |
| CN104320285A (en) | Website running status monitoring method and device | |
| JP4932634B2 (en) | Wide area data linkage system | |
| WO2024060657A1 (en) | Method and apparatus for monitoring whole-house air environment, and device and storage medium | |
| CN108696393A (en) | A kind of network traffic analysis system based on big data | |
| US11556120B2 (en) | Systems and methods for monitoring performance of a building management system via log streams | |
| WO2023147731A1 (en) | Abnormal data processing method and apparatus, and electronic device | |
| WO2015025379A1 (en) | Monitoring device, monitoring method, and recording medium | |
| CN116506300A (en) | Website traffic data statistics method and system | |
| JP2004062276A (en) | Device and method for collecting and distributing equipment information, and program and recording medium having the program recorded thereon | |
| CN105607983A (en) | Data exception monitoring method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 401336 No.8 Yuma Road, Chayuan New District, Nan'an District, Chongqing Patentee after: CHINA MOBILE IOT Co.,Ltd. Patentee after: CHINA MOBILE COMMUNICATIONS GROUP Co.,Ltd. Address before: 401336 No.8 Yuma Road, Chayuan New District, Nan'an District, Chongqing Patentee before: CHINA MOBILE IOT Co.,Ltd. Patentee before: China Mobile Communications Corp. |