CN111968302B - Payment reminding method and device - Google Patents
Payment reminding method and device Download PDFInfo
- Publication number
- CN111968302B CN111968302B CN202010887777.XA CN202010887777A CN111968302B CN 111968302 B CN111968302 B CN 111968302B CN 202010887777 A CN202010887777 A CN 202010887777A CN 111968302 B CN111968302 B CN 111968302B
- Authority
- CN
- China
- Prior art keywords
- payment
- user
- charge
- current
- users
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/10—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity with alarm or warning devices, e.g. indicating the interrupting of the supply
Abstract
The embodiment of the specification provides a payment reminding method and a payment reminding device, wherein the payment reminding method comprises the following steps: acquiring payment data of a payment mechanism; judging whether the payment mechanism finishes current charge based on the payment data; if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment; determining non-payment users who do not pay for the current charge-off among the payment users; and carrying out payment reminding processing on the unpaid users.
Description
Technical Field
The document relates to the technical field of data processing, in particular to a payment reminding method and device.
Background
Resources such as water, electricity and gas are essential resources for daily life, and are resource consumption which must be generated by a user every month, and bills generated by the resource consumption of the water, the electricity and the gas need to be paid by the user within a set time, but in practice, the user often can stop supplying the resources such as the water, the electricity and the gas because the resources are not paid as expected due to various factors, and great troubles are brought to the life of the user.
Disclosure of Invention
One or more embodiments of the present specification provide a payment reminding method. The payment reminding method comprises the following steps: and acquiring payment data of a payment mechanism. Judging whether the payment mechanism finishes current charge based on the payment data; if yes, inquiring the payment user related to the payment mechanism in the association relationship between the mechanism and the user payment. And determining the non-payment users who do not pay for the current charge. And carrying out payment reminding processing on the unpaid users.
One or more embodiments of the present specification provide a payment reminding apparatus, including: the payment data acquisition module is configured to acquire payment data of a payment mechanism. The current charge-off judging module is configured to judge whether the charging mechanism finishes current charge-off or not based on the charging data; if yes, operating a payment user query module, a non-payment user determination module and a payment reminding processing module. The payment user inquiry module is configured to inquire payment users related to the payment mechanism in the association relationship between the mechanism and the user payment. The non-payment user determination module is configured to determine non-payment users who do not pay for the current payment in the payment users. The payment reminding processing module is configured to carry out payment reminding processing on the unpaid user.
One or more embodiments of the present specification provide a data processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and acquiring payment data of a payment mechanism. Judging whether the payment mechanism finishes current charge based on the payment data; if yes, inquiring the payment user related to the payment mechanism in the association relationship between the mechanism and the user payment. And determining the non-payment users who do not pay for the current charge. And carrying out payment reminding processing on the unpaid users.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: and acquiring payment data of a payment mechanism. Judging whether the payment mechanism finishes current charge based on the payment data; if yes, inquiring the payment user related to the payment mechanism in the association relationship between the mechanism and the user payment. And determining the non-payment users who do not pay for the current charge. And carrying out payment reminding processing on the unpaid users.
Drawings
In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.
Fig. 1 is a processing flow chart of a payment reminding method according to one or more embodiments of the present disclosure;
fig. 2 is a processing flow diagram of a payment reminding method applied to a third-party platform scenario according to one or more embodiments of the present specification;
fig. 3 is a schematic view of a payment reminding apparatus according to one or more embodiments of the present disclosure;
fig. 4 is a schematic structural diagram of a data processing apparatus according to one or more embodiments of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
The embodiment of the payment reminding method provided by the specification comprises the following steps:
referring to fig. 1, the payment reminding method provided in this embodiment includes steps S102 to S110.
Step S102, acquiring payment data of a payment mechanism.
In practical application, payment mechanisms of living services such as water, electricity, gas and the like can be paid out according to the actual monthly usage of a user, the user needs to pay corresponding fees for bills generated after the payment is made, however, in practice, payment mechanisms for providing living payment services for different cities or different areas are possibly different, and meanwhile, payment mechanisms for providing different types of living payment services for the same city or area are also different, so that the number of the payment mechanisms is huge, and higher requirements are provided for a third-party platform connected with the payment mechanisms.
According to the payment reminding method provided by the embodiment, for the payment mechanism entering the third-party platform, the payment incidence relation between each payment mechanism and the payment user of the payment mechanism is established in advance, on the basis, the payment data of the payment mechanism is started, and under the condition that the payment mechanism is predicted to complete the current charge, all the payment users of the payment mechanism are inquired in the pre-established payment incidence relation, and the part of the un-paid users who have not paid the current charge in all the payment users of the payment mechanism is further determined, so that the payment reminding is specifically carried out on the un-paid users who have paid the current charge in the payment mechanism, the situation that the reminding of the part of the paid users is disturbed due to the fact that the payment reminding is sent to all the payment users of the payment mechanism is avoided, and the effectiveness and the timeliness of the payment reminding are improved.
The payment mechanism in this embodiment is a mechanism for providing payment services in the fields of water, electricity, gas, and the like, and a user who uses the payment service provided by the payment mechanism to pay fees is a payment user of the payment mechanism. Specifically, each payment mechanism has a respective payment service area, for example, the payment mechanism a provides an electric charge payment service for the electricity users in the area range of xx district in xx city, and for example, the payment mechanism B provides a gas charge payment service for the gas users in xx district in xx city.
In the present embodiment, for a plurality of payment institutions providing payment services of the same payment type, their respective payment service areas have regional exclusivity, that is: the payment service areas of a plurality of payment mechanisms with the same payment type are not overlapped, for example, the payment mechanism a and the payment mechanism C are the mechanisms providing the electric charge payment service, the payment service areas of the payment mechanism a and the payment mechanism C cannot be overlapped on the geographical position level, the payment service area of the payment mechanism a is the area range of xx area, and the payment service area of the payment mechanism C cannot be the area range of xx area. The reason why the payment service areas of the payment institutions with the same payment type are required to have regional exclusivity is that: the method and the system avoid repeated reminding of users in the area caused by a plurality of payment mechanisms providing payment service for the same area.
The payment data refers to related data generated in the payment process of a payment user of the payment mechanism, for example, a payment order generated by the payment user through payment service provided by the payment mechanism, and information such as a user identifier, a payment amount, a payment account period, a name of the payment mechanism, and the like of the payment user is recorded in the payment order.
Optionally, the payment mechanism is a parking mechanism of a third-party platform, the payment user is a platform user of the third-party platform, the payment user performs payment processing based on the third-party platform, and payment data of the payment mechanism is acquired through the third-party platform.
For any platform user of the third-party platform, if the platform user carries out payment processing on the third-party platform aiming at least one parking mechanism, or the platform user and the at least one parking mechanism sign a payment service agreement for the payment processing, the platform user is the payment user of the parking mechanism; on the contrary, if the platform user does not perform payment processing on any parking mechanism on the third-party platform and does not sign a payment service agreement with any parking mechanism, the platform user cannot be called as a payment user.
Based on this, in order to avoid unnecessary reminding interference caused to the platform users of the third-party platform in the process of executing the third-party platform by the payment processing method provided by this embodiment, according to the user data of the platform users on the third-party platform, historical payment users (platform users who have performed payment processing for at least one parking institution) and agreement payment users (platform users who have signed a payment service agreement for payment processing with at least one parking institution) can be screened from the platform users of the third-party platform as the payment users.
In specific implementation, under the condition that the number of the payment mechanisms resident on the third-party platform is huge, if each payment mechanism is monitored in real time and whether each payment mechanism is paid out or not is respectively monitored, the required resources or the generated calculated amount is large, in order to improve the processing efficiency and avoid the waste of the calculated resources, the characteristic that the payment mechanisms only carry out one-time payment in each payment period is considered, in an optional implementation manner provided by the embodiment, batch scheduling is adopted, the parking mechanisms are taken as the payment mechanisms for carrying out current payment judgment, specifically, the historical paying-out time conditions of each parking mechanism are analyzed by using the historical paying data of the parking mechanisms, so that the possible paying-out time or time period of each parking mechanism is predicted, on the basis, the parking mechanisms are divided into a plurality of batches according to the paying-out time, and sequentially carrying out subsequent expenditure presentation judgment and payment reminding processing on the lodging mechanisms of each batch according to the time sequence of the expenditure presentation time of the lodging mechanisms of each batch from front to back.
As described above, the present embodiment requires that the payment service areas of the payment mechanisms with the same payment type have regional exclusivity, and in practice, if the payment service areas are determined inaccurately, which results in possible overlapping of the payment service areas, the payment service range of the payment mechanism can be subjected to duplicate removal processing, so as to avoid that multiple payment mechanisms providing payment service for the same area cause repeated reminding of users in the area.
And step S104, judging whether the payment mechanism finishes current charge based on the payment data.
The current accounting refers to an accounting operation corresponding to an accounting time interval to which the current time point belongs, or an accounting operation for unpaid charges in a time interval before the current time point. Taking the payment mechanism a providing the electricity fee payment service as an example, the charge-off period of the payment mechanism a is 1 month, the current time point is 2 months, the charge-off of the payment mechanism a in 2 months is the electricity consumption fee of the electricity consumer in 1 month, and the bill after charge-off is also the electricity bill generated by the electricity consumption behavior of the electricity consumer in 1 month.
In order to improve the accuracy of the charge-off judgment of the payment mechanism, in an optional implementation manner provided in this embodiment, the current charge-off judgment is performed by inputting the payment data into a charge-off judgment model, and by using the historical charge-off time, the payment time distribution and the payment proportion determined based on the payment data as model inputs, the current charge-off judgment is performed by the charge-off judgment model according to the historical charge-off time, the payment time distribution, the payment proportion and respective corresponding weight factors, specifically, the current charge-off judgment is performed based on the charge-off judgment model as follows:
determining the historical charge-off time of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
determining the payment time distribution of the historical payment users of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
calculating the current charge accounting ratio of the charge mechanism based on the order number of the current charge orders generated by charging for the current charge and the total number of users of the charge users associated with the charge mechanism in the charge data; wherein, the payment proportion is equal to the ratio of the number of the orders to the total number of the users;
and inputting an expenditure judging model to judge whether the payment mechanism finishes the current expenditure by taking the historical expenditure time, the payment time distribution and/or the payment proportion as input.
Optionally, in the process of performing current-term charge-off judgment by the charge-off judgment model, current-term charge-off judgment is performed based on the historical charge-off time, the payment time distribution and/or the payment proportion and respective corresponding weight factors; the weight factor is determined according to payment data of the payment mechanism.
For example, in the process of carrying out current charge-off judgment on the payment mechanism a, firstly, historical payment bills of all payment users in half a year after the payment mechanism a passes are obtained, and on one hand, the historical payment bills of each month are analyzed to obtain the charge-off time of the payment mechanism a in each month; on the other hand, the payment time of all the payment users per month of the payment mechanism A is counted, and the distribution of the payment time per month of the payment mechanism A is determined; and thirdly, calculating the ratio of the number of orders for current payment to the total number of the payment users of the payment mechanism A, taking the ratio as the current payment proportion, taking the charge-out time of each month, the payment time distribution of each month and the current payment proportion of the payment mechanism A in half a year as inputs, and carrying out current charge-out judgment by the charge-out judgment model according to the inputs and combining with the weight factor.
Furthermore, in order to further improve the accuracy of the charge-off judgment, different weight factors can be respectively set for different payment mechanisms, that is, the weight factors of the charge-off judgment model correspond to the payment mechanisms one by one, and the weight factors can be specifically determined according to the historical payment data of each payment mechanism, for example, for the payment mechanisms with more regular historical charge-off time (the charge-off time is concentrated in a shorter time period), the weight factors corresponding to the historical charge-off time can be properly increased in the process of carrying out the charge-off judgment; for example, for a payment mechanism with concentrated payment time distribution, the weighting factor corresponding to the payment time distribution can be appropriately increased in the process of making the payment judgment. In the specific implementation process, historical expenditure time, payment time distribution, payment proportion and corresponding weight factors of the historical expenditure time, the payment time distribution and the payment proportion can be simultaneously used as model input, and the expenditure judgment model is used for carrying out current expenditure judgment; after the expenditure presentation judging model is input according to the historical expenditure presentation time, the payment time distribution and the payment proportion, the expenditure presentation judging model firstly determines the weight factor of the payment mechanism according to the input, and then carries out the current expenditure presentation judgment according to the historical expenditure presentation time, the payment time distribution and the payment proportion on the basis of the determined weight factor.
In specific implementation, whether the payment mechanism finishes current charge is judged based on the payment data;
if yes, indicating that the current account of the payment mechanism is finished, executing the following step S106, and inquiring a payment user associated with the payment mechanism in a payment association relationship between the mechanism and the user;
if not, the payment mechanism is indicated to be not subjected to current expenditure, the batch scheduling process of the parking mechanism of the third-party platform is returned to be executed, namely the historical payment data based on the parking mechanism is executed, and the batch scheduling parking mechanism is used as the payment mechanism for current expenditure judgment.
And S106, inquiring a payment user related to the payment mechanism in the association relationship between the payment mechanism and the user.
The mechanism and user payment incidence relation of the embodiment is used for recording payment mechanisms, payment users of the payment relation and payment incidence relations of the payment mechanisms and the payment users; the payment incidence relation is also embodied in that the geographic position of the payment user is in a payment service area of the payment mechanism.
In order to improve the query efficiency in the process of querying the payment user associated with the payment mechanism in the mechanism and user payment association relationship, in an optional implementation manner provided in this embodiment, before performing payment reminding processing, a mechanism and user payment association relationship in one-to-one correspondence with the payment mechanism is established, specifically, the mechanism and user payment association relationship is established in the following manner:
acquiring a payment service area of a payment mechanism and position information of a payment user in a payment user set;
determining the payment users whose geographic positions corresponding to the position information in the payment user set are in the payment service area;
and establishing an association relation between the payment mechanism and a payment user with the geographical position in the payment service area as a payment association relation between the mechanism corresponding to the payment mechanism and the user.
For example, a payment service area of a payment mechanism A is obtained from the payment mechanism A, the payment service area of the payment mechanism A is a regional range of xx district in city, positioning information of all payment users who have payment behaviors is obtained from a third party platform, then the payment users of which the positioning information is in the regional range of xx district in city are determined, and the determined payment users are established with an association relation with the payment mechanism A, so that the payment association relation between the institution of the payment mechanism A and the users is generated.
Here, the purpose of querying the payment user from the mechanism and user payment association relationship is to prepare for subsequently sending a payment reminder to the payment user, so that in order to reduce the probability that the payment reminder disturbs the payment user, in the process of establishing the mechanism and user payment association relationship, a payment service area and payment dimensions of the payment mechanism, and position information and a historical payment type of the payment user in the payment user set can be further obtained; then, screening out payment users with the historical payment types matched with the payment dimensions of the payment mechanism from the payment user set; secondly, determining the payment users of which the geographic positions corresponding to the position information in the screened payment users are in the payment service area; and finally, establishing an association relation between the payment mechanism and a payment user with the geographic position in the payment service area, wherein the association relation is used as the payment association relation between the mechanism corresponding to the payment mechanism and the user.
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 may also be updated according to the payment order of the payment user, in an optional implementation manner provided in this embodiment, a payment order generated by the platform user of the third party platform for paying for the payment institution is first obtained; and then establishing an incidence relation between the platform user corresponding to the generated payment order and the payment mechanism recorded in the generated payment order, and updating the payment incidence relation between the mechanism and the user based on the established incidence relation.
In specific implementation, based on a pre-established mechanism and user payment association relationship, a payment user associated with the payment mechanism is inquired in the mechanism and user payment association relationship. Under the condition that the payment mechanism corresponds to the payment association relationship between the mechanism and the user, all payment users recorded in the payment association relationship between the mechanism and the user corresponding to the payment mechanism are the payment users associated with the payment users.
Step S108, determining the non-payment users who do not pay for the current charge.
In order to improve the accuracy of determining the non-payment users among the payment users associated with the payment mechanism, so as to improve the effectiveness of subsequent payment reminding processing on the non-payment users, in an optional implementation manner provided in this embodiment, the following manner is adopted for determining the non-payment users among the payment users associated with the payment mechanism who do not pay for the current payment:
detecting a payment order of the payment user in the charge time interval to which the current charge belongs;
if the payment order of the payment user in the charge-off time interval is detected to be empty, determining the payment user as the non-payment user;
if the payment order of the payment user in the charge-off time interval is not detected to be empty, judging whether the detected payment order is a current payment order for paying for the current charge-off; if yes, the payment user is shown to have already processed payment processing on the current charge of the payment mechanism, and the processing is not needed; if not, the payment user is shown not to have performed payment processing on the current payment of the payment mechanism, and payment reminding processing is performed on the payment user.
According to the above example, the current charge of the payment mechanism A is that the generated electricity bill in 1 month is charged in the charge time interval of 2 months, and for a payment User1 of the payment mechanism A, whether a payment order exists in the month 2 of the payment User1 is detected; if the payment order exists, whether the payment order of the payment User1 in month 2 is the payment order for paying the electricity bill in month 1 of the payment mechanism A is further judged, and if not, the payment User1 is determined as the non-payment User of the payment mechanism A.
And step S110, carrying out payment reminding processing on the unpaid user.
After the non-payment user of the payment mechanism is determined, in order to remind the non-payment user of performing payment processing on the current payment of the payment mechanism, the mechanical energy of the non-payment user can be reminded of payment processing for the user in a manner of sending a payment notification message of the current payment of the payment mechanism to the non-payment user.
In addition, on the basis that the payment mechanism is an entry mechanism of a third-party platform and the unpaid user is a platform user of the third-party platform, the payment reminding of the current-term payment of the payment mechanism can be pushed to the unpaid user through the third-party platform. On this basis, in order to realize more humanized reminding and reduce the disturbance of reminding of the platform users who do not want to receive the payment reminding or mistakenly remind the payment reminding, so as to improve the experience of the users on the payment reminding and further improve the use experience of the users on a third-party platform, in an optional implementation manner provided by this embodiment, a reminding refusing control is configured in the payment reminding, and under the condition that the reminding refusing control is triggered, the non-payment users who are associated with the payment mechanism in the association relationship between the mechanism and the user payment mechanism and trigger the reminding refusing control are deleted.
The following further explains the payment reminding method provided in this embodiment by taking an application of the payment reminding method provided in this embodiment in a third party platform scenario as an example, and referring to fig. 2, the payment reminding method applied in the third party platform scenario specifically includes steps S202 to S220.
And S202, scheduling the payment mechanism residing on the third-party platform in a batch scheduling mode.
Step S204, payment data of a plurality of payment mechanisms corresponding to the scheduling task is obtained from a third-party platform.
Step S206, determining the historical charge-out time, the payment time distribution and the current payment proportion of each payment mechanism based on the payment data.
Step S208, inputting historical expenditure time, payment time distribution and current-term payment proportion as input, and inputting an expenditure judging model to judge whether each payment mechanism finishes current expenditure;
if yes, go to step S210;
if not, returning to execute the step S202;
step S210, inquiring the payment users associated with each payment mechanism in the association relationship between the payment mechanism and the user.
Step S212, detecting whether the inquired payment user is empty in the charge time interval to which the current charge belongs;
if the inquired payment user is not detected to be empty in the payment order within the charge-off time interval, executing step S214, step S218 and step S220;
if it is detected that the payment order within the queried payment user billing time interval is not empty, step S216 is executed.
Step S214, determining the payment user with the empty payment order as the non-payment user.
Step S216, judging whether the detected payment order is a current payment order for paying for current charge;
if yes, no treatment is needed;
if not, the payment user whose payment order is not empty is determined as the non-payment user, and step S218 and step S220 are executed.
Step S218, a payment reminding of the current payment of the payment mechanism is pushed to the non-payment user through the third party platform.
Step S220, under the condition that the reminding rejection control configured in the payment reminding is triggered, the un-paid user who is associated with the payment mechanism in the association relationship between the mechanism and the user payment and triggers the reminding rejection control is deleted.
In summary, the payment reminding method provided in this embodiment starts from the payment data of the payment mechanism, queries the payment users associated with the payment mechanism in the payment association relationship under the condition that it is determined that the payment mechanism completes the current payment, and further determines the part of the non-payment users associated with the payment mechanism that have not paid for the current payment, so as to specifically carry out the payment reminding on the non-payment users that are in the current payment of the payment mechanism, thereby avoiding the disturbance on the reminding of the part of the paid users that have paid for the part of the payment users caused by sending the payment reminding to all the payment users of the payment mechanism, and improving the effectiveness and timeliness of the payment reminding.
The embodiment of a payment reminding device provided by the specification is as follows:
in the above embodiment, a payment reminding method is provided, and correspondingly, a payment reminding device is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of a payment reminding device provided in this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
This embodiment provides a reminding device collects fee, includes:
a payment data acquisition module 302 configured to acquire payment data of a payment mechanism;
a current charge-off judging module 304 configured to judge whether the charging mechanism completes current charge-off based on the charging data;
if yes, operating a payment user query module 306, an unpaid user determination module 308 and a payment reminding processing module 310;
the payment user query module 306 is configured to query payment users associated with the payment mechanism in the association relationship between the mechanism and the user payment;
the unpaid user determination module 308 is configured to determine unpaid users who do not pay for the current charge-out among the paying users;
the payment reminding processing module 310 is configured to perform payment reminding processing on the unpaid user.
Optionally, the current statement determining module 304 is specifically configured to:
determining the historical charge-off time of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
determining the payment time distribution of the historical payment users of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
calculating the current charge accounting ratio of the charge mechanism based on the order number of the current charge orders generated by charging for the current charge and the total number of users of the charge users associated with the charge mechanism in the charge data;
and inputting an expenditure judging model to judge whether the payment mechanism finishes the current expenditure by taking the historical expenditure time, the payment time distribution and/or the payment proportion as input.
Optionally, the mechanism and the user payment association relationship are in one-to-one correspondence with the payment mechanism, and the mechanism and the user payment association relationship are established by operating the following modules:
the region acquisition module is configured to acquire a payment service region of a payment mechanism and position information of a payment user in a payment user set;
the payment user determining module is configured to determine a payment user of which the geographic position corresponding to the position information in the payment user set is in the payment service area;
and the incidence relation establishing module is configured to establish incidence relation between the payment mechanism and a payment user with the geographic position in the payment service area, and the incidence relation is used as the payment incidence relation between the mechanism corresponding to the payment mechanism and the user.
Optionally, the unpaid user determining module 308 is specifically configured to detect a payment order of the payment user in the charge time interval to which the current charge belongs; and if the payment order of the payment user in the expenditure presentation time interval is detected to be empty, determining the payment user as the unpaid user.
Optionally, if the unpaid user determining module 308 detects that the payment order of the payment user in the check-out time interval is not empty, it is determined whether the detected payment order is a current payment order for paying for the current check-out; if not, the payment reminding processing is carried out on the payment user.
Optionally, the payment mechanism is a parking mechanism of a third-party platform, the payment user is a platform user of the third-party platform, the payment user performs payment processing based on the third-party platform, and payment data of the payment mechanism is acquired through the third-party platform.
Optionally, the payment reminding processing module 310 is specifically configured to:
pushing a payment reminding of the current payment of the payment mechanism to the non-payment user through the third party platform;
and/or the presence of a gas in the gas,
and sending a payment notification message of the current payment of the payment mechanism to the unpaid user.
Optionally, a reminding rejection control is configured in the payment reminding; correspondingly, the reminding device of collecting fee still includes:
and the non-payment user deleting module is configured to delete the non-payment user which is associated with the payment mechanism in the association relationship between the mechanism and the user payment and triggers the reminding rejection control under the condition that the reminding rejection control is triggered.
Optionally, the payment reminding device further includes:
the payment order acquisition module is configured to acquire a payment order generated by a platform user of the third-party platform for payment aiming at the charge-off of a payment mechanism;
and the incidence relation updating module is configured to establish incidence relation between the platform user corresponding to the generated payment order and the payment mechanism recorded in the generated payment order, and update the payment incidence relation between the mechanism and the user based on the established incidence relation.
Optionally, the payment reminding device further includes:
and the batch scheduling module is configured to schedule the parking mechanism as the payment mechanism for making current charge-off judgment based on the historical payment data of the parking mechanism.
Optionally, if the output judgment result after the current accounting judgment module 304 operates is negative, the batch scheduling module operates.
Optionally, in the process of performing current-term charge-off judgment by the charge-off judgment model, current-term charge-off judgment is performed based on the historical charge-off time, the payment time distribution and/or the payment proportion and respective corresponding weight factors; the weight factor is determined according to payment data of the payment mechanism.
The embodiment of the payment reminding device provided by the specification is as follows:
corresponding to the above-described payment reminding method, based on the same technical concept, one or more embodiments of the present specification further provide a payment reminding device, where the payment reminding device is configured to execute the provided payment reminding method, and fig. 4 is a schematic structural diagram of the payment reminding device provided in one or more embodiments of the present specification.
The reminding equipment that pays that this embodiment provides includes:
as shown in fig. 4, the payment reminding apparatus may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, where the memory 402 may store one or more stored applications or data. Wherein memory 402 may be transient or persistent. The application program stored in the memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a payment reminder device. Still further, 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 reminding apparatus may also include one or more power sources 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, etc.
In one particular embodiment, the payment reminder apparatus 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 apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:
acquiring payment data of a payment mechanism;
judging whether the payment mechanism finishes current charge based on the payment data;
if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment;
determining non-payment users who do not pay for the current charge-off among the payment users;
and carrying out payment reminding processing on the unpaid users.
Optionally, the determining, based on the payment data, whether the payment mechanism completes the current posting includes:
determining the historical charge-off time of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
determining the payment time distribution of the historical payment users of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
calculating the current charge accounting ratio of the charge mechanism based on the order number of the current charge orders generated by charging for the current charge and the total number of users of the charge users associated with the charge mechanism in the charge data;
and inputting a charge-out judgment model to judge whether the payment mechanism finishes current charge-out by taking the historical charge-out time, the payment time distribution and/or the payment proportion as input.
Optionally, the mechanism and the user payment association relationship correspond to the payment mechanism one to one, and the mechanism and the user payment association relationship are established in the following manner:
acquiring a payment service area of a payment mechanism and position information of a payment user in a payment user set;
determining the payment users whose geographic positions corresponding to the position information in the payment user set are in the payment service area;
and establishing an association relation between the payment mechanism and a payment user with the geographical position in the payment service area as a payment association relation between the mechanism corresponding to the payment mechanism and the user.
Optionally, the determining an unpaid user who is not paying for the current charge-out among the paying users includes:
detecting a payment order of the payment user in the charge time interval to which the current charge belongs;
and if the payment order of the payment user in the charge-off time interval is detected to be empty, determining the payment user as the non-payment user.
Optionally, if it is detected that the payment order of the payment user in the charge-off time interval is not empty, determining whether the detected payment order is a current payment order for paying for the current charge-off;
if not, the payment reminding processing is carried out on the payment user.
Optionally, the payment mechanism is a parking mechanism of a third-party platform, the payment user is a platform user of the third-party platform, the payment user performs payment processing based on the third-party platform, and payment data of the payment mechanism is acquired through the third-party platform.
Optionally, the process of reminding payment to the unpaid user includes:
pushing a payment reminding of the current payment of the payment mechanism to the non-payment user through the third party platform;
and/or the presence of a gas in the atmosphere,
and sending a payment notification message of the current payment of the payment mechanism to the unpaid user.
Optionally, a reminding rejection control is configured in the payment reminding;
and under the condition that the reminding rejection control is triggered, deleting the unpaid users which are associated with the payment mechanism in the association relationship between the mechanism and the user payment and trigger the reminding rejection control.
Optionally, the computer executable instruction, in the process of being executed, further includes:
acquiring a payment order generated by a platform user of the third-party platform for paying for the charge of the charge mechanism;
and establishing an incidence relation between the platform user corresponding to the generated payment order and the payment mechanism recorded in the generated payment order, and updating the payment incidence relation between the mechanism and the user based on the established incidence relation.
Optionally, the computer executable instruction, in the process of being executed, further includes:
and based on the historical payment data of the parking mechanism, batch scheduling the parking mechanism as the payment mechanism for carrying out current expenditure judgment.
Optionally, if the result of the judgment on whether the payment mechanism completes the current accounting instruction execution is negative based on the historical payment data, the historical payment data based on the parking mechanism is executed, and the parking mechanism is dispatched in batches as the payment mechanism instruction for performing the current accounting judgment.
Optionally, in the process of performing current-term charge-off judgment by the charge-off judgment model, current-term charge-off judgment is performed based on the historical charge-off time, the payment time distribution and/or the payment proportion and respective corresponding weight factors; the weight factor is determined according to payment data of the payment mechanism.
An embodiment of a storage medium provided in this specification is as follows:
on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the payment reminding method described above.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when executed, the computer-executable instructions implement the following processes:
acquiring payment data of a payment mechanism;
judging whether the payment mechanism finishes current charge based on the payment data;
if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment;
determining non-payment users who do not pay for the current charge in the payment users;
and carrying out payment reminding processing on the unpaid users.
Optionally, the determining, based on the payment data, whether the payment mechanism completes the current posting includes:
determining the historical charge-off time of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
determining the payment time distribution of the historical payment users of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
calculating the current charge accounting ratio of the charge mechanism based on the order number of the current charge orders generated by charging for the current charge and the total number of users of the charge users associated with the charge mechanism in the charge data;
and inputting an expenditure judging model to judge whether the payment mechanism finishes the current expenditure by taking the historical expenditure time, the payment time distribution and/or the payment proportion as input.
Optionally, the mechanism and the user payment association relationship correspond to a payment mechanism one to one, and the mechanism and the user payment association relationship are established in the following manner:
acquiring a payment service area of a payment mechanism and position information of a payment user in a payment user set;
determining the payment users whose geographic positions corresponding to the position information in the payment user set are in the payment service area;
and establishing an association relation between the payment mechanism and a payment user with the geographical position in the payment service area as a payment association relation between the mechanism corresponding to the payment mechanism and the user.
Optionally, the determining that the non-payment user who does not pay for the current charge includes:
detecting a payment order of the payment user in the charge time interval to which the current charge belongs;
and if the payment order of the payment user in the charge-off time interval is detected to be empty, determining the payment user as the non-payment user.
Optionally, if it is detected that the payment order of the payment user in the charge-off time interval is not empty, determining whether the detected payment order is a current payment order for paying for the current charge-off;
if not, the payment reminding processing is carried out on the payment user.
Optionally, the payment mechanism is a parking mechanism of a third-party platform, the payment user is a platform user of the third-party platform, the payment user performs payment processing based on the third-party platform, and payment data of the payment mechanism is acquired through the third-party platform.
Optionally, the process of reminding payment to the unpaid user includes:
pushing a payment reminding of the current payment of the payment mechanism to the non-payment user through the third party platform;
and/or the presence of a gas in the gas,
and sending a payment notification message of the current payment of the payment mechanism to the unpaid user.
Optionally, a reminding rejection control is configured in the payment reminding;
and under the condition that the reminding rejection control is triggered, deleting the unpaid users which are associated with the payment mechanism in the association relationship between the mechanism and the user payment and trigger the reminding rejection control.
Optionally, the computer executable instructions, when executed, further implement the following process:
acquiring a payment order generated by a platform user of the third-party platform for paying for the charge of the charge mechanism;
and establishing an association relationship between the platform user corresponding to the generated payment order and the payment mechanism recorded in the generated payment order, and updating the payment association relationship between the mechanism and the user based on the established association relationship.
Optionally, before the process of acquiring the payment data of the payment mechanism is executed, the computer-executable instructions, when executed, further implement the following process:
and based on the historical payment data of the parking mechanism, batch scheduling the parking mechanism as the payment mechanism for carrying out current expenditure judgment.
Optionally, if the result of the judgment on whether the payment mechanism completes the current accounting process execution is negative based on the historical payment data, the historical payment data based on the parking mechanism is executed, and the parking mechanism is dispatched in batches to serve as the payment mechanism process for performing the current accounting judgment.
Optionally, in the process of performing current-term charge-off judgment by the charge-off judgment model, current-term charge-off judgment is performed based on the historical charge-off time, the payment time distribution and/or the payment proportion and respective corresponding weight factors; the weight factor is determined according to payment data of the payment mechanism.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the payment reminding method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described here.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry for implementing the logical method flows can be readily obtained by a mere need to program the method flows with some of the hardware description languages described above and into an integrated circuit.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, 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.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.
Claims (15)
1. A payment reminding method is applied to a third-party platform and comprises the following steps:
acquiring payment data of a payment mechanism; the payment data is acquired at the third-party platform;
based on the payment data, determining the historical charge-out time, the payment time distribution and/or the current-term payment proportion of the payment mechanism and predicting whether the payment mechanism completes the current charge-out;
if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment;
determining non-payment users who do not pay for the current charge-off among the payment users;
and carrying out payment reminding processing on the unpaid users.
2. The payment reminding method according to claim 1, wherein the determining whether the payment mechanism completes the current payment based on the payment data comprises:
determining the historical charge-off time of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
determining the payment time distribution of the historical payment users of the payment mechanism based on the payment time recorded in the historical payment order contained in the payment data;
calculating the current charge accounting ratio of the charge mechanism based on the order number of the current charge orders generated by charging for the current charge and the total number of users of the charge users associated with the charge mechanism in the charge data;
and inputting an expenditure judging model to judge whether the payment mechanism finishes the current expenditure by taking the historical expenditure time, the payment time distribution and/or the payment proportion as input.
3. The payment reminding method according to claim 1, wherein the institution and user payment incidence relation is in one-to-one correspondence with payment institutions, and the institution and user payment incidence relation is established by the following method:
acquiring a payment service area of a payment mechanism and position information of a payment user in a payment user set;
determining the payment users whose geographic positions corresponding to the position information in the payment user set are in the payment service area;
and establishing an association relation between the payment mechanism and a payment user with the geographical position in the payment service area as a payment association relation between the mechanism corresponding to the payment mechanism and the user.
4. The payment reminding method according to claim 1, wherein the determining of the non-payment users who do not pay for the current payment comprises:
detecting a payment order of the payment user in the charge time interval to which the current charge belongs;
and if the payment order of the payment user in the charge-off time interval is detected to be empty, determining the payment user as the non-payment user.
5. The payment reminding method according to claim 4, if it is detected that the payment order of the payment user in the charge-off time interval is not empty, determining whether the detected payment order is a current payment order for paying for the current charge-off;
if not, the payment reminding processing is carried out on the payment user.
6. The payment reminding method according to claim 1, wherein the payment mechanism is a parking mechanism of a third party platform, the payment user is a platform user of the third party platform, the payment user performs payment processing based on the third party platform, and payment data of the payment mechanism is acquired through the third party platform.
7. The payment reminding method according to claim 6, wherein the payment reminding processing for the non-payment user comprises:
pushing a payment reminding of the current payment of the payment mechanism to the non-payment user through the third party platform;
and/or the presence of a gas in the gas,
and sending a payment notification message of the current payment of the payment mechanism to the unpaid user.
8. The payment reminding method according to claim 7, wherein a reminding rejection control is configured in the payment reminding;
and under the condition that the reminding rejection control is triggered, deleting the unpaid users which are associated with the payment mechanism in the association relationship between the mechanism and the user payment and trigger the reminding rejection control.
9. The payment reminding method according to claim 6, further comprising:
acquiring a payment order generated by a platform user of the third-party platform for paying for the charge of the charge mechanism;
and establishing an incidence relation between the platform user corresponding to the generated payment order and the payment mechanism recorded in the generated payment order, and updating the payment incidence relation between the mechanism and the user based on the established incidence relation.
10. The payment reminding method according to claim 6, before the step of obtaining payment data of a payment institution is executed, further comprising:
and based on the historical payment data of the parking mechanism, batch scheduling the parking mechanism as the payment mechanism for carrying out current expenditure judgment.
11. A payment reminding method according to claim 10, if the result of the determination is negative after the payment mechanism completes the current charge-out step based on the historical payment data, the step of scheduling the parking mechanism in batches as the payment mechanism for the current charge-out determination is executed based on the historical payment data of the parking mechanism.
12. The payment reminding method according to claim 2, wherein in the process of the current charge judgment of the charge judgment model, the current charge judgment is carried out based on the historical charge time, the charge time distribution and/or the charge ratio and the respective corresponding weight factors;
the weight factor is determined according to payment data of the payment mechanism.
13. The utility model provides a reminding device collects fee, moves in third party's platform, includes:
the payment data acquisition module is configured to acquire payment data of a payment mechanism; the payment data is acquired at the third-party platform;
the current-period charge-out prediction module is configured to determine historical charge-out time, charge-out time distribution and/or current-period charge proportion of the charge mechanism based on the charge data and predict whether the charge mechanism completes current charge-out;
if yes, operating a payment user query module, a non-payment user determination module and a payment reminding processing module;
the payment user inquiry module is configured to inquire payment users related to the payment mechanism in the association relationship between the mechanism and the user payment;
the non-payment user determining module is configured to determine non-payment users who do not pay for the current expenditure in the payment users;
the payment reminding processing module is configured to carry out payment reminding processing on the unpaid user.
14. A data processing apparatus comprising:
a processor; and the number of the first and second groups,
a memory configured to store computer-executable instructions that, when executed, cause the processor to:
acquiring payment data of a payment mechanism; the payment data is acquired at a third-party platform;
based on the payment data, determining the historical charge-out time, the payment time distribution and/or the current-term payment proportion of the payment mechanism and predicting whether the payment mechanism completes the current charge-out;
if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment;
determining non-payment users who do not pay for the current charge in the payment users;
and carrying out payment reminding processing on the unpaid users.
15. A storage medium storing computer-executable instructions that when executed implement the following:
acquiring payment data of a payment mechanism; the payment data is acquired at a third-party platform;
based on the payment data, determining the historical charge-out time, the payment time distribution and/or the current-term payment proportion of the payment mechanism and predicting whether the payment mechanism completes the current charge-out;
if yes, inquiring a payment user associated with the payment mechanism in the association relationship between the mechanism and the user payment;
determining non-payment users who do not pay for the current charge-off among the payment users;
and carrying out payment reminding processing on the unpaid users.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010887777.XA CN111968302B (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
| CN202210935688.7A CN115331355A (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010887777.XA CN111968302B (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210935688.7A Division CN115331355A (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111968302A CN111968302A (en) | 2020-11-20 |
| CN111968302B true CN111968302B (en) | 2022-08-12 |
Family
ID=73401005
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010887777.XA Active CN111968302B (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
| CN202210935688.7A Pending CN115331355A (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210935688.7A Pending CN115331355A (en) | 2020-08-28 | 2020-08-28 | Payment reminding method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN111968302B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112488893B (en) * | 2020-11-30 | 2023-11-17 | 泰康保险集团股份有限公司 | Service data processing method and device, storage medium and electronic equipment |
| CN113765681B (en) * | 2021-09-08 | 2023-02-28 | 中国电信股份有限公司 | Expenditure presentation processing method, device, medium and equipment |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104484770A (en) * | 2014-12-29 | 2015-04-01 | 芜湖乐锐思信息咨询有限公司 | Intellectual property payment reminding system based on cloud database |
| CN106447177A (en) * | 2016-09-09 | 2017-02-22 | 国家电网公司 | Intelligent power-rationing method and intelligent electric meter |
| CN107016535A (en) * | 2016-11-11 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of area message sharing method and device |
| CN107087017A (en) * | 2017-03-09 | 2017-08-22 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of business drainage |
| CN107478882A (en) * | 2017-09-06 | 2017-12-15 | 上海斐讯数据通信技术有限公司 | Intelligent electric meter long-distance monitorng device |
| CN108062665A (en) * | 2017-12-29 | 2018-05-22 | 安徽知创空间企业管理有限公司 | Property charging management system |
| CN109086622A (en) * | 2018-07-25 | 2018-12-25 | 深圳慧安康科技有限公司 | A kind of implementation method and node device of intelligence community |
| CN109472938A (en) * | 2018-11-21 | 2019-03-15 | 奕铭（大连）科技发展有限公司 | A kind of multi-functional resident's fare payment system |
| CN110136002A (en) * | 2019-03-21 | 2019-08-16 | 阿里巴巴集团控股有限公司 | Payment based reminding method and device calculate equipment and computer readable storage medium |
| CN111080910A (en) * | 2019-11-15 | 2020-04-28 | 苏州浪潮智能科技有限公司 | Remote meter reading method and system based on block chain |
| CN111311218A (en) * | 2018-12-11 | 2020-06-19 | 杭州壹凌贰四科技有限公司 | Property charging management system |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101141512A (en) * | 2007-09-28 | 2008-03-12 | 中国移动通信集团福建有限公司 | Virtual month account processing equipment for communication industry |
| JP5451206B2 (en) * | 2009-06-23 | 2014-03-26 | Ｎｅｃインフロンティア株式会社 | Self-service station settlement device and self-service station settlement method |
| CN104424534A (en) * | 2013-09-10 | 2015-03-18 | 北京市燃气集团有限责任公司 | Management system for gas-charging information |
| CN105260815A (en) * | 2015-09-18 | 2016-01-20 | 国网辽宁省电力有限公司鞍山供电公司 | Electric power system payment channel evaluating method based on large data |
| CN106056772B (en) * | 2016-06-12 | 2019-01-22 | 江苏荣夏安全科技有限公司 | A kind of electricity charge pre-paid system and method |
| CN106372883A (en) * | 2016-08-29 | 2017-02-01 | 成都支付通卡友电子商务有限公司 | Urban integrated public utility payment system |
| CN109389484A (en) * | 2018-09-26 | 2019-02-26 | 中国平安人寿保险股份有限公司 | Account is entered an item of expenditure in the accounts method, apparatus, computer equipment and storage medium |
| CN109903182A (en) * | 2019-02-25 | 2019-06-18 | 国网河南省电力公司电力科学研究院 | Power customer arrears risk analysis method and device based on random forests algorithm |
| TWM590284U (en) * | 2019-07-12 | 2020-02-01 | 謝清茹 | Online water/electricity/gas fee payment management system for rental items of estate |
| CN111105562A (en) * | 2019-12-16 | 2020-05-05 | 广东电网有限责任公司 | Electricity fee inquiry and payment system |
| CN111581483B (en) * | 2020-04-02 | 2024-04-05 | 网宿科技股份有限公司 | Charging method, electronic equipment and storage medium |
-
2020
- 2020-08-28 CN CN202010887777.XA patent/CN111968302B/en active Active
- 2020-08-28 CN CN202210935688.7A patent/CN115331355A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104484770A (en) * | 2014-12-29 | 2015-04-01 | 芜湖乐锐思信息咨询有限公司 | Intellectual property payment reminding system based on cloud database |
| CN106447177A (en) * | 2016-09-09 | 2017-02-22 | 国家电网公司 | Intelligent power-rationing method and intelligent electric meter |
| CN107016535A (en) * | 2016-11-11 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of area message sharing method and device |
| CN107087017A (en) * | 2017-03-09 | 2017-08-22 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of business drainage |
| CN107478882A (en) * | 2017-09-06 | 2017-12-15 | 上海斐讯数据通信技术有限公司 | Intelligent electric meter long-distance monitorng device |
| CN108062665A (en) * | 2017-12-29 | 2018-05-22 | 安徽知创空间企业管理有限公司 | Property charging management system |
| CN109086622A (en) * | 2018-07-25 | 2018-12-25 | 深圳慧安康科技有限公司 | A kind of implementation method and node device of intelligence community |
| CN109472938A (en) * | 2018-11-21 | 2019-03-15 | 奕铭（大连）科技发展有限公司 | A kind of multi-functional resident's fare payment system |
| CN111311218A (en) * | 2018-12-11 | 2020-06-19 | 杭州壹凌贰四科技有限公司 | Property charging management system |
| CN110136002A (en) * | 2019-03-21 | 2019-08-16 | 阿里巴巴集团控股有限公司 | Payment based reminding method and device calculate equipment and computer readable storage medium |
| CN111080910A (en) * | 2019-11-15 | 2020-04-28 | 苏州浪潮智能科技有限公司 | Remote meter reading method and system based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115331355A (en) | 2022-11-11 |
| CN111968302A (en) | 2020-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111968302B (en) | Payment reminding method and device | |
| CN108960790B (en) | Method, device, server and system for processing bill service | |
| CN108596401B (en) | Traffic prediction method and device | |
| KR20150037882A (en) | Push-based recommendations | |
| WO2021203960A1 (en) | Information processing method and apparatus, device, and storage medium | |
| TWI718379B (en) | Evaluation method, device and equipment for users using shared items | |
| CN109949141A (en) | Financial settlement method, apparatus and system | |
| CN114141048A (en) | Parking space recommendation method and device, and parking space prediction method and device of parking lot | |
| CN110008252B (en) | Data checking method and device | |
| CN115456801B (en) | Artificial intelligence big data wind control system, method and storage medium for personal credit | |
| CN116188123A (en) | Renting management method and device based on credit | |
| CN113191817B (en) | Service charge calculation method and device | |
| CN112634476B (en) | Parking data management method, server, device, equipment and system | |
| CN113657635B (en) | Method for predicting loss of communication user and electronic equipment | |
| CN114550322A (en) | Vehicle service fee processing method and device | |
| CN113627634A (en) | Vehicle charging reservation processing method and device | |
| CN109345300B (en) | Data statistical method and device | |
| CN105989501B (en) | Method and device for inquiring consultation account | |
| CN113065831B (en) | Charging equipment distribution processing method and device | |
| CN118052544A (en) | Order payment processing method and device | |
| CN116070921A (en) | Service policy generation method, device and equipment | |
| CN114819949A (en) | Recharge processing method and device | |
| CN112418882B (en) | Block chain based product circulation method, device, equipment and system | |
| CN114779914B (en) | Battery electric quantity reminding method and device | |
| CN117194514A (en) | Data summarization method, device and medium for business data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |