Offline blacklist synchronization method, system and device and storage medium

Abstract

The invention relates to an offline blacklist synchronization method, system and device and a storage medium, and relates to the field of software design. The method is based on a blacklist management system comprising an application background end and an equipment end, and comprises the following steps: reading a full-version blacklist library of the application background end, and generating a Bloom filter according to the full-version blacklist library; generating initial configuration information of a full-version blacklist library by using a Bloom filter; when blacklist updating information of the application background end is received, generating updating configuration information of the initial configuration information according to the blacklist updating information; updating a full-version blacklist library according to the update configuration information; and when an update request of the equipment end is received, reading the blacklist configuration of the equipment end, and updating the equipment blacklist configuration according to update configuration information to obtain synchronous equipment blacklist configuration. The technical effect of the invention is that the offline blacklist synchronization efficiency of the application background end and the device end and the offline blacklist matching efficiency of the device end are improved.

Description

Technical Field

[0001] The present application relates to the field of information processing, and in particular to an offline blacklist synchronization method, system, device and storage medium. Background Art

[0002] Blacklist synchronization refers to updating the blacklist information in the device or application background to the other party in real time or regularly to ensure that the blacklist data of both parties remains consistent.

[0003] Usually, the application background uses the full + incremental list to send the blacklist to the device. Due to the large number of blacklists, a single full list download takes a long time, and the incremental list cannot be increased indefinitely. After reaching a certain data, it needs to be merged into the full list, which will cause the device to need to update the full list periodically, which will result in low blacklist synchronization efficiency. Summary of the invention

[0004] In order to improve the blacklist synchronization efficiency between the application backend and the device end, the present application provides an offline blacklist synchronization method, system, device and storage medium.

[0005] In a first aspect, the present application provides an offline blacklist synchronization method, which adopts the following technical solution:

[0006] Read the full version blacklist library of the application backend, and generate a Bloom filter according to the full version blacklist library;

[0007] Generating initial configuration information of the full version blacklist library using the Bloom filter;

[0008] When receiving the blacklist update information from the application backend, generating update configuration information of the initial configuration information according to the blacklist update information;

[0009] Update the full version blacklist library according to the update configuration information;

[0010] When an update request from the device is received, the blacklist configuration of the device is read, and the device blacklist configuration is updated according to the update configuration information to obtain a synchronized device blacklist configuration.

[0011] Through the above technical solution, the present application realizes the synchronization of the blacklist by updating the configuration information, avoids the download of the full list, and greatly improves the update frequency and update speed of the offline blacklist.

[0012] In a specific implementation scheme, the full version blacklist library includes an initial blacklist and an initial whitelist, and the initial configuration information of the full version blacklist library generated by using the Bloom filter includes:

[0013] Filtering the full version blacklist library according to the Bloom filter, storing the filtering results of the initial blacklist by page in the form of a hex array, and recording the page number position and hash value of the initial blacklist;

[0014] A whitelist index is generated according to the page number position, and the initial whitelist is searched according to the hash value to generate a whitelist list.

[0015] Through the above technical solution, only one full download is required to generate the initial configuration information, and subsequent blacklist modifications only need to be made according to the updated content, and no full download is required, thereby improving the blacklist synchronization efficiency.

[0016] In a specific implementation scheme, the blacklist update information includes an updated blacklist card number, and the updated configuration information for generating the initial configuration information according to the blacklist update information includes:

[0017] Generate the updated content and updated page number position in the hex array according to the updated blacklist card number using the Bloom filter, and record the updated hash value of the blacklist updated card number;

[0018] Generate an update whitelist list and an update whitelist index according to the update page number position and the update hash value;

[0019] The update configuration information of the initial configuration information is cached in the application backend, wherein the update configuration information includes the update content, the update page position, the update whitelist index and the update whitelist list.

[0020] Through the above technical solution, the updated configuration information is first obtained according to the blacklist update information, and the updated configuration information does not require a phased full list update, thereby improving the blacklist synchronization efficiency.

[0021] In a specific implementation scheme, the application backend includes a blacklist version number corresponding to the full version blacklist library, and updating the full version blacklist library according to the update configuration information includes:

[0022] When receiving the curing instruction from the application backend, recording the date and time information and generating the target blacklist version number according to the date and time information;

[0023] Update the full version blacklist library and the blacklist version number according to the target blacklist version number and the update configuration information;

[0024] After the update is completed, the update configuration information is cleared.

[0025] Through the above technical solution, the present application realizes the synchronization of the blacklist by updating the configuration information, avoids the download of the full list, and greatly improves the update frequency and update speed of the offline blacklist.

[0026] In a specific implementation scheme, reading the blacklist configuration of the device includes:

[0027] Determine whether the blacklist version number is updated;

[0028] If the blacklist version number is updated, the blacklist configuration of the device is read.

[0029] Through the above technical solution, by setting the blacklist version number, the device side can know whether the background side is updated according to whether the blacklist version number is updated, so as to start the device side blacklist synchronization.

[0030] In a specific implementation scheme, the synchronization device blacklist configuration includes a Bloom filter, a whitelist index and a whitelist list, and after the synchronization device blacklist configuration is updated according to the update configuration information to obtain the synchronization device blacklist configuration, it also includes:

[0031] When receiving a card number query instruction from the device, the card number query instruction includes the card number to be queried, calculating a hash value of the card number, and determining whether the hash value is in a Bloom filter;

[0032] If the hash value is in the Bloom filter, the unusable card number is identified according to the hash value, the whitelist index and the whitelist.

[0033] In a specific implementation scheme, identifying an unusable card number based on the hash value, the whitelist index and the whitelist includes:

[0034] Determine whether there is a hash value conflict;

[0035] If there is no hash value conflict, it is determined that the card number cannot be used;

[0036] If there is a hash value conflict, the whitelist index is queried according to the hash value, and the whitelist is queried according to the whitelist index. The whitelist includes a whitelist card number. If the whitelist card number is inconsistent with the card number, it is determined that the card number cannot be used.

[0037] Through the above technical solution, the blacklist is matched through the Bloom filter, the whitelist index and the whitelist. After filtering by the Bloom filter, the blacklist is matched from the reverse side starting from the whitelist with a smaller number, so that the blacklist matching efficiency is improved.

[0038] In a second aspect, the present application provides an offline blacklist management system, which adopts the following technical solution: the system includes:

[0039] A Bloom filter generation module, used to read the full version blacklist library of the application backend, and generate a Bloom filter according to the full version blacklist library;

[0040] An initial configuration information generating module, used to generate initial configuration information of the full version blacklist library by using the Bloom filter;

[0041] An update configuration information generation module, configured to generate update configuration information of the initial configuration information according to the blacklist update information when receiving the blacklist update information from the application backend;

[0042] An application backend update module is used to update the full version blacklist library according to the update configuration information;

[0043] The device-side update module is used to read the blacklist configuration of the device-side when receiving an update request from the device-side, and update the device blacklist configuration according to the update configuration information to obtain a synchronized device blacklist configuration.

[0044] In a third aspect, the present application provides a computer device, which adopts the following technical solution: it includes a memory and a processor, and the memory stores a computer program that can be loaded by the processor and executes the above-mentioned offline blacklist synchronization method.

[0045] In a fourth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solution: storing a computer program that can be loaded by a processor and execute the above-mentioned offline blacklist synchronization method.

[0046] In summary, this application has the following beneficial technical effects:

[0047] (1) This application realizes the synchronization of the blacklist by updating the configuration information, avoiding the download of the full list, and greatly improving the synchronization frequency and speed of the offline blacklist.

