JP6386780B2 - Delivery management method and delivery management system - Google Patents

Description

  The present invention relates to a delivery management method and a delivery management system, and more particularly, to a delivery management method and a delivery management system suitable for preventing misdelivery and facilitating management of delivery work using biometric authentication technology.

  In the distribution industry represented by the courier industry, a delivery service system using information processing technology by a computer system has become common. For example, a service is provided in which an orderer receives an inquiry number when ordering a courier and can refer to the delivery status using a Web page or the like.

  In addition, as in Patent Document 1, a technique is known in which an authentication code that can be used to verify the identity is displayed on a portable terminal and the identity can be authenticated by reading the authentication code in order to confirm the recipient. Further, as in Patent Document 2, a technology is known in which a delivery-related password is transmitted to a recipient's terminal, and the delivery item is delivered when the recipient knows the password.

  By the way, in the personal authentication, there are a method of inputting a password remembered by the person, a method of so-called biometric authentication using a biometric feature of the person, and the like. In particular, finger vein authentication using a finger vein pattern as a biometric feature for authentication is expected to be widely used because it can realize high security, high authentication accuracy, and a small and inexpensive device. For example, Patent Document 3 discloses a personal authentication device that reads a finger blood vessel pattern using transmitted light.

JP 2006-92507 A JP2007-168924 JP 2008-279275 A

  In the practice of conventional delivery flights, the delivery person confirms the name of the person who is notified and receives the signature or seal so that the person is assumed to be the recipient and delivers the package. . This increases the risk of a so-called impersonation trouble that is wrongly given to a person other than the person himself / herself.

  In addition, in the conventional delivery service, it is common to give a part of the document that has become a continuous form after signing as a receipt. Actually, the receipt is not sufficiently managed by the recipient, and if the recipient forgets that it has been received, it may cause trouble. Furthermore, there is a problem in that the system cannot be checked when a breach of the rule that the delivery of goods is completed even though the delivery person has not received a signature or seal.

  In addition, the recipient must disclose personal information such as name and address to the shipper of the package, and the name and address are usually displayed on the package sticker to be delivered. There is also a problem from the viewpoint of privacy protection.

  The present invention has been made to solve the above-mentioned problems, and its purpose is to enable the delivery management system to deliver the package to the recipient himself / herself safely and easily to solve the trouble on the system. In addition, it is an object of the present invention to provide a delivery management method and system excellent in protecting the privacy of users.

In order to solve the above-mentioned problem, the delivery management system according to the present invention is preferably a delivery management system in which a delivery person delivers a delivery sent by a sender to a recipient. A delivery management server that accesses and updates / stores a database related to management, an authentication server that accesses and updates / stores an authentication information database, authenticates biometric authentication information, and a deliverer terminal that inputs sender registration information; A recipient terminal to which the first authentication device is connected and inputs recipient registration information including the recipient's biometric information, and a delivery terminal to which the second authentication device is connected and carried by the deliverer during delivery are provided.
The delivery management server, the authentication server, the sender terminal, the recipient terminal, and the delivery terminal are connected by a network.

The sender terminal transmits the input sender registration information to the delivery management server and registers it in the database of the delivery management server, and the recipient terminal receives the recipient biometric information input from the first authentication device. Is sent to the delivery management server and registered in the databases of the delivery management server and the authentication server.
At the time of delivery, the delivery person requests biometric authentication such as finger vein authentication from the recipient.

  Then, the recipient is authenticated by the second authentication device, and the delivery terminal transmits the input biometric authentication information to the authentication server. The authentication server authenticates the authentication result of the authentication server to the delivery terminal. By displaying, the delivery person determines whether or not to deliver the delivery item to the person. After delivery, when delivering the delivery, the delivery terminal issues a receipt in accordance with an instruction from the delivery management server.

  According to the present invention, it is possible to deliver a package to the recipient himself / herself safely, to easily take measures against troubles on the system, and to realize a delivery management system excellent in protecting users' privacy.

