CN112947814A

CN112947814A - Bill counting method and bill counting device

Info

Publication number: CN112947814A
Application number: CN202110373244.4A
Authority: CN
Inventors: 李磊
Original assignee: Vivo Mobile Communication Hangzhou Co Ltd
Current assignee: Vivo Mobile Communication Hangzhou Co Ltd
Priority date: 2021-04-07
Filing date: 2021-04-07
Publication date: 2021-06-11

Abstract

The application discloses a bill counting method and a bill counting device, and belongs to the technical field of electronic equipment. The method comprises the following steps: under the condition that icon positions of at least two target applications are detected to meet preset conditions, acquiring bill data of the at least two target applications, wherein the target applications are applications with payment functions; and generating a target bill according to the bill data of the at least two target applications and a preset period.

Description

Bill counting method and bill counting device

Technical Field

The application belongs to the technical field of electronic equipment, and particularly relates to a bill counting method and a bill counting device.

Background

With the development of internet technology, mobile payment is becoming a common payment means for people. At present, a user generally uses a plurality of applications with a payment function to pay, and if the user needs to count bills of the plurality of applications, the user needs to obtain bills corresponding to each application under each application, and then the user manually collects the bills of the plurality of applications.

Therefore, the technical problem that the process of carrying out bill statistics on a plurality of applications is complex exists in the prior art.

Disclosure of Invention

The embodiment of the application aims to provide a bill counting method and a bill counting device, which can solve the technical problem that the process of carrying out bill information counting on a plurality of applications is complex in the prior art.

In a first aspect, an embodiment of the present application provides a bill counting method, where the method includes:

under the condition that icon positions of at least two target applications are detected to meet preset conditions, acquiring bill data of the at least two target applications, wherein the target applications are applications with payment functions;

and generating a target bill according to the bill data of the at least two target applications and a preset period.

In a second aspect, an embodiment of the present application provides a bill counting apparatus, including:

the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring bill data of at least two target applications under the condition that icon positions of the at least two target applications are detected to meet preset conditions, and the target applications are applications with payment functions;

and the generation module is used for generating a target bill according to the bill data of the at least two target applications and the preset period.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

In the embodiment of the application, when a user needs to perform bill counting on a plurality of applications including a payment function, icon positions of the plurality of applications can be set to meet a preset condition, so that the bill counting device can acquire bill data of the applications under the condition that the icon positions of the plurality of applications meet the preset condition, and generate a target bill according to the acquired bill data and a preset period. Therefore, the method and the device for billing statistics can simplify the process of billing statistics on the plurality of applications, and enable the user to obtain billing statistical data of the plurality of applications more conveniently.

Drawings

Fig. 1 is a schematic flowchart of a bill counting method according to an embodiment of the present application;

fig. 2 is an exemplary diagram of two target applications provided in an embodiment of the present application, where icon positions of the two target applications meet a preset condition;

FIG. 3 is an exemplary diagram of aggregated bills provided by embodiments of the present application;

FIG. 4 is an exemplary diagram of a classification statistic of aggregated bills provided by an embodiment of the present application;

FIG. 5 is an exemplary diagram of another classification statistic for aggregated bills provided by an embodiment of the present application;

FIG. 6 is an exemplary diagram of a setup interface provided by an embodiment of the present application;

FIG. 7 is an exemplary diagram of a resource transfer interface provided by an embodiment of the application;

FIG. 8 is a diagram of an example of a list of functions provided by an embodiment of the present application;

FIG. 9 is a diagram of another example of a list of functions provided by an embodiment of the present application;

FIG. 10 is an exemplary diagram of FIG. 9 corresponding to determining a corresponding function according to a sliding direction of a user's finger;

fig. 11 is a block diagram illustrating a bill counting apparatus according to an embodiment of the present disclosure;

fig. 12 is a block diagram of an electronic device according to an embodiment of the present disclosure;

fig. 13 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

The following describes the bill statistics provided by the embodiments of the present application in detail through specific embodiments and application scenarios thereof with reference to the accompanying drawings.