[0048] (2) The blacklist is matched through the Bloom filter, the whitelist index and the whitelist. After filtering by the Bloom filter, the blacklist is matched from the reverse side starting from the whitelist with a smaller number, thereby improving the blacklist matching efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 This is a flowchart of offline blacklist synchronization in an embodiment of the present application.

[0050] Figure 2 This is a flowchart of blacklist matching in an embodiment of the present application.

[0051] Figure 3 It is a structural block diagram of an offline blacklist synchronization in an embodiment of the present application.

[0052] Reference numerals: 301, Bloom filter generation module; 302, initial configuration information generation module; 303, update configuration information generation module; 304, application backend update module; 305, device end update module. DETAILED DESCRIPTION

[0053] The following is combined with Figure 1-3 This application is described in further detail.

[0054] The embodiments of the present application disclose an offline blacklist synchronization method, system, device and storage medium, which are used to improve the blacklist synchronization efficiency between the application background end and the device end.

[0055] Blacklist synchronization refers to updating the blacklist information in the device or application background to the other party in real time or regularly to ensure that the blacklist data of both parties remains consistent.

[0056] Usually, the application background uses the full + incremental list to send the blacklist to the device. Due to the large number of blacklists, a single full list download takes a long time, and the incremental list cannot be increased indefinitely. After reaching a certain data, it needs to be merged into the full list, which will cause the device to need to update the full list periodically, which will result in low blacklist synchronization efficiency.

[0057] Therefore, the present application proposes an offline blacklist synchronization method, which is used to improve the blacklist synchronization efficiency between the application background end and the device end.

[0058] like Figure 1 As shown, the method is based on a blacklist management system including an application backend and a device end, and the method specifically includes the following steps:

[0059] S10, read the full version blacklist library of the application backend, and generate a Bloom filter according to the full version blacklist library.

[0060] Specifically, the application backend of this application masters the full version blacklist library (the full version blacklist library not only refers to the blacklist, but the list of all card numbers in the system used for hash conflict judgment), reads the full version blacklist library of the application backend, and generates a Bloom filter based on the full version blacklist library. The number and length of the Bloom filters can be calculated based on the total number of lists and the proportion of blacklist card numbers, and are uniformly generated by the application backend. The storage structure of the Bloom filter is several HEX arrays, and each array corresponds to a hash algorithm, i.e., a hash function.

[0061] S20, using the Bloom filter to generate initial configuration information of the full version blacklist library.

[0062] Specifically, when the blacklist is first encountered, the application backend needs to generate the initial configuration information of the blacklist and synchronize it to the device. The initial configuration information mainly includes several hex arrays of the Bloom filter, the whitelist index, and the whitelist list corresponding to the whitelist index.

[0063] S30, when the blacklist update information is received from the application backend, the update configuration information of the initial configuration information is generated according to the blacklist update information.

[0064] Specifically, when the blacklist is updated, the application backend first receives the blacklist update information, which will contain the changed blacklist card numbers and changes (increases or decreases). The Bloom filter is used to generate the corresponding update configuration information based on the blacklist update information. For example, for changes to several hex arrays, only the page content that needs to be updated needs to be updated. Regarding changes to the whitelist index, the blacklist update causes the hex array page to be updated. Since each whitelist index corresponds to a page of each hex array in the Bloom filter, the whitelist index corresponding to the updated hex array page only needs to be updated. Regarding changes to the whitelist list, the blacklist update will cause changes to the whitelist that will cause hash value conflicts, and the whitelist list that stores the whitelist card numbers will change accordingly. The starting address and offset that need to be updated for the whitelist index are generated based on the updated storage location of the whitelist card number.

[0065] S40, updating the full version blacklist library according to the update configuration information.

[0066] Specifically, the update configuration information is cached first, and when the blacklist version solidification instruction is triggered, the full version blacklist library is updated according to the update configuration information.

[0067] S50, when an update request from the device is received, the blacklist configuration of the device is read, and the device blacklist configuration is updated according to the update configuration information to obtain a synchronized device blacklist configuration.

