Lexploria

9.3.2021

EN

Official Journal of the European Union

L 82/60

Only the original UN/ECE texts have legal effect under international public law. The status and date of entry into force of this Regulation should be checked in the latest version of the UN/ECE status document TRANS/WP.29/343, available at:http://www.unece.org/trans/main/wp29/wp29wgs/wp29gen/wp29fdocstts.html

UN Regulation No 156 – Uniform provisions concerning the approval of vehicles with regards to software update and software updates management system [2021/388]

Date of entry into force: 22 January 2021

This document is meant purely as documentation tool. The authentic and legally binding text is: ECE/TRANS/WP.29/2020/80.

CONTENTS

REGULATION

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.ANNEXES

1Information document

Appendix 1 – Model of declaration of compliance for Software Update Management System

2

3

4

1. SCOPE

1.1.

2. DEFINITIONS

2.1.

(a)

The manufacturer’s designation of the vehicle type;

(b)

Essential aspects of the design of the vehicle type with respect to software update processes.

2.2.

2.3.

2.4.

2.5.

2.6.

2.7.

2.8.

2.9.

2.10.

2.11.

3. APPLICATION FOR APPROVAL

3.1.

3.2.

3.3.

3.4.

3.5.

3.6.

3.7.

(a)

The formal documentation package for the approval, containing the material specified in Annex 1 which shall be supplied to the Approval Authority or its Technical Service at the time of submission of the type approval application. This documentation package shall be used by the Approval Authority or its Technical Service as the basic reference for the approval process. The Approval Authority or its Technical Service shall ensure that this documentation package remains available for at least 10 years counted from the time when production of the vehicle type is definitely discontinued.

(b)

Additional material relevant to the requirements of this regulation may be retained by the manufacturer but made open for inspection at the time of type approval. The manufacturer shall ensure that any material made open for inspection at the time of type approval remains available for at least a period of 10 years counted from the time when production of the vehicle type is definitely discontinued.

4. MARKING

4.1.

4.1.1.

4.1.2.

4.2.

4.3.

4.4.

4.5.

5. APPROVAL

5.1.

5.1.1.

5.2.

5.3.

6. CERTIFICATE OF COMPLIANCE FOR SOFTWARE UPDATE MANAGEMENT SYSTEM

6.1.

6.2.

6.3.

6.3.1.

6.3.2.

6.4.

6.5.

6.6.

6.7.

6.8.

6.9.

6.10.

7. GENERAL SPECIFICATIONS

7.1.

7.1.1.

7.1.1.1.

7.1.1.2.

7.1.1.3.

7.1.1.4.

7.1.1.5.

7.1.1.6.

7.1.1.7.

7.1.1.8.

7.1.1.9.

(a)

Entries in the information package will need to be modified;

(b)

Test results no longer cover the vehicle after modification;

(c)

Any modification to functions on the vehicle will affect the vehicle’s type approval.

7.1.1.10.

7.1.1.11.

7.1.1.12.

7.1.2.

7.1.2.1.

7.1.2.2.

7.1.2.3.

7.1.2.4.

7.1.2.5.

(a)

The purpose of the update;

(b)

What systems or functions of the vehicle the update may affect;

(c)

Which of these are type approved (if any);

(d)

If applicable, whether the software update affects the fulfilment of any of the relevant requirements of those type approved system;

(e)

Whether the software update affects any system type approval parameter;

(f)

Whether an approval for the update was sought from an approval body;

(g)

How the update may be executed and under what conditions;

(h)

Confirmation that the software update will be conducted safely and securely;

(i)

Confirmation that the software update has undergone and successfully passed verification and validation procedures.

7.1.3.

7.1.3.1.

7.1.3.2.

7.1.3.3.

7.1.4.

7.1.4.1.

7.1.4.2.

7.2.

7.2.1.

7.2.1.1.

7.2.1.2.

7.2.1.2.1.

7.2.1.2.2.

If RXSWINs are not held on the vehicle, the manufacturer shall declare the software version(s) of the vehicle or single ECUs with the connection to the relevant type approvals to the Approval Authority. This declaration shall be updated each time the declared software version(s) is updated. In this case, the software version(s) shall be easily readable in a standardized way via the use of an electronic communication interface, at least by the standard interface (OBD port).

7.2.1.2.3.

7.2.2.

7.2.2.1.

7.2.2.1.1.

7.2.2.1.2.

7.2.2.1.3.

7.2.2.2.

(a)

The purpose of the update. This could include the criticality of the update and if the update is for recall, safety and/or security purposes;

(b)

Any changes implemented by the update on vehicle functions;

(c)

The expected time to complete execution of the update;

(d)

Any vehicle functionalities which may not be available during the execution of the update;

(e)

Any instructions that may help the vehicle user safely execute the update;

In case of groups of updates with a similar content one information may cover a group.

7.2.2.3.

(a)

Ensure the vehicle cannot be driven during the execution of the update;

(b)

Ensure that the driver is not able to use any functionality of the vehicle that would affect the safety of the vehicle or the successful execution of the update.

7.2.2.4.

(a)

The vehicle user is able to be informed of the success (or failure) of the update;

(b)

The vehicle user is able to be informed about the changes implemented and any related updates to the user manual (if applicable).

7.2.2.5.

8. MODIFICATION OF VEHICLE TYPE AND EXTENSION OF TYPE APPROVAL

8.1.

