Delivery company terminal program, delivery company terminal, and user terminal program

Abstract

To provide a delivery management device capable of preventing personal information leakage in a delivery process and confirming the identity of a sender.SOLUTION: A delivery management server 2 includes: identification information transmission means for transmitting delivery identification information that can identify a delivery request for an item to a user terminal 3; sender information registration means for receiving sender information including sender's personal information and settlement information; delivery information acquisition means for acquiring delivery information consisting of delivery destination information and item information from the user terminal 3; identity confirmation means for confirming identity of the sender based on the settlement information; delivery charge calculation means for calculating a delivery charge based on the delivery information; and settlement means for settling the delivery charge based on the settlement information when the identity of the sender is successfully confirmed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a delivery management device and a delivery management program, and more particularly to a delivery management device and a delivery management program that verify the identity of a sender. [Background technology]

[0002] When a shipper wishes to have a package delivered to a consignee, it is common for them to use a delivery service. The shipper brings the item to be delivered to the delivery company's office (or a parcel acceptance store such as a convenience store or hotel). The shipper then handwrites the necessary information (the names, addresses, and telephone numbers of the shipper and consignee, and the item to be delivered) on a delivery slip, attaches the delivery slip to the item to be delivered, and requests the delivery of the package. According to the delivery management system described in Patent Document 1, the necessary information on the delivery slip can be coded and encrypted to prevent the personal information of the shipper and consignee from being leaked during the delivery process. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-031969 Summary of the Invention [Problem to be solved by the invention]

[0004] Although the technology disclosed in Patent Document 1 can prevent the leakage of personal information during the delivery process, there is a problem in that a person requesting delivery of a package can falsify their identity. This means that when the recipient receives the package, they cannot verify the authenticity of the sender, and there is also the risk of a suspicious object being delivered unsolicited by an unknown sender. In other words, it is possible to easily commit acts that harm others by using the goods delivery system.

[0005] The present invention has been made in consideration of the above-mentioned problems, and its purpose is to provide a delivery management device and a delivery management program that can prevent the leakage of personal information during the delivery process and can verify the identity of the sender. [Means for solving the problem]

[0006] The above-mentioned problem is solved by the delivery company terminal program of the present invention, which is connected to a delivery management device that manages delivery of items via an electric communication line and is used by a delivery company that collects and delivers delivery items, by making the computer of the delivery company terminal function as a delivery identification information reading means that reads delivery identification information that is attached to the delivery item and can identify the delivery request for the delivery item, a delivery status notifying means that notifies the delivery management device of the delivery status of the delivery request associated with the delivery identification information, a delivery information acquiring means that acquires delivery information including delivery destination information related to the delivery destination of the delivery request associated with the delivery identification information and item information related to the delivery item, and an identity verification requesting means that requests identity verification by comparing personal information of the sender related to the delivery request associated with the delivery identification information with the payment information of the sender. The identity verification requesting means requests the identity verification without transmitting the personal information of the sender and the payment information of the sender to the delivery management device. This is solved by:

[0008] In addition, the above The delivery identification information reading means reads the encoded identification information obtained by encoding the delivery identification information. and is suitable 。

[0009] In addition, the above The delivery status includes at least one of redelivery information regarding redelivery of the delivery item and storage period information regarding the period during which the delivery item was stored in a predetermined location, and the computer further functions as a delivery status receiving means for receiving input of the delivery status of the delivery request associated with the delivery identification information. and is suitable 。

[0010] Also, A delivery company terminal including a processor, the processor executing the delivery company terminal program. and is suitable 。

[0011] Furthermore, the above-mentioned problem is solved by the user terminal program of the present invention, which is connected to a delivery management device that manages delivery of goods via an electric communication line and is used by a sender of a delivery item, and which includes a delivery identification information acquisition means that acquires delivery identification information that can identify a delivery request related to the delivery item from the delivery management device, a sender information acceptance means that accepts input of sender information including personal information of the sender and payment information used to settle a delivery fee and to confirm the identity of the sender, and transmits the input to the delivery management device, a delivery information acceptance means that accepts input of delivery information including delivery destination information related to the delivery destination of the delivery request and item information related to the delivery item, and transmits the input to the delivery management device, and an identity confirmation result notification receiving means that receives a notification of the result of the identity confirmation using the payment information from the delivery management device. ,before and a means for outputting the delivery identification information. The identity verification is performed using the personal information and payment information of the sender registered in the delivery management device, and the delivery identification information output means outputs the delivery identification information based on whether the identity verification is successful. This is solved by:

[0012] Also, The delivery identification information output means prints out encoded identification information obtained by encoding the delivery identification information. and is suitable 。 [Effects of the Invention]

[0016] According to the present invention, it is possible to prevent leakage of personal information during the delivery process and to verify the identity of the sender. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a delivery management system. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a delivery management server. [Figure 3] FIG. 2 is a diagram showing the data structure of a sender information database. [Figure 4] FIG. 2 is a diagram showing the data structure of a delivery management database. [Figure 5] FIG. 10 is a diagram showing the data structure of a delivery fee table. [Figure 6] FIG. 4 is a diagram showing the data structure of an additional charge table. [Figure 7] FIG. 2 is a diagram illustrating a functional configuration of a delivery management server. [Figure 8] FIG. 2 is a diagram illustrating the functional configuration of a user terminal. [Figure 9] FIG. 2 is a diagram illustrating a functional configuration of a sales office terminal. [Figure 10] FIG. 10 is a diagram showing a sequence of goods delivery. [Figure 11] FIG. 10 is a diagram showing an input screen for a delivery request. [Figure 12] FIG. 10 is a diagram showing the flow of a delivery fee calculation process. [Figure 13] FIG. 10 is a diagram illustrating a functional configuration of a delivery management server according to a second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0018] A delivery management system 1 (hereinafter referred to as this system 1) according to one embodiment of the present invention (hereinafter referred to as this embodiment) will be described below with reference to Figures 1 to 12. Note that the embodiment described below is intended to facilitate understanding of the present invention and does not limit the present invention. In other words, the present invention may be modified or improved without departing from the spirit thereof, and of course, the present invention also includes equivalents thereof.

