11. Application & Device ManagementΒΆ
GEISA provides a uniform mechanism for managing edge devices and the applications that run on top of them. ADM conformant devices from different platform vendors can be managed by a single ADM conformant edge management system. See System Architecture for more discussion of the general concept.
ADM conformance devices support a set of standard transactions using the Open Mobile Alliance Lightweight M2M [LwM2M] transaction definitions, over the IETF CoAP [RFC7252] protocol. ADM conformant platform implementations MUST support the LwM2M transactions detailed in this chapter and the supporting device behaviors described. ADM conformant edge management systems MUST support the LwM2M transactions detailed in this chapter and the supporting edge management system behaviors described.
Note
ADM conformance does not preclude platforms or edge management systems from supporting additional or supplementary management protocols.
Note
Platform vendors may offer an ADM conformant device without offering an ADM conformant edge management system or an ADM conformant edge management system without offering an ADM conformant device.
As described in the GEISA Application Programming Interface (API), GEISA provides a default Application Messaging and Configuration
mechanism. ADM-conformant platforms transport these messages over CoAP. An
ADM-conformant EMS MUST provide the required ReST POST operation for an
authorized Vendor Application Server to submit messages for delivery to an
Edge Application. That message is delivered through /3600 Server to
Client. In the other direction, the EMS MUST make /3600 Client to Server
application messages available for Kafka-protocol Data Distribution. Configured
Data Distribution routes determine actual publication. Other EMS ReST
operations are not required for GEISA interoperability.