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

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:
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.
WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
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.
Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date:
OneM2M portal introduction Group Name: Technical Plenary Source: Gerry McAuley, ETSI, Meeting Date: Agenda Item: 1.5.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
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.
App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
Proposal for OID-based M2M Node ID Group Name: WG2 Architecture at TP#8 (Miyazaki, December 2013) Source: Yong-Suk Park, KETI, Meeting.
Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless
Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
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.
WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.
Work Programme Management Ad hoc Group Report Group Name: one M2M TP12 Source: Convenor WPM Joachim Koss, Gemalto M2M,
WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,
Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.
Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.
AllJoyn-Interworking Discussion Group Name: TP WG2 ARC Source: Josef Blanz, Phil Hawkes, Qualcomm Inc., Meeting Date:
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.
WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.
Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:
Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.
WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,
App-ID Use Cases, Syntax and Attributes ARC R01-App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.
Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: Agenda Item:
Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.
ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.
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:
Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.
OIC INTERWORKING Resource mapping
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.
SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:
Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.
WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
WG2 - ARC TP #20 Status Report Group Name: oneM2M TP #20 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
Clarification of Access Control Mechanism on Rel-1 & Rel-2 Group Name: SEC ( ARC & PRO for information) Source: FUJITSU Meeting Date: Agenda.
WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.
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:
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.
Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.
TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,
Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:
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.
TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.
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.
App-ID Ad-Hoc Technical Issues TP AppID R02
Service Framework Proposal
MIME Type Definition Group Name: PRO WG
Proposed design principles for modelling interworked devices
3GPP Interworking Abstraction
Considering issues regarding handling token
Presentation transcript:

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

Introduction This contribution is to discuss how to handle App-ID in ARC TS © 2013 oneM2M Partners 2

Current Status of App-ID © 2013 oneM2M Partners 3 App-ID is to indicate sort of AE However App-ID is not unique, which means that App1 can use AppID1 and App2 can use AppID1 even though they are not the same kind of AEs.

Current Usage of App-ID © 2013 oneM2M Partners 4 There are several occurrences: – AE – m2mServiceSubscription (Removed) – cmdhDefaultValue – cmdhLimit – statsCollect

There are two options 1.Remove All the App-ID concept in ARC TS 2.Make App-ID unique within M2M SP (Proposal) © 2013 oneM2M Partners 5 How to handle

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.