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

Slides:

Advertisements

Similar presentations

oneM2M and AllJoyn Interworking

Advertisements

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

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

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.

Device Management using mgmtCmd resource

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.

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,

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.

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.

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

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.

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

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

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.

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

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

3GPP Rel-13 Interworking discussions

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

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

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

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

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

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

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

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

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

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

Draft way Forward on Access Control Model and associated Terminology Group Name: SEC Source: Dragan Vujcic, Oberthur Technologies,

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:

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

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

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

3GPP R13 Small Data Delivery

Resource subscription using DDS in oneM2M

3GPP MBMS protocol stack

Service Framework Proposal

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

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

NIDD Discussion Points

Proposed design principles for modelling interworked devices

oneM2M Service Layer Protocol Version Handling

MAF&MEF Interface Specification discussion of the next steps

3GPP Rel-13 Interworking discussions

Discussion to clarify online/offline behavior

3GPP Interworking Abstraction

oneM2M Versioning Next Steps

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

Group multicast Group Name: ARC

Considering issues regarding handling token

LWM2M Interworking with <mgmtObj> Resources

MinitorEvent(UE_Reachability)

Service Layer Dynamic Authorization [SLDA]

3GPP V2X Interworking Potential Impact

Summary of the MAF and MEF Interface Specification TS-0032

Notification Target Discussion

Presentation transcript:

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

Management Procedure using resource type Creating a into a Hosting CSE and target entity to be managed is indicated in the ‘execTarget’ attribute which addresses a resource Determining which management protocol is used for communicating Establishing a management session – In this step, Management Server embedded in IN-CSE can make session with managed entity’s management client Sending the management request(s) to the managed entity using a management protocol (e.g., BBF TR-069 or proprietary) © 2014 oneM2M Partners 2

Management Procedure ASN or MN Case © 2014 oneM2M Partners 3 CSEBase execTarget nodeID hostedCSELink resource of ASN or MN resource of ASN or MN Hosting CSE Management Server Managed Entity’ s CSE CSEBase Management Client Mcn(ms) mc Mcc ASN or MN Question : How to get the address of the ‘management client’? IN

Management Procedure ADN Case © 2014 oneM2M Partners 4 CSEBase execTarget nodeID resource of ASN or MN resource of ASN or MN Hosting CSE Management Server Managed Entity’ s AE Management Client Mcn(ms) mc Mca ADN Question : How to get the address of the ‘management client’? IN

Management Procedure All Cases © 2014 oneM2M Partners 5 CSEBase execTarget nodeID hostedCSELink resource of ASN or MN resource of ASN or MN Hosting CSE Management Server Managed Entity’ s CSE CSEBase Management Client Mcn(ms) mc Mcc ASN or MN Question : How to get the address of the ‘management client’? For existing management server – OMA or BBF, the making device management session procedure is well defined and the server can utilize an out-of-band way to get the client address Especially If a system is used proprietary management protocol, getting the management client address is more sophisticated The management server embedded in the IN-CSE cannot convert the node ID to management client address No way to make management session

Proposals © 2014 oneM2M Partners 6 Proposal to define an optional way to specify the address of managed entity – Add an attribute into resource type named ’mgmtClientAddress’ – The attribute specifies the address of the managed entity’s address containing the underlying transport protocol as well as the IP address and port (or an FQDN) like ’pointOfAccess’