JP7170462B2 - Proposed device, proposed method and proposed program - Google Patents

Description

The present invention relates to a proposal device, a proposal method, and a proposal program.

Conventionally, for the delivery of products by a home delivery company, a technology has been disclosed that selects a storage locker for delivery of products based on the judgment result of the quantity and size of ordered products and the storage conditions for each product ( For example, Patent Document 1). Further, there is disclosed a technique of reserving a locker that is in use at the time of locker reservation by dividing the locker's available use time into a plurality of use time slots (for example, Patent Document 2). Also, a technique of reserving a plurality of available lockers for storing a group of products for which an order has been received is disclosed (for example, Patent Document 3).

JP 2010-176605 A JP 2017-215822 A JP 2017-165556 A

However, the above conventional technology is merely a technology for selecting or reserving a storage locker for delivery of ordered products based on the judgment result of the quantity and size of the product and the storage conditions for each product. However, it is not always possible to further improve usability for users who use lockers to store their belongings.

The present application has been made in view of the above, and proposes a proposed device, a proposed method, and a proposed program that can further improve usability for users who use lockers to store their personal belongings. intended to provide

The proposed device according to the present application includes an acquisition unit that acquires measurement information of a storage object to be stored in a locker, and a locker that can store the storage object based on the measurement information acquired by the acquisition unit. It is characterized by comprising a specifying unit and a proposing unit for proposing the locker specified by the specifying unit to the user.

According to one aspect of the embodiment, there is an effect that usability can be further improved for the user who uses the locker.

FIG. 1 is a diagram illustrating an example of proposal processing according to the embodiment. FIG. 2 is a diagram illustrating a configuration example of the proposal system according to the embodiment. FIG. 3 is a diagram illustrating a configuration example of a terminal device according to the embodiment; FIG. 4 is a diagram illustrating a configuration example of a locker management device according to the embodiment; FIG. 5 is a diagram illustrating a configuration example of a locker proposal server according to the embodiment; 6 is a diagram illustrating an example of a locker information storage unit according to the embodiment; FIG. FIG. 7 is a flowchart illustrating an example of proposal processing according to the embodiment. FIG. 8 is a hardware configuration diagram showing an example of a computer that implements the functions of the locker proposal server.

Embodiments for implementing the proposed apparatus, proposed method, and proposed program (hereinafter referred to as "embodiments") according to the present application will be described in detail below with reference to the drawings. Note that the proposed device, the proposed method, and the proposed program according to the present application are not limited to this embodiment. Also, in each of the following embodiments, the same parts are denoted by the same reference numerals, and overlapping descriptions are omitted.

(embodiment)
[1. Example of proposal processing]
First, an example of proposal processing according to the embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an example of proposal processing according to the embodiment. FIG. 1 shows an example in which the proposal process according to the embodiment is executed by the locker proposal server 100 . It should be noted that although luggage such as suitcases and bags are shown as an example of objects to be stored in the following embodiments, any object that can be stored in a locker may be used. In addition, the "locker" shown by the following embodiment shall include a coin-operated locker. Further, in the following embodiment, the proposal by the locker proposal server 100 refers to processing in which the locker proposal server 100 selects candidate lockers based on the acquired information and determines the optimum locker location. Further, the proposal by the locker proposal server 100 may be a process in which the locker proposal server 100 displays reservation information on a screen or recommends or presents a specified locker.

FIG. 1 shows an example in which the locker proposal server 100 acquires luggage measurement information based on an image of the luggage. Accordingly, the locker proposal server 100 can mechanically acquire the measurement information without the user inputting the size and amount of the baggage measured in advance. FIG. 1 shows an example in which the locker proposal server 100 proposes to the user a locker that can store the size of the package using the acquired measurement information. As a result, the locker proposal server 100 can allow the user to use the locker without having to search for a locker that can store the size of the luggage. In this way, the locker proposal server 100 can improve usability for users who want to use a locker to store their personal luggage. Also, for example, the locker proposal server 100 proposes a locker based on the information about the package transmitted from the terminal device 10 used by the user.

[Configuration of proposed system]
Prior to the description of FIG. 1, the configuration of the proposed system 1 will be described using FIG. FIG. 2 is a diagram illustrating a configuration example of the proposal system according to the embodiment. As shown in FIG. 2 , the proposed system 1 includes a terminal device 10 , a locker proposal server 100 and a locker management device 200 . The terminal device 10, the locker proposal server 100, and the locker management device 200 are connected via a predetermined network N so as to be communicable by wire or wirelessly. The proposed system 1 shown in FIG. 2 may include a plurality of terminal devices 10, a plurality of locker proposal servers 100, and a plurality of locker management devices 200. FIG.

The terminal device 10 is an information processing device used by a user. The terminal device 10 is realized by a smart phone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. The terminal device 10 transmits to the locker proposal server 100 information about the object to be kept in the locker. The terminal device 10 also transmits information about the user to the locker proposal server 100 .

The locker proposal server 100 is an information processing device that proposes a locker that can be stored based on the measurement information of the object to be stored. To give a specific example, the locker suggestion server 100 is a signage installed in a self-supporting manner. For example, the locker proposal server 100 is provided with a touch panel screen, which displays information about lockers and accepts user operations. Further, the locker proposal server 100 is equipped with a sensor on the side or inside the screen, and captures an image of an object placed in front. For example, the locker proposal server 100 captures an image of the object using a camera provided on the side of the screen or inside. Further, for example, the locker proposal server 100 is provided with a plurality of sensors on the side or inside the screen, and stereoscopically images the target.

The locker management device 200 is an information processing device that unlocks lockers based on the reservation information transmitted from the locker proposal server 100 . Specifically, the locker management device 200 is a computer built inside the locker. Further, the locker management device 200 may be a device that manages a single locker, or a device that manages a locker group consisting of a plurality of adjacent lockers.

Although FIG. 2 shows a case where the locker proposal server 100 and the locker management device 200 are separate devices, the locker proposal server 100 and the locker management device 200 may be integrated. Also, the locker proposal server 100 and the locker management device 200 may be managed by the same manager.

Returning to the description of FIG. In the example of FIG. 1, locker proposal server 100 shows a case where user U1 proposes a locker for storing baggage such as suitcases and bags. An example of the proposal process will be described below with reference to FIG. The locker proposal server 100 displays in the area FR1 a request to place the luggage to be stored in the locker. A region FR1 shown in FIG. 1 is a region within the imaging range of the sensor and is a region where luggage is placed. In the example shown in FIG. 1, the locker proposal server 100 displays the text data "Please put your luggage in the frame." Then, the locker proposal server 100 takes an image of the luggage placed in the area FR1 (step S101). Further, the locker proposal server 100 acquires the measurement information of the package based on the captured image (step S102). For example, the locker proposal server 100 acquires the three-dimensional package size (for example, length, width, and height) based on the area FR1. For example, the locker proposal server 100 acquires three-dimensional baggage measurement information by analyzing a plurality of images captured by a plurality of sensors provided in the locker proposal server 100 . Further, for example, the locker proposal server 100 acquires measurement information by analyzing a plurality of images captured by the sensor provided in the locker proposal server 100 and the terminal device 10 . Thus, the acquisition of measurement information shall be based on image analysis, radar measurements, or other spatial measurement solutions.

As in the example shown in FIG. 1 , when there are multiple pieces of baggage that user U1 keeps, locker proposal server 100 may measure the plurality of pieces of baggage. Here, the locker proposal server 100 may measure a plurality of packages placed in the area FR1 at once, or if the area FR1 cannot accommodate a plurality of packages, the locker proposal server 100 may measure the packages a plurality of times. It can be measured separately. As in the example shown in FIG. 1 , the locker proposal server 100 acquires measurement information measured by the locker proposal server 100 . Note that the locker proposal server 100 may acquire measurement information measured by the terminal device 10 . For example, the locker proposal server 100 acquires measurement information based on an image captured by the terminal device 10 . The locker proposal server 100 then proposes the locker specified based on the measurement information (step S103).

When proposing a locker, the locker proposal server 100 may display map information MP1 including information on the position of the proposed locker. The map information MP1 shown in FIG. 1 is map information displayed on the signage screen and is information indicating the location of the locker. Further, the locker proposal server 100 may display that the specified locker is proposed. In the example shown in FIG. 1, the locker suggestion server 100 displays text data saying "This coin locker is recommended." Then, the locker proposal server 100 accepts a locker reservation based on the user's operation (step S104). For example, the locker proposal server 100 may accept a locker reservation based on an operation on information displayed on a signage screen. Then, when accepting the locker reservation, the locker proposal server 100 transmits reservation information to the locker management device 200 that manages the reserved locker (step S105). Further, the locker proposal server 100 may display information indicating that the locker has been reserved, information for unlocking the locker, and information regarding the locker reservation time limit. In the example shown in FIG. 1, the locker proposal server 100 provides QR (Quick Response) information QR1, "I have reserved a coin locker." Please.” is displayed.

[2. Configuration of terminal device]
Next, the configuration of the terminal device 10 according to the embodiment will be described using FIG. FIG. 3 is a diagram showing a configuration example of the terminal device 10 according to the embodiment. As shown in FIG. 3 , the terminal device 10 has a communication section 11 , an input section 12 , an output section 13 and a control section 14 .

(Communication unit 11)
The communication unit 11 is realized by, for example, a NIC (Network Interface Card) or the like. The communication unit 11 is connected to a predetermined network N by wire or wirelessly, and transmits and receives information to and from the locker proposal server 100 via the predetermined network N.

(Input unit 12)
The input unit 12 receives various operations from the user. For example, the input unit 12 may receive various operations from the user through the display surface using a touch panel function. The input unit 12 may also receive various operations from buttons provided on the terminal device 10 or from a keyboard or mouse connected to the terminal device 10 .

(Output unit 13)
The output unit 13 is a display screen of a tablet terminal realized by, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display, and is a display device for displaying various information. In addition, the output unit 13 outputs an image of the storage target. The output unit 13 also outputs measurement information based on the captured image.

(control unit 14)
The control unit 14 is, for example, a controller, and a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like stores various programs stored in a storage device inside the terminal device 10 into a RAM (Random Access Memory). ) as a work area. For example, the various programs include application programs installed in the terminal device 10 . For example, these various programs include an application program for acquiring measurement information of an object to be stored based on a captured image. Also, the control unit 14 is implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

As shown in FIG. 3, the control unit 14 includes an imaging unit 141, an acquisition unit 142, a transmission unit 143, a reception unit 144, a display unit 145, a second transmission unit 146, and a second reception unit 147. and implements or performs the information processing operations described below.

(Imaging unit 141)
The imaging unit 141 captures an image to be stored based on a user's operation.

(Acquisition unit 142)
The acquisition unit 142 acquires the image captured by the imaging unit 141 . Also, the acquisition unit 142 acquires the measurement information of the object to be stored based on the image captured by the imaging unit 141 . In addition, the acquisition unit 142 may acquire the measurement information of the storage target stored in the storage unit.

(Sending unit 143)
The transmission unit 143 transmits the image acquired by the acquisition unit 142 to the locker proposal server 100 . Also, the transmission unit 143 may transmit the measurement information acquired by the acquisition unit 142 to the locker proposal server 100 . Also, the transmission unit 143 transmits the location information indicated by the user to the locker proposal server 100 . For example, the transmission unit 143 may transmit location information about the user's current location and location information about the user's destination to the locker proposal server 100 .