8.1.1.

8.1.2.

8.1.3.

9. CONFORMITY OF PRODUCTION

9.1.

9.1.1.

9.1.2.

9.1.3.

10. PENALTIES FOR NON-CONFORMITY OF PRODUCTION

10.1.

10.2.

11. PRODUCTION DEFINITIVELY DISCONTINUED

11.1.

12. NAMES AND ADDRESSES OF TECHNICAL SERVICES RESPONSIBLE FOR CONDUCTING APPROVAL TEST, AND OF TYPE APPROVAL AUTHORITIES

12.1.

(1) As defined in the Consolidated Resolution on the Construction of Vehicles (R.E.3.), document ECE/TRANS/WP.29/78/Rev.6, para. 2 - www.unece.org/trans/main/wp29/wp29wgs/wp29gen/wp29resolutions.html

(2) The distinguishing numbers of the Contracting Parties to the 1958 Agreement are reproduced in Annex 3 to the Consolidated Resolution on the Construction of Vehicles (R.E.3), document ECE/TRANS/WP.29/78/Rev.6.

ANNEX 1

Information document

The following information, if applicable, shall be supplied in triplicate and include a list of contents. Any drawings shall be supplied in appropriate scale and in sufficient detail on size A4 or on a folder of A4 format. Photographs, if any, shall show sufficient detail.

1.Make (trade name of manufacturer): …

2.(Type is the type to be approved, commercial description refers to the product in which the approved type is used)

3.Means of identification of type, if marked on the vehicle: …

4.Location of that marking: …

5.Category(ies) of vehicle: …

6.Name and address of manufacturer/manufacturer's representative: …

7.Name(s) and Address(es) of assembly plant(s): …

8.Photograph(s) and/or drawing(s) of a representative vehicle: …

9.Software Updates

9.1.

General construction characteristics of the vehicle type: …

9.2.

The number of the Certificate of Compliance for Software Update Management System: …

9.3.

Security measures.

9.3.1.

Documents for the vehicle type to be approved describing that the update process will be performed securely …

9.3.2.

Documents for the vehicle type to be approved describing that the RXSWINs on a vehicle are protected against unauthorized manipulation …

9.4.

Software updates over the air

9.4.1.

Documents for the vehicle type to be approved describing that the update process will be performed safely…

9.4.2.

How a vehicle user is able to be informed about an update before and after its execution. …

Appendix 1 to Annex 1

Model of declaration of compliance for Software Update Management System

Manufacturer’s declaration of compliance with the requirements for Software Update Management System

Manufacturer Name:…

Manufacturer Address: …

…………… (Manufacturer Name) attests that the necessary processes to comply with the requirements for the Software Update Management System laid down in paragraph 7.1 of UN Regulation No 156 are installed and will be maintained.

Done at: ………………………………………… (place)

Date: …

Name of the signatory: …

Function of the signatory: …

………………………………………………

(Stamp and signature of the manufacturer’s representative)

ANNEX 2

Communication

(Maximum format: A4 (210 × 297 mm))

issued by:

Name of administration:

…

Concerning (2):

Approval granted

Approval extended

Approval withdrawn with effect from dd/mm/yyyy

Approval refused

Production definitively discontinued

of a vehicle type, pursuant to UN Regulation No 156

Approval No: …

Extension No: …

Reason for extension: …

1.Make (trade name of manufacturer): …

2.Type and general commercial description(s) …

3.Means of identification of type, if marked on the vehicle: …

3.1.

Location of that marking: …

4.Category(ies) of vehicle: …

5.Name and address of manufacturer/manufacturer’s representative: …

6.Name(s) and Address(es) of the production plant(s) …

7.Number of the certificate of compliance for software update management system: …

8.Software updates over the air included (yes/no): …

9.Technical Service responsible for carrying out the tests: …

10.Date of test report: …

11.Number of test report: …

12.Remarks: (if any) …

13.Place: …

14.Date: …

15.Signature: …

16.The index to the information package lodged with the Approval Authority, which may be obtained on request is attached.

(1) Distinguishing number of the country which has granted/extended/refused/withdrawn approval (see marking provisions (footnote) in this Regulation).

(2) Strike out what does not apply.

ANNEX 3

Arrangement of approval mark

MODEL A

(See paragraph 4.2 of this Regulation)

a = 8 mm min.

The above approval mark affixed to a vehicle shows that the road vehicle type concerned has been approved in the Netherlands (E 4), pursuant to Regulation No 156, and under the approval number 001234. The first two digits of the approval number indicate that the approval was granted in accordance with the requirements of this Regulation in its original form (00).

ANNEX 4

Model of Certificate of Compliance for Software Update Management System

Certificate of Compliance for Software Update Management System

with UN Regulation No 156

Certificate Number [Reference number]

[……. Approval Authority]

Certifies that

Manufacturer: …

Address of the manufacturer: …

Complies with the provisions of Regulation No 156

Verifications have been performed on: …

by (name and address of the Approval Authority): …

Number of report: …

The certificate is valid until: [………………………………………………Date]

Done at: [……………………………………Place]

On: [……………………………………Date]

[…………………………………………………Signature]

Menu

UN Regulation No 156 – Uniform provisions concerning the approval of vehicles with regards to software update and software updates management system [2021/388]

UN Regulation No 156 – Uniform provisions concerning the approval of vehicles with regards to software update and software updates management system [2021/388]

LEXI