WO2019019401A1 - 电子装置、名单除重方法和计算机可读存储介质 - Google Patents

电子装置、名单除重方法和计算机可读存储介质 Download PDF

Info

Publication number
WO2019019401A1
WO2019019401A1 PCT/CN2017/105025 CN2017105025W WO2019019401A1 WO 2019019401 A1 WO2019019401 A1 WO 2019019401A1 CN 2017105025 W CN2017105025 W CN 2017105025W WO 2019019401 A1 WO2019019401 A1 WO 2019019401A1
Authority
WO
WIPO (PCT)
Prior art keywords
list
type identifier
customer
processed
found
Prior art date
Application number
PCT/CN2017/105025
Other languages
English (en)
French (fr)
Inventor
沈毅
张勋
王刚
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Priority to SG11201901800VA priority Critical patent/SG11201901800VA/en
Priority to JP2018553483A priority patent/JP6648307B2/ja
Priority to US16/089,385 priority patent/US20210081380A1/en
Publication of WO2019019401A1 publication Critical patent/WO2019019401A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24553—Query execution of query operations
    • G06F16/24554—Unary operations; Data partitioning operations
    • G06F16/24556—Aggregation; Duplicate elimination

Definitions

  • the present invention relates to the field of data processing technologies, and in particular, to an electronic device, a list deduplication method, and a computer readable storage medium.
  • the current list deduplication method is usually simply based on the customer identification code (such as userId, customerId, etc.) or the mobile phone number, that is, by searching whether the system has the same customer identification code or mobile phone number list. , when there is the same weight, save, if not the same.
  • Such a method of removing weight has defects, and may cause the latest information of the customer to be deleted and deleted without being updated, and may also cause a large number of duplicate lists to be saved, failing to achieve the weight removal effect.
  • the main object of the present invention is to provide a method for list weight removal, which aims to improve the accuracy of list weight removal.
  • a first aspect of the present invention provides an electronic device including a memory and a processor, the memory having a list de-duplication system operable on the processor, the list de-duplication system being executed by the processor Implement the following steps:
  • the first-type identifier is the same as the first-type identifier of the to-be-processed client list;
  • the second type identifier is the same as the second type identifier of the to-be-processed client list.
  • the second type identifier is the same as the second type identifier of the to-be-processed client list, check whether the found customer list has the first type identifier;
  • the found customer list has a first type identifier, refreshing the information of the found customer list according to the to-be-processed database, and then searching for the second type identifier of the to-be-processed client list The second type of identification of the customer list is compared;
  • the to-be-processed client list is deduplicated.
  • a second aspect of the present invention provides a list weight removal method, the method comprising the steps of:
  • the first-type identifier is the same as the first-type identifier of the to-be-processed client list;
  • the second type identifier is the same as the second type identifier of the to-be-processed client list.
  • the second type identifier is the same as the second type identifier of the to-be-processed client list, check whether the found customer list has the first type identifier;
  • the found customer list has a first type identifier, refreshing the information of the found customer list according to the to-be-processed database, and then searching for the second type identifier of the to-be-processed client list The second type of identification of the customer list is compared;
  • the to-be-processed client list is deduplicated.
  • a third aspect of the invention provides a computer readable storage medium storing an information query control system, the information query control system being executable by at least one processor to cause the at least one processor Do the following:
  • the first-type identifier is the same as the first-type identifier of the to-be-processed client list;
  • the second type identifier is the same as the second type identifier of the to-be-processed client list.
  • the second type identifier is the same as the second type identifier of the to-be-processed client list, check whether the found customer list has the first type identifier;
  • the found customer list has a first type identifier, refreshing the information of the found customer list according to the to-be-processed database, and then searching for the second type identifier of the to-be-processed client list The second type of identification of the customer list is compared;
  • the to-be-processed client list is deduplicated.
  • the technical solution of the present invention firstly searches for a customer list of the first type identifier in the valid customer database by using the first type identifier of the unique identifier in the pending customer list, and when the first type identifier is not found,
  • the second type identifier in the pending customer list is searched in the valid customer database; after the second type identifier of the pending customer list is found, the customer list of the same second type identifier is found, and the found customer list already has the first
  • the type identifier is used to refresh the information of the customer list that is found according to the database to be processed, and the second type identifier of the refreshed customer list is compared with the second type identifier of the pending customer list, if the second type If the identifiers are still consistent, the current pending customer list will be removed and removed.
  • the solution avoids the problem of incomplete weight removal in the manner of performing weight removal only according to the ID search, and avoids the problem of causing the wrong weight removal only according to the method of removing the weight of the mobile phone number, thereby improving the problem.
  • FIG. 1 is a schematic flow chart of an embodiment of a method for deduplication of a list according to the present invention
  • FIG. 2 is a schematic flowchart of a second embodiment of a method for deduplication of a list according to the present invention
  • FIG. 3 is a schematic diagram of an operating environment of an embodiment of a list de-duplication system according to the present invention.
  • FIG. 4 is a block diagram showing a program module of an embodiment of the list de-duplication system of the present invention.
  • FIG. 5 is a block diagram showing a program module of a second embodiment of the list de-duplication system of the present invention.
  • Figure 6 is a block diagram showing the program module of the third embodiment of the list de-duplication system of the present invention.
  • the present invention proposes a list de-duplication method.
  • FIG. 1 is a schematic flowchart of an embodiment of a method for de-listing a list according to the present invention.
  • the method for removing the list includes the following steps:
  • Step S10 Obtain a to-be-processed client list one by one from the to-be-processed database, and analyze whether the obtained to-be-processed client list has the first type identifier;
  • the to-be-processed client list is a list of customer information recorded by the business system in the job, and the newly generated pending client list is all stored in the database to be processed, and the list de-duplication system periodically treats the database to be processed.
  • the list of pending clients may include a first type of identifier (eg, username, registration name, etc.), a second type of identifier (eg, registered mobile phone number, registration certificate number, etc.) and a third type of identification (eg, a common contact number)
  • the first type identifier is a unique identifier of the customer.
  • the partial processing client list may not have the first type identifier, and the partial processing client list may not even have the first type identifier and the second.
  • Type identifier In this embodiment, the first type identifier is a user ID, the second type identifier is a registered mobile phone number, the third type identifier is a common contact number, and the third type identifier may be multiple.
  • the list de-duplication system obtains the to-be-processed client list in the database to be processed in a manner of obtaining one by one, and first checks whether the obtained-to-be-processed client list has the first-type identifier.
  • step S20 if the to-be-processed client list has the first type identifier, the client list in the first-type identifier and the first-type identifier of the to-be-processed client list is searched in the valid customer database;
  • the list de-duplication system After confirming that the to-be-processed customer list has the first type identifier, the list de-duplication system searches the valid customer data for the first-type identifier and the same-type customer identifier of the first-type identifier of the pending customer list to determine a valid customer database. Whether there is already a customer list with the same first type of identification.
  • the first type identifier is the same as the first type identifier of the to-be-processed client list
  • the first type identifier is the unique identifier of the customer, that is, the found customer list and the The list of pending customers is the same customer's information, and because the pending customer list is the latest recorded customer's related information, the list de-duplication system will update the information of the found customer list according to the pending customer list.
  • the latest information of the customer list of the first type identifier is saved in the valid customer database.
  • Step S30 If the client list that is the same as the first type identifier of the to-be-processed client list is not found, find the client with the second type identifier and the second type identifier of the to-be-processed client list in the valid customer database. List
  • the list de-duplication system does not find the same type of customer ID in the active customer database as the first type identifier of the pending customer list, since the valid database also has a customer list that does not record the first type identifier, It is not confirmed that there is no customer list in the valid customer database that is duplicated with the information in the pending customer list; therefore, the list deduplication system performs further searching through the second type identifier, that is, the second type identifier is found in the effective customer database. A customer list that is the same as the second type identifier of the pending customer list to confirm whether the second type identifier in the pending customer list has been registered before.
  • Step S40 If the second type identifier is the same as the second type identifier of the to-be-processed client list, the client list is found to have the first type identifier.
  • the list deduplication system finds the same type of the second type identifier in the effective customer database as the second type identifier of the to-be-processed client list, it indicates that the second type identifier has been registered, and the search is performed at this time. Whether the obtained client list already has the first type identifier to confirm whether the second type identifier is previously registered by the other first type identifier. If the list de-duplication system does not find the first type identifier from the found customer list, the same type of the second type identifier may be used to confirm the found customer list.
  • the information about the customer to be processed is the same as the information of the customer list to be processed.
  • the list de-duplication system updates the information of the found customer list according to the information in the pending customer list, that is, the information in the pending customer list. Saved to the found customer list, the found customer list is updated with the first type identifier.
  • Step S50 If the found customer list has a first type identifier, refresh the information of the found customer list according to the to-be-processed database, and then use the second type identifier of the pending customer list. Comparing the second type identifiers of the found customer lists;
  • the list de-duplication system finds the first type identifier from the found customer list, and the list de-duplication system first finds the same first in the valid database through the first type identifier of the pending customer list.
  • the customer list of the type identifier indicates that the first type identifier of the customer list found by the second type identifier of the pending customer list is different from the first type identifier of the pending customer list, that is, a second type identifier is displayed. This situation is not allowed for the case of two first type identifiers; the reason for this situation may be: 1.
  • the found customer list is The customer may have already logged off the second type of identifier, and the second type of identifier is now in use by others; 2. the second type of identified customer uses the second type of identifier to register with a different first type of identifier. The second type of identification is registered by another person as the second type of identification.
  • the list de-duplication system refreshes the information of the found customer list according to the to-be-processed database, so that the second type identifier in the found customer list is The information is up-to-date, and after refreshing, the second type identifier of the found customer list is compared with the second type identifier of the pending customer list.
  • Step S60 If the second type identifier of the to-be-processed client list is the same as the second type identifier of the found customer list, the to-be-processed client list is deduplicated.
  • the second type identifier is still consistent with the second type identifier of the to-be-processed client list, indicating that the second type identifier of the to-be-processed client list has been searched
  • the first type identifier of the customer list is registered, and the second type identifier is still used by the first type identifier of the found customer list, and the other first type identifier is not allowed to be performed by the second type identifier.
  • the registration is repeated, so the list de-duplication system removes the list of pending customers, and deletes the list of pending customers.
  • the first type identifier of the unique identifier in the to-be-processed client list is used to search for a client list of the first type identifier in the valid customer database, and when the first type identifier is not found,
  • the second type identifier in the pending customer list is searched in the effective customer database; when the second type identifier of the pending customer list is found, the customer list of the same second type identifier is found, and the found customer is found.
  • the user list has the first type of identifier, and the information is refreshed according to the database to be processed, and the second type identifier of the refreshed customer list is compared with the second type identifier of the pending customer list.
  • the solution of the embodiment avoids the problem that the weight removal is not complete according to the method of performing weight removal according to the ID search, and avoids the problem of the weight removal caused by the weight removal method only. Improve the effect and accuracy of the list deduplication.
  • step S50 the step of refreshing the information of the found customer list according to the to-be-processed database in step S50 includes:
  • the list deduplication system searches for the list of pending clients matching the same first type identifier in the database to be processed through the first type identifier of the found customer list. The latest information of the customer identified by the first type.
  • the information of the found client list is updated according to the matched pending client list.
  • the list de-duplication system matches the to-be-processed client list of the first type identifier according to the matching
  • the information in the pending customer list updates the found customer list so that the information in the found customer list is up-to-date, that is, its second type identifier is also updated.
  • the to-be-processed database does not have the same pending client list as the first type identifier of the found client list, the information of the found client list is kept unchanged.
  • FIG. 2 is a flowchart of a second embodiment of a method for de-listing a list according to the present invention.
  • the embodiment is based on the solution of an embodiment.
  • the list de-duplication method further includes:
  • Step S70 If the second type identifier of the to-be-processed client list is different from the second type identifier of the found client list, searching for the third type identifier and the to-be-processed client from the valid customer database.
  • the second type of list identifies the same customer list;
  • the second type identifier is inconsistent with the second type identifier of the to-be-processed client list, indicating that the found customer list has changed the second type identifier, and the previous
  • the second type identifier is deregistered, so the second type identifier in the pending customer list does not conflict with the second type identifier of the client list in the valid customer database, and the second type identifier of the pending customer list is valid;
  • the time list deduplication system further searches the valid customer database for the same type of customer list as the second type identifier of the pending customer list.
  • Step S80 If a customer list with the third type identifier and the second type identifier of the to-be-processed client list is not found from the valid customer database, create a new list in the valid customer database, and The information in the pending customer list is saved to the newly created list;
  • the list de-duplication system does not find the third type identifier in the valid customer database that is the same as the second type identifier of the pending customer list, then there is no customer in the valid customer database associated with the second type identifier of the pending name.
  • the list confirms that the pending customer list is a new list, and the list de-duplication system saves the information in the pending customer list to the newly created list by creating a new list in the effective customer database, forming a new one in the effective customer database.
  • the customer list and the list of pending customers is deleted.
  • step S90 if the third type identifier is the same as the second type identifier of the to-be-processed client list, the client list is analyzed to have a second type identifier.
  • the list de-duplication system searches for the second type identifier of the to-be-processed client list in the third type identifier with the customer list, it further checks whether the searched customer list has the second type identifier.
  • Step S100 If the searched customer list does not have the second type identifier, merge the to-be-processed client list with the searched customer list;
  • the information of the searched customer list is not the information of the existing registered customer, and the searched customer list information is associated with the information of the pending customer list. Therefore, the searched customer list is merged with the pending customer list to form the latest customer list, and the information in the pending customer list is merged into the searched customer list, and the pending customer list is deleted. .
  • Step S110 If the searched customer list has a second type identifier, create a new list in the valid customer database, save the information in the pending customer list to the new list, and The third type identifier of the searched customer list is the same as the second type identifier of the pending customer list.
  • the searched customer list When the searched customer list already has a second type of identifier, the pending customer list and the searched customer list are respectively different customer information; and the searched customer list is related to the pending customer list.
  • the second type identifier of the second type identifier is already used as the second type identifier of the to-be-processed client list, so the third type identifier in the searched customer list should be deleted; the reason for this may be The third type of identification has already been logged out by the customer, but the information has not been updated yet.
  • the list de-duplication system saves the information of the to-be-processed customer list into a new list in the valid customer database to form a new customer list; and the searched customer
  • the third type identifier in the list that is the same as the second type identifier of the to-be-processed client list is cleared to update the information of the searched client list.
  • the list de-duplication method of the embodiment further includes:
  • the second-type identifier or the third-type identifier is the same as the second-type identifier or the third-type identifier of the to-be-processed client list.
  • the list de-duplication system determines that the to-be-processed client list does not have the first-type identifier
  • the client list of the second-type identifier or the third-type identifier including the to-be-processed client list is searched in the valid customer database, and it is determined that there is no first
  • the type identifies the information of the pending customer list in the valid customer database.
  • the list de-duplication system does not find the same customer list in the valid customer database as the second type identifier or the third type identifier of the pending customer list, the second type identifier and the third type of the pending customer list are indicated.
  • the identifiers are all not in the valid customer database, that is, the list of pending customers is new customer information.
  • the list deduplication system creates a new list in the effective customer database, and saves all the information in the pending customer list to the In the new list, the list of pending customers is deleted, that is, a new customer list without the first type identifier is added to the effective customer database.
  • the to-be-processed client list is deduplicated.
  • the list de-duplication system finds the same customer list in the valid customer database as the second type identifier or the third type identifier of the to-be-processed client list, the information of the to-be-processed client list exists in the valid customer database, and Since the to-be-processed client list does not have the first type identifier, it is not necessary to save a duplicate list without the first type identifier and the customer list in the valid customer database, so the list de-duplication system directly deletes the to-be-processed client list. .
  • the present invention also proposes a list weight removal system.
  • FIG. 3 is a schematic diagram of an operating environment of a preferred embodiment of the list de-duplication system 10 of the present invention.
  • the list de-duplication system 10 is installed and operated in the electronic device 1.
  • the electronic device 1 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a server.
  • the electronic device 1 may include, but is not limited to, a memory 11, a processor 12, and a display 13.
  • Figure 3 shows only the electronic device 1 with the components 11-13, but it should be understood It is not required to implement all of the illustrated components, and more or fewer components may be implemented instead.
  • the memory 11 may be an internal storage unit of the electronic device 1 in some embodiments, such as a hard disk or memory of the electronic device 1.
  • the memory 11 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in hard disk equipped on the electronic device 1, a smart memory card (SMC), and a secure digital (SD). Card, flash card, etc.
  • the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device.
  • the memory 11 is used to store application software and various types of data installed in the electronic device 1, such as program code of the list deduplication system 10.
  • the memory 11 can also be used to temporarily store data that has been output or is about to be output.
  • the processor 12 in some embodiments, may be a Central Processing Unit (CPU), microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing a list de-duplication System 10 and so on.
  • CPU Central Processing Unit
  • microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing a list de-duplication System 10 and so on.
  • the display 13 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like in some embodiments.
  • the display 13 is for displaying information processed in the electronic device 1 and a user interface for displaying visualization, such as a business customization interface or the like.
  • the components 11-13 of the electronic device 1 communicate with one another via a system bus.
  • FIG. 4 is a block diagram of a program of an embodiment of the list de-duplication system 10 of the present invention.
  • the list deduplication system 10 can be divided into one or more modules, one or more modules are stored in the memory 11, and by one or more processors (the processor 12 in this embodiment) It is performed to complete the present invention.
  • the list de-duplication system 10 can be divided into an acquisition module 101, a first search module 102, a second search module 103, a first view module 104, a comparison module 105, and a first de-duplication module 106.
  • module refers to a series of computer program instruction segments capable of performing a specific function, and is more suitable than the program for describing the execution process of the list deduplication system 10 in the electronic device 1, wherein:
  • the obtaining module 101 is configured to obtain a to-be-processed client list one by one from the to-be-processed database, and analyze whether the obtained to-be-processed client list has the first type identifier;
  • the to-be-processed customer list is a list of customer information recorded by the business system in the operation, and the newly generated pending customer list is all stored in the to-be-processed database, and the list de-duplication system 10 periodically processes the database.
  • the list of pending customers is processed.
  • the list of pending clients may include a first type of identifier (eg, username, registration name, etc.), a second type of identifier (eg, registered mobile phone number, registration certificate number, etc.) and a third type of identification (eg, a common contact number)
  • the first type identifier is a unique identifier of the client.
  • the partial processing client list may not have the first type identifier, and the partial processing client list may not even have the first type identifier and the first type identifier.
  • Two types of identification In this embodiment, the first type identifier is a user ID, the second type identifier is a registered mobile phone number, the third type identifier is a common contact number, and the third type identifier may be multiple.
  • the list de-duplication system 10 obtains the to-be-processed client list in the database to be processed in a manner of obtaining one by one, and first checks whether the obtained-to-be-processed client list has the first-type identifier.
  • the first search module 102 is configured to: after determining that the to-be-processed client list has the first type identifier, searching, in the valid customer database, the client list of the first type identifier and the first type identifier of the to-be-processed client list;
  • the list de-duplication system 10 After confirming that the to-be-processed customer list has the first type of identifier, the list de-duplication system 10 searches the valid customer data for the first-type identifier and the same-type customer identifier of the first-type identifier of the pending customer list to determine a valid customer. Whether the customer list with the same first type identifier already exists in the database.
  • the first type identifier is the same as the first type identifier of the to-be-processed client list
  • the first type identifier is the unique identifier of the customer, that is, the found customer list and the
  • the list of the customer to be processed is the information of the same customer, and the information of the customer who is the latest record in the list of pending customers is updated by the list deduplication system 10 according to the list of the customer to be processed.
  • the latest information of the customer list of the first type identifier is saved in the valid customer database.
  • the second search module 103 is configured to: after finding the same client list as the first type identifier of the to-be-processed client list, searching for the second type identifier and the second list of the pending client list in the effective customer database Type identifies the same customer list;
  • the list deduplication system 10 does not find the client list of the first type identifier and the first type identifier of the to-be-processed client list in the valid customer database, since the valid database also has a client list that does not record the first type identifier, Therefore, it is not confirmed at this time that there is no customer list in the valid customer database that is duplicated with the information in the pending customer list; therefore, the list deduplication system 10 performs further searching through the second type identifier, that is, searches for the second in the effective customer database.
  • the type identifies the same customer list as the second type identifier of the pending customer list to confirm whether the second type identifier in the pending customer list has been registered before.
  • the first viewing module 104 is configured to check whether the found customer list has a first type identifier after searching for the same type of the second type identifier and the second type identifier of the to-be-processed client list.
  • the list deduplication system finds the same type of the second type identifier in the effective customer database as the second type identifier of the to-be-processed client list, it indicates that the second type identifier has been registered, and the search is performed at this time. Whether the obtained client list already has the first type identifier to confirm whether the second type identifier is previously registered by the other first type identifier. If the list de-duplication system 10 does not find the first type identifier from the found customer list, the same type of identifier can be confirmed according to the second type identifier of the two. The list and the customer list to be processed are the same customer information.
  • the list deduplication system 10 updates the information of the found customer list according to the information in the pending customer list, that is, in the pending customer list.
  • the information is saved to the found customer list, and the found customer list is updated to have the first type identifier.
  • the comparison module 105 is configured to refresh the information of the found customer list according to the to-be-processed database after the found customer list has the first type identifier, and then use the second-to-be-processed customer list The type identifier is compared with the second type identifier of the found customer list;
  • the list deduplication system 10 finds the first type of identification from the found customer list, and because the list deduplication system 10 first searches through the valid database in the first type of the pending customer list, the same is not found.
  • the customer list of the first type identifier indicates that the first type identifier of the customer list found by the second type identifier of the pending customer list is different from the first type identifier of the pending customer list, that is, a second appears.
  • the type identifier corresponds to the situation of two first type identifiers. This situation is not allowed; the reason for this situation may be: 1.
  • the second type of identification Since the information of the customer list in the effective customer database is not the latest information, the found customer The customer of the list may have already logged off the second type of identification, the second type of identification is now being used by others; 2. the customer of the second type of identification uses the second type of identification to register with different first type of identification; 3. The second type of identification is registered by another person as the second type of identification.
  • the list deduplication system 10 refreshes the information of the found customer list according to the to-be-processed database, so that the second type in the found customer list is The identifier information is up-to-date, and after refreshing, the second type identifier of the found customer list is compared with the second type identifier of the to-be-processed client list.
  • the first de-duplication module 106 is configured to perform weight removal on the to-be-processed client list after the second type identifier of the to-be-processed client list is compared with the second type identifier of the found client list.
  • the second type identifier is still consistent with the second type identifier of the to-be-processed client list, indicating that the second type identifier of the to-be-processed client list has been searched
  • the first type identifier of the customer list is registered, and the second type identifier is still used by the first type identifier of the found customer list, and the other first type identifier is not allowed to be performed by the second type identifier.
  • the registration is repeated, so the list de-duplication system removes the list of pending customers, and deletes the list of pending customers.
  • the first type identifier of the unique identifier in the to-be-processed client list is used to search for a client list of the first type identifier in the valid customer database, and when the first type identifier is not found, Finding in the valid customer database through the second type of identifier in the pending customer list; when passing the pending customer list
  • the second type identifier finds the customer list of the same second type identifier, and the found customer list already has the first type identifier, the information is refreshed according to the database to be processed, and the refreshed customer list is
  • the second type identifier is further compared with the second type identifier of the to-be-processed client list.
  • the solution of the embodiment avoids the problem that the weight removal is not complete according to the method of performing weight removal according to the ID search, and avoids the problem of the weight removal caused by the weight removal method only. Improve the effect and accuracy of the list deduplication.
  • the operation of the comparison module 105 to refresh the information of the found customer list according to the to-be-processed database is specifically: matching the first type identifier and the found in the to-be-processed database.
  • the first type of the customer list identifies the same pending customer list; after matching the to-be-processed customer list, the information is updated according to the matched pending customer list.
  • the comparison module 105 searches for the list of pending clients in the database to be matched with the same first type identifier through the first type identifier of the found customer list to find out The latest information of the customer identified by the first type. If the pending database has the same pending client list as the first type identifier of the found client list, the matching module 105 matches the to-be-processed client list of the first type identifier according to the matching The information in the pending customer list updates the found customer list so that the information in the found customer list is up-to-date, that is, its second type identifier is also updated. In addition, if the to-be-processed database does not have the same pending client list as the first type identifier of the found client list, the information of the found client list is kept unchanged.
  • the list de-duplication system 10 of this embodiment further includes:
  • the searching module 107 is configured to search for a third type identifier from the valid customer database after the second type identifier of the to-be-processed client list is different from the second type identifier of the found client list.
  • the second type of pending customer list identifies the same customer list;
  • the second type identifier is inconsistent with the second type identifier of the to-be-processed client list, indicating that the found customer list has changed the second type identifier, and the previous
  • the second type identifier is deregistered, so the second type identifier in the pending customer list does not conflict with the second type identifier of the customer list in the valid customer database, and the second type identifier of the pending customer list is valid;
  • the deduplication system 10 further searches the valid customer database for a third type of identification that identifies the same customer list as the second type of identification of the pending customer list.
  • a first new module 108 configured to not search for the same type of the third type identifier from the valid customer database as the second type identifier of the to-be-processed client list After the single entry, create a new list in the valid customer database, and save the information in the pending customer list to the newly created list;
  • the list deduplication system 10 does not find the third type identifier in the valid customer database that is the same as the second type identifier of the pending customer list, then the valid customer database is not associated with the second type identifier of the pending name.
  • the customer list confirms that the list of pending customers is a new list, and the list deduplication system 10 creates a new list in the valid customer database, and saves the information in the pending customer list to the newly created list to form a valid customer database. Add a new customer list and delete the pending customer list.
  • the second viewing module 109 is configured to analyze whether the searched customer list has a client list after the third type identifier is the same as the second type identifier of the to-be-processed client list. Second type identifier;
  • the list deduplication system 10 searches for the second type identifier of the to-be-processed client list in the third type identifier having the client list, it further checks whether the searched client list has the second type identifier.
  • the merging module 110 is configured to merge the to-be-processed client list with the searched client list after determining that the searched customer list does not have the second type identifier;
  • the information of the searched customer list is not the information of the existing registered customer, and the searched customer list information is associated with the information of the pending customer list. Therefore, the searched customer list is merged with the pending customer list to form the latest customer list, and the information in the pending customer list is merged into the searched customer list, and the pending customer list is deleted. .
  • the second new module 111 is configured to: after determining that the searched customer list has the second type identifier, create a new list in the valid customer database, and save the information in the pending customer list to the new list. And deleting the third type identifier of the searched client list that is the same as the second type identifier of the to-be-processed client list.
  • the searched customer list When the searched customer list already has a second type of identifier, the pending customer list and the searched customer list are respectively different customer information; and the searched customer list is related to the pending customer list.
  • the second type identifier of the second type identifier is already used as the second type identifier of the to-be-processed client list, so the third type identifier in the searched customer list should be deleted; the reason for this may be
  • the third type of identification has already been logged out by the customer, but the information has not been updated yet.
  • the list de-duplication system 10 saves the information of the to-be-processed customer list into a new list in the valid customer database to form a new customer list; and lists the to-be-processed client in the searched customer list.
  • the second type identifies the same third type of identity clear to update the information of the searched customer list.
  • the list de-duplication system 10 of this embodiment further includes:
  • the third searching module 112 is configured to: when the to-be-processed client list does not have the first type identifier, search for the second type identifier or the third type identifier and the second type identifier of the to-be-processed client list or the third in the valid customer database.
  • Type identifies the same customer list;
  • the list de-duplication system 10 determines that the to-be-processed client list does not have the first-type identifier, the list of clients including the second-type identifier or the third-type identifier of the to-be-processed client list is searched in the effective customer database, and it is determined that there is no The information of a type of identified customer list to be processed exists in the valid customer database.
  • the third new module 113 is configured to create a new list in the valid customer database when the client list that is the same as the second type identifier or the third type identifier of the to-be-processed client list is not found, and the The information in the processing client list is saved to the newly created list;
  • the list de-duplication system 10 does not find the same customer list in the valid customer database as the second type identifier or the third type identifier of the pending customer list, the second type identifier and the third of the pending customer list are indicated.
  • the type identifier is not in the valid customer database, that is, the pending customer list is new customer information.
  • the list deduplication system 10 creates a new list in the effective customer database, and saves all the information in the pending customer list. In the new list, a new customer list without the first type of identifier is added to the effective customer database.
  • the second de-duplication module 114 is configured to remove the to-be-processed client list after finding the same client list as the second type identifier or the third type identifier of the to-be-processed client list.
  • the list deduplication system 10 finds the same customer list in the valid customer database as the second type identifier or the third type identifier of the to-be-processed client list, the information of the to-be-processed client list exists in the valid customer database. And because the to-be-processed client list does not have the first type identifier, it is not necessary to save a duplicate list without the first type identifier and the customer list existence information in the valid customer database, so the list de-duplication system 10 directly treats the pending customer. The list is deleted.
  • the present invention also provides a computer readable storage medium storing an information query control system, the information query control system being executable by at least one processor to cause the at least one processor to perform the above-described The list de-duplication method in one embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Quality & Reliability (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种电子装置、名单除重方法及介质，其中，该方法包括：从待处理数据库中逐个获取待处理名单，分析获取到的待处理名单是否具有第一类型标识（S10）；若具有第一类型标识，则在有效客户数据库中查找第一类型标识与待处理名单的第一类型标识相同的客户名单（S20）；若没有查找到，则在有效客户数据库中查找与待处理名单的第二类型标识相同的客户名单（S30）；若查找到，则查看查找到的客户名单是否具有第一类型标识（S40）；若具有第一类型标识，则根据待处理数据库刷新查找到的客户名单的信息，再将待处理名单的第二类型标识与查找到的客户名单的第二类型标识进行比对（S50）；若比对上，则将待处理名单进行除重（S60）。该方法实现了提升名单除重的效果和准确性。

Description

电子装置、名单除重方法和计算机可读存储介质
本申请基于巴黎公约申明享有2017年7月25日递交的申请号为CN 201710614495.0、名称为“电子装置、名单除重方法和计算机可读存储介质”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本发明涉及数据处理技术领域，特别涉及一种电子装置、名单除重方法和计算机可读存储介质。
背景技术
目前的名单除重处理方式，通常只是简单地根据客户识别码(比如userId、customerId等单一识别码)或手机号进行除重，即通过查找***中是否已经有相同客户识别码或手机号的名单，在有相同时除重，没有相同时就保存。这样的除重方式，存在缺陷，可能会让客户的最新信息得不到更新就被除重删除，也可能会造成大量重复的名单保存，达不到除重效果。
发明内容
本发明的主要目的是提供一种名单除重方法，旨在提高名单除重的准确性。
本发明第一方面提供一种电子装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的名单除重***，所述名单除重***被所述处理器执行时实现如下步骤：
从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
本发明第二方面提供一种名单除重方法，该方法包括步骤：
从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
本发明第三方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有信息查询控制***，所述信息查询控制***可被至少一个处理器执行，以使所述至少一个处理器执行如下操作：
从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
本发明技术方案，首先通过待处理客户名单中的唯一识别码第一类型标识在有效客户数据库中查找是否有该第一类型标识的客户名单，在通过第一类型标识未查找到时，再通过待处理客户名单中的第二类型标识在有效客户数据库中查找；当通过待处理客户名单的第二类型标识查找到了相同第二类型标识的客户名单后，且查找到的客户名单已经有第一类型标识，则根据待处理数据库对查找到的客户名单进行信息刷新，刷新后的该客户名单的第二类型标识再与所述待处理客户名单的第二类型标识进行比对，如果第二类型标识仍然一致，则将当前待处理客户名单进出除重。与现有技术相比，本方案避免了仅根据ID查找进行除重的方式存在的除重不彻底的问题，也避免了仅根据手机号除重的方式造成误除重的问题，使得提升了名单除重的效果和准确性。
附图说明
图1为本发明名单除重方法一实施例的流程示意图；
图2为本发明名单除重方法二实施例的流程示意图；
图3为本发明名单除重***一实施例的运行环境示意图；
图4为本发明名单除重***一实施例的程序模块图；
图5为本发明名单除重***二实施例的程序模块图；
图6为本发明名单除重***三实施例的程序模块图。
具体实施方式
以下结合附图对本发明的原理和特征进行描述，所举实例只用于解释本发明，并非用于限定本发明的范围。
本发明提出一种名单除重方法。
如图1所示，图1为本发明名单除重方法一实施例的流程示意图。
本实施例中，该名单除重方法包括步骤：
步骤S10，从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
本实施例中，待处理客户名单是业务***在作业中产生的记录有客户信息的名单，新产生的待处理客户名单全部存储到待处理数据库中，名单除重***定时对待处理数据库中的待处理客户名单进行处理。待处理客户名单中可包含第一类型标识(例如，用户名、注册名等)、第二类型标识(例如，注册手机号、注册证件号等)和第三类型标识(例如，常用联系号码)，其中，第一类型标识是客户的唯一识别码；本实施例中，待处理数据库中，部分处理客户名单可能没有第一类型标识，部分处理客户名单甚至可能没有第一类型标识和第二 类型标识。本实施例优选采用第一类型标识为用户ID，第二类型标识为注册手机号，第三类型标识为常用联系号码，且第三类型标识可为多个。本实施例名单除重***以逐一获取的方式获取待处理数据库中的待处理客户名单，先查看获取到的待处理客户名单有没有第一类型标识。
步骤S20，若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
在确认该待处理客户名单具有第一类型标识后，名单除重***则在有效客户数据中查找第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，以确定有效客户数据库中是否已经存有相同第一类型标识的客户名单。如果在有效客户数据中查找到第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，由于第一类型标识是客户的唯一识别码，即说明该查找到的客户名单与该待处理客户名单为同一客户的信息，又由于该待处理客户名单中为最新记录的客户的相关信息，因此名单除重***将根据该待处理客户名单对查找到的客户名单进行信息更新，使该有效客户数据库中保存该第一类型标识的客户名单的最新信息。
步骤S30，若没有查找到与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
如果名单除重***在有效客户数据库中没有找到第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，由于有效数据库中也存有未记录第一类型标识的客户名单，故此时并不能确认有效客户数据库中没有与该待处理客户名单中的信息重复的客户名单；因此名单除重***通过第二类型标识进行进一步的查找，即再在有效客户数据库中查找第二类型标识与该待处理客户名单的第二类型标识相同的客户名单，以确认该待处理客户名单中的第二类型标识之前有没有被注册过。
步骤S40，若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
当名单除重******在有效客户数据库中找到了第二类型标识与该待处理客户名单的第二类型标识相同的客户名单时，说明该第二类型标识已经被注册过，此时查看该查找到的客户名单是否已经具有第一类型标识，以确认该第二类型标识之前是不是被其它第一类型标识注册。如果名单除重***从该查找到的客户名单中没有发现第一类型标识，则根据两者的第二类型标识相同可确认该查找到的客户名单 与该待处理客户名单为同一客户的信息，此时名单除重***将根据该待处理客户名单中的信息对该查找到的客户名单的进行信息更新，即以该待处理客户名单中的信息保存到该查找到的客户名单中，该查找到的客户名单更新后则具有第一类型标识。
步骤S50，若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
当名单除重***从该查找到的客户名单中找到了第一类型标识，且由于名单除重***最先通过该待处理客户名单的第一类型标识在有效数据库中查找时没有找到相同第一类型标识的客户名单，则说明通过该待处理客户名单的第二类型标识查找到的客户名单的第一类型标识与该待处理客户名单的第一类型标识不同，即出现了一个第二类型标识对应两个第一类型标识的情形，这种情形是不允许的；造成这种情形的原因可能为：1、由于有效客户数据库中的客户名单的信息不是最新信息，该查找到的客户名单的客户可能已经将注销了该第二类型标识，该第二类型标识现在是别人在使用；2、该第二类型标识的客户又使用该第二类型标识以不同第一类型标识进行注册，3、该第二类型标识被其它人用作第二类型标识进行注册。出现这种情形时，为确认是上面那种原因造成，名单除重***根据所述待处理数据库对该查找到的客户名单的信息进行刷新，使该查找到的客户名单中的第二类型标识信息最新，刷新后，再将该查找到的客户名单的第二类型标识与所述待处理客户名单的第二类型标识比对。
步骤S60，若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
当所述查找到的客户名单被刷新信息后，第二类型标识仍然与所述待处理客户名单的第二类型标识一致，则说明所述待处理客户名单的第二类型标识已经被所述查找到的客户名单的第一类型标识所注册，且该第二类型标识仍在被所述查找到的客户名单的第一类型标识使用，不允许其它第一类型标识再以该第二类型标识进行重复注册，故名单除重***将所述待处理客户名单除重，即将该待处理客户名单删除。
本实施例技术方案，首先通过待处理客户名单中的唯一识别码第一类型标识在有效客户数据库中查找是否有该第一类型标识的客户名单，在通过第一类型标识未查找到时，再通过待处理客户名单中的第二类型标识在有效客户数据库中查找；当通过待处理客户名单的第二类型标识查找到了相同第二类型标识的客户名单后，且查找到的客 户名单已经有第一类型标识，则根据待处理数据库对查找到的客户名单进行信息刷新，刷新后的该客户名单的第二类型标识再与所述待处理客户名单的第二类型标识进行比对，如果第二类型标识仍然一致，则将当前待处理客户名单进出除重。与现有技术相比，本实施例方案避免了仅根据ID查找进行除重的方式存在的除重不彻底的问题，也避免了仅根据手机号除重的方式造成误除重的问题，使得提升了名单除重的效果和准确性。
优选地，所述步骤S50中的根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
因为待处理数据库中存储着最新的客户信息，因此，名单除重***通过查找到的客户名单的第一类型标识去待处理数据库中匹配相同第一类型标识的待处理客户名单，以找出该第一类型标识的客户最新信息。
在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
如果该待处理数据库中有与该查找到的客户名单的第一类型标识相同的待处理客户名单，则名单除重***在匹配到该第一类型标识的待处理客户名单后，根据该匹配到的待处理客户名单中的信息更新该查找到的客户名单，使该查找到的客户名单中的信息最新，即也更新了其第二类型标识。另外，若该待处理数据库中没有与该查找到的客户名单的第一类型标识相同的待处理客户名单，则保持该查找到的客户名单的信息不变。
如图2所示，图2为本发明名单除重方法二实施例的流程图。本实施例基于一实施例的方案，在本实施例中，该名单除重方法在所述步骤S50之后，还包括：
步骤S70，若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识不相同，则从所述有效客户数据库中搜寻第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
当所述查找到的客户名单进行信息刷新后，其第二类型标识与待处理客户名单的第二类型标识不一致了，则说明该查找到的客户名单已经变更了第二类型标识，其之前的第二类型标识已经注销，故该待处理客户名单中的第二类型标识没有与有效客户数据库中的客户名单的第二类型标识冲突，该待处理客户名单的第二类型标识有效；此 时名单除重***进一步从所述有效客户数据库中搜寻第三类型标识与该待处理客户名单的第二类型标识相同的客户名单。
步骤S80，若从所述有效客户数据库中没有搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
如果名单除重***没在有效客户数据库中搜寻到与该待处理客户名单的第二类型标识相同的第三类型标识，则有效客户数据库中没有与该待处理名的第二类型标识关联的客户名单，确认该待处理客户名单为新名单，名单除重***则通过在有效客户数据库中新建名单，将该待处理客户名单中的信息保存到该新建名单中，形成有效客户数据库中新增的客户名单，并将该待处理客户名单删除。
步骤S90，若从所述有效客户数据库中搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则分析所述搜寻到的客户名单是否具有第二类型标识；
当名单除重***搜寻到有客户名单的第三类型标识中含有所述待处理客户名单的第二类型标识时，则进一步地查看该搜寻到的客户名单有没有第二类型标识。
步骤S100，若所述搜寻到的客户名单没有第二类型标识，则将所述待处理客户名单与所述搜寻到的客户名单进行信息合并；
当该搜寻到的客户名单中没有第二类型标识，则说明该搜寻到的客户名单的信息不是已有注册客户的信息，且该搜寻到的客户名单信息与该待处理客户名单的信息相关联，因此将搜寻到的客户名单与该待处理客户名单进行信息合并以形成最新的客户名单，即将该待处理客户名单中的信息合并到搜寻到的客户名单中，并将该待处理客户名单删除。
步骤S110，若所述搜寻到的客户名单具有第二类型标识，则在所述有效客户数据库中新建名单，将所述待处理客户名单中的信息保存到所述新建名单中，并将所述搜寻到的客户名单的与所述待处理客户名单的第二类型标识相同的第三类型标识清除。
当该搜寻到的客户名单已经具有第二类型标识，说明该待处理客户名单与该搜寻到的客户名单分别为不同客户的信息；由于该搜寻到的客户名单中的与该待处理客户名单的第二类型标识相同的第三类型标识，现已经作为该待处理客户名单的第二类型标识，因此该搜寻到的客户名单中的该第三类型标识应当删除；出现这种情况的原因可能是该第三类型标识早已经被客户注销，只是还没有进行信息更新。此时名单除重***将该待处理客户名单的信息通过保存到有效客户数据库中的新建名单内以形成新的客户名单；并且将该搜寻到的客户 名单中的与所述待处理客户名单的第二类型标识相同的第三类型标识清除，以更新该搜寻到的客户名单的信息。
进一步地，本实施例的名单除重方法于所述步骤S10之后，还包括：
若待处理客户名单没有第一类型标识，则在有效客户数据库中查找第二类型标识或第三类型标识与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单；
当名单除重***确定该待处理客户名单没有第一类型标识时，则在有效客户数据库中查找包括该待处理客户名单的第二类型标识或第三类型标识的客户名单，确定该没有第一类型标识的待处理客户名单的信息在有效客户数据库中是否存在。
若查找不到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
如果名单除重***在有效客户数据库中查不到与该待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则说明该待处理客户名单的第二类型标识和第三类型标识都是有效客户数据库中没有的，即该待处理客户名单为新的客户信息，此时名单除重***则在有效客户数据库中新建名单，将该待处理客户名单中的信息全部保存到该新建名单中，并将该待处理客户名单删除，即在有效客户数据库中新增了一个没有第一类型标识的客户名单。
若查找到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则将所述待处理客户名单进行除重。
当名单除重***在有效客户数据库中查找到了与该待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则说明该待处理客户名单的信息在有效客户数据库中存在，且由于该待处理客户名单没有第一类型标识，因此没必要将一个没有第一类型标识且与有效客户数据库中的客户名单存在信息重复名单保存，故名单除重***直接将该待处理客户名单删除。
本发明还提出一种名单除重***。
请参阅图3，是本发明名单除重***10较佳实施例的运行环境示意图。
在本实施例中，名单除重***10安装并运行于电子装置1中。电子装置1可以是桌上型计算机、笔记本、掌上电脑及服务器等计算设备。该电子装置1可包括，但不仅限于，存储器11、处理器12及显示器13。图3仅示出了具有组件11-13的电子装置1，但是应理解 的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
存储器11在一些实施例中可以是电子装置1的内部存储单元，例如该电子装置1的硬盘或内存。存储器11在另一些实施例中也可以是电子装置1的外部存储设备，例如电子装置1上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，存储器11还可以既包括电子装置1的内部存储单元也包括外部存储设备。存储器11用于存储安装于电子装置1的应用软件及各类数据，例如名单除重***10的程序代码等。存储器11还可以用于暂时地存储已经输出或者将要输出的数据。
处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)，微处理器或其他数据处理芯片，用于运行存储器11中存储的程序代码或处理数据，例如执行名单除重***10等。
显示器13在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。显示器13用于显示在电子装置1中处理的信息以及用于显示可视化的用户界面，例如业务定制界面等。电子装置1的部件11-13通过***总线相互通信。
请参阅图4，是本发明名单除重***10一实施例的程序模块图。在本实施例中，名单除重***10可以被分割成一个或多个模块，一个或者多个模块被存储于存储器11中，并由一个或多个处理器(本实施例为处理器12)所执行，以完成本发明。例如，在图4中，名单除重***10可以被分割成获取模块101、第一查找模块102、第二查找模块103、第一查看模块104、比对模块105及第一除重模块106。本发明所称的模块是指能够完成特定功能的一系列计算机程序指令段，比程序更适合于描述名单除重***10在电子装置1中的执行过程，其中：
获取模块101，用于从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
本实施例中，待处理客户名单是业务***在作业中产生的记录有客户信息的名单，新产生的待处理客户名单全部存储到待处理数据库中，名单除重***10定时对待处理数据库中的待处理客户名单进行处理。待处理客户名单中可包含第一类型标识(例如，用户名、注册名等)、第二类型标识(例如，注册手机号、注册证件号等)和第三类型标识(例如，常用联系号码)，其中，第一类型标识是客户的唯一识别码；本实施例中，待处理数据库中，部分处理客户名单可能没有第一类型标识，部分处理客户名单甚至可能没有第一类型标识和第 二类型标识。本实施例优选采用第一类型标识为用户ID，第二类型标识为注册手机号，第三类型标识为常用联系号码，且第三类型标识可为多个。本实施例名单除重***10以逐一获取的方式获取待处理数据库中的待处理客户名单，先查看获取到的待处理客户名单有没有第一类型标识。
第一查找模块102，用于在确定所述待处理客户名单具有第一类型标识后，在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
在确认该待处理客户名单具有第一类型标识后，名单除重***10则在有效客户数据中查找第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，以确定有效客户数据库中是否已经存有相同第一类型标识的客户名单。如果在有效客户数据中查找到第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，由于第一类型标识是客户的唯一识别码，即说明该查找到的客户名单与该待处理客户名单为同一客户的信息，又由于该待处理客户名单中为最新记录的客户的相关信息，因此名单除重***10将根据该待处理客户名单对查找到的客户名单进行信息更新，使该有效客户数据库中保存该第一类型标识的客户名单的最新信息。
第二查找模块103，用于在没有查找到与所述待处理客户名单的第一类型标识相同的客户名单后，在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
如果名单除重***10在有效客户数据库中没有找到第一类型标识与该待处理客户名单的第一类型标识相同的客户名单，由于有效数据库中也存有未记录第一类型标识的客户名单，故此时并不能确认有效客户数据库中没有与该待处理客户名单中的信息重复的客户名单；因此名单除重***10通过第二类型标识进行进一步的查找，即再在有效客户数据库中查找第二类型标识与该待处理客户名单的第二类型标识相同的客户名单，以确认该待处理客户名单中的第二类型标识之前有没有被注册过。
第一查看模块104，用于在查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单后，查看所述查找到的客户名单是否具有第一类型标识；
当名单除重******在有效客户数据库中找到了第二类型标识与该待处理客户名单的第二类型标识相同的客户名单时，说明该第二类型标识已经被注册过，此时查看该查找到的客户名单是否已经具有第一类型标识，以确认该第二类型标识之前是不是被其它第一类型标识注册。如果名单除重***10从该查找到的客户名单中没有发现第一类型标识，则根据两者的第二类型标识相同可确认该查找到的客户 名单与该待处理客户名单为同一客户的信息，此时名单除重***10将根据该待处理客户名单中的信息对该查找到的客户名单的进行信息更新，即以该待处理客户名单中的信息保存到该查找到的客户名单中，该查找到的客户名单更新后则具有第一类型标识。
比对模块105，用于在所述查找到的客户名单具有第一类型标识后，根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
当名单除重***10从该查找到的客户名单中找到了第一类型标识，且由于名单除重***10最先通过该待处理客户名单的第一类型标识在有效数据库中查找时没有找到相同第一类型标识的客户名单，则说明通过该待处理客户名单的第二类型标识查找到的客户名单的第一类型标识与该待处理客户名单的第一类型标识不同，即出现了一个第二类型标识对应两个第一类型标识的情形，这种情形是不允许的；造成这种情形的原因可能为：1、由于有效客户数据库中的客户名单的信息不是最新信息，该查找到的客户名单的客户可能已经将注销了该第二类型标识，该第二类型标识现在是别人在使用；2、该第二类型标识的客户又使用该第二类型标识以不同第一类型标识进行注册；3、该第二类型标识被其它人用作第二类型标识进行注册。出现这种情形时，为确认是上面那种原因造成，名单除重***10根据所述待处理数据库对该查找到的客户名单的信息进行刷新，使该查找到的客户名单中的第二类型标识信息最新，刷新后，再将该查找到的客户名单的第二类型标识与所述待处理客户名单的第二类型标识比对。
第一除重模块106，用于在所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识比对上后，将所述待处理客户名单进行除重。
当所述查找到的客户名单被刷新信息后，第二类型标识仍然与所述待处理客户名单的第二类型标识一致，则说明所述待处理客户名单的第二类型标识已经被所述查找到的客户名单的第一类型标识所注册，且该第二类型标识仍在被所述查找到的客户名单的第一类型标识使用，不允许其它第一类型标识再以该第二类型标识进行重复注册，故名单除重***将所述待处理客户名单除重，即将该待处理客户名单删除。
本实施例技术方案，首先通过待处理客户名单中的唯一识别码第一类型标识在有效客户数据库中查找是否有该第一类型标识的客户名单，在通过第一类型标识未查找到时，再通过待处理客户名单中的第二类型标识在有效客户数据库中查找；当通过待处理客户名单的第 二类型标识查找到了相同第二类型标识的客户名单后，且查找到的客户名单已经有第一类型标识，则根据待处理数据库对查找到的客户名单进行信息刷新，刷新后的该客户名单的第二类型标识再与所述待处理客户名单的第二类型标识进行比对，如果第二类型标识仍然一致，则将当前待处理客户名单进出除重。与现有技术相比，本实施例方案避免了仅根据ID查找进行除重的方式存在的除重不彻底的问题，也避免了仅根据手机号除重的方式造成误除重的问题，使得提升了名单除重的效果和准确性。
本实施例中，所述比对模块105根据所述待处理数据库刷新所述查找到的客户名单的信息的操作具体为：在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
因为待处理数据库中存储着最新的客户信息，因此，比对模块105通过查找到的客户名单的第一类型标识去待处理数据库中匹配相同第一类型标识的待处理客户名单，以找出该第一类型标识的客户最新信息。如果该待处理数据库中有与该查找到的客户名单的第一类型标识相同的待处理客户名单，则比对模块105在匹配到该第一类型标识的待处理客户名单后，根据该匹配到的待处理客户名单中的信息更新该查找到的客户名单，使该查找到的客户名单中的信息最新，即也更新了其第二类型标识。另外，若该待处理数据库中没有与该查找到的客户名单的第一类型标识相同的待处理客户名单，则保持该查找到的客户名单的信息不变。
参照图5，本实施例的名单除重***10还包括：
搜寻模块107，用于在所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识不相同后，从所述有效客户数据库中搜寻第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
当所述查找到的客户名单进行信息刷新后，其第二类型标识与待处理客户名单的第二类型标识不一致了，则说明该查找到的客户名单已经变更了第二类型标识，其之前的第二类型标识已经注销，故该待处理客户名单中的第二类型标识没有与有效客户数据库中的客户名单的第二类型标识冲突，该待处理客户名单的第二类型标识有效；此时名单除重***10进一步从所述有效客户数据库中搜寻第三类型标识与该待处理客户名单的第二类型标识相同的客户名单。
第一新建模块108，用于在从所述有效客户数据库中没有搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名 单后，在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
如果名单除重***10没在有效客户数据库中搜寻到与该待处理客户名单的第二类型标识相同的第三类型标识，则有效客户数据库中没有与该待处理名的第二类型标识关联的客户名单，确认该待处理客户名单为新名单，名单除重***10则通过在有效客户数据库中新建名单，并将该待处理客户名单中的信息保存到该新建名单中，形成有效客户数据库中新增的客户名单，并将该待处理客户名单删除。
第二查看模块109，用于在从所述有效客户数据库中搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单后，分析所述搜寻到的客户名单是否具有第二类型标识；
当名单除重***10搜寻到有客户名单的第三类型标识中含有所述待处理客户名单的第二类型标识时，则进一步地查看该搜寻到的客户名单有没有第二类型标识。
合并模块110，用于在确定所述搜寻到的客户名单没有第二类型标识后，将所述待处理客户名单与所述搜寻到的客户名单进行信息合并；
当该搜寻到的客户名单中没有第二类型标识，则说明该搜寻到的客户名单的信息不是已有注册客户的信息，且该搜寻到的客户名单信息与该待处理客户名单的信息相关联，因此将搜寻到的客户名单与该待处理客户名单进行信息合并以形成最新的客户名单，即将该待处理客户名单中的信息合并到搜寻到的客户名单中，并将该待处理客户名单删除。
第二新建模块111，用于在确定所述搜寻到的客户名单具有第二类型标识后，在所述有效客户数据库中新建名单，将所述待处理客户名单中的信息保存到所述新建名单中，并将所述搜寻到的客户名单的与所述待处理客户名单的第二类型标识相同的第三类型标识清除。
当该搜寻到的客户名单已经具有第二类型标识，说明该待处理客户名单与该搜寻到的客户名单分别为不同客户的信息；由于该搜寻到的客户名单中的与该待处理客户名单的第二类型标识相同的第三类型标识，现已经作为该待处理客户名单的第二类型标识，因此该搜寻到的客户名单中的该第三类型标识应当删除；出现这种情况的原因可能是该第三类型标识早已经被客户注销，只是还没有进行信息更新。此时名单除重***10将该待处理客户名单的信息通过保存到有效客户数据库中的新建名单内以形成新的客户名单；并且将该搜寻到的客户名单中的与所述待处理客户名单的第二类型标识相同的第三类型标识清除，以更新该搜寻到的客户名单的信息。
参照图6，本实施例的名单除重***10还包括：
第三查找模块112，用于在待处理客户名单没有第一类型标识时，在有效客户数据库中查找第二类型标识或第三类型标识与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单；
当名单除重***10确定该待处理客户名单没有第一类型标识时，则在有效客户数据库中查找包括该待处理客户名单的第二类型标识或第三类型标识的客户名单，确定该没有第一类型标识的待处理客户名单的信息在有效客户数据库中是否存在。
第三新建模块113，用于在查找不到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单时，在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
如果名单除重***10在有效客户数据库中查不到与该待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则说明该待处理客户名单的第二类型标识和第三类型标识都是有效客户数据库中没有的，即该待处理客户名单为新的客户信息，此时名单除重***10则在有效客户数据库中新建名单，将该待处理客户名单中的信息全部保存到该新建名单中，即在有效客户数据库中新增了一个没有第一类型标识的客户名单。
第二除重模块114，用于在查找到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单后，将所述待处理客户名单进行除重。
当名单除重***10在有效客户数据库中查找到了与该待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则说明该待处理客户名单的信息在有效客户数据库中存在，且由于该待处理客户名单没有第一类型标识，因此没必要将一个没有第一类型标识且与有效客户数据库中的客户名单存在信息重复名单保存，故名单除重***10直接将该待处理客户名单删除。
本发明还提出一种计算机可读存储介质，该计算机可读存储介质存储有信息查询控制***，所述信息查询控制***可被至少一个处理器执行，以使所述至少一个处理器执行上述任一实施例中的名单除重方法。
以上所述仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是在本发明的发明构思下，利用本发明说明书及附图内容所作的等效结构变换，或直接/间接运用在其他相关的技术领域均包括在本发明的专利保护范围内。

