Delivery system with point return

Abstract

To provide a delivery system for reducing the number of packages between bases to improve efficiency of long-distance transportation, and at the same time effectively reducing re-delivery in individual deliveries beyond an arrival base.SOLUTION: Provided is a delivery system that includes a shared transportation mode in which a plurality of packages are consigned and delivered in a common package box between a departure base and an arrival base. A server 3 comprises: a delivery management unit 301 for receiving delivery requests and managing all or a part of steps from shipping to receiving of packages with matching delivery destinations and dates and times; and a point management unit 312 for managing points to be given to a person who cooperates in delivery beyond the arrival base. The point management unit has a consignee point unit XPb and a delivery person point unit XPc, and gives points for receipt cooperation and / or points for delivery burden to the consignee point unit XPb and / or the delivery person point unit XPc depending on a delivery state from the arrival base to a consignee, which is a part of management information of the delivery management unit 301 (delivery data management unit 311).SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a delivery system with point redemption. [Background technology]

[0002] In recent years, the 2024 problem is fast approaching. The 2024 problem is a problem in the logistics and transportation industry where the Working Style Reform Act sets an upper limit on overtime work for truck drivers, shortening the driving distance per person and making it impossible to transport goods over long distances, which is becoming a reality, leading to a delay in logistics. Patent Document 1 is not directly related to the present invention, but is similar in that it proposes measures to deal with the 2024 problem (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2023-102300 A Summary of the Invention [Problem to be solved by the invention]

[0004] The inventor has focused on long-distance transportation, which is the biggest burden in the 2024 problem, and has recently proposed the use of so-called "carpooling," in which multiple packages with the same destination and schedule are packaged together in a large box between bases. This would reduce the actual number of packages handled between bases, and could be an effective solution to the 2024 problem related to long-distance transportation.

[0005] However, by dispersing the delivered packages, the number of packages returns to the original number, and the fact remains that each package must be delivered individually. If redelivery is required at this time, the burden on the delivery person increases, so it is important to increase the incentive for the recipient to receive and pick up the package for the first time.

[0006] The present invention has been made in consideration of these problems, and its purpose is to solve the above problems by adopting a new system that reduces long-distance freight charges by using carpooling and encourages initial receipt of deliveries at the individual delivery stage, thereby reducing the rate of redelivery of individual deliveries and rewarding the efforts of redelivery workers. [Means for solving the problem]

[0007] In order to achieve the above object, the present invention provides the following means.

[0008] In other words, the delivery system with point redemption of the present invention adopts a shared transportation method in which multiple packages are mixed together and delivered in a common package box between a departure point and an arrival point, and is equipped with a delivery management unit that accepts delivery requests and manages all or part of the process from shipping to receiving of packages with matching delivery destinations and dates and times, and a point management unit that manages points to be awarded to those who cooperate in delivery beyond the arrival point, and is characterized in that the point management unit has a consignee point unit and a delivery person point unit, and awards points for receipt cooperation and / or points for delivery burden to the consignee point unit and / or delivery person point unit depending on the delivery status from the arrival point to the consignee, which is part of the management information of the delivery management unit.

[0009] As mentioned above, reducing the number of packages between bases by sharing is extremely useful in preparing for the 2024 pandemic. However, if the packages that arrive are separated, the number of packages will return to the individual delivery stage, so it is important to make deliveries as efficiently as possible. The present invention increases the incentive to cooperate in delivery by giving points to recipients who cooperate in delivery, while rewarding the efforts of redelivery by transferring points to the delivery person if the redelivery burden increases. Moreover, by reducing the number of packages between bases by sharing, the unit price per package can be reduced while still providing a surplus, so the operating costs of the point redemption system can be reasonably secured.

[0010] An effective aspect is to award points related to delivery cooperation to the recipient's points section when the package is received for the first time, and to transfer and award points related to delivery burden to the delivery person's points section in the case of redelivery.

[0011] In order to award points in stages, it is preferable to award the full amount of points to the consignee point section as points related to delivery cooperation upon first receipt of the consignment, and after the specified number of redeliveries, transfer and award the full amount of points to the delivery person point section as points related to delivery burden, and from the second receipt of the consignment until the specified number of redeliveries, allocate the points and award them to the recipient point section and the delivery person point section.

[0012] In the case of pick-up, it is preferable to give points equivalent to the initial receiving points to the recipient's points section as cooperation points.

[0013] It is preferable that the points be managed in a separate system from the basic fee system required for the delivery management department to receive delivery requests and manage the process from shipment to receipt.

[0014] In this case, it is appropriate that the consignee points and delivery person points managed by the point management unit are transmitted to another point management server that executes point usage. In order to increase the success rate of shared delivery, it is preferable that a plurality of sizes of the same package be defined in advance and a delivery request be made by selecting the size.

[0015] In order to increase the success rate of ride-sharing, it is preferable to accept delivery requests until the number of packages is met through matching, or until a predetermined period of time has elapsed since the start of acceptance, whichever comes first.

[0016] In order to ensure reliable individual delivery of packages, it is preferable to carry out a delivery date and time communication step in which the arrival point and the consignee agree and share the receipt date and time, and then use that agreed date and time as the base point for delivery management and point management related to the individual delivery.

[0017] The present invention can be effectively used even in cases where carpooling is not a prerequisite.

[0018] For example, a delivery system with point redemption can be mentioned, which comprises a delivery management unit that receives delivery requests and manages delivery destinations and dates and times, and a point management unit that manages points to be awarded to those who cooperate with delivery, and the point management unit has a recipient point unit and a delivery person point unit, and depending on the delivery status, which is part of the management information of the delivery management unit, awards points for receipt cooperation and / or points for delivery burdens to the recipient point unit and / or the delivery person point unit.

[0019] Even if one focuses only on individual deliveries, the point redemption system of the present invention can be effectively utilized to reduce redelivery.

[0020] In this case, too, it is preferable that points related to delivery cooperation be awarded to the consignee's points section when the consignment is received for the first time, and that in the case of redelivery, points related to the delivery burden be transferred and awarded to the deliverer.

[0021] It is also preferable that, upon first receipt of the consignment, the full amount of points is awarded to the consignee point section as points related to delivery cooperation, and after the specified number of redeliveries, the full amount of points is transferred and awarded to the delivery person point section as points related to delivery burden, and from the second receipt of the consignment until the specified number of redeliveries, points are allocated and awarded to the recipient point section and the delivery person point section.

[0022] In the case of pick-up, it is preferable to give points equivalent to the initial receiving points to the recipient's points section as cooperation points. Effect of the Invention

[0023] According to the present invention, it is possible to provide a new and useful delivery system with point redemption, which reduces the number of packages between bases to improve the efficiency of long-distance transportation, and in individual delivery from the arrival base, increases the first-time acceptance rate through a point redemption system and rewards the efforts of delivery personnel who make redeliveries. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 is a diagram for explaining an overview of a delivery system of the present invention. [Diagram 2] FIG. 1 is a diagram showing an example of the configuration of a delivery system. [Diagram 3] FIG. 2 is a diagram showing an example of the configuration of a server device. [Figure 4] FIG. 2 is a diagram showing an example of the configuration of a luggage management database according to an embodiment of the present invention. [Diagram 5] FIG. 13 is a diagram showing an example of the configuration of a package management database. [Figure 6] FIG. 4 is a diagram for explaining a package management database. [Figure 7] FIG. [Figure 8] FIG. 4 is a diagram showing a process flow relating to the acceptance of a delivery request. [Figure 9] FIG. 4 is a diagram showing an example of the configuration of a screen displayed on a client terminal. [Figure 10] FIG. 13 is a diagram showing the flow of processing related to delivery. [Figure 11] FIG. 13 is a diagram showing an example of the structure of an enclosed file. [Figure 12] FIG. [Figure 13] FIG. [Figure 14] FIG. 13 is a diagram showing a slip used in the point redemption system. [Figure 15] FIG. 13 is a diagram showing the contents of delivery data. [Figure 16] A diagram showing the consignee point and the courier point. [Figure 17] A diagram showing cooperation with other point management systems. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0026] <1-1. Overview of the delivery system 100> An overview of the delivery system 100 will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining the overview of the delivery system 100.

