1. Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: 2015-01-19~23 Agenda Item: (To Be Assigned)

2. Introduction The current Subscription and Notification process can not adequately support the scenarios when multiple subscribers of the service started with one service subscription from the Originator (creator of the resource in the Hosting CSE), and later on, some of the subscribers (other than the originator) want to cancel the service subscription. The problem can be avoided with a refinement in the existing Subscription and Notification procedures. © 2015 oneM2M Partners 2

3. Issues © 2015 oneM2M Partners 3 1. Situation: Tom subscribes the Live weather Broadcast service for Sam, Marry, and Sophie via sending “create Subscription request” to the Live Weather Broadcast platform. 2. Platform returns the Create Subscription Response to Tom. 3, 4 Platform then initiates the subscription verifications to Sam, Mary and Sophie subsequently. If Sam later intends to cancel this Live Weather Broadcast service: 1. How dose Sam let the Live Weather platform stop sending notification again? 2. How does the platform notify Tom that Sam intends to cancel the notification?

4. Current Subscription and Notification © 2015 oneM2M Partners 4 The Subscription Verification Procedure

5. Scenario 1 © 2015 oneM2M Partners 5 Step 2:Notification Target returns Notify Response including e.g. a parameter, to indicate stop receiving further notifications to Hosting CSE. Step 4:Hosting CSE sends Notify Request message including notificationCancellation and Address of Notification Target to the Originator. Then the Originator updates resource subsequently.

6. Scenario 2 Step 1: Notification Target sends Notify Request including notificationCancellation. Step 4: Hosting CSE sends Notify Request message including notificationCancellation and Address of Notification Target to the Originator. Then the Originator updates resource subsequently. © 2015 oneM2M Partners 6

7. Proposed Solution © 2015 oneM2M Partners 7 The Hosting CSE shall notify the Originator by including a ”notificationCancellation” parameter indicated by the Notification Target through the Notify Response message, or received from the Notification Target through the Notify Request message.

8. Thanks © 2015 oneM2M Partners 8