JP6563265B2 - Delivery support system and delivery support method - Google Patents

Description

  The present invention relates to a delivery support system and delivery support method for supporting delivery.

  When delivering a delivery item, the delivery person often goes to the delivery address and delivers the package to the recipient. If the recipient is absent, an absence slip is issued, a contact from the recipient is awaited, and redelivery, transfer, etc. are performed. The absence of the recipient is a burden on the delivery company such as labor, delivery cost, and luggage storage space. In addition, the recipient may be bothered and burdened by delays in receiving the package and adjusting the schedule for receiving the package.

  In view of this, a package transportation system for reducing the situation in which the recipient is absent has been studied (see Patent Document 1). According to the technique described in this patent document, the user DB accumulates the desired package receipt time in advance. The Web server receives the delivery information transmission request transmitted from the service staff terminal. Then, the collection / delivery master extracts the delivery information, the user DB extracts the desired time for receiving the package based on the consignee user identification information included in the delivery information, and the Web server determines the desired time for receiving the package. Reply to the device.

  In addition, a technique for delivering a product to a home delivery locker, instead of directly delivering it to a recipient, has been studied (see Patent Document 2). According to the technique described in this patent document, the home delivery management unit receives the ordering information from the ordering terminal and instructs the user to deliver the ordered food to the apartment. The home delivery locker into which the food has been carried in transmits the carry-in completion information to the locker management unit. When receiving the carry-in completion information, the locker management unit updates the use state of the home delivery locker, and transmits the delivery completion information to a pre-registered notification destination. The ordered food is delivered to the home delivery locker while being contained in the food container. When the food container is carried in by the user, the home delivery locker transmits the container return information to the locker management unit.

  Further, a technique for receiving luggage such as a convenience store has been studied (see Patent Document 3). According to the technique described in this patent document, a recipient of a package can use a terminal such as a PC or a mobile phone to set a delivery service server based on the package ID and the URL of the delivery service server described in the absence slip. Access and specify the desired date and time of receiving the package and the package receiving location such as a convenience store where the authentication terminal is installed. Subsequently, when the settlement information for storing the delivery fee is transmitted, the home delivery service server generates identification information used when receiving the package, and transmits it to the recipient's terminal and the authentication terminal. When receiving the package, the recipient of the package goes to the receiving place and presents the identification information. When it is confirmed that the identification information is valid, the package is delivered to the recipient.

JP 2003-150869 A JP 2012-64072 A JP 2003-196354 A

  In the technique described in Patent Literature 1, when many delivery requests occur in one delivery time zone, time adjustment may be difficult. Furthermore, if there is an urgent need for the recipient, there is a possibility that it cannot be received. Also, if there is a range of delivery times, the recipient may have to wait.

  Moreover, in the technique described in Patent Document 2, it is necessary to provide a locker for housing a delivery item in an apartment house such as an apartment. However, it is difficult to arrange lockers unless the scale is such as a housing complex.

  On the other hand, in the technique described in Patent Document 3, it is necessary to visit a convenience store as a delivery destination. In this case, when the luggage is large or heavy, the burden of taking it out is large for the recipient. Convenience stores also have a burden of storing and delivering luggage.

  The present invention has been made to solve the above problems, and it is an object of the present invention to provide a delivery support system and a delivery support method for efficient delivery.

  (1) A delivery support system that solves the above problems includes a control unit connected to a delivery person terminal and a shipper terminal, a receiving box code of a receiving box for storing deliverables, an installation location, and information on the installer. An installation information storage unit that stores information, and a request information storage unit that stores delivery information of deliverables. And the said control part acquires the receiving box code as delivery destination information from the said 1st process which acquires the receiving information about a receiving box code, an installation place, and an installer, and registers into the said installation information storage part, and the said sender | caller terminal. If acquired, the installation information storage unit sends the confirmation result of the installation status of the receiving box to the sender terminal, and the delivery information is delivered to the request information storage unit when a delivery request for delivery is received. A third process for storing information; a receiving box code specified based on information printed on a delivery label of a delivery in the delivery person terminal; and a receiving box code displayed in the receiving box at the delivery destination And a fourth process of recording delivery completion information in the request information storage unit based on the collation result. Thereby, delivery can be delivered to the receiving box.

  (2) In the delivery support system, it is preferable that, in the fourth process, the delivery person terminal outputs a delivery completion slip of the delivery item when the receiving box code can be collated. Thereby, the efficiency of the work at the time of delivery of a delivery thing can be aimed at.

  (3) In the fourth process, the delivery support system preferably transmits a delivery completion notice to the installer terminal of the receiving box when the delivery completion is recorded in the request information storage unit. Thereby, the installation person of a receiving box can grasp | ascertain the delivery with respect to a receiving box.

  (4) In the fourth process, the delivery support system preferably transmits a delivery completion notice to the delivery requester terminal of the delivery when the delivery completion is recorded in the request information storage unit. Thereby, the delivery requester of the delivery can grasp the delivery to the receiving box.

(5) It is preferable that the delivery support system acquires a use history of the receiving box based on delivery information recorded in the request information storage unit. Thereby, the utilization condition of a receiving box can be grasped | ascertained.

  (6) In the delivery support system, structure information of the receiving box is recorded in the installation information storage unit, and delivery item information is acquired together with the delivery destination information from the sender terminal. It is preferable that the structure information of the receiving box associated with the receiving box code of the information is acquired, and the collation result between the structure information and the delivery item information is returned to the sender terminal. Accordingly, it is possible to determine whether delivery to the receiving box is possible based on a comparison between the delivery information (for example, the type and size of the package) and the structure information of the receiving box.

  According to the present invention, delivery can be performed efficiently.

Schematic of the system of this embodiment. It is explanatory drawing of the receiving box of this embodiment, Comprising: (a) is a locked state, (b) is an unlocked state, (c) is an accommodation state of a delivery thing, (d) is explanatory drawing of the locked state after accommodation. . It is explanatory drawing of the data recorded on the memory | storage part of this embodiment, Comprising: (a) is an installation information storage part, (b) is explanatory drawing of a request information storage part. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. It is explanatory drawing of the process sequence of other embodiment, Comprising: (a) is delivery of an unlocking key, (b) is use of an unlocking key, (c) is explanatory drawing of deletion of an unlocking key. Explanatory drawing of the process sequence of other embodiment.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that a product sold by mail order is delivered to a delivery destination designated by a purchaser (user). Here, the product is delivered to a storage box (receiving box) for receiving a delivery set installed in the purchaser's home. Further, in the present embodiment, it is assumed that delivery personnel of a plurality of delivery companies deliver delivery items.

As shown in FIG. 1, in this embodiment, a receiving box 10, a management server 20, a user terminal 30, a seller server 40, and a delivery person terminal 50 are used.
As shown in FIG. 2A, the receiving box 10 is a rectangular parallelepiped storage container and has an internal space. The receiving box 10 is provided with a door 11 and a locking part 12. By closing the door 11, the internal space is sealed. The locking unit 12 includes a key operation unit for inputting an unlocking key. In this embodiment, the locking unit 12 stores a unique unlocking key of each receiving box 10 and an unlocking key assigned to the delivery company, and unlocking the door 11 by inputting these unlocking keys. To do.

  As shown in FIG. 2 (b), the delivery can be stored in the internal space of the receiving box 10 by unlocking the locking portion 12 and opening the door 11. Further, a receiving box label on which the code image 13 is printed is attached inside the receiving box 10. In this embodiment, the case where it is affixed inside the door 11 is assumed. In the code image 13, a receiving box code individually assigned to each receiving box 10 is encoded.

As shown in FIG. 2 (c), the delivery item is stored in the internal space of the receiving box 10 when the delivery item is delivered.
And as shown in FIG.2 (d), the receiving box 10 is locked by the locking part 12 by closing the door 11. As shown in FIG.

  A user terminal 30 shown in FIG. 1 is a computer terminal (installer terminal of a receiving box) used by a user of the receiving box 10. This user terminal 30 can be connected to a network. The user terminal 30 is used when registering the receiving box 10 by accessing the management server 20. Furthermore, the user terminal 30 is used when purchasing a product by accessing the seller server 40.