[0027] In order to deal with the so-called 2024 problem, this delivery system 100 adopts a shared transportation method in which multiple packages are mixed together and delivered in a common package box between the departure point and the arrival point, and also incorporates a point reward system PRS into part of the delivery system 100, which awards points to the person (consignee) who cooperates with the initial delivery at the individual delivery stage from the arrival point, and in the event of a redelivery, the points are transferred to the delivery person and given to reward the delivery person's efforts.

[0028] First, the basic delivery system 100 will be described, and then the point redemption system PRS incorporated in this delivery system 100 will be described.

[0029] In the delivery system 100, a plurality of bases 1 are set. In addition, in the delivery system 100, an area 10 under the jurisdiction of each base 1 is defined. A facility that can temporarily store luggage 2 is selected as the base 1. For example, a newspaper store, a convenience store, a gas station, a dry cleaning shop, etc. may be defined as the base 1. When a newspaper store is defined as the base 1, its delivery area may be defined as the area 10 under the jurisdiction of the base 1. The location of each base 1 and the division of the area 10 under the jurisdiction of each base 1 are registered in map information 600 (FIG. 3) by an administrator of the delivery system 100 or the like. At gas stations and dry cleaning, users visit to fill up the tank and receive and deliver dry cleaning, and they also deliver kerosene and collect and deliver dry cleaning, so they understand the local circumstances and are easy to match with a luggage base.

[0030] In the delivery system 100, a package 2 requested for delivery is collected at one of the bases 1 (start base 1a). The package 2 may be brought to the base 1 by the consignor Pa. In this case, the base 1 where the consignor Pa brought the package 2 becomes the start base 1a. Alternatively, the package 2 may be collected from the consignor Pa by a delivery person Pc and brought to the base 1. In this case, the package 2 is brought to the base 1 that has jurisdiction over the area 10 to which the address of the collection destination (typically the address of the consignor Pa) belongs, and the base 1 becomes the departure base 1a.

[0031] In the delivery system 100, the parcel 2 requested for delivery is received by the designated consignee Pb via one of the bases 1 (arrival base 1b). The parcel 2 may be picked up by the consignee Pb at one of the bases 1. In this case, the base 1 where the consignee Pb comes to pick up the parcel 2 becomes the arrival base 1b. Alternatively, the parcel 2 may be individually delivered to the consignee Pb by a delivery person Pc. In this case, the base 1 that has jurisdiction over the area 10 to which the address of the individual delivery destination of the parcel 2 (typically the address of the consignee Pb) belongs becomes the arrival base 1b.

[0032] In the delivery system 100, a combination of parcels 2 is determined from parcels 2 that have the same departure base 1a and the same arrival base 1b. The combined parcels 2 are then transported from the departure base 1a to the arrival base 1b in a state where they are packaged together in one box (package box) 20. In other words, between the departure base 1a and the arrival base 1b, the combined parcels 2 are packaged together in one package box 20 and transported as one parcel. This reduces the delivery costs between bases (particularly the costs incurred according to the number of parcels, such as the labor required for sorting and procedures). Here, the package box 20 is an outer box, and the parcels 2 are inner boxes that are placed in the outer box. The contents of the inner box are the actual items to be delivered.

[0033] <1-2. Configuration of the delivery system 100> Next, the configuration of the delivery system 100 will be described with reference to Fig. 2 and Fig. 3. Fig. 2 is a diagram showing an example of the configuration of the delivery system 100. Fig. 3 is a diagram showing an example of the configuration of the server device 3.

[0034] The delivery system 100 is configured to include a server device (management server) 3 managed by the operator, a base terminal 4 arranged at each base 1, a client terminal 5a of the sender Pa, a client terminal 5b of the receiver Pb, and a terminal 5c of the delivery person. The server device 3, the base terminal 4, the client terminal 5a of the sender Pa, the client terminal 5b of the receiver Pb, and the terminal 5c of the delivery person are connected to each other so as to be able to communicate with each other via a network (communication network) N such as the Internet.

[0035] The entity of the server device 3 is, for example, a general personal computer or a workstation that is a computer with higher performance than a general personal computer. The server device 3 is configured to include, for example, a CPU 31, a memory 32, a communication unit 33, a storage unit 34, a display unit 35, an operation unit 36, and the like. The CPU 31, for example, performs overall control of the server device 3 according to a procedure described in a program. The memory 32 is configured to include, for example, a volatile storage device such as a RAM. The memory 32 temporarily stores, for example, data from each of the client terminals 5a and 5b. The communication unit 33 is a network interface for communicating with external devices (the base terminal 4, each of the client terminals 5a and 5b, etc.) via wireless communication or the like. The storage unit 34 is configured to include, for example, a nonvolatile storage device such as a ROM. The storage unit 34 stores a program in which an operation procedure is described. The storage unit 34 also stores map information 600 in which the positions of the multiple bases 1 and the sections of the area 10 under the jurisdiction of each base 1 are registered. Furthermore, the memory unit 34 stores a parcel management database 700 and a package management database 800. The display unit 35 is an element for displaying various information, and is configured using a liquid crystal display, a CRT display, etc. The operation unit 36 ​​is an element for receiving various inputs, and is configured using a keyboard, a mouse, a scanner, a drive device for CD-ROM, DVD, etc. Furthermore, the server device 3 realizes a delivery management unit 301 and a combination determination unit 302, which are functional units for realizing the operation of the delivery system 100. The delivery management unit 301 and the combination determination unit 302 are realized, for example, by installing predetermined application software in the server device 3.

[0036] Each of the base terminal 4, the client terminal 5a of the sender Pa, the client terminal 5b of the receiver Pb, and the terminal 5c of the delivery person is a communication terminal device capable of realizing a general information processing function, and is configured to include a CPU, a memory, a communication unit, a storage unit, a display unit, an operation unit, and the like. As these terminals 4, 5a, and 5b, for example, a smartphone, a tablet-type communication terminal, a mobile phone, a notebook computer, a general personal computer, and the like are assumed. A functional unit for realizing the operation of the delivery system 100 may be realized in at least one of the base terminal 4, the client terminal 5a of the sender Pa, and the client terminal 5b of the receiver Pb. In this case, each functional unit is realized, for example, by installing a predetermined application software in the terminal 4, 5a, or 5b.

[0037] <1-3. Baggage management database> The luggage management database 700 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of the luggage management database 700.

[0038] The parcel management database 700 is a database for managing information about parcels 2 for which delivery has been requested, and is managed by a database management system (DBMS) with general functions. In the parcel management database 700, each record 7 corresponds to one parcel 2 for which delivery has been requested. Below, each record 7 in the parcel management database 700 is also referred to as a "parcel record 7." A record number (parcel number) 70 is assigned to each parcel record 7. This parcel number 70 is assigned mechanically in the order in which it is received.

[0039] In each package record 7, the size 71 of the package (inner box) 2 is registered. In the delivery system 100, a predetermined size type F1 is prepared as a package box (outer box) 20 that can be handled, and the sizes of the package (inner box) 2 that can be packaged and delivered in this package box (outer box) 20 are classified and specified into several types. That is, two or more size types E11, E12, ... are specified in advance as the sizes of the package (inner box) 2 that can be delivered. Then, in each package record 7, one of the two or more size types E11, E12, ... is selected and specified as the size 71 of the package (inner box) 2. Here, the outer box 20 of size type F1 is the size of a mandarin orange box (120), E11 is the inner box size that two packages can fit in the outer box 20, E12 is the inner box size that three packages can fit in the outer box 20, and E13 is the inner box size that four packages can fit in the outer box 20 (FIG. 7).

[0040] Information (departure base information) 72a for identifying the departure base 1a and information (arrival base information) 72b for identifying the arrival base 1b are registered in each baggage record 7. For example, identification information (e.g., base code, base number, base name, etc.) given to each base 1 is registered as the base information 72a and 72b.

[0041] Each parcel record 7 includes, for example, the name 73a, address 74a, and contact information 75a (telephone number, email address, etc.) of the sender Pa, and the name 73b, address 74b, and contact information 75b (telephone number, email address, etc.) of the recipient Pb.

[0042] In each baggage record 7, a selection 76a of whether or not the baggage 2 is to be carried to the departure base 1a is registered. In addition, in each baggage record 7, a selection 76b of whether or not individual delivery is to be made from the arrival base 1b is registered.

[0043] Information (group information) 77 that identifies the group to which the luggage 2 belongs is registered in each luggage record 7. Here, each luggage record 7 registered in the luggage management database 700 is grouped so that luggage 2 having the same departure base 1a and the same arrival base 1b belong to the same group, and identification information given to each group (e.g., group code, group number, group name, etc.) is registered as group information 77. For example, a luggage record 7 (baggage number "02" in the figure) that satisfies the conditions of departure base K2 and arrival base D1 is treated as group "K2D1."

[0044] <1-4. Parcel Management Database> The package management database 800 will be described with reference to Figures 5 and 6. Figure 5 is a diagram showing an example of the configuration of the package management database 800, which is managed by a database management system (DBMS) equipped with general functions. Figure 6 is a diagram for explaining the relationship between the package box (outer box) 20 used in this embodiment and the package management database 800.

[0045] The package management database 800 is a database for managing combinations of packages (inner boxes) 2 to be packaged in a package box (outer box) 20. As described above, the package records 7 registered in the package management database 700 are grouped such that inner boxes 2 having the same departure base 1a and the same arrival base 1b belong to the same group. In the package management database 800, inner boxes 2 belonging to the same group are extracted and managed in group units. For example, a separate package management database 800 is created for each group (A5L7, M3P9, K2D1). That is, the storage unit 34 stores the same number of package management databases 800 as the groups, and each package management database 800 manages combinations of package records 7 belonging to the same group in units of package boxes (outer boxes) 20. In other words, from among the parcel records 7 belonging to the same group (e.g., K2D1), a combination of parcel records 7 corresponding to a combination of parcels (inner boxes) 2 to be packaged in one package box (outer box) 20 is determined and managed in the package management database 800.

[0046] In the package management database 800, each record 8 corresponds to one package box (outer box) 20. Below, each record 8 in the package management database 800 is referred to as a "package box record 8" or an "outer box record 8." A package box number (BOX number) (A5589, A5590, ...) is assigned to each package box record 8. The package box number (BOX number) is composed of a string of alphanumeric characters.

[0047] In each package box record 8, the size 81 of the package box (outer box) 20 is registered. For example, in this embodiment, an outer box of size type F1 is used, but depending on which of the inner boxes 2 of size types E11 to E13 is put in, as shown in Figs. 6 and 7, the outer box of size type F1 is further classified into inner types F11, F12, F13, and F14 (mixed), and managed by inner type. In the delivery system 100, as shown in Fig. 6 as an example other than size type F1, one or more types of boxes of different size types may be selected as the usable package box (outer box) 20. In other words, when two or more size types F1, F2, ... are specified in advance as the size of the usable package box (outer box) 20, in each package box record 8, one or more of the specified size types F1, F2, ... can be selected and specified as the size 81 of the package box (outer box) 20. Each size type F1, F2, ... is defined by, for example, the dimensions of the three sides (length, width, and depth) of the box. As an example, a cardboard box of a general-purpose standard size may be selected as the usable packaging box (outer box) 20, in which case each size type F1, F2, ... corresponds to a general-purpose standard size. In FIG. 6, as described above, the size type F1 has a total of 120 for the three sides, the size type F2 has a total of 100 for the three sides, the size type F3 has a total of 80 for the three sides, the size type F4 has a total of 60 for the three sides, and the size type F5 has a total of 40 for the three sides. Similarly to the size type F1, the size types F2 to F5 can also be prepared with inner boxes 2 further classified into sub-types (F21, F22, ...) according to the sizes (E21, E22, ...) of the inner boxes 2 that fit them.

[0048] A parcel record 7 (specifically, information identifying the parcel record 7, such as a record number (parcel number) 70) is registered in each cell 82 of each parcel box record 8. The parcel (inner box) 2 corresponding to the parcel record 7 registered in each cell 82 of one parcel box record 8 will be packaged in the parcel box (outer box) 20 corresponding to that parcel box record 8. In other words, a combination of parcel records 7 registered in one parcel box record 8 becomes a combination of parcels (inner boxes) 2 packaged in one parcel box (outer box) 20. For example, inner boxes 2 of parcel records 02 and 05 are managed as parcels to be packaged together.

[0049] Here, the size types E11, E12, E21, E22,... and the number of items (inner boxes) 2 to be packed in the same package box (outer box) 20 are specified in advance for each size type F1, F2,... of the same package box (outer box) 20 (this is also called "packing conditions"). Also, when multiple internal types F11, F12,... are specified for one size type F1, the packing conditions are specified for each internal type F11, F12,... For example, as illustrated in FIG. 7, the packing conditions for the packing box (outer box) 20 of "size type F1" are stipulated according to the number of divisions of the packing box (outer box) 20, such as "two packages (inner boxes) 2 of size type E11", "three packages of size type E12", "four packages of size type E13", and "mixed type of size type E14 E3 and E1". In other words, for the packing box 20 of "size type F1", the size types E11, E12, ... and the number of packages 2 are stipulated as packing conditions according to the number of packages 2 packed in the packing box 20. Similarly, the packing conditions for the packing box (outer box) 20 of "size type F2" are stipulated according to the number of divisions of the packing box (outer box) 20, such as size types E21, E22, .... The same applies to size types F3 to F5.

[0050] In each parcel box record 8, a registration condition is assigned to each cell 82 of the parcel box record 8 so as to match the packing conditions defined for the size types F1, F2, ... selected as the parcel box size 81. For example, referring to the outer box record 8 in spread format shown in Fig. 5 and the packing conditions in Fig. 7, two cells 82 that accept size type E11 in parcel box number (BOX number) A5589, three cells 82 that accept size type E12 in parcel box number (BOX number) A5590, and four cells that accept size type E13 in parcel box number (BOX number) A5591 are each enabled in an input-enabled state and can be registered in the blank areas.

[0051] In each package box record 8, a package record 7 is registered according to the registration conditions assigned thereto. That is, in an enabled cell 82, a package record 7 of a size type that satisfies the registration conditions of that cell 82 is registered. In this way, a combination of package records 7 is determined that satisfies the package conditions.

[0052] The fact that the parcel record 7 is registered in all the cells 82 in the horizontal direction that are enabled in the parcel box record 8 means that the combination of the parcel records 7 that meets the parcel condition is completed (i.e., the parcel is established). In other words, when the parcel box record 8 has a cell 82q in which the parcel record 7 is not registered despite being enabled, the combination is not completed (the parcel is not established). In such a state, the cell 82q in which the parcel record 7 is not registered corresponds to the "empty space Q" in the parcel box (outer box) 20. For example, in the case of the registration status illustrated in FIG. 5, the parcel record 7 is registered in all the enabled cells 82 in the parcel box record 8 of "parcel box number (BOX number) A5589", so that the parcel is established. In other words, the parcel box (outer box) 20 corresponding to this parcel box record 8 does not have the empty space Q. On the other hand, in the parcel box record 8 of "parcel box number (BOX number) 5591", there is a cell 82q in which the parcel record 7 is not registered despite being enabled, so that the parcel is not established. In other words, there is a vacant space Q in the packing box (outer box) 20 corresponding to this packing box record 8.

[0053] <1-5. Processing flow> A description will now be given of the flow of processing carried out in the delivery system 100. In the delivery system 100, processing related to the acceptance of a delivery request and processing related to delivery are carried out in parallel.

[0054] (a) Processing related to receipt of delivery requests The flow of processing related to receiving a delivery request will be described with reference to Fig. 8. Fig. 8 is a diagram showing the flow of the processing.

[0055] When the server device 3 receives an inquiry about availability transmitted from the client terminal 5a (step S1), the delivery management unit 301 requests the inquirer to input information (basic information) required to check availability through the client terminal 5a (step S2). When the inquirer inputs the basic information through the client terminal 5a, the input basic information is transmitted to the server device 3 (step S3). When the server device 3 receives the basic information, the delivery management unit 301 accepts the basic information. As the basic information, for example, the size type (E11 to E13) of the package (inner box) 2, the departure base 1a of the package (inner box) 2, and the arrival base 1b of the package (inner box) 2 are accepted. Any mode may be used to have the inquirer input the basic information. For example, the inquirer may be requested to input the address of the sender Pa (or the consignee Pb), and the delivery management department 301 may identify the area 10 to which the input address belongs from the map information 600, and accept the base 1 in that area 10 as the departure base 1a (or the arrival base 1b).

[0056] When the basic information is accepted, the delivery management unit 301 refers to the package management database 800 to search for the free space Q, specifically, the cell 82q corresponding to the free space Q (step S4). Specifically, the delivery management unit 301 first identifies a group corresponding to the combination of the departure base 1a and the arrival base 1b included in the accepted basic information, and reads out the package management database 800 for the group. Then, from the read package management database 800, a cell 82q corresponding to the free space Q (i.e., a cell that is enabled and in which a package record 7 is not registered) with a matching size type (E11-E13) (i.e., a cell in which the size type (E11-E13) of the package (inner box) 2 that can be registered matches the size type (E11-E13) of the package (inner box) 2 accepted as the basic information) is searched for. If such a cell 82q is found, the delivery management unit 301 sets the state of the cell 82q to "temporarily reserved" and temporarily makes it impossible to register the package record 7.

[0057] Next, the delivery management unit 301 notifies the inquirer's client terminal 5a of the search result for the free space Q, and requests the inquirer to input through the client terminal 5a whether or not to proceed to a delivery request (step S5). Specifically, for example, if the delivery management unit 301 finds a cell 82q that corresponds to the free space Q and has a suitable size type in step S4, it displays a message such as "Free space found. Would you like to request delivery?" on the display unit of the inquirer's client terminal 5a (FIG. 9(b)). Also, if the delivery management unit 301 does not find a cell 82q that corresponds to the free space Q and has a suitable size type in step S4, it displays a message such as "Free space not found. Would you like to request delivery and collect package recipients?" on the display unit of the inquirer's client terminal 5a (FIG. 9(c)).

[0058] If the inquirer inputs through the client terminal 5a a selection not to proceed with the delivery request, the selection input is sent to the server device 3, and the delivery management unit 301 accepts the selection input. If a selection not to proceed with the delivery request is accepted, the delivery management unit 301 ends the process. If there is a cell 82q that was set to "temporarily reserved" in step S4, the delivery management unit 301 returns the cell 82q to a state in which the parcel record 7 can be registered again, and then ends the process.

[0059] On the other hand, if the inquirer inputs a selection to proceed to the delivery request through the client terminal 5a, the selection input is also sent to the server device 3, and the delivery management unit 301 accepts the selection input (step S6). When the selection to proceed to the delivery request is accepted, the delivery management unit 301 requests the inquirer (at this point, the delivery requester) to input information (request information) required for the delivery request through the client terminal 5a (step S7). When the delivery requester inputs the request information through the client terminal 5a, the input request information is transmitted to the server device 3 (step S8). When the request information is received by the server device 3, the delivery management unit 301 accepts the request information. As the request information, for example, the name, address, and contact information (telephone number, email address, etc.) of the sender Pa, the name, address, and contact information (telephone number, email address, etc.) of the recipient Pb, whether or not the package (inner box) 2 will be brought to the departure base 1a, and whether or not individual delivery will be made from the arrival base 1b are accepted.

[0060] When the request information is accepted, the delivery management unit 301 registers the accepted request information together with the previously accepted basic information in the parcel management database 700 (step S9). Specifically, the delivery management unit 301 creates a new parcel record 7 in the parcel management database 700, and registers the basic information and each content accepted as the request information in each item of the new parcel record 7. In addition, the delivery management unit 301 identifies the group to which the parcel record 7 should belong based on the departure base 1a and arrival base 1b registered in the parcel record 7, and registers the identification information of the group as group information 77.

[0061] Next, the combination determination unit 302 registers the package record 7 created in step S9 (specifically, for example, the record number (package number) 70 of the package record 7) in the package management database 800 (step S10). The manner in which the combination determination unit 302 registers the package record 7 differs depending on whether the delivery request is accepted when the free space Q has been found or not.

[0062] In other words, when a delivery request is accepted when free space Q has been found, the combination determination unit 302 registers the parcel record 7 created in step S9 in the cell 82q that was set as "temporarily reserved" in step S4.

