Information processing method, program, and information processing device

Abstract

To provide an information processing method etc. capable of charging each user an appropriate fee even if there is an error in recording the user's entry and exit. [Solution] The information processing method involves a computer executing a process to obtain the user ID and entry time of a user who unlocks a smart lock from outside the room, and the user ID and exit time of a user who unlocks the smart lock from inside the room.When multiple entry or exit times are obtained for each user ID for each date, the computer calculates the usage time, which is the time from the first entry time of the day to the last exit time of the same day, and charges each user's usage fee, calculated based on the user ID and usage time, via the user's credit card.

Description

[Technical Field]

[0001] The present invention relates to an information processing method, a program, and an information processing device. [Background technology]

[0002] A rental space management method has been proposed that manages the usage time of a rental space by sending and receiving signals between a mobile terminal owned by a user and a communication device installed in the rental space (Patent Document 1).

[0003] A management device has been proposed for use in a shared house, shared office, coworking space, or the like used by multiple users, which charges each user according to their usage record (Patent Document 2). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-021192 [Patent Document 2] Japanese Patent Application Publication No. 2017-228274 Summary of the Invention [Problem to be solved by the invention]

[0005] In the management method of Patent Document 1 and the management device of Patent Document 2, if the entry and exit of users is not accurately recorded, it is not possible to determine an appropriate fee for each user.

[0006] In one aspect, an object is to provide an information processing method etc. that can charge each user an appropriate fee even if there is an omission in the record of the user's entry and exit. [Means for solving the problem]

[0007] The information processing method is The system receives a request from a registered parent user for issuance of key information to be used by a child user for membership registration, transmits the key information issued based on the issuance request, accepts membership registration by the child user using the transmitted key information, issues a membership card that the child user can use to unlock a smart lock installed in the room, and charges the parent user a usage fee for the child user's use of the room. The processing is performed by a computer. [Effects of the Invention]

[0008] In one aspect, it is possible to provide an information processing method or the like that can determine appropriate fees for each user even if there is a omission in the record of the user's entry and exit. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram illustrating a configuration of an information processing system. [Figure 2] FIG. 1 is an explanatory diagram illustrating a configuration of an information processing system. [Figure 3] FIG. 10 is an explanatory diagram illustrating the record layout of an entry / exit DB. [Figure 4] FIG. 10 is an explanatory diagram illustrating the record layout of a valid DB. [Figure 5] FIG. 2 is an explanatory diagram illustrating the record layout of a member DB. [Figure 6] FIG. 10 is an explanatory diagram illustrating the record layout of a billing DB. [Figure 7] FIG. 10 is an explanatory diagram illustrating a calculation rule for usage time. [Figure 8] 10 is an example of a screen displaying congestion status. [Figure 9] 10 is an example of a management screen. [Figure 10] 10 is an example of a management screen. [Figure 11] 10 is a flowchart illustrating a processing flow of a program executed by an authentication server. [Figure 12] 10 is a flowchart illustrating the flow of processing of a program for determining a congestion state. [Figure 13] 10 is a flowchart illustrating the flow of processing by a program that executes processing for billing a fee. [Figure 14] 10 is a flowchart illustrating the flow of processing in a daily fee calculation subroutine. [Figure 15] 10 is a flowchart illustrating the flow of processing of a program according to the second embodiment. [Figure 16] FIG. 11 is a functional block diagram of an information processing device according to a third embodiment. [Figure 17] FIG. 10 is an explanatory diagram illustrating the configuration of an information processing device according to a fourth embodiment. [Figure 18] 10 is a map of a coworking space in accordance with the fifth embodiment. [Figure 19] FIG. 10 is an explanatory diagram illustrating the record layout of a reservation key DB. [Figure 20] FIG. 10 is an explanatory diagram illustrating the record layout of a reservation DB. [Figure 21] 13 is a flowchart illustrating the flow of program processing at the time of reservation in the fifth embodiment. [Figure 22] 13 is a flowchart illustrating the flow of processing of a program when unlocking in the fifth embodiment. [Figure 23] This is a screen according to the fifth embodiment. [Figure 24] This is a screen according to the fifth embodiment. [Figure 25] This is a map of the coworking space for variant 5-1. [Figure 26] 13 is a flowchart illustrating the flow of processing of a program according to the sixth embodiment. [Figure 27] FIG. 20 is an explanatory diagram illustrating a record layout of a member DB according to the seventh embodiment. [Figure 28] 13 is a flowchart illustrating the flow of processing of a program according to a seventh embodiment. [Figure 29] FIG. 20 is an explanatory diagram illustrating a record layout of a member DB according to the eighth embodiment. [Figure 30] 13 is a flowchart illustrating the flow of processing of a program according to the eighth embodiment. [Figure 31] 13 is a flowchart illustrating the flow of processing of a program according to a ninth embodiment. [Figure 32] 9 is a screen example of modified example 9-1. [Figure 33] 9 is a screen example of modified example 9-1. [Figure 34] FIG. 20 is an explanatory diagram illustrating a product locker according to a tenth embodiment. [Figure 35] FIG. 10 is an explanatory diagram illustrating the record layout of a product DB. [Figure 36] 20 is a flowchart illustrating the processing flow of a program according to a tenth embodiment. [Figure 37] 16 is a screen example of the tenth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] [Embodiment 1] FIG. 1 is an explanatory diagram illustrating the configuration of an information processing system 10. In this embodiment, an information processing system 10 that manages a so-called coworking space will be described as an example. The coworking space in this embodiment is an example of a room. The coworking space in this embodiment is a room suitable for desk work such as working, studying, or reading, and is equipped with desks and chairs that multiple users can sit and use. The coworking space is provided to users for a fee.

[0011] The information processing system 10 includes an information processing device 20, a mobile device 30, an authentication server 40, a gate unit 11, and a membership card 15. The membership card 15 is held by each user who uses the coworking space.

[0012] The gate unit 11 is provided in a part of the wall surrounding the coworking space. The gate unit 11 includes an entrance 12 such as a door, a key mechanism 13 that locks and unlocks the entrance 12, a first reader 141 arranged on the outside of the wall, and a second reader 142 arranged on the inside of the wall. In the following description, when it is not necessary to distinguish between the first reader 141 and the second reader 142, they may be referred to as readers 14.

[0013] The reader 14 and the key mechanism 13 are so-called IoT (Internet of Things) devices that are used while connected to a network. The key mechanism 13, the reader 14, the membership card 15, and the authentication server 40 constitute a so-called smart lock that can be locked and unlocked via a network.

[0014] The first reader 141 is an example of an entry information acquisition unit that acquires information about a user who has entered the coworking space by opening the entrance 12 from outside the coworking space. The second reader 142 is an example of an exit information acquisition unit that acquires information about a user who has opened the entrance 12 from inside the coworking space and left the coworking space.

[0015] The authentication server 40 is a server that controls the reader 14 and the key mechanism 13 via a network. The authentication server 40 includes a control unit 41, a main memory device 42, an auxiliary memory device 43, a communication unit 44, and a bus. The control unit 41 is an arithmetic and control device that executes the program of this embodiment. The control unit 41 uses one or more CPUs (Central Processing Units) or multi-core CPUs, etc. The control unit 41 is connected to each hardware unit that constitutes the authentication server 40 via the bus.

[0016] The main memory device 42 is a storage device such as an SRAM (Static Random Access Memory), a DRAM (Dynamic Random Access Memory), a flash memory, etc. The main memory device 42 temporarily stores information required during processing performed by the control unit 41 and programs currently being executed by the control unit 41.

[0017] The auxiliary storage device 43 is a storage device such as an SRAM, flash memory, hard disk, or magnetic tape. The entrance / exit DB 51, the validity DB 52, the programs to be executed by the control unit 41, and various data required for executing the programs are stored in the auxiliary storage device 43. The communication unit 44 is an interface for communication between the authentication server 40 and the network.

[0018] Reader 14 reads the membership card ID recorded on membership card 15 using, for example, NFC (Near Field Communication) and transmits it to authentication server 40. First reader 141 and second reader 142 are barcode readers and may read the membership card ID displayed as a barcode on the surface of membership card 15. The membership card ID will be described later.

[0019] The control unit 41 determines whether the membership card 15 is valid. If it is determined that the membership card 15 is valid, the control unit 41 controls the key mechanism 13 to unlock the entrance / exit 12. As a result, a user who has had their membership card 15 read by the reader 14 can pass through the entrance / exit 12.

[0020] After a predetermined time has elapsed, or after a sensor (not shown) detects the passage of a user, the control unit 41 controls the key mechanism 13 to automatically lock the entrance 12. The key mechanism 13 may also autonomously lock the entrance 12 after a predetermined time has elapsed, or after detecting the passage of a user.

[0021] 2 is an explanatory diagram illustrating the configuration of the information processing system 10. The configurations of the information processing device 20 and the mobile device 30 will be described using FIG.

[0022] The information processing device 20 includes a control unit 21, a main memory device 22, an auxiliary memory device 23, a communication unit 24, a display unit 251, an input unit 252, and a bus. The control unit 21 is an arithmetic and control device that executes the program of this embodiment. The control unit 21 uses one or more CPUs or multi-core CPUs, etc. The control unit 21 is connected to each hardware unit that constitutes the information processing device 20 via the bus.

[0023] The main memory device 22 is a memory device such as an SRAM, a DRAM, a flash memory, etc. The main memory device 22 temporarily stores information required during processing performed by the control unit 21 and programs being executed by the control unit 21.

[0024] The auxiliary storage device 23 is a storage device such as an SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 23 stores an entry / exit DB 56, a member DB 57, a billing DB 58, programs to be executed by the control unit 21, and various data required for executing the programs. The communication unit 24 is an interface for communication between the information processing device 20 and the network.

[0025] The display unit 251 is a liquid crystal display panel, an organic EL display panel, etc. The input unit 252 is a keyboard, a mouse, a microphone, etc. The display unit 251 and the input unit 252 may be stacked to form a touch panel.

