Bill Query Method, Device, Equipment and Storage Medium

Abstract

According to an embodiment of the present disclosure, there are provided a bill query method, apparatus, device, and storage medium. The method includes: obtaining a query request of a user; and in response to the query request, presenting a target bill, where a target attribute of the target bill matches the query request, and 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 a user combines multiple bills for payment or pays a single bill through multiple payment channels, when the user performs a bill query operation, the corresponding historical bill information can still be queried.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and particularly to a bill query method, apparatus, device, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of network technology, various terminal devices can provide people with various services in aspects such as work and life. For example, users can conduct transactions on the Internet to obtain desired services or goods, etc. During the transaction process, users need to pay corresponding virtual resources. The virtual resources herein can be funds, various types of assets, various types of points, etc. The service platform can store each transaction of the user in the form of a bill and support the user to query their historical bills. In real transaction scenarios, the payment methods are becoming increasingly complex. For example, users can combine multiple bills for payment or pay a single order through multiple payment methods. As the payment methods become more and more complex and diverse, the traditional query solutions can no longer meet the query needs of users. Summary of the Invention

[0003] In a first aspect of the present disclosure, a bill query method is provided. The method includes: obtaining a query request of a user; and in response to the query request, presenting a target bill, where the target attribute of the target bill matches the query request, and 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 combines multiple bills for payment or pays a single bill through multiple payment channels, when the user performs a bill query operation, the corresponding bill information can still be queried.

[0004] In a second aspect of the present disclosure, a bill query apparatus is provided. The apparatus includes: 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, where the target attribute of the target bill matches the query request, and 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.

[0005] 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, the at least one memory being 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 execute the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0007] 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 execute the method of the first aspect or the second aspect.

[0008] It should be understood that the content described in this part is not intended to define the key features or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In conjunction with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages, and aspects of the embodiments of the present disclosure will become more apparent. In the drawings, the same or similar reference numerals denote the same or similar elements, where:

[0010] Figure 1 A schematic diagram showing an example environment in which the embodiments of the present disclosure can be implemented;

[0011] Figure 2 A schematic diagram showing a bill storage data structure according to some embodiments of the present disclosure;

[0012] Figures 3A to 3F A schematic diagram showing an example interface for page interaction according to some embodiments of the present disclosure;

[0013] Figures 4A to 4C A schematic diagram showing an example interface for page interaction according to some embodiments of the present disclosure;

[0014] Figure 5A and 5B A flowchart showing a bill query method according to some embodiments of the present disclosure;

[0015] Figure 6 A flowchart showing a bill query method according to some embodiments of the present disclosure;

[0016] Figure 7 A schematic structural block diagram showing a bill query device according to certain embodiments of the present disclosure; and

[0017] Figure 8 A block diagram showing an electronic device in which one or more embodiments of the present disclosure can be implemented. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0019] In the description of the embodiments of the present disclosure, the term "including" and its like should be understood as an open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". There may also be other explicit and implicit definitions hereinafter.

[0020] In this article, unless expressly stated, performing a step "in response to A" does not mean that the step is immediately performed after "A", but may include one or more intermediate steps.

[0021] It can be understood that the data involved in the technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of the corresponding laws, regulations and related provisions.

[0022] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained through appropriate means according to relevant laws and regulations.

[0023] For example, when a user's active request is received, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information, so that the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server or a storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

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

[0025] It is understandable that the above-mentioned notification and the process of obtaining user authorization are only illustrative and do not limit the implementation manner of the present disclosure. Other manners that comply with relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0026] As used herein, the term "in response to" represents a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the execution timing of subsequent actions performed in response to the event or condition and the time when the event occurs or the condition is established are not necessarily strongly correlated. For example, in some cases, the subsequent action can be immediately executed when the event occurs or the condition is established; while in other cases, the subsequent action can be executed after a period of time after the event occurs or the condition is established.

[0027] As briefly discussed above, with the development of network technology, various terminal devices can provide people with various services in aspects such as work and life. For example, users can conduct transactions on the Internet to obtain desired services or goods, etc. During the transaction process, users need to pay corresponding virtual resources. The virtual resources in this article can be funds, coupons, various types of points, etc.

[0028] 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 they have spent but cannot remember what they have specifically bought. In other words, users expect to be able to query the historical bills corresponding to the specified consumption amount. This need more often appears on the bank statement date. For example, users have doubts about a certain consumption record on their bank card and expect to further query in the bills of the trading platform to obtain detailed consumption information. In the traditional solution, the service platform uses each bill as a storage unit. For each bill, information such as the transaction amount of the bill is stored. During 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.

[0029] However, as briefly discussed above, the real Internet transaction scenarios are complex and diverse. For example, during the real transaction process, users can combine multiple bills for payment, which is abbreviated as "combined payment" for the convenience of discussion in this article, or pay a single bill through multiple payment methods, which is abbreviated as "composite payment" for the convenience of discussion in this article. As discussed above, in the traditional solution, the service platform uses each bill as a storage unit. In this case, when users perform bill queries, since the combined payment information and the composite payment information are not associated and recorded in the bill information, the bills involving combined payment and composite payment cannot be queried. The above problems will be elaborated in more detail in combination with the following example scenarios.

[0030] As an example scenario, the user places an order for a first product worth 10 yuan in store A and simultaneously places an order for a second product worth 15 yuan in store B. When making the payment, the user uses the first payment account for combined payment. For this specific scenario, in the service platform, the consumption record of the first product is stored as the first bill with an amount of 10 yuan, and the consumption record of the second product is stored as the second bill with an amount of 15 yuan. However, in the user's first payment account, a consumption record of 25 yuan is generated. When the user queries the consumption record in the first payment account, they expect to know the details of the consumption record corresponding to this 25 yuan. At this time, when the user queries the bill in the service platform by the consumption amount of 25, the query result is 0.

[0031] In another example scenario, the user consumes a third product worth 45 yuan in store C, where 25 yuan is paid through the first payment account and the remaining 20 yuan is paid through the second payment account. In this case, in the service platform, the consumption record of the third product is stored as the third bill with an amount of 45 yuan. However, in the user's first payment account, a consumption record of 25 yuan is generated, and in the user's second payment account, a consumption record of 20 yuan is generated. When the user views the consumption record in their first payment account, they expect to obtain the details of the consumption record corresponding to this 25 yuan. At this time, when the user queries the bill in the service platform by the consumption amount of 25, the query result is 0.

[0032] At least from the above example embodiments, it can be seen that as the transaction methods become more and more complex and diverse, the traditional query method cannot meet the user's query needs. If the service platform does not support querying bills related to combined payment and combined payment, the user can only view the historical bills one by one.

[0033] According to the embodiments of the present disclosure, there are provided a bill query method, apparatus, device, and storage medium. The method includes: obtaining a query request of a user; and in response to the query request, presenting a target bill, where the target attribute of the target bill matches the query request, and 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 makes a combined payment for multiple bills or pays a single bill through multiple payment channels, when the user performs a bill query operation, the corresponding bill information can still be queried.

[0034] The various embodiments of the present disclosure will be further described below with reference to the accompanying drawings.

[0035] Example environment

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

[0037] In Figure 1 environment 100, if the application 120 is active, the terminal device 150 can present a page 160 of the application 120. The page 160 can include various types of pages that the application 120 can provide, such as an information display page, a consumption page, a bill query page, and so on.

[0038] In some embodiments, the terminal device 150 can communicate with a server 130 to implement the supply of services for the application 120. The terminal device 150 can be any type of mobile terminal, fixed terminal, or portable terminal, including a mobile phone, 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 / video camera, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 150 can also support any type of user interface (such as a "wearable" circuit, etc.). The server 130 can be various types of computing systems / servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, computing devices in a cloud environment, and so on.

[0039] In some embodiments, the terminal device 150 and the server 130 can cooperate to provide a specific service for the user 140. In some exemplary embodiments of the present disclosure, the exemplary process is described with the terminal device 150 as the execution subject. It should be understood that the described exemplary process can be implemented by the cooperation of the terminal device 150 and the server 130. For the sake of brevity only, the same or similar content will not be repeated.

[0040] It should be understood that the structures and functions of the various elements in the environment 100 are described only for exemplary purposes, and do not imply any limitation on the scope of the present disclosure. Various exemplary implementations of the present disclosure will be described in detail below.

[0041] Example bill query process

[0042] As discussed below, the present disclosure provides a bill query solution. Through the solution of the present disclosure, even if a user pays multiple bills together or pays a single bill through multiple payment methods, when the user performs a bill query operation, the corresponding bill information can still be queried.

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

[0044] As Figure 2 shown, for each bill, the data structure 200 stores the following metadata: bill identifier, transaction order number, bill title, transaction amount, etc. Further, when the bill involves 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 order number, and other information.

