A client information import method and device, an electronic device, and a storage medium

Abstract

The application discloses a kind of import methods of customer information, it is related to artificial intelligence field, the method includes: in response to obtaining customer information list, extract customer information in customer information list, and store customer information into message queue;The compliance verification is carried out to customer information in message queue, and the compliant customer information is filled in by the storage information in database, to import the compliant customer information after filling into job system.The technical scheme of the embodiment of the application realizes the decoupling of customer information and list file, so that the import of other customer information in customer information list is not affected when single customer information exists error, the import efficiency of customer information is improved, and at the same time, the storage information in database is used to fill compliant customer information, to further ensure the data integrity of customer information imported by job system.

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence, and more particularly to a method, apparatus, electronic device, and storage medium for importing customer information. Background Technology

[0002] With the rapid development of business globalization, enterprises are facing an increasingly wide range of customers, and the effective management of customer information has become one of the important challenges they face.

[0003] Front-end staff typically record relevant information for each customer in a list file. Customer information is also imported in batches in the job system in the same list file format. When one or more customer information fails to be verified, the staff modifies each failed verification message and re-imports it into the job system until the list file is free of verification errors, at which point all customer information can be successfully imported.

[0004] However, with this method of importing information, operators must wait for the system to finish verification before they can perform other operations, which takes a long time. Furthermore, the list file needs to be imported successfully in one go. If multiple modifications are involved, the modified data may not be imported in time due to the presence of other abnormal data, resulting in low efficiency in importing customer information. Summary of the Invention

[0005] This invention provides a method, apparatus, electronic device, and storage medium for importing customer information, in order to solve the problem of low import efficiency when importing customer information into an operating system.

[0006] According to one aspect of the present invention, a method for importing customer information is provided, comprising:

[0007] In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue;

[0008] The customer information in the message queue is verified for compliance, and the compliant customer information that passes the compliance verification is matched with the stored information in the database;

[0009] If the database contains first target stored information with a matching degree greater than or equal to a first preset threshold, the compliant customer information is populated according to the first target stored information so as to import the populated compliant customer information into the operating system.

[0010] According to another aspect of the present invention, a customer information import device is provided, comprising:

[0011] The customer information extraction module is used to extract customer information from the customer information list in response to obtaining the customer information list, and store the customer information into a message queue;

[0012] The compliance verification execution module is used to perform compliance verification on the customer information in the message queue and match the compliant customer information that has passed the compliance verification with the stored information in the database.

[0013] The information filling execution module is used to fill the compliant customer information according to the first target stored information if there is a first target stored information in the database with a matching degree greater than or equal to a first preset threshold, so as to import the filled compliant customer information into the operating system.

[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0015] At least one processor; and

[0016] A memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the customer information import method according to any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the customer information import method according to any embodiment of the present invention.

[0019] The technical solution of this invention, after obtaining the customer information list, decouples the customer information from the list file by extracting the customer information and storing it in a message queue. This ensures that if a single customer information has an error, it will not affect the import of other customer information in the customer information list, and also ensures that the customer information can be verified in the background. This improves the efficiency of importing customer information. At the same time, for compliant customer information that has passed the compliance verification, the stored information in the database is used to populate the compliant customer information, further ensuring the data integrity of the customer information imported by the operating system.

[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart of a method for importing customer information according to Embodiment 1 of the present invention;

[0023] Figure 2 This is a flowchart of a customer information import method provided in Embodiment 2 of the present invention;

[0024] Figure 3 This is a flowchart of a customer information import method provided according to Embodiment 3 of the present invention;

[0025] Figure 4 This is a flowchart of a customer information import method provided in Embodiment 4 of the present invention;

[0026] Figure 5 This is a schematic diagram of a customer information import device according to Embodiment 5 of the present invention;

[0027] Figure 6 This is a schematic diagram of the structure of an electronic device that implements the customer information import method of this invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] Example 1