The management server 20 is a computer system that supports delivery. The management server 20 includes a control unit 21, an installation information storage unit 22, and a request information storage unit 23.
The control unit 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing described later (processing including a registration processing stage, an address confirmation stage, a request reception stage, a delivery support stage, a billing management stage, etc.). Then, by executing the delivery support program for this purpose, the control unit 21 functions as a registration processing unit 211, an address confirmation unit 212, a request reception unit 213, a delivery support unit 214, a charging management unit 215, and the like.

The registration processing unit 211 executes a registration process for the newly installed receiving box 10.
The address confirmation unit 212 executes confirmation processing of the address of the delivery destination where the receiving box 10 is installed.
The request reception unit 213 executes processing for receiving a delivery request for the receiving box 10.
The delivery support unit 214 executes processing for supporting delivery when the delivery item is stored in the receiving box 10.

  The billing management unit 215 performs billing processing for the usage fee of the receiving box 10 for a delivery company that has delivered using the receiving box 10. The billing management unit 215 holds fee calculation information for calculating a usage fee according to the use of the receiving box 10.

  As shown in FIG. 3A, the installation information storage unit 22 records an installation management record 220 regarding the receiving box 10 installed in the user's home. The installation management record 220 is recorded when installation registration of a new receiving box 10 is performed. In the installation management record 220, data related to a receiving box code, an installation location, an installer, and a size are recorded.

In the receiving box code data area, data relating to an identifier for specifying each receiving box 10 is recorded.
In the installation location data area, data relating to an address (including a zip code) where the receiving box 10 is installed is recorded.

In the installer data area, data relating to the name of the user who installed the receiving box 10 is recorded.
In the size data area, data relating to the size (accommodable amount) of the installed receiving box 10 is recorded as structure information of the receiving box 10. Based on this structure information, it can be determined whether or not the delivery item can be stored in the receiving box 10.

  As shown in FIG. 3B, a request management record 230 related to a delivery request is recorded in the request information storage unit 23. This request management record 230 is recorded when a delivery request is accepted. In the request management record 230, data relating to a tracking code, a reception date / time, a shipper, a delivery destination, a delivery company, a collection date / time, and a delivery completion date / time are recorded.

Data relating to an identifier for specifying each delivery is recorded in the tracking code data area.
In the reception date and time data area, data related to the date and time when the delivery request is received is recorded.

  In the shipper data area, shipper information for specifying the shipper who made the delivery request is recorded. In this embodiment, the merchandise seller is the shipper. In this shipper data area, an identifier for identifying the shipper (shipper identifier) and data relating to contact information are recorded. The management server 20 may be provided with a customer information storage unit, and the customer information storage unit may store a sender identifier and a contact address in association with each other. In this case, the contact information associated with the shipper identifier is specified from the customer information storage unit.

  Data for specifying a delivery destination is recorded in the delivery destination data area. In this data area, the store name, store code, etc. of the convenience store that receives the address and delivery are recorded. Furthermore, when delivering to the receiving box 10, the data regarding the receiving box code for specifying the receiving box 10 of a delivery destination are recorded.

In the delivery company data area, data relating to an identifier for specifying the delivery company that performs the delivery is recorded.
In the collection date / time data area, data related to the date and time when collection is performed for this delivery request is recorded.
In the delivery completion date and time data area, data related to the date and time when delivery for this delivery request is completed is recorded.

  The seller server 40 is a computer system (shipping requester terminal) of a seller (here, a mail order business operator) who sells products. The seller server 40 includes a control unit 41, a product information storage unit 42, a customer information storage unit 43, and an order information storage unit 44.

  The control unit 41 performs management of products to be sold, management of customers, and management of transactions with customers. The control unit 41 holds delivery fee calculation information for calculating a delivery fee. In the present embodiment, a box-use delivery fee when the delivery destination is the receiving box 10 and a normal delivery fee when the delivery destination is an address other than the receiving box 10 are recorded. The box-use delivery fee is set to be lower than the normal delivery fee in consideration of a burden such as carry-back in the absence of delivery.

  The merchandise information storage unit 42 records merchandise management records for merchandise sold to customers. This merchandise management record is recorded when the merchandise information of merchandise to be sold is registered in the mail order business. The merchandise management record includes data relating to a merchandise code, a merchandise name, a price, and merchandise content.

In the product code data area, data relating to an identifier for specifying a product sold by a mail order company is recorded.
In the product name data area and the price data area, data related to the product name and price are recorded.
In the product content data area, data relating to the size, weight, etc. of the product is recorded.

  The customer information storage unit 43 stores customer management records for customers who make transactions. The customer management record is recorded when a customer is registered. In the customer management record, data relating to a customer ID, name, address, contact address, and delivery destination candidate is recorded.

Data relating to an identifier for identifying each customer is recorded in the customer ID data area.
In the name and address data area, data related to the name and address of the customer are recorded.

In the contact data area, data related to the customer's contact information (telephone number, e-mail address, etc.) is recorded.
In the delivery destination candidate data area, data related to delivery destination candidates for the purchased product of the customer is recorded. As the delivery destination candidate, an address designated by the customer, a store used for receiving a convenience store, a receiving box code, or the like is used.

  The order information storage unit 44 stores an order management record for a transaction with a customer. This order management record is recorded when an order for merchandise sales is received. In the order management record, data relating to a transaction code, customer code, order date and time, delivery destination, order contents, delivery agent, and tracking code are recorded.

Data relating to an identifier for specifying each transaction is recorded in the transaction code data area.
In the customer code data area, data relating to an identifier for identifying a customer who has made a transaction is recorded.

In the order date / time data area, data relating to the date and time when the transaction was performed is recorded.
Data relating to the delivery destination of the transaction product is recorded in the delivery destination data area.

Data for specifying the product and quantity is recorded in the order detail data area.
In the delivery company data area, data relating to an identifier for specifying a delivery company delivering this product is recorded.
In the tracking code data area, data relating to an identifier for specifying delivery of the product is recorded.

  The delivery person terminal 50 is a computer terminal of a delivery person belonging to the delivery company. The delivery staff terminal 50 includes a display, a code reader, and a printing unit. The display is used to output the result of collating the receiving box code. The code reader is used to read a tracking code image printed on a delivery label affixed to a delivery item. The printing unit is used for printing various slips.

Next, a processing procedure for performing delivery support processing using the system configured as described above will be described with reference to FIGS.
(Installation process of the receiving box 10)
A process when the user installs the receiving box 10 will be described with reference to FIG. Inside the door 11 of the receiving box 10, a code image 13 of the receiving box code is affixed.

  First, the user terminal 30 executes an access process (step S1-1). Specifically, when the user installs the receiving box 10 at home, the user accesses the management server 20 using the user terminal 30.

  In this case, the control unit 21 of the management server 20 executes a registration screen transmission process (step S1-2). Specifically, the registration processing unit 211 of the control unit 21 transmits a registration screen to the user terminal 30. This registration screen is provided with input fields such as a receiving box code, a size, an address, and a name of an installer (user) of the receiving box 10 installed.

  Next, the user terminal 30 executes a receiving box application process (step S1-3). Specifically, the user terminal 30 outputs the registration screen acquired from the management server 20 to the display. And a user performs input to each input column of a registration screen. When the input is completed, the user terminal 30 transmits registration application data to the management server 20. This registration application data includes data related to the receiving box code, size, address, and installer name.

  Next, the control part 21 of the management server 20 performs a receiving box registration process (step S1-4). Specifically, the registration processing unit 211 of the control unit 21 generates an installation management record 220 that records the box code, size, address, and installer name included in the registration application data, and registers them in the installation information storage unit 22. To do.

(Transaction processing)
Next, with reference to FIG. 4, transaction processing in the case of purchasing a product in the seller server 40 will be described.

  Here, the user terminal 30 executes an access process (step S2-1). Specifically, when a user (customer) purchases a product, the user terminal 30 is used to access the seller server 40. In this case, the control unit 41 of the seller server 40 performs user authentication of the accessor and specifies the customer code.

  Next, the control part 41 of the seller server 40 performs an order receiving process (step S2-2). Specifically, the control unit 41 generates a product list screen recorded in the product information storage unit 42 and outputs it to the display of the user terminal 30. Then, the seller server 40 identifies the product selected on the product list screen.

  Next, the control unit 41 of the seller server 40 executes a delivery destination information acquisition process (step S2-3). Specifically, the control unit 41 outputs a delivery destination setting screen to the display of the user terminal 30. This delivery destination setting screen is provided with a delivery destination candidate selection field and a new delivery destination setting field recorded in the customer management record of the customer information storage unit 43 for the user authenticated by the user. And the control part 41 specifies the delivery destination information designated on the delivery destination setting screen.

  Next, the control part 41 of the seller server 40 performs the determination process about whether it is use of a receiving box (step S2-4). Specifically, the control unit 41 determines whether or not the receiving box 10 is used based on the delivery destination information specified on the delivery destination setting screen. Here, if a receiving box code is specified in the shipping destination candidate selection field or the new shipping destination setting field on the delivery destination setting screen, it is determined that the receiving box is used.

  Here, when it is determined that the receiving box is used (“YES” in step S2-4), the seller server 40 executes a receiving box confirmation request process (step S2-5). Specifically, the seller server 40 transmits a receipt confirmation request to the management server 20. The receipt box confirmation request includes data relating to the receipt box code, address, and name acquired from the user terminal 30.

  The control unit 21 of the management server 20 that has received the receiving box confirmation request executes a receiving box installation information acquisition process (step S2-6). Specifically, the address confirmation unit 212 of the control unit 21 searches the installation information storage unit 22 for the installation management record 220 in which the receiving box code of the receiving box confirmation request is recorded. If the installation management record 220 can be extracted, the address confirmation unit 212 acquires the address and name recorded in the installation management record 220.

  Next, the control part 21 of the management server 20 performs collation processing of receiving box installation information (step S2-7). Specifically, the address confirmation unit 212 of the control unit 21 collates the address and name recorded in the extracted installation management record 220 with the address and name of the reception box confirmation request.

  Next, the control unit 21 of the management server 20 executes a confirmation result notification process (step S2-8). Specifically, the address confirmation unit 212 of the control unit 21 transmits a confirmation result notification to the seller server 40. This confirmation result notification includes data related to the verification result. Specifically, when the content recorded in the installation management record 220 matches the content included in the reception box confirmation request, a verification result indicating completion of verification is included. On the other hand, if the installation management record 220 cannot be extracted, or if the contents recorded in the installation management record 220 and the contents included in the receiving box confirmation request do not match, a matching result indicating that matching cannot be performed is included.

  Next, the control part 41 of the seller server 40 performs the determination process about whether a box delivery is possible (step S2-9). Specifically, the control unit 41 determines that the box delivery is possible when a collation result indicating collation completion is acquired. On the other hand, when a collation result indicating that collation is not possible is obtained, it is determined that the box delivery is not possible.

If it is determined that the box delivery is not possible (“NO” in step S2-9), the control unit 41 of the seller server 40 returns to the delivery destination information acquisition process (step S2-3).
On the other hand, when it is determined that the box can be delivered (“YES” in step S2-9), the control unit 41 of the seller server 40 executes a determination process as to whether or not it is the first time (step S2-10). Specifically, the control unit 41 confirms whether or not the receiving box code is recorded in the customer management record of the customer information storage unit 43. If no customer box record is recorded in the customer management record, it is determined as the first time.

  When it is determined to be the first time (in the case of “YES” in step S2-10), the control unit 41 of the seller server 40 executes a receiving box registration process (step S2-11). Specifically, the control unit 41 records the receiving box code in the customer management record in the customer information storage unit 43.

  On the other hand, when it is determined that it is not the first time (in the case of “NO” in step S2-10), the control unit 41 of the seller server 40 skips the receiving box registration process (step S2-11).

  If it is determined that the box is not used (in the case of “NO” in step S2-4), the control unit 41 of the seller server 40 receives the box confirmation request process (step S2-5) to the box registration. The process (step S2-11) is skipped.

  Next, the control part 41 of the seller server 40 performs a payment process (step S2-12). Specifically, the control unit 41 calculates a delivery fee based on the delivery destination. Here, when the receiving box 10 is designated as a delivery destination, the receiving box use delivery charge is calculated in the delivery charge calculation information. On the other hand, when an address other than the receiving box 10 is designated as the delivery destination, the normal delivery fee is calculated in the delivery fee calculation information. Next, the merchant server 40 generates a payment screen for designating the total price including the ordered product price and the delivery fee and the payment method, and outputs the payment screen to the display of the user terminal. When settlement approval is input on the settlement screen, the control unit 41 generates an order management record in which the order contents are recorded and records the order management record in the order information storage unit 44. And the control part 41 performs payment by the payment method designated by the customer.

