WO2021052289A1 - 事件通知方法、系统、服务器设备、计算机存储介质 - Google Patents

事件通知方法、系统、服务器设备、计算机存储介质 Download PDF

Info

Publication number
WO2021052289A1
WO2021052289A1 PCT/CN2020/115074 CN2020115074W WO2021052289A1 WO 2021052289 A1 WO2021052289 A1 WO 2021052289A1 CN 2020115074 W CN2020115074 W CN 2020115074W WO 2021052289 A1 WO2021052289 A1 WO 2021052289A1
Authority
WO
WIPO (PCT)
Prior art keywords
event notification
monitoring
monitoring data
rule
time point
Prior art date
Application number
PCT/CN2020/115074
Other languages
English (en)
French (fr)
Inventor
赵君杰
苏京
王新安
陈少蓓
张乾
赵砚秋
Original Assignee
京东方科技集团股份有限公司
北京京东方技术开发有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司, 北京京东方技术开发有限公司 filed Critical 京东方科技集团股份有限公司
Priority to EP20866007.6A priority Critical patent/EP4033722A4/en
Priority to JP2022516700A priority patent/JP2022547726A/ja
Priority to US17/642,740 priority patent/US11909839B2/en
Priority to KR1020227012343A priority patent/KR20220059543A/ko
Publication of WO2021052289A1 publication Critical patent/WO2021052289A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • 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/55—Push-based network services
    • C—CHEMISTRY; METALLURGY
    • C02—TREATMENT OF WATER, WASTE WATER, SEWAGE, OR SLUDGE
    • C02F—TREATMENT OF WATER, WASTE WATER, SEWAGE, OR SLUDGE
    • C02F1/00—Treatment of water, waste water, or sewage
    • C02F1/008—Control or steering systems not provided for elsewhere in subclass C02F
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • 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
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network

