Vehicle all-in-one machine data storage method

Abstract

The invention provides a vehicle all-in-one machine data storage method which comprises the steps that an uploaded standardized data file is received to a specified directory, and the standardized data file comprises all-in-one machine parameters arranged according to a preset sequence; verifying each piece of data in the standardized data file; if the verification fails, recording error line information to an abnormal record table and terminating the process; after verification is passed, all-in-one machine objects are constructed in sequence, user identification card data / Bluetooth data are associated, all-in-one machine-user identification card binding relation data, vehicle machine data, equipment grouping data and all-in-one machine binding data are created, and the associated data sub-tables are stored in the corresponding database sub-tables in sequence. According to the method, the compatibility problem of multi-supplier data is solved through standardized uploading and sequential storage, the data consistency is ensured through step-by-step associated storage, and dirty data is avoided as much as possible.

Description

Technical Field

[0001] This application relates to the field of vehicle information management technology, and in particular to a method for data entry into a vehicle integrated machine. Background Technology

[0002] With the rapid development of intelligent connected vehicles, the vehicle infotainment system, as a core component of the in-vehicle infotainment system, needs to establish a complete data mapping relationship between the vehicle and the user in a cloud-based backend database to achieve functions such as vehicle control and user identity verification. Currently, the cloud-based storage of vehicle infotainment system data mainly relies on the following two methods:

[0003] 1. Supplier direct database write mode

[0004] Different vendors can directly access the cloud database to write data, but this has the following significant drawbacks:

[0005] (1) Inconsistent data standards: Each supplier uses independent units (such as date format and field naming), which makes it easy to parse the data incorrectly.

[0006] (2) Security risks: Suppliers directly operating the database may cause security problems such as accidental deletion and injection attacks.

[0007] (3) High rate of dirty data: lack of unified verification mechanism, duplicate data is directly entered into the database.

[0008] 2. Scheduled Batch Script Import Mode

[0009] While triggering a script to parse files at fixed intervals, the following shortcomings still exist:

[0010] (1) Lack of verification mechanism: Only the basic format is verified, and the logical relationship between fields is not verified.

[0011] (2) Disordered entry order: The data was not written in the order of device dependencies, resulting in the break of foreign key associations.

[0012] (3) Insufficient flexibility: It only supports scheduled tasks and cannot respond to urgent data entry needs. Summary of the Invention

[0013] This application aims to solve at least one technical problem existing in the prior art mentioned above, and proposes a method for data entry into a vehicle integrated machine.

[0014] This application provides a method for importing vehicle integrated machine data into a database, including:

[0015] Receive the uploaded standardized data file to the specified directory, wherein the standardized data file contains all-in-one machine parameters arranged in a preset order;

[0016] Validate each piece of data in the standardized data file; if the validation fails, record the error line information to the exception record table and terminate the process.

[0017] After verification, the all-in-one machine object is constructed in sequence and associated with user identification card data / Bluetooth data. All-in-one machine-user identification card binding relationship data, vehicle data, device grouping data and all-in-one machine binding data are created, and the associated data is stored in the corresponding database tables in sequence.

[0018] Furthermore, constructing the all-in-one machine object includes:

[0019] If the device corresponding to the device report number does not exist in the basic all-in-one machine table, a new all-in-one machine object is created and the device number and creation information are written in; if it exists, the all-in-one machine object is directly associated with it.

[0020] Furthermore, associated Bluetooth data includes:

[0021] If the Bluetooth physical address does not exist in the basic Bluetooth table, a new Bluetooth object is created and associated with the security chip code.

[0022] After associating the security chip code, the Bluetooth object is saved to the basic Bluetooth table, and then the Bluetooth physical address is written to the corresponding all-in-one machine object.

[0023] Furthermore, the associated user identification card data includes:

[0024] If the user identification card data corresponding to the mobile user identification code does not exist in the basic user identification card table, then create a new user identification card object and write the mobile user identification code into it;

[0025] Save the user identification card object to the basic user identification card table, and write the user identification card data to the corresponding all-in-one machine object.

[0026] Further, create all-in-one machine-user identification card binding relationship data, including:

[0027] If the all-in-one machine binding table does not contain the relationship data corresponding to the all-in-one machine report number, then create a new binding relationship object and write the all-in-one machine report number, mobile user identification code, version number, deletion flag information and creation / update time.

[0028] Save the binding relationship object to the all-in-one machine binding table.

[0029] Furthermore, create vehicle-mounted data, including:

[0030] If the vehicle data corresponding to the vehicle serial number does not exist in the basic vehicle data table, a new vehicle data object is created and the vehicle hardware version number, vehicle software version number, vehicle serial number, deletion flag and creation / update time are written in.

[0031] Save the vehicle infotainment object to the basic vehicle infotainment table.

[0032] Further, device grouping data is created, including:

[0033] Record the project group data of the all-in-one machine;

[0034] Record the data of the project group of the vehicle's infotainment system.

[0035] Further, create all-in-one machine binding data, including:

[0036] If the vehicle group code is empty, a random universally unique identifier is generated as the group code;

[0037] Create separate integrated machine group objects and vehicle-mounted machine group objects. Write the group code, integrated machine report number, creation time and device type into the integrated machine group object, and write the group code, vehicle-mounted machine serial number, creation time and device type into the vehicle-mounted machine group object.

[0038] Ensure consistency of group codes between the integrated machine group objects and the vehicle-mounted machine group objects.

[0039] Furthermore, the standardized data file requires the all-in-one machine parameters to be arranged in the following order:

[0040] All-in-one machine part number, all-in-one machine serial number, vehicle machine serial number, mobile user identification code;

[0041] The verification methods for validating each piece of data in a standardized data file include:

[0042] Non-empty verification, the relevant verification parameters include one or more of the following: all-in-one machine report number, all-in-one machine serial number, vehicle machine serial number, mobile user identification code, mobile device identification code, integrated circuit card identification code, vehicle network card operator, production line production date and shipping destination;

[0043] and / or

[0044] Field duplication verification involves one or more of the following parameters: vehicle serial number, mobile device identification code, mobile user identification code, integrated circuit card identification code, and Bluetooth physical address.

[0045] Furthermore, it also includes two execution modes:

[0046] Scheduled task mode: Scans directory files at fixed intervals and automatically inserts them into the database;

[0047] Manual trigger mode: Receive supplier requests in real time and execute data entry.

[0048] This application provides a method for importing vehicle integrated machine data into a database. It solves the compatibility problem of multi-supplier data through standardized uploading and sequential data import, and ensures data consistency through step-by-step associated storage, thereby avoiding dirty data as much as possible. Attached Figure Description

[0049] Figure 1 A core flowchart of a vehicle integrated machine data entry method provided in this application embodiment;

[0050] Figure 2 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0051] To enable those skilled in the art to better understand the technical solutions of this application, exemplary embodiments of this application are described below in conjunction with 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.

[0052] Where there is no conflict, the various embodiments of this application and the features thereof may be combined with each other.

[0053] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0054] 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 intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that when the terms “comprising” and / or “made of” are used in this specification, 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.