[0026] The information processing device 20 is a general-purpose personal computer, smartphone, tablet, or mainframe computer used by the operator of the coworking space, or a virtual machine running on a mainframe computer. The information processing device 20 may be configured with hardware such as multiple personal computers or mainframe computers that perform distributed processing. The information processing device 20 may also be configured with a cloud computing system. The information processing device 20 may also be hardware dedicated to the editing support processing of this embodiment.

[0027] The mobile device 30 includes a control unit 31, a main memory device 32, an auxiliary memory device 33, a communication unit 24, a touch panel 35, and a bus. The control unit 31 is an arithmetic and control device that executes the program of this embodiment. The control unit 31 uses one or more CPUs or multi-core CPUs, etc. The control unit 31 is connected to each hardware unit that constitutes the mobile device 30 via the bus.

[0028] The main memory device 32 is a memory device such as an SRAM, a DRAM, a flash memory, etc. The main memory device 32 temporarily stores information required during processing performed by the control unit 31 and programs being executed by the control unit 31.

[0029] The auxiliary storage device 33 is a storage device such as an SRAM, flash memory, hard disk, or magnetic tape. The auxiliary storage device 33 stores programs to be executed by the control unit 31 and various data required for executing the programs. The communication unit 34 is an interface for communicating between the mobile device 30 and a network. The touch panel 35 has a configuration in which a display unit 351 such as a liquid crystal display panel or an organic EL display panel and an input unit 352 are stacked.

[0030] The mobile device 30 is a general-purpose smartphone, tablet, personal computer, etc. used by each user who uses the coworking space. When a user accesses the information processing system 10 from home, work, etc., the mobile device 30 may be a desktop personal computer.

[0031] 3 is an explanatory diagram illustrating the record layout of the entry / exit DB 51. The entry / exit DB 51 is a DB that records the location of the coworking space, the date and time when the reader 14 read the membership card 15, the user ID corresponding to the membership card 15, and the entry / exit status, in association with each other.

[0032] The entry / exit DB 51 has a location field, a date and time field, a user ID field, and an entry / exit field. The date and time field has a date field and a time subfield. The location field records the name of the coworking space. The date field records the date on which the reader 14 read the membership card 15. The time field records the time on which the reader 14 read the membership card 15.

[0033] The user ID field records the user ID corresponding to the read membership card 15. The entry / exit field records whether the user entered or exited. The entry / exit distinction is determined by whether the first reader 141 or the second reader 142 read the membership card 15.

[0034] Specifically, "entry" indicates that a user has entered the coworking space by having the first reader 141 read their membership card 15 from outside the coworking space, and "exit" indicates that a user has left the coworking space by having the second reader 142 read their membership card 15 from inside the coworking space. The entry / exit DB 51 has one record for each reading of the membership card 15.

[0035] In some cases, other users may enter or exit together with the user who opened the door, which is known as tailgating. It is considered good manners to hold the door open to allow subsequent users to pass through easily, so it is difficult to prevent tailgating when using a standard door. Information about users who enter or exit a room by tailgating is not recorded in the entry / exit DB 51.

[0036] That is, in the information processing system 10 of the present embodiment, there are cases where the entry and exit of a user are not accurately recorded. Specifically, for the same user ID, there are cases where entry is recorded multiple times in succession, exit is recorded multiple times in succession, exit is recorded at the beginning of the day, and entry is recorded at the end of the day.

[0037] Each record recorded in the entry / exit DB 51 is copied as needed to the entry / exit DB 56 by replication processing. Therefore, the entry / exit DB 56 has the same record layout as the entry / exit DB 51. Since the replication processing has been used for a long time, detailed explanation will be omitted.

[0038] A coworking space operator may operate the coworking space by installing an information processing device 20 in each region, for example. Multiple operators may each install an information processing device 20. In this case, during replication processing, records related to the coworking spaces to be managed are extracted and copied to the entry / exit DB 56.

[0039] 4 is an explanatory diagram illustrating the record layout of the validity DB 52. The validity DB 52 is a DB that records, in association with each other, a membership card ID uniquely assigned to a membership card 15, a user ID uniquely assigned to a user, and whether the membership card 15 is valid or invalid.

[0040] The validity DB 52 has a membership card ID field, a user ID field, and a status field. The membership card ID field records a membership card ID that is uniquely assigned to the membership card 15. The membership card ID is written to an ID chip mounted on the membership card 15.

[0041] The user ID field records a user ID uniquely assigned to a user who uses the coworking space. The status field records whether the membership card 15 is valid or invalid. A membership card 15 is invalid, for example, when the user has completed the membership cancellation procedure or has not paid the required membership fee.

[0042] The validity DB 52 has one record for each membership card 15. The control unit 41 updates the validity DB 52 as appropriate based on the registration information of the membership card 15 transmitted from the information processing device 20.

[0043] 5 is an explanatory diagram illustrating the record layout of the member DB 57. The member DB 57 is a DB that records user IDs, membership card IDs, names, membership types, billing addresses, registration dates, and options in association with each other. The member DB 57 has a user ID field, a membership card ID field, a name field, a membership type field, a billing address field, a registration date field, and an option field.

[0044] The user ID field stores a user ID uniquely assigned to the user. The membership card ID field stores a membership card ID stored on the membership card 15 held by the user.

[0045] The name field stores the user's name. The membership type field stores the membership type. "Pay-per-use" indicates a pay-per-use membership where the usage fee is paid according to the time spent using the coworking space. "Fixed" indicates a fixed fee membership where a fixed usage fee is paid, for example, monthly, regardless of the time spent using the coworking space.

[0046] The membership types are not limited to "pay-per-use" and "fixed rate." For example, various membership types can be set as appropriate, such as members who can only use the service during the daytime, members who have different fees for daytime and evening use on weekdays, members with a limit on the number of times they can use the service, members with student rates, and members with group discount rates.

[0047] The billing destination field records information necessary for billing a fee via a credit card held by a user, such as the credit card number, the name of the credit card holder, and the expiration date of the credit card. The billing destination field may also record an identification ID necessary for collecting fees from members via a payment agency service. By using a payment agency service, it is possible to avoid having to manage important information such as credit card numbers in the information processing system 10.

[0048] The registration date field records the date of member registration. The option field records optional contracts. For example, "Locker" indicates that an optional contract for a personal locker has been concluded. In other words, the member DB 57 records the user ID and the contract terms of the user in association with each other. The optional contract may be, for example, a contract for a mail receiving service, a contract for an address service, etc.

[0049] The method of billing is not limited to credit card. For example, the billing field may contain information necessary for billing via a bank account, such as a bank account number and account holder name. The billing field may contain information necessary for billing via electronic money, such as electronic money authentication information.

[0050] Although not shown, member DB 57 may have fields for recording information such as a user's address, telephone number, email address, telephone number, SNS (Social Network Service) account, occupation, date of birth, etc. Member DB 57 has one record for one user ID.

[0051] 6 is an explanatory diagram illustrating the record layout of the billing DB 58. The billing DB 58 is a DB that records the billing month, user ID, billing amount, and payment status in association with each other. The billing DB 58 has a billing month field, a user ID field, a billing amount field, and a payment field.

[0052] The billing month field records the billing month. The user ID field records the user ID. The billing amount field records the billing amount calculated based on each user's membership type and usage history. The payment field records the payment status. "Completed" indicates that the payment has been completed and the payment has been made. "Not yet" indicates that the payment has not been completed. For example, if a problem occurs, such as a pre-registered credit card being invalid and billing not being possible, "Error" will be recorded.

[0053] An overview of member registration will now be described. The control unit 21 presents a membership application form to the user via, for example, a WEB (World Wide Web) site and accepts information filled in by the user. The control unit 21 may also obtain the information necessary for membership using a chat system.

[0054] The control unit 21 creates a new record in the member DB 57 and records the information entered by the user in the respective fields. The control unit 21 assigns a unique user ID to the user and notifies the user of the ID.

[0055] A user using the coworking space for the first time stops by the reception desk and presents the user ID notified at the time of registration. The receptionist operates a computer or other device installed at the reception desk to associate the membership card ID recorded on an unused membership card 15 with the user ID and record it in the member DB 57. The receptionist then hands the membership card 15 to the user. This completes the member registration process.

[0056] When recording a record related to a new user in the member DB 57, the control unit 21 may record the membership card ID recorded on an unused membership card 15. In this case, the receptionist refers to the member DB 57 to confirm the membership card ID and hands the corresponding membership card 15 to the user.

[0057] A computer or tablet for accepting member registrations may be installed near the reception desk. Member registration applications may also be accepted by paper application form. In this case, the receptionist enters the information into the member database 57, or the information is automatically read by OCR and recorded in the member database 57.

[0058] A user who has a membership card 15 can use the coworking space without stopping by the reception desk. Specifically, the user can unlock the lock mechanism 13 and enter the coworking space by having the first reader 141 read the membership card 15. Similarly, the user can unlock the lock mechanism 13 and leave the coworking space by having the second reader 142 read the membership card 15.

[0059] Therefore, there is no need for a person to be present at the coworking space to handle reception procedures and manage entry and exit. For example, an employee of an adjacent store may also serve as the coworking space manager.

[0060] Users can easily enter and exit the space using their membership card 15, eliminating the need to install restrooms, vending machines, etc. within the coworking space. Operating companies can easily set up paid coworking spaces by partitioning off parts of large commercial facilities or office buildings. Therefore, operating companies can monetize unused space by using it as paid coworking spaces with a relatively low initial investment.

[0061] The walls surrounding the coworking space should be strong enough that users cannot easily climb over or slip through. For example, you could use connected partitions about one meter high as walls. Since the situation inside the coworking space can be seen from outside, it is possible to provide a coworking space that even first-time users can use with confidence.

[0062] By using walls that are lower than the ceiling height to create a space between the ceiling and the wall, there is no need to install dedicated air conditioning equipment, lighting equipment, fire alarms, etc. within the coworking space, which reduces the initial investment required for the coworking space.

[0063] Unlike the gates used in large facilities such as amusement parks that limit the number of people allowed to pass through to one at a time to prevent tailgating, regular doors can be used, reducing the initial investment required for coworking spaces.

[0064] Figure 7 is an explanatory diagram illustrating the calculation rules for usage time. Figure 7 shows the usage status of the coworking space for each of five users, ID010 to ID050. The vertical axis represents each user, and the horizontal axis represents the time from opening to closing of the coworking space.

[0065] The triangle indicates the time of entry, i.e., the time when the membership card 15 held by the user is read by the first reader 141. The inverted triangle indicates the time of exit, i.e., the time when the membership card 15 held by the user is read by the second reader 142. The thick line indicates the time determined to be the usage time of the user.

[0066] Let's explain this with a specific example. A user with "ID010" entered the room at time t11 and left at time t12. The usage time was from t11 to t12. A user with "ID020" entered the room at time t21, left at time t22, entered at time t23, and left at time t24. The usage time was from t21 to t24.

[0067] The user "ID030" entered the room at time t31, reentered at time t32, and exited at time t33. It is estimated that this user exited the room with someone else between time t31 and time t32. The usage time was from t31 to t33.

[0068] The user with "ID040" entered the store at time t41, but the time of his exit is not recorded. It is assumed that this user left the store with someone else. The usage time was from t41 until closing time.

[0069] User "ID050" left the room at time t51. The entry time is not recorded. It is assumed that this user entered the room with someone else. The usage time was from opening time until t51.

[0070] If a user enters the room for the first time without having their membership card 15 read by the first reader 141, or if a user leaves the room for the last time without having their membership card 15 read by the second reader 142, their usage time will be determined to be long. By informing users of this calculation method, they will be encouraged to read their membership card 15 at least when they enter the room for the first time and when they leave the room for the last time.

[0071] On the other hand, it is acceptable to enter and exit the space together during use, such as for a toilet break, etc. Therefore, a coworking space can be provided that users can use in a casual atmosphere.

[0072] Figure 8 is an example of a screen displaying the congestion status. Figure 8 shows a web page on a website introducing coworking spaces, for example. The congestion status is displayed in a congestion status column 61 in the center of the screen.

[0073] The user can operate the mobile device 30 to view the page and check the congestion status. The congestion information for each of multiple coworking spaces may be displayed as a list on the screen. The user can select a coworking space to use by considering convenience, such as the time required for travel, and the congestion status.

[0074] 9 and 10 are examples of the management screen. Figures 9 and 10 are screens operated and viewed by a person in charge of a coworking space operating company. A menu column 62 is displayed on the left side of the screen.

[0075] 9 shows an example of a screen with "Top" displayed in the menu column 62. In the top column 63 displayed to the right of the menu column 62, the number of fixed-fee members, the number of pay-as-you-go members, the current number of users, the previous month's billing amount, the previous month's deposit amount, and the previous month's refund amount are displayed as icons. Note that refunds are issued in irregular circumstances, such as when a user cancels membership midway through the month or when an incorrect billing occurred in the previous month.

[0076] The top screen allows users to get an overview of the coworking space's operating status. The top screen may also display, for example, the operating expenses for the previous month and the number of active members who have used the space at least once in the previous month.

[0077] 10 shows an example of a screen in which a "member list" is displayed in the menu field 62. A member list field 64 displayed to the right of the menu field 62 lists the user IDs, names, and membership types of members in a table format.

[0078] The person in charge can narrow down the users to be displayed in the list using the search field 641 located at the top of the screen. If the person in charge selects the "Download CSV (Comma Separated Value)" button, the control unit 21 generates a list of members in CSV format.

[0079] Although not shown in the figure, when the person in charge selects the "Details" button, the control unit 21 displays detailed information about the member recorded in the member DB 57. Similarly, when the person in charge selects the "History" button, the control unit 21 displays the entry and exit history of the member recorded in the entry and exit DB 56.

[0080] Although not shown in the figure, when the person in charge selects "Usage history" in the menu field 62, the control unit 21 displays a list of the usage dates and usage times of each user. When the person in charge selects "Daily usage history" in the menu field 62, the control unit 21 displays a list of the usage times of each user on the date specified by the user.

[0081] When the person in charge selects "Billing Information" in the menu field 62, the control unit 21 displays a list of the amount billed to each user. When the person in charge selects "Deposit Information" in the menu field 62, the control unit 21 displays a list of the amount deposited by each user. When the person in charge selects "Refund Information" in the menu field 62, the control unit 21 displays a list of the amount refunded to each user.

[0082] It should be noted that the screens displayed by the control unit 21 are not limited to the screens exemplified above. The user can specify the information they wish to view by appropriately operating the input unit 252. The control unit 21 displays information on the display unit 251 in response to the user's operation.

[0083] Fig. 11 is a flowchart illustrating the flow of processing of a program executed by the authentication server 40. The program in Fig. 11 is executed during business hours of the coworking system.

[0084] The control unit 41 reads the membership card ID recorded on the membership card 15 via the reader 14 (step S501). The control unit 41 searches the validity DB 52 using the membership card ID as a key to extract a record. The control unit 41 references the status field of the extracted record to determine whether the membership card 15 is valid or not (step S502). If the control unit 41 cannot extract a record from the validity DB 52 using the membership card ID as a key, it determines that the membership card 15 is not valid.

[0085] If it is determined that the password is not valid (NO in step S502), the control unit 41 outputs an error notification (step S503). Specifically, the control unit 41 outputs a beep or a voice message such as "Error" from a speaker (not shown), for example.

[0086] The control unit 41 may output an error notification by flashing an LED (Light Emitting Diode) (not shown) provided in the reader 14. The control unit 41 may display the error notification on a display panel (not shown) provided in the reader 14. The control unit 41 may notify the person in charge of the coworking space of the error.

[0087] If it is determined to be valid (YES in step S502), the control unit 41 controls the key mechanism 13 to unlock the gate unit 11 (step S504). Releasing the lock allows the user to pass through the entrance / exit 12. The control unit 41 records the user's entry and exit (step S505). Specifically, the control unit 41 creates a new record in the entry / exit DB 51. The control unit 41 records the date and time when the reader 14 read the membership card 15 in the date and time field.

[0088] The control unit 41 records the user ID extracted in step S502 in the user ID field. When the membership card 15 is read from the first reader 141, the control unit 41 records "in" in the entry / exit field. When the membership card 15 is read from the second reader 142, the control unit 41 records "exit" in the entry / exit field. Therefore, either "in" or "exit" is recorded in the entry / exit field.

[0089] After step S503 or step S505 is completed, the control unit 41 determines whether to end the process (step S506). For example, if the closing time of the coworking space has passed, the control unit 41 determines to end the process.

[0090] If it is determined not to end the process (NO in step S506), the control unit 41 returns to step S501. If it is determined to end the process (YES in step S506), the control unit 41 ends the process.

[0091] In step S503, the control unit 41 may record the existence of the user who attempted to use the invalid membership card 15 so that the person in charge can refer to the record later. The person in charge may take action such as sending the user direct mail informing them how to renew their contract.

[0092] Fig. 12 is a flowchart illustrating the processing flow of the program for determining the congestion state. The program in Fig. 12 is started before the coworking space opens for business and is executed during business hours.

[0093] The control unit 21 sets the variable "number of people" to an initial value of zero (step S601). The control unit 21 acquires one new record added to the entry / exit DB 56 through replication processing with the entry / exit DB 51 (step S602). The control unit 21 determines whether "enter" is recorded in the entry / exit field of the acquired record (step S603).

[0094] If it is determined that "enter" is recorded (YES in step S603), the control unit 21 adds 1 to the variable "number of people" (step S604). If it is determined that "enter" is not recorded (NO in step S603), the control unit 21 subtracts 1 from the variable "number of people" (step S605). Note that if the "number of people" is zero, the control unit 21 does not perform the subtraction and keeps the "number of people" at zero.

[0095] The control unit 21 compares the variable "number of people" with a predetermined first threshold and a predetermined second threshold to make a determination (step S606). The first threshold is, for example, a value of about 75 percent of the capacity of the coworking space. The second threshold is, for example, a value of about 90 percent of the capacity of the coworking space.

[0096] If the variable "number of people" is less than the first threshold (less than the first threshold in step S606), the control unit 21 determines that the congestion state of the coworking space is "roomy" (step S607). If the variable "number of people" is equal to or greater than the first threshold and less than the second threshold (equal to or greater than the first threshold and less than the second threshold in step S606), the control unit 21 determines that the congestion state of the coworking space is "slightly crowded" (step S608). If the variable "number of people" is equal to or greater than the second threshold (equal to or greater than the second threshold in step S606), the control unit 21 determines that the congestion state of the coworking space is "full" (step S609).

[0097] After step S607, step S608, or step S609 is completed, the control unit 21 transmits the congestion status to a web server (not shown) (step S610). The web server reflects the received congestion status on a web page. For example, FIG. 8 shows an example of a web page when the control unit 21 determines in step S606 that the variable "number of people" is less than the first threshold value.

[0098] The control unit 21 determines whether to end the process (step S611). For example, if the closing time of the coworking space has passed, the control unit 21 determines to end the process. If it is determined not to end the process (NO in step S611), the control unit 21 returns to step S602. If it is determined to end the process (YES in step S611), the control unit 21 ends the process.

[0099] Fig. 13 is a flowchart illustrating the processing flow of a program that executes processing for billing fees. The program in Fig. 13 is executed, for example, during monthly billing processing. The program in Fig. 13 may also be executed when designated by a person in charge at the operating company.

[0100] The control unit 21 selects the user ID of the member to be billed (step S621). The control unit 21 may accept input of the user ID by the administrator. The control unit 21 searches the member DB 57 using the user ID as a key to extract a record. The control unit 21 determines whether the member is a pay-as-you-go member based on the membership type field of the extracted record (step S622).

[0101] If it is determined that the user is not a pay-per-use member, i.e., a fixed fee member (NO in step S622), the control unit 21 creates a new record in the billing DB 58. The control unit 21 records the billing month being calculated in the billing month field, the user ID selected in step S621 in the user ID field, a predetermined fixed fee in the billing amount field, and "Not yet" in the settlement field (step S623). The fixed fee recorded in the billing amount field includes the fee for any paid options to which the user has subscribed.

[0102] If it is determined that the user is a pay-per-use member (YES in step S622), the control unit 21 starts a daily fee calculation subroutine (step S624). The daily fee calculation subroutine is a subroutine that calculates a daily usage fee based on the data recorded in the entry / exit DB 56. The processing flow of the daily fee calculation subroutine will be described later.

[0103] The control unit 21 determines whether the processing for the billing period has ended (step S625). If it determines that the processing has not ended (NO in step S625), the control unit 21 returns to step S624. If it determines that the processing has ended (YES in step S625), the control unit 21 calculates the fee to be billed to the user by adding up the daily usage fee calculated in the daily fee calculation subroutine and the fee for the paid option to which the user has subscribed (step S626).

[0104] The control unit 21 creates a new record in the billing DB 58. The control unit 21 records the billing month being calculated in the billing month field, the user ID selected in step S621 in the user ID field, the usage fee calculated in step S626 in the billing amount field, and "Not yet" in the payment field (step S627).

[0105] After step S623 or step S627 is completed, control unit 21 performs billing processing (step S628). Specifically, control unit 21 searches member DB 57 using the user ID acquired in step S621 as a key to extract a record. Control unit 21 transmits data related to the billing of the fee to the credit card company based on the information recorded in the billing destination field of the extracted record.

[0106] When the invoiced fee is paid, the control unit 21 extracts the corresponding record from the invoice DB 58 and records "paid" in the payment field. In this way, the control unit 21 realizes the function of the payment processing unit of this embodiment.

[0107] The control unit 21 may process the invoicing process for the fixed fee of a user on a fixed fee system and the fee for a paid option separately without adding them up.The control unit 21 may process the invoicing process for the usage fee of a user on a pay-per-use system and the fee for a paid option separately without adding them up.

[0108] The control unit 21 determines whether to end the process (step S629). For example, when the process for all members has been completed, or when the process for the member designated by the administrator has been completed, the control unit 21 determines to end the process.

[0109] If it is determined not to end (NO in step S629), the control unit 21 returns to step S621. If it is determined to end (YES in step S629), the control unit 21 ends the process.

[0110] 14 is a flowchart illustrating the flow of processing in the daily fee calculation subroutine. The daily fee calculation subroutine is a subroutine for calculating a fee for one day based on the data recorded in the entry / exit DB 56.

[0111] Using the user ID and date as keys, the control unit 21 extracts records for one day for one user from the entry / exit DB 56 (step S641). The control unit 21 determines whether the record with the earliest time among the extracted records indicates entry, i.e., whether "enter" is recorded in the entry / exit field (step S642).

[0112] If it is determined that it means entering the room (YES in step S642), the control unit 21 determines that the entry time on that day is the time recorded in the time field of the earliest record (step S643).If it is determined that it does not mean entering the room (NO in step S642), the control unit 21 determines that the entry time on that day is the opening time of the coworking space (step S644).

[0113] After step S643 or step S644 is completed, control unit 21 determines whether the latest record among the extracted records indicates leaving the room, that is, whether "exit" is recorded in the entry / exit field (step S645).

[0114] If it is determined that this means leaving the room (YES in step S645), the control unit 21 determines that the leaving time on that day is the time recorded in the time field of the latest record (step S646).If it is determined that this does not mean leaving the room (NO in step S645), the control unit 21 determines that the leaving time on that day is the closing time of the coworking space (step S647).

[0115] After step S646 or step S647 is completed, the control unit 21 calculates the user's stay time, that is, the time from the time of entry to the time of exit (step S648). By step S648, the control unit 21 realizes the function of a usage time calculation unit that calculates the user's usage time.

[0116] The control unit 21 calculates the daily fee based on the length of stay (step S649). The fee is calculated by multiplying the hourly fee by the length of stay, for example. A maximum daily fee may be set.

[0117] The control unit 21 associates the user ID, the date, and the fee for one day, and temporarily records them in the auxiliary storage device 23 or the main storage device 22 (step S650). The control unit 21 may record the fee for each date in a predetermined database. Thereafter, the control unit 21 ends the process.

[0118] The entrance / exit 12 may be an automatic door. In that case, the key mechanism 13 controls the opening and closing of the automatic door instead of locking and unlocking. Multiple entrances / exits 12 may be installed in one coworking space. A first reader 141 and a second reader 142 may be installed at each entrance / exit 12. There may be an entrance / exit 12 dedicated to entry where the first reader 141 is installed, and an entrance / exit 12 dedicated to exit where the second reader 142 is installed.

[0119] A user ID may be recorded on the membership card 15. The first reader 141 and the second reader 142 read the user ID recorded on the membership card 15, and search the validity DB 52, which records the user ID in association with its validity, to determine whether the read user ID is valid.

[0120] The mobile device 30 owned by the user may also serve as the membership card 15. For example, a serial number registered in a short-range wireless communication chip built into the mobile device 30 owned by the user can be used as the membership card ID. The user can enter the coworking space by having the reader 14 read the mobile device 30.

[0121] Authentication application software that transmits a user ID from a short-range wireless communication chip may be installed in the portable device 30 owned by the user. Authentication application software that displays a barcode indicating the user ID may be installed in the portable device 30 owned by the user.

[0122] The program described using FIG. 12 may have a function that allows the manager to instruct the correction of the number of users. For example, when the manager enters the room for cleaning, the manager counts the number of users present and corrects the variable "number of users." This allows the program to correct errors caused by tailgating and display the appropriate congestion status.

[0123] Instead of using the program described with reference to Figure 12, the congestion situation may be determined based on images captured by a camera installed in the coworking space. Technology for determining the number of people captured in an image is well known, and therefore a description thereof will be omitted. Installing a camera in the coworking space is also expected to have the effect of suppressing inappropriate behavior by users.

[0124] According to this embodiment, it is possible to provide an information processing system 10 that charges an appropriate fee to each user even when tailgating occurs. According to this embodiment, it is possible to provide an information processing system 10 that uses unused space as a paid coworking space with a relatively inexpensive initial investment, thereby generating profits.

[0125] Users do not need to worry about being tailgated except when they first enter and when they finally leave. Therefore, it is possible to provide a coworking space with a peaceful atmosphere where there is no problem if users observe good manners, such as holding the door when entering or leaving.

[0126] As mentioned above, the coworking space is an example of a room. The room in which gate unit 11 is installed may be, for example, an exercise gym equipped with exercise equipment such as a treadmill, a kids' space equipped with play equipment for young children, a game corner equipped with game machines, or a reading space equipped with comics and books.

[0127] [Variation 1-1] In step S628 described with reference to FIG. 13, the control unit 21 issues an invoice to a predetermined destination instead of sending data related to the charge to the credit card company. The control unit 21 may issue a single invoice that combines charges related to multiple user IDs. By using an invoice, a company or the like can process employee usage fees as an expense, for example, as part of employee benefit programs or teleworking measures.

[0128] The control unit 21 may issue an estimate instead of an invoice. Even in a company or the like that makes payments after internal approval based on an estimate, the employee usage fees can be expensed in accordance with the company rules.

[0129] The control unit 21 may automatically issue a receipt after the invoice is paid. Automatic confirmation of invoices and payments via bank accounts or cloud services has been performed for some time, so detailed explanations will be omitted.

[0130] [Variation 1-2] The fee for a pay-as-you-go user may vary depending on the time period during which the user enters the room. For example, in the daily fee calculation subroutine described with reference to Fig. 14, the control unit 21 sets the fee per hour based on the time of entry determined in step S643. For example, the control unit 21 sets the fee for a user whose entry time determined in step S643 is in the morning to 200 yen per hour regardless of the time of exit determined in step S646, and sets the fee for a user whose entry time determined in step S643 is between 6:00 PM and 8:00 PM to 300 yen per hour regardless of the time of exit determined in step S646.

[0131] The control unit 21 may use different usage fees for each date, each day of the week, or each month. These usage fees are set based on, for example, the congestion status or congestion forecast of the coworking space. The control unit 21 displays the usage fee for that day on, for example, a digital signage display placed near the gate unit 11 and on a website introducing the coworking space.

[0132] Pay-as-you-go users can use the coworking space with peace of mind, as the usage fee confirmed upon entry is applied all day. By setting lower fees for users who enter during times when there are relatively few users and higher fees for users who enter during times when there are relatively many users, the usage of the coworking space can be leveled out.

[0133] The control unit 21 may use different fees for each time period during which the user stays. A specific example will be given below. As an example, the usage fee in the morning is set to 200 yen per hour, the usage fee in the afternoon is set to 250 yen per hour, and the usage fee in the evening after 6:00 PM is set to 300 yen per hour.

[0134] If the entry time determined in step S643 is 10:00 and the exit time determined in step S646 is 15:00, the user will stay for 2 hours in the 200 yen time slot and for 3 hours in the 250 yen time slot. Therefore, in step S649, the control unit 21 calculates the fee as 200 x 2 + 250 x 3 = 1,150 yen.

[0135] [Embodiment 2] This embodiment relates to an information processing system 10 that notifies a user who is a pay-as-you-go member when the fee exceeds a threshold value. Explanation of parts common to the first embodiment will be omitted.

[0136] Fig. 15 is a flowchart illustrating the flow of processing of the program according to embodiment 2. The program in Fig. 15 is executed every time a user leaves the room, or during the night on the day when the user uses the coworking space.

[0137] The control unit 21 selects the user ID of the member for whom the fee is to be calculated (step S661). The control unit 21 searches the member DB 57 using the user ID as a key to extract a record. The control unit 21 determines whether the member is a pay-as-you-go member based on the membership type field of the extracted record (step S662).

[0138] If it is determined that the user is a pay-per-use member (YES in step S662), the control unit 21 starts a daily fee calculation subroutine (step S663). The daily fee calculation subroutine is the same as the subroutine described using FIG. 14.

[0139] The control unit 21 determines whether the processing for the billing period has ended (step S664). If it determines that the processing has not ended (NO in step S664), the control unit 21 returns to step S663. If it determines that the processing has ended (YES in step S664), the control unit 21 adds up the fees for each day calculated in the daily fee calculation subroutine to calculate the cumulative fee (step S665).

[0140] The control unit 21 determines whether the cumulative charge is equal to or greater than a predetermined threshold (step S666). The threshold may be, for example, a fixed fee. The threshold may also be a fee set in advance by the user. If it is determined that the cumulative charge is equal to or greater than the threshold (YES in step S666), the control unit 21 sends a notification to the mobile device 30 via email, SMS (Short Message Service), or the like (step S667).

[0141] The control unit 31 receives the notification (step S701). The control unit 31 outputs the received notification to the display unit 351 (step S702). The notification may contain content such as, "This month's pay-as-you-go fee has exceeded 20,000 yen. If you change to a fixed-fee membership by the end of the month, you can use the service for 18,000 yen." The notification may also include a URL (Uniform Resource Locator) for the procedure to change membership type.

[0142] The notification may be posted on a website that each user can access after password authentication, etc. The notification may be displayed on the screen of an application program installed on the mobile device 30.

[0143] If it is determined that the user is not a pay-per-use member, i.e., a fixed fee member (NO in step S662), if it is determined that the number of users is not equal to or greater than the threshold (NO in step S666), or after step S667 is completed, the control unit 21 determines whether or not to terminate the process (step S668). If it is determined not to terminate (NO in step S668), the control unit 21 returns to step S661. If it is determined to terminate (YES in step S668), the control unit 21 terminates the process.

[0144] Instead of sending the notification in step S667, the control unit 21 may automatically switch to the fixed fee system. In that case, the control unit 21 may automatically return the setting to the pay-as-you-go system the following month.

[0145] According to this embodiment, it is possible to provide an information processing system 10 that notifies a user who is a pay-per-use member when the fee exceeds a fixed fee. By preventing the user from being charged an unexpected fee, it is possible to provide an information processing system 10 that improves customer satisfaction.

[0146] [Embodiment 3] 16 is a functional block diagram of an information processing device 20 according to embodiment 3. The information processing device 20 includes an entry information acquisition unit 81, an exit information acquisition unit 82, a usage time calculation unit 83, and a billing processing unit 84.

[0147] The entry information acquisition unit 81 acquires the user ID and entry time of a user who unlocks the smart lock from outside the room. The exit information acquisition unit 82 acquires the user ID and exit time of a user who unlocks the smart lock from inside the room. The usage time calculation unit 83 calculates the usage time of each user based on the user ID, entry time, and exit time. The billing processing unit 84 bills each user's usage fee, calculated based on the user ID and usage time, via the user's credit card.

[0148] [Embodiment 4] 17 is an explanatory diagram illustrating the configuration of an information processing system 10 according to a fourth embodiment. This embodiment relates to a form in which an information processing device 20 according to this embodiment is realized by combining and operating a general-purpose computer 90 and a program 97. Explanations of parts common to the first embodiment will be omitted.

[0149] The computer 90 includes a reading unit 29 in addition to the control unit 21, main memory device 22, auxiliary memory device 23, communication unit 24, display unit 251, input unit 252, and bus.

[0150] The program 97 is recorded on a portable recording medium 96. The control unit 21 reads the program 97 via the reading unit 29 and stores it in the auxiliary storage device 23. The control unit 21 may also read the program 97 stored in a semiconductor memory 98, such as a flash memory, implemented in the computer 90. Furthermore, the control unit 21 may download the program 97 from another server computer (not shown) connected via the communication unit 24 and a network (not shown) and store it in the auxiliary storage device 23.

[0151] The program 97 is installed as a control program in the computer 90, and is executed by loading it into the main storage device 22. In this way, the information processing device 20 described in the first embodiment is realized.

[0152] [Embodiment 5] This embodiment relates to an information processing system 10 that manages a coworking space including a reservation target area 192. Explanation of parts common to the first embodiment will be omitted.

[0153] FIG. 18 is a map of a coworking space according to the fifth embodiment. The coworking space according to the present embodiment is surrounded by walls or partitions on all four sides, and has a gate unit 11 located in one place. Two reservation target areas 192 are located inside the room. The reservation target area 192 is surrounded by walls or partitions on all four sides, and has a reservation gate unit 111 located in one place.

[0154] The reservation gate unit 111 is composed of an entrance or exit such as a door, and a key mechanism 13. The key mechanism 13 of the reservation gate unit 111 is a so-called smart lock that is locked and unlocked via a network, similar to the key mechanism 13 of the gate unit 11. The reservation gate unit 111 may also be equipped with a reader 14, similar to the gate unit 11.

[0155] It is desirable that reservation gate unit 111 has a structure that does not prevent users in reservation target area 192 from going outside reservation target area 192 even when in a locked state. This can prevent accidents in which users are trapped inside reservation target area 192.

[0156] The reservable area 192 may be, for example, a private work booth used by a user who wants to concentrate on work. The reservable area 192 may be a conference room where multiple users can gather. The reservable area 192 may be a conference booth for a web conference. The reservable area 192 may be a recreation area where users can play games, exercise, or the like. The uses and facilities of the two reservable areas 192 may be different.

[0157] The area other than the reservation target area 192 is a common area 191 that can be used as needed by users who have passed through the gate section 11. The common area 191 is equipped with a drink corner with desks, chairs, coffee servers, etc., a multifunction printer, lockers, etc. (not shown).

[0158] 18 is an example. The overall shape of the room, the position of the gate unit 11, the number and arrangement of the reservation target areas 192, etc. are not limited to those shown in FIG.

[0159] In this embodiment, the user makes a reservation for reservation target area 192 using mobile device 30. When the reservation is established, key information for unlocking reservation gate unit 111 of reservation target area 192 at the reserved time is sent to the user, for example, by email or SMS. In the following explanation, an example is given in which the key information is an unlocking URL that can be accessed to send an unlocking request to control unit 41.

[0160] At the reserved time, the user accesses the unlocking URL using the mobile device 30. An unlock button is displayed on the touch panel 35. When the user taps the unlock button, an unlock signal to unlock the reservation gate unit 111 is sent from the web server that displayed the unlock button to the authentication server 40.

[0161] The authentication server 40 unlocks the designated reservation gate unit 111 in response to the unlock signal. The user can enter the reservation target area 192. If the user does not exit the reservation target area 192 after the reserved time has passed, the user is notified that the reservation time has passed by a display installed in the reservation target area 192 or by a push notification on the mobile device 30, for example.

[0162] 19 is an explanatory diagram illustrating the record layout of the reservation key DB 53. The reservation key DB 53 is a database that records location IDs, reservation times, and key information in association with each other. Here, the location ID is an ID uniquely assigned to the reservation target area 192, and by identifying the location ID, the reservation gate unit 111 in the reservation target area 192 can also be identified.

[0163] The reservation key DB 53 has a location ID field, a reservation time field, and a key information field. The reservation time field has a start field and an end field. The location ID field records a location ID. The start field and end field record the start time and end time of the reservation, respectively. The key information field records key information issued by the control unit 41.

[0164] The reservation key DB 53 has one record for each reservation. The reservation key DB 53 is stored in the auxiliary storage device 43 or an external mass storage device connected to the authentication server 40.

[0165] 20 is an explanatory diagram illustrating the record layout of the reservation DB 59. The reservation DB 59 is a database that records location IDs, reservation times, user IDs, and key information in association with each other. The reservation DB 59 has a location ID field, a reservation time field, a user ID field, and a key information field. The reservation time field has a start field and an end field.

[0166] The location ID field records the location ID. The start field and end field record the start time and end time of the reservation, respectively. The user ID field records the user ID of the user who made the reservation. The key information field records key information issued by the control unit 41.

[0167] The reservation DB 59 has one record for each reservation. The reservation DB 59 is recorded in the auxiliary storage device 23 or an external mass storage device connected to the information processing device 20. The control units 21 and 41 synchronize each record recorded in the reservation key DB 53 with each record recorded in the reservation DB 59, excluding the user ID field, through a replication process. Since the replication process has been used for a long time, detailed explanation will be omitted.

[0168] Fig. 21 is a flowchart illustrating the flow of processing of a program at the time of reservation according to embodiment 5. The program of Fig. 21 is started by the user operating the mobile device 30 when making a reservation for the reservation target area 192.

[0169] The control unit 31 acquires reservation information recorded in the reservation DB 59 from the information processing device 20 via the network (step S711). The control unit 31 displays a reservation reception screen 65 (see FIG. 23) on the display unit 351 (step S712). As will be described later, the reservation reception screen 65 displays time slots for which reservations have already been made.

[0170] The user operates the input unit 352 to input a reservation request. The reservation request includes information about the reservation target area 192 and time period for which the user wishes to make a reservation. The control unit 31 accepts the input reservation request (step S713). The control unit 31 transmits the reservation request to the information processing device 20 (step S714).

[0171] The control unit 21 receives the user ID and information related to the reservation (step S671). The control unit 21 requests the authentication server 40 to issue key information for unlocking the reservation gate unit 111 corresponding to the reservation target area 192 received in step S671 during the reservation target time period (step S672).

[0172] The control unit 41 receives the request (step S511). The control unit 41 generates key information according to the received request (step S512). Here, the key information is data used when unlocking a specific reservation gate unit 111 during a specific time period, and is an example of reservation unlocking information in this embodiment. As mentioned above, the key information will be described using an example in which the key information is an unlocking URL that can be accessed to send an unlocking request to the control unit 41.

[0173] The control unit 41 transmits the generated key information to the information processing device 20 (step S513). The control unit 41 creates a new record in the reservation key DB 53, and records the location ID corresponding to the reservation target area 192, the reservation time, and the generated key information (step S514).

[0174] The control unit 21 receives the key (step S673). The control unit 21 creates a new record in the reservation DB 59, and records the location ID corresponding to the reservation target area 192 received in step S671, the user ID, and the key information received in step S673 (step S674).

[0175] The control unit 21 transmits the key information to the mobile device 30 via email, SMS, or the like (step S675). The control unit 31 receives the key information (step S715). The control unit 31 notifies the user that the key information has been received (step S716). Thereafter, the mobile device 30 ends the process.

[0176] Fig. 22 is a flowchart illustrating the flow of processing of a program when unlocking according to embodiment 5. The program of Fig. 21 is started by the user operating the mobile device 30 when unlocking the reservation target area 192.

[0177] The control unit 31 displays the key information received in step S715 of the flowchart described with reference to Fig. 21 on the touch panel 35 (step S721). As described above, the key information will be described as an unlocking URL.

[0178] The user operates the input unit 352 to access the unlocking URL. If it is within the reserved time period, an unlock button is displayed on the touch panel 35. If it is before the reserved time period, a message indicating the available time for unlocking, or a simple error message, is displayed on the touch panel 35. If it is after the reserved time period, a message indicating that the reserved time has passed, or a simple error message, is displayed on the touch panel 35. The flowchart in FIG. 22 shows the processing when the unlock button is displayed on the touch panel 35.

[0179] The user taps the unlock button by operating the input unit 352. The control unit 31 accepts the operation by the user (step S722). The key information displayed in step S721 is transmitted to the authentication server 40 via the web server that displayed the unlock button.

[0180] The control unit 41 receives the key information (step S521). The control unit 41 determines whether authentication based on the received key information has been successful (step S522). Specifically, the control unit 41 searches the reservation key DB 53 using the key information as a key to extract a record. If the current time is within the reservation time slot recorded in the reservation time field of the extracted record, the control unit 41 determines that authentication has been successful. If the record cannot be extracted or if the current time is not within the reservation time slot, the control unit 41 determines that authentication has not been successful.

[0181] If it is determined that the authentication is successful (YES in step S522), the control unit 41 controls the key mechanism 13 to unlock the reservation gate unit 111 (step S523). As a result, the user can enter the reservation target area 192 that he or she has reserved.

[0182] After a predetermined time has elapsed, or after a sensor (not shown) detects the passage of a user, the control unit 41 controls the key mechanism 13 to automatically lock the reservation gate unit 111. The key mechanism 13 may also autonomously lock the reservation gate unit 111 after a predetermined time has elapsed, or after detecting the passage of a user.

[0183] If it is determined that the authentication has not been successful (NO in step S522), or after step S523 is completed, the control unit 41 returns to a state of waiting for key information from the mobile device 30. The control unit 41 may display, on a display or the like attached to the reservation gate unit 111, that the authentication has not been successful. The control unit 41 may also notify the administrator of the coworking space or the like that an unauthorized request has been made.

[0184] The control unit 31 waits until the reservation end time approaches (step S723). For example, two minutes before the reservation end time, the control unit 31 notifies the user that the reservation end time is approaching by sounding an alarm, vibrating the vibrator, displaying a message on the display unit 351, or the like (step S724). Thereafter, the control unit 31 ends the process.

[0185] Fig. 23 is a screen according to the fifth embodiment. In step S712 of the flowchart described with reference to Fig. 21, the control unit 31 displays the reservation acceptance screen 65 shown in Fig. 23. The reservation acceptance screen 65 includes a schedule field 658 displayed in the center of the screen, a facility to be used field 651 and a date of use field 653 displayed above the schedule field 658, and a time of use field 654, an area to be used field 652, and an enter button 659 displayed below the schedule field 658.

[0186] The user operates the usage date field 653 to specify a date. The user operates the usage facility field 651 to specify a facility to use. Note that if there is only one facility that the user can use, the usage facility field 651 does not need to be displayed. The control unit 31 displays in the schedule field 658 the reservation status for the reservation target areas 192 installed in the usage facility field 651 on the date specified in the usage date field 653. "Booth 1" and "Booth 2" in FIG. 23 indicate the names given to the respective reservation target areas 192. The horizontal axis of the schedule field 658 indicates the business hours of the coworking space. Hatching indicates time periods that are already booked.

[0187] The user operates the usage time field 654 to set the reservation start time and reservation end time. The user operates the usage area field 652 to specify the reservation target area 192 for which the reservation is to be made. Note that if a time period with a prior reservation is specified, the control unit 31 sets the decision button 659 to an unselectable state. After completing the input, the user selects 659. This completes the user's reservation input, and the control unit 31 accepts information related to the reservation (step S713).

[0188] FIG. 24 shows a screen according to the fifth embodiment. When the user selects "Reservation Information" from the menu field 62 on the left side of the screen, the control unit 31 displays the reservation information screen shown in FIG. 24. The reservation information screen includes a reservation information field 66. The user can check the schedule for which the user has made a reservation by looking at the reservation information field 66. When the user selects the details button 655, the control unit 31 may display key information corresponding to the reservation. The user can use the search field displayed above the reservation information field 66 to search for the schedule for which the user has made a reservation.

[0189] According to this embodiment, it is possible to provide an information processing system 10 that manages a reservation target area 192. By making a reservation, a user can be sure to use a reservation target area 192 that is equipped with desired facilities and the like.

[0190] Providing the reservation gate unit 111 in the reservation area 192 makes it possible to prevent outsiders from carelessly entering the reservation area 192. Therefore, it is possible to provide the reservation area 192 that can be used for meetings or video conferences regarding confidential matters. Note that by sending the key information to the user by email or SMS, the user can distribute the key information to participants in the conference as appropriate.

[0191] For use of the reservation target area 192, an additional fee may be set not only for pay-per-use members but also for fixed-fee members. The "Usage Fee" column in FIG. 24 indicates the amount of the additional fee incurred for each reservation. The additional fee may vary depending on the time of reservation or the time of use. For example, a discounted fee may be offered to users who make a reservation immediately before use.

[0192] For fixed-amount members, conditions may be set such as free use up to 1,000 yen per month. The control unit 21 adds an additional fee to the fee described in the first embodiment and bills the user.

[0193] The reservation target area 192 may be located in a place that a user can reach without passing through the gate unit 11. A user can easily invite a person to a meeting to be held in the reservation target area 192, even if the person is not a registered user of the coworking space.

[0194] Instead of providing the key information to the invited guest, the user may give the guest his / her phone number, etc. When the guest arrives in front of reservation gate unit 111, he / she calls the inviting user to notify them of his / her arrival. The user operates mobile device 30 to use the key information to unlock reservation gate unit 111. In this embodiment, since the lock can be unlocked using the key information without going to reservation gate unit 111, there is no need to explain to the guest how to unlock reservation gate unit 111, etc.

[0195] The control unit 21 may acquire location information of the portable device 30 in addition to the key information, and unlock the portable device 30 only when the portable device 30 is in front of the reservation gate unit 111. It is possible to provide an information processing system 10 that prevents anyone other than the person who made the reservation from entering the reservation target area 192.

[0196] An electronic money settlement terminal using NFC or a barcode may be installed in the reservation gate unit 111. After successful authentication in step S522, the control unit 41 bills the user for the use of the reservation target area 192 via the settlement terminal. After the settlement is complete, the control unit 41 proceeds to step S523 and unlocks the reservation gate unit 111. As described above, it is possible to provide an information processing system 10 that settles the fee each time the reservation target area 192 is used.

[0197] The key information may be a two-dimensional or one-dimensional barcode that is read by a camera attached to the reservation gate unit 111 to unlock the reservation gate unit 111. When a barcode is used as the key information, the control unit 31 displays the barcode on the touch panel 35 in step S721. Step S722 is omitted. The user holds the barcode up to the camera attached to the reservation gate unit 111. In step S521, the control unit 41 acquires the barcode via the network.

[0198] The key information may be a key code that the user inputs using a numeric keypad attached to the reservation gate unit 111 to unlock the reservation gate unit 111. When a key code is used as the key information, the control unit 31 displays the key code on the touch panel 35 in step S721. Step S722 is omitted. The user inputs the key code into the numeric keypad attached to the reservation gate unit 111. In step S521, the control unit 41 acquires the input key code via the network.

[0199] [Variation 5-1] FIG. 25 is a map of a coworking space according to Modification 5-1. In this modification, each reservation target area 192 does not have a reservation gate unit 111. A user can use the reservation target area 192 at the reserved time without performing any operations such as unlocking. If a user who made a reservation visits the reservation target area 192 and finds that another user is using it, the two users will mutually confirm the reservation information screen, for example, as described using FIG. 24.

[0200] It should be noted that reservation target areas 192 with reservation gate sections 111 and reservation target areas 192 without reservation gate sections 111 may coexist.

[0201] [Embodiment 6] This embodiment relates to an information processing system 10 that provides a reservation target area 192 that has not been reserved until immediately before, without any additional charge. Explanation of parts common to the fifth embodiment will be omitted.

[0202] Fig. 26 is a flowchart illustrating the flow of processing of the program according to embodiment 6. The control unit 21 continues to execute the program of Fig. 26 in parallel for each reservation target area 192 during business hours.

[0203] The control unit 21 searches the reservation DB 59 and determines whether the reservation target area 192 has not been reserved, i.e., has become vacant, for example, five minutes from now (step S681). If it is determined that the area is vacant (YES in step S681), the control unit 21 displays a notification, for example, on a display disposed in the coworking space and on a web page related to the coworking space (step S682).

[0204] For example, the notification might be a message such as, "Web conference booth A can be used at no additional charge from 3:00 p.m. to 4:00 p.m. Use is on a first-come, first-served basis. Please come directly to Web conference booth A."

[0205] The control unit 21 waits until a time when no reservations have been made arrives (step S683). Specifically, for example, when the above message is displayed, the control unit 21 waits until 3:00 p.m. The control unit 21 transmits a request to the authentication server 40 to unlock the reservation gate unit 111 for the reservation target area 192 that is vacant (step S684).

[0206] The control unit 41 receives the unlock request (step S531). The control unit 41 confirms that the information processing device 20 that sent the unlock request is the server that manages the reservation target area 192 (step S532). If the confirmation cannot be made, the control unit 41 ignores the unlock request received in step S531.

[0207] The control unit 41 controls the key mechanism 13 to unlock the reservation gate unit 111 (step S533). In this embodiment, even after the user has passed through the reservation gate unit 111, the control unit 41 keeps the reservation gate unit 111 unlocked.

[0208] The control unit 21 waits until the end of the available time (step S685). For example, two minutes before the end of the available time, the control unit 21 displays a notice on a display or the like installed in the reservation target area 192 (step S686).

[0209] The notification may be, for example, a message such as "The time during which you can use this Web conference booth A without additional charges will soon end. Please leave immediately." After the free time ends, the control unit 21 transmits a locking request to the authentication server 40 for the reservation gate unit 111 for the reservation target area 192 (step S687).

