Information processing apparatus, information processing system, and program

Abstract

To provide an information processing apparatus, an information processing system, and a program that enable a customer who has placed an order to check whether his / her order has been properly notified to a store device.SOLUTION: A relay server (information processing apparatus) comprises: an order receiving unit for receiving order data generated based on order information from a mobile terminal or order data from a store server that manages the provision of services related to the order information; an order data update unit for storing the received order data; an order data output unit for outputting the order data based on the order information to the store server; a status acquisition unit (order confirmation acquisition unit) for acquiring, from the store server, confirmation information indicating that the order data has been received; and a status notification unit (receipt completion notification unit) for notifying the mobile terminal that receipt of the order information has been completed on conditions that the confirmation information has been acquired.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] An embodiment of the present invention relates to an information processing device, an information processing system, and a program. [Background technology]

[0002] In recent years, the number of stores where customers can order products using their own mobile terminals such as smartphones and tablet terminals inside or outside the store, such as restaurants, has been increasing. An ordering system has been proposed that allows customers who visit a store to access a management control device using their own mobile terminal to order products (for example, Patent Document 1). A mobile order system is also known that allows customers to order and pay for products using their mobile terminals such as smartphones and tablet terminals.

[0003] In such conventional ordering systems, if there is an error in the order data received from the customer, or if some problem occurs with the store equipment that received the order data, the order data cannot be processed correctly. In such cases, the cooking of the food ordered by the customer may not start, and in some cases the order data may be discarded. To solve such problems, it is desirable for the customer who placed the order to be able to check whether his or her order has been properly notified to the store. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide an information processing device, an information processing system, and a program that enable a customer who has placed an order to check whether his or her order has been properly notified to the store equipment. [Means for solving the problem]

[0005] The information processing device of the embodiment includes an order receiving unit, an order data storage unit, an order data output unit, an order confirmation acquisition unit, and an acceptance completion notification unit. The order receiving unit receives order data generated based on order information from a mobile terminal, or order data from a store server that manages the provision of services related to the order information. The order data storage unit stores the accepted order information. The order data output unit outputs order data based on the order information to the store server. The order confirmation acquisition unit acquires confirmation information from the store server indicating that the order data has been accepted. The acceptance completion notification unit notifies the mobile terminal that acceptance of the order information has been completed, provided that the confirmation information has been acquired. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram illustrating an example of a schematic configuration of an ordering system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a data structure of the product master. [Diagram 3] FIG. 3 is a diagram illustrating an example of a data structure of the store master. [Figure 4] FIG. 4 is a diagram illustrating an example of the data structure of the member master. [Diagram 5] FIG. 5 is a diagram showing an example of the data structure of the order data held by the mobile order server, the relay server, and the store server. [Figure 6] FIG. 6 is a hardware block diagram showing an example of a hardware configuration of a relay server included in the ordering system. [Figure 7] FIG. 7 is a hardware block diagram showing an example of a hardware configuration of a store server included in the ordering system. [Figure 8] FIG. 8 is a sequence diagram showing an example of a flow of updating order data in the ordering system of the embodiment. [Figure 9] FIG. 9 is a sequence diagram showing an example of a process flow when a failure occurs in communication between a relay server and a store server in the ordering system. [Figure 10]FIG. 10 is a sequence diagram showing an example of a process flow in which, when a store server cannot process order data, the store server notifies the mobile terminal of the fact in the ordering system. [Figure 11] FIG. 11 is a diagram illustrating another example of the data structure of the order data. [Figure 12] FIG. 12 is a functional block diagram illustrating an example of a functional configuration of the relay server. [Figure 13] FIG. 13 is a functional block diagram illustrating an example of a functional configuration of the store server. [Figure 14] FIG. 14 is a flowchart showing an example of the flow of processing performed by the relay server. [Figure 15] FIG. 15 is a flowchart showing an example of the flow of processing performed by the store server. [Figure 16] FIG. 16 is a flowchart showing an example of the flow of communication confirmation processing performed between the store server and the relay server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, the embodiments will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments described below.

[0008] (Embodiment) Hereinafter, an ordering system 1 according to an embodiment of the present disclosure will be described with reference to the drawings.

[0009] (Outline of the ordering system) FIG. 1 is a block diagram showing an example of a schematic configuration of an ordering system according to an embodiment. The ordering system 1 includes a customer's mobile terminal 2, a mobile order server 3, a relay server 4, and a store server 5. The mobile terminal 2, the mobile order server 3, the relay server 4, and the store server 5 are connected to each other via a network N such as the Internet so that they can communicate with each other. The store server 5 is connected to a kitchen display, a printer, a POS terminal, and the like (not shown). The store server 5 displays the contents of the order received from the mobile terminal 2 via the mobile order server 3 and the relay server 4 on the kitchen display, and prints out a receipt with the order contents printed on it using a printer. The cook cooks the food while looking at the display on the kitchen display and the printed-out receipt. The POS terminal also handles accounting when a customer who has finished eating pays for the food and drink.

[0010] The ordering system 1 is constructed across, for example, customers who use a store, restaurants, a mobile order service provider that provides a mobile order service to the customers, and an associated service provider that provides an order association service that links the store and the mobile order service provider. The mobile order service provider accepts an order for a product from a customer, places an order with a store that sells the product via the associated service provider, and makes a payment for the order. In this embodiment, the ordering system 1 is described as a system for ordering a food and drink menu at a restaurant, as an example. That is, a customer orders a food and drink menu from a mobile terminal 2 to a mobile order server 3. The order can be made in the form of an eat-in or take-out purchase at the store, or, for example, a delivery request from a home to a restaurant. The ordering system 1 is an example of an information processing system in the present disclosure.

[0011] The mobile terminal 2 is an information processing terminal owned by a customer who uses the mobile order service, and is composed of a smartphone, a tablet terminal, a personal computer, etc. The mobile terminal 2 transmits and receives information to and from the mobile order server 3. The mobile terminal 2 may transmit and receive information to and from the mobile order server 3 using a function of a mobile order app, or may transmit and receive information to and from the mobile order server 3 by accessing a website using a browser. When eating and drinking in a restaurant, a customer may place an order through a mobile order by taking a seat and inputting a code symbol such as a two-dimensional code or a table number attached to the table into the app on the mobile terminal 2. This allows a customer who visits the restaurant to order a product even if a staff member has not come to the table where the customer is seated. Therefore, even if the restaurant is crowded or there are few staff members, the customer can quickly order a product.

[0012] The mobile order server 3 is managed, for example, by a mobile order service provider. The mobile order server 3 stores and manages order information received from the mobile terminal 2 of a customer who is a member. The order information received by the mobile order server 3 is sent to the store server 5 via the relay server 4. The store server 5 updates the order information according to the progress of the order at the store. The store server 5 outputs the updated order information to the relay server 4. In addition, the relay server 4 outputs the updated order information to the mobile order server 3. In this way, the mobile order server 3, the relay server 4, and the store server 5 share the order information.

[0013] The mobile order server 3 stores a product master 31, a store master 32, a member master 33, and order data 34.

[0014] The product master 31 is a master file that manages product information in association with a product ID that identifies a product sold in a store. The product information includes information such as product name and price. The product master 31 will be described in detail later (see FIG. 2).

[0015] The store master 32 is a master file that manages information about stores that use the mobile order service. The store master 32 will be described in detail later (see FIG. 3).

[0016] The member master 33 is a master file that stores member information for the mobile order service. The member master 33 will be described in detail later (see FIG. 4).

[0017] The order data 34 is a master file that stores the details of an order. The order data 34 will be described in detail later (see FIG. 5).

[0018] 2 is a diagram showing an example of the data structure of the product master. The product master 31 stores the product name and price, which are product information of the product, in association with a product ID that uniquely identifies the product. The product information may also include other information, such as sale information.

[0019] The product ID is information that identifies a product. The product ID is an example of product identification information. The product name is information that indicates the name of the product. The price is information that indicates the price of the product. The product master 31 may also store other product information such as product images.

[0020] 3 is a diagram showing an example of the data structure of the store master 32. The store master 32 stores the store name and the notification destination in association with the store ID.

[0021] The store ID is identification information that uniquely identifies a store. The store name is information that indicates the name of the store. The notification destination is information that indicates the notification destination of the store, such as the communication address of the store server 5 and the store's telephone number.

[0022] 4 is a diagram showing an example of the data structure of the member master. The member master 33 stores, for example, a member ID for identifying a member, the member's name, a notification destination (email address, phone number, etc.), payment information, etc. in association with each other. The payment information is account information, etc., required for making a payment through a payment business operator.

[0023] FIG. 5 is a diagram showing an example of the data structure of the order data held by the mobile order server, the relay server, and the store server. The order data 34 stores various information indicating the contents of the order in association with an order ID that uniquely identifies the order information notified from the mobile terminal 2 to the mobile order server 3. Since the order data 34 is held by the mobile order server 3, the relay server 4, and the store server 5, the order data held by each server will be distinguished by different symbols in the following description. Specifically, the mobile order server 3 holds the order data 34, the relay server 4 holds the order data 412 (see FIG. 6), and the store server 5 holds the order data 512 (see FIG. 7). The order ID is issued by the mobile order server 3 that receives the order from the user. The contents of the information managed by the order data 34 are not limited to the example of FIG. 5. For example, the order data 34 may include a customer ID that uniquely identifies the customer who placed the order.

[0024] The order data 34 includes an order information management file 35, an order data header management file 36, and an order data body management file 37. Of these, the order data header management file 36 and the order data body management file 37 are generated by the mobile order server 3 that receives the order.

[0025] The order information management file 35 is a file for managing the progress of an order. The order information management file 35 is generated by the relay server 4.

[0026] The order information management file 35 stores a store ID 12, an order acceptance date and time 13, a slip number 14, a table number 15, and a status 16 in association with an order ID 11 that uniquely identifies an order.

[0027] The order ID 11 is an identification number issued by the mobile order server 3 to uniquely identify an order.

[0028] The store ID 12 is identification information that uniquely identifies the store where the order was placed.

[0029] The order reception date and time 13 is the date and time when the relay server 4 receives the order data. Note that the order reception date and time 13 may be the date and time when the mobile order server 3 receives the order input from the mobile terminal 2.

[0030] The slip number 14 is identification information that is issued (numbered) by the store server 5 on the condition that the order data is accepted, and is managed for each store to identify the order information.

[0031] Table number 15 is the number of the table where the customer is seated.

[0032] Status 16 is information that indicates the progress of an order, the status of the exchange of order data between servers, etc. Status 16 is, for example, "Order successful", "Order failed", "Communication error occurred", "Transaction completed", etc. "Order successful" indicates that the store server 5 has accepted the order data. "Order failed" indicates that the store server 5 has not accepted the order data. "Communication error occurred" indicates that a communication error has occurred between the relay server 4 and the store server 5. "Transaction completed" indicates that the transaction related to the order ID has been completed. However, the types of status 16 are not limited to these.

[0033] The order information management file 35 and the order data header management file 36 are updated as needed according to the progress of the order in the store server 5. For example, the status 16 of the order information management file 35 is updated according to the progress of the order. The slip number 19 of the order data header management file 36 is empty when the mobile order server 3 generates the order data 34, and is assigned a slip number when the order data 34 is notified to the store server 5 and the store server 5 issues a slip number. Each file is shared by the mobile order server 3, the relay server 4, and the store server 5 every time it is updated. Note that, although the information included in the order data 34 is shared by the mobile order server 3, the relay server 4, and the store server 5, the data format of the database that constitutes the order data 34 may be different between the mobile order server 3, the relay server 4, and the store server 5 due to reasons such as different server administrators.

[0034] The order data header management file 36 is a file that manages information that uniquely identifies an order. The order data header management file 36 stores an order category 18, a slip number 19, a table number 20, a delivery number 21, and a number of people 22 in association with an order ID 17 that uniquely identifies an order.

[0035] Order ID 17 is the same information as order ID 11 described above.

[0036] The order category 18 is, for example, information for identifying the type of order. The order category 18 stores information for identifying whether the order is for eating in, i.e., an order for taking out, or an order for delivery.

[0037] The slip number 19 is the same information as the slip number 14 described above.

[0038] The table number 20 is a number that identifies the table at which the customer is seated when an order is made in the form of eat-in. When placing an order, the customer obtains the table number registered in the code symbol by reading a code symbol (barcode or two-dimensional code) attached to the table at which the customer is seated.

[0039] The delivery number 21 is identification information for identifying an order when the order is placed in the form of delivery.

[0040] The number of people 22 is the number of people in a group including the customer when an order is placed in the form of eat-in. The customer inputs the number of people 22 into the mobile terminal 2 when placing an order.

[0041] The order data body management file 37 is a file that indicates specific order contents. The order data body management file 37 stores the sequence number 24, the product ID 25, the quantity 26, the unit price 27, and the takeaway flag 28 in association with the order ID 23 that uniquely identifies the order.

[0042] Order ID23 is the same information as order ID11 described above.

[0043] The sequence number 24 is an identification number that identifies multiple products ordered at the same time and that are associated with the same order ID 23. The sequence number 24 is issued by the relay server 4. For example, if a customer orders product A and product B, product A is assigned a sequence number, for example, "1," and product B is assigned a sequence number, for example, "2."

[0044] The product ID 25 is information for identifying the ordered product. The product ID 25 corresponds to the product ID stored in the product master 31 described above.

[0045] The quantity 26 is information indicating the order quantity of the product with the product ID 25 .

[0046] The unit price 27 is information that indicates the unit price of the product with the product ID 25 .

[0047] The take-out flag 28 is identification information that indicates that the product is to be taken home when an order is placed in the form of take-out.

[0048] The order information management file 35, the order data header management file 36, and the order data body management file 37 are associated with each other by order IDs. That is, for the same order, the order ID 11 stored in the order information management file 35, the order ID 17 stored in the order data header management file 36, and the order ID 23 stored in the order data body management file 37 store the same identification number.

[0049] The relay server 4 is a server that implements a WebAPI for linking the order data input by the customer to the store server 5, since the order is placed via the carrier line (Internet line) of the mobile terminal 2. The WebAPI (Application Programming Interface) is a mechanism that allows the functions of software running on a certain computer to be used by other computers via a network N such as the Internet. The mobile terminal 2, the mobile order server 3, and the store server 5 connected to the relay server 4 via the Internet can link with the relay server 4 by calling the functions defined in the WebAPI. The relay server 4 stores the above-mentioned order data. The relay server 4 communicates with the store server 5 and updates the order data according to the progress of the order at the store. Specifically, it updates the status 16 of the order information management file 35. The relay server 4 also outputs the updated contents of the order data to the mobile order server 3. The relay server 4 is an example of an information processing device in the present disclosure.

[0050] The store server 5 manages various information related to the sale of the ordered product. When the store server 5 receives a notification from the relay server 4 that a new order has been placed, the store server 5 inquires of the relay server 4 and acquires the order data from the relay server 4. Alternatively, the store server 5 repeatedly inquires of the relay server 4 at intervals of about a few seconds and acquires the order data from the relay server 4. The store server 5 also displays the order details on a kitchen display (not shown) connected to the store server 5 based on the acquired order data. Furthermore, a slip with the order details printed on it is printed out by a printer (not shown) connected to the store server 5. The cook checks the display on the kitchen display and the slip and starts cooking. The store server 5 also updates the order data according to the progress of the order and outputs the updated contents to the relay server 4.

[0051] (Hardware configuration of relay server) The hardware configuration of the relay server 4 will be described with reference to Fig. 6. Fig. 6 is a hardware block diagram showing an example of the hardware configuration of the relay server constituting the ordering system.

[0052] The relay server 4 includes a control unit 40, a storage unit 41, a display unit 42, an operation unit 43, and a communication unit 44. The control unit 40, the storage unit 41, the display unit 42, the operation unit 43, and the communication unit 44 are connected to each other via a bus 45 or the like.

[0053] The control unit 40 is configured as a computer including a CPU 401, a ROM 402, and a RAM 403. The CPU 401, the ROM 402, and the RAM 403 are connected to each other via a bus 45.

[0054] The CPU 401 controls the overall operation of the relay server 4. The ROM 402 stores various programs, such as a program used to drive the CPU 401, and various data. The RAM 403 is used as a work area for the CPU 401, and loads various programs and data stored in the ROM 402 and the storage unit 41. The control unit 40 executes various control processes of the relay server 4 by the CPU 401 operating in accordance with the ROM 402 and a control program 411 stored in the storage unit 41 and loaded in the RAM 403.

[0055] The storage unit 41 is configured with a storage medium such as a HDD or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 41 stores a control program 411, a store master 32, order data 412, and the like.

[0056] The control program 411 is a program for causing the relay server 4 to perform a predetermined operation.

[0057] The store master 32 is as described above (see FIG. 3).

[0058] The order data 412 is the same as the order data 34 described above (see FIG. 5). However, since the contents of the order data may differ depending on the timing of data updates, different reference numerals will be used in the description of this embodiment.

[0059] The relay server 4 is equipped with a WebAPI that can be used by the mobile order server 3 and the store server 5 connected via a network N such as the Internet. The WebAPI has functions such as "order data notification," "order data acquisition," "order data status notification," "order data status acquisition," and "communication confirmation."

[0060] The relay server 4 uses the "order data notification" function to receive the notification of the order data 34 from the mobile order server 3. In addition, the relay server 4 uses the "order data notification" function to notify the store server 5 that it has received the notification of the order data 34 from the mobile order server 3.

[0061] The relay server 4 uses the "order data acquisition" function to acquire the order data 34 from the mobile order server 3. In addition, the relay server 4 uses the "order data acquisition" function to accept a request from the store server 5 and notify the store server 5 of the order data 34 acquired from the mobile order server 3 (updated order data 412).

[0062] The relay server 4 uses the "order data status notification" function to obtain the status 16 of the order data 512 notified from the store server 5. The relay server 4 obtains from the store server 5, for example, an order failure status indicating that processing of the order data has failed and the error code that occurred at that time.

[0063] Upon receiving a request for “order data status acquisition” from the mobile order server 3 , the relay server 4 notifies the mobile order server 3 of the status 16 of the order data 412 .

[0064] The relay server 4 repeatedly checks whether the communication between the store server 5 and the relay server 4 is normal using the "communication check" function.

[0065] (Store server hardware configuration) The hardware configuration of the store server 5 will be described with reference to Fig. 7. Fig. 7 is a hardware block diagram showing an example of the hardware configuration of the store server constituting the ordering system.

[0066] The store server 5 includes a control unit 50, a memory unit 51, a display unit 52, an operation unit 53, and a communication unit 54. The control unit 50, the memory unit 51, the display unit 52, the operation unit 53, and the communication unit 54 are connected to each other via a bus 55 or the like.

[0067] The control unit 50 is configured as a computer including a CPU 501, a ROM 502, and a RAM 503. The CPU 501, the ROM 502, and the RAM 503 are connected to each other via a bus 55.

[0068] The CPU 501 controls the overall operation of the store server 5. The ROM 502 stores various programs, such as a program used to drive the CPU 501, and various data. The RAM 503 is used as a work area for the CPU 501, and loads various programs and data stored in the ROM 502 and the storage unit 51. The control unit 50 executes various control processes of the store server 5 by the CPU 501 operating in accordance with the ROM 502 and a control program 511 stored in the storage unit 51 and loaded in the RAM 503.

[0069] The storage unit 51 is configured with a storage medium such as a HDD or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 51 stores a control program 511, a product master 31, order data 512, and the like.

[0070] The control program 511 is a program for causing the store server 5 to perform a predetermined operation.

[0071] The product master 31 is as described above (see FIG. 2).

[0072] The order data 512 is the same as the order data 34 described above (see FIG. 5). However, since the contents of the order data may differ depending on the timing of data updates, different reference numerals will be used in the description of this embodiment.

[0073] (Order data update procedure) A flow in which the order data 34, which is placed at the mobile order server 3, is updated and shared between the relay server 4 and the store server 5 will be described with reference to Fig. 8. Fig. 8 is a sequence diagram showing an example of the flow of updating order data in the ordering system of the embodiment.

[0074] The customer inputs an order into the mobile terminal 2 (step S0). Note that, as an example, the following description will be given assuming that the customer comes to a store and eats and drinks there.

[0075] The mobile terminal 2 notifies the mobile order server 3 of order information (step S1). The order information includes at least the member ID of the mobile order service, the store ID, the table number, the number of customers, and the product ID of the ordered product.

[0076] The mobile order server 3 acquires the order information notified from the mobile terminal 2 and issues an order ID (step S2).

[0077] Furthermore, the mobile order server 3 generates the order data 34 including the order data header management file 36 and the order data body management file 37 (step S3). At this time, the mobile order server 3 issues the sequence number 24.

[0078] The mobile order server 3 notifies the relay server 4 of the order data 34 (step S4). Specifically, the mobile order server 3 notifies the relay server 4 of the generated order data header management file 36 and order data body management file 37.

[0079] The relay server 4 generates the order information management file 35 from the order data header management file 36 and the order data body management file 37 (step S5). The generated order information management file 35, the order data header management file 36 and the order data body management file 37 acquired from the relay server 4 become the order data 412.

[0080] The relay server 4 holds the order data 412 generated in step S5 (step S6).

[0081] The relay server 4 notifies the store server 5 of the order data 412 (step S7).

[0082] The store server 5 receives the order data 412 from the relay server 4 (step S8).

[0083] The store server 5 issues a slip number (step S9).

[0084] The store server 5 updates the order data 512 by storing the slip number in the corresponding location of the order data 512 (step S10).

[0085] The store server 5 notifies the relay server 4 of the issued slip number (step S11). This notification of the slip number also serves as a notification of the status "order successful", which indicates that the store server 5 has received the order data 412 from the relay server 4.

[0086] The relay server 4 stores the slip number in the corresponding location of the order data 412 and changes the status 16 to information indicating "order successful", thereby updating and storing the order data 412 (step S12).

[0087] The mobile order server 3 sends a request for notifying the status of the order data to the relay server 4 (step S13). The mobile order server 3 requests the relay server 4 to notify the status of the order data at a predetermined time interval.

[0088] The relay server 4 receives the order data status notification request from the mobile order server 3 and notifies the mobile order server 3 of the slip number and the status (order successful) (step S14).

[0089] The mobile order server 3 updates and stores the order data 34 by storing the slip number and the status in the corresponding locations of the order data 34 (step S15).

[0090] The mobile order server 3 notifies the customer's mobile terminal 2 of the slip number (step S16).

[0091] The mobile terminal 2 notifies the customer that the order has been transmitted to the store server 5, for example by displaying the received slip number on the screen (step S17).

[0092] If the customer needs to place an additional order, he or she inputs the order again into the mobile terminal 2 (step S18).

[0093] The mobile terminal 2 notifies the mobile order server 3 of the order information again (step S19). The order information includes at least the member ID of the mobile order service, the store ID, the table number, the number of customers, and the product ID of the ordered product.

[0094] The mobile order server 3 generates order data 34 including the details of the additional order (step S20). Specifically, the mobile order server 3 generates an order data header management file 36 and an order data body management file 37, similar to step S3. At this time, the mobile order server 3 issues a sequence number 24.

[0095] The mobile order server 3 notifies the relay server 4 of the order data 34 relating to the reorder (step S21).

[0096] The relay server 4 acquires the order data 34 notified in step S21, and generates the order information management file 35. Then, the relay server 4 holds the generated order information management file 35, the order data header management file 36, and the order data body management file 37 as order data 412 (step S22).

[0097] The relay server 4 notifies the store server 5 of the stored order data 412 (step S23).

[0098] The store server 5 receives the order data 412 from the relay server 4 (step S24).

[0099] The store server 5 issues a slip number (step S25). If there is an unaccounted order accepted from a table with the same table number remaining in the order data 512 held by the store server 5, the store server 5 determines that a reorder has been made and issues, for example, a slip number that is the same as the slip number 14 already assigned to the unaccounted order data 512. Alternatively, the store server 5 may issue a slip number associated with the slip number 14 already assigned to the unaccounted order data 512. This allows the store server 5 to handle multiple orders with different order IDs made from the same table as a single order, making it possible, for example, to carry out accounting for multiple orders all at once.

[0100] The store server 5 holds the order data 512 (step S26). At this time, the store server 5, having acquired the order data 512, updates the status 16 of the order information management file 35 to "order successful."

[0101] The store server 5 notifies the relay server 4 of a status indicating "order success" (step S27).

[0102] The relay server 4 stores a status indicating "order successful" in the corresponding portion of the order data 34, and holds the order data 412 (step S28).

[0103] The mobile order server 3 sends a request for notifying the status of the order data to the relay server 4 (step S29). The mobile order server 3 requests the relay server 4 to notify the status of the order data at a predetermined time interval.

[0104] The relay server 4 notifies the mobile order server 3 of the status (order success) (step S30).

[0105] The mobile order server 3 stores the status in a corresponding location of the order data 34 and retains the order data 34 (step S31).

[0106] The mobile order server 3 notifies the customer's mobile terminal 2 of the status (order success) (step S32).

[0107] The mobile terminal 2 notifies the customer that the reorder has been transmitted to the store server 5 (step S33).

[0108] Of the processes described here, the processes performed between the relay server 4 and the mobile order server 3, and the processes performed between the relay server 4 and the store server 5 are performed using the functions of the WebAPI described above.

[0109] Here, the store server 5 is described as issuing the slip number 14 for the reorder, but the mobile order server 3 that has received the reorder may determine that a reorder has been made based on the fact that there is an unaccounted order received from the same mobile terminal 2 or customer with the same customer ID remaining in the order data 34 that it holds, and may use the same slip number as the slip number 14 already assigned to the unaccounted order data 34 at the time of receiving the reorder, for example, at step S20 in FIG. 8. That is, the reorder may be associated with the slip number of the unaccounted order from the same customer and saved as order data. Note that the relay server 4, instead of the mobile order server 3, may determine that a reorder has been made based on the fact that there is an unaccounted order received from the same mobile terminal 2 or customer with the same customer ID remaining in the order data 412 that it holds, and may use the same slip number as the slip number 14 already assigned to the unaccounted order data 412 at the time of receiving the reorder, for example, at step S22 in FIG. 8. That is, the mobile order server 3 or the relay server 4 may perform linking processing of the invoice numbers of unpaid orders from the same customer and reorders, and store them as order data. In this case, if an invoice number is assigned to the order data, the store server 5 uses that invoice number, and if no invoice number is assigned, it simply issues a new invoice number.

[0110] (Processing flow between servers when a communication failure occurs) Next, a process flow performed by the ordering system 1 when a failure occurs in communication between the relay server 4 and the store server 5 will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing an example of a process flow when a failure occurs in communication between the relay server and the store server in the ordering system.

[0111] The store server 5 transmits a communication confirmation signal to the relay server 4 at a predetermined time interval (step S41). The communication confirmation signal is a test signal transmitted to confirm that communication is normally performed between the store server 5 and the relay server 4. The communication confirmation signal is repeatedly transmitted at a predetermined time interval while the order data reception process described in FIG. 8 is being performed.

[0112] The relay server 4 receives the communication confirmation signal (step S42).

[0113] The relay server 4 transmits a response signal indicating that the communication confirmation signal has been received to the store server 5 (step S43).

[0114] The store server 5 repeatedly transmits a communication confirmation signal to the relay server 4 at a predetermined time interval (step S44).

[0115] When communication between the store server 5 and the relay server 4 is interrupted, the relay server 4 detects that it cannot receive a communication confirmation signal from the store server 5 (step S45).

[0116] The mobile order server 3 requests the relay server 4 to notify the status of the order data 412 (step S46). The mobile order server 3 requests the relay server 4 to notify the status of the order data at a predetermined time interval.

[0117] When the relay server 4 detects a breakdown in communication with the store server 5, it notifies the mobile order server 3 of an error response indicating the breakdown in communication (step S47).

[0118] The relay server 4 receives the error response (step S48).

[0119] The relay server 4 notifies the mobile terminal 2 of an error response (step S49).

[0120] The mobile terminal 2 receives the error response and notifies the user that the order has failed due to the occurrence of an error (step S50).

[0121] In this way, when communication between the store server 5 and the relay server 4 is interrupted, the ordering system 1 can notify the customer's mobile terminal 2 of the interruption of communication via the mobile order server 3. This allows the customer to recognize that they are unable to place an order with the store. Note that when the mobile terminal 2 is notified that communication between the store server 5 and the relay server 4 is interrupted, it may not accept orders from customers.

[0122] (Notification of an error due to incomplete order data) The flow of processing performed by the ordering system 1 when there is an error in the order data 412 notified from the relay server 4 to the store server 5 will be described with reference to Fig. 10. Fig. 10 is a sequence diagram showing an example of the flow of processing in the ordering system when the store server cannot process the order data and notifies the mobile terminal of that fact.

[0123] The relay server 4 notifies the store server 5 of the order data 412 (step S51).

[0124] The store server 5 receives the order data 412 from the relay server 4 (step S52).

[0125] The store server 5 detects that the received order data 412 is incomplete or that an error has occurred during the process of accepting the received order data 412 (step S53).

[0126] The store server 5 notifies the relay server 4 of a status indicating that the order has failed and an error code indicating the content of the error (step S54). The error code is assumed to be shared between the mobile order server 3, the relay server 4, and the store server 5. The order data 34 (or the order data 412, the order data 512) described above may be in the format of the order data 39 shown in FIG. 11. The order data 39 has an order information management file 38, an order data header management file 36, and an order data body management file 37. The order data header management file 36 and the order data body management file 37 are as described above (see FIG. 5). The order information management file 38 further stores an error code 29 in addition to the order information management file 35. The error code 29 is information for identifying the content of the error that has occurred in the store server 5.

[0127] The relay server 4 updates the order data 412 held therein based on the information notified in step S54 (step S55).

[0128] The mobile order server 3 requests the relay server 4 to notify the status of the order data 412 (step S56).

[0129] The relay server 4 notifies the mobile order server 3 of the order failure status and the error code (step S57).

[0130] The mobile order server 3 receives the order failure status and the error code, and updates the order data 34 (step S58).

[0131] The mobile order server 3 notifies the mobile terminal 2 of the order failure status and the error code (step S59).

[0132] The mobile terminal 2 receives the order failure status and the error code, and then notifies the user that the order has failed and the details of the error that has occurred by displaying the information on the screen of the mobile terminal 2 (step S60).

[0133] (Functional configuration of the relay server) The functional configuration of the relay server 4 will be described with reference to Fig. 12. Fig. 12 is a functional block diagram showing an example of the functional configuration of the relay server.

[0134] The control unit 40 functions as an order receiving unit 61, an order data updating unit 62, an order data output unit 63, a status acquiring unit 64, a status notifying unit 65, a communication checking unit 66, and an error responding unit 67, as a result of the CPU 401 operating in accordance with the control programs stored in the ROM 402 or the storage unit 41. Note that all or part of these functions may be configured using hardware such as a dedicated circuit.

[0135] The order receiving unit 61 obtains, from the mobile order server 3, order data 34 that the mobile order server 3 has generated based on order information from the mobile terminal 2. The order receiving unit 61 also obtains, from the store server 5, order data 512 to which a slip number issued by the store server 5 has been assigned and order data 512 with an updated status. Note that the order receiving unit 61 does not receive the order data 34 from the mobile order server 3 if the communication confirmation unit 66 cannot confirm communication.

[0136] The order data update unit 62 generates an order information management file 35 (or an order information management file 38) from the order data 34 acquired from the mobile order server 3. The order data update unit 62 also holds order data 412 including the generated order information management file 35. The order data update unit 62 also holds the order data 512 acquired from the store server 5 as the order data 412.

[0137] The order data output unit 63 outputs the order data 412 to the store server 5 that manages the provision of the service related to the order data.

[0138] The status acquisition unit 64 acquires the status 16 such as confirmation information indicating that the order data 412 has been accepted from the store server 5. The status acquisition unit 64 is an example of an order confirmation acquisition unit in the present disclosure.

[0139] The status notification unit 65 notifies the mobile terminal 2 that the acceptance of the order information notified from the mobile terminal 2 to the mobile order server 3 has been completed, on the condition that confirmation information has been obtained from the store server 5. In this embodiment, the status notification unit 65 notifies the mobile terminal 2 that the acceptance of the order information has been completed via the mobile order server 3. The status notification unit 65 is an example of a acceptance completion notification unit in the present disclosure.

[0140] The communication confirmation unit 66 receives the communication confirmation signal repeatedly transmitted by the store server 5. Furthermore, when the communication confirmation unit 66 receives the communication confirmation signal, it transmits a response signal to the store server 5 indicating that the communication confirmation signal has been received.

[0141] The error response unit 67 notifies the mobile terminal 2 of an error response on condition that the communication confirmation unit 66 does not receive the communication confirmation signal. In this embodiment, the error response unit 67 notifies the mobile terminal 2 of the error response via the mobile order server 3.

[0142] (Store server functional configuration) The functional configuration of the store server 5 will be described with reference to Fig. 13. Fig. 13 is a functional block diagram showing an example of the functional configuration of the store server.

[0143] The control unit 50 functions as an order receiving unit 71, a slip number issuing unit 72, an order data updating unit 73, an order data output unit 74, a status notifying unit 75, a payment processing unit 76, and a communication checking unit 77, as a result of the CPU 501 operating in accordance with the control programs stored in the ROM 502 or the storage unit 51. Note that all or part of these functions may be configured using hardware such as a dedicated circuit.

[0144] The order receiving unit 71 receives the order data 412 from the relay server 4. In addition, the order receiving unit 71 checks whether the order data 412 is complete.

[0145] The slip number issuing unit 72 issues (issues) a slip number 14 on the condition that the order data 412 has been accepted from the relay server 4. Furthermore, when the slip number issuing unit 72 accepts the order data 412, if there is unaccounted order data 512 accepted from the same table number or the same customer, it determines that a reorder has been made and uses the same slip number as the slip number 14 already assigned to the unaccounted order data 512. Alternatively, it issues a slip number associated with the slip number 14 already assigned to the unaccounted order data 512. Note that, as described above, the mobile order server 3 or the relay server 4 that accepted the reorder may use the same slip number as the slip number 14 already assigned to the unaccounted order data when accepting the reorder. In this case, the slip number issuing unit 72 may use the slip number if a slip number has been assigned to the order data, or may issue a new slip number if no slip number has been assigned.

[0146] The order data update unit 73 updates and holds the order data 512 in accordance with the progress of the order.

[0147] The order data output unit 74 notifies the relay server 4 of the issued slip number 14 .

[0148] The status notification unit 75 notifies the relay server 4 when the status 16 in the order data 512 is updated.

[0149] The payment processing unit 76 performs payment related to the order data 512. The payment processing unit 76 also causes an external server device (not shown) or the like to perform payment related to the order data 512.

[0150] The communication confirmation unit 77 repeatedly performs communication confirmation to check whether communication is normally performed between the relay server 4 and the store server 5. The communication confirmation unit 77 transmits a communication confirmation signal to the relay server 4 at a predetermined time interval.

[0151] (Processing flow performed by the relay server) The flow of processing performed by the relay server 4 will be described with reference to Fig. 14. Fig. 14 is a flowchart showing an example of the flow of processing performed by the relay server.

[0152] The order receiving unit 61 judges whether the order data 34 has been notified from the mobile order server 3 (step S61). If it is judged that the order data 34 has been notified from the mobile order server 3 (step S61: Yes), the process proceeds to step S62. On the other hand, if it is not judged that the order data 34 has been notified from the mobile order server 3 (step S61: No), the process proceeds to step S65.

[0153] When it is determined in step S61 that the order data 34 has been notified from the mobile order server 3, the order data update unit 62 generates a new order information management file 35 (or order information management file 38) (step S62).

[0154] The order data update unit 62 replaces the order data 412 currently held by the relay server 4 with the order data 412 including the order information management file 35 (or order information management file 38) generated in step S62 and holds it (step S63).

[0155] The order data output unit 63 notifies the store server 5 of the order data 412 held in step S64 (step S64). Then, the process returns to step S61.

[0156] Returning to step S61, the explanation will be made. If it is determined in step S61 that the order data 34 has not been notified from the mobile order server 3, the order receiving unit 61 determines whether the order data 512 has been notified from the store server 5 (step S65). If it is determined that the order data 512 has been notified from the store server 5 (step S65: Yes), the process proceeds to step S66. On the other hand, if it is determined that the order data 512 has not been notified from the store server 5 (step S65: No), the process returns to step S61.

[0157] When it is determined in step S65 that the order data 512 has been notified from the store server 5, the order data update unit 62 replaces the order data 412 currently held by the relay server 4 with the order data 512 acquired from the store server 5 and holds it (step S66).

[0158] The status acquisition unit 64 determines whether the status 16 of the order data 412 held in step S66 is an error status (step S67). If it is determined that the status 16 is an error status (step S67: Yes), the process proceeds to step S68. On the other hand, if it is not determined that the status 16 is an error status (step S67: No), the process proceeds to step S69.

[0159] If it is determined in step S67 that the status 16 is an error status, the status notification unit 65 notifies the mobile order server 3 of at least the order ID 11, the error status, and the error code (step S68). The notification in step S68 is a notification indicating that the order has failed. Thereafter, the relay server 4 ends the process. The mobile order server 3, which has been notified that the order has failed, notifies the mobile terminal 2 accordingly.

[0160] On the other hand, if it is determined in step S67 that the status 16 is not an error status, the status notification unit 65 notifies the mobile order server 3 of at least the order ID 11, the slip number 14, and the order success status (step S69). The notification in step S69 is a notification indicating that the order was successful. Thereafter, the relay server 4 ends the process. Note that, upon being notified that the order was successful, the mobile order server 3 notifies the mobile terminal 2 accordingly.

[0161] The relay server 4 performs the notification to the mobile order server 3 in steps S68 and S69 when it receives a status notification request for the order data 412 from the mobile order server 3.

[0162] (Processing flow performed by the store server) The flow of processing performed by the store server 5 will be described with reference to Fig. 15. Fig. 15 is a flow chart showing an example of the flow of processing performed by the store server.

[0163] The order receiving unit 71 determines whether the order data 412 has been notified from the relay server 4 (step S81). If it is determined that the order data 412 has been notified from the relay server 4 (step S81: Yes), the process proceeds to step S82. On the other hand, if it is determined that the order data 412 has not been notified from the relay server 4 (step S81: No), the process proceeds to step S89.

[0164] If it is determined in step S81 that the order data 412 has been notified from the relay server 4, the order receiving unit 71 acquires the order data 412 (step S82).

[0165] The order receiving unit 71 determines whether the acquired order data 412 is normal (step S83). If it is determined that the order data 412 is normal (step S83: Yes), the process proceeds to step S84. On the other hand, if it is determined that the order data 412 is not normal (step S83: No), the process proceeds to step S92.

[0166] If it is determined in step S83 that the order data 412 is normal, the slip number issuing unit 72 determines whether there is unaccounted order data 512 ordered from the same table number (step S84). If it is determined that there is unaccounted order data 512 ordered from the same table number (step S84: Yes), the process proceeds to step S86. On the other hand, if it is not determined that there is unaccounted order data 512 ordered from the same table number (step S84: No), the process proceeds to step S85.

[0167] If it is determined in step S84 that there is unaccounted order data 512 ordered from the same table number, then slip number issuing unit 72 issues a slip number associated with the slip number assigned to unaccounted order data 512 (step S86). Note that slip number issuing unit 72 may issue the same slip number as the slip number assigned to unaccounted order data 512 ordered from the same table number. Then, proceed to step S87.

[0168] On the other hand, if it is determined in step S84 that there is no unaccounted order data 512 from the same table number, slip number issuing unit 72 issues a new slip number (step S85).

[0169] Following step S85 or step S86, the order data update unit 73 stores the issued slip number in the order data 412 obtained from the relay server 4, and holds this as order data 512 in the storage unit 51 (step S87).

[0170] The order data output unit 74 notifies the relay server 4 of the order ID 11 and the slip number 14 issued in step S85 or step S86 (step S88), and then proceeds to step S89.

[0171] Returning to step S83, the explanation will be made. If it is determined in step S83 that the order data 412 is not normal, the status notification unit 75 notifies the relay server 4 of at least the order ID 11, the error status, and the error code (step S92). After that, the store server 5 ends the process. The notification in step S92 is a notification indicating that the order has failed. The relay server 4, which has been notified that the order has failed, notifies the mobile terminal 2 of that effect via the mobile order server 3.

[0172] If it is determined in step S81 that the order data has not been notified from the relay server 4, or following step S88, the payment processor 76 determines whether the transaction has been completed (step S89). If it is determined that the transaction has been completed (step S89: Yes), the process proceeds to step S90. On the other hand, if it is not determined that the transaction has been completed (step S89: No), the process returns to step S81.

[0173] If it is determined in step S89 that the transaction is completed, the order data update unit 73 updates the status of the order data 512 to "transaction completed" and stores this in the storage unit 51 (step S90).

[0174] The status notification unit 75 notifies the relay server 4 of at least the order ID 11 and the transaction completion status (step S91). After that, the store server 5 ends the process.

[0175] (Flow of communication confirmation process) The flow of the communication check process performed between the store server 5 and the relay server 4 will be described with reference to Fig. 16. Fig. 16 is a flowchart showing an example of the flow of the communication check process performed between the store server and the relay server.

[0176] The communication confirmation unit 77 of the store server 5 transmits a communication confirmation signal to the relay server 4 (step S101). Note that the transmission of the communication confirmation signal is repeatedly performed at predetermined time intervals.

[0177] The communication confirmation unit 66 of the relay server 4 determines whether a communication confirmation signal has been received from the store server 5 (step S102). If it is determined that a communication confirmation signal has been received from the store server 5 (step S102: Yes), the communication confirmation unit 66 repeats the reception confirmation of the communication confirmation signal in step S102. On the other hand, if it is not determined that a communication confirmation signal has been received from the store server 5 (step S102: No), the process proceeds to step S103.

[0178] In step S102, if it is determined that the communication confirmation signal has not been received from the store server 5, the error response unit 67 notifies the mobile order server 3 of an error status (step S103). After that, the reception confirmation of the communication confirmation signal in step S102 is repeatedly performed.

[0179] (Effects of the embodiment) As described above, the relay server 4 (information processing device) of the embodiment includes an order receiving unit 61 that receives order data 34 generated based on order information from the mobile terminal 2 or order data 512 from the store server 5 that manages the provision of services related to the order information, an order data updating unit 62 that holds the received order data, an order data output unit 63 that outputs order data 412 based on the order information to the store server 5, a status acquiring unit 64 (order confirmation acquiring unit) that acquires confirmation information indicating that the order data 412 has been accepted from the store server 5, and a status notifying unit 65 (acceptance completion notifying unit) that notifies the mobile terminal 2 that acceptance of the order information has been completed on condition that the confirmation information has been acquired. Therefore, a customer who has placed an order can confirm whether his or her order has been correctly notified to the store server 5.

[0180] Furthermore, when the relay server 4 (information processing device) of the embodiment receives multiple pieces of order information from the mobile terminal 2 during one transaction, the confirmation information for the order data 412 that the order data output unit 63 outputs for the first time to the store server 5 is the slip number 14 issued on the condition that the store server 5 has received the order data 412, and the confirmation information for the order data 412 that the order data output unit 63 outputs for the second or subsequent times to the store server 5 is status information indicating that the store server 5 has received the order data 412. Therefore, even when orders relating to one transaction are made repeatedly, the customer who made the order can check whether his or her order has been properly notified to the store server 5.

[0181] Moreover, the relay server 4 (information processing device) of the embodiment further includes a communication confirmation unit 66 that receives a communication confirmation signal repeatedly transmitted by the store server 5, and an error response unit 67 that notifies the mobile terminal 2 of an error response on condition that the communication confirmation unit 66 does not receive the communication confirmation signal. Therefore, by immediately detecting the occurrence of a communication interruption between the relay server 4 and the store server 5 and notifying the customer, the customer can be made aware that the order cannot be notified to the store.

[0182] Furthermore, in the relay server 4 (information processing device) of the embodiment, when the communication confirmation unit 66 cannot confirm communication, the order receiving unit 61 does not accept order information from the mobile terminal 2. Therefore, when the order cannot be notified to the store server 5, the order reception is stopped, so that the customer can be made aware that the order cannot be notified to the store.

[0183] Furthermore, in the relay server 4 (information processing device) of the embodiment, the status acquisition unit 64 (order confirmation acquisition unit) further receives, from the store server 5, identification information for identifying the order data 512 and error information indicating the reason for failure to accept the order information, and the status notification unit 65 (acceptance completion notification unit) further notifies the identification information and error information to the mobile terminal 2. Therefore, if an abnormality occurs in the ordering system 1, the customer who placed the order can be immediately notified of the system status.

[0184] In particular, since the relay server 4 of the embodiment implements a WebAPI, the information held by each device can be easily linked between the mobile terminal 2, the mobile order server 3, and the store server 5 by invoking functions defined in the WebAPI via a network N such as the Internet.

[0185] The ordering system 1 of the embodiment is an information processing system having a mobile order server 3 that receives order information from a mobile terminal 2, a store server 5 that manages the provision of services related to the order information, and a relay server 4 that relays between the mobile order server 3 and the store server 5. The mobile order server 3 receives order information from the mobile terminal 2, the relay server 4 receives order data 34 generated based on the order information received by the mobile order server 3, holds it as order data 412, and notifies the store server 5. The store server 5 holds the order data 412 received from the relay server 4 as order data 512, and notifies the relay server 4 of confirmation information indicating that the order data 412 has been received. The relay server 4 updates the order data 412 based on the confirmation information, and notifies the mobile order server 3 of the confirmation information. The mobile order server 3 notifies the mobile terminal 2 of the confirmation information. Therefore, a customer who has placed an order can check whether his or her order has been correctly notified to the store server 5.

[0186] (Modification of the embodiment) In the previous embodiment, a case was described in which a customer places an order at a restaurant using his or her own mobile terminal 2, but the ordering system 1 may also accept customer orders using an order terminal (not shown) that is placed on each table in the store and operated by the customer, or a handheld terminal (not shown) that is carried and operated by a store staff member, both of which are connected to the store server 5.

[0187] The store server 5 associates orders made by the same customer from the mobile terminal 2, the order terminal, and the handy terminal, and stores and manages them in the same order data 152. Orders received from the mobile terminal 2, the order terminal, and the handy terminal can be associated with each other, for example, by table number. That is, from a table with the same table number, orders made from the mobile terminal 2, the order terminal, and the handy terminal are associated as being orders by the same customer, and are stored in the same order data 152. Alternatively, orders made from the mobile terminal 2, the order terminal, and the handy terminal may be associated with each other by a member ID registered in the member master 33.

[0188] The order ID that identifies an order received from an order terminal or handheld terminal is issued by the store server 5. In contrast, the order ID received from a mobile terminal 2 is issued by the mobile order server 3 as described above. Therefore, when the store server 5 receives an order from an order terminal or handheld terminal, it issues an order ID that is separate from the one issued by the mobile order server 3.

[0189] As described above, orders received from the mobile terminal 2, orders received from the order terminal, and orders received from the handheld terminal are associated in the order data 152 by the table number and member ID. Therefore, regardless of the ordering method, a customer may process the payment after eating and drinking at a POS terminal (not shown) connected to the store server 5, or may use a payment app pre-installed on the mobile terminal 2.

[0190] The ordering system 1 may also detect that an order placed from an order terminal or handheld terminal has been correctly notified to the store server 5 using the method described in the above embodiment. The ordering system 1 may then notify the order terminal or handheld terminal that placed the order that an order placed from the order terminal or handheld terminal has been correctly notified to the store server 5. The ordering system 1 may also notify the customer's mobile terminal 2 that an order placed from the order terminal or handheld terminal has been correctly notified to the store server 5.

[0191] The ordering system 1 can handle any payment method when processing the transaction, such as cash, credit card, prepaid card, electronic money, etc. In particular, when performing a cashless payment that does not involve the receipt and receipt of cash, the store server 5 causes an external server (not shown) to perform the payment process using the specified payment method.

[0192] Although the ordering system 1 has been described as being constructed across a number of different businesses, it may be constructed by the same business.

[0193] Although the embodiments of the present invention have been described above, these embodiments are merely examples and are not intended to limit the scope of the invention. This novel embodiment can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0194] 1. Ordering system (information processing system) 2. Mobile devices 3. Mobile Order Server 4. Relay server (information processing device) 5. Store Server 31 Product Master 32 Store Master 33 Member Master 34,39 Order data 35,38 Order information management file 36 Order Data Header Management File 37 Order Data Body Management File 61 Order Reception Department 62 Order Data Update Section 63 Order data output section 64 Status acquisition unit (order confirmation acquisition unit) 65 Status notification section (reception completion notification section) 66 Communication Check Section 67 Error response section 71 Order Reception Department 72 Invoice Number Issuer 73 Order Data Update Section 74 Order data output section 75 Status notification section 76 Payment Processing Unit 77 Communication Check Section N Network [Prior art documents] [Patent documents]

[0195] [Patent Document 1] Patent No. 6694402

Claims

1. an order receiving unit that receives order data generated based on order information from a mobile terminal or order data from a store server that manages the provision of a service related to the order information; an order data update unit for storing the received order data; an order data output unit that outputs order data based on the order information to the store server; an order confirmation acquisition unit that acquires, from the store server, confirmation information indicating that the order data has been accepted; and a reception completion notifying unit that notifies the mobile terminal that reception of the order information has been completed on condition that the confirmation information has been acquired. Information processing device.

2. when a plurality of pieces of order information are received from the mobile terminal during one transaction, the confirmation information for the order data that is first output to the store server by the order data output unit is a slip number that is issued on the condition that the store server has received the order data, the confirmation information for the order data outputted by the order data output unit to the store server for the second or subsequent time is status information indicating that the store server has accepted the order data; The information processing device according to claim 1 .

3. a communication confirmation unit that receives a communication confirmation signal repeatedly transmitted by the store server; and an error response unit that notifies the mobile terminal of an error response on condition that the communication confirmation unit does not receive the communication confirmation signal.

3. The information processing device according to claim 1 or 2.

4. When the communication confirmation unit cannot confirm communication, the order reception unit does not accept order information from the mobile terminal. The information processing device according to claim 3 .

5. The order confirmation acquisition unit further receives, from the store server, identification information for identifying the order data and error information indicating a reason for failure in accepting the order data; The acceptance completion notification unit further notifies the portable terminal of the identification information and the error information.

3. The information processing device according to claim 1 or 2.

6. An information processing system having a mobile order server that receives order information from a mobile terminal, a store server that manages the provision of services related to the order information, and a relay server that relays between the mobile order server and the store server, The mobile order server receives order information from the mobile terminal, The relay server receives and stores the order data generated based on the order information received by the mobile order server, and notifies the store server of the order data. The store server holds the order data received from the relay server, and notifies the relay server of confirmation information indicating that the order data has been received, The relay server updates the order data based on the confirmation information and notifies the mobile order server of the confirmation information, The mobile order server notifies the mobile terminal of the confirmation information. Information processing system.

7. Computer, an order receiving unit that receives order data generated based on order information from a mobile terminal or order data from a store server that manages the provision of a service related to the order information; an order data update unit for storing the received order data; an order data output unit that outputs order data based on the order information to the store server; an order confirmation acquisition unit that acquires, from the store server, confirmation information indicating that the order data has been accepted; an acceptance completion notifying unit that notifies the mobile terminal that acceptance of the order information has been completed on condition that the confirmation information has been acquired; A program that can be used to

Images