CS/OTA informal group proposal for a document to assist with the implementation of the new UN Regulation on cybersecurity management. This document is also available with track changes in a word document format and portable document format.

Proposal to improve the text with editorial clarifications and restructuring.

Presentation raising concerns over discrepancies and risks of misinterpretation in the application of the regulation by technical services.

Proposal to clarify that the Approval Authority should postpone granting a cybersecurity management approval in the absence of agreement on the common interpretation of a provision where the interpretation of the Approval Authority has raised comments from other authorities under the review procedure provided for in paragraph 5.3.4.

Proposal from the Informal Working Group on Advanced Emergency Braking Systems (AEBS) for vehicles of Categories M1 and N1 to supplement the proposals of document GRVA/2020/26 to improve the text on a number of issues.

Proposal from the Informal Working Group on Advanced Emergency Braking Systems (AEBS) for vehicles of Categories M1 and N1 in order to supplement the proposals of document GRVA/2020/27 to improve the text on a number of issues.

Proposal from the Informal Working Group on Advanced Emergency Braking Systems (AEBS) for vehicles of Categories M1 and N1 in order to supplement the proposals of document GRVA/2020/35 to improve the text on a number of issues.

This proposal revises the changes proposed in document GRVA/2020/7 based on stakeholder feedback. The proposal introduces provisions for M₁ vehicle to allow for lateral accelerations up to 40% greater than the 3 m/s² limitation for a period up to two seconds in order to in order navigate unexpected changes in the radius of the curvature of a bend and avoid driving behaviour that may be unexpected and/or confusing to the operator and following vehicles.

Proposal for amendments to document GRVA/2020/22.

Proposal for an alternative to ensure user attentiveness when activating a remote-controlled parking system.

Proposal to modify the following elements:

1. paragraph 5.6.4.2.3., delete “temporarily”
2. paragraph 5.6.4.5.2.1., replace “actually” by “anticipated to be”
3. paragraph 5.6.4.6.6., B1 shall resume “in a timely manner”
4. paragraph 5.6.4.6.8.1., clarify the suppression criteria
5. paragraph 5.6.4.7., define distance tolerances for lane-change critical distances
6. Annex 8, Paragraph 2., Carry over the language already adopted for ACSF B1: “At the manufacturer’s discretion and with the agreement of the Technical Service, a lane with a width of less than 3.5 m may be used, if the correct function of the system on roads with wider lanes can be demonstrated.” and allow for lower temperature and wet surface test conditions, and
7. Annex 8, Paragraph 3.5.1.2. (j), amend the pass condition with regard to direction indicator deactivation.

Consolidated proposal incorporating comments from OICA/CLEPA, CITA, Germany, and AVERE (including most recent proposal to the 7th GRVA session).

Proposal to clarify the text with regard to:

1. paragraph 2.6., Definition of an imminent collision
2. paragraphs 5.1.9 and 7.1.4., Lifetime of the system
3. paragraph 5.2.3.3., Traffic Rules and Safety Distance to the front
4. paragraph 5.2.5.2. – “anticipated TTC” in cut-in scenario
5. paragraph 6.2.5.1., Deactivation by input to driving controls
6. paragraph 6.2.6., Transition to assisted driving
7. paragraph 6.4.4., Examples of information to the driver
8. Annex 5 – Tests
   • Section 5.1. contains physical tests that have to be performed at the time of type approval
   • Section 5.2. aims to confirm at the time of type approval, that the system complies with the corresponding provisions of the main text. This confirmation shall be done by at least one physical test per provision, if possible due to the nature of the provision, and may be supported by further evidence.
   • Section 5.3. is a collection of additional scenarios, that the ALKS could encounter. Whether they are relevant to the ALKS depends on its ODD. So either the manufacturer explains why his system will not need to handle these scenarios, or has to explain the behaviour of the ALKS.
   • larify the content of par. 5.2. by rewording the provisions similar to that of the core text.

This document proposes a new 04 series of amendments to Regulation 79 with regard to a system that aims at bringing the vehicle to a safe stop in case of driver unavailability, defining a “risk mitigation function”.

Proposal to permit manoeuvring assistance in defined low speed driving situations to reduce damages and injuries.

Proposal to address risks related to activities other than driving and to clarify that a declaration of a maximum operational speed that exceeds 60 km/h is possible, but not required.

Proposal to amend the proposal from Germany regarding lane-change functionality:

1. paragraph 5.2.1. – lane keeping
2. paragraph 5.2.6.1. – risk to safety of the vehicle occupants and other road users
3. paragraphs 5.2.6.2. and 5.2.6.3. – preconditions for a lane change procedure
4. paragraph 5.2.6.5. – timing of a lane change maneuver
5. paragraph 5.2.6.6. and its sub-paragraphs – criticality of a lane change maneuver
6. paragraph 7.1.3. – rear detection range
7. Annex 5. – test cases for rear detection range, lane change.

The intention of the proposed amendment is to clarify the existing text on continued support of an ACSF B1 if the boundary conditions are exceeded. It clarifies that under certain circumstances, e.g. if there are no lane markings present or if the vehicle has already drifted substantially out of the lane such that the lane may no longer be recognized, a continuation of support may no longer be possible or reasonable.

The proposal aims to correct 5 types of inconsistencies:

1. The reference to Annex 4 is repeated in each sub-paragraph and should instead be stated once in each paragraph.
2. Acronyms are used inconsistently. Proposal to use them consistently throughout similar to UN-R79, e.g. Emergency Manoeuvre (EM), and when used in the text as “emergency manoeuvre”
3. Each sub-paragraph has a heading, this helps understand the structure and should be carried over to par. 8.1., 9.1. and 9.2. as well, the wording for the heading of par. 9.1. and 9.2. are derived from UN-R155 and UN-R156 respectively.
4. Consistent use of term throughout, e.g. R₁₅₇SWIN without blank, Cyber Security as two words as used in UN-R155
5. Editorial corrections, e.g. missing paragraph numbers, missing full stop in the paragraph number.

Proposal to include all vehicle categories M and N in the scope of UN R157.

The intention of the proposed amendment is to clarify the existing text on continued support of an ACSF B1 if the boundary conditions are exceeded.

This document is password protected. Please contact the GRVA secretariat for access.

Under the initial ALKS regulation and its reference to the new cyber security requlation, manufacturers are permitted to use an alternative software identification system instead of the proposed RxSWIN format. This proposal seeks to clarify the use of such alternative identifications in the approval process.

Japan supports the proposal from Germany (GRVA-07-03) to establish an informal working group to develop requirements for heavy-duty vehicle VRU AEBS. Japan proposes to adapt provisions from UN R152 on light vehicle AEBS.

Proposal to ensure that the information provided regarding software updates is accessible for use in type approval, conformity of production, market surveillance, recalls and Periodic Technical Inspection (PTI).

Presentation regarding requirements for stop lamp illumination with regard to various types of braking systems, including those of electric vehicles.

Proposal to clarify the explanation of the requirements of paragraph 7 and Annex 1 of the UN R156 (software updates and software updates management systems) and provide information on what may be used to evidence those requirements.

Proposal to clarify the explanation of the requirements of paragraph 7 and Annex 1 of the UN R156 (software updates and software updates management systems) and provide information on what may be used to evidence those requirements.

Proposal to replace the specification of the type and size of brake caliper and brake disc for brake lining CoP assessment with specifications for a pad area and thickness of the original approval. The original specification corresponds to obsolete caliper and rotor configurations no longer in widespread use.