Service delivery system, program, terminal program, and server program

Abstract

To provide a service providing system configured to allow a guest to enter a rental space alone, and manage entry, or the like, of the guest.SOLUTION: A management server 30 issues a guest passcode in accordance with an application from an application member. A guest visits a store at which the application member, who is an inviter, is present, and images a second QR code (R) disposed in the store using a terminal device 60 carried by the guest (S104). The second QR code has a URL of a website disclosed by the management server 30. The guest accesses the displayed URL (S108), and inputs (S112) the guest passcode on a displayed guest entry screen (S111). The input guest passcode is transmitted to the management server 30 (S114). The management server 30 transmits, when determining that the received guest passcode is valid (S115: Yes), an instruction to a store terminal 40 to unlock a door to a booth (S121).SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present invention relates to a service providing system that provides a service of lending out spaces provided in stores to users.

Background Art

[0002] An application program (so-called matching app) for matching users is known (see, for example, Patent Document 1). The matching app is installed on the terminal devices possessed by app members and communicates with a management server. The management server performs matching between app members based on the occupation, hobbies, residential area, age, gender, etc. of the app members collected from the matching app.

[0003] Some matching apps provide a service of lending out spaces for app members to actually meet (see, for example, Patent Document 2). Users visit the store that lends out the space and perform check-in and check-out using the matching app. That is, the matching app for matching app members is also used for lending out spaces.

[0004] In addition, some systems for lending out spaces have a door lock device provided at the entrance and exit to the space (see, for example, Patent Document 3). In this system, an unlocking request is sent from an application program installed on the terminal device possessed by the user to the management server. When the management server receives the unlocking request, it sends an unlocking instruction to a control device that performs drive control of the door lock device.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Patent Document 3

[0006] The inventor of the present invention considered adopting a method for unlocking the door lock based on whether the app member has checked in or checked out, in a service provision system that provides space rental services to app members.

[0007] App members may want to rent a space to meet with non-app members for interviews, business meetings, etc. If a door lock device is installed at the entrance to the rental space, non-app members who do not have the matching app installed on their device will not be able to enter the rental space unless accompanied by an app member. Furthermore, the inventor of this application considered it necessary to manage which app member invited which guest entering the rental space.

[0008] This invention has been made in view of the above circumstances, and its purpose is to provide a service provision system that enables non-app members to enter rental spaces on their own and that can manage the entry of non-app members. [Means for solving the problem]

[0009] (1) The service provision system according to the present invention comprises a management server having a first communication interface connected to the Internet, a first memory, and a first controller; a terminal device having a second communication interface connected to the Internet, a second memory, a display, and a second controller, and implementing a terminal program; a door lock device installed at the entrance and exit of the rental space of the store; and a store terminal having the door lock device, a third communication interface connected to the Internet, and a third controller. The second controller performs a check-in application transmission process which acquires store identification information and transmits a check-in application including the acquired store identification information and user identification information to the management server via the second communication interface; and a check-out application transmission process which acquires the store identification information and transmits a check-out application including the acquired store identification information and user identification information to the management server via the second communication interface.The first controller performs the following: a check-in request reception process to receive the check-in request through the first communication interface; a first registration process to store the user identification information and check-in information in the first memory based on the receipt of the check-in request; a first unlock instruction transmission process to send an unlock instruction to the store terminal through the first communication interface based on the receipt of the check-in request; a check-out request reception process to receive the check-out request through the first communication interface; a second registration process to store the user identification information and check-out information in the first memory based on the receipt of the check-out request; a second unlock instruction transmission process to send an unlock instruction to the store terminal through the first communication interface based on the receipt of the check-out request; and, based on the determination that the store identification information and user identification information are registered in the first memory, generates a guest passcode and the generated guest passcode and The following processes are executed: a third registration process that stores the above-mentioned user identification information and the above-mentioned store identification information in association with the first memory; a guest passcode issuance process that transmits notification information including the guest passcode to the terminal device via the first communication interface; a guest check-in application reception process that receives a guest check-in application including the store identification information and the guest passcode; a first matching process that determines whether the combination of the store identification information and the guest passcode included in the received guest check-in application is stored in the first memory; a guest check-in information registration process that stores the guest check-in information in association with the above-mentioned user identification information based on the determination in the first matching process that the combination is stored in the first memory; and a third unlock instruction transmission process that transmits an unlock instruction to the store terminal via the first communication interface based on the determination in the first matching process that the combination of the store identification information and the guest passcode is stored in the first memory.The third controller performs the following: receiving the unlock instruction through the third communication interface; and transmitting an unlock command through the third communication interface to the door lock device based on the receipt of the unlock instruction.

[0010] The management server issues a guest passcode to a user (app member) who owns a terminal device on which the terminal program (app) is installed, provided that the store identification information and user identification information are stored in the first memory in association with each other. The app member notifies the guest, who is not an app member, of the issued guest passcode using email or other means. The guest visits the store where the inviting app member is waiting and accesses a designated website by, for example, scanning a guest QR code (registered trademark) posted in the store with the camera of the guest terminal device that the guest possesses. Alternatively, the guest accesses the website indicated by the URL notified along with the guest passcode. On the accessed website, the guest enters the notified guest passcode. The management server obtains the entered guest passcode and the store identification information read by the guest terminal device from the guest QR code (registered trademark), or the store identification information entered along with the guest passcode, and verifies whether the combination of the obtained guest passcode and store identification information is stored in the first memory. When the management server determines that the combination is stored in the first memory, it sends a third unlock instruction to the store terminal to unlock the door and stores guest check-in information, indicating that the door has been unlocked and the guest has entered the rental space, as well as the time of entry, in the first memory, associated with user identification information indicating the inviter. In other words, a guest who is not an app member can enter the rental space where the inviter (an app member) is waiting, even if the terminal program is not installed on their guest terminal device and without having to contact the inviter to have the door unlocked. Furthermore, guest check-in information, such as information indicating that the guest has entered the rental space and the time of entry, is managed in association with the app member who invited the guest.

[0011] (2) The second controller may further perform an issuance request transmission process to send a guest passcode issuance request including the user identification information to the management server via the second communication interface. The first controller performs the guest passcode issuance process based on having received the guest passcode issuance request via the first communication interface.

[0012] The management server issues a guest passcode when an app member requests one.

[0013] (3) The first controller may execute the third unlock instruction transmission process based on the fact that it has received the check-in request and has not received the check-out request.

[0014] The management server only allows guests invited by the inviter to enter the rental space while the inviter (an app member) is renting the space. Therefore, it prevents guests from entering the rental space when the inviter is not present.

[0015] (4) The first controller may determine the user usage fee and the guest usage fee based on the check-in information, the check-out information, and the guest check-in information, and perform a payment process for the user indicated by the user identification information associated with the guest check-in information stored in the first memory.

[0016] The fee charged to the inviter for using the rental space (user usage fee) and the fee charged to the guest invited by the inviter for using the rental space (guest usage fee) will be charged to the inviter.

[0017] (5) The first controller may further perform a charge notification process to transmit the user charges and guest charges to the terminal device through the first communication interface. The second controller, based on having received the user charges and guest charges through the second communication interface, further performs a charge display process to display the received user charges and guest charges on the display.

[0018] The host will be notified of the fees charged for using the rental space (user usage fee) and the fees charged for using the rental space by the guest (guest usage fee).

[0019] (6) The second controller may further perform a reservation request process to send a reservation request including the store identification information and the user identification information stored in the second memory to the management server via the second communication interface. The first controller further performs a reservation request reception process to receive the reservation request via the first communication interface, and a reservation registration process to store the store identification information and the user identification information included in the received reservation request in association with the first memory. Based on the fact that the store identification information and the user identification information are stored in association with the first memory in the reservation registration process or the first registration process, the first controller performs the third registration process and the guest passcode issuance process.

[0020] The guest passcode is generated and notified to the app member after they make a reservation or check in.

[0021] (7) The first controller may, based on the receipt of the checkout request, further perform a deletion process to remove the guest passcode from the first memory.

[0022] When the app member who is the host checks out, the guest passcode is deleted. Therefore, it is possible to prevent a guest who was previously invited from accidentally entering the lending space when the app member borrows the lending space next time.

[0023] (8) The service system according to the present invention may further include a first code image and a second code image installed in the store. The first code image is an image including the store identification information. The second code image is an image including a predetermined URL and the store identification information. The terminal device further has a camera. In the check-in application transmission process and the check-out application transmission process, the second controller acquires the store identification information from the first code image captured by the camera. The first controller further executes a guest entry screen data return process for returning guest entry screen data for accepting input of the guest passcode based on receiving a screen data request including the store identification information, which is a request transmitted to the predetermined URL.

[0024] The guest uses the camera of the terminal device in their possession to capture the second code image installed in the store, accesses the predetermined URL obtained from the second code image, enters the guest passcode on the displayed guest entry screen, and enters the lending space. Therefore, it is possible to suppress the door from being unlocked even though the guest has not visited the store. As a result, the security of the lending space is further enhanced.

[0025] (9) The service providing system according to the present invention may further include a third code image installed in the store. The first code images are installed both inside and outside the lending space. The second code image is installed outside the lending space and is an image further including information indicating entry. The third code image is installed inside the lending space and is an image including a predetermined URL, store identification information, and information indicating checkout. Based on receiving a screen data request that is a request sent to the predetermined URL and includes the store identification information and the information indicating checkout, the first controller performs a guest checkout screen data reply process of replying with guest checkout screen data for accepting input of the guest passcode, a guest checkout application receiving process of receiving a guest checkout application including the guest passcode and the store identification information through the first communication interface, a second verification process of determining whether a combination of the store identification information and the guest passcode included in the received guest checkout application is stored in the first memory, a fourth lock release instruction transmission process of transmitting the lock release instruction to the store terminal through the first communication interface based on determining that it is stored in the first memory in the second verification process, and a first guest checkout information registration process of storing first guest checkout information indicating that the guest has exited the lending space or the time of exit in association with the user identification information in the first memory based on determining that it is stored in the first memory in the second verification process.

[0026] According to the above configuration, a guest can exit the lending space before the host. Also, it is suppressed that the door is unlocked even though the guest is not in the lending space. Further, first guest checkout information indicating that the guest has exited the lending space or the time of exit is managed in association with the user identification information indicating the host.

[0027] (10) The first controller may further perform a determination process to determine whether the first guest checkout information is stored in the first memory based on the receipt of the checkout request, and a second guest checkout information registration process to store second guest checkout information indicating that the user has left the store with the guest in the first memory in association with the user identification information, based on the determination process to determine that the first guest checkout information is not stored in the first memory.

[0028] If the host checks out, the door lock is released, and the guest leaves the premises with the host, the guest's check-out is considered to have been done together with the host. Therefore, the guest is saved the trouble of having to enter a guest passcode or other information into their terminal device.

[0029] (11) Based on the determination in the first matching process that the combination is stored in the first memory, the first controller may further execute a guest entry information transmission process to send guest entry information indicating the guest's entry to the terminal device via the first communication interface. Based on the receipt of the guest entry information via the second communication interface, the second controller further executes a guest entry information display process to display a guest entry notification screen on the display.

[0030] The inviter is notified when a guest enters the room.

[0031] (12) Based on the determination in the second matching process that the above combination is stored in the first memory, the first controller may further execute a guest departure information transmission process to transmit guest departure information indicating the guest's departure to the terminal device via the first communication interface. Based on the receipt of the guest departure information via the second communication interface, the second controller further executes a guest departure information display process to display a guest departure notification screen on the display.

[0032] The host is notified when a guest leaves.

[0033] (13) The program according to the present invention comprises a server program implemented in a management server having a first communication interface connected to the Internet, a first memory, and a first controller; a terminal program implemented in a terminal device having a second communication interface connected to the Internet, a second memory, a display, and a second controller; and a store program implemented in a store terminal having a door lock device installed at the entrance and exit of the store's rental space, a third communication interface connected to the Internet, and a third controller. The terminal program causes the second controller to execute a check-in request transmission process that acquires store identification information and transmits a check-in request including the acquired store identification information and the user identification information to the management server via the second communication interface; and a check-out request transmission process that acquires store identification information and transmits a check-out request including the acquired store identification information and the user identification information to the management server via the second communication interface.The server program performs the following actions: a check-in request reception process to receive the check-in request through the first communication interface; a first registration process to store the user identification information and check-in information in the first memory based on the receipt of the check-in request; a first unlock instruction transmission process to send an unlock instruction to the store terminal through the first communication interface based on the receipt of the check-in request; a check-out request reception process to receive the check-out request through the first communication interface; a second registration process to store the user identification information and check-out information in the first memory based on the receipt of the check-out request; a second unlock instruction transmission process to send an unlock instruction to the store terminal through the first communication interface based on the receipt of the check-out request; and, based on the determination that the store identification information and user identification information are registered in the first memory, generates a guest passcode and the generated guest passcode and the user identification information. The first controller is instructed to execute: a third registration process that stores the separate information and the store identification information in association with the first memory; a guest passcode issuance process that transmits notification information including the guest passcode to the terminal device via the first communication interface; a guest check-in application reception process that receives a guest check-in application including the store identification information and the guest passcode; a first matching process that determines whether the combination of the store identification information and the guest passcode included in the received guest check-in application is stored in the first memory; a guest check-in information registration process that stores the guest check-in information in association with the user identification information based on the determination in the first matching process that the combination is stored in the first memory; and a third unlock instruction transmission process that transmits an unlock instruction to the store terminal via the first communication interface based on the determination in the first matching process that the combination of the store identification information and the guest passcode is stored in the first memory.The store program causes the third controller to perform the following: a lock release instruction receiving process, which receives the lock release instruction through the third communication interface; and a lock release instruction transmission process, which, based on the receipt of the lock release instruction, transmits a lock release command to the door lock device through the third communication interface.

[0034] The present invention can also be considered as a program comprising a server program implemented on a management server, a terminal program implemented on a terminal device, and a store program implemented on a store terminal.

[0035] (14) The server program according to the present invention is implemented on a management server having a communication interface connected to the Internet, server memory, and a controller.The server program includes: a check-in request reception process that receives a check-in request through the communication interface; a first registration process that stores user identification information and check-in information in the server memory based on the receipt of the check-in request; a first unlock instruction transmission process that sends an unlock instruction to the store terminal through the communication interface based on the receipt of the check-in request; a check-out request reception process that receives a check-out request through the communication interface; a second registration process that stores user identification information and check-out information in the server memory based on the receipt of the check-out request; a second unlock instruction transmission process that sends an unlock instruction to the store terminal through the communication interface based on the receipt of the check-out request; and, based on the determination that the store identification information and user identification information are registered in the server memory, a guest passcode is generated, and the generated guest passcode is associated with the user identification information and the store The controller is instructed to execute the following: a third registration process that stores the store identification information in association with the user identification information in the server memory; a guest passcode issuance process that sends notification information including the guest passcode to the terminal device held by the user via the communication interface; a guest check-in request reception process that receives a guest check-in request including the store identification information and the guest passcode; a verification process that determines whether the combination of the store identification information and the guest passcode included in the received guest check-in request is stored in the server memory; a guest check-in information registration process that stores the guest check-in information in association with the user identification information in the server memory based on the verification process's determination that the combination is stored in the server memory; and a third unlock instruction transmission process that sends an unlock instruction to the store terminal via the communication interface based on the verification process's determination that the combination of the store identification information and the guest passcode is stored in the server memory.

[0036] This invention can also be viewed as a server program implemented on a management server.

[0037] (15) The terminal program according to the present invention is implemented in a terminal device having a communication interface connected to the Internet, terminal memory, a display, and a controller. The terminal program causes the controller to execute a check-in request transmission process which acquires store identification information and sends a check-in request including the acquired store identification information and user identification information to the management server via the communication interface; a check-out request transmission process which acquires the store identification information and sends a check-out request including the acquired store identification information and user identification information to the management server via the communication interface; and a fee display process which, based on the receipt of user usage fees and guest usage fees via the communication interface, displays the received user usage fees and guest usage fees on the display.

[0038] This invention can also be considered as a terminal program implemented in a terminal device. [Effects of the Invention]

[0039] This invention makes it possible for non-app members (guests) to enter rental spaces independently, and also allows for the management of entry by non-app members. [Brief explanation of the drawing]

[0040] [Figure 1] Figure 1 is a diagram showing the configuration of the service provision system 10, and is also a functional block diagram of terminal device 20, terminal device 60, management server 30, and store terminal 40. [Figure 2] Figure 2 shows the user management database. [Figure 3] Figure 3 is a diagram showing the store management database. [Figure 4] Figure 4 is a flowchart of the reservation process. [Figure 5]Figure 5 shows the spot screen, registration recommendation screen, store selection screen, and date and time specification screen. [Figure 6] Figure 6 is a flowchart of the check-in process. [Figure 7] Figure 7 shows the check-in screen, scanning screen, plan selection screen, final confirmation screen, and completion notification screen. [Figure 8] Figure 8 is a flowchart of the guest passcode issuance process. [Figure 9] Figure 9 shows the guest invitation screen, error notification screen, store selection screen, and guest passcode notification screen. [Figure 10] Figure 10 is a flowchart of the guest check-in process. [Figure 11] Figure 11 shows the guest entry screen, the unlock notification screen, and the guest entry notification screen. [Figure 12] Figure 12 is a flowchart of the guest checkout process. [Figure 13] Figure 13 shows the guest exit screen, the lock release notification screen, and the guest exit notification screen. [Figure 14] Figure 14 shows a portion of the checkout process flowchart. [Figure 15] Figure 15 shows another part of the checkout process flowchart. [Figure 16] Figure 16 shows the checkout screen, the scanning screen, and the checkout completion notification screen. [Modes for carrying out the invention]

[0041] Embodiments of the present invention will be described below. It goes without saying that the embodiments described below are merely examples of the present invention, and the embodiments of the present invention can be modified as appropriate without changing the gist of the invention. For example, some of the processes shown in Figures 4, 6, 8, 10, 12, 14, and 15 may be omitted, the order of the processes may be changed, or they may be changed to other processes, without changing the gist of the invention. Also, the icons and characters displayed on the screens shown in Figures 5, 7, 9, 11, 13, and 16 may be omitted, their display positions may be changed, or they may be changed to other text boxes, icons, or characters, without changing the gist of the invention.

[0042] 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 app members with a service that matches them with other app members, and a service that rents out booths (rental spaces) as places for app members to meet. An app member is defined as a person who has registered for the service provided by the service provider and installed the terminal program 28 on their terminal device 20. The terminal device 20 is a communication terminal that the app member can carry, such as a smartphone (registered trademark), tablet (registered trademark), or laptop computer.

[0043] Furthermore, service providers also rent out booths as a place for app members to meet non-app members. Non-app members are defined as individuals who are not registered for the services provided by the service provider and whose terminal devices 60 do not have the terminal program 28 installed. App members invite non-app members to the booths for purposes such as interviews or business negotiations. App members who invite non-app members to the booths are also referred to as inviters. Non-app members invited by inviters are also referred to as guests.

[0044] The service provider operates multiple stores, each having multiple booths. In each store, the doors leading to the booths are equipped with a door locking device 50 for locking and unlocking. In each store, there may be one door for multiple booths, or one door for each booth. In other words, each store may have one door locking device 50, or multiple door locking devices 50. The following explanation will focus on the case where each store has one door locking device 50.

[0045] The door lock device 50 is operated remotely by the management server 30. The management server 30 unlocks the door based on whether an app member has checked in or checked out at the store. The management server 30 also unlocks the door in response to a guest's request.

[0046] The configuration and execution processes of the service provision system 10 will be explained in detail below.

[0047] The service provision system 10 comprises a management server 30 operated by the service provider, terminal devices 20 owned by each app member, a store terminal 40, and a door lock device 50. Although not included in the service provision system 10, terminal devices 60 owned by non-app members are also shown in Figure 1.

[0048] Furthermore, the service provision system 10 includes a first QR code (registered trademark), a second QR code (registered trademark), and a third QR code (registered trademark) that are affixed to the doors of stores, etc.

[0049] The first QR code (registered trademark) is used for app members' check-in and check-out, and is affixed to the interior and exterior surfaces of doors, or nearby. The first QR code (registered trademark) is a code that can read a store ID that identifies each store. The first QR code (registered trademark) is an example of the first code image. The store ID is an example of store identification information.

[0050] The second QR code (registered trademark) is for guest entry and is affixed to the outside surface of the door or nearby. The second QR code (registered trademark) is a code that can read the first URL. The first URL includes the server address, which is the communication address of the management server 30, and the first path. The first path is, for example, the address where the guest entry input screen data is stored. The second QR code (registered trademark) also includes the store ID or information indicating the store ID. In other words, a different second QR code (registered trademark) is used for each store. The information indicating the store ID is, for example, the first path itself. In other words, a different first path is used for each store. The second QR code (registered trademark) is an example of the second code image. The first URL is an example of a predetermined URL. The first path is an example of store identification information and information indicating entry.

[0051] The third QR code (registered trademark) is for guest exit and is affixed to the interior side of the door or nearby. The third QR code (registered trademark) is a code that can read the second URL. The second URL includes the server address, which is the communication address of the management server 30, and the second path. The second path is, for example, the address where the guest exit input screen data is stored. The third QR code (registered trademark) also includes the store ID or information indicating the store ID. In other words, a different third QR code (registered trademark) is used for each store. The information indicating the store ID is, for example, the second path itself. In other words, a different second path is used for each store. The third QR code (registered trademark) is an example of a third code image. The second URL is an example of a predetermined URL. The second path is an example of store identification information and information indicating exit.

[0052] The terminal device 20 includes a CPU 21, memory 22, communication interface 23, display 24, input interface 25, and camera 29.

[0053] The CPU 21 is a central processing unit that executes the OS 26, browser 27, terminal program 28, and mailer 61 stored in memory 22. The CPU 21 is an example of a second controller and a controller.

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

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

[0056] Camera 29 has a lens and multiple image sensors. Camera 29 outputs image data generated by imaging. Camera 29 is a so-called digital camera. Camera 29 is used to capture QR codes (registered trademark).

[0057] Memory 22 includes ROM and RAM. Memory 22 is an example of second memory and terminal memory.

[0058] Memory 22 stores the operating system OS 26, the browser 27, and the mailer 61. The mailer 61 is an application program for sending emails to a mail server (not shown) and receiving emails that have arrived at the mail server.

[0059] Furthermore, memory 22 has a memory area capable of storing terminal program 28. Terminal program 28 is a program provided by a service provider to app members. Terminal program 28 may be a so-called application program, or a so-called plug-in app that extends the functionality of browser 27. Alternatively, terminal program 28 may be HTML data containing JavaScript.

[0060] App members, for example, launch a browser 27 and access a URL published on the internet 11 by the management server 30, displaying a webpage provided by the service provider on the display 24. On the webpage, the app member 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) on the terminal device 20. The downloaded server address, user ID, and terminal program 28 are stored in memory 22.

[0061] The server address is the global IP address assigned to the management server 30. The URL above includes both the server address and the path to the webpage.

[0062] The User ID is identification information that individually identifies the app member, the terminal device 20, and the terminal program 28. The User ID is an example of user identification information.

[0063] App members launch the downloaded terminal program 28 and display the input screen. On the input screen, app members enter public information such as their location (address), occupation, and hobbies. The entered public information is sent to the management server 30 using the server address. The management server 30 registers the received public information in the user management database (see Figure 2) described later. The management server 30 uses the registered public information to match app members with each other and sends information about the other matched app members back to the terminal device 20. App members make requests to the other matched app members to meet in person via the management server 30. After the other matched app member agrees or accepts, the app member makes a reservation for a booth at a store operated by the service provider using the terminal program 28. Alternatively, the app member makes a reservation for a booth to meet a non-app member using the terminal program 28.

[0064] Furthermore, app members use terminal program 28 to check in at the store, rent a booth, and meet other app members who have been matched with them or non-app members they have invited. App members also use terminal program 28 to check out at the store and leave the store.

[0065] The door lock device 50 comprises, for example, a housing (not shown), a deadbolt (not shown) slidably supported by the housing, a drive device 52 for sliding the deadbolt, a control unit 51 for controlling the drive of the drive device 52, and a communication interface 53. The drive device 52 is, for example, a solenoid. The control unit 51 is, for example, a microprocessor. The communication interface 53 is connected to a LAN (Local Area Network) 12 attached to the store by wire or wireless. The door lock device 50 is connected to the store terminal 40 via the LAN 12.

[0066] The control unit 51 of the door lock device 50 drives the drive unit 52 in response to a lock command input from the store terminal 40 via the communication interface 53. The drive unit 52 slides the deadbolt to lock the door. The control unit 51 drives the drive unit 52 in response to an unlock command input from the store terminal 40 via the communication interface 53. The drive unit 52 slides the deadbolt to unlock the door. Alternatively, the control unit 51 keeps the door locked at all times, and when an unlock command is input, it maintains the door unlocked for a certain period of time.

[0067] A commercially available electric lock or electronic lock is used as the door lock device 50. However, any door lock device 50 may be used as long as the door can be unlocked by a command entered from the store terminal 40. The following description will focus on the case where a door lock device 50 that keeps the door locked at all times and only unlocks the door for a certain period of time when an unlock command is entered is used.

[0068] The store terminal 40 is a personal computer, notebook computer, or tablet installed in the store. The store terminal 40 includes a CPU 41, memory 42, communication interface 43, display 44, and input interface 45. The configuration of the CPU 41, memory 42, and communication interface 43 is the same as that of the CPU 21, memory 22, and communication interface 23 of the terminal device 20. If the store terminal 40 is a personal computer, the display 44 is a so-called monitor, and the input interface 45 is a mouse, keyboard, or microphone. The CPU 41 is an example of a third controller. The communication interface 43 is an example of a third communication interface.

[0069] The communication interface 43 is connected to a LAN 12 installed in the store. The store terminal 40 can communicate with the door lock device 50 via the LAN 12. A gateway device (not shown), such as a router, which is connected to the internet 11, is connected to the LAN 12. The store terminal 40 can communicate with the management server 30 via the LAN 12, the gateway device, and the internet 11.

[0070] Based on receiving an unlock command from the management server 30 via the LAN 12, gateway device, and internet 11, the store terminal 40 sends an unlock command to the door lock device 50 via the LAN 12. In other words, the management server 30 can unlock the door remotely.

[0071] The terminal device 60 possessed by non-app members is a portable communication terminal such as a smartphone (registered trademark), tablet (registered trademark), or laptop computer, similar to the terminal device 20 possessed by app members. The terminal device 60 is equipped with a CPU 21, memory 22, communication interface 23, display 24, input interface 25, and camera 29, similar to the terminal device 20.

[0072] The memory 22 of the terminal device 60 stores the OS 26, browser 27, mailer 61, and QR code reading application 62. The QR code reading application 62 is an application program that activates the camera 29 and obtains information such as the URL from the image data of the QR code (registered trademark) captured by the camera 29.

[0073] The management server 30 includes 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.

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

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

[0076] 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 a function to obtain the current time via the internet 11.

[0077] 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 first memory and server memory may be memory owned by other servers, such as storage servers, that are accessible to the management server 30.

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

[0079] As shown in Figure 2, the user management database is a database that manages information about app members (upper section), reservation information about booth reservations made by app members (middle section), and usage information about the actual use of a booth after it has been used (lower section).

[0080] The user management database has multiple columns and multiple records (rows). Each column is assigned a field name. One column is named "User ID". Each field in the column named "User ID" contains a User ID. Each record is individually identified by its User ID. In other words, each record corresponds to one application member.

[0081] 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.

[0082] 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."

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

[0084] Each field in the column labeled "Occupation" and "Hobby 1" contains the occupation and hobby of the app member, respectively. The server program 37 registers the occupation and hobby included in the matching information sent by the terminal program 28 into each field of the respective column. Although Figure 2 only shows the column labeled "Hobby 1," the user management database may have multiple columns labeled "Hobby 2," "Hobby 3," and so on.

[0085] The fields in the columns labeled "Matching User ID" and "Group ID" each contain the user IDs (matching user IDs) of other app members that have been matched with the app member, and the group IDs assigned to the groups to which the app member belongs. When the server program 37 matches app members, it registers the user IDs of the other matched app members as matching user IDs in the corresponding fields of the columns. Additionally, if an app member joins an existing group, the server program 37 registers the group ID assigned to the group the app member has joined in the corresponding fields of the columns. Alternatively, if an app member creates a new group, the server program 37 generates a unique group ID that is not yet registered in the user management database and registers the generated group ID in the corresponding fields of the columns.

[0086] Furthermore, matching between app members, joining groups, and creating new groups can be done in any way.

[0087] Each field in the column labeled "Payment Information" will contain the information necessary for app members to automatically pay for booth rentals (payment information). For example, payment information includes credit card numbers and authentication information for identity verification. The card number and authentication information will be registered as payment information in each field of the column labeled "Payment Information." However, payment information may also include bank IDs, account numbers, and authentication information.

[0088] If an app member 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.

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

[0090] The column named "Reservation Information" has multiple subcolumns. These subcolumns are named "Store ID," "Reservation Date," "Start Time," "End Time," "Reservation Period," "Service Type," "Check-in Time," "Expected End Time," "Guest Passcode," "Guest Check-in Time," "Guest Check-out Time," "Guest Usage Time," and "Guest Usage Fee." If multiple guest passcodes are issued, the subcolumn named "Guest Passcode" will be generated for each guest passcode issued. In the example shown in Figure 2, two subcolumns named "Guest Passcode" are registered in the user management database.

[0091] Each field in the sub-column labeled "Store ID" contains the Store ID, which is the identification information assigned to the store that the app member reserved.

[0092] Each field in the sub-column labeled "Reservation Date" contains the date on which the app member plans to rent a booth. Each field in the sub-column labeled "Start Time" contains the planned start time for the period during which the app member will use the booth. Each field in the sub-column labeled "End Time" contains the planned end time for the period during which the app member will rent the booth. Each field in the sub-column labeled "Reservation Period" contains the period during which the app member will rent the booth. "1h" indicates 1 hour, and "3h" indicates 3 hours.

[0093] 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.

[0094] Each field in the sub-column named "Check-in Time" will register the actual check-in time of the app member. For example, if an app member is 30 minutes late for a booth reservation at "10:00", a check-in time of "10:30" will be registered in the field of that column. Note that "-" indicates that the app member has not yet checked in, or that the app member did not rent a booth despite having made a reservation.

[0095] 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 that the time the app member actually checked in (check-in time) is the start time of the booth rental.

[0096] Each field in the sub-column labeled "Guest Passcode" registers the guest passcode issued by the server program 37 to the app member. As shown in Figure 3, only one guest passcode may be issued for a single reservation, or multiple guest passcodes may be issued for a single reservation. Furthermore, one guest passcode may be issued for one guest, or one guest passcode may be issued for multiple guests.

[0097] Each field in the subcolumn named "Guest Check-in Time" records the time the guest entered the booth. Each field in the subcolumn named "Guest Check-out Time" records the time the guest left the booth. Each field in the subcolumn named "Guest Usage Time" records the duration the guest stayed in the booth. Each field in the subcolumn named "Guest Usage Fee" records the usage fee (guest usage fee) for the booth used by the guest. Note that the guest check-in time, guest check-out time, and guest usage fee are registered for each guest. For example, if two guests are invited, the guest check-in time, guest check-out time, and guest usage fee for one guest, and the guest check-in time, guest check-out time, and guest usage fee for the other guest will be registered in the usage information of the user management database.

[0098] Although not shown in Figure 2, the user management database also includes a column where information is registered when an app member visits a store and checks in without making a reservation. This column may be named, for example, "No-Reservation Usage Information". This column has sub-columns with the aforementioned item names such as "Store ID", "Service Type", "Check-in Time", "Expected End Time", "Guest Passcode", "Guest Check-in Time", "Guest Check-out Time", "Guest Usage Time", and "Guest Usage Fee".

[0099] The information registered in each field of each sub-column under the item name "Reservation Information" will be deleted from the user management database or moved to another database after the use of the reserved booth has ended (after check-out) or after the scheduled end time has passed. Similarly, the information registered in each field of each sub-column under the item name "Non-Reservation Usage Information" will be deleted from the user management database or moved to another database after the use of the booth has ended (after check-out).

[0100] The user management database has columns with item names such as "Usage Information 1" and "Usage Information 2". After an app member actually uses a booth, specifically after check-out, the information registered in the item names "Reservation Information" and "No-Reservation Usage Information" is moved and registered in each field of these columns. In other words, information regarding app members' reservations and usage is managed in the column with the item names "Reservation Information" and "No-Reservation Usage Information" until check-out, and after use is completed, it is managed in the column with the item name "Usage Information 1" or "Usage Information 2". 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" and "Usage Information 2", etc. are not distinguished, they will simply be referred to as "Usage Information".

[0101] Columns labeled "Usage Information" have multiple sub-columns. These sub-columns are labeled with items such as "Store ID," "Date of Use," "Service Type," "Check-in Time," "Check-out Time," "Usage Duration," "User Usage Fee," "Number of Guests," "Guest Check-in Time," "Guest Check-out Time," "Guest Usage Duration," and "Guest Usage Fee."

[0102] Each field in the sub-column labeled "Store ID" will contain the store ID assigned to the store where the app member checked in. Each field in the sub-column labeled "Date of Use" will contain the date on which the app member checked in. Each field in the sub-column labeled "Service Type" will contain the type of service selected by the app member when they checked in.

[0103] Each field in the subcolumn named "Check-in Time" will register the time the app member checked in. Each field in the subcolumn named "Check-out Time" will register the time the app member checked out. Each field in the subcolumn named "Usage Time" will register the duration the app member used the booth, i.e., the time from check-in time to check-out time. Each field in the subcolumn named "User Usage Fee" will register the usage fee for the booth used by the app member.

[0104] Each field in the sub-column labeled "Number of Guests" will register the number of guests invited by the app member. Each field in the sub-column labeled "Guest Check-in Time" will register the time the guest entered the booth. Each field in the sub-column labeled "Guest Check-out Time" will register the time the guest left the booth. Each field in the sub-column labeled "Guest Usage Time" will register the duration the guest used the booth. Each field in the sub-column labeled "Guest Usage Fee" will register the usage fee for the booth used by the guest.

[0105] The user management database may also have columns with item names other than those mentioned above.

[0106] Next, the store management database 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.

[0107] As shown in Figure 3, the store management database has multiple columns and multiple records (rows). Each column is assigned a field 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. In other words, one record corresponds to one store.

[0108] Other columns in the store management database include item names such as "Store Name," "Address," "Photo," "Price / 15 minutes," "Store Reservation Information 1," and "Store Reservation Information 2." The user management database may also have columns with item names such as "Store Reservation Information 3" and "Store Reservation Information 4." In the following explanation, if we do not distinguish between item names such as "Store Reservation Information 1" and "Store Reservation Information 2," we will simply refer to them as "Store Reservation Information."

[0109] Each field in the subcolumn labeled "Store Name" contains the store name, such as "Itabashi Store," "Tsurumi Store," or "Chikusa Store." Each field in the subcolumn labeled "Address" contains the store's location (address).

[0110] 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 where that photo file is stored. In the example shown, the photo file is a PDF file.

[0111] Each field in the column labeled "Charge / 15 minutes" contains the usage fee per unit of time (15 minutes).

[0112] The column named "Store Reservation Information" has multiple sub-columns. Each sub-column is named after an item such as "User ID," "Reservation Date," "Start Time," "End Time," "Reservation Period," and "Service Type."

[0113] Each field in the subcolumn labeled "User ID" contains the User ID of the app member who made the reservation. Each field in the subcolumn labeled "Reservation Date" contains the date (reservation date) on which the app member plans to rent the booth. Each field in the subcolumn labeled "Start Time" contains the planned start time for the period the app member will rent the booth. Each field in the subcolumn labeled "End Time" contains the planned end time for the period the app member will rent the booth. Each field in the subcolumn labeled "Reservation Period" contains the period for which the app member will rent the booth. Each field in the subcolumn labeled "Service Type" contains the type of service selected by the app member.

[0114] Furthermore, the store management database may have columns with item names other than those mentioned above.

[0115] Next, the reservation process executed by the terminal program 28 and the server program 37 when an app member 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 CPU 21, which is the controller (or computer). Similarly, the process executed by the server program 37 is also the process executed by the CPU 31, which is the controller (or computer). Also, in the flowcharts shown in Figures 4, 6, 8, 10, 12, 14, and 15, "database" is abbreviated as "DB".

[0116] The app member starts the terminal program 28 on the terminal device 20. The started terminal program 28 displays a home screen (not shown) on the display 24 (S11). The terminal program 28 has pre-existing format data for the home screen and other display screens. Alternatively, when the terminal program 28 is downloaded to the terminal device 20, the above format data is stored in the memory 22.

[0117] App members make inputs on the displayed home screen to display the spot screen (see Figure 5(A)). Based on the acceptance of this input (S12), the terminal program 28 sends an HTTP request including the user ID and a store information request to the management server 30 via the internet 11 (S13). Store information requests and the various requests and applications described below are, for example, commands.

[0118] When the server program 37 of the management server 30 receives an HTTP request including a user ID and a request for store information (S13), it reads store information, such as the store ID, store name, address, 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 in the identified record and generates payment information confirmation information indicating whether payment information is registered (S15). The payment information confirmation information indicates whether automatic payment (so-called automatic withdrawal) can be performed. The server program 37 sends an HTTP response including 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).

[0119] 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).

[0120] 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 has a "Booth Reservation" icon 71. After the app member decides which store to reserve by referring to the displayed address, etc., they select (tap) the "Booth Reservation" icon 71.

