Discussion on oneM2M HTTP Binding Interoperability Test Spec.

Slides:

Advertisements

Similar presentations

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

Advertisements

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

IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit

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

TAKING A LOOK INSIDE Nicolas Damour

oneM2M High Level Overview

The importance of the collection pattern for OneM2M architecture Group Name: ARC/PRO Source: Mahdi Ben Alaya, LAAS-CNRS,

Device Management using mgmtCmd resource

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

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

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

oneM2M-OIC Interworking Technical Comparison

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

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.

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24.

Fuctional Procedure for oiC interworking

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

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

An introduction to oneM2M

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

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

OIC device management interworking procedure

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

M2M Service Session Management (SSM) CSF

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:

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:

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

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

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

3GPP SCEF Interworking Discussions

oneM2M based IoT Platform Development of SK Telecom

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

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

CMDH and Policies Contribution: oneM2M-ARC-0603

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

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

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

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

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

TST TTCN-3_development_plan TTCN-3 development plan Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

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

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jinhyeock Choi, Samsung Electronics,

[authenticationProfile] <mgmtObj> specialization

Provisional Architecture for oneM2M

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

2nd Interoperability testing issues

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

Proximal IoT Interworking solution discussion

TS-0004 Data Representation Proposal Discussion

oneM2M Versioning Next Steps

Proposals on Test Events

Considering issues regarding handling token

LWM2M Interworking with <mgmtObj> Resources

Development Guideline for oneM2M Products and Services

On Management, Abstraction & Semantics

Summary of the MAF and MEF Interface Specification TS-0032

Notification Target Discussion

Presentation transcript:

Discussion on oneM2M HTTP Binding Interoperability Test Spec. TST-2015-0004-Discussion_on_oneM2M_HTTP_Binding_Interoperability_Test_Spec Discussion on oneM2M HTTP Binding Interoperability Test Spec. Source: Sungchan Choi, csc@keti.re.kr Data: 2015-01-06

Contents of ETSI HTTP Binding Test Spec Reference Scope References Definitions, Symbols and abbreviation Conventions Test Description Summary Basic Configuration Test Configuration Test Description

Test Description Consideration Before we write HTTP binding Test Spec, we need to define several considerations as below Which test configurations needs to be considered? Which resources are handled in the Test Description? (E.g., AE, remoteCSE, container, contentInstance, subscription, group ..) Baseline of HTTP Request/Response format (including oneM2M Resource Representation) And more?

Test Configurations

Single-hop case (Mca Interface) Field Domain Infrastructure Domain Mca AE 1 AE 3 Mca Mcc CSE AE 5 Mca Mca CSE Mca AE AE 5 2 AE AE Mcc 3 Mca Mca 4 CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Single-hop case (Mca Interface) ADN-AE to IN-CSE ADN-AE to MN-CSE ASN-AE to ASN-CSE MN-AE to MN-CSE IN-AE to IN-CSE 1 AE to Local CSE Access 2 3 4 5

Single-hop case (Mcc Interface) Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE 1 Mca Mca CSE Mca AE AE 4 AE Mcc Mca 2 CSE Mcc 3 M2M Device M2M Gateway M2M Server Admin/ User

Single-hop case (Mcc Interface) ASN-CSE to IN-CSE ASN-CSE to MN-CSE MN-AE to MN-CSE MN-AE to IN-CSE 1 CSE to Remote CSE Access 2 3 4

Multi-hop ASN-AE to IN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Multi-hop ADN-AE to IN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Multi-hop ASN-AE to MN-CSE to IN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Multi-hop IN-AE to MN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Multi-hop IN-AE to ASN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

Multi-hop IN-AE to MN-CSE to ASN-CSE Field Domain Infrastructure Domain Mca AE AE Mca Mcc CSE AE Mca Mca CSE Mca AE AE AE AE Mcc Mca Mca CSE CSE Mcc M2M Device M2M Gateway M2M Server Admin/ User

oneM2M Resources

Which resource types (applying CRUD operations) we need to consider? oneM2M Resource Types accessControlPolicy AE Container contentInstance CSEBase delivery eventConfig execInstance fanOutPoint(v) group latest (v) locationPolicy mgmtCmd mgmtObj m2mServiceSubscriptonProfile node oldest (v) pollingChannel pollingChannelURI (v) remoteCSE request schedule serviceSubsribedNode statsCollect statsConfig Subscription serviceSubscribedRule Which resource types (applying CRUD operations) we need to consider?

Next Step

Proposal Agreement on baseline of HTTP binding format (example) including oneM2M resource representation Detailed test description after resolving test configuration and resource types to be handled in the test spec. Schedule plan for TP15, 16, 17,..