JP2019197272A - Recipient confirmation system and recipient confirmation method - Google Patents

Abstract

To provide a recipient confirmation system and a recipient confirmation method to confirm a recipient himself/herself by recipient confirmation information specified by an orderer when an ordered article is delivered from a consignor to the recipient.SOLUTION: A recipient confirmation system 50 includes a recipient confirmation server 60, a collation DB 64 connected to the recipient confirmation server 60, an authentication server 70, an authentication DB 74 connected to the authentication server 70, a token DB 75 and a management terminal 80 on the main body side, and includes a smart phone 91 of a collection/delivery person 90 on the terminal side.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a recipient confirmation system and a recipient confirmation method for confirming identity of a recipient by recipient confirmation information designated by the orderer when delivering an ordered item from a shipper to the recipient.

  Traditionally, delivery service providers receive invoices and packages from the shipper, bring them to the collection center, sort them, and then deliver the packages to the recipient's address on the request slip. In addition, receipt is confirmed by having the recipient stamp or sign.

  In recent years, with the enforcement of the Act on Prevention of Transfer of Criminal Proceeds, it has become important to verify the recipient based on the identification details (name, residence, date of birth, etc.) described in the official certificate. There is a growing need for recipient confirmation in the delivery of parcels such as mail-order items.

  Therefore, when delivering the package to the recipient's address, the collection / reader reads the two-dimensional code that encrypts the recipient confirmation information printed on the package invoice on the terminal and matches it with the information on the presented document. A service for confirming the recipient by confirming whether or not the recipient is confirmed has been developed (see, for example, Patent Document 1 and Patent Document 2).

  Also, when delivering a package to the address of the recipient, the recipient confirmation information entered in the document presented by the recipient is input from the collector's terminal and sent to the center to confirm the recipient. A system has also been developed (see, for example, Patent Document 3).

Japanese Patent No. 4204762 Japanese Patent No. 5203766 JP 2004-157583 A

  Recipient verification information, such as identity-specific items on the official certificate for recipient verification, must be strictly managed as personal information and stored in a location that can be easily accessed from the outside via a communication network. I can't do it.

  On the other hand, when delivering the package, the collector / deliverer needs to check the recipient confirmation information and the confirmation data presented by the recipient at some place of delivery in order to confirm the recipient.

  As in Patent Document 1 and Patent Document 2, a method is simple in which the recipient confirmation information is printed as an encrypted two-dimensional code on a package invoice and the information is acquired by the collection / reader using a terminal at the delivery location. It is.

  However, even if it is encrypted, the fact that the recipient confirmation information is printed together with the address and name of the recipient on the invoice has a high risk of being misused considering the case where the invoice itself is not properly discarded.

  Also, as in Patent Document 3, the recipient confirmation information is stored in the center, the collection / delivery person photographs the official certificate at the terminal at the delivery location, and the image is sent to the center for collation. It is good that the person confirmation information is not sent outside the center, but creating and sending an image that shows the recipient confirmation information such as address, name, and date of birth reduces security. .

  Furthermore, it is a resisting means for the recipient to take his / her own public certificate, and the means to input the address, name, date of birth, etc. one by one from the terminal without keying is not available. Not convenient.

  Also, since the collection / delivery uses dedicated terminals for collection / delivery, as the number of delivery / delivery increases, more dedicated terminals are required as the number of collection / delivery increases. It will be a burden for me.

  The present invention has been made in view of the above problems, and stores only data necessary for recipient confirmation on the system body side accessed from the outside, uses a smartphone as a terminal for communication with the system body side, and receives the recipient. It is an object of the present invention to provide a recipient confirmation system for confirming a recipient by inputting confirmation data such as a password and date of birth to be confirmed from a smartphone and transmitting the confirmation data to a system main body.

In order to achieve the above-mentioned object, the consignment data including the recipient name, recipient address, confirmation document type, recipient confirmation information and invoice number from the shipper, the recipient name, the recipient address, and the invoice number A recipient verification system connected to a delivery service provider's consignment management system that is requested to deliver an order that requires recipient verification, along with an invoice printed with
A collation data management unit connected to the trust management system and the collation DB;
A recipient confirmation server including the collation DB and a recipient confirmation information collation unit connected to the collation data management unit;
A collation unit;
A communication control unit connected to the Internet;
An ID management unit connected to the communication control unit and the authentication DB;
An authentication server connected to the recipient confirmation server including the communication control unit, the ID management unit, and a token management unit connected to a token DB;
Connected to the authentication server via the Internet, and includes a smart phone of a collector who has a temporary storage memory, a barcode reader, and a camera;
The collation data management unit
Of the trust data, the invoice number received from the trust management system, the confirmation document type, and collation data including the recipient confirmation information are stored in the collation DB,
Sending verification result information including the verification result received from the recipient confirmation information verification unit to the trust management system;
The collation unit
Search the matching DB with the invoice number included in the inquiry information received from the token management unit, and send the stored confirmation document type to the token management unit,
The recipient confirmation information verification unit
Recipient confirmation data received from the token manager is collated with the recipient confirmation information stored in the collation DB, and a collation result and collation completion date / time are transmitted to the token manager and the collation data manager.
The communication control unit
Control data communication via the Internet between the ID management unit and the token management unit and the smartphone,
The ID management unit
After verifying login information including the user ID and password received from the smartphone with the authentication DB, request a token generation to the token management unit,
The token management unit
In response to the token generation request, an access token and a refresh token are generated and transmitted to the smartphone, and stored in the token DB as token information together with the user ID and generation time,
Search and authenticate the token DB with the access token received with the command from the smartphone,
Deliver the received command to the collation unit or the recipient confirmation information collation unit, send the returned confirmation document type or the collation result and the collation completion date and time to the smartphone,
The smartphone
Transmitting the login information to the authentication server, storing the returned access token and the refresh token in the temporary storage memory;
The barcode of the invoice number printed on the invoice is photographed by the camera and read by the barcode reader, and transmitted to the authentication server together with the access token as the inquiry information,
The recipient confirmation data input on the input screen displayed according to the type of the confirmation document to be returned is transmitted to the authentication server together with the access token, and the verification result returned is displayed on the screen and the receipt The gist is to confirm the person.

  In addition, the gist of the present invention is that the smartphone further has a short-range wireless communication function, is connected to a portable printer by short-range wireless communication, and prints a delivery completion letter including the verification result.

