# US 12,764,200 B2 · Infrastructure-delegated orchestration backup using networked processing units > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,764,200 B2 - Document ID: US12764200B2 - Status: Granted - Kind: B2 - Application number: 18/090,786 - Filed: 2022-12-29 - Published: 2023-05-04 - Granted: 2026-10-13 - Earliest claimed: 2022-11-16 - Assignees: Intel Products IP LLC - Applicants: Intel Products IP LLC - Inventors: Francesc Guim Bernat; Christian Maciocco; Kshitij Arun Doshi; Karthik Kumar - Web page: https://patentgrep.com/patent/US12764200B2 ## CPC - H04L 67/63: Routing a service request depending on the request content or context - G06F 9/3005: {to perform operations for flow control} - G06F 9/3885: {using a plurality of independent parallel functional units} - G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues} - G06F 9/5038: {considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups)} - G06F 9/505: {considering the load} - 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 9/5083: {Techniques for rebalancing the load in a distributed system} - G06F 9/54: Interprogram communication - G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)} - G06F 12/0851: {Cache with interleaved addressing} - G06F 12/0873: Mapping of cache memory to specific storage devices or parts thereof - H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint} - H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)} - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1091: {Interfacing with client-server systems or between P2P systems} - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 41/5003: Managing SLA; Interaction between SLA and QoS - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Various approaches for monitoring and responding to orchestration or service failures with the use of infrastructure processing units (IPUs) and similar networked processing units are disclosed. A method performed by a computing device for deploying remedial actions in failure scenarios of an orchestrated edge computing environment may include: identifying an orchestration configuration of a controller entity (responsible for orchestration) and a worker entity (subject to the orchestration to provide at least one service); determining a failure scenario of the orchestration of the worker entity, such as at a networked processing unit implemented at a network interface located between the controller entity and the worker entity; and causing a remedial action to resolve the failure scenario and modify the orchestration configuration, such as replacing functionality of the controller entity or the worker entity with functionality at a replacement entity. ## Claims ### Claim 1 A method performed by a network processing unit for deploying remedial actions of failure scenarios occurring in at least one orchestrated edge computing environment, comprising: identifying an orchestration configuration of a controller entity and a worker entity, wherein both the controller entity and the worker entity include: (i) respective compute processing units to execute at least one service and (ii) respective network processing units to process network communication between the controller entity and the worker entity, and wherein the controller entity is responsible for orchestration of the worker entity to provide the at least one service; determining a failure scenario of the orchestration of the worker entity, based on network data received at the network processing unit in a network established between the controller entity and the worker entity; and causing a remedial action to resolve the failure scenario and modify the orchestration configuration, wherein the remedial action includes replacing functionality of the controller entity or the worker entity with functionality at a replacement entity, wherein the remedial action is performed by at least one of the respective network processing units of the controller entity or the worker entity. ### Claim 2 (depends on 1) The method of claim 1, wherein the failure scenario includes an event where at least one life cycle management feature of the at least one service provided by the worker entity is not responsive, and wherein the remedial action causes the at least one life cycle management feature to be performed at the replacement entity. ### Claim 3 (depends on 1) The method of claim 1, wherein the failure scenario includes an event where the at least one service provided by the worker entity is not responsive, and wherein the remedial action causes the at least one service to be migrated to the replacement entity. ### Claim 4 (depends on 3) The method of claim 3, wherein the remedial action further causes tracking of service requests associated with the failure scenario, and coordination of the tracked service requests among the worker entity and the replacement entity. ### Claim 5 (depends on 1) The method of claim 1, wherein the failure scenario includes an event where the controller entity is not responsive, and wherein the remedial action causes the replacement entity to assume control of the orchestration of the worker entity. ### Claim 6 (depends on 1) The method of claim 1, wherein the failure scenario includes an event where the controller entity is not responsive, wherein the controller entity is additionally responsible for orchestration of entities in multiple clusters, and wherein the remedial action includes providing a notification to at least one user based on the failure scenario. ### Claim 7 (depends on 1) The method of claim 1, wherein the failure scenario is determined in response to interruption of a heartbeat at the controller entity or the worker entity. ### Claim 8 (depends on 1) The method of claim 1, wherein the at least one orchestrated edge computing environment is arranged in a single site implementation, and wherein the controller entity operates as an orchestrator for a plurality of workers including the worker entity. ### Claim 9 (depends on 1) The method of claim 1, wherein the at least one orchestrated edge computing environment is arranged in a multiple site implementation, and wherein the controller entity operates as an orchestrator for multiple points of presence including the worker entity. ### Claim 10 (depends on 1) The method of claim 1, wherein the at least one orchestrated edge computing environment is arranged in a hub and spoke hierarchy, and wherein the controller entity operates as an orchestrator for multiple worker entities including the worker entity in the hierarchy. ### Claim 11 (depends on 1) The method of claim 1, wherein the worker entity provides at least one microservice using at least one container. ### Claim 12 A device, comprising: a network processing unit connected to a network of at least one orchestrated edge computing environment; and a storage medium including instructions embodied thereon, wherein the instructions, which when executed by the network processing unit, configure the network processing unit to deploy remedial actions for failure scenarios occurring in the at least one orchestrated edge computing environment, with operations to: retrieve an orchestration configuration of a controller entity and a worker entity, wherein both the controller entity and the worker entity include: (i) respective compute processing units to execute at least one service and (ii) respective network processing units to process network communication between the controller entity and the worker entity, and wherein the controller entity is responsible for orchestration of the worker entity to provide the at least one service; determine a failure scenario of the orchestration of the worker entity, based on network data received at the network processing unit, the network processing unit located in the network between the controller entity and the worker entity; and cause a remedial action to resolve the failure scenario and modify the orchestration configuration, wherein the remedial action includes replacing functionality of the controller entity or the worker entity with functionality at a replacement entity, wherein the remedial action is performed by at least one of the respective network processing units of the controller entity or the worker entity. ### Claim 13 (depends on 12) The device of claim 12, wherein the failure scenario includes an event where at least one life cycle management feature of the at least one service provided by the worker entity is not responsive, and wherein the remedial action causes the at least one life cycle management feature to be performed at the replacement entity. ### Claim 14 (depends on 12) The device of claim 12, wherein the failure scenario includes an event where the at least one service provided by the worker entity is not responsive, and wherein the remedial action causes the at least one service to be migrated to the replacement entity. ### Claim 15 (depends on 14) The device of claim 14, wherein the remedial action further causes tracking of service requests associated with the failure scenario, and coordination of the tracked service requests among the worker entity and the replacement entity. ### Claim 16 (depends on 12) The device of claim 12, wherein the failure scenario includes an event where the controller entity is not responsive, and wherein the remedial action causes the replacement entity to assume control of the orchestration of the worker entity. ### Claim 17 (depends on 12) The device of claim 12, wherein the failure scenario includes an event where the controller entity is not responsive, wherein the controller entity is additionally responsible for orchestration of entities in multiple clusters, and wherein the remedial action includes providing a notification to at least one user based on the failure scenario. ### Claim 18 (depends on 12) The device of claim 12, wherein the failure scenario is determined in response to interruption of a heartbeat at the controller entity or the worker entity. ### Claim 19 (depends on 12) The device of claim 12, wherein the at least one orchestrated edge computing environment is arranged in one of: a single site implementation where the controller entity operates as an orchestrator for a plurality of workers including the worker entity; a multiple site implementation where the controller entity operates as an orchestrator for multiple points of presence including the worker entity; or a hub and spoke hierarchy, and wherein the controller entity operates as an orchestrator for multiple worker entities including the worker entity in the hierarchy. ### Claim 20 A non-transitory machine-readable storage medium comprising information representative of instructions, wherein the instructions, when executed by a network processing unit having processing circuitry, cause the processing circuitry to: obtain data for an orchestration configuration of a controller entity and a worker entity, wherein both the controller entity and the worker entity include: (i) respective compute processing units to execute at least one service and (ii) respective network processing units to process network communication between the controller entity and the worker entity, and wherein the controller entity is responsible for orchestration of the worker entity to provide the at least one service; determine a failure scenario of the orchestration of the worker entity, based on network data received at the network processing unit in a network established between the controller entity and the worker entity; and cause a remedial action to resolve the failure scenario and modify the orchestration configuration, wherein the remedial action includes replacing functionality of the controller entity or the worker entity with functionality at a replacement entity, wherein the remedial action is performed by at least one of the respective network processing units of the controller entity or the worker entity. ### Claim 21 (depends on 20) The non-transitory machine-readable storage medium of claim 20, wherein the failure scenario includes an event where: at least one life cycle management feature of the at least one service provided by the worker entity is not responsive, and the remedial action causes the at least one life cycle management feature to be performed at the replacement entity; the at least one service provided by the worker entity is not responsive, and the remedial action causes the at least one life cycle management feature to be performed at the replacement entity; the controller entity is not responsive, and the remedial action causes the replacement entity to assume control of the orchestration of the worker entity; or the controller entity is not responsive, and wherein the remedial action includes providing a notification to at least one user based on the failure scenario. ### Claim 22 (depends on 20) The non-transitory machine-readable storage medium of claim 20, wherein the network provides an orchestrated edge computing environment that is arranged in one of: a single site implementation where the controller entity operates as an orchestrator for a plurality of workers including the worker entity; a multiple site implementation where the controller entity operates as an orchestrator for multiple points of presence including the worker entity; or a hub and spoke hierarchy where the controller entity operates as an orchestrator for multiple worker entities including the worker entity in the hierarchy.