JP2018077680A - Locker management system and locker management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To correspond to electronic collection of information such as the number of vacant lockers without closing, modification or model change of an existing key type locker.SOLUTION: A locker management system includes a transmitter attached to a key, a receiver that receives transmission by the transmitter, and one or more information processing devices connected to the receiver via a network. In the system, the transmitter transmits key data by which the key can be identified, to the receiver, the receiver receives the key data, the receiver acquires reception intensity at which the key data is received, the information processing device receives reception data in which the key data is associated with the reception intensity, the information processing device stores locker data by which a locker associated with the key is identified, and the information processing device calculates the number of vacant lockers on the basis of the reception data and the locker data.SELECTED DRAWING: Figure 11

Description

  The present invention relates to a locker management system and a locker management method.

  Conventionally, coin lockers (hereinafter sometimes simply referred to as “lockers”) that can be used when coins are inserted are installed in stations, commercial facilities, amusement parks, and the like. And the method of managing a locker has the following methods, for example.

  For example, a coin locker may be operated by a plurality of managers. First, in the locker network system, a locker ID (Identification) for identifying a locker, a locker corner ID, and a key ID for identifying a key for locking the locker are associated and held. Next, these IDs are transmitted and received by non-contact communication using a wireless tag. In this way, locker information indicating the operating status of the locker corner is collected for each group. Thereby, a method of performing seamless cooperation between a plurality of managers is known (for example, Patent Document 1).

  There is also known a method in which a stocker management apparatus manages a stocker having a plurality of lockable deliveries. Specifically, first, a beacon device arranged corresponding to the stocker transmits a beacon signal. Next, when a beacon signal is received, the mobile terminal calculates position information. When the parent device receives the member ID from the mobile terminal, the parent device determines the member ID and unlocks the delivery box. Thus, a method for improving user convenience is known (for example, Patent Document 2).

  In addition, a method for managing a plurality of locker devices by a locker management server connected to the Internet network is known. Specifically, first, empty locker information is generated at a predetermined timing. Furthermore, monetary information is generated separately from the free locker information. In this way, a method for efficiently managing locker vacancy information in a wide area is known (for example, Patent Document 3).

JP 2006-285658 A JP, 2006-134138, A Japanese Patent No. 5917891

  However, in the conventional method, when a locker to be managed is repaired or replaced, it may be necessary to stop the operation of the locker using the key.

  One aspect of the present invention has been made in view of such a problem, and is adapted to computerization that collects information such as the number of vacancies without closing, repairing, or changing the model of an existing key locker. For the purpose.

In order to solve the above-described problems and achieve the object, in one embodiment of the present invention, a transmitter attached to a key, a receiver that receives transmission by the transmitter, the receiver and the network In a locker management system having one or more information processing devices connected,
The transmitter is
A transmission unit that transmits key data capable of identifying the key to the receiver;
The receiver is
A receiving unit for receiving the key data;
An acquisition unit for acquiring the reception strength of receiving the key data;
The information processing apparatus includes:
An input unit for inputting reception data in which the key data and the reception intensity are associated;
A storage unit for storing locker data for identifying a locker corresponding to the key;
A calculation unit that calculates the number of empty lockers based on the received data and the locker data.

  ADVANTAGE OF THE INVENTION According to this invention, it can be made to respond | correspond to the digitization which collects information, such as a vacancy number, without closing the locker used as management object, repairing or changing a model.

It is a figure which shows the example of the locker made into the management object by the locker management system in embodiment of this invention. It is an external view which shows the structural example of the key used in embodiment of this invention. It is a figure which shows the example of arrangement | positioning of the receiver etc. which the locker management system in embodiment of this invention has. It is a block diagram which shows an example of the hardware constitutions of the information processing apparatus which the locker management system in embodiment of this invention has. It is a sequence diagram which shows an example of the whole process by the locker management system in embodiment of this invention. It is a flowchart which shows an example of the process by the information processing apparatus which the locker management system in embodiment of this invention has. It is a table | surface which shows an example of the locker data which the locker management system in embodiment of this invention memorize | stores. It is a table | surface which shows an example of the reception data which the locker management system in embodiment of this invention inputs. It is a table | surface which shows an example of the result as which the locker management system in embodiment of this invention determined the vacant state of the locker. It is a table | surface which shows an example of the result of having calculated the vacant state of the locker for every size and every group by the locker management system in embodiment of this invention. It is a functional block diagram which shows an example of a function structure of the locker management system in embodiment of this invention.

Embodiments of the present invention will be described in the following order.

1. 1. Example of overall configuration of locker management system 2. Example of overall processing by locker management system Functional configuration example of locker management system

≪ １． Example of overall configuration of locker management system ≫
FIG. 1 is a diagram illustrating an example of lockers to be managed by the locker management system according to the embodiment of the present invention. For example, the locker management system in the embodiment of the present invention manages a plurality of lockers as shown. Specifically, as illustrated, it is assumed that there are nine lockers such as the first locker LCK1 to the ninth locker LCK9. The illustrated first locker LCK1 to ninth locker LCK9 are assumed to be one group GR.

  Each locker has three types of sizes. Specifically, as illustrated, the first rocker LCK1, the fourth rocker LCK4, and the seventh rocker LCK7 installed in the upper stage are assumed to be the “small” size that is the smallest among the three types. Further, as illustrated, the second rocker LCK2, the fifth rocker LCK5, and the eighth rocker LCK8 installed in the middle stage are larger than the “small” size and smaller than the “large” size. Suppose that it is a medium size. Further, as illustrated, the third locker LCK3, the sixth locker LCK6, and the ninth locker LCK9 installed in the lower stage are assumed to be the “large” size that is the largest among the three types.

  Each locker has a key that can lock and unlock the door of each locker. Specifically, the first key KEY1 corresponds to the first locker LCK1. That is, when the first key KEY1 is used, the user unlocks the door of the first locker LCK1, and stores the luggage in the first locker LCK1, or takes out the luggage from the first locker LCK1. Can do. Furthermore, when the first key KEY1 is used, the user can lock the luggage after storing the luggage in the first locker LCK1, and deposit the luggage in the first locker LCK1.

  On the other hand, even if a key other than the first key KEY1, such as a key for the second locker LCK2, is used for the first locker LCK1, the user can lock and unlock the door of the first locker LCK1. I can't. In this way, the door of each locker and the corresponding key are paired.

  The key is used in the following configuration, for example.

  FIG. 2 is an external view showing a configuration example of a key used in the embodiment of the present invention. For example, as shown in FIG. 2A, the key KEY is composed of a key body and a transmitter TR attached to the key body by a ring or the like.

  Then, the transmitter TR transmits data indicating a key ID that can identify the key KEY (hereinafter referred to as “key data”) to a receiver RE installed in advance.

  The key KEY may have the following configuration. For example, the key KEY may have a configuration in which an electronic circuit board to be a transmitter TR is embedded in a key body as illustrated in FIG. Even in such a configuration, the transmitter TR can transmit the key data to the receiver RE, as in FIG.

  As shown in the drawing, when the transmitter TR is attached to the key body by ring or embedding, the transmitter TR is easily attached to the key even during operation.

  That is, wireless communication such as RFID (Radio Frequency Identifier) is realized by the transmitter TR and the receiver RE. For example, the wireless communication method is a method that conforms to a standard such as Bluetooth (registered trademark).

  Specifically, an RF tag that transmits key data, that is, a transmitter TR is attached to the key KEY. The receiver RE receives the key data transmitted from the transmitter TR. In this way, the transmitter TR transmits data such as key data to the receiver RE by a so-called beacon.

  The transmitter TR preferably includes a battery or the like and actively performs transmission. That is, the transmitter TR is preferably a so-called active tag. As described above, when the transmitter TR is an active tag, the communicable distance can be increased as compared with the passive tag. Therefore, the number of receivers installed may be reduced. Further, when the transmitter TR is an active tag, the size can be reduced as compared with a passive tag.

  Further, it is desirable for the transmitter TR to transmit periodically. For example, the transmitter TR periodically transmits key data at intervals of about once every 10 seconds. Note that the transmission cycle may be set based on, for example, the battery life.

  Further, when receiving the transmission from the transmitter TR, the receiver RE can measure the reception strength (RSSI, Received Signal Strength Indicator) and acquire the reception strength.

  The key KEY and the receiver RE with the transmitter TR as described above are used, for example, arranged as follows.

  FIG. 3 is a diagram illustrating an arrangement example of receivers and the like included in the locker management system according to the embodiment of the present invention. For example, as shown in the figure, an example where two receivers are arranged will be described below.

  Specifically, the first receiver RE1 (in the illustrated example, the receiver disposed on the left side) and the second receiver RE2 (in the illustrated example, the receiver disposed on the right side). ) Are arranged as shown. Note that the number of receivers included in the locker management system may be one or three or more.

  The first receiver RE1 receives each key data from a transmitter within the first range RA1. Then, the first receiver RE1 transmits data to the server 10 which is an example of an information processing apparatus, via a network NW such as a LAN (Local Area Network).

  Similarly, the second receiver RE2 receives each key data from the transmitter within the second range RA2. Then, the second receiver RE2 also transmits data to the server 10 via the network NW.

  On the other hand, when the locker is locked and the user moves with a key, the distance between the transmitter and the receiver becomes longer, and the reception intensity decreases. When the key moves out of the first range RA1, the first receiver RE1 cannot receive data from the transmitter attached to the key carried by the user. Therefore, if the first receiver RE1 cannot receive data from within the first range RA1, the first receiver RE1 can determine that the locker is not locked and that the locker is in use.

  The server 10 is a device having the following hardware configuration, for example.

  FIG. 4 is a block diagram illustrating an example of a hardware configuration of the information processing apparatus included in the locker management system according to the embodiment of the present invention. Specifically, the server 10 includes a CPU (Central Processing Unit) 101, a storage device 102, a network I / F (interface) 103, an input I / F 104, and an output I / F 105. That is, the server 10 is a computer that executes a predetermined procedure based on a program installed in advance.

  The CPU 101 is an arithmetic device that performs calculations for realizing various processes and various controls and processes various data. Further, the CPU 101 is a control device that controls hardware included in the server 10.

  The storage device 102 stores data, programs, setting values, and the like. The storage device 102 is a so-called memory or the like. Note that the storage device 102 may include an auxiliary storage device such as a hard disk.

  The network I / F 103 transmits / receives various data and the like to / from devices connected via the network. For example, the network I / F 103 is a connector or the like for connecting a NIC (Network Interface Controller) and a LAN cable. Note that the network I / F 103 is not limited to an I / F that uses a network, and may be an I / F that transmits and receives to / from an external device through a cable, wireless, or a connector.

  The input I / F 104 is an input interface with a user or the like. Specifically, the input I / F 104 inputs various operations performed by a user or the like. For example, the input I / F 104 includes an input device such as a keyboard and a connector for connecting the input device.

  The output I / F 105 is an output interface with a user or the like. Specifically, the output I / F 105 outputs processing results and the like of various processes to the user and the like. For example, the output I / F 105 is an output device such as a display and a connector for connecting the output device. Note that the output I / F 105 may generate data indicating a processing result and output the data to an external device.

  The server 10 may further include an auxiliary device that assists processing by each hardware resource. Further, the server 10 may further include an apparatus inside or outside in order to process various processes and controls in parallel, redundantly, or distributedly.

  Furthermore, the locker management system may have a plurality of information processing apparatuses. For example, the information processing apparatus may be configured to include an information processing apparatus that receives data from a plurality of receivers separately from the server 10. That is, the locker management system may include a device (hereinafter referred to as “collection terminal”) that collects data from each transmitter and a server 10 that receives data from the collection terminal.

  The collection terminal is connected to a plurality of receivers. That is, the collection terminal is a device that serves as a gateway. Then, the collection terminal transmits data to the server 10 based on the result of totalizing the collected data at a predetermined interval. For example, the predetermined interval is an interval of 2 minutes. Thus, if there is a collection terminal, the number of lockers or receivers can be easily increased or decreased. More preferably, the collection terminal preferably has a type of port other than a LAN port. Thus, when there are a plurality of types of ports, the collection terminal can connect various types of cables.

  In many cases, the collection terminal receives the respective data from the respective receivers and then performs a process of collecting the respective data. Therefore, it is desirable that the predetermined interval be set in consideration of the time for collecting the respective data. Hereinafter, an example in which the information processing apparatus includes only the server 10 will be described.

