Bill query method and device, equipment and storage medium
By obtaining user query requests in the bill query system and matching the attributes of the target bill, the problem of the information association of traditional bill query methods that cannot handle combined payment and combined payment is solved, and the bill query function in complex transaction scenarios is realized to satisfy users query requirements.
Patent Information
- Application Number
- CN202410962338.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-07-17
AI Technical Summary
Traditional bill query methods cannot meet users' query needs when making combined bill payments or combined payments, and cannot effectively associate and display information about combined bills or combined payments, resulting in users being unable to query specific consumption records.
By obtaining the user's query request, the target bill is presented. The target attributes of the target bill are determined based on multiple sub-bills or multiple payment channels associated with the target bill, ensuring that the user can query the corresponding bill even if the combined payment or combined payment is made. information.
The query functions of combining the bill and combining the bill are realized, and users can query transaction details more comprehensively to meet the query needs in complex transaction scenarios.
Smart Images

Figure CN118964710A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more 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 work and life. For example, users can trade on the Internet to obtain the services or goods they expect. In the process of trading, users need to pay corresponding virtual resources. The virtual resources in this article 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 users to query their historical bills. In real transaction scenarios, payment methods are becoming more and more complicated. For example, users can pay multiple bills together or pay a single order through multiple payment methods. As payment methods become more and more complex and diverse, traditional query solutions can no longer meet users' query needs. 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 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, wherein 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. In this way, even if the user pays multiple bills jointly or pays a single bill through multiple payment methods, the corresponding bill information can still be queried when the user performs a bill query operation.
[0004] In a second aspect of the present disclosure, a bill query device is provided. The device includes: a retrieval request acquisition module configured to acquire a query request from a user; and a bill presentation module configured to present a target bill, the target attribute of the target bill matching the query request, wherein 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.
[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 is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.
[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein 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, which is tangibly stored in a computer storage medium and includes computer executable instructions, which, when executed by a device, cause the device to perform the method of the first aspect or the second aspect.
[0008] It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended 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] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0010] Figure 1 A schematic diagram showing an example environment in which 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 of a bill query method according to some embodiments of the present disclosure is shown;
[0015] Figure 6 A flowchart of a bill query method according to some embodiments of the present disclosure is shown;
[0016] Figure 7 A schematic structural block diagram of a bill query device according to some embodiments of the present disclosure is shown; and
[0017] Figure 8 A block diagram of an electronic device is shown in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION
[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0019] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part 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". Other explicit and implicit definitions may also be included below.
[0020] Herein, unless explicitly stated, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.
[0021] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.
[0022] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, 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 in an appropriate manner in accordance with relevant laws and regulations.
[0023] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information, so that the user can independently choose whether to provide personal information to software or hardware such as electronic devices, applications, servers or storage media that execute operations of the technical solution of the present disclosure based on the prompt message.
[0024] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information is sent to the user in a manner such as a pop-up window, in which the prompt information can be presented in text form. In addition, the pop-up window can 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 notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0026] The term "in response to" as used herein refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of executing a subsequent action executed in response to the event or condition is not necessarily strongly related to the time when the event occurs or the condition is satisfied. For example, in some cases, the subsequent action may be executed immediately when the event occurs or the condition is satisfied; while in other cases, the subsequent action may be executed some time after the event occurs or the condition is satisfied.
[0027] As briefly discussed above, with the development of network technology, various terminal devices can provide people with various services in work and life. For example, users can trade on the Internet to obtain their desired services or goods. In the process of trading, users need to pay corresponding virtual resources. The virtual resources in this article can be funds, coupons, various points, etc.
[0028] Currently, service providers can provide users with bill query functions. However, when users use the bill amount query function, they often only know how much money they spent, but cannot remember what they bought specifically. In other words, users expect to be able to query historical bills corresponding to the specified consumption amount. This demand is more common on bank billing days. For example, users have questions about a certain consumption record on their bank cards and expect to further query the bills on the transaction platform to obtain detailed consumption information. In traditional solutions, 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 entered by the user are matched with the target attributes of the bill stored in the bill data to output the bill query results.
[0029] However, as briefly discussed above, real Internet transaction scenarios are complex and diverse. For example, in a real transaction process, a user can make a combined payment for multiple bills, which for the sake of discussion will be referred to as "combined payment" in this article, or pay a single bill through multiple payment methods, which for the sake of discussion will be referred to as "combined payment" in this article. As discussed above, in traditional solutions, the service platform uses each bill as a storage unit. In this case, when the user performs a bill query, since the combined payment information and the combined payment information are not recorded in the bill information in an associated manner, the bills involving combined payment and combined payment cannot be queried. The above issues will be explained in more detail in conjunction with the following example scenarios.
[0030] As an example scenario, a user places an order for a first product worth 10 yuan in store A, and at the same time places an order for a second product worth 15 yuan in store B. When making payment, the user uses the first payment account to pay for the combined order. For this specific scenario, in the service platform, the consumption record of the first product is stored as a first bill with an amount of 10 yuan, and the consumption record of the second product is stored as a second bill with an amount of 15 yuan. However, a consumption record of 25 yuan is generated in the user's first payment account. When the user queries the consumption record in the first payment account, he expects to know the details of the consumption record corresponding to the 25 yuan. At this time, when the user queries the bill in the service platform with a consumption amount of 25, the query result is 0.
[0031] In another example scenario, a user consumes a third commodity worth 45 yuan in store C, of which 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 commodity is stored as a third bill with an amount of 45 yuan. However, a consumption record of 25 yuan is generated in the user's first payment account, and a consumption record of 20 yuan is generated in the user's second payment account. When the user views the consumption record of his first payment account, he expects to obtain the details of the consumption record corresponding to the 25 yuan. At this time, when the user queries the bill in the service platform with the consumption amount of 25, the query result is 0.
[0032] At least through the above example embodiments, it can be seen that as transaction methods become more and more complex and diverse, traditional query methods cannot meet the query needs of users. If the service platform does not support querying related bills using combined payment or combined payment, users can only view historical bills one by one.
[0033] According to an embodiment of the present disclosure, a bill query method, apparatus, device and storage medium are provided. The method includes: obtaining a query request from a user; and in response to the query request, presenting a target bill, wherein the target attribute of the target bill matches the query request, wherein 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. In this way, even if the user pays multiple bills together or pays a single bill through multiple payment methods, the corresponding bill information can still be queried when the user performs a bill query operation.
[0034] Various embodiments of the present disclosure will be further described below in conjunction with the accompanying drawings.
[0035] Example Environment
[0036] Figure 1A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In the example 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] exist Figure 1 In the environment 100, if the application 120 is in an active state, the terminal device 150 can present a page 160 of the application 120. The page 160 can include various pages that the application 120 can provide, such as an information display page, a consumption page, a bill query page, and the like.
[0038] In some embodiments, the terminal device 150 can communicate with the server 130 to realize 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 mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication systems (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio broadcast receivers, e-book devices, gaming devices, 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 interface for the user (such as "wearable" circuits, etc.). The server 130 can be various types of computing systems / servers that can provide computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like.
[0039] In some embodiments, the terminal device 150 can cooperate with the server 130 to provide a specific service for the user 140. In some example embodiments of the present disclosure, the example process is described with the terminal device 150 as the execution subject. It should be understood that the described example process can be implemented by the terminal device 150 and the server 130 in cooperation. For the purpose of brevity only, the same or similar content will not be repeated.
[0040] It should be understood that the structure and function of each element in the environment 100 are described for exemplary 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.
[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 inquiry process of the present disclosure in detail, first refer to Figure 2 A schematic diagram 200 of a data structure 200 of a bill store according to some embodiments of the present disclosure is shown.
[0044] like Figure 2 As shown, for each bill, the data structure 200 stores the following metadata: bill identifier, transaction number, bill title, transaction amount, etc. Furthermore, when the bill involves a combined payment, the data structure 200 further stores the combined bill information. The combined bill information includes but is not limited to: total transaction amount / accumulated bill amount, combined bill number, and other information.
[0045] The example embodiment including the consolidated bill information is now further discussed in conjunction with the following example. In operation, if user 140 pays for multiple items in one consumption behavior, for example, the user orders a first item worth 10 yuan in store A, and the user orders a second item worth 15 yuan in store B. When making a payment, user 140 uses the first payment account to make a consolidated payment. In this case, the above consumption records can be saved as two bills, for example, bill #1 and bill #2. Bill #1 stores: bill identification #1, transaction number #1, bill title #1, transaction amount 15, and stores consolidated bill information, including a total transaction amount of 25, a consolidated bill number, etc. Bill #2 stores: bill identification #2, transaction number #2, bill title #2, transaction amount 10, and stores consolidated bill information, including a total transaction amount of 25, a consolidated bill number, etc.
[0046] Through the above operation, the detailed information of the combined payment can be retained in each bill. When performing a query operation, when the user uses the transaction amount 25 as a keyword to query, bill #1 and bill #2 can be queried, and based on the same combined bill 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 users with more comprehensive query results.
[0047] Furthermore, when the bill involves a combined payment, the data structure 200 further stores the 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 can 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 multiple sub-bill entries store payment information corresponding to the multiple payment channels.
[0049] The scenario involving combined payment information is now further discussed in conjunction with the following example. In operation, if user 140 consumes a third commodity worth 45 yuan in store C, 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. Bill #3 stores: bill identification #3, transaction order number #3, bill title #3, transaction amount 45, and 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 operation, the detailed information of the combined payment can be retained in each bill. When performing a query operation, when the user uses the transaction amount 25 as a keyword to query, bill #3 can be queried. In this way, the bill query operation can cover the combined payment scenario, thereby providing users with a more comprehensive query result.
[0051] Furthermore, when the bill involves the use of a coupon, data structure 200 further stores preferential information. In some embodiments, the preferential information is stored in parallel with the combined payment information. Alternatively, the preferential information is used as a payment method involved in the combined payment information. As an example embodiment, a user has a coupon worth 500 yuan, and the coupon is used when paying bill #1 and bill #2. In this case, the coupon information is recorded in the data structure of bill #1 and bill #2. When performing a query operation, when the user uses the preferential information as a keyword to query, all historical bills related to the coupon can be queried.
[0052] Through the above operation, the preferential information used by the bill can be retained in each bill. In this way, the bill query operation can cover the scenario of using coupons to pay bills, thereby providing users with more comprehensive query results.
[0053] Next, we will combine Figures 3A to 4C The example user interfaces 300A to 400C shown are used to further describe the example bill query process of the present disclosure. It should be understood that Figures 3A to 4CThe user interfaces shown are merely examples, and various designs may exist in practice. For example, the various graphical elements and / or controls in the user interface may have different arrangements and different visual representations, one or more of the elements and / or controls may be omitted or replaced, and one or more other elements and / or controls may also exist. In addition, any appropriate content may be included in the user interface. The scope of the present disclosure is not limited in this respect.
[0054] In an example embodiment of the present disclosure, the example user interfaces 300A to 400C may be implemented at the terminal device 150 , which may be any page of the application 120 .
[0055] In operation, the terminal device 150 obtains a query request from a user. In response to the query request, the terminal device 150 presents a target bill, wherein the target attribute of the target bill matches the query request.
[0056] According to various embodiments of the present disclosure, in some scenarios, the target attribute of the target bill can be determined based on multiple sub-bills associated with the target bill. Alternatively or additionally, the target attribute of the target bill can be determined based on multiple payment methods associated with the target bill.
[0057] In some embodiments, multiple sub-bills are determined based on the following process: determining a group of candidate bill entries from multiple bill entries in a bill database, and the consolidated payment information corresponding to the group of candidate bill entries matches the query request; and based on the consolidated bill information indicated by the group of candidate bill entries, determining multiple sub-bills corresponding to the same consolidated bill identifier, and the target bill corresponds to the consolidated bill identifier.
[0058] In some embodiments, the terminal device 150 obtains a query request, wherein the query request indicates a target bill amount. In response to the query, the terminal device 150 may 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, wherein the first bill includes a plurality of sub-bills, the cumulative bill amount of the plurality of sub-bills matches the target bill amount, and the second bill is associated with a plurality of payment channels, the cumulative payment amount of the plurality of payment channels matches the target bill amount.
[0059] refer to Figure 3AExample user interface 300A shown. Example user interface 300A includes query bar 301. User 140 can enter keywords, such as consumption amount, coupon, product name, consumption category, etc. through query bar 301. If user 140 enters the consumable amount in query bar 301, terminal device 150 can present user interface 300B. In user interface 300B, 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 a historical bill 312, which is a transaction record of a combined bill payment. In this case, the target attribute is the cumulative payment amount of the combined bill 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 methods associated with the target bill. For example, the user interface 300B includes a historical bill 313, which is a combined payment transaction record. In this case, the target attribute is the payment amount corresponding to any one of the payment methods in the combined payment bill.
[0062] In some embodiments, in response to multiple historical bills matching the query request, the terminal device presents multiple historical bills based on the time sequence of the multiple historical bills. Referring to the example user interface 300B, historical bills 311 to 313 are presented in chronological order, wherein updated historical bills are presented at a more advanced position.
[0063] Additionally, multiple historical orders may be presented in a cluster. In some embodiments, multiple historical bills may be presented in a cluster according to a predetermined time unit, such as by month, by quarter, etc. In some embodiments, multiple historical bills may also be presented in a cluster according to a predetermined type, such as shopping mall consumption, transfer, etc.
[0064] Further, in the query result display interface, the user 140 can click on any bill to view the details of the bill. For example, when the user 140 clicks to view the bill 311, the terminal device 150 presents the 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, transaction order number, product details, etc. Further, the example user interface 300C may also include merchant information and after-sales service controls, etc.
[0065] In some embodiments, the 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, wherein the sub-bill information at least indicates the amount of the corresponding sub-bill. For example, when the user 140 clicks to view the bill 312, the terminal device 150 may present an 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 detailed information of the sub-bill 331 and the sub-bill 332 and the respective consumption amounts.
[0066] In some embodiments, in response to selecting a target sub-bill from among the multiple sub-bills, the terminal device 150 may present a detail page of the target sub-bill. For example, when the user 140 selects any sub-bill from among sub-bill 331 and sub-bill 332, the terminal device 150 may present the bill details of the 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 can present a second information page. In the second information page, the terminal device 150 can present the payment amounts corresponding to the multiple payment methods. For example, when the user 140 clicks to view the bill 313, the terminal device 150 can present an 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, change and savings card. In this case, the example user interface 300E displays payment details 341, including the payment amounts corresponding to the multiple payment methods.
[0068] In some embodiments, the terminal device 150 may determine at least one account associated with the user 140 , and determine a target bill matching the query request from a plurality of historical bills associated with the at least one account.
[0069] In some scenarios, user 140 may be associated with multiple accounts. In this case, the query scope of the bill may be determined and the corresponding query results may be returned based on the current authorization authentication information of user 140. Specifically, when terminal device 150 has the first authorization authentication information of user 140, terminal device 150 may perform a query operation in the first account set of user 140, and when terminal device 150 has the second authorization authentication information of user 140, terminal device 150 may perform a query operation in the second account set of user 140.
[0070] In some embodiments, the current login of user 140 is a first account. In response to the authentication control being activated, terminal device 150 may present an authentication interface. Further, terminal device 150 may obtain authentication information via the authentication interface. In response to the authentication information being verified, terminal device 150 may determine at least one second account associated with user 140. Figure 3B and 3F The example user interfaces 300B and 300F shown 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 the following Figure 4A The example authentication interface 400A shown is, for example, a face recognition interface. If the authentication is successful, the terminal device 150 may present an example user interface 400B to receive a query request from the user 140. According to the query request input by the user 140, the terminal device 150 may present an example user interface 400C, that is, presenting query results in multiple associated accounts.
[0071] Alternatively, in response to the authentication being passed, the terminal device 150 may directly present the example user interface 400C. That is, the terminal device 150 automatically performs a query operation corresponding to the last bill query request input by the user 140 in multiple associated accounts.
[0072] In some embodiments, based on determining that none of the historical bills associated with the first account number matches the query request, the terminal device 150 may present the authentication control. For example, when the user 140 enters the search amount of 25 in the example user interface 300A, the terminal device 150 does not find 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 have been found, and guides the user 140 to perform further authentication or obtain query authority for the second account.
[0073] For a better understanding of the above process, see Figure 5A A flowchart of a bill query method 500A according to some embodiments of the present disclosure is shown.
[0074] In 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. In block 502, the terminal device 150 determines whether the query content is of the amount type. If the query content is determined not to be of the amount type, in block 503, the terminal device 150 fuzzy matches the bill title according to the obtained query content, and in block 504, filters the query results that meet the conditions.
[0075] 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 in box 504. If it is determined to be of the text type, in box 506, the bill title is fuzzy matched, and in box 511, the query results that meet the conditions are screened.
[0076] If it is determined in box 505 that the input type is a numeric type, the amount is classified in 507, and in boxes 508 to 510, the transaction information in the bill data structure is matched respectively, including the transaction amount, the total transaction amount in the combined order information, and the transaction amount in the combined payment information, and in box 511, the query results that meet the conditions are screened.
[0077] See also Figure 5B A flowchart of a bill query method 500B according to some embodiments of the present disclosure is shown.
[0078] In block 551 , the terminal device 150 optionally determines whether the query result is empty. If the query result is not empty, then in block 553 , the terminal device 150 sorts the query result based on the transaction time, and displays the query result in block 554 .
[0079] If it is determined whether the query result is empty, it is determined in box 552 whether the user 140 triggers further authentication. If the user 140 does not trigger further authentication, the terminal device 150 ends the current query process. If it is determined that the user 140 triggers further authentication, the terminal device 150 determines whether there are multiple accounts under the user name in box 552. If it is determined that there are no multiple accounts, it is determined in box 556 that the query result is empty and in box 554, the query result is displayed.
[0080] If it is determined that there are multiple accounts, then in box 557, a bill query tool entrance is provided. In box 558, the user 140 can provide authentication information by scanning the face. If the authentication information is passed, in box 559, the terminal device 150 receives the query date and the exact amount input by the user. In box 560, the terminal device 150 accurately matches the order transaction information of each account, and in box 561, the terminal device 150 merges the query results of multiple accounts. In box 562, the terminal device 150 sorts the query results based on the transaction time. In box 554, the query results are displayed.
[0081] Through the above process, users can more easily query the historical bills corresponding to the consumption records of the payment account, regardless of whether the historical bills are combined payments or combined payments.
[0082] Example Method
[0083] Figure 6800 is a flowchart of a method 600 for page interaction according to some embodiments of the present disclosure. The method 600 may be implemented at the terminal device 150 (or implemented by the terminal device 150 and the server 130). For ease of discussion, in the following example embodiment, the process 800 is implemented at the terminal device 150. Figure 1 Process 600 is described.
[0084] In block 610 , the terminal device obtains a query request from a user.
[0085] In box 620, the terminal device presents a target bill in response to the query request, and the target attributes of the target bill match the query request, wherein the target attributes of the target bill are 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 selection of a target sub-bill from among the multiple sub-bills, the terminal device presents a detail 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 payment amounts corresponding to the multiple payment methods 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 matching the query request from a plurality of historical bills associated with the at least one account.
[0091] In some embodiments, the user is currently logged into a first account, and the terminal device presents an authentication interface in response to determining that none of the historical bills associated with the first account match the query request. Further, authentication information is obtained via the authentication interface; and in response to the authentication information being verified, the terminal device determines at least one second account associated with the user.
[0092] 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.
[0093] In some embodiments, multiple sub-bills are determined based on the following process: determining a group of candidate bill entries from multiple bill entries in a bill database, and the consolidated payment information corresponding to the group of candidate bill entries matches the query request; and based on the consolidated bill information indicated by the group of candidate bill entries, determining multiple sub-bills corresponding to the same consolidated bill identifier, and the target bill corresponds to the consolidated bill identifier.
[0094] In some embodiments, the consolidated bill information also indicates a cumulative bill amount of the target bill.
[0095] In some embodiments, the target bill corresponds to a target bill entry in a billing 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, a target bill entry corresponding to the target bill is constructed in the billing database, and multiple sub-bill entries store payment information corresponding to the multiple payment channels.
[0096] Example devices and equipment
[0097] Figure 7 A schematic structural block diagram of an apparatus 700 for page interaction according to some embodiments of the present disclosure is shown. The apparatus 700 may be implemented as or included in a terminal device 150. Each module / component in the apparatus 700 may be implemented by hardware, software, firmware, or any combination thereof.
[0098] like Figure 7 As shown, the bill query device 700 includes: a retrieval request acquisition module 710, configured to obtain a user's query request; and a bill presentation module 720, configured to present a target bill, wherein the target attribute of the target bill matches the query request, wherein 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.
[0099] 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.
[0100] In some embodiments, the target bill is associated with multiple sub-bills, and the device 700 also includes a sub-bill presentation module, which is configured to present a first information page in response to selection of the target bill; and present 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.
[0101] In some embodiments, the device 700 also includes a sub-bill details presentation module configured to: in response to selection of a target sub-bill among the multiple 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 device 700 also includes a payment method presentation module, which is configured to: present a second information page in response to selection of the target bill; and present payment amounts corresponding to the multiple payment methods 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 matching the query request from a plurality of historical bills associated with the at least one account.
[0104] In some embodiments, the user is currently logged in to the first account, and the bill presentation module 720 is also configured to: in response to determining that all historical bills associated with the first account do not 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 present the multiple historical bills based on the time sequence of the multiple historical bills in response to the multiple historical bills matching the query request.
[0106] In some embodiments, multiple sub-bills are determined based on the following process: determining a group of candidate bill entries from multiple bill entries in a bill database, and the consolidated payment information corresponding to the group of candidate bill entries matches the query request; and based on the consolidated bill information indicated by the group of candidate bill entries, determining multiple sub-bills corresponding to the same consolidated bill identifier, and the target bill corresponds to the consolidated bill identifier.
[0107] In some embodiments, the consolidated bill information also indicates a cumulative bill amount of the target bill.
[0108] In some embodiments, the target bill corresponds to a target bill entry in a billing 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, a target bill entry corresponding to the target bill is constructed in the billing database, and multiple sub-bill entries store payment information corresponding to the multiple payment channels.
[0109] Figure 8 8 is a block diagram of an electronic device 800 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 8The electronic device 800 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 8 The electronic device 800 shown can be used to implement Figure 1 terminal device 150.
[0110] like Figure 8 As shown, the electronic device 800 is in the form of a general electronic device. The components of the electronic device 800 may 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 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 820. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 800.
[0111] The electronic device 800 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 800, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 820 may be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 830 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data (e.g., training data for training) and may be accessed within the electronic device 800.
[0112] The electronic device 800 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 8 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 820 may include a computer program product 825 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.
[0113] The communication unit 840 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 800 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 800 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
[0114] The input device 850 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 860 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 800 may also communicate with one or more external devices (not shown) through the communication unit 840 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 800, or communicate with any device that allows the electronic device 800 to communicate with one or more other electronic devices (e.g., a network card, a 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, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.
[0116] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0117] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0118] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0119] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0120] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art 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, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.
Claims
1. A bill query method, comprising: Get the user's query request; as well as In response to the query request, presenting a target bill, the target attribute of the target bill matching the query request, 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.
2. The method according to claim 1, wherein the query request indicates a bill amount to be queried, and the target attribute is used to indicate one of the following: The cumulative payment amount of the target bill, or A payment amount corresponding to any one of the multiple payment methods associated with the target bill.
3. 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.
4. The method according to claim 3, 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.
5. The method according to claim 1, wherein the target bill is associated with the multiple 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.
6. The method of 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.
7. The method of claim 6, 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.
8. The method according to claim 7, 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.
9. 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.
10. 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. The method according to claim 10 , wherein the combined bill information further indicates a cumulative bill 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 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 multiple sub-bill entries store payment information corresponding to the multiple payment methods.
13. A bill query device, comprising: A search request acquisition module is configured to acquire a user's query request; 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 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.
14. 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 12 when executed by the at least one processing unit.
15. 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 12.
16. 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 12.
Citation Information
Patent Citations
Recording and inquiring method, device and electronic device for bill installment event
CN109508975A
Composite bill generation method, device and equipment and computer storage medium
CN110020089A
Order payment method and device, storage medium and electronic equipment
CN114819938A
Multi-account combined payment method and device, electronic equipment and storage medium
CN115936705A
Method and system for facilitating payment of credit card bills
US20160275463A1
