WO2018019281A1 - Method, apparatus and system for notification - Google Patents

Abstract

A method, apparatus and system for notification. The method comprises: determining an event notification rule (S1001); determining whether participant information satisfies the event notification rule (S1002); and if so, sending a notification to a notified party (S1003), wherein the participant information comprises at least one of a participant identifier, a participant identifier feature, a participant role and a participant role feature. When a subscription server detects a participant that satisfies the participant information, a notification message is sent to a notified party, thereby realizing the notification service based on the participant and satisfying the requirement of user differentiation.

Description

Method, device and system for notifying Technical field

Embodiments of the present disclosure are directed to a method, apparatus, and system for making a notification.

Background technique

With the development of the Internet of Things technology, the application fields of various Internet of Things have been rapidly developed, and many private agreements have emerged. Because the proprietary protocols are not fully compatible, it may hinder the development of Internet of Things technology.

A subscription notification mechanism is defined in the Internet of Things communication protocol, and the subscription direction is sent by the subscriber to send a subscription request, and when the event occurs, a notification is sent to the notified party.

Summary of the invention

Embodiments of the present disclosure provide a method, apparatus, and system for making notifications.

The method for performing notification includes:

Determining an event notification rule; determining whether the participant information satisfies the event notification rule, and if yes, sending a notification to the notified party; wherein the participant information includes a participant identifier, a participant identification feature, a participant role, and a participant At least one of the character characteristics.

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

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

The event notification rule is determined from an event notification rule set.

For example, it also includes:

A subscription resource is created, and the event notification rule is included in the subscription resource.

For example, before the creating the subscription resource, the method further includes: receiving a request to create a subscription resource sent by the subscriber.

For example, determining 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.

For example, the method further includes: receiving a subscription request sent by the subscriber to determine the event notification rule.

For example, the method for performing notification further includes: receiving an operation request, wherein the operation request includes the participant information.

For example, the method for performing notification further includes: receiving a registration request, wherein the registration request includes the participant information.

For example, determining whether the participant information satisfies the event notification rule includes: determining whether the participant information is different from the determination feature, and if yes, determining that the participant information satisfies the event notification rule.

For example, determining whether the participant information satisfies the event notification rule includes: determining whether the participant information is equivalent to the determination feature, and if yes, determining that the participant information satisfies the event notification rule.

For example, determining whether the participant information satisfies the event notification rule includes: counting the number of participants having the participant information different from the judgment feature; determining whether the number of the participants meets the event notification rule; The number of participants satisfies the event notification rule, and it is determined that the participant information satisfies the event notification rule.

For example, determining whether the number of the participants meets the event notification rule includes: determining whether the number of the participants is greater than or equal to a first threshold, and if yes, determining that the number of the participants meets the event notification rule 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 participants meets the event notification rule; or determining whether the number of participants is greater than or equal to a first threshold and It is less than or equal to the second threshold, and if so, it is determined that the number of the participants satisfies the event notification rule.

For example, determining whether the participant information satisfies the event notification rule includes: counting the number of participants having the same participant information and the determination feature; determining whether the number of the participants meets the event notification rule; And determining that the participant information satisfies the event notification rule.

For example, determining whether the number of the participants meets the event notification rule includes: determining whether the number of the participants is greater than or equal to a third threshold, and if yes, determining that the number of the participants meets 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 participants meets the event notification rule; or determining whether the number of participants is greater than or equal to a third threshold and Less than or equal to the fourth threshold, and if so, The number of the participants is determined to satisfy the event notification rule.

For example, the determination feature includes at least one of an identification, a character, an identification feature, and a character feature.

For example, the identifier includes a subscriber identifier, a subscriber identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscriber preset identifier, a notified party preset identifier, and a participant preset identifier. At least one of the roles; the role includes a subscriber role, a subscriber role, a notified party role, a participant role, a subscriber preset role, a subscriber preset role, a notified party preset role, and a participant At least one of the roles; the identity feature includes a subscriber identity feature, a subscriber identity feature, a notified party identity feature, a party identity feature, a subscriber preset identity feature, a subscriber default tag feature, At least one of a notified party preset identification feature and a participant preset identification feature; the role feature includes a subscriber role feature, a subscriber role feature, a notified party role feature, a participant role feature, and a subscriber pre- At least one of a character feature, a predetermined role feature of the subscriber, a preset role feature of the notified party, and a preset role feature of the participant are set.

An embodiment of the present disclosure further provides an apparatus for performing notification, including: a determining unit, configured to determine an event notification rule; a notification unit, configured to determine whether the participant information satisfies the event notification rule, and if yes, to the notified party Sending the notification; wherein the participant information includes at least one of a participant identifier, a participant identification feature, and a participant role and a participant role identifier.

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.

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.

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

For example, the notification unit is specifically configured to determine whether the participant information matches the feature value, and if yes, determine that the participant information satisfies the event notification rule, and then send a notification to the notified party.

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

For example, the first receiving unit is further configured to receive an operation request, where the operation request is The participant information is included.

For example, the notification unit is specifically configured to determine whether the participant information is different from the determination feature, and if yes, determine that the participant information satisfies the event notification rule, and send a notification to the notified party.

For example, the notification unit is specifically configured to determine whether the participant information is equivalent to the determination feature, and if yes, determine that the participant information satisfies the event notification rule and send a notification to the notified party.

For example, the event notification unit is specifically configured to: count the number of participants having the participant information different from the judgment feature; determine whether the number of the participants meets the event notification rule; if the number of the participants meets The event notification rule determines that the participant information satisfies the event notification rule and sends a notification to the notified party.

For example, the notification unit is specifically configured to: count the number of participants having the same participant information and the determination feature; determine whether the number of the participants meets the event notification rule; if yes, determine the participant information The event notification rule is satisfied, and a notification is sent to the notified party.

For example, the determination feature includes at least one of an identification, a character, an identification feature, and a character feature.

For example, the identifier includes a subscriber identifier, a subscriber identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscriber preset identifier, a notified party preset identifier, and a participant preset identifier. At least one of the roles; the role includes a subscriber role, a subscriber role, a notified party role, a participant role, a subscriber preset role, a subscriber preset role, a notified party preset role, and a participant At least one of the roles; the identity feature includes a subscriber identity feature, a subscriber identity feature, a notified party identity feature, a party identity feature, a subscriber preset identity feature, a subscriber default tag feature, At least one of a notified party preset identification feature and a participant preset identification feature; the role feature includes a subscriber role feature, a subscriber role feature, a notified party role feature, a participant role feature, and a subscriber pre- At least one of a character feature, a predetermined role feature of the subscriber, a preset role feature of the notified party, and a preset role feature of the participant are set.

An embodiment of the present disclosure also provides a system for performing notification, including:

Any of the devices described above, the device being 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;

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

Embodiments of the present disclosure provide a method, apparatus, and system for making notifications based on specific parameters Implement a subscription notification with the party. Specifically, after the subscription service party detects that the specific participant meets the event notification rule party, the notification message is sent to the notified party, where the specific participant is: the participant information includes the participant identifier and the participant role. At least one of the participants. In this way, the notification service based on the specific participant is realized, and the demand for user differentiation is satisfied.

DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only the present invention. Some embodiments, rather than the limitations of the present disclosure, may be obtained by those skilled in the art from the drawings without departing from the scope of the invention.

1 is a hardware schematic block diagram of a system for subscription notification provided by at least one embodiment of the present disclosure;

2 is a flowchart of a method for performing notification according to at least one embodiment of the present disclosure;

FIG. 3 is a schematic block diagram of an apparatus for subscribing to a service according to at least one embodiment of the present disclosure;

4 is a schematic diagram of a process for subscribing to a notification according to at least one embodiment of the present disclosure;

5 is a schematic diagram of a process of subscribing to a notification provided by at least one embodiment of the present disclosure;

6 is a schematic diagram of a process of subscribing to a notification provided by at least one embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of an exemplary subscription resource according to at least one embodiment of the present disclosure;

FIG. 8 is a flowchart of a method for performing notification according to at least one embodiment of the present disclosure.

Reference mark:

Subscribing device 101; participant device 104; notified party device 106; subscription service device 150; processor 152; memory 154; network 160; subscription service device 300; subscription resource creation unit 330; event notification unit 320; first receiving unit 340; second receiving unit 350; participant device 402; subscription device 404; notified party device 406.

detailed description

In order to make the objects, technical solutions and advantages of the present disclosure more clear, the following embodiments are directed to the present disclosure. For further details. It is apparent that the described embodiments are only a part of the embodiments of the present disclosure, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

In the related art, the subscription direction subscription service party (also referred to as the subscriber or the notifier) sends a subscription request, and the subscription request may indicate that when the event occurs, the subscription service party sends a message to the notified party. The subscriber and the notified party can be the same entity or different entities. The rule in which the event occurs is defined under the subscribed resource (for example, the <subscription> resource is created under the subscribed resource, and the event notification rule is included in the eventNotificationCriteria parameter of the <subscription> resource). When the event notification rule is met, the subscription service direction is sent by the notifying party. For example, the parameters of the event notification rule include, but are not limited to, the parameters listed in Table 1:

Table 1

The current subscription mechanism does not take into account the different situations of participating entities (eg, subscribers, parties, notified parties, etc.). In practical applications, when the notified party wishes to perform a corresponding action based on a specific participant (for example, when a certain party performs an operation), the subscribing service party can send a message to the notified party. Existing subscription notification mechanisms do not meet these requirements. The special A predetermined participant can be understood as: a participant other than the subscriber, the subscriber, and the notified party; the other party can perform operations such as updating, deleting, creating, and the like. Of course, the participant and the subscriber, the subscriber or the notified party may be the same entity or different entities.

Embodiments of the present disclosure provide a method, apparatus, and system for making a notification, implementing a notification, such as a subscription, based on a particular participant. Specifically, when the subscription service party detects a specific participant, the notification message is sent to the notified party, and the notification service based on the participant is implemented, and the user differentiated requirement is satisfied.

Specifically, embodiments of the present disclosure provide a method, apparatus, and system for performing notification (Notify), implementing notification based on a specific participant. Specifically, after the subscription service party detects that the specific participant meets the event notification rule party, the notification message is sent to the notified party. For example, when the subscription service party detects that the specific party information satisfies the event notification rule, it sends a notification message to the notified party.

For example, the event notification rule is an event notification condition (eventNotificationCriteria conditions), and the event notification rule may be an event notification rule set, and the event notification rule set may include one or more sub-conditions. When it is judged that the participant information satisfies the event notification rule, it may be determined that the participant information satisfies any one of the sub-conditions, or all sub-conditions are satisfied.

For example, the participant information includes at least one of a participant identifier, a participant role, a participant role feature, and a participant identification feature.

In this way, the notification service based on the specific participant is realized, and the demand for user differentiation is satisfied.

The following is a description of the method, device, and system for notification during the subscription process.

FIG. 1 is a schematic block diagram of hardware of a system 100 for performing notification according to an embodiment of the present disclosure. As shown in FIG. 1, the system 100 can include a subscription device 101, a participant device 104, a notified party device 106, and a subscription service device 150 (a subscription service device is a notification device that performs notification). Devices in system 100 can be connected by network 160. Devices of system 100 can communicate with each other directly or indirectly, for example, devices of system 100 can transmit and receive data and/or signals to each other over network 160.

The network 160 can be a network capable of interconnecting common objects having independent functions. Network 160 may be a wireless network, although network 160 may also include a wired network. E.g, Network 160 may be an Internet of Things based Internet and/or telecommunications network. Each user can use an electronic tag to connect ordinary objects to the Internet of Things. Therefore, the specific location of each common physics can be found on the Internet of Things. Through the Internet of Things, central machines can be used to centrally manage and control various machines and devices. For example, remote control of home devices (eg, smart refrigerators, smart microwave ovens, etc.), automobiles, and the like, as well as searching for their location and the like.

The subscription service device 150 (ie, the notification device) can be a computing device that includes a processor and a memory. For example, the subscription service device 150 can be a server. Of course, the subscription service device 150 can also be a desktop computer, a notebook computer, a smart phone, a tablet computer, and other devices including a processor and a memory. FIG. 1 shows subscriber server 150 including processor 152 and memory 154.

Processor 152 can process data signals and can include various computing structures, such as a Complex Instruction Set Computer (CISC) architecture, a Structured Reduced Instruction Set Computer (RISC) architecture, or a structure that implements a combination of multiple instruction sets. In some embodiments, processor 152 can also be a microprocessor, such as an X86 processor or an ARM processor, or can be a digital processor (DSP) or the like. The processor 152 can control other components in the subscription service device 150 to perform the desired functions.

Memory 154 can hold instructions and/or data executed by processor 152. For example, memory 154 can include one or more computer program products, which can include various forms of computer readable storage media, such as volatile memory and/or nonvolatile memory. The volatile memory may include, for example, a random access memory (RAM) and/or a cache or the like. The nonvolatile memory may include, for example, a read only memory (ROM), a hard disk, a flash memory, or the like. One or more computer program instructions can be stored on the computer readable storage medium, and the processor 152 can execute the program instructions to implement the functionality of the subscription notifications described below and/or other desired functionality. Various applications and various data may also be stored in the computer readable storage medium, such as various data used and/or generated by the application, and the like.

Subscription device 101 can be a computing device that includes a processor and a memory. For example, the subscription device 101 can be a television, a desktop computer, a notebook computer, a smart phone, a tablet computer, a game controller, a music player (eg, an mp3 player, etc.), and other terminals including a processor and a memory (eg, a mobile terminal, Intelligent Terminal). In some embodiments, the subscription device 101 can include a processor, memory, and other components such as input devices and output devices.

Participant device 104 can be a computing device that includes a processor and a memory. For example, the participant device 104 can be a television, a smart home appliance, a charging car, a desktop computer, a laptop battery Brains, smartphones, tablets, and other terminals including processors and memories (eg, mobile terminals, smart terminals). In some embodiments, the participant device 104 can include a processor, memory, and other components such as input devices and output devices.

The notifier device 106 can be a computing device that includes a processor and a memory. For example, the notified party device 106 can be a television, a smart home appliance, a charging car, a desktop computer, a laptop, a smartphone, a tablet, a game controller, a music player (eg, an mp3 player, etc.), and others including a processor and A terminal of a memory (for example, a mobile terminal, a smart terminal). In some embodiments, the notifier device 106 can include a processor, memory, and other components such as input devices and output devices.

In some embodiments, the subscriber and the notified party may be the same entity or different entities. Participants and subscribers can be the same entity or different entities; if they are the same entity, the entity is an entity that has both a subscriber and a participant role, and can subscribe and third-party operations simultaneously. Of course, the subscriber, the notified party, and the participant may also be entities that are different from each other.

In some embodiments, the subscriber operates on the subscription device 101 and sends a subscription creation request to the subscription service device 150. In the case of no ambiguity, the subscriber described in the embodiment of the present disclosure may refer to the subscription device 101, the subscriber operating the subscription device 101, or the subscription device 404 installed in the subscription device 101 described below.

The operator can operate on the participant device 104 to send an operation request to the subscription service device 150. Of course, the participant device 104 can also automatically send an operation request to the subscription service device 150 without human intervention. Without ambiguity, the participants described in the embodiments of the present disclosure may refer to the participant device 104, the operator operating the participant device 104, or the participant device 402 installed on the participant device 104 described below.

The notified person can operate on the notified device 106, for example, the notified person can read the notification from the subscription service device 150 by the notified device 106. The notified party described in the embodiment of the present disclosure may refer to the notified device 106, the notified person who operates the notified device 106, or the notified party device installed on the notified device 106 described below, without causing ambiguity. 406.

The service provider can operate on the subscription service device 150 to send a notification to the notified party. Of course, the subscription service device 150 can also automatically send a notification to the notified party when the event notification rule is satisfied without human intervention. The subscription service described in the embodiment of the present disclosure without ambiguity The service party may refer to the subscription service device 150, the service provider operating the subscription service device 150, or the subscription service device 300 installed on the subscription service device 150 described below (the subscription service device is the notification device that performs the notification).

In some embodiments, each device of system 100 may also include a display device (eg, an LCD, OLED, or projection device), an input device (eg, a touch device, a keyboard, a microphone, a mouse, etc.), a speaker or a vibrating device, etc., as desired.

An embodiment of the present disclosure provides a method for performing notification in a subscription scenario. As shown in FIG. 8, the method includes:

Step S1001 includes: determining an event notification rule; step S1002 includes: determining whether the participant information satisfies the event notification rule, and if yes, sending a notification to the notified party; wherein the participant information includes a participant identifier, a participant identifier At least one of a feature, a participant role, and a participant role identifier. Step S1003 includes: if the participant information satisfies the event notification rule, sending a notification to the notified party.

The method provided by the embodiment of the present disclosure may be based on the participant information, in particular, the matching relationship between the participant information and the event notification rule based on the participant identifier, the participant identification feature, the participant role, the participant role identifier, and the like. To determine whether to notify, meet the notification needs of more users or participants.

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

For example, in some embodiments, the rule in which the event occurs is defined under the subscription resource, that is, the event notification rule (ie, the event notification condition, eventNotificationCriteria) is included in the subscription resource, and a subscription resource may correspond to the event notification under the resource. rule. When the event notification rule is determined, the event notification rule may be determined from the subscription resource, for example, the event notification rule in the subscription resource is directly selected as an event notification rule that needs to be determined.

For another example, in other embodiments, the event notification rule is not included in the subscription resource, but is set independently in the event notification rule set outside the subscription resource, and the event notification rule set may include one or more Event notification rules. When the event notification rule is determined, one or more event notification rules may be determined from the event notification rule set as the event notification rule to be determined.

Determining an event notification rule from a subscription resource, including: may include a notification rule from the event The event notification rule is obtained in the subscription resource, and the event notification rule in the subscription resource can be directly matched without obtaining. The event notification rule may be obtained by directly acquiring one or more event notification rules from the event notification rule set, or may directly match the event notification rule in the event notification rule set, so as to determine whether the event notification rule is satisfied when the participant information is obtained. .

