JP5249962B2 - Transaction management server, system and method for integrating a plurality of transactions - Google Patents

Description

  The present invention relates to a transaction management server, system, and method for integrating a plurality of transactions.

  2. Description of the Related Art Conventionally, a technique related to online shopping is known in which shopping is performed using a terminal device that can be connected to a web server via a communication network (Patent Document 1). In this technology, not only shopping at a single online shopping store, but also a plurality of mall servers can be used to issue purchase instructions for multiple shopping across different stores or product fields. Yes. Users can shop with less effort by using such online shopping technology.

JP-A-11-219389

  Here, for example, when shopping is performed across a plurality of product fields, or when a plurality of processes are involved, the web server that has received one http request performs a plurality of transaction processes different for each product field. There is a case. In such a situation, the web server cannot immediately return a response to the terminal even if there is a transaction that has been completed early among the plurality of transactions due to the characteristics of the http protocol such as an http request and a response to the request. It is necessary to respond to the terminal after waiting for completion of the last transaction completed. In this way, the slowest transaction that completes processing becomes the bottleneck of the entire system, and in some cases, the session between the web server and the terminal times out or the user cannot wait for the web server and the terminal to There was also the possibility of disconnecting communication.

  It is an object of the present invention to provide a transaction management server, system, and method for managing a plurality of transactions in an integrated manner.

  In the present invention, the following solution is provided.

  (1) A transaction management server that is communicably connected to a terminal and a web server, the information identifying the terminal that has transmitted one http request accompanied by a plurality of transaction requests from the web server to the web server. And a means for receiving information identifying the one http request, and waiting for completion of the plurality of transactions continuously on behalf of the web server based on the received information identifying the one http request. Means for storing each status information; and means for transmitting link information for inquiring status information of each of the plurality of transactions to the terminal based on the received information for identifying the terminal. Provided transaction management server.

  The transaction management server that integrates and manages the status information according to the present invention waits for the completion of a plurality of transactions on behalf of the web server, and transmits link information for inquiring the status information of the transactions to the terminal. Therefore, the user of the terminal can quickly receive notification of the link information without waiting for completion of the transaction. Furthermore, the web server does not need to wait for completion of the plurality of transactions, and can receive an http request accompanied by a request for a new transaction.

  Therefore, when shopping is performed across a plurality of product fields at the user's terminal, even when the web server that has received the request performs a plurality of transaction processes different for each product field, the transaction management server Without waiting for the completion of the plurality of transactions, it is possible to respond to the terminal on behalf of the web server. As a result, it is possible to suppress the possibility that the session between the web server and the terminal will time out, or that the user cannot wait and disconnect the communication between the web server and the terminal.

  (2) A system including a transaction management server that is communicably connected to a terminal and a web server, wherein the web server receives a single http request with a plurality of transaction requests from the terminal. Means for transmitting information identifying the terminal and information identifying the one http request to the transaction management server, wherein the transaction management server receives the information identifying the terminal and the one of the one from the web server. Based on the means for receiving the information identifying the http request and the received information identifying the one http request, the status information of each status is continuously waited for the completion of the plurality of transactions on behalf of the web server. And means for storing the received terminal Based on that information, the system comprising relative to said terminal, and means for transmitting link information for inquiring the status information of each of the plurality of transactions.

  By doing in this way, the system which can have the same effect as (1) can be provided.

  (3) The web server further includes means for transmitting information indicating an acceptance notification to the terminal when transmitting information identifying the one http request to the transaction management server. system

  By doing so, the web server included in the system according to the present invention has received the transaction earlier than the transaction management server transmits link information for inquiring status information of a plurality of transactions. Notifications can be sent to the user's terminal. Therefore, the user can further receive a notification that the transaction has been accepted prior to receiving the notification of the link information.

  (4) A method of managing a transaction by a transaction management server communicably connected to a terminal and a web server, wherein the transaction management server sends one http request accompanied by a plurality of transaction requests from the web server. Receiving the information identifying the terminal and the information identifying the one http request transmitted to the web server, and continuing on behalf of the web server based on the received information identifying the one http request And waiting for completion of the plurality of transactions, storing each status information, and receiving the status information of each of the plurality of transactions for the terminal based on the received information for identifying the terminal. Send link information for inquiry Method for managing transactions for executing the steps that, the.

  By doing in this way, the transaction management server which can have the same effect as (1) can provide the method of managing a transaction. The steps of the method according to the present invention may be provided as a program for performing the method using a computer system. The program may be provided by being stored in an appropriate storage medium, or may be provided in the form of a custom LSI (Large Scale Integrated circuit) including a data input / output, a data bus, a memory bus, a system bus, and the like.

  ADVANTAGE OF THE INVENTION According to this invention, it can provide the transaction management server which transmits the link information for inquiring the status information of a transaction to a terminal instead of a web server. Therefore, the user of the terminal can quickly receive notification of the link information without waiting for completion of transaction processing. Furthermore, the web server does not need to wait for the completion of processing of the transaction, and can receive an http request accompanied by a request for a new transaction.

It is a figure which illustrates the whole structure containing the transaction management server 100 based on this embodiment. It is a figure which illustrates the data structure of transaction management DB180 based on this embodiment. It is a flowchart which illustrates the step of operation | movement of the web server 20 based on this embodiment. It is a flowchart which illustrates the various steps of operation | movement of the transaction management server 100 based on this embodiment. It is a figure which illustrates the operation | movement sequence of the system which manages a transaction based on this embodiment. It is a figure which shows the example response message based on this embodiment. It is a figure which illustrates the whole structure containing the transaction management server 100 based on another embodiment of this invention. FIG. 6 is a flow diagram illustrating stages of operation of a backend server 30 according to another embodiment of the invention. It is a figure which illustrates the operation | movement sequence of the system which manages the transaction based on another embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described. This is merely an example, and the technical scope of the present invention is not limited to this.

  This embodiment is applied to a computer and its peripheral devices. Each unit in the present embodiment is configured by hardware included in a computer and its peripheral devices, and software that controls the hardware.

  The hardware includes a storage unit, a communication device, a display device, and an input device in addition to a CPU (Central Processing Unit) as a control unit. Examples of the storage unit include a memory (RAM: Random Access Memory, ROM: Read Only Memory, etc.), a hard disk drive (HDD: Hard Disk Drive), and an optical disk (CD: Compact Disc, DVD: Digital Versatile Drive, etc.). Can be mentioned. Examples of the communication device include various wired and wireless interface devices. Examples of the display device include various displays such as a liquid crystal display and a plasma display. Examples of the input device include a keyboard and a pointing device (mouse, tracking ball, etc.).

  The software includes a computer program and data for controlling the hardware. The computer program and data are stored in the storage unit, and are appropriately executed and referenced by the control unit. The computer program and data can be distributed via a communication line, or can be recorded on a computer-readable medium such as a CD-ROM and distributed.

[overall structure]
FIG. 1 is a diagram illustrating an overall configuration including a transaction management server 100 according to the present embodiment. In the example of the overall configuration illustrated in FIG. 1, the transaction management server 100 is communicably connected to the user terminal 10 and the web server 20. The communication is usually performed through wide-area communication such as the Internet, but is not limited. Note that there may be a plurality of transaction management servers 100. In this case, when a transaction is transferred from the Web server 20, a transaction management server that accepts the transfer may be distributed according to an ID or the like. .

  The user terminal 10 is a terminal used for transmitting a processing request 210 that is an http request for online shopping or the like to the web server 20. The user terminal 10 may be a personal computer or a mobile phone connected to a network.

  The web server 20 receives and accepts the processing request 210 transmitted from the user terminal 10, and transmits the acceptance request 220 to the user terminal 10 that accepts the processing request 210. An acceptance notification transmission unit 120 as a unit for transmitting information indicating a notification, and a transaction transfer unit 130 that transfers the processing request 210 to the transaction management server 100 according to the present embodiment as a transfer notification 230 are provided.

In the prior art, the web server 20 waits for completion of a plurality of processes necessary for the process request 210, waits for the completion of all processes, and returns it to the user terminal 10 as a web page response. Furthermore, it requests a plurality of processes to a server device such as a back-end server (not shown, hereinafter simply referred to as a back-end server) that processes the transactions, and waits for responses such as processing completion notifications for the plurality of transactions. It can be configured to be possible.
However, in this embodiment, the web server 20 uses the transaction transfer unit 130 to transfer the information of the processing request 210 to the transaction management server 100 in response to receiving the processing request 210. Thereafter, the transaction management server 100 waits for responses such as processing completion notifications for a plurality of transactions in place of the web server 20. Therefore, in the present embodiment, the web server 20 does not have to wait for a response such as a processing completion notification for a plurality of transactions.
In the present embodiment, the actual transaction processing may be performed by the transaction management server 100. As will be described later, a plurality of back-end servers 30 (FIG. 7) are connected to the transaction management server 100, and the back-end server 30 (FIG. 7) may do.

  The web server 20 transmits an acceptance notification 220 to the user terminal 10 that the processing request 210 has been accepted. As a result, a user or the like who operates the user terminal 10 can know that an http request such as an order for a product has been accepted by the web server 20. In the present embodiment, the case where the reception notification 220 is returned before the actual transaction processing is completed has been described. However, the present invention is not limited to this, and “complete” corresponding to the reception notification 220 after the actual processing is completed. "Return" may be performed.

  Next, the web server 20 transmits a transfer notification 230 to the transaction management server 100. The transfer notification 230 includes information for identifying a transaction based on the processing request 210 and information for identifying the user terminal 10 that has transmitted the processing request 210.

  The transaction management server 100 shown in FIG. 1 includes a transaction transfer acceptance unit 150, a link information notification unit 160, a transaction management unit 170, and a transaction management DB 180.

  The transaction transfer receiving unit 150 is a unit that receives the transfer notification 230 transmitted by the transaction transfer unit 130 of the web server 20. Therefore, the transaction management server 100 can receive information for identifying a transaction based on the processing request 210 that is an http request and information for identifying the user terminal 10 that has transmitted the processing request 210 that is an http request.

  The link information notification unit 160 is a unit that transmits link information for inquiring transaction status information to the user terminal 10. That is, the link information notification unit 160 notifies the user terminal 10 of the link information 240 in response to the transaction transfer reception unit 150 receiving the transfer notification 230. The link information 240 includes information for the user terminal 10 that has transmitted the processing request 210 to track a status 184 (described later in FIG. 2) regarding the transaction processing status and the like. Examples of such information include, but are not limited to, an e-mail address or a URL of a site that accepts an inquiry (Uniform Resource Locator) that can inquire about the processing status of a transaction. It may be the telephone number of the inquiry, the postal address or the name of the department in charge. A specific aspect of the link information 240 will be described as a response message 282 (FIG. 6).

  Based on the transfer notification 230, the transaction management unit 170 waits for completion of a plurality of transactions, and stores the status 184 (FIG. 2) for each of the plurality of transactions in the transaction management DB 180.

  Furthermore, the transaction management means 170 transmits information on the processing status of a plurality of transactions to the user terminal 10 as a status notification 280 (FIG. 5). The transaction management unit 170 may transmit the status notification 280 to the user terminal 10 in response to receiving the inquiry 250 that the user terminal 10 arbitrarily transmits. A specific mode of the status notification 280 will be described as a response message 292 (FIG. 5).

  The transaction management DB 180 is means for storing statuses 184 (FIG. 2) relating to a plurality of transactions. That is, the transaction management DB 180 is used by the transaction management means 170 to store information on the processing status including the status 184.

  In this way, the transaction management server 100 according to the present embodiment waits for completion of each of the plurality of transactions based on the processing request 210 that is an http request in response to the transfer notification 230 from the web server 20. A response to the inquiry from the terminal 10 can be transmitted.

[Data structure of transaction management DB 180]
FIG. 2 is a diagram illustrating a data structure of the transaction management DB 180 according to the present embodiment. The data structure of the transaction management DB 180 shown in FIG. 2 includes a request destination server ID 182, a status notification method 183, a status 184, and a notification confirmation 185 in association with the transaction ID 181.

  The transaction ID 181 is an identifier used to identify the transfer notification 230 shown in FIG. 1 as one transaction. Therefore, the information identified by the transaction ID 181 is associated with one transfer notification 230.

  The requested server ID 182 includes server device identification information necessary for processing the transaction corresponding to the transfer notification 230. Specifically, this server device is the transaction management server 100 or the back-end server 30 (FIG. 7) according to the present embodiment. By specifying the server device using the request destination server ID 182, each server device that actually processes the transaction corresponding to the transfer notification 230 is associated with the transaction ID 181.

  The status notification method 183 is information on a progress status notification means for the user who has transmitted the processing request 210. The status notification method 183 can be selected from an appropriate means capable of receiving information using the user terminal 10 such as an email or a web page, but is not limited thereto. Normally, the status notification method 183 may be specified by the user when the processing request 210 is transmitted.

  The status 184 is information representing the progress of transaction processing based on the transfer notification 230. FIG. 2 stores that the status 184 is “completed” for the transaction whose transaction ID 181 is “122” and the status 184 is “waiting” for the transaction whose transaction ID 181 is “123”. . Here, “waiting” includes an incomplete meaning for this transaction. The form of the status 184 is not limited to these, and may include a progress status for each of a plurality of transactions included in one transfer notification 230.

  The notification confirmation 185 is information for confirming notification to the user terminal 10 for the transaction identified by the transaction ID 181. Specifically, information such as “OK” may be stored in the notification confirmation 185 when the link information 240 illustrated in FIG. 1 is transmitted from the transaction management server 100 to the user terminal 10. In addition, the notification confirmation 185 may include information transmitted from the transaction management server 100 to the user terminal 10 by the status notification 280. The notification confirmation 185 can individually store information that an arbitrary form of information is transmitted from the transaction management server 100 to the user terminal 10 in association with the transaction ID 181.

  By doing in this way, the transaction management server 100 according to the present embodiment, for each transaction identified by the transaction ID 181, information related to the server device that performs processing of the transaction, a status notification method to the user terminal 10, The status 184 indicating the progress of the transaction and the notification confirmation 185 can be stored in the transaction management DB 180 in association with the transaction ID 181.

[Operation of Web Server 20]
FIG. 3 is a flowchart illustrating the steps of the operation of the web server 20 according to the present embodiment.

  In step S110, the web server 20 receives and accepts the processing request 210 transmitted from the user terminal 10.

  In step S120, the web server 20 transmits the acceptance notification 220 to the user terminal that the processing request 210 has been accepted. Note that the order of processing of the reception notification 220 is not limited to this, and may be performed after transaction transfer reception and link information notification by the transaction management server 100 described later. Further, the screen of this reception notification 220 may also serve as a screen for notification of link information.

  In step S130, the web server 20 performs transaction transfer. Specifically, using the transaction transfer unit 130 shown in FIG. 1, information for identifying a transaction based on the processing request 210 and information for identifying the user terminal 10 that has transmitted the processing request 210 are used as a transfer notification 230. It transmits to the management server 100.

  After step S130, the web server 20 ends the operation for one processing request 210. The web server 20 may optionally return to step S110 and wait for the next processing request 210. Therefore, in the transaction management method according to the present embodiment, the web server 20 does not have to wait for the completion of the transaction.

[Operation of Transaction Management Server 100]
FIG. 4 is a flowchart illustrating the steps of the operation of the transaction management server 100 according to this embodiment. FIG. 4A is a flowchart illustrating the whole of this operation, and FIG. 4B is a flowchart illustrating the steps of the operation in the transaction management unit 170.

  In step S210, the transaction management server 100 receives and accepts the transfer notification 230 transmitted by the web server 20 in step S130. The following steps in the transaction management server 100 are sequentially executed in response to receiving the transfer notification 230.

  In step S220, the transaction management server 100 performs link information notification. Specifically, the transaction management server 100 transmits to the user terminal 10 link information 240 for inquiring transaction status information, using the link information notification unit 160 shown in FIG. For example, the link information 240 may include information on a schedule that the transaction can be predicted to complete based on the time when the transaction management server 100 receives the transfer notification 230 and the period until the normal product shipment. Not. The link information notification process is not limited to this, and may be performed by the Web server 20 that has received the notification from the transaction management server 100. Moreover, you may comprise so that link information may be mailed from the back end server 30 (process) demonstrated by the below-mentioned embodiment. Further, such link information may be configured so that it can be confirmed from the screen of details.

In step S230, the transaction management server 100 executes transaction management processing using the transaction management means 170. Specifically, step S230 includes the following steps shown in FIG.
Step S232: The transaction management server 100 generates a transaction processing request corresponding to the transfer notification 230. The generated request is transmitted to the server device that processes the transaction. The server device may be the transaction management server 100 or the back-end server 30 (FIG. 7) connected to the transaction management server 100.
The flow diagram of FIG. 4 shows a case where the transaction management server 100 processes the transaction. The transaction processing request is transmitted to the subsequent step S233 using, for example, a known technique such as interprocess communication.
Step S233: The transaction management server 100 receives a notification of completion of the transaction processing. Specifically, in response to receiving a transaction processing request, the transaction management server 100 activates a predetermined program or the like that can perform the transaction processing, and sets the status 184 of the transaction management DB 180 to “waiting”. Set and wait for and accept a transaction processing completion notification from that process.
Step S234: When the transaction corresponding to the request in step S232 is completed, the transaction management server 100 sets the status 184 of the transaction management DB 180 to “completed” accordingly. The transaction management server 100 continues to wait until a completion notification is received for all the transaction processing requests corresponding to the request in step S232. Even while the standby is continued, the transaction management server 100 can execute the processes in the subsequent steps S235 and S236.
Step S235: The transaction management server 100 receives and accepts an inquiry 250 (FIG. 5) arbitrarily transmitted by the user terminal 10.
Step S236: The transaction management server 100 refers to the transaction management DB 180, acquires the status 184 of the transaction ID 181 and transmits a status notification 280 including the contents to the user terminal 10. The transaction management server 100 can transmit the latest status 184 in response to the inquiry 250 of the status 184 from the user terminal 10 by repeatedly executing steps S235 and S236.

  As an example of the transaction management operation in step S230, for example, the user terminal 10 transmits a transaction progress inquiry 250, for example, if the status notification method 183 is an email, an email is sent. If it is a Web page, the URL is transmitted. In response to receiving the inquiry 250, the transaction management server 100 generates information related to the progress of the transaction based on the status 184, and transmits the generated information to the user terminal 10.

  As another example of the transaction management operation in step S230, when a specific transaction is completed, the transaction management server 100 sends information indicating that the processing of the specific transaction is completed to the user terminal 10 by mail. Also good.

[Operation sequence of the system that manages transactions]
FIG. 5 is a diagram illustrating an operation sequence of a system for managing transactions according to the present embodiment. This operation sequence shows the mutual relationship between the stages of the operations of the web server 20 and the transaction management server 100 shown in FIGS. 3 and 4, and the same reference numerals correspond to the same steps.

  First, the user terminal 10 transmits a processing request 210 to the web server 20. The web server 20 sequentially performs the operations from step S110 to step S130 described above, transmits an acceptance notification 220 to the user terminal, and transmits a transfer notification 230 to the transaction management server 100. As a result, a user or the like who operates the user terminal 10 can know that an http request such as an order for a product has been accepted by the web server 20.

Next, in response to receiving the transfer notification 230 from the web server 20 in step S210, the transaction management server 100 transmits the link information 240 to the user terminal 10 in the subsequent step S220. As a result, a user or the like who operates the user terminal 10 can know information such as an inquiry about the processing status of the ordered product.
Furthermore, the transaction management server 100 executes a transaction management process in step S230. Specifically, step S230 is various stages of the operation of the transaction management unit 170 shown in FIG. 1, and includes steps S232 to S236.

Step S232: The transaction management server 100 generates a request for processing a plurality of transactions corresponding to the transfer notification 230. The generated request is transmitted to the server device that processes the transaction. The server device may be the transaction management server 100 or the back-end server 30 (FIG. 7) connected to the transaction management server 100.
FIG. 5 shows a case where the transaction management server 100 processes the transaction. In the present embodiment, a transaction processing request is transmitted to a plurality of processes that actually perform transaction processing. A known technique such as interprocess communication can be used for this transmission. The case of using the back-end server 30 (FIG. 7) will be described later with reference to FIG.
Step S233: The transaction management server 100 receives a notification of completion of the transaction processing. Specifically, in response to a transaction processing request, the transaction management server 100 starts a predetermined program or the like that can perform the transaction processing, and sets the status 184 of the transaction management DB 180 to “waiting”. Thus, the transaction processing completion notification from the process is waited and accepted.
Step S234: When all of the transactions corresponding to the processing requests for the plurality of transactions are completed, the transaction management server 100 sets the status 184 of the transaction management DB 180 to “completed” accordingly. The transaction management server 100 continues to wait until a completion notification is received for all the transaction processing requests corresponding to the transaction processing request in step S232. Even while the standby is continued, the transaction management server 100 can execute the processes in the subsequent steps S235 and S236.
Step S235: The transaction management server 100 receives and accepts an inquiry 250 arbitrarily transmitted by the user terminal 10.
In step S 236, the transaction management server 100 refers to the transaction management DB 180, acquires the status 184 of the transaction ID 181, and transmits a status notification 280 including the contents to the user terminal 10. The transaction management server 100 can transmit the latest status 184 in response to the inquiry 250 of the status 184 from the user terminal 10 by repeatedly executing steps S235 and S236.

The status notification 280 transmitted from the transaction management server 100 to the user terminal 10 in step S236 can include at least one of the following information, and each information can include the status 184.
(Information included in the status notification 280-1) Information on the progress of processing of the transaction corresponding to the inquiry 250 at the time when the transaction management server 100 receives and accepts the inquiry 250 arbitrarily transmitted by the user terminal 10.
(Information-2 included in status notification 280) Information indicating completion of a transaction based on completion of any or all transactions.

[Example response message]
FIG. 6 is a diagram illustrating an exemplary response message according to the present embodiment. FIG. 6A is a diagram illustrating a response message 282 as link information 240 transmitted from the transaction management server 100 to the user terminal 10. FIG. 6B is a diagram illustrating a response message 292 as a status notification 280 transmitted from the transaction management server 100 to the user terminal 10.

  The response message 282 shown in FIG. 6A is generated by the link information notification unit 160 and transmitted to the user terminal 10 as link information 240. As an example, the response message 282 includes shipping information 284 and status confirmation link information 286. The information included in the response message 282 and the order of the information are not limited to these, and can be arbitrarily set.

  The shipping information 284 can include, for example, scheduled shipping schedule information based on a predetermined product shipping period or the like.

  The status confirmation link information 286 can include information on the inquiry destination of the progress of the transaction corresponding to the processing request 210. The status confirmation link information 286 is, for example, an inquiry e-mail address or a URL of a site that accepts an inquiry, but is not limited thereto.

  As a result, a user or the like who operates the user terminal 10 can quickly obtain a transaction processing schedule corresponding to the processing request 210 and information on an inquiry destination after the processing request 210 is transmitted.

  The response message 292 shown in FIG. 6B is generated by the transaction management unit 170 and transmitted to the user terminal 10 as the status notification 280. As described above, the status notification 280 is transmitted from the transaction management server 100 to the user terminal 10 in response to the inquiry 250 from the user terminal or in response to completion of a plurality of transactions. FIG. 6B shows an example of the status notification 280 in response to the inquiry 250 arbitrarily transmitted from the user terminal 10.

  As an example, the response message 292 includes progress information 294 and 296. FIG. 6B shows that information indicating the progress of the transaction is separately included for each of two different types of products. The number or format of these pieces of information is shown in this example. It is not limited and can be designed appropriately.

  In the example shown in FIG. 6B, the progress status information 294 includes information that “a stock is available, so that shipment can be arranged immediately” for a certain product (item A). Further, the progress status information 296 includes information on the arrival schedule of another product (item B). That is, the progress status information 294 includes information regarding the progress status of the transaction processing corresponding to the query 250 at the time when the transaction management server 100 receives and accepts the query 250 arbitrarily transmitted by the user terminal 10. Can do. The progress status may be appropriately expressed according to the status 184 shown in FIG.

  Although FIG. 6B shows the status notification 280 corresponding to the inquiry 250, the progress status information 294 can also be generated based on the completion of a plurality of transactions. In this case, the progress status information 294 and 296 can include information indicating that each product can be shipped.

  By doing in this way, in the system including the transaction management server 100 that integrates a plurality of transactions according to the present embodiment, the user can quickly obtain the information of the inquiry destination regarding the progress of the processing such as net shopping ordered by the user. In response to an arbitrary inquiry to the inquiry destination, it is possible to receive a response including information on the progress of processing such as online shopping. In this embodiment, the example of merchandise sales is shown. However, the present invention is not limited to this, and various embodiments such as application for digital contents are possible.

[Another embodiment of overall configuration]
FIG. 7 is a diagram illustrating an overall configuration including the transaction management server 100 according to another embodiment of the present invention. A description of portions common to FIG. 1 is omitted.

  In the example illustrated in FIG. 7, the transaction management server 100 is communicably connected to the user terminal 10, the web server 20, and the back-end server 30.

  In response to receiving the processing request 210, the web server 20 transmits a transfer notification 230 to the transaction management server 100 using the transaction transfer unit 130. In the example shown in FIG. 7, the transfer notification 230 may also include information for identifying the back-end server 30 for processing a transaction (hereinafter simply referred to as the back-end server 30). Thereafter, the response from the back-end server 30 is received by the transaction management server 100. Therefore, the web server 20 does not have to wait for a response from the back-end server 30.

  The back-end server 30 processes transactions such as online shopping one by one in accordance with individual processing requests 260 (FIG. 9) described later. The back-end server 30 may include a plurality of server devices in order to handle information on products in different fields or information on individual shopping sites. For example, FIG. 7 shows an example in which three server devices such as the back-end server A 310, the back-end server B 320, and the back-end server C 330 are included in the back-end server 30, but the present invention is not limited to this. Any number is acceptable. Further, the geographical location where each server device included in the back-end server 30 is installed may be anywhere, and a part of the server device may be installed remotely from the others.

  Normally, a specific server device (hereinafter referred to as a specific server device) included in the back-end server 30 that can process the individual processing request 260 is used. The specific server device is selected from the back-end server 30 based on, for example, the type of product included in the transaction. The specific server device may be a part of the back-end server 30 or the entire back-end server 30.

  In the example shown in FIG. 7, the transaction management means 170 of the transaction management server 100 sends an individual processing request 260 (FIG. 9), which is a request for processing the transaction, to the back-end server 30 based on the transfer notification 230. Send. In addition, the transaction management unit 170 receives processing status information including the status 184 regarding the transaction in the back-end server 30. This processing status information is received as a completion notification 270 (FIG. 9) from the related back-end server 30. FIG. 7 shows, as an example, that the individual processing request 260 and the completion notification 270 are transmitted and received between the transaction management unit 170 and the back-end server A 310. However, the individual processing request 260 and the completion notification 270 are shown in FIG. Can be transmitted to and received from other back-end servers 30 in the same manner.

  In the example shown in FIG. 7, the transaction management DB 180 is means for continuously receiving and storing a response from the related back-end server 30 in place of the web server 20.

  By doing so, the transaction management server 100 according to the present embodiment acquires the processing status in the back-end server 30 on behalf of the web server 20 in response to the transfer notification 230, and responds to the inquiry from the user terminal 10. Can be sent.

[Operation of back-end server 30]
FIG. 8 is a flow diagram illustrating the stages of operation of the backend server 30 according to another embodiment of the invention.

  In step S <b> 310, the back-end server 30 executes the transaction reception process by receiving and receiving the individual process request 260. The individual processing request 260 is a request for processing a specific transaction included in the processing request 210. The individual processing request 260 is accepted by a specific server device included in the back-end server 30 that can process the specific transaction.

  In step S320, the back-end server 30 executes transaction processing. For example, an instruction for purchasing a product such as online shopping transmitted as the processing request 210 using the user terminal 10 is processed. If the transaction processing requires processing in a plurality of server devices included in the back-end server 30, the transaction processing in step S320 may be completed at different times for each server device.

  In step S330, the back-end server 30 executes a completion process. Specifically, the back-end server 30 transmits a completion notification 270 including transaction completion information for each server device to the transaction management unit 170 of the transaction management server 100.

  When the back-end server 30 performs processing as described above, the transaction management unit 170 of the transaction management server 100 performs the following processing. Specifically, in the processing of the transaction management server 100 shown in FIG. 4B, the processing from step S232 to step S234 can be changed.

Step S232: The transaction management server 100 transmits an individual processing request 260, which is a request for processing a transaction corresponding to the transfer notification 230, to the back-end server 30.
Step S233: The transaction management server 100 further sets the status 184 of the transaction management DB 180 to “waiting” and waits for the completion notification 270 from the back-end server 30.
Step S234: In response to receiving the completion notification 270 from the back-end server, the transaction management server 100 sets the status 184 of the transaction management DB 180 to “complete”. The transaction management server 100 continues to wait until it receives the completion notification 270 from the backend server 30 for all the individual processing requests 260 requested to the backend server 30 in step S232, and executes the processing.

  Further, in the processing of the transaction management server 100 shown in FIG. 4A, the transaction management server 100 receives the completion notification 270 from the back-end server 30 as another example of the transaction management operation in step S230. Accordingly, information indicating that the processing of the specific transaction has been completed may be sent to the user terminal 10 by mail.

[Another Embodiment of Operation Sequence]
FIG. 9 is a diagram illustrating an operation sequence of a system for managing transactions according to another embodiment of the invention. This operation sequence shows the mutual relationship among the respective stages of processing of the web server 20, the transaction management server 100 and the back-end server 30 shown in FIGS. 3, 4 and 8, and the same reference numerals are the same. Corresponds to a step. Description of portions common to FIG. 5 is omitted.

In step S 232, the transaction management server 100 transmits the individual processing request 260 to the back-end server 30. The individual processing request 260 is a request for processing a specific transaction included in the processing request 210, and is accepted by a specific server device included in the back-end server 30 that can process the specific transaction.
In step S 233, the transaction management server 100 further sets the status 184 of the transaction management DB 180 to “waiting” and waits for the completion notification 270 from the back-end server 30.
In step S234, the transaction management server 100 sets the status 184 of the transaction management DB 180 to “completed” in response to receiving the completion notification 270 from the back-end server. The transaction management server 100 continues to wait until it receives the completion notification 270 from the backend server 30 for all the individual processing requests 260 requested to the backend server 30 in step S232, and executes the processing.

The back-end server 30 executes the subsequent steps S320 and S330 in response to receiving the individual processing request 260 from the transaction management server 100 in step S310.
In step S320, the back-end server 30 executes transaction processing. Specifically, the transaction is processed by a specific server device that can process the individual processing request 260.
In step S330, the back-end server 30 executes a completion process. Specifically, the back-end server 30 transmits a completion notification 270 to the transaction management server 100.

In step S236, the status notification 280 transmitted from the transaction management server 100 to the user terminal 10 is the above-mentioned (information included in the status notification 280-1) or the next (information-3 included in the status notification 280). Either piece of information can be included, and each piece of information can include a status 184.
(Information included in status notification 280-3) Information indicating completion of the transaction based on the completion notification 270 transmitted by the back-end server 30.

  By doing so, the transaction management server 100 according to the present embodiment can also make an actual transaction be performed by the back-end server 30. Therefore, regardless of whether the actual transaction processing is performed by the transaction management server 100 itself or the back-end server 30, the transaction management server 100 according to the present embodiment integrates the transaction. Can be managed.

  As mentioned above, although demonstrated using embodiment of this invention, the technical scope of this invention is not limited to the range as described in the said embodiment. Various modifications or improvements can be added to the above embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 10 User terminal 20 Web server 30 Back end server 50 Inquiry and response 100 Transaction management server 110 http request reception means 120 Transaction transfer means 150 Transaction transfer reception means 160 Link information notification means 170 Transaction management means 180 Transaction management DB
210 Processing Request 220 Acceptance Notification 230 Transfer Notification 240 Link Information 250 Inquiry 260 Individual Processing Request 270 Completion Notification 280 Status Notification 282, 292 Response Message

Claims (4)

A transaction management server communicably connected to a terminal and a web server,
Information indicating an acceptance notification without waiting for completion of all the processes of the plurality of transactions executed by the transaction management server after receiving one http request accompanied by a plurality of transaction requests from the terminal. from the web server to be transmitted to the terminal, means for receiving information identifying information and the one http request identifying the pre SL terminal,
Means for continuously waiting for completion of the plurality of transactions on the basis of the received information identifying the one http request and storing each status information on behalf of the web server;
And a means for transmitting link information for inquiring status information of each of the plurality of transactions to the terminal based on the received information for identifying the terminal. A system including a transaction management server that is communicably connected to a terminal and a web server,
The web server is
Means for transmitting information identifying the terminal and information identifying the one http request to the transaction management server in response to receiving one http request accompanied by a plurality of transaction requests from the terminal;
The transaction management server
Means for receiving from the web server information identifying the terminal and information identifying the one http request;
Means for continuously waiting for completion of the plurality of transactions on the basis of the received information identifying the one http request and storing each status information on behalf of the web server;
Means for transmitting link information for inquiring status information of each of the plurality of transactions to the terminal based on the received information for identifying the terminal ;
The web server is
The system further comprising means for transmitting information indicating an acceptance notification to the terminal without waiting for completion of all the processes of the plurality of transactions executed by the transaction management server . The web server is
In response to receiving an http request with a request for the plurality of transactions from the terminal, for each transaction, information for identifying the terminal and information for identifying the transaction are transmitted to the transaction management server,
The transaction management server
Based on the information identifying the transaction received from the web server, and continuously waiting for the completion of the transaction on behalf of the web server, storing each status information,
Based on the information for identifying the terminal received from the web server, the link information for inquiring the status information of the transaction is transmitted to the terminal for each transaction.
The system according to claim 2. A transaction management server communicatively connected to a terminal and a web server manages a transaction,
The transaction management server is
Information indicating an acceptance notification without waiting for completion of all the processes of the plurality of transactions executed by the transaction management server after receiving one http request accompanied by a plurality of transaction requests from the terminal. from the web server to be transmitted to the terminal, receiving information identifying the information and the one http request identifying the pre SL terminal,
Based on the information identifying the received one http request, continuously waiting for the completion of the plurality of transactions on behalf of the web server, and storing each status information;
Transmitting a link information for inquiring status information of each of the plurality of transactions to the terminal based on the received information for identifying the terminal.

Images