Method and system for managing life cycle information of automobile based on two-dimensional code

Abstract

The application discloses a kind of based on two-dimensional code's automobile life cycle information management method, based on vehicle VIN code supplementary additional information generation as unified information index vehicle identity two-dimensional code, solve the problem that traditional VIN code information capacity is insufficient, cannot be associated with full-quantity data.Establish the relational database with this two-dimensional code as primary key, the document data dispersed in each link are carried out centralized structured storage, realizes the overall management of information.Construction based on B / S architecture, provide Web-service interface remote server system, and for car factory, 4S shop, user etc. different identity is configured differentiating data access permission, so that multiple terminals can be flexibly, safely access system and carry out data operation.In data write operation, introduce concurrency control mechanism, effectively guarantee the data consistency when multiple users collaborative operation.The method can effectively integrate the fragmented information of automobile full life cycle, and can realize safe, efficient, scalable information sharing and business collaboration.

Description

Technical Field

[0001] This application relates to the field of automotive information management technology, specifically to a method and system for automotive lifecycle information management based on QR codes. Background Technology

[0002] Throughout the entire lifecycle of automobiles—from research and development, production, sales, and after-sales service—a vast amount of diverse and dispersed information is continuously generated, including design drawings, process documents, production problem records, sales invoices, and maintenance files. Currently, this information is typically identified primarily by the Vehicle Identification Number (VIN) and is stored in separate paper or electronic systems by suppliers, various departments within the automaker, and 4S dealerships, lacking unified integration and management.

[0003] Existing technical solutions have significant shortcomings. For example, while some solutions utilize QR codes to manage components, they cannot cover a wider range of documentation; others store documents for each stage separately and associate them with the vehicle, but information cannot be shared between systems, resulting in poor standardization and accuracy, and low efficiency in querying and updating. This leads to a break in the information chain throughout the vehicle's lifecycle, making it difficult to achieve data sharing and in-depth analysis, and failing to provide effective support for product improvement, precise services, and business decisions. Summary of the Invention

[0004] This application aims to address the problems of fragmented, difficult-to-coordinate, inconvenient-access, and poor-scalability information management in existing automotive lifecycle management technologies, and provides an information management method and system that enables unified management, secure sharing, efficient access, and elastic scalability. To achieve the above objectives, the technical solution adopted in this application includes:

[0005] In a first aspect, embodiments of this application provide a method for managing vehicle lifecycle information based on QR codes, including:

[0006] A vehicle identification QR code is generated based on the vehicle's VIN code and supplemented with additional information.

[0007] Establish a relational database with the vehicle identification QR code as the primary key to store document information in multiple stages and formats throughout the vehicle's lifecycle;

[0008] Construct a remote server system based on a B / S architecture. The remote server system includes an application server and a data server. The application server provides a Web-service interface that supports access from multiple terminals via a browser or HTTP protocol.

[0009] Access permissions are configured according to different user identities, and the creation, maintenance and / or query services for the relational database are provided through the Web-service interface;

[0010] Responding to user operation requests, performing data write and / or read operations according to permissions, and implementing concurrency control during data write to ensure data consistency.

[0011] Furthermore, the user identity includes vehicle manufacturer personnel, 4S store personnel, and / or end users;

[0012] Configure access permissions based on different user identities, specifically including:

[0013] Configure read and write permissions for production information tables for vehicle factory personnel;

[0014] Configure 4S store personnel with read-only access to the production information table and read / write access to the sales information table;

[0015] and / or

[0016] Configure end users' query permissions for the after-sales information table.

[0017] Furthermore, the data writing operation also includes:

[0018] Before writing, check if the target data is locked. If it is not locked, lock the data and execute the write. After the write is completed, synchronize and update the data consistency between the local and external systems.

[0019] Furthermore, it also includes:

[0020] Create a file attribute table for unstructured documents to uniformly manage multiple file formats and support online preview or retrieval.

[0021] Furthermore, it also includes:

[0022] After the user's operation times out or they actively log out, the Web-service connection and data lock are automatically released, and cached resources are cleared.

