Provisional Architecture for oneM2M

Slides:

Advertisements

Similar presentations

Internet of Things (IoT) Work Group

Advertisements

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

ETSI M2M / TIA architecture harmonization O. Elloumi.

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

OneM2M portal introduction Group Name: Technical Plenary Source: Gerry McAuley, ETSI, Meeting Date: Agenda Item: 1.5.

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

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

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Common Service Entities

Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda Item:

Draft-engelstad-manet- name-resolution-00.txt IETF 57, Vienna MANET WG meeting Paal Engelstad, Telenor R&D / UniK.

WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.

Proposal for WG3 & WG5 work area split

Computer Science and Engineering - University of Notre Dame Jimmy Neutron CSE 40827/60827 – Ubiquitous Computing December 9, 2009 Project Presentation.

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

Process for Documenting Resources related services and Alignment with Service Components Group Name: WG2-ARC-( ) Source: Ericsson Meeting Date:

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:

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) 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.

Introduction to IETF CoRE Link Format Soumya Kanti Datta Mobile Communications Department

Introduction to Telecommunications, 2/e By M.A.Rosengrant Copyright (c) 2007 by Pearson Education, Inc. All rights reserved. Figure 24–1 CDMA spread spectrum.

Home Device Caching & Replacement Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

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

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

ETSI TCCE WG4 work G. Marque-Pucheu (Airbus / ETSI TCCE WG4) 26-27/08/ 2014.

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

Common Channel Tag Mobile System RTlab Kang Moo jin.

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,

Munix Bus WiFi Authentication, Log Management, Internet Security, Content Filter & VPN Service Internet Gateway & Business Intelligence

Sensors Journal, IEEE, Issue Date: May 2013,

Survey on architecture of Mobile Web Services

Business Intelligence

Munix Healthcare Customer Profiling, Frequency Analysis, Location Mapping, Movement Analysis, Web Classification, Time Analysis, and much more …. Internet.

3GPP MBMS protocol stack

Cisco Unified Communications Management

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Discussion about Use Case and Architecture in Developer Guide

Francisco da Silva, Senior Councillor, Huawei

Information Collection and Presentation Enriched by Remote Sensor Data

MAF&MEF Interface Specification discussion of the next steps

Solving the IoT Platform Challenge

Project Proposals: ODL-SDNi App

SUPA/YMCA (Yang Models for Configuration and topology Abstraction)

GF and RS, Dept. of CS, Mangalore University

Proximal IoT Interworking solution discussion

3GPP Interworking Abstraction

EA C451 Vishal Gupta.

oneM2M Work on IoT Semantic and Data Model Interoperability

Considering issues regarding handling token

OmniRAN Introduction and Way Forward

LWM2M Interworking with <mgmtObj> Resources

QOS Requirements for Real-Time Services over IP

Open-O GUI Project Proposal

Location Based Services support

Advanced Network Training

UMTS Terrestrial Radio Access Network Architecture

3GPP V2X Interworking Potential Impact

TITLE - TITLE - TITLE Subtitle – Subtitle - Subtitle

HGI (Home Gateway Initiative) Progress report

GSC: Standardization Advancing Global Communications

IETF-100, MPTCP WG, November 2017

Francisco da Silva, Senior Councillor, Huawei

OmniRAN Introduction and Way Forward

CS 31006: Computer Networks – Moving From End-to-End To Per Hop

Presentation transcript:

Provisional Architecture for oneM2M Group Name: WG2 Architecture Source: Mihai Voicu, ILS Technology Meeting Date: 2013-04-17 Agenda Item: ARCH

Underlying Network Services Application X Common Services Y Z Underlying Network Services Figure 1: High level services model

Underlying Networks Service functions Application functions X (0..p) CS functions Y (1..q) Y (1..1) – to other CSE Z (0..n) Underlying Networks Service functions Figure 2: Generic Functional view

Figure 3: Functional architecture node Notes: - Legacy devices are not show in this architecture. Integration of legacy devices is FFS Multiple domain cases are FFS. CSE functions in D, G, S are FFS and may be different. FFS: Z interface could be internal to the node X A A X A Intermediate node Infrastructure node A G S X A A A X X Y X X Y Y Y CSE CSE CSE Z Z Z A X Y CSE Z Figure 3: Functional architecture

(implemented in a device) CSE (implemented in a device) Y CSE (implemented in a device) CSE (implemented in a gateway) Y Y EXAMPLE 1

(implemented in a device) Application (use for aggregation) CSE (implemented in a device) Application (use for aggregation) X Y CSE (implemented in a device) CSE (implemented in a gateway) Y Y EXAMPLE 2

(implemented in a device) Application CSE (implemented in a device) X Y CSE (implemented in a gateway) CSE (implemented in a server) CSE (implemented in a device) Y Y Z Z Underlining Network EXAMPLE 3

(implemented in a device) Application CSE (implemented in a device) X Y CSE (implemented in a gateway) CSE (implemented in a server) CSE (implemented in a device) Y Y EXAMPLE 3’

(implemented in a device) CSE (implemented in a device) Y Y CSE (implemented in a gateway) CSE (implemented in a gateway) CSE (implemented in a gateway) Y Z Z Z Underlining Network (WIFI) Underlining Network (mobile) EXAMPLE 4

(implemented in a device) CSE (implemented in a device) Y CSE (implemented in a device) CSE (implemented in a device) Y Y EXAMPLE 5

X (0..p) CSE REST over IP REST over IP Y (1..q) Routing IP WIFI MOBILE Z (0..n)

Contact Details: Thank you! Mihai Voicu mvoicu@ilstechnology.com © ETSI 2011. All rights reserved