[0121] As shown in Figure 4, the terminal program 28 accepts the selection of the "booth reservation" icon 71 by the app member (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 can be made (S19). If the terminal program 28 determines that automatic payment cannot be made (S19: No), it displays a registration recommendation screen on the display 24 (S20). The registration recommendation screen prompts the app member to register payment information. In other words, booth reservations require automatic payment.

[0122] Figure 5(B) shows the registration recommendation screen. The registration recommendation screen has the text "Credit card registration is required to reserve a booth" and a "Register" icon 72. If an app member wishes to reserve a booth, they select the "Register" icon 72. If an app member 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.

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

[0124] If the terminal program 28 determines that the received input is the selection of the "Register" icon 72 (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 the 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 verification processes, such as sending the card number and authentication information to a server operated by a credit card company or bank, and then registers the card number and authentication information in the user management database. The server program 37 also sends an HTTP response to the terminal device 20 as a response to the HTTP request containing the card number and authentication information, which includes a registration completion notification indicating that registration has been completed.

[0125] 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 on the determination in step S19 that automatic payment is possible (S19: Yes).

[0126] As shown in Figure 5(C), the store selection screen has multiple store selection icons 73, each with a store name, and a "search" icon 74. The app member selects one store selection icon 73 from the multiple store selection icons 73, and then selects the "search" icon 74.

[0127] As shown in Figure 4, the terminal program 28 of the terminal device 20, based on receiving input from an app member who has selected a store selection icon 73 and a "search" icon 74 (S25), sends an HTTP request to the management server 30 via the internet 11, including the store ID of the store selected by the app member and a request for a reply with reservation information (S26).

[0128] Based on the receipt of an HTTP request containing the store ID and a reply request (S26), the server program 37 of the management server 30 identifies a record in the store management database that has the same store ID as the received store ID, 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).

[0129] The terminal program 28 of the terminal device 20 displays a date and time specification screen on the display 24 based on the receipt of an HTTP response containing store information and store reservation information (S29).

[0130] As shown in Figure 5(D), the date and time selection screen has a calendar 76 consisting of multiple "date" icons 75 and a "confirm" icon 77. The app member selects the "date" icon 75 for the date they wish to reserve.

[0131] The terminal program 28 displays a reservation period input screen (not shown) on the display 24 based on the app member's selection of the "Date" icon 75. 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 type of service. On the reservation period input screen, the app member selects the planned start time and end time of booth use, as well as the type of service. After making these selections, the app member selects the "Confirm" icon 77 on the date and time specification screen.

[0132] As shown in Figure 4, the terminal program 28 generates a reservation request (S31) based on the selection of the "Date" icon 75, the specification of the reservation date, the selection of the scheduled start time and scheduled end time of use, the selection of the service type, and the selection of the "Confirm" icon 77 (S30). The reservation request includes the user ID, store ID, reservation date, scheduled start time of use, scheduled end time of use, and service type. The terminal program 28 sends an HTTP request including the generated reservation request to the management server 30 via the internet 11 (S32). Note that the selection of the service type may be made at check-in rather than at the time of reservation. The processing in step S32 is an example of reservation request processing.

[0133] 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 registers reservation information such as the store ID, reservation date, scheduled start time (start time), scheduled end time (end time), reservation period, and service type included in the reservation request in each field of the identified record, in each field of the column with the item name "Reservation Information" (S33). The process in step S32 is an example of the reservation request reception process. The process in step S33 is an example of the reservation registration process.

[0134] Furthermore, the server program 37 identifies a record in the store management database that has the same store ID as the store ID included in the reservation application. The server program 37 registers reservation information such as the user ID, reservation date, scheduled start time (start time), scheduled end time (end time), reservation period, and service type included in the reservation application in each field of the identified record, in each field of the column with the item name "Store Reservation Information" (S34). Based on the fact that the reservation information has been registered in the user management database and the store management database, i.e., the reservation application has been accepted, the server program 37 sends back an HTTP response to the terminal device 20 as a response to the HTTP request received in step S32, including a reservation completion notification indicating that the reservation has been completed (S35), and terminates the reservation process (end).

[0135] Based on the receipt of 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).

[0136] Next, the check-in process executed by the terminal program 28 and the server program 37 when an app member checks in at a store they visit will be explained.

[0137] The app member 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 app member selects an icon that instructs the display of the check-in screen (Figure 7(A)).

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

[0139] As shown in Figure 7(A), the check-in screen has a "check-in" icon 81. When an app member wants to check in, they select the "check-in" icon 81.

[0140] As shown in Figure 6, based on the selection of the "check-in" icon 81 (S43), the terminal program 28 displays the reading screen (see Figure 7(B)) on the display 24 and activates the camera 29 (S44).

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

[0142] As shown in Figure 6, the terminal program 28 acquires the image data output by the camera 29 based on the app member's input of an imaging instruction (S45) (S46). The terminal program 28 reads the store ID from the acquired image data (S47). Note that the process of reading the store ID from the image data may be performed by a QR code reading application (not shown) implemented on the terminal device 20.

[0143] 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).

[0144] 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 has reservation information registered that has 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 app member has made a reservation (S49).

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

[0146] If the server program 37 determines that a reservation exists (S49: Yes), it reads the reservation information registered in the identified record (S51). The server program 37 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).

[0147] 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).

[0148] 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 type of service, etc. The app member enters the type of service, etc. on the input screen. The input screen may be the same screen as the plan selection screen (see Figure 7(C)) described later. The terminal program 28 accepts input for the type of service, etc. on the input screen (S55).

[0149] 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 confirmation information for payment. When 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 and prompts the app member 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.

[0150] 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).

[0151] As shown in Figure 7(C), the plan selection screen has multiple "service selection" icons 83 that accept the selection of service type (plan), a "number of people" icon 84 that accepts the specification of the number of people, and a "next" icon 85.

[0152] App members select the service type (plan type) and specify the number of users on the plan selection screen, and then select the "Next" icon.

[0153] The terminal program 28 may also display a screen on the display 24 that accepts changes to the scheduled start time and scheduled end time of use specified by the app member at the time of reservation, and may accept such changes.

[0154] As shown in Figure 6, the terminal program 28 displays a final confirmation screen on the display 24 based on the acceptance of the selection of the service type (plan type), the specification of the number of people, and the selection of the "Next" icon 85 on the plan selection screen (S57), or based on the acceptance of the input in step S55 (S58). The service type (plan type) and the specification of the 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 process, are examples of check-in information.

[0155] As shown in Figure 7(D), the final confirmation screen includes text indicating the type of service (plan) such as "30-hour pack," text indicating the number of people such as "1 person," a warning message 86 consisting of the text "Please scan the QR code when you leave the store," a "Yes" icon 87, and a "No" icon 88.

[0156] App members, after reviewing the warning message 86, select the "Yes" icon 87 if they wish to use the booth.

[0157] As shown in Figure 6, the terminal program 28, based on the app member's selection of the "Yes" icon 87 (S59), generates a check-in request including the user ID, store ID, scheduled start time (check-in time), scheduled end time, and service type (S60). The terminal program 28 sends an HTTP request containing the generated check-in request to the management server 30 via the internet 11 (S61). The process in step S61, in which the terminal program 28 sends the check-in request to the management server 30, is an example of the check-in request transmission process.

[0158] The server program 37 of the management server 30 receives an HTTP request including a check-in request (S61). The processing in step S61 is an example of the check-in request reception processing.

[0159] 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 check-in request. The server program 37 also identifies a 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 check-in request 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 check-in request was sent or received in the field of the column labeled "Check-in Time". For example, if an app member wants to start using the service earlier than the scheduled start time specified at the time of reservation, they make an input indicating this on the terminal device 20. Based on this input, the server program 37 registers the time the check-in request was sent or received as the check-in time in the user management database. In that case, the server program 37 changes the scheduled end time of use according to the difference between the determined check-in time and the scheduled start time of use, and registers it in the user management database. The process in step S62 is an example of the first registration process.

[0160] Meanwhile, the store program 48 of the store terminal 40 installed in the store periodically sends an HTTP request to the management server 30 via the internet 11, which includes an inquiry request asking whether or not there is an instruction to unlock the device (S63). For example, the store program 48 periodically sends an HTTP request including an inquiry request to the management server 30 at intervals of several seconds to more than ten seconds.

[0161] Based on receiving the check-in request (S61), the server program 37 sends an HTTP response including an unlock instruction to the store terminal 40 as a response to the HTTP request received in step S63 (S64). The unlock instruction is, for example, a command that the store program 48 can process. The processing in step S64 is an example of the first unlock instruction transmission process.

[0162] The store program 48 of the store terminal 40 receives an HTTP response including an unlock instruction (S64). Based on the receipt of the unlock instruction (S64), the store program 48 sends an unlock command to the door lock device 50 via the LAN 12 attached to the store (S65). The unlock command is a command that can be processed, for example, by the control unit 51 of the door lock device 50. The processing in step S64 is an example of the unlock instruction reception processing. The processing in step S65 is an example of the unlock command transmission processing.

[0163] Based on the receipt of the unlock command (S65), the door lock device 50 unlocks the door (S66). Although not shown in the flowchart, the door lock device 50 relocks the door after a predetermined time has elapsed since unlocking. This predetermined time is, for example, several tens of seconds to several tens of seconds.

[0164] After sending the unlock command (S65), the store program 48 of the store terminal 40 sends an HTTP request to the management server 30 via the internet 11, which includes an unlock notification indicating that the door has been unlocked (S67).

[0165] Based on receiving an HTTP request containing an unlock notification (S67), the server program 37 of the management server 30 sends an HTTP response containing a check-in completion notification to the terminal device 60 as a response to the HTTP request received in step S61 (S68), and terminates the check-in process (end).

[0166] The terminal program 28 of the terminal device 20 receives an HTTP response containing a check-in completion notification (S68). 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 the check-in is complete, and terminates the check-in process (end).

[0167] Figure 7(E) shows the completion notification screen. The completion notification screen has the text "Check-in complete," text indicating the type of service (plan) such as "30-hour pack," text indicating the number of people such as "1 person," and a "Back" icon 89. After the app member confirms the displayed text, they select the "Back" icon 89.

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

[0169] Next, the guest passcode issuance process executed by the terminal program 28 and server program 37 of the terminal device 20 when an app member (inviter) invites a non-app member (guest) will be explained with reference to Figure 8.

[0170] App members who have reserved a booth or checked in operate 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 app member selects the icon that instructs the display of the guest invitation screen (Figure 9(A)).

[0171] As shown in Figure 8, the terminal program 28 of the terminal device 20 displays the guest invitation screen (Figure 9(A)) on the display 24 based on the selection of an icon that instructs the display of the guest invitation screen (Figure 9(A)) (S71) (S72).

[0172] As shown in Figure 9(A), the guest invitation screen has the text "Do you want to invite a guest?" and a "Next" icon 91. If the user wants to invite a guest, they select the "Next" icon 91.

[0173] As shown in Figure 8, the terminal program 28 accepts the selection of the "Next" icon 91 on the guest invitation screen (S73). Based on the acceptance of the selection of the "Next" icon 91, the terminal program 28 generates a reservation information request including the user ID (S74), and sends an HTTP request including the generated reservation information request to the management server 30 via the internet 11 (S75).

[0174] The server program 37 of the management server 30 receives an HTTP request that includes a request for reservation information, etc. (S75). The server program 37 searches the user management database for reservation information and non-reservation usage information that have a user ID that matches the user ID included in the received request for reservation information, etc. If reservation information and non-reservation usage information are found, the server program 37 reads the reservation information and non-reservation usage information from the user management database (S76). Reservation information is information that is registered in the user management database when an app member makes a reservation, as described above. Non-reservation usage information is information that is registered in the user management database when an app member checks in without making a reservation.

[0175] The server program 37 determines, based on the search results, whether reservation information or information about use without a reservation is registered in the user management database (S77). In other words, in step S77, it is determined whether an app member who wishes to invite a guest has made a booth reservation or checked in, and whether the store ID and user ID are registered in association with each other in the user management database. That is, issuing a guest passcode (S86) requires that the store ID and user ID be registered in association with each other in the user management database.

[0176] Furthermore, having a reservation may be the only requirement for issuing a guest passcode. In that case, step S77 determines whether or not the reservation information is registered in the management database. Alternatively, having checked in, regardless of whether or not a reservation exists, may be the only requirement for issuing a guest passcode. In that case, step S77 determines whether or not the check-in time is registered in the reservation information or the information for users without a reservation.

[0177] If the server program 37 determines that an app member who wishes to invite a guest has not made a booth reservation or check-in (S77: No), it sends an HTTP response including an error notification to the terminal device 20 as a response to the HTTP request received in step S75 (S78). If the server program 37 determines that an app member who wishes to invite a guest has made a booth reservation or check-in (S77: Yes), it generates a reservation notification including the store ID contained in the reservation information or no-reservation usage information read in step S76, and sends an HTTP response including the generated reservation notification to the terminal device 20 as a response to the HTTP request received in step S75 (S79). The store ID included in the reservation notification is the store ID of all stores that the app member has reserved. That is, if the app member has made reservations at, for example, three stores, the store IDs of those three stores will be included in the reservation notification.

[0178] Furthermore, as mentioned above, reservation information is deleted from the user management database after the scheduled end time has passed or after check-out, thus preventing the issuance of guest passcodes for "past reservations" whose scheduled end time has passed before the current time.

[0179] The terminal program 28 of the terminal device 20 receives error notifications or reservation notifications sent back by the management server 30 (S78, S79). The terminal program 28 determines whether the received notification is an error notification or a reservation notification (S80). If the terminal program 28 determines that the received notification is an error notification (S80: error notification), it displays the error notification screen (see Figure 9(B)) on the display 24 (S81).

[0180] As shown in Figure 9(B), the error notification screen has the text, "No reservation or check-in has been made. A reservation or check-in is required to invite a guest. Do you want to make a reservation?", a "Reservation" icon 92, and a "Back" icon 93.

[0181] If a user does not wish to invite guests, or if they wish to make a reservation after confirming the date and time of the invitation, they select the "Back" icon 93. If they wish to make a reservation on the spot, they select the "Reservation" icon 92.

[0182] As shown in Figure 8, the terminal program 28 of the terminal device 20 determines whether the icon selected by the user is the "back" icon 93 or the "reservation" icon 92 (S82). If the terminal program 28 determines that the icon selected by the app member (inviter) is the "back" icon 93 (S82: back), it displays the guest invitation screen again on the display 24 (S72). If the terminal program 28 determines that the icon selected by the app member is the "reservation" icon 92 (S82: reservation), it executes the processes from step S17 onwards in the reservation process (see Figure 4). That is, it accepts the booth reservation by the app member. After making a booth reservation, the app member invites guests from the guest invitation screen (see Figure 9(A)).

[0183] In step S80, the terminal program 28 of the terminal device 20 determines that the received notification is a reservation notification (S80: Reservation Notification), and displays a store selection screen (see Figure 9(C)) on the display 24. The store selection screen accepts the selection of a store to invite guests to and the selection (specification) of the number of guests to invite.

[0184] As shown in Figure 9(C), the store selection screen has the text "Please specify the store and number of guests to invite," a pull-down menu 94, and a pull-down menu 95. The pull-down menu 94 has the store names of the stores indicated by the store ID included in the reservation notification received by the terminal program 28 in step S79 (see Figure 8) as selection options. In other words, the pull-down menu 94 is an icon that accepts the selection (specification) of one store to invite guests from among multiple stores for which the app member has currently made a reservation. The pull-down menu 95 has "1 person," "2 people," "3 people," and "4 or more people" as selection options. In other words, the pull-down menu 95 is an icon that accepts the specification of the number of guests to be invited by the app member (inviter). Alternatively, instead of the pull-down menu 95, a text box for the app member to directly input the number of guests may be displayed on the store selection screen.

[0185] Furthermore, if reservations have been made for the same store on different dates, the store selection screen may also include a dropdown menu that allows users to specify a date.

[0186] App members specify the name of the store to which they want to invite guests using the pull-down menu 94, and specify the number of guests to invite using the pull-down menu 95.

[0187] As shown in Figure 8, the terminal program 28 of the terminal device 20 accepts the specification of the store to which the guests will be invited and the specification of the number of guests to be invited (S84). The terminal program 28 generates a guest passcode issuance request that includes a store ID indicating the specified store, the specified number of guests, and a user ID, and sends an HTTP request containing the generated guest passcode issuance request to the management server 30 via the internet 11 (S85). The processing in step S85 is an example of the issuance request transmission process.

[0188] The server program 37 of the management server 30 receives an HTTP request that includes a guest passcode issuance request (S85). The server program 37 generates a unique guest passcode that is not currently registered in the user management database (S86). If there are multiple guests, one guest passcode may be generated for each guest, or one guest passcode may be generated for multiple guests. The following describes an example where one guest passcode is generated for each guest.

[0189] The server program 37 registers the generated guest passcode in the user management database (S87). Specifically, the server program 37 identifies reservation information or non-reservation usage information in the user management database that has a user ID and store ID that match the user ID and store ID included in the guest passcode issuance request received in step S85. The server program 37 registers the generated guest passcode in the field of the sub-column named "Guest Passcode" in the identified reservation information or non-reservation usage information. The process in step S87 is an example of the third registration process.

[0190] Furthermore, the server program 37 reads the store ID and reservation date registered in the identified reservation information or the information for use without a reservation. The server program 37 generates notification information including the read store ID and reservation date and the guest passcode generated in step S86, and sends an HTTP response containing the generated notification information back to the terminal device 20 as a response to the HTTP request received in step S85 (S88). The processing in step S88 is an example of the guest passcode issuance process.

[0191] The terminal program 28 of the terminal device 20 receives an HTTP response containing notification information sent back by the management server 30 (S88). The terminal program 28 displays a guest passcode notification screen (Figure 9(D)) on the display 24 to notify the app member of the received notification information (S89).

[0192] As shown in Figure 9(D), the guest passcode notification screen contains the name of the store indicated by the store ID included in the received notification information, and characters indicating the date indicated by the reservation date. In the example shown in Figure 9(D), the guest passcode notification screen contains the text, "We are inviting a guest to Itabashi store on September 1, 2022."

[0193] The guest passcode notification screen also displays the text "Inviting guests incurs a fee," the text "Guest Passcode," and the guest passcode included in the received notification. In the example shown in Figure 9(D), the guest passcode "YAMADA15A2C" is displayed.

[0194] The guest passcode notification screen also includes the text "Please email the guest passcode to your guest (inviter)," an "Launch Mailer" icon 97, and an "Exit" icon 98.

[0195] If the user wants to immediately notify the guest of the guest passcode they received, they select the "Launch Mailer" icon 97. If they want to notify the guest of the guest passcode later, they select the "Exit" icon 98.

[0196] As shown in Figure 8, the terminal program 28 of the terminal device 20 accepts the selection of either the "Launch Mailer" icon 97 or the "Exit" icon 98 on the guest passcode notification screen (S90). The terminal program 28 determines whether the selected icon is the "Exit" icon 98 or the "Launch Mailer" icon 97 (S91). If the terminal program 28 determines that the selected icon is the "Exit" icon 98 (S91: Exit), it terminates the process (End). If the terminal program 28 determines that the selected icon is the "Launch Mailer" icon 97 (S91: Launch Mailer), it launches the mailer 61 via the OS 26 (S92). When launching the mailer 61, the terminal program 28 passes the store name, invitation date, and guest passcode displayed on the guest passcode notification screen to the mailer 61 via the OS 26. In addition to the store name and guest passcode, the terminal program 28 may also pass the store's address and map data including the store to the mailer 61.

[0197] The app member (inviter) specifies the guest's email address and enters the invitation time, etc., in the launched mailer 61 (S93). The mailer 61 accepts the guest's email address, etc. (S93) and generates a guest passcode notification email containing the store name and guest passcode received from the terminal program 28 (S94). The mailer 61 sends the generated guest passcode notification email to the terminal device 60 held by the guest via a mail server (not shown) (S95). The mailer 61 installed in the terminal device 60 held by the guest receives the guest passcode notification email.

[0198] Next, the guest check-in process executed by the server program 37 of the management server 30 when a guest enters the store using a guest passcode will be explained with reference to Figure 10.

[0199] The guest visits the store indicated in the guest passcode notification email received by the terminal device 60, enters the passcode into the terminal device 60 (S101), and launches the QR code reading application 62 (S102). The launched QR code reading application 62 then activates the camera 29 and accepts the guest's instruction to take an image (S103).

[0200] The guest has the camera 29 of the terminal device 60 capture an image of the second QR code (registered trademark) affixed to the exterior surface of the door leading to the booth.

[0201] Based on the reception of the imaging instruction (S103), the QR code reading application 62 causes the camera 29 to capture the second QR code (registered trademark) (S104) and generates image data. The QR code reading application 62 reads the first URL from the image data and displays the read first URL on the display 24 of the terminal device 60.

[0202] The guest inputs information into the terminal device 60 (S106) and launches the browser 27 (S107). The launched browser 27 accesses the first URL. Specifically, the browser 27 sends an HTTP request containing a web page request that includes the first path included in the first URL to the management server 30 indicated by the address included in the first URL, via the internet 11 (S108). The web page request containing the first path is an example of a screen data request.

[0203] The server program 37 of the management server 30 receives an HTTP request that includes a web page request (S108). The server program 37 obtains the guest access web page data indicated by the first path included in the received web page request (S109). At that time, the server program 37 obtains the store ID indicated by the first path. In other words, the server program 37 identifies which store the guest who requested the guest access web page data is in. The server program 37 sends back an HTTP response to the terminal device 60 as a response to the HTTP request received in step S108, including the obtained guest access web page data, the store ID, and the store name indicated by the store ID (S110). The guest access web page data is screen data of an input screen that can accept the input of a guest passcode, and is, for example, HTML data including JavaScript. The guest access web page data is an example of guest access screen data. The processing in step S110 is an example of guest access screen data return processing.

[0204] The browser 27 of the terminal device 60 receives an HTTP response containing guest entry web page data, store ID, and store name (S110). The browser 27 displays the guest entry screen (see Figure 11(A)) indicated by the received guest entry web page data on the display 24 of the terminal device 60 (S111).

[0205] Figure 11(A) shows the guest entry screen. The guest entry screen has the store name received in step S110. Specifically, the guest entry screen has the text "You will enter the Itabashi store as a guest (invited guest)," the text "If you enter, the app member (inviter) will be charged," the text "Please enter the guest passcode notified by the inviter," a text box 101, and an "OK" icon 102.

[0206] The guest pastes or enters the guest passcode included in the email received in step S95 (see Figure 8) into the text box 101, and then selects the "OK" icon 102.

[0207] The guest entry screen may also include a text box for entering the store name. In that case, the second QR code (registered trademark) does not need to include the store ID or information indicating the store ID, and a common second QR code (registered trademark) can be used at each store.

[0208] Browser 27 accepts the input of a guest passcode and the selection of an "OK" icon 102 according to the JavaScript contained in the guest entry web page data (S112). Browser 27 also generates a guest check-in request according to the JavaScript contained in the guest entry web page data (S113). The guest check-in request includes the entered guest passcode and the store ID received in step S110. Browser 27 sends an HTTP request containing the generated guest check-in request to the management server 30 via the internet 11 (S114).

[0209] The server program 37 of the management server 30 receives an HTTP request including a guest check-in request (S114). The processing in step S114 is an example of the guest check-in request reception processing. The server program 37 determines whether the combination of store ID and guest passcode included in the guest check-in request is registered in the user management database (S115). Note that in step S87 (see Figure 8), the guest passcode generated by the server program 37 is registered in the user management database in association with the store ID. The processing in step S115 is an example of the first matching processing.

[0210] If the server program 37 determines that the combination of store ID and guest passcode included in the guest check-in application is not registered in the user management database (S115: No), it sends an HTTP response including an error notification back to the terminal device 60 as a response to the HTTP request received in step S114 (S116).

[0211] Although not shown in the flowchart of Figure 10, the browser 27 of the terminal device 60, upon receiving an HTTP response including an error notification (S116), displays an error notification screen (not shown) on the display 24 of the terminal device 60, which is indicated by the web page image data included in the error notification. The error notification screen may have the text, for example, "Incorrect passcode." The error notification screen may also have a text box for re-entering the guest passcode.

[0212] If the server program 37 determines that the combination of store ID and guest passcode included in the guest check-in application is registered in the user management database (S115: Yes), it reads and obtains reservation information or no-reservation usage information that has the said combination of store ID and guest passcode from the user management database (S117).

[0213] The server program 37 determines whether the app member who invited the guest (inviter) is present in the booth based on the acquired reservation information or non-reservation usage information (S118). Specifically, the server program 37 determines whether a check-in time is registered in the reservation information or non-reservation usage information acquired in step S117. If the server program 37 determines that the app member who invited the guest (inviter) is not present in the booth (S118: No), it sends an HTTP response to the terminal device 60 as a response to the HTTP request received in step S114, including an error notification indicating that entry into the booth is not possible (S119). In other words, the presence of the inviter is a requirement for unlocking the door lock device 50. That is, if the inviter is not present in the booth, the guest's entry into the booth is restricted.

[0214] Although not shown in the flowchart of Figure 10, the browser 27 of the terminal device 60, upon receiving an HTTP response including an error notification (S119), displays an error notification screen (not shown) on the display 24 of the terminal device 60, which is indicated by the web page image data included in the error notification. The error notification screen has text such as, "You cannot enter the booth because the inviter has not checked in."

[0215] Furthermore, although not shown in the flowchart of Figure 10, if the server program 37 determines that the app member who invited the guest (inviter) is not present in the booth (S118: No), it may include a guest arrival notification in its response to the HTTP request from the terminal device 20 held by the app member, indicating that the guest has arrived at the store. The guest arrival notification may include, for example, text notifying the guest of their arrival, the name of the store the guest is visiting, and the date and time the guest check-in request (S114) was received. The guest arrival notification may also be sent to the app member (inviter) by email. The app member's email address is pre-registered in the user management database, for example, along with their name and address.

[0216] Meanwhile, the store program 48 of the store terminal 40 installed in the store periodically sends an HTTP request to the management server 30 via the internet 11, as described above, which includes an inquiry request asking whether or not an unlocking instruction has been given (S63).

[0217] In step S118, if the server program 37 determines that the app member who invited the guest (inviter) is present in the booth (S118: Yes), it sends an HTTP response including an unlock instruction to the store terminal 40 as a response to the HTTP request received in step S63 (S121). The processing in step S121 is an example of the third unlock instruction transmission process.

[0218] The store program 48 of the store terminal 40 receives an HTTP response including an unlock instruction (S121). Based on the receipt of the unlock instruction (S121), the store program 48 sends an unlock command to the door lock device 50 via the LAN attached to the store (S122). The unlock command is, for example, a command that can be processed by the control device of the door lock device 50. The processing in step S121 is an example of the process of receiving an unlock instruction. The processing in step S122 is an example of the process of sending an unlock command.

[0219] The door lock device 50 unlocks the door (S123) upon receiving a command to unlock (S122). Although not shown in the flowchart, the door lock device 50 locks the door after a predetermined time has elapsed since unlocking, as described above.

[0220] After sending the unlock command (S122), the store program 48 of the store terminal 40 sends an HTTP request to the management server 30 via the internet 11, which includes an unlock notification indicating that the door has been unlocked (S124).

[0221] Based on receiving an HTTP request containing an unlock notification (S124), the server program 37 of the management server 30 sends back an HTTP response to the terminal device 60 as a response to the HTTP request received in step S114 (S125), which includes unlock information indicating that the door has been unlocked. The unlock information includes web page data showing the unlock notification screen (see Figure 11(B)).

[0222] The browser 27 of the terminal device 60 receives an HTTP response containing unlock information (S125). The browser 27 displays an unlock notification screen on the display 24 of the terminal device 60, which is indicated by the received unlock information.

[0223] As shown in Figure 11(B), the unlock notification screen displays the text, "The lock has been released. You can now enter."

[0224] Meanwhile, after executing step S67 (see Figure 6), the terminal program 28 periodically sends an HTTP request containing the inquiry request shown in Figure 10 to the management server 30 via the internet 11 (S127).

[0225] After sending the unlock information (S125), the server program 37 of the management server 30 sends an HTTP response containing a guest entry notification to the inviter's terminal device 20 as a response to the HTTP request received in step S127 (S128) to notify the inviter that the guest has entered the booth. The guest entry notification contains screen data showing the guest entry notification screen (see Figure 11(C)), the inviter's last name or full name, and the store name. The inviter's name and store name are included in the reservation information or non-reservation usage information obtained from the user management database in step S117. The guest entry notification is an example of guest entry information. The processing in step S128 is an example of the guest entry information transmission process.

[0226] The terminal program 28 of the inviter's terminal device 20 receives an HTTP response containing a guest entry notification (S128). The terminal program 28 displays the guest entry notification screen indicated by the received guest entry notification on the display 24 (S129). The process in step S129 is an example of the guest entry information display process.

[0227] As shown in Figure 11(C), the guest entry notification screen includes the inviter's last name (or full name) and the store name. In the example shown in Figure 11(C), the guest entry notification screen includes the text, "A guest invited by Mr. / Ms. Yamada is entering the Itabashi store." The guest entry notification screen also includes the text, "Guest usage fees will be incurred upon the guest's entry," and an "OK" icon 103.

[0228] The app member (inviter) selects the "OK" icon 103 on the guest entry notification screen after confirming that the guest has arrived. Although not shown in the flowchart in Figure 10, the terminal program 28 of the terminal device 20 removes the guest entry notification screen from the display 24 based on the selection of the "OK" icon 103.

[0229] After sending a lock release notification or a guest entry notification (S125, S128), the server program 37 of the management server 30 registers the guest check-in time in the user management database (S130). Specifically, the server program 37 registers the guest check-in time in the field of the sub-column named "Guest Check-in Time" in the reservation information or no-reservation usage information identified in step S117. The guest check-in time is, for example, the time when the server program 37 receives the guest check-in request (S114) or the time when the server program 37 sends a lock release instruction (S121) to the store terminal 40. The guest check-in time is an example of guest check-in information. The process in step S130 is an example of the guest check-in information registration process.

[0230] Next, the process executed by the server program 37 of the management server 30 when a guest leaves the store will be explained with reference to Figure 12.

[0231] The guest inputs information into the terminal device 60 (S131) ​​and launches the QR code reading application 62 (S132). The launched QR code reading application 62 then activates the camera 29 and accepts the guest's imaging instruction (S133).

[0232] The guest has the camera 29 of the terminal device 60 capture an image of the third QR code (registered trademark) that is affixed to the interior side of the door leading to the booth.

[0233] Based on the reception of the imaging instruction (S133), the QR code reading application 62 causes the camera 29 to capture the third QR code (registered trademark) (S134) and generates image data. The QR code reading application 62 reads the third URL from the image data and displays the read third URL on the display 24 of the terminal device 60.

[0234] The guest inputs information into the terminal device 60 (S136) to launch the browser 27 (S137). The launched browser 27 accesses the third URL. Specifically, the browser 27 generates a web page request that includes the third path contained in the third URL. The browser 27 sends an HTTP request containing the generated web page request to the server address contained in the third URL via the internet 11 (S138). The web page request containing the third path is an example of a screen data request.

[0235] The server program 37 of the management server 30 receives an HTTP request that includes a web page request (S138). The server program 37 obtains the guest exit web page data indicated by the third path included in the received web page request (S139). At that time, the server program 37 obtains the store ID indicated by the third path. In other words, the server program 37 identifies which store the guest who requested the guest exit web page data is in. The server program 37 sends back an HTTP response to the terminal device 60 as a response to the HTTP request received in step S138, including the obtained guest exit web page data, the store ID, and the store name indicated by the store ID (S140). The guest exit screen indicated by the guest exit web page data is an input screen that can accept the input of a guest passcode, and the guest exit web page data is, for example, HTML data including JavaScript. The guest exit web page data is an example of guest exit screen data. The processing in step S140 is an example of guest exit screen data return processing.

[0236] The browser 27 of the terminal device 60 receives an HTTP response containing guest exit web page data, store ID, and store name (S140). The browser 27 displays the guest exit screen (see Figure 13(A)) indicated by the received guest exit web page data on the display 24 of the terminal device 60 (S141).

[0237] Figure 13(A) shows the guest exit screen. The guest exit screen has the store name received in step S140. Specifically, the guest exit screen has the text "Leaving Itabashi store," the text "Please enter the guest passcode notified by the inviter," a text box 104, and an "OK" icon 105.

[0238] The guest pastes or enters the guest passcode included in the email received in step S95 (see Figure 8) into the text box 104, and then selects the "OK" icon 105.

[0239] The guest exit screen may also include a text box for entering the store name. In that case, the 3rd QR code (registered trademark) does not need to include the store ID or information indicating the store ID, and a common 3rd QR code (registered trademark) can be used at each store.

[0240] As shown in Figure 12, the browser 27 accepts the input of a guest passcode and the selection of an "OK" icon 105 according to the JavaScript contained in the guest exit web page data (S142). The browser 27 also generates a guest checkout request according to the JavaScript contained in the guest exit web page data (S143). The guest checkout request includes the entered guest passcode and the store ID received in step S140. The browser 27 sends an HTTP request containing the generated guest checkout request to the management server 30 via the internet 11 (S144).

[0241] The server program 37 of the management server 30 receives an HTTP request including a guest checkout request (S144). The server program 37 determines whether the combination of store ID and guest passcode included in the guest checkout request is registered in the user management database (S145). The processing in step S144 is an example of the guest checkout request reception processing. The processing in step S145 is an example of the second matching processing.

[0242] If the server program 37 determines that the combination of store ID and guest passcode included in the guest checkout request is not registered in the user management database (S145: No), it sends an HTTP response including an error notification back to the terminal device 60 as a response to the HTTP request received in step S144 (S146).

[0243] Although not shown in the flowchart of Figure 12, the browser 27 of the terminal device 60, upon receiving an HTTP response including an error notification (S146), displays an error notification screen (not shown) on the display 24 of the terminal device 60, which is indicated by the web page image data included in the error notification. The error notification screen may have the text, for example, "Incorrect passcode." The error notification screen may also have a text box for re-entering the guest passcode.

[0244] If the server program 37 determines that the combination of store ID and guest passcode included in the guest checkout request is registered in the user management database (S145: Yes), it identifies the reservation information or no-reservation usage information that has the said combination of store ID and guest passcode in the user management database (S147).

[0245] Meanwhile, the store program 48 of the store terminal 40 installed in the store periodically sends an HTTP request to the management server 30 via the internet 11, as described above, which includes an inquiry request asking whether or not an unlocking instruction has been issued (S63).

[0246] If the server program 37 determines in step S145 that the combination of the store ID and guest passcode is correct (S145: Yes), it sends an HTTP response including an unlock instruction to the store terminal 40 as a response to the HTTP request received in step S63 (S148). The processing in step S148 is an example of the fourth unlock instruction transmission process.

[0247] The store program 48 of the store terminal 40 receives an HTTP response including an unlock instruction (S148). Based on the receipt of the unlock instruction (S148), the store program 48 inputs an unlock command to the door lock device 50 via the LAN attached to the store (S149).

[0248] Based on the receipt of the unlock command (S149), the door lock device 50 unlocks the door (S150). Although not shown in the flowchart, as described above, the door lock device 50 locks the door after a predetermined time has elapsed since unlocking.

[0249] After sending the unlock command (S149), the store program 48 of the store terminal 40 sends an HTTP request to the management server 30 via the internet 11, which includes an unlock notification indicating that the door has been unlocked (S151).

[0250] Based on receiving an HTTP request containing an unlock notification (S151), the server program 37 of the management server 30 sends back an HTTP response to the terminal device 60 as a response to the HTTP request received in step S144 (S152), which includes unlock information indicating that the door has been unlocked. The unlock information includes web page data showing the unlock notification screen (see Figure 13(B)).

[0251] The browser 27 of the terminal device 60 receives an HTTP response containing unlock information (S152). The browser 27 displays an unlock notification screen on the display 24 of the terminal device 60, which is indicated by the received unlock information (S153).

[0252] As shown in Figure 13(B), the unlock notification screen displays the text, "The lock has been released. You can now leave."

[0253] As shown in Figure 12, after sending the unlock information (S152), the server program 37 of the management server 30 identifies the guest check-out time and registers it in the user management database (S154). The server program 37 identifies the guest check-out time as, for example, the time when the guest check-out request (S144) was received, the time when the unlock instruction (S148) was sent, the time when the unlock notification (S151) was received, or the time when the unlock information (S152) was sent. The guest check-out time is an example of the first guest check-out information. The processing in step S154 is an example of the first guest check-out information registration process.

[0254] The server program 37 calculates the guest usage time, which is the time the guest used the booth, based on the guest check-out time identified in step S154 and the guest check-in time registered in the reservation information or no-reservation usage information identified in step S147 (S155). The server program 37 also calculates the guest usage fee based on the calculated guest usage time and the usage fee per unit time registered in the store management database (S155). The server program 37 registers the guest check-in time identified in step S154 and the guest usage time and guest usage fee calculated in step S155 in the reservation information or no-reservation usage information identified in step S147 (S156).

[0255] Meanwhile, after executing step S67 (see Figure 6), the terminal program 28 periodically sends an HTTP request containing the inquiry request shown in Figure 12 to the management server 30 via the internet 11 (S127).

[0256] The server program 37 of the management server 30 registers the guest usage fee and other information in the user management database (S156), and then, in order to notify the app member (inviter) that the guest has left the booth, it sends an HTTP response including a guest departure notification to the inviter's terminal device 20 as a response to the HTTP request received in step S127 (S157). The guest departure notification includes screen data showing the guest departure notification screen (see Figure 13(C)), the inviter's last name or full name, and the store name. The inviter's name and store name are information included in the reservation information or non-reservation usage information identified in step S145. The guest departure notification may also include the guest usage time and guest usage fee calculated in step S155. The guest departure notification is an example of guest departure information. The processing in step S157 is an example of guest departure information transmission processing.

[0257] The terminal program 28 of the inviter's terminal device 20 receives an HTTP response including a guest departure notification (S157). The terminal program 28 displays the guest departure notification screen indicated by the received guest departure notification on the display 24 (S158). The process in step S158 is an example of the guest departure information display process.

[0258] As shown in Figure 13(C), the guest departure notification screen includes the inviter's last name (or full name) and the store name. In the example shown in Figure 13(C), the guest departure notification screen has the text "The guest invited by Mr. / Ms. Yamada has left the Itabashi store," the text "The guest usage fee is 250 yen," and an "OK" icon 106. The guest departure notification screen may also include text indicating the guest's usage time.