[0063] On the other hand, if the delivery request is accepted in a situation where the free space Q has not been found, the combination determination unit 302 creates a new parcel box record 8 in the parcel management database 800, and registers the parcel record 7 created in step S9 in the cell 82 of the new parcel box record 8. Specifically, the combination determination unit 302 first reads out the parcel management database 800 of the group to which the created parcel record 7 belongs. Then, the combination determination unit 302 creates a new parcel box record 8 in the read out parcel management database 800. Furthermore, the combination determination unit 302 specifies an appropriate size type of the parcel box (outer box) 20 based on the size type of the parcel (inner box) 2 accepted as basic information, and further specifies an appropriate division type, and selects this as the size 81 of the new parcel box record 8. The appropriate size type of the parcel box (outer box) 20 is one in which the size type of the parcel (inner box) 2 specified in the packaging conditions of the size type includes the size type of the parcel (inner box) 2 accepted as basic information. Similarly, an appropriate division type is one in which the size type of the package (inner box) 2 specified in the packing conditions of the division type includes the size type of the package (inner box) 2 accepted as basic information. Then, the combination determination unit 302 registers the package record 7 created in step S9 in a cell 82 of the new package box record 8 (obviously, a validated cell in which the size type of the package (inner box) 2 matches).

[0064] Delivery requests are accepted until the number of packages is met through matching, or until a specified period of time has passed since the start of acceptance (for example, one or at the latest two days after the first package is accepted), whichever comes first. If matching is achieved during that time, the package will be ready for shipment, but even if matching is incomplete, the request will be closed and the package will be shipped once the time arrives. Packages that are difficult to deliver on a specific date and time can be left to existing delivery services.

[0065] (b) Delivery Processing The flow of processing relating to delivery will be described with reference to Figures 10 and 11. Figure 10 is a diagram showing the flow of processing. Figure 11 is a diagram showing an example of the structure of a package file 80.

[0066] The delivery management unit 301 monitors whether a package box record 8 for which a package has been formed (i.e., a package box record 8 for which a parcel record 7 has been registered in all enabled cells 82) has been generated in each package management database 800, and when a package box record 8 for which a package has been formed is generated (YES in step S101), the delivery management unit 301 starts the following processing as processing after the package has been formed.

[0067] In this case, when a package box record 8 in which a package has been established is generated, processing will proceed to the processing after the package has been established. However, if the package has been established by the package deadline as described above, processing will proceed to the processing after the package has been established at the time of establishment or at the package deadline. If the package has not been established by the package deadline, processing will proceed to the processing after the package has been established at the time the package deadline arrives.

[0068] (Package file creation process) The delivery management unit 301 first creates a file (package file) 80 shown in FIG. 11 that describes information about the package (inner box) 2 to be packaged in the package box (outer box) 20 corresponding to the package box record (hereinafter also referred to as the "target package box record") 8 for which the package was created (step S102). Specifically, for example, the delivery management unit 301 reads out the registered contents (contents registered in each item) of the package records 7 registered in each cell 82 of the target package box record 8 (i.e., each package record 7 combined in the target package box record 8) from the package management database 700, and lists these and describes them in the package file 80. Furthermore, the delivery management unit 301 describes the contents registered as size 81 in the target package box record 8 (i.e., the size type of the package box (outer box) 20 corresponding to the target package box record 8) in the package file 80. This package file 80 serves as basic data for outer box information and inner box information that associate the outer box 20 and the inner box 2.

[0069] (Notification process to shipper) Next, the delivery management unit 301 notifies the sender Pa of each package (inner box) 2 packaged in the package box (outer box) 20 corresponding to the target package box record 8 (specifically, the client terminal 5a identified from the contact information 75a of the sender Pa registered in each package record 7 combined in the target package box record 8) that the package (inner box) 2 will be shipped (step S103). Specifically, for example, the delivery management unit 301 sends an email including a message such as "The requested package will be delivered" to the client terminal 5a. This email may include various information. For example, if the carry-on of the luggage (inner box) 2 to the departure base 1a is set to "no", the email sent to the client terminal 5a of the sender Pa may include a message such as "We will collect the luggage at address XXX on XXX month, XXX day, XXX time", and if the carry-on of the luggage (inner box) 2 to the departure base 1a is set to "yes", the email sent to the client terminal 5a of the sender Pa may include a message such as "Please bring the luggage to address XXX by XXX month, XXX day, XXX time". At this time, as shown in FIG. 12, the shipping information and the BOX number are sent to the client terminal 5a (smartphone) of the sender Pa.

[0070] In addition, the delivery management unit 301 transmits the package file 80 created in step S102 to the base terminal 4 of the departure base 1a of the package box (outer box) 20 corresponding to the target package box record 8 (i.e., the departure base 1a registered in each parcel record 7 that was combined with the target package box record 8) (step S104).

[0071] (Shipping process) As a result, as shown in FIG. 12, the parcels (inner boxes) 2 requested for delivery are basically collected at each departure base 1a. The parcels (inner boxes) 2 for which the delivery of the parcels (inner boxes) 2 to the departure base 1a is set to "Yes" are brought to the departure base 1a by the sender Pa. There, the shipping information and BOX number are confirmed at the store, and a delivery slip 2X is printed and affixed to the outer surface of the parcel (inner box) 2. Payment may be made online or at the store. The delivery slip 2X displays detailed information such as the name, address, and telephone number of the sender Pa and the recipient Pb of each parcel (inner box) 2, the BOX number, and an access code AC (QR code (registered trademark), barcode, etc.) as inner box information (inner box display). This access code AC is mainly used to access the package file 80 and verify the identity of the recipient Pb from the detailed information at the time of receipt, but it can also be used to access the package file 80 and process the payment of the sender Pa. Access to this access code AC is permitted only to those with authority, and it is configured so that it cannot be read from a general smartphone, or even if it is read, it cannot be accessed because it does not have the information required for authority. Also, the luggage (inner box) 2 that is set as "not allowed" is collected from the sender Pa by the collector Pc (person in charge) and brought to the departure base 1a. In this case, the person in charge goes to collect the luggage. The center receives the shipping information and BOX number, and compares it with the shipping information and BOX number on the sender Pa's smartphone to receive the luggage (inner box) 2. After that, the same delivery slip 2X as above is printed and affixed to the collected luggage (inner box) 2. Payment can be made online, or it can be made locally at this time. The fact that the luggage (inner box) 2 has been received is reflected in the package file 80 by access through the access code AC.

[0072] (Notification process to the recipient) The delivery process does not begin until the settlement is complete. Here, for example, the process of notifying the consignee Pb begins after the settlement is completed. That is, when the settlement is completed, the delivery management unit 301 first notifies the consignee Pb of each package (inner box) 2 packaged in the package box (outer box) 20 corresponding to the target package box record 8 (specifically, the client terminal 5b identified from the contact information 75b of the consignee Pb registered in each package record 7 combined in the target package box record 8) that the package (inner box) 2 will be shipped at an appropriate timing after the settlement is completed (step S105). Specifically, for example, the delivery management unit 301 sends an email including a message such as "The requested package will be delivered" to the client terminal 5b. This email may include various information. If individual delivery from the arrival base 1b is set to "No", the email sent to the client terminal 5b of the consignee Pb may include a message such as "Please come to address XX to pick up the package after XX / XX / XX." At this time, as shown in FIG. 13, the client terminal 5b (smartphone) of the consignee Pb receives the package information required for authentication when receiving the package 2. If individual delivery from the arrival base 1b is set to "Yes", individual delivery will be made from the arrival base onwards, but as will be described later, the delivery person Pc will contact the consignee Pb in advance, and the delivery person Pc and the consignee Pb will agree on and confirm the date and time of receipt of the package.

