JP2010128535A - Delivery confirmation system, portable terminal, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To confirm delivery time, delivery place and a recipient from electronic slip data authenticated. <P>SOLUTION: In a delivery confirmation system 100, a portable terminal 4 for delivery electronically signs delivery slip data including reception confirmation information input through an input part 45 by a recipient at delivery, current time and current location acquired by a GPS 47, and transmits the delivery slip data with electronic signatures to a management server 1. The management server 1 verifies authenticity of the delivery slip data with the electronic signatures received from the portable terminal 4 for delivery using the public key of the portable terminal 4 for delivery, and updates a database 161 in which electronic slip information is stored with the delivery slip data successfully authenticated. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a delivery confirmation system.

  2. Description of the Related Art Conventionally, as a delivery receipt receipt certificate, a slip on which a delivery address is written is signed or stamped by a recipient. However, the authenticity of the information on the receipt certificate is not high, and it is difficult to confirm the time and place of delivery and the authenticity of the recipient's signature or seal.

For example, Patent Document 1 describes a technique for transmitting an electronic document with an electronic signature, an electronic certificate, and a user's handwritten signature image attached thereto.
JP 2003-263647 A

  In Patent Document 1, an electronic signature is added to the text of an electronic document, and a user's handwritten image is additionally added. Therefore, it is possible to verify whether or not the electronic document has been tampered with. In addition, since the user's handwritten image is attached, it is possible to receive an electronic document as if the recipient received a handwritten signature or a stamped document.

  However, in Patent Document 1, since the signature range of the electronic signature is only the text of the electronic document, it cannot be determined whether or not the handwritten image has been altered. In addition, the location and time at which the electronic document was created cannot be verified. Therefore, for example, even if the technique of Patent Document 1 is applied to a delivery receipt proof and an electronic signature and a handwritten image of the recipient are attached to the electronic slip, the delivery time and location of the package cannot be proved, Also, the authenticity of the signature of the recipient's handwritten image cannot be confirmed.

  An object of the present invention is to provide a delivery confirmation system capable of confirming a delivery time, a delivery place, and a recipient using electronic voucher data whose authenticity is ensured.

In order to solve the above-mentioned problem, the invention described in claim 1
A delivery confirmation system comprising a mobile terminal and a server,
The portable terminal is
A communication means for transmitting and receiving data to and from the server;
Time acquisition means for acquiring the current time;
Position acquisition means for acquiring the current position;
An input means for inputting receipt confirmation information indicating that the package recipient has received the package;
An electronic signature is applied to electronic voucher data including the receipt confirmation information input from the input means, the current time output from the time acquisition means, and the current position output from the position acquisition means when delivering the package. Control means for transmitting the electronic slip data with an electronic signature to the server by the communication means;
With
The server
A communication means for transmitting and receiving data to and from the portable terminal;
Control means for verifying authenticity of the electronic slip data with the electronic signature received from the portable terminal by the communication means;
Is provided.

The invention according to claim 2 is the invention according to claim 1,
The portable terminal has a security chip that stores a secret key used when performing an electronic signature on the electronic slip data, and performs an electronic signature on the electronic slip data using the secret key,
The control means of the portable terminal causes the electronic chip data to be digitally signed by the security chip.

The invention according to claim 3 is the invention according to claim 1 or 2,

The server has storage means for storing an electronic certificate of the mobile terminal including a public key of the mobile terminal;
The server control means separates the electronic voucher data with the electronic signature into text data and electronic signature data, the first hash value obtained by decrypting the electronic signature data using the public key, The authenticity of the electronic slip data is verified by comparing with the second hash value calculated by inputting the text data to the hash function.

The invention according to claim 4 is the invention according to any one of claims 1 to 3,
A web server is provided that generates a web page for providing the electronic voucher data with an electronic signature verified to the authenticity to a package requester and a recipient and publishes it on the Internet.

The invention according to claim 5 is the invention according to claim 4,
The delivery confirmation system further includes a client terminal used for a package client and a receiver terminal used for a package receiver;
The server is configured to be connectable to the Internet, and includes notification means for notifying the client terminal and the recipient terminal of the URL of the web page via the Internet.

The invention according to claim 6 is the invention according to claim 5,
The web server accepts a download request for electronic voucher data with an electronic signature whose authenticity is verified from the client terminal or the recipient terminal via the web page, and the authenticity is determined in response to the download request. The electronic voucher data with the digital signature verified and the electronic certificate of the portable terminal are transmitted to the requester terminal or the receiver terminal of the request source.

The invention according to claim 7 is the invention according to any one of claims 1 to 6,
The input means is a touch panel for inputting handwritten characters.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to provide the delivery confirmation system which can confirm delivery time, a delivery place, and a recipient with the electronic slip data with which the authenticity was ensured.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
First, the configuration will be described.

(Configuration of delivery confirmation system 100)
FIG. 1 shows an example of the overall configuration of a delivery confirmation system 100 according to an embodiment of the present invention. As shown in FIG. 1, a delivery confirmation system 100 includes a management server 1, a Web (World Wide Web) server 2, a collection portable terminal 3, a delivery portable terminal 4, a client PC (Personal Computer) 5, and a recipient PC 6. It is configured with.
The management server 1 and the Web server 2 are arranged in a distribution center and are connected to each other via an in-house network N1 such as a LAN (Local Area Network) so that data can be transmitted and received. The in-house network N1 is connected to the Internet N2 via a router R or the like, and the management server 1 and Web server 2 are a client PC5, a recipient PC6, and a certificate authority server (not shown) via the Internet N2. Etc., and data can be transmitted and received. In order to ensure security, the management server 1 preferably transmits and receives data to and from each device on the Internet N2 via a firewall.
The mobile terminal 3 for collection and the mobile terminal 4 for delivery are mobile terminals possessed by a collector who collects the package from the client and a deliverer who delivers the package to the recipient. However, when the collector or delivery person returns to the distribution center, it can be connected to the in-house network N1 via a cradle (not shown). In addition, the number of each device of the collection portable terminal 3, the delivery portable terminal 4, the client PC 5 and the recipient PC 6 is not particularly limited.

(Configuration of management server 1)
In FIG. 2, the example of a principal part structure of the management server 1 is shown. As shown in FIG. 2, the management server 1 includes a CPU 11, a RAM (Random Access Memory) 12, a ROM (Read Only Memory) 13, an input unit 14, a display unit 15, a storage unit 16, a communication unit 17, a scanner unit 18, A timer unit 19 is provided, and each unit is connected via a bus 101.

  The CPU 11 reads out a system program stored in the ROM 13, develops it in a work area formed in the RAM 12, and controls each unit according to the system program. Further, the CPU 11 reads out various processing programs stored in the ROM 13 and develops them in the work area, and executes various processes including a collection slip verification process and a delivery slip verification process described later.

  The RAM 12 temporarily stores various programs read from the ROM 13 by the CPU 11, input or output data, parameters, and the like.

  The ROM 13 stores a system program executed by the CPU 11, a program for executing various processes, data necessary for executing these programs, and the like. The program is stored in the ROM 13 in the form of computer-readable program code, and the CPU 11 sequentially executes operations according to the program code.

  The input unit 14 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse. The input signal is input to the CPU 11 by key operation or mouse operation on the keyboard. Output.

  The display unit 15 includes an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), an organic EL (Electro-Luminescence) display, and the like, and displays various screens according to instructions of a display signal input from the CPU 11.

  The storage unit 16 is configured by an HDD (Hard Disc Drive) or the like. The storage unit 16 has a database 161. The database 161 stores electronic slip information in the delivery confirmation system 100.

  FIG. 3 shows a data configuration example of a record (electronic slip information) stored in the database 161. As shown in FIG. 3, each record stored in the database 161 is composed of management information, client information, collection information, recipient information, delivery information, collection form data electronic signature, delivery form data electronic signature, and the like. Yes.

  The management information includes a reception date, a slip number, and a product name. The reception date is a date when a request for delivery of the package from the client is received. The slip number is a number uniquely given to a package delivery request from a client. The product name is the product name of the package requested for delivery. In the present embodiment, delivery includes both collection and delivery of packages.

  The requester information includes the name, telephone number, postal code, address, desired collection date and time, e-mail address, etc. of the delivery requester.

  The collection information includes GPS position information, GPS time information, a collection confirmation signature, and client entry information. The GPS position information is position information acquired by GPS (Global Positioning System) at the time of package collection and indicates a location where the package is actually collected. The GPS time information is time information acquired by the GPS when the package is collected, and indicates the time when the package is actually collected. The collection confirmation signature is collection confirmation information indicating that the collection has been confirmed, which is input by the client when the package is collected. The client entry information is arbitrary information input by the client when the package is collected.

  The recipient information includes the name, telephone number, postal code, address, desired delivery date and time, e-mail address, etc. of the recipient of the package.

  The delivery information is composed of GPS position information, GPS time information, receipt confirmation signature, and recipient entry information. The GPS position information is position information acquired by GPS at the time of delivery (delivery) of the package, and indicates a location where the package was actually delivered (delivered to the recipient). The GPS time information is time information acquired by GPS at the time of delivery of a package (when a package is delivered), and indicates a time at which the package is actually delivered (delivered to a recipient). The receipt confirmation signature is receipt confirmation information indicating that the package has been received, which is input by the recipient when the package is delivered. The recipient entry information is arbitrary information entered by the recipient when the package is delivered.

The collection form data electronic signature is electronic signature data given to electronic document data for collection (hereinafter referred to as collection form data) by the collection portable terminal 3.
The delivery form data electronic signature is electronic signature data given to delivery electronic slip data (hereinafter referred to as delivery form data) by the delivery portable terminal 4.

  Returning to FIG. 2, the communication unit 17 includes a modem, a router, a TA (Terminal Adapter), and the like, and via the in-house network N1 and the Internet N2, the Web server 2, the collection mobile terminal 3, the delivery mobile terminal 4, Controls data transmission / reception with an external device such as the client PC 5.

  The scanner unit 18 includes a barcode reader, a barcode scanner, or the like that reads a barcode provided on a collection slip or the like.

  The timer unit 19 is configured by an RTC (Real Time Clock) or the like, and measures the current time and the current date and outputs them to the CPU 11.

(Configuration of Web server 2)
Since the configuration of the Web server 2 is substantially the same as the configuration of the management server 1, the same components are denoted by the same reference numerals, and the illustration of the configuration is omitted. That is, the Web server 2 includes a CPU 21, a RAM 22, a ROM 23, an input unit 24, a display unit 25, a storage unit 26, a communication unit 27, and a time measuring unit 29, and each unit is connected via a bus 201.

  The ROM 23 stores a system program executed by the CPU 21, a program for executing a function as a Web server, a program for executing various processes such as a delivery request registration process and a delivery status tracking page providing process. ing. The storage unit 26 stores various page data (HTML (HyperText Markup Language) file or the like) for displaying a Web page such as a delivery request registration page. The CPU 21 executes a delivery request registration process, a delivery status tracking page provision process, and the like according to a program stored in the ROM 23, and a delivery request registration page (see FIG. 9) and a delivery status tracking page (see FIGS. 29 and 30). Web pages such as are published on the Internet.

  About each other component, since it is the same as that of what was demonstrated about the management server 1, description is used.

(Configuration of mobile terminal 3 for collection and mobile terminal 4 for delivery)
FIG. 4 shows a configuration example of main parts of the mobile terminal 3 for collection and the mobile terminal 4 for delivery.
As shown in FIG. 4, the collection portable terminal 3 includes a CPU 31, a RAM 32, a ROM 33, a security chip 34, an input unit 35, a display unit 36, a GPS 37, a communication unit 38, a printing unit 39, and a scanner unit 301. Each unit is connected via a bus 302. The delivery portable terminal 4 includes a CPU 41, a RAM 42, a ROM 43, a security chip 44, an input unit 45, a display unit 46, a GPS 47, a communication unit 48, a printing unit 49, and a scanner unit 401, and each unit is connected via a bus 402. Connected.
As shown in FIG. 4, the collection portable terminal 3 and the delivery portable terminal 4 have the same configuration. Therefore, the collection portable terminal 3 will be described as a representative, and the description of the delivery portable terminal 4 will be referred to. To do.

  The CPU 31 reads a system program stored in the ROM 33, develops it in a work area formed in the RAM 32, and controls each unit according to the system program. Further, the CPU 31 reads out various processing programs stored in the ROM 33 and develops them in the work area, and executes various processes including a collection confirmation input process described later.

  The RAM 32 temporarily stores various programs read from the ROM 33 by the CPU 31, input or output data, parameters, and the like.

  The ROM 33 stores a system program executed by the CPU 31, various processing programs, and data necessary for executing these programs. The program is stored in the ROM 33 in the form of computer-readable program code, and the CPU 31 sequentially executes operations according to the program code.

  The security chip 34 is a dedicated device for creating and storing a secret key and a public key. The security chip 34 cannot be accessed from an external program, and the security of data stored inside is ensured. In addition, the security chip 34 performs an electronic signature on the input data by a public key cryptosystem using a stored secret key, and outputs it to the CPU 31.

The input unit 35 includes a numeric keypad, a cursor key, a power ON / OFF key, various function buttons, and the like, and outputs an operation signal based on a key or button pressing signal to the CPU 31. The function buttons include a collection slip download button for instructing the download of the collection slip data from the management server 1, and a collection slip upload button for instructing the upload of the collection slip data to the management server 1 (portable terminal 4 for delivery). Includes a delivery slip download button for instructing download of delivery slip data from the management server 1, a delivery slip upload button for instructing upload of delivery slip data to the management server 1, and the like.
The input unit 35 has a touch panel provided so as to cover the display screen of the display unit 36, and is based on a coordinate reading principle such as an electromagnetic induction type, a magnetostriction type, a pressure sensitive type, etc., with a dedicated pen. The tapped coordinate is detected, and the detected coordinate is output to the CPU 31 as a position signal.

  The display unit 36 is configured by an LCD, an organic EL display, or the like, and displays various screens according to instructions of a display signal input from the CPU 31.

  The GPS 37 includes a GPS antenna (not shown). The GPS antenna receives GPS signals transmitted from a plurality of GPS satellites launched into a low earth orbit. The GPS antenna receives GPS signals transmitted from at least three GPS satellites, acquires the absolute current position (latitude, longitude) and current time of the collection portable terminal 3 based on the received GPS signals. , Output to the CPU 31.

  The communication unit 38 is an interface for connecting to a cradle (not shown) on the in-house network N1, and performs data transmission / reception with an external device such as the management server 1 and the Web server 2 connected to the in-house network N1 via the cradle. .

(Configuration of client PC5 and recipient PC6)
The client PC 5 and the recipient PC 6 are computer terminals that have a CPU, RAM, ROM, input unit, display unit, communication unit, etc. (all not shown) and have a Web browser function.

(Generate server certificate and terminal certificate)
Next, the operation of the delivery confirmation system 100 will be described.
As a premise of the operation in the delivery confirmation system 100, the management server 1, the collection portable terminal 3, and the delivery portable terminal 4 obtain an electronic certificate that proves the authenticity of its public key from a certificate authority (CA), Saved. The electronic certificate of the management server 1 is called a server certificate, and the electronic certificates of the collection mobile terminal 3 and the delivery mobile terminal 4 are called terminal certificates. The certificate authority has an electronic certificate (referred to as a CA certificate) that is publicly certified by another certificate authority and proves the authenticity of its public key.

  FIG. 5 shows a flow of a server certificate acquisition process executed between the management server 1 and a certificate authority server (not shown). The processing on the management server 1 side is executed by the cooperation of the CPU 11 and the program.

  First, certificate information is input by the input unit 14 (step S1). The certificate information is information necessary for applying for an electronic certificate, and is information indicating the company name, organization name, address, and the like of the entity that owns the management server 1.

  Next, a key pair of a secret key and a public key used for public key encryption is generated in the management server 1 (step S2). Next, certificate request data including certificate information and a public key is transmitted to the certificate authority server by the communication unit 17 (step S3).

  In the certificate authority server, when the certificate request data transmitted from the management server 1 is received, the received certificate request data, that is, the certificate information of the management server 1 and the public key are added to the digital signature of the certificate authority. Is given, a server certificate of the management server 1 is generated (step S4). The digital signature of the certificate authority is obtained by calculating the hash value by the hash function with the certificate request data as input and encrypting the calculated hash value with the secret key of the certificate authority. The server certificate is data including certificate information of the management server 1, a public key, and an electronic signature of a certificate authority. If the value obtained by decrypting the digital signature of the certificate authority with the public key of the certificate authority and the hash value calculated by the hash function with the certificate information and the public key of the management server 1 as input, the certificate authority of the management server 1 The certificate information and public key are proved. The certificate authority confirms the authenticity of the contents of the certificate information, and the server certificate is generated only when it is correct.

When the server certificate is generated, the certificate authority transmits the generated server certificate to the management server 1 (step S5).
In the management server 1, when the server certificate transmitted from the certificate authority server is received by the communication unit 17, the server certificate is stored and stored in the storage unit 16 (step S6).
In the certificate authority server, the generated server certificate of the management server 1 is stored, and when the server certificate of the management server 1 is requested from the outside, the server certificate is disclosed.

  FIG. 6 shows a flow of a terminal certificate acquisition process executed between the collection mobile terminal 3 or the delivery mobile terminal 4 and the server of the certificate authority. Since the processing of the collection portable terminal 3 and the delivery portable terminal 4 is the same, the collection portable terminal 3 will be described below as a representative, and the description of the delivery portable terminal 4 will be referred to. The processing on the collection mobile terminal 3 (delivery mobile terminal 4) side is executed in cooperation with the CPU 31 (CPU 41) and the program.

  First, certificate information is input by the input unit 35 (step S11). The certificate information is information necessary for applying for an electronic certificate, and is information indicating the company name, organization name, address, etc. of the entity that owns the collection portable terminal 3.

  Next, the security chip 34 generates and stores a private key / public key pair used for public key encryption in the collection portable terminal 3 (step S12). Next, certificate request data including certificate information and a public key is transmitted to the certificate authority server by the communication unit 38 (step S13).

  When the certificate request server receives the certificate request data from the collection portable terminal 3, the certificate authority server adds the certificate authority's electronic signature to the received certificate request data, that is, the certificate information and the public key. Thus, the terminal certificate of the collection portable terminal 3 is generated (step S14). The digital signature of the certificate authority is obtained by calculating the hash value by the hash function with the certificate request data as input and encrypting the calculated hash value with the secret key of the certificate authority. The terminal certificate is data including certificate information and public key (certificate request data) of the collection portable terminal 3 and an electronic signature of the certificate authority. If the value obtained by decrypting the digital signature of the certificate authority with the public key of the certificate authority and the hash value calculated by the hash function using the certificate information and the public key of the collection portable terminal 3 as input, the certificate authority uses for collection The certificate information and the public key of the portable terminal 3 are certified. The certificate authority confirms the authenticity of the contents of the certificate information, and the terminal certificate is generated only when it is correct.

