Solution for ensuring efficient and accurate issuing of clues of complex data structure

Abstract

The invention belongs to the technical field of database and big data processing, and discloses a solution for ensuring efficient and accurate issuing of complex data structure clues. The solution method comprises the following specific steps: S1, initializing page data; S2, switching a connection condition and obtaining a dealer list; S3, carrying out cache and database interaction; S4, updating a connection condition array; according to the method, an innovative clue follow-up issuing scheme is provided, the Redis high-performance cache technology is ingeniously integrated into the SCRM system, the inquired dealer data is pre-stored into the Redis, the high-speed read-write capability of the Redis is utilized, the speed of inquiring the dealer list is remarkably increased, the response performance of an issuing interface is further improved, the recursive algorithm is applied, and the issuing efficiency is improved. And the Cartesian product of a plurality of arrays is accurately calculated.

Description

Technical Field

[0001] The present invention belongs to the technical field of database and big data processing, and specifically provides a solution to ensure efficient and accurate delivery of clues of complex data structures. Background Art

[0002] In the SCRM system, sending leads is a key marketing activity. Usually, it is relatively simple to assign unfollowed leads to dealers in specific cities and car series. However, when it is necessary to send leads in batches to many dealers in multiple cities and car series, the problem becomes complicated. At this time, it is necessary to ensure the comprehensiveness and accuracy of the sending, and to avoid page freezes or crashes caused by the huge amount of data. This places extremely high demands on the system performance and user experience. At the same time, the current technical solution has obvious deficiencies in processing the sending of lead data. When the amount of data is small, the user has no obvious perception; however, in the face of complex connection situations, multiple car series and multiple city sending requirements, the browser needs to cache a large amount of data, resulting in page freezes and a greatly reduced user experience. As the amount of data to be sent increases, although the page freezes can be alleviated to a certain extent, the server needs to query the dealer list of each data one by one, which slows down the interface response speed and frequently timeouts. These problems not only affect the user experience, but also limit the processing capacity and efficiency of the system, and urgently need to be optimized and improved. Summary of the invention

[0003] The purpose of the present invention is to provide a solution to ensure that clues of complex data structures are efficiently and accurately issued, so as to solve the problems raised in the above-mentioned background technology.

[0004] In order to achieve the above-mentioned purpose, the present invention provides the following technical solution: a solution to ensure efficient and accurate delivery of clues of complex data structures, the specific steps of which are as follows:

[0005] S1: Initialize page data: Initialize data for clue delivery page: default connection, city, car ID array;

[0006] S2: Switch connection status and obtain dealer list: Switch connection status: request the interface to obtain and display the dealer list of the corresponding city and car series;

[0007] S3: Interaction between cache and database: To query the dealer list: first check the Redis cache, if there is no dealer list, check the database and cache the result;

[0008] S4: Update the diallist connection status array: update the diallist connection status array in real time according to user operation or system update;

[0009] S5: Add a new city and series: Add a new city and series: update the ID list and synchronize the data to cityList and seriesList;

[0010] S6: Calculate the Cartesian product and obtain the dealer list: Calculate the Cartesian product, concatenate the RedisKey to obtain the dealer list, and check the database if it is invalid;

[0011] S7: Call the delivery interface to follow up and deliver the clues: Call the delivery interface to ensure that the Cartesian product combination clues are delivered accurately.

[0012] Preferably, the specific steps of initializing page data in S1 are as follows:

[0013] Step 1: Initialize the connection status array

[0014] Enter the clue distribution page:

[0015] The system loads the dialList array by default, which contains all the dial conditions.

[0016] Step 2: Initialize the city ID array

[0017] Load the default city ID:

[0018] The system loads the city ID array cityList by default, which contains one or more default selected city IDs;

[0019] Step 3: Initialize the car ID array

[0020] Load the default car ID:

[0021] The system loads the series ID array seriesList by default, which contains one or more series IDs selected by default.

