Payment reminder method and device

Abstract

The embodiments of this specification provide a payment reminder method and device, wherein a payment reminder method includes: obtaining payment data of a payment institution; based on the payment data, determining whether the payment institution has completed the current billing; if so, querying the payment users associated with the payment institution in the institution-user payment association relationship; determining the unpaid users among the payment users who have not paid for the current billing; and performing payment reminder processing on the unpaid users.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of August 28, 2020, application number CN202010887777.X, and name “Payment Reminder Method and Device”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a payment reminder method and device. Background Art

[0003] Resources such as water, electricity, and gas are essential resources in daily life and are resources that users must consume every month. The bills generated by the consumption of water, electricity, gas and other resources require users to pay within a specified time. However, in reality, users may often fail to pay on time due to various factors, which will result in the suspension of water, electricity, gas and other resources, causing great trouble to users' lives. Summary of the invention

[0004] One or more embodiments of the present specification provide a payment reminder method. The payment reminder method includes: obtaining payment data of a payment institution. Based on the payment data, determining whether the payment institution has completed the current billing; if so, querying the payment users associated with the payment institution in the payment association relationship between the institution and the user. Determining the unpaid users among the payment users who have not paid for the current billing. Performing payment reminder processing on the unpaid users.

[0005] One or more embodiments of the present specification provide a payment reminder device, including: a payment data acquisition module, configured to acquire payment data of a payment institution. A current billing judgment module, configured to judge whether the payment institution has completed the current billing based on the payment data; if so, run a payment user query module, an unpaid user determination module and a payment reminder processing module. The payment user query module is configured to query the payment users associated with the payment institution in the payment association relationship between the institution and the user. The unpaid user determination module is configured to determine the unpaid users among the payment users who have not paid for the current billing. The payment reminder processing module is configured to perform payment reminder processing on the unpaid users.

[0006] One or more embodiments of the present specification provide a data processing device, including: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: obtains payment data of a payment institution. Based on the payment data, determines whether the payment institution has completed the current billing; if so, queries the payment users associated with the payment institution in the payment association relationship between the institution and the user. Determine the unpaid users among the payment users who have not paid for the current billing. Perform payment reminder processing on the unpaid users.

[0007] One or more embodiments of the present specification provide a storage medium for storing computer executable instructions, which implement the following process when executed: Obtain payment data of a payment institution. Based on the payment data, determine whether the payment institution has completed the current billing; if so, query the payment users associated with the payment institution in the payment association relationship between the institution and the user. Determine the unpaid users among the payment users who have not paid for the current billing. Perform payment reminder processing on the unpaid users. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, 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 labor.

[0009] Figure 1 A processing flow chart of a payment reminder method provided for one or more embodiments of this specification;

[0010] Figure 2 A processing flow chart of a payment reminder method applied to a third-party platform scenario provided in one or more embodiments of this specification;

[0011] Figure 3 A schematic diagram of a payment reminder device provided for one or more embodiments of this specification;

[0012] Figure 4 A schematic diagram of the structure of a data processing device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

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

[0014] This specification provides a payment reminder method embodiment:

[0015] See also Figure 1The payment reminder method provided in this embodiment includes steps S102 to S110.

[0016] Step S102, obtaining payment data of the payment institution.

[0017] In actual applications, payment institutions for life services such as water, electricity, and gas will issue bills based on the user's actual monthly usage. Users need to pay the corresponding fees for the bills generated after the billing. However, in reality, the payment institutions providing life payment services in different cities or regions may be different. At the same time, for the same city or region, the payment institutions providing different types of life payment services are also different. As a result, the number of payment institutions is relatively large, which puts higher requirements on the third-party platforms that connect with the payment institutions.

[0018] The payment reminder method provided in this embodiment pre-establishes a payment association relationship between each payment institution and the paying users of the payment institution for payment institutions settled in the third-party platform. On this basis, starting from the payment data of the payment institution, when it is predicted that the payment institution has completed the current billing, all the paying users of the payment institution are queried in the pre-established payment association relationship, and the unpaid users who have not yet paid the fees for the current billing among all the paying users of the payment institution are further determined, so as to provide payment reminders to the unpaid users of the current billing of the payment institution in a targeted manner, thereby avoiding sending payment reminders to all paying users of the payment institution, which would disturb the reminders of the paid users who have already paid the fees, and improving the effectiveness and timeliness of payment reminders.

[0019] The payment institution described in this embodiment refers to an institution that provides payment services in the fields of water, electricity, gas, etc. Users who use the payment services provided by the payment institution to pay fees are the payment users of the payment institution. Specifically, each payment institution has its own payment service area. For example, payment institution A provides electricity payment services for electricity users in the area of ​​xx district in xx city. For another example, payment institution B provides gas payment services for gas users in xx community in xx district in xx city.

