1 Scope
This document sets out the rules and basic principles of the design guidelines for networked vehicles. This document applies to Class M and Class N vehicles.
2 Normative references
The contents of the following documents constitute the essential provisions of this document through the normative references in the text. Among them, note the date of the cited documents, only the date of the corresponding version applicable to this document; do not note the date of the cited documents, its latest version (including all the revision of the list) applicable to this document.
GB/T 41901.1 Road Vehicles - Methodology for Connected Vehicles - Part 1: General Information (GB/T 41901.1-2022, ISO 20077-1: 2017, MOD)
3 Terms and definitions
The terms defined in GB/T 41901.1 and the following terms and definitions apply to this document.
3.1
Basic principle
Design principles to be taken into account in the design of networked vehicles
3.2
Life cycle
The life cycle of a vehicle is the range of conditions that can be encountered throughout its life, including design, manufacture, customer use, maintenance and recycling. manufacturing, customer use, maintenance and recycling.
3.3
local diagnostic facilitator
A person who maintains communication with a remote technician, is able to operate as requested by the remote technician and answer the remote technician's questions, thus assisting in the diagnosis.
Note. The local diagnostic facilitator has the ability to understand and describe what is displayed on the on-board instruments and signalling devices.
3.4 Operator
Operator
A person who operates, controls or services a networked vehicle from within the vehicle. Example: Local diagnostic assistant -
3.5
Requester requesier
A company or legal entity that submits a request for a new function to the manufacturer of a connected vehicle.
Note 1: The vehicle manufacturer, as an after-sales service provider, is considered to be the demander when submitting a demand.
Note 2: If the vehicle manufacturer is the same as the web-enabled vehicle manufacturer, the internal requirements process can be used.
4 Abbreviations
The following abbreviations apply to this document.
5 Examples for identifying rules and basic principles and specifying their content
5.1 In this document, the rules and basic principles are expressed in the following way: x x NUM: the content of the rule or basic principle.
Note: Rules and basic principles may be followed by explanatory text.
6 Overview
6.1 Role of the design guidelines in the design process of networked vehicles
The purpose of this document is to provide a common body of rules and basic principles for the design (physical, documentation, support, etc.) of networked vehicles and their interfaces by specifying a common body of rules and basic principles. Documentation, support, etc.). Based on the rules and basic principles, the manufacturer of a connected vehicle should develop a methodology or process for designing a connected vehicle for a specific use case or scenario.
Each connected vehicle manufacturer typically standardises the way in which this design process works through collaborative methods and processes, as shown in Figure 1.
6.2 The main elements of the connected vehicle design guidelines
The Design Guidelines for Connected Vehicles contain the following elements (see Figure 2):
--Technical requirement templates for the complete description of the minimum information when proposing new requirement functions (see Appendix B and Appendix C);
--A system of rules and basic principles to guide the design of new net-linked vehicle functions (see Chapters 4 and 8);
--Technical response templates for the complete description of minimum information when responding to new requirement functions (see Appendix B and Appendix D).
6.3 Consideration of new net-linked vehicle features
The manufacturer of a connected vehicle applies the design guidelines for a connected vehicle by implementing the rules and basic principles of this document. The design guidelines apply to the design of, or design changes to, a connected vehicle, including direct or indirect communication between the vehicle and a third party (e.g. the vehicle operator, owner, service provider or other connected vehicle interested party).
New functional requirements for Internet-connected vehicles may arise from regulations. Standards and individual requirements, the requirements for new connected vehicle functionality should be precisely described by the requirement owner through a technical requirement template for all required elements (e.g. performance-related elements).
The design guidelines also apply to the design of new interfaces from regulatory requirements for remote communication in vehicles.
This document applies both to any demand-side requirements for new functions of a net-connected vehicle and to situations where existing functions need to be extended or used remotely. For vehicles produced in multiple stages, this document applies to all relevant manufacturers. Enabling new functions by simply adding new equipment without taking into account the existing design may not achieve the desired results, on the one hand because the new functions may uncontrollably interfere with the initial or existing functions and, on the other hand, because the original vehicle system does not usually have all the components required for the new functions. The basic principles of the design guidelines are intended to emphasise the treatment of these risks.
These rules and basic principles set out in this document are intended to address in an appropriate manner the internal risks to the connected vehicle resulting from new connected vehicle functionality, whether or not this functionality already exists, by taking measures to manage these risks, including but not limited to the following:
-- modifying the electronic systems (resources, etc.) of the existing connected vehicle to implement the new functionality.
--do not configure the new functionality
- - Configuring new functions, but only under certain conditions; - - Modifying other existing functions.
Non-technical measures (e.g. contractual measures) may also be used to manage risks, e.g. risks related to the degradation or disruption of existing functions or services.
7 Rules
7.1 Overview
The design guidelines for networked vehicles are based on remote access and should maintain the essential safety and protection of the vehicle throughout its life cycle. Therefore, this document contains two rules (R001 and R 002), which should be adopted by the manufacturers of Internet-connected vehicles in their design methods and processes, 7.2 Security-related rules
R 001, When designing new features of a connected vehicle, the manufacturer of the connected vehicle shall take into account the possible security risks. Features that affect safety should be handled in accordance with best safety practices.
When designing an Internet-connected vehicle, the manufacturer should consider the safety of the vehicle, its occupants, operators and other users over the lifetime of the network.
When designing new functions for connected vehicles, connected vehicle manufacturers should apply rule R 001.
This classification is determined by the inherent risk of the function of the connected vehicle, the risk in a particular situation or the risk of the operation of a particular function (the same action may lead to a different risk).
Examples of safety risks for vehicles in operation; Example 1: Impaired braking capability of the vehicle.
Example 2: Inappropriate function, e.g. bringing the vehicle to a sudden standstill while driving on the road
Example 3: Inappropriate functions that exceed the set parameters.
Examples of safety risks in stationary vehicles:
Example 4: False activation of the airbag when the front seats are occupied. Example 5: False activation of high voltage components when the high voltage battery is disconnected. Example 6: False activation of a component during maintenance work -
7.3 Protection-related rules
R 002, When designing new functions of a connected vehicle, the manufacturer of the connected vehicle shall take into account the possible risks of protectiveness. Features that affect protectiveness should be handled in accordance with best protectiveness practices.
The manufacturer of a connected vehicle is responsible for ensuring that the vehicle is protected throughout its life cycle,
8 Basic principles
8.1 Overview
The Netlink vehicle manufacturer shall always meet the rules set out in this document when applying the Basic Principles to its own design methods and processes. 8.2 General Basic Principles
BP 001: The manufacturer of a networked vehicle is responsible for the design of the networked vehicle
BP 002: The networked vehicle manufacturer is responsible for the design of all interfaces of the networked vehicle to enable communication with the networked vehicle and BP 003: The networked vehicle manufacturer is responsible for the implementation of the new energy requirements of the networked vehicle.
The NVM is responsible for the design of the NUV and its functions, so that the NVM is responsible for both the implementation of each function of the NUV and the consistency of the entire set of functions.
The following objective limitations may exist in the implementation of new functions of the connected vehicle according to the methodology specified in this document:
--Objective limitations on the usability of the functionality;
--Objective limitations of functional performance;
--objective limitations due to differences in vehicles, models, etc;
--objective limitations due to special market conditions.
8.3 Basic principles of life-cycle relevance
BP 004; The manufacturer of a connected vehicle is responsible for assessing the impact of new connected vehicle features on the vehicle throughout its life cycle.
The demander shall not be limited in accessing data regarding the availability and expected performance of the required net connected vehicle functionality over the full life cycle. The manufacturer of the connected vehicle should analyse the impact of integrating this functionality over the full lifecycle of the vehicle (see Figure 3) to identify possible incompatibilities that may arise in cases not mentioned by the demand side (e.g. during the manufacturing, maintenance or recycling phases), the results of which may lead to a reduction in the performance and usability of the required new functionality.
Appendix A (informative) Comparison of the structure numbering of this document with ISO 20077-2:2018
Appendix B (informative) Technical template for the design guidelines for networked vehicles
Appendix C (informative) Template for technical requirements
Appendix D (informative) Technical response template
Bibliography
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Examples for identifying rules and basic principles and specifying their content
6 Overview
7 Rules
8 Basic principles
Appendix A (informative) Comparison of the structure numbering of this document with ISO 20077-2:
Appendix B (informative) Technical template for the design guidelines for networked vehicles
Appendix C (informative) Template for technical requirements
Appendix D (informative) Technical response template
Bibliography
1 Scope
This document sets out the rules and basic principles of the design guidelines for networked vehicles. This document applies to Class M and Class N vehicles.
2 Normative references
The contents of the following documents constitute the essential provisions of this document through the normative references in the text. Among them, note the date of the cited documents, only the date of the corresponding version applicable to this document; do not note the date of the cited documents, its latest version (including all the revision of the list) applicable to this document.
GB/T 41901.1 Road Vehicles - Methodology for Connected Vehicles - Part 1: General Information (GB/T 41901.1-2022, ISO 20077-1: 2017, MOD)
3 Terms and definitions
The terms defined in GB/T 41901.1 and the following terms and definitions apply to this document.
3.1
Basic principle
Design principles to be taken into account in the design of networked vehicles
3.2
Life cycle
The life cycle of a vehicle is the range of conditions that can be encountered throughout its life, including design, manufacture, customer use, maintenance and recycling. manufacturing, customer use, maintenance and recycling.
3.3
local diagnostic facilitator
A person who maintains communication with a remote technician, is able to operate as requested by the remote technician and answer the remote technician's questions, thus assisting in the diagnosis.
Note. The local diagnostic facilitator has the ability to understand and describe what is displayed on the on-board instruments and signalling devices.
3.4 Operator
Operator
A person who operates, controls or services a networked vehicle from within the vehicle. Example: Local diagnostic assistant -
3.5
Requester requesier
A company or legal entity that submits a request for a new function to the manufacturer of a connected vehicle.
Note 1: The vehicle manufacturer, as an after-sales service provider, is considered to be the demander when submitting a demand.
Note 2: If the vehicle manufacturer is the same as the web-enabled vehicle manufacturer, the internal requirements process can be used.
4 Abbreviations
The following abbreviations apply to this document.
5 Examples for identifying rules and basic principles and specifying their content
5.1 In this document, the rules and basic principles are expressed in the following way: x x NUM: the content of the rule or basic principle.
Note: Rules and basic principles may be followed by explanatory text.
6 Overview
6.1 Role of the design guidelines in the design process of networked vehicles
The purpose of this document is to provide a common body of rules and basic principles for the design (physical, documentation, support, etc.) of networked vehicles and their interfaces by specifying a common body of rules and basic principles. Documentation, support, etc.). Based on the rules and basic principles, the manufacturer of a connected vehicle should develop a methodology or process for designing a connected vehicle for a specific use case or scenario.
Each connected vehicle manufacturer typically standardises the way in which this design process works through collaborative methods and processes, as shown in Figure 1.
6.2 The main elements of the connected vehicle design guidelines
The Design Guidelines for Connected Vehicles contain the following elements (see Figure 2):
--Technical requirement templates for the complete description of the minimum information when proposing new requirement functions (see Appendix B and Appendix C);
--A system of rules and basic principles to guide the design of new net-linked vehicle functions (see Chapters 4 and 8);
--Technical response templates for the complete description of minimum information when responding to new requirement functions (see Appendix B and Appendix D).
6.3 Consideration of new net-linked vehicle features
The manufacturer of a connected vehicle applies the design guidelines for a connected vehicle by implementing the rules and basic principles of this document. The design guidelines apply to the design of, or design changes to, a connected vehicle, including direct or indirect communication between the vehicle and a third party (e.g. the vehicle operator, owner, service provider or other connected vehicle interested party).
New functional requirements for Internet-connected vehicles may arise from regulations. Standards and individual requirements, the requirements for new connected vehicle functionality should be precisely described by the requirement owner through a technical requirement template for all required elements (e.g. performance-related elements).
The design guidelines also apply to the design of new interfaces from regulatory requirements for remote communication in vehicles.
This document applies both to any demand-side requirements for new functions of a net-connected vehicle and to situations where existing functions need to be extended or used remotely. For vehicles produced in multiple stages, this document applies to all relevant manufacturers. Enabling new functions by simply adding new equipment without taking into account the existing design may not achieve the desired results, on the one hand because the new functions may uncontrollably interfere with the initial or existing functions and, on the other hand, because the original vehicle system does not usually have all the components required for the new functions. The basic principles of the design guidelines are intended to emphasise the treatment of these risks.
These rules and basic principles set out in this document are intended to address in an appropriate manner the internal risks to the connected vehicle resulting from new connected vehicle functionality, whether or not this functionality already exists, by taking measures to manage these risks, including but not limited to the following:
-- modifying the electronic systems (resources, etc.) of the existing connected vehicle to implement the new functionality.
--do not configure the new functionality
- - Configuring new functions, but only under certain conditions; - - Modifying other existing functions.
Non-technical measures (e.g. contractual measures) may also be used to manage risks, e.g. risks related to the degradation or disruption of existing functions or services.
7 Rules
7.1 Overview
The design guidelines for networked vehicles are based on remote access and should maintain the essential safety and protection of the vehicle throughout its life cycle. Therefore, this document contains two rules (R001 and R 002), which should be adopted by the manufacturers of Internet-connected vehicles in their design methods and processes, 7.2 Security-related rules
R 001, When designing new features of a connected vehicle, the manufacturer of the connected vehicle shall take into account the possible security risks. Features that affect safety should be handled in accordance with best safety practices.
When designing an Internet-connected vehicle, the manufacturer should consider the safety of the vehicle, its occupants, operators and other users over the lifetime of the network.
When designing new functions for connected vehicles, connected vehicle manufacturers should apply rule R 001.
This classification is determined by the inherent risk of the function of the connected vehicle, the risk in a particular situation or the risk of the operation of a particular function (the same action may lead to a different risk).
Examples of safety risks for vehicles in operation; Example 1: Impaired braking capability of the vehicle.
Example 2: Inappropriate function, e.g. bringing the vehicle to a sudden standstill while driving on the road
Example 3: Inappropriate functions that exceed the set parameters.
Examples of safety risks in stationary vehicles:
Example 4: False activation of the airbag when the front seats are occupied. Example 5: False activation of high voltage components when the high voltage battery is disconnected. Example 6: False activation of a component during maintenance work -
7.3 Protection-related rules
R 002, When designing new functions of a connected vehicle, the manufacturer of the connected vehicle shall take into account the possible risks of protectiveness. Features that affect protectiveness should be handled in accordance with best protectiveness practices.
The manufacturer of a connected vehicle is responsible for ensuring that the vehicle is protected throughout its life cycle,
8 Basic principles
8.1 Overview
The Netlink vehicle manufacturer shall always meet the rules set out in this document when applying the Basic Principles to its own design methods and processes. 8.2 General Basic Principles
BP 001: The manufacturer of a networked vehicle is responsible for the design of the networked vehicle
BP 002: The networked vehicle manufacturer is responsible for the design of all interfaces of the networked vehicle to enable communication with the networked vehicle and BP 003: The networked vehicle manufacturer is responsible for the implementation of the new energy requirements of the networked vehicle.
The NVM is responsible for the design of the NUV and its functions, so that the NVM is responsible for both the implementation of each function of the NUV and the consistency of the entire set of functions.
The following objective limitations may exist in the implementation of new functions of the connected vehicle according to the methodology specified in this document:
--Objective limitations on the usability of the functionality;
--Objective limitations of functional performance;
--objective limitations due to differences in vehicles, models, etc;
--objective limitations due to special market conditions.
8.3 Basic principles of life-cycle relevance
BP 004; The manufacturer of a connected vehicle is responsible for assessing the impact of new connected vehicle features on the vehicle throughout its life cycle.
The demander shall not be limited in accessing data regarding the availability and expected performance of the required net connected vehicle functionality over the full life cycle. The manufacturer of the connected vehicle should analyse the impact of integrating this functionality over the full lifecycle of the vehicle (see Figure 3) to identify possible incompatibilities that may arise in cases not mentioned by the demand side (e.g. during the manufacturing, maintenance or recycling phases), the results of which may lead to a reduction in the performance and usability of the required new functionality.
Appendix A (informative) Comparison of the structure numbering of this document with ISO 20077-2:2018
Appendix B (informative) Technical template for the design guidelines for networked vehicles
Appendix C (informative) Template for technical requirements
Appendix D (informative) Technical response template
Bibliography
Contents of GB/T 41901.2-2022
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Examples for identifying rules and basic principles and specifying their content
6 Overview
7 Rules
8 Basic principles
Appendix A (informative) Comparison of the structure numbering of this document with ISO 20077-2:
Appendix B (informative) Technical template for the design guidelines for networked vehicles
Appendix C (informative) Template for technical requirements
Appendix D (informative) Technical response template
Bibliography