1 is a schematic diagram of a delivery management system according to a first embodiment. It is a data flow figure of the delivery management system concerning a first embodiment. It is a block diagram of a delivery management server. It is a block diagram of an authentication server. It is a block diagram of a sender terminal. It is a block diagram of a recipient terminal. It is a block diagram of a delivery person terminal. It is a block diagram of an authentication device. It is a figure which shows sender registration data which concern on 1st embodiment. It is a figure which shows recipient registration data. It is a figure which shows the delivery transaction which concerns on 1st embodiment. It is a figure which shows authentication data. It is a sequence diagram which shows a process when a sender ships a delivery. It is a sequence diagram which shows a process when a recipient registers biometric information and receives a delivery thing later (the 1). It is a sequence diagram which shows a process when a recipient registers biometric information and receives a delivery thing later (the 2). It is a figure which shows a mode when authenticating by the delivery terminal. It is a figure which shows an example of a receipt. It is a figure which shows sender registration data which concern on 2nd embodiment. It is a figure which shows the delivery transaction which concerns on 2nd embodiment. It is the figure which showed the mode of the delivery label which concerns on 3rd embodiment.

  Hereinafter, embodiments according to the present invention will be described with reference to the drawings.

Embodiment 1
Hereinafter, a first embodiment will be described with reference to FIGS. 1 to 16.
First, the configuration of the delivery management system according to the first embodiment of the present invention will be described with reference to FIGS. 1 and 8.

  FIG. 1 is a schematic diagram of a delivery management system according to the first embodiment. FIG. 2 is a data flow diagram of the delivery management system according to the first embodiment of the present invention.

  The delivery management system 1 according to the present embodiment is a delivery management system that manages delivery operations by a sender site of a sender who delivers a package, a recipient site of a recipient who receives the package, a delivery site that delivers the package, and a delivery company. It consists of a center, logistics collection, shipping delivery base and collection center.

  The sender site has a sender terminal 200, from which the sender accesses the delivery management server 100 of the delivery management center via the network 60 as a sender, and registers necessary information in the delivery management DB 190. It is also possible to order the delivery 10 to be sent online to the delivery management center via the network 60. Here, the network 60 may be a global network such as the Internet, or a network network operated by a delivery company.

  The shipper asks the delivery person to come to the house or company, or goes to the delivery base 810 and hands over the delivery item 10 to the delivery company.

  The recipient site includes a recipient terminal 300, from which the recipient accesses the delivery management server 100 of the delivery management center via the network 60 as a recipient, and registers necessary information in the delivery management DB 190. At this time, the finger vein authentication related to the person is registered from the authentication device 380 connected to the recipient terminal 300. Recipient registration information is stored in the delivery management DB 580 and authentication information DB 160 managed by the delivery management server 100 and the authentication server 500, respectively. In the present embodiment, the recipient's finger vein authentication is registered from the authentication device 380 connected to the recipient terminal 300. However, the recipient's finger vein authentication may be registered. Finger vein authentication may be registered from a terminal connected to the network. In addition, registration of finger vein authentication may be performed from the authentication device 480 connected to the deliverer terminal brought by the deliverer.

The delivery 10 is delivered to the recipient designated by the delivery person via the delivery base 810 and the collection centers 800 in various places. At that time, the delivery status is input from a terminal at each delivery site 810 or the collection center 800, and the delivery status of the delivery 10 is reported to the delivery management server.
In FIG. 1, the delivery management center and the collection center are illustrated as different ones, but they may be installed at the same point.

  The deliverer site is a site where the deliverer is constantly moving on a truck or the like, and the deliverer brings a delivery person terminal 400 for managing his own delivery work and receiving instructions from the delivery management server 100. Yes. Then, the delivery person terminal 400 accesses the delivery management server 100 via the base station 70 and the network 70 by radio.

  Further, an authentication device 480 is connected to the deliverer terminal 400 so that the finger vein authentication of the recipient can be performed.

  The recipient of the delivery 10 makes an inquiry to the delivery management server 100 from the delivery terminal 400 when finger vein authentication is performed by the authentication device 480. Then, the delivery management server 100 performs finger vein authentication by the authentication server 500 and returns the authentication result to the delivery person terminal 400. In addition, if the recipient is a genuine recipient, an instruction to issue a receipt is also given.

  When the delivery person sees the result and determines that the authenticated person is the genuine recipient, the delivery person hands over the delivery item 10 and at the same time, prints the receipt 30 and hands it over to the recipient. .