Fig. 1 shows a schematic flowchart of a bill counting method according to an embodiment of the present application.

Step 101: under the condition that icon positions of at least two target applications are detected to meet preset conditions, acquiring bill data of the at least two target applications, wherein the target applications are applications with payment functions;

step 102: and generating a target bill according to the bill data of the at least two target applications and a preset period.

The embodiment of the application can be executed by a bill counting device, and the bill counting device can be any electronic equipment provided with a payment application program, and the payment application program can comprise a payment function, but not limited to the payment function, and for example, the payment application program can also comprise an instant messaging function, a video playing function or a game function and the like.

In the embodiment of the present application, the bill counting apparatus may be installed with a plurality of payment-type applications, and the at least two target applications may be any two or more of the payment-type applications. The target application may be, for example, a bank-type application, an instant messaging application, and other payment-type applications. The payment function of the target application may include a transfer function, a payment function, a collection function, and the like.

The icon positions of the at least two target applications satisfy the preset condition, which may be understood as that the icons of the at least two target applications are in contact with each other, or the icons of the at least two target applications are shielded from each other, or the icons of the at least two target applications are located in a certain preset area, and so on. Further, in addition to being considered solely from the positional relationship, a duration for which at least two target applications satisfy the positional relationship may be considered. For example, when the time when the icons of the at least two target applications contact each other reaches a preset time, the icon positions of the at least two target applications may be considered to satisfy a preset condition.

When the user needs to count bills of a plurality of target applications, the icons of the plurality of target applications can be moved to a position where the positions of the icons of the plurality of target applications meet a preset condition. For example, the user may press an icon of a certain target application for a long time and drag the icon to an icon of another target application, or the user may press icons of two target applications for the same time and drag the two target applications to a certain preset area, and the like, which is not limited in the embodiment of the present application.

Fig. 2 shows an example in which a user moves icons of two target applications to make the icon positions of the two target applications satisfy a preset condition. As shown in fig. 2, the user long-presses the icon of the application a, and drags the icon of the application a to the area where the icon of the application b is located, and at this time, the positions of the icons of the application a and the application b meet the preset condition.

In step 101, the billing statistics apparatus may obtain billing data of at least two target applications when detecting that icon positions of the at least two target applications satisfy a preset condition.

The bill data acquired by the bill counting device may include data such as transaction date, transaction amount, transaction account, consumption type or transaction location.

In step 102, the bill counting device may generate a target bill according to the bill data of at least two target applications and a preset period.

The process of generating the target bill by the bill counting device may be understood as a process of aggregating bills of at least two target applications by the bill counting device to generate one target bill.

The preset period may include a period of month, quarter or year, and correspondingly, the target bill may be a target bill counted in the preset period of month, quarter or year. Taking the preset period as a month degree as an example, the target bill may include the balance (or called transaction) of each target application in each month, and the target bill may list the balance of each target application in each month in a list manner, or list the balance of each target application in each month in a graph manner. FIG. 3 shows an example of tabulating the balance of target applications per month.

Optionally, before the generating the target bill, the method further includes:

under the condition that the icon positions of at least two target applications are detected to meet preset conditions, displaying target operation objects, wherein the target operation objects comprise first operation objects;

receiving a first input of a user to the first operation object;

generating a target bill according to the bill data of the at least two target applications and a preset period, wherein the generating of the target bill comprises the following steps:

and responding to the first input, and generating a target bill according to the bill data of the at least two target applications and a preset period.

The implementation mode provides a technical scheme for triggering the bill counting device to aggregate bills of a plurality of applications through the operation object.

In this embodiment, the first operation object may be understood as a control for aggregating bills (may be referred to as an "aggregated bill" control for short), and the user may trigger the bill counting device to aggregate bills of the plurality of applications by operating the first operation object, or by using the first input acting on the first operation object, so as to generate the target bills counted in a preset period. By way of example, the user may trigger the bill counting device to aggregate bills of the plurality of applications through a click operation on the first operation object.

