CN114065277B - Bill pushing method and device, electronic equipment and storage medium - Google Patents
Bill pushing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114065277B CN114065277B CN202111279495.2A CN202111279495A CN114065277B CN 114065277 B CN114065277 B CN 114065277B CN 202111279495 A CN202111279495 A CN 202111279495A CN 114065277 B CN114065277 B CN 114065277B
- Authority
- CN
- China
- Prior art keywords
- account
- task
- bill
- pushing
- subscription
- 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
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 abstract description 8
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 238000013475 authorization Methods 0.000 description 3
- 230000002354 daily effect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 230000001172 regenerating effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure provides a bill pushing method, a device, an electronic device and a storage medium, relates to the technical field of data processing, in particular to the technical field of cloud computing, and comprises the following steps: acquiring account identification and subscription content; judging whether the account has the authority of subscribing the subscription content according to the account identification; if the account has the authority of subscribing the subscription content, judging whether the account has an opened storage space; if the storage space is opened, generating a subscription record and storing the subscription record into a subscription record table; generating a push task according to the subscription record and storing the push task in a push task table when at least one first preset time point; judging whether an account identifier corresponding to a push task in a push task table is associated with a sub-account identifier or not when at least one second preset time point corresponding to the first preset time point is reached; if yes, generating a bill file according to an account number identifier corresponding to the pushing task and a sub-account number identifier associated with the account number identifier, pushing the bill file to a user to which the account number belongs, and storing the bill file in a storage space corresponding to the account number.
Description
Technical Field
The disclosure relates to the technical field of data processing, in particular to the technical field of cloud computing, and specifically relates to a bill pushing method, a device, electronic equipment and a storage medium.
Background
The existing billing system only has a PULL mode (a user needs to actively acquire data from a server through a client), so that the user in the existing billing system cannot acquire own billing information in time, and experience is poor.
Disclosure of Invention
The disclosure provides a bill pushing method, a bill pushing device, electronic equipment and a storage medium.
According to an aspect of the present disclosure, there is provided a bill pushing method, including:
Acquiring account identification and subscription content;
Judging whether the account has the authority of subscribing the subscription content according to the account identification;
If the account has the authority to subscribe the subscription content, judging whether the account has opened a storage space;
if the account has opened a storage space, generating a subscription record according to the account identification and subscription content and storing the subscription record in a subscription record table;
Generating a push task according to the subscription record in the subscription record table and storing the push task in a push task table when at least one first preset time point;
Judging whether an account identifier corresponding to a push task in the push task table is associated with at least one sub-account identifier or not when at least one second preset time point corresponding to a first preset time point is reached;
And if the account identifier is associated with at least one sub-account identifier, generating a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier, pushing the bill file to a user to which the account belongs, and storing the bill file in a storage space corresponding to the account.
According to another aspect of the present disclosure, there is provided a bill pushing device including:
the acquisition module is used for acquiring account identification and subscription content;
The judging module is used for judging whether the account has the authority of subscribing the subscription content according to the account identification;
The judging module is further used for judging whether the account has the storage space opened or not if the account has the authority to subscribe the subscription content;
the computing module is used for generating a subscription record according to the account identification and the subscription content and storing the subscription record in a subscription record table if the account has opened a storage space;
the computing module is further configured to generate a push task according to a subscription record in the subscription record table and store the push task in a push task table when at least one first preset time point;
The judging module is further configured to judge, when at least one second preset time point corresponding to the first preset time point, whether an account identifier corresponding to a push task in the push task table is associated with at least one sub-account identifier;
And the pushing module is used for generating a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier if the account identifier is associated with the at least one sub-account identifier, pushing the bill file to a user to which the account belongs and storing the bill file in a storage space corresponding to the account.
According to another aspect of the present disclosure, there is provided an electronic device including:
at least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the preceding claims.
According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform any one of the methods described above.
According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of any of the above.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
According to the method disclosed by the invention, the user can clearly receive the consumption condition of the user in each timed period by pushing the bill information to the user at regular time, the user experience is improved, the bill file is stored in the storage space corresponding to the account after the bill is pushed to the user, the user can download the bill file from the storage space corresponding to the account when required, the user can conveniently use the bill file, the user can select whether to acquire the bill information of the sub-account when subscribing, and if a plurality of sub-accounts are associated, one or a plurality of sub-accounts can be selected, so that the bill information required by the user can be acquired, the user can conveniently manage a plurality of accounts, the operation of the user is facilitated, and the use experience of the user is improved.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
fig. 1 is a flow diagram of a bill pushing method provided according to an embodiment of the present disclosure;
Fig. 2 is a flow chart of a bill pushing subscription method provided according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of a method for generating push tasks according to an embodiment of the present disclosure;
FIG. 4 is a flow chart of another method for generating push tasks provided in accordance with an embodiment of the present disclosure;
FIG. 5 is a flow chart of a method for regenerating push tasks provided in accordance with an embodiment of the present disclosure;
FIG. 6 is a flow chart of a method for regenerating a billing file provided in accordance with an embodiment of the present disclosure;
FIG. 7 is a schematic diagram of a bill pushing device provided in accordance with an embodiment of the present disclosure;
fig. 8 is a block diagram of an electronic device for implementing a bill pushing method of an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In order to enable a user to push bills to the user in a timed manner, so that the user can acquire own bill information in time, and the experience of the user is improved, as shown in fig. 1, an embodiment of the disclosure provides a bill pushing method, which includes:
step 101, acquiring account identification and subscription content.
The account identification of the account and the subscription content required by the user are obtained, and the subscription content refers to bill content required by the user, such as running bill, resource month bill, historical consumption trend, cash balance detail and the like.
And 102, judging whether the account has the authority to subscribe the subscription content according to the account identification.
As shown in fig. 2, after the account identifier and the subscription content are obtained, whether the account has the authority to subscribe to the corresponding subscription content is determined according to the account identifier of the account, if the account has the authority to subscribe to the subscription content, step 103 is continuously executed, and if the account does not have the authority to subscribe to the subscription content, the subscription fails.
And step 103, if the account has the authority to subscribe the subscription content, judging whether the account has opened a storage space.
As shown in fig. 2, if the account has the authority to subscribe to the corresponding subscription content, then continuing to determine whether the account has a storage space opened, if the account has a storage space opened, continuing to execute step 104, if the account has no storage space opened, notifying the user to enable the user to open the storage space, and after the user opens the storage space, continuing to execute step 104;
In an embodiment, after determining that the account has opened the storage space, the user may further obtain authorization, if the user refuses the authorization, the subscription fails, and if the user agrees to the authorization, the step 104 is further performed.
And 104, if the account has opened a storage space, generating a subscription record according to the account identification and subscription content, and storing the subscription record in a subscription record table.
If the account number opens the storage space, generating a subscription record according to the account number identification and subscription content and storing the subscription record in a subscription record table;
for example, the account number of a certain account number is identified as 0127, and subscription content required by the user is a running bill, a resource month bill, a historical consumption trend and a cash balance, and the subscription content is converted into an array: and generating a subscription record by converting the account identification and the subscription content of the plurality of groups into the subscription record list, and storing the subscription record list.
And 105, generating a push task according to the subscription record in the subscription record table and storing the push task in the push task table when at least one first preset time point is reached.
Generating a push task according to a subscription record in a subscription record table and storing the push task in the push task table when at least one first preset time point;
For example, at 5 points 20 minutes per day, generating a push task according to a subscription record in a subscription record table and storing the push task in the push task table;
For another example, at point 1 and point 8 for 20 minutes each month, generating a push task according to the subscription record in the subscription record table and storing the push task in the push task table;
The two examples differ in that daily billing information is pushed daily, while monthly billing information is pushed per month 1.
And step 106, judging whether the account identification corresponding to the push task in the push task list is associated with at least one sub-account identification or not when at least one second preset time point corresponding to the first preset time point is reached.
When at least one second preset time point corresponding to the first preset time point, judging whether an account identifier corresponding to a push task in a push task table is associated with at least one sub-account identifier, namely judging whether an account corresponding to the push task is associated with at least one sub-account, when subscription content is acquired in step 101, a user can select whether to acquire bill information of the sub-account, if a plurality of sub-accounts are associated, one or a plurality of sub-accounts can be selected, so that bill information required by the user is acquired, the user can conveniently manage the plurality of accounts, the bill information of the plurality of accounts is acquired, operation of the user is facilitated, and use experience of the user is improved.
And 107, if the account identifier is associated with at least one sub-account identifier, generating a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier, pushing the bill file to a user to which the account belongs, and storing the bill file in a storage space corresponding to the account.
If at least one sub-account is associated with the account, acquiring bill information of the account and the at least one sub-account associated with the account according to an account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier, so as to generate a bill file containing the bill information of the account and the at least one sub-account associated with the account, pushing the bill file to a user to which the account belongs and storing the bill file in a storage space corresponding to the account;
For example, the time for generating the pushing task is 5 points per day for 20 time sharing, and then a bill file is generated at 8 points per day for 10 points per day according to the pushing task in the pushing task list and pushed to the user to which the account belongs and stored in a storage space corresponding to the account;
For another example, the time for generating the pushing task is 20 minutes at the number 1 point of each month, and then a bill file is generated at the number 1 point of each month according to the pushing task in the pushing task list and pushed to the user to which the account belongs and stored in a storage space corresponding to the account;
The daily consumption condition or the monthly consumption condition of the user can be clearly received by the user through pushing the bill information to the user every day and every month No. 1, the user experience is improved, the bill file is stored in the storage space corresponding to the account after the bill is pushed to the user, the user can download the bill file from the storage space corresponding to the account when needed, the user can conveniently use the bill file, the user can select whether to acquire the bill information of the sub-account when subscribing, and if a plurality of sub-accounts are associated, one or a plurality of sub-accounts can be selected, so that the bill information required by the user is acquired, the user can conveniently manage a plurality of accounts, the bill information of the plurality of accounts is acquired, the operation of the user is facilitated, and the use experience of the user is improved.
In step 106, a bill file is generated according to the account identifier corresponding to the push task and at least one sub-account identifier associated with the account identifier, and pushed to the user to whom the account belongs and stored in a storage space corresponding to the account, and in one embodiment, a bill request is generated according to the push task in the push task table;
splitting the billing request into a plurality of sub-billing requests;
Generating a plurality of sub-bill files according to the plurality of sub-bill requests, and merging the plurality of sub-bill files into a bill file;
pushing the bill file to a user to which the account belongs and storing the bill file into a storage space corresponding to the account.
Generating a bill request according to the pushing task in the pushing task list, and splitting the bill request into a plurality of sub bill requests;
For example, the bill request needs to request various data such as a running bill, a resource month bill, a historical consumption trend, a cash balance statement, and the like, and the bill request is split into 6 sub-bill requests, each of which requests one data;
for another example, the bill request has a special field, and the special field corresponds to a larger data volume, so that the special field is split into a sub-request independently, and other fields are split into a plurality of sub-requests according to the data volume;
Splitting the bill request into a plurality of sub-requests, reducing the data volume of the simultaneous requests, remarkably reducing the pressure of equipment, improving the overall stability of the system, pushing the bill file to a user to which the account belongs after generating a plurality of sub-bill files according to the plurality of sub-bill requests and combining the plurality of sub-bill files into the bill file, and storing the bill file into a storage space corresponding to the account.
In step 105, before generating a push task according to a subscription record in the subscription record table and storing the push task in the push task table, in an implementation manner, when at least one first preset time point, judging whether the last push time corresponding to the subscription record in the subscription record table is the last first preset time point;
if yes, judging whether the retry times of the generated pushing task based on the subscription record are smaller than the first preset times;
if yes, the subscription record is distributed to a target port of the target machine to generate a push task, and the subscription record is bound with the port.
As shown in fig. 3, when at least one first preset time point is needed, that is, when a push task needs to be generated according to a subscription record in a subscription record table and stored in a push task table, it is judged whether the last push time corresponding to the subscription record in the subscription record table is the last first preset time point, if the last push time corresponding to the subscription record is not the last first preset time point, the subscription record may be pushed or has failed, the push task is generated and failed, whether the subsequent manual checking needs to be continuously performed is needed, if the last push time corresponding to the subscription record is the last first preset time point, it is explained that the subscription record is normal, it is continuously judged whether the retry number of the push task based on the subscription record is smaller than the first preset number, if the retry number of the push task based on the subscription record is larger than or equal to the first preset number, if the retry number of the push task based on the subscription record is larger than the first preset number of times, some reasons that the push task may not be overcome may exist, then the manual checking needs to be generated, if the subscription record is required to be bound to the first preset number of times and the subscription record is allowed to be executed in a designated table, and the subscription record is allowed to be executed in any table, assigning the subscription record to a designated one or any port of a designated one or any machine to generate a push task and binding the subscription record with the port can prevent the subscription record from being repeatedly executed by other machines or other ports of the machine, prevent the overall efficiency of the system from being reduced, and even repeatedly generate the push task, so that the user is repeatedly pushed with the bill file.
In step 105, before generating a bill file according to the account identifier corresponding to the push task and at least one sub-account identifier associated with the account identifier, in an embodiment, it is determined whether a subscription record corresponding to the push task is bound to the target port;
if yes, judging whether the retry number of the generated bill file based on the pushing task is smaller than a second preset number;
If yes, the push task is distributed to the target port, and the push task is bound with the target port.
As shown in fig. 4, when a bill file is generated according to a pushing task in the pushing task table at least at a second preset time point corresponding to a first preset time point, it is determined whether a subscription record corresponding to the pushing task is bound to a target port, if the subscription record corresponding to the pushing task is not bound to the target port, the subscription record corresponding to the pushing task may have a problem, the generation of the pushing task fails, the subsequent manual audit is required, if the subscription record corresponding to the pushing task is bound to the target port, it is continuously determined whether the retry number of generated bill files based on the pushing task is smaller than the second preset number, if the retry number of generated bill files based on the pushing task is larger than or equal to the second preset number, if the retry number of generated bill files based on the pushing task is too large, there may be some unavoidable reasons, the generation of the pushing task fails, if the retry number of generated bill files based on the pushing task is smaller than the second preset number, the first execution or in the target port is allowed to be bound to the target port, the efficiency of the pushing task can be prevented from being executed, and the end port can be prevented from being repeatedly executed by the machine, and the target port can be prevented from being repeatedly executed.
In step 105, after generating a push task according to the subscription record in the subscription record table, in an implementation manner, whether the generation of the push task according to the subscription record is successful is determined;
if the generation of the push task fails, judging whether the retry number of the generated push task based on the subscription record is smaller than a first preset number;
If the number of times is smaller than the first preset number of times, generating a push task again according to the subscription record, and adding 1 to the retry number of the generated push task.
As shown in fig. 5, after a push task is generated according to a subscription record in a subscription record table, whether the push task is successfully generated needs to be judged, and generation of the push task according to the subscription record in the subscription record table is possible to cause generation failure due to some reasons, so that whether the push task is successfully generated needs to be judged, if the push task is successfully generated, the push task is not required to be regenerated, then the push task is stored in the push task table, if the push task is failed to be generated, whether the retry number of the push task generated based on the subscription record is smaller than a first preset number of times is continuously judged, if the retry number of the push task generated based on the subscription record is larger than or equal to the first preset number of times, the retry number of the push task generated based on the subscription record is excessive, and some reasons which cannot be overcome are possibly needed to be overcome, and subsequently, if the retry number of the push task generated based on the subscription record is smaller than the first preset number of times, the subscription record is possible to cause generation failure due to some sporadic reasons, such as request timeout, the retry number of the push task is required to be executed again, and the retry number of the push task generated is not required to be repeated, and the reliability is improved due to the reasons that the reliability of the push task is failed, and the reliability is finally improved;
Whether the push task is successfully generated is judged, whether the number of the subscription records in the subscription table is consistent with the number of the push tasks in the push task table can be checked, if the number of the subscription records in the subscription table is inconsistent with the number of the push tasks in the push task table, the fact that the corresponding push tasks are generated by some subscription records fails is indicated, whether the subscription records are failed to generate the corresponding push tasks needs to be further confirmed, and then the push tasks are regenerated according to the confirmed subscription records.
In step 106, after generating a bill file according to the account identifier corresponding to the push task and at least one sub-account identifier associated with the account identifier, in an embodiment, it is determined whether the generation of the bill file according to the push task in the push task table is successful;
if the generation of the bill file fails, judging whether the retry number of the bill file generated based on the pushing task is smaller than a second preset number;
and if the number of times is smaller than the second preset number of times, generating the bill file again according to the pushing task, and adding 1 to the retry number of the generated bill file.
As shown in fig. 6, after the pushing task in the pushing task table generates the bill file, it is further required to determine whether the bill file is successfully generated, and generation failure may be caused by some reasons according to the pushing task in the pushing task table, so here, it is required to determine whether the bill file is successfully generated, if the bill file is successfully generated, the bill file is not required to be regenerated, then the bill file is pushed to a user and stored in a storage space corresponding to an account number, if the bill file is failed to be generated, then it is continuously determined whether the number of times of retries of the generated bill file based on the pushing task is less than the second preset number of times, if the number of times of retries of the generated bill file based on the pushing task is greater than or equal to the second preset number of times, it is indicated that the number of times of retries of the generated bill file based on the pushing task is excessive, there may be some reasons that cannot be overcome, then the bill file is not required to be regenerated, if the number of retries of the generated bill file based on the pushing task is less than the second preset number of times, then some reasons that the generated bill file is required to be manually checked, the number of times of retries of the generated bill file based on the pushing task is likely to be transmitted due to the fact that the temporary reasons such as the number of times of retries of the generated bill file is not exceeds the second preset number of times, if the number of retries of the generated bill file based on the pushing task is failed, and the reason that the number of the generated bill file is failed due to be most caused by the fact that the system is failed to be executed due to the fact is increased.
The pushing of the bill file may also fail, and after the bill file is pushed, whether the bill file is successfully pushed needs to be judged, if so, whether the number of retries of the pushing bill file of the bill file is smaller than the third preset number of times is judged, and if so, the bill file is pushed again.
When the generation of the pushing task fails according to the subscription record, the generation of the bill file fails according to the pushing task or the generation of the bill file fails and the corresponding retry times are greater than or equal to the corresponding preset times, the system can display the failed task list to a manual customer service or an operator, and the manual customer service or the operator can manually modify the retry times or other data corresponding to the failed tasks so that the failed tasks can be executed again, and the overall stability and the usability of the system are effectively improved.
An embodiment of the present disclosure provides a bill pushing device, as shown in fig. 7, including:
the acquisition module 10 is used for acquiring account identification and subscription content;
The judging module 20 is configured to judge whether the account has a right to subscribe to the subscription content according to the account identifier;
the judging module 20 is further configured to judge whether the account has an opened storage space if the account has permission to subscribe to the subscription content;
the computing module 30 is configured to generate a subscription record according to the account identifier and the subscription content and store the subscription record in a subscription record table if the account has opened a storage space;
The computing module 30 is further configured to generate a push task according to a subscription record in the subscription record table and store the push task in a push task table at least at one first preset time point;
The judging module 20 is further configured to judge, when at least one second preset time point corresponding to the first preset time point, whether an account identifier corresponding to a push task in the push task table is associated with at least one sub-account identifier;
And the pushing module 40 is configured to generate a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier, push the bill file to the user to whom the account belongs, and store the bill file in a storage space corresponding to the account if the account identifier is associated with the at least one sub-account identifier.
Wherein, the computing module 30 is further configured to generate a billing request according to the push task in the push task table;
The computing module 30 is further configured to split the bill request into a plurality of sub-bill requests;
The calculating module 30 is further configured to generate a plurality of sub-bill files according to the plurality of sub-bill requests, and combine the plurality of sub-bill files into a bill file;
The pushing module 40 is further configured to push the bill file to a user to which the account belongs, and store the bill file in a storage space corresponding to the account.
The judging module 20 is further configured to judge, when at least one first preset time point, whether a last push time corresponding to a subscription record in the subscription record table is the last first preset time point;
The judging module 20 is further configured to judge whether the retry number of the generated push task based on the subscription record is less than a first preset number of times if yes;
The computing module 30 is further configured to, if yes, assign the subscription record to a target port of the target machine to generate a push task and bind the subscription record with the port.
The judging module 20 is further configured to judge whether a subscription record corresponding to the push task is bound to the target port;
the judging module 20 is further configured to judge whether the retry number of the generated bill file based on the push task is less than a second preset number of times if yes;
the computing module 30 is further configured to, if yes, allocate the push task to the target port, and bind the push task with the target port.
The judging module 20 is further configured to judge whether the push task generated according to the subscription record is successful;
The judging module 20 is further configured to judge whether the retry number of the generated push task based on the subscription record is less than a first preset number if the generated push task fails;
the calculation module 30 is further configured to, if the number of times is smaller than the first preset number of times, generate a push task again according to the subscription record and add 1 to the retry number of the generated push task.
The judging module 20 is further configured to judge whether the bill file is successfully generated according to the pushing task in the pushing task table;
The judging module 20 is further configured to judge whether the retry number of the generated bill file based on the push task is less than a second preset number if the generation of the bill file fails;
the calculating module 30 is further configured to, if the number of times is smaller than the second preset number of times, re-generate the bill file according to the pushing task and add 1 to the retry number of the generated bill file.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
Fig. 8 illustrates a schematic block diagram of an example electronic device 300 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 8, the apparatus 300 includes a computing unit 301 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 302 or a computer program loaded from a storage unit 308 into a Random Access Memory (RAM) 303. In the RAM303, various programs and data required for the operation of the device 300 may also be stored. The computing unit 301, the ROM302, and the RAM303 are connected to each other by a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
Various components in device 300 are connected to I/O interface 305, including: an input unit 306 such as a keyboard, a mouse, etc.; an output unit 307 such as various types of displays, speakers, and the like; a storage unit 308 such as a magnetic disk, an optical disk, or the like; and a communication unit 309 such as a network card, modem, wireless communication transceiver, etc. The communication unit 309 allows the device 300 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 301 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 301 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 301 performs the various methods and processes described above, such as the bill pushing method. For example, in some embodiments, the bill pushing method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 308. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 300 via the ROM302 and/or the communication unit 309. When the computer program is loaded into RAM303 and executed by computing unit 301, one or more steps of the bill pushing method described above may be performed. Alternatively, in other embodiments, the computing unit 301 may be configured to perform the bill pushing method by any other suitable means (e.g. by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (10)
1. A bill pushing method, comprising:
Acquiring account identification and subscription content;
Judging whether the account has the authority of subscribing the subscription content according to the account identification;
If the account has the authority to subscribe the subscription content, judging whether the account has opened a storage space;
if the account has opened a storage space, generating a subscription record according to the account identification and subscription content and storing the subscription record in a subscription record table;
Generating a push task according to the subscription record in the subscription record table and storing the push task in a push task table when at least one first preset time point;
Judging whether an account identifier corresponding to a push task in the push task table is associated with at least one sub-account identifier or not when at least one second preset time point corresponding to a first preset time point is reached;
And if the account identifier is associated with at least one sub-account identifier, generating a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier, pushing the bill file to a user to which the account belongs, and storing the bill file in a storage space corresponding to the account.
2. The method of claim 1, wherein the generating a bill file according to the account identifier corresponding to the pushing task and at least one sub-account identifier associated with the account identifier, pushing the bill file to the user to which the account belongs and storing the bill file in a storage space corresponding to the account, includes:
Generating a bill request according to the pushing task in the pushing task list;
splitting the billing request into a plurality of sub-billing requests;
Generating a plurality of sub-bill files according to the plurality of sub-bill requests, and merging the plurality of sub-bill files into a bill file;
pushing the bill file to a user to which the account belongs and storing the bill file into a storage space corresponding to the account.
3. The method of claim 1, further comprising, prior to generating a push task from a subscription record in the subscription record table and storing in a push task table:
Judging whether the last push time corresponding to the subscription record in the subscription record table is the last first preset time point or not when at least one first preset time point is reached;
if yes, judging whether the retry times of the generated pushing task based on the subscription record are smaller than the first preset times;
if yes, the subscription record is distributed to a target port of the target machine to generate a push task, and the subscription record is bound with the port.
4. The method according to claim 3, before the generating the bill file according to the account identifier corresponding to the push task and at least one sub-account identifier associated with the account identifier, further comprising:
judging whether the subscription record corresponding to the push task is bound with the target port or not;
if yes, judging whether the retry number of the generated bill file based on the pushing task is smaller than a second preset number;
If yes, the push task is distributed to the target port, and the push task is bound with the target port.
5. The method of claim 1, further comprising, after generating a push task from a subscription record in the subscription record table:
judging whether the generation of the pushing task is successful or not according to the subscription record;
if the generation of the push task fails, judging whether the retry number of the generated push task based on the subscription record is smaller than a first preset number;
If the number of times is smaller than the first preset number of times, generating a push task again according to the subscription record, and adding 1 to the retry number of the generated push task.
6. The method according to claim 1, wherein after generating the bill file according to the account identifier corresponding to the push task and at least one sub-account identifier associated with the account identifier, the method further comprises:
judging whether the generation of the bill file is successful or not according to the pushing task in the pushing task list;
if the generation of the bill file fails, judging whether the retry number of the bill file generated based on the pushing task is smaller than a second preset number;
if the number of times is smaller than the second preset number of times, generating the bill file again according to the pushing task and adding 1 to the retry number of the generated bill file.
7. A bill pushing device, comprising:
the acquisition module is used for acquiring account identification and subscription content;
The judging module is used for judging whether the account has the authority of subscribing the subscription content according to the account identification;
The judging module is further used for judging whether the account has the storage space opened or not if the account has the authority to subscribe the subscription content;
the computing module is used for generating a subscription record according to the account identification and the subscription content and storing the subscription record in a subscription record table if the account has opened a storage space;
the computing module is further configured to generate a push task according to a subscription record in the subscription record table and store the push task in a push task table when at least one first preset time point;
The judging module is further configured to judge, when at least one second preset time point corresponding to the first preset time point, whether an account identifier corresponding to a push task in the push task table is associated with at least one sub-account identifier;
And the pushing module is used for generating a bill file according to the account identifier corresponding to the pushing task and the at least one sub-account identifier associated with the account identifier if the account identifier is associated with the at least one sub-account identifier, pushing the bill file to a user to which the account belongs and storing the bill file in a storage space corresponding to the account.
8. An electronic device, comprising:
at least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
9. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-6.
10. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111279495.2A CN114065277B (en) | 2021-10-29 | 2021-10-29 | Bill pushing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111279495.2A CN114065277B (en) | 2021-10-29 | 2021-10-29 | Bill pushing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114065277A CN114065277A (en) | 2022-02-18 |
| CN114065277B true CN114065277B (en) | 2024-07-16 |
Family
ID=80236401
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111279495.2A Active CN114065277B (en) | 2021-10-29 | 2021-10-29 | Bill pushing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114065277B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107071060A (en) * | 2017-05-27 | 2017-08-18 | 北京思特奇信息技术股份有限公司 | A kind of SFTP files transmitting method and system |
| CN108512851A (en) * | 2018-03-30 | 2018-09-07 | 掌阅科技股份有限公司 | Account processing method, electronic equipment and storage medium are read by family |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10476758B2 (en) * | 2013-07-11 | 2019-11-12 | Google Llc | Systems and methods for providing notifications of changes in a cloud-based file system |
| CN110100426B (en) * | 2017-09-18 | 2023-05-26 | 深圳市欢太科技有限公司 | Method and device for subscribing message, computer equipment and computer storage medium |
| CN108875387B (en) * | 2018-05-29 | 2019-12-10 | 平安科技（深圳）有限公司 | Data processing method, device, equipment and medium based on AD system |
| CN110020089A (en) * | 2018-08-20 | 2019-07-16 | 深圳壹账通智能科技有限公司 | Compound bill generation method, device, equipment and computer storage medium |
| CN111259053A (en) * | 2020-02-03 | 2020-06-09 | 中国银联股份有限公司 | Bill inquiry method and device |
| CN111325626B (en) * | 2020-02-21 | 2023-07-25 | 中国工商银行股份有限公司 | Account checking data pushing method and device |
-
2021
- 2021-10-29 CN CN202111279495.2A patent/CN114065277B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107071060A (en) * | 2017-05-27 | 2017-08-18 | 北京思特奇信息技术股份有限公司 | A kind of SFTP files transmitting method and system |
| CN108512851A (en) * | 2018-03-30 | 2018-09-07 | 掌阅科技股份有限公司 | Account processing method, electronic equipment and storage medium are read by family |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114065277A (en) | 2022-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102193502B1 (en) | Method and device for obtaining a payment threshold | |
| CN110888893A (en) | Order processing method based on micro-service e-commerce system | |
| CN112132674A (en) | Transaction processing method and device | |
| CN110706093A (en) | Accounting processing method and device | |
| CN112184240A (en) | Refund request processing method and device | |
| CN111161071A (en) | Data processing method, device, equipment and storage medium based on block chain | |
| CN110400139B (en) | Payment method, device and system based on public digital wallet | |
| CN106034148B (en) | Rapid information interaction method, local server, remote server and system | |
| CN114065277B (en) | Bill pushing method and device, electronic equipment and storage medium | |
| CN113297153A (en) | Data export method, device, equipment and storage medium | |
| WO2023088462A1 (en) | Method and apparatus for processing data, device, and storage medium | |
| EP4239979A1 (en) | Data download method and apparatus, electronic device, and readable storage medium | |
| CN107609852B (en) | Method and apparatus for processing payment requests | |
| CN113157911A (en) | Service verification method and device | |
| CN115454576A (en) | Virtual machine process management method and system and electronic equipment | |
| CN114581088A (en) | Aggregated payment method, device and system for SaaS (software as a service) system | |
| CN112884382A (en) | Resource quota management method, device, equipment and storage medium of cloud platform | |
| CN114722108A (en) | Customer service data processing method and device, electronic equipment and storage medium | |
| CN113918282A (en) | Database access method and device, electronic equipment and computer readable medium | |
| CN112101810A (en) | Risk event control method, device and system | |
| CN115250276A (en) | Distributed system and data processing method and device | |
| CN111402018A (en) | Method and system for reporting resource budget | |
| CN111861746A (en) | Method and device for processing transaction data | |
| CN112053125A (en) | Countersigning method and device, electronic equipment and computer readable storage medium | |
| CN111526184A (en) | Business auditing method and device |
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 |