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

Slides:

Advertisements

Similar presentations

On-Demand Access Authorization for SIP Event Subscriptions D. Trossen, H. Schulzrinne.

Advertisements

MIP6-HA-Local-Assignment-Capability indication to MS Contributors grant a free, irrevocable license to 3GPP2 and its Organization Partners.

CMDH Refinement Contribution: oneM2M-ARC-0397

HUAWEI TECHNOLOGIES CO., LTD. Huawei Technologies Co., Ltd. grant a free, irrevocable license to 3GPP2 and its Organizational Partners to.

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Summary on the M2M CMDH Policies Management Object (MCMDHMO)

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

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

Sept 2011 Mobile Messaging Solutions ICE. Mobile Sdn Bhd (By Yaw Mei)

OneM2M-ARC Service_examples_and_evolution Service examples and evolution Group Name: WG2 Source: Philip Jacobs, Cisco Systems,

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Discussion on Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

3GPP Rel-13 Interworking discussions

Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

Usage Scenarios for CSE Group Name: WG2(ARC-WG) Source: Shingo Meeting Date: Agenda Item: Message.

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

HUAWEI TECHNOLOGIES CO., LTD. Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext LT Medium Font to be used by customers.

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

1. How to handle Request-ID? oneM2M joint WG2 & WG3 discussion PRO Josef Blanz July 2 nd, 2014.

Issues pertaining to IOP test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

App and Management End- to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm,

LWM2M Interworking Proxy Procedures ARC Considerations

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

Resource subscription using DDS in oneM2M

3GPP MBMS protocol stack

Service Enabled AE (SAE)

End-to-End Security for Primitives

Group multicast fanOut Procedure

Possible options of using DDS in oneM2M

Issues of <locationPolicy> Discussion

Invite IIC testbeds to oneM2M interops

Discussion to clarify online/offline behavior

oneM2M Versioning Next Steps

Group multicast Group Name: ARC

Aggregation of notification

Considering issues regarding handling token

Discussion on feature catalogue

CMDH Refinement Contribution: oneM2M-ARC-0397R01

MinitorEvent(UE_Reachability)

Service Layer Dynamic Authorization [SLDA]

3GPP V2X Interworking Potential Impact

3GPP Interworking and use of <schedule> resource

MAPID for User Plane Support

MAPID for User Plane Support

Notification Target Discussion

Presentation transcript:

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

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

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?

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

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.

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

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.

Thanks © 2015 oneM2M Partners 8