JP7750472B2 - Information processing method, program, and information processing device - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies. Published on the ABBOCC website on October 16, 2020 (https://abbocc.work/). Published and pamphlets distributed at the Aoyama Book Center main store on October 25, 2020. Published and opened at ABBOCC on November 9, 2020 (https://www.bookoffgroup.co.jp/rent/topics/2020.html#shop_20201109).

The present invention relates to an information processing method, a program, and an information processing device.

A rental space management method has been proposed in which signals are sent and received between a user's mobile terminal and a communication device installed in the rental space to manage the usage time of the rental space (Patent Document 1).

A management device has been proposed for use in shared houses, shared offices, coworking spaces, and other facilities used by multiple users, in which charges are calculated based on each user's usage history (Patent Document 2).

Japanese Patent Application Laid-Open No. 2020-021192 Japanese Patent Application Laid-Open No. 2017-228274

With the management method of Patent Document 1 and the management device of Patent Document 2, if user entry and exit are not accurately recorded, it is not possible to determine appropriate fees for each user.

In one aspect, the objective is to provide an information processing method that can charge each user an appropriate fee even if there is a omission in the user's entry/exit record.

The information processing method involves a computer executing a process in which it receives a request from a parent user who has already registered as a member to issue 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 bills the parent user for the usage fee for the child user's use of the room .

In one aspect, an information processing method can be provided that can set appropriate fees for each user even if there are gaps in the user's entry and exit records.

FIG. 1 is an explanatory diagram illustrating a configuration of an information processing system. FIG. 1 is an explanatory diagram illustrating a configuration of an information processing system. FIG. 10 is an explanatory diagram illustrating the record layout of an entry/exit DB. FIG. 10 is an explanatory diagram illustrating the record layout of a valid DB. FIG. 2 is an explanatory diagram illustrating a record layout of a member DB. FIG. 10 is an explanatory diagram illustrating the record layout of a billing DB. FIG. 10 is an explanatory diagram illustrating a calculation rule for usage time. 10 is an example of a screen displaying congestion status. 10 is an example of a management screen. 10 is an example of a management screen. 10 is a flowchart illustrating a processing flow of a program executed by an authentication server. 10 is a flowchart illustrating the flow of processing of a program for determining a congestion state. 10 is a flowchart illustrating the flow of processing by a program that executes processing for billing a fee. 10 is a flowchart illustrating the flow of processing in a daily fee calculation subroutine. 10 is a flowchart illustrating the flow of processing of a program according to a second embodiment. FIG. 11 is a functional block diagram of an information processing device according to a third embodiment. FIG. 10 is an explanatory diagram illustrating the configuration of an information processing device according to a fourth embodiment. 10 is a map of a coworking space according to the fifth embodiment. FIG. 10 is an explanatory diagram illustrating the record layout of a reservation key DB. FIG. 2 is an explanatory diagram illustrating a record layout of a reservation DB. 13 is a flowchart illustrating the flow of program processing at the time of reservation in the fifth embodiment. 13 is a flowchart illustrating the flow of program processing during unlocking in embodiment 5. This is a screen according to the fifth embodiment. This is a screen according to the fifth embodiment. This is a map of the coworking space for variant 5-1. 13 is a flowchart illustrating the flow of processing of a program according to a sixth embodiment. FIG. 20 is an explanatory diagram illustrating a record layout of a member DB according to the seventh embodiment. 13 is a flowchart illustrating the flow of processing of a program according to a seventh embodiment. FIG. 20 is an explanatory diagram illustrating the record layout of a member DB according to the eighth embodiment. 13 is a flowchart illustrating the flow of processing of a program according to an eighth embodiment. 13 is a flowchart illustrating the processing flow of a program according to a ninth embodiment. 9 is a screen example of modified example 9-1. 9 is a screen example of modified example 9-1. An explanatory diagram illustrating a product locker according to a tenth embodiment. FIG. 2 is an explanatory diagram illustrating a record layout of a product DB. 20 is a flowchart illustrating the processing flow of a program according to a tenth embodiment. 16 is a screen example according to the tenth embodiment.

[First Embodiment]
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.

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.

The gate unit 11 is located in a portion of the wall surrounding the coworking space. The gate unit 11 includes an entrance/exit 12 such as a door, a key mechanism 13 for locking and unlocking the entrance/exit 12, a first reader 141 located on the outside of the wall, and a second reader 142 located on the inside of the wall. In the following description, when there is no need to distinguish between the first reader 141 and the second reader 142, they may be referred to as readers 14.

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

The first reader 141 is an example of an entry information acquisition unit that acquires information about users who have opened the entrance/exit 12 from outside the coworking space and entered. The second reader 142 is an example of an exit information acquisition unit that acquires information about users who have opened the entrance/exit 12 from inside the coworking space and left.

The authentication server 40 is a server that controls the reader 14 and 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 makes up the authentication server 40 via the bus.

The main memory device 42 is a storage device such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), or flash memory. 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.

The auxiliary storage device 43 is a storage device such as SRAM, flash memory, a hard disk, or magnetic tape. The auxiliary storage device 43 stores the entry/exit DB 51, the validity DB 52, programs to be executed by the control unit 41, and various data required for program execution. The communication unit 44 is an interface that communicates between the authentication server 40 and the network.

The reader 14 reads the membership card ID recorded on the membership card 15 using, for example, near field communication (NFC) and transmits it to the authentication server 40. The first reader 141 and the second reader 142 are barcode readers and may read the membership card ID displayed as a barcode on the surface of the membership card 15. The membership card ID will be described later.

The control unit 41 determines whether the membership card 15 is valid. If it determines that the membership card 15 is valid, the control unit 41 controls the lock 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.

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

Figure 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 explained using Figure 2.

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.

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

The auxiliary storage device 23 is a storage device such as SRAM, flash memory, a hard disk, or magnetic tape. The auxiliary storage device 23 stores the entry/exit DB 56, the member DB 57, the 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 that communicates between the information processing device 20 and the network.

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

The information processing device 20 is a general-purpose PC, 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 PCs 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.

The portable 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 component that makes up the portable device 30 via the bus.

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

The auxiliary storage device 33 is a storage device such as SRAM, flash memory, a 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 that communicates between the mobile device 30 and the network. The touch panel 35 has a stacked configuration of a display unit 351, such as a liquid crystal display panel or an organic EL display panel, and an input unit 352.

The mobile device 30 is a general-purpose smartphone, tablet, personal computer, etc. used by each user of 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.

Figure 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, all in association with each other.

The entry/exit DB51 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.

The user ID field records the user ID corresponding to the membership card 15 that was read. 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.

Specifically, "enter" 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 a membership card 15.

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

In other words, in the information processing system 10 of this embodiment, user entry and exit may not be recorded accurately. Specifically, for the same user ID, entry may be recorded multiple times in succession, exit may be recorded multiple times in succession, exit may be recorded at the beginning of the day, or entry may be recorded at the end of the day.

Each record recorded in entry/exit DB51 is copied to entry/exit DB56 as needed through replication processing. Therefore, entry/exit DB56 has the same record layout as entry/exit DB51. Since replication processing has been used for a long time, details will not be explained here.

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

Figure 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, the membership card ID uniquely assigned to the membership card 15, the user ID uniquely assigned to the user, and whether the membership card 15 is valid or invalid.

The validity DB 52 has a membership card ID field, a user ID field, and a status field. The membership card ID field records the membership card ID uniquely assigned to the membership card 15. The membership card ID is written to the ID chip installed on the membership card 15.

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, if the user has completed the membership cancellation procedure or has not paid the required membership fee.

The validity DB 52 contains one record for each membership card 15. The control unit 41 updates the validity DB 52 as appropriate based on the registration information for the membership card 15 sent from the information processing device 20.

Figure 5 is an explanatory diagram illustrating the record layout of member DB 57. 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. 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.

The user ID field records the user ID uniquely assigned to the user. The membership card ID field records the membership card ID recorded on the membership card 15 held by the user.

The name field contains the user's name. The membership type field contains the membership type. "Pay-as-you-go" indicates a pay-as-you-go membership where the usage fee is based on the amount of time the coworking space is used. "Fixed" indicates a fixed fee membership where a fixed usage fee is paid, for example, monthly, regardless of the amount of time the coworking space is used.

Membership types are not limited to "pay-as-you-go" and "fixed rate." For example, various membership types can be set as appropriate, such as members who limit usage to daytime hours, members who have different fees for weekday daytime and evening hours, members with a limit on the number of times they can be used, members with student rates, members with group discount rates, etc.

The billing destination field records information required when billing a fee via a user's credit card, such as the credit card number, the credit card holder's name, and the credit card expiration date. The billing destination field may also record an identification ID required when 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.

The registration date field records the date of membership 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, member DB 57 records the user ID and the contract terms for that user in association with each other. An optional contract may be, for example, a contract for a mail receiving service, a contract for an address service, etc.

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

Although not shown in the figure, member DB 57 may have fields that record information such as the user's address, telephone number, email address, telephone number, SNS (Social Network Service) account, occupation, or date of birth. Member DB 57 has one record for each user ID.

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

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 deposit has been made. "Not yet" indicates that the payment has not been completed. For example, if a problem occurs, such as a previously registered credit card being invalid and billing not being possible, "Error" will be recorded.

