Wherein, P_ijIndicating that the event resource corresponding to the first event of the second account changes in the ith sub-period of the jth period, C_jIndicating the second account in the j periodThe sum of the original event resource and the added event resource of the number.

For example, the present week profit-loss ratio is calculated. P_ijRepresenting the profit and loss of the second account on the ith day of the week (namely, the event resource change corresponding to the first event), wherein the profit and loss of each day can be represented by the difference between the profit and loss after closing the disk and the profit and loss before opening the disk;

representing the total profit and loss in the week; c_jRepresents the cost of the week (i.e., the sum of the original event resources and the added event resources of the second account number), i.e., the sum of the market value taken prior to the first trading day of the week and the inflow cost of the week. When calculating the present week profit-loss ratio, P_1jFor profit or loss on the first trade day of the week, P_njFor profit or loss of the last trade day of the week, A_jThe profit-loss ratio of the week. When calculating the monthly profit-loss ratio, P_1jFor profit or loss on the first trade day of this month, P_njFor profit or loss of the last trade day of this month, C_jThe cost of this month, i.e. the sum of the market value before the first trade day of this month and the inflow cost of this week, is also expressed accordingly.

Optionally, calculating a first event execution result of the second account executing the first event according to the execution record and the event resource change includes: the first event execution result a is calculated in the following manner_j：

Wherein M is_njRepresents the total event resource, M, of the second account in the last sub-period n of the jth period_1jRepresents the total event resource S of the second account in the 1 st sub-period of the j period before the second account executes the first event_jRepresenting an event resource obtained by the second account executing the first event in the jth cycle, B_jRepresents the event resource consumed by the second account to execute the first event in the jth period, C_jRepresenting the original event resource and the added of the second account in the j periodSum of event resources.

In the example of calculating the win-loss ratio, M_njThe total market value (i.e. total event resources) of the second account number after the last trading day of the week is recorded, M_1jTotal market value of the second account number before opening for the first trading day of the week, S_jThe amount of money to be gained by selling shares in the week for the second account, B_jIndicating the amount spent by the second account to buy stock in this week. C_jIndicating the weekly inflow cost.

According to the change of the query time period carried by the query request, the calculation period can be adjusted, so that a first event execution result corresponding to the query time period carried by the query request is obtained. The adjustment method is the same as the adjustment method of the period, and is not described again.

In the above embodiment, the circulation inflow cost C_jIt can be calculated according to the following rules:

calculating according to the sequence of transaction time, and if the sale transaction is executed, increasing the sale amount of the fund in the fund pool; if a buy transaction is performed and the buy amount is greater than the funds in the fund pool, the weekly inflow cost increases the difference between the buy amount and the fund pool amount; if the purchase amount is less than or equal to the funds in the fund pool, the fund pool amount is subtracted by the purchase amount.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

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

Example 3

According to an embodiment of the present invention, there is also provided an event result display apparatus for implementing the method for displaying an event result according to embodiment 1, where the event result display apparatus is mainly used to execute the method for displaying an event result according to embodiment 1 of the present invention, and the method for displaying an event result according to the embodiment of the present invention is specifically described as follows:

fig. 6 is a schematic diagram of an event result display device according to embodiment 3 of the present invention, and as shown in fig. 6, the event result display device mainly includes: a transmitting unit 50, a receiving unit 52 and a first presentation unit 54.

The sending unit 50 is configured to send, to the server through a client of the first application, a query request for querying a first event execution result of a second account of the first application, where the client logs in by using the first account, the second account has an association relationship with the first account, and a first event execution result of the second account is in a public state, and the public state is used to indicate that the first account is allowed to view the first event execution result obtained by the second account executing the first event in the first event platform.