When the ordered product is prepared and packed, the mail order business operator inputs completion of preparation for shipment to the seller server 40.
In this case, the control unit 41 of the seller server 40 executes a shipping instruction process (step S2-13). Specifically, the control unit 41 assigns a tracking code and records this tracking code in the order management record of the order information storage unit 44. And the control part 41 outputs the delivery label which printed sender information, recipient information, and a tracking code image. In the case of delivery using the receiving box 10, “use of receiving box” is printed on the delivery label. This delivery label is affixed to a delivery packaged with products.

  When the receiving box 10 is designated as the delivery destination, the control unit 41 of the seller server 40 executes delivery notification processing (step S2-14). Specifically, the seller server 40 transmits a delivery notification to the management server 20. This delivery notification includes data related to the receiving box code, tracking number, and the like.

  In this case, the control unit 21 of the management server 20 executes delivery carrier information recording processing (step S2-15). Specifically, the request reception unit 213 of the control unit 21 uses the installation information storage unit 22 to search for an installation management record 220 in which the receiving box code included in the delivery notification is recorded. If the installation management record 220 in which this box code is recorded cannot be extracted, the request reception unit 213 returns a message indicating that the box cannot be delivered to the seller server 40. In this case, the mail-order business operator changes the delivery to a delivery that does not use the receiving box 10 and replaces it with a delivery label on which “use of receiving box” is not printed. In addition, when performing the collation process (step S2-7) of receiving box installation information, you may make it skip confirmation of receiving box installation. When the installation management record 220 in which the receiving box code included in the delivery notification is recorded can be extracted, the request reception unit 213 determines the delivery company that performs delivery using the business operator decision rule. . And the data regarding a tracking code, a sender, a delivery destination, and a delivery company are recorded on the request management record 230 of the request information memory | storage part 23. FIG.

  The control unit 21 of the management server 20 executes a collection instruction process (step S2-16). Specifically, the request receiving unit 213 of the control unit 21 specifies the address of the installation location of the installation management record 220 in which the receiving box code is recorded. Then, a collection request is transmitted to the delivery company server of the delivery company. This collection request includes information on the collection destination (such as the seller's address).

  Then, a delivery person in charge of the delivery company collects the delivery items. In this case, the collection date and time is recorded in the request management record 230 of the request information storage unit 23. The delivery company then delivers the collected goods to the delivery address.

(Processing on delivery)
Next, the delivery process will be described with reference to FIG. This process is performed when delivering a “use of box” delivery to a delivery destination. In this case, the administrator of the management server notifies the delivery company of the unlock key in advance. In the pickup instruction process (step S2-16), an unlock key may be notified. Further, the delivery company notifies the delivery person in advance of the unlock key.

  First, the delivery person terminal 50 executes a tracking code reading process (step S3-1). Specifically, the delivery person causes the tracking code image printed on the delivery label to be read using the code reader of the delivery person terminal 50. In this case, the delivery staff terminal 50 decodes the tracking code image. Then, the delivery person in charge terminal 50 transmits a confirmation request to the management server 20. This confirmation request includes data relating to the tracking code read on the delivery label.

  Next, the delivery person in charge terminal 50 executes a receiving box code acquisition process (step S3-2). Specifically, the management server 20 that has received the confirmation request acquires the request management record 230 in which the tracking code is recorded from the request information storage unit 23. Then, the control unit 21 of the management server 20 returns the receiving box code recorded in the request management record 230 to the delivery person in charge terminal 50. Thereby, the delivery person in charge terminal 50 acquires a receiving box code.

  Next, the delivery person in charge terminal 50 executes a receiving box code reading process (step S3-3). Specifically, the delivery person in charge of the delivery company inputs the unlocking key notified in advance to the locking unit 12 and unlocks the receiving box 10. Then, using the delivery person terminal 50, the code image 13 of the receiving box label attached to the inside of the receiving box 10 is read. In this case, the delivery staff terminal 50 decodes the read code image 13.

  Next, the delivery person in charge terminal 50 performs the determination process about whether collation is completed (step S3-4). Specifically, the delivery person in charge terminal 50 compares the receiving box code acquired from the management server 20 with the receiving box code read from the receiving box label. If the two match, it is determined that the collation is complete.

  When it is determined that the receiving box codes do not match and the collation is not completed (“NO” in step S3-4), the delivery person terminal 50 executes an alarm process (step S3-5). Specifically, the delivery person in charge terminal 50 displays a message indicating that it is different from the delivery destination receiving box 10 on the display.

  On the other hand, when the receiving box codes match and it is determined that the collation is completed (in the case of “YES” in step S3-4), the delivery person terminal 50 executes a delivery completion slip printing process (step S3-6). . Specifically, the delivery person in charge terminal 50 outputs a delivery completion slip by the printing unit. The person in charge of delivery stores the delivery completion slip in the postal box at the delivery destination.

  Next, the delivery person in charge terminal 50 executes delivery notification transmission processing (step S3-7). Specifically, the delivery person in charge terminal 50 transmits a delivery notification to the management server 20. This delivery notification includes data relating to the tracking code read from the delivery label affixed to the delivered item.

  The control unit 21 of the management server 20 that has received the delivery notification from the delivery staff terminal 50 executes a delivery completion notification transmission process (step S3-8). Specifically, the request reception unit 213 of the control unit 21 acquires a request management record 230 in which a tracking code for delivery notification is recorded from the request information storage unit 23. Then, the request reception unit 213 transmits a delivery completion notification to the contact information recorded in the requester data area. Further, the request reception unit 213 specifies the contact information of the seller server 40 based on the sender information recorded in the request information storage unit 23, and transmits a delivery completion notification to the seller server 40. In this case, the user terminal 30 and the seller server 40 receive the delivery completion notification.

  Next, the control unit 21 of the management server 20 executes a delivery status recording process (step S3-9). Specifically, the request reception unit 213 of the control unit 21 records the delivery completion date and time in the request management record 230 of the request information storage unit 23.

Then, the user who grasps the arrival of the delivery by the delivery completion notification opens the door 11 of the receiving box 10 using the unlock key and takes out the delivery.
Next, the control unit 21 of the management server 20 executes a billing process for the delivery company (step S3-10). Specifically, the billing management unit 215 of the control unit 21 uses the request information storage unit 23 to specify the delivery company recorded in the delivery person data area of the request management record 230. Then, the charge management unit 215 calculates the usage fee for the receiving box 10 using the fee calculation information based on the usage history recorded in the request management record 230. Then, the billing management unit 215 performs usage fee billing processing for each delivery company. Further, each delivery company charges the delivery fee to the mail order company in consideration of this usage fee.

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, the receiving box 10 that houses the delivery is installed at home. Thereby, the user can receive the delivery using the receiving box 10. Therefore, the delivery can be received even when absent. Furthermore, for the delivery company, it is possible to carry out efficient delivery by eliminating take-back.

  (2) In the present embodiment, the user terminal 30 executes a receiving box application process (step S1-3). And the control part 21 of the management server 20 performs a receiving box registration process (step S1-4). Thereby, delivery can be performed using the newly installed receiving box 10.

  (3) In this embodiment, the control part 41 of the seller server 40 performs a delivery destination information acquisition process (step S2-3) and a determination process (step S2-4) as to whether or not the box is used. When it is determined that the box is used (in the case of “YES” in step S2-4), the seller server 40 executes a confirmation request process for the box (step S2-5). In this case, the control unit 21 of the management server 20 executes a receiving box installation information acquisition process (step S2-6) to a confirmation result notification process (step S2-8). Thereby, the installation condition of the receiving box 10 can be confirmed.

  (4) In this embodiment, when it is determined that the box delivery is possible (“YES” in step S2-9), the control unit 41 of the seller server 40 executes a determination process as to whether or not it is the first time ( Step S2-10). When it is determined to be the first time (in the case of “YES” in step S2-10), the control unit 41 of the seller server 40 executes a receiving box registration process (step S2-11). Thereby, in the transaction with the seller server 40, the receiving box 10 can be used as a delivery destination candidate.

  (5) In this embodiment, the control part 41 of the seller server 40 performs a payment process (step S2-12). When the delivery destination is the receiving box 10, the receiving box use delivery fee is calculated, and when it is other than the receiving box 10, the normal use delivery fee is calculated. Thereby, different delivery charges can be set depending on whether the delivery destination is the receiving box 10 or a case other than the receiving box 10.

  (6) In this embodiment, the control part 41 of the seller server 40 performs a delivery notification process (step S2-14). And the control part 21 of the management server 20 performs the recording process of delivery company information (step S2-15). In this case, data relating to the tracking code, the sender, the delivery destination, and the delivery company is recorded in the request management record 230 of the request information storage unit 23. As a result, it is possible to specify the delivery carrier to be charged. Further, since the installation information storage unit 22 is used to search for the installation management record 220 in which the receiving box code included in the delivery notification is recorded, the status of the receiving box 10 can be confirmed at the time of shipping.

  (7) In the present embodiment, the delivery person in charge terminal 50 receives the receiving box code (step S3-2), the receiving box code reading process (step S3-3), and the determination process regarding whether or not collation is completed (step S3-4) is executed. Thereby, it is possible to confirm whether or not the delivery destination is correct at the time of delivery.

  (8) In this embodiment, when the receiving box codes match and it is determined that the collation is completed (in the case of “YES” in step S3-4), the delivery person terminal 50 executes the delivery completion slip printing process. (Step S3-6). Thereby, the work at the time of delivery can be reduced. The delivery officer terminal 50 executes delivery notification transmission processing (step S3-7), and the management server 20 executes delivery completion notification transmission processing (step S3-8). Thereby, the user and the shipper can grasp the arrival of the delivery.

Moreover, you may change the said embodiment as follows.
In the above embodiment, the delivery person in charge terminal 50 executes a receiving box code acquisition process (step S3-2). In this case, the receiving box code corresponding to the tracking code is acquired from the management server 20. Alternatively, a receiving box code may be printed on the delivery label. In this case, the delivery person in charge terminal 50 is used to decode the code image of the delivery label and obtain the receiving box code. Thereby, the delivery person in charge terminal 50 can acquire the receiving box code without accessing the management server 20.

  In the above embodiment, the merchant server 40 executes a receiving box confirmation request process (step S2-5). In this case, the control unit 21 of the management server 20 executes a collation process for the receiving box installation information (step S2-6). Here, the availability of the receiving box 10 may be determined based on the type and size of the delivery. In this case, the seller server 40 holds a determination list for specifying the types of products that can be delivered in the box. For example, in the determination list, information for specifying a predetermined amount or less and a product type that can be stored at room temperature is recorded.

The transaction process will be described with reference to FIG.
First, similarly to steps S2-2 to S2-4, the control unit 41 of the merchant server 40 receives an order processing (step S4-1), a delivery destination information acquisition process (step S4-2), and whether or not to use a receiving box. The determination process about whether (step S4-3) is performed.

  When it is determined that the box is used (in the case of “YES” in step S4-3), the control unit 41 of the seller server 40 executes a determination process as to whether the product is a box-usable product (step S4-). 4). Specifically, the seller server 40 collates whether or not the type of the ordered product is included in the determination list. If it is included in the determination list, it is determined that the ordered product can be delivered to the receiving box 10.

  If it is determined that the product can be used in the receiving box (“YES” in step S4-4), the seller server 40 executes a receiving box confirmation request process in the same manner as in step S2-5 (step S4-5). ). The receipt box confirmation request includes data relating to the receipt box code, address, and name acquired from the user terminal 30. Further, the receipt confirmation request includes data relating to the size of the container for packing the product.

  Next, the control unit 21 of the management server 20 executes receiving box installation information and size acquisition processing (step S4-6). Specifically, the address confirmation unit 212 of the control unit 21 searches the installation information storage unit 22 for the installation management record 220 in which the receiving box code of the receiving box confirmation request is recorded. When the installation management record 220 can be extracted, the address confirmation unit 212 acquires the address, name, and size of the receiving box 10 recorded in the installation management record 220.

