# US 2025/0147748 A1 · Automated Detection and Propagation of Multi-System Launches

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0147748 A1
- Document ID: US20250147748A1
- Status: Published application
- Kind: A1
- Application number: 18/501,634
- Filed: 2023-11-03
- Published: 2025-05-08
- Earliest claimed: 2023-11-03
- Assignees: Uber Technologies, Inc.
- Applicants: Uber Technologies, Inc.
- Inventors: Arunagiriswaran Ezhilan; Srinivasan Hariram; Amrut Bharat Joshi; Jeff Moore; Jayaram Valliyur
- Web page: https://patentgrep.com/patent/US20250147748A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/60: Software deployment
- G06F 9/3838: {Dependency mechanisms, e.g. register scoreboarding}
- G06F 9/4843: {by program, e.g. task dispatcher, supervisor, operating system}
- G06F 9/4856: {resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence)}
- G06F 9/5072: {Grid computing}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 11/26: Functional testing
- G06F 11/3668: Testing of software
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 2209/549: Remote execution
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for detecting and orchestrating the deployment of software changes. The system can access schema data indicative of a change associated with a first system, wherein executable code associated with the change is executable within a first computing environment. The system can determine a potential impact to a second system. The system can generate one or more computing tasks to notify the second system of the change and an acknowledgment placeholder with a unique identifier associated with the second system. The system can access data indicative of an execution status of the one or more computing tasks. The system can generate an update indicating that the one or more computing tasks have been executed by the second system. The system can transmit to the first system, data acknowledging the potential impact to the second system, and command instructions to deploy the executable code to a second computing environment.

## Claims

### Claim 1

A computer-implemented method comprising:
accessing schema data indicative of a change associated with a first system within a multi-system computing architecture, wherein executable code associated with the change is executable within a first computing environment;
determining, based on the schema data, a potential impact to a second system within the multi-system computing architecture, the potential impact arising from the change associated with the first system;
based on the potential impact to the second system, generating (i) one or more computing tasks to notify the second system of the change and (ii) an acknowledgment placeholder with a unique identifier associated the second system, the acknowledgement placeholder being stored within a data structure in association with the unique identifier;
accessing, over a communication channel associated with the second system, data indicative of an execution status of the one or more computing tasks, wherein the data indicative of the execution status is associated with the unique identifier;
generating, based on the execution status and the unique identifier, an update to the data structure storing the acknowledgement placeholder, the update indicating that the one or more computing tasks have been executed by the second system; and
in response to the one or more computing tasks being executed by the second system, transmitting:
(iii) to the first system, data acknowledging the potential impact to the second system arising from the change associated with the first system, and
(iv) one or more command instructions to deploy the executable code associated with the change from the first computing environment to a second computing environment.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the first computing environment is associated with a test environment and the second computing environment is associated with a production environment.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein outputting, one or more command instructions comprises:
generating a request executable by a remote computing system, the request indicative of the change to be deployed in the second computing environment; and
transmitting, the request to the remote computing system.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein determining a potential impact to the second system comprise:
accessing value data associated with one or more fields of a schema; and
determining, based on the value data, one or more dependencies between the first system and the second system.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, further comprising storing the one or more dependencies in a storage system.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, wherein the one or more dependencies comprise at least one of direct dependencies or indirect dependencies.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the change associated with the first system comprises at least one of:
(i) a service addition or service removal,
(ii) an RPC (remote procedure call) addition or removal,
(iii) a schema field addition or removal, or
(iv) a field value addition or removal.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising outputting the one or more computing tasks to the second system.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein the change comprises one or more interface changes associated with the first system.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the one or more computing tasks comprise one or more test scripts executable by the second system.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10, further comprising:
receiving one or more executed test scripts from the second system, wherein:
the one or more executed test scripts are associated with the one or more computing tasks, and
the one or more executed test scripts are indicative of test results associated with the potential impact of the change to the second system.

### Claim 12 (depends on 10)

The computer-implemented method of claim 10, further comprising:
updating, based on the one or more executed test scripts, the execution status of the one or more computing tasks.

