# US 12,224,897 B2 · Active network node resilience pattern for cloud service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,224,897 B2 - Document ID: US12224897B2 - Status: Granted - Kind: B2 - Application number: 17/986,213 - Filed: 2022-11-14 - Published: 2024-05-16 - Granted: 2025-02-11 - Earliest claimed: 2022-11-14 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Aby Jose; Sowmya Lakshmi R - Web page: https://patentgrep.com/patent/US12224897B2 ## CPC - H04L 41/0663: Performing the actions predefined by failover planning, e.g. switching to standby network elements - H04L 41/0668: by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 41/20: {Network management software packages} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system associated with a distributed cloud service may include an active network node within a network environment between a provider application and a consumer application. The active network node may have an execution environment, an operating system to support the execution environment, and active hardware. The active network node may automatically detect, via a platform and language independent centralized resilience process, a failure event in an active network that routes packets to support the distributed cloud service. The failure event might be associated with, for example, an unreliable network, a low bandwidth, a high latency, a topology change, transport costs, etc. Responsive to the detection of the failure event, the active network node may dynamically implement an application resilience pattern (e.g., a circuit breaker or bounded queue) by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application. ## Claims ### Claim 1 A system associated with a distributed cloud service, comprising: an active network node within a network environment, between a provider application and a consumer application, the active network node having an execution environment, an operating system to support the execution environment, and active hardware, including: a computer processor, and a computer memory storage device, coupled to the computer processor, that contains instructions that when executed by the computer processor enable the active network node to: (i) automatically detect, via a platform and language independent centralized resilience process of the active network node, a failure event in an active network that routes packets to support the distributed cloud service, and (ii) responsive to the detection of the failure event, dynamically implement an application resilience pattern by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application. ### Claim 2 (depends on 1) The system of claim 1, wherein the active hardware comprises network processors. ### Claim 3 (depends on 1) The system of claim 1, wherein the failure event is associated with at least one of: (i) an unreliable network, (ii) a low bandwidth, (iii) a high latency, (iv) a topology change, and (v) transport costs. ### Claim 4 (depends on 1) The system of claim 1, wherein the active network node is associated with at least one of: (i) a target service, and (ii) an external service. ### Claim 5 (depends on 1) The system of claim 1, wherein the active network node is associated with at least one of: (i) a web dispatcher, (ii) a load balancer, (iii) a database, (iv) an application server, (v) an Application Programming Interface (“API”) gateway and (vi) a component that receives and processes input from multiple sources. ### Claim 6 (depends on 1) The system of claim 1, wherein the application resilience pattern comprises a circuit breaker. ### Claim 7 (depends on 1) The system of claim 1, wherein the application resilience pattern comprises a bounded queue. ### Claim 8 (depends on 1) The system of claim 1, wherein the application resilience pattern is associated with a discrete approach where programs are injected into the active network node separately from passive data. ### Claim 9 (depends on 1) The system of claim 1, wherein the application resilience pattern is associated with an integrated approach where programs are integrated into smart packets along with passive data. ### Claim 10 (depends on 9) The system of claim 9, wherein a smart packet includes an Internet Protocol (“IP”) header and an Active Network Encapsulation Protocol (“ANEP”) header along with a payload. ### Claim 11 (depends on 1) The system of claim 1, wherein the application resilience pattern is associated with at least one of: (i) loose coupling, (ii) isolation, (iii) latency control, and (iv) supervision. ### Claim 12 A computer-implemented method associated with a distributed cloud service, comprising: automatically detecting, via a platform and language independent centralized resilience process at a computer processor of an active network node within a network environment, between a provider application and a consumer application, a failure event in an active network that routes packets to support the distributed cloud service, the active network node having an execution environment, an operating system to support the execution environment, and active hardware; and responsive to the detection of the failure event, dynamically implementing an application resilience pattern by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application. ### Claim 13 (depends on 12) The method of claim 12, wherein the active hardware comprises network processors. ### Claim 14 (depends on 12) The method of claim 12, wherein the failure event is associated with at least one of: (i) an unreliable network, (ii) a low bandwidth, (iii) a high latency, (iv) a topology change, and (v) transport costs. ### Claim 15 (depends on 12) The method of claim 12, wherein the active network node is associated with at least one of: (i) a target service, (ii) an external service, (iii) a web dispatcher, (iv) a load balancer, (v) a database, (xi) an application server, (vii) an Application Programming Interface (“API”) gateway and (viii) a component that receives and processes input from multiple sources. ### Claim 16 (depends on 12) The method of claim 12, wherein the application resilience pattern comprises a circuit breaker. ### Claim 17 (depends on 12) The method of claim 12, wherein the application resilience pattern comprises a bounded queue. ### Claim 18 A non-transitory, computer readable medium having executable instructions stored therein to implement a method associated with a distributed cloud service, the method comprising: automatically detecting, via a platform and language independent centralized resilience process at a computer processor of an active network node within a network environment, between a provider application and a consumer application, a failure event in an active network that routes packets to support the distributed cloud service, the active network node having an execution environment, an operating system to support the execution environment, and active hardware; and responsive to the detection of the failure event, dynamically implementing an application resilience pattern by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application. ### Claim 19 (depends on 18) The medium of claim 18, wherein the application resilience pattern is associated with a discrete approach where programs are injected into the active network node separately from passive data. ### Claim 20 (depends on 18) The medium of claim 18, wherein the application resilience pattern is associated with an integrated approach where programs are integrated into smart packets along with passive data. ### Claim 21 (depends on 20) The medium of claim 20, wherein a smart packet includes an Internet Protocol (“IP”) header and an Active Network Encapsulation Protocol (“ANEP”) header along with a payload.