An overview of member registration will now be provided. The control unit 21 presents a membership application form to the user via a web (World Wide Web) site, for example, and accepts the information filled out by the user. The control unit 21 may also use a chat system to obtain the information necessary for membership.

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

A user using the coworking space for the first time stops by the reception desk and presents the user ID provided 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 this in the member DB 57. The receptionist then hands the membership card 15 to the user. This completes member registration.

When recording a record for a new user in the member DB 57, the control unit 21 may also 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 hand over the corresponding membership card 15 to the user.

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

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

Therefore, there is no need for a person to be on-site at the coworking space to handle tasks such as reception procedures and entry/exit management. For example, an employee of an adjacent store could also serve as the coworking space's person in charge.

Because users can easily enter and exit the space using their membership card 15, there is no 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.

The walls surrounding the coworking space should be strong enough that users cannot easily climb over or slip through. For example, interlocking partitions just over one meter high could be used 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.

By using walls that are lower than the ceiling height and creating space between the ceiling and walls, 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.

Instead of installing gates, which are used in large facilities such as amusement parks to limit the number of people allowed through to one at a time and prevent tailgating, standard doors can be used, reducing the initial investment required for coworking spaces.

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

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

Let's explain this using a specific example. User "ID010" entered the room at time t11 and left at time t12. Their usage time was from t11 to t12. User "ID020" entered the room at time t21, left at time t22, entered at time t23, and left at time t24. Their usage time was from t21 to t24.

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.

User "ID040" entered the facility at time t41, but the exit time was not recorded. It is presumed that this user left the facility with someone else. The usage time was from t41 until closing time.

User "ID050" left the room at time t51. The entry time was not recorded. It is presumed that this user entered the room with a companion. The usage time was from opening time until t51.

If a user enters the room for the first time without having their membership card 15 scanned by the first reader 141, or if they leave the room for the last time without having their membership card 15 scanned 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 scan 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.

On the other hand, it is acceptable for users to enter and exit the space together during use, such as for toilet breaks. This allows for the provision of a coworking space that users can use in a relaxed atmosphere.

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

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 to travel, and the congestion status.

Figures 9 and 10 are examples of the management screen. Figures 9 and 10 are screens operated and viewed by the coworking space operator's staff. A menu column 62 is displayed on the left side of the screen.

Figure 9 shows an example screen with "Top" displayed in the menu column 62. The top column 63, displayed to the right of the menu column 62, displays 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, each displayed as an icon. Note that refunds are issued in irregular circumstances, such as when a user cancels membership mid-month or when an incorrect billing occurred in the previous month.

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 previous month's operating expenses and the number of active members who used the space at least once in the previous month.

Figure 10 shows an example screen with "Member List" displayed in the menu field 62. The member list field 64, displayed to the right of the menu field 62, lists the members' user IDs, names, and membership types in table format.

The person in charge can use the search field 641 located at the top of the screen to narrow down the users to be displayed in the list. If the person in charge selects the "CSV (Comma Separated Value) Download" button, the control unit 21 will generate a member list in CSV format.

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.

Although not shown in the figure, if the person in charge selects "Usage History" in menu field 62, the control unit 21 will display a list of the usage dates and usage times for each user. If the person in charge selects "Daily Usage History" in menu field 62, the control unit 21 will display a list of the usage times for each user on the date specified by the user.

If the person in charge selects "Billing Information" in menu field 62, the control unit 21 will display a list of the amounts billed to each user. If the person in charge selects "Deposit Information" in menu field 62, the control unit 21 will display a list of the amounts deposited by each user. If the person in charge selects "Refund Information" in menu field 62, the control unit 21 will display a list of the amounts refunded to each user.

Note 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 operating the input unit 252 as appropriate. The control unit 21 displays information on the display unit 251 in response to the user's operation.

Figure 11 is a flowchart explaining the processing flow of the program executed by the authentication server 40. The program in Figure 11 is executed during business hours of the coworking system.

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 (step S502). Note that 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.

If it is determined that the information 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.

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

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.

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 "out" in the entry/exit field. Therefore, either "in" or "out" is recorded in the entry/exit field.

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

If it is determined that the processing should not be terminated (NO in step S506), the control unit 41 returns to step S501. If it is determined that the processing should be terminated (YES in step S506), the control unit 41 terminates the processing.

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

Figure 12 is a flowchart explaining the processing flow of the program that determines the congestion level. The program in Figure 12 is started before the coworking space opens for business and runs during business hours.

The control unit 21 sets the variable "number of people" to its 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).

If it is determined that "enter" has been 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" has not been 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.

The control unit 21 makes a determination by comparing the variable "number of people" with a predetermined first threshold and a predetermined second threshold (step S606). The first threshold is, for example, a value that is approximately 75% of the capacity of the coworking space. The second threshold is, for example, a value that is approximately 90% of the capacity of the coworking space.

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 situation 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 (greater than or equal to the first threshold and less than the second threshold in step S606), the control unit 21 determines that the congestion situation of the coworking space is "slightly crowded" (step S608). If the variable "number of people" is equal to or greater than the second threshold (greater than or equal to the second threshold in step S606), the control unit 21 determines that the congestion situation of the coworking space is "full" (step S609).

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 the web page. For example, Figure 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.

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

Figure 13 is a flowchart explaining the processing flow of a program that executes the billing process. The program in Figure 13 is executed, for example, during monthly billing processing. The program in Figure 13 may also be executed when specified by a person in charge at the operating company.

The control unit 21 selects the user ID of the member to be billed (step S621). The control unit 21 may also 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 records. 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).

If it is determined that the user is not a pay-as-you-go 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, the specified fixed fee in the billing amount field, and "Not yet" in the settlement field (step S623). Note that the fixed fee recorded in the billing amount field also includes the fees for paid options to which the user has subscribed.

If it is determined that the user is a pay-as-you-go member (YES in step S622), the control unit 21 launches a daily fee calculation subroutine (step S624). The daily fee calculation subroutine 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.

The control unit 21 determines whether processing for the billing period has ended (step S625). If it determines that processing has not ended (NO in step S625), the control unit 21 returns to step S624. If it determines that 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 fees for paid options subscribed to by the user (step S626).

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).

After step S623 or step S627 is completed, the control unit 21 performs billing processing (step S628). Specifically, the control unit 21 searches the member DB 57 using the user ID acquired in step S621 as a key to extract a record. The control unit 21 then 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.

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 functions of the payment processing unit of this embodiment.

The control unit 21 may process billing for the fixed fee of a user on a fixed fee system and the fee for a paid option separately, without adding them together. The control unit 21 may process billing for the usage fee of a user on a pay-as-you-go system and the fee for a paid option separately, without adding them together.

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

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

Figure 14 is a flowchart explaining the processing flow of the daily fee calculation subroutine. The daily fee calculation subroutine calculates a daily fee based on the data recorded in the entry/exit DB 56.

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

If it is determined that this indicates entry (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 this does not indicate entry (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).

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

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

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

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

The control unit 21 associates the user ID, date, and daily fee, and temporarily records them in the auxiliary storage device 23 or main storage device 22 (step S650). The control unit 21 may also record the fee for each date in a specified database. The control unit 21 then terminates processing.

The entrance/exit 12 may be an automatic door. In this case, the key mechanism 13 controls the opening and closing of the automatic door instead of locking and unlocking it. 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.

A user ID may be recorded on the membership card 15. The first reader 141 and 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.

The mobile device 30 owned by the user may also serve as the membership card 15. For example, the serial number registered on 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.

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

The program described using Figure 12 may have a function that allows the manager to instruct the administrator to correct the number of users. For example, when the administrator enters the room for cleaning, etc., they can count the number of users present and correct the variable "number of users." This makes it possible to create a program that corrects errors caused by tailgating and displays an appropriate level of congestion.

Instead of using the program described using Figure 12, the congestion level may be determined based on images captured by a camera installed within the coworking space. Technology for determining the number of people captured from an image is well known, so a detailed explanation will be omitted. Installing a camera within the coworking space can also be expected to have the effect of curbing inappropriate behavior by users.

According to this embodiment, an information processing system 10 can be provided that charges each user an appropriate fee even when tailgating occurs. According to this embodiment, an information processing system 10 can be provided that, with a relatively low initial investment, utilizes unused space as a paid coworking space, thereby generating revenue.

Users do not need to worry about being tailgated except when they first enter and when they finally leave. This means that a coworking space with a peaceful atmosphere can be provided, where it is acceptable to observe good manners such as holding the door when entering or leaving.

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

[Modification 1-1]
In step S628 described with reference to FIG. 13 , the control unit 21 issues an invoice to a predetermined address 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.

The control unit 21 may issue an estimate instead of an invoice. Even in companies that make payments after internal approval based on an estimate, employee usage fees can be expensed in accordance with internal company rules.

The control unit 21 may automatically issue a receipt after payment for the invoice has been made. Automatic confirmation of invoices and payments via bank accounts or cloud services, etc., is a conventional practice, so further details will not be provided.

[Modification 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, the control unit 21 sets an hourly fee based on the time of entry determined in step S643 in the daily fee calculation subroutine described with reference to FIG. 14. 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.

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

Users on a pay-as-you-go plan can use the coworking space with peace of mind, as the usage fee confirmed upon entry applies throughout the 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 more users, it is possible to level out usage of the coworking space.

The control unit 21 may use different fees for each time period during which the user stays. A specific example will be given below. Let's take the example of a case where the morning usage fee is set at 200 yen per hour, the afternoon usage fee at 250 yen per hour, and the night usage fee after 6:00 PM at 300 yen per hour.

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 two hours in the 200 yen time slot and three 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.

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

Figure 15 is a flowchart explaining the processing flow of the program in embodiment 2. The program in Figure 15 is executed each time a user leaves the room, or at night on the day the user uses the coworking space.

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).

If it is determined that the user is a pay-as-you-go member (YES in step S662), the control unit 21 launches a daily fee calculation subroutine (step S663). The daily fee calculation subroutine is the same as the subroutine described using Figure 14.

The control unit 21 determines whether processing for the billing period has ended (step S664). If it determines that processing has not ended (NO in step S664), the control unit 21 returns to step S663. If it determines that 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).

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-rate charge. The threshold may also be a charge 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).

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 membership type change procedure.

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

If it is determined that the user is not a pay-as-you-go member, i.e., a fixed-fee member (NO in step S662), if it is determined that the number 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 processing (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 processing.

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

This embodiment provides an information processing system 10 that notifies users who are pay-as-you-go members when their fees exceed a fixed fee. By preventing users from being charged unexpected fees, an information processing system 10 can be provided that improves customer satisfaction.

[Third embodiment]
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.

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, to the user's credit card.

[Fourth embodiment]
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 the present 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.

The computer 90 includes the aforementioned control unit 21, main memory device 22, auxiliary memory device 23, communication unit 24, display unit 251, input unit 252, and bus, as well as a reading unit 29.

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.

The program 97 is installed on the computer 90 as a control program, and is loaded into the main memory device 22 and executed. This achieves the information processing device 20 described in embodiment 1.

Fifth Embodiment
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.

Figure 18 is a map of a coworking space in embodiment 5. The coworking space in this embodiment is surrounded by walls or partitions on all four sides, and has a gate unit 11 located in one location. 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 location.

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

It is desirable that the reservation gate unit 111 be designed so that, even when locked, it does not prevent users within the reservation target area 192 from leaving the reservation target area 192. This can prevent accidents in which users become trapped within the reservation target area 192.

The reservation target area 192 may be, for example, a private work booth used by a user who wants to concentrate on work. The reservation target area 192 may also be a conference room where multiple users can gather. The reservation target area 192 may also be a conference booth for web conferences. The reservation target area 192 may also be a recreation area where users can play games, exercise, etc. The uses and facilities of the two reservation target areas 192 may be different.

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).

Note that the map shown in Figure 18 is an example. The overall shape of the room, the location of the gate unit 11, the number and arrangement of reservation target areas 192, etc. are not limited to those shown in Figure 18.

In this embodiment, the user makes a reservation for the reservation target area 192 using the mobile device 30. When the reservation is confirmed, key information for unlocking the reservation gate unit 111 of the reservation target area 192 at the reserved time is sent to the user, for example, by email or SMS. In the following explanation, we will use as an example a case where the key information is an unlocking URL that can be accessed to send an unlocking request to the control unit 41.

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.

The authentication server 40 unlocks the specified 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, etc.

Figure 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 section 111 of the reservation target area 192 can also be identified.

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 the 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.

The reservation key DB 53 contains one record for each reservation. The reservation key DB 53 is stored in the auxiliary storage device 43 or an external large-capacity storage device connected to the authentication server 40.

Figure 20 is an explanatory diagram illustrating the record layout of reservation DB 59. Reservation DB 59 is a database that records location IDs, reservation times, user IDs, and key information in association with each other. 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.

The location ID field records the location ID. The start field and end field record the start and end times 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.

Reservation DB 59 has one record for each reservation. Reservation DB 59 is stored in the auxiliary storage device 23 or an external large-capacity storage device connected to the information processing device 20. The control unit 21 and control unit 41 use a replication process to synchronize each record recorded in the reservation key DB 53 with each record recorded in the reservation DB 59, excluding the user ID field. Replication processes have been used for some time, so details will not be explained here.

Figure 21 is a flowchart explaining the flow of program processing when making a reservation in embodiment 5. The program in Figure 21 is launched by the user operating the mobile device 30 when making a reservation for the reservation target area 192.

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 the reservation reception screen 65 (see Figure 23) on the display unit 351 (step S712). As described below, the reservation reception screen 65 displays time slots for which reservations have already been made.

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).

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 to unlock the reservation gate unit 111 corresponding to the reservation target area 192 received in step S671 during the reservation target time period (step S672).

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

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).

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).

The control unit 21 sends the key information to the mobile device 30, for example, via email or SMS (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). The mobile device 30 then terminates processing.

Figure 22 is a flowchart explaining the processing flow of the program when unlocking in embodiment 5. The program in Figure 21 is started by the user operating the mobile device 30 when unlocking the reservation target area 192.

