Bill processing method and device and server

Abstract

The invention provides a bill processing method, a bill processing device and a server, which can be used in the financial field. When it is determined that the preset triggering condition is met currently, historical reminding data of the current bill query period of the target user is obtained; determining target bill query time in the current bill query period according to historical reminding data of the current bill query period of the target user and bill query time corresponding to a historical bill query period; detecting whether a target bill exists based on the target bill query time; and sending a target payment prompt to the target user under the condition of determining that the target bill exists. Therefore, the target bill query time of the current account checking period can be quickly and accurately determined according to the historical reminding data, and the reminding message carrying the payment link can be sent to the user for the unpaid bill, so that the user can directly pay the unpaid bill through the reminding message, the operation of the user is simplified, and the user experience is improved. And the payment experience of the user is improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and more particularly to a bill processing method, device and server. Background Art

[0002] At present, the payment reminder process of mobile banking is relatively simple. Most of them are based on the reminder time set by the user. It is often the case that the reminder comes before the payment, and the user needs to manually confirm the payment, resulting in low overall bill processing efficiency and easy omission of bills. In addition, based on the existing method, users are often unable to pay directly after receiving the payment reminder, which makes the user operation more cumbersome and affects the user's payment experience.

[0003] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0004] This specification provides a bill processing method, device and server to solve the problems of low efficiency, easy missing of bills and poor payment experience in the prior art. It can quickly and accurately determine the target bill query time of the current account checking cycle and improve the user's payment experience.

[0005] This manual provides a bill processing method, including:

[0006] When it is determined that the preset trigger condition is currently met, historical reminder data of the target user in the current bill query cycle is obtained; wherein the historical reminder data includes the number of historical payment reminders sent to the target user in the historical bill query cycle, the sending time of the historical payment reminder, and the payment time when the target user paid the historical payment reminder;

[0007] Determine a target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0008] Based on the target bill query time, detecting whether a target bill exists;

[0009] When it is determined that the target bill exists, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0010] In one embodiment, determining the target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle includes:

[0011] Determine the time difference according to the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder;

[0012] The target bill query time is determined according to the number of historical payment reminders sent to the target user during the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period.

[0013] In one embodiment, determining the target bill query time according to the number of historical payment reminders sent to the target user within the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period includes:

[0014] If the number of historical payment reminders sent to the target user during the historical bill query period is not greater than a preset number threshold, determining the target bill query time according to the bill query time corresponding to the historical bill query period;

[0015] When the number of historical payment reminders sent to the target user during the historical bill query period is greater than a preset number threshold, and the time difference is less than a preset difference threshold, determining the target bill query time according to the bill query time corresponding to the historical bill query period;

[0016] When the number of historical payment reminders sent to the target user during the historical bill query cycle is greater than a preset number threshold and the time difference is not less than a preset difference threshold, the target bill query time is determined based on the bill query time corresponding to the historical bill query cycle and the time difference.

[0017] In one embodiment, the bill query time corresponding to the historical bill query cycle is determined according to the number of payments made by the target user for bills in different time periods of a preset historical payment cycle.

[0018] In one embodiment, there are multiple target bill query times, and determining the target bill query time in the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle includes:

[0019] Determine the first bill query time in the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0020] Determine the time period in which the first bill query time is located within the current bill query cycle, and determine a target time interval corresponding to the time period in which the first bill query time is located according to a preset correspondence between the time period and the time interval;

[0021] The target bill query time is determined according to the first bill query time and the target time interval.

[0022] In one embodiment, the method further comprises:

[0023] In the case where it is determined that the target bill does not exist, determining a second bill query time according to a preset delay interval and the target bill query time;

[0024] Based on the second bill query time, it is detected whether a target bill exists.

[0025] In one embodiment, before determining the second bill query time according to the preset delay interval and the target bill query time, the method further includes:

[0026] The time period in which the target bill query time is located within the current bill query cycle is determined, and the preset delay interval corresponding to the time period in which the target bill query time is located is determined according to a preset correspondence between the time period and the time interval.

[0027] In one embodiment, determining the target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle includes:

[0028] Determine the payment time difference of the target user for different types of bills according to the historical reminder data of the current bill query period of the target user, wherein the payment time difference is determined according to the sending time of the historical payment reminder and the payment time when the target user pays the historical payment reminder;

[0029] The historical billing time of the different types of bills is obtained, and the target bill query time for the different types of bills in the current bill query cycle is determined based on the historical billing time and the payment time difference of the target user for the different types of bills.

[0030] In one embodiment, when determining that the target bill exists, sending a target payment reminder to the target user includes:

[0031] In the case where it is determined that the target bill exists, determining, according to the type of the target bill, a target reminder method corresponding to the type of the target bill in the preset reminder methods;

[0032] According to the target reminder method, the target payment reminder is sent to the target user.

[0033] This fact sheet provides an alternative method of billing, including:

[0034] When it is determined that the preset trigger condition is currently met, historical reminder data of the current bill query cycle of the target user is obtained; wherein the historical reminder data includes the billing time of the historical bill and the historical payment time when the target user paid the historical bill;

[0035] Determine the target bill query time within the current bill query cycle according to the billing time of the historical bill;

[0036] Determine the first time of the target user in the current bill query cycle according to the historical payment time;

[0037] Based on the target bill query time and the first time, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0038] In one embodiment, sending a target payment reminder to the target user based on the target bill query time and the first time includes:

[0039] Based on the target bill query time, detecting whether the target user has paid the target bill;

[0040] When non-payment is detected, the target payment reminder is sent to the target user based on the first time.

[0041] This specification provides a bill processing device, including:

[0042] A historical data determination module, configured to obtain historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the number of historical payment reminders sent to the target user during the historical bill query cycle, the sending time of the historical payment reminder, and the payment time when the target user paid the historical payment reminder;

[0043] A bill query determination module, configured to determine a target bill query time within a current bill query cycle based on historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0044] A target bill determination module, used to detect whether a target bill exists based on the target bill query time;

[0045] The payment determination module is used to send a target payment reminder to the target user when it is determined that the target bill exists. The target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0046] The present specification also provides a server, comprising a processor and a memory for storing processor executable instructions, wherein the processor implements a bill processing method when executing the instructions.

[0047] The present specification also provides a computer-readable storage medium having computer instructions stored thereon, which implement a bill processing method when the instructions are executed.

[0048] The present specification also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, a bill processing method is implemented.

[0049] Based on a bill processing method provided by this specification, when it is determined that the preset trigger condition is currently met, the historical reminder data of the current bill query cycle of the target user is obtained; wherein the historical reminder data includes the number of historical payment reminders sent to the target user in the historical bill query cycle, the sending time of the historical payment reminder, and the payment time of the target user for the historical payment reminder; according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle, the target bill query time in the current bill query cycle is determined; based on the target bill query time, whether there is a target bill is detected; if it is determined that the target bill exists, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of the payment task for the target bill. In this way, when it is determined that the preset trigger condition is currently met, the target bill query time in the current bill query cycle can be quickly and accurately determined based on the historical reminder data of the current bill query cycle of the target user, so that based on the target bill query time, when it is determined that the target bill exists, the target payment reminder is sent to the target user. This can effectively avoid the poor user experience caused by the target user's frequent manual account checks during the current bill inquiry cycle, simplify user operations, and improve bill inquiry efficiency as well as accuracy and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, the target user can directly trigger the payment task for the target bill according to the payment link in the target payment reminder, thus connecting the payment process, further simplifying user operations, and improving bill processing efficiency and user payment experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 It is a flowchart of a bill processing method provided by an embodiment of this specification;

[0052] Figure 2 It is a schematic diagram of the overall flow of a bill processing method provided by an embodiment of this specification;

[0053] Figure 3 It is a flowchart of updating the target bill query time provided by an embodiment of this specification;

[0054] Figure 4 It is a flowchart of an initial target bill query time provided by an embodiment of this specification;

[0055] Figure 5 It is a flowchart of multiple target bill query times provided by an embodiment of this specification;

[0056] Figure 6 is a flowchart of another bill processing method provided by an embodiment of this specification;

[0057] Figure 7 It is a schematic diagram of the structure of an electronic device provided by an embodiment of this specification;

[0058] Figure 8 It is a schematic diagram of the structure of a bill processing device provided by an embodiment of this specification;

[0059] Fig. 9 It is a schematic diagram of the structural composition of another bill processing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0061] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0062] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0063] See also Figure 1As shown, the embodiment of this specification provides a bill processing method, wherein the method is specifically applied to the server side. When implemented specifically, the method may include the following contents:

[0064] S101: When it is determined that a preset trigger condition is currently met, historical reminder data of a current bill query period of a target user is obtained; wherein the historical reminder data includes the number of historical payment reminders sent to the target user during the historical bill query period, the sending time of the historical payment reminders, and the payment time when the target user paid for the historical payment reminders;

[0065] S102: Determine a target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0066] S103: Detecting whether a target bill exists based on the target bill query time;

[0067] S104: When it is determined that the target bill exists, a target payment reminder is sent to the target user, wherein the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0068] During specific implementation, it may be first detected whether a preset trigger condition is currently met.

[0069] The above detection of whether the preset triggering condition is currently satisfied may include: determining whether the current bill query cycle has been reached, or determining whether the current number of arrears is greater than a preset number threshold, etc.

[0070] For example, taking the bill query cycle as each natural month, the preset trigger condition can be to determine whether the current date has reached the first day of each natural month, that is, if the current date is the first day of the natural month (such as January 1, February 1, etc.), it can be determined that the preset trigger condition is currently met. Alternatively, the number of arrears of the target user within a preset period (such as the past three months, the past six months, etc.) can also be obtained, and the preset trigger condition can be to determine whether the current number of arrears is greater than the preset number threshold, that is, if the current number of arrears is greater than the preset number threshold, it can be determined that the preset trigger condition is currently met.

[0071] In addition, there may be various trigger conditions, and different trigger conditions may be selected according to different actual application scenarios, and the embodiments of this specification do not specifically limit this.

[0072] Among them, the above-mentioned historical bill query cycle may be one or more bill query cycles before the current bill query cycle. For example, the historical bill query cycle may be the three bill query cycles before the current bill query cycle. Specifically, assuming that the current bill query cycle may be April 1st to April 30th, then the historical bill query cycle may include historical bill query cycle 1 (i.e. January 1st to January 31st), historical bill query cycle 2 (i.e. February 1st to February 28th), and historical bill query cycle 3 (i.e. March 1st to March 31st).

[0073] In some embodiments, historical reminder data of the current bill query period of the target user may be obtained in the following manner, including:

[0074] Specifically, the historical reminder data related to the target user within the historical bill query period can be obtained by querying the background log of the payment reminder system or accessing the database of the bill management system.

[0075] In some embodiments, the target bill query time within the current bill query cycle may be determined according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle in the following manner, including:

[0076] The target bill query time in the current bill query cycle is determined by using a preset first model based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle.

[0077] Among them, the preset first model can be a model constructed based on a machine learning algorithm for determining the bill query time.

[0078] The target bill may be an unpaid bill, or the target bill may be an unpaid bill whose bill type meets the preset bill type. The preset bill type may be a type preset by the target user, or a bill type determined according to the target user's arrears (e.g., the type of bill whose arrears exceed a preset threshold within a preset period may be determined as the preset bill type). For example, if the target user has arrears for water bills exceeding a preset threshold in the past three months, the water bill may be determined as the preset bill type, that is, when the target bill query time is reached, it may be queried whether there is an unpaid water bill (i.e., the target bill).

[0079] In addition, if Figure 2 As shown, after sending the target payment reminder to the target user, the payment status of the target bill can be obtained. When the payment status of the target bill is paid, the target payment reminder time and payment time of the target bill are stored.

[0080] For example, if there are multiple target bill query times within the current bill query cycle, the payment status of the target bill of the previous target bill query time can be obtained at each target bill query time. If there is an unpaid target bill, the target payment reminder can continue to be sent to the target user at the current target bill query time.

[0081] Further, assuming that the target bill query time within the current bill query cycle includes April 1 and April 15, if the existence of target bill 1 is detected on April 1, a target payment reminder for target bill 1 can be sent to the target user, and the payment status of target bill 1 can be obtained on April 15. If the payment status of target bill 1 is unpaid, payment reminders for target bill 1 can continue to be sent to the target user on April 15.

[0082] In addition, the time interval for obtaining the payment status of the target bill can be determined based on the bill level of the target bill, and when the payment status of the target bill is unpaid, the target payment reminder can be sent to the target user again based on the bill level of the target bill until the payment status of the target bill is paid.

[0083] For example, assuming that the target bill query time in the current bill query cycle includes April 1 and April 15, if the existence of target bill 1 and target bill 2 is detected on April 1, target payment reminders for target bill 1 and target bill 2 can be sent to the target user. If the bill level of target bill 1 is higher than the bill level of target bill 2, the payment status of target bill 1 can be obtained every three days (i.e., April 4, April 7, etc.), and when the payment status of target bill 1 is found to be unpaid, the target payment reminder for target bill 1 is sent to the target user again until the payment status of target bill 1 is paid. In addition, since the bill level of target bill 2 is lower than the bill level of target bill 1, the payment status of target bill 2 can be queried again on April 15.

[0084] Among them, the bill level of the target bill can be determined based on factors such as the historical payment habits of the target user, the payment preferences of the target user, and the grace period of the payment reminder system.

[0085] Based on the above embodiment, when it is determined that the preset trigger condition is currently met, the target bill query time within the current bill query cycle can be quickly and accurately determined based on the historical reminder data of the target user's current bill query cycle, so that based on the target bill query time, when it is determined that the target bill exists, a target payment reminder is sent to the target user. This can effectively avoid the situation where the target user needs to frequently perform manual account checks during the current bill query cycle, which causes poor user experience, simplifies user operations, and improves bill query efficiency, accuracy, and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, it is convenient for the target user to directly trigger the execution of the payment task for the target bill according to the payment link in the target payment reminder, which connects the payment process in series, further simplifies user operations, and improves bill processing efficiency and user payment experience.

[0086] In some embodiments, the target bill query time within the current bill query cycle is determined based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle. When the method is specifically implemented, it may also include the following contents:

[0087] S1: determining a time difference according to the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder;

[0088] S2: Determine the target bill query time according to the number of historical payment reminders sent to the target user during the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period.

[0089] Based on the above embodiment, the target bill query time can be accurately determined by combining historical reminder data and jointly analyzing the billing rules of the target bill and the payment habits of the target user.

[0090] In some embodiments, the time difference may be determined according to the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder in the following manner, including:

[0091] S1: Obtaining a first difference between the sending time of each of the historical payment reminders and the payment time at which the target user paid for the historical payment reminder;

[0092] S2: Determine the time difference according to the first difference.

[0093] Specifically, the mean (or maximum value, minimum value, median, etc.) of the first difference may be determined as the time difference.

[0094] In some embodiments, see Figure 3 As shown, the target bill query time is determined according to the number of historical payment reminders sent to the target user within the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period. When the method is specifically implemented, it may also include the following contents:

[0095] S1: when the number of historical payment reminders sent to the target user within the historical bill query period is not greater than a preset number threshold, determine the target bill query time according to the bill query time corresponding to the historical bill query period;

[0096] S2: if the number of historical payment reminders sent to the target user during the historical bill query period is greater than a preset number threshold, and the time difference is less than a preset difference threshold, determine the target bill query time according to the bill query time corresponding to the historical bill query period;

[0097] S3: When the number of historical payment reminders sent to the target user during the historical bill query cycle is greater than a preset number threshold, and the time difference is not less than a preset difference threshold, the target bill query time is determined according to the bill query time corresponding to the historical bill query cycle and the time difference.

[0098] Based on the above embodiments, different situations can be divided according to the relationship between the number of historical payment reminders and the preset number threshold, and / or the relationship between the time difference and the preset difference threshold, so as to determine the target bill query time in different situations and improve the accuracy of determining the target bill query time.

[0099] Among them, when there are multiple historical bill query cycles, the target number of historical payment reminders can be determined according to the number of historical payment reminders corresponding to the multiple historical bill query cycles, and based on whether the target number of historical payment reminders is not greater than the preset number threshold, it is determined whether the number of historical payment reminders sent to the target user within the historical bill query cycle is not greater than the preset number threshold.

[0100] For example, assuming that there are three historical bill query cycles, and the number of historical payment reminders corresponding to these three historical bill query cycles are 1, 2, and 3 respectively, then the target number of historical payment reminders (i.e., 2 times) can be determined based on the average of these three numbers, and then, when the preset number threshold is greater than 3 times, it can be determined that the number of historical payment reminders sent to the target user during the historical bill query cycle is not greater than the preset number threshold (i.e., the target number of historical payment reminders is not greater than the preset number threshold).

[0101] In some embodiments, when the number of historical payment reminders sent to the target user within the historical bill query cycle is not greater than a preset number threshold, determining the target bill query time according to the bill query time corresponding to the historical bill query cycle includes:

[0102] S1: when the number of historical payment reminders sent to the target user within the historical bill query cycle is not greater than a preset number threshold, obtaining the time period of the bill query time corresponding to the historical bill query cycle;

[0103] S2: according to the preset correspondence between the time period and the duration, obtaining the target duration corresponding to the time period;

[0104] S3: Determine the target bill query time according to the time period of the bill query time corresponding to the historical bill query cycle and the target duration.

[0105] For example, see Figure 3 As shown, it is assumed that the preset correspondence between time periods and durations is shown in Table 1 below.

[0106] Table 1

[0107] Time Duration Period 1 3 days Period 2 2 days Period 3 1 day

[0108] Assuming that the bill query time corresponding to the historical bill query cycle is the 9th day of the historical bill query cycle, that is, the bill query time corresponding to the historical bill query cycle (that is, the historical bill query time) is in time period 1, then, according to the preset correspondence shown in Table 1 above, the target duration can be determined to be 3 days, that is, the target bill query time can be the 6th day of the current bill query cycle (that is, 9-3).

[0109] In some embodiments, determining the target bill query time according to the bill query time corresponding to the historical bill query cycle and the time difference includes:

[0110] The target bill query time is determined according to the bill query time corresponding to the historical bill query cycle and the product of the time difference and a preset multiple.

[0111] Specifically, for example, taking the preset multiple of 0.5 as an example, assuming that the bill query time corresponding to the historical bill query cycle is the 3rd day, and the time difference is 4 days, then the target bill query time can be the 5th day of the current bill query cycle (ie 3+4*0.5).

[0112] In some embodiments, see Figure 4As shown, the bill query time corresponding to the historical bill query cycle can be determined according to the number of payments made by the target user for the bill in different time periods of the preset historical payment cycle. When the specific method is implemented, it can also include the following contents:

[0113] S1: Divide the historical bill query cycle into multiple time periods, and obtain the number of payments corresponding to each time period;

[0114] S2: Determine the payment proportion corresponding to each of the time periods according to the number of payments corresponding to each of the time periods and the number of payments corresponding to the historical bill query cycle;

[0115] S3: Determine the bill query time corresponding to the historical bill query cycle according to the payment proportion corresponding to each of the time periods.

[0116] Based on the above embodiment, the payment habits of the target user can be determined according to the payment proportions in different time periods, that is, the bill query time corresponding to the historical bill query cycle can be accurately determined according to the payment proportions in different time periods.

[0117] In some embodiments, determining the bill query time corresponding to the historical bill query cycle according to the payment proportion corresponding to each of the time periods includes:

[0118] In the case where there is a target time period in which the payment ratio is not less than the preset ratio among the payment ratios corresponding to the multiple time periods, determining a target bill query time according to the target time period; or,

[0119] When there is no time period in which the payment proportion corresponding to the multiple time periods is greater than the preset proportion, the preset query date is set as the target bill query time.

[0120] For example, assuming that the historical bill query cycle can be divided into the first time period, the second time period and the third time period, and the preset proportion is 50%, then among these three time periods, if there is a target time period in which the payment proportion is not less than 50%, the target bill query time can be determined according to the target time period; if the payment proportions corresponding to these three time periods are all less than 50%, the preset query date (such as the first day of each bill query cycle) can be set as the target bill time.

[0121] Among them, if there is only one target time period, the middle time point (or starting time point, ending time point, etc.) of the target time period can be determined as the target bill query time; if there are two target time periods, the middle time point of the two target time periods can be determined as the target bill query time.

[0122] In some embodiments, participation Figure 5As shown, there are multiple target bill query times. According to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle, the target bill query time within the current bill query cycle is determined. When the method is specifically implemented, it may also include the following contents:

[0123] S1: Determine the first bill query time in the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0124] S2: Determine the time period in which the first bill query time is located within the current bill query cycle, and determine a target time interval corresponding to the time period in which the first bill query time is located according to a preset correspondence between the time period and the time interval;

[0125] S3: Determine the target bill query time according to the first bill query time and the target time interval.

[0126] Based on the above embodiments, in the current bill query cycle, multiple target bill query times can be accurately determined according to the time period in which the bill query time is located, and the correspondence between the time period and the time interval, so as to avoid resource waste caused by frequent queries in the current bill query cycle and missed orders caused by too few queries.

[0127] The preset correspondence between the time period and the time interval may be as shown in Table 2 below.

[0128] Table 2

[0129] Time Time interval Period 1 3 days Period 2 2 days Period 3 1 day

[0130] For example, assuming that the current bill query cycle includes time period 1 (including days 1 to 10 of the current bill query cycle), time period 2 (including days 11 to 20 of the current bill query cycle) and time period 3 (including days 21 to 30 of the current bill query cycle), the target time interval can be determined based on the time period in which the first bill query time is located and the preset correspondence between the time periods and time intervals shown in Table 2 above, and then the target bill query time can be determined based on the first bill query time and the target time interval.