[0019] <<Outline of the embodiment>> First, an overview of the system 1 will be described. This system 1 is used to manage the delivery of goods by acquiring delivery information from a user terminal 3 used by a sender who wishes to have an item delivered, transmitting the delivery information to a delivery company's business terminal 4, and acquiring the delivery status from the business terminal 4. Then, goods are delivered by affixing delivery identification information for identifying delivery information to the goods without using a slip containing personal information. This prevents the leakage of personal information of the sender and consignee. In addition, because the sender's identity is confirmed based on payment information (credit card user information), it is possible to prevent unsolicited delivery of suspicious items from senders of unknown identity.

[0020] FIG. 1 is a diagram showing an overview of the system 1. This system 1 is composed of a delivery management server 2 managed and operated by a delivery company, a user terminal 3 used by the sender, and an office terminal 4 used by delivery personnel at the delivery company's office. The delivery management server 2, user terminal 3, and office terminal 4 are connected to each other so that they can communicate with each other via a wide-area telecommunications line available to the public (e.g., an Internet line). Although a single user terminal 3 is shown in FIG. 1, multiple user terminals 3 may be connected to the Internet line. Similarly, multiple office terminals 4 may be connected to the Internet line.

[0021] The delivery management server 2 as a delivery management device is a server device managed and operated by a delivery company that provides delivery services for goods. The functions of the delivery management server 2 may be realized by a plurality of server devices. The user terminal 3 is an information communication terminal used by the sender. Specifically, the user terminal 3 may be a mobile terminal such as a smartphone, a tablet terminal, a PDA, or a laptop computer, or may be a desktop PC.

[0022] The business office terminal 4 is a terminal used at a business office (or a baggage acceptance store such as a convenience store or accommodation facility) that collects and delivers items for delivery. In other words, the business office terminal 4 is a terminal used at each business office to obtain delivery information for items and input delivery status. The business office terminal 4 can also be a tablet terminal, smartphone, PDA, laptop computer, or desktop PC. In this embodiment, the office terminal 4 includes both a terminal used by a manager who manages deliveries at the office and a mobile terminal used by delivery personnel. The office also includes a collection point or storage area where delivery items can be collected and temporarily stored.

[0023] The following describes the process from when a sender requests delivery of an item using the system 1 to when the item is delivered to a recipient. (1) Prior to requesting delivery of an item, the sender operates the user terminal 3 to request the delivery management server 2 to issue a delivery code, and receives the delivery code. The delivery code is a two-dimensionally encoded version of delivery identification information issued for each delivery request of an item, which is then converted into a QR code (registered trademark).

[0024] (2) Next, the sender registers sender information consisting of the sender's personal information (such as name, address, and telephone number) and payment information (such as a credit card number) for settling the delivery fee. The sender then inputs delivery information consisting of delivery destination information about the consignee and item information about the item to be delivered into the user terminal 3 and transmits it to the delivery management server 2. Here, the sender information and delivery information are registered and managed in the delivery management server 2 in association with delivery identification information. The registration of sender information and the input of delivery information may be performed simultaneously or at different times. That is, the sender information may be registered first, and then the delivery information may be input.

[0025] (3) After that, the delivery management server 2 verifies the identity of the sender. That is, it inquires about the credit card user information of the issuer of the credit card that the sender desires as the payment method, and determines whether or not it matches the personal information of the sender received from the user terminal 3. If the identity verification fails, the delivery request from the sender may not be accepted. (4) Next, the delivery management server 2 determines whether delivery is possible based on the delivery information. That is, it estimates the lead time required for delivery of the item and determines whether delivery of the item is possible by the desired delivery date.

[0026] (5) If the delivery management server 2 determines that the item can be delivered, it calculates the delivery fee based on the delivery information and notifies the delivery fee to the user terminal 3 used by the sender. The method of calculating the delivery fee will be described later. (6) After receiving notification of the delivery fee, the sender attaches the delivery slip with the delivery code (QR code) printed on it to the item and takes it to the nearest branch office.

[0027] (7) The delivery person at the office who receives the delivery item acquires delivery information from the delivery management server 2. Specifically, the office terminal 4 reads the delivery code attached to the delivery item and acquires a delivery identification number that can identify the delivery information. The office terminal 4 accesses the delivery management server 2 and acquires the delivery information associated with the delivery identification number. (8) The delivery person delivers the item to the recipient based on the delivery information and sends a notification to the delivery management server 2 that the delivery has been completed.

[0028] (9) Upon receiving the notification of delivery completion, the delivery management server 2 finally processes the payment of the delivery fee. The sender can access the delivery management server 2 to check the delivery status and confirm that delivery has been completed.

[0029] In the past, senders would attach a delivery slip containing personal information to items to be delivered when making delivery requests, which posed a problem of personal information being leaked to third parties during the delivery process. In contrast, this system 1 does not attach a delivery slip containing personal information to items, making it possible to prevent the leakage of personal information. In addition, in the past, senders could make delivery requests by falsifying their own identity, making it impossible for consignees to verify whether the delivered goods were sent by the real sender. In contrast, the present system 1 verifies the sender's identity by collating the sender's personal information based on payment information, thereby preventing goods from being unilaterally delivered to a consignee by falsifying their identity.

