Bill query method and apparatus, and device and storage medium

Abstract

Provided in the embodiments of the present disclosure are a bill query method and apparatus, and a device and a storage medium. The method comprises: acquiring a query request from a user; and in response to the query request, presenting a target bill, wherein a target attribute of the target bill matches the query request, and the target attribute of the target bill is determined on the basis of a plurality of sub-bills associated with the target bill or a plurality of payment ways associated with the target bill. In this way, no matter the user pays a plurality of bills in a combined manner or pays a single bill in a plurality of payment ways, the user can still find corresponding historical bill information when executing a bill query operation.

Description

Bill query method, device, equipment and storage medium

[0001] The present application claims priority to the Chinese patent application No. 202410962338.9, filed on July 17, 2024, entitled “Bill query method, device, equipment and storage medium”, the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The example embodiments of the present disclosure generally relate to the field of computer, in particular, to a bill query method, device, equipment, computer readable storage medium and computer program product. BACKGROUND

[0003] With the development of network technology, various terminal devices can provide people with various services in work and life, for example, users can make transactions on the Internet to obtain their desired services or goods, etc. In the process of transaction, the user needs to pay the corresponding virtual resources. The virtual resources in this paper can be funds, various assets, various points, etc. The service platform can store each transaction of the user in the form of a bill and support the user to query the historical bills. In the real transaction scenario, the payment method is becoming more and more complex, for example, the user can pay multiple bills jointly, or pay a single order through multiple payment methods. With the payment method becoming more and more complex and diverse, the traditional query scheme has been unable to meet the user's query demand.

[0004] SUMMARY

[0005] In a first aspect of the present disclosure, a bill query method is provided. The method comprises: obtaining a query request of a user; and presenting a target bill in response to the query request, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill. In this way, even if the user jointly pays multiple bills or pays a single bill through multiple payment channels, the corresponding bill information can still be queried when the user performs the bill query operation.

[0006] In a second aspect of the present disclosure, a bill query device is provided. The device comprises: a retrieval request obtaining module configured to obtain a query request of a user; and a bill presenting module configured to present a target bill, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill.

[0007] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. The instructions, when executed by the at least one processing unit, cause the device to perform the method of the first aspect.

[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has stored thereon a computer program, the computer program being executable by a processor to implement the method of the first aspect.

[0009] In a fifth aspect of the present disclosure, a computer program product is provided. The computer program product is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method of the first aspect or the second aspect.

[0010] It is to be understood that the particulars shown herein are by way of example and for purposes of illustrative discussion of the embodiments of the present disclosure only and are not intended to limit the scope of the present disclosure to the particular embodiment illustrated. Other objectives, features and aspects of the disclosed embodiments will become apparent from the description given herein. BRIEF DESCRIPTION OF DRAWINGS

[0011] The above and other features, aspects and advantages of embodiments of the present disclosure will become more apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numerals represent like elements throughout the several views, and wherein:

[0012] FIG. 1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

[0013] FIG. 2 shows a schematic diagram of a bill storage data structure, according to some embodiments of the present disclosure;

[0014] [Corrected according to Rule 91 12.09.2024] FIGS. 3A to 3F show schematic diagrams of example interfaces for page interaction, according to some embodiments of the present disclosure;

[0015] [Corrected according to Rule 91 12.09.2024] FIGS. 4A to 4C show schematic diagrams of example interfaces for page interaction, according to some embodiments of the present disclosure;

[0016] FIGS. 5A and 5B show a flowchart of a bill query method, according to some embodiments of the present disclosure;

[0017] FIG. 6 shows a flowchart of a bill query method, according to some embodiments of the present disclosure;

[0018] FIG. 7 shows a schematic structural block diagram of a bill query apparatus, according to certain embodiments of the present disclosure; and

[0019] FIG. 8 shows a block diagram of an electronic device in which one or more embodiments of the disclosure can be implemented. DETAILED DESCRIPTION

[0020] Embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be embodied in various forms and should not be interpreted as being limited to the embodiments set forth herein, but rather, the embodiments are provided so that the present disclosure can be more thoroughly and completely understood. It will be understood that the drawings of the present disclosure are for illustrative purposes only and are not intended to limit the scope of the present disclosure.

[0021] In the description of embodiments of the present disclosure, the term "comprising" and its conjugations should be understood to encompass the meanings of "consisting of" and "consisting essentially of". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "an embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions can also be included below.

[0022] In this document, unless explicitly stated otherwise, performing a step "in response to" an event means that the step can be performed immediately after the event, or it can include one or more intermediate steps.

[0023] It can be understood that the data involved in the technical solutions of the present disclosure (including but not limited to the data itself, the obtaining or use of the data) should comply with the requirements of the relevant laws and regulations and the relevant provisions.

[0024] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the type of personal information involved in the present disclosure, the scope of use, the use scenario, etc. should be informed to the user and the authorization of the user should be obtained through appropriate means according to the relevant laws and regulations.

[0025] For example, in response to receiving the active request of the user, a prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will require obtaining and using the personal information of the user, so that the user can voluntarily choose whether to provide the personal information to the software or hardware such as electronic device, application program, server or storage medium, etc. that performs the operation of the technical solutions of the present disclosure according to the prompt information.

[0026] As an optional but not limiting implementation manner, in response to receiving the active request of the user, the manner of sending the prompt information to the user may, for example, be the manner of pop-up window, and the prompt information may, for example, be presented in the form of text in the pop-up window. In addition, the pop-up window may also carry selection controls for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0027] It can be understood that the above notification and user authorization obtaining process is only illustrative and does not limit the implementation of the present disclosure, and other ways that meet relevant laws and regulations can also be applied to the implementation of the present disclosure.

[0028] The term "in response to" used herein indicates a state in which a corresponding event occurs or a condition is met. It will be understood that the timing of the execution of the subsequent action in response to the event or condition is not necessarily strongly associated with the time at which the event occurs or the condition is met. For example, in some cases, the subsequent action can be performed immediately when the event occurs or the condition is met; in other cases, the subsequent action can be performed after a period of time after the event occurs or the condition is met.

[0029] As briefly discussed above, with the development of network technology, various terminal devices can provide various services to people in work and life, for example, users can trade on the Internet to obtain their desired services or goods, etc. In the process of trading, the user needs to pay for the corresponding virtual resources. The virtual resources in this paper can be funds, coupons, various points, etc.

[0030] Currently, service providers can provide users with a bill query function. However, when users use the bill amount query function, they often only know how much money they have spent, but they cannot remember what they have bought. In other words, users expect to be able to query the historical bills corresponding to the specified consumption amount. This demand occurs more frequently on the bank account day, for example, a user has doubts about a certain consumption record of a bank card and expects to further query in the transaction platform bill to obtain detailed consumption information. In the traditional scheme, the service platform takes each bill as a storage unit. For each bill, the transaction amount and other information of the bill are stored. In the query process, the keywords input by the user are matched with the target attributes of the bills stored in the bill data to output the bill query result.

[0031] However, as briefly discussed above, the real Internet transaction scenario is complex and diverse. For example, in the real transaction process, a user can pay for multiple bills in a single payment, which is referred to as "single payment" for convenience of discussion, or pay for a single bill through multiple payment methods, which is referred to as "combined payment" for convenience of discussion. As discussed above, in the traditional scheme, the service platform takes each bill as a storage unit. In this case, when the user performs a bill query, the bills involving single payment and combined payment cannot be queried because the single payment information and the combined payment information are not recorded in the bill information in association.

[0032] As an example scenario, a user places an order for a first item with a value of 10 yuan in store A, and places an order for a second item with a value of 15 yuan in store B. When making payment, the user uses a first payment account to make a combined payment. For this particular scenario, in the service platform, the consumption record of the first item is stored as a first bill with an amount of 10 yuan, and the consumption record of the second item is stored as a second bill with an amount of 15 yuan. However, a consumption record of 25 yuan is generated in the first payment account of the user. When the user queries the consumption record in the first payment account, he expects to obtain the details of the consumption record corresponding to the 25 yuan. At this time, when the user performs a bill query in the service platform by consumption amount 25, the query result is 0.

[0033] In another example scenario, a user consumes a third item with a value of 45 yuan in store C, of which 25 yuan is paid by the first payment account and the remaining 20 yuan is paid by the second payment account. In this case, in the service platform, the consumption record of the third item is stored as a third bill with an amount of 45 yuan. However, a consumption record of 25 yuan is generated in the first payment account of the user, and a consumption record of 20 yuan is generated in the second payment account of the user. When the user views the consumption record of the first payment account, he expects to obtain the details of the consumption record corresponding to the 25 yuan. At this time, when the user performs a bill query in the service platform by consumption amount 25, the query result is 0.

[0034] At least through the above example embodiments, it can be seen that as the way of transaction becomes more and more complex and diverse, the traditional query method cannot meet the query needs of the user. If the service platform does not support querying the combined payment related bill, the user can only view the historical bills one by one.

[0035] According to embodiments of the present disclosure, a bill query method, device, equipment and storage medium are provided. The method comprises: obtaining a query request of a user; and in response to the query request, presenting a target bill, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment approaches associated with the target bill. In this way, even if the user makes a combined payment for multiple bills or pays a single bill through multiple payment approaches, the corresponding bill information can still be queried when the user performs a bill query operation.

[0036] Various embodiments of the present disclosure will be further described below with reference to the accompanying drawings.

[0037] Example environment

