Management system, information processing apparatus, program, and information processing method

Abstract

To provide a management system capable of extending a time for securing equipment of a specific facility by a simple operation, an information processing device, a program, and an information processing method.SOLUTION: A management system 10 comprising an information processing device (a management server 200) for managing vacancy information of equipment provided by a facility and equipment terminals (tablet terminals 401-1 to n) includes: management means for managing use state information in response to a request from a user terminal 300; and transmission means for transmitting the use state information to the equipment terminals. Upon receiving a request for securing a seat, the management means changes the use state information of equipment selected from the equipment to information showing a reservation state, and the transmission means transmits the information showing the reservation state to the equipment terminal. The equipment terminal displays a first prescribed time reservation state screen in a display part, and upon receiving a request for extending a seat reservation, receives the extension if a prescribed condition is satisfied, and adds a second prescribed time to a time for displaying the reservation state screen to display the time in the display part.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a management system, an information processing apparatus, a program, and an information processing method.

Background Art

[0002] Currently, in a network environment, there is a service that allows a user to access a reservation site (for example) using their own terminal (such as a smartphone or personal computer) and make a reservation for a seat or table at a facility such as a café, restaurant, or izakaya. For example, Patent Document 1 discloses a technique for improving the convenience of reservations by presenting the user with the arrangement of tables and seats at a facility for which a reservation is a candidate and the number of available people per table when the user makes a reservation for such a facility.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, due to various circumstances such as unexpected situations where the road is congested or the train stops midway, the user may be late and not make it in time for the reserved time. Therefore, in view of such a situation, the present disclosure proposes a technique that allows a user to extend the time for which a seat used at a facility is reserved with a simple operation.

Means for Solving the Problems

[0005] To solve the above problems, the present disclosure provides a management system including an information processing apparatus that manages vacancy information of facilities provided by a facility, and a facility terminal installed in the facility and having a display unit. The information processing apparatus includes a storage unit that stores usage status information indicating the usage status of each facility, a management unit that manages the usage status information in response to a request from a user terminal, and a transmission unit that transmits the usage status information to the facility terminal. When the management unit receives a request for securing a seat from the user terminal, it selects one of the facilities, changes the usage status information of the selected facility to information indicating that it is reserved, and when the transmission unit transmits the information indicating that it is reserved to the facility terminal, the facility terminal displays a reservation screen indicating that it is reserved on the display unit for a first predetermined time. Further, when the management unit receives a request for extending the seat reservation from the user terminal, if a predetermined condition is satisfied, it accepts the extension, and the transmission unit transmits information regarding the extension to the facility terminal, and the facility terminal adds and displays the time for which the reservation screen is to be displayed on the display unit by a second predetermined time.

Advantages of the Invention

[0006] According to the technology of the present disclosure, by accepting the time for securing a seat used in a facility through a simple operation, it becomes possible to promote the comfortable use of the facility for both the facility and the user.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2A

Figure 2B

Figure 3

Figure 4A

Figure 4B

Figure 5A

Figure 5B

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0008] Hereinafter, this embodiment will be described with reference to the drawings. The same components will be described with the same reference numerals. Note that the following embodiments do not necessarily limit the technology of the present disclosure, and not all combinations of the features described in this embodiment are essential for solving the above problems.

[0009] (1) First Embodiment The first embodiment describes a method of accepting an extension when a user wants to extend the seat reservation time in a system that secures seats in a facility (i.e., reserves the time after a predetermined time as the reservation time) from the time a reservation is accepted (for example, 15 minutes). In this embodiment, a store that involves food and drink such as a café or a restaurant is taken as an example of the facility, but it can be applied to various other facilities such as a co - working space or a parking lot. The store collects information on the availability status such as whether there are empty seats or it is crowded as availability information, and it can be viewed on a user terminal or a digital signage.

[0010] <Configuration Example of Management System 10> FIG. 1 is a diagram showing a configuration example of a management system 10 according to an embodiment of the present disclosure. The management system 10 is a system for managing the empty seat information of a store, and includes a management server 200 (information processing device), a plurality of tablet terminals 401 - 1 to 401 - n, and at least one user terminal 300. The plurality of tablet terminals 401 - 1 to 401 - n (hereinafter, the general term for the plurality of tablet terminals or any one of them is denoted as 401) are installed as seat - use terminals at positions where they can be used from the seats for each unit in which a user uses a seat in the store 400. Specifically, when each table seat or counter seat is installed, the plurality of tablet terminals 401 are installed on the counter tops of each counter seat, notify the management server 200 of the usage status of each table seat, and inform the store user of the current usage time and the like. The plurality of tablet terminals 401 are also referred to as information processing devices or facility - use terminals. In FIG. 1, only one store 400 is shown, but usually there may be a plurality of stores 400. In this case, the tablet terminals of each store are configured to be communicable with the management server 200. Further, although not essential, the management system 10 may further include a store management terminal 402 for managing the tablet terminals 401 arranged at each seat of the store 400.

[0011] The management server 200 is installed outside the store 400 and is a server that receives information on the usage status (vacant or in use) received from each tablet terminal 401 of the store 400 and manages the usage status of each seat in each store. The user terminal 300 is a device such as a smartphone, for example, and is a terminal of a user who uses the service provided by the management system 10. Each tablet terminal 401, management server 200, and user terminal 300 as described above are interconnected via a network such as the Internet, for example. Note that the user terminal 300 can be configured so that it cannot directly access each tablet terminal 401 of each store 400.

[0012] Each tablet terminal 401 displays the usage status of the corresponding seat (any one of vacant, reserved (reserving), or in use) on the display screen. Here, when the usage status of the corresponding seat is vacant, it can be said that it is available for anyone to use. When the management server 200 notifies (receives a seat reservation notification) that there has been a reservation for the seat from the user terminal 300, each tablet terminal 401 changes the display of the usage status from "vacant" to "reserving". Also, when a user who has reserved a seat comes to the store 400 and arrives at the corresponding seat and enters the reservation number (password) described later in the reservation number input field on the display screen of the tablet terminal 401-k (the terminal placed at the reserved seat), the usage status of the seat is changed from "reserving" to "in use". Furthermore, when a user without a reservation comes to the store 400 and arrives at a seat where the usage status is vacant (a seat that is neither reserved nor in use) and presses the occupancy button on the display screen of the tablet terminal 401 displayed as "vacant", the usage status of the seat is changed from "vacant" to "in use". Also, when the user presses the departure button on the display screen (for example, and will leave the store 400 thereafter), each tablet terminal 401 changes the display screen from "in use" to "vacant". Furthermore, each tablet terminal 401- notifies the management server 200 of the change in the usage status (the change in the usage status from "reserving" or "vacant" to "in use" and from "in use" to "vacant (changed to "vacant" by leaving the seat)") when the usage status of the seat is changed.

[0013] The management server 200 manages the usage status of each store 400 on the database by storing (updating) in the database 241 (see FIG. 2B) the data indicating the usage status of each seat in each store 400 received from each tablet terminal 401 of each store 400.

[0014] A user who is about to visit any store 400 can inquire of the management server 200 about the congestion status of each store 400 via the user terminal 300. The management server 200 responds to the inquiry and acquires from the database 241 information (vacancy information) indicating a group of stores within a predetermined distance range from the position of the user terminal 300 or a specified position on the map by the user (for example, the position tapped on the map displayed on the display screen of the user terminal 300) and their vacancy status (congestion status). The management server 200 returns the information of the acquired store group and the vacancy information to the user terminal 300 as a response to the inquiry. The user terminal 300 displays (for example, pin displays) or list-displays the store group and their vacancy information received from the management server 200 on the map. Note that the management server 200 transmits, for example, vacancy information indicating "vacancy available" to the user terminal 300 if there are a predetermined number or more (it can also be one or more, or a specific number of seats can be set) of vacant seats in the store 400, transmits vacancy information indicating "congested" to the user terminal 300 if a predetermined number of tables / seats in the store 400 are reserved or in use, and transmits vacancy information indicating "fully occupied" to the user terminal 300 if all tables / seats in the store 400 are "in use".

[0015] On the display screen of the user terminal 300, the congestion status of each store 400 sent from the management server 200 in response to the query is displayed. When one of the stores 400 is selected by the user, a reservation screen for designating a seat at the selected store 400 is displayed on the display screen of the user terminal 300. In this embodiment, for each seat attribute, it is assumed that "vacant" or "in use" is displayed. The seat attribute is defined by, for example, the number of available people and the type of seat. For example, it is distinguished as a 4-person table seat, a 4-person sofa seat, a 1-person counter seat, a 2-person table seat, etc. When there are 50 seats with the seat attribute of a 4-person table seat and there is even one "vacant" seat, the seat attribute (4-person table seat) and the display of "vacant" are made in the UI on the display screen. If none of the 50 seats with the seat attribute of a 4-person table seat is "vacant" (all 50 seats are in use or reserved), the display of the seat attribute (4-person table seat) and "in use" is made. When the seat attribute with the use status of "vacant" is selected by the user, the user terminal 300 transmits the selected seat attribute to the management server 200 as selection information.

[0016] The management server 200 that has received the selection information randomly selects a seat from the seats with the selected seat attribute (table seat, counter seat, etc.), or according to a predetermined rule (for example, a rule that can be adopted to perform reservation processing with priority given to seats that have left the seats in use due to a request from the store 400 side). Then, the management server 200 changes the status information in the database 241 of the selected seat from "vacant" to "reserved", and notifies the tablet terminal 401-k installed at the seat that a reservation has been made for the seat. Then, the tablet terminal 401-k that has received the notification changes the displayed usage status on the screen from "vacant" to "reserved".

[0017] In addition, when the vacant seat management system 10 includes the store management terminal 402, the store management terminal 402 communicates with the management server 200 periodically or each time the usage status of each tablet terminal 401-k changes (it may be configured to be able to communicate directly with each tablet terminal 401-k), and displays the usage status of each tablet terminal 401-k on the display screen, enabling the store manager to manage the usage status of each seat in the store 400.

[0018] <Hardware configuration example of the management server 200> FIG. 2A is a diagram showing a hardware configuration example of the management server 200. The management server 200 includes a CPU (Central Processing Unit) 210, a ROM (Read Only Memory) 220, a RAM (Random Access Memory) 230, a storage device 240, and a communication device 250. The CPU 210 realizes the functions provided by the management server 200 by executing a program described later. The ROM 220 and the RAM 230 hold data used by the CPU 210. The storage device 240 stores a database and a program described later. The communication device 250 communicates with the user terminal 300 and the tablet terminals 401-k (k is an integer from 1 to n) of the store 400 via a network.

[0019] <Functional Configuration Example of Management Server 200> Figure 2B is a block diagram showing a functional configuration example of management server 200. Management server 200 includes a receiving unit 211, a management unit 212, a notification unit 213, an authentication unit 214, and a settlement unit 215 as software modules (functions configured by various programs being expanded in the internal memory of CPU 210) executed by CPU 210. Hereinafter, for convenience of description, these modules may be described as the operating entities, but since it is actually CPU 210 that executes these modules, CPU 210 can also be used as the operating entity. Storage device 240 stores database 241. Database 241 has a store table that stores information on the usage status (vacant seat status, crowded status) of each seat in each store 400, and a user table that stores user information such as names and settlement information. A configuration example of the tables included in database 241 will be described later.

[0020] Receiving unit 211 directly receives, via communication device 250, data indicating the usage status of each seat in store 400 from each tablet terminal 401 of store 400. From tablet terminal 401, information corresponding to an input (pressing of the seating button or leaving button on the screen, input of the reservation number) by a user who has come to the store to the display screen of tablet terminal 401-k, such as "in use" or "left", is received.

[0021] Based on the store ID (store identification information) and seat ID (seat identification information) of each store 400 included in the information received by receiving unit 211, management unit 212 identifies the store and the seat, and updates the usage status data in store table 2410 of database 241. Also, based on a request received by receiving unit 211 from user terminal 300, etc., the usage status data in store table 2410 of database 241 is updated. Authentication unit 214 performs authentication processing regarding the user.

[0022] When the receiving unit 211 receives a request from the user terminal 300 to check the congestion status of a specific store or stores in the surrounding area of the user terminal 300, the notification unit 214 transmits the latest status information on the congestion status of each store within a predetermined range to the target user terminal 300. The user terminal 300 that has received these data constructs a UI for store selection (for example, pin display on a map) and displays (pin display) the vacancy information on the map there. Also, the receiving unit 211 first accepts a reservation for a seat of a specific attribute in the "vacant" state of a specific store 400 from the user terminal 300. At this time, the user makes a reservation by specifying only the seat attributes such as "table for two", "counter seat", "booth seat", etc., rather than a reservation specifying the position of the seat to be used. After the receiving unit 211 accepts the reservation, the management unit 212 randomly or according to a predetermined rule selects a seat of the seat attribute reserved by the user and assigns (makes a reservation for) a seat to the user. Further, the notification unit 214 transmits reservation information (including at least the reservation date and time, reservation number) to the tablet terminal 401-k placed on the reserved seat.

[0023] <Configuration example of store table 2410 and user table 2420> FIG. 3 is a diagram showing a configuration example of a store table 2410 for managing the usage status of each seat in each store 400 and a user table 2420 for managing user information. The store table 2410 and the user table 2420 can be configured, for example, by storing data describing the contents of records in the storage device 240. In this embodiment, the database 241 is represented in a table format, but it is not limited to this format, and any format can be used as long as each data is associated. Therefore, it can also be simply referred to as store data or store information. The store table 2410 is a data table for managing attribute information used when a user searches for a store and the latest congestion status for each store. For example, it has a store ID, a name, a store location, a store phone number, a table / seat ID, a table / seat attribute, and the usage status of the corresponding seat as constituent items.

[0024] The store ID is an ID for identifying each store within the database 241. The first record indicates the usage status of the table with store ID = 001 or seat ID = A001, and the second record indicates the usage status of a different table or seat (ID = A002) in the same store. The information assigned with the same store ID is information indicating the usage status of different tables or seats within the same store.

[0025] The name is information indicating the name of each store 400. The location is information representing the location of each store 400 in latitude and longitude. The phone number is information indicating the contact information of each store 400. Although it is used as a phone number here, other contact information may be managed instead.

[0026] The table / seat ID is an ID for uniquely identifying each table or each seat within the same store 400. The table / seat attribute is information indicating the type of the table or the like. For example, "1" can represent a 4-person table seat, "2" can represent a 2-person table seat, "3" can represent a single-person counter seat, "4" can represent a 4-person sofa seat, and "5" can represent a single-person booth seat. Note that since the table / seat attribute varies by store, text data may be stored.

[0027] The usage status is information (usage status information) indicating the usage status of the corresponding seat. For example, "0" indicates an empty seat, "1" indicates reserved, and "2" indicates in use. The usage status 2417 is information that changes among "0", "1", and "2" according to the information received from each tablet terminal 401-1 to 401-n of each store 400 and the user terminal 300. The user table 2420 is a data table that manages information about pre-registered users. For example, it has user ID, user name, address, phone number, email address, payment information, and authentication information as its constituent items. These pieces of information are pre-input by the user as account information and registered, and are used when logging in. The payment information is identification information that can identify a payment. For example, credit card information (such as credit card number) or account balance information, etc., information associated with the user ID in available payment methods is stored as payment information. The authentication information is the password used by the user to log in. The management server 200 can execute a payment using the payment information while the user is logged in using the authentication information.

[0028] <Hardware Configuration Example of User Terminal 300> Figure 4A is a diagram showing a hardware configuration example of the user terminal 300. The user terminal 300 includes a CPU 310, a display unit 320, an input unit 330, a communication unit 340, and a memory 350. The CPU 310 controls the operations of each part included in the user terminal 300. The communication unit 340 communicates with the management server 200 via a network and receives information on the congestion status of the store 400 and the usage status of each seat attribute of the store 400. The display unit 320 displays on the screen the congestion status information of each store 400 received from the management server 200 and the usage status information of each seat attribute of the selected store. The input unit 330 is an interface used for the user to input an operation instruction to the user terminal 300. For example, the display unit 320 and the input unit 330 can be integrally configured by a touch panel or the like.