The client of the first application is a client installed in the terminal 102 and sends a query request to theserver 104. The client logs in by using a first account, the second account is an account which has an association relationship with the first account in the first application, and the second account is displayed in the client which logs in by using the first account and is even a communication application, for example, the second account and the first account are in a friend relationship in the first application, or the second account and the first account participate in a member of a certain activity in the first application together. The public state of the second account refers to a first event execution result obtained by the first account being capable of viewing, at the client of the first application, the first event executed by the second account in the first event platform. That is, the second account authorizes the first account to view the first event execution result at the client of the first application. The first event platform and the client of the first application realize different functions, and the first event platform can be two platforms which are completely independent from the first application, or the first event platform and the first application can be the same platform. When the first application and the first event platform are the same platform, the platform can simultaneously realize the functions of the first application and the functions of the first event platform. The first event platform may also be a function in the first application, e.g. as a functional plug-in to the first application.

The receiving unit 52 is configured to receive a result of the first event execution sent by the server in response to the query request.

The first presenting unit 54 is configured to present the received first event execution result in the client of the first application.

Optionally, the second account includes a plurality of accounts, and the first display unit includes: and the arranging module is used for arranging and displaying each account in the plurality of accounts and the first event execution result corresponding to each account in the client according to the size sequence of the change of the event resource corresponding to the first event indicated by the first event execution result.

In the example that the first application client is a WeChat client and the first event platform is a dealer platform, when the second accounts are multiple accounts and all have a friend relationship with the first account, and the execution result of the first event of each account is in a public state, when the first account requests to view the profit-loss ratio of the friend buying and selling stocks, the profit-loss ratios of the multiple accounts are displayed in the client logged in by using the first account, and are displayed in an arrangement manner according to the profit-loss ratio from large to small or from small to large. The order of the first account selection arrangement display is from large to small or from small to large.

Optionally, the first display unit comprises: and the updating module is used for updating a first event execution result obtained by the second account executing the first event in the first event platform in a first time period when the first event platform allows the second account to execute the first event and/or a second time period with a preset time relationship with the first time period in the client of the first application.

Optionally, the first display unit comprises: the display module is used for displaying a first event execution result and a second event execution result in a client of the first application, wherein the second event execution result is an event execution result obtained by the first account executing a second event on the second event platform, and the first account is set to allow the second account to view the second event execution result obtained by the first account executing the second event on the second event platform.

Optionally, the query request carries a query time period, and the sending unit includes: the sending module is used for sending a query request for querying a first event execution result obtained by executing a first event by a second account of a first application in a query time period to the server through a client of the first application.

Optionally, the apparatus further comprises: the detection unit is used for detecting the click operation of clicking the execution result of the first event after the received execution result of the first event is displayed in the client of the first application; and the second display unit is used for displaying a first event object of a first event executed by the second account on the first event platform in the client after the click operation is detected, wherein the first event execution result receives the click operation under the condition that the second account is set to allow the first account to view the first event object.

Example 4

According to an embodiment of the present invention, there is also provided an event result display apparatus for implementing the method for displaying an event result according toembodiment 2, where the event result display apparatus is mainly used to implement the method for displaying an event result according toembodiment 2 of the present invention, and the method for displaying an event result according to embodiment of the present invention is specifically described as follows:

fig. 7 is a schematic diagram of an event result display device according to embodiment 4 of the present invention, and as shown in fig. 7, the event result display device mainly includes: a request receiving unit 60, a status detecting unit 62 and a result transmitting unit 64.

The request receiving unit 60 is configured to receive a query request sent by a client of a first application, where the query request is used to request to query a first event execution result of a second account in the client of the first application, where the client logs in by using the first account, and the second account has an association relationship with the first account.

The state detection unit 62 is configured to detect whether the second account is in a public state, where the public state is used to indicate that the second account allows the first account to view a first event execution result obtained by the second account executing the first event in the first event platform.

The result sending unit 64 is configured to send the first event execution result to the client if the second account is in the public state, so as to present the first event execution result in the client of the first application.

Optionally, the apparatus further comprises: the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring an execution record of a first event and an event resource change of a second account in a first application client, wherein the second account has an association relation with the first account, and executes the first event on a first event platform; and the calculating unit is used for calculating a first event execution result of the first event executed by the second account according to the execution record and the event resource change.