[0022] Preferably, switching the connection status and obtaining the dealer list in S2 refers to the user switching the drop-down option of the connection status in the clue sending page. When "connected but not replied" is selected, the system will automatically capture this action. Then, the system will obtain the city ID selected by the current user. Subsequently, the system will send a request to the background interface in a specific parameter format based on these selected conditions. The request is intended to obtain a list of dealers that match the selected connection status, city and car series. After the interface returns the data, the system will display the dealer information at the corresponding position of the page for the user to view and select.

[0023] Preferably, the specific steps of the interaction between the cache and the database in S3 are as follows:

[0024] Step 1: Check the Redis cache

[0025] The system will use "city id_car series id_connection status enumeration value" as the key to find out whether there is corresponding data in the Redis cache;

[0026] Step 2: Process Redis cache results

[0027] If the corresponding data exists in the Redis cache, the system will directly obtain the data and return it to the requester as a dealer list, so that the user can quickly see the required dealer information;

[0028] Step 3: Query the database and store it in Redis cache

[0029] If the corresponding data is not found in the Redis cache, the system will turn to the database for query; by executing the corresponding database query statement, the system will obtain a set of dealer lists that match the request conditions. Subsequently, the data will be stored in the Redis cache so that subsequent requests can obtain the data faster. At the same time, the system will also return the queried dealer list to the requester.

[0030] Preferably, updating the dialing status array in S4 means that the dialList array on the page will be updated in real time according to the user's operation or the automatic update of the system. The array is used to record and manage different dialing statuses.

[0031] Preferably, the specific steps of adding a new city and car series in S5 are as follows:

[0032] Step 1: Add an ID and update the list

[0033] When a new city or series is added to the system, S2 and S3 are executed in a loop, and the new city ID or series ID needs to be added to the corresponding cityList or seriesList;

[0034] Step 2: Perform data synchronization and cache update

[0035] After updating cityList or seriesList, the system needs to perform data synchronization operations to ensure that the relevant data in the database and Redis cache system are also updated, synchronize the new city ID or series ID to the database, and update the relevant data in the Redis cache. When the user performs subsequent operations, the system can provide the latest and most accurate data support.

[0036] Preferably, the specific steps of calculating the Cartesian product and obtaining the dealer list in S6 are as follows:

[0037] Step 1: Calculate the Cartesian product

[0038] Before submitting the follow-up, first calculate the Cartesian product based on the three lists of dialList, cityList and seriesList to generate all the combination arrays. The combination array will contain all the permutations and combinations of each city ID, car series ID and connection status enumeration value;

[0039] Step 2: Concatenate RedisKey and get data

[0040] Next, concatenate each combination in the Cartesian product array into a key in Redis in the format of "city id_car series id_connection status enumeration value"; then, use these keys to query the corresponding dealer list from Redis;

[0041] Step 3: Process invalid data and query the database

[0042] When getting data from Redis, you may encounter invalid or non-existent data. In this case, you need to start a database query to ensure data integrity. For keys that do not exist in Redis, use the corresponding combination as the query condition, query the corresponding dealer list from the database, and update it to Redis. This ensures data integrity and accuracy even when Redis data is invalid.

[0043] Preferably, calling the sending interface in S7 to follow up and send leads means that before submitting the follow-up and sending, the system will prepare the data for the follow-up and sending of leads based on the dealer list obtained from Redis or the database, and the Cartesian product combination previously calculated by dialList, cityList and seriesList, and the data includes the dealer list corresponding to each city ID, car series ID and connection status enumeration value. Subsequently, the system will call the sending interface to send these leads to the corresponding dealers accurately according to the calculated Cartesian product combination.

[0044] The beneficial effects of the present invention are as follows:

[0045] 1. The present invention proposes an innovative clue follow-up and delivery solution, cleverly integrates Redis high-performance caching technology into the SCRM system, and pre-stores the queried dealer data in Redis and utilizes Redis's high-speed reading and writing capabilities to significantly improve the speed of querying the dealer list, thereby improving the response performance of the delivery interface. The recursive algorithm is used to accurately calculate the Cartesian product of multiple arrays, which plays a key role in Redis querying the dealer list, effectively avoiding the page caching a large amount of data, thereby greatly improving the page performance. When querying Redis data, if the data is invalid, the system will immediately turn to the database query to ensure the integrity and accuracy of the data, achieving perfect coordination between the front and back ends, not only ensuring the integrity of the delivered data, but also significantly enhancing the fluency of page interaction, bringing users a more outstanding user experience.

