Locker system and locker management method

Abstract

Provided is a locker system in which usefulness to a locker user is increased. The locker system comprises an acquisition unit, a determination unit, and a locker control unit. The acquisition unit acquires biological information about the user. The determination unit determines a request relating to the locker use of the user. The locker control unit opens a locker specified on the basis of the request relating to the locker use in relation to a user specified by a comparison process using the biological information.

Description

[Technical field]

[0001] The present invention relates to a locker system, a locker management system, a locker management method, and a storage medium. [Background technology]

[0002] In recent years, diverse work styles have been promoted. For example, the "free address" system, where employees are free to use any available seat without being assigned a specific desk, is being promoted. In this case, a single free address floor may be used by employees belonging to a specific department, but the floor may also be used by an unspecified number of users across departments and companies.

[0003] Users may leave a floor temporarily. When an unspecified number of users are on the same floor, users who temporarily leave the floor must store their belongings in a locker.

[0004] Patent Document 1 describes that a locker system is provided that enables a user to perform a remote authentication procedure when retrieving a deposited baggage in an emergency and prevents human error. When the locker box is temporarily locked, the locker system disclosed in Patent Document 1 drives an imaging unit to capture an image of the user until the completion of a payment process using an operation display unit. The locker system stores one or more images captured at a predetermined timing as a first image in association with the number of the locker box and performs a proper locking. The locker system captures an image using the imaging unit in response to an operation to receive a baggage on the operation display unit, and transmits an unlocking request to a management center together with a second image captured in response to the receiving operation, the first image, and the number of the locker box. The locker system unlocks the locker box corresponding to the locker number based on an unlocking instruction transmitted from the management center in response to a result of matching the first image and the second image based on the unlocking request. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-200593 A Summary of the Invention [Problem to be solved by the invention]

[0006] As mentioned above, free address floors and the like require lockers (locker boxes). When using existing lockers, users insert a fee into the locker and use a physical key to lock the locker containing their luggage. However, lockers that use physical keys to lock are not suitable for the temporary storage (deposit) of luggage on free address floors. This is because users are required to insert a fee and lock the lock every time they temporarily leave a free address floor.

[0007] A primary object of the present invention is to provide a locker system, a locker management system, a locker management method, and a storage medium that contribute to improving convenience for locker users. [Means for solving the problem]

[0008] According to a first aspect of the present invention, a locker system is provided which includes an acquisition unit that acquires biometric information of a user, a determination unit that determines the user's request for locker use, and a locker control unit that unlocks a locker identified based on the request for locker use for a user identified by a matching process using the biometric information.

[0009] According to a second aspect of the present invention, there is provided a locker management system including a server device and a locker system connected to the server device, the locker system comprising an acquisition unit that acquires biometric information of a user, a determination unit that determines a request for locker use from the user, a request unit that sends a locker unlock request including the biometric information and the request for locker use to the server device, and a locker control unit that unlocks a locker based on the response acquired from the server device, wherein the server device identifies the user by a matching process using the biometric information included in the locker unlock request, identifies the locker to be unlocked based on the request for locker use included in the locker unlock request, and includes the locker ID of the identified locker in its response to the locker unlock request.

[0010] According to a third aspect of the present invention, a locker management method is provided in a locker system, which acquires biometric information of a user, determines a request for the user to use a locker, and unlocks a locker identified based on the request for use of the locker for a user identified by a matching process using the biometric information.

[0011] According to a fourth aspect of the present invention, there is provided a computer-readable storage medium that stores a program for causing a computer installed in a locker system to execute the following processes: acquiring biometric information of a user; determining a request for the user to use a locker; and unlocking a locker identified based on the request for use of the locker for a user identified by a matching process using the biometric information. Effect of the Invention

[0012] According to each aspect of the present invention, a locker system, a locker management system, a locker management method, and a storage medium are provided that contribute to improving the convenience of locker users. Note that the effects of the present invention are not limited to the above. The present invention may achieve other effects instead of or in addition to the above effects. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram for explaining an overview of an embodiment. [Diagram 2] 1 is a diagram illustrating an example of a schematic configuration of a locker management system according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of the appearance of a biometric authentication-enabled locker according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a display by the biometric authentication-enabled locker according to the first embodiment. [Diagram 5] FIG. 4 is a diagram showing an example of a display by the biometric authentication-enabled locker according to the first embodiment. [Figure 6] FIG. 4 is a diagram showing an example of a display by the biometric authentication-enabled locker according to the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of a processing configuration of a server device according to the first embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a user registration unit according to the first embodiment. [Figure 9] 4 is a diagram for explaining the operation of a user information acquisition unit according to the first embodiment; FIG. [Figure 10] FIG. 2 is a diagram showing an example of a user database according to the first embodiment; [Figure 11] FIG. 2 is a diagram showing an example of an attendee management database according to the first embodiment. [Figure 12] 4 is a diagram illustrating an example of a locker management database according to the first embodiment; FIG. [Figure 13] FIG. 2 is a diagram showing an example of the processing configuration of a biometric authentication-enabled locker according to the first embodiment. [Figure 14] 4 is a diagram illustrating an example of a processing configuration of an entrance management terminal according to the first embodiment; FIG. [Figure 15] 4 is a sequence diagram showing an example of the operation of the locker management system according to the first embodiment. FIG. [Figure 16] FIG. 11 is a diagram for explaining the operation of a user request determination unit according to the second embodiment. [Figure 17] FIG. 11 is a diagram for explaining the operation of a user request determination unit according to the second embodiment. [Figure 18] FIG. 13 is a diagram showing an example of the processing configuration of a biometric authentication-enabled locker according to the third embodiment. [Figure 19] FIG. 13 is a diagram for explaining the operation of a gate control unit according to the fourth embodiment. [Figure 20] FIG. 13 is a diagram for explaining the operation of a gate control unit according to the fourth embodiment. [Figure 21] FIG. 13 is a diagram illustrating an example of a processing configuration of a server device according to the fifth embodiment. [Figure 22] FIG. 13 is a diagram for explaining the operation of an equipment management unit according to the fifth embodiment. [Diagram 23] FIG. 13 is a diagram showing an example of an equipment management database according to the fifth embodiment. [Figure 24] FIG. 13 is a diagram illustrating an example of a locker management database according to the fifth embodiment. [Diagram 25] FIG. 13 is a diagram for explaining the operation of a user request determination unit according to the fifth embodiment. [Figure 26] FIG. 23 is a diagram for explaining the operation of a user request determination unit according to the sixth embodiment. [Figure 27] FIG. 23 is a diagram for explaining the operation of a user request determination unit according to the sixth embodiment. [Figure 28] FIG. 2 illustrates an example of a hardware configuration of a server device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] First, an outline of one embodiment will be described. The reference numerals in the drawings are added to each element for convenience as an example to aid in understanding, and the description of the outline is not intended to be limiting. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units rather than hardware units. The connection lines between the blocks in each drawing include both bidirectional and unidirectional. The unidirectional arrows are used to diagrammatically indicate the flow of the main signal (data) and do not exclude bidirectionality. In this specification and the drawings, elements that can be similarly described may be given the same reference numerals to avoid redundant description.

[0015] A locker system 100 according to one embodiment includes an acquisition unit 101, a determination unit 102, and a locker control unit 103 (see FIG. 1). The acquisition unit 101 acquires biometric information of a user. The determination unit 102 determines a request for use of a locker by the user. The locker control unit 103 unlocks a locker identified based on the request for use of a locker for a user identified by a matching process using the biometric information.

[0016] The locker system 100 acquires biometric information (e.g., face image) of a user and determines the user's request for locker use (e.g., putting away or taking out luggage). The locker system 100 transmits the biometric information and the request for locker use to, for example, a control device that manages and controls the use of the lockers. The server device identifies the locker user by matching using the acquired biometric information. The server device identifies the locker to be unlocked in response to the request of the identified locker user and transmits the ID of the identified locker to the locker system 100. The locker system 100 unlocks the locker corresponding to the acquired locker ID. In this way, the locker management system including the locker system 100 unlocks the locker by biometric authentication of the user, improving the convenience of the locker user. In other words, the locker user does not need to insert a fee (coin) or lock the locker with a physical key, which are required in existing locker systems. The locker system 100 may realize the above-mentioned functions of the server device by itself, without transmitting the biometric information and the request for locker use to the server device. In other words, the locker system 100 may store biometric information of users who are allowed to use the lockers, and verify (identify) the users using the stored biometric information.

[0017] Specific embodiments will be described in more detail below with reference to the drawings.

[0018] [First embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0019] Fig. 2 is a diagram showing an example of a schematic configuration of the locker management system according to the first embodiment. Referring to Fig. 2, the locker management system includes a biometric authentication-enabled locker 10, a server device 20, an entrance management terminal 30-1, an exit management terminal 30-2, and a camera device 40.

[0020] The devices shown in Fig. 2 are interconnected. For example, the biometric authentication-enabled lockers 10 and the server device 20 are connected by wired or wireless communication means, and are configured to be able to communicate with each other. Note that Fig. 2 shows the connection lines between the biometric authentication-enabled lockers 10 and the server device 20, but other components (entrance management terminal 30-1, exit management terminal 30-2, camera device 40) are also connected to the server device 20. Furthermore, a stationary PC (Personal Computer) installed on the floor is also connected to the server device 20.

[0021] In the following description, unless there is a particular reason to distinguish between the entrance management terminal 30-1 and the exit management terminal 30-2, they will simply be referred to as "terminal 30."

[0022] The server device 20 may be installed in the same building as the biometric authentication-enabled locker 10, or may be installed on a network (on the cloud).

[0023] The floor shown in Fig. 2 is a so-called free address floor, where employees can freely select an available seat to perform their work. The biometric authentication-enabled locker 10 is installed on the free address floor. However, it is of course not intended that the installation location of the biometric authentication-enabled locker 10 disclosed in this application be limited to a free address floor. The biometric authentication-enabled locker 10 may be installed in a place visited by an unspecified number of users, such as a station or an airport.

[0024] The biometric authentication-enabled locker 10 is a locker system for storing belongings of floor users (e.g., clothing, notebooks, writing implements, etc.). The biometric authentication-enabled locker 10 identifies the user through biometric authentication and performs an operation according to the identified user. For example, the biometric authentication-enabled locker 10 identifies the user by using the user's "face." This disclosure will mainly explain the case where a "face image" or a "feature amount generated from a face image" is treated as biometric information. However, it is not intended to limit the biometric information to a "face image" or the like, and other biometric information (e.g., iris, etc.) may be used for authentication.

[0025] Fig. 3 is a diagram showing an example of the exterior (front view) of a biometric authentication-enabled locker 10. As shown in Fig. 3, the biometric authentication-enabled locker 10 comprises a plurality of lockers (eight locker boxes in the example of Fig. 3), a display panel 11, and a camera 12. The biometric authentication-enabled locker 10 comprises lockers of different sizes (different storage capacities for luggage, etc.). The letters and numbers written in the upper left corner of each locker shown in Fig. 3 indicate the number of each locker (locker number).

[0026] The display panel 11 provides various information to the user. The display panel 11 is integrated with an operation device such as a touch panel. The biometric authentication-enabled locker 10 accepts operations by the user via the touch panel. A GUI (Graphical User Interface) is provided to the user by the display panel 11 and the touch panel.

[0027] The camera 12 is installed so as to be able to capture an image of a user standing in front of the device (biometric authentication-enabled locker 10).

[0028] 2 is a device that controls and manages various devices on a floor, including the biometric authentication-enabled lockers 10. For example, the server device 20 controls the biometric authentication-enabled lockers 10.

[0029] The entrance management terminal 30-1 is a terminal installed at the entrance to the free address floor. The entrance management terminal 30-1 is connected to the gate 31. When the entrance management terminal 30-1 successfully authenticates a visitor to the floor, it opens the gate 31 and permits the visitor to enter the free address floor.

[0030] The exit management terminal 30-2 is a terminal installed at the exit of the free address floor. Like the entrance management terminal 30-1, the exit management terminal 30-2 is also connected to the gate 31. When the exit management terminal 30-2 succeeds in authenticating (identifying) the person exiting, it opens the gate 31.

[0031] 2 shows a case where floor entrants are managed by terminals 30 (entrance management terminal 30-1, exit management terminal 30-2) and gate 31. However, as mentioned above, when biometric authentication-enabled lockers 10 are installed in places such as train stations and airports, the above devices are not necessary. In other words, in the locker management system disclosed in this application, the terminals 30 and gates 31 do not need to be installed.

[0032] The server device 20 manages the entrance and exit of floor users using an entrance management terminal 30-1 and an exit management terminal 30-2.

[0033] At least one camera device 40 is installed on the floor shown in Fig. 2. The camera device 40 is installed so as to overlook the entire floor. Although one camera device 40 is shown in Fig. 2, if multiple camera devices 40 are required to obtain an image overlooking the entire floor, a number of camera devices 40 that will achieve this purpose will be installed.

[0034] [System operation overview] An outline of the operation of the locker management system according to the first embodiment will be described with reference to FIG.

[0035] When a visitor to a floor approaches the entrance management terminal 30-1, the entrance management terminal 30-1 captures a facial image of the visitor. The entrance management terminal 30-1 transmits the captured facial image to the server device 20 and requests authentication processing of the visitor. If the server device 20 succeeds in authenticating the visitor, it notifies the entrance management terminal 30-1 of that fact. Upon receiving the notification, the entrance management terminal 30-1 opens the gate 31 and allows the visitor to enter.

[0036] The server device 20 manages visitors within the floor based on the result of the authentication process.

[0037] When a visitor on the floor moves in front of the exit management terminal 30-2, the exit management terminal 30-2 captures a facial image of the visitor. The exit management terminal 30-2 transmits the captured facial image to the server device 20 and requests authentication processing of the visitor. If the server device 20 succeeds in authenticating the visitor, it notifies the exit management terminal 30-2 of that effect. Upon receiving the notification, the exit management terminal 30-2 opens the gate 31 and allows the visitor to exit.

[0038] When temporarily leaving the free address floor, the visitor stores his / her baggage (items, objects) in the biometric authentication-enabled locker 10. The locker user moves to the front of the biometric authentication-enabled locker 10 (particularly, in front of the camera 12).

[0039] When the biometric authentication locker 10 confirms the presence of a user, it provides the user with a GUI that accepts operations related to the user's request (storing or removing luggage). For example, the biometric authentication locker 10 displays a screen as shown in Fig. 4 to grasp the user's request.

[0040] The biometric authentication-enabled locker 10 captures a facial image of a user standing in front of it. For example, the biometric authentication-enabled locker 10 captures a facial image while making it clear to the user that a facial image will be captured by displaying a message as shown in Fig. 5.

[0041] The biometric authentication-enabled locker 10 transmits to the server device 20 a "locker unlock request" that includes the user's request (putting or taking out luggage) and an image of the user's face.

[0042] The server device 20 extracts the face image from the acquired locker unlock request and performs a matching process using the face image. By performing the matching process, the server device 20 identifies the locker user from among those entering the floor.

[0043] The server device 20 controls and manages the locker in response to the user's request (storing or retrieving luggage) included in the locker unlock request for the identified locker user.

[0044] Specifically, if the user's request is to "store luggage," the server device 20 selects an empty locker that does not contain luggage and stores the selected locker in association with the user. The server device 20 also transmits a response to the biometric authentication-enabled locker 10, including information identifying the selected locker (e.g., locker number) and the user's request (store luggage).

[0045] If the user's request is to "remove luggage," the server device 20 identifies the locker in which the identified user's luggage is stored. The server device 20 transmits a response including the identified locker number, the user's request (remove luggage), etc. to the biometric authentication-enabled locker 10.

[0046] The biometric authentication locker 10 that receives a response to the locker unlock request will perform an action according to the response. For example, when the biometric authentication locker 10 receives a locker number along with "storing luggage," it will display the message shown in Fig. 6(a) and open the corresponding locker. Alternatively, when the biometric authentication locker 10 receives a locker number along with "removing luggage," it will display the message shown in Fig. 6(b) and open the corresponding locker.

[0047] When it is detected that the opened locker has been closed, the biometric authentication locker 10 detects whether or not there is luggage in the locker. When the detection process is completed, the biometric authentication locker 10 transmits "luggage presence / absence information" to the server device 20. The luggage presence / absence information includes the locker number of the closed locker and information regarding the presence or absence of luggage in the locker (luggage status).

[0048] The server device 20 ensures consistency between the locker management status and the actual status (presence or absence of luggage) within the locker based on luggage presence / absence information acquired from the biometric authentication-enabled lockers 10.

[0049] <Advance preparation> System users (users of the free address floor) need to make some advance preparations. The advance preparations are explained below.

[0050] A user registers his / her attribute values ​​such as biometric information and profile in the system. Specifically, the user inputs a face image to the server device 20. The user also inputs his / her profile (e.g., name, employee number, place of work, department, job title, contact information, etc.) to the server device 20.

[0051] Any method can be used to input the biometric information, profile, and other information. For example, the user takes an image of his or her face using a terminal such as a smartphone. Furthermore, the user uses the terminal to generate a text file or the like in which the profile is described. The user operates the terminal to transmit the information (face image, profile) to the server device 20. Alternatively, the user may input the necessary information to the server device 20 using an external storage device such as a Universal Serial Bus (USB) in which the information is stored.

[0052] Alternatively, the server device 20 may function as a WEB server, and the user may input the necessary information using a form provided by the server. Alternatively, a terminal for inputting the above information may be installed outside the floor, and the user may input the necessary information from the terminal to the server device 20. Alternatively, the user may input the necessary information to the server device 20 from the entrance management terminal 30-1.

[0053] The server device 20 updates a database that manages system users using the acquired user information (biometric information, profile, etc.). Details regarding updating the database will be described later, but the server device 20 updates the database through the following operations. In the following description, the database for managing users who use the system disclosed in the present application will be referred to as the "user database."

[0054] If the person corresponding to the acquired user information is a new user who is not registered in the user database, the server device 20 assigns an ID (Identifier) ​​to the user. In addition, the server device 20 generates a feature quantity that characterizes the acquired face image.

[0055] The server device 20 adds an entry to the user database, including the ID assigned to the new user, the feature amount generated from the face image, the face image of the user, a profile, etc. By the server device 20 registering the user information, the user is allowed to enter the free address floor.

[0056] Next, details of each device included in the locker management system according to the first embodiment will be described.

[0057] [Server device] Fig. 7 is a diagram showing an example of a processing configuration (processing module) of the server device 20 according to the first embodiment. Referring to Fig. 7, the server device 20 includes a communication control unit 201, a user registration unit 202, a matching unit 203, a user management unit 204, a locker management unit 205, and a storage unit 206.

[0058] The communication control unit 201 is a means for controlling communication with other devices. Specifically, the communication control unit 201 receives data (packets) from the biometric authentication-enabled locker 10. The communication control unit 201 also transmits data to the biometric authentication-enabled locker 10. The communication control unit 201 passes the data received from the other device to the other processing module. The communication control unit 201 transmits the data acquired from the other processing module to the other device. In this way, the other processing module transmits and receives data to and from the other device via the communication control unit 201.

[0059] The user registration unit 202 is a means for realizing the above-mentioned system user registration. The user registration unit 202 includes a plurality of sub-modules. FIG. 8 is a diagram showing an example of a processing configuration of the user registration unit 202. Referring to FIG. 8, the user registration unit 202 includes a user information acquisition unit 211, an ID generation unit 212, a feature generation unit 213, and an entry management unit 214.

[0060] The user information acquisition unit 211 is a means for acquiring the user information described above. The user information acquisition unit 211 acquires the biometric information and profile of each of a plurality of users who use the locker management system. More specifically, the user information acquisition unit 211 acquires the biometric information (e.g., face image) and profile (e.g., name, affiliation, etc.) of the system users. The system users may input the above information into the server device 20 from their own terminals, or may input the above information by operating the biometric authentication-enabled locker 10.

[0061] The user information acquisition unit 211 may provide a GUI or a form for inputting the above information. For example, the user information acquisition unit 211 displays an information input form as shown in Fig. 9 on a terminal operated by the user.

[0062] The system user inputs the information shown in Fig. 9. The system user also selects whether to register a new user in the system or to update information that has already been registered. After inputting all the information, the system user presses the "Send" button and inputs the biometric information and profile into the server device 20.

[0063] The user information acquisition unit 211 stores the acquired user information in the storage unit 206 .

[0064] The ID generation unit 212 is a means for generating an ID to be assigned to a system user. When the user information input by the system user is information related to a new registration, the ID generation unit 212 generates an ID for identifying the new user. For example, the ID generation unit 212 may calculate a hash value of the acquired user information (face image, profile), and use the hash value as the ID to be assigned to the user. Alternatively, the ID generation unit 212 may assign a unique value each time a user is registered, and use this value as the ID. In the following explanation, the ID generated by the ID generation unit 212 (the ID for identifying a system user) will be referred to as a "user ID."

[0065] The feature amount generating unit 213 is a means for generating a feature amount (a feature vector consisting of a plurality of feature amounts) that characterizes a face image from a face image included in the user information. Specifically, the feature amount generating unit 213 extracts feature points from the acquired face image. Note that since existing technology can be used for the feature point extraction process, a detailed description thereof will be omitted. For example, the feature amount generating unit 213 extracts the eyes, nose, mouth, etc. as feature points from the face image. Thereafter, the feature amount generating unit 213 calculates the position of each feature point and the distance between each feature point as feature amounts, and generates a feature vector consisting of a plurality of feature amounts (vector information that characterizes the face image).

[0066] The entry management unit 214 is a means for managing entries in the user database. When registering a new user in the database, the entry management unit 214 adds an entry to the user database, including the user ID generated by the ID generation unit 212, the feature amount generated by the feature amount generation unit 213, the face image, and the profile acquired from the user.

[0067] When updating information of a user already registered in the user database, the entry management unit 214 identifies the entry for which information is to be updated by an employee number or the like, and updates the user database using the acquired user information. At that time, the entry management unit 214 may update the difference between the acquired user information and the information registered in the database, or may overwrite each item in the database with the acquired user information. Similarly, with regard to the feature amount, the entry management unit 214 may update the database if there is a difference in the generated feature amount, or may overwrite the existing feature amount with the newly generated feature amount.

[0068] By operating the user registration unit 202, a user database (a database that stores a user ID for identifying a system user, biometric information, and a profile in association with each other) as shown in Fig. 10 is constructed. Note that the contents registered in the user database shown in Fig. 10 are merely examples, and are of course not intended to limit the information to be registered in the user database. It is sufficient for the user database to store at least the user ID for identifying a user and the biometric information in association with each other.

[0069] Returning to the explanation of Fig. 7, the matching unit 203 is a means for performing matching processing using biometric information (face image). When the matching unit 203 acquires a face image from the terminal 30 or the biometric authentication-enabled locker 10, the matching unit 203 executes matching processing using the acquired image.

[0070] For example, the matching unit 203 receives an authentication request from the entrance management terminal 30-1. Since the authentication request includes a facial image of the visitor (person to be authenticated), the matching unit 203 extracts the facial image from the authentication request. The matching unit 203 calculates feature amounts from the acquired facial image.

[0071] The matching unit 203 sets the feature amount calculated based on the face image acquired from the entrance management terminal 30-1 as the target of matching, and performs matching processing with the feature amount registered in the user database. More specifically, the matching unit 203 sets the calculated feature amount (feature vector) as the target of matching, and performs 1:N (N is a positive integer, the same applies below) matching with multiple feature vectors registered in the user database.

[0072] The matching unit 203 calculates the similarity between the feature to be matched and each of the multiple feature on the registration side. The similarity can be calculated using chi-square distance, Euclidean distance, etc. Note that the greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.

[0073] The matching unit 203 identifies a feature that has a similarity to the feature to be matched that is equal to or greater than a predetermined value and is the highest of the multiple feature amounts registered in the user database. The matching unit 203 refers to the user database and reads out the user ID corresponding to the identified feature amount.

[0074] The collation unit 203 passes the read user ID to the user management unit 204. At that time, the collation unit 203 notifies the user management unit 204 that the authentication request from the entrance management terminal 30-1 has been processed.

[0075] The collation unit 203 also performs the same process as above on the face image acquired from the exit management terminal 30-2 (the face image of the person exiting the floor) to identify the user ID corresponding to the face image. The collation unit 203 passes the identified user ID to the user management unit 204. At that time, the collation unit 203 notifies the user management unit 204 that the authentication request from the exit management terminal 30-2 has been processed.

[0076] If the matching process on the face image acquired from the terminal 30 fails, the matching unit 203 notifies the terminal 30 accordingly. The terminals 30 (entrance management terminal 30-1, exit management terminal 30-2) that receive the notification of authentication failure do not open the gate 31. The terminals 30 notify the user of the authentication failure and encourage them to take action such as contacting a specified contact point.

[0077] The matching unit 203 also performs the same process when it receives a locker unlocking request from a biometric authentication-enabled locker 10. The matching unit 203 refers to the user database and identifies the user ID corresponding to the biometric information included in the locker unlocking request. Specifically, the matching unit 203 extracts a face image from the request and performs matching processing using the user database. The matching unit 203 identifies the user ID of the corresponding person through the matching processing.

[0078] The collation unit 203 then checks whether the identified user ID is included in the visitor management database. If the user ID is included in the database, the collation unit 203 notifies the locker management unit 205 of the user request (storing or removing luggage) included in the locker unlock request and the identified user ID.

[0079] On the other hand, if the user ID is not included in the visitor management database, the matching unit 203 notifies the biometric authentication locker 10 of authentication failure. By confirming that the user ID is included in the visitor management database, the matching unit 203 limits the use of the locker to users who have entered the floor through proper procedures. The matching unit 203 also notifies the biometric authentication locker 10 of authentication failure if the person in the face image included in the locker unlock request is not registered in the user database. Upon receiving a notification of authentication failure, the biometric authentication locker 10 notifies the user accordingly.

[0080] In the first embodiment, a case will be described in which users of the biometric authentication-enabled lockers 10 are restricted to visitors to a free address floor. Therefore, the server device 20 manages visitors to the floor using a visitor management database, but if the use of the lockers is not restricted to visitors, the visitor management database does not need to be used.

[0081] The user management unit 204 is a means for managing users (visitors and visitors to the floor) in the free address floor. The user management unit 204 manages visitors using the user ID acquired from the collation unit 203.

[0082] The user management unit 204 manages the user ID in association with the date and time when the user entered the floor. Specifically, the user management unit 204 manages visitors using a visitor management database having fields for storing at least the above two pieces of information. For example, the user management unit 204 manages visitors using a visitor management database as shown in FIG. 11.

[0083] When the user management unit 204 receives a notification from the collation unit 203 that "the authentication request from the entrance management terminal 30-1 has been processed," the user management unit 204 adds the above entry (an entry including the user ID and the entry date and time) to the visitor management table. When the user management unit 204 receives a notification from the collation unit 203 that "the authentication request from the exit management terminal 30-2 has been processed," the user management unit 204 deletes the above entry from the visitor management table.

[0084] It should be noted that the visitor management database shown in Fig. 11 is an example, and in addition to the entry date and time, the status (work status) of the visitor may also be managed. For example, if the visitor is in a meeting, the visitor's status may be set to "in a meeting", and if the visitor is performing work at a round table or the like, the visitor's status may be set to "regular work". It should be noted that whether or not the visitor is "in a meeting" may be determined by analyzing an image acquired from the camera device 40.

[0085] Returning to Fig. 7, the locker management unit 205 is a means for managing each locker provided in the biometric authentication-enabled locker 10. The locker management unit 205 processes a "locker unlock request" received from the biometric authentication-enabled locker 10.

[0086] The locker management unit 205 uses a "locker management database" to manage each locker included in the biometric authentication-enabled locker 10. The locker management database stores the locker ID, locker attributes, and usage status in association with each other (see FIG. 12).

[0087] The locker ID is an ID for identifying each locker included in the biometric authentication locker 10. For example, the locker number is used as the locker ID. In Fig. 12, the locker numbers shown in Fig. 3 are used as the locker IDs.

[0088] The attribute field stores attribute information such as the characteristics of each locker. For example, the luggage storage capacity of each locker (locker size) is used as the locker's attribute value. Alternatively, the locker's position may be used as the attribute value. In FIG. 12(a), the size of each locker is set as the attribute value. In FIG. 12(b), the position of each locker (relative position in the biometric authentication-enabled locker 10) is set as the attribute value.

[0089] The usage status field stores the usage status of each locker (whether or not there is luggage; luggage present, luggage not present). If there is no luggage in the locker, nothing is set in this field, and if there is luggage in the locker, the user ID corresponding to that user is set. The example in Figure 12 shows that locker "R02" contains luggage for a user who has been assigned "ID01" as the user ID.

[0090] 12 is merely an example and is of course not intended to limit the information stored in the locker management database. The locker management database only needs to store at least the locker IDs of the biometric authentication-enabled lockers 10 and the usage status of each locker in association with each other. Alternatively, the locker management database may store multiple attribute values ​​(for example, the size and location of the locker).

[0091] If the user's request is to "store luggage", the locker management unit 205 refers to the locker management database and selects an available locker. The locker management unit 205 sets the user ID (the user ID identified by the matching process by the matching unit 203) in the usage status field of the selected locker. The locker management unit 205 notifies the biometric authentication-enabled locker 10 of the locker ID (locker number) of the selected locker, the user's request (storing luggage), etc.

[0092] If the user's request is to "remove luggage," the locker management unit 205 refers to the locker management database and identifies the locker ID in which the user ID acquired from the collation unit 203 is set in the usage status field. The locker management unit 205 notifies the biometric authentication-enabled locker 10 of the identified locker ID (locker number), the user's request (remove luggage), etc.

[0093] The locker management unit 205 notifies an error to the locker unlock request if the user's request is to "storage luggage" and there are no vacant lockers 10. The locker management unit 205 notifies an error to the locker unlock request if the user's request is to "remove luggage" and the user ID specified by the matching unit 203 is not set in the usage status field.

[0094] In addition, when the biometric authentication-enabled locker 10 stores the user's request (storing or removing luggage) set in the locker unlocking request, the locker management unit 205 does not need to notify the request to the biometric authentication-enabled locker 10. In other words, the response (response to the locker unlocking request) sent from the server device 20 to the biometric authentication-enabled locker 10 does not need to include the user's request.

[0095] In this way, when the request for locker use (user request) is to store luggage, the locker management unit 205 selects a locker for storing the luggage. Furthermore, the locker management unit 205 sets the identified user ID in the usage status field corresponding to the selected locker. The locker management unit 205 notifies the biometric authentication-enabled locker 10 of the locker ID of the selected locker. When the request for locker use is to retrieve luggage, the locker management unit 205 refers to the locker management database and identifies the locker ID for which the identified user ID is set in the usage status field. The locker management unit 205 notifies the biometric authentication-enabled locker 10 of the identified locker ID.

[0096] When the locker management unit 205 receives "luggage presence information" from a biometric authentication-enabled locker 10, it extracts the locker ID and information on the presence or absence of luggage (luggage status) from the received information. If the luggage status is "no luggage", the locker management unit 205 sets "free" to the usage status field corresponding to the locker ID.

[0097] If the luggage status is "baggage present", the locker management unit 205 confirms that a user ID is set in the usage status field corresponding to the locker ID. If the luggage status is "baggage present" and a user ID is not set in the usage status field corresponding to the locker ID, the locker management unit 205 notifies an administrator or the like of that fact. Since such a situation does not occur in normal operation, the administrator or the like checks the situation and takes appropriate action.

