JP7530072B2 - Shipping Cases and Shipping Management Systems - Google Patents

Description

The present invention relates to a delivery case and a delivery management system.

Conventionally, when sending small parcels, users would bring the parcel to a convenience store or a parcel company's office, or request the parcel to be collected by the parcel company. For example, Patent Document 1 proposes a parcel collection management system that can check that the parcel does not exceed the load capacity of the transport vehicle at the location where the parcel is to be received, does not burden the parcel company with carrying the parcel to the parcel receiving location, and can also calculate the shipping fee for the ordered parcel.

JP 2011-225313 A

In recent years, there has been a demand for services that offer low delivery fees even if delivery takes several days. In order to keep delivery fees low, it is necessary to maximize the loading rate of delivery vehicles such as trucks, but deliveries vary in size and shape, which has been an obstacle to improving loading rates.

The present invention aims to provide a delivery case and delivery management system that can meet the needs of those who want to use a service with low delivery fees even if the delivery takes several days.

The delivery management system of the present invention comprises a delivery case consisting of an inner case and an outer case, and a server that manages the delivery case, wherein each of the inner case and outer case has a first identifier that allows information to be optically read and a second identifier that allows information to be read by wireless communication, the first identifier includes case identification information for managing each case, and the second identifier includes case identification information for managing each case and parcel identification information for managing parcels, the server manages the size, usage status and delivery information of each case in association with the case identification information, the delivery information includes information on the delivery location and the delivery route to the next delivery base, the server manages the parent-child relationship between the inner case and the outer case based on the information on the delivery route to the next delivery base, and the server is provided with a means for issuing delivery instructions to store the multiple inner cases in the same outer case and deliver them to the next delivery base when the multiple inner cases have different delivery locations and have the same delivery route to the next delivery base .
In the above delivery management system, the usage status of the case can be configured to include information on parent case, child case, and unused case.
In the above delivery management system, the server can be configured to include a means for managing the number of times each case has been used in association with the case identification information, and a means for sending an alert to a specific terminal when the number of times each case has been used exceeds a predetermined number.
The above delivery management system can further include a first reading terminal that reads the first identifier and transmits it to the server, and a second reading terminal that reads the second identifier and transmits it to the server, wherein the second reading terminal can simultaneously read the second identifiers of multiple contained inner cases without unpacking the outer case, and the server can be configured to include a means for checking consistency between delivery information for the contained inner case and delivery information for the outer case that contains the inner case based on information on the second identifier of the inner case received from the second reading terminal.
In the above delivery management system, the first reading terminal and/or the second reading terminal can have a means for transmitting location information to the server, and the server can be configured to have a means for managing the location information received from the first reading terminal and/or the second reading terminal in association with the case identification information, and a means for transmitting the location information of the delivery case queried by an external terminal when the location information of the delivery case is queried from the external terminal.
In the above-mentioned delivery management system, the second identifier is a medium on which information can be rewritten, and is equipped with a writer terminal capable of rewriting the information recorded in the second identifier, and the second reading terminal can be configured to wait for communication with the server to be restored when communication with the server is impossible, and then transmit the information of the second identifier that has been read to the server.
In the above delivery management system, the first reading terminal and the second reading terminal may be configured to be composed of a smartphone or a tablet.

The present invention can improve the loading rate of delivery vehicles and meet the needs of those who want to use a service that offers low delivery fees even if the delivery takes several days.

FIG. 2 is a conceptual diagram of a delivery management method according to the present embodiment. FIG. 1 is a configuration diagram of a delivery management system according to an embodiment of the present invention. FIG. 4 is a diagram showing an example of data stored in a delivery information table according to the embodiment. 11 is a diagram showing an example of data stored in a table of delivery days by base-to-base route according to the embodiment. FIG. 11 is a diagram showing an example of data stored in a delivery base-specific storage days table according to the embodiment. FIG. FIG. 4 is a diagram showing an example of data stored in a delivery means table according to the embodiment. 11 is a diagram showing an example of data stored in a case management table according to the embodiment; FIG. FIG. 13 is a diagram showing an example of a screen showing the storage relationship of delivery cases displayed on the display of a management terminal. FIG. 1 is a perspective view showing an overview of a shipping case according to the present embodiment. 10 is a cross-sectional view taken along line XX in FIG. 9. FIG. 13 is a diagram illustrating a shipping case stored in a larger shipping case. 1A to 1C are diagrams showing variations of a shipping case according to the present embodiment. 10 is a flowchart showing a receiving process according to the embodiment. 10 is a flowchart showing a delivery management process according to the embodiment.

Below, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a conceptual diagram of a delivery management method according to this embodiment. In the following, first, the delivery management method according to this embodiment will be described with reference to FIG. 1.

In the delivery management process according to the present embodiment, as shown in FIG. 1, multiple delivery bases 2 to 5 are connected in a network, and delivery item B is delivered from the receiving location 2 to the delivery location 5 via each of the delivery bases 2 to 5 in sequence. FIG. 1 illustrates a scene in which sender S delivers delivery item B to recipient R. In the following, the rough delivery direction (direction) from each delivery base N to the next delivery base N+1 is called the inter-base route. For example, in the example shown in FIG. 1, delivery item B is delivered from receiving location 2f to delivery location 5e via inter-base route C1f from receiving location 2f to primary storage location 3b, inter-base route C2d from primary storage location 3b to secondary storage location 4b, and inter-base route C3e from secondary storage location 4b to delivery location 5e. In addition, if there are multiple delivery directions from delivery base N to the next delivery base N+1, there will be multiple inter-base routes starting from delivery base N. For example, in the example shown in FIG. 1, there is an inter-base route C2c that starts at the primary storage location 3b and heads from the primary storage location 3b to the secondary storage location 4a, and an inter-base route C2d that heads from the primary storage location 3b toward the secondary storage location 4b.

When the sender S delivers delivery item B, he/she starts a dedicated program installed in the user terminal 50 and inputs the delivery information for delivery item B. As a result, the delivery information for delivery item B is sent from the user terminal 50 to the delivery management server 10 and stored in the database 11 of the delivery management server 10. Then, as shown in FIG. 1, the sender S brings delivery item B to the nearest receiving location 2 (for example, receiving location 2f in the example shown in FIG. 1) and hands over delivery item B to receiving location 2. The receiving location 2 may be, for example, a newspaper store, a gas station, a branch of a JA (agricultural cooperative), or a convenience store.

When delivery item B is received at the receiving location 2, the reading terminal 42 installed at the receiving location 2 obtains the delivery information of delivery item B. For example, the sender S displays the identification information of delivery item B on the display of the user terminal 50 using a dedicated program of the user terminal 50, and the reading terminal 42 reads the identification information of delivery item B, so that the reading terminal 42 can obtain the delivery information of delivery item B. The reading terminal 42 then transmits the identification information of delivery item B to the delivery management server 10 via the management terminal 41, and the delivery status of delivery item B stored in the delivery management server 10 is updated to, for example, "being stored at receiving location 2". In addition, the reading terminal 42 can optically read the QR code (registered trademark) 61 of the delivery case 60 to transmit the identification information of the delivery case 60 linked to the delivery to be shipped to the delivery management server 10.

At the receiving location 2, one or more deliveries B are stored in a delivery case 60. A two-dimensional code (e.g., QR code 61) and an IC tag (e.g., RF tag 62) that store identification information of the delivery case 60 are attached to the delivery case 60, and by reading the QR code 61 or the RF tag 62 with a handheld reading terminal 42, the identification information of the delivery case 60 is transmitted to the delivery management server 10 via the management terminal 41, and the delivery case 60 is associated with the delivery B stored therein in the database 11.

Then, the delivery item B is sorted for each base route C1 at the receiving location 2, and is delivered from the receiving location 2 to the primary storage location 3 for each base route C1 by a delivery means such as a truck that delivers the delivery item B along each base route C1. For example, in the example shown in FIG. 1, the delivery item B is delivered to the primary storage location 3b via the base route C1f, so it is sorted into the same group as other deliveries that are delivered to the primary storage location 3b via the same base route C1f, and is delivered to the primary storage location 3b via the base route C1f together with the other deliveries sorted into the same group. In addition, at each of the delivery bases 2 to 4, when shipping the delivery item B, the RF tags 62 of the delivery cases 60 are read simultaneously by the reading terminal 42 in a non-contact manner, so that the identification information of the delivery case 60 linked to the delivery item to be shipped can be transmitted to the delivery management server 10, and the delivery status of the delivery item to be shipped can be updated to "moving along the base route C1" or the like in the delivery management server 10. In addition, by optically reading the QR code 61 on the delivery case 60 with the reading terminal 42, the identification information of the delivery case 60 linked to the delivery item being shipped can be transmitted to the delivery management server 10.

At the primary storage location 3, deliveries are received from multiple receiving locations 2, and the deliveries are sorted for each inter-base route C2 to the secondary storage location 4, which is the next delivery base. At each of the delivery bases 3 to 5, when deliveries are received, the RF tags 62 of the delivery cases 60 containing the deliveries are read simultaneously in a non-contact manner by the reading terminal 42, and the identification information of the delivery cases 60 linked to the received deliveries can be transmitted to the delivery management server 10. This allows the delivery management server 10 to update the delivery status of the received deliveries to "being stored at delivery bases 3 to 5", for example. Also, the QR code 61 of the delivery case 60 can be optically read by the reading terminal 42, and the identification information of the delivery case 60 linked to the received deliveries can be transmitted to the delivery management server 10.

If the delivery B stored in the primary storage location 3 meets any of the following conditions, it is delivered to the secondary storage location 4. Whether the following conditions are met is determined for each inter-base route.
Condition 1: The total volume of the deliveries exceeds a predetermined standard volume determined based on the available capacity of a delivery means such as a truck (for example, 80% of the available capacity of the truck's loading platform).
Condition 2: There is a delivery whose margin of residence, which is the difference between the delivery deadline days of the delivery and the number of days required for delivery, is less than a predetermined reference number of days.
Regarding condition 2, for example, if the delivery deadline for delivery item B is 20 days and the number of days required for delivery is 18 days, the remaining margin days will be 2 days. In this case, if the reference number of days is 3 days, delivery item B will be a "delivery item with a retention margin days less than the predetermined reference number of days," and deliveries (including deliveries with a retention margin days that are not less than the predetermined reference number of days) that are delivered on the base-to-base route on which delivery item B exists will be delivered.

Furthermore, delivery B delivered to the secondary storage location 4 is sorted according to inter-base route C3 and delivered to the delivery location 5. When delivery B arrives at the delivery location 5, the delivery management server 10 sends a notification to recipient R that delivery B has been delivered to the delivery location 5. This allows recipient R to go to the delivery location 5 to pick up delivery B. Furthermore, the delivery fee required for the delivery of delivery B is charged to sender S and/or recipient R by the delivery management server 10.

In the present invention, the delivery means such as trucks that deliver items between each of the delivery bases 2 to 5 are not only trucks arranged exclusively by the delivery company, but also the free space (free capacity) of trucks arranged by companies that do not specialize in the delivery of items, such as the bed of a truck after delivering newspapers from a printing company to a newspaper delivery office, the bed of a truck after delivering food to the JA, or the bed of a truck after delivering kerosene to a gas station, making it possible to keep delivery costs low. In addition, the delivery means for delivery from the primary storage location 3 to the secondary storage location 4 is not limited to automobiles such as trucks, and motorcycles, bicycles, freight trains, ships, etc. may also be used. In addition, although a configuration using an airplane as the delivery means can be used, it is preferable to use a configuration that does not use an airplane as the delivery means from the viewpoint of delivery costs.

System Configuration
Next, the delivery management system 1 according to this embodiment will be described. Fig. 2 is a configuration diagram of the delivery management system 1 according to this embodiment. As shown in Fig. 2, the delivery management system 1 according to this embodiment is composed of a delivery management server 10, a WMS (Warehouse Management System) server 20, a TMS (Transport Management System) server 30, a management terminal 41 and a reading terminal 42 arranged at each of the delivery bases 2 to 5, a user terminal 50 owned by a user, and a delivery case 60 for containing delivery items. Each component will be described below.

As shown in FIG. 2, the delivery management server 10 has a database 11, a computing device 12, a storage device 13, and a communication device 14.

The database 11 stores various tables that store information necessary for the delivery management processing according to this embodiment. Specifically, the database 11 stores a delivery information table 111, a delivery days table 112 for each route between bases, a storage days table 113 for each delivery base, a delivery means table 114, and a case management table 115.

Figure 3 is a diagram showing an example of information stored in the delivery information table 111. As shown in Figure 3, the delivery information table 111 stores various information related to the delivery of the delivery, such as the identification information (identification number) of the delivery, the weight of the delivery, the size of the delivery, the name and contact information of the sender, the name and contact information of the receiver, and the delivery location. In this embodiment, the size of the delivery can be the size of the delivery case 60 in which the delivery is stored, and is defined as the number of units of the smallest delivery case 60, as described later. In addition, the delivery information table 111 also stores the delivery status (or the location information of the delivery) indicating which delivery base 2 to 5 the delivery is stored at, or which inter-base route C1 to C3 the delivery is being delivered to. Furthermore, the identification information (identification number) of the delivery case 60 in which the delivery is stored is also stored in the delivery information table 111 in association with each delivery.

Figure 4 is a diagram showing an example of information stored in the table of delivery days by base route 112. As shown in Figure 4, the table of delivery days by base route 112 stores the number of delivery days for each base route. The number of delivery days is the number of days required for a delivery means (vehicle, ship, railway, etc.) to deliver each base route C1 to C3, and does not include the number of days of residence at each delivery base. For example, if it takes one day for a truck T1 to deliver a delivery item on the base route C1f, as shown in Figure 4, the table of delivery days by base route 112 stores the number of delivery days for the base route C1f as "one day". In this embodiment, the number of delivery days for each base route C1 to C3 is previously checked, and the table of delivery days by base route 112 stores the number of delivery days for each base route C1 to C3 in advance. The number of delivery days can also be calculated based on the distance of each base route C1 to C3 and the average moving speed of the delivery means that delivers each base route C1 to C3.

Figure 5 is a diagram showing an example of information stored in the distribution base storage days table 113. As shown in Figure 5, the distribution base storage days table 113 stores the storage days of deliveries for each of the distribution bases 2 to 4 and each of the base routes C1 to C3. For example, as shown in Figure 5, the storage days of deliveries are stored such that the storage days for the base route C2c from the primary storage location 3b are 4 days, and the storage days for the base route C2d are 3 days, etc. In this embodiment, the actual data on the storage days of deliveries is statistically compiled for each of the distribution bases 2 to 4 and each of the base routes C1 to C3, and the average, frequent value, median, etc. of the storage days are calculated as the storage days, and are stored in advance in the distribution base storage days table 113. The distribution base storage days table 113 can also be configured so that the storage days are periodically updated using the latest actual data.

Figure 6 is a diagram showing an example of information stored in the delivery means table 114. As shown in Figure 6, the delivery means table 114 stores information on delivery means (for example, vehicles, ships, railways, etc.) that can deliver items on each of the base-to-base routes C1 to C3. Here, the delivery management system 1 according to this embodiment also uses free space (free capacity) on trucks and the like arranged by other companies, and there may be multiple delivery means on one base-to-base route, and there may be cases where one delivery means delivers on multiple base-to-base routes. For this reason, the delivery means table 114 stores information on delivery means for each base-to-base route and for each delivery means.

In addition, the delivery means table 114 also stores information that changes in real time, such as the location information of the delivery means and the free space of the loading platform of the delivery means. For example, when the delivery means is undergoing receiving or shipping procedures at a delivery base, the location of the delivery base is used as the location information of the delivery means, and when the delivery means has completed the shipping procedures and is moving between delivery bases, the location indicating the distance between the delivery bases where the delivery means is traveling, such as when traveling between delivery bases, can be stored in the delivery means table 114 as the location information of the delivery means. Alternatively, the delivery management server 10 can obtain GPS location information (latitude and longitude information) of the delivery means via the TMS server 30 from an information terminal installed on the delivery means or a mobile terminal carried by the driver of the delivery means, and update the location information of the delivery means in the delivery means table 114 in real time, as shown in FIG. 6. In addition, the free space of the delivery means is information on the size (capacity) of the delivery items that the delivery means can deliver, such as the capacity of 6, 12, or 18 items in the smallest delivery case 60. In this embodiment, the TMS server 30 is aware of the delivery status of the delivery means, and from that delivery status, estimates the free space on the delivery means' berth and transmits it to the delivery management server 10, thereby updating the information on the free space on the delivery means berth in the delivery means table 114 in real time.

7 is a diagram showing an example of information stored in the case management table 115. As shown in FIG. 7, the case management table 115 stores the identification number of the delivery case 60, the size of the delivery case 60, the identification information of the delivery item B directly accommodated in the delivery case 60, the number of times the delivery case 60 has been used, the identification number of the parent case (the delivery case 60 of one size larger that directly accommodates the delivery case 60), the usage status of the delivery case 60, and the like. Examples of the usage status of the delivery case 60 include a "child case (inner case)" indicating a state in which the delivery case 60 is accommodated in another delivery case 60, a "parent case (outer case)" indicating a state in which the delivery item is accommodated and is not accommodated in another delivery case 60 (a state in which only another delivery case 60 is accommodated or a state in which only delivery items are accommodated), and "unused" which does not accommodate any delivery items. The case management table 115 can be configured to store the weight of the delivery case 60 or the weight of the delivery case 60 and the delivery item.

When a delivery case 60 is used, the delivery management server 10 accesses the case management table 115 and increments the number of times it has been used by one. Based on the number of times the delivery case 60 has been used, the delivery management server 10 can also send an instruction to the management terminal 41 of the delivery base 2 to 5 where the delivery case 60 is stored to replace or discard the delivery case 60 that has been used a predetermined number of times or more.

Furthermore, in this embodiment, when delivery item B is received at the receiving location 2 and stored in the delivery case 60, the management terminal 41 at the receiving location 2 transmits the identification information of delivery item B and the identification information of the delivery case 60 to the delivery management server 10, and the identification information of the delivery stored in the delivery case 60 is stored in the case management table 115.

As described below, in this embodiment, multiple delivery cases 60 that are delivered along the same base-to-base route are stored together in a large delivery case 60 and delivered. For example, in the example shown in FIG. 7, a delivery case 60 with identification number "xxx601" and a delivery case 60 with identification number "xxx602" are stored in a delivery case 60 with identification number "xxx604". In this case, in the case management table 115, identification number "xxx604" is stored as the parent case of delivery cases 60 with identification number "xxx601" and identification number "xxx602".

Furthermore, in this embodiment, the management terminal 41 of each of the distribution bases 2 to 5 can refer to the case management table 115 to display information on the distribution cases 60 and the deliveries contained in each distribution case 60 on the display of the management terminal 41, as shown in FIG. 8. For example, in the example shown in FIG. 8, it is displayed so that it can be seen at a glance that the distribution case 60 with identification number "xxx604" contains distribution cases 60 with identification numbers "xxx601" and "xxx602", the distribution case 60 with identification number "xxx601" contains a delivery item with identification number "xx201", and the distribution case 60 with identification number "xxx602" contains a delivery item with identification number "xx202".

To perform the delivery management process according to this embodiment, the calculation device 12 executes the delivery management program stored in the storage device 13, thereby executing the following functions: delivery information registration function, retention margin calculation function, delivery feasibility determination function, and delivery instruction function. These functions are described below.

The delivery information registration function of the computing device 12 stores the delivery information of the delivery item input by the sender S from the user terminal 50 in the delivery information table 111. In this embodiment, when the sender S delivers the delivery item B, the user first starts a dedicated program on the user terminal 50, inputs the delivery information of the delivery item B, such as the identification number of the delivery item, the sender's name and contact information, the receiver's name and contact information, and the delivery location, and transmits the delivery information of the delivery item B to the delivery management server 10. As a result, the delivery information registration function receives the delivery information, such as the identification number of the delivery item, the sender's name and contact information, the receiver's name and contact information, and the delivery location, from the user terminal 50 via the communication device 14, and stores it in the delivery information table 111 of the database 11. In this embodiment, as described later, at the receiving location 2, a delivery case 60 that will accommodate the delivery item is determined based on the size and weight of the delivery item, and the delivery item is accommodated in the corresponding delivery case 60. Therefore, when the delivery management server 10 receives identification information of a delivery case 60 containing a delivery item from the management terminal 41, it stores delivery information such as the weight of the delivery item (set as the upper weight limit of the delivery case 60) and the size of the delivery item (how many items it is in the smallest delivery case 60 unit) in the delivery information table 111 of the database 11 based on the size of the delivery case 60.

In addition, in this embodiment, when the QR code 61 or RF tag 62 on the delivery case 60 containing delivery item B is read by the reading terminal 42 during the receiving or shipping procedure at each of the distribution bases 2 to 5, delivery information for updating the delivery status of delivery item B is sent from the management terminal 41 of each of the distribution bases 2 to 5 to the delivery management server 10. When the delivery information registration function receives delivery information indicating the delivery status of delivery item B from the management terminal 41 of each of the distribution bases 2 to 5, it updates the delivery status of the delivery item in the delivery information table 111 to the delivery status of delivery item B received from the management terminal 41 of each of the distribution bases 2 to 5.

The calculation function of the computing device 12 calculates the number of days that a delivery can be held at a delivery base, and is calculated as the difference between the delivery deadline and the number of days required for delivery of the delivery. Specifically, the calculation function of the number of days that a delivery can be held at a delivery base obtains the number of delivery days for each of the inter-base routes C1 to C3 from the table of delivery days by inter-base route 112, and obtains the number of days that the delivery will be stored for each of the delivery bases 2 to 4 and for each of the inter-base routes C1 to C3 from the table of storage days by delivery base 113. The calculation function of the number of days that a delivery can be held at a delivery base B obtains the number of days that the delivery will be stored for each of the delivery bases 2 to 4 and for each of the inter-base routes C1 to C3, and calculates the number of days that the delivery will be stored for each of the delivery bases B by adding the total number of delivery days for one or more inter-base routes that the delivery will take from the delivery base where the delivery is currently stored to the delivery location 5, and the total number of storage days for one or more delivery bases that the delivery will take.

For example, in the example shown in FIG. 1, delivery item B is stored in primary storage location 3b. In the future, delivery item B is delivered to secondary storage location 4b via inter-base route C2d, and after being stored in secondary storage location 4b, is delivered to handover location 5e via inter-base route C3e. In this case, the number of delivery days for inter-base route C2d is 3 days, the number of delivery days for inter-base route C3e is 2 days, and the number of storage days for the delivery item on inter-base route C3e at secondary storage location 4b is 5 days. In this case, the remaining margin calculation function can calculate the number of days required for delivery as "3 days" for inter-base route C2d + "5 days" for storage days at secondary storage location 4b + "2 days" for delivery days for inter-base route C3e = 10 days.

Then, the retention margin calculation function calculates the difference between the delivery deadline days of the delivery item and the required delivery days (delivery deadline days - required delivery days) as the retention margin days. Note that the delivery deadline days of the delivery item is not the original delivery deadline days, but the current delivery deadline days. For example, if the original delivery deadline days is 30 days and 10 days have passed since the current delivery deadline, the retention margin calculation function calculates the delivery deadline days as 20 days. Also, if the required delivery days for delivery B stored in primary storage location 3b are 10 days and the current delivery deadline days are 20 days, the retention margin calculation function calculates the delivery deadline days (20 days - required delivery days = 10 days) as the retention margin days. The number of days until the delivery deadline (initial number of days until the delivery deadline) is not particularly limited, but since the delivery management system 1 according to this embodiment is intended to meet the needs of those who wish to use a service with low delivery fees even if delivery takes a long time, the number of days until the delivery deadline is set to 3 days or more, preferably 5 days or more, and more preferably 10 days or more.

The delivery possibility judgment function of the calculation device 12 judges whether it is time to deliver the delivery item from the current delivery base N to the next delivery base N+1. Specifically, the delivery possibility judgment function first refers to the delivery means table 114 and extracts information on delivery means that can deliver the delivery item from the delivery base N to the next delivery base N+1. Then, based on the extracted information on the free space of the delivery means, the delivery possibility judgment function sets a reference capacity for judging whether the delivery item should be delivered from the current delivery base N to the next delivery base N+1. For example, the delivery possibility judgment function can set 80% of the free space (free capacity) of the delivery means as the reference capacity. In this case, if the free space of the delivery means is the free capacity for 10 delivery cases 60, the delivery possibility judgment function can set the capacity for 8 delivery cases 60 as the reference capacity. In addition, if there are multiple delivery means that can deliver the delivery item from the delivery base N to the next delivery base N+1, the delivery possibility judgment function can set a reference capacity for each delivery means based on the free space of each delivery means.

Then, when the total volume of the delivery items delivered on the inter-base route from the current delivery base N to the next delivery base N+1 exceeds a predetermined standard capacity set based on the free capacity of each delivery means, the delivery possibility judgment function allows the delivery of the delivery items on the inter-base route. For example, when delivering delivery items from the primary storage location 3b to the secondary storage location 4b, if the delivery means capable of delivering the inter-base route C2d is the truck T1 and the standard capacity set based on the free capacity of this truck T1 is the capacity of 8 delivery cases 60, the delivery possibility judgment function judges whether the delivery items delivered on the inter-base route C2d from the primary storage location 3b to the secondary storage location 4b exceed 8 delivery cases 60. Then, when the delivery items delivered on the inter-base route C2d are 9 or more delivery cases 60, the delivery possibility judgment function allows the delivery of the delivery items on the inter-base route C2d by the truck T1. On the other hand, if the number of delivery items being delivered on the base-to-base route C2d is eight or less in delivery cases 60, the delivery feasibility determination function does not permit delivery on the base-to-base route C2d by truck T1, and determines that the delivery items should be stored in the primary storage location 3d.

In this embodiment, as described later, a plurality of different sizes of delivery cases 60 are used (see FIG. 12). When a plurality of sizes of delivery cases 60 are used, the capacity of the delivery item, the free capacity of the delivery means, and the reference capacity are set with the smallest size of the delivery case 60 as a unit. For example, when a delivery item is delivered from the primary storage location 3b to the secondary storage location 4b, if the reference capacity set based on the free capacity of the delivery means capable of delivering the base-to-base route C2d is the capacity of eight pieces of the smallest size 60 delivery case 60, the delivery possibility determination function determines whether the delivery item delivered on the base-to-base route C2d from the primary storage location 3b to the secondary storage location 4b exceeds eight pieces of the size 60 delivery case 60. If the delivery item delivered on the base-to-base route C2d is nine or more pieces of the size 60 delivery case 60, the delivery possibility determination function allows the delivery of the delivery item on the base-to-base route C2d by the truck T1. In this case, if there is one size 80 delivery case 60 (details to be described later) that can hold two size 60 delivery cases 60 at the delivery base, the delivery feasibility determination function will make a delivery determination assuming that there are two size 60 delivery cases 60 at the delivery base.

In addition, when there are multiple delivery means capable of delivering one base-to-base route, the delivery possibility determination function can be configured to set a standard capacity for each delivery means based on the free capacity of each delivery means, and to permit delivery of the delivery item to the delivery means whose total capacity exceeds the standard capacity. In addition, when delivery of the delivery item is permitted for multiple delivery means, the delivery possibility determination function may permit delivery to the delivery means with the largest free capacity of the loading platform, or may permit delivery by the delivery means closest to the current delivery base N. In addition, in this embodiment, the delivery possibility determination function is configured to set a standard capacity for each delivery means by acquiring information on the free capacity of the loading platform of each delivery means in real time from the TMS server 30, but is not limited to this configuration, and for example, a configuration can be made in which free capacity for delivering the delivery item is reserved in advance for each delivery means. In this case, the standard capacity of each delivery means can be stored in advance in the delivery means table 114 based on the free capacity reserved in advance, and the delivery means permitted to deliver the delivery item can be selected by acquiring the standard capacity for each delivery means from the delivery means table 114.

In addition, the delivery possibility determination function determines whether the number of days that the delivery item can be held for is less than a predetermined standard number of days for each delivery item. If there is a delivery item whose number of days that the delivery item can be held for is less than the predetermined standard number of days, the delivery possibility determination function allows the delivery of the delivery item along the base route along which the delivery item is to be delivered. As a result, even if the total volume of the delivery items to be delivered along the base route from the current delivery base N to the next delivery base N+1 does not exceed the predetermined standard capacity set based on the available capacity of each delivery means, if there is a delivery item whose number of days that the delivery item can be held for is less than the predetermined standard number of days, the delivery possibility determination function keeps the delivery item stored at the current delivery base N for base routes along which there are no delivery items whose number of days that the delivery item can be held for is less than the predetermined standard number of days, as long as the total volume of the delivery items to be delivered along the base route from the current delivery base N to the next delivery base N+1 does not exceed the predetermined standard capacity set based on the available capacity of each delivery means.

For example, suppose that one delivery B1, among the deliveries stored in the primary storage location 3b, which is delivered via inter-base route C2d, has a dwell time of two days and a predetermined reference time of three days. In this case, the delivery feasibility determination function determines that the dwell time of two days for delivery B1 is less than the reference time of three days, and allows the delivery of not only delivery B1, but also deliveries stored in the primary storage location 3b and delivered via inter-base route C2d. The predetermined reference time can be set appropriately according to the delivery management method.

In this way, the delivery feasibility determination function determines, for each base route, whether the total volume of the delivery item exceeds the standard capacity of the delivery means (condition 1) or whether there is a delivery item whose number of available days of retention is less than a predetermined standard number of days (condition 2). If either condition is met, the delivery feasibility determination function allows the delivery item to be delivered on that base route, but if neither condition is met, it determines that the delivery item cannot be delivered on that base route, and leaves the delivery item to be delivered on that base route stored at the current delivery base N.

The delivery instruction function of the calculation device 12 issues instructions for delivering the delivery item permitted by the delivery possibility determination function. Specifically, as shown in FIG. 2, the delivery instruction function transmits a transportation instruction to the TMS server 30 via the communication device 14. When the TMS server 30 receives a transportation instruction from the delivery management server 10, it transmits a transportation instruction for the delivery item to each delivery means via the communication device 33. For example, if there is a base-to-base route where the total capacity of the delivery item exceeds the reference capacity of the delivery means, the delivery instruction function can transmit a transportation instruction to the TMS server 30 so that the delivery item is delivered to the delivery means that delivers the base-to-base route. In addition, if there is a base-to-base route where there is a delivery item whose retention allowance days are less than a predetermined reference number, the delivery instruction function can transmit a transportation instruction to the TMS server 30 so that the delivery item is delivered to the delivery means that delivers the base-to-base route. Note that, if there are multiple delivery means that can deliver the delivery item on one base-to-base route, it can also be configured to issue a transportation instruction to one delivery means based on a predetermined priority order or the like.

The delivery instruction function also transmits, via the communication device 14, to the WMS server 20, shipping instructions to the sender of the delivery and receiving instructions to the destination of the delivery. When the WMS server 20 receives a receiving instruction from the delivery management server 10, it transmits a shipping instruction for the delivery to the management terminal 41 located at the delivery base of the sender via the communication device 23. As a result, the delivery base of the sender performs shipping procedures such as sorting and loading the delivery based on the received shipping instruction. When the WMS server 20 receives a receiving instruction from the delivery management server 10, it transmits a receiving instruction for the delivery to the management terminal 41 located at the delivery base of the destination via the communication device 23. As a result, the delivery base of the destination performs receiving procedures such as securing a storage space, unloading the delivery, and storing the delivery based on the received receiving instruction.

In the shipping procedure at the shipping base of the shipping source, the RF tags 62 attached to the shipping cases 60 containing the items to be shipped are read all at once by the reading terminals 42 installed at the shipping base of the shipping source, and the identification information of the shipping cases 60 containing the items to be shipped is transmitted to the shipping management server 10 via the management terminal 41. As a result, the shipping management server 10 can identify the item to be shipped based on the received identification information of the shipping case 60, and the shipping status of the item to be shipped is updated to "moving along the next inter-base route" or the like. For example, in the example shown in FIG. 1, when item B is shipped from the primary storage location 3b to the secondary storage location 4b, the shipping status of item B is updated to "moving along the inter-base route C2d" or the like. In addition, in the receiving procedure at the shipping base of the shipping destination, the RF tags 62 attached to the shipping cases 60 containing the received deliveries are read all at once by the reading terminals 42 installed at the shipping base of the shipping destination, and the identification information of the shipping cases 60 containing the received deliveries is transmitted to the shipping management server 10 via the management terminal 41. As a result, the delivery management server 10 can identify the received deliveries based on the received identification information of the delivery cases 60, and the delivery status of the received deliveries is updated to "stored at the shipping base of the shipping destination" or the like. For example, in the example shown in FIG. 1, when delivery B is received at the secondary storage location 4b, the delivery status of delivery B is updated to "stored at the secondary storage location 4b" or the like.

Next, the WMS server 20 will be described. As shown in FIG. 2, the WMS server 20 has a calculation device 21, a storage device 22, and a communication device 23, and executes the warehouse management program stored in the storage device 22 by the calculation device 21, thereby performing the warehouse management process described below.

For example, when the conditions for delivering a delivery item are met in the delivery management server 10, the delivery management server 10 sends a shipping instruction and a receiving instruction to the WMS server 20, including information on the delivery item to be shipped, information on the delivery base of the shipper, and information on the delivery base of the destination. The WMS server 20 receives a shipping instruction from the delivery base of the shipper and a receiving instruction from the delivery base of the destination from the delivery management server 10 via the communication device 23, and sends a shipping instruction to a management terminal 41 deployed at the delivery base of the shipper, as shown in FIG. 2, and also sends a receiving instruction to a management terminal 41 deployed at the delivery base of the destination. As a result, the delivery procedure for the delivery item is carried out at the delivery base of the shipper, and the receiving procedure for the delivery item is carried out at the delivery base of the destination.

Next, the TMS server 30 will be described. As shown in FIG. 2, the TMS server 30 has a calculation device 31, a storage device 32, and a communication device 33. The TMS server 30 also executes the transportation and delivery management program stored in the storage device 32 with the calculation device 31, thereby executing the transportation and delivery management process described below.

For example, when the conditions for delivering the delivery item are met in the delivery management server 10, the delivery management server 10 transmits to the TMS server 30 delivery instructions for the delivery item, including information on the delivery item to be shipped, information on the delivery base of the shipping origin, information on the delivery base of the shipping destination, information on the route between bases for delivering the delivery item, or information on the delivery means capable of delivering the delivery item. When the TMS server 30 receives a delivery instruction from the delivery management server 10, it identifies a delivery means capable of delivering the delivery item based on the delivery instruction, and issues a delivery instruction to the delivery means so that the delivery means delivers the delivery item. In this embodiment, an information terminal is installed in the delivery means, or the driver of the delivery means has a mobile terminal, and by transmitting delivery information from the TMS server 30 to the information terminal of the delivery means or the mobile terminal of the driver, each delivery means can perform the delivery procedure (collection of the delivery item at the delivery base of the shipping origin, delivery of the delivery item on the route between bases, and handover of the delivery item at the delivery base of the shipping destination).

Next, the management terminal 41 and the reading terminal 42 according to this embodiment will be described. In the delivery management system 1, the management terminal 41 and the reading terminal 42 are provided at each of the delivery bases 2 to 5. The management terminal 41 and the reading terminal 42 are connected by wire or wirelessly, and information read by the reading terminal 42 is transmitted to the management terminal 41. The management terminal 41 is also connected to the delivery management server 10 via an electric communication line, and is capable of transmitting and receiving information to and from the delivery management server 10. For example, when the sender S brings the delivery B to the receiving location 2, the identification information (e.g., the identification number) of the delivery B is read by the reading terminal 42 at the receiving location 2 and transmitted to the management terminal 41. As a result, the management terminal 41 transmits the identification information of the delivery B and information indicating the delivery status of the delivery B, "being stored at the receiving location 2", to the delivery management server 10. As a result, the delivery status of the delivery B is updated to "being stored at the receiving location 2" in the delivery information table 111 of the delivery management server 10. The information read by the reading terminal 42 can also be configured to be sent directly to the delivery management server 10.

At the receiving location 2, the delivery item B is stored in the delivery case 60. A QR code 61 and an RF tag 62 storing the identification information of the delivery case 60 are attached to the delivery case 60, and the delivery item B can be associated with the delivery case 60. That is, the management terminal 41 can associate the identification information of the delivery case 60 storing the delivery item B stored in the QR code 61 or the RF tag 62 with the identification information of the delivery item B and transmit them to the delivery management server 10, whereby the identification information of the delivery case 60 storing the delivery item B is also stored as the delivery information of the delivery item B in the delivery information table 111. The reading terminal 42 is a device for reading the QR code 61 and/or the RF tag 62, and can read the QR code 61 and/or the RF tag 62 without contact. By setting the reading range of the reading terminal 42 to several meters, the reading terminal 42 can read the identification information of a plurality of delivery cases 60 at once. As an example of such a reading terminal 42, a reading terminal with a reading distance of 5 to 8 meters, a transmission frequency of 916.8 MHz to 922.2 MHz, and approximately 70 tags/second is disclosed. In this embodiment, a terminal capable of reading both the QR code 61 and the RF tag 62 is illustrated as an example of the reading terminal 42, but this configuration is not limited to the reading terminal 42, and a configuration using a reading terminal 42 for reading the QR code 61 and a reading terminal 42 for reading the RF tag 62 may be used. The reading terminal 42 may also be configured using a smartphone. For example, by attaching an attachment for enabling the RF tag 62 to be read to a smartphone capable of reading the QR code 61 by a camera, the smartphone can be used as the reading terminal 42 capable of reading the QR code 61 and the RF tag 62. The reading terminal 42 may be a handheld terminal device, or may be a terminal device fixed to, for example, the top of a conveyor along which the delivery case 60 is transported.

The management terminal 41 of each of the distribution bases 2 to 5 receives the receiving instruction and the shipping instruction of the delivery item from the WMS server 20. Based on the received receiving instruction and the shipping instruction, each of the distribution bases 2 to 5 performs the receiving procedure of receiving the delivery item delivered by the delivery means at the distribution base, and the shipping procedure of handing over the delivery item to the delivery means. In this embodiment, when performing the receiving procedure, the identification information of the delivery case 60 that contains the delivery item to be received is read all at once by the reading terminal 42. The management terminal 41 can sort the received delivery items by the inter-base route by receiving the delivery information of each delivery item from the delivery management server 10 based on the acquired identification information of the delivery case 60. In addition, the management terminal 41 can update the delivery status of the delivery item stored in the delivery information table 111 from, for example, "moving along the inter-base route C1f" to "kept at the distribution base 3b", by transmitting the identification information of the delivery case 60 to the delivery management server 10. Similarly, when carrying out the shipping procedure, the identification information of the delivery cases 60 that contain the delivery items to be shipped is simultaneously read by the reading terminals 42. This allows the management terminal 41 to send the identification information of the delivery cases 60 to the delivery management server 10, thereby updating the delivery status of the delivery items stored in the delivery information table 111, for example, from "stored at delivery base 3b" to "moving along inter-base route C2d," etc.

Next, the user terminal 50 according to this embodiment will be described. The user terminal 50 is an information terminal owned by the sender S and the recipient R, and may be, for example, a smartphone, a tablet, or a personal computer. The user terminal 50 can communicate with the delivery management server 10 via an electric communication line, and can transmit the delivery information of the delivery B to the delivery management server 10 by inputting the delivery information of the delivery B on the user terminal 50. The user terminal 50 can also receive a delivery receipt notification, a shipping notification to the delivery location of the delivery, or an arrival notification from the delivery management server 10. The user terminal 50 can be configured to input the delivery information of the delivery B by installing a program dedicated to delivery management processing and starting the program, and to transmit the delivery information to the delivery management server 10, or to start a web browser on the user terminal 50, and to input the delivery information of the delivery B on the web browser, and to transmit the delivery information of the delivery B to the delivery management server 10. The user terminal 50 can also have a function of paying the cost related to the delivery by the delivery management system 1 according to this embodiment.

The delivery case 60 is a dedicated packaging material for containing the delivery item B when the delivery item B is delivered, and is used repeatedly. The material of the delivery case 60 is not particularly limited, but a material that has a certain strength and is light in weight for repeated use is preferable, and for example, so-called plastic corrugated cardboard (hollow molded sheet made of resin such as polypropylene) can be used. Here, FIG. 9 is a perspective view showing an overview of the delivery case 60 according to this embodiment. As shown in FIG. 9, a QR code 61 is drawn on the outer surface of the delivery case 60, and the QR code 61 can be read by the reading terminal 42. Also, as shown in FIG. 9, an RF tag 62 is also attached to the delivery case 60, and the information stored in the RF tag 62 can be read by the reading terminal 42. When a new delivery case 60 is prepared, the QR code 61 is made a code indicating the identification information of the delivery case 60, and the identification information of the delivery case 60 is written into the RF tag 62 using a writer device dedicated to the RF tag 62. In addition, in this embodiment, the QR code 61 is drawn directly on the delivery case 60, but it is also possible to affix a sticker with the QR code 61 on it to the delivery case 60.

In addition, in this embodiment, in addition to the identification information of the delivery case 60, a writer device dedicated to the RF tag 62 can be used to write to the RF tag 62 the identification information of the base-to-base route along which the delivery will be delivered next, the passing status of the delivery base or base-to-base route, and information on the date and time of the passing status update. Examples of the passing status include "shipping inspection," "in transit," "unloaded," and "arrived." The writer device can be configured, for example, by attaching an attachment capable of writing information to the RF tag 62 to a reading terminal 42 such as a smartphone carried by an employee at the delivery base. In this way, by writing to the RF tag 62 the identification information of the base-to-base route along which the next delivery will be made, the passing status of the delivery base or base-to-base route, and the updated date and time of the passing status, even if communication between the reading terminal 42 and the management terminal 41 or between the reading terminal 42 and the delivery management server 10 is poor and the base-to-base route along which the delivery case 60 will be next delivered or the status of the delivery case 60 is unknown, this information can be obtained from the RF tag 62, and delays in logistics operations can be effectively prevented. In addition, in such a case, the writer device can transmit information about the delivery case 60 at the timing when it becomes able to communicate with the management terminal 41 or the delivery management server 10, thereby updating the information about the delivery case 60 in the delivery management server 10.

In this embodiment, the identification information of the delivery case 60 is stored in the QR code 61 and the RF tag 62, and the reading terminal 42 can obtain the identification information of the delivery case 60 by reading the QR code 61 or the RF tag 62. Therefore, by storing delivery item B in the delivery case 60, it becomes possible to identify delivery item B by the delivery case 60. The identification information of the delivery case 60 read by the reading terminal 42 is transmitted to the delivery management server 10 via the management terminal 41 and stored in the delivery information table 111 in association with the delivery information of delivery item B stored in the delivery case 60. In addition, the case management table 115 stores the delivery information of delivery item B corresponding to the identification information of the delivery case 60.

Also, FIG. 10 is a cross-sectional view taken along line X-X in FIG. 9, where (A) shows the state in which the cushioning material 63 is not inflated, and (B) shows the state in which the cushioning material 63 is inflated after the delivery item B is placed in the delivery case 60. As shown in FIG. 10(A), the delivery case 60 has a plurality of cushioning materials 63 attached to its inner wall surface, and each cushioning material 63 is spatially connected to the adjacent cushioning materials 63. In this embodiment, an air valve 64 provided on the wall of the delivery case 60 is connected to one of the plurality of cushioning materials 63, and by opening this air valve 64 and introducing air from the outside into the cushioning material 63, all of the cushioning materials 63 can be inflated with air through the air valve 64 as shown in FIG. 10(B). This makes it possible to inflate the cushioning material 63 to match the shape of the delivery item B, as shown in FIG. 10(B), and the delivery item B can be appropriately protected. Similarly, by opening the air valve 64 and discharging the air inside the cushioning material 63 to the outside, the air inside the cushioning material 63 can be discharged to the outside, and the cushioning material 63 can be put into an uninflated state, as shown in FIG. 10(A).

In this embodiment, two or more types of cases having different sizes are used as the delivery case 10. Fig. 11 illustrates a scene in which a small delivery case 60 ₂ is accommodated in a large delivery case 60 _1. As shown in Fig. 11, the accommodation size of the large delivery case 60 ₁ is slightly larger than the size of two small delivery cases 60 ₂ , and by injecting air into the cushioning material 63 through the air valve 64 with two small delivery cases 60 ₂ accommodated, the small delivery case 60 ₂ can be fixed within the large delivery case 60 ₁ .

Also, FIG. 12 is a diagram showing an example of the size variations of the delivery case 60 according to this embodiment. In this embodiment, the smallest size delivery case 60 has a total height, width, and depth of about 60 cm (size 60), and a size 80 delivery case that can hold two size 60 delivery cases 60, a size 100 delivery case that can hold four size 60 delivery cases 60, and a size 120 delivery case that can hold eight size 60 delivery cases 60 can be used. Also, the size of the delivery case 60 is not limited to that shown in FIG. 12, and for example, a size 140 delivery case that can hold 16 size 60 delivery cases 60, a size 160 delivery case that can hold 24 size 60 delivery cases 60, and the like can also be used. In the above variations, the capacity of the delivery case 60 can be 7.6 L for size 60, 15.2 L for size 80, 30 L for size 100, 60 L for size 120, 120 L for size 140, and 180 L for size 160. In the example shown in FIG. 12, a delivery case 60 of size 60 is illustrated as the smallest size, but this is not limited to this. For example, a delivery case 60 of a size less than size 60 (for example, size 40 with a total height, width, and depth of 40 cm) or a size larger than size 60 (for example, size 80) can also be used as the smallest size. However, in order to improve the loading rate of the delivery means, it is preferable to design the size of the delivery case 60 to be the same as the size shown in FIG. 12.

When storing the delivery case 60 in a larger delivery case 60, as shown in FIG. 12, the delivery case 60 may be stored in a delivery case 60 of one size larger, such as storing two 60-size delivery cases 60 in an 80-size delivery case, two 80-size delivery cases 60 in a 100-size delivery case, or two 100-size delivery cases 60 in a 120-size delivery case, or the delivery case 60 may be stored in a delivery case 60 of two or more sizes larger, such as storing four 60-size delivery cases 60 in a 100-size delivery case.

In this embodiment, in principle, a delivery item that can be put into a 60-size delivery case 60 is delivered in the 60-size delivery case 60, and a delivery item that cannot be accommodated in the 60-size delivery case 60 is accommodated in the delivery case 60 with the smallest capacity that can accommodate the delivery item. In addition, in this embodiment, an upper limit value for the weight of the delivery item that can be accommodated is set for each delivery case 60. For example, 2 kg for a 60-size delivery case 60, 5 kg for an 80-size delivery case 60, and 10 kg for a 100-size delivery case 60. As a result, even if a delivery item has a capacity that can be accommodated in a 60-size delivery case 60, if its weight is 3 kg, it will exceed the weight upper limit value of the 60-size delivery case 60, so the delivery item will be accommodated in the 80-size delivery case 60. By setting an upper limit value for the weight of the delivery item that can be accommodated for each size of the delivery case 60 in this way, it is possible to effectively prevent the delivery means that transports the delivery item from being overloaded.

In this embodiment, in the sorting procedure at each of the distribution bases 2 to 4, multiple deliveries delivered via the same inter-base route are consolidated into one delivery case 60. By consolidating deliveries delivered via the same inter-base route in a large delivery case _60-1 as shown in FIG. 11, the work of sorting during shipping and receiving procedures can be reduced. For example, as shown in FIG. 7, there is a delivery item contained in a delivery case _60-2 with an identification number "xxx601" and a delivery item contained in a delivery case _60-2 with an identification number "xxx602", and as a result of acquiring delivery information based on the identification numbers of these deliveries, if these deliveries are in the same primary storage location 3b and are delivered via the same inter-base route C2d, the 60-size delivery case _60-2 that contains these deliveries can be accommodated in a delivery case _60-1 with an identification number "xxx604", which is one size larger (80 size). The delivery management server 10 may be configured to have a function of searching for delivery cases 60 ₂ that can be accommodated in the same delivery case 60 ₁ and sending the search results to the management terminal 41 of each of the delivery bases 2 to 4. This makes it possible to easily sort deliveries for each inter-base route at each of the delivery bases 2 to 4.

Also, for example, in the example shown in FIG. 1, deliveries that are delivered from the primary storage location 3b to the secondary storage location 4b, but are then delivered to different delivery bases such as delivery locations 5d and 5e, can be stored in the same large delivery case 60 ₁ at the primary storage location 3b. In this case, by reading the RF tags 62 of the large delivery case 60 ₁ and the small delivery case 60 ₂ contained therein at the secondary storage location 4b, it is possible to know that the large delivery case 60 ₁ contains deliveries for the two inter-base routes C3d and C3e, and the small delivery case 60 ₂ can be taken out from the large delivery case 60 ₁ and delivered to each of the delivery locations 5d and 5e. As a result, for example, deliveries within the same prefecture or neighboring areas such as neighboring prefectures are delivered in a relatively small delivery case 60 (for example, an inner case), and deliveries are delivered in a relatively large delivery case 60 (for example, an outer case) when delivering to a trunk line such as distant prefectures.

The delivery case 60 according to the present embodiment has both the QR code 61 and the RF tag 62, and thus can solve the following problem. That is, in the present embodiment, a large delivery case 60 ₁ contains a plurality of small delivery cases 60 ₂ containing deliveries to be delivered along the same base-to-base route, and deliveries are performed. However, during the receiving procedure, due to human error or the like, deliveries to be delivered along different base-to-base routes may be contained in the same large delivery case 60 _1. In order to prevent such an error, before the delivery of the deliveries, the RF tags 62 of the delivery cases 60 ₁ and 60 ₂ are read simultaneously in a non-contact manner by the reading terminal 42 in a state in which the small delivery cases 60 ₂ are contained in the large delivery case 60 ₁ , and it is possible to check whether deliveries to be delivered along different base-to-base routes are contained in the same large delivery case 60 ₁ . In other words, by reading the RF tags 62 all at once with the reading terminal 42, it is possible to read the identification information of the small delivery cases ₆₀₂ contained in the large delivery case ₆₀₁ without removing the small delivery cases ₆₀₂ from the large delivery case 601, making it easy to check whether deliveries delivered via different base route are contained in the _same large delivery case ₆₀₁ .

On the other hand, since the RF tag 62 can be read at a distance of several centimeters to several dozen meters, for example, when a delivery case 60 containing a delivery item to be delivered via a certain base-to-base route is placed near a delivery case 60 containing a delivery item to be delivered via another base-to-base route, it may not be possible to properly perform procedures that require correct identification of the delivery item (such as managing the delivery status by receiving and shipping each delivery item or loading and unloading each delivery item). In such cases, the QR code 61 affixed to the outer surface of the delivery case 60 can be read to individually identify the target delivery item. In this way, in this embodiment, by having both the QR code 61 and the RF tag 62, the QR code 61 and the RF tag 62 can be used depending on the type of delivery procedure (whether it is a procedure that can be identified all at once or a procedure that must be identified individually), making it possible to perform efficient delivery processing.

Next, the delivery management process of the delivery management system 1 according to this embodiment will be described with reference to Figs. 13 and 14. Fig. 13 is a flowchart showing the delivery receipt process, and Fig. 14 is a flowchart showing the delivery management process. The receipt process shown in Fig. 13 is executed when delivery B is received at the receipt location 2. The delivery management process shown in Fig. 14 is for determining whether or not the delivery can be delivered at each of the delivery bases 2 to 4, and a determination is made at regular intervals as to whether or not the delivery can be delivered for each inter-base route.

First, the receiving process shown in FIG. 12 will be described. In step S101, the delivery information of the delivery item B is input by the user terminal 50. For example, the sender S can input the delivery information required for the delivery of the delivery item B from the user terminal 50 by installing a dedicated program in advance in the user terminal 50 and starting the dedicated program. The delivery information input at the user terminal 50 includes the identification number of the delivery item, the receiving location 2, the delivery location 5, the name and contact information of the sender S, the name and contact information of the recipient R, etc. In addition, the management terminal 41 inputs delivery information such as the weight and size of the delivery item (how many items in the smallest delivery case 60 unit) based on the information of the delivery case 60 in which the delivery item is stored. The input delivery information of the delivery item B is transmitted to the delivery management server 10 via an electric communication line and stored in the delivery information table 111 of the database 11. In this embodiment, in order to expedite the receipt process of delivery B at the receiving location 2, an identification number for delivery B is stored in the user terminal 50 to identify the delivery information for delivery B stored in the delivery management server 10. After the delivery information for delivery B is registered in the database 11, the delivery person S brings delivery B to the nearest receiving location 2, and the process proceeds to step S102.

In step S102, the reading terminal 42 at the receiving location 2 reads the delivery information of the delivery item B. For example, in this embodiment, the identification information of the delivery item B is stored in the user terminal 50 of the sender S, and the identification information of the delivery item can be displayed on the display of the user terminal 50 in the form of, for example, a QR code. In this case, the reading terminal 42 obtains the identification information of the delivery item B by scanning the QR code displayed on the display of the user terminal 50, and transmits it to the management terminal 41. The management terminal 41 can obtain the delivery information of the delivery item based on the identification information of the delivery item B by accessing the delivery management server 10. In addition, at the receiving location 2, a delivery case 60 that will accommodate the delivery item is determined based on the weight and size of the delivery item. Specifically, the smallest size delivery case 60 among the delivery cases 60 that has a capacity that can accommodate the delivery item and whose weight does not exceed the upper weight limit is determined as the delivery case 60 corresponding to the delivery item. As a result, the management terminal 41 transmits identification information of the delivery case 60 that contains the delivery item to the delivery management server 10, and the delivery management server 10 stores delivery information such as the weight and size of the delivery item (how many items fit into the smallest delivery case 60 unit) in the delivery information table 111 based on the size of the delivery case 60.

In step S103, the delivery information registration function of the delivery management server 10 associates the identification information of the delivery item B with the identification information of the delivery case 60 that contains the delivery item B. The delivery case 60 has a QR code 61 attached thereto, and the management terminal 41 can obtain the identification information of the delivery case 60 by reading the QR code 61 attached to the delivery case 60 that contains the delivery item B using the reading terminal 42. The management terminal 41 then associates the identification information of the delivery item acquired in step S102 with the identification information of the delivery case 60 acquired in step S103, and transmits them to the delivery management server 10. As a result, the delivery management server 10 associates the delivery information of the delivery item B with the identification information of the delivery case 60 that contains the delivery item B, and stores them in the delivery information table 111 and the case management table 115. In the next step S104, the delivery management server 10 updates the delivery status of the delivery item in the delivery information table 111 to "In storage at receiving location 2."

The receiving process according to this embodiment is carried out as described above. Next, the delivery management process according to this embodiment will be described with reference to FIG. 14.

First, in step S201, the delivery feasibility determination function of the delivery management server 10 calculates the total volume of deliveries for each delivery base and each inter-base route. For example, the delivery feasibility determination function identifies the inter-base route when delivering deliveries managed at each delivery base N to the next delivery base N+1 based on the delivery information of each delivery item stored in the delivery information table 111. The delivery feasibility determination function then classifies the deliveries by inter-base route, and calculates the total volume of deliveries for each inter-base route based on the delivery information of each delivery item.

In the following steps S202 to S205, the delivery management server 10 uses its function of calculating the number of days that the delivery can be left for each delivery to calculate the number of days that the delivery can be left for each delivery. Therefore, in steps S202 to S205, each process is performed for each delivery.

Specifically, in step S202, the delay margin calculation function calculates the total number of delivery days for each delivery item along each inter-base route. For example, the delay margin calculation function identifies the delivery route of each delivery item (the inter-base route and delivery item along which the delivery item passes from the current delivery base to the delivery location) based on the delivery information of each delivery item. The delay margin calculation function then refers to the inter-base route delivery days table 112 stored in database 11, and calculates, for each delivery item, the total number of delivery days for all inter-base routes along which the delivery item passes from the current delivery base to the delivery location 5.

In step S203, the remaining days of storage calculation function calculates the total number of days of storage at each distribution center for each delivery item. For example, the remaining days of storage calculation function refers to the storage days by distribution center table 113 stored in database 11, and calculates for each delivery item the total number of days of storage at all distribution centers that each delivery item passes through on its way from the current distribution center to delivery location 5.

In step S204, the number of days required for delivery of each delivery item is calculated by the residual margin calculation function. Specifically, the residual margin calculation function calculates the number of days required for delivery for each delivery item by adding the total number of delivery days along the routes between bases calculated in step S202 and the total number of storage days at each delivery base calculated in step S203.

In step S205, the remaining margin days calculation function calculates the remaining margin days for each delivery item. Specifically, the remaining margin days calculation function first obtains the delivery deadline days for each delivery item. The delivery deadline days may be stored, for example, in a dedicated table, or may be stored as delivery information in the delivery information table 111. The remaining margin days calculation function then calculates the difference between the delivery deadline days for each delivery item and the number of days required for delivery of each delivery item calculated in step S204 as the remaining margin days for each delivery item.

Next, in steps S206 to S211, processing is performed for each inter-site route. In the following, the inter-site route for which processing is performed will be referred to as the target inter-site route.

First, in step S206, the delivery possibility judgment function of the delivery management server 10 judges whether the total volume of the delivery items on the target base route calculated in step S201 exceeds a predetermined standard capacity set based on the free capacity of the delivery means. For example, in this embodiment, the delivery possibility judgment function refers to the delivery means table 114 to identify delivery means that can deliver on the target base route. In addition, the delivery possibility judgment function sets a standard capacity (for example, 80% of the free capacity of the loading space of the delivery means) for each delivery means that can deliver on the target base route based on the information on the free capacity of each delivery means stored in the delivery means table 114. Then, if the total volume of the delivery items on the target base route exceeds the set predetermined standard capacity, the delivery possibility judgment function allows the delivery of the delivery items on the target base route. Note that if there are multiple delivery means for the target base route and only the standard capacity set based on the free capacity of some of the delivery means is exceeded, delivery by only those some of the delivery means may be allowed. If the delivery of the delivery items is permitted by the delivery possibility judgment function, the process proceeds to step S208. On the other hand, if the total volume of deliveries on the route between the target bases is equal to or less than the predetermined standard volume, processing proceeds to step S207.

In step S207, the delivery feasibility determination function determines whether or not there is a delivery on the target base route whose remaining detention days calculated in step S205 are less than the predetermined reference number of days. If there is a delivery on the target base route whose remaining detention days are less than the predetermined reference number of days, the process proceeds to step S208 to deliver the delivery on the target base route. On the other hand, if there is no delivery on the target base route whose remaining detention days are less than the predetermined reference number of days, the process proceeds to step S211.

In step S208, the delivery instruction function of the delivery management server 10 issues a transportation delivery instruction for the delivery item along the route between the target bases. Specifically, the delivery instruction function sends a transportation delivery instruction to the TMS server 30 to deliver the delivery item along the route between the target bases. This causes the TMS server 30 to select a delivery means for delivering the delivery item and send a transportation delivery instruction for the delivery item to the selected delivery means. As a result, the delivery means delivers the delivery item along the route between the target bases.

In addition, in steps S209 and S210, the delivery instruction function transmits to the WMS server 20 the receipt instruction and the shipping instruction of the delivery item along the target base route. The WMS server 20 transmits the shipping instruction of the delivery item along the target base route to the management terminal 41 arranged at the delivery base of the shipper, and the shipping procedure of the delivery item along the target base route is carried out at the delivery base of the shipper. In addition, the WMS server 20 transmits the receipt instruction of the delivery item along the target base route to the management terminal 41 arranged at the delivery base of the destination, and the receiving procedure of the delivery item along the target base route is carried out at the delivery base of the destination. After that, the process proceeds to step S211. In addition, in the shipping procedure, the delivery items to be delivered along the same base route may be collected together and stored in a large delivery case _60-1 as shown in FIG. 11. In addition, when a delivery item that has been delivered along the same base-to-base route is later delivered along a different base-to-base route, the multiple delivery items stored in the large delivery case ₆₀₁ can be removed from the large delivery case ₆₀₁ and shipped separately according to the respective base-to-base routes.

In step S211, the delivery feasibility determination function determines whether steps S206 to S210 have been performed for all inter-base routes. If steps S206 to S210 have not been performed for all inter-base routes, the inter-base route for which no processing has been performed is treated as the target inter-base route and steps S206 to S210 are performed. If steps S206 to S210 have been performed for all inter-base routes, the process returns to step S201 and the process is repeated from step S201.

As described above, the delivery management system 1 according to the present embodiment delivers the delivery item B by storing it in the delivery case 60. The delivery case 60 has an identifier (QR code 61 or RF tag 62) for identifying the delivery case 60, and by associating the identification information of the delivery case 60 with the identification information of the delivery item B, the delivery item B can be managed using the delivery case 60. In addition, by managing the delivery item B using the delivery case 60, even when deliveries of various shapes are delivered, it is possible to store them in a delivery case 60 of a certain standard, and the loading rate of the delivery means can be improved, so that the delivery cost can be reduced accordingly. In addition, in the delivery management system 1 according to the present embodiment, multiple small delivery cases 60 ₂ that store deliveries delivered on the same base route can be stored in the same large delivery case 60 ₁ , so that the effort of sorting and the like can be reduced in the subsequent delivery process. In addition, the delivery case 60 according to this embodiment is available in a plurality of types of delivery cases 60 with different sizes (same size), and a small delivery case 60 ₂ can be accommodated in a large delivery case 60 ₁ with little space between them. This can further improve the loading rate of the delivery means.

In addition, in the delivery management system 1 according to this embodiment, the delivery case 60 has a QR code 61, which is an identifier that can identify the delivery case 60 individually, and an RF tag 62, which is an identifier that can identify all the delivery cases 60 at once. As a result, in the delivery management system 1 according to this embodiment, depending on whether the procedure during shipping or receiving procedures allows all the delivery cases to be identified at once (for example, a bulk check of deliveries) or whether the delivery cases must be identified individually (for example, management of the delivery status by entering and leaving the warehouse or loading and unloading each delivery item), sorting procedures can be performed by using the QR code 61 and the RF tag 62 appropriately, making it possible to carry out efficient delivery processing.

Furthermore, the delivery management system 1 according to this embodiment has multiple cushioning materials 63 on the inner wall surface, and by introducing air into the cushioning materials 63 to inflate them, the shape of the cushioning materials 63 can be changed to match the shape of the delivery item B, thereby providing appropriate protection for the delivery item B. Furthermore, the delivery management system 1 according to this embodiment can count the number of times the delivery case 60 has been used, and when the number of times the delivery case 60 has been used reaches or exceeds a predetermined number of times, an instruction can be sent to the management terminal 41 to replace or discard the delivery case 60. In this way, the delivery case 60 can also be appropriately managed.

In addition, the delivery management system 1 according to this embodiment judges whether the total volume of the delivery items for each base route connecting each delivery base exceeds a predetermined standard volume determined based on the free capacity of the delivery means, and instructs the delivery of the delivery items on the base route where the total volume of the delivery items exceeds the predetermined standard volume. As a result, the delivery management system 1 according to this embodiment can increase the loading rate of the delivery means on the base route, and can reduce the delivery fee. That is, in conventional delivery management systems, the delivery period is set relatively short (for example, about 2 to 3 days), and in order to comply with the delivery period, the delivery items are delivered even if the loading rate of the delivery means is low. Therefore, conventionally, the delivery period is short but the delivery fee is expensive, and it has not been possible to meet the needs of those who want to use a service with a low delivery fee even if it takes several days to deliver. In contrast, the delivery management system 1 according to this embodiment stores deliveries at delivery bases until the total volume of deliveries for each base route exceeds a predetermined standard capacity determined based on the free capacity of the delivery means, and when the total volume of deliveries for each base route exceeds the predetermined standard capacity, delivery is instructed, thereby increasing the loading rate of the delivery means and meeting the needs of those who want to use a service with low delivery fees even if delivery takes several days.

Furthermore, the delivery management system 1 according to this embodiment determines for each base route whether there is a delivery whose number of available days to stay is less than a predetermined standard number of days, and for a base route where there is a delivery whose number of available days to stay is less than the predetermined standard number of days, delivery of the delivery is permitted on that base route even if the total volume of the delivery does not exceed the predetermined standard volume. This makes it possible for the delivery management system 1 according to this embodiment to effectively prevent a delivery from being delivered beyond the initially set delivery deadline.

The above describes preferred embodiments of the present invention, but the technical scope of the present invention is not limited to the above description of the embodiments. Various modifications and improvements can be made to the above embodiments, and such modifications or improvements are also included in the technical scope of the present invention.

For example, in the above embodiment, the delivery items are stored at the delivery base N until the total volume of the delivery items to be delivered from each delivery base N to the next delivery base N+1 exceeds a predetermined standard volume, and when the total volume of the delivery items exceeds the predetermined standard volume, delivery of the delivery items from the delivery base N to the next delivery base N+1 is permitted. However, the present invention is not limited to this configuration, and the delivery items may be stored at the delivery base N until the total weight of the delivery items to be delivered from each delivery base N to the next delivery base N+1 exceeds a predetermined standard weight, and when the total weight of the delivery items exceeds the predetermined standard weight, delivery of the delivery items from the delivery base N to the next delivery base N+1 is permitted. Furthermore, for each inter-base route connecting the delivery base N and the next delivery base N+1, it may be determined whether the total weight of the delivery items exceeds a predetermined standard weight, and when the total weight of the delivery items on the inter-base route exceeds the predetermined standard weight, delivery of the delivery items on the inter-base route is permitted.

In the example shown in FIG. 1, a configuration is exemplified in which it is determined whether or not a delivery item may be delivered only when the delivery is made from the primary storage location 3 to the secondary storage location 4, but this configuration is not limited to this. For example, when delivering from the receiving location 2 to the primary storage location 3, or when delivering from the secondary storage location 4 to the handover location 5, it is possible to determine whether the total volume of the delivery items exceeds a predetermined standard volume (such as 80% of the free space in the truck's loading compartment) based on the free space of the delivery means such as a truck (Condition 1), or whether there is a delivery item whose retention allowance, which is the difference between the delivery deadline days of the delivery item and the number of days required for delivery, is less than a predetermined standard number of days (Condition 2), and if either of the conditions is met, the delivery item is delivered to the next delivery base.

Furthermore, in the above-described embodiment, the delivery management server 10 transmits the base-to-base route by which the delivery item can be delivered to the TMS server 30, and the TMS server 30 identifies the delivery means for delivering the delivery item along the base-to-base route and issues a transportation delivery instruction to the delivery means. However, this configuration is not limited to this. For example, the delivery management server 10 may refer to the delivery means table 114, identify the delivery means for delivering the delivery item along the base-to-base route, and include the base-to-base route and the delivery means in the transportation delivery instruction and send it to the TMS server 30, and the TMS server 30 may issue a transportation delivery instruction to the delivery means included in the received transportation delivery instruction.

In the above-described embodiment, the delivery management server 10 is configured to be independent of the WMS server 20 and the TMS server 30, but the WMS server 20 may have the functions of the delivery management server 10, or the TMS server 30 may have the functions of the delivery management server 10. The WMS server 20 and the TMS server may be configured to be integrated, or the delivery management server 10, the WMS server 20, and the TMS server may be configured to be integrated.

In addition, in the above-described embodiment, for example, when delivering items from a delivery base N, the delivery items are sorted for each inter-base route Cn from the delivery base N to the next delivery base N+1, and for each inter-base route Cn, it is determined whether the above-described condition 1 or condition 2 is satisfied. However, this configuration is not limited to this, and for example, at the delivery base N, the delivery items may be sorted for each inter-base route Cn+1 from the next delivery base N+1 to the next delivery base N+2, and it may be determined for each inter-base route Cn+1 whether the above-described condition 1 or condition 2 is satisfied.

Furthermore, in the above-described embodiment, as shown in FIG. 10, a configuration having one air valve 64 on the wall of the delivery case 60 is exemplified, but this configuration is not limited thereto, and for example, a configuration having two or more air valves 64 is also possible.

In the above embodiment, the configuration in which the number of days to wait is calculated in days has been exemplified, but the number of days to wait can be calculated in hours. That is, in the present invention, the "time to wait" can include the number of days to wait. When the time to wait is calculated in hours, the database 11 stores a delivery time table 112 for each base route that stores the delivery time for each base route C1 to C3, and a storage time table 113 for each distribution base that acquires the storage time of the delivery item for each of the distribution bases 2 to 4 and the inter-base routes C1 to C3. The number of days to wait calculation function (time to wait calculation function) acquires the delivery time for each of the inter-base routes C1 to C3 from the delivery time table 112 for each base route, and acquires the storage time of the delivery item for each of the distribution bases 2 to 4 and the inter-base routes C1 to C3 from the storage time table 113 for each distribution base. Then, for each delivery B, the required delivery time is calculated as the sum of the delivery time on one or more inter-base routes that the delivery B takes from the delivery base where it is currently stored to the delivery location 5 plus the total storage time at one or more delivery bases that the delivery B takes. Then, the difference between the preset delivery deadline and the required delivery time (delivery deadline - required delivery time) is calculated as the waiting time. The delivery feasibility determination function determines for each delivery whether the waiting time of the delivery is less than a predetermined reference time, and if there is a delivery whose waiting time is less than the predetermined reference time, it can permit delivery of the delivery along the inter-base route along which the delivery B is delivered.

In addition, in the above-described embodiment, the delivery case 60 is configured to be used to store and deliver items for delivery, but the present invention is not limited to this configuration, and can also be configured to be used for inventory management of parts and the like in a warehouse. This makes it possible to perform inventory management of parts and the like in association with the delivery case 60 by reading the identification information of the delivery case from the QR code 61 or RF tag 62 of the delivery case 60.

LIST OF SYMBOLS 1...Delivery management system 10...Delivery management server 11...Database 12...Calculation device 13...Storage device 14...Communication device 20...WMS server 21...Calculation device 22...Storage device 23...Communication device 30...TMS server 31...Calculation device 32...Storage device 33...Communication device 41...Management terminal 42...Reading terminal 50...User terminal 60...Delivery case 61...QR code 62...RF tag 63...Cushioning material 64...Air valve 2...Receiving location 3...Primary storage location 4...Secondary storage location 5...Delivery location S...Sender R...Recipient B...Delivery item

Claims (7)

a shipping case consisting of an inner case and an outer case;
A server that manages the delivery cases;
The shipping case comprises:
Each of the inner case and the outer case has a first identifier capable of optically reading information and a second identifier capable of wirelessly reading information;
The first identifier includes case identification information for managing each case;
the second identifier includes case identification information for managing each case and baggage identification information for managing each baggage,
The server manages size, usage status and delivery information of each case in association with the case identification information;
The delivery information includes information on a delivery location and a delivery route to a next delivery base,
the server manages a parent-child relationship between the inner case and the outer case based on information of a delivery route to the next delivery base ,
The server is a delivery management system that includes a means for issuing delivery instructions to place multiple inner cases with different delivery locations in the same outer case and deliver them to the next delivery base when the multiple inner cases have the same delivery route to the next delivery base. The delivery management system of claim 1, wherein the case usage status includes information on parent case, child case, and unused case. a means for managing the number of times each case is used in association with the case identification information in the server;
3. The delivery management system according to claim 1, further comprising: means for sending an alert to a specific terminal when the number of times each case has been used exceeds a predetermined number of times. a first reading terminal that reads the first identifier and transmits it to the server;
a second reading terminal that reads the second identifier and transmits it to the server;
The second reading terminal can simultaneously read second identifiers of a plurality of contained inner cases without unpacking the outer case,
A delivery management system according to any one of claims 1 to 3, wherein the server is provided with a means for checking consistency between the delivery information of the contained inner case and the delivery information of the outer case that contains the inner case based on information on the second identifier of the inner case received from the second reading terminal. The first reading terminal and/or the second reading terminal has a means for transmitting location information to the server;
A means for managing the location information received from the first reading terminal and/or the second reading terminal in association with the case identification information;
The delivery management system according to claim 4, further comprising: a means for transmitting, when an external terminal inquires about the location information of the delivery case, the inquired location information of the delivery case to the external terminal. the second identifier is a rewritable medium;
a writer terminal capable of rewriting information recorded in the second identifier,
6. The delivery management system according to claim 4, wherein, when the second reading terminal is unable to communicate with the server, the second reading terminal waits for recovery of communication with the server and transmits the read information of the second identifier to the server. A delivery management system according to any one of claims 4 to 6, wherein the first reading terminal and the second reading terminal are configured as a smartphone or a tablet.