Delivery method and allocation server

JP2023081822A5Active Publication Date: 2024-12-03NICE EZE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022112664
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2022-07-13
Publication Date
2024-12-03
Estimated Expiration
2041-12-01

AI Technical Summary

Technical Problem

The challenge of delivering packages to users who are often absent at the time of delivery, leading to increased costs and burdens for re-delivery and potential theft or leakage of personal information.

Method used

A package delivery method utilizing an allocation server that manages locker usage information for multiple delivery boxes in a housing complex, assigning packages to lockers and identifying them to a delivery management server before storage, ensuring packages are securely stored without the need for re-delivery.

Benefits of technology

Reduces delivery burdens and costs, enhances security by preventing theft, and allows users to collect packages at their convenience, improving operational efficiency and reducing environmental impact.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

To provide: a method for delivering a package to a resident of a multiple dwelling house with a home delivery box; and system and server for implementing the method.SOLUTION: A delivery method includes: acquiring, in an allocation server, locker use information relating to use states of a plurality of lockers provided in at least one home delivery box provided at a multiple dwelling house; allocating, on the allocation server, one of the plurality of lockers to at least one package to be delivered to a resident of the multiple dwelling house; and before storing the package in the allocated locker, transmitting a locker identifier for identifying the allocated locker, from the allocation server to a delivery management server managing the delivery of the package.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0004] , , , ,

[0005] , , , , ,

[0003] , ,

[0001] One embodiment of the present invention relates to a delivery method for delivering packages, a delivery system, and an allocation server for realizing this delivery method.

Background Art

[0002] When delivering a package to a user, the user may be absent. In this case, for example, the package is carried into a delivery box and the user is notified of the package's entry, so that the user can pick up the package from the delivery box at any time. This reduces the burden and cost for redelivery, and the user is also freed from time constraints as there is no need to wait for delivery. In addition, theft of packages and leakage of personal information can be prevented (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] One embodiment of the present invention aims to provide a novel method for delivering packages to a user, as well as a system and a server for realizing this method. Alternatively, one embodiment of the present invention aims to provide a method for delivering packages to residents of an apartment building equipped with a delivery box, as well as a system and a server for realizing this method.

Means for Solving the Problems

[0005] One embodiment of the present invention is a method for delivering packages. This delivery method includes, on an allocation server, acquiring locker usage information regarding the usage status of multiple lockers in at least one delivery box provided in an apartment building; assigning one of the multiple lockers to at least one package to be delivered to a resident of the apartment building on the allocation server; and, before placing the package in the assigned locker, transmitting a locker identifier from the allocation server to a delivery management server that manages the delivery of the package, in order to identify the assigned locker.

[0006] One embodiment of the present invention is an allocation server. This allocation server is configured to acquire locker usage information regarding the usage status of multiple lockers in at least one delivery box installed in an apartment building, to assign one of the multiple lockers to at least one package to be delivered to a resident of the apartment building, and to transmit a locker identifier to a delivery management server that manages the delivery of the package in order to identify the assigned locker before the package is placed in the assigned locker.

[0007] One embodiment of the present invention is a system for delivering packages. This system includes an allocation server connected to each other by a network, a delivery management server that manages the delivery of packages, and a delivery box installed in an apartment building. The allocation server is configured to acquire locker usage information regarding the usage status of multiple lockers in at least one delivery box installed in the apartment building, to assign one of the multiple lockers to at least one package to be delivered to a resident of the apartment building, and to transmit a locker identifier to the delivery management server that manages the delivery of packages in order to identify the assigned locker before placing the package in the assigned locker. [Brief explanation of the drawing]

[0008] [Figure 1]A conceptual diagram of a delivery method and delivery system according to an embodiment of the present invention. [Figure 2] An example of a floor plan of an apartment building in which the delivery method according to an embodiment of the present invention is used. [Figure 3] A schematic front view of a delivery box in a delivery system according to an embodiment of the present invention. [Figure 4] A schematic perspective view of a delivery box for a delivery system according to an embodiment of the present invention, and a container configured to be housed in the locker of the delivery box. [Figure 5] A schematic top view of a container configured to be housed in a locker of a delivery box in a delivery system according to an embodiment of the present invention. [Figure 6] A flowchart illustrating a delivery method according to an embodiment of the present invention. [Figure 7] A flowchart illustrating a delivery method according to an embodiment of the present invention. [Modes for carrying out the invention]

[0009] The embodiments of the present invention will be described below with reference to the drawings and other materials. However, the present invention can be implemented in various forms without departing from its spirit, and is not to be interpreted as being limited to the embodiments described below.

[0010] While drawings may schematically represent the width, thickness, shape, etc., of each part compared to the actual embodiment in order to clarify the explanation, these are merely examples and do not limit the interpretation of the present invention. In this specification and each figure, elements having the same function as those described in previously shown figures may be denoted by the same reference numeral to omit redundant explanations. This reference numeral is used to represent multiple identical or similar structures collectively, and when representing them individually, a hyphen and a natural number are added after the reference numeral. Furthermore, when indicating a part of a single structure, a lowercase alphabet letter may be added after the reference numeral.