[0030] <<Hardware configuration of delivery management server 2>> 2 shows the hardware configuration of the delivery management server 2. As shown in the figure, the delivery management server 2 includes a CPU 21, a ROM 22, a RAM 23, an input unit 24, a display unit 25, a communication interface 26, and a storage unit 27, which are interconnected via a bus line such as a data bus.

[0031] The CPU 21 executes various programs stored in the ROM 22 and the storage unit 27, and performs various information processing and control operations based on temporary data stored in the RAM 23. The CPU 21 executes a delivery management process and a delivery fee calculation process, which will be described later, in accordance with a delivery management program 275 stored in the storage unit 27.

[0032] The ROM 22 corresponds to the main storage device of the delivery management server 2, and is a non-volatile memory in which the basic input / output program of the delivery management server 2 and the like are stored. The RAM 23 is a volatile memory that has a program storage area and a data storage area and forms a work area for temporarily storing data required for the CPU 21 to execute processing. In this embodiment, sender information, delivery information, a delivery fee table 273, an additional fee table 274, a delivery management program 275, and the like, which will be described below, are temporarily stored in the RAM 23.

[0033] The input unit 24 is an input device including a keyboard and a mouse, and can accept input from an administrator who manages the delivery management server 2, etc. The display unit 25 is a display device made up of an LCD (liquid crystal display), and can be used when performing maintenance and management of the delivery management server 2.

[0034] The communication interface 26 is connected to a public telecommunications line such as the Internet, and performs bidirectional data communication with a plurality of user terminals 3 and a plurality of business terminals 4 . Specifically, the communication interface 26 receives sender information and delivery information from the user terminal 3, and transmits a delivery code that encodes delivery identification information to the user terminal 3. The communication interface 26 also transmits delivery information to the office terminal 4, as well as delivery status information (information such as delivery completed, redelivery, or temporary storage).

[0035] The storage unit 27 is a non-volatile auxiliary storage device such as an HDD (Hard Disc Drive) or an SSD (Solid State Drive), etc. The storage unit 27 stores a sender information database 271, a delivery management database 272, a delivery fee table 273, and an additional fee table 274, as well as application programs such as a delivery management program 275, which will be described later.

[0036] FIG. 3 shows an example of the data structure of the sender information database 271. As shown in FIG. 3, the sender information database 271 is made up of records including a user ID, a password, personal information such as name, sex, date of birth, address, and telephone number, and payment information such as payment method, card number, and expiration date. The user ID is information that can identify the sender and is issued by the delivery management server 2. The password is information used for user authentication when the sender accesses the delivery management server 2 and is stored in a state that has undergone a predetermined encryption process. The name, gender, date of birth, address, and telephone number are the sender's name, gender, date of birth, address, and telephone number, respectively.

[0037] The payment method and card number are information that can identify the credit card, debit card, etc. that the sender will use to pay the delivery fee. The expiration date is information that indicates the expiration date if the credit card, debit card, etc. has an expiration date. Although Figure 3 shows a single payment information item, the storage area for multiple payment information items may be provided. Sender information database 271 stores sender information by sender information registration unit 202, which will be described later.

[0038] FIG. 4 shows an example of the data structure of the delivery management database 272 serving as the delivery information storage means. As shown in Figure 4, the delivery management database 272 is composed of records including delivery identification information, a user ID, delivery information such as the delivery origin address, the consignee's name, the delivery destination address, the item name, the desired delivery date and time, the delivery fee, and delivery status such as the storage location, storage period, and redelivery. The delivery identification number is issued for each delivery request by the delivery code issuing unit 201, which will be described later, and is an identification number that can identify the delivery request. The user ID is information that can identify the person who pays the delivery fee, and is, for example, the user ID of the sender.

[0039] The origin address, consignee name, destination address, product name, and desired delivery date and time are delivery information entered by the sender from user terminal 3, and indicate that an item with the specified product name will be delivered from the origin address to the destination address on the desired delivery date and time. The delivery fee is calculated based on the delivery information by a delivery fee calculation unit 206. The method for calculating the delivery fee will be described later with reference to FIG.

[0040] The delivery status is information that can identify the delivery status of the delivery item, and includes information that can identify the storage location of the delivery item, information that can identify the storage period, and the number of redeliveries. The storage location is information that can identify the location (including a sales office, collection point, or storage facility, etc.) to which the item has been delivered if delivery of the item has not been completed, and information indicating that delivery has been completed is stored if delivery of the item has been completed to the destination. The storage period stores information that can identify the period during which the item was temporarily stored in a predetermined storage location without being delivered. If the item cannot be delivered due to the recipient's absence and redelivery is performed, the number of times this has been done (number of redelivery attempts) is stored.

[0041] FIG. 5 shows an example of the data structure of the delivery fee table 273. As shown in Figure 5, delivery fee table 273 specifies the delivery fee for delivering an item from one office to another, for each of multiple offices where a delivery company collects and delivers items. The delivery fees stored in delivery fee table 273 are determined based on the delivery distance between each office. Delivery fee table 273 has multiple delivery fee tables prepared in advance according to the size, weight, and delivery conditions of the item to be delivered, and one delivery fee table is selected and referenced based on the size, weight, and conditions of the item to be delivered. As will be described later, the delivery fee calculation unit 206 calculates the overall delivery fee based on the delivery fee based on the delivery fee table 273 (referred to as the basic delivery fee) and the additional delivery fee described later with reference to Figure 6.

