This document specifies the general information of network connected vehicles. This document is applicable to M and N vehicles.
2 Normative References
The contents in the following documents, through normative references, constitute indispensable provisions of this document. Among them, for dated references, only the version corresponding to that date applies to the undated references in this document E, and the latest version (including all amendments) applies to this document.
GB/T41901.2 Road Vehicles - Methodology for Connected Vehicles - Part 2: Design Guidelines (GB/T41901.2-2022, ISO20077-2:2018, MOD)
3 Terms and definitions
The following terms and definitions defined in GB/T41901.2 are applicable to this document.
three point one
Extended vehicle
The vehicle system meets the specification requirements of the vehicle manufacturer, but is beyond the physical scope of road vehicles. It is composed of road vehicles, external interfaces, networking accessories and data communications generated through external interfaces.
Note 1: Network connected vehicles may not have network connected accessories.
Note 2: When the communication object is a non network connected accessory (such as road infrastructure and other traffic participants), the network connected vehicle is composed of road vehicles, external interfaces and data communication generated through external interfaces. The road infrastructure and other traffic participants are not network connected vehicles.
Note 3: The common application fields of connected vehicles are shown in Appendix B, and the methodological standards of connected vehicles are shown in Appendix c
three point two
Off board system
For road vehicles, the software and hardware outside the vehicle used to achieve the required functions through definition, design, development and/or manufacturing.
three point three
Connected Accessories
The external system provided by the networked vehicle manufacturer and used to realize the networked function.
three point four
Vehicle manufacturer
The manufacturer or company that issues the ex factory certificate or product conformity certificate of motor vehicles and bears the sole responsibility for vehicle product responsibility and vehicle identification number (VIN), and has nothing to do with the location of the assembly plant.
Functional requirement is the description given by the vehicle manufacturer to ensure necessary behaviors and/or results.
Note 2 Functional requirements are given by the organization responsible for product or process design.
three point seven
Function
A task, action, or activity performed to meet functional requirements.
Example: Start and stop the engine.
Note 2 The same function can be used for many different use cases.
three point eight
Use inverted use case
A sequence of interactions between one or more participants and related systems, which has specific goals and quantifiable results.
Example: Read all valid diagnostic trouble codes.
Note 1: "Read all valid diagnostic trouble codes" can be composed of the following interactions: communication initialization, vehicle identification, sending request to obtain diagnostic trouble code information, receiving diagnostic trouble code information, and communication end.
Note 2: The operator can be a human or a machine.
Note 3: In order to implement the design of networked vehicles, use cases need to be determined by appropriate scenarios and functional requirements.
three point nine
Use case set A group of use cases with the same goal and quantifiable results. Example: remote diagnosis, fleet management.
Note 1: The use case set itself can be re divided into different fields, in which different types of technical solutions may be generated. Some solutions are applicable to multiple fields.
Note 2: Network connected vehicles can be used in the use case set field of all vehicle interconnection, such as cooperative ITS, fleet management, remote diagnosis, vehicle sharing, etc.
three point one zero
Web service
Software system used for device interaction through network and with machine processable format interface.
4 Abbreviations
ExVe: ExtendedVehicle
FMS: Fleet Management System
ITS: Intelligent Transportation System R Day: Roadside Inspection
V21: Vehicle to Infrastructure V2V: Vehicle to Vehicle
5 General Information of Connected Vehicles
5.1 Concept of Allianz vehicles
5.1.1 Connected vehicle refers to all technical components capable of realizing vehicle functions, including external interfaces, as shown in Figure 1 and Figure 2. Figure 1 shows the overall concept, and Figure 2 shows the representative interfaces, including:
-- Physical connection interface;
-- Network service interface;
-- Wireless real-time communication interface;
Other interfaces, such interfaces have no standardization requirements.
5.1.2 Since the road vehicle is a part of the network connected vehicle, some physical connection interfaces of the road vehicle (see Figure 2) are also external interfaces of the network connected vehicle.
5.1.3 Network service interface is one of the representative external interfaces of network connected vehicles, as shown in Figure 2. The network service realizes the interaction between the network connected vehicle and the server through the network service interface. The server managed by the service provider does not belong to the network connected vehicle, and the service provider can communicate with the network connected vehicle through the server (see Figure 3).
5.2 Design limitation of network connected vehicle
The remote access function of the network connected vehicle shall not endanger the basic security of people or goods (inside or outside the vehicle) and the security of the vehicle in its entire life cycle (including information security).
Appendix A (Informative) Comparison between the structure number of this document and ISO 20077-1:2017
Appendix B (Informative) Expected application fields of network connected vehicles
B. 1 Network connected vehicle is not a special technical solution to solve specific needs (such as remote diagnosis). This technology extends conventional road vehicles to include out of vehicle systems. This technology can be applied to all fields requiring vehicle interconnection.
B. 2 There are six main expected application areas for connected vehicles (see Figure B.1).
Vehicle maintenance and upgrading. The typical use case set in this field is remote diagnosis, prediction, repair, online software upgrade, and the characteristics of this field are greatly affected by national or local regulations.
111. Vehicle inspection. The typical use case set in this field is remote RSI, and the feature of this field is that the inspection operator is supervised by the local authority.
Driving task support area. Typical use case sets in this field include V2V, V2I and communication supporting driving assistance and automatic driving. The characteristic of this field is that low delay communication is required.
11. Transportation management. A typical use case set in this area is remote FMS, which is characterized by the fleet as a whole.
11. Manufacturing and sales. The typical use case set in this field is vehicle remote diagnosis in the manufacturing process. The characteristic of this field is that the vehicle owner is still the vehicle manufacturer.
11. Non automotive sector. Typical use case sets in this field are infotainment, vehicle insurance, remote driver and driving survey. This field is characterized by a wide variety of use cases, usually from outside the automotive industry.
B. 3 In response to so many requirements, a good description of the use case set is crucial to the development of technical solutions based on networked vehicles.
Appendix C (Informative) Methodology standard for connected vehicles
C. Content of GB/T41901 series documents
GB/T41901 series documents contain various general specifications applicable to network connected vehicles. These documents do not contain any specific technical specifications.
This document is the first part of GB/T41901, including the basic definitions, concepts, examples and relevant standards of network connected vehicles.
GB/T41901.2 is used to guide the design and development of network connected vehicles, and its contents are introduced in C.2.2.
C. 2.1 Purpose of GB/T41901.2
The purpose of GB/T41901.2 is to guide the design of network connected vehicles and their external interfaces (physics, documents, support, etc.), so as to limit the risks related to security, protection and regulatory compliance, especially when fair competition is involved.
Most vehicle manufacturers have implemented effective quality management systems (for example, they have been certified to conform to ISO9001 or equivalent series of standards). Therefore, the design quality of network connected vehicles can be ensured through the following steps:
-- Based on the rules and basic principles in GB/T41901.2, vehicle manufacturers establish their own methods and processes to design networked vehicles, so as to meet the legal requirements of the target sales market; The vehicle manufacturer shall adopt the methods and processes required by its quality management system.
GB/T41901.2 is intended to guide the design process of network connected vehicles, and does not involve the process of obtaining information from the manufacturer of network connected vehicles to develop new business. However, in order to reduce risks, it is recommended that all parties who choose to apply GB/T41901.2 can adopt these processes.
1 Scope 2 Normative References 3 Terms and definitions 4 Abbreviations 5 General Information of Connected Vehicles Appendix A (Informative) Comparison between the structure number of this document and ISO 20077-1:2017 Appendix B (Informative) Expected application fields of network connected vehicles Appendix C (Informative) Methodology standard for connected vehicles
1 Scope
This document specifies the general information of network connected vehicles. This document is applicable to M and N vehicles.
2 Normative References
The contents in the following documents, through normative references, constitute indispensable provisions of this document. Among them, for dated references, only the version corresponding to that date applies to the undated references in this document E, and the latest version (including all amendments) applies to this document.
GB/T41901.2 Road Vehicles - Methodology for Connected Vehicles - Part 2: Design Guidelines (GB/T41901.2-2022, ISO20077-2:2018, MOD)
3 Terms and definitions
The following terms and definitions defined in GB/T41901.2 are applicable to this document.
three point one
Extended vehicle
The vehicle system meets the specification requirements of the vehicle manufacturer, but is beyond the physical scope of road vehicles. It is composed of road vehicles, external interfaces, networking accessories and data communications generated through external interfaces.
Note 1: Network connected vehicles may not have network connected accessories.
Note 2: When the communication object is a non network connected accessory (such as road infrastructure and other traffic participants), the network connected vehicle is composed of road vehicles, external interfaces and data communication generated through external interfaces. The road infrastructure and other traffic participants are not network connected vehicles.
Note 3: The common application fields of connected vehicles are shown in Appendix B, and the methodological standards of connected vehicles are shown in Appendix c
three point two
Off board system
For road vehicles, the software and hardware outside the vehicle used to achieve the required functions through definition, design, development and/or manufacturing.
three point three
Connected Accessories
The external system provided by the networked vehicle manufacturer and used to realize the networked function.
three point four
Vehicle manufacturer
The manufacturer or company that issues the ex factory certificate or product conformity certificate of motor vehicles and bears the sole responsibility for vehicle product responsibility and vehicle identification number (VIN), and has nothing to do with the location of the assembly plant.
three point five
Tonglian Vehicle Manufacturer
Vehicle manufacturer producing network connected vehicles.
three point six
Functional requirement is the description given by the vehicle manufacturer to ensure necessary behaviors and/or results.
Note 2 Functional requirements are given by the organization responsible for product or process design.
three point seven
Function
A task, action, or activity performed to meet functional requirements.
Example: Start and stop the engine.
Note 2 The same function can be used for many different use cases.
three point eight
Use inverted use case
A sequence of interactions between one or more participants and related systems, which has specific goals and quantifiable results.
Example: Read all valid diagnostic trouble codes.
Note 1: "Read all valid diagnostic trouble codes" can be composed of the following interactions: communication initialization, vehicle identification, sending request to obtain diagnostic trouble code information, receiving diagnostic trouble code information, and communication end.
Note 2: The operator can be a human or a machine.
Note 3: In order to implement the design of networked vehicles, use cases need to be determined by appropriate scenarios and functional requirements.
three point nine
Use case set A group of use cases with the same goal and quantifiable results. Example: remote diagnosis, fleet management.
Note 1: The use case set itself can be re divided into different fields, in which different types of technical solutions may be generated. Some solutions are applicable to multiple fields.
Note 2: Network connected vehicles can be used in the use case set field of all vehicle interconnection, such as cooperative ITS, fleet management, remote diagnosis, vehicle sharing, etc.
three point one zero
Web service
Software system used for device interaction through network and with machine processable format interface.
4 Abbreviations
ExVe: ExtendedVehicle
FMS: Fleet Management System
ITS: Intelligent Transportation System R Day: Roadside Inspection
V21: Vehicle to Infrastructure V2V: Vehicle to Vehicle
5 General Information of Connected Vehicles
5.1 Concept of Allianz vehicles
5.1.1 Connected vehicle refers to all technical components capable of realizing vehicle functions, including external interfaces, as shown in Figure 1 and Figure 2. Figure 1 shows the overall concept, and Figure 2 shows the representative interfaces, including:
-- Physical connection interface;
-- Network service interface;
-- Wireless real-time communication interface;
Other interfaces, such interfaces have no standardization requirements.
5.1.2 Since the road vehicle is a part of the network connected vehicle, some physical connection interfaces of the road vehicle (see Figure 2) are also external interfaces of the network connected vehicle.
5.1.3 Network service interface is one of the representative external interfaces of network connected vehicles, as shown in Figure 2. The network service realizes the interaction between the network connected vehicle and the server through the network service interface. The server managed by the service provider does not belong to the network connected vehicle, and the service provider can communicate with the network connected vehicle through the server (see Figure 3).
5.2 Design limitation of network connected vehicle
The remote access function of the network connected vehicle shall not endanger the basic security of people or goods (inside or outside the vehicle) and the security of the vehicle in its entire life cycle (including information security).
Appendix A (Informative) Comparison between the structure number of this document and ISO 20077-1:2017
Appendix B (Informative) Expected application fields of network connected vehicles
B. 1 Network connected vehicle is not a special technical solution to solve specific needs (such as remote diagnosis). This technology extends conventional road vehicles to include out of vehicle systems. This technology can be applied to all fields requiring vehicle interconnection.
B. 2 There are six main expected application areas for connected vehicles (see Figure B.1).
Vehicle maintenance and upgrading. The typical use case set in this field is remote diagnosis, prediction, repair, online software upgrade, and the characteristics of this field are greatly affected by national or local regulations.
111. Vehicle inspection. The typical use case set in this field is remote RSI, and the feature of this field is that the inspection operator is supervised by the local authority.
Driving task support area. Typical use case sets in this field include V2V, V2I and communication supporting driving assistance and automatic driving. The characteristic of this field is that low delay communication is required.
11. Transportation management. A typical use case set in this area is remote FMS, which is characterized by the fleet as a whole.
11. Manufacturing and sales. The typical use case set in this field is vehicle remote diagnosis in the manufacturing process. The characteristic of this field is that the vehicle owner is still the vehicle manufacturer.
11. Non automotive sector. Typical use case sets in this field are infotainment, vehicle insurance, remote driver and driving survey. This field is characterized by a wide variety of use cases, usually from outside the automotive industry.
B. 3 In response to so many requirements, a good description of the use case set is crucial to the development of technical solutions based on networked vehicles.
Appendix C (Informative) Methodology standard for connected vehicles
C. Content of GB/T41901 series documents
GB/T41901 series documents contain various general specifications applicable to network connected vehicles. These documents do not contain any specific technical specifications.
This document is the first part of GB/T41901, including the basic definitions, concepts, examples and relevant standards of network connected vehicles.
GB/T41901.2 is used to guide the design and development of network connected vehicles, and its contents are introduced in C.2.2.
C. 2.1 Purpose of GB/T41901.2
The purpose of GB/T41901.2 is to guide the design of network connected vehicles and their external interfaces (physics, documents, support, etc.), so as to limit the risks related to security, protection and regulatory compliance, especially when fair competition is involved.
Most vehicle manufacturers have implemented effective quality management systems (for example, they have been certified to conform to ISO9001 or equivalent series of standards). Therefore, the design quality of network connected vehicles can be ensured through the following steps:
-- Based on the rules and basic principles in GB/T41901.2, vehicle manufacturers establish their own methods and processes to design networked vehicles, so as to meet the legal requirements of the target sales market; The vehicle manufacturer shall adopt the methods and processes required by its quality management system.
GB/T41901.2 is intended to guide the design process of network connected vehicles, and does not involve the process of obtaining information from the manufacturer of network connected vehicles to develop new business. However, in order to reduce risks, it is recommended that all parties who choose to apply GB/T41901.2 can adopt these processes.
Contents of GB/T 41901.1-2022
1 Scope
2 Normative References
3 Terms and definitions
4 Abbreviations
5 General Information of Connected Vehicles
Appendix A (Informative) Comparison between the structure number of this document and ISO 20077-1:2017
Appendix B (Informative) Expected application fields of network connected vehicles
Appendix C (Informative) Methodology standard for connected vehicles