Next, a hardware configuration and a software configuration in each device of the delivery management system will be described with reference to FIGS.
FIG. 3 is a configuration diagram of the delivery management server. FIG. 4 is a configuration diagram of the authentication server. FIG. 5 is a configuration diagram of the sender terminal. FIG. 6 is a block diagram of the recipient terminal. FIG. 7 is a block diagram of the delivery terminal. FIG. 8 is a configuration diagram of the authentication apparatus.

  As shown in FIG. 3, the hardware configuration of the delivery management server 100 includes a CPU 102, a main storage device 108, a display I / F 104, an input / output I / F 106, a network I / F 850, and an auxiliary storage I / F 112 connected by a bus. It is a thing.

  The display device 110 displays an operating status monitor and output results. Input / output devices such as a keyboard 120 and a mouse 122 are connected to the input / output I / F 106, and an administrator inputs commands and the like from these input / output devices. A network 60 such as a LAN or a WAN is connected to the network I / F 110 and communicates with an external device via the I / F. In this example, it is assumed that the authentication server 500 in the delivery management center is connected by a LAN. A storage device such as a hard disk device 160 that stores data and programs is connected to the auxiliary storage I / F 112. The hard disk device 160 may be connected on the array to form a disk array.

  Business processing application programs, an OS, and the like are stored in the hard disk device 160, loaded into the main storage device 108 when executed, and executed by the CPU 102.

  In particular, the delivery management server 100 includes a delivery management program 180 for accessing the delivery management DB 190 and an authentication server interface program 182 that exchanges authentication data with the authentication server and receives an authentication result.

  The hardware configuration of the authentication server 200 may be the same as that of the delivery management server shown in FIG. 3, as shown in FIG.

  In particular, as a program executed as the authentication server 200, the degree of similarity between the authentication DB management program 580 for accessing the authentication DB 590, and the registered finger vein pattern and the finger vein pattern input for authentication is shown. There is an authentication program 582 that performs calculation and determination, and a delivery management server interface program 584 that exchanges authentication data with the delivery management server 100 and transmits an authentication result.

  The hardware configuration of the sender terminal 200 is realized by, for example, a general personal computer as shown in FIG.

In the sender terminal 200, a CPU (Central Processing Unit) 202, a main storage device 204, a network I / F 206, a display I / F 208, an input / output I / F 210, and an auxiliary storage I / F 212 are connected by a bus. ing.
The CPU 202 controls each part of the sender terminal 200 and loads and executes a necessary program in the main storage device 204.

The main storage device 204 is usually composed of a volatile memory such as a RAM, and stores a program executed by the CPU 202 and data to be referred to.
The network I / F 206 is an interface for connecting to the network 60.