(Receiver 144)
The receiving unit 144 receives information about lockers identified by the locker proposal server 100 . For example, the receiving unit 144 receives information about the location of the locker identified by the locker proposal server 100 . For example, the receiving unit 144 receives map information indicating the location of the specified locker.

(Display unit 145)
The display unit 145 displays the locker-related information received by the reception unit 144 . For example, the display unit 145 displays map information including information indicating the location of the locker identified by the locker proposal server 100 . In addition, the display unit 145 may display information indicating that a reservation for using the specified locker is accepted.

(Second transmission unit 146)
The second transmission unit 146 transmits to the locker proposal server 100 information regarding the operation on the information displayed by the display unit 145 . For example, the second transmission unit 146 transmits to the locker proposal server 100 information indicating that the use of the specified locker is reserved.

(Second receiver 147)
The second reception unit 147 receives information for unlocking the locker from the locker proposal server 100 . The second receiving unit 147 receives information for unlocking the locker based on the information indicating that the use of the locker is reserved, which is transmitted by the second transmitting unit 146 .

[3. Configuration of Locker Management Device]
Next, the configuration of the locker management device 200 according to the embodiment will be described using FIG. FIG. 4 is a diagram showing a configuration example of the locker management device 200 according to the embodiment. As shown in FIG. 4 , the locker management device 200 has a communication section 210 , a reservation information storage section 220 and a control section 230 . The locker management device 200 has an input unit (for example, keyboard, mouse, etc.) for receiving various operations from the administrator of the locker management device 200, and a display unit (for example, liquid crystal display, etc.) for displaying various information. You may

(Communication unit 210)
The communication unit 210 is implemented by, for example, a NIC. The communication unit 210 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the locker proposal server 100 via the network N.

(Reservation information storage unit 220)
The reservation information storage unit 220 is implemented by, for example, a semiconductor memory device such as a RAM or flash memory, or a storage device such as a hard disk or optical disc. The reservation information storage unit 220 stores reservation information transmitted by the locker proposal server 100 . For example, the reservation information storage unit 220 stores information about reserved lockers. As a specific example, the reservation information storage unit 220 stores locker IDs for identifying reserved lockers, and information related to dates and times when lockers are reserved. In addition, the reservation information storage unit 220 stores information for specifying the user who made the reservation. For example, the reservation information storage unit 220 stores QR information. For example, the reservation information storage unit 220 stores information about the user's IC (Integrated Circuit) card.

(control unit 230)
The control unit 230 is a controller, and is implemented, for example, by executing various programs stored in a storage device inside the locker management device 200 using the RAM as a work area by the CPU, MPU, or the like. Also, the control unit 230 is a controller, and is implemented by an integrated circuit such as an ASIC or FPGA, for example.

As shown in FIG. 4, the control unit 230 has a receiving unit 231, a receiving unit 232, a determining unit 233, an unlocking unit 234, a resetting unit 235, and a transmitting unit 236, which will be described below. Realize or perform information processing operations. Note that the internal configuration of the control unit 230 is not limited to the configuration shown in FIG. 4, and may be another configuration as long as it performs information processing to be described later.

(Receiver 231)
The reception unit 231 receives reservation information transmitted from the locker proposal server 100 . For example, the receiving unit 231 receives information about reserved lockers and information for specifying the user who made the reservation. For example, the receiving unit 231 receives information about the locker ID, information about the date and time when the locker was reserved, and QR information.

(Reception unit 232)
The reception unit 232 receives information for unlocking the locker. For example, the reception unit 232 receives QR information presented by the user, input information input by the user, and information transmitted from the terminal device 10 .

(Determination unit 233)
The determination unit 233 determines whether or not to unlock the locker based on the reservation information received by the reception unit 231 and the information received by the reception unit 232 . For example, the determination unit 233 determines whether to unlock the locker based on whether the reservation information matches the information for unlocking the locker. Also, the determination unit 233 determines based on a predetermined condition for unlocking the locker. For example, the determination unit 233 determines based on a predetermined time limit. For example, the determination unit 233 determines whether information for unlocking the locker has been received within a predetermined time limit.

(Unlocking unit 234)
The unlocking unit 234 unlocks the locker based on the determination result determined by the determining unit 233 . For example, the unlocking unit 234 unlocks when the reservation information received by the receiving unit 231 and the information received by the receiving unit 232 match. For example, the unlocking unit 234 unlocks based on the user's IC card. For example, the unlocking unit 234 unlocks the locker when information for unlocking the locker is received within a predetermined time limit.

(Reset unit 235)
Reset unit 235 resets the reservation information received by receiving unit 231 . For example, the reset unit 235 resets the reservation information when the information for unlocking the locker is not received within a predetermined time limit. For example, the reset unit 235 resets the reservation information when the user finishes using the locker.

(transmitting unit 236)
The transmission unit 236 transmits the reservation information reset by the reset unit 235 to the locker proposal server 100 . For example, the transmission unit 236 transmits that the information for unlocking the locker has not been received within a predetermined time limit. For example, the transmission unit 236 transmits that the user has finished using the locker.

[4. Configuration of Locker Proposal Server]
Next, the configuration of the locker proposal server 100 according to the embodiment will be described using FIG. FIG. 5 is a diagram showing a configuration example of the locker suggestion server 100 according to the embodiment. As shown in FIG. 5 , the locker suggestion server 100 has a communication section 110 , a storage section 120 and a control section 130 . The locker proposal server 100 has an input unit (for example, a keyboard, a mouse, etc.) that receives various operations from the administrator of the locker proposal server 100, and a display unit (for example, a liquid crystal display, etc.) for displaying various information. You may

(Communication unit 110)
The communication unit 110 is implemented by, for example, a NIC. The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information between the locker management device 200 and the terminal device 10 via the network N.

(storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory device such as a RAM or flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 5 , storage unit 120 has user information storage unit 121 and locker information storage unit 122 .

The user information storage unit 121 stores information about users who use lockers. For example, the user information storage unit 121 stores information about user attributes. For example, the user information storage unit 121 stores information regarding the user's IC card. For example, the user information storage unit 121 associates and stores the acquired measurement information to be stored and the user information. Specifically, the user information storage unit 121 associates and stores the measurement information of the object to be stored and the user information acquired when the user used the locker in the past. For example, the user information storage unit 121 may store information regarding the frequency of use of the locker by the user. For example, the user information storage unit 121 may store a condition set by the user as a condition for storing the storage target. Thus, the user information storage unit 121 may have items such as "user ID", "user IC", "target", "frequency", and "condition". Here, "user ID" indicates identification information for identifying a user. "User IC" indicates code information stored inside the user's IC card. "Target" indicates information about a user's storage target. "Frequency" indicates the usage frequency of the user. "Condition" indicates a condition set by the user for each storage target.

The locker information storage unit 122 stores comprehensive information about lockers. For example, the locker information storage unit 122 stores information for identifying a locker, information on the size of a locker that can be stored, information on charges for using the locker, and information on the state of use of the locker. Here, FIG. 6 shows an example of the locker information storage unit 122 according to the embodiment. As shown in FIG. 6, the locker information storage unit 122 has items such as "locker ID", "position", "number", "size", "fee", and "status".

"Locker ID" indicates identification information for identifying a locker. "Position" indicates information about the position of the locker. The example of FIG. 6 indicates that the locker indicated by locker ID "A11" is located at the location indicated by "S1 station point AA1". In the example of FIG. 6, an example is shown in which conceptual information such as "S1 station point AA1" is stored in "position", but in reality, data of an actual place is stored. "Number" indicates information about the locker number. Specifically, "number" indicates information on a number for specifying a predetermined locker from among a plurality of lockers located at the location indicated by "position". In the example of FIG. 6, an example is shown in which conceptual information such as "BB1" and "BB2" is stored in "number", but actually number data is stored.

"Size" indicates information about the size of the locker that can be stored. The example of FIG. 6 indicates that the locker indicated by the locker ID "A11" can store the storage object of the size defined by "small". "Fee" indicates information about the fee for using the locker. "Status" indicates information about the usage status of the locker.

(control unit 130)
Returning to the description of FIG. 5, the control unit 130 is a controller, and various programs stored in a storage device inside the locker proposal server 100 are executed by the CPU, MPU, etc., using the RAM as a work area. It is realized by Also, the control unit 130 is a controller, and is implemented by an integrated circuit such as an ASIC or FPGA, for example.

As shown in FIG. 5, the control unit 130 includes an imaging unit 131, an acquisition unit 132, an identification unit 133, a proposal unit 134, a display unit 135, a reception unit 136, a transmission unit 137, and a reception unit 138. and implements or performs the information processing operations described below. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in FIG. 5, and may be another configuration as long as it performs information processing described later.

(Imaging unit 131)
The imaging unit 131 captures an image to be stored based on a user's operation. In the example shown in FIG. 1, the imaging unit 131 captures an image to be stored placed in the area FR1. Further, when there are a plurality of storage targets, the imaging unit 131 captures images of the plurality of storage targets. In addition, the imaging unit 131 may display a request to place the object to be stored in a predetermined area for imaging at the time of imaging. In addition, the imaging unit 131 may stereoscopically capture an image of the storage target using a plurality of sensors.

(Acquisition unit 132)
The acquisition unit 132 acquires measurement information to be stored. For example, the acquisition unit 132 acquires measurement information based on the image captured by the imaging unit 131 . For example, the acquisition unit 132 acquires measurement information including the length, width, and height of the object to be stored based on a plurality of images captured by the imaging unit 131 and captured by a plurality of sensors. In this case, the acquisition unit 132 may acquire the length, width, and height ratios and sizes based on coordinates predetermined for the region FR1 and image information. Also, for example, the acquiring unit 132 acquires the three-dimensional measurement information of the object to be stored based on the image captured by the imaging unit 131 and the image captured by the terminal device 10 . Further, for example, the acquisition unit 132 may acquire the three-dimensional measurement information of the object to be stored based on a combination of analysis processing of captured images and radar measurement. Further, for example, the acquisition unit 132 may acquire measurement information stored by the user information storage unit 121 . Further, for example, the acquisition unit 132 may acquire measurement information input by the user. Further, for example, the acquisition unit 132 may acquire measurement information transmitted by the terminal device 10 . Also, for example, the acquisition unit 132 may acquire the measurement information based on the image transmitted by the terminal device 10 .

(Specifying unit 133)
The specifying unit 133 specifies a locker capable of storing the storage target based on the measurement information acquired by the acquiring unit 132 . For example, the identifying unit 133 identifies a locker in which the objects to be kept can fit almost without gaps. For example, the specifying unit 133 determines that the length, width, and height of the locker are equal to or greater than the length, width, and height of the object to be stored, and that the maximum capacity of the locker is the maximum capacity of the object to be stored. Preferentially identify lockers that are closer. Alternatively, the specifying unit 133 may specify a locker in which a gap of a predetermined space or more is created when an object to be kept is placed. For example, the identifying unit 133 may preferentially identify a locker that enhances usability and is easy for the user to use. For example, the identifying unit 133 may preferentially identify the locker on the first stage when the measurement information to be stored is equal to or greater than a predetermined threshold.

The identifying unit 133 may preferentially identify a locker that enhances the usability that the user feels is easy to use, based on a predetermined condition regarding usability. For example, the identification unit 133 preferentially identifies a locker "a locker in a close location but with a high usage fee" over a locker "a locker in a distant location but with a low usage fee" according to usability. may

The identification unit 133 identifies a locker based on the movement cost required to move from a predetermined position to the locker. The movement cost may be a two-dimensional movement distance or a movement cost based on movement between floors. In this case, the identifying unit 133 may identify a plurality of locker candidates. As a specific example, the identification unit 133 identifies a locker based on the travel cost from the measurement location. For example, the identification unit 133 may identify a locker based on the travel cost from a predetermined position on the travel route to a predetermined destination accepted by the user. For example, the identification unit 133 may identify a locker based on the movement cost from a predetermined station entrance or ticket gate on the movement route. Further, the specifying unit 133 may specify a locker based on a moving cost required to move from a predetermined position to the locker and a usage cost required to use the locker. Note that the usage cost may be, for example, a usage fee paid by the user when using the locker. For example, the identifying unit 133 may identify a locker located at a location where the total sum of movement cost and usage cost is the minimum.

The specifying unit 133 may preferentially specify a locker positioned in a predetermined direction among the plurality of locker candidates. For example, when identifying two lockers located 100 meters to the right and 100 meters to the left from a predetermined position as candidates, the identification unit 133 may preferentially identify the locker located on one side. good. Further, for example, when the specifying unit 133 selects a plurality of adjacent lockers located at the same place as candidates, the specifying unit 133 may preferentially specify the locker located at the upper rightmost position. Further, the specifying unit 133 may correct the travel cost based on the attributes of the user stored by the user information storage unit 121 . For example, when the user is pregnant, the specifying unit 133 may calculate the travel cost based on the weighting applied to the travel corrected according to the attribute of the user. Further, for example, when the user is a foreigner, the specifying unit 133 may calculate the travel cost from a position that is easy to understand or easy to mark from the viewpoint of public transportation. Further, the specifying unit 133 may determine whether or not the candidate locker satisfies the conditions based on the conditions stored by the user information storage unit 121 .

If there are a plurality of storage objects, the identifying unit 133 identifies the lockers based on the measurement information of the plurality of storage objects. For example, the identifying unit 133 identifies a locker capable of storing a plurality of storage objects. The specifying unit 133 also specifies a locker that satisfies a condition for storing a plurality of storage objects. Specifically, the specifying unit 133 selects a locker that satisfies the conditions such as "Do not lay down storage object A because it is food" or "Do not place objects upside down because storage object B is fragile". Identify. For example, the identifying unit 133 identifies a locker having a size that can store the object A, based on the measurement information of the object A that is vertically long. In such a case, the specifying unit 133 specifies not only a locker in which the object A can be placed vertically, but also a locker in which the object A can be placed horizontally. Here, if a condition such as "Do not lay storage object A horizontally because storage object A is food" is set, the specifying unit 133 excludes lockers in which storage object A can be laid horizontally from the proposal targets, Only lockers that allow A to be placed vertically are subject to proposal. Further, for example, the specifying unit 133 sets a condition such as "do not put anything on storage object B because it is fragile" even if there is a locker that can store both storage object A and storage object B together. If so, the locker that can store the storage object A and the locker that can store the storage object B are individually specified. Further, for example, the identifying unit 133 may identify a locker for refrigerating or freezing. For example, the locker proposal server 100 specifies a locker for refrigerating or freezing when a condition such as "the storage object A is food" is set.

The identifying unit 133 identifies a plurality of lockers capable of storing a plurality of storage targets. For example, the identifying unit 133 may separately identify a locker capable of storing a suitcase and a locker capable of storing a bag, or may identify a locker capable of simultaneously storing a suitcase and a bag. For example, the identification unit 133 identifies multiple lockers within a predetermined distance range. Further, when specifying a plurality of lockers, the specifying unit 133 may specify information regarding a combination of a plurality of storage targets for storing a plurality of storage targets. Further, when the identification unit 133 cannot identify a plurality of lockers within a predetermined distance range, the identification unit 133 may display a message indicating that the plurality of lockers cannot be identified. Further, if the specifying unit 133 cannot specify a plurality of lockers within a predetermined distance range, the specifying unit 133 may specify another storage location where the storage target can be stored. For example, the identifying unit 133 may identify other storage locations within a predetermined distance range.

(Proposal unit 134)
The proposal unit 134 proposes the lockers identified by the identification unit 133 . For example, the proposing unit 134 proposes a locker that enhances usability and is easy for the user to use. For example, the suggestion unit 134 may suggest a locker located at a specific height according to the measurement information of the object to be stored.

The proposal unit 134 proposes lockers in an order based on predetermined conditions regarding usability. For example, the proposal unit 134 proposes lockers in a predetermined order related to usage patterns when the user uses the lockers. More specifically, the proposal unit 134 proposes lockers in order of increasing usability such that the user feels that they are easy to use. For example, the proposing unit 134 proposes lockers in order based on "the locker is located nearby but the usage fee is high".

The proposing unit 134 proposes the locker specified based on the movement cost required to move from the predetermined position to the locker. In this case, the proposal unit 134 may propose a plurality of locker candidates identified by the identification unit 133 . For example, the proposal unit 134 proposes a locker specified based on the cost of moving from the measurement location. For example, the proposal unit 134 may propose a locker identified based on the travel cost from a predetermined position on the travel route to a predetermined destination. The proposing unit 134 may propose a locker identified based on a movement cost for moving from a predetermined position to the locker and a usage cost for using the locker. For example, the proposal unit 134 may propose a locker identified based on the sum of the travel cost and the usage cost. When the identification unit 133 identifies a plurality of locker candidates, the proposal unit 134 may preferentially propose a locker located in a predetermined direction. Further, when the specifying unit 133 specifies a plurality of adjacent locker candidates located at the same location, the proposing unit 134 may, for example, preferentially suggest the locker located at the upper rightmost position.

The proposal unit 134 proposes lockers specified based on the measurement information of a plurality of objects to be stored. For example, the proposing unit 134 proposes a locker capable of storing the plurality of storage objects specified by the specifying unit 133 . Also, for example, the proposing unit 134 proposes a locker that satisfies the conditions for storing the plurality of storage objects specified by the specifying unit 133 . For example, the suggestion unit 134 suggests lockers for refrigerating or freezing. Also, the proposal unit 134 proposes a plurality of lockers identified by the identification unit 133 . For example, the proposal unit 134 proposes a plurality of lockers within the predetermined distance range identified by the identification unit 133 . Also, the proposing unit 134 proposes information regarding a combination of multiple storage objects for storing multiple storage objects in the multiple lockers specified by the specifying unit 133 . Further, the proposal unit 134 does not have to propose lockers when the identification unit 133 cannot identify a plurality of lockers within a predetermined distance range. Further, when the specifying unit 133 cannot specify a plurality of lockers within a predetermined distance range, the proposing unit 134 may suggest other storage locations where the storage target can be stored. For example, the suggesting unit 134 may suggest other storage locations within a predetermined distance range.

(Display unit 135)
The display unit 135 displays information proposed by the proposal unit 134 . For example, the display unit 135 displays information about lockers proposed by the proposal unit 134 . Specifically, the display unit 135 displays map information including information regarding the location of the locker proposed by the proposal unit 134 . In addition, the display unit 135 may display information regarding a plurality of locker candidates. In addition, the display unit 135 may display information indicating that locker reservations have been received. Further, when proposing a plurality of lockers for storing a plurality of storage targets, the display unit 135 may display information regarding a combination of the plurality of storage targets. In addition, the display unit 135 may display information to the effect that a locker cannot be proposed when a locker that satisfies a predetermined condition cannot be proposed. In this case, the display unit 135 may display information about other storage locations where the storage target can be stored.

(Reception unit 136)
Accepting unit 136 accepts an operation on the information displayed by display unit 135 . The accepting unit 136 may also accept an operation for information proposed by the proposing unit 134 . For example, the reception unit 136 receives an operation from the user on the information indicating that the locker reservation is being accepted displayed by the display unit 135 . For example, the reception unit 136 may receive a selection from the user for information regarding a plurality of locker candidates displayed by the display unit 135 .

(Sending unit 137)
The transmitting unit 137 transmits locker reservation information to the locker management device 200 based on the operation received by the receiving unit 136 . For example, the transmission unit 137 transmits information about the reserved locker and information for specifying the user who made the reservation. Specifically, the transmission unit 137 transmits information about the locker ID of the reserved locker, information about the date and time when the locker reservation was accepted, and information for unlocking the locker.

(Receiver 138)
The receiving unit 138 receives the reservation information reset by the locker management device 200 . For example, the receiving unit 138 receives information that unlocking of the locker has not been accepted within a predetermined time limit. For example, the receiving unit 138 receives information indicating that the user has finished using the locker.

[5. Proposal processing flow]
Next, a procedure of proposal processing by the proposal system 1 according to the embodiment will be described with reference to FIG. FIG. 7 is a flowchart showing a procedure of proposal processing by the proposal system 1 according to the embodiment.

As shown in FIG. 7, the locker proposal server 100 acquires measurement information to be stored (step S201). For example, the locker proposal server 100 acquires the measurement information of the storage target based on the captured image of the storage target. The locker proposal server 100 identifies a locker capable of storing the storage target based on the acquired measurement information (step S202). Here, although not shown in FIG. 7, the locker suggestion server 100 may perform a process of determining whether or not the specified locker satisfies the conditions set by the user. The locker proposal server 100 proposes the identified locker (step S203). Here, the locker suggestion server 100 may perform a process of proposing the specified locker when the specified locker satisfies the conditions set by the user. The locker suggestion server 100 also suggests the identified locker along with map information including information about the location of the identified locker. Also, for example, the locker proposal server 100 makes a proposal by displaying information about the identified locker. Then, the locker proposal server 100 waits until the user's reservation for the proposed locker is accepted.

Subsequently, when the locker proposal server 100 accepts the user's reservation for the proposed locker (Step S<b>204 ; Yes), the locker proposal server 100 transmits locker reservation information to the locker management device 200 . If the locker proposal server 100 accepts not to make a reservation for the proposed locker (step S204; No), the locker proposal server 100 ends without transmitting locker reservation information. Further, if the locker proposal server 100 does not receive an operation for the proposal from the user within a predetermined time, the locker proposal server 100 regards it as having received the fact that the proposed locker is not to be reserved, and transmits locker reservation information. You can exit without

[6. Modification]
The proposed system 1 according to the above-described embodiment may be implemented in various different forms other than the above-described embodiment. Therefore, another embodiment of the proposed system 1 will be described below.

In the above-described embodiment, the locker proposal server 100 reserves a proposed locker based on the user's operation directly accepted by the locker proposal server 100 . Here, the locker proposal server 100 may reserve a locker proposed by the locker proposal server 100 based on the user's operation accepted by the terminal device 10 . A procedure of the proposal process according to the modification will be described with reference to FIG.

In step S<b>201 of FIG. 7 , the locker proposal server 100 acquires the measurement information of the storage target based on the image captured by the terminal device 10 . In step S202 of FIG. 7, the locker proposal server 100 identifies a locker capable of storing the storage target based on the acquired measurement information. In step S<b>203 of FIG. 7 , the locker proposal server 100 transmits information about the identified locker to the terminal device 10 . In step S<b>204 of FIG. 7 , the locker proposal server 100 waits until it receives from the terminal device 10 information indicating that the specified locker is to be reserved.

In step S205 of FIG. 7, the locker proposal server 100 transmits information for unlocking the identified locker to the terminal device 10 when receiving the instruction to reserve the identified locker. In this case, the locker proposal server 100 transmits reservation information regarding the reservation of the identified locker to the locker management device 200 . Further, when the locker proposal server 100 receives an instruction not to reserve the specified locker, the locker suggestion server 100 terminates without transmitting information for unlocking the specified locker. Further, if the locker proposal server 100 does not receive an instruction regarding the reservation of the specified locker within a predetermined time, the locker proposal server 100 considers that it has received an instruction not to reserve the specified locker, and opens the specified locker. It may end without transmitting the information for locking.

[7. effect〕
As described above, the locker proposal server 100 according to the embodiment has the acquisition unit 132 , the identification unit 133 and the proposal unit 134 . Acquisition unit 132 acquires measurement information of an object to be stored in a locker. The specifying unit 133 specifies a locker capable of storing the storage target based on the measurement information acquired by the acquiring unit 132 . The proposal unit 134 proposes the locker identified by the identification unit 133 to the user.

As a result, the locker proposal server 100 according to the embodiment can give the user an opportunity to use the locker without the user having to search for a locker capable of storing the object to be kept. Thus, the locker proposal server 100 according to the embodiment can improve usability for a user who wants to use a locker to store his/her personal luggage.

Further, the acquisition unit 132 acquires the measurement information of the object to be stored based on the captured image of the object to be stored.

As a result, the locker proposal server 100 according to the embodiment acquires the measurement information of the object to be stored based on the image, so that usability can be further improved.

Also, the acquisition unit 132 acquires the measurement information based on the information transmitted from the terminal device used by the user.

Thereby, the locker proposal server 100 according to the embodiment can give the user an opportunity to use the locker regardless of the measurement location.

Further, the identifying unit 133 identifies lockers in an order based on predetermined conditions regarding usability.

Thereby, the locker proposal server 100 according to the embodiment can propose a locker with higher usability to the user.

Further, the identifying unit 133 identifies the locker based on the movement cost required to move from the predetermined position to the locker.

Accordingly, the locker proposal server 100 according to the embodiment can propose a locker based on the movement cost to the user.

Further, the specifying unit 133 specifies a locker based on the cost of moving from the measuring place where the object to be kept is measured.

Thereby, the locker proposal server 100 according to the embodiment can propose a locker to the user based on the movement cost from the measurement location.

Further, the identifying unit 133 identifies a locker based on the movement cost from a predetermined position on the movement route to the predetermined destination accepted by the user.

Thereby, the locker proposal server 100 according to the embodiment can propose a locker located on the travel route. Further, the locker proposal server 100 according to the embodiment can propose a locker to the user based on the movement cost from the movement route.

Further, the identifying unit 133 identifies the locker based on the movement cost and the usage cost of using the locker.

Thereby, the locker proposal server 100 according to the embodiment can propose a locker based on the usage cost to the user.

In addition, the identifying unit 133 identifies the locker at the position where the sum of the movement cost and the usage cost is minimized.

Thereby, the locker proposal server 100 according to the embodiment can propose closer and cheaper lockers to the user.

Further, when there are a plurality of lockers whose movement cost falls within a predetermined range, the identifying unit 133 preferentially identifies a locker located in a predetermined direction among the plurality of lockers.

Thereby, the locker proposal server 100 according to the embodiment can clarify a group of lockers that are not being used and a group of lockers that are being used.

Further, when there are a plurality of storage targets, the specifying unit 133 specifies a locker based on the measurement information of the plurality of storage targets.

Thereby, the locker proposal server 100 according to the embodiment can specify a locker in which a plurality of storage objects can be stored.

The specifying unit 133 also specifies a locker that satisfies a condition for storing a plurality of storage objects.

Thereby, the locker proposal server 100 according to the embodiment can specify a locker for storing a storage target that requires specific management when storing.

Further, the identifying unit 133 identifies a plurality of lockers capable of storing a plurality of storage targets.

Thereby, the locker proposal server 100 according to the embodiment can identify a plurality of lockers.

The identifying unit 133 also identifies a plurality of lockers within a predetermined distance range.

Thereby, the locker suggestion server 100 according to the embodiment can identify a plurality of nearby lockers.

In addition, the proposing unit 134 proposes information regarding a combination of multiple storage targets for storing multiple storage targets in multiple lockers.

As a result, the locker suggestion server 100 according to the embodiment can propose more specific information regarding locker usage to the user.

In addition, the proposal unit 134 does not propose a locker when a plurality of lockers cannot be identified within a predetermined distance range.

As a result, the locker proposal server 100 according to the embodiment can propose only lockers that are easy for the user to use.

The proposing unit 134 also proposes other storage locations where the storage target can be stored.

As a result, the locker suggestion server 100 according to the embodiment can propose another storage location when there is no locker that is easy for the user to use.

[8. Hardware configuration]
Further, the locker proposal server 100, the locker management device 200, and the terminal device 10 according to the embodiments described above are implemented by, for example, a computer 1000 configured as shown in FIG. FIG. 8 is a hardware configuration diagram showing an example of a computer that implements the functions of the locker proposal server 100, the locker management device 200, and the terminal device 10. As shown in FIG. Computer 1000 has CPU 1100 , RAM 1200 , ROM 1300 , HDD 1400 , communication interface (I/F) 1500 , input/output interface (I/F) 1600 and media interface (I/F) 1700 .

The CPU 1100 operates based on programs stored in the ROM 1300 or HDD 1400 and controls each section. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, a program depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. Communication interface 1500 receives data from another device via a predetermined communication network, sends the data to CPU 1100, and transmits data generated by CPU 1100 to another device via a predetermined communication network.

The CPU 1100 controls output devices such as displays and printers, and input devices such as keyboards and mice, through an input/output interface 1600 . CPU 1100 acquires data from an input device via input/output interface 1600 . CPU 1100 also outputs the generated data to an output device via input/output interface 1600 .

Media interface 1700 reads programs or data stored in recording medium 1800 and provides them to CPU 1100 via RAM 1200 . CPU 1100 loads such a program from recording medium 1800 onto RAM 1200 via media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. etc.

For example, when the computer 1000 functions as the locker proposal server 100, the locker management device 200, and the terminal device 10 according to the embodiment, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to control the control unit 130, It implements the functions of 230 and 14. CPU 1100 of computer 1000 reads these programs from recording medium 1800 and executes them, but as another example, these programs may be obtained from another device via a predetermined communication network.

[9. others〕
Further, among the processes described in the above embodiments and modifications, all or part of the processes described as being performed automatically can be performed manually, or described as being performed manually. All or part of the processing can also be performed automatically by known methods. In addition, information including processing procedures, specific names, various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

Also, each component of each device illustrated is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured.

Also, the above-described embodiments and modifications can be appropriately combined within a range that does not contradict the processing content.

As described above, some of the embodiments of the present application have been described in detail based on the drawings. It is possible to carry out the invention in other forms with modifications.

Also, the above-mentioned "section, module, unit" can be read as "means" or "circuit". For example, the acquisition unit can be read as acquisition means or an acquisition circuit.

1 proposal system 10 terminal device 11 communication unit 12 input unit 13 output unit 14 control unit 100 locker proposal server 110 communication unit 120 storage unit 121 user information storage unit 122 locker information storage unit 130 control unit 131 imaging unit 132 acquisition unit 133 identification unit 134 proposal unit 135 display unit 136 reception unit 137 transmission unit 138 reception unit 141 imaging unit 142 acquisition unit 143 transmission unit 144 reception unit 145 display unit 146 second transmission unit 147 second reception unit 200 locker management device 210 communication unit 220 reservation information Storage unit 230 Control unit 231 Reception unit 232 Reception unit 233 Determination unit 234 Unlock unit 235 Reset unit 236 Transmission unit

Claims (19)

an acquisition unit that acquires measurement information of an object to be stored in a locker;
Based on the measurement information acquired by the acquisition unit and a predetermined condition specified based on the attribute information of the storage object and specifying how the storage object is placed on the locker , a specifying unit that specifies a locker that satisfies the predetermined condition and can store the storage object;
a proposal unit that proposes the locker identified by the identification unit to the user;
The proposed device, characterized by comprising: The acquisition unit
2. The proposal device according to claim 1, wherein measurement information of said object to be stored is acquired based on an image of said object to be stored. The acquisition unit
3. The proposal device according to claim 1, wherein the measurement information is obtained based on information transmitted from a terminal device used by a user. The identification unit
The suggesting device according to any one of claims 1 to 3, wherein the lockers are identified in an order based on predetermined conditions regarding usability. The identification unit
5. The proposing device according to any one of claims 1 to 4, wherein the locker is specified based on the cost of moving from a predetermined position to the locker. The identification unit
6. The proposing device according to claim 5, wherein the locker is specified based on the cost of moving from a measuring place where the object to be stored is measured. The identification unit
6. The proposal device according to claim 5, wherein the locker is identified based on the travel cost from the predetermined position on the travel route to a predetermined destination accepted by the user. The identification unit
8. The proposing device according to any one of claims 5 to 7, wherein the locker is specified based on the moving cost and the usage cost of using the locker. The identification unit
9. The proposal device according to claim 8, wherein the locker located at a position that minimizes the sum of the movement cost and the usage cost is specified. The identification unit
Claims 5 to 9, characterized in that when there are a plurality of lockers whose movement cost falls within a predetermined range, the locker located in a predetermined direction is preferentially identified among the plurality of lockers. The proposed apparatus according to any one of . The identification unit
The proposal device according to any one of claims 1 to 10, wherein when there are a plurality of storage objects, the locker is specified based on measurement information of the plurality of storage objects. The identification unit
12. The proposing device according to claim 11, wherein the locker that satisfies a condition for storing the plurality of storage objects is specified. The identification unit
13. The proposal device according to claim 11 or 12, wherein a plurality of lockers capable of storing the plurality of storage objects are specified. The identification unit
14. The suggestion device of claim 13, wherein the suggestion device identifies the plurality of lockers within a predetermined distance range. The proposal department
15. The proposal device according to claim 14, wherein information regarding a combination of the plurality of storage objects for storing the plurality of storage objects in the plurality of lockers is proposed. The proposal department
15. The proposal device according to claim 14, wherein the locker is not proposed when the plurality of lockers cannot be identified within the predetermined distance range. The proposal department
17. The proposal device according to claim 16, which proposes another storage location capable of storing the storage object. A proposed method implemented by a computer, comprising:
an acquisition step of acquiring measurement information of an object to be stored in a locker;
Based on the measurement information obtained by the obtaining step and a predetermined condition specified based on the attribute information of the object to be stored and specifying how to place the object to be stored on the locker , a specifying step of specifying a locker that satisfies the predetermined conditions and can store the storage object;
a proposing step of proposing the locker identified by the identifying step to the user;
A proposed method comprising: an acquisition procedure for acquiring measurement information of an object to be stored in a locker;
Based on the measurement information acquired by the acquisition procedure and a predetermined condition specified based on the attribute information of the storage object and specifying how the storage object is placed on the locker , a specifying procedure for specifying a locker that satisfies the predetermined conditions and can store the storage object;
a proposal procedure for proposing the locker identified by the identification procedure to the user;
A proposed program characterized by causing a computer to execute

Images