[0055] Unless otherwise specified, all terms used herein (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 the 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 herein.

[0056] To meet supplier needs, different integrated unit (a vehicle infotainment system installed in the car's center console, primarily for communication between the driver and vehicle) suppliers can upload data to the cloud platform via file upload using the same method. A scheduled task then inputs the supplier-uploaded data into the cloud platform's backend system. However, existing technologies suffer from technical shortcomings mentioned in the background section, such as inconsistent data standards, high rates of dirty data, lack of verification mechanisms, and insufficient flexibility. Therefore, this application proposes a method for importing vehicle integrated unit data. This method establishes a standard that allows different suppliers to import relevant data from various vehicle integrated units under a unified dimension via file upload. It aims to address the verification process before data import and the order of data import into different tables. Data verification serves two purposes: preventing data duplication and verifying whether the information conforms to the standard. The order of data import is also crucial; changing the order may lead to the generation of dirty data.

[0057] The proposed method for data entry into a vehicle integrated unit proposed in this application mainly consists of two stages. The first stage is the file upload stage, in which the supplier uploads the relevant data files to a fixed directory. The data must be written in a specific order, such as the integrated unit warranty number, integrated unit serial number, vehicle serial number, and mobile user identification code. If the order of the data is inconsistent with the specified order, inconsistencies between fields and data may occur. The second stage is the data entry stage, which is further divided into three sub-stages: verification, data entry, and fault reporting processing. Fault reporting processing is distributed within the verification and data entry processes. This data entry method can be implemented automatically or manually. The supplier can place the files in a certain directory in advance and wait for the automatic data entry operation at a fixed time each day. Alternatively, if the data entry is urgently needed, the method can be manually invoked after the supplier submits the data to complete the data entry operation. The main parameters involved in this data entry method are shown in Table 1.

[0058] Table 1 Vehicle Integrated Unit Data Parameter Table

[0059]

[0060] The database tables involved in this application include an exception record table, a basic Bluetooth table, a basic ATB (all-in-one) table, a basic SIM card (user identification card) table, an ATB binding table, a basic vehicle infotainment system table, and a basic grouping table. These different database tables record information about different parts and their relationships to ensure that the entered information can cover all inputs and information that is effective later.

[0061] refer to Figure 1 One embodiment of this application proposes a method for importing vehicle integrated machine data into a database, which may specifically include the following steps.

[0062] Step 1: First, the supplier enters information for each field according to a fixed template. Information for one or multiple all-in-one machines can be entered. This information is then uploaded to a designated server file directory. After a certain time, the data entry process begins. If the data entry is urgent, the supplier can be waited for and the data can be manually entered into the database.

[0063] Step 2: The next step is the cloud-based processing flow.

[0064] The first step is to validate the parameters. This process involves validating each piece of data. The parameters that need to be validated for non-emptiness are atbid, atbSn, iviPdsn, imsi, imii, iccid, suppler, eolDate, and destination.

[0065] Among them, eolDate needs to be formatted to determine whether it meets the format "yyyy-mm-dd". If there is any empty information, the field is recorded in an error message list and the subsequent field duplication checks are performed.

[0066] This field duplication check primarily verifies whether certain identical fields in a file are duplicated. The method involves adding the corresponding parameters to a list for each piece of information entered. During the import of that data, it checks if the parameters match those of previously entered identical fields. The parameters involved in this duplication check include iviPdsn, imei, imsi, iccid, and bleMac. If any of these are duplicated, the corresponding field information is added to the error message list. The error message list is then checked for errors; if any are found, an error is reported, and the relevant information is entered into an exception log table, specifically recording which row's data is problematic. The program then terminates. If the check passes, the subsequent data import process continues.

[0067] Step 3: Construct ATB data (all-in-one device data). This process requires first checking the database (here referring to the basic all-in-one device table) to see if a device corresponding to the ATBId exists. If it does not exist, an ATB object is created, and information such as the device number, creation date, and creator is written into it. If it exists, the ATB object is retrieved directly. Then, the SIM card information and Bluetooth-related information are written into the ATB object (all-in-one device object).

[0068] Step 4: Determine if Bluetooth-related information exists in the input parameters. If a Bluetooth MAC address (physical address) exists, first search the basic Bluetooth table for the Bluetooth data information based on the Bluetooth MAC address. If it exists, directly retrieve the Bluetooth object. If it does not exist, create a Bluetooth object and write its Bluetooth MAC address and creation time, etc. Then, write the security chip information (SIED) from the input parameters into the Bluetooth object. After information injection, save the Bluetooth object to the basic Bluetooth table. After successful saving, write the Bluetooth MAC information into the corresponding ATB object to establish a connection between the two. If Bluetooth information does not exist, skip this step and proceed to the next step.

[0069] Step 5: Save the ATB object to the database, then create the SIM card information. In this process, first, the database (here, the basic SIM card table) is checked for the existence of the corresponding SIM card information using the IMSI information. If it doesn't exist, a SIM card object is created, and the IMSI information, including the IMSI information, logical deletion flag (referred to as the deletion flag), and creation time, is written to it. If it exists, the SIM card object is retrieved. Then, the ICCID and carrier information from the input parameters are injected into the SIM card object. After these operations are completed, the SIM card object is saved to the basic SIM card table, and the SIM card information is written to the corresponding ATB object.

[0070] Step 6: Create ATB and SIM card binding relationship data. The main purpose of this process is to allow you to find the bound SIM card using the ATB serial number later. This process first checks the `fittings` table (all-in-one device binding table) for the ATBId to see if the corresponding relationship information for the Tbox exists. If not, a `fittings` object (binding relationship object) is created, and the creation time and deletion flag information are written into it. If the Tbox exists, the `fittings` object is retrieved directly. After obtaining the `fittings` object, information such as ATBId, IMSI, version number, and update time are written into it. After the information injection is complete, the object is saved to the all-in-one device binding table.

[0071] Step 7: Create vehicle infotainment data. This process first checks the basic vehicle infotainment table for the input iviPdsn to see if corresponding vehicle infotainment information exists. If not, a new IPDA object (vehicle infotainment object) is created, and information such as iviPdsn, deletion flag, and creation time are written into it. If the information exists, the IPDA object is retrieved directly. After retrieving the vehicle infotainment object, information such as the vehicle infotainment hardware version number, vehicle infotainment software version number, and update time are injected into the vehicle infotainment object. After these operations are completed, the vehicle infotainment object is saved to the basic vehicle infotainment table.

[0072] Step 8: Create a device account group table (device grouping data). This process requires creating two databases: one to record the ATB project group data, and the other to record the IPDA project group data. The main purpose of this table is to distinguish the project group information of major vehicle parts. After a part is replaced and no longer linked to a vehicle, this data can be used to identify the project to which the part belongs.

[0073] Step 9: Create integrated device binding data. During this process, a new random serial number UUID (Universally Unique Identifier) ​​needs to be generated. First, check if the vehicle group ID (vehicleGroup) in the input parameters is empty. If it is not empty, it means the vehicle data has already been entered into the database, so change the groupId (group code) to the vehicle group ID; otherwise, use the randomly generated UUID directly. Then, create an atbGroup object (integrated device grouping object) and an iviGroup object (vehicle-mounted device grouping object). Inject the groupId, atbId, creation time, and device type into the atbGroup, and then inject the groupId, iviPdsn, creation time, and device type into the iviGroup. It is essential to ensure that the groupId in both objects (atbGroup and iviGroup) is consistent to avoid anomalies during the subsequent parts replacement process.

[0074] Step 10: After successfully generating the atbGroup and iviGroup objects, save the corresponding information for atb and ivi to the database.

[0075] This application supports the input of standard dimensional data for all all-in-one machines, meeting the needs of different all-in-one machine suppliers. It also isolates operational permissions; suppliers only need to upload data, and subsequent program calls are only authorized by the cloud platform. Furthermore, customers can query publicly available all-in-one machine information through the app.

[0076] This application can accommodate various supplier needs. If the all-in-one machine information needs to be entered urgently, the relevant information can be entered manually. If the entry requirement is not urgent, the relevant files can be uploaded and the scheduled task can be completed. If the supplier has missed any information, this application can also print out the specific row numbers to notify the supplier of which data has an anomaly and what kind. The supplier can then conduct the corresponding checks and ultimately complete the correct data entry.

[0077] Based on the same inventive concept, embodiments of this application also provide an electronic device. Figure 2 This is a structural block diagram of an electronic device provided in an embodiment of this application. Figure 2As shown in the embodiments of this application, an electronic device includes: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, enable the one or more processors to implement any of the vehicle integrated machine data entry methods described in the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory, configured to enable information interaction between the processor and the memory.

[0078] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0079] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0080] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0081] This application also provides a computer-readable medium. The computer-readable medium stores a computer program, which, when executed by a processor, implements the steps of any of the vehicle integrated machine data entry methods described in the above embodiments. The computer-readable storage medium can be volatile or non-volatile.

