WO2016173444A1 - 事务处理的记录方法及装置 - Google Patents

事务处理的记录方法及装置 Download PDF

Info

Publication number
WO2016173444A1
WO2016173444A1 PCT/CN2016/079828 CN2016079828W WO2016173444A1 WO 2016173444 A1 WO2016173444 A1 WO 2016173444A1 CN 2016079828 W CN2016079828 W CN 2016079828W WO 2016173444 A1 WO2016173444 A1 WO 2016173444A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
transaction
receipt
agent
service platform
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.)
Ceased
Application number
PCT/CN2016/079828
Other languages
English (en)
French (fr)
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.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Publication of WO2016173444A1 publication Critical patent/WO2016173444A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION 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/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, 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/407—Cancellation of a transaction

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to a recording method and apparatus for transaction processing.
  • the services that occur in the e-commerce platform generally introduce a third-party platform, and the third-party platform acts as a security supervisor for transaction processing in the business to ensure the security of transaction processing in the service platform.
  • the service platform when a service platform generates a service (two users related to the service are respectively referred to as a first user and a second user), the service platform sends a transaction of the first user to the second user to the third-party platform. Request, executed by a third-party platform.
  • the transaction processing may be performed by the third party platform together with the agent of the first user (the agent of the first user is a proxy platform selected by the first user and the third party platform completes the transaction related matters).
  • the transaction specifically includes processing of specified information or items involved in the business generated between the first user and the second user.
  • the processing of the specified information or the item by the third-party platform includes: receiving the specified information or the item (corresponding to the transaction of the first user for the second user described in the present application), returning the specified information if the preset condition is met, or An item (corresponding to the first user described in this application revoking a transaction for the second user), and transmitting the specified information or item to the second user.
  • the first user requests to cancel the transaction for the second user for some reason. For example, if the first user's proxy requests to cancel the transaction for the second user, the first user's proxy sends a request to the third party platform to revoke the first user's transaction for the second user, and the undo transaction is satisfied. In the case of a preset condition, the third party platform will allow the agent of the first user to revoke the transaction for the second user.
  • the third-party platform cannot know the information related to the undo transaction, for example, it only knows that one agent cancels a transaction, and cannot know which first user corresponding to the transaction, which is the corresponding service platform. And the corresponding second user, etc., therefore, for the revocation office
  • the business of the third party platform cannot be associated with the related information of the corresponding transaction, and the business of the undo transaction cannot be effectively managed.
  • One of the technical problems to be solved by the present invention is to provide a transaction processing recording method and apparatus for implementing an undo transaction processing associated with related information of a corresponding transaction, thereby effectively managing the undo transaction.
  • a recording method for transaction processing including:
  • performing the transaction processing includes:
  • a first receipt executing the transaction is received from an agent of the first user.
  • revoking the transaction includes:
  • the first receipt and the second receipt include the same execution identification number.
  • the method further includes:
  • the execution identification number is associated with the identification of the first user and the identification of the service platform in the request from the service platform for the transaction of the first user for the second user.
  • the method further includes:
  • the identifier of the first user of the associated record and the identifier of the service platform are searched according to the execution identification number in the second receipt.
  • the method further includes:
  • the method further includes:
  • a transaction processing apparatus including:
  • a transaction processing and recording unit configured to execute the transaction in response to receiving a request from a service platform for a transaction of the first user for the second user, and recording the first user as an executor of the transaction,
  • the second user record is the recipient of the transaction;
  • Revoking a transaction processing and recording unit responsive to receiving a request from a first user's agent that the first user revokes a transaction for the second user, revoking the transaction, and recording the first user as a revocation
  • the recipient of the transaction, and the business platform is recorded as an executor who revokes the transaction.
  • the transaction processing and recording unit includes:
  • a sending subunit configured to send, to the agent of the first user, a request to perform the transaction
  • a transaction receipt receipt subunit is configured to receive a first receipt to perform the transaction from an agent of the first user.
  • the undo transaction processing and recording unit includes:
  • the revocation receipt receiving unit is configured to receive a second receipt for confirming the cancellation of the transaction from the agent of the first user.
  • the first receipt and the second receipt include the same execution identification number.
  • the transaction processing and recording unit further includes:
  • An association record subunit configured to receive, after receiving the first receipt of the transaction from the agent of the first user, the identification number and the first request from the service platform for the transaction of the first user for the second user A user's identity, the identity of the service platform, and associated records.
  • the undo transaction processing and recording unit further includes:
  • a locating unit configured to search for an identifier of the first user of the associated record and an identifier of the service platform according to the execution identification number in the second receipt in response to receiving the second receipt;
  • a recording subunit configured to record, by the first user corresponding to the identifier of the first user that is found by the searching subunit, as a recipient that cancels the transaction, and record the service platform corresponding to the identifier of the service platform as the withdrawal
  • the performer of the transaction is pinned.
  • the undo transaction processing and recording unit includes:
  • the obligation object space establishes a sub-unit for establishing the obligation object space of the service platform as an executor of the transaction.
  • the undo transaction processing and recording unit further includes:
  • a requesting subunit configured to request the service platform to perform an execution item as an executor of the transaction
  • a convergence subunit configured to converge the result of the service platform performing the required execution item as the executor of the transaction in the obligation object space.
  • the first user in executing the transaction processing of the first user for the second user, the first user is recorded as the executor of the transaction, the second user is recorded as the recipient of the transaction; and the execution of the first user is revoked for the second
  • the first user is recorded as the recipient of the transaction being revoked, and the service platform is recorded as the executor of the transaction.
  • FIG. 1 is a flow chart of a recording method of a transaction processing according to an embodiment of the present invention.
  • FIG. 2 is a flow chart of a method of performing a transaction, in accordance with one embodiment of the present invention.
  • FIG. 3 is a flow diagram of a method of performing an undo transaction, in accordance with one embodiment of the present invention.
  • FIG. 4 is a flowchart of an application scenario operation of a recording method of a transaction processing according to the present invention.
  • FIG. 5 is a block diagram showing the structure of a transaction processing apparatus according to an embodiment of the present invention.
  • FIG. 6 is a block diagram showing the structure of a transaction processing and recording unit according to an embodiment of the present invention.
  • FIG. 7 is a block diagram showing the structure of an undo transaction processing and recording unit according to an embodiment of the present invention.
  • FIG. 8 is a block diagram showing the structure of an undo transaction processing and recording unit according to another embodiment of the present invention.
  • the computer device includes a user device and a network device.
  • the user equipment includes, but is not limited to, a computer, a smart phone, a PDA, etc.
  • the network device includes but is not limited to a single network server, a server group composed of multiple network servers, or a cloud computing based computer Or a cloud composed of a network server, wherein cloud computing is a type of distributed computing, a super virtual computer composed of a group of loosely coupled computers.
  • the computer device can be operated separately to implement the present invention, and can also access the network and implement the present invention by interacting with other computer devices in the network.
  • the network in which the computer device is located includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a VPN network, and the like.
  • the user equipment, the network equipment, the network, and the like are merely examples, and other existing or future possible computer equipment or networks, such as those applicable to the present invention, are also included in the scope of the present invention. It is included here by reference.
  • the execution entity of the method is a third-party platform, and is applied to a third-party platform in the process of executing a transaction related matter of the first user for the second user.
  • the method mainly includes the following steps:
  • the first user and the second user are two users involved in one service generated in the service platform.
  • step S10 the transaction of the first user for the second user is a necessary execution step in the service, and the service can be sequentially executed only after the transaction is completed.
  • the first user is targeting the second
  • the transaction of the user that is, the first user fulfills the need for execution of the second user.
  • the transaction includes processing of specified information or items involved in the business generated between the first user and the second user.
  • the processing of the specified information or the item includes: receiving the specified information or the item (corresponding to the transaction of the first user for the second user in the embodiment), and returning the specified information or the item if the preset condition is met ( Corresponding to the first user described in the embodiment, the transaction for the second user is revoked), and the specified information or item is sent to the second user.
  • the request from the service platform for the transaction of the second user for the second user may include related information about the transaction, for example, including the number of the specified information or the item sent to the second user by the first user, and includes The identifier of the first user, the identifier of the service platform, the identifier of the second user, the service serial number, and the like.
  • the operation of performing the transaction may be performed by a third party platform in cooperation with the agent of the first user.
  • the agent of the first user is a proxy platform selected by the first user to complete the transaction with a third-party platform, that is, a platform for transmitting the specified information or item to a third-party platform.
  • the third-party platform may, after receiving the request from the service platform for the transaction of the first user for the second user, provide an agent for the user to select, and receive the agent selected by the first user, thereby determining that the cooperation is completed first. Which agent the user is handling for the second user's transaction.
  • the method of performing the transaction in an embodiment may be as shown in FIG. 2, and includes the following sub-steps:
  • Sub-step 101 sending a request to perform execution of the transaction to a proxy of the first user
  • the agent requesting the first user transmits the specified information or item and instructs to send the specified information or the number of items.
  • the service serial number of the corresponding service may be carried in the request, so that the agent of the first user records the association relationship between the transaction and the specific service.
  • Sub-step 102 receiving a first receipt executing the transaction from an agent of the first user.
  • the first receipt may include: the specified information or an item sent by the agent of the first user to the third-party platform; or the specified information sent by the agent of the first user to the third-party platform or The item and the manifest file of the specified information or item; may also include only the specified information or platform manifest file sent by the first user agent to the third-party platform (in this case, the received content has been received before receiving the first receipt) Specify information or items).
  • the agent of the first user may generate an execution identification number for the transaction. Carrying an execution identification number for the transaction in the first receipt, the third party platform may use the execution identification number from the service platform The first user performs an association record on the identifier of the first user and the identifier of the service platform in the request for processing the transaction of the second user, so that the corresponding first user and the service platform can be found according to the execution identification number.
  • the transaction is completed, and the first user may be recorded as the executor of the transaction, and the second user is recorded as the recipient of the transaction.
  • the executor of the transaction is equivalent to the specified information or the obligation sender of the item involved in the transaction; the recipient of the transaction is equivalent to the designated information or the right recipient of the item involved in the transaction.
  • Step S11 is a step of revoking the above transaction.
  • the undo transaction processing described in this embodiment is performed under the condition that the preset condition is satisfied, and the preset condition is, for example, within a predetermined time range in which the transaction is performed.
  • the preset condition is not specifically limited. In general, the request initiated by the first user to cancel the transaction for the second user satisfies the preset condition.
  • the request for the first user to revoke the transaction for the second user is simply referred to as a revocation request.
  • the transaction may be partially revoked, for example, returning the partial specified information or the item that the agent of the first user has sent to the third-party platform;
  • the transaction is revoked all, for example, by returning the specified information or item that all of the first user's agents have sent to the third party platform.
  • the first user can initiate the revocation request through the agent of the first user. That is, the first user requests the first user's agent to revoke the transaction for the second user.
  • the first user's agent sends the revocation request to the third party platform if the preset condition is met.
  • the cancellation request may carry the execution identification number of the transaction to be revoked, the specified information or the number of items to be revoked, and the like.
  • the third party platform performs the revocation of the transaction in response to receiving the revocation request from the agent of the first user.
  • An embodiment of the method of performing the method of revoking the transaction may be as shown in FIG. 3, including the following sub-steps:
  • Sub-step 111 revoking the transaction for the second user that the agent of the first user has performed.
  • the third-party platform After receiving the revocation request, the third-party platform first identifies whether the revocation request satisfies the preset condition, and the specific identification method is not specifically limited in this embodiment.
  • the third party platform allows the agent of the first user to revoke the transaction for the second user that the agent of the first user has performed. For example, the specified information or items received from the agent of the first user are returned to the agent of the first user in accordance with the amount indicated in the revocation request.
  • the third-party platform may not have executed the transaction with the second user, that is, the specified information or the item has not been sent to the second user; Transaction processing with the second user is performed, that is, the specified information or item has been sent to the second user.
  • Sub-step 112 receiving a second receipt from the agent of the first user for confirming the cancellation of the transaction.
  • the agent of the first user for the undo operation generates and sends a receipt (hereinafter referred to as a second receipt) to confirm the cancellation of the transaction.
  • the execution identifier of the revoked transaction is included in the second receipt, that is, the execution identification number it contains is the same as the execution identification number included in the first receipt. It can be understood that the second receipt is not limited to the execution identification number, and may include other information such as confirming the execution result of the revocation transaction.
  • the third-party platform in response to receiving the second receipt, can find the identifier of the first user of the associated record, the identifier of the service platform, and the like according to the execution identification number in the second receipt, thereby obtaining the association associated with the revoked transaction.
  • First user and business platform The first user can be recorded as the recipient of the transaction being revoked and the service platform is recorded as an executor who revokes the transaction. Equivalent to recording the first user as the designated information or the returned right of the returned party. Through this record, the transaction of the undo transaction can be associated with a specific user, thereby knowing which user of the specified information or the final recipient of the item corresponding to the undo service.
  • Recording the service platform as an executor to revoke the transaction is equivalent to recording the service platform as the specified sender of the returned information or the obligatory sender (ie, the payer).
  • the record it is possible to determine the corresponding sender for the specified information or item returned, so that the specified information or item having the same number of specified information or items returned can be obtained from the sender as compensation for realizing the transaction and Undo the effective management of specified information or items in a transaction.
  • the embodiment of the present application may also establish the service object platform as the obligation object space of the executor of the transaction processing, and may request the service platform to perform the required execution item as the executor of the transaction to perform the service platform fulfillment as a transaction.
  • the result of the required execution of the processed performer is gathered in the obligation object space.
  • the duty object space is a space for collecting the specified information or items.
  • Requesting the service platform to perform the required execution as the performer of the transaction includes: requesting the service platform to send the specified information or the item, the specified information or the quantity of the item to be sent and the specified information or item returned to the agent of the first user The same amount. Converging the results of the execution of the business platform as an executor of the transaction to the obligation pair
  • the image space, that is, the specified information or item acquired from the service platform is saved in the obligation object space.
  • the embodiment of the present application records the first user as the executor of the transaction, and records the second user as the recipient of the transaction;
  • the first user is recorded as the recipient of the transaction being revoked, and the service platform is recorded as the executor of the transaction.
  • the undo transaction can be associated with the related information of the corresponding transaction, thereby effectively managing the undo transaction.
  • an application scenario of the solution is taken as an example to further introduce the foregoing solution. It can be understood that the embodiments of the present application are not limited to the following application scenarios.
  • the specific scenario of the example is: on a service platform, a service is generated between user A and user B. During the execution of the service, the user A's funds need to be sent to user B through a third-party platform, that is, in this scenario.
  • the specified item involved in the transaction is funds.
  • the user A's funds are first sent to the third-party platform, and the third-party platform sends it to the user B in the specified case.
  • the flow of the specific transaction processing method is as shown in FIG. 4, and includes the following steps:
  • the agent platform selected by the user A After the agent platform selected by the user A sends the funds that the user A needs to pay the user B to the third-party platform, the agent platform selected by the user A sends a payment list file about the payment service to the third-party platform.
  • the payment list file contains the payment service serial number generated by the agent platform for the payment service.
  • the third-party platform records the payment service serial number with the user A and the service platform, and can also record the association with the user B at the same time.
  • the transaction of user A for user B is: user A sends a specified amount of funds to user B. Then, the user A, as the performer of the payment service, needs to execute the item: sending the designated amount of funds to the user B; recording the user B as the recipient of the payment service, that is, the specified amount sent by the user B as the user A. The right to receive funds.
  • the user A withdraws the payment to the user B, and returns the funds requested for revocation to the proxy platform, and records the user A as the recipient of the revocation service. Record the business platform as the executor of the business.
  • the third-party platform will allow the revocation behavior of the proxy platform selected by the user A, that is, the proxy platform selected by user A can successfully user.
  • a request for revocation of funds is returned from the third party platform.
  • the agent platform selected by the user A After successfully returning the funds requested by the user A to be revoked, the agent platform selected by the user A sends a revocation list file to the third-party platform, and the revocation list file includes the payment service serial number of the payment service for which the revocation service is directed.
  • the third-party platform can find the user A and the service platform of the previously associated record through the payment service serial number.
  • the agent platform selected by the user A cancels a fund
  • the corresponding funds need to be compensated to achieve the balance of funds within the third-party platform.
  • the user A can be recorded as The recipient of the cancellation service records the business platform as the executor of the cancellation service.
  • the executor of the service platform as the revoked service needs to execute the following items: send the funds involved in the revoked service to the user A; record the user A as the recipient of the revoked service, that is, record the user A as the revoked service. The right to accept the funds involved.
  • the cancellation service is associated with the related information in the payment service, so that the cancellation service can be effectively managed.
  • the embodiment of the present application further provides a recording device for transaction processing corresponding to the above-mentioned transaction processing method, and the device is disposed on a third-party platform, and a schematic structural diagram of an embodiment thereof is as shown in FIG. 5, and mainly includes the following Unit: transaction processing and recording unit 50 and revocation transaction processing and recording unit 51.
  • the transaction processing and recording unit 50 is configured to perform the transaction processing and record the first user as a transaction in response to receiving a request from the service platform for the transaction of the first user for the second user.
  • the executor recording the second user as the recipient of the transaction;
  • the first user and the second user are two users involved in one service generated in the service platform.
  • the transaction of the first user for the second user is a necessary execution step in the service, and the service can be sequentially executed only after the transaction is completed.
  • the transaction of the first user for the second user that is, the first user fulfills the required matter for the second user.
  • the transaction includes processing of specified information or items involved in the business generated between the first user and the second user.
  • the processing of the specified information or item includes: receiving the specified information or the item (corresponding to the first user for the second user described in this embodiment) Transmitting), returning the specified information or item if the preset condition is met (corresponding to the first user canceling the transaction for the second user in the embodiment), and transmitting the specified information or item to the second user.
  • the request from the service platform for the transaction of the second user for the second user may include related information about the transaction, for example, including the number of the specified information or the item sent to the second user by the first user, and includes The identifier of the first user, the identifier of the service platform, the identifier of the second user, the service serial number, and the like.
  • the operation of performing the transaction may be completed by the transaction processing and recording unit 50 in cooperation with the agent of the first user.
  • the agent of the first user is a proxy platform selected by the first user to cooperate with the third-party platform to complete the transaction, that is, a platform for transmitting the specified information or item.
  • the transaction processing and recording unit 50 may, after receiving the request from the service platform for the transaction of the first user for the second user, provide an agent for the user to select, and receive the agent selected by the first user, thereby determining the cooperation. Which agent is completed by the first user for the transaction of the second user.
  • the transaction processing and recording unit 50 can include the following sub-units to perform the operations of the transaction:
  • the sending subunit 501 is configured to send a request for performing the transaction to the agent of the first user; for example, requesting the agent of the first user to send the specified information or item, and instructing to send the specified information or the quantity of the item.
  • the service serial number of the corresponding service may be carried in the request, so that the agent of the first user records the association relationship between the transaction and the specific service.
  • a transaction receipt receipt sub-unit 502 is configured to receive a first receipt to perform the transaction from an agent of the first user.
  • the first receipt may include: the specified information or an item sent by an agent of the first user; or include: the specified information or item sent by an agent of the first user, and the specified information or item
  • the manifest file may also include only the specified information sent by the first user agent or the manifest file of the platform (in this case, the specified information or item has been received before receiving the first return receipt).
  • the transaction processing and recording unit 50 can also include:
  • the association record sub-unit 503 is configured to: after receiving the first receipt after fulfilling the obligation of the first user from the agent of the first user, execute the request with the identification number and the transaction of the first user from the service platform for the second user The identifier of the first user in the middle, and the identifier of the service platform.
  • the transaction processing and recording unit 50 records the first user as the executor of the transaction and the second user records For the recipient of the transaction, it is convenient for the third-party platform to effectively manage the transaction and subsequent undo transaction processing.
  • the executor of the transaction is equivalent to the specified information or the obligation sender of the item involved in the transaction; the recipient of the transaction is equivalent to the designated information or the right recipient of the item involved in the transaction.
  • the undo transaction processing described in this embodiment is performed under the condition that the preset condition is satisfied, and the preset condition is, for example, within a predetermined time range in which the transaction is performed.
  • the preset condition is not specifically limited. In general, the request initiated by the first user to cancel the transaction for the second user satisfies the preset condition.
  • the request for the first user to revoke the transaction for the second user is simply referred to as a revocation request.
  • the transaction may be partially revoked, for example, returning the partial specified information or the item that the agent of the first user has sent to the third-party platform;
  • the transaction is all revoked, for example, the specified information or item that has been sent by all of the first user's agents has been returned.
  • the first user can initiate the revocation request through the agent of the first user. That is, the first user requests the first user's agent to revoke the transaction for the second user.
  • the agent of the first user sends the revocation request to the device of the embodiment.
  • the cancellation request may carry the execution identification number of the transaction to be revoked, the specified information or the number of items to be revoked, and the like.
  • the undo transaction processing and recording unit 51 may include the following subunits to perform the operation of undoing the transaction:
  • the undo subunit 511 is configured to cancel the transaction for the second user that has been executed by the agent of the first user;
  • the third-party platform After receiving the revocation request, the third-party platform first identifies whether the revocation request satisfies the preset condition, and the specific identification method is not specifically limited in this embodiment.
  • the agent of the first user is allowed to revoke the transaction for the second user that the agent of the first user has performed.
  • the specified information or items received from the agent of the first user are returned to the agent of the first user in accordance with the amount indicated in the revocation request.
  • the third-party platform may not have executed the transaction with the second user, that is, the specified information or the item has not been sent to the second user; Execute transaction processing with the second user, that is, the specified information or item has been sent to the first Two users.
  • the revocation receipt receiving unit 512 is configured to receive a second receipt for confirming the revocation of the transaction from the agent of the first user.
  • the agent of the first user for the undo operation generates and sends a receipt (hereinafter referred to as a second receipt) to confirm the cancellation of the transaction.
  • the execution identifier of the revoked transaction is included in the second receipt, that is, the execution identification number it contains is the same as the execution identification number included in the first receipt. It can be understood that the second receipt is not limited to the execution identification number, and may include other information such as confirming the execution result of the revocation transaction.
  • the undo transaction processing and recording unit 51 described in this embodiment may further include:
  • the locating sub-unit 513 is configured to search, according to the execution identifier number in the second receipt, the identifier of the first user of the association record and the identifier of the service platform, so as to be associated with the revoked transaction, in response to receiving the second receipt.
  • a recording sub-unit 514 configured to record, by the first sub-user corresponding to the identifier of the first user that is searched by the sub-unit, as a revocation of the transaction, and record the service platform corresponding to the identifier of the service platform as revocation
  • the executor of the transaction Equivalent to recording the first user as the designated information or the returned right of the returned party.
  • the transaction of the undo transaction can be associated with a specific user, thereby knowing which user of the specified information or the final recipient of the item corresponding to the undo service. Recording the service platform as an executor who revokes the transaction is equivalent to recording the service platform as the obligated sender of the specified information or item returned.
  • the record it is possible to determine the corresponding sender (ie, the payer) for the specified information or item returned, so that the specified information or item having the same number of returns can be obtained from the sender as compensation for realizing the transaction. And the effective management of specified information or items in the revocation transaction.
  • the undo transaction processing and recording unit 51 may further include:
  • the obligation object space establishing sub-unit 515 is configured to establish the obligation object space of the service platform as an executor of the transaction process.
  • the requesting subunit 516 is configured to request the service platform to perform an execution item as an executor of the transaction.
  • the requesting execution of the service platform as an executor of the transaction includes: requesting the service platform to send the specified information or the item, the specified information or the quantity of the item to be sent and the specified information of the agent returned to the first user or The number of items is the same.
  • the convergence sub-unit 517 is configured to converge the result of the service platform fulfilling the required execution item as the executor of the transaction in the obligation object space.
  • the result of the business platform fulfilling the required execution item as the executor of the transaction is aggregated in the obligation object space, that is, the specified information or item acquired from the service platform is saved in the obligation object space.
  • the first user in performing transaction processing of the first user for the second user, the first user is recorded as the executor of the transaction, and the second user is recorded as the recipient of the transaction;
  • the first user In the transaction of the two users, the first user is recorded as the recipient of the transaction cancellation, and the service platform is recorded as the executor of the transaction.
  • the undo transaction can be associated with the related information of the corresponding transaction, thereby effectively managing the undo transaction.
  • the present invention can be implemented in software and/or a combination of software and hardware, for example, using an application specific integrated circuit (ASIC), a general purpose computer, or any other similar hardware device.
  • the software program of the present invention may be executed by a processor to implement the steps or functions described above.
  • the software program (including related data structures) of the present invention can be stored in a computer readable recording medium such as a RAM memory, a magnetic or optical drive or a floppy disk and the like.
  • some of the steps or functions of the present invention may be implemented in hardware, for example, as a circuit that cooperates with a processor to perform various steps or functions.
  • a portion of the invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide a method and/or solution in accordance with the present invention.
  • the program instructions for invoking the method of the present invention may be stored in a fixed or removable recording medium and/or transmitted by a data stream in a broadcast or other signal bearing medium, and/or stored in a The working memory of the computer device in which the program instructions are run.
  • an embodiment in accordance with the present invention includes a device including a memory for storing computer program instructions and a processor for executing program instructions, wherein when the computer program instructions are executed by the processor, triggering
  • the apparatus operates based on the aforementioned methods and/or technical solutions in accordance with various embodiments of the present invention.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种事务处理的记录方法及装置。其中，事务处理的记录方法包括：响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。实现了将撤销事务处理与对应的事务处理的相关信息相关联，从而有效管理撤销事务处理。

Description

事务处理的记录方法及装置
本申请要求2015年04月29日递交的申请号为201510213459.4、发明名称为“事务处理的记录方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计算机技术领域，尤其涉及一种事务处理的记录方法及装置。
背景技术
电子商务平台(以下简称业务平台)中发生的业务一般会引入第三方平台，由第三方平台作为业务中事务处理的安全监管方，来保证业务平台中事务处理的安全性。例如，在业务平台产生一个业务时(与该业务相关的两个用户分别称为第一用户和第二用户)，该业务平台会向第三方平台发送第一用户针对第二用户的事务处理的请求，由第三方平台执行该事务处理。所述事务处理具体的可以由该第三方平台与第一用户的代理(第一用户的代理是第一用户选择的配合第三方平台完成与事务处理相关事项的代理平台)共同来执行完成。
所述的事务处理具体的包括对第一用户与第二用户之间产生的业务中涉及的指定信息或物品的处理。第三方平台对该指定信息或物品的处理包括：接收指定信息或物品(对应本申请中所述的第一用户针对第二用户的事务处理)、在满足预设条件情况下退回该指定信息或物品(对应本申请中所述的第一用户撤销针对第二用户的事务处理)、以及将该指定信息或物品发送给第二用户。
在业务执行过程中经常会发生如下情况：第一用户由于某种原因请求撤销针对第二用户的事务处理。例如，其通过第一用户的代理请求撤销针对第二用户的事务处理，则第一用户的代理向第三方平台发送撤销第一用户针对第二用户的事务处理的请求，在满足撤销事务处理的预设条件情况下，则第三方平台会允许第一用户的代理撤销针对第二用户的事务处理。
此时，由于第三方平台无法获知与撤销事务处理相关的信息，例如，其仅知道一个代理撤销了一个事务处理，而无法获知该事务处理对应的第一用户是哪个，对应的业务平台是哪个，以及对应的第二用户是哪个等等，因此，对于该撤销事务处 理的业务，第三方平台无法与对应的事务处理的相关信息相关联，也就无法有效管理该撤销事务处理的业务。
发明内容
本发明解决的技术问题之一是提供一种事务处理的记录方法及装置，用以实现撤销事务处理与对应的事务处理的相关信息相关联，从而有效管理撤销事务处理。
根据本发明一方面的一个实施例，提供了一种事务处理的记录方法，包括：
响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；
响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。
可选地，执行所述事务处理包括：
向第一用户的代理发送执行所述事务处理的请求；
从第一用户的代理接收执行所述事务处理的第一回执。
可选地，撤销所述事务处理包括：
撤销第一用户的代理已执行的所述针对第二用户的事务处理；
接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
可选地，所述第一回执和第二回执中包含相同的执行标识号。
可选地，从第一用户的代理接收执行所述事务处理的第一回执后，所述方法还包括：
将执行标识号与来自业务平台的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识关联记录。
可选地，所述方法还包括：
响应于接收到第二回执，根据第二回执中的执行标识号查找关联记录的第一用户的标识、业务平台的标识。
可选地，所述方法还包括：
建立所述业务平台作为事务处理的执行者的义务对象空间。
可选地，所述方法还包括：
请求所述业务平台履行作为事务处理的执行者的需执行事项；
将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间。
根据本发明另一方面的一个实施例，提供了一种事务处理的记录装置，包括：
事务处理及记录单元，用于响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；
撤销事务处理及记录单元，用于响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。
可选地，所述事务处理及记录单元包括：
发送子单元，用于向第一用户的代理发送执行所述事务处理的请求；
事务处理回执接收子单元，用于从第一用户的代理接收执行所述事务处理的第一回执。
可选地，所述撤销事务处理及记录单元包括：
撤销子单元，用于撤销第一用户的代理已执行的所述针对第二用户的事务处理；
撤销回执接收单元，用于接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
可选地，所述第一回执和第二回执中包含相同的执行标识号。
可选地，所述事务处理及记录单元还包括：
关联记录子单元，用于从第一用户的代理接收执行所述事务处理的第一回执后，将执行标识号与来自业务平台的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识关联记录。
可选地，所述撤销事务处理及记录单元还包括：
查找子单元，用于响应于接收到第二回执，根据第二回执中的执行标识号查找关联记录的第一用户的标识、业务平台的标识；
记录子单元，用于将查找子单元查找出的第一用户的标识对应的第一用户记录为撤销所述事务处理的接受者，并将所述业务平台的标识对应的业务平台记录为撤 销所述事务处理的执行者。
可选地，所述撤销事务处理及记录单元包括：
义务对象空间建立子单元，用于建立所述业务平台作为事务处理的执行者的义务对象空间。
可选地，所述撤销事务处理及记录单元还包括：
请求子单元，用于请求所述业务平台履行作为事务处理的执行者的需执行事项；
汇聚子单元，用于将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间。
本实施例在执行第一用户针对第二用户的事务处理中，将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；在执行第一用户撤销针对第二用户的事务处理中，将第一用户记录为撤销所述事务处理的接受者，并将业务平台记录为撤销所述事务处理的执行者。通过该记录方式可将撤销事务处理与对应的事务处理的相关信息相关联，从而有效管理撤销事务处理。
本领域普通技术人员将了解，虽然下面的详细说明将参考图示实施例、附图进行，但本发明并不仅限于这些实施例。而是，本发明的范围是广泛的，且意在仅通过后附的权利要求限定本发明的范围。
附图说明
通过阅读参照以下附图所作的对非限制性实施例所作的详细描述，本发明的其它特征、目的和优点将会变得更明显：
图1是根据本发明一个实施例的事务处理的记录方法的流程图。
图2是根据本发明一个实施例的执行事务处理的方法的流程图。
图3是根据本发明一个实施例的执行撤销事务处理的方法的流程图。
图4是根据本发明的事务处理的记录方法的一种应用场景操作流程图。
图5是根据本发明一个实施例的事务处理的记录装置的结构示意图。
图6是根据本发明一个实施例的事务处理及记录单元的结构示意图。
图7是根据本发明一个实施例的撤销事务处理及记录单元的结构示意图。
图8是根据本发明另一个实施例的撤销事务处理及记录单元的结构示意图。
附图中相同或相似的附图标记代表相同或相似的部件。
具体实施方式
在更加详细地讨论示例性实施例之前应当提到的是，一些示例性实施例被描述成作为流程图描绘的处理或方法。虽然流程图将各项操作描述成顺序的处理，但是其中的许多操作可以被并行地、并发地或者同时实施。此外，各项操作的顺序可以被重新安排。当其操作完成时所述处理可以被终止，但是还可以具有未包括在附图中的附加步骤。所述处理可以对应于方法、函数、规程、子例程、子程序等等。
所述计算机设备包括用户设备与网络设备。其中，所述用户设备包括但不限于电脑、智能手机、PDA等；所述网络设备包括但不限于单个网络服务器、多个网络服务器组成的服务器组或基于云计算(Cloud Computing)的由大量计算机或网络服务器构成的云，其中，云计算是分布式计算的一种，由一群松散耦合的计算机集组成的一个超级虚拟计算机。其中，所述计算机设备可单独运行来实现本发明，也可接入网络并通过与网络中的其他计算机设备的交互操作来实现本发明。其中，所述计算机设备所处的网络包括但不限于互联网、广域网、城域网、局域网、VPN网络等。
需要说明的是，所述用户设备、网络设备和网络等仅为举例，其他现有的或今后可能出现的计算机设备或网络如可适用于本发明，也应包含在本发明保护范围以内，并以引用方式包含于此。
后面所讨论的方法(其中一些通过流程图示出)可以通过硬件、软件、固件、中间件、微代码、硬件描述语言或者其任意组合来实施。当用软件、固件、中间件或微代码来实施时，用以实施必要任务的程序代码或代码段可以被存储在机器或计算机可读介质(比如存储介质)中。(一个或多个)处理器可以实施必要的任务。
这里所公开的具体结构和功能细节仅仅是代表性的，并且是用于描述本发明的示例性实施例的目的。但是本发明可以通过许多替换形式来具体实现，并且不应当被解释成仅仅受限于这里所阐述的实施例。
应当理解的是，虽然在这里可能使用了术语“第一”、“第二”等等来描述各个单元，但是这些单元不应当受这些术语限制。使用这些术语仅仅是为了将一个单元与另一个单元进行区分。举例来说，在不背离示例性实施例的范围的情况下，第一单元可以被称为第二单元，并且类似地第二单元可以被称为第一单元。这里所使用的术语 “和/或”包括其中一个或更多所列出的相关联项目的任意和所有组合。
应当理解的是，当一个单元被称为“连接”或“耦合”到另一单元时，其可以直接连接或耦合到所述另一单元，或者可以存在中间单元。与此相对，当一个单元被称为“直接连接”或“直接耦合”到另一单元时，则不存在中间单元。应当按照类似的方式来解释被用于描述单元之间的关系的其他词语(例如“处于...之间”相比于“直接处于...之间”，“与...邻近”相比于“与...直接邻近”等等)。
这里所使用的术语仅仅是为了描述具体实施例而不意图限制示例性实施例。除非上下文明确地另有所指，否则这里所使用的单数形式“一个”、“一项”还意图包括复数。还应当理解的是，这里所使用的术语“包括”和/或“包含”规定所陈述的特征、整数、步骤、操作、单元和/或组件的存在，而不排除存在或添加一个或更多其他特征、整数、步骤、操作、单元、组件和/或其组合。
还应当提到的是，在一些替换实现方式中，所提到的功能/动作可以按照不同于附图中标示的顺序发生。举例来说，取决于所涉及的功能/动作，相继示出的两幅图实际上可以基本上同时执行或者有时可以按照相反的顺序来执行。
下面结合附图对本发明的技术方案作进一步详细描述。
图1是根据本发明一个实施例的事务处理的记录方法的流程图。该方法的执行主体为第三方平台，应用于第三方平台执行第一用户针对第二用户的事务处理相关事项的过程中。如图1中所示，所述方法主要包括如下步骤：
S10、响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者。
S11、响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。
下面对上述各步骤做进一步详细介绍。
其中，第一用户和第二用户是所述业务平台中所产生的一个业务所涉及的两个用户。
步骤S10中，所述的第一用户针对第二用户的事务处理是所述业务中的一个必要执行步骤，只有完成该事务处理，所述业务才能顺序执行。第一用户针对第二用 户的事务处理，即，第一用户履行针对第二用户的需执行事项。所述事务处理包括对第一用户与第二用户之间产生的业务中涉及的指定信息或物品的处理。对该指定信息或物品的处理包括：接收指定信息或物品(对应本实施例中所述的第一用户针对第二用户的事务处理)、在满足预设条件情况下退回该指定信息或物品(对应本实施例中所述的第一用户撤销针对第二用户的事务处理)、以及将该指定信息或物品发送给第二用户。
来自业务平台的、第一用户针对第二用户的事务处理的请求中可以包含关于所述事务处理的相关信息，例如，包含关于第一用户向第二用户发送指定信息或物品的数量，还包含：第一用户的标识、业务平台的标识、第二用户的标识及业务流水号等等。
其中，执行所述事务处理的操作可以由第三方平台与所述第一用户的代理配合来完成。所述的第一用户的代理是第一用户选择的配合第三方平台完成所述事务处理的代理平台，即发送所述指定信息或物品给第三方平台的平台。第三方平台可在接收到所述来自业务平台的、第一用户针对第二用户的事务处理的请求后，提供供用户选择的代理，并接收第一用户选择的代理，从而确定配合完成第一用户针对第二用户的事务处理的是哪个代理。
一种实施例中执行所述事务处理的方法可以如图2中所示，包括如下子步骤：
子步骤101、向第一用户的代理发送执行所述事务处理的请求；
例如，请求第一用户的代理发送所述指定信息或物品，并指示发送所述指定信息或物品的数量。其中，可以在该请求中携带对应业务的业务流水号，以便第一用户的代理记录该事务处理与具体业务的关联关系。
子步骤102、从第一用户的代理接收执行所述事务处理的第一回执。
需要说明的是，所述第一回执可以包括：第一用户的代理向第三方平台发送的所述指定信息或物品；或包括：第一用户的代理向第三方平台发送的所述指定信息或物品以及该指定信息或物品的清单文件；也可以仅包括第一用户代理发送给第三方平台的指定信息或平台的清单文件(此种情况下，在接收该第一回执前已经接收到所述指定信息或物品)。
其中，第一用户的代理可为该事务处理生成一执行标识号。在该第一回执中携带针对该事务处理的执行标识号，该第三方平台可将该执行标识号与来自业务平台 的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识进行关联记录，以便根据该执行标识号可查找到对应的第一用户以及业务平台。
接收到第一用户的代理发送的所述第一回执即执行完成了所述事务处理，此时可将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者，以方便第三方平台对该事务处理以及后续撤销事务处理进行有效管理。所述的事务处理的执行者相当于事务处理所涉及的指定信息或物品的义务发送方；所述的事务处理的接受者相当于事务处理所涉及的指定信息或物品的有权接收方。
步骤S11是关于撤销上述事务处理的步骤。本实施例所述的撤销事务处理是在满足预设条件情况下执行的，所述预设条件例如，在距离执行所述事务处理规定时间范围内。本实施例对该预设条件不做具体限制，总之第一用户发起的撤销针对第二用户的事务处理的请求满足该预设条件。
为描述方便，以下将第一用户撤销针对第二用户的事务处理的请求简称为撤销请求。
其中，对于第一用户撤销针对第二用户的事务处理的请求，可以是部分撤销所述事务处理，例如，退回第一用户的代理已经发送给第三方平台的部分指定信息或物品；也可以是全部撤销所述事务处理，例如，退回全部第一用户的代理已经发送给第三方平台的指定信息或物品。
第一用户可通过该第一用户的代理发起该撤销请求。也就是第一用户向第一用户的代理请求撤销针对第二用户的事务处理。在满足预设条件情况下，第一用户的代理会向第三方平台发送该撤销请求。其中，可在该撤销请求中携带需要撤销的所述事务处理的执行标识号以及需要撤销的指定信息或物品的数量等。第三方平台响应于接收到来自第一用户的代理的、撤销请求，执行撤销所述事务处理。一种实施例执行撤销所述事务处理的方法的流程可如图3中所示，包括如下子步骤：
子步骤111、撤销第一用户的代理已执行的针对第二用户的事务处理。
可以理解的是，第三方平台在接收到该撤销请求后会首先识别该撤销请求是否满足预设条件，具体识别方法本实施例不做具体限制。
在确定所述撤销请求满足预设条件情况下，第三方平台允许第一用户的代理撤销第一用户的代理已执行的针对第二用户的事务处理。例如，将从第一用户的代理接收的指定信息或物品中按照撤销请求中指示的数量退回给第一用户的代理。
需要说明的是，在执行撤销该事务处理的操作时，第三方平台有可能还没有执行与第二用户间的事务处理，也就是还没有将指定信息或物品发送给第二用户；也有可能已经执行与第二用户间的事务处理，也就是已经将指定信息或物品发送给第二用户。
子步骤112、接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
针对该撤销操作第一用户的代理会生成并发送一回执(本实施例以下称为第二回执)，用以对撤销所述事务处理进行确认。在第二回执中包含所撤销的事务处理的执行标识号，也就是其包含的执行标识号与所述第一回执中包含的执行标识号相同。可以理解的是，该第二回执中并不局限于所述执行标识号，还可包括对撤销事务处理的执行结果进行确认等其他信息。
第三方平台响应于接收到第二回执，根据第二回执中的执行标识号可以查找到关联记录的第一用户的标识、业务平台的标识等信息，从而获知与该撤销的事务处理相关联的第一用户以及业务平台。并可将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。相当于将第一用户记录为所退回的指定信息或物品的有权接收方。通过该记录可将撤销事务处理的业务与具体的用户关联，从而知道该撤销业务对应的指定信息或物品的最终接收方是哪个用户。将所述业务平台记录为撤销所述事务处理的执行者，相当于将业务平台记录为所退回的指定信息或物品的义务发送方(即赔付方)。通过该记录可以实现对于所退回的指定信息或物品确定出对应的发送方，从而可从该发送方获取与退回的指定信息或物品数量相同的指定信息或物品作为补偿，以实现对事务处理及撤销事务处理中指定信息或物品有效管理。
本申请实施例还可建立所述业务平台作为事务处理的执行者的义务对象空间，并可请求所述业务平台履行作为事务处理的执行者的需执行事项，以将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间。其中，义务对象空间是用于汇聚所述指定信息或物品的空间。请求所述业务平台履行作为事务处理的执行者的需执行事项包括：请求业务平台发送指定信息或物品，该发送的指定信息或物品的数量与退回给第一用户的代理的指定信息或物品的数量相同。将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对 象空间，即，将从业务平台获取的指定信息或物品保存于所述义务对象空间中。
从上面的描述可以看出，本申请实施例在执行第一用户针对第二用户的事务处理中，将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；在执行第一用户撤销针对第二用户的事务处理中，将第一用户记录为撤销所述事务处理的接受者，并将业务平台记录为撤销所述事务处理的执行者。通过该记录方式可将撤销事务处理与对应的事务处理的相关信息相关联，从而有效管理撤销事务处理。
为便于理解上述技术方案，下面以该方案的一种应用场景为例对上述方案做进一步介绍。可以理解的是，本申请实施例并不局限于以下应用场景。该实例的具体场景为：在一个业务平台上，用户A与用户B之间产生一个业务，该业务执行过程中，需要通过第三方平台将用户A的资金发送给用户B，即，此场景中事务处理涉及的指定物品为资金。该用户A的资金先发送给第三方平台，在指定情况下第三方平台再将其发送给用户B。则具体的事务处理的记录方法的流程如图4中所示，包括如下步骤：
S40、响应于接收到来自业务平台的、用户A向用户B付款的请求，与用户A选择的代理平台交互获取用户A需要付给用户B的资金，并将用户A记录为支付业务的执行者，将用户B记录为支付业务的接受者。
其中，在用户A选择的代理平台将用户A需要付给用户B的资金发送给第三方平台后，该用户A选择的代理平台会发送关于该付款业务的支付清单文件给第三方平台，在该支付清单文件中包含该代理平台为该支付业务生成的支付业务流水号。第三方平台将该支付业务流水号与用户A以及业务平台关联记录，当然也可同时与用户B进行关联记录。
此场景下，用户A针对用户B的事务处理即为：用户A向用户B发送指定数额的资金。则用户A作为该支付业务的执行者需执行事项即为：向用户B发送指定数额的资金；将用户B记录为该支付业务的接受者即，将用户B作为用户A发送的所述指定数额的资金的有权接受方。
S41、响应于接收到来自用户A选择的代理平台的、用户A撤销付款给用户B的请求，将请求撤销的资金退回给所述代理平台，并将用户A记录为该撤销业务的接受者，将业务平台记录为撤销业务的执行者。
假设用户A选择的代理平台是在满足预设条件情况下发出的该撤销请求，则第三方平台将允许该用户A选择的代理平台的撤销行为，即，用户A选择的代理平台能够成功将用户A请求撤销的资金从第三方平台退回。该用户A选择的代理平台在成功退回用户A请求撤销的资金后，会向第三方平台发送一个撤销清单文件，在该撤销清单文件中包含该撤销业务所针对的支付业务的支付业务流水号。第三方平台通过该支付业务流水号可以查找到之前关联记录的用户A以及业务平台等信息。此时对于第三方平台来说，由于被用户A选择的代理平台撤销一笔资金，则需要有相应的资金作为补偿才能实现第三方平台内部的资金收支平衡，此时可将用户A记录为该撤销业务的接受者，将业务平台记录为撤销业务的执行者。则此时业务平台作为撤销业务的执行者需执行事项为：发送撤销业务中涉及的资金给用户A；将用户A记录为该撤销业务的接受者，即，将用户A记录为撤销业务中所涉及资金的有权接受方。通过该记录，可以确定被撤销的资金的去向，也就是被撤销的资金最终对应哪个用户的账户，以及从哪获取相应的补偿资金。本实施例不区分第三方平台是否已经将该用户A的资金发送给用户B，均将业务平台作为撤销的资金的补偿方。通过该记录方式实现了撤销业务与支付业务中相关信息相关联，从而可有效管理撤销业务。
本申请实施例还提供一种与上述事务处理的记录方法相对应的事务处理的记录装置，该装置设置于第三方平台，其一种实施例的结构示意图如图5中所示，主要包括如下单元：事务处理及记录单元50及撤销事务处理及记录单元51。
其中，事务处理及记录单元50，主要用于响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；
其中，第一用户和第二用户是所述业务平台中所产生的一个业务所涉及的两个用户。
所述的第一用户针对第二用户的事务处理是所述业务中的一个必要执行步骤，只有完成该事务处理，所述业务才能顺序执行。第一用户针对第二用户的事务处理，即，第一用户履行针对第二用户的需执行事项。所述事务处理包括对第一用户与第二用户之间产生的业务中涉及的指定信息或物品的处理。对该指定信息或物品的处理包括：接收指定信息或物品(对应本实施例中所述的第一用户针对第二用户的事 务处理)、在满足预设条件情况下退回该指定信息或物品(对应本实施例中所述的第一用户撤销针对第二用户的事务处理)、以及将该指定信息或物品发送给第二用户。
来自业务平台的、第一用户针对第二用户的事务处理的请求中可以包含关于所述事务处理的相关信息，例如，包含关于第一用户向第二用户发送指定信息或物品的数量，还包含：第一用户的标识、业务平台的标识、第二用户的标识及业务流水号等等。
其中，执行所述事务处理的操作可以由事务处理及记录单元50与所述第一用户的代理配合来完成。所述的第一用户的代理是第一用户选择的配合第三方平台完成所述事务处理的代理平台，即发送所述指定信息或物品的平台。事务处理及记录单元50可在接收到所述来自业务平台的、第一用户针对第二用户的事务处理的请求后，提供供用户选择的代理，并接收第一用户选择的代理，从而确定配合完成第一用户针对第二用户的事务处理的是哪个代理。
如图6中所示，该事务处理及记录单元50可包括如下子单元以执行事务处理的操作：
发送子单元501，用于向第一用户的代理发送执行所述事务处理的请求；例如，请求第一用户的代理发送所述指定信息或物品，并指示发送所述指定信息或物品的数量。其中，可以在该请求中携带对应业务的业务流水号，以便第一用户的代理记录该事务处理与具体业务的关联关系。
事务处理回执接收子单元502，用于从第一用户的代理接收执行所述事务处理的第一回执。
需要说明的是，所述第一回执可以包括：第一用户的代理发送的所述指定信息或物品；或包括：第一用户的代理发送的所述指定信息或物品以及该指定信息或物品的清单文件；也可以仅包括第一用户代理发送的指定信息或平台的清单文件(此种情况下，在接收该第一回执前已经接收到所述指定信息或物品)。
所述事务处理及记录单元50还可包括：
关联记录子单元503，用于从第一用户的代理接收履行第一用户的义务后的第一回执后，将执行标识号与来自业务平台的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识关联记录。
事务处理及记录单元50将第一用户记录为事务处理的执行者，将第二用户记录 为事务处理的接受者，以方便第三方平台对该事务处理以及后续撤销事务处理进行有效管理。所述的事务处理的执行者相当于事务处理所涉及的指定信息或物品的义务发送方；所述的事务处理的接受者相当于事务处理所涉及的指定信息或物品的有权接收方。
本实施例所述的撤销事务处理是在满足预设条件情况下执行的，所述预设条件例如，在距离执行所述事务处理规定时间范围内。本实施例对该预设条件不做具体限制，总之第一用户发起的撤销针对第二用户的事务处理的请求满足该预设条件。
为描述方便，以下将第一用户撤销针对第二用户的事务处理的请求简称为撤销请求。
其中，对于第一用户撤销针对第二用户的事务处理的请求，可以是部分撤销所述事务处理，例如，退回第一用户的代理已经发送给第三方平台的部分指定信息或物品；也可以是全部撤销所述事务处理，例如，退回全部第一用户的代理已经发送的指定信息或物品。
第一用户可通过该第一用户的代理发起该撤销请求。也就是第一用户向第一用户的代理请求撤销针对第二用户的事务处理。在满足预设条件情况下，第一用户的代理会向本实施例的装置发送该撤销请求。其中，可在该撤销请求中携带需要撤销的所述事务处理的执行标识号以及需要撤销的指定信息或物品的数量等。
如图7中所示，该撤销事务处理及记录单元51可包括如下子单元来完成撤销所述事务处理的操作：
撤销子单元511，用于撤销第一用户的代理已执行的所述针对第二用户的事务处理；
可以理解的是，第三方平台在接收到该撤销请求后会首先识别该撤销请求是否满足预设条件，具体识别方法本实施例不做具体限制。
在确定所述撤销请求满足预设条件情况下，允许第一用户的代理撤销第一用户的代理已执行的针对第二用户的事务处理。例如，将从第一用户的代理接收的指定信息或物品中按照撤销请求中指示的数量退回给第一用户的代理。
需要说明的是，在执行撤销该事务处理的操作时，第三方平台有可能还没有执行与第二用户间的事务处理，也就是还没有将指定信息或物品发送给第二用户；也有可能已经执行与第二用户间的事务处理，也就是已经将指定信息或物品发送给第 二用户。
撤销回执接收单元512，用于接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
针对该撤销操作第一用户的代理会生成并发送一回执(本实施例以下称为第二回执)，用以对撤销所述事务处理进行确认。在第二回执中包含所撤销的事务处理的执行标识号，也就是其包含的执行标识号与所述第一回执中包含的执行标识号相同。可以理解的是，该第二回执中并不局限于所述执行标识号，还可包括对撤销事务处理的执行结果进行确认等其他信息。
本实施例所述的撤销事务处理及记录单元51还可包括：
查找子单元513，用于响应于接收到第二回执，根据第二回执中的执行标识号查找关联记录的第一用户的标识、业务平台的标识，从而可获知与该撤销的事务处理相关联的第一用户以及业务平台；
记录子单元514，用于将查找子单元查找出的第一用户的标识对应的第一用户记录为撤销所述事务处理的接受者，并将所述业务平台的标识对应的业务平台记录为撤销所述事务处理的执行者。相当于将第一用户记录为所退回的指定信息或物品的有权接收方。通过该记录可将撤销事务处理的业务与具体的用户关联，从而知道该撤销业务对应的指定信息或物品的最终接收方是哪个用户。将所述业务平台记录为撤销所述事务处理的执行者相当于将业务平台记录为所退回的指定信息或物品的义务发送方。通过该记录可以实现对于所退回的指定信息或物品确定出对应的发送方(即赔付方)，从而可从该发送方获取与退回的数量相同的指定信息或物品作为补偿，以实现对事务处理及撤销事务处理中指定信息或物品有效管理。
如图8中所示，撤销事务处理及记录单元51还可包括：
义务对象空间建立子单元515，用于建立所述业务平台作为事务处理的执行者的义务对象空间。
请求子单元516，用于请求所述业务平台履行作为事务处理的执行者的需执行事项。
其中，请求所述业务平台履行作为事务处理的执行者的需执行事项包括：请求业务平台发送指定信息或物品，该发送的指定信息或物品的数量与退回给第一用户的代理的指定信息或物品的数量相同。
汇聚子单元517，用于将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间。
将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间，即，将从业务平台获取的指定信息或物品保存于所述义务对象空间中。
本申请实施例在执行第一用户针对第二用户的事务处理中，将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；在执行第一用户撤销针对第二用户的事务处理中，将第一用户记录为撤销所述事务处理的接受者，并将业务平台记录为撤销所述事务处理的执行者。通过该记录方式可将撤销事务处理与对应的事务处理的相关信息相关联，从而有效管理撤销事务处理。
需要注意的是，本发明可在软件和/或软件与硬件的组合体中被实施，例如，可采用专用集成电路(ASIC)、通用目的计算机或任何其他类似硬件设备来实现。在一个实施例中，本发明的软件程序可以通过处理器执行以实现上文所述步骤或功能。同样地，本发明的软件程序(包括相关的数据结构)可以被存储到计算机可读记录介质中，例如，RAM存储器，磁或光驱动器或软磁盘及类似设备。另外，本发明的一些步骤或功能可采用硬件来实现，例如，作为与处理器配合从而执行各个步骤或功能的电路。
另外，本发明的一部分可被应用为计算机程序产品，例如计算机程序指令，当其被计算机执行时，通过该计算机的操作，可以调用或提供根据本发明的方法和/或技术方案。而调用本发明的方法的程序指令，可能被存储在固定的或可移动的记录介质中，和/或通过广播或其他信号承载媒体中的数据流而被传输，和/或被存储在根据所述程序指令运行的计算机设备的工作存储器中。在此，根据本发明的一个实施例包括一个装置，该装置包括用于存储计算机程序指令的存储器和用于执行程序指令的处理器，其中，当该计算机程序指令被该处理器执行时，触发该装置运行基于前述根据本发明的多个实施例的方法和/或技术方案。
对于本领域技术人员而言，显然本发明不限于上述示范性实施例的细节，而且在不背离本发明的精神或基本特征的情况下，能够以其他的具体形式实现本发明。因此，无论从哪一点来看，均应将实施例看作是示范性的，而且是非限制性的，本发明的范围由所附权利要求而不是上述说明限定，因此旨在将落在权利要求的等同要件的含义和范围内的所有变化涵括在本发明内。不应将权利要求中的任何附图标 记视为限制所涉及的权利要求。此外，显然“包括”一词不排除其他单元或步骤，单数不排除复数。系统权利要求中陈述的多个单元或装置也可以由一个单元或装置通过软件或者硬件来实现。第一，第二等词语用来表示名称，而并不表示任何特定的顺序。

Claims (16)

  1. 一种事务处理的记录方法，其特征在于，包括：
    响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；
    响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。
  2. 根据权利要求1所述的方法，其特征在于，执行所述事务处理包括：
    向第一用户的代理发送执行所述事务处理的请求；
    从第一用户的代理接收执行所述事务处理的第一回执。
  3. 根据权利要求2所述的方法，其特征在于，撤销所述事务处理包括：
    撤销第一用户的代理已执行的所述针对第二用户的事务处理；
    接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
  4. 根据权利要求3所述的方法，其特征在于，所述第一回执和第二回执中包含相同的执行标识号。
  5. 根据权利要求4所述的方法，其特征在于，从第一用户的代理接收执行所述事务处理的第一回执后，所述方法还包括：
    将执行标识号与来自业务平台的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识关联记录。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    响应于接收到第二回执，根据第二回执中的执行标识号查找关联记录的第一用户的标识、业务平台的标识。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    建立所述业务平台作为事务处理的执行者的义务对象空间。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    请求所述业务平台履行作为事务处理的执行者的需执行事项；
    将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述 义务对象空间。
  9. 一种事务处理的记录装置，其特征在于，包括：
    事务处理及记录单元，用于响应于接收到来自业务平台的、第一用户针对第二用户的事务处理的请求，执行所述事务处理，并将第一用户记录为事务处理的执行者，将第二用户记录为事务处理的接受者；
    撤销事务处理及记录单元，用于响应于接收到来自第一用户的代理的、第一用户撤销针对第二用户的事务处理的请求，撤销所述事务处理，并将第一用户记录为撤销所述事务处理的接受者，并将所述业务平台记录为撤销所述事务处理的执行者。
  10. 根据权利要求9所述的装置，其特征在于，所述事务处理及记录单元包括：
    发送子单元，用于向第一用户的代理发送执行所述事务处理的请求；
    事务处理回执接收子单元，用于从第一用户的代理接收执行所述事务处理的第一回执。
  11. 根据权利要求10所述的装置，其特征在于，所述撤销事务处理及记录单元包括：
    撤销子单元，用于撤销第一用户的代理已执行的所述针对第二用户的事务处理；
    撤销回执接收单元，用于接收来自第一用户的代理的、用于对撤销所述事务处理进行确认的第二回执。
  12. 根据权利要求11所述的装置，其特征在于，所述第一回执和第二回执中包含相同的执行标识号。
  13. 根据权利要求12所述的装置，其特征在于，所述事务处理及记录单元还包括：
    关联记录子单元，用于从第一用户的代理接收执行所述事务处理的第一回执后，将执行标识号与来自业务平台的、第一用户针对第二用户的事务处理的请求中的第一用户的标识、业务平台的标识关联记录。
  14. 根据权利要求13所述的装置，其特征在于，所述撤销事务处理及记录单元还包括：
    查找子单元，用于响应于接收到第二回执，根据第二回执中的执行标识号查找 关联记录的第一用户的标识、业务平台的标识；
    记录子单元，用于将查找子单元查找出的第一用户的标识对应的第一用户记录为撤销所述事务处理的接受者，并将所述业务平台的标识对应的业务平台记录为撤销所述事务处理的执行者。
  15. 根据权利要求9所述的装置，其特征在于，所述撤销事务处理及记录单元包括：
    义务对象空间建立子单元，用于建立所述业务平台作为事务处理的执行者的义务对象空间。
  16. 根据权利要求15所述的装置，其特征在于，所述撤销事务处理及记录单元还包括：
    请求子单元，用于请求所述业务平台履行作为事务处理的执行者的需执行事项；
    汇聚子单元，用于将所述业务平台履行作为事务处理的执行者的需执行事项的结果汇聚于所述义务对象空间。
PCT/CN2016/079828 2015-04-29 2016-04-21 事务处理的记录方法及装置 Ceased WO2016173444A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510213459.4 2015-04-29
CN201510213459.4A CN106203970A (zh) 2015-04-29 2015-04-29 事务处理的记录方法及装置

Publications (1)

Publication Number Publication Date
WO2016173444A1 true WO2016173444A1 (zh) 2016-11-03

Family

ID=57199678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079828 Ceased WO2016173444A1 (zh) 2015-04-29 2016-04-21 事务处理的记录方法及装置

Country Status (2)

Country Link
CN (1) CN106203970A (zh)
WO (1) WO2016173444A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108776886B (zh) * 2018-05-11 2021-02-05 创新先进技术有限公司 一种事务协助方法、装置及电子设备
CN113793155B (zh) * 2018-06-27 2024-04-19 创新先进技术有限公司 一种对已发出消息的处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101183449A (zh) * 2007-12-26 2008-05-21 腾讯科技（深圳）有限公司 一种电子交易方法及系统
JP4199570B2 (ja) * 2003-03-26 2008-12-17 株式会社富士通ソーシアルサイエンスラボラトリ ホテルオーダ処理システム、ホテルオーダ処理方法、ホテルオーダ処理プログラム
CN101454794A (zh) * 2006-03-30 2009-06-10 奥博佩公司 移动的个人之间支付系统
CN102521747A (zh) * 2011-12-05 2012-06-27 中国联合网络通信集团有限公司 电子钱包账户绑定方法、业务处理方法、装置及系统
CN102970373A (zh) * 2012-12-03 2013-03-13 亚信联创科技（中国）有限公司 一种数据同步方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4199570B2 (ja) * 2003-03-26 2008-12-17 株式会社富士通ソーシアルサイエンスラボラトリ ホテルオーダ処理システム、ホテルオーダ処理方法、ホテルオーダ処理プログラム
CN101454794A (zh) * 2006-03-30 2009-06-10 奥博佩公司 移动的个人之间支付系统
CN101183449A (zh) * 2007-12-26 2008-05-21 腾讯科技（深圳）有限公司 一种电子交易方法及系统
CN102521747A (zh) * 2011-12-05 2012-06-27 中国联合网络通信集团有限公司 电子钱包账户绑定方法、业务处理方法、装置及系统
CN102970373A (zh) * 2012-12-03 2013-03-13 亚信联创科技（中国）有限公司 一种数据同步方法、装置及系统