[0098] By transmitting and receiving "luggage presence / absence information" between the biometric authentication-enabled lockers 10 and the server device 20, inconsistencies are prevented between the state of each locker and the locker management database. For example, there may be cases where a user selects "storing luggage" and opens a locker, but closes the locker without storing any luggage. In this case, when the locker ID is notified to the biometric authentication-enabled locker 10, the user ID is set in the usage status field. However, since the luggage presence / absence information later reveals that the locker is empty, the locker management unit 205 can set the usage status of the corresponding locker to "empty." In other words, by updating the locker management database using the luggage presence / absence information, the locker management unit 205 prevents inconsistencies from occurring between the state of the locker and the database.

[0099] The storage unit 206 is a means for storing information necessary for the operation of the server device 20 .

[0100] [Biometric authentication lockers] Fig. 13 is a diagram showing an example of the processing configuration (processing module) of the biometric authentication-enabled locker 10 according to the first embodiment. Referring to Fig. 13, the biometric authentication-enabled locker 10 comprises a communication control unit 301, a user detection unit 302, a user request determination unit 303, a face image acquisition unit 304, an unlock request unit 305, a locker control unit 306, and a storage unit 307.

[0101] The communication control unit 301 is a means for controlling communication with other devices. Specifically, the communication control unit 301 receives data (packets) from the server device 20. The communication control unit 301 also transmits data to the server device 20. The communication control unit 301 passes the data received from the other devices to the other processing modules. The communication control unit 301 transmits the data acquired from the other processing modules to the other devices. In this way, the other processing modules transmit and receive data to and from the other devices via the communication control unit 301.

[0102] The user detection unit 302 is a means for detecting whether or not a user (locker user) is present in front of the device itself. The user detection unit 302 detects the presence or absence of a user by any means. For example, the user detection unit 302 detects the user by controlling the camera 12 and analyzing the acquired image.

[0103] The user detection unit 302 controls the camera 12 to capture an image in front of the device periodically or at a predetermined timing. The user detection unit 302 determines whether or not the captured image contains a human face image, and sets "user present" if a face image is included. Alternatively, the user detection unit 302 may detect the presence or absence of a user using a human presence sensor or the like. When a user is detected, the user detection unit 302 notifies the user request determination unit 303 of that effect.

[0104] The user request determination unit 303 is a means for determining a request from a locker user (a request related to using the locker; for example, storing or removing luggage). When the user request determination unit 303 receives a notification that "user present" from the user detection unit 302, it generates a GUI as shown in FIG. 4, for example. The user request determination unit 303 passes the request (storing or removing luggage) acquired by the GUI to the face image acquisition unit 304.

[0105] The facial image acquisition unit 304 is a means for controlling the camera 12 and acquiring a facial image (biometric information) of a visitor in front of the visitor. When the facial image acquisition unit 304 acquires a user's request from the user request determination unit 303, it captures an image of the user in front of the visitor. The facial image acquisition unit 304 extracts a facial image from the image data. The facial image acquisition unit 304 notifies the unlock request unit 305 of the facial image and the user's request (storing or removing luggage). It is preferable that the facial image acquisition unit 304 display as shown in FIG. 5 so that the user can recognize that a facial image is being acquired.

[0106] Since existing technologies can be used for the face image detection process and face image extraction process by the user detection unit 302 and the face image acquisition unit 304, detailed explanations will be omitted. For example, the face image acquisition unit 304 etc. may extract a face image (face region) from image data using a learning model learned by a CNN (Convolutional Neural Network). Alternatively, the face image acquisition unit 304 etc. may extract a face image using a method such as template matching.

[0107] The unlock request unit 305 is a means for requesting the server device 20 to notify the locker ID to be unlocked. The unlock request unit 305 transmits to the server device 20 a "locker unlock request" including the user's request (storing or removing luggage) and a facial image of the user.

[0108] The unlock request unit 305 receives a response to the request (a response including the user's request and the locker ID of the locker to be unlocked) from the server device 20. The unlock request unit 305 passes the acquired response to the locker control unit 306.

[0109] The locker control unit 306 is a means for controlling and managing the lockers included in the biometric authentication-enabled locker 10. The locker control unit 306 controls the locking and unlocking of each locker. For example, each locker is equipped with an electromagnetic lock, and the locker control unit 306 controls the locking and unlocking of each locker by controlling the power supply to the electromagnetic lock.

[0110] For example, a weight sensor is attached to each locker. Locker control unit 306 can determine whether or not luggage is stored in each locker based on the output of the weight sensor. Any means can be used for locker control unit 306 to determine the presence or absence of luggage. For example, a small camera can be installed in each locker, and locker control unit 306 can determine the presence or absence of luggage by analyzing images obtained from the camera.

[0111] The locker control unit 306 unlocks the locker based on the response obtained from the server device 20. Specifically, the locker control unit 306 unlocks the locker corresponding to the locker ID obtained from the unlock request unit 305. At that time, the locker control unit 306 displays a message according to the user's request (storing or removing luggage). For example, the locker control unit 306 displays a message as shown in FIG. 6(a) or FIG. 6(b).

[0112] The locker control unit 306 detects that the user has closed the locker by any method. For example, the locker control unit 306 detects that the locker has been closed by using a contact sensor or the like.

[0113] When a locker is closed, the locker control unit 306 checks the status of the locker (whether or not there is luggage). The locker control unit 306 generates "luggage presence / absence information" including information on the presence / absence of luggage (luggage status) and transmits it to the server device 20. Specifically, if there is no luggage in a closed locker, the locker control unit 306 sets the luggage status to "no luggage; luggage not present" and transmits the luggage presence / absence information including the locker ID and the luggage status to the server device 20. If there is luggage in a closed locker, the locker control unit 306 sets the luggage status to "luggage present; luggage present" and transmits the luggage presence / absence information including the locker ID and the luggage status to the server device 20.

[0114] The storage unit 307 is a means for storing information necessary for the operation of the biometric authentication locker 10.

[0115] [Admission management terminal] 14 is a diagram showing an example of a processing configuration (processing module) of the entrance management terminal 30-1. Referring to FIG. 14, the entrance management terminal 30-1 includes a communication control unit 401, a face image acquisition unit 402, a gate control unit 403, and a storage unit 404.

[0116] The basic functions and operations of the communication control unit 401, facial image acquisition unit 402, and memory unit 404 of the entrance management terminal 30-1 can be the same as the corresponding processing modules of the biometric authentication-enabled locker 10, so detailed explanations will be omitted. Also, the gate control unit 403 is a means for controlling the opening and closing of the gate 31 in response to the authentication result from the server device 20.

[0117] The processing configuration (processing module) of the exit management terminal 30-2 can be the same as that of the entrance management terminal 30-1, so a description corresponding to FIG. 14 will be omitted.

[0118] [Operation of the locker management system] Next, the operation of the locker management system according to the first embodiment will be described.

[0119] Fig. 15 is a sequence diagram showing an example of the operation of the locker management system according to the first embodiment. Fig. 15 is a sequence diagram showing an example of the system operation when the biometric authentication-enabled locker 10 is used. It is assumed that the system users have been registered beforehand prior to the operation of Fig. 15.

[0120] The biometric authentication compatible locker 10 detects the user (step S01).

[0121] When the biometric authentication-enabled locker 10 detects the presence of a user, it determines the request of the user (putting or taking out luggage) (step S02).

[0122] The biometric authentication-enabled locker 10 acquires the biometric information (face image) of the user (step S03).

[0123] The biometric authentication-enabled locker 10 transmits a locker unlock request, which includes the user's request and the biometric information, to the server device 20 (transmitting unlock request; step S04).

[0124] The server device 20 extracts the biometric information from the locker unlocking request, and executes a matching process using the extracted biometric information (step S11).

[0125] The server device 20 uses the user ID identified by the collation process, the locker management database, and the user's request (storing or retrieving luggage) to select a locker to be unlocked (step S12).

[0126] The server device 20 transmits a response including the locker ID of the selected locker and the user's request to the biometric authentication-enabled locker 10 (step S13).

[0127] The biometric authentication-enabled locker 10 extracts the locker ID from the acquired response, and unlocks the locker corresponding to the locker ID (step S05).

[0128] When it is detected that the unlocked locker has been closed, the biometric authentication-enabled locker 10 checks whether or not there is luggage in the locker, and transmits the luggage presence / absence information to the server device 20 (step S06).

[0129] The server device 20 updates the locker management database based on the luggage presence / absence information (step S14).

[0130] As described above, the biometric authentication-enabled locker 10 according to the first embodiment acquires a face image of the locker user, and transmits the user's request (storing or removing luggage) and the face image to the server device 20 as a locker unlocking request. The server device 20 identifies the locker user by a matching process using the biometric information included in the locker unlocking request, and identifies the locker to be unlocked based on the user's request included in the locker unlocking request. The server device 20 includes the locker ID of the identified locker in a response to the locker unlocking request and transmits it to the biometric authentication-enabled locker 10. The biometric authentication-enabled locker 10 unlocks the locker corresponding to the acquired locker ID. In this way, the locker management system according to the first embodiment unlocks the locker by the biometric authentication of the user, improving the convenience of the locker user. This is because the locker user does not need to insert a fee (coin) or lock the lock with a physical key, which was necessary in the existing locker system, every time he or she temporarily leaves the free address floor.

[0131] [Second embodiment] Next, the second embodiment will be described in detail with reference to the drawings.

[0132] In the first embodiment, a case has been described in which the biometric authentication-enabled locker 10 acquires a user's request (storing or removing luggage). When using the method (method of acquiring a user's request) as described in the first embodiment, the user needs to touch the display panel 11 of the biometric authentication-enabled locker 10. When a user is planning to store a small item in the locker, the user can input information into the biometric authentication-enabled locker 10 with one hand. However, when a user is planning to store a large item in the locker, both hands of the user are often occupied. In such a case, it is difficult for the user to input information into the biometric authentication-enabled locker 10.

[0133] In the second embodiment, a case will be described in which the user does not directly touch the display panel 11 of the biometric authentication locker 10, and the system determines the user's request (storing or removing luggage).

[0134] The configuration of the locker management system according to the second embodiment can be the same as that of the first embodiment, so the explanation corresponding to Fig. 2 will be omitted. Also, the processing configuration of the biometric authentication-enabled locker 10, server device 20, etc. according to the second embodiment can be the same as that of the first embodiment, so the explanation will be omitted. The following explanation will focus on the differences between the first and second embodiments.