[0038] FIG. 1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. In this example environment 100, a terminal device 150 has an application 120 installed therein. A user 140 can interact with the application 120 via the terminal device 150 and / or an attached device of the terminal device 150.

[0039] In the environment 100 of FIG. 1, the terminal device 150 can render a page 160 of the application 120 if the application 120 is in an active state. The page 160 can include various types of pages that the application 120 can provide, such as an information presentation page, a consumption page, a bill inquiry page, and so on.

[0040] In some embodiments, the terminal device 150 can communicate with a server 130 to implement provisioning of services of the application 120. The terminal device 150 can be any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a game device, or any combination thereof, including an accessory or peripheral device of any of the foregoing or any combination thereof. In some embodiments, the terminal device 150 can also support any type of interface to the user (such as "wearable" circuitry, etc.). The server 130 can be various types of computing systems / servers capable of providing computing capabilities, including but not limited to mainframes, edge computing nodes, computing devices in a cloud environment, and so on.

[0041] In some embodiments, the terminal device 150 can cooperate with the server 130 to provide specific services for the user 140. In some example embodiments of the present disclosure, example procedures are described with the terminal device 150 as the performing subject. It should be understood that the described example procedures can be implemented with cooperation of the terminal device 150 and the server 130. For brevity purposes only, the same or similar content will not be repeated.

[0042] It should be understood that the structure and functionality of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure. Various example implementations of the present disclosure will be described in detail below.

[0043] Example bill inquiry procedure

[0044] As discussed below, the present disclosure provides a bill query scheme. Through the scheme of the present disclosure, even if a user makes a combined payment for multiple bills or makes a single payment for a single bill through multiple payment channels, the corresponding bill information can still be queried when the user performs a bill query operation.

[0045] Before discussing the bill query process of the present disclosure in detail, first refer to the schematic diagram 200 of a data structure 200 of bill storage according to some embodiments of the present disclosure shown in FIG. 2.

[0046] As shown in FIG. 2, the data structure 200 stores the following metadata for each bill: bill identifier, transaction serial number, bill title, transaction amount, etc. Further, when the bill involves a combined payment, the data structure 200 further stores combined bill information. The combined bill information includes but is not limited to: total transaction amount / accumulated bill amount, combined bill serial number, and other information.

[0047] Now further discuss the example embodiments including combined bill information in combination with the following example. In operation, if the user 140 makes a payment for multiple goods in one consumption behavior, for example, the user orders a first good with a value of 10 yuan in store A, and the user orders a second good with a value of 15 yuan in store B. When making the payment, the user 140 makes a combined payment using a first payment account. In this case, the above consumption record can be saved as two bills, for example, bill #1 and bill #2. Bill #1 stores: bill identifier #1, transaction serial number #1, bill title #1, transaction amount 15, and stores the combined bill information, including total transaction amount 25, combined bill serial number, etc. Bill #2 stores: bill identifier #2, transaction serial number #2, bill title #2, transaction amount 10, and stores the combined bill information, including total transaction amount 25, combined bill serial number, etc.

[0048] Through the above operation, the details of the combined payment can be retained in each bill. When performing a query operation, when the user queries with the transaction amount 25 as the keyword, bill #1 and bill #2 can be queried, and according to the same combined bill serial number, bill #1 and bill #2 can be associated to display the combined payment result. In this way, the bill query operation can cover the combined payment scenario, thereby providing the user with more comprehensive query results.

[0049] Further, when the bill involves a combined payment, the data structure 200 further stores combined payment information. The stored combined payment information includes but is not limited to the transaction amount and transaction account corresponding to each payment method and other information.

[0050] In some embodiments, the bill entry including the combined payment information can be constructed based on the following procedure: in response to the target bill being paid through multiple payment channels, constructing a target bill entry corresponding to the target bill in the bill database, and the multiple sub-bill entries storing payment information corresponding to the multiple payment channels.

[0051] The scenario including the combined payment information is further discussed in connection with the following example. In operation, if the user 140 consumes a third commodity in the shop C with a value of 45 yuan, 25 yuan of which is paid through the first payment account, and the remaining 20 yuan is paid through the second payment account. The above consumption record is saved as a bill, for example, bill #3. The bill #3 stores: bill identification #3, transaction serial number #3, bill title #3, transaction amount 45, and stores the combined payment information. The combined payment information includes: payment method 1, transaction amount 25, first payment account; and payment method 2, transaction amount 20, second payment account.

[0052] Through the above operation, the details of the combined payment can be retained in each bill. When performing a query operation, when the user queries with the transaction amount 25 as the keyword, the bill #3 can be queried. In this way, the bill query operation can cover the scenario of combined payment, thereby providing the user with more comprehensive query results.

[0053] Further, when the bill involves the use of a coupon, the data structure 200 further stores the discount information. In some embodiments, the discount information is stored together with the combined payment information. Alternatively, the discount information is involved as one of the payment methods of the combined payment information. As an example embodiment, the user has a 500 yuan coupon, and the coupon is used when paying the bill #1 and the bill #2. In this case, the coupon information is recorded in the data structure of the bill #1 and the bill #2. When performing a query operation, when the user queries with the discount information as the keyword, all historical bills related to the coupon can be queried.

[0054] Through the above operation, the discount information used by the bill can be retained in each bill. In this way, the bill query operation can cover the scenario of paying the bill using the coupon, thereby providing the user with more comprehensive query results.

[0055] Next, example bill query processes of the present disclosure will be further described in connection with example user interfaces 300A-400C shown in FIGS. 3A-4C. It should be understood that the user interfaces shown in FIGS. 3A-4C are merely examples, and various designs can actually exist. For example, various graphical elements and / or controls in the user interfaces can have different arrangements and different visual representations, one or more elements and / or controls therein can be omitted or replaced, and one or more other elements and / or controls can also exist. In addition, any appropriate content can be included in the user interfaces. The scope of the present disclosure is not limited in this regard.

[0056] In example embodiments of the present disclosure, the example user interfaces 300A-400C can be implemented at the terminal device 150, which can be any page of the application 120.

[0057] In operation, the terminal device 150 obtains a query request of a user. In response to the query request, the terminal device 150 presents a target bill, where a target attribute of the target bill matches the query request.

[0058] According to various embodiments of the present disclosure, in some scenarios, the target attribute of the target bill can be determined based on a plurality of sub-bills associated with the target bill. Alternatively or additionally, the target attribute of the target bill can be determined based on a plurality of payment channels associated with the target bill.

[0059] In some embodiments, the plurality of sub-bills is determined based on the following processes: determining a set of candidate bill entries from a plurality of bill entries of a bill database, the set of candidate bill entries corresponding to consolidated payment information matching the query request; and determining, based on consolidated bill information indicated by the set of candidate bill entries, a plurality of sub-bills corresponding to a same consolidated bill identifier, the target bill corresponding to the consolidated bill identifier.

[0060] In some embodiments, the terminal device 150 obtains a query request, where the query request indicates a target bill amount. In response to the query, the terminal device 150 can present a set of historical bills matching the target bill amount. According to embodiments of the present disclosure, the set of historical bills includes at least one of: a first bill or a second bill, where the first bill includes a plurality of sub-bills, a cumulative bill amount of the plurality of sub-bills matching the target bill amount, and the second bill is associated with a plurality of payment channels, a cumulative payment amount of the plurality of payment channels matching the target bill amount.

[0061] Referring to FIG. 3A, an example user interface 300A is shown. The example user interface 300A includes a query bar 301. The user 140 can input a keyword, e.g., a consumption amount, a coupon, a product name, a consumption category, etc. via the query bar 301. If the user 140 inputs a consumable amount in the query bar 301, the terminal device 150 can present a user interface 300B. In the user interface 300B, the terminal device 150 presents historical bills 311-313, where the historical bill 311 is a regular bill, the historical bill 312 is a bill involving a joint payment, and the historical bill 313 is a bill involving a combined payment.

[0062] In some embodiments, the query request indicates a bill amount to be queried, and the target attribute is used to indicate a cumulative payment amount of a target bill. For example, the user interface 300B includes the historical bill 312, which is a joint payment transaction record. In this case, the target attribute is the cumulative payment amount of the joint payment.

[0063] In some embodiments, the query request indicates a bill amount to be queried, and the target attribute is used to indicate a payment amount corresponding to any payment approach of a plurality of payment approaches associated with a target bill. For example, the user interface 300B includes the historical bill 313, which is a combined payment transaction record. In this case, the target attribute is the payment amount corresponding to any payment approach in the combined payment bill.

[0064] In some embodiments, in response to a plurality of historical bills matching the query request, the terminal device presents the plurality of historical bills based on a time sequence of the plurality of historical bills. Referring to the example user interface 300B, the historical bills 311-313 are presented in a time sequence, where a more recently updated historical bill is presented in a more forward position.

[0065] Additionally, the plurality of historical orders can be presented in clusters. In some embodiments, the plurality of historical bills can be presented in clusters according to predetermined time units, e.g., monthly, quarterly, etc. In some embodiments, the plurality of historical bills can also be presented in clusters according to predetermined types, e.g., mall consumption, transfer, etc.

[0066] Further, in the query result display interface, the user 140 can click on any bill to view details of the bill. For example, when the user 140 clicks to view the bill 311, the terminal device 150 presents an example user interface 300C. The example user interface 300C displays information related to the historical bill 311, including but not limited to, payment information, consumption time information, a transaction number, product details, etc. Further, the example user interface 300C can also include merchant information and after-sales service controls, etc.