[0068] Specifically, after the blacklist on the application backend is changed, the blacklist on the application backend and the device are out of sync, so the device sends an update request. When the blacklist is first contacted, the application backend needs to generate the initial configuration information of the blacklist and synchronize it to the device. The device has the blacklist configuration, and converts the updated configuration information of the application backend into an update protocol that can be run on the device, and updates and synchronizes the blacklist configuration.

[0069] This application achieves blacklist synchronization by updating configuration information, avoiding the download of the full list and greatly improving the synchronization frequency and speed of the offline blacklist.

[0070] In one embodiment, in order to improve the blacklist synchronization efficiency, the step of using the Bloom filter to generate the initial configuration information of the full version blacklist library can be specifically performed as follows:

[0071] First, add the initial blacklist to the Bloom filter. The Bloom filter is stored in the form of a hex array by page, and the page number position and hash value of the initial blacklist are recorded. The whitelist index is generated according to the page number position, and the initial whitelist is searched according to the hash value to generate the whitelist list. Specifically, the initial configuration information is generated as follows: the Bloom filter uses a number of hex arrays to store status information, and the initial value of all bits is 0. When a blacklist card number is to be added to the Bloom filter, the Bloom filter uses a number of hash functions to determine the corresponding position of the blacklist card number on the hex arrays, sets the bits at these positions to 1, and records its hash value. Repeat the above steps of adding the blacklist card number to the Bloom filter, add all the blacklist card numbers of the initial blacklist to the Bloom filter, divide each hex array into a page of 256 bytes, and when the blacklist is updated, only the content of the changed page is updated to achieve the blacklist update effect.

[0072] When a hash value conflict occurs, it will cause the Bloom filter to misjudge. In order to reduce misjudgment, an additional whitelist can be provided for comparison. The hash value of the initial whitelist is calculated by the hash function. If the hash value of the initial whitelist is consistent with the hash value of the initial blacklist, an additional whitelist needs to be provided. First, a whitelist index is generated. Each whitelist index corresponds to a page of each hex array in the Bloom filter. The index consists of a start address and an offset. Generally speaking, the default length of the start address is 4 bytes, and the default length of the offset is 2 bytes. The specific length can be adjusted according to the actual total blacklist. Each start address and offset is a group; then a whitelist list corresponding to the whitelist index is established, and the whitelist card number corresponding to the hash value conflict on a page of each hex array is stored in the whitelist list. The start address and offset of the whitelist index are generated according to the storage location of the whitelist card number. The whitelist list is used to list the whitelist of the conflicting lists in the Bloom filter. When a hash value conflict occurs during the blacklist matching process, it is convenient to quickly match. The storage and reading of the whitelist refer to the disk access mode to ensure that the list within a single index range is continuous.

[0073] In actual operation, this application solution only needs to download the initial configuration information once. Subsequent blacklist modifications only need to be made according to the updated content, and no full download is required, which improves the blacklist synchronization efficiency. At the same time, in addition to blacklist-related information, the initial configuration also includes whitelist information with hash value conflicts, which improves the blacklist matching efficiency on the device side.

[0074] In one embodiment, the blacklist update information includes updating the blacklist card number, and the step of generating the update configuration information of the initial configuration information according to the blacklist update information can be specifically performed as follows:

[0075] First, the Bloom filter is used to generate the updated content and updated page number position in the hex array according to the updated blacklist card number, and the updated hash value of the blacklist updated card number is recorded. Specifically, for example, when the blacklist is increased, the newly added blacklist card number can be known. The Bloom filter uses several hash functions to determine the corresponding positions of the blacklist card number on several hex arrays, and sets the bits at these positions to 1. In this way, the updated content and updated page number position of the newly added blacklist on the hex array can be known, and its hash value is recorded at the same time. Since the hex array is stored by page, it only needs to be updated by page when updating.