[0259] The app member (inviter) confirms that the guest has left the room on the guest departure notification screen and then selects the "OK" icon 106. Although not shown in the flowchart in Figure 12, the terminal program 28 of the terminal device 20 removes the guest departure notification screen from the display 24 based on the selection of the "OK" icon 106.

[0260] Furthermore, if the app member (inviter) has invited multiple guests, a guest departure notification screen will be displayed on the terminal device 20's display 24 each time a guest leaves.

[0261] Next, the checkout process executed by the terminal program 28 and the server program 37 when an app member finishes using a booth and checks out upon leaving the store will be explained with reference to Figures 14 and 15.

[0262] The app member 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 app member selects an icon that instructs the user to display the checkout screen (see Figure 16(A)).

[0263] Based on the fact that the above icon has been selected on the home screen (S161), the terminal program 28 displays the checkout screen on the display 24 (S162).

[0264] As shown in Figure 16(A), the checkout screen includes text indicating the store name, the words "Checking in", a time display indicating the time the booth was used (e.g., "02:50:34"), and a "Checkout" icon 111. When an app member wants to check out, they select the "Checkout" icon 111.

[0265] As shown in Figure 14, based on the selection of the "checkout" icon 111 (S163), the terminal program 28 displays the reading screen (see Figure 16(B)) on the display 24 and activates the camera 29 (S164).

[0266] As shown in Figure 16(B), the reading screen has an image display area 112 that displays the image captured by the camera 29. The app member points the camera 29 at the first QR code (registered trademark) installed in the store and inputs an instruction to capture the first QR code (registered trademark).

[0267] As shown in Figure 14, the terminal program 28 acquires image data output by the camera 29 based on the input of an imaging instruction from the app member (S165) (S166). The terminal program 28 reads the store ID from the acquired image data (S167). Note that the process of acquiring the store ID from the image data may also be performed by the QR code reading application implemented on the terminal device 20.

[0268] The terminal program 28 generates a checkout request including the acquired store ID and the user ID stored in memory 22, and sends an HTTP request including the generated checkout request to the management server 30 via the internet 11 (S168). The processing in step S168 is an example of the checkout request transmission process.

[0269] The server program 37 of the management server 30 receives an HTTP request that includes the store ID, user ID, and checkout request (S168). The processing in step S168 is an example of the checkout request reception processing.

[0270] The server program 37 identifies reservation information or unreserved usage information in the user management database that has a user ID that matches the user ID included in the received HTTP request (S169). The server program 37 reads the end time (scheduled end time of use) registered in the identified reservation information or unreserved usage information and determines whether the current time output by the clock module 34 exceeds the read end time (S170). In other words, the server program 37 determines whether the app member used the booth beyond the scheduled time, or in other words, whether the usage time was extended (so-called time extension) (S170).

[0271] If the server program 37 determines that the usage period has not been extended (S170: No), it determines the current time or the scheduled end time of use as the checkout time (S171). If the server program 37 determines that the usage period has been extended (S170: Yes), it determines the current time or the time the checkout request (S168) was received as the checkout time (S172).

[0272] The server program 37 moves the store ID, guest passcode, check-in time, guest check-in time, guest check-out time, guest usage time, and guest usage fee, which were identified in step S169 and registered in the reservation information or no-reservation usage information, to the field of the column with the item name "Usage Information" (S173). Note that the guest passcode etc. registered in the reservation information or no-reservation usage information are deleted. The process in step S173 is an example of a deletion process.

[0273] The server program 37 registers the checkout time determined in step S171 or step S172 in the field of the column labeled "Usage Information" (S174). The store ID, checkout time, and usage time registered in the field of the column labeled "Usage Information" are examples of checkout information. The processing in steps S173 and S174 is an example of the second registration process.

[0274] The server program 37 calculates the usage time of the app member based on the check-in and check-out times registered in the usage information, and calculates the user usage fee based on the calculated usage time, the usage fee per unit time registered in the store management database, and the type of service registered in the usage information (S175). The server program 37 registers the calculated user usage fee in the usage information of the user management database (S176).

[0275] The server program 37 determines whether the guest check-in time is registered in the usage information (S177). That is, the server program 37 determines whether the app member who checked out had invited the guest. If the server program 37 determines that the app member who checked out had invited the guest (S177: Yes), it determines whether the guest check-out time is registered in the usage information (S178). That is, the server program 37 determines whether the guest has already left the store or left the store together with the app member (inviter). If the server program 37 determines that the guest left the store together with the app member (inviter) (S178: No), it determines the check-out time, which is the time the app member left the store, as the guest check-out time, and registers the determined guest check-out time in the field of the column with the item name "Guest Check-out Time" in the usage information (S179). The processing in step S178 is an example of a determination process. The guest check-out time is an example of second guest check-out information. Step S179 is an example of second guest check-out information registration processing.

[0276] The server program 37 calculates the guest's usage time based on the guest check-in time and guest check-out time registered in the usage information, and registers the calculated guest usage time in the item named "Guest Usage Time" in the usage information (S180). The server program 37 also calculates the guest usage fee based on the calculated guest usage fee, the usage fee per unit time registered in the store management database, and the type of service, and registers the calculated guest usage fee in the field of the column labeled "Guest Usage Fee" in the usage information (S181).

[0277] Furthermore, as shown in Figure 15, the server program 37 sends an HTTP response containing an unlock instruction back to the store terminal 40 as a response to an HTTP request (S63) periodically sent from the store terminal 40 (S182). The processing in step S182 is an example of the second unlock instruction transmission process.

[0278] The store program 48 of the store terminal 40, upon receiving an unlock instruction (S182), sends an unlock command to the door lock device 50 via the LAN 12 installed in the store (S183). The door lock device 50, upon receiving the unlock command (S183), unlocks the door (S184). The process in step S182 is an example of the process of receiving an unlock instruction. The process in step S183 is an example of the process of sending an unlock command.

[0279] Based on the fact that the store program 48 of the store terminal 40 has sent an unlock command to the door lock device 50, it sends an HTTP request including an unlock notification to the management server 30 via the internet 11 (S185).

[0280] Based on receiving the unlock notice (S185), the server program 37 of the management server 30 returns an HTTP response including unlock information as a response to the HTTP request including the checkout application received in step S168 (see FIG. 14) to the terminal device 20 of the app member (S186). The unlock information includes unlock notice screen data.

[0281] The terminal program 28 of the terminal device 20 receives an HTTP response including unlock information (S186). The terminal program 28 causes the display 24 to display the unlock notice screen (see FIG. 13(B)) indicated by the unlock notice screen data included in the received unlock information (S187).

[0282] On the other hand, after transmitting the HTTP response including the unlock information (S186), the server program 37 of the management server 30 generates checkout completion notice screen data indicating a checkout completion notice screen (see FIGS. 16(C) and 16(D)) (S188). Specifically, the server program 37 reads out the user usage fee registered in the user management database in S176, the guest usage time and guest usage fee registered in the user management database in steps S180 and S181, and other information from the user management database. The server program 37 inputs the read information such as the user usage fee into the format data pre-stored in the memory 32 to generate the checkout completion notice screen data.

[0283] On the other hand, after receiving the HTTP response including the unlock information (S186), the terminal program 28 of the terminal device 20 periodically transmits an HTTP request including a fee inquiry request to the management server 30 through the Internet 11 (S189).

[0284] The server program 37 of the management server 30 sends back an HTTP response containing the checkout notification screen data generated in step S188 to the terminal device 20 as a response to the HTTP request received in step S189 (S190). The processing in step S190 is an example of charge notification processing.

[0285] The terminal program 28 of the terminal device 20 receives an HTTP response containing checkout notification screen data (S190). The terminal program 28 displays the checkout notification screen indicated by the received checkout notification screen data on the display 24 (S191). The processing in step S191 is an example of the fee display processing.

[0286] Figure 16(C) shows the checkout notification screen displayed on display 24 when the app member has not invited any guests. The checkout notification screen includes the words "Usage Details," characters (numbers) indicating the time of entry, time of departure, duration of stay, and number of users, characters indicating the type of service (plan) used, and characters (numbers) indicating the billing amount. In other words, the checkout notification screen displays the charges incurred by the app member as a result of using the booth.

[0287] Figure 16(D) shows the checkout notification screen displayed on display 24 when an app member invites a guest. The checkout notification screen includes the words "Usage Details," characters (numbers) indicating the entry time, exit time, stay time, and number of users, characters indicating the type of service (plan) used, and characters (numbers) indicating the amount incurred as a result of the app member's use of the booth (user usage fee). The checkout notification screen also includes the words "Guest 1" and "Guest 2," characters (numbers) indicating the guest's entry time, exit time, and stay time, characters (numbers) indicating the total usage time of the guest, and characters (numbers) indicating the guest's usage fee (guest usage fee). The checkout notification screen also includes characters (numbers) indicating the billing amount, which is the sum of the user usage fee and the guest usage fee, and is the amount to be billed to the app member. In other words, the checkout notification screen displays the user usage fee incurred as a result of the app member's use of the booth, the guest usage fee incurred as a result of the guest's use of the booth, and the total amount of the user usage fee and guest usage fee (billing amount).

[0288] As shown in Figure 15, the server program 37 of the management server 30 executes a settlement process (S192) by sending the user usage fee, guest usage fee, and payment information registered in the user management database to servers operated by credit card companies and banks via the Internet 11, and then terminates the checkout process (end). The process in step S192 is an example of a settlement process.

[0289] [Effects of the Embodiment] In this embodiment, a non-app member (guest) invited by an app member can enter the booth where the inviter is waiting, even if the terminal program 28 is not installed on their terminal device 60, and without having to contact the inviter to have the door unlocked. In addition, the guest check-in time, which indicates that the guest has entered the booth, is registered and managed in the user management database in association with the inviter's user ID.

[0290] Furthermore, the server program 37 of the management server 30 issues a guest passcode only when an application member requests one, thus preventing the unnecessary issuance of guest passcodes.

[0291] Furthermore, the server program 37 of the management server 30 unlocks the door only if the inviter, who is an app member, is present in the booth. This prevents guests from entering the booth even if the inviter is not present.

[0292] Furthermore, the fee charged to the inviter for using the booth (user usage fee) and the fee charged to the guest invited by the inviter for using the booth (guest usage fee) will be charged to the inviter. Therefore, even non-app members who are not subscribed to the service provided by the service provider can use the booth.

[0293] Furthermore, since the inviter is notified of the fees charged for using the booth (user usage fee) and the fees charged for using the booth by the guest (guest usage fee), the inviter can easily recognize the amount spent on inviting guests.

[0294] The guest passcode is deleted from the user management database once the inviter (app member) checks out. This prevents the previously invited guest from accidentally entering the booth the next time the app member rents one.

[0295] Furthermore, the door lock is released when the guest uses the camera 29 of their terminal device 60 to scan the second QR code (registered trademark) installed in the store. Therefore, it is prevented that the door lock will be released even if the guest is not present in the store. As a result, the security of the booth is further enhanced.

[0296] Guests can unlock the door and exit by scanning the third QR code (registered trademark) installed in the store with the camera 29 of their terminal device 60. In other words, guests can leave the booth before their inviter. This also prevents the door from being accidentally unlocked when the guest is not in the booth. Furthermore, the time when the guest leaves the booth (guest checkout time) is registered and managed in the user management database.

[0297] Furthermore, if the host checks out, the door is unlocked, and the guest leaves together with the host, the guest's check-out is considered to have occurred together with the host. Therefore, the guest is spared the trouble of entering a guest passcode into their terminal device 60.

[0298] Furthermore, the terminal device 20 is notified when a guest enters the booth and when a guest leaves the booth. Therefore, the inviter can confirm that the guest arrived and that the guest left promptly.

[0299] [Differentiation] In the above-described embodiment, an example was given in which one door was installed in each store. However, one door may be installed in each booth. In that case, the second QR code (registered trademark) and the third QR code (registered trademark) may be codes that can read a door ID that identifies the door, either in place of the store ID or in addition to the store ID.

[0300] In the above embodiment, an example was described in which the second QR code (registered trademark) installed on the outside of the door and the third QR code (registered trademark) installed on the inside of the door are different. However, the second QR code (registered trademark) and the third QR code (registered trademark) may be the same. In that case, when the server program 37 of the management server 30 receives a web page request sent by the terminal device 60 owned by the guest (S108, S138), it determines whether or not the guest check-in time is registered in the user management database. If the server program 37 determines that the guest check-in time is not registered, it sends an HTTP response containing guest entry web page data to the terminal device 60 (S110). If the server program 37 determines that the guest check-in time is registered, it sends an HTTP response containing guest exit web page data to the terminal device 60 (S140).

[0301] In the above embodiment, an example was described in which a guest passcode is issued (S88) on the condition that the app member has applied for the issuance of a guest passcode (S85). However, a guest passcode may also be issued on the condition that the app member has made a booth reservation. In other words, a guest passcode may be issued along with a booth reservation, even if the app member does not apply for the issuance of a guest passcode.

