Presentation is loading. Please wait.

Presentation is loading. Please wait.

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Similar presentations


Presentation on theme: "Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD."— Presentation transcript:

1 Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD

2 Introduction After the successful subscription procedure, the notification message shall be transferred to Receiver(s) specified in the notificationURI attribute. – The notificationURI is a URI where the resource subscriber will receive notifications. – The Receiver having notificationURI can be AE(s) or a CSE(s) including a subscriber. Also, the notification procedure can be classified either a request-reachable(server capable) and a request- unreachable(non-server capable) type depending on the Receive. © 2013 oneM2M Partners 2

3 Notification for Request-Reachable Receiver For the request-reachable receiver, the notification procedure can be classified into – Case 1. Subscriber = Receiver – Case 2. Subscriber ≠ Receiver © 2013 oneM2M Partners 3 AE1 (Subscriber /Receiver) CSE1 (Hosting CSE) ① subscription notificationURI => Subscriber ② event ③ notification AE1 (Subscriber) CSE1 (Hosting CSE) ① subscription notificationURI => Receiver ② event ③ notification AE2 (Receiver) Request-reachable entity No problem in the request-reachable Receiver.

4 For a request-unreachable Receiver, a certain resource which stores notifications is needed. – Case 1. Subscriber = Receiver – The Receiver knows information related to the notification address stored on notifications (e.g., ), action type to obtain notifications (e.g., long-polling). – “Case 1” has no problems to obtain notifications. © 2013 oneM2M Partners 4 AE1 (Subscriber /Receiver) CSE1 (Hosting CSE) ① subscription notificationURI => ② event ③ notification CSE2 (Having ) Request-unreachable entity ③ notification ④ obtain notifications I know information related to the notification. Notification for Request-Unreachable Receiver (1)

5 – Case 2. Subscriber ≠ Receiver – The Receiver doesn’t know anything about the notification. – Therefore, the subscriber shall inform the request-reachable Receiver of the information related to the notification. © 2013 oneM2M Partners 5 AE1 (Subscriber) CSE1 (Hosting CSE) ① subscription ② event ③ notification Request-unreachable entity ③ notification I cannot get notifications, because I don’t know any information for the notification. AE2 (Receiver) notificationURI => CSE2 (Having ) Notification for Request-Unreachable Receiver (2)

6 Suggestion If the Receiver of the notification is a request-reachable entity, the subscriber – subscribes to subscribed-to resource in the hosting CSE – notifies the Receiver of information related to the notification policy © 2013 oneM2M Partners 6 ② notification notificationURI => notificationType => long-polling AE1 (Subscriber) CSE1 (Hosting CSE) ① subscription notificationURI => ③ event ④ notification AE2 (Receiver) CSE2 (Having ) ⑤ obtain notifications I know information related to the notification. Notify the request- unreachable Receiver of information


Download ppt "Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD."

Similar presentations


Ads by Google