[0135] The user request determination unit 303 according to the second embodiment determines a request for locker use based on the behavior of the locker user (characteristic behavior of the user that is predetermined by the system). For example, the user request determination unit 303 determines the user's request (putting or taking out luggage) by analyzing a facial image of the user in front of the locker user.

[0136] The user request determination unit 303 determines the user's request based on changes in the locker user's face. For example, the user request determination unit 303 determines the user's request based on which eye the user is closed. For example, the user request determination unit 303 determines "putting luggage away" if the right eye is closed, and "removing luggage" if the left eye is closed. In this case, the user request determination unit 303 displays, for example, a message as shown in FIG. 16.

[0137] The user request determination unit 303 controls the camera 12 to capture an image of the user. The user request determination unit 303 analyzes the obtained image and determines which eye the user has closed. The user request determination unit 303 makes this determination using, for example, a template or the like, and obtains the user's request (storing or removing luggage).

[0138] Alternatively, the user request determination unit 303 may determine the user's request (putting away or taking out luggage) according to the direction of the user's face (facing right, facing left; facing up, facing down).

[0139] [Modification of the second embodiment] The user request determination unit 303 may determine a request (storing or removing luggage) based on a larger action of the user. For example, the user request determination unit 303 may determine a user request (storing or removing luggage) based on the direction in which the user walks toward the device.

[0140] The user request determination unit 303 analyzes the images obtained from the camera 12 and calculates the trajectory of the user's movement. Specifically, the user request determination unit 303 extracts multiple face images of the same person from a video or multiple still images. The user request determination unit 303 extracts images of the same person from each of multiple frame images forming a video using a known image processing algorithm that tracks the same object (person) across different frames. The user request determination unit 303 identifies the movement direction of the extracted same person from the change in position within the image. The user request determination unit 303 determines the user's request (storing or removing luggage) based on the identified movement direction.

[0141] For example, as shown in Fig. 17, when a user approaches from the right side of the biometric authentication-enabled locker 10, the user request determination unit 303 determines that the user's request is to "put away luggage." On the other hand, when a user approaches from the left side of the biometric authentication-enabled locker 10, the user request determination unit 303 determines that the user's request is to "take out luggage."

[0142] The correspondence between the user's movement direction and the request (storing or taking out luggage) may be determined according to the positional relationship between the biometric authentication locker 10 and other components (floor components; for example, entrances, desks, conference rooms, etc.). For example, if a user comes from the direction of a desk, it is assumed that the user will often be putting away luggage, so the direction of movement is determined as "storing luggage." On the other hand, if a user comes from the entrance, it is assumed that the user will often be taking out luggage stored in the biometric authentication locker 10, so the direction of movement is determined as "taking out luggage."

[0143] In addition, when the user's request (storing or removing luggage) is automatically determined based on the direction of movement, it is desirable to provide a mechanism that allows the user to correct the automatically determined result.

[0144] The determination of the user's movement direction may be performed by the server device 20. The server device 20 calculates the movement of the user within the floor in real time by analyzing images obtained from the camera device 40 that overlooks the entire floor. When the server device 20 identifies a user moving within the floor and moving toward the biometric authentication-enabled locker 10, it notifies the biometric authentication-enabled locker 10 of the movement direction of the user. The biometric authentication-enabled locker 10 acquires the user's request (storing or retrieving luggage) based on the notification.

[0145] As described above, the biometric authentication locker 10 according to the second embodiment predicts the user's request (storing or removing luggage) based on the user's behavior (characteristic behavior of the user). As a result, a user carrying a large amount of luggage can communicate his or her request to the biometric authentication locker 10 without touching the locker. This further improves the convenience of the biometric authentication locker 10.

[0146] [Third embodiment] Next, the third embodiment will be described in detail with reference to the drawings.

[0147] In the first embodiment, a case where the server device 20 selects any available locker is described. In the third embodiment, a case where the server device 20 selects a locker suitable for a user from among a plurality of available lockers is described. Note that the third embodiment is a form in which a locker for storing luggage is selected from among available lockers. Therefore, in the third embodiment, a case where the user's request is to "store luggage" is described.

[0148] The configuration of the locker management system according to the third embodiment can be the same as that of the first embodiment, so the explanation corresponding to Fig. 2 will be omitted. In addition, the processing configuration of the server device 20 etc. according to the third embodiment can also be the same as that of the first embodiment, so the explanation will be omitted. The following explanation will focus on the differences between the first to third embodiments.

[0149] When a biometric authentication-enabled locker 10 according to the third embodiment transmits a locker unlocking request, the request includes accompanying information about the user. Examples of the accompanying information included in the locker unlocking request include information about the user's height and the user's baggage.

[0150] Fig. 18 is a diagram showing an example of the processing configuration (processing module) of the biometric authentication-enabled locker 10 according to the third embodiment. Referring to Fig. 18, an accompanying information generating unit 308 has been added to the configuration of the biometric authentication-enabled locker 10 according to the first embodiment.

[0151] The associated information generating unit 308 generates associated information related to a user (locker user). For example, the associated information generating unit 308 generates "information related to the user's height" as the associated information. The associated information generating unit 308 estimates the user's height using any method. For example, the associated information generating unit 308 may estimate the user's height by analyzing an image obtained from the camera 12. In this case, the associated information generating unit 308 estimates the user's height according to the position of the face area in the entire image data. Specifically, if the face area is included in the upper area of ​​the image data, the associated information generating unit 308 estimates that the user is "tall". On the other hand, if the face area is included in the lower area of ​​the image data, the associated information generating unit 308 estimates that the user is "short".

[0152] Alternatively, a plurality of distance sensors may be arranged vertically at a predetermined interval, and the plurality of distance sensors may be used to estimate (measure) height. That is, the associated information generating unit 308 may estimate height based on the output of the distance sensors. The associated information generating unit 308 monitors the output of each of the plurality of sensors, and measures the user's height from the difference in the output value of each sensor. If the user is short, the number of sensors that react to the user is small, and if the user is tall, the number of sensors that react to the user is large. The associated information generating unit 308 estimates the user's height according to the change in sensor output caused by the difference in the user's height.

[0153] The associated information generating unit 308 passes the information about the height of the user to the unlock request unit 305 .

[0154] The unlock request unit 305 transmits a locker unlock request including the associated information to the server device 20 .

[0155] The locker management unit 205 of the server device 20 refers to the associated information included in the locker unlock request and selects a locker to provide to the user. At that time, the locker management unit 205 refers to the attribute field and the associated information in the locker management database to select a locker.

[0156] Specifically, the locker management unit 205 selects a locker based on information about the height of the user. For example, if the user is estimated to be tall, the locker management unit 205 preferentially selects a locker located at the top of the available lockers. In the example of Fig. 12(b), lockers with locker IDs "R01" and "R04" are preferentially selected.

[0157] [Modification of the third embodiment] The biometric authentication-enabled lockers 10 may select lockers according to the size of the luggage that the user intends to store in the locker.

[0158] The associated information generating unit 308 analyzes an image showing the user and the luggage to estimate the size of the luggage. For example, the associated information generating unit 308 estimates the size of the luggage by a method such as template matching. The associated information generating unit 308 may estimate the size of the luggage by using a learning model generated by machine learning such as AI (Artificial Intelligence).

[0159] The biometric authentication-enabled locker 10 transmits a locker unlock request to the server device 20, which includes information on the size of the luggage (information on the size of the luggage carried by the user) as accompanying information.

[0160] The locker management unit 205 refers to the locker management database and selects a locker that is suitable for the size of the luggage to be stored. For example, when the locker management unit 205 acquires accompanying information that the luggage size is "small", it preferentially selects lockers with an attribute value of "small size" from among available lockers. In the example of FIG. 12(a), lockers with locker IDs of "R01" and "R04" are preferentially selected.

[0161] The biometric authentication-enabled locker 10 may provide the user with an interface that allows input of information regarding the size of the luggage. In other words, the server device 20 may select a locker based on accompanying information generated by the user's self-declaration (declaration regarding the size of the luggage).

[0162] The server device 20 selects a locker only when the user's request is to "store luggage." Therefore, it is sufficient for the associated information generating unit 308 to generate associated information only when the user's request is to "store luggage."

[0163] As described above, the biometric authentication-enabled locker 10 according to the third embodiment generates associated information for a user and transmits it to the server device 20. The server device 20 uses the received associated information as a clue to grasp the situation and characteristics of the locker user, and selects a locker suitable for that locker user. The biometric authentication-enabled locker 10 unlocks the locker (the locker selected by the server device 20 using the associated information). As a result, the convenience of the biometric authentication-enabled locker 10 is further improved.

[0164] [Fourth embodiment] Next, a fourth embodiment will be described in detail with reference to the drawings.

[0165] In the fourth embodiment, a case will be described in which, when a visitor leaves his / her baggage in a biometric authentication-enabled locker 10 when leaving a free address floor, the visitor is notified of this.

[0166] The configuration of the locker management system according to the fourth embodiment can be the same as that of the first embodiment, so the explanation corresponding to Fig. 2 will be omitted. Also, the processing configuration of the biometric authentication-enabled locker 10, server device 20, etc. according to the fourth embodiment can be the same as that of the first embodiment, so the explanation will be omitted. The following explanation will focus on the differences between the first to fourth embodiments.

[0167] When the user management unit 204 of the server device 20 receives an authentication request from the exit management terminal 30-2, it determines whether or not the user ID identified by the authentication is registered in the locker management database.

[0168] If the user ID is registered in the locker management database, the user management unit 204 notifies the exit management terminal 30-2 of that fact.

[0169] The gate control unit 403 of the exit management terminal 30-2 that has received the above notification notifies the exiting person that luggage is in the locker before opening the gate 31. For example, the gate control unit 403 displays a message as shown in Fig. 19 to notify the exiting person of the presence of luggage stored in the locker.

[0170] If the person is only leaving the floor temporarily, he or she ignores the notification and leaves the floor. If the person determines that he or she has left his or her baggage behind in the biometric authentication locker 10, he or she returns to the biometric authentication locker 10 and retrieves the baggage.

[0171] Alternatively, the exit management terminal 30-2 may display a GUI for confirming the user's intention, and control the opening and closing of the gate 31 based on information obtained from the GUI. For example, the gate control unit 403 displays as shown in Fig. 20. If the user selects temporary exit, the gate control unit 403 opens the gate 31.

[0172] As described above, the locker management system according to the fourth embodiment utilizes the exit management terminal 30-2 that controls the gate that restricts the exit of users. The exit management terminal 30-2 transmits biometric information of the exiting person (a person exiting from a floor) to the server device 20. The server device 20 identifies the user ID of the exiting person through a matching process using the biometric information of the exiting person. When the user ID of the identified exiting person is set in the usage status field, the server device 20 notifies the exit management terminal 30-2 about the luggage left behind. As a result, the exiting person will not leave his / her luggage in the locker and go home (unintentionally go home). This further improves the convenience of the locker management system.

[0173] [Fifth embodiment] Next, the fifth embodiment will be described in detail with reference to the drawings.

[0174] In the fifth embodiment, a case where equipment is stored in a biometric authentication-enabled locker 10 will be described.

[0175] The configuration of the locker management system according to the fifth embodiment can be the same as that of the first embodiment, so the explanation corresponding to Fig. 2 will be omitted. In addition, the processing configuration of the biometric authentication-enabled locker 10 etc. according to the fifth embodiment can also be the same as that of the first embodiment, so the explanation will be omitted. The following explanation will focus on the differences between the first to fifth embodiments.

[0176] Fig. 21 is a diagram showing an example of a processing configuration (processing module) of the server device 20 according to the fifth embodiment. Referring to Fig. 21, an equipment management unit 207 is added to the configuration of the server device 20 according to the first embodiment.

[0177] The equipment management unit 207 is a means for managing equipment stored in the lockers. The equipment management unit 207 acquires reservation information regarding the use of equipment by any means. The equipment management unit 207 displays, for example, an information input form as shown in Fig. 22 on the terminal operated by the user.

[0178] The person reserving the equipment inputs the information shown in FIG. 22. The equipment management unit 207 updates the equipment management database based on the information obtained from the person reserving (equipment reservation information). Specifically, the equipment management unit 207 searches the user database using the name and employee number of the person reserving as keys to identify the corresponding user ID. The equipment management unit 207 adds an entry including the identified user ID, department, equipment (reserved equipment), and usage period to the equipment management database. For example, an equipment management database as shown in FIG. 23 is constructed.

[0179] Moreover, the locker management database according to the fifth embodiment stores the lockers in which the equipment is stored. For example, as shown in Fig. 24, the locker management database stores the equipment and the locker ID of the locker in which the equipment is stored in association with each other.

[0180] The equipment management unit 207 checks the equipment management database periodically or at a predetermined timing. More specifically, the equipment management unit 207 checks the usage period field of the database and identifies reservations (entries) whose usage period is approaching. For example, the equipment management unit 207 identifies an entry whose usage period will start after a predetermined time has elapsed (e.g., 5 minutes). The equipment management unit 207 sets the ID of the person who made the reservation in the usage status field (a field in the locker management database) of the locker that stores the equipment of the identified entry. For example, in the example of FIG. 23, when the start time of use of equipment "B01" approaches, "ID21", which is the user ID of the person who made the reservation, is set in the usage status field of the locker that stores equipment "B01" (see the first row of FIG. 24).

[0181] When the user's request is to "store luggage," the locker management unit 205 does not select a locker that contains equipment, but selects a locker that does not contain equipment. In the example of Fig. 24, the locker with the locker ID "R04" is selected.

[0182] When the user's request is to "take out luggage," the locker management unit 205 identifies a locker to notify the biometric authentication-enabled locker 10 of, as in the first embodiment. Specifically, the locker management unit 205 identifies the usage status field in which the user ID identified by the matching process is stored, and notifies (responds to) the biometric authentication-enabled locker 10 of the corresponding locker ID. Therefore, when the reserver inputs an operation for "taking out luggage" to the biometric authentication-enabled locker 10, the locker containing the equipment opens.

[0183] When the usage period of the reservation information has elapsed, the locker management unit 205 deletes the user ID set in the usage status field. Even if the person who made the reservation attempts to use the equipment after the usage period has elapsed, the locker storing the equipment will not open because the user ID of the user has been deleted.

[0184] The biometric authentication-enabled locker 10 may provide the user with an interface that distinguishes between normal baggage retrieval and reserved equipment retrieval. For example, the user request determination unit 303 may obtain the user's request (storing, retrieval, retrieval of equipment) using an interface as shown in FIG.

[0185] The request is sent to the server device 20. The locker management unit 205 of the server device 20 may identify the locker to be unlocked in response to the user's request (removal, removal of equipment). For example, if the person who made the reservation has reserved equipment and stored their own luggage in the locker, identifying the locker based on the request is effective. Specifically, if the same user ID is set in the usage status field of the locker management database, a locker that does not store equipment will be unlocked in the normal case of "removing luggage." On the other hand, if the request obtained from the biometric authentication-enabled locker 10 is "removal of equipment," a locker that stores equipment will be unlocked.

[0186] [Modification of the fifth embodiment] In the fifth embodiment, a case has been described in which a reserving party inputs "equipment reservation information" to the server device 20. In a modified example of the fifth embodiment, a case will be described in which the server device 20 manages a user (equipment borrower) who has taken equipment out of a locker.

[0187] In the fifth embodiment, it is assumed that the lockers storing the equipment are unlocked.

[0188] When a locker storing an item is opened, the facial image acquisition unit 304 of the biometric authentication locker 10 acquires a facial image of the person who opened the locker. The facial image acquisition unit 304 passes the acquired facial image to the locker control unit 306.

[0189] The locker control unit 306 transmits to the server device 20 an "equipment management request" including the locker ID of the locker opened by the equipment borrower and the acquired facial image.

[0190] The matching unit 203 of the server device 20 receives the equipment management request and performs matching processing using the acquired face image. The matching unit 203 identifies the user ID of the equipment borrower identified by the matching processing, and passes the locker ID included in the equipment management request to the equipment management unit 207.

[0191] The equipment management unit 207 searches the locker management database using the locker ID as a key to identify the equipment contained in the locker opened by the equipment borrower. The equipment management unit 207 manages the identified equipment by associating it with the user ID of the equipment borrower. For example, the equipment management unit 207 manages the rental of equipment using an equipment rental database that stores equipment and user IDs.

[0192] In this way, in the modified example of the fifth embodiment, the user who has taken out the equipment can be identified from the image captured by the camera 12, and the rental of the equipment can be managed using the rental table (equipment rental database).

[0193] As described above, the server device 20 according to the fifth embodiment includes an equipment management unit 207 that manages equipment stored in the biometric authentication-enabled lockers 10, and an equipment management database. The equipment management database stores the user ID of the user who reserved the equipment, the reserved equipment, and the usage period of the reserved equipment in association with each other. Before the usage period of the reserved equipment arrives, the equipment management unit 207 sets the user ID of the user who reserved the equipment in the usage status field of the locker storing the reserved equipment. In this way, the locker user can borrow equipment by performing the operations described in the first embodiment, improving the convenience of the locker management system.

[0194] Furthermore, in the locker management system according to the fifth embodiment, the unlocking of the locker is controlled in conjunction with the equipment usage period, so that the equipment can be prevented from being used outside the reserved time.

[0195] [Sixth embodiment] Next, the sixth embodiment will be described in detail with reference to the drawings.

[0196] In the sixth embodiment, a case will be described in which a user who stores luggage (hereinafter referred to as a luggage storer) and a user who removes luggage (hereinafter referred to as a luggage remover) are different.

[0197] The configuration of the locker management system according to the sixth embodiment can be the same as that of the first embodiment, so the explanation corresponding to Fig. 2 will be omitted. Also, the processing configuration of the biometric authentication-enabled locker 10, server device 20, etc. according to the sixth embodiment can be the same as that of the first embodiment, so the explanation will be omitted. The following explanation will focus on the differences between the first to sixth embodiments.

[0198] The user request determination unit 303 of the biometric authentication-enabled locker 10 can obtain information on the person who will pick up the luggage, in addition to obtaining the user's request as described above. Specifically, the user request determination unit 303 displays a screen as shown in Fig. 26, allowing the user to specify the person who will pick up the luggage.

[0199] For example, when a user presses the "storage with designated person to pick up" button, the user request determination unit 303 displays a screen as shown in Fig. 27. When the user sees a screen as shown in Fig. 27, he or she inputs the name of the person who can pick up the package in the character input area. After inputting the name of the person who will pick up the package, the user presses the confirm button.

[0200] If the user desires "storage with designated person to pick up," the user request determination unit 303 sets the user's request to "storage with designated person to pick up" and notifies the unlock request unit 305 together with the name of the designated person to pick up the luggage.

[0201] The unlock request unit 305 transmits to the server device 20 a locker unlock request including the face image of the person putting the luggage, the user's request (storage with designated person for picking up the luggage), and the name of the person for picking up the luggage.

[0202] The collation unit 203 of the server device 20 acquires a face image from the locker unlock request and executes collation processing. The collation unit 203 notifies the locker management unit 205 of the user ID (user ID of the person storing the luggage) identified by the collation processing, the user request (storage with designated person to retrieve the luggage), and the name of the person to retrieve the luggage.

[0203] When the user's request is for "storage with designated retriever," the matching unit 203 does not need to notify the locker management unit 205 of the user ID identified by the matching process. This is because the matching process by the matching unit 203 is a process for ensuring that the person attempting to store luggage in the biometric authentication-enabled locker 10 is registered in the system. In other words, when a user who is not registered in the system is permitted to use a locker, matching process using a facial image of the user is not necessary.

[0204] When the user's request is "storage with designated person for collection," the locker management unit 205 searches the user database using the name of the person for collection as a key to identify the corresponding user ID. The locker management unit 205 refers to the locker management database and selects a locker for storing the luggage from among available lockers. The locker management unit 205 sets the user ID corresponding to the name of the person for collection in the usage status field of the selected locker.

[0205] When a parcel recipient (a user designated as the parcel recipient) approaches the biometric authentication-enabled locker 10, the biometric authentication-enabled locker 10 transmits a locker unlock request including the user's facial image and "remove parcel" to the server device 20. The server device 20 identifies the user ID through matching processing using the facial image, and identifies the locker to be unlocked. Since the locker management database contains an entry storing the user ID of the person picking up the parcel, the server device 20 notifies the biometric authentication-enabled locker 10 of the locker ID of that entry. The biometric authentication-enabled locker 10 unlocks the locker with the notified locker ID. The person picking up the parcel can then remove the parcel from the locker.

[0206] As described above, the biometric authentication-enabled locker 10 according to the sixth embodiment transmits a locker unlock request including information about the person retrieving luggage (a person who can retrieve luggage stored in a locker) to the server device 20. The server device 20 identifies the user ID of the person retrieving luggage based on the information about the person retrieving luggage, and sets the user ID of the person retrieving luggage in the usage status field corresponding to the locker storing the luggage. As a result, when the person retrieving luggage moves in front of the biometric authentication-enabled locker 10, authentication processing using the facial image of the person retrieving luggage is successful. The person retrieving luggage can retrieve luggage stored by another person (luggage storer). This allows luggage to be handed over with a time lag, improving the convenience of the locker management system.

