Detail of GB/T 41047-2021

Introduction of GB/T 41047-2021

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

Contents of GB/T 41047-2021

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