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

Slides:

Advertisements

Similar presentations

Access Control Mechanism Discussion

Advertisements

CMDH Refinement Contribution: oneM2M-ARC-0397

Summary on the M2M CMDH Policies Management Object (MCMDHMO)

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

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

SeungKwon Lee(KT) Scheduled Polling Mechanism. History  M2M#20 Meeting (June 4 th ~ June 8 th )  Contribution : M2M(12)20_066 Scheduled Polling Mechanism.

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.

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

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

Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.

Step by step approach Group Name: WG2

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

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

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

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.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

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.

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

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

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

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

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

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

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,

Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

LWM2M Interworking Proxy Procedures ARC Considerations

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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

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.

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

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

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

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

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

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

Background Data Transfer

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

Group multicast fanOut Procedure

2nd Interoperability testing issues

Issues of <locationPolicy> Discussion

Discussion about Use Case and Architecture in Developer Guide

Proposed design principles for modelling interworked devices

oneM2M Versioning Next Steps

ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC

Aggregation of notification

Considering issues regarding handling token

Discussion on feature catalogue

CMDH Refinement Contribution: oneM2M-ARC-0397R01

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

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

Needs Entities in subscription/notification – Resource subscriber who created – Subscription hosting CSE who sends notifications Long polling is needed – In some cases, a notification cannot be sent to receiver due to NAT or firewall – Short polling by the subscriber is costly – The subscriber performs long polling to retrieve notifications from the hosting CSE © 2013 oneM2M Partners 2

ARC at TP#7 (1/2) notification channel resource type for long- polling (notification retrieval), – has a virtual child resource © 2013 oneM2M Partners 3 Subscription Hosting CSE Resource Subscriber channel channel status retrieve notifications with long polling targeting “/ /channel” send triggered notifications to“/ /channel”

ARC at TP#7 (2/2) Main feedback was why not use – short polling on is available, but costly – as it is cannot support long polling © 2013 oneM2M Partners 4 Subscription Hosting CSE Resource Subscriber latest … … retrieve notifications with long polling… targeting “???” container latest instance triggered notifications to be stored as instances

Summary What we need to do is – supporting long-polling notification retrieval to solve non-server capable resource subscriber issue – NOT re-using Resource subscriber does not matter whether notifications are stored in container of subscription hosting CSE or not. The subscriber only matters how to retrieve notifications. The hosting CSE might matter but that’s implementation issue. © 2013 oneM2M Partners 5

Suggestion Basically the same as suggestion of TP#7, – has a virtual child resource named “notification” utilize virtual resource concept/benefit – status is not needed – does not matter notification storage e.g., or 3 rd party external storage © 2013 oneM2M Partners 6 notification retrieve notifications with long polling targeting “/ /notification” triggered notifications conceptually channel INPUT conceptually channel OUTPUT

Example (1/2) © 2013 oneM2M Partners 7 ADN-AEMN-CSE 1. create request resource type: 2. create response new resource “MN-CSE/noti_ch” created 3. create request resource type: notificationURI: “MN-CSE/noti_ch/notification” 4. create response new resource “MN-CSE/sub” created

Example (2/2) © 2013 oneM2M Partners 8 ADN-AEMN-CSE 6. retrieve response content: notification data a notification is triggered send a notification to “/noti_ch/notification” (internally) 5. retrieve request target: “MN-CSE/noti_ch/notification” (  long polling URI) pending the retrieve request until a notification is received at notification channel

The other long polling Non-server capable entity does this for – Notification retrieval – Other CRUD requests retrieval channel hosting CSE re-targets request(s) to a channel Non server capable entity retrieves the request(s) from the channel © 2013 oneM2M Partners 9 CSE2base CSE1 retrieve request(s) with long polling from “entity2_base/entity1/channel” A request to CSE1 channel CSE1 AE2 Re-target Cannot send a request to a non server capable entity

Way Forward To bring a contribution proposing a new resource type – 2 main usages for non server capable AE/CSE Notification retrieval channel for AE/CSE  Notification channel (in ETSI TC M2M) CRUD request retrieval channel for CSE  Communication channel (in ETSI TC M2M) – Eventually both are for long polling – So it has more generic name