Information processing device and program
The information processing device manages withdrawal from rented spaces by checking current usage status and requiring authentication, preventing unauthorized exits and enhancing security in service management.
Patent Information
- Application Number
- JP2020011764
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-01-28
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2040-01-28
AI Technical Summary
Existing systems face issues with unauthorized withdrawal from rented spaces, leading to potential problems such as users being trapped in spaces or locked out when they should not be, especially when the status of the user's presence is unclear or communication sessions are disconnected.
An information processing device that controls the withdrawal process based on the current usage status of a rented space, prohibiting withdrawal if the user is present or a communication session is active, and requiring authentication to ensure authorized exit.
Prevents unauthorized withdrawal, ensuring users are not trapped or locked out of rented spaces, thereby enhancing security and reliability in service management.
Smart Images

Figure 0007581623000001 
Figure 0007581623000002 
Figure 0007581623000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device and a program. [Background technology]
[0002] 2. Description of the Related Art Systems that provide services to registered users are known.
[0003] Patent document 1 describes a system which, upon receiving a withdrawal request from a client, including an identification code to identify the member, stores a suspension flag in the member file identified by the identification code, and, upon receiving a re-membership request, including the identification code, deletes the suspension flag stored in the member file identified by the identification code.
[0004] Patent Document 2 describes a system in which a terminal that wishes to withdraw from a network broadcasts a withdrawal signal at an assigned time within a reserved slot, thereby withdrawing from the network.
[0005] Patent document 3 describes a system in which a member server performs a service withdrawal process based on a notification that the deletion of a user's biometric information stored on an IC card or user terminal device has been completed, thereby ensuring the deletion of the biometric information and performing the service withdrawal process. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] JP 2003-67640 A [Patent Document 2] JP 2005-80234 A [Patent Document 3] JP 2007-183767 A Summary of the Invention [Problem to be solved by the invention]
[0007] An object of the present invention is to prevent problems caused by cancellation of a service for rented space with managed locking. [Means for solving the problem]
[0008] The invention according to claim 1 has a processor, and the processor controls a space that is rented out with locking management. and receiving an instruction to withdraw from the service from a terminal device operated by a user who uses the service in a space that is not unlocked when the user withdraws from the service. Control the execution of the cancellation process according to the current usage status of the service death , When information indicating the presence or absence of the user in the space is not acquired, the user is prohibited from leaving the space. It is an information processing device.
[0011] Claim 2 In the present invention, the processor prohibits a user who has reserved the service from canceling the membership when the user is using the service. 1 The present invention relates to an information processing device.
[0012] Claim 3 The invention is an information processing device according to claim 1, characterized in that the processor allows the user to cancel membership if the user is not using the service.
[0014] Claim 4 The invention is an information processing device according to claim 1, characterized in that the processor prohibits the user from canceling membership if a communication session related to use of the service is disconnected.
[0015] Claim 5 The invention relates to an information processing device as described in claim 1, characterized in that a personal account is defined as an account for individual users to use the service, and an organizational account is defined as an account for users belonging to an organization to use the service, and the processor prohibits the organization from canceling membership when a user belonging to the organization is using the service using the organizational account.
[0016] Claim 6The invention is an information processing device as described in claim 1, characterized in that the processor further prohibits the user from canceling his / her membership if an abnormality occurs in at least one of the space and the system managing reservations for use of the space.
[0017] Claim 7 The present invention is characterized in that the processor further executes a process of authenticating a user who is withdrawing from the membership when the withdrawal process is performed. 6 1 is an information processing device according to any one of claims 1 to 9.
[0018] Claim 8 The present invention is characterized in that, when the processor executes the withdrawal process for the user from the service, the processor further controls to cancel a reservation for use of another service that is used in conjunction with the service. 7 1 is an information processing device according to any one of claims 1 to 9.
[0019] Claim 9 The invention according to any one of claims 1 to 5 further comprises, when the withdrawal process is about to be performed while the service is being used, outputting in the space a guide indicating that the withdrawal process is about to be performed. 8 1 is an information processing device according to any one of claims 1 to 9.
[0020] Claim 10 The invention relates to a program that, when a computer receives an instruction to cancel a service from a terminal device operated by a user who uses a service for a rented space with locking control and which will not be unlocked when the user cancels the service, controls the execution of a cancellation process according to the current usage status of the service, and prohibits the user from canceling the space if information indicating the presence or absence of the user in the space is not obtained. Effect of the Invention
[0021] Claim 1, 10According to the present invention, it is possible to prevent malfunctions caused by withdrawal from the service of a space that is rented out under lock management. It is also possible to prevent malfunctions that may occur in a space that is not unlocked when withdrawal from the service is made. It is also possible to prevent malfunctions that may occur when a user withdraws from the service under a situation where it is unclear whether the user is present in the space.
[0023] Claim 2 to According to this invention, it is possible to prevent the occurrence of problems that may occur when using a service.
[0024] Claim 3 According to the present invention, it is possible to cancel the service without causing any malfunction.
[0026] Claim 4 According to the present invention, it is possible to prevent problems that may occur when a user cancels their membership in a service when a communication session is disconnected.
[0027] Claim 5 According to the present invention, it is possible to prevent problems that may occur when an organization withdraws from a service while the service is being used by users belonging to the organization.
[0028] Claim 6 According to the present invention, it is possible to prevent the occurrence of problems that may occur when a user cancels membership in a service when an abnormality occurs.
[0029] Claim 7 According to the present invention, the occurrence of spoofing and the like can be suppressed compared to a case where authentication is not performed.
[0030] Claim 8 According to the present invention, it is possible to cancel reservations for other services that are not expected to be used.
[0031] Claim 9According to the present invention, it is possible to notify the user that the withdrawal process is about to be performed. [Brief description of the drawings]
[0032] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a configuration of an operation management system. [Diagram 3] FIG. 1 is a block diagram showing a configuration of a reservation management system. [Figure 4] FIG. 2 is a block diagram showing a configuration of a terminal device. [Diagram 5] FIG. 13 is a flowchart showing a process for registering an individual user in the reservation management system. [Figure 6] FIG. 13 illustrates an individual user management table. [Figure 7] FIG. 13 illustrates a login screen. [Figure 8] FIG. 13 illustrates a reservation screen. [Figure 9] FIG. 13 illustrates a reservation management table. [Figure 10] FIG. 13 is a flowchart showing the payment process for a user with a personal account. [Figure 11] FIG. 13 is a flowchart showing a process for canceling an individual user from the reservation management system. [Figure 12] FIG. 13 is a flowchart showing a process for registering a corporate user in the reservation management system. [Figure 13] FIG. 13 illustrates a corporate user management table. [Figure 14] FIG. 13 illustrates a login screen. [Figure 15] FIG. 13 illustrates a service selection screen. [Figure 16] FIG. 13 is a flowchart showing the flow of payment for a corporation. [Figure 17] FIG. 13 is a flowchart showing a process for causing a corporate user to withdraw from the operation management system. [Figure 18] FIG. 13 is a diagram showing booth usage times. [Figure 19] FIG. 13 shows a withdrawal screen. [Figure 20] FIG. [Figure 21] FIG. 2 is a diagram showing the subordinate relationships of each user belonging to a corporation. [Figure 22] FIG. 13 illustrates a reservation management table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0033] An information processing system according to this embodiment will be described with reference to Fig. 1. Fig. 1 shows an example of the configuration of the information processing system according to this embodiment.
[0034] The information processing system according to this embodiment includes an operation management system 10, a reservation management system 12 which is an example of a service provision system, a service provision system other than the reservation management system 12 (e.g., service provision systems 14A and 14B), a booth control device 18 which controls a booth 16 which is an example of a place of use, an individual payment system 20, a corporate authentication system 22, a corporate payment system 24, and terminal devices (e.g., terminal devices 26A, 26B, and 26C). The number of each system and each device shown in FIG. 1 is merely an example.
[0035] Each system and each device included in the information processing system has a function of communicating with other systems and other devices. The communication may be wired communication using a cable, or wireless communication. That is, each system and each device may be physically connected to the other systems and other devices by a cable and transmit and receive information to each other, or may transmit and receive information to each other by wireless communication. For example, short-range wireless communication or Wi-Fi (registered trademark) is used as the wireless communication. Wireless communication of other standards may be used. For example, short-range wireless communication is Bluetooth (registered trademark), RFID (Radio Frequency Identifier), NFC, etc. For example, each system and each device communicates with the other systems and other devices via a communication path N such as a LAN (Local Area Network) or the Internet.
[0036] In the information processing system according to the present embodiment, a service is provided to a user by a service providing system. The services provided by the service providing system include, for example, a service for providing a booth 16 to a user, a service for providing a place other than the booth 16 (for example, a conference room, a shared room, a shared office, or other rooms, etc.) to a user, a service for providing a printer, a service for providing a virtual desktop infrastructure (VDI), a service for providing a TV conference, a Web service, or other services. The Web service is, for example, a service for providing an application on a network such as the Internet, or other services. For example, Web learning (for example, learning English conversation), WBT (web-based training), Web mail, SNS (social networking service), a service for providing videos and music on the Internet, a service for selling and reserving products on the Internet, a search service on the Internet, a service for providing information on the Internet, etc., correspond to examples of the Web service. Of course, services other than these may be provided by the service providing system.
[0037] For example, when a user account is created and the user is registered in the information processing system, the user can use services that the user is permitted to use.
[0038] A user account may be, for example, a personal account that is an account for an individual user to use a service, or an organizational account that is an account for a user belonging to an organization (for example, a corporation such as a company or other organization) to use a service. In the following, as an example, the organization is a corporation (for example, a for-profit corporation or a non-profit corporation), and the organizational account is a corporation account.
[0039] Hereinafter, a user who uses the service using a personal account will be referred to as a "personal user," and a user who uses the service using a corporate account will be referred to as a "corporate user."
[0040] An individual user can use a personal account to use a service that is permitted to be used using the personal account. For example, an individual user is registered for each service, and can use the service for which the individual user is registered. A corporate user can use a corporate account to use a service that is permitted to be used using the corporate account. When a contract for the use of one or more services is concluded between a corporation and an operating company or the like that provides the operation management system 10, a corporate user belonging to the corporation can use one or more services that are permitted to be used by the contract, by using the corporate account.
[0041] A user may have both a personal account and a corporate account. For example, when a user is registered as a personal user, the user is assigned a personal account. Also, if the user belongs to a corporation, a corporate account may be issued and assigned to the user. In this case, the user has both a personal account and a corporate account. The user may use the service using the personal account or the corporate account.
[0042] The services provided by the service providing system are basically paid services, and when a service is used by a user, the payment system performs payment for the use of the service. In other words, when a service is used, a fee for the service is charged, and the payment system performs billing processing (e.g., payment processing). Of course, free services may also be provided.
[0043] The operation management system 10 is configured to manage the operation of the information processing system according to this embodiment. For example, the operation management system 10 supports the provision of services by the reservation management system 12 and the service providing systems 14A and 14B, and controls processing related to payments. For example, the operation management system 10 is operated by an operating company or the like that provides the information processing system according to this embodiment.
[0044] The reservation management system 12 is configured to manage reservations of booths 16. For example, when a booth 16 is reserved by a user, the user who made the reservation is permitted to use the reserved booth 16. For example, when a booth 16 is reserved by a user specifying a usage time during which the booth 16 can be used, the user is permitted to use the reserved booth 16 during the usage time. The usage time is determined by, for example, a date and a time period. The reservation management system 12 may also manage reservations of spaces or locations other than the booths 16.
[0045] The service providing systems 14A and 14B are configured to provide services other than the services provided by the reservation management system 12. The service providing systems 14A and 14B may provide different services or the same services. In the example shown in Fig. 1, the service providing systems 14A and 14B are included in the information processing system as service providing systems other than the reservation management system 12, but one or more service providing systems may be included in the information processing system as systems other than the reservation management system 12, or service providing systems other than the reservation management system 12 may not be included in the information processing system.
[0046] The booth 16 is an example of a space or place rented out to a user. For example, a partitioned space, a private room, a seat, or a section, etc. are examples of the booth 16. The booth 16 is rented out to a user with its locking managed. For example, the booth 16 has a door that can be locked by an electronic lock. Reservations for renting the booth 16 are managed by the reservation management system 12. Although one booth 16 is shown in FIG. 1, multiple booths 16 may be installed and reservations for the multiple booths 16 may be managed by the reservation management system 12.
[0047] Booth 16 may be equipped with lighting, a power source, an air conditioner, and other devices (such as a multifunction machine having a printing function, a scanning function, a copying function, etc.).
[0048] Various sensors may be provided in the booth 16. For example, a human presence sensor that detects the presence or absence of a person in the booth 16, a temperature sensor that detects the temperature in the booth 16, a humidity sensor that detects the humidity in the booth 16, an odor sensor that detects the odor in the booth 16, an air pressure sensor that detects the air pressure in the booth 16, a camera that photographs the inside of the booth 16, a microphone that collects sounds in the booth 16, etc. may be provided in the booth 16.
[0049] The booth control device 18 controls an electronic lock provided in the booth 16 and controls each device installed in the booth 16. For example, the booth control device 18 includes a communication device, a UI, a memory, and a processor. For example, the electronic lock and each device in the booth 16 are controlled by the processor of the booth control device 18. The booth control device 18 may control one booth 16 or multiple booths 16. Furthermore, multiple booth control devices 18 may be included in an information processing system, and each booth control device 18 may control one or multiple booths 16.
[0050] The individual payment system 20 is configured to perform payment for an individual user when the service is used by the individual user using a personal account. That is, the individual payment system 20 processes the charging of the usage fee to the individual user. The individual payment system 20 may use a known payment system. For example, an individual payment account, which is an account for performing payment for an individual user, is created, and the individual user's personal account and the individual payment account are linked and managed. When the service is used using a personal account, the individual payment system 20 performs payment using the individual payment account linked to the personal account. For example, the individual payment system 20 registers information on the user's credit card, and the individual payment system 20 performs payment using the credit card. The individual payment system 20 corresponds to an example of a first payment system.
[0051] The corporate authentication system 22 is configured to authenticate users who belong to a corporation, which is an example of an organization. For example, SPF (Sender Policy Framework) authentication is used for this authentication. For example, corporate user management information is stored in the corporate authentication system 22. For example, for each corporation, corporate identification information (e.g., a corporate ID, etc.) that is information for identifying the corporation and user information (e.g., information including user identification information, etc. that is information for identifying a user) that is information about a user who belongs to the corporation are linked, and these pieces of information are registered and managed in the corporate user management information.
[0052] The corporate payment system 24 is configured to perform payment for a corporation when a service is used by a user using a corporate account. In other words, the corporate payment system 24 processes billing for usage fees to the corporation. A publicly known payment system may be used for the corporate payment system 24. For example, usage unit price information indicating the unit price of usage of the service is created, and the usage unit price information is stored in the corporate payment system 24. The unit price of usage may be determined for each corporation. For example, the unit price of usage is determined by a contract or the like. The corporate payment system 24 performs payment for the corporation by using the usage unit price information. The corporate payment system 24 corresponds to an example of a second payment system.
[0053] The terminal devices 26A, 26B, and 26C are, for example, personal computers (hereinafter, referred to as "PCs"), tablet PCs, smartphones, or mobile phones.
[0054] For example, terminal device 26A is used by an individual user, terminal device 26B is used by a user belonging to a corporation, and terminal device 26C is used by a person who manages the users belonging to the corporation. In the following, when there is no need to distinguish between terminal devices 26A, 26B, and 26C, terminal devices 26A, 26B, and 26C will be referred to as "terminal device 26." Note that a terminal device used by a person who manages operation management system 10 may be included in the information processing system.
[0055] In the information processing system according to this embodiment, data on the usage history of a service used by a user is transmitted to a different payment system depending on the type of the user's account, and payment is made by the payment system. The usage history includes, for example, the type of service, the length of time the service was used, the time period of use, and the number of uses. The payment system makes payment based on the usage history. For example, the usage history data is transmitted to the payment system at predetermined intervals (e.g., monthly) and payment is made.
[0056] Specifically, when a user uses a service using a personal account, data on the actual usage of the service used by the user is sent to the personal payment system 20, and payment for the user is made by the personal payment system 20.
[0057] When a user belonging to a corporation uses a service using a corporate account, data on the actual usage of the service by each user belonging to the corporation is sent to the corporate payment system 24, and payment is made for the corporation by the corporate payment system 24. The corporate payment system 24 does not make payments for individual users belonging to the corporation.
[0058] The configuration of the operation management system 10 will be described in detail below with reference to Fig. 2. Fig. 2 shows an example of the configuration of the operation management system 10.
[0059] The operation management system 10 includes, for example, a communication device 28, a UI 30, a memory 32, and a processor 34. The operation management system 10 may include components other than these.
[0060] The communication device 28 is a communication interface and has a function of transmitting data to other devices and a function of receiving data transmitted from other devices. The communication device 28 may have a wireless communication function or a wired communication function. The communication device 28 may communicate with other devices by using, for example, short-range wireless communication, or may communicate with other devices via a communication path N such as a LAN or the Internet.
[0061] The UI 30 is a user interface and includes at least one of a display device and an operation device. The display device is a liquid crystal display, an EL display, etc. The operation device is a keyboard, an input key, an operation panel, etc. The UI 30 may be a UI such as a touch panel that combines a display device and an operation device.
[0062] The memory 32 is a device that configures one or more storage areas for storing data. The memory 32 is, for example, a hard disk drive, various types of memory (e.g., RAM, DRAM, ROM, etc.), other storage devices (e.g., optical disks, etc.), or a combination thereof. One or more memories 32 are included in the operation management system 10.
[0063] The processor 34 is configured to control the operation of each part of the operation management system 10. The processor 34 may include a memory.
[0064] The configuration of the reservation management system 12 will be described in detail below with reference to Fig. 3. Fig. 3 shows an example of the configuration of the reservation management system 12.
[0065] The reservation management system 12 includes, for example, a communication device 36, a UI 38, a memory 40, and a processor 42. The reservation management system 12 may include components other than these.
[0066] The communication device 36 is a communication interface and has a function of transmitting data to other devices and a function of receiving data transmitted from other devices. The communication device 36 may have a wireless communication function or a wired communication function. The communication device 36 may communicate with other devices by using, for example, short-range wireless communication, or may communicate with other devices via a communication path N such as a LAN or the Internet.
[0067] The UI 38 is a user interface and includes at least one of a display device and an operation device. The display device is a liquid crystal display, an EL display, etc. The operation device is a keyboard, an input key, an operation panel, etc. The UI 38 may be a UI such as a touch panel that combines a display device and an operation device.
[0068] The memory 40 is a device constituting one or more storage areas for storing data. The memory 40 is, for example, a hard disk drive, various types of memory (e.g., RAM, DRAM, ROM, etc.), other storage devices (e.g., optical disks, etc.), or a combination thereof. One or more memories 40 are included in the operation management system 10.
[0069] The memory 40 stores, for example, individual user management information, reservation management information, sensor information, and booth information.
[0070] The personal user management information is information for managing users registered in the reservation management system 12. For example, the accounts of users registered in the reservation management system 12 are registered in the personal user management information. Specifically, user information and the like relating to users registered in the reservation management system 12 are registered in the personal user management information. Users registered in the reservation management system 12 can use the services provided by the reservation management system 12. In other words, users registered in the reservation management system 12 can reserve booths 16 through the reservation management system 12.
[0071] The reservation management information is information for managing reservations for each booth 16. For example, booth identification information, which is information for identifying the booth 16, usage time information, which is information indicating the usage time of the booth 16 (e.g., the date and time of reservation), user information on the user who reserved the booth 16, and usage information, which is information necessary to use the booth 16 during the usage time, are registered in the reservation management information.
[0072] The sensor information is information obtained by each sensor provided in the booth 16. When an abnormality is detected by a sensor, information indicating that the abnormality has been detected may be included in the sensor information. For example, the sensor information of each booth 16 is stored in the memory 40.
[0073] The booth information is information that indicates the usage status of the booth 16. For example, for each booth 16, whether or not the booth 16 is in use is managed, and this information is included in the booth information.
[0074] At least one of the individual user management information, the reservation management information, the sensor information, and the booth information may be stored in the memory 32 of the operation management system 10. In this case, the information stored in the operation management system 10 does not need to be stored in the reservation management system 12.
[0075] The processor 42 is configured to control the operation of each part of the reservation management system 12. The processor 42 may include a memory.
[0076] For example, the processor 42 is configured to manage reservations of the booth 16. For example, the processor 42 receives a request to reserve the booth 16 from the terminal device 26, and registers the reservation of the booth 16 in the reservation management information. The processor 42 permits the user who has reserved the booth 16 to use the booth 16. When a usage time is reserved, the processor 42 permits use during the usage time.
[0077] The processor 42 is also configured to transmit usage record data of a service provided by the reservation management system 12 and used by the user (e.g., data on usage record of the booth 16) to a different payment system depending on the type of account of the user. For example, when a service provided by the reservation management system 12 (e.g., the booth 16) is used using a personal account, the processor 42 transmits usage record data to the personal payment system 20, and when a service provided by the reservation management system 12 (e.g., the booth 16) is used using a corporate account, the processor 42 transmits usage record data to the corporate payment system 24. As a result, when a service is used using a personal account, payment is made by the personal payment system 20, and when a service is used using a corporate account, payment is made by the corporate payment system 24.
[0078] The processor 42 may also be configured to perform operations such as creating an account for using the services provided by the reservation management system 12, registering a user, and authenticating the user.
[0079] The processes executed by the processor 42 of the reservation management system 12 may be executed by the processor 34 of the operation management system 10. For example, when a service is used using a corporate account, the processor 34 of the operation management system 10 may transmit data on the actual usage to the corporate payment system 24. Other processes may also be executed by the processor 34 of the operation management system 10 in a similar manner.
[0080] Like the reservation management system 12, the service providing systems 14A and 14B each include a communication device, a UI, a memory, and a processor.
[0081] The memory of the service providing system 14A stores personal user management information, which is information for managing users registered in the service providing system 14A. For example, the accounts of users registered in the service providing system 14A are registered in the personal user management information. Users registered in the service providing system 14A can use the services provided by the service providing system 14A. The same applies to the service providing system 14B.
[0082] Furthermore, when the service provided by the service providing system 14A is a service that can be reserved, reservation management information for managing reservations for the service provided by the service providing system 14A is stored in the memory of the service providing system 14A.
[0083] The processor of the service providing system 14A is configured to transmit data on the usage history of a service provided by the service providing system 14A and used by a user to a different payment system depending on the type of the user's account. For example, when a service provided by the service providing system 14A is used using a personal account, the processor 42 of the service providing system 14A transmits data on the usage history to the personal payment system 20, and when a service provided by the service providing system 14A is used using a corporate account, the processor 42 transmits data on the usage history to the corporate payment system 24. As a result, when a service is used using a personal account, payment is made by the personal payment system 20, and when a service is used using a corporate account, payment is made by the corporate payment system 24. The same applies to the service providing system 14B.
[0084] The processor of the service providing system 14A may be configured to create an account for using the service provided by the service providing system 14A, register a user, authenticate the user, etc. The same applies to the service providing system 14B.
[0085] The processes executed by the processors of the service providing systems 14A and 14B may be executed by the processor 34 of the operation management system 10.
[0086] The configuration of the terminal device 26 will be described in detail below with reference to Fig. 4. Fig. 4 shows an example of the configuration of the terminal device 26.
[0087] The terminal device 26 includes, for example, a communication device 44 , a UI 46 , a memory 48 , and a processor 50 .
[0088] The communication device 44 is a communication interface and has a function of transmitting data to other devices and a function of receiving data transmitted from other devices. The communication device 44 may have a wireless communication function or a wired communication function. The communication device 44 may communicate with other devices by using, for example, short-range wireless communication, or may communicate with other devices via a communication path N such as a LAN or the Internet.
[0089] The UI 46 is a user interface and includes at least one of a display device and an operation device. The display device is a liquid crystal display, an EL display, etc. The operation device is a keyboard, an input key, an operation panel, etc. The UI 46 may be a UI such as a touch panel that combines a display device and an operation device.
[0090] The memory 48 is a device constituting one or more storage areas for storing data. The memory 48 is, for example, a hard disk drive, various types of memory (e.g., RAM, DRAM, ROM, etc.), other storage devices (e.g., optical disks, etc.), or a combination thereof. One or more memories 48 are included in the terminal device 26.
[0091] The processor 50 is configured to control the operation of each part of the terminal device 26. The processor 50 may include a memory.
[0092] The following describes a case where a user uses the services provided by the reservation management system 12. That is, the case where a booth 16 is reserved, the reservation is managed by the reservation management system 12, and the reserved booth 16 is used will be described.
[0093] In the information processing system according to this embodiment, an account for using a service (for example, the booth 16) is created by a process that differs depending on the type of user.
[0094] For example, when an individual user's means of payment is registered in the individual payment system 20, the processor 42 of the reservation management system 12 creates a personal account for the individual user to use the booth 16. In addition, when a user belonging to a corporation receives a notification of user registration and the information of the notified user is registered, the processor 42 creates a corporate account for the notified user to use the booth 16. These processes may be executed by the processor 34 of the operation management system 10. These processes will be described in detail below.
[0095] The process of registering an individual user in the reservation management system 12 will be described with reference to Fig. 5. A flowchart showing the process is shown in Fig. 5. The scene of registering an individual user in the reservation management system 12 corresponds to an example of the scene of concluding a contract for the individual user to use a service provided by the reservation management system 12.
[0096] First, the processor 42 of the reservation management system 12 receives a request for registration of an individual user and registers the individual user in the reservation management system 12 (S01). For example, when a user accesses the reservation management system 12 using the terminal device 26A and requests the reservation management system 12 to register an individual user, a screen for registering the user as an individual user in the reservation management system 12 is displayed on the UI 46 of the terminal device 26A. When the user inputs information such as the user's name, email address, and password on the screen using the terminal device 26A, the information is transmitted from the terminal device 26A to the reservation management system 12. The processor 42 of the reservation management system 12 registers the information in the individual user management information, creates an individual account, and issues the individual account to the user. For example, the processor 42 creates a user ID linked to the individual account, registers the user ID in the individual user management information, and transmits the user ID to the terminal device 26A. As a result, the user ID is notified to the user. The user ID may be determined by the user, input to the reservation management system 12, and registered in the personal user management information. The user ID and password associated with the personal account are used by the user to log in to the reservation management system 12 using the personal account.
[0097] At the stage where a payment method has not been registered, the user can log in to the reservation management system 12 using a personal account, but cannot reserve a booth 16. In other words, the processor 42 of the reservation management system 12 does not permit the user to reserve a booth 16.
[0098] Next, the processor 42 of the reservation management system 12 registers the payment method for the use of the booth 16 in the reservation management system 12 and the individual payment system 20 (S02). For example, when a user is registered in the reservation management system 12 and a personal account is created, a screen for registering the payment method and a menu for displaying the screen are displayed on the UI 46 of the terminal device 26A. The user inputs information about the payment method on the screen using the terminal device 26A. For example, when a credit card is used as the payment method, the user inputs information about the credit card (for example, the name, number, expiration date, and security code of the credit card owner). The information about the credit card corresponds to an example of information about the payment method. The information about the credit card is transmitted from the terminal device 26A to the reservation management system 12. The processor 42 of the reservation management system 12 links the information about the credit card to the personal account and registers it in the personal user management information. The information about the credit card is also transmitted to the individual payment system 20 and registered in the individual payment system 20.
[0099] When the information regarding the credit card is registered in the personal payment system 20, a personal payment account is created by the personal payment system 20 (S03).
[0100] Information regarding the personal payment account is transmitted from the personal payment system 20 to the reservation management system 12. The processor 42 of the reservation management system 12 links the personal account and the personal payment account and registers them in the personal user management information.
[0101] Once the credit card information is registered in the individual payment system 20, the individual user can reserve the booth 16. In other words, the processor 42 of the reservation management system 12 permits the individual user to reserve the booth 16.
[0102] The name, email address, password, and credit card information of the individual user may be stored in the operation management system 10 and managed by the operation management system 10.
[0103] Here, the personal user management information will be described in detail with reference to Fig. 6. Fig. 6 shows an example of a personal user management table, which is an example of the personal user management information. The data of the personal user management table is stored in the memory 40 of the reservation management system 12.
[0104] In the personal user management table, for example, each user is linked to a user ID, information indicating the type of user, information indicating the user's name, information indicating the user's email address, a password, information indicating the payment method, and a personal payment account.
[0105] There are two types of users: individual users and corporate users. A user who has been registered according to the steps described with reference to Fig. 5 is registered as an individual user in the individual user management table.
[0106] As described above, individual users are requested to input information regarding a credit card, which is an example of a payment method, and the inputted credit card information is registered in the individual user management table as information indicating the payment method.
[0107] Further, for each individual user, a personal payment account for making payments in the personal payment system 20 is created and registered in the personal user management table.
[0108] As described below, users registered as corporate users are not required to input information regarding a credit card, which is an example of a payment method, and information regarding a credit card is not registered in the personal user management table for users registered as corporate users. In addition, personal payment accounts are not created and personal payment accounts are not linked to corporate users.
[0109] For example, the accounts of user ID "0001" and user ID "0003" are personal accounts, and user A1 with user ID "0001" and user A2 with user ID "0003" are registered as personal users in the personal user management table. For example, when user A1 is registered in the reservation management system 12 according to the steps described with reference to FIG. 5, a personal account is created for user ID "0001", and a personal payment account is also created, and these are registered in the personal user management table as information linked to user ID "0001". The same is true for user A2 with user ID "0003".
[0110] As will be described later, the accounts of individual users belonging to a corporation are also registered in the individual user management table as corporate accounts. For example, user A1 is also registered in the individual user management table as a user belonging to corporation α. The account with user ID "0002" is a corporate account linked to user A1. The creation and registration of corporate accounts will be described in detail later. Note that the email address registered in the individual account and corporate account of the same user may be the same, or registration of the same email address may not be permitted.
[0111] As for the service providing systems 14A and 14B, individual user management tables are created and stored in the service providing systems 14A and 14B, respectively.
[0112] The data of the individual user management table may be stored in the memory 32 of the operation management system 10, and each piece of information registered in the individual user management table may be managed by the operation management system 10.
[0113] As described above, once a personal account and a personal payment account for an individual user have been created and registered in the individual user management table, the individual user can reserve a booth 16.
[0114] For example, when an individual user accesses the reservation management system 12 using the terminal device 26A, a login screen 52 is displayed on the UI 46 of the terminal device 26A as shown in Fig. 7. The login screen 52 displays fields for inputting information (e.g., a user ID and a password) for logging in to the reservation management system 12 using a personal account. When the user inputs a user ID and a password on the login screen 52, the input user ID and password are transmitted from the terminal device 26A to the reservation management system 12. If the input user ID and password are registered in the individual user management table, the processor 42 of the reservation management system 12 permits the user to log in. If the input user ID and password are not registered in the individual user management table, the processor 42 of the reservation management system 12 does not permit the user to log in.
[0115] When login to the reservation management system 12 is permitted, a reservation screen 54 is displayed on the UI 46 of the terminal device 26A as shown in FIG. 8. The reservation screen 54 is a screen for reserving the use of a booth 16. On the reservation screen 54, it is possible to search for the location where the booth 16 is installed, the booth 16 that can be reserved, and the time of use that can be reserved. A list of the booths 16 that can be reserved and a list of the time of use that can be reserved may be displayed. When the user instructs a reservation by specifying the booth 16 and the time of use on the reservation screen 54, information indicating the specified booth 16 and the time of use is transmitted from the terminal device 26A to the reservation management system 12. The processor 42 of the reservation management system 12 registers the booth 16 and the time of use specified by the user in the reservation management information. This completes the reservation of the booth 16.
[0116] Further, the processor 42 of the reservation management system 12 creates usage information, which is information necessary to use the booth 16 at the usage time, links the usage information to the reserved booth 16 and the usage time, registers the usage information in the reservation management information, and transmits the usage information to the terminal device 26A used for the reservation. The usage information may be displayed on the UI 46 of the terminal device 26A, or may be stored in the memory 48 of the terminal device 26A. The usage information is information including, for example, passwords and key information. For example, the processor 42 of the reservation management system 12 creates different usage information for each reservation. A user using the terminal device 26A can use the booth 16 by using the usage information. For example, when the booth 16 is locked, the usage information is used to unlock the booth 16. Furthermore, the usage information may be used to indicate that the booth 16 is being used legitimately. For example, when the booth 16 is a seat, a vehicle, or the like, the usage information may be used to indicate that the seat, the vehicle, or the like is being used legitimately. It should be noted that if the booth 16 is an open space or location, or if no operations are required to use the booth 16, the usage information does not need to be used.
[0117] The reservation management information will be described in detail below with reference to Fig. 9. An example of a reservation management table, which is an example of the reservation management information, is shown in Fig. 9. The data of the reservation management table is stored in the memory 40 of the reservation management system 12.
[0118] In the reservation management table, for example, for each reservation of a booth 16, a reservation ID, a booth ID, information indicating the usage time, information regarding the user, and usage information are linked together.
[0119] The booth ID is an example of information for identifying the reserved booth 16. The booth ID is predetermined for each booth 16 and associated with the booth 16 in advance.
[0120] The usage time is the time during which the reserved booth 16 is used. For example, the usage time is specified when the user reserves the booth 16.
[0121] The information about the user includes user identification information for identifying the user who reserved the booth 16, and terminal identification information for identifying the terminal device 26 used by the user. The user identification information includes, for example, information indicating the user's name, a user ID, information indicating the type of account the user has, and an email address. The terminal identification information is, for example, address information (e.g., an IP address or a MAC address) and a serial number of the terminal device 26. For example, when a user reserves a booth 16, information about the user is transmitted from the terminal device 26 used for the reservation to the reservation management system 12 and registered in the reservation management table.
[0122] The reservation management table will be described with a specific example. A booth 16 having a booth ID "B1" has been reserved by user A1, who is an individual user having a personal account with user ID "0001". The usage time is from 10:00 to 11:00 on January 6th. Furthermore, usage information C1 is defined as information for using the booth 16 from 10:00 to 11:00 on January 6th. This usage information C1 is transmitted from the reservation management system 12 to the terminal device 26 used for the reservation.
[0123] User A1 is also registered as a user belonging to a corporation, and user A1, who has a corporation account with user ID "0002", has reserved booth 16 with booth ID "B2". The usage time is from 10:00 to 11:00 on January 7th. Furthermore, usage information C2 is defined as information for using the booth 16 from 10:00 to 11:00 on January 7th. This usage information C2 is transmitted from the reservation management system 12 to the terminal device 26 used for the reservation.
[0124] The following describes the process when a user uses the booth 16. Here, it is assumed that the booth 16 having the booth ID "B1" is used by a user A1 who has a personal account. For ease of explanation, the booth 16 having the booth ID "B1" will be referred to as "booth B1" below.
[0125] When the user A1 performs an operation to use the booth B1, the processor 42 of the reservation management system 12 performs an authentication process to confirm whether the user A1 is permitted to use the booth B1.
[0126] For example, the door of the booth B1 is locked by an electronic lock. The door is provided with a wireless communication device that performs short-distance wireless communication. When the user A1 brings the terminal device 26A close to the door, the terminal device 26A transmits the usage information to the wireless communication device using short-distance wireless communication. As described above, when the user A1 reserves the booth B1, the usage information is transmitted from the reservation management system 12 to the terminal device 26A and stored in the memory 48 of the terminal device 26A. The wireless communication device that receives the usage information from the terminal device 26A transmits the usage information and the booth ID of the booth B1 to the reservation management system 12 via the booth control device 18 or without the booth control device 18. The processor 42 of the reservation management system 12 refers to the reservation management table shown in FIG. 9 and checks whether the transmitted usage information (e.g., usage information C1) linked to the transmitted booth ID and the usage time including the current date and time matches the transmitted usage information.
[0127] If the transmitted usage information matches the usage information C1, the processor 42 of the reservation management system 12 permits the user A1, who has a personal account, to use the booth B1. In this case, the processor 42 of the reservation management system 12 transmits information indicating an instruction to unlock the door to a wireless communication device provided on the door of the booth B1, either via the booth control device 18 or without the booth control device 18. In accordance with the unlocking instruction, the electronic lock is unlocked. When the electronic lock is unlocked, the user A1 can open the door and enter the booth B1. The processor 42 of the reservation management system 12 also transmits information indicating a usage time, which is a time during which the booth B1 can be used, to the booth control device 18 using the usage information C1. The information indicating the usage time is stored in the memory of the booth control device 18.
[0128] If the transmitted usage information does not match the usage information C1, the processor 42 of the reservation management system 12 does not permit the user A1 to use the booth B1. In this case, the processor 42 of the reservation management system 12 does not transmit information indicating an unlocking instruction. As a result, the electronic lock on the door of the booth B1 is not unlocked.
[0129] For example, if the current date and time is between 10:00 and 11:00 on January 6th and the usage information transmitted to the reservation management system 12 matches the usage information C1, the processor 42 of the reservation management system 12 permits the user A1 to use the booth B1. If the current date and time is between 10:00 and 11:00 on January 6th and the transmitted usage information does not match the usage information C1, the processor 42 of the reservation management system 12 does not permit the user A1 to use the booth B1. Also, even if the transmitted usage information matches the usage information C1, if the current date and time is other than between 10:00 and 11:00 on January 6th, the processor 42 of the reservation management system 12 does not permit the user A1 to use the booth B1.
[0130] The user ID, booth ID, and usage information may be transmitted from the terminal device 26A to the reservation management system 12. In this case, the processor 42 of the reservation management system 12 checks whether the transmitted combination of the user ID and usage information matches the combination of the user ID and usage information C1 linked to the usage information C1. If these combinations match, the processor 42 permits the user A1 to use the booth B1, and if these combinations do not match, the processor 42 does not permit the user A1 to use the booth B1.
[0131] For example, when the end time of the usage time (e.g., 11:00) has passed, the booth control device 18 transmits information indicating that the usage time has passed to the terminal device 26A used by the user A1. The information indicating that the usage time has passed is displayed on the UI 46 of the terminal device 26A. Alternatively, the information indicating that the usage time has passed may be displayed on a display device installed in the booth B1.
[0132] When the end time of the usage time (for example, 11:00) has passed and the user A1 has left the booth B1, the electronic lock on the door of the booth B1 is locked. After the end time has passed, the user A1 cannot unlock the electronic lock using the usage information C1.
[0133] When a booth 16 is used using a personal account, the usage fee for the booth 16 is charged to the user who has the personal account. In the above example, the usage fee for booth B1 is charged to user A1 who has user ID "0001". Payment for users who have personal accounts is made by the personal payment system 20.
[0134] Hereinafter, a detailed description will be given of payment for a user with a personal account with reference to Fig. 10. Fig. 10 shows a flowchart illustrating the flow of payment for a user with a personal account.
[0135] The processor 42 of the reservation management system 12 refers to the reservation management table and creates usage history data, which is data showing the usage history of the booth 16, for each user with a personal account (S10). To explain this by giving a specific example, the processor 42 of the reservation management system 12 creates usage history data showing the usage history of user A1, who is an individual user. The same applies to other individual users.
[0136] For example, the processor 42 of the reservation management system 12 creates usage history data for each month. The usage history data includes billing data. The billing data is created based on the usage fee of the booth 16. The usage fee may be determined for each booth 16, for example, depending on the length of usage time, or depending on the usage status of the equipment installed in the booth 16. Even if the booth 16 is not actually used at the reserved usage time, if the reservation for the use of the booth 16 is not canceled, the user who made the reservation is charged. Note that refund processing or discount processing may be performed, and billing data reflecting these processing may be created. For example, the operator of the operation management system 10 may perform refund processing in response to complaints from users, or perform discount processing based on a campaign or the like.
[0137] Next, the processor 42 of the reservation management system 12 transmits the usage history data of each individual user to the individual payment system 20 (S11). Note that when an administrator or the like of the operation management system 10 instructs transmission of the usage history data, the usage history data may be transmitted to the individual payment system 20. In addition, the usage history may be displayed on the UI 46 of the terminal device 26 used by the administrator or the like of the operation management system 10.
[0138] Next, the individual payment system 20 performs payment for each individual user based on the usage history data (S12). For example, the individual payment system 20 performs payment using a registered credit card.
[0139] When the payment is completed, the individual payment system 20 transmits data on the result of the payment to the reservation management system 12. The processor 42 of the reservation management system 12 receives the result of the payment and updates the status of the usage record of each individual user (S13). For example, the processor 42 associates information indicating that the payment has been completed with the user who has completed the payment in the individual user management table.
[0140] When payment is made by the individual payment system 20, a deposit process may be performed from the individual payment system 20 to the administrator of the operation management system 10, etc.
[0141] As described above, when a user uses a personal account to use the booth 16, payment is made through the personal payment system 20.
[0142] Similarly, when a user uses a service provided by the service providing systems 14A and 14B, payment is made by the individual payment system 20. That is, the processor of the service providing system 14A transmits usage history data of each individual user to the individual payment system 20. This usage history data is data indicating the usage history of the service provided by the service providing system 14A. The same is true for the service providing system 14B. The individual payment system 20 makes payments individually for each service used by an individual user. That is, payment for the use of the booth 16 provided by the reservation management system 12, payment for the use of the service provided by the service providing system 14A, and payment for the use of the service provided by the service providing system 14B are each made separately.
[0143] The process of withdrawing an individual user from the reservation management system 12 will be described below with reference to Fig. 11. A flowchart showing the process is shown in Fig. 11. The situation in which an individual user is withdrawn from the reservation management system 12 corresponds to an example of a situation in which a contract under which the individual user uses a service provided by the reservation management system 12 is terminated.
[0144] First, a user accesses the reservation management system 12 using the terminal device 26A and logs in to the reservation management system 12 using the user's personal account. When the user logs in to the reservation management system 12 using the personal account, a menu screen including a withdrawal menu is displayed on the UI 46 of the terminal device 26A. When the user logs in to the reservation management system 12 using a corporate account, the menu screen does not include the withdrawal menu. In other words, only when the user logs in to the reservation management system 12 using a personal account, the menu screen includes the withdrawal menu and the withdrawal menu is displayed (S20).
[0145] When the user issues an instruction to withdraw from the reservation management system 12 using the terminal device 26A (S21), information indicating the instruction is transmitted from the terminal device 26 to the reservation management system 12.
[0146] When the processor 42 of the reservation management system 12 receives the instruction to withdraw, it cancels all reservations of booths 16 linked to the withdrawing user (S22). For example, if user A logs into the reservation management system 12 using a personal account user ID "0001" and issues an instruction to withdraw from the reservation management system 12, the processor 42 of the reservation management system 12 cancels all reservations linked to the user ID "0001" and registered in the reservation management table. At this stage, the processor 42 of the reservation management system 12 does not delete the personal account of user ID "0001" from the personal user management table.
[0147] Next, the processor 42 of the reservation management system 12 deletes from the personal user management table the personal accounts and personal payment accounts of users who have issued an instruction to withdraw from the personal user management table for which a predetermined time or more has passed since the instruction was issued (S23). For example, when making a payment (e.g., monthly, etc.), the processor 42 checks users who have issued an instruction to withdraw from the personal user management table for which a predetermined time or more (e.g., two months) has passed since the instruction was issued, and deletes the personal accounts and personal payment accounts of those users from the personal user management table. The processor 42 also sends an instruction to the personal payment system 20 to delete the personal payment accounts. The personal payment system 20 deletes the personal payment accounts registered in the personal payment system 20 in accordance with the instruction.
[0148] Between the time the instruction to cancel membership is given and the time the personal account is deleted (i.e., between steps S21 and S23), the user may be re-registered as a personal user in the reservation management system 12. In this case, a new personal payment account (i.e., a personal payment account different from the already registered personal payment account) is created and registered in the reservation management system 12 and the personal payment system 20. Note that information regarding the credit card linked to the already registered personal payment account may be used as information regarding the credit card to be linked to the new personal payment account.
[0149] The process of registering a corporate user in the reservation management system 12 will be described below with reference to Fig. 12. A flowchart showing the process is shown in Fig. 12. The scene of registering a corporate user in the reservation management system 12 corresponds to an example of a scene of concluding a contract for the corporate user to use a service provided by the reservation management system 12.
[0150] First, a contract is concluded between a corporation and an operating company of the operation management system 10, contract information is created, and the contract specifies the services that each user belonging to the corporation can use (S30). For example, the contract specifies that each user belonging to corporation α can use the booth 16 provided by the reservation management system 12 and the services provided by the service providing system 14A.
[0151] Next, the operator of the operation management system 10 uses the terminal device 26C to register target users who are users who belong to the corporation α and who are authorized to use the booth 16 provided by the reservation management system 12 (i.e., users who can use the booth 16) and target users who are authorized to use the service provided by the service providing system 14A (i.e., users who can use the service) in the corporation authentication system 22 (S31). For example, an administrator screen is displayed on the UI 46 of the terminal device 26C, and the administrator registers the target users in the corporation authentication system 22 on the administrator screen. For example, the administrator specifies corporation identification information for identifying the corporation, user information related to the target users, and information for identifying the services that the target users can use. The processor 34 of the operation management system 10 registers these pieces of information in the corporation user management information of the corporation authentication system 22. The processor 42 of the reservation management system 12 may register the corporation identification information and user information related to the target users who can use the booth 16 (e.g., user identification information, email address, etc.) in the corporation user management information of the corporation authentication system 22. Similarly, the processor of the service providing system 14A may register, in the corporate user management information of the corporate authentication system 22, corporate identification information and user information related to target users who can use the services provided by the service providing system 14A.
[0152] Next, the target user is notified of the user registration information (S32). For example, the processor 34 of the operation management system 10 notifies the target user of the user registration information for the service that the target user can use by e-mail or the like. For example, the processor 34 of the operation management system 10 notifies the target user who is authorized to use the booth 16 of the user registration information for the reservation management system 12, and notifies the target user who is authorized to use the service provided by the service providing system 14A of the user registration information for the service providing system 14A. Note that the processor 42 of the reservation management system 12 may notify the target user who is authorized to use the booth 16 of the user registration information for the reservation management system 12, and the processor of the service providing system 14A may notify the target user who is authorized to use the service provided by the service providing system 14A of the user registration information for the service providing system 14A.
[0153] The target user who has received the notification of the user registration performs user registration for the services for which he / she has the right to use (S33). User registration in the reservation management system 12 will be described below.
[0154] When the target user accesses the reservation management system 12 using the terminal device 26B and requests the reservation management system 12 to register the corporate user, a screen for registering the user as a corporate user in the reservation management system 12 is displayed on the UI 46 of the terminal device 26B. When the target user inputs information such as the user's name, email address, and password on the screen using the terminal device 26B, the information is transmitted from the terminal device 26B to the reservation management system 12. The processor 42 of the reservation management system 12 registers the information in the personal user management information, creates a corporate account, and issues the corporate account to the target user. For example, the processor 42 creates a user ID linked to the corporate account, registers the user ID in the personal user management information, and transmits the user ID to the terminal device 26B. This notifies the user of the user ID. The user ID may be determined by the user, input to the reservation management system 12, and registered in the personal user management information. The user ID and password linked to the corporate account are used by the user to log in to the operation management system 10 and the reservation management system 12 using the corporate account. For example, the user ID and password are transmitted to the corporate authentication system 22 and registered in the corporate user management information. The user ID and password may also be stored in the operation management system 10.
[0155] For example, the processor 42 of the reservation management system 12 checks whether or not the user requesting the registration of a corporate user is registered in the corporate user management information as a target user who has the authority to use the services provided by the reservation management system 12. For example, the processor 42 may refer to the corporate user management information, or may inquire of the corporate authentication system 22 for the confirmation. If the user requesting the registration of a corporate user is registered in the corporate user management information as a target user who has the authority to use the services provided by the reservation management system 12, the processor 42 registers the user as a corporate user. If the user requesting the registration of a corporate user is not registered in the corporate user management information as a target user who has the authority to use the services provided by the reservation management system 12, the processor 42 does not register the user as a corporate user.
[0156] As described above, when a target user is registered in the reservation management system 12 as a corporate user and issued a corporate account, the target user can use the corporate account to log in to the operation management system 10 and the reservation management system 12 and reserve a booth 16. In other words, the processor 42 of the reservation management system 12 permits the corporate user to reserve the booth 16. The same applies to the service providing system 14A.
[0157] The name, email address, password, etc. of the corporate user may be stored in the operation management system 10 and managed by the operation management system 10.
[0158] Here, the corporate user management information will be described in detail with reference to Fig. 13. An example of a corporate user management table, which is an example of the corporate user management information, is shown in Fig. 13. The data of the corporate user management table is stored in the corporate authentication system 22.
[0159] In the corporate user management table, for example, a corporate ID, information indicating the corporate name, information indicating the name of a user belonging to the corporation, information indicating the user's email address, information indicating the services that the user can use, and information indicating whether the user has the authority to use the services are linked for each corporation. In addition, the user ID and password of each user are registered in the corporate user management table.
[0160] For example, users A1 and A2 are registered as corporate users belonging to a corporation α. The users A1 and A2 have the authority to use the booth 16 provided by the reservation management system 12 and the services provided by the service providing system 14A.
[0161] Additionally, user A1 is registered in the reservation management system 12 as a corporate user. For example, as shown in FIG. 6, user A1 is registered in the personal user management table as a corporate user and is assigned a user ID of "0002." The same is true for user A2. Note that, because the corporate user itself is not charged, the payment method and personal payment account are not linked to the corporate user.
[0162] For example, by using the user ID "0002" and the password associated therewith, user A1 can log in to the reservation management system 12 as a corporate user and reserve the use of the booth 16. The reservation method is the same as the method by which an individual user reserves the use of the booth 16. For example, as shown in FIG. 9, a booth 16 having a booth ID "B2" is reserved by user A1, who is a corporate user. By using the usage information C2, user A1 can unlock the electronic lock on the door of the booth 16 and use the booth 16 as a corporate user between 10:00 and 11:00 on January 7th.
[0163] User A1 is also registered in the personal user management table as an individual user. Therefore, user A1 may reserve the use of booth 16 using a personal account, or may reserve the use of booth 16 using a corporate account. When booth 16 is reserved and used using a personal account, user A1 is charged by personal payment system 20. When booth 16 is reserved and used using a corporate account, user A1 is not charged, but corporation α to which user A1 belongs is charged by corporate payment system 24.
[0164] For example, when a corporate user accesses the operation management system 10 using the terminal device 26B, as shown in FIG. 14, a login screen 56 is displayed on the UI 46 of the terminal device 26B. The login screen 56 displays a field for inputting information (e.g., a user ID and a password) for logging in to the operation management system 10 using a corporate account. When the user inputs a user ID and a password on the login screen 56, the input user ID and password are transmitted from the terminal device 26B to the corporate authentication system 22 via the operation management system 10 or without the operation management system 10. The corporate authentication system 22 authenticates the user who has requested the login, and permits the login to the operation management system 10 if the authentication is successful, and does not permit the login to the operation management system 10 if the authentication is not successful. For example, the corporate authentication system 22 permits the login to the operation management system 10 if the input user ID and password are registered in the corporate user management table, and does not permit the login to the operation management system 10 if the input user ID and password are not registered in the corporate user management table. The operation management system 10 may determine whether or not to permit login.
[0165] When login to the operation management system 10 is permitted, a service selection screen 58 is displayed on the UI 46 of the terminal device 26B, as shown in Fig. 15. A list of services that the logged-in user A1 has the authority to use is displayed on the service selection screen 58. For example, the processor 34 of the operation management system 10 refers to the corporate user management table to identify services that the user A has the authority to use, and displays a list of the identified services on the service selection screen 58.
[0166] When the user A1 selects a service on the service selection screen 58, a screen for reserving the use of the selected service is displayed on the UI 46 of the terminal device 26B. For example, when the booth 16 is selected, a reservation screen 54 shown in Fig. 8 is displayed on the UI 46 of the terminal device 26B. The user A1 can reserve the booth 16 on the reservation screen 54.
[0167] For example, as shown in Fig. 9, a booth 16 having a booth ID "B2" is reserved by user A1, who is a corporate user having a corporate account with user ID "0002". The usage time is from 10:00 to 11:00 on January 7th. In addition, usage information C2 is defined as information for using the booth 16 from 10:00 to 11:00 on January 7th. This usage information C2 is transmitted from the reservation management system 12 to the terminal device 26B used for the reservation.
[0168] The process when user A1, a corporate user, uses booth 16 is the same as the process when an individual user uses booth 16, but the payment method is different. When booth 16 is used using a corporate account, the usage fee for booth 16 is charged to corporation α to which user A1 who has the corporate account belongs. Payment for the corporation is made by corporate payment system 24.
[0169] Payment for a corporation will be described in detail below with reference to Fig. 16. Fig. 16 shows a flowchart showing the flow of payment for a corporation.
[0170] The processor of each service providing system creates usage history data for each corporation, which is data showing the usage history of the service it provides (S40). For example, the processor 42 of the reservation management system 12 refers to the reservation management table and creates usage history data for each corporation, which is data showing the usage history of the booth 16. To explain this using a specific example, the processor 42 of the reservation management system 12 creates usage history data showing the usage history of all users belonging to corporation α. The same applies to other corporations. The same applies to the service providing systems 14A and 14B.
[0171] For example, the processor of each service providing system creates usage history data for each month. The usage history data includes billing data. The billing data is created based on the usage fee of the service. The usage fee may be determined for each service, for example, according to the length of usage time, or according to the usage status of the equipment. Even if the service is not actually used at the reserved usage time, if the reservation for the use of the service is not canceled, the user who made the reservation is charged. Note that refund processing or discount processing may be performed, and billing data reflecting these processes may be created. For example, the operator of the operation management system 10 may perform refund processing in response to complaints from users, or perform discount processing based on a campaign or the like.
[0172] Next, for each corporation, usage history data on all services used by all users belonging to the corporation is transmitted to the corporate settlement system 24 (S41). This transmission is performed under the control of the operation management system 10. The operation management system 10 keeps track of the usage history of the services provided by each service providing system, and each service providing system transmits the usage history data of each corporation to the corporate settlement system 24 according to instructions from the operation management system 10.
[0173] Next, the corporate settlement system 24 performs settlement for each corporation based on the usage history data (S42). The corporate settlement system 24 calculates the total usage fee indicated by the usage history data of all services for each corporation, and bills the corporation for the total usage fee. For example, when a user belonging to corporation α uses the booth 16 and the service provided by the service providing system 14A, the usage history data of the booth 16 and the usage history data of the service provided by the service providing system 14A are transmitted to the corporate settlement system 24. The corporate settlement system 24 calculates the total usage fee indicated by the usage history data of the booth 16 and the usage fee indicated by the usage history data of the service provided by the service providing system 14A, and bills the corporation α for the total usage fee. In this way, settlement for all services is performed collectively for each corporation. The total usage fee may be calculated by the operation management system 10, the reservation management system 12, or another service providing system. Of course, settlement may be performed for each service.
[0174] When the payment is completed, the corporate payment system 24 transmits data on the result of the payment to the corporate authentication system 22. In response to the result of the payment, the corporate authentication system 22 updates the status of the usage record of each corporation (S43). For example, in the corporate user management table, the corporate authentication system 22 associates information indicating that the payment has been completed with the corporation that has completed the payment.
[0175] When the payment is made by the corporate payment system 24, a deposit process may be performed from the corporate payment system 24 to the administrator of the operation management system 10, etc.
[0176] As described above, when a service is used by a corporate user, the user is not charged as an individual, but the corporate settlement system 24 charges the corporation to which the corporate user belongs.
[0177] When a service is used using a personal account, payment is made by the personal payment system 20, and when a service is used using a corporate account, payment is made by the corporate payment system 24. This reduces the load on the payment system compared to when payments for individual users and for corporations are made by the same payment system (e.g., the corporate payment system 24).
[0178] Hereinafter, the process of withdrawing a corporate user from the operation management system 10 will be described with reference to Fig. 17. A flowchart showing the process is shown in Fig. 17. The scene where a corporate user is withdrawn from the operation management system 10 corresponds to an example of the scene where the usage authority of the corporate user is suspended.
[0179] First, the manager of the operation management system 10 suspends the usage authority of the target user in accordance with a contract with the corporation (S50). For example, an manager screen is displayed on the UI 46 of the terminal device 26C used by the manager. The manager issues an instruction to suspend the usage authority of the target user on the manager screen. Information indicating the instruction is transmitted from the terminal device 26C to the operation management system 10.
[0180] Next, under the control of the operation management system 10, the processor of each service providing system cancels all reservations for the service associated with the target user whose usage authority has been suspended (S51). For example, the processor 42 of the reservation management system 12 cancels all reservations for the booth 16 associated with the target user whose usage authority for the booth 16 has been suspended. For example, when the usage authority of user A having a user ID "0002" of a corporate account is suspended, all reservations associated with the user ID "0002" and registered in the reservation management table are canceled. Note that, when there are reservations that are eligible for refund, information indicating that may be sent by e-mail or the like to the person in charge of the corporation or the operator of the operation management system 10. The process of step S51 may be performed during a predetermined time period (for example, at night).
[0181] A user whose usage authority has been suspended is not permitted to log in to the operation management system 10 using a corporate account, and is not permitted to reserve and use services provided by each service providing system.
[0182] In addition, the contract may be terminated in whole or in part. For example, when the contract is terminated in its entirety, the usage rights of all users belonging to the corporation are suspended. As a partial termination of the contract, the number of users registered as corporate users with usage rights may be reduced. For example, when 100 users belong to the same corporation and are registered as corporate users with usage rights, the number of corporate users with usage rights may be reduced. For example, it may be reduced to 50 people, etc.
[0183] Various embodiments are described below.
[0184] In the above-described embodiment, the payment for the individual user is made by the registered payment means (e.g., a credit card), but the payment may be made by a payment means different from the registered payment means. For example, the payment may be made by using an IC card for payment, a two-dimensional code, or the like (e.g., payment by electronic money, etc.) instead of a credit card, according to the user's instruction. For example, a button for unlocking the electronic lock without using a registered credit card is displayed on the UI 46 of the terminal device 26A of the individual user who uses the booth 16. For example, when an application for reserving the booth 16 is started on the terminal device 26A, or when the reservation management system 12 (e.g., a website) is accessed using the terminal device 26A, the button is displayed. When the user presses the button, information indicating that the payment is not made by credit card is transmitted from the terminal device 26A to the individual payment system 20 via the reservation management system 12. When the user holds the IC card for payment over a reading device provided in the booth 16, the payment is completed. Also, a two-dimensional code is displayed on a display device provided in the booth 16, and when the two-dimensional code is read by the terminal device 26A, the payment is completed. When payment is completed in this manner, information indicating this is sent to the individual payment system 20 via the reservation management system 12. The individual payment system 20 does not make any payment for a reservation for which payment has been completed. Note that when reserving a booth 16, it may be possible to set payment to be made by a payment method other than the registered payment method.
[0185] It should be noted that if payment is not completed using an IC card or two-dimensional code for payment (for example, if the remaining balance is insufficient to cover the usage fee), the electronic lock will not be unlocked. In this case, if a credit card is registered as a payment method, the processor 42 of the reservation management system 12 may notify the user of a guide to payment by credit card. For example, the processor 42 may transmit information indicating the guide to the user's terminal device 26, or may display it on a display device installed in the booth 16. If the user selects payment by credit card, payment is made by credit card.
[0186] If the electronic lock of the booth 16 is not unlocked even after a predetermined time has passed since the start time of the reserved usage time (e.g., 10:00), if payment by IC card or two-dimensional code is not completed, or if the user does not select payment by credit card, the processor 42 of the reservation management system 12 may cancel the reservation. If the reservation is canceled, another user can reserve the usage time.
[0187] The payment by the personal account and the payment by the corporate account may be switched. For example, when a corporate user uses the booth 16 using a corporate account, if the corporate user selects the payment by the personal payment system 20, the processor 42 of the reservation management system 12 transmits the usage record data of the booth 16 to the personal payment system 20. In this case, the payment for the usage is made by the personal payment system 20, and not by the corporate payment system 24. To explain in more detail, when a user reserves a booth 16 using a corporate account, unlocks the electronic lock of the booth 16, and uses the booth 16, if the user selects the payment by the personal payment system 20, the payment for the usage is made by the personal payment system 20. For example, during or after using the booth 16, a button for switching the payment by the corporate account to the payment by the personal account is displayed on the UI 46 of the user's terminal device 26. When the user presses the button to switch the payment by the corporate account to the payment by the personal account, information indicating the switching is transmitted from the terminal device 26 to the reservation management system 12. In response to the switching instruction, the processor 42 of the reservation management system 12 transmits the usage history data to the individual payment system 20. The same applies to the service providing systems 14A and 14B.
[0188] Furthermore, the processor 42 of the reservation management system 12 may allow the user to change the payment system until payment is made. For example, after payment through a corporate account is switched to payment through a personal account, the processor 42 allows the user to change the payment system until payment is made through the personal payment system 20. If payment through the personal account is switched to payment through the corporate account during that time, the processor 42 transmits usage history data to the corporate payment system 24.
[0189] The functions that can be used to reserve a service may differ between a personal account and a corporate account. For example, a corporate user is permitted to use a corporate account to reserve a service reserved by a corporation (e.g., a service reserved by a representative of a corporation) as a service to be used by the corporate user himself / herself. On the other hand, a personal account is not permitted to reserve a service reserved by the corporation as a service to be used by the corporate user himself / herself.
[0190] For example, the processor 42 of the reservation management system 12 allows a corporate user to reserve a booth 16 reserved by a corporation as a service to be used by the corporate user himself / herself by using a corporate account, whereas the processor 42 does not allow a user to reserve a booth 16 reserved by a corporation as a service to be used by the user himself / herself by using a personal account.
[0191] Here, a specific example will be described with reference to FIG. 18. FIG. 18 shows the usage time of the booth 16. For example, a certain booth 16 (for example, booth B) is reserved by the corporation α from 10:00 to 11:00 on a certain day (for example, January 10). For example, this reservation is made by a contract between the corporation α and an operating company of the operation management system 10. In this case, the processor 42 of the reservation management system 12 permits each corporate user belonging to the corporation α to reserve the use of each time period including that time period (for example, 10:00 to 11:00). In the example shown in FIG. 18, each corporate user belonging to the corporation α is permitted to reserve the use of each time period on January 10. A user can access the reservation management system 12 using a corporate account linked to the corporation α and reserve the use of each time period on January 10. In other words, the processor 42 of the reservation management system 12 permits a user who logs in to the reservation management system 12 using a corporate account linked to the corporation α to reserve the use of each time period on January 10.
[0192] On the other hand, an individual user cannot use a personal account to reserve use of each time slot on January 10. In other words, the processor 42 of the reservation management system 12 does not permit a user who logs in to the reservation management system 12 using a personal account to reserve use of each time slot on January 10.
[0193] As another example, the types of devices that can be used in the booth 16 may differ between a personal account and a corporate account. For example, a corporate user who logs in to the reservation management system 12 using a corporate account may be permitted to use high-performance air conditioners, multifunction printers, etc., compared to an individual user who logs in to the reservation management system 12 using a personal account. Also, if a locked box containing special tools, etc. is installed in the booth 16, the corporate user may be permitted to unlock the key to the box. For example, if the box is locked with an electronic lock, the electronic lock may be unlocked by the usage information linked to the corporate account.
[0194] For example, the booth 16 may be used by medical personnel or those making contracts. Medical personnel may perform treatment, draw blood, or the like in the booth 16. Tools for this purpose may be stored in the box, and a user with a medical-related corporate account may be permitted to unlock the electronic lock and open the box. Also, a seal or the like may be stored in the box and used when making a contract, etc.
[0195] If an error occurs in the system, notification of the error is controlled. For example, if an error occurs in the corporate authentication system 22 or the corporate payment system 24 when a user logs in to the reservation management system 12, no error notification is sent by email to the operator of the operation management system 10. In this case, the operator receives a call from the user and performs a refund process, etc. Also, if an error occurs in the corporate authentication system 22 or the corporate payment system 24 when payment is being made, no error notification is sent by email to the operator of the operation management system 10. In this case, processing is performed according to a predetermined operation process. For example, manual payment is performed, etc.
[0196] Furthermore, if an error occurs in the individual payment system 20 when registering a user in the reservation management system 12, the operator of the operation management system 10 is not notified of the error by email. In this case, the operator receives contact from the user and provides support for user registration. Furthermore, if an error occurs in the individual payment system 20 when payment is being made, the operator of the operation management system 10 is not notified of the error by email. In this case, processing is performed according to a predetermined operation process. For example, payment is made manually.
[0197] The process for canceling a user's membership in a service will be described in more detail below.
[0198] When a user is about to withdraw from a service, execution of the withdrawal process may be controlled according to the current usage status of the service. More specifically, when a user of a service of a space that is rented out under lock management is about to withdraw from the service, execution of the withdrawal process is controlled according to the current usage status of the service.
[0199] The space is, for example, a booth 16 that is rented out with locking control. For example, when a user wishes to withdraw from the reservation management system 12, the processor 42 of the reservation management system 12 controls the execution of withdrawal processing according to the current usage status of the booth 16. The same applies to the service providing systems 14A and 14B.
[0200] For example, a booth 16 will not be unlocked if a user withdraws from the reservation management system 12 while using the booth 16. In other words, when a user using the booth 16 withdraws from the reservation management system 12 while the booth 16 is in use, the processor 42 of the reservation management system 12 locks the electronic lock of the booth 16 so that it cannot be unlocked. Therefore, if a user withdraws from the reservation management system 12 while inside the booth 16, the user will be locked inside the booth 16. Also, if a user withdraws from the reservation management system 12 while outside the booth 16, the user will be locked out of the booth 16 and will not be able to enter the booth 16.
[0201] Therefore, when a user is using the booth 16, the processor 42 of the reservation management system 12 prohibits the user from withdrawing from the reservation management system 12. For example, the processor 42 checks whether or not a user is in the booth 16 using a human presence sensor or an entrance / exit management system, and when a user is in the booth 16, prohibits the user from withdrawing from the reservation management system 12. To explain in more detail, when a user who has reserved a booth 16 is using the booth 16, the processor 42 of the reservation management system 12 prohibits the user who has reserved the booth 16 from withdrawing from the booth 16. In other words, when the user who has reserved the booth 16 unlocks the electronic lock of the booth 16, enters the booth 16 and uses the booth 16 during the reserved usage time, the processor 42 prohibits the user from withdrawing from the booth 16.
[0202] On the other hand, if the user is not using the booth 16, the processor 42 of the reservation management system 12 permits the user to withdraw from the reservation management system 12. In other words, if it is outside the usage time reserved by the user, the processor 42 permits the user to withdraw from the reservation management system 12. As another example, if it is confirmed that the user is not inside the booth 16 during the usage time reserved by the user, the processor 42 permits the user to withdraw from the reservation management system 12. For example, if the electronic lock of the booth 16 has not been unlocked by the user, it is presumed that the user is not inside the booth 16 even during the reserved usage time, and therefore the processor 42 permits the user to withdraw from the reservation management system 12.
[0203] Furthermore, if a human presence in the booth 16 is detected by a human presence sensor or the like during a usage time when no reservation has been made, the processor 42 of the reservation management system 12 may permit the user to leave the reservation management system 12. A person who is in the booth 16 during a usage time when no reservation has been made may be a trespasser or the like who is not a user authorized to use the booth 16, so in this case the processor 42 permits the user to leave.
[0204] Here, a screen for withdrawing from the membership (hereinafter, referred to as a "withdrawal screen") will be described with reference to Fig. 19. Fig. 19 shows an example of the withdrawal screen.
[0205] For example, when a user logs in to the reservation management system 12 using a personal account with the terminal device 26A, a menu screen including a withdrawal menu is displayed on the UI 46 of the terminal device 26A. When the user selects the withdrawal menu on the menu screen, a withdrawal screen 60 is displayed on the UI 46. A notice may be displayed on the withdrawal screen 60.
[0206] If the user is permitted to withdraw, a withdrawal button 62 is displayed on the withdrawal screen 60, and the user can press the withdrawal button 62. When the user presses the withdrawal button 62, information indicating an instruction to withdraw is transmitted from the terminal device 26A to the reservation management system 12, and the reservation management system 12 performs the withdrawal process. For example, the process described with reference to FIG. 11 is executed. If the withdrawal process is successful, a message such as "The withdrawal process has been successful" may be displayed on the UI 46 of the terminal device 26A. If the withdrawal process fails, a message such as "The withdrawal process has failed" may be displayed on the UI 46 of the terminal device 26A. Note that if a cancel button is displayed on the withdrawal screen 60 and the cancel button is pressed by the user, the withdrawal screen 60 is no longer displayed.
[0207] If a user successfully cancels their membership, all reservations linked to that user's account will be canceled. The account will not be deleted until payment is complete. A deletion flag will be added to the information about that user to indicate that the user has canceled their membership.
[0208] When the withdrawal process is performed, the processor 42 of the reservation management system 12 may execute a process of authenticating the withdrawing user. For example, the processor 42 may transmit a pin code to the email address of the withdrawing user, or may authenticate the user using biometric information (e.g., fingerprint information, face image, etc.).
[0209] If the user is not permitted to cancel his / her membership, the cancellation screen 60 is not displayed even when the cancellation menu is selected, the cancellation screen 60 is displayed but the cancellation button 62 is not displayed, the cancellation button 62 is displayed but the cancellation button 62 cannot be pressed, or the processor 42 does not accept the instruction to cancel even when the cancellation button 62 is pressed. For example, the cancellation button 62 is displayed in a grayed-out state, and the cancellation button 62 cannot be pressed. By carrying out such processing, the user is unable to cancel his / her membership from the reservation management system 12.
[0210] When the withdrawal process is about to be performed while the booth 16 is in use, the processor 42 of the reservation management system 12 may output, at the booth 16, a notice indicating that the withdrawal process is about to be performed. For example, the processor 42 causes a display device installed in the booth 16 to display information indicating the notice. The processor 42 may also send the information indicating the notice to the email address of the user who is about to withdraw, or cause the information to be displayed on the UI 46 of the terminal device 26 of the user who is about to withdraw. For example, when a user who is using the booth 16 selects the withdrawal menu on the menu screen during the use, the processor 42 outputs the notice. To explain in more detail, when a user who has reserved the booth 16 unlocks the electronic lock of the booth 16 during the reserved use time, enters the booth 16, and selects the withdrawal menu while using the booth 16, the processor 42 outputs the notice. FIG. 20 shows an example of the notice. For example, a screen 64 is displayed on a display device installed in the booth 16 or on the UI 46 of the terminal device 26. For example, a message is displayed to prompt the user to confirm that there is no problem with withdrawing.
[0211] The processor 42 of the reservation management system 12 may prohibit the user from withdrawing if information indicating the presence or absence of the user in the booth 16 (hereinafter referred to as "confirmation information") is not acquired. The confirmation information is, for example, information indicating the detection result of a human presence sensor. For example, the processor 42 may not be able to acquire the confirmation information due to a communication failure or the like. In this case, the processor 42 prohibits the user from withdrawing because it cannot confirm whether the user is in the booth 16.
[0212] If a communication session related to the use of the service is disconnected, the processor 42 of the reservation management system 12 may prohibit the user from withdrawing from the service. The communication session is a communication session established within the information processing system, such as a communication session between the terminal device 26 and the reservation management system 12, or a communication session between the individual payment system 20 and another device or system. If any communication session is disconnected, there is a possibility that payment cannot be made, so the processor 42 prohibits the user from withdrawing from the service.
[0213] If an abnormality occurs in at least one of the booth 16 and the reservation management system 12, the processor 42 of the reservation management system 12 may prohibit the user from withdrawing from the booth. The abnormality may be, for example, a communication error, a system error, or a system failure. If such an abnormality occurs, it is not possible to confirm whether the user is in the booth 16, and therefore the processor 42 prohibits the user from withdrawing from the booth.
[0214] When a user belonging to a corporation uses a booth 16 using a corporation account, the processor 42 of the reservation management system 12 may prohibit the corporation from withdrawing from the reservation management system 12. This process will be described in detail below with reference to Fig. 21. Fig. 21 shows the subordinate relationships of each user belonging to the corporation.
[0215] For example, users A1, A2, and A3 belong to a corporation α. User A1 is a higher-ranking user (e.g., a superior) of users A2 and A3, and users A2 and A3 are lower-ranking users (e.g., subordinates) of user A1. Users A2 and A3 are users of the same rank. A higher-ranking corporation account is assigned to user A1, and lower-ranking corporation accounts are assigned to users A2 and A3. Each of users A1, A2, and A3 is permitted to log in to the reservation management system 12 using the corporation account assigned to them, and to reserve and use a booth 16. In addition, user A1, who has a higher-ranking corporation account, has the authority to withdraw corporation α from the reservation management system 12. In other words, user A1 has the authority to suspend the usage authority held by users A1, A2, and A3, and to withdraw users A1, A2, and A3 from the reservation management system 12. For example, user A1 is a representative of corporation α. Users A2 and A3 who have lower-level corporate accounts do not have the authority to cancel the membership of corporation α from the reservation management system 12.
[0216] For example, if at least one of users A2 and A3 who have a lower-level corporate account is using the booth 16, the processor 42 of the reservation management system 12 does not permit user A1 who has a higher-level corporate account to withdraw corporation α from the reservation management system 12. In other words, the processor 42 prohibits withdrawal of corporation α from the reservation management system 12. For example, if it is confirmed that at least one of users A2 and A3 has reserved the booth 16 and unlocked the electronic lock of the booth 16 at the reserved usage time, or if it is confirmed by a human sensor or the like that there is a person in the booth 16 during the usage time, the processor 42 prohibits withdrawal of corporation α from the reservation management system 12. Note that the unlocking of the electronic lock is confirmed by transmitting usage information to the reservation management system 12.
[0217] For example, if withdrawal from corporation α is permitted, as described with reference to Fig. 19, a withdrawal screen is displayed on the UI 46 of the terminal device 26 of user A1, and when the withdrawal button is pressed, processing for withdrawal from corporation α is performed. If withdrawal from corporation α is not permitted, the withdrawal screen is not displayed, the withdrawal screen is displayed but the withdrawal button is not displayed, the withdrawal button is displayed but the withdrawal button cannot be pressed, or even if the withdrawal button is pressed, the processor 42 does not accept the instruction to withdraw. For example, the withdrawal button is displayed grayed out, and the withdrawal button cannot be pressed.
[0218] When a user wishes to withdraw from a service, reservations for other services used in conjunction with the service may be canceled. For example, when a user withdraws from the reservation management system 12, reservations for other services reserved by the user and used in conjunction with the booth 16 reserved by the user are canceled. This process will be described in detail below with reference to FIG. 22.
[0219] An example of a reservation management table is shown in Fig. 22. In this reservation management table, a reservation ID, a booth ID, information indicating a usage time, information on a user, information indicating other services, and usage information are linked. Information other than the information indicating other services is the same as the information registered in the reservation management table shown in Fig. 9.
[0220] The information indicating the other services is a service used in conjunction with the reserved booth 16. The other services are services provided by the service providing systems 14A and 14B, and are, for example, a service used in the booth 16, a service used in the surrounding areas of the booth 16, or a service used on the route to the booth 16. For example, specific examples of the other services include a printing service using a multifunction device installed in the booth 16, in a surrounding store, or in a store on the route, a service of receiving food and drink, or a service of receiving education. Of course, services other than these may be included in the other services.
[0221] For example, when a user reserves a booth 16, the user also reserves other services. The time to use the other services is reserved, etc. The reservation of the other services is made to a service providing system that provides the other services, and the reservation is managed by the service providing system. The reservation management system 12 shares reservation information by cooperating with the service providing system, and links the other services reserved together with the booth 16 to the reservation of the booth 16, registers them in a reservation management table, and manages them. The user can use the other services during the reserved usage time.
[0222] To explain this with a specific example, a user A1 who has a personal account with ID "0001" reserves a booth 16 with a booth ID "B1" and another service "Service YYY" that is used in conjunction with the booth 16. The usage time of the other service may be the same as or different from the usage time of the booth 16.
[0223] For example, if user A1 cancels his / her membership with the reservation management system 12, the processor 42 of the reservation management system 12 cancels the reservation of the booth 16 reserved by user A1, and further cancels the reservation of the use of another service linked to the booth 16. For example, the processor 42 outputs an instruction to the service providing system that provides the other service to cancel the reservation of the use of the other service. The service providing system that receives the instruction from the processor 42 cancels the reservation of the use of the other service.
[0224] When the processor 42 of the reservation management system 12 receives an instruction to cancel membership in the reservation management system 12, the processor 42 may notify the canceling user of a guide indicating that reservations for other services are to be cancelled. For example, the processor 42 transmits information indicating the guide to the terminal device 26 of the canceling user. When the canceling user gives an instruction to cancel reservations for use of other services, the processor 42 cancels the reservations for use of other services in response to the instruction.
[0225] In each of the above embodiments, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.). Furthermore, the operation of the processor in each of the above embodiments may not only be performed by one processor, but may also be performed by multiple processors located at physically separate locations working together. Furthermore, the order of each operation of the processor is not limited to the order described in each of the above embodiments, and may be changed as appropriate. [Explanation of symbols]
[0226] 10 operation management system, 12 reservation management system, 14A, 14B service provision system, 16 booth, 20 individual payment system, 24 corporate payment system.
Claims
1. A processor is included. The processor, When an instruction to withdraw from the service is received from a terminal device operated by a user who uses a service of a space that is rented out under lock management and that will not be unlocked when the user withdraws from the service, execution of a withdrawal process is controlled according to a current usage status of the service; If information indicating the presence or absence of the user in the space is not acquired, prohibiting the user from leaving the space.
23. An information processing apparatus comprising:
2. The processor, prohibiting a user who has reserved the service from canceling the service when the user is using the service; 2. The information processing apparatus according to claim 1,
3. The processor, If the user is not using the service, permitting the user to cancel the membership; 2. The information processing apparatus according to claim 1,
4. The processor, prohibiting the user from canceling the service if the communication session related to the use of the service is disconnected; 2. The information processing apparatus according to claim 1,
5. A personal account is defined as an account for an individual user to use the service, and an organizational account is defined as an account for a user belonging to an organization to use the service, The processor, When a user belonging to the organization is using the service using the organization account, the organization prohibits the user from canceling the membership.
2. The information processing apparatus according to claim 1,
6. The processor further comprises: prohibiting the user from canceling the membership if an abnormality occurs in at least one of the space and a system that manages reservations for use of the space; 2. The information processing apparatus according to claim 1,
7. The processor further comprises: When the withdrawal process is performed, an authentication process for the withdrawing user is executed.
7. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer.
8. The processor further comprises: When the withdrawal process of the user is executed from the service, control is performed so as to cancel reservations for use of other services that are used in conjunction with the service.
8. The information processing device according to claim 1, wherein the information processing device is a computer.
9. The processor further comprises: If the withdrawal process is about to be performed while the service is being used, a guide indicating that the withdrawal process is about to be performed is output in the space.
9. The information processing device according to claim 1, wherein the information processing device is a computer.
10. On the computer, a space that is rented out under lock management and that will not be unlocked when a user withdraws from the service receives an instruction to withdraw from the service from a terminal device operated by a user who uses the service, and controls execution of a withdrawal process according to a current usage status of the service; If information indicating the presence or absence of the user in the space is not acquired, prohibiting the user from withdrawing from the space. A program characterized by:
Citation Information
Patent Citations
Automatically renting apparatus
JP1989046188A
Rental locker system
JP2002260093A
Server used for member revival and control method therefor
JP2003067640A
Rental booth as well as rental booth group management device and its method
JP2004086582A
Wireless interterminal communication method
JP2005080234A