[0210] The control unit 41 receives the lock request (step S534). The control unit 41 confirms that the information processing device 20 that sent the lock request is the server that manages the reservation target area 192 (step S535). If the control unit 41 cannot confirm this, the control unit 41 ignores the unlock request received in step S534. After confirmation, the control unit 41 controls the key mechanism 13 to lock the reservation gate unit 111 (step S536).

[0211] If it is determined that the space is not available (NO in step S681), or after step S687 is completed, the control unit 21 determines whether to end the process (step S689). For example, if the closing time of the coworking space is approaching, the control unit 21 determines to end the process.

[0212] If it is determined not to end (NO in step S689), control unit 21 returns to step S681. If it is determined to end (YES in step S689), control unit 21 ends the process.

[0213] According to this embodiment, it is possible to provide an information processing system 10 that can effectively utilize the reservation target area 192 that has not been reserved. By allowing the user to experience using the reservation target area 192 without any additional charge, it is possible to provide an information processing system 10 that allows the user to experience the benefits of the reservation target area 192 and encourages future use.

[0214] [Embodiment 7] This embodiment relates to an information processing system 10 that can be used under a ticket system in which tickets are purchased as needed, in addition to the fixed fee system and pay-per-use system described above. Explanation of parts common to the first embodiment will be omitted.

[0215] Fig. 27 is an explanatory diagram illustrating the record layout of the member DB 57 according to the seventh embodiment. The member DB 57 according to the present embodiment has a configuration in which a ticket field is added to the member DB 57 according to the first embodiment described using Fig. 5. The ticket field records the number of tickets held by each user.

[0216] "Ticket" in the membership type field indicates a ticket-based membership type. Ticket-based members purchase tickets online by operating the mobile device 30. The control unit 21 adds the number of tickets purchased by the user to the ticket field. Note that so-called multi-ride tickets may also be offered, which allow users to purchase 11 tickets for the price of 10.

[0217] 28 is a flowchart illustrating the flow of processing of the program according to embodiment 7. The program in FIG. 28 is executed in place of the program described with reference to FIG.

[0218] The control unit 41 reads the membership card ID recorded on the membership card 15 via the reader 14 (step S501). The control unit 41 searches the validity DB 52 using the membership card ID as a key to extract a record. The control unit 41 references the status field of the extracted record to determine whether the membership card 15 is valid or not (step S502). If the control unit 41 cannot extract a record from the validity DB 52 using the membership card ID as a key, it determines that the membership card 15 is not valid.

[0219] If it is determined to be valid (YES in step S502), the control unit 41 transmits the membership card ID read in step S501 to the information processing device 20 (step S541). The control unit 21 receives the membership card ID (step S691). The control unit 21 determines whether the user's membership type is a ticket-based membership (step S692).

[0220] Specifically, control unit 21 searches member DB 57 using the membership card ID as a key and extracts a record. If "ticket" is recorded in the membership type field of the extracted record, control unit 21 determines that the user's membership type is a ticket system.

[0221] If it is determined that the user is not a ticket-based member, that is, a pay-per-use or fixed-rate member (NO in step S692), the control unit 21 transmits a message to the authentication server 40 to unlock the gate unit 11 (step S693).

[0222] If it is determined that the user is a ticket-based member (YES in step S692), the control unit 21 obtains the number of tickets held by the user from the ticket field of the extracted record. If the user holds the required number of tickets, the control unit 21 updates the data in the ticket field to a value obtained by subtracting the required number of tickets (step S694).

[0223] When a user who has entered the gate unit 11 once is permitted to enter and exit the gate unit 11 freely on the same day, the control unit 21 updates the data in the ticket field only if it is the first entry on the day.

[0224] The control unit 21 transmits information regarding whether the gate unit 11 has been unlocked to the authentication server 40 (step S695). Specifically, if the user has the required number of tickets in step S694, the control unit 21 transmits a message to the authentication server 40 indicating that the gate unit 11 will be unlocked. If the number of tickets is insufficient, the control unit 21 transmits a message to the authentication server 40 indicating that the gate unit 11 will not be unlocked.

[0225] The control unit 41 receives the information transmitted in step S693 or step S695 (step S542). The control unit 41 determines whether the received information indicates that the lock should be released (step S543). If it is determined that the information indicates that the lock should be released (YES in step S543), the control unit 41 controls the key mechanism 13 to release the lock on the gate unit 11 (step S504). The control unit 41 records the entry and exit of the user in the entry and exit DB 51 (step S505).

[0226] If it is determined that the setting is not valid (NO in step S502), or if it is determined that the setting is not to be released (NO in step S543), the control unit 41 outputs an error notification (step S503). Specifically, the control unit 41 outputs a beep or a voice message such as "Error" from a speaker (not shown), for example.

[0227] After step S503 or step S505 is completed, the control unit 41 determines whether to end the process (step S506). For example, if the closing time of the coworking space has passed, the control unit 41 determines to end the process.

[0228] If it is determined not to end the process (NO in step S506), the control unit 41 returns to step S501. If it is determined to end the process (YES in step S506), the control unit 41 ends the process.

[0229] After step S695 is completed, the control unit 21 transmits the number of tickets owned by the user to the mobile device 30 (step S696). The mobile device 30 receives the number of tickets (step S731). The mobile device 30 displays a message according to the number of tickets on the touch panel 35 (step S732).

[0230] For example, if there are two tickets remaining, the control unit 31 displays "There are two tickets remaining." If there is one ticket remaining, the control unit 31 displays "There are no more tickets. Please purchase a ticket before your next visit." If there are not enough tickets and the gate unit 11 is not unlocked, the control unit 31 displays "You cannot enter because there are not enough tickets. Please purchase the ticket you need."

[0231] The control unit 31 may display a button for purchasing tickets online on the touch panel 35. The control unit 31 may also display, on the touch panel 35, a button for purchasing a coupon ticket and a button for purchasing a single-ride ticket, side by side.

[0232] A user who does not have enough tickets can operate the portable device 30 to purchase tickets online, and then have the reader 14 read the membership card 15 again, thereby unlocking the gate unit 11 and allowing entry.

[0233] According to this embodiment, it is possible to provide the information processing system 10 that can accommodate users who want to pay only for the amount of use. For example, it is possible to provide the information processing system 10 that can carry out sales promotions by offering three tickets as gifts to newly registered users.

[0234] The number of tickets required for one use may be set to differ depending on the facility used. A pay-per-use or fixed-rate user may be able to use the tickets described in this embodiment when using the reservation target area 192 described in the fifth embodiment.

[0235] [Embodiment 8] This embodiment relates to an information processing system 10 that can limit the number of times a user can use the system. Explanation of parts common to the first embodiment will be omitted.

[0236] Figure 29 is an explanatory diagram illustrating the record layout of the member DB 57 of the eighth embodiment. The member DB 57 of this embodiment has a configuration in which a remaining number of times field is added to the member DB 57 of the first embodiment described using Figure 5. The remaining number of times each user can use the facility is recorded in the remaining number of times field. "Unlimited" indicates that there is no limit on the number of times the facility can be used.

[0237] Each time a user uses a facility, the control unit 21 decrements the value in the remaining number of times field by one. If the value in the remaining number of times field becomes zero, the gate unit 11 of the facility will not be unlocked with the membership card 15 of that user. The control unit 21 sets the remaining number of times field to an initial value at a predetermined frequency, for example, once a day or once a week. Note that the initial value may be set to a different value for each user.

[0238] Fig. 30 is a flowchart illustrating the processing flow of the program according to the eighth embodiment. The processing up to step S691 is the same as the processing flow of the seventh embodiment explained using Fig. 28, and therefore the explanation will be omitted. The control unit 21 determines whether the remaining number of times for the user is zero (step S801).

[0239] Specifically, the control unit 21 searches the member DB 57 using the membership card ID as a key and extracts a record. If the remaining number of times field of the extracted record has "0" recorded, the control unit 21 determines that the remaining number of times for the user is zero.

[0240] If it is determined that the remaining number of times is not zero, i.e., that the user is a member who can use the facility (NO in step S801), the control unit 21 updates the extracted record and decrements the remaining number of times by one (step S802). The control unit 21 transmits a message to the authentication server 40 indicating that the gate unit 11 will be unlocked (step S803). If it is determined that the remaining number of times is zero (YES in step S801), the control unit 21 transmits a message to the authentication server 40 indicating that the gate unit 11 will not be unlocked (step S804).

[0241] The control unit 41 receives the information transmitted in step S803 or step S804 (step S542). The subsequent processing is the same as the processing flow in the seventh embodiment described with reference to FIG. 28, and therefore a description thereof will be omitted.

[0242] The control unit 21 transmits a message that the remaining number of times is zero to the mobile device 30 (step S805). The mobile device 30 receives the message that the remaining number of times is zero (step S741). The mobile device 30 displays a message described below on the touch panel 35 (step S742).

[0243] For example, if the remaining number of times is initialized once a day, the control unit 31 displays "Today's usage limit has been exceeded. You cannot use the service again today." Similarly, if the remaining number of times is initialized once a week, the control unit 31 displays "This week's usage limit has been exceeded. Please wait until next Monday."

[0244] For users who can use the service by changing their membership type, the control unit 31 may display a button for applying to change their membership type along with a message saying, "You have exceeded the number of uses for today. If you wish to use the service again, please go through the procedure to change to a fixed membership."

[0245] The control unit 31 may display a button for purchasing tickets online along with a message saying, "Today's usage limit has been exceeded. Additional tickets can be purchased for 200 yen each." When the user purchases a ticket, the control unit 21 adds the number of tickets purchased to the remaining number of times field.

[0246] If the user agrees to pay the additional fee according to the terms and conditions, the control unit 21 sends a message to the authentication server 40 in step S804 that the gate unit 11 will be unlocked, and the control unit 21 may display a message in step S742 saying, "Today's usage limit has been exceeded. Any subsequent usage will incur an additional fee of 10 yen per minute." The control unit 21 bills the user for the additional fee in addition to the regular fee.

[0247] According to this embodiment, by imposing usage restrictions or charging additional fees on specific users who use the system frequently, it is possible to provide an information processing system 10 that equalizes usage among users and manages the system in a way that makes it easy for many users to use.

[0248] [Embodiment 9] This embodiment relates to an information processing system 10 that can issue an unmanned membership card 15. Explanation of parts common to the first embodiment will be omitted.