[0023] Secondly, embodiments of this application provide an automotive lifecycle information management system capable of implementing any of the foregoing automotive lifecycle information management methods, comprising:

[0024] The QR code generation module is used to generate a vehicle identification QR code based on the vehicle's VIN code and additional information.

[0025] The database module is used to store document information in multiple stages and forms throughout the vehicle's lifecycle, with the vehicle identification QR code as the primary key.

[0026] The server module adopts a B / S architecture, including an application server and a data server, wherein the application server provides a Web-service interface;

[0027] The access control module is used to configure data access permissions for users with different identities.

[0028] The operation control module is used to respond to user operation requests, perform data write and / or read operations according to permissions, and perform concurrency control during data writing to ensure data consistency.

[0029] Furthermore, the permission management module specifically includes:

[0030] Role classification unit, used to distinguish between car manufacturer personnel, 4S store personnel and / or end users;

[0031] The permission configuration unit is used to assign read / write or read-only permissions to the corresponding information tables for each role.

[0032] Furthermore, the operation control module also includes:

[0033] The lock management unit is used to detect and lock the target data before it is written, ensuring the exclusivity of the operation;

[0034] The synchronization unit is used to synchronize local and external system data after data updates.

[0035] Furthermore, the database module also includes:

[0036] The file attribute management unit is used to uniformly manage the attribute information of documents in various file formats;

[0037] The preview interface unit supports direct previewing of PDF, Word, and / or Excel files in a browser.

[0038] Furthermore, it also includes:

[0039] The session management module is used to monitor the user session status and automatically release resources after timeout or logout.

[0040] This application discloses a QR code-based method for managing vehicle lifecycle information. It generates a vehicle identity QR code as a unified information index based on supplementary information from the vehicle's VIN code, and links it to a standardized database and information system. This solves the problems of insufficient information capacity and inability to link the entire lifecycle of data from R&D to production to sales using traditional VIN codes. A relational database with this QR code as the primary key is established to centrally and structurally store and query documents scattered across various stages, achieving unified information management. A remote server system based on a B / S architecture and providing a Web-service interface is constructed, and differentiated data access permissions are configured for different roles such as car manufacturers, 4S stores, and users, enabling multiple terminals to flexibly and securely access the system for data operations. A concurrency control mechanism is introduced in data writing operations to effectively ensure data consistency during multi-user collaborative operations. This method can effectively integrate fragmented information throughout the entire vehicle lifecycle, enabling secure, efficient, and scalable information sharing and business collaboration. Attached Figure Description

[0041] Figure 1 A core flowchart of a vehicle lifecycle information management method based on QR codes provided in this application embodiment;

[0042] Figure 2 A detailed flowchart of a vehicle lifecycle information management method based on QR codes provided in this application embodiment;

[0043] Figure 3 A schematic diagram of the architecture of a QR code-based vehicle lifecycle information management system provided in this application embodiment;

[0044] Figure 4 A schematic diagram illustrating the use cases designed according to the user's identity and needs, dividing permissions into three categories, as provided in the embodiments of this application;

[0045] Figure 5 This is a schematic diagram of the module structure of a vehicle lifecycle information management system based on QR codes, provided as an embodiment of this application. Detailed Implementation

[0046] To enable those skilled in the art to better understand the technical solutions of this application, exemplary embodiments of this application are described below with reference to the accompanying drawings, including various details of the embodiments of this application to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description. Unless otherwise specified, the various embodiments of this application and the features within those embodiments can be combined with each other.

[0047] As used herein, the term "and / or" includes any and all combinations of one or more of the associated enumerated entries. The terminology used herein is for describing particular embodiments only and is not intended to limit the application. As used herein, the singular forms "a" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that when the terms "comprising" and / or "made of" are used herein, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as "connected" or "linked" are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0048] Unless otherwise specified, all terms used in this application (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It should also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this application, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this application.

[0049] refer to Figure 1 and Figure 2 One embodiment of this application proposes a method for managing vehicle lifecycle information based on QR codes. The core process of this method includes the following steps.

[0050] S1. Generate a vehicle identification QR code based on the vehicle VIN code and supplementary information.

[0051] First, at the beginning of the vehicle's lifecycle (such as when it rolls off the production line), a unique vehicle identification QR code is generated based on the vehicle's VIN code, supplemented with additional information not covered by the VIN, such as the production line number and production batch. This vehicle identification QR code will serve as the vehicle's digital ID in the entire lifecycle information system and will be printed on the vehicle's nameplate, manual, and other similar items.

[0052] S2. Establish a relational database with the vehicle identification QR code as the primary key to store document information in multiple stages and formats throughout the vehicle's lifecycle.

[0053] Next, a relational database is established. Using the generated vehicle identification QR code as the primary key, a main table for basic vehicle information is constructed. Then, entities that need to be managed in each stage of R&D, production, sales, and after-sales (such as "drawings," "process cards," "vehicle cards," "one-yuan problem management table," "repair records," etc.) and their relationships are abstracted to form an entity-relationship model. Based on this model, using the vehicle identification QR code as the foreign key, various subordinate tables and related tables are established, thereby constructing a database with a clear structure and well-defined relationships to centrally store document information from all stages.

[0054] S3. Construct a remote server system based on a B / S architecture. The remote server system includes an application server and a data server. The application server provides a Web-service interface that supports access from multiple terminals via a browser or HTTP protocol.

[0055] Then, build a remote server system. For example... Figure 3 As shown, the system adopts a three-tier B / S architecture. At the server layer, application servers and data servers are deployed. The application server, based on Web-service technology, encapsulates business logic such as data creation, maintenance, querying, and permission verification into standard service interfaces for publication. The data server manages the aforementioned relational database. This design makes the terminal layer extremely flexible; any device configured with a standard web browser (such as a workstation, laptop, mobile phone, or in-vehicle head unit) or supporting the HTTP protocol (such as a dedicated diagnostic instrument) can access the Internet through the network (transport layer) to access the services provided by the application server, thereby enabling data creation, maintenance, and querying.

[0056] S4. Configure access permissions according to different user identities, and provide creation, maintenance and / or query services for the relational database through the Web-service interface.

[0057] Access control is crucial for secure system collaboration. For example... Figure 4 As shown, users are categorized into three groups based on their business roles: vehicle manufacturer personnel, 4S store personnel, and end users, with differentiated permissions configured accordingly. For example, vehicle manufacturer personnel are granted read and write permissions to all production information tables; 4S store personnel are granted read-only permissions to relevant production information tables, as well as read and write permissions to sales and after-sales information tables; and end users are granted read-only permissions to query their own vehicle's after-sales information. After a user initiates an access request through their terminal, the server first verifies their identity and queries their permissions, thereby opening the corresponding data service interfaces and storage areas.

[0058] S5. Respond to user operation requests, perform data write and / or read operations according to permissions, and perform concurrency control during data writing to ensure data consistency.

[0059] Finally, the system responds to specific user operations. For read-heavy, infrequent write operations (such as 4S stores), a centralized version management mode and synchronous data writing are provided. When a user requests to write data (such as 4S store personnel entering repair records), the operation control module calls the corresponding service on the application server. The service first checks whether the target data has been locked by other users. Only after the data server confirms that the data is not locked and has exclusive operation privileges will the write operation be performed. Files stored locally in this information system can be edited directly; for files managed by external (remote) systems (such as car factory OA systems), after editing is completed in the external system, the relevant attribute data in the database of this system is synchronously updated through the interoperability interface, thereby ensuring the consistency of global data. When a user requests to read data, the system performs a consistency check on the data to be read to ensure that the latest version is obtained, and then outputs it directly or previews it through a browser. After the user's operation is completed, the system will actively or after a timeout release the connection and lock resources to ensure system security and efficient resource utilization.

[0060] For operations that periodically perform continuous writes (such as automotive production lines), a distributed version management model and asynchronous data writing are provided to avoid prolonged locking. Before each round of writing begins, a read is performed to check the differences between local and remote data. If there are no conflicts, only the newly changed data is committed for writing. If there are conflicts, the conflict is marked and resolution is guided. Then, the edited conflicting data and the conflict-free new changes are committed for writing. For the committed write, the differences between the data and the remote data are checked again. If there are no conflicts, the write is executed to update the data consistency. If there are still conflicts, the above operations are iteratively executed.

[0061] As business grows, traffic and data volume may surge. At this point, expanding the application server cluster and introducing a load balancer can distribute service requests, improving system responsiveness and stability. Simultaneously, the data server cluster can be expanded, employing distributed storage technology to manage massive amounts of data and support higher concurrent access performance.

[0062] For users who cannot be continuously online, the method described in this embodiment also provides an offline mode. Version management in offline mode adopts the aforementioned distributed version management model. Specifically, transmission and permission management in offline mode includes: providing corresponding keys based on different user permissions; during both reading and writing, packaging the entire database (e.g., production information table + sales information table + after-sales information table), and encrypting / decrypting only the data corresponding to the user's permissions within the full data packet based on different keys. This allows for flexible permission changes even when online conditions are unavailable, and significantly reduces the difficulty of data inspection and conflict resolution.

[0063] For unstructured documents, the method described in this embodiment manages documents in various file formats such as PDF, Word, and Excel by constructing a file attribute table, and provides online preview or calling interface. Users can directly view drawings, process cards and other documents in a browser without downloading special software, thereby greatly improving the convenience of access.

[0064] refer to Figure 5 One embodiment of this application proposes a QR code-based vehicle lifecycle information management system, which mainly includes the following functional modules.

[0065] (1) QR code generation module: used to generate vehicle identification QR codes based on vehicle VIN codes and additional information. It is deployed in the vehicle manufacturer's production information system and is responsible for generating vehicle identification QR codes according to rules.

[0066] (2) Database module: Used to store document information in multiple stages and forms throughout the vehicle's lifecycle, with the vehicle identification QR code as the primary key. Deployed on a data server, it includes various data tables and file attribute management units with the vehicle identification QR code as the primary key, used for structured storage of information and unified management of file attributes.

[0067] (3) Server Module: Adopting a B / S architecture, it includes an application server and a data server. The application server provides a Web-service interface. Specifically, it includes an application server cluster and a data server cluster. The application server contains a load balancing unit for distributing user requests; the data server supports a distributed storage unit. The application server provides business services through the Web-service interface.

[0068] (4) Access Control Module: Used to configure data access permissions for users with different identities. Deployed on the application server, it includes a role classification unit and an access control configuration unit, and is responsible for implementation. Figure 4 The fine-grained access control strategy is shown.

[0069] (5) Operation Control Module: This module responds to user operation requests, performs data write and / or read operations according to permissions, and performs concurrency control during data write to ensure data consistency. It is also deployed on the application server and includes a lock management unit and a synchronization unit, responsible for processing... Figure 2 The concurrency control and data consistency maintenance process is shown.

[0070] In addition, the system may include a session management module to monitor user session status and automatically release resources after timeout or logout to ensure system security.

[0071] refer to Figure 3When a car manufacturer engineer logs into the system (a QR code-based automotive lifecycle information management system) via the company intranet (transmission layer) using a workstation (terminal layer), the access control module identifies them as a "car manufacturer personnel" and grants them permission to edit the "One-Element Problem Management Table." When the engineer submits the edit, the lock management unit of the operation control module locks the record to prevent others from modifying it simultaneously. The lock is released after the editing is completed and synchronized to the database. Simultaneously, a car owner scans a QR code inside the car with their mobile phone to request a query for maintenance records. This request is distributed to an idle application server via the load balancing unit. The access control module identifies the "user" and only opens the query interface. The operation control module retrieves the latest record from the database and returns it to the car owner's mobile browser for display.

[0072] Overall, the beneficial effects of this application compared to the prior art mainly include:

[0073] (1) It has realized the integrated and standardized management of cross-link and multi-format information throughout the entire process of automobile research and development to scrapping, breaking down information silos.

[0074] (2) Through refined access control, it ensures that car manufacturers, 4S stores, users and other parties can access and operate related data flexibly and reliably under the premise of security, which promotes business process collaboration.

[0075] (3) The system architecture has good scalability and can smoothly cope with the ever-increasing data volume and access pressure through technologies such as server clusters, load balancing, and distributed storage, ensuring the long-term stable operation and efficient service of the system.

[0076] The aforementioned embodiments of the vehicle lifecycle information management method based on QR codes and the embodiments of the vehicle lifecycle information management system based on QR codes are identical or related in technical concept. They can be referred to each other in terms of technical details and technical effects, which will not be repeated here.

[0077] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and / or operation of possible implementations of systems, methods, and / or computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0078] Exemplary embodiments have been disclosed in this application, and while specific terminology has been used, it is used only and should be interpreted in a general illustrative sense and is not intended to be limiting. In some embodiments, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this application as set forth by the appended claims.

