WO2020047840A1 - Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal - Google Patents

Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal Download PDF

Info

Publication number
WO2020047840A1
WO2020047840A1 PCT/CN2018/104602 CN2018104602W WO2020047840A1 WO 2020047840 A1 WO2020047840 A1 WO 2020047840A1 CN 2018104602 W CN2018104602 W CN 2018104602W WO 2020047840 A1 WO2020047840 A1 WO 2020047840A1
Authority
WO
WIPO (PCT)
Prior art keywords
transactions
user
page
bill
query
Prior art date
Application number
PCT/CN2018/104602
Other languages
English (en)
Chinese (zh)
Inventor
周诗松
姚伟
Original Assignee
威富通科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 威富通科技有限公司 filed Critical 威富通科技有限公司
Priority to PCT/CN2018/104602 priority Critical patent/WO2020047840A1/fr
Priority to CN201880001279.1A priority patent/CN109313642B/zh
Publication of WO2020047840A1 publication Critical patent/WO2020047840A1/fr

Links

Classifications

    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction

Definitions

  • the present application belongs to the technical field of data query, and particularly relates to a billing information buffering method, a billing information querying method, and a terminal device.
  • the transaction information is stored in the billing database.
  • the billing database When the bill is queried, all the transaction information in the billing database is summarized, and then the page information is displayed and displayed in real time.
  • the billing database caches transaction information, it simply sorts the cache based on the time of the transaction or the amount of the transaction.
  • querying the bill it directly accesses all the transaction information in the billing database, which puts great pressure on the billing database and even causes the query service to fail to complete. A large number of concurrent queries may cause the system to crash.
  • embodiments of the present application provide a method for billing information caching, a method for querying billing information, and a terminal device, so as to solve the huge pressure on the billing database when the billing query in the prior art is caused.
  • a first aspect of the embodiments of the present application provides a method for buffering bill information, including:
  • the day-end data of the preset day closest to the query day is obtained from the preset day-end data table according to the identity of the user, and according to the acquired Day-end data and the preset number of transactions per page, pagination of bills for the preset day's transactions closest to the query day of the user, determining the transaction time information of each page of the bill based on the results of the paging, and dividing the paged results with The transaction time information of each page of bills is stored in the cache, wherein a piece of daily settlement data includes the number of transactions per day of the user.
  • a second aspect of the embodiments of the present application provides a bill query method based on the bill information cache method of the foregoing embodiment, including:
  • a third aspect of the embodiments of the present application provides a billing information buffering device, including:
  • a request query module is used to query whether there is data in the cache when a bill query request sent by a user terminal is received;
  • a transaction determining module configured to obtain, if there is no data in the cache, a user querying the number of transactions on the day, and determining whether the number of transactions reaches a preset number of transactions;
  • An information buffer module configured to: if the number of transactions reaches the preset number of transactions, perform pagination of bills on the transaction of the user's query on the basis of the number of transactions and the preset number of transactions per page, and The result determines the transaction time information of each page of the bill, and stores the paged result and the transaction time information of each page of the bill into the cache;
  • the information caching module is further configured to: if the number of transactions does not reach the preset number of transactions, obtain a date of a preset day closest to the query day from the preset day-end data table according to the identity of the user; Settle the data, and based on the obtained daily settlement data and the preset number of transactions per page, perform billing pagination on the preset day's transactions closest to the query day of the user, and determine the transaction time of each page of bills based on the paged results Information, and store the paged results and transaction time information of each page of bills into the cache, where a day-end data includes the number of transactions per day of the user.
  • a fourth aspect of the embodiments of the present application provides a bill query device based on the bill information cache device of the foregoing embodiment, including:
  • a time determination module is used to determine the time span of each page of the user's transaction according to the paged results in the cache and the transaction time information of each page of the bill when the bill query request sent by the user is received;
  • a data acquisition module configured to acquire daily settlement data of the user from a preset daily settlement data table according to a time span of the bill of each page;
  • the flow query module is configured to query the flow data of each page corresponding to the user and the date on which the flow of each page is located according to the daily settlement data of the user.
  • a fifth aspect of the embodiments of the present application provides a terminal device including a memory, a processor, and a computer program stored in the memory and executable on the processor.
  • the processor executes the computer program, Implement the steps of the billing information caching method as described above.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the billing information caching method described above are implemented.
  • the client when the client sends a bill query request, it first queries whether there is data in the cache. If there is no data in the cache, it is determined whether the number of transactions on the user ’s query day reaches the preset number of transactions.
  • the number of transactions and the preset number of transactions per page paginate the transactions and determine the transaction time information of each page of the bill, and store the paged results and the transaction time information of each page of the bill into the cache; if it does not reach, obtain the nearest Set the day-to-day data, perform billing based on the day-to-day data and the preset number of transactions per page, and determine the transaction time information of each page of the bill.
  • the paged results and transaction time information of each page of the bill are stored in the cache.
  • the number of transactions is first cached on the billing information.
  • the time span of the user's transaction bill is determined based on the data in the cache, and the user's billing data is further queried based on the time span. To ensure the successful completion of the query service, which improves the query speed. A large amount of time to avoid system crashes.
  • FIG. 1 is a schematic flowchart of an implementation of a billing information caching method provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of the implementation of step S103 in FIG. 1;
  • FIG. 3 is a schematic flowchart of an implementation of a bill query method according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a billing information buffering device provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a bill inquiry device according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • an angle trigger of a terminal is used as an example for description.
  • the terminal may be a mobile terminal such as a smart phone or a tablet computer.
  • the processing process of the terminal may include the following steps:
  • Step S101 when receiving a bill query request sent by a user terminal, query whether there is data in the cache.
  • the data refers to a paged result and transaction time information of each page of the bill, which are obtained according to the number of transactions on the day of the user's query or the day-end data of a preset day closest to the day of the query.
  • the terminal when the user terminal sends a bill query request, the terminal first queries whether there is user data in the cache. If there is data, it directly obtains the total transaction information of the user's query on the basis of the data in the cache and the user's identity. , Or directly obtain the day-end data of the preset day closest to the query day in the preset day-end data table based on the data in the cache and the user ’s identity, and display the total transaction information for the day or the day-end data of the preset day In the query bill, for the current user to view, the query speed is improved.
  • step S102 if there is no data in the cache, the user queries the number of transactions for the current day, and determines whether the number of transactions reaches the preset number of transactions.
  • the determination of whether the number of transactions reaches the preset number of transactions is to first determine whether the user queries whether there is a transaction on the day, and if there is a transaction, the current bill query conditions are met, and according to the number of transactions and The preset number of transactions per page performs pagination of the bills on the day of the user's query. If there is no transaction, it means that the number of transactions on the day of the query does not meet the current bill query conditions. Get the day-end data of the preset day closest to the query day in the end-data table.
  • the client sends a bill query request on August 20, and there is no data in the cache, then the user's transaction number on August 20 is obtained, the transaction number is 6 and the preset transaction number is 2 transactions, if the number of transactions reaches the preset number of transactions, billing pagination of transactions on the day of the user's query is performed according to the number of transactions and the preset number of transactions per page.
  • the client sends a bill query request on August 20, and there is no data in the cache, then the transaction number of the user on August 20 is obtained.
  • the transaction number is 2 and the preset transaction number is 5, if the number of transactions does not reach the preset number of transactions, the day-end data of the preset day closest to the query day is obtained from the preset day-end data table according to the identity of the user, for example, from Get the day-end data in the preset day-end data table for the 8 days closest to the query day.
  • step S103 if the number of transactions reaches the preset number of transactions, then according to the number of transactions and the preset number of transactions per page, perform billing pagination on the transactions of the user's query day, and determine each Page transaction time information, and paged results and transaction time information of each page bill are stored in the cache.
  • the paged results and transaction time information of each page of bills are stored in the cache, so that when a user initiates a bill query request again, he can directly obtain the data in the cache (paged results and transaction time information of each page of bills).
  • the transaction information of the users in the daily settlement database does not need to access the entire billing database, which improves the query speed of the bill and reduces the pressure on the billing database.
  • each transaction includes the transaction time, and can also include the transaction amount.
  • step S103 according to the number of transactions and a preset number of transactions per page, perform billing pagination on the transaction of the user's query day, and determine the transaction of each page of billing according to the paging results.
  • the specific implementation process of time information includes:
  • the difference between the number of transactions minus the preset number of transactions per page is divided by the preset number of transactions per page, and the resulting quotient is rounded up by one and finally the pageable number is obtained.
  • the number of transactions is 95
  • the preset number of transactions per page is 20
  • the quotient obtained is 3.75
  • the quotient is rounded and rounded
  • 1 is added to obtain a pageable number of 5 pages.
  • Step S202 Determine the transaction time information of each page of the bill according to the pageable number and the transaction time of each transaction.
  • the transaction time information of each page of the bill may include the start transaction time and the last transaction time of each page of the bill, that is, each page of the bill includes the start transaction time point and the end transaction time point.
  • each transaction is allocated to a pageable bill according to a preset number of transactions per page. After the allocation is completed, the start time and end of each page of the bill can be determined according to the transaction time of each transaction in the bill of each page. Trading point in time.
  • the client sends a bill query request on August 20th, and there is no data in the cache, then the transaction number of the user on August 20th is obtained, and the transaction number reaches the preset transaction number, according to the The number of transactions and the preset number of transactions per page are used to perform pagination of the transactions on the day of the user's query.
  • the number of transactions on August 20 is 36
  • the default number of transactions per page is 10
  • the pageable number is 4 pages.
  • 36 transactions are allocated to 4 pages of bills according to the preset number of transactions per page.
  • each page of the bill includes the time point of starting the transaction and the time point of ending the transaction.
  • Step 104 if the number of transactions does not reach the preset number of transactions, obtain the day-end data of the preset day closest to the query day from the preset day-end data table according to the identity of the user, and According to the obtained daily settlement data and the preset number of transactions per page, perform billing pagination on the preset day's transactions closest to the query day of the user, determine the transaction time information of each page of bills based on the paged results, and Paging results and transaction time information for each page of bills are stored in the cache, where a piece of daily settlement data includes the number of transactions per day of the user.
  • the day-end data of the preset day closest to the query day includes the number of transactions per day in the preset day.
  • the obtained daily settlement data of the preset days is summarized, that is, the total number of transactions of the preset days is obtained, and according to the total number of transactions of the preset days and the preset number of transactions per page, the user is The transactions on the preset day closest to the query day are billed by page.
  • the setting of the preset day may be obtained by accumulating according to the query interval of the user's multiple query. For example, if the user frequently inquires the bill for the last 5 days, the user can automatically set the preset day to 5 days when he initiates the query request.
  • the billing information caching method further includes:
  • the daily transaction number of each user is summarized after the daily cut, and the daily settlement data of each user is generated according to the transaction number of the previous day of each user and stored in the preset daily settlement data table.
  • the daily transaction number of each user is stored in the preset daily settlement data table in units of daily settlement data, that is, the daily transaction number of each user is stored as one daily settlement data.
  • the daily settlement data may also include information on each transaction of the user per day, such as the transaction time and transaction amount of each transaction.
  • a client when a client sends a billing query request, it first queries whether there is data in the buffer. If there is no data in the buffer, it is determined whether the number of transactions on the user's query day reaches a preset number of transactions.
  • the number of transactions and the preset number of transactions per page paginate the transaction and determine the transaction time information of each page of the bill, and store the paged results and the transaction time information of each page of the bill in the cache; if not, obtain the closest Set the daily settlement data for a preset day, perform billing based on the daily settlement data and the preset number of transactions per page, and determine the transaction time information for each page of the bill.
  • the paged results and the transaction time information for each page of the bill are stored in the cache.
  • the number of transactions is first cached for billing information.
  • the time span of the user's transaction bill is determined based on the data in the cache, and the user's billing flow data is further queried according to the time span. Pressure to ensure the successful completion of the query service and increase the query speed, When large queries concurrently to avoid system crashes.
  • this embodiment provides a bill query method based on the bill information caching method in the foregoing embodiment.
  • the specific process is as follows:
  • step S301 upon receiving the bill query request sent by the user terminal, the time span of the bill of each page of the user transaction is determined according to the paged results in the cache and the transaction time information of the bill of each page.
  • the query of bills is based on the current user ID.
  • the user can check the billing data of the user at all times, which will cause great pressure on the billing database, reduce the query speed, and even cause the query service to be completed.
  • this implementation scans the user transaction information in the preset day-end data table according to the paged results in the cache and the transaction time information of each page of the bill, reducing the amount of data scanned per query, reducing the load pressure of the database paging query, and greatly Improved query performance.
  • the transaction time information of each page of the bill may include the starting transaction time and the last transaction time of each page of the bill, that is, each page of the bill includes the starting transaction time point and the ending transaction time point. According to the starting transaction of each page of the bill, The time point and the end time of the transaction determine the time span of each page of the user's transaction.
  • Step S302 Acquire the daily settlement data of the user from a preset daily settlement data table according to the time span of the bill of each page.
  • Step S303 Query the per-page flow data corresponding to the user and the date of each page flow based on the user's day-end data.
  • the flow data of each page corresponding to the user is determined according to the daily settlement data of the user, for example, the transaction amount and transaction route of each transaction, and the transaction time of each transaction is determined, so that the user can query the bill At the same time, understand your current transaction situation.
  • the number of bills displayed on each page is set according to the time span of each page, which reduces the amount of data scanned per query and reduces database paging. Query load pressure, while increasing the user's query experience.
  • the bill query method further includes:
  • the number of transactions in each page of the bill may be different, so each transaction in each page of the bill can be sorted according to the transaction time, so that the user can see it at a glance when viewing the bill.
  • each transaction in each page of the bill can also be sorted by the transaction amount.
  • each transaction in each page of the bill can be sorted according to the transaction amount, so that the user can see at a glance what time he is at The amount of segment transactions is relatively large, increasing the user experience.
  • the time span of each page of the bill is determined by the paged results in the cache and the transaction time information of each page of the bill, and then based on the time of each page of the bill
  • the span obtains the user's day-end data from the preset day-end data table, and finally queries the user's per-page flow data and the date of each page's flow based on the day-end data, reducing the amount of data scanned per query and the database.
  • Pagination query load pressure greatly improves query efficiency.
  • This embodiment provides another bill query method.
  • the specific process is as follows:
  • the user queries the number of transactions for the current day, and determines whether the number of transactions reaches the preset number of transactions.
  • the day-end data of the preset day closest to the query day is obtained from the preset day-end data table according to the identity of the user, and according to the acquired Day-end data and the preset number of transactions per page, pagination of bills for the preset day's transactions closest to the query day of the user, determining the transaction time information of each page of the bill based on the results of the paging, and dividing the paged results with The transaction time information of each page of bills is stored in the cache, wherein a piece of daily settlement data includes the number of transactions per day of the user.
  • the time span of each page of the user's transaction is determined according to the paged results in the cache and the transaction time information of each page of the bill.
  • the billing information is first cached according to the number of transactions of the user, and the day-end data in the preset day-end data table is directly obtained during the query based on the paged results in the cache and the transaction time information of each page of the bill. , Reduce the amount of data scanned per query, reduce the load on the billing database query load, improve the query speed, and greatly improve the query efficiency.
  • FIG. 4 shows a structural block diagram of the billing information buffering device in this embodiment. For convenience of explanation, only the parts related to this embodiment are shown.
  • the device includes a request query module 110, a transaction determination module 120, and an information cache module 130.
  • the request querying module 110 is configured to query whether there is data in the cache when a billing query request sent by a user terminal is received.
  • the transaction determining module 120 is configured to obtain the number of transactions of a user's query on the day if there is no data in the cache, and determine whether the number of transactions reaches a preset number of transactions.
  • the information buffering module 130 is configured to: if the number of transactions reaches the preset number of transactions, perform pagination of bills on the transaction of the user's query on the basis of the number of transactions and the preset number of transactions per page, and As a result, the transaction time information of each page of bills is determined, and the paging results and the transaction time information of each page of bills are stored in the cache.
  • the information caching module 130 is further configured to obtain, from the preset day-end data table, the day closest to the query day if the number of transactions does not reach the preset number of transactions, according to the identity of the user. Settle the data, and based on the obtained daily settlement data and the preset number of transactions per page, perform billing pagination on the preset day's transactions closest to the query day of the user, and determine the transaction time of each page of bills based on the paged results Information, and store the paged results and transaction time information of each page of bills into the cache, where a day-end data includes the number of transactions per day of the user.
  • the device further includes: a daily settlement summary module.
  • the daily settlement summary module is used to summarize the number of transactions of the previous day for each user after the daily cut, and generate the daily settlement data of each user based on the number of transactions of the previous day for each user and store them in the preset day settlement. Data sheet.
  • the requesting query module 110 first checks whether there is data in the buffer. If there is no data in the buffer, the transaction determining module 120 determines whether the number of transactions on the user's query day reaches the preset number of transactions.
  • Module 130 paginates the transactions according to the number of transactions and the preset number of transactions per page and determines the transaction time information of each page of the bill, and stores the paged results and the transaction time information of each page of the bill into the cache; if not, the information cache module 130 Obtain the daily settlement data of the preset day closest to the query day, perform billing based on the daily settlement data and the preset number of transactions per page, and determine the transaction time information of each page of the bill, that is, the billing information is first based on the number of transactions by the user. Prediction cache is used to obtain transaction information based on the data in the cache when querying, which reduces the load on the billing database query load and improves the query speed.
  • FIG. 5 shows a structural block diagram of the bill query device in this embodiment, which is based on the bill information cache device described in any one of the fourth embodiments. For convenience of explanation, only the parts related to this embodiment are shown.
  • the device includes: a time determination module 210, a data acquisition module 220, and a pipeline query module 230.
  • the time determining module 210 is configured to determine the time span of each page of the user's transaction according to the paged results in the cache and the transaction time information of each page of the bill when receiving the bill query request sent by the user.
  • the data obtaining module 220 is configured to obtain daily settlement data of the user from a preset daily settlement data table according to a time span of the bill of each page.
  • the flow query module 230 is configured to query the flow data of each page corresponding to the user and the date on which the flow of each page is located according to the daily settlement data of the user.
  • the time determination module 210 determines the time span of each page of the billing transaction of the user through the paged results in the cache and the transaction time information of each page of billing when receiving the billing query request sent by the client.
  • the obtaining module 220 obtains the daily settlement data of the user from a preset daily settlement data table according to the time span of the bill of each page, and finally the flow query module 230 queries the corresponding data of each page of the user and the date of each page of the flow according to the daily settlement data. , Reduce the amount of data scanned per query, reduce the database paging query load pressure, and greatly improve query efficiency.
  • FIG. 6 is a schematic diagram of a terminal device 100 provided in Embodiment 3 of the present application.
  • the terminal device 100 includes a processor 140, a memory 150, and a computer program 151 stored in the memory 150 and executable on the processor 140, such as a billing information cache. Method procedure, or bill inquiry method procedure.
  • the processor 140 executes the computer program 151, the steps of the foregoing billing information caching method embodiments are implemented, such as steps S101 to S104 shown in FIG. 1, or the steps of the above billing query method embodiments are implemented, For example, steps S101 to S103 shown in FIG. 3.
  • the functions of the modules / units in the foregoing device embodiments are implemented, for example, the functions of modules 110 to 130 shown in FIG. 4 or the functions of modules 210 to 230 shown in FIG. 5 Features.
  • the computer program 151 may be divided into one or more modules / units, and the one or more modules / units are stored in the memory 150 and executed by the processor 140 to complete this invention.
  • the one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe an execution process of the computer program 151 in the terminal device 100.
  • the computer program 151 can be divided into a request query module, a transaction determination module, and an information cache module. The specific functions of each module are as follows:
  • the request query module is used to query whether there is data in the cache when a bill query request sent by a user terminal is received.
  • the transaction determination module is used to obtain the number of transactions of a user's query on the day if there is no data in the cache, and determine whether the number of transactions reaches a preset number of transactions.
  • the information cache module is configured to: if the number of transactions reaches the preset number of transactions, according to the number of transactions and the preset number of transactions per page, perform pagination of the bills of the transaction of the user's query on the current day, and according to the paged results Determine transaction time information for each page of bills, and store the paged results and transaction time information for each page of bills into the cache.
  • the information caching module is further configured to obtain the day end of the preset day closest to the query day from the preset day end data table according to the identity of the user, if the number of transactions does not reach the preset number of transactions. Data, and according to the obtained daily settlement data and the preset number of transactions per page, perform billing pagination on the preset day's transactions closest to the query day of the user, and determine the transaction time information of each page of bills based on the paged results , And storing the paged results and transaction time information of each page of bills into the cache, wherein a piece of daily settlement data includes the number of transactions per day of the user.
  • the computer program 151 may be divided into a time determination module, a data acquisition module, and a pipeline query module.
  • the specific functions of each module are as follows:
  • the time determination module is used to determine the time span of each page of the user's transaction according to the paged results in the cache and the transaction time information of each page of the bill when receiving the bill query request sent by the user.
  • the data acquisition module is configured to acquire daily settlement data of the user from a preset daily settlement data table according to a time span of the bill of each page.
  • the flow query module is used to query the flow data of each page corresponding to the user and the date on which the flow of each page is located according to the daily settlement data of the user.
  • the terminal device 100 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the terminal device 100 may include, but is not limited to, a processor 140 and a memory 150.
  • FIG. 6 is only an example of the terminal device 100, and does not constitute a limitation on the terminal device 100. It may include more or fewer components than shown in the figure, or combine some components or different components.
  • the terminal device 100 may further include an input / output device, a network access device, and a bus.
  • the processor 140 may be a central processing unit (Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), and application-specific integrated circuits (Applications) Specific Integrated Circuit (ASIC), off-the-shelf Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU Central Processing Unit
  • DSP digital signal processor
  • ASIC application-specific integrated circuits
  • FPGA off-the-shelf Programmable Gate Array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory 150 may be an internal storage unit of the terminal device 100, such as a hard disk or a memory of the terminal device 100.
  • the memory 150 may also be an external storage device of the terminal device 100, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, and a flash memory card provided on the terminal device 100. (Flash Card), etc.
  • the memory 150 may further include both an internal storage unit of the terminal device 100 and an external storage device.
  • the memory 150 is configured to store the computer program and other programs and data required by the terminal device 100.
  • the memory 150 may also be used to temporarily store data that has been output or is to be output.
  • the disclosed apparatus / terminal device and method may be implemented in other ways.
  • the device / terminal device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division.
  • components can be combined or integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated module / unit When the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the present invention implements all or part of the processes in the methods of the above embodiments, and may also be completed by a computer program instructing related hardware.
  • the computer program may be stored in a computer-readable storage medium.
  • the computer When the program is executed by a processor, the steps of the foregoing method embodiments can be implemented.
  • the computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file, or some intermediate form.
  • the computer-readable medium may include: any entity or system capable of carrying the computer program code, a recording medium, a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signals, telecommunication signals, and software distribution media.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • electric carrier signals telecommunication signals
  • software distribution media any entity or system capable of carrying the computer program code
  • a recording medium a U disk, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signals, telecommunication signals, and software distribution media.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention, qui est applicable au domaine technique de l'interrogation de données, concerne un procédé de mise en cache d'informations de facture, un procédé d'interrogation de facture et un dispositif terminal. Un procédé selon la présente invention comprend : le fait d'interroger s'il y a des données dans un cache lorsqu'un côté utilisateur envoie une demande d'interrogation de facture ; s'il n'y en a pas, le fait de déterminer si le nombre de transactions d'un utilisateur le jour de l'interrogation atteint un nombre prédéfini de transactions, et s'il en est ainsi, l'exécution d'une pagination de factures sur des transactions selon le nombre de transactions et selon un nombre prédéfini de transactions sur chaque page, la détermination d'informations de temps de transaction de chaque page de facture et le stockage de celles-ci dans un cache ; et dans le cas contraire, l'acquisition de données de règlement journalières à un jour prédéfini le plus proche du jour de l'interrogation, l'exécution d'une pagination de factures selon les données de règlement journalières et selon le nombre prédéfini de transactions sur chaque page, la détermination d'informations de temps de transaction de chaque page de facture et le stockage de celles-ci dans le cache, lorsque l'utilisateur interroge la facture, la détermination d'un intervalle de temps d'une facture de transaction de l'utilisateur selon les données dans le cache, et en outre l'interrogation de données de relevé de compte de la facture de l'utilisateur selon l'intervalle de temps. La présente invention est simple et rapide, réduit la pression de charge lors de l'interrogation d'une base de données de factures et augmente la vitesse d'interrogation.
PCT/CN2018/104602 2018-09-07 2018-09-07 Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal WO2020047840A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/104602 WO2020047840A1 (fr) 2018-09-07 2018-09-07 Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal
CN201880001279.1A CN109313642B (zh) 2018-09-07 2018-09-07 账单信息缓存方法、账单信息查询方法和终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/104602 WO2020047840A1 (fr) 2018-09-07 2018-09-07 Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal

Publications (1)

Publication Number Publication Date
WO2020047840A1 true WO2020047840A1 (fr) 2020-03-12

Family

ID=65221740

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104602 WO2020047840A1 (fr) 2018-09-07 2018-09-07 Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal

Country Status (2)

Country Link
CN (1) CN109313642B (fr)
WO (1) WO2020047840A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112506970A (zh) * 2020-12-11 2021-03-16 中信银行股份有限公司 数据查询方法、装置、电子设备及计算机可读存储介质
CN113377812A (zh) * 2021-01-08 2021-09-10 北京数衍科技有限公司 大数据的订单去重方法和装置
CN113516476A (zh) * 2021-05-18 2021-10-19 中国工商银行股份有限公司 对账处理方法及装置
CN115455015A (zh) * 2022-08-08 2022-12-09 中亿(深圳)信息科技有限公司 一种海量数据存储方法以及装置、存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083763A (zh) * 2019-04-09 2019-08-02 上海车轮互联网服务有限公司 数据查询方法及装置
CN111125148B (zh) * 2019-12-12 2023-07-07 中化石化销售有限公司 一种数据库的分页查询方法及装置
CN111428459A (zh) * 2020-03-27 2020-07-17 中国建设银行股份有限公司 一种员工交易量的统计方法及装置
CN114579528B (zh) * 2022-04-27 2022-08-02 广州市伍麦信息科技有限公司 基于预缓存的文件快速查阅管理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888547A (zh) * 2014-04-16 2014-06-25 中国银行股份有限公司 一种账单处理方法和服务器
CN105243169A (zh) * 2015-11-12 2016-01-13 中国建设银行股份有限公司 一种数据查询方法及系统
US20170177655A1 (en) * 2015-12-17 2017-06-22 SpringAhead, Inc. Dynamic data normalization and duplicate analysis
CN106886548A (zh) * 2016-08-03 2017-06-23 阿里巴巴集团控股有限公司 数据查询方法及装置
CN107918635A (zh) * 2017-08-17 2018-04-17 上海陆家嘴国际金融资产交易市场股份有限公司 账单查询方法、操作装置及计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040193656A1 (en) * 2003-03-28 2004-09-30 Pizzo Michael J. Systems and methods for caching and invalidating database results and derived objects
US8321494B2 (en) * 2007-12-03 2012-11-27 Velocix Ltd. Method and apparatus for reporting and invoicing of data downloads
US10275347B2 (en) * 2010-03-08 2019-04-30 Excalibur Ip, Llc System, method and computer program product for managing caches
US8775488B2 (en) * 2010-04-14 2014-07-08 Siemens Product Lifecycle Management Software Inc. System and method for data caching
CN103533002A (zh) * 2012-07-05 2014-01-22 阿里巴巴集团控股有限公司 一种数据处理方法和系统
CN105468644B (zh) * 2014-09-10 2018-11-23 菜鸟智能物流控股有限公司 一种用于在数据库中进行查询的方法与设备
US10572390B2 (en) * 2016-02-29 2020-02-25 Apple Inc. Methods and apparatus for loading firmware on demand
CN108196829A (zh) * 2017-12-12 2018-06-22 广东广业开元科技有限公司 一种可分析账目的人工智能手机记账系统和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888547A (zh) * 2014-04-16 2014-06-25 中国银行股份有限公司 一种账单处理方法和服务器
CN105243169A (zh) * 2015-11-12 2016-01-13 中国建设银行股份有限公司 一种数据查询方法及系统
US20170177655A1 (en) * 2015-12-17 2017-06-22 SpringAhead, Inc. Dynamic data normalization and duplicate analysis
CN106886548A (zh) * 2016-08-03 2017-06-23 阿里巴巴集团控股有限公司 数据查询方法及装置
CN107918635A (zh) * 2017-08-17 2018-04-17 上海陆家嘴国际金融资产交易市场股份有限公司 账单查询方法、操作装置及计算机可读存储介质

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112506970A (zh) * 2020-12-11 2021-03-16 中信银行股份有限公司 数据查询方法、装置、电子设备及计算机可读存储介质
CN113377812A (zh) * 2021-01-08 2021-09-10 北京数衍科技有限公司 大数据的订单去重方法和装置
CN113516476A (zh) * 2021-05-18 2021-10-19 中国工商银行股份有限公司 对账处理方法及装置
CN115455015A (zh) * 2022-08-08 2022-12-09 中亿(深圳)信息科技有限公司 一种海量数据存储方法以及装置、存储介质
CN115455015B (zh) * 2022-08-08 2024-01-26 中亿(深圳)信息科技有限公司 一种海量数据存储方法以及装置、存储介质

