CN105868973B - Event resource processing method and device - Google Patents

Event resource processing method and device Download PDF

Info

Publication number
CN105868973B
CN105868973B CN201610235722.4A CN201610235722A CN105868973B CN 105868973 B CN105868973 B CN 105868973B CN 201610235722 A CN201610235722 A CN 201610235722A CN 105868973 B CN105868973 B CN 105868973B
Authority
CN
China
Prior art keywords
event
account
resource
target
resources
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610235722.4A
Other languages
Chinese (zh)
Other versions
CN105868973A (en
Inventor
张建
吴建国
阳恩忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201610235722.4A priority Critical patent/CN105868973B/en
Publication of CN105868973A publication Critical patent/CN105868973A/en
Application granted granted Critical
Publication of CN105868973B publication Critical patent/CN105868973B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108Remote banking, e.g. home banking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405Establishing or using transaction specific rules
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/06Asset management; Financial planning or analysis

Abstract

The invention discloses a method and a device for processing event resources. Wherein, the method comprises the following steps: acquiring the residual event resources corresponding to the first account; detecting a first instruction, wherein the first instruction is used for instructing to transfer a first event resource from the first account to a second account, and the second account and the first account are accounts on a first event platform; and transferring the first event resource in the remaining event resources to the second account according to the first instruction, wherein the second account is set to be not allowed to be transferred until the event resource corresponding to the second account meets a target condition. The invention solves the technical problem that the transfer of the event resources in the account cannot be controlled.

Description

Event resource processing method and device
Technical Field
The invention relates to the field of data processing, in particular to a method and a device for processing event resources.
Background
In the prior art, when an event platform processes event resources, the event resources may be saved in an account of the event platform at any time or transferred from the account. Due to the convenience of the instant saving and instant transferring, under the condition that the event resources are expected to be saved in the account for a long time, the event resources expected to be saved in the account for a long time are difficult to be guaranteed. For example, when storing funds, even if a user expects a storage term or amount, since the existing storage platform can access the funds at any time, the storage term or amount cannot be guaranteed to meet the expectation, that is, the transfer of event resources in the account cannot be controlled.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a method and a device for processing event resources, which at least solve the technical problem that the transfer of the event resources in an account cannot be controlled.
According to an aspect of the embodiments of the present invention, there is provided a method for processing event resources, including: acquiring the residual event resources corresponding to the first account; detecting a first instruction, wherein the first instruction is used for instructing to transfer a first event resource from the first account to a second account, and the second account and the first account are accounts on a first event platform; and transferring the first event resource in the remaining event resources to the second account according to the first instruction, wherein the second account is set to be not allowed to be transferred until the event resource corresponding to the second account meets a target condition.
According to another aspect of the embodiments of the present invention, there is also provided an event resource processing apparatus, including: the first acquisition unit is used for acquiring the residual event resources corresponding to the first account; a detecting unit, configured to detect a first instruction, where the first instruction is used to instruct to transfer a first event resource from the first account to a second account, where the second account and the first account are accounts on a first event platform; a transferring unit, configured to transfer the first event resource in the remaining event resources to the second account according to the first instruction, where the second account is set to be not allowed to be transferred until the event resource corresponding to the second account meets a target condition.
In the embodiment of the invention, because the event resource corresponding to the first account is not allowed to be transferred before the target condition is met, the event resource in the second account can be saved in the first account after being transferred to the first account, thereby solving the technical problem that the transfer of the event resource in the account cannot be controlled because the existing account can be saved and transferred at any time and achieving the technical effect of controlling the transfer of the event resource in the account.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of a hardware system according to an embodiment of the invention;
FIG. 2 is a flow diagram of a method of processing event resources according to an embodiment of the invention;
FIG. 3 is an interaction diagram of a method of processing event resources according to an embodiment of the invention;
FIG. 4 is a block diagram of an account on a first event platform according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an event resource processing apparatus according to an embodiment of the present invention;
fig. 6 is an architecture diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
In accordance with an embodiment of the present invention, there is provided an embodiment of a method that may be performed by an embodiment of the apparatus of the present application, it being noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
Alternatively, in this embodiment, the event resource processing method may be applied to a hardware environment formed by the terminal 102 and the server 104 shown in fig. 1. As shown in fig. 1, a terminal 102 is connected to a server 104 via a network including, but not limited to: the terminal 102 may be a mobile phone terminal, or may also be a PC terminal, a notebook terminal, or a tablet terminal.
The main operating principles of the hardware environment system shown in fig. 1 are: the user sets the target condition of the second account through the terminal 102, the terminal 102 sends the target condition to the server 104, and the server 104 stores the target condition. The terminal 102 detects the first instruction, and after detecting the first instruction, the terminal 102 requests the server 104 to transfer the first event resource in the remaining event resources corresponding to the first account to the second account. And the server 104 responds to the request of the terminal 102 and transfers the first event resource in the remaining event resources corresponding to the first account to the second account. After completing the transfer of the first event resource, the server 104 sends the transfer result to the terminal 102. And displaying the remaining event resources corresponding to the first account and the first event resources corresponding to the second account in the terminal 102.
Fig. 2 is a flowchart of a processing method of an event resource according to an embodiment of the present invention, and the following describes in detail the processing method of an event resource provided in the embodiment of the present invention with reference to fig. 2, as shown in fig. 2, the processing method of an event resource mainly includes the following steps:
step S202, obtaining the remaining event resources corresponding to the first account.
Step S204, a first instruction is detected, where the first instruction is used to instruct to transfer the first event resource from the first account to the second account, and the second account and the first account are accounts on the first event platform.
Step S206, transferring the first event resource in the remaining event resources to the second account according to the first instruction, wherein the second account is set to be not allowed to be transferred until the event resource corresponding to the second account meets the target condition.
The remaining event resources are the event resources indicated by the first account, and the remaining event resources may be stored on the server. The first account may record identifications, which may indicate the number and type of remaining event resources, etc. Similarly, the event resource corresponding to the second account may also be stored in the server, the second account may also record an identifier, and the identifier in the second account may also indicate the number and type of the first event resource.
The first account and the second account are accounts on the same event platform, and can be used as two sub-accounts under the same target account or two related accounts not under the same account, preferably two sub-accounts under the same account. The first event platform may be a platform provided by an application installed on the terminal.
And under the condition that the first account and the second account are two sub-accounts under the same account, the first account stores the residual event resources, the second account can store the first event resources transferred from the first account, and the residual event resources and the events corresponding to the first account are used as the total event resources of the same account to which the first account and the second account belong. The target condition may be time or amount of the event resource corresponding to the second account, and before the event resource corresponding to the second account meets the target condition, the event resource can only be transferred into the second account, but the event resource is not allowed to be transferred out of the second account.
The first event resource indicated by the first instruction may be a part of or all of the remaining event resources, and the event resource corresponding to the second account may satisfy the target condition according to the first event resource transferred by the first instruction, or the first event resource may be transferred from the first account to the second account multiple times so that the event resource corresponding to the second account satisfies the target condition. It should be noted that the above step S202 may be executed before the step S204, or executed after the step S204.
In this embodiment, because the event resource corresponding to the first account is not allowed to be transferred until the target condition is met, the event resource in the second account can be stored in the first account after being transferred to the first account, which solves the technical problem that the transfer of the event resource in the account cannot be controlled because the existing account can be stored and transferred at any time, and achieves the technical effect of controlling the transfer of the event resource in the account.
For example, the financing platform has a target account, and the target account includes two sub-accounts, which are a first account and a second account. The remaining event resource corresponding to the first account may be fund a stored in the first account, the first event resource may be fund b, and the amount of fund b is less than or equal to the amount of fund a. The first instruction may be an instruction sent by a user or an instruction automatically generated by the terminal, and funds b in the first account are transferred to the second account according to the first instruction. Since the second account number is set to: before the target condition is met, the fund corresponding to the second account is not allowed to be transferred, so that the fund can be ensured to be stored in the second account, and the stored fund is not transferred, thereby solving the technical problem that the transfer of event resources in the account cannot be controlled in the prior art.
The control of the transfer of the event resource can be initiated by the user actively or executed on the first event platform according to a predetermined period, so that the flexibility of transferring the event resource is increased, specifically as follows:
optionally, when the first instruction is generated by the terminal, the first account may be controlled to transfer the first event resource to the second account according to a predetermined cycle, so that the second account can satisfy the target condition, and detecting the first instruction includes: judging whether the event resources corresponding to the second account meet the target conditions or not; and when the event resource corresponding to the second account does not meet the target condition, generating a first instruction, wherein the first instruction is used for indicating to transfer the first event resource to the second account according to a preset period.
It should be noted that, before transferring the first event resource to the second account according to the preset period, it may also be determined whether the event resource corresponding to the second account already satisfies the target condition, and when the event resource corresponding to the second account does not yet satisfy the target condition, the first event resource may be transferred to the second account; or transferring the first event resource to the second account when the event resource corresponding to the second account meets the target condition.
For example, a second account in the financing platform needs to hold 5 ten thousand dollars (target condition) as funds for a purchase, and a first account in the financing platform needs to transfer 1000 dollars per month to the second account (first event resource). The first instruction may be an instruction for instructing the first account to transfer 1000 units to the second account every month 15, or an instruction for instructing to transfer 1000 units to the second account, which is generated every month 15.
Optionally, the first instruction is initiated by a user through a terminal where the first event platform is located, and detecting the first instruction includes: the method comprises the steps of detecting touch operation on a terminal screen, and generating a first instruction according to the touch operation. The touch operation includes any one of touch, click, tap, slide, drag, and the like. The first instruction may also be the above-mentioned instruction for instructing to periodically perform the branch action or the periodically generated instruction, and is not described herein again.
Optionally, transferring the first event resource of the remaining event resources to the second account according to the first instruction includes: sending an execution request for requesting to execute a target event to a second event platform in a second account according to a first instruction, wherein event resources required by the execution of the target event are first event resources; after response information sent by the second event platform in response to the execution request is received, executing the target event on the second event platform by using the first event resource in the remaining event resources; the first event resource required for executing the target event is recorded as having been saved in the second account.
When the transfer is executed, the first event resource may be simply stored in the second account from the first account, or the target event may be executed by using the event resource in the first account, and the first event resource required for executing the target event may be used as the event resource of the second account. An execution request for executing the target event is issued on the first event platform, and the target event is executed on the second event platform. The target event is executed using the first event resource in the first account, and the first event resource required to execute the target event is used as the event resource in the second account.
Optionally, after recording the first event resource required for executing the target event in the second account, the method further includes: acquiring a second event resource obtained by executing the target event, wherein the second event resource is an event resource except the first event resource in the event resources obtained by executing the target event; the first event resource is saved in the second account and the second event resource is saved in the first account.
The execution target event can obtain a first event resource and a second event resource, and the first event resource is already used as an event resource in the second account when the target event is executed, so that the first event resource obtained by executing the target event is not allowed to be transferred and needs to be saved in the second account. And the second event resource belongs to the event resource which is additionally obtained by executing the target event, and therefore, the second event resource is stored in the first account and is used as the event resource of the first account.
Optionally, after executing the target event on the second event platform using the first event resource of the remaining event resources, the method further includes: and updating the residual event resources in the first account into the difference between the residual event resources and the first event resources, and displaying second event resources obtained by executing the target event in the second account.
And updating the event resource in the first account into the difference between the residual event resource and the first event resource when the target event is executed by utilizing the residual event resource in the first account. The second event resource obtained by executing the target event is saved in the first account, and then the second event resource can be displayed in the second account. And if the target event is executed in the first account while the target event is executed in the second account, displaying the event resource obtained by the target event of the first account in the first account, and displaying the event resource obtained by the target event of the second account in the second account.
For example, as shown in FIG. 3, the first event platform is a financing platform and the second event platform is a platform of a fund company. The execution target event is the purchase of fund x, and the fund c required for the purchase of fund x is the first event resource.
In step S1, the user sends a first instruction to the financial platform.
Step S2, after receiving the first instruction, sends a purchase request to the platform of the fund company for requesting to purchase the fund x (i.e. issuing an execution request).
And step S3, the fund company returns the procurement result to the financing platform. Funds x are purchased (subject to the target event) using funds a stored in the first account.
In step S4, the payment service platform deducts the purchase amount from the first account. Namely, the purchased fund x is recorded in the second account, and the fund a spent on purchasing the fund x is deducted from the first account, namely, after the target event is executed, the difference between the fund a and the fund c is updated by the residual event resources in the first account, and the event resources stored in the second account are the fund c.
Step S5, pay callback. Namely, the payment service informs the financing platform of completing the purchase.
In step S6, the fund company confirms that the purchase requisition is completed.
In step S7, an affirmative acquisition result is returned.
And step S8, accumulating the purchase amount in the second account. That is, the event resource held in the second account exists in the form of fund, and the profit (second event resource) obtained by purchasing the fund x is displayed in the second account.
In step S9, the amount of funds purchased in the second account is not allowed to be transferred.
In some cases, the platform for deducting funds may be a platform with the financial platform, for example, a bank platform may complete both deduction and purchase of funds.
Optionally, after sending the execution request requesting execution of the target event to the second event platform and before receiving the response information, the method further includes: under the condition that the second event platform does not allow the target event to be executed, sending a reservation request to the second event platform, wherein the reservation request is used for requesting the reservation of the target event to be executed; the first event resource required for executing the target event in the first account is set not to be allowed to be transferred. When the target event is executed in the second account, if the second event platform does not allow the target event to be executed, the target event can be reserved to be executed, and when the second event platform allows the target event to be executed, the target event is executed. When the execution target event is reserved, although the execution target event is not completed, the event resource for executing the target event is already frozen and is not allowed to be transferred.
For example, the fulfillment targeting event is the purchase of fund x, which is reserved if the fund x has been sold out. The first event resources required to purchase fund x are frozen, i.e., not allowed to be transferred, at the time of the reservation purchase of fund x.
Optionally, the target conditions include a preset time and a preset number, and after the first event resource in the remaining event resources is transferred to the second account according to the first instruction, the method further includes: judging whether the event resources corresponding to the second account meet the preset time or the preset quantity; and if the event resources corresponding to the second account meet the preset time and/or the preset quantity, executing the preset event by using the event resources corresponding to the second account, wherein the event resources in the second account are allowed to be transferred.
And when the second account meets the preset time or the preset number, or meets the preset time and the preset number simultaneously, setting the event resources in the second account to be allowed to be transferred. The event resource in the second account may be used to continue executing the target event, or to execute other events. The second account satisfying the preset time may be that the time for which the event resource in the second account is set to be not allowed to be transferred satisfies the preset time, and the second account satisfying the preset number may be that the number of the event resource in the second account satisfies the preset number.
After the second account meets the target condition, the second account may continue to execute the target event before receiving the instruction of the user, or stop executing the target event when the execution cycle of the target event itself has ended before receiving the instruction of the user. The second account can continue to execute the target event or other events according to preset conditions, or only be saved in the second account and be in a state of being allowed to be transferred. The steps are executed on the physical property, and the continuous income of the second account can be ensured.
It should be noted that a target account on the first event platform may have a plurality of such first accounts, and each first account may have different target conditions.
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 2
In this embodiment, the first event platform is taken as an example for explanation. As shown in fig. 4, the user a registers a target account on the financial platform, where the target account includes a first account, a second account, a third account, and a fourth account. The first account is used for storing the residual event resources, the second account is used for storing fund d for purchasing cars, the third account is used for storing fund m for purchasing rooms, and the fourth account is used for storing fund n for traveling. The funds in the second and third accounts are also set to not be allowed to be transferred. That is, a user's target account may include multiple accounts for holding funds for different purposes, and the funds in these accounts are not allowed to be transferred until the target conditions are met. The funds in the second account may be maintained in the second account in the form of a purchase fund, such that the funds maintained in the second account may receive revenue.
User a creates a financial plan (i.e., a first account or a plan account between a first account and a target account) with the financial platform, enters a plan name and purpose, which may include, but is not limited to, an amount of money, a plan deadline, and an action after the plan terminates (the funds in the account are allowed to be transferred) (e.g., take another high-yield product).
The second event platform is a fund platform, the target event is a fund, and the execution target event is a purchase fund. The first instruction instructs a transfer of funds b into the second account number each month. The target condition is that the event resource corresponding to the second account is fund d. The second account is an account planned to purchase the vehicle, namely the fund d corresponding to the second account is used for purchasing the vehicle.
The first account has fund a, fund b required for purchasing fund is deducted from the first account after the first instruction is received and the fund b is recorded in the second account. After the revenue is obtained after the fund is purchased, the obtained revenue is displayed in the second account. The principal fund b for the purchase of funds is held in the second account and is not permitted to be transferred, while the income earned is held in the first account and is in a state permitted to be transferred.
When the fund b is transferred into the second account for 11 times, and the fund corresponding to the second account is already equal to the fund d, the fund can not be transferred into the second account any more. At this time, the fund d corresponding to the second account is in a state of being allowed to be transferred. The fund d may continue to purchase the current fund or other fund, or be transferred to another account, depending on the planned post-expiration activity for A as previously set.
When the fund b is transferred to the second account, the same or different fund can be purchased each time, the event resource can be transferred by purchasing stocks, bonds and the like, and even the fund b is directly saved in the second account, which is not limited in detail here.
Because the second account is set to not allow the transfer of the event resource therein, the control of the second account can be realized, the technical problem that the transfer of the event resource in the account cannot be controlled in the prior art is solved, and the technical effect of controlling the transfer of the event resource in the account is achieved. And the event resource which is not allowed to be transferred can be allowed to generate revenue continuously.
Example 3
In this embodiment, the first event platform is taken as an example of a game platform. The second event platform is a virtual currency value-adding platform, and the first account and the second account are two sub-accounts of the same target account. The execution target event is to increment the virtual currency. The first instruction instructs transfer of the virtual currency h into the second account every month. The target condition is that the event resource corresponding to the second account is the virtual currency f. The second account is an account for planning to purchase the game equipment, namely, the virtual currency f corresponding to the second account is used for purchasing the game equipment.
The first account has virtual currency g, after receiving the first instruction, the virtual currency is added with value in the second account, the virtual currency h required by the virtual currency is deducted from the first account, and the virtual currency h is recorded in the second account. And after the virtual currency is added to obtain the income, displaying the obtained income in the second account. The principal virtual money h for adding value to the virtual money is held in the second account and is not allowed to be transferred, and the obtained profit is held in the first account and is allowed to be transferred.
When the number of times of transferring the virtual currency h to the second account reaches 11 times, and the virtual currency corresponding to the second account is already equal to the virtual currency f, the virtual currency can not be transferred to the second account any more. At this time, the virtual currency f corresponding to the second account is in a state of being allowed to be transferred. The virtual currency f may continue to be incremented in other ways or be transferred to other accounts.
When the virtual currency h is transferred to the second account, the value of the virtual currency h can be added in the same or different manner each time, and even the virtual currency h is directly stored in the second account, which is not limited herein.
Because the second account is set to not allow the transfer of the event resource therein, the control of the second account can be realized, the technical problem that the transfer of the event resource in the account cannot be controlled in the prior art is solved, and the technical effect of controlling the transfer of the event resource in the account is achieved. And the event resource which is not allowed to be transferred can be allowed to generate revenue continuously.
It should be noted that, this embodiment mainly illustrates that the event resource in the first account can be transferred to the second account, and since the event resource in the second account is not allowed to be transferred, it can be ensured that the event resource corresponds to the second account. The event resource may be transferred by executing the target event or directly transferring, which is not limited herein.
Example 4
In this embodiment, a first event platform is taken as an example of a software testing platform. The first account and the second account are two sub-accounts of the same target account. The first instruction instructs to transfer the data segment to be tested to the second account periodically or quantitatively, and the software program test is carried out in the second account. In order to ensure the security of the second account and avoid moving the data segments to be tested corresponding to the second account in the testing process, all the data segments to be tested stored in the second account are not allowed to be transferred before all the data segments to be tested which need to be transferred into the second account for testing are completed, so that the security of the program to be tested which is tested in the second account is improved.
Specifically, the first account includes to-be-tested software composed of 3 to-be-tested data fragments, the 3 to-be-tested data fragments are connected in sequence, and the 3 to-be-tested data fragments are to-be-tested data fragment 1, to-be-tested data fragment 2 and to-be-tested data fragment 3 respectively. The application needs to be tested under the second account. When testing the application program, the data segments to be tested are required to be tested one by one, and when testing one data segment to be tested, the last data segment to be tested is required to be relied on, so that the last data segment to be tested is not allowed to be transferred from the second account before the 3 data segments to be tested are tested.
When the data segment to be tested 1 is transferred to the second account, the data segment to be tested 2 and the data segment to be tested 3 are stored in the first account, and the data segment to be tested 1 is tested in the second account. In the testing process, the data segment 1 to be tested is not allowed to be transferred, and the testing progress of the data segment 1 to be tested can be displayed in the second account. The first instruction can indicate that the data segment to be tested 2 is transferred to the second account for testing after the data segment to be tested 1 is tested, and the data segment to be tested in the second account is not allowed to be transferred before the 3 data segments to be tested are tested, so that the safety of the data segment to be tested in the second account is guaranteed.
Example 5
According to an embodiment of the present invention, there is also provided an event resource processing apparatus for implementing the event resource processing method, where the event resource processing apparatus is mainly used to execute the event resource processing method provided in the foregoing description of the embodiment of the present invention, and the event resource processing apparatus provided in the embodiment of the present invention is specifically described as follows:
fig. 5 is a schematic diagram of an event resource processing apparatus according to an embodiment of the present invention, and as shown in fig. 5, the event resource processing apparatus mainly includes: a first acquisition unit 10, a detection unit 30 and a transfer unit 50.
The first obtaining unit 10 is configured to obtain the remaining event resources corresponding to the first account.
The detecting unit 30 is configured to detect a first instruction, where the first instruction is used to instruct to transfer a first event resource from a first account to a second account, and the second account and the first account are accounts on a first event platform.
The transferring unit 50 is configured to transfer a first event resource of the remaining event resources to a second account according to the first instruction, where the second account is set to be set such that the event resource corresponding to the second account is not allowed to be transferred until a target condition is met.
The first account and the second account are accounts on the same event platform, and can be used as two sub-accounts under the same target account or two related accounts not under the same account, preferably two sub-accounts under the same account. The first event platform may be a platform provided by an application installed on the terminal.
And under the condition that the first account and the second account are two sub-accounts under the same account, the first account stores the residual event resources, the second account can store the first event resources transferred from the first account, and the residual event resources and the events corresponding to the first account are used as the total event resources of the same account to which the first account and the second account belong. The target condition may be time or amount of the event resource corresponding to the second account, and before the event resource corresponding to the second account meets the target condition, the event resource can only be transferred into the second account, but the event resource is not allowed to be transferred out of the second account.
The first event resource indicated by the first instruction may be a part of or all of the remaining event resources, and the event resource corresponding to the second account may satisfy the target condition according to the first event resource transferred by the first instruction, or the first event resource may be transferred from the first account to the second account multiple times so that the event resource corresponding to the second account satisfies the target condition.
In this embodiment, because the event resource corresponding to the first account is not allowed to be transferred until the target condition is met, the event resource in the second account can be stored in the first account after being transferred to the first account, which solves the technical problem that the transfer of the event resource in the account cannot be controlled because the existing account can be stored and transferred at any time, and achieves the technical effect of controlling the transfer of the event resource in the account.
For example, the financing platform has a target account, and the target account includes two sub-accounts, which are a first account and a second account. The remaining event resource corresponding to the first account may be fund a stored in the first account, the first event resource may be fund b, and the amount of fund b is less than or equal to the amount of fund a. The first instruction may be an instruction sent by a user or an instruction automatically generated by the terminal, and funds b in the first account are transferred to the second account according to the first instruction. Since the second account number is set to: before the target condition is met, the fund corresponding to the second account is not allowed to be transferred, so that the fund can be ensured to be stored in the second account, and the stored fund is not transferred, thereby solving the technical problem that the transfer of event resources in the account cannot be controlled in the prior art.
The control of the transfer of the event resource can be initiated by the user actively or executed on the first event platform according to a predetermined period, so that the flexibility of transferring the event resource is increased, specifically as follows:
optionally, when the first instruction is generated by the terminal, the first account may be controlled to transfer the first event resource to the second account according to a predetermined cycle, so that the second account can satisfy the target condition, that is, the detecting unit includes: the judging module is used for judging whether the event resources corresponding to the second account meet the target conditions or not; and the generating module is used for generating a first instruction when the event resource corresponding to the second account is judged not to meet the target condition, wherein the first instruction is used for indicating that the first event resource is transferred to the second account according to a preset period.
It should be noted that, before transferring the first event resource to the second account according to the preset period, it may also be determined whether the event resource corresponding to the second account already satisfies the target condition, and when the event resource corresponding to the second account does not yet satisfy the target condition, the first event resource may be transferred to the second account; or transferring the first event resource to the second account when the event resource corresponding to the second account meets the target condition.
For example, a second account in the financing platform needs to hold 5 ten thousand dollars (target condition) as funds for a purchase, and a first account in the financing platform needs to transfer 1000 dollars per month to the second account (first event resource). The first instruction may be an instruction for instructing the first account to transfer 1000 units to the second account every month 15, or an instruction for instructing to transfer 1000 units to the second account, which is generated every month 15.
Optionally, the first instruction is initiated by a user through a terminal where the first event platform is located, that is, the detecting unit includes: the detection module is used for detecting touch operation on a terminal screen and generating a first instruction according to the touch operation. The touch operation includes any one of touch, click, tap, slide, drag, and the like. The first instruction may also be the above-mentioned instruction for instructing to periodically perform the branch action or the periodically generated instruction, and is not described herein again.
Optionally, the transfer unit comprises: a first sending module, configured to send, in a second account, an execution request for requesting execution of a target event to a second event platform according to a first instruction, where an event resource required for executing the target event is a first event resource; the execution module is used for executing the target event on the second event platform by utilizing the first event resource in the remaining event resources after receiving the response information sent by the second event platform in response to the execution request; and the recording module is used for recording the first event resource required by executing the target event as being stored in the second account.
When the transfer is executed, the first event resource may be simply stored in the second account from the first account, or the target event may be executed by using the event resource in the first account, and the first event resource required for executing the target event may be used as the event resource of the second account. An execution request for executing the target event is issued on the first event platform, and the target event is executed on the second event platform. The target event is executed using the first event resource in the first account, and the first event resource required to execute the target event is used as the event resource in the second account.
Optionally, the apparatus further comprises: the acquisition module is used for acquiring a second event resource obtained by executing the target event after recording a first event resource required by executing the target event in a second account, wherein the second event resource is an event resource except the first event resource in the event resource obtained by executing the target event; and the storage module is used for storing the first event resource in the second account and storing the second event resource in the first account.
The execution target event can obtain a first event resource and a second event resource, and the first event resource is already used as an event resource in the second account when the target event is executed, so that the first event resource obtained by executing the target event is not allowed to be transferred and needs to be saved in the second account. And the second event resource belongs to the event resource which is additionally obtained by executing the target event, and therefore, the second event resource is stored in the first account and is used as the event resource of the first account.
Optionally, the apparatus further comprises: and the updating module is used for updating the residual event resources of the first account into the difference between the residual event resources and the first event resources after the target event is executed on the second event platform by utilizing the first event resources in the residual event resources, and displaying the second event resources obtained by executing the target event in the second account.
And updating the event resource in the first account into the difference between the residual event resource and the first event resource when the target event is executed by utilizing the residual event resource in the first account. The second event resource obtained by executing the target event is saved in the first account, and then the second event resource can be displayed in the second account. And if the target event is executed in the first account while the target event is executed in the second account, displaying the event resource obtained by the target event of the first account in the first account, and displaying the event resource obtained by the target event of the second account in the second account.
Optionally, the apparatus further comprises: the second sending module is used for sending a reservation request to the second event platform after sending an execution request requesting execution of the target event to the second event platform and before receiving response information, and under the condition that the second event platform does not allow execution of the target event, after sending the execution request requesting execution of the target event to the second event platform and before receiving the response information, wherein the reservation request is used for requesting reservation of execution of the target event; and the setting module is used for setting the first event resource required by executing the target event in the first account as not allowed to be transferred.
When the target event is executed in the second account, if the second event platform does not allow the target event to be executed, the target event can be reserved to be executed, and when the second event platform allows the target event to be executed, the target event is executed. When the execution target event is reserved, although the execution target event is not completed, the event resource for executing the target event is already frozen and is not allowed to be transferred.
For example, the fulfillment targeting event is the purchase of fund x, which is reserved if the fund x has been sold out. The first event resources required to purchase fund x are frozen, i.e., not allowed to be transferred, at the time of the reservation purchase of fund x.
Optionally, the target condition includes a preset time and a preset number, and the apparatus further includes: the judging unit is used for judging whether the event resources corresponding to the second account meet the preset time or the preset quantity after the first event resources in the remaining event resources are transferred to the second account according to the first instruction; and the execution unit is used for executing the preset event by utilizing the event resource corresponding to the second account when the event resource corresponding to the second account is judged to meet the preset time and/or the preset quantity, wherein the event resource in the second account is allowed to be transferred.
And when the second account meets the preset time or the preset number, or meets the preset time and the preset number simultaneously, setting the event resources in the second account to be allowed to be transferred. The event resource in the second account may be used to continue executing the target event, or to execute other events. The second account satisfying the preset time may be that the time for which the event resource in the second account is set to be not allowed to be transferred satisfies the preset time, and the second account satisfying the preset number may be that the number of the event resource in the second account satisfies the preset number.
After the second account meets the target condition, the second account may continue to execute the target event before receiving the instruction of the user, or stop executing the target event when the execution cycle of the target event itself has ended before receiving the instruction of the user. The second account can continue to execute the target event or other events according to preset conditions, or only be saved in the second account and be in a state of being allowed to be transferred. The steps are executed on the physical property, and the continuous income of the second account can be ensured.
According to an embodiment of the present invention, there is also provided a mobile terminal for implementing the above event resource processing method, as shown in fig. 6, the mobile terminal mainly includes a processor 501, a camera 502, a display 503, a data interface 504, a memory 505, and a network interface 506, where:
the camera 502 is mainly used for authenticating a user who logs in the first event platform.
The data interface 504 authenticates the user logged on the first event platform mainly by means of data transmission.
The memory 505 is mainly used for storing the identity information and account information of the user logging in the first event platform.
The network interface 506 is mainly used for network communication with the server, sending account information to the server for saving, and enabling the first event platform to communicate with other platforms.
The display 503 is mainly used for displaying the first account, the second account, the first event resource and the remaining event resource, detecting the first instruction, and the like.
The processor 501 is mainly configured to perform the following operations:
and acquiring the residual event resources corresponding to the first account. And detecting a first instruction, wherein the first instruction is used for indicating that the first event resource is transferred from the first account to the second account, and the second account and the first account are accounts on the first event platform. And transferring the first event resource in the remaining event resources to a second account according to the first instruction, wherein the second account is set to be not allowed to be transferred until the event resource corresponding to the second account meets the target condition.
The processor 501 is further configured to determine whether an event resource corresponding to the second account meets a target condition; and when the event resource corresponding to the second account does not meet the target condition, generating a first instruction, wherein the first instruction is used for indicating to transfer the first event resource to the second account according to a preset period.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiments 1 to 4 above, 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 configured to store program codes of the event resource processing method according to the embodiment of the present invention.
Optionally, in this embodiment, the storage medium may be located in at least one of a plurality of network devices in a network of a mobile communication network, a wide area network, a metropolitan area network, or a local area network.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
S1,obtaining the residual event resource corresponding to the first account
S2,Detecting a first instruction, wherein the first instruction is used for instructing to transfer a first event resource from a first account to a second account, and the second account and the first account are accounts on a first event platform
S3,Transferring a first event resource of the remaining event resources to a second event resource according to a first instructionTwo account numbers
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.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiments 1 to 4 above, and this embodiment is not described herein again.
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 (12)

1. A method for processing event resources is characterized by comprising the following steps:
acquiring the residual event resources corresponding to the first account;
detecting a first instruction, wherein the first instruction is used for instructing to transfer a first event resource from the first account to a second account, and the second account and the first account are sub-accounts of a target account on a first event platform;
transferring the first event resource in the remaining event resources to the second account according to the first instruction, wherein the second account is set to only transfer event resources to the second account and not transfer event resources from the second account before a target condition is met;
wherein transferring the first event resource of the remaining event resources to the second account according to the first instruction comprises:
sending an execution request for requesting to execute a target event to a second event platform in the second account according to the first instruction, wherein event resources required by executing the target event are the first event resources;
executing the target event on the second event platform by using the first event resource in the remaining event resources after receiving response information sent by the second event platform in response to the execution request;
recording the first event resource required for executing the target event as an event resource of the second account;
after recording the first event resource required for executing the target event in the second account, the method further includes:
acquiring a second event resource obtained by executing the target event, wherein the second event resource is an event resource except the first event resource in the event resources obtained by executing the target event;
and corresponding the first event resource to the second account, and corresponding the second event resource to the first account, wherein the second event resource is set to be in a state of being allowed to be transferred.
2. The method of claim 1, wherein after executing the target event on the second event platform using the first one of the remaining event resources, the method further comprises:
and updating the residual event resources of the first account to be the difference between the residual event resources and the first event resources, and displaying second event resources obtained by executing the target event in the second account.
3. The method of claim 1, wherein after sending an execution request to the second event platform requesting execution of the target event and before receiving the response information, the method further comprises:
under the condition that the second event platform does not allow the target event to be executed, sending a reservation request to the second event platform, wherein the reservation request is used for requesting to reserve the target event to be executed;
setting the first event resource required for executing the target event in the second account as not allowed to be transferred.
4. The method according to claim 1, wherein the target conditions comprise a preset time and a preset number, and after transferring the first event resource of the remaining event resources to the second account according to the first instruction, the method further comprises:
judging whether the event resources corresponding to the second account meet the preset time or the preset quantity;
and if the event resource corresponding to the second account meets the preset time and/or the preset quantity, executing a preset event by using the event resource corresponding to the second account, wherein the event resource in the second account is allowed to be transferred.
5. The method of claim 1, wherein detecting the first instruction comprises:
judging whether the event resource corresponding to the second account meets the target condition;
and generating the first instruction when the event resource corresponding to the second account is judged not to meet the target condition, wherein the first instruction is used for indicating that the first event resource is transferred to the second account according to a preset period.
6. An apparatus for processing event resources, comprising:
the first acquisition unit is used for acquiring the residual event resources corresponding to the first account;
a detecting unit, configured to detect a first instruction, where the first instruction is used to instruct to transfer a first event resource from the first account to a second account, where the second account and the first account are sub-accounts of a target account on a first event platform;
a transferring unit, configured to transfer the first event resource in the remaining event resources to the second account according to the first instruction, where the second account is set to only transfer an event resource to the second account and not transfer an event resource from the second account until a target condition is met;
the transfer unit includes:
a first sending module, configured to send, in the second account, an execution request for requesting execution of a target event to a second event platform according to the first instruction, where an event resource required for executing the target event is the first event resource;
an execution module, configured to execute the target event on the second event platform by using the first event resource in the remaining event resources after receiving response information sent by the second event platform in response to the execution request;
a recording module, configured to record the first event resource required for executing the target event as being stored in the second account;
the device further comprises:
an obtaining module, configured to obtain a second event resource obtained by executing the target event after recording the first event resource required for executing the target event in the second account, where the second event resource is an event resource other than the first event resource in the event resources obtained by executing the target event;
and the saving module is used for saving the first event resource in the second account and saving the second event resource in the first account, wherein the second event resource is set to be in a state of allowing to be transferred.
7. The apparatus of claim 6, further comprising:
an updating module, configured to update the remaining event resources of the first account to a difference between the remaining event resources and the first event resources after the target event is executed on the second event platform by using the first event resource in the remaining event resources, and display a second event resource obtained by executing the target event in the second account.
8. The apparatus of claim 6, further comprising:
a second sending module, configured to, after sending an execution request requesting execution of a target event to a second event platform and before receiving the response information, send a reservation request to the second event platform after sending the execution request requesting execution of the target event to the second event platform and before receiving the response information, where the reservation request is used to request reservation for execution of the target event, and in a case where the second event platform does not allow execution of the target event;
a setting module, configured to set the first event resource required by the second account to execute the target event as disallowed to be transferred.
9. The apparatus of claim 6, wherein the target condition comprises a preset time and a preset number, the apparatus further comprising:
a determining unit, configured to determine whether the event resource corresponding to the second account satisfies the preset time or the preset number after the first event resource in the remaining event resources is transferred to the second account according to the first instruction;
and the execution unit is used for executing a preset event by using the event resource corresponding to the second account when the event resource corresponding to the second account is judged to meet the preset time and/or the preset quantity, wherein the event resource in the second account is allowed to be transferred.
10. The apparatus of claim 6, wherein the detection unit comprises:
the judging module is used for judging whether the event resources corresponding to the second account meet the target conditions or not;
and a generating module, configured to generate the first instruction when it is determined that the event resource corresponding to the second account does not meet the target condition, where the first instruction is used to instruct to transfer the first event resource to the second account according to a preset period.
11. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to carry out the method of any one of claims 1 to 5 when executed.
12. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 5 by means of the computer program.
CN201610235722.4A 2016-04-15 2016-04-15 Event resource processing method and device Active CN105868973B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610235722.4A CN105868973B (en) 2016-04-15 2016-04-15 Event resource processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610235722.4A CN105868973B (en) 2016-04-15 2016-04-15 Event resource processing method and device

Publications (2)

Publication Number Publication Date
CN105868973A CN105868973A (en) 2016-08-17
CN105868973B true CN105868973B (en) 2020-12-25

Family

ID=56632198

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610235722.4A Active CN105868973B (en) 2016-04-15 2016-04-15 Event resource processing method and device

Country Status (1)

Country Link
CN (1) CN105868973B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114549156A (en) * 2016-08-24 2022-05-27 创新先进技术有限公司 Network resource transfer method, fund transfer method, repayment method and device
CN106657058B (en) * 2016-12-20 2019-12-06 腾讯科技(深圳)有限公司 Event resource allocation method and device
CN106815765B (en) * 2016-12-29 2021-03-30 网易(杭州)网络有限公司 Asset allocation method and equipment
TWI700661B (en) * 2018-01-23 2020-08-01 遠東國際商業銀行股份有限公司 Financial capital transaction method and system
CN110704190A (en) * 2019-09-29 2020-01-17 腾讯科技(深圳)有限公司 Virtual resource processing method, device, equipment and storage medium
CN113313600A (en) * 2020-02-26 2021-08-27 京东数字科技控股股份有限公司 Message processing method, device and system, storage medium and electronic device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103856915A (en) * 2012-12-06 2014-06-11 阿里巴巴集团控股有限公司 Data resource transfer method and device
CN104376491A (en) * 2014-10-29 2015-02-25 中国建设银行股份有限公司 Virtual resource monitoring method, device and system
CN104751266A (en) * 2013-12-31 2015-07-01 腾讯科技(深圳)有限公司 Data processing method, value-added server and system
CN105096195A (en) * 2014-05-08 2015-11-25 陈衡 Account money amount processing method and system based on internet application platform
CN105354745A (en) * 2015-12-03 2016-02-24 腾讯科技(深圳)有限公司 Processing method of data information, data information processing platform and management platform

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103856915A (en) * 2012-12-06 2014-06-11 阿里巴巴集团控股有限公司 Data resource transfer method and device
CN104751266A (en) * 2013-12-31 2015-07-01 腾讯科技(深圳)有限公司 Data processing method, value-added server and system
CN105096195A (en) * 2014-05-08 2015-11-25 陈衡 Account money amount processing method and system based on internet application platform
CN104376491A (en) * 2014-10-29 2015-02-25 中国建设银行股份有限公司 Virtual resource monitoring method, device and system
CN105354745A (en) * 2015-12-03 2016-02-24 腾讯科技(深圳)有限公司 Processing method of data information, data information processing platform and management platform

Also Published As

Publication number Publication date
CN105868973A (en) 2016-08-17

Similar Documents

Publication Publication Date Title
CN105868973B (en) Event resource processing method and device
CN110599323B (en) Resource processing method and processing equipment
US11126996B2 (en) Settlement system, server device, terminal device, method and program
US8676701B2 (en) Credit card usage management system, credit card usage management method, program, and information storage medium
US20130198013A1 (en) Consumer-initiated payment to skip electronic advertisements
CN105939362A (en) User account management method and device
CN110009365B (en) User group detection method, device and equipment for abnormally transferring electronic assets
EP4358000A1 (en) Digital currency-based payment method, platform, terminal, and payment system
CN104283898A (en) Information processing method and device
CN105225111A (en) A kind of method and apparatus of online payment checking
US20180341966A1 (en) System and method for promoting product sales by using distribution of sales profit according to event success
CN111242603A (en) Riding settlement method and device based on block chain
CN110991837A (en) Online taxi appointment transaction data processing method, device and system
KR20240011203A (en) Method and apparatus for providing mutiple subscription service
CN107679839B (en) Data processing method and system
KR101735287B1 (en) The method, server and system for providing application funding service
CN105408925A (en) Extensible interface for synchronous and asynchronous payment
JP5197700B2 (en) Electronic book browsing terminal, electronic book distribution system, electronic book distribution server and method
CN109460981B (en) Message interaction method and device, storage medium and electronic device
CN111427658A (en) Block chain-based user data processing method, device, equipment and storage medium
US20230050176A1 (en) Method of processing a transaction request
CN108985933A (en) A kind of bookkeeping methods and device
CN110163606B (en) Refund method and device based on blockchain and electronic equipment
CN110599146B (en) Data processing method, device, terminal, node equipment and storage medium
CN111415263A (en) Data matching method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant