IoT-A: main Architectural Reference Model concepts

Transcription

1 IoT-A: main Architectural Reference Model concepts Alessandro Bassi IoT-A Technical Coordinator 1 st iot-forum, Berlin Nov 23rd, 2011

2 IoT-A Fact Sheet Flagship FP7 IP project,call 5, Objective 1.3 Total Budget 18.6 M EUR 17 Partners from 8 EU countries Coordinator: Sebastian Lange Technical Coordinator: Alessandro Bassi Start Date: Sept 1st, 2010 Duration: 36 months.

3 IoT Domain - current status Vertical silos Fragmented architectures, no coherent unifying concepts, solutions exist only for specific application silos. No coherent approaches to implement the IoT have been proposed, yet. Many island solutions do exist (RFID, Sensor nets, etc.). Little cross-sectorial re-use of technology and exchange of knowledge. In essence, today we have only Intranets of Things.

4 Introducing the IoT-A tree: a generic Reference Model, derived from Business considerations, application-based requirements and current technologies, able to generate different Reference architectures depending on domain-specific requirements, to be used as a blueprint for concrete architecture design.

5 IoT-A Objectives Establishing Internet of Things modelling foundation. Providing guidelines for the technical design of its protocols, interfaces, and algorithms; Building the enabling architectural framework for the IoT; Federating heterogeneous IoT technologies into a homogeneous IoT fabric; Removing the barriers of IoT widescale acceptance.

6 Means of Implementation 1 Setting up of an architectural reference model for the interoperability of Internet-of-Things systems, 2 Outlining principles and guidelines for the technical design of its protocols, interfaces, and algorithms 3 Establishing corresponding mechanism for its efficient integration into the service layer of the FI

7 Means of Implementation (cont d) 4 Providing a protocol suite based on open protocols centred around a narrow waste 5 Defining a novel resolution infrastructure, allowing scalable look up and discovery of Internet-of-Things resources, entities of the real world, and their associations; 6 Building novel device platform components; 7 Implementing real-life use cases demonstrating the benefits of the developed architecture.

8 Heterogeneity of technologies in the IoT is significantly higher than in traditional computing systems: they include RFID, sensor networks, embedded systems and mobile technologies; Interoperability has to be supported in all functionality groups and communication layers; Communication technologies will co-exist: gateways will be a necessity; Interoperability not only has to be achieved across a single domain, but across different administrative and application domains.

9 Architectural Reference Model

10 Reference Model

11 Domain Model

12 Communication Model: Channel Analysis Standard Internet Model IoT Model

13 Communication Model: The Protocol Stack

14 Physical layer The physical layer remains unchanged from the OSI definition. This is necessary in order to neither exclude any available technology, nor to prevent emerging solutions from being integrated into the reference model. The convergence of the different solutions taking part in the communication stack will be managed in the upper layer.

15 Link layer In order to address the heterogeneousness of networking technologies represented in the IoT universe, the link layer requires special attention. In fact, most networks implement similar, but customised communication schemes and security solutions. In order for IoT systems to achieve full interoperability, as well as the support of heterogeneous technologies and a comprehensive security framework, this layer must allow for diversity. But, at the same time, it needs to provide upper layers with uniform interfaces

16 Network layer Here, again, the layer provides the same functionalities as the correspondent OSI stack. However, in order to support global manageability, interoperability, and scalability, this layer needs to provide a common communication paradigm for every possible networking solution.

17 ID layer The virtual-entity identifier (VE-ID), split from the locator, is the centre of the first convergence point in the communication stack, i.e. the ID layer. Leveraging on uniform interfaces provided by the link layers, the ID Layer allows for a common resolution framework for the IoT. Also, security, authentication, and high-end services will exploit this layer for providing uniform addressing to the many different devices and technologies in IoT networks.

18 End-to-end layer This layer takes care of translation functionalities, proxies/gateways support and of tuning configuration parameters when the communication crosses different networking environments. By building on top of the ID and the network layers, the end-to-end layer provides the final building block for achieving a global M2M communication model. Data layer At the top of the communication stack, the data layer interfaces with the data layer. A high-level description of the data pertinent to IoT is provided by the information model.

19 A gateway for IoT

20 Thank you for your attention