It defines the structure of all information of Virtual Entities only at conceptual level and not at concrete level. In other words, it covers all aspects of adding information in the data. Here, structure covers attributes, relations and services that helps to know what, who, where, and when.
The detailed representation of information is not covered in this model.
This model covers following details (elements & their association) and of modelling of virtual entities:
1. Virtual Entity has attributes with name and its type.
Each virtual entity has a unique id or type i.e human, a car, or a temperature sensor.
A virtual entity can have zero to many attributes.
2. Attribute can have one or more values.
Each attribute has a name, a type (semantics) and one to many values.
3.Valuehas meta information(Meta data)
Value can further also have more values and each value has zero or many meta data. A virtual container keeps grouping of a value and associated zero or many meta data.
4. Meta Data might help to define other information like:
Time stamp (what time information is defined)
Location (Location where measurement took place
Quality (Quality of measurement) etc.
Meta data can itself have additional meta data i.e unit
5. Association between Virtual entity and Service description for specific attributes. Service allows to read attribute value or set the value based on changes in physical entity.
6. Services description describes services and associated interface. It also contains resource description that covers functionality of resource those are exposed by service.
7. Resource Description describes a resource and also contains description of device on which resource is hosted.
It is an IoT Platform which is available in following forms:
In-premise solution (Anyone can use it for their specialized or customized solution)
Cloud based solution (Kaa provides Platform as a service solution – PaaS for their customization solution)
Below are the two major characteristics of Kaa architecture:
Modular Architecture
*Microservice Architecture
This type of architecture offers below benefits:
Scalability
Extensibility
This platform offers below features:
Feature
Description
Device management
– Digital twining and records of such devices – Filtering & Grouping of devices – Accessing credentials and metadata of devices
Communication
Establishing communication between Device & Gateway to address below requirements: – Authentication & Authorization – Data exchange – Multiplexing
Data collection
Collection & Storage of below types of data and automatic remote transmission (telemetry) – Time Series – Device Logs – Alerts
Configuration management
Device and overall system configuration data in small & large scale deployment
Command invocation
Sending on demand or time based commands remotely.
Data analytics
Querying mechanism to analyze & visualize the data.
Software updates
Continuous software up-gradation
Visualization
Web interfaces for below requirements: – Data Visualization – Device Management – Platform Administration Also provides customizable dashboard
*Multi-tenancy
Support for accessing solution by multiple tenants
Infrastructure
Managing and monitoring clustering operations
Table 1.0
*Microservice architecture enables split a large solution into separate small multiple services where each service is responsible for specific functionality.
*Multi-tenancy is an architecture where a single instance of software is used by multiple tenants (group of users). Multi-tenancy architecture is different from multi-instances architecture.
Technology 