[0082] This application also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described vehicle integrated machine data entry method.

[0083] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0084] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0085] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0086] The computer program instructions used to perform the operations of this application may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuits, such as programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), are personalized by utilizing the status information of the computer-readable program instructions. These electronic circuits can execute the computer-readable program instructions to implement various aspects of this application.

[0087] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0088] Various aspects of this application are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0089] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0090] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0091] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and 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.

[0092] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for general illustrative purposes only and should not be construed as limiting. In some embodiments, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in connection with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in connection 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 data entry into a vehicle integrated machine database, characterized in that, include: Receive the uploaded standardized data file to the specified directory, wherein the standardized data file contains all-in-one machine parameters arranged in a preset order; Validate each piece of data in the standardized data file; if the validation fails, record the error line information to the exception record table and terminate the process. After verification, the all-in-one machine object is constructed in sequence and associated with user identification card data / Bluetooth data. All-in-one machine-user identification card binding relationship data, vehicle data, device grouping data and all-in-one machine binding data are created, and the associated data is stored in the corresponding database tables in sequence.

2. The warehousing method according to claim 1, characterized in that, The construction of the all-in-one machine object includes: If the device corresponding to the device report number does not exist in the basic all-in-one machine table, a new all-in-one machine object is created and the device number and creation information are written in; if it exists, the all-in-one machine object is directly associated with it.

3. The warehousing method according to claim 1, characterized in that, Associated Bluetooth data, including: If the Bluetooth physical address does not exist in the basic Bluetooth table, a new Bluetooth object is created and associated with the security chip code. After associating the security chip code, the Bluetooth object is saved to the basic Bluetooth table, and then the Bluetooth physical address is written to the corresponding all-in-one machine object.

4. The warehousing method according to claim 1, characterized in that, Associated user identification card data, including: If the user identification card data corresponding to the mobile user identification code does not exist in the basic user identification card table, then create a new user identification card object and write the mobile user identification code into it; Save the user identification card object to the basic user identification card table, and write the user identification card data to the corresponding all-in-one machine object.

5. The warehousing method according to claim 1, characterized in that, Create all-in-one machine - user identification card binding relationship data, including: If the all-in-one machine binding table does not contain the relationship data corresponding to the all-in-one machine report number, then create a new binding relationship object and write the all-in-one machine report number, mobile user identification code, version number, deletion flag information and creation / update time. Save the binding relationship object to the all-in-one machine binding table.

6. The warehousing method according to claim 1, characterized in that, Create vehicle infotainment data, including: If the vehicle data corresponding to the vehicle serial number does not exist in the basic vehicle data table, a new vehicle data object is created and the vehicle hardware version number, vehicle software version number, vehicle serial number, deletion flag and creation / update time are written in. Save the vehicle infotainment object to the basic vehicle infotainment table.

7. The warehousing method according to claim 1, characterized in that, Create device grouping data, including: Record the project group data of the all-in-one machine; Record the data of the project group of the vehicle's infotainment system.

8. The warehousing method according to claim 1, characterized in that, Create all-in-one machine binding data, including: If the vehicle group code is empty, a random universally unique identifier is generated as the group code; Create separate integrated machine group objects and vehicle-mounted machine group objects. Write the group code, integrated machine report number, creation time and device type into the integrated machine group object, and write the group code, vehicle-mounted machine serial number, creation time and device type into the vehicle-mounted machine group object. Ensure consistency of group codes between the integrated machine group objects and the vehicle-mounted machine group objects.

9. The warehousing method according to claim 1, characterized in that, Standardized data files require all-in-one machine parameters to be arranged in the following order: All-in-one machine part number, all-in-one machine serial number, vehicle machine serial number, mobile user identification code; The verification methods for validating each piece of data in a standardized data file include: Non-empty verification, the relevant verification parameters include one or more of the following: all-in-one machine report number, all-in-one machine serial number, vehicle machine serial number, mobile user identification code, mobile device identification code, integrated circuit card identification code, vehicle network card operator, production line production date and shipping destination; and / or Field duplication verification involves one or more of the following parameters: vehicle serial number, mobile device identification code, mobile user identification code, integrated circuit card identification code, and Bluetooth physical address.

10. The warehousing method according to claim 1, characterized in that, It also includes two execution modes: Scheduled task mode: Scans directory files at fixed intervals and automatically inserts them into the database; Manual trigger mode: Receive supplier requests in real time and execute data entry.

Images