+ All Categories
Home > Documents > Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant...

Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant...

Date post: 14-Dec-2015
Category:
Upload: jason-millner
View: 215 times
Download: 2 times
Share this document with a friend
Popular Tags:
13
Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139
Transcript
Page 1: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

Internet of Things (IoT)Work Group

GISFI IoT Architecture Comparison

Soma Bandyopadhyay and Hemant Kumar Rath

TCS

Doc No: GISFI_IoT_201112139

Page 2: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

2

• TCS proposed arch in GISFI – With Incorporated comments from last meeting

• ETSI high level arch with interfaces• GISFI-ETSI interfaces/reference point comparisons• GISFI-TIA interfaces• GISI-ETSI-TIA Comparison• TIA-ETSI Comparison• GISFI – 3GPP Comparison• Conclusion

GISFI # 07, Dec 19-22, 2011, New Delhi

AgendaAgenda

Page 3: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

3

System ArchitectureSystem Architecture

Addressable Sensors

Services

Access Gateway with Sensor Middleware

Application Middleware/Controller

Ban

kin

g utili

ties

Agr

icul

ture

Hea

lthca

re

I1

I2

I3

Sensor-domain

Sensors to network backbone interface

controlled by access gateway

sensor middleware

Application/Service to network

backbone interface

IoT Core

IoT core to application

controller interface

Indicates the communication across the application controllers & across the access gateways

Proposed IoT ArchProposed IoT Arch

Page 4: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

4

ETSI High level Architecture with InterfacesETSI High level Architecture with Interfaces

mid

mia

diamid

Page 5: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

5

GISFI-ETSI InterfacesGISFI-ETSI Interfaces

CASE -1 Direct device to device Connectivity and interfaces are not considered in GISFI current arch

Page 6: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

66

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.

TIA Reference PointsTIA Reference Points

GISFI # 07, Dec 19-22, 2011, New Delhi

Page 7: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

GISFI-TIA InterfacesGISFI-TIA Interfaces

Page 8: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

3GPP M2M High-level Architecture3GPP M2M High-level Architecture

•MTC : Machine Type Communication•MTCu : Provides MTC devices access to the 3GPP network for the transport of user traffic•MTCi : Reference point for MTC server to connect the 3GPP network via 3GPP bearer service•MTCsms : Reference point for MTC server to connect the 3GPP network via 3GPP SMS

•Explains 3 different type of Communicating scenarios•Scenario 1 (Located in the operator domain)•Scenario 2 (Located outside the operator domain)•Scenario 3 (Communication directly with each other without an intermediate MTC server)

•Comments•Low Mobility, secure connection, group based triggering•Time controlled transmission (only at pre-defined time)•Time tolerant transmission•Network operator shall provide PS service with or without an MSISDN.

3GPP Bearer Services /SMS/IMS

MTC Device

MTC Server

MTC Server

MTCu

MTCsms

MTCi

Page 9: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

GISFI vs. 3GPPGISFI vs. 3GPP

3GPP Bearer

Services /SMS/IMSMTC

Device

MTC Server

MTC Server

MTCu

MTCsms

MTCi

GISFI # 07, Dec 19-22, 2011, New Delhi

Page 10: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

10IoT_Arch_Dec 2011 GISFI # 07,

GISFI-ETSI-TIA ComparisonGISFI-ETSI-TIA Comparison

Standard body

Domain distribution Interconnection among gateway

Direct device addressability

Interfaces

GISFI 3 domains : Sensor, IoT core, Application/service.Applications do not have direct accessibility to devices

Chaining or interoperation with gateways and application controller. Present , But does not have any interfaces

Device /sensors are addressable . Present.

Three interfaces – I1, I2, I3 – device to device interface is out of scopeI2 ->B5: application server -> smart deviceI2B1. application -intermediate node.I2->B5,B1->mid

ETSI Two domains : Network Domain (includes access , core, & M2M service

capability), Device and Gateway Domain

NA Present (Direct Connectivity from application to device as well as device to device).The M2M Device performs the procedures such as registration, authentication,authorization, management and provisioning with the Network Domain

Three interfaces – mia,mid,dia device to device interfaces are also considered

TIA Two domains : Device & application. Application directly access device gateway & devices

Chaining of intermediate nodes.B6,B7 are defined reference points

Present -Direct Device Interaction. Uses standardized set of verbs applied to a specific device like Set, Get. Device to device interaction is also possible

Intermediate nodes/gateways to gateways interfaces are considered

GISFI # 07, Dec 19-22, 2011, New Delhi

Page 11: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

11

GISFI-3GPP ComparisonGISFI-3GPP Comparison

Standard body

Domain distribution Interconnection among gateway

Direct device addressability

Interfaces

GISFI 3 domains : Sensor, IoT core, Application/service.Applications do not have direct accessibility to devices

Chaining or interoperation with gateways and application controller. Present , But does not have any interfaces

Device /sensors are addressable . Present.

Three interfaces – I1, I2, I3 – device to device interface is out of scope

3GPP 3 different types of communications

NA Alternative addressing solution based on IP addresses . Nodes are addressable

MTC devices communicating with the MTC server through API.(within the access network). MTC server connects to IoT stack through I1 (functionality need to be understood)

MTC device supporting directly Internet, can connect to I2

GISFI # 07, Dec 19-22, 2011, New Delhi

Page 12: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

1212

Conclusion: TCS Proposed IoT Architecture in GISFIConclusion: TCS Proposed IoT Architecture in GISFI

GISFI # 07, Dec 19-22, 2011, New Delhi

• I1 Signifies a family of interfaces including the 3rd party network accessibility.

• Device to device connectivity and interfaces are not considered.

• I2 Signifies the interfaces for application middleware/ application to devices directly, as well as application middleware to access gateway. Devices are considered addressable.

• Internet is considered as Backbone network.

• Chaining among application middleware nodes as well as access gateways are considered.

• No interfaces are defined for this. No use case is mapped yet. Chaining of application middleware may suitable for distributed computing.

• I3 (APIs) Interface exposed from application middleware to Application does not exist in ETSI & TIA

Page 13: Internet of Things (IoT) Work Group GISFI IoT Architecture Comparison Soma Bandyopadhyay and Hemant Kumar Rath TCS Doc No: GISFI_IoT_201112139.

1313GISFI # 07, Dec 19-22, 2011, New Delhi


Recommended