Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Ownership and identity relationships
  • Object Identifier and Namespace
  • Authentication and Authorization
  • Governance of data and Privacy

see See details in our paper published in the proceedings of the IEEE World Forum on Internet of Things (WF-IoT) 2014:  Challenges from the Identities of Things

...

There is no special identifier for IoT. And there won't be one kind of Identifier. Many standards, de facto standards, protocols and solutions already exist in the area of IoT. There are various kinds of identifiers with different characteristics suitable for specific purposes. (for details see our Identifier Survey).

...

Mapping and discovery become important services in large IoT deployments with differnt different systems, standards and domains. Let's give an example: A street lamp might have a field bus address consisting of 2 bytes. It is connected with a gateway. Within the gateway the lamp is mapped to "lamp 123". A lamp management system can switch on and off "lamp123" intertnally. Via a REST interface the lamp management system exposes the lamp, for example as oneM2M "application entity". So other management systems can switch the lamp on and off by sending messages to a specific oneM2M URL. In this example a thing (lamp) is identified with different identifiers that are mapped to each other (field bus address, internal ID, oneM2M-URL).

...

It takes more effort to find and map various identifier identifiers but the mapping process also gives also the possibility to implement access control mechanisms. Only entitled service services or user users are able to rersolve resolve or discover the identifier of a thing.This way its it's possible to control whether an identifier is visible or not or who can "see" a certain thing or not. In our example the policy check could be implemented in the lamp management system or with the REST API.

...

Absolutely not. In most cases DNS (Domain Name Service) can't be used directly. DNS was designed to map between IP-addresses and human readable domain names. DNS is not able to handle identifier formats from various IoT protocols. It is also not possible to propagate changes in a very short time. But DNS has a outstanding anoutstanding governance process that ensures world-wide unique identifiers. So DNS is at least part of most mapping processes. In our example DNS might be used to find the company domain of the lamp management or the address of the REST API.

...

Privacy and Trust becomes crucial in the Internet of Things because even arbitrary data, like a temperature, might be related to a user when it’s combined with other data like location or is profiled over a period of time. So it is possible to see whether a person is at home or not. One extreme exemplary privacy issues issue is the ability to determine what kind of TV-Program a user is watching just from measuring the energy consumption with very frequent samples [ 1 ]. 

...

How to design a privacy ensured IoT system?

The are various design startegies strategies and architecture concepts to ensure privacy in communication and during resource access control. The Identity of Thing Discussion Group supports IEEE P2413 IoT Architecture Working Group in writing a Privacy - and  and Trust Architecture View Point. This viewpoint is described in an Architecture viewpoint template of ISO/IEC/IEEE 42010:2011. This uses describes concerns and models to frame the viewpoint. Find here the: current concerns of the Privacy and Trust Architecture Viewpoint. This first draft of the complete P2413 architecture draft is expected to be published late 2017.

...