The Ericsson Device & Data Management (DDM) platform is developed to support a wide range of applications, vertical solutions, and use cases. The built-in data model in DDM is metadata-driven. It can be adapted to support languages and terms used in the different applications and vertical solutions.
DDM consists of three main feature areas:
- Device Management
- Hardware templates for rapid Gateway/Device registration
- Blacklisting function for Gateway/Device registration
- Tags for grouping Gateways/Devices to enable filtering in APIs and Rules engine
- Location (GPS coordinates) for Gateway/Device positioning
- Firmware and application updates
- LwM2M support for standardized Device management
- Data Management
- Storage of raw sensor data, harmonized to a common internal data model based on the IPSO model
- Creation of aggregated values per Sensor, Tag, Location etc. for rapid access to aggregated data
- Creation of “virtual Sensors” and “virtual Devices” based on physical sensor data through mathematical formulas
- Extendable metadata model to add more information about Devices and Sensors to simplify integration with external systems
- 3rd party data integration via secured APIs with user access control
- Real-time processing
- Rule engine to create alarm triggers; triggers can be set on discrete Sensor values or aggregated values based on Location, Device type, Sensor type, and Tags
- Multiple event Consumers per alarm trigger to enable 3rd party system/application integration
- Data streaming between Devices through the Transformer framework
- Actuators simplify end to end processes, reading and acting on values and triggers
All communication from gateways and devices to DDM is secured through encrypted communication channels via the open standard protocols HTTPS, AMQP, and LWM2M. As standards evolve new protocols are added. Other protocols such as MQTT can be added through proxy mediation services. The platform is agnostic to underlying connectivity channels (cellular, fiber, Wi-Fi, NB-IoT, LOra etc.) and transport protocol (UDP/TCP).
Access to data from applications such as mobile apps, web, integration software etc. is handled through APIs where every request is secured and handled based on user or applications access rights. User identity is handled through federated identity and will integrate with all credential solutions supporting SAML/OAUTH and/or API-keys where each key is given one or several access responsibilities.
Communication to the platform from the gateways and devices is based on various IP protocols. Applications can communicate with DDM through secured and documented APIs, gateways, devices, and end-users. DDM comes with a Dashboard where use cases are defined, and a device registration application for mobile devices used to simplify the registration of devices into their final position and use case.