|
Summary:
|
This Recommendation introduces digital entity architecture and its prospective in addressing interoperability and security among IoT applications.
This Recommendation defines an architecture framework for information-oriented services that makes use of existing infrastructures, including the Internet infrastructure, to enhance secure and managed information sharing over a distributed networking environment. It defines an architecture framework for information management based on the use of digital entity, and a common set of secure services that will help the registration, discovery, resolution, and dissemination of such digital entities. The set of services is designed to facilitate sharing across any storage boundaries, any heterogeneous application boundaries, and any organization boundaries.
Digital entity architecture defines a minimum set of needed architectural components, and services to provide a generic information and service interoperability. It will facilitate the interoperability of identification, description, representation, access, storage and security of IoT devices. This architecture framework encourages a common security and management interface across different IoT applications.
Under a digital entity architecture, information represented in digital form is structured as digital entity, each of which has an associated unique persistent identifier. However, metadata contained in the digital entities (e.g. location of the object) could be updated without changing its identifier.
The identifier allows the digital entities to be identified and discovered, regardless where they are located or stored. Digital entities are not confined within any particular application boundary and may be moved from host to host, accessed from application to application, shared from organization to organization, without losing its ownership or management control, in order to enhance interoperability. The digital entity's data model allows ownership and access control information to be defined by data owners independently of any specific applications.
This Recommendation can be used with different identification and addressing protocols (e.g. IP and/or non IP based networks).
|
