R156-MARKET-SURV | Cooperation with market surveillance authorities | 0 |
R156-OTA-WIRELESS | Additional requirements for OTA updates | 0 |
R156-PRIVACY | Data minimisation in update telemetry | 0 |
R156-RECORDS | Records of updates per vehicle | 0 |
R156-RXSWIN-MGMT | RXSWIN management and traceability | 0 |
R156-SUMS-GOV | Software Update Management System governance | 0 |
R156-SUPPLIER | Supplier-delivered software management | 0 |
R156-SW-COMPAT | Pre-update compatibility and dependency check | 0 |
R156-SW-EXECUTION | Safe and reliable update execution | 0 |
R156-SW-IMPACT | Assessment of impact on type approval and safety | 0 |
R156-SW-INTEGRITY | Integrity and authenticity of software updates | 0 |
R156-SW-INVENTORY | Software identification and documentation | 0 |
R156-SW-USERINFO | Information to the user before and after the update | 0 |
UNECER156-1 | Software Updates Management System (SUMS) | 0 |
UNECER156-2 | Type Approval and RxSWIN | 0 |
UNECER156-3 | Update Process and Vehicle Owner Information | 0 |
UNECER156-4 | Cyber Linkage to R155 and Lifecycle | 0 |
10 | 10 and 12 Penalties for non-conformity and authority contacts | 0 |
11.1 | 11.1 Inform the authority when production is definitively discontinued | 0 |
13 | 13 Transitional provisions of the 01 series | 0 |
3 | 3 Application for approval | 0 |
3.3 | 3.3 Application documents: vehicle type description and the SUMS certificate | 0 |
3.4 | 3.4 Sufficient information despite intellectual property or know-how | 0 |
3.6 | 3.6 Submit a vehicle representative of the type for testing | 0 |
3.7 | 3.7 Documentation package and material open for inspection, kept ten years | 0 |
4.1 | 4.1 International approval mark on every conforming vehicle | 0 |
5 | 5 Approval: authority verification and notification | 0 |
6 | 6 Certificate of Compliance for Software Update Management System | 0 |
6.3 | 6.3 SUMS certificate application: SUMS documents and signed declaration | 0 |
6.4 | 6.4 Declare and demonstrate the necessary SUMS processes | 0 |
6.5 | 6.1, 6.5 to 6.7, 6.9 and 6.10 Authority grant, validity, withdrawal and renewal of the SUMS certificate | 0 |
6.8 | 6.8 Inform the authority of changes affecting the SUMS certificate | 0 |
7 | 7 General specifications | 0 |
7.1.1 | 7.1.1 Processes to be verified at initial assessment | 0 |
7.1.1.1 | 7.1.1.1 Information documented, securely held and available to the authority | 0 |
7.1.1.10 | 7.1.1.10 Assess whether an update adds, alters or enables functions or changes legislated parameters | 0 |
7.1.1.11 | 7.1.1.11 Assess effects on other systems needed for safe operation and on functionality since registration | 0 |
7.1.1.12 | 7.1.1.12 Process to inform the vehicle user about updates | 0 |
7.1.1.13 | 7.1.1.13 Make RXSWIN register and target vehicle records available to authorities | 0 |
7.1.1.2 | 7.1.1.2 Unique identification of software versions, integrity data and hardware of type approved systems | 0 |
7.1.1.3 | 7.1.1.3 Assign a dedicated RXSWIN to every approval whose relevant software is updated | 0 |
7.1.1.4 | 7.1.1.4 Access and update RXSWIN information before and after an update | 0 |
7.1.1.5 | 7.1.1.5 Verify that software on a component matches its RXSWIN | 0 |
7.1.1.6 | 7.1.1.6 Identify interdependencies of the updated system with other systems | 0 |
7.1.1.7 | 7.1.1.7 Identify target vehicles for a software update | 0 |
7.1.1.8 | 7.1.1.8 Confirm compatibility with the target vehicles' last known configuration before issue | 0 |
7.1.1.9 | 7.1.1.9 Assess, identify and record whether an update affects type approved systems | 0 |
7.1.2 | 7.1.2 Records kept for each update applied to a vehicle type | 0 |
7.1.2.1 | 7.1.2.1 Documentation of the update processes and standards used | 0 |
7.1.2.2 | 7.1.2.2 Configuration of type approved systems before and after an update | 0 |
7.1.2.3 | 7.1.2.3 Auditable register of all software relevant to each RXSWIN | 0 |
7.1.2.4 | 7.1.2.4 Target vehicle list and compatibility confirmation | 0 |
7.1.2.5 | 7.1.2.5 Documentation for every update: purpose, effects, approval status, conditions, safety, security and V&V | 0 |
7.1.3 | 7.1.3 Security: what the manufacturer demonstrates | 0 |
7.1.3.1 | 7.1.3.1 Protect software updates against manipulation before the update process starts | 0 |
7.1.3.2 | 7.1.3.2 Protect the update processes and the development of the delivery system | 0 |
7.1.3.3 | 7.1.3.3 Appropriate verification and validation of vehicle software | 0 |
7.1.4 | 7.1.4 No updates to registered 01 series vehicles unless every assessed approval has an RXSWIN | 0 |
7.1.5 | 7.1.5 Additional requirements for software updates over the air | 0 |
7.1.5.1 | 7.1.5.1 Assess that over-the-air updates will not impact safety if conducted during driving | 0 |
7.1.5.2 | 7.1.5.2 Updates needing skilled or complex action proceed only with a skilled person present or in control | 0 |
7.2 | 7.2 Requirements for the vehicle type | 0 |
7.2.1.1 | 7.2.1.1 Protect the authenticity and integrity of software updates on the vehicle | 0 |
7.2.1.2 | 7.2.1.2 Requirements for RXSWIN | 0 |
7.2.1.2.1 | 7.2.1.2.1 Each RXSWIN uniquely identifiable and updated on extension or new approval | 0 |
7.2.1.2.2 | 7.2.1.2.2 RXSWIN or software versions readable through a standard interface | 0 |
7.2.1.2.3 | 7.2.1.2.3 Protect RXSWINs and software versions on the vehicle against unauthorised modification | 0 |
7.2.2 | 7.2.2 Additional requirements for over-the-air updates | 0 |
7.2.2.1.1 | 7.2.2.1.1 Restore the previous version or reach a safe state after a failed or interrupted update | 0 |
7.2.2.1.2 | 7.2.2.1.2 Execute updates only with enough power to complete or recover | 0 |
7.2.2.1.3 | 7.2.2.1.3 Technical means ensure safe execution where an update may affect safety | 0 |
7.2.2.2 | 7.2.2.2 Inform the user before execution: purpose, changes, duration, unavailable functions, instructions | 0 |
7.2.2.3 | 7.2.2.3 Prevent driving and unsafe functions where execution while driving may be unsafe | 0 |
7.2.2.4 | 7.2.2.4 Inform the user after execution of success or failure and of changes | 0 |
7.2.2.5 | 7.2.2.5 Vehicle checks preconditions before executing an update | 0 |
8.1 | 8.1 Notify modifications of the vehicle type | 0 |
9.1.1 | 9.1.1 Conformity of production: record test results and keep the documents | 0 |
ANNEXES | Annexes 1 to 4: information document, communication, approval mark, SUMS certificate model | 0 |
INTERPRETATION | The Interpretation Document for UN Regulation No. 156 | 0 |
STANDARD | UN Regulation No. 156: the Regulation, its scope and definitions | 0 |
STATUS | Status: the 01 series in force from 4 June 2026 beside the original version | 0 |