[0020] It should be noted that, in this embodiment, for multiple payment institutions that provide payment services of the same payment type, their respective payment service areas have geographical exclusivity, that is, the payment service areas of multiple payment institutions with the same payment type do not overlap with each other. For example, payment institution A and payment institution C are both institutions that provide electricity bill payment services, and their payment service areas cannot overlap at the geographical level. The payment service area of ​​payment institution A is the area of ​​xx district in xx city, and the payment service area of ​​payment institution C cannot be the area of ​​xx district in xx city. The reason for requiring the payment service areas of payment institutions with the same payment type to have geographical exclusivity is to avoid repeated reminders to users in the same area by multiple payment institutions that provide payment services in the same area.

[0021] The payment data refers to the relevant data generated during the payment process of the paying users of the payment institution, such as the payment order generated by the paying users through the payment service provided by the payment institution. The payment order records the paying user's user ID, payment amount, payment account period, name of the payment institution and other information.

[0022] Optionally, the payment institution is an institution settled in the third-party platform, the paying user is a platform user of the third-party platform, and the paying user performs payment processing based on the third-party platform, and the payment data of the payment institution is obtained through the third-party platform.

[0023] For any platform user of the third-party platform, if the platform user processes payment for at least one resident institution on the third-party platform, or the platform user signs a payment service agreement with at least one resident institution regarding payment processing, the platform user is the paying user of the resident institution; conversely, if the platform user does not process payment for any resident institution on the third-party platform and does not sign a payment service agreement with any resident institution, the platform user cannot be called a paying user.

[0024] Based on this, in order to avoid unnecessary reminder interference to the platform users of the third-party platform during the execution of the payment processing method provided in this embodiment on the third-party platform, historical payment users (platform users who have performed payment processing for at least one resident institution) and agreement payment users (platform users who have signed a payment service agreement with at least one resident institution regarding payment processing) can be screened out from the platform users of the third-party platform according to the user data of the platform users on the third-party platform as the payment users.

[0025] In specific implementation, when the number of payment institutions settled in the third-party platform is relatively large, if each payment institution is monitored in real time to monitor whether each payment institution has issued an account, the required resources or the amount of calculation generated will be relatively large. Considering the characteristic that the payment institution only issues an account once in each account period, in order to improve processing efficiency and avoid wasting computing resources, an optional implementation method provided in this embodiment adopts a batch scheduling method, and schedules the settled institutions in batches as the payment institutions that perform current account issuance judgments. Specifically, the historical payment data of the settled institutions is used to analyze the historical account issuance time of each settled institution, so as to predict the possible account issuance time or time period of each settled institution. On this basis, the settled institutions are divided into multiple batches according to the account issuance time, and the settled institutions in each batch are subjected to subsequent account issuance judgments and payment reminder processing in order from front to back according to the time sequence of the account issuance time of the settled institutions in each batch.

[0026] As described above, this embodiment requires that the payment service areas of payment institutions with the same payment type have geographical exclusivity. In practice, if the payment service area is inaccurately determined, resulting in possible overlap of payment service areas, the payment service scope of the payment institution can be deduplicated to avoid repeated reminders to users in the same area by multiple payment institutions providing payment services in the same area.

[0027] Step S104, based on the payment data, determining whether the payment institution has completed the current payment.

[0028] The current billing in this embodiment refers to the billing operation corresponding to the billing time interval to which the current time point belongs, or the billing operation for the unpaid fees in the time interval before the current time point. Taking the payment institution A that provides electricity bill payment services as an example, the billing cycle of payment institution A is 1 month, and the current time point is February. The billing of payment institution A in February is the electricity fee of the electricity user in January. The bill after the billing is the electricity bill generated by the electricity user's electricity consumption behavior in January.

[0029] In order to improve the accuracy of the billing judgment of the payment institution, in an optional implementation manner provided in this embodiment, the payment data is input into a billing judgment model to perform current billing judgment, and the historical billing time, payment time distribution, and payment proportion determined based on the payment data are used as model inputs. The billing judgment model performs current billing judgment based on the historical billing time, payment time distribution, payment proportion, and respective corresponding weight factors. Specifically, the process of performing current billing judgment based on the billing judgment model is implemented as follows:

[0030] Determine the historical payment time of the payment institution based on the payment time recorded in the historical payment order contained in the payment data;

[0031] Determine the payment time distribution of historical payment users of the payment institution based on the payment time recorded in the historical payment orders contained in the payment data;

[0032] Calculate the payment proportion of the current billing of the payment institution based on the number of current payment orders generated for the current billing in the payment data and the total number of paying users associated with the payment institution; wherein the payment proportion is equal to the ratio of the number of orders to the total number of users;

[0033] The historical billing time, the payment time distribution and / or the payment ratio are used as inputs, and the billing judgment model is input to judge whether the payment institution has completed the current billing.

[0034] Optionally, in the process of making current billing judgments by the billing judgment model, current billing judgments are made based on the historical billing time, the payment time distribution and / or the payment ratio and their respective corresponding weight factors; wherein the weight factors are determined based on the payment data of the payment institution.

[0035] For example, in the process of making a current billing judgment on payment institution A, first, the historical payment bills of all paying users of payment institution A in the past six months are obtained. On the one hand, the historical payment bills of each month are analyzed to obtain the billing time of payment institution A in each month; on the other hand, the payment time of all paying users of payment institution A each month is counted to determine the payment time distribution of payment institution A each month; thirdly, the ratio of the number of orders for current payment to the total number of paying users of payment institution A is calculated as the current payment proportion, and the billing time of each month in half a year, the payment time distribution of each month and the current payment proportion of payment institution A are used as input, and the billing judgment model makes the current billing judgment based on the input and combined with the weight factor.

[0036] Furthermore, in order to further improve the accuracy of billing judgment, different weight factors can be set for different payment institutions, that is, the weight factors of the billing judgment model correspond to the payment institutions one by one, and the weight factors can be determined according to the historical payment data of each payment institution. For example, for payment institutions with relatively regular historical billing time (the billing time is concentrated in a short period of time), the weight factors corresponding to the historical billing time can be appropriately increased in the process of billing judgment; for payment institutions with relatively concentrated payment time distribution, the weight factors corresponding to the payment time distribution can be appropriately increased in the process of billing judgment. In the specific implementation process, the historical billing time, payment time distribution, payment proportion and the corresponding weight factors of the three can be used as model inputs at the same time, and the billing judgment model can make the current billing judgment; or after the historical billing time, payment time distribution and payment proportion are input into the billing judgment model, the billing judgment model first determines the weight factor of the payment institution according to the input, and then makes the current billing judgment based on the determined weight factor combined with the historical billing time, payment time distribution and payment proportion.

[0037] In specific implementation, based on the payment data, it is determined whether the payment institution has completed the current payment;

[0038] If yes, it indicates that the payment institution's current payment has been completed, and the following step S106 is executed to query the payment user associated with the payment institution in the payment association relationship between the institution and the user;

[0039] If not, it indicates that the payment institution has not yet made the current payment, and then the process returns to execute the above-mentioned process of scheduling the institutions stationed in the third-party platform in batches, that is, executing the above-mentioned step of scheduling the institutions stationed in batches as the payment institutions for making current payment judgments based on the historical payment data of the institutions stationed.

[0040] Step S106, querying the payment user associated with the payment institution in the payment association relationship between the institution and the user.

[0041] The payment association relationship between the institution and the user described in this embodiment is used to record the payment institution, the paying user of the payment relationship, and the payment association relationship between the two parties; this payment association relationship is also reflected in that the geographical location of the paying user is within the payment service area of ​​the payment institution.

[0042] In order to improve the query efficiency in the process of querying the payment user associated with the payment institution in the payment association relationship between the institution and the user, in an optional implementation mode provided in this embodiment, before processing the payment reminder, an institution-user payment association relationship corresponding to the payment institution is established one by one. Specifically, the institution-user payment association relationship is established in the following manner:

[0043] Obtain the payment service area of ​​the payment institution and the location information of the paying users in the payment user set;

[0044] Determine the paying users in the paying user set whose geographical locations corresponding to their location information are in the paying service area;

[0045] An association relationship between a payment institution and a payment user whose geographical location is within the payment service area is established as a payment association relationship between the payment institution and the user.

[0046] For example, first obtain the payment service area from payment institution A, which is the area of ​​xx district in xx city, and obtain the location information of all paying users who have made payment behaviors from the third-party platform, and then determine the paying users whose location information is in the area of ​​xx district in xx city, and establish an association relationship between the determined paying users and payment institution A, thereby generating an institution-user payment association relationship of payment institution A.

[0047] Here, the purpose of querying paying users from the payment association relationship between the institution and the user is to prepare for the subsequent sending of payment reminders to the paying users. Therefore, in order to reduce the probability of payment reminders disturbing paying users, in the process of establishing the payment association relationship between the institution and the user, the payment service area, payment dimension, and location information and historical payment types of the paying users in the paying user set of the payment institution can also be obtained; then, the paying users whose historical payment types match the payment dimensions of the payment institution are screened out from the paying user set; secondly, the paying users whose geographical locations corresponding to their location information are in the payment service area are determined among the screened paying users; finally, an association relationship between the payment institution and the paying users whose geographical locations are in the payment service area is established as the institution-user payment association relationship corresponding to the payment institution.

[0048] In order to further improve the payment association relationship between the institution and the user, the payment association relationship between the institution and the user can also be updated according to the payment order of the paying user. In an optional implementation provided by this embodiment, the payment order generated by the platform user of the third-party platform for payment of the payment institution's billing is first obtained; then an association relationship is established between the platform user corresponding to the generated payment order and the payment institution recorded in the generated payment order, and the payment association relationship between the institution and the user is updated based on the established association relationship.

[0049] In specific implementation, based on the pre-established payment association relationship between an institution and a user, the payment user associated with the payment institution is queried in the payment association relationship between an institution and a user. In the case where the payment institution corresponds to the payment association relationship between an institution and a user one to one, all the payment users recorded in the payment association relationship between an institution and a user corresponding to the payment institution are payment users associated with the payment user.

[0050] Step S108, determining the unpaid users among the paying users who have not paid for the current billing period.

[0051] In order to improve the accuracy of determining the non-paying users among the paying users associated with the payment institution, and thus improve the effectiveness of the subsequent payment reminder processing for the non-paying users, in an optional implementation manner provided in this embodiment, the non-paying users who have not paid for the current billing are determined in the following manner:

[0052] Detecting a payment order of the paying user within the billing time interval to which the current billing belongs;

[0053] If it is detected that the payment order of the paying user within the billing time interval is empty, the paying user is determined as the non-paying user;

[0054] If it is detected that the payment order of the paying user within the billing time interval is not empty, determine whether the detected payment order is a current payment order for the current billing; if so, it indicates that the paying user has already made payment for the current billing of the payment institution, and no processing is required; if not, it indicates that the paying user has not yet made payment for the current billing of the payment institution, and the paying user is reminded to pay.

[0055] Continuing with the above example, the current billing of payment institution A is to issue bills for the electricity bill generated in January within the billing time range of February. For the paying user User1 of payment institution A, it is checked whether the paying user User1 has a payment order in February; if there is a payment order, it is further determined whether the payment order of the paying user User1 in February is a payment order for the electricity bill of payment institution A in January. If not, the paying user User1 is determined as an unpaid user of payment institution A.

[0056] Step S110, reminding the user who has not paid the fee to pay.

[0057] After the unpaid users of the payment institution are determined as above, in order to remind the unpaid users to pay the current bills of the payment institution, a payment notification message of the current bills of the payment institution can be sent to the unpaid users, so that the unpaid users can be mechanically reminded to pay.

[0058] In addition, if the payment institution is an institution that joins the third-party platform, and the unpaid user is a platform user of the third-party platform, the payment reminder of the current bill of the payment institution can be pushed to the unpaid user through the third-party platform. On this basis, in order to achieve more humane reminders, and also to reduce the reminder disturbances for those platform users who do not want to receive payment reminders or are mistakenly reminded, so as to improve the user experience of payment reminders, and then improve the user experience of the third-party platform, in an optional implementation provided by this embodiment, by configuring a reminder rejection control in the payment reminder, when it is detected that the reminder rejection control is triggered, the unpaid user associated with the payment institution and triggering the reminder rejection control in the payment association relationship between the institution and the user is deleted.

[0059] The following takes the application of a payment reminder method provided by this embodiment in a third-party platform scenario as an example to further illustrate the payment reminder method provided by this embodiment. Figure 2 , a payment reminder method applied to a third-party platform scenario, specifically includes steps S202 to S220.

[0060] Step S202: Schedule the payment institutions that have settled in the third-party platform in batches.

[0061] Step S204, obtaining payment data of multiple payment institutions corresponding to this scheduling task from a third-party platform.

[0062] Step S206, based on the payment data, determine the historical payment time, payment time distribution and current payment ratio of each payment institution.

[0063] Step S208, using the historical payment time, payment time distribution and current payment ratio as input, inputting the payment judgment model to judge whether each payment institution has completed the current payment;

[0064] If yes, execute step S210;

[0065] If not, return to step S202;

[0066] Step S210, querying the payment users associated with each payment institution in the payment association relationship between each payment institution and the user.

[0067] Step S212, checking whether the payment order of the queried payer within the billing time interval to which the current billing belongs is empty;

[0068] If it is detected that the payment order of the queried payer within the billing time interval is empty, step S214, step S218 and step S220 are executed;

[0069] If it is detected that the payment order within the queried payment time interval of the paying user is not empty, step S216 is executed.

[0070] Step S214: Determine the paying user whose payment order is empty as a non-paying user.

[0071] Step S216, determining whether the detected payment order is a current payment order for payment of the current billing;

[0072] If so, no action is required;

[0073] If not, the paying users whose payment orders are not empty are determined as non-paying users, and steps S218 and S220 are executed.

[0074] Step S218, push the payment reminder of the current billing period of the payment institution to the unpaid user through the third-party platform.

[0075] Step S220, when it is detected that the reminder rejection control configured in the payment reminder is triggered, delete the unpaid users who are associated with the payment institution and have triggered the reminder rejection control in the institution-user payment association relationship.

[0076] To sum up, the payment reminder method provided in this embodiment starts from the payment data of the payment institution. When it is determined that the payment institution has completed the current billing, the payment users associated with the payment institution are queried in the payment association relationship, and the unpaid users among the payment users associated with the payment institution who have not yet paid the fees for the current billing are further determined, thereby providing payment reminders to the unpaid users of the current billing of the payment institution in a targeted manner, avoiding the sending of payment reminders to all paying users of the payment institution, which would disturb the paid users who have already paid the fees, and improving the effectiveness and timeliness of payment reminders.

[0077] An embodiment of a payment reminder device provided in this specification is as follows:

[0078] In the above-mentioned embodiment, a payment reminder method is provided, and correspondingly, a payment reminder device is also provided, which is described below in conjunction with the accompanying drawings.

[0079] Reference Figure 3 , which shows a schematic diagram of a payment reminder device provided in this embodiment.

[0080] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0081] This embodiment provides a payment reminder device, including:

[0082] The payment data acquisition module 302 is configured to acquire payment data of a payment institution;

[0083] The current payment judgment module 304 is configured to judge whether the payment institution has completed the current payment based on the payment data;

[0084] If yes, run the payment user query module 306, the non-payment user determination module 308 and the payment reminder processing module 310;

[0085] The payment user query module 306 is configured to query the payment user associated with the payment institution in the payment association relationship between the institution and the user;

[0086] The non-paying user determination module 308 is configured to determine the non-paying users among the paying users who have not paid for the current billing period;

[0087] The payment reminder processing module 310 is configured to perform payment reminder processing on the overdue user.

[0088] Optionally, the current payment determination module 304 is specifically configured as follows:

[0089] Determine the historical payment time of the payment institution based on the payment time recorded in the historical payment order contained in the payment data;

[0090] Determine the payment time distribution of historical payment users of the payment institution based on the payment time recorded in the historical payment orders contained in the payment data;

[0091] Calculate the payment proportion of the current billing of the payment institution based on the number of current payment orders generated for the current billing in the payment data and the total number of paying users associated with the payment institution;

[0092] The historical billing time, the payment time distribution and / or the payment ratio are used as inputs, and the billing judgment model is input to judge whether the payment institution has completed the current billing.

[0093] Optionally, the payment association relationship between the institution and the user corresponds to the payment institution one by one, and the payment association relationship between the institution and the user is established by running the following modules:

[0094] The area acquisition module is configured to acquire the payment service area of ​​the payment institution and the location information of the payment users in the payment user set;

[0095] A paying user determining module, configured to determine paying users in the paying user set whose geographical locations corresponding to their location information are in the paying service area;

[0096] The association relationship establishment module is configured to establish an association relationship between a payment institution and a payment user whose geographical location is in the payment service area, as a payment association relationship between the payment institution and the user.

[0097] Optionally, the non-paying user determination module 308 is specifically configured to detect the payment order of the paying user within the billing time interval to which the current billing belongs; if it is detected that the payment order of the paying user within the billing time interval is empty, the paying user is determined as the non-paying user.

[0098] Optionally, if the unpaid user determination module 308 detects that the payment order of the paying user within the billing time interval is not empty, it determines whether the detected payment order is a current payment order for the current billing; if not, a payment reminder is performed on the paying user.

[0099] Optionally, the payment institution is an institution settled in the third-party platform, the paying user is a platform user of the third-party platform, and the paying user performs payment processing based on the third-party platform, and the payment data of the payment institution is obtained through the third-party platform.

[0100] Optionally, the payment reminder processing module 310 is specifically configured to:

[0101] Pushing payment reminders of the current billing period of the payment institution to the unpaid user through the third-party platform;

[0102] and / or,

[0103] A payment notification message of the current billing period of the payment institution is sent to the unpaid user.

[0104] Optionally, the payment reminder is configured with a reminder rejection control; accordingly, the payment reminder device further includes:

[0105] The overdue user deletion module is configured to delete the overdue user who is associated with the payment institution and triggers the reminder rejection control in the institution-user payment association relationship when it is detected that the reminder rejection control is triggered.

[0106] Optionally, the payment reminder device further includes:

[0107] A payment order acquisition module is configured to acquire a payment order generated by a platform user of the third-party platform for payment of an outgoing payment from a payment institution;

[0108] The association updating module is configured to establish an association between the platform user corresponding to the generated payment order and the payment institution recorded in the generated payment order, and update the payment association between the institution and the user based on the established association.

[0109] Optionally, the payment reminder device further includes:

[0110] The batch scheduling module is configured to schedule the resident institutions in batches as the payment institutions for current billing judgment based on the historical payment data of the resident institutions.

[0111] Optionally, if the judgment result output by the current payment judgment module 304 after running is negative, the batch scheduling module is run.

[0112] Optionally, in the process of making current billing judgments by the billing judgment model, current billing judgments are made based on the historical billing time, the payment time distribution and / or the payment ratio and their respective corresponding weight factors; wherein the weight factors are determined based on the payment data of the payment institution.

[0113] An embodiment of a payment reminder device provided in this specification is as follows:

[0114] Corresponding to the payment reminder method described above, based on the same technical concept, one or more embodiments of this specification also provide a payment reminder device, which is used to execute the payment reminder method provided above. Figure 4 A schematic diagram of the structure of a payment reminder device provided in one or more embodiments of this specification.

[0115] A payment reminder device provided in this embodiment includes:

[0116] like Figure 4As shown, the payment reminder device may have relatively large differences due to different configurations or performances, and may include one or more processors 401 and memory 402, and the memory 402 may store one or more storage applications or data. Among them, the memory 402 may be a temporary storage or a permanent storage. The application stored in the memory 402 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the payment reminder device. Furthermore, the processor 401 may be configured to communicate with the memory 402 to execute a series of computer executable instructions in the memory 402 on the payment reminder device. The payment reminder device may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input and output interfaces 405, one or more keyboards 406, etc.

[0117] In a specific embodiment, the payment reminder device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for the payment reminder device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following:

[0118] Obtain payment data from payment institutions;

[0119] Based on the payment data, determining whether the payment institution has completed the current payment;

[0120] If yes, query the payment user associated with the payment institution in the payment association relationship between the institution and the user;

[0121] Determining unpaid users among the paying users who have not paid for the current billing period;

[0122] The unpaid users are reminded to pay.

[0123] Optionally, judging whether the payment institution has completed the current payment based on the payment data includes:

[0124] Determine the historical payment time of the payment institution based on the payment time recorded in the historical payment order contained in the payment data;

[0125] Determine the payment time distribution of historical payment users of the payment institution based on the payment time recorded in the historical payment orders contained in the payment data;

[0126] Calculate the payment proportion of the current billing of the payment institution based on the number of current payment orders generated for the current billing in the payment data and the total number of paying users associated with the payment institution;

[0127] The historical billing time, the payment time distribution and / or the payment ratio are used as inputs, and the billing judgment model is input to judge whether the payment institution has completed the current billing.

[0128] Optionally, the payment association relationship between the institution and the user corresponds to the payment institution one by one, and the payment association relationship between the institution and the user is established in the following manner:

[0129] Obtain the payment service area of ​​the payment institution and the location information of the paying users in the payment user set;

[0130] Determine the paying users in the paying user set whose geographical locations corresponding to their location information are in the paying service area;

[0131] An association relationship between a payment institution and a payment user whose geographical location is within the payment service area is established as a payment association relationship between the payment institution and the user.

[0132] Optionally, the determining of the unpaid users among the paying users who have not paid for the current billing includes:

[0133] Detecting a payment order of the paying user within the billing time interval to which the current billing belongs;

[0134] If it is detected that the payment order of the paying user within the billing time interval is empty, the paying user is determined as the non-paying user.

[0135] Optionally, if it is detected that the payment order of the paying user within the billing time interval is not empty, determining whether the detected payment order is a current payment order for payment of the current billing;

[0136] If not, a payment reminder is provided to the paying user.

[0137] Optionally, the payment institution is an institution settled in the third-party platform, the paying user is a platform user of the third-party platform, and the paying user performs payment processing based on the third-party platform, and the payment data of the payment institution is obtained through the third-party platform.

[0138] Optionally, the step of reminding the non-paying user to pay includes:

[0139] Pushing payment reminders of the current billing period of the payment institution to the unpaid user through the third-party platform;

[0140] and / or,

[0141] A payment notification message of the current billing period of the payment institution is sent to the unpaid user.

[0142] Optionally, the payment reminder is configured with a reminder rejection control;

[0143] In the case where it is detected that the reminder rejection control is triggered, the unpaid users who are associated with the payment institution and have triggered the reminder rejection control are deleted from the payment association relationship between the institution and the user.

[0144] Optionally, the process of executing the computer executable instructions further includes:

[0145] Obtaining a payment order generated by a platform user of the third-party platform for payment of an outgoing payment from a payment institution;

[0146] Establish an association relationship between the platform user corresponding to the generated payment order and the payment institution recorded in the generated payment order, and update the payment association relationship between the institution and the user based on the established association relationship.

[0147] Optionally, the process of executing the computer executable instructions further includes:

[0148] Based on the historical payment data of the resident institutions, the resident institutions are dispatched in batches as the payment institutions for current billing judgment.

[0149] Optionally, if the judgment result after judging whether the payment institution has completed the execution of the current billing instruction based on the historical payment data is no, the historical payment data based on the resident institutions is executed, and the resident institutions are scheduled in batches as the payment institution instructions for making current billing judgments.

[0150] Optionally, in the process of making current billing judgments by the billing judgment model, current billing judgments are made based on the historical billing time, the payment time distribution and / or the payment ratio and their respective corresponding weight factors; wherein the weight factors are determined based on the payment data of the payment institution.

[0151] An embodiment of a storage medium provided in this specification is as follows:

[0152] Corresponding to the payment reminder method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0153] The storage medium provided in this embodiment is used to store computer executable instructions, and the computer executable instructions implement the following process when executed:

[0154] Obtain payment data from payment institutions;

[0155] Based on the payment data, determining whether the payment institution has completed the current payment;

[0156] If yes, query the payment user associated with the payment institution in the payment association relationship between the institution and the user;

[0157] Determining unpaid users among the paying users who have not paid for the current billing period;

[0158] The unpaid users are reminded to pay.

[0159] Optionally, judging whether the payment institution has completed the current payment based on the payment data includes:

[0160] Determine the historical payment time of the payment institution based on the payment time recorded in the historical payment order contained in the payment data;

[0161] Determine the payment time distribution of historical payment users of the payment institution based on the payment time recorded in the historical payment orders contained in the payment data;

[0162] Calculate the payment proportion of the current billing of the payment institution based on the number of current payment orders generated for the current billing in the payment data and the total number of paying users associated with the payment institution;

[0163] The historical billing time, the payment time distribution and / or the payment ratio are used as inputs, and the billing judgment model is input to judge whether the payment institution has completed the current billing.

[0164] Optionally, the payment association relationship between the institution and the user corresponds to the payment institution one by one, and the payment association relationship between the institution and the user is established in the following manner:

[0165] Obtain the payment service area of ​​the payment institution and the location information of the paying users in the payment user set;

[0166] Determine the paying users in the paying user set whose geographical locations corresponding to their location information are in the paying service area;