The control unit 31 displays the key information received in step S715 of the flowchart described using Figure 21 on the touch panel 35 (step S721). As mentioned above, the key information will be described as an unlocking URL.

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

The user operates the input unit 352 to tap the unlock button. The control unit 31 accepts the user's operation (step S722). The key information displayed in step S721 is sent to the authentication server 40 via the web server that displayed the unlock button.

The control unit 41 receives the key information (step S521). The control unit 41 determines whether authentication based on the received key information was 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 was successful. If the record cannot be extracted or is not within the reservation time slot, the control unit 41 determines that authentication was not successful.

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). This allows the user to enter the reserved reservation target area 192.

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.

If it is determined that authentication was not 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 also display on a display or the like attached to the reservation gate unit 111 that authentication was not successful. The control unit 41 may also notify the administrator of the coworking space or the like that an unauthorized request has been made.

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). The control unit 31 then terminates processing.

Figure 23 shows a screen in embodiment 5. The control unit 31 displays the reservation acceptance screen 65 shown in Figure 23 in step S712 of the flowchart described using Figure 21. 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 a confirm button 659 displayed below the schedule field 658.

The user operates the usage date field 653 to specify a date. The user operates the usage facility field 651 to specify the facility to use. Note that if the user has only one facility available for use, the usage facility field 651 does not need to be displayed. The control unit 31 displays the reservation status for the reservation target areas 192 set in the usage facility field 651 on the date specified in the usage date field 653 in the schedule field 658. "Booth 1" and "Booth 2" in Figure 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.

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 OK 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).

Figure 24 shows a screen in embodiment 5. 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 Figure 24. The reservation information screen includes a reservation information field 66. The user can check the schedule for which they have made a reservation by looking at the reservation information field 66. When the user selects the details button 655, the control unit 31 may also display key information corresponding to the reservation. The user can search for the schedule for which they have made a reservation using the search field displayed above the reservation information field 66.

This embodiment provides 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 has the desired facilities, etc.

By providing a reservation gate unit 111 in the reservation target area 192, it is possible to prevent outsiders from inadvertently entering the reservation target area 192. This makes it possible to provide a reservation target area 192 that can be used for confidential meetings or video conferences. Furthermore, by sending key information to the user via email or SMS, the user can distribute the key information to participants in the meeting as appropriate.

With regard to 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 Figure 24 indicates the amount of the additional fee incurred for each reservation. The additional fee may vary depending on the time of reservation or use. For example, a discounted fee may be offered to users who make a reservation immediately before use.

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 embodiment 1 and bills the user.

The reservation target area 192 may be located in a location that users can reach without passing through the gate unit 11. Users can easily invite people to meetings held in the reservation target area 192, even if they are not registered users of the coworking space.

Instead of providing key information to invited guests, users may provide their phone number, etc. When a guest arrives in front of the reservation gate unit 111, they call the inviting user to notify them of their arrival. The user operates the mobile device 30 to use the key information to unlock the reservation gate unit 111. In this embodiment, since the lock can be unlocked using the key information without having to go to the reservation gate unit 111, there is no need to explain to the guest how to unlock the reservation gate unit 111.

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

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 charges the usage fee for the reservation target area 192 via the payment terminal. After the settlement is complete, the control unit 41 proceeds to step S523 and unlocks the reservation gate unit 111. As a result, an information processing system 10 can be provided that settles the fee each time the reservation target area 192 is used.

The key information may be a two-dimensional or one-dimensional barcode that unlocks the reservation gate unit 111 when read by a camera attached to the reservation gate unit 111. If 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 over the camera attached to the reservation gate unit 111. In step S521, the control unit 41 acquires the barcode via the network.

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. If 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 using the numeric keypad attached to the reservation gate unit 111. In step S521, the control unit 41 obtains the key code input via the network.

[Modification 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 having to perform 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 with reference to FIG. 24.

Note that there may be a mixture of reservation target areas 192 with reservation gate sections 111 and reservation target areas 192 without reservation gate sections 111.

Sixth Embodiment
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.

Figure 26 is a flowchart explaining the processing flow of the program in embodiment 6. The control unit 21 continues to execute the program in Figure 26 in parallel for each reservation target area 192 during business hours.

The control unit 21 searches the reservation DB 59 to determine whether the reservation target area 192 has not been reserved, i.e., is 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 located in the coworking space and on a web page related to the coworking space (step S682).

The notification could be a message such as, "Web Conference Booth A can be used from 3:00 PM to 4:00 PM at no additional charge. Use is on a first-come, first-served basis. Please come directly to Web Conference Booth A."

The control unit 21 waits until a time when no reservations have been made arrives (step S683). Specifically, for example, if the above message is displayed, the control unit 21 will wait until 3:00 p.m. The control unit 21 sends 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).

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 confirmation is not possible, the control unit 41 ignores the unlock request received in step S531.

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

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

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 sends a request to the authentication server 40 to lock the reservation gate unit 111 for the reservation target area 192 (step S687).

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, it 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).