In the present invention, the verification data includes address position information obtained by converting the recipient address into (latitude, longitude) data by the trust management system,
The smartphone further includes a delivery place GPS data acquired by a GPS receiving function included in the inquiry information, and transmits the data to the authentication server together with the access token.
The GPS data collation unit determines whether the unloading location GPS data received from the token management unit is within an allowable range from the address location information stored in the verification DB. Storing the unloading location GPS data in the verification DB;
The collation data management unit
The gist is to include the delivery place GPS data stored in the verification DB in the verification result information and transmit it to the consignment management system.

Further, according to the present invention, the authentication server further includes a management terminal connected to the token management unit,
The token management unit
If the time limit monitoring timer that starts when the refresh token is generated times out, the user ID and the occurrence time are notified to the management terminal as an occurrence of an abnormality,
When the user ID and status data are input from the management terminal, the corresponding token information is deleted from the token DB,
Sending the user ID and the situation data to the ID management unit;
The ID management unit
The gist is to set the status data and the invalid flag in the authentication DB corresponding to the received user ID.

In addition, the consignment data including the recipient name, recipient address, confirmation document type, recipient confirmation information and invoice number, and the recipient name, recipient address, and invoice number barcode are printed from the shipper. Recipient Confirmation Method in Recipient Confirmation System Including Reconciliation DB, Authentication DB, and Token DB Connected to Delivery Service Contractor's Contract Management System Requested to Deliver Ordered Items that require Recipient Confirmation Because
Among the entrusted data, the collation data including the invoice number, the confirmation document type, and the recipient confirmation information is stored in the collation DB,
After verifying login information including the user ID and password received from the collector's smartphone via the Internet with the authentication DB, an access token and a refresh token are generated and transmitted to the smartphone, and the token information together with the user ID and generation time Is stored in the token DB as
From the smartphone, the barcode of the invoice number printed on the invoice is photographed by the camera and transmitted with the access token as read inquiry information by the barcode reader,
After searching and authenticating the token DB with the access token received from the smartphone, search the verification DB with the invoice number included in the inquiry information, and send the stored confirmation document type to the smartphone,
Recipient confirmation data entered on the input screen displayed according to the confirmation document type on the smartphone, transmitted together with the access token,
After searching and authenticating the token DB with the access token received from the smartphone, the recipient confirmation data is collated with the recipient confirmation information stored in the collation DB, and a collation result and a collation completion date and time are obtained. Send it to your smartphone,
The gist is to display the verification result on the screen on the smartphone and perform recipient confirmation.

In the present invention, the verification data includes address position information obtained by converting the recipient address into (latitude, longitude) data by the trust management system,
Including the unloading location GPS data acquired by the GPS reception function from the smartphone in the inquiry information, and sending it together with the access token,
Judging whether the unloading location GPS data received from the smartphone is within an allowable range from the address location information stored in the verification DB,
In addition, the gist is to check the place of delivery.

  As described above, according to the present invention, only the data necessary for recipient confirmation is stored on the main body side of the recipient confirmation system accessed from the outside, and the recipient confirmation system communicates with the main body side of the recipient confirmation system. Recipients set by the orderer by using a smartphone as a terminal, inputting confirmation data such as the password and date of birth to be verified against the recipient confirmation information from the smartphone, and sending it to the main body of the recipient confirmation system Recipient confirmation can be performed without external information seeing the confirmation information.

  In addition, the delivery destination GPS data acquired with the smartphone and the address information of the recipient address are compared on the main body side of the recipient confirmation system to confirm that the recipient confirmation was performed at the recipient address location. it can.

  In addition, since the delivery location GPS data is transmitted to and stored in the consignment management system, the delivery service provider can confirm the situation evidence in the case where a trouble occurs later.