Definitions

  • the present disclosure relates to the field of Internet of Things, and in particular to an event notification method, system, server device, and computer storage medium.
  • the Internet of Things uses communication technologies such as local networks or the Internet to connect sensors, controllers, machines, people, and objects in new ways to form a connection between people and things, and things and things.
  • communication technologies such as local networks or the Internet to connect sensors, controllers, machines, people, and objects in new ways to form a connection between people and things, and things and things.
  • Terminal devices connected to the Internet of Things can obtain data or event notifications by sending a subscription request to the server device.
  • the IoT platform can send data or event notifications to the notifier in the subscription request.
  • an event notification method including: receiving a subscription request from a subscriber, the subscription request including at least one receiver for receiving event notification; within a monitoring time interval, determining whether Satisfying the continuous event notification rule; and in the case of satisfying the continuous event notification rule, sending the event notification of the subscription request to the at least one recipient.
  • the event notification method further includes: obtaining at least one piece of monitoring data within the monitoring time interval, wherein determining whether the continuous event notification rule is satisfied includes: determining whether the at least one piece of monitoring data is Whether each monitoring data meets the event notification rules.
  • the event notification method further includes: obtaining at least one piece of monitoring data within the monitoring time interval, wherein determining whether the continuous event notification rule is satisfied includes: For each monitoring data, determine whether the event notification rule is met; determine the number of monitoring data meeting the event notification rule; if the number is not less than the count threshold, determine whether the continuous event notification rule is satisfied, wherein the count threshold is based on The number of monitoring data received within the monitoring time interval is determined.
  • the event notification method further includes: obtaining at least one piece of monitoring data within the monitoring time interval, wherein determining whether the continuous event notification rule is satisfied includes: For each monitoring data, determine whether the event notification rule is met; determine the length of time to satisfy the event notification rule based on the time interval of the monitoring data that meets the event notification rule; when the ratio of the time length to the monitoring time interval is not less than In the case of a time threshold, it is determined that the continuous event notification rule is satisfied, wherein the time threshold is less than or equal to 1.
  • the event notification rule includes any one of the following: the monitoring data is greater than a monitoring threshold; the monitoring data is equal to the monitoring threshold; the monitoring data is less than the monitoring threshold; the monitoring data is not Less than the monitoring threshold; and the monitoring data is not greater than the monitoring threshold. value.
  • the event notification method further includes: acquiring at least one piece of monitoring data within the monitoring time interval, wherein determining whether the continuous event notification rule is satisfied includes: in a case where the event notification rule is determined to be satisfied , Determine whether the monitoring data rule is satisfied, and obtain a monitoring result; based on the monitoring result, determine whether the continuous event notification rule is satisfied.
  • the event notification rule includes at least one of the following: update the attributes of the subscribed resource; create the subscribed resource subresource; delete the subscribed resource subresource; obtain the subscribed container resource Content instance sub-resource; receiving an operation request from a certain requester; receiving a request for a certain type of operation, the monitoring data rule includes any one of the following: the monitoring data is greater than the monitoring threshold; the monitoring data is equal to the monitoring threshold The monitoring data is less than the monitoring threshold; the monitoring data is not less than the monitoring threshold; and the monitoring data is not greater than the monitoring threshold.
  • determining whether the monitoring data rule is satisfied and obtaining the monitoring result includes: for each monitoring data of the at least one monitoring data, determining whether the monitoring data meets the monitoring data rule, wherein, in the monitoring data When the monitoring data rules are met, the monitoring results that meet the monitoring data rules are obtained; when the monitoring data does not meet the monitoring data rules, the monitoring results that do not meet the monitoring data rules are obtained.
  • determining whether the continuous event notification rule is satisfied includes: determining the number of monitoring results that meet the monitoring data rule; in the case that the number of monitoring results that meets the monitoring data rule is not less than the count threshold, determining that the continuous event is satisfied The notification rule, wherein the counting threshold is determined based on the number of monitoring data received within the monitoring time interval.
  • determining whether the continuous event notification rule is satisfied includes: determining the length of time corresponding to the monitoring result satisfying the monitoring data rule; when the ratio of the length of time to the monitoring time interval is not less than a time threshold , It is determined that the continuous event notification rule is satisfied, wherein the time threshold is less than or equal to 1.
  • it further includes: a start time point and an end time point of a monitoring time interval, wherein the time point that satisfies the event notification rule is determined as the start time point; based on the monitoring time interval and the determination The start time point of determines the end time point.
  • it further includes: a start time point and an end time point of a monitoring time interval, wherein the time point that satisfies the event notification rule is determined as the end time point; based on the monitoring time interval and the determined The end time point determines the start time point.
  • it further includes the start time point and the end time point of the monitoring time interval, wherein the time point meeting the event notification rule is determined as the intermediate time point; based on the monitoring time interval and the determined intermediate time point The start time point and the end time point are determined, wherein the intermediate time point is located between the start time point and the end time point.
  • the subscription request further includes the monitoring time interval
  • the event notification method further includes: creating a subscription resource
  • the subscription resource includes the following attributes: a monitoring time interval attribute for determining The monitoring time interval; the continuous event notification rule attribute is used to determine whether to send an event notification to the at least one recipient; the event notification list attribute is used to store the address information of the at least one recipient.
  • a server device including a transceiver and a processor, wherein the transceiver is configured to receive a subscription request from a subscribing device, and the subscription request includes information for receiving event notifications.
  • the processor is configured to: within the monitoring time interval, determine whether the continuous event notification rule is met; the transceiver is further configured to, in the case where the continuous event notification rule is met, send the notification to the at least A receiver sends an event notification of the subscription request.
  • an event notification system including: a subscription device configured to send a subscription request to a server device, the subscription request including at least one recipient for receiving event notifications; the server device, It is configured to: receive a subscription request from a subscribing device; obtain at least one monitoring data; within the monitoring time interval, determine whether the continuous event notification rule is satisfied; and in the case where the continuous event notification rule is satisfied, to the at least one receiving Sending the event notification of the subscription request; and a monitoring device configured to send monitoring data to the server device.
  • a computer storage medium in which computer-readable codes are stored, and the computer-readable codes perform the above-mentioned event notification method when executed by one or more processors.
  • Figure 1A shows a flow chart of the instant event notification processing
  • Figure 1B shows a time flow chart of instant event notification
  • Fig. 2 shows a flowchart of an event notification method according to an embodiment of the present disclosure
  • FIG. 3 shows a time flow chart of determining that each monitoring data meets the event notification rule according to an embodiment of the present disclosure
  • FIG. 4 shows a time flow chart of determining the number of monitoring data satisfying the event notification rule according to an embodiment of the present disclosure
  • FIG. 5 shows a time flow chart for determining the length of time for satisfying an event notification rule according to an embodiment of the present disclosure
  • FIG. 6 shows a time flow chart for determining the number of monitoring results that satisfy the monitoring data rule according to an embodiment of the present disclosure
  • FIG. 7 shows a time flow chart for determining the length of time corresponding to the monitoring result that satisfies the monitoring data rule according to an embodiment of the present disclosure
  • FIG. 8 shows a time flow chart for determining a start time point and an end time point according to an embodiment of the present disclosure
  • FIG. 9 shows a time flow chart of determining a start time point and an end time point according to an embodiment of the present disclosure
  • FIG. 10 shows a time flow chart for determining a start time point and an end time point according to an embodiment of the present disclosure
  • FIG. 11 shows a schematic diagram of a resource structure of a subscription resource according to an embodiment of the present disclosure
  • FIG. 12A shows a schematic diagram of a system according to an embodiment of the present disclosure
  • FIG. 12B shows a processing flowchart of continuous event notification according to an embodiment of the present disclosure
  • FIG. 13 shows a schematic block diagram of a server device according to an embodiment of the present disclosure
  • Fig. 14 shows a schematic block diagram of an event notification system according to an embodiment of the present disclosure.
  • the Internet of Things can include the Internet and all resources on the Internet, and is compatible with Internet applications.
  • various new application fields such as smart home, smart transportation, smart health, and smart water quality monitoring have emerged.
  • the terminal equipment may be, for example, smoke alarms, fire alarms, various household appliances, water quality monitoring equipment, and various types of sensing equipment, execution equipment, and the like.
  • the IoT platform may be implemented as a general service entity, or called a server device, for example, and the terminal device may be connected to the server device by sending registration information to the server device, and the server device pair is connected to it. Terminal equipment for management.
  • the terminal device connected to the server device can also perform operations such as data transmission and information interaction with the server device.
  • the terminal devices described in this article may be various terminal devices in the field of the Internet of Things, or may also be software modules in the device.
  • Some terminal devices can subscribe to information, data, etc. from other terminal devices (for example, as a monitoring device) by sending a subscription request to the server device, and the subscription device can also request information from the server device.
  • Data, operations, etc. are not restricted here.
  • the subscription request may include a subscription condition, so that the server device sends an event notification when the subscription condition is determined to be satisfied (for example, a smoke alarm generates an alarm).
  • the subscription condition may also be referred to as an event notification rule. In other words, when the server device determines that the event notification rule is satisfied, an event notification is sent.
  • the subscription device and the monitoring device can connect to the server device by sending a registration request to the server device.
  • the subscription device may send a subscription request to the server device, and the subscription request may include event notification rules.
  • the monitoring device may specifically be a water quality monitoring device, and the event notification rule may be that the water quality data monitored by the water quality monitoring device is greater than a preset threshold.
  • the water quality monitoring device can continuously send the detected water quality data to the server device, and the server device can determine whether the received water quality data meets the event notification rules. When it is determined that the water quality data is greater than the preset threshold (that is, the event notification rules are met) In this case, the server device sends an event notification.
  • FIG 1B shows the time flow chart of the instant event notification.
  • the server device receives the water quality data of the monitoring device, it immediately determines whether the water quality data meets the event notification rules, and determines whether the event notification rules are met. After that, an event notification is sent. Therefore, for application scenarios that require continuous monitoring of water quality data such as water quality monitoring, the monitoring device continuously sends data to the server device, and the server device continuously sends event notifications to the subscribing device.
  • the subscription device needs to monitor the water quality data within a period of time, and make judgments based on the water quality data within the period of time. For example, in the above example, the subscribing device is notified when the water quality data exceeds a preset threshold.
  • the reasons that cause the water quality data to exceed the preset threshold may include, for example, household sewage discharge and enterprise sewage discharge. The above two reasons may cause the water quality data to exceed the preset threshold, or the water quality exceeds the standard.
  • the time for household sewage discharge is shorter, and the enterprise sewage discharge time is longer, and the subscription device may only hope to strengthen the governance of enterprise sewage discharge.
  • the subscription device will continue to receive event notifications from the server device, and based on the above notifications, determine whether it is household sewage discharge or corporate sewage discharge. For example, if the water quality data continues to exceed the standard during the monitoring period, that is, the water quality data continues If it is greater than the preset threshold, it is confirmed that the water quality exceeding the standard is caused by the enterprise's sewage discharge, and the water pollution incident will be handled.
  • the subscription device monitors continuous data changes, and it needs to continuously receive event notifications, which increases the communication load between devices and may also cause communication congestion.
  • the monitoring of continuous data changes performed by the subscription device will also increase the requirements for the processing capabilities of the subscription device.
  • the continuous events can be continuous data changes or continuous state changes, for example, water quality exceeding the standard for 10 minutes, air pollution exceeding the standard for 10 minutes, noise The pollution lasts for more than 20 minutes, the faucet keeps on for 5 minutes, the door keeps on for more than 5 minutes, etc.
  • the present disclosure provides an event notification method.
  • a server device implements continuous event monitoring. When it is determined that the received data meets the continuous event notification rule, the event notification is sent to the subscription device, which can improve the processing efficiency of the Internet of Things system and reduce The requirement for the processing capacity of the subscription device can also avoid the communication load and communication congestion between the devices, and reduce the number of event notifications.
  • FIG. 2 shows a flowchart of an event notification method according to an embodiment of the present disclosure.
  • the event notification method shown in FIG. 2 may be executed by a server device in the field of Internet of Things.
  • a subscription request from a subscriber is received, and the subscription request includes at least one receiver for receiving event notifications.
  • the subscriber may be a terminal device connected to the server device, or an application connected to the server. For example, when certain data is needed, the subscriber device may send a subscription request to the server device.
  • the subscription request may include subscribed data, events, or operations.
  • the subscriber may be one or multiple, that is, multiple subscribers may send a subscription request to the server device.
  • the recipient may be a receiving device for receiving event notifications, or a receiving application for receiving event notifications.
  • After the server device receives the subscription request it will obtain the list information of all recipients, and it may also be based on the type of recipient, The recipients are grouped by level, content of the subscription request, etc., so as to send event notifications more accurately.
  • the subscriber and receiver can be the same device or application, or different devices or applications.
  • the subscription device 1 may send a subscription request to the server device.
  • the subscription request includes the receiving device 1, the receiving device 2, and the subscription device 1 as the receiver, for receiving event notifications when the subscription conditions are met. .
  • step S102 it is determined whether the continuous event notification rule is satisfied within the monitoring time interval.
  • the monitoring time interval may be a continuous period of time, such as 1 hour, and the time length of the monitoring time interval may be set according to specific application requirements. The steps to determine whether the continuous event notification rule is met will be described in detail below.
  • step S103 if the continuous event notification rule is satisfied, the event notification of the subscription request is sent to the at least one recipient.
  • the server device may send event notifications to the receiving device 1, the receiving device 2, and the subscribing device 1, so as to realize the monitoring of the continuous event.
  • the event notification method may further include: acquiring at least one monitoring data within the monitoring time interval.
  • the monitoring device may be a water quality monitoring device, which may periodically send water quality data to the server device as the monitoring data.
  • the water quality monitoring device sends the monitored water quality data to the server device every 10 minutes. Therefore, in the case where the above-mentioned monitoring time interval is 1 hour, the server device can receive 6 water quality data from the water quality monitoring device within the monitoring time interval.
  • determining whether the continuous event notification rule is satisfied may include: determining whether each of the at least one monitoring data satisfies the event notification rule.
  • the event notification rule may include any one of the following: the monitoring data is greater than the monitoring threshold; the monitoring data is equal to the monitoring threshold; the monitoring data is less than the monitoring threshold; the monitoring data is not less than the monitoring threshold; and the The monitoring data is not greater than the monitoring threshold.
  • the event notification rule can also be set according to actual application requirements, which is not limited here.
  • Fig. 3 shows a time flow chart of determining that each monitoring data satisfies the event notification rule according to an embodiment of the present disclosure.
  • the monitoring time interval may be a time period from t1 to t2, for example, 1 hour.
  • the server device receives 6 water quality data from the water quality monitoring device. Determining whether the continuous event notification rule is met may include: determining that the six received water quality data meet the event notification rule. In other words, when the server device determines that each of the 6 received water quality data meets the event notification rule (such as greater than the monitoring threshold), it determines that the continuous event notification rule is satisfied, and then can The receiver sends event notifications.
  • determining whether the continuous event notification rule is satisfied may include: for each monitoring data in the at least one monitoring data, determining whether the event notification rule is satisfied; determining the number of monitoring data satisfying the event notification rule; In the case that the number is not less than the counting threshold, it is determined that the continuous event notification rule is satisfied.
  • the counting threshold may be determined based on the number of monitoring data received within the monitoring time interval. Exemplarily, when the number of monitoring data received in the monitoring time interval is 6, the counting threshold can be set to 5, 4, or 3, or any value from 1-6, different applications The scene can match different values or the same value.
  • FIG. 4 shows a time flow chart for determining the number of monitoring data that meets the event notification rule according to an embodiment of the present disclosure.
  • the server device receives 6 water quality data from the water quality monitoring device, and judges each water quality data to determine whether it meets the event notification rules, for example , Whether it is greater than the monitoring threshold, and determine the number of water quality data (ie, monitoring data) that meet the event notification rule, for example, it can be 5. Since the number is not less than the counting threshold of 5, it is determined that the continuous event notification rule is satisfied, and then an event notification can be sent to the receiver.
  • the event notification may be a message sent by a server device to one or more recipients, and the message may be associated with the subscription request.
  • the recipient may determine that the continuous event notification rule in the subscription request is satisfied based on receiving the message, for example, within the monitoring time interval, the water quality data continuously exceeds the monitoring threshold. Then, the recipient can perform further processing operations, such as finding the source of water pollution and water purification treatment.
  • determining whether the continuous event notification rule is satisfied may include: for each of the at least one monitoring data, determining whether the event notification rule is satisfied; based on the monitoring data satisfying the event notification rule
  • the time interval is used to determine the length of time that the event notification rule is met; when the ratio of the time length to the monitoring time interval is not less than a time threshold, it is determined that the continuous event notification rule is met, wherein the time threshold is less than or equal to 1.
  • the time threshold may be set to 5/6. In the case that the monitoring time interval is 1 hour, and the time length for satisfying the event notification rule is greater than or equal to 50 minutes, it may be determined that the continuous event notification is satisfied. rule.
  • Fig. 5 shows a time flow chart for determining the length of time for satisfying an event notification rule according to an embodiment of the present disclosure.
  • the server device receives 6 water quality data from the water quality monitoring device, and judges each water quality data to determine whether it meets the event notification rules, and then , To determine the length of time that the event notification rule is met.
  • the server device obtains the water quality data
  • the time interval is 10 minutes, and it can be determined that the length of time to satisfy the event notification rule is 50 minutes. Therefore, the ratio of the length of time (50 minutes) to the monitoring time interval (1 hour, 60 minutes) is equal to 5/6, that is, not less than the time threshold, it is determined that the continuous event notification rule is met, and then you can The receiver sends event notifications.
  • each node By judging whether the monitoring data at each node meets the event notification rules, it can be obtained whether each node meets the event notification rules.
  • Two adjacent nodes that meet the event notification rules The length between nodes is "a time length unit that satisfies the event notification rule", and the sum of all time length units that meet the event notification rule is the time length.
  • the monitoring time interval t can also be divided into multiple time periods, such as three time periods ts1, ts2, and ts3 (not shown), where one or more time periods acquired in each time period can be Each monitoring data is judged, that is, it is determined whether the monitoring data meets the event notification rule.
  • the number of monitoring data acquired in each time period is related to the length of the time period (for example, 20 minutes) and the time interval for the monitoring device to send the monitoring data (for example, 10 minutes).
  • the judgment result can include that the monitoring data obtained during the ts1 period meets the event notification rules, the monitoring data obtained during the ts2 time period does not meet the event notification rules, and the ts3 time
  • the monitoring data obtained in the segment satisfies the event notification rule, so it can be determined that the time length for satisfying the event notification rule is ts1+ts3, and further, the ratio of the time length ts1+ts3 to the monitoring time interval t can be determined, and In the case that the ratio is not less than the time threshold, it is determined that the continuous event notification rule is satisfied.
  • the event notification rule directly judges the value of the monitoring data, for example, whether it is greater than the monitoring threshold, and the monitoring is performed based on the event notification rule.
  • the judgment result of the data is used to determine whether the continuous event notification rule is satisfied. Therefore, the starting point of the monitoring time interval may be the time point when the server device receives the monitoring data, and from this point in time, the water quality data within 1 hour is continuously monitored to determine whether the continuous event notification is satisfied. The determination of the rules. In the case where it is determined that the continuous event notification rule is satisfied, an event notification can be sent to the receiver.
  • the subscribing device as the receiver can determine that the sewage is discharged from the enterprise and perform further processing actions without subscribing to the device to complete the "shown in Figure 1A" Judgment whether the water quality continues to exceed the standard during the monitoring period. While realizing continuous event monitoring, it reduces the requirements for the processing capabilities of subscribed devices, thereby reducing the communication pressure between devices and improving system efficiency. In addition, it can also avoid the notification interference of the subscribed device by continuously receiving event notifications.
  • determining whether the continuous event notification rule is satisfied may include: in a case where the event notification rule is determined to be satisfied, determining whether the acquired at least one monitoring data meets the monitoring data rule, and obtaining a monitoring result; As a result of the monitoring, it is determined whether the continuous event notification rule is met. Therefore, in this embodiment, the event notification method may further include: acquiring at least one piece of monitoring data, for example, receiving at least one piece of monitoring data from a monitoring device.
  • the monitoring device may be a water quality monitoring device, which may periodically send water quality data to the server device as the monitoring data.
  • the water quality monitoring device sends the monitored water quality data to the server device every 10 minutes. Therefore, in the case where the above-mentioned monitoring time interval is 1 hour, the server device can receive 6 water quality data from the water quality monitoring device within the monitoring time interval.
  • the event notification rule may include at least one of the following: update the attributes of the subscribed resource, create the subscribed resource subresource, delete the subscribed resource subresource, and obtain the subscribed container resource
  • the content instance sub-resources of, receive the operation request of a certain requester, and receive the request of a certain type of operation (including creation request, update request, deletion request, and acquisition request).
  • the server device may create content instance sub-resources in the subscribed resource (monitoring data resource container) to implement operations such as data storage.
  • the event notification rule does not analyze or judge the content of the monitoring data (such as whether the data is greater than the monitoring threshold).
  • the event notification rule may be a non-content judgment rule.
  • the event notification rule may also be to receive an operation request from a certain requester, that is, the event notification rule is satisfied when the operation request is received from a specific requester.
  • the event notification rule may also be to update the attribute of the subscribed resource, that is, if the attribute of the subscribed resource is updated, the event notification rule is satisfied.
  • the event notification rule may also be to delete the sub-resource of the subscribed resource, that is, the event notification rule is satisfied when the sub-resource of the subscribed resource is deleted.
  • the event notification rule may also be to obtain the content instance sub-resource of the subscribed container resource, that is, when the sub-resource of the subscribed resource is obtained, the event notification rule is satisfied.
  • the event notification rule may also be to receive a request for a certain type of operation (including a creation request, an update request, a deletion request, and an acquisition request), that is, the server satisfies the event notification rule when a specified type of request is received.
  • determining whether the monitoring data rule is satisfied and obtaining the monitoring result may include: for each monitoring data in the at least one monitoring data, determining whether the monitoring data meets the monitoring data rule, where the monitoring data meets the In the case of monitoring data rules, a monitoring result that meets the monitoring data rules is obtained; when the monitoring data does not meet the monitoring data rules, a monitoring result that does not meet the monitoring data rules is obtained.
  • determining whether the continuous event notification rule is satisfied may include: determining the number of monitoring results that satisfy the monitoring data rule; and determining that the continuous event is satisfied if the number of monitoring results that meets the monitoring data rule is not less than a count threshold
  • the notification rule wherein the counting threshold is determined based on the number of monitoring data received within the monitoring time interval. Exemplarily, when the number of monitoring data received in the monitoring time interval is 6, the counting threshold may be set to 5.
  • FIG. 6 shows a time flow chart of determining the number of monitoring results that satisfy the monitoring data rule according to an embodiment of the present disclosure.
  • the event notification rule is satisfied, for example, a periodic monitoring request from the subscription device is received.
  • the number of monitoring results that satisfy the monitoring data rule can be determined, for example, it can be six.
  • the number of monitoring results that satisfy the monitoring data rule is greater than the count threshold, that is, it is determined that the continuous event notification rule is satisfied, and then an event notification can be sent to the recipient.
  • determining whether the continuous event notification rule is satisfied includes: determining the length of time corresponding to the monitoring result that satisfies the monitoring data rule; when the ratio of the length of time to the monitoring time interval is not less than a time threshold , It is determined that the continuous event notification rule is satisfied, wherein the time threshold is less than or equal to 1.
  • the time threshold may be set to 5/6. In the case that the monitoring time interval is 1 hour, and the time length for satisfying the event notification rule is greater than or equal to 50 minutes, it may be determined that the continuous event notification is satisfied. rule.
  • FIG. 7 shows a time flow chart for determining the length of time corresponding to the monitoring result that satisfies the monitoring data rule according to an embodiment of the present disclosure.
  • the event notification rule is satisfied, for example, a periodic monitoring request from the subscription device is received.
  • the server device receives 6 water quality data from the water quality monitoring device, and judges each water quality data to determine whether it meets the monitoring data rules, and then , To determine the length of time to meet the monitoring data rules.
  • the ratio of the length of time (50 minutes) to the monitoring time interval (1 hour, 60 minutes) is equal to 5/6, that is, not less than the time threshold, it is determined that the continuous event notification rule is met, and then you can The receiver sends event notifications.
  • the event notification method may further include: determining the start time point and the end time point of the monitoring time interval.
  • FIG. 8 shows a time flow chart of determining a start time point and an end time point according to an embodiment of the present disclosure.
  • the time point that satisfies the event notification rule may be determined as the start time point t1, and the end time point t2 is determined based on the monitoring time interval (for example, 1 hour) and the determined start time point t1 .
  • Fig. 9 shows a time flow chart for determining a start time point and an end time point according to an embodiment of the present disclosure.
  • the time point that satisfies the event notification rule may be determined as the end time point t2, and then the start time point is determined based on the monitoring time interval (for example, 1 hour) and the determined end time point t2 t1.
  • FIG. 10 shows a time flow chart for determining a start time point and an end time point according to an embodiment of the present disclosure.
  • the time point at which the event notification rule is satisfied may be determined as the intermediate time point t3.
  • the start time point t1 and the end time point t2 may be determined based on the monitoring time interval (for example, 1 hour) and the determined intermediate time point t3, wherein the intermediate time point is located at the start time point And the end time point.
  • the intermediate time point t3 is located between the start time point and the end time point. For example, a time interval 30 minutes before and 30 minutes after the time point t3 that meets the event notification rule may be determined as the monitoring time interval.
  • the server device can judge the monitoring data received during the monitoring time interval, for example, for each monitoring data, determine whether the monitoring data meets the monitoring data rules, and then determine the number of monitoring results that meet the monitoring data rules , And determine whether the continuous event notification rule is met based on the set counting threshold. When it is determined that the continuous event notification rule is satisfied, an event notification is sent to the receiver.
  • the subscription request may further include the monitoring time interval.
  • the length of the monitoring time interval is provided by the subscription device to the server device in the subscription request.
  • the subscription device may set the monitoring time interval for this subscription request according to actual application requirements, such as 2 days.
  • the monitoring time interval can also be set by the server device, which is not limited here.
  • the event notification method may further include creating a subscription resource.
  • Fig. 11 shows a schematic diagram of a resource structure of a subscription resource according to an embodiment of the present disclosure.
  • the subscription resource includes multiple attributes. For example, a monitoring time interval attribute used to determine the monitoring time interval, a continuous event notification rule attribute used to determine whether to send an event notification to the at least one recipient, and address information used to store the at least one recipient The properties of the event notification list.
  • the server device may implement the event notification method according to the present disclosure based on the set subscription resource. It should be noted that the subscription resource can also be used to implement other attributes of its function, and there is no restriction here.
  • FIG. 12A shows a schematic diagram of a system according to an embodiment of the present disclosure
  • FIG. 12B shows a processing flowchart of continuous event notification according to an embodiment of the present disclosure.
  • the overall flow of event notification according to the event notification method of the present disclosure will be described in conjunction with FIG. 12A and FIG. 12B.
  • sensor devices, execution devices, and smart water service applications can be connected to the smart water service platform by sending a registration request.
  • the sensing device can be used as a monitoring device
  • the smart water service application can be used as a subscription device
  • the smart water service platform can be used as a server device.
  • the subscription device and the monitoring device can respectively send a registration request to the server device, and receive a registration response sent by the server device, thereby connecting with the server device, and the server device is responsible for performing operations on the devices connected to it. management.
  • the server device is responsible for performing operations on the devices connected to it. management.
  • the subscription device may send a subscription request to the server device, and the subscription request includes the continuous event notification rule and the monitoring time interval.
  • the server device may create a subscription resource, for example, as shown in FIG. 11.
  • the monitoring device may continuously send data to the server device in a data request manner, and receive the data request response returned by the server device. For example, if the server device determines that each piece of monitoring data within the monitoring time interval satisfies the event notification rule, it determines that the continuous event notification rule is satisfied. Then, send event notifications to the subscribing device.
  • the subscription device can process the notified water pollution event after receiving the event notification.
  • the smart water service application shown in FIG. 12A may send a control instruction to the execution device through the smart water service platform.
  • the above describes the event notification method provided by the present disclosure in conjunction with specific embodiments.
  • the server device determines whether the continuous event notification rule is satisfied, and when the continuous event notification rule is satisfied, the event notification is sent to the receiver.
  • the event notification method according to the embodiment of the present disclosure can meet the application requirements of monitoring continuous events, improve system efficiency, reduce the requirements for processing capabilities of subscribed devices, and reduce communication pressure between devices. In addition, it can also avoid the notification interference of the subscribed device by continuously receiving event notifications.
  • FIG. 13 shows a schematic diagram of a server device according to an embodiment of the present disclosure.
  • the server device 100 may include a transceiver 101 and a processor 102, wherein the transceiver 101 may be configured to receive a subscription request from a subscribing device, and the subscription request includes at least one recipient for receiving event notifications. .
  • the processor 102 may be configured to determine whether the continuous event notification rule is satisfied within the monitoring time interval.
  • the processor 102 may be further configured to instruct the transceiver 101 to send the event notification of the subscription request to the at least one recipient when the continuous event notification rule is satisfied.
  • the transceiver 101 is further configured to send the event notification of the subscription request to the at least one recipient when the continuous event notification rule is satisfied.
  • the aforementioned server device 100 may also have a built-in or an external memory for storing resources created for, for example, terminal devices, and storing related instructions, which when executed by the processor 102, implement the steps of the aforementioned event notification method.
  • an event notification system is also provided.
  • Fig. 14 shows a schematic diagram of an event notification system according to an embodiment of the present disclosure.
  • the event notification system 200 may include a subscription device 201 and a server device 202.
  • the subscription device 201 is configured to send a subscription request to the server device 202, and the subscription request includes at least one recipient for receiving event notifications.
  • the at least one recipient may include the subscribing device 201, or include other devices other than the subscribing device 201.
  • the server device 202 may be configured to receive a subscription request from a subscribing device; determine whether the continuous event notification rule is satisfied within the monitoring time interval; and when the continuous event notification rule is satisfied, to the at least one recipient Send an event notification of the subscription request.
  • the event notification system 200 may further include a monitoring device 203.
  • the monitoring device 203 may be configured to send monitoring data to the server device 202.
  • the server device 202 may also be configured to receive at least one piece of monitoring data from the monitoring device within the monitoring time interval.
  • a computer storage medium stores computer readable codes, and when the computer readable codes are executed by one or more processors, the event notification method described above can be performed, and details are not described herein again.
  • the computer storage medium may be any available storage medium that can be accessed by a computer.
  • the computer-readable storage medium includes, but is not limited to, volatile memory and/or non-volatile memory.
  • the volatile memory may include random access memory (RAM) and/or cache memory (cache), for example.
  • the non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, and the like.
  • the computer storage medium may be any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Hydrology & Water Resources (AREA)
  • Environmental & Geological Engineering (AREA)
  • Water Supply & Treatment (AREA)
  • Chemical & Material Sciences (AREA)
  • Organic Chemistry (AREA)
  • Telephonic Communication Services (AREA)
  • Selective Calling Equipment (AREA)

Abstract

本公开提供了一种事件通知方法、系统、服务器设备、计算机存储介质。所述事件通知方法包括：接收来自订阅方的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；在监测时间间隔内，确定是否满足连续事件通知规则；以及在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。

Description

事件通知方法、系统、服务器设备、计算机存储介质 技术领域
本公开涉及物联网领域，具体的涉及一种事件通知方法、系统、服务器设备、计算机存储介质。
背景技术
随着信息技术尤其是互联网技术的发展，用于实现信息化、远程管理控制和智能化的物联网技术逐渐成熟。物联网利用局部网络或互联网等通信技术把传感器、控制器、机器、人员和物品等通过新的方式联接在一起，形成人与物、物与物之间的连接。随着物联网技术在各个应用领域的快速发展，越来越多的设备连接至物联网，出现了诸如智能家居、智能交通、智慧健康等各种新的应用领域。连接至物联网的终端设备可以通过向服务器设备发送订阅请求的方式来获得数据或者事件通知。在满足订阅条件时，物联网平台可以向订阅请求中的通知方发送数据或者事件通知。
发明内容
根据本公开的一方面，提供了一种事件通知方法，包括：接收来自订阅方的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；在监测时间间隔内，确定是否满足连续事件通知规则；以及在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
根据本公开的一些实施例，所述事件通知方法还包括：在所述监测时间间隔内，获取至少一个监测数据，其中，确定是否满足连续事件通知规则包括：确定所述至少一个监测数据中的每一个监测数据是否均满足事件通知规则。
根据本公开的一些实施例，所述事件通知方法还包括：在所述监测时间间隔内，获取至少一个监测数据，其中，确定是否满足连续事件通知规则包括：对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；确定满足事件通知规则的监测数据的数目；在所述数目不小于计数 阈值的情况下，确定满足连续事件通知规则，其中，所述计数阈值是基于在所述监测时间间隔内接收的监测数据的数目确定的。
根据本公开的一些实施例，所述事件通知方法还包括：在所述监测时间间隔内，获取至少一个监测数据，其中，确定是否满足连续事件通知规则包括：对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；基于满足事件通知规则的所述监测数据的时间间隔来确定满足事件通知规则的时间长度；在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。
根据本公开的一些实施例，所述事件通知规则包括以下中的任一项：所述监测数据大于监测阈值；所述监测数据等于监测阈值；所述监测数据小于监测阈值；所述监测数据不小于监测阈值；以及所述监测数据不大于监测阈。值。
根据本公开的一些实施例，所述事件通知方法还包括：在所述监测时间间隔内，获取至少一个监测数据，其中，确定是否满足连续事件通知规则包括：在确定满足事件通知规则的情况下，确定是否满足监测数据规则，获得监测结果；基于所述监测结果，确定是否满足所述连续事件通知规则。
根据本公开的一些实施例，其中，所述事件通知规则包括以下中的至少一种：更新被订阅资源的属性；创建被订阅资源子资源；删除被订阅资源子资源；获取被订阅容器资源的内容实例子资源；接收某一请求方的操作请求；接收某一类操作的请求，所述监测数据规则包括以下中的任一项：所述监测数据大于监测阈值；所述监测数据等于监测阈值；所述监测数据小于监测阈值；所述监测数据不小于监测阈值；以及所述监测数据不大于监测阈值。
根据本公开的一些实施例，确定是否满足监测数据规则，获得监测结果包括：对于所述至少一个监测数据中的每一个监测数据，确定该监测数据是否满足监测数据规则，其中，在该监测数据满足监测数据规则的情况下，获得满足监测数据规则的监测结果；在该监测数据不满足监测数据规则的情况下，获得不满足监测数据规则的监测结果。
根据本公开的一些实施例，确定是否满足连续事件通知规则包括：确定满足监测数据规则的监测结果的数目；在满足监测数据规则的监测结果的数 目不小于计数阈值的情况下，确定满足连续事件通知规则，其中，所述计数阈值是基于在所述监测时间间隔内接收的监测数据的数目确定的。
根据本公开的一些实施例，确定是否满足连续事件通知规则包括：确定满足监测数据规则的监测结果对应的时间长度；在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。
根据本公开的一些实施例，还包括：监测时间间隔的起始时间点和结束时间点，其中将满足事件通知规则的时间点确定为所述起始时间点；基于所述监测时间间隔和确定的起始时间点确定所述结束时间点。
根据本公开的一些实施例，还包括：监测时间间隔的起始时间点和结束时间点，其中将满足事件通知规则的时间点确定为所述结束时间点；基于所述监测时间间隔和确定的结束时间点确定所述起始时间点。
根据本公开的一些实施例，还包括监测时间间隔的起始时间点和结束时间点，其中将满足事件通知规则的时间点确定为中间时间点；基于所述监测时间间隔和确定的中间时间点确定所述起始时间点和结束时间点，其中，所述中间时间点位于所述起始时间点和结束时间点之间。
根据本公开的一些实施例，所述订阅请求中还包括所述监测时间间隔，所述事件通知方法还包括：创建订阅资源，所述订阅资源中包括以下属性：监测时间间隔属性，用于确定所述监测时间间隔；连续事件通知规则属性，用于确定是否向所述至少一个接收方发送事件通知；事件通知列表属性，用于存储所述至少一个接收方的地址信息。
根据本公开的另一方面，还提供了一种服务器设备，包括收发器和处理器，其中，所述收发器配置成接收来自订阅设备的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；所述处理器配置成：在监测时间间隔内，确定是否满足连续事件通知规则；所述收发器还配置成在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
根据本公开的又一方面，还提供一种事件通知系统，包括：订阅设备，配置成向服务器设备发送订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；服务器设备，配置成：接收来自订阅设备的订阅请求； 获取至少一个监测数据；在监测时间间隔内，确定是否满足连续事件通知规则；以及在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知；以及监测设备，配置成向所述服务器设备发送监测数据。
根据本公开的又一方面，还提供了一种计算机存储介质，其中存储有计算机可读代码，所述计算机可读代码在由一个或多个处理器执行时进行如上所述的事件通知方法。
附图说明
为了更清楚地说明本公开实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1A示出了即时事件通知的处理流程图；
图1B示出了即时事件通知的时间流程图；
图2示出了根据本公开实施例的事件通知方法的流程图；
图3示出了根据本公开实施例的确定每个监测数据满足事件通知规则的时间流程图；
图4示出了根据本公开实施例的确定满足事件通知规则的监测数据的数目的时间流程图；
图5示出了根据本公开实施例的确定满足事件通知规则的时间长度的时间流程图；
图6示出了根据本公开实施例的确定满足监测数据规则的监测结果的数目的时间流程图；
图7示出了根据本公开实施例的确定满足监测数据规则的监测结果对应的时间长度的时间流程图；
图8示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图；
图9示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图；
图10示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图；
图11示出了根据本公开实施例的订阅资源的资源结构示意图；
图12A示出了根据本公开一个实施例的系统示意图；
图12B示出了根据本公开一个实施例的连续事件通知的处理流程图；
图13示出了根据本公开实施例的服务器设备的示意性框图；
图14示出了根据本公开实施例的事件通知系统的示意性框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在无需创造性劳动的前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开中使用的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“包括”或者“包含”等类似的词语意指出现该词前面的元件或者物件涵盖出现在该词后面列举的元件或者物件及其等同，而不排除其他元件或者物件。“连接”或者“相连”等类似的词语并非限制于物理连接或者机械连接，而是可以包括诸如电性连接等连接方式，例如，所述电性连接可以是直接的连接也可以是间接的连接。
本公开中使用了流程图用来说明根据本公开的实施例的方法的步骤。应当理解的是，前面或后面的步骤不一定按照顺序来精确的进行。相反，可以按照倒序或同时处理各种步骤。同时，也可以将其他操作添加到这些过程中，或从这些过程移除某一步个步骤或数个步骤。
物联网作为互联网的延伸，可以包括互联网及互联网上所有的资源，并且兼容互联网中的应用。随着物联网应用在各个领域不断扩展，出现了诸如智能家居、智能交通、智慧健康、智能水质监测等各种新的应用领域。
越来越多的终端设备连接到物联网平台。所述终端设备例如可以是烟雾报警器、火灾报警器、各类家用电器、水质监测设备以及各种类型的传感设备、执行设备等。所述物联网平台例如可以实施为通用服务实体，或者称为 服务器设备，所述终端设备可以通过向服务器设备发送注册信息的方式来与所述服务器设备连接，由所述服务器设备对连接到其的终端设备进行管理。连接到服务器设备的终端设备还可以与该服务器设备进行数据传输、信息交互等操作。需要注意的是，本文中所描述的终端设备可以是物联网领域中的各类终端设备，或者也可以是设备中的软件模块等。
一些终端设备(例如，作为订阅设备)可以通过向服务器设备发送订阅请求的方式来订阅来自其他终端设备(例如，作为监测设备)的信息、数据等，所述订阅设备也可以请求来自服务器设备的数据、操作等，在此不作限制。
所述订阅请求中可以包括订阅条件，使得服务器设备在确定满足该订阅条件(例如，烟雾警报器发出警报)的情况下，发送事件通知。所述订阅条件也可以称为事件通知规则，换句话说，在服务器设备确定满足事件通知规则的情况下，则发送事件通知。
上述事件通知的方式可以称为即时事件通知。图1A示出了即时事件通知的处理流程图。首先，订阅设备以及监测设备可以通过向服务器设备发送注册请求的方式来与服务器设备连接。订阅设备可以向服务器设备发送订阅请求，所述订阅请求中可以包括事件通知规则。以监测水质变化为例，所述监测设备具体可以是水质监测设备，所述事件通知规则可以是所述水质监测设备监测到的水质数据大于预设阈值。水质监测设备可以持续地向服务器设备发送检测到的水质数据，服务器设备可以对接收的水质数据进行是否满足事件通知规则的判断，在确定水质数据大于预设阈值(即，满足事件通知规则)的情况下，服务器设备发送事件通知。
图1B示出了即时事件通知的时间流程图，结合图1A可知，在服务器设备接收到监测设备的水质数据之后，立即进行该水质数据是否满足事件通知规则的判断，并在确定满足事件通知规则之后，发送事件通知。由此，对于诸如水质监测等需要持续性监测其水质数据的应用场景中，监测设备持续地向服务器设备发送数据，服务器设备则不断地向订阅设备发送事件通知。
进一步地，订阅设备有需要对一段时间内的水质数据进行监控，并基于该时间段内的水质数据做出判断。例如，在上述示例中，当水质数据超过预设阈值时通知订阅设备。然而，在实际应用场景中，造成水质数据超过预设 阈值的原因例如可以包括：家庭污水排放和企业污水排放。以上两种原因都可能造成水质数据超过预设阈值，或者称为水质超标。通常，家庭污水排放时间较短，而企业污水排放时间较长，订阅设备可能只希望加强对企业污水排放的治理。在一段时间内，订阅设备将持续地从服务器设备接收事件通知，并基于以上通知来进行是家庭污水排放还是企业污水排放的判断，例如，如果监测周期内水质数据持续超标，即，水质数据持续大于预设阈值，由此确认水质超标现象由企业排污导致，并对此水质污染事件进行处理。
总的来说，在实际应用中，有需要对连续的数据变化(或者，状态变化)进行监控，诸如，一段时间内的水质数据，在以上结合图1A和图1B描述的即时事件通知的实现方式中，由订阅设备来进行对连续的数据变化的监控，其需要持续地接收事件通知，这增加了设备之间的通信负荷，也可能会造成通信拥塞的情况。此外，由订阅设备来进行对连续的数据变化的监控处理也将增加对订阅设备的处理能力的要求。
因此，有需要提供一种应用于连续事件的监控机制，所述连续事件例如可以是连续数据变化，也可以是连续状态变化等，例如，水质超标持续10分钟、空气污染超标持续10分钟、噪声污染持续超过20分钟、水龙头持续打开5分钟、门持续打开超过5分钟等。
本公开提供一种事件通知方法，由服务器设备实现对连续事件的监控，在确定接收的数据满足连续事件通知规则的情况下，向订阅设备发送事件通知，能提升物联网系统的处理效率，降低对于订阅设备的处理能力的要求，还能避免设备之间的通信负荷以及通信拥塞，减少事件通知的次数。
具体的，图2示出了根据本公开实施例的事件通知方法的流程图。例如，图2中示出的事件通知方法可以由物联网领域中的服务器设备来执行。
首先，在步骤S101，接收来自订阅方的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方。所述订阅方可以是连接至服务器设备的终端设备，也可以是连接至服务器的应用，例如，在需要某些数据时，订阅设备可以向服务器设备发送订阅请求。所述订阅请求中可以包括订阅的数据、事件或者操作。
所述订阅方可以是一个也可以是多个，即，可以由多个订阅方向服务器设备发送订阅请求。所述接收方可以是用于接收事件通知的接收设备，也可 以是接收事件通知的接收应用，在服务器设备接收到订阅请求后将获得所有接收方的列表信息，还可以基于接收方的类型、级别、订阅请求的内容等来对所述接收方进行分组，以用于更精准的发送事件通知。需要注意的是，订阅方和接收方可以是同一设备或应用，也可以是不同的设备或应用。举例来说，订阅设备1可以向服务器设备发送订阅请求，订阅请求中包括接收设备1、接收设备2以及所述订阅设备1作为所述接收方，用于在满足订阅条件的情况下接收事件通知。
接着，在步骤S102，在监测时间间隔内，确定是否满足连续事件通知规则。所述监测时间间隔可以是持续地一段时间，诸如1小时，可以根据具体的应用需求来设置所述监测时间间隔的时间长度。确定是否满足连续事件通知规则的步骤将在下文进行详细描述。
接着，在步骤S103，在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。例如，在服务器设备确定满足连续事件通知规则的情况下，可以向所述接收设备1、接收设备2以及订阅设备1发送事件通知，从而实现对于连续事件的监控。
根据本公开的一些实施例，所述事件通知方法还可以包括：在所述监测时间间隔内，获取至少一个监测数据。例如，监测设备可以是水质监测设备，其可以定期地向服务器设备发送水质数据，作为所述监测数据。例如，水质监测设备每隔10分钟向服务器设备发送监测的水质数据。由此，在上述监测时间间隔是1小时的情形中，在该监测时间间隔内，服务器设备可以从水质监测设备接收到6个水质数据。
根据本公开的一个示例，确定是否满足连续事件通知规则可以包括：确定所述至少一个监测数据中的每一个监测数据是否满足事件通知规则。所述事件通知规则可以包括以下中的任一项：所述监测数据大于监测阈值；所述监测数据等于监测阈值；所述监测数据小于监测阈值；所述监测数据不小于监测阈值；以及所述监测数据不大于监测阈值。此外，还可以根据实际地应用需求设置所述事件通知规则，在此不作限制。
图3示出了根据本公开实施例的确定每个监测数据满足事件通知规则的时间流程图。以上述水质监测为例，所述监测时间间隔可以是从t1至t2的时间段，例如，1小时。在1小时内，服务器设备从水质监测设备接收6个 水质数据。确定是否满足连续事件通知规则可以包括：确定接收的6个水质数据满足事件通知规则。换句话说，在服务器设备确定接收的6个水质数据中的每个水质数据均满足事件通知规则(诸如，大于监测阈值)的情况下，则确定满足所述连续事件通知规则，接着，可以向接收方发送事件通知。
根据本公开的另一示例，确定是否满足连续事件通知规则可以包括：对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；确定满足事件通知规则的监测数据的数目；在所述数目不小于计数阈值的情况下，确定满足连续事件通知规则。根据本公开实施例，所述计数阈值可以是基于在所述监测时间间隔内接收的监测数据的数目确定的。示例性地，在所述监测时间间隔内接收的监测数据的数目为6的情况下，所述计数阈值可以设置为5、4或3，或者是1-6中的任一数值，不同的应用场景可以匹配不同的数值或相同的数值。
图4示出了根据本公开实施例的确定满足事件通知规则的监测数据的数目的时间流程图。以上述水质监测为例，在所述监测时间间隔(1小时)内，服务器设备从水质监测设备接收到6个水质数据，并对每个水质数据进行判断，确定其是否满足事件通知规则，例如，是否大于监测阈值，并确定满足事件通知规则的水质数据(即监测数据)的数目，例如，可以是5个。由于所述数目不小于计数阈值5，则确定满足连续事件通知规则，接着，可以向接收方发送事件通知。根据本公开实施例，所述事件通知可以是由服务器设备向一个或多个接收方发送的消息，该消息可以与所述订阅请求相关联。所述接收方可以基于接收到该消息而确定所述订阅请求中的连续事件通知规则得到满足，例如，在监测时间间隔内，水质数据持续超过监测阈值。接着，所述接收方可以进行进一步地处理操作，诸如查找水质污染源，以及水质净化处理。
根据本公开的另一示例，确定是否满足连续事件通知规则可以包括：对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；基于满足事件通知规则的所述监测数据的时间间隔来确定满足事件通知规则的时间长度；在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。示例性地，所述时间阈值可以设置为5/6，在所述监测时间间隔为1小时的情况下， 在满足事件通知规则的时间长度大于等于50分钟的情况下，可以确定满足连续事件通知规则。
图5示出了根据本公开实施例的确定满足事件通知规则的时间长度的时间流程图。以上述水质监测为例，在所述监测时间间隔(1小时)内，服务器设备从水质监测设备接收到6个水质数据，并对每个水质数据进行判断，确定其是否满足事件通知规则，接着，确定满足事件通知规则的时间长度。例如，在确定满足事件通知规则的水质数据(即监测数据)的数目为5个的情况下，并且基于所述水质监测设备每隔10分钟向服务器设备发送水质数据，即，服务器设备获取水质数据的时间间隔为10分钟，可以确定满足事件通知规则的时间长度为50分钟。由此，所述时间长度(50分钟)与所述监测时间间隔(1小时，即60分钟)的比值等于5/6，即不小于时间阈值，则确定满足连续事件通知规则，接着，可以向接收方发送事件通知。一个时间轴上有多个节点(监测数据时间点)，通过判断每个节点处的监测数据是否满足事件通知规则，从而可以得到各个节点是否满足事件通知规则，相邻两个满足事件通知规则的节点之间的长度为“满足事件通知规则的一个时间长度单元”，所有满足事件通知规则的时间长度单元加起来即为所述时间长度。
作为另一示例，还可以将所述监测时间间隔t划分为多个时间段，诸如3个时间段ts1、ts2和ts3(未示出)，其中，可以对各个时间段内获取的一个或多个监测数据进行判断，即，确定监测数据是否满足事件通知规则。在各个时间段内获取的监测数据的数目与该时间段的长度(例如，20分钟)以及监测设备发送监测数据的时间间隔(例如，10分钟)相关。例如，以三个时间段ts1、ts2和ts3为例，判断结果可以包括，ts1时间段内获取的监测数据满足事件通知规则，ts2时间段内获取的监测数据不满足事件通知规则，以及ts3时间段内获取的监测数据满足事件通知规则，由此可以确定满足事件通知规则的时间长度为ts1+ts3，进一步的，可以确定所述时间长度ts1+ts3与所述监测时间间隔t的比值，以及在所述比值不小于时间阈值的情况下，确定满足连续事件通知规则。
在以上结合图3-5描述的确定是否满足连续事件通知规则的示例中，所述事件通知规则直接对监测数据的数值进行判断，例如，是否大于监测阈值，并基于所述事件通知规则对监测数据的判断结果来进行是否满足连续事件通 知规则的确定。由此，所述监测时间间隔的起始点可以是在服务器设备接收到监测数据的时间点处，并从该时间点处开始，持续监控诸如1小时内的水质数据，以进行是否满足连续事件通知规则的确定。在确定满足连续事件通知规则的情况下，可以向接收方发送事件通知。在上述水质监测示例中，作为所述接收方的订阅设备在接收到事件通知后，便可以确定是企业污水排放，并进行进一步的处理动作，而无需订阅设备来完成图1A中示出的“监测周期内水质是否持续超标”的判断。在实现连续事件监控的同时，降低了对于订阅设备的处理能力的要求，从而降低设备之间的通信压力，提升系统效率。此外，还可以避免持续接收事件通知对订阅设备的通知干扰。
根据本公开的另一些实施例，确定是否满足连续事件通知规则可以包括：在确定满足事件通知规则的情况下，确定所获取的至少一个监测数据是否满足监测数据规则，获得监测结果；基于所述监测结果，确定是否满足所述连续事件通知规则。因此在此实施例中，所述事件通知方法还可以包括：获取至少一个监测数据，例如，从监测设备接收至少一个监测数据。例如，所述监测设备可以是水质监测设备，其可以定期地向服务器设备发送水质数据，作为所述监测数据。例如，水质监测设备每隔10分钟向服务器设备发送监测的水质数据。由此，在上述监测时间间隔是1小时的情形中，在该监测时间间隔内，服务器设备可以从水质监测设备接收到6个水质数据。
在根据本公开的上述实施例中，所述事件通知规则可以包括以下中的至少一种：更新被订阅资源的属性、创建被订阅资源子资源、删除被订阅资源子资源、获取被订阅容器资源的内容实例子资源、接收某请求方的操作请求、接收某类操作的请求(包括创建请求、更新请求、删除请求、获取请求)。
举例来说，在从监测设备接收到监测数据之后，服务器设备可以在被订阅资源(监测数据资源容器)创建内容实例子资源，以实现对于数据的存储等操作。需要注意的是，上述实施例中，所述事件通知规则并不对监测数据的内容进行分析、判断(诸如，数据是否大于监测阈值)。换句话说，所述事件通知规则可以是非内容判断规则。例如，所述事件通知规则还可以是接收某一请求方的操作请求，即，在接收到操作请求来自特定的请求方则满足所述事件通知规则。又例如，所述事件通知规则也可以是更新被订阅资源的属性，即被订阅资源的属性发生更新则满足事件通知规则。又例如，所述事件 通知规则还可以为删除被订阅资源的子资源，即当被订阅资源的子资源被删除时满足事件通知规则。又例如，所述事件通知规则还可以是获取被订阅容器资源的内容实例子资源，即被订阅资源的子资源被获取时则满足事件通知规则。又例如，所述事件通知规则还可以为接收某类操作的请求(包括创建请求、更新请求、删除请求、获取请求)，即服务器接收到指定类型的请求时满足事件通知规则。
根据本公开实施例，确定是否满足监测数据规则，获得监测结果可以包括：对于所述至少一个监测数据中的每一个监测数据，确定该监测数据是否满足监测数据规则，其中，在该监测数据满足监测数据规则的情况下，获得满足监测数据规则的监测结果；在该监测数据不满足监测数据规则的情况下，获得不满足监测数据规则的监测结果。
根据本公开的一个示例，确定是否满足连续事件通知规则可以包括：确定满足监测数据规则的监测结果的数目；在满足监测数据规则的监测结果的数目不小于计数阈值的情况下，确定满足连续事件通知规则，其中，所述计数阈值是基于在所述监测时间间隔内接收的监测数据的数目确定的。示例性地，在所述监测时间间隔内接收的监测数据的数目为6的情况下，所述计数阈值可以设置为5。
图6示出了根据本公开实施例的确定满足监测数据规则的监测结果的数目的时间流程图。首先，在时间点t1确定满足事件通知规则，例如，接收到来自所述订阅设备的周期监测请求。接着，对于在由t1和t2表示的监测时间间隔内接收到的每一个监测数据，确定该监测数据是否满足监测数据规则，并获得监测结果。接着，可以确定满足监测数据规则的监测结果的数目，例如，可以是6个。由此，可以确定满足监测数据规则的监测结果的数目大于计数阈值，即，确定满足连续事件通知规则，接着，可以向接收方发送事件通知。
根据本公开的另一示例，确定是否满足连续事件通知规则包括：确定满足监测数据规则的监测结果对应的时间长度；在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。示例性地，所述时间阈值可以设置为5/6，在所述监测时间间隔为1小时的情况下，在满足事件通知规则的时间长度大于等于 50分钟的情况下，可以确定满足连续事件通知规则。
图7示出了根据本公开实施例的确定满足监测数据规则的监测结果对应的时间长度的时间流程图。类似的，可以在时间点t1处确定满足事件通知规则，例如，接收到来自所述订阅设备的周期监测请求。接着，对于在监测时间间隔内接收到的每一个监测数据，确定该监测数据是否满足监测数据规则，并获得监测结果。以上述水质监测为例，在所述监测时间间隔(1小时)内，服务器设备从水质监测设备接收到6个水质数据，并对每个水质数据进行判断，确定其是否满足监测数据规则，接着，确定满足监测数据规则的时间长度。举例来说，在确定满足监测数据规则的监测数据的数目为5个的情况下，并且基于所述水质监测设备每隔10分钟向服务器设备发送水质数据，可以确定满足监测数据规则的时间长度为50分钟。由此，所述时间长度(50分钟)与所述监测时间间隔(1小时，即60分钟)的比值等于5/6，即不小于时间阈值，则确定满足连续事件通知规则，接着，可以向接收方发送事件通知。
根据本公开实施例，所述事件通知方法还可以包括：确定监测时间间隔的起始时间点和结束时间点。
图8示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图。作为一个示例，可以将满足事件通知规则的时间点确定为所述起始时间点t1，基于所述监测时间间隔(例如，1小时)和确定的起始时间点t1确定所述结束时间点t2。
图9示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图。作为一个示例，可以将满足事件通知规则的时间点确定为所述结束时间点t2，接着，基于所述监测时间间隔(例如，1小时)和确定的结束时间点t2确定所述起始时间点t1。
图10示出了根据本公开实施例的确定起始时间点和结束时间点的时间流程图。作为一个示例，可以将满足事件通知规则的时间点确定为中间时间点t3。接着，可以基于所述监测时间间隔(例如，1小时)和确定的中间时间点t3确定所述起始时间点t1和结束时间点t2，其中，所述中间时间点位于所述起始时间点和结束时间点之间。如图10所示出的，所述中间时间点t3位于所述起始时间点和结束时间点之间。举例来说，可以将满足事件通知规则的时间点t3之前30分钟以及之后30分钟的时间区间确定为所述监测时 间间隔。接着，服务器设备可以对在此监测时间间隔内接收到的监测数据进行判断，例如，对于每一个监测数据，确定该监测数据是否满足监测数据规则，接着，确定满足监测数据规则的监测结果的数目，并基于设置的计数阈值确定是否满足连续事件通知规则。在确定满足连续事件通知规则的情况下，向接收方发送事件通知。
根据本公开实施例，所述订阅请求中还可以包括所述监测时间间隔。换句话说，所述监测时间间隔的时间长度由订阅设备在所述订阅请求中提供给服务器设备。例如，订阅设备可以根据实际的应用需求设置针对此订阅请求的监测时间间隔，诸如，2天。此外，所述监测时间间隔还可以由服务器设备来设置，在此不作限制。
根据本公开实施例，所述事件通知方法还可以包括创建订阅资源。图11示出了根据本公开实施例的订阅资源的资源结构示意图。如图11所示，所述订阅资源中包括多个属性。例如，用于确定所述监测时间间隔的监测时间间隔属性、用于确定是否向所述至少一个接收方发送事件通知的连续事件通知规则属性、以及用于存储所述至少一个接收方的地址信息的事件通知列表属性。所述服务器设备可以基于设置的订阅资源来实施根据本公开的事件通知方法。需要注意的是，所述订阅资源中还可以用于实现其功能的其他属性，在此不作限制。
图12A示出了根据本公开一个实施例的系统示意图，图12B示出了根据本公开一个实施例的连续事件通知的处理流程图。以下，将结合图12A和图12B来描述根据本公开的事件通知方法进行事件通知的整体流程。
如图12A所示，以智能水务应用为示例，传感设备、执行设备以及智能水务应用可以通过发送注册请求的方式连接到智能水务服务平台。其中，所述传感设备可以作为监测设备，所述智能水务应用可以作为订阅设备，所述智能水务服务平台可以作为服务器设备。
如图12B所示，订阅设备、监测设备可以分别向服务器设备发送注册请求，并接收服务器设备发送的注册响应，由此与所述服务器设备连接，所述服务器设备负责对接入其的设备进行管理。其中，所述监测设备可以是一个也可以是多个，在此不作限制。
接着，订阅设备可以向服务器设备发送订阅请求，所述订阅请求中包括 连续事件通知规则以及监测时间间隔。响应于接收到的订阅请求，所述服务器设备可以创建订阅资源，例如，如图11所示出的。
接着，在所述监测时间间隔内，监测设备可以以数据请求的方式持续地向服务器设备发送数据，并接收服务器设备返回的数据请求响应。举例来说，如果所述服务器设备确定在所述监测时间间隔内的每一个监测数据均满足事件通知规则，则确定满足连续事件通知规则。接着，向订阅设备发送事件通知。所述订阅设备在接收到事件通知后即可对通知的水质污染事件进行处理。例如，响应于接收的事件通知，图12A中示出的智能水务应用可以通过智能水务服务平台向执行设备发送控制指令。
以上结合具体的实施例描述了根据本公开提供的事件通知方法，在监测时间间隔内，由服务器设备确定是否满足连续事件通知规则，在满足连续事件通知规则的情况下，向接收方发送事件通知。根据本公开实施例的事件通知方法可以满足监控连续事件的应用需求，提升了系统效率，降低对于订阅设备的处理能力的要求，降低设备之间的通信压力。此外，还可以避免持续接收事件通知对订阅设备的通知干扰。
根据本公开实施例，还提供了一种服务器设备。图13示出了根据本公开实施例的服务器设备的示意图。所述服务器设备100可以包括收发器101和处理器102，其中，所述收发器101可以被配置为接收来自订阅设备的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方。所述处理器102可以被配置为在监测时间间隔内，确定是否满足连续事件通知规则。此外，所述处理器102还可以被配置为在满足所述连续事件通知规则的情况下，指示所述收发器101向所述至少一个接收方发送所述订阅请求的事件通知。所述收发器101还配置成在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
可选地，上述服务器设备100还可以内置或者外接存储器，用于存储为诸如终端设备创建的资源，以及存储有关指令，所述指令在由处理器102执行时，实现上述事件通知方法的步骤。
根据本公开实施例，还提供了一种事件通知系统。图14示出了根据本公开实施例的事件通知系统的示意图。所述事件通知系统200可以包括订阅设备201和服务器设备202。所述订阅设备201配置成向所述服务器设备202 发送订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方。根据本公开实施例，所述至少一个接收方可以包括所述订阅设备201，或者包括除所述订阅设备201之外的其他设备。
所述服务器设备202可以配置成接收来自订阅设备的订阅请求；在监测时间间隔内，确定是否满足连续事件通知规则；以及在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
根据本公开实施例，所述事件通知系统200还可以包括监测设备203。所述监测设备203可以配置成向所述服务器设备202发送监测数据。所述服务器设备202还可以配置成在所述监测时间间隔内，从监测设备接收至少一个监测数据。
根据本公开实施例，还提供了一种计算机存储介质。所述计算机存储介质中存储有计算机可读代码，所述计算机可读代码在由一个或多个处理器执行时进行可以进行如上所述的事件通知方法，在此不再赘述。所述计算机存储介质可以是能被计算机访问的任何可用存储介质。例如，所述计算机可读存储介质包括但不限于易失性存储器和/或非易失性存储器。所述易失性存储器例如可以包括随机存取存储器(RAM)和/或高速缓冲存储器(cache)等。所述非易失性存储器例如可以包括只读存储器(ROM)、硬盘、闪存等。或者，所述计算机存储介质可以是能被用来承载或存储指令或数据结构形式的期望程序代码且能被计算机访问的任何其他介质。
本领域技术人员能够理解，本公开所披露的内容可以出现多种变型和改进。例如，以上所描述的各种设备或组件可以通过硬件实现，也可以通过软件、固件、或者三者中的一些或全部的组合实现。
此外，虽然本公开对根据本公开的实施例的系统中的某些单元做出了各种引用，然而，任何数量的不同单元可以被使用并运行在客户端和/或服务器上。所述单元仅是说明性的，并且所述系统和方法的不同方面可以使用不同单元。
除非另有定义，这里使用的所有术语(包括技术和科学术语)具有与本公开所属领域的普通技术人员共同理解的相同含义。还应当理解，诸如在通常字典里定义的那些术语应当被解释为具有与它们在相关技术的上下文中的含义相一致的含义，而不应用理想化或极度形式化的意义来解释，除非这里 明确地这样定义。
以上是对本公开的说明，而不应被认为是对其的限制。尽管描述了本公开的若干示例性实施例，但本领域技术人员将容易地理解，在不背离本公开的新颖教学和优点的前提下可以对示例性实施例进行许多修改。因此，所有这些修改都意图包含在权利要求书所限定的本公开范围内。应当理解，上面是对本公开的说明，而不应被认为是限于所公开的特定实施例，并且对所公开的实施例以及其他实施例的修改意图包含在所附权利要求书的范围内。本公开由权利要求书及其等效物限定。
本申请要求于2019年9月16日递交、发明名称为“事件通知方法、系统，服务器设备、计算机存储介质”的中国专利申请第201910872383.4号的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。

Claims (17)

  1. 一种事件通知方法，包括：
    接收来自订阅方的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；
    在监测时间间隔内，确定是否满足连续事件通知规则；以及
    在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
  2. 根据权利要求1所述的事件通知方法，还包括：在所述监测时间间隔内，获取至少一个监测数据，其中，确定是否满足连续事件通知规则包括：
    确定所述至少一个监测数据中的每一个监测数据是否满足事件通知规则。
  3. 根据权利要求1所述的事件通知方法，还包括：在所述监测时间间隔内，获取至少一个监测数据，
    其中，确定是否满足连续事件通知规则包括：
    对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；
    确定满足事件通知规则的监测数据的数目；
    在所述数目不小于计数阈值的情况下，确定满足连续事件通知规则，其中，所述计数阈值是基于在所述监测时间间隔内接收的监测数据的数目确定的。
  4. 根据权利要求1所述的事件通知方法，还包括：在所述监测时间间隔内，获取至少一个监测数据，
    其中，确定是否满足连续事件通知规则包括：
    对于所述至少一个监测数据中的每一个监测数据，确定是否满足事件通知规则；
    基于满足事件通知规则的所述监测数据的时间间隔确定满足事件通知规则的时间长度；
    在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。
  5. 根据权利要求2-4中任一项所述的事件通知方法，其中，所述事件通知规则包括以下中的任一项：
    所述监测数据大于监测阈值；
    所述监测数据等于监测阈值；
    所述监测数据小于监测阈值；
    所述监测数据不小于监测阈值；以及
    所述监测数据不大于监测阈值。
  6. 根据权利要求1所述的事件通知方法，还包括：在所述监测时间间隔内，获取至少一个监测数据，
    其中，确定是否满足连续事件通知规则包括：
    在确定满足事件通知规则的情况下，对于所述至少一个监测数据，确定是否满足监测数据规则，获得监测结果；
    基于所述监测结果，确定是否满足所述连续事件通知规则。
  7. 根据权利要求6所述的事件通知方法，其中，所述事件通知规则包括以下中的至少一种：更新被订阅资源的属性；创建被订阅资源子资源；删除被订阅资源子资源；获取被订阅容器资源的内容实例子资源；接收某一请求方的操作请求；接收某一类操作的请求，
    所述监测数据规则包括以下中的任一项：监测数据大于监测阈值；监测数据等于监测阈值；监测数据小于监测阈值；监测数据不小于监测阈值；以及，监测数据不大于监测阈值。
  8. 根据权利要求6所述的事件通知方法，其中，确定是否满足监测数据规则，获得监测结果包括：
    对于所述至少一个监测数据中的每一个监测数据，确定该监测数据是否满足监测数据规则，其中，
    在该监测数据满足监测数据规则的情况下，获得满足监测数据规则的监测结果；在该监测数据不满足监测数据规则的情况下，获得不满足监测数据规则的监测结果。
  9. 根据权利要求8所述的事件通知方法，其中，确定是否满足连续事件通知规则包括：
    确定满足监测数据规则的监测结果的数目；
    在满足监测数据规则的监测结果的数目不小于计数阈值的情况下，确定满足连续事件通知规则，其中，所述计数阈值是基于在所述监测时间间隔内接收的监测数据的数目确定的。
  10. 根据权利要求8所述的事件通知方法，其中，确定是否满足连续事件通知规则包括：
    确定满足监测数据规则的监测结果对应的时间长度；
    在所述时间长度与所述监测时间间隔的比值不小于时间阈值的情况下，确定满足连续事件通知规则，其中，所述时间阈值小于等于1。
  11. 根据权利要求6所述的事件通知方法，还包括：确定监测时间间隔的起始时间点和结束时间点，其中，将满足事件通知规则的时间点确定为所述起始时间点；
    基于所述监测时间间隔和确定的起始时间点确定所述结束时间点。
  12. 根据权利要求6所述的事件通知方法，还包括：确定监测时间间隔的起始时间点和结束时间点，其中，
    将满足事件通知规则的时间点确定为所述结束时间点；
    基于所述监测时间间隔和确定的结束时间点确定所述起始时间点。
  13. 根据权利要求6所述的事件通知方法，还包括：确定监测时间间隔的起始时间点和结束时间点，其中，
    将满足事件通知规则的时间点确定为中间时间点；
    基于所述监测时间间隔和确定的中间时间点确定所述起始时间点和结束时间点，其中，所述中间时间点位于所述起始时间点和结束时间点之间。
  14. 根据权利要求1所述的事件通知方法，其中，所述订阅请求中还包括所述监测时间间隔，所述事件通知方法还包括：创建订阅资源，所述订阅资源中包括以下属性：
    监测时间间隔属性，用于确定所述监测时间间隔；
    连续事件通知规则属性，用于确定是否向所述至少一个接收方发送事件通知；
    事件通知列表属性，用于存储所述至少一个接收方的地址信息。
  15. 一种服务器设备，包括收发器和处理器，其中，
    所述收发器配置成接收来自订阅方的订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；
    所述处理器配置成：在监测时间间隔内，确定是否满足连续事件通知规则；
    所述收发器还配置成在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知。
  16. 一种事件通知系统，包括：
    订阅设备，配置成向服务器设备发送订阅请求，所述订阅请求中包括用于接收事件通知的至少一个接收方；
    服务器设备，配置成：
    接收来自订阅设备的订阅请求；
    获取至少一个监测数据；
    在监测时间间隔内，确定是否满足连续事件通知规则；以及
    在满足所述连续事件通知规则的情况下，向所述至少一个接收方发送所述订阅请求的事件通知；
    监测设备，配置成向所述服务器设备发送监测数据。
  17. 一种计算机存储介质，其中存储有计算机可读代码，所述计算机可读代码在由一个或多个处理器执行时进行如权利要求1-14中任一项所述的事件通知方法。
PCT/CN2020/115074 2019-09-16 2020-09-14 事件通知方法、系统、服务器设备、计算机存储介质 WO2021052289A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20866007.6A EP4033722A4 (en) 2019-09-16 2020-09-14 EVENT NOTIFICATION METHOD, SYSTEM, SERVER DEVICE AND COMPUTER STORAGE MEDIUM
JP2022516700A JP2022547726A (ja) 2019-09-16 2020-09-14 イベント通知方法、システム、サーバデバイス、コンピュータ記憶媒体
US17/642,740 US11909839B2 (en) 2019-09-16 2020-09-14 Event notification method, system, server device, and computer storage medium
KR1020227012343A KR20220059543A (ko) 2019-09-16 2020-09-14 이벤트 통지 방법, 시스템, 서버 디바이스, 및 컴퓨터 저장 매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910872383.4A CN112511579A (zh) 2019-09-16 2019-09-16 事件通知方法、系统，服务器设备、计算机存储介质
CN201910872383.4 2019-09-16

Publications (1)

Publication Number Publication Date
WO2021052289A1 true WO2021052289A1 (zh) 2021-03-25

Family

ID=74884463

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/115074 WO2021052289A1 (zh) 2019-09-16 2020-09-14 事件通知方法、系统、服务器设备、计算机存储介质

Country Status (6)

Country Link
US (1) US11909839B2 (zh)
EP (1) EP4033722A4 (zh)
JP (1) JP2022547726A (zh)
KR (1) KR20220059543A (zh)
CN (1) CN112511579A (zh)
WO (1) WO2021052289A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102687134A (zh) * 2009-12-29 2012-09-19 摩托罗拉解决方案公司 用于基于事件序列的呈现通知的方法
WO2015117417A1 (zh) * 2014-08-19 2015-08-13 中兴通讯股份有限公司 一种定制事件通知的方法、服务器和系统
CN107770754A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种通知发送方法、装置和系统
CN107968805A (zh) * 2016-10-20 2018-04-27 华为技术有限公司 一种事件通知方法及服务器
WO2018205532A1 (zh) * 2017-05-12 2018-11-15 京东方科技集团股份有限公司 生成和订阅通知的方法和装置

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030046395A1 (en) 2000-12-12 2003-03-06 Robert Fleming System and method for bounding the life of an event subscription to the availability of an object
JP5068435B2 (ja) * 2005-07-15 2012-11-07 日本電気株式会社 情報交換システム、管理サーバ及びそれらに用いるネットワーク負荷軽減方法並びにそのプログラム
CN100531056C (zh) * 2006-04-11 2009-08-19 中国移动通信集团公司 信息家电的数据存储系统及数据处理方法
CN101159711B (zh) 2007-11-27 2010-06-02 航天东方红卫星有限公司 自适应的实时消息订阅与发布系统及方法
US8296376B2 (en) * 2009-03-26 2012-10-23 International Business Machines Corporation Utilizing E-mail response time statistics for more efficient and effective user communication
JP2011053793A (ja) * 2009-08-31 2011-03-17 Toshiba Tec Corp 商品情報管理装置及びプログラム
CN102523137B (zh) * 2011-12-22 2014-10-08 华为技术服务有限公司 一种故障监测方法、装置及系统
US10476758B2 (en) 2013-07-11 2019-11-12 Google Llc Systems and methods for providing notifications of changes in a cloud-based file system
US9082282B1 (en) * 2014-01-28 2015-07-14 Domo, Inc. Determining usefulness of a data alert
CN105101412A (zh) * 2014-05-21 2015-11-25 中兴通讯股份有限公司 通知消息的发送方法及装置
US9576466B2 (en) 2014-11-04 2017-02-21 Canary Connect, Inc. Backup contact for security/safety monitoring system
WO2016114698A1 (en) * 2015-01-16 2016-07-21 Telefonaktiebolaget Lm Ericsson (Publ) A wireless communication device, a core network node and methods therein, for extended drx paging cycle
US10568034B2 (en) * 2016-01-23 2020-02-18 Blustream Corporation Intelligent power management for monitoring a movable object
KR102615419B1 (ko) * 2016-07-14 2023-12-20 콘비다 와이어리스, 엘엘씨 가입 및 통지 서비스
CN113159910A (zh) * 2016-07-29 2021-07-23 京东方科技集团股份有限公司 进行通知的方法、装置和系统
CN107698805A (zh) 2016-08-09 2018-02-16 丁玉琴 一种退热贴用复合水凝胶膜的制备方法
CN106683331A (zh) 2017-03-14 2017-05-17 北京小米移动软件有限公司 家庭安全监控方法和装置
EP3759954A4 (en) 2018-04-06 2021-03-31 Samsung Electronics Co., Ltd. METHOD AND APPARATUS FOR PROVIDING A TERMINAL MOBILITY EVENT NOTIFICATION SERVICE IN A WIRELESS COMMUNICATIONS SYSTEM
US10866844B2 (en) 2018-05-04 2020-12-15 Microsoft Technology Licensing, Llc Event domains
CN111262893B (zh) * 2018-11-30 2022-11-18 京东方科技集团股份有限公司 用于事件通知的方法、服务器设备、事件通知装置、介质
US10972368B2 (en) * 2019-05-17 2021-04-06 Oracle International Corporation Methods, systems, and computer readable media for providing reduced signaling internet of things (IoT) device monitoring

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102687134A (zh) * 2009-12-29 2012-09-19 摩托罗拉解决方案公司 用于基于事件序列的呈现通知的方法
WO2015117417A1 (zh) * 2014-08-19 2015-08-13 中兴通讯股份有限公司 一种定制事件通知的方法、服务器和系统
CN107968805A (zh) * 2016-10-20 2018-04-27 华为技术有限公司 一种事件通知方法及服务器
WO2018205532A1 (zh) * 2017-05-12 2018-11-15 京东方科技集团股份有限公司 生成和订阅通知的方法和装置
CN107770754A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种通知发送方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4033722A4

Also Published As

Publication number Publication date
EP4033722A4 (en) 2023-09-27
US20220329669A1 (en) 2022-10-13
JP2022547726A (ja) 2022-11-15
KR20220059543A (ko) 2022-05-10
CN112511579A (zh) 2021-03-16
EP4033722A1 (en) 2022-07-27
US11909839B2 (en) 2024-02-20

Similar Documents

Publication Publication Date Title
US10313455B2 (en) Data streaming service for an internet-of-things platform
EP3493485B1 (en) Method, apparatus and system for notification
KR101871383B1 (ko) 계층적 데이터 구조의 노드 상에서 재귀적 이벤트 리스너를 사용하기 위한 방법 및 시스템
CN106230997B (zh) 一种资源调度方法和装置
US20180262581A1 (en) State Information For a Service
EP3255849A1 (en) Multi-channel communications for sending push notifications to mobile devices
WO2016065842A1 (zh) M2m群组及其通告资源创建、信息交互方法和存储介质
WO2019237531A1 (zh) 一种网络节点的监测方法与系统
CN111897659B (zh) 业务处理频率的控制方法、系统、装置、电子设备
KR101570933B1 (ko) 데이터분산서비스에서 동적 블룸 필터를 이용한 노드 탐색 시스템 및 방법
WO2021052289A1 (zh) 事件通知方法、系统、服务器设备、计算机存储介质
CN111400045B (zh) 一种负载均衡方法及装置
WO2007059667A1 (fr) Procede d'obtention de donnees d'alarme des elements de reseau
WO2021143834A1 (zh) 群组更新方法、消息发送方法及装置
WO2017206634A1 (zh) 一种语义查询的方法及装置
CN113835905A (zh) 一种消息队列负载均衡方法、装置、电子设备及介质
WO2019179387A1 (zh) 数据处理方法及系统
CN115967564B (zh) 一种数据内容防护方法和存储介质
US11553050B2 (en) Event notification method and device, apparatus and computer storage medium
US11973838B2 (en) Devices and methods for managing subscriptions of subscribers
US20230164232A1 (en) Event notification method, server device, apparatus and computer storage medium
WO2021092724A1 (zh) 设备管理的方法和ble设备
CN113765711A (zh) 一种网络设备保活方法及装置
CN117040794A (zh) 基于sql的通信交互方法、装置、通信节点及可读介质
JP2023119832A (ja) ネットワーク管理システム及び方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20866007

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022516700

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227012343

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020866007

Country of ref document: EP

Effective date: 20220419