1. Input for Interpretation Document on Software Update
Japan
Coordination Meeting for Test Phase of SUMS
February

2. Scope Issue Main scope: Inside vehicle & Interfaces
　　This Regulation applies to vehicles of the categories:
[L], M, N, [O, R, S and T]
　Main scope: Inside vehicle & Interfaces
Outside vehicle(incl. Relevant Backend Servers)
Relevant Backend Servers are servers which store data(software) updated and update version data or administrator etc.
From TFCS-11-04

3. Boundary phase R&D Production Sales& Service Ｏｗｎｅｒ Ｕｓｅｒ SUMS’s Role
Software Version
Management Ａ A A A
Fail
Recovery A
N/A A A
Campaine/Relese
infomation A
N/A A A
Contracts and
Permissions
N/A
N/A A A
Recording and
Traceability A A A A
：Coorperate with Backend System
A: Apply Certification of SUMS

4. Document For Evidencing
7.1 Requirements for the SUMS of the vehicle manufacturer
Requirment
Evidence
A process whereby information regarding
all initial and updated software versions,
including integrity validation data,
and relevant hardware components
of a type approved system can be uniquely identified
▽Software bill of materials
▽Hardware bill of materials
▽Software version traceability provision
▽Software distribution management manual
A process whereby any interdependencies of
the updated system with other systems can be identified
▽System architecture specification
▽System interface specification
▽Software update control specification

5. Hardware to be traced by software update is not ECU ID but CPU ID
　Chart 1
ECU ID:1000A
ECU ID:1000B
CPU ID
xx01
CPU ID
xx02
CPU ID
xx01
CPU ID
xx02
CPU ID
xx03
CPU ID
xx04
Hardware to be traced by software update is not ECU ID but CPU ID

6. Document For Evidencing
7.2 Requirements for the the vehicle Type
Requirment
Evidence
The vehicle manufacturer shall protect the RXSWINs
on a vehicle against unauthorised modification.
At the time of Type Approval, the means implemented
to protect against unauthorized modification
of the RXSWIN chosen by the vehicle manufacturer
shall be confidentially outlined.
▽UNR approval provision
▽Security control specification
▽Software version traceability provision
▽Software distribution management manual
The vehicle manufacturer shall ensure that the vehicle is able to restore systems to their previous version
in case of a failed or interrupted update or that the vehicle can be placed into a safe state after a failed or interrupted update.
▽Software update control specification
▽Software distribution management manual
▽Software version traceability provision

7. Confirmation of updating by User
Update process(example)
Confirmation of updating by User
Fail recovery for ) )
Fail
Download
Resume D/L
Success
Fail
Install
Resume Install
Success
Fail
Install
Hardware Fail
Success

8. Update process(example) continued
Fail recovery
In cases which a hardware fail occurred, a skilled person, such as a mechanic, may compete the process.
Fail
Reboot
Retry Install
＆Reboot
Success
Fail
Reboot
Hardware Fail
Success
Process Completed

9. How to Demonstrate？ For Software Update Management System
Manufacturers shall document that the processes used within their
Software Update Management System ensure vehicle safety and security adequately.
TechnicaI Services shall acknowledge that the processes used
within their Software Update Management System ensure vehicle safety and security on the document basis. (This activity includes inspections with the presence of TS.)
For Software Update Vehicle Type
Manufacturers shall demonstrate that the manufacture has taken
the necessary measures for the vehicle type by evidences.
Technical Services shall verify that the manufacturer has taken the
necessary measures for the vehicle type by evidences.