[0042] Fig. 6 shows an example of the data structure of the additional fee table 274. (a) in Fig. 6 shows the additional fee for redelivery, (b) in Fig. 6 shows the additional fee for storage period, and (c) in Fig. 6 shows the additional fee for special delivery services. Figure 6 (a) shows the predetermined additional charge for the number of times (re-delivery count) that a delivery person from a branch office goes to a delivery address to make a delivery, but the recipient is not at home, so the delivery item is taken back to the branch office and the delivery needs to be made again at a later date.

[0043] FIG. 6(b) shows a predetermined additional charge for the storage period during which the delivery item is temporarily stored at a business office (including a collection point and a storage facility) without being delivered to the delivery destination. Figure 6(c) shows the additional charges that are predetermined for special delivery services (for example, "urgent delivery" for short-term delivery, or "international delivery" for delivery to a foreign country).

[0044] The CPU 21 loads and executes the delivery management program 275 stored in the storage unit 27 into a program storage area of ​​the RAM 23. As a result, the delivery management program 275 as software and the above hardware devices (specifically, the CPU 21, the ROM 22, the RAM 23, the communication interface 26, and the storage unit 27) work together to realize the delivery management process and the delivery fee calculation process described below.

[0045] Like the delivery management server 2, the user terminal 3 and the sales office terminal 4 also have a basic hardware configuration consisting of a CPU, ROM, RAM, input unit, display unit, communication interface, and memory unit (not shown). The user terminal 3 and the sales office terminal 4 may be configured to include an input unit such as a touch panel, an optical reader such as a QR code reader for reading QR codes, or a camera for taking photographs. The user terminal 3 and the sales office terminal 4 may also be configured to include a printer as an output unit.

[0046] <<Functional configuration of delivery management server 2>> Next, the functional configuration of the delivery management server 2 will be described. 7 shows the functional configuration of the delivery management server 2. The delivery management server 2 has a delivery code issuing unit 201, a sender information registration unit 202, a delivery information acquisition unit 203, a personal identification unit 204, a delivery feasibility determination unit 205, a delivery fee calculation unit 206, a settlement unit 207, and a delivery status acquisition unit 208.

[0047] When the delivery code issuing unit 201, which serves as an identification information transmitting means, receives a delivery code issuance request from the user terminal 3 via a telecommunications line, it issues delivery identification information that can identify the delivery request. The delivery code issuing unit 201 then generates a delivery code by encoding the delivery identification information into a QR code and transmits it to the user terminal 3. The QR code generated by encoding the identification information corresponds to encoded identification information. Although the description has been given assuming that the delivery code issuing unit 201 generates a delivery code, this is not limiting. The delivery code issuing unit 201 issues delivery identification information and transmits the delivery identification information to the user terminal 3 without encoding it. In this case, the user terminal 3 encodes the received delivery identification information to generate a delivery code.

[0048] The sender information registration unit 202, which serves as a user information registration means, receives sender information from the user terminal 3 and registers it in the sender information database 271. The sender information may be registered before or after the issuance of the delivery code described above. As described above, the sender information includes the sender's personal information and information about the payment method used by the sender to pay the delivery fee.

[0049] The delivery information acquisition unit 203 as a delivery information acquisition means receives delivery information from the user terminal 3, and registers the information in the delivery management database 272 in association with delivery identification information and a user ID. As described above, the delivery information includes the address of the sender, the name of the recipient, the delivery address, the name of the item to be delivered, and the desired delivery date and time.

[0050] The identity verification unit 204, which serves as an identity verification means, verifies the identity of the sender. More specifically, the identity verification unit 204 references the sender information database 271 to acquire the registered personal information and payment information of the sender. Next, the identity verification unit 204 inquires about the credit card user information of the credit card in the payment information from the issuing company of the credit card. The identity verification unit 204 then verifies the identity of the sender by determining whether the sender's personal information (including at least name, sex, and date of birth) matches the credit card user information (including at least name, sex, and date of birth).

[0051] The delivery feasibility determination unit 205 references the delivery management database 272 and determines whether the delivery request can be carried out based on the delivery information. More specifically, the delivery feasibility determination unit 205 estimates the lead time required for delivery (the required delivery time, i.e., the number of days and time required to deliver the item requested for delivery) from the relative positions of the delivery source and delivery destination. The lead time required for delivery is estimated by referencing a required delivery time table that stores required delivery times predetermined based on past delivery records, etc., for combinations of multiple delivery bases. The delivery feasibility determination unit 205 then determines that delivery is possible if the estimated delivery date and time obtained by adding the lead time to the current time is before the desired delivery date and time, and determines that delivery is not possible if the estimated delivery date and time is after the desired delivery date and time. The delivery possibility determination unit 205 may determine whether or not a delivery request can be executed by inquiring (performing a credit inquiry) with an external credit card company to see whether or not payment is possible using the payment method desired by the sender.

[0052] The delivery fee calculation unit 206, which serves as a delivery fee calculation means, refers to the delivery management database 272, determines the basic delivery fee and additional delivery fee based on the delivery information and delivery status, and calculates the delivery fee by adding these together. The basic delivery fee is the delivery fee required to deliver an item from the business office corresponding to the address of the delivery origin to the business office corresponding to the address of the delivery destination, and is a fee that is stored in advance in the delivery fee table 273. The delivery fee table 273 stores fees based on the delivery distance between business offices. This allows the delivery fee calculation unit 206 to calculate the delivery fee based on the delivery distance of the item to be delivered, thereby improving fairness in setting delivery fees.