Also Published As

Publication number Publication date
CN106203970A (zh) 2016-12-07

Similar Documents

Publication Publication Date Title
US9459860B2 (en) Mixed mode session management
WO2021026420A1 (en) Blockchain-based secure resource management
US9665577B2 (en) Controlling enterprise data on mobile device via the use of a tag index
US10050899B2 (en) Data processing method, apparatus, client, server and system
CA2824394C (en) Method and system for providing a session in a heterogeneous environment
KR20140056004A (ko) 메타데이터 조정기를 통한 보안
JP2019503000A (ja) 異なるシステム間でのサービス操作を実行する方法、サービスプラットフォーム及びターゲットシステム
CN104125078B (zh) 云计算服务委托计费的方法及服务器
KR20140047230A (ko) 분산 시스템에서 분산 트랜잭션의 최적화를 위한 방법 및 트랜잭션을 최적화한 분산 시스템
WO2016173444A1 (zh) 事务处理的记录方法及装置
CN106301881B (zh) 一种业务处理方法和装置
CN110233843B (zh) 一种用户请求的处理方法及装置
RU2696299C2 (ru) Управление при инициировании элементарных задач на серверной платформе
JP2019510289A (ja) サービス処理方法及び装置
US11385924B1 (en) Method and system for collecting user information according to providing virtual desktop infrastructure service
US8712786B2 (en) Method and apparatus for controlling a multi-node process
CN112395104A (zh) 一种分布式事务上下文在路由层传递的实现方法与装置
CN105787791A (zh) 业务请求处理方法及装置
WO2023246480A1 (zh) 一种身份认证方法、装置、设备、介质及产品
WO2014094315A1 (zh) 在系统升级过程中对业务进行处理的方法、装置和设备
CA3037933C (en) Method and system for moving customer data to trusted storage
US9672083B2 (en) Operating a program code object in conjunction with an application context
CN109347940B (zh) 处理跨域业务请求及对跨域业务的请求方法和装置
US10599528B1 (en) Deviceless brokerless backup
HK1231229A1 (zh) 事务处理的记录方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16785875

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16785875

Country of ref document: EP

Kind code of ref document: A1