Back to results
US 10,884,902 B2Granted
Software version verification for autonomous vehicles
AssigneeUatc, LLC
InventorsDima Kislovskiy, David McAllister Bradley
Life of this patent
Estimating the term…
Abstract
An autonomous vehicle software management system can distribute AV software versions to safety-driven autonomous vehicles (SDAVs) operating within a given region. The system can receive log data from the SDAVs indicating any trip anomalies of the SDAVs while executing the AV software version. When a predetermined safety standard has been met based on the log data, the system can verify the AV software version for execution on fully autonomous vehicles (FAVs) operating within the given region.
Claims18
An autonomous vehicle (AV) software management system comprising:
- a network communication interface connected, over one or more networks, with a plurality of AVs operating throughout a given region;
- one or more processors;
- and
- one or more memory resources storing instructions that, when executed by the one or more processors, cause the AV software management system to:
- distribute, over the one or more networks, an unverified AV software version to safety-driven autonomous vehicles (SDAVs) operating within the given region, each of the SDAVs including a human safety driver that takes over control of the SDAV when the SDAV, executing the unverified AV software version, requires correction;
- receive, over the one or more networks, log data from the SDAVs, the log data indicating trip anomalies of the SDAVs while executing the unverified AV software version;
- when a predetermined safety standard has been met based on the log data, verify the unverified AV software version for execution on fully autonomous vehicles (FAVs) operating within the given region, wherein each of the FAVs is a self-driving vehicle that does not include a human safety driver, and wherein the predetermined safety standard corresponds to a threshold confidence level that the unverified AV software version is safer than an average human driver over a defined set of conditions;
- and
- distribute, over the one or more networks, the verified AV software version to a plurality of FAVs operating within the given region for execution,
- wherein the log data comprises live sensor data, telemetry data, diagnostic data and correlation data indicating which the software versions were in use during operation.
7 more elements
A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
- distribute, over one or more networks, an unverified AV software version to safety-driven autonomous vehicles (SDAVs) operating within a given region, each of the SDAVs including a human safety driver that takes over control of the SDAV when the SDAV, executing the unverified AV software version, requires correction;
- receive, over the one or more networks, log data from the SDAVs, the log data indicating any trip anomalies of the SDAVs while executing the unverified AV software version;
- when a predetermined safety standard has been met based on the log data, verify the unverified AV software version for execution on fully autonomous vehicles (FAVs) operating within the given region, wherein each of the FAVs is a self-driving vehicle that does not include a human safety driver, and wherein the predetermined safety standard corresponds to a threshold confidence level that the unverified AV software version is safer than an average human driver over a defined set of conditions;
- distribute, over the one or more networks, the verified AV software version to a plurality of FAVs operating within the given region for execution,
- wherein the log data comprises live sensor data, telemetry data, diagnostic data and correlation data indicating which the software versions were in use during operation.
2 more elements
A computer-implemented method of verifying software versions for autonomous vehicles (AVs), the method being performed by one or more processors and comprising:
- distributing, over one or more networks, an unverified AV software version to safety-driven autonomous vehicles (SDAVs) operating within a given region, each of the SDAVs including a human safety driver that takes over control of the SDAV when the SDAV, executing the unverified AV software version, requires correction;
- receiving, over the one or more networks, log data from the SDAVs, the log data indicating any trip anomalies of the SDAVs while executing the unverified AV software version;
- when a predetermined safety standard has been met based on the log data, verifying the unverified AV software version for execution on fully autonomous vehicles (FAVs) operating within the given region, wherein each of the FAVs is a self-driving vehicle that does not include a human safety driver, and wherein the predetermined safety standard corresponds to a threshold confidence level that the unverified AV software version is safer than an average human driver over a defined set of conditions;
- and
- distributing, over the one or more networks, the verified AV software version to a plurality of FAVs operating within the given region for execution,
- wherein the log data comprises live sensor data, telemetry data, diagnostic data and correlation data indicating which the software versions were in use during operation.
3 more elements
Dependencies are inferred from the claim text.