[0131] Specifically, assuming that the first bill query time is the 12th day of the current bill query cycle, then, according to the corresponding relationship shown in Table 2, it can be determined that the target time interval corresponding to the first bill query time is 2 days. According to the target time interval and the first bill query time, it can be determined that the target bill query time includes the 12th day, the 15th day, the 18th day, the 21st day, the 24th day, the 27th day, and the 30th day of the current bill query cycle.

[0132] In some embodiments, the method may further include the following when implemented:

[0133] S1: when it is determined that the target bill does not exist, determining a second bill query time according to a preset delay interval and the target bill query time;

[0134] S2: Based on the second bill query time, detect whether a target bill exists.

[0135] Based on the above embodiment, if the target bill does not exist at the target bill query time, the second bill query time can be determined based on the preset delay interval, so as to continue to detect whether the target bill exists based on the second bill query time to avoid missing bills.

[0136] In some embodiments, before determining the second bill query time according to the preset delay interval and the target bill query time, the method may further include the following when implemented:

[0137] The time period in which the target bill query time is located within the current bill query cycle is determined, and the preset delay interval corresponding to the time period in which the target bill query time is located is determined according to a preset correspondence between the time period and the time interval.

[0138] The preset correspondence between the time period and the time interval may be the same as the above preset correspondence, that is, the preset correspondence between the time period and the time interval may also be the preset correspondence as shown in Table 2 above.

[0139] Based on the above embodiment, the preset delay interval corresponding to the time period of the target bill query time can be determined in a targeted manner according to the preset correspondence between the time period and the time interval, so as to avoid the problem of frequent queries or too few queries.

[0140] For example, if the target bill query time is the 25th day of the current bill query cycle, then according to the corresponding relationship shown in Table 1, it can be determined that the preset time interval corresponding to the target bill query time is 1 day. That is, when it is determined that there is no target bill, the second bill query time is determined according to the preset delay interval and the target bill query time, which can be the 27th day of the current bill query cycle, and whether there is a target bill can be detected based on the 27th day of the current bill query cycle.

[0141] In addition, if it is determined on the 27th day of the current bill query cycle (i.e., the second bill query time) that there is no target bill, the third bill query time can be determined based on the preset delay interval corresponding to the time period of the second bill query time and the second bill query time, and based on the third bill query time, it can be detected whether there is a target bill.

[0142] In some embodiments, determining the target bill query time within the current bill query cycle based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle may also include the following contents:

[0143] S1: determining the payment time difference of the target user for different types of bills according to the historical reminder data of the current bill query period of the target user, wherein the payment time difference is determined according to the sending time of the historical payment reminder and the payment time when the target user pays the historical payment reminder;

[0144] S2: Obtain the historical billing time of the different types of bills, and determine the target bill query time for the different types of bills in the current bill query cycle based on the historical billing time and the payment time difference of the target user for the different types of bills.

[0145] Based on the above embodiment, the historical data of different types of bills (i.e., payment time difference and historical billing time) can be combined to further accurately determine the target bill query time corresponding to different types of bills, thereby improving the accuracy of determining the target bill query time.

[0146] Among them, the above-mentioned different types of bills may be water bills, electricity bills, gas bills, etc.

[0147] For example, when the payment time difference of a certain type of bill is not greater than the preset time threshold, the target bill query time for bills of this type in the current bill query cycle can be determined based on the historical bill issuance time; when the payment time difference of a certain type of bill is greater than the preset time threshold, the target bill query time for bills of this type in the current bill query cycle can be determined based on the sum of the historical bill issuance time and the payment time difference.

[0148] Specifically, assuming that the target user's payment time difference for electricity bills is not greater than the preset time threshold, while the payment time difference for water bills is greater than the preset time threshold, then the target bill query time for the electricity bill in the current bill query cycle can be set to the historical billing time of the electricity bill, and the target bill query time for the water bill in the current bill query cycle can be determined by the sum of the historical billing time and the payment time difference of the water bill.

[0149] In this way, different bill query times can be set for different types of bills according to the user's payment habits for different types of bills.

[0150] In some embodiments, when it is determined that the target bill exists, a target payment reminder is sent to the target user. When the method is specifically implemented, the following contents may also be included:

[0151] S1: when it is determined that the target bill exists, determining, according to the type of the target bill, a target reminder method corresponding to the type of the target bill in the preset reminder methods;

[0152] S2: Sending the target payment reminder to the target user according to the target reminder method.

[0153] Based on the above embodiment, a payment reminder can be sent to the target user according to the target reminder method corresponding to the type of the target bill, thereby improving the reminder efficiency and ensuring the reminder effect.

[0154] Among them, the above-mentioned preset reminder methods include but are not limited to text messages, emails, application push, etc.

[0155] As can be seen from the above, a bill processing method provided by an embodiment of the present specification obtains historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the number of historical payment reminders sent to the target user in the historical bill query cycle, the sending time of the historical payment reminder, and the payment time of the target user for the historical payment reminder; according to the historical reminder data of the current bill query cycle of the target user, and the bill query time corresponding to the historical bill query cycle, the target bill query time in the current bill query cycle is determined; based on the target bill query time, whether there is a target bill is detected; if it is determined that the target bill exists, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of the payment task for the target bill. In this way, if it is determined that the preset trigger condition is currently met, the target bill query time in the current bill query cycle can be quickly and accurately determined based on the historical reminder data of the current bill query cycle of the target user, so as to send the target payment reminder to the target user based on the target bill query time and if it is determined that the target bill exists. This can effectively avoid the poor user experience caused by the target user's frequent manual account checks during the current bill inquiry cycle, simplify user operations, and improve bill inquiry efficiency as well as accuracy and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, the target user can directly trigger the payment task for the target bill according to the payment link in the target payment reminder, thus connecting the payment process, further simplifying user operations, and improving bill processing efficiency and user payment experience.

[0156] See also Figure 6 , the embodiment of this specification provides another bill processing method, wherein the method is specifically applied to the server side. When implemented specifically, the method may include the following contents:

[0157] S601: When it is determined that the preset trigger condition is currently met, historical reminder data of the current bill query cycle of the target user is obtained; wherein the historical reminder data includes the billing time of the historical bill and the historical payment time when the target user paid the historical bill;

[0158] S602: Determine a target bill query time within a current bill query cycle according to the billing time of the historical bill;

[0159] S603: Determine the first time of the target user in the current bill query cycle according to the historical payment time;

[0160] S604: Based on the target bill query time and the first time, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0161] In some embodiments, the method of sending a target payment reminder to the target user based on the target bill query time and the first time may further include the following when the method is specifically implemented:

[0162] S1: Based on the target bill query time, detecting whether the target user has paid the target bill;

[0163] S2: When non-payment is detected, sending the target payment reminder to the target user based on the first time.

[0164] As can be seen from the above, a bill processing method provided by an embodiment of the present specification obtains historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the billing time of the historical bill and the historical payment time of the target user for the historical bill; according to the billing time of the historical bill, the target bill query time within the current bill query cycle is determined; according to the historical payment time, the first time of the target user within the current bill query cycle is determined; based on the target bill query time and the first time, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of the payment task for the target bill. In this way, when it is determined that the preset trigger condition is currently met, the target bill query time within the current bill query cycle can be determined more accurately and quickly based on the billing time of the historical bill and the historical payment time of the target user for the historical bill, so as to send a target payment reminder to the target user based on the target bill query time when it is determined that there is a target bill. It ensures that the target bill query time of the current bill query cycle is after the target bill is issued, thereby effectively avoiding the poor user experience caused by the target user's frequent manual account checks during the current bill query cycle, simplifying user operations, and improving bill query efficiency as well as accuracy and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, the target user can directly trigger the payment task for the target bill according to the payment link in the target payment reminder, connecting the payment process in series, further simplifying user operations, and improving bill processing efficiency and user payment experience.

[0165] See also Figure 7 As shown, the embodiment of this specification also provides a specific electronic device, wherein the electronic device includes a network communication port 701, a processor 702 and a memory 703, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0166] The network communication port 701 may be used to obtain historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met.

[0167] The processor 702 can be specifically used to determine the target bill query time within the current bill query cycle based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle; based on the target bill query time, detect whether there is a target bill; and when it is determined that the target bill exists, send a target payment reminder to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0168] The memory 703 may be specifically used to store corresponding instruction programs.

[0169] Based on the above method, the relevant structural performance of the electronic device can be effectively utilized, the data processing speed of the electronic device can be improved, and the bill processing method can be efficiently implemented.

[0170] In this embodiment, the network communication port 701 can be a virtual port that is bound to different communication protocols so that different data can be sent or received. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. In addition, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM, CDMA, etc.; it can also be a Wifi chip; it can also be a Bluetooth chip.

[0171] In this embodiment, the processor 702 may be implemented in any appropriate manner. For example, the processor may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, etc. This specification does not limit this.

[0172] In this embodiment, the memory 703 may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function that has no physical form is also called a memory, such as RAM, FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0173] The embodiment of the present specification also provides a computer-readable storage medium based on the above-mentioned bill processing method, the computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed, the following are achieved: when it is determined that the preset trigger condition is currently met, the historical reminder data of the current bill query cycle of the target user is obtained; wherein the historical reminder data includes the number of historical payment reminders sent to the target user within the historical bill query cycle, the sending time of the historical payment reminder, and the payment time of the target user for the historical payment reminder; according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle, the target bill query time within the current bill query cycle is determined; based on the target bill query time, whether there is a target bill is detected; when it is determined that the target bill exists, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of the payment task for the target bill.

[0174] In this embodiment, the storage medium includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD), or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0175] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other implementations and will not be described in detail here.

[0176] The embodiments of the present specification also provide a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, it implements the following method steps: when it is determined that a preset trigger condition is currently met, obtaining historical reminder data of the current bill query cycle of the target user; wherein the historical reminder data includes the number of historical payment reminders sent to the target user within the historical bill query cycle, the sending time of the historical payment reminder, and the payment time of the target user for the historical payment reminder; according to the historical reminder data of the current bill query cycle of the target user, and the bill query time corresponding to the historical bill query cycle, determining the target bill query time within the current bill query cycle; based on the target bill query time, detecting whether there is a target bill; when it is determined that the target bill exists, sending a target payment reminder to the target user, the target payment reminder carrying a payment link for the target bill, and the payment link being used to trigger the execution of the payment task for the target bill.

[0177] See also Figure 8 At the software level, the embodiment of this specification also provides a bill processing device, which may specifically include the following structural modules:

[0178] The historical data determination module 801 is used to obtain the historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the number of historical payment reminders sent to the target user during the historical bill query cycle, the sending time of the historical payment reminder, and the payment time when the target user paid the historical payment reminder;

[0179] The bill query determination module 802 is used to determine the target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle;

[0180] A target bill determination module 803, configured to detect whether a target bill exists based on the target bill query time;

[0181] The payment determination module 804 is used to send a target payment reminder to the target user when it is determined that the target bill exists. The target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of the payment task for the target bill.

[0182] In some embodiments, the above-mentioned bill query determination module 802, when implemented, determines the time difference based on the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder; the target bill query time determination module is used to determine the target bill query time based on the number of historical payment reminders sent to the target user during the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period.

[0183] In some embodiments, when the above-mentioned target bill query time determination module is specifically implemented, when the number of historical payment reminders sent to the target user during the historical bill query cycle is not greater than the preset number threshold, the target bill query time is determined according to the bill query time corresponding to the historical bill query cycle; when the number of historical payment reminders sent to the target user during the historical bill query cycle is greater than the preset number threshold, and the time difference is less than the preset difference threshold, the target bill query time is determined according to the bill query time corresponding to the historical bill query cycle; when the number of historical payment reminders sent to the target user during the historical bill query cycle is greater than the preset number threshold, and the time difference is not less than the preset difference threshold, the target bill query time is determined according to the bill query time corresponding to the historical bill query cycle and the time difference.

[0184] In some embodiments, the bill query time corresponding to the above historical bill query cycle is determined according to the number of payments made by the target user for the bill in different time periods of a preset historical payment cycle.

[0185] In some embodiments, there are multiple target bill query times. When the bill query determination module 802 is implemented, it determines the first bill query time in the current bill query cycle based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle; determines the time period in which the first bill query time is located in the current bill query cycle, and determines the target time interval corresponding to the time period in which the first bill query time is located based on the preset correspondence between the time period and the time interval; determines the target bill query time based on the first bill query time and the target time interval.

[0186] In some embodiments, the method further comprises:

[0187] A second bill query time determination module, configured to determine a second bill query time according to a preset delay interval and the target bill query time when it is determined that the target bill does not exist;

[0188] The target bill query module is used to detect whether a target bill exists based on the second bill query time.

[0189] In some embodiments, before the above-mentioned target bill query module, during specific implementation, the time period in which the target bill query time is located within the current bill query cycle is determined, and based on the preset correspondence between the time period and the time interval, the preset delay interval corresponding to the time period in which the target bill query time is located is determined.

[0190] In some embodiments, the above-mentioned bill query determination module 802, when implemented, determines the payment time difference of the target user for different types of bills based on the historical reminder data of the current bill query cycle of the target user, and the payment time difference is determined based on the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder; obtains the historical billing time of the different types of bills, and determines the target bill query time for different types of bills within the current bill query cycle based on the historical billing time and the payment time difference of the target user for different types of bills.

[0191] In some embodiments, the above-mentioned payment determination module 804, when specifically implemented, when it is determined that the target bill exists, determines the target reminder method corresponding to the type of the target bill in the preset reminder method according to the type of the target bill; and sends the target payment reminder to the target user according to the target reminder method.

[0192] As can be seen from the above, based on a bill processing device provided by the embodiment of this specification, when it is determined that the preset trigger condition is currently met, the target bill query time within the current bill query cycle can be quickly and accurately determined based on the historical reminder data of the target user's current bill query cycle, so as to send a target payment reminder to the target user based on the target bill query time and when it is determined that the target bill exists. This can effectively avoid the situation where the target user needs to frequently perform manual account checks during the current bill query cycle, which causes poor user experience, simplifies user operations, and improves bill query efficiency, accuracy, and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, it is convenient for the target user to directly trigger the execution of the payment task for the target bill according to the payment link in the target payment reminder, which connects the payment process in series, further simplifies user operations, and improves bill processing efficiency and user payment experience.

[0193] See also Fig. 9 At the software level, the embodiment of this specification also provides another bill processing device, which may specifically include the following structural modules:

[0194] The data determination module 901 is used to obtain the historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the billing time of the historical bill and the historical payment time when the target user paid the historical bill;

[0195] A query determination module 902, configured to determine a target bill query time within a current bill query cycle according to the billing time of the historical bill;

[0196] A first time determination module 903, for determining the first time of the target user in the current bill query cycle according to the historical payment time;

[0197] The payment reminder module 904 is used to send a target payment reminder to the target user based on the target bill query time and the first time. The target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

[0198] In some embodiments, the above-mentioned payment reminder module 904, when implemented, detects whether the target user has paid the target bill based on the target bill query time; if non-payment is detected, the target payment reminder is sent to the target user based on the first time.

[0199] As can be seen from the above, based on a bill processing device provided by the embodiment of this specification, when it is determined that the preset trigger condition is currently met, the target bill query time within the current bill query cycle can be determined more accurately and quickly based on the time when the historical bill is issued and the historical payment time when the target user pays for the historical bill, so as to send a target payment reminder to the target user based on the target bill query time when it is determined that the target bill exists. It is ensured that the target bill query time of the current bill query cycle must be after the target bill is issued, thereby effectively avoiding the situation where the target user needs to frequently perform manual account checks during the current bill query cycle, which causes poor user experience, simplifies user operations, and improves bill query efficiency, accuracy, and timeliness; further, by setting a payment connection for the target bill in the target payment reminder sent to the target user, it is convenient for the target user to directly trigger the execution of the payment task for the target bill according to the payment link in the target payment reminder, which connects the payment process in series, further simplifies user operations, and improves bill processing efficiency and user payment experience.

[0200] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described separately by functions divided into various modules. Of course, when implementing this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0201] Although the present specification provides method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps, and does not represent a unique execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. The first, second, etc. words are used to represent the name, and do not represent any particular order.

[0202] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0203] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer-readable storage media including storage devices.

[0204] Through the description of the above embodiments, it can be known that those skilled in the art can clearly understand that the present specification can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present specification can essentially be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in each embodiment of the present specification or some parts of the embodiments.

[0205] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. This specification can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0206] Although the present specification is described through embodiments, those skilled in the art will appreciate that there are many modifications and changes to the present specification without departing from the spirit of the present specification, and it is intended that the appended claims include these modifications and changes without departing from the spirit of the present specification.

Claims

1. A bill processing method, characterized in that: include: When it is determined that the preset trigger condition is currently met, historical reminder data of the target user in the current bill query cycle is obtained; wherein the historical reminder data includes the number of historical payment reminders sent to the target user in the historical bill query cycle, the sending time of the historical payment reminder, and the payment time when the target user paid the historical payment reminder; Determine a target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle; Based on the target bill query time, detecting whether a target bill exists; When it is determined that the target bill exists, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

2. The method according to claim 1, characterized in that: The determining of the target bill query time within the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle includes: Determine the time difference according to the sending time of the historical payment reminder and the payment time of the target user for the historical payment reminder; The target bill query time is determined according to the number of historical payment reminders sent to the target user during the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period.

3. The method according to claim 2, characterized in that The determining the target bill query time according to the number of historical payment reminders sent to the target user within the historical bill query period, the time difference, and the bill query time corresponding to the historical bill query period includes: If the number of historical payment reminders sent to the target user during the historical bill query period is not greater than a preset number threshold, determining the target bill query time according to the bill query time corresponding to the historical bill query period; When the number of historical payment reminders sent to the target user during the historical bill query period is greater than a preset number threshold, and the time difference is less than a preset difference threshold, determining the target bill query time according to the bill query time corresponding to the historical bill query period; When the number of historical payment reminders sent to the target user during the historical bill query cycle is greater than a preset number threshold and the time difference is not less than a preset difference threshold, the target bill query time is determined based on the bill query time corresponding to the historical bill query cycle and the time difference.

4. The method according to claim 3, characterized in that The bill query time corresponding to the historical bill query cycle is determined according to the number of payments made by the target user for the bills in different time periods of the preset historical payment cycle.

5. The method according to claim 4, characterized in that There are multiple target bill query times, and determining the target bill query time in the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle includes: Determine the first bill query time in the current bill query cycle according to the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle; Determine the time period in which the first bill query time is located within the current bill query cycle, and determine a target time interval corresponding to the time period in which the first bill query time is located according to a preset correspondence between the time period and the time interval; The target bill query time is determined according to the first bill query time and the target time interval.

6. The method according to claim 1, characterized in that The method further comprises: In the case where it is determined that the target bill does not exist, determining a second bill query time according to a preset delay interval and the target bill query time; Based on the second bill query time, it is detected whether a target bill exists.

7. The method according to claim 6, characterized in that Before determining the second bill query time according to the preset delay interval and the target bill query time, the method further includes: The time period in which the target bill query time is located within the current bill query cycle is determined, and the preset delay interval corresponding to the time period in which the target bill query time is located is determined according to a preset correspondence between the time period and the time interval.

8. The method according to claim 1, characterized in that The determining, based on the historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle, a target bill query time within the current bill query cycle includes: Determine the payment time difference of the target user for different types of bills according to the historical reminder data of the current bill query period of the target user, wherein the payment time difference is determined according to the sending time of the historical payment reminder and the payment time when the target user pays the historical payment reminder; The historical billing time of the different types of bills is obtained, and the target bill query time for the different types of bills in the current bill query cycle is determined based on the historical billing time and the payment time difference of the target user for the different types of bills.

9. The method according to claim 8, characterized in that The step of sending a target payment reminder to the target user when it is determined that the target bill exists includes: In the case where it is determined that the target bill exists, determining, according to the type of the target bill, a target reminder method corresponding to the type of the target bill in the preset reminder methods; According to the target reminder method, the target payment reminder is sent to the target user.

10. A bill processing method, characterized in that: The method comprises: When it is determined that the preset trigger condition is currently met, historical reminder data of the current bill query cycle of the target user is obtained; wherein the historical reminder data includes the billing time of the historical bill and the historical payment time when the target user paid the historical bill; Determine the target bill query time within the current bill query cycle according to the billing time of the historical bill; Determine the first time of the target user in the current bill query cycle according to the historical payment time; Based on the target bill query time and the first time, a target payment reminder is sent to the target user, the target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

11. The method according to claim 10, characterized in that The sending a target payment reminder to the target user based on the target bill query time and the first time includes: Based on the target bill query time, detecting whether the target user has paid the target bill; When non-payment is detected, the target payment reminder is sent to the target user based on the first time.

12. A bill processing device, characterized in that: include: A historical data determination module, configured to obtain historical reminder data of the current bill query cycle of the target user when it is determined that the preset trigger condition is currently met; wherein the historical reminder data includes the number of historical payment reminders sent to the target user during the historical bill query cycle, the sending time of the historical payment reminder, and the payment time when the target user paid the historical payment reminder; A bill query determination module, configured to determine a target bill query time within a current bill query cycle based on historical reminder data of the current bill query cycle of the target user and the bill query time corresponding to the historical bill query cycle; A target bill determination module, used to detect whether a target bill exists based on the target bill query time; The payment determination module is used to send a target payment reminder to the target user when it is determined that the target bill exists. The target payment reminder carries a payment link for the target bill, and the payment link is used to trigger the execution of a payment task for the target bill.

13. A server, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 11 when executing the instructions.

14. A computer-readable storage medium, characterized in that: Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

15. A computer program product, characterized in that The invention comprises a computer program, which implements the steps of the method according to any one of claims 1 to 11 when being executed by a processor.

Images