≪ 2. Example of overall processing by locker management system ≫
FIG. 5 is a sequence diagram illustrating an example of overall processing by the locker management system according to the embodiment of the present invention. For example, the locker management system 1 performs the illustrated process at predetermined intervals. In the following example, it is assumed that there are five transmitters, that is, five keys, and two receivers as shown in FIG. In the following description, similar processing is denoted by the same reference numeral, and description thereof is omitted.

<< Example of Key Data Transmission (Step S101) >>
In step S101, each transmitter transmits key data to the receiver. In the example illustrated, the first transmitter TR1 and the second transmitter TR2 transmit the respective key data to the first receiver RE1. Similarly, the third transmitter TR3, the fourth transmitter TR4, and the fifth transmitter TR5 transmit the respective key data to the second receiver RE2.

  Note that it is desirable that step S101 is periodically performed and that each key data is transmitted at a preset period.

≪ Key data reception and reception strength acquisition example (step S102) ≫
In step S102, each receiver receives key data transmitted by each transmitter. In step S102, each receiver measures the reception intensity of each radio wave transmitted with the key data and acquires the reception intensity when receiving each key data. In addition, each receiver may record the received date and time.

<< Locker data storage example (step S103) >>
In step S103, the server 10 stores data (hereinafter referred to as “locker data”) that can identify the locker corresponding to the key. Details of the storage procedure and locker data will be described later.

≪ Example of input of received data (step S104) ≫
In step S104, the server 10 inputs data in which the key data is associated with the reception intensity (hereinafter referred to as “reception data”). That is, in step S104, the server 10 inputs each result received and acquired in step S102 from each receiver. For example, the received data is generated by CGI (Common Gateway Interface) or the like. The input of received data is realized by a request and response in HTTP (Hypertext Transfer Protocol). Details of the input procedure and received data will be described later.

≪ Example of calculating the number of empty lockers (step S105) ≫
In step S105, the server 10 calculates the number of empty lockers. For example, the server 10 determines the availability of each locker based on the received data and locker data. Next, based on the determination result, the server 10 calculates the number of empty lockers by counting the number of lockers determined to be empty. If it does in this way, the locker management system 1 can grasp | ascertain the number of empty lockers. Details of the calculation procedure will be described later.

≪ Output example based on the number of empty lockers (step S106) ≫
In step S106, the server 10 may cause the external device to output the calculated number of empty lockers, for example. For example, as illustrated, it is assumed that an output terminal OT is connected to the locker management system 1. The output terminal OT is, for example, a display terminal such as a display or a mobile terminal such as a smartphone.

  For example, the server 10 causes the output terminal OT to display the number of empty lockers as a number or an icon based on the determination result. Moreover, the output terminal OT may display the installation location of the locker determined to be an empty locker, for example, using a map or the like. In addition, the output terminal OT may display the number of empty lockers for each size.

  The processes performed by the server 10, that is, steps S103 to S105 are the following processes.

  FIG. 6 is a flowchart illustrating an example of processing performed by the information processing apparatus included in the locker management system according to the embodiment of the present invention. In the following description, the same processing as in FIG.

<< Locker data storage example (step S103) >>
In step S103, the server 10 (see FIG. 4) stores locker data. The locker data is, for example, data in which each item is input in advance by the user. The locker data is, for example, the following data.

  FIG. 7 is a table showing an example of locker data stored in the locker management system according to the embodiment of the present invention. In the illustrated example, the locker data DLCK is data that associates “Group No.”, “Locker Frontage No.”, “Size”, and “Key ID”.

  “Group No.” is an example of locker group data that can identify a group to which each locker belongs. In the illustrated example, the locker data DLCK indicates that the lockers whose “locker frontage No.” is “8001” to “8004” belong to the group “group No.” “L2001”. Further, when “Group No.” is known, the server 10 can identify the location where the locker is installed.

  “Locker frontage No.” is an example of locker identification data indicating a number or the like that can specify each locker. For example, “Locker frontage No.” is the serial number or management number of each locker.

  “Size” is an example of locker size data indicating the size of each locker. In the illustrated example, the locker data DLCK indicates that the locker whose “locker frontage No.” is “8001” is “small”. For example, a “small mouth” locker is a storage space for a small bag or the like. On the other hand, in the illustrated example, the locker data DLCK indicates that the locker whose “locker frontage No.” is “8003” is “large”. For example, a “large mouth” locker is a storage space in which large bags such as carry bags or suitcases can be placed.

  The “size” is not limited to the three types of “small mouth”, “medium mouth”, and “large mouth”. That is, the number of types may be two or less or four or more. The “size” may be input as a numerical value or the like.

  The “key ID” is data that can specify a key corresponding to each locker. In the example shown in the figure, the locker data DLCK indicates that a key whose “key ID” is “A0001” corresponds to a locker whose “locker frontage No.” is “8001”.

  Specifically, when the server 10 stores the locker data DLCK shown in the figure, the server 10 can determine the lockers belonging to the group GR shown in FIG. 1 from “Group No.” and “Locker frontage No.”. Further, when the location where the group GR is installed can be specified, the server 10 can specify the location of each locker based on the “group No.” and the “locker frontage No.”.

  Further, when the server 10 stores the locker data DLCK shown in the figure, the server 10 can specify the key corresponding to each locker based on the “locker frontage No.” and the “key ID”. For example, it is assumed that the key whose “key ID” is “A0001” is the first key KEY1 shown in FIG. That is, the locker data DLCK is input with the first key KEY1 corresponding to the first locker LCK1.

  In the illustrated locker data DLCK, “small”, “medium” and “large” correspond to the sizes of “small”, “medium” and “large” shown in FIG.

≪ Example of input of received data (step S104) ≫
Returning to FIG. 6, in step S104, the server 10 inputs received data. The received data is, for example, the following data.

  FIG. 8 is a table showing an example of received data input by the locker management system according to the embodiment of the present invention. In the illustrated example, the received data is data that associates “key ID” with “reception strength”. As shown in the figure, the reception data may be data in which “last reception time” or the like is recorded.

  “Key ID” is a key ID indicated by the received key data.

  The “last reception time” indicates the date and time when the key data is received.

  “Reception strength” indicates the reception strength at which each key data is received. In the following description, it is assumed that the distance between the receiver and the transmitter can be calculated based on the reception intensity.

  The received data may be processed, that is, updated so that past data is deleted and the latest reception result remains when key data having the same key ID is received.

≪ Example of calculating the number of empty lockers (step S105) ≫
Returning to FIG. 6, in step S105, the server 10 calculates the number of empty lockers. First, when there is locker data DLCK as shown in FIG. 7, the server 10 can calculate the distance at which each key corresponding to each locker is present based on the reception intensity. Then, when the received intensity is compared with a preset threshold value, the server 10 can determine the availability of each locker.

  Hereinafter, the first locker LCK1 shown in FIG. 1 will be described as an example. First, the server 10 can specify that the corresponding key is the key “A0001” based on the locker data DLCK. Therefore, the server 10 determines the free state of the first locker LCK1 based on the reception strength at which the key data “A0001” is received.

  Note that the threshold value may be set for each locker. The reception intensity is affected by, for example, whether the place where the locker is installed is a closed space such as a locker room or an open space such as a station. In addition, the reception strength is often affected by the distance between the locker and the receiver, whether or not there is a shield between the locker and the receiver, and the like.

  Therefore, the threshold value is preferably a value measured in a state where each key is attached to the locker for each place where the locker is installed, each locker or each group. The group is, for example, “Group No.” shown in FIG. In this manner, the threshold value may be set in consideration of each usage environment in consideration of the usage environment of each locker. Note that a value including a safety factor or the like may be set as the threshold in consideration of the influence of an error or the like.

  That is, when the locker is locked, as in the first locker LCK1 shown in FIG. 1, the received intensity is close to the intensity measured in advance when the key is locked. That is, when the locker is “vacant”, the reception intensity is close to a predetermined intensity.

  On the other hand, the reception strength is weaker when the key is released from the locker, as in the case of the second locker LCK2 shown in FIG. If the key is separated beyond a predetermined range, the receiver cannot receive the key data. That is, when the locker is “in use”, the reception intensity is weaker than a predetermined intensity, or the receiver cannot receive the key data.

  Therefore, for example, when each threshold is compared with each received intensity indicated by the received data and the received intensity is a value exceeding the threshold, the server 10 indicates that the locker is in an “empty” state. judge. On the other hand, the server 10 compares the respective threshold values with the respective reception strengths indicated by the reception data, and if the reception strength does not exceed the threshold value or the target key data is not included in the reception data, the server 10 Is determined to be “in use”. As described above, the server 10 makes a determination by comparing the reception strength associated with each key with the threshold value based on the received data. And the server 10 determines the empty state of the locker corresponding to each key based on locker data. For example, the determination result is as follows.

  FIG. 9 is a table showing an example of a result of the locker management system according to the embodiment of the present invention determining the availability of lockers. In the example shown in the illustrated empty state data DST, “Group No.” and “Locker frontage No.” are the same items as the locker data DLCK shown in FIG. Further, the “empty state” is a free state of each locker determined in step S105 shown in FIG.

  In the example of the vacant state data DST shown in the figure, with respect to the keys corresponding to the lockers with “8001”, “8003”, “9001”, and “9002” as “Locker frontage No.”, the respective reception strengths exceed the threshold values. Yes, when it is determined to be in the “free” state. That is, the lockers with “8001”, “8003”, “9001”, and “9002” in the “locker frontage No.” are in a state in which the user can store luggage or the like in each locker.

  On the other hand, in the example of the vacant state data DST shown in the figure, for the keys corresponding to the lockers with “8002”, “8004”, and “9003” for the “locker frontage No.”, the respective reception strengths are not values that exceed the threshold. , When it is determined to be in use. In other words, the lockers with “8002”, “8004”, and “9003” in the “Locker frontage No.” are in a state in which luggage or the like is already stored in the respective lockers.

  Then, the server 10 can calculate the number of empty lockers by counting the number of lockers in which the empty state becomes “empty”.

  The number of empty lockers is preferably calculated for each size or group. For example, the number of empty lockers is preferably calculated as follows.

  FIG. 10 is a table showing an example of a result of the locker management system according to the embodiment of the present invention calculating locker availability for each size and group. In the example indicated by the calculation result data DCL shown in the drawing, “Group No.” and “Size” are the same items as the locker data DLCK shown in FIG. The “number of free lockers” indicates the number of free lockers for each size in each group.

  Since the locker data DLCK shown in FIG. 7 is stored in advance, the server 10 can specify the size and group of the locker corresponding to each key. Therefore, for example, the server 10 can specify the size of the locker in the “empty” state by using the free state data DST shown in FIG. 9.

  Specifically, in the example of the empty state data DST, for example, in the group “L2001”, a locker that is “available” in the “small” size is a locker whose “locker frontage No.” is “8001”. Only. Therefore, the number of empty lockers is “1”. Therefore, in the calculation result data DCL, “the number of empty lockers” of “small” in “L2001” is “1”.

  Similarly, in the group of “L2001”, the locker in the “vacant” state with the size of “center entrance” is “in use” because the locker with “8002” in the “locker frontage No.” is “in use”. There are no lockers in the state. Therefore, the number of empty lockers is “0”. Therefore, in the calculation result data DCL, the “number of empty lockers” of “middle entrance” in “L2001” is “0”.

  If it calculates as mentioned above, the server 10 can calculate the number of empty lockers for every group and every size.

≪ Output example based on the number of empty lockers (step S106) ≫
Returning to FIG. 6, in step S <b> 106, the server 10 may cause the external device such as the output terminal OT (see FIG. 5) to output the calculated number of empty lockers and the like. For example, in step S106, the server 10 transmits data indicating the number of empty lockers calculated in step S105 to the output terminal OT. Then, the output terminal OT displays the number of empty lockers and the like based on the received data. In this way, the server 10 may display the calculation result or the like on the external device.

≪ 3. Functional configuration example of locker management system ≫
FIG. 11 is a functional block diagram illustrating an example of a functional configuration of the locker management system according to the embodiment of the present invention. For example, the locker management system 1 has a functional configuration including a transmission unit FN1, a reception unit FN2, an acquisition unit FN3, an input unit FN4, a storage unit FN5, and a calculation unit FN6.

  The transmission unit FN1 transmits key data DKEY to the receiver RE. For example, the transmission unit FN1 is realized by an antenna included in the transmitter TR, an IC (Integrated Circuit) chip, and the like.

  The receiving unit FN2 receives the key data DKEY. For example, the reception unit FN2 is realized by an antenna, an IC chip, and the like included in the receiver RE.

  The acquisition unit FN3 acquires the reception strength received from the key data DKEY. For example, the acquisition unit FN3 is realized by an antenna and an IC chip included in the receiver RE.

  The input unit FN4 inputs the reception data DRE. For example, the input unit FN4 is realized by the network I / F 103 (see FIG. 4), the CPU 101 (see FIG. 4), and the like.

  The storage unit FN5 stores locker data DLCK. For example, the storage unit FN5 is realized by the storage device 102 (see FIG. 4) or the like.

  The calculation unit FN6 calculates the number of empty lockers based on the reception data DRE and the locker data DLCK. For example, the calculation unit FN6 is realized by the CPU 101 (see FIG. 4) or the like.

  First, for example, as shown in FIG. 2, a transmitter TR is attached to the key KEY. A key ID or the like that can identify the key is set in the transmitter TR. Therefore, the transmitter TR can transmit the key data DKEY indicating the key ID and the like by the transmission unit FN1.

  Next, for example, like the first receiver RE1 and the second receiver RE2 shown in FIG. 3, the receiver RE is installed in advance at a place where a locker is installed. In this way, the receiver RE can receive the key data DKEY transmitted by the transmitter TR by the receiving unit FN2.

  The receiver RE can acquire the reception intensity by the acquisition unit FN3 when measuring the reception intensity when receiving the key data DKEY. Therefore, when the key data DKEY received by the reception unit FN2 and the reception intensity acquired by the acquisition unit FN3 when the key data DKEY is received, the receiver RE receives, for example, reception data as illustrated in FIG. A DRE can be generated.

  The receiver RE and the server 10 are connected via a network NW, for example, as shown in FIG. Therefore, when the reception data DRE is sent from the receiver RE to the server 10 via the network NW, the server 10 can input the reception data DRE through the input unit FN4.

  Further, the server 10 stores, for example, rocker data DLCK as illustrated in FIG. 7 by the storage unit FN5. In addition, a key ID is input to the locker data DLCK shown in FIG. 7 corresponding to locker identification data such as “Locker frontage No.” that can identify each locker.

  Further, the locker data DLCK is input with locker group data such as “Group No.” indicating the group to which each locker belongs. Thus, if there is locker group data, the server 10 can specify the group to which each locker belongs.

  In addition, rocker size data such as “size” indicating the size of each locker is input to the locker data DLCK. Thus, if there is locker size data, the server 10 can specify the size of each locker.

  In the server 10, a threshold value used for comparison is set in advance. Then, the server 10 compares the threshold value with the reception intensity indicated by the reception data DRE. Next, based on the result of the comparison, the availability of each locker is determined.

  The server 10 can associate the key ID and the locker with the locker data DLCK. The key ID and the reception strength can be associated with each other by the reception data DRE. Therefore, the determination result based on the reception intensity can be associated with each locker, and the determination result by the server 10 is, for example, empty state data DST shown in FIG.

  Subsequently, based on the empty state data DST, the server 10 can calculate the number of empty lockers by counting the number of lockers in the “empty” state by the calculation unit FN6.

  The number of empty lockers is preferably calculated for each size as shown in FIG. For example, when a user intends to store a large baggage such as a carry-back in a locker, the user searches for a locker that is “large” and that is in an “empty” state. Therefore, as shown in FIG. 10, when the number of “large” size empty lockers is known, the locker management system 1 can display the number of empty lockers of the size that the user is looking for.

  Moreover, as shown in FIG. 10, the number of empty lockers is preferably calculated for each group. When the group can be specified, the locker management system 1 can specify the installation location of the empty locker. Therefore, when the number of empty lockers can be calculated for each group, the locker management system 1 can display the installation location of the lockers in an “empty” state to the user.

  Furthermore, as shown in FIG. 2, when the transmitter is attached to the key later, the locker can be easily managed even if the locker is repaired or replaced. Specifically, the locker management system according to the present invention is configured to be easily managed even if a locker using a key as shown in FIG. 2 and a locker using an electronic lock or the like are mixed. For example, even when a locker using a key is replaced, the locker management system according to the present invention can reduce the stoppage of the operation of the locker using the key even at the time of replacement.

  That is, in the locker management system according to the present invention, there is little need to change the locker. That is, in the locker management system according to the present invention, if a transmitter is attached to a key and a receiver is installed, the administrator of the locker attaches a new device to the locker or installs a locker for management. You can save time and effort to replace with other models.

  On the other hand, in order to determine the “empty state” of the locker without using the reception intensity as in the locker management system according to the present invention, for example, a sensor such as a touch sensor is installed in the locker, and the sensor opens and closes the door. If no is detected, the “empty state” may not be determined. Alternatively, in the electronic lock method or the like, the “empty state” may not be determined unless a process for determining in response to input of a password or the like for opening the door is executed. Therefore, compared with these comparative examples, the locker management system according to the present invention reduces the need to install an information processing device or the like in the locker.

(Other embodiments)
Note that all or part of each processing according to an embodiment of the present invention is realized by a program for causing a computer described in a low-level language, a high-level language, or a combination thereof to execute a locker management method. Also good. That is, the program is a computer program for causing a computer such as an information processing apparatus to execute all or part of each process.

  The program can be stored and distributed in a computer-readable recording medium. The recording medium may be a flash memory, a flexible disk, an optical disk such as a CD-ROM or a Blu-ray disk, an SD (registered trademark) card, an auxiliary storage device, or an MO. Furthermore, the program can be distributed through a telecommunication line.

  Each process according to an embodiment of the present invention is not limited to the illustrated procedure. For example, some or all of the processes may be processed in different orders, in parallel, distributed, or omitted.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the above-described embodiments, and various modifications or changes can be made within the scope of the gist of the present invention described in the claims. Is possible.

1 locker management system KEY key TR transmitter TR1 first transmitter TR2 second transmitter TR3 third transmitter TR4 fourth transmitter TR5 fifth transmitter RE receiver RE1 first receiver RE2 second receiver 10 server FN1 Transmission unit FN2 Reception unit FN3 Acquisition unit FN4 Input unit FN5 Storage unit FN6 Calculation unit DKEY Key data DLCK Locker data DRE Reception data

Claims (6)

A locker management system comprising: a transmitter attached to a key; a receiver that receives transmission by the transmitter; and one or more information processing devices connected to the receiver via a network,
The transmitter is
A transmission unit that transmits key data capable of identifying the key to the receiver;
The receiver is
A receiving unit for receiving the key data;
An acquisition unit for acquiring the reception strength of receiving the key data;
The information processing apparatus includes:
An input unit for inputting reception data in which the key data and the reception intensity are associated;
A storage unit for storing locker data for identifying a locker corresponding to the key;
A locker management system including a calculation unit that calculates the number of empty lockers based on the received data and the locker data. The locker data is
And at least locker size data indicating the size of the locker,
The calculation unit includes:
The locker management system according to claim 1, wherein the number of empty lockers for each size is calculated based on the locker size data. The locker data is
Having locker group data indicating a group to which the locker belongs;
The calculation unit includes:
The locker management system according to claim 1 or 2 which calculates the number of each said empty locker for every said group based on said locker group data. The calculation unit includes:
The locker management system according to any one of claims 1 to 3, wherein the reception strength and a threshold value are compared to determine a free state of a locker identified based on the key data.   The locker management system according to any one of claims 1 to 4, wherein the transmitter is an active tag. A locker management method performed by a locker management system having a transmitter attached to a key, a receiver that receives transmission by the transmitter, and one or more information processing devices connected to the receiver via a network There,
A transmission procedure in which the transmitter transmits key data capable of identifying the key to the receiver;
A reception procedure in which the receiver receives the key data;
An acquisition procedure in which the receiver acquires the reception strength at which the key data is received;
An input procedure for inputting received data in which the information processing apparatus associates the key data with the received intensity;
A storage procedure in which the information processing apparatus stores locker data for identifying a locker corresponding to the key;
A locker management method including: a calculation procedure in which the information processing apparatus calculates the number of empty lockers based on the received data and the locker data.

Images