# US 2025/0085958 A1 · Iterative prioritized background data transfer for vehicle over-the-air updates

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

- Number: US 2025/0085958 A1
- Document ID: US20250085958A1
- Status: Published application
- Kind: A1
- Application number: 18/466,480
- Filed: 2023-09-13
- Published: 2025-03-13
- Earliest claimed: 2023-09-13
- Assignees: Ford Global Technologies, LLC
- Applicants: Ford Global Technologies, LLC
- Inventors: Oliver Lei; Yun Ho Lee; Jayanthi Rao
- Web page: https://patentgrep.com/patent/US20250085958A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- 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 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- 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

In a first iteration, an OTA update is initiated as a background data transfer over a communications network to a plurality of vehicles. Delivery statuses for the OTA update are received from the plurality of vehicles. A vehicle list is updated to remove the vehicles with a completed OTA update based on the delivery statuses and to set a low priority to the vehicles having poor RF status. In a subsequent iteration, a first background data transfer is initiated to send the OTA update to the vehicles on the vehicle list having high priority and then a second background data transfer is initiated to send the OTA update to the vehicles on the vehicle list having the low priority. The receiving, updating, and subsequent iteration operations are repeated until all of the vehicles have received the OTA update.

## Claims

### Claim 1

A system for iterative prioritized background data transfer for vehicle over-the-air (OTA) updates, comprising:
a cloud server, configured to send an OTA update over a communications network to a plurality of vehicles on a vehicle list by performing operations including to:
in a first iteration, initiate a background data transfer to send the OTA update over the communications network to the plurality of vehicles;
receive delivery statuses for the OTA update from the plurality of vehicles, the delivery statuses indicating radio frequency (RF) status of the plurality of vehicles over the communications network, whether the OTA update is complete, and whether the vehicles are on or off;
update the vehicle list to remove the vehicles with a completed OTA update based on the delivery statuses and to set a low priority to the vehicles having poor RF status;
in a subsequent iteration, initiate a first background data transfer to send the OTA update to the vehicles on the vehicle list having high priority and then initiate a second background data transfer to send the OTA update to the vehicles on the vehicle list having the low priority; and
repeat the receive, update, and subsequent iteration operations until all of the vehicles have received the OTA update.

### Claim 2 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to:
receive a condition change message from one of the vehicles, the condition change message indicating that, since the one of the vehicles has sent the delivery status to the cloud server, one or more of that the one of the vehicles has moved its location or that the RF status of the one of the vehicles has changed; and
update the vehicle list to set the one of the vehicles to the high priority.

### Claim 3 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to:
receive network load information from the communications network; and
initiate the operations to send the OTA update responsive to the network load information indicating that the communications network has network load below a predefined threshold, and otherwise perform a wait operation,
wherein the cloud server iteratively performs the receive, initiate and wait operations until the OTA update is initiated.

### Claim 4 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to:
receive network load information from the communications network; and
initiate the subsequent iteration responsive operations, responsive to the network load information indicating that the communications network has network load below a predefined threshold, and otherwise perform a wait operation before reattempting to receive the network load information and initiate the subsequent iteration.

### Claim 5 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to:
responsive to a quantity of vehicles on the vehicle list being below a minimum threshold, send the OTA update to all the vehicles on the vehicle list, regardless of network load.

### Claim 6 (depends on 5)

The system of claim 5, wherein to send the OTA update to all the vehicles on the vehicle list, regardless of network load, includes to send the OTA update to the vehicles in random order.

### Claim 7 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to abandon the send of the OTA update responsive to expiration of a predefined time period for sending the OTA update.

### Claim 8 (depends on 1)

The system of claim 1, wherein the cloud server is further configured to:
receive vehicle location information; and
generate the vehicle list to include those vehicles within a region defined by a region definition stored to the cloud server, the region definition indicating one or more cells of the communications network in which the vehicles are located for receiving the OTA update.

### Claim 9 (depends on 8)

The system of claim 8, wherein the cloud server is further configured to initiate the send of the OTA update responsive to a quantity of vehicles identified for the vehicle list reaching at least a predefining quantity of vehicles.

### Claim 10 (depends on 8)

The system of claim 8, wherein the cloud server is further configured to:
identify a location within the region definition having historically successful OTA transfers of the OTA update; and
indicate the location to the vehicles as a suggested location for receiving the OTA update.

### Claim 11 (depends on 10)

The system of claim 10, wherein the cloud server is further configured to receive a delivery status report from one of the vehicles, responsive to the one vehicle moving to the location, to indicate that the vehicle is in position to receive the OTA update.

### Claim 12

A method for iterative prioritized background data transfer for vehicle over-the-air (OTA) updates, comprising:
in a first iteration, initiating a background data transfer to send an OTA update over a communications network to a plurality of vehicles;
receiving delivery statuses for the OTA update from the plurality of vehicles, the delivery statuses indicating radio frequency (RF) status of the plurality of vehicles over the communications network, whether the OTA update is complete, and whether the vehicles are on or off;
updating a vehicle list to remove the vehicles with a completed OTA update based on the delivery statuses and to set a low priority to the vehicles having poor RF status;
in a subsequent iteration, initiating a first background data transfer to send the OTA update to the vehicles on the vehicle list having high priority and then initiate a second background data transfer to send the OTA update to the vehicles on the vehicle list having the low priority; and
repeating the receiving, updating, and subsequent iteration operations until all of the vehicles have received the OTA update.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
receiving a condition change message from one of the vehicles, the condition change message indicating that, since the one of the vehicles has sent the delivery status to the cloud server, one or more of that the one of the vehicles has moved its location or that the RF status of the one of the vehicles has changed; and
updating the vehicle list to set the one of the vehicles to the high priority.

### Claim 14 (depends on 12)

The method of claim 12, further comprising:
receiving network load information from the communications network;
initiating the operations to send the OTA update responsive to the network load information indicating that the communications network has network load below a predefined threshold, and otherwise perform a wait operation; and
iteratively performing the receiving, initiating and waiting operations until the OTA update is initiated.

### Claim 15 (depends on 12)

The method of claim 12, further comprising:
receiving network load information from the communications network; and
initiating the subsequent iteration responsive operations, responsive to the network load information indicating that the communications network has network load below a predefined threshold, and otherwise perform a wait operation before reattempting to receive the network load information and initiate the subsequent iteration.

### Claim 16 (depends on 12)

The method of claim 12, further comprising responsive to a quantity of vehicles on the vehicle list being below a minimum threshold, sending the OTA update to all the vehicles on the vehicle list, regardless of network load.

### Claim 17 (depends on 16)

The method of claim 16, wherein sending the OTA update to all the vehicles on the vehicle list, regardless of network load, includes sending the OTA update to the vehicles in random order.

### Claim 18 (depends on 12)

The method of claim 12, further comprising abandoning the send of the OTA update responsive to expiration of a predefined time period for sending the OTA update.

### Claim 19 (depends on 12)

The method of claim 12, further comprising:
receiving vehicle location information; and
generating the vehicle list to include the vehicles within a region defined by a region definition, the region definition indicating one or more cells of the communications network in which the vehicles are located for receiving the OTA update.

### Claim 20 (depends on 19)

The method of claim 19, further comprising initiating the send of the OTA update responsive to a quantity of vehicles identified for the vehicle list reaching at least a predefining quantity of vehicles.

### Claim 21 (depends on 19)

The method of claim 19, further comprising:
identifying a location within the region definition having historically successful OTA transfers of the OTA update; and
indicating the location to the vehicles as a suggested location for receiving the OTA update.

### Claim 22 (depends on 21)

The method of claim 21, further comprising receiving a delivery status report from one of the vehicles, responsive to the one vehicle moving to the location, to indicate that the vehicle is in position to receive the OTA update.

### Claim 23

A non-transitory computer-readable medium comprising instructions for vehicle over-the-air (OTA) updates that, when executed by a cloud server, cause the cloud server to perform operations including to:
in a first iteration, initiate a background data transfer to send an OTA update over a communications network to a plurality of vehicles;
receive delivery statuses for the OTA update from the plurality of vehicles, the delivery statuses indicating radio frequency (RF) status of the plurality of vehicles over the communications network, whether the OTA update is complete, and whether the vehicles are on or off;
updating a vehicle list to remove the vehicles with a completed OTA update based on the delivery statuses and to set a low priority to the vehicles having poor RF status;
in a subsequent iteration, initiate a first background data transfer to send the OTA update to the vehicles on the vehicle list having high priority and then initiate a second background data transfer to send the OTA update to the vehicles on the vehicle list having the low priority; and
repeat the receive, update, and subsequent iteration operations until all of the vehicles have received the OTA update.
