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

Slides:

Advertisements

Similar presentations

Access Control Mechanism Discussion

Advertisements

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

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

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.

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:

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

Device Management using mgmtCmd resource

On Persistent AE Identifiers Group Name: SEC#12.2 Source: Phil Hawkes, Qualcomm Inc (TIA), Francois Ennesser,

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

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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

3GPP Rel-13 Interworking discussions

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.

SEC Identity_of_registrar_CSE Identity of Registrar CSE Group Name: SEC, ARC and PRO Source:FUJITSU Meeting Date: Agenda Item: Authentication.

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.

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

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.

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

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

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.

Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless

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

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

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

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:

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

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

Issue regarding authentication at MN-CSE Group Name: ARC & SEC Source: FUJITSU Meeting Date: Agenda Item: Security Admin API.

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

3GPP SCEF Interworking Discussions

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:

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

CMDH and Policies Contribution: oneM2M-ARC-0603

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

ARC Possible_Collaboration_Area_with_OSGi.pptx Possible Collaboration Area with OSGi Group Name: ARC WG Source: Hiroyuki Maeomichi, NTT (TTC)

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

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

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

Possible Solution of Interworking between oneM2M and OSGi

Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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

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

oneM2M interop 3 issues and optimizations

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

End-to-End Security for Primitives

Proximal IoT Interworking discussion

Group multicast fanOut Procedure

Possible options of using DDS in oneM2M

Issues of <locationPolicy> Discussion

Proposed design principles for modelling interworked devices

MAF&MEF Interface Specification discussion of the next steps

Invite IIC testbeds to oneM2M interops

Proximal IoT Interworking solution discussion

oneM2M Versioning Next Steps

Group multicast Group Name: ARC

Aggregation of notification

Discussion on feature catalogue

LWM2M Interworking with <mgmtObj> Resources

On Management, Abstraction & Semantics

3GPP V2X Interworking Potential Impact

Presentation transcript:

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

Current statues Please refer to ARC Node_resolution as the background

Problem list Issue one: – How to represent devices in the M2M Area Network in our current resource structure? Issue two: – What resource to address if AE wants to manage something? Issue three: – How to correlate the physical device id and something in the service layer? Issue four: – What is the resource structure relate to management? © 2013 oneM2M Partners 3

Issue One We use Node to represent MN\ASN\ADN currently Do we still use Node to represent devices in the M2M Area Network? Or do we introduce a new resource type (attachedDevice as an example)? May be a little hard since TS0001 has frozen. Decision Point 1 Decision Point 2

Issue Two: We currently address Node to manage memory, storage, power and topology. We currently address application to manage corresponding software. We need to attach the other mgmtObjs to some where. We also need to solve the inconsistencies such as storage, power and networkTopology.

Issue Two Proposal – Attach every mgmtObj to Node – Delete storage as it’s a not supported mgmtObj – Change Power to battery – Change networkTopology to areaNwkInfo – Delete software under application Decision Point 3

Issue Three M2M-Node-ID is the identifier to ADN, ASN and MN. Seems M2M-Node-ID is a volunteer identifier for service layer representative of devices. Need to consider the relationship between Node-ID and CSE-ID – 1:1, one CSE per Node (Suggested from my side in R1) – m:1, multiple CSEs per Node is where the identifier of physical device (devId) is kept. – Multiple per Node? The Node may be distributed over several devices. Distributed system or backup case. – Only one per Node? Restrict to one Node one physical device – may be shared by multiple Node? Multiple Nodes running on one physical device. Virtual machine case, sandboxed Node instances.

Issue Three Proposal – Node and CSE one to one mapping – One Node could have multiple – As well as one can be shared by multiple Nodes. Decision Point 4

Issue Four hostedCSEId 11 nodeLink 0…1 0…1 0…1 0…n

Issue Four-Proposal Decision Point 5 hostedCSEId 0…n 0…1 nodeLink 0…1 0…1 nodeLink 0…1 Management shall only be performed through IN All Node attached to only IN All mgmtObj can only be found under Node Management Adaptor on ASN-CSE and MN- CSE can communicate with IN-CSE to update corresponding Node resource over Mcc r/p

Thanks!