Event notification method, device, apparatus and computer storage medium
The event notification method in IoT platforms addresses the issue of simultaneous notifications by grouping notifiers and using interval-based criteria, improving efficiency and reducing interference.
Patent Information
- Application Number
- JP2021530220
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-11-28
- Filing Date
- 2019-11-21
- Publication Date
- 2024-11-11
- Estimated Expiration
- 2039-11-21
AI Technical Summary
Existing event notification methods in the Internet of Things (IoT) platforms fail to accommodate varying notification preferences of different levels of management centers, leading to simultaneous notifications that cause information interference and resource wastage.
An event notification method that groups notifiers based on their preferences and criteria, allowing for differentiated timing of notifications through verification and transmission intervals, ensuring timely and efficient delivery.
The method enhances notification efficiency by avoiding simultaneous notifications, reducing information interference, and optimizing resource utilization among different levels of management centers.
Smart Images

Figure 0007580376000001 
Figure 0007580376000002 
Figure 0007580376000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to the field of Internet of Things, and in particular to an event notification method, device, apparatus, and computer storage medium. [Background technology]
[0002] With the development of information technology, especially Internet technology, Internet of Things technology is becoming mature to realize informatization, remote management control, and intelligentization. Internet of Things uses communication technologies such as local networks and the Internet to connect sensors, controllers, machines, people, objects, etc. in a new way, forming connections between people and objects, and between objects and objects. As Internet of Things technology develops rapidly in each application field, more and more devices are connected to the Internet of Things, and various new application fields such as smart home, smart transportation, smart health, etc. are emerging. A device terminal connected to the Internet of Things platform can subscribe to data related to it by sending a subscription request to the Internet of Things platform, and the Internet of Things platform sends an event notification to a notifier related to the subscription request when the subscription condition is met. Summary of the Invention
[0003] According to one aspect of the present disclosure, there is provided an event notification method including receiving an event subscription request from a subscriber, where the event subscription request includes one or more notifiers; dividing the one or more notifiers into one or more groups, where each group includes one or more notifiers; and sending an event notification to notifiers in at least one of the one or more groups.
[0004] According to an embodiment of the present disclosure, sending an event notification to a notifier in at least one of the one or more groups includes determining whether an event notification rule is satisfied, and if the event notification rule is satisfied, sending the event notification to a notifier in at least one of the one or more groups.
[0005] According to an embodiment of the present disclosure, sending an event notification to a notifier in at least one of the one or more groups further includes: after sending the event notification, determining whether a re-notification criterion is met, and if the re-notification criterion is met, sending the event notification to a notifier in at least one of the one or more groups.
[0006] According to an embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a verification event notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0007] According to an embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a transmission notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0008] According to an embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining that the re-notification criterion is met at a time determined by a transmission notification interval.
[0009] According to an embodiment of the present disclosure, the method further includes setting a transmission notification interval and a verification event notification interval, wherein the transmission notification interval is greater than the verification event notification interval; and determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by the verification event notification interval, and if the event notification rule is met, waiting for a transmission event notification, determining that the re-notification criterion is met at a time determined by the transmission notification interval, and sending an event notification to a notifier in at least one of the one or more groups.
[0010] According to an embodiment of the present disclosure, the method further includes setting a transmission notification interval and a verification event notification interval, wherein the transmission notification interval is smaller than the verification event notification interval, and determining whether the re-notification criterion is met includes determining that the re-notification criterion is met at a time determined by the transmission notification interval.
[0011] According to an embodiment of the present disclosure, the event notification method further includes: determining whether an event notification rule is satisfied at a time determined by the verification event notification interval; if the event notification rule is satisfied, waiting for a sending event notification; and sending the event notification to a notifier in at least one of the one or more groups at a time determined by the sending notification interval.
[0012] According to an embodiment of the present disclosure, the method includes defining at least one of an event notification rule attribute for determining whether to send an event notification to a notifier, and an event notification list attribute for storing address information of the one or more notifiers based on the one or more groups.
[0013] According to an embodiment of the present disclosure, the event notification method further includes defining a validation event notification interval attribute for setting a time interval for determining whether an event notification rule is satisfied.
[0014] According to an embodiment of the present disclosure, the event notification method further includes defining a sending notification interval attribute for setting a time interval for sending the event notification.
[0015] According to an embodiment of the present disclosure, the event notification method further includes defining a validation event notification enable attribute for setting whether the validation event notification interval attribute is enabled.
[0016] According to an embodiment of the present disclosure, the event subscription request is used to request to receive update data from an application entity.
[0017] According to an embodiment of the present disclosure, the event notification method further includes determining whether an event notification rule is satisfied based on the update data.
[0018] According to an embodiment of the present disclosure, a group to which an event notification is sent if the event notification rules are met is represented as an initial notification group, and a group to which an event notification is sent if the re-notification criteria are met is represented as a re-notification group, and the initial notification group and the re-notification group are different.
[0019] According to an embodiment of the present disclosure, sending an event notification to notifiers in at least one of the one or more groups further includes determining the at least one group to which the event notification should be sent based on an order of the one or more groups.
[0020] According to an embodiment of the present disclosure, sending an event notification to a notifier in at least one of the one or more groups includes determining whether an event notification rule is satisfied, and if the event notification rule is satisfied, determining whether a re-notification criterion is satisfied, and if the re-notification criterion is satisfied, sending the event notification to a notifier in at least one of the one or more groups.
[0021] According to an embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a verification event notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0022] According to an embodiment of the present disclosure, the event subscription request is at least one of a single-resource subscription request and a cross-resource subscription request.
[0023] According to another aspect of the present disclosure, there is provided a server device comprising a transceiver and a processor, wherein the transceiver is configured to receive an event subscription request from a subscriber, the event subscription request including one or more notifiers, and the processor is configured to divide the one or more notifiers into one or more groups, each group including one or more notifiers, and to instruct the transceiver to send an event notification to notifiers in at least one of the one or more groups.
[0024] According to an embodiment of the present disclosure, the processor is further configured to determine whether an event notification rule is satisfied, and if the event notification rule is satisfied, instruct the transceiver to send an event notification to notifiers in at least one of the one or more groups. According to an embodiment of the present disclosure, after instructing the transceiver to send an event notification to notifiers in at least one of the one or more groups, the processor is further configured to determine whether a re-notification criterion is satisfied, and if the re-notification criterion is satisfied, instruct the transceiver to send an event notification to notifiers in at least one of the one or more groups, wherein a group to which an event notification is sent if the event notification rule is satisfied is referred to as an initial notification group, and a group to which an event notification is sent if the re-notification criterion is satisfied is referred to as a re-notification group, and the initial notification group and the re-notification group are different.
[0025] According to another aspect of the present disclosure, there is provided an event notification device comprising one or more processors and one or more memories storing computer readable code, which, when executed by the one or more processors, performs an event notification method as described above.
[0026] According to another aspect of the present disclosure, there is provided a computer storage medium having computer readable code stored thereon, the computer readable code, when executed by one or more processors, causing an event notification method as described above to be performed.
[0027] In order to more clearly describe the embodiments of the present disclosure or the technical solutions of the prior art, the drawings required in the description of the embodiments or the prior art are briefly described below. However, the drawings in the following description are only a part of the embodiments of the present disclosure, and it is obvious to those skilled in the art that they can obtain other drawings based on these drawings without exerting creative efforts. [Brief description of the drawings]
[0028] [Figure 1] 1 is a flowchart of an event notification method according to an embodiment of the present disclosure. [Diagram 2] 1 is a flowchart of sending an event notification according to one embodiment of the present disclosure. [Figure 3A] FIG. 13 is a schematic diagram of setting a transmission notification interval to be greater than a validation event notification interval, according to an embodiment of the present disclosure. [Figure 3B] FIG. 13 is a schematic diagram of setting a transmission notification interval to be smaller than a validation event notification interval according to an embodiment of the present disclosure. [Figure 4A] FIG. 2 is a schematic diagram of a subscription resource configuration for implementing an event notification method according to one embodiment of the present disclosure. [Figure 4B] FIG. 4B is another schematic diagram of the subscription resource configuration shown in FIG. 4A. [Diagram 5] 4C is a flowchart of an event notification method corresponding to the subscription resource configuration shown in FIG. 4A and FIG. 4B. [Figure 6A] FIG. 13 is a schematic diagram of a subscription resource configuration for implementing an event notification method according to another embodiment of the present disclosure. [Figure 6B] FIG. 6B is another schematic diagram of the subscription resource configuration shown in FIG. 6A. [Figure 7] 6C is a flowchart of an event notification method corresponding to the subscription resource configuration shown in FIGS. 6A and 6B. [Figure 8A] FIG. 13 is a schematic diagram of a subscription resource configuration for implementing an event notification method according to another embodiment of the present disclosure. [Figure 8B] FIG. 8B is another schematic diagram of the subscription resource configuration shown in FIG. 8A. [Figure 9A] 8C is a flowchart of an event notification method corresponding to the subscription resource configuration shown in FIG. 8A and FIG. 8B. [Figure 9B] 8C is another flowchart of an event notification method corresponding to the subscription resource configuration shown in FIGS. 8A and 8B. [Figure 10A] 11 is a flowchart of sending an event notification to one notifier in a fourth group according to an embodiment of the present disclosure. [Figure 10B] 11 is a flowchart of sending an event notification to multiple notifiers in a fifth group according to an embodiment of the present disclosure. [Figure 11] 4 is a flowchart of a cross-resource subscription in an event notification method according to an embodiment of the present disclosure. [Figure 12] FIG. 2 is a schematic diagram of a server device according to an embodiment of the present disclosure. [Figure 13] FIG. 1 is a schematic diagram of an event notification device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] Hereinafter, the technical solutions in the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure. Of course, the described embodiments are only some embodiments of the present disclosure, and are not all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative efforts belong to the protection scope of the present disclosure.
[0030] As used in this disclosure, "first," "second," and similar words do not imply any order, quantity, or importance, but are only used to distinguish different components. Similarly, similar words such as "include" or "comprise" mean that the element or object appearing before the word encompasses the element or object appearing after the word and its equivalents, and does not exclude other elements or objects. Terms such as "coupled" or "connected" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect.
[0031] In the present disclosure, flow charts are used to describe steps of methods according to embodiments of the present disclosure. It is to be noted that the steps do not necessarily have to be performed in exact order. Conversely, various steps may be processed in reverse order or simultaneously. It is also possible to add other operations to these procedures or to remove certain steps.
[0032] As an extension of the Internet, the Internet of Things includes the Internet and all resources on the Internet, and supports all applications of the Internet. As the Internet of Things technology is applied in various fields, various new application fields such as smart home, smart transportation, smart health, etc. are emerging.
[0033] With the development of Internet of Things technology, more and more terminal devices, such as smoke alarms, fire alarms, manhole cover movement sensors, etc., connect to the Internet of Things platform. The Internet of Things platform may be embodied as a generic service entity, for example, and the terminal device may connect to the generic service entity by sending registration information to the generic service entity, and the generic service entity manages the terminal device that accesses it. The terminal device is represented as an application entity, and the application entity that accesses the generic service entity can perform operations such as data transmission and information exchange with the generic service entity. Note that the application entity described in this document may be a terminal device of the Internet of Things, or a software module in the device, etc.
[0034] Some application entities (e.g., as subscribers) can subscribe to, for example, information, data, etc. from other application entities (e.g., as subscribed parties) by sending a subscription request to the generic service entity, and the subscriber can request, for example, data, operations, etc. from the generic service entity, without any limitation thereto. The subscription request can include multiple notifiers for receiving event notifications related thereto. The subscription request can further include an event notification rule, i.e., if the event notification rule is satisfied (e.g., a smoke alarm is triggered), an event notification is sent to the notifiers included in the subscription request, and the event notification rule can be referred to as a subscription condition. Thus, if the event notification rule is satisfied, the generic service entity sends the event notification to all notifiers included in the subscription request. For example, when the manhole cover is moved, the manhole cover movement sensor detects this change and sends update data to the general-purpose service entity, and the general-purpose service entity can determine whether the event notification rule is satisfied based on the update data of the manhole cover movement sensor. For example, if the subscription condition is the movement of the manhole cover, then the general-purpose service entity determines that the event notification rule is satisfied and sends an event notification to all notifiers included in the subscription request requesting subscription to the event notification of the manhole cover movement, that is, notifies all notifiers of the event that the manhole cover has been moved.
[0035] In the existing subscription request notification rule, when the subscription condition is satisfied, the general-purpose service entity sends the event notification to all notifiers. However, in some scenarios, not all notifiers may want to receive the event notification at the same time. For example, in the subscription request of the above manhole cover movement, the notifiers may include different levels of municipal management departments, such as a street manhole cover management center, an area manhole cover management center, a ward manhole cover management center, and a city manhole cover management center. These different levels of manhole cover management centers want to receive the event notification related to the manhole cover movement, but on the other hand, they do not want to receive all the event notifications at the same time. For example, the notifier, which is a lower management center, may process the event of the manhole cover movement in a timely manner after receiving the event notification, and the notifier, which is a higher management center, may monitor and manage the processing of the event of the manhole cover movement. In this case, the upper management center needs to receive the event notification only when the lower management center does not process the manhole cover movement event in a timely manner, and the event notification rules of the conventional technology cannot meet the application requirements in such a case. Also, if the event notification is sent to all notified parties at the same time, information interference occurs for the notifiers, resulting in a waste of resources.
[0036] The present disclosure proposes an event notification method for managing notifiers in subscription requests, realizing accurate transmission of event notifications, improving notification efficiency, and avoiding information interference to notifiers.
[0037] 1 shows a flowchart of an event notification method in an embodiment of the present disclosure. First, in step S101, an event subscription request is received from a subscriber, where the event subscription request includes one or more notifiers. The subscriber may be an application entity connected to a generic service entity, for example, when some data is needed to operate, it can send a subscription request to the service entity, and the subscription request may include an event or operation to subscribe to and one or more notifiers to receive the event notification. Note that the subscriber may be one or more, that is, multiple subscribers may send event subscription requests to the generic service entity to subscribe to event notifications.
[0038] Next, in step S102, one or more notifiers are divided into one or more groups, where each group includes one or more notifiers. According to an embodiment of the present disclosure, when the event subscription request includes multiple notifiers, the generic service entity can obtain list information of all notifiers after receiving the subscription request, and group the multiple notifiers based on the type, level, content of the event notification, etc. of the notifiers, so as to send the event notification more accurately. According to another embodiment of the present disclosure, the generic service entity can also group the multiple notifiers based on the instruction of the subscriber. Alternatively, the generic service entity can group the notifiers based on other methods that are more advantageous to improving the event notification efficiency. It should be noted that the present disclosure does not limit the grouping method. The case where the event subscription request includes one notifier will be described in detail with reference to an embodiment.
[0039] According to an embodiment of the present disclosure, the general-purpose service entity may distinguish the plurality of groups in the notifier list. For example, the plurality of groups may be divided into a first group, a second group, a third group, etc., and a group that currently needs to be notified may be determined when performing an event notification, and the event notification may be performed to a notifier in the determined group. According to an embodiment of the present disclosure, the at least one group to which the event notification is sent may be determined based on the order of the plurality of groups. Hereinafter, different groups may be represented as a first group, a second group, a third group, etc. Note that the first and second here are merely for distinguishing different groups, and do not mean the order of event notification for the groups. That is, when performing an event notification, the general-purpose service entity may first determine to send the event notification to a notifier in the first group, or may determine to send the event notification to a notifier in the second group or another group, for example, a third group. Furthermore, according to the embodiments of the present disclosure, the notifiers included in the different groups may or may not be identical, i.e., one notifier may be included in a first group and one notifier may be included in a second group, and is not limited thereto.
[0040] Next, in step S103, the event notification is sent to the notifiers in at least one of the one or more groups. According to an embodiment of the present disclosure, the general-purpose service entity first determines whether the event notification rule is satisfied. certain If an event notification rule is met, an event notification can be sent to at least one notifier in the group.
[0041] FIG. 2 shows a flowchart for sending an event notification according to an embodiment of the present disclosure. According to the embodiment of the present disclosure, sending the event notification to notifiers of at least one group of one or more groups may include the step S201 of determining whether an event notification rule is satisfied, and sending the event notification to notifiers in at least one group of the one or more groups if the event notification rule is satisfied. The event notification rule may be determined by a subscriber sending a subscription request. A general service entity may create an event notification rule attribute and set the event notification rule based on the subscription request, and store address information of the multiple subscribers based on the one or more groups by creating the event notification rule attribute.
[0042] For example, in one example according to the present disclosure, the event subscription request may be used to request receiving notification of update data from application entity 1 and set an event notification rule for receiving the notification, for example, the update data is greater than a first threshold. After receiving the subscription request, the generic service entity may generate an event notification rule attribute and an event notification list attribute corresponding to the subscription request. After receiving the update data from application entity 1, the generic service entity determines whether the update data satisfies the event notification rule, and if the event notification rule is satisfied (i.e., the update data is greater than a first threshold), sends the update data or update information related to the update data to notifiers in at least one of the one or more groups stored in the event notification list attribute.
[0043] According to an embodiment of the present disclosure, sending an event notification to a notifier in at least one of the one or more groups may further include a step S202 of determining whether a re-notification criterion is met after sending the event notification, and sending the event notification to a notifier in at least one of the one or more groups if the re-notification criterion is met. According to an embodiment of the present disclosure, a group that sends an event notification when an event notification rule is met (step S201) is represented as an initial notification group, and a group that sends an event notification when a re-notification criterion is met (step S202) is represented as a re-notification group, and the initial notification group is different from the re-notification group. According to another embodiment of the present disclosure, the initial notification group and the re-notification group may be the same or may be partially the same.
[0044] For example, in the above example of receiving a subscription request for update data, after receiving the update data of the application entity 1, the general-purpose service entity determines that the update data meets the event notification rule, and sends the event notification to the notifiers in the initial notification group (e.g., the first group). After sending the event notification, the general-purpose service entity further determines whether the re-notification criteria are met, and if the re-notification criteria are met, sends the event notification to the notifiers in the re-notification group (e.g., the second group).
[0045] According to an embodiment of the present disclosure, in step S202, before determining whether the re-notification criteria are met, the step may include determining whether there are any notifiers who have not sent an event notification, and determining whether the re-notification criteria are met if there are any notifiers who have not sent an event notification.
[0046] The re-notification criteria will now be described in detail.
[0047] According to an embodiment of the present disclosure, determining whether the re-notification criterion is satisfied may include determining whether an event notification rule is satisfied at a time determined by a verification event notification interval, and determining that the re-notification criterion is satisfied if the event notification rule is satisfied. For example, the generic service entity can set a time interval for determining whether the event notification rule is satisfied by creating a verification event notification interval attribute. For example, the verification event notification interval attribute is determined as a verification event notification interval of 4 hours, that is, the generic service entity performs verification of whether the event notification rule is satisfied every 4 hours after sending an event notification (e.g., after sending an event notification to a notifier in a first group). In this embodiment, determining whether the event notification rule is satisfied at a time determined by the verification event notification interval may be a re-notification criterion. If the event notification rule is satisfied, i.e., if it is determined that the re-notification criterion is satisfied, send an event notification to a notifier in at least one of the one or more groups (e.g., a notifier in a second group).
[0048] According to another embodiment of the present disclosure, determining whether the re-notification criterion is satisfied may include determining whether an event notification rule is satisfied at a time determined by a sending notification interval, and determining that the re-notification criterion is satisfied if the event notification rule is satisfied. For example, the generic service entity can set a time interval for sending an event notification by creating a sending notification interval attribute. For example, the sending notification interval attribute is determined as a sending notification interval of 5 hours, that is, the generic service entity performs verification of whether the event notification rule is satisfied every 5 hours after sending an event notification (e.g., after sending an event notification to a notifier in a first group), and sends an event if the event notification rule is satisfied. In this embodiment, determining whether the event notification rule is satisfied at a time determined by a sending event notification interval may be a re-notification criterion. If the generic service entity determines that the event notification rule is satisfied at a time determined by a sending event notification interval, that is, if the re-notification criterion is satisfied, it sends an event notification to a notifier in at least one of the one or more groups (e.g., a notifier in a second group).
[0049] According to another embodiment of the present disclosure, it is determined that the re-notification criterion is satisfied at a time determined by the sending notification interval. That is, in this embodiment, the condition for satisfying the re-notification criterion is to reach a time determined by the sending notification time interval. For example, the generic service entity can set a time interval for sending an event notification by creating a sending notification interval attribute. For example, the sending notification interval attribute determines the sending notification interval as 4 hours, that is, the generic service entity triggers a sending operation of the event notification (e.g., sending to the notifiers in the second group) every 4 hours after sending the event notification (e.g., after sending the event notification to the notifiers in the first group). That is, when the generic service entity determines that the re-notification criterion is satisfied at a time determined by the sending event notification interval, it sends the event notification to the notifiers in at least one of the one or more groups (e.g., the notifiers in the second group).
[0050] According to another embodiment of the present disclosure, the event notification method may include setting a sending notification interval and a verification event notification interval, where the sending notification interval is greater than the verification event notification interval. In this embodiment, determining whether the re-notification criterion is met may include determining whether an event notification rule is met at a time determined by the verification event notification interval, and if the event notification rule is met, waiting for a sending event notification, determining that the re-notification criterion is met at a time determined by the sending notification interval, and sending an event notification to notifiers in at least one of the one or more groups.
[0051] Fig. 3A is a schematic diagram of setting a sending notification interval greater than a verification event notification interval in an embodiment of the present disclosure. Hereinafter, the procedure of determining a re-notification criterion in this embodiment will be described with reference to Fig. 3A. Note that in the specific embodiment shown in Fig. 3A, the event subscription request includes multiple notifiers, and the multiple notifiers are divided into one or more groups.
[0052] For example, the generic service entity can set a time interval for sending an event notification by creating a sending notification interval attribute. For example, the sending notification interval attribute may be determined to be 5 hours. The generic service entity can set a time interval for verifying an event notification by creating a verification event notification interval attribute. For example, the verification event notification interval attribute may be determined to be 4 hours. That is, the sending notification interval is set to be greater than the verification event notification interval.
[0053] 3A indicates a time axis, and for example, the time when the general-purpose service entity sends an event notification to a notifier in an initial notification group can be represented as the starting point of the time axis, whereby the general-purpose service entity sets a time every four hours from the starting point as the time for verifying whether the event notification rule is satisfied, and sets a time every five hours from the starting point as the time for sending the event notification.
[0054] In this embodiment, as shown in FIG. 3A, since the sending notification interval is greater than the verification event notification interval, the generic service entity first reaches the verification event notification time after sending the event notification (i.e., the start point of the time axis) and determines whether the event notification rule is satisfied; if the event notification rule is not satisfied, for example, if the update data is less than or equal to the first threshold, the generic service entity terminates the operation of this event notification. If the generic service entity determines that the event notification rule is satisfied, for example, if the update data is greater than the first threshold, the generic service entity waits for the sending event notification, i.e., does not send the event notification at this verification event notification time (for example, 4 hours), and when the time determined by the sending notification interval (for example, 5 hours) is reached, the generic service entity sends the event notification to notifiers in at least one group (for example, re-notification group) of the multiple groups. As described above, the generic service entity determines the re-notification group in the order of the groups or in other manners, and further, the re-notification group may be different from the initial notification group, and the description is omitted here.
[0055] 3A, the general-purpose service entity waits until the next verification event notification time (e.g., 8 hours) and determines whether the event notification rule is satisfied at that time, and if the event notification rule is satisfied, sends the event notification to notifiers in at least one group (e.g., another re-notification group) of the plurality of groups at the next event notification sending time (e.g., 10 hours), and thus infers. In the embodiment of the present disclosure, the other re-notification group may be different from the re-notification group or the initial notification group.
[0056] According to another embodiment of the present disclosure, the event notification method may further include setting a verification event notification interval and a transmission notification interval, where the transmission notification interval is smaller than the verification event notification interval. In this embodiment, determining whether the re-notification criterion is met may include determining that the re-notification criterion is met at a time determined by the transmission notification interval. Determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by the verification event notification interval, and if the event notification rule is met, waiting for the transmission event notification, and sending the event notification to a notifier in at least one of the multiple groups at a time determined by the transmission notification interval.
[0057] FIG. 3B is a schematic diagram of setting a sending notification interval smaller than a verification event notification interval in an embodiment of the present disclosure. Hereinafter, the procedure of determining a re-notification criterion in this embodiment will be described with reference to FIG. 3B. In addition, in the specific embodiment shown in FIG. 3B, the event subscription request includes multiple notifiers, and the multiple notifiers are divided into one or more groups.
[0058] For example, the generic service entity creates a transmission notification interval attribute and a validation event notification interval attribute, and sets the transmission notification interval to be smaller than the validation event notification interval. For example, the transmission notification interval attribute is determined to be 5 hours, and the validation event notification interval attribute is determined to be 6 hours. That is, the transmission notification interval is set to be smaller than the validation event notification interval.
[0059] 3B indicates a time axis, and for example, the time when the general-purpose service entity sends an event notification to a notifier in an initial notification group can be represented as the starting point of the time axis, whereby the general-purpose service entity sets a time every six hours from the starting point as a time for verifying whether the event notification rule is satisfied, and sets a time every five hours from the starting point as a time for sending the event notification.
[0060] In this embodiment, as shown in FIG. 3B, since the sending notification interval is smaller than the verification event notification interval, the general-purpose service entity first reaches a sending event notification time (e.g., 5 hours) after sending the event notification (i.e., the start point of the time axis), and the general-purpose service entity determines that the sending event notification time meets the re-notification criterion, and sends the event notification to notifiers in at least one group (e.g., the re-notification group) of the multiple groups. When the verification event notification interval time is reached (e.g., 6 hours), the general-purpose service entity judges whether the event notification rule is met, and if the event notification rule is met, waits for the sending event notification, and when the sending notification time is reached (e.g., 10 hours), sends the event notification to notifiers in at least one group (e.g., another re-notification group) of the multiple groups. In the embodiment according to the present disclosure, the other re-notification group may be different from the re-notification group or the initial notification group.
[0061] According to an embodiment of the present disclosure, when the general-purpose service entity creates a validation event notification interval attribute, it may also create a validation event notification enable attribute for setting whether to enable the validation event notification interval attribute corresponding to the validation event notification interval attribute.
[0062] The event notification method of the present disclosure divides notifiers in a subscription request into groups, performs event notification based on the group rather than sending event notifications to all notifiers in the subscription request at once, and further performs the above event notification process by setting a sending event notification interval and / or a verifying event notification interval, thereby realizing management of notifiers in a subscription request, making the sending of event notifications accurate, improving notification efficiency, and avoiding information interference with notifiers.
[0063] Fig. 4A is a schematic diagram showing a subscription resource configuration for performing an event notification method according to an embodiment of the present disclosure, Fig. 4B is another schematic diagram of the subscription resource configuration shown in Fig. 4A, and Fig. 5 is a flowchart of an event notification method corresponding to the subscription resource configuration shown in Fig. 4A and Fig. 4B. Hereinafter, the event notification method according to the embodiment of the present disclosure and its embodiment will be described in detail with reference to Figs. 4A-4B and 5.
[0064] As shown in FIG. 5, the Internet of Things is composed of a generic service entity (also called a service entity) and a set of application entities, where the application entities may be various sensor devices, user terminals such as mobile phones, software modules in devices, applications on mobile phones, etc. The generic service entity manages the application entities connected thereto, and performs operations such as registration, data transmission, and task execution. For example, as shown in FIG. 5, the service entity receives device registration requests from application entities and subscriber 1 and subscriber 2, thereby establishing associations between the application entities and subscriber 1 and subscriber 2. In the application of a subscription request, the subscribers (e.g., subscriber 1 and subscriber 2) can send an event subscription request including multiple notifiers to the service entity. For example, the subscription request may be used to request to receive update data from the application entities, or may be used to request the service entities to perform certain operation processing, which will not be described here.
[0065] Upon receiving the same subscription request from each of subscriber 1 and subscriber 2, the service entity creates a subscription resource corresponding to the subscription request. For example, the subscription request as shown in FIG. 5 may be used to request an event notification of the movement of a manhole cover, and the subscription requests from subscriber 1 and subscriber 2 may include multiple notifiers, for example, the subscription request from subscriber 1 includes notifier A, notifier B, and notifier C, and the subscription request from subscriber 2 includes notifier D, notifier E, and notifier F. The configuration of the subscription resource may be as shown in FIG. 4A or FIG. 4B. As shown in FIG. 4B, the subscription resource may include an event notification rule attribute, a notifier list attribute, and a verification event notification interval attribute, where the round-cornered boxes in the subscription resource configurations shown in FIG. 4A and FIG. 4B indicate attributes. The subscription resource may include a verification event notification interval enable attribute for determining whether the verification event notification interval attribute is enabled. As shown in FIG. 4A, the subscription resource may include an event notification rule attribute. In addition, the subscription resource may include an event notification resource for sending an event notification, and the rectangular box indicates the resource. The event notification resource may include sub-attributes, such as a notifier list attribute, a validation event notification interval attribute, and a validation event notification interval valid attribute.
[0066] According to an embodiment of the present disclosure, the general-purpose service entity divides the notifiers included in the subscription request into multiple groups, for example, three groups, and stores the information of the notifiers in the notifier list based on the groups. For example, the first group may include notifier A, notifier B, and notifier C, the second group may include notifier D and notifier E, and the third group may include notifier F. According to an embodiment of the present disclosure, in the notifier list, different groups are separated by semicolons, for example, A, B, C; D, E; F.
[0067] In the above embodiment, the application entity in FIG. 5 may be a manhole cover movement sensor that can periodically send an update request to a service entity to update data on whether the detected manhole cover has moved. The service entity receives the update request from the application entity and sends an update response to the application entity, and the application entity sends update data to the service entity based on the update response. After receiving the update data, the service entity can determine whether the update data satisfies an event notification rule, for example, whether an event of manhole cover movement has occurred. If the service entity determines that the update data does not satisfy the event notification rule, for example, an event of manhole cover movement has not occurred, it does not send an event notification to the subscriber. If the service entity determines that the update data satisfies the event notification rule, for example, an event of manhole cover movement has occurred, it sends an event notification 1 to the first group of notifiers in the notifier list (i.e., notifier A, notifier B, and notifier C). Note that the subscriber 1 shown in FIG. 5 includes the notifier A, notifier B, and notifier C. Note that the above subscriber 1 including subscriber A, subscriber B, and subscriber C is merely an example, and in another embodiment, subscriber A, subscriber B, and subscriber C may be devices different from subscriber 1, for example, subscriber 1 is device 1, subscriber A is device 2, subscriber B is device 3, and subscriber C is device 4.
[0068] As shown in FIG. 5, after receiving the event notification 1, the subscriber 1 (including notifier A, notifier B, and notifier C) can send a notification response corresponding to the event notification 1 to the service entity. In the subscription request for the manhole cover moving, the notifier A, notifier B, and notifier C may be devices belonging to a mechanism responsible for the safety management of the manhole cover, and after receiving the event notification of the manhole cover moving, the mechanism responsible for the safety management of the manhole cover can process the event in a timely manner, for example, check the cause of the movement of the manhole cover, and adjust the position of the manhole cover in a timely manner to avoid the occurrence of a dangerous event.
[0069] After sending the event notification 1, the service entity determines whether a re-notification criterion is met, and if the re-notification criterion is met, sends the event notification 2 to notifiers in at least one of the multiple groups, for example, the second group.
[0070] As shown in FIG. 5, the service entity judges again whether the event notification rule is satisfied at the time determined by the verification event notification interval attribute, and determines that the re-notification criterion is satisfied if the event notification rule is satisfied, for example, when the manhole cover is moved. Then, the service entity sends an event notification 2 to notifiers in at least one group of the plurality of groups, where the at least one group may be, for example, a second group, that is, including notifier D and notifier E. For example, notifier D and notifier E may be devices belonging to a mechanism for supervising manhole cover security management. This enables event notifications to be sent to notifiers belonging to different groups according to the manhole cover moving event.
[0071] In this embodiment, after receiving the update data on the manhole cover moving, the service entity first sends an event notification to the first group of notifiers to quickly process the manhole cover moving event. After a time has passed, that is, after reaching a time determined by the verification event notification interval, the service entity judges again whether the event notification rule is satisfied, and if it is determined that the event notification rule of the manhole cover moving is still satisfied, the service entity sends the event notification to the second group of notifiers to monitor the event, and at this time, the second group of notifiers can know that the manhole cover moving event has occurred, and the first group of notifiers does not process the event within the verification event notification interval, thereby achieving the purpose of the mechanism for monitoring the security management of the manhole cover. If the service entity judges that the event notification rule of the manhole cover moving is not satisfied at the time determined by the verification event notification interval, the event notification is not sent. In this case, after the first group of notifiers receives the event notification, it processes the manhole cover moving event, indicating that the manhole cover has been restored. In this case, the notifiers in the second group do not receive the event notification, which is unnecessary information, so there is less information interference with the notifiers in the second group, and less waste of resources in sending event notifications to all notifiers.
[0072] Also, in this embodiment, the service entity groups notifiers based on their responsibilities, although other embodiments according to this disclosure may group them in other ways.
[0073] According to another embodiment of the present disclosure, the service entity may realize the determination of whether the re-notification criterion is met in another manner.
[0074] FIG. 6A is a diagram showing a subscription resource configuration for realizing an event notification method according to another embodiment of the present disclosure, FIG. 6B shows another schematic diagram of the subscription resource configuration shown in FIG. 6A, and FIG. 7 shows a flowchart of an event notification method corresponding to the subscription resource configuration shown in FIG. 6A and FIG. 6B.
[0075] Hereinafter, an event notification method and its embodiment according to an embodiment of the present disclosure will be described in detail with reference to FIGS. 6A-6B and 7. FIG.
[0076] In the above embodiment of the present disclosure, after receiving subscription requests from each of subscriber 1 and subscriber 2, the service entity creates a subscription resource corresponding to the subscription request. The configuration of the subscription resource may be as shown in FIG. 6A or FIG. 6B. The subscription resource may include an event notification rule attribute, a notifier list attribute, and a send event notification interval attribute, as shown in FIG. 6B. Wherein, the send event notification attribute sets a time interval for sending an event notification. As shown in FIG. 6A, the subscription resource may further include an event notification resource for sending an event notification. The notifier list attribute and the send event notification interval attribute are sub-attributes of the event notification resource. The embodiment of the subscription request shown in FIG. 7 is similar to the scheme described in FIG. 5, and therefore will not be described here.
[0077] In the flowchart shown in Fig. 7, the service entity judges whether the re-notification request is satisfied based on the sending event notification interval attribute shown in Fig. 6A and Fig. 6B. The service entity determines whether the event notification rule is satisfied at the time determined by the sending notification interval attribute, and if the event notification rule is satisfied, determines that the re-notification criterion is satisfied, and sends event notification 2 to a second group of notifiers stored in the notifier list, thereby realizing gradual sending of event notifications to different notifiers.
[0078] Fig. 8A is a schematic diagram of a subscription resource configuration for realizing an event notification method according to yet another embodiment of the present disclosure, Fig. 8B is another schematic diagram of the subscription resource configuration shown in Fig. 8A, Fig. 9A is a flowchart of an event notification method corresponding to the subscription resource configuration shown in Fig. 8A and Fig. 8B, and Fig. 9B is yet another flowchart of an event notification method corresponding to the subscription resource configuration shown in Fig. 8A and Fig. 8B. Hereinafter, the event notification method according to the embodiment of the present disclosure and its embodiment will be described in detail with reference to Figs. 8A-8B and Figs. 9A-9B.
[0079] As shown in Fig. 8B, a subscription resource created after the service entity receives a subscription request may include an event notification rule attribute, a notifier list attribute, a validation event notification interval attribute, and a send event notification interval attribute. The subscription resource may also include a validation event notification interval enable attribute for determining whether the validation event notification interval attribute is enabled. As shown in Fig. 8A, the subscription resource may further include an event notification resource for sending an event notification. The notifier list attribute, the validation event notification interval attribute, the send event notification interval attribute, and the validation event notification interval attribute may be sub-attributes of the event notification resource.
[0080] In the above-mentioned embodiment of the present disclosure, the sending event notification interval attribute and the verification event notification interval attribute can be used to set the sending notification interval to be greater than the verification event notification interval, and a schematic diagram of the time interval is shown in Fig. 3A. In this embodiment, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by the verification event notification interval, and if the event notification rule is met, determining that the re-notification criterion is met, waiting for sending an event notification, and sending an event notification 2 to notifiers in at least one group of the multiple groups, for example, the second group, at a time determined by the sending notification interval.
[0081] As shown in Fig. 9B, the service entity uses the sending event notification interval attribute and the verification event notification interval attribute shown in Fig. 8A or 8B to set the sending notification interval to be smaller than the verification event notification interval, and the schematic diagram of the time interval is shown in Fig. 3B. In this embodiment, determining whether the re-notification criterion is met includes determining that the re-notification criterion is met at a time determined by the sending notification interval, and sending an event notification 2 to at least one group of the multiple groups, for example, notifiers in the second group (i.e., notifiers D and E). After receiving the event notification 2, the notifiers in the second group can send a notification response corresponding to the event notification 2 to the service entity.
[0082] In this implementation, the service entity can determine whether an event notification rule is satisfied at a time determined by the verification event notification interval, and if the event notification rule is satisfied, wait for the outgoing event notification, and further send an event notification 3 to at least one of the multiple groups, for example, a notifier in a third group (i.e., notifier F), at a time determined by the outgoing notification interval. After receiving the event notification 3, the notifier in the third group can send a notification response corresponding to the event notification 2 to the service entity.
[0083] In the above embodiments of the present disclosure, after the service entity sends event notification 1 (or event notification 2), it judges whether there is a notifier to send the event notification to it, and if it determines that the notifier does not exist, that is, if none of the notifiers in the notifier list has received the event notification, the service entity does not judge whether the re-notification criteria are met.
[0084] The event notification method disclosed herein divides notifiers in a subscription request into groups, and performs event notifications based on the groups rather than sending event notifications to all notifiers at once, and further realizes the above-mentioned grouping and sending event notifications by setting a transmission event notification interval and / or a verification event notification interval, thereby realizing management of notifiers in a subscription request, achieving accuracy in sending event notifications, improving notification efficiency, and avoiding information interference with notifiers.
[0085] According to an embodiment of the present disclosure, the event subscription request may include only one notifier, in which case the one notifier is divided into one group, for example, a fourth group. In this embodiment, sending an event notification to at least one notifier in the one or more groups includes determining whether the event notification rule is satisfied, and if the event notification rule is satisfied, determining whether a re-notification criterion is satisfied, and if the re-notification criterion is satisfied, sending the event notification to the one or more notifiers. That is, if it is determined that the event notification rule is satisfied, the event notification is not sent to the notifier in the fourth group, and a determination is made as to whether the re-notification rule is satisfied, thereby realizing the effect of delaying the sending of the event notification to the notifier in the fourth group.
[0086] According to an embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a verification event notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0087] Specifically, FIG. 10A shows a flowchart of sending an event notification to one notifier in the fourth group in an embodiment of the present disclosure. As shown in FIG. 10A, a subscriber, a notifier, and an application entity realize device registration by sending a device registration request to a service entity. Then, a subscriber can send a subscription request to the service entity. The subscription request may be a single-resource subscription request as described above, and further, the event subscription request may include one notifier and may include an event notification rule and a re-notification criterion for determining whether to send an event notification. The service entity may also create a subscription resource based on the received subscription request and send a subscription response to the subscriber of the subscription request.
[0088] The application entity may be a manhole cover movement sensor that can periodically send an update request to a service entity to update data on whether the manhole cover has moved or not. The service entity receives the update request from the application entity and sends an update response to the application entity, and the application entity sends update data to the service entity based on the update response. After receiving the update data, the service entity can determine whether the update data satisfies an event notification rule.
[0089] If it is determined that the update data satisfies the event notification rule, the service entity waits until a time determined by a verification event notification interval, and when the time is reached, the service entity again judges whether the event notification rule is satisfied, and if it is determined that the received update data still satisfies the event notification rule, the service entity sends an event notification to the notifier included in the subscription request, thereby achieving the effect of delaying the sending of the event notification to one notifier in the fourth group.
[0090] According to an embodiment of the present disclosure, the event subscription request may include multiple notifiers, in which case the multiple notifiers are divided into a group, for example, a fifth group. In this embodiment, sending an event notification to at least one of the one or more groups is determined to satisfy the event notification rule, and if the event notification rule is satisfied, it is determined whether a re-notification criterion is satisfied, and if the re-notification criterion is satisfied, the event notification is sent to the notifiers in the fifth group. That is, if it is determined that the event notification rule is satisfied, the event notification is not sent to the multiple notifiers in the fifth group, and a determination is made as to whether the re-notification rule is satisfied, thereby realizing the effect of delaying the sending of the event notification to the multiple notifiers in the fifth group.
[0091] FIG. 10B shows a flowchart for sending an event notification to multiple notifiers in multiple fifth groups in an embodiment of the present disclosure. As shown in FIG. 10B, the subscription request can further include multiple notifiers, for example, two notifiers. The specific flowchart of the event notification delay shown in FIG. 10B is similar to the flowchart shown in FIG. 10A, so the description is omitted here. It should be noted that the two notifiers shown in FIG. 10B do not include the subscriber who sends the subscription request, but this is an example, and the multiple notifiers may include the subscribers themselves.
[0092] According to the embodiment of the present disclosure, the event subscription request may be at least one of a single resource subscription request and a cross resource subscription request. The single resource subscription request may be implemented as shown in Fig. 5, Fig. 7, Fig. 9A, or Fig. 9B above, that is, a subscriber may request to subscribe to update data of one application entity. The cross resource subscription request may be implemented as a subscriber may request to subscribe to update data of multiple application entities.
[0093] 11 is a flowchart of a cross-resource subscription in an event notification method according to an embodiment of the present disclosure. As shown in FIG. 11, the subscription request is a cross-resource subscription request. In this case, the event notification rule may be a cross-resource event notification rule. After receiving update data of multiple application entities (two application entities are shown in FIG. 11), the service entity determines whether the cross-resource event notification rule is satisfied.
[0094] If it is determined that the cross-resource event notification rule is satisfied, the service entity waits until a time determined by a verification event notification interval, and when the time is reached, the service entity again judges whether the cross-resource event notification rule is satisfied, and if it is determined that the received update data still satisfies the cross-resource event notification rule, the service entity sends an event notification to one or more notifiers included in the subscription request, thereby achieving the effect of delaying the sending of the event notification to the one or more notifiers.
[0095] According to the event notification method disclosed herein, when received update data satisfies an event notification rule, instead of immediately sending an event notification to one or more notifiers included in the subscription request, the method waits until a time determined by a verification event notification interval is reached, and when that time is reached, a determination is made again as to whether or not the event notification rule is satisfied, and if it is determined that the event notification rule is satisfied, the event notification is sent to the one or more notifiers.
[0096] According to an embodiment of the present disclosure, a server device is further provided. FIG. 12 is a schematic diagram of a server device in an embodiment of the present disclosure. The server device 100 includes a transceiver 101 and a processor 102, where the transceiver 101 is configured to receive an event subscription request from a subscriber, the event subscription request including one or more notifiers. The processor 102 is configured to divide the one or more notifiers into one or more groups, each group including one or more notifiers, and to instruct the transceiver to send an event notification to at least one of the one or more groups.
[0097] According to an embodiment of the present disclosure, the processor 102 is further configured to determine whether an event notification rule is satisfied, and if the event notification rule is satisfied, instruct the transceiver 101 to send an event notification to a notifier in at least one of the one or more groups.
[0098] According to an embodiment of the present disclosure, the processor 102 further determines whether a re-notification criterion is met after instructing the transceiver 101 to send an event notification to a notifier in at least one of the one or more groups, and if the re-notification criterion is met, instructs the transceiver 101 to send an event notification to a notifier in at least one of the one or more groups, wherein a group that sends the event notification if an event notification rule is met is designated as an initial notification group, and a group that sends the event notification if the re-notification criterion is met is designated as a re-notification group, and the initial notification group is different from the re-notification group.
[0099] According to one embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a verification event notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0100] According to another embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining whether an event notification rule is met at a time determined by a transmission notification interval, and determining that the re-notification criterion is met if the event notification rule is met.
[0101] According to another embodiment of the present disclosure, determining whether the re-notification criterion is met includes determining that the re-notification criterion is met at a time determined by a transmission notification interval.
[0102] Optionally, the above server device 100 may further have an internal or external memory for storing resources created for the application entities and for storing associated instructions that, when executed by the processor 102, perform the steps of the above event notification method.
[0103] According to an embodiment of the present disclosure, there is further provided an event notification device. Fig. 13 is a schematic diagram of the event notification device in the embodiment of the present disclosure. The event notification device 200 may include one or more processors 201 and one or more memories 202. Here, the processor 201 stores computer-readable code, which, when executed by the one or more processors 202, can perform the event notification method as described above, and the description thereof will be omitted here.
[0104] According to an embodiment of the present disclosure, there is further provided a computer storage medium, wherein the computer storage medium has computer readable code stored thereon, the computer readable code being capable of performing the event notification method as described above when executed by one or more processors, the description of which is omitted herein.
[0105] Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. Furthermore, terms as defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted in an ideal or very formal sense unless expressly defined in this application.
[0106] Although the present disclosure has been described above, the present disclosure is not limited to the above-mentioned embodiments. Although several exemplary embodiments of the present disclosure have been described, those skilled in the art will easily understand that many modifications can be made to the exemplary embodiments without departing from the novel teachings and advantages of the present disclosure. Therefore, all such modifications are intended to be included within the scope of the present disclosure as defined by the claims. The above is a description of the present disclosure, and should not be construed as being limited to the specific embodiments disclosed, and it should be understood that modifications to the disclosed embodiments and other embodiments are intended to be included within the scope of the appended claims. The present disclosure is defined by the claims and their equivalents.
[0107] This application claims priority to Chinese Patent Application No. 201811432991.5, filed on November 28, 2018, the entire contents of which are incorporated herein by reference as part of this application. [Explanation of symbols]
[0108] 100 devices 101 Transmitter / Receiver 102 processors 200 equipment 201 Memory 202 Processor
Claims
1. An event notification method, comprising: receiving an event subscription request from a subscriber, the event subscription request including one or more notifiers; dividing the one or more notifiers into one or more groups, each group including one or more notifiers; determining whether an event notification rule is satisfied, using the event notification rule to determine whether an event notification has occurred, and if the event notification rule is satisfied, sending an event notification to notifiers in at least one of the one or more groups; Sending an event notification to notifiers in at least one of the one or more groups includes: After sending the event notification, determine whether a re-notification criterion is met, and if the re-notification criterion is met, send the event notification to at least one of the one or more groups, where the one or more groups are obtained by grouping the one or more notifiers included in the event subscription request; a group to which an event notification is sent if the event notification rule is satisfied, the group being referred to as an initial notification group, and a group to which an event notification is sent if the re-notification criterion is satisfied, the group being referred to as a re-notification group, the initial notification group and the re-notification group being different; The event notification method includes: Checking the transmission notification interval and the verification event notification interval to determine which interval is larger, and determining whether the re-notification criterion is met based on the checking; If the transmission notification interval is greater than the validation event notification interval, the criteria for determining whether the re-notification criteria are met include: At a time determined by the verification event notification interval, determining whether an event notification rule is satisfied, and if the event notification rule is satisfied, waiting for an event notification to be sent; at a time determined by the sending notification interval, determining that the re-notification criterion is satisfied, and sending an event notification to a notifier in at least one of the one or more groups; If the validation event notification interval is greater than the transmission notification interval, the criterion for determining that the re-notification criterion is met is: determining whether the re-notification criterion is satisfied at a time determined by the transmission notification interval, the event notification method further including: determining whether an event notification rule is satisfied at a time determined by the verification event notification interval; if the event notification rule is satisfied, waiting for the transmission event notification; and sending the event notification to a notifier in at least one of the one or more groups at a time determined by the transmission notification interval. Event notification method.
2. Determining whether the renotification criteria are met includes: determining whether an event notification rule is satisfied at a time determined by the verification event notification interval; and determining that the re-notification criterion is satisfied if the event notification rule is satisfied; The event notification method according to claim 1 .
3. Determining whether the renotification criteria are met includes: determining whether an event notification rule is satisfied at a time determined by the transmission notification interval; and determining that the re-notification criterion is satisfied if the event notification rule is satisfied; The event notification method according to claim 1 .
4. Determining whether the renotification criteria are met includes: determining that the re-notification criteria are met at a time determined by a transmission notification interval; The event notification method according to claim 1 .
5. an event notification rule attribute for determining whether to send an event notification to a notifier; an event notification list attribute for storing address information of the one or more notifiers based on the one or more groups; a validation event notification interval attribute for setting a time interval for determining whether an event notification rule is satisfied; a validation event notification enable attribute for setting whether the validation event notification interval attribute is enabled; a sending notification interval attribute for setting a time interval for sending the event notification. The event notification method according to claim 1 .
6. The event subscription request is used to request to receive update data from an application entity; The event notification method includes: determining whether an event notification rule is satisfied based on the update data; The event notification method according to claim 1 .
7. Sending an event notification to notifiers in at least one of the one or more groups includes: determining, based on an order of the one or more groups, to which an event notification should be sent, the at least one group; The event notification method according to claim 1 .
8. Sending an event notification to notifiers in at least one of the one or more groups includes: determining whether an event notification rule is satisfied, and if the event notification rule is satisfied, determining whether a re-notification criterion is satisfied; sending an event notification to notifiers in at least one of the one or more groups if the re-notification criteria are met. The event notification method according to claim 1 .
9. Determining whether the renotification criteria are met includes: determining whether an event notification rule is satisfied at a time determined by the verification event notification interval; and determining that the re-notification criterion is satisfied if the event notification rule is satisfied; The event notification method according to claim 8.
10. the event subscription request is at least one of a single-resource subscription request and a cross-resource subscription request; The event notification method according to claim 1 .
11. 1. A server device, comprising: A transceiver and a processor, The transceiver is configured to receive an event subscription request from a subscriber, the event subscription request including one or more notifiers; the processor is configured to divide the one or more notifiers into one or more groups, each group including one or more notifiers; and determine whether an event notification rule is satisfied; determine whether an event notification has occurred using the event notification rule; and if the event notification rule is satisfied, instruct the transceiver to send an event notification to at least one of the one or more groups; After sending the event notification, the processor determines whether a re-notification criterion is met, and if the re-notification criterion is met, instructs the transceiver to send the event notification to notifiers in at least one of the one or more groups, the one or more groups being obtained by grouping the one or more notifiers included in the event subscription request; A group to which an event notification is sent when the event notification rule is satisfied is represented as an initial notification group, and a group to which an event notification is sent when the re-notification criterion is satisfied is represented as a re-notification group, and the initial notification group and the re-notification group are configured to be different; The processor, Checking the sending notification interval and the verification event notification interval to determine which interval is larger, and determining whether the re-notification criterion is met based on the checking; If the transmission notification interval is greater than the validation event notification interval, the criteria for determining whether the re-notification criteria are met include: At a time determined by the verification event notification interval, determining whether an event notification rule is satisfied, and if the event notification rule is satisfied, waiting for an event notification to be sent; at a time determined by the sending notification interval, determining that the re-notification criterion is satisfied, and sending an event notification to a notifier in at least one of the one or more groups; If the validation event notification interval is greater than the transmission notification interval, the criterion for determining that the re-notification criterion is met is: determining that the re-notification criterion is met at a time determined by the transmission notification interval, the processor further being configured to determine whether an event notification rule is met at a time determined by the validation event notification interval, and if an event notification rule is met, wait for the transmission event notification, and send the event notification to notifiers in at least one of the one or more groups at a time determined by the transmission notification interval. Server device.
12. An event notification device, one or more processors; one or more memories in which computer readable code is stored; The computer readable code, when executed by the one or more processors, performs the event notification method according to any one of claims 1 to 10. Event notifier.
13. A computer storage medium having computer readable code stored thereon, The computer readable code, when executed by one or more processors, performs the event notification method according to any one of claims 1 to 10. Computer storage media.
Citation Information
Patent Citations
Method, apparatus and system for carrying out notification
CN107666432A
Event notification method and server
CN107968805A
Information processing device, system, and method
JP2006092254A
Recruitment system and recruitment program
JP2013037414A
Method and Apparatus for Analyzing and Grouping Service Layer Subscriptions and Notifications for Increased Efficiency
JP2018526703A