[0046] 2. The present invention uses a recursive algorithm innovatively to accurately calculate the Cartesian product set of the connection status, city, and car series corresponding to the clues issued, and cleverly uses Redis cache technology to store dealer information in preparation for the need to issue clues. This solution can effectively relieve browser pressure when facing large-scale data issuance, ensuring smooth user operation. At the same time, through the cache mechanism, the interface response time has been greatly optimized, and the tp999 indicator has been successfully controlled within 200ms. More importantly, while efficiently issuing clues, it also ensures the integrity and accuracy of the data, bringing users a more stable and reliable user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 It is a schematic diagram of the overall use process of the present invention;

[0048] Figure 2 This is a schematic diagram of the page for following up on clues of the present invention;

[0049] Figure 3 A schematic diagram of the process of issuing clues of the present invention;

[0050] Figure 4 A schematic diagram of the Cartesian product operation calculated by the recursive algorithm of the present invention;

[0051] Figure 5 The figure is a flow chart of the algorithm for recursively calculating Cartesian product arrays according to the present invention. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0053] like Figures 1 to 5 As shown, the embodiment of the present invention provides a solution to ensure efficient and accurate delivery of clues of complex data structures. The specific steps of the solution are as follows:

[0054] S1: Initialize page data: Initialize data for clue delivery page: default connection, city, car ID array;

[0055] S2: Switch connection status and obtain dealer list: Switch connection status: request the interface to obtain and display the dealer list of the corresponding city and car series;

[0056] S3: Interaction between cache and database: To query the dealer list: first check the Redis cache, if there is no dealer list, check the database and cache the result;

[0057] S4: Update the diallist connection status array: update the diallist connection status array in real time according to user operation or system update;

[0058] S5: Add a new city and series: Add a new city and series: update the ID list and synchronize the data to cityList and seriesList;

[0059] S6: Calculate the Cartesian product and obtain the dealer list: Calculate the Cartesian product, concatenate the RedisKey to obtain the dealer list, and check the database if it is invalid;

[0060] S7: Call the delivery interface to follow up and deliver the clues: Call the delivery interface to ensure that the Cartesian product combination clues are delivered accurately.

[0061] The specific steps of initializing page data in S1 are as follows:

[0062] Step 1: Initialize the connection status array

[0063] Enter the clue distribution page:

[0064] The system loads the dialList array by default, which contains all dial conditions, for example, ['Not connected', 'Not connected regular delivery', 'Unable to connect']; these dial conditions will be used for subsequent delivery operations and screening conditions.

[0065] Step 2: Initialize the city ID array

[0066] Load the default city ID:

[0067] The system loads the city ID array cityList by default, which contains one or more default selected city IDs, for example: [110100].

[0068] These city IDs will be used to determine the geographic scope of where the leads will be sent.

[0069] Step 3: Initialize the car ID array

[0070] Load the default car ID:

[0071] The system loads the series ID array seriesList by default, which contains one or more series IDs selected by default. For example:

[98723] .

[0072] These vehicle IDs will be used to determine the specific model or range of vehicles to which the clues are issued.

[0073] Initializing the page data can automatically load the default arrays of connection conditions, cities and car models, providing basic data for the lead distribution page. This process ensures that users can immediately see and operate these preset information when entering the page, improving work efficiency and user experience. At the same time, it also simplifies the data input process, reduces the workload of users' manual selection, and makes the page more intuitive and easy to use.

[0074] Among them, switching the connection status and obtaining the dealer list in S2 refers to the user switching the drop-down option of the connection status in the clue delivery page. When "Connected but not replied" is selected, the system will automatically capture this action. Then, the system will obtain the city ID (taking 110100 as an example) and car series ID (taking 98723 as an example) selected by the current user. Subsequently, the system will send a request to the background interface based on these selected conditions and a specific parameter format (i.e. {pickUp:'Connected but not replied', cityId:110100, seriesId:98723}). The request is intended to obtain a list of dealers that match the selected connection status, city and car series. After the interface returns the data, the system will display the dealer information in the corresponding position of the page for users to view and select.

