ETSI M2M / TIA architecture harmonization O. Elloumi.

Slides:

Advertisements

Similar presentations

World Class Standards 1 SCP(11)0001 SCP Plenary #47 January 12-14, 2011 Title*: Update on TC M2M activities (and Smart Metering Mandate) Submitted by:

Advertisements

M2M and Semantic Sensor Web

CDMA Standards Update M2M Small Group Discussion: CONVERGENCE LAYER CONCEPTS Orlett W. Pearson January 2012.

Internet of Things (IoT) Work Group

® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All ETSI Standardization Activities on M2M communications Joachim Koss, ETSI Board Member Document No:

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

28.2 Functionality Application Software Provides Applications supply the high-level services that user access, and determine how users perceive the capabilities.

Broadband Forum Machine-to-Machine (M2M) Solutions Robin Mersh, CEO The information in this presentation is public.

The OSI Model and the TCP/IP Protocol Suite

Exmouth House 3–11 Pine Street London EC1R 0JH T F E W CAE – Next generation and Building.

ETSI M2M / TIA architecture harmonization next steps.

ETSI Home Networking activities Rainer Münch ETSI TISPAN Chairman Presenter: Ian Spiers DOCUMENT #:GSC13-GTSC6-20r1 FOR:Presentation SOURCE:Rainer Münch,

Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.

© 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

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

Presentation of ETSI TC M2M security features Group Name: WG4 Securtity Source: Francois Ennesser, Gemalto Meeting Date: Agenda Item: SEC.

CECS 5460 – Assignment 3 Stacey VanderHeiden Güney.

Minutes of the Meeting IoT WG GISFI #7 New Delhi, Dec 19-22, 2011 Doc No: GISFI_IoT_

The Design Discipline.

Chapter 2 Network Design Essentials Instructor: Nhan Nguyen Phuong.

DOCUMENT #:GSC15-PLEN-53 FOR:Presentation SOURCE:ETSI AGENDA ITEM:PLEN 6.11 CONTACT(S):Emmanuel Darmois, Board Member Marylin Arndt, TC M2M chair Smart.

1 The Telecommunications Industry Association (TIA) ADVANCING GLOBAL COMMUNICATIONS Jeff Smith, Ph.D., Chief Technology Officer of Numerex (Nasdaq: nmrx)

Step by step approach Group Name: WG2

An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.

Margherita Forcolin (Insiel S.p.A.) Thessaloniki, 13 October 2011.

Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,

Overview TIA TR-50 – Smart Device Communications Orlett W. Pearson March 2010.

© 2015 Redbend – Confidential1 Aug 2015 ALLJOYN UPDATE SERVICE UPDATED CONTRIBUTION & DEMO PLAN.

1 Presentation_ID © 1999, Cisco Systems, Inc. Cisco All-IP Mobile Wireless Network Reference Model Presentation_ID.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

Machine-to-Machine(M2M) Communication for cdma2000 Systems Orlett W. Pearson, 3GPP2 LS to TR-50 February 2011.

HUAWEI TECHNOLOGIES CO., LTD. Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext LT Medium Font to be used by customers.

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

Overview of analysis of existing SDO M2M architectures Group Name: REQ ARC#2 Source: Alcatel-Lucent.

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

ITU-T SG16 and JCA-IoT activities

IoT High Level Architecture (HLA) AIOTI Edited by AIOTI WG3 Chairs Patrick Guillemin Jean-Pierre Desbenoit AIOTI WG3 IoT High Level Architecture – Release.

Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN

Role Based Access Control In oneM2m

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

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

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

Communication and Security in Machine-to-Machine Systems Date │ Reporter │ 李雅樺 1.

November 2001 Lars Falk, TeliaSlide 1 doc.: IEEE /617r1 Submission Status of 3G Interworking Lars Falk, Telia.

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

TIA – ETSI workshop Conclusions March 22nd Objectives Harmonize the documents into a single set of documents (requirements, definition, architecture.

Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN

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

© 2006 Cisco Systems, Inc. All rights reserved. BSCI v3.0—8-1 Implementing IPv6 Defining IPv6 Addressing.

Framework for DWDM interface Management and Control draft-kdkgall-ccamp-dwdm-if-mng-ctrl-fwk-01 Ruediger KunzeDeutsche Telekom Gabriele Galimberti Cisco.

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

Deployment Diagram.

Provisional Architecture for oneM2M

Deployment Diagram.

“Internet of Things” – The new age drivers of Power Distribution Automation Speaker: Jayant Sinha Date of session: 2 Oct, 2015.

Possible options of using DDS in oneM2M

IEEE 802 OmniRAN Study Group: SDN Use Case

1st Draft for Defining IoT (1)

Deployment Diagram.

ETSI Standardization Activities on M2M communications

מרכז אימות לפלטפורמת מתן שירותים

HIS Smart Grid – Summary (1)

ETSI Standardization Activities on M2M Communications

Standards for Shared ICT

ETSI Standardization Activities on M2M Communications

IEEE 802 Scope of OmniRAN Abstract

May 2004 doc.: IEEE /629r1 May 2004 The Nature of an ESS

Nobuo Fujii (GTSC Chair) Rapporteur: Nicole Butler

Q1/13 - NGN Initial Considerations

Presentation transcript:

ETSI M2M / TIA architecture harmonization O. Elloumi

TR50.1 architecture, general observations Intermediate node is the equivalent of an ETSI M2M Gateway (G’ in particular, TBC), although not explicitely stated as such in the architecture specification Chaining of intermediate nodes is possible (not part of ETSI M2M R1) No horizontal service platform: Application server implements functions of NA and NSCL Smart Device is equivalent to D & D’ device, while Device is equivalent to legacy ‘d’ in ETSI M2M parlance. –X interface is out of scope for ETSI Interfaces to AAA are not shown in ETSI Architecture, but are recognized as internal interfaces

High-level mapping

Delta for ETSI to take into account TIA Delta: G to G (in ETSI M2M this can be handled via the the network) D to D (not necessarily via LAN/PAN)

Way forward on harmonization TIA TR50.1 architecture considers the need for multiple interconnected gateways as important aspect of the architecture to account for e.g. Smart Grid deployments TIA TR50.1 identifies the need for a convergence layer as a means to hide network specificities Intermediate node would connect multiple smart devices and intermediate nodes. ETSI consider the M2M service platform as separate from the Application Server (common agreement on this) Next steps: – discussion over the joint mailing list (Paul Russel to trigger a way forward discussion) – discussion on definitions (Mitch to trigger discussion on definitions alignment) –May 11 conf. call (2 and ½), Victoria will send practical arrangements –June 7 th conf. call (2 and ½) (decide for date and venue for the F2F meeting taking into account the current progress)

Reference points mapping A1: AAA the application server. A2: AAA the intermediate node. A3: AAA the smart device controller. A4: AAA the smart device. B1: application intermediate node. B3: intermediate node smart device controller. B5: application server smart device. B6: intermediate node intermediate node B7: smart device smart device X: device smart device controller. This reference point is outside the scope of this document. NSCL to MAS interface (internal in ETSI) Does not exist mId (Note: intermediate node is G’ equivalent) Does not exist in R1 (but is mId variant?) mId Does not exist in R1 Considered out of scope Out of scope (position similar to TIA) For further discussion: mIa and dIa have no equivalent in TIA TR50