[0207] Next, the hardware of each device constituting the entrance / exit management system will be described.

[0208] The server device 20 can be configured by an information processing device (so-called a computer), and has the configuration exemplified in Fig. 28. For example, the server device 20 has a processor 311, a memory 312, an input / output interface 313, and a communication interface 314. The components such as the processor 311 are connected by an internal bus or the like, and are configured to be able to communicate with each other.

[0209] However, the configuration shown in Fig. 28 is not intended to limit the hardware configuration of the server device 20. The server device 20 may include hardware not shown, and may not include the input / output interface 313 as necessary. In addition, the number of processors 311 and the like included in the server device 20 is not intended to be limited to the example shown in Fig. 28, and for example, the server device 20 may include multiple processors 311.

[0210] The processor 311 is, for example, a programmable device such as a central processing unit (CPU), a micro processing unit (MPU), or a digital signal processor (DSP). Alternatively, the processor 311 may be a device such as a field programmable gate array (FPGA), or an application specific integrated circuit (ASIC). The processor 311 executes various programs including an operating system (OS).

[0211] The memory 312 is a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), etc. The memory 312 stores an OS program, application programs, and various data.

[0212] The input / output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display, etc. The input device is, for example, a keyboard, a mouse, etc. that accepts user operations.

[0213] The communication interface 314 is a circuit, a module, etc. that communicates with other devices. For example, the communication interface 314 includes a network interface card (NIC).

[0214] The functions of the server device 20 are realized by various processing modules. For example, the processing modules are realized by the processor 311 executing a program stored in the memory 312. The program can be recorded in a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. The program can be downloaded via a network or updated using a storage medium storing the program. The processing modules may also be realized by a semiconductor chip.

[0215] The basic hardware configuration of the biometric authentication lockers 10, terminals 30, etc. is the same as that of the server device 20, so a detailed explanation will be omitted. For example, the biometric authentication lockers 10 may be equipped with a display panel 11, a camera 12, etc.

[0216] The server device 20 is equipped with a computer, and the functions of the server device 20 can be realized by having the computer execute a program. Similarly, the biometric authentication-enabled locker 10 is equipped with a computer, and the functions of the biometric authentication-enabled locker 10 can be realized by having the computer execute a program. Also, the server device 20 and the biometric authentication-enabled locker 10 may work together to execute the locker management method, or the biometric authentication-enabled locker 10 may execute the locker management method independently.

[0217] [Variations] It should be noted that the configuration, operation, etc. of the locker management system described in the above embodiment are merely examples and are not intended to limit the system configuration, etc.

[0218] In the above embodiment, the server device 20 stores biometric information and identifies the locker user. However, the biometric authentication-enabled locker 10 may store the biometric information and identify the locker user. In other words, some or all of the functions of the server device 20 may be realized by the biometric authentication-enabled locker 10.

[0219] The profile of a system user (user attribute values) may be input using a scanner or the like. For example, the user inputs an image of his / her business card to the server device 20 using a scanner. The server device 20 performs an optical character recognition (OCR) process on the acquired image. The server device 20 may determine the user profile based on the obtained information.

[0220] In the above embodiment, a case has been described in which biometric information related to a "face image" is transmitted from the biometric authentication-enabled locker 10 and the terminal 30 to the server device 20. However, biometric information related to "feature amounts generated from a face image" may also be transmitted from the biometric authentication-enabled locker 10 etc. to the server device 20. The server device 20 may use the acquired feature amounts (feature vector) to execute a matching process against the feature amounts registered in the user database.

[0221] In the above embodiment, it has been described that a user who leaves a free address floor with their luggage stored in the biometric authentication-enabled locker 10 is notified of this fact. In such a case, the server device 20 may send an email to the user who leaves (has left) their luggage in the locker, stating that their luggage is still in the locker.

[0222] In the above embodiment, the case where one user reserves equipment has been described. However, equipment reservations may be made in groups. For example, the person reserving the equipment may input the department to which the person belongs as the "equipment reserving person" to the server device 20. In this case, the server device 20 refers to the user database and identifies the user ID (at least one or more user IDs) of the entered department. The server device 20 sets the identified at least one or more user IDs in the "user ID" field of the equipment management database. When the equipment usage period approaches, the server device 20 sets the one or more user IDs set in the user ID field in the usage status field of the locker management database (see FIG. 24). Multiple user IDs (multiple user IDs of users in the same department) are set in the usage status field. If the user ID identified by biometric authentication is included in the multiple user IDs, the server device 20 instructs the biometric authentication-enabled locker 10 to unlock the corresponding locker. As a result, even if the person reserving the equipment and the user (borrower) of the equipment are different, the equipment can be rented out. In other words, equipment lending is managed on a group (department) basis, and only employees of authorized departments can use the equipment.

[0223] In the above embodiment, the rental of equipment via a locker has been described. The rental of the equipment may be linked to the billing process associated with the rental of the equipment. For example, the server device 20 may bill the person who made the reservation for the equipment or the person who borrows the equipment for the cost of using the equipment. For example, the user registers information on the payment method (e.g., information on a credit card) when registering the user in the system. The server device 20 refers to the user database and identifies the billing destination for the equipment usage fee from the user ID of the equipment borrower, etc. The server device 20 executes the necessary billing process for the identified billing destination.

[0224] Alternatively, the fee for the use of the equipment may be charged on a department basis. The server device 20 refers to the user database to identify the department to which the equipment borrower belongs. The server device 20 may charge the expenses for the use of the equipment to the identified department. In this case, the server device 20 may execute the necessary charging process by, for example, referring to table information that stores the department and its billing destination.

[0225] The server device 20 may control so that only users who have reserved a conference room installed on a free address floor can use the biometric authentication-enabled lockers 10. Specifically, the server device 20 may obtain information on the conference participants (such as the names of the conference participants) and set the user IDs of the conference participants in the usage status field of the locker management database.

[0226] The server device 20 may manage equipment rentals and the like in conjunction with reservations of conference rooms and the like. For example, the server device 20 acquires detailed information about a conference held in a conference room on a free address floor. For example, the server device 20 acquires information about the conference participants, the conference room number, the conference period, the conference theme, and the like. The server device 20, for example, identifies equipment that is in line with the theme of the conference, and sets the user ID of the conference participant to the user of the identified equipment (user ID field of the equipment management database). The server device 20 also sets the conference period in the usage period field of the database. With this kind of response, the equipment in line with the theme of the conference is reserved just before the conference starts, and when one of the conference participants approaches the biometric authentication-enabled locker 10, the necessary equipment can be taken out. That is, the locker management system disclosed in the present application automatically reserves equipment suitable for the theme (agenda) of the conference, and enables the conference participants to use the equipment. The conference participants do not need to make two reservations, that is, the conference room reservation and the equipment reservation, and can easily borrow the necessary equipment.

[0227] The server device 20 may perform billing for consumables used in a conference and food and drink (e.g., tea, sweets, etc.) provided to guests. For example, the server device 20 identifies a person who opens a locker containing sweets, etc., by face recognition (identifies a user ID). The server device 20 bills the identified user or the department to which the user belongs for the cost of the sweets, etc.

[0228] The server device 20 may link the use of lockers and the use of a reserved PC for a conference room (a PC installed on a free address floor). The server device 20 refers to the locker management database and identifies a user whose user ID is set in the usage status field. The server device 20 may obtain a login request from the PC, and when the ID included in the login request matches the identified user ID, may permit the user to use the PC (may approve the login request). The server device 20 may also permit the user who has reserved the conference room to use the PC in the same manner.

[0229] In the above embodiment, a case has been described in which one user is designated as the person who can retrieve luggage stored in a locker. However, multiple luggage retrievers may be designated. Alternatively, the luggage putter may be designated as a "department" as the "luggage retriever." In this case, the server device 20 may set the user ID of a user belonging to the designated department in the usage status field of the locker management database. Alternatively, a conference participant may be designated as the luggage retriever. In this case, the server device 20 may check the information about the conference and set the user ID of a participant attending the same conference in the usage information field of the locker management database. In this way, the effort of the luggage putter can be reduced by designating the luggage retriever according to the attributes, etc. of the luggage putter.

[0230] By allowing the person who puts the luggage to be different from the person who picks up the luggage, various applications and services can be provided and realized using the biometric authentication-enabled locker 10. For example, a user requests delivery of a lunch box or tea from a restaurant or the like, and an employee of the restaurant designates the person who placed the order as the person who will pick up the luggage. In this manner, delivery of the lunch box or tea can be carried out via the locker. Alternatively, a billing process (payment of the price) can be carried out in conjunction with the delivery. Alternatively, a restaurant, retail store, etc. can periodically store predetermined products in the locker and deliver the products to the locker user.

[0231] Alternatively, a delivery company or the like may be designated as the person to retrieve the package. In this case, when a visitor to a free address floor sends a package to his / her home, there is no need to contact a delivery company or the like. The delivery company retrieves the package from the biometric authentication-enabled locker 10 and delivers the package to the home (delivery destination) of the person who put the package. Also, email may be used to exchange information between a visitor to the floor and the delivery company. A visitor to the floor sends an email to a delivery company requesting collection. The delivery company may identify the sender from the sender address of the email and set the sender's home as the destination of the package. Alternatively, a visitor may directly specify the destination of the package by email. Alternatively, the delivery company may identify the user's location from the received email and determine the destination of the package. For example, if the email is sent from the user's personal account, the delivery company may set the destination of the package to "home," and if the email is sent from the company's account, the delivery company may set the destination of the package to "company."

[0232] In addition, a problem specific to the use of a free address flow is that in a free address flow, the desks of each individual are not fixed, and the parcel delivery person cannot grasp the detailed destination of the parcel (a detailed destination beyond the free address floor). The locker management system disclosed in the present application is effective for such a problem. That is, the locker management system disclosed in the present application is effective for temporarily storing parcels addressed to employees (individuals) who use a free address floor. Specifically, the parcel delivery person (the person who distributes parcels on the free address floor) stores the parcel that arrives on the floor in the biometric authentication-enabled locker 10. At that time, the biometric authentication-enabled locker 10 provides the delivery person with a GUI for specifying a parcel recipient. For example, the user request determination unit 303 of the biometric authentication-enabled locker 10 creates a GUI for acquiring a request for "temporary deposit". When temporary deposit is specified, the user request determination unit 303 generates a GUI for inputting information (e.g., name, etc.) of the parcel recipient (a GUI for the delivery person to input the name of the parcel recipient). When the biometric authentication-enabled locker 10 acquires information (e.g., name) about the parcel recipient, it transmits the information to the server device 20. The server device 20 refers to a user database to identify the user ID of the parcel recipient. After determining a locker in which to temporarily store the parcel, the server device 20 notifies the biometric authentication-enabled locker 10 of the locker ID of the determined locker. At that time, the server device 20 sets the user ID of the parcel recipient in the usage status field of the determined locker. In this manner, the floor user (parcel recipient) can take out the parcel from the biometric authentication-enabled locker 10. Note that, when the server device 20 identifies a locker in which to temporarily store the parcel, it is preferable that the server device 20 notifies the parcel recipient that the parcel has been temporarily stored. For example, the server device 20 notifies the parcel recipient of the above information by email or the like.

[0233] In the above embodiment, the biometric authentication locker 10 acquires a request for locker use from a user, and the server device 20 determines which locker to unlock based on the request. However, in the locker management system disclosed in the present application, it is also possible to specify a locker to unlock without using the request for locker use. In other words, with respect to a user's request (storing or removing luggage), the locker management system can also determine the user's request by face authentication. Specifically, the face image acquisition unit 304 of the biometric authentication locker 10 acquires a face image of the user in front of the user. The face image acquisition unit 304 transmits the face image to the server device 20. The collation unit 203 of the server device 20 identifies the user ID of the user based on the acquired face image. The locker management unit 205 refers to the locker management database, and if the identified user ID is not set in the usage status field of the database, it determines that the request is to store luggage. On the other hand, if the identified user ID is set in the usage status field of the database, the locker management unit 205 determines that the request is to remove luggage. By doing this, the server device 20 can specify the locker to be unlocked without receiving a request from the user. The biometric authentication locker 10 also manages the usage status of each locker, and if the user wishes to store more luggage, a GUI may be provided to the user to confirm whether or not they wish to store additional luggage.

[0234] In the flow charts (flow charts, sequence diagrams) used in the above description, multiple steps (processes) are described in order, but the order of execution of the steps executed in the embodiments is not limited to the order described. In the embodiments, the order of the steps shown in the figures can be changed to a degree that does not interfere with the content, such as executing each process in parallel.

[0235] The above-mentioned embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all of the configurations described above are necessary. In addition, when a plurality of embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace a part of the configuration of an embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of an embodiment. Furthermore, it is possible to add, delete, or replace a part of the configuration of an embodiment with another configuration.

[0236] The above explanation makes clear the industrial applicability of the present invention, and the present invention is suitably applicable to locker management systems used in free address floors of companies, etc.

[0237] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes. [Appendix 1] An acquisition unit that acquires biometric information of a user; A determination unit that determines a request for the user to use a locker; A locker control unit that unlocks a locker identified based on a request for use of the locker for a user identified by a matching process using the biometric information; A locker system comprising: [Appendix 2] a request unit that transmits a locker unlock request to a server device, the request including the biometric information and a request regarding use of the locker; The server device identifies the user by a matching process using the biometric information included in the locker unlock request, and identifies the locker to be unlocked based on the request regarding locker use included in the locker unlock request, and includes a locker ID of the identified locker in a response to the locker unlock request. The locker system according to claim 1, wherein the locker control unit unlocks the locker based on the response obtained from the server device. [Appendix 3] The locker system of claim 2, wherein the determination unit determines a request regarding locker use based on the user's behavior. [Appendix 4] The locker system described in Appendix 3, wherein the determination unit determines a request regarding use of the locker based on changes in the user's face. [Appendix 5] The locker system described in Appendix 3, wherein the determination unit determines a request regarding use of the locker based on the user's direction of movement. [Appendix 6] A generating unit that generates associated information regarding the user, The request unit transmits a locker unlock request including the generated associated information to the server device, The locker system according to any one of claims 2 to 5, wherein the locker control unit unlocks a locker selected by the server device using the associated information. [Appendix 7] The locker system described in Appendix 6, wherein the generation unit generates information regarding the user's height as the associated information. [Appendix 8] The locker system described in Appendix 6, wherein the generation unit generates information regarding the size of luggage carried by the user as the associated information. [Appendix 9] The determination unit does not determine a request regarding the user's use of a locker, The request unit transmits a locker unlock request including the biometric information to a server device, The locker system described in Appendix 2, wherein the server device identifies the user through a matching process using the biometric information included in the locker unlocking request, and identifies the locker to be unlocked based on whether the identified user is using the locker. [Appendix 10] A server device; a locker system connected to the server device; Including, The locker system comprises: An acquisition unit that acquires biometric information of a user; A determination unit that determines a request for the user to use a locker; a request unit that transmits a locker unlock request including the biometric information and a request regarding use of the locker to the server device; A locker control unit that unlocks the locker based on the response obtained from the server device; Equipped with The server device identifies the user through a matching process using the biometric information included in the locker unlock request, identifies the locker to be unlocked based on the request regarding locker use included in the locker unlock request, and includes the locker ID of the identified locker in a response to the locker unlock request. [Appendix 11] The server device includes: a user database that stores at least a user ID for identifying the user and biometric information in association with each other; A locker management database that stores at least the locker ID of each locker in the locker system and the usage status of each locker in association with each other; A matching unit that refers to the user database and identifies the user ID corresponding to the biometric information included in the locker unlock request; a locker management unit that, when the request for using a locker is to store luggage, selects a locker for storing luggage and sets the specified user ID in a usage status field of the locker management database corresponding to the selected locker; Equipped with The locker management system of claim 10, wherein the locker management unit notifies the locker system of the locker ID of the selected locker. [Appendix 12] The locker management system described in Appendix 11, wherein, when the request for locker use is to retrieve luggage, the locker management unit refers to the locker management database, identifies the locker ID for which the identified user ID is set in the usage status field, and notifies the locker system of the identified locker ID. [Appendix 13] Further comprising an exit management terminal for controlling a gate for restricting the exit of users; The exit management terminal transmits biometric information of the exiting person to the server device, The matching unit identifies a user ID of the leaving person by a matching process using biometric information of the leaving person, A locker management system as described in Appendix 11 or 12, wherein the locker management unit notifies the exit management terminal of luggage left behind when the user ID of the identified exiting person is set in the usage status field. [Appendix 14] The server device has an equipment management unit that manages the equipment stored in the locker system; an equipment management database that stores a user ID of a user who has reserved the equipment, the reserved equipment, and a usage period of the reserved equipment in association with each other; Further equipped with A locker management system as described in any one of Appendices 11 to 13, wherein the equipment management unit sets the user ID of the user who reserved the equipment in the usage status field of the locker storing the reserved equipment before the usage period of the reserved equipment arrives. [Appendix 15] the request unit transmits to the server device the locker unlock request, the locker unlock request including information about a person who is permitted to retrieve luggage stored in the locker; A locker management system as described in any one of Appendices 11 to 14, wherein the locker management unit identifies the user ID of the person picking up the luggage based on information about the person picking up the luggage, and sets the user ID of the person picking up the luggage in the usage status field corresponding to the locker that stores the luggage. [Appendix 16] In the locker system, Acquire the user's biometric information, determining a locker access request for said user; A locker management method, which unlocks a locker identified based on a request for use of the locker for a user identified by a matching process using the biometric information. [Appendix 17] The computer installed in the locker system A process of acquiring biometric information of a user; determining a request for locker use by the user; A process of unlocking a locker identified based on a request for use of the locker for a user identified by a matching process using the biometric information; A computer-readable storage medium that stores a program for executing the above.

[0238] The disclosures of the above cited prior art documents are incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. In other words, the present invention naturally includes various modifications and amendments that a person skilled in the art can make in accordance with the entire disclosure, including the scope of the claims, and the technical ideas. [Explanation of symbols]

[0239] 10 Biometric lockers 11 Display Panel 12 Camera 20 Server device 30-1 Entrance management terminal 30-2 Exit management terminal Gate 31 40 Camera Equipment 100 Locker System 101 Acquisition Department 102 Judgment section 103, 306 Locker control unit 201, 301, 401 Communication control unit 202 User Registration Department 203 Matching Unit 204 User Management Department 205 Locker Management Department 206, 307, 404 Storage section 207 Equipment Management Department 211 User information acquisition department 212 ID generation section 213 Feature Generation Unit 214 Entry Management Department 302 User detection unit 303 User request determination section 304, 402 Face image acquisition unit 305 Unlock request section 308 Accompanying information generation unit 311 Processor 312 Memory 313 Input / Output Interface 314 Communication Interface 403 Gate control section

Claims

1. An acquisition unit that acquires biometric information of a user; A determination unit that determines a request for the user to use a locker; a locker control unit that unlocks a locker identified for the user identified by the matching process using the biometric information based on a request for using the locker and information indicating a correspondence between each locker and the user's identification information; Equipped with The request for using the locker includes information indicating an action the user desires to take with respect to the locker, The determination unit determines the request for use of the locker based on a positional relationship between the locker and a component on a floor on which the locker is installed and a movement direction of the user. Locker system.

2. a request unit that transmits a locker unlock request to a server device, the request including the biometric information and a request regarding use of the locker; The server device identifies the user by a matching process using the biometric information included in the locker unlock request, and identifies a locker to be unlocked based on information indicating the correspondence between each locker and the user's identification information and a request regarding the locker use included in the locker unlock request, and includes a locker ID of the identified locker in a response to the locker unlock request. The locker system according to claim 1 , wherein the locker control unit unlocks the locker based on the response obtained from the server device.

3. The locker system according to claim 2 , wherein the determination unit determines the request for locker use based on an action by the user.

4. The locker system according to claim 3 , wherein the determination unit determines the request for use of the locker based on a change in the user's face.

5. A generating unit that generates associated information regarding the user, The request unit transmits the locker unlock request including the generated associated information to the server device, The locker system according to claim 2 , wherein the locker control unit unlocks a locker selected by the server device using the associated information.

6. The locker system according to claim 5 , wherein the generation unit generates information relating to a height of the user as the associated information.

7. The locker system according to claim 5 , wherein the generation unit generates information regarding a size of luggage carried by the user as the associated information.

8. The request unit transmits the locker unlock request including the biometric information to the server device, The locker system of claim 2, wherein the server device identifies the user by a matching process using the biometric information included in the locker unlocking request, and identifies the locker to be unlocked based on whether the identified user is using the locker, regardless of the judgment result by the judgment unit.

9. In the locker system, Acquire the user's biometric information, determining a locker access request for said user; unlocking a locker identified based on a request for use of the locker and information indicating a correspondence between each locker and the identification information of the user identified by the matching process using the biometric information; The request for using the locker includes information indicating an action the user desires to take with respect to the locker, In the determination, the request for use of the locker is determined based on a positional relationship between the locker and a structure on the floor on which the locker is installed and a moving direction of the user. Locker management methods.

Images