@@ -1525,10 +1525,10 @@ In this clause, notification examples are provided for the understanding of noti
|API Name |Notification procedure when the <subscription> resource has notificationEventType set to 1(Hosting CSE sends notification when the subscribed-to resource has been updated) |
|<br/>Description |Figure below depicts the procedure for notification.<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br/><br/>Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 1 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br/>Step 02: An AE2 sends an UPDATE request to the <container> resource. The Registrar CSE updates a <container> resource and sends back a response.<br/>Step 03: The Hosting CSE sends notification as soon as update succeed. The originator sends back an ACK message. |
|**S****tep 02**<br/><br/> |**HTTP Header Information**<br/><br/>Header and Value pair information:<br/>Accept : application/ json<br/>X-M2M-RI : Request ID<br/>X-M2M-Origin : AE-ID of request originator<br/>Content-Type : application/json<br/>X-M2M-RVI : Release Version Indicator |
...
...
@@ -1548,10 +1548,10 @@ In this clause, notification examples are provided for the understanding of noti
|**API Name** |Notification procedure when the <subscription> resource has notificationEventType set to 2(Hosting CSE sends notification when the subscribed to resource has been deleted) |
|<br/>**Description** |Figure below depicts the procedure for notification.<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br/><br/>Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 2 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br/>Step 02: An AE2 sends a DELETE request to the <container> resource. The Registrar CSE deletes a <container> resource and sends back a response.<br/>Step 03: The Hosting CSE sends notification as soon as delete succeed. The originator sends back an ACK message. |
|**S****tep 02**<br/><br/> |**HTTP Header Information**<br/><br/>Header and Value pair information:<br/>Accept : application/ json<br/>X-M2M-RI : Request ID<br/>X-M2M-Origin : AE-ID of request originator<br/>X-M2M-RVI : Release Version Indicator |
...
...
@@ -1571,10 +1571,10 @@ In this clause, notification examples are provided for the understanding of noti
|**API Name** |Notification procedure when the <subscription> resource has notificationEventType set to 3 (Hosting CSE sends notification when the direct child resource has been created) |
|<br/>**Description** |Figure below depicts the procedure for notification.<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br/><br/>Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 3 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br/>Step 02: An AE2 sends a CREATE request of the <contentInstance> resource to the <container> resource. The Registrar CSE creates a <contentInstance> resource and sends back a response.<br/>Step 03: The Hosting CSE sends notification as soon as create succeed. The originator sends back an ACK message. |