JP2015221200A - Delivery system, locker device and delivery management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enhance convenience in delivery of articles.SOLUTION: A method of utilizing a locker for delivering an article comprises: accepting a delivery request specifying the locker as a delivery destination of the article; locking the locker when the article is stored in the locker on the basis of the delivery request; and notifying a requester of the delivery request about retrieval key data required for unlocking. Here, when the article is stored in the locker and the delivery key data is accepted, the delivery key data is put in a delivery notification stand-by state and, when it is determined that delivery operation is complete, the delivery notification is performed for the delivery key data in the delivery notification stand-by state.

Description

  The present invention relates to a delivery system, a locker device, and a delivery management method for delivering an article.

  Conventionally, when delivering a package to a home or the like, it is necessary that the recipient who receives the package is at home. If the recipient is absent, delivery cannot be completed even if he / she has the parcel to the delivery destination, and the delivery is performed again, which places a heavy burden on the recipient and the delivery company.

  Therefore, delivery time specification, receipt at convenience stores, delivery boxes, etc. are used. For example, the delivery box disclosed in Patent Document 1 automatically responds to a visitor, and if a specific word is identified from the visitor's voice, the visitor's response type is determined as “delivery”, and the package A technique for notifying a voice message for guiding the warehousing is disclosed.

JP2013-126498A

  However, since the installation and operation of the delivery box as disclosed in the above-mentioned prior art is costly, it is used only in a part of an apartment house, and the actual situation is that the installation in a general house is not progressing. . Moreover, even if such a delivery box is used, there remains a restriction that it can be received only at home.

  The receiving service at the convenience store has a large merit for the recipient because there is no additional cost for the recipient and the receiving location can be selected to some extent. However, there is a problem that it places a heavy burden on the convenience store side.

  Even when the delivery time is designated, it is not always possible to stay home at the designated time, so there is a possibility that a situation where the delivery cannot be performed may occur. Moreover, since it can be received only at home, it is not convenient for a person who has a short stay at home.

  For these reasons, there is a need for further improvement in convenience for both the delivery side and the receiving side. In particular, in recent years, the use of services such as Internet shopping on the premise of delivery of goods has increased, and the efficiency of delivery has become increasingly important.

  The present invention has been made to solve the above-described problems of the prior art, and an object of the present invention is to provide a delivery system, a locker device, and a delivery management method that can improve the convenience of delivery of articles. .

  In order to solve the above-described problems and achieve the object, the present invention provides a delivery system for delivering an article, the locker device having a locker capable of storing and locking the article, and delivering the locker to the article. A delivery request accepting means for accepting a delivery request specified as a destination; a delivery instruction means for instructing delivery of the article based on the delivery request accepted by the delivery request accepting means; and in response to an instruction from the delivery instruction means When an article is stored in the locker, a locker for locking the locker, and unlocking data necessary for unlocking the locker locked by the locker are notified to the requester of the delivery request. And an unlocking data notifying means.

  Further, the present invention, in the above invention, further comprises usage status management means for managing the usage status of the locker, wherein the delivery request receiving means is the delivery destination from the locker determined to be usable by the usage status management means. It is characterized by accepting designation of a locker.

  Further, the present invention is the above invention, wherein the locker device further comprises unlocking data generation means for generating the unlocking data when the locker is locked by the locking means, and the unlocking data notification The means is characterized by notifying the unlocking data to the requester of the delivery request and the recoverer who collects the article when the article is not received by the requester.

  Further, the present invention is the above invention, wherein the unlocking data generation means sets an expiration date for the use of the unlocking data by the request source, and the use of the unlocking data by the collector A waiting period is set for the above.

  Further, the present invention is the above invention, wherein the unlocking data generating means is for the unlocking by the recoverer when the unlocking data cannot be used by the requester due to the expiration date. The expiration date and the waiting period are set so that data can be used.

  Further, the present invention is the above invention, wherein the delivery instruction means generates delivery data specifying the delivery request, the locking means identifies and locks the delivery data, and the unlocking data notification The means is characterized by notifying the unlocking data to a delivery requester specified by the delivery data.

  Further, the present invention is the above invention, wherein the delivery request accepting unit specifies an article to be purchased and accepts a delivery request for designating the locker as a delivery destination of the article. It is characterized by instructing a store of an article specified as a purchase target to sell the article and deliver it to the locker.

  In addition, the present invention is a locker device having a locker that can lock a product and locks the delivery request identifying means for identifying a delivery request specifying the locker as a delivery destination of the product, and the product is stored in the locker Locking means for locking the locker, and unlocking data notifying means for notifying the requester of the delivery request of unlocking data necessary for unlocking the locker locked by the locking means. It is characterized by comprising.

  The present invention is also a delivery management method for managing delivery of an article, the delivery request accepting step for accepting a delivery request for designating a locker that can store and lock the article as a delivery destination of the article, and the delivery A delivery instruction step for instructing delivery of the article based on the delivery request received in the request acceptance step, and locking the locker when the article is stored in the locker in accordance with an instruction in the delivery instruction step A locking step; and an unlocking data notification step of notifying the requester of the delivery request of unlocking data necessary for unlocking the locker locked by the locking step.

  According to the present invention, unlocking data necessary for receiving a delivery request designating a locker as a delivery destination of an article, locking and unlocking the article when the article is stored in the locker based on the delivery request. Is notified to the requester of the delivery request, the locker is used for delivery of the article, and the convenience in delivery of the article can be improved.

FIG. 1 is an explanatory diagram for explaining the concept of the delivery system according to the first embodiment. FIG. 2 is an explanatory diagram for explaining Internet shopping according to the present invention. FIG. 3 is an external configuration diagram showing an external configuration of the locker device. FIG. 4 is a block diagram showing an internal configuration of the rocker device. FIG. 5 is an explanatory diagram of the locker management data shown in FIG. FIG. 6 is a block diagram showing the internal configuration of the server. FIG. 7 is an explanatory diagram of the order management data shown in FIG. FIG. 8 is a flowchart showing a processing procedure of the locker device. FIG. 9 is a flowchart for explaining the details of the delivery work reception process shown in FIG. FIG. 10 is a flowchart for explaining the details of the take-out acceptance process shown in FIG. FIG. 11 is a flowchart showing the processing procedure of the server. FIG. 12 is an explanatory diagram for explaining the concept of the delivery system according to the second embodiment. FIG. 13 is an explanatory diagram for explaining internet shopping according to the second embodiment. FIG. 14 is a block diagram illustrating an internal configuration of the rocker device according to the second embodiment. FIG. 15 is a block diagram illustrating the internal configuration of the server according to the second embodiment. FIG. 16 is an explanatory diagram for dealing with misplacement. FIG. 17 is a flowchart showing a processing procedure for handling misplacement in the clerk mode.

  Exemplary embodiments of a delivery system, a locker device, and a delivery management method according to the present invention will be described below in detail with reference to the accompanying drawings.

  First, the concept of the delivery system according to the first embodiment will be described. FIG. 1 is an explanatory diagram for explaining the concept of the delivery system according to the first embodiment. The delivery system according to the first embodiment is characterized in that the locker device 10 can be selected as a delivery destination.

  The locker device 10 has a plurality of lockers for storing articles, and can lock the plurality of lockers individually. Moreover, it is preferable to install the locker device 10 in public facilities such as a plurality of stations. The locker device 10 may have a coin locker function that assumes that the same person performs deposit and removal of articles, but in the first embodiment, for the sake of simplicity of explanation, delivery used only as an article delivery destination. The dedicated locker device 10 will be described as an example.

  A user (for example, a purchaser of an article as will be described later) operates the terminal device 30 and makes a delivery request for the article to the server 20 (1). In this delivery request, the locker of the locker device 10 can be selected as a delivery destination.

  Upon receiving the delivery request, the server 20 instructs the delivery company to deliver the article (2). Here, the server 20 generates delivery key data corresponding to the delivery request, and includes the delivery key data in the delivery instruction. The delivery company stores the article in the locker of the locker device 10 based on the delivery instruction and causes the locker device 10 to read the delivery key data.

  The locker device 10 locks the locker in which the article is stored, and generates takeout key data for unlocking the lock. Then, a delivery notice including delivery key data and take-out key data is transmitted to the server 20 (3). The delivery notification performed by the locker device 10 to the server 20 is referred to as a “first delivery notification” for convenience.

  The server 20 that has received the first delivery notification identifies the delivery request by the delivery key data, and transmits a delivery notification including the take-out key data to the terminal device 30 that is the requester of the delivery request (4). The delivery notification performed by the server 20 to the terminal device 30 is referred to as a “second delivery notification” for convenience. When the user causes the locker device 10 to read out the extraction key data included in the second delivery notification (5), the locker device 10 unlocks the corresponding locker, so that the user can receive the goods. It becomes possible.

  In this way, a delivery request specifying the locker as the delivery destination of the article is accepted, and when the article is stored in the locker based on the delivery request, the extraction key data necessary for unlocking and unlocking is requested. By notifying the requester, the locker can be used for delivery of goods. Therefore, it is possible to realize a delivery system that is highly convenient for both the delivery side and the reception side.

  In addition, for example, when a single delivery company stores a plurality of articles in different lockers based on a plurality of delivery requests, a delivery notification is not sent to the requester each time the items are stored in one locker. It is preferable to wait until the storage of a plurality of articles to be delivered as a series of operations is completed, and then notify the requester. This is to prevent an erroneous delivery notification from reaching the request source when the correspondence between the stored article and the delivery key data is erroneously operated.

  Next, a specific example when the delivery system according to the present invention is applied to Internet shopping will be described. FIG. 2 is an explanatory diagram for explaining Internet shopping according to the present invention.

  In the example shown in FIG. 2, the server 20 provides a sales site for selling goods. Specifically, the server 20 can display and control information on articles sold by the store 40, and can accept purchase operations for the articles, that is, orders. Further, the server 20 can acquire data indicating an empty locker that can be used as a delivery destination from the locker device 10.

  The purchaser operates the terminal device 30 to access the server 20 and purchases a desired article (1). This purchase corresponds to the delivery request. If the locker of the locker device 10 is desired as the delivery destination of the purchased item, the server 20 controls the display of an empty locker of the locker device 10 and accepts the selection of the delivery destination.

  When the purchase is made, the server 20 issues an order number (2). Furthermore, if the delivery destination is a locker, the server 20 generates delivery key data corresponding to the order number (3). Thereafter, the server 20 places an order with respect to the store 40 (4). This order corresponds to the delivery instruction. In ordering, the store 40 is notified of the order number and delivery key data in addition to the information specifying the purchased item and its delivery destination.

  The store 40 ships the purchased item according to the order (5). Delivery key data is attached to the article. When a numeric string or a two-dimensional barcode is used as the delivery key data, the delivery key data can be attached by printing on the slip.

  The delivery company 50 delivers the goods shipped from the store 40 to the designated locker device 10 (6). Then, the article is stored in the designated locker, and the delivery key data is read by the locker device 10.

  The locker device 10 locks the locker in which the article is stored, and generates takeout key data which is unlocking data for unlocking the lock (7). The retrieval key data is used by the purchaser to receive the item. Further, when the purchaser does not receive the article within the set time limit, the article can be used for the delivery company to collect the article. The extraction key data may be in an arbitrary format such as a numeric string or a two-dimensional barcode.

  The locker device 10 transmits a first delivery notification including delivery key data and take-out key data to the server 20 (7).

  Receiving the first delivery notification, the server 20 specifies the order number from the delivery key data, and transmits a second delivery notification including the extraction key data to the purchaser's terminal device 30 (8). The purchaser can know that the purchased item is stored in the designated locker by the second delivery notification, and can unlock the locker with the take-out key data and take out the purchased item.

  If the purchaser does not take out the article for a predetermined period after the article is stored in the locker of the locker device 10, the server 20 issues a collection instruction to the delivery company 50 (9). This collection instruction includes the extraction key data. Therefore, the delivery company 50 can take out and collect the articles using the take-out key data. In this case, the use of the extraction key data by the purchaser may be invalidated and the terminal device 30 notified accordingly. By enabling the delivery company 50 to collect the article using the take-out key data, it is possible to prevent the locker from being occupied for a long period of time.

  Next, the external configuration of the locker device 10 will be described. FIG. 3 is an external configuration diagram showing an external configuration of the locker device 10. As shown in FIG. 3, the locker device 10 includes a plurality of lockers including lockers L01b and L02b, and a lock mechanism corresponding to each locker. For example, the lock mechanism L01a is a mechanism that locks and unlocks the locker L01b, and the lock mechanism L02a is a mechanism that locks and unlocks the locker L02b. Furthermore, the locker device 10 has a user interface including a display operation unit 11.

  Next, the internal configuration of the locker device 10 will be described. FIG. 4 is a block diagram showing an internal configuration of the rocker device 10. As shown in FIG. 4, the locker device 10 includes a display operation unit 11, a code reader 12, a receipt issuing unit 13, a communication unit 14, a storage unit 15, and a control unit 16. The locker device 10 includes a plurality of lockers including lockers L01b and L02b, and lock mechanisms (L01a and L02a, etc.) corresponding to the lockers.

  The display operation unit 11 includes a touch panel color liquid crystal display and the like, and is used for displaying information to the delivery company 50 and the purchaser and receiving various inputs. When numeric strings are used as the delivery key data and the extraction key data, the display operation unit 11 accepts these inputs.

  The code reader 12 is a reading unit for reading delivery key data and take-out key data. When two-dimensional barcodes are used as delivery key data and take-out key data, the code reader 12 is configured by a camera that captures these images and an image processing unit.

  The receipt issuing unit 13 is a printer unit for issuing receipts as necessary, such as when delivering or taking out articles. The communication unit 14 is an interface unit for communicating with the server 20 via a predetermined communication line. The storage unit 15 is a storage device composed of a hard disk device, a nonvolatile memory, or the like. The storage unit 15 stores locker management data 15a.

  The control unit 16 is a control unit that controls the locker device 10 as a whole, and includes a locker management unit 16a, a delivery work reception unit 16b, a delivery key data identification unit 16c, a duplication determination unit 16d, an unlocking data generation unit 16e, and a lock control. Unit 16f, notification standby processing unit 16g, and delivery notification execution unit 16h. Actually, programs corresponding to these functional units are stored in a ROM or a non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the locker management unit 16a, The delivery operation receiving unit 16b, the delivery key data identification unit 16c, the duplication determination unit 16d, the unlocking data generation unit 16e, the lock control unit 16f, the notification standby processing unit 16g, and the delivery notification execution unit 16h are caused to execute corresponding processes. It will be.

  The locker management unit 16a is a processing unit that manages the state of each locker. The locker management unit 16a updates the locker management data 15a when the state of the locker is changed. Further, the locker availability data indicated in the locker management data 15a is appropriately transmitted to the server 20.

  The locker status includes “empty”, “waiting for delivery”, “waiting for delivery notification”, “delivered”, and “being out of order”. “Empty” is a state that can be selected as a new delivery destination because no items are stored in the locker and no items are scheduled to be delivered. “Delivery wait” is a state in which the delivery destination is selected but the article is not stored. “Waiting for delivery notification” is a state in which the delivery destination is selected and the article is stored, but waiting for delivery notification to be executed because other delivery work remains. “Delivery completed” is a state where the delivery destination is selected, the article is stored, and a delivery notification is made. This state is a state in which an article exists in the locker and is waiting for removal by the purchaser or delivery company 50. If the purchaser or the delivery company 50 takes out the locker, the locker state is “empty”. In addition, other states such as “failing” are provided.

  If the locker status is “delivery waiting”, “waiting for delivery notification” or “delivered”, the locker is associated with delivery key data, and the delivery key data uniquely identifies the delivery request and locker. Function as. Therefore, if the locker status is “delivery waiting”, “waiting for delivery notification” or “delivery completed”, the status of the delivery key data is “delivery waiting”, “waiting for delivery notification” or “delivery completed”. It can be treated as being.

  The delivery work accepting unit 16b is a processing unit that accepts delivery work by the delivery company 50. Specifically, the delivery work receiving unit 16b authenticates a trader code given in advance to the delivery trader 50 as an operation corresponding to the start of the delivery work. After the delivery work is started, the delivery work acceptance unit 16b accepts delivery key data. In addition, after receiving one or a plurality of delivery key data, a delivery end operation which is an operation indicating the end of the delivery work can be received. If there is no locker in the “delivery waiting” state due to the receipt of the delivery key data, it is possible to determine the end of the delivery work regardless of the delivery end operation.

  As for the authentication of the supplier code, for example, the input supplier code may be transmitted to the server 20 to make an inquiry, and the authentication result by the server 20 may be received. In such a configuration, the server 20 manages the registration, deletion, update, etc. of the supplier code, thereby reducing the risk that the supplier code is illegally used. In addition, if the latest supplier code is periodically received from the server device 20 and held in the locker device 10, an inquiry to the server 20 is not required at the time of authentication of the supplier code. The situation of failure can be avoided.

  The delivery key data identification unit 16c is a processing unit that identifies whether or not the delivery key data is legitimate data. If the server 20 generates delivery key data, the locker device 10 holds the delivery key data notified from the server 20 at the time of purchase establishment, etc., if the delivery key data is notified to the locker device 10. The delivery key data can be identified by comparing with the delivery key data received from the delivery company 50. If the server 20 generates the delivery key data and the configuration is such that the delivery key data is not notified to the locker device 10, the locker device 10 transmits the delivery key data received from the delivery agent 50 to the server 20. It may be inquired whether it is data.

  The duplication determination unit 16d determines whether or not duplication has occurred between the delivery key data received from the start to the end of the delivery work when a single delivery company 50 stores a plurality of articles in different lockers. It is a processing part which determines whether. Specifically, when new delivery key data is received, the duplication determination unit 16d determines whether or not it overlaps with existing delivery key data that has already been received and is in the “delivery notification standby” state.

  The unlocking data generation unit 16e is a processing unit that generates unlocking data corresponding to the delivery key data received from the delivery company 50. The unlocking data generation unit 16e generates extraction key data as unlocking data. The retrieval key data is used when the purchaser receives the item. The take-out key data is also used for collecting the goods when the purchaser does not receive the goods. The extraction key data may be in an arbitrary format such as a numeric string or a two-dimensional barcode.

  In addition, the unlocking data generation unit 16e sets an expiration date for use of the extraction key data by the purchaser, thereby determining a receipt time limit that is a time limit for the purchaser to receive the article. Further, the unlocking data generation unit 16e determines a collection period for collecting the articles. A waiting period may be provided between the delivery of the article and the start of the collection period.

  Specifically, by setting a waiting period, it is preferable to set the reception deadline and the start time of the collection period to coincide. In this case, only the purchaser can take out the goods until the receipt deadline, and if the purchaser does not receive the goods within the receipt deadline, the purchaser cannot take out the goods and can be taken out by the delivery company 50. Become.

  Note that the receipt deadline may be set after the start of the collection period. In this case, at the beginning of the collection period, it is possible for either the purchaser or the delivery company 50 to take out the article. The same applies when the receipt deadline is set to indefinite. Further, an end point may be set in the collection period, or collection may be made indefinitely after the start of the collection period.

  The lock control unit 16f is a processing unit that controls locking / unlocking of the locker by transmitting a locking instruction or an unlocking instruction to the lock mechanisms L01a, L02a and the like. The lock control unit 16f is provided on the condition that if the delivery agent 50 stores the article in the locker and the delivery key data is read, the read delivery key data does not overlap with the delivery key data in the “waiting for delivery notification” state. The locker in which the article is stored is locked, and the read delivery key data and the extracted key data are associated with each other. Further, the read delivery key data is changed from the “delivery waiting” state to the “delivery notification waiting” state.

  If the read delivery key data overlaps with the delivery key data in the “waiting for delivery notification” state, the lock control unit 16f unlocks the locker corresponding to the duplicated delivery key data in the “waiting for delivery notification” state. At this time, the duplicate delivery key data in the “waiting for delivery notification” state is changed to the “waiting for delivery” state.

  Further, the lock control unit 16f unlocks the corresponding locker when the extraction key data is read. At this time, the unlocked locker is changed to the “empty” state.

  The notification standby processing unit 16g is a processing unit that sets the delivery key data received from the delivery company 50 from the “delivery standby” state to the “delivery notification standby” state. When the delivery work accepting unit 16b determines that the delivery work has been completed, the delivery notice execution unit 16h performs delivery notice for the delivery key data in the “delivery notification standby” state, and changes the state to the “delivered” state. It is a processing unit. The delivery notification by the delivery notification execution unit 16h includes delivery key data and take-out key data, and is transmitted to the server 20.

  The receipt issuing unit 13 may issue a receipt to the delivery company 50 when the delivery notification is executed. On this receipt, the delivery date and time, the door number assigned to the locker door, delivery key data, etc. are printed and used as a copy of delivery.

  Next, the locker management data 15a shown in FIG. 4 will be described. FIG. 5 is an explanatory diagram of the locker management data 15a shown in FIG. As shown in FIG. 5, the locker management data 15a includes data related to delivery and take-out in addition to basic data.

  The locker management data 15a includes a locker ID, a door number, and a state as basic data. The locker ID is identification information that uniquely identifies the locker. The door number is a number assigned to the locker door. The status indicates the locker status by values such as “0: empty”, “1: delivery waiting”, “2: delivery notification waiting”, “3: delivered”, “7: in failure”, and the like.

  The locker management data 15a includes delivery key data and delivery date / time as data relating to delivery. The delivery key data is delivery key data corresponding to a delivery request with the locker as a delivery destination. The delivery date and time indicates the date and time when the state becomes “3: delivery completed”.

  The locker management data 15a includes take-out key data, receipt deadline, collection period, take-out date and time, and take-out type as data relating to take-out. The extraction key data is generated and stored by the unlocking data generation unit 16e. The receipt time limit and the collection period are set and stored by the unlocking data generation unit 16e. The extraction date / time indicates the date / time when the locker is unlocked by the extraction key data. When the locker is unlocked by the extracted key data, the locker state is “0: empty”.

  The extraction type takes one of the values “0: waiting for extraction”, “1: received”, and “2: recovered”. When the status becomes “3: Delivery completed”, the extraction type is first set to “0: waiting for extraction”. After that, when the takeout key data is used by the purchaser and the locker is unlocked, the takeout type is set to “1: received”. If the delivery key 50 uses the extraction key data and the locker is unlocked, the extraction type is set to “2: collected”. Whether the take-out key data is used by the purchaser or the delivery company 50 can be identified, for example, by whether or not a delivery company code of the delivery company 50 has been received.

  Next, the internal configuration of the server 20 will be described. FIG. 6 is a block diagram showing the internal configuration of the server 20. As illustrated in FIG. 6, the server 20 is connected to the display unit 21 and the input unit 22, and includes a communication unit 23, a storage unit 24, and a control unit 25.

  The display unit 21 is a liquid crystal panel, a display device, or the like. The input unit 22 is a keyboard, a mouse, or the like. The communication unit 23 is an interface unit for performing data communication with the locker device 10, the terminal device 30, the store 40, the delivery company 50, and the like via a communication line. The storage unit 24 is a storage device such as a hard disk device or a non-volatile memory, and stores order management data 24a and business registration data 24b.

  The control unit 25 is a control unit that controls the entire server 20, and includes a locker state acquisition unit 25a, an order reception unit 25b, a delivery key data generation unit 25c, an order processing unit 25d, a delivery key data confirmation unit 25e, and a delivery notification execution unit. 25f and a collection instruction unit 25g. Actually, programs corresponding to these functional units are stored in a ROM or non-volatile memory (not shown), and these programs are loaded into the CPU and executed, thereby obtaining a locker state acquisition unit 25a and an order reception unit 25b. The delivery key data generation unit 25c, the order processing unit 25d, the delivery key data confirmation unit 25e, the delivery notification execution unit 25f, and the collection instruction unit 26g are caused to execute corresponding processes.

  The locker state acquisition unit 25a is a processing unit that acquires the state of the locker from the locker device 10 as necessary. The order receiving unit 25b is a processing unit that displays and controls information on articles sold by the store 40 in response to access from the terminal device 30 and receives orders.

  The order receiving unit 25b issues an order number for the received order. When a locker is designated as the delivery destination of the received order, the locker state acquisition unit 25a acquires the locker state, and accepts the delivery destination selection from the empty locker.

  The delivery key data generating unit 25c is a processing unit that generates delivery key data corresponding to the order number when the order receiving unit 25b receives an order with a locker as a delivery destination. Delivery key data can be generated by any method. For example, the delivery key data may be combined with the order number and the supplier code of the delivery company 50. The trader code of the delivery trader 50 is registered in the business registration data 24b and updated as appropriate. Therefore, by combining the order number issued by the order receiving unit 25b and the trader code of the delivery trader 50 in charge of delivery of the order, delivery key data that uniquely identifies the delivery request can be obtained. The order processing unit 25d is a processing unit that places an order to the store 40 based on the order received by the order receiving unit 25b. In ordering, the store 40 is notified of the order number and delivery key data in addition to the information specifying the purchased item and its delivery destination.

  The delivery key data confirmation unit 25e is a processing unit that identifies the order number by the delivery key data included in the delivery notification when the delivery notification is received from the locker device 10. In addition, when the delivery key data confirmation unit 25e receives an inquiry from the locker device 10 as to whether the delivery key data is legitimate data, the delivery key data confirmation unit 25e confirms whether the delivery key data is data generated by itself, The result can be returned to the locker device 10. Further, when the delivery key data confirmation unit 25e receives an inquiry about the trader code from the locker device 10, the delivery key data confirmation unit 25e authenticates the trader code depending on whether or not the trader code is registered in the business operator registration data 24b. To the locker device. The delivery key data confirmation unit 25e can also periodically transmit the latest supplier code to the locker device 10.

  The delivery notification execution unit 25f is a processing unit that, when receiving a delivery notification from the locker device 10, transmits a delivery notification to the purchaser's terminal device 30 based on the order number specified by the delivery key data confirmation unit 25e. . This delivery notification includes the extraction key data.

  The collection instruction unit 25g is a processing unit that issues a collection instruction to the delivery company 50 when there is extraction key data that has entered the collection period without being received by the purchaser. The collection instruction includes the extraction key data.

  Next, the order management data 24a shown in FIG. 6 will be described. FIG. 7 is an explanatory diagram of the order management data 24a shown in FIG. As shown in FIG. 7, the order management data 24a includes data related to delivery and receipt in addition to basic data.

  The order management data 24a includes, as basic data, an order number, order item data, purchaser data, order destination data, delivery destination data, and status. The order number is identification information issued by the order receiving unit 25b and uniquely identifying the order. The order item data is data for specifying the type and number of ordered items. The purchaser data is data indicating the name and address of the purchaser. The order destination data is data for specifying the store 40, and the delivery destination data is data indicating the delivery destination of the article.

  The status indicates the status of the order by values such as “1: received order”, “2: ordered”, “3: delivered”, “4: received”, “5: collected”. “1: Order received” indicates that an order number has been issued and the order has not been placed at the store 40. “2: Ordered” indicates that an order has been placed at the store 40 and delivery has not been completed. “3: Delivery completed” indicates that the article is stored in the locker and has not been taken out. “4: Received” indicates that the item has been removed by the purchaser. “5: Collected” indicates that the item has been taken out by the delivery company 50.

  The order management data 24a includes delivery key data and delivery date / time as data relating to delivery. The delivery key data is delivery key data corresponding to the order. The delivery date and time indicates the date and time when the state becomes “3: delivery completed”.

  The order management data 24a includes take-out key data, receipt deadline, collection period, and take-out date / time as data relating to take-out. The extraction key data, the reception deadline, and the collection period are included in the delivery notification from the locker device 10. The extraction date / time indicates the date / time when the locker is unlocked by the extraction key data.

  Next, the processing procedure of the locker device 10 will be described. FIG. 8 is a flowchart showing a processing procedure of the locker device 10. The locker device 10 first updates the locker management data 15a by the locker management unit 16a, and notifies the server 20 of the state of the locker (step S101). Next, the delivery work acceptance unit 16b performs delivery work acceptance processing by the delivery company 50 (step S102), and the lock control unit 16f performs article take-out acceptance processing by the purchaser or delivery company 50 (step S103). Exit.

  FIG. 9 is a flowchart for explaining the details of the delivery work reception process shown in FIG. First, the delivery work reception unit 16b determines whether or not a delivery start operation has been received (step S201). In the delivery start operation, a delivery start button or the like may be provided on the touch panel, and reading of the supplier code may be regarded as a delivery start operation.

  If the delivery start operation has not been received (step S201; No), the delivery work accepting unit 16b ends the delivery work accepting process. If the delivery start operation is accepted (step S201; Yes), the delivery work accepting unit 16b authenticates the supplier code (step S202). If the merchant code has not been read in step S201, a display output for requesting the delivery merchant 50 to input the merchant code is performed. If authentication of the read merchant code has failed (step S202; No), the merchant code authentication failure is notified and the delivery work acceptance process is terminated. In addition, for authentication of a trader code, for example, three grace periods may be set, and re-input of the trader code may be accepted up to three times.

  If the authentication of the merchant code is successful (step S202; Yes), the delivery key data identification unit 16c identifies the delivery key data received from the delivery company 50 (step S203). As a result of the identification, if it is not regular delivery key data (step S204; No), the process proceeds to step S203 to identify new delivery key data.

  As a result of the identification, if it is legitimate delivery key data (step S204; Yes), the duplication determination unit 16d determines whether or not it overlaps with the delivery key data in the “delivery notification standby” state (step S205). .

  If it overlaps with the delivery key data in the “delivery notification standby” state (step S205; Yes), the lock control unit 16f unlocks the locker corresponding to the duplicate delivery key data in the “delivery notification standby” state ( In step S206), the duplicated delivery key data in the “delivery notification waiting” state is changed to the “delivery waiting” state. In addition, the display operation unit 11 notifies the occurrence of duplication by displaying (step S208), and proceeds to step S203. Here, the delivery company 50 puts a load in a locker and closes the door.

  If there is no overlap with the delivery key data in the “delivery notification standby” state (step S205; No), the unlocking data generation unit 16e generates the extraction key data (step S209). Then, the lock control unit 16f locks the locker in which the article is stored (step S210), and sets the state of the delivery key data to the “delivery notification standby” state (step S211).

  After step S211, the delivery work accepting unit 16b determines whether there is no other delivery key data in the “delivery waiting” state (step S212). If delivery key data in the “delivery waiting” state remains (step S212; No), the delivery work receiving unit 16b determines whether or not a delivery end operation, which is an operation indicating the end of the delivery work, has been received (step S212; No). Step S213). If the delivery end operation has not been accepted (step S213; No), the process proceeds to step S203, and the next delivery key data is identified.

  When there is no delivery key data in the “delivery waiting” state (step S212; Yes), or when a delivery end operation is accepted (step S213; Yes), the delivery notification execution unit 16h receives the delivery key in the “delivery notification waiting” state. A delivery notification is executed for the data, the status is changed to the “delivered” state (step S214), and the delivery work acceptance process is terminated.

  FIG. 10 is a flowchart for explaining the details of the take-out acceptance process shown in FIG. First, the lock control unit 16f determines whether or not the supplier code has been authenticated (step S301). When the vendor code is read and the authentication is successful (step S301; Yes), the lock control unit 16f controls the display of the vendor menu screen on the display unit 21 (step S307).

  If the supplier code has not been read or authentication of the supplier code has failed (step S301; No), the lock control unit 16f displays the menu screen used by the purchaser, It is determined whether authentication has been performed (step S302). Specifically, the extracted key data is read, and it is authenticated whether the extracted key data is regular data and is within the expiration date. If the extraction key data has not been read or the authentication of the extraction key data has failed (step S302; No), the lock control unit 16f ends the extraction reception process. If the extraction key data is successfully authenticated (step S302; Yes), the lock control unit 16f unlocks the locker corresponding to the extraction key data (step S303). Here, the purchaser takes out the package. The lock control unit 16f sets the extraction date / time of the locker management data 15a to the current date / time, sets the extraction type to “received” (step S304), and sets the status to “empty” (step S305). Thereafter, the lock control unit 16f notifies the server 20 of the completion of reception (step S306), and ends the takeout acceptance process.

  On the other hand, after controlling the display of the trader menu screen on the display unit 21 in step S307, the lock control unit 16f determines whether or not the extraction key data has been authenticated (step S308). Specifically, the extraction key data is read, and it is authenticated whether the extraction key data is regular data and within the collection period. If the extraction key data has not been read or authentication of the extraction key data has failed (step S308; No), the lock control unit 16f ends the extraction reception process.

  If the extraction key data is successfully authenticated (step S308; Yes), the lock control unit 16f unlocks the locker corresponding to the extraction key data (step S309). Then, the extraction date / time of the locker management data 15a is set to the current date / time, the extraction type is set to “collected” (step S310), and the state is set to “empty” (step S311). Thereafter, the lock control unit 16f notifies the server 20 of the completion of collection (step S312), and ends the takeout acceptance process.

  Next, the processing procedure of the server 20 will be described. FIG. 11 is a flowchart showing a processing procedure of the server 20. First, the order receiving unit 25b determines whether or not an order has been received (step S401).

  If the order is accepted (step S401; Yes), the order acceptance unit 25b issues an order number (step S402), and the delivery key data generation unit 25c generates delivery key data (step S403). Then, the order processing unit 25d places an order to the store 40 (step S404).

  After completion of step S404, or when no order has been received (step S401; No), the delivery key data confirmation unit 25e determines whether or not a delivery notification has been received from the locker device 10 (step S405).

  If the delivery notification is received from the locker device 10 (step S405; Yes), the delivery key data confirmation unit 25e specifies the order number by the delivery key data included in the delivery notification (step S406). Then, the delivery notification execution unit 25f transmits a delivery notification to the purchaser's terminal device 30 based on the identified order number (step S407).

  After completion of step S407 or when a delivery notification has not been received from the locker device 10 (step S405; No), the collection instructing unit 25g receives the extraction key data that has entered the collection period without being received by the purchaser. It is determined whether or not there exists, that is, whether or not there is a delivery request that has entered the collection period without being received by the purchaser (step S408).

  If there is no take-out key data that has entered the collection period without being received by the purchaser (step S408; No), the process is terminated as it is. If there is extraction key data that has entered the recovery period without being received by the purchaser (step S408; Yes), the recovery instruction unit 25g transmits a recovery instruction to the delivery company 50 ( Step S409), the process is terminated.

  As described above, in the delivery system according to the first embodiment, a delivery request designating a locker as an item delivery destination is received, and when the article is stored in the locker based on the delivery request, the lock is performed and the unlocking is performed. The locker can be used for delivery of the article by notifying the requester of the delivery request of the take-out key data necessary to do so. Therefore, it is possible to realize a delivery system that is highly convenient for both the delivery side and the reception side.

  In addition, when an article is stored in a locker and delivery key data is received, the delivery key data is set to a delivery notification standby state, and when it is determined that the delivery operation is completed, the delivery key data in the delivery notification standby state is delivered. Since the notification is configured to be executed, it is possible to prevent an erroneous delivery notification from reaching the request source when the correspondence between the stored article and the delivery key data is erroneously operated.

  As described above, in the first embodiment, the case where the locker device 10 performs the process related to the delivery notification hold has been described as an example, but the server 20 may perform the process related to the delivery notification hold. In this case, the locker device 10 sends a delivery notification (first delivery notification) to the server 20 every time the delivery key data is read, and the server 20 sends a delivery notification to the terminal device 30 until it is determined that the delivery work is completed. (Second delivery notice) is put on hold.

  Further, although description is omitted in the first embodiment, the locker in the “empty” state or the “delivery waiting” state may be locked or unlocked. When locking in the “delivery waiting” state, the corresponding locker is unlocked by reading the delivery key data.

  Further, in the first embodiment, a recovery period is set for the extraction key data, and it is set so that the article cannot be recovered using the extraction key data before entering the recovery period. Is not essential, and the extraction key data may be usable for recovery immediately after generation. In this case, the collection timing is controlled by adjusting the timing at which the extraction key data is transmitted from the server 20 to the delivery company 50.

  In the first embodiment, the case where the end of the delivery work is determined regardless of the delivery end operation when there is no delivery key data in the “delivery waiting” state has been described. A combination of delivery key data used in the work may be managed, and it may be determined that the delivery work is finished when all the delivery key data used in one delivery work is “delivered”. With this configuration, even when the delivery company divides the delivery work into a plurality of times, the end of the delivery work can be accurately determined. This is because the end of the delivery work can be determined even if the delivery key data not associated with the delivery work being accepted is “delivery waiting”.

  In the second embodiment, a modified example showing the use of the two-dimensional barcode and the countermeasure against the wrong insertion of articles will be described. FIG. 12 is an explanatory diagram for explaining the concept of the delivery system according to the second embodiment.

  The user operates the terminal device 130 to request delivery of an article to the server 120 (1). In this delivery request, the locker of the locker device 110 can be selected as a delivery destination. The terminal device 130 is a portable terminal and has a display unit that can display a two-dimensional barcode.

  Upon receiving the delivery request, the server 120 instructs the delivery company to deliver the article (2). Here, the server 120 generates delivery key data corresponding to the delivery request, and includes a delivery key code that is a two-dimensional barcode obtained by encoding the delivery key data in the delivery instruction. The delivery company stores the article in the locker of the locker device 110 based on the delivery instruction, and holds the delivery key code over the camera of the locker device 110.

  The locker device 110 captures the delivery key code and decrypts it to obtain delivery key data. Further, the locker device 110 locks the locker in which the article is stored, and generates takeout key data for unlocking the lock. Then, a delivery notification including delivery key data and take-out key data is transmitted to the server 120 (3). The delivery notification performed by the locker device 110 to the server 120 is referred to as a “first delivery notification” for convenience.

  The server 120 that has received the first delivery notification identifies the delivery request by the delivery key data, generates a take-out key code that is a two-dimensional barcode obtained by encoding the take-out key data, and is a terminal that is the request source of the delivery request A delivery notification including the extraction key code is transmitted to the device 130 (4). The delivery notification performed by the server 120 to the terminal device 130 is referred to as a “second delivery notification” for convenience. This second delivery notification is made by e-mail, for example. In this case, the retrieval key code is attached to the electronic mail as image data and can be displayed on the display unit of the terminal device 130.

  The user carries the mobile terminal 130, displays the extraction key code on the display unit of the mobile terminal 130, and holds it over the camera of the locker device 110. The locker device 110 captures the extracted key code and decrypts it to obtain the extracted key data. Since the locker corresponding to the take-out key data is unlocked, the user can receive the article (5).

  As described above, if the delivery key data and the extraction key data are encoded into the two-dimensional barcode, the locker device 110 can be read by holding the code, and it takes input of the delivery key data and the extraction key data. Labor can be reduced and mistakes can be prevented.

  Next, a specific example when the delivery system according to the second embodiment is applied to Internet shopping will be described. FIG. 13 is an explanatory diagram for explaining internet shopping according to the second embodiment.

  In the example shown in FIG. 13, the server 120 provides a sales site for selling goods. Specifically, the server 120 can display and control information on articles sold by the store 140, and can accept purchase operations for the articles, that is, orders. Further, the server 120 can acquire data indicating an empty locker that can be used as a delivery destination from the locker device 110. The server 120 has an encoding function for generating a two-dimensional barcode, and the locker device 110 has a decoding function for decoding the two-dimensional barcode.

  The purchaser operates the terminal device 130 to access the server 120 and purchases a desired article (1). This purchase corresponds to the delivery request. If the locker of the locker device 110 is desired as the delivery destination of the purchased item, the server 120 controls the display of an empty locker of the locker device 110 and accepts the selection of the delivery destination.

  When the purchase is made, the server 120 issues an order number (2). Further, if the delivery destination is a locker, the server 120 generates delivery key data corresponding to the order number (3a), and encodes the generated delivery key data into a delivery key code that is a two-dimensional barcode ( 3b). Thereafter, the server 120 places an order with respect to the store 140 (4). This order corresponds to the delivery instruction. In ordering, the store 140 is notified of the order number and the delivery key code, in addition to the information specifying the purchased item and its delivery destination.

  The store 140 ships the purchased item according to the order (5). A delivery key code is attached to the article. The delivery company 150 delivers the goods shipped from the store 140 to the designated locker device 110 (6). Then, the article is stored in the designated locker, and the delivery key code is held over the camera of the locker device 110.

  The locker device 110 captures the delivery key code and decrypts it to obtain delivery key data (7a). Further, the locker device 110 locks the locker in which the article is stored, and generates take-out key data that is unlocking data for unlocking the lock (7b). The retrieval key data is used by the purchaser to receive the item. Further, when the purchaser does not receive the article within the set time limit, the article can be used for the delivery company to collect the article.

  The locker device 110 transmits a first delivery notification including delivery key data and take-out key data to the server 120 (7c).

  Upon receiving the first delivery notification, the server 120 identifies the order number from the delivery key data, generates a take-out key code that is a two-dimensional barcode obtained by encoding the take-out key data (8a), and purchaser's terminal device A second delivery notification including the extraction key code is transmitted to 130 (8b). The purchaser can know that the purchased item is stored in the designated locker by the second delivery notification, and unlocks the locker by holding the take-out key code over the camera of the locker device 110. Purchased items can be taken out.

  If the purchaser does not take out the article for a predetermined period or more after the article is stored in the locker of the locker device 110, a collection instruction including the takeout key code is transmitted to the delivery company 150 (9). The delivery company 150 can take out and collect the article by holding the take-out key code over the camera of the locker device 110.

  Next, the internal configuration of the locker device 110 will be described. FIG. 14 is a block diagram illustrating an internal configuration of the locker device 110 according to the second embodiment. In the locker device 110, the code reader 12 includes a camera 12a and an image processing unit 12b. Moreover, the point which the control part 116 further has the decoding process part 116a and the attendant mode process part 116b differs from the locker apparatus 10 shown in FIG. Since other configurations and operations are the same as those of the rocker device 10 shown in FIG. 4, the same components are denoted by the same reference numerals and description thereof is omitted.

  The camera 12a of the code reader 12 is an imaging device that images a delivery key code and an extraction key code. The image processing unit 12b detects a two-dimensional barcode from the image captured by the camera 12a, performs binarization processing, etc., and outputs the result to the control unit 116.

  The decoding processing unit 116a is a processing unit that performs a decoding process on the two-dimensional barcode detected by the image processing unit 12b. Delivery key data or take-out key data is obtained by this decryption processing. Accordingly, the delivery work accepting unit 16b accepts the delivery key data decrypted from the delivery key code by the decryption processing unit 116a. Further, the lock control unit 16f unlocks the corresponding locker when the decryption processing unit 116a decrypts the extracted key data from the extracted key code.

  The clerk mode processing unit 116b is a processing unit that controls the operation in the clerk mode that is an operation mode used by the clerk of the maintenance company. Maintenance of the locker device 110 is performed by a staff member of a maintenance company different from the delivery company 150 or the like.

  As specifically described in the first embodiment, when the delivery key data is duplicated, the locker device 110 can detect the duplication and suppress transmission of an erroneous delivery notification. However, if a misplacement of goods occurs, the delivery key data does not overlap, so there is a possibility that an incorrect delivery notification will reach the user. Specifically, the locker corresponding to the delivery notification is in a state where other articles are contained. In such a case, it is necessary to take out articles with different insertions and reinsert them correctly.

  However, when the corresponding locker is unlocked using the extracted key data, the unlocked locker is changed to the “empty” state. Therefore, when opening the locker in order to deal with misplacement, the above-mentioned clerk mode is used, and the locker is unlocked and re-locked without changing the locker state, that is, in the “delivered” state. .

  Next, the internal configuration of the server 120 will be described. FIG. 15 is a block diagram of an internal configuration of the server 120 according to the second embodiment. As shown in FIG. 15, the server 120 is different from the server 20 shown in FIG. 6 in that the control unit 125 further includes an encoding processing unit 125a. Since other configurations and operations are the same as those of the server 20 illustrated in FIG. 6, the same components are denoted by the same reference numerals and description thereof is omitted.

  The encoding processing unit 125a is a processing unit that generates a two-dimensional barcode by encoding. Specifically, the encoding processing unit 125a generates a delivery key code from the delivery key data and generates an extraction key code from the extraction key data.

  Next, how to deal with misplacement will be described. FIG. 16 is an explanatory diagram for dealing with misplacement. FIG. 16A shows a state where the article P1 and the article P2 are correctly stored in the lockers.

  Specifically, the delivery key data “D1111” is attached to the article P1, and the delivery key data “D2222” is attached to the article P2. The article P1 is correctly stored in the associated locker “L1111”, and the article P2 is correctly stored in the associated locker “L2222”.

  As a result, a delivery notification of the product P1 is transmitted to the user who purchased the product P1, and the delivery notification includes the takeout key “K1111” for unlocking the locker “L1111”. Therefore, the user who purchased the article P1 can unlock the locker “L1111” and receive the article P1. Similarly, a delivery notification of the product P2 is transmitted to the user who purchased the product P2, and the delivery notification includes an extraction key “K2222” for unlocking the locker “L2222”. Therefore, the user who purchased the article P2 can unlock the locker “L2222” and receive the article P2.

  FIG. 16 (b1) shows a state where the article P1 and the article P2 are misplaced. Specifically, the article P1 to which the delivery key data “D1111” is attached is erroneously stored in the locker “L2222” instead of the associated locker “L1111”, and the article to which the delivery key data “D2222” is attached. P1 is erroneously stored in the locker “L1111”, not the associated locker “L2222”.

  As a result, a delivery notification of the product P1 is transmitted to the user who purchased the product P1, and the delivery notification includes the takeout key “K1111” for unlocking the locker “L1111”. However, since the article P2 is stored in the locker “L1111”, the article P1 cannot be received. Similarly, a delivery notification of the product P2 is transmitted to the user who purchased the product P2, and the delivery notification includes an extraction key “K2222” for unlocking the locker “L2222”. However, since the article P1 is stored in the locker “L2222”, the article P2 cannot be received.

  If such a misplacement is found, the clerk replaces the article as shown in FIG. 16 (b2). By using the clerk mode for this replacement, it is possible to replace only the article while maintaining the state of the locker. The article P1 is correctly stored in the locker “L1111” and the article P2 is correctly stored in the associated locker “L2222”. It becomes a state.

  For this reason, when the user who purchased the article P1 unlocks the locker “L1111”, the article P1 can be received. Similarly, when the user who purchased the article P2 unlocks the locker “L2222”, the article P2 can be received.

  Next, a processing procedure for handling misplacement in the staff mode will be described. FIG. 17 is a flowchart showing a processing procedure for handling misplacement in the clerk mode. The attendant mode processing unit 116b first determines whether or not a misplacement reporting operation has been accepted (step S501). This misplacement reporting operation is performed by a user or a delivery company. For example, when the user who has received the delivery notification unlocks the locker with the take-out key code and notices that the wrong article is contained, the user performs a misplacement reporting operation on the display operation unit 11. In addition, when the delivery company notices the wrong insertion after putting the article in the locker and locking it, the wrong insertion reporting operation is performed on the display operation unit 11.

  If a misplacement reporting operation has not been received (step S501; No). The attendant mode processing unit 116b ends the process as it is. If a misplacement report operation is accepted (step S501; Yes). The staff mode processing unit 116b makes a staff call (step S502). The clerk call is made by communication with the maintenance company.

  When the clerk call is made, the clerk is dispatched to the locker device 110. The locker device 110 determines whether or not authentication of the dispatched staff has been performed (step S503). If the clerk is not authenticated (step S503; No), the process proceeds to step S503 and waits for the clerk to be authenticated.

  If the clerk is authenticated (step S503; Yes), the clerk mode processing unit 116b starts the clerk mode (step S504). Then, the first locker, which is one of the lockers in which a misplacement has occurred, is forcibly unlocked (step S505). The locker is forcibly unlocked by a key exclusively for an attendant, and is an unlocking that does not change the state of the locker. The clerk takes out the article from the first locker forcibly unlocked. Thereafter, the locker device 110 locks the first locker (step S506).

  After step S506, the clerk mode processing unit 116b forcibly unlocks the second locker, which is the other of the lockers where the misplacement has occurred (step S507). The clerk takes out the article from the second locker forcibly unlocked, and puts the article taken out from the first locker. Thereafter, the locker device 110 locks the second locker (step S508).

  After step S508, the attendant mode processing unit 116b forcibly unlocks the first locker again (step S509). The clerk puts the article taken out from the second locker. Put in the first locker. Thereafter, the locker device 110 locks the first locker (step S510). After step S510, the clerk mode processing unit 116b ends the clerk mode (step S511) and ends the process.

  As described above, in the delivery system according to the second embodiment, the delivery key data and the retrieval key data are encoded and used as a two-dimensional barcode, and therefore the locker device 110 can be read by holding the code over the delivery key data. It is possible to reduce labor for inputting delivery key data and take-out key data, and to prevent occurrence of mistakes.

  In addition, in the delivery system according to the second embodiment, it is possible to cope with the misplacement of articles by using the clerk mode capable of unlocking and locking the locker without changing the locker state. Correct goods can be delivered without discarding the lock data.

  Each configuration illustrated in the first and second embodiments is functionally schematic and does not necessarily need to be physically configured as illustrated. In other words, the form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part thereof may be functionally / physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured.

  As described above, the delivery system, the locker device, and the delivery management method according to the present invention are suitable for improving convenience in delivery of articles.

DESCRIPTION OF SYMBOLS 10, 110 Locker apparatus 11 Display operation part 12 Code reader 12a Camera 12b Image processing part 13 Receipt issuing part 14, 23 Communication part 15, 24 Storage part 15a Locker management data 16, 25, 116, 125 Control part 16a Locker management part 16b Delivery work reception unit 16c Delivery key data identification unit 16d Duplicate determination unit 16e Unlocking data generation unit 16f Lock control unit 16g Notification standby processing unit 16h Delivery notification execution unit 20, 120 Server 21 Display unit 22 Input unit 24a Order management data 24b Business registration data 25a Locker state acquisition unit 25b Order reception unit 25c Delivery key data generation unit 25d Order processing unit 25e Delivery key data confirmation unit 25f Delivery notification execution unit 25g Collection instruction unit 30, 130 Terminal device 40, 140 Store 50, 150 delivery 'S 116a decoding section 116b clerk mode processing section 125a encoding unit L01a, L02a locking mechanism L01b, L02b locker

Claims (9)

A delivery system for delivering goods,
A locker device having a locker for storing and locking the article;
A delivery request accepting means for accepting a delivery request designating the locker as a delivery destination of the article;
Delivery instruction means for instructing delivery of the article based on the delivery request received by the delivery request receiving means;
Locking means for locking the locker when an article is stored in the locker according to an instruction by the delivery instruction means;
A delivery system comprising: unlocking data notifying means for notifying unlocking data required for unlocking the locker locked by the locking means to the requester of the delivery request. It further comprises usage status management means for managing the usage status of the locker,
The delivery system according to claim 1, wherein the delivery request accepting unit accepts designation of a locker serving as the delivery destination from a locker determined to be usable by the usage status managing unit. The locker device further includes unlocking data generation means for generating the unlocking data when the locker is locked by the locking means,
The unlocking data notification means notifies the unlocking data to a requester of the delivery request and a recoverer who collects the article when the article is not received by the requester. The delivery system according to claim 1 or 2.   The unlocking data generation means sets an expiration date for the use of the unlocking data by the requester, and sets a waiting period for the use of the unlocking data by the collector The delivery system according to claim 3, wherein the delivery system is characterized.   The unlocking data generation means is configured to enable the unlocking data to be used by the recoverer when the requester cannot use the unlocking data due to the expiration date. The delivery system according to claim 4, wherein a deadline and the waiting period are set. The delivery instruction means generates delivery data for specifying the delivery request;
The locking means identifies and locks the delivery data,
The delivery according to any one of claims 1 to 5, wherein the unlocking data notification means notifies the unlocking data to a requester of a delivery request specified by the delivery data. system. The delivery request acceptance means identifies an article to be purchased and accepts a delivery request for designating the locker as a delivery destination of the article,
The delivery instruction means instructs the store of the article specified as the purchase target to sell the article and deliver it to the locker. The delivery system described. A locker device having a locker capable of storing and locking an article,
A delivery request identifying means for identifying a delivery request designating the locker as a delivery destination of the article;
A locking means for locking the locker when an article is stored in the locker;
A locker device comprising: unlocking data notifying means for notifying the requester of the delivery request of unlocking data necessary for unlocking the locker locked by the locking means. A delivery management method for managing delivery of goods,
A delivery request accepting step for accepting a delivery request for designating a locker storing and locking the article as a delivery destination of the article;
A delivery instruction step for instructing delivery of the article based on the delivery request accepted by the delivery request acceptance step;
A locking step for locking the locker when an article is stored in the locker in accordance with an instruction by the delivery instruction step;
And a unlocking data notifying step of notifying the requester of the delivery request of unlocking data necessary for unlocking the locker locked in the locking step.

Images