[0029] <Functional Configuration Example of User Terminal 300> FIG. 4B is a block diagram showing a functional configuration example of user terminal 300. User terminal 300 includes a generation unit 3101, a display control unit 3102, a communication control unit 3103, and a memory control unit 3104 as software modules executed by CPU 310 (functions configured by expanding various programs in the internal memory of CPU 310). Hereinafter, for convenience of description, these modules may be described with the modules as the operating entities. However, since CPU 310 actually executes these modules, CPU 310 can also be used as the operating entity.

[0030] The generation unit 3101 generates UI data (store selection UI data) corresponding to the vacancy information of each store 400 received from the management server 200. As the store selection UI data, for example, a form in which each store name and vacancy information are displayed in a list in text, or text data or mark data corresponding to the vacancy information (text / mark corresponding to vacant seat "0", text / mark corresponding to congestion "1", text / mark corresponding to full seat "2") is read from the memory 350 and superimposed and displayed on the map can be adopted. Further, the generation unit 3101 generates UI data (seat attribute selection UI data) indicating the usage status of each seat attribute of the selected store 400 in response to the user's store selection input. As the seat attribute selection UI data, a form in which text data ("vacant seat", "reserved", and "in use") corresponding to the usage status is displayed in a list together with the seat attribute (two-seater, four-seater, counter seat, etc.) can be adopted. Further, the generation unit 3101 generates reservation completion UI data indicating that a reservation is in progress. The reservation completion UI data is data for displaying the reservation number and an indication for accepting an extension. Details will be described later.

[0031] The display control unit 3102 controls the data display operation by the display unit 320. For example, the display control unit 3102 displays the UI data generated by the generation unit 3101 on the screen of the display unit 320. Also, it receives an instruction from the user in response to an operation on the UI data.

[0032] The communication control unit 3103 controls the communication operations (e.g., communication with the management server 200) executed by the communication unit 340. For example, when a user instructs the transmission of a request to inquire about the congestion status of the store 400 to the management server 200, the communication control unit 3103 acquires the current position (latitude and longitude information) of the user terminal 300 and controls the communication unit 340 to transmit a request with the current position information to the management server 200. Further, the communication control unit 3103 controls the communication unit 340 to transmit a reservation request for a desired seat attribute of a desired store, and controls the communication unit 340 to receive a reservation number and reservation confirmation information (such as reservation completion display data and reservation completion confirmation email) from the management server 200 when the reservation is completed.

[0033] The memory control unit 3104 controls the data reading operation from the memory 350 and the data writing operation to the memory 350. For example, the memory control unit 3104 receives the reservation number and reservation confirmation information from the management server 200 received by the communication unit 340 and writes them to the memory 350. Further, for example, the memory control unit 3104 reads out the vacancy information of the store and the usage status information of each seat attribute (seat type group) of the store from the memory 350 in response to a command from the generation unit 3101 and delivers it to the generation unit 3101.

[0034] <Hardware Configuration Example of Tablet Terminal 401-k> FIG. 5A is a diagram showing a hardware configuration example of a tablet terminal 401-k (k is an integer from 1 to n) arranged at each seat of each store 400. The tablet terminal 401-k includes a CPU 4011, a display unit 4012, an input unit 4013, a communication unit 4014, and a memory 4015. The CPU 4011 controls the operations of each unit included in the tablet terminal 401-k. The communication unit 4014 receives reservation information (reservation date and time, reservation number) of the target seat from the management server 200 via a network, and transmits information on the start and departure of the use of the target seat in the store 400 to the management server 200.

[0035] When the management server 200 receives reservation information, the display unit 320 of the tablet terminal 401-k placed on the reserved seat displays information indicating that the seat is in a reserved state (for example, a message "This table is reserved" as described later) on the tablet display screen (see Fig. 9(b)). On the other hand, the display unit 320 of the tablet terminal 401-k placed on the vacant seat displays information indicating that the seat is vacant (for example, a "Seating button" as described later) on the tablet display screen. Further, the tablet terminal 401-k placed on the seat in use displays the current usage time and a departure button that the user or a store clerk presses when the user departs on the tablet display screen.

[0036] The input unit 330 is an interface used for a user who visits the store 400 and takes a seat or a store clerk of the store 400 to input an operation instruction to the tablet terminal 401-k. For example, the display unit 320 and the input unit 330 can be integrally configured by a touch panel or the like.

[0037] <Functional Configuration Example of Tablet Terminal 401> Fig. 5B is a block diagram showing a functional configuration example of the tablet terminal 401-k (k is an integer from 1 to n). The tablet terminal 401-k includes a UI data generation unit 40111, a display control unit 40112, a communication control unit 40113, and a storage control unit 40114 as software modules executed by the CPU 4011 (functions configured by various programs being expanded in the internal memory of the CPU 4011). Hereinafter, for convenience of description, these modules may be described with the modules as the operating entities, but since it is actually the CPU 4011 that executes these modules, the CPU 4011 can also be used as the operating entity.

[0038] The UI data generation unit 40111 reads UI data corresponding to the seat usage status (empty seat, reserved, in use) from the memory 4015 and transfers the UI data to the display control unit 40112. Specifically, when the seat where the tablet terminal 401-k is placed becomes an "empty seat", the UI data generation unit 40111 reads the UI data for empty seats from the memory 4015 and transfers it to the display control unit 40112. Also, when the seat where the tablet terminal 401-k is placed becomes "reserved" (for example, when it is notified from the management server 200 that a reservation has been made for the seat), the UI data generation unit 40111 reads the UI data for reserved seats from the memory 4015 and transfers it to the display control unit 40112. Furthermore, when the seat where the tablet terminal 401-k is placed becomes "in use" (for example, when the reserved user comes to the store and changes from "reserved" to "in use" or when a non-reserved user comes to the store and takes the seat and becomes "in use"), the UI data generation unit 40111 reads the UI data for in-use from the memory 4015 and transfers it to the display control unit 40112.

[0039] The display control unit 40112 controls the data display operation by the display unit 4012. For example, the display control unit 40112 generates a display screen from various UI data received from the UI data generation unit 40111 and displays it on the screen of the display unit 4012.

[0040] The communication control unit 40113 controls the communication operations (e.g., communication with the management server 200) executed by the communication unit 4014. For example, when a user visits the store 400, takes a seat, and presses the seat button on the UI display of the tablet terminal 401-k, the UI display of the seat is changed to "in use". At this time, the communication control unit 40113 controls the communication unit 4014 to notify the management server 200 that the seat has become "in use". When the user vacates a seat that is "in use" (the user presses the vacate button), the communication control unit 40113 controls the communication unit 4014 to notify the management server 200 that the seat has become "vacant". When a reserved user arrives at a "reserved" seat (enters the reservation number in the reservation number input field on the screen (UI display) of the tablet terminal 401-k), the communication control unit 40113 controls the communication unit 4014 to notify the management server 200 that the seat has changed from "reserved" to "in use".

[0041] The memory control unit 40114 controls the data reading operation from the memory 4015 and the data writing operation to the memory 4015. For example, the memory control unit 40114 receives seat reservation information (information indicating that a specific seat has been reserved by a user, including reservation date and time, reservation number, etc.) received by the communication unit 4014 from the management server 200 and writes it to the memory 4015. Also, for example, the memory control unit 40114 reads the corresponding UI data (UI data for vacant seats, UI data for reserved seats, UI data for in-use seats) from the memory 4015 in response to a UI data reading command from the UI data generation unit 40111 and delivers it to the UI data generation unit 40111.

[0042] <Details of Seat Reservation Processing> Figure 6 is a flowchart for explaining the seat reservation processing executed between the management server 200 and the user terminal 300. In the following, the steps in the flowchart will be denoted as "S".

[0043] (1) The user terminal 300 (communication unit 340) generates a store search (café search) request and transmits it to the management server 200. The store search request includes the current location information of the user terminal 300 (for example, the latitude and longitude information obtained from GPS). In addition, as the store search request, in addition to the search request based on the current location of the user terminal 300, it can be in the form of a search request for stores in a specific designated location (for example, the user is currently around Tokyo Station, but around Ginza Station), a search request specifying a specific store (in this case, the user wants to know the availability information of a specific store), etc.

[0044] (2) When the reception unit 211 of the management unit 212 receives a store search request from the user terminal 300, the management unit 212 returns to the user terminal 300 that transmitted the store search request the information of the store group corresponding to the store search request (each store name, location, etc.) and the availability information corresponding to each store (whether there are vacant seats in each store, whether each store is in a crowded state or full). Note that how the state of "crowded" is determined can be appropriately determined by each store or the server administrator. For example, it may be set as the "crowded state" when a predetermined number or more of seats are in use or reserved and occupied, or it can also be set as the "crowded state" based on the input from the store 400 side (for example, information transmitted from a store management terminal (not shown) to the management server 200). Furthermore, at the request of the store 400 side, instead of using the expression "crowded", the state of the store may be represented by only two states of "vacant seats" and "full seats".

[0045] (3) When the communication unit 340 receives the search results (information of the store group and their availability information) from the management server 200, the generation unit 3101 of the user terminal 300 generates a store selection (store group display) UI for displaying the store group and the availability information on the screen. The store selection UI can be a map display UI for displaying the store group and the availability information on a map or a text display UI for displaying the store group and the availability information in a list. Then, the display control unit 3102 displays the created store selection UI on the display unit 320 (display screen).

[0046] (4) When the user selects a store from the store groups displayed on the screen via the input unit 330 (such as key input or tablet input) (receives a store designation input), the generation unit 3101 generates selection information including the store name or store ID and passes it to the communication control unit 3103. Then, the communication control unit 3103 uses the communication unit 340 to transmit the selection information to the management server 200.

[0047] (5) When the receiving unit 211 of the management server 200 receives the selection information from the user terminal 300, the management unit 212 acquires the seat attribute status information corresponding to the store included in the selection information from the storage device 240 and passes it to the notification unit 213. The notification unit 213 uses the communication device 250 to transmit the seat attribute status information to the user terminal 300. Here, the seat attribute status information is information including text information or image information indicating the attributes of the seats arranged in the store (for example, an image of the seat attribute (type)) and information indicating the current usage status (empty or in use) of each seat attribute.

[0048] (6) When the communication unit 340 receives the seat attribute status information from the management server 200, the generation unit 3101 of the user terminal 300 generates UI data for seat attribute selection for displaying the seat attribute status information on the display unit 320 and passes it to the display control unit 3102. The UI data for seat attribute selection is data for constructing a UI for notifying the user of information for identifying the seat attribute (seat type) and the usage status of the entire seat attribute (if there is even one "empty" seat, it is "empty"; if there is no "empty" seat, it is "in use" (including reserved)). Then, the display control unit 3102 displays the received UI data for seat attribute selection on the display unit 320.

[0049] (7) When the user selects an empty seat attribute from the seat attribute status information displayed on the screen via the input unit 330 (reserves a seat type), the generation unit 3101 generates reservation information regarding the specified seat attribute (including information for identifying the store and seat attribute (store ID and seat attribute ID)) and passes it to the communication control unit 3103.

[0050] (8) The communication control unit 3103 uses the communication unit 340 to transmit reservation information to the management server 200.

[0051] (9) When the receiving unit 211 of the management server 200 receives reservation information from the user terminal 300, the management unit 212 randomly selects an available seat among the seats with the specified seat attributes, assigns a password (reservation number), and passes the seat ID and password to the notification unit 213. The notification unit 213 uses the communication device 250 to transmit the seat ID and password to the user terminal 300 that made the reservation. In addition, the notification unit 213 also transmits reservation information (that there is a reservation, reservation date and time, and password) to the tablet terminal 401-k arranged on the seat of the store 400 to be reserved. Here, the management server 200 stores the reservation information in the storage device 240. The reservation information is stored by associating the facility ID, user ID, reservation reception time, seat ID, and password.

[0052] (10) The management unit 212 changes the usage status 2417 of the seat to which the password has been assigned from "available (0)" to "reserved (1)" in the seat usage status management database 2410.

[0053] (11) When the communication unit 340 of the user terminal 300 receives a password (reservation number) from the management server 200, the display control unit 3102 receives the password from the communication control unit 3103 and displays the reserved information (store name and seat information) and the password on the display unit 320. Thereby, the user can know that the reservation is completed. Also, in this embodiment, when the reservation is completed, it is a reservation service that the user must go to the target store within a predetermined time (for example, within 15 minutes). Therefore, the display unit 320 of the user terminal 300 may display a warning that the reservation is valid for only 15 minutes. If the user cannot come to the store within 15 minutes and does not extend the secured time described later, the reservation will be cancelled.

[0054] (12) If the user selects "Extend the reservation time by 10 minutes" displayed on the screen via the input unit 330 within 15 minutes of securing the seat, the generation unit 3101 generates request information for extension (including the user ID and reservation information) and passes it to the communication control unit 3103. Note that "Extend the reservation time by 10 minutes" is only displayed or selectable within the predetermined time (here 15 minutes as described above) for securing the seat when the reservation was first made. That is, if the predetermined time has already been exceeded, it is assumed that the extension of the reservation time cannot be accepted.

[0055] (13) When the receiving unit 211 of the management server 200 receives request information regarding the extension from the user terminal 300, the authentication unit 214 determines whether to accept the extension. First, the authentication unit 214 refers to the reservation information included in the request information and determines whether the reservation specified from the user terminal 300 exists in the storage device 240. If it exists, the authentication unit 214 obtains the payment method of the user ID included in the request information from the user table 2420, and the notification unit 213 uses the communication device 250 to notify the user terminal 300 that the extension is accepted and of the payment method. Here, since completing the payment is a condition for accepting the extension, the management server 200 transmits information regarding the payment method to the user terminal 300.

[0056] (14) When the communication unit 340 receives information indicating that the extension is accepted from the management server 200, the generation unit 3101 of the user terminal 300 generates payment UI data for display and passes it to the display control unit 3102. The payment UI data is data for constructing a UI that displays information for confirming whether to make a payment and a part of the payment information used for the payment linked to the user for confirmation. Then, the display control unit 3102 displays the payment UI data on the display unit 320.

[0057] (15) When the user checks the payment information displayed on the screen via the input unit 330 and selects "Confirm", the generation unit 3101 generates payment instruction information indicating that the payment process is to be confirmed and delivers it to the communication control unit 3103. Here, the payment instruction information includes payment information, user ID, payment date and time information, and the payment amount.

[0058] (16) When the receiving unit 211 of the management server 200 receives the payment instruction information from the user terminal 300, the payment unit 215 executes the payment process. For example, in the case of electronic payment, the payment amount is subtracted from the balance corresponding to the user's account, and the payment amount is added to the balance of the account corresponding to the store that is the payee. Alternatively, in the case of payment using a credit card, the payment unit 215 communicates with the credit card company and executes the payment process. When the payment unit 215 completes the payment process, the notification unit 213 transmits to the user terminal 300 that the payment process has been completed.

[0059] (17) When the user terminal 300 is notified by the notification unit 213 that the payment process has been completed, the display control unit 3102 generates UI data indicating that the payment has been completed and displays it on the display unit 320. Also, the remaining time of the seat reservation time obtained by adding the extension time (here 10 minutes) to the predetermined time (here 15 minutes) for initially securing a seat at the reservation acceptance time included in the reservation information is displayed on the display unit 320.

[0060] (18) The management unit 212 of the management server 200 notifies the tablet terminal 401 corresponding to the seat ID included in the reservation information that has received the extension, of the extension information indicating that the reservation time is extended by 10 minutes. Thus, a series of processes when accepting a seat reservation for securing a seat at a predetermined time from now and further accepting a reservation for the time to secure the seat is completed.

[0061] <Details of Seat Management Process> Figure 7 is a flowchart of the seat management process executed by each tablet terminal 401 according to the first embodiment. The seat management process is a process for managing the usage status (vacant seat, reserved, in use) of the seat where the tablet terminal 401 is placed. In the flowchart of FIG. 6, it is assumed that the seat management process starts when the usage status of the target seat is "vacant". For example, when the store 400 opens, each seat is vacant. Therefore, before the store opens, after the power of each tablet terminal 401-1 to 401-n is turned on, the flowchart of FIG. 7 starts on each tablet terminal 401-1 to 401-n as the store opens. In the following description, the UI data generation unit 40111 is mainly used as the operating entity. However, for each process, a separate processing unit may be newly set as the operating entity. In addition, since the UI data generation unit 40111 and the newly set processing unit are realized by the CPU 4011, the operating entity of each step can be read as the CPU 4011.

[0062] (i) S701 When the seat is vacant, the display control unit 40112 generates vacant seat display data from the vacant seat GUI data and displays it on the display screen of the display unit 4012. The vacant seat GUI data is read from the memory 4015 by the UI data generation unit 40111 and passed to the display control unit 40112. (ii) S702 The UI data generation unit 40111 determines whether it has received reservation information (information indicating that the seat has been reserved by a specific user) from the management server 200. If it has not received the reservation information (when reservation acceptance has not been performed: NO in S702), the process proceeds to S703. If it has received the reservation information (when reservation acceptance has been performed: YES in S702), the process proceeds to S704.

[0063] (iii) The S703 UI data generation unit 40111 determines whether the seat has entered the usage start state. For example, when a user without a seat reservation visits the store and presses the seating button on the UI screen of the tablet terminal 401-k placed at a "vacant seat", the usage status of the seat changes from "vacant" to "in use". When the seat has entered the usage start state (when usage start acceptance has been received: YES in S703), the process proceeds to S704. On the other hand, when the seat has not entered the usage start state (when usage start acceptance has not been received: NO in S703), the process returns to S701. At this time, the screen display of the tablet terminal 401-k remains the display for vacant seats.

[0064] (iv) The S704 UI data generation unit 40111 reads the reserved seat UI data from the memory 4015 and transfers it to the display control unit 40112. Then, the display control unit 40112 generates a reserved seat display screen based on the reserved seat UI data, displays it on the display unit 4012 (the screen display of the tablet terminal 401-k shows "reserved"), and stores the reservation number (password) sent from the management server 200 in the memory 4015.

[0065] (v) The S705 UI data generation unit 40111 identifies the seat reservation time and determines whether there has been a check-in for the seat by the user who made the reservation within the seat reservation time. The seat reservation time is obtained from the reservation information of the seat ID corresponding to the tablet terminal 401 and (if any) extension information to identify the seat reservation time. Specifically, if there is only reservation information, the time from the reservation acceptance time included in the reservation information to a predetermined time (15 minutes later) set in advance is set as the seat availability time. Also, when there is reservation information and extension information corresponding to the seat ID, the time up to the time obtained by adding the extension time to the predetermined time is set as the seat reservation time. When it is determined that it is within the seat reservation time (YES in S705), the process proceeds to S707. When it is determined that it is not within the seat reservation time (NO in S705), the process proceeds to S706. Note that if a user who made a reservation has not yet checked in but it is within the seat reservation time, the reservation status display continues.

[0066] (vi) The S706 UI data generation unit 40111 changes the reserved seat display screen to the available seat display screen. Then, the communication control unit 40113 uses the communication unit 4014 to notify the management server 200 of the reservation cancellation (since the user with a reservation did not arrive within the seat reservation time, the reservation was cancelled). Note that upon receiving the reservation cancellation, the management server 200 changes the seat usage status 2417 of the corresponding seat in the seat usage status management database 2410 from "reserved (1)" to "available (0)". Also, the management server 200 notifies the user terminal 300 of the user of the reservation cancellation.

[0067] (vii) The S707 UI data generation unit 40111 determines whether check-in has been performed. Specifically, it collates the reservation number (password) input by the arriving user with the reservation number of the corresponding seat stored in the memory 4015 (the number notified by the management server 200). Note that if the input reservation number is appropriate as a result of the collation, the process proceeds to S708 as check-in completed. If no check-in operation is performed here (no number input by the user), the process returns to S705. If a check-in operation has been performed in S707 but the input reservation number is inappropriate, a message prompting the user to re-enter the reservation number is displayed. For example, if the collation fails 5 times, the user may be prohibited from using the corresponding seat as check-in is not possible. Alternatively, a warning may be issued to prompt a store employee to handle the situation (for example, notify the store terminal (not shown) of the reservation number collation failure and immediately send a warning notice (message) to the corresponding seat to prompt the employee to go there). And, for example, the store employee can also press the seat occupancy button on the available seat display screen after the reservation is cancelled and the seat usage status becomes "available", and allow the user to use the seat.

[0068] (viii) The S708 UI data generation unit 40111 changes the UI display of the tablet terminal 401-k from the reserved seat display to the in-use display screen. (ix) When the collation of the reservation number is successful, the S709 UI data generation unit 40111 activates a timer (not shown) and counts the time.

[0069] (x) The S710 UI data generation unit 40111 determines whether a predetermined time A (for example, 60 minutes) has elapsed since the timer was activated. If the predetermined time A has not elapsed yet (NO in S710), the process returns to S709 and the time count by the timer continues. On the other hand, if the predetermined time A has elapsed (YES in S710), the process proceeds to S711.

[0070] (xi) After the elapse of the predetermined time A, the S711 UI data generation unit 40111 starts the volume-based charging for determining the seat usage fee according to the seat usage time (the time exceeding 60 minutes), displays "Volume-based charging in progress" on the usage display screen, and alerts the user to the start of volume-based charging.

[0071] (xii) The S712 UI data generation unit 40111 uses the communication unit 4014 via the communication control unit 40113 to notify the management server 200 that the seat has shifted to the volume-based charging system, and sends a request to check whether there is an empty seat (empty seat information) in other seats of the store 400. In response to the notification of the start of the volume-based charging, the management server 200 may add information (for example, a flag, not shown in FIG. 3) indicating that the seat of the store 400 in the seat usage status management database 2410 is "under volume-based charging". Also, in response to the empty seat check request, the management server 200 checks the presence or absence of empty seats in the store 400 from the seat usage status management database 2410 and sends the check result to the tablet terminal 401-k that sent the request. If there is a store management terminal 402 that manages the usage status of each seat in the store 400, the empty seat information may be obtained from the store management terminal 402.

[0072] (xiii) When the communication unit 4014 receives the check result of the presence or absence of an empty seat from the management server 200, the UI data generation unit 40111 determines whether there is an empty seat in other seats of the store 400 based on the check result. If there is no empty seat (NO in S713), the process proceeds to S714. If there is an empty seat (YES in S713), the process proceeds to S715.

[0073] (xiv) S714 UI Data Generation Unit 4011 1 reads, for example, the departure promotion UI data from the memory 4015 and superimposes and displays the departure promotion UI on the in - use display screen.

[0074] (xv) S715 UI Data Generation Unit 40111 determines whether the departure button displayed on the in - use display screen has been pressed by the user. If the departure button has not been pressed yet (NO in S715), the process proceeds to S716. If the departure button has been pressed (YES in S715), the process proceeds to S717.

[0075] (xvi) S716 UI Data Generation Unit 40111 activates the timer (not shown) again, starts the time count, and determines whether a predetermined time B (for example, 5 minutes) has elapsed. If the predetermined time B has not elapsed yet (NO in S716), the process returns to S715. In this case, the timer count continues. On the other hand, if the predetermined time B has elapsed (YES in S716), the process proceeds to S712.

[0076] (xvii) S717 UI Data Generation Unit 40111 executes the over - time fee settlement procedure when there is an over - time, and changes the display screen of the tablet terminal 401 - k from the in - use display screen to the vacant - seat display screen. The over - time settlement procedure can take forms such as, for example, making a settlement at the seat (QR settlement, etc.), displaying the over - time fee on the display screen, and displaying a message prompting settlement at the cashier counter. Alternatively, similar to accepting an extension of the seat reservation time, the settlement information can be used by referring to the user table 2420 to accept the settlement. Also, the communication control unit 40113 uses the communication unit 4014 to notify the management server 200 that the usage status of the seat has changed from "in use" to "vacant". Then, the process proceeds to S701. Note that the management server 200 that has received the notification changes the usage status 2417 of the target seat in the seat usage status management database 2410 from "in use (2)" to "vacant (0)".

