SNIP_ADAPTIVE_CAN_FIGURE_Figure_13_4_PLATFORMDESIGN

Figure 13.4: Overview Vehicle Package Y ou can find below for information purpose a description of the fields that should be contained in Vehicle Package Manifest: • Repository: uri, repository or diagnostic address, for history , tracking and security purposes • Minimum supported V-UCM version: to make sure that the Vehicle Package can be parsed properly by the V-UCM. • For update campaign orchestration: – UCM identifier: unique identifier within vehicle architecture, to allow V-UCM identifying UCM subordinates in the vehicle – Associations of Software Packages to describe the sequence of transfer, processing, and activation – Vehicle driver notification: to interact with vehicle driver, asking for his consent or notifying him at several steps of the vehicle update of the optional safety measures to be taken during update. The Vehicle Package could be used by a garage to fix a car having issues downloading an update for instance. Therefore, like backend Package, Vehicle Package Manifest shall be an ARXML file format for interoperability purposes.