RXSWIN Goals Tesla A process that identifies securely

  • Slides: 6
Download presentation
RXSWIN Goals (Tesla) • A process that identifies securely hardware and software versions of

RXSWIN Goals (Tesla) • A process that identifies securely hardware and software versions of all ECUs on the vehicle, identifiable via onboard user-interface or diagnostic tools. • A process that identifies a secure reference of each type approval for one or more vehicle subsystems, identifiable via onboard user-interface, diagnostic tools, or stored at the vehicle manufacturer. • A process that correlates reference of each type approval, and all affected software and hardware versions, identifiable via onboard userinterface or diagnostic tools, or stored at the vehicle manufacturer.

RXSWIN Goals (KBA / RDW) • Identification of the type approval relevant software (aspects)

RXSWIN Goals (KBA / RDW) • Identification of the type approval relevant software (aspects) for each system approval by introducing a software identification number in the system approvals • Identification of type approval relevant software modifications • Knowledge of old and current acceptable software (RXSWIN as well as the software on the ECUs including their integrity, validation data) • Connection between the RXSWINs/ type approval of the systems and the software on the ECUs (or the global software version number) • Identification of the software versions (in the absence of RXSWIN), or RXSWIN on single vehicles • Verification of the RXSWIN or software versions (software) on single vehicles with the OBD port for inspection, market surveillance, … - is the software on the vehicles known and legitimate • Connection between the RXSWINs/ software versions on a vehicle and the VIN by using the Do. C & DETA

Proposed Implementation – Use of Global Version Number Information available on vehicle and stored

Proposed Implementation – Use of Global Version Number Information available on vehicle and stored at manufacturer Information submitted to authorities Vehicle Global Software Version Number (v 1. 0*) ECU 1 v 5. 9** Information submitted to Technical Authorities ECU 2 v 1. 0** Type Approval Reference X 1 on Regulation X, applied on v 1. 0 ECU 3 v 2. 0** ECU 4 v 2. 0** Information submitted to Technical Authorities Type Approval Reference Y 1 on Regulation Y, applied on v 1. 0 (*): Information available to customers and via diagnostic tools (**): information available via diagnostic tools

Proposed Implementation – Use of Global Version Number Software update not affecting vehicle type

Proposed Implementation – Use of Global Version Number Software update not affecting vehicle type Information available on vehicle and stored at manufacturer Vehicle Global Software Version Number (v 1. 1*) Information submitted to authorities V 1. 1 assessed to not require Type Approval Extension ECU 1 v 5. 10** Information submitted to Technical Authorities ECU 2 v 1. 2** Type Approval Reference X 1 on Regulation X, applied on v 1. 0 and v 1. 1 ECU 3 v 2. 2** ECU 4 v 2. 0** Information submitted to Technical Authorities Type Approval Reference Y 1 on Regulation Y, applied on v 1. 0 (*): Information available to customers and via diagnostic tools (**): information available via diagnostic tools

Proposed Implementation – Use of Global Version Number Software update affecting vehicle type Information

Proposed Implementation – Use of Global Version Number Software update affecting vehicle type Information available on vehicle and stored at manufacturer Vehicle Global Software Version Number (v 2. 0*) Information submitted to authorities V 2. 0 assessed to require Type Approval Extension X 2 ECU 1 v 6. 0** Information submitted to Technical Authorities ECU 2 v 1. 2** Type Approval Reference X 2 on Regulation X, applied on v 2. 0 ECU 3 v 2. 5** ECU 4 v 2. 2** Information submitted to Technical Authorities Type Approval Reference Y 1 on Regulation Y, applied on v 1. 0, v 1. 1, v 2. 0 (*): Information available to customers and via diagnostic tools (**): information available via diagnostic tools

Proposed Implementation – Use of ECU Version Numbers Software update not affecting vehicle type

Proposed Implementation – Use of ECU Version Numbers Software update not affecting vehicle type Information available on vehicle and stored at manufacturer Information submitted to authorities X 1 assessed to not require Type Approval Extension ECU 1 v 5. 10** Information submitted to Technical Authorities ECU 2 v 1. 2** Type Approval Reference X 1 on Regulation X Applicable to ECU 1 v 5. 9, 5. 10 & ECU 2 v 1. 0, v 1. 2 ECU 3 v 2. 2** ECU 4 v 2. 0** Information submitted to Technical Authorities Type Approval Reference Y 1 on Regulation Y Applicable to ECU 4 v 2. 0 (*): Information available to customers and via diagnostic tools (**): information available via diagnostic tools