[0077] <Example of Screen Configuration at Seat Reservation in User Terminal 300> FIG. 8 is a diagram showing an example of a UI screen configuration displayed on the screen of user terminal 300 when a user reserves a seat at store 400 in the first embodiment. FIG. 8(a) is a diagram showing an example of the configuration of a store selection UI screen 801 that displays a group of stores corresponding to a store search request transmitted to management server 200 and their vacancy information. Although FIG. 8(a) shows a list display configuration, it may be configured to display each store as a pin on a map. The store selection UI screen 801 according to FIG. 8(a) is composed of a list of store information 8011-1 to 8011-n. Each store information 8011-k (k is an integer from 1 to n) includes a store name (such as Café A) and the distance and required time from the current position of user terminal 300 (the position at the time of request transmission). The distance and required time are calculated by management server 200 based on the position information of user terminal 300 (information included in the store search request) and the location information of the store. When one store is selected by the user from the store selection UI screen 801, the information of the selected store is transmitted to management server 200, and the seat attribute status information and their usage status information of the selected store are transmitted from management server 200 (FIG. 8(b)).

[0078] FIG. 8(b) is a diagram showing a configuration example of a seat attribute selection UI screen 802 that displays seat attribute status information of a store selected by a user. The seat attribute selection UI screen 802 according to FIG. 8(b) is composed of seat attribute status information 8021-1 to 8021-n indicating whether there is availability for each seat type. Each of the seat attribute status information 8021-1 to 8021-n includes, for example, information (1-person counter seat, 2-person table seat, 4-person table seat, 4-person sofa seat, 1-person booth seat, etc.) 8022-1 to 8022-n indicating the attribute (type) of the seat, displays 8023-1 to 8023-n indicating the usage status (availability or in use: reservation in progress is included in in use), facility information 8024-1 to 8024-n indicating the facilities available at the seat, and image images 8025-1 to 8025-n of the type of the seat. When an available seat attribute is selected by the user from the seat attribute selection UI screen 802, the information of the selected seat attribute is transmitted to the management server 200. When the management server 200 receives (reservation reception) the information of the seat attribute from the user terminal 300, it assigns a reservation number (password) to the reservation and finalizes the reservation. Then, a reservation completion notification including the reservation number is transmitted from the management server 200 to the user terminal 300.

[0079] FIG. 8(c) is a diagram showing a configuration example of a reservation completion notification 803 displayed on the display screen of the user terminal 300. The reservation completion notification 803 includes information 8031 of the reserved seat, rule information 8032 regarding the reservation, a cancel button 8033 for canceling the reservation, and an extension button 8034 for extending the seat reservation by 10 minutes. The seat information 8031 includes the attribute of the seat, the seat / table number, the usage number (reservation number), and the remaining reservation time (e.g., counting down from 15 minutes) indicating the time (remaining time) for which the seat is reserved by the reservation. Also, as the rule information 8032 regarding the reservation, it is displayed that the reservation will be canceled if the user does not arrive at the store within a predetermined time (15 minutes) after the reservation is completed, the usage time is 60 minutes, and the user needs to enter the usage number into the tablet terminal 401-k of the seat (table) after arriving at the store.

[0080] <Example of the Display Screen Configuration of the Tablet Terminal 401-k in Store 400> FIG. 9 is a diagram showing an example of the display screen configuration of the tablet terminal 401-k according to the seat usage status. FIG. 9(a) is a diagram showing an example of the configuration of the display screen 901 when the seat is vacant. The display screen 901 when the seat is vacant includes a table number 9011, a seating button 9012, and a usage rule display 9013. A user who comes to the store without a reservation can use the seat by pressing the seating button 9012 on the screen when there is a vacant seat. When the seating button 9012 is pressed, the screen of the tablet terminal 401-k changes to the in-use display screen 903 (FIG. 9(c)).

[0081] FIG. 9(b) is a diagram showing an example of the configuration of the display screen 902 during reservation. The display screen 902 during reservation includes a table number 9021, a usage start button 9022, a reserved display 9023, and a usage number (reservation number) input field 9024. A user with a reservation who comes to the store within the above-mentioned secured time (15 minutes) inputs the usage number (reservation number) given by the management server 200 at the time of reservation into the usage number input field 9024 on the screen of the tablet terminal 401-k placed at the seat / table reserved by the user. Then, when the usage start button is pressed, the screen of the tablet terminal 401-k changes to the in-use display screen 903 (FIG. 9(c)).

[0082] FIG. 9(c) is a diagram showing an example of the configuration of the display screen 903 during use. The display screen 903 during use includes a table number 9031, a leaving button 9032, and a current usage time display 9033. When a user using the seat presses the leaving button 9032 when leaving the seat, the screen changes to the display screen 901 when the seat is vacant (FIG. 9(a)). Also, when the usage time 9033 elapses for a predetermined time (60 minutes), a reminder screen is displayed (FIG. 9(d)).

[0083] FIG. 9(d) is a diagram showing a configuration example of a reminder screen display 904 that prompts a user to leave after a predetermined time (60 minutes) defined by the seat usage rules and indicates a transition to a per-use charging system in which an overcharge is incurred. The reminder screen display 904 includes a table number 9041, a leave button 9042, a usage time & overcharge occurrence display 9043 indicating that the usage time has elapsed 60 minutes and an overcharge has occurred under the per-use charging system, and a reminder message (leave promotion message) 9044. When the user presses the leave button 9042 in response to the reminder message, the display screen changes to the display screen 901 (FIG. 9(a)) when the seat is vacant.

[0084] As described above, when there is a change in the seat usage status on each tablet terminal 401-k of each seat, the screen display changes. In addition to that, a change in the usage status (vacant → in use, reserved → in use, in use → vacant) is transmitted to the management server 200, and the usage status 2417 in the seat usage status management database 2410 is updated.

[0085] <Summary of the First Embodiment> In the first embodiment, when a user makes a reservation to secure a seat at a specific store from their user terminal 300 and ensure a predetermined time starting now, if there is a possibility that the user may not be able to arrive at the store seat within the time, the management server 200 accepts a paid extension. While the seat is secured, it is displayed on the tablet terminal of the secured seat as "Reserved", but when extended, the time displayed as "Reserved" can be lengthened. By enabling the extension of the seat securing time in this way, when the user is delayed in moving due to some reason more than expected, the user can secure the seat for a longer time. Also, while checking the remaining time, the user can simply tap the area where "Extension" is desired on the user terminal 300, and the time displayed as "In Use" on the tablet terminal of the secured seat is extended, so the seat reservation can be extended without complicated operations. Furthermore, for the facility, instead of setting a long seat securing time for all users, by setting a short time when initially accepting seat reservations, users who can arrive at the facility quickly can be encouraged to move promptly. Also, by accepting a paid extension of seat reservation for users who intend to use the facility, the facility can obtain revenue instead of the sales of the store's products.

[0086] Note that in this embodiment, the extension of the seat securing time is accepted only once, but it may be repeated or accepted up to a predetermined number of times. In that case, after the management server 200 notifies the user 300 that the settlement process has been completed, the display control unit 3102 of the user terminal 300 displays the extension button again on the display unit 320 together with the fact that the settlement has been completed and the remaining time of the seat reservation. Also, each time a request for extension is received, the fee can be increased. In this case, the management server 200 can, for example, notify the user terminal 300 of the amount corresponding to the number of extensions as the fee for the next extension when notifying that the settlement process has been completed.

[0087] In the above explanation, the reservation information and extension information are sent to the tablet terminal of the corresponding seat ID, but for example, the management server 200 may store the end time of the time for which each seat is reserved (the time for which the status is reserved) in the store table 2410. In this case, when the management server 200 updates the end time of the time for which the seat is reserved, it only needs to notify the corresponding tablet terminal of the updated end time.

