Information processing device, information processing program, and information processing method
The information processing device addresses issues in karaoke store reservation systems by managing customer entry and exit to ensure smooth operations, prevent underage alcohol sales, and facilitate automatic room cleaning and locking, enhancing operational efficiency and security.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2026-04-09
AI Technical Summary
Existing reservation systems in stores like karaoke stores face issues with food delivery by partner companies, fraudulent orders, and lack of customer usage status verification, leading to operational inefficiencies and security risks.
An information processing device with a reception unit, locking control unit, and notification unit that manages reservations, locks/unlocks private rooms, and sends messages based on customer entry and exit, enabling age verification, order acceptance, and payment processing.
Ensures smooth operation of unmanned stores by guiding customers to private rooms, preventing underage alcohol consumption, and allowing automatic room cleaning and locking, thus enhancing operational efficiency and security.
Smart Images

Figure 2026062360000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an information processing apparatus, an information processing program, and an information processing method.
Background Art
[0002] With the development of communication technology, a reservation system is known that connects to the Internet and makes reservations for seats in stores, event venues, etc. via, for example, a website. In this case, a user can make a reservation for a store by accessing a web server device that manages the website using a user terminal such as a personal computer (PC), a smartphone, or a tablet terminal, and inputting the information necessary for the reservation.
[0003] In a karaoke store, a reservation reception, song selection, and ordering system in a karaoke store that enables online confirmation of vacant rooms and reception of reservations, allows users to settle accounts for each user, and eliminates the need for facilities in the kitchen and reception is disclosed (see, for example, Patent Document 1). In Patent Document 1, using a mobile terminal such as a user's mobile phone, it is possible to receive reservations, select songs, and place orders for private rooms in a karaoke store. When a reservation request for a private room in a karaoke store is transmitted from the mobile terminal of a user making a reservation, the reservation request is received, a reservation log is generated and held, and a reservation ticket including a reservation ID for identifying the reservation is transmitted to the mobile terminal. When the user inputs the reservation ID from the input means of the reserved private room, the reservation ID and the reservation log are matched to confirm that it is a proper reservation, and the door of the private room is automatically unlocked. At the end of the usage time, a message requesting the user to leave the room is transmitted and the door is automatically locked.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] However, in Patent Document 1, food is delivered to unmanned stores by partner companies, which may cause problems in cases where the company prepares its own food. Also, since the customer's usage status is not checked when taking orders or payment requests from customers, there is a risk of fraudulent orders and payment processing.
[0006] Therefore, the present invention provides a technology that enables smooth operation of a store where customers reserve and use the store facilities. [Means for solving the problem]
[0007] An information processing device according to one embodiment of the present invention is characterized by comprising: a reception unit that receives reservations from customers regarding the use of a store; a locking control unit that controls the locking or unlocking of private rooms within the store; and a notification unit that notifies the customer's terminal device of a predetermined message based on the customer's entry into the store and the customer's completion of use of the store, as confirmed by the reception of the store based on the reservation.
[0008] The notification unit, upon receiving an order request from the customer, accepts the order based on the customer's entry and exit information regarding the customer's entry into the store and the end of their use of the store. When the preparation of the ordered items is complete, it notifies the customer of a message prompting them to come and pick up the items as they are ready.
[0009] The notification unit, upon receiving an order request from the customer, is characterized in that, based on the customer's entry and exit information regarding the customer's entry into the store and the customer's end of use of the store, if it accepts the order, it determines the customer's age for a given product and notifies the customer of a message indicating that the order for the product cannot be accepted based on the determination result.
[0010] The notification unit is characterized in that, based on the entry and use completion information regarding the customer's entry into the store and the customer's use of the store, it notifies the customer's terminal device whether or not to extend the usage time a predetermined time before the time when the entry and use of the store will end, and if the time when the entry and use of the store will end arrives without accepting a payment request, it updates the entry and use time by a predetermined amount.
[0011] The notification unit, upon receiving an order request from the customer, accepts a payment request based on the customer's entry and end-of-use information, and locks the door to the private room if it receives information that the private room has been cleaned after the payment processing.
[0012] An information processing program in one embodiment of the present invention causes a computer to perform the following: an acceptance process for receiving a reservation from a customer regarding the use of a store; a locking control process for controlling the locking or unlocking of a private room in the store; and a notification process for notifying a predetermined message to the customer's terminal device based on the customer's entry into the store and the customer's end of use of the store, as confirmed by the acceptance of the reservation into the store.
[0013] In an information processing method according to one embodiment of the present invention, a computer performs the following: reception processing for receiving a reservation from a customer regarding the use of a store; locking control processing for controlling the locking or unlocking of a private room in the store; and notification processing for notifying a predetermined message to the customer's terminal device based on the customer's entry into the store and the customer's end of use of the store, as confirmed by the reception of the store based on the reservation. [Effects of the Invention]
[0014] According to the present invention, operations can be carried out smoothly in an unmanned store where customers reserve and use the store facilities. [Brief explanation of the drawing]
[0015] [Figure 1] This figure illustrates the overview of an information processing device in an embodiment of the present invention. [Figure 2] It is a diagram showing an example of the overall configuration of the store management system in this embodiment. [Figure 3] It is a functional block diagram of the store management server in this embodiment. [Figure 4] It is a diagram showing an example of the data structure of the database managed by the store management server in this embodiment. [Figure 5] It is a diagram showing the overall flow in this embodiment. [Figure 6] It is a diagram showing an example of the order reception screen in this embodiment. [Figure 7] It is a diagram showing an example of the cart confirmation screen in this embodiment. [Figure 8] It is a diagram showing an example of the order history screen in this embodiment. [Figure 9] It is a diagram showing an example of the call screen in this embodiment. [Figure 10] It is a sequence diagram of user registration in this embodiment. [Figure 11] It is a sequence diagram of the reception procedure performed when a customer visits the store in this embodiment. [Figure 12] It is a sequence diagram of order processing in this embodiment. [Figure 13] It is a sequence diagram from accounting processing to cleaning in this embodiment. [Figure 14] It is a diagram showing the reception processing flow by the store management server 12 in this embodiment. [Figure 15] It is a diagram showing the order reception processing flow in this embodiment. [Figure 16] It is a flowchart showing an example of the usage time extension processing by the store management server 12 in this embodiment. [Figure 17] It is a flowchart showing an example of the processing from receiving an accounting request by the store management server 12 to locking up in this embodiment. [Figure 18] It is a flowchart showing another embodiment of the process of S80 in FIG. 15. [Figure 19] This is an example of a block diagram showing the configuration of the hardware environment of a computer that runs the program in this embodiment. [Modes for carrying out the invention]
[0016] Figure 1 is a diagram illustrating the overview of an information processing device in an embodiment of the present invention. The information processing device 1 includes a reception unit 2, a locking control unit 3, and a notification unit 4. An example of the information processing device 1 is the store management server 12, which will be described later.
[0017] Reception Unit 2 accepts reservations from customers regarding the use of the store. An example of Reception Unit 2 is the reservation processing unit 32. The store may be, for example, an unmanned store (including cases where only the reception is unmanned). However, the store may also be a staffed store. Furthermore, the store may be a private room such as a karaoke box, or a restaurant.
[0018] The locking control unit 3 controls the locking or unlocking of the private rooms within the store. An example of the locking control unit 3 is the locking management unit 36. Here, in order to remotely operate the locking or unlocking of the private rooms, for example, an external locking / unlocking device such as a so-called smart lock for controlling the rotation of the thumbturn may be installed on the inside (room side) of the private room door, or a locking / unlocking device in which the smart lock is built into the door may be installed.
[0019] The notification unit 4 notifies the customer's terminal device of a predetermined message based on the customer's entry into the store and the completion of their use of the store, as confirmed by the reservation. An example of a terminal device is the user terminal 14, which will be described later. Notifying the customer's terminal device of a predetermined message also includes displaying the predetermined message on the customer's terminal device. The notification unit 4 may also be a display control unit that displays the predetermined message on the customer's terminal device. The predetermined message includes various messages in this embodiment.
[0020] This configuration allows for smooth operation in unmanned stores where customers make reservations to use the store facilities. In other words, it is possible to guide reserved customers to private rooms within the store without human intervention and provide them with various services based on predetermined messages.
[0021] When a customer places an order, the notification unit 4 accepts the order based on the customer's entry and exit information regarding their time in the store. Once the ordered items are ready, it notifies the customer with a message prompting them to come and pick up their items.
[0022] By configuring the system in this way, it becomes possible to call customers to come and pick up their ordered items, eliminating the need to have serving staff on hand. This allows for smooth operation in unmanned stores where customers reserve and use the store facilities.
[0023] When a customer places an order, the notification unit 4, based on the customer's entry and exit information regarding their entry into the store and the end of their use of the store, will determine the customer's age for the specified product and, based on the determination result, notify the customer that the order for the product cannot be accepted.
[0024] By configuring the system in this way, alcoholic beverages can be served only after age verification, thus preventing underage alcohol consumption at unmanned stores.
[0025] Based on the entry and end-of-use information regarding the customer's entry into the store and the end of the customer's use of the store, the notification unit 4 notifies the customer's terminal device whether or not to extend the usage time a predetermined time before the time of entry and end-of-use. If the time of entry and end-of-use arrives without accepting a payment request, the notification unit 4 updates the entry and end-of-use time by a predetermined amount.
[0026] By configuring the system in this way, even if a customer does not respond to a notification about whether or not they wish to extend their usage time, if they do not indicate their intention to pay by the scheduled end time, it will be considered an indication of their intention to extend, and the usage time will be automatically extended, allowing for smooth business operations.
[0027] When a customer places an order, the notification unit 4 accepts the payment request based on the information regarding the customer's entry into the store and the end of their use of the store. After processing the payment, if it receives information that the private room has been cleaned, it locks the door to the private room.
[0028] This configuration allows for cleaning and locking of the private rooms after each use. For example, even if the cleaning of the private rooms is outsourced to an external company, the rooms can be cleaned and locked after each use, enabling smooth business operations.
[0029] Embodiments of the present invention will be described below with reference to the drawings.
[0030] Figure 2 shows an example of the overall configuration of the store management system in this embodiment. The store management system 11 includes a store management server 12, a smart lock management server 13, a user terminal 14, a communication network 15, a reception terminal 23, a smart lock 24, an order management terminal 25, and a wireless router 28. The store management server 12, the smart lock management server 13, and the user terminal 14 are connected to the communication network 15 by wireless or wired connections. The reception terminal 23, the smart lock 24, and the order management terminal 25 are also connected to the communication network 15 via the wireless router 28 through a wireless or wired LAN (Local Area Network).
[0031] The store management server 12 manages store reservations, manages orders from store users, controls the locking and unlocking of smart locks 24 that lock and unlock the store's private rooms, and manages accounting. The smart lock management server 13 is a server that controls the locking or unlocking of smart locks based on instructions from the store management server 12.
[0032] The store management server 12 and the smart lock management server 13 may each be a server system composed of one or more physical information processing devices, or a virtual server system composed of one or more virtual server devices. Furthermore, the store management server 12 may include the smart lock management server 13.
[0033] Store 21 is a store that primarily has cooks but no one to handle reception or other operations (hereinafter sometimes referred to as an "unmanned store"). Store 21 is a store with multiple private rooms 22, such as a karaoke box. In Store 21, a reception terminal 23 is installed at the entrance. Smart locks 24 are installed on the doors of the private rooms 22 to lock and unlock the rooms. The smart lock 24 is installed on the inside of the door and controls the rotation of the thumbturn on the inside of the door via wireless communication to control locking and unlocking.
[0034] Furthermore, store 21 is equipped with a kitchen 27, and an order management terminal 25 is installed in the kitchen 27. A cook is on standby in the kitchen 27. When a cooking instruction is received via the order management terminal 25, the cook prepares the food according to the instruction, and once the cooking is complete, the cook enters "cooking complete" into the order management terminal 25.
[0035] The order management terminal 25 is used to transmit orders received by the store management server 12 to the cooks in the kitchen 27, and to notify the customers who placed orders when cooking is complete, instructing them to come to the handover counter 26 to pick up their orders. In this embodiment, the order management terminal 25 is used to confirm and manage order information received from customers. The order management terminal 25 may be, for example, a personal computer (PC), a smartphone, or a tablet device.
[0036] User terminal 14 is, for example, an information and communication terminal with communication and imaging functions owned or occupied by a user who has reserved store 21, and includes, for example, a personal computer (PC), a smartphone, and a tablet computer. User terminal 14 has an application program installed that reads and analyzes two-dimensional codes.
[0037] Figure 3 is a functional block diagram of the store management server 12 in this embodiment. The store management server 12 includes a control unit 31 and a storage unit 41. The control unit 31 functions as a reservation processing unit 32, a reception management unit 33, an order processing unit 34, an accounting processing unit 35, and a locking management unit 36 by reading and executing the program in this embodiment.
[0038] The reservation processing unit 32 receives reservations from customers who wish to use the store 21 and manages the received reservations. The reservation processing unit 32 also handles user registration and identity verification processes.
[0039] The reception management department 33 handles reception processing (check-in processing) for customers who have arrived based on accepted reservations, confirms whether they wish to extend their usage time when their pre-booked usage time is about to end, and processes extensions of usage time.
[0040] The order processing unit 34 receives an order request for goods (food, beverages, etc.) from the user terminal 14, accepts the order, and processes the order by displaying the order instructions on the order management terminal 25. When the order management terminal 25 reports that the cooking is complete, it sends a message to the user terminal 14 informing it that the ordered goods are ready and that it should come to the handover counter 26 to pick them up.
[0041] The accounting processing unit 35 receives a settlement request from the user terminal 14, transmits the settlement information to the POS (Point of Sales) system, and performs the settlement process. After the settlement process, the accounting processing unit 35 also notifies the cleaning staff's terminal of the request to clean the private room used by the user who made the settlement.
[0042] The locking management unit 36 controls the locking or unlocking of the smart lock 24 installed on the door of the private room 22 via the API (Application Programming Interface) of the smart lock management server 13, in response to instructions from the reception management unit 33.
[0043] In this embodiment, the storage unit 41 stores a customer management DB 42, a reservation management DB 43, a private room management DB 44, a smart lock management DB 45, and an order management DB 46. The customer management DB 42 is a database that manages information about customers (users) (including identity verification information). The reservation management DB 43 is a database that manages information about reservations from customers who wish to use the store. The private room management DB 44 is a database that manages information about private rooms that are actually used in the store 21. The smart lock management DB 45 is a database that manages smart locks installed on the doors of each private room. The order management DB 46 is a database that manages orders received from users.
[0044] Figure 4 shows an example of the data structure of the database managed by the store management server 12 in this embodiment. Note that each piece of information (each record) managed in the customer management DB 42 may be referred to as customer management information. Each piece of information (each record) managed in the reservation management DB 43 may be referred to as reservation management information. Each piece of information (each record) managed in the private room management DB 44 may be referred to as private room management information. Each piece of information (each record) managed in the smart lock management DB 45 may be referred to as smart lock management information. Each piece of information (each record) managed in the order management DB 46 may be referred to as order management information.
[0045] The customer management DB42 includes data items such as "User ID," "App ID," "Identity Verification Decision," and "Customer Information." The "User ID" item stores information (User ID) that identifies the customer (user). The "App ID" item stores information (App ID) that identifies the application software (hereinafter sometimes referred to as "App") that the customer uses to make reservations at stores. The "Identity Verification Decision" item stores "Identity Verified" if the identity verification was successful, and "Identity Verification Not Completed" if the identity verification was unsuccessful. The "Customer Information" item stores information about the customer (for example, the customer's name, date of birth, address, telephone number, email address, etc.).
[0046] The reservation management DB43 includes data items such as "Store Number," "User ID," "Reservation Date and Time," "Scheduled Usage Time," and "Number of People." The "Store Number" item stores the store identification number. The "User ID" item stores customer identification information (User ID). The "Reservation Date and Time" item stores the desired date and time for using the store. The "Scheduled Usage Time" item stores the time to be used on the reservation date. The "Number of People" item stores the number of people using the service.
[0047] The private room management DB44 includes data items such as "Store Number," "Room Number," "Start Date and Time of Use," "Scheduled Time of Use," "User ID," "Number of People," "Entry Flag," "Exit Flag," "Accounting Flag," and "Receipt Number." The "Store Number" field stores the store identification number. The "Room Number" field stores the room identification number for the private room in that store. The "Start Date and Time of Use" field stores the date and time when the private room will be used. The "Scheduled Time of Use" field stores the time the room will be used. The "User ID" field stores the customer identification information (User ID). The "Number of People" field stores the number of people using the room. The "Entry Flag" field stores information indicating whether the customer has entered the store (not entered, entered). The "Exit Flag" field stores information indicating whether the customer has left the store (not left, left). The "Accounting Flag" field stores information regarding the accounting status (not yet paid, paying in progress, paid). The "Invoice Number" field stores the invoice number for the customer's transaction in question. The "Invoice Number" field also contains other information related to the charges subject to payment, such as the order details.
[0048] The smart lock management DB45 includes data items such as "Store Number," "Room Number," "Smart Lock ID," and "Lock / Unlock Flag." The "Store Number" item stores the store identification number. The "Room Number" item stores the room identification number for that store. The "Smart Lock ID" item stores the smart lock identification number. The "Lock / Unlock Flag" item stores information indicating whether the smart lock is locked or unlocked.
[0049] The order management DB46 includes data items such as "Store Number," "Invoice Number," "Product," and "Order Flag." The "Store Number" field stores the store identification number. The "Invoice Number" field stores the unique invoice number. The "Product" field stores the name of the ordered product. The "Order Flag" field stores whether the order is not called (default), in progress, or called.
[0050] Figure 5 shows the overall flow in this embodiment. A customer (user) who wishes to use store 21 first downloads and installs the application according to this embodiment on the user terminal 14. The user launches the application on the user terminal 14 and follows the instructions displayed on the screen to complete user registration and identity verification procedures (S1). After that, the user uses the application on the user terminal 14 to make a reservation for store 21 (S2).
[0051] The user visits the store on the day of their reservation and checks in (S3). A private room 22 that matches the reservation details is then determined, and the smart lock on that private room 22 is unlocked (S4). The user enters the private room 22 and begins using it.
[0052] The user places an order for food and drinks while using the private room 22 using the user terminal 14 (S5). Upon receiving the order, the order instructions are notified to the order management terminal 25 in the store. The cook who sees the notification prepares the ordered items. When the preparation of the ordered items is complete, a message is sent to the user terminal 14 to call for pickup (S6). The user then goes to the pickup counter 26 to collect the items.
[0053] As the end of the usage time approaches, the user operates the user terminal 14 to request payment (settlement) (S7). Payment is made using, for example, a pre-registered credit card. Once the payment process is complete, a message stating "Payment process complete. We look forward to your next visit." is displayed on the user terminal 14. The user then leaves the store.
[0054] After the accounting process is complete and the user leaves the store, a notification is sent to the cleaning staff's terminal 29 requesting that the used private room 22 be cleaned. Upon receiving the notification, the cleaning staff cleans the private room 22 and reports the completion of the cleaning (S8). At that point, the smart lock 24 of the private room 22 is locked (S9).
[0055] Figure 6 shows an example of an order acceptance screen in this embodiment. When a customer (user) launches the application in this embodiment and performs a predetermined operation, the order acceptance screen 51 is displayed on the screen of the user terminal 14.
[0056] The order acceptance screen 51 includes a store name display field 52, a user ID display field 53, a category selection button 54, a product image display field 55 (55a, 55b, ...), an add product button 56 (56a, 56b, ...), a delete product button 57 (57a, 57b, ...), a total amount display field 58, and a "Check Cart" button 59.
[0057] The store name display field 52 displays the store name of store 21. The user ID display field 53 displays the user ID sent from the user terminal 14. When the category selection button 54 is selected (pressed), images of one or more products corresponding to the pressed category are displayed in the product image display field 55 (55a, 55b, ...).
[0058] The product image display area 55 (55a, 55b, ...) displays images of products belonging to the category selected by the category selection button 54. Pressing the add product button 56 (56a, 56b, ...) adds the product displayed in the product image display area 55 (55a, 55b, ...) to the cart. Here, the cart refers to the electronic space where products added by the user using the add product button 56 (56a, 56b, ...) are temporarily stored until payment is completed. Tapping the delete product button 57 (57a, 57b, ...) removes the product displayed in the product image display area 55 (55a, 55b, ...) that has been added to the cart.
[0059] The total amount display field 58 shows the total amount of the items added to the cart. Tapping the "Check Cart" button 59 will take you to the screen shown in Figure 7, where you can check the items added to your cart.
[0060] Figure 7 shows an example of the shopping cart confirmation screen in this embodiment. The shopping cart confirmation screen 61 includes a store name display field 62, a user ID display field 63, a list of items in the cart 64, a "back" button 65, and an "order" button 66.
[0061] The store name display field 62 displays the store name of store 21. The user ID display field 63 displays the user ID sent from the user terminal 14. The shopping cart product list 64 displays the details of the products added to the cart, along with their subtotals, consumption tax, and total amount. Pressing the "Back" button 65 returns to the order acceptance screen 51 (Figure 6). Pressing the "Order" button 66 confirms the order and sends the order information to the store management server 12.
[0062] Figure 8 shows an example of the order history screen in this embodiment. The customer (user) can operate the user terminal 14 to transition from the order acceptance screen 51 to the order history screen 71.
[0063] The order history screen 71 includes a store name display field 72, a user ID display field 73, a list of ordered items 74, a "back" button 75, and a "checkout" button 76.
[0064] The store name display field 72 displays the store name of store 21. The user ID display field 73 displays the user ID sent from the user terminal 14. The ordered items list 74 displays the details of the ordered items, their subtotal, consumption tax, and total amount. Pressing the "Back" button 75 returns to the cart confirmation screen 61 (Figure 7). Pressing the "Checkout" button 76 sends facility usage fee information and order history information to the store management server 12, which then sends the facility usage fee information and order history information to the POS system as checkout information.
[0065] Figure 9 shows an example of a call screen in this embodiment. The call screen 81 in Figure 9 shows an example of how it is displayed in the chat application's display format. On the call screen 81, a message such as "Your order is ready. Please come to the pickup counter to pick it up. Call number: 1121" is sent from the store management server 12 and displayed.
[0066] At the handover counter 26, the product (food or beverage) with the assigned call number is prepared. The user who sees the notification message goes to the handover counter 26 to pick up the product.
[0067] Figure 10 is a sequence diagram of user registration in this embodiment. The user accesses the store management server 12 using the user terminal 14 (S11). The store management server 12 establishes a connection by responding to the access (S12).
[0068] The user enters their personal information (name, date of birth, contact information, etc.) using the user terminal 14 (S13). The store management server 12 responds to the user terminal 14 that it has finished acquiring the personal information (S14). The user takes a photo of their face using the imaging function of the user terminal 14 and sends it to the store management server 12 (S15). The store management server 12 responds to the user terminal 14 that it has finished acquiring the face photo (S16). The user takes a photo of their identification document (for example, driver's license, My Number card, residence card, basic resident register card, special permanent resident certificate, driver's history certificate, passport, etc.) using the imaging function of the user terminal 14 and sends it to the store management server 12 (S17). The store management server 12 responds to the user terminal 14 that it has finished acquiring the identification document (S18).
[0069] The store management server 12 determines whether the acquired facial photograph and the facial photograph on the identification document belong to the same person. If it is determined that the acquired facial photograph and the facial photograph on the identification document do not belong to the same person, the store management server 12 notifies the user terminal 14 that identity verification cannot be completed and prompts the user to take another facial photograph and a photograph of the identification document. If it is determined that the acquired facial photograph and the facial photograph on the identification document belong to the same person, the store management server 12 notifies the user terminal 14 that identity verification is complete (S19). The user then uses the user terminal 14 to enter reservation information (store to be reserved, reservation date and time, planned usage time, number of people, etc.) (S20). The store management server 12 responds to the user terminal 14 that the reservation has been accepted (S21).
[0070] Figure 11 is a sequence diagram of the check-in procedure performed when a customer visits the store in this embodiment. Here, it is assumed that the user has made a reservation for the store 21 in advance. When the user visits the store 21, they perform a check-in operation using the check-in terminal 23 (S31). In the check-in operation, the user inputs the reservation name, telephone number, or a reservation number issued in advance as check-in information to the check-in terminal 23. The check-in terminal 23 transmits the check-in information to the store management server 12 (S32).
[0071] When the store management server 12 receives the reception information, it searches for an available private room that matches the reservation information from the inventory information of available private rooms and determines which private room to assign to the user. The store management server 12 requests the smart lock management server 13 to unlock the smart lock 24 of the determined private room (S33). The smart lock management server 13 sends an unlocking instruction to the smart lock 24 of the determined private room (S34). The smart lock 24 of the determined private room performs the unlocking process based on the unlocking instruction and sends a notification of completion of unlocking to the smart lock management server 13 (S35).
[0072] The smart lock management server 13 reports to the store management server 12 that the smart lock 24 of the selected private room has been unlocked (S36). The store management server 12 notifies the reception terminal 23 of the room number (store number, room number) of the selected private room (S37). The reception terminal 23 displays the room number to be used by the user who made the reservation. The store management server 12 also notifies the user terminal 14 of the store number, room number, and receipt number (S38).
[0073] Figure 12 is a sequence diagram of the order processing in this embodiment. The user operates the user terminal 14 to display the order acceptance screen 51. The user terminal 14 then sends an order acceptance screen display request (user ID (or application ID), store number, room number) to the store management server 12. When the store management server 12 receives the order acceptance screen display request (user ID (or application ID)), it displays the order acceptance screen 51 on the screen of the user terminal 14 (S42).
[0074] The user operates the user terminal 14 to place an order for food and beverages via the order acceptance screen 51 and the cart confirmation screen 61, and then confirms the order by pressing the "Order" button 66 (S43). The user terminal 14 then sends the order information (user ID (or app ID), store number, room number, product ID) to the store management server 12.
[0075] The store management server 12 sends cooking instructions to the order management terminal 25 based on the order information received from the user terminal 14 (S44). The order management terminal 25 responds to the store management server 12 that it has received the cooking instructions (S45). The store management server 12 sends a message to the user terminal 14 that it has received the order (S46).
[0076] The cook prepares the food based on the cooking instructions displayed on the order management terminal 25. After cooking is complete, the cook carries the prepared food to the handover counter 26 and enters "cooking complete" into the order management terminal 25. The order management terminal 25 then sends the cooking complete message to the store management server 12 (S47). The store management server 12 sends a call message to the user terminal 14 of the customer who placed the order (S48).
[0077] Figure 13 is a sequence diagram from accounting processing to cleaning in this embodiment. The user operates the user terminal 14 and presses the "Settlement" button 76 on the order history screen 71 to request accounting (S51). The user terminal 14 then sends the accounting request (user ID (or app ID), store number, room number) to the store management server 12. The store management server 12 performs accounting processing (settlement processing) in response to the accounting request and notifies the user terminal 14 that accounting is complete (S52).
[0078] After accounting processing, the store management server 12 notifies the cleaning staff's terminal 29 of the cleaning request for the private room (room number) for which accounting processing was performed (S53). The cleaning staff's terminal 29 receives the cleaning request from the store management server 12. The cleaning staff member uses the terminal 29 to confirm the details of the request and uses the terminal 29 to respond to the store management server 12 that they will clean the target private room (S54). After cleaning is completed, the cleaning staff member's terminal 29 notifies the store management server 12 that cleaning is complete (S55).
[0079] The store management server 12 notifies the smart lock management server 13 of a locking request for the smart lock 24 installed in the private room 22 for which a cleaning completion report has been received (S56). When the smart lock management server 13 receives the locking request from the store management server 12, it sends a locking instruction to the smart lock 24 in question (S57). The smart lock 24 performs the locking process based on the locking instruction from the smart lock management server 13 and sends a locking completion notification to the smart lock management server 13 (S58). The smart lock management server 13 reports the locking completion to the store management server 12 (S59). The store management server 12 then notifies the terminal 29 of the locking completion based on that notification (S60).
[0080] Figure 14 shows the reception processing flow by the store management server 12 in this embodiment. When the store management server 12 receives a reception operation from the reception terminal 23 (S61), it determines a private room that meets the reservation conditions from the inventory information of available private rooms in the store (S62).
[0081] The store management server 12 obtains the smart lock ID of the smart lock 24 corresponding to the private room determined from the smart lock management DB 45. The store management server 12 requests the smart lock management server 13 to unlock the smart lock 24 with the obtained smart lock ID (S63).
[0082] After the smart lock management server 13 has processed the unlocking of the smart lock 24, the store management server 12 receives from the smart lock management server 13 that the smart lock 24 with that smart lock ID has been unlocked (S64). The store management server 12 changes the entry flag of the record in the private room management DB 44 corresponding to the room number of the private room 22 determined for that store from "Not entered" to "Entered," and changes the lock / unlock flag of the record in the smart lock management DB 45 corresponding to that smart lock ID from "Locked" to "Unlocked" (S65). The store management server 12 notifies the reception terminal 23 and the user terminal 14, respectively, of the room number of the private room 22 determined for that store (S66).
[0083] Figure 15 shows the order acceptance processing flow in this embodiment. The store management server 12 obtains an order screen display request (user ID (or app ID), store number, room number, slip number) from the user terminal 14 (S71).
[0084] The store management server 12 retrieves a record corresponding to the combination of store number and room number from the private room management DB 44 based on the order screen display request, and determines whether the entry flag of the retrieved record is "entered" or not (S72). If the entry flag of the retrieved record is "not entered" (NO in S72), the store management server 12 displays "Not available before entering" on the user terminal 14 (S73).
[0085] If the entry flag of the acquired record is "Entered" (YES in S72), the store management server 12 determines whether the exit flag of the acquired record is "Not Exited" or not (S74). If the exit flag is "Exited" (NO in S74), the store management server 12 displays "Cannot be used after exiting" on the user terminal 14 (S75).
[0086] If the store departure flag is "not yet left" (YES in S74), the store management server 12 displays the order acceptance screen 51 on the user terminal 14's display unit (S76). The store management server 12 remains in a waiting state until it receives an order request from the user terminal 14 (NO in S77).
[0087] The user operates the user terminal 14 to place an order for food and beverages via the order acceptance screen 51 and the cart confirmation screen 61, and then confirms the order by pressing the "Order" button 66. The user terminal 14 then sends the order information (user ID (or app ID), store number, room number, product ID) to the store management server 12.
[0088] When the store management server 12 receives an order request from the user terminal 14 (YES in S77), it determines whether the accounting flag of the acquired record is "in accounting" (S78). If the accounting flag is "in accounting" (YES in S78), the store management server 12 notifies the user terminal 14 with the message, "We are currently processing your order, so you cannot place an order now." This message is displayed on the display unit of the user terminal 14 (S84).
[0089] If the accounting flag is not "Accounting in Progress" (NO in S78), the store management server 12 determines whether there are M (M: integer) minutes remaining until the scheduled end time of use (= reservation time + scheduled usage time) (S79). M is, for example, 5 minutes, 10 minutes, 15 minutes, etc.
[0090] If there is more than M (an integer) minutes remaining until the scheduled end time of use (NO in S79), the store management server 12 processes the order based on the order request received from the user terminal 14 (S80). That is, the store management server 12 registers the order information based on the order request in the order management DB 46. At this time, the order flag is registered as "Order in progress". Based on the order request, the store management server 12 sends cooking instructions to the order management terminal 25.
[0091] The order management terminal 25 responds to the store management server 12 that it has received the cooking instructions. The store management server 12 sends a message to the user terminal 14 confirming that the order has been received. The cook prepares the food based on the cooking instructions displayed on the order management terminal 25. After cooking is complete, the cook carries the prepared food to the handover counter 26 and enters "cooking complete" into the order management terminal 25. The order management terminal 25 then sends the cooking complete message to the store management server 12. The store management server 12 sends a call message to the user terminal 14 of the customer who placed the order.
[0092] The store management server 12 waits until it receives a cooking completion report from the order management terminal 25 (NO in S81). When it receives a cooking completion report from the order management terminal 25 (YES in S81), the store management server 12 notifies the user terminal 14 with the message, "Your order is ready. Please come to the pickup counter. Call number: 1121" (S82). The call screen 81 displayed on the user terminal 14 shows this message. The store management server 12 changes the order flag for the product in the order management DB 46 from "Ordered" to "Called" (S83).
[0093] If there are M (integer) minutes remaining until the scheduled end time (YES in S79), the store management server 12 sends the message "You have M minutes left until the end time. Would you like to place an order?" to the user terminal 14 (S85). This message is displayed on the display unit of the user terminal 14.
[0094] The store management server 12 receives a response from the user terminal 14 (S86). If the response received from the user terminal 14 is "I will place an order" (YES in S87), the store management server 12 performs the process in S80. If the response received from the user terminal 14 is "I will not place an order" (NO in S87), this flow ends.
[0095] Figure 16 is a flowchart showing an example of the usage time extension process performed by the store management server 12 in this embodiment. This flow is executed repeatedly on a record-by-record basis in the private room management DB 44 and at predetermined time intervals (for example, in units of a few milliseconds, a few seconds, etc.).
[0096] The store management server 12 retrieves one record from the private room management DB 44 (S90). The store management server 12 determines whether the entry flag of the retrieved record is "entered" or not (S91). If the entry flag is "not entered" (NO in S91), the store management server 12 processes the next record.
[0097] If the entry flag of the retrieved record is "Entered" (YES in S91), the store management server 12 determines whether the exit flag of the retrieved record is "Not Exited" or not (S92). If the exit flag of the retrieved record is "Exited" (NO in S92), the store management server 12 processes the next record.
[0098] If the exit flag for the retrieved record is "not exited" (YES in S92), the store management server 12 compares the time obtained by adding the "scheduled usage time" to the "start date and time of use" of the retrieved record (scheduled end time of use) with the current time and determines whether the current time is N (N: integer) minutes before the scheduled end time of use (S93). N minutes can be, for example, 5 minutes, 10 minutes, 15 minutes, etc.
[0099] If the current time is within N (integer) minutes of the scheduled end time (NO in S93), the store management server 12 processes the next record. If the current time is within N (integer) minutes of the scheduled end time (YES in S93), the store management server 12 displays "Your usage time will end in N minutes. Do you want to extend your usage time?" on the display of the user terminal 14 (S94). If the user chooses to extend, they can operate the user terminal 14 to specify how much time to extend (for example, 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, 90 minutes, 120 minutes, etc.).
[0100] If the store management server 12 receives an instruction from the user terminal 14 not to extend the time (NO in S95), it displays a message on the user terminal 14's display screen stating, "When your time is up, please press the "Checkout" button and leave the premises." (S96). After that, it processes the next record as described in S90.
[0101] If the store management server 12 receives an instruction from the user terminal 14 to extend the time (including the store number, room number, and information on how long to extend the time (for example, 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, 90 minutes, 120 minutes, etc.)) (YES in S95), it performs the extension process (S97). Here, the store management server 12 updates the scheduled usage time of the corresponding record in the private room management DB 44 based on the store number, room number, and information on how long to extend the time. After that, the store management server 12 notifies the user terminal 14 that the time has been extended (S98).
[0102] Furthermore, if the user terminal 14 does not respond in S96 either to extend the time or not to extend it, and the scheduled end time of use has arrived but no payment request has been made from the user terminal 14, the time will be automatically extended by a predetermined time (for example, 10 minutes, 20 minutes, 30 minutes, 60 minutes, etc.), and processing in S97 and S98 will be performed.
[0103] Figure 17 is a flowchart illustrating an example of the process from receiving a payment request by the store management server 12 to locking the door in this embodiment. The user presses the "Pay" button 76 on the order history screen 71 displayed on the user terminal 14. The user terminal 14 then sends a payment request (user ID (or app ID), store number, room number, receipt number) to the store management server 12.
[0104] The store management server 12 receives an accounting request (user ID (or application ID), store number, room number, receipt number) from the user terminal 14 (S101). Based on the accounting request, the store management server 12 retrieves a record from the private room management DB 44 that corresponds to the combination of store number and room number.
[0105] The store management server 12 determines whether the entry flag of the acquired record is "entered" or not (S102). If the entry flag of the acquired record is "not entered" (NO in S102), the store management server 12 displays "Cannot be used before entering the store." on the display of the user terminal 14 (S103). Then, this flow ends.
[0106] If the entry flag of the acquired record is "Entered" (YES in S102), the store management server 12 determines whether the exit flag of the acquired record is "Not Exited" or not (S104). If the exit flag of the acquired record is "Exited" (NO in S104), the store management server 12 displays "Cannot be used after exiting the store." on the display unit of the user terminal 14 (S105).
[0107] If the exit flag of the retrieved record is "not exited" (YES in S104), the store management server 12 determines whether or not there are any items on order (S106). Here, the store management server 12 searches the order management DB 46 for items with an order flag of "on order" based on the store number and slip number.
[0108] If there are items on order (YES in S106), the store management server 12 displays "There are items on order. Would you like to proceed with payment?" on the display of the user terminal 14 (S107).
[0109] If the user terminal 14 responds that it will not pay (NO in S108), this flow ends. If the user terminal 14 responds that it will pay (YES in S108), the store management server 12 displays "When you leave the store, please pick up your items at the handover counter." on the display of the user terminal 14 (S109). Then, the process proceeds to S110.
[0110] If there are no items in the order (NO in S106), the store management server 12 performs accounting processing (S110). Here, the store management server 12 performs accounting processing (settlement processing) based on the order information and usage time information linked to the slip number, and performs payment processing based on the pre-registered credit card information.
[0111] After accounting processing, the store management server 12 changes the exit flag of the acquired record from "not yet exited" to "exited" (S111). The store management server 12 displays "Accounting processing is complete" on the display of the user terminal 14 (S112).
[0112] The store management server 12 displays a cleaning request (including store number and room number) for the private room 22 for which the accounting process has been completed on the display unit of the cleaning staff's terminal 29 (S113). The store management server 12 remains in a waiting state (NO in S114) until it receives a cleaning completion report from the cleaning staff's terminal 29.
[0113] When the store management server 12 receives a cleaning completion report (including the store number and room number) from the cleaning staff's terminal 29 (YES in S114), it retrieves the smart lock ID corresponding to that store number and room number combination from the smart lock management DB 45. The store management server 12 then requests the smart lock management server 13 to lock the smart lock 24 corresponding to the retrieved smart lock ID (S115).
[0114] When the smart lock management server 13 receives a locking request from the store management server 12, it sends a locking instruction to the smart lock 24. The smart lock 24 performs the locking process based on the locking instruction from the smart lock management server 13 and sends a locking completion message to the smart lock management server 13. The smart lock management server 13 then sends a locking completion report to the store management server 12.
[0115] When the store management server 12 receives a locking completion report from the smart lock management server 13 (S116), it changes the lock / unlock flag of the record corresponding to the smart lock ID in the smart lock management DB 45 from "unlocked" to "locked" (S117). The store management server 12 displays "locking complete" on the display unit of the terminal 29 (S118).
[0116] Next, we will explain the procedures for ordering alcoholic beverages. Since the premise is that orders are not handed over face-to-face by intermediaries, it is necessary to ensure that alcoholic beverages are not sold to minors.
[0117] Figure 18 is a flowchart showing another embodiment of the process in S80 of Figure 15. The store management server 12 determines whether or not the received order contains alcohol (S121).
[0118] If the received order does not include alcohol (NO in S121), the store management server 12 processes the order (S124). At this time, the store management server 12 registers the order date and time, slip number, and product ID in the order management system (not shown) and notifies the order management terminal 25 of the cooking instructions for the ordered products. The store management server 12 waits until the order management terminal 25 reports that the cooking is complete (NO in S81 in Figure 15).
[0119] If the accepted order includes alcohol (YES in S121), the store management server 12 determines whether the customer is under 20 years old (S122). The store management server 12 uses the user ID (or app ID) included in the order request to identify the user from the customer management DB 42 and obtains the age from the identified user's date of birth. The store management server 12 then determines whether the obtained age is equal to or greater than a predetermined age (for example, 20 years old).
[0120] If the acquired age is above a specified age (for example, 20 years old) (NO in S122), the store management server 12 processes the order (S124). At this time, the store management server 12 registers the order date and time, slip number, and product ID in the order management system (not shown) and notifies the order management terminal 25 of the cooking instructions for the ordered products. The store management server 12 waits until the order management terminal 25 reports that the cooking is complete (NO in S81 in Figure 15).
[0121] If the age obtained is below a specified age (for example, 20 years old) (YES in S122), the store management server 12 notifies the user terminal 14 display with the message, "We cannot sell alcoholic beverages to minors. Please place your order again." (S123). In this case, the flow in Figure 15 also ends.
[0122] Figure 19 is an example of a block diagram of the hardware environment of a computer that executes the program in this embodiment. Computer 121 may be a store management server 12, a web server (not shown), a user terminal 14, or any other terminal. Computer 121 consists of a CPU 122, ROM 123, RAM 124, storage device 125, input I / F 126, output I / F 127, communication I / F 128, reader 129, and bus 130.
[0123] Here, CPU refers to the central processing unit. ROM refers to read-only memory. RAM refers to random access memory. I / F refers to the interface. The bus 130 may be connected to the CPU 122, ROM 123, RAM 124, storage device 125, input I / F 126, output I / F 127, communication I / F 128, and optionally a reader 129.
[0124] The CPU 122 reads the program according to this embodiment from the storage device 125 and, for example, when functioning as a store management server 12, executes the program as a reservation processing unit 32, reception management unit 33, order processing unit 34, accounting processing unit 35, and locking management unit 36. ROM 123 is read-only memory. RAM 124 is memory for temporary storage.
[0125] The storage device 125 is a device for storing large amounts of information. Various types of storage devices can be used as the storage device 125, such as hard disks, solid-state drives (SSDs), and flash memory cards. For example, when functioning as the storage unit 41 of the store management server 12, the storage device 125 stores programs according to the embodiment of the present invention and various data stored in the storage unit 41.
[0126] Input I / F126 can be connected to input devices such as keyboards, mice, electronic cameras, webcams, microphones, scanners, sensors, tablets, touch panels, and information reading devices. Output I / F127 can be connected to output devices such as displays, touch panels, projectors, printers, and speakers.
[0127] Communication I / F 128 is an interface such as a port for connecting to a communication network and communicating with other devices. The communication network may be the Internet, a local area network (LAN), a wide area network (WAN), a dedicated line, wired, wireless, or other communication network. Reader 129 is a device for reading portable recording media.
[0128] The program that implements the processing described in the above embodiment may be stored, for example, in the storage device 125 via the communication network and communication I / F 128 from the program provider. Alternatively, the program that implements the processing described in the above embodiment may be stored in a commercially available and distributed portable storage medium. In this case, the portable storage medium may be set in the reader 129, and the program may be read and executed by the CPU 122. Various types of storage media can be used as portable storage media, such as CD-ROMs, flexible disks, optical disks, magneto-optical disks, IC cards, USB memory devices, and semiconductor memory cards. The program stored in such a storage medium is read by the reader 69.
[0129] Furthermore, the program may be installed on a standalone computer, or it may be installed on a cloud computer and only its functionality may be provided to the user.
[0130] The embodiments of this specification have been described above based on the embodiments and modifications described above. The embodiments described above are for the purpose of facilitating understanding of this specification and do not limit it. This specification may be modified and improved without departing from its spirit and the scope of the claims, and equivalents thereof are included in this specification. Furthermore, any technical features that are not described as essential in this specification may be deleted as appropriate. [Explanation of Symbols]
[0131] 1. Information Processing Device 2. Reception Department 3. Locking control unit 4 Notification section 11. Store Management System 12 Store Management Server 13 Smart Lock Management Server 13 14 User terminals 21 stores 22 private rooms 23 Reception terminal 24 Smart Locks 25 Order Management Terminal 26 Handover Counter 27 Kitchen 28 Wireless Routers 29. Cleaning staff terminal
Claims
1. The reception desk accepts reservations from customers regarding the use of the store, A locking control unit that controls the locking or unlocking of private rooms within the store, A notification unit notifies the customer's terminal device of a predetermined message based on the customer's entry into the store and the customer's completion of use of the store, as confirmed by the customer's check-in at the store based on the aforementioned reservation. An information processing device equipped with the following features.
2. When the customer places an order, the notification unit accepts the order based on the customer's entry and exit information regarding their use of the store. When the preparation of the ordered items is complete, the notification unit notifies the customer of a message prompting them to come and pick up the items as they are ready. The information processing apparatus according to feature 1.
3. When the customer places an order, the notification unit, based on the customer's entry and exit information regarding the customer's entry into the store and the end of their use of the store, will determine the customer's age for the specified product and, based on the determination result, notify the customer of a message indicating that the order for the product cannot be accepted. The information processing apparatus according to feature 1.
4. Based on the entry and exit information regarding the customer's entry into the store and the customer's use of the store, the notification unit notifies the customer's terminal device whether or not to extend the usage time a predetermined time before the time of entry and exit ends. If the time of entry and exit ends arrives without the customer requesting payment, the notification unit updates the entry and exit time by a predetermined amount. The information processing apparatus according to feature 1.
5. When the notification unit receives an order request from the customer, it accepts the payment request based on the information regarding the customer's entry into the store and the end of the customer's use of the store. After the payment processing, if it receives information that the private room has been cleaned, it locks the door to the private room. The information processing apparatus according to feature 1.
6. On the computer, The process of receiving reservations from customers regarding the use of the store, A locking control process that controls the locking or unlocking of private rooms within the aforementioned store, Based on the information regarding the customer's entry into the store and the completion of their use of the store, which is received at the store based on the aforementioned reservation, a notification process is performed to notify the customer's terminal device of a predetermined message. An information processing program that executes [something].
7. Computers The process of receiving reservations from customers regarding the use of the store, A locking control process that controls the locking or unlocking of private rooms within the aforementioned store, Based on the information regarding the customer's entry into the store and the completion of their use of the store, which is received at the store based on the aforementioned reservation, a notification process is performed to notify the customer's terminal device of a predetermined message. An information processing method that performs the following.
Citation Information
Patent Citations
Order management program and order management method
JP2004302888A
Identification data management device, identification data management method, and identification data management program
JP2013069074A
Order management system, order management program, and portable terminal
JP2014002641A
Ordering system
JP2017102850A
Order management system and order management method
JP2017162028A