Method and system for deploying third party device services through an enclosed appliance interface using containers
View Patent ↗A method and system for deploying third party device services through an enclosed appliance interface using containers. Specifically, the disclosed method and system entail employing a generic plugin to facilitate the integration and execution of custom, third-party plugins onto the framework of a platform. The custom, third-party plugins, via the generic plugin, perform hardware device operations as secured and sandboxed computer processes (i.e., containers), which are stateless, and thus, fail to cause idling across computer processor and memory usage.
1. A method for deploying a third-party device service for a hardware device managed by a platform, comprising:
receiving, for the third-party device service, a services installation package (SIP) comprising a service container image (SCI), container registration information (CRI), device authorization information (DAI), and device operations information (DOI);
installing a service container onto the platform using the SCI;
generating, for the service container, a service container profile (SCP) using the CRI, the DAI, and the DOI;
registering the SCP with a generic container plugin (GCP) implemented on the platform; and
following a registration of the SCP:
executing the third-party device service on the hardware device using the service container, the SCP, and the GCP,
wherein executing the third-party device service on the hardware device using the service container, the SCP, and the GCP, comprises:
receiving, for the hardware device, a device operation request (DOR) comprising a device type and at least one device operation reference;
identifying the SCP using the device type and the at least one device operation reference;
accessing, as specified in the SCP, the DAI to obtain a device connection application programming interface (API) schema and a device disconnection API schema;
interfacing with the service container through the GCP and using the device connection API schema;
for each device operation reference of the at least one device operation reference:
accessing, as specified in the SCP, the DOI to identify a device operation API schema associated with the device operation reference; and
invoking a device operation of the hardware device using the device operation API schema.
2. The method of claim 1 , wherein:
the SCI is an image-based snapshot of the service container,
the service container is obtained upon restoration of the SCI, and
the restoration of the SCI comprises allocating computing resources for the service container.
3. The method of claim 1 , wherein the CRI comprises a container identifier (ID) referencing the service container, an application programming interface (API) schema type specifying an API schema, a profile ID referencing the SCP, a device type referencing a product line to which the hardware device belongs, and an operations list comprising at least one device operation reference.
4. The method of claim 3 , wherein the API schema pertains to a representational state transfer (REST)ful API.
5. The method of claim 3 , wherein the at least one device operation reference identifies at least one device operation performable by the hardware device, wherein the at least one device operation is a subset of all device operations for a plurality of hardware devices supported by the platform.
6. The method of claim 1 , wherein the DAI comprises a device connection application programming interface (API) schema and a device disconnection API schema, wherein the device connection API schema specifies a first set of properties required for connecting to the hardware device, wherein the device disconnection API schema specifies a second set of properties required for disconnecting from the hardware device.
7. The method of claim 1 , wherein the DOI comprises at least one device operation application programming interface (API) schema for at least one device operation performable by the hardware device, wherein the at least one device operation API schema specifies a set of properties required for invoking the at least one device operation.
8. The method of claim 1 , wherein the platform is a management and orchestration platform (MOP).
9. The method of claim 1 , wherein the GCP references to a container registry, wherein registering the SCP with the GCP comprises at least storing the SCP in the container registry.
10. The method of claim 1 , further comprising:
for each device operation reference of the at least one device operation reference:
obtaining, from the invoking, an operation response; and
after the operation response is obtained for each device operation reference:
terminating the service container through the GCP and using the device disconnection API schema.
11. A system for deploying a third-party device service for a hardware device managed by a platform, comprising:
a client computing system (CCS), wherein the CCS is executed on hardware; and
a platform operatively connected to the CCS, and comprising a container deployment agent (CDA) programmed to:
receive, from the CCS, a services installation package (SIP) comprising a service container image (SCI), container registration information (CRI), device authorization information (DAI), and device operations information (DOI);
install a service container onto the platform using the SCI;
generate, for the service container, a service container profile (SCP) using the CRI, the DAI, and the DOI;
register the SCP with a generic container plugin (GCP) implemented on the platform; and
following a registration of the SCP:
execute the third-party device service on the hardware device using the service container, the SCP, and the GCP,
wherein executing the third-party device service on the hardware device using the service container, the SCP, and the GCP, comprises:
receiving, for the hardware device, a device operation request (DOR) comprising a device type and at least one device operation reference;
identifying the SCP using the device type and the at least one device operation reference;
accessing, as specified in the SCP, the DAI to obtain a device connection application programming interface (API) schema and a device disconnection API schema;
interfacing with the service container through the GCP and using the device connection API schema;
for each device operation reference of the at least one device operation reference:
accessing, as specified in the SCP, the DOI to identify a device operation API schema associated with the device operation reference; and
invoking a device operation of the hardware device using the device operation API schema.
12. The system of claim 11 , wherein the platform further comprises a plurality of hardware devices, wherein the service container deploys a third-party device service for one hardware device of the plurality of hardware devices.
13. The system of claim 11 , wherein the platform further comprises a data repository, wherein the data repository comprises a container store for storing at least the service container and a container registry for storing at least the SCP.
14. The system of claim 11 , wherein the platform is a management and orchestration platform (MOP).
15. A non-transitory computer readable medium (CRM) comprising computer readable program code, which when executed by a computer processor, enables the computer processor to:
receive, pertaining to a third-party device service for a hardware device, a services installation package (SIP) comprising a service container image (SCI), container registration information (CRI), device authorization information (DAI), and device operations information (DOI);
install, using the SCI, a service container onto a platform whereon the computer processor resides;
generate, for the service container, a service container profile (SCP) using the CRI, the DAI, and the DOI;
register the SCP with a generic container plugin (GCP) implemented on the platform; and
following a registration of the SCP:
execute the third-party device service on the hardware device using the service container, the SCP, and the GCP,
wherein executing the third-party device service on the hardware device using the service container, the SCP, and the GCP, comprises:
receiving, for the hardware device, a device operation request (DOR) comprising a device type and at least one device operation reference;
identifying the SCP using the device type and the at least one device operation reference;
accessing, as specified in the SCP, the DAI to obtain a device connection application programming interface (API) schema and a device disconnection API schema;
interfacing with the service container through the GCP and using the device connection API schema;
for each device operation reference of the at least one device operation reference:
accessing, as specified in the SCP, the DOI to identify a device operation API schema associated with the device operation reference; and
invoking a device operation of the hardware device using the device operation API schema.
16. The non-transitory CRM of claim 15 , wherein the hardware device is managed by the platform.
17. The non-transitory CRM of claim 15 , wherein the device connection API schema, the device disconnection API schema, and each device operation API schema for the at least one device operation reference employ a same API schema type, wherein the same API schema type is specified in the CRI.
18. The non-transitory CRM of claim 15 , further comprising computer readable program code, which when executed by the computer processor, enables the computer processor to:
for each device operation reference of the at least one device operation reference:
obtain, from invoking the device operation, an operation response; and
after the operation response is obtained for each device operation reference:
terminate the service container through the GCP and using the device disconnection API schema.