[0053] The additional delivery fee is a fee that is collected on top of the basic delivery fee. Specifically, the additional delivery fee consists of an additional redelivery fee incurred when the delivery item is redelivered, an additional storage fee incurred when the delivery item is left at a collection point or storage facility, and a special fee incurred when special delivery services (e.g., express delivery or international delivery) are used. The delivery fee calculation unit 206 calculates the delivery fee based on the redelivery information stored in the delivery management database 272. This makes it possible to reflect the costs incurred by redelivery in the delivery fee, thereby increasing fairness in setting delivery fees.

[0054] Furthermore, the delivery fee calculation unit 206 calculates the delivery fee based on the storage period (storage period information) stored in the delivery management database 272. This makes it possible to reflect the costs incurred in storing the delivery item in the delivery fee, thereby improving fairness in setting the delivery fee.

[0055] The settlement unit 207 as a settlement processing means settles the delivery fee based on the settlement means desired by the sender, that is, the settlement information stored in the sender information database 271 . The delivery status acquisition unit 208 as a delivery status acquisition means receives the delivery status of the item from the business terminal 4 and stores the delivery status in the delivery management database 272 .

[0056] <<Functional configuration of user terminal 3>> Next, the functional configuration of the user terminal 3 will be described. 8 shows the functional configuration of the user terminal 3. The user terminal 3 has a delivery code acquisition unit 301, a sender information input unit 302, a delivery information transmission unit 303, and a delivery status acquisition unit 304.

[0057] The delivery code acquisition unit 301 acquires a delivery code by receiving the delivery code transmitted by the delivery code issuing unit 201 of the delivery management server 2. The delivery code can be received as image data of a QR code. The delivery code acquisition unit 301 decodes the received QR code to acquire delivery identification information from the delivery code. The sender information input unit 302 accepts input of sender information consisting of the sender's personal information and payment information, and transmits the input sender information to the delivery management server 2. The sender information input unit 302 also receives from the delivery management server 2 a user ID that can identify the sender.

[0058] The delivery information transmitting unit 303 accepts input of delivery information consisting of delivery destination information and product information. Then, the delivery information transmitting unit 303 associates the input delivery information with the delivery identification information acquired by the delivery code acquiring unit 301 and the user ID acquired by the sender information input unit 302, and transmits the information to the delivery management server 2.

[0059] The delivery status acquisition unit 304 transmits delivery identification information to the delivery management server 2 and acquires the delivery status of the delivery item corresponding to the delivery identification information from the delivery management server 2. The acquired delivery status is displayed on the display unit of the user terminal 3. This allows the sender to check the delivery status of the item for which they have requested delivery.

[0060] <<Functional configuration of sales office terminal 4>> Next, the functional configuration of the business office terminal 4 will be described. 9 shows the functional configuration of the business office terminal 4. The business office terminal 4 has a delivery information acquisition unit 401, a delivery status notification unit 402, and a delivery item detection unit 403.

[0061] The delivery information acquisition unit 401 receives delivery information transmitted by the delivery management server 2 to acquire delivery information. The delivery status notification unit 402 receives input of delivery status from delivery personnel at the office, and transmits the input delivery status to the delivery management server 2. The delivery item detection unit 403 detects the delivery item brought in by the sender. Specifically, the delivery item detection unit 403 detects the dimensions and weight of the delivery item brought in by the sender. This enables the delivery staff at the office to determine whether the delivered delivery item is appropriate.

[0062] <<Delivery management process sequence>> Next, the flow of delivery management processing and goods delivery carried out between the delivery management server 2, the user terminal 3, and the office terminal 4 will be described with reference to FIGS. 10, 11, and 12. FIG. FIG. 10 shows the sequence of the delivery management process. First, the CPU of the user terminal 3 determines whether or not the sender has performed an operation to request a delivery code (step S11). If it is determined that the sender has not performed an operation to request a delivery code (step S11: No), the CPU of the user terminal 3 waits until the sender performs an operation to request a delivery code.

[0063] On the other hand, if it is determined that an operation to request a delivery code has been performed (step S11: Yes), the CPU of the user terminal 3 requests a delivery code from the delivery management server 2 (step S12). Upon receiving the delivery code request, the CPU 21 of the delivery management server 2 generates a delivery code (step S13). That is, the CPU 21 issues delivery identification information and encodes the delivery identification information to generate a delivery code in the form of a QR code. The CPU 21 then transmits the generated delivery code to the user terminal 3 (step S14). When the CPU of the user terminal 3 receives the delivery code, it decodes the QR code to obtain delivery identification information.

[0064] Next, the CPU of the user terminal 3 determines whether sender information has been input (step S15). That is, the CPU of the user terminal 3 displays a delivery request input screen on the display unit of the user terminal 3 and accepts input of the sender's personal information and payment information. 11(a) shows the delivery request screen with the "Personal Information" tab selected, which allows the sender to enter personal information. As shown in FIG. 11(a), a "Register" button is provided along with input fields for the sender's personal information, which includes the sender's name, gender, date of birth, address, and telephone number. The CPU of the user terminal 3 determines whether the personal information has been entered and the "Register" button has been pressed.

[0065] FIG. 11(b) shows the delivery request screen with the "Payment Information" tab selected, allowing the sender to enter information (payment information) regarding the payment method desired by the sender. As shown in FIG. 11(b), the sender can enter the payment method they wish to use when paying the delivery fee. While only one payment method may be registered, it is also possible to register multiple payment methods in advance. This allows the sender to specify the payment method when making a delivery request simply by selecting the desired payment method from the pre-registered payment methods, and also makes it possible to use multiple payment methods depending on the content of the delivery request, for example. If it is determined that sender information has not been input (step S15: No), the CPU of the user terminal 3 waits until sender information is input.

[0066] On the other hand, if it is determined that sender information has been input (step S15: Yes), it is determined whether delivery information has been input (step S16). That is, the CPU of the user terminal 3 displays a delivery request input screen on the display unit of the user terminal 3 and accepts input of delivery information. Figure 11(c) shows the delivery request screen with the "Delivery Request" tab selected, which allows entry of delivery information. As shown in Figure 11(c), there are fields for entering delivery destination information, including the recipient's name, address, telephone number, desired delivery date and desired delivery time, and delivery item information, including the item name, along with a "Register" button. The CPU of the user terminal 3 determines whether the delivery destination information and delivery item information have been entered and the "Register" button has been pressed. If it is determined that the delivery information has not been input (step S16: No), the CPU of the user terminal 3 waits until the delivery information is input.

[0067] On the other hand, if it is determined that the delivery information has been input (step S16: Yes), the CPU of the user terminal 3 transmits the sender information and delivery information together with the delivery identification information to the delivery management server 2 (step S17).

[0068] The CPU 21 of the delivery management server 2 verifies the identity of the sender based on the sender information (step S18). More specifically, the CPU 21 inquires about the credit card user via the communication interface 26 with the credit card issuer based on the payment information acquired in step S17. The CPU 21 then verifies the identity of the sender by comparing the sender's name, gender, and date of birth with the name, gender, and date of birth of the credit card user. If the sender's identity verification fails, the CPU 21 may notify the user terminal 3 that the sender's identity verification is not possible, and may not accept the delivery request.

[0069] Next, CPU 21 determines whether delivery is possible based on the delivery information (step S19). Specifically, the lead time required for delivery of the item is estimated based on the delivery information, and whether delivery of the item is possible by the desired delivery date and time is determined. If it is determined that delivery is possible, CPU 21 registers the delivery information in delivery management database 272 (step S20). Here, the CPU 21 may determine whether or not delivery is possible by inquiring (performing credit inquiry) with an external credit card company to see whether or not payment is possible using the payment method desired by the sender.

[0070] Next, CPU 21 calculates a delivery fee based on the delivery information (step S21). The method of calculating the delivery fee will be described later with reference to Fig. 12. After calculating the delivery fee, CPU 21 notifies user terminal 3 of the delivery fee (step S22).

[0071] After checking the delivery fee via the display of the user terminal 3, the sender prints the delivery code received in step S11 from the printer and affixes it to the delivery item. The sender then takes the delivery item with the delivery code affixed to the nearest delivery company office (or a parcel acceptance store such as a convenience store). As mentioned above, the delivery code does not contain personal information. Therefore, third parties cannot learn the delivery information, and the leakage of personal information of the sender and consignee is prevented.

[0072] The CPU of the office terminal 4 determines whether the delivery item has been brought in (step S23). In particular, a sales clerk at the office uses a QR code reader to read the code attached to the delivery item and obtains delivery identification information by decoding the QR code. The CPU of the office terminal 4 determines whether the delivery item has been brought in by determining whether delivery identification information has been input. If it is determined that the delivery item has not been brought in (step S23: No), the CPU of the office terminal 4 waits until the delivery item is brought in.

[0073] On the other hand, if it is determined that the delivery item has been brought in (step S23: Yes), the CPU of the office terminal 4 notifies the delivery status by sending information that can identify the office along with the delivery identification information to the delivery management server 2 (step S24). The CPU 21 of the delivery management server 2 registers the delivery status received from the business office terminal 4 in the delivery management database 272 (step S25). That is, the fact that the delivery item has been brought to the business office of the delivery company is registered in the delivery management database 272. Then, the CPU 21 notifies the business office terminal 4 of the delivery information (step S26).

[0074] Next, the CPU of the office terminal 4 determines whether or not the delivery status has been input (step S27). Here, the input of the delivery status is information indicating that the delivery item has been delivered to another office, collection point, storage facility, or consignee. The delivery status is also input by the delivery person when redelivery is required due to the consignee's absence. If it is determined that the delivery status has not been input (step S27: No), the CPU of the office terminal 4 waits until the delivery status is input. On the other hand, if it is determined that the delivery status has been input (step S27: Yes), the CPU of the office terminal 4 notifies the delivery management server 2 of the delivery status (step S28).

[0075] The CPU 21 of the delivery management server 2 registers the delivery status received from the office terminal 4 in the delivery management database 272 (step S29). Once the delivery status is registered, the CPU 21 recalculates the delivery fee (step S30). That is, changes in the delivery status (increase in the number of redeliveries or storage period) are reflected in the delivery fee. This makes it possible to set an appropriate delivery fee according to the delivery status, thereby improving fairness in setting delivery fees. The method of calculating the delivery fee will be described later with reference to FIG. 12.

[0076] Next, CPU 21 determines whether delivery has been completed (step S30). That is, CPU 21 determines whether information indicating that the item has been delivered to the consignee has been stored in delivery management database 272. If it is determined that delivery has not been completed (step S30: No), CPU 21 waits until further notification of the delivery status is received.

[0077] On the other hand, if it is determined that delivery is completed (step S30: Yes), the CPU 21 performs payment (step S31). That is, payment is made using the payment method designated in advance by the delivery sender. Then, the CPU 21 notifies the user terminal 3 that payment has been made (step S32).

