Method, device and system for notification

Abstract

A method, device and system for notification. The method comprises: determining an event notification rule; judging whether the participant information satisfies the event notification rule, and if so, sending a notification to the notified party; wherein the participant information comprises at least one of a participant identification, a participant identification feature, a participant role, and a participant role feature. In the embodiment of the present disclosure, when a subscription service party detects a participant that satisfies the above participant information, a notification message is sent to the notified party, thereby realizing a notification service based on the above participant and meeting the differentiated needs of users.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 12, 2016, application number 201610665731.7, and invention name “Method, device and system for notification”. Technical Field

[0002] Embodiments of the present disclosure relate to a method, device, and system for performing notification. Background Art

[0003] With the development of Internet of Things technology, various application fields of Internet of Things have developed rapidly, and many private protocols have emerged. Since the private protocols are not fully compatible with each other, it may hinder the development of Internet of Things technology.

[0004] The IoT communication protocol defines a subscription notification mechanism, where the subscriber sends a subscription request to the subscriber and a notification is sent to the subscriber when an event occurs. Summary of the invention

[0005] Embodiments of the present disclosure provide a method, device, and system for performing notification.

[0006] The method for notifying includes:

[0007] Determine event notification rules; determine whether the participant information satisfies the event notification rules, and if so, send a notification to the notified party; wherein the participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role feature.

[0008] For example, determining the event notification rule may include: determining the event notification rule from a subscription resource or from an event notification rule set.

[0009] For example, determining the event notification rule from a subscription resource; or

[0010] The event notification rule is determined from a set of event notification rules.

[0011] For example, it also includes:

[0012] A subscription resource is created, wherein the subscription resource includes the event notification rule.

[0013] For example, before creating the subscription resource, the method further includes: receiving a subscription resource creation request sent by the subscriber.

[0014] For example, judging whether the participant information satisfies the event notification rule includes:

[0015] Determine whether the participant information matches the feature value, and if so, determine that the participant information satisfies the event notification rule.

[0016] For example, it also includes: receiving a subscription request sent by a subscriber to determine the event notification rule.

[0017] For example, the notification method further includes: receiving an operation request, wherein the operation request includes the participant information.

[0018] For example, the notification method further includes: receiving a registration request, wherein the registration request includes the participant information.

[0019] For example, judging whether the participant information satisfies the event notification rule includes: judging whether the participant information is different from the judgment feature, and if so, determining that the participant information satisfies the event notification rule.

[0020] For example, judging whether the participant information satisfies the event notification rule includes: judging whether the participant information is equivalent to the judgment feature, and if so, determining that the participant information satisfies the event notification rule.

[0021] For example, determining whether the participant information satisfies the event notification rule includes: counting the number of participants whose participant information is different from the judgment characteristics; determining whether the number of participants satisfies the event notification rule; if the number of participants satisfies the event notification rule, determining that the participant information satisfies the event notification rule.

[0022] For example, determining whether the number of the participants satisfies the event notification rules includes: determining whether the number of the participants is greater than or equal to a first threshold, and if so, determining that the number of the participants satisfies the event notification rules; or determining whether the number of the participants is less than or equal to a second threshold, and if so, determining that the number of the participants satisfies the event notification rules; or determining whether the number of the participants is greater than or equal to the first threshold and less than or equal to the second threshold, and if so, determining that the number of the participants satisfies the event notification rules.

[0023] For example, determining whether the participant information satisfies the event notification rule includes: counting the number of participants whose participant information is the same as the judgment feature; determining whether the number of participants satisfies the event notification rule; if so, determining that the participant information satisfies the event notification rule.

[0024] For example, determining whether the number of the participants satisfies the event notification rules includes: determining whether the number of the participants is greater than or equal to a third threshold, and if so, determining that the number of the participants satisfies the event notification rules; or determining whether the number of the participants is less than or equal to a fourth threshold, and if so, determining that the number of the participants satisfies the event notification rules; or determining whether the number of the participants is greater than or equal to the third threshold and less than or equal to the fourth threshold, and if so, determining that the number of the participants satisfies the event notification rules.

[0025] For example, the judgment feature includes at least one of an identification, a role, an identification feature, and a role feature.

[0026] For example, the identification includes at least one of a subscriber identification, a subscribed party identification, a notified party identification, a participant identification, a subscriber preset identification, a subscribed party preset identification, a notified party preset identification and a participant preset identification; the role includes at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role and a participant preset role; the identification feature includes at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature and a participant preset identification feature; the role feature includes at least one of a subscriber role feature, a subscribed party role feature, a notified party role feature, a participant role feature, a subscriber preset role feature, a subscribed party preset role feature, a notified party preset role feature and a participant preset role feature.

[0027] An embodiment of the present disclosure also provides a device for notification, comprising: a determination unit, used to determine an event notification rule; a notification unit, used to determine whether the participant information satisfies the event notification rule, and if so, sends a notification to the notified party; wherein the participant information includes a participant identification, a participant identification feature, and at least one of a participant role and a participant role identification feature.

[0028] For example, the determining unit is specifically configured to determine the event notification rule from a subscription resource or from an event notification rule set.

[0029] For example, the subscription service device further includes: a subscription resource creation unit, configured to create a subscription resource, wherein the subscription resource includes the event notification rule.

[0030] For example, the subscription service device further includes: a first receiving unit, configured to receive a subscription resource creation request sent by a subscriber before creating a subscription resource.

[0031] For example, the notification unit is specifically used to determine whether the participant information matches the feature value. If so, it is determined that the participant information meets the event notification rule, and a notification is sent to the notified party.

[0032] For example, the subscription service device further includes: a second receiving unit, configured to receive a subscription request sent by a subscriber to determine the event notification rule.

[0033] For example, the first receiving unit is further used to receive an operation request, wherein the operation request includes the participant information.

[0034] For example, the notification unit is specifically used to determine whether the participant information is different from the judgment feature. If so, it is determined that the participant information meets the event notification rule and a notification is sent to the notified party.

[0035] For example, the notification unit is specifically used to determine whether the participant information is equivalent to the judgment feature. If so, it is determined that the participant information meets the event notification rule and a notification is sent to the notified party.

[0036] For example, the event notification unit is specifically used to: count the number of participants whose participant information is different from the judgment characteristics; judge whether the number of participants satisfies the event notification rules; if the number of participants satisfies the event notification rules, determine that the participant information satisfies the event notification rules, and send a notification to the notified party.

[0037] For example, the notification unit is specifically used to: count the number of participants whose participant information is the same as the judgment feature; judge whether the number of participants meets the event notification rule; if so, determine that the participant information meets the event notification rule and send a notification to the notified party.