If it is determined that the space is not vacant (NO in step S681), or after step S687 is completed, the control unit 21 determines whether to terminate the process (step S689). For example, if the coworking space's closing time is approaching, the control unit 21 determines to terminate the process.

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

According to this embodiment, an information processing system 10 can be provided that can effectively utilize reservation target areas 192 that have not yet been reserved. By allowing users to experience using the reservation target areas 192 at no additional charge, it is possible to provide an information processing system 10 that allows users to experience the benefits of the reservation target areas 192 and encourages future use.

Seventh Embodiment
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.

Figure 27 is an explanatory diagram illustrating the record layout of the member DB 57 in embodiment 7. The member DB 57 in this embodiment has a configuration in which a ticket field has been added to the member DB 57 in embodiment 1 described using Figure 5. The ticket field records the number of tickets held by each user.

The "Ticket" in the Membership Type field indicates a ticket-based membership type. Ticket-based members purchase tickets online by operating their 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.

Figure 28 is a flowchart illustrating the processing flow of the program in embodiment 7. The program in Figure 28 is executed in place of the program described using Figure 11.

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 (step S502). Note that 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.

If it is determined to be valid (YES in step S502), the control unit 41 sends 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).

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

If it is determined that the user is not a ticket-based member, i.e., a pay-as-you-go or fixed-rate member (NO in step S692), the control unit 21 sends a message to the authentication server 40 to unlock the gate unit 11 (step S693).

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 minus the required number of tickets (step S694).

In addition, if a user who has entered legally once is allowed to freely enter and exit the gate unit 11 on the same day, the control unit 21 will only update the data in the ticket field if this is the user's first entry on the day.

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.

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 determines 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 user's entry and exit in the entry and exit DB 51 (step S505).

If it is determined that the setting is not valid (NO in step S502), or if it is determined that the setting should not 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.

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

If it is determined that the processing should not be terminated (NO in step S506), the control unit 41 returns to step S501. If it is determined that the processing should be terminated (YES in step S506), the control unit 41 terminates the processing.

After step S695 is completed, the control unit 21 transmits the number of tickets held 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 corresponding to the number of tickets on the touch panel 35 (step S732).

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."

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

A user who is short of tickets can purchase tickets online using their mobile device 30, then have the reader 14 read their membership card 15 again, unlocking the gate 11 and allowing them to enter.

This embodiment makes it possible to provide an information processing system 10 that can accommodate users who wish to pay only for what they use. For example, it is possible to provide an information processing system 10 that can carry out sales promotions by offering three tickets as a gift to newly registered users.

The number of tickets required for one use may be set to vary depending on the facility used. Users on a pay-as-you-go or fixed-rate plan may be able to use the tickets described in this embodiment when using the reservation target area 192 described in embodiment 5.

Eighth Embodiment
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.

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

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 reaches zero, the facility's gate unit 11 will not be unlocked using that user's membership card 15. The control unit 21 sets the remaining number of times field to its initial value at a predetermined frequency, such as once a day or once a week. Note that the initial value may be different for each user.

Figure 30 is a flowchart explaining the processing flow of the program in embodiment 8. The processing up to step S691 is the same as the processing flow in embodiment 7 explained using Figure 28, so explanation will be omitted. The control unit 21 determines whether the user's remaining number of times is zero (step S801).

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 contains "0," the control unit 21 determines that the remaining number of times for that user is zero.

If it is determined that the remaining number of times is not zero, i.e., that the member is eligible to 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 sends 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 sends a message to the authentication server 40 indicating that the gate unit 11 will not be unlocked (step S804).

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 embodiment 7 described using Figure 28, and therefore will not be described again.

The control unit 21 transmits to the mobile device 30 a message indicating that the remaining number of times is zero (step S805). The mobile device 30 receives the message indicating 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).

For example, if the remaining number of uses is initialized once a day, the control unit 31 will display "You have exceeded the number of uses for today. You will not be able to use the service again today." Similarly, if the remaining number of uses is initialized once a week, the control unit 31 will display "You have exceeded the number of uses for this week. Please wait until next Monday."

For users who will be able to 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 would like to use the service again, please apply to change to a fixed membership."

The control unit 31 may display a button to purchase tickets online along with a message saying, "You have exceeded the number of uses for today. Additional tickets can be purchased for 200 yen per use." When the user purchases a ticket, the control unit 21 adds the number of tickets purchased to the remaining number of times field.

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

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

Ninth Embodiment
This embodiment relates to an information processing system 10 that can issue a membership card 15 unattended. Explanation of parts common to the first embodiment will be omitted.

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 guest user key information issued online and operate the automatic registration machine themselves.

In this embodiment, the reservation gate unit 111 described in embodiment 5 is installed at the entrance to the room. The user receives the key information described in embodiment 5 online. The issuance of the key information is the same as the process described in embodiment 5 using Figure 21, so a detailed description will be omitted.

Figure 31 is a flowchart explaining the processing flow of the program in embodiment 9. The processing up to step S523 is the same as the processing flow of the program in embodiment 5 explained using Figure 22, so explanation will be omitted.

After the gate unit 11 is unlocked in step S523, the user passes through the gate unit 11, enters 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.

The control unit 21 accepts input of the information required for member registration from the user (step S811). Note that the control unit 21 may also display the information entered by the user when applying for key information and accept additions or modifications by the user.

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

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).

As a result of the above, the IC card or smartphone etc. that the user already owns is registered in the member DB 57 and begins to function as the membership card 15. Note that for users who do not wish to use an IC card etc. 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.

This embodiment provides an information processing system 10 that can issue membership cards 15 without human intervention.

[Modification 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.

In this embodiment, an organization such as a company or school serves as the parent user and manages child users such as employees or students. Figures 32 and 33 are example screens for variant example 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.

Using the screen shown in Figure 32, the person in charge sends the employee's name, email address, password, etc. to the information processing device 20 and requests 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.

Figure 33 shows an example of a screen that allows a general affairs department employee to manage the registered information of their company's employees. Using the screen shown in Figure 33, the employee can search for registered employees, change registered information, delete registered information, and more.

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 each employee's user ID in association with a parent ID held by the company, and bills the parent user company for the usage fees for each employee in a lump sum.

According to this modified example, companies can provide their employees with a workspace for teleworking. As part of employee benefits, child IDs may be issued to employees who request them.

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

Figure 34 is an explanatory diagram illustrating a product locker 18 according to embodiment 10. The product locker 18 is installed, for example, in a common area 191. In the example shown in Figure 34, the product locker 18 comprises 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.

The display shows a list of the products stored in each locker. In the example shown in Figure 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 coworking space usage fee.

Figure 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.

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.

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 large-capacity storage device connected to the information processing device 20.

Figure 36 is a flowchart explaining the processing flow of the program in embodiment 10. The program in Figure 36 is launched by the user operating the mobile device 30 when the user wishes to purchase an item in the item locker 18.

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 location of a product locker 18 located near the gate unit 11 through which the user recently entered or exited (step S822).

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 being sold in that product locker 18 (step S823). The control unit 21 transmits the extracted information to the mobile device 30 (step S824).

The control unit 31 receives the list of products (step S752). The control unit 31 displays a product selection screen, such as that shown in FIG. 37, on the touch panel 35 (step S753). The control unit 31 accepts the user's selection of a product (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.

The control unit 21 receives the information (step S825). The control unit 21 sends an unlock request to the authentication server 40 for 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 removes the product. The control unit 21 records in the product DB 55 that the product selected by the user is no longer available (step S827).

Figure 37 is an example screen in embodiment 10. Using Figure 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 the 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.

This embodiment provides an information processing system 10 that performs unmanned sales of products of various shapes and sizes that are difficult to handle with ordinary vending machines.

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 to be considered as illustrative in all respects and not restrictive. 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.

REFERENCE SIGNS LIST 10 Information processing system 11 Gate section 111 Reservation gate section 12 Entrance/exit 13 Key mechanism 14 Reader 141 First reader 142 Second reader 15 Membership card 18 Product locker 191 Common area 192 Reservation target area 20 Information processing device 21 Control section 22 Main memory device 23 Auxiliary memory device 24 Communication section 251 Display section 252 Input section 29 Reading section 30 Portable device 31 Control section 32 Main memory device 33 Auxiliary memory device 34 Communication section 35 Touch panel 351 Display section 352 Input section 40 Authentication server 41 Control section 42 Main memory device 43 Auxiliary memory device 44 Communication section 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 Occupancy status field 62 Menu field 63 Top field 64 Member list field 641 Search field 65 Reservation reception screen 651 Facility to be used field 652 Area to be used field 653 Date of use field 654 Time of use field 655 Details button 658 Schedule field 659 Confirm button 66 Reservation information field 681 Product selection field 682 Purchase button 81 Room entry information acquisition unit 82 Room exit information acquisition unit 83 Usage time calculation unit 84 Billing processing unit 90 Computer 96 Portable recording medium 97 Program 98 Semiconductor memory

Claims (9)

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,
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. The destination of the key information issued based on the issuance request is the parent user.
The information processing method according to claim 1 . receiving a request for issuing key information from the parent user along 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 . 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. 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. 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. 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. 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. 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.