When the terminal certificate is generated, the generated terminal certificate is transmitted to the collection portable terminal 3 by the server of the certificate authority (step S15).
In the collection portable terminal 3, when the terminal certificate transmitted from the certificate authority server is received by the communication unit 38, the terminal certificate is transferred to the management server 1 by the communication unit 38 (step S16).

In the management server 1, when the terminal certificate transmitted from the collection mobile terminal 3 is received by the communication unit 17, the terminal certificate is stored in the storage unit 16 in association with the terminal ID of the collection mobile terminal 3. (Step S17).
In the certificate authority server, the generated terminal certificate of the collection portable terminal 3 is stored, and when the terminal certificate of the collection portable terminal 3 is requested from the outside, the terminal certificate is disclosed. The

(Processing flow between devices of delivery confirmation system 100)
Next, with reference to FIGS. 7A to 30, processing of each device in the delivery confirmation system 100 from delivery request by the client to delivery of the package to the recipient and confirmation thereof will be described.

7A to 7B show a processing flow of the delivery confirmation system 100 as a whole.
As shown in FIG. 7A, first, the client PC 5 accesses the URL (Uniform Resource Locator) of the delivery request registration page (step T1). The URL of the delivery request registration page is widely open to the public.

  In the Web server 2, when the client PC 5 accesses the URL of the delivery request registration page, a delivery request registration process is executed (step T2).

  FIG. 8 shows a flowchart of the delivery request registration process executed by the Web server 2 in step T2 of FIG. 7A. The delivery request registration process is executed in cooperation with the CPU 21 and the program stored in the ROM 23 when the URL of the delivery request registration page is accessed.

  In the delivery request registration process, first, page data for displaying a delivery request registration page is read from the storage unit 26 and transmitted to the client PC 5 by the communication unit 27 (step T101).

  In the client PC 5, when page data for displaying a delivery request registration page is received from the Web server 2, a delivery request registration page 501 is displayed on the display unit as shown in FIG. Is performed (step T3 in FIG. 7A).

  FIG. 9 shows an example of the delivery request registration page 501 displayed on the client PC 5. As shown in FIG. 9, the delivery request registration page 501 includes an input field 501a for inputting the contents of input items such as the name of the package to be delivered, the requester information, the recipient information, and the delivery based on the input contents. A delivery request button 501b for instructing a request is displayed. When the client PC 5 makes an input to the input field 501a of the delivery request registration page 501 using an input unit such as a keyboard or a mouse, and the delivery request button 501b is pressed, the inputted information (delivery request data) is transferred to the Web server 2. Sent to.

  Returning to FIG. 8, when the delivery request data transmitted from the client PC 5 is received by the communication unit 27 (step T102; YES), each input item included in the delivery request data is verified (step T103). For example, it is verified whether or not there is an error item or the like that has not been input or has no data type.

  When there is an error item in the delivery request data (step T103; NG), the communication unit 27 transmits instruction data for instructing the requester PC 5 to display the error item and prompting re-input (step T104). Return to Step T102. If there is no error item in the delivery request data (step T103; OK), the delivery request data is transferred to the management server 1 by the communication unit 27, and new electronic slip information is registered in the database 161 (step T105, FIG. 7A). Step T4). Specifically, in the management server 1, a new record is added to the database 161, a slip number is assigned, and the product name, requester information, and recipient information of the received delivery request data are registered in the new record. Then, the delivery request registration process ends.

  In the Web server 2, a delivery request registration process is executed each time an access request to the delivery request registration page from the client PC 5 is received.

  In the management server 1, as shown in FIG. 7A, when a predetermined start time of the collection form data creation process comes (step T5 in FIG. 7A; YES), the collection form data creation process is executed (FIG. 7A). Step T6).

FIG. 10 shows a collection slip data creation process executed by the CPU 11 of the management server 1 in step T6 of FIG. 7A. This collection form data creation processing is executed in cooperation with the CPU 11 and the program stored in the ROM 13.
Note that the ROM 13 has a collection slip data creation process start time, a collection time (collection start time and collection end time), a delivery slip data creation process start time, and a delivery time (delivery start time and delivery end time), which will be described later. Assume that it is stored in advance. The collection form data creation process is paired with collection, and the collection form data creation process is scheduled to be executed before the start of collection. The delivery form data creation process is paired with delivery, and the delivery form data creation process is scheduled to be executed before the start of delivery. Pick-up and delivery are performed one or more times per day.

  In the collection form data creation process, first, electronic slip information (record) that is in an uncollected state and whose desired collection date and time is within the range of the next collection time is extracted from the database 161 (step T201). Specifically, the uncollected electronic slip information is a record in which no data is written in the item of the collection information.

  Next, the extracted electronic voucher information is sorted by the address of the client information and the desired collection date and time (step T202), and the sorted electronic voucher information is divided by the number of units that can be collected by one collector, A data set is created (step T203). The collection form data is data composed of management information, client information, recipient information, and collection information necessary for collection in the electronic slip information. At this point, the data of each item of the collection information is empty and can be added later. The collection form data is temporarily stored in the RAM 12.

Next, the process waits for the collection portable terminal 3 to be connected (step T204).
When the collection time arrives, the collector places the collection portable terminal 3 on the cradle and presses the collection form download button. When the collection portable terminal 3 is placed on a cradle (not shown) and the collection form download button is pressed, a collection form data download process (see FIG. 11) is executed as shown in FIG. 7A (see FIG. 7A). Step T7). The collection slip data download process will be described later.

Returning to FIG. 8, when the download request from the collection mobile terminal 3 is received by the communication unit 17 (step T204; YES), the RAM 12 is referred to and it is determined whether or not the collection form data exists (step S204). T205). When it is determined that the collection form data exists in the RAM 12 (step T205; YES), a response to the effect that the collection form data exists is transmitted to the collection portable terminal 3 by the communication unit 17 (step T206). A set of collection form data is read and transmitted to the collection portable terminal 3 by the communication unit 17 (step T207). Then, the process proceeds to step T209. Note that the collected collection slip data is deleted from the RAM 12.
When it is determined that the collection form data does not exist in the RAM 12 (step T205; NO), a response that the collection form data does not exist is transmitted to the collection portable terminal 3 by the communication unit 17 (step T208), and the process is step. The process proceeds to T209.

  In step T209, it is determined whether or not the collection end time has arrived based on the output from the time measuring unit 19, and if it is determined that the collection end time has not arrived (step T209; NO), the process proceeds to step T209. Return to T204. On the other hand, if it is determined that the collection end time has arrived (step T209; YES), the collection form data creation process ends.

  FIG. 11 shows a flowchart of the collection form data download process executed by the CPU 31 of the collection portable terminal 3 in step T7 of FIG. 7A. The collection form data download process is executed in cooperation with the CPU 31 and the program stored in the ROM 33.

  First, a collection form data download request is transmitted to the management server 1 by the communication unit 38 (step T301).

  Next, the process enters a standby state for a response from the management server 1. When the communication unit 38 does not receive a response from the management server 1 for a predetermined time or longer (step T302; NO), an error message indicating that there is no response from the management server 1 is displayed on the display unit 36 (step T303). The vote data download process ends. For example, the case where no response is received from the management server 1 corresponds to, for example, the case where the management server 1 is not operating due to some failure or the like, or the case where the collection form processing is not executed in the management server 1.

  When the response from the management server 1 is received by the communication unit 38 (step T302; YES), it is determined based on the received response whether or not the collection form data exists in the management server 1 (step T304). When it is determined that the collection form data does not exist in the server 1 (step T304; NO), a message indicating that the collection form data does not exist in the management server 1 is displayed on the display unit 36 (step T305). The download process ends.

  On the other hand, when it is determined that the collection form data exists in the management server 1 (step T304; YES), the collection form data sequentially transmitted from the management server 1 is downloaded by the communication unit 38 and stored in the RAM 32 (step T306). ). When the download is completed, a message indicating that the download of the collection form data has been completed is displayed on the display unit 36 (step T307), and the collection form data download process ends.

  In the collection portable terminal 3, as shown in FIG. 7A, when the collection form data download process is completed, a collection confirmation input process is executed (step T6 in FIG. 7A).

  12A to 12B show a flowchart of the collection confirmation input process executed by the CPU 31 of the collection portable terminal 3 in step T6 of FIG. 7A. The collection confirmation input process is executed in cooperation with the CPU 31 and the program stored in the ROM 33.

  First, a list of client information is displayed on the display unit 36 based on the downloaded collection slip data (step T401 in FIG. 12A). The screen displayed in step T401 displays a slip processing button for instructing slip processing for pickup from the client selected from the list together with a list of client information of the pickup slip data. Is done.

  When the client information is selected by the input unit 35 and the slip processing button is pressed (step T402; YES), the current position information is acquired from the GPS 37, and whether the current position is within a certain range from the address of the client information. It is determined whether or not (step T403). If it is determined that the current position acquired from the GPS 37 is not within a certain range from the address of the client information (step T403; NO), for example, “It is not near the client address. Please check the client information”, etc. Is displayed (step T404), and the process returns to step T401.

  When it is determined that the current position acquired from the GPS 37 is within a certain range from the address of the client information (step T403; YES), a collection slip screen 361 is displayed on the display unit 36 (step T405).

  FIG. 13 shows an example of the collection slip screen 361 displayed in step T405. As shown in FIG. 13, the collection slip screen 361 displays collection slip data 361a, a collection confirmation button 361b, and a return button 361c. The collection confirmation button 361b is a button for instructing transition to the collection confirmation signature screen 362 (see FIG. 14). The return button 361c is a button for instructing to return the display on the display unit 36 to the client information list. The collector displays this collection slip screen 361 to the client and requests confirmation of whether the contents of the collection slip data are correct. If there is no mistake in the contents of the collection form data, the collector receives the package from the requester, presses the collection confirmation button 361b by the input unit 35, and inputs the collection confirmation signature.

  If the collection confirmation button 361b is not pressed on the collection slip screen 361 (step T406 in FIG. 12A; NO) and the return button 361c is pressed (step T407; YES), the process returns to step T401. When the collection confirmation button 361b is pressed on the collection slip screen 361 (step T406; YES), a collection confirmation signature screen 362 is displayed on the display unit 36 (step T408).

  FIG. 14 shows an example of the collection confirmation signature screen 362 displayed on the display unit 36 in step T408. As shown in FIG. 14, the collection confirmation signature screen 362 displays a collection confirmation signature column 362a, a client entry column 362b, and an OK button 362c. The collection confirmation signature column 362a is an area for the client to input the collection confirmation signature by hand using a touch pen or the like. The client entry field 362b is an area for the client to input an arbitrary figure or character by handwriting. The OK button 362c is a button that is pressed to proceed to the next processing when the input of a signature or the like is completed.

  When the OK button 362c is pressed by the input unit 35 on the collection confirmation signature screen 362 (step T409; YES), it is determined whether or not an input is made in the collection confirmation signature column 362a, and it is determined that no input is made. When it is done (step T410; NO), for example, a message for prompting the collection confirmation signature such as “It is not signed in the collection confirmation signature column. Please sign” is displayed on the display unit 36 (step T411), and processing is performed. Returns to step T408.

  If it is determined that the collection confirmation signature field 362a has been input (step T410; YES), current position information and current time information are acquired from the GPS 37 (step T412 in FIG. 12B), and the acquired current position information and The current time information is added as GPS position information and GPS time information of the collection information of the collection slip data, respectively, and the data input from the collection confirmation signature column 362a is used as the collection confirmation signature of the collection information from the client entry column 362b. The input data is added to the collection slip data as client entry information (step T413).

  Next, electronic signature processing is performed using the collection slip data with the collection information added as input data (step T414).

FIG. 15 shows a flowchart of the electronic signature process. The electronic signature process is executed in cooperation with the CPU 31 and a program stored in the ROM 33.
First, a hash value is calculated from input data (here, collection slip data) using a hash function (step A1).

  Next, the hash value is transferred to the security chip 34, and the hash value is encrypted using the private key of the collection portable terminal 3 in the security chip 34 (step A2). This encrypted hash value is electronic signature data.

Next, the input data and the electronic signature data are combined and stored in the RAM 32 (step A3). Then, the electronic signature process ends.
Data obtained by combining the collection form data and the electronic signature data is called collection form data with an electronic signature.

Returning to FIG. 12B, when the electronic signature process is completed, the collection slip D is printed by the printing unit 39 based on the collection slip data with the electronic signature (step T415).
FIG. 16 shows an example of the collection slip D printed in step T415 of FIG. 12B. In the collection slip D, collection slip data D1, collection confirmation data D2, and a barcode image D3 indicating electronic signature data are displayed. The data in the client entry column that the client arbitrarily entered at the time of collection is not printed on the collection slip D. This collection slip D is attached to the collected package.

  The processes of steps T401 to T415 are repeatedly executed until the collection slip data with an electronic signature is created for all the collection slip data or the collection end instruction is input from the input unit 35 until the collection ends. Is finished (step T416; YES), the collection confirmation input process is finished.

  When the collection is completed, the collector returns to the distribution center with the collection portable terminal 3 and delivers the collected packages to the distribution center. Then, the collection portable terminal 3 is placed on a cradle (not shown) and the collection form upload button of the input unit 35 is pressed. When the collection portable terminal 3 is placed on the cradle and the collection form upload button is pressed, the collection form data upload process is executed as shown in FIG. 7A (step T9 in FIG. 7A).

  FIG. 17 shows a flowchart of the collection form data upload process executed by the CPU 31 in step T9 of FIG. 7A. The collection form data upload process is executed in cooperation with the CPU 31 and the program stored in the ROM 33.

  First, it is determined whether or not the collection form data (including collection form data with an electronic signature) exists in the RAM 32. If it is determined that the collection form data does not exist (step T501; NO), “There was no collection form” or the like. Is displayed on the display unit 36 (step T502), and the collection slip data upload process ends.

  When it is determined that the collection form data exists in the RAM 32 (step T501; YES), an upload request is transmitted to the management server 1 by the communication unit 38, and the collection form data stored in the RAM 32 is transmitted to the management server 1. (Step T503). The collected collection slip data is deleted from the RAM 32.

  Next, it is determined whether or not the collection form data exists in the RAM 32. If it is determined that the collection form data exists (step T504; YES), the process returns to step T503, and the next collection form data is transmitted to the management server 1 by the communication unit 38. Sent to. If it is determined that the collection form data does not exist in the RAM 32 (step T504; NO), the collection form data upload process ends.

  In the management server 1, as shown in FIG. 7A, when an upload request is received from the collection mobile terminal 3 by the communication unit 17, a collection form verification process is executed (step T10).

  FIGS. 18A to 18B show a flowchart of the collection form verification process executed by the CPU 11 of the management server 1 in step T10 of FIG. 7A. This process is executed in cooperation with the CPU 11 and the program stored in the ROM 13.

  First, collection form data is acquired from the collection portable terminal 3 by the communication unit 17 (step T601). Next, it is determined whether or not the received collection form data has an electronic signature. If it is determined that the received collection form data does not have an electronic signature (step T602; NO), the process proceeds to step T616 in FIG. 18B.

  If it is determined that the received collection form data is signed (step T602; YES), verification processing of data with an electronic signature is executed using the collection form data as input data (step T603).

  FIG. 19 shows a flowchart of verification processing of data with an electronic signature. The verification process of the data with the electronic signature is executed in cooperation with the CPU 11 and the program stored in the ROM 13.

  First, the input data is separated into text data and electronic signature data, which are associated with each other and stored in the RAM 12 (step A11).

  Next, the electronic signature data is decrypted with the public key of the collection portable terminal 3 to obtain a first hash value (step A12). As described above, the storage unit 16 stores the terminal certificate of the collection portable terminal 3, and the public key is acquired from the terminal certificate.

  Next, the second hash value is calculated by the hash function using the body data as input (step A13). Then, the first hash value and the second hash value are compared (step A14).

  If the first hash value matches the second hash value (step A14; YES), the authenticity of the collection form data has been successfully verified (that is, the collection form data is the same as at the time of the electronic signature and has been tampered with. Is not output) (step A15), and the verification process of the data with the electronic signature ends. On the other hand, if the first hash value and the second hash value do not match (step A14; NO), the verification of the authenticity of the collection form data has failed (that is, the collection form data is different from the time of the electronic signature). And a verification result indicating that the data has been tampered with is output (step A16), and the verification process of the data with the electronic signature ends.

  Returning to FIG. 18A, when the verification process of the data with the electronic signature is completed, it is determined based on the verification result of the process whether or not the authenticity of the received collection form data has been successfully verified (step T604). . If it is determined that the verification of the authenticity of the received collection form data has failed (step T604; NO), the verification of the authenticity of the collection form data such as “the verification of the collection form data has failed” has failed. A message indicating that it has been displayed is displayed on the display unit 15 (step T605), and the process proceeds to step T616 in FIG. 18B.

  When it is determined that the authenticity of the received collection slip data has been successfully verified (step T604; YES), the display unit 15 displays “Please scan the collection slip attached to the collection with the slip number XX”. "A message prompting the user to scan the package collection slip is displayed (step T606). When the collection slip D is read by the scanner unit 18 (step T607; YES), it is determined whether the value acquired by the scanner unit 18 matches the value of the electronic signature data of the collection slip data (FIG. 18B, step T608). Here, if the value acquired by the scanner unit 18 matches the value of the electronic signature data, it indicates that the pickup form data and the pickup are the same. Further, it is verified that the electronic signature data used for verifying the collection slip data has not been tampered with.

  If it is determined that the value acquired by the scanner unit 18 and the value of the electronic signature data of the collection form data do not match (step T608; NO), such as “the collection and the collection form do not match”, etc. A message indicating that the collection form data does not match the collection is displayed (step T609). For example, when the collection unit D is scanned again by the scanner unit 18 (for example, when the collection unit D is scanned incorrectly) (step T610; YES), the process returns to step T608. If the scan is not performed again (step T610; NO), the process proceeds to step T616.

  When it is determined that the value acquired by the scanner unit 18 matches the value of the electronic signature data of the collection form data (step T608; YES), the received collection form data and the slip number are stored in the database 161. A matching record is searched, and the searched record is updated with the received collection slip data (step T611). Specifically, management information, client information, collection information, recipient information, and collection slip data electronic signature (electronic signature data of collection slip data) included in the received collection slip data are written in the retrieved record. It is.

  Next, in the retrieved record, it is determined whether or not the mail address of the client information is stored. If it is determined that it is stored (step T612; YES), the delivery status tracking page (FIG. 29, FIG. 30) is sent to the email address of the client information by the communication unit 17 (step T613), and the process proceeds to step T614. The delivery status tracking page is a Web page for requesters and recipients to check the delivery status. The URL includes, for example, information for specifying the storage position in the database 161 of the searched record. If it is determined that the email address of the client information is not stored in the retrieved record (step T612; NO), the process proceeds to step T614.

  In step T614, it is determined whether or not the mail address of the recipient information is stored in the retrieved record. If it is determined that it is stored (step T614; YES), the URL of the delivery status tracking page Is sent to the mail address of the recipient information by the communication unit 17 (step T615), and the process proceeds to step T616. If it is determined that the e-mail address of the recipient information is not stored in the retrieved record (step T614; NO), the process proceeds to step T616.

  In step T616, it is determined whether or not the communication unit 17 has received a request for transmission of the next collection form data from the collection portable terminal 3, and if it is determined that a transmission request for the next collection form data has been received ( Step T616; YES), the process returns to Step T601. If it is determined that the connection request has not been received since the next collection form data transmission request has not been received (step T616; NO), the collection form verification process ends.

  The collection form verification process is executed every time an upload request from the collection portable terminal 3 is received.

  In the management server 1, as shown in FIG. 7A, when a predetermined delivery slip data creation processing start time arrives (step T11 in FIG. 7A; YES), the delivery slip data creation processing is executed (step T12). ).

  FIG. 20 shows a delivery form data creation process executed by the CPU 11 of the management server 1. This delivery form data creation process is executed in cooperation with the CPU 11 and a program stored in the ROM 13.

  In the delivery slip data creation process, first, electronic slip information (record) that is undelivered and whose desired delivery date and time is within the range of the next delivery time is extracted from the database 161 (step T701). The undelivered electronic slip information is a record in which no data is written in the delivery information.

  Next, the extracted electronic voucher information is sorted by the address of the recipient information and the desired delivery date and time (step T702), and the sorted electronic voucher information is divided by the number of units that can be delivered by one delivery person, and the delivery slip A data set is created (step T703). The delivery slip data is data including management information necessary for delivery, client information, recipient information, collection information, delivery information, and collection slip data electronic signature among electronic slip information. At this time, the data of each item of delivery information is empty and can be stored later.

Next, the process waits for the delivery portable terminal 4 to be connected.
When the delivery time arrives, the delivery person places the delivery portable terminal 4 on the cradle and presses the delivery form download button. In the delivery portable terminal 4, when the delivery person places it on a cradle (not shown) and presses the delivery form download button, the delivery form data download process (see FIG. 21) shown in FIG. 7A is executed (FIG. 7A). Step T13). The delivery form data download process will be described later.

  Returning to FIG. 20, when the download request from the delivery portable terminal 4 is received by the communication unit 17 (step T704; YES), the RAM 12 is referred to and it is determined whether or not delivery form data exists (step S704). T705). If it is determined that the delivery form data exists in the RAM 12 (step T705; YES), a response to the effect that the delivery form data exists is transmitted from the communication unit 17 to the delivery portable terminal 4 (step T706). A set of delivery form data is read and transmitted to the delivery portable terminal 4 by the communication unit 17 (step T707). Then, the process proceeds to step T709. The transmitted delivery slip data is deleted from the RAM 12.

  On the other hand, if it is determined that there is no delivery form data in the RAM 12 (step T705; NO), a response to the effect that no delivery form data exists is transmitted to the delivery portable terminal 4 by the communication unit 17 (step T708), and processing Moves to step T709.

  In step T709, it is determined whether or not the delivery end time has arrived based on the output from the time measuring unit 19, and if it is determined that the delivery end time has not arrived (step T709; NO), the process proceeds to step T709. Return to T704. On the other hand, if it is determined that the delivery end time has arrived (step T709; YES), the delivery form data creation process ends.

  FIG. 21 shows a flowchart of the delivery form data download process executed by the CPU 41 of the delivery portable terminal 4 in step T13 of FIG. 7A. The delivery slip data download process is executed in cooperation with the CPU 41 and the program stored in the ROM 43.

  First, a download request is transmitted to the management server 1 by the communication unit 48 (step T801).

  Next, the process enters a standby state for a response from the management server 1. When the communication unit 48 does not receive a response from the management server 1 for a predetermined time or longer (step T802; NO), an error message indicating that there is no response from the management server 1 is displayed on the display unit 46 (step T803). The vote data download process ends. For example, the case where no response is received from the management server 1 corresponds to, for example, the case where the management server 1 is not operating due to some failure or the like, or the case where the delivery server data creation process is not executed in the management server 1.

  When the response from the management server 1 is received by the communication unit 48 (step T802; YES), it is determined based on the received response whether delivery form data exists in the management server 1 (step T804). If it is determined that there is no delivery form data in the management server 1 (step T804; NO), a message indicating that there is no delivery form data in the management server 1 is displayed on the display unit 46 (step T805). The data download process ends.

  On the other hand, if it is determined that the delivery form data exists in the management server 1 (step T804; YES), the delivery form data sequentially transmitted from the management server 1 is downloaded by the communication unit 48 and stored in the RAM 42 (step T806). ). When the download is completed, a message indicating that the delivery form data has been downloaded is displayed on the display unit 46 (step T807), and the delivery form data download process ends.

  When the delivery table data download process ends, the delivery portable terminal 4 executes a delivery package confirmation process as shown in FIG. 7A (step T14 in FIG. 7A).

  FIG. 22 shows a flowchart of delivery package confirmation processing executed by the CPU 41 of the delivery portable terminal 4. The delivery package confirmation process is executed in cooperation with the CPU 41 and the program stored in the ROM 43.

  First, a message such as “Please scan the barcode on the collection slip attached to the delivery” is displayed on the display unit 46 (step T901). When the barcode image D3 of the collection slip attached to the delivery item is read by the scanner unit 401 (step T902; YES), the value acquired by the scanner unit 401 and each delivery slip data stored in the RAM 42 are stored. The value of the collection slip electronic signature data is collated, and it is determined whether or not the delivery slip data in which the value acquired by the scanner unit 401 matches the value of the collection slip electronic signature data exists in the RAM 42 (step T903).

  If it is determined that there is no delivery form data in the RAM 42 that matches the value obtained by scanning and the value of the electronic signature data of the collection form (step T903; NO), “The package is not included in the delivery form data. "A message indicating that there is no delivery form data of the scanned delivery is displayed on the display unit 46 (step T904), and the process proceeds to step T906.

  If it is determined that there is delivery slip data in the RAM 42 that matches the value acquired by scanning and the value of the electronic signature data of the collection slip (step T903; YES), there is a corresponding delivery in the matching delivery slip data. Is attached (referred to as a delivery tag) (step T905). Next, it is determined whether or not a delivery tag is attached to all delivery form data stored in the RAM 42 (step T906).

  If it is determined that the delivery tag is attached to all the delivery slip data stored in the RAM 42 (step T906; YES), “All packages corresponding to the delivery slip data have been confirmed”, etc. A message indicating that all deliverables corresponding to the delivery slip data have been confirmed is displayed on the display unit 46 (step T907), and the delivery parcel confirmation process ends.

  On the other hand, when it is determined that there is delivery form data to which no delivery tag is attached (step T906; NO), it is determined whether or not an instruction to interrupt scanning is input by the input unit 45 (step T908). If it is determined by the input unit 45 that a scan interruption instruction has not been input (step T908; NO), the process returns to step T901. When it is determined that the scan interruption instruction is input by the input unit 45 (step T908; YES), delivery slip data to which no delivery tag is attached is extracted from the delivery slip data stored in the RAM 42, The slip number of the extracted delivery slip data is stored in the variable N (step T909). Then, a message indicating that there is no delivery of slip number N is displayed, such as “The delivery of slip number N cannot be found. Please contact the person in charge”, and the delivery parcel confirmation processing is performed. finish.

  When the delivery package confirmation process is completed, the delivery confirmation input process is executed in the delivery portable terminal 4 as shown in FIG. 7B (step T15 in FIG. 7B).

  23A to 23B show a flowchart of the delivery confirmation input process executed by the CPU 41 of the delivery portable terminal 4 in step T15 of FIG. 7B. The delivery confirmation input process is executed in cooperation with the CPU 41 and the program stored in the ROM 43.

  First, a list of recipient information is displayed on the display unit 46 based on the downloaded delivery slip data (step T1001 in FIG. 23A). A screen (not shown) displayed in step T1001 is used for instructing slip processing for delivery to a recipient selected from the list together with a list of recipient information of delivery form data. A slip processing button is displayed.

  When the recipient information is selected by the input unit 45 and the slip processing button is pressed (step T1002; YES), the current location information is acquired from the GPS 47, and whether the current location is within a certain range from the address of the recipient information. It is determined whether or not (step T1003). If it is determined that the current position acquired from the GPS 47 is not within a certain range from the address of the recipient information (step T1003; NO), “It is not near the recipient address. Please check the recipient information”, etc. A message indicating that it is not near the recipient address is displayed on the display unit 46 (step T1004), and the process returns to step T1001.

  When it is determined that the current position acquired from the GPS 47 is within a certain range from the address of the recipient information (step T1003; YES), a collection slip screen 461 is displayed on the display unit 46 (step T1005). The collection slip screen 461 is the same screen as that described with reference to FIG.

  If the collection confirmation button 461b is not pressed on the collection slip screen 461 (step T1006; NO) and the return button 461c is pressed (step T1007; YES), the process returns to step T1001. When the collection confirmation button 461b is pressed on the collection slip screen 461 (step T1006; YES), a collection confirmation signature screen 462 is displayed on the display unit 46 (step T1008).

  FIG. 24 shows an example of the collection confirmation signature screen 462 displayed on the display unit 46 in step T1008. As shown in FIG. 24, the collection confirmation signature screen 462 displays a collection information column 462a, a collection confirmation signature column 462b, a requester entry column 462c, and a receipt confirmation signature button 462d. The collection information column 462a is an area in which the GPS position information and GPS time information of the collection information included in the delivery slip data are displayed. The collection confirmation signature column 462a is an area for displaying a collection confirmation signature input by the client using a touch pen or the like at the time of collection. The client entry field 462c is an area for displaying an arbitrary figure or character input by the client at the time of pickup. The receipt confirmation signature button 462d is a button that is pressed to shift to a receipt confirmation signature screen 463 (see FIG. 25) for inputting a receipt confirmation signature.

  When the receipt confirmation signature button 462d is pressed by the input unit 45 on the collection confirmation signature screen 462 (step T1009; YES), the receipt confirmation signature screen 463 is displayed on the display unit 46 (step T1010).

FIG. 25 shows an example of the receipt confirmation signature screen 463.
As shown in FIG. 25, the receipt confirmation signature screen 463 displays a receipt confirmation signature column 463a, a recipient entry column 463b, and an OK button 463c. The receipt confirmation signature field 463a is an area for the recipient to input the receipt confirmation signature by hand using a touch pen or the like. The recipient entry field 463b is an area for the recipient to input an arbitrary figure or character by handwriting. The OK button 463c is a button that is pressed to proceed to the next processing when the input of a signature or the like is completed.

  When the OK button 463c is pressed by the input unit 45 on the receipt confirmation signature screen 463 (step T1011; YES), it is judged whether or not an entry is made in the receipt confirmation signature field 463a, and it is judged that no entry has been made. When this is done (step T1012; NO), a message prompting the receipt confirmation signature such as “Signature is not signed in the receipt confirmation signature field. Please sign” is displayed on the display unit 46 (step T1013). It returns to step T1010.

  If it is determined that the receipt confirmation signature field 463a has been input (step T1012; YES), current position information and current time information are acquired from the GPS 47 (step T1014 in FIG. 23B), and the acquired current position information and The current time information is added as GPS position information and GPS time information of the delivery information of the delivery slip data, respectively, and the data input from the receipt confirmation signature column 463a is used as the receipt confirmation signature of the delivery information from the recipient entry column 463b. The input data is added to the delivery form data as recipient entry information (step T1015).

  Next, electronic signature processing is performed using the delivery slip data storing the delivery information as input data (step T1016 in FIG. 23B). Since the flow of the electronic signature process is the same as that described with reference to FIG. In step T1016, the electronic signature process is executed using the delivery slip data to which the delivery information is added as input data. Note that the secret key of the delivery portable terminal 4 is used for encryption of the hash value. Data obtained by combining delivery form data and electronic signature data is referred to as delivery form data with electronic signature.

  The processes of steps T1001 to T1016 are repeatedly executed until the delivery slip data with the electronic signature is created for all the delivery slip data or the delivery end instruction is input from the input unit 45 until the delivery ends. Is completed (step T1017; YES), the delivery slip confirmation input process ends.

  When the delivery is completed, the delivery person carries the delivery portable terminal 4 and returns to the delivery center, places the delivery portable terminal 4 in a cradle (not shown), and presses the delivery form upload button of the input unit 35. When the delivery portable terminal 4 is placed on the cradle and the delivery form upload button is pressed, the delivery form data upload process is executed as shown in FIG. 7B (step T16 in FIG. 7B).

  FIG. 26 shows a flowchart of the delivery form data upload process executed by the CPU 41 of the delivery portable terminal 4 in step T16 of FIG. 7B. The delivery form data upload process is executed in cooperation with the CPU 41 and the program stored in the ROM 43.

  First, it is determined whether or not the delivery slip data (including delivery slip data with an electronic signature) exists in the RAM 42. If it is determined that the delivery slip data does not exist (step T1101; NO), “There was no delivery slip” A message indicating that there is no delivery form data, such as, is displayed on the display unit 46 (step T1102), and the delivery form data upload process ends.

  If it is determined that there is delivery slip data in the RAM 42 (step T1101; YES), an upload request is transmitted to the management server 1 by the communication unit 48, and the delivery slip data stored in the RAM 42 is transmitted to the management server 1. (Step T1103). The transmitted delivery slip data is deleted from the RAM 42.

  Next, it is determined whether or not the delivery form data exists in the RAM 42. If it is determined that the delivery form data exists (step T1104; YES), the process returns to step T1103, and the next delivery form data is transmitted by the communication unit 48 to the management server 1 Sent to. If it is determined that there is no delivery form data in the RAM 42 (step T1104; YES), the delivery form data upload process ends.

  In the management server 1, as shown in FIG. 7B, when an upload request is received from the delivery portable terminal 4 by the communication unit 17, a delivery slip verification process is executed (step T17 in FIG. 7B).

  FIG. 27 shows a flowchart of the delivery slip verification process executed by the CPU 11 of the management server 1 in step T17 of FIG. 7B. This process is executed in cooperation with the CPU 11 and the program stored in the ROM 13.

  First, the delivery form data is acquired from the delivery portable terminal 4 by the communication unit 17 (step T1201). Next, it is determined whether or not the received delivery slip data has an electronic signature. If it is determined that the delivery signature data does not have an electronic signature (step T1202; NO), the process proceeds to step T1211.

  If it is determined that the received delivery slip data is signed (step T1202; YES), verification processing of data with an electronic signature is executed using the delivery slip data as input data (step T1203). The verification process for data with an electronic signature is the same as that described with reference to FIG. As the public key used for decrypting the data with the electronic signature, the public key acquired from the terminal certificate of the delivery portable terminal 4 stored in the storage unit 16 is used.

  When the verification process of the data with the electronic signature is completed, it is determined whether or not the verification of the authenticity of the delivery form data is successful based on the verification result of the process (step T1204). If it is determined that the verification of the authenticity of the delivery slip data has failed (step T1204; NO), a message indicating an error such as “delivery slip verification failed” is displayed on the display unit 15 (step T1205). ), And the process proceeds to step T1211.

  If it is determined that the authenticity of the delivery slip data has been successfully verified (step T1204; YES), the database 161 is searched for a record whose slip number matches the received delivery slip data, and the retrieved record is received. It is updated with the delivered delivery form data (step T1206). Specifically, management information, client information, collection information, recipient information, collection slip data electronic signature, delivery information, delivery slip data electronic signature (delivery slip data electronic signature data) included in the delivery slip data is Written to the retrieved record.

  Next, in the retrieved record, it is determined whether or not the mail address of the client information is stored. If it is determined that it is stored (step T1207; YES), the delivery status tracking page (FIG. 29, FIG. 30) is sent to the email address of the client information by the communication unit 17 (step T1208), and the process proceeds to step T1209. The delivery status tracking page is a Web page for requesters and recipients to check the delivery status. The URL includes, for example, information for specifying the storage position in the database 161 of the searched record. If it is determined that the email address of the client information is not stored in the retrieved record (step T1207; NO), the process proceeds to step T1209.

  In step T1209, it is determined whether or not the mail address of the recipient information is stored in the retrieved record. If it is determined that it is stored (step T1209; YES), the URL of the delivery status tracking page Is sent to the mail address of the recipient information by the communication unit 17 (step T1210), and the process proceeds to step T1211. If it is determined that the e-mail address of the recipient information is not stored in the retrieved record (step T1209; NO), the process proceeds to step T1211.

  In step T1211, it is determined whether or not the next delivery form data transmission request has been received from the delivery portable terminal 4 by the communication unit 17, and if it is determined that the next delivery form data transmission request has been received ( Step T1211; YES), the process returns to Step T1201. When it is determined that the connection request has not been received since the next delivery form data transmission request has not been received (step T1211; NO), the delivery form verification process ends.

  As shown in FIG. 7B, when the client PC5 and the recipient PC6 access the URL of the delivery status tracking page notified from the management server 1 (steps T18 and T19), the Web server 2 performs the delivery status tracking page providing process. It is executed (step T20).

  FIG. 28 shows a flowchart of the delivery status tracking page providing process executed by the CPU 21 of the Web server 2 in step T20 of FIG. 7B.

  First, based on the URL specified by the requester PC5 or the recipient PC6, an inquiry for electronic slip information corresponding to the requester PC5 or the recipient PC6 is made to the database 161 of the management server 1 (step T1301).

  The management server 1 searches the database 161 for the electronic slip information specified by the designated URL, and if the corresponding electronic slip information is not searched, the Web server 2 indicates that the corresponding electronic slip information does not exist. Responded. The corresponding electronic voucher information is searched, and when the electronic voucher information includes delivery information and delivery slip electronic signature data, a response indicating that the delivery has been completed and verified is transmitted to the Web server 2. In addition, when the electronic slip information does not include delivery information and delivery slip electronic signature data, but the collection information and the collection slip electronic signature data are included, a response indicating that the pickup has been completed and verified It is transmitted to the Web server 2. As shown in FIGS. 18B and 27, the URL is notified only to the requester and recipient who have collected and verified the requested delivery, or have been delivered and verified. If the search does not correspond to any of the above, the Web server 2 responds that there is no corresponding electronic slip information.

  Next, based on the response from the management server 1, it is determined whether or not the electronic slip information specified by the URL has been collected and verified (step T1302). When it is determined that the electronic voucher information specified by the URL has been collected and verified (step 1302; YES), the electronic voucher information is acquired from the management server 1, and based on the acquired electronic voucher information, Page data is generated to display the first delivery status tracking page (step T1303). Then, the generated page data is transmitted by the communication unit 27 to the requesting client PC 5 or the recipient PC 6 (step T1304), and the delivery status tracking page providing process ends.

  FIG. 29 shows an example of the first delivery status tracking page 700 displayed at the client PC 5 or the recipient PC 6. The first delivery status tracking page 700 is delivered from, for example, the client PC 5 or the recipient PC 6 after the delivery status tracking page URL is notified in step T10 in FIG. 7A and before the delivery slip verification process in step T17 is completed. Displayed when the status tracking page is accessed. As shown in FIG. 29, the delivery status tracking page 700 displays information necessary for confirming collection of the electronic slip information. Specifically, the contents D11 of the collection slip data with electronic signature, the image D12 of the collection confirmation signature, and the image D13 in the requester entry column are displayed. The client can check whether there is an error in the contents of the delivery request, whether the contents signed and filled in at the time of collection are falsified, or the like. The recipient can confirm the contents requested by the client and that the pickup has been made. Note that a “file download” button B 1 is displayed on the first delivery status tracking page 700. When the button B1 is pressed, the client PC 5 or the receiver PC 6 receives the collection slip data with electronic signature, the CA certificate of the certificate authority, and the terminal certificate of the collection portable terminal 3 used at the time of collection. People can download and verify the authenticity of the data themselves.

  Returning to FIG. 28, when it is determined that the electronic voucher information specified by the URL has not been collected or verified (step 1302; NO), is the electronic voucher information specified by the URL already delivered and verified? It is determined whether or not (step T1305). When it is determined that the electronic voucher information specified by the URL has been delivered and verified (step 1305; YES), the electronic voucher information is acquired from the management server 1, and based on the acquired electronic voucher information, Page data is generated to display the second delivery status tracking page (step T1306). Then, the generated page data is transmitted by the communication unit 27 to the requesting client PC 5 or the recipient PC 6 (step T1307), and the delivery status tracking page providing process ends.

  On the other hand, when it is determined that the electronic voucher information specified by the URL is not delivered or verified (step 1305; NO), the designated delivery such as “the delivery designated by the URL does not exist” or the like. The page data notifying that there is no data is read from the storage unit 26 and transmitted to the requester PC 5 or the recipient PC 6 as the access source by the communication unit 27 (step T1308), and the delivery status tracking page providing process ends.

  FIG. 30 shows an example of the second delivery status tracking page 701. As shown in FIG. 30, the second delivery status tracking page 701 displays information necessary for confirming the collection and delivery of the electronic slip information. Specifically, the contents D21 of the delivery slip data with the electronic signature, the image D22 of the collection confirmation signature, the image D23 of the requester entry column, the image D24 of the receipt confirmation signature, and the image D25 of the recipient entry column are displayed. The client can confirm whether the package has arrived at the recipient, whether there is an error in the contents of the delivery request, the date and place of the collection, whether the contents signed or filled in at the time of collection have been tampered with, etc. . The recipient can confirm whether or not the place, date and time of receipt, receipt confirmation signature, entry column, etc. have been tampered with. Note that a “file download” button B 2 is displayed on the second delivery status tracking page 701. When the button B2 is pressed, the client PC 5 or the recipient PC 6 uses the electronically signed delivery form data and the CA certificate of the certificate authority, the terminal certificate of the collection portable terminal 3 used at the time of collection, and is used at the time of delivery. The requester / recipient can download the terminal certificate of the delivery portable terminal 4 and verify the authenticity of the data.

  As described above, according to the delivery confirmation system 100, the collection mobile terminal 3 uses the collection confirmation information input from the input unit 35 by the client at the time of package collection, the current time and the current acquired by the GPS 37. An electronic signature is applied to the collection form data including the position, and the collection form data with the electronic signature is transmitted to the management server 1. The management server 1 verifies the authenticity of the collection slip data with the electronic signature received from the collection mobile terminal 3 using the public key of the collection mobile terminal 3, and uses the collection slip data that has been successfully verified for authenticity. The database 161 storing the electronic slip information is updated.

  Accordingly, since the collection slip data including the collection time, collection location, and collection confirmation information of the client who has been verified for authenticity is stored in the database 161, the collection time, the collection with the information whose authenticity is ensured later. It is possible to confirm the collection confirmation information input by the location and the client.

  Further, according to the delivery confirmation system 100, the delivery portable terminal 4 includes the delivery confirmation information inputted from the input unit 45 by the recipient at the time of delivery of the package, the delivery including the current time and the current position acquired by the GPS 47. An electronic signature is applied to the slip data, and delivery slip data with the electronic signature is transmitted to the management server 1. The management server 1 verifies the authenticity of the delivery slip data with the electronic signature received from the delivery mobile terminal 4 using the public key of the delivery mobile terminal 4, and uses the delivery slip data that has been successfully verified for authenticity. The database 161 storing the electronic slip information is updated.

  Accordingly, the delivery date data including the delivery time, delivery location, and receipt confirmation information inputted by the recipient is stored in the database 161. It is possible to confirm the delivery location and the receipt confirmation information of the recipient.

  In addition, the collection portable terminal 3 and the delivery portable terminal 4 have a security chip that cannot be accessed by an external program, and store a secret key used when an electronic signature is applied to the security chip and use the secret key. Since the electronic signature is performed on the collection form data and the delivery form data, the security of the secret key, the collection form data, and the delivery form data can be ensured.

  In addition, the management server 1 stores a terminal certificate including the public key of the collection mobile terminal 3. When receiving the collection form data with the electronic signature from the collection mobile terminal 3, the management server 1 converts the collection data into the main text data and the electronic signature data. The first hash value obtained by separating and decrypting the electronic signature data using the public key of the collection portable terminal 3 is compared with the second hash value calculated by inputting the body data into the hash function. By doing so, the authenticity of the collection slip data can be verified. Similarly, the management server 1 stores a terminal certificate including the public key of the delivery portable terminal 4, and when receiving delivery form data with an electronic signature from the delivery portable terminal 4, the body data and the electronic signature data And the first hash value obtained by decrypting the electronic signature data using the public key of the delivery portable terminal 4 and the second hash value calculated by inputting the body data into the hash function. By comparing, the authenticity of the delivery form data can be verified.

  Further, the delivery confirmation system 100 is a delivery status tracking which is a web page for providing electronic voucher data (collection voucher data, delivery voucher data) with an electronic signature whose authenticity has been verified to a package requester and a recipient. A Web server 2 that generates pages and publishes them on the Internet is provided. Accordingly, the requester and recipient of the package can easily check on the Web whether the package has been collected, whether the package has arrived at the delivery center, or whether the package has been delivered.

  Further, since the URL of the delivery status tracking page is notified to the client PC 5 and the receiver PC 6, the client and the receiver can check whether the package has been collected or the package has been delivered on the Web. It can be easily confirmed.

  The Web server 2 accepts a download request for electronic voucher data (collection voucher data, delivery voucher data) with an electronic signature whose authenticity has been verified from the client PC 5 or the recipient PC 6 on the delivery status tracking page. In response to this, collection form data with an electronic signature, delivery form data, terminal certificate, etc., whose authenticity is verified are transmitted. Therefore, the client PC 5 and the receiver PC 6 can download the collection slip data and the delivery slip data so that the requester and the receiver themselves can verify the authenticity of the data.

  Since collection confirmation information and receipt confirmation information are input from a touch panel for handwritten input, collection confirmation information and receipt confirmation information should be input in the same sense as collection confirmation and receipt confirmation using a conventional signature. Is possible.

