Subscription and notification service
Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.
1. An apparatus comprising:
one or more processors; and
one or more memories coupled with the one or more processors, the one or more memories comprising executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
obtaining a subscription request from a subscriber device to a first resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having a representation that can be manipulated via RESTful methods, wherein the subscription request comprises:
an event notification criteria that defines when an event notification is to be generated, and
instructions on when, how, or which notification should be recorded;
detecting the event notification criteria has been met for the first resource;
generating the event notification for the first resource;
transmitting a notification message to the subscriber device;
recording the notification message to a second resource based on the instructions in the subscription request when the notification message has failed;
receiving, via RESTful methods, a retrieval request to retrieve the recorded notification message stored in the second resource; and
based on the retrieval request, sending a response, wherein the response comprises content of the recorded notification message stored in the second resource.
2. The apparatus of claim 1 , the operations further comprising:
obtaining a second subscription request to retrieve the event notification when the event notification occurs during a time period; and
sending a response to the second subscription request that comprises the notification message for the time period.
3. The apparatus of claim 1 , the operations further comprising:
obtaining a second subscription request to retrieve the event notification associated with a notification target based on discovery criteria; and
when the discovery criteria is met, sending a response to the second subscription request that comprises the notification message.
4. The apparatus of claim 1 , the operations further comprising:
obtaining a second subscription request to retrieve the event notification associated with a notification target based on discovery criteria, wherein discovery criteria comprises a request for messages that have been sent and have not been acknowledged as obtained by the notification target; and
when the discovery criteria is met, sending a response to the second subscription request that comprises the notification message.
5. The apparatus of claim 1 , the operations further comprising:
obtaining a second subscription request to delete the event notification associated with a notification target based on discovery criteria; and
when the discovery criteria is met, sending a response acknowledging the second subscription request.
6. The apparatus of claim 1 , the operations further comprising:
obtaining a second subscription request to delete the event notification associated with a notification target based on discovery criteria, wherein discovery criteria comprises messages that have been sent during a time period; and
when the discovery criteria is met, sending a response acknowledging the second subscription request.
7. The apparatus of claim 1 , wherein the subscription request comprises instructions to record every notification issued during a time period.
8. The apparatus of claim 1 , wherein the subscription request comprises instructions to record notifications which are issued during a time period, delivered to notification targets in a list, and generated by conditions in the list.
9. The apparatus of claim 1 , wherein the subscription request comprises instructions to record notifications when a certain number have failed for a particular notification target.
10. The apparatus of claim 1 , the operations further comprising obtaining an indication of an expiration time of a notification resource to be created.
11. The apparatus of claim 1 , wherein the apparatus is a service layer.
12. A method for subscribing to a notification comprising:
obtaining a subscription request from a subscriber device to a first resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having a representation that can be manipulated via RESTful methods, wherein the subscription request comprises:
an event notification criteria that defines when an event notification is to be generated, and
instructions on when, how, or which notification should be recorded;
detecting the event notification criteria has been met for the first resource;
generating the event notification for the first resource;
transmitting a notification message to the subscriber device;
recording the notification message to a second resource based on the instructions in the subscription request when the notification message has failed;
receiving, via the RESTful methods, a retrieval request to retrieve the recorded notification message stored in the second resource; and
based on the retrieval request, sending a response, wherein the response comprises content of the recorded notification message stored in the second resource.
13. The method of claim 12 , further comprising:
obtaining a second subscription request to retrieve the event notification when the event notification occurs during a time period; and
sending a response to the second subscription request that comprises the notification message for the time period.
14. The method of claim 12 , further comprising:
obtaining a second subscription request to retrieve the event notification associated with a notification target based on discovery criteria; and
when the discovery criteria is met, sending a response to the second subscription request that comprises the notification message.
15. The method of claim 12 , further comprising:
obtaining a second subscription request to retrieve the event notification associated with a notification target based on discovery criteria, wherein discovery criteria comprises a request for messages that have been sent and have not been acknowledged as obtained by the notification target; and
when the discovery criteria is met, sending a response to the second subscription request that comprises the notification message.
16. The method of claim 12 , further comprising:
obtaining a second subscription request to delete the event notification associated with a notification target based on discovery criteria; and
when the discovery criteria is met, sending a response acknowledging the second subscription request.
17. The method of claim 12 , further comprising:
obtaining a second subscription request to delete the event notification associated with a notification target based on discovery criteria, wherein discovery criteria comprises messages that have been sent during a time period; and
when the discovery criteria is met, sending a response acknowledging the second subscription request.
18. The method of claim 12 , wherein the subscription request comprises instructions to record notifications which are issued during a time period, delivered to notification targets in a list, and generated by conditions in the list.
19. The method of claim 12 , wherein the subscription request comprises instructions to record notifications when a certain number have failed for a particular notification target.
20. A system, the system comprising:
one or more processors; and
memory coupled with the one or more processors, the memory comprising executable instructions that when executed by the one or more processors cause the one or more processors to effectuate operations comprising:
obtaining a subscription request from a subscriber device to a first resource being a uniquely addressable element in a Resource Oriented Architecture (ROA) having a representation that can be manipulated via RESTful methods, wherein the subscription request comprises:
an event notification criteria that defines when an event notification is to be generated, and
instructions on when, how, or which notification should be recorded;
detecting the event notification criteria has been met for the first resource;
generating the event notification for the first resource;
transmitting a notification message to the subscriber device;
recording the notification message to a second resource based on the instructions in the subscription request when the notification message has failed;
receiving, via RESTful methods, a retrieval request to retrieve the recorded notification message stored in the second resource; and
based on the retrieval request, sending a response, wherein the response comprises content of the recorded notification message stored in the second resource.