[0045] Now, a sample embodiment including combined bill information will be further discussed with the following example. In the operation, if user 140 pays for multiple items in a single consumption behavior. For example, the user places an order for a first item worth 10 yuan in store A and an order for a second item worth 15 yuan in store B. When making the payment, user 140 uses a first payment account for combined payment. In this case, the above consumption records can be saved as two bills, for example, bill #1 and bill #2. In bill #1, it stores: bill identifier #1, transaction order number #1, bill title #1, transaction amount 15, and stores combined bill information, including total transaction amount 25, combined bill order number, etc. In bill #2, it stores: bill identifier #2, transaction order number #2, bill title #2, transaction amount 10, and stores combined bill information, including total transaction amount 25, combined bill order number, etc.

[0046] Through the above operation, the details of 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, bills #1 and #2 can be queried, and based on the same combined bill order number, bills #1 and #2 can be associated to display the combined payment result. In this way, the bill query operation can cover the scenario of combined payment, thereby providing a more comprehensive query result to the user.

[0047] Further, when the bill involves 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.

[0048] In some embodiments, a bill entry including combined payment information may be constructed based on the following process: in response to a target bill being paid through multiple payment channels, a target bill entry corresponding to the target bill is constructed in a bill database, and a plurality of sub-bill entries store payment information corresponding to the multiple payment channels.

[0049] The scenario including combined payment information will be further discussed with the following example. In operation, if user 140 consumes a third commodity worth 45 yuan in store C, where 25 yuan is paid through a first payment account and the remaining 20 yuan is paid through a second payment account. Then the above consumption record is saved as a bill, for example, bill #3. Bill #3 stores: bill identifier #3, transaction order number #3, bill title #3, transaction amount 45, and stores 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.

[0050] Through the above operations, the detailed information of combined payment can be retained in each bill. When performing a query operation, when the user queries with the transaction amount 25 as a keyword, bill #3 can be queried. In this way, the bill query operation can cover the scenario of combined payment, so as to provide a more comprehensive query result to the user.

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

[0052] Through the above operations, the coupon information used in the bill can be retained in each bill. In this way, the bill query operation can cover the scenario of paying bills with coupons, so as to provide a more comprehensive query result to the user.

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

[0054] In an exemplary embodiment of the present disclosure, the exemplary user interfaces 300A to 400C can be implemented at the terminal device 150, which can be any page of the application 120.

[0055] In operation, the terminal device 150 obtains a query request from the user. In response to the query request, the terminal device 150 presents a target bill, where the target attributes of the target bill match the query request.

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

[0057] In some embodiments, the multiple sub-bills are determined based on the following process: determining a set of candidate bill entries from multiple bill entries in the bill database, where the combined payment information corresponding to the set of candidate bill entries matches the query request; and based on the combined bill information indicated by the set of candidate bill entries, determining multiple sub-bills corresponding to the same combined bill identifier, and the target bill corresponds to the combined bill identifier.

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

[0059] Reference Figure 3AThe exemplary user interface 300A shown. The exemplary user interface 300A includes a query bar 301. User 140 can enter keywords through the query bar 301, such as, consumption amount, coupon, commodity name, consumption category, etc. If user 140 enters the consumable amount in the query bar 301, the terminal device 150 can present the user interface 300B. In the user interface 300B, the terminal device 150 presents historical bills 311 to 313, where historical bill 311 is a regular bill, historical bill 312 is a bill involving combined payment, and historical bill 313 is a bill involving combined payment.

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

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

[0062] In some embodiments, in response to multiple historical bills matching the query request, the terminal device presents the multiple historical bills based on the chronological order of the multiple historical bills. Refer to the exemplary user interface 300B, where the historical bills 311 to 313 are presented in chronological order, and the updated historical bills are presented in a more forward position.

[0063] Additionally, multiple historical orders can be presented in a clustered manner. In some embodiments, multiple historical bills can be presented in a clustered manner according to a predetermined time unit, such as, monthly, quarterly, etc. In some embodiments, multiple historical bills can also be presented in a clustered manner according to a predetermined type, such as, mall consumption, transfer, etc.

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

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

[0066] In some embodiments, in response to the selection of a target sub-bill among multiple sub-bills, the terminal device 150 may present a detailed page of the target sub-bill. For example, when the user 140 selects any one of sub-bill 331 and sub-bill 332, the terminal device 150 may present the bill details of that sub-bill.

[0067] In some embodiments, the target bill is associated with multiple payment methods. In this case, in response to the selection of the target bill, the terminal device 150 may present a second information page. In the second information page, the terminal device 150 may present the payment amounts corresponding to the multiple payment methods respectively. For example, when the user 140 clicks to view bill 313, the terminal device 150 may present the exemplary user interface 300E. The exemplary user interface 300E displays information related to the historical bill 313. The historical bill 313 involves two payment methods, change and debit card. In this case, the exemplary user interface 300E displays the payment details 341, which includes the payment amounts corresponding to the multiple payment methods respectively.

[0068] In some embodiments, the terminal device 150 may determine at least one account associated with the user 140, and determine a target bill that matches the query request from multiple historical bills associated with the at least one account.

[0069] In some scenarios, the user 140 may be associated with multiple accounts. In this case, the query scope of the bill may be determined according to the current authorization authentication information of the user 140 and the corresponding query result may be returned. Specifically, when the terminal device 150 has the first authorization authentication information of the user 140, the terminal device 150 may perform a query operation in the first account set of the user 140, and when the terminal device 150 has the second authorization authentication information of the user 140, the terminal device 150 may perform a query operation in the second account set of the user 140.

[0070] In some embodiments, the current login of user 140 is the first account. In response to the activation of the authentication control, 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 passing the verification, the terminal device 150 can determine at least one second account associated with user 140. Refer to Figure 3B and 3F the example user interfaces 300B and 300F shown, which include authentication controls 314 and 361 respectively. When 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 as shown in Figure 4A , for example, a face recognition interface. If the authentication is passed, the terminal device 150 can present the example user interface 400B to receive the query request of user 140. According to the query request input by user 140, the terminal device 150 can present the example user interface 400C, that is, present the query results among multiple associated accounts.

[0071] Alternatively, in response to the authentication passing, the terminal device 150 can directly present the example user interface 400C. That is, the terminal device 150 automatically performs a query operation corresponding to the previous bill query request input by user 140 within multiple associated accounts.

[0072] In some embodiments, according to the determination that the historical bills associated with the first account do not match the query request, the terminal device 150 can present the authentication control. For example, when user 140 inputs a search amount of 25 in the example user interface 300A and the terminal device 150 does not query any historical bills, 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 user 140 to perform further authentication or obtain the query permission for the second account.

[0073] For a better understanding of the above process, further refer to Figure 5A the flowchart of the bill query method 500A according to some embodiments of the present disclosure shown in

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

[0075] If it is determined that the query content is of the amount type, in block 504, the terminal device 150 further classifies the input format of the query content. If it is determined to be of the text type, then in block 506, the bill title is fuzzy-matched, and in block 511, the query results that meet the conditions are filtered.

[0076] If it is determined in block 505 that the input type is of the numeric type, then in 507, the amounts are classified, and in blocks 508 to 510, the transaction information in the bill data structure is respectively matched, including the transaction amount, the total transaction amount in the combined order information, and the transaction amount in the combined payment information, and in block 511, the query results that meet the conditions are filtered.

[0077] See further Figure 5B The flowchart of the bill query method 500B according to some embodiments of the present disclosure shown in

[0078] In block 551, the terminal device 150 optionally determines whether the query results are empty. If the query results are not empty, then in block 553, the terminal device 150 sorts the query results based on the transaction time and in block 554, presents the query results.

[0079] If it is determined whether the query results are empty, then in block 552, it is determined whether the user 140 triggers further authentication. If the user 140 does not trigger further authentication, then the terminal device 150 ends the current query process. If it is determined that the user 140 triggers further authentication, then in block 552, the terminal device 150 determines whether there are multiple accounts under the user's name. If it is determined that there are no multiple accounts, then in block 556, it is determined that the query results are empty and in block 554, the query results are presented.

[0080] If it is determined that there are multiple accounts, then in block 557, an entry for the bill query tool is provided. In block 558, the user 140 can provide authentication information by face recognition. If the authentication information passes, in block 559, the terminal device 150 receives the user's input of the query date and the exact amount. In block 560, the terminal device 150 precisely matches the order transaction information of each account, and in block 561, the terminal device 150 combines the query results of multiple accounts. In block 562, the terminal device 150 sorts the query results based on the transaction time and in block 554, presents the query results.

[0081] 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.

[0082] Example method

[0083] Figure 6The flowchart of a method 600 for page interaction according to some embodiments of the present disclosure is shown. The method 600 may 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 following exemplary embodiments, the process 800 is implemented at the terminal device 150. The following references Figure 1 describe the process 600.

[0084] In block 610, the terminal device obtains a query request from the user.

[0085] In block 620, in response to the query request, the terminal device presents a target bill, where the target attribute of the target bill matches the query request, and the target attribute of the target bill is determined based on multiple sub-bills associated with the target bill or multiple payment methods associated with the target bill.

[0086] In some embodiments, the query request indicates the bill amount to be queried, and the target attribute is used to indicate the cumulative payment amount of the target bill, or the payment amount corresponding to any one of the multiple payment methods associated with the target bill.

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

[0088] In some embodiments, in response to the selection of a target sub-bill among the multiple sub-bills, the terminal device presents a details page of the target sub-bill.

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

[0090] In some embodiments, the terminal device determines at least one account associated with the user, and determines a target bill that matches the query request from multiple historical bills associated with the at least one account.

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

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

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

[0094] In some embodiments, the combined bill information further indicates the cumulative bill amount of the target bill.

[0095] 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 the following process: 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 storing payment information corresponding to the multiple payment channels in a plurality of sub-bill entries.

[0096] Example device and equipment

[0097] Figure 7 FIG. shows a schematic structural block diagram of a device 700 for page interaction according to certain embodiments of the present disclosure. The device 700 may be implemented as or included in a terminal device 150. Each module / component in the device 700 may be implemented by hardware, software, firmware, or any combination thereof.

[0098] As Figure 7 shown, the bill query device 700 includes: a retrieval request acquisition module 710 configured to acquire a query request of a user; and a bill presentation module 720 configured to present a target bill, wherein a target attribute of the target bill matches the query request, and 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.

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

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

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

[0102] In some embodiments, the target bill is associated with multiple payment methods, and the apparatus 700 further includes a payment method presentation module, configured to: in response to a selection of the target bill, present a second information page; and present payment amounts corresponding to the multiple payment methods respectively in the second information page.

[0103] In some embodiments, the bill presentation module 720 is further configured to: determine at least one account associated with the user; and determine a target bill that matches the query request from among a plurality of historical bills associated with the at least one account.

[0104] In some embodiments, the user is currently logged in to a first account, and the bill presentation module 720 is further configured to: in response to determining that none of the historical bills associated with the first account match 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 associated with the user.

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

[0106] In some embodiments, the plurality of sub-bills are determined based on the following process: determining a set of candidate bill entries from among a plurality of bill entries in a bill database, where the combined payment information corresponding to the set of candidate bill entries matches the query request; and determining a plurality of sub-bills corresponding to the same combined bill identifier based on the combined bill information indicated by the set of candidate bill entries, and the target bill corresponds to the combined bill identifier.

[0107] In some embodiments, the combined bill information further indicates the cumulative bill amount of the target bill.

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

[0109] Figure 8 A block diagram of an electronic device 800 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that Figure 8The illustrated electronic device 800 is merely exemplary and should not impose any limitation on the functionality and scope of the embodiments described herein. Figure 8 The illustrated electronic device 800 can be used to implement Figure 1 the terminal device 150.

[0110] As Figure 8 illustrated, the electronic device 800 is in the form of a general-purpose electronic device. The 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 an actual or virtual processor and is capable of performing various processes according to the programs stored in the memory 820. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capability of the electronic device 800.

[0111] The electronic device 800 generally includes multiple computer storage media. Such media can be any accessible media that can be obtained by the electronic device 800, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 820 can be a volatile memory (such as registers, caches, random access memory (RAM)), a non-volatile memory (such as 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 medium and can include machine-readable media, such as a flash drive, a magnetic disk, or any other medium that can be used to store information and / or data (such as training data for training) and can be accessed within the electronic device 800.

[0112] The electronic device 800 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown Figure 8 herein, a disk drive for reading from or writing to a removable, non-volatile magnetic disk (such as a "floppy disk") and an optical disk drive for reading from or writing to a removable, non-volatile optical disk can be provided. In these cases, each drive can be connected to a 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 that are configured to execute various methods or actions of the various embodiments of the present disclosure.

[0113] The communication unit 840 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 800 may be implemented in a single computing cluster or multiple computing machines that are capable of communicating via a communication link. Thus, the electronic device 800 may operate in a networked environment using a logical connection to one or more other servers, network personal computers (PCs), or another network node.

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

[0115] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, the computer program product being tangibly stored on a non-transitory computer-readable medium and including computer-executable instructions, and the computer-executable instructions being executed by a processor to implement the method described above.

[0116] Aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and the combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0117] These computer-readable program instructions may be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, thereby producing a machine such that when the instructions are executed by the processing unit of the computer or other programmable data processing apparatus, a device is created that implements the functions / acts specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium, which instructions cause a computer, a programmable data processing apparatus, and / or other devices to operate in a particular manner, so that the computer-readable medium storing the instructions includes a manufacture, which includes instructions for implementing various aspects of the functions / acts specified in one or more blocks of the flowchart and / or block diagram.

[0118] Computer-readable program instructions may be loaded onto a computer, other programmable data processing apparatus, or other devices, causing a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other devices to generate a computer-implemented process, such that the instructions executed on the computer, other programmable data processing apparatus, or other devices implement the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0119] The flowcharts and block diagrams in the figures 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 flowchart or block diagram may represent a module, a segment of a program, or a portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two consecutive blocks may in fact be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or actions, or by a combination of dedicated hardware and computer instructions.

[0120] The various implementations of the present disclosure have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art in the field of the technology without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, the practical application, or the improvement of the technology in the market, or to enable other ordinary skilled artisans in the field of the technology to understand the various implementations disclosed herein.

Claims

1. A bill query method, comprising: Obtaining a query request from a user, where the query request indicates a bill amount to be queried; as well as In response to the query request, presenting a target bill, the target attribute of the target bill matches the query request, the target bill includes a bill constructed by merging and paying multiple sub-bills or a single order paid through multiple payment channels, and the target attribute is used to indicate: the cumulative payment amount of the target bill, or the payment amount corresponding to any one of the multiple payment channels associated with the target bill; The target attribute of the target bill is determined based on the multiple sub-bills associated with the target bill or the multiple payment methods associated with the target bill.

2. The method according to claim 1, wherein the target bill is associated with the plurality of sub-bills, the method further comprising: In response to selection of the target bill, presenting a first information page; as well as Sub-bill information corresponding to the plurality of sub-bills is presented in the first information page, and the sub-bill information at least indicates the amounts of the corresponding sub-bills.

3. The method according to claim 2, further comprising: In response to selection of a target sub-bill among the multiple sub-bills, a detail page of the target sub-bill is presented.

4. The method according to claim 1, wherein the target bill is associated with the plurality of payment methods, the method further comprising: In response to selection of the target bill, presenting a second information page; as well as The payment amounts corresponding to the multiple payment methods are presented in the second information page.

5. The method according to claim 1, wherein presenting the target bill comprises: determining at least one account associated with the user; as well as The target bill matching the query request is determined from a plurality of historical bills associated with the at least one account.

6. The method of claim 5, wherein the user is currently logged into a first account, and determining at least one account associated with the user comprises: In response to the authentication control being activated, presenting an authentication interface; Acquiring authentication information via the authentication interface; as well as In response to the authentication information being verified, at least one second account associated with the user is determined.

7. The method according to claim 6, further comprising: The authentication control is presented based on determining that all historical bills associated with the first account do not match the query request.

8. The method of claim 1, wherein presenting the target bill comprises: In response to a plurality of historical bills matching the query request, the plurality of historical bills are presented based on a time sequence of the plurality of historical bills.

9. The method of claim 1, wherein the plurality of sub-bills are determined based on the following process: Determining a group of candidate billing items from a plurality of billing items in a billing database, wherein the combined payment information corresponding to the group of candidate billing items matches the query request; and Based on the consolidated bill information indicated by the set of candidate bill entries, the multiple sub-bills corresponding to the same consolidated bill identifier are determined, and the target bill corresponds to the consolidated bill identifier.

10. The method according to claim 9, wherein the combined bill information further indicates a cumulative bill amount of the target bill.

11. 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 the following process: In response to the target bill being paid through the multiple payment methods, the target bill entry corresponding to the target bill is constructed in the bill database, and the target bill entry stores payment information corresponding to the multiple payment methods.

12. A bill query device, comprising: A retrieval request acquisition module is configured to acquire a query request from a user, wherein the query request indicates a bill amount to be queried; as well as a bill presenting module, configured to present a target bill, wherein a target attribute of the target bill matches the query request, the target bill comprises a bill constructed by merging and paying a plurality of sub-bills or a single order paid through a plurality of payment channels, and the target attribute is used to indicate: a cumulative payment amount of the target bill, or a payment amount corresponding to any one of the plurality of payment channels associated with the target bill; The target attribute of the target bill is determined based on the multiple sub-bills associated with the target bill or the multiple payment methods associated with the target bill.

13. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 11 when executed by the at least one processing unit.

14. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 11.

15. A computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to any one of claims 1 to 11.

Images