In addition, the description content in the said embodiment is a suitable example of the delivery confirmation system 100 which concerns on this invention, and is not limited to this.
For example, in the above embodiment, the input means is a touch panel, and the client or recipient inputs a handwritten collection confirmation signature or receiver signature from the touch panel when collecting or receiving the package. The collection confirmation information indicating that the item has been confirmed and the receipt confirmation information indicating that the recipient has confirmed that the package has been received are not limited thereto. For example, it is not limited to a touch panel as long as it is an input means for inputting information that can identify an individual such as an image of a client or a recipient, an electronic seal stamp, a fingerprint, an iris, etc., instead of a handwritten signature.

  In the above embodiment, the management server 1 and the Web server 2 have been described as separate bodies. However, the management server 1 may be a single server in which the function of the Web server 2 is built.

  In the above embodiment, the electronic signature data (collection slip data, delivery slip data) including information for confirming the time, position, and pickup (recipient) at both the time of collection and delivery is electronically signed. However, the system may be configured to check only at the time of collection or delivery.

  In the above embodiment, the collection portable terminal 3 and the delivery portable terminal 4 are connected to the in-house network N1 via the cradle and transmit / receive data to / from the management server 1. The method of data transmission / reception with the portable terminal 3 and the delivery portable terminal 4 is not limited to this. For example, data transmission / reception may be performed by wireless communication, or a data communication cable such as USB (Universal Serial Bus). It is good also as performing data transmission / reception directly via.

  In addition, the detailed configuration and detailed operation of each device constituting the delivery confirmation system 100 can be changed as appropriate without departing from the spirit of the invention.