[0067] In some embodiments, the target bill can be associated with a plurality of sub-bills. In this case, in response to the selection of the target bill, the terminal device 150 can present a first information page. In the first information page, the terminal device can present sub-bill information corresponding to the plurality of sub-bills, wherein the sub-bill information at least indicates the amount of the respective sub-bill. For example, when the user 140 clicks to view the bill 312, the terminal device 150 can present the example user interface 300D. The example user interface 300D displays information related to the historical bill 312. The historical bill 312 includes a sub-bill 331 and a sub-bill 332. The example user interface 300D displays the detail information of the sub-bill 331 and the sub-bill 332 and the respective consumption amount.

[0068] In some embodiments, in response to the selection of a target sub-bill in the plurality of sub-bills, the terminal device 150 can present a detail page of the target sub-bill. For example, when the user 140 selects any one of the sub-bill 331 and the sub-bill 332, the terminal device 150 can present the bill details of the sub-bill.

[0069] In some embodiments, the target bill is associated with a plurality of payment channels. In this case, in response to the selection of the target bill, the terminal device 150 can present a second information page. In the second information page, the terminal device 150 can present the payment amount corresponding to the plurality of payment channels respectively. For example, when the user 140 clicks to view the bill 313, the terminal device 150 can present the example user interface 300E. The example user interface 300E displays information related to the historical bill 313. The historical bill 313 involves two payment methods, cash and savings card. In this case, the example user interface 300E displays the payment details 341, which includes the payment amount corresponding to the plurality of payment channels respectively.

[0070] In some embodiments, the terminal device 150 can determine at least one account associated with the user 140, and determine the target bill matching the query request from a plurality of historical bills associated with the at least one account.

[0071] In some scenarios, the user 140 can be associated with a plurality of accounts. In this case, the query range of the bill and the corresponding query result can be determined according to the current authorized authentication information of the user 140. Specifically, when the terminal device 150 has the first authorized authentication information of the user 140, the terminal device 150 can perform a query operation in the first account set of the user 140, and when the terminal device 150 has the second authorized authentication information of the user 140, the terminal device 150 can perform a query operation in the second account set of the user 140.

[0072] In some embodiments, the current login of the user 140 is a first account. In response to the authentication control being activated, the terminal device 150 can present an authentication interface. Further, the terminal device 150 can obtain authentication information via the authentication interface. In response to the authentication information being verified, the terminal device 150 can determine at least one second account associated with the user 140. Referring to the example user interfaces 300B and 300F shown in FIGS. 3B and 3F, which include authentication controls 314 and 361, respectively. When the user 140 triggers the authentication controls 314 and 361, the authentication operation can be activated. Specifically, the terminal device 150 can present an example authentication interface 400A, e.g., a facial recognition interface, as shown in FIG. 4A. If the authentication is passed, the terminal device 150 can present an example user interface 400B to receive a query request of the user 140. According to the query request input by the user 140, the terminal device 150 can present an example user interface 400C, i.e., present the query results in the plurality of associated accounts.

[0073] Alternatively, in response to the authentication being passed, the terminal device 150 can directly present the example user interface 400C. That is, the terminal device 150 automatically performs the query operation corresponding to the last bill query request input by the user 140 in the plurality of associated accounts.

[0074] In some embodiments, according to a determination that no historical bills associated with the first account match the query request, the terminal device 150 can present the authentication control. For example, when the user 140 inputs a search amount of 25 in the example user interface 300A, the terminal device 150 does not query any historical bills, and the terminal device 150 presents the example user interface 300F. The example user interface 300F prompts that no relevant historical bills are queried and guides the user 140 to further authenticate or obtain the query permission of the second account.

[0075] For better understanding of the above process, further referring to a flowchart of a bill query method 500A according to some embodiments of the present disclosure shown in FIG. 5A.

[0076] At block 501, the terminal device 150 obtains the query content input by the user 140. As discussed above, the query content can be a transaction amount, a coupon, an item name, a transaction type, etc. At block 502, the terminal device 150 determines whether the query content is of an amount type. If it is determined that the query content is not of the amount type, at block 503, the terminal device 150 performs a fuzzy match of bill titles according to the obtained query content, and at block 504, filters the query results that meet the conditions.

[0077] If the query content is determined to be of the amount type, the terminal device 150 further classifies the input format of the query content at block 504. If the query content is determined to be of the text type, the terminal device 150 fuzzily matches the bill title at block 506 and filters the query results that meet the conditions at block 511.

[0078] If the input type is determined to be of the number type at block 505, the terminal device 150 classifies the amount at block 507 and matches the transaction information in the bill data structure, including the transaction amount, the total transaction amount in the combined order information, and the transaction amount in the combined payment information, at blocks 508-510, respectively, and filters the query results that meet the conditions at block 511.

