| UN R155 and R156: Approvals for ‘out-of-scope’ vehicles |
| Reference Number: TFCS-38-03 |
|
Vehicles of categories M1, N, O, R, S and T may fall out of scope of UN R155 or UN R156 if they lack ECUs or do not permit software updates. Approval authorities currently make individual determinations regarding whether vehicles are in or out of scope, and justification for out-of-scope decisions must be recorded to ensure vehicles remain out of scope during the lifetime of whole vehicle approval. UN Regulation No. 10 provides precedent by allowing approvals for vehicles where certain equipment is not relevant. A similar provision could be incorporated into UN R155 and UN R156 by amending the scope and adding provisions to section 5 allowing manufacturers to obtain approvals for vehicles that do not permit software updates, with requirements of paragraph 7 not applying. |
| Submitted by: VCA |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 23 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| CS/OTA: Draft updated terms of reference |
| Reference Number: TFCS-38-02/Rev.1 |
|
The Informal Working Group on Cyber Security and Software Updates will continue to consider how cyber security and software updates have a bearing on automotive safety and security, and whether any changes are necessary to the Regulations and guidance it has produced under WP.29. In particular, the IWG shall maintain official documents regarding UN R155, UN R156, and Recommendations on uniform provisions concerning cyber security and software updates; develop amendments to relevant documents; develop a proposal to amend UN Regulations under the responsibility of GRVA to record details of an RXSWIN where applicable which have been mandated by the 01 series of UN Regulation No. 156; develop proposals to amend UN Regulation No. 155 and its interpretation document to support application in national/regional frameworks for aspects such as multi-stage manufacturing; consider and develop deliverables regarding software updates after registration potentially creating a proposal for modification to the type approval numbering or a classification of update categories; support and review the application of cyber security and software update provisions across GRs notably for the Global Technical Regulation on Automated Driving Systems; and provide opportunities to participants to share knowledge, experience and ideas from implementation of national regulation/standards regarding CS/OTA as well as UN R155 and R156. The IWG will continue its activities until November 2029. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R156: Question on 01 series of amendments interpretation |
| Reference Number: TFCS-38-07 |
|
The document clarifies two interpretation points regarding UN R156-01. First, software updates to registered vehicles require that an RXSWIN be assigned to every Regulation No. X type approval assessed during the update process, unless the manufacturer does not plan software updates for that particular system Regulation. Second, regarding para. 7.2.1.2.2., it is proposed to delete the requirement that software version changes be declared each time they are updated, since software versions are declared for each regulation subject to software updates following amendments to RE.3 Annex 7. |
| Submitted by: NTSEL |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 26 Jun 26 |
| Relevant to: UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| Cyber security: Modifications to GRVA-25-30 |
| Reference Number: TFCS-38-12 |
|
Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information. |
| Meeting Sessions: 38th TFCS session (30 Jun-1 Jul) |
| Document date: 30 Jun 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
No matching documents.
Over the Air: A method of delivering and installing software updates to a vehicle remotely via a wireless communication link