It is a figure which shows the example of whole structure of the delivery confirmation system in embodiment of this invention. It is a block diagram which shows the functional structure of the management server of FIG. It is a figure which shows the data structural example of the electronic slip information stored in the database of FIG. It is a block diagram which shows the functional structure of the portable terminal for collection of FIG. 1, and the portable terminal for delivery. It is a figure which shows the flow of the server certificate acquisition process performed between the management server of FIG. 1, and the server of a certification authority. It is a figure which shows the flow of the terminal certificate acquisition process performed between the portable terminal for collection (delivery portable terminal) of FIG. 1, and the server of a certification authority. It is a figure which shows the flow of a process of the delivery confirmation system whole shown in FIG. It is a figure which shows the flow of a process of the delivery confirmation system whole shown in FIG. It is a flowchart which shows the delivery request registration process performed by CPU of the Web server of FIG. An example of the delivery request registration page displayed on the display part of client PC of FIG. 1 is shown. It is a flowchart which shows the collection form data creation process performed by CPU of the management server of FIG. It is a flowchart which shows the collection tag data download process performed by CPU of the portable terminal for collection of FIG. It is a flowchart which shows the collection confirmation input process performed by CPU of the portable terminal for collection of FIG. It is a flowchart which shows the collection confirmation input process performed by CPU of the portable terminal for collection of FIG. It is a figure which shows an example of the collection slip screen displayed on the portable terminal for collection and the portable terminal for delivery of FIG. It is a figure which shows an example of the collection confirmation signature screen displayed on the portable terminal for collection of FIG. It is a flowchart which shows the electronic signature process performed by CPU of the portable terminal for collection of FIG. 1, and the portable terminal for delivery. It is a figure which shows an example of the collection slip printed in the portable terminal for collection of FIG. It is a flowchart which shows the collection tag data upload process performed by CPU of the portable terminal for collection of FIG. It is a flowchart which shows the collection form verification process performed by CPU of the management server of FIG. It is a flowchart which shows the collection form verification process performed by CPU of the management server of FIG. It is a flowchart which shows the verification process of the data with an electronic signature performed by CPU of the management server of FIG. It is a flowchart which shows the delivery slip data preparation process performed by CPU of the management server of FIG. It is a flowchart which shows the delivery slip data download process performed by CPU of the delivery portable terminal of FIG. It is a flowchart which shows the delivery package confirmation process performed by CPU of the delivery portable terminal of FIG. It is a flowchart which shows the delivery confirmation input process performed by CPU of the delivery portable terminal of FIG. It is a flowchart which shows the delivery confirmation input process performed by CPU of the delivery portable terminal of FIG. It is a figure which shows an example of the collection confirmation signature screen displayed on the display part of the delivery portable terminal of FIG. It is a figure which shows an example of the receipt confirmation signature screen displayed on the display part of the delivery portable terminal of FIG. It is a flowchart which shows the delivery form data upload process performed by CPU of the delivery portable terminal of FIG. It is a flowchart which shows the delivery slip verification process performed by CPU of the management server of FIG. It is a flowchart which shows the delivery status tracking page provision process performed by CPU of the Web server of FIG. It is a figure which shows an example of the 1st delivery status tracking page displayed in client PC5 or recipient PC6 of FIG. It is a figure which shows an example of the 2nd delivery status tracking page displayed in client PC5 or recipient PC6 of FIG.

Explanation of symbols

100 delivery confirmation system 1 management server 11 CPU
12 RAM
13 ROM
14 Input unit 15 Display unit 16 Storage unit 161 Database 17 Communication unit 18 Scanner unit 19 Timekeeping unit 101 Bus 2 Web server 21 CPU
22 RAM
23 ROM
24 Input Unit 25 Display Unit 26 Storage Unit 27 Communication Unit 29 Timekeeping Unit 201 Bus 3 Portable Terminal 31 for Collecting CPU
32 RAM
33 ROM
34 Security chip 35 Input unit 36 Display unit 37 GPS
38 Communication Unit 39 Printing Unit 301 Scanner Unit 302 Bus 4 Portable Terminal 41 for Delivery CPU
42 RAM
43 ROM
44 Security chip 45 Input unit 46 Display unit 47 GPS
48 Communication unit 49 Printing unit 401 Scanner unit 402 Bus 5 Client PC
6 Recipient PC

Claims (7)

A delivery confirmation system comprising a mobile terminal and a server,
The portable terminal is
A communication means for transmitting and receiving data to and from the server;
Time acquisition means for acquiring the current time;
Position acquisition means for acquiring the current position;
An input means for inputting receipt confirmation information indicating that the package recipient has received the package;
An electronic signature is applied to electronic voucher data including the receipt confirmation information input from the input means, the current time output from the time acquisition means, and the current position output from the position acquisition means when delivering the package. Control means for transmitting the electronic slip data with an electronic signature to the server by the communication means;
With
The server
A communication means for transmitting and receiving data to and from the portable terminal;
Control means for verifying authenticity of the electronic slip data with the electronic signature received from the portable terminal by the communication means;
Delivery confirmation system with. The portable terminal has a security chip that stores a secret key used when performing an electronic signature on the electronic slip data, and performs an electronic signature on the electronic slip data using the secret key,
The delivery confirmation system according to claim 1, wherein the control means of the portable terminal causes the electronic chip data to be digitally signed by the security chip. The server has storage means for storing an electronic certificate of the mobile terminal including a public key of the mobile terminal;
The server control means separates the electronic voucher data with the electronic signature into text data and electronic signature data, the first hash value obtained by decrypting the electronic signature data using the public key, The delivery confirmation system according to claim 1 or 2, wherein the authenticity of the electronic slip data is verified by comparing the second hash value calculated by inputting the text data into the hash function.   4. A web server for generating a web page for providing the electronic voucher data with an electronic signature whose authenticity is verified to a package requester and a recipient and publishing the web page on the Internet. The delivery confirmation system according to one item. The delivery confirmation system further includes a client terminal used for a package client and a receiver terminal used for a package receiver;
The delivery confirmation system according to claim 4, wherein the server is configured to be connectable to the Internet, and includes a notification unit that notifies the client terminal and the recipient terminal of the URL of the web page via the Internet.   The web server accepts a download request for electronic voucher data with an electronic signature whose authenticity is verified from the client terminal or the recipient terminal via the web page, and the authenticity is determined in response to the download request. 6. The delivery confirmation system according to claim 5, wherein the electronic voucher data with the electronic signature verified and the electronic certificate of the portable terminal are transmitted to the requester terminal or recipient terminal of the request source.   The delivery confirmation system according to any one of claims 1 to 6, wherein the input means is a touch panel for inputting handwritten characters.

Images