The display I / F 208 is an interface for connecting a display device 20 such as an LCD (Liquid Crystal Display).
The input / output I / F 210 is an interface for connecting an input / output device. In the example of FIG. 5, a keyboard 230 and a mouse 232 of a pointing device are connected.

  The auxiliary storage I / F 212 is an interface for connecting an auxiliary storage device such as an HDD (Hard Disk Drive) 250 and a DVD drive (Digital Versatile Disk) 240.

  The HDD 250 has a large storage capacity, and stores a program for executing this embodiment. A web browser 260 and a delivery management client program 262 are installed in the sender terminal 200. In order for the sender to access the delivery management server 100 from the sender terminal 200, the sender may be able to access from the general Web browser 260, or may be accessible only by the dedicated delivery management client program 262. Good.

  The DVD drive 240 is a device that writes data to or reads data from an optical disk such as a DVD or CD, and the delivery management client program 262 installs, for example, what is provided by a CD-ROM. be able to.

  Similarly to the sender terminal 200, the hardware configuration of the recipient terminal 300 is also realized by a general personal computer as shown in FIG.

  However, as a different place, the recipient terminal 300 has a serial I / F 314 and an authentication device 380 is connected thereto. The serial I / F 314 is, for example, a USB (Universal Serial Bus) interface. The authentication device 380 connected to the recipient terminal 300 is used for registering the recipient's biometric information.

  In addition, a Web browser 360, a delivery management client program 362, and an authentication device driver 364 are installed in the HDD 350 connected to the recipient terminal 300.

  In order for the recipient to access the delivery management server 100 from the recipient terminal 300, the Web browser 360 and the delivery management client program 362 are the same as the sender terminal 200. The authentication device driver 364 is a program for operating the authentication device.

  As shown in FIG. 7, the deliverer terminal 400 is a portable information processing device such as a tablet terminal, a notebook computer, a smartphone, or a dedicated handy terminal.

  In particular, it has a wireless I / F 406 and accesses the delivery management server 100 via the base station 70 as shown in FIG.

  Similarly to the recipient terminal 300, an authentication device 480 is connected via the serial I / F 414. The serial I / F 414 is a USB interface, for example. However, although the authentication device 480 connected to the delivery person terminal 400 can be used for registration, it is assumed that it is mainly used for authenticating the recipient. Further, in the deliverer terminal 400, a printer for issuing a receipt to the recipient of the delivery 10 is connected to the serial I / F 414.

  The input / output device may be a keyboard or a mouse, but in FIG. 7, a command or information is input from the touch panel 430.

As the auxiliary memory, it is desirable to use a semiconductor memory such as the flash memory 460 that is strong against impulses in consideration of always carrying it.
As a program stored in the auxiliary storage, a transport management client program 462 for a delivery person to execute a job is installed. Further, an authentication device driver 464 and a printer driver 466 for operating each device are installed.

As shown in FIG. 8, the authentication device 480 (also for 380) is a device for reading a finger vein pattern by applying light.
The authentication device 480 includes a light source unit 482, an imaging unit 484, an image capturing unit 486, and a serial I / F 488.

  The light source unit 482 is, for example, a part that issues an LED (Light Emitting Diode) as a light source. The imaging unit 484 is a part that images a target. Usually, a CCD (Charge Coupled Device) is used to convert light into an electrical signal. The image capturing unit 486 is a part that captures an image captured by the imaging unit 484. The serial I / F 488 is connected to a terminal through a serial I / F such as a USB interface, and exchanges data and commands.

  Next, the data structure of the delivery management system according to the first embodiment will be described with reference to FIGS. FIG. 9 is a diagram showing sender registration data. FIG. 10 is a diagram showing recipient registration data. FIG. 11 is a diagram showing a delivery transaction. FIG. 12 is a diagram showing authentication data.

  Among them, sender registration data, recipient registration data, and delivery transactions are data stored in the delivery management DB 180, and authentication data is data stored in the authentication information DB 590.

  The sender registration data 1000 is data for registering and identifying a sender in the delivery management system as shown in FIG. 9, and one record is created for one sender.

The sender registration ID 1010 is an identifier for uniquely identifying this data.
The name 1020 stores the name of the sender. The address 1030 stores the address of the sender. The contact telephone number 1040 stores the telephone number of the sender's contact information. The contact e-mail address 1050 stores the e-mail address of the sender's contact address.

  The delivery destination information 1060 is information relating to the recipient registered as the delivery destination by the sender. The delivery destination information 1060 includes items of a recipient name 1062, a recipient address 1064, and proxy acceptability 1066. A plurality of delivery destination information 1060 can be registered.

  The proxy receipt permission / inhibition 1066 is a flag indicating whether or not to accept a proxy when a proxy recipient is registered instead of the recipient. The proxy receipt is assumed to be a person who has some relationship with the recipient, such as a person in the recipient's family or a person in the same department of the company.

  The recipient registration data 2000 is data for registering and identifying a recipient in the delivery management system as shown in FIG. 10, and one record is created for each recipient.

  The recipient registration ID 2010 is an identifier for uniquely identifying this data. The name 2020 stores the name of the recipient. The address 2030 stores the address of the recipient. The contact telephone number 2040 stores the telephone number of the recipient's contact. The contact email address 2050 stores the email address of the recipient contact.

  The agent ID stores an ID indicating a person who is permitted to receive a delivery to be sent to the recipient. When the proxy receipt permission 1066 of the item in the sender registration data 1000 is enabled and the agent ID is registered, the agent is authenticated and the result is that the agent is the agent himself / herself. Sometimes the delivery person operates to deliver the delivery to the agent.

  As already mentioned, the agent is assumed to be a person of the recipient's family or someone who has some relationship with the recipient, such as a person in the same department of the company. In addition, ranks may be assigned to deliverables and agents, and whether or not delivery items can be delivered is determined according to the ranks of the deliverables and agents.

  The delivery transaction 3000 is data for registering and identifying a delivery business (delivery item) in the delivery management system as shown in FIG. 11, and one record is stored for one delivery business. Made.

  The delivery transaction ID 3010 is an identifier for uniquely identifying this data. The inquiry number 3020 is a number used when the sender wants to refer to the status of the delivery item 10. The inquiry number 3020 may be the same as the delivery transaction ID 3010. The sender registration ID 3030 stores the sender registration ID of the person who shipped the delivery 10 related to this delivery service.

  The delivery destination information 3040 is information relating to the recipient designated as the delivery destination by the sender. The delivery destination information 3040 includes items such as a recipient name 3042, a recipient address 3044, and proxy acceptability 3046. A plurality of delivery destination information 3040 can be registered.

  In the desired delivery date and time 3050, the date and time that the sender wants the recipient to receive by this date and time is designated. The reception date 3060 stores the date on which the delivery work for the delivery item 10 is received. The package item name 3070 stores the item name representing the contents of the delivery item. For example, books, electronic devices, furniture, tableware, foods, and the like. The size / weight 3080 stores the size and weight of the delivery item 10. The size is normally designated as the total outer dimensions (total dimensions of length, width, and height) at the time of packing.

  The package handling type 3090 is a column for storing items that require special attention when the delivery company provides a special service or for this package. For example, information such as a service for transporting foods that need to be frozen and stored in a truck with a freezer, and information such as “Caution on the self”.

  The responsible delivery person ID 3100 is an ID for uniquely identifying the delivery person, and stores the ID of the delivery person in charge of this delivery fish absence. Although not shown, the delivery management DB 180 also stores a table for storing information on deliverers. The fee 3110 stores a fee as a consideration for delivery to be received from the sender at the time of advance payment and from the recipient at the time of payment.

  The advance payment / cash on delivery 3120 stores a flag indicating whether the advance payment, that is, the sender pays the fee, or the payment, that is, whether the recipient pays the fee. The cash on delivery transaction 3130 stores a flag indicating whether or not it is a cash on delivery transaction. Cash-on-delivery transaction means that the delivery item 10 is delivered for commercial purposes, the sender is the person who sells the item, and the recipient is the person who purchases the item. This is a form of delivery service in which the recipient receives the goods.

  The cash-on-delivery transaction fee / fee 3140 stores a charge for the product and a fee taken as an addition when the transaction is a cash-on-delivery transaction. The delivery status 3150 is an item for storing information indicating the current status of the delivery item 10. This is updated from time to time from each terminal provided by the delivery company and from the delivery terminal owned by the delivery person. For example, “shipping reception”, “XX branch reception”, “from XX branch to YY branch delivery”, “delivery completed”, etc. Is stored.

  The authentication data 4000 is data as shown in FIG. 12, and stores the registered recipient registration ID 4010 and the person's biometric authentication data 4020. In the present embodiment, three types of finger vein patterns, finger vein pattern 1, finger vein pattern 2, and finger vein pattern 3 are digitized and stored.