In particular, the calculation unit is configured to operate in the following mannerCalculating a first event execution result A_j：

Wherein, P_ijIndicating that the event resource corresponding to the first event of the second account changes in the ith sub-period of the jth period, C_jRepresenting the sum of the original event resource and the added event resource of the second account in the j-th period.

Optionally, the calculating unit is configured to calculate the first event execution result a in the following manner_j：

Wherein M is_njRepresents the total event resource, M, of the second account in the last sub-period n of the jth period_1jRepresents the 1 st sub-period of the jth periodSecond Account Prior to execution of the first event, the second Account' S total event resources, S_jRepresenting an event resource obtained by the second account executing the first event in the jth cycle, B_jRepresents the event resource consumed by the second account to execute the first event in the jth period, C_jRepresenting the sum of the original event resource and the added event resource of the second account in the j-th period.

It should be noted that, in this embodiment, the first event execution result is calculated in the domain of the server, and is stored in the cache of the server, and the first event execution result is extracted from the cache and is sent to the client of the first application, so that interaction with the first event platform and the client of the instant messaging is isolated, so as to ensure the information security of the second account acquired in the first event platform.

Example 5

According to an embodiment of the present invention, there is also provided a terminal for implementing the method for displaying event results, as shown in fig. 8, the terminal mainly includes aprocessor 701, acamera 702, adisplay 703, adata interface 704, amemory 705, and anetwork interface 706, where:

thecamera 702 is mainly used for shooting an avatar of the first account.

The data interface 704 transmits data (such as picture data and music data) acquired by the third-party tool to theprocessor 701 mainly by means of data transmission.

Thememory 705 is mainly used for storing files required for running the first application and data saved by the first application.

Thenetwork interface 706 is mainly used for performing network communication with the server to obtain the result of the first event execution.

Thedisplay 703 is mainly used for displaying the result of the execution of the first event.

Theprocessor 701 is mainly configured to perform the following operations: sending a query request for querying a first event execution result of a second account of a first application to a server through a client of the first application, wherein the client logs in by using the first account, the second account has an association relation with the first account, the first event execution result of the second account is in a public state, and the public state is used for indicating that the first account is allowed to view the first event execution result obtained by the second account executing the first event in a first event platform; receiving a first event execution result sent by the server in response to the query request; and displaying the received first event execution result in the client of the first application.

Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 andembodiment 2, and this embodiment is not described herein again.

Example 6

The embodiment of the invention also provides a storage medium. Optionally, in this embodiment, the storage medium may be located in at least one of a plurality of network devices in a network.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:

s1, sending a query request for querying a first event execution result of a second account of a first application to a server through a client of the first application, wherein the client logs in by using the first account, the second account has an association relation with the first account, the first event execution result of the second account is in a public state, and the public state is used for indicating that the first account is allowed to view the first event execution result obtained by the second account executing the first event in a first event platform;

s2, receiving the first event execution result sent by the server in response to the query request;

s3, displaying the received first event execution result in the client of the first application.

Optionally, the storage medium may be further configured to store program code for performing the steps of:

s1, receiving a query request sent by a client of a first application, where the query request is used to request query of a first event execution result of a second account in the client of the first application, where the client logs in by using the first account, and the second account has an association relationship with the first account;

s2, detecting whether the second account is in a public state, wherein the public state is used for indicating that the second account allows the first account to check a first event execution result obtained by the second account executing a first event in a first event platform;

s3, sending the first event execution result to the client when the second account is in the public state, so as to display the first event execution result in the client of the first application.

Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A method for displaying event results is characterized by comprising the following steps:

sending a query request for querying a first event execution result of a second account of a first application to a server by a client of the first application, wherein the client logs in by using the first account, the second account has an association relationship with the first account, the first event execution result of the second account is in a public state, and the public state is used for indicating that the first account is allowed to view the first event execution result obtained by the second account executing a first event in a first event platform;

receiving the first event execution result sent by the server in response to the query request, wherein the first event execution result A is_jExpressed as:

wherein, P_ijIndicating that in the ith sub-period of the jth period, the secondEvent resource change corresponding to the first event of the account, C_jRepresenting the sum of the original event resource and the increased event resource of the second account in the j period; or

The first event execution result A_jExpressed as:

wherein M is_njRepresents the total event resource, M, of the second account in the last sub-period n of the jth period_1jRepresenting the total event resource, S, of the second account before the second account executes the first event in the 1 st sub-period of the jth period_jRepresents an event resource obtained by the second account executing the first event in the j period, B_jRepresents the event resource consumed by the second account to execute the first event in the j period, C_jRepresenting the sum of the original event resource and the increased event resource of the second account in the j period;

arranging and displaying each account in a plurality of accounts and the first event execution result corresponding to each account in the client according to the size sequence of the change of the event resource corresponding to the first event, which is indicated by the first event execution result, wherein the second account comprises the plurality of accounts;

detecting a click operation of clicking the first event execution result on the client; after the click operation is detected, displaying a first event object of the first event executed by the second account on the first event platform in the client, wherein the click operation is accepted as the execution result of the first event under the condition that the second account is set to allow the first account to view the first event object;

the first event platform and the platform where the client of the first application is located are different platforms, and the execution results of the first event displayed by the client of the first application logged in by using the first account and the second account are different.

2. The method of claim 1, wherein presenting the received first event execution result in the client of the first application comprises:

updating, in the client of the first application, the first event execution result obtained by executing the first event in the first event platform by the second account within a first time period in which the first event platform allows the second account to execute the first event, and/or within a second time period having a preset time relationship with the first time period.

3. The method of claim 1, wherein presenting the received first event execution result in the client of the first application comprises:

displaying the first event execution result and a second event execution result in the client of the first application, wherein the second event execution result is an event execution result obtained by the first account executing a second event on a second event platform, and the first account is set to allow the second account to view the second event execution result obtained by the first account executing the second event on the second event platform.

4. The method of claim 1, wherein the query request carries a query time period, and sending, by a client of a first application, a query request for querying an execution result of a first event of a second account of the first application to a server comprises:

sending, by the client of a first application, a query request to the server for querying a result of the first event execution, obtained by executing the first event by the second account of the first application within the query time period.

5. A method for displaying event results is characterized by comprising the following steps:

receiving a query request sent by a client of a first application, wherein the query request is used for requesting to query a first event execution result of a second account in the client of the first application, the client logs in by using the first account, and the second account has an association relation with the first account;

detecting whether the second account is in a public state, wherein the public state is used for indicating that the second account allows the first account to view a first event execution result obtained by the second account executing a first event in a first event platform, and the first event execution result A is obtained_jExpressed as:

wherein, P_ijIndicating that in the ith sub-period of the jth period, the event resource corresponding to the first event of the second account is changed, C_jRepresenting the sum of the original event resource and the increased event resource of the second account in the j period; or

The first event execution result A_jExpressed as:

wherein M is_njRepresents the total event resource, M, of the second account in the last sub-period n of the jth period_1jRepresenting the total event resource, S, of the second account before the second account executes the first event in the 1 st sub-period of the jth period_jRepresents an event resource obtained by the second account executing the first event in the j period, B_jRepresents the event resource consumed by the second account to execute the first event in the j period, C_jIs shown inThe sum of the original event resource and the increased event resource of the second account in the jth period;

sending the first event execution result to the client when the second account is in the public state, so as to arrange and display each account in a plurality of accounts and the first event execution result corresponding to each account in the client of the first application according to the size sequence of the change of the event resource corresponding to the first event, which is indicated by the first event execution result, in the client, wherein the second account comprises the plurality of accounts;

the first event platform and a platform where the client of the first application is located are different platforms, and the execution results of the first event displayed by the client of the first application logged in by using a first account and a second account are different;

the client is used for displaying a first event object of the first event executed by the second account on the first event platform after detecting a click operation of clicking the first event execution result, wherein the first event execution result receives the click operation when the second account is set to allow the first account to view the first event object.

6. The method of claim 5, wherein prior to issuing the first event execution result to the client, the method further comprises:

acquiring an execution record of a first event executed by a second account in the client of the first application, wherein the second account has an association relation with the first account, and the execution record and the event resource change of the second account are acquired on the first event platform;

and calculating the first event execution result of the second account executing the first event according to the execution record and the event resource change.

7. An apparatus for displaying event results, comprising:

a sending unit, configured to send, by a client of a first application, to a server, a query request for querying a first event execution result of a second account of the first application, where the client logs in by using a first account, the second account has an association relationship with the first account, the first event execution result of the second account is in a public state, and the public state is used to indicate that the first account is allowed to view the first event execution result obtained by the second account executing a first event in a first event platform;

a receiving unit, configured to receive the first event execution result sent by the server in response to the query request, where the first event execution result a is_jExpressed as:

The first event execution result A_jExpressed as:

wherein M is_njRepresents the total event resource, M, of the second account in the last sub-period n of the jth period_1jRepresenting the total event resource, S, of the second account before the second account executes the first event in the 1 st sub-period of the jth period_jRepresents an event resource obtained by the second account executing the first event in the j period, B_jRepresents the event resource consumed by the second account to execute the first event in the j period, C_jTo representThe sum of the original event resource and the increased event resource of the second account in the j period;

a first presentation unit, configured to present, in the client of the first application, the received first event execution result;

the detection unit is used for detecting a click operation of clicking the first event execution result after the received first event execution result is displayed in the client of the first application;

a second presentation unit, configured to, after the click operation is detected, present, in the client, a first event object of the first event executed by the second account on the first event platform, where in a case where the second account is set to allow the first account to view the first event object, a result of the execution of the first event accepts the click operation;

the first display unit comprises: and the arranging module is used for arranging and displaying each account in a plurality of accounts and the first event execution result corresponding to each account in the client according to the size sequence of the change of the event resource corresponding to the first event indicated by the first event execution result, wherein the second account comprises the plurality of accounts.

8. The apparatus of claim 7, wherein the first presentation unit comprises:

an updating module, configured to update, in the client of the first application, a first event execution result obtained by executing the first event in the first event platform by the second account in a first time period in which the first event platform allows the second account to execute the first event, and/or in a second time period having a preset time relationship with the first time period.

9. The apparatus of claim 7, wherein the first presentation unit comprises:

a display module, configured to display the first event execution result and a second event execution result in the client of the first application, where the second event execution result is an event execution result obtained by the first account executing a second event on a second event platform, and the first account is set to allow the second account to view the second event execution result obtained by the first account executing the second event on the second event platform.

10. The apparatus of claim 7, wherein the query request carries a query time period, and the sending unit comprises:

a sending module, configured to send, to the server through the client of a first application, a query request for querying a first event execution result obtained by executing the first event by the second account of the first application within the query time period.

11. An apparatus for displaying event results, comprising:

a request receiving unit, configured to receive a query request sent by a client of a first application, where the query request is used to request to query a first event execution result of a second account in the client of the first application, where the client logs in by using the first account, and the second account has an association relationship with the first account;

a state detection unit, configured to detect whether the second account is in a public state, where the public state is used to indicate that the second account allows the first account to view a first event execution result obtained by the second account executing a first event in a first event platform, where the first event execution result a is an event execution result a_jExpressed as:

The first event execution result A_jExpressed as:

a result sending unit, configured to send the first event execution result to the client when the second account is in the public state, so as to arrange and display, in the client of the first application, each account in a plurality of accounts and the first event execution result corresponding to the each account in the client according to a size order of a change in an event resource corresponding to the first event, where the change is indicated by the first event execution result, and the second account includes the plurality of accounts;

12. The apparatus of claim 11, further comprising:

an obtaining unit, configured to obtain, before sending the first event execution result to the client, an execution record of a first event executed by a second account in the client of the first application, where the second account has an association relationship with the first account, on the first event platform, and an event resource change of the second account;

and the calculating unit is used for calculating the first event execution result of the first event executed by the second account according to the execution record and the event resource change.