CN109523045B

CN109523045B - Method and equipment for providing travel service

Info

Publication number: CN109523045B
Application number: CN201811292481.2A
Authority: CN
Inventors: 史超; 王华瑞
Original assignee: Shenzhen Smartcom Business Co ltd
Current assignee: Shenzhen Smartcom Business Co ltd
Priority date: 2018-10-31
Filing date: 2018-10-31
Publication date: 2021-03-30
Anticipated expiration: 2038-10-31
Also published as: CN109523045A

Abstract

The embodiment of the application discloses a method for providing travel service and related equipment, wherein the method comprises the following steps: the first block chain node receives travel service information; the block link points generate travel blocks according to travel service information; the block chain node initiates a check process on the travel block, where the check process includes: the block chain node checks the travel block and/or sends the travel block to other block chain nodes except the block chain node in a block chain system for checking; if the travel block is successfully verified, the block link point records the travel block into a travel block chain; and the block link point informs other block link points to record the travel block into a travel block chain. The embodiment of the application can enhance the reliability of the travel service information.

Description

Method and equipment for providing travel service

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for providing travel services.

Background

Travel management, also called business travel management, refers to that an enterprise plans the whole travel activities with the help of Travel Management Company (TMC) and purchases resources as a whole. The travel management process and policy can be optimized through travel management, and the travel cost is further reduced and the travel efficiency is improved on the premise of not influencing business development and travel experience. At present, TMC generally stores business travel service transaction conditions of enterprise users in its own information system, and the credit granting state and fund usage details of an enterprise are not open to external enterprise users, so that the information is opaque and the credibility is low.

Content of application

The embodiment of the application provides a method and related equipment for providing travel service, which can enhance the credibility of travel service information.

In a first aspect, an embodiment of the present application provides a method for providing travel service, which is applied to a blockchain system, where the blockchain system includes at least two blockchain nodes, and the method includes: the first block link point receives travel service information, wherein the travel service information comprises information generated by calling an intelligent contract by an enterprise client and/or information generated by calling the intelligent contract by a TMC client of a travel service company; the first block link point generates a travel block according to the travel service information and initiates verification processing on the travel block; if the travel block is successfully verified, the first block link point records the travel block into a travel block chain; and the first block link point informs other block link points to record the travel block into a travel block chain.

By the mode, the block link point can receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information can be ensured by verifying the travel service information by the block link point; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

With reference to the first aspect, in a possible implementation manner, the checking process includes: and the block chain node checks the travel block and/or sends the travel block to other block chain nodes except the block chain node in a block chain system for checking.

With reference to the first aspect, in a possible implementation manner, the initiating the verification processing on the travel block includes: the first blockchain node broadcasts the travel block to the other blockchain devices; the first block chain link point receives verification success information sent by other block chain nodes; and if the number of the received verification success information is larger than the number threshold, the block link point determines that the verification of the travel block is successful.

With reference to the first aspect, in a possible implementation manner, the travel service information is generated by the TMC client invoking a predetermined information sent by an intelligent contract to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

With reference to the first aspect, in a possible implementation manner, the predetermined information is sent to the second block link node by the TMC client after determining that a target user has a predetermined right to the second block link node; wherein whether or not to have the predetermined authority is determined by the second block link point based on a user identification of a target user and/or a predetermined digital asset.

With reference to the first aspect, in a possible implementation manner, the travel service information is generated by the TMC client invoking a credit return confirmation message sent by an intelligent contract to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

With reference to the first aspect, in a possible implementation manner, the money return confirmation message is generated by the TMC client after receiving an event notification that money return is successful, where the event notification is sent by the second blockchain node; the event notification of successful reimbursement is generated after the second blockchain node verifies that the first money information and the second money information are successful; the first money information is generated after the first server receives a payment response of the second server, and the second money information is generated after the second server successfully collects money.

With reference to the first aspect, in a possible implementation manner, the money return confirmation message is generated after the TMC client receives a verification message that the collection is successful, where the verification message is sent by the second server; the verification message of successful collection is generated after the second server receives the verification request sent by the TMC client and verifies that collection is successful; the verification request is generated after the TMC client receives a refund event notification sent to the TMC client by the second block link point calling intelligent contract.

With reference to the first aspect, in a possible implementation manner, the refund event notification is generated after the enterprise client receives a payment completion notification sent by the first server, and the payment completion notification is generated after the first server receives a payment response sent by the second server.

In a second aspect, an embodiment of the present application provides another method for providing a travel service, including: the TMC client receives a first verification request of a TMC subscription system, wherein the first verification request is used for indicating whether a verification target user has a predetermined right or not; the TMC client calls an intelligent contract to send a second verification request to the block chain node; the TMC client receives a verification result sent by the block chain node; and if the verification result shows that the target user has the preset authority, the TMC client sends a preset response message to the TMC subscription system, wherein the preset response message is used for indicating the TMC subscription system to execute the reservation.

With reference to the second aspect, in a possible implementation manner, the TMC client receives predetermined information, where the predetermined information is generated after the TMC subscription system performs subscription according to the predetermined response message; and the TMC client calls an intelligent contract to send the reservation information to the block chain nodes, and the reservation information is used for storing the block chain nodes in the travel block chain.

In a third aspect, an embodiment of the present application provides another method for providing a travel service, including: when detecting a money return request event, the enterprise client generates a money return request; the enterprise client calls an intelligent contract to send the refund request to the block chain node, the refund request is used for indicating the block chain node to generate a first event notification, and the first event notification is used for indicating the first server to transfer the digital assets to the second server.

With reference to the third aspect, in one possible implementation manner, the detecting, by the enterprise client, a refund request event includes:

the enterprise client receives a second event notification sent by the blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to make a refund; the enterprise client side calls an intelligent contract to monitor that a target user needs to pay back; the enterprise client receives one or more of the rebate trigger operations.

With reference to the third aspect, in a possible implementation manner, the method further includes: the enterprise client receives an event notice of successful money return sent by the block chain node; the enterprise client issues a notification indicating that the target user has completed the transfer of the digital asset.

In a fourth aspect, an embodiment of the present application provides a first blockchain node located in a blockchain system, where the blockchain system includes at least two blockchain nodes, and the first blockchain node includes a receiving unit, a checking unit, a recording unit, and a notification unit, where: the receiving unit is used for receiving travel service information, and the travel service information comprises information generated by calling an intelligent contract by an enterprise client and/or information generated by calling the intelligent contract by a TMC client of a travel service company; the checking unit is used for generating a travel block according to the travel service information and initiating checking processing on the travel block; the recording unit is used for recording the travel block into a travel block chain when the travel block is successfully verified; and the notification unit is used for notifying other block link points to record the travel block into a travel block chain.

With reference to the fourth aspect, in a possible implementation manner, the verification unit is specifically configured to: and checking the travel block and/or sending the travel block to other block chain nodes except the block chain node in a block chain system for checking.

With reference to the fourth aspect, in a possible implementation manner, the verification unit is specifically configured to: broadcasting the travel blocks to the other blockchain devices; receiving successful verification information sent by the other block chain nodes; and if the number of the received verification success information is larger than the number threshold, determining that the verification of the travel block is successful.

With reference to the fourth aspect, in a possible implementation manner, the travel service information is generated by the TMC client invoking a predetermined information sent by an intelligent contract to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

With reference to the fourth aspect, in a possible implementation manner, the predetermined information is sent to the second block link node by the TMC client after determining that a target user has a predetermined right to the second block link node; wherein whether or not to have the predetermined authority is determined by the second block link point based on a user identification of a target user and/or a predetermined digital asset.

With reference to the fourth aspect, in a possible implementation manner, the travel service information is generated by the TMC client invoking an intelligent contract to send a fund return confirmation message to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

With reference to the fourth aspect, in a possible implementation manner, the money return confirmation message is generated after the TMC client receives an event notification that money return is successful, where the event notification is sent by the second blockchain node; the event notification of successful reimbursement is generated after the second blockchain node verifies that the first money information and the second money information are successful; the first money information is generated after the first server receives a payment response of the second server, and the second money information is generated after the second server successfully collects money.

With reference to the fourth aspect, in a possible implementation manner, the money return confirmation message is generated after the TMC client receives a verification message that the money collection is successful, where the verification message is sent by the second server; the verification message of successful collection is generated after the second server receives the verification request sent by the TMC client and verifies that collection is successful; the verification request is generated after the TMC client receives a refund event notification sent to the TMC client by the second block link point calling intelligent contract.

With reference to the fourth aspect, in a possible implementation manner, the refund event notification is generated after the enterprise client receives a payment completion notification sent by the first server, and the payment completion notification is generated after the first server receives a payment response sent by the second server.

In a fifth aspect, an embodiment of the present application provides a TMC client, where the TMC client includes a first receiving unit, a second receiving unit, a first sending unit, and a second sending unit, where: the first receiving unit is used for receiving a first verification request of the TMC reservation system, wherein the first verification request is used for indicating whether a verification target user has a preset authority or not; the first sending unit is used for calling the intelligent contract to send a second verification request to the block chain link point; the second receiving unit is configured to receive a verification result sent by the blockchain node; and the second receiving unit is used for sending a predetermined response message to the TMC subscription system when the verification result shows that the target user has the predetermined right, wherein the predetermined response message is used for indicating the TMC subscription system to execute the reservation.

With reference to the fifth aspect, in a possible implementation manner, the TMC client further includes a third receiving unit and a third sending unit, where: the third receiving unit is configured to receive predetermined information, where the predetermined information is generated after the TMC reservation system performs reservation according to the predetermined response message; the third sending unit is configured to invoke an intelligent contract to send the reservation information to a block link node, where the reservation information is used for the block link node to be stored in a travel block chain.

In a sixth aspect, an embodiment of the present application provides an enterprise client, where the enterprise client includes a generating unit and a sending unit, where: the generating unit is used for generating a money return request when a money return request event is detected; the sending unit is used for calling the intelligent contract to send the refund request to the block chain node, the refund request is used for indicating the block chain node to generate a first event notification, and the first event notification is used for indicating the first server to transfer the digital assets to the second server.

With reference to the sixth aspect, in a possible implementation manner, the enterprise client further includes a detection unit, where the detection unit is specifically configured to: receiving a second event notification sent by a blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to pay back; calling an intelligent contract to monitor whether a target user needs to pay back or not; one or more of the rebate trigger operations are received.

With reference to the sixth aspect, in a possible implementation manner, the enterprise client further includes a receiving unit and a publishing unit, where: the receiving unit is configured to receive an event notification that the money return is successful, where the event notification is sent by the blockchain node; the publishing unit is configured to publish a notification indicating that the target user has completed the transfer of the digital asset.

In a seventh aspect, an embodiment of the present application provides another first blockchain node, including a processor and a memory, where the processor and the memory are connected to each other, where the memory is configured to store program instructions, and the processor is configured to call the program instructions in the memory to execute the method described in the first aspect or any possible implementation manner of the first aspect.

In an eighth aspect, an embodiment of the present application provides another TMC client, including a processor and a memory, where the processor and the memory are connected to each other, where the memory is used to store program instructions, and the processor is used to call the program instructions in the memory to execute the method described in the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, the present application provides another enterprise client, including a processor and a memory, where the processor and the memory are connected to each other, where the memory is used to store program instructions, and the processor is used to call the program instructions in the memory to execute the method described in the third aspect or any possible implementation manner of the third aspect.

In a tenth aspect, embodiments of the present application provide a computer-readable storage medium, where the computer-readable storage medium stores program instructions, and when the program instructions are executed by a processor, the processor performs the first aspect or any possible implementation manner of the first aspect, or performs the second aspect or any possible implementation manner of the second aspect, or performs the method described in any possible implementation manner of the third aspect or the third aspect.

In an eleventh aspect, an embodiment of the present application provides a computer program, which when executed on a processor, performs the above first aspect or any possible implementation manner of the first aspect, or performs any possible implementation manner of the second aspect or the second aspect, or performs the method described in any possible implementation manner of the third aspect or the third aspect.

In the embodiment of the application, the block link node can receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information can be ensured through the verification of the block link node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.

Fig. 1 is a schematic diagram of a system architecture for providing travel services according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a system architecture for providing travel services according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a system architecture for providing travel services according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a system architecture for providing travel services according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for providing travel services according to an embodiment of the present application;

FIG. 6 is a flow chart of a method for providing a scheduled travel service provided by an embodiment of the present application;

fig. 7 is a flowchart of a method for providing a refund travel service according to an embodiment of the present application;

FIG. 8 is a flowchart of a method for providing a refund travel service according to an embodiment of the present application;

fig. 9 is a schematic diagram of a first blockchain node according to an embodiment of the present application;

fig. 10 is a schematic diagram of a TMC client provided in an embodiment of the present application;

FIG. 11 is a schematic diagram of an enterprise client provided by an embodiment of the present application;

fig. 12 is a schematic diagram of a first blockchain node according to another embodiment of the present invention;

fig. 13 is a schematic diagram of another TMC client provided in an embodiment of the present application;

fig. 14 is a schematic diagram of another enterprise client provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application are described in more detail below.

Referring to fig. 1, a schematic diagram of a system architecture for providing travel service according to an embodiment of the present application is shown, where the system includes a blockchain system, an enterprise client, and a TMC client; the blockchain system can communicate with the enterprise client, and can also communicate with the TMC client. These devices will be further described below.

And the block chain system is used for storing business or travel service information generated by TMC in the application. Wherein, a plurality of interconnected and interactive block chain link points form the block chain system. In the blockchain system, a distributed data storage and point-to-point transmission mode is adopted, and the different blockchain nodes in one blockchain system have the common identity. In this application, the travel service information (e.g., authorization status, transaction information, etc.) stored in the blockchain is public and non-tamperproof to both the enterprise side and the TMC side, making the travel service information trustworthy.

An enterprise client through which an enterprise may issue a travel service request (e.g., booking an airline ticket service, booking a hotel service, canceling a booking service, etc.) to a TMC booking system. The enterprise client and the TMC booking system may communicate over a wired network or a wireless network. Specifically, the enterprise client is a terminal device with a communication function, for example, a computer, a mobile phone, a tablet computer, and the like.

And the TMC client is used for operating the TMC reservation system, managing the TMC reservation system and processing the travel service request sent by the enterprise. The TMC client and the TMC subscription system may communicate through a wired network or a wireless network, and may also communicate through a data line. Specifically, the TMC client is a terminal device with a communication function, such as a computer, a mobile phone, a tablet computer, and the like.

Fig. 2 is a schematic diagram of another system architecture for providing travel services according to an embodiment of the present application, in which a TMC reservation system is added to the system architecture based on fig. 1. The TMC reservation system can communicate with the enterprise client, and can also communicate with the TMC client. Specifically, the TMC reservation system is used to provide information on travel services, such as air ticket information, hotel information, and the like. A business-issued travel service request may be received. Through the processing of the travel service request by the TMC client, the TMC reservation system provides the enterprise with the reservation of the travel service. Specifically, the TMC subscription system has terminal devices, such as computers, servers, and the like, having communication and data processing functions.

Fig. 3 is a schematic diagram of another system architecture for providing travel services according to an embodiment of the present application, in which a first server and a second server are added to the system architecture based on fig. 1. The first server can communicate with the blockchain system and can also communicate with the second server; the second server may be in communication with the blockchain system. Specifically, the first server is a server of a first bank where the enterprise user handles the fund service, and the second server is a server of a second bank where the TMC handles the fund service. This connection enables the bank to communicate directly with the blockchain system.

Referring to fig. 4, a schematic diagram of another system architecture for providing travel services according to an embodiment of the present application is provided, in which a first server and a second server are added to the basic system architecture of fig. 1. Wherein the first server may be in communication with the enterprise client, the first server may also be in communication with the second server; the second server may communicate with the TMC client. Specifically, the first server is a server of a first bank where the enterprise user handles the fund service, and the second server is a server of a second bank where the TMC handles the fund service. The connection mode can enable the bank to carry out information transmission with the client connected with the bank.

Referring to fig. 5, which is a flowchart of a method for providing travel service provided by an embodiment of the present application, the method may be implemented based on the architecture shown in fig. 1, and a block link point described below may be a block link node in the system architecture shown in fig. 1, and the method includes, but is not limited to, the following steps.

S501, the first block link point receives travel service information.

The first blockchain node is determined by a consensus algorithm for a plurality of blockchain nodes in the blockchain system, and is used for constructing a block and/or a broadcast block. The travel service information comprises information generated by calling the intelligent contract by the enterprise client and/or information generated by calling the intelligent contract by the TMC client of the travel service company. In particular, a smart contract (smart contract) is a computer protocol that aims to propagate, verify, or execute contracts in an informational manner. Smart contracts allow trusted transactions to be conducted without third parties, which transactions are traceable and irreversible. In the traditional travel service process, the travel service information of the enterprise is stored in an information system inside the TMC, the credit and fund use condition of the enterprise is not opened to enterprise clients, and the information is opaque. Therefore, the enterprises and the TMC are not trusted, and the enterprises consume the information recorded by the TMC and may have doubt on the consumption information. In the scheme, the block chain technology based on the intelligent contract is adopted to process the travel service information, so that the real and credible travel service information can be provided.

In a possible case, the travel service information is generated by the TMC client invoking a predetermined message sent by an intelligent contract to a second blockchain node, where the second blockchain node is any one of the first blockchain node or the other blockchain nodes. Specifically, the reservation information may be information for reserving travel services (e.g., reserving hotels, reserving airline tickets, etc.) for the enterprise user; information about scheduled business trip changes, such as changing scheduled hotel stay dates, changing scheduled airplane trip dates, adjusting the price of scheduled tickets, etc.; information for canceling a reservation for a travel service may also be provided, such as canceling a reservation for a hotel, canceling a reservation for a motor car, and so forth. A detailed description will be made later on the generation process of the travel service information in the predetermined scenario.

In yet another possible case, the travel service information is generated by the TMC client invoking a refund confirmation message sent by an intelligent contract to a second blockchain node, where the second blockchain node is any one of the first blockchain node or the other blockchain nodes. The generation process of the travel service information in the refund scene will be specifically described later.

S502, the first block link point generates a travel block according to the travel service information, and initiates verification processing on the travel block.

Wherein the verification process comprises: and the block chain node checks the travel block and/or sends the travel block to other block chain nodes except the block chain node in a block chain system for checking. The checking the travel block by the block chain node comprises the following steps: and checking whether the contents of the travel block are accurate or not according to the check field, and determining whether the data address contained in the travel block is real and valid or not.

Specifically, the initiating the verification processing on the travel block includes: the first blockchain node broadcasts the travel block to the other blockchain devices; the first block chain link point receives verification success information sent by other block chain nodes; and if the number of the received verification success information is larger than the number threshold, the block link point determines that the verification of the travel block is successful.

S503, if the travel block is successfully verified, the first block link point records the travel block into a travel block chain.

The correctness of the travel service information can be ensured through the verification of the block link point on the travel service information.