[0031] Figure 1 This is a flowchart of a customer information import method provided in Embodiment 1 of the present invention. This embodiment can be applied to importing customer information from a customer information list into an operating system. The method can be executed by a customer information import device, which can be implemented in hardware and / or software and can be configured in electronic devices such as servers.

[0032] A server can be a standalone server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms; for example... Figure 1 As shown, the method includes:

[0033] S101. In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue.

[0034] The customer information list is a file uploaded to the server by operators using a browser or client program via a front-end page. Each customer information list records one or more customer information entries, with each row or column representing one customer entry. After receiving the customer information list, the server extracts the customer information and stores it in a message queue. This decouples the customer information from the list file, meaning it removes the association between the customer information and the list file itself. This ensures that if a single customer entry is incorrect, it will not affect the import of other customer information entries in the list, preventing import failures due to erroneous or missing data in the list file.

[0035] To facilitate effective management of customer information, the server assigns a unique list identifier to each received customer information list. This list identifier is used to manage the individual customer information items within that list. Optionally, in this embodiment of the invention, the file format of the customer information list is not specifically limited. Message queues can use a message queue (MQ) cluster (e.g., Rabbit Message Queue) to process data in a multi-threaded manner, improving data processing efficiency. Furthermore, if a single computing device in the message queue cluster malfunctions, it will not affect the data processing of other computing devices; the message queue cluster will distribute the processing task to a normally functioning computing device. This solves the problem of low efficiency when relying on a single computing device for single-threaded processing and avoids data processing failures due to device instability or downtime.

[0036] Optionally, in this embodiment of the invention, extracting customer information from the customer information list includes: reading the associated information under each header according to the header information of the customer information list; or after storing the customer information in the message queue, it further includes: removing non-associated information in the message queue that does not have an association with the header information of the customer information list.

[0037] Specifically, the header, or the beginning of the customer information list, defines the data type of a row or column of information. When recording information, staff often add notes in blank spaces outside the main text, based on their personal habits. Since these notes only reflect the staff's personal habits and lack general reference value, to ensure the acquired customer information conforms to a unified standard, when reading the customer information list file, only the related information under each header is read based on the header information. This allows for targeted reading of effective information, filtering out notes reflecting staff personal habits and ensuring standardized customer information entry. Furthermore, since the reading of the customer information list and the data processing of customer information in the message queue are often performed by different servers in a server cluster or by different functional modules on a single server, after obtaining the customer information list, all data can be quickly read in a full-page manner to improve reading efficiency. Then, asynchronous removal of unrelated information from the message queue ensures the standardization of customer information entry.

[0038] S102. Perform compliance verification on the customer information in the message queue, and match the compliant customer information that has passed the compliance verification with the stored information in the database.

[0039] Compliance verification can include checking the number and type of parameters in customer information. If a customer information entry includes only a few parameters (e.g., only one parameter), it indicates that there is insufficient effective information describing the customer to reflect their actual situation, and the customer information is considered to have failed the compliance verification. If the customer information entry includes a large number of parameters, it indicates that there is sufficient effective information describing the customer to reflect their actual situation, and the customer information is considered to have passed the compliance verification. Furthermore, both the enterprise name and the unified social credit code are unique. If a customer information entry does not include any data under either of these parameter types, it indicates that the customer cannot be uniquely matched based on other parameters, and the customer information is considered to have failed the compliance verification. If a customer information entry includes relevant parameters under at least one of these parameter types, it indicates that the customer can be uniquely matched based on these parameters, and the customer information is considered to have passed the compliance verification.