[0011] <First Embodiment> This embodiment describes an overview of a delivery method according to one embodiment of the present invention, and the configuration and functions of a delivery system 100 for realizing this delivery method.

[0012] 1. Overview of shipping methods Figure 1(A) schematically shows a conceptual diagram of a delivery method using the delivery system 100. This delivery method is for delivering packages to apartment buildings and other multi-unit dwellings, and the packages are delivered to the residents of the multi-unit dwelling or their representatives (hereinafter collectively referred to as resident 102). There are no restrictions on the packages; they may include goods ordered by resident 102 themselves, or items sent to resident 102 by ordinary individuals. For example, packages may include goods or service results (hereinafter, goods and service results are collectively referred to as goods) ordered by resident 102 via the network 120 or communication lines such as telephone or fax, or goods ordered by resident 102 through face-to-face commercial transactions. Therefore, the goods included in packages are not limited to goods traded electronically, but also include goods traded at physical stores in all industries, such as supermarkets and department stores, liquor stores, dry cleaners, restaurants and cafes, fast food restaurants, bookstores, stationery stores, and drugstores that handle cosmetics and pharmaceuticals. Furthermore, the products may be rental items (rental shoes, rental costumes, rental bags, etc.) or samples (sample cosmetics, sample foods, etc.). Here, network 120 refers to a communication network such as the Internet or a wide area network, which mediates communication between various communication terminals and servers.

[0013] The sender 104, who is the entity sending the package, includes the trading partner (hereinafter referred to as the seller) of the goods being sent as a package, as well as the individual who sends the goods to the resident 102.

[0014] There are no restrictions on the entity (deliverer) responsible for delivering the goods; it may be the seller of the goods ordered by resident 102, or an individual who ships the goods to resident 102. In this case, the sender may also act as the delivery person. Alternatively, the delivery person may be a delivery company 106 that is commissioned by the sender to deliver the goods and performs delivery as one of its services.

[0015] Here, all packages to be delivered are left in a delivery box 130 installed in the apartment building. In other words, packages are directly stored in lockers in the delivery box 130 and are not delivered to each individual dwelling unit of the residents 102. Therefore, delivery personnel do not need to transport packages to each dwelling unit, nor do they need to check whether residents 102 are home or not. As a result, this delivery method places an extremely small burden on delivery personnel, significantly reduces the time and cost required for delivery, and allows for the effective use of delivery personnel's human resources.

[0016] In this delivery method, a delivery box 130 and its locker are assigned to each package before it is delivered. More specifically, before delivering a package, the delivery person receives a designation of a delivery box 130 and a suitable locker from a locker allocation service provider (hereinafter referred to as the allocation provider 108) via the network 120. This ensures that a locker for the package is secured in advance before delivery, thus eliminating the burden of redelivery. The allocation provider 108 also receives information regarding the usage status of each locker in the delivery box 130 (hereinafter referred to as locker usage information) via the network 120, either directly from the delivery box 130 or from the service provider managing the delivery box 130 (hereinafter referred to as the box management service provider 110), either periodically or as needed. This allows the allocation provider to respond promptly to the delivery person's request and quickly assign an appropriate locker.

[0017] In this delivery system, the allocation operator 108 may also serve as the delivery operator 106. That is, the allocation operator 108 may perform the allocation of lockers and also collect and deliver packages.

[0018] 2. Configuration and Functions of the Delivery System An example of the configuration of the delivery system 100 is shown in Fig. 1(B). The delivery system 100 includes an allocation server 109 managed by the allocation operator 108, at least one home delivery box 130, a shipping server 105 managed by the shipper 104 of the package, a delivery management server 107 managed by the delivery operator 106, etc. The at least one home delivery box 130 may include a plurality of home delivery boxes 130. The delivery system 100 may further include a box management server 111 managed by the box management operator 110. Also, the delivery system 100 may include a user terminal 103 which is a communication terminal managed by the resident 102. These components are connected so as to be able to communicate with each other via the network 120.

[0019] In the case where the allocation operator 108 also serves as the delivery operator 106, the allocation server 109 and the delivery management server 107 may be managed by the same operator, or may function as one integrated server.

[0020] 2-1. Allocation Server (1) Configuration The allocation server 109 is connected to the delivery boxes 130 via the network 120. A storage device (not shown) connected to the allocation server 109 stores a box identifier (box ID) to identify each delivery box 130, a user identifier (user ID) to identify a pre-registered resident 102, and a locker identifier (locker ID) to identify each of the multiple lockers that each delivery box 130 has. Each box ID may be associated with the name of the corresponding delivery box 130, the address and name of the apartment building where it is installed, and whether or not there are access restrictions (described later) and what those restrictions are, and these are stored in the storage device. The user ID may be associated with the name of the resident 102, the address and name of the apartment building where they live, their floor, their apartment number, an address for communicating with the user terminal 103, and a user score (described later), and these are also stored in the storage device. The locker ID may be associated with the number of the corresponding locker, its size (e.g., width, depth, height, volume, etc.), and its location in the delivery box 130, and these are also stored in the storage device. Furthermore, a delivery person identifier (delivery person ID) for identifying the delivery person may be stored in the storage device. The delivery person ID may be associated with the delivery person's name, address, delivery person score (described later), and communication address, and these are also stored in the storage device.