At the time of registration, the recipient registration ID and the biometric authentication data are sent from the delivery management server 100 to the authentication server 500 and registered in the authentication information DB 590.
Further, when the recipient is authenticated, the biometric authentication data of the authenticated person is sent from the delivery management server 100 to the authentication server 500, and the corresponding recipient registration ID is picked up from the authentication information DB 590.

  Next, the delivery process of the delivery management system and the state of delivery will be described with reference to FIGS. FIG. 13 is a sequence diagram showing a process when the shipper ships a delivery item. 14A and 14B are sequence diagrams showing processing when the recipient registers biometric information and later receives a delivery. FIG. 15 is a diagram illustrating a state when authentication is performed by the delivery terminal. FIG. 16 is a diagram illustrating an example of a receipt.

First, the processing when the sender ships the delivery will be described with reference to FIG.
First, in order to use the delivery management system, the sender sends the sender information as its own information to the delivery management server 100 (A100), and the delivery management server 100 registers it in the delivery management DB 180 (SQ100). ). This is done when the sender starts up the Web browser 260 from the sender terminal 200 and accesses the website of the delivery management system or executes the dedicated delivery management client program 262.

  Next, the sender places a delivery order from the sender terminal 200 (A102). The delivery management server 100 registers the delivery information related to the delivery order item in the delivery management DB 180 (SQ102). Then, for example, the inquiry number of the sender is notified by e-mail (A104). The inquiry number may be displayed on a screen output by the delivery management system website or the delivery management client program 262. The sender terminal 200 may be at the sender's home or company, or may be installed at the delivery base 810 by the delivery company.

  Then, the delivery person goes to the place of the sender and collects the delivery article 10 or accepts the delivery article 10 at the delivery base 810. The delivery status is sent to the delivery management server 100 from each terminal or delivery person terminal installed at each delivery base or collection center of the delivery company to the delivery management server 100 (A106) and updated (SQ104).

  The sender can make an inquiry with an inquiry number at an arbitrary time (A110).

  When receiving the inquiry by the inquiry number, the delivery management server 100 searches for the relevant case (SQ106) and notifies the sender terminal 200 of the delivery status. The delivery status is displayed on a screen output by the delivery management system website or the delivery management client program 262. In addition, the e-mail of the sender may be notified.

Next, the processing when the recipient receives the delivered goods will be described with reference to FIGS. 14A and 14B.
First, the recipient reads the authentication device 480 connected to the recipient terminal 300, sends the recipient information including the biometric information as its own information to the delivery management server 100 (A200), and the delivery management server 200. Registers it in the delivery management DB 180 (SQ120). This is done by the recipient starting up the Web browser 360 from the recipient terminal 300 and accessing the Web site of the delivery management system or executing the dedicated delivery management client program 362. The biometric authentication information is sent to the authentication server 500 (A202) and registered in the authentication information DB 590 (SQ500).

  Next, the delivery person goes to the recipient 10 with the delivery 10 and asks the recipient for authentication. When the recipient agrees to the offer, the finger is put into the authentication device 480 and the finger vein pattern is read (A204). The read biometric authentication information is sent from the delivery person terminal 400 to the delivery management server 100 and the authentication server 500 (A206, A208).

  The authentication server 500 matches the biometric authentication information sent to the biometric authentication information in the delivery information DB 590 to make an authentication determination (SQ502), and sends the result to the delivery person terminal via the delivery management server 100. Transmit (A210, A212).

  The delivery person looks at the authentication result displayed on the delivery terminal 400 (SQ400), determines whether or not the subject who has performed the authentication test is a genuine recipient, and determines whether or not to deliver the delivery item 10. to decide. The situation at this time is shown in FIG.

  When the delivery person makes a delivery report from the delivery terminal 400 (A214), the delivery management server 100 instructs the delivery terminal 200 to issue the recipient (A216), and the delivery terminal 400 is connected to the connected printer. To 490, the receipt 30 as shown in FIG. 16 is printed (SQ402). Finally, the recipient receives the receipt 30 (A218), and the delivery management server 100 sends a delivery completion notification to the sender terminal (A220).

  In this embodiment, after authenticating the person by biometric authentication called finger vein authentication, the delivery person delivers the delivery, so that an accident of delivering the delivery to the wrong person can be prevented. Safety can be increased.

