# US 12,111,733 B2 · Orchestrating a container-based application on a terminal device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,111,733 B2 - Document ID: US12111733B2 - Status: Granted - Kind: B2 - Application number: 17/352,439 - Filed: 2021-06-21 - Published: 2021-12-30 - Granted: 2024-10-08 - Earliest claimed: 2020-06-26 - Assignees: Siemens Aktiengesellschaft - Applicants: Siemens Aktiengesellschaft - Inventors: Christian Muff Knierim; Christian Peter Feist - Web page: https://patentgrep.com/patent/US12111733B2 ## CPC - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 9/5005: {to service a request} - G06F 9/5072: {Grid computing} - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 11/142: {Reconfiguring to eliminate the error (group management mechanisms in a peer-to-peer network H04L67/1044)} - G06F 11/1471: involving logging of persistent data for recovery - G06F 11/1482: using middleware or operating system [OS] functionalities - H04L 41/0894: Policy-based network configuration management - G06F 9/544: {Buffers; Shared memory; Pipes} - G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing} - G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Provided is a method for orchestrating a container-based application that is executed on a terminal device, in which implementation information is received in an orchestration slave unit on the terminal device via a communication connection from an orchestration master unit, and the application is configured and/or controlled by the orchestration slave unit based on the implementation information, wherein the received implementation information is additionally saved persistently in a memory unit in the terminal device, and if the communication connection to the orchestration master unit is interrupted, the most recently saved implementation information is retrieved from the orchestration slave unit and the application is configured and/or controlled based on the most recently saved implementation information. ## Claims ### Claim 1 A method for orchestrating a container-based application that is executed on a terminal device, the method comprising: receiving implementation information in an orchestration slave unit on the terminal device via a communication connection from an orchestration master unit, wherein the orchestration slave unit is controlled by a control manager in the orchestration master unit, and the orchestration slave unit reports a status at short time intervals; and configuring and/or controlling the application by the orchestration slave unit based on a contingency policy contained within the implementation information, wherein the implementation information is additionally saved persistently in a memory unit in the terminal device; wherein, if the communication connection to the orchestration master unit is interrupted, a most recently saved implementation information is retrieved from the orchestration slave unit and the application is configured and/or controlled based on a contingency policy of the most recently saved implementation information, and a safety-relevant container instance, identified by the orchestration master unit, is preferentially instantiated by the orchestration slave unit; wherein the contingency policy of the most recently saved implementation information is designed such that different contingency measures are executed by different contingency levels; wherein the orchestration slave unit changes a configuration and/or a control of the application depending on the contingency policy received from the orchestration master unit; wherein the orchestration slave unit starts an at least one contingency container instance and/or stops at least one working container instance of the application depending on the contingency policy, and the different contingency levels comprise different level policies and, depending on an ascertained contingency level, a level policy assigned to the contingency level is activated by the orchestration slave unit. ### Claim 2 (depends on 1) The method as claimed in claim 1, wherein if the communication connection to the orchestration master unit is interrupted, and if at least one container instance fails at the terminal device, the at least one container instance is restarted by the orchestration slave unit using the most recently saved implementation information. ### Claim 3 (depends on 1) The method as claimed in claim 1, wherein if the communication connection to the orchestration master unit is interrupted and the terminal device is restarted, the application is started by the orchestration slave unit using the most recently saved implementation information. ### Claim 4 (depends on 1) The method as claimed in claim 1, wherein the prioritized container instance is identified as prioritized when the implementation information is prepared by the orchestration master unit. ### Claim 5 (depends on 1) The method as claimed in claim 1, wherein at least one contingency container image is saved in the memory unit, and the at least one contingency container image executes at least one function which, when the communication connection is present, is executed by an application interface connected to the terminal device via the communication connection. ### Claim 6 (depends on 1) The method as claimed in claim 1, wherein the contingency level is ascertained depending on a duration and/or a type of a failure of the communication connection and/or of the master orchestration unit. ### Claim 7 (depends on 6) The method as claimed in claim 6, wherein, depending on the level policy, an at least one further contingency container instance is started and/or different amounts of resources are assigned to the at least one contingency container instance for a duration of the contingency level. ### Claim 8 (depends on 7) The method as claimed in claim 7, wherein, depending on the level policy, container instances that are present but are not necessary for the contingency operation are stopped, paused, or resource assignments are changed, and resources that have thereby become free are assigned to the contingency container instance. ### Claim 9 (depends on 8) The method as claimed in claim 8, wherein, after restoring the communication connection, data collected in the contingency container instance is transmitted to an application interface. ### Claim 10 (depends on 1) The method as claimed in claim 1, wherein after restoring the communication connection, a normal operation policy is received from the orchestration master unit in the orchestration slave unit, and the terminal device is transferred into a normal state. ### Claim 11 A system for orchestrating a container-based application that is executed on a terminal device, comprising: an orchestration slave unit associated with the terminal device; an orchestration master unit connected via a communication connection to the terminal device, wherein the orchestration slave unit is controlled by a control manager in the orchestration master unit, and the orchestration slave unit reports a status at short time intervals, the system configured to: receive implementation information in the orchestration slave unit via the communication connection from the orchestration master unit; and configure and/or to control the application by the orchestration slave unit based on a contingency policy contained within the implementation information, wherein the implementation information is additionally saved persistently in a memory unit in the terminal device; wherein, if the communication connection is interrupted, the most recently saved implementation information is retrieved from the orchestration slave unit and the application is configured and/or controlled based on a contingency policy of a most recently saved implementation information, and a safety-relevant container instance, identified by the orchestration master unit, is preferentially instantiated by the orchestration slave unit; wherein the contingency policy of the most recently saved implementation information is designed such that different contingency measures are executed by different contingency levels; wherein the orchestration slave unit changes a configuration and/or a control of the application depending on the contingency policy received from the orchestration master unit; wherein the orchestration slave unit starts an at least one contingency container instance and/or stops at least one working container instance of the application depending on the contingency policy, and the different contingency levels comprise different level policies and, depending on an ascertained contingency level, a level policy assigned to the contingency level is activated by the orchestration slave unit. ### Claim 12 (depends on 1) A computer program product, comprising a computer readable hardware storage device having computer readable program code stored therein, said program code executable by a processor of a computer system to implement the method as claimed in claim 1.