It is a composition outline figure of an embodiment of the invention. It is a data block diagram of order DB of an order management server. It is a data block diagram of trust DB of a trust data server, and collation DB of a recipient confirmation server. It is a data block diagram of authentication DB and token DB of an authentication server. It is a sequence diagram of a consignment process from receiving an order from the orderer to receiving consignment of delivery from the shipper. FIG. 10 is a sequence diagram of a pre-delivery process before a collection / delivery person confirms a recipient. It is a sequence diagram (the 1) of the goods delivery process in which a collection / delivery person confirms a recipient. It is a sequence diagram (the 2) of the goods delivery process in which a collection / delivery person confirms a recipient. FIG. 10 is a sequence diagram when an access token expires. It is a sequence diagram in case a refresh token has expired. It is a flowchart figure of an order receipt management server. It is a flowchart figure of the trust data management part of a trust data server. It is a flowchart figure of the collation data management part of a recipient confirmation server. It is a flowchart figure of the GPS data collation part of a recipient confirmation server. It is a flowchart figure of the recipient confirmation information collation part of a recipient confirmation server. It is a flowchart figure of the ID management part of an authentication server. It is a flowchart figure of the token management part of an authentication server (the 1). It is a flowchart figure of the token management part of an authentication server (the 2). It is a flowchart figure of the token management part of an authentication server (the 3). It is a flowchart figure of the token management part and ID management part of the authentication server at the time of abnormality occurrence. It is a flowchart figure of the confirmation application of a collector's smart phone (the 1). It is a flowchart figure of the confirmation application of a collector's smart phone (the 2). Screen display diagram of the collector's smartphone (part 1). Screen display diagram of the collector's smartphone (part 2).

  In the embodiment of the present invention, as shown in FIG. 1, a PC 11 of an orderer 10 connected via the Internet 100, an order management server 21 of a shipper 20 that requests delivery of an ordered item, and a delivery request. The delivery management company 30 of the delivery management company 40 and the recipient confirmation system 50 and the smart phone 91 of the collector 90 are configured.

  Here, in the recipient confirmation system 50 of the present invention, on the main body side, a recipient confirmation server 60, a verification DB 64 connected to the recipient confirmation server 60, an authentication server 70, and an authentication DB 74 connected to the authentication server 70. And the token DB 75 and the management terminal 80, and the smart phone 91 of the collector 90 is included on the terminal side.

  The function of each component shown in FIG. 1 will be described. In the following description, the database is abbreviated as DB.

  The order management server 21 of the shipper 20 assigns the order number and the invoice number to the order data d1 including the recipient confirmation information and saves it in the order DB 22, and then generates the consignment data d2 for the delivery request and prints it as the invoice 23. (S1) and transmit to the commission management system 40.

  Further, the order management server 21 of the shipper 20 stores the delivery result information d11 received from the trust management system 40 after delivery in the order DB 22.

  The commission management system 40 of the delivery service provider 30 includes a commission data server 41 and a commission DB 43.

  The entrusted data management unit 42 included in the entrusted data server 41 saves the received entrusted data d2 in the entrusted DB 43, generates the verification data d3 using only the data necessary for confirming the recipient, and receives the recipient confirmation system 50. It transmits to the person confirmation server 60.

  Further, the consignment data management unit 42 stores the collation result information d10 received from the recipient confirmation server 60 after delivery in the consignment DB 43, and transmits the delivery result information d11 included therein to the order management server 21.

  The recipient confirmation server 60 includes a collation data management unit 61, a GPS data collation unit 62, and a recipient confirmation information collation unit 63.

  The verification data management unit 61 stores the verification data d3 received from the commissioned data management unit 42 in the verification DB 64.

  Further, the collation data management unit 61 transmits collation result information d10 including the collation result set by the GPS data collation unit 62 and the recipient confirmation information collation unit 63 after delivery to the commissioned data management unit 42.

  The GPS data collation unit 62 determines whether the delivery location GPS data received from the smartphone 91 of the collector / deliverer 90 is within a range allowed from the address position information of the collation data d3 stored in the collation DB 64. In this case, the delivery place GPS data is stored in the verification DB 64, and the confirmation document type included in the verification data d3 is transmitted.

  The recipient confirmation information collating unit 63 collates whether the recipient confirmation data received from the smart phone 91 of the collector / deliverer 90 matches the recipient confirmation information in the collation data d3 stored in the collation DB 64, and collation is completed with the collation result. The date and time is transmitted to the token management unit and the verification data management unit.

  The authentication server 70 includes an ID management unit 72 connected to the authentication DB 74, a token management unit 73 connected to the token DB 75, and a communication control unit 71 connected to the ID management unit 72 and the token management unit 73.

  The communication control unit 71 controls data communication via the Internet 100 between the connected ID management unit 72 and token management unit 73 and the smartphone 91 of the collector 90.

  The ID management unit 72 receives the user ID and password as login information d4 from the smartphone 91 of the collector 90, and collates with the data set in the authentication DB 74. If the authentication is successful, the ID management unit 72 stores the token information in the token management unit 73. Request generation.

  In response to the token generation request, the token management unit 73 generates an access token and a refresh token, transmits them to the smart phone 91 of the collector 90, and stores them in the token DB 75 together with the user ID and generation time.

  Further, the token management unit 73 searches the token DB 75 with the access token transmitted from the smartphone 91 of the collector 90, and authenticates whether it is valid.

  Further, the token management unit 73 activates a refresh token expiration monitoring timer, and when a timeout occurs, the token management unit 73 notifies the connected management terminal 80 of the occurrence of an abnormality together with the user ID and the occurrence time.

  A confirmation application 91a is mounted on the smartphone 91 of the collector 90, and includes a barcode reader, a camera, a GPS reception function, and a short-range wireless communication function, which are not shown.

  Hereinafter, the description will be made simply as the smartphone 91 including the confirmation application 91a.

  When the smartphone 91 transmits the input user ID and password as login information d4 to the authentication server 70, stores the returned token d5 including the access token and the refresh token in the temporary storage memory 91b, and transmits the data. Always send with an access token.

  The smartphone 91 reads the barcode of the invoice number printed on the invoice 23 to be delivered (s2) with a barcode reader, and simultaneously acquires GPS information of the current location by the GPS reception function, and delivers the invoice number and the acquired GPS information. Inquiry information d6 as local GPS data is transmitted to the authentication server 70.

  The smartphone 91 displays an input screen corresponding to the confirmation document type d7 to be returned, and when the recipient confirmation data d8 is input, transmits it to the authentication server 70.

  The smartphone 91 displays the returned collation result d9 on the screen, connects to a portable printer (not shown) by short-range wireless communication, and prints it as a delivery completion letter.

(Data structure)
Next, the data structure of each information used in the recipient confirmation system 50 of the present invention will be described. However, not only the data elements shown below but also other data elements can be added and configured. Included in the technical scope.

  As shown in FIG. 2, in the order DB 22 managed by the order management server 21, the order item information, orderer name, orderer address, and recipient name as order data d1 input and transmitted by the orderer 10 are transmitted. , Recipient address, confirmation document type, recipient confirmation information, order number and invoice number assigned by the order management server 21 are stored.

  Here, the confirmation document type is information that uses a password as information for confirming the recipient or specifies which public certificate in the case of a public certificate such as a driver's license.

  Recipient confirmation information is data that can specify an individual such as a password when a password is specified by the type of confirmation document, and a date of birth written on the public certificate when another public certificate is specified.

  The order DB 22 also stores a delivery result (OK / NG) and delivery completion date and time as delivery result information d11 transmitted from the trust management system 40 of the delivery service provider 30.

  As shown in FIG. 2, the order management server 21 selects a recipient name, recipient address, confirmation document type, recipient confirmation information, and invoice number from the data in the order DB 22 as the consignment data d2.

  Further, as shown in FIG. 2, the order management server 21 prints the invoice number of the consignment data d2, the bar code obtained by converting it into a bar code, the recipient address and the name of the recipient on the invoice 23. In addition, the shipper address and shipper name, or the orderer address and orderer name, or both are printed.

  As shown in FIG. 3 (a), the consignment DB 43 managed by the consignment data server 41 of the consignment management system 40 stores the recipient name, recipient address, and confirmation sent as the consignment data d2 from the order management server 21. Document type, recipient confirmation information and invoice number are stored.

  In addition, in the consignment DB 43, the delivery result (OK / NG), the delivery completion date and time, and the delivery place GPS data are also stored as the matching result information d10 transmitted from the matching data management unit 61 of the recipient confirmation server 60. .

  As shown in FIG. 3B, the collation DB 64 of the recipient confirmation server 60 includes invoice number, confirmation document type, recipient confirmation information, and consignment data as collation data d3 transmitted from the consignment data server 41. The server 41 stores address position information obtained by converting the recipient address into (latitude, longitude) data.

  The collation DB 64 also stores the delivery location GPS data received from the smartphone 91 of the collector 90 by the GPS data collation unit 62 of the recipient confirmation server 60.

  As shown in FIG. 4A, the user ID and password of the collector / deliverer 90 are set in the authentication DB 74 of the authentication server 70.

  The authentication DB 74 can also set a user ID valid / invalid flag and invalid status information because an abnormal situation has occurred, such as the smartphone 91 of the collector 90 being lost.

  As shown in FIG. 4B, in the token DB 75 of the authentication server 70, the user ID of the collector / delivery person 90, an access token and a refresh token that are generated when the collector / distributor 90 logs in, and the generation time are token information. Stored as t1.

(Sequence in the embodiment)
Each data and operation will be described according to the sequence diagrams of FIGS. 5 to 8 with reference to the configuration diagram of FIG.

  Each data in the sequence diagram describes only main information elements, and the specific data configuration is as described in the data configuration item.