[0021] (2) Function A. Obtaining locker usage information The allocation server 109 is configured to receive signals containing locker usage information from each delivery box 130 periodically or upon request from the allocation server 109. The locker usage information includes whether or not there are packages in each locker. Alternatively, the allocation server 109 may be configured to receive signals containing locker usage information from the box management server 111. This allows the allocation server 109 to obtain the locker usage information.

[0022] I. Locker assignment The allocation server 109 is configured to receive a locker allocation request by receiving a signal containing the request sent from the shipping server 105 and / or the delivery management server 107. The locker allocation request includes the user ID of the resident 102 to whom the package is destined, and may also include the sender ID, delivery person ID, delivery person ID, desired delivery date and time for the package, package size (e.g., width, depth, height, volume, etc.), deadline for the resident 102 to receive the package, and the date and time for the delivery person to collect the package.

[0023] Upon receiving a locker allocation request, the allocation server 109 first identifies the delivery box 130 based on the resident's user ID. If there is only one delivery box 130 in the apartment building where resident 102 resides, that delivery box 130 is automatically identified. On the other hand, if there are multiple delivery boxes 130 in the apartment building, any of the delivery boxes 130 may be selected.

[0024] However, access restrictions may differ for multiple delivery boxes 130 installed in the same apartment building. For example, as shown in the schematic floor plan of the entrance of the apartment building (Figure 2), in an apartment building where the occupied area 142 and the common area 140 are separated by a door 146 that can only be entered by residents 102 and those who have been permitted by residents 102 in advance (hereinafter referred to as "specified persons"), and where there is also a door 144 that prohibits non-specified persons from entering during certain hours (restricted hours), two types of delivery boxes 130-1 and 130-2 may be provided. Since delivery box 130-1 is installed inside the door 144 (semi-common area 140-1), non-specified delivery persons cannot access it during restricted hours, and can only access it at times outside of restricted hours (unrestricted hours). On the other hand, delivery box 130-2 is separated into an area that anyone can enter regardless of the time (fully shared area) 140-2 and a semi-shared area 140-1, and is provided so that it can be accessed from both the semi-shared area 140-1 and the fully shared area 140-2. When multiple delivery boxes 130 with different access restrictions are provided in this way, it is preferable to configure the allocation server 109 to prioritize the identification of delivery boxes 130 that are difficult for delivery personnel to access (i.e., delivery boxes 130-1 with higher access restrictions). By adopting such a configuration, it becomes easier to secure a locker for delivery box 130-2 that is always accessible to delivery personnel. Conversely, if there is a delivery box 130 that the delivery person cannot access at the desired delivery date and time or scheduled delivery date and time, a delivery box that the delivery person can access (in the example in Figure 2, delivery box 130-2) will be identified.

[0025] After identifying the delivery box 130, the allocation server 109 further assigns one of the empty lockers to each package. Locker assignment may be done by randomly or arbitrarily selecting one of several empty lockers, or by selecting based on the resident's score. For example, for a package addressed to resident 102 with a high score, a locker in an easily accessible location may be prioritized. Alternatively, the allocation server 109 may be configured to assign a locker suitable for the size and shape of the package. In this case, for example, an empty locker that can accommodate the package and has the highest ratio of package volume to locker volume may be assigned. By assigning lockers while considering the size and shape of the package in this way, mismatches between lockers and packages can be prevented, allowing for more efficient use of lockers. Furthermore, when assigning multiple lockers to multiple packages delivered to the same resident 102, the allocation server 109 may be configured to assign multiple lockers located close to each other. In addition, if there are multiple packages delivered to the same resident 102, a locker that can accommodate multiple packages in one package may be assigned.

[0026] After allocating a locker, the allocation server 109 sends information including the box ID and locker ID (allocation information) as a response to the shipping server 105 and / or delivery management server 107 that sent the locker allocation request. This allocation information may include the various pieces of information associated with the box ID and locker ID as described above. By obtaining the allocation information, the delivery person can secure a locker before delivering the package, thus avoiding the need for redelivery of packages that would otherwise be forced due to reasons such as the absence of empty lockers or the inability to use empty lockers because they are of an unsuitable shape or volume to accommodate the package. The allocation server 109 may also store the time the allocation information was sent in its storage device. Furthermore, the allocation information may also be sent to the user terminal 103.

[0027] (c) Various notifications to delivery persons, senders, and residents When a delivery person places a package in a locker, the package is detected by a sensor installed in each locker, and a notification (placement notification) indicating that the package has been placed is sent to the box management server 111. The allocation server 109 may be configured to receive the placement notification directly from the delivery box 130 or via the box management server 111. The allocation server 109 may be configured to determine the time the package was placed based on the placement notification and store this time in a storage device.