### Claim 13 (depends on 1)

The computer-implemented method of claim 1, comprising:
determining, based on the schema data, a potential impact to a third system within the multi-system computing architecture;
based on the potential impact to the third system, generating one or more computing tasks to notify the third system of the change and an acknowledgement placeholder with a unique identifier associated with the third system, the acknowledgement placeholder being stored within a data structure in association with the unique identifier;
accessing, over a communication channel associated with the third system, data indicative of an execution status of the one or more computing tasks associated with the third system, wherein the data indicative of the execution status is associated with the unique identifier associated with the third system; and
generating, based on the execution status and the unique identifier, an update to the data structure storing the acknowledgement placeholder, the update indicating that the one or more computing tasks have been executed by the third system.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, further comprising in response to the one or more computing tasks being executed by the third system, outputting data acknowledging the potential impact to the third system arising from the change associated with the first system.

### Claim 15

A computing system comprising:
one or more processors; and
one or more memory resources storing instructions executable by the one or more processors to cause the one or more processors to perform operations, the operations comprising:
accessing schema data indicative of a change associated with a first system within a multi-system computing architecture, wherein executable code associated with the change is executable within a first computing environment;
determining, based on the schema data, a potential impact to a second system within the multi-system computing architecture, the potential impact arising from the change associated with the first system;
based on the potential impact to the second system, generating (i) one or more computing tasks to notify the second system of the change and (ii) an acknowledgment placeholder with a unique identifier associated the second system, the acknowledgement placeholder being stored within a data structure in association with the unique identifier;
accessing, over a communication channel associated with the second system, data indicative of an execution status of the one or more computing tasks, wherein the data indicative of the execution status is associated with the unique identifier;
generating, based on the execution status and the unique identifier, an update to the data structure storing the acknowledgement placeholder, the update indicating that the one or more computing tasks have been executed by the second system; and
in response to the one or more computing tasks being executed by the second system, transmitting:
(iii) to the first system, data acknowledging the potential impact to the second system arising from the change associated with the first system, and
(iv) one or more command instructions to deploy the executable code associated with the change from the first computing environment to a second computing environment.

### Claim 16 (depends on 15)

The computing system of claim 15, wherein the first computing environment is associated with a test environment and the second computing environment is associated with a production environment.

### Claim 17 (depends on 15)

The computing system of claim 15, wherein outputting, one or more command instructions comprises:
generating a request executable by a remote computing system, the request indicative of the change to be deployed in the second computing environment; and
transmitting, the request to the remote computing system.

### Claim 18 (depends on 15)

The computing system of claim 15, wherein determining a potential impact to the second system comprise:
accessing value data associated with one or more fields of a schema; and
determining, based on the value data, one or more dependencies between the first system and the second system.

### Claim 19 (depends on 18)

The computing system of claim 18, wherein the operations further comprise storing the one or more dependencies in a storage system.

### Claim 20

A non-transitory computer-readable media storing instructions that are executable by one or more processors to cause the one or more processors to perform operations, the operations comprising:
accessing schema data indicative of a change associated with a first system within a multi-system computing architecture, wherein executable code associated with the change is executable within a first computing environment;
determining, based on the schema data, a potential impact to a second system within the multi-system computing architecture, the potential impact arising from the change associated with the first system;
based on the potential impact to the second system, generating (i) one or more computing tasks to notify the second system of the change and (ii) an acknowledgment placeholder with a unique identifier associated the second system, the acknowledgement placeholder being stored within a data structure in association with the unique identifier;
accessing, over a communication channel associated with the second system, data indicative of an execution status of the one or more computing tasks, wherein the data indicative of the execution status is associated with the unique identifier;
generating, based on the execution status and the unique identifier, an update to the data structure storing the acknowledgement placeholder, the update indicating that the one or more computing tasks have been executed by the second system; and
in response to the one or more computing tasks being executed by the second system, transmitting:
(iii) to the first system, data acknowledging the potential impact to the second system arising from the change associated with the first system, and
(iv) one or more command instructions to deploy the executable code associated with the change from the first computing environment to a second computing environment.
