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(規范性)數據共享接口報文規范
參考文獻