[0028] Similarly, when resident 102 retrieves a package from the locker, this is detected by a sensor installed in each locker, and a notification (receipt notification) indicating that the package has been received is sent to the box management server 111. The allocation server 109 may be configured to obtain the receipt notification directly from the delivery box 130 or from the box management server 111. The allocation server 109 may be configured to determine the time when the package was received by resident 102 based on the receipt notification and store this in a storage device. By using the storage notification and the receipt notification, the time (dwell time) from when the package is stored in the locker until it is retrieved by resident 102 can be calculated. This dwell time can be used to calculate a user score. On the other hand, the time (delivery time) from when the allocation information is sent until the package is stored in the locker can also be calculated, and this may be used to calculate the delivery person's score.

[0029] The allocation server 109 may also be configured to prompt residents 102 to pick up their packages. For example, the allocation server 109 may be configured to send a signal to the user terminal 103 to notify the resident 102 of the package pickup deadline when it approaches (24 hours, 12 hours, 3 hours, 1 hour before the deadline, etc.) or when the package pickup deadline has passed.

[0030] Alternatively, the allocation server 109 may be configured to send a notification (retrieval notification) to the shipping server 105 and / or the delivery management server 107 to the delivery person to retrieve a package once it has been stored, in order to prevent packages from remaining in the locker for a long period of time without being received by the resident 102. Adopting such a configuration not only improves the efficiency of locker utilization, but also prevents spoilage in the locker if the package contains perishable items such as food or ingredients, thus ensuring product liability to the resident 102.

[0031] Calculation of the score As described above, this delivery system 100 reduces the burden on delivery personnel and significantly reduces the time and cost required for delivery. It also eliminates the waste of energy associated with redelivery of packages, which can be considered a contribution to the natural environment. On the other hand, residents 102 are not required to be home when packages are delivered, and only need to receive the package by the deadline, thus freeing them from the stress associated with receiving packages and allowing them to use their time effectively. In order to promote the widespread adoption of this delivery system 100, which has such advantages, the contribution of residents 102 and delivery personnel to this delivery system 100 may be calculated as a score and used to improve services for residents 102 and delivery personnel.

[0032] A score for a delivery person may be calculated based on, for example, the total number of times the delivery person has used the delivery system 100 or the number of uses within a certain period. Alternatively, the delivery time, i.e., the time from locker assignment to the placement of the package in the locker, may be used, with a higher score awarded to the delivery person for shorter times. Similarly, the time from sending a package collection notification to the collection of the package may be used, with a higher score awarded to the delivery person for shorter times. This can improve the efficiency of locker utilization. Services for delivery people based on their score may include a reduction in the fee charged for locker assignment services and priority assignment to lockers that are easier to accommodate packages in.

[0033] Similarly, the score for resident 102 may be calculated based on, for example, the total number of times resident 102 has used the delivery system 100 or the number of times it has been used over a certain period. Alternatively, the dwell time of the package, i.e., the time from when the storage notification is received by the allocation server 109 until the receipt notification is received by the allocation server 109, may be used, and a shorter time may result in a higher score for resident 102. Conversely, if the pickup deadline is exceeded, the score may be reduced according to the amount of time the pickup deadline has been exceeded. This can improve the efficiency of locker utilization. Alternatively, the floor on which resident 102 lives may be reflected in the score. When a delivery person transports packages to each dwelling unit, the burden is greater the higher the floor the delivery destination is. Therefore, by more strongly promoting the use of the delivery system 100 to residents 102 who live on higher floors, it is possible to reduce delivery costs more effectively. Services for resident 102 according to the score may include lower delivery fees via the delivery company 106, provision of free delivery services, and priority allocation of lockers that are easy for residents to use.

[0034] 2-2. Delivery Boxes As described above, the delivery box 130 is installed in an apartment building. It is also possible to use a known delivery box as the delivery box 130. For example, as shown in Figure 3(A), a delivery box 130 can be used that has multiple lockers 132 of different sizes. The delivery box 130 may be equipped with a monitor 134 for explaining the status of packages and how to operate the delivery box 130, a card reader 136 for residents 102 and delivery personnel to unlock the lockers, an operation panel 138, etc. Although not shown, an optical scanner capable of reading QR codes (registered trademark) or barcodes, or a reader using short-range wireless communication (RF reader), may be provided instead of, or in conjunction with, the card reader 136. Each locker 132 is equipped with a sensor for detecting the presence or absence of packages. The delivery box 130 is configured to transmit information to the allocation server 109 and / or the box management server 111 based on signals obtained from the sensors, indicating whether or not there are packages in each locker, i.e., whether or not each locker is available.

[0035] Alternatively, as shown in Figure 3(B), the delivery system 100 may use a delivery box 130 in which all lockers 132 are the same size. In this case, the depth of the locker 132 is preferably 150 mm to 600 mm, 200 mm to 500 mm, or 200 mm to 400 mm, for example, a length corresponding to A4 size (297 mm) is preferred. The width of the locker 132 is preferably 100 mm to 500 mm, 150 mm to 400 mm, or 200 mm to 300 mm, for example, a width corresponding to A4 size (210 mm) is preferred. The height of the locker 132 is preferably 50 mm to 20 mm, 75 mm to 150 mm, or 90 mm to 125 mm, for example, 100 mm is preferred. In the field of distribution, the size of most packages delivered is within the above ranges, so by configuring the locker 132 to satisfy the above parameters, it is possible to accommodate most of the packages delivered.