Claims (20)

  1. 一种电子装置，其特征在于，所述电子装置包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的名单除重***，所述名单除重***被所述处理器执行时实现如下步骤：
    A1、从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
    B1、若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
    C1、若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    D1、若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
    E1、若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
    F1、若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
  2. 如权利要求1所述的电子装置，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  3. 如权利要求1所述的电子装置，其特征在于，于所述步骤E1之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识不相同，则从所述有效客户数据库中搜寻第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    若从所述有效客户数据库中没有搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若从所述有效客户数据库中搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则分析所述搜寻到的客户名单是否具有第二类型标识；
    若所述搜寻到的客户名单没有第二类型标识，则将所述待处理客户名单与所述搜寻到的客户名单进行信息合并；
    若所述搜寻到的客户名单具有第二类型标识，则在所述有效客户数据库中新建名单，将所述待处理客户名单中的信息保存到所述新建名单中，并将所述搜寻到的客户名单的与所述待处理客户名单的第二类型标识相同的第三类型标识清除。
  4. 如权利要求3所述的电子装置，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  5. 如权利要求1所述的电子装置，其特征在于，于所述步骤A1之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若待处理客户名单没有第一类型标识，则在有效客户数据库中查找第二类型标识或第三类型标识与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单；
    若查找不到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若查找到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则将所述待处理客户名单进行除重。
  6. 如权利要求5所述的电子装置，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  7. 如权利要求1所述的电子装置，其特征在于，于所述步骤D1之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若所述查找到的客户名单没有第一类型标识，则根据所述待处理 客户名单的信息更新所述查找到的客户名单。
  8. 如权利要求7所述的电子装置，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  9. 一种名单除重方法，其特征在于，该方法包括步骤：
    A2、从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
    B2、若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
    C2、若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    D2、若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
    E2、若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
    F2、若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
  10. 如权利要求9所述的名单除重方法，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  11. 如权利要求9所述的名单除重方法，其特征在于，于所述步骤E2之后，所述名单除重方法还包括步骤：
    若所述待处理客户名单的第二类型标识与所述查找到的客户名 单的第二类型标识不相同，则从所述有效客户数据库中搜寻第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    若从所述有效客户数据库中没有搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若从所述有效客户数据库中搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则分析所述搜寻到的客户名单是否具有第二类型标识；
    若所述搜寻到的客户名单没有第二类型标识，则将所述待处理客户名单与所述搜寻到的客户名单进行信息合并；
    若所述搜寻到的客户名单具有第二类型标识，则在所述有效客户数据库中新建名单，将所述待处理客户名单中的信息保存到所述新建名单中，并将所述搜寻到的客户名单的与所述待处理客户名单的第二类型标识相同的第三类型标识清除。
  12. 如权利要求11所述的名单除重方法，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  13. 如权利要求9所述的名单除重方法，其特征在于，于所述步骤A2之后，所述名单除重方法还包括步骤：
    若待处理客户名单没有第一类型标识，则在有效客户数据库中查找第二类型标识或第三类型标识与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单；
    若查找不到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若查找到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则将所述待处理客户名单进行除重。
  14. 如权利要求13所述的名单除重方法，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  15. 如权利要求9所述的名单除重方法，其特征在于，于所述步骤D2之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若所述查找到的客户名单没有第一类型标识，则根据所述待处理客户名单的信息更新所述查找到的客户名单。
  16. 如权利要求15所述的名单除重方法，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
  17. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有信息查询控制***，所述信息查询控制***可被至少一个处理器执行，以使所述至少一个处理器执行如下操作：
    A3、从待处理数据库中逐个获取待处理客户名单，分析获取到的待处理客户名单是否具有第一类型标识；
    B3、若所述待处理客户名单具有第一类型标识，则在有效客户数据库中查找第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单；
    C3、若没有查找到第一类型标识与所述待处理客户名单的第一类型标识相同的客户名单，则在有效客户数据库中查找第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    D3、若查找到第二类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则查看所述查找到的客户名单是否具有第一类型标识；
    E3、若所述查找到的客户名单具有第一类型标识，则根据所述待处理数据库刷新所述查找到的客户名单的信息，再将所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识进行比对；
    F3、若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识相同，则将所述待处理客户名单进行除重。
  18. 如权利要求17所述的计算机可读存储介质，其特征在于， 于所述步骤E3之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若所述待处理客户名单的第二类型标识与所述查找到的客户名单的第二类型标识不相同，则从所述有效客户数据库中搜寻第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单；
    若从所述有效客户数据库中没有搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若从所述有效客户数据库中搜寻到第三类型标识与所述待处理客户名单的第二类型标识相同的客户名单，则分析所述搜寻到的客户名单是否具有第二类型标识；
    若所述搜寻到的客户名单没有第二类型标识，则将所述待处理客户名单与所述搜寻到的客户名单进行信息合并；
    若所述搜寻到的客户名单具有第二类型标识，则在所述有效客户数据库中新建名单，将所述待处理客户名单中的信息保存到所述新建名单中，并将所述搜寻到的客户名单的与所述待处理客户名单的第二类型标识相同的第三类型标识清除。
  19. 如权利要求17所述的计算机可读存储介质，其特征在于，于所述步骤A3之后，所述处理器还用于执行所述名单除重***，以实现如下步骤：
    若待处理客户名单没有第一类型标识，则在有效客户数据库中查找第二类型标识或第三类型标识与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单；
    若查找不到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则在所述有效客户数据库中新建名单，并将所述待处理客户名单中的信息保存到所述新建名单中；
    若查找到与所述待处理客户名单的第二类型标识或第三类型标识相同的客户名单，则将所述待处理客户名单进行除重。
  20. 如权利要求17所述的计算机可读存储介质，其特征在于，所述根据所述待处理数据库刷新所述查找到的客户名单的信息的步骤包括：
    在所述待处理数据库中匹配第一类型标识与所述查找到的客户名单的第一类型标识相同的待处理客户名单；
    在匹配到待处理客户名单后，根据所述匹配到的待处理客户名单对所述查找到的客户名单进行信息更新。
PCT/CN2017/105025 2017-07-25 2017-09-30 电子装置、名单除重方法和计算机可读存储介质 WO2019019401A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
SG11201901800VA SG11201901800VA (en) 2017-07-25 2017-09-30 Electronic device, list deduplication method and computer-readable storage medium
JP2018553483A JP6648307B2 (ja) 2017-07-25 2017-09-30 電子装置、名簿エントリの重複排除方法及びコンピュータ読み取り可能な記憶媒体
US16/089,385 US20210081380A1 (en) 2017-07-25 2017-09-30 Electronic Device, List Deduplication Method and Computer-Readable Storage Medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710614495.0A CN107688603B (zh) 2017-07-25 2017-07-25 电子装置、名单除重方法和计算机可读存储介质
CN201710614495.0 2017-07-25

Publications (1)

Publication Number Publication Date
WO2019019401A1 true WO2019019401A1 (zh) 2019-01-31

Family

ID=61152987

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105025 WO2019019401A1 (zh) 2017-07-25 2017-09-30 电子装置、名单除重方法和计算机可读存储介质

Country Status (5)

Country Link
US (1) US20210081380A1 (zh)
JP (1) JP6648307B2 (zh)
CN (1) CN107688603B (zh)
SG (1) SG11201901800VA (zh)
WO (1) WO2019019401A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108805587A (zh) * 2018-06-14 2018-11-13 泰康保险集团股份有限公司 一种客户信息处理方法、装置、介质和电子设备
CN109461009A (zh) * 2018-11-13 2019-03-12 泰康保险集团股份有限公司 一种电销客户资料数据下发的方法、装置、设备和介质
CN110335069B (zh) * 2019-06-19 2024-07-02 中国平安财产保险股份有限公司 一种统计首拨进度的方法、装置、计算机设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070100929A1 (en) * 2005-10-27 2007-05-03 International Business Machines Corporation Method, system and program storage device for assigning unique identification numbers to new user accounts and groups in a computing environment with multiple registries
CN103118043A (zh) * 2011-11-16 2013-05-22 阿里巴巴集团控股有限公司 一种用户账号的识别方法及设备
CN103312701A (zh) * 2013-05-30 2013-09-18 腾讯科技（深圳）有限公司 一种联系人信息整合方法、服务器、终端以及***
CN104573094A (zh) * 2015-01-30 2015-04-29 深圳市华傲数据技术有限公司 网络账号识别匹配方法
CN105956435A (zh) * 2016-06-07 2016-09-21 微梦创科网络科技（中国）有限公司 一种移动app的注册、以及登陆方法和装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8417696B2 (en) * 2010-06-10 2013-04-09 Microsoft Corporation Contact information merger and duplicate resolution
US9173072B2 (en) * 2012-08-28 2015-10-27 Facebook, Inc. Methods and systems for verification in account registration
CN102905002A (zh) * 2012-10-31 2013-01-30 广东欧珀移动通信有限公司 一种自动合并联系人条目的方法和***
CN103716401A (zh) * 2013-12-31 2014-04-09 北京飞流九天科技有限公司 用于管理通讯录的方法、终端和服务器
CN104219360B (zh) * 2014-08-01 2017-08-01 小米科技有限责任公司 信息处理方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070100929A1 (en) * 2005-10-27 2007-05-03 International Business Machines Corporation Method, system and program storage device for assigning unique identification numbers to new user accounts and groups in a computing environment with multiple registries
CN103118043A (zh) * 2011-11-16 2013-05-22 阿里巴巴集团控股有限公司 一种用户账号的识别方法及设备
CN103312701A (zh) * 2013-05-30 2013-09-18 腾讯科技（深圳）有限公司 一种联系人信息整合方法、服务器、终端以及***
CN104573094A (zh) * 2015-01-30 2015-04-29 深圳市华傲数据技术有限公司 网络账号识别匹配方法
CN105956435A (zh) * 2016-06-07 2016-09-21 微梦创科网络科技（中国）有限公司 一种移动app的注册、以及登陆方法和装置