[0073] In addition, the delivery management unit 301 transmits the package file 80 created in step S102 to the base terminal 4 of the arrival point 1b of the package box (outer box) 20 corresponding to the target package box record 8 (i.e., the arrival point 1b registered in each parcel record 7 that was combined with the target package box record 8) (step S106).

[0074] (Mixing process) The manager of the departure base 1a prints the BOX number and the name (sender Pa, consignee Pb) of each package (inner box) 2 as outer box information (outer box display) from the package file 80 received in advance by the base terminal 4, and attaches it to the outside of the outer box 20 as a label 20X. The information here is a minimum simplified display required for association with the package (inner box) 2. This is because the outer box 20 will remain at the center (arrival base 1b) after delivery. Then, the collected multiple packages (inner boxes) 2 and outer boxes 20 are put into one corresponding package box (outer box) 20 while checking the BOX number and the name (sender Pa, consignee Pb). Since there may be people with the same name, it is desirable to check the BOX number at the same time to improve accuracy. If a barcode for checking the BOX number is attached to the outer box 20 and the inner box 2, it can be read by a reader and visually or mechanically identified and checked, which is effective when handling a large amount of packages. When all of the specified packages (inner boxes) 2 are packed together (mixed) in the same packing box (outer box) 20, the manager seals the same packing box (outer box) 20. Needless to say, when all of the specified inner boxes 2 are packed together in the outer box 20, the same box number is attached to the outer surface of the outer box 20 and each of the inner boxes 2 contained therein.

[0075] (Delivery process) The package box (outer box) 20 is transported from the departure base 1a to the target arrival base 1b. In other words, the combined packages 2 are packaged in one package box (outer box) 20 between the departure base 1a and the arrival base 1b and transported as one package. The delivery of the package box (outer box) 20 between the bases may be performed under the management of the delivery system 100, or may be performed under the management of another delivery company (such as an existing delivery company). Of course, upon receiving a request from a certain delivery company, delivery between the bases may be performed by a delivery company belonging to this delivery system 100 or another delivery company.

[0076] (Receiving process) As shown in FIG. 13, the package box (outer box) 20 that arrives at the arrival base 1b is first received by the manager of the arrival base 1b. After that, the manager unseals the package box (outer box) 20, and each package (inner box) 2 packaged in the package box (outer box) 20 is received by each consignee Pb. Packages 2 for which individual delivery from the arrival base 1b is set to "no" are handed over to the consignee Pb who comes to the arrival base 1b to receive them. Packages 2 for which this is set to "yes" are individually delivered from the arrival base 1b to the consignee Pb by a collector Pc (delivery staff). When individual delivery is made, detailed information about the consignee Pb is displayed on the delivery slip 2X affixed to the package (inner box) 2, so the staff Pc relies on this to deliver directly to the consignee Pb. In this case, as described above, the delivery person Pc contacts the consignee Pb in advance, and the delivery person Pc and the consignee Pb agree on and confirm the date and time of receipt. In this case, identity verification is not required, so the consignee Pb only needs to sign the delivery slip 2X to receive the parcel. Of course, the signature may be omitted, or the parcel may be left at the door. On the other hand, if the consignee Pb comes to the center to receive the parcel, identity verification is required. In this case, before handing over the parcel (inner box) 2, the center will ask the consignee Pb to present the receipt information issued in advance to the consignee Pb, or it will be confirmed that the telephone number displayed on the parcel (inner box) 2 matches the telephone number of the consignee Pb, or identity verification will be performed through other authentication information that can be used to verify the identity of the consignee Pb in the package file 80 accessed through the access code AC.

[0077] (Individual delivery management) At this individual delivery stage, the parcel number and recipient information are extracted in advance based on the package record 80 shown in Fig. 11, and the delivery data shown in Fig. 15 is generated. One record of the delivery data corresponds to one parcel 2 and one waybill 2X.

[0078] Once the delivery person (delivery person) Pc is decided, a delivery date and time communication step S100 is carried out to arrange and share the receipt date and time between the distribution center 1b (delivery person Pc) and the consignee Pb, as shown in FIG. 13. For example, the delivery person Pc may arrange the delivery date and time with the consignee Pb in advance via telephone or SNS, or may send a push notification of the delivery date and time according to the delivery schedule. At the same time, the delivery data management unit 311 (see FIG. 3) on the delivery management unit 301 shown in FIG. 3 adds necessary data to the delivery data shown in FIG. 15 for each package. From this point, communication regarding the first delivery, redelivery, and third redelivery begins.

[0079] The delivery data includes fields for the consignee, the deliverer, the scheduled delivery, the delivery date and time, and the status, and the deliverer Pc takes the package 2 with the delivery slip 2X shown in Fig. 14 attached from the center and performs the individual delivery as shown in Fig. 13. Then, when the delivery is completed, the deliverer takes the package 2 in exchange for a signature or stamp on the delivery slip 2X and takes home all or part of the delivery slip 2X, or takes home the delivery slip 2X and the package 2 if the recipient is not at home.

[0080] The slip in FIG. 14 shows a part of the delivery slip 2X in FIG. 13. When the delivery is completed, the delivery person Pc marks a circle in a part of the corresponding column (point display part in the figure) of the first delivery column 200a, the re-delivery column 200b, or the second re-delivery column 200c, and takes the delivery slip 2X home after receiving the recipient's seal or signature as described based on FIG. 13. If the recipient is absent, a line is drawn through a part of the corresponding column (point display part) shown in FIG. 14 and takes it home. Then, based on the slip, the delivery person Pc directly or indirectly inputs whether the delivery is complete or not into the delivery management unit 301 (delivery data management unit 311). As a result, the delivery date and time are displayed next to the delivery schedule in the delivery data shown in FIG. 15, and the status column next to it reflects whether the recipient is absent or received.

[0081] Of course, if the delivery person Pc has a terminal 5c (see FIG. 2) that is linked to the system, the delivery person Pc may input the delivery data while on the road.

[0082] In the case of redelivery, when the next delivery schedule is made, the next scheduled delivery date and time is entered in the delivery schedule column of the delivery data in Fig. 15, and when the consignee Pb contacts or inputs the next desired delivery date and time, the next scheduled delivery date and time is also entered in the same delivery schedule column. This scheduled delivery date is reflected in the slip 2X in Fig. 14 that is printed at the time of the next delivery and is affixed to the package 2.

[0083] (Introduction of the points redemption system PRS) In operating the above-described delivery system 100, this embodiment incorporates a point redemption system PRS by providing a point management unit 312 linked to the delivery management unit 301 (delivery data management unit 311) as shown in FIG. 3, in order to award points to those who cooperate in individual deliveries beyond the arrival point 1b.

[0084] As shown in FIG. 16, the point management unit 312 has a consignee point section XPb and a delivery person (delivery person) point section XPc, and is configured to award recipient points to the consignee Pb who cooperates in receiving the package, and to award delivery person points to the delivery person Pc who bears the delivery costs, depending on the delivery status from the arrival point 1b to the consignee Pb.

