Back to results
US 12,769,838 B2Granted
Method for modifying software in a motor vehicle
AssigneeAmpere S.A.S.
InventorsSebastien Bessiere, Arnaud Devreese, Thibaud Dravigny, Benoit Fradin
Life of this patent
Estimating the term…
Abstract
A method for modifying software in a motor vehicle includes a step of receiving software data and deployment data and steps of verifying the deployment data. If the verification steps are validated, software is modified in the motor vehicle via the software data.
Claims9
A method for bringing about a software modification in a motor vehicle, said method comprising the following steps implemented in said motor vehicle:
- receiving a first data group and a second data group, said first data group comprising software data and general software-deployment data, said general software-deployment data having been signed by a primary supervisory authority to determine a signature of the general software-deployment data, said second data group comprising specific software-deployment data, said specific software-deployment data being choices among the general software-deployment data, said specific software-deployment data having been signed by a secondary supervisory authority to determine a signature of the specific software-deployment data;
- verifying, in a first verifying step, the signature of the specific software-deployment data;
- verifying, in a second verifying step, the compatibility of the specific software-deployment data with specific characteristics of the motor vehicle;
- verifying, in a third verifying step, the signature of the general software-deployment data;
- verifying, in a fourth verifying step, the compatibility of the specific software-deployment data with the general software-deployment data;
- and
- modifying, when the first verifying step, the second verifying step, the third verifying step, and the fourth verifying step are validated, software in the motor vehicle via the software data of the first data group,
- wherein the general deployment data of the software comprise at least one of the following criteria for deployment of the software:
- a general space criterion for software deployment, a general time criterion for software deployment, and
- a general identification criterion for identifying the vehicles concerned by the software deployment,
- wherein the specific deployment data of the software comprise at least one of the following criteria:
- a specific space criterion for software deployment;
- a specific time criterion for software deployment;
- and
- a specific identification criterion for identifying the vehicles concerned by the software deployment, and
- the general space criterion for software deployment defines all possible locations in which software deployment may be carried out including locations that are not be included in the specific deployment data, and the specific space criterion is a choice among the locations,
- the general time criterion for software deployment defines all of the time ranges in which software deployment may be carried out including time ranges that are not be included in the specific deployment data, and the specific space criterion is a choice among the time ranges, and
- the general identification criterion defines all possible types of identifiers including types of identifiers that are not be included in the specific deployment data, and the specific identification criterion is a choice of a group of identifiers for the type of identifier,
- wherein the first data group comprises a digital fingerprint of the software data, said digital fingerprint having been obtained by a hash function and wherein this digital fingerprint is compared with a digital fingerprint generated in the motor vehicle from the software data with a view to implementing the modifying.
16 more elements
An automotive computer configured to be used in a motor vehicle, comprising:
- one or more processors configured to
- receive a first data group and a second data group, said first data group comprising software data and general software-deployment data, said general software-deployment data having been signed by a primary supervisory authority, said general deployment data of the software comprising at least one of the following criteria for software deployment:
- a general space criterion for software deployment,
- a general time criterion for software, and
- a general identification criterion for identifying the vehicles concerned by the software deployment,
- said second data group comprising specific software-deployment data, said specific software-deployment data being choices among the general software-deployment data, said specific software-deployment data having been signed by a secondary supervisory authority;
- verify the signature of the specific software-deployment data;
- verify the compatibility of the specific software-deployment data with specific characteristics of the motor vehicle;
- verify the signature of the general software-deployment data;
- verify the compatibility of the specific software-deployment data with the general software-deployment data;
- and
- modify software in the motor vehicle via the software data of the first data group,
- wherein the specific deployment data of the software comprise at least one of the following criteria:
- a specific space criterion for software deployment;
- a specific time criterion for software deployment;
- and
- a specific identification criterion for identifying the vehicles concerned by the software deployment, and
- the general space criterion for software deployment defines all possible locations in which software deployment may be carried out including locations that are not be included in the specific deployment data, and the specific space criterion is a choice among the locations,
- the general time criterion for software deployment defines all of the time ranges in which software deployment may be carried out including time ranges that are not included in the specific deployment data, and the specific space criterion is a choice among the time ranges, and
- the general identification criterion defines all possible types of identifiers including types of identifiers that are not be included in the specific deployment data, and the specific identification criterion is a choice of a group of identifiers for the type of identifier,
- wherein the first data group comprises a digital fingerprint of the software data, said digital fingerprint having been obtained by a hash function and wherein this digital fingerprint is compared with a digital fingerprint generated in the motor vehicle from the software data with a view to implementing the modifying.
18 more elements
A non-transitory removable storage medium configured to be used in a motor vehicle, comprising:
- means for storing a first data group and a second data group, said first data group comprising software data and general software-deployment data, said general software-deployment data having been signed by a primary supervisory authority, said general deployment data of the software comprising at least one of the following criteria for software deployment:
- a general space criterion for software deployment,
- a general time criterion for software deployment, and
- a general identification criterion for identifying the vehicles concerned by the software deployment,
- said second data group comprising specific software-deployment data, said specific software-deployment data being choices among the general software-deployment data, said specific software-deployment data having been signed by a secondary supervisory authority;
- and
- wherein a computer connected with the non-transitory removable storage medium is configured to transfer the first data group and the second data group to the motor vehicle, the signature of the specific software-deployment data being configured to be verified in said motor vehicle in a first verifying step, the specific deployment data of the software being configured to be verified in order to assess their compatibility with specific characteristics of the motor vehicle in a second verifying step, the signature of the general software-deployment data being configured to be verified in said motor vehicle in a third verifying step, the specific software-deployment data and the general software-deployment data being configured to be verified in order to assess their compatibility in a fourth verifying step, the software data of the first data group being configured to perform a software modification in the motor vehicle when the first verifying step, the second verifying step, the third verifying step, and the fourth verifying step are validated,
- wherein the specific deployment data of the software comprise at least one of the following criteria:
- a specific space criterion for software deployment;
- a specific time criterion for software deployment;
- and
- a specific identification criterion for identifying the vehicles concerned by the software deployment, and
- the general space criterion for software deployment defines all possible locations in which software deployment may be carried out including locations that are not be included in the specific deployment data, and the specific space criterion is a choice among the locations,
- the general time criterion for software deployment defines all of the time ranges in which software deployment may be carried out including time ranges that are not included in the specific deployment data, and the specific space criterion is a choice among the time ranges, and
- the general identification criterion defines all possible types of identifiers including types of identifiers that are not be included in the specific deployment data, and the specific identification criterion is a choice of a group of identifiers for the type of identifier,
- wherein the first data group comprises a digital fingerprint of the software data, said digital fingerprint having been obtained by a hash function and wherein this digital fingerprint is compared with a digital fingerprint generated in the motor vehicle from the software data with a view to implementing the modifying.
13 more elements
Dependencies are inferred from the claim text.