[0038] For example, the judgment feature includes at least one of an identification, a role, an identification feature, and a role feature.

[0039] For example, the identification includes at least one of a subscriber identification, a subscribed party identification, a notified party identification, a participant identification, a subscriber preset identification, a subscribed party preset identification, a notified party preset identification and a participant preset identification; the role includes at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role and a participant preset role; the identification feature includes at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature and a participant preset identification feature; the role feature includes at least one of a subscriber role feature, a subscribed party role feature, a notified party role feature, a participant role feature, a subscriber preset role feature, a subscribed party preset role feature, a notified party preset role feature and a participant preset role feature.

[0040] An embodiment of the present disclosure also provides a system for notification, including:

[0041] Any device as described above, wherein the device is a subscription service device;

[0042] A subscription device, configured to send a subscription creation request to the subscription service device;

[0043] A participant device configured to send an operation request to the subscription service device; and

[0044] The notified party device is configured to receive a notification from the subscription service device.

[0045] The embodiments of the present disclosure provide a method, device and system for notification, which implement subscription notification based on specific participants. Specifically, when the subscription service detects that a specific participant meets the event notification rule, a notification message is sent to the notified party, wherein the specific participant is a participant whose participant information includes at least one of a participant identification and a participant role. In this way, a notification service based on the specific participant is implemented, meeting the differentiated needs of users. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for describing the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention, rather than limitations of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0047] Figure 1A hardware schematic block diagram of a system for subscription notification provided in an embodiment of the present disclosure;

[0048] Figure 2 A flowchart of a notification method provided for at least one embodiment of the present disclosure;

[0049] Figure 3 A schematic block diagram of a device for subscription services provided for at least one embodiment of the present disclosure;

[0050] Figure 4 A schematic diagram of a notification subscription process provided by an embodiment of the present disclosure;

[0051] Figure 5 A schematic diagram of a process of subscribing to notifications provided for some embodiments of the present disclosure;

[0052] Figure 6 A schematic diagram of a process of subscribing to notifications provided for some embodiments of the present disclosure; and

[0053] Figure 7 A schematic diagram of an exemplary subscription resource structure provided in an embodiment of the present disclosure;

[0054] Figure 8 A flowchart of a notification method provided for at least one embodiment of the present disclosure.

[0055] Reference numerals:

[0056] Subscribing device 101; participant device 104; notified party device 106; subscription service device 150; processor 152; memory 154; network 160; subscription service apparatus 300; resource creation unit 302; operation unit 306; notification unit 310; participant apparatus 402; subscription apparatus 404; notified party apparatus 406. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solutions and advantages of the present disclosure clearer, the present disclosure is further described in detail with reference to the following embodiments. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure. In the current related technology, the subscriber sends a subscription request to the subscription service party (also referred to as the subscribed party or the notified party), and the subscription request may indicate that when an event occurs, the subscription service party sends a message to the notified party. The subscriber and the notified party may be the same entity or different entities. The rules for the occurrence of the event are defined under the subscribed resource (for example, a subscribed resource is created under the subscribed resource). <subscription>resource, <subscription>The eventNotificationCriteria parameter of the resource contains the event notification rules. When the event notification rules are met, the subscribing service sends a notification to the notified party. For example, the parameters of the event notification rules include, but are not limited to, the parameters listed in Table 1:

[0058] Table 1

[0059]

[0060]

[0061] The current subscription mechanism does not take into account the different situations of participating entities (e.g., subscribers, participants, notified parties, etc.). In practical applications, when the notified party wishes to perform corresponding actions based on a specific participant (e.g., when a participant performs an operation), the subscription service provider can send a message to the notified party. The existing subscription notification mechanism cannot meet these requirements. The specific participant can be understood as other participants other than the subscriber, the subscribed party, and the notified party, and the other participants can perform operations such as update, delete, create, etc. Of course, the participant and the subscriber, the subscribed party, or the notified party can be one entity or different entities.

[0062] The embodiments of the present disclosure provide a method, device and system for notification, which implements notification based on specific participants, such as subscription. Specifically, when the subscription service detects a specific participant, it sends a notification message to the notified party, thereby implementing a notification service based on the participant and meeting the differentiated needs of users.

[0063] Specifically, the embodiments of the present disclosure provide a method, device and system for notification, which implements notification based on a specific participant. Specifically, when the subscription service detects that a specific participant meets the event notification rule, a notification message is sent to the notified party. For example, when the subscription service detects that the specific participant information meets the event notification rule, a notification message is sent to the notified party.

[0064] The event notification rule is an event notification condition (eventNotificationCriteriaconditions), and the event notification rule may be an event notification rule set, which may include one or more sub-conditions. When determining whether the participant information satisfies the event notification rule, it may be determined whether the participant information satisfies any one of the sub-conditions, or satisfies all the sub-conditions.

[0065] The participant information includes at least one of participant identification, participant role, participant role characteristics, and participant identification characteristics.

[0066] In this way, a notification service based on the specific party is implemented, meeting the differentiated needs of users.

[0067] The following uses subscription as an application scenario to illustrate the method, device and system for notification during the subscription process.

[0068] Figure 1 FIG. 1 is a hardware schematic block diagram of a system 100 for performing notification provided in an embodiment of the present disclosure. Figure 1 As shown, the system 100 may include a subscription device 101, a participant device 104, a notified party device 106, and a subscription service device 150 (the subscription service device is a notification device that performs notification). The devices in the system 100 may be connected via a network 160. The devices in the system 100 may communicate with each other directly or indirectly. For example, the devices in the system 100 may send and receive data and / or signals to each other via the network 160.

[0069] The network 160 may be a network that can realize the interconnection of common objects with independent functions. The network 160 may be a wireless network, and of course, the network 160 may also include a wired network. For example, the network 160 may be an Internet of Things (IoT) based on the Internet and / or telecommunications network. Each user can use an electronic tag to connect an ordinary object to the IoT, so the specific location of each ordinary physical object can be found on the IoT. Through the IoT, a central computer can be used to centrally manage and control various machines and equipment. For example, machines or equipment such as household appliances (e.g., smart refrigerators, smart microwave ovens, etc.) and cars can be remotely controlled, and their locations can be searched.

[0070] The subscription service device 150 (i.e., notification device) may be a computing device including a processor and a memory. For example, the subscription service device 150 may be a server. Of course, the subscription service device 150 may also be a desktop computer, a laptop computer, a smart phone, a tablet computer, or other devices including a processor and a memory. Figure 1 Subscription server 150 is shown to include a processor 152 and a memory 154 .

