Unit 4 Architectural Approach for IoT

Unit No: 4 Architectural Approach for IoT Empowerment

Security and Privacy Elements Personal acquisition and local storage: The primary means of data acquisition in GAMBAS are personal Internet-connected objects that are owned by a particular user such as a user’s mobile phone, tablet, laptop, etc.

The data acquired through the built-in sensors of these devices is stored locally such that the user remains in full control. Hence the middleware provides mechanisms to disable particular subsets of sensors in order to prevent the accumulation of data that a user may not want to collect and store at all.

Security and Privacy Elements

Anonymised data discovery: In order to enable the sharing of data among the devices of a single user or a group of users, the data storages on the local device can be connected to form a distributed data processing system. To enable this, the GAMBAS middleware introduces a data discovery system that makes use of pseudonyms to avoid revealing the user’s identity.

The pseudonyms can be synchronized in automated fashion with a user defined group of legitimate persons such that it is possible to dynamically change them.

Security and Privacy Elements Policy-based access control: To limit the access to the user’s data, the networked data storages perform access control

based on a policy that can be defined by a user. In order to reduce the configuration effort, the GAMBAS middleware encompasses a policy generator tool that can be used to derive the initial settings based on the user’s sharing

behaviour that he exhibits when using social services.

Security and Privacy Elements Secure distributed query processing: On top of the resulting set of connected and access-controlled local data storages, the GAMBAS middleware enables distributed query processing in a secure manner. Towards this end, the query processing engine makes use of authentication mechanisms and encryption protocols that are bootstrapped by means of novel key exchange mechanisms that leverage the existing web-infrastructure that is already used by the users.

What is Standardisation Standardisation is a voluntary cooperation among industry, consumers, public authorities and other interested parties for the development of technical specifications based on consensus. Standardisation complements market-based competition, typically in order to achieve objectives such as the interoperability of complementary products/services, to agree on test methods and on requirements for safety, health and environmental performance. Standardisation also has a dimension of public interest. Standard makers should be close to standard users/implementers.

What are the Gaps between IoT Standardisation, IoT Research, IoT Development and IoT Innovation ? In order to fill gaps between IoT Research, Development and Innovation and standardisation life cycles , IERC encourages the creation of prestandardisation groups. They allowed to build communities around consensus to develop standards, for example on Semantic Interoperability.

Research, development and innovation life cycle

M2M Service Layer Standardisation

M2M Service Layer Standardisation Standardised M2M service layer including definitions of interworking with existing underlying standards like 3GPP or iPv6 on the WAN side, ZigBee or KNX on the M2M area side and a clear definition of application interfaces will open up a complete new business opportunities for existing players and more important for new players. The heterogeneous standards environment is shown in figure. As such this horizontally integrated service layer can be seen as the operational system of the future IoT providing a set of commonly required services to a broad range of applications and underlying communication technologies.

Opportunities An open world-wide standard M2M service layer based on the future oneM2M standard will open up the possibility for a broad range of companies and players to enter the business field with different sets of possible business models. A broad range of business models and solutions can be envisaged. In an initial deployment phase companies can provide the software and the required services for the implementation of a full M2M network for the service providing companies and the device manufacturers.

Opportunities The available open application interfaces in the different component of the M2M architecture (device, gateway, network) will allow for an open market place for the development of M2M applications. These applications can be integrated into the M2M network components and thus can extend the capabilities in a very flexible manner. These applications can be independent of the deployed communication technology and thus can address a much broader market place than specific applications.

OGC Sensor Web for IoT Location and Sensors in IoT All IoT things are at a location. Location is a fundamental piece of information for most of the new and innovative applications enabled by IoT. Location information is ubiquitous but not always correct. Location data quality can be easy to maintain, but subtle mistakes can creep in and cause failures, damage and death. Accurate handling of location information in IoT is being built on the standards for location well established by several standards developing organizations, in particular as established by the Open Geospatial Consortium (OGC).