[0076] Then, an updated whitelist list and an updated whitelist index are generated according to the updated page number position and the updated hash value. Specifically, changes in the blacklist will increase or decrease the whitelist with hash value conflicts, and the whitelist list needs to be updated. When the whitelist list is updated, it is updated together with the whitelist index. For the whitelist index, the blacklist update causes the hex array page to be updated, and the whitelist index corresponding to the updated hex array page is updated. The new whitelist list and the updated whitelist index are recorded.

[0077] Next, the update configuration information of the initial configuration information is cached in the application background end, and the update configuration information includes update content, update page position, update whitelist index and update whitelist. Specifically, the update configuration information is cached first and waits for the solidification instruction before updating.

[0078] In actual operation, this application solution only requires one full download to generate the initial configuration information. Subsequent blacklist modifications only need to be made according to the updated content, and no full download is required, thereby improving the efficiency of blacklist synchronization.

[0079] In one embodiment, the application backend includes the blacklist version number corresponding to the full version blacklist library. The step of updating the full version blacklist library according to the update configuration information can be specifically performed as follows:

[0080] First, when a solidification instruction is received from the application backend, the date and time information is recorded and the target blacklist version number is generated based on the date and time information. Specifically, a timer is configured to trigger the blacklist version solidification process at a regular interval. The application backend issues a solidification instruction, generates a target blacklist version number based on the current date and time, and caches it.

[0081] Then, the full version blacklist library and the blacklist version number are updated according to the target blacklist version number and the update configuration information. Specifically, the target blacklist version number and the update configuration information are read and written into the full version blacklist library for updating.

[0082] Next, after the update is completed, the update configuration information is cleared and the cache information is cleared to prevent confusion between the update configuration information and the target blacklist version number when the blacklist is updated next time.

[0083] In one embodiment, the step of reading the blacklist configuration on the device side may be specifically performed as follows:

[0084] Determine whether the blacklist version number is updated. Specifically, the device obtains the blacklist version number through the "heartbeat protocol" and determines whether the blacklist on the application background is updated based on whether the blacklist version number is updated.

[0085] If the blacklist version number is updated, the blacklist configuration on the device side is read. Specifically, if the blacklist version number is updated, the blacklist on the application background side is updated, then the blacklist configuration on the device side is retrieved to prepare for update synchronization; if the blacklist version number is not updated, the blacklist on the application background side is not updated, and the device side does not need to be updated.

[0086] By setting the blacklist version number, the device side can know whether the backend side is updated based on whether the blacklist version number is updated, so as to start the device side blacklist synchronization.

[0087] In one embodiment, the device blacklist configuration includes a Bloom filter, a whitelist index, and a whitelist list. After the device blacklist configuration is updated according to the update configuration information to obtain the synchronized device blacklist configuration, the following steps may be further performed:

[0088] The blacklist matching process is as follows: Figure 2 As shown, when a card number query instruction is received from the device, the card number query instruction includes the card number to be queried, the hash value of the card number is calculated, and whether the hash value is in the Bloom filter is determined. Specifically, when the device is actually used, a card number blacklist match is required. The device will receive the card number query instruction, first calculate the hash value of the card number, and determine whether the hash value is in the Bloom filter.

[0089] If the hash value is not in the Bloom filter, the card number must be in the whitelist and the card number can be used normally. If the hash value is in the Bloom filter, the unusable card number can be identified based on the hash value, whitelist index and whitelist list. Specifically, the hash value is in the Bloom filter, and the hash value conflict cannot be ruled out. Therefore, it is also necessary to judge the usable status of the card number based on the hash value, whitelist index and whitelist list to identify the unusable card number.

[0090] In one embodiment, the step of identifying the unusable card number based on the hash value, the whitelist index and the whitelist can be specifically performed as follows:

[0091] Check whether there is a conflict in the whitelist index. Specifically, the Bloom filter calculates the card number corresponding to several hex array positions through several hash functions. Since the hex array is stored by page and the whitelist index corresponds to a page of each hex array, check whether there is a conflict in the whitelist index on the hex array page where the card number is located.

