GISFI #9, Mumbai IoT Working Group June 20, 2012 IoT/M2M/Smart Device Communications (SDC) Contribution on Service Capabilities

Size: px
Start display at page:

Download "GISFI #9, Mumbai IoT Working Group June 20, 2012 IoT/M2M/Smart Device Communications (SDC) Contribution on Service Capabilities"

Transcription

1 GISFI #9, Mumbai IoT Working Group June 20, 2012 IoT/M2M/Smart Device Communications (SDC) Contribution on Service Capabilities Contributors: Anil Kripalani, WIrefreeCom Inc. Mihai Voicu, ILS Technology Thomas Burke, OPC Foundation Presenter: Anil Kripalani This contribution GISFI_IoT_ supports the document GISFI_IoT_ , which is based on a baselined specification in TIA TR-50, originally submitted by OPC Foundation and ILS Technology

2 M2M/IoT/SDC Systems Need to enable low-cost solutions for large scale deployment M2M/IoT/SDC will achieve global scale if we truly support plug-and-play interoperability for connected devices and IoT systems taking full advantage of new Web technologies and the Cloud Service Capabilities Standards are critical for plug and play Learning and reusing from the industrial automation sector

3 M2M/IoT/SDC Key Definitions (extracted from TIA TR50.1 Smart Device Communications Common Terminology PN Approved Dec 2011) * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

4 M2M/IoT/SDC Definitions Machine-to-Machine communications A form of data communication which involves one or more entities that do not necessarily need human interaction. The entities include devices (e.g. sensor modules or identity tags), network/application interface devices (e.g. data collectors or tag readers), network elements, and functional entities (e.g. application server or controllers). Smart Device Communications is a form of data communication which involves one or more entities similar to M2M Communication or MTC; however, SDC do consider the applications with limited human interaction. The entities include devices (e.g. sensor modules, identity tags, smartphones and electronic book readers), network/application interface devices (e.g. data collectors or tag readers), network elements, and functional entities (e.g. application server, controllers, and Web servers). * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

5 M2M/IoT/SDC Definitions Sensor Module A sensor is a device that detects and measures a physical, chemical, and bio-chemical quantity and converts it into a signal which can be read by an observer or by an instrument. A sensor module typically includes circuitry to convert the measures into digital readings that can be ported into a computer or a digital communication device. Smart Device Any sensing or actuating element coupled with an embedded, accessible intelligence controller * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

6 Gateway M2M/IoT/SDC Definitions In a communications network, a gateway is a network node equipped for interfacing with another network that uses different protocols. A gateway may contain devices such as protocol translators, impedance matching devices, rate converters, fault isolators, or signal translators as necessary to provide system interoperability. It also requires the establishment of mutually acceptable administrative procedures between both networks. A protocol translation/mapping gateway interconnects networks with different network protocol technologies by performing the required protocol conversions. Routers exemplify special cases of gateways. Gateways, also called protocol converters, can operate at any layer of the OSI model. The job of a gateway is much more complex than that of a router or switch. Typically, a gateway must convert one protocol stack into another. * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

7 Remote Sensing M2M/IoT/SDC Definitions Remote sensing is the small or large-scale acquisition of information of an object or phenomenon, by the use of either recording or real-time sensing device(s) that are wireless, or not in physical or intimate contact with the object (such as by way of aircraft, spacecraft, satellite, buoy, or ship). In practice, remote sensing is the stand-off collection through the use of a variety of devices for gathering information on a given object or area. Middleware Middleware is the software modules connecting application software and operating systems. Typically, it consists of User Interface (UI) and Application Interface (API). * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

8 Application Servers M2M/IoT/SDC Definitions An application server is a software framework dedicated to the efficient execution of procedures (programs, routines, scripts) for supporting the construction of applications. The term was originally used when discussing early client server systems and servers that ran SQL services[1] and middleware servers to differentiate them from file servers. An application server acts as a set of components accessible to the software developer through an API defined by the platform itself. Normally the term refers to java application servers. When this is the case, the application server behaves like an extended virtual machine for the running applications, handling transparently connections to the database at one side, and connections to the web client at the other. * Source: TIA TR50.1 SDC Standard Definitions, Dec 2011

9 TIA TR-50: M2M/SDC Protocol Stack PoA application API node application API home application API smart device protocol smart text device protocol smart device protocol convergence convergence convergence transport 2 transport 2 transport 1 transport 1 PoA node server Access agnostic monitoring and bi-directional communication of events and information between smart devices and other devices, applications or networks Layers below the transport layer kept beyond the scope of the above TIA standard * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

10 AAA-SD M2M/IoT/SDC Definitions provide authentication, authorization and accounting services to other entities in the network to establish and enforce security policies. The services may include generation of keys, generation and validation of certificates, validation of signatures, etc. (SD -> Smart Devices) Home Application The home application is responsible for the business logic, either directly or via supervision and interaction with node and PoA applications and with PoA devices Node Application The node application acts as an intermediary between the home application and the PoA application and between the home application and the PoA device. Interacts with home application, PoA application and PoA device. May perform functions such as a data aggregation, a load balancing, etc. * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

11 PoA Application M2M/IoT/SDC Definitions PoA application provides resources to node or home applications or to other PoA applications. Interacts with home, node and PoA applications and with PoA devices. May perform functions such as autonomous reporting of values reported by devices, monitoring for values reported by devices that exceed specified limits, trend analysis of values reported by devices, etc. Container Software applications operate within containers. A container is hosted on a physical device, but there may be more than one container per physical device. A container may span multiple physical devices. The container provides services to the applications that operate within it, and enforce security policies * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

12 TIA TR-50: M2M/SDC High Level System Architecture PoA applications node applications home applications application management application domain admin admin admin PoA devices device management device domain smart device protocol smart device protocol smart device protocol authentication, authorization and accounting AAA-SD container convergence convergence convergence PoA container node container server container network management core IP * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

13 TIA TR-50: M2M/SDC High Level System Architecture PoA applications node applications home applications application management application domain Software applications operate within containers admin PoA devices smart device protocol convergence PoA container admin smart device protocol convergence node container admin smart device protocol convergence server container core IP device management AAA-SD container network management device domain authentication, authorization and accounting A container is hosted on a physical device, but there may be more than one container per physical device. A container may span multiple physical devices. The container provides services to the application(s) that operate within it, and enforce security policies. * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

14 TIA TR-50: M2M/SDC Reference Architecture home home application B1 B6 A1 B7 B2/B2' B4 node application node B5/B5' B3/B3' B8 PoA application/device PoA A3/A3' A2 authentication, authorization and accounting AAA-SD * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

15 M2M/IoT/SDC Service Capability Types Capability Type Capability Type ID Description Discovery Services DS Allows the home application to discover PoA Device/Applications within a PoA container and read the security configurations required to establish a secure communication SecureChannel Services SCS Allows the home application to establish a secure channel to communicate with the PoA Container NodeManagement Services NMS Allows the home application to add/delete/update PoA devices/application in a PoA container View/Query Services VQS Allows the home application to browse devices/applications in a PoA container * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

16 M2M/IoT/SDC Service Capability Types Capability Type Capability Type ID Description Attribute Services AS Allows the home application to read/update values in an PoA device or application Method Services MS Allows the home application to invoke methods on the PoA container (either on PoA device or PoA application) MonitoredItem Services Subscription Services MIS SS Allows the home application to performed operations on the PoA container, PoA device or PoA Application to create, delete or update monitoring items definitions. Must work in conjunction with Subscription Services. Allows the home application to create, delete or update subscriptions. Subscriptions are the mean for the notifications on Monitored Items to be send out. * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

17 M2M/IoT/SDC Standard Service Capabilities Capability Capability Type Description DeviceRegistration DS Should be used for the registration of a PoA device with the home application. ApplicationRegistration DS Should be used for the registration of a PoA application with the home application. DeviceDiscovery DS Should be used by the home application to retrieve the list of PoA devices included to the PoA container Should be used by the home application to retrieve the list of the PoA devices that are attached to a PoA Application ApplicationDiscovery DS Should be used by the home application to retrieve the list of PoA applications included to the PoA container AddDevice NMS Should be used by the home application to add a device to a PoA either to a PoA container or a PoA application DeleteDevice NMS Should be used by the home application to remove a device to a PoA either to a PoA container or a PoA application AddApplication NMS Should be used by the home application to add an applicaiton to a PoA container * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

18 M2M/IoT/SDC Standard Service Capabilities Capability Description Capability Type DeleteApplication NMS Should be used by the home application to remove an application to a PoA container ReadValue AS Should be used for the home application to interact with a PoA device to read a device s value. UpdateValue AS Should be used for the home application to interact with a PoA device to update/write a device s value. CreateSubscription SS Should be used by the home application to create notifications when data changes or event occurs on a PoA either in a PoA Application or PoA Device RemoveSubscription SS Should be used by the home application to remove notifications when data changes or event occurs on a PoA either in a PoA Application or PoA Device PublishData SS Should be used by the PoA (either a PoA application or PoA device) to send or report data changes or events to home application. InvokeAction (Call) MS Should be used by the home application to invoke (synchronous) a pre-defined in the PoA (PoA application or PoA device) callable action (method) that can perform tasks on the PoA. * Source: TIA TR50 PN _V05 SM2M/Smart Device Communications Reference Architecture, Dec 2011

19 The Need to Standardize IoT Service Capabilities Common Global Minimum Set Common Protocols Designed to be extensible Promotes Interoperability Enables Plug and Play subsystems Supports differentiation in Features Supports different regional regulatory requirements

20 Some Thoughts OneM2M Partnership Project happening now GISFI participation? Input from GISFI on Service Capabilities should reflect real industrial experience GISFI should add value through knowledge from novel vertical markets GISFI should facilitate plug and play and certification testing of IoT systems and devices in India

21 Thank you! Anil Kripalani