Vehicle dealer data storage method and device and medium

Abstract

The invention provides a vehicle dealer data storage method, which comprises the following steps of: checking incoming vehicle dealer parameters, and if any parameter fails to be checked, terminating batch import; extracting a mapping relation among the large area, the small area, the province and the city from the database; querying whether there is special store data corresponding to a code in a database according to the special store code in the transmitted vehicle dealer parameters; if not, a logic deletion mark is generated, the creation information is filled, and the new dealer list is added; if so, updating the version number and the modification information; generating hierarchical codes on the basis of the inquired vehicle factory codes in combination with the special store codes, and creating / updating dealer organization objects in the region table; obtaining abnormal data of the previous steps and writing the abnormal data into a basic abnormal table; and writing the vehicle dealer data which are successfully put in storage into a cache. According to the method, three-stage closed-loop processing is realized, the problem of batch data integrity and format verification is solved, and data relevance is improved by organizing coding hierarchy.

Description

Technical Field

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

[0002] In back-office information management systems for automobile manufacturing, sales, leasing, repair, and traffic management, accurate and complete recording of vehicle dealer data is crucial. This information forms the basis for various business activities such as vehicle identification, inventory management, after-sales service, data analysis, and / or policy formulation.

[0003] Currently, in order to support the needs of offline car dealerships to join the network and record basic information of traded vehicles, existing related approximation technologies often suffer from problems such as missing regional information and insufficient data rationality. Summary of the Invention

[0004] This application aims to solve at least one technical problem existing in the prior art mentioned above, and proposes a method, device and medium for data entry of vehicle dealers.

[0005] In a first aspect, embodiments of this application provide a method for storing vehicle dealership data, including:

[0006] Verify the input vehicle dealer parameters; if any parameter fails to be verified, terminate the batch import process.

[0007] Extract the mapping relationships between regions, sub-regions, provinces, and cities from the database;

[0008] Based on the dealership code in the input vehicle dealership parameters, the database is checked to see if there is any dealership data corresponding to that code; if not, a logical deletion flag is generated and creation information is populated, and the dealership is added to the new dealership list; if it exists, the version number and modification information are updated.

[0009] Based on the vehicle manufacturer code obtained from the query and the dealership code, a hierarchical code is generated, and the dealer organization object in the region table is created / updated.

[0010] Obtain the abnormal data from the aforementioned steps and write it into the basic exception table;

[0011] Write the data of successfully registered vehicle dealers to the cache.

[0012] Furthermore, the verification of the input vehicle dealer parameters includes:

[0013] Verify the non-emptiness of the input franchise store code; if it is empty, the franchise store code verification fails.

[0014] Verify that the format of the input creation time conforms to the preset format specification; if it does not conform, the creation time verification will fail.

[0015] Furthermore, the mapping relationship is constructed in the following ways:

[0016] The region corresponds to a set of several provinces;

[0017] The community corresponds to a set of several cities within the province.

[0018] Furthermore, if it does not exist, a logical deletion flag is generated, including:

[0019] If it does not exist, the logical deletion flag for the expired dealer will be set according to the passed-in franchise store status information.

[0020] Furthermore, the generation of hierarchical codes based on the vehicle manufacturer code obtained from the query and the dealership code includes:

[0021] The vehicle manufacturer code and dealership code are concatenated with characters using a prefix and suffix to obtain the hierarchical code.

[0022] Furthermore, the abnormal data is written to the basic exception table, including:

[0023] The abnormal data is associated with the franchise store code and written to the basic anomaly table with a timestamp.

[0024] Furthermore, it also includes:

[0025] Based on the vehicle manufacturer code in the dealer organization object, query the account table to see if there is dealer account data. If not, create an account and configure security for the new dealer.

[0026] Account permissions are assigned based on the responsible person's job title field, with different responsible persons granted different data access scope permissions.

[0027] Furthermore, create accounts for new distributors, including:

[0028] The dictionary is searched based on the input brand code to determine if data corresponding to that brand code exists. If it does not exist, the vehicle manufacturer code is imported. If it exists, subsequent operations are performed.

[0029] After obtaining the vehicle manufacturer code, check the region table to see if the corresponding vehicle manufacturer organization exists. If it does not exist, report an error; if it exists, proceed with the next steps.

[0030] After retrieving the data from the dictionary table, the default dealer role code is extracted. The corresponding project information is then retrieved from the project table based on the brand code. Finally, the dealer organization information, the default dealer role, and the vehicle manufacturer organization information are used as parameters to request and create the dealer organization and account.

[0031] Secondly, embodiments of this application provide an electronic device, including: one or more processors;

[0032] A memory for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are able to implement the steps in any of the preceding storage methods.

[0033] Thirdly, embodiments of this application provide a computer-readable medium storing a computer program, which, when executed by a processor, can implement the steps in any of the aforementioned data entry methods.

[0034] This application provides a method for importing vehicle dealership data. Through a three-stage closed-loop process—data verification, data import, and exception handling and caching—it solves the problems of batch data integrity and format verification. By organizing the coding hierarchy, it improves data correlation and solves the problems of missing regional information and insufficient data rationality mentioned in the background technology. Attached Figure Description

[0035] Figure 1 This application provides a core flowchart of a method for importing vehicle dealer data into a database.

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

[0037] 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.

[0038] 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 the purpose of 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 in this specification, the presence of the stated features, integrals, steps, operations, elements, and / or components 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.

[0039] 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.

[0040] To support the online registration needs of offline car dealerships and record basic information about traded vehicles, existing related technologies often suffer from issues such as missing regional information and insufficient data reliability. To address at least one of these technical problems in the existing technologies, this application proposes a method, device, and medium for data entry into a vehicle dealership database.

[0041] One embodiment of this application proposes a method for importing vehicle dealer data into a database, which can be mainly divided into three stages.

[0042] The first stage is the data verification stage, which mainly verifies the integrity of the parameters. If some important information is incomplete, the data cannot be inserted into the database.

[0043] The second stage is the data entry stage, which mainly involves writing the relevant data of the dealers into the database. During this process, new data may be added or the previous dealer data may be modified.

[0044] The third stage is the exception handling stage. After problems and errors occur in the first and second stages, the system will capture the relevant exception information and return it, indicating that the data import process has failed and the data import has failed.

[0045] refer to Figure 1 More specifically, a method for importing vehicle dealer data may include the following steps.

[0046] Step 1: Validate the input vehicle dealer parameters (see Table 1 for the vehicle dealer parameter table). This process primarily validates two aspects of data: the dealership code, which serves as a unique identifier for the dealership data and cannot be empty; and the creation time format, which must be "yyyy-MM-dd". Both fields (dealership code + creation time) must meet the requirements; otherwise, an error will be returned. Since this function supports importing batch store information, the operation will stop if even one piece of data is incorrect.

[0047] In some embodiments, when importing 100 vehicle dealerships in batches, if the creation time of the 5th dealership is in the format createDate="20230501", it is considered an error, and the processing of the subsequent 95 dealerships is immediately terminated. This setting prevents local dirty data from polluting the overall database and ensures the atomicity of batch operations.

[0048] Table 1 Vehicle Dealer Parameter Table

[0049]

[0050] Step 2: First, retrieve the map information from the database. The main regions involved are categorized into four types: large regions, smaller regions, provinces, and cities. Large regions mainly include collections of several provinces, such as South China, North China, and Southwest China. Small regions mainly include a range of cities within a province, such as Central Shandong, Eastern Shandong, and Southern Shanxi. Extract this information first for subsequent operations.

[0051] In some embodiments, for example, the region "South China" is mapped to ["Guangdong", "Guangxi"], and the sub-region "Central Shandong" is mapped to ["Jinan", "Zibo"]. This establishes a four-level regional coding system, which can support the accurate collection of dealer geographic information.

[0052] Step 3: Query all stores in the database, categorize them into online stores and offline stores based on their status, and then import the information one by one according to the input parameter data.