<Contract process>
FIG. 5 is a sequence diagram of a consignment process until the delivery service provider 30 receives a consignment for delivery from the shipper 20 who has received an order from the orderer 10.

  First, the orderer 10 inputs the order data d1 from the PC 11 (p1), and the order management server 21 of the shipper 20 receives the order data d1 (p2).

  The order management server 21 stores the received order data d1 in the order DB 22 (p3) and receives it (p2).

  The order management server 21 assigns an order number and an invoice number to the order data d1 and stores them in the order DB 22 (p3), and creates consignment data d2 for a delivery request (p4).

  The invoice number, the bar code converted into a bar code, the address of the recipient, and the name of the recipient are printed on the invoice 23 from the created acceptance data d2 (p5), and are sent to the commission data server 41 of the commission management system 40. The commission data d2 is transmitted (p6).

  The entrusted data management unit 42 of the entrusted data server 41 stores the received entrusted data d2 in the entrusted DB 43 (p7).

  Further, the consignment data management unit 42 converts the recipient address of the consignment data d2 into address position information of (latitude, longitude) (p8), and combines it with the invoice number, confirmation document type, and recipient confirmation information of the consignment data d2. The collation data d3 is created (p9).

  The entrusted data management unit 42 transmits the created verification data d3 to the verification data management unit 61 of the recipient confirmation server 60 of the recipient confirmation system 50 (p10).

  The verification data management unit 61 stores the received verification data d3 in the verification DB 64 (p11).

  Up to this point, the collation data d3 has been input from the outside to the recipient confirmation system 50 of the present invention as information necessary to confirm the recipient.

<Order delivery process>
FIG. 6 shows that the collection / delivery person 90 starts the confirmation application 91a of the portable smartphone 91 in order to confirm the recipient before delivering the ordered item to the recipient (10: illustrated as the same person as the orderer 10). It is a sequence diagram of an order goods delivery preparation process to be.

  First, the collector / delivery person 90 starts by touching the icon of the confirmation application 91a on the screen of the smartphone 91 (p12).

  The collector 90 inputs the user ID and password to the user ID and password input fields displayed on the screen of the smartphone 91 by an input means such as a keyboard displayed on the screen, and receives the recipient via the Internet 100. The login information d4 is transmitted to the authentication server 70 of the confirmation system 50 (p13).

  The communication control unit 71 of the authentication server 70 of the recipient confirmation system 50 is a means for controlling data communication with the smart phone 91 of the collector 90, and passes the received login information d4 to the ID management unit 72 of the authentication server 70.

  The ID management unit 72 performs authentication by comparing the received login information d4 with the user ID and password of the connected authentication DB 74 (p14).

  When the authentication is successful, the ID management unit 72 activates the token management unit 73, the token management unit 73 generates an access token and a refresh token (p15), and is connected as token information t1 together with the user ID and generation time. Save in the DB 75 (p16).

  The token management unit 73 transmits the token d5 (access token and refresh token) to the smart phone 91 of the collector 90 via the communication control unit 71 (p17).

  The smart phone 91 of the collector 90 sets the received token d5 (access token and refresh token) temporarily in the smart phone 91 (p18), and transmits the data after adding the access token at the time of subsequent data transmission.

  The token management unit 73 activates a refresh token expiration monitoring timer (p19), so that when the refresh token expires, the smartphone 91 of the collector 90 can be notified as an abnormal state that has not been used for a long time. Yes.

<Order delivery process>
FIGS. 7 and 8 are sequence diagrams of the order delivery process for confirming the recipient when the collector / deliverer 90 delivers the order together with the invoice 23 to the recipient (10) (s2).

  The smartphone 91 of the collector 90 reads the barcode of the invoice number printed on the invoice 23 with a barcode reader (p20), and simultaneously acquires the GPS information of the current location as the unloading location GPS data by the GPS reception function of the smartphone 91. (P21).

  The read invoice number and the acquired delivery place GPS data are transmitted as inquiry information d6 together with the access token, and a confirmation document type inquiry is made to the authentication server 70 (p22).

  The token management unit 73 of the authentication server 70 authenticates the access token transmitted together with the inquiry information d6 with the access token stored in the token DB 75 (p23).

  After the authentication, the token management unit 73 passes the invoice number and the delivery place GPS data to the GPS data matching unit 62 of the recipient confirmation server 60, and makes a confirmation document type request (p24).

  The GPS data collation unit 62 of the recipient confirmation server 60 searches the collation DB 64 with the invoice number (p25), and collates the address location information of the read collation data d3 with the received delivery location GPS data (p26).

  The GPS data collating unit 62 performs collation by determining whether or not the delivery place GPS data is within a predetermined range from the value of (latitude, longitude) of the address position information.

  At this time, the GPS data collation unit 62 stores the collated delivery place GPS data in the collation DB 64.

  After collation, the confirmation document type included in the read collation data d3 is returned to the token management unit 73 of the authentication server 70, and the token management unit 73 sends the confirmation document type to the smartphone 91 of the collector 90 via the communication control unit 71. Is transferred (p27).

  The smartphone 91 of the collector 90 displays an input screen corresponding to the received confirmation document type (p28), and the confirmation data described in the designated document is input by the collector 90 or the recipient (10). (P29).

  The smartphone 91 of the collector 90 transmits the input confirmation data and invoice number as recipient confirmation data d8 to the authentication server 70 token management unit 73 together with the access token (p30).

  The token management unit 73 of the authentication server 70 authenticates the access token transmitted together with the recipient confirmation data d8 with the access token stored in the token DB 75 (p31).

  After the authentication, the token management unit 73 passes the recipient confirmation data d8 including the invoice number and the confirmation data to the recipient confirmation information collating unit 63 of the recipient confirmation server 60, and makes a confirmation data collation request (p32).

  The recipient confirmation information matching unit 63 of the recipient confirmation server 60 searches the matching DB 64 with the invoice number (p33) and collates the recipient confirmation information of the read matching data d3 with the received confirmation data (p34).

  When the collation is completed, the recipient confirmation information collation unit 63 returns the collation result d9 to the token management unit 73 of the authentication server 70, and the token management unit 73 notifies the smartphone 91 of the collector / delivery person 90 via the communication control unit 71. The verification result d9 is transferred (p35).

  The recipient confirmation information matching unit 63 also passes the matching result d9 to the matching data management unit 61. The matching data management unit 61 sends the invoice number, delivery result (OK), delivery completion date and time, and delivery location. The GPS data is transmitted as the collation result information d10 to the commissioned data management unit 42 of the commissioned data server 41 (p36).

  The collation data management unit 61 finally deletes the collation data d3 and the delivery place GPS data from the collation DB 64 (p37).

  On the other hand, the smartphone 91 of the collector / deliverer 90 displays a screen of the received verification result d9 (p38). If the verification is successful, the collector / deliverer 90 delivers the ordered item to the recipient (10) (s3). .

  In addition, the smartphone 91 is connected to the portable printer by short-range wireless communication, and prints the collation result d9 as a delivery completion letter together with an invoice number, delivery completion date and time, a collection / delivery name, and the like (p39).

  Further, the consignment data management unit 42 of the consignment data server 41 saves the received collation result information d10 in the consignment DB 43 (p40), the invoice number, the delivery result (OK), and the delivery completion date / time in the collation result information d10. To the order receiving management server 21 as delivery result information d11 (p41).

  The order management server 21 stores the received delivery result information d11 in the order DB 22 (42).

  The above is the sequence when the recipient confirmation is normally performed.

