1 Scope
This document specifies the general technical requirements for the automotive product recall process traceability system, the core metadata data synchronisation data sharing requirements, and the system performance and security requirements.
This document applies to the construction and provision of data services of the automotive product recall process traceability system by automotive product producers and related parties of the automotive product recall technical body.
2 Normative reference documents
The contents of the following documents constitute essential provisions of this document by means of normative references in the text. Where a reference document is dated, only the version corresponding to that date applies to this document; where a reference document is not dated, the latest version (including all amendment sheets) applies to this document.
GB/T 7408 Data elements and exchange formats Information exchange dates and times
GB 16735 Vehicle identification number (VIN) for road vehicles
GB 16737 World manufacturer identification code (WMI) for road vehicles
GB/T 26816 Core metadata for information resources
GB/T 39061 Automotive product recall numbering rules and numbering applications
3 Terminology and definitions
The following terms and definitions apply to this document.
3.1
recall plan
The specific implementation plan developed by the producer for a recall campaign.
Note: The implementation plan includes, but is not limited to, information on the producer, information on the recalled product. Description of the product range defects and possible consequences. In the back repair measures emergency disposal methods, product improvement measures recall notification methods.
[Source: GB/T 39603- -2020, 3.2, with modifications]
3.2
recall report
The act of submitting a recall plan by the producer in accordance with the provisions of the competent authority.
3.3
recall number
A standardised set of codes for the management of recall activities.
3.4
recall process tracing
The activity of tracking and tracing the implementation of a product recall by recording information about the time, place and measures taken to recall a defective product.
3.5
traceability system of recall process
Based on documentation, computer software. Hardware equipment and communication networks, etc., the information management system for data related to the traceability of the recall process.
3.6
enterprise terminal of traceability system
A system that carries out information collection and audit of product recall implementation and synchronizes data to the management terminal of the traceability system.
Note: The enterprise terminal of traceability system in this document is an integral part of the traceability system of the recall process of an automotive product, which is managed by the automotive product manufacturer.
3.7
Management terminal of traceability system
Receiving the information on the implementation of product recalls synchronised by the enterprise side of the traceability system. It also supports the monitoring and alarming of the operational status of the enterprise side of the traceability system.
Note: The management terminal of traceability system in this document is a component of the recall process of automotive products and is managed by the technical body of automotive product recall.
3.8
Service terminal of tracebilit system
A system that provides services such as querying, pushing and data sharing of recall information to government departments, industry enterprises, the public and other relevant parties.
Note: The service terminal of tracebilit system in this document is an integral part of the tracebilit system of the automotive product recall process, which is managed by the technical body of automotive product recall.
3.9
recall information management system of motor vehicle products
The system is used to record information about the producers of motor vehicle products, to collect, process and analyse defective clues, to carry out recall filing and form evaluation, and to publish recall-related information.
4 Abbreviations
The following abbreviations apply to this document.
HTTPS: Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS)
JSON :Scripting Language Object Notation
UTF 8: 8 bit Unicode Transformation Format
VIN: Vehicle Identification Number
5 General technical requirements
5.1 System Composition
The traceability system of the automotive product recall process consists of three parts: the enterprise side of the traceability system, the management side of the traceability system and the service side of the traceability system (see Figure 1). The enterprise side of the traceability system completes the collection and audit of the recall process information and synchronizes the data to the management side of the traceability system; the management side of the traceability system integrates the recall process information with the recall plan information in the automotive product recall information management system to form a complete vehicle The management side of the traceability system integrates the recall process information with the recall plan information in the automotive product recall information management system to form complete vehicle recall information and conduct statistical analysis; the service side of the traceability system provides recall information enquiry, pushing and sharing services for government departments, industry enterprises, the public and other relevant parties.
5.2 Functional requirements
5.2.1 Functional requirements for the enterprise side of the traceability system
5.2.1.1 The enterprise side of the traceability system shall obtain information on the recall process from distributors in a timely manner and realise data collection on the implementation of the recall activities of the enterprise.
5.2.1.2 The enterprise side of the traceability system shall check the VIN in the recall process information in accordance with the coding rules stipulated in GB16735, review whether the parts information and repair measures are consistent with the recall plan, and confirm the accuracy and validity of the recall process information.
5.2.1.3 The enterprise side of the traceability system shall regularly and automatically synchronise the recall process information to the management side of the traceability system and realise the uploading of data.
5.2.2 Functional requirements for the management side of the traceability system
5.2.2.1 The management side of the traceability system shall have the function of exchanging data with the enterprise side of the receiver's traceability system to obtain recall process information; the management side of the traceability system shall have the function of exchanging data with the automotive product recall information management system to realise the association between recall plan information and recall process information.
5.2.2.2 The management side of the traceability system shall carry out statistical analysis of the recall process data and generate statistical analysis reports to provide support for regulatory decision-making and social governance industry services.
5.2.2.3 The management side of the traceability system shall manage the enterprise side of the traceability system of the receiver, monitor the state of the data interface of the enterprise side of the traceability system and alarm the abnormal situation.
5.2.2.4 The traceability system management side shall control the user rights through user management and role management to ensure that different users can only access the data within their rights to ensure the security of the information.
5.2.3 Traceability system service side functional requirements
5.2.3.1 The service side of the traceability system shall provide the public with vehicle recall information enquiry services.
5.2.3.2 The service end of the traceability system shall push vehicle recall information to subscribers to improve the efficiency of vehicle recall information dissemination.
5.2.3.3 The service end of the traceability system may share relevant vehicle recall information with relevant parties.
6 Core metadata
The metadata description of the recall process traceability system shall comply with the requirements of GB/T 26816, and the core metadata description is shown in Appendix A.
7 Data synchronisation requirements
7.1 Data synchronization methods
The recall process information shall be transmitted between the enterprise side and the management side of the traceability system by means of a data interface.
7.2 Data synchronization content
The recall process information synchronized from the enterprise side of the traceability system to the management side shall include the following contents and requirements;
Recall number: It shall comply with the requirements of GB/T 39061;
The VIN of the recalled vehicle: it shall comply with the requirements of GB 16735 and GB 16737;
The time of the recall: should comply with the requirements of GB/T 7408;
Vehicle maintenance record number: should be accurate, true and unique;
The name or number of the dealer who carried out the recall: should be consistent with the recall record information;
Contact information of the recipient of the recall notice.
7.3 Timing of data synchronisation
After the recall of a vehicle has been implemented, the manufacturer shall synchronise the recall process information to the management side of the traceability system via the enterprise side of the traceability system no later than 24:00 hours the following day.
7.4 Data storage requirements
The data storage of the traceability system shall meet the following requirements:
a) The data on the enterprise side of the traceability system shall be stored for not less than 10 years;
b) The data on the management side of the traceability system shall be stored permanently;
c) The traceability system management should adopt distributed storage and provide backup.
7.5 Data synchronization interface requirements
7.5.1 Interface protocol
The data synchronization interface protocol of the traceability system shall meet the following requirements
a) HTTPS transmission protocol shall be adopted:
b) POST request method is adopted;
c) The data format shall be JSON format;
d) The character encoding shall be UTF-8.
7.5.2 Exchange process
The producer opens the data interface at the enterprise end of the traceability system and authorizes the data interface access rights to the management end of the traceability system.
The traceability system management end sends a data synchronization request message to the enterprise end of the traceability system, and the enterprise end of the traceability system shall respond to the request message within 58 to synchronize the recall process information to the traceability system management end. If the traceability system management side does not receive the reply message within 5 s, it shall interrupt the transmission and make a new request.
7.5.3 Message structure
The request message and reply message structure of data synchronization between the management side of the traceability system and the enterprise side of the traceability system shall conform to the provisions in Appendix B.
8 Data sharing requirements .
8.1 Data sharing mode
The service end of the traceability system shall provide vehicle recall information enquiry services to the public and share vehicle recall information to relevant parties by way of data interface.
8.2 Data sharing within the cellar
According to the requirements of laws and regulations and the actual needs of relevant parties, the service terminal of the tracking system can share the recall information of relevant vehicles, including the following
Content:
The name of the manufacturer;
Vehicle brand;
Vehicle model series;
Vehicle type;
Recall number;
Recall start date;
Vehicle VIN;
Description of the defect and its possible consequences;
Recall repair measures;
Whether or not the vehicle is subject to a recall.
8.3 Data sharing interface requirements
8.3.1 Interface protocol
The traceability system data sharing interface protocol shall be implemented in accordance with 7.5.1.
8.3.2 Exchange process
The traceability system service terminal opens the data interface and authorizes the data interface access rights to the data user.
The data user sends a data synchronization request message to the traceability system service terminal, which shall answer the request message within 38 seconds and synchronize the vehicle recall information to the data user. If the data user does not receive an answer within 3 s, it shall interrupt the transmission and make a new request.
The tracking system service terminal shall send the vehicle recall information to the data user, and return the success mark after the information is successfully sent.
8.3.3 Message structure
The data sharing request message and reply message structure between the data user and the service end of the tracing system shall conform to the provisions of Appendix C.
9 Performance requirements
9.1 Performance requirements of the enterprise side of the traceability system
The enterprise side of the traceability system shall meet the following requirements:
10 Safety requirements
Appendix A (informative) Core metadata for the recall process traceability system
Appendix B (normative) Data synchronisation interface message specification
Appendix C (prescriptive) Data Sharing Interface Message Specification
References
1 Scope
2 Normative reference documents
3 Terminology and definitions
4 Abbreviations
5 General technical requirements
6 Core metadata
7 Data synchronisation requirements
8 Data sharing requirements .
9 Performance requirements
10 Safety requirements
Appendix A (informative) Core metadata for the recall process traceability system
Appendix B (normative) Data synchronisation interface message specification
Appendix C (prescriptive) Data Sharing Interface Message Specification
1范围
本文件规定了汽车产品召回过程追溯系统的总体技术要求,核心元数据数据同步数据共享要求，以及系统性能和安全要求。
本文件适用于汽车产晶召回技术机构汽车产品生产者以及相关方开展汽车产晶召回过程追溯系统的建设和提供数据服务。
2规范性引用文件
下列文件中的内容通过文中的规范性引用而构成本文件必不可少的条款。其中,注日期的引用文件,仅该日期对应的版本适用于本文件;不注日期的引用文件,其最新版本(包括所有的修改单)适用于本文件。
GB/T 7408数据元和交换格式信息交换日 期和时间表示法
GB 16735道路车辆车辆识别代号(VIN)
GB 16737道路车辆世界制造厂识别代号(WMI)
GB/T 26816信息资源核心元数据
GB/T 39061汽车产品召回编号规则及编号应用
3术语和定义
下列术语和定义适用于本文件.
3.1
召回计划
recall plan
生产者针对召回活动所制定的具体实施方案。
注:实施方案内容包括但不限于生产者信息、召回产晶信息.开回产品范围缺陷描述及可能造成的后果。在回维修措施应急处置方法、产品改进措施召回通知方式等。
[来源:GB/T 39603- -2020,3.2,有修改]
3.2
召回备案
recall report
生产者按照主管部门的规定,提交召回计划的行为。
3.3
召回编号
recall number
用于召回活动管理的一组规范化编码。
3.4
召回过程追溯recall process tracing
通过记录存在缺陷的产品实施召回的时间、地点、措施等信息,追踪和溯源产品召回实施情况的活动。
3.5
召回过程追溯系统traceability system of recall process
基于文件记录、计算机软件.硬件设备和通信网络等,对召回过程追溯相关数据进行信息化管理的系统。
3.6
追溯系统企业端
enterprise terminal of traceability system
开展产品召回实施信息采集与审核,并向追潮系统管理端同步数据的系统。
注:本文件中的追测系统企业端是汽车产品召回过程追潮系统的组成部分,由汽车产品生产者管理。
3.7
追溯系统管理端management terminal of traceability system
对追溯系统企业端同步的产品召回实施信息进行接收.校验、存储和统计,支持对接入的追溯系统企业端运行状态进行监测及报警等活动的系统。
注:本文件中的追潮系统管理端是汽车产品召回过程迫溯系统的组成部分，由汽车产晶召回技术机构管理。
3.8
追溯系统服务端service terminal of tracebilit system
向政府部门行业企业、社会公众等相关方提供召回信息查询、推送和数据共享等服务的系统。
注:本文件中的追溯系统服务端是汽车产品召回过程追溯系统的组成部分,由汽车产品召回技术机构管理.
3.9
汽车产品召回信息管理系统
recall information management system of motor vehicle products
用于备案汽车产品生产者信息,采集、处理与分析缺陷线索,开展召回备案及形式评估,发布召回相关信息的系统。
4缩略语
下列缩略语适用于本文件。
HTTPS:超文本传输安全协议(Hyper Text Transfer Protocol over Secure Socket Layer)
JSON :脚本语言对象标记(JavaScript Object Notation)
UTF- 8:8位统一可变长度字符编码(8 bit Unicode Transformation Format)
VIN:车辆识别代号(Vehicle Identification Number)
5总体技术要求
5.1系统构成
汽车产品召回过程追溯系统由追朔系统企业端、追溯系统管理端和追溯系统服务端三部分构成(见图1)追溯系统企业端完成召回过程信息的收集、审核以及向追潮系统管理端的数据同步;追溯系统管理端将召回过程信息与汽车产品召回信息管理系统中召回计划信息进行整合,形成完整的车辆召回信息并进行统计分析;追溯系统服务端面向政府部门、行业企业、社会公众等相关方提供召回信息查询、推送与共享服务。
5.2功能要求
5.2.1追溯系統企业端功能要求
5.2.1.1追溯系统企业端应从经销商处及时获取召回过程信息,实现本企业召回活动实施情况数据收集。
5.2.1.2追溯系统企业端对召回过程信息中的VIN应按照GB16735规定的编码规则进行校验,对零部件信息维修措施等是否与召回计划--致进行审核,确认召回过程信息的准确性和有效性。
5.2.1.3追溯系统企业端应定期、自动向追溯系统管理端同步召回过程信息,实现数据的上传。
5.2.2追溯系统管理端功能要求
5.2.2.1追溯系统管理端应具备与接人的追溯系统企业端进行数据交换的功能,获取召回过程信息;追溯系统管理端应具备与汽车产品召回信息管理系统进行數据交换的功能,实现召回计划信息与召回过程信息的关联。
5.2.2.2追溯系统管理端应对召回过程数据进行统计分析,生成数据统计分析报表,为监管决策、社会治理行业服务提供支撑。
5.2.2.3追溯系统管理端应对接人的追溯系统企业端进行统管理,对追溯系统企业端数据接口状态进行监测并对异常情况进行报警。
5.2.2.4追溯系统管理端应通过用户管理和角色管理对用户权限进行控制,保证不同用户仅能访向其权限范围内的数据,确保信息的安全性。
5.2.3追溯系统服务端功能要求
5.2.3.1追溯系统服务端应向社会公众提供车辆召回信息查询服务。
5.2.3.2追溯系统服务端应向订阅用户推送车辆召回信息,提高车辆召回信息传播效率。
5.2.3.3追溯系统服务端可向相关方共享相关车辆召回信息。
6核心元数据
召回过程追溯系统元数据描述应符合GB/T 26816的要求,核心元数据描述见附录A.
7数据同步要求
7.1 数据同步方式
追溯系统企业端和管理端之间通过数据接口方式传输召回过程信息。
7.2数据同步内容
追溯系统企业端向管理端同步的召回过程信息应包括的内容及要求如下;
召回编号:应符合GB/T 39061的要求;
实施召回的车辆VIN:应符合GB 16735和GB 16737的要求;
实施召回的时间:应符合GB/T 7408的要求;
车辆维修记录编号:应准确、真实且具有唯-性;
实施H回的经销商名称或编号:应与召回备案信息保持-致;
召回通知接收人的联系方式。
7.3数据同步时效
车辆召回实施完成后,生产者应最迟不超过次日24时,通过追溯系统企业端将召回过程信息同步至追溯系统管理端。
7.4数据存储要求
追潮系统数据存储满足下列要求:
a)追溯系统企业端数据应保存不低于10年;
b)追溯系统管理端数据应永久保存;
c)追溯系统管理应采用分布式存储,并提供备份。
7.5数据同步接口要求
7.5.1接口协议
追溯系统数据同步接口协议应满足:
a)采用HTTPS传输协议:
b)采用POST请求方式;
c)数据格式为JSON格式;
d)字符编码采用UTF-8。
7.5.2交换过程
生产者在追潮系统企业端开通数据接口,向追溯系统管理端授权数据接口访问权限。
追溯系统管理端向追溯系统企业端发送数据同步请求报文,追溯系统企业端应在58内应答该请求报文,向追溯系统管理端同步召回过程信息。追溯系统管理端5s内未收到应答报文,应中断发送后重新进行一次请求。
7.5.3报文结构
追溯系统管理端与追溯系统企业端的数据同步请求报文和应答报文结构应符合附录B的规定。
8数据共享要求 .
8.1数据共享方式
追溯系统服务端应向社会公众提供车辆召回信息查询服务,并通过数据接口方式向相关方共享车辆召回信息。
8.2数据共享内窨
追溯系统服务端根据法律法规要求和相关方实际需求,可共享相关车辆的召回信息,包括以下
内容:
生产者名称;
一车辆品牌;
车型系列;
车辆类型;
召回编号;
召回开始时间;
车辆VIN;
缺陷描述及可能造成的后果;
召回维修措施;
车辆是否实施召回。
8.3数据共享接口要求
8.3.1接口协议
追溯系统数据共享接口协议应按7.5.1执行。
8.3.2交换过程
追溯系统服务端开通数据接口,并向数据用户授权数据接口访问权限。
数据用户向追溯系统服务端发送数据同步请求报文,追溯系统服务端应在38内应答请求报文,向数据用户同步车辆召回信息。数据用户3 s内未收到应答报文,应中断发送后重新进行一次请求。
追溯系统服务端将车辆召回信息发送至数据用户,信息发送成功后返回成功标识。
8.3.3报文结构
数据用户与追潮系统服务端的数据共享请求报文和应答报文结构应符合附录C的规定。
9性能要求
9.1追溯系统企业端性能要求
追溯系统企业端应满足下列要求:
10安全要求
附录A（资料性)召回过程追溯系统核心元数据
附录B(规范性)数据同步接口报文规范
附录C(规范性)数据共享接口报文规范
参考文献
