# US 2026/0093472 A1 · Distributed network with robust fault indication containment and software revision control method

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

- Number: US 2026/0093472 A1
- Document ID: US20260093472A1
- Status: Published application
- Kind: A1
- Application number: 18/903,431
- Filed: 2024-10-01
- Published: 2026-04-02
- Earliest claimed: 2024-10-01
- Assignees: GM Global Technology Operations LLC
- Applicants: GM Global Technology Operations LLC
- Inventors: Anthony J. Sumcad; Eric T. Hosey; Suchinder K. Govindan; David Adams; Russell A. Patenaude
- Web page: https://patentgrep.com/patent/US20260093472A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A distributed network system includes a back office server and a population of one or more host systems, e.g., vehicles. A first telematics network of the back office server includes a remote calibration tool. Each host system includes a second telematics network having an electronic control unit (ECU) operable for communicating with the back office server. The host systems also include one or more devices controlled by corresponding software code. The back office server is configured, in response to a configuration signal, to transmit an over-the-air (OTA) software update to a predetermined one or more of the host systems. The ECU is configured, in response to the OTA software update, to selectively mask or unmask a software partition of the corresponding software code to respectively disable or enable a function of the one or more devices.

## Claims

### Claim 1

A distributed network system, comprising:
a back office server having a first telematics network and a remote calibration tool; and
a population of host systems in wireless communication with the back office server, each respective host system of the population of host systems including a second telematics network, the second telematics network having:
an electronic control unit (ECU) operable for communicating remotely with the back office server; and
one or more devices controlled by corresponding software code;
wherein the back office server is configured, in response to a configuration signal, to transmit an over-the-air (OTA) software update to the ECU of a predetermined one or more of the host systems, and wherein the ECU is configured, in response to the OTA software update, to selectively mask or unmask a software partition of the corresponding software code to respectively disable or enable a function of the one or more devices.

### Claim 2 (depends on 1)

The distributed network system of claim 1, wherein the ECU is configured, in response to the OTA software update, to temporarily disable a diagnostic trouble code (DTC) associated with the function of the one or more devices.

### Claim 3 (depends on 1)

The distributed network system of claim 1, wherein the ECU is configured to determine a confidence score indicative of a likelihood of the OTA software update having corrected a fault in the corresponding software code, and to unmask the software partition when the confidence score exceeds a confidence threshold.

### Claim 4 (depends on 1)

The distributed network system of claim 1, wherein the ECU is configured to compare a flag in the OTA software update to a flag in the software partition to determine whether the OTA update is directed to correcting a fault in the software partition, and to unmask the software partition when the flag in the OTA software update matches the flag in the software partition.

### Claim 5 (depends on 1)

The distributed network system of claim 1, wherein the ECU is configured to selectively upload a set of host system updates to the back office, the set of host system updates including an updated status of the software partition.

### Claim 6 (depends on 1)

The distributed network system of claim 1, wherein the back office server includes a graphical use interface (GUI) as part of the first telematics network, and wherein the remote calibration tool is accessible to a user of the back office server via the GUI.

### Claim 7 (depends on 1)

The distributed network system of claim 1, wherein ECU is configured, in response to the OTA software update including an updated software version, to selectively unmask the software partition of the corresponding software code to enable the function of the one or more devices.

### Claim 8 (depends on 1)

The distributed network system of claim 1, wherein the ECU of each respective host system is identically configured, and wherein the back office is configured to transmit the OTA software update to a subset of the host systems in the population of host systems based on the configuration signal.

### Claim 9

A method for use with a distributed network system, the method comprising:
in response to a configuration signal, transmitting an over-the-air (OTA) software update to one or more of host systems via a first telematics network of a back office server; and
selectively disabling or enabling a function of a device of a host system in response to receipt of the OTA software update by the host system, including selectively masking or unmasking a software partition of a corresponding software code via an electronic control unit (ECU) of a second telematics network of the host system, the second telematics network being in wireless communication with the first telematics network of the back office server.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
temporarily disabling a diagnostic trouble code (DTC) associated with the function of the one or more devices, via the ECU, in response to the OTA software update.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
determining a confidence score, via the ECU, that is indicative of a likelihood of the OTA software update having corrected a fault in the corresponding software code; and
unmasking the software partition when the confidence score exceeds a confidence threshold.

### Claim 12 (depends on 9)

The method of claim 9, further comprising:
comparing, via the ECU, a flag in the OTA software update to a flag in the software partition to determine whether the OTA update is directed to correcting a fault in the software partition; and
unmasking the software partition when the flag in the OTA software update matches the flag in the software partition.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
selectively uploading a set of host system updates to the back office server via the ECU, the set of host system updates including an updated status of the software partition.

### Claim 14 (depends on 9)

The method of claim 9, further comprising:
using a graphical use interface (GUI) of the back office server to access the first telematics network.

### Claim 15 (depends on 9)

The method of claim 9, further comprising:
in response to the OTA software update including an updated software version, using the ECU to selectively unmask the software partition of the corresponding software code to enable the function of the one or more devices.

### Claim 16 (depends on 9)

The method of claim 9, further comprising:
transmitting the OTA software update from the back office server to a subset of a population of host systems based on the configuration signal.

### Claim 17

A vehicle in communication with a back office server in a distributed network, the vehicle comprising:
an electronic control unit (ECU) operable for communicating with the back office server via a telematics system of the vehicle; and
one or more vehicle devices controlled by corresponding software code, wherein the ECU is configured to:
receive an over-the-air (OTA) software update from the back office server via the telematics system; and
in response to the OTA software update from the back office server, selectively mask or unmask a software partition of the corresponding software code to respectively disable or enable a function of the one or more vehicle devices, including temporarily disabling or enabling a diagnostic trouble code (DTC) associated with the function of the one or more vehicle devices.

### Claim 18 (depends on 17)

The vehicle of claim 17, wherein the ECU is configured to:
determine a confidence score indicative of a likelihood of the OTA software update having corrected a fault in the corresponding software code; and
unmask the software partition when the confidence score exceeds a confidence threshold.

### Claim 19 (depends on 17)

The vehicle of claim 17, wherein the ECU is configured to:
compare a flag in the OTA software update to a flag in the software partition to determine whether the OTA update is directed to correcting a fault in the software partition; and
unmask the software partition when the flag in the OTA software update matches the flag in the software partition.

### Claim 20 (depends on 17)

The vehicle of claim 17, wherein the ECU is configured to:
selectively upload a set of host system updates to the back office server, the set of host system updates including an updated status of the software partition.
