CN111259053A - Bill inquiry method and device - Google Patents
Bill inquiry method and device Download PDFInfo
- Publication number
- CN111259053A CN111259053A CN202010078990.6A CN202010078990A CN111259053A CN 111259053 A CN111259053 A CN 111259053A CN 202010078990 A CN202010078990 A CN 202010078990A CN 111259053 A CN111259053 A CN 111259053A
- Authority
- CN
- China
- Prior art keywords
- account
- user
- storage system
- bill
- bill information
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention provides a method and a device for inquiring bills, wherein the method comprises the following steps: receiving a bill inquiry request of a user; according to the bill inquiry request, searching the bill information of each account of the user from a first storage system; sending the first bill information of the first account of the user inquired from the first storage system to the user; initiating an asynchronous query request to a bank system where a second account of the user is located, wherein the second account is an account of the user except the first account; and sending the second bill information of the second account obtained through the asynchronous query request to the user. By adopting the method, a plurality of accounts of the user can be managed simultaneously, the bill information existing in the first storage system is firstly provided for the user, and then the bill information acquired by asynchronous inquiry is provided for the user, so that the time for the user to inquire the bill information is shortened.
Description
Technical Field
The present application relates to the field of communications networks, and in particular, to a method and an apparatus for inquiring bills.
Background
With the rapid development of the network, the network technology is visible everywhere in the life and work of people, and the application of the network technology not only enriches the life of people, but also brings much convenience to the life of people; for example, most financial services can be directly processed by depending on the network, so that the manpower resource is greatly saved, the financial services can be quickly and accurately processed, and the accuracy and the real-time performance of financial service processing are improved.
Financial services include insurance, trust, risk investment, real-time investment and the like, and the services almost cannot be inquired and obtained without making a bill, taking a bank credit card as an example; some banks build systems by themselves in which a user can quickly query and display billing information of his bank credit card at the bank at the user side. Although this method can quickly obtain billing information for the user, it can only manage credit cards of a single bank for the user, and cannot manage credit cards of a plurality of banks centrally. Another APP capable of centrally managing bank credit cards includes a function of centrally managing a plurality of credit cards for users, but the speed of acquiring bills is slow, the users need to wait for use, and the time cost is high.
Therefore, there is a need for a method and an apparatus for inquiring bills, which are used to manage accounts in a centralized manner and quickly obtain bill information corresponding to each account.
Disclosure of Invention
The embodiment of the invention provides a method and a device for inquiring bills, which are used for managing accounts in a centralized manner and quickly acquiring bill information corresponding to each account.
In a first aspect, an embodiment of the present invention provides a method for inquiring a bill, where the method includes:
receiving a bill inquiry request of a user; according to the bill inquiry request, searching the bill information of each account of the user from a first storage system; sending the first bill information of the first account of the user inquired from the first storage system to the user; initiating an asynchronous query request to a bank system where a second account of the user is located, wherein the second account is an account of the user except the first account; and sending the second bill information of the second account obtained through the asynchronous query request to the user.
By adopting the method, the bill information of each account of the user in the first storage system is inquired by receiving the bill inquiry request of the user, the bill information searched in the first storage system is sent to the user side, if the bill information is not searched, an asynchronous inquiry request corresponding to the bill information account is initiated, and the bill information obtained by the asynchronous inquiry request is sent to the user side. By the method, multiple accounts of the user can be managed simultaneously, the bill information existing in the first storage system is firstly provided for the user, then the bill information acquired through asynchronous inquiry is provided for the user, and the waiting time for the user to inquire the bill information is reduced.
In one possible design, initiating an asynchronous query request to a banking system where the second account of the user is located includes: for each second account, creating an asynchronous query request of the second account and sending the asynchronous query request to a bank system where the second account is located; and storing the second bill information of the second account, which is acquired from the bank system where the second account is located, in the first storage system.
By adopting the method, the second bill information is stored in the first storage system, so that the second bill information of the second account can be rapidly provided when the subsequent user inquires the bill information.
In one possible design, sending second billing information of the second account obtained by the asynchronous query request to the user includes: and acquiring the second bill information from the first storage system in a polling mode and sending the second bill information to the user in a polling process.
By adopting the method, the second bill information of the second account obtained by the asynchronous query request can be obtained in time in a polling mode, and the second bill information is fed back to the user in time.
In one possible design, the method further includes: determining a third account satisfying the subscription requirement; the subscription requirement is preset by the user; storing third bill information of the third account acquired from the first storage system to a second storage system; generating a reminding message of the third account according to the third bill information acquired from the second storage system; and sending the reminding message to the user corresponding to the third account.
By adopting the method, the subscription requirement preset by the user is determined, the third bill information is obtained from the first storage system, the bill information is stored in the second storage system, the reminding message of the third account is sent, and the reminding message is sent to the user corresponding to the third account. By the method, the task of sending the reminding message of the third account can be decoupled into the second storage system, and the generation and sending of the reminding message are accelerated.
In one possible design, the method includes: the billing inquiry request is triggered after receiving the reminder message.
By adopting the method, the user inquires the bill information after receiving the reminding message, and the bill information is stored in the first storage system and the second storage system before the user receives the reminding message, so that the acquisition of the bill information of the user can be accelerated, and the waiting time for the user to acquire the bill information is reduced.
In one possible design, before storing the third billing information of the third account acquired from the first storage system to the second storage system, the method further includes: determining whether the first storage system stores the third billing information; if the third bill information is not stored, sending the asynchronous query request to a bank system where the third account is located; storing the third billing information obtained through the asynchronous query request to the first storage system.
By adopting the method, the third bill information is obtained from the first storage system according to the subscription requirement preset by the user, and if the third bill information does not exist in the first storage system, the asynchronous query request is initiated to obtain the third bill information and the third bill information is stored in the first storage system. Therefore, when the user checks the bill information again, the bill information can be obtained from the first storage system, and the bill information can be displayed for the user quickly.
In one possible design, before determining the third account that meets the subscription requirement, the method further includes:
storing the received subscription requirements of the third account to the second storage system; generating a subscription operation of the third account according to the subscription requirement acquired from the second storage system; writing the subscription operation in a third storage system.
By adopting the method, after the subscription requirement of the third account set by the user is received, the subscription requirement of the third account is stored in the second storage system. Therefore, the service layer is not required to provide the memory all the time, the subscription requirement corresponding to the third account is recorded, and the pressure of the service layer system can be relieved. And acquiring a subscription request of a third account from the second storage system, generating a subscription operation, and writing the subscription operation into the third storage system. The method and the device realize the decoupling of the subscription generation operation from the business process of acquiring the bill, accelerate the speed of acquiring the bill, and also can finish the subscription generation operation so as to ensure that the subscription generation operation is subsequently acquired and a reminding message is sent to the user.
In one possible design, determining a third account that satisfies the subscription requirement includes: and determining a third account meeting the subscription requirement through the third storage system in a distributed task mode.
By adopting the method, the third account of which the third storage system meets the subscription requirement is determined in a distributed task mode, the distributed task mode can separately store and manage the accounts of all the current users, so that elastic expansion and contraction can be realized, and when the access volume is increased or decreased, the service processing capacity can be improved and the service processing cost can be reduced by increasing or decreasing the number of servers.
In a second aspect, an embodiment of the present invention provides an apparatus for inquiring bills, where the apparatus includes:
the receiving module is used for receiving a bill inquiry request of a user;
the processing module is used for searching the bill information of each account of the user from a first storage system according to the bill inquiry request;
the sending module is used for sending the first bill information of the first account of the user inquired from the first storage system to the user;
the sending module is further configured to initiate an asynchronous query request to a banking system where a second account of the user is located, where the second account is an account of the user other than the first account;
the sending module is further configured to send second billing information of the second account, which is obtained through the asynchronous query request, to the user.
In one possible design, the sending module is specifically configured to: for each second account, creating an asynchronous query request of the second account and sending the asynchronous query request to a bank system where the second account is located; and storing the second bill information of the second account, which is acquired from the bank system where the second account is located, in the first storage system.
In one possible design, the sending module is specifically configured to: and acquiring the second bill information from the first storage system in a polling mode and sending the second bill information to the user in a polling process.
In one possible design, the processing module is further to:
determining a third account satisfying the subscription requirement; the subscription requirement is preset by the user;
storing third bill information of the third account acquired from the first storage system to a second storage system; generating a reminding message of the third account according to the third bill information acquired from the second storage system;
the sending module is further configured to send the reminding message to the user corresponding to the third account.
In one possible design, the receiving module is further configured to: the billing inquiry request is triggered after receiving the reminder message.
In one possible design, the processing module is further to: determining whether the first storage system stores the third billing information; if the third bill information is not stored, sending the asynchronous query request to a bank system where the third account is located; storing the third billing information obtained through the asynchronous query request to the first storage system.
In one possible design, the processing module is further to: storing the received subscription requirements of the third account to the second storage system; generating a subscription operation of the third account according to the subscription requirement acquired from the second storage system; writing the subscription operation in a third storage system.
In one possible design, comprising: and determining a third account meeting the subscription requirement through the third storage system in a distributed task mode.
In a third aspect, an embodiment of the present application further provides a computing device, including: a memory for storing program instructions; a processor for calling program instructions stored in said memory to execute the method as described in the various possible designs of the first aspect according to the obtained program.
In a fourth aspect, embodiments of the present application also provide a computer-readable non-transitory storage medium including computer-readable instructions which, when read and executed by a computer, cause the computer to perform the method as set forth in the various possible designs of the first aspect.
These and other implementations of the present application will be more readily understood from the following description of the embodiments.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic diagram of a bill query architecture according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a bill inquiry method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another bill inquiry method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a bill query architecture according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a bill inquiry method according to an embodiment of the present invention;
fig. 6 is a schematic flowchart of a bill inquiry method according to an embodiment of the present invention;
fig. 7 is a schematic device diagram of a bill inquiry method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, a service module 102 receives a bill query request of a user, searches for bill information corresponding to each account of the user in a first storage system, returns the found bill information of the account to a user side, and sends the bill information corresponding to the account that is not found to the user side, where an asynchronous query request is initiated by a query module 101, and the service module 102 sends the bill information corresponding to the account obtained by receiving the asynchronous query request to the user.
Based on this, an embodiment of the present application provides a method flow for inquiring a bill, as shown in fig. 2, including:
here, the billing inquiry request is an inquiry request for billing information for at least one account of the user.
here, the first storage system may be a Kafka, Redis, or the like storage system. And searching the bill information of each account of the user in the first storage system according to the bill inquiry request.
For example, the user has A, B, C, D credit card, and after initiating the bill query request, the user queries A, B, C, D the first storage system for the bill information corresponding to the credit card.
here, the first account is an account for which the bill information is found in the first storage system, the first bill information is the bill information corresponding to the first account, and the found bill information of the first account is sent back to the user side.
In the above example, if the billing information of the a credit card and the B credit card is found in the first storage system, the billing information of the a credit card and the billing information of the B credit card are transmitted to the user.
here, the second account is an account for which the billing information is not found in the first storage system, and the asynchronous query request is a billing information acquisition request initiated to a banking system corresponding to each account.
In the last example, if the billing information of the C credit card and the D credit card is not found in the first storage system, the asynchronous query request is respectively initiated to the banking system corresponding to the C credit card and the banking system corresponding to the D credit card.
The step of initiating an asynchronous query request to a bank system where the second account of the user is located includes: for each second account, creating an asynchronous query request of the second account and sending the asynchronous query request to a bank system where the second account is located; and storing the second bill information of the second account, which is acquired from the bank system where the second account is located, in the first storage system.
Here, the second billing information is billing information of the second account, and for each second account, an asynchronous query request for the second account is created and sent to a bank system corresponding to the second account, the billing information of the second account returned by the bank system is acquired, and the billing information of the second account is stored in the first storage system.
In the last example, an asynchronous query request is initiated to a banking system corresponding to the C credit card and a banking system corresponding to the D credit card, the bill information of the C credit card returned by the banking system corresponding to the C credit card is obtained, and the bill information of the C credit card is stored in the first storage system; and acquiring the bill information of the D credit card returned by the bank system corresponding to the D credit card, and storing the bill information of the D credit card in the first storage system.
Here, the bill information corresponding to the second account, which is obtained from the banking system corresponding to the second account by sending the asynchronous query request, is sent to the user.
Wherein sending second billing information of the second account obtained by the asynchronous query request to the user comprises: and acquiring the second bill information from the first storage system in a polling mode and sending the second bill information to the user in a polling process.
Here, a polling mechanism is set to search the first storage system for the bill information corresponding to the second account, and if the bill information corresponding to the second account exists, the bill information is sent to the user. That is to say, if the time for the banking system corresponding to each second account to return the second bill information is different, the time for each second account to store the second bill information in the first storage system is different before and after, and the polling mechanism can realize that the second bill information is sent to the user every time one second bill information is stored.
In the last example, if the polling mechanism searches the first storage system once every 200ms, the reaction time of the bank system corresponding to the credit card C is 400ms, and the reaction time of the bank system corresponding to the credit card D is 800 ms; initiating an asynchronous query request to a bank system corresponding to the credit card C and a bank system corresponding to the credit card D, acquiring the bill information of the credit card C returned by the bank system corresponding to the credit card C in 400ms, storing the bill information of the credit card C in a first storage system, searching the first storage system by a polling mechanism to acquire the bill information of the credit card C firstly, and sending the bill information of the credit card C to a user; and acquiring the bill information of the D credit card returned by the bank system corresponding to the D credit card in 800ms, storing the bill information of the D credit card in a first storage system, searching the bill information of the D credit card acquired by the first storage system through a polling mechanism, and sending the bill information of the D credit card to a user.
By adopting the method, the bill information of each account of the user in the first storage system is inquired by receiving the bill inquiry request of the user, the bill information searched in the first storage system is sent to the user side, if the bill information is not searched, an asynchronous inquiry request corresponding to the bill information account is initiated, and the bill information obtained by the asynchronous inquiry request is sent to the user side. By the method, a plurality of accounts of the user can be managed simultaneously, the bill information existing in the first storage system is firstly provided for the user, then the bill information which originally does not exist in the first storage system and is acquired by asynchronous inquiry is provided for the user, and the waiting time of the user for inquiring the bill information is reduced.
Based on the above flow, an embodiment of the present application provides a method flow for a bill query, as shown in fig. 3, including:
here, the subscription request may be a request corresponding to a preset operation, such as a repayment reminding request for setting a credit card, a bill pushing request for setting a fixed date for setting a bank card, and the like. The third account is an account meeting the subscription requirement, for example, if the current day is 2019, month 2 and 28, the account with the repayment reminding date of 2019, month 2 and 28 is set as the third account in the subscription requirement.
Before determining the third account satisfying the subscription requirement, the method further includes: storing the received subscription requirements of the third account to the second storage system; generating a subscription operation of the third account according to the subscription requirement acquired from the second storage system; writing the subscription operation in a third storage system.
Here, the second storage system may be a Kafka, Redis, or the like storage system. The third storage system is a database or storage system that stores subscription operations. Here, there may be a plurality of second storage systems and third storage systems, and thus a small number or more of second storage systems and/or third storage systems may be provided according to the amount of data. The subscription operation is a corresponding operation set according to a subscription requirement of the user, for example, the subscription operation corresponding to the subscription requirement setting of a repayment reminding request corresponding to the credit card and the setting of a bill pushing request with a fixed date corresponding to the bank card is a repayment reminding corresponding to the credit card and a bill pushing with a fixed date corresponding to the bank card. Before determining a third account meeting the subscription requirement, receiving the subscription requirement of the third account, storing the subscription requirement in a second storage system, acquiring the subscription requirement of the third account from the second storage system to generate a subscription operation of the third account, and writing the subscription operation of the third account into the third storage system. For example, the user sends a request for setting date of 28 th in 2 th and 2019 th as a payment reminding date, the request is cached in the second storage system, the request for setting date of 28 th in 2 th and 2019 th as the payment reminding date is obtained from the second storage system, a subscription operation of sending a reminding message in 28 th in 2 th and 2019 th is generated according to the request, and the subscription operation of sending the reminding message in 28 th in 2 th and 2019 th is stored in the third storage system. Thus, when day 28/2/2019, it is determined that the third account needs to send a payment reminder.
here, the third billing information is billing information corresponding to the third account. And after determining a third account meeting the subscription requirement, searching third bill information of the third account from the first storage system, and storing the third bill information in the second storage system. In the last example, when 28 days 2 and 9 in 2019, it is determined that the third account needs to send a repayment reminder, the third billing information of the third account is found from the first storage system, and the third billing information is stored in the second storage system.
Before storing the third bill information of the third account acquired from the first storage system to the second storage system, the method further includes: determining whether the first storage system stores the third billing information; if the third bill information is not stored, sending the asynchronous query request to a bank system where the third account is located; storing the third billing information obtained through the asynchronous query request to the first storage system. That is to say, after the third account meeting the subscription requirement is determined, when the third bill information of the third account is not found from the first storage system, the asynchronous query request is sent to the bank system where the third account is located, the third bill information is stored in the first storage system after the third bill information corresponding to the asynchronous query request is received each time, then the third bill information of the third account acquired from the first storage system is stored in the second storage system, or the third bill information is stored in the second storage system while the third bill information is stored in the first storage system.
here, the reminding message of the third account may be a payment reminding of a credit card, a bill push of a bank card, a bill push of a game card, and the like.
And step 304, sending the reminding message to the user corresponding to the third account.
Here, the reminding message is sent to the user corresponding to the third account.
In the method, the third account meeting the subscription requirement may be determined by the third storage system in a distributed task manner.
That is, there may be a plurality of third storage systems, each third storage system stores the subscription operation of the account and the corresponding account basic information, each third storage system corresponds to a subsystem, and the subsystem may be used to determine a third account that meets the subscription requirement. Therefore, each subsystem corresponds to one third storage system, when the subscription operation of the account in the third storage system and the corresponding basic information of the account are excessive, pressure is applied to the server processing work, so that the server processing work is slowed down, the subsystems and the corresponding third storage systems can be added, and the subsystems and the corresponding third storage systems are placed on another server, so that the speed of the server processing work can be increased.
Wherein the bill inquiry request sent by the user is triggered after receiving the reminding message.
Here, after receiving the reminding message, the user can click the reminding message to send out a bill inquiry request, obtain the first bill information of the first account from the first storage system and send the first bill information to the user, so that the process of obtaining the bill information by going to a bank system is reduced, and the bill information can be rapidly displayed to the user.
By adopting the method, the subscription requirement preset by the user is determined, the third bill information is obtained from the first storage system, the bill information is stored in the second storage system, the reminding message of the third account is sent, and the reminding message is sent to the user corresponding to the third account. By the method, the task of sending the reminding message of the third account can be decoupled into the second storage system, so that the working pressure of the third storage system and the corresponding subsystem is relieved, and the generation and the sending of the reminding message are accelerated.
Based on the method flows in fig. 2 and fig. 3, an embodiment of the present application provides yet another architecture diagram for a bill query, as shown in fig. 4, including:
when a user inquires a bill at a user side, a bill inquiry request is sent to a service layer 401, after receiving the bill inquiry request, the service layer 401 acquires bill information corresponding to each account of the user from a first storage system (such as Redis)402, returns the acquired bill information to the user, and initiates an asynchronous bill inquiry request to an asynchronous bill inquiry service 403 for the bill information which is not acquired; the asynchronous bill query service 403 creates an asynchronous query request corresponding to an account for which bill information is not acquired, the asynchronous bill query service 403 sends the asynchronous query request corresponding to the account to the bank interface 404 corresponding to the account, the asynchronous bill query service 403 receives the bill information of the account returned by the bank interface 404, and sends the bill information of the account to the service layer 401, and the bill information of the account is stored by the Redis 402; the polling mechanism of the service layer 401 obtains the billing information of the account and sends the billing information to the user.
After the user sets a subscription requirement at the user side, the service layer 401 receives the subscription requirement and stores the received subscription requirement in the third storage system (e.g. Kafka) 405; the database operation and reminding service 406 acquires the subscription requirement from Kafka405, generates a subscription operation, and stores the subscription operation of the user in an account DB database where the user account is located in the distribution system 407; the distribution system 407 performs a subscription operation in a distributed task manner, including a plurality of task units jobi for performing the subscription operation; specifically, the job determines, according to each subscription operation, that the account corresponding to the user is a third account, the distribution system 407 queries the billing information of the third account from the Redis402, and sends the billing information of the third account to the Kafka 405; the database operation and reminder service 406 obtains the billing information of the third account from Kafka405 to generate a reminder message and sends the reminder message to the user. If the distribution system 407 does not query the billing information of the third account from the Redis402, an asynchronous billing query request is initiated to the asynchronous billing query service 403; the asynchronous bill query service 403 creates an asynchronous query request corresponding to the third account, the asynchronous bill query service 403 sends the asynchronous query request corresponding to the third account to the bank interface 404 corresponding to the third account, the asynchronous bill query service 403 receives the bill information of the third account returned by the bank interface 404, and sends the bill information of the third account to the service layer 401, which is stored by the Redis402 and simultaneously sent to the Kafka 405; the database operation and alert service 406 obtains the billing information of the third account from Kafka405, generates an alert message, and sends the alert message to the user.
Based on this, an embodiment of the present application provides a method flow for bill query, as shown in fig. 5, including:
step 501, a user queries a bill at a user side, and correspondingly sends a bill query request to a service layer.
Step 502, after receiving the bill inquiry request, the service layer inquires whether the Redis contains the bill information of each account of the user, and the user bill inquiry request is set to inquire A, B, C, D the bill information corresponding to the credit card.
Step 503, if the billing information of the credit card a is inquired in the Redis, returning to the user.
Step 504, after the service layer receives the bill query request, if the bill information of the credit card B, C, D is not queried in the Redis, the service layer initiates a bill query request to the asynchronous bill query service.
And step 505, after receiving the bill query request sent by the service layer, the asynchronous bill query service creates a bill information request for asynchronously querying the credit card B and sends the bill information request to the bank interface.
Step 506, create a bill information request for asynchronously querying credit card C and send it to the bank interface.
Step 507, creating a bill information request of the asynchronous inquiry credit card D and sending the bill information request to the bank interface.
Step 508, the bank interface returns the bill information of the credit card B according to the bill information request of the asynchronous inquiry credit card B.
Step 509, the asynchronous billing inquiry service writes the billing information for credit card B into Redis.
At step 510, the user terminal polls the user's credit card B, C, D for billing information.
Step 511, the service layer polls the user's credit card B, C, D for billing information in Redis.
Step 512, obtaining the bill information of the credit card B in Redis.
Step 513, sending the bill information of the credit card B to the user.
Step 514, the bank interface returns the billing information of the credit card C according to the asynchronous inquiry of the billing information request of the credit card C.
Step 515, the asynchronous billing inquiry service writes the billing information for credit card C into Redis.
At step 516, the user terminal polls the user's credit card C, D for billing information.
Step 517, the service layer polls billing information of the user's credit card C, D in Redis.
Step 518, obtaining billing information for credit card C in Redis.
Step 519, the billing information of the credit card C is sent to the user.
Step 520, the bank interface returns the bill information of the credit card D according to the bill information request of the asynchronous inquiry credit card D.
Step 521, the asynchronous billing inquiry service writes the billing information of the credit card D into Redis.
The user terminal polls the billing information of the user's credit card D, step 522.
Step 523, the service layer polls the billing information of the user's credit card D in Redis.
Step 524, obtaining billing information of the credit card D in Redis.
Step 525, the billing information of the credit card D is sent to the user.
Based on the architecture of fig. 4, an embodiment of the present application provides a method flow of a bill query, as shown in fig. 6, including:
step 601, the job polls its corresponding account DB database to determine A, B, C that the credit card is the third account, that is, A, B, C that the credit card needs to obtain its corresponding billing information.
Step 602, jobs inquires A, B, C the bill information of the credit card from Redis.
Step 603, the job acquires the bill information of the A credit card, and does not acquire the bill information of the B, C credit card. joba writes the billing information for the a credit card into Kafka.
Step 604, the database operation and reminder service obtains billing information for the A credit card from Kafka and generates a reminder message.
Step 605, the database operation and reminder service sends the reminder message of the A credit card to the user.
Step 606, joba sends an asynchronous query credit card B, C billing information request to the asynchronous billing query service.
Step 607, the asynchronous bill inquiry service receives the asynchronous inquiry credit card B, C bill information request, creates a request for asynchronous inquiry of the bill information of credit card B and sends it to the bank interface.
Step 608, the asynchronous bill inquiry service creates a request for asynchronous inquiry of the bill information for credit card C and sends it to the bank interface.
Step 609, the bank interface returns the billing information for credit card B.
Step 610, the asynchronous billing inquiry service writes the billing information for credit card B into Redis.
Step 611, the asynchronous billing inquiry service writes the billing information for credit card B into Kafka.
Step 612, the database operation and reminder service obtains the billing information of the credit card B and generates a reminder message.
Step 613, the database operation and reminder service sends the reminder message to the user.
Step 614, the bank interface returns the billing information for credit card C.
Step 615, the asynchronous billing inquiry service writes the billing information of the credit card C into Redis.
Step 616, the asynchronous billing inquiry service writes the billing information for credit card C into Kafka.
Step 617, the database operation and reminder service obtains the billing information of the credit card C and generates a reminder message.
Step 618, the database operations and reminder service sends the reminder message to the user.
It should be noted here that the order of the steps in the flowcharts shown in fig. 5 and fig. 6 is not exclusive, and step 503 and step 504 in fig. 5 may be performed simultaneously, or step 504 may be performed before step 503. Step 604 and step 606 in fig. 6 may be performed simultaneously, or step 606 may be performed before step 604.
Based on the same concept, an embodiment of the present invention provides a device for inquiring bills, and fig. 7 is a schematic diagram of the device for inquiring bills provided by the embodiment of the present application, as shown in fig. 7, including:
a receiving module 701, configured to receive a bill query request of a user;
a processing module 702, configured to search, according to the bill query request, bill information of each account of the user from a first storage system;
a sending module 703, configured to send the first billing information of the first account of the user, which is queried from the first storage system, to the user;
the sending module 703 is further configured to initiate an asynchronous query request to a banking system where a second account of the user is located, where the second account is an account of each account of the user other than the first account;
the sending module 703 is further configured to send the second billing information of the second account obtained through the asynchronous query request to the user.
In one possible design, the sending module 703 is specifically configured to: for each second account, creating an asynchronous query request of the second account and sending the asynchronous query request to a bank system where the second account is located; and storing the second bill information of the second account, which is acquired from the bank system where the second account is located, in the first storage system.
In one possible design, the sending module 703 is specifically configured to: and acquiring the second bill information from the first storage system in a polling mode and sending the second bill information to the user in a polling process.
In one possible design, the processing module 702 is further configured to:
determining a third account satisfying the subscription requirement; the subscription requirement is preset by the user; storing third bill information of the third account acquired from the first storage system to a second storage system; generating a reminding message of the third account according to the third bill information acquired from the second storage system;
the sending module 703 is further configured to send the prompting message to the user corresponding to the third account.
In one possible design, the receiving module 701 is further configured to: the billing inquiry request is triggered after receiving the reminder message.
In one possible design, the processing module 702 is further configured to: determining whether the first storage system stores the third billing information; if the third bill information is not stored, sending the asynchronous query request to a bank system where the third account is located; storing the third billing information obtained through the asynchronous query request to the first storage system.
In one possible design, the processing module 702 is further configured to: storing the received subscription requirements of the third account to the second storage system; generating a subscription operation of the third account according to the subscription requirement acquired from the second storage system; writing the subscription operation in a third storage system.
In one possible design, comprising: and determining a third account meeting the subscription requirement through the third storage system in a distributed task mode.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. 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.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (11)
1. A method of billing inquiry, comprising:
receiving a bill inquiry request of a user;
according to the bill inquiry request, searching the bill information of each account of the user from a first storage system;
sending the first bill information of the first account of the user inquired from the first storage system to the user;
initiating an asynchronous query request to a bank system where a second account of the user is located, wherein the second account is an account of the user except the first account;
and sending the second bill information of the second account obtained through the asynchronous query request to the user.
2. The method of claim 1, wherein initiating an asynchronous query request to a banking system in which the second account of the user is located comprises:
for each second account, creating an asynchronous query request of the second account and sending the asynchronous query request to a bank system where the second account is located;
and storing the second bill information of the second account, which is acquired from the bank system where the second account is located, in the first storage system.
3. The method of claim 1, wherein sending second billing information for the second account obtained by the asynchronous query request to the user comprises:
and acquiring the second bill information from the first storage system in a polling mode and sending the second bill information to the user in a polling process.
4. The method of claim 1, wherein the method further comprises:
determining a third account satisfying the subscription requirement; the subscription requirement is preset by the user;
storing third bill information of the third account acquired from the first storage system to a second storage system;
generating a reminding message of the third account according to the third bill information acquired from the second storage system;
and sending the reminding message to the user corresponding to the third account.
5. The method of claim 4, wherein the method comprises:
the billing inquiry request is triggered after receiving the reminder message.
6. The method of claim 4, wherein prior to storing the third billing information for the third account obtained from the first storage system to the second storage system, further comprising:
determining whether the first storage system stores the third billing information;
if the third bill information is not stored, sending the asynchronous query request to a bank system where the third account is located;
storing the third billing information obtained through the asynchronous query request to the first storage system.
7. The method of claim 4, wherein prior to determining a third account that satisfies subscription requirements, further comprising:
storing the received subscription requirements of the third account to the second storage system;
generating a subscription operation of the third account according to the subscription requirement acquired from the second storage system;
writing the subscription operation in a third storage system.
8. The method of claim 7, wherein determining a third account that satisfies subscription requirements comprises:
and determining a third account meeting the subscription requirement through the third storage system in a distributed task mode.
9. An apparatus for billing inquiry, the apparatus comprising:
the receiving module is used for receiving a bill inquiry request of a user;
the processing module is used for searching the bill information of each account of the user from a first storage system according to the bill inquiry request;
the sending module is used for sending the first bill information of the first account of the user inquired from the first storage system to the user;
the sending module is further configured to initiate an asynchronous query request to a banking system where a second account of the user is located, where the second account is an account of the user other than the first account;
the sending module is further configured to send second billing information of the second account, which is obtained through the asynchronous query request, to the user.
10. A computing device, comprising:
a memory for storing program instructions;
a processor for calling program instructions stored in said memory to execute the method of any one of claims 1 to 8 in accordance with the obtained program.
11. A computer-readable non-transitory storage medium including computer-readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010078990.6A CN111259053A (en) | 2020-02-03 | 2020-02-03 | Bill inquiry method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010078990.6A CN111259053A (en) | 2020-02-03 | 2020-02-03 | Bill inquiry method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111259053A true CN111259053A (en) | 2020-06-09 |
Family
ID=70952637
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010078990.6A Pending CN111259053A (en) | 2020-02-03 | 2020-02-03 | Bill inquiry method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111259053A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114065277A (en) * | 2021-10-29 | 2022-02-18 | 北京百度网讯科技有限公司 | Bill pushing method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006323519A (en) * | 2005-05-17 | 2006-11-30 | Ntt Comware Corp | Demand storage system, demand storage device, method, and computer program |
| CN108345693A (en) * | 2018-03-16 | 2018-07-31 | 中国银行股份有限公司 | A kind of document handling method and device |
| CN108960790A (en) * | 2017-05-23 | 2018-12-07 | 阿里巴巴集团控股有限公司 | A kind of processing method, device, server and the system of bill business |
| CN109711980A (en) * | 2018-12-27 | 2019-05-03 | 中国建设银行股份有限公司 | Reconciliation form processing method, device, storage medium and system |
| CN110020089A (en) * | 2018-08-20 | 2019-07-16 | 深圳壹账通智能科技有限公司 | Compound bill generation method, device, equipment and computer storage medium |
| US20190244186A1 (en) * | 2017-03-10 | 2019-08-08 | Tencent Technology (Shenzhen) Company Limited | Electronic bill management method, apparatus, and storage medium |
| CN110321461A (en) * | 2019-05-24 | 2019-10-11 | 平安银行股份有限公司 | Bill processing method, system, computer equipment and storage medium |
| CN110443558A (en) * | 2018-05-04 | 2019-11-12 | 腾讯科技（深圳）有限公司 | A kind of method, apparatus and equipment of bill processing |
-
2020
- 2020-02-03 CN CN202010078990.6A patent/CN111259053A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006323519A (en) * | 2005-05-17 | 2006-11-30 | Ntt Comware Corp | Demand storage system, demand storage device, method, and computer program |
| US20190244186A1 (en) * | 2017-03-10 | 2019-08-08 | Tencent Technology (Shenzhen) Company Limited | Electronic bill management method, apparatus, and storage medium |
| CN108960790A (en) * | 2017-05-23 | 2018-12-07 | 阿里巴巴集团控股有限公司 | A kind of processing method, device, server and the system of bill business |
| CN108345693A (en) * | 2018-03-16 | 2018-07-31 | 中国银行股份有限公司 | A kind of document handling method and device |
| CN110443558A (en) * | 2018-05-04 | 2019-11-12 | 腾讯科技（深圳）有限公司 | A kind of method, apparatus and equipment of bill processing |
| CN110020089A (en) * | 2018-08-20 | 2019-07-16 | 深圳壹账通智能科技有限公司 | Compound bill generation method, device, equipment and computer storage medium |
| CN109711980A (en) * | 2018-12-27 | 2019-05-03 | 中国建设银行股份有限公司 | Reconciliation form processing method, device, storage medium and system |
| CN110321461A (en) * | 2019-05-24 | 2019-10-11 | 平安银行股份有限公司 | Bill processing method, system, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114065277A (en) * | 2021-10-29 | 2022-02-18 | 北京百度网讯科技有限公司 | Bill pushing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108446975B (en) | Quota management method and device | |
| CN111652096B (en) | Face recognition method, device and system based on block chain | |
| CN109241067A (en) | transaction data management method and device | |
| CN110659971B (en) | Transaction data processing method and device | |
| US11531984B2 (en) | Method and device facilitating expansion of primary payment instruments | |
| CN111259053A (en) | Bill inquiry method and device | |
| EP4264472A1 (en) | Systems and methods for hard deletion of data across systems | |
| CN107451301B (en) | Processing method, device, equipment and storage medium for real-time delivery bill mail | |
| CN110782310B (en) | Method, device and system for asynchronously acquiring user attribute information from third-party platform | |
| CN115658753A (en) | Method and device for inquiring electronic receipt and related equipment | |
| CN111489212B (en) | Order billing method, device, equipment and medium based on big data | |
| CN109447777B (en) | Financial data processing method and device, electronic equipment and readable medium | |
| CN113177843A (en) | Cross-bank loan service processing method and device based on block chain | |
| CN110930206A (en) | Invoice matching method and device and storage medium | |
| CN113055401B (en) | Enterprise business authorization processing method and device | |
| CN111061573A (en) | Resource transfer method, device, electronic equipment and storage medium | |
| CN111918264B (en) | Service menu display method and device | |
| CN113971007B (en) | Information processing method, device, electronic equipment and medium | |
| CN112446783B (en) | Method and device for displaying transaction data | |
| CN106815289B (en) | Data storage method and device in transaction processing system | |
| CN113986984A (en) | Financial electronic bill management system and method | |
| CN117437002A (en) | Service carding method, device, computer equipment and storage medium | |
| CN117078392A (en) | Method for determining credit limit, credit server, electronic equipment and medium | |
| CN117035855A (en) | Resource management method, apparatus, device, storage medium, and program product | |
| CN115018494A (en) | Water fee recharging method and device, storage medium and electronic equipment |
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 |