[0078] Next, the delivery fee calculation process in steps S21 and S30 will be described with reference to FIG. FIG. 12 shows the flow of the delivery fee calculation process executed by the CPU 21 of the delivery management server 2. As shown in Figure 12, the CPU 21 first determines a basic delivery fee (step S41). Specifically, the CPU 21 selects one delivery fee table 273 from a plurality of delivery fee tables 273 prepared in advance based on the size and weight of the item to be delivered. The CPU 21 then determines the basic delivery fee by referring to the delivery fee table 273 based on the business office corresponding to the delivery origin address and the business office corresponding to the delivery destination address in the delivery information.

[0079] Next, the CPU 21 determines the redelivery fee (step S42). Specifically, the CPU 21 refers to the delivery management database 272 to acquire the number of redeliveries, and determines the additional redelivery fee shown in (a) of Fig. 6. Similarly, the CPU 21 refers to (b) and (c) of Fig. 6 to determine the additional storage fee and special fee. Finally, CPU 21 calculates the delivery fee by adding the additional fee determined in steps S42 to S44 to the basic delivery fee determined in step S41 (step S45). When calculating delivery fees for multiple items to be delivered, CPU 21 repeatedly executes steps S41 to S45.

[0080] By carrying out the delivery process of an item according to the above procedure, it is possible to prevent the leakage of personal information during the delivery process and to verify the identity of the sender. Furthermore, since delivery fees can be set according to the delivery distance and delivery status (redelivery and storage period) of the item, fairness in setting delivery fees can be increased.

[0081] Although one embodiment of the present invention has been described above, the present invention is not limited to the described embodiment, and various modifications can be made without departing from the spirit of the present invention. (1) For example, in the above-described embodiment, the sender's identity verification is performed after the delivery information is entered. However, this is not limited to this and may be performed before the consignee receives the delivery item. For example, a delivery person at a sales office may request the delivery management server 2 to verify the sender's identity before delivering the delivery item to the consignee, and if the sender's identity verification is successful, the delivery item may be delivered and the delivery fee may be settled.

[0082] (2) In the above embodiment, the delivery management server 2 determines whether or not to deliver the item after verifying the sender's identity, but the timing of determining whether or not to deliver the item is not limited to this. In other words, the determination may be made when the sender brings the item to the office. In this case, the delivery item detection unit 403 of the office terminal 4 detects the size or weight of the delivery item and transmits the detection result to the delivery management server 2. Then, the CPU 21 of the delivery management server 2 may refer to the item information in the delivery management database 272 and compare it with the detection result to determine whether or not delivery is possible.

[0083] (3) Furthermore, the delivery item detection unit 403 of the business terminal 4 may be an X-ray inspection device that inspects the contents of the delivery item. In this case, the delivery item detection unit 403 of the office terminal 4 acquires an X-ray image of the delivery item and transmits the acquired X-ray image to the delivery management server 2. The CPU 21 of the delivery management server 2 then performs image recognition processing on the received X-ray image to estimate the delivery item. The CPU 21 may then refer to the item information in the delivery management database 272 and compare it with the estimated delivery item to determine whether or not delivery is possible.

[0084] (4) The criteria for determining whether delivery is possible may differ depending on the delivery location. That is, some items may be determined to be deliverable and others may be determined to be undeliverable depending on the delivery location. In this case, the delivery management server 2 stores in advance a list of delivery items that are determined to be undeliverable for the delivery location in the storage unit 27. The delivery feasibility determination unit 205 can then determine whether delivery is possible by referencing the item information in the delivery management database 272 and comparing it with the list described above.

[0085] (5) In the above embodiment, delivery is performed based on delivery information entered in advance by the sender, but the delivery information may be modified later. When the delivery information is corrected, the delivery management server 2 again determines whether delivery is possible and calculates the delivery fee. This allows the delivery management server 2 to properly determine whether delivery is possible and calculate the delivery fee for the corrected delivery information, thereby improving fairness in the setting of fees.

[0086] <<Delivery Management Server According to the Second Embodiment>> Next, a delivery management server 2A according to a second embodiment of the present invention will be described with reference to FIG. 13 shows the functional configuration of the delivery management server 2A in the second embodiment. The delivery management server 2A has a delivery code issuing unit 201, a user information registration unit 202A, a delivery information acquisition unit 203, a personal identification unit 204, a delivery feasibility determination unit 205, a delivery fee calculation unit 206A, a payment unit 207A, a delivery status acquisition unit 208, and a payment management unit 209A. The delivery management server 2A of the second embodiment is obtained by changing the sender information registration unit 202 of the delivery management server 2 shown in Figure 7 to a user information registration unit 202A, changing the delivery fee calculation unit 206 to a delivery fee calculation unit 206A, changing the settlement unit 207 to a settlement unit 207A, and adding a settlement management unit 209A. Since the other configurations are the same as those of the delivery management server 2 of the first embodiment, the same reference numerals are used and explanations are omitted, and only the different parts will be explained.

[0087] In the second embodiment, the user information registration unit 202A has a function to register sender information as well as a function to register consignee information. Here, the consignee information is information including the consignee's personal information (such as name, address, and telephone number) and payment information (such as a credit card number) used by the consignee to pay the delivery fee. The consignee information is stored in a user information database 271A (not shown) that has the same data structure as the sender information database 271.

[0088] The settlement management unit 209A, which serves as a settlement management means, determines the delivery charges as sender-paid delivery charges to be borne by the sender and consignee-paid delivery charges to be borne by the consignee. Specifically, the settlement management unit 209A determines the charges incurred when the sender requests delivery of the item as sender-paid delivery charges, while determining the charges incurred due to the consignee's circumstances as consignee-paid delivery charges. More specifically, the settlement management unit 209A determines the delivery charges calculated based on the delivery information transmitted from the user terminal 3 (step S21 in FIG. 10) as sender-paid delivery charges. On the other hand, if the delivery destination is changed due to the consignee's circumstances, or if a redelivery fee or storage fee is incurred (step S30 in FIG. 10), it determines these as recipient-paid delivery charges. The settlement management unit 209A may determine the additional delivery charges as recipient-paid delivery charges, provided that either or both the sender and the consignee confirm that the additional delivery charges will be borne by the consignee. In other words, if an operation is input via the user terminal 3 used by the sender or the consignee to confirm that the consignee will bear the delivery charges, the additional delivery charges may be determined to be delivery charges borne by the consignee.

[0089] The delivery fee calculation unit 206A in the second embodiment calculates a sender-paid delivery fee and a consignee-paid delivery fee based on the determination result by the settlement management unit 209A. Then, the delivery fee calculation unit 206A stores the sender-paid delivery fee and the consignee-paid delivery fee in the delivery management database 272 shown in Figure 4 in association with the sender's user ID and the consignee's user ID, respectively. The settlement unit 207A then refers to the user information database 271A and settles the sender's share of the delivery fee based on the settlement information included in the sender information, and settles the consignee's share of the delivery fee based on the settlement information included in the consignee information. This allows the sender and consignee to appropriately share the delivery fee, thereby increasing fairness in setting delivery fees.

[0090] The programs executed by each device in the above-described embodiments and modifications are provided by being pre-installed in a storage medium (ROM or storage unit) included in each device, but this is not limiting. For example, the programs may be provided by being recorded in an installable or executable file format on a computer-readable storage medium such as a CD-ROM, CD-R, or DVD. Furthermore, the programs executed by each device in the above-described embodiments and modifications may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. [Explanation of symbols]

[0091] 1. Delivery management system 2, 2A Delivery management server (Delivery management device) 3. User terminal 4 Sales office terminal 21 CPU 22 ROM 23 RAM 24 Input section 25 Display section 26 Communication Interface 27 Memory section 201 Delivery code issuing unit (identification information transmitting means) 202 Sender information registration unit (user information registration means) 202A User information registration unit (user information registration means) 203 Delivery information acquisition unit (delivery information acquisition means) 204 Identity Verification Unit (Identity Verification Means) 205 Delivery possibility determination section 206, 206A Delivery fee calculation unit (delivery fee calculation means) 207, 207A payment unit (payment processing means) 208 Delivery status acquisition unit (delivery status acquisition means) 209A Payment Management Unit (Payment Management Means) 271 Sender Information Database 271A User Information Database 272 Delivery management database (delivery information storage means) 273 Shipping Fee Table 274 Additional Fee Table 275 Delivery Management Program 301 Delivery Code Acquisition Unit 302 Sender information input section 303 Delivery Information Transmission Unit 304 Delivery status acquisition unit 401 Delivery information acquisition department 402 Delivery Status Notification Section 403 Delivery Item Detection Unit

Claims

1. A computer of a delivery company terminal connected via a telecommunications line to a delivery management device that manages delivery of goods and used by a delivery company that collects and delivers delivery goods, a delivery identification information reading means for reading delivery identification information attached to the delivery item and capable of identifying the delivery request of the delivery item; a delivery status notification means for notifying the delivery management device of the delivery status of the delivery request associated with the delivery identification information; a delivery information acquisition means for acquiring delivery information including delivery destination information relating to the delivery destination of the delivery request associated with the delivery identification information and item information relating to the delivery item; and functioning as an identity verification requesting means for requesting identity verification by comparing the sender's personal information relating to the delivery request associated with the delivery identification information with the sender's payment information; The delivery company terminal program is characterized in that the identity verification requesting means requests identity verification using the personal information and payment information of the sender registered in the delivery management device.

2. 2. The delivery company terminal program according to claim 1, wherein the delivery identification information reading means reads encoded identification information obtained by encoding the delivery identification information.

3. The delivery status includes at least one of redelivery information regarding redelivery of the delivery item and storage period information regarding the period during which the delivery item was stored in a predetermined location, The delivery company terminal program according to claim 1, further comprising causing the computer to function as a delivery status receiving means for receiving input of the delivery status of the delivery request associated with the delivery identification information.

4. A delivery company terminal including a processor, the delivery company terminal causing the processor to execute the delivery company terminal program according to any one of claims 1 to 3.

5. A computer of a user terminal used by a sender of a delivery item, which is connected to a delivery management device that manages delivery of the item via an electric communication line, a delivery identification information acquisition means for acquiring, from the delivery management device, delivery identification information capable of identifying a delivery request relating to the delivery item; sender information receiving means for receiving input of sender information including personal information of the sender and payment information used for settling a delivery fee and for verifying the identity of the sender, and transmitting the information to the delivery management device; a delivery information receiving means for receiving input of delivery information including delivery destination information relating to the delivery destination of the delivery request and item information relating to the item to be delivered, and transmitting the information to the delivery management device; an identity verification result notification receiving means for receiving a notification of the result of the identity verification using the payment information from the delivery management device; functioning as a delivery identification information output means for outputting the delivery identification information; The identity verification is performed using the personal information and payment information of the sender registered in the delivery management device, The user terminal program is characterized in that the delivery identification information output means outputs the delivery identification information when the identity verification is successful.

6. 6. The user terminal program according to claim 5, wherein said delivery identification information output means prints out encoded identification information obtained by encoding said delivery identification information.

Images