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

Description

Application of Article 30, Paragraph 2 of the Patent Act Released on October 16, 2020 on the ABBOCC website (https://abbocc.work/) October 25, 2020, Aoyama Book Center Main Store Distribute and publish pamphlets 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 apparatus.

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

In shared houses, shared offices, co-working spaces, and the like used by a plurality of users, there has been proposed a management device that charges according to the usage record of each user (Patent Document 2).

JP 2020-021192 A JP 2017-228274 A

In the management method of Patent Document 1 and the management device of Patent Document 2, appropriate fees for each user cannot be determined if the entry and exit of users are not recorded accurately.

An object of one aspect of the present invention is to provide an information processing method and the like capable of billing each user for an appropriate fee even if there is an omission in the record of user entry and exit.

The information processing method acquires the user ID and room entry time of the user who unlocked the smart lock from outside the room, acquires the user ID and room exit time of the user who unlocked the smart lock from inside the room, and obtains each date When a plurality of room entry times or room exit times are obtained for each of the user IDs, the usage time , which is the time from the first entry time of the day to the last exit time of the same day, is calculated, The computer executes a process of billing the user's usage fee calculated based on the user ID and the usage time through the user's credit card.

In one aspect, it is possible to provide an information processing method or the like that can determine an appropriate charge for each user even if there is an omission in the records of user entry and exit.

It is an explanatory view explaining composition of an information processing system. It is an explanatory view explaining composition of an information processing system. FIG. 4 is an explanatory diagram for explaining a record layout of an entry/exit DB; FIG. 10 is an explanatory diagram for explaining a record layout of an effective DB; It is an explanatory view explaining a record layout of member DB. FIG. 10 is an explanatory diagram for explaining a record layout of an invoice DB; FIG. FIG. 4 is an explanatory diagram for explaining usage time calculation rules; It is an example of a screen displaying congestion conditions. It is a screen example of a management screen. It is a screen example of a management screen. 4 is a flowchart for explaining the flow of processing of a program executed by an authentication server; It is a flow chart explaining a flow of processing of a program which judges a congestion situation. FIG. 10 is a flow chart for explaining the flow of processing of a program that executes processing for billing; FIG. FIG. 11 is a flow chart for explaining the processing flow of a subroutine for daily charge calculation; FIG. 10 is a flowchart for explaining the flow of processing of a program according to Embodiment 2; 11 is a functional block diagram of an information processing device according to Embodiment 3; FIG. FIG. 11 is an explanatory diagram for explaining the configuration of an information processing device according to a fourth embodiment; 10 is a map of a coworking space according to Embodiment 5. FIG. FIG. 4 is an explanatory diagram for explaining a record layout of a reservation key DB; It is an explanatory view explaining a record layout of reservation DB. FIG. 14 is a flow chart for explaining the flow of program processing at the time of reservation according to Embodiment 5. FIG. FIG. 12 is a flow chart for explaining the processing flow of a program when unlocking according to Embodiment 5. FIG. 10 is a screen according to Embodiment 5. FIG. 10 is a screen according to Embodiment 5. FIG. It is a map of the coworking space of modification 5-1. FIG. 14 is a flowchart for explaining the flow of processing of a program according to Embodiment 6; FIG. FIG. 21 is an explanatory diagram illustrating a record layout of a member DB according to Embodiment 7; FIG. 21 is a flow chart for explaining the flow of processing of a program according to Embodiment 7; FIG. FIG. 23 is an explanatory diagram illustrating a record layout of a member DB according to Embodiment 8; FIG. 22 is a flowchart for explaining the flow of processing of a program of Embodiment 8; FIG. FIG. 22 is a flowchart for explaining the flow of processing of a program according to Embodiment 9; FIG. It is an example of a screen of modification 9-1. It is an example of a screen of modification 9-1. FIG. 22 is an explanatory diagram for explaining a product locker according to Embodiment 10; It is an explanatory view explaining a record layout of goods DB. FIG. 22 is a flow chart for explaining the flow of processing of a program according to the tenth embodiment; FIG. FIG. 11 is a screen example of the tenth embodiment. FIG.

[Embodiment 1]
FIG. 1 is an explanatory diagram for explaining the configuration of an information processing system 10. As shown in FIG. In this embodiment, an information processing system 10 that manages a so-called coworking space will be described as an example. The coworking space of this embodiment is an example of a room. A coworking space according to the present embodiment is a room suitable for deskwork such as work, study, or reading, and is equipped with desks and chairs that can be used by a plurality of users. Coworking spaces are 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 section 11 and a membership card 15 . The membership card 15 is possessed by each user who uses the coworking space.

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

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

The first reader 141 is an example of a room entry information acquisition unit that acquires information about users who have entered the coworking space by opening the doorway 12 from outside. The second reader 142 is an example of a room exit information acquisition unit that acquires information about users who have left the coworking space by opening the doorway 12 from inside.

Authentication server 40 is a server that controls reader 14 and key mechanism 13 via a network. The authentication server 40 includes a control section 41, a main storage device 42, an auxiliary storage device 43, a communication section 44 and a bus. The control unit 41 is an arithmetic control device that executes the program of this embodiment. One or a plurality of CPUs (Central Processing Units), multi-core CPUs, or the like is used for the control unit 41 . The control unit 41 is connected to each hardware unit constituting the authentication server 40 via a bus.

The main storage device 42 is a storage device such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), flash memory, or the like. The main storage device 42 temporarily stores information necessary during the processing performed by the control unit 41 and the program being executed by the control unit 41 .

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

The reader 14 reads the membership card ID recorded in the membership card 15 using, for example, NFC (Near field communication), 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 in 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. When determining that the membership card 15 is valid, the control unit 41 controls the key mechanism 13 to unlock the doorway 12 . As described above, the user who causes the reader 14 to read the membership card 15 can pass through the entrance/exit 12 .

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

FIG. 2 is an explanatory diagram for explaining the configuration of the information processing system 10. As shown in FIG. The configurations of the information processing device 20 and the mobile device 30 will be described using FIG.

The information processing device 20 includes a control section 21, a main storage device 22, an auxiliary storage device 23, a communication section 24, a display section 251, an input section 252 and a bus. The control unit 21 is an arithmetic control device that executes the program of this embodiment. One or a plurality of CPUs, a multi-core CPU, or the like is used for the control unit 21 . The control unit 21 is connected to each hardware unit forming the information processing apparatus 20 via a bus.

The main storage device 22 is a storage device such as SRAM, DRAM, flash memory, or the like. The main storage device 22 temporarily stores information necessary during the process performed by the control unit 21 and the program being executed by the control unit 21 .

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

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

The information processing device 20 is a general-purpose personal computer, a smartphone, a tablet, a large computer, or a virtual machine that operates on a large computer used by a coworking space operator. The information processing apparatus 20 may be configured by hardware such as a plurality of personal computers or large computers that perform distributed processing. The information processing device 20 may be configured by a cloud computing system. The information processing device 20 may be hardware dedicated to the editing support processing of the present embodiment.

The mobile device 30 includes a control section 31, a main memory device 32, an auxiliary memory device 33, a communication section 24, a touch panel 35 and a bus. The control unit 31 is an arithmetic control device that executes the program of this embodiment. One or a plurality of CPUs, a multi-core CPU, or the like is used for the control unit 31 . The control unit 31 is connected to each hardware unit forming the mobile device 30 via a bus.

The main storage device 32 is a storage device such as SRAM, DRAM, flash memory, or the like. The main storage device 32 temporarily stores information necessary during the process performed by the control unit 31 and the program being executed by the control unit 31 .

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

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

FIG. 3 is an explanatory diagram for explaining the record layout of the entry/exit DB 51. As shown in FIG. The entrance/exit DB 51 is a DB that records the location of the coworking space, the date and time when the reader 14 reads the membership card 15, the user ID corresponding to the membership card 15, and the entry/exit distinction of the room in association with each other.

The entrance/exit DB 51 has a location field, a date/time field, a user ID field, and an entrance/exit field. The datetime 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 when the reader 14 reads the membership card 15 . The time field records the time when the reader 14 reads the membership card 15 .

A user ID corresponding to the read membership card 15 is recorded in the user ID field. In the entry/exit field, entry/exit of the user is recorded. The entry/exit is determined by which of the first reader 141 and the second reader 142 reads the membership card 15 .

Specifically, "enter" indicates that the user entered the coworking space by having the first reader 141 read the membership card 15 from outside the coworking space, and "exit" indicates that the user entered the coworking space. The membership card 15 is read by the second reader 142 from inside to indicate that the user has left the coworking space. The entrance/exit DB 51 has one record for one reading of the membership card 15 .

In addition to the user who opened the door, other users may enter and exit together, so-called tailgating may occur. It is difficult to prevent tailgating when a general door is used because there is a manner of holding the door open so that the following person can easily pass. Information about users entering and exiting the room by tailgating is not recorded in the entry/exit DB 51 .

In other words, in the information processing system 10 of the present embodiment, there are cases where the entry and exit of the user are not recorded accurately. Specifically, for the same user ID, when entering the room is recorded multiple times in succession, when leaving the room is recorded multiple times in succession, when leaving the room is recorded at the beginning of the day, and , entry may be recorded at the end of the day.

Each record recorded in the entrance/exit DB 51 is copied to the entrance/exit DB 56 at any time by replication processing. Accordingly, the room entrance/exit DB 56 has the same record layout as the room entrance/exit DB 51 . Since the replication process has been used conventionally, the detailed explanation is omitted.

A coworking space operator may install an information processing device 20 in each region, for example, and operate the coworking space. A plurality of operators may each install the information processing device 20 . In such a case, records relating to the co-working space to be managed are extracted and copied to the entrance/exit DB 56 during the replication process.

FIG. 4 is an explanatory diagram for explaining the record layout of the valid DB 52. As shown in FIG. The validity DB 52 is a DB in which 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 are recorded in association with each other.

Valid DB 52 has a membership card ID field, a user ID field and a status field. A membership card ID uniquely assigned to the membership card 15 is recorded in the membership card ID field. A membership card ID is written in an ID chip mounted on the membership card 15 .

A user ID uniquely assigned to a user who uses the coworking space is recorded in the user ID field. The status field records whether the membership card 15 is valid or invalid. A case where the membership card 15 is invalid is, for example, a case where the user has performed a withdrawal procedure, or a case where the user has not paid a predetermined membership fee.

The valid DB 52 has one record for one membership card 15 . The control unit 41 appropriately updates the valid DB 52 based on the registration information of the membership card 15 transmitted from the information processing device 20 .

FIG. 5 is an explanatory diagram for explaining the record layout of the member DB 57. As shown in FIG. The member DB 57 is a DB in which user IDs, membership card IDs, names, membership types, billing destinations, registration dates, and options are associated and recorded. The member DB 57 has a user ID field, a membership card ID field, a name field, a membership type field, a billing address field, a registration date field, and an option field.

A user ID uniquely assigned to the user is recorded in the user ID field. A membership card ID recorded in the membership card 15 owned by the user is recorded in the membership card ID field.

The user's name is registered in the name field. A member type is registered in the member type field. “Pay-as-you-go” indicates a pay-as-you-go member who pays the usage fee according to the time the coworking space is used. “Fixed” indicates a fixed-fee member who pays a fixed usage fee, for example, every month, regardless of the time the coworking space is used.

Note that the membership type is not limited to the two types of "rate" and "fixed". For example, members who limit usage time to daytime, members who charge different rates for daytime and nighttime on weekdays, members who set an upper limit on the number of times of use, members who pay student rates, members who pay group discount rates, etc. Can be set.

In the billing field, information necessary for billing through the user's credit card, such as credit card number, credit card holder name, credit card expiration date, etc., is recorded. The billing destination field may record an identification ID that is necessary when collecting fees from a member via a payment agency service. By using the payment agency service, it is possible to avoid managing important information such as credit card numbers in the information processing system 10 .

The date of registration is recorded in the registration date field. An option contract is recorded in the option field. For example, "locker" indicates that an option contract for personal lockers has been concluded. That is, the member DB 57 records the user ID and the contract conditions of the user in association with each other. The option contract may be, for example, a mail receiving service contract, an address use service contract, or the like.

The billing method is not limited to credit cards. For example, the billing field may contain information necessary for billing through a bank account, such as bank account number and account holder. In the billing destination field, information necessary for billing charges via electronic money, such as electronic money authentication information, may be recorded.

Although not shown, the member DB 57 may have fields recording information such as the user's address, telephone number, email address, telephone number, SNS (Social Network Service) account, occupation, date of birth, and the like. The member DB 57 has one record for one user ID.

FIG. 6 is an explanatory diagram for explaining the record layout of the billing DB 58. As shown in FIG. The billing DB 58 is a DB that records billing months, user IDs, billing amounts, and payment statuses in association with each other. The billing DB 58 has a billing month field, a user ID field, a billing amount field and a settlement field.

The billing month field records the billing month. A user ID is recorded in the user ID field. In the billing amount field, the billing amount calculated based on the membership type and usage history of each user is recorded. The settlement field records the settlement status. "Completed" indicates that the payment has been completed and the payment has been made. "Not yet" indicates that the payment has not been completed. For example, if a pre-registered credit card is invalid and a problem such as inability to charge occurs, an "error" is recorded.

Explain the outline of membership registration. Control unit 21 presents a membership application form to the user, for example, via a WEB (World Wide Web) site, and receives information entered by the user. The control unit 21 may use a chat system to acquire 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 each field. The control unit 21 assigns a unique user ID to the user and notifies the user.

A user who uses the coworking space for the first time stops by the reception and presents the user ID notified at the time of registration. The person in charge of reception operates a personal computer or the like installed at the reception desk to record the membership card ID recorded in the unused membership card 15 in the member DB 57 in association with the user ID. The person in charge gives the membership card 15 to the user. Member registration is completed by the above.

The control unit 21 may record the membership card ID recorded in the unused membership card 15 when recording the record regarding the new user in the member DB 57 . In such a case, the person in charge of reception refers to the member DB 57 to confirm the membership card ID, and hands the corresponding membership card 15 to the user.

A personal computer or tablet for accepting membership registration may be installed near the reception. A paper application form may be accepted for membership registration. In such a case, the person in charge of reception inputs the information into the member DB 57 or the information is automatically read by OCR and recorded in the member DB 57 .

A user who has a membership card 15 can use the coworking space without visiting the reception. Specifically, the user can unlock the key mechanism 13 and enter the coworking space by causing the first reader 141 to read the membership card 15 . Similarly, the user can unlock the key mechanism 13 and leave the coworking space by causing the second reader 142 to read the membership card 15 .

Therefore, there is no need for a coworking space to always have a person in charge of performing tasks such as reception procedures and room entry/exit management. For example, an employee of an adjacent store may also serve as the person in charge of the coworking space.

Since the user can easily enter and exit the room using the membership card 15, there is no need to install, for example, a toilet and a vending machine in the coworking space. Operators can easily set up coworking spaces for a fee by partitioning part of large-scale commercial facilities or office buildings. Therefore, the operator can use the idle space as a co-working space with a relatively low initial investment and make a profit.

The walls surrounding the coworking space should be of a size that users cannot easily climb over or slip through. For example, interlocking partitions or the like with a height of about one meter or more may be used for 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 peace of mind.

By using a wall that is lower than the ceiling height and creating a space between the ceiling and the wall, there is no need to install dedicated air conditioning equipment, lighting equipment, fire alarms, etc. in the coworking space. initial investment can be reduced.

Initial investment in co-working spaces, as it is possible to use ordinary doors without installing gates that limit the number of people who can pass through at a time to prevent tailgating, which is used in large-scale facilities such as amusement parks. can be reduced.

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

A triangle indicates the time of entering the room, that is, the time when the membership card 15 held by the user is read by the first reader 141 . An inverted triangle indicates the time of leaving the room, that is, the time when the membership card 15 held by the user is read by the second reader 142 . The thick line indicates the time determined to be the usage time of the user.

A specific example will be given for explanation. The user with "ID010" entered the room at time t11 and left at time t12. The usage time is from t11 to t12. The user with "ID020" entered the room at time t21, left at time t22, entered the room at time t23, and left at time t24. The usage time is from t21 to t24.

The user with "ID030" entered the room at time t31, entered the room at time t32, and left the room at time t33. This user is presumed to have left the room due to tailgating between time t31 and time t32. The usage time is from t31 to t33.

The user with "ID040" entered the room at time t41, and the leaving time is not recorded. This user is presumed to have left the room due to tailgating. The usage time is from t41 to closing time.

The user with "ID050" left the room at time t51. The time of entry was not recorded. This user is presumed to have entered the room by tailgating. The usage time is from opening time to t51.

When the user tailgates without having the first reader 141 read the membership card 15 when entering the room for the first time, and when the user tailgates without having the second reader 142 read the membership card 15 when leaving the room last, the usage time of the user is judged long. By notifying the user of this calculation method, the user is encouraged to read the membership card 15 at least when entering the room for the first time and when leaving the room for the last time.

On the other hand, when entering and exiting the room during use, such as restroom breaks, you may accompany the person with you. Therefore, it is possible to provide a coworking space that users can use in a casual atmosphere.

FIG. 8 is an example of a screen displaying congestion conditions. FIG. 8 is a WEB page in a WEB site introducing, for example, a coworking space. 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 browse the page and check the congestion status. A list of congestion information for each of a plurality of coworking spaces may be displayed on the screen. The user can select the coworking space to be used by considering the convenience such as the time required for moving and the congestion situation.

9 and 10 are screen examples of the management screen. 9 and 10 are screens operated and viewed by the person in charge of the coworking space operator. A menu column 62 is displayed on the left side of the screen.

FIG. 9 shows a screen example in which "top" is displayed in the menu column 62. In FIG. In the top column 63 displayed on the right side of the menu column 62, the number of fixed fee members, the number of pay-as-you-go members, the number of current users, the previous month's billing amount, the previous month's deposit amount, and the previous month's refund amount are Each is represented by an icon. Refunds occur in irregular situations, such as when the user withdraws in the middle of the month, or when there is an erroneous billing in the previous month.

The top screen allows the user to get an overview of the operational status of the coworking space. The top screen may display, for example, the operating expenses of the previous month, the number of active members who have used the service at least once in the previous month, and the like.

FIG. 10 shows an example of a screen in which "member list" is displayed in the menu column 62. As shown in FIG. In a member list column 64 displayed on the right side of the menu column 62, the member's user ID, name, and member type are displayed in tabular form.

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

Although illustration is omitted, 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 member's entry/exit history recorded in the entry/exit DB 56. FIG.

Although illustration is omitted, when the person in charge selects "usage history" in the menu column 62, the control unit 21 displays a list of usage dates and usage times for each user. When the person in charge selects "daily usage history" in the menu column 62, the control unit 21 displays a list of usage times of the user on the date specified by the user.

When the person in charge selects "billing information" in the menu column 62, the control unit 21 displays a list of amounts billed to each user. When the person in charge selects "payment information" in the menu column 62, the control unit 21 displays a list of the amounts paid by each user. When the person in charge selects "refund information" in the menu column 62, the control unit 21 displays a list of refund amounts for each user.

In addition, the screen displayed by the control unit 21 is not limited to the screen illustrated above. The user can appropriately operate the input unit 252 to designate information to be browsed. The control unit 21 displays information on the display unit 251 according to the user's operation.

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

The control unit 41 reads the membership card ID recorded in the membership card 15 via the reader 14 (step S501). The control unit 41 searches the valid DB 52 using the membership card ID as a key to extract records. The control unit 41 refers to the status field of the extracted record and determines whether or not the membership card 15 is valid (step S502). If the control unit 41 cannot extract a record from the valid 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 it 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 sound or a voice such as "Error" from a speaker (not shown).

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

If it is determined to be valid (YES in step S502), the control section 41 controls the key mechanism 13 to unlock the gate section 11 (step S504). By releasing the lock, the user can pass through the entrance/exit 12 . The control unit 41 records the entry and exit of the user (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 reads 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 controller 41 records "enter" in the entry/exit field. When the membership card 15 is read from the second reader 142, the controller 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 ends, the control unit 41 determines whether or not to end the process (step S506). For example, when the closing time of the coworking space has passed, the control unit 41 determines to end the process.

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

In step S503, the control unit 41 may record the presence of the user who tried to use the invalid membership card 15 so that the person in charge can refer to it later. The person in charge can, for example, send a direct mail to the user informing them of how to renew the contract.

FIG. 12 is a flow chart for explaining the processing flow of a program for judging congestion conditions. The program in FIG. 12 is started before the coworking space opens and is executed during business hours.

The control unit 21 sets the variable "number of people" to zero, which is the initial value (step S601). The control unit 21 obtains one new record added to the room entrance/exit DB 56 by replication processing with the room entrance/exit DB 51 (step S602). The control unit 21 determines whether or not "enter" is recorded in the entry/exit field of the acquired record (step S603).

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

The control unit 21 compares the variable "number of people" with a predetermined first threshold value and a predetermined second threshold value to make a determination (step S606). The first threshold is, for example, a value of about 75% of the capacity of the coworking space. The second threshold is, for example, a value of about 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 status of the coworking space is "too much room" (step S607). If the variable "number of people" is greater than or equal to the first threshold and less than the second threshold (more than or equal to the first threshold and less than the second threshold in step S606), the control unit 21 determines that the congestion status of the coworking space is "slightly congested". (Step S608). If the variable "number of people" is greater than or equal to the second threshold (more than or equal to the second threshold in step S606), the control unit 21 determines that the coworking space is "full" (step S609).

After completing step S607, step S608, or step S609, 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, FIG. 8 shows an example of a web page when the control unit 21 determines in step S606 that the variable "number of people" is less than the first threshold.

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

FIG. 13 is a flow chart for explaining the flow of processing of a program that executes billing processing. The program of FIG. 13 is executed, for example, during monthly billing processing. The program of FIG. 13 may be executed when designated by the person in charge of the operator.

The control unit 21 selects the user ID of the member to be billed (step S621). The control unit 21 may accept input of a user ID by a person in charge of administration. 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 or not the member is a pay-as-you-go member based on the member type field of the extracted record (step S622).

If it is determined that the user is not a pay-as-you-go member, that is, a fixed-rate member (NO in step S622), the control unit 21 creates a new record in the billing DB 58. FIG. The control unit 21 records the billing month under calculation in the billing month field, the user ID selected in step S621 in the user ID field, the predetermined fixed fee in the billing amount field, and "not yet" in the settlement field ( step S623). Note that the fixed charges recorded in the billing amount field include charges for paid options contracted by the user.

If it is determined that the user is a pay-as-you-go member (YES in step S622), the control unit 21 starts a daily charge calculation subroutine (step S624). The daily charge calculation subroutine is a subroutine for calculating a daily usage charge based on the data recorded in the entry/exit DB 56 . The processing flow of the daily charge calculation subroutine will be described later.

The control unit 21 determines whether or not processing for the billing period has ended (step S625). If it is determined that the processing has not ended (NO in step S625), the control unit 21 returns to step S624. If it is determined that the processing has ended (YES in step S625), the control unit 21 sums up the usage fee for each day calculated by the daily fee calculation subroutine and the fee for the paid option contracted by the user, and bills the user. A fee to be charged is calculated (step S626).

The control unit 21 creates a new record in the billing DB 58 . The control unit 21 sets the billing month under calculation 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. Record (step S627).

After completing step S623 or step S627, 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 records. Based on the information recorded in the billing destination field of the extracted record, the control unit 21 transmits data regarding billing to the credit card company.

When the billed fee is paid, the control unit 21 extracts the corresponding record from the billing DB 58 and records "completed" in the settlement field. As described above, the control unit 21 implements the functions of the settlement processing unit of the present embodiment.

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

The control unit 21 determines whether or not to end the process (step S629). For example, the control unit 21 determines to end the process when all the members have been processed or when the member specified by the person in charge of management has been processed.

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

FIG. 14 is a flow chart for explaining the processing flow of the daily charge calculation subroutine. The daily charge calculation subroutine is a subroutine for calculating a daily charge based on the data recorded in the entry/exit DB 56 .

Using the user ID and the date as keys, the control unit 21 extracts one day's worth of records of one user from the entry/exit DB 56 (step S641). The control unit 21 determines whether or not the record with the earliest time among the extracted records means entering the room, that is, whether or not "Enter" is recorded in the entry/exit field (step S642).

If it is determined that it means entering the room (YES in step S642), the control unit 21 determines that the entry time of the day is the time recorded in the time field of the earliest record (step S643). If it is determined that it does not mean entering the room (NO in step S642), the control unit 21 determines that the entry time of the 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 or not the record with the latest time among the extracted records indicates leaving the room, that is, whether or not "exit" is recorded in the entry/exit field. (Step S645).

If it is determined to mean leaving the room (YES in step S645), the control unit 21 determines that the leaving time on the day is the time recorded in the time field of the latest record (step S646). If it is determined that it does not mean leaving the room (NO in step S645), the control unit 21 determines that the leaving time of the 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 stay time of the user, that is, the time from the time of entering the room to the time of leaving (step S648). By step S648, the control unit 21 implements the function of the utilization time calculation unit that calculates the utilization time of the user.

The control unit 21 calculates the charge for one day based on the length of stay (step S649). The fee is calculated by integrating the hourly fee and the stay time, for example. A daily maximum charge may be set.

Control unit 21 associates the user ID, the date, and the daily charge, and temporarily records them in auxiliary storage device 23 or main storage device 22 (step S650). The control unit 21 may record charges for each date in a predetermined database. After that, the control unit 21 terminates the process.

The entrance/exit 12 may be an automatic door. In such a case, the key mechanism 13 controls the opening and closing of the automatic door instead of locking and unlocking. A plurality of entrances/exits 12 may be installed in one coworking space. A first reader 141 and a second reader 142 may be arranged at each entrance/exit 12 . A doorway 12 dedicated to entering the room, in which the first reader 141 is arranged, and a doorway 12 dedicated to leaving the room, in which the second reader 142 is arranged, may be provided.

A user ID may be recorded in the membership card 15 . The first reader 141 and the second reader 142 read the user ID recorded on the membership card 15 and search the valid DB 52 in which the user ID and validity are recorded in association with each other to confirm that the read user ID is valid. Determine whether or not

The mobile device 30 owned by the user may also serve as the membership card 15 . For example, the serial number registered in the short-range wireless communication chip built in 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 .

Application software for authentication that transmits a user ID from a short-range wireless communication chip may be installed in the mobile device 30 owned by the user. Application software for authentication that displays a barcode indicating a user ID may be installed in the mobile device 30 owned by the user.

The program described with reference to FIG. 12 may have a function of instructing the administrator to modify the number of users. For example, when the person in charge of management enters the room for cleaning or the like, the number of users in the room is counted, and the variable "number of people" is corrected. It is possible to implement a program that corrects the error caused by tailgating and displays an appropriate congestion situation.

Instead of using the program described using FIG. 12, the congestion situation may be determined based on images captured by cameras installed in the coworking space. Techniques for determining the number of people photographed from an image are well-known, so description thereof will be omitted. By installing a camera in the coworking space, it can be expected to have the effect of suppressing inappropriate behavior by users.

According to the present embodiment, it is possible to provide the information processing system 10 that charges appropriate fees to each user even when tailgating occurs. According to the present embodiment, it is possible to provide the information processing system 10 with a relatively low initial investment and the use of idle space as a paid co-working space for profit.

The user does not need to worry about tailgating except when entering the room for the first time and when leaving the room for the last time. Therefore, it is possible to provide a co-working space with a friendly atmosphere in which manners such as holding the door when entering and exiting can be observed.

As mentioned above, the coworking space is an example of a room. The room in which the gate unit 11 is installed is, for example, an exercise gym equipped with exercise equipment such as a treadmill, a kids' space equipped with playground equipment for infants, a game corner equipped with game machines, or a comic and book store. It may be a reading space or the like where etc. are arranged.

[Modification 1-1]
At step S628 described with reference to FIG. 13, the control unit 21 issues a bill to a predetermined destination instead of transmitting data relating to billing to the credit card company. The control unit 21 may issue a single bill that collects bills for multiple user IDs. By using invoices, companies can expense their employees' usage fees, for example, as part of a welfare program or telework measures.

The control unit 21 may issue an estimate instead of the invoice. Even in a company that pays after an internal decision based on an estimate, the employee's usage fee can be expensed in accordance with the company's rules.

The control unit 21 may automatically issue a receipt after the bill is paid. Automatic confirmation of billing and payment via bank accounts, cloud services, etc. is conventional, and will not be described in detail.

[Modification 1-2]
The fee for a pay-as-you-go user may vary depending on the time zone in which the user enters the room. For example, the control unit 21 sets the charge per hour based on the room entry time determined in step S643 in the daily charge calculation subroutine described using FIG. For example, the control unit 21 sets the fee for the user whose entry time determined in step S643 to be in the morning to 200 yen per hour regardless of the time to leave the room determined in step S646, and the fee for the user whose entry time determined in step S643 starts at 18:00. The fee for the user at 20:00 is set to 300 yen per hour regardless of the time of leaving the room 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 based on, for example, the state of congestion in the coworking space, prediction of congestion, or the like. The control unit 21 displays the usage fee for the day on, for example, a digital signage display arranged near the gate unit 11 and a WEB site that introduces the coworking space.

Pay-as-you-go users can use the coworking space with peace of mind because the usage fee confirmed at the time of entry is applied all day long. By setting a low fee for users who enter the room during a period when there are relatively few users and a high fee for users who enter the room during a period when there are relatively many users, it is possible to level the usage of the coworking space.

The control unit 21 may use different fees for each time period during which the user stayed. A specific example will be given for explanation. For example, the usage fee in the morning is set at 200 yen per hour, the usage fee in the afternoon is set at 250 yen per hour, and the usage fee at night after 18:00 is set at 300 yen per hour.

If the entering time determined in step S643 is 10:00 and the leaving time determined in step S646 is 15:00, the user stays for 2 hours during the 200 yen time slot and for 3 hours during the 250 yen time slot. there is Therefore, in step S649, the control unit 21 calculates the charge of 200×2+250×3=1150 yen.

[Embodiment 2]
The present embodiment relates to an information processing system 10 that notifies when the charge of a user who is a pay-as-you-go member exceeds a threshold. Descriptions of parts common to the first embodiment are omitted.

FIG. 15 is a flowchart for explaining the processing flow of the program according to the second embodiment. The program in FIG. 15 is executed every time the user leaves the room or at night when the user uses the coworking space.

The control unit 21 selects the user ID of the member whose 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 records. The control unit 21 determines whether or not the member is a pay-as-you-go member based on the member 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 starts a subroutine for daily charge calculation (step S663). The daily charge calculation subroutine is the same as the subroutine described using FIG.

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

The control unit 21 determines whether or not the cumulative charge is equal to or greater than a predetermined threshold (step S666). The threshold is, for example, a fixed rate charge. The threshold may be a fee set by the user in advance. If determined to be equal to or greater than the threshold (YES in step S666), the control unit 21 transmits a notification to the mobile device 30 via e-mail, SMS (Short Message Service), or the like (step S667).

The control unit 31 receives the notification (step S701). Control unit 31 outputs the received notification to display unit 351 (step S702). The content of the notification is, for example, "The pay-as-you-go fee for this month has exceeded 20,000 yen. If you switch to a fixed-rate membership by the end of the month, you can use the service for 18,000 yen." A URL (Uniform Resource Locator) for membership type change procedures may be included in the notification.

The notification may be posted on a website that can be accessed by each user through password authentication or the like. The notification may be displayed on the screen of the application program installed on the mobile device 30. FIG.

If it is determined that the member is not a pay-as-you-go member, that is, a fixed-fee member (NO in step S662), or if it is determined that the member is not equal to or greater than the threshold value (NO in step S666), or after step S667 is completed, the control unit 21 determines whether or not to end the process (step S668). If it is determined not to end (NO in step S668), the control unit 21 returns to step S661. If it is determined to end (YES in step S668), the control unit 21 ends the process.

Note that the control unit 21 may automatically switch to the fixed charge system instead of transmitting the notification in step S667. In such a case, the control unit 21 may automatically return the setting to the pay-as-you-go system for the next month.

According to the present embodiment, it is possible to provide information processing system 10 that notifies when the charge of a user who is a pay-as-you-go member exceeds the fixed charge. By preventing the user from being billed an unexpected fee, it is possible to provide the information processing system 10 that improves customer satisfaction.

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

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

[Embodiment 4]
FIG. 17 is an explanatory diagram illustrating the configuration of the information processing system 10 according to the fourth embodiment. The present embodiment relates to a mode of realizing the information processing apparatus 20 of the present embodiment by operating a general-purpose computer 90 and a program 97 in combination. Descriptions of parts common to the first embodiment are omitted.

The computer 90 includes a reading section 29 in addition to the aforementioned control section 21, main storage device 22, auxiliary storage device 23, communication section 24, display section 251, input section 252 and bus.

A 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 . Control unit 21 may also read program 97 stored in semiconductor memory 98 such as a flash memory installed in 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 in the computer 90 as a control program, loaded into the main storage device 22 and executed. As described above, the information processing apparatus 20 described in the first embodiment is realized.

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

FIG. 18 is a map of a coworking space according to Embodiment 5. FIG. The coworking space of the present embodiment is surrounded by walls or partitions on all four sides, and a gate section 11 is arranged in one place. Two reserved areas 192 are arranged inside the room. The reservation target area 192 is surrounded on all sides by walls or partitions, and the reservation gate section 111 is arranged in one place.

The reservation gate unit 111 is configured by an entrance such as a door and the key mechanism 13, for example. The key mechanism 13 of the reservation gate section 111 is a so-called smart lock that is locked and unlocked via a network, like the key mechanism 13 of the gate section 11 . The reservation gate unit 111 may have a reader 14 like the gate unit 11 .

It is desirable that the reservation gate unit 111 has a structure that does not prevent a user in the reservation target area 192 from leaving the reservation target area 192 even when the reservation gate unit 111 is in the locked state. As a result, an accident in which the user is confined within the reserved area 192 can be prevented.

The reserved area 192 is, for example, a private room type work booth used by a user who wants to work intensively. The reserved area 192 may be a conference room where multiple users gather. The reservation target area 192 may be a conference booth for a web conference. Reserved area 192 may be a recreational area where users may play games, exercise, or the like. The uses and facilities of the two reserved areas 192 may differ.

The area other than the reserved area 192 is a common area 191 that can be used by users who have passed through the gate section 11 as appropriate. In the common area 191, desks, chairs, coffee servers, etc., which are not shown, are installed, a multifunction machine, lockers, and the like are arranged.

Note that the map shown in FIG. 18 is an example. The shape of the entire room, the position of the gate section 11, the number and arrangement of the reservation target areas 192, etc. are not limited to those shown in FIG.

In this embodiment, the user uses portable device 30 to make a reservation for reservation target area 192 . When the reservation is established, key information for unlocking the reservation gate section 111 of the reservation target area 192 at the reserved time is sent to the user by e-mail or SMS, for example. In the following description, the key information is an unlocking URL that can transmit an unlocking request to the control unit 41 by accessing it.

At the reserved time, the user uses the mobile device 30 to access the unlocking URL. An unlock button is displayed on the touch panel 35 . When the user taps the unlock button, an unlock signal for unlocking the reservation gate unit 111 is transmitted from the WEB server displaying the unlock button to the authentication server 40 .

The authentication server 40 unlocks the designated reservation gate section 111 according to the unlock signal. The user can enter the reserved area 192 . If the user does not leave the reserved area 192 even after the reserved time elapses, the user is notified that the reserved time has passed by a display installed in the reserved area 192 or a push notification of the mobile device 30 or the like. to be notified.

FIG. 19 is an explanatory diagram for explaining the record layout of the reservation key DB 53. As shown in FIG. The reservation key DB 53 is a database in which location IDs, reservation times, and key information are recorded in association with each other. Here, the location ID is an ID uniquely assigned to the reservation target area 192, and the reservation gate section 111 of the reservation target area 192 is also specified by specifying the location ID.

The reservation key DB 53 has a location ID field, a reservation time field and a key information field. The appointment time field has a start field and an end field. A location ID is recorded in the location ID field. The start and end fields record the start and end times of the reservation, respectively. Key information issued by the control unit 41 is recorded in the key information field.

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

FIG. 20 is an explanatory diagram for explaining the record layout of the reservation DB 59. As shown in FIG. The reservation DB 59 is a database in which location IDs, reservation times, user IDs, and key information are recorded in association with each other. The reservation DB 59 has a location ID field, a reservation time field, a user ID field and a key information field. The appointment time field has a start field and an end field.

A location ID is recorded in the location ID field. The start and end fields record the start and end times of the reservation, respectively. The user ID of the user who made the reservation is recorded in the user ID field. Key information issued by the control unit 41 is recorded in the key information field.

The reservation DB 59 has one record for one reservation. The reservation DB 59 is recorded 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 the control unit 41 synchronize each record recorded in the reservation key DB 53 by replication processing with each record recorded in the reservation DB 59 except for the user ID field. Since the replication process has been used conventionally, the detailed explanation is omitted.

FIG. 21 is a flow chart for explaining the processing flow of the program at the time of reservation according to the fifth embodiment. The program of FIG. 21 is started by the user operating the mobile device 30 when making a reservation for the reservation target area 192 .

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 acceptance screen 65 (see FIG. 23) on the display unit 351 (step S712). As will be described later, the reservation reception screen 65 displays the 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 the time slot that the user wants to reserve. The control unit 31 accepts the input reservation request (step S713). The control unit 31 transmits a reservation request to the information processing device 20 (step S714).

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

The control unit 41 receives the request (step S511). The control unit 41 generates key information according to the received request (step S512). Here, the key information is data used when unlocking a specific reservation gate section 111 in a specific time zone, and is an example of reservation unlocking information of the present embodiment. As described above, the case where the key information is an unlocking URL that can transmit an unlocking request to the control unit 41 by accessing will be described as an example.

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, reservation time, and generated key information corresponding to the reservation target area 192 (step S514).

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 and user ID corresponding to the reservation target area 192 received in step S671, and the key information received in step S673 (step S674).

Control unit 21 transmits the key information to mobile device 30 via e-mail, SMS, or the like (step S675). The control unit 31 receives the key information (step S715). The control unit 31 notifies the user that the key information has been received (step S716). After that, the portable device 30 ends the process.

FIG. 22 is a flow chart for explaining the processing flow of the unlocking program according to the fifth embodiment. The program of FIG. 21 is activated by the user operating the portable device 30 when unlocking the reserved area 192 .

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

The user operates the input unit 352 to access the unlocking URL. An unlock button is displayed on the touch panel 35 if it is within the reserved time zone. If it is before the reserved time slot, a message indicating the possible unlocking time or a simple error message is displayed on the touch panel 35. - 特許庁If it is later than the reserved time zone, a message indicating that the reserved time has passed or a simple error message is displayed on the touch panel 35 . The flowchart of FIG. 22 shows processing when an unlock button is displayed on the touch panel 35 .

The user operates the input unit 352 and taps the unlock button. The control unit 31 receives an operation by the user (step S722). The key information displayed in step S721 is transmitted to the authentication server 40 via the WEB server displaying the unlock button.

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

If it is determined that the authentication has succeeded (YES in step S522), the control section 41 controls the key mechanism 13 to unlock the reservation gate section 111 (step S523). As described above, the user can enter the reserved reservation target area 192 .

After a predetermined period of time has passed, or after a sensor (not shown) has detected the passage of the user, the control section 41 controls the key mechanism 13 to automatically lock the reservation gate section 111 . The key mechanism 13 may autonomously lock the reservation gate section 111 after a predetermined period of time has elapsed or after detecting the passage of the user.

If it is determined that the authentication has not succeeded (NO in step S522), or after step S523 is finished, the control unit 41 returns to the state of waiting for key information from the mobile device 30. FIG. Note that the control unit 41 may display on the display or the like attached to the reservation gate unit 111 that the authentication has not succeeded. The control unit 41 may 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 means of an alarm sound, vibration of the vibrator, display on the display unit 351, or the like (step S724). After that, the control unit 31 terminates the process.

FIG. 23 shows a screen according to the fifth embodiment. The control unit 31 displays the reservation acceptance screen 65 shown in FIG. 23 in step S712 of the flowchart explained using FIG. The reservation acceptance screen 65 includes a schedule column 658 displayed in the center of the screen, a facility use column 651 and a date of use column 653 displayed above the schedule column 658, and a usage time displayed below the schedule column 658. It includes a column 654 , a usage area column 652 and an OK button 659 .

The user operates the usage date column 653 to specify the date. The user designates the facility to be used by operating the facility to be used column 651 . Note that if there is only one facility that the user can use, the facility to use column 651 does not have to be displayed. The control unit 31 displays in the schedule column 658 the reservation status for the date specified in the date of use column 653 for the reservation target area 192 set in the facility to use column 651 . "Booth 1" and "booth 2" in FIG. The horizontal axis of the schedule column 658 indicates the business hours of the coworking space. Hatching indicates the time slots that are already fully booked.

The user operates the usage time column 654 to set the reservation start time and reservation end time. The user designates the reservation target area 192 to be reserved by operating the use area column 652 . It should be noted that the control unit 31 sets the decision button 659 to a non-selectable state when a time period with a prior commitment is specified. After completing the input, the user selects 659 . As described above, the input of the reservation by the user is completed, and the control unit 31 receives information regarding the reservation (step S713).

FIG. 24 shows a screen according to the fifth embodiment. When the user selects "reservation information" from the menu column 62 on the left side of the screen, the control section 31 displays the reservation information screen shown in FIG. The reservation information screen includes a reservation information column 66 . The user can see the reservation information column 66 and confirm the schedule for which he/she has already reserved. The control unit 31 may display the key information corresponding to the reservation when the user selects the details button 655 . The user can use the search field displayed on the upper side of the reservation information field 66 to search for schedules reserved by him/herself.

According to this embodiment, the information processing system 10 that manages the reservation target area 192 can be provided. By making a reservation, the user can certainly use the reserved area 192 equipped with the desired facilities.

By providing the reservation gate section 111 in the reservation target area 192, it is possible to prevent an outsider from entering the reservation target area 192 carelessly. Therefore, it is possible to provide a reservation target area 192 that can also be used for conferences, video conferences, or the like regarding confidential matters. By sending the key information to the user by e-mail or SMS, the user can appropriately distribute the key information to the participants in the conference.

Regarding the use of the reservation target area 192, an additional fee may be determined not only for the pay-as-you-go member but also for the fixed amount member. The "usage charge" column in FIG. 24 indicates the amount of the additional charge incurred for each reservation. Additional charges may vary depending on the time of reservation or the time of use. For example, a user who makes a reservation just before use may be offered a discounted rate.

For fixed-amount members, conditions may be set such that, for example, use of up to 1000 yen per month is free of charge. The control unit 21 adds an additional charge to the charge described in the first embodiment and charges the user.

The reservation target area 192 may be arranged in a place that the user can reach without passing through the gate section 11 . The user can easily invite even a person who is not registered as a user of the coworking space to a meeting held in the reservation target area 192 .

The user may give his/her own telephone number or the like to the invited guest instead of giving the key information. A guest who arrives in front of the reservation gate section 111 calls the inviting user to inform them of their arrival. The user unlocks the reservation gate unit 111 by operating the mobile device 30 and using the key information. In this embodiment, since the lock can be released using the key information without going to the reservation gate section 111, there is no need to explain the unlocking method of the reservation gate section 111 to the guest.

The control section 21 may acquire the position information of the mobile device 30 in addition to the key information, and unlock only when the mobile device 30 is present in front of the reservation gate section 111 . It is possible to provide the information processing system 10 that prevents the reservation target area 192 from being made by someone other than the person who made the reservation.

The reservation gate unit 111 may be provided with an electronic money settlement terminal using NFC or a bar code. After the authentication is successful in step S522, the control unit 41 charges the usage fee for the reserved area 192 via the payment terminal. After completing the settlement, the control unit 41 advances to step S523 and unlocks the reservation gate unit 111 . As described above, it is possible to provide the information processing system 10 that settles the charge each time the reserved area 192 is used.

Note that the key information may be a two-dimensional or one-dimensional bar code that unlocks the reservation gate section 111 by being read by a camera attached to the reservation gate section 111 . When using a barcode for 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 bar code up to the camera attached to the reservation gate section 111 . In step S521, the control unit 41 acquires the barcode via the network.

The key information may be a key code for unlocking the reservation gate section 111 by inputting it using the numeric keypad attached to the reservation gate section 111 by the user. When using a key code for the key information, the control unit 31 displays the key code on the touch panel 35 in step S721. Step S722 is omitted. The user inputs the key code into the numeric keypad attached to the reservation gate section 111 . At step S521, the control unit 41 acquires the key code input via the network.

[Modification 5-1]
FIG. 25 is a map of the coworking space of modification 5-1. In this modification, the reservation gate section 111 is not provided in each reservation target area 192 . The user can use the reserved area 192 at the reserved time without performing an operation such as unlocking. If the user who made the reservation goes to the reservation target area 192 and it is being used by another user, for example, the reservation information screen described using FIG. 24 is mutually confirmed.

Note that the reservation target area 192 provided with the reservation gate unit 111 and the reservation target area 192 not provided with the reservation gate unit 111 may be mixed.

[Embodiment 6]
The present embodiment relates to an information processing system 10 that provides a reservation target area 192 that has not been reserved until just before, without an additional charge. Descriptions of the portions common to the fifth embodiment are omitted.

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

The control unit 21 searches the reservation DB 59 and determines whether or not the reservation target area 192 is in a so-called vacant state after five minutes (step S681). If it is determined that the space is vacant (YES in step S681), the control unit 21 displays a notification on, for example, a display arranged in the coworking space and a web page related to the coworking space (step S682). .

The notification is, for example, a message such as "From 15:00 to 16:00, Web conference booth A can be used without 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 it reaches a time when no reservation is made (step S683). Specifically, for example, when the above message is displayed, the control unit 21 waits until 15:00. The control unit 21 transmits to the authentication server 40 a request to unlock the reservation gate unit 111 regarding the reservation area 192 that is in an empty state (step S684).

The control unit 41 receives the unlocking request (step S531). The control unit 41 confirms that the information processing device 20 that has transmitted the unlocking request is the server managing the reserved area 192 (step S532). If it cannot be confirmed, the controller 41 ignores the unlocking 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, even after the user has passed through reservation gate section 111, control section 41 keeps reservation gate section 111 unlocked.

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

The notification is, for example, a message such as "The time during which the Web conference booth A can be used without additional charges will soon expire. Customers, please leave immediately." After the free time ends, the control section 21 transmits a request to lock the reservation gate section 111 regarding the reservation target area 192 to the authentication server 40 (step S687).

Control unit 41 receives the lock request (step S534). The control unit 41 confirms that the information processing device 20 that has transmitted the lock request is the server that manages the reserved area 192 (step S535). If it cannot be confirmed, the control unit 41 ignores the unlocking request received in step S534. After confirmation, the control section 41 controls the key mechanism 13 to lock the reservation gate section 111 (step S536).

When it is determined that the space is not empty (NO in step S681), or after step S687 is completed, the control unit 21 determines whether or not to end the process (step S689). For example, when the closing time of the coworking space is approaching, the control unit 21 determines to end the process.

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

According to this embodiment, it is possible to provide the information processing system 10 that can effectively utilize the reserved area 192 that has not been reserved. It is possible to provide the information processing system 10 that allows users to experience the merits of the reserved area 192 by experiencing the use of the reserved area 192 at no additional charge, and encourages future use.

[Embodiment 7]
The present embodiment relates to an information processing system 10 that can be used in a ticket system in which tickets are purchased and used as necessary, in addition to the above-described fixed fee system and metered system. Descriptions of parts common to the first embodiment are omitted.

FIG. 27 is an explanatory diagram for explaining the record layout of the member DB 57 of the seventh embodiment. The member DB 57 of the present embodiment has a configuration in which a ticket field is added to the member DB 57 of the first embodiment described using FIG. The number of tickets owned by each user is recorded in the ticket field.

"Ticket" in the membership type field indicates the membership type of the ticket system. A ticket-based member operates a mobile device 30 to purchase a ticket online. The control unit 21 adds the number of tickets purchased by the user to the ticket field. It should be noted that a so-called coupon-type ticket may be provided, in which a ticket for 11 rides can be purchased for the price of 10 rides, for example.

FIG. 28 is a flowchart for explaining the processing flow of the program according to the seventh embodiment. The program of FIG. 28 is executed instead of the program described using FIG.

The control unit 41 reads the membership card ID recorded in the membership card 15 via the reader 14 (step S501). The control unit 41 searches the valid DB 52 using the membership card ID as a key to extract records. The control unit 41 refers to the status field of the extracted record and determines whether or not the membership card 15 is valid (step S502). If the control unit 41 cannot extract a record from the valid 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 transmits the membership card ID read in step S501 to the information processing device 20 (step S541). The control unit 21 receives the membership card ID (step S691). The control unit 21 determines whether or not the membership type of the user is a ticket system (step S692).

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

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

If it is determined that the user is a member of the ticket system (YES in step S692), the control unit 21 acquires the number of tickets held by the user from the ticket field of the extracted record. If the user has the required number of tickets, the control unit 21 updates the ticket field data to the value obtained by subtracting the required number of tickets (step S694).

If a user who has entered the venue once is permitted to freely enter and leave the gate section 11 during the day, the control section 21 updates the data in the ticket field only when it is the first entry on the day.

The control unit 21 transmits to the authentication server 40 information regarding whether or not the gate unit 11 is unlocked (step S695). Specifically, if the user has the required number of tickets in step S694, the control unit 21 transmits to the authentication server 40 that the lock of the gate unit 11 is to be released. If the number of tickets is insufficient, the control unit 21 notifies the authentication server 40 that the lock will not be released.

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

If it is determined that it is not valid (NO at step S502), or if it is determined that it is not canceled (NO at step S543), the control unit 41 outputs an error notification (step S503). Specifically, the control unit 41 outputs a beep sound or a voice such as "Error" from a speaker (not shown).

After step S503 or step S505 ends, the control unit 41 determines whether or not to end the process (step S506). For example, when the closing time of the coworking space has passed, the control unit 41 determines to end the process.

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

After step S695, 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, when the remaining number of tickets is 2, the control unit 31 displays "There are 2 remaining tickets." When the remaining number of tickets is one, the control unit 31 displays "Tickets are exhausted. Please purchase a ticket before the next use." If the ticket is insufficient and the lock of the gate section 11 is not released, the control section 31 displays "You cannot enter because there are insufficient tickets. Please purchase the necessary ticket."

The control unit 31 may display a button for online ticket purchase on the touch panel 35 . Control unit 31 may display, for example, a button for purchasing a coupon and a button for purchasing a single ticket on touch panel 35 side by side.

A user with insufficient tickets can enter by unlocking the gate part 11 by having the reader 14 read the membership card 15 again after purchasing the tickets online by operating the portable device 30.例文帳に追加

According to the present embodiment, it is possible to provide the information processing system 10 that can accommodate users who want to pay for the amount used. For example, it is possible to provide the information processing system 10 that can promote sales by offering tickets for three times to newly registered users.

Note that the number of tickets required for one use may be set differently depending on the facility to be used. When using the reservation target area 192 described in the fifth embodiment, a metered or fixed rate user may be able to use the ticket described in the present embodiment.

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

FIG. 29 is an explanatory diagram for explaining the record layout of the member DB 57 of the eighth embodiment. The member DB 57 of the present embodiment has a configuration in which a remaining count field is added to the member DB 57 of the first embodiment described using FIG. The remaining number of times each user can use the facility is recorded in the remaining number of times field. "Unlimited" indicates that there is no limit on the number of times of use.

Each time the user uses the facility, the control unit 21 decrements the value of the remaining count field by one. When the value of the remaining number field becomes zero, the membership card 15 of the user does not unlock the gate section 11 of the facility. Control unit 21 sets the remaining number of times field to an 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.

FIG. 30 is a flowchart for explaining the processing flow of the program according to the eighth embodiment. The processing up to step S691 is the same as the processing flow of the seventh embodiment described with reference to FIG. 28, so description thereof will be omitted. The control unit 21 determines whether or not 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 to extract records. When "0" is recorded in the remaining count field of the extracted record, the control unit 21 determines that the remaining count of the user is zero.

If it is not zero, that is, if it is determined that the member can use the facility (NO in step S801), the control unit 21 updates the extracted record and decrements the remaining count by one (step S802). The control unit 21 transmits to the authentication server 40 that the lock of the gate unit 11 is to be released (step S803). If it is determined that the remaining number of times is zero (YES in step S801), the control unit 21 notifies the authentication server 40 of not unlocking the gate unit 11 (step S804).

The control unit 41 receives the information transmitted in step S803 or step S804 (step S542). Since the subsequent processing is the same as the processing flow of the seventh embodiment described using FIG. 28, the description is omitted.

The control unit 21 notifies the portable device 30 that the remaining number of times is zero (step S805). The portable device 30 receives 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, when resetting the remaining number of times once a day, the control unit 31 displays "The number of times of use for today has been exceeded. You cannot use it again today." Similarly, when the remaining number of times is initialized once a week, the control unit 31 displays "The number of times of use for this week has been exceeded. Please wait until next Monday."

For a user who can use the service by changing the membership type, the control unit 31 gives the message "You have exceeded the number of times of use for today. Please," along with a button for applying to change the membership type may be displayed.

The control unit 31 may display a button for purchasing a ticket online together with a message saying "The number of times of use for today has been exceeded. You can use it by purchasing an additional ticket of 200 yen/time." When the user purchases a ticket, the control unit 21 adds the purchased number to the remaining number field.

If the user agrees to pay the additional charge according to the contract, etc., the control unit 21 transmits to the authentication server 40 in step S804 that the lock of the gate unit 11 is to be released, and in step S742 the control unit 31 outputs "today's payment". The number of times of use per minute has been exceeded. Subsequent use will incur an additional charge of 10 yen/minute." may be displayed. The control unit 21 charges the user an additional fee in addition to the normal fee.

According to the present embodiment, information is managed in a state that is easy for many users to use by leveling the usage status among users by restricting usage or charging additional fees to specific users with high usage frequency. A processing system 10 can be provided.

[Embodiment 9]
This embodiment relates to an information processing system 10 that can issue a membership card 15 unattended. Descriptions of parts common to the first embodiment are omitted.

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

In this embodiment, the reservation gate section 111 explained in the fifth embodiment is installed at the entrance of the room. The user receives the key information described in the fifth embodiment online. The issuance of key information is the same as the process of the fifth embodiment described with reference to FIG. 21, so description thereof will be omitted.

FIG. 31 is a flowchart for explaining the processing flow of the program according to the ninth embodiment. The processing up to step S523 is the same as the processing flow of the program of the fifth embodiment described with reference to FIG. 22, so description thereof will be omitted.

After the gate section 11 is released in step S523, the user passes through the gate section 11, enters the room, and operates the automatic registration machine. The automatic registration machine is connected to the information processing device 20 via a network and controlled by the control section 21 .

The control unit 21 receives input of information necessary for member registration from the user (step S811). Note that the control unit 21 may display the information input by the user when applying for the key information, and accept additions or corrections by the user.

A user holds up an IC card, a smart phone, or the like on hand to a card reader attached to the automatic registration machine. The control unit 21 acquires the ID information uniquely assigned to the IC card or the IC chip built in the smart phone via the card reader (step S812). Control unit 21 creates a new record in member DB 57 .

The control unit 21 issues a user ID unique to the user and records it in the user ID field. The control unit 21 records the ID information obtained in step S812 in the membership card ID field. The control unit 21 also records appropriate information in the fields after the name field (step S813).

As described above, the IC card or smart phone that the user already possesses is registered in the member DB 57 and functions as the membership card 15 . For users who do not wish to use their existing IC card or the like, the control unit 21 may issue a membership card 15 using a blank IC card held in the automatic registration machine. good.

According to this embodiment, it is possible to provide the information processing system 10 that can issue the membership card 15 without human intervention.

[Modification 9-1]
This modification relates to an information processing system 10 that issues a child user membership card 15 that is linked to a parent user. The description of the parts common to the ninth embodiment is omitted.

In this embodiment, an organization such as a company or school serves as a parent user and manages child users such as employees or students. 32 and 33 are screen examples of modification 9-1. FIG. 32 shows an example of a screen of a personal computer used by a person in charge of the general affairs department of a company, for example, when registering an employee.

Using the screen shown in FIG. 32, the person in charge sends the employee's name, e-mail address, password, etc. to the information processing device 20 to request the issuance of key information. The information processing device 20 acquires key information for each employee from the authentication server 40 and transmits it to the person in charge. The person in charge forwards the key information to the employee. Note that the key information may be directly transmitted from the information processing device 20 to each employee.

FIG. 33 is an example of a screen used by a person in charge of the general affairs department to manage the registered information of the company's employees. The person in charge can use the screen shown in FIG. 33 to search for registered employees, change registered information, delete registered information, and the like.

The employee who has received the key information goes to the designated place and operates the automatic registration machine to register the membership card 15 as described in the ninth embodiment. The automatic registration machine may be installed in the company. The control unit 21 records the user ID of each employee in association with the parent ID owned by the company, and collectively bills the company, which is the parent user, for the usage fee of each employee.

According to this modified example, a company can provide employees with a work place for telework. Child IDs may be issued to desired employees as part of the welfare program.

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

FIG. 34 is an explanatory diagram for explaining the commodity locker 18 of the tenth embodiment. Product lockers 18 are installed, for example, in common area 191 . In the example shown in FIG. 34, the product lockers 18 are provided with a total of five lockers of three different sizes, large, medium and small, and one display installed in the center. A key mechanism 13 is attached to each locker door, and is remotely operated by an authentication server 40 .

The display shows a list of products stored in each locker. In the example shown in FIG. 34, locker No. 1 contains an energy drink, locker No. 3 contains a blanket, and locker No. 4 contains a hand towel. Lockers No. 2 and No. 5 contain no products. The user can select the desired product, open the door, and take out the product inside. The control unit 21 bills the price of the product together with the usage fee of the coworking space.

FIG. 35 is an explanatory diagram for explaining the record layout of the product DB 55. As shown in FIG. The product DB 55 has an installation location field, a locker ID field, a product field and a price field. The place where the product locker 18 is installed is recorded in the installation place field.

A locker ID uniquely assigned to each locker is recorded in the locker ID field. The commodity field records the commodity accommodated in the locker. The price field records the price of the product.

The product DB 55 has one record for one locker. The product DB 55 is recorded in the auxiliary storage device 23 or an external large-capacity storage device connected to the information processing device 20 .

FIG. 36 is a flowchart for explaining the processing flow of the program according to the tenth embodiment. The program in FIG. 36 is started by the user operating the portable device 30 when the user wants to purchase the product in the product 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 installation location of the product locker 18 installed near the gate 11 that the user recently entered/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 sold in the 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 product list (step S752). The control unit 31 displays the product selection screen illustrated in FIG. 37 on the touch panel 35 (step S753). The control unit 31 accepts the product selection by the user (step S754). The control unit 31 transmits information about the selected product or information about the locker number to the information processing device 20 (step S755). The control unit 31 ends the processing.

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

FIG. 37 shows an example of a screen according to the tenth embodiment. An example of a product purchase screen displayed on the touch panel 35 by the control unit 31 in step S753 will be described with reference to FIG. A product selection field 681 is displayed in the center of the product purchase screen. The item selection field 681 is in the form of a pull-down menu. After the user selects a desired product by operating the product selection column 681 , the user taps the purchase button 682 arranged on the lower side of the product selection column 681 . As described above, the product selection is completed, and the door is unlocked by the control unit 41 .

According to this embodiment, it is possible to provide an information processing system 10 for unmanned vending of commodities of various shapes and sizes that are difficult to handle with general vending machines.

The technical features (constituent elements) described in each embodiment can be combined with each other, and new technical features can be formed by combining them.
The embodiments disclosed this time are illustrative in all respects and should be considered not restrictive. The scope of the present invention is indicated by the scope of the claims rather than the meaning described above, and is intended to include all modifications within the scope and meaning equivalent to the scope of the claims.

10 Information Processing System 11 Gate Section 111 Reservation Gate Section 12 Doorway 13 Key Mechanism 14 Reader 141 First Reader 142 Second Reader 15 Membership Card 18 Product Locker 191 Common Area 192 Reserved Area 20 Information Processing Device 21 Control Section 22 Main Storage Device 23 auxiliary storage device 24 communication unit 251 display unit 252 input unit 29 reading unit 30 mobile device 31 control unit 32 main storage unit 33 auxiliary storage device 34 communication unit 35 touch panel 351 display unit 352 input unit 40 authentication server 41 control unit 42 main memory Device 43 Auxiliary storage device 44 Communication unit 51 Entrance/exit DB
52 effective database
53 Reserved key DB
55 Product database
56 Entrance/Exit DB
57 Member DB
58 Billing database
59 Reservation DB
61 Congestion status column 62 Menu column 63 Top column 64 Member list column 641 Search column 65 Reservation reception screen 651 Facility column 652 Area column 653 Date column 654 Hours of use column 655 Details button 658 Schedule column 659 Confirm button 66 Reservation information column 681 Product selection field 682 Purchase button 81 Entering information acquiring unit 82 Leaving information acquiring unit 83 Usage time calculating unit 84 Billing processing unit 90 Computer 96 Portable recording medium 97 Program 98 Semiconductor memory

Claims (14)

Acquire the user ID and room entry time of the user who unlocked the smart lock from outside the room,
Acquiring the user ID and room exit time of the user who unlocked the smart lock from inside the room,
For each date, when multiple room entry times or multiple room exit times are obtained for each of the user IDs, calculate the usage time, which is the time from the first room entry time of the day to the last room exit time of the same day ,
An information processing method in which a computer executes a process of billing the usage fee of each user calculated based on the user ID and the usage time through the user's credit card. A first reader is arranged outside the room to read a membership card ID uniquely assigned to the membership card from the membership card possessed by the user,
A second reader for reading the membership card ID from the membership card is arranged inside the room,
When it is determined that the membership card ID read by the first reader or the second reader is associated with a valid user ID by searching a database in which a membership card ID and a valid user ID are associated and recorded. to unlock the smart lock
The information processing method according to claim 1 . transmitting the key information of the smart lock to the guest user;
unlocking the smart lock when the key information is received;
The guest user is registered as a member via a registration machine installed inside the room.
The information processing method according to claim 2 . read the ID of the IC card or the IC chip mounted on the smartphone held by the guest user through the registration machine;
Using the read ID as the membership card ID, the membership card ID and the user ID given to the guest user are associated and recorded in a database in which the membership card ID and the valid user ID are recorded in association with each other.
The information processing method according to claim 3 . Receiving a request to issue the key information from the registered parent user, and billing the parent user for the fee of the child user who has registered as a member using the key information.
The information processing method according to claim 3 or 4 . 6. The information processing method according to any one of claims 1 to 5 , wherein congestion information of said room is output based on said user IDs of a plurality of users, said room entry time and said room exit time. If the contract conditions of the user corresponding to the user ID obtained from the database that records the user ID and contract conditions in association with each other is a fixed fee system,
7. The information processing method according to any one of claims 1 to 6 , wherein a fixed fee based on said contract terms is charged via said user's credit card. If the terms and conditions include a locker contract, bill the locker via the user's credit card
The information processing method according to claim 7 . Receiving a reservation request including the designation of the reservation target area and the reservation time,
transmitting reservation unlocking information corresponding to the reservation request;
determining whether it is within the reserved time when the reservation unlocking information is received;
The information processing method according to any one of claims 1 to 8 , wherein, when it is determined that it is within the reserved time, a smart lock installed in the reserved area is unlocked. The reserved area is arranged inside the room
The information processing method according to claim 9 . The reserved area is the entire room
The information processing method according to claim 9 . Acquire the user ID and room entry time of the user who unlocked the smart lock from outside the room,
Acquiring the user ID and room exit time of the user who unlocked the smart lock from inside the room,
calculating usage time of each user based on the user ID, the entry time and the exit time;
billing the user's usage fee calculated based on the user ID and the usage time via the user's credit card ;
transmitting the key information of the smart lock to the guest user;
unlocking the smart lock when the key information is received;
The guest user is registered as a member via a registration machine installed inside the room.
An information processing method in which a computer executes processing. Acquire the user ID and room entry time of the user who unlocked the smart lock from outside the room,
Acquiring the user ID and room exit time of the user who unlocked the smart lock from inside the room,
When a plurality of room entry times or room exit times are acquired for each user ID for each date, the usage time , which is the time from the first entry time of the day to the last exit time of the same day, is calculated. ,
A program that causes a computer to execute a process of billing the usage fee of each user calculated based on the user ID and the usage time through the user's credit card. a room entry information acquisition unit that acquires the user ID of the user who unlocked the smart lock from outside the room and the room entry time;
a room exit information acquisition unit that acquires the user ID of the user who unlocked the smart lock from inside the room and the room exit time;
When a plurality of room entry times or room exit times are obtained for each user ID for each date, the usage time , which is the time from the first entry time of the day to the last exit time of the same day, is calculated. a usage time calculation unit;
An information processing apparatus comprising: a billing processing unit that bills each user's usage fee calculated based on the user ID and the usage time through the user's credit card.

Images