- You understand the Kaa platform microservice-based architecture.
Kaa command invocation feature helps controlling devices remotely. Using it, you can send short lived messages to connected devices (commands), make them react as necessary, and receive responses. For example, you can toggle light, pop up car trunk, or request an immediate device status report.
The command invocation feature is implemented in Kaa primarily with Command Execution Extension service (CEX) and REST Command Invocation service (RCI).
Command Execution Extension service (CEX) extends the communication capability of Kaa Protocol (1/KP) by implementing Command Execution Protocol (11/CEP). CEX supports this extension protocol to deliver commands to endpoints and consume endpoint command execution result. As with other Kaa extension services, CEX uses Extension Service Protocol (4/ESP) for integration with a communication service.
CEX implements a proactive command push—commands are sent to an endpoint as soon as possible, and an explicit endpoint subscription is not required.
CEX communicates with RCI via the Command Invocation Protocol (12/CIP). This protocol is used to accept command requests and return results back to the caller.
The table below summarizes the list of Kaa platform components that contribute to this feature:
|Command Execution Extension (CEX)||1.1.4|
|REST Command Invocation (RCI)||1.1.2|