In addition, since the receipt is issued after biometric authentication, the data issued by the recipient and the issued fact remain as evidence on the system. Will also be easier.
In the present embodiment, a method using finger vein authentication as biometric authentication has been described. However, other biometric authentication, for example, authentication means such as fingerprint, iris, and face authentication may be used.

[Embodiment 2]
Hereinafter, the second embodiment will be described with reference to FIGS. 17 and 18.
In the first embodiment, the delivery destination information 1060 of the sender registration data includes items of a recipient name 1062, a recipient address 1064, and proxy acceptability 1066. In the second embodiment, the sender registration data and the item of the delivery destination information of the delivery transaction are changed. The system configuration of other delivery management systems and the general configuration of the software may be the same.

  FIG. 17 is a diagram showing sender registration data according to the second embodiment. FIG. 18 is a diagram showing a delivery transaction according to the second embodiment.

As shown in FIG. 17, the delivery destination information 1080 of the sender registration data 1000a of the present embodiment is a recipient registration ID 1082 and proxy acceptability 1084.
That is, as compared with the first embodiment, the recipient name 1062 and the recipient address 1064 are changed to the recipient registration ID 1082.

  Further, the delivery destination information 3200 of the delivery transaction 3000a is a recipient registration ID 3202 and proxy acceptability 3204 as shown in FIG. Therefore, it is necessary for the sender to register as sender registration data in advance by receiving a notification of the receiver registration ID from the receiver.

  If the delivery management server 100 has the recipient registration ID 1082, the name and address can be known from the recipient registration and can be displayed on the delivery terminal 400, so there is no inconvenience in system operation.

  At the time of authentication, the authentication server 500 determines whether or not the authenticated data of the subject exists in the authentication DB, picks up the recipient registration ID shown in FIG. 12, and sends it to the delivery management server 100. The delivery management server determines that the recipient is a genuine recipient when it matches the recipient registration ID 3202 of the delivery transaction 3000a.

A feature of this embodiment is that the recipient of the delivery can receive the delivery without disclosing privacy information such as name and address to the sender. For example, when making a transaction on an auction site where the other party's personal information is not well understood on the network, it is possible to make the delivery possible by notifying the other party only of the recipient registration ID as their own information. Risk can be prevented so that privacy must be disclosed to strangers. At this time, if it is used together with the cash on delivery service provided by the delivery company, it is possible to prevent a fraudulent act in which goods are not sent even though the price has been paid.
The auctioneer can also leave the delivery with peace of mind because the goods are delivered only to those who have been authenticated.

  In the first embodiment, the name and address of the recipient are held as the entry of the sender registration data and the recipient information of the delivery transaction. In this embodiment, the recipient registration ID is held. However, both may be mixed in one table.

[Embodiment 3]
Hereinafter, a third embodiment will be described with reference to FIG. FIG. 19 is a diagram showing a delivery label according to the third embodiment. The third embodiment relates to a delivery label to be attached to a delivery item on the premise of the delivery management system described in the first embodiment.

  Usually, a delivery label is affixed to the delivery 10, and the sender name, address, telephone number, recipient name, address, telephone number, and other information necessary for delivery are described on the delivery label. .

  As shown in FIG. 19, the delivery label 40 affixed to the delivery item 10 in this embodiment is a delivery ID (same as the delivery transaction ID shown in FIG. 11 of the first embodiment), product name, and handling. And so on.

  A delivery person inputs information by reading or inputting a delivery ID using a scanner (not shown) connected to the delivery terminal 400, and inquiring the delivery ID to the delivery management server 100, thereby providing information necessary for delivery. Can be displayed.

  Thereby, it is possible to prevent the personal information of the sender and the recipient from being exposed to an unspecified number of people at the distribution stage of the delivery.

  DESCRIPTION OF SYMBOLS 1 ... Delivery management system, 10 ... Delivery thing, 30 ... Receipt, 100 ... Delivery management server, 180 ... Delivery management DB, 200 ... Shipper terminal, 300 ... Recipient terminal, 380 ... Authentication apparatus, 400 ... Delivery person terminal 480: Authentication device, 500: Authentication server, 180: Authentication information DB, 800: Collection center, 810: Delivery base.