[0092] If there is no conflict, the card number is determined to be unusable. Specifically, there is no hash value conflict and the card number cannot be used if it is in the blacklist.

[0093] If there is a conflict, the whitelist index is queried according to the hash value, and the whitelist is queried according to the whitelist index. The whitelist includes the whitelist card number. If the whitelist card number and the card number are inconsistent, the card number is determined to be unusable. Specifically, if there is a conflict in the whitelist index on the hex array page where the queried card number is located, the starting address and offset of the whitelist index are retrieved, and the card number corresponding to the whitelist list is found according to the starting address and offset. If the card number in the whitelist list is inconsistent with the card number to be queried, the card number cannot be used in the blacklist; if the card number in the whitelist list is consistent with the card number to be queried, the card number can be used normally in the whitelist.

[0094] The blacklist is matched through the Bloom filter, the whitelist index and the whitelist. After filtering by the Bloom filter, the blacklist is matched from the reverse side starting from the whitelist with a smaller number, so that the blacklist matching efficiency is improved.

[0095] Based on the above method, the present application embodiment also discloses a method system for synchronizing the offline blacklist. Figure 3 The system includes the following modules:

[0096] The Bloom filter generation module 301 is used to read the full version blacklist library of the application backend and generate a Bloom filter according to the full version blacklist library;

[0097] An initial configuration information generating module 302 is used to generate initial configuration information of a full version blacklist library using a Bloom filter;

[0098] The update configuration information generation module 303 is used to generate update configuration information of the initial configuration information according to the blacklist update information when receiving the blacklist update information from the application backend;

[0099] The application backend update module 304 is used to update the full version blacklist library according to the update configuration information;

[0100] The device-side updating module 305 is used to read the blacklist configuration of the device-side when receiving an update request from the device-side, and update the device blacklist configuration according to the update configuration information to obtain the synchronized device blacklist configuration.

[0101] In one embodiment, the initial configuration information generation module 302 is specifically used to add the initial blacklist to the Bloom filter. The Bloom filter is stored by page in the form of a hex array, and the page number position and hash value of the initial blacklist are recorded; a whitelist index is generated according to the page number position, and the initial whitelist is searched according to the hash value to generate a whitelist list.

[0102] In one embodiment, the update configuration information generation module 303 is specifically used to use a Bloom filter to generate update content and update page number positions in a hex array according to the updated blacklist card number, and record the updated hash value of the blacklist updated card number; generate an updated whitelist list and an updated whitelist index according to the updated page number position and the updated hash value; cache the update configuration information of the initial configuration information in the application background end, and the update configuration information includes the update content, the updated page number position, the updated whitelist index and the updated whitelist.

[0103] In one embodiment, the application backend update module 304 is specifically used to record the date and time information and generate the target blacklist version number according to the date and time information when receiving the solidification instruction from the application backend; update the full version blacklist library and the blacklist version number according to the target blacklist version number and the update configuration information; and clear the update configuration information after the update is completed.

[0104] In one embodiment, the device-side update module 305 is specifically used to determine whether the blacklist version number is updated; if the blacklist version number is updated, read the blacklist configuration of the device-side.

[0105] The embodiment of the present application also discloses a computer device.

[0106] Specifically, the computer device includes a memory and a processor, and the memory stores a computer program that can be loaded by the processor and execute the above-mentioned offline blacklist synchronization method.

[0107] The embodiment of the present application also discloses a computer-readable storage medium.

[0108] Specifically, the computer-readable storage medium stores a computer program that can be loaded by a processor and execute the offline blacklist synchronization method as described above. The computer-readable storage medium includes, for example, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Claims