[0071] The processor 152 can process data signals and may include various computing structures, such as a complex instruction set computer (CISC) structure, a reduced instruction set computer (RISC) structure, or a structure that implements a combination of multiple instruction sets. In some embodiments, the processor 152 may also be a microprocessor, such as an X86 processor or an ARM processor, or may be a digital signal processor (DSP), etc. The processor 152 may control other components in the subscription service device 150 to perform desired functions.

[0072] The memory 154 can store instructions and / or data executed by the processor 152. For example, the memory 154 may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 152 may run the program instructions to implement the subscription notification function described below and / or other desired functions. Various applications and various data, such as various data used and / or generated by the application, may also be stored in the computer-readable storage medium.

[0073] Subscription device 101 may be a computing device including a processor and a memory. For example, subscription device 101 may be a television, a desktop computer, a laptop computer, a smart phone, a tablet computer, a game controller, a music player (e.g., an MP3 player, etc.), and other terminals including a processor and a memory (e.g., a mobile terminal, a smart terminal). In some embodiments, subscription device 101 may include a processor, a memory, and other components such as an input device and an output device.

[0074] The participant device 104 may be a computing device including a processor and a memory. For example, the participant device 104 may be a television, a smart home appliance, a charging car, a desktop computer, a laptop computer, a smart phone, a tablet computer, and other terminals including a processor and a memory (e.g., a mobile terminal, a smart terminal). In some embodiments, the participant device 104 may include a processor, a memory, and other components such as an input device and an output device.

[0075] The notified party device 106 may be a computing device including a processor and a memory. For example, the notified party device 106 may be a television, a smart home appliance, a charging car, a desktop computer, a laptop computer, a smart phone, a tablet computer, a game controller, a music player (such as an MP3 player, etc.), and other terminals including a processor and a memory (such as a mobile terminal, a smart terminal). In some embodiments, the notified party device 106 may include a processor, a memory, and other components such as an input device and an output device.

[0076] In some embodiments, the subscriber and the notified party may be the same entity or different entities. The participant and the subscriber may be the same entity or different entities. If they are the same entity, then the entity has the roles of both the subscriber and the participant, and can perform subscription and third-party operations at the same time. Of course, the subscriber, the notified party, and the participant may also be different entities.

[0077] In some embodiments, the subscriber operates the subscription device 101 and sends a subscription creation request to the subscription service device 150. Without ambiguity, the subscriber described in the embodiments of the present disclosure may refer to the subscription device 101, the subscriber operating the subscription device 101, or the subscription apparatus 404 installed in the subscription device 101 described below.

[0078] The operator may operate the participant device 104 to send an operation request to the subscription service device 150. Of course, the participant device 104 may also automatically send an operation request to the subscription service device 150 without human intervention. In the absence of ambiguity, the participant described in the embodiment of the present disclosure may refer to the participant device 104, the operator operating the participant device 104, or the participant apparatus 402 installed on the participant device 104 described below.

[0079] The notified person may operate the notified device 106. For example, the notified person may read the notification from the subscription service device 150 through the notified device 106. Without ambiguity, the notified party described in the embodiment of the present disclosure may refer to the notified device 106, the notified person operating the notified device 106, or the notified party apparatus 406 installed in the notified device 106 described below.

[0080] The service provider can operate the subscription service device 150 to send notifications to the notified party. Of course, the subscription service device 150 can also automatically send notifications to the notified party without human intervention when the event notification rules are met. In the absence of ambiguity, the subscription service party described in the embodiment of the present disclosure may refer to the subscription service device 150, the service provider operating the subscription service device 150, or the subscription service device 300 installed in the subscription service device 150 described below (the subscription service device is the notification device for notification).

[0081] In some embodiments, each device of system 100 may also include a display device (such as LCD, OLED or projection device), an input device (such as touch device, keyboard, microphone, mouse, etc.), a speaker or a vibration device, etc. as needed.

[0082] The present invention discloses a method for performing notification in a subscription scenario, such as Figure 8 As shown, it includes:

[0083] Step S1001 includes: determining an event notification rule; step S1002 includes: determining whether the participant information meets the event notification rule, and if so, sending a notification to the notified party; wherein the participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role identification. Step S1003 includes: if the participant information meets the event notification rule, sending a notification to the notified party.

[0084] The method provided by the present invention can determine whether to notify based on the participant information, especially based on the matching relationship between at least one of the participant information including the participant identification, participant identification feature, participant role, participant role identification, etc. and the event notification rules, thereby meeting the notification needs of more users or participants.

[0085] The determining of the event notification rule may include determining the event notification rule from a subscription resource or from an event notification rule set.

[0086] For example, in some embodiments, the rules for event occurrence are defined under subscription resources, that is, the subscription resources include event notification rules (i.e., event notification conditions, eventNotificationCriteria), and one subscription resource may correspond to the event notification rules under the resource. When determining the event notification rules, the event notification rules may be determined from the subscription resources, such as directly determining the event notification rules in the subscription resources as the event notification rules that need to be determined.

[0087] For another example, in some other embodiments, the event notification rule is not included in the subscription resource, but is independently set in an event notification rule set outside the subscription resource, and the event notification rule set may include one or more event notification rules. When determining the event notification rule, one or more event notification rules may be determined from the event notification rule set as the event notification rule that needs to be determined.

[0088] The above-mentioned determination of the event notification rule from the subscription resource specifically includes: obtaining the event notification rule from the subscription resource including the event notification rule, or directly matching the event notification rule in the subscription resource without obtaining it. Of course, one or more event notification rules can be directly obtained from the event notification rule set, or the event notification rule in the event notification rule set can be directly matched, so as to determine whether the event notification rule is satisfied when the participant information is obtained.

[0089] In some implementations, the subscription resource may be a subscription resource created in response to a subscription resource creation request after receiving the subscription resource creation request sent by the subscriber. <subscription>When a resource is requested, the corresponding subscriber creates <subscription>The resource request creates a subscription resource including the event notification rule. Alternatively, when receiving a subscription resource request sent by a subscriber, a subscription resource that matches the subscription resource request is determined from the created subscription resources for the subscription resource request.

[0090] Wherein, the determination of the event notification rule may be performed after receiving the subscription request sent by the subscriber. For example, when the participant and the subscriber are UPNP CP, the subscribed party is UPNP Client, and the notified party is UPNP Device, the subscriber sends a subscription request to the subscribed party, and the subscription request carries the URL of the subscribed party, the service identifier, and the URL of the notified party. After the subscribed party receives the subscription request, the subscription resource is matched for the subscriber, and the subscription resource may be determined according to the pre-configured event notification rule. After that, the participant sends an action request to the subscribed party. When the subscribed party receives the action request, the action request carries the information of the participant (e.g., the participant ID). After receiving the action request, the subscribed party determines whether the information of the participant satisfies the pre-configured notification rule (e.g., determines whether the ID of the participant satisfies the notification rule), and notifies the notified party.

[0091] The participants will be emphasized again below, and the participants can be understood as other participants except the subscriber, the subscribed party and the notified party.

[0092] In some IoT communication protocols (such as M2M protocols), the originator and receiver are defined from the dimension of information interaction. The party that initiates the request is called the originator, which can be an AE (application entity) or a CSE (common service entity), and the party that receives the request is called the receiver, which can be a CSE.

[0093] For example, if the initiator is the one who initiated the creation <subscription>Resource request, the initiator becomes the resource subscriber, referred to as the subscriber, and the corresponding receiver is the subscriber. In some IoT protocols, since there is no definition of the subscriber, the Hosting CSE is used to refer to the subscriber. For another example, if the initiator initiates a registration request, the initiator becomes the registrant, and the corresponding receiver is the registrant.

[0094] For another example, if the initiator initiates an operation request, the initiator becomes the operation requester (requester for short), and the receiver becomes the operation request receiver. The registrant, subscriber, and operation requester can be different roles when the same entity performs different actions, or different entities performing different actions. In this embodiment, the participant, subscriber, subscribed party, and notified party can be different roles when the same entity performs different actions, or different entities performing different actions. If the participant sends a registration request, it is the registrant, and if the participant sends an operation requester, it becomes the operation requester.

[0095] Optionally, determine whether the participant information satisfies the event notification rule, specifically: determine whether the participant information matches a specified value, and if so, determine that the participant information satisfies the event notification rule.

[0096] Wherein, the characteristic value is a specific value, which can be configured in the subscription resource or outside the subscription resource. It is provided to the subscription resource when judging whether the participant information meets the event notification rule. The specific value can be a value indicating a data type, a value indicating a data structure, a value indicating a data content, etc. For example, the specific value can be a content feature of an identifier (such as 1111-22). Wherein, judging whether the participant information matches the characteristic value (specified value) includes judging whether the participant information is equal to the characteristic value, whether it is greater than the characteristic value, whether it is less than the characteristic value, or whether the number of participant information is greater than the number of the characteristic value, whether it is equal to the data of the characteristic value, whether it is less than the data of the characteristic value, etc., and the matching method of matching the participant information with the characteristic value is configured according to different application scenarios. For example, when it is desired to notify the notified party when the number of participants exceeds a certain specific value, the matching method can be configured to judge the number of identifications of the participants, and when the number of identifications is greater than the specific value, the notified party is notified.

[0097] It should be noted that the identifier can be a specific value, a specific numerical value, a symbol or a combination thereof. For example, the identifier of entity A is 1111-22, and the identifier of entity B is 2222-11. If the identifiers are compared, the two identifiers are different.

[0098] The identification feature is a feature of the identification, which can be a structural feature of the identification and / or a content feature of the identification. For example, the identification of entity A is AAAA-AA, and the identification of entity B is AAAA-BB. The structures of the two identifications are in the form of XXXX-YY, and the structural features of the two identifications are the same. The identification AAAA-AA includes a character A, and the identification AAAA-BB includes two characters A and B. It can be seen that the identification content features of the two identifications are different.

[0099] Roles and role traits are similar. Role refers to the role itself, and role traits refer to the characteristics possessed by the role. I will not go into details here.

[0100] Based on the subscription application scenario, before determining the event notification rule, the above method further includes: receiving a subscription request sent by the subscriber. In this way, the event notification rule can be determined based on the subscription request. After receiving the subscription request, the subscription resource corresponding to the subscription request can be determined, such as obtaining a pre-stored subscription resource locally or creating a subscription resource. Generally, the determined subscription resource includes the event notification rule. When determining the event notification rule, the event notification rule can be obtained from the subscription resource.

[0101] The following will take creating a subscription resource after receiving a subscription request as an example to illustrate the specific process of the notification method of the present invention.

[0102] Figure 2 1 is a schematic flow chart of a method 200 for performing notification provided in one of the above embodiments of the present disclosure. In some embodiments, the method 200 may include: Figure 2 Of course, method 200 may also include other steps not shown in the figure. Figure 2 The steps shown in .

[0103] Step S202 includes: receiving a subscription creation request from a subscriber (i.e., a request to create a subscription resource or to create a subscription resource). <subscription>resource request).

[0104] Step S204 includes: creating a subscription resource, wherein the subscription resource includes an event notification rule.

[0105] Step S206 includes: determining whether the participant information satisfies the event notification rule, wherein the participant information includes at least one of a participant identifier (ID), a participant role, a participant identification feature, and a participant role feature.

[0106] Step S208 includes: if the participant information satisfies the event notification rule, sending a notification to the notified party; otherwise, ending the process.

[0107] The method 200 further includes:

[0108] After the subscribed party creates the subscription resource, the subscribed party receives an operation request, which includes the participant information; or receives a registration request, which includes the participant information. Specifically, the operation request is an operation request from the participant (i.e., the operation requester); the registration request is a registration request from the registrant. Taking into account that in actual scenarios, what needs to be monitored are the operation conditions of other devices besides the registrant, the registrant, and the notified party, the subscribed party can be configured to receive an operation request from a participant, and determine whether the event notification rules are met based on the participant information carried in the operation request (such as the ID of the operation requester, in which case the participant is the operation requester).

