# US 12,001,306 B2 · Cross-jurisdictional microservice-based cloud platform deployment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,001,306 B2 - Document ID: US12001306B2 - Status: Granted - Kind: B2 - Application number: 16/855,153 - Filed: 2020-04-22 - Published: 2020-10-29 - Granted: 2024-06-04 - Earliest claimed: 2019-04-23 - Assignees: Avanade Holdings LLC - Applicants: Avanade Holdings LLC - Inventors: Gnana Geetha Gandhi - Web page: https://patentgrep.com/patent/US12001306B2 ## CPC - G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)} - G06F 8/60: Software deployment - G06F 9/5072: {Grid computing} - G06F 9/546: {Message passing systems or structures, e.g. queues} - H04L 63/0209: {Architectural arrangements, e.g. perimeter networks or demilitarized zones} - H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals} - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - G06F 11/008: {Reliability or availability analysis} - G06F 11/302: {where the computing system component is a software system} - G06F 11/3419: {by assessing time} - G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)} - G06F 2201/815: Virtual - 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 An orchestrator device may receive a request from a first module deployed in a second cloud platform in a second jurisdiction, wherein the request is compliant with a jurisdictional characteristic of the second jurisdiction. The orchestrator device may process the request in order to identify a second module deployed in the first cloud platform to which to forward the request. The orchestrator device may forward the request to the second module to enable fulfillment of the request. The orchestrator device may receive a response from the second module, wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction. The orchestrator device may process the response, to identify a third module deployed in the second cloud platform to which to forward the response. The orchestrator device may forward the response, to the third module. ## Claims ### Claim 1 A method, comprising: receiving, by an orchestrator device in a first cloud platform in a first jurisdiction, a request from a first module deployed in a second cloud platform in a second jurisdiction, wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction, wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and wherein the request, received by the orchestrator device, includes the first portion and does not include the second portion; processing, by the orchestrator device, the request in order to identify a second module deployed in the first cloud platform to which to forward the request; receiving, by the orchestrator device, a token confirming receipt of the second portion within the second cloud platform; forwarding, by the orchestrator device and to the second module, the token to indicate that the request is to be fulfilled without the orchestrator device receiving the second portion; forwarding, by the orchestrator device, the request to the second module to enable fulfillment of the request; receiving, by the orchestrator device, a response from the second module, wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction; identifying, by the orchestrator device and based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and forwarding, by the orchestrator device, the response, to the third module. ### Claim 2 (depends on 1) The method of claim 1, wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall. ### Claim 3 (depends on 1) The method of claim 1, wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement. ### Claim 4 (depends on 1) The method of claim 1, wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction. ### Claim 5 (depends on 1) The method of claim 1, further comprising: receiving, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and controlling the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction. ### Claim 6 (depends on 1) The method of claim 1, further comprising: monitoring, by the orchestrator device, one or more microservices of at least one of the first cloud platform or the second cloud platform. ### Claim 7 (depends on 1) The method of claim 1, further comprising: confirming receipt of the second portion within the second cloud platform; and providing data indicating that the request is to be fulfilled without the orchestrator device receiving the second portion. ### Claim 8 A device, comprising: one or more processors to: receive a request from a first module deployed in a second cloud platform in a second jurisdiction, wherein the device is associated with a first cloud platform in a first jurisdiction, wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction, wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and wherein the request, received by the device, includes the first portion and does not include the second portion; process the request in order to identify a second module deployed in the first cloud platform to which to forward the request; receive a token confirming receipt of the second portion within the second cloud platform; forward, to the second module, the token to indicate that the request is to be fulfilled without the device receiving the second portion; forward the request to the second module to enable fulfillment of the request; receive a response from the second module, wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction; identify, based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and forward the response to the third module. ### Claim 9 (depends on 8) The device of claim 8, wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall. ### Claim 10 (depends on 8) The device of claim 8, wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement. ### Claim 11 (depends on 8) The device of claim 8, wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction. ### Claim 12 (depends on 8) The device of claim 8, wherein the one or more processors are further to: receive, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and control the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction. ### Claim 13 (depends on 8) The device of claim 8, wherein the one or more processors are further to: monitor one or more microservices of at least one of the first cloud platform or the second cloud platform. ### Claim 14 (depends on 8) The device of claim 8, wherein the one or more processors are further to: confirm receipt of the second portion within the second cloud platform; and provide data indicating that the request is to be fulfilled without the device receiving the second portion. ### Claim 15 A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to: receive a request from a first module deployed in a second cloud platform in a second jurisdiction, wherein the device is associated with a first cloud platform in a first jurisdiction, wherein the first jurisdiction and the second jurisdiction are associated with different jurisdictional characteristics related to restrictions of data transmission external to the first jurisdiction and the second jurisdiction, wherein information associated with fulfillment of the request includes at least a first portion that is compliant with a jurisdictional characteristic of the second jurisdiction, and a second portion that is not compliant with the jurisdictional characteristic of the second jurisdiction, and wherein the request, received by the device, includes the first portion and does not include the second portion; process the request in order to identify a second module deployed in the first cloud platform to which to forward the request; receive a token confirming receipt of the second portion within the second cloud platform; forward, to the second module, the token to indicate that the request is to be fulfilled without the device receiving the second portion; forward the request to the second module to enable fulfillment of the request; receive a response from the second module, wherein the response is compliant with a jurisdictional characteristic of the first jurisdiction; identify, based on processing the response, a third module deployed in the second cloud platform to which to forward the response; and forward the response to the third module. ### Claim 16 (depends on 15) The device of claim 15, wherein the first cloud platform and the second cloud platform are separated by a jurisdictional firewall. ### Claim 17 (depends on 15) The device of claim 15, wherein at least one of the jurisdictional characteristic of the first jurisdiction or the jurisdictional characteristic of the second jurisdiction is an information privacy requirement. ### Claim 18 (depends on 15) The device of claim 15, wherein the first cloud platform is co-located in the first jurisdiction with a first interface to one or more systems in the first jurisdiction, and the second cloud platform is co-located in the second jurisdiction with a second interface to one or more systems in the second jurisdiction. ### Claim 19 (depends on 15) The device of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: receive, via an interface in the first jurisdiction, one or more commands relating to one or more development operations tools; and control the second cloud platform in the second jurisdiction based at least in part on receiving the one or more commands relating to the one or more development operations tools via the interface in the first jurisdiction. ### Claim 20 (depends on 15) The device of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: monitor one or more microservices of at least one of the first cloud platform or the second cloud platform.