[0036] When using a delivery box 130 equipped with lockers 132 of the same size, each locker 132 may be configured to accommodate a dedicated container 150 of the same size and shape. For example, the container 150 shown in Figure 4(B) can be used. The container 150 has a basic configuration comprising a housing 152 that provides space for storing luggage, and a lid 154 for closing the space, and may optionally have a lock 156 or a handle 158. The lid 154 has a fixing part 152b that is fixed on the housing 152, and a movable part 152a that can be opened and closed, and is configured so that only a part of the lid 154 opens. The container 150 is configured to be approximately the size of the volume of the locker 132 (for example, 75% to 100%, 80% to 100%, 90% to 100%, or 95% to 100% of the volume of each locker).

[0037] The delivery person carries the package, stored in container 150, to the delivery box 130 and inserts container 150 into locker 132 (Figure 4(A)). Meanwhile, the resident 102 pulls container 150 out of locker 132, opens the lid 154 to take out the package, and returns container 150 to locker 132. Once the package is removed, empty container 150 is collected when the delivery person places another container 150 into locker 132. Therefore, regardless of the type or shape of the package being delivered, the delivery person delivers containers 150 of the same size and shape. This means that only packages of standardized, identical shape and size are handled during delivery, which greatly contributes to improving delivery efficiency. Furthermore, since the package is delivered while stored in container 150, there is no need to use packaging materials such as cardboard to temporarily maintain its shape for delivery. This contributes not only to reducing delivery costs but also to protecting the natural environment by reducing the consumption of packaging materials.

[0038] Furthermore, when using container 150 for delivery, it is preferable to configure the delivery box 130 and container 150 so that container 150 cannot be removed by the resident 102. For example, as shown in the schematic top view of Figure 5, a stopper 160 may be provided on container 150, and an anti-discharge mechanism 162 that can come into contact with the stopper 160 may be provided on each locker 132. The anti-discharge mechanism 162 can take a first mode that allows the removal of container 150 and a second mode that prohibits the removal of container 150, and should be configured to come into contact with the stopper 160 in the second mode and not come into contact with the stopper 160 in the first mode. It is preferable that the anti-discharge mechanism 162 is configured such that when container 150 is pulled out of the locker 132 to its maximum extent in the second mode, the entire movable part 152a and part of the fixed part 152b of the lid 154 are exposed from the locker 132, and the other part of the fixed part is located inside the locker 132 and comes into contact with the stopper 160. This configuration allows resident 102 to open the lid 154 and retrieve their belongings, while also preventing resident 102 from removing container 150.

[0039] 2-3. Box Management Server The box management server 111 is a server or terminal connected to the delivery boxes 130 via the network 120 so as to be able to communicate with them. The box management server 111 is configured to acquire locker usage information for each delivery box 130 based on signals from sensors installed in each locker. If the allocation server 109 does not acquire locker usage information from the delivery boxes 130, the box management server 111 is configured to send the locker usage information to the allocation server 109 periodically or in response to requests from the allocation server 109.

[0040] 2-4. Shipping Server The shipping server 105 is a server or terminal managed by the seller to whom resident 102 orders goods, or by the individual who ships goods to resident 102. The shipping server 105 may be a stationary (desktop) computer, a notebook computer, or a mobile communication terminal such as a mobile phone, tablet, or smartphone.

[0041] When a sender requests delivery service provider 106 to ship a package, the shipping server 105 may be configured to send a delivery request to the delivery management server 107. The delivery request may include the fact that resident 102 has selected this delivery system 100, as well as the user ID, resident 102's address and name, and may also include the contents, shape, and size of the package, desired delivery date and time, deadline for receiving the package, and date and time for package collection.

[0042] On the other hand, if the seller themselves delivers the goods as a package, or if an individual delivers goods as a package, the shipping server 105 may be configured to send a locker allocation request to the allocation server 109 and receive allocation information sent from the allocation server 109 in response. The shipping server 105 may also be configured to manage the packages to be delivered and to arrange vehicles for package delivery. After receiving the allocation information, the shipping server 105 may be configured to send information to the user terminal 103, including the box ID, address, name, locker ID, locker number, scheduled delivery date and time, pickup deadline, and some or all of the collection date and time of the delivery box 130 where the package will be stored.

[0043] 2-5. Delivery Management Server The delivery management server 107 is a server managed by the delivery company 106 and is equipped with the necessary functions for carrying out delivery operations, as well as the function of receiving delivery requests from the dispatch server 105. The delivery management server 107 is configured to send a locker allocation request to the allocation server 109 after receiving a delivery request, and to receive allocation information sent from the allocation server 109 in response. The box ID and locker ID included in the allocation information are associated with identifiers assigned to packages on the delivery management server 107. The delivery management server 107 may also be configured to send information including the scheduled delivery date and time of the package, the number of the delivery box 130 or its locker 132 at the delivery destination, the deadline for receiving the package, and the collection date and time to the dispatch server 105 and / or the user terminal 103.

