JP7847375B2 - Service delivery system, program, server program, and terminal program - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act: On December 3, 2021, Accea Co., Ltd. made available to app members the download of a "program" invented by Tadashi Yoshida on its website (https://spot.accea.co.jp).

This invention relates to a service provision system that provides users with a service to rent out space located within a store.

Application programs that match users with each other (so-called matching apps) are known (see, for example, Patent Document 1). Matching apps are implemented on terminal devices owned by users and communicate with a management server. The management server matches users based on information collected from the matching app, such as occupation, hobbies, residential area, age, and gender.

Some matching apps offer a service that provides spaces for users to meet in person (see, for example, Patent Document 2). Users visit the store that rents out the space and scan a QR code installed in the store with their terminal device. Once the terminal device scans the QR code, the matching app communicates with a management server. The matching app receives input such as the usage time and sends the received usage time and other information to the management server to submit a usage request (so-called check-in).

Japanese Patent Publication No. 2010-152477 Japanese Patent Publication No. 2021-165974

For example, the user scans a QR code installed in the store with a terminal device upon leaving. Once the terminal device scans the QR code, the matching app communicates with the management server and notifies the server that the user's usage has ended at the current time (so-called check-out). The management server determines the usage fee based on the check-in and check-out times and processes the payment.

If a user forgets to check out and leaves the store, the management server will be unable to process the payment.

This invention was made in view of the above circumstances, and its purpose is to provide a service provision system that allows for proper payment even if the user forgets to check out before leaving the store.

(1) The service provision system according to the present invention comprises a management server equipped with a first communication interface, a first memory, and a first controller, and a terminal device equipped with a second communication interface, a second memory, an input interface, a camera, a display, and a second controller. The second controller performs a first acquisition process for acquiring store identification information indicated by a code image captured by the camera, a first reception process for receiving check-in information input through the input interface, and a first transmission process for transmitting a usage application including the store identification information, the check-in information, and user identification information to the management server via the second communication interface and the internet. The second controller is capable of performing a second reception process for receiving check-out instructions input through the input interface, and a second transmission process for transmitting a termination notice including the store identification information and user identification information to the management server via the second communication interface and the internet based on the acceptance of the check-out instructions. The first controller performs the following processes: a first reception process to receive the application for use through the first communication interface; a check-in time determination process to determine the check-in time based on the time corresponding to the transmission or reception time of the application for use, or the scheduled start time of use indicated by the check-in information; an end time determination process to identify the scheduled end time of use based on the determined check-in time and the check-in information; a forced check-out time determination process to determine a forced check-out time that is later than the scheduled end time of use; and a check-out time determination process. The check-out time determination process, based on the receipt of the end notification, determines the check-out time based on the time corresponding to the transmission or reception time of the end notification, or the scheduled end time of use; and, based on the current time being the forced check-out time and the fact that the end notification has not been received, determines the forced check-out time as the check-out time.

Upon entering the store, the user scans a code image displayed in the store using a terminal device and enters check-in information such as room number and usage time into the terminal device to complete check-in. Upon leaving the store, the user scans a code image displayed in the store using a terminal device and enters information such as selecting an icon to complete check-out. The terminal device sends a completion notification to the management server in response to the check-out instruction. The management server determines the check-out time based on the time the completion notification is sent or received, or the scheduled end time at the time of reservation. Payment is processed based on the determined check-out time. Furthermore, in case the user forgets to check out before leaving, a mandatory check-out time is set at check-in or after the scheduled end time has elapsed. If check-out is not completed by the mandatory check-out time, the mandatory check-out time is set as the check-out time. Therefore, even if the user forgets to check out, payment can still be processed.

(2) The forced check-out time determination process described above may include: a store type identification process that identifies whether the store indicated by the store identification information is a first-type store with a closing time or a second-type store without such a closing time; and a process that, based on the identification of the store as a first-type store, determines the closing time as the forced check-out time, and based on the identification of the store as a second-type store, determines the forced check-out time to be a time that is a predetermined time stored in the first memory after the scheduled end time of use, or a predetermined time stored in the first memory.

If the store where the user checks in has a closing time, that closing time is determined as the mandatory check-out time. If the store where the user checks in is a so-called 24-hour store without a closing time, the mandatory check-out time is determined as a predetermined time one hour after the scheduled end time of use, or at a predetermined time such as midnight (0:00). Therefore, an appropriate mandatory check-out time can be determined according to the type of store.

(3) The first controller may further perform a third transmission process, which involves sending a confirmation notice to the terminal device via the first communication interface and the Internet, based on the fact that the checkout time has not been determined and the elapsed time from the scheduled end time of use has reached the second predetermined time stored in the first memory. The second controller performs a second reception process to receive the confirmation notice and a display process to display the confirmation screen indicated by the confirmation notice on the display.

If checkout has not been completed within two predetermined hours from the scheduled end time, the management server sends a confirmation notification to the terminal device and displays a confirmation screen on the terminal device's display. This confirmation screen prompts the user to confirm, for example, whether they have extended their usage period and are still using the space, or whether they have forgotten to check out and left the premises. The display of this confirmation screen on the terminal device's display allows the server to prompt the user to check out if they have forgotten to do so.

(4) The second controller may further execute a fourth transmission process to acquire location information and transmit it to the management server via the second communication interface and the Internet. The first controller further executes a process to calculate the distance between the location indicated by the received location information and the store location indicated by the store identification information; a first determination process to determine whether the distance is less than a threshold distance stored in the first memory; and a first stop process to stop the execution of the third transmission process based on the determination that the distance is less than the threshold distance.

According to the above configuration, if the user is inside or near the store, no confirmation notification will be sent to the terminal device.

(5) The second controller may, while the confirmation screen is being displayed, accept either a usage continuation instruction input indicating that the user is continuing to use the store, or a checkout instruction input, and execute a fifth transmission process to send instruction information indicating the said instruction input to the management server via the second communication interface and the Internet. The first controller may , based on the fact that it has not received the instruction information by the time elapsed since the execution of the third transmission process reaches the third predetermined time stored in the first memory, execute the third transmission process again.

According to the above configuration, if the user does not respond to the confirmation notice, the confirmation notice will be resent to the terminal device after a predetermined time period has elapsed. As a result, it is possible to more reliably prompt the user to check out.

(6) The first controller may further execute a third receiving process to receive the instruction information. The checkout time determination process includes determining the transmission or reception time of the instruction information as the checkout time, based on the fact that the received instruction information indicates the checkout instruction input.

If a user forgets to check out, they will enter a checkout instruction on the confirmation screen. The checkout time will be determined based on the time the checkout instruction is entered, and payment will be processed accordingly.

(7) The first controller may further execute a second determination process to determine whether the current time has passed the scheduled end time. Based on the determination that the current time has passed the scheduled end time, the forced checkout time determination process is executed.

(8) The program according to the present invention comprises a server program implemented in a management server having a first communication interface, a first memory, and a first controller, and a terminal program implemented in a terminal device having a second communication interface, a second memory, an input interface, a camera, a display, and a second controller. The terminal program causes the second controller to execute a first acquisition process for acquiring store identification information indicated by a code image captured by the camera, a first reception process for receiving input of check-in information through the input interface, and a first transmission process for sending a usage application including the store identification information, the check-in information, and user identification information to the management server via the second communication interface and the internet. The terminal program causes the second controller to execute a second reception process for receiving input of a check-out instruction through the input interface, and a second transmission process for sending a completion notification including the store identification information and user identification information to the management server via the second communication interface and the internet based on the acceptance of the check-out instruction . The server program instructs the first controller to execute the following: a first reception process that receives the above-mentioned application for use through the first communication interface; a check-in time determination process that determines the check-in time as the time corresponding to the transmission or reception time of the application for use, or the scheduled start time of use indicated by the check-in information; an end time determination process that identifies the scheduled end time of use based on the determined check-in time and the check-in information; a forced check-out time determination process that determines a forced check-out time which is a time later than the scheduled end time of use; and a check-out time determination process. The check-out time determination process determines the check-out time as the time corresponding to the transmission or reception time of the termination notice, or the scheduled end time of use, based on the receipt of the termination notice, and determines the forced check-out time as the check-out time based on the fact that the current time is the forced check-out time and the termination notice has not been received.

(9) The server program according to the present invention is implemented in a management server equipped with a communication interface, server memory, and a controller. The server program causes the controller to execute a first reception process which receives a usage application transmitted by a terminal device, which includes store identification information, check-in information, and user identification information, via the communication interface; a check-in time determination process which determines the check-in time as a time corresponding to the transmission or reception time of the usage application, or the scheduled start time of use indicated by the check-in information; an end time determination process which identifies the scheduled end time of use based on the determined check-in time and the check-in information ; a forced check-out time determination process which determines a forced check-out time which is a time later than the scheduled end time of use; and a check-out time determination process. The check-out time determination process determines the check-out time as a time corresponding to the transmission or reception time of the end notice transmitted by the terminal device, or the scheduled end time of use, based on the fact that the current time is the forced check-out time and that the end notice has not been received.

(10) The terminal program according to the present invention is implemented in a terminal device comprising a communication interface, terminal memory, input interface, camera, display, and controller. The terminal program causes the controller to execute a first acquisition process for acquiring store identification information indicated by a code image captured by the camera; a first reception process for receiving input of check-in information through the input interface ; and a first transmission process for sending a usage application including the store identification information, the check-in information, and user identification information to a management server via the communication interface and the internet. The terminal program also causes the controller to execute a second reception process for receiving input of a check-out instruction through the input interface; a second transmission process for sending a termination notice including the store identification information and user identification information to the management server via the communication interface and the internet based on the receipt of the check-out instruction; and a payment confirmation process for receiving a payment notification from the management server indicating that payment has been made using the forced check-out time, and displaying a payment confirmation screen showing the payment notification on the display.

(11) The terminal program according to the present invention is implemented in a terminal device comprising a communication interface, terminal memory, input interface, camera, display, and controller. The terminal program causes the controller to execute a first acquisition process for acquiring store identification information indicated by a code image captured by the camera; a first reception process for receiving input of check-in information through the input interface ; a first transmission process for sending a usage application including the store identification information, the check-in information, and user identification information to the management server via the communication interface and the internet; a second reception process for receiving input of a check-out instruction through the input interface; a second transmission process for sending a termination notice including the store identification information and user identification information to the management server via the communication interface and the internet based on the receipt of the check-out instruction; a reception process for receiving a confirmation notice sent by the management server requesting check-out via the internet and the communication interface; a display process for displaying an instruction reception screen showing the received confirmation notice on the display; and a third transmission process for sending the check-out instruction received on the instruction reception screen to the management server via the communication interface and the internet.

(12) The first memory may also store the upper limit time. The forced check-out time determination process is a process that determines the forced check-out time as the time obtained by adding the upper limit time to the check-in time.

Because there is a set limit on the usage time (maximum time) for mandatory checkout, the user will not be charged for usage time exceeding the limit.

(13) The above upper limit time may be stored in the first memory in association with the above store identification information.

The maximum operating time may be set individually for each store.

(14) The first memory may further store the store identification information and the closing time in association. The first controller further executes a third determination process to determine whether the forced checkout time determined in the forced checkout time determination process is later than the closing time, and a forced checkout time re-determination process to re-determine the closing time to the forced checkout time based on the determination in the third determination process that the forced checkout time is later than the closing time.

For stores with a closing time, the mandatory checkout time will never be later than the closing time.

According to this invention, even if a user forgets to check out before leaving the store, payment can still be processed correctly.

Figure 1 is a diagram showing the configuration of the service provision system 10, and is also a functional block diagram of the terminal device 20 and the management server 30. Figure 2 shows the user management database. Figure 3 is a diagram showing the store management database. Figure 4 is a flowchart of the reservation process. Figure 5 shows the screens displayed on the display 24 of the terminal device 20, where (A) is the spot screen, (B) is the registration recommendation screen, (C) is the store selection screen, and (D) is the date and time specification screen. Figure 6 is a flowchart of the check-in process. Figure 7 shows the screens displayed on the display 24 of the terminal device 20, where (A) is the check-in screen, (B) is the reading screen, (C) is the plan selection screen, (D) is the confirmation screen, and (E) is the completion notification screen. Figure 8 is a flowchart of the checkout process. Figure 9 shows the screens displayed on the display 24 of the terminal device 20, where (A) is the checkout screen, (B) is the reading screen, and (C) is the checkout completion notification screen. Figure 10 is a part of the monitoring process flowchart. Figure 11 shows another part of the monitoring process flowchart. Figure 12(A) is a flowchart showing the transmission and reception of location information, and Figure 12(B) is a flowchart showing the process by which the terminal device 20 displays a confirmation screen and a payment confirmation screen. Figure 13 shows the screens displayed on the display 24 of the terminal device 20, where (A) is the first confirmation screen, (B) is the second confirmation screen, (C) is the first payment confirmation screen, and (D) is the second payment confirmation screen. Figure 14 shows a store management database in a modified example. Figure 15 is a flowchart of the monitoring process in a modified example.

The following describes embodiments of the present invention. It should be noted that the embodiments described below are merely examples of the present invention, and the embodiments can be appropriately modified without altering the essence of the invention. For example, some of the processes shown in Figures 4, 6, 8, 10, 11, and 12 may be omitted, their order changed, or replaced with other processes, without altering the essence of the invention. Furthermore, the icons and text displayed on the screens shown in Figures 5, 7, 9, and 13 may be omitted, their display position changed, or replaced with other text boxes, icons, or text, without altering the essence of the invention.

In this embodiment, the service provision system 10 shown in Figure 1 will be described. The service provider uses the service provision system 10 to provide users with services such as matching users with each other and providing booths as a place for users to meet in person. To provide booths to users, the service provider operates multiple stores, each with multiple booths. The purpose of using the booths is not limited to matching users; for example, users may use them for remote work. Furthermore, it is not mandatory for stores to have booths; for example, a store may have a space that can be used jointly by multiple people, such as a co-working space, and such a space may be provided.

The service provision system 10 comprises a management server 30 operated by the service provider and terminal devices 20 owned by each user. The management server 30 is a so-called web server that publishes a URL on the internet, and collects user information from the terminal devices 20 via the internet to match users with each other. On the other hand, the terminal devices 20 are mobile communication terminals such as smartphones (registered trademark) and tablets (registered trademark). Users use the terminal devices 20 to reserve booths, check in, and check out. The configuration of the terminal devices 20 and the management server 30 will be explained in detail below.

The terminal device 20 includes a central processing unit (CPU) 21, memory 22, a communication interface 23, a display 24, an input interface 25, and a camera 29.

The CPU 21 is a central processing unit that executes programs such as the OS 26, browser 27, and terminal program 28 stored in memory 22. The CPU 21 is an example of a second controller and a controller.

The communication interface 23 is an interface that transmits and receives information and data via wireless communication such as mobile communication or Wi-Fi. The communication interface 23 is an example of a second communication interface.

The input interface 25 is, for example, a transparent, film-like touch sensor superimposed on the display 24, or a microphone for voice input.

Camera 29 is a so-called digital camera that has a lens and multiple image sensors, and outputs image data generated by imaging. Camera 29 is used for capturing QR codes (registered trademark).

Memory 22 includes ROM, RAM, internal or external hard disks, and removable portable storage media. A portable storage medium is, for example, a USB memory stick (registered trademark). Memory 22 is an example of a second memory and terminal memory.

Memory 22 stores the operating system (OS 26) and the browser (27). Memory 22 also has a storage area capable of storing the terminal program (28).

The terminal program 28 is a program provided by the service provider to the user. The terminal program 28 may be a so-called application program, or a so-called plug-in application that extends the functionality of the browser 27. Alternatively, the terminal program 28 may be HTML data containing JavaScript.

The user, for example, launches a browser 27 and accesses a URL published by the management server 30, displaying the homepage provided by the service provider on the display 24. On this homepage, the user enters their name, age, gender, address, etc., and applies to join the service provided by the service provider. Based on the application, the management server 30 returns the server address, user ID, and terminal program 28 to the terminal device 20. That is, the server address, user ID, and terminal program 28 are downloaded (installed) to the terminal device 20. The downloaded server address, user ID, and terminal program 28 are stored in memory 22.

The server address is the global IP address assigned to the management server 30. The URL above includes both the server address and the file path to the homepage.

The User ID is identification information that individually identifies the terminal program 28, the terminal device 20, and the user.

The user launches the downloaded terminal program 28 and displays the input screen. On the input screen, the user enters information such as location, occupation, and hobbies (hereinafter referred to as "matching information"). The entered matching information is sent to the management server 30 using the server address. The management server 30 registers the received matching information in the user management database described later. The management server 30 uses the registered matching information to match users and sends information about the other matched users back to the terminal device 20. The user makes requests to the other matched users to actually meet them via the management server 30. After the other matched users agree or accept, the user makes a reservation for a booth at a store operated by the service provider using the terminal program 28. The user also checks in at the store using the terminal program 28, rents the booth, and meets the other matched user. The user also checks out at the store using the terminal program 28 and leaves the store. In other words, the service provider uses the management server 30 and terminal program 28 to provide users with a service that introduces them to other users and a rental booth service that provides them with a booth. On the other hand, the user receives the introduction service and the rental booth service through the terminal program 28.

The management server 30 comprises a CPU 31, memory 32, a communication interface 33, and a clock module 34. The management server 30 may be a server owned by the service provider, or it may be a so-called rental server.

The CPU 31 is a central processing unit that executes programs such as the OS 36 and server programs 37 stored in the memory 32. The CPU 31 is an example of a first controller.

The communication interface 33 is connected to the Internet 11 via a LAN and gateway device, or directly to the Internet 11. The communication interface 33 is an example of a first communication interface.

The clock module 34 is a module that outputs the current time. Alternatively, instead of the clock module 34 being located on the management server 30, the server program 37 may have the function to obtain the current time via the internet 11.

Memory 32 stores the operating system (OS 36), server program 37, user management database, and store management database. Memory 32 is an example of first memory and server memory. Note that the first memory and server memory may also be memory located on other servers, such as storage servers, that are accessible to the management server 30.

The server program 37 includes communication functions for communicating with the terminal device 20, database management functions for managing the user management database and the store management database, a matching function for matching users by reading information registered in the user management database, and reservation and payment functions for booth reservations, check-in, check-out, and payment. The server program 37 may be a collection of multiple modules (programs) that each execute the above functions, or it may be a single program.

As shown in Figure 2, the user management database is a database that manages information about users (upper section), reservation information regarding booth reservations made by users (middle section), and usage information regarding actual use after the use (lower section).

The user management database has multiple columns and multiple records (rows). Each column has a field name. One column is named "User ID". Each field in the column named "User ID" contains the User ID. Each record is individually identified by its User ID; that is, each record corresponds to one user.

When the server program 37 receives the membership application sent by the terminal device 20, it generates a new record in the user management database, generates a unique user ID that is not currently used in the user management database, and registers the generated user ID in the newly generated record.

Other columns in the user management database include fields such as "Name," "Gender," "Age," "Address," "Occupation," "Hobby 1," "Matching User ID," "Affiliated Group," and "Payment Information."

Each field in the column labeled "Name" contains the user's last name and first name. Each field in the column labeled "Gender" contains the user's gender. Each field in the column labeled "Age" contains the user's age. Each field in the column labeled "Address" contains the user's address. The server program 37 registers the user's name, gender, age, and address, which are included in the membership application sent by the terminal program 28, into the respective fields of each column.

The fields in the columns labeled "Occupation" and "Hobby 1" contain the user's occupation and hobbies, respectively. The server program 37 registers the occupation and hobbies included in the matching information transmitted by the terminal program 28 into the respective fields of each column. Note that while Figure 2 only shows the column labeled "Hobby 1," the user management database may contain multiple columns labeled "Hobby 2," "Hobby 3," and so on.

The fields in the columns labeled "Matching User ID" and "Group ID" each contain the User IDs of other users matched with the user (Matching User IDs) and the Group IDs assigned to the groups to which the user belongs. When a user is matched with another user, the server program 37 registers the ID of the matched user as the Matching User ID in the corresponding column. Furthermore, if a user joins an existing group, the server program 37 registers the Group ID assigned to that group in the corresponding column. Alternatively, if a user creates a new group, the server program 37 generates a unique Group ID not yet registered in the user management database and registers the generated Group ID in the corresponding column.

Furthermore, the matching of users, joining groups, and creating new groups may be carried out in any manner.

Each field in the column labeled "Payment Information" will contain the information necessary for automatically processing payments when a user rents a booth (payment information). For example, payment information might include a credit card number and authentication information for identity verification. The card number and authentication information will be registered in the respective fields of the column labeled "Payment Information." However, payment information could also include a bank ID, account number, and authentication information.

If a user wishes to use automatic payment, they provide payment information to the service provider (management server 30) using the terminal program 28. The server program 37 of the management server 30 registers the provided payment information in the user management database.

The user management database has columns with item names such as "Reservation Information 1" and "Reservation Information 2" (not shown). Each field in these columns registers reservation information related to booth reservations made by the user. The user management database may also have columns with item names such as "Reservation Information 3" and "Reservation Information 4." In the following explanation, when the item names "Reservation Information 1," "Reservation Information 2," etc., are not distinguished, they will simply be referred to as "Reservation Information."

The column named "Reservation Information" has multiple subcolumns. These subcolumns are named "Store ID," "Closing Time," "Booth Number," "Reservation Date," "Start Time," "End Time," "Reservation Period," "Service Type," "Check-in Time," "Scheduled End Time," "Check-out Time," "Mandatory Check-out Time," "First Confirmation Notification Time," "Second Confirmation Notification Time," and "Location Information," respectively. The user management database may further have subcolumns named "Third Confirmation Notification Time," "Fourth Confirmation Notification Time," etc. In the following explanation, if "First Confirmation Notification Time," "Second Confirmation Notification Time," etc., are not distinguished, they will simply be referred to as "Confirmation Notification Time."

Each field in the sub-column labeled "Store ID" contains the Store ID, which is the identification information assigned to the store the user reserved.

Each field in the sub-column labeled "Closing Time" contains either the store's closing time or a dash ("-") indicating that it is open 24 hours.

Each field in the sub-column labeled "Booth Number" contains the number assigned to the booth reserved by the user. For example, a user reserves a booth of a size (area) appropriate to the number of people in their party. Note that if the booth is specified during check-in, the sub-column labeled "Booth Number" does not need to be present in the "Reservation Information" column.

Each field in the sub-column labeled "Reservation Date" contains the date the user plans to rent the booth. Each field in the sub-column labeled "Start Time" contains the planned start time of the booth rental period. Each field in the sub-column labeled "End Time" contains the planned end time of the booth rental period. Each field in the sub-column labeled "Reservation Period" contains the rental period the user will be renting the booth. "1h" indicates one hour, and "3h" indicates three hours.

Each field in the sub-column labeled "Service Type" contains the service type set by the service provider. For example, "30h Pack" indicates a service that rents out a booth for 30 hours at a fixed rate lower than the regular rate.

Each field in the sub-column named "Check-in Time" will record the actual check-in time of the user. For example, if a user is 30 minutes late for a booth reservation at "10:00," a check-in time of "10:30" will be recorded in the corresponding field. A "-" indicates that the user has not yet checked in, or that the user did not rent a booth despite having made a reservation.

Each field in the sub-column labeled "Expected End Time of Use" will register the expected end time of the rental (use) of the booth, assuming the user's actual check-in time (check-in time) is considered the start time of the booth rental.

Each field in the sub-column labeled "Confirmation Notification Time" registers the transmission time of the confirmation notification sent to the user's terminal device 20 when the user leaves the store without checking out. If the user checks out upon leaving the store, no confirmation notification is sent to the user's terminal device 20. In this case, "-" is registered in the field of that column.

Each field in the sub-column labeled "Location Information" registers the location information transmitted from the user's terminal device 20 when the user leaves the store without checking out. If the user checks out upon leaving the store, "-" is registered in the corresponding field.

Although not shown in Figure 2, the user management database includes a column where information is registered when a user visits a store and checks in without a reservation. This column is, for example, named "No Reservation." This column has sub-columns named "Store ID," "Closing Time," "Booth Number," "Service Type," "Check-in Time," "Expected End Time," "Forced Check-out Time," "Confirmation Notification Time," and "Location Information," as well as a sub-column named "Usage Period" instead of "Reservation Period." Each field in this sub-column registers the check-in time, the booth number and service type selected by the user at check-in, and the usage period.

The user management database has columns with item names such as "Usage Information 1" and "Usage Information 2." After a user actually uses a booth, specifically after check-out, information registered in the sub-columns of the "Reservation Information" and "No-Reservation Use" columns is slid into each field of these columns. In other words, user reservation and usage information is managed in the "Reservation Information" and "No-Reservation Use" columns until check-out, and then managed in the "Usage Information 1" and "Usage Information 2" columns after use is complete. The user management database may also have columns with item names such as "Usage Information 3" and "Usage Information 4." In the following explanation, if the item names "Usage Information 1," "Usage Information 2," etc., are not distinguished, they will simply be referred to as "Usage Information."

The column labeled "Usage Information" has multiple sub-columns. These sub-columns are labeled with items such as "Store ID," "Booth Number," "Date of Use," "Service Type," "Check-in Time," "Check-out Time," "Price," and "Confirmation Notification Time."

Each field in the sub-column named "Store ID" will contain the store ID assigned to the store where the user checked in. Each field in the sub-column named "Booth Number" will contain the booth number assigned to the booth rented by the user. Each field in the sub-column named "Date of Use" will contain the date the user checked in. Each field in the sub-column named "Service Type" will contain the type of service selected by the user during check-in.

Each field in the subcolumn named "Check-in Time" registers the time the user checked in. Each field in the subcolumn named "Check-out Time" registers the time the user checked out, or the time the server program 37 forcibly checked out the user if they left without checking out. Each field in the subcolumn named "Fee" registers the fee for using the booth. Each field in the subcolumn named "Confirmation Notification Time" registers the time the confirmation notification mentioned above was sent.

Furthermore, the user management database may have columns with column names other than those mentioned above.

Next, the store management database (see Figure 1) stored in memory 32 will be explained. The store management database is a database that manages information about stores operated by the service provider and information about reservations made for those stores.

As shown in Figure 3, the store management database has multiple columns and multiple records (rows). Each column has a name. One column is named "Store ID". Each field in the column named "Store ID" contains the Store ID. Each record is individually identified by its Store ID. That is, each record corresponds to one store.

Other columns in the store management database include fields such as "Store Name," "Address," "Number of Booths," "Photo," "Closing Time," "Price/15 Minutes," "Store Reservation Information 1," and "Store Reservation Information 2." The user management database may also have columns with fields such as "Store Reservation Information 3" and "Store Reservation Information 4." In the following explanation, if the fields "Store Reservation Information 1," "Store Reservation Information 2," etc., are not distinguished, they will simply be referred to as "Store Reservation Information."

Each field in the sub-column labeled "Store Name" contains the store name, such as "Itabashi Store," "Tsurumi Store," or "Chikusa Store." Each field in the sub-column labeled "Address" contains the store's location (address).

Each field in the sub-column named "Number of Booths" contains the number of booths provided in the store. In this case, the store management database record has multiple sub-records. The number of sub-records generated corresponds to the number of booths the store has.

Each field in the sub-column labeled "Photo" contains either a photo file showing a picture of the store or a file path indicating the location of that photo file. In the example shown, the photo file is a PDF file.

In the sub-column named "Closing Time," if the store has a closing time, that time is registered; if the store is open 24 hours, "-" is registered.

The column labeled "Price/15 minutes" has two sub-columns. One sub-column is labeled "Booth Number," and the other is labeled "Price." Each field in the "Booth Number" column contains the aforementioned booth number, while each field in the "Price" column contains the amount. In other words, the price per unit time (15 minutes) is registered in the store management database for each booth. For example, a small booth for two people might be charged 150 yen per 15 minutes, a medium-sized booth for three to four people 200 yen per 15 minutes, and a large booth for five to eight people 300 yen per 15 minutes, all registered in the store management database. Note that the booth price may be uniform regardless of the size of the space.

The column named "Store Reservation Information" has multiple sub-columns. Each sub-column has a name such as "User ID," "Reservation Date," "Start Time," "End Time," "Reservation Period," and "Service Type."

Each field in the sub-column labeled "User ID" contains the User ID of the user who made the reservation. Each field in the sub-column labeled "Reservation Date" contains the date (reservation date) on which the user plans to rent the booth. Each field in the sub-column labeled "Start Time" contains the planned start time of the period the user is renting the booth. Each field in the sub-column labeled "End Time" contains the planned end time of the period the user is renting the booth. Each field in the sub-column labeled "Reservation Period" contains the period the user is renting the booth. Each field in the sub-column labeled "Service Type" contains the type of service the user has selected.

Furthermore, the store management database may have additional columns with column names other than those mentioned above.

Next, the reservation process executed by the terminal program 28 and the server program 37 when a user makes a booth reservation using the terminal device 20 will be explained with reference to Figure 4. Note that the process executed by the terminal program 28 is also the process executed by the controller (or computer) CPU 21, and the process executed by the server program 37 is also the process executed by the controller (or computer) CPU 31. Also, in the flowcharts shown in Figures 4, 6, 8, 10, and 11, "database" is abbreviated as "DB".

The user launches the terminal program 28 on the terminal device 20. The launched terminal program 28 displays the home screen (not shown) on the display 24 (S11). The terminal program 28 pre-loads screen data for the home screen and various other display screens described below. Alternatively, when the terminal program 28 is downloaded to the terminal device 20, the above screen data is stored in the memory 22.

The user enters information on the displayed home screen to display the spot screen. Based on receiving this input (S12), the terminal program 28 sends an HTTP request containing the user ID and a store information request to the management server 30 via the internet 11 (S13). The store information request and the various requests described below are, for example, commands.

When the server program 37 of the management server 30 receives an HTTP request containing a user ID and a request for store information (S13), it reads store information such as the store ID, store name, address, number of booths, and photo files registered in the store management database based on the request for store information (S14). The server program 37 also identifies a record in the user management database (see Figure 2) that has the same user ID as the received user ID. The server program 37 determines whether payment information is registered for the identified record and generates payment information confirmation information indicating whether payment information is registered (S15). This payment information confirmation information indicates whether automatic payment (so-called automatic withdrawal) is possible. The server program 37 sends an HTTP response containing the store information and the payment information confirmation information back to the terminal device 20 as a response to the HTTP request received in step S13 (S16).

The terminal program 28 of the terminal device 20 receives the HTTP response sent back by the management server 30 (S16). The terminal program 28 displays the spot screen containing the store information included in the received HTTP response on the display 24 (S17).

Figure 5(A) shows the spot screen. The spot screen displays the store name, address, and a photo of the store. The spot screen also includes a "Booth Reservation" icon 41. The user refers to the displayed store address and other information, decides which store to reserve, and then selects (taps) the "Booth Reservation" icon 41.

As shown in Figure 4, the terminal program 28 accepts the user's selection of the "Booth Reservation" icon 41 (S18). Based on the payment information confirmation information included in the HTTP response received in step S16, the terminal program 28 determines whether automatic payment is possible (S19). If the terminal program 28 determines that automatic payment is not possible (S19: No), it displays a registration recommendation screen on the display 24 (S20). The registration recommendation screen prompts the user to register payment information. In other words, booth reservations require automatic payment.

Figure 5(B) shows the registration recommendation screen. The registration recommendation screen includes the text "Credit card registration is required to reserve a booth" and a "Register" icon 42. If the user wishes to reserve a booth, they select the "Register" icon 42. If the user decides against reserving a booth, they select the "Back" icon (not shown). The "Back" icon is, for example, the default icon displayed on the display 24 of the terminal device 20.

As shown in Figure 4, the terminal program 28 receives user input (S21) and determines whether the received input is a selection of the "Register" icon 42 (S22). If the terminal program 28 determines that the received input is a selection of the "Back" icon and not the "Register" icon 42 (S22: No), it displays the spot screen again on the display 24 (S17).

When the terminal program 28 determines that the received input is a selection of the "Register" icon 42 (S22: Yes), it executes the registration process (S23). Specifically, the terminal program 28 displays an input screen (not shown) on the display 24 and accepts input of the credit card number and authentication information. The terminal program 28 sends an HTTP request containing the received card number and authentication information to the management server 30 via the internet 11. The server program 37 of the management server 30 performs predetermined processing, such as sending the card number and authentication information to a server operated by a financial institution such as a bank, and then registers the card number and authentication information in the user management database. Furthermore, the server program 37 sends an HTTP response containing a registration completion notification to the terminal device 20 as a response to the HTTP request containing the card number and authentication information.

The terminal program 28 of the terminal device 20 displays the store selection screen on the display 24 (S24) based on the receipt of the registration completion notification, or based on the determination in step S19 that automatic payment is possible (S19: Yes).

As shown in Figure 5(C), the store selection screen has multiple store selection icons 43, each with a store name, and a "Search" icon 44. The user selects one store selection icon 43 from the multiple store selection icons 43, and then selects the "Search" icon 44.

As shown in Figure 4, the terminal program 28 of the terminal device 20, based on receiving user input to select the store selection icon 43 and the "search" icon 44 (S25), sends an HTTP request to the management server 30 via the internet 11, including the store ID of the store selected by the user and a request for a reply with reservation information (S26).

Based on the receipt of the store ID and reply request (S26), the server program 37 of the management server 30 identifies a record with the same store ID as the received store ID in the store management database, and reads the store information and store reservation information registered in the identified record (S27). The server program 37 sends the HTTP response containing the read store information and store reservation information back to the terminal device 20 as a response to the HTTP request received in step S26 (S28).

The terminal program 28 of the terminal device 20 displays a booth selection screen (not shown) on the display 24 based on the reception of an HTTP response containing store information and store reservation information. The booth selection screen displays the types and booth numbers of booths available at the store selected by the user. The booth type refers to the size of the booth (area, usable capacity, etc.). The user specifies (selects) the booth type or booth number on the booth selection screen. Note that the acceptance of the booth type and selection may occur at the same time as the store selection in step S24.

The terminal program 28 of the terminal device 20 displays a date and time specification screen on the display 24 based on the acceptance of the booth selection (S29).

As shown in Figure 5(D), the date and time selection screen has a calendar 46 consisting of multiple "date" icons 45 and a "confirm" icon 47. The user selects the "date" icon 45 for the date to be reserved.

The terminal program 28, upon receiving the user's selection of the "Date" icon 45, displays a reservation period input screen (not shown) on the display 24. The reservation period input screen includes, for example, a pull-down menu for selecting the planned start time of booth use, a pull-down menu for selecting the planned end time of booth use, and a pull-down menu for selecting the service type. On the reservation period input screen, the user selects the planned start and end times of booth use and the service type. After making these selections, the user then selects the "Confirm" icon 47 on the date and time specification screen. If the booth is already reserved for the date and time or period specified by the user, an error message or similar indication will be displayed to show that it is already reserved. The terminal program 28 determines whether the booth is reserved or not based on the store reservation information described above.

As shown in Figure 4, the terminal program 28, based on receiving the selection of the "Date" icon 45, the specification of the reservation date, the selection of the scheduled start and end times of use, the selection of the service type, and the selection of the "Confirm" icon 47 (S30), generates a reservation application containing the user ID, store ID, booth number, reservation date, scheduled start time, scheduled end time of use, and service type (S31). The terminal program 28 sends an HTTP request containing the generated reservation application to the management server 30 via the internet 11 (S32). Note that the selection of the service type, booth type, and booth number may be made at check-in rather than at the time of reservation.

Based on the receipt of the reservation request (S32), the server program 37 of the management server 30 identifies a record in the user management database that has the same user ID as the user ID included in the reservation request. The server program 37 then registers the reservation information included in the reservation request in each field of the identified record, specifically in the column labeled "Reservation Information" (S33). This information includes the store ID, booth number, reservation date, planned start time (start time), planned end time (end time), reservation period, and service type.

Furthermore, the server program 37 identifies a record in the store management database that has the same store ID and booth number as the store ID and booth number included in the reservation application. The server program 37 registers reservation information, such as the user ID, reservation date, planned start time (start time), planned end time (end time), reservation period, and service type, in each field of the identified record, specifically in the column named "Store Reservation Information" (S34). If the identified record has a closing time registered, the server program 37 reads the closing time and registers it in the user management database in the record identified in step S33. Based on the registration of reservation information in the user management database and the store management database, i.e., the acceptance of the reservation application, the server program 37 sends an HTTP response including a reservation completion notification to the terminal device 20 as a response to the HTTP request received in step S32 (S35), and terminates the reservation process (end).

Based on receiving the reservation completion notification (S35), the terminal program 28 of the terminal device 20 displays a reservation completion notification screen (not shown) on the display 24 (S36), and terminates the reservation process (end).

Next, the check-in process (see Figure 6) executed by the terminal program 28 and the server program 37 when a user who has made a reservation or a user who has not made a reservation checks in at the store will be explained.

The user operates the terminal device 20 to launch the terminal program 28. The launched terminal program 28 displays the home screen (not shown) on the display 24. On the displayed home screen, the user selects an icon to display the check-in screen (Figure 7(A)).

As shown in Figure 6, the terminal program 28, based on receiving the selection of the above icon on the home screen (S41), displays the check-in screen on the display 24 (S42).

As shown in Figure 7(A), the check-in screen has a "Check-in" icon 51. When a user wants to check in, they select the "Check-in" icon 51.

As shown in Figure 6, based on the selection of the "Check In" icon 51 (S43), the terminal program 28 displays the reading screen (see Figure 7(B)) on the display 24 and activates the camera 29 (S44).

As shown in Figure 7(B), the reading screen has an image display area 52 that displays the image captured by the camera 29. The user points the camera 29 at the QR code (registered trademark) installed in the store and inputs an instruction to capture the QR code.

The QR code contains the store ID assigned to the store where it is installed. The QR code shown is an example of a code image. The code image may also be a barcode or other format.

As shown in Figure 6, the terminal program 28 acquires the image data output by the camera 29 (S46) based on receiving the user's imaging instruction input (S45). The terminal program 28 then acquires the store ID indicated by the acquired image data (QR code) (S47). Note that the process of acquiring the store ID from the image data (QR code) may be executed by another application program implemented on the terminal device 20. The store ID is an example of store identification information. The process in step S47 is an example of the first acquisition process.

The terminal program 28 sends an HTTP request containing the acquired store ID, the user ID stored in memory 22, and a reservation confirmation request to the management server 30 via the internet 11 (S48).

The server program 37 of the management server 30 receives an HTTP request containing the store ID, user ID, and reservation confirmation request (S48). The server program 37 identifies a record in the user management database that has the same user ID as the received user ID. The server program 37 determines whether the identified record contains reservation information with the same date as the current date and the same store ID as the received store ID (S49). In other words, the server program 37 determines whether the user has made a reservation at the store they visited (S49).

If the server program 37 determines that no reservation has been made (S49: No), it sends an HTTP response containing a no-reservation notification to the terminal device 20 as a response to the HTTP request received in step S48 (S50).

When the server program 37 determines that a reservation exists (S49: Yes), it reads the reservation information registered in the identified record (S51), and sends an HTTP response containing the read reservation information back to the terminal device 20 as a response to the HTTP request received in step S48 (S52).

The terminal program 28 of the terminal device 20 receives an HTTP response containing a no-reservation notification (S50) or an HTTP response containing reservation information (S52). The terminal program 28 determines whether the received HTTP response contains a no-reservation notification or reservation information (S53).

When the terminal program 28 determines that the received HTTP response contains an unscheduled notification (S53: Unscheduled Notification), it displays an input screen (not shown) on the display 24 (S54). The input screen accepts input for specifying the booth type, booth number, service type, etc. The user enters the booth type, booth number, service type, etc., on the input screen.

Furthermore, the display of the input screen may require that payment information be registered in the user management database and that automatic payment is possible. For example, the HTTP response returned by the management server 30 in step S50 includes the aforementioned payment information confirmation information. If the terminal program 28 of the terminal device 20 determines in step S53 that it is a no-reservation notification (S53: no-reservation notification), it displays a registration recommendation screen (see Figure 5(B)) on the display 24, prompting the user to register their credit card number and authentication information. After the payment information is registered in the user management database, the terminal program 28 displays the input screen on the display 24. In other words, the use of a booth in a store may require that automatic payment is possible.

The terminal program 28 accepts input such as the booth type, booth number, and service type on the input screen (S55).

When the terminal program 28 determines that the received HTTP response contains reservation information (S53: reservation information), it displays the plan selection screen on the display 24 (S56).

As shown in Figure 7(C), the plan selection screen has multiple "service selection" icons 53 for accepting the selection of service type (plan), a "number of people" icon 54 for specifying the number of people, and a "next" icon 55.

On the plan selection screen, the user selects the service type (plan type) and specifies the number of users, then selects the "Next" icon 55.

Furthermore, the terminal program 28 may display a screen on the display 24 that allows the user to change the type of booth, booth number, scheduled start time, and scheduled end time of use selected at the time of reservation, and may accept such changes.

As shown in Figure 6, the terminal program 28 displays a final confirmation screen on the display 24 (S58) based on the acceptance of the selection of service type (plan type), the specification of the number of people, and the selection of the "Next" icon 55 on the plan selection screen (S57), or based on the acceptance of the input in step S55. The processing in steps S55 and S57 is an example of the first acceptance processing. The booth number, service type (plan type), and number of people entered or selected in steps S55 and S57, as well as the reservation date, scheduled start time, and scheduled end time entered or selected in the reservation processing, are examples of check-in information.

As shown in Figure 7(D), the final confirmation screen includes a first warning display 56 consisting of text indicating the service type (plan) such as "30-hour pack," text indicating the number of people such as "1 person," and text saying "Please scan the QR code when you leave the store." It also includes a second warning display 57 consisting of text saying "If you leave the store without scanning the QR code, you will be charged for up to 24 hours of service," an "No" icon 58, and a "Yes" icon 59.

After reviewing warnings 56 and 57, the user selects the "Yes" icon 59 if they wish to use the booth.

As shown in Figure 6, based on the user's selection of the "Yes" icon 59 (S59), the terminal program 28 generates a usage application including the user ID, store ID, booth number, scheduled start time (check-in time), scheduled end time, and service type (S60). The terminal program 28 sends an HTTP request containing the generated usage application to the management server 30 via the internet 11 (S61). The processing in step S61, where the terminal program 28 sends the usage application to the management server 30, is an example of the first transmission process.

The server program 37 of the management server 30 receives an HTTP request including a usage application (S61). The processing in step S61, where the server program 37 receives the usage application, is an example of the first reception process.

The server program 37 identifies a record in the user management database that has the same user ID as the user ID included in the received application. The server program 37 also identifies reservation information in the identified record that has the same date as the current date and the same store ID as the received store ID. The server program 37 registers the scheduled start time (check-in time) and scheduled end time included in the received application in the fields of the columns labeled "Check-in Time" and "Scheduled End Time" in the identified reservation information (S62). The server program 37 may also register the time the application was submitted or received in the field of the column labeled "Check-in Time". For example, if a user wants to start using the service earlier than the scheduled start time specified at the time of reservation, they make an input indicating this in the terminal device 20. Based on this input, the server program 37 registers the time the application was submitted or received as the check-in time in the user management database. In this case, the server program 37 changes the scheduled end time according to the difference between the determined check-in time and the scheduled start time, and registers it in the user management database. The process in step S62, which registers the check-in time in the user management database, is an example of the check-in time determination process and the scheduled end time determination process.

Next, the server program 37 sends an HTTP response containing a check-in completion notification to the terminal device 20 as a response to the HTTP request received in step S61 (S63), and terminates the check-in process (end).

The terminal program 28 of the terminal device 20 receives an HTTP response including a check-in completion notification (S63). Based on the receipt of the check-in completion notification, the terminal program 28 displays a completion notification screen on the display 24 indicating that check-in is complete, and terminates the check-in process (end).

Figure 7(E) shows the completion notification screen. The completion notification screen displays the text "Check-in complete," text indicating the service type (plan) such as "30-hour pack," text indicating the number of people such as "1 person," and a "Back" icon 60. After confirming the displayed text, the user selects the "Back" icon 60.

Although not shown in the flowchart, the terminal program 28 displays other screens, such as the home screen mentioned above, on the display 24 based on the selection of the "back" icon 60.

Next, the checkout process (see Figure 8) executed by the terminal program 28 and the server program 37 when a user finishes using a booth and checks out upon leaving the store will be explained.

The user operates the terminal device 20 to launch the terminal program 28. The launched terminal program 28 displays the home screen (not shown) on the display 24. On the displayed home screen, the user selects the icon that instructs the user to display the checkout screen (Figure 9(A)).

As shown in Figure 8, the terminal program 28, based on receiving the selection of the above icon on the home screen (S71), displays the checkout screen on the display 24 (S72).

As shown in Figure 9(A), the checkout screen includes text indicating the store name, the words "Checking In," a time display showing the booth usage time (e.g., "02:50:34"), and a "Checkout" icon 61. When a user wants to check out, they select the "Checkout" icon 61.

As shown in Figure 8, the terminal program 28, based on receiving the selection of the "Checkout" icon 61 (S73), displays the reading screen (see Figure 9(B)) on the display 24 and activates the camera 29 (S74). The processing in step S73 is an example of the second reception process. The user's selection of the "Checkout" icon 61 is an example of inputting a checkout instruction.

As shown in Figure 9(B), the reading screen has an image display area 62 that displays the image captured by the camera 29. The user points the camera 29 at the QR code installed in the store and inputs an instruction to capture the QR code.

As shown in Figure 8, the terminal program 28 acquires the image data output by the camera 29 (S76) based on receiving the user's imaging instruction input (S75). The terminal program 28 then acquires the store ID indicated by the acquired image data (QR code) (S77). Note that the process of acquiring the store ID from the image data may be executed by another application program implemented in the terminal device 20.

The terminal program 28 sends an HTTP request containing the acquired store ID, the user ID stored in memory 22, and a termination notification to the management server 30 via the internet 11 (S78). The processing in step S78 is an example of the second transmission process.

The server program 37 of the management server 30 receives an HTTP request containing the store ID, user ID, and termination notification (S78). The server program 37 identifies a record in the user management database (see Figure 2) that has a user ID matching the user ID included in the received HTTP request. It also identifies a column (reservation information) in the user management database that has a store ID matching the store ID included in the received HTTP request (S79). The server program 37 reads the termination time (scheduled end time) registered in the identified reservation information and determines whether the current time output by the clock module 34 exceeds the read termination time (S80). That is, the server program 37 determines whether the user used the booth beyond the scheduled period, or in other words, whether the usage period was extended (so-called time extension) (S80).

If the server program 37 determines that the usage period has not been extended (S80: No), it determines the current time or the scheduled end time of use as the checkout time (S81), and registers the determined checkout time in the sub-column field labeled "Checkout Time" in the usage information identified in step S79 (S82). The process in step S81 is an example of the checkout time determination process.

The server program 37 calculates the fee based on the check-in time, check-out time, store ID, booth number, and service type registered in the user management database, and the hourly rate registered in the store management database (S83). The server program 37 may also calculate information regarding the service type along with the fee. For example, the server program 37 may calculate the remaining available time for a "30-hour pack."

The server program 37 registers the calculated fee in the sub-column field labeled "Fee" in the usage information identified in step S79 (S84). The server program 37 also re-registers the store ID, booth number, reservation date, start time, end time, reservation period, service type, and check-in time, which were registered in each field of the identified reservation information sub-column, into a column labeled "Usage Information" (S85).

If the server program 37 determines that the checkout period has been extended (S80: Yes), it determines the current time or the time the HTTP request was received in step S78 as the checkout time (S86), and then executes the processes described in steps S82 to S85. The process in step S86 is an example of the checkout time determination process.

The server program 37 sends an HTTP response containing a payment notification to the terminal device 20 as a response to the HTTP request received in step S78 (S87). The payment notification includes the fee calculated in step S83, the check-out time determined in step S81 or step S86, the check-in time and number of users registered in the user management database, and the usage period calculated from the check-in and check-out times.

Subsequently, the server program 37 performs settlement processing, such as sending settlement information to the server operated by the financial institution (S88), and then terminates the checkout process (end).

The terminal program 28 of the terminal device 20 receives an HTTP response containing a payment notification with a charge (S87). Based on the receipt of the payment notification, the terminal program 28 displays a checkout completion notification screen on the display 24 (S89).

Figure 9(C) shows the checkout completion notification screen. The checkout completion notification screen displays text and numbers indicating the date and time of arrival (reservation date and check-in time), the date and time of departure (reservation date and check-out time), the period of use (usage period), the number of users, the type of service used, and the fee. Furthermore, if the user extends their time using the booth beyond the scheduled end time, the checkout completion notification screen will display text and numbers indicating the extension fee. After confirming the fees and other details on the checkout completion notification screen, the user selects the "Back" icon (not shown).

The terminal program 28 terminates the checkout process (end) based on the selection of the "Back" icon (not shown) on the checkout completion notification screen, or on the input of a command to stop the terminal program 28.

Next, the monitoring process (Figures 10 and 11) executed by the server program 37 of the management server 30 will be explained. The management process monitors usage where checkout has not been performed even after the scheduled end time.

The server program 37 performs monitoring processing, for example, every few minutes, every ten minutes or so, or every few tens of minutes. First, the server program 37 searches the management data database (see Figure 2) for a first specific record (reservation information) where check-out has not been performed even after the scheduled end time of use has passed (S91). Specifically, the server program 37 searches the user management database for a first specific record where a check-in time is registered, the current time is past the scheduled end time of use, and no forced check-out time is registered (S91).

The server program 37 determines whether or not the first specific record has been found (S92). If the server program 37 determines that the first specific record has been found (S92: Yes), it reads the closing time registered in the reservation information (see Figure 2) of the first specific record and identifies the store type (S93). That is, the server program 37 determines whether the store the user is using is a store with a closing time (hereinafter referred to as "Type 1 store") or a 24-hour store without a closing time (hereinafter referred to as "Type 2 store"). For example, the server program 37 identifies the store the user is using as a Type 1 store based on the fact that the closing time is registered in the reservation information, and identifies the store the user is using as a Type 2 store based on the fact that the closing time is not registered in the reservation information. The processing in step S92 is an example of the second determination process. The processing in step S93 is an example of the store type identification process.

The server program 37 determines the forced check-out time based on the identified store type and the scheduled end time of use registered in the reservation information of the first identified record (S94). Specifically, if the identified store type is a first-type store, the server program 37 determines the forced check-out time to be the closing time. If the identified store type is a second-type store, the server program 37 determines the forced check-out time to be a time that is one predetermined time after the scheduled end time of use. The first predetermined time is stored in memory 32 beforehand. The first predetermined time is, for example, 24 hours. However, the first predetermined time may be other times such as 6 hours or 12 hours. The processing in step S94 is an example of the forced check-out time determination process.

The server program 37 registers the determined mandatory check-out time in the field of the column labeled "Mandatory Check-out Time" in the reservation information of the first specific record (S95). That is, the mandatory check-out time is determined and registered in the user management database after the scheduled end time has passed. However, the mandatory check-out time may also be determined and registered in the user management database before the scheduled end time has passed, i.e., immediately after check-in.

If the server program 37 determines in step S92 that the first specific record was not found (S92: No), it skips the processing in steps S93 to S95.

If the server program 37 determines that the first specific record was not found (S92: No), or after executing the process in step S95, it searches the user management database to see if there is a second specific record in which the forced checkout time is registered (S96). Then, the server program 37 determines whether the second specific record was found (S97). If the server program 37 determines that the second specific record was found (S97: Yes), it determines whether a second predetermined time has elapsed from the scheduled end time (S98). The second predetermined time is a time pre-stored in memory 32, for example, 3 hours. However, the second predetermined time is not limited to 3 hours; it may be 1 hour, 2 hours, or other times. For example, the server program 37 calculates the elapsed time from the scheduled end time to the current time and determines whether the calculated elapsed time exceeds the second predetermined time (S98).

When the server program 37 determines that a second predetermined time has elapsed from the scheduled end time of use (S98: Yes), it determines whether or not location information is registered in the second specific record (S99).

Referring to Figure 12(A), the registration of location information in the user management database will be explained. If the user settings allow the transmission of location information, the terminal program 28 of the terminal device 20 periodically acquires the location information (GPS location information/GNSS location information) received by the terminal device 20 (S121). The terminal program 28 periodically sends an HTTP request containing the acquired location information and user ID to the management server 30 via the internet 11 (S122). Steps S121 and S122 are an example of the fourth transmission process.

On the other hand, the server program 37 of the management server 30 receives an HTTP request containing the user ID and location information (S122). The server program 37 identifies the record with the same user ID as the received user ID in the user management database (S123), and registers the received location information in the field of the column labeled "Location Information" in the reservation information of the identified record (S124).

As shown in Figure 10, when the server program 37 determines that location information is registered in the second specific record (S99: Yes), it calculates the distance between the user and the store (S100). For example, the server program 37 reads the store's address from the store management database and calculates the distance based on the read address and the location information. The process in step S100 is an example of the process for calculating the distance.

The server program 37 determines whether the calculated separation distance exceeds a threshold distance pre-stored in memory 32 (S101). The threshold distance is, for example, several meters to several tens of meters. That is, in step S101, the server program 37 determines whether the user has left the store. The processing in step S101 is an example of the first decision process.

If the server program 37 determines that the user settings on the terminal device 20 do not permit the transmission of location information and that the location information is not registered in the user management database (S99: No), it skips the processing in steps S100 and S101.

The server program 37, upon determining that location information is not registered in the user management database (S99: No), or that the distance between devices exceeds a threshold distance (S101: Yes), sends a first confirmation notice to the terminal device 20 (S102). For example, the server program 37 sends an HTTP response, including the first confirmation notice, back to the terminal device 20 as a response to the HTTP requests periodically sent by the terminal program 28 of the terminal device 20. The processing in step S102 is an example of the third transmission process.

As shown in Figure 12(B), the terminal program 28 of the terminal device 20 receives the first confirmation notification sent by the management server 30 (S131). Based on the receipt of the first confirmation notification, the terminal program 28 displays the first confirmation screen on the display 24 (S132). The processing in step S131 is an example of the second reception processing and reception processing. The processing in step S132 is an example of the display processing.

Figure 13(A) shows the first confirmation screen. The first confirmation screen contains text indicating that checkout has not been completed even after the scheduled end time, the text "Are you currently using the booth?", and icons 71 and 72. If the user is using the booth beyond the scheduled end time, they select the "Yes" icon 71. If the user has forgotten to check out and left the premises, they select the "No" icon 72. The user's selection of the "Yes" icon 71 is an example of inputting an instruction to continue using the booth.

If the user selects the "No" icon 72, the terminal program 28 displays the second confirmation screen shown in Figure 13(B) on the display 24. The second confirmation screen has the text "Please check out" and the "Check out on the spot" icon 73. The user selects the "Check out on the spot" icon 73 if they wish to check out. The user's selection of the "Check out on the spot" icon 73 is an example of a checkout instruction input. The first and second confirmation screens are examples of confirmation screens.

As shown in Figure 12(B), the terminal program 28 of the terminal device 20 accepts the selection of a "Yes" icon 71, a "No" icon 72, or a "Checkout on the Spot" icon 73 (S133). The terminal program 28 sends an HTTP request containing the user ID and instruction information to the management server 30 via the internet 11 (S134). The instruction information indicates either a "Continue Use Instruction" or a "Checkout Instruction." If the instruction information indicates a "Continue Use Instruction," it includes the extension time. For example, the terminal program 28 obtains the extension time entered or selected by the user and includes the obtained extension time in the instruction information. The processing in step S134 is an example of the fifth transmission process and the third transmission process.

The processing from step S135 onward will be explained after the explanation of the monitoring process.

As shown in Figure 10, after sending the first confirmation notice (S102), the server program 37 of the management server 30 registers the transmission time of the first confirmation notice in the field of the column named "First Confirmation Notice Time" in the "Reservation Information" section of the user management database (see Figure 2) (S103).

If the server program 37 determines that it could not find the second specific record in which the forced checkout time is registered in the user management database (S97: No), it skips steps S98 to S103. Furthermore, if the server program 37 determines that the second predetermined time has not elapsed from the scheduled end time of use (S98: No), it skips steps S99 to S103. Also, if the server program 37 determines that the separation distance does not exceed the threshold distance (S101: No), it skips steps S102 and S103. In other words, the first confirmation notification is not sent to the terminal device 20 until the second predetermined time has elapsed from the scheduled end time of use, or if the user is still inside the store. The skipping of step S102 when the separation distance does not exceed the threshold distance (S101: No) is an example of the first stop process.

The server program 37 determines whether it has received the instruction information transmitted by the terminal device 20 in step S134 (Figure 12(B)) (S104). If the server program 37 determines that it has received instruction information corresponding to the first confirmation notification (S104: Yes), it determines whether the received instruction information indicates a checkout instruction or a continued use instruction, as shown in Figure 11 (S105). The process by which the server program 37 receives instruction information (S104: Yes) is an example of the third reception process.

When the server program 37 determines that the received instruction information indicates a checkout instruction (S105: Yes), it determines the current time or the time the instruction information was received as the checkout time and registers the determined checkout time in the user management database (S106). Then, after executing steps S82 to S85 of the checkout process (see Figure 8), the server program 37 sends a first settlement notification to the terminal device 20 (S87). Specifically, the server program 37 sends an HTTP response containing the first settlement notification back to the terminal device 20 as a response to the HTTP requests that the terminal device 20 periodically sends to the management server 30. Then, the server program 37 executes the settlement process in step S88. The process in step S106 is an example of the checkout time determination process.

In step S105, if the server program 37 determines that the received instruction information is a continuation instruction rather than a checkout instruction (S105: No), it obtains the extension time associated with the instruction information and uses the obtained extension time to perform an extension process (S107) to update (change) the scheduled end time of use registered in the identified second specific record. Then, the server program 37 removes the record that underwent the settlement process in step S87 or the extension process in step S107 from the second specific record. That is, the record that underwent settlement or extension processing is excluded from the "second specific record that received the instruction information" in step S104 (see Figure 10).

After executing steps S105 to S108, the server program 37 repeats the process shown in Figure 10, step S104. That is, the server program 37 repeatedly executes steps S105 to S108 until all second specific records corresponding to the terminal device 20 that transmitted the instruction information are excluded from processing.

The server program 37 executes steps S105 to S108 for all second-specific records corresponding to the terminal device 20 that sent the instruction information. If it determines that there is no second-specific record corresponding to the terminal device 20 that sent the instruction information (S104: No), it searches the user management database (see Figure 2) for a third-specific record for which the first confirmation notice has been sent (S109). Specifically, the server program 37 searches the user management database for records in the field of the column with the item name "First Confirmation Notice Time" where a time is registered (S109). Then, the server program 37 determines whether or not a third-specific record was found (S110).

When the server program 37 determines that a third specific record has been found (S110: Yes), it determines whether the elapsed time from the time registered in the field of the column named "First Confirmation Notification Time" to the current time exceeds a third predetermined time pre-stored in memory 32. That is, the server program 37 determines whether the third predetermined time has elapsed since sending the first confirmation notification to the terminal device 20 without receiving a checkout instruction or a continued use instruction (S111). In other words, the server program 37 confirms whether the user responded to the first confirmation notification. The third predetermined time is, for example, three hours, the same as the second predetermined time. However, the third predetermined time does not have to be the same as the second predetermined time, and it may be a time other than three hours, such as one hour or two hours.

When the server program 37 determines that a third predetermined time has elapsed since sending the first confirmation notice (S111: Yes), it sends a second confirmation notice to the terminal device 20 (S112). For example, the server program 37 sends an HTTP response including the second confirmation notice back to the terminal device 20 as a response to an HTTP request containing location information, etc., that the terminal program 28 of the terminal device 20 periodically sends. The processing in step S112 is an example of re-executing the third transmission process.

Upon receiving the second confirmation notice, the terminal program 28 of the terminal device 20 executes the processing steps S131 to S136 (see Figure 12(B)) in the same manner as when the first confirmation notice was received.

After sending the second confirmation notice (S112), the server program 37 registers the transmission time of the second confirmation notice in the field of the column labeled "Second Confirmation Notice Time" in the "Reservation Information" section of the user management database (see Figure 2) (S113).

If the server program 37 determines in step S110 that the third specific record is not found (S110: No), it skips the processing in steps S111 to S113. Also, if the server program 37 determines in step S111 that the third predetermined time has not elapsed since sending the first confirmation notice (S111: No), it skips the processing in steps S112 and S113.

Although the flowchart shows an example where two confirmation notifications are sent to the terminal device 20, the confirmation notifications may be sent repeatedly to the terminal device 20 at predetermined intervals until the user responds to the confirmation notification, or until the current time reaches the mandatory checkout time.

After executing the process in step S113, the server program 37 searches the user management database for a fourth specific record in the reservation information (see Figure 2) where the forced checkout time is earlier than the current time (S114). In other words, records where checkout or continued use (time extension) was not performed up to the forced checkout time are searched.

The server program 37 determines whether or not the fourth specific record has been found (S115). If the server program 37 determines that the fourth specific record has been found (S115: Yes), it sets the mandatory checkout time registered in the reservation information of the management database as the checkout time, and registers the determined checkout time in the field of the column named "Checkout Time" in the usage information of the user management database (S116). That is, if the user does not check out or continue using the facility (extend the time) by the mandatory checkout time, checkout is performed and the user's use ends. In the example shown in Figure 2, the checkout time registered in the user management database is either the closing time ("23:00") or "20220331 12:00", which is 24 hours after the scheduled end time of use. The process in step S116 is an example of the checkout time determination process.

Based on determining the checkout time and registering it in the user management database, the server program 37 executes steps S83 to S85 of the checkout process (see Figure 8), and then sends a second settlement notification to the terminal device 20. Specifically, as a response to the HTTP request that the terminal program 28 of the terminal device 20 periodically sends to the management server 30, it sends an HTTP response containing the second settlement notification back to the terminal device 20. Subsequently, the server program 37 of the management server 30 executes the settlement process in step S88 and terminates the monitoring process (end).

On the other hand, the terminal program 28 of the terminal device 20 determines whether or not it has received the first settlement notification sent by the management server 30 in step S87 (see Figure 11), as shown in Figure 12(B) (S135). If the terminal program 28 determines that it has received the first settlement notification (S135: Yes), it displays the first settlement confirmation screen (see Figure 13(C)) on the display 24 (S136).

The first payment confirmation screen shown in Figure 13(C) is displayed on the display 24 when the user selects the "Checkout Now" icon 73 on the second confirmation screen (see Figure 13(B)) and payment is completed. The first payment confirmation screen contains text indicating that checkout is complete and the text "Thank you for using our service." The checkout time may also be displayed on the first payment confirmation screen.

Furthermore, as shown in Figure 12(C), the terminal program 28 of the terminal device 20 determines whether or not it has received the second settlement notification sent by the management server 30 in step S87 (see Figure 10) (S141). If the terminal program 28 determines that it has received the second settlement notification (S141: Yes), it displays the second settlement confirmation screen (see Figure 13(D)) on the display 24 (S142). If the terminal program 28 determines that it has not received the second settlement notification (S141: No), it skips the process in step S142. The processes in steps S141 and S142 are an example of the settlement confirmation process.

The second payment confirmation screen shown in Figure 13(D) is displayed on display 24 when the mandatory checkout time is set as the checkout time and checkout is performed. The second payment confirmation screen contains text indicating that checkout was performed at the closing time (closing time) and the text "Thank you for your patronage." If the store used by the user is open 24 hours, the second payment confirmation screen will display the time after the scheduled end time (24 hours) has elapsed (the mandatory checkout time) instead of the closing time.

[Effects of the Embodiment]
The server program 37 of the management server 30 determines the mandatory checkout time as the checkout time and processes the payment if the user leaves the store without checking out and checkout is not completed by the mandatory checkout time. Therefore, even if the user leaves the store without checking out, payment can be processed appropriately.

Furthermore, in this embodiment, if the store where the user checks in is a Type 1 store with a closing time, the closing time is determined as the mandatory check-out time. If the store where the user checks in is a Type 2 store that operates 24 hours a day, the mandatory check-out time is determined to be a time one predetermined hour after the scheduled end time of use. Therefore, an appropriate mandatory check-out time can be determined according to the type of store.

Furthermore, in this embodiment, if check-out has not been completed even after a second predetermined time has elapsed from the scheduled end time, the server program 37 sends a first confirmation notification to the terminal device 20, causing the first confirmation screen to be displayed on the terminal device 20's display 24. The display of the first confirmation screen on the terminal device 20's display 24 prompts the user to check out if they forget to do so before leaving the store.

Furthermore, in this embodiment, if the user is inside the store (S101: No), step S102 is skipped and the first confirmation notification is not sent to the terminal device 20. Therefore, it is possible to prevent the first confirmation notification from being sent to a user who is using a booth.

Furthermore, in this embodiment, if the user does not respond to the first confirmation notice (S102), a second confirmation notice (S112) is sent to the terminal device 20 after a third predetermined time has elapsed. Therefore, users who did not notice the first confirmation notice can be prompted to check out again.

Furthermore, in this embodiment, by displaying a second confirmation screen (see Figure 13(B)) on the display 24 of the terminal device 20 and accepting the selection of the "Checkout on the Spot" icon 73, checkout can be accepted even after the user has left the store.

[Variations]
In the above embodiment, an example was described in which, in the case of a 24-hour store, the mandatory check-out time is determined to be 24 hours after the scheduled end time of use, and in the case of a store with a closing time, the closing time is determined to be the mandatory check-out time. In this modified example, an example is described in which the mandatory check-out time is determined to be a time after the maximum time has elapsed from the check-in time, or the closing time is determined to be the mandatory check-out time. In other words, in this modified example, an example is described in which, when a mandatory check-out is performed, the maximum time (usage time) for which the user is deemed to have used the booth is predetermined.

In the following, the configurations and processes described in the embodiments will be omitted from further explanation, using the same reference numerals and step numbers as in the embodiments.

The memory 32 of the management server 30 stores the store management database shown in Figure 14, instead of the store management database shown in Figure 3.

The store management database in this modified example includes, in addition to the columns with item names such as "Store ID" found in the store management database described in the embodiment, a column with the item name "Maximum Time." Each field in the column with the item name "Maximum Time" contains the registered maximum time. For example, a service provider offers a one-day usage package (maximum 9 hours) to a user. When a user uses this service, they can use a booth for a fixed price for up to 9 hours per day. This maximum usage time for the one-day package is registered as the maximum time in the store management database (see Figure 14). However, the maximum time may be set independently of the service provided by the service provider.

The maximum operating hours are associated with the store ID in the store management database. In other words, the maximum operating hours are set for each store. Note that the maximum operating hours may be the same for all stores. Furthermore, the maximum operating hours may differ between 24-hour stores (without a closing time) and stores with a closing time.

The server program 37 of the management server 30 executes the monitoring process shown in Figure 15 instead of the monitoring processes shown in Figures 10 and 11. After executing steps S91 and S92, the server program 37 reads the closing time and maximum time limit from the store management database (S151). More specifically, the server program 37 reads the store ID, which indicates the store used by the user, from the first identified record in step S91. The server program 37 then reads the closing time and maximum time limit associated with the read store ID from the store management database. Note that if the store is open 24 hours, information indicating that there is no closing time is read from the store management database.

The server program 37 calculates the forced check-out time by adding the upper limit time read in step S151 to the check-in time registered in the first specified record identified in step S91 (S152).

Next, the server program 37 determines whether a closing time is registered in the first specific record identified in step S91 (S153). That is, the server program 37 determines whether the store the user is using is a 24-hour store or a store with a closing time.

If the server program 37 determines that the store the user is using is either a 24-hour store or a store with a closing time (S153: Yes), it then determines whether the forced checkout time calculated in step S152 is later than the closing time read in step S151 (S154). The process in step S154 is an example of the third decision process.

If the server program 37 determines that the forced checkout time is later than the closing time (S154: Yes), it resets the closing time to the forced checkout time (S155). For example, the forced checkout time is reset by overwriting the forced checkout time calculated in step S152 with the closing time (S155). The process in step S155 is an example of the forced checkout time reset process.

In step S153, the server program 37 determines that the store the user is using is a 24-hour store (S153: No), or after re-determining the closing time as the forced check-out time (S155), it registers the forced check-out time determined in step S152, or the forced check-out time re-determined in step S155, in the user management database (S95).

The server program 37, after executing the processes from steps S96 to S113 as in the embodiment, searches for the record (fourth specific record) where the current time has reached the mandatory checkout time (S114), and registers the checkout time in the user management database (S115). Next, the server program 37 calculates the usage time and usage fee, performs the settlement process (S83-S88), and terminates the monitoring process (end). Note that the usage fee determined in step S83 may be a "flat rate" which is the usage fee for a one-day usage package (maximum 9 hours) if the closing time is not the mandatory checkout time. Alternatively, the usage fee may be calculated from the usage time and the amount per unit time, as in the embodiment.

[Effects and Effects of Modifications]
In this modified example, a maximum usage time (maximum time) is predetermined for cases where forced checkout occurs. Therefore, the user will not be charged for usage time exceeding the maximum time.

Furthermore, in this modified version, stores with a closing time will not have a mandatory checkout time set after the closing time.

[Other variations]
In the above embodiment, an example was described in which, when the type of store is a 24-hour store that does not have a closing time, the mandatory check-out time is determined to be 24 hours after the scheduled end time of use. However, the server program 37 may determine the mandatory check-out time to be a predetermined time such as 24:00 (0:00) when the type of store is a 24-hour store that does not have a closing time.

In the above-described embodiment, an example was explained in which the checkout time is determined by the time the server program 37 of the management server 30 receives the termination notification (S78) or instruction information (S104), or by the current time. However, the checkout time may also be determined by the time the terminal program 28 of the terminal device 20 sends the termination notification or instruction information.

In the above-described embodiment, an example was explained in which the service provision system 10 includes one management server 30. However, the management server 30 may be composed of multiple servers. For example, the management server 30 may consist of a server that communicates with the terminal device 20 and a server that manages the management database.

In the above-described embodiment, an example was explained in which the server program 37 performs user matching and store (booth) usage management. However, the server program 37 may also perform only store usage management.

In the above embodiment, an example was described in which the management server 30 acquires location information transmitted by the terminal device 20. However, the management server 30 does not need to acquire location information. In that case, the processes from steps S99 to S101 in the monitoring process shown in Figure 10 are omitted. Also, the location information registration process shown in Figure 12(A) is omitted.

In the above embodiment, in step S94 (see Figure 10), an example was described in which, for a 24-hour store (Type 2 store), the mandatory check-out time is determined to be a time that is 24 hours after the scheduled end time of use. However, the mandatory check-out time may also be determined to be 24 hours after the check-in time.

In the above embodiment, an example was described in which a usage fee is set for each booth (see Figure 3). However, a usage fee may also be set for each room (coworking space). For example, multiple booths and a shared space may be installed within the coworking space. The user checks in and enters the coworking space, selects a booth to use from the multiple booths installed in the coworking space, or uses a shared space. The server program 37 calculates the usage fee for the coworking space, not the usage fee for a booth (S83), and notifies the user (S87). Note that a coworking space may have only a shared space and no booths, or vice versa. Furthermore, each store may have only one coworking space or multiple coworking spaces.

10...Service provision system 20...Terminal device 21...CPU
22...Memory 23...Communication interface 24...Display 25...Input interface 28...Terminal program 29...Camera 30...Management server 31...CPU
32...Memory 33...Communication interface 37...Server program

Claims (14)

A management server comprising a first communication interface, a first memory, and a first controller,
The terminal device comprises a second communication interface, a second memory, an input interface, a camera, a display, and a second controller.
The second controller described above is:
The first acquisition process involves obtaining store identification information indicated by the code image captured by the above camera,
A first reception process that accepts the input of check-in information through the above input interface,
The first transmission process is performed to send the application for use, including the above store identification information, the above check-in information, and the user identification information, to the above management server via the above second communication interface and the Internet.
The second controller described above is:
A second reception process that accepts checkout instructions through the above input interface,
Based on the acceptance of the above checkout instruction input, a second transmission process can be executed, which transmits a completion notice including the above store identification information and user identification information to the management server via the second communication interface and the internet.
The first controller described above is
A first receiving process that receives the above application for use through the first communication interface,
A check-in time determination process that determines the check-in time based on the time the above application for use is sent or received, or the scheduled start time of use indicated in the above check-in information,
The process of determining the estimated end time of use based on the determined check-in time and the above check-in information,
A forced checkout time determination process determines a forced checkout time that is later than the scheduled end time mentioned above,
The checkout time determination process is executed,
The above checkout time determination process is:
Based on the receipt of the above termination notice, the check-out time will be determined to be the time corresponding to the time the termination notice was sent or received, or the above scheduled end time of use.
A service provision system that determines the mandatory checkout time as the checkout time based on the fact that the current time has reached the mandatory checkout time and that the termination notice has not been received. The above forced checkout time determination process is,
A store type identification process that determines whether the store indicated by the above store identification information is a Type 1 store with a closing time or a Type 2 store without such a closing time,
A service provision system according to claim 1, comprising the process of determining the closing time as the forced check-out time based on the identification of the store as the first type of store, and determining the forced check-out time as a time that is a predetermined time stored in the first memory, or a predetermined time stored in the first memory, from the scheduled end time of use. The first controller described above is
If the above checkout time has not been determined, and the elapsed time from the above scheduled end time of use has reached the second predetermined time stored in the first memory, a third transmission process is further executed, which sends a confirmation notice to the terminal device via the first communication interface and the internet.
The second controller described above is:
The second receiving process for receiving the above confirmation notice,
The service provision system according to claim 1, which performs a display process that causes the confirmation screen indicated by the above confirmation notice to be displayed on the above display. The second controller described above is
A fourth transmission process is further executed to acquire location information and transmit it to the management server via the second communication interface and the internet.
The above-mentioned first controller is,
A process to calculate the distance between the location indicated by the received location information and the store location indicated by the store identification information,
A first determination process that determines whether the above separation distance exceeds the threshold distance stored in the first memory,
The service provision system according to claim 3, further comprising: a first stop process that stops the execution of the third transmission process based on the determination that the above separation distance does not exceed the above threshold distance. The second controller described above is:
While the above confirmation screen is displayed, it is possible to receive either an instruction input indicating continued use of the store or an instruction input indicating checkout, and to execute a fifth transmission process that transmits instruction information indicating the said instruction input to the management server via the second communication interface and the internet.
The first controller described above is
The service provision system according to claim 3, wherein the instruction information is not received before the elapsed time since the execution of the third transmission process reaches the third predetermined time stored in the first memory, the third transmission process is executed again. The first controller described above is
A third receiving process is further executed to receive the above instruction information.
The above checkout time determination process is:
The service provision system according to claim 5, which includes a process of determining the time of transmission or reception of the instruction information to be the checkout time, based on the fact that the received instruction information indicates the checkout instruction input. The first controller described above is
A second determination process is then performed to determine whether the current time has exceeded the scheduled end time mentioned above.
The service provision system according to claim 1, which executes the forced check-out time determination process based on the determination that the current time has exceeded the scheduled end time of use. A server program implemented in a management server comprising a first communication interface, a first memory, and a first controller,
A program comprising: a terminal program implemented in a terminal device having a second communication interface, a second memory, an input interface, a camera, a display, and a second controller;
The above terminal program,
The first acquisition process involves obtaining store identification information indicated by the code image captured by the above camera,
A first reception process that accepts the input of check-in information through the above input interface,
The second controller is instructed to perform a first transmission process, which involves sending a usage application including the above-mentioned store identification information, the above-mentioned check-in information, and user identification information to the management server via the above-mentioned second communication interface and the internet.
The above terminal program,
A second reception process that accepts checkout instructions through the above input interface,
Based on the acceptance of the above checkout instruction input, the second controller is instructed to perform a second transmission process, which involves sending a completion notice containing the above store identification information and user identification information to the management server via the second communication interface and the Internet.
The above server program,
A first receiving process that receives the above application for use through the first communication interface,
A check-in time determination process that determines the check-in time based on the time the above application for use is sent or received, or the scheduled start time of use indicated in the above check-in information,
The process of determining the estimated end time of use based on the determined check-in time and the above check-in information,
A forced checkout time determination process determines a forced checkout time that is later than the scheduled end time mentioned above,
The first controller is instructed to perform the checkout time determination process.
The above checkout time determination process is:
Based on the receipt of the above termination notice, the check-out time will be determined to be the time corresponding to the time the termination notice was sent or received, or the above scheduled end time of use.
A program that determines the mandatory checkout time as the checkout time, based on the fact that the current time has reached the mandatory checkout time and that the termination notice has not been received. A server program implemented in a management server comprising a communication interface, server memory, and a controller,
A first receiving process that receives a usage application transmitted by a terminal device, which includes store identification information, check-in information, and user identification information, through the above communication interface,
A check-in time determination process that determines the check-in time based on the time the above application for use is sent or received, or the scheduled start time of use indicated in the above check-in information,
The process of determining the estimated end time of use based on the determined check-in time and the above check-in information,
A forced checkout time determination process determines a forced checkout time that is later than the scheduled end time mentioned above,
The above controller is instructed to perform the checkout time determination process.
The above checkout time determination process is:
Based on the receipt of the termination notice sent by the terminal device, the checkout time is determined to be the time corresponding to the time the termination notice was sent or received, or the scheduled end time of use mentioned above.
A server program that determines the mandatory checkout time as the checkout time based on the fact that the current time has reached the mandatory checkout time and that the termination notice has not been received. A terminal program implemented in a terminal device comprising a communication interface, terminal memory, input interface, camera, display, and controller,
The first acquisition process involves obtaining store identification information indicated by the code image captured by the above camera,
A first reception process that accepts the input of check-in information through the above input interface,
The controller is instructed to perform a first transmission process, which involves sending a usage application including the above-mentioned store identification information, the above-mentioned check-in information, and user identification information to the management server via the above-mentioned communication interface and the Internet.
A second reception process that accepts checkout instructions through the above input interface,
Based on the acceptance of the above checkout instruction input, a second transmission process is performed to send a completion notice including the above store identification information and user identification information to the above management server via the above communication interface and the internet,
A terminal program that receives a payment notification from the management server, indicating that payment was made using the forced checkout time, and causes the controller to execute a payment confirmation process that displays a payment confirmation screen showing the payment notification on the display. A terminal program implemented in a terminal device comprising a communication interface, terminal memory, input interface, camera, display, and controller,
The first acquisition process involves obtaining store identification information indicated by the code image captured by the above camera,
A first reception process that accepts the input of check-in information through the above input interface,
The controller is instructed to perform a first transmission process, which involves sending a usage application including the above-mentioned store identification information, the above-mentioned check-in information, and user identification information to the management server via the above-mentioned communication interface and the Internet.
A second reception process that accepts checkout instructions through the above input interface,
Based on the acceptance of the above checkout instruction input, a second transmission process is performed to send a completion notice including the above store identification information and user identification information to the above management server via the above communication interface and the internet.
The receiving process includes receiving a confirmation notice sent by the management server mentioned above, which is a confirmation notice requesting checkout, via the Internet and the communication interface mentioned above.
A display process that displays the instruction reception screen showing the received confirmation notice on the above display,
A terminal program that causes the controller to perform a third transmission process, which involves sending the checkout instructions received on the instruction reception screen to the management server via the communication interface and the internet. The first memory mentioned above also stores the upper limit time.
The above forced checkout time determination process is,
The service provision system according to claim 1, wherein the process determines the mandatory check-out time to be the time obtained by adding the above-mentioned check-in time to the above-mentioned upper limit time. The service provision system according to claim 12, wherein the above-mentioned upper limit time is stored in the first memory in association with the above-mentioned store identification information. The above-mentioned first memory further stores the above-mentioned store identification information and closing time in association with each other.
The first controller described above is
A third determination process determines whether the forced check-out time determined in the above forced check-out time determination process is later than the above closing time,
The service provision system according to claim 12, further comprising: a forced check-out time re-determination process that, based on the determination in the third determination process that the forced check-out time is later than the closing time, re-determines the closing time to the forced check-out time.