[0079] Referring further to the flowchart of the bill query method 500B according to some embodiments of the present disclosure shown in FIG. 5B.

[0080] The terminal device 150 optionally determines whether the query results are empty at block 551. If the query results are not empty, the terminal device 150 sorts the query results based on the transaction time at block 553 and displays the query results at block 554.

[0081] If the query results are determined to be empty, the terminal device 150 determines whether the user 140 triggers further authentication at block 552. If the user 140 does not trigger further authentication, the terminal device 150 ends the current query process. If the user 140 is determined to trigger further authentication, the terminal device 150 determines whether there are multiple accounts under the user name at block 552. If there are determined to be no multiple accounts, the terminal device 150 determines that the query results are empty at block 556 and displays the query results at block 554.

[0082] If there are determined to be multiple accounts, the terminal device 150 provides a bill query tool entry at block 557. The user 140 can provide authentication information by facial recognition at block 558. If the authentication information is passed, the terminal device 150 receives the user input query date and the exact amount at block 559. The terminal device 150 accurately matches the order transaction information of each account at block 560 and merges the query results of multiple accounts at block 561. The terminal device 150 sorts the query results based on the transaction time at block 562 and displays the query results at block 554.

[0083] Through the above process, the user can more easily query the historical bills corresponding to the consumption records of the payment account, whether the historical bills are combined payments or combined payments.

[0084] Example method

[0085] FIG. 6 shows a flowchart of a method 600 for page interaction, according to some embodiments of the present disclosure. The method 600 can be implemented at the terminal device 150 (or jointly implemented by the terminal device 150 and the server 130). For ease of discussion, in the example embodiments below, the process 800 is implemented at the terminal device 150. The process 600 is described below with reference to FIG. 1.

[0086] At block 610, the terminal device obtains a query request of the user.

[0087] At block 620, the terminal device presents a target bill in response to the query request, the target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill.

[0088] In some embodiments, the query request indicates a bill amount to be queried, and the target attribute is used to indicate a cumulative payment amount of the target bill or a payment amount corresponding to any of the plurality of payment channels associated with the target bill.

[0089] In some embodiments, the target bill is associated with a plurality of sub-bills. Further, in response to selection of the target bill, the terminal device presents a first information page, and the terminal device presents sub-bill information corresponding to the plurality of sub-bills in the first information page, the sub-bill information indicating at least an amount of the corresponding sub-bill.

[0090] In some embodiments, in response to selection of a target sub-bill of the plurality of sub-bills, the terminal device presents a detail page of the target sub-bill.

[0091] In some embodiments, the target bill is associated with a plurality of payment channels. Further, in response to selection of the target bill, the terminal device presents a second information page; and the terminal device presents payment amounts corresponding to the plurality of payment channels respectively in the second information page.

[0092] In some embodiments, the terminal device determines at least one account associated with the user, and determines the target bill matching the query request from a plurality of historical bills associated with the at least one account.

[0093] In some embodiments, the user is currently logged in a first account, and the terminal device presents an authentication interface in response to determining that no historical bill associated with the first account matches the query request. Further, authentication information is obtained via the authentication interface; and in response to the authentication information passing verification, the terminal device determines at least one second account associated with the user.

[0094] In some embodiments, in response to the plurality of historical bills matching the query request, the terminal device presents the plurality of historical bills based on a time sequence of the plurality of historical bills.

[0095] In some embodiments, the plurality of sub-bills are determined based on a process of: determining a set of candidate bill entries from the plurality of bill entries of the bill database, the set of candidate bill entries corresponding to the consolidated payment information matching the query request; and determining the plurality of sub-bills corresponding to the same consolidated bill identifier based on the consolidated bill information indicated by the set of candidate bill entries, the target bill corresponding to the consolidated bill identifier.

[0096] In some embodiments, the consolidated bill information further indicates a cumulative bill amount of the target bill.

[0097] In some embodiments, the target bill corresponds to a target bill entry in the bill database, and the target bill entry is constructed based on a process of: in response to the target bill being paid by a plurality of payment channels, constructing the target bill entry corresponding to the target bill in the bill database, the plurality of sub-bill entries storing payment information corresponding to the plurality of payment channels.

[0098] Example apparatus and device

[0099] FIG. 7 illustrates a schematic structural block diagram of an apparatus 700 for page interaction, according to certain embodiments of the present disclosure. The apparatus 700 can be implemented as or included in the terminal device 150. Various modules / components in the apparatus 700 can be implemented by hardware, software, firmware, or any combination thereof.

[0100] As shown in FIG. 7, the bill query apparatus 700 includes: a retrieval request obtaining module 710 configured to obtain a query request of a user; and a bill presentation module 720 configured to present a target bill, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill.