[0044] 2-6. User Terminals The user terminal 103 is a terminal equipped with communication functions that can be operated by the resident 102, and examples include a stationary (desktop) computer, a notebook computer, or a mobile communication terminal such as a mobile phone, tablet, or smartphone. The resident 102 can use the user terminal 103 to order goods via e-commerce, and at that time, can notify the seller, i.e., the sender of the package including the goods, whether or not to use this delivery system 100. The user terminal 103 is also configured to receive various notifications sent from the allocation server 109, the shipping server 105, and / or the delivery management server 107. This function allows the resident 102 to know the delivery date and time of the package, the delivery box 130 and its locker 132 to which the package will be delivered, the deadline for receiving the package, and the collection date and time.

[0045] Furthermore, resident 102 registers with the allocation provider 108 in advance, or when using the delivery system 100 for the first time. Upon registration, a user ID is issued, and the various information described above regarding resident 102 and user terminal 103 is associated with the user ID.

[0046] As described above, in the delivery method using this delivery system 100, the delivery person secures the delivery box 130 and its locker 132, then delivers the package and places it in the locker 132. At this time, there is no need to deliver the package to each resident 102's dwelling unit, nor is there any need to confirm that residents 102 are at home. Therefore, this delivery method places an extremely small burden on the delivery person and can significantly reduce the time and cost required for delivery. In addition, residents 102 are freed from the stress of waiting for package delivery and can use their time effectively.

[0047] Furthermore, in this delivery method, the allocation of lockers 132 is performed by an allocation server 109 that is independent of the delivery companies 106 that undertake deliveries and the box management companies 110 that manage the delivery boxes 130. Therefore, even in the delivery industry which consists of multiple delivery companies 106 and multiple box management companies 110, the usage status of lockers 132 of delivery boxes 130 with different models and specifications can be centrally monitored. As a result, even when various senders 104 send packages to residents 102 living in different apartment buildings using different delivery companies 106, lockers 132 can be efficiently allocated, leading to improved operational efficiency and effective use of human resources for the entire delivery industry.

[0048] <Second Embodiment> In this embodiment, the method of delivering a package using the delivery system 100 will be specifically explained using the flowchart shown in Figure 6. Here, as an example, we will describe a case in which a resident 102 orders goods from a seller via e-commerce, and the seller requests a delivery company to deliver the package containing those goods as the sender. Therefore, the delivery company is responsible for shipping the package. Configurations that are the same as or similar to those described in the first embodiment may be omitted from the explanation.

[0049] First, resident 102 uses user terminal 103 to place an order for goods with the seller. The order may be placed directly with the seller's shipping server 105 via network 120, or through an e-commerce platform provided by a third party (platform provider). The former is called a company-owned website type e-commerce, and the latter is called a mall type e-commerce. The following explanation will mainly use company-owned website type e-commerce as an example, but this delivery system 100 can also be applied to mall type e-commerce.

[0050] Specifically, resident 102 operates user terminal 103 and accesses shipping server 105 via network 120 (S100). This allows resident 102 to select desired products on shipping server 105 and place an order. Once the order is confirmed, the seller uses shipping server 105 to access delivery management server 107 and send a delivery request (S102). As described above, the delivery request includes the user ID, resident 102's address and name, and may also include the contents, shape, and size of the package, desired delivery date and time, deadline for receiving the package, and package collection date and time.

[0051] Subsequently, the availability of lockers 132 in the delivery box 130 of the apartment building where resident 102 is a delivery destination is checked on the delivery management server 107. Specifically, the delivery management server 107 sends a locker allocation request to the allocation server 109 (S104). Upon receiving the locker allocation request, the allocation server 109 allocates a locker 132 to accommodate the package based on locker usage information periodically obtained from the delivery box 130 or the box management server 111. If locker usage information is not periodically obtained, the allocation server 109 sends a signal to the delivery box 130 or the box management server 111 requesting locker usage information (S106, S108). In response to the signal requesting locker usage information, the delivery box 130 and the box management server 111 send the locker ID of an empty locker 132 to the allocation server 109 (S110, S112). In this case, if there are multiple empty lockers 132, it is preferable that the locker IDs of all empty lockers 132 be sent to the allocation server 109. If there are delivery boxes 130 that the delivery person cannot access at the desired delivery date and time or scheduled delivery date and time, the allocation server 109 will select a delivery box 130 that the delivery person can access.

[0052] The allocation server 109 further assigns lockers 132 to packages based on locker usage information. At this time, as described above, a locker 132 suitable for the size and shape of the package may be assigned. For example, a locker 132 that can accommodate the package and has the maximum ratio of the package's volume to the locker's volume may be assigned. Also, if there are multiple packages to be delivered to the same resident 102, a locker 132 that can accommodate multiple packages may be assigned. Furthermore, lockers 132 may be assigned according to the resident 102's score.

[0053] After the allocation of locker 132 is complete, the allocation server 109 sends the allocation information to the delivery management server 107 (S114). Upon receiving the allocation information, the delivery management server 107 sends information to the user terminal 103 that includes all or some of the following: the name of the delivery box 130 and the number of locker 132 included in the allocation information, as well as the scheduled delivery time, the deadline for receiving the package, and the date and time of package collection (S106). The delivery management server 107 may also send all or some of this information to the dispatch server 105 (S108). At this time, the resident 102 may send a signal from the user terminal 103 to the delivery management server 107 to change the scheduled delivery time within the acceptable range of the delivery company 106. Upon receiving this signal, the delivery management server 107 determines whether or not to allow the change in the scheduled delivery time, and if it does, changes the time to allocate locker 132 considering the desired delivery date and time after the change.

[0054] The goods to be delivered to resident 102 may be transported from the sender 104 to the delivery company 106, or the delivery company 106 may collect them. Alternatively, if the goods are stored in a logistics warehouse managed by the delivery company 106, the delivery company 106 may pick up the goods and then deliver them. If the allocation company 108 also acts as the delivery company 106, the packages to be delivered are collected by the allocation company 108, a locker 132 is assigned to each package, and then the packages are delivered by the allocation company 108.

[0055] When a package is placed in a locker by the delivery person, a storage notification is sent to the box management server 111 based on a signal from a sensor installed in each locker (S110). The storage notification may also be sent directly from the delivery box 130 to the allocation server 109 (S112). The delivery management server 107 also sends a notification (delivery completion notification) to the user terminal 103 to inform the resident 102 that the delivery of the package has been completed (S114). The delivery completion notification may also be sent to the dispatch server 105 (S116). The delivery completion notification includes the fact that the package has been stored, as well as the name of the delivery box 130 and the locker number 132. The delivery completion notification may also include the pickup deadline and the date and time of package collection. Although not shown in the diagram, if the package pickup deadline is approaching, or if the resident 102 does not pick up the package by the deadline, the allocation server 109 may send a notification to the user terminal 103 to encourage pickup. Furthermore, if a certain period of time has elapsed since the pickup deadline, the allocation server 109 may send a retrieval notification to the delivery management server 107, and after the package has been retrieved, a notification informing the user terminal 103 that the package has been retrieved may be sent. In addition, if the package is not delivered after a certain period of time has elapsed since the allocation of the locker 132 (for example, if a storage notification is not sent even after a certain period of time has elapsed since the allocation information was sent), the allocation server 109 may cancel the allocation.

[0056] When a package is received by resident 102, a receipt notification is sent from the delivery box 130 to the box management server 111 based on signals from sensors installed in each locker (S118). This notification may also be sent from the delivery box 130 to the allocation server 109 (S120). As a result, the now-empty locker 132 can be used again for allocation on the allocation server 109.

[0057] This delivery method can also be applied when resident 102 orders goods in a face-to-face transaction and has them delivered. In this case, at least part of step S100 is done orally or in writing, and resident 102 only needs to specify the delivery destination, the delivery box 130, i.e., the apartment building in which they live, to the seller, who is the sender. This delivery method can also be applied when an individual requests a delivery company 106 to ship a package. In this case, the individual, who is the sender, sends a delivery request to the delivery company 106 via the shipping server 105 (S102). At this time, information about resident 102, the recipient of the delivery (name, address, name of the apartment building, unit number, address of user terminal 103, etc.) should be included in the delivery request.

[0058] As described above, in the delivery method described in this embodiment, the delivery company, which is the delivery person, secures a locker 132 in advance to hold the package before delivering it. Therefore, regardless of whether the resident 102 is at home or not, the package can be reliably stored in the locker 132, completely eliminating the hassle of redelivery. As a result, it is possible to significantly reduce delivery costs and make effective use of the human resources of the delivery person.

[0059] <Third Embodiment> In this embodiment, the delivery method will be specifically explained using an example in which a seller who conducts commercial transactions with resident 102 delivers a package containing goods. In this example, the seller acts as both the sender and the delivery person. Configurations that are the same as or similar to those described in the first and second embodiments may be omitted from the explanation.

[0060] Figure 7 shows a flowchart of this delivery method. First, the resident 102 uses the user terminal 103 to access the seller's shipping server 105 and place an order for the goods (S130). Similar to the second embodiment, the order for the goods may be placed through face-to-face business transactions, in which case at least part of this step will be done orally or in writing. Subsequently, the seller sends a locker allocation request to the allocation server 109 via the shipping server 105 in order to deliver the package containing the goods to the delivery box 130 (S132). Similar to the second embodiment, the allocation server 109, upon receiving the locker allocation request, accesses the delivery box 130 or the box management server 111 (S134, S136) and receives locker usage information (S138, S140). If locker usage information is periodically transmitted from the delivery box 130 or the box management server 111, steps S134 and S136 do not need to be performed.

[0061] Similar to the second embodiment, the allocation server 109 allocates the delivery box 130 and its locker 132 based on the locker usage information, generates allocation information, and sends it to the shipping server 105 (S142). The seller, who is the delivery person, can secure the delivery box 130 and its locker 132 to store the package using the name of the delivery box 130 and the number of the locker 132 included in the allocation information. After this, information including the scheduled delivery time, the deadline for receiving the package, and the date and time of package collection may be sent to the user terminal 103 via the shipping server 105 (S144).

[0062] Once the delivery of the package is complete, a delivery notification is sent from the delivery box 130 to the box management server 111 (S146). Similar to the second embodiment, the delivery notification may also be sent to the allocation server 109 (S148). The seller may also send a shipping completion notification to the user terminal 103 via the shipping server 105 (S150). Subsequently, once the package is received by the resident 102, a receipt notification is sent from the delivery box 130 to the box management server 111 (S154). The receipt notification may also be sent from the delivery box 130 to the allocation server 109 (S156).

[0063] In the delivery method described in this embodiment, the seller, who also acts as the delivery person and sender, secures a locker 132 in advance to hold the package before delivering it. Therefore, regardless of whether the resident 102 is at home or not, the package can be reliably placed in the locker 132, completely eliminating the need for redelivery. Furthermore, it is possible to significantly reduce delivery costs and reduce the time the package remains in the locker 132. As a result, it is possible to improve the satisfaction of the resident 102 while suppressing the increase in the number of lockers 132 relative to the volume of packages.

[0064] The embodiments described above as embodiments of the present invention can be combined and implemented as appropriate, insofar as they do not contradict each other. Furthermore, devices based on the display devices of each embodiment, in which a person skilled in the art has added, deleted, or modified components, or added, omitted, or modified processes, are also included within the scope of the present invention, as long as they retain the essence of the present invention.

[0065] Any effects or benefits other than those brought about by the embodiments described above, if they are clear from the description herein or easily predictable to a person skilled in the art, are naturally considered to be brought about by the present invention. [Explanation of Symbols]

[0066] 100: Delivery system, 102: Permanent resident, 102: Resident, 103: User terminal, 104: Shipper, 105: Shipping server, 106: Delivery company, 107: Delivery management server, 108: Allocation company, 109: Allocation server, 110: Box management company, 111: Box management server, 120: Network, 130: Delivery box, 130-1: Delivery box, 130-2: Delivery box, 132: Locker, 134: Monitor, 136: Card reader, 138: Control panel, 140: Shared area, 140-1: Semi-shared area, 140-2: Fully shared area, 142: Private area, 144: Door, 146: Door, 150: Container, 152: Enclosure, 152a: Movable part, 152b: Fixed part, 154: Lid, 156: Lock, 158: Handle, 160: Stopper, 162: Discharge prevention mechanism

Claims

1. In the allocation server, locker usage information relating to the usage status of a plurality of lockers in at least one delivery box provided in the apartment building is acquired from a box management server that manages the at least one delivery box; allocating, on the allocation server, one of the plurality of lockers to at least one package to be delivered to a resident of the housing complex; and A delivery method including transmitting a locker identifier for identifying the assigned locker from the allocation server to a delivery management server that manages the delivery of the package before storing the package in the assigned locker.

2. The delivery method according to claim 1 , further comprising transmitting the locker identifier from the allocation server to a user terminal managed by the resident before storing the package in the assigned locker.

3. The method of claim 1 , wherein the allocation of the lockers is based on a size of the package and a size of the plurality of lockers.

4. The delivery method according to claim 1, further comprising storing in a storage device connected to the allocation server the time when the locker identifier of the assigned locker was transmitted and the time when the package was placed in the assigned locker.

5. The delivery method according to claim 2 , further comprising sending a delivery completion notification to the user terminal to notify the user that the package has been placed in the assigned locker.

6. The delivery method according to claim 5, further comprising storing the time when the delivery completion notification was sent and the time when the package was removed from the assigned locker in a storage device connected to the allocation server.

7. The method of claim 1 , further comprising storing the occupant's floor address in a storage device connected to the allocation server.

8. The method of claim 1 , further comprising storing the number of deliveries of the package to the resident in a storage device connected to the allocation server.

9. the at least one package delivered to the same resident includes multiple packages; The delivery method according to claim 1 , wherein the allocation of the lockers is performed such that priority is given to the lockers capable of accommodating the plurality of packages.

10. the at least one package includes a plurality of packages; The delivery method according to claim 1 , wherein the plurality of packages to which the lockers are assigned are collected at one location and then delivered to the delivery box.

11. Acquiring locker usage information relating to the usage status of a plurality of lockers in at least one delivery box provided in the apartment building from a box management server that manages the delivery box; assigning one of the plurality of lockers to at least one package to be delivered to a resident of the apartment complex; and An allocation server configured to transmit a locker identifier to a delivery management server that manages the delivery of the package to identify the assigned locker before storing the package in the assigned locker.

12. The allocation server of claim 11, further configured to transmit the locker identifier to a user terminal managed by the resident before storing the luggage in the assigned locker.

13. The allocation server of claim 11, wherein the allocation of the lockers is based on a size of the package and a size of the plurality of lockers.

14. The allocation server of claim 11, further configured to store in a storage device a time of transmitting the locker identifier of the assigned locker and a time of receiving the luggage in the assigned locker.

15. The allocation server according to claim 12, further configured to send a delivery completion notification to the user terminal to notify that the package has been placed in the assigned locker.

16. 16. The allocation server of claim 15, further configured to store in a storage device the time the delivery completion notification was sent and the time the package was removed from the assigned locker.

17. The allocation server of claim 11 further configured to store the resident's floor address in a storage device.

18. The allocation server of claim 11 , further configured to store in a storage device the number of deliveries of the package to the resident.

19. The allocation server according to claim 11, configured to preferentially allocate the locker capable of containing the multiple packages when the at least one package delivered to the same resident includes multiple packages.