Claims (7)

A delivery management method of a delivery management system in which a deliverer delivers a delivery sent by a sender to a recipient,
The delivery management system includes:
A delivery management server that accesses, updates, and stores a database related to delivery management;
An authentication server that accesses and updates and stores the authentication information database and authenticates biometric authentication information;
A sender terminal for entering sender registration information including information on the availability of proxy receipt ;
A recipient terminal connected to the first authentication device for inputting recipient registration information including the recipient's biometric information and the recipient's information that can be received on behalf of the delivery;
A second authentication device is connected, and the delivery person carries a delivery terminal for delivery,
The delivery management server, the authentication server, the sender terminal, the recipient terminal, and the delivery terminal are connected by a network,
The sender terminal sends the input sender registration information to the delivery management server and registers it in the database of the delivery management server;
The recipient terminal transmits recipient registration information including the recipient's biometric information input from the first authentication device to the delivery management server and registers it in the database of the delivery management server and the authentication server. And steps to
When a person who receives as a proxy is registered as information indicating whether or not the proxy can be received, the delivery management server determines whether or not the delivery can be delivered according to the rank of the delivery and the person who can receive the proxy. Steps,
Authenticating the recipient by the second authentication device, the delivery terminal transmitting the input biometric authentication information to the authentication server, and the authentication server authenticating;
The delivery terminal displaying an authentication result of the authentication server;
A delivery management method comprising:   The delivery management method according to claim 1, wherein the delivery terminal prints a receipt of a delivery related to the delivery.   The recipient registration information is identified by a recipient registration ID that uniquely identifies each recipient, and the sender registration information includes the recipient registration ID with respect to recipient information. The delivery management method according to claim 1. The delivery management server stores a delivery transaction that occurs for each delivery in a delivery management database, and the delivery transaction has a delivery transaction ID that uniquely identifies each delivery transaction;
2. The delivery management method according to claim 1, wherein the delivery label attached to the delivery includes the delivery transaction ID and does not contain the sender registration information and the recipient registration information. .   The delivery management method according to claim 1, wherein the biometric authentication information is information on finger vein authentication, and the first authentication device and the second authentication device are devices that perform finger vein authentication. . A delivery management system in which a deliverer delivers a delivery sent by a sender to a recipient,
The delivery management system
A delivery management server that accesses, updates, and stores a database related to delivery management;
An authentication server that accesses and updates and stores the authentication information database and authenticates biometric authentication information;
A sender terminal for entering sender registration information including information on the availability of proxy receipt ;
A recipient terminal connected to the first authentication device for inputting recipient registration information including the recipient's biometric information and the recipient's information that can be received on behalf of the delivery;
A second authentication device is connected, and the delivery person carries a delivery terminal for delivery,
The delivery management server, the authentication server, the sender terminal, the recipient terminal, and the delivery terminal are connected by a network,
The sender terminal sends the input sender registration information to the delivery management server, registers it in the database of the delivery management server,
The recipient terminal transmits recipient registration information including the recipient's biometric information input from the first authentication device to the delivery management server and registers it in the database of the delivery management server and the authentication server. And
When a person who receives as a proxy is registered as information regarding whether or not the proxy can be received, the delivery management server determines whether or not the delivery can be delivered according to the rank of the delivery and the person who can receive the proxy. ,
The recipient is authenticated by the second authentication device, the delivery terminal transmits the input biometric authentication information to the authentication server, and the authentication server authenticates,
The delivery management system, wherein the delivery terminal displays an authentication result of the authentication server. The delivery management server stores a delivery transaction that occurs for each delivery in a delivery management database, and the delivery transaction has a delivery transaction ID that uniquely identifies each delivery transaction;
7. The delivery management system according to claim 6 , wherein the delivery label affixed to the delivery includes the delivery transaction ID and does not contain the sender registration information and the recipient registration information. .

Images