In some embodiments, the subscription resource may be a subscription resource created for the create subscription resource request after receiving a request to create a subscription resource sent by the subscriber. For example, when a request for creating a <subscription> resource is initiated by an AE or a CSE, the corresponding subscribing party creates a subscription resource including an event notification rule according to the request to create a <subscription> resource. The subscription resource corresponding to the subscription resource request may be determined in the created subscription resource for the subscription resource request when receiving the subscription resource request sent by the subscriber.

For example, the determining the event notification rule may be performed after receiving a subscription request sent by a subscriber. For example, when the participant and the subscriber are UPNP CP, the subscriber is the UPNP Client, and the notified party is the UPNP Device, the subscription direction is sent by the subscriber to the subscription request, and the subscription request carries the URL of the subscriber, the service identifier. And the URL of the notified party, after the subscriber receives the subscription request, the subscriber matches the subscription resource, and the subscription resource may be determined according to a pre-configured event notification rule, and then 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 (for example, the participant ID), and after receiving the action request, the subscriber determines whether the participant information satisfies the pre-configured notification rule. (For example, it is determined whether the ID of the participant satisfies the notification rule). If the participant information satisfies the pre-configured notification rule, the notification is sent to the notified party.

It should be noted that in some embodiments of the present disclosure, the participant may be understood as a participant other than the subscriber, the subscriber, and the notified party.

In some IoT communication protocols (such as the M2M protocol), an originator and a receiver are defined from the dimension of information interaction. The party that initiated the request is called the originator. The originator can be an AE (application entity) or a CSE (public service entity). The party receiving the request is called the receiver (Receiver), and the receiver can be the CSE.

For example, if the initiator initiates the creation of a <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, Hosting CSE is used to refer to the subscriber because it is not defined by the subscriber. For another example, if the originator initiates the registration request, the initiator becomes the registrant and the corresponding receiver It is the registered party.

For another example, if the initiator initiates an operation request, the initiator becomes an operation requester (referred to as a requester), and the receiver becomes an operation request recipient. The registrant, the subscriber, and the operation requester may perform different roles for different actions for the same entity, or perform different actions for different entities. In this embodiment, the participant, the subscribing party, the subscribing party, and the notified party may perform different roles for different actions for the same entity, or may be different entities that perform different actions, if the participant sends The registration request is the registrant, and if the participant sends the operation requester, it becomes the operation requester.

Optionally, determining whether the participant information meets the event notification rule specifically includes: determining whether the participant information matches a specified value, and if yes, determining that the participant information meets the event Notification rules.

For example, the feature value is a specific value, and the specific value may be configured in the subscription resource or may be configured outside the subscription resource. The subscription resource is provided when it is determined whether the participant information satisfies an event notification rule. The specific value may refer to a value of a data type, a value of a data structure, a value of a data content, etc., for example, the specific value may be an identified content feature (eg, 1111-22). For example, the determining whether the participant information matches the specified value comprises: determining whether the participant information is equal to the feature value, whether it is greater than the feature value, whether it is less than the feature value, or the number of participant information. Whether it is greater than the number of the feature values, whether the data is equal to the feature value, whether the data is smaller than the feature value, or the like, and the matching manner in which the participant information matches the feature value is configured according to the application scenario. For example, when it is desired to notify the notified party when the number of participants exceeds a certain value, the matching manner may be configured to determine the number of identifiers of the participant, and when the number of the identifiers is greater than the specific value, the notified party is notified.

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

The feature that identifies the feature is an identified feature, which may be a structural feature of the identity, and/or a content feature of the identity. For example, the identifier of the entity A is AAAA-AA, the identifier of the entity B is AAAA-BB, and the structures of the two identifiers are all in the form of XXXX-YY, and the structural features of the two are the same. The identifier AAAA-AA includes a character A, and the identifier AAAA-BB includes two characters A and B. It can be seen that the identification content characteristics of the two identifiers are different.

The roles and role characteristics are similar. The role refers to the role itself. The character characteristics refer to the characteristics of the character, which will not be detailed here.

Based on the subscription application scenario, before determining the event notification rule, the foregoing method further includes: receiving a subscription request sent by the subscriber. This can determine an event notification rule based on the subscription request. Since the subscription resource corresponding to the subscription request can be determined after receiving the subscription request, for example, the pre-stored subscription resource can be obtained locally or a subscription resource can be created. Generally, the event notification rule is included in the determined subscription resource. When the event notification rule is determined, the event notification rule can be obtained from the subscription resource.

The specific process of the notification method in the embodiment of the present disclosure is described below by taking the example of creating a subscription resource after receiving the subscription request.

FIG. 2 is a schematic flowchart of a method 200 for performing notification according to an embodiment of the present disclosure. In some embodiments, method 200 can include some or all of the steps shown in FIG. 2 (eg, some or all of steps 202, 204, 206, and 208). Of course, method 200 can also include other steps not shown in FIG.

Step S202 includes receiving a subscription creation request from a subscriber (ie, creating a subscription resource request or creating a <subscription> resource request).

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

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

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

The method 200 further includes:

After the subscriber creates the subscription resource, the subscriber receives the operation request, and the operation request includes the participant information; or the subscriber receives the registration request, and the registration request includes the participant information. Specifically, the operation request is an operation request from the participant (ie, the operation requester); the registration request is a registration request from the registrant. Considering the actual scenario, what needs to be monitored is the operation of other devices than the registrant, the registrant, and the notified party, and the subscribing party can be configured to receive an operation request from the participant, according to the operation. Request The participant information carried in (for example, the ID of the operation requester, and the participant is the operation requester at this time) determines whether the event notification rule is satisfied.