1. An offline blacklist synchronization method, characterized in that: The method is based on a blacklist management system including an application backend and a device end, and the method includes: Read the full version blacklist library of the application backend, and generate a Bloom filter according to the full version blacklist library; Generating initial configuration information of the full version blacklist library using the Bloom filter; When receiving the blacklist update information from the application backend, generating update configuration information of the initial configuration information according to the blacklist update information; Update the full version blacklist library according to the update configuration information; When an update request from the device is received, the blacklist configuration of the device is read, and the device blacklist configuration is updated according to the update configuration information to obtain a synchronized device blacklist configuration.

2. The method according to claim 1, characterized in that: The full version blacklist library includes an initial blacklist and an initial whitelist, and the initial configuration information of generating the full version blacklist library by using the Bloom filter includes: Adding the initial blacklist to the Bloom filter, the Bloom filter is stored in the form of a hex array by page, and recording the page number position and hash value of the initial blacklist; A whitelist index is generated according to the page number position, and the initial whitelist is searched according to the hash value to generate a whitelist list.

3. The method according to claim 1, characterized in that: The blacklist update information includes an updated blacklist card number, and the update configuration information for generating the initial configuration information according to the blacklist update information includes: Generate the updated content and updated page number position in the hex array according to the updated blacklist card number using the Bloom filter, and record the updated hash value of the blacklist updated card number; Generate an update whitelist list and an update whitelist index according to the update page number position and the update hash value; The update configuration information of the initial configuration information is cached in the application backend, wherein the update configuration information includes the update content, the update page position, the update whitelist index and the update whitelist list.

4. The method according to claim 1, characterized in that: The application backend includes a blacklist version number corresponding to the full version blacklist library, and updating the full version blacklist library according to the update configuration information includes: When receiving the curing instruction from the application backend, recording the date and time information and generating the target blacklist version number according to the date and time information; Update the full version blacklist library and the blacklist version number according to the target blacklist version number and the update configuration information; After the update is completed, the update configuration information is cleared.

5. The method according to claim 1, characterized in that: The reading of the blacklist configuration of the device includes: Determine whether the blacklist version number is updated; If the blacklist version number is updated, the blacklist configuration of the device is read.

6. The method according to claim 1, characterized in that: The synchronization device blacklist configuration includes a Bloom filter, a whitelist index and a whitelist list. After the synchronization device blacklist configuration is updated according to the update configuration information to obtain the synchronization device blacklist configuration, the following further includes: When receiving a card number query instruction from the device, the card number query instruction includes the card number to be queried, calculating a hash value of the card number, and determining whether the hash value is in a Bloom filter; If the hash value is in the Bloom filter, the unusable card number is identified according to the hash value, the whitelist index and the whitelist list.

7. The method according to claim 6, characterized in that: The identifying of the unusable card number according to the hash value, the whitelist index and the whitelist list comprises: Check whether there is a conflict in the whitelist index; If there is no conflict, it is determined that the card number cannot be used; If there is a conflict, the whitelist index is queried according to the hash value, and the whitelist is queried according to the whitelist index, the whitelist includes the whitelist card number, and if the whitelist card number is inconsistent with the card number, it is determined that the card number cannot be used.

8. An offline blacklist management system, characterized in that: The system comprises: A Bloom filter generation module (301), used for reading the full version blacklist library of the application backend, and generating a Bloom filter according to the full version blacklist library; An initial configuration information generating module (302), configured to generate initial configuration information of the full version blacklist library using the Bloom filter; An update configuration information generation module (303), configured to generate update configuration information of the initial configuration information according to the blacklist update information when receiving the blacklist update information from the application backend; An application backend update module (304) is used to update the full version blacklist library according to the update configuration information; The device-side update module (305) is used to read the blacklist configuration of the device-side when receiving an update request from the device-side, and update the device blacklist configuration according to the update configuration information to obtain a synchronized device blacklist configuration.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program which can be loaded by the processor and executes the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored which can be loaded by a processor and execute the method according to any one of claims 1 to 7.

Images