[0088] <Modification of the First Embodiment> Furthermore, in S609, the management server 200 may accept a reservation on the condition that the same user has not repeatedly made unnecessary reservations within a short period of time. When the management server 200 receives reservation information from the user terminal 300, it searches for reservation information (hereinafter referred to as past reservation information) with the same user ID as the received user ID from past reservation information (hereinafter referred to as reservation history information) stored in the storage device 240. If the same user ID is not present, the management server 200 accepts the received reservation information and executes assignment and transmission of a reservation number. If the same user ID is present, the management server 200 identifies the reservation acceptance time of the most recent reservation information among the past reservation information, and judges whether a predetermined time (for example, one hour) has passed since the current reception time. If the predetermined time has passed, the management server 200 accepts the received reservation information, and if there is past reservation information accepted within the predetermined time, it notifies the user terminal 300 that the reservation cannot be accepted. In this way, a system can be provided that reduces reservations by users who do not intend to use the facility and supports the facility by charging for an extension of seat reservation based on the facility's intention.

[0089] (2) Second embodiment In the second embodiment, an embodiment will be described in which the seat reservation time can be extended depending on the congestion state of the store. It can manage whether the tablet terminal 401 is installed and being used. Therefore, the management server 200 can calculate the congestion situation of the store by referring to the store table 2410. When the management server 200 indicates that the congestion situation is congested, it shall not accept the extension of the seat reservation time from the user. When the management server 200 indicates that the congestion situation is vacant, it shall accept the extension of the seat reservation time from the user. Note that the first embodiment is mainly different in the extension acceptance process in S613. Hereinafter, the differences from the first form will be described, and the description of the same processes as those in the first embodiment will be omitted.

[0090] <Extension Acceptance Process in Management Server 200> FIG. 10 shows a flowchart of the extension acceptance process in the second embodiment. (1) S1001 When the reception unit 211 of the management server 200 receives request information regarding extension from the user terminal 300, first, the management server 200 calculates the congestion rate of the target store. In this form, the ratio of the tablet terminals among the tablet terminals 401-k corresponding to the store that are in use or reserved is calculated. (2) S1002 The management server 200 compares the congestion rate of the store with a pre-set threshold value and determines whether the congestion rate is less than the threshold value. For example, a threshold value such as 95% is set. When the threshold value is set to 100, the extension will not be accepted when the store is full. If the congestion rate is less than the threshold value in S1002, the process proceeds to S1003. If it is greater than or equal to the threshold value, the process proceeds to S1004.

[0091] (3) S1003 The management server 200 refers to the reservation information included in the request information and determines whether there is a reservation specified by the user terminal 300 in the storage device 240. If there is a reservation, the process proceeds to S1004. If there is no reservation, the process proceeds to S1005. (4) S1004 The management server 200 obtains the payment method of the user ID included in the request information from the user table 2420 and uses the communication device 250 to notify the user terminal 300 that the extension is accepted and of the payment method.

[0092] (5) When the management server 200 determines that the store is congested or cannot confirm a reservation for which an extension request has been received, it notifies the user that the extension cannot be accepted. At this time, text data indicating the reason for the non - acceptance of the extension shall be notified together.

[0093] <Example of the screen configuration of the seat reservation extension request result on the user terminal 300> FIG. 11 is a diagram showing an example of the UI screen configuration displayed on the screen of the user terminal 300 when the user requests an extension of the seat reservation time in the store 400 in the second embodiment but the extension is not accepted. FIG. 11(a) is a diagram showing an example of the configuration of the screen 1101 displayed when the extension of the reservation time cannot be accepted because the store is congested. At this time, it indicates that the extension cannot be made due to congestion and prompts the user to choose whether to cancel or not. Thus, when it is clear that the user cannot arrive within the reserved time, the user can be prompted to release the seat earlier. Also, FIG. 11(b) is an example of the configuration of the screen 1105 displayed when the reservation verification fails. Although such cases rarely occur, they can occur, for example, when the cancellation has already occurred after a predetermined reservation time has passed. By displaying different screens in the cases of FIG. 11(a) and FIG. 11(b), the reason for the non - extension can be presented to the user.

[0094] <Summary of the second embodiment> In the second embodiment, it is determined whether to accept the extension of the time for which the user has reserved a seat in a specific store according to the congestion situation. Specifically, the extension is not accepted when the store is congested, and the extension is accepted when the store is not congested. By changing the tablet terminal 401 placed on the seat from "reserved" to "vacant", the seat can be released, for example, when waiting for the use of the seat, reducing the time during which the seat in the store is reserved but not used, and promoting the preferential use of the seat for the people who have already arrived at the store.

[0095] <Modification of the second embodiment> In the second embodiment described above, the extension of the seat reservation time is not accepted according to the congestion rate. However, it is also possible to configure the system to accept the extension for a user who wants to extend the seat reservation time at a fee according to the congestion rate. In this case, S1002 is a different process. For example, in S1002, the extension fee is calculated using information (table or calculation formula) indicating the amount for each congestion rate set in advance. If the congestion rate is below a threshold, the fee is set to 200 yen, and if it is above the threshold, the fee is set to 400 yen. Alternatively, multiple thresholds may be set, and the fee may be set in three or more stages, such as if the congestion rate is below a first threshold, if it is above the first threshold and below a second threshold, and if it is above the second threshold. (In this case, there is no branch from S1002 to S1005.) Then, when notifying S1004, the fact that the extension is accepted is notified along with the amount of the extension. This makes it possible to charge for seat reservation in a crowded situation, which leads to support for the operation of the store.

[0096] In addition, the management server 200 has been described as calculating the congestion rate based on the usage status information of each tablet terminal installed corresponding to the equipment of the store, but the present invention is not limited to this. In addition to the tablet terminals corresponding to the equipment, there may be another terminal that transmits congestion information in the store to the management server 200. For example, the management server 200 may determine the congestion state by detecting users using a camera that captures images in the store or a sensor installed in the equipment, or a dedicated input device (such as a tablet terminal, smartphone, or dedicated button terminal) that allows the store manager to visually check the inside of the store and input the congestion state may be used, or the management server 200 may collect the congestion state of the store using a system that manages queues for waiting to use Kochi's stores.

[0097] (3) Third Embodiment In the second embodiment, whether to accept an extension was determined according to the congestion rate inside the store. In this system, the management server 200 can manage the usage status of each seat, and information regarding the seat attributes of each seat is also stored in the database 241. Therefore, in the third embodiment, when receiving an extension request from the user terminal 300, whether to accept the extension may be determined according to the congestion rate of the seat attributes of the target seat.

[0098] <Extension Acceptance Processing in the Management Server 200> FIG. 12 shows a flowchart of the extension acceptance processing in the third embodiment. Here, although the verification of reservation information is omitted, similar to the first and second embodiments, a process of checking whether there is reservation information requested before notifying the acceptance of the extension may be included. (1) S1201 The management server 200 refers to the reservation information included in the extension request information from the store table 2410 to identify the table / seat attributes of the seat to be extended. Then, from the store table 2410, seats with the same table / seat attributes as the identified table / seat attributes are searched, and the usage status of each seat is obtained.

[0099] (2) S1202 The management server 200 determines whether there is a seat with an available status in the seat group with the table / seat attributes identified in S1201. If there is another available seat with the same seat attributes, it proceeds to S1203; if there is no other available seat with the same seat attributes, it proceeds to S1204. (3) S1203 The management server 200 obtains the payment method of the user ID included in the request information from the user table 2420, and uses the communication device 250 to accept the extension and notify the user terminal 300 of the payment method.

[0100] (4) S1204 When the store is congested or when the reservation for which the extension request was received cannot be confirmed, the management server 200 notifies the user that the extension cannot be accepted. At this time, text data indicating the reason for not being able to extend, etc. shall be notified together.

[0101] <Screen Configuration Example of Seat Reservation Extension Request Result in User Terminal 300> In this embodiment, since there is no vacancy in the seat attribute for which the extension request was made, the extension is not accepted, and there may be sufficient vacancies in other seat attributes. Therefore, for example, instead of the text data "The store is currently crowded, so the reservation time could not be extended." shown in Fig. 11(a), the text data "The reserved single-person booth seat is currently crowded, so the reservation time could not be extended." may be displayed. In addition to the text data "Do you want to cancel?" and the cancel button 8033, the text data "Look for other types of seats" may be displayed, and the process may be restarted from the process of displaying Fig. 8(b).