[0075] Switching the connection status and obtaining the dealer list can respond to user operations in real time. According to the connection status, city ID and car ID selected by the user, it automatically sends a request to the background interface to quickly obtain the matching dealer information and display it on the page. This function improves the user experience and enables users to easily obtain the required information. At the same time, the automated processing flow also improves the efficiency and accuracy of the system.

[0076] The specific steps of the interaction between the cache and the database in S3 are as follows:

[0077] Step 1: Check the Redis cache

[0078] The system will use "city id_car series id_connection status enumeration value" as the key to find out whether the corresponding data exists in the Redis cache. This step is to quickly obtain data and reduce the access pressure of the database.

[0079] Step 2: Process Redis cache results

[0080] If the corresponding data exists in the Redis cache, the system will directly obtain the data and return it to the requester as a dealer list, so that the user can quickly see the required dealer information;

[0081] Step 3: Query the database and store it in Redis cache

[0082] If the corresponding data is not found in the Redis cache, the system will turn to the database for query; by executing the corresponding database query statement, the system will obtain a set of dealer lists that match the request conditions. Subsequently, the data will be stored in the Redis cache so that subsequent requests can obtain the data faster. At the same time, the system will also return the queried dealer list to the requester.

[0083] The cache and database interaction process can efficiently use Redis cache to quickly respond to requests and reduce the burden on the database; when the cache hits, users can quickly obtain the required dealer information and improve the experience; if the cache misses, the system will query and update the cache from the database to ensure data accuracy and speed up future requests. This mechanism balances speed and accuracy, optimizes resource utilization, and improves the overall performance of the system.

[0084] Among them, updating the connection status array in S4 means that according to the user's operation or the automatic update of the system, the dialList array on the page will be updated in real time. The array is used to record and manage different connection situations; for example, when the user selects or the system adds the option of "connected but not replied", the dialList array will be updated to a new array including options such as "connected but not replied", "unconnected regular delivery" and "unable to connect". Such an update mechanism ensures the accuracy and real-time nature of the page data and provides users with a better operation experience.

[0085] It can respond to user operations or system updates in real time to ensure that the dialList array accurately records and manages the connection status. When the user selects or the system adds a new connection status option, the array will be updated immediately to ensure the accuracy and real-time nature of the page data. This mechanism optimizes the user experience, allowing users to obtain the latest connection status at any time, improves the flexibility and availability of the system, and provides strong support for business decisions.

[0086] The specific steps for adding a new city and car series in S5 are as follows:

[0087] Step 1: Add an ID and update the list

[0088] When a new city or car series is added to the system, S2 and S3 are executed in a loop, and the new city ID or car series ID needs to be added to the corresponding cityList or seriesList. For example, if a new city ID is 110390, then cityList will be updated from [110100] to [110100,110390]. Similarly, if a new car series ID is 97348, then seriesList will be updated from

[98723] to [98723,97348].

[0089] Step 2: Perform data synchronization and cache update

[0090] After updating cityList or seriesList, the system needs to perform data synchronization operations to ensure that relevant data in systems such as the database and Redis cache are also updated, synchronize the new city ID or series ID to the database, and update the relevant data in the Redis cache. When the user performs subsequent operations, the system can provide the latest and most accurate data support.

[0091] The above internal system can ensure that the system data is updated in real time. When a new city or car series is added, the ID is added to the corresponding list in a loop, and the database and Redis cache are updated synchronously, thereby ensuring the integrity and accuracy of the system data. This process improves data processing efficiency, allowing users to obtain the latest and most accurate data support when performing subsequent operations, optimizing user experience and enhancing system reliability and practicality.

[0092] The specific steps of calculating the Cartesian product and obtaining the dealer list in S6 are as follows:

[0093] Step 1: Calculate the Cartesian product

[0094] Before submitting the follow-up, first calculate the Cartesian product based on the three lists of dialList, cityList and seriesList to generate all the combination arrays. The combination array will contain all the permutations and combinations of each city ID, car series ID and connection status enumeration value; the permutations and combinations are as follows:

[0095] [["Not connected",98723,110100],["Not connected",98723,110390],["Not connected",97348,110100],["Not connected",97348,110390],["Not connected",96547,110100],["Not connected",96547,110390],["Not connected, regular delivery",98723,110100],["Not connected, regular delivery",98723,110390],["Not connected, regular delivery",97348,110100],[" Not connected to the regular delivery",97348,110390],["Not connected to the regular delivery",96547,110100],["Not connected to the regular delivery",96547,110390],["Unable to connect",98723,110100],["Unable to connect",98723,110390],["Unable to connect",97348,110100],["Unable to connect",97348,110390],["Unable to connect",96547,110100],["Unable to connect",96547,110390]]

[0096] Step 2: Concatenate RedisKey and get data

[0097] Next, concatenate each combination in the Cartesian product array into a key in Redis in the format of "city id_car series id_connection status enumeration value"; then, use these keys to query the corresponding dealer list from Redis; this step will take advantage of Redis's high-speed access feature to quickly obtain large amounts of data.

[0098] Step 3: Process invalid data and query the database

[0099] When getting data from Redis, you may encounter invalid or non-existent data. In this case, you need to start a database query as a data integrity guarantee. For keys that do not exist in Redis, use the corresponding combination as the query condition, query the corresponding dealer list from the database, and update it to Redis (if necessary). In this way, even if the Redis data is invalid, the integrity and accuracy of the data can be ensured.

[0100] The benefits of calculating the Cartesian product and obtaining the dealer list are: it can fully integrate the dialList, cityList and seriesList information to generate a detailed combination array; by splicing RedisKey, a large amount of data can be quickly accessed and obtained to improve efficiency; at the same time, for invalid data in Redis, the system can automatically query the database and update it to ensure the integrity and accuracy of the data. This process optimizes data processing, improves work efficiency, and provides reliable data support for business decisions.

[0101] Among them, calling the issuing interface in S7 to follow up and issue leads means that before submitting the follow-up and issuance, the system will prepare the data for the follow-up and issuance of leads based on the dealer list obtained from Redis or the database and the Cartesian product combination calculated by dialList, cityList and seriesList before. The data includes the dealer list corresponding to each city ID, car series ID and connection status enumeration value. Subsequently, the system will call the issuing interface to accurately issue these leads to the corresponding dealers according to the calculated Cartesian product combination. In this process, the system will ensure that all relevant leads are correctly processed and accurately issued according to the predetermined combination to support subsequent follow-up work.

[0102] The benefit of calling the dispatching interface to follow up and dispatch leads is that the system can efficiently integrate dealer data and Cartesian product combination information in Redis or database, and accurately match the dealer list corresponding to each city ID, car series ID and connection status. Through this process, it is ensured that all relevant leads are accurately dispatched, which not only improves work efficiency, but also enhances the accuracy and completeness of data processing, laying a solid foundation for subsequent follow-up work.

[0103] SCRM system: Social Customer Relationship Management system. It is a new customer relationship management method that integrates and analyzes user data from social media and other channels to provide more personalized and efficient customer service and user promotion.

[0104] Cartesian product: is an operation performed on two sets in set theory. For example, the Cartesian product of three sets a, b, and c is a set consisting of three ordered triplets (a, b, c).

[0105] Redis: is a memory-based data structure storage system

[0106] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0107] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A solution to ensure efficient and accurate delivery of clues of complex data structures, characterized by: The specific steps of this solution are as follows: S1: Initialize page data: Initialize data for clue delivery page: default connection, city, car ID array; S2: Switch connection status and obtain dealer list: Switch connection status: request the interface to obtain and display the dealer list of the corresponding city and car series; S3: Interaction between cache and database: To query the dealer list: first check the Redis cache, if there is no dealer list, check the database and cache the result; S4: Update the diallist connection status array: update the diallist connection status array in real time according to user operation or system update; S5: Add a new city and series: Add a new city and series: update the ID list and synchronize the data to cityList and seriesList; S6: Calculate the Cartesian product and obtain the dealer list: Calculate the Cartesian product, concatenate the Redis Keys to obtain the dealer list, and check the database if it is invalid; S7: Call the delivery interface to follow up and deliver the clues: Call the delivery interface to ensure that the Cartesian product combination clues are delivered accurately.

2. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: The specific steps of initializing page data in S1 are as follows: Step 1: Initialize the connection status array Enter the clue delivery page: the system loads the dial list array by default, which contains all the dial lists. Step 2: Initialize the city ID array Load default city ID: The system loads the city ID array cityList by default, which contains one or more default selected city IDs; Step 3: Initialize the car ID array Load default car series ID: The system loads the car series ID array seriesList by default, which contains one or more default selected car series IDs.

3. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1 is characterized by: Switching the connection status and obtaining the dealer list in S2 refers to the user switching the drop-down option of the connection status in the clue sending page. When "connected but not replied" is selected, the system will automatically capture this action. Then, the system will obtain the city ID selected by the current user. Subsequently, the system will send a request to the background interface in a specific parameter format based on these selected conditions. The request is intended to obtain a list of dealers that match the selected connection status, city and car series. After the interface returns the data, the system will display the dealer information at the corresponding position of the page for the user to view and select.

4. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: The specific steps of the interaction between the cache and the database in S3 are as follows: Step 1: Check the Redis cache The system will use "city id_car series id_connection status enumeration value" as the key to check whether the corresponding data exists in the Redis cache; Step 2: Process Redis cache results If the corresponding data exists in the Redis cache, the system will directly obtain the data and return it to the requester as a dealer list, so that the user can quickly see the required dealer information; Step 3: Query the database and store it in Redis cache If the corresponding data is not found in the Redis cache, the system will turn to the database for query; by executing the corresponding database query statement, the system will obtain a set of dealer lists that match the request conditions. Subsequently, the data will be stored in the Redis cache so that subsequent requests can obtain the data faster. At the same time, the system will also return the queried dealer list to the requester.

5. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: Updating the connection status array in S4 means that the dialList array on the page will be updated in real time according to the user's operation or the automatic update of the system. This array is used to record and manage different connection situations.

6. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: The specific steps for adding a new city and car series in S5 are as follows: Step 1: Add an ID and update the list When a new city or series is added to the system, S2 and S3 are executed in a loop, and the new city ID or series ID needs to be added to the corresponding cityList or seriesList; Step 2: Perform data synchronization and cache update After updating cityList or seriesList, the system needs to perform data synchronization operations to ensure that the relevant data in the database and Redis cache system are also updated, synchronize the new city ID or series ID to the database, and update the relevant data in the Redis cache. When the user performs subsequent operations, the system can provide the latest and most accurate data support.

7. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: The specific steps of calculating the Cartesian product and obtaining the dealer list in S6 are as follows: Step 1: Calculate the Cartesian product Before submitting the follow-up, first calculate the Cartesian product based on the three lists of dialList, cityList and seriesList to generate all the combination arrays. The combination array will contain all the permutations and combinations of each city ID, car series ID and connection status enumeration value; Step 2: Concatenate Redis Keys and get data Next, concatenate each combination in the Cartesian product array into a key in Redis in the format of "city id_car series id_connection status enumeration value"; then, use these keys to query the corresponding dealer list from Redis; Step 3: Process invalid data and query the database When getting data from Redis, you may encounter invalid or non-existent data. In this case, you need to start a database query to ensure data integrity. For keys that do not exist in Redis, use the corresponding combination as the query condition, query the corresponding dealer list from the database, and update it to Redis. This ensures data integrity and accuracy even when Redis data is invalid.

8. The solution for ensuring efficient and accurate delivery of complex data structure clues according to claim 1, characterized in that: Calling the sending interface to follow up and send leads in S7 means that before submitting the follow-up and sending, the system will prepare the data for the follow-up and sending of leads based on the dealer list obtained from Redis or the database and the Cartesian product combination previously calculated by dialList, cityList and seriesList. The data includes the dealer list corresponding to each city ID, car series ID and connection status enumeration value. Subsequently, the system will call the sending interface to send these leads to the corresponding dealers accurately according to the calculated Cartesian product combination.

Images