[0167] An association relationship between a payment institution and a payment user whose geographical location is within the payment service area is established as a payment association relationship between the payment institution and the user.

[0168] Optionally, the determining of the unpaid users among the paying users who have not paid for the current billing includes:

[0169] Detecting a payment order of the paying user within the billing time interval to which the current billing belongs;

[0170] If it is detected that the payment order of the paying user within the billing time interval is empty, the paying user is determined as the non-paying user.

[0171] Optionally, if it is detected that the payment order of the paying user within the billing time interval is not empty, determining whether the detected payment order is a current payment order for payment of the current billing;

[0172] If not, a payment reminder is provided to the paying user.

[0173] Optionally, the payment institution is an institution settled in the third-party platform, the paying user is a platform user of the third-party platform, and the paying user performs payment processing based on the third-party platform, and the payment data of the payment institution is obtained through the third-party platform.

[0174] Optionally, the step of reminding the non-paying user to pay includes:

[0175] Pushing payment reminders of the current billing period of the payment institution to the unpaid user through the third-party platform;

[0176] and / or,

[0177] A payment notification message of the current billing period of the payment institution is sent to the unpaid user.

[0178] Optionally, the payment reminder is configured with a reminder rejection control;

[0179] In the case where it is detected that the reminder rejection control is triggered, the unpaid users who are associated with the payment institution and have triggered the reminder rejection control are deleted from the payment association relationship between the institution and the user.

[0180] Optionally, the computer executable instructions further implement the following process when executed:

[0181] Obtaining a payment order generated by a platform user of the third-party platform for payment of an outgoing payment from a payment institution;

[0182] Establish an association relationship between the platform user corresponding to the generated payment order and the payment institution recorded in the generated payment order, and update the payment association relationship between the institution and the user based on the established association relationship.

[0183] Optionally, before the process of obtaining payment data of a payment institution is executed, the computer executable instructions further implement the following process when executed:

[0184] Based on the historical payment data of the resident institutions, the resident institutions are dispatched in batches as the payment institutions for current billing judgment.

[0185] Optionally, if the judgment result after judging whether the payment institution has completed the current billing process based on the historical payment data is no, the process based on the historical payment data of the resident institutions is executed, and the resident institutions are scheduled in batches as the payment institution process for current billing judgment.

[0186] Optionally, in the process of making current billing judgments by the billing judgment model, current billing judgments are made based on the historical billing time, the payment time distribution and / or the payment ratio and their respective corresponding weight factors; wherein the weight factors are determined based on the payment data of the payment institution.

[0187] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the payment reminder method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0188] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0189] In the 1930s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0190] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0191] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0192] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0193] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0194] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0195] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0196] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0197] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0198] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0199] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0200] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0201] One or more embodiments of the present 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, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present 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 storage media, including storage devices.

[0202] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0203] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A payment reminder method, comprising: Based on the payment data of the payment institutions settled in the third-party platform, if it is predicted that the payment institutions have completed the current billing, the payment users associated with the payment institutions are queried in the pre-established payment association relationship; whether the current billing is completed is predicted based on the historical billing time determined based on the payment data, the payment time distribution of the historical payment users and the current payment ratio, and the payment service areas of multiple payment institutions with the same payment type do not overlap with each other; Determining unpaid users among the paying users who have not paid for the current billing period; The unpaid users are reminded to pay.

2. According to the payment reminder method of claim 1, whether the current payment is completed is predicted in the following way: Determine the historical payment time of the payment institution based on the payment time recorded in the historical payment order contained in the payment data; Determine the payment time distribution of historical payment users of the payment institution based on the payment time recorded in the historical payment orders contained in the payment data; Calculate the payment proportion of the current billing of the payment institution based on the number of current payment orders generated for the current billing in the payment data and the total number of paying users associated with the payment institution; The historical payment time, the payment time distribution of the historical paying users and the payment proportion are used as input, and the payment judgment model is input to judge whether the payment institution has completed the current payment.

3. According to the payment reminder method of claim 1, the payment association relationship corresponds to the payment institution one by one, and the payment association relationship is established in the following manner: Obtain the payment service area of ​​the payment institution and the location information of the paying users in the payment user set; Determine the paying users in the paying user set whose geographical locations corresponding to their location information are in the paying service area; An association relationship between a payment institution and payment users whose geographical locations are within the payment service area is established as the payment association relationship corresponding to the payment institution.

4. The payment reminder method according to claim 1, wherein the determining of the unpaid users among the paying users who have not paid for the current billing period comprises: Detecting a payment order of the paying user within the billing time interval to which the current billing belongs; If it is detected that the payment order of the paying user within the billing time interval is empty, the paying user is determined as the non-paying user.

5. The payment reminder method according to claim 4, if it is detected that the payment order of the paying user in the billing time interval is not empty, determining whether the detected payment order is a current payment order for the current billing; If not, a payment reminder is provided to the paying user.

6. According to the payment reminder method according to claim 1, the payment institution is an institution settled in the third-party platform, the paying user is a platform user of the third-party platform, and the paying user performs payment processing based on the third-party platform, and the payment data of the payment institution is obtained through the third-party platform.

7. The payment reminder method according to claim 6, wherein the step of performing payment reminder processing on the non-paying user comprises: Pushing payment reminders of the current billing period of the payment institution to the unpaid user through the third-party platform; and / or, A payment notification message of the current billing period of the payment institution is sent to the unpaid user.

8. The payment reminder method according to claim 7, wherein the payment reminder is configured with a reminder rejection control; In the case where it is detected that the reminder rejection control is triggered, the unpaid user who is associated with the payment institution and has triggered the reminder rejection control in the payment association relationship is deleted.

9. The payment reminder method according to claim 6, further comprising: Obtaining a payment order generated by a platform user of the third-party platform for payment of an outgoing payment from a payment institution; An association relationship is established between the platform user corresponding to the generated payment order and the payment institution recorded in the generated payment order, and the payment association relationship is updated based on the established association relationship.

10. The payment reminder method according to claim 6, further comprising: Based on the historical payment data of the resident institutions, the resident institutions are dispatched in batches as the payment institutions for current billing judgment.

11. The payment reminder method according to claim 10, if it is predicted that the payment institution has not completed the current billing, the step of scheduling the resident institutions in batches as the payment institutions for current billing judgment based on the historical payment data of the resident institutions is executed.

12. The payment reminder method according to claim 2, wherein the payment judgment model performs the current payment judgment based on the historical payment time, the payment time distribution of the historical payment users, the payment proportion and the corresponding weight factors; in, The weight factor is determined according to the payment data of the payment institution.

13. A payment reminder method, comprising: Based on the payment data of the payment institutions settled in the third-party platform, determine the historical payment time of the payment institutions, the payment time distribution of historical payment users and the current payment ratio, and predict whether the payment institutions have completed the current payment; If yes, query the payment user associated with the payment institution in the pre-established payment association relationship; If it is detected that the payment order of the paying user within the billing time interval to which the current billing belongs is not empty, determining whether the payment order is a current payment order for paying the current billing; If so, no processing is required; if not, the paying user whose payment order is not empty is determined as an unpaid user, and a payment reminder of the current billing of the payment institution is pushed to the unpaid user through the third-party platform.

14. A payment reminder method, comprising: The payment institutions settled in the third-party platform are dispatched in batches; Based on the payment data of multiple payment institutions corresponding to this scheduling task obtained from the third-party platform, determine the historical billing time of each payment institution, the payment time distribution of historical payment users and the current payment ratio; Predicting whether the payment institution has completed the current payment based on the historical payment time, the payment time distribution of historical payment users and the current payment ratio; If not, return to execute the step of scheduling the payment institutions settled in the third-party platform in batches; if yes, query the payment users associated with each payment institution in the pre-established payment association relationship, and if it is not detected that the payment order of the queried payment user is empty within the billing time interval, the payment user with an empty payment order is determined as an unpaid user, and the payment reminder of the current billing of the payment institution is pushed to the unpaid user through the third-party platform; If it is detected that the payment order within the queried billing time interval of the paying user is not empty, and the detected payment order is not a current payment order for the current billing, the paying user whose payment order is not empty will be determined as a non-paying user, and the payment reminder of the current billing of the payment institution will be pushed to the non-paying user through the third-party platform.

15. A payment reminder device, comprising: The current billing prediction module is configured to run the payment user query module, the unpaid user determination module and the payment reminder processing module based on the payment data of the payment institution settled in the third-party platform, if it is predicted that the payment institution has completed the current billing; whether the current billing is completed is predicted based on the historical billing time determined based on the payment data, the payment time distribution of the historical payment users and the current payment ratio, and the payment service areas of multiple payment institutions with the same payment type do not overlap with each other; The payment user query module is configured to query the payment users associated with the payment institution in the pre-established payment association relationship; The non-paying user determination module is configured to determine the non-paying users among the paying users who have not paid for the current billing; The payment reminder processing module is configured to perform payment reminder processing on the overdue user.

16. A data processing device comprising: processor; as well as, a memory configured to store computer executable instructions which, when executed, cause the processor to: Based on the payment data of the payment institutions settled in the third-party platform, if it is predicted that the payment institutions have completed the current billing, the payment users associated with the payment institutions are queried in the pre-established payment association relationship; whether the current billing is completed is predicted based on the historical billing time determined based on the payment data, the payment time distribution of the historical payment users and the current payment ratio, and the payment service areas of multiple payment institutions with the same payment type do not overlap with each other; Determining unpaid users among the paying users who have not paid for the current billing period; The unpaid users are reminded to pay.

17. A storage medium for storing computer executable instructions, wherein the computer executable instructions implement the following process when executed: Based on the payment data of the payment institutions settled in the third-party platform, if it is predicted that the payment institutions have completed the current billing, the payment users associated with the payment institutions are queried in the pre-established payment association relationship; whether the current billing is completed is predicted based on the historical billing time determined based on the payment data, the payment time distribution of the historical payment users and the current payment ratio, and the payment service areas of multiple payment institutions with the same payment type do not overlap with each other; Determining unpaid users among the paying users who have not paid for the current billing period; The unpaid users are reminded to pay.

Images