[0101] In some embodiments, the query request indicates a bill amount to be queried, and the target attribute is used to indicate a cumulative payment amount of the target bill or a payment amount corresponding to any of the plurality of payment channels associated with the target bill.

[0102] In some embodiments, the target bill is associated with the plurality of sub-bills, and the apparatus 700 further includes a sub-bill presentation module configured to: in response to selection of the target bill, present a first information page; and present sub-bill information corresponding to the plurality of sub-bills in the first information page, the sub-bill information at least indicating an amount of a corresponding sub-bill.

[0103] In some embodiments, the apparatus 700 further includes a sub-bill detail presentation module configured to, in response to selection of a target sub-bill in the plurality of sub-bills, present a detail page of the target sub-bill.

[0104] In some embodiments, the target bill is associated with a plurality of payment channels, and the apparatus 700 further includes a payment channel presentation module configured to, in response to selection of the target bill, present a second information page, and present, in the second information page, payment amounts respectively corresponding to the plurality of payment channels.

[0105] In some embodiments, the bill presentation module 720 is further configured to determine at least one account number associated with the user, and determine, from a plurality of historical bills associated with the at least one account number, a target bill matching the query request.

[0106] In some embodiments, the user is currently logged in a first account number, and the bill presentation module 720 is further configured to, in response to determining that no historical bill associated with the first account number matches the query request, present an authentication interface, obtain authentication information via the authentication interface, and in response to the authentication information passing verification, determine at least one second account number associated with the user.

[0107] In some embodiments, the bill presentation module 720 is further configured to, in response to the plurality of historical bills matching the query request, present the plurality of historical bills based on a time sequence of the plurality of historical bills.

[0108] In some embodiments, the plurality of sub-bills are determined based on a process of determining a set of candidate bill entries from a plurality of bill entries of a bill database, the set of candidate bill entries corresponding to consolidated payment information matching the query request, and determining, based on consolidated bill information indicated by the set of candidate bill entries, a plurality of sub-bills corresponding to a same consolidated bill identifier, the target bill corresponding to the consolidated bill identifier.

[0109] In some embodiments, the consolidated bill information further indicates a cumulative bill amount of the target bill.

[0110] In some embodiments, the target bill corresponds to a target bill entry in the bill database, and the target bill entry is constructed based on a process of, in response to the target bill being paid via a plurality of payment channels, constructing, in the bill database, a target bill entry corresponding to the target bill, the plurality of sub-bill entries storing payment information corresponding to the plurality of payment channels.

[0111] FIG. 8 illustrates a block diagram of an electronic device 800 in which one or more embodiments of the disclosure can be implemented. It should be understood that the electronic device 800 illustrated in FIG. 8 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 800 illustrated in FIG. 8 can be used to implement the terminal device 150 of FIG. 1.

[0112] As illustrated in FIG. 8, the electronic device 800 is in the form of a general electronic device. Components of the electronic device 800 can include, but are not limited to, one or more processors or processing units 810, a memory 820, a storage device 830, one or more communication units 840, one or more input devices 850, and one or more output devices 860. The processing unit 810 can be a real or virtual processor and is capable of executing various processing in accordance with programs stored in the memory 820. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve parallel processing capability of the electronic device 800.

[0113] The electronic device 800 typically includes a number of computer storage media. Such media can be any available media that is accessible by the electronic device 800 and includes both volatile and non-volatile media, removable and non-removable media. The memory 820 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 830 can be a removable or non-removable media and can include machine-readable media, such as a flash drive, a magnetic disk, or any other media that can be used to store information and / or data (e.g., training data for training) and that can be accessed by the electronic device 800.

[0114] The electronic device 800 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 8, a disk drive and a disk drive interface can be provided for reading from or writing to a removable, non- volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive and disk drive interface can be provided for reading from or writing to a removable, non-volatile optical disk (e.g., a "CD-ROM" or "DVD"). In these instances, each drive can be connected to the bus (not shown) by one or more data media interfaces. The memory 820 can include a computer program product 825 having one or more program modules configured to carry out the various methods or actions of the various embodiments of the present disclosure.

[0115] The communication unit 840 enables communication through the communication medium with other electronic devices. Additionally, the functionality of the components of the electronic device 800 can be implemented in a single computing cluster or a plurality of computer machines that are capable of communicating over a communication connection. As such, the electronic device 800 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0116] The input device 850 can be one or more input devices, such as a mouse, a keyboard, a trackball, etc. The output device 860 can be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 800 can also communicate with one or more external devices (not shown), such as a storage device, a display device, etc., through the communication unit 840, as necessary, with one or more devices that enable a user to interact with the electronic device 800, or with any device (e.g., a network card, a modem, etc.) that enables the electronic device 800 to communicate with one or more other electronic devices. Such communication can be carried out via an input / output (I / O) interface (not shown).