<When access token has expired>
Next, as shown in FIG. 9, a sequence when the access token expires in the middle will be described.

  When the invoice number and the delivery location GPS data are transmitted as inquiry information d6 from the smart phone 91 of the collector 90 together with the access token, and the confirmation document type inquiry is made to the authentication server 70 (p22), the access token Let's take as an example the case where

  The token management unit 73 of the authentication server 70 authenticates the access token transmitted together with the inquiry information d6 with the access token stored in the token DB 75 (p23).

  Here, when the token management unit 73 determines that the valid time of the predetermined access token has passed from the token generation time and the access token used is invalid, Request transmission of the refresh token (p50).

  The smartphone 91 of the collector 90 transmits the refresh token to the token management unit 73 of the authentication server 70 (p51).

  The token management unit 73 authenticates the transmitted refresh token with the refresh token stored in the token DB 75 (p52).

  Here, when the authentication of the refresh token is NG, the collector / delivery person 90 performs re-login.

  When the refresh token is authenticated, the token management unit 73 newly regenerates an access token (p53), updates the token DB 75 with the newly generated access token, and rewrites the generation time to a new time (p54). ).

  The token management unit 73 transmits the newly generated access token to the smartphone 91 of the collector 90 (p55).

  The smart phone 91 of the collector 90 sets the received new access token in the temporary storage memory, and thereafter uses the new access token (p56).

  Here, the smartphone 91 of the collector 90 again transmits the invoice number and the delivery place GPS data as inquiry information d6 together with a new access token, and makes an inquiry to the authentication server 70 about the confirmation document type (p57). ).

  In this way, even if the access token expires, if the refresh token is valid, the access token is automatically updated, and the collector 90 can continue the work without logging in again.

<When the refresh token has expired>
Next, as shown in FIG. 10, a sequence when the refresh token expiration monitoring timer times out and the refresh token expires will be described.

  In the token management unit 73 of the authentication server 70, the refresh token expiration monitoring timer times out (p60).

  The token management unit 73 notifies the management terminal 80 that an abnormality has occurred along with the abnormality notification data t2 including the user ID and the occurrence time (p61).

  The management terminal 80 that has received the abnormality notification data t2 displays a message on the screen, and the administrator identifies the collector 90 from the user ID and checks the situation (s4).

  The management terminal 80 transmits status information t3 including the user ID input by the administrator and status data such as loss to the token management unit 73 of the authentication server 70 (p62).

  When receiving the status information t3, the token management unit 73 searches the token DB 75 with the received user ID, deletes the corresponding token information, and passes the status information t3 to the ID management unit 72.

  The ID management unit 72 searches the authentication DB 74 with the user ID of the status information t3, sets status data in the corresponding user ID information, sets an invalid flag, and sets the user ID stop (63).

  This is effective in stopping access by another person using the smartphone 91 when the collector / distributor 90 loses the smartphone 91.

(Processing flow of each server)
(Order Management Server 21)
Details of processing of the order management server 21 of the shipper 20 will be described with reference to FIGS. 11 and 2.

  The order management server 21 receives the order data d1 from the PC 11 of the orderer 10 via the Internet 100 (S10).

  The order management server 21 assigns an order number and stores the received order data d1 in the order DB 22 (S11).

  Next, the order management server 21 assigns an invoice number to the order data d1 and saves it in the order DB 22 in order to request delivery to the delivery service provider 30, and receives the recipient name, recipient address, confirmation document type, and receipt. The contract data d2 including the person confirmation information and the invoice number is created (S12).

  The order management server 21 converts the invoice number of the consignment data d2 into a bar code, and, as shown in FIG. 2, the invoice number, the bar code converted into the bar code, the recipient address and the name of the recipient in the invoice 23. Printing is performed (S13).

  The order management server 21 transmits the created trust data d2 to the trust data server 41 of the trust management system 40 (S14).

  On the other hand, after the delivery is completed, the order management server 21 receives the delivery result information d11 from the consignment data server 41 (S20).

  The order management server 21 searches the order DB 22 with the invoice number included in the received delivery result information d11 and stores it in the order DB 22 so as to add the delivery result information d11 to the corresponding order data d1 (S21).

(Consignment data server 41)
Details of the processing of the consignment data management unit 42 included in the consignment data server 41 of the consignment management system 40 of the delivery service company 30 will be described with reference to FIGS. 12 and 3.

  The consignment data management unit 42 receives the consignment data d2 transmitted from the order management server 21 of the shipper 20 (S30).

  The entrusted data management unit 42 stores the received entrusted data d2 in the entrusted DB 43 (S31).

  The entrusted data management unit 42 converts the recipient address in the stored entrusted data d2 into address position information of (latitude, longitude) (S32).

  The entrusted data management unit 42 creates collation data d3 including the converted address position information, the invoice number, the confirmation document type, and the recipient confirmation information (S33).

  The entrusted data management unit 42 transmits the created verification data d3 to the recipient confirmation server 60 of the recipient confirmation system 50 (S34).

  On the other hand, after the delivery is completed, the consignment data management unit 42 receives the verification result information d10 from the recipient confirmation server 60 (S40).

  The consignment data management unit 42 searches the consignment DB 43 with the invoice number included in the received collation result information d10, adds the collation result information d10 to the corresponding consignment data d2, and stores it in the consignment DB 43 (S41).

  The consignment data management unit 42 creates delivery result information d11 including the invoice number, the matching result, and the delivery completion date / time from the stored matching result information d10, and transmits it to the order management server 21 (S42).