[0109] Taking into account the actual scenario, it is necessary to know whether there is a new device registered. The subscribed party can be configured to receive a registration request from the registrant and determine whether the event notification rules are met based on the participant information carried in the registration request (such as the registrant's ID, in this case the participant is the registrant).

[0110] Under some IoT protocols (such as M2M protocols), the registrant and the subscriber may be different roles of the same entity when performing different actions.

[0111] For example, after a specific entity A (registrant) initiates a registration request to another entity B (registered party) and the registration is successful, entity A can send a request to create a subscription resource to entity B. At this time, entity A is the subscriber and entity B is the subscribed party. Entity B creates subscription resources for entity A, and the subscription is successful.

[0112] For example, when entity A sends a registration request and a request to create a subscription resource to entity B, and the registration and subscription are successful, and then entity D registers with entity B, it can be determined whether the ID of entity D is equal to the ID of the registered device, that is, whether the ID of entity D is equal to the ID of entity A (at this time, the ID of entity A is a specified value). If not, the notified party is notified that a new device has been registered.

[0113] For another example, when entity A sends a registration request and a request to create a subscription resource to entity B, and the registration and subscription are successful, entity C sends a registration request to entity B and after the registration is successful, it sends an operation request to entity B, it is determined whether the ID carried in the operation request of entity C is greater than 10 (at this time, the value 10 is a characteristic value, specified value). If it is greater, the notified party can be notified that 10 devices request to perform the operation action.

[0114] Furthermore, after receiving the operation request, the subscribed party sends a response to the operation request to the participating party, or sends a response to the registration request to the registrant.

[0115] The operation request may be a create request, an obtain request, an update request, a delete request or other types of requests. The operation request may include the information of the participant (hereinafter referred to as participant information). The participant information includes at least one of a participant identifier (ID), a participant role, a participant identification feature, and a participant role feature.

[0116] In some embodiments, all participants can be classified according to roles or role characteristics. Taking the participant information as the participant role as an example, all participants can be divided into categories such as administrator, ordinary user, VIP user, other user, etc. The participant role indicates that the participant is an administrator, ordinary user, VIP user or other user. The role characteristic of the participant is based on user identity.

[0117] In some embodiments, each participant identifier may be one of an application entity identifier (AE-ID), a common service entity identifier (CSE-ID), or a resource identifier (resourceID). The participant identifier records whether the participant is an application entity identifier, a common service entity identifier, or a resource identifier, as well as its specific number. For example, the participant identifier is 1234ABC.

[0118] In some embodiments, the participant information may be a participant identification feature. For example, if the participant identification is 1234ABC, then its identification feature is four consecutive digits + three consecutive letters.

[0119] In some embodiments, in step S204, creating the subscription resource includes: creating the subscription resource in response to the subscription resource creation request; and setting the event notification rule of the subscription resource. For example, the judgment feature of the event notification rule can be set (the judgment feature is the feature value, that is, the specified value). The judgment feature can include at least one of an identifier, a role, an identifier feature, and a role feature. The identifier can include at least one of a subscriber identifier, a subscribed party identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscribed party preset identifier, a notified party preset identifier, and a participant preset identifier. The role can include at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role, and a participant preset role. The identification feature can include at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature, and a participant preset identification feature. The role may include at least one of a subscriber role characteristic, a subscribed party role characteristic, a notified party role characteristic, a participant role characteristic, a subscriber preset role characteristic, a subscribed party preset role characteristic, a notified party preset role characteristic, and a participant preset role characteristic.

[0120] For example, the judgment feature may be set to a subscriber identifier, a preset identifier, or a notified party identifier. For another example, the judgment feature may be set to a subscriber role, a preset role, or a notified party role. For another example, the judgment feature may include: a subscriber identifier and a subscriber role; or, a subscriber preset identifier and a subscriber preset role; or, a notified party identifier and a notified party role. Of course, the judgment feature may also be set to other features, which are not limited in this disclosure.

[0121] In step S206, judging whether the participant information satisfies the event notification rule includes: judging whether the participant information is different from the judgment feature; and if the participant information is different from the judgment feature, determining that the participant information satisfies the event notification rule.

[0122] For example, the judgment feature may be a subscriber ID, and it may be judged whether the participant ID is different from the subscriber ID; if the participant ID is different from the subscriber ID (for example, participant ID≠subscriber ID), it is judged that the participant information satisfies the event notification rule. The subscriber ID may be obtained from a subscription creation request from the subscriber.

[0123] For another example, the judgment feature may be a subscriber role, and it may be judged whether the participant role is different from the subscriber role; if the participant role is different from the subscriber role (for example, participant role ≠ subscriber role), it is judged that the participant information satisfies the event notification rule. The subscriber role may be obtained from a subscription creation request from a subscriber.

[0124] In some embodiments, determining whether the participant information satisfies the event notification rule includes: determining whether the participant information is the same as a determination feature; and if the participant information is the same as the determination feature, determining that the participant information satisfies the event notification rule.

[0125] For example, the judgment feature may be a preset identifier, and whether the participant identifier is the same as the preset identifier is judged; if the participant identifier is the same as the preset identifier (for example, participant ID = preset ID), it is judged that the participant information satisfies the event notification rule.

[0126] For another example, the judgment feature may be a preset role, and it is judged whether the participant role is the same as the preset role; if the participant role is the same as the preset role (for example, participant role = preset role), it is judged that the participant information satisfies the event notification rule.

[0127] In step S206, determining whether the participant information satisfies the event notification rules may also include: counting the number of participants whose participant information is different from the judgment characteristics; determining whether the number of participants satisfies the event notification rules; if the number of participants satisfies the event notification rules, determining that the participant information satisfies the event notification rules.

[0128] In some embodiments, determining whether the number of the participants satisfies the event notification rules includes: determining whether the number of the participants is greater than or equal to a first threshold; if the number of the participants is greater than or equal to the first threshold, determining that the number of the participants satisfies the event notification rules.

[0129] For example, the participants can be classified according to roles (administrators, ordinary users, VIP users, other users, etc.). Assume that the judgment feature is set to VIP users in the role (that is, the judgment feature is set to "VIP users"), and the first threshold is set to 15. When the number of participants with the "VIP user" role that send an operation request to the subscription service device 300 is equal to or greater than 15 (that is, the number of participants with the "VIP user" role ≥ the first threshold 15), the event notification rule is met and a notification can be sent to the notified party.

[0130] In some embodiments, determining whether the number of the participants satisfies the event notification rules includes: determining whether the number of the participants is less than or equal to a second threshold; if the number of the participants is less than or equal to the second threshold, determining that the number of the participants satisfies the event notification rules.

[0131] For example, assuming that the judgment feature is set to a VIP user in a role (i.e., the judgment feature is set to "VIP user"), and the second threshold is set to 25. When the number of parties with the "VIP user" role that send an operation request to the subscription service device 300 is equal to or less than 25 (i.e., the number of parties with the "VIP user" role ≤ the second threshold 25), the event notification rule is satisfied, and a notification can be sent to the notified party.

[0132] In other embodiments, determining whether the number of the participants satisfies the event notification rules includes: determining whether the number of the participants is greater than or equal to a first threshold and less than or equal to a second threshold; if the number of the participants is greater than or equal to the first threshold and less than or equal to the second threshold, determining that the number of the participants satisfies the event notification rules.

[0133] For example, assuming that the judgment feature is set to a VIP user in a role (i.e., the judgment feature is set to "VIP user"), the first threshold is set to 15, and the second threshold is set to 25. When the number of parties with a "VIP user" role that send an operation request to the subscription service device 300 is equal to or greater than 15 and equal to or less than 25 (i.e., the first threshold 15 ≤ the number of parties with a "VIP user" role ≤ the second threshold 25), the event notification rule is satisfied, and a notification can be sent to the notified party.

[0134] Alternatively, in step S206, judging whether the participant information satisfies the event notification rule includes: counting the number of participants whose participant information is the same as the judgment feature; judging whether the number of participants satisfies the event notification rule; if the number of participants satisfies the event notification rule, determining that the participant information satisfies the event notification rule. Wherein, judging whether the number of participants satisfies the event notification rule includes: judging whether the number of participants is greater than or equal to a third threshold, and if so, determining that the number of participants satisfies the event notification rule; or, judging whether the number of participants is less than or equal to a fourth threshold, and if so, determining that the number of participants satisfies the event notification rule; or, judging whether the number of participants is greater than or equal to the third threshold and less than or equal to the fourth threshold, and if so, determining that the number of participants satisfies the event notification rule.

[0135] It is worth noting that the event notification rule may include the first threshold, the second threshold, the third threshold and / or the fourth threshold. The first threshold, the second threshold, the third threshold and / or the fourth threshold may be set while setting the event notification rule. Of course, the specific values ​​of the first threshold, the second threshold, the third threshold and / or the fourth threshold may be set by the subscriber, the subscription service provider or the notified party, and the present disclosure does not limit this.

[0136] The present invention also provides another method for notifying, comprising:

[0137] Receive subscription requests from subscribers and obtain event notification rules;

[0138] Determine whether the participant information meets the event notification rules, and if so, send a notification to the notified party.

[0139] Furthermore, it also includes: creating or directly acquiring a subscription resource after receiving the subscription request, wherein the subscription resource includes the event notification rule;

[0140] Acquiring the event notification rule includes: acquiring the event notification rule included in the subscription resource.

[0141] Wherein, the participant includes a registrant; the method further includes: receiving a registration request from the registrant, wherein the registration request includes the participant information; or

[0142] The participants include a requester; the method further includes: receiving an operation request from the third-party participant.

[0143] The participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role identification.

[0144] Figure 3 A schematic block diagram of a subscription service device 300 provided in an embodiment of the present disclosure. The subscription service device 300 is used to notify a notified party, and includes a determination unit 310 and a notification unit 320; the determination unit 310 is used to determine an event notification rule; the notification unit 320 is used to determine whether the participant information meets the event notification rule, and if so, send a notification to the notified party; wherein the participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role identification feature.

[0145] For example, the determining unit 310 may be specifically configured to determine the event notification rule from a subscription resource or from an event notification rule set.

[0146] For example, the subscription service device 300 further includes: a subscription resource creation unit 330, which is used to create a subscription resource, wherein the subscription resource includes the event notification rule.

[0147] For example, the subscription service device 300 further includes: a first receiving unit 340, configured to receive a subscription resource creation request sent by a subscriber before creating a subscription resource.

[0148] For example, the notification unit 320 is specifically used to determine whether the participant information matches the feature value. If so, it is determined that the participant information meets the event notification rule, and a notification is sent to the notified party.

[0149] For example, the subscription service device 300 further includes: a second receiving unit 350, configured to receive a subscription request sent by a subscriber to determine the event notification rule.

[0150] For example, the first receiving unit 340 is further configured to receive an operation request, wherein the operation request includes the participant information.

[0151] For example, the notification unit 320 may be specifically used to determine whether the participant information is different from the determination feature. If so, it is determined that the participant information satisfies the event notification rule and a notification is sent to the notified party.

[0152] For example, the notification unit 320 is specifically used to determine whether the participant information is equivalent to the judgment feature. If so, it is determined that the participant information meets the event notification rule and a notification is sent to the notified party.

[0153] For another example, the notification unit 320 is specifically used to: count the number of participants whose participant information is different from the judgment characteristics; judge whether the number of participants satisfies the event notification rules; if the number of participants satisfies the event notification rules, determine that the participant information satisfies the event notification rules, and send a notification to the notified party.

[0154] Alternatively, the notification unit 320 is specifically used to: count the number of participants whose participant information is the same as the judgment feature; determine whether the number of participants meets the event notification rule; if so, determine that the participant information meets the event notification rule and send a notification to the notified party.

[0155] For example, the judgment feature includes at least one of an identification, a role, an identification feature, and a role feature.

[0156] For example, the identification includes at least one of a subscriber identification, a subscribed party identification, a notified party identification, a participant identification, a subscriber preset identification, a subscribed party preset identification, a notified party preset identification and a participant preset identification; the role includes at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role and a participant preset role; the identification feature includes at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature and a participant preset identification feature; the role feature includes at least one of a subscriber role feature, a subscribed party role feature, a notified party role feature, a participant role feature, a subscriber preset role feature, a subscribed party preset role feature, a notified party preset role feature and a participant preset role feature.

[0157] Each unit of the subscription service device 300 may be configured to perform the following steps: Figure 2 The functions or steps of the method 200 shown in the figure are not described in detail in this disclosure. Figure 1 The processor 152 in the subscription service device 150 shown in the figure executes the program instructions stored in the memory 154 to implement and execute the steps in the method 200, as well as other steps not shown in the figure. Figure 2 The steps shown in .

[0158] An embodiment of the present disclosure also provides a notification subscription system, comprising: the subscription service device 300 as described above; a subscription device, configured to send a subscription creation request to the subscription service device and receive a response to the subscription creation request from the subscription service device; a participant device, configured to send an operation request to the subscription service device and receive a response to the operation request from the subscription service device; and a notified party device, configured to receive a notification from the subscription service device.

[0159] The subscription service device 300 may be arranged in the subscription service device 150 , the subscription device may be arranged in the subscription device 101 , the participant device may be arranged in the participant device 104 , and the notified party device may be arranged in the notified party device 106 .

[0160] Figure 4 A schematic diagram of a notification subscription process provided in an embodiment of the present disclosure.

[0161] First, the subscription device 404 sends a request to create a subscription resource to the subscription service device 300 (step 410). <subscription>The subscription resource creation request may include subscriber information (e.g., subscriber identification, subscriber role, etc.). In response to the subscription creation request, the subscription service device 300 creates the subscription resource. Specifically, it creates <subscription>, contains eventNotificationCriteria, eventNotificationCriteria contains fixedID parameter.

[0162] The subscription resource includes event notification rules eventNotificationCriteria (step 412).

[0163] The subscription service device 300 sends a response to the subscription creation request to the subscription device 404 (step 414).

[0164] The participant device 402 sends an operation request to the subscription service device 300 (step 416), such as a request for create, retrieve, update, delete, etc. The operation request may include participant information (eg, participant identification or participant role, etc.).

[0165] The subscription service device 300 sends a response to the operation request to the participant device 402 (step 418).

[0166] The subscription service device 300 determines whether the participant information satisfies the event notification rule. For example, the subscription service device 300 determines whether the participant information is different from the judgment feature (step 420). If the participant information is different from the judgment feature, the subscription service device 300 determines that the participant information satisfies the event notification rule (step 422). The subscription service device 300 sends a notification to the notified party device 406 (step 424). The notified party device 406 sends a response to the notification to the subscription service device 300 (step 426).

[0167] For example, after receiving the operation request, the subscription server detects the ID of the sender of the operation request, such as AE-ID, CSE-ID or resourceID, and compares it with the preset fixedID of the subscription resource. If they are the same, a notification (Notify) is sent to the notified party, and a response to the notification is received from the notified party.

[0168] Figure 5 A schematic diagram of another process of subscribing to notifications provided in an embodiment of the present disclosure.

[0169] First, the subscription device 404 sends a request to create a subscription resource to the subscription service device 300 (step 510), that is, the subscription direction sends a request to create a subscription resource to the subscribed party. <subscription>In response to the subscription creation request, the subscription service device 300 creates the subscription resource. Specifically, the subscription resource is created under <subscription>Sub-resource, including the roleNr parameter. The eventNotificationCriteria parameter includes the roleNrBigger and roleNrSmaller sub-parameters.

[0170] The subscription resource includes event notification rules eventNotificationCriteria (step 512). The subscription service device 300 sends a response to the subscription creation request to the subscription device 404 (step 514), that is, the subscribed party sends a creation request to the subscriber. <subscription>Response. The participant device 402 sends an operation request to the subscription service device 300 (step 516), such as the participant sending any of create / retrieve / update / delete requests to the subscribed party. The subscription service device 300 sends a response to the operation request to the participant device 402 (step 518), such as the subscribed party sending a response to any of create / retrieve / update / delete requests to the participant.

[0171] The subscription service device 300 determines whether the participant information satisfies the event notification rule. For example, the subscription service device 300 determines whether the participant information is the same as the judgment feature (step 520). If the participant information is the same as the judgment feature, the subscription service device 300 determines that the participant information satisfies the event notification rule (step 522). The subscription service device 300 sends a notification to the notified party device 406 (step 524). The notified party device 406 sends a response to the notification to the subscription service device 300 (step 526).

[0172] For example, after the subscriber accepts the request, if it detects whether the roleID is different from the roleID that has been saved, <subscription> / roleNr increases by 1 to determine whether roleNr is greater than roleNrBigger or less than roleNrSmaller. If so, the subscribed party sends a Notify request to the notified party; the notified party sends a Notify response to the subscribed party.

[0173] Figure 6 A schematic diagram of another process of subscribing to notifications provided in an embodiment of the present disclosure. First, the subscription device 404 sends a request to create a subscription resource to the subscription service device 300 (step 610). In response to the request to create a subscription resource, the subscription service device 300 creates the subscription resource, wherein the subscription resource includes an event notification rule (step 612). The subscription service device 300 sends a response to the subscription creation request to the subscription device 404 (step 614).

[0174] The participant device 402 sends an operation request to the subscription service device 300 (step 616). The operation request may include participant information (e.g., participant identification or participant role, etc.). The subscription service device 300 sends a response to the operation request to the participant device 402 (step 618).

[0175] The subscription service device 300 determines whether the participant information satisfies the event notification rule. For example, the subscription service device 300 counts the number of participants whose participant information is different from the judgment feature (step 619). For example, among all the participants who access the subscription service device 300, the subscription service device 300 records the number of participants whose participant information is different from the judgment feature, and the number of other participants whose participant information is the same as the judgment feature is not counted. The subscription service device 300 determines whether the number of the participants satisfies the event notification rule (step 620). If the number of the participants satisfies the event notification rule, the subscription service device 300 determines that the participant information satisfies the event notification rule (step 622). The subscription service device 300 sends a notification to the notified party device 406 (step 624). The notified party device 406 sends a response to the notification to the subscription service device 300 (step 626).

[0176] An example of a subscription notification is as follows. For example, a subscriber subscribes to an energy notification service through a subscription device 101 (or a subscription device 404) to a subscription service device 300 (e.g., an energy management platform) to manage energy consumption (such as electricity) at home. The home appliances in the subscriber's home can all be participant devices 104, and can all be registered with the energy management platform in the subscription service device 150. One of the purposes of registration is to allow the user terminal to control and manage the home appliances through the energy management platform. After registration is completed, the subscriber can subscribe to the energy notification service through the subscription device 101 to the subscription service device 300 (e.g., an energy management platform). The notification service of this subscription is that if more than 10 home appliances consume electricity in one night, an energy consumption notification is sent to another family member (the notified party, different from the subscriber). Because the home appliances will send an update request to the energy management platform after consuming electricity, requesting to modify the value of the corresponding resource on the energy management platform, so when more than the 10th home appliance modifies the resource value on the energy management platform in one night, the energy management platform will send a notification to another family member (the notified party).

[0177] Figure 7 A schematic diagram of an exemplary subscription resource structure provided by the embodiment of the present disclosure. After the participant is registered by the subscriber, an application entity resource (such as Figure 7 shown <ae>Resources), the application entity resources include container resources ( <container>Resources). Container resources include content subresources (such as Figure 7 shown <contentinstance>), the content sub-resource can be used to store information content.

[0178] When a subscriber sends a subscription request to a subscribed party (for example, the request indicates that the subscription application entity resource <ae>The subscriber is under the application entity resource / container resource (i.e., Figure 7 In <ae> / <container>Resources) to create a subscription resource (that is, Figure 7 In <subscription>The subscription resource includes event notification rules (eventNotificationCriteria), notification URI, group ID, notification forwarding URI, subscriber URI, etc. The subscription resource may also include other Figure 7 The content items shown in the present disclosure are not limited here.

[0179] The present disclosure provides a notification method, device and system, which implement subscription notification based on specific participants. When the subscription service detects a specific participant, it sends a notification message to the notified party, thus implementing a notification service based on the participant and meeting the differentiated needs of users.

[0180] In this article, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0181] Obviously, those skilled in the art can make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.

[0182] The above description is only a specific embodiment of the disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.< / subscription> < / container> < / ae> < / ae> < / contentinstance> < / container> < / ae> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription> < / subscription>

Claims

1. A method for sending notifications by a subscription service device in an Internet of Things, wherein: The Internet of Things includes a participant, a subscriber, and a notified party, and the method includes: Determine an event notification rule, wherein a subscription resource includes the event notification rule, and the subscription resource is created in response to the subscriber sending a request to create a subscription resource; Determine whether the participant information of the participant satisfies the event notification rule, and if so, send a notification to the notified party; wherein the participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role feature of the participant role; Wherein, judging whether the participant information satisfies the event notification rule includes: Determining whether the participant information matches the feature value, and if so, determining that the participant information satisfies the event notification rule; The characteristic value includes at least one of a value indicating a data type, a value indicating a data structure, and a value indicating data content.

2. The method according to claim 1, further comprising: Receiving the subscription resource creation request sent by the subscriber; The subscription resource is created, wherein the subscription resource includes the event notification rule.

3. The method according to claim 1, further comprising: A subscription request sent by the subscriber is received to determine the event notification rule.

4. The method according to claim 1, further comprising: An operation request is received, wherein the operation request includes the participant information.

5. The method according to claim 1, further comprising: A registration request is received, wherein the registration request includes the participant information.

6. The method according to claim 1, wherein: Determining whether the participant information satisfies the event notification rule includes: Determine whether the participant information is different from the determination feature, and if so, determine that the participant information satisfies the event notification rule.

7. The method according to claim 1, wherein: Determining whether the participant information satisfies the event notification rule includes: Determine whether the participant information is equivalent to the determination feature, and if so, determine whether the participant information satisfies the event notification rule.

8. The method according to claim 1, wherein: Determining whether the participant information satisfies the event notification rule includes: Count the number of participants whose information is different from the judgment characteristics; Determining whether the number of the participants satisfies the event notification rule; If the number of the participants satisfies the event notification rule, it is determined that the participant information satisfies the event notification rule.

9. The method according to claim 8, wherein: Determining whether the number of the participants satisfies the event notification rule includes: Determine whether the number of the participants is greater than or equal to a first threshold, and if so, determine that the number of the participants satisfies the event notification rule; or Determine whether the number of the participants is less than or equal to a second threshold, and if so, determine that the number of the participants satisfies the event notification rule; or It is determined whether the number of the participants is greater than or equal to a first threshold and less than or equal to a second threshold. If so, it is determined that the number of the participants satisfies the event notification rule.

10. The method according to claim 1, wherein: Determining whether the participant information satisfies the event notification rule includes: Count the number of participants whose participant information and judgment characteristics are the same; Determining whether the number of the participants satisfies the event notification rule; If so, it is determined that the participant information satisfies the event notification rule.

11. The method according to claim 10, wherein: Determining whether the number of the participants satisfies the event notification rule includes: Determine whether the number of the participants is greater than or equal to a third threshold, and if so, determine that the number of the participants satisfies the event notification rule; or Determining whether the number of the participants is less than or equal to a fourth threshold, and if so, determining that the number of the participants satisfies the event notification rule; or It is determined whether the number of the participants is greater than or equal to a third threshold and less than or equal to a fourth threshold. If so, it is determined that the number of the participants satisfies the event notification rule.

12. The method according to any one of claims 6 to 11, wherein: The judgment feature includes at least one of an identification, a role, an identification feature and a role feature.

13. The method according to claim 12, wherein: The identifier includes at least one of a subscriber identifier, a subscribed party identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscribed party preset identifier, a notified party preset identifier, and a participant preset identifier; The role includes at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role and a participant preset role; The identification feature includes at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature, and a participant preset identification feature; The role characteristics include at least one of a subscriber role characteristic, a subscribed party role characteristic, a notified party role characteristic, a participant role characteristic, a subscriber preset role characteristic, a subscribed party preset role characteristic, a notified party preset role characteristic and a participant preset role characteristic.

14. The method according to claim 1, wherein: The participant identification feature includes a structural feature of the participant identification or a content feature of the participant identification.

15. A device for sending notifications in an Internet of Things, wherein: The Internet of Things includes a participant, a subscriber, and a notified party, and the device includes: A determining unit, configured to determine an event notification rule, wherein a subscription resource includes the event notification rule, and the subscription resource is created in response to the subscriber sending a subscription resource creation request; a notification unit, configured to determine whether the participant information of the participant satisfies the event notification rule, and if so, send a notification to the notified party; wherein the participant information includes at least one of a participant identification, a participant identification feature, a participant role, and a participant role identification of the participant role; The notification unit is used to determine whether the participant information matches the feature value, and if so, determine that the participant information meets the event notification rule, and send a notification to the notified party; The characteristic value includes at least one of a value indicating a data type, a value indicating a data structure, and a value indicating data content.

16. The apparatus according to claim 15, further comprising: A first receiving unit, configured to receive a request for creating a subscription resource sent by the subscriber; The subscription resource creation unit is used to create the subscription resource, wherein the subscription resource includes the event notification rule.

17. The apparatus according to claim 15, further comprising: The second receiving unit is configured to receive a subscription request sent by the subscriber to determine the event notification rule.

18. The device according to claim 16, wherein: The first receiving unit is further used to receive an operation request, wherein the operation request includes the participant information; or is further used to receive a registration request, wherein the registration request includes the participant information.

19. The device according to claim 15, wherein: The notification unit is used to determine whether the participant information is different from the judgment feature. If so, it is determined that the participant information meets the event notification rule and a notification is sent to the notified party.

20. The device according to claim 15, wherein: The notification unit is used to determine whether the participant information is equivalent to the judgment feature. If so, it is determined that the participant information meets the event notification rule and a notification is sent to the notified party.

21. The device according to claim 15, wherein: The notification unit is used to: count the number of participants whose participant information is different from the judgment feature; Determining whether the number of the participants satisfies the event notification rule; If the number of the participants meets the event notification rule, it is determined that the participant information meets the event notification rule, and a notification is sent to the notified party.

22. The device according to claim 15, wherein: The notification unit is used for: Count the number of participants whose participant information and judgment characteristics are the same; Determining whether the number of the participants satisfies the event notification rule; If so, it is determined that the participant information satisfies the event notification rule, and a notification is sent to the notified party.

23. The device according to any one of claims 19 to 22, wherein: The judgment feature includes at least one of an identification, a role, an identification feature and a role feature.

24. The device according to claim 23, wherein: The identifier includes at least one of a subscriber identifier, a subscribed party identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscribed party preset identifier, a notified party preset identifier, and a participant preset identifier; The role includes at least one of a subscriber role, a subscribed party role, a notified party role, a participant role, a subscriber preset role, a subscribed party preset role, a notified party preset role and a participant preset role; The identification feature includes at least one of a subscriber identification feature, a subscribed party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscribed party preset identification feature, a notified party preset identification feature, and a participant preset identification feature; The role characteristics include at least one of a subscriber role characteristic, a subscribed party role characteristic, a notified party role characteristic, a participant role characteristic, a subscriber preset role characteristic, a subscribed party preset role characteristic, a notified party preset role characteristic and a participant preset role characteristic.

25. The device according to claim 15, wherein: The participant identification feature includes a structural feature of the participant identification or a content feature of the participant identification.

26. A system for sending notifications in an Internet of Things, wherein: The system comprises: The device according to any one of claims 15 to 25, wherein the device is a subscription service device; A subscription device, configured to send a subscription creation request to the subscription service device; A participant device configured to send an operation request to the subscription service device; and The notified party device is configured to receive a notification from the subscription service device.

Images