A method, system and storage medium for sending overdue messages with a cycle check

Abstract

The application discloses a kind of methods for circulating verification to send overdue message, system and storage medium, belong to information technology field, solve the problems such as low efficiency, low accuracy or / and easy to affect system performance in data verification of prior art.The application includes setting the message strategy configuration table of collection system in database;In database, configure the original data temporary table for storing data warehouse push content;Business table 1 is configured in database;Business table 2 is configured in database;Circulatingly traverses the data meeting the sending strategy in message strategy configuration table in business table 1, after comparing and verifying the result with original data temporary table, obtain the final data meeting the sending strategy, and carry out message sending, simultaneously, the data meeting the sending strategy is written into business table 2.The application is used to circulating verification to send overdue message.

Description

Technical Field

[0001] A method, system, and storage medium for cyclically verifying the sending of overdue SMS messages are disclosed, belonging to the field of information technology. Background Technology

[0002] Traditional debt collection systems receive all raw data pushed from the upstream data warehouse during evening batch processing. This data is then linked and integrated using the loan receipt number, and SMS messages are sent to relevant loan receipts that match the SMS sending strategy. However, since all data in the debt collection system originates from upstream, there is an inherent weakness in data verification. Existing technologies have the following technical problems in data verification:

[0003] 1. Sensitive operations such as sending text messages lack a verification mechanism, resulting in low accuracy and easy user dissatisfaction. Because text messages are sent automatically in batches and only contain text content, the lack of a verification mechanism cannot ensure the accuracy of the sent data. If customers who have not yet received the overdue text messages receive overdue text messages, it will lead to a large number of complaints.

[0004] 2. If the verification is performed by querying the bank's core system and accounting system through the interface, the efficiency is low and the large amount of data will have a performance impact on the bank's core system and accounting system.

[0005] 3. Manually sending SMS messages is labor-intensive, inefficient, and also suffers from low accuracy. Summary of the Invention

[0006] To address the problems mentioned above, the present invention aims to provide a method, system, and storage medium for cyclically verifying the sending of overdue SMS messages, thereby solving the problems of low efficiency, low accuracy, and / or easy impact on system performance in data verification of existing technologies.

[0007] To achieve the above objectives, the present invention adopts the following technical solution:

[0008] A method for cyclically verifying the sending of overdue SMS messages includes the following steps:

[0009] Step 1: Set up the SMS policy configuration table for the collection system in the database. The SMS policy configuration table includes ID, availability, and sending policy. The sending policy is configured to send different SMS templates based on different product channels and overdue days.

[0010] Step 2: Configure a temporary table in the database to store raw data pushed content from the data warehouse. The temporary table includes overdue data that has not been integrated.

[0011] Configure Business Table 1 in the database. Business Table 1 is used to record the full data after the collection system runs and parses the original data temporary table and integrates it. Business Table 1 includes the ID field, batch number and overdue data generated by the collection system. The ID and batch number are used to distinguish the collection records after different stages of overdue for the same loan number.

[0012] The overdue data includes loan receipt information, loan overdue information, customer information, and third-party contact information. Loan receipt information includes the loan receipt number and transaction number. Loan overdue information includes the overdue date, overdue days, and overdue amount. Customer information includes the customer's name, customer ID card number, and customer contact information. Third-party contact information includes the name of the associated person and the contact information of the associated person. The ID field is used to store all operations of each loan receipt in the collection system.

[0013] Configure Business Table 2 in the database. Business Table 2 includes the IOU number, customer information, and SMS template.

[0014] Step 3: Loop through and query the data in Business Table 1 that matches the sending strategy in the SMS strategy configuration table. Compare and verify the results with the original data temporary table and Business Table 2 to obtain the final data that matches the sending strategy, and send the SMS. At the same time, write the data that matches the sending strategy into Business Table 2.

[0015] Furthermore, the specific steps of step 3 are as follows:

[0016] Step 3.1: Create two collections, List1 and List2. List1 and List2 respectively include the IOU number, the customer information corresponding to the IOU number, the SMS sending frequency corresponding to the IOU number, and the SMS template corresponding to the IOU number. The customer information includes the customer's name, mobile phone number, and ID card number.

[0017] Step 3.2: Traverse and query the data in Business Table 1 that match the sending strategy in SMS Strategy Configuration Table 1, and save them to Collection List1;

[0018] Step 3.3: Perform a loop check between the data in collection List1 and the original temporary data table. If the check results are consistent each time, save the consistent data to collection List2; otherwise, filter out the abnormal data.

[0019] Step 3.4: Loop through the IOU numbers in the List2 collection and check if they exist in the business table 2. If they exist, go to step 3.5; otherwise, send the SMS directly and write it into the business table 2, and record the SMS sending time.

[0020] Step 3.5: Perform loop verification between the data in set List2 and business table 2. If the sending interval of the data in set List2 conforms to the sending strategy after each verification, then send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval does not conform to the sending strategy. The sending interval is a given number of days or a range of days.

[0021] Furthermore, in step 3.3, the loan receipt information and overdue days in set List1 are compared with those in the original temporary data table by querying the loan receipt number or customer ID card.

[0022] Furthermore, the specific steps of step 3.5 are as follows:

[0023] Step 3.51: Identify the loan receipt information and determine whether the loan receipt is currently overdue. If it is overdue, proceed to step 3.42; otherwise, do not process it.

[0024] Step 3.52: Verify customer information, that is, check whether a single customer has multiple overdue payments. If so, match the sending strategy with the longest overdue IOU and proceed to step 3.53; otherwise, directly match the sending strategy and proceed to step 3.53.

[0025] Step 3.53: Verify the sending interval duration, that is, check whether the sending interval duration meets the sending strategy of the loan information. If it does, send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval duration does not meet the sending strategy.

[0026] A system for cyclically verifying the sending of overdue SMS messages includes:

[0027] A. Configuration Module: Set up the SMS policy configuration table for the collection system in the database. The SMS policy configuration table includes ID, availability, and sending policy. The sending policy is configured to send different SMS templates based on different product channels and overdue days.

[0028] B Configuration Module: Configures a temporary table in the database to store raw data pushed content from the data warehouse. The temporary table includes overdue data that has not been integrated or processed.

[0029] Configure Business Table 1 in the database. Business Table 1 is used to record the full data after the collection system runs and parses the original data temporary table and integrates it. Business Table 1 includes the ID field, batch number and overdue data generated by the collection system. The ID and batch number are used to distinguish the collection records after different stages of overdue for the same loan number.

[0030] The overdue data includes loan receipt information, loan overdue information, customer information, and third-party contact information. Loan receipt information includes the loan receipt number and transaction number. Loan overdue information includes the overdue date, overdue days, and overdue amount. Customer information includes the customer's name, customer ID card number, and customer contact information. Third-party contact information includes the name of the associated person and the contact information of the associated person. The ID field is used to store all operations of each loan receipt in the collection system.

[0031] Configure Business Table 2 in the database. Business Table 2 includes the IOU number, customer information, and SMS template.

[0032] Verification module: Iterates through the data in business table 1 that conforms to the sending strategy in the SMS strategy configuration table, compares the results with the original data temporary table and business table 2 to obtain the final data that conforms to the sending strategy, sends the SMS, and writes the data that conforms to the sending strategy into business table 2.

[0033] Furthermore, the specific implementation steps of the verification module are as follows:

[0034] Step 3.1: Create two collections, List1 and List2. List1 and List2 respectively include the IOU number, the customer information corresponding to the IOU number, the SMS sending frequency corresponding to the IOU number, and the SMS template corresponding to the IOU number. The customer information includes the customer's name, mobile phone number, and ID card number.

[0035] Step 3.2: Traverse and query the data in Business Table 1 that match the sending strategy in SMS Strategy Configuration Table 1, and save them to Collection List1;

[0036] Step 3.3: Perform a loop check between the data in collection List1 and the original temporary data table. If the check results are consistent each time, save the consistent data to collection List2; otherwise, filter out the abnormal data.

[0037] Step 3.4: Loop through the IOU numbers in the List2 collection and check if they exist in the business table 2. If they exist, go to step 3.5; otherwise, send the SMS directly and write it into the business table 2, and record the SMS sending time.

[0038] Step 3.5: Perform loop verification between the data in set List2 and business table 2. If the sending interval of the data in set List2 conforms to the sending strategy after each verification, then send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval does not conform to the sending strategy. The sending interval is a given number of days or a range of days.

[0039] Furthermore, in step 3.3, the loan receipt information and overdue days in set List1 are compared with those in the original temporary data table by querying the loan receipt number or customer ID card.

[0040] Furthermore, the specific steps of step 3.5 are as follows:

[0041] Step 3.51: Identify the loan receipt information and determine whether the loan receipt is currently overdue. If it is overdue, proceed to step 3.42; otherwise, do not process it.

[0042] Step 3.52: Verify customer information, that is, check whether a single customer has multiple overdue payments. If so, match the sending strategy with the longest overdue IOU and proceed to step 3.53; otherwise, directly match the sending strategy and proceed to step 3.53.

[0043] Step 3.53: Verify the sending interval duration, that is, check whether the sending interval duration meets the sending strategy of the loan information. If it does, send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval duration does not meet the sending strategy.

[0044] A storage medium for a method of cyclically verifying the sending of overdue SMS messages, and a server storing the method of cyclically verifying the sending of overdue SMS messages.

[0045] Compared with the prior art, the beneficial effects of this invention are as follows:

[0046] This invention is applied to the context of sending overdue SMS messages in internet bank collection systems. It utilizes raw data pushed from an upstream temporary data table to promptly identify data problems in the collection system during batch processing (such as data not being successfully updated according to upstream data, resulting in incorrect overdue status, inconsistent overdue days, etc.). Compared to calling the bank's core and accounting systems through interfaces for verification, this invention does not put any performance pressure on the bank's core and accounting systems, compensates for the deficiencies in the data verification function of the collection system, and improves the collection system's ability to identify errors such as erroneous SMS messages. By adding multiple loop verifications, and assuming the verification process ends normally, it can completely prevent any SMS message mis-sending problems caused by erroneous data. Detailed Implementation

[0047] The present invention will now be further described in conjunction with specific embodiments.

[0048] A method for cyclically verifying the sending of overdue SMS messages includes the following steps:

[0049] Step 1: Set up the SMS policy configuration table for the collection system in the database. The SMS policy configuration table includes ID, availability, and sending policy. The sending policy is configured to send different SMS templates based on different product channels and overdue days. ID is a unique identifier for the SMS sending policy, used to distinguish different sending policies. The availability field is an enumeration type, where 0 is unavailable and 1 is available. When iterating through the data in business table 1 that matches the sending policy in the SMS policy configuration table, if the policy is configured as 1, the sending policy will be matched and verified. If it is 0, the policy will not be matched and verified. The sending policy field is a JSON string. For example, for IOUs overdue for 1-3 days, send SMS template 1 once a day; for IOUs overdue for 4-30 days, send SMS template 2 once every three days; for IOUs overdue for 31 days or more, send SMS template 3 once a week. The above sending policies are divided into 3 and stored as {"overdueDay":[1,3],"interval":1","smsTemplate":"template1"}.

[0050] {“overdueDay”:[4,30],“interval”:3,“smsTemplate”:“template2};

[0051] {“overdueDay”:[31,0],“interval”:7,“smsTemplate”:“Template 2”}

[0052] Step 2: Configure a temporary table in the database to store raw data pushed content from the data warehouse. The temporary table includes overdue data that has not been integrated.

[0053] Configure Business Table 1 in the database. Business Table 1 is used to record the full data after the collection system runs and parses the original temporary data table (such as the method in CN202110717009.4 to implement the collection system's batch parsing). Business Table 1 includes the ID field, batch number and overdue data generated by the collection system. The ID and batch number are used to distinguish the collection records after different stages of overdue for the same loan number.

[0054] The overdue data includes loan receipt information, loan overdue information, customer information, and third-party contact information. Loan receipt information includes the loan receipt number and transaction number. Loan overdue information includes the overdue date, overdue days, and overdue amount. Customer information includes the customer's name, customer ID card number, and customer contact information. Third-party contact information includes the name of the associated person and the contact information of the associated person. The ID field is used to store all operations of each loan receipt in the collection system.

[0055] Configure Business Table 2 in the database. Business Table 2 includes the IOU number, customer information, and SMS template.

[0056] Step 3: Loop through and query the data in Business Table 1 that matches the sending strategy in the SMS strategy configuration table. Compare and verify the results with the original data temporary table and Business Table 2 to obtain the final data that matches the sending strategy, and send the SMS. At the same time, write the data that matches the sending strategy into Business Table 2.

[0057] The specific steps are as follows:

[0058] Step 3.1: Create two collections, List1 and List2. List1 and List2 respectively include the IOU number, the number of overdue days, the customer information corresponding to the IOU number, the SMS sending frequency for the corresponding IOU number, and the SMS template for the corresponding IOU number.

[0059] Step 3.2: Traverse and query the data in Business Table 1 that match the sending strategy in SMS Strategy Configuration Table 1, and save them to Collection List1;

[0060] Step 3.3: Perform a loop check between the data in collection List1 and the original temporary data table. If the check results are consistent each time, save the consistent data to collection List2; otherwise, filter out the abnormal data. Perform a loop check between the data in collection List1 and the original temporary data table by querying and comparing the loan receipt number and the customer's ID card. First, check if the status of the loan receipt number in the original temporary data table is overdue. If it is overdue, check if the overdue days are consistent. Finally, check if the customer's ID card is consistent. Otherwise, filter out the abnormal data.

[0061] Step 3.4: Loop through the IOU numbers in the List2 collection and check if they exist in the business table 2. If they exist, go to step 3.5; otherwise, send the SMS directly and write it into the business table 2, and record the SMS sending time.

[0062] Step 3.5: Perform loop verification between the data in set List2 and business table 2. If the sending interval of the data in set List2 conforms to the sending strategy after each verification, then send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval does not conform to the sending strategy. The sending interval is a given number of days or a range of days.

[0063] The specific steps are as follows:

[0064] Step 3.51: Identify the loan receipt information and determine whether the loan receipt is currently overdue. If it is overdue, proceed to step 3.52; otherwise, do not process it.

[0065] Step 3.52: Verify customer information, that is, check whether a single customer has multiple overdue payments. If so, match the sending strategy with the longest overdue payment and go to step 3.43; otherwise, directly match the sending strategy and go to step 3.43.

[0066] Step 3.53: Verify the sending interval duration, that is, check whether the sending interval duration meets the sending strategy of the loan information. If it does, send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval duration does not meet the sending strategy. Example

[0067] The SMS policy configuration table is used to match the sending policies created in the business table 1. Data that matches the sending policies is saved sequentially to List1. For example, for a certain channel under a certain product, if the overdue period is 1 to 3 days, one Template 1 SMS is sent every day; if the overdue period is 4 days or more, one Template 2 SMS is sent every 3 days. In this case, all IOU numbers overdue by 1 day or more for a certain product and channel, along with the corresponding customer information (including customer name, mobile phone number, and ID number), the overdue days for each IOU number, and the corresponding SMS template will be saved in List1. After looping and validating the IOU numbers in List1 against the original temporary data table, abnormal data is filtered out, and the results are saved in List2. At this point, the data in List2 contains all the data that needs to be sent SMS messages. It needs to be looped and validated again against the historical data in Business Table 2 to prevent multiple SMS messages from being sent within the same sending cycle. If set List1 contains loan receipt numbers 1, 2, 3, and 4, and in the original temporary data table, loan receipt number 3 is in a non-overdue state, after verification, the relevant data for loan receipt number 3 is filtered, and loan receipt numbers 1, 2, and 4, along with their relevant data, are saved to set List2. At this point, the data in set List2 contains the verified data that needs to be sent via SMS. Due to the limitation on the sending interval, business table 2 stores the sending time (time-based sending interval) for each loan receipt number. The system iterates through the loan receipt numbers in set List2, checking if they exist in business table 2. If they exist in business table 2 and the difference between the most recent sending time and the current time is less than the time-based sending interval in the sending strategy, then the loan receipt number is filtered. If they exist in business table 2 and the difference between the most recent sending time and the current time is greater than or equal to the time-based sending interval in the SMS strategy, or if they do not exist in business table 2, an SMS can be sent directly. Finally, the filtered data in set List2 is written into business table 2, and the SMS sending time is recorded.

[0068] The above are merely representative embodiments among the many specific applications of this invention, and do not constitute any limitation on the scope of protection of this invention. All technical solutions formed by transformation or equivalent substitution fall within the scope of protection of this invention.

Claims

1. A method for cyclically verifying the sending of overdue SMS messages, characterized in that, Includes the following steps: Step 1: Set up the SMS policy configuration table for the collection system in the database. The SMS policy configuration table includes ID, availability, and sending policy. The sending policy is configured to send different SMS templates based on different product channels and overdue days. Step 2: Configure a temporary table in the database to store raw data pushed content from the data warehouse. The temporary table includes overdue data that has not been integrated. Configure Business Table 1 in the database. Business Table 1 is used to record the full data after the collection system runs and parses the original data temporary table and integrates it. Business Table 1 includes the ID field, batch number and overdue data generated by the collection system. The ID and batch number are used to distinguish the collection records after different stages of overdue for the same loan number. The overdue data includes loan receipt information, loan overdue information, customer information, and third-party contact information. Loan receipt information includes the loan receipt number and transaction number. Loan overdue information includes the overdue date, overdue days, and overdue amount. Customer information includes the customer's name, customer ID card number, and customer contact information. Third-party contact information includes the name of the associated person and the contact information of the associated person. The ID field is used to store all operations of each loan receipt in the collection system. Configure Business Table 2 in the database. Business Table 2 includes the IOU number, customer information, and SMS template. Step 3: Loop through and query the data in Business Table 1 that match the sending strategy in the SMS strategy configuration table. Compare and verify the results with the original data temporary table and Business Table 2 to obtain the final data that matches the sending strategy. Send the SMS and write the data that matches the sending strategy into Business Table 2. The specific steps of step 3 are as follows: Step 3.1: Create two collections, List1 and List2. List1 and List2 respectively include the IOU number, the customer information corresponding to the IOU number, the SMS sending frequency corresponding to the IOU number, and the SMS template corresponding to the IOU number. The customer information includes the customer's name, mobile phone number, and ID card number. Step 3.2: Traverse and query the data in Business Table 1 that match the sending strategy in SMS Strategy Configuration Table 1, and save them to Collection List1; Step 3.3: Perform a loop check between the data in collection List1 and the original temporary data table. If the check results are consistent each time, save the consistent data to collection List2; otherwise, filter out the abnormal data. Step 3.4: Loop through the IOU numbers in the List2 collection and check if they exist in the business table 2. If they exist, go to step 3.5; otherwise, send the SMS directly and write it into the business table 2, and record the SMS sending time. Step 3.5: Perform loop verification between the data in set List2 and business table 2. If the sending interval of the data in set List2 conforms to the sending strategy after each verification, then send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval does not conform to the sending strategy. The sending interval is a given number of days or a range of days.

2. The method for cyclically verifying and sending overdue SMS messages according to claim 1, characterized in that, Step 3.3 involves querying and comparing the loan information and overdue days in Set List1 using the loan receipt number or customer ID card to see if they match the loan information and overdue days in the original temporary data table.

3. The method for cyclically verifying and sending overdue SMS messages according to claim 2, characterized in that, The specific steps of step 3.5 are as follows: Step 3.51: Identify the loan receipt information and determine whether the loan receipt is currently overdue. If it is overdue, proceed to step 3.42; otherwise, do not process it. Step 3.52: Verify customer information, that is, check whether a single customer has multiple overdue payments. If so, match the sending strategy with the longest overdue IOU and proceed to step 3.53; otherwise, directly match the sending strategy and proceed to step 3.

53. Step 3.53: Verify the sending interval duration, that is, check whether the sending interval duration meets the sending strategy of the loan information. If it does, send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval duration does not meet the sending strategy.

4. A system for cyclically verifying the sending of overdue SMS messages, characterized in that, include: A. Configuration Module: Set up the SMS policy configuration table for the collection system in the database. The SMS policy configuration table includes ID, availability, and sending policy. The sending policy is configured to send different SMS templates based on different product channels and overdue days. B Configuration Module: Configures a temporary table in the database to store raw data pushed content from the data warehouse. The temporary table includes overdue data that has not been integrated and processed. Configure Business Table 1 in the database. Business Table 1 is used to record the full data after the collection system runs and parses the original data temporary table and integrates it. Business Table 1 includes the ID field, batch number and overdue data generated by the collection system. The ID and batch number are used to distinguish the collection records after different stages of overdue for the same loan number. The overdue data includes loan receipt information, loan overdue information, customer information, and third-party contact information. Loan receipt information includes the loan receipt number and transaction number. Loan overdue information includes the overdue date, overdue days, and overdue amount. Customer information includes the customer's name, customer ID card number, and customer contact information. Third-party contact information includes the name of the associated person and the contact information of the associated person. The ID field is used to store all operations of each loan receipt in the collection system. Configure Business Table 2 in the database. Business Table 2 includes the IOU number, customer information, and SMS template. Verification module: Iterates through the business table 1 to query the data that conforms to the sending strategy in the SMS strategy configuration table, compares the results with the original data temporary table and business table 2 to obtain the final data that conforms to the sending strategy, and sends the SMS. At the same time, the data that conforms to the sending strategy is written into business table 2. The specific implementation steps of the verification module are as follows: Step 3.1: Create two collections, List1 and List2. List1 and List2 respectively include the IOU number, the customer information corresponding to the IOU number, the SMS sending frequency corresponding to the IOU number, and the SMS template corresponding to the IOU number. The customer information includes the customer's name, mobile phone number, and ID card number. Step 3.2: Traverse and query the data in Business Table 1 that match the sending strategy in SMS Strategy Configuration Table 1, and save them to Collection List1; Step 3.3: Perform a loop check between the data in collection List1 and the original temporary data table. If the check results are consistent each time, save the consistent data to collection List2; otherwise, filter out the abnormal data. Step 3.4: Loop through the IOU numbers in the List2 collection and check if they exist in the business table 2. If they exist, go to step 3.5; otherwise, send the SMS directly and write it into the business table 2, and record the SMS sending time. Step 3.5: Perform loop verification between the data in set List2 and business table 2. If the sending interval of the data in set List2 conforms to the sending strategy after each verification, then send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval does not conform to the sending strategy. The sending interval is a given number of days or a range of days.

5. The system for cyclically verifying and sending overdue SMS messages according to claim 4, characterized in that, Step 3.3 involves querying and comparing the loan information and overdue days in Set List1 using the loan receipt number or customer ID card to see if they match the loan information and overdue days in the original temporary data table.

6. The system for cyclically verifying and sending overdue SMS messages according to claim 5, characterized in that, The specific steps of step 3.5 are as follows: Step 3.51: Identify the loan receipt information and determine whether the loan receipt is currently overdue. If it is overdue, proceed to step 3.42; otherwise, do not process it. Step 3.52: Verify customer information, that is, check whether a single customer has multiple overdue payments. If so, match the sending strategy with the longest overdue IOU and proceed to step 3.53; otherwise, directly match the sending strategy and proceed to step 3.

53. Step 3.53: Verify the sending interval duration, that is, check whether the sending interval duration meets the sending strategy of the loan information. If it does, send the SMS and write it into business table 2, and record the SMS sending time. Otherwise, filter out the data whose sending interval duration does not meet the sending strategy.

7. A storage medium for a method of cyclically verifying the sending of overdue SMS messages, characterized in that: A server storing the method for cyclically verifying the sending of overdue SMS messages as described in any one of claims 1-3.