[0085] The point value is displayed in advance on the delivery slip shown in Figure 14. Here, as an example, the first delivery is given 150 points, the second delivery is given 50 points, and the third delivery and thereafter are given 0 points. As mentioned above, when the delivery person Pc has completed handing over the package 2 at the delivery destination, he marks the points portion corresponding to the first delivery, second delivery, or third delivery with a circle, and if the delivery person is not at home, he crosses out the corresponding portion and takes the slip 2X home.

[0086] Based on the returned delivery slip 2X, the delivery status is updated by the delivery person Pc or the office staff, etc., in the delivery data record shown in Fig. 15. At this time, when it is determined whether it is the first delivery, re-delivery, or third re-delivery, 150 points, 50 points, or 0 points (i.e., no points are awarded) are awarded to the consignee points section XPb shown in Fig. 16.

[0087] On the other hand, the points deducted by redelivery and redelivery are transferred to the delivery person Pc whose delivery burden has increased, and 100 points are added to the delivery person point section XPc. After the redelivery, the recipient's points become 0, so 150 points are added to the delivery person point section XPc.

[0088] As shown in FIG. 17, the point management unit 312 shares the points generated with the point operation system PS with which the point management unit 312 has a contract in advance at the timing when the points are awarded or at an appropriate timing thereafter, by linking the points with the member information through the Web. Examples of the point operation system PS include systems such as Rakuten and T-Point, which have constructed general-purpose point operation systems. In order to share data with the point operation system PS, as shown in FIG. 16, the consignee point unit XPb and the delivery person point unit XPc are registered with the point systems (A company points, B company points) of which the consignee Pb and the delivery person Pc are members, along with their member information. It is also desirable that the consignee Pb and the delivery person Pc can select from multiple point operation systems PS for this point system. FIG. 16 shows an example in which the consignee Pb has registered that he will receive points from the A company point system, and the delivery person Pc has registered that he will receive points from the B company point system.

[0089] The A company point system PS(1) and B company point operation system PS(2) in Fig. 17, which share data with the point operation system PS, write points to the consignee point section 1001a and the delivery person point section 1002a corresponding to the membership number through their point management sections 1001 and 1002. This allows the consignee Pb and the delivery person Pc to use the points generally at any time.

[0090] If a point system is not registered in Figure 16, appropriate handling will be necessary. For example, points may be held (reserved) in this point redemption system PRS until a new point system is registered, and the points may be shared when a specific point system and its member information are entered or at an appropriate time thereafter.

[0091] On the other hand, if the individual delivery in the file shown in Fig. 11 is "No," the consignee Pb will come to the center 1b to pick up the package 2, as shown in Fig. 13. In the case of pick-up, no delivery fee is required, and there is no problem with redelivery, so when the package 2 is handed over, 150 points, which is equivalent to the initial receiving points, are given as cooperation points to the consignee point section XPb shown in Fig. 16. The subsequent processing is the same as above.

[0092] (Effect of the carpooling system) The delivery system 100 according to the above embodiment includes a server device 3 and a client terminal 5a connected to the server device 3 via a network N. The server device 3 is equipped with a memory unit 34 that stores map information 600 in which the positions of multiple bases 1 are registered, and a parcel management database 700 having a parcel record 7 each corresponding to one parcel (inner box) 2, a delivery management unit 301 that generates a parcel record 7 corresponding to the parcel (inner box) 2 in the parcel management database 700 in response to a delivery request for a parcel (inner box) 2 received from the client terminal 5a, and registers in the parcel record 7 the departure base 1a and arrival base 1b through which the parcel (inner box) 2 will pass, and further groups the parcel records 7 so that parcels (inner boxes) 2 that have the same departure base 1a and the same arrival base 1b belong to the same group, and a combination determination unit 302 that determines, from the parcel records 7 belonging to the same group, a combination of parcel records 7 corresponding to a combination of parcels (inner boxes) 2 to be packaged in one packaging box (outer box) 20. Then, between the departure base 1a and the arrival base 1b, the combined luggage (inner box) 2 is packed into one package box (outer box) 20 and transported as one luggage.

[0093] According to this configuration, the combined package (inner box) 2 is packed in one package box (outer box) 20 and transported as one package between bases, which reduces the effort required for sorting and procedures for delivery between bases and makes it possible to send packages at low delivery charges.

[0094] As an example, consider the case of delivering a "size 120" (total of three external sides within 120 cm) package from Tokyo to Osaka using a single 4-ton truck. Now, if the "size 120" package shown in Figure B is 60 cm long, 35 cm wide, and 22 cm deep, 828 of these packages can be loaded onto a 4-ton truck (bed dimensions: 220 cm x 820 cm x 268 cm) (3 rows x 23 rows x 12 layers). If the cost of chartering a 4-ton truck from Tokyo to Osaka is 100,000 yen, dividing this by the number of cardboard boxes loaded comes to approximately 120 yen. In other words, a "size 120" cardboard box can be transported from Tokyo to Osaka for a cost of approximately 120 yen. This "size 120" cardboard box is used as a package box (outer box) 20, and two packages (inner boxes) 2 that are "28 cm long, 30 cm wide, and 20 cm deep," that is, "size 80 (total of the three outer sides is within 80 cm)," are packed inside it. In this case, the "size 80" packages can be transported from Tokyo to Osaka for about 60 yen each. (For reference, the shipping cost for sending a "size 120" cardboard box from Tokyo to Osaka is generally about 1,700 yen. Also, the shipping cost for sending an "size 80" cardboard box from Tokyo to Osaka is about 1,200 yen.)

[0095] (Effect of the point redemption system) As described above, the delivery system PRS with point redemption of this embodiment utilizes a shared transportation system 100 that delivers multiple packages 2 mixed together in a common package box 20 between the departure point 1a and the arrival point 1b, and is equipped with a delivery management unit 301 that accepts delivery requests and manages all or part of the process from shipping to receiving of packages 2 that match the delivery destination and date and time, and a point management unit 312 that manages points to be awarded to those who cooperate in delivery from the arrival point 1b onwards.The point management unit 302 has a consignee point unit XPb and a delivery person point unit XPc, and is characterized in that it awards points for receipt cooperation and / or points for delivery burden to the consignee point unit XPb and / or delivery person point unit XPc depending on the delivery status from the arrival point to the consignee Pb, which is part of the management information of the delivery management unit 301 (delivery data management unit 311).

[0096] This delivery system 100 consists of the phases of collection and delivery (or drop-off) at the departure base 1a, transportation between the bases 1a and 1b, and individual delivery (or pick-up) at the arrival base 1b. Generally, the fare is determined by collection and delivery + transportation between the bases + individual delivery, but in this embodiment, the cost of transportation between the bases can be significantly reduced by carpooling, so that even if the point operation cost is factored in, the overall cost can be reduced to below the conventional fare. In this way, reducing the number of packages between the bases 1a and 1b by carpooling not only creates an effective foothold for solving the 2024 problem, but also secures the funds for the point redemption system PRS.

[0097] Then, in the individual delivery phase, the incentive to cooperate with delivery is increased by giving points to the recipient Pb who cooperates with delivery, while if the delivery burden increases, the points can be transferred to the delivery person Pc to reward the effort of redelivery, making it possible to naturally and effectively increase the efficiency of individual deliveries overall.

[0098] Specifically, when the delivery is received for the first time, points related to delivery cooperation are awarded to the recipient point section XPb, and in the case of redelivery, points related to the delivery burden are transferred and awarded to the delivery person point section XPc. This makes it possible to effectively deal with the fact that whether the delivery is received by the recipient Pb or not and whether the delivery burden by the delivery person Pc is increased are extremely closely related to whether the delivery is received for the first time or not and how the delivery person Pc is not affected.

[0099] In this embodiment, upon first receipt of the consignment, the full amount of points is awarded to the consignee points section XPb as points related to delivery cooperation, and after the specified number of redeliveries (i.e., third delivery), the full amount of points is transferred and awarded to the delivery person points section XPc as points related to delivery burden, and from the second receipt of the consignment until the specified number of redeliveries (i.e., third delivery), points are allocated and awarded to the recipient points section XPb and the delivery person points section XPc, so that the point transfer ratio can be changed gradually.

[0100] In addition, when the consignee Pb comes to the center 1b to pick up the parcel, points equivalent to the initial receipt points are given to the consignee point section XPb as cooperation points, so that it is possible to effectively deal with cases that are not included in either initial receipt or re-delivery.

[0101] The points are managed in a separate system, separate from the basic fee system required for management of the process from receiving delivery requests to shipment and receipt, which is carried out by the delivery management unit 301. If the points were incorporated into the basic fee system, it would be difficult to utilize the points in a general-purpose manner, but since the points are separated, the attribute of rewarding cooperation becomes clear, and practical operation becomes possible using general-purpose point operation systems PS(1), PS(2), etc.

[0102] For this reason, the consignee points and delivery points managed by the point management unit 312 are transmitted to the servers of other point operation systems PS(1), PS(2) that implement point usage, so that the points can be appropriately transferred to a general-purpose point system.

[0103] In this delivery system, multiple sizes of the parcel box 20 are specified in advance, and delivery requests are made by selecting the size, but in this system, the type of box, destination, and schedule are the keys to matching parcels, so standardizing the boxes as described above can effectively increase the matching probability. Sizes that do not fit this embodiment (such as those that are too large, too small, too heavy, or too long) can be left to existing home delivery services.

[0104] In this embodiment, delivery requests are accepted until the number of packages is met through matching, or until a specified period of time has passed since the start of acceptance, whichever comes first. In this system 100, the type of box, destination, and schedule are the keys to matching packages, but by allowing time for matching as described above, the matching probability can be effectively increased. In addition, by targeting packages that do not require the delivery time to be as short as possible, those involved in delivery can be relieved from unreasonable delivery work.

[0105] Furthermore, since the parcel box is moved based on the most common shipping date and time and arrival date and time for the parcels contained in the parcel, individual delivery management is required after arrival. However, a delivery date and time communication step S100 is carried out in which the arrival point and the consignee agree and share the receipt date and time, and the delivery management and point management related to the individual delivery are carried out based on the agreed date and time, so that the individual delivery of the parcel 2 can be carried out reliably.

[0106] This system can basically be used for both BtoB and CtoC.

[0107] Although an embodiment of the present invention has been described above, the specific configuration of each part is not limited to the above-described embodiment.

[0108] In particular, in the above embodiment, the point redemption system PRS is incorporated into the delivery system 100 that is based on ride-sharing. However, even in a general delivery system that performs individual deliveries from centers in various locations, regardless of whether ride-sharing is used or not, the introduction of the point redemption system can achieve the same effect as the above embodiment, that is, it is possible to increase the first-time delivery rate and reward the efforts of delivery personnel who make redeliveries.

[0109] Other configurations can also be modified in various ways without departing from the spirit of the present invention. [Explanation of symbols]

[0110] 100 Delivery System 301 Delivery Management Department 312 Point Management Department XPb Recipient Point Section XPc Delivery Point Department PRS Points Rebate System 1 base 1a Departure point 1b Arrival point 2. Luggage 20 Same packaging box

Claims

1. This includes a shared transportation mode in which multiple packages are delivered in a common package between a departure point and an arrival point, A delivery management section that receives delivery requests and manages all or part of the process from shipment to receipt of packages that match the delivery destination and date and time; A point management unit that manages points to be given to a person who cooperates in delivery beyond the arrival base, The point management unit has a consignee point unit and a delivery person point unit, and grants points as receipt cooperation and / or points as delivery burden to the consignee point unit and / or the delivery person point unit according to the delivery status from the arrival base to the consignee, which is a part of the management information of the delivery management unit. A delivery system with point redemption.

2. 2. A delivery system with point redemption as described in claim 1, wherein points related to delivery cooperation are awarded to the recipient's points section when the delivery is received for the first time, and in the case of redelivery, points related to delivery burden are transferred to the delivery person's points section and awarded thereto.

3. A delivery system with point redemption as described in claim 2, wherein, at the first receipt of the consignment, the full amount of points is awarded to the consignee point section as points related to delivery cooperation, and after a predetermined number of redeliveries, the full amount of points is transferred and awarded to the delivery person point section as points related to delivery burden, and from the second receipt of the consignment until the predetermined number of redeliveries, points are allocated and awarded to the recipient point section and the delivery person point section.

4. 4. A delivery system with points redemption according to claim 3, wherein in the case of pick-up, points equivalent to the initial receiving points are awarded to the recipient's points department as cooperation points.

5. 2. The delivery system with point redemption according to claim 1, wherein the points are managed in a separate system from a basic fee system required for the delivery management department to receive delivery requests and manage the process from shipment to receipt.

6. 6. A delivery system with point redemption according to claim 5, wherein the consignee points and the delivery person points managed by the point management unit are transmitted to another point management server which executes point usage.

7. 2. The delivery system with point redemption according to claim 1, wherein a plurality of sizes of the package are predefined, and a delivery request is made by selecting a size.

8. 2. The delivery system with point redemption according to claim 1, wherein delivery requests are accepted until the number of packages is met through matching or until a predetermined period of time has elapsed since the start of acceptance, whichever comes first.

9. 2. A delivery system with point redemption as described in claim 1, which carries out a delivery date and time communication step in which the arrival point and the consignee agree and share the date and time of receipt of the goods, and the delivery management and point management related to individual deliveries are carried out based on the agreed date and time.

10. A delivery management department that receives delivery requests and manages delivery destinations and dates and times; A point management unit that manages points to be given to those who cooperate in delivery, The point management unit has a consignee point unit and a delivery person point unit, and grants points as receipt cooperation and / or points as delivery burden to the consignee point unit and / or the delivery person point unit according to the delivery status, which is a part of the management information of the delivery management unit. A delivery system with point redemption.

11. The delivery system with point redemption according to claim 10, wherein points relating to delivery cooperation are awarded to the recipient's points section when the delivery is received for the first time, and in the case of redelivery, points relating to delivery burden are transferred and awarded to the deliverer.

12. A delivery system with point redemption as described in claim 10, wherein, at the first receipt of the consignment, the full amount of points is awarded to the consignee point section as points related to delivery cooperation, and after a predetermined number of redeliveries, the full amount of points is transferred and awarded to the delivery person point section as points related to delivery burden, and from the second receipt of the consignment until the predetermined number of redeliveries, points are allocated and awarded to the recipient point section and the delivery person point section.

13. 13. A delivery system with point redemption according to claim 12, wherein in the case of pick-up, points equivalent to the initial receiving points are awarded to the recipient point department as cooperation points.

Images