UN Task Force on Cyber Security and OTA issues

Slides:



Advertisements
Similar presentations
December ''Member State experience – follow up to the notifications - actions undertaken in relation to the notifications'' Brussels, December 1.
Advertisements

Instructions and forms
By Drudeisha Madhub Data Protection Commissioner Date:
Systems Analysis and Design: The Big Picture
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
EReg ANNUAL CONFERENCE 11 th MAY 2010 Vehicle Administrative Platform Walter Nissler European Commission Directorate General Mobility & Transport Road.
EReg The German PTI Database / Information System Folie 1.
Green Partnerships Kick-off meeting Expenditure reporting procedure in PRESAGE- CTE JTS MED Programme cofinancé par le Fonds Européen de Développement.
Supervision SICOR Securities, Inc.. Why? NASD 3110 requires the firm to “…establish and maintain a system to supervise the activities of each registered.
Federal Motor Transport Authority KBA - We score with road safety - Vehicle Technology- Product Safety and Recalls Informal document EFWG (1 st meeting.
CABLING SYSTEM WARRANTY REGISTRATION. PURPOSE OF CABLING REGISTRATION.
Networks ∙ Services ∙ People eduGAIN Townhall Meeting Nicole Harris (or updating the eduGAIN policy suite) “Unicorns can be sued in Wales”
Organization and Implementation of a National Regulatory Program for the Control of Radiation Sources Program Performance Criteria.
Implementation of the Digital Tachograph Card Issuing System in Poland – Case Study Speaker: Piotr KUŹNIAK – Polish Security Printing Works
Activity processes of brokers in carrying out operations on the customs clearance of goods Activity processes of brokers in carrying out operations on.
Doc.: IEEE /0377r2 Submission March 2005 Adrian Stephens, Intel CorporationSlide 1 Ballotting Process Improvements Notice: This document has been.
TF#4 – Mechanical Integrity Approved Japanese proposal for addition of vehicle mechanical protection structure into mechanical integrity requirement. EVS-11-17e.
Status report on the activities of TF-CS/OTA
GRRF Ad-Hoc Working Group
Submitted by FIA Document No. ITS/AD-10-06
Introduction TRL’s study was performed in the context of ACSF updates to UN Regulation No 79. Focus: Ensure safe system function in all real-world driving.
Submitted by FIA Document No. TFCS-05-11
Software Quality Control and Quality Assurance: Introduction
Chapter 18 Maintaining Information Systems
RISGE-RG use case template
Federal Motor Transport Authority
Documentation control
Outcome TFCS-05 // May OICA, Paris
Distribution of software version numbers
OICA input on software updates to UN TF CS/OTA
Concept of ACSF TAN (Type Approval Number)
Suggestion on software update
Pre-Execution Process Review Presentation
Outcome TFCS-11// February Washington DC
General Computer Applications by Barbara Teterycz
EU Database Protection
Outcome TFCS-11// February Washington DC
Informal Document: ACSF-11-08
Outcome of TFCS-12 - summary slides - (detailed meeting minutes will be provided separately) April The Shilla Seoul, ROK.
Summary of software update progress
Status of the Informal Working Group on ACSF
What is Digital Right Management’s Role in Modern Education System’s Play? —A Comparative Research of DRM System’s Influence in.
Status of the Informal Working Group on ACSF
Status report on the activities of TF-CS/OTA
Informal document GRVA nd GRVA, 28 Jan Feb. 2019
Technical Assistance for Development of a Strategy for Alignment with
Technical Assistance for Development of a Strategy for Alignment with
Maintaining Information Systems (SAD- 18)
Status report from UNECE Task Force on Cyber Security &
Declaration of Conformance (DOC) Proposal for Implementation
Lifecycle of vehicle type vs Lifetime of one vehicle
Informal document GRVA st GRVA, September 2018
Replies by the Task Force to the comments provided by GRVA members
Input for Interpretation Document on Software Update
Status report of TF-CS/OTA
Development roadmap of Suomi.fi-services
International Telecommunication Union CITS meeting 8 March 2019 Geneva Status report of the GRVA activities Context, current activities and impact François.
Overview of the recommendations on software updates
Leuven Policy implementation.
Highlights of the 177th WP.29 session and
Your First Car Mandatory Permit and Label
Input for ad hoc on software update on 7th Dec. from Japan
Input for ad hoc on software update on 7th Dec. from Japan
Chapter 18 Maintaining Information Systems
National data opt-out - Preparing for implementation
Software Updates Current situation
Japan CS/OTA 15th session, Geneva 27-28, August 2019
Access to data requirementS
Management of Change GROUP HSE RULE (CR-GR-HSE-302)
1) Application of Cybersecurity Regulation for new registrations
Presentation transcript:

UN Task Force on Cyber Security and OTA issues Type-approval    

Current situation Changes of type approval related software could cause an extension of the type approval(s) or demand new type approval(s) and can be afterwards installed in new vehicles before registration (Issuing of a new CoC could be necessary) Software updates by the manufacture which does not effect type approval related issues and do not relate to the product safety act are possible to be installed in vehicles after first registration under the responsibility of the manufacturer Software after the first registration from another manufacturer and type approval relevant software changes have to be handle on a national level (individual approval, an approval with limited scope, etc.) Software updates could have influences on the national registration, the national procedures for changes of vehicles have to take into consideration

Possible solution Develop an international regulation for type approval related software, which can be installed in vehicles after registration (replacement software), or develop annexes for software changes after the registration for the single regulations Develop a message for actual vehicle information (AVI), which can be shared between the member states, where an electronic CoC or DoC have to be a part of it

Possible national interim process to deal with OTA issues in Germany With the documentation for the extension of the type approval or for the documentation for the new system approval the manufacturer declare on which vehicles the new software can be installed (VIN numbers or extension numbers of the whole vehicle type approval) The manufacturer have to describe, how the validity of the software can be checked during PTI The manufacturer explain, how the software is protected against manipulation and how the integrity of the software can be verified The technical service verifies, if the software can be installed in the vehicles declared by the manufacturer and if the validity and integrity of the software can be checked during the PTI The technical service confirms in the test report of the extension of the type approval or in the test report of the new system approval that the declaration and distribution of the manufacturer is correct

Possible national interim process to deal with OTA issues in Germany The possibility to install the software on registered vehicles becomes part of the extension of the type approval or part of the new system approval The vehicle owner may need an extract of the extension or an extract of the new approval and the information if the changes modify the registration documents (immediately changes are necessary or changes have to be recorded at the next opportunity) If the registration documents have to be changed (immediately), e.g. because of an in increase of engine power, the vehicle owner have to contact the registration authority What is the procedure in other member states? Could other member states accept the described process? How can the (extract of the of) the extension or (the extract of) the new approval be provided to other member states? Have the manufacturer to contact every member state, provided the (extract of the of) the extension or (the extract of) the new approval and ask for acceptance?

General comments It is important to check during the PTI, if a valid software is installed on the vehicle - the PTI organizations therefore need access to the AVI and may also need to add single information to it Current legislation have to be analyzed regarding the impact of software changes and the demand of granting extensions of type approvals or granting new type approvals The difference between the current way of installing modified software on vehicles (in the car service station from professional personal) and the installation of software over the air by the customer should be a part of the discussion in the group - Under which circumstances it is allowed to install what functionality and how should the customer be informed (about the process and the changes)?

Thanks for your attention! Legal notice Publisher: Kraftfahrt-Bundesamt 24932 Flensburg Internet: www.kba.de Special information and advice: Phone: 0461 316-0 Fax: 0461 316-1650 E-mail: kba@kba.de Issued in May 2011 Version: May 2012 Printing: Druckzentrum KBA Picture Source: xxx All rights reserved. Reproduction and dissemination of this publication, including in parts or in digital form, is permitted provided the Kraftfahrt-Bundesamt is acknowledged as its source. This includes the dissemination of contents of this publication that have been obtained indirectly. © Kraftfahrt-Bundesamt, Flensburg Questions? We score with road safety!