[0053] Step 4: Based on the franchise store code in the input parameters, query the database to see if there is any data for the franchise store corresponding to that code. If it does not exist, modify the logical deletion flag according to the input outlet status (dlrStatus) information, setting the logical deletion flag for expired dealers. Then, populate the version, creator, and creation date information, and write this data into a new dealer list for later account creation for these dealers. If data corresponding to the franchise store code exists, update the version information to the current version plus one more version, and update the modifier and modification date information.

[0054] In some embodiments, if dlrStatus="OFFLINE", the logical deletion flag is set to 1 (historical data is retained). This setting avoids data loss due to physical deletion and supports branch status tracking.

[0055] Step 5: Update the dealer code, dealer name, dealer abbreviation, and dealer status to the object. Update the region, sub-region, province, and city information from the input parameters to the object. Based on all the information obtained above, convert the corresponding Chinese characters into encoded information and finally put them into the object.

[0056] Step 6: Update the creation time, address, dealer phone number, after-sales service phone number, and roadside assistance phone number to the object, determining the data to be written based on the job title. If the title is Sales Manager, fill in the name, phone number, and job title from the Responsible Person field into the Sales Manager's name and phone number field in the object; if the job title is Regional Manager, change these fields to the Regional Manager's relevant information. Then add information such as remarks, dealer type, and number of display vehicles.

[0057] Step 7: Update or save the information to the database. Any exceptions encountered during the process are directly saved in the basic exception table so that the information can be queried when the data entry fails later.

[0058] Specifically, abnormal data is associated with the franchise store code and written to the basic anomaly table with a timestamp. This enables precise anomaly localization, provides structured logs for troubleshooting, and improves troubleshooting efficiency.

[0059] Step 8: After the entire data import is successful, check if there is any new dealer information in the dealer list. If there is, continue to step 9; otherwise, proceed to step 14.

[0060] Step 9: Create an account for the newly added dealer. Based on the input brand code, check the dictionary table to see if there is data corresponding to the brand code. If not, return an error. The data dictionary table needs to be configured with the vehicle manufacturer code for the brand. This needs to be imported by the administrator. If it exists, proceed with the following operations.

[0061] Step 10: After obtaining the vehicle manufacturer code, check the region table to see if the corresponding vehicle manufacturer organization exists. If not found, report an error: "No vehicle manufacturer organization found for this brand." Contact the administrator for assistance. If found, proceed with the following steps.

[0062] Step 11: After obtaining the data from the dictionary table, extract the default dealer role code, query the corresponding project information in the project table based on the brand code, and then use the dealer organization information, default dealer role, and vehicle manufacturer organization information as parameters to request the creation of dealer organization and account.

[0063] Step 12: Based on the dealership code, check the region table for corresponding dealer organization information (the region table contains both brand manufacturer organization information and dealer organization information). If not, create a new object org (dealer organization object), set its region type to dealer type, and change the hierarchical code to the format of manufacturer code plus dealer code (to reflect the relevant information of its manufacturer code). Update the creation time, code, and name, and finally save this information to the region table. If it exists, directly retrieve the organization object org.

[0064] In some embodiments, the hierarchical code DFMC_DLR_CN_1001 is obtained by prefixing it with the vehicle manufacturer code DFMC and suffixing it with the dealership code DLR_CN_1001, connected by underscores. This configuration allows the attribution relationship to be reflected through the coding structure, reducing database query time from hundreds of milliseconds to milliseconds, thereby improving real-time query efficiency.

[0065] Step 13: Check if dealer account data exists in the account table based on the vehicle manufacturer code in the org. If not, proceed with the user creation process, writing the dealer name, responsible person name, vehicle manufacturer code, and other information into the database. Then, add security configuration information to the database; this table mainly records whether the account has configured security permissions.

[0066] Step 14: After all the information has been completely entered into the database, perform a caching operation to write all the dealer information into the cache so that the relevant information can be quickly found later.