Considering the actual scenario, if it is necessary to know whether a new device is registered, the subscribing party may be configured to receive the registration request from the registrant according to the participant information carried in the registration request (for example, the registrant's ID, At this time, the participant is the registrant) to determine whether the event notification rule is satisfied.

Under some IoT protocols (eg, M2M protocol), the registrant and the subscriber may be different roles of the same entity in performing different actions.

For example, after a specific entity A (registered party) initiates a registration request to another entity B (registered party) and successfully registers, entity A can send a request to create a subscription resource to entity B, where entity A is a subscriber, entity B is the subscribing party, and entity B creates a subscription resource for entity A, that is, the subscription is successful.

For example, when the entity A sends a registration request and a subscription resource request to the entity B, after the registration is successful and the subscription is successful, and the entity D registers with the entity B, it can be determined whether the ID of the entity D is equal to the ID of the registered device. That is, it is determined whether the ID of the entity D is equal to the ID of the entity A (in this case, the ID of the entity A is a feature value, a specified value), and if not, the notified party has a new device registration.

For another example, when the entity A sends a registration request and a subscription resource request to the entity B, after the registration is successful and the subscription is successful, the entity C sends the registration request to the entity B, and after the registration is successful, the operation request is sent to the entity B, and the entity is determined. Whether the ID carried in the operation request of C is greater than 10 (in this case, the value 10 is a characteristic value, a specified value), and if it is greater than, the notified party has 10 devices requesting to perform an operation.

Further, after receiving the operation request, the participant is sent a response to the operation request to the participant, or sends a response to the registration request to the registrant.

For example, the operation request can be a create request, a get request, an update request, a delete request, or other type of request. The operation request may include information of the party (abbreviation, party information). For example, the participant information includes at least one of a participant identifier (ID), a participant role, a participant identification feature, and a participant role feature.

In some embodiments, all participants can be classified according to role or character characteristics. Taking the participant information as the participant role as an example, all participants can be classified into administrators, ordinary users, VIP users, and other users. The participant role indicates that the participant is an administrator, Ordinary user, VIP user, or other user. The role of the participant is characterized by the identity of the user.

In some embodiments, each participant identifier may be one of an application entity ID (AE-ID), a common service entity identifier (CSE-ID), or a resource identifier (resource ID). Kind. The participant identifier records that the participant is an application entity identifier, a general service entity identifier or a resource identifier, and a specific number thereof. For example, the participant ID is 1234ABC.

In some embodiments, the party information may be a participant identification feature. For example, if the participant ID is 1234ABC, the identification feature is four consecutive digits + three consecutive letters.

In some embodiments, in step S204, creating the subscription resource comprises: creating the subscription resource in response to the creating a subscription resource request; and setting an event notification rule of the subscription resource. For example, the judgment feature of the event notification rule may be set (the judgment feature is the feature value, that is, the specified value). The determining feature can include at least one of an identification, a character, an identification feature, and a character feature. The identifier may include a subscriber identifier, a subscriber identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscriber preset identifier, a notified party preset identifier, and a participant preset identifier. At least one. The role may include a subscriber role, a subscriber role, a notified party role, a participant role, a subscriber preset role, a subscriber preset role, a notified party preset role, and a participant preset role. At least one. The identification feature may include a subscriber identity feature, a subscriber identity feature, a notified party identity feature, a participant identity feature, a subscriber preset identity feature, a subscriber preset identity feature, and a notified party preset identity feature. And at least one of the participant preset identification features. The role may include a subscriber role feature, a subscriber role feature, a notified party role feature, a participant role feature, a subscriber preset role feature, a subscribed preset role feature, a notified party preset role feature, and The participant presets at least one of the character characteristics.

For example, the judgment feature may be set as a subscriber identity, a preset identity, or a notified party identity. For another example, the judgment feature may be set as a subscriber role, a preset role, or a notified party role. For another example, the determining feature may include: a subscriber identity 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 determination feature can also be set as other feature values, and the disclosure is not limited herein.

In step S206, in some embodiments, determining whether the participant information satisfies the event notification rule comprises: determining whether the participant information is different from the determining feature; and if The participant information is different from the determining feature, and the participant information is determined to satisfy the event notification rule.

For example, the determining feature may be a subscriber identity, and may determine whether the participant identity is different from the subscriber identity; if the participant identity is different from the subscriber identity (eg, participant ID/subscriber ID) And determining that the participant information satisfies the event notification rule. The subscriber identity can be obtained from a subscription creation request from a subscriber.

For another example, the determining feature can be a subscriber role, and the participant role can be determined whether the participant role is different from the subscriber role; if the participant role is different from the subscriber role (eg, the participant role/subscriber role) And determining that the participant information satisfies the event notification rule. The subscriber role can be obtained from a subscription creation request from a subscriber.

In step S206, in another embodiment, determining whether the participant information satisfies the event notification rule comprises: determining whether the participant information is the same as the determination feature; and if the participant information and the The judgment features are the same, and it is determined that the participant information satisfies the event notification rule.

For example, the determining feature may be a preset identifier, and determining whether the participant identifier is the same as the preset identifier; if the participant identifier is the same as the preset identifier (eg, participant ID=pre-set ID) And determining that the participant information satisfies the event notification rule.

For another example, the determining feature may be a preset role, determining whether the participant role is the same as the preset role; if the participant role is the same as the preset role (eg, participant role = preset role) And determining that the participant information satisfies the event notification rule.

In step S206, determining whether the participant information satisfies the event notification rule may further include: counting the number of participants having different participant information different from the determining feature; determining whether the number of the participants meets the An event notification rule; if the number of the participants satisfies the event notification rule, determining that the participant information satisfies the event notification rule.

In some embodiments, determining whether the number of the participants meets the event notification rule comprises: 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 The first threshold determines that the number of participants meets the event notification rule.

For example, participants can be classified according to roles (administrators, regular users, VIP users, other users, etc.). It is assumed that the judgment feature is set as a VIP user in the role (ie, judging The flag is set to "VIP User" and the first threshold is set to 15. When the number of participants having the "VIP User" role transmitting the operation request to the subscription service device 300 is equal to or greater than 15 (ie, the number of participants having the "VIP User" role is ≥ the first threshold 15), then the satisfaction is satisfied. An event notification rule that can send a notification to the notified party.

In other embodiments, determining whether the number of the participants meets the event notification rule 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 is determined to determine that the number of participants meets the event notification rule.

For example, assuming that the judgment feature is set as a VIP user in the role (ie, the judgment feature is set to "VIP User"), the second threshold is set to 25. When the number of participants having the "VIP User" role to send an operation request to the subscription service device 300 is equal to or less than 25 (ie, the number of participants having the "VIP User" role ≤ the second threshold 25), then the satisfaction is satisfied. An event notification rule that can send a notification to the notified party.

In still other embodiments, determining whether the number of the participants meets the event notification rule 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; The number of participants is greater than or equal to the first threshold and less than or equal to the second threshold, and it is determined that the number of participants satisfies the event notification rule.

For example, assuming that the judgment feature is set as a VIP user in the role (ie, the judgment feature is set to "VIP User"), the first threshold is set to 15, and the second threshold is set to 25. The number of participants having the "VIP User" role when the operation request is transmitted to the subscription service device 300 is equal to or greater than 15 and equal to or less than 25 (ie, the first threshold 15 ≤ the number of participants having the "VIP User" role ≤ second threshold 25), the event notification rule is satisfied, and the notification can be sent to the notified party.

Or, in step S206, determining whether the participant information satisfies the event notification rule comprises: counting the number of participants having the same participant information and the determination feature; determining whether the number of the participants meets the An event notification rule; if the number of the participants satisfies the event notification rule, determining that the participant information satisfies the event notification rule. For example, determining whether the number of the participants meets the event notification rule includes: determining whether the number of the participants is greater than or equal to a third threshold, and if yes, determining that the number of the participants meets the event notification rule Or, determining whether the number of participants is less than or equal to a fourth threshold, and if so, Determining that the number of the participants meets the event notification rule; or determining whether the number of the participants is greater than or equal to a third threshold and less than or equal to a fourth threshold, and if yes, determining that the number of participants is satisfied The event notification rule.

It is worth noting that the event notification rule may include the first threshold, the second threshold, the third threshold, and/or the third threshold. The first threshold, the second threshold, the third threshold, and/or the fourth threshold may be set while setting the event notification rule. Certainly, the specific value of the first threshold, the second threshold, the third threshold, and/or the fourth threshold may be set by the subscriber, the subscription service party or the notified party, and the disclosure is not limited herein.

The embodiment of the present disclosure further provides another method for performing notification, including:

Receiving a subscription request from a subscriber to obtain an event notification rule;

It is determined whether the participant information satisfies the event notification rule, and if so, sends a notification to the notified party.

Further, the method further includes: after receiving the subscription request, creating or directly acquiring a subscription resource, where the subscription resource includes the event notification rule;

Obtaining an event notification rule includes: obtaining an event notification rule included in the subscription resource.

For example, the participant includes a registrant; the method further includes: receiving a registration request from the registrant, the registration request including the party information. Alternatively, the participant includes a requesting party; the method further includes receiving an operation request from the third party participant.

For example, the participant information includes at least one of a participant identifier, a participant identification feature, a participant role, and a participant role identifier.

FIG. 3 is a schematic block diagram of a subscription service apparatus 300 according to an embodiment of the present disclosure. The subscription service device 300 is configured to notify the notified party, and includes a determining unit 310 and a notification unit 320. The determining unit 310 is configured to determine an event notification rule. The notification unit 320 is configured to determine whether the participant information satisfies the event notification. The rule, if yes, sends a notification to the notified party; wherein the participant information includes at least one of a participant identifier, a participant identification feature, and a participant role and a participant role identifier.

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.

For example, the subscription service device 300 further includes: a subscription resource creation unit 330, for creating A subscription resource is created, wherein the event notification rule is included in the subscription resource.

For example, the subscription service apparatus 300 further includes: a first receiving unit 340, configured to receive a create subscription resource request sent by the subscriber before creating the subscription resource.

For example, the notification unit 320 is specifically configured to determine whether the participant information matches the feature value, and if yes, determine that the participant information satisfies the event notification rule, and then send a notification to the notified party.

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

For example, the first receiving unit 340 is further configured to receive an operation request, where the participant information is included in the operation request.

For example, the notification unit 320 may be specifically configured to determine whether the participant information is different from the determination feature, and if yes, determine that the participant information satisfies the event notification rule, and send a notification to the notified party.

For example, the notification unit 320 is specifically configured to determine whether the participant information is equivalent to the determination feature, and if yes, determine that the participant information satisfies the event notification rule and send a notification to the notified party.

For another example, the notification unit 320 is specifically configured to: count the number of participants having the participant information different from the determination feature; determine whether the number of the participants meets the event notification rule; if the number of the participants The event notification rule is satisfied, and the participant information is determined to satisfy the event notification rule, and the notification is sent to the notified party.

Alternatively, the notification unit 320 is specifically configured to: count the number of participants having the same participant information and the determination feature; determine whether the number of the participants meets the event notification rule; if yes, determine the participant The information satisfies the event notification rule and sends a notification to the notified party.

For example, the determination feature includes at least one of an identification, a character, an identification feature, and a character feature. For example, the determination feature is a type of feature value.

For example, the identifier includes a subscriber identifier, a subscriber identifier, a notified party identifier, a participant identifier, a subscriber preset identifier, a subscriber preset identifier, a notified party preset identifier, and a participant preset identifier. At least one of the roles; the role includes a subscriber role, a subscriber role, a notified party role, a participant role, a subscriber preset role, a subscriber preset role, a notified party preset role, and a participant At least one of the roles; the identification feature includes a subscriber identification feature, At least one of a subscribing party identification feature, a notified party identification feature, a participant identification feature, a subscriber preset identification feature, a subscriber preset identification feature, a notified party preset identification feature, and a participant preset identification feature The character features include a subscriber role feature, a subscriber role feature, a notified party character feature, a participant role feature, a subscriber preset role feature, a subscriber preset role feature, and a notified party preset role. At least one of a feature and a participant preset role feature.

The units of the subscription service device 300 may be configured to perform the functions or steps of the method 200 as shown in FIG. 2, and the disclosure is not described herein again. For example, the various units of the subscription service device 300 can be implemented by the processor 152 in the subscription service device 150 shown in FIG. 1 running program instructions stored in the memory 154, and can perform the steps in the method 200, as well as other The steps shown in Figure 2.

An embodiment of the present disclosure further provides a system for notifying a subscription, comprising: a subscription service device 300 as described above; a subscription device configured to send a subscription creation request to the subscription service device and receive the subscription from the subscription service device a response to the subscription creation request; a participant device configured to send an operation request to the subscription service device and a response to receive the operation request from the subscription service device; and a notified party device configured to receive from the Subscribe to the notifications of the service device.

The subscription service device 300 may be disposed in the subscription service device 150, the subscription device may be disposed in the subscription device 101, the participant device may be disposed in the participant device 104, and the notified party device may It is set in the notified party device 106.

FIG. 4 is a schematic diagram of a process for subscribing to a notification according to an embodiment of the present disclosure.

First, the subscribing device 404 sends a request to create a subscription resource to the subscription service device 300 (step 410), such as sending a create<subscription> request. The request to create a subscription resource may include subscriber information (eg, subscriber identity, subscriber role, etc.). In response to the subscription creation request, the subscription service device 300 creates the subscription resource, specifically, creating a <subscription> under the subscribed resource, including an eventNotificationCriteria, and the eventNotificationCriteria includes a fixedID parameter. For example, the subscription resource includes an event notification rule eventNotificationCriteria (step 412).

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

The participant device 402 sends an operation request (step 416) to the subscription service device 300, such as a request for an operation such as create, retrieve, update, delete, and the like. The operational request may include party information (eg, party identity or party role, etc.).

The subscription service device 300 transmits a response to the operation request to the participant device 402 (step 418).

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 determination feature (step 420). If the participant information is different from the determination feature, the subscription service device 300 determines that the participant information satisfies the event notification rule (step 422). The subscription service device 300 transmits a notification to the notified party device 406 (step 424). The notified party device 406 transmits a response to the notification to the subscription service device 300 (step 426).

For example, after receiving the operation request, the subscriber detects the ID of the sender of the operation request, for example, includes an AE-ID, a CSE-ID or a resourceID, etc., and compares with the subscription resource preset fixedID, and if the same, sends a notification (Notify) to Notified party. Receive the respondent's response to the notification.

FIG. 5 is a schematic diagram of another process for subscribing to a notification according to an embodiment of the present disclosure.

First, the subscribing device 404 sends a request to create a subscription resource to the subscription service device 300 (step 510), that is, the subscription direction is sent by the subscribing party to create a <subscription> request. In response to the subscription creation request, the subscription service device 300 creates the subscription resource. Specifically, the <subscription> sub-resource is created under the subscribing resource, and includes a role number (roleNr) parameter, and the eventNotificationCriteria parameter includes a comparison parameter (ie, roleNrBigger, roleNrSmaller sub-parameter).

For example, the subscription resource includes an event notification rule eventNotificationCriteria (step 512). The subscription service device 300 sends a response to the subscription creation request to the subscribing device 404 (step 514), ie, the subscription sends a create <subscription> response to the subscriber. The participant device 402 sends an operation request to the subscription service device 300 (step 516), for example, the participation direction is sent by the subscriber to any of the create/retrieve/update/delete requests. The subscription service device 300 sends a response to the operation request to the participant device 402 (step 518), as the subscription is sent to the participant to send a response to any of the create/retrieve/update/delete requests.

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 determination feature (step 520). If the participant information is identical to the determination feature, the subscription service device 300 determines that the participant information satisfies the event notification rule (step 522). The subscription service device 300 transmits a notification to the notified party device 406 (step 524). The notified party device 406 transmits a response to the notification to the subscription service device 300 (step 526).

For example, when the subscriber accepts the request and detects that the roleID is different from the retained roleID, then the angle The number of colors is increased by 1 (ie, <subscription>/roleNr is increased by 1); then, it is judged whether the number of characters is greater than the first comparison parameter (ie, whether or not roleNr is greater than roleNrBigger), or whether the number of roles is smaller than the second comparison parameter (ie, It is determined whether the roleNr is smaller than roleNrSmaller), and if so, the subscription direction is sent by the notifying party to the Notify request; the notified direction is sent by the subscriber to the Notify response.

FIG. 6 is a schematic diagram of still another process for subscribing to a notification according to an embodiment of the present disclosure. First, the subscribing device 404 sends a request to create a subscription resource to the subscription service device 300 (step 610). In response to the create a subscription resource request, 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 subscribing device 404 (step 614).

The participant device 402 sends an operation request to the subscription service device 300 (step 616). The operational request may include party information (eg, party identity or party role, etc.). The subscription service device 300 transmits a response to the operation request to the participant device 402 (step 618).

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 having different party information than the decision feature (step 619). For example, among all the participants accessing the subscription service device 300, the subscription service device 300 records the number of participants having the participant information different from the judgment feature, and for the other parties having the same participant information and the same feature. The number is not counted. The subscription service device 300 determines whether the number of participants satisfies the event notification rule (step 620). If the number of 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 transmits a notification to the notified party device 406 (step 624). The notified party device 406 transmits a response to the notification to the subscription service device 300 (step 626).

An example of a subscription notification is as follows. For example, the subscriber subscribes to the subscription service device 300 (eg, the energy management platform) via the subscription device 101 (or subscription device 404) with an energy notification service for managing energy consumption (eg, electrical energy) at home. The home appliance of the subscriber's home can be the participant device 104, and both can be registered with the energy management platform in the subscription service device 150. One of the purposes of the registration is to enable the user terminal to control and manage the home appliance through the energy management platform. After the registration is completed, the subscriber can subscribe to the energy notification service through the subscription device 101 to the subscription service device 300 (eg, the energy management platform). The notification service for this subscription is 10 nights if there are 10 When the home appliance consumes power, it sends an energy consumption notification to another family member (notified party, different from the subscriber). Because the household electrical appliance sends an update request to the energy management platform after consuming the power, requesting to modify the value of the corresponding resource on the energy management platform. Therefore, when the 10th or more household appliances are modified to the resource value on the energy management platform in one night, The energy management platform will send a notification to another family member (notified party).

FIG. 7 is a schematic structural diagram of an exemplary subscription resource according to an embodiment of the present disclosure. After the participation direction is registered by the subscriber, an application entity resource (such as the <AE> resource shown in FIG. 7) is generated, and the application entity resource includes a container resource (<container> resource). The container resource includes a content instance resource (such as <contentInstance> shown in FIG. 7), and the content instance resource can be used to store information content.

When the subscription direction is sent by the subscriber to the subscription request (eg, the request indicates subscription to the application entity resource <AE>), the subscriber is under the application entity resource/container resource (ie, <AE>/< in FIG. 7) Under container>resources) create a subscription resource (ie, the <subscription> resource in Figure 7). The subscription resource includes an event notification rule (eventNotificationCriteria), a notification party address (notificationURI), a group identity (groupID), a notification forwarding address (notificationForwardingURI), a subscriber address (subscriber URI), and the like. The subscription resource may also include other content items not shown in FIG. 7, and the disclosure is not limited herein.

A method, apparatus, and system for performing notification provided by an embodiment of the present disclosure implements subscription notification based on a specific participant. When the subscription service party detects a specific participant, the notification message is sent to the notified party, and the notification service based on the participant is realized, which satisfies the requirement of user differentiation.

In this document, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such. The actual relationship or order. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

It will be apparent to those skilled in the art that various changes and modifications can be made in the present disclosure without departing from the spirit and scope of the disclosure. Thus, it is intended that the present invention cover the modifications and the modifications

The above description is only the specific embodiment disclosed, but the scope of the disclosure is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the disclosure. It is intended to be covered by the scope of the present disclosure. Therefore, the scope of protection of the present disclosure should be determined by the scope of the claims.

The present disclosure claims the priority of the Chinese Patent Application No. 201610617868.5 filed on July 29, 2016 and the Chinese Patent Application No. 201610665731.7 filed on Aug. 12, 2016, the entire disclosure of Part of the disclosure.

Claims (22)

A method of notification, including: Determine event notification rules; Determining whether the participant information satisfies the event notification rule, and if yes, sending a notification to the notified party; wherein the participant information includes at least one of a participant identifier, a participant identifier feature, a participant role, and a participant role feature one. The method of claim 1 wherein said determining an event notification rule comprises: Determining the event notification rule from a subscription resource; or The event notification rule is determined from an event notification rule set. The method of claim 2 further comprising: Receiving a request to create a subscription resource sent by a subscriber; A subscription resource is created, and the event notification rule is included in the subscription resource. The method according to claim 1, determining whether the participant information satisfies the event notification rule comprises: Determining whether the participant information matches the feature value, and if so, determining that the participant information satisfies the event notification rule. The method of claim 1 further comprising: A subscription request sent by the subscriber is received to determine the event notification rule. A method according to any of claims 1-5, further comprising: Receiving an operation request, wherein the operation request includes the participant information; or Receiving a registration request, wherein the registration request includes the participant information. The method according to any one of claims 1 to 6, wherein determining whether the participant information satisfies the event notification rule comprises: Determining whether the participant information is different from the determination feature, and if yes, determining that the participant information satisfies the event notification rule; or Determining whether the participant information is equivalent to the judgment feature, and if yes, determining that the participant information satisfies the event notification rule. The method according to any one of claims 1 to 6, wherein determining whether the participant information satisfies the event notification rule comprises: Counting the number of participants who satisfy the participant's information differently from the judgment feature; Determining whether the number of the participants meets 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. The method of claim 8, wherein determining whether the number of participants meets the event notification rule comprises: Determining whether the number of the participants is greater than or equal to a first threshold, and if yes, determining that the number of participants meets the event notification rule; 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 meets the event notification rule; 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 yes, determining that the number of participants meets the event notification rule. The method according to any one of claims 1 to 6, wherein determining whether the participant information satisfies the event notification rule comprises: Count the number of participants with the same participant information and judgment characteristics; Determining whether the number of the participants meets the event notification rule; If yes, it is determined that the participant information satisfies the event notification rule. The method of claim 10, wherein determining whether the number of participants meets the event notification rule comprises: 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 meets the event notification rule; or Determining whether the number of the participants is less than or equal to a fourth threshold, and if yes, determining that the number of participants meets the event notification rule; or Determining whether the number of the participants is greater than or equal to a third threshold and less than or equal to a fourth threshold, and if so, determining that the number of participants satisfies the event notification rule. The method of any of claims 7-11, wherein the determining feature comprises at least one of an identity, a character, an identification feature, and a character feature. A device for notifying, comprising: a determining unit configured to determine an event notification rule; The notification unit is configured to determine whether the participant information satisfies the event notification rule, and if yes, send a notification to the notified party; wherein the participant information includes a participant identifier and a participation indicator At least one of a feature, a participant role, and a participant role identifier. The apparatus of claim 13, wherein the determining unit is configured to: The event notification rule is determined from a subscription resource or from an event notification rule set. The apparatus of claim 14 further comprising: a first receiving unit configured to receive a request to create a subscription resource sent by a subscriber; A subscription resource creation unit configured to create a subscription resource, wherein the event notification rule is included in the subscription resource. The apparatus according to claim 13, wherein the notification unit is configured to determine whether the participant information matches a feature value, and if so, determining that the participant information satisfies the event notification rule, The notifying party sends a notification. The apparatus of claim 13 further comprising: The second receiving unit is configured to receive a subscription request sent by the subscriber to determine the event notification rule. The apparatus according to any one of claims 13-17, wherein the first receiving unit is further configured to receive an operation request, wherein the operation request includes the party information; or is further configured to receive a registration The request, wherein the registration request includes the participant information. The apparatus of claim 13, wherein the notification unit is configured to: Determining whether the participant information is different from the determination feature, and if yes, determining that the participant information satisfies the event notification rule, and sending a notification to the notified party; or Determining whether the participant information is equivalent to the determination feature, and if so, determining that the participant information satisfies the event notification rule and sends a notification to the notified party. The apparatus of claim 13, wherein the notification unit is configured to: The statistics have different participant information than the number of participants in the judgment feature, or the number of participants having the same participant information and the judgment feature; Determining whether the number of the participants meets 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, and sends a notification to the notified party. The apparatus of any one of claims 19-20, wherein the determining feature comprises at least one of an identification, a character, an identification feature, and a character feature. A system for notification, including: The device of any of claims 13-21, the device being 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; The notified party device is configured to receive a notification from the subscription service device.

Images