S504, the first block link point informs other block link points to record the travel block into a travel block chain.

In this way, each blockchain node in the blockchain system can be made to store the same and credible travel service information. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

In the method shown in fig. 5, the block link node may receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information may be ensured through the verification of the block link node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 6, it is a flowchart of a method for providing scheduled travel service provided in this embodiment, where the method may be implemented based on the architecture shown in fig. 2, a block link point described below may be a block link node in the system architecture shown in fig. 2, a TMC client described below may be a TMC client in the system architecture shown in fig. 2, and a TMC scheduling system described below may be a TMC scheduling system in the system architecture shown in fig. 2, where the method includes, but is not limited to, the following steps.

S601, the enterprise client sends a reservation request to the TMC reservation system, and correspondingly, the TMC reservation system receives the reservation request.

S602, the TMC booking system sends a first verification request to the TMC client according to the booking request.

The first authentication request is used for indicating whether an authentication target user has a preset authority or not, and the first authentication request contains a user identification of the target user.

S603, the TMC client calls an intelligent contract to send a second verification request to the block chain node, and correspondingly, the block chain node receives the second verification request.

The second verification request and the first verification request can be the same, and the TMC client forwards the first verification request sent by the TMC subscription system to the block chain node; the second verification request may also be different from the first verification request, where the second verification request is information generated by the TMC client according to the first verification request, and the second verification request is used to indicate whether the block link node verifies that the target user has the predetermined right.

S604, the block chain node verifies whether the target user has the preset authority, and a verification result is generated.

Wherein the blockchain node verifies whether the target user has a predetermined right, which is determined according to the user identification of the target user and/or a predetermined digital asset. The block chain node stores the corresponding relation between the user identification and the preset digital assets. Specifically, the value of the amount of money available to the target user is the difference between the target user's predetermined digital assets minus the assets that have been used. And when the difference value obtained by subtracting the preset required amount from the available amount of the target user is not less than zero, the target user has the preset authority.

S605, the block link node sends the verification result to the TMC client, and correspondingly, the TMC client receives the verification result sent by the block link node.

S606, if the verification result shows that the target user does not have the preset authority, the TMC client sends a response message which does not allow the preset to a TMC booking system; accordingly, the TMC subscription system receives the response message not allowing subscription.

S607, the TMC subscription system sends the event notice of not allowing subscription to the enterprise client according to the response message of not allowing subscription.

S608, if the verification result shows that the target user has the predetermined authority, the TMC client sends a predetermined response message to the TMC subscription system; accordingly, the TMC subscription system receives the subscription response message.

Wherein the reservation response message is used to instruct the TMC reservation system to perform a reservation.

And S609, the TMC booking system performs booking according to the booking response message and generates a booking message.

S610, the TMC booking system sends the booking information to the TMC client, and correspondingly, the TMC client receives the booking information.

S611, the TMC client calls an intelligent contract to send the preset information to the block chain node, and correspondingly, the block chain node receives the preset information.

Specifically, the reservation information is stored in the travel block chain as travel service information through the block link point. The method for receiving the travel service message by the blockchain node and storing the travel service message in the travel blockchain may refer to the method shown in fig. 5, and details are not repeated here.

In the method shown in fig. 6, the block link node may receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information may be ensured through the verification of the block link node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 7, which is a flowchart of a method for providing a refund travel service according to an embodiment of the present disclosure, the method may be implemented based on the architecture shown in fig. 3, a block link node described below may be a block link node in the system architecture shown in fig. 3, a TMC client described below may be a TMC client in the system architecture shown in fig. 3, an enterprise client described below may be an enterprise client in the system architecture shown in fig. 3, a first server described below may be a first server in the system architecture shown in fig. 3, and a second server described below may be a second server in the system architecture shown in fig. 3. The method includes, but is not limited to, the following steps.

And S701, generating a money return request when the enterprise client detects a money return request event.

The enterprise client detects a money return request event, and the method comprises the following steps: the enterprise client receives a second event notification sent by the blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to make a refund; the enterprise client side calls an intelligent contract to monitor that a target user needs to pay back; the enterprise client receives one or more of the rebate trigger operations. The rebate trigger may be an operation entered by an enterprise user.

There may be two situations where the target user needs to make a refund. Both of these cases will be described below.

In a first case, the intelligent contract is used for monitoring the credit granting status of the one or more enterprise users, and the credit granting status includes one or more of no early warning, early warning and no booking. Specifically, the credit granting state of the enterprise indicates that the available amount of money of the enterprise is greater than or equal to a preset threshold value when no early warning is given, the credit granting state of the enterprise indicates that the available amount of money of the enterprise in the early warning is less than the preset threshold value and greater than zero, and the credit granting state of the enterprise indicates that the available amount of money of the enterprise is equal to zero or less than zero when the enterprise is not booked. Wherein the value of the available amount of the enterprise user is the difference of the preset digital assets of the target user minus the used assets. And when the monitored credit granting state of the target user is in early warning or not bookable, indicating that the target user needs to pay back.

In a second case, the intelligent contract is used to monitor the time interval between the current time and the last time the one or more enterprise users made a money. Specifically, the preset time interval is a money return period allocated to the enterprise user by the TMC in advance, and may be one month, two months, three months, and the like. And if the time interval between the current time and the last time of the money making of the target user is greater than the preset time interval, indicating that the target user needs to make money back.

S702, the enterprise client calls an intelligent contract to send the money return request to the block chain node, and correspondingly, the block chain node receives the money return request.

And S703, the block link node generates a first event notification according to the money return request.

Wherein the first event notification is to instruct the first server to transfer the digital asset to the second server.

S704, the block chain node sends the first event notification to a first server, and correspondingly, the first server receives the first event notification.

S705, the first server informs the second server of the transfer of the digital assets according to the first event, and correspondingly, the second server receives the transfer of the digital assets.

S706, the second server sends a payment response to the first server, and correspondingly, the first server receives the payment response from the second server.

And S707, the first server generates first money information according to the payment response sent by the second server.

The first money information comprises account information of a payer, account information of a payee, a collection amount and the like.

And S708, the second server generates second money information according to the received digital assets.

S709, the first server sends the first money information to the block link point.

And S710, the second server sends the second money information to the blockchain node.

The second money information comprises account information of a payer, account information of a payee, a collection amount and the like.

And S711, if the block link point verifies that the first money information is the same as the second money information, sending an event notification of successful money return to a TMC client, and correspondingly, receiving the event notification of successful money return sent by the block link node by the TMC client.

And if the block link point verifies that the first money information is not the same as the second money information, sending an event notification of money return failure to the TMC client to notify that the digital asset transfer is unsuccessful.

And S712, the TMC client generates travel service information according to the event notification of successful money return sent by the block link node.

Wherein the travel service message is to notify the target user that the transfer of digital assets has been completed.

S713, the TMC client calls an intelligent contract to send the travel service information to the block link point, and correspondingly, the block link point receives the travel service information.

Specifically, the travel service information is stored in the travel block chain through the block chain node. The method for receiving the travel service message by the blockchain node and storing the travel service message in the travel blockchain may refer to the method shown in fig. 5, and details are not repeated here.

S714, the block link node sends an event notification of successful money return to the enterprise client, and correspondingly, the enterprise client receives the notification of the money return event.

And S715, the enterprise client sends a notice according to the notice of the refund event.

Wherein the notification indicates that the target user has completed the transfer of the digital asset.

In the method shown in fig. 7, the block link node may receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information may be ensured through the verification of the block link node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 8, which is a flowchart of another method for providing a refund travel service according to an embodiment of the present disclosure, the method may be implemented based on the architecture shown in fig. 4, the block link node described below may be a block link node in the system architecture shown in fig. 4, the TMC client described below may be a TMC client in the system architecture shown in fig. 4, the enterprise client described below may be an enterprise client in the system architecture shown in fig. 4, the first server described below may be a first server in the system architecture shown in fig. 4, and the second server described below may be a second server in the system architecture shown in fig. 4. The method includes, but is not limited to, the following steps.

And S801, generating a money return request when the enterprise client detects a money return request event.

This step is the same as S701 and is not described here again.

S802, the enterprise client sends the money returning request to a first server, and correspondingly, the first server receives the money returning request.

And S803, the first server transfers the digital assets to a second server according to the refund request, and correspondingly, the second server receives the transfer of the digital assets.

S804, the second server sends a payment response to the first server, and correspondingly, the first server receives the payment response of the second server.

And S805, the first server generates a payment completion notification according to the payment response.

S806, the first server sends the payment completion notification to the enterprise client, and correspondingly, the enterprise client receives the payment completion notification.

S807, the enterprise client generates a refund event notification according to the payment completion notification sent by the first server.

Wherein the refund event notification is to notify the enterprise user that the transfer of the digital asset has been completed.

And S808, the enterprise client calls an intelligent contract to send a money return event notification to the block link node, and correspondingly, the block link node equipment receives the money return event notification.

And S809, the block link node calls an intelligent contract to send the money return event notification to the TMC client, and correspondingly, the TMC client receives the money return event notification sent by the block link node.

And S810, the TMC client generates a verification request according to the refund event notification.

Wherein the validation request is for instructing the second server to validate whether it has received a transfer of the correct amount of the digital asset.

S810, the TMC client sends the verification request to the second server, and correspondingly, the second server receives the verification request.

S811, if the second server is successful in verification, the second server sends a verification message that the money collection is successful to the TMC client, and correspondingly, the TMC client receives the verification message that the money collection is successful.

And S812, the TMC client generates money return confirmation information according to the verification message that the money collection is successful.

And S813, the TMC client calls an intelligent contract to send the money return confirmation information to the block chain node.

Specifically, the money return confirmation information is stored in the travel block chain as travel service information through the block link point. The method for receiving the travel service message by the blockchain node and storing the travel service message in the travel blockchain may refer to the method shown in fig. 5, and details are not repeated here.

S814, the block link node sends an event notification of successful money return to the enterprise client, and correspondingly, the enterprise client receives the notification of the money return event.

And S815, the enterprise client side issues a notice according to the notice of the money return event.

In the method shown in fig. 8, the block link node may receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information may be ensured through the verification of the block link node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Above, embodiments of the method of the present application are described, and below, corresponding embodiments of the apparatus are described.

Referring to fig. 9, which is a schematic diagram of a first blockchain node provided in an embodiment of the present application and located in a blockchain system, where the blockchain system includes at least two blockchain nodes, and the first blockchain node includes a receiving unit 901, a checking unit 902, a recording unit 903, and a notification unit 904. These units will be described in detail below.

The receiving unit 901 is configured to receive travel service information, where the travel service information includes information generated by an enterprise client invoking an intelligent contract and/or information generated by a travel service company TMC client invoking an intelligent contract.

The verification unit 902 is configured to generate a travel block according to the travel service information, and initiate verification processing on the travel block.

The recording unit 903 is configured to record the travel block into a travel block chain when the travel block is successfully verified.

The notifying unit 904 is configured to notify other block link points to record the travel block into a travel block chain.

In a possible implementation manner, the verification unit is specifically configured to: and checking the travel block and/or sending the travel block to other block chain nodes except the block chain node in a block chain system for checking.

In a possible implementation manner, the verification unit is specifically configured to: broadcasting the travel blocks to the other blockchain devices; receiving successful verification information sent by the other block chain nodes; and if the number of the received verification success information is larger than the number threshold, determining that the verification of the travel block is successful.

In a possible implementation manner, the travel service information is generated by predetermined information sent by the TMC client invoking an intelligent contract to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

In a possible implementation manner, the predetermined information is sent to the second block link node by the TMC client after determining that the target user has the predetermined right to the second block link node; wherein whether or not to have the predetermined authority is determined by the second block link point based on a user identification of a target user and/or a predetermined digital asset.

In a possible implementation manner, the travel service information is generated by the TMC client invoking a credit return confirmation message sent by an intelligent contract to a second block chain node, where the second block chain node is any one of the first block chain node and the other block chain nodes.

In a possible implementation manner, the money return confirmation message is generated after the TMC client receives an event notification that the money return is successful, where the event notification is sent by the second blockchain node; the event notification of successful reimbursement is generated after the second blockchain node verifies that the first money information and the second money information are successful; the first money information is generated after the first server receives a payment response of the second server, and the second money information is generated after the second server successfully collects money.

In a possible implementation manner, the money return confirmation message is generated after the TMC client receives a verification message that money collection is successful and sent by the second server; the verification message of successful collection is generated after the second server receives the verification request sent by the TMC client and verifies that collection is successful; the verification request is generated after the TMC client receives a refund event notification sent to the TMC client by the second block link point calling intelligent contract.

In a possible implementation manner, the refund event notification is generated after the enterprise client receives a payment completion notification sent by the first server, and the payment completion notification is generated after the first server receives a payment response sent by the second server.

In the block link point shown in fig. 9, the block link point may receive travel service information sent by an enterprise client or a TMC client, and the correctness of the travel service information may be ensured through the verification of the block link point on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 10, which is a schematic diagram of a TMC client provided in this embodiment of the application, the TMC client 100 includes a first receiving unit 1001, a second receiving unit 1002, a first sending unit 1003, and a second sending unit 1004. These units will be described in detail below.

The first receiving unit 1001 is configured to receive a first authentication request of the TMC subscription system, where the first authentication request is used to indicate whether an authentication target user has a predetermined right.

The first sending unit 1002 is configured to invoke an intelligent contract to send a second verification request to the block chain node.

The second receiving unit 1003 is configured to receive the verification result sent by the blockchain node.

The second sending unit 1004 is configured to send, to the TMC subscription system, a reservation response message when the verification result indicates that the target user has the predetermined right, where the reservation response message is used to instruct the TMC subscription system to perform reservation.

In a possible implementation manner, the TMC client further includes a third receiving unit and a third sending unit, where: the third receiving unit is configured to receive predetermined information, where the predetermined information is generated after the TMC reservation system performs reservation according to the predetermined response message; the third sending unit is configured to invoke an intelligent contract to send the reservation information to a block link node, where the reservation information is used for the block link node to be stored in a travel block chain.

In addition, the implementation of the operations in fig. 10 may also correspond to the corresponding description with reference to any one of the method embodiments shown in fig. 5-8.

In the TMC client shown in fig. 10, the travel service information sent by the enterprise client or the TMC client may be received by the block link node, and the correctness of the travel service information may be ensured by verifying the travel service information by the block link node; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 11, it is a schematic diagram of an enterprise client provided in an embodiment of the present application, where the enterprise client includes a generating unit 1101 and a sending unit 1102. These units will be described in detail below.

The generating unit 1101 is configured to generate a money return request when a money return request event is detected.

The sending unit 1102 is configured to invoke an intelligent contract to send the refund request to a block link point, where the refund request is used to instruct the block link point to generate a first event notification, and the first event notification is used to instruct a first server to transfer a digital asset to a second server.

In a possible implementation manner, the enterprise client further includes a detection unit, where the detection unit is specifically configured to: receiving a second event notification sent by a blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to pay back; calling an intelligent contract to monitor whether a target user needs to pay back or not; one or more of the rebate trigger operations are received.

In one possible implementation manner, the enterprise client further includes a receiving unit and a publishing unit, where: the receiving unit is configured to receive an event notification that the money return is successful, where the event notification is sent by the blockchain node; the publishing unit is configured to publish a notification indicating that the target user has completed the transfer of the digital asset.

In addition, the implementation of the operations in fig. 11 may also correspond to the corresponding description with reference to any one of the method embodiments shown in fig. 5-8.

In the enterprise client illustrated in fig. 11, the travel service information sent by the enterprise client or the TMC client may be received by the block link node, and the correctness of the travel service information may be ensured by verifying the travel service information by the block link node; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 12, which is a schematic diagram of a further first blockchain node according to an embodiment of the present invention, the first blockchain node 120 includes a processor 1201, a memory 1202, and a communication interface 1203, where the processor 1201, the memory 1202, and the communication interface 1203 are connected to each other through a bus 1204.

The memory 1202 includes, but is not limited to, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1202 is used for related instructions and data. The communication interface 1203 is used for receiving and transmitting data.

The processor 1201 may be one or more Central Processing Units (CPUs), and in the case that the processor 1201 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1201 in the server 120 is configured to read the program code stored in the memory 1202, and perform the following operations:

and receiving travel service information, wherein the travel service information comprises information generated by calling an intelligent contract by an enterprise client and/or information generated by calling the intelligent contract by a TMC client of a travel service company.

And generating a travel block according to the travel service information, and initiating verification processing on the travel block.

And if the travel block is successfully verified, recording the travel block into a travel block chain.

And informing other block link points to record the traveling block into a traveling block chain.

In a possible implementation manner, the processor 1201 is specifically configured to: and the block chain node checks the travel block and/or sends the travel block to other block chain nodes except the block chain node in a block chain system for checking.

In a possible implementation manner, the processor 1201 is specifically configured to: the first blockchain node broadcasts the travel block to the other blockchain devices; the first block chain link point receives verification success information sent by other block chain nodes; and if the number of the received verification success information is larger than the number threshold, the block link point determines that the verification of the travel block is successful.

In addition, the implementation of the operations in fig. 12 may also correspond to the corresponding description with reference to any one of the method embodiments shown in fig. 5-8.

In the first block chain node shown in fig. 12, the block chain node may receive the travel service information sent by the enterprise client or the TMC client, and the correctness of the travel service information may be ensured through the verification of the block chain node on the travel service information; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 13, it is a schematic diagram of another TMC client provided in this embodiment of the present application, where the TMC client includes a processor 1301, a memory 1302, and a communication interface 1303, and the processor 1301, the memory 1302, and the communication interface 1303 are connected to each other through a bus 1304.

The memory 1302 includes, but is not limited to, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1302 is used for related instructions and data. The communication interface 1303 is used for receiving and transmitting data.

The processor 1301 may be one or more Central Processing Units (CPUs), and in the case that the processor 1301 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1301 in the server 130 is configured to read the program code stored in the memory 1302, and perform the following operations:

a first authentication request of a TMC subscription system is received, the first authentication request indicating whether an authentication target user has a predetermined right.

And calling the intelligent contract to send a second verification request to the block chain node.

And receiving the verification result sent by the block chain node.

And if the verification result shows that the target user has the preset authority, sending a preset response message to the TMC reservation system, wherein the preset response message is used for indicating the TMC reservation system to execute the reservation.

In a possible implementation manner, the processor 1301 is further configured to receive predetermined information, where the predetermined information is generated after the TMC reservation system performs reservation according to the predetermined response message; and the TMC client calls an intelligent contract to send the reservation information to the block chain nodes, and the reservation information is used for storing the block chain nodes in the travel block chain.

In addition, the implementation of the operations in fig. 13 may also correspond to the corresponding description with reference to any one of the method embodiments shown in fig. 5-8.

In the TMC client shown in fig. 13, the travel service information sent by the enterprise client or the TMC client may be received by the block link node, and the correctness of the travel service information may be ensured by verifying the travel service information by the block link node; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

Referring to fig. 14, a schematic diagram of another enterprise client according to an embodiment of the present invention is provided, where the enterprise client 140 includes a processor 1401, a memory 1402, and a communication interface 1403, and the processor 1401, the memory 1402, and the communication interface 1403 are connected to each other through a bus 1404.

The memory 1402 includes, but is not limited to, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1402 is used for related instructions and data. Communication interface 1403 is used for receiving and transmitting data.

The processor 1401 may be one or more Central Processing Units (CPUs), and in the case where the processor 1401 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1401 in the server 140 is configured to read the program code stored in the memory 1402, and perform the following operations:

when a refund request event is detected, a refund request is generated.

And calling an intelligent contract to send the refund request to the block chain node, wherein the refund request is used for indicating the block chain node to generate a first event notice, and the first event notice is used for indicating the first server to transfer the digital assets to the second server.

In one possible implementation, the processor 1401 is further configured to: receiving a second event notification sent by a blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to pay back; calling an intelligent contract to monitor whether a target user needs to pay back or not; one or more of the rebate trigger operations are received.

In one possible implementation, the processor 1401 is further configured to: receiving an event notice of successful money return sent by the blockchain node; a notification is issued indicating that the target user has completed the transfer of the digital asset.

In addition, the implementation of each operation in fig. 14 may also correspond to the corresponding description with reference to any one of the method embodiments shown in fig. 5-8.

In the enterprise client shown in fig. 14, the travel service information sent by the enterprise client or the TMC client may be received by the block chain node, and the correctness of the travel service information may be ensured by verifying the travel service information by the block chain node; and then, the block link point informs other block link points to record the travel service information, so that the same and credible travel service information can be stored in each block link point in the block chain system. Since the travel service information stored in the blockchain system is public and tamper-proof for both the enterprise side and the TMC side, this approach enhances the credibility of the travel service information.

In another embodiment of the invention, a computer program product is provided, the method of any of the method embodiments shown in fig. 5-8 being implemented when the computer program product is run on a computer.

In another embodiment of the invention, a computer-readable storage medium is provided, which stores a computer program that, when executed by a computer, implements the method of any of the method embodiments shown in fig. 5-8.

While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for providing travel services, applied to a blockchain system, the blockchain system comprising at least two blockchain nodes, the method comprising:

the first block link point receives travel service information, wherein the travel service information comprises information generated by calling an intelligent contract by an enterprise client and/or information generated by calling the intelligent contract by a TMC client of a travel service company; the business trip service information is generated by calling a predetermined message sent to a second block link node by the TMC client according to an intelligent contract, wherein the predetermined message is sent to the second block link node by the TMC client after determining that a target user has a predetermined authority to the second block link node; the predetermined information is not generated when the TMC client determines that the target user does not have the predetermined authority to the second block link point; or the travel service information is generated by calling the intelligent contract by the TMC client to send the fund return confirmation information to the second block link node; the money return confirmation message is generated after the TMC client receives a successful money return event notification sent by the second blockchain node, and the successful money return event notification is generated after the second blockchain node verifies that the first money information and the second money information are successful; the first money information is generated after the first server receives a payment response of the second server, and the second money information is generated after the second server successfully collects money; or the money return confirmation message is generated after the TMC client receives a verification message that money collection is successful and sent by a second server, the first server is a server of a first bank where an enterprise user processes fund service, the second server is a server of a second bank where the TMC processes fund service, and the second block link node is any one of the first block link node or other block link nodes;

the money return confirmation information is generated in response to a money return request event detected by the enterprise client, and the money return request event detected by the enterprise client includes: the enterprise client receives a second event notification sent by the second block link node, wherein the second event notification is generated after the second block link node calls an intelligent contract to monitor that a target user needs to make a fund back; the enterprise client calls the intelligent contract to monitor one or more of the target users needing to make a refund; the first block link point generates a travel block according to the travel service information and initiates verification processing on the travel block;

if the travel block is successfully verified, the first block link point records the travel block into a travel block chain;

and the first block link point informs the other block link points to record the travel block into a travel block chain.

2. The method of claim 1, wherein the verification process comprises: and the block chain node checks the travel block and/or sends the travel block to other block chain nodes except the block chain node in a block chain system for checking.

3. The method of claim 1 or 2, wherein the initiating the verification process for the travel block comprises:

the first blockchain node broadcasts the travel block to the other blockchain devices;

the first block chain link point receives verification success information sent by other block chain nodes;

and if the number of the received verification success information is larger than the number threshold, the block link point determines that the verification of the travel block is successful.

4. The method of claim 1, wherein whether or not to have a predetermined privilege is determined by the second block link point based on a user identification of a target user and/or a predetermined digital asset.

5. The method of claim 1, wherein the verification message that the collection is successful is generated after the second server receives the verification request sent by the TMC client and verifies that the collection is successful; the verification request is generated after the TMC client receives a refund event notification sent to the TMC client by the second block link point calling intelligent contract.

6. The method of claim 5, wherein the refund event notification is generated by the enterprise client upon receiving a payment completion notification sent by the first server, wherein the payment completion notification is generated by the first server upon receiving a payment response sent by the second server.

7. A method of providing travel services, comprising:

the TMC client receives a first verification request of a TMC subscription system, wherein the first verification request is used for indicating whether a verification target user has a predetermined right or not;

the TMC client calls an intelligent contract to send a second verification request to the block chain node;

the TMC client receives a verification result sent by the block chain node;

if the verification result shows that the target user has the preset authority, the TMC client sends a preset response message to the TMC booking system, wherein the preset response message is used for indicating the TMC booking system to execute the reservation;

and if the verification result shows that the target user does not have the preset authority, the TMC client sends a response message which does not allow the preset to a TMC booking system.

8. The method of claim 7, further comprising:

the TMC client receives preset information, wherein the preset information is generated after the TMC reservation system executes reservation according to the preset response message;

and the TMC client calls an intelligent contract to send the reservation information to the block chain nodes, and the reservation information is used for storing the block chain nodes in the travel block chain.

9. A method of providing travel services, comprising:

when detecting a money return request event, the enterprise client generates a money return request; wherein the enterprise client detects a refund request event, including: the enterprise client receives a second event notification sent by the blockchain node, wherein the second event notification is generated after the blockchain node calls an intelligent contract to monitor that a target user needs to make a refund; the enterprise client calls the intelligent contract to monitor one or more of the target users needing to make a refund;

the enterprise client calls the intelligent contract to send the refund request to the block chain node, wherein the refund request is used for indicating the block chain node to generate a first event notice, and the first event notice is used for indicating the first server to transfer the digital assets to the second server.

10. The method of claim 9, wherein the enterprise client detects a chargeback request event, further comprising:

and the enterprise client receives a money return triggering operation.

11. The method according to claim 9 or 10, characterized in that the method further comprises:

the enterprise client receives an event notice of successful money return sent by the block chain node;

the enterprise client issues a notification indicating that the target user has completed the transfer of the digital asset.

12. A first blockchain node in a blockchain system, the blockchain system including at least two blockchain nodes, the first blockchain node including a receiving unit, a checking unit, a recording unit, and a notification unit, wherein:

the receiving unit is used for receiving travel service information, and the travel service information comprises information generated by calling an intelligent contract by an enterprise client and/or information generated by calling the intelligent contract by a TMC client of a travel service company;

the business trip service information is generated by calling a predetermined message sent to a second block link node by the TMC client according to an intelligent contract, wherein the predetermined message is sent to the second block link node by the TMC client after determining that a target user has a predetermined authority to the second block link node; the predetermined information is not generated when the TMC client determines that the target user does not have the predetermined authority to the second block link point;

or the travel service information is generated by calling the intelligent contract by the TMC client to send the fund return confirmation information to the second block link node; the money return confirmation message is generated after the TMC client receives a successful money return event notification sent by the second blockchain node, and the successful money return event notification is generated after the second blockchain node verifies that the first money information and the second money information are successful; the first money information is generated after the first server receives a payment response of the second server, and the second money information is generated after the second server successfully collects money; or the money return confirmation message is generated after the TMC client receives a verification message that money collection is successful and sent by a second server, the first server is a server of a first bank where an enterprise user processes fund service, the second server is a server of a second bank where the TMC processes fund service, and the second block link node is any one of the first block link node or other block link nodes;

the money return confirmation information is generated in response to a money return request event detected by the enterprise client, and the money return request event detected by the enterprise client includes: the enterprise client receives a second event notification sent by the block chain node, wherein the second event notification is generated after the block chain node calls an intelligent contract to monitor that a target user needs to pay back; the enterprise client calls the intelligent contract to monitor one or more of the target users needing to make a refund;

the checking unit is used for generating a travel block according to the travel service information and initiating checking processing on the travel block;

the recording unit is used for recording the travel block into a travel block chain when the travel block is successfully verified;

and the notification unit is used for notifying the other block link points to record the travel block into the travel block chain.

13. The first blockchain node of claim 12, wherein the check unit is specifically configured to: and checking the travel block and/or sending the travel block to other block chain nodes except the block chain node in a block chain system for checking.

14. The first blockchain node according to claim 12 or 13, wherein the checking unit is specifically configured to:

broadcasting the travel blocks to the other blockchain devices;

receiving successful verification information sent by the other block chain nodes;

and if the number of the received verification success information is larger than the number threshold, determining that the verification of the travel block is successful.

15. The first blockchain node of claim 12, wherein whether the second blockchain node has a predetermined right is determined based on a user identification of a target user and/or a predetermined digital asset.

16. The first blockchain node according to claim 12, wherein the verification message that the collection is successful is generated after the second server receives the verification request sent by the TMC client and verifies that the collection is successful; the verification request is generated after the TMC client receives a refund event notification sent to the TMC client by the second block link point calling intelligent contract.

17. The first blockchain node of claim 16, wherein the refund event notification is generated by the enterprise client upon receiving a payment completion notification from the first server, the payment completion notification being generated by the first server upon receiving a payment response from the second server.

18. A TMC client is characterized by comprising a first receiving unit, a second receiving unit, a first sending unit and a second sending unit, wherein:

the first receiving unit is used for receiving a first verification request of the TMC reservation system, wherein the first verification request is used for indicating whether a verification target user has a preset authority or not;

the first sending unit is used for calling the intelligent contract to send a second verification request to the block chain link point;

the second receiving unit is configured to receive a verification result sent by the blockchain node;

the second sending unit is used for sending a predetermined response message to the TMC reservation system when the verification result shows that the target user has the predetermined right, wherein the predetermined response message is used for instructing the TMC reservation system to execute reservation;

the second sending unit is further configured to send a response message that reservation is not allowed to the TMC reservation system when the verification result indicates that the target user does not have the predetermined right.

19. The TMC client according to claim 18, characterized in that the TMC client further comprises a third receiving unit and a third sending unit, wherein:

the third receiving unit is configured to receive predetermined information, where the predetermined information is generated after the TMC reservation system performs reservation according to the predetermined response message;

the third sending unit is configured to invoke an intelligent contract to send the reservation information to a block link node, where the reservation information is used for the block link node to be stored in a travel block chain.

20. An enterprise client, comprising a generating unit, a detecting unit and a sending unit, wherein:

the generating unit is used for generating a money return request when a money return request event is detected;

the detection unit is used for receiving a second event notification sent by a block chain node, wherein the second event notification is generated after the block chain node calls an intelligent contract to monitor that a target user needs to pay back; calling an intelligent contract to monitor whether one or more of the target users need to make a refund;

the sending unit is used for calling the intelligent contract to send the refund request to the block chain node, the refund request is used for indicating the block chain node to generate a first event notification, and the first event notification is used for indicating the first server to transfer the digital assets to the second server.

21. The enterprise client of claim 20, wherein the detection unit is further configured to:

and receiving a money return triggering operation.

22. The enterprise client according to claim 20 or 21, further comprising a receiving unit and a publishing unit, wherein:

the receiving unit is configured to receive an event notification that the money return is successful, where the event notification is sent by the blockchain node;

the publishing unit is configured to publish a notification indicating that the target user has completed the transfer of the digital asset.

23. A block link point comprising a processor and a memory, wherein the memory is configured to store program instructions and the processor is configured to perform the method of any one of claims 1-6 according to the program instructions.

24. A TMC client comprising a processor and a memory, wherein the memory is configured to store program instructions and the processor is configured to perform the method according to the program instructions as claimed in claim 7 or 8.

25. An enterprise client comprising a processor and a memory, wherein the memory is configured to store program instructions and the processor is configured to perform the method of any of claims 9-11 according to the program instructions.

26. A computer-readable storage medium, characterized in that the computer storage medium stores program instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1-11.

27. A computer program product, characterized in that it implements the method of any of claims 1-11 when run on a processor.