Also Published As

Publication number Publication date
CN109313642A (zh) 2019-02-05
CN109313642B (zh) 2022-07-12

Similar Documents

Publication Publication Date Title
WO2020047840A1 (fr) Procédé de mise en cache d'informations de facture, procédé d'interrogation d'informations de facture et dispositif terminal
CN109144647B (zh) 一种表单设计方法与装置、终端设备以及存储介质
WO2019033605A1 (fr) Appareil et procédé de traitement de commande asynchrone, et support d'informations et terminal
WO2019041753A1 (fr) Procédé de modification d'informations, appareil, dispositif informatique et support de stockage lisible par ordinateur
CN110909025A (zh) 数据库的查询方法、查询装置及终端
CN107943828B (zh) 业务状态查询方法、装置、计算机设备和存储介质
US9721015B2 (en) Providing a query results page
WO2021217863A1 (fr) Procédé et appareil de génération d'identifiants de commandes, server, et support de stockage
CN108038112B (zh) 文件处理方法、移动终端及计算机可读存储介质
CN111897818A (zh) 数据存储方法、装置、电子设备及存储介质
US20210192046A1 (en) Resource Management Unit for Capturing Operating System Configuration States and Managing Malware
CN111104426A (zh) 一种数据查询方法及系统
WO2019019702A1 (fr) Procédé et dispositif d'algorithme, dispositif terminal et support de stockage
WO2018166145A1 (fr) Procédé et dispositif d'offre par lots de données de remboursement
CN110909022A (zh) 一种数据查询方法和装置
US20230088718A1 (en) Resource Management Unit for Capturing Operating System Configuration States and Offloading Tasks
CN107992569B (zh) 数据访问方法、装置、电子设备及计算机可读存储介质
CN113377289A (zh) 一种缓存管理方法、系统、计算设备及可读存储介质
CN113129150A (zh) 交易数据的处理方法、装置、终端设备及可读存储介质
WO2019127772A1 (fr) Procédé et dispositif d'affichage de dictionnaire de données, dispositif terminal et support de stockage
CN109271564A (zh) 保单查询方法及设备
CN116992180A (zh) 缓存数据的方法、装置、终端设备及存储介质
WO2019019596A1 (fr) Procédé de traitement d'une liste de points d'arrêt, dispositif, serveur et support
CN110782310B (zh) 从第三方平台异步获取用户属性信息的方法、装置和系统
CN107609119B (zh) 文件处理方法、移动终端及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18932931

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18932931

Country of ref document: EP

Kind code of ref document: A1