The first operation object may be identified in an icon form, may also be identified in a text form, and may also be identified in an icon form and a text form.

In this embodiment, triggering the bill aggregation by operating the object can prevent the bill counting apparatus from performing unnecessary bill aggregation due to a user's misoperation.

Optionally, the target operation object further includes a second operation object;

after the displaying the target operation object, the method further comprises:

receiving a second input of the user to the second operation object;

in response to the second input, generating classification statistics for the target bill from bill data for the at least two target applications.

The implementation mode provides a technical scheme for triggering the bill counting device to carry out aggregate counting on bills of a plurality of applications through the operation object. In this way, the bill counting apparatus has a function of performing aggregation counting of bills of a plurality of applications in addition to a function of performing aggregation counting of bills of a plurality of applications.

In this embodiment, the second operation object may be understood as a control for performing aggregate statistics on bills (which may be referred to as an "aggregate statistics" control for short), and the user may trigger the bill statistics apparatus to perform aggregate statistics on bills of multiple applications by operating the second operation object, or by using a second input acting on the second operation object, so as to generate the classification statistics data of the target bill. By way of example, the user may trigger the bill counting device to perform aggregate counting on bills of the plurality of applications through a click operation on the second operation object.

The second operation object may be identified in an icon form, may also be identified in a text form, and may also be identified in an icon form and a text form.

To more clearly understand the difference between the billing aggregation and the billing aggregation statistics, the following description is made in conjunction with fig. 3 and 4.

As described above, fig. 3 is a schematic diagram of bill aggregation to generate a target bill (which may be referred to as an "aggregated bill") counted in months. In fig. 3, the aggregated bill includes a list of the balances of each target application per month. As can be seen, bill aggregation refers to the process of aggregating multiple bills to generate an aggregated bill.

Fig. 4 is a schematic diagram of performing bill aggregation statistics to generate classification statistics of aggregated bills. In fig. 4, the classification statistics include the payment proportion or payment amount of each target application under each category. As can be seen, the bill aggregation statistics refers to a process of performing classification statistics on the aggregated bill to generate classification statistical data.

In this embodiment, the aggregated bill may be classified and counted in various forms, for example, the aggregated bill may be classified and counted in a list form, or the aggregated bill may be classified and counted in a chart form such as a sector chart, a pie chart, a bar chart, and the like. The classification method for performing classification statistics on the aggregated bills may also be various, for example, the classification statistics on the aggregated bills may be performed according to consumption types, the classification statistics on the aggregated bills may also be performed according to account types, and the like.

In the implementation mode, not only can bill aggregation be realized, but also bill aggregation statistics can be realized, and multiple requirements of a user on aggregation or aggregation statistics of bills of multiple target applications can be met.

Optionally, the generating, according to the bill data of the at least two target applications, classification statistical data of the target bills includes at least one of:

generating transaction data of the target bill classified according to a preset account in a target time period according to the bill data of the at least two target applications;

and generating transaction data of the target bill classified according to preset consumption types in a target time period according to the bill data of the at least two target applications.

In some embodiments, the aggregated bill may be classified and counted according to a preset account, where the preset account may be a specific account preset by a user (which may be called an affinity account), or the preset account may be one or more top-ranked accounts sorted according to transaction amount; and so on. For example, the user may preset the account of a specific customer as the preset account, or may preset the account of a specific relative or friend as the preset account. The number of the preset accounts may be one or multiple, and when the number of the preset accounts is multiple, the transaction data of each preset account of the target bill in the target time period may be generated respectively.

In some embodiments, the aggregated bill may be classified and counted according to a preset consumption type, where the preset consumption type may be a specific consumption type preset by a user, or the preset consumption type may be one or more consumption types ranked in the top in order according to a transaction amount, or the preset consumption type may be all consumption types; and so on.