[0117] According to an example implementation of the present disclosure, there is provided a computer-readable storage medium having computer-executable instructions stored thereon, where the computer-executable instructions are executed by a processor to implement the method described above. According to an example implementation of the present disclosure, there is also provided a computer program product tangibly stored on a non-transitory computer-readable medium and including computer-executable instructions, where the computer-executable instructions are executed by a processor to implement the method described above.

[0118] Various aspects of the disclosure are now described with reference to the drawings. In general, the drawings described below are diagrammatic and schematic representations of actual or conceptual structures and processes, and are not limiting of the scope of the present disclosure. In the drawings, the same reference numerals are used to represent similar components. The embodiments of the present disclosure will be described with reference to the drawings, beginning with FIG. 1.

[0119] These computer readable program instructions can be provided to a processor of a general purpose computer, special purpose computer, 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 / acts specified in the flowchart and / or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can include a non-transitory computer readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including a manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks.

[0120] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0121] The flow diagrams and the block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various implementations of the present disclosure. In this regard, each block in the flow diagrams and the block diagrams can represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logic functions (s). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in some cases, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and

[0122] implementations. Numerous modifications and adaptations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The herein described subject matter is to be considered in all its novel implications and applications and can be practiced in a variety of environments. It is also to be understood that such features are only examples and that many modifications, additions, or omissions can be made without departing from the scope of the claimed disclosure. Accordingly, the exemplary implementations described herein are not intended to limit the scope of the claimed disclosure but rather are intended to embrace all such alterations, modifications, additions, omissions, and equivalents that are within the scope and spirit of the claimed disclosure.

Claims

1.A method for bill inquiry, comprising: obtaining a query request of a user; and presenting a target bill in response to the query request, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill. 2.The method of claim 1, wherein the query request indicates an amount of a bill to be inquired, and the target attribute is used to indicate one of: a total payment amount of the target bill, or a payment amount corresponding to any of the plurality of payment channels associated with the target bill. 3.The method of claim 1, wherein the target bill is associated with the plurality of sub-bills, the method further comprising: presenting a first information page in response to a selection of the target bill; and presenting sub-bill information corresponding to the plurality of sub-bills in the first information page, the sub-bill information indicating at least an amount of a respective sub-bill. 4.The method of claim 3, further comprising: presenting a detail page of a target sub-bill in response to a selection of the target sub-bill from the plurality of sub-bills. 5.The method of claim 1, wherein the target bill is associated with the plurality of payment channels, the method further comprising: presenting a second information page in response to a selection of the target bill; and presenting payment amounts corresponding to the plurality of payment channels respectively in the second information page. 6.The method of claim 1, wherein presenting a target bill comprises: determining at least one account associated with the user; and determining the target bill matching the query request from a plurality of historical bills associated with the at least one account. 7.The method of claim 6, wherein the user is currently logged in a first account, and determining at least one account associated with the user comprises: presenting an authentication interface in response to an authentication control being activated bill; obtaining authentication information via the authentication interface; and determining at least one second account associated with the user in response to the authentication information being verified. 8.The method of claim 7, further comprising: presenting the authentication control according to a determination that no historical bill associated with the first account matches the query request. 9.The method of claim 1, wherein presenting a target bill comprises: presenting a plurality of historical bills based on a time sequence of the plurality of historical bills in response to the plurality of historical bills matching the query request. 10.The method of claim 1, wherein the plurality of sub-bills are determined based on a process comprising: determining a set of candidate bill entries from a plurality of bill entries of a bill database, the set of candidate bill entries corresponding to consolidated payment information matching the query request; and determining the plurality of sub-bills corresponding to a same consolidated bill identifier based on consolidated bill information indicated by the set of candidate bill entries, the target bill corresponding to the consolidated bill identifier. ​ ​ ​ ​ ​ ​ 11.The method of claim 10, wherein the consolidated billing information further indicates a cumulative billing amount of the target bill. 12.The method of claim 1, wherein the target bill corresponds to a target bill entry in a bill database, and the target bill entry is constructed based on a process comprising: in response to the target bill being paid through a plurality of payment channels, constructing the target bill entry corresponding to the target bill in the bill database, the plurality of sub-bill entries storing payment information corresponding to the plurality of payment channels. 13.A bill query apparatus, comprising: a retrieval request obtaining module configured to obtain a query request of a user; and a bill presenting module configured to present a target bill, a target attribute of the target bill matching the query request, wherein the target attribute of the target bill is determined based on a plurality of sub-bills associated with the target bill or a plurality of payment channels associated with the target bill. 14.An electronic device, comprising: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to any one of claims 1 to 12. 15.A computer-readable storage medium having stored thereon a computer program, the computer program being executable by a processor to implement the method according to any one of claims 1 to 12. 16.A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 12. ​ ​ ​ ​ ​ ​ ​ ​

Images