[0102] <Summary of the Third Embodiment> In the third embodiment, when a request is made to extend the time for reserving a specific seat in the store from the user terminal 300, it is determined whether to accept the request according to the congestion rate (presence or absence of vacant seats and utilization rate) in the seat group with the same seat attribute as the requested seat. As a result, the time when the seats with the congested seat attribute cannot be used can be reduced as much as possible, and the seats can be released.

[0103] <Modification Example of the Third Embodiment> As the acceptance setting for extension for each seat attribute, not only the determination of acceptance or non-acceptance according to the congestion rate but also a method of setting in advance whether to accept the extension for each seat attribute may be used. In this case, after identifying the seat attribute of the seat included in the extension request information, it may be determined whether to accept the extension by determining whether the identified seat attribute is set to be able to accept the extension. Further, a fee for extension for each seat attribute may be set, and the management server 200 may accept the extension and notify the user terminal 300 of the fee according to the seat attribute.

[0104] <Others> In the above-described embodiment, if it is within the reservation time for securing a specific seat, a request for extension is accepted. However, for example, a request for extension may be accepted only when the remaining time of the seat reservation time becomes short (for example, less than 2 minutes). Specifically, as a UI displayed on the screen of the user terminal 300, the display of the button area (8034) of "Extend the reservation time by 10 minutes" may be controlled not to be displayed until the remaining time reaches 2 minutes, and to be displayed when it becomes less than 2 minutes. That is, as a condition for accepting an extension, in the first embodiment, it refers to being within the reservation time and the settlement of the cost for the extension being completed, and in the second embodiment, it further refers to the congestion situation of the store. However, alternatively, the short remaining time may be used as a condition for accepting an extension.

[0105] As described above, the technology of the present disclosure can be realized by supplying a program that realizes one or more functions of the above-described embodiment to a system or device via a network or a storage medium, and by a process in which one or more processors in the computer of the system or device read and operate the program. Alternatively, it may be realized by a circuit that realizes one or more functions.

Description of Reference Numerals

[0106] 10 Management system 200 Management server 210 CPU (Processor) 220 ROM 230 RAM 240 Storage device 250 Communication device 300 User terminal 400 Store 402 Store management terminal 401-k (k = 1 to n) Tablet terminal 4011 CPU (Processor) 4012 Display unit 4013 Input unit 4014 Communication unit 4015 Memory

Claims

1. An information processing apparatus that manages usage status information indicating the usage status of each of a plurality of provided facilities, and a facility terminal installed in the facility and having a display unit, comprising: The information processing apparatus: A management means for managing the usage status information for each facility; A transmission means for transmitting the usage status information to the facility terminal; and has, When the management means receives a request for securing the facility from the user terminal, it selects one of the facilities, changes the usage status information of the selected facility to information indicating reservation, and when the transmission means transmits the information indicating reservation to the facility terminal, the facility terminal displays a reservation screen indicating reservation on the display unit for a first predetermined time. Furthermore, when receiving a request for extension of reservation from the user terminal, if there are a predetermined number of available facilities among the facilities other than the facility secured by the user terminal, it accepts the extension, and the transmission means transmits information regarding the extension to the facility terminal, and the facility terminal adds and displays the time for which the reservation screen is displayed on the display unit by a second predetermined time. A management system characterized by this.

2. The management means calculates the congestion rate of the facility where the plurality of facilities are installed, and determines whether to accept the extension by determining whether the congestion rate is less than a predetermined threshold value. The management system according to claim 1, characterized by this.

3. An information processing apparatus that manages availability information of facilities provided by a facility, and a facility terminal installed in the facility and having a display unit, comprising: The information processing apparatus: A storage means for storing usage status information indicating the usage status of each facility; A management means for managing the usage status information; A transmission means for transmitting the usage status information to the facility terminal; It has a settlement means for executing settlement processing from a user terminal, When the management means receives a request for securing the facility from the user terminal, it selects one of the facilities, changes the usage status information of the selected facility to information indicating reservation, and when the transmission means transmits the information indicating reservation to the facility terminal, the facility terminal displays a reservation screen indicating reservation on the display unit for a first predetermined time. When receiving a request for extension of reservation from the user terminal, if the payment process for the cost required for the extension is completed, the extension is accepted, the transmission means transmits information regarding the extension to the facility terminal, and the facility terminal adds and displays on the display unit the time for displaying the in-reservation screen for a second predetermined time. A management system characterized by this.

4. Furthermore, the management means specifies the attributes of the facility that is the target of the request, and determines whether to accept the extension based on the usage status information of the group of facilities with the specified attributes. The management system according to any one of claims 1 to 3, characterized by this.

5. An information processing apparatus that is communicably connected to a facility terminal corresponding to a facility provided by a facility, and manages usage status information regarding the usage status of the facility set in the facility terminal, The usage status includes available, in use, and in reservation. Storage means for storing the usage status information; Management means for managing the usage status information based on data transmitted from a user terminal or the facility terminal; Transmission means for transmitting the usage status information to the facility terminal, and has The management means updates the usage status information corresponding to a specific facility to information indicating in reservation in response to a request from the user terminal, and transmits the information indicating in reservation to the facility terminal corresponding to the specific facility. Furthermore, when receiving a request from the user terminal to extend the reserved time for the specific facility, if there are a predetermined number of available facilities among the facilities other than the facility reserved by the user terminal, the transmission means transmits information instructing the extension of the reserved time to the facility terminal corresponding to the specific facility. An information processing apparatus characterized by this.

6. An information processing apparatus that is communicably connected to a facility terminal corresponding to a facility provided by a facility, and manages usage status information regarding the usage status of the facility set in the facility terminal, The usage status includes available, in use, and in reservation. Storage means for storing the usage status information; Management means for managing the usage status information based on data transmitted from a user terminal or the facility terminal; Transmission means for transmitting the usage status information to the facility terminal; It has payment means for executing a payment process from the user terminal. In response to a request from the user terminal, the management means updates the usage status information corresponding to the specific facility to information indicating reservation in progress, and transmits the information indicating reservation in progress to the facility terminal corresponding to the specific facility. Furthermore, when receiving a request from the user terminal to extend the reserved time for the specific facility, if the settlement process for the cost required for the extension is completed, the extension is accepted, and the transmission means transmits information instructing the extension of the reserved time to the facility terminal corresponding to the specific facility. An information processing apparatus characterized by this.

7. A program for causing a computer to function as the information processing apparatus according to any one of claims 1 to 6.

8. An information processing method for managing usage status information regarding the usage status of a facility set in a facility terminal communicably connected to a facility provided by a facility, which is executed by a computer, comprising: The usage status includes available, in use, and reserved. A management step of managing the usage status information based on data transmitted from a user terminal or the facility terminal; A transmission step of transmitting the usage status information to the facility terminal; and having In the management step, in response to a request from the user terminal, the usage status information corresponding to the specific facility is updated to information indicating reservation in progress, and the information indicating reservation in progress by the transmission step is transmitted to the facility terminal corresponding to the specific facility. Furthermore, when receiving a request from the user terminal to extend the reserved time for the specific facility, if there are a predetermined number of available facilities among the facilities other than the facility secured by the user terminal, the transmission step transmits information instructing the extension of the reserved time to the facility terminal corresponding to the specific facility. An information processing method characterized by this.

9. An information processing method for managing usage status information regarding the usage status of a facility set in a facility terminal communicably connected to a facility provided by a facility, which is executed by a computer, comprising: The usage status includes available, in use, and reserved. A management step of managing the usage status information based on data transmitted from a user terminal or the facility terminal; A transmission step of transmitting the usage status information to the facility terminal; A settlement step of executing a settlement process from the user terminal; and having The management step updates the usage status information corresponding to a specific facility to information indicating reservation in response to a request from the user terminal, and transmits the information indicating reservation by the transmission step to the terminal for the facility corresponding to the specific facility. Furthermore, when receiving a request from the user terminal to extend the secured time during which the specific facility is reserved, if the settlement process for the cost required for the extension is completed, the extension is accepted, and the transmission step transmits information instructing the extension of the secured time to the terminal for the facility corresponding to the specific facility. An information processing method characterized by the above.

Images