Also Published As

Publication number Publication date
JP2019528493A (ja) 2019-10-10
US20210081380A1 (en) 2021-03-18
CN107688603A (zh) 2018-02-13
SG11201901800VA (en) 2019-04-29
CN107688603B (zh) 2019-03-26
JP6648307B2 (ja) 2020-02-14

Similar Documents

Publication Publication Date Title
JP4688111B2 (ja) 情報処理装置、データベース・システム、情報処理方法、およびプログラム
CA2850672C (en) Entity resolution
US9798762B2 (en) Real time big data master data management
US11256690B2 (en) Using row value constructor (RVC) based queries to group records of a database for multi-thread execution
US9996607B2 (en) Entity resolution between datasets
US8214411B2 (en) Atomic deletion of database data categories
US8805777B2 (en) Data record collapse and split functionality
JP2020140699A (ja) データを記憶およびクエリするための方法、装置、設備、および媒体
US20150363468A1 (en) Query handling in a columnar database
WO2019019401A1 (zh) 电子装置、名单除重方法和计算机可读存储介质
US10311111B2 (en) Search method and apparatus and storage medium
EP2863311A2 (en) Domain centric test data generation
US10013315B2 (en) Reverse snapshot clone
US9336245B2 (en) Systems and methods providing master data management statistics
CN109815240A (zh) 用于管理索引的方法、装置、设备和存储介质
US20150081616A1 (en) Database insert with deferred materialization
EP2752778B1 (en) Method and system for creating and maintaining unique data repository
EP3318988A1 (en) Transaction-based refresh of a long database transaction's workspace
US8909681B2 (en) Gap detection in a temporally unique index in a relational database
WO2019071899A1 (zh) 电子装置、车辆数据导入方法及存储介质
CN107004036B (zh) 用以搜索包含大量条目的日志的方法和***
JP2007334412A (ja) 検索プログラムおよび検索装置
WO2019080427A1 (zh) 医疗数据清洗方法、电子装置及存储介质
US20230030246A1 (en) Utilizing progress identifiers to rewrite an event query
US20150081380A1 (en) Complement self service business intelligence with cleansed and enriched customer data

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018553483

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05.08.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17919335

Country of ref document: EP

Kind code of ref document: A1