[0040] Optionally, in this embodiment of the invention, the compliance verification of customer information in the message queue includes at least one of the following: performing data format standardization verification on customer information in the message queue by determining whether a specified parameter item includes a specified character and / or whether the number of characters in the specified parameter item is greater than or equal to a preset number threshold; performing data content duplication verification on customer information in the message queue by determining whether there is identical customer information in the message queue through the enterprise name and / or unified social credit code; and performing mandatory data missingness verification on customer information in the message queue by determining whether required fields are missing data. When registering customer information, staff may use abbreviations instead of full names for parameters such as company name and address to facilitate recording. This results in non-standard data format. Therefore, if the number of characters in the company name is small, for example, less than the preset threshold, or if the company name does not include characters such as "company" or "limited liability", the company name can be considered non-standard. Similarly, if the number of characters in the company address is small, or if the address does not include characters such as house number and street name, the company address can also be considered non-standard. Thus, the current customer information fails the data format standardization check.

[0041] Data content duplication verification checks whether different customer information comes from the same customer, thus preventing duplicate information of the same customer. Taking the above technical solution as an example, if two or more customer information have the same company name or unified social credit code, it indicates that the above customer information actually corresponds to the same customer, and there is a problem of duplicate customer information. The above two or more customer information will be identified as failing the data content duplication verification.

[0042] Based on the field identifiers in the table header corresponding to the current parameter, it can be determined whether the current parameter is a required or optional field. A required field means that the current parameter must be filled in; missing data will affect the import of the current customer's data. An optional field means that missing data will not affect the import of the current customer's data; after importing the data, the corresponding data will be displayed with "None," "Not Available," or blank. If the missing data corresponds to a required field, it indicates that the current customer has lost important information and needs to be supplemented. Obviously, the current customer information cannot pass the required data missingness check. Therefore, through data format standardization checks, data content duplication checks, and required data missingness checks, the accuracy and completeness of the customer information imported by the operating system are further ensured.

[0043] When matching compliant customer information that has passed compliance verification with the stored information in the database, the database can be an internal business information database used to record historical customer information, or it can be a third-party database (e.g., a third-party database that stores business registration data). Since the compliant customer information itself is valid information that has passed verification, in order to ensure the accuracy of the first target stored information and avoid incorrect matching results that could lead to incorrect filling of the compliant customer information, thus causing incorrect information to be mistakenly added to the otherwise accurate customer information, the first preset threshold can be set to a relatively large value.

[0044] Specifically, when matching compliant customer information with stored information, matching can be performed by specifying data items, such as the company name and unified social credit code. Since these parameters are unique, they need to be completely consistent with the stored information in the database to determine the first target stored information to be matched. In this case, the first preset threshold can be set to 100%. Alternatively, matching can be performed based on information such as the registered address and the legal representative of the company, but since the above data items may change, and the possibility of change is usually small, the first preset threshold can be set to a larger value slightly less than 100%, such as 95%.

[0045] S103. If there is a first target storage information in the database that matches the compliant customer information with a degree greater than or equal to a first preset threshold, then the compliant customer information is filled according to the first target storage information so as to import the filled compliant customer information into the operating system.

[0046] The customer information that has passed compliance verification describes the customer's basic information from multiple perspectives, but it cannot guarantee the completeness of the data content in all information items of the customer, especially for non-mandatory data. Many non-mandatory parameter items in the customer information may still be blank. Therefore, based on the obtained first target storage information, the corresponding blank items in the compliant customer information are directly filled in. At the same time, if a certain information item in the compliant customer information already contains data content, but the information item in the first target storage information contains other data content, such as a phone number, meaning that the compliant customer information and the first target storage information record different phone numbers, then, while retaining the current data content of the compliant customer information, the data content of the same information item in the first target storage information is also filled into the compliant customer information to ensure the data integrity of the filled compliant customer information.

[0047] Optionally, in this embodiment of the invention, the method for importing customer information includes at least one of the following: displaying the import progress of the customer information list through a front-end page; and, in response to an operation instruction that obtains an abnormal customer information set matching the customer information list, performing an information deletion operation, a data modification operation, or a data entry operation on the abnormal customer information in the abnormal customer information set. Regarding the import progress of each customer information in the current customer information list, the server can update the import progress on the front-end page according to a preset update cycle; it can also initiate an import progress update to the corresponding front-end page each time a new customer information is imported; or it can send the current import progress to the corresponding front-end page each time an import progress update request is received from the front-end page (e.g., the front-end page initiates an import progress update in a polling manner).

[0048] Specifically, the import status of each customer's information in the message queue can be stored in a key-value pair storage database, such as a Redis (Remote Dictionary Server) cluster. The abnormal customer information set is a collection of customer information that failed compliance checks even after automatic modification, merging, and population of data. Therefore, each customer information in this set requires manual operation commands from the user. Based on these commands, the server deletes, modifies, or populates information in the abnormal customer information set. This allows operators to easily repair customer information through batch operations when the server cannot automatically fix it. After importing the customer information from the customer information list into the job system, subsequent customer maintenance can be performed through the job system.

[0049] The technical solution of this invention, after obtaining the customer information list, decouples the customer information from the list file by extracting the customer information and storing it in a message queue. This ensures that if a single customer information has an error, it will not affect the import of other customer information in the customer information list, and also ensures that the customer information can be verified in the background. This improves the efficiency of importing customer information. At the same time, for compliant customer information that has passed the compliance verification, the stored information in the database is used to populate the compliant customer information, further ensuring the data integrity of the customer information imported by the operating system.

[0050] This invention allows customer information to be imported into an operational system based on artificial intelligence (AI) technology. AI is the theory, method, technology, and application system that uses digital computers or computers-controlled machines to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to achieve optimal results.

[0051] Example 2

[0052] Figure 2 This is a flowchart of a customer information import method provided in Embodiment 2 of the present invention. The relationship between this embodiment and the above embodiments is that, for the first type of customer information that fails the data format standardization check, non-standard data modification processing is performed. For example... Figure 2 As shown, the method includes:

[0053] S201. In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue; execute S202.

[0054] S202. Perform compliance verification on the customer information in the message queue; wherein, the compliance verification includes data format standardization verification; if it fails, proceed to S203; if it passes, proceed to S206.

[0055] S203. For the first type of customer information that fails the data format standardization verification, determine whether there is a second target stored information in the database that matches the first type of customer information with a degree greater than or equal to a second preset threshold based on other data items besides the non-standard data; wherein the second preset threshold is less than the first preset threshold; if yes, execute S204; if no, execute S205.

[0056] S204. Modify the non-standard data in the first type of customer information using the second target storage information; return to execute S202 to perform compliance verification on the modified first type of customer information again.

[0057] Because the first type of customer information contains non-standard data, which may appear in required or important data, such as company name, company address, and contact number; the company name uses an abbreviation instead of the full name, the contact number does not meet the specified number of digits, and the company address does not indicate the city name; when matching the first type of customer information with the stored information in the database, it is clear that matching can only be done through data items other than non-standard data; however, other data items, such as the company's legal representative, company contact person, and company address, are subject to change, so even for the same customer, the matching results may not be completely consistent when matching with the stored information in the database through these other data items; therefore, the second preset threshold can be set to be lower than the first preset threshold to reduce the matching requirements between the first type of customer information and the stored information.

[0058] After obtaining the second target storage information that matches the first type of customer information, the data item corresponding to the non-standard data in the first type of customer information is determined in the second target storage information, and the non-standard data is replaced with the data in the data item to realize the automatic modification of the non-standard data; for example, the company name is changed from "AA" to "AA Limited Liability Company".

[0059] In particular, when compliance verification includes multiple verification types, such as data format standardization verification, data content duplication verification, and mandatory data missing verification, the modified Type 1 customer information not only needs to undergo data format standardization verification again, but also data content duplication verification and mandatory data missing verification. This is because the modified Type 1 customer information may still have data content duplication issues (i.e., Type 1 customer information may also be Type 2 customer information) or mandatory data missing issues (i.e., Type 1 customer information may also be Type 3 customer information). Therefore, the modified Type 1 customer information needs to pass all compliance verifications to be determined as compliant customer information.

[0060] S205. Add the first type of customer information to the abnormal customer information set.

[0061] Adding a customer to the abnormal customer information set means that the customer information needs to be manually repaired by the operators.

[0062] S206. Match the compliant customer information that has passed the compliance verification with the stored information in the database; execute S207.

[0063] S207. If there is a first target storage information in the database that matches the compliant customer information with a degree greater than or equal to a first preset threshold, then the compliant customer information is filled according to the first target storage information so as to import the filled compliant customer information into the operating system.

[0064] The technical solution disclosed in this invention addresses the first type of customer information that fails the data format standardization verification. When matching second target storage information is obtained from the database based on other data items besides the non-standard data, the non-standard data in the first type of customer information is filled in using the second target storage information. This achieves automatic repair of non-standard data, ensuring the standardization of customer information while improving the efficiency of customer information import.

[0065] Example 3

[0066] Figure 3 This is a flowchart of a customer information import method provided in Embodiment 3 of the present invention. The relationship between this embodiment and the above embodiments is that data merging processing is performed on the second type of customer information that failed the data content duplication check. Figure 3 As shown, the method includes:

[0067] S301. In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue; execute S302.

[0068] S302. Perform compliance verification on the customer information in the message queue; wherein, the compliance verification includes data content duplication verification; if it fails, proceed to S303; if it passes, proceed to S306.

[0069] S303. For the second type of customer information that failed the data content duplication check, determine whether the second type of customer information meets the preset merging rules; if yes, execute S304; if no, execute S305.

[0070] For corporate clients, both the company name and the unified social credit code are unique and can identify a specific corporate client. Therefore, if multiple pieces of customer information have the same company name and the same unified social credit code, it indicates that the above customer information actually comes from the same customer. That is, the above multiple pieces of customer information meet the preset merging rules and are merged. For example, the contact phone numbers in the above multiple pieces of customer information are merged, and after merging, the customer has multiple contact phone numbers.

[0071] When performing data duplication verification, multiple customer information entries are identified as belonging to the same customer based on identical company names or unified social credit codes, thus failing the data duplication verification. However, when determining whether the aforementioned second type of customer information meets the preset merging rules, if multiple entries only have the same customer name but different unified social credit codes, or only the same unified social credit code but different customer names, it does not prove that the multiple entries come from the same customer. It is possible that the staff mistakenly entered different customer names as the same customer name when filling out the customer information list. Therefore, the aforementioned second type of customer information does not meet the preset merging rules, thus avoiding the merging of different customer information into information about the same customer.

[0072] S304. Merge the second type of customer information; return to execute S302 to perform compliance verification on the merged second type of customer information again.

[0073] In particular, when compliance verification includes multiple verification types, such as data format compliance verification, data content duplication verification, and mandatory data missing verification, the merged second-type customer information not only needs to undergo data content duplication verification again, but also data format compliance verification and mandatory data missing verification. This is because the merged second-type customer information may still have data format compliance issues (i.e., the second-type customer information may also be the first-type customer information) or mandatory data missing issues (i.e., the second-type customer information may also be the third-type customer information). Therefore, the merged second-type customer information needs to pass all compliance verifications to be determined as compliant customer information.

[0074] S305. Add the second type of customer information to the abnormal customer information set.

[0075] S306. Match the compliant customer information that has passed the compliance verification with the stored information in the database; execute S307.

[0076] S307. If there is a first target storage information in the database that matches the compliant customer information with a degree greater than or equal to a first preset threshold, then the compliant customer information is filled according to the first target storage information so as to import the filled compliant customer information into the operating system.

[0077] The technical solution disclosed in this invention addresses the second type of customer information that fails the data content duplication check. Based on preset merging rules, it merges the second type of customer information, achieving automatic merging of identical customer information. This ensures the standardization of customer information while improving the efficiency of importing customer information.

[0078] Example 4

[0079] Figure 4 This is a flowchart of a customer information import method provided in Embodiment 4 of the present invention. The relationship between this embodiment and the above embodiments is that, for the third type of customer information that fails the mandatory data missingness check, the missing mandatory data is filled in. Figure 4 As shown, the method includes:

[0080] S401. In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue; execute S402.

[0081] S402. Perform compliance verification on the customer information in the message queue; wherein, the compliance verification includes verification of missing required data; if it fails, proceed to S403; if it passes, proceed to S406.

[0082] S403. For the third type of customer information that fails the mandatory data missingness check, determine whether there is a third target stored information in the database storage information that matches the third type of customer information with a degree greater than or equal to a third preset threshold, based on other data items besides the missing mandatory data; wherein the third preset threshold is less than the first preset threshold; if yes, execute S204; if no, execute S205.

[0083] S404. Fill in the missing required data in the third type of customer information using the third target storage information; return to execute S402 to perform compliance verification on the filled third type of customer information again.

[0084] Because the third type of customer information lacks required data, and required data is often a distinctive feature that differentiates the current customer from other customers, such as a unique company name and unified social credit code, when matching the third type of customer information with the stored information in the database, it is clear that matching can only be done through data items other than the missing required data. However, other data items, such as the company's legal representative, contact person, and address, are subject to change. Therefore, even for the same customer, the matching results may not be completely accurate when matching the stored information with the stored information using these other data items. Therefore, the second preset threshold can be set to be lower than the first preset threshold to reduce the matching requirements between the third type of customer information and the stored information.

[0085] After obtaining the third target storage information that matches the third type of customer information, the data item corresponding to the missing mandatory data in the third target storage information is determined, and the data in the data item is used to fill the missing mandatory data to achieve automatic filling of the missing mandatory data; for example, the company name is filled from blank to "AA Limited Liability Company".

[0086] In particular, when compliance verification includes multiple verification types, such as data format compliance verification, data content duplication verification, and mandatory data missing verification, the filled third-type customer information not only needs to undergo mandatory data missing verification again, but also data format compliance verification and data content duplication verification. This is because the filled third-type customer information may still have problems with data format non-compliance (i.e., the third-type customer information may also be the first-type customer information) or data content duplication (i.e., the third-type customer information may also be the second-type customer information). Therefore, the filled third-type customer information needs to pass all compliance verifications to be determined as compliant customer information.

[0087] S405. Add the third type of customer information to the abnormal customer information set.

[0088] S406. Match the compliant customer information that has passed the compliance verification with the stored information in the database; execute S407.

[0089] S407. If there is a first target storage information in the database that matches the compliant customer information with a degree greater than or equal to a first preset threshold, then the compliant customer information is filled according to the first target storage information so as to import the filled compliant customer information into the operating system.

[0090] The technical solution disclosed in this invention addresses the issue of missing data in third-type customer information that fails the mandatory data missingness check. When matching third target storage information is obtained from the database based on other data items besides the missing mandatory data, the missing mandatory data in the third-type customer information is filled in using this third target storage information. This achieves automatic filling of missing data, ensuring the integrity of customer information while improving the efficiency of customer information import.

[0091] Example 5

[0092] Figure 5 This is a structural block diagram of a customer information import device provided in Embodiment 5 of the present invention. The device specifically includes:

[0093] The customer information extraction module 501 is used to extract customer information from the customer information list in response to obtaining the customer information list, and store the customer information into a message queue;

[0094] The compliance verification execution module 502 is used to perform compliance verification on the customer information in the message queue and match the compliant customer information that has passed the compliance verification with the stored information in the database.

[0095] The information filling execution module 503 is used to fill the compliant customer information according to the first target storage information if there is a first target storage information in the database that matches the compliant customer information with a degree greater than or equal to a first preset threshold, so as to import the filled compliant customer information into the operating system.

[0096] The technical solution of this invention, after obtaining the customer information list, decouples the customer information from the list file by extracting the customer information and storing it in a message queue. This ensures that if a single customer information has an error, it will not affect the import of other customer information in the customer information list, and also ensures that the customer information can be verified in the background. This improves the efficiency of importing customer information. At the same time, for compliant customer information that has passed the compliance verification, the stored information in the database is used to populate the compliant customer information, further ensuring the data integrity of the customer information imported by the operating system.

[0097] Optionally, the customer information extraction module 501 is used to read the associated information under each header according to the header information of the customer information list.

[0098] Optionally, the customer information import device also includes:

[0099] The unrelated information removal module is used to remove unrelated information from the message queue that is not related to the header information of the customer information list.

[0100] Optionally, the compliance verification execution module 502 is specifically used to perform data format standardization verification on customer information in the message queue by determining whether a specified parameter item includes a specified character and / or whether the number of characters in the specified parameter item is greater than or equal to a preset number threshold; and / or to perform data content duplication verification on customer information in the message queue by determining whether there is identical customer information in the message queue through the enterprise name and / or unified social credit code; and / or to perform mandatory data missingness verification on customer information in the message queue by determining whether required fields are missing data.

[0101] Optionally, the customer information import device also includes:

[0102] The data modification execution module is used to determine, for the first type of customer information that has failed the data format standardization verification, whether there is a second target stored information in the database that matches the first type of customer information with a degree greater than or equal to a second preset threshold, based on other data items besides the non-standard data; wherein the second preset threshold is less than the first preset threshold; if the second target stored information exists, the non-standard data in the first type of customer information is modified using the second target stored information, and the modified first type of customer information is then subjected to compliance verification again by the compliance verification execution module 502; if the second target stored information does not exist, the first type of customer information is added to the abnormal customer information set.

[0103] Optionally, the customer information import device also includes:

[0104] The data merging execution module is used to determine whether the second type of customer information that failed the data content duplication check meets the preset merging rules. If it meets the preset merging rules, the second type of customer information is merged, and the merged second type of customer information is then subjected to compliance check again by the compliance check execution module 502. If it does not meet the preset merging rules, the second type of customer information is added to the abnormal customer information set.

[0105] Optionally, the customer information import device also includes:

[0106] The data filling execution module is used to determine, based on other data items besides the missing mandatory data, whether there is any third target stored information in the database that matches the third type of customer information with a degree greater than or equal to a third preset threshold, for third type of customer information that fails the mandatory data missing validation for third type of customer information; wherein the third preset threshold is less than the first preset threshold; if the third target stored information exists, the missing mandatory data in the third type of customer information is filled in using the third target stored information, and the filled third type of customer information is then subjected to compliance validation again by the compliance validation execution module 502; if the third target stored information does not exist, the third type of customer information is added to the abnormal customer information set.

[0107] Optionally, the customer information import device may also include at least one of the following:

[0108] The import progress execution module is used to display the import progress of the customer information list through the front-end page;

[0109] The operation instruction response module is used to respond to an operation instruction that obtains an abnormal customer information set that matches the customer information list, and to perform information deletion, data modification, or data entry operations on the abnormal customer information in the abnormal customer information set.

[0110] The above-described apparatus can execute the customer information import method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the customer information import method provided in any embodiment of the present invention.

[0111] Example 6

[0112] Figure 6 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0113] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0114] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0115] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the method for importing customer information.

[0116] In some embodiments, the customer information import method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the customer information import method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the customer information import method by any other suitable means (e.g., by means of firmware).

[0117] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0118] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0119] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0120] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0121] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0122] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0123] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0124] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for importing customer information, characterized in that, include: In response to obtaining the customer information list, extract the customer information from the customer information list and store the customer information in the message queue; The customer information in the message queue is subjected to compliance verification, and the compliant customer information after passing the compliance verification is matched with the stored information in the database; wherein, the compliance verification of the customer information in the message queue includes: determining whether a specified parameter item includes a specified character and / or whether the number of characters in the specified parameter item is greater than or equal to a preset number threshold, so as to perform data format standardization verification on the customer information in the message queue; If the database contains first target stored information with a matching degree greater than or equal to the first preset threshold, then the compliant customer information is populated according to the first target stored information, so as to import the populated compliant customer information into the operating system. After verifying the compliance of customer information in the message queue, the method further includes: for the first type of customer information that fails the data format standardization verification, determining whether there is second target stored information in the database storage information that matches the first type of customer information with a degree greater than or equal to a second preset threshold based on other data items besides the non-standard data; wherein the second preset threshold is less than the first preset threshold; if there is second target stored information, then the non-standard data in the first type of customer information is modified using the second target stored information, and the modified first type of customer information is verified for compliance again; if there is no second target stored information, then the first type of customer information is added to the abnormal customer information set.

2. The method according to claim 1, characterized in that, The step of retrieving customer information from the customer information list includes: Based on the header information of the customer information list, read the associated information under each header; Alternatively, after storing the customer information in the message queue, the method may also include: Remove unrelated information from the message queue that is not associated with the header information of the customer information list.

3. The method according to claim 1, characterized in that, The compliance verification of customer information in the message queue includes at least one of the following: The system uses the company name and / or unified social credit code to determine whether there is duplicate customer information in the message queue, so as to perform data content duplication verification on the customer information in the message queue. The required fields are checked for missing data to verify the missing data in the customer information in the message queue.

4. The method according to claim 3, characterized in that, After performing compliance verification on the customer information in the message queue, the process also includes: For the second type of customer information that failed the data content duplication check, determine whether the second type of customer information meets the preset merging rules; If the preset merging rules are met, the second type of customer information will be merged, and the merged second type of customer information will be verified for compliance again. If the default merging rules are not met, the second type of customer information will be added to the abnormal customer information set.

5. The method according to claim 3, characterized in that, After performing compliance verification on the customer information in the message queue, the process also includes: For third-type customer information that fails the mandatory data missingness check, the database storage information is judged based on other data items besides the missing mandatory data to determine whether there is third target storage information in the database storage information with a matching degree greater than or equal to the third type of customer information; wherein, the third preset threshold is less than the first preset threshold; If third target storage information exists, the missing mandatory data in the third type of customer information is filled in using the third target storage information, and the compliance verification is performed again on the filled third type of customer information. If no third target storage information exists, the third type of customer information is added to the abnormal customer information set.

6. The method according to any one of claims 1-5, characterized in that, Includes at least one of the following: The import progress of the customer information list is displayed on the front-end page; In response to an operation instruction that obtains a set of abnormal customer information that matches the customer information list, perform information deletion, data modification, or data entry operations on the abnormal customer information in the abnormal customer information set.

7. A customer information import device, characterized in that, include: The customer information extraction module is used to extract customer information from the customer information list in response to obtaining the customer information list, and store the customer information into a message queue; The compliance verification execution module is used to perform compliance verification on the customer information in the message queue and match the compliant customer information that has passed the compliance verification with the stored information in the database; wherein, the compliance verification on the customer information in the message queue includes: determining whether a specified parameter item includes a specified character and / or whether the number of characters in the specified parameter item is greater than or equal to a preset number threshold, so as to perform data format standardization verification on the customer information in the message queue; The information filling execution module is used to fill the compliant customer information according to the first target storage information if there is a first target storage information in the database with a matching degree greater than or equal to a first preset threshold, so as to import the filled compliant customer information into the operation system. The data modification execution module is used to determine, for the first type of customer information that has failed the data format standardization verification, whether there is a second target stored information in the database that matches the first type of customer information with a degree greater than or equal to a second preset threshold, based on other data items besides the non-standard data; wherein the second preset threshold is less than the first preset threshold; if the second target stored information exists, the non-standard data in the first type of customer information is modified using the second target stored information, and the modified first type of customer information is then subjected to compliance verification again by the compliance verification execution module; if the second target stored information does not exist, the first type of customer information is added to the abnormal customer information set.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the customer information import method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method for importing customer information as described in any one of claims 1-6.

Images