Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date:

Slides:

Advertisements

Similar presentations

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

Advertisements

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.

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

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

Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Meeting Date:

3GPP Rel-13 Interworking discussions

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.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd.

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

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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.

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

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

TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,

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

3GPP Rel-13 Interworking discussions

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.

SE abstraction scenarios Group Name: SEC Source: Claus Dietze, Giesecke & Devrient Meeting Date: Agenda Item: WI SE abstraction.

Planning for the test event Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

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

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Communication Method Group Name: ARC Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

LWM2M Interworking Proxy Procedures ARC Considerations

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

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

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

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:

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

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) 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:

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

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

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Proximal IoT Interworking discussion

Group multicast fanOut Procedure

WG2 - ARC TP#29 Status Report

3GPP interworking in R3 Group Name: ARC

Issues of <locationPolicy> Discussion

Modbus interworking Group Name: ARC

3GPP Rel-13 Interworking discussions

WPM ad-hoc group report TP#25

Invite IIC testbeds to oneM2M interops

WG2 - ARC TP#29 Status Report

Proximal IoT Interworking solution discussion

Group multicast Group Name: ARC

Aggregation of notification

Considering issues regarding handling token

Discussion on feature catalogue

LWM2M Interworking with <mgmtObj> Resources

Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Consideration on MAC enhancement of IEEE ]

Presentation transcript:

Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD

Background and Question There are many resource constraint devices in the M2M world. – Shortage of memory, battery – Limited processing capability – Unable to hold long term connection – Unable to receive requests – Limited bandwidth The M2M industry is trying to make the battery powered device last long enough to save the budget of replacing battery or buy new devices. – NB-M2M/eMTC/Sigfox/LoRa learns how to cut down the power consumption of the wireless module – CoAP/6LowPAN learns how to make the best use of limited bandwidth – LWM2M learns how to do an efficient device management The question is: – What can we do in the service layer in oneM2M? © 2014 oneM2M Partners 2

Current status Two separate rounds of request and responses are needed to transfer one single temperature value – See contribution ARC xx-subscription_to_childResource Devices need to be server capable or being able to hold long time connection to receive notifications The wrapper of contentInstance is still too much for masses of creations. The constraint device is not guaranteed with enough sleeping time. The constraint device has no right to change the locationUpdatePeriod to a slower frequency if the device hardly moves. And so on…

Conclusion & Proposal There is indeed quite a lot of things to do in the service layer. Proposal: – Start a dedicated new WI on the investigation of resource constraint devices in oneM2M. – The output of the WI includes a bunch of CR. – May deliver TS or TR based on the discussion we have.