Claims

1. A method for managing vehicle lifecycle information based on QR codes, characterized in that, include: A vehicle identification QR code is generated based on the vehicle's VIN code and supplemented with additional information. Establish a relational database with the vehicle identification QR code as the primary key to store document information in multiple stages and formats throughout the vehicle's lifecycle; Construct a remote server system based on a B / S architecture. The remote server system includes an application server and a data server. The application server provides a Web-service interface that supports access from multiple terminals via a browser or HTTP protocol. Access permissions are configured according to different user identities, and the creation, maintenance and / or query services for the relational database are provided through the Web-service interface; Responding to user operation requests, performing data write and / or read operations according to permissions, and implementing concurrency control during data write to ensure data consistency.

2. The vehicle lifecycle information management method according to claim 1, characterized in that, The user identities include vehicle manufacturer personnel, 4S store personnel, and / or end users; Configure access permissions based on different user identities, specifically including: Configure read and write permissions for production information tables for vehicle factory personnel; Configure 4S store personnel with read-only access to the production information table and read / write access to the sales information table; and / or Configure end users' query permissions for the after-sales information table.

3. The vehicle lifecycle information management method according to claim 1, characterized in that, The data write operation also includes: Before writing, check if the target data is locked. If it is not locked, lock the data and execute the write. After the write is completed, synchronize and update the data consistency between the local and external systems.