In some embodiments, the aggregated bill may be classified and counted in a manner of classifying according to a preset account, or may be classified and counted in a manner of classifying according to a preset consumption type. Therefore, the bill counting device can respectively display different classified statistical data in different areas of the same display interface; and different classification statistical data can be respectively displayed on different display interfaces.

As an example, fig. 5 shows that the statistical data classified according to the consumption type and the statistical data classified according to the familiarity account are respectively displayed in different areas of the same display interface.

In some embodiments, the user can set the statistical time period (or statistical period) and the affinity account by himself through a pre-configured portal.

As an embodiment, the target operation object further includes an operation object (which may be referred to as a "setting" control for short) for setting a statistical period and an affinity account; upon receiving user input to the "settings" control, the bill counting apparatus displays a settings interface in response to the input. Fig. 6 illustrates an exemplary diagram of a setup interface that provides a statistical period setup window and an affinity account setup window, as shown in fig. 6.

Optionally, when it is detected that the icon positions of the first target application and the second target application meet the preset condition, the target operation object further includes a third operation object;

after the displaying the target operation object, the method further comprises:

receiving a third input of the third operation object from the user;

in response to the third input, displaying a resource transfer interface of the first target application to the second target application.

In this embodiment, the bill counting device has the functions of bill aggregation and bill aggregation counting as described above, and when it is detected that the positions of the icons of the two target applications satisfy the preset condition, the bill counting device may be triggered to display the resource transfer interface.

In this embodiment, the third operation object may be understood as a control (may be referred to as a "transfer" control for short) for triggering the bill counting device to display the resource transfer interface, and the user may trigger the bill counting device to display the resource transfer interface from the first target application to the second target application by operating the third operation object, or by using a third input acting on the third operation object. By way of example, the user may trigger the billing statistics apparatus to display the resource transfer interface from the first target application to the second target application by clicking on the third operation object. The third operation object may be identified in an icon form, may also be identified in a text form, and may also be identified in an icon form and a text form.

Fig. 7 is a diagram illustrating an example of a resource transfer interface from an application a (i.e., a first target application) to an application b (i.e., a second target application), where an account bound to the first target application is a resource transfer-out party and an account bound to the second target application is a resource transfer-in party. The determination of the first target application and the second target application may be determined based on preset settings of a user, may be determined based on historical transfer habits, may be determined based on a positional relationship of icons of the two target applications, and the like. At the resource transfer interface, the user may enter the transfer amount and enter a confirmation instruction, for example, by clicking on the "confirm roll out" control. Under the condition that a confirmation instruction input by a user is received, the bill counting device can send a transfer request to the server, wherein the transfer request can comprise account information bound to the first target application, account information bound to the second target application, transfer amount and other information. And after the server receives the transfer request, the identity authentication can be carried out, and after the identity authentication is passed, the resource matched with the transfer amount can be transferred from the account bound to the first target application to the account bound to the second target application.

In the implementation mode, bill aggregation can be achieved, one-key account transfer between accounts bound by different target applications can be achieved, and a more convenient and more diversified account transfer mode is provided for a user.

In some embodiments, after the receiving of the third input of the third operation object by the user, the method further includes:

checking whether the account of the first target application and the account of the second target application are bound or not;

the displaying the resource transfer interface from the first target application to the second target application includes:

and displaying a resource transfer interface from the first target application to the second target application under the condition that the account of the first target application and the account of the second target application are bound.

Optionally, the displaying a resource transfer interface of the first target application to the second target application in response to the third input includes:

and under the condition that the icon of the first target application is detected to be dragged to the icon of the second target application, responding to the third input, and displaying a resource transfer interface from the first target application to the second target application.

In this embodiment, the resource transfer-out direction and the resource transfer-in direction may be determined according to the icon dragging direction of the target application, where an account bound to the target application corresponding to the dragged icon may be determined as the resource transfer-out direction, and an account bound to the target application corresponding to the icon that is not dragged may be determined as the resource transfer-in direction.

In the embodiment, the resource transferring-out direction and the resource transferring-in direction are determined through the icon dragging direction, so that the operation is convenient and fast, and the operation habit of a user is met.

In some embodiments, when it is detected that the icon positions of the at least two target applications satisfy the preset condition, the bill counting apparatus may implement the functions of bill aggregation, bill aggregation statistics, and the like of the at least two target applications, implement the resource transfer function between the two target applications, and implement the functions of a statistics period or an in-person account setting, and the like, based on the needs of the user. The following description specifically illustrates that the icon positions of two target applications satisfy the preset condition as an example.

As shown in fig. 8 to 9, in the case where it is detected that the user drags the icon of the application a to the icon of the application b, that is, the positions of the icons of the application a and the application b satisfy the preset condition, the billing statistics apparatus may simultaneously display the first operation object 23, the second operation object 24, the third operation object 25, and the fourth operation object 26. The user can trigger the bill counting device by clicking different operation objects to realize the functions of bill aggregation, bill aggregation statistics, resource transfer, statistics period or setting of familiarity accounts and the like.

As an example, as shown in fig. 8, in the case that it is detected that the icon positions of the application a and the application b satisfy the preset condition, the bill counting apparatus may display a function list 2a, in which a first operand 23, a second operand 24, a third operand 25, and a fourth operand 26 are displayed, the first operand 23 being an "aggregated bill" control, the second operand 24 being an "aggregated statistics" control, the third operand 25 being a "transfer" control, and the fourth operand 26 being a "setting" control. For example, when the user clicks on the "aggregate bills" control, the bill statistics apparatus may aggregate the bills of application a and application b, generating the target bill as shown in fig. 3.

As another example, as shown in fig. 9, in the case where it is detected that the positions of the icons of the application a and the application b satisfy the preset condition, the bill counting apparatus may display a function dial 2b, in which a first operand 23, a second operand 24, a third operand 25, and a fourth operand 26 are displayed, the first operand 23 being a "bill" control, the second operand 24 being a "count" control, the third operand 25 being a "transfer" control, and the fourth operand 26 being a "setting" control. For example, when the user clicks the "statistics" control, the billing statistics apparatus may perform aggregate statistics on the bills of the application a and the application b, generating the classification statistics data as shown in fig. 4.

In addition, as shown in fig. 10, the bill counting device may also implement corresponding functions according to the direction in which the user's finger slides. For example, when the sliding direction of the finger of the user is upward, the bill counting device realizes the bill aggregation counting function; when the sliding direction of the fingers of the user is downward, the bill counting device realizes the function of counting the period or setting the familiarity account; when the sliding direction of the fingers of the user is leftward, the bill counting device realizes the function of transferring accounts; when the sliding direction of the fingers of the user is rightward, the bill counting device achieves a bill aggregation function.

In summary, the method and the device for billing statistics can simplify the billing statistics process of multiple applications, so that a user can acquire billing statistics data of multiple applications more conveniently.

It should be noted that, in the bill counting method provided in the embodiment of the present application, the execution subject may be a bill counting apparatus, or a control module in the bill counting apparatus for executing the bill counting method. In the embodiment of the present application, a bill counting device is taken as an example to execute a bill counting method, and the bill counting device provided in the embodiment of the present application is described.

Fig. 11 shows a schematic structural diagram of a bill counting apparatus according to an embodiment of the present application.

As shown in fig. 11, the bill counting apparatus 300 includes:

an obtaining module 301, configured to obtain, when it is detected that icon positions of at least two target applications meet a preset condition, bill data of the at least two target applications, where the target applications are applications including a payment function;

the first generating module 302 is configured to generate a target bill according to the bill data of the at least two target applications and the preset period.

Optionally, the bill counting apparatus 300 further includes:

the first display module is used for displaying a target operation object under the condition that the icon positions of at least two target applications are detected to meet preset conditions, wherein the target operation object comprises a first operation object;

the first receiving module is used for receiving a first input of a user to the first operation object;

the first generating module 302 is specifically configured to:

the bill counting apparatus 300 further includes:

the second receiving module is used for receiving a second input of the user to the second operation object;

