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

Agenda TCS proposed arch in GISFI ETSI high level arch with interfaces 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

Proposed IoT Arch System Architecture utilities Agriculture Healthcare Services utilities Agriculture Healthcare Banking Proposed IoT Arch System Architecture Application/Service to network backbone interface I3 Application Middleware/Controller I2 IoT core to application controller interface Indicates the communication across the application controllers & across the access gateways IoT Core Access Gateway with Sensor Middleware Sensors to network backbone interface controlled by access gateway sensor middleware I1 Sensor-domain Addressable Sensors 3

ETSI High level Architecture with Interfaces mia mid dia mid

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

TIA Reference Points 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. GISFI # 07, Dec 19-22, 2011, New Delhi 6

GISFI-TIA Interfaces ETSI M2M / TIA architecture harmonization 7

3GPP M2M High-level Architecture 3GPP Bearer Services /SMS/IMS MTC Device MTC Server MTCu MTCsms MTCi 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.

GISFI vs. 3GPP 3GPP Bearer Services /SMS/IMS MTC Device MTC Server MTCu MTCsms MTCi GISFI # 07, Dec 19-22, 2011, New Delhi

GISFI-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 scope I2 ->B5: application server -> smart device I2B1. 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 IoT_Arch_Dec 2011 GISFI # 07, GISFI # 07, Dec 19-22, 2011, New Delhi

GISFI-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

Conclusion: TCS Proposed IoT Architecture in GISFI 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 GISFI # 07, Dec 19-22, 2011, New Delhi 12

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