[0067] In some embodiments, cache preheating may include storing a dealership code as the key and a complete dealer information object as the value in Redis. A cache key-value pair "DLR_CN_1001": {copName: "XX Auto", address: "No. 1, XX Road"...} is created. This setup can reduce database query time from hundreds of milliseconds to milliseconds, and also improve real-time query efficiency.

[0068] This application provides a method for importing vehicle dealership data into a database. Through a three-stage closed-loop process—data verification, data import, and anomaly handling and caching—it solves the problems of batch data integrity and format verification. By organizing the coding hierarchy, it improves data relevance, enabling more information to be reflected in the database tables. This addresses the issues of missing regional information and insufficient data validity mentioned in the background technology, facilitating the collection of dealership information and satisfying the querying needs for dealership store information.

[0069] 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 2 As 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, cause the one or more processors to implement any of the vehicle dealer 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.

[0070] 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).

[0071] 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.

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

[0073] 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 dealer data entry methods described in the above embodiments. The computer-readable storage medium can be volatile or non-volatile.

[0074] 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 dealer data entry method.

[0075] 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).

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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 storing vehicle dealership data, characterized in that, include: Verify the input vehicle dealer parameters; if any parameter fails to be verified, terminate the batch import process. Extract the mapping relationships between regions, sub-regions, provinces, and cities from the database; Based on the dealership code in the input vehicle dealership parameters, query the database to see if there is dealership data corresponding to that code; If it does not exist, generate a logical deletion flag and populate the creation information, then add it to the list of new dealers; if it exists, update the version number and modification information. Based on the vehicle manufacturer code obtained from the query and the dealership code, a hierarchical code is generated, and the dealer organization object in the region table is created / updated. Obtain the abnormal data from the aforementioned steps and write it into the basic exception table; Write the data of successfully registered vehicle dealers to the cache.

2. The warehousing method according to claim 1, characterized in that, The verification of the input vehicle dealer parameters includes: Verify the non-emptiness of the input franchise store code; if it is empty, the franchise store code verification fails. Verify that the format of the input creation time conforms to the preset format specification; if it does not conform, the creation time verification will fail.

3. The warehousing method according to claim 1, characterized in that, The mapping relationship is constructed in the following ways: The region corresponds to a set of several provinces; The community corresponds to a set of several cities within the province.

4. The warehousing method according to claim 1, characterized in that, If it does not exist, a logical deletion flag is generated, including: If it does not exist, the logical deletion flag for the expired dealer will be set according to the passed-in franchise store status information.

5. The warehousing method according to claim 1, characterized in that, The generation of hierarchical codes based on the vehicle manufacturer code obtained from the query and the dealership code includes: The vehicle manufacturer code and dealership code are concatenated with characters using a prefix and suffix to obtain the hierarchical code.

6. The warehousing method according to claim 1, characterized in that, Write the abnormal data into the basic exception table, including: The abnormal data is associated with the franchise store code and written to the basic anomaly table with a timestamp.

7. The warehousing method according to claim 1, characterized in that, Also includes: Based on the vehicle manufacturer code in the dealer organization object, query the account table to see if there is dealer account data. If not, create an account and configure security for the new dealer. Account permissions are assigned based on the responsible person's job title field, with different responsible persons granted different data access scope permissions.

8. The warehousing method according to claim 7, characterized in that, To create an account for a new distributor, including: The dictionary is searched based on the input brand code to determine if data corresponding to that brand code exists. If it does not exist, the vehicle manufacturer code is imported. If it exists, subsequent operations are performed. After obtaining the vehicle manufacturer code, check the region table to see if the corresponding vehicle manufacturer organization exists. If it does not exist, report an error; if it exists, proceed with the next steps. After retrieving the data from the dictionary table, the default dealer role code is extracted. The corresponding project information is then retrieved from the project table based on the brand code. Finally, the dealer organization information, the default dealer role, and the vehicle manufacturer organization information are used as parameters to request and create the dealer organization and account.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the steps in the data entry method as described in any one of claims 1 to 8.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it can perform the steps of the data entry method as described in any one of claims 1 to 8.

Images