(Recipient Confirmation Server 60)
With reference to FIGS. 13 and 3, the details of the processing of the verification data management unit 61 included in the recipient confirmation server 60 of the recipient confirmation system 50 of the delivery service company 30 will be described.

  The collation data management unit 61 receives the collation data d3 transmitted from the consignment data management unit 42 of the consignment data server 41 (S50).

  The verification data management unit 61 stores the received verification data d3 in the verification DB 64 (S51).

  On the other hand, after the delivery is completed, the verification data management unit 61 receives the verification result d9 from the recipient confirmation information matching unit 63 included in the same recipient confirmation server 60 (S60).

  The verification data management unit 61 uses the received verification result d9 as a delivery result, and sends the invoice number, delivery completion date and time, and delivery location GPS data as verification result information d10 to the consignment data management unit 42 of the consignment data server 41. (S61).

  The collation data management unit 61 finally deletes the collation data d3 and the delivery place GPS data from the collation DB 64 (S62).

  Details of the processing of the GPS data matching unit 62 included in the recipient confirmation server 60 of the recipient confirmation system 50 of the delivery service provider 30 will be described with reference to FIG.

  The GPS data matching unit 62 receives the confirmation document type request from the token management unit 73 included in the authentication server 70 of the recipient confirmation system 50 (S70).

  The GPS data matching unit 62 searches the matching DB 64 with the invoice number included in the confirmation document type request (S71).

  If there is no corresponding verification data d3 in the verification DB 64, the GPS data verification unit 62 transmits an error to the token management unit 73 and ends the process (S72).

  On the other hand, if the matching data d3 exists in the matching DB 64, the GPS data matching unit 62 uses the address location information in the matching data d3 and the received delivery location GPS data as the (latitude, longitude) of the location information. It is verified by determining whether or not the delivery place GPS data falls within a predetermined range from the value of (S73).

  If the delivery location GPS data is out of range, the GPS data collation unit 62 transmits an error to the token management unit 73 and ends the process (S74).

  On the other hand, when the delivery place GPS data is within the range, the GPS data collation unit 62 adds the delivery place GPS data to the corresponding collation data d3 in the collation DB 64 and stores it, and the confirmation document in the collation data d3. The type is returned to the token management unit 73 (S75).

  Details of the processing of the recipient confirmation information matching unit 63 included in the recipient confirmation server 60 of the recipient confirmation system 50 of the delivery service provider 30 will be described with reference to FIG.

  The recipient confirmation information matching unit 63 receives the confirmation data matching request from the token management unit 73 included in the authentication server 70 of the recipient confirmation system 50 (S80).

  The recipient confirmation information matching unit 63 searches the matching DB 64 with the invoice number included in the confirmation data matching request (S81).

  The recipient confirmation information collating unit 63 collates the recipient confirmation information in the collation data d3 with the confirmation data received from the token management unit 73 (S82).

  The recipient confirmation information verification unit 63 transmits the verification result (OK / NG) and the verification completion date and time to the token management unit 73 (S83).

  Further, the recipient confirmation information collation unit 63 transmits the collation result (OK / NG) and the collation completion date and time to the collation data management unit 61 (S84).

(Authentication server 70)
The authentication server 70 of the recipient confirmation system 50 of the delivery service provider 30 includes a communication control unit 71, an ID management unit 72, and a token management unit 73.

  The communication control unit 71 is a means for controlling data communication via the Internet 100 between the smart phone 91 of the collector 90 and the ID management unit 72 and the token management unit 73.

  Details of processing of the ID management unit 72 included in the authentication server 70 of the recipient confirmation system 50 of the delivery service provider 30 will be described with reference to FIGS. 16, 20, and 4.

  The ID management unit 72 receives the user ID and password transmitted as the login information d4 from the smartphone 91 of the collector 90 (S90).

  The ID management unit 72 searches the authentication DB 74 with the received user ID and acquires a registered password (S91).

  The ID management unit 72 performs authentication by collating the received password with the password acquired from the authentication DB 74 (S92).

  If the authentication is NG, the ID management unit 72 transmits an error to the smartphone 91 of the collector 90 (S93).

  On the other hand, if the authentication is OK, the ID management unit 72 passes the user ID to the token management unit 73 and requests token generation (S94).

  As shown in FIG. 20, when receiving a user ID stop request from the token management unit 73, the ID management unit 72 searches the authentication DB 74 with the received user ID, and uses the received status data as status information. The corresponding user ID is stored in the authentication DB 74 (S145).

  Further, the ID management unit 72 sets an invalid flag for the corresponding user ID in the authentication DB 74 (S146).

  Details of processing of the token management unit 73 included in the authentication server 70 of the recipient confirmation system 50 of the delivery service provider 30 will be described with reference to FIGS. 17 to 20 and FIG. 4.

  As shown in FIG. 17, the token management unit 73 receives a token generation request from the ID management unit 72 (S100).

  The token management unit 73 generates a new access token and a refresh token (S101).

  The token management unit 73 stores the generated access token and refresh token in the token DB 75 together with the user ID and generation time (S102).

  The token management unit 73 transmits the generated access token and refresh token to the smart phone 91 of the collector 90 (S103).

  The token management unit 73 starts a refresh token expiration monitoring timer (S104).

  Next, as illustrated in FIG. 18, the token management unit 73 receives an access token transmitted from the smartphone 91 of the collector 90 (S110).

  The token management unit 73 searches the token DB 75 with the received access token, determines whether it is currently within a predetermined effective period from the generation time, and authenticates it (S111).

  If the access token is valid and the authentication is successful, the token management unit 73 determines a command received from the smartphone 91 of the collector 90 (S112).

  If the received command is a confirmation document type inquiry, the token management unit 73 delivers the inquiry information d6 including the received invoice number and the delivery location GPS data to the GPS data matching unit 62, and sets the confirmation document type d7. A request is made (S113).

  Then, the token management unit 73 transmits the confirmation document type d7 returned from the GPS data matching unit 62 to the smartphone 91 of the collector 90 (S114).

  On the other hand, if the received command is confirmation data transmission, the token management unit 73 delivers the recipient confirmation data d8 consisting of the received invoice number and confirmation data to the recipient confirmation information collation unit 63, and sends a confirmation data collation request. It performs (S115).

  Then, the token management unit 73 transmits the verification result d9 returned from the recipient confirmation information verification unit 63 to the smartphone 91 of the collector 90 (S116).

  Next, a case where the access token is invalid and authentication is NG will be described with reference to FIG.

  The token management unit 73 requests a refresh token from the smartphone 91 of the collector 90 (S120).

  The token management unit 73 receives the refresh token from the smart phone 91 of the collector 90 (S121).

  The token management unit 73 searches the token DB 75 with the received refresh token (S122).

  If the authentication of the refresh token is OK, the token management unit 73 generates a new access token (S123).

  The token management unit 73 updates the token DB 75 with the newly generated access token and generation time (S124).

  The token management unit 73 transmits the generated access token to the smartphone 91 of the collector 90 (S125).

  Thereafter, the token management unit 73 returns to the location where the access token authentication is NG and continues the processing.

  On the other hand, as a result of the search, when the refresh token authentication is NG because the corresponding refresh token does not exist in the token DB 75, the token management unit 73 requests the smart phone 91 of the collector 90 to log in again (S130). ).

  The token management unit 73 deletes the corresponding data in the token DB 75 (S131).

  The token management unit 73 stops the expiration monitoring timer for the refresh token that has been activated and ends (S132).

  Next, as shown in FIG. 20, the token monitoring unit 73 times out the expiration monitoring timer of the activated refresh token (S140).

  The token management unit 73 searches the token DB 75 with the refreshed token that has timed out, reads the corresponding user ID, and notifies the management terminal 80 of the abnormality notification data t2 including the user ID and the time of occurrence of the timeout (S141).

  The token management unit 73 receives the situation information t3 including the situation ID data such as the user ID and the loss input by the administrator from the management terminal 80 (S142).

  Upon receiving the status information t3, the token management unit 73 searches the token DB 75 with the received user ID and deletes the corresponding token information (S143).

  The token management unit 73 transmits the status information t3 to the ID management unit 72 and requests the corresponding user ID to be stopped (S144).