Next, the control part 21 of the management server 20 performs the collation process of receiving box installation information similarly to step S2-7 (step S4-7).
Next, the control unit 21 of the management server 20 executes size collation processing (step S4-8). Specifically, the address confirmation unit 212 of the control unit 21 collates the size recorded in the installation management record 220 with the size of the receiving box confirmation request.

  Next, the control unit 21 of the management server 20 executes a confirmation result notification process (step S4-9). Specifically, the address confirmation unit 212 of the control unit 21 transmits a confirmation result notification to the seller server 40. This confirmation result notification includes data related to the verification result. Specifically, when the content recorded in the installation management record 220 matches the content included in the reception box confirmation request, a verification result indicating completion of verification is included. On the other hand, when the installation management record 220 cannot be extracted, or when the contents recorded in the installation management record 220 and the contents included in the receiving box confirmation request do not match, a matching result indicating that matching cannot be performed is included. Furthermore, even if the size included in the receiving box confirmation request is larger than the size of the receiving box 10, a matching result indicating that matching cannot be performed is included.

Next, similarly to step S2-9, the control unit 41 of the seller server 40 executes a determination process as to whether or not the box can be delivered (step S4-10).
Then, similarly to Steps S2-10 to S2-16, the determination processing for the first time is executed (Steps S4-11 to S4-17). If it is determined that the box is not used (in the case of “NO” in step S4-4), the control unit 41 of the seller server 40 receives the box confirmation request process (step S4-5) to the box registration. The process (step S2-12) is skipped.

Thereby, in the seller server 40, the availability of the receiving box 10 can be determined according to the kind of goods. For example, storage in the receiving box 10 can be suppressed for expensive products or products that require refrigeration. The determination list may be held in the management server 20, and product type information may be acquired from the seller server 40 to determine whether the receiving box 10 can be used.
Further, through the size verification process (step S4-8), the management server 20 can determine whether or not the receiving box 10 can be used based on the size of the packing container.

  In the above embodiment, when delivering a delivery item to a delivery destination, processing at the time of delivery is performed. In addition to this, pre-delivery processing for confirming the delivery status may be performed before delivery. In this case, a scheduled delivery date data area is provided in the request management record 230 of the request information storage unit 23. In this scheduled delivery date data area, the scheduled delivery date is recorded at the delivery base when the delivery preparation is completed.

The pre-delivery process will be described with reference to FIG.
(Pre-delivery processing)
Here, first, the delivery person in charge terminal 50 executes a delivery code tracking code reading process (step S5-1). Specifically, the delivery person uses the delivery person terminal 50 to read the tracking code of the delivery label affixed to the delivery item before delivery.

  Next, the delivery person in charge terminal 50 executes a confirmation request process for the usage status of the receiving box (step S5-2). Specifically, the delivery person in charge terminal 50 transmits a confirmation request for the usage status of the receiving box to the management server 20. This confirmation request includes data relating to the tracking code read from the delivery label.

  Next, the control unit 21 of the management server 20 executes delivery schedule acquisition processing (step S5-3). Specifically, the delivery support unit 214 of the control unit 21 extracts from the request information storage unit 23 the request management record 230 in which the tracking code of the confirmation request for the use status of the receiving box is recorded. The delivery support unit 214 records the scheduled delivery date (date of the current day) in the scheduled delivery date data area of the request management record 230.

  Next, the control part 21 of the management server 20 performs the acquisition process of the use condition of a receiving box (step S5-4). Specifically, the delivery support unit 214 of the control unit 21 specifies the receiving box code recorded in the request management record 230 extracted from the request information storage unit 23. Then, the delivery support unit 214 searches the request information storage unit 23 for all the request management records 230 in which the box code is recorded and the current day is recorded as the scheduled delivery date. Further, the delivery support unit 214 confirms whether or not the delivery completion date is recorded in the extracted request management record 230. In this case, the delivery support unit 214 calculates the planned delivery number based on the number of records in the extracted request management record 230. Furthermore, the delivery support unit 214 specifies the number of delivered items based on the number of records in the request management record 230 in which the delivery completion date / time is recorded.

  Next, the control unit 21 of the management server 20 executes a confirmation result transmission process (step S5-5). Specifically, the delivery support unit 214 of the control unit 21 transmits a confirmation result to the delivery person terminal 50. This confirmation result includes information regarding the number of scheduled deliveries and the number of delivered items.

  Next, the delivery person in charge terminal 50 executes a confirmation result output process (step S5-6). Specifically, the delivery person in charge terminal 50 outputs the confirmation result acquired from the management server 20 to the display.

Then, the delivery company delivers the delivery to the receiving box 10 in consideration of the confirmation result.
Also in this case, a delivery process is performed when delivering the delivery.
Here, the delivery person in charge terminal 50 executes the delivery notification transmission process in the same manner as in step S3-7 (step S6-1). Then, similarly to steps S3-8 to S3-10, the control unit 21 of the management server 20 transmits a delivery completion notification transmission process (step S6-2), a delivery status recording process (step S6-3), and a delivery business. A billing process for the user (step S6-4) is executed.
Thereby, the person in charge of delivery can perform delivery in consideration of the use situation of the receiving box 10.

  In the above embodiment, the receiving box 10 is used when delivering a delivery. In addition to this, the receiving box 10 may be used when a delivery item is collected. In this case, a request management record 230 relating to collection is recorded in the request information storage unit 23. And the data regarding the receiving box code | cord | chord of the receiving box 10 which accommodates the delivery to collect is recorded on a sender data area.

The collection process will be described with reference to FIG.
(Collection processing)
First, the user terminal 30 executes a delivery company designation process (step S7-1). Specifically, a user who desires collection accesses the management server 20 using the user terminal 30. In this case, the control unit 21 of the management server 20 outputs a collection screen to the user terminal 30. This collection screen includes a list of delivery companies that can collect goods. Further, the collection screen is provided with an input field for a tracking code printed on a delivery label affixed to a delivery item to be collected and a box code of the box 10. Then, the user selects a desired delivery company in the delivery company list.

  Next, the user terminal 30 executes a collection request process (step S7-2). Specifically, the user terminal 30 transmits a collection request to the management server 20 when the input completion is detected on the collection screen. This collection request includes the tracking code input on the collection screen, the receiving box code, and the specific information of the selected delivery company. Then, the user stores the delivery in the receiving box 10.

  The control unit 21 of the management server 20 that has received the collection request executes a collection registration process (step S7-3). Specifically, the delivery support unit 214 of the control unit 21 generates a request management record 230 that records the tracking code, the receiving box code, and the delivery company, and records the request management record 230 in the request information storage unit 23. Further, the delivery support unit 214 records the reception date in the request management record 230.

  Next, the control unit 21 of the management server 20 executes a collection instruction process for the delivery company (step S7-4). Specifically, the delivery support unit 214 of the control unit 21 transmits the collection request to the delivery company server of the delivery company included in the collection request. This collection request includes data on the address where the receiving box 10 is installed, the name of the user, and the tracking code.

  In this case, the delivery company server transmits a collection instruction to the delivery person terminal 50. This pickup instruction includes data on the address where the receiving box 10 is installed, the user's name, and the tracking code. The delivery person visits the collection destination based on the collection instruction output to the delivery person terminal 50.

Next, the delivery person in charge terminal 50 executes a receiving box code specifying process (step S8-1). Specifically, the delivery person in charge terminal 50 specifies a receiving box code included in the pickup instruction.
Next, the delivery person in charge terminal 50 executes a receiving box code reading process (step S8-2). Specifically, the person in charge of the delivery company unlocks the receiving box 10 and reads the code image 13 attached to the inside of the receiving box 10 using the code reader of the person in charge of delivery 50. In this case, the delivery person in charge terminal 50 decodes the code image 13 and acquires a receiving box code.

  Next, the delivery person terminal 50 executes a determination process as to whether or not collation is complete (step S8-3). Specifically, the delivery person in charge terminal 50 compares the decrypted box receiving code with the box receiving code included in the pickup instruction. When the decrypted receiving box code matches the receiving box code included in the pickup instruction, it is determined that the collation is complete.

  When it is determined that the collation cannot be performed (in the case of “NO” in Step S8-3), the delivery person terminal 50 executes an alarm process (Step S8-4). Specifically, the delivery person terminal 50 outputs an error message indicating that the collection target receiving box 10 is wrong.

  On the other hand, when it is determined that the collation is completed (in the case of “YES” in step S8-3), the delivery person terminal 50 executes the collection slip printing process (step S8-5). Specifically, the delivery person in charge terminal 50 outputs a collection slip. This collection slip is printed with a tracking code and information about the name of the delivery company that collected the goods.

  Next, the delivery person in charge terminal 50 executes a collection notification transmission process (step S8-6). Specifically, the delivery person in charge terminal 50 transmits a collection notice to the management server 20. This pickup notice includes data relating to the tracking code.

  Next, the delivery person in charge terminal 50 executes a collection completion notification transmission process (step S8-7). Specifically, the delivery support unit 214 of the control unit 21 transmits a collection completion notification to the user terminal 30.

  Next, the control unit 21 of the management server 20 executes a collection status recording process (step S8-8). Specifically, the delivery support unit 214 of the control unit 21 extracts the request management record 230 in which the tracking code is recorded from the request information storage unit 23, and records the collection date and time.

  -In the said embodiment, the case where the locking part 12 was unlockable by the unlocking key specific to each receiving box 10 and the unlocking key allocated for every delivery company was assumed. The unlocking method is not limited to this. For example, individual unlocking keys and master keys may be used, such as a locking mechanism (TSA lock (registered trademark)) approved by the Transportation Security Agency of the US Department of Homeland Security. In this case, a master key is assigned to the delivery company. Moreover, you may make it use the card | curd which recorded the unlocking key. In this case, a card reader is provided in the locking part 12. Thereby, the operation burden of unlocking can be reduced.

  Further, the locking unit 12 may be provided with a communication function with the user terminal 30 and the delivery person terminal 50. In this case, the locking unit 12 acquires the unlock key from the user terminal 30 or the delivery person terminal 50. In this case, the installation information storage unit 22 stores an unlock key when the user unlocks the receiving box 10.

  Further, the management server 20 may receive an unlock notification from the user terminal 30 or the delivery person terminal 50 when unlocking. Here, the management server 20 may execute the management process of the usage status of the receiving box 10 based on the unlock notification. In this case, data related to the user's unlock key and storage status (storage number) is recorded in the installation management record 220 of the installation information storage unit 22. Further, data related to the delivery date and time of delivery is recorded in the request management record 230 of the request information storage unit 23.

(Management processing of the usage status of the receiving box 10)
The management process of the usage status of the receiving box 10 will be described with reference to FIG. Here, it is assumed that the receiving box 10 is used for delivery (FIG. 5) and collection (FIG. 8) of deliverables.

  First, the user terminal 30 and the delivery staff terminal 50 execute an unlocking process (step S9-1). Specifically, the locking unit 12 of the receiving box 10 acquires the unlock key from the user terminal 30 or the delivery person terminal 50. And the door 11 is unlocked with the acquired unlocking key. Then, the user and the person in charge of delivery store and take out the delivery items.

  In this case, the user terminal 30 and the delivery person in charge terminal 50 execute the unlock notification process (step S9-2). Specifically, the user terminal 30 and the delivery officer terminal 50 transmit an unlock notification to the management server 20. The unlock notification includes data related to the receiving box code and the unlock key.

  The control unit 21 of the management server 20 that has received the unlock notification executes unlocker information acquisition processing (step S9-3). Specifically, the delivery support unit 214 of the control unit 21 acquires the unlock key included in the unlock notification.

  Next, the control part 21 of the management server 20 performs the determination process about whether it is the user (installer) of the receiving box 10 (step S9-4). Specifically, the delivery support unit 214 of the control unit 21 acquires from the installation information storage unit 22 the installation management record 220 in which the receiving box code included in the unlock notification is recorded. When the unlock key recorded in the installation management record 220 matches the unlock key included in the unlock notification, it is determined that the user is a user. On the other hand, when the unlock keys are different, it is determined that the delivery company is an unlocker based on the unlock key included in the unlock notification.

  When it is determined that the user of the receiving box 10 is an unlocker (in the case of “YES” in step S9-4), the control unit 21 of the management server 20 executes a determination process as to whether or not the delivery item has been stored. (Step S9-5). Specifically, the delivery support unit 214 of the control unit 21 searches the request information storage unit 23 for a request management record 230 in which the extraction date / time is not recorded. When the request management record 230 in which the extraction date / time is not recorded is extracted, it is determined that the delivery has been stored.

  When it is determined that the delivery has been stored (in the case of “YES” in step S9-5), the control unit 21 of the management server 20 executes a delivery takeout recording process (step S9-6). Specifically, the delivery support unit 214 of the control unit 21 records the extraction date and time in the request management record 230. Further, the delivery support unit 214 resets the storage status of the installation management record 220 in which the receiving box code is recorded.

  On the other hand, if it is determined that the delivery has not been stored (“NO” in step S9-5), the control unit 21 of the management server 20 skips the delivery takeout recording process (step S9-6).

  Next, the control part 21 of the management server 20 performs the determination process about whether there exists a collection schedule (step S9-7). Specifically, the delivery support unit 214 of the control unit 21 searches the request information storage unit 23 for the request management record 230 in which the collection request reception date and time is recorded and the collection date and time is not recorded. When the collection date and time of receipt is recorded and the request management record 230 with no collection date and time is extracted, it is determined that there is a collection schedule.

  When it is determined that there is a collection schedule (in the case of “YES” in step S9-7), the control unit 21 of the management server 20 executes a storage record process for the delivery item (step S9-8). Specifically, the delivery support unit 214 of the control unit 21 records the storage number as the storage status of the installation management record 220 in which the receiving box code is recorded.

  On the other hand, when it is determined that there is no scheduled collection (in the case of “NO” in step S9-7), the control unit 21 of the management server 20 skips the storage record processing (step S9-8) of the delivery item.

  When it is determined that the delivery person is the unlocker (“NO” in step S9-4), the control unit 21 of the management server 20 has either a collection schedule or a delivery schedule. The determination process is performed (step S9-9). Specifically, the delivery support unit 214 of the control unit 21 records, in the request information storage unit 23, a request management record in which the date of the day is recorded as the scheduled delivery date and the delivery completion date / time is not recorded. 230 is searched. Further, the request information storage unit 23 searches the delivery management company for a request management record 230 in which the date of the current day is recorded as the collection reception date and the collection date is not recorded. If any request management record 230 is detected, it is determined that there is a request.

  If it is determined that there is no schedule for collection or delivery (“NO” in step S9-9), the control unit 21 of the management server 20 executes an alarm recording process (step S9-10). Specifically, the delivery support unit 214 of the control unit 21 records an alarm as the storage status of the installation management record 220 in which the receiving box code is recorded. Further, the delivery support unit 214 outputs an alarm to the administrator terminal of the management server 20. In this case, the administrator of the management server 20 prompts the delivery company that unlocked the receiving box 10 to confirm.

  When it is determined that there is at least one schedule of collection or delivery (when “YES” in step S9-9), the control unit 21 of the management server 20 performs a determination process on whether or not there is a collection schedule. Execute (Step S9-11). Specifically, the delivery support unit 214 of the control unit 21 searches the request information storage unit 23 for a request management record 230 in which the collection date / time is not recorded. If the request management record 230 can be extracted, it is determined that there is a collection schedule.

  When it is determined that there is a collection schedule (in the case of “YES” in step S9-11), the control unit 21 of the management server 20 executes a collection recording process for the delivery (step S9-12). Specifically, the delivery support unit 214 of the control unit 21 records the collection date and time in the request management record 230. Further, the delivery support unit 214 subtracts the number of collections from the stored number in the storage state of the installation management record 220 in which the receiving box code is recorded.

  On the other hand, when it is determined that there is no scheduled collection (in the case of “NO” in step S9-11), the control unit 21 of the management server 20 skips the collection recording process (step S9-12) of the delivery item.

  Next, the control part 21 of the management server 20 performs the determination process about whether there is a delivery schedule (step S9-13). Specifically, the delivery support unit 214 of the control unit 21 searches the request management record 230 in the request information storage unit 23 where the scheduled delivery date is recorded and the delivery date and time is not recorded.

When it is determined that there is a delivery schedule (“YES” in step S9-13), the control unit 21 of the management server 20 executes a delivery storage record process (step S9-14). Specifically, the delivery support unit 214 of the control unit 21 records the delivery completion date and time in the request management record 230. Furthermore, the delivery support unit 214 adds the planned delivery number to the number of stored items in the storage status of the installation management record 220 in which the receiving box code is recorded.
On the other hand, if it is determined that there is no delivery plan (“NO” in step S9-13), the control unit 21 of the management server 20 skips the delivery storage record process (step S9-14).

Thereby, the storage state of the receiving box 10 can be managed based on the unlock notification from the user terminal 30 or the delivery person terminal 50.
In addition, the determination process (step S9-4) about whether it is a user of the receiving box 10 is not limited to the case where an unlocking key is used. For example, in the unlock notification process (step S9-2), it is possible to include information that can identify the user terminal 30 and the delivery person terminal 50.

  In the above embodiment, it is assumed that the locking unit 12 can be unlocked using the unlocking key assigned to each delivery company. Here, an unlock key (one-time key) that can be used only once may be provided to the delivery person in charge terminal 50.

  In this case, as shown in FIG. 10A, when a delivery or collection request is received, the unlock key of the receiving box 10 is transmitted to the delivery person terminal 50 that performs delivery or collection. . Further, an unlock key used by the delivery company is also transmitted to the receiving box 10. In this case, the locking part 12 of the receiving box 10 temporarily stores the unlocking key.

As shown in FIG. 10B, the receiving box 10 that has acquired the unlock key from the delivery person terminal 50 checks whether or not it matches the unlock key acquired in advance from the management server 20.
As shown in FIG.10 (c), when it corresponds, the locking part 12 performs unlocking. Then, the locking unit 12 deletes the used unlocking key.

Thereby, security can be improved by distributing the unlock key that can be used only once.
Note that the management method of the unlock key that can be used only once is not limited to the deletion of the unlock key used in the locking unit 12. For example, one time unlocking may be realized by deleting from the delivery person terminal 50 at the time of unlocking.

Further, the unlocking function of the delivery person terminal 50 may be validated at the time of collection or delivery.
This process will be described with reference to FIG.

First, the control unit 21 of the management server 20 executes a collection instruction / delivery instruction process (step S10-1). Specifically, the delivery support unit 214 of the control unit 21 transmits a collection instruction and a delivery instruction in the receiving box 10 to the delivery person terminal 50. This collection instruction or delivery instruction includes authentication information.
In this case, the delivery person in charge terminal 50 executes an instruction output process (step S10-2). Specifically, the delivery person in charge terminal 50 outputs a collection instruction and a delivery instruction on the display. The person in charge of delivery visits the installation location of the receiving box 10 based on this instruction.

  Next, the delivery person in charge terminal 50 executes the unlock request process (step S10-3). Specifically, when the person in charge arrives at the installation location of the target receiving box 10, the person in charge transmits an unlocking request to the management server 20 using the delivery person in charge terminal 50. This unlocking request includes authentication information for a collection instruction and a delivery instruction.

  Next, the control part 21 of the management server 20 performs an unlocking confirmation process (step S10-4). Specifically, the delivery support unit 214 of the control unit 21 confirms whether the unlocking request includes authentication information included in the collection instruction or the delivery instruction.

When unlocking confirmation has been made, the control unit 21 of the management server 20 executes unlocking instruction processing (step S10-5). Specifically, the delivery support unit 214 of the control unit 21 transmits an unlocking instruction to the delivery person terminal 50.
The delivery person in charge terminal 50 that has received the unlocking instruction executes the unlocking function validation process (step S10-6). Specifically, the delivery person in charge terminal 50 enables transmission of the unlock key.

  And the delivery person in charge terminal 50 performs an unlocking process using an unlocking function (step S10-7). Specifically, the delivery person terminal 50 performs unlocking by transmitting an unlocking key to the locking unit 12 of the receiving box 10. In this case, the locking unit 12 returns an unlocking completion notification to the delivery person in charge terminal 50.

Next, the delivery person in charge terminal 50 executes the unlocking function invalidation process (step S10-8). Specifically, the delivery staff terminal 50 that has received the unlocking completion notification from the locking unit 12 of the receiving box 10 stops the unlocking function.
Thereby, security can be improved by the one-time unlocking function. In this case, it is not necessary to use the unlocking key only once, and the unlocking can be performed only once using a predetermined unlocking key assigned to the delivery company.

  In the above embodiment, the control unit 21 of the management server 20 executes a billing process for the delivery company (step S3-10). Here, the control unit 21 of the management server 20 may periodically perform a billing process for the delivery company at regular intervals. In this case, the usage fee is recorded in the fee calculation information according to the usage history (number of times of use). The control unit 21 of the management server 20 uses the request information storage unit 23 to extract a request management record 230 in which the delivery completion date and time for a predetermined period is recorded. Next, the billing management unit 215 uses the extracted request management record 230 to acquire the usage history (usage count) of the receiving box 10 for each delivery company recorded in the delivery person data area. Next, the charge management unit 215 calculates the usage fee for the receiving box 10 using the fee calculation information based on the acquired usage history. Then, the billing management unit 215 performs usage fee billing processing for each delivery company.

  In the above embodiment, the control unit 41 of the seller server 40 executes delivery destination information acquisition processing (step S2-3). If it is determined that the receiving box is used (“YES” in step S2-4), the merchant server 40 executes a receiving box confirmation request process (step S2-5). In this case, the receipt confirmation request includes data relating to the receipt box code, address, and name acquired from the user terminal 30. Here, the control unit 41 of the seller server 40 may acquire “only the box code” or “only the box code and name” as the delivery destination information. In this case, the reception box confirmation request includes “only the reception box code” and “only the reception box code and name”. Then, the control unit 21 of the management server 20 includes only the installation status of the receiving box 10 in the confirmation result notification in the installation information storage unit 22. In addition, “delivery box code only” or “receipt box code and name only” may be printed as recipient information on the delivery label output in the shipping instruction process (step S2-13). In this case, at the time of cargo collection, the installation location and the installer are acquired from the installation information storage unit 22 and printed delivery labels are output. As a result, delivery can be performed without the sender knowing the address of the recipient.

In the above embodiment, a receiving box label on which the code image 13 is printed is attached inside the receiving box 10. In this case, the case where it is affixed inside the door 11 is assumed. The place where the receiving box label is affixed is not limited to the inside of the door 11, but may be any position that can be viewed when the receiving box 10 is opened.
Moreover, you may make it affix a receiving box label after installation of the receiving box 10. FIG. For example, in the receiving box registration process (step S1-4), a receiving box code may be allocated, a receiving box label on which the code image 13 is printed may be printed and sent to the installer. In this case, the registration application data in the inbox application process (step S1-3) includes data on the size, address, and installer name. Then, the installer who has acquired the receiving box label attaches the receiving box label to a predetermined position. In addition, the person in charge of the business operator who manages the management server 20 (for example, the person in charge of the area who performs the collection and delivery work) may visit the address of the installer of the receiving box 10 and attach the receiving box label.

  In the above embodiment, the control unit 41 of the seller server 40 executes an order receiving process (step S2-2) and a delivery destination information acquisition process (step S2-3). If it is determined that the receiving box is used (“YES” in step S2-4), the merchant server 40 executes a receiving box confirmation request process (step S2-5). Instead, for a customer who has been authenticated by the user, if a box receiving code is recorded as a delivery destination candidate in the customer management record of the customer information storage unit 43, the seller server 40 performs a box receiving confirmation request process. (Step S2-5) may be executed. Then, when it is determined that the box delivery is not possible based on the confirmation result notification acquired from the management server 20, the control unit 41 of the seller server 40 uses the delivery destination setting screen obtained by removing the receipt box from the delivery destination candidates. To the display of the user terminal 30. Therefore, the delivery destination can be efficiently specified using the delivery destination setting screen.

  In the above embodiment, the control unit 21 of the management server 20 executes a collation process for the receiving box installation information (step S2-7). In this case, the address and name recorded in the installation management record 220 are collated with the address and name of the receiving box confirmation request. Here, the verification target is not limited to an address and a name. For example, the installation information storage unit 22 may use the postal code recorded in association with the receiving box code and the postal code included in the receiving box confirmation request. Thereby, it is possible to perform collation by eliminating name mismatch due to family use and address mismatch due to fluctuating address information.

Next, the technical idea that can be grasped from the above embodiment and other examples will be described below.
(A) When the unlocking information of the receiving box is obtained from the delivery person in charge terminal, the storage of the delivery item in the receiving box is registered in the request information storage unit, and the receiving box is received from the user terminal of the receiving box. When the unlocking information is acquired, the removal of the package from the receiving box is registered in the request information storage unit, and when the request for the receiving box status is acquired from the delivery person terminal or the user terminal, the request is received. A delivery support system characterized by returning a receiving box status recorded in an information storage unit.
According to the invention described in (a), it is possible to grasp the usage status of the receiving box.

(B) The delivery support system according to (a), wherein a delivery company that uses the receiving box is recorded in the request information storage unit.
According to the invention described in (b), it is possible to grasp the usage history of the receiving box in the delivery company.

(C) When receiving a collection request from the user terminal and acquiring the unlocking information of the receiving box from the user terminal, registering the storage of the collection target object in the receiving box in the request information storage unit. The delivery support system according to (a) or (b).
According to the invention described in (c), it is possible to manage the use situation of the receiving box in the installation person of the receiving box.

(D) In any one of (a) to (c), when the collection request includes designation of a delivery company, the collection request is transmitted to the delivery company. The delivery support system described.
According to the invention described in (d), it is possible to specify a delivery company and request collection.

  (E) Any one of (a) to (d), wherein when receiving the unlocking information of the receiving box from the delivery person in charge terminal, the storage of the delivery object to be collected is reset. The delivery support system described in 1.

  According to the invention described in (e), it is possible to manage the usage status of the receiving box in the person in charge of delivery.

  DESCRIPTION OF SYMBOLS 10 ... Receipt box, 11 ... Door, 12 ... Locking part, 13 ... Code image, 20 ... Management server, 21 ... Control part, 211 ... Registration processing part, 212 ... Address confirmation part, 213 ... Request reception part, 214 ... Delivery Supporting unit, 215 ... charging management unit, 22 ... installation information storage unit, 23 ... request information storage unit, 30 ... user terminal, 40 ... merchant server, 41 ... control unit, 42 ... product information storage unit, 43 ... customer Information storage unit 44... Order information storage unit 50.

Claims (7)

A control unit connected to the delivery person terminal and the shipper terminal;
An installation information storage unit for storing information about a receiving box code for receiving a delivery item, an installation location, and an installer;
A delivery support system comprising a request information storage unit for storing delivery information of delivery items,
The control unit is
A first process of acquiring installation information regarding a receiving box code, an installation location, and an installer, and registering the installation information in the installation information storage unit;
When obtaining a receiving box code as delivery destination information from the shipper terminal, in the installation information storage unit, a second process of returning a confirmation result of the receiving box installation status to the shipper terminal;
A third process for storing delivery information in the request information storage unit when receiving a delivery request for delivery;
The delivery person terminal outputs a collation result obtained by collating the receiving box code specified based on the information printed on the delivery label of the delivery item and the receiving box code displayed in the receiving box at the delivery destination. And a fourth process of recording delivery completion information in the request information storage unit based on the collation result.   2. The delivery support system according to claim 1, wherein in the fourth process, the delivery person terminal outputs a delivery completion slip of the delivery item when the receiving box code can be collated. 3.   3. The delivery according to claim 1, wherein, in the fourth process, when delivery completion is recorded in the request information storage unit, a delivery completion notice is transmitted to an installer terminal of the receiving box. 4. Support system.   4. The delivery completion notification is transmitted to the delivery requester terminal of the delivery item when the delivery completion is recorded in the request information storage unit in the fourth process. 5. The delivery support system according to one item. The delivery support system according to any one of claims 1 to 4, wherein a use history of the receiving box is acquired based on delivery information recorded in the request information storage unit. In the installation information storage unit, structure information of the receiving box is recorded,
Obtaining delivery information along with the delivery destination information from the sender terminal,
Obtaining structural information of the receiving box associated with the receiving code of the delivery destination information;
The delivery support system according to any one of claims 1 to 5, wherein a result of collation between the structure information and the delivery information is returned to the sender terminal. A control unit connected to the delivery person terminal and the shipper terminal;
An installation information storage unit for storing information about a receiving box code for receiving a delivery item, an installation location, and an installer;
A method of supporting delivery using a delivery support system comprising a request information storage unit for storing delivery information of a delivery item,
The control unit is
A first process of acquiring installation information regarding a receiving box code, an installation location, and an installer, and registering the installation information in the installation information storage unit;
When obtaining a receiving box code as delivery destination information from the shipper terminal, in the installation information storage unit, a second process of returning a confirmation result of the receiving box installation status to the shipper terminal;
A third process for storing delivery information in the request information storage unit when receiving a delivery request for delivery;
The delivery person terminal outputs a collation result obtained by collating the receiving box code specified based on the information printed on the delivery label of the delivery item and the receiving box code displayed in the receiving box at the delivery destination. And a fourth process of recording delivery completion information in the request information storage unit based on the collation result.