and the second generation module is used for responding to the second input and generating the classification statistical data of the target bill according to the bill data of the at least two target applications.

Optionally, the second generating module is specifically configured to at least one of:

the bill counting apparatus 300 further includes:

the third receiving module is used for receiving a third input of the user to the third operation object;

and the second display module is used for responding to the third input and displaying a resource transfer interface from the first target application to the second target application.

Optionally, the second display module is specifically configured to:

The bill counting device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The bill counting device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system (Android), an iOS operating system, or other possible operating systems, which is not specifically limited in the embodiments of the present application.

The bill counting device provided in the embodiment of the present application can implement each process implemented by the method embodiments in fig. 1 to fig. 10, and is not described here again to avoid repetition.

Optionally, as shown in fig. 12, an electronic device 600 is further provided in this embodiment of the present application, and includes a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and executable on the processor 601, where the program or the instruction is executed by the processor 601 to implement each process of the above bill counting method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.

Fig. 13 is a schematic hardware structure diagram of an electronic device implementing an embodiment of the present application.

The electronic device 700 includes, but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 7010.

Those skilled in the art will appreciate that the electronic device 700 may further comprise a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 7010 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system. The electronic device structure shown in fig. 13 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.

Wherein the processor 7010 is configured to:

In the embodiment of the application, when a user needs to perform bill counting on a plurality of applications including a payment function, icon positions of the plurality of applications can be set to meet a preset condition, so that the electronic device can acquire bill data of the applications under the condition that the icon positions of the plurality of applications meet the preset condition, and generate a target bill according to the acquired bill data and a preset period. Therefore, the method and the device for billing statistics can simplify the process of billing statistics on the plurality of applications, and enable the user to obtain billing statistical data of the plurality of applications more conveniently.

Optionally, the display unit 706 is configured to:

a user input unit 707 for:

receiving a first input of a user to the first operation object;

processor 7010, further configured to:

a user input unit 707 further for:

receiving a second input of the user to the second operation object;

processor 7010, further configured to:

Optionally, the processor 7010 is further configured to at least one of:

a user input unit 707 further for:

receiving a third input of the third operation object from the user;

a display unit 706, further configured to:

Optionally, the display unit 706 is further configured to:

It should be understood that in the embodiment of the present application, the input unit 704 may include a soft keyboard 7041 and a microphone 7042. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts of a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. Memory 709 may be used to store software programs as well as various data, including but not limited to applications and operating systems. The processor 7010 may integrate an application processor, which handles primarily the operating system, user interfaces, application programs, etc., and a modem processor, which handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 7010.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by the processor, the program or the instruction implements each process of the above bill counting method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above bill counting method embodiment, and can achieve the same technical effect, and for avoiding repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A bill counting method, comprising:

2. The method of claim 1, wherein prior to said generating a target bill, the method further comprises:

receiving a first input of a user to the first operation object;

3. The method of claim 2, wherein the target operands further comprise a second operand;

after the displaying the target operation object, the method further comprises:

receiving a second input of the user to the second operation object;

4. The method according to claim 2, wherein in the case that the icon positions of the first target application and the second target application are detected to meet the preset condition, the target operation objects further comprise a third operation object;

after the displaying the target operation object, the method further comprises:

receiving a third input of the third operation object from the user;

5. The method of claim 4, wherein the displaying a resource transfer interface of the first target application to the second target application in response to the third input comprises:

6. A bill counting apparatus, comprising:

and the first generation module is used for generating a target bill according to the bill data of the at least two target applications and a preset period.

7. The apparatus of claim 6, further comprising:

the first generation module is specifically configured to:

8. The apparatus of claim 7, wherein the target operands further comprise a second operand;

the device further comprises:

9. The device according to claim 7, wherein in the case that it is detected that the icon positions of the first target application and the second target application satisfy the preset condition, the target operation objects further comprise a third operation object;

the device further comprises:

10. The apparatus of claim 9, wherein the second display module is specifically configured to: