Event notification method, system, server device, and computer storage medium

Patent metadata

Field	Value
Publication number	US-11909839-B2
Application number	US-202017642740-A
Country	US
Kind code	B2
Filing date	Sep 14, 2020
Priority date	Sep 16, 2019
Publication date	Feb 20, 2024
Grant date	Feb 20, 2024

Abstract

The present disclosure provides an event notification method, a system, a server device, and a computer storage medium. The event notification method includes: receiving a subscription request from a subscriber, the subscription request includes at least one receiver for receiving event notifications; during a monitoring interval, determining whether a continuous event notification rule is satisfied; and in the case where the continuous event notification rule is satisfied, sending the event notification of the subscription request to the at least one receiver.

First claim

What is claimed is:

1. An event notification method, comprising:
receiving a subscription request from a subscriber, wherein the subscription request comprises at least one receiver used for receiving an event notification;
determining whether a continuous event notification rule is satisfied during a monitoring time interval; and
transmitting the event notification for the subscription request to the at least one receiver in a case that the continuous event notification rule is satisfied,
wherein determining whether the continuous event notification rule is satisfied comprises:
in a case that it is determined that an event notification rule is satisfied, for at least one pieces of monitored data acquired during the monitoring time interval, determining whether a monitored data rule is satisfied and obtaining monitored results, and
determining whether the continuous event notification rule is satisfied based on the monitored results,
wherein, a start time point and an end time point of the monitoring time interval are determined by one of:
determining a time point when the event notification rule is satisfied as the start time point, and determining the end time point based on the monitoring time interval and the determined start time point; or
determining a time point when the event notification rule is satisfied is determined as the end time point, and determining the start time point based on the monitoring time interval and the determined end time point; or
determining a time point when the event notification rule is satisfied is determined as an intermediate time point, and determining the start time point and the end time point based on the monitoring time interval and the determined intermediate time point, and the intermediate time point is between the start time point and the end time point.

2. The event notification method of claim 1 , wherein the event notification rule comprises at least one of the following: updating an attribute of a subscribed resource; creating a sub-resource of the subscribed resource; deleting the sub-resource of the subscribed resource; acquiring a content instance sub-resource of a subscribed container resource; receiving an operation request from a certain requester; and receiving a request for a certain type of operations, and
the monitored data rule comprises any one of the following: a value of a piece of monitored data being greater than a monitoring threshold; the value of the piece of monitored data being equal to the monitoring threshold; the value of the piece of monitored data being less than the monitoring threshold; the value of the piece of monitored data being not less than the monitoring threshold; and the value of the piece of monitored data being not greater than the monitoring threshold.

3. The event notification method of claim 1 , wherein determining whether the monitored data rule is satisfied and obtaining the monitored results comprises:
for each piece of monitored data of the at least one piece of monitored data, determining whether the piece of monitored data satisfies the monitored data rule,
obtaining a monitored result that the monitored data rule is satisfied in a case that the piece of monitored data satisfies the monitored data rule; and obtaining the monitored result that the monitored data rule is not satisfied in a case that the piece of monitored data does not satisfy the monitored data rule.

4. The event notification method of claim 3 , wherein determining whether the continuous event notification rule is satisfied comprises:
determining a number of monitored results that the monitored data rule is satisfied; and
determining the continuous event notification rule is satisfied in a case where the number of monitored results that the monitored data rule is satisfied is not less than a counting threshold, wherein the counting threshold is determined based on a number of pieces of monitored data received during the monitoring time interval.

5. The event notification method of claim 3 , wherein determining whether the continuous event notification rule is satisfied comprises:
determining a time length corresponding to the monitored results that the monitored data rule is satisfied;
determining the continuous event notification rule is satisfied in a case where a ratio of the time length to the monitoring time interval is not less than a time threshold, wherein the time threshold is less than or equal to 1.

6. The event notification method of claim 1 , wherein the subscription request further comprises the monitoring time interval, and the event notification method further comprises: creating a subscription resource, wherein the subscription resource comprises the following attributes:
a monitoring time interval attribute, used for determining the monitoring time interval;
a continuous event notification rule attribute, used for determining whether to transmit the event notification to the at least one receiver; and
an event notification list attribute, used for storing address information for the at least one receiver.

7. A non-transitory computer storage medium stored with computer readable code, when executed by one or more processors, causing the one or more processors to perform the event notification method of claim 1 .

8. A server device, comprising a transceiver and a processor,
wherein the transceiver is configured to receive a subscription request from a subscriber, and the subscription request comprises at least one receiver used for receiving an event notification;
the processor is configured to determine whether a continuous event notification rule is satisfied during a monitoring time interval; and
the transceiver is further configured to transmit the event notification for the subscription request to the at least one receiver in a case where the continuous event notification rule is satisfied,
wherein when determining whether the continuous event notification rule is satisfied, the processor is configured to:
in a case that it is determined that an event notification rule is satisfied, for at least one pieces of monitored data acquired during the monitoring time interval, determine whether a monitored data rule is satisfied and obtaining monitored results, and
determine whether the continuous event notification rule is satisfied based on the monitored results,
wherein, a start time point and an end time point of the monitoring time interval are determined by one of:
determining a time point when the event notification rule is satisfied as the start time point, and determining the end time point based on the monitoring time interval and the determined start time point; or
determining a time point when the event notification rule is satisfied is determined as the end time point, and determining the start time point based on the monitoring time interval and the determined end time point; or
determining a time point when the event notification rule is satisfied is determined as an intermediate time point, and determining the start time point and the end time point based on the monitoring time interval and the determined intermediate time point, and the intermediate time point is between the start time point and the end time point.

9. The server device of claim 8 , wherein
when determining whether the monitored data rule is satisfied and obtaining the monitored results, the processor is configured to:
for each piece of monitored data of the at least one piece of monitored data, determining whether the piece of monitored data satisfies the monitored data rule,
obtaining a monitored result that the monitored data rule is satisfied in a case that the piece of monitored data satisfies the monitored data rule; and obtaining the m

Assignees

• Beijing Boe Technology Dev Co Ltd
• Boe Technology Group Co Ltd

Inventors

• Zhao Junjie
• Su Jing
• Wang Xinan
• Chen Shaobei
• Zhang Qian
• Zhao Yanqiu

Classifications

• H04L67/125

  involving control of end-device applications over a network · CPC title

• H04L67/55 Primary

  Push-based network services · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• 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 (admission control or resource allocation H04L47/70) · CPC title

• H04L67/12 Primary

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title