4. The vehicle lifecycle information management method according to claim 1, characterized in that, Also includes: Create a file attribute table for unstructured documents to uniformly manage multiple file formats and support online preview or retrieval.

5. The vehicle lifecycle information management method according to claim 1, characterized in that, Also includes: After the user's operation times out or they actively log out, the Web-service connection and data lock are automatically released, and cached resources are cleared.

6. A vehicle lifecycle information management system capable of implementing the vehicle lifecycle information management method according to any one of claims 1-5, characterized in that, include: The QR code generation module is used to generate a vehicle identification QR code based on the vehicle's VIN code and additional information. The database module is used to store document information in multiple stages and forms throughout the vehicle's lifecycle, with the vehicle identification QR code as the primary key. The server module adopts a B / S architecture, including an application server and a data server, wherein the application server provides a Web-service interface; The access control module is used to configure data access permissions for users with different identities. The operation control module is used to respond to user operation requests, perform data write and / or read operations according to permissions, and perform concurrency control during data writing to ensure data consistency.

7. The vehicle lifecycle information management system according to claim 6, characterized in that, The permission management module specifically includes: Role classification unit, used to distinguish between car manufacturer personnel, 4S store personnel and / or end users; The permission configuration unit is used to assign read / write or read-only permissions to the corresponding information tables for each role.

8. The vehicle lifecycle information management system according to claim 6, characterized in that, The operation control module also includes: The lock management unit is used to detect and lock the target data before it is written, ensuring the exclusivity of the operation; The synchronization unit is used to synchronize local and external system data after data updates.

9. The vehicle lifecycle information management system according to claim 6, characterized in that, The database module also includes: The file attribute management unit is used to uniformly manage the attribute information of documents in various file formats; The preview interface unit supports direct previewing of PDF, Word, and / or Excel files in a browser.

10. The vehicle lifecycle information management system according to claim 6, characterized in that, Also includes: The session management module is used to monitor the user session status and automatically release resources after timeout or logout.

Images