[0302] In the above-described embodiment, an example was given in which the door lock device 50 locks the door after a certain period of time has elapsed since it was unlocked. However, the door lock device 50 may also lock the door when it receives a lock command. In that case, the server program 37 of the management server 30 sends an HTTP response including a lock command back to the store terminal 40 based on the fact that a certain period of time has elapsed since the transmission of the unlock command (S63, S121, S148). The store program 48 of the store terminal 40 sends a lock command to the door lock device 50 based on the fact that it has received the lock command.

[0303] In the above-described embodiment, an example was described in which the door lock is released for a guest to enter, on the condition that the app member is present in the booth. However, the door lock may be released for a guest to enter even if the app member is not present in the booth.

[0304] In the above-described embodiment, an example was described in which the browser 27 of the terminal device 60 acquires the first URL by the guest imaging the second QR code (registered trademark) using the terminal device 60. However, the first URL may be transmitted to the terminal device 20 together with the guest passcode. The app member (inviter) notifies the guest of the guest passcode and the first URL by email. The guest accesses the notified first URL.

[0305] In the above-described embodiment, an example was described in which the guest invited by the app member (inviter) is a non-app member. However, the guest invited by the inviter may be an app member. For example, when app members meet at a booth, one app member can invite another app member as a guest.

Explanation of Reference Numerals

[0306] 10 ··· Service providing 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

1. A management server having a first communication interface connected to the internet, a first memory, and a first controller, A terminal device having a second communication interface connected to the internet, a second memory, a display, and a second controller, and implementing a terminal program, A door lock device installed at the entrance / exit of the rental space in the store, The system comprises a door lock device, a third communication interface connected to the internet, and a store terminal having a third controller. The second controller described above is: A check-in request transmission process that obtains store identification information and sends a check-in request containing the obtained store identification information and user identification information to the management server via the second communication interface, The process involves obtaining the above store identification information, and sending a checkout request containing the obtained store identification information and the above user identification information to the management server via the second communication interface. The first controller described above is A check-in request reception process that receives the check-in request through the first communication interface described above, Based on the receipt of the above check-in request, a first registration process is performed to associate the above user identification information and check-in information and store them in the above first memory, Based on the receipt of the above check-in request, a first unlock instruction transmission process is performed to transmit an unlock instruction to the store terminal via the first communication interface, A checkout request reception process that receives the checkout request through the first communication interface described above, Based on the receipt of the above checkout request, a second registration process is performed to associate the above user identification information and checkout information and store them in the first memory, Based on the receipt of the above checkout request, a second unlock instruction transmission process is performed, which transmits an unlock instruction to the store terminal via the first communication interface. A third registration process is performed, in which, based on the determination that the above store identification information and the above user identification information are registered in the first memory, a guest passcode is generated, and the generated guest passcode is associated with the above user identification information and the above store identification information and stored in the first memory; A guest passcode issuance process that transmits notification information including the above-mentioned guest passcode to the terminal device via the above-mentioned first communication interface, Upon receiving a guest check-in request containing the above store identification information and guest passcode, the guest check-in request reception process is performed. A first matching process that determines whether the combination of the store identification information and the guest passcode included in the received guest check-in application is stored in the first memory, Based on the determination in the first matching process that the above combination is stored in the first memory, a guest check-in information registration process is performed to store the guest check-in information in the first memory in association with the above user identification information. Based on the determination in the first matching process that the combination of the store identification information and the guest passcode is stored in the first memory, a third unlock instruction transmission process is performed, which transmits an unlock instruction to the store terminal via the first communication interface. The above third controller is, An unlock instruction reception process that receives the above unlock instruction through the third communication interface, A service provision system that performs a lock release command transmission process, which, based on the receipt of the above-mentioned lock release instruction, transmits a lock release command to the door lock device via the above-mentioned third communication interface.

2. The second controller described above is: Further, an issuance request transmission process is performed to send a guest passcode issuance request containing the above user identification information to the management server via the second communication interface. The first controller described above is The service provision system according to claim 1, which executes the guest passcode issuance process based on the receipt of the above guest passcode issuance request through the above first communication interface.

3. The first controller described above is The service provision system according to claim 1, which executes the third lock release instruction transmission process based on the fact that it has received the above check-in request and has not received the above check-out request.

4. The first controller described above is A service provision system according to claim 1, which determines user usage fees and guest usage fees based on the above check-in information, above check-out information, and above guest check-in information, and performs payment processing for the user indicated by the user identification information associated with the guest check-in information stored in the first memory.

5. The first controller described above is Further, a fee notification process is performed to transmit the above user usage fee and the above guest usage fee to the terminal device via the above first communication interface. The second controller described above is: The service provision system according to claim 4, further comprising a fee display process that displays the received user usage fees and guest usage fees on the display, based on the receipt of the above-mentioned user usage fees and guest usage fees through the above-mentioned second communication interface.

6. The second controller described above is: Further, a reservation request process is performed to send a reservation request including the above store identification information and the user identification information stored in the second memory to the management server via the second communication interface. The first controller described above is A reservation request reception process that receives the above reservation request through the above first communication interface, Further, the system performs a reservation registration process that associates the store identification information and user identification information included in the received reservation application with the first memory and stores them in that memory. The first controller described above is The service provision system according to claim 1, wherein the store identification information and the user identification information are stored in association in the first memory in the above reservation registration process or the above first registration process, and the third registration process and the guest passcode issuance process are executed.

7. The first controller described above is The service provision system according to claim 1, further comprising: a deletion process that deletes the guest passcode from the first memory based on the receipt of the above checkout request.

8. It further includes a first code image and a second code image installed in the store, The above first code image is an image containing the above store identification information, The above second code image is an image that includes a predetermined URL and the above store identification information. The above terminal device further includes a camera, The second controller described above is: In the above check-in application transmission process and the above check-out application transmission process, the above store identification information is obtained from the above first code image captured by the above camera. The first controller described above is The service provision system according to claim 1, further comprising: a guest entry screen data reply process that, based on the receipt of a request sent to the above-mentioned predetermined URL, a screen data request including the above-mentioned store identification information, returns guest entry screen data that accepts the input of the guest passcode.

9. It also features a third code image installed in the store, The above first code image is installed both inside and outside the rental space. The above second code image is located outside the rental space and further includes information indicating entry into the room. The above third code image is installed within the rental space and includes a designated URL, store identification information, and information indicating exit. The first controller described above is A guest exit screen data reply process that, based on the receipt of a request sent to the above-mentioned designated URL, which includes the above-mentioned store identification information and the above-mentioned exit information, returns guest exit screen data that accepts the input of the guest passcode, A guest checkout request reception process that receives a guest checkout request including the above guest passcode and the above store identification information through the above first communication interface, A second matching process that determines whether the combination of the store identification information and the guest passcode included in the received guest checkout application is stored in the first memory, Based on the determination in the second verification process described above that the data is stored in the first memory, a fourth unlock instruction transmission process transmits the unlock instruction to the store terminal via the first communication interface, The service provision system according to claim 8, further comprising: a first guest checkout information registration process, which, based on the determination in the second matching process described above that the information is stored in the first memory, stores the first guest checkout information in association with the user identification information in the first memory.

10. The first controller described above is Based on the receipt of the above checkout request, a determination process is performed to determine whether or not the above first guest checkout information is stored in the above first memory, The service provision system according to claim 9, further comprising: a second guest checkout information registration process, which, based on the determination in the above determination process that the first guest checkout information is not stored in the first memory, stores a second guest checkout information indicating that the user has left the store with the guest in the first memory in association with the user identification information.

11. The first controller described above is Based on the determination in the first matching process that the above combination is stored in the first memory, a guest entry information transmission process is further executed to transmit guest entry information indicating the guest's entry to the terminal device via the first communication interface. The second controller described above is: The service provision system according to claim 1, further comprising a guest entry information display process that displays a guest entry notification screen on the display based on the receipt of the above-mentioned guest entry information through the above-mentioned second communication interface.

12. The first controller described above is Based on the determination in the second matching process described above that the above combination is stored in the first memory, a guest exit information transmission process is further executed to transmit guest exit information indicating the guest's departure to the terminal device via the first communication interface. The second controller described above is: The service provision system according to claim 9, further comprising a guest departure information display process that displays a guest departure notification screen on the display based on the receipt of the above-mentioned guest departure information through the above-mentioned second communication interface.

13. A server program implemented in a management server having a first communication interface connected to the internet, a first memory, and a first controller, A terminal program implemented in a terminal device having a second communication interface connected to the internet, a second memory, a display, and a second controller, It comprises a door lock device installed at the entrance and exit of the store's rental space, a third communication interface connected to the internet, and a store program implemented in a store terminal having a third controller. The above terminal program, A check-in request transmission process that obtains store identification information and sends a check-in request containing the obtained store identification information and user identification information to the management server via the second communication interface, The second controller is instructed to perform a checkout request transmission process, which involves obtaining the above store identification information and sending a checkout request containing the obtained store identification information and the above user identification information to the management server via the second communication interface. The above server program, A check-in request reception process that receives the check-in request through the first communication interface described above, Based on the receipt of the above check-in request, a first registration process is performed to associate the above user identification information and check-in information and store them in the above first memory, Based on the receipt of the above check-in request, a first unlock instruction transmission process is performed to transmit an unlock instruction to the store terminal via the first communication interface, A checkout request reception process that receives the checkout request through the first communication interface described above, Based on the receipt of the above checkout request, a second registration process is performed to associate the above user identification information and checkout information and store them in the first memory, Based on the receipt of the above checkout request, a second unlock instruction transmission process is performed, which transmits an unlock instruction to the store terminal via the first communication interface. A third registration process is performed, in which, based on the determination that the above store identification information and the above user identification information are registered in the first memory, a guest passcode is generated, and the generated guest passcode is associated with the above user identification information and the above store identification information and stored in the first memory; A guest passcode issuance process that transmits notification information including the above-mentioned guest passcode to the terminal device via the above-mentioned first communication interface, Upon receiving a guest check-in request containing the above store identification information and guest passcode, the guest check-in request reception process is performed. A first matching process that determines whether the combination of the store identification information and the guest passcode included in the received guest check-in application is stored in the first memory, Based on the determination in the first matching process that the above combination is stored in the first memory, a guest check-in information registration process is performed to store the guest check-in information in the first memory in association with the above user identification information. Based on the determination made in the first matching process that the combination of the store identification information and the guest passcode is stored in the first memory, the first controller is instructed to execute a third unlock instruction transmission process, which transmits an unlock instruction to the store terminal via the first communication interface. The above store program, An unlock instruction reception process that receives the above unlock instruction through the third communication interface, A program that causes the third controller to perform a lock release command transmission process, which transmits a lock release command to the door lock device via the third communication interface, based on the receipt of the above-mentioned lock release instruction.

14. A server program implemented in a management server having a communication interface connected to the internet, server memory, and a controller, The above communication interface receives a check-in request and processes the check-in request. Based on the receipt of the above check-in request, a first registration process is performed to associate the user identification information and check-in information and store them in the server memory. Based on the receipt of the above check-in request, a first unlock instruction transmission process is performed, which transmits an unlock instruction to the store terminal via the above communication interface, The checkout request reception process receives a checkout request through the above communication interface, Based on the receipt of the above checkout request, a second registration process is performed to associate the above user identification information and checkout information and store them in the above server memory, Based on the receipt of the above checkout request, a second unlock instruction transmission process is performed, which transmits an unlock instruction to the store terminal via the above communication interface, A third registration process is performed, in which, based on the determination that the store identification information and the user identification information are registered in the server memory, a guest passcode is generated, and the generated guest passcode is associated with the user identification information and the store identification information and stored in the server memory. A guest passcode issuance process that transmits notification information, including the above guest passcode, to the terminal device owned by the user via the above communication interface, Upon receiving a guest check-in request containing the above store identification information and guest passcode, the guest check-in request reception process is performed. A matching process to determine whether the combination of the store identification information and the guest passcode included in the received guest check-in application is stored in the server memory, Based on the determination in the above matching process that the above combination is stored in the above server memory, a guest check-in information registration process is performed to store the guest check-in information in the above server memory in association with the above user identification information. A server program that causes the controller to execute a third unlock instruction transmission process, which, based on the determination in the above matching process that the combination of the above store identification information and the above guest passcode is stored in the above server memory, transmits an unlock instruction to the above store terminal via the above communication interface.

15. A terminal program implemented in a terminal device having a communication interface connected to the Internet, terminal memory, display, and controller, A check-in request transmission process that obtains store identification information and sends a check-in request containing the obtained store identification information and user identification information to the management server via the above communication interface, A checkout request transmission process that obtains the above store identification information and sends a checkout request containing the obtained store identification information and the above user identification information to the management server via the above communication interface, A terminal program that causes the controller to perform a fee display process, which displays the received user usage fees and guest usage fees on the display, based on the receipt of the user usage fees and guest usage fees through the above communication interface.

Images