(Smartphone 91 of the collector 90)
The operation of the smartphone 91 in which the confirmation application 91a of the collection / delivery person 90 used as a terminal of the recipient confirmation system 50 of the delivery service company 30 is mounted will be described with reference to FIGS. .

  As shown in FIG. 23A, the icon B1 of the confirmation application 91a is displayed on the screen of the smartphone 91 of the collector / delivery person 90, and the distributor 90 touches the icon B1 to display the confirmation application 91a. Start up and display a login screen (S150).

  The login information d4 of the user ID and password is input by the collection / delivery person 90 to the user ID column C1 and the password column C2 of the login screen shown in FIG. When the input button B2 on the screen is touched, the login information d4 is transmitted to the authentication server 70 (S151).

  When ID authentication is completed in the authentication server 70 and a token is given, and the access token and the refresh token are received from the authentication server 70, the smartphone 91 stores the access token in the temporary storage memory 91b as shown in (c) of FIG. A refresh token is set and the screen of the recipient confirmation start button B3 is displayed (S152).

  When the recipient confirmation start button B3 shown in (c) of FIG. 23 is touched, the smartphone 91 activates the camera as shown in (d) of FIG. 24, and is printed on the invoice by the barcode reader. The bar-coded invoice number is read (S153).

  Furthermore, the smartphone 91 receives GPS data of the current location by the GPS reception function (S154).

  The smartphone 91 displays the read invoice number and the received GPS data in the invoice number column C3 and the GPS data column C4 of the confirmation document type inquiry screen shown in FIG. 24E (S155).

  When the transmission button B4 is touched, the smartphone 91 uses the invoice number displayed on the screen and the GPS data as the delivery place GPS data as the inquiry information d6 together with the access token set in the temporary storage memory 91b. It transmits to the authentication server 70 (S156).

  The smartphone 91 displays a type-corresponding input screen according to the confirmation document type returned from the authentication server 70 (S157).

  As shown in FIG. 24 (f), for example, when the confirmation document type is a car license, an input column C5 of the date of birth is displayed as confirmation data.

  When the confirmation data is input to the input screen and the transmission button B5 is touched, the smartphone 91 transmits the invoice number and the input confirmation data to the authentication server 70 together with the access token as the recipient confirmation data d8 ( S158).

  Upon receiving the verification result from the authentication server 70, the smartphone 91 displays the received data as a verification result screen as shown in (g) of FIG. 24 (S159).

  When the print button B6 displayed on the screen is touched, the smartphone 91 is connected to the portable printer by short-range wireless communication, prints a delivery completion letter, and when the end button B67 is touched, the recipient confirmation starts. The screen is displayed again (S160).

  In this way, at the next and the recipient, the recipient confirmation can be started without performing a login operation.

<Other embodiment 1>
In the embodiment described above, when the consignment management system 40 receives the consignment data d2 from the order management server 21, the collation data d3 is generated and the operation order transmitted to the recipient confirmation server 60 is shown. When the GPS data collation unit 62 receives the inquiry information d6 including the invoice number from the smartphone 91, the order in which the collation data management unit 61 requests the trust management system 40 to transmit the collation data d3 may be used.

  Further, when the collector / deliverer 90 takes out the ordered item from the collection / delivery center for delivery, the invoice number is read by the smartphone 91 from the invoice attached to the ordered item, and the read invoice number is transmitted to the recipient confirmation server 60. The order in which the collation data management unit 61 requests the trust management system 40 to transmit the collation data d3 may be used.

  In this case, if the invoice number transmitted from the collection / delivery person 90 is recorded in the collation DB as a take-out list for each collection / delivery person 90, it can also be used for managing the ordered items taken out from the collection / delivery center.

<Other embodiment 2>
In the above embodiment, the recipient confirmation server 60 of the recipient confirmation system 50 is provided with the GPS data verification unit 62 and has a function of determining whether or not the delivery has been performed near the position designated by the shipper. However, the GPS data matching unit 62 may not be provided.

  That is, the consignment data management unit 42 does not have a function of converting (p8) the recipient address of the consignment data d2 into address position information of latitude and longitude. That is, the collation data d3 does not include address position information of latitude and longitude.

  Further, the smartphone 91 does not have a function of including the delivery place GPS data in the inquiry information d6.

  Further, the token management unit 73 of the authentication server 70 does not have a function of transmitting the delivery place GPS data to the recipient confirmation server 60.

  Further, the verified delivery place GPS data is not stored in the verification DB 64.

  Moreover, the collation data management part 61 does not include the delivery place GPS data in the collation result information d10.

  When the collector / deliverer 90 takes out the ordered item from the collection / delivery center for delivery, the invoice number is read by the smartphone 91 from the invoice attached to the ordered item, and the read invoice number is transmitted to the recipient confirmation server 60. The order in which the collation data management unit 61 requests the trust management system 40 to transmit the collation data d3 may be used.

  In this case, if the invoice number transmitted from the collection / delivery person 90 is recorded in the collation DB as a take-out list for each collection / delivery person 90, it can also be used for managing the ordered items taken out from the collection / delivery center.

  As described above, the embodiment of the recipient confirmation system which is the basis of the present invention and the other embodiments have been described.

  Further, it is preferable that data transmitted and received by the recipient confirmation system of the present invention and stored in each DB is encrypted.

10 ... Ordering person 11 ... PC
20 ... Shipper 21 ... Order Management Server 22 ... Order DB
23 ... Invoice 30 ... Delivery service provider 40 ... Contract management system 41 ... Contract data server 42 ... Contract data management unit 43 ... Contract DB
DESCRIPTION OF SYMBOLS 50 ... Recipient confirmation system 60 ... Recipient confirmation server 61 ... Collation data management part 62 ... GPS data collation part 63 ... Recipient confirmation information collation part 64 ... Collation DB
DESCRIPTION OF SYMBOLS 70 ... Authentication server 71 ... Communication control part 72 ... ID management part 73 ... Token management part 74 ... Authentication DB
75 ... Token DB
80 ... management terminal 90 ... collector 91 ... smartphone 100 ... internet

Claims (7)

Invoice from the shipper printed with the recipient name, recipient address, confirmation document type, recipient confirmation information and invoice number, and the recipient name, recipient address, and barcode of the invoice number And a recipient confirmation system connected to a consignment management system of a delivery service provider who is requested to deliver an order that requires recipient confirmation,
A collation data management unit connected to the trust management system and the collation DB;
A recipient confirmation server including the collation DB and a recipient confirmation information collation unit connected to the collation data management unit;
A collation unit;
A communication control unit connected to the Internet;
An ID management unit connected to the communication control unit and the authentication DB;
An authentication server connected to the recipient confirmation server including the communication control unit, the ID management unit, and a token management unit connected to a token DB;
Connected to the authentication server via the Internet, and includes a smart phone of a collector who has a temporary storage memory, a barcode reader, and a camera;
The collation data management unit
Of the trust data, the invoice number received from the trust management system, the confirmation document type, and collation data including the recipient confirmation information are stored in the collation DB,
Sending verification result information including the verification result received from the recipient confirmation information verification unit to the trust management system;
The collation unit
Search the matching DB with the invoice number included in the inquiry information received from the token management unit, and send the stored confirmation document type to the token management unit,
The recipient confirmation information verification unit
Recipient confirmation data received from the token manager is collated with the recipient confirmation information stored in the collation DB, and a collation result and collation completion date / time are transmitted to the token manager and the collation data manager.
The communication control unit
Control data communication via the Internet between the ID management unit and the token management unit and the smartphone,
The ID management unit
After verifying login information including the user ID and password received from the smartphone with the authentication DB, request a token generation to the token management unit,
The token management unit
In response to the token generation request, an access token and a refresh token are generated and transmitted to the smartphone, and stored in the token DB as token information together with the user ID and generation time,
Search and authenticate the token DB with the access token received with the command from the smartphone,
Deliver the received command to the collation unit or the recipient confirmation information collation unit, send the returned confirmation document type or the collation result and the collation completion date and time to the smartphone,
The smartphone
Transmitting the login information to the authentication server, storing the returned access token and the refresh token in the temporary storage memory;
The barcode of the invoice number printed on the invoice is photographed by the camera and read by the barcode reader, and transmitted to the authentication server together with the access token as the inquiry information,
The recipient confirmation data input on the input screen to be displayed according to the confirmation document type to be returned is transmitted to the authentication server together with the access token,
A recipient confirmation system, wherein the verification result displayed is displayed on a screen to confirm the recipient.   The recipient confirmation system according to claim 1, wherein the smartphone further has a short-range wireless communication function, is connected to a portable printer by short-range wireless communication, and prints a delivery completion letter including the verification result. With a GPS data verification unit,
The verification data includes address location information obtained by converting the recipient address into (latitude, longitude) data by the trust management system,
The smartphone further includes a delivery place GPS data acquired by a GPS receiving function included in the inquiry information, and transmits the data to the authentication server together with the access token.
The GPS data collation unit determines whether the unloading location GPS data received from the token management unit is within an allowable range from the address location information stored in the verification DB. Storing the unloading location GPS data in the verification DB;
The collation data management unit
The recipient confirmation system according to claim 1 or 2, wherein the delivery place GPS data stored in the verification DB is included in the verification result information and transmitted to the trust management system. The authentication server further includes a management terminal connected to the token management unit,
The token management unit
If the time limit monitoring timer that starts when the refresh token is generated times out, the user ID and the occurrence time are notified to the management terminal as an occurrence of an abnormality,
When the user ID and status data are input from the management terminal, the corresponding token information is deleted from the token DB,
Sending the user ID and the situation data to the ID management unit;
The ID management unit
2. The recipient confirmation system according to claim 1, wherein the status data and the invalid flag are set in the authentication DB corresponding to the received user ID. A consignment data including a receiver's name, recipient address, confirmation document type, recipient confirmation information and invoice number from the shipper and a bar code for the recipient name, recipient address and invoice number And a recipient confirmation method in a recipient confirmation system including a verification DB, an authentication DB, and a token DB connected to a delivery management system of a delivery service provider who is requested to deliver an ordered item requiring recipient confirmation. And
Among the entrusted data, the collation data including the invoice number, the confirmation document type, and the recipient confirmation information is stored in the collation DB,
After verifying login information including the user ID and password received from the collector's smartphone via the Internet with the authentication DB, an access token and a refresh token are generated and transmitted to the smartphone, and the token information together with the user ID and generation time Is stored in the token DB as
From the smartphone, the barcode of the invoice number printed on the invoice is photographed with a camera and sent as read inquiry information with a barcode reader together with the access token,
After searching and authenticating the token DB with the access token received from the smartphone, search the verification DB with the invoice number included in the inquiry information, and send the stored confirmation document type to the smartphone,
Recipient confirmation data entered on the input screen displayed according to the confirmation document type on the smartphone, transmitted together with the access token,
After searching and authenticating the token DB with the access token received from the smartphone, the recipient confirmation data is collated with the recipient confirmation information stored in the collation DB, and a collation result and a collation completion date and time are obtained. Send it to your smartphone,
Recipient confirmation method, wherein the verification result is displayed on the screen of the smartphone and the recipient is confirmed. The verification data includes address location information obtained by converting the recipient address into (latitude, longitude) data by the trust management system,
Including the unloading location GPS data acquired by the GPS reception function from the smartphone in the inquiry information, and sending it together with the access token,
Judging whether the unloading location GPS data received from the smartphone is within an allowable range from the address location information stored in the verification DB,
6. The recipient confirmation method according to claim 5, further comprising collating a delivery place. The recipient confirmation system includes a management terminal,
If the time limit monitoring timer that starts when the refresh token is generated times out, the user ID and the occurrence time are notified to the management terminal as an occurrence of an abnormality,
When the user ID and status data are input from the management terminal, the corresponding token information is deleted from the token DB,
7. The recipient confirmation method according to claim 5, wherein the received status data and invalid flag are set in the authentication DB.

Images