[0249] In this embodiment, an automatic registration machine for membership cards 15 is installed in the common area 191. Unregistered users enter the common area 191 using key information for guest users issued online and operate the automatic registration machine themselves.

[0250] In this embodiment, the reservation gate unit 111 described in the fifth embodiment is installed at the entrance of the room. The user receives the key information described in the fifth embodiment online. The issuance of the key information is the same as the process in the fifth embodiment described using FIG. 21, and therefore a description thereof will be omitted.

[0251] Fig. 31 is a flowchart illustrating the processing flow of the program according to the embodiment 9. The processing up to step S523 is the same as the processing flow of the program according to the embodiment 5 explained using Fig. 22, and therefore the explanation will be omitted.

[0252] After the gate unit 11 is unlocked in step S523, the user passes through the gate unit 11 to enter the room and operates the automatic registration machine. The automatic registration machine is connected to the information processing device 20 via the network and is controlled by the control unit 21.

[0253] The control unit 21 receives input of information required for member registration from the user (step S811). Note that the control unit 21 may display the information that the user input when applying for key information and receive additions or modifications by the user.

[0254] The user holds their IC card or smartphone over the card reader attached to the automatic registration machine. The control unit 21 acquires ID information uniquely assigned to the IC chip built into the IC card or smartphone via the card reader (step S812). The control unit 21 creates a new record in the member DB 57.

[0255] The control unit 21 issues a unique user ID to the user and records it in the user ID field. The control unit 21 records the ID information acquired in step S812 in the membership card ID field. The control unit 21 also records information in the name field and subsequent fields as appropriate (step S813).

[0256] As a result of the above, an IC card or smartphone or the like that the user already owns is registered in the member DB 57 and begins to function as the membership card 15. For users who do not wish to use an IC card or the like that they already own, the control unit 21 may issue a membership card 15 using a blank IC card stored in the automatic registration machine.

[0257] According to this embodiment, it is possible to provide an information processing system 10 that can issue a membership card 15 without human intervention.

[0258] [Variation 9-1] This modification relates to an information processing system 10 that issues a membership card 15 for a child user linked to a parent user. Explanation of parts common to the ninth embodiment will be omitted.

[0259] In this embodiment, an organization such as a company or a school becomes a parent user and manages child users such as employees or students. Figures 32 and 33 are example screens for Modification 9-1. Figure 32 is an example screen of a personal computer used by, for example, a person in the general affairs department of a company when registering employees.

[0260] The person in charge uses the screen shown in Fig. 32 to send the employee's name, email address, password, etc. to the information processing device 20 and request the issuance of key information. The information processing device 20 obtains key information for each employee from the authentication server 40 and sends it to the person in charge. The person in charge forwards the key information to the employee. Note that the key information may also be sent directly from the information processing device 20 to each employee.

[0261] Figure 33 shows an example of a screen that allows a person in the general affairs department to manage the registered information of their company's employees. Using the screen shown in Figure 33, the person in charge can search for registered employees, change registered information, delete registered information, etc.

[0262] As explained in the ninth embodiment, the employee who receives the key information goes to a designated location and operates the automatic registration machine to register the membership card 15. The automatic registration machine may be installed within the company. The control unit 21 records the user ID of each employee in association with the parent ID held by the company, and bills the parent user company for the usage fees for each employee in a lump sum.

[0263] According to this modification, a company can provide its employees with a place to work for teleworking. As part of employee benefits, a child ID may be issued to employees who request it.

[0264] [Embodiment 10] This embodiment relates to an information processing system 10 that sells various items using user IDs. Explanation of parts common to the first embodiment will be omitted.

[0265] FIG. 34 is an explanatory diagram illustrating a product locker 18 according to the tenth embodiment. The product locker 18 is installed, for example, in a common area 191. In the example shown in FIG. 34, the product locker 18 includes a total of five lockers of three sizes, large, medium, and small, and one display installed in the center. A key mechanism 13 is attached to the door of each locker, and is remotely operated by the authentication server 40.

[0266] The display shows a list of the products stored in each locker. In the example shown in FIG. 34, locker 1 contains an energy drink, locker 3 contains a lap blanket, and locker 4 contains a hand towel. Lockers 2 and 5 contain no products. The user can select the desired product, open the door, and remove the product. The control unit 21 charges the user for the product along with the usage fee for the coworking space.

[0267] 35 is an explanatory diagram illustrating the record layout of the product DB 55. The product DB 55 has an installation location field, a locker ID field, a product field, and a price field. The installation location field records the location where the product locker 18 is installed.

[0268] The locker ID field records the locker ID that is uniquely assigned to each locker. The product field records the product stored in the locker. The price field records the price of the product.

[0269] The product DB 55 has one record for each locker. The product DB 55 is stored in the auxiliary storage device 23 or an external mass storage device connected to the information processing device 20.

[0270] Fig. 36 is a flowchart illustrating the flow of processing of the program according to embodiment 10. The program of Fig. 36 is started by the user operating the mobile device 30 when the user wishes to purchase an item in the item locker 18.

[0271] The control unit 31 transmits the user ID to the information processing device 20 (step S751). The control unit 21 receives the user ID (step S821). The control unit 21 searches the entry / exit DB 56 using the received user ID as a key, and determines the installation location of a product locker 18 that is installed near the gate unit 11 through which the user recently entered / exited (step S822).

[0272] The control unit 21 searches the product DB 55 using the installation location of the product locker 18 as a key, and extracts a list of products sold in the product locker 18 (step S823). The control unit 21 transmits the extracted information to the mobile device 30 (step S824).

[0273] The control unit 31 receives the list of products (step S752). The control unit 31 displays a product selection screen, as shown in FIG. 37, on the touch panel 35 (step S753). The control unit 31 accepts the product selection by the user (step S754). The control unit 31 transmits information about the selected product or information about the locker number to the information processing device 20 (step S755). The control unit 31 ends the process.

[0274] The control unit 21 receives the information (step S825). The control unit 21 transmits to the authentication server 40 a request to unlock the door of the locker containing the product selected by the user (step S826). The control unit 41 receives the unlock request (step S551). The control unit 41 controls the key mechanism 13 to unlock the locker door (step S552). The user opens the door and takes out the product. The control unit 21 records in the product DB 55 that the product selected by the user is gone (step S827).

[0275] FIG. 37 is an example of a screen in the tenth embodiment. Using FIG. 37, an example of a product purchase screen that the control unit 31 displays on the touch panel 35 in step S753 will be described. A product selection field 681 is displayed in the center of the product purchase screen. The product selection field 681 is in the form of a pull-down menu. The user operates the product selection field 681 to select a desired product, and then taps the purchase button 682 located below the product selection field 681. This completes the product selection, and the control unit 41 unlocks the door.

[0276] According to this embodiment, it is possible to provide an information processing system 10 that performs unmanned sales of products of various shapes and sizes that are difficult to handle with a general vending machine.

[0277] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0278] 10 Information Processing Systems 11 Gate section 111 Reservation Gate 12 Entrance / exit 13 Key mechanism 14 Leader 141 First Leader 142 Second Leader 15 Membership Card 18 Merchandise Lockers 191 Common Area 192 Reservation Area 20 Information processing equipment 21 Control section 22 Main storage 23 Auxiliary storage device 24 Communications Department 251 Display section 252 Input section 29 Reading unit 30 Mobile devices 31 Control Unit 32 Main storage 33 Auxiliary storage device 34 Communications Department 35 Touch Panel 351 Display section 352 Input section 40 Authentication Server 41 Control Unit 42 Main storage 43 Auxiliary storage device 44 Communications Department 51 Entry / Exit DB 52 valid databases 53 Reservation Key DB 55 Product DB 56 Entry / Exit DB 57 Member DB 58 Billing DB 59 Reservation DB 61 Congestion status column 62 Menu column 63 Top column 64 Member list column 641 Search field 65 Reservation reception screen 651 Facilities available 652 Usage area column 653 Use date column 654 Usage time column 655 Details button 658 Schedule column 659 Decision button 66 Reservation Information 681 Product Selection Column 682 Buy Button 81 Entry Information Acquisition Unit 82 Exit information acquisition unit 83 Usage time calculation section 84 Billing Department 90 Computer 96 Portable recording media 97 Programs 98 Semiconductor Memory

Claims

1. A method of receiving a request from a registered parent user to issue key information used by a child user to register as a member, Transmitting key information issued based on the issuance request; Accepting membership registration by the child user using the transmitted key information; A membership card is issued to the child user that can be used to unlock the smart lock installed in the room, A usage fee for the use of the room by the child user is charged to the parent user. An information processing method in which processing is performed by a computer.

2. The destination of the key information issued based on the issuance request is the parent user. The information processing method according to claim 1 .

3. receiving from the parent user a request for issuing key information together with the name and email address of the child user; The destination of the key information issued based on the issuance request is the email address of the child user. The information processing method according to claim 1 .

4. The membership card has a membership card ID that can be read by a reader of the smart lock installed in the room, Before issuing a membership card to the child user, the membership card ID and the user ID issued to the child user are recorded in association with each other.

4. The information processing method according to claim 1.

5. The usage fee is calculated based on the date and time when the membership card ID is read by the reader. The information processing method according to claim 4.

6. The membership card ID is read by the reader via short-range wireless communication.

6. The information processing method according to claim 4 or 5.

7. The reader is a barcode reader, The membership card ID is displayed as a barcode.

6. The information processing method according to claim 4 or 5.

8. A request for issuing key information to be used by a child user for member registration is received from a parent user who has already registered as a member; Transmitting key information issued based on the issuance request; Accepting membership registration by the child user using the transmitted key information; issuing a membership card to the child user; Charge the parent user for the usage fee related to the child user's membership card A program that causes a computer to perform a process.

9. An information processing device having a control unit, The control unit A request for issuing key information to be used by a child user for member registration is received from a parent user who has already registered as a member, Transmitting key information issued based on the issuance request; Accepting membership registration by the child user using the transmitted key information; A membership card is issued to the child user that can be used to unlock the smart lock installed in the room, Charge the parent user for the use of the room by the child user. Information processing device.

Images