Delivery system and delivery management method

Abstract

To provide a novel delivery system.SOLUTION: A delivery system includes: a first acquisition part to acquire invoice identification information on an invoice attached to a package to be delivered; a second acquisition part to acquire destination information based on a recognition result, in which a character string representing the destination information is recognized according to a captured image of a form attached to the package, the form having the destination information written thereon capable of identifying a destination; and a first processing part to store, in a storage part, the invoice identification information acquired by the first acquisition part and the destination information acquired by the second acquisition part.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a delivery system and a delivery management method. [Background technology]

[0002] When a delivery requester delivers a package to a destination, the delivery requester writes the recipient's address, name, telephone number, etc. on a delivery slip, attaches it to the package, and takes it to a delivery center or has a delivery company collect it. Also, when creating a waybill, there are services that allow the delivery requester to input the recipient's address, etc. into a terminal device and print the waybill based on the input information using a printer at the delivery requester. Users can select any of the various ways to create a waybill and create it. There is also a system in which the user requesting delivery inputs information such as the delivery destination into a terminal device in advance, and when the user bringing the package to the delivery company's base, a delivery label is printed based on the information input in advance, creating a shipping label (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, although users can create invoices and request delivery in a variety of ways, it would be desirable to be able to provide a new delivery mechanism.

[0005] The present invention has been made in view of the above circumstances, and its object is to provide a delivery system and a delivery management method that can provide a new delivery mechanism. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a delivery system having a first acquisition unit that acquires waybill identification information of a waybill attached to a package to be delivered, a second acquisition unit that acquires destination information based on a recognition result in which a character string representing the destination information is recognized from an image of a fill-in form attached to the package, the fill-in form having destination information that can identify the destination filled in, and a first processing unit that stores the waybill identification information acquired by the first acquisition unit and the destination information acquired by the second acquisition unit in a memory unit.

[0007] Another aspect of the present invention is a delivery management method executed by a computer, which includes acquiring waybill identification information of a waybill attached to a package to be delivered, acquiring destination information based on a recognition result in which a character string representing the destination information is recognized from an image of a fill-in form attached to the package, the fill-in form having destination information that can identify the destination, and storing the acquired waybill identification information and the acquired destination information in a memory unit. [Effects of the Invention]

[0008] As described above, according to the present invention, a new delivery mechanism can be provided. Even if you don't have a dedicated device for printing shipping labels, the user can digitally link the delivery destination to the shipping label, and the delivery person can use the shipping label as is to make the delivery. It is also possible to request delivery using both the entry form and the shipping label. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a schematic block diagram showing the configuration of a delivery system S according to an embodiment of the present invention. [Figure 2] 10 is a diagram showing an example of the appearance of an invoice L. FIG. [Figure 3]1 is a diagram showing an example of the appearance of an entry form OP, which is a medium separate from an invoice. [Figure 4] FIG. 2 is a schematic functional block diagram showing the functions of the delivery management server 30. [Figure 5] FIG. 2 is a schematic functional block diagram showing the functions of a deliverer terminal 50a. [Figure 6] FIG. 10 is a diagram showing an example of delivery data stored in a storage unit 302. [Figure 7] FIG. 2 is a diagram illustrating the operation of the delivery system S. [Figure 8] FIG. 10 is a conceptual diagram illustrating the flow of a registration process. [Figure 9] FIG. 2 is a diagram illustrating the operation of the delivery system S. [Figure 10] FIG. 1 is a conceptual diagram illustrating the flow of receiving a package. [Figure 11] FIG. 2 is a diagram illustrating the operation of the delivery system S. [Figure 12] FIG. 2 is a diagram illustrating the operation of the delivery system S. [Figure 13] 10 is a flowchart illustrating the operation of the delivery management server 30. DETAILED DESCRIPTION OF THE INVENTION

[0010] A delivery system S according to one embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of a delivery system S according to one embodiment of the present invention. The delivery system S includes a user terminal 10 (10a, 10b), a POS terminal 20, a delivery management server 30, an invoice printing server 40, an invoice printing device 41, a deliverer terminal 50 (50a, 50b), a mobile printer 55 (55a, 55b), and a network NW.

[0011] The user terminal 10 (10a, 10b) is a terminal device used by a user. The user may be either a general consumer or an employee of a company or organization. When used by a general consumer, the user terminal 10 is used at the general consumer's home or on the go. When the user terminal 10 is used by an employee of a company or organization, it is used in a facility managed by the company or organization. For example, the user terminal 10a is used by a user who has requested delivery, and the user terminal 10b is used by a user at the destination of the package (for example, a recipient). The user terminal 10 may be, for example, any of a smartphone, a tablet, a mobile phone, a PC (Personal Computer), etc. If the user terminal 10 has a camera, it can read a machine-readable code. The machine-readable code represents invoice identification information that individually identifies an invoice, and may be any of a one-dimensional barcode, a two-dimensional barcode, etc. The machine-readable code is attached to the invoice. The user terminal 10 also has a display function for displaying various data on a display screen, an input function for inputting various data, etc. The display screen may be a liquid crystal display panel provided on the deliverer terminal 50. Data is input via an input device such as a touch panel, keyboard, or mouse based on operational input from the user. The input data may be, for example, destination information or delivery requester information. Furthermore, if the user terminal 10 is not equipped with a camera or if a camera is not used, the input data may be waybill identification information. The user terminal 10 is communicably connected to the delivery management server 30 via the network NW.

[0012] The POS terminal 20 is communicably connected to the delivery management server 30 via the network NW. The POS terminal 20 optically reads the machine-readable code attached to the shipping invoice using a scanner, and also processes the payment of the delivery fee from the user who has requested the delivery. The POS terminal 20 is installed at a base. The base is a base that manages packages for delivery in response to a request from a user who is the delivery requester. The bases include a collection base where packages are collected, a relay base where the collected packages are relayed before being delivered to the destination user, and the like. Of these, the POS terminal 20 is installed at a collection point. The collection point may be, for example, a base that accepts parcels from delivery requesters, such as a delivery company office, a convenience store, a drugstore, or a private shop.

[0013] The delivery management server 30 is communicably connected to the user terminal 10a, the user terminal 10b, the POS terminal 20, the shipping label print server 40, the deliverer terminal 50a, and the deliverer terminal 50b via the network NW. The delivery management server 30 executes various processes related to delivery.

[0014] The invoice printing server 40 is communicably connected to the delivery management server 30 via the network NW, and is also communicably connected to the invoice printing device 41. The invoice printing server 40 receives number range data representing the number range used for invoices from the delivery management server 30, and causes the invoice printing device 41 to print an invoice based on the number range data. The invoice printer 41 is communicably connected to the invoice print server 40. The invoice printer 41 prints invoices by printing on a print medium based on the number band data output from the invoice print server 40. The print medium used as an invoice has one main surface that is printable, and the other main surface has an adhesive layer formed thereon and a release paper attached thereto. The user who made the delivery request or the person in charge of collection at the collection point can attach the shipping label to the package by peeling off the release paper and attaching the adhesive side to the package. Such shipping label can be used as a shipping label.

[0015] The deliverer terminals 50 (50a, 50b) are communicably connected to the delivery management server 30 via the network NW. The deliverer terminals 50 are also communicably connected to a mobile printer 55. The deliverer terminal 50 is used by a person in charge of parcel delivery. For example, it is carried by a collection driver, a delivery driver, etc. The deliverer terminal 50 has a camera and a function to read machine-readable codes attached to waybills, a display function to display various data on a display screen, etc. The display screen may be a liquid crystal display panel provided on the deliverer terminal 50. The deliverer terminal 50 may be, for example, a smartphone, a tablet, a mobile phone, a PC, or the like. The deliverer terminal 50 outputs the print data to the mobile printer 55, thereby causing the mobile printer 55 to print the print data. The print data may be, for example, destination information or part of the destination information.

[0016] The deliverer terminal 50a is used, for example, by a person in charge of collection, and the deliverer terminal 50b is used by a person in charge of delivery.

[0017] The mobile printers 55 (55a, 55b) are printing devices that are communicably connected to the deliverer terminal 50 and print print data sent from the deliverer terminal 50 onto a print medium. The mobile printer 55 may be a device separate from the deliverer terminal 50, but the mobile printer 55 may also be provided integrally with the deliverer terminal 50.

[0018] The network NW is a communication network including at least a part of, for example, the Internet, a wide area network (WAN), a local area network (LAN), a provider device, a wireless base station, a dedicated line, etc. The network NW may be wired or wireless, or may be a combination of wired and wireless.

[0019] FIG. 2 is a diagram showing an example of the appearance of the invoice L. As shown in FIG. On one main surface of the invoice L, various data can be printed. A two-dimensional barcode La, invoice identification information Lb, one-dimensional barcode Lc, and one-dimensional barcode Ld are printed on the invoice L, and a portion of the invoice is set aside as a reserved area Le. The two-dimensional barcode La is a two-dimensional barcode that represents the invoice identification information. In addition, in the case of corporate use, corporate information may be written following the invoice identification information. In this case, the two-dimensional barcode may include the invoice identification information and the corporate information. The invoice identification information Lb represents the invoice identification information using a character string and is the same as the invoice identification information represented by the two-dimensional barcode La. The one-dimensional barcode Lc and one-dimensional barcode Ld can be used for various management purposes.

[0020] For example, the one-dimensional barcode Lc may be a machine-readable code including invoice identification information. In this case, even if the POS terminal 20 does not have a scanner capable of reading the two-dimensional barcode La, if the POS terminal 20 has a scanner capable of reading the one-dimensional barcode Lc, it can read the invoice identification information by reading the one-dimensional barcode Lc. Furthermore, the one-dimensional barcode Lc may be a JAN (Japanese Article Number) code. In this case, the one-dimensional barcode Lc and the two-dimensional barcode La may be stored in association with each other in the storage unit 302 of the delivery management server 30, so that the invoice identification information based on the two-dimensional barcode La can be identified if the one-dimensional barcode Lc can be read by a scanner. The reserved area Le is an area that can be used as needed to write necessary information by hand or to attach labels, slips, etc. when delivering a package. The package may be delivered without anything written in this reserved area Le, or without a label or slip attached.

[0021] 3 is a diagram showing an example of the appearance of the entry form OP, which is a medium separate from the shipping label. One main surface of the form OP is provided with fields where destination information and delivery requester information can be entered. These fields can be filled in with a writing implement such as a ballpoint pen. After the necessary information has been entered, the form OP can be optically read using a camera or the like, and an OCR (Optical Character Reader) process can be performed to recognize the text portion of the image data based on the read result and convert it into character data. For example, part of the entry area of the form OP is set aside as an area for entering information that can identify the destination, and this area is assigned as a destination entry field D for entering the destination's address, name, telephone number, etc. In addition to the entry area of the form OP, an area is provided for entering information that can identify the delivery requester, and this area is allocated as a delivery requester entry field R for entering the delivery requester's address, name, telephone number, etc. The form OP may also have other areas for entering information such as the contents of the item to be sent and the date and time specified.

[0022] The destination entry field D and delivery requester entry field R each have multiple character boxes for writing each character of the string to be entered. By having the user enter one character per character box, it is possible to reduce misrecognition of characters during OCR processing. Such an entry form OP can be filled out by the user who has requested delivery when requesting delivery of a package. Furthermore, such forms OP are sometimes called OCR forms because they are the media that undergo OCR processing.

[0023] FIG. 4 is a schematic functional block diagram showing the functions of the delivery management server 30. The delivery management server 30 includes a communication unit 301, a memory unit 302, a first acquisition unit 303, a second acquisition unit 304, a first processing unit 305, a second processing unit 306, a transmission unit 307, a control unit 308, and an OCR processing unit 309. The communication unit 301 communicates with various external devices via the network NW. The storage unit 302 stores various data such as delivery data. The memory unit 302 is configured by a storage medium, such as a hard disk drive (HDD), flash memory, electrically erasable programmable read-only memory (EEPROM), random access read / write memory (RAM), read-only memory (ROM), or any combination of these storage media. The storage unit 302 may be, for example, a nonvolatile memory.

[0024] The first acquisition unit 303 acquires the waybill identification information of the waybill attached to the package to be delivered. For example, the first acquisition unit 303 may acquire the waybill identification information sent from the user terminal of the user who made the delivery request, when the waybill identification information on the waybill that is printed on the waybill and placed at the base is read by the user terminal of the user who made the delivery request. Furthermore, the first acquisition unit 303 may acquire the waybill identification information of the waybill L from the deliverer terminal 50a based on the image of the waybill L being captured by the deliverer terminal 50a.

[0025] The second acquisition unit 304 acquires destination information that can identify the destination. For example, the second acquisition unit 304 may acquire, from the user terminal, destination information that can identify a destination based on an operational input by the user. The second acquisition unit 304 may acquire destination information based on the recognition result of recognizing a character string representing the destination information from an image of a fill-in form attached to the package, on which destination information that can identify the destination is filled in. The second acquisition unit 304 can obtain destination information from at least one of the invoice information generated by the OCR processing described below from the captured image of the form, and the destination information entered in response to the user's input.

[0026] The first processing unit 305 stores the acquired waybill identification information and the acquired destination information in the storage unit 302. For example, the first processing unit 305 stores the waybill identification information acquired by the first acquisition unit 303 and the destination information acquired by the second acquisition unit 304 in the storage unit 302. With regard to the destination information to be stored together with the waybill identification information, the destination information acquired by the second acquisition unit 304 may be either waybill information generated from a captured image of a form or destination information input in response to a user's operation input.

[0027] In response to the waybill identification information of the waybill attached to the package to be delivered being read by the delivery person's delivery terminal, the second processing unit 306 stores acceptance information indicating that the package has been accepted in accordance with the waybill identification information sent from the delivery person's terminal in association with the destination information in the memory unit 302.

[0028] When the waybill identification information of the waybill attached to the package to be delivered is read by the delivery person's terminal 50 or the user terminal 10 of the user to whom the package is to be delivered, the sending unit 307 sends the destination information corresponding to the read waybill identification information to the terminal that read the waybill identification information (the delivery person's terminal 50 or the user terminal 10).

[0029] The control unit 308 controls each unit of the delivery management server 30. The control unit 308 also writes and reads each piece of data stored in the storage unit 302 according to the delivery status.

[0030] When a captured image of the form OP is transmitted from a terminal device (either the deliverer terminal 50a or the user terminal 10a) and received by the communication unit 301, the OCR processing unit 309 performs OCR processing on the received captured image. By performing OCR processing, the OCR processing unit 309 recognizes a character string representing destination information from an image area of the captured image that corresponds to the destination entry field D of the form OP, and generates destination information based on the recognition result. Furthermore, when the captured image is received by the communication unit 301, the OCR processing unit 309 recognizes character strings representing delivery requester information from an image area of the received captured image corresponding to the delivery requester entry field R on the form OP, and generates delivery requester information based on the recognition results. Furthermore, if character strings representing information such as the contents of the item and the specified date and time are written on the form OP, the OCR processing unit 309 may recognize these character strings representing information such as the contents of the item and the specified date and time, and generate information based on the recognition results.

[0031] FIG. 5 is a schematic functional block diagram showing the functions of the deliverer terminal 50a. The deliverer terminal 50 a includes a communication unit 501 , a storage unit 502 , an imaging unit 503 , an OCR processing unit 504 , a control unit 505 , an input unit 506 , an output unit 507 , and a display unit 508 . A communication unit 501 communicates with various external devices via a network NW. The storage unit 502 stores various types of data. The storage unit 502 is configured by a storage medium such as a HDD, a flash memory, an EEPROM, a RAM, a ROM, or any combination of these storage media. For example, a non-volatile memory can be used for the storage unit 502. The imaging unit 503 captures an image of the outside of the deliverer terminal 50a and generates a captured image according to the imaging result. For example, the imaging unit 503 can capture an image of the waybill L and also capture an image of the entry form OP.

[0032] The OCR processing unit 504 generates destination information by performing OCR processing on the image area corresponding to the destination entry field D based on the captured image of the form OP captured by the imaging unit 503. The OCR processing unit 504 also generates delivery requester information by performing OCR processing on the image area corresponding to the delivery requester entry field R based on the captured image of the form OP captured by the imaging unit 503. The OCR processing unit 504 may have the same function as the OCR processing unit 309 described above. The control unit 505 controls each unit of the deliverer terminal 50a. The input unit 506 receives operational input from an operator (for example, a driver who is a delivery person) who operates the deliverer terminal 50a. The input unit 506 may be, for example, a touch panel.

[0033] The output unit 507 outputs various data in response to instructions from the control unit 505 . The display unit 508 displays various data on a display screen based on instructions from the control unit 505 or the output unit 507. The display unit 508 may be, for example, a liquid crystal display panel. The input unit 506 and the display unit 508 may be an integrated touch panel. Here, the functions of the deliverer terminal 50a have been described, but a configuration similar to that of the deliverer terminal 50a may be installed in the deliverer terminal 50b.

[0034] FIG. 6 is a diagram showing an example of delivery data stored in storage unit 302. As shown in FIG. The delivery data includes waybill identification information, delivery requester information, delivery destination information, package information, status, and a one-dimensional barcode. The invoice identification information is information that individually identifies an invoice. The delivery requester information is information relating to the delivery requester, and includes, for example, the address, name, telephone number, etc. of the user who has requested delivery. The destination information is information relating to the source of the destination, and includes, for example, the address, name, and telephone number of the destination user. The package information is information relating to the package, and includes, for example, the size of the package, whether it is refrigerated or frozen, delivery charges, and the like. The status is information that indicates the delivery status of the package, and includes, for example, an acceptance flag, a delivery flag, a delivery completion flag, an absence flag, etc. The acceptance flag is information that indicates whether the package has been accepted by the collection officer. For example, an acceptance flag of "0" indicates that the package has not been accepted, and an acceptance flag of "1" indicates that the package has been accepted.

[0035] The one-dimensional barcode is data individually assigned to the waybill L, and represents the one-dimensional barcode Lc attached to the waybill L. In this case, when the one-dimensional barcode Lc is read by the POS terminal 20, the control unit 308 of the delivery management server 30 can identify the one-dimensional barcode stored in the memory unit 302 that corresponds to the one-dimensional barcode Lc acquired from the POS terminal 20, and identify the waybill identification information that corresponds to the identified one-dimensional barcode.

[0036] The delivery flag is information that indicates whether the package is currently being delivered. For example, a delivery flag of "0" indicates that the package has not yet been delivered (before the package is accepted, after delivery has been completed, etc.), and a delivery flag of "1" indicates that the package is currently being delivered (between acceptance and delivery to the destination user). The delivery completion flag is information indicating whether the package has been received by the destination user. For example, a delivery completion flag of "0" indicates that the delivery has not been completed (for example, the state between the time the package is left at the collection point and the time delivery to the destination user is completed), and a delivery completion flag of "1" indicates that the delivery of the package to the destination user has been completed. The absence flag is information that indicates whether the delivery driver visited the destination address but the user was not present and so the delivery driver has returned the package. For example, an absence flag of "0" indicates that the delivery driver has not yet visited the destination address, and an absence flag of "1" indicates that the delivery driver visited the destination address but the user was not present and so the delivery driver has returned the package.

[0037] The above-mentioned communication unit 301, first acquisition unit 303, second acquisition unit 304, first processing unit 305, second processing unit 306, transmission unit 307, and control unit 308 may be configured, for example, by a processing unit such as a CPU (Central Processing Unit) or a dedicated electronic circuit.

[0038] Next, the operation of the above-mentioned delivery system S will be explained using Figures 7 to 13. Figure 7 is a diagram explaining the operation of the delivery system S, Figure 8 is a conceptual diagram explaining the flow of the registration process, Figure 9 is a diagram explaining the operation of the delivery system S, Figure 10 is a conceptual diagram explaining the flow of receiving a package, Figure 11 is a diagram explaining the operation of the delivery system S, and Figure 12 is a diagram explaining the operation of the delivery system S.

[0039] The delivery management server 30 assigns an available waybill number range (FIG. 9; step S301). The waybill number range is data representing available waybill identification information that can be used as waybill identification information to be attached to a waybill. For example, the waybill identification information can be represented by a character string, and if the character string is represented by a number, the waybill number range represents a range of available numbers. For example, the waybill number range may specify a range of numbers, such as from 1 to n (sequential numbers), or may specify available character strings individually (it does not have to be sequential numbers). Furthermore, the waybill identification information may be a string of multiple numbers, a string of letters or symbols, or a string combining at least two of numbers, letters, and symbols. The waybill number may be made available for reuse after it has been issued, printed on the waybill, attached to the package, delivered, or after a certain period of time has passed, etc. Numbers that can be used in this way are assigned as waybill number bands. The delivery management server 30 transmits number range data representing the number range to be used for the invoice to the invoice print server 40 (FIG. 7; step S101, FIG. 9; step S305).

[0040] When the invoice printing server 40 receives the number band data from the delivery management server 30, it causes the invoice printing device 41 to print an invoice in accordance with the invoice use number band indicated by the received number band data (FIG. 7; step S105, FIG. 9; step S315). For example, the invoice printing server 40 generates a two-dimensional barcode representing the invoice identification information included in the invoice use number band (FIG. 9; step S310) and prints one two-dimensional barcode on each different invoice. Here, the two-dimensional barcode representing the invoice identification information may be printed on the invoice, or the character string representing the invoice identification information itself may be printed on the invoice. Alternatively, both the two-dimensional barcode and the character string representing the invoice identification information may be printed. In this embodiment, the invoice identification information is printed as a two-dimensional barcode, but a one-dimensional barcode may also be used.

[0041] The invoice printer 41 prints one invoice identification information on one invoice in accordance with instructions from the invoice print server 40 (FIG. 9; step S320). Here, if the invoice use number band contains multiple invoice identification information, each invoice identification information is printed on a different invoice.

[0042] Once the shipping label is printed, it is sent to a base and placed there. For example, the printed shipping label is handed over to a convenience store and placed there (FIG. 7; step S110). The shipping label placed at the convenience store can be distributed to the user who requested delivery.

[0043] When a user who has requested delivery wishes to have a package delivered, the user can register in advance with the delivery management server 30. By registering as a user, the address, name, telephone number, etc. of the user who has requested delivery can be specified as the address, name, telephone number, etc. of the user who has requested delivery without having to directly input the address, name, telephone number, etc. of the user who has requested delivery from the user terminal 10a, etc., each time delivery is made. When a delivery requesting user registers, the user uses the user terminal 10a to access a web page for user registration made public by the delivery management server 30 and inputs various necessary information on the user registration screen. The necessary information includes, for example, the address, name, and telephone number of the delivery requesting user. The user terminal 10a performs user registration processing based on the operation input from the user (FIG. 9; step S325). The user terminal 10a transmits the various data input by the user to the delivery management server 30 and also transmits a user registration request (FIG. 9; step S330).

[0044] The delivery management server 30 assigns user identification information that individually identifies the user based on the user registration request sent from the user terminal 10a, and stores the user identification information in association with the various data sent from the user terminal 10a in the storage unit 302 (FIG. 9; step S335). In this way, user processing in the delivery management server 30 is executed.

[0045] Furthermore, when a user who has requested delivery wishes to have a package delivered, the user brings the package to a base such as a convenience store, and receives a waybill at the base (FIG. 7; step S115). When the delivery requesting user receives the waybill, the delivery requesting user captures the waybill identification information printed on the waybill using the camera of the user terminal 10a to read it (FIG. 8; step 201, FIG. 9; S340), and then inputs the recipient's address, name, telephone number, etc. as delivery destination information using the input device of the user terminal 10a, and transmits the waybill identification information and the recipient's address to the delivery management server (FIG. 7; step S120, FIG. 8; step S205, FIG. 9; step S345). This completes the registration procedure for various information related to the waybill identification information. Here, if the delivery requesting user has previously registered as a user, they can log in through the delivery service's web service or application program and set the user-registered data as delivery requesting user information without manually entering the delivery requesting user's address, name, telephone number, etc. If the delivery requesting user has not previously registered as a user, they may input their own address, name, telephone number, etc. as delivery requesting user information through the user terminal 10a. In this case, the delivery management server 30 may assign a guest account to a user who has not yet been registered, and manage the user who has requested delivery using the guest account for a certain period of time.

[0046] Here, the user terminal 10a may read the waybill identification information with a camera, transmit the waybill identification information to the delivery management server 30, and then have the user who made the delivery request input destination information based on an operational input from the user, and transmit the destination information to the delivery management server 30. Alternatively, the user terminal 10a may have the user input destination information and transmit the destination information to the delivery management server 30, and then have the user read the waybill identification information of the waybill with a camera, and transmit the waybill identification information to the delivery management server 30. Furthermore, the user terminal 10a may read the waybill identification information with a camera, temporarily store the read waybill identification information in a storage area within the user terminal 10a, and after the user inputs the destination information, transmit the waybill identification information together with the destination information to the delivery management server 30. Furthermore, the user terminal 10a may read the waybill identification information with a camera, temporarily store the input destination information in a storage area within the user terminal 10a, and after the user inputs the destination information, transmit the waybill identification information together with the destination information to the delivery management server 30. Furthermore, the waybill identification information can be extracted from the two-dimensional barcode by reading it with the user terminal 10a, but if the waybill identification information is printed on the waybill as a character string rather than a two-dimensional barcode, the character string can be captured by the camera of the user terminal 10a and the captured image can be subjected to OCR (Optical Character Reader) processing to extract the character string. Also, if a character string representing the waybill identification information is printed on the waybill, the user who has requested delivery can register it by manually entering the character string directly into the user terminal 10a.

[0047] The user who has requested delivery sends the waybill identification information and destination information to the delivery management server 30, then attaches the waybill with the waybill identification information attached to the package to be delivered (Figure 8; step S210) and hands it over to the person in charge at the base station (Figure 7; step S125). Here, when handing over the package, the user requesting delivery may or may not handwrite the address, name, telephone number, etc. of the user requesting delivery and the address, name, telephone number, etc. of the user at the destination in the spare area Le of the waybill, as necessary. Here, since the destination information and the information of the user requesting delivery are already registered in the waybill identification information, it is not necessary to write or print information about the destination and the user requesting delivery as character strings directly on the waybill.

[0048] When the delivery management server 30 receives the waybill identification information, delivery requester information, and delivery destination information from the user terminal 10a, it stores them in the storage unit 302. The delivery management server 30 also uses the address included in the received delivery requester information and the address included in the delivery destination information as provisional data, calculates a delivery route based on this provisional data (FIG. 9; step S350), and stores the delivery route in the storage unit 302 in association with the waybill identification information. The delivery management server 30 may also transmit a provisional delivery schedule corresponding to the delivery route based on the provisional data to the user terminal 10a, and display it on the user terminal 10a.

[0049] When a package is handed over from a user who has requested delivery, a person in charge (e.g., a store clerk) at the base (e.g., a convenience store) reads the shipping label identification information printed on the shipping label attached to the package using the scanner of the POS terminal 20 (FIG. 8; step S215, FIG. 11; step S501). If the POS terminal 20 is capable of reading two-dimensional barcodes such as the two-dimensional barcode La on the invoice L, it can read the two-dimensional barcode representing the two-dimensional barcode La. On the other hand, if the POS terminal 20 is not capable of reading two-dimensional barcodes but is capable of reading one-dimensional barcodes, the one-dimensional barcode Lc on the invoice L may be read by the POS terminal 20 to identify the invoice identification information. Here, when the waybill identification information is successfully read by the scanner of the POS terminal 20 (FIG. 11; step S505), the POS terminal 20 transmits the read waybill identification information to the delivery management server 30. The control unit 308 of the delivery management server 30 refers to the storage unit 302 and determines whether or not destination information for the waybill identification information received from the POS terminal 20 is stored in the storage unit 302 (FIG. 11; step S503). If destination information is stored for the waybill identification information (FIG. 11; step S503-YES), the delivery management server 30 registers that the package to be delivered has been stored (handed over) at the base where the POS terminal 20 is located. Then, when the scanner successfully reads the waybill identification information, the person in charge at the base stores the package in a storage location (FIG. 7; step S130).

[0050] In response to the registration of the storage of a package to be delivered, the delivery management server 30 may send a receipt notification to the user terminal 10a, which includes information such as which package was received and the date and time of receipt. On the other hand, in step 503, if the destination information corresponding to the waybill identification information is not stored in the storage unit 302 (FIG. 11; step S503-NO), the control unit 308 of the delivery management server 30 notifies the POS terminal 20 of an alert indicating that the destination information has not been registered. When the POS terminal 20 receives this alert notification, a screen indicating the content of the alert is displayed on the display screen of the POS terminal 20. The content of the alert may be, for example, a message such as "The address and name of the recipient, and the information of the person requesting delivery are missing. Please provide a form for them to fill out, or register the destination information from their smartphone." When the person in charge at the base sees this message, they will hand the form to the customer who requested the shipment and ask them to fill in the destination information, etc., or instruct them to enter the destination information, etc., on their smartphone.

[0051] When the customer requesting shipment fills in the destination information and the like on the entry form OP, the customer receives the entry form OP from the person in charge at the base, fills in the necessary information (destination information (address, name, telephone number, etc. of the recipient) and delivery requester information (address, name, telephone number, etc. of the delivery requester) on the entry form, and hands it over to the person in charge at the base. Here, instead of filling in the entry form, the customer may take an image of the waybill identification information on the waybill and input the destination information and delivery requester information, as in steps S120, S205, S345, etc. described above. Once the customer has completed registering this information, the customer may show the person in charge at the base a registration completion screen on user terminal 10a to confirm that registration is complete. Here, the customer may own a user terminal such as a smartphone, but may not own one, or may not be accustomed to operating a user terminal to input characters, etc. Such customers can use this delivery system S by filling out the necessary information on a form.

[0052] The customer receives the form from the person in charge at the base, writes the delivery destination information and delivery requester information on the form using a writing implement, and hands it over to the person in charge at the base (step S207 in FIG. 8). The person in charge at the base attaches the received entry form OP to the spare area of the shipping label or to a position on the outer periphery of the package around the shipping label (Step S210 in FIG. 8). The entry form OP may be attached by the customer who has requested delivery, rather than by the person in charge at the base. Once the form has been attached, the person in charge at the base will store the package in a storage location (FIG. 7; step S130).

[0053] Furthermore, the delivery management server 30 receives waybill identification information from the POS terminal 20, and if destination information is stored for the waybill identification information, it determines the delivery route stored in the storage unit 302 that corresponds to the waybill identification information (FIG. 11; step S510). Once the delivery route is determined, the delivery management server 30 transmits instructions for dispatching a vehicle to the center, loading the parcel, and collection of the parcel. For example, the delivery management server 30 transmits a collection instruction to the deliverer terminal 50 in charge of collecting the parcel from the collection point (FIG. 11; step S525). Upon receiving this instruction, the deliverer terminal 50 displays the instruction on the display screen. This allows the driver in charge of collection to recognize that collection will be performed. Furthermore, the delivery management server 30 may extract destination information for packages that fall within the delivery area of the delivery person based on the delivery route and transmit the destination list to the delivery person's terminal 50. This allows the delivery person's terminal 50 to determine the destinations based on the destination list. By transmitting the destination list to the delivery person's terminal 50, the delivery person can determine which package to deliver. Furthermore, the delivery management server 30 may transmit the destination list to the delivery person's terminal 50, including the destination information, delivery requester information, and waybill identification information. This allows various information about the package to be obtained without the delivery person's terminal 50 reading the waybill identification information attached to the waybill and querying the delivery management server 30. For example, even if the delivery management server 30 and the delivery person's terminal 50 cannot communicate with each other, various information about the package can be determined based on the delivery destination list in the delivery person's terminal 50. Here, the waybill identification information is printed on the waybill as text, separate from the two-dimensional barcode, so that the correspondence between the package and the data contained in the delivery destination list can be determined based on the waybill identification information.

[0054] The delivery management server 30 also sends a notification to the user terminal 10b of the destination user indicating that the package has been collected (FIG. 11; step S515). This notification may be sent using SMS (Short Message Service) to the telephone number included in the destination information. This message may also include the delivery route and the scheduled delivery date based on the collection date and time. The user terminal 10b receives this notification and displays a message indicating that the package has been shipped and the expected delivery date on the display screen (FIG. 11; step S520).

[0055] Among the delivery companies, the driver in charge of collection carries the deliverer terminal 50a and visits each base to collect the package (FIG. 7; step S135). Here, the driver also visits the base where the package was stored in FIG. 7; step S130, and picks up the package stored at the base. When the driver in charge of collection receives the package, he checks the waybill L attached to the package to see if only the waybill L is attached, or if the waybill L and a fill-in form are attached. If the fill-in form is not attached and the waybill L is attached, the driver in charge of collection reads the waybill identification information on the waybill L attached to the received package using the deliverer terminal 50a (FIG. 11; step S530) and presses the "collection button" indicating that the package has been collected. When the deliverer terminal 50a reads the waybill identification information and the collection button is pressed, it transmits the waybill identification information and data indicating "collection" to the delivery management server 30.

[0056] On the other hand, if the package is accompanied by a waybill L and an entry form, the pickup driver uses the deliverer terminal 50a to capture and read the waybill identification information on the waybill L, and also capture and read the entry form. Here, the reading order may be such that the entry form is read first, and then the waybill identification information on the waybill L is read. Alternatively, the entry form and the waybill L may both be captured at the same time by capturing an image so that both fit within the image capture area. By analyzing the captured image of the entry form and the waybill L to obtain image features, it is possible to identify image areas corresponding to the waybill identification information, destination information, and delivery requester information, and extract each piece of information.

[0057] When the delivery person terminal 50a reads the waybill identification information of the waybill L and the entry form, it performs OCR processing on the image area of the image of the entry form to extract a character string from the character image written in the destination entry field D from the image area and generate destination information including the extracted character string (FIG. 11, step S532).The delivery person terminal 50a also extracts a character string from the character image written in the delivery requester entry field R from the image area and generate sender information including the extracted character string. Then, the deliverer terminal 50a transmits the generated destination information and delivery requester information to the delivery management server 30 together with waybill identification information corresponding to the two-dimensional code. When the delivery management server 30 receives the destination information, delivery request source information, and waybill identification information corresponding to the two-dimensional code from the deliverer terminal 50a, it identifies the waybill identification information in the memory unit 302 that matches the received waybill identification information, and stores the received destination information and delivery request source information in association with the identified waybill identification information.

[0058] Here, we have explained the case where the deliverer terminal 50 performs the process of generating destination information and delivery requester information from an image of the form OP by performing OCR processing. However, it is also possible to send an image of the form from the deliverer terminal 50 to the delivery management server 30, and have the OCR processing unit 309 of the delivery management server 30 perform OCR processing on the image of the form, extract the destination information and delivery requester information, and store them in association with the waybill identification information. When the deliverer terminal 50a captures the waybill L and the entry form OP to acquire destination information and delivery requester information (for example, when step S503-NO in Figure 11 and processing of step S532 is executed), the delivery management server 30 determines the delivery route corresponding to the waybill identification information based on the acquired destination information (step S510 in Figure 11).

[0059] When the delivery management server 30 receives data indicating collection and the waybill identification information from the deliverer terminal 50a, it refers to the storage unit 302 and verifies whether the data matches the waybill identification information sent from the POS terminal 20 and registered (FIG. 11; step S530). If the verification shows that the waybill identification information matches, the delivery management server 30 rewrites the status corresponding to the waybill identification information to "Collected" and rewrites the acceptance flag (acceptance information) included in the status information from "0" to "1." By rewriting the acceptance flag to "1," it is possible to know from the status that the package left at the collection point has been handed over to the delivery company. Here, when a package is delivered using a handwritten delivery slip, if the address, name, and telephone number of the recipient, the address, name, and telephone number of the delivery requester, the name of the package, etc. are written by hand, it is possible to know that the delivery slip has been started to be used, but since the waybill in the above-mentioned embodiment is used with a two-dimensional barcode or the like printed on it, the recipient information and the delivery requester information are not necessarily written on the waybill. Therefore, it is difficult to know from the face of the waybill alone whether the waybill has been started to be used, for example, whether it has been accepted by the delivery company. However, by reading the waybill identification information on the waybill with the user terminal 10 or the deliverer terminal 50, it is possible to access the delivery management server 30 and refer to the acceptance flag to know whether the waybill has been started to be used and whether the package has been accepted by the delivery company.

[0060] Here, the driver in charge of collection can input an operation to the deliverer terminal 50a to print a portion of the destination information. When the delivery label of the package for which the portion of the destination information is to be printed is read and an operation to print a portion of the delivery label information is input, the deliverer terminal 50a causes the mobile printer 55a connected to the deliverer terminal 50a to print the read portion of the delivery label information (FIG. 7; step S145, FIG. 11; S535). The mobile printer 55a prints a portion of the destination information on a print medium based on the instruction from the deliverer terminal 50a. The part of the destination information may be information including at least a part of the address, name, and telephone number of the destination. In addition, the deliverer terminal 50a may cause the mobile printer 55a to print a character string representing the part of the destination information, or may generate a two-dimensional barcode corresponding to the part of the destination information and cause the mobile printer 55a to print the generated two-dimensional barcode.

[0061] The print medium may be a label that can be attached as a sticker. If part of the destination information is printed on such a label, the driver in charge of collection may attach the label with the part of the destination information printed on it to the spare area Le of the shipping label. If a character string representing part of the destination information is printed on a label and attached to the shipping label, the delivery company or the user at the destination can see the address, name, and telephone number of the user who requested delivery, and the address, name, and telephone number of the user at the destination by looking at the shipping label. Also, if part of the destination information is a two-dimensional barcode representing the name of the user who requested delivery and part of the address of the destination (for example, an address in a smaller division than a city, ward, town, or village) printed on a label and attached to the shipping label, the two-dimensional barcode on the label can be read by the deliverer terminal 50 or the user terminal 10b of the destination and interpreted, thereby extracting part of the address and the name from the two-dimensional barcode offline without having to send an online inquiry to the delivery management server 30. This allows the delivery person to grasp the destination and continue delivery operations even if, for example, an environment occurs in which the deliverer terminal 50 cannot communicate with the delivery management server 30 when reading the two-dimensional barcode on the label (out of range of the network NW, communication error, etc.). Here, the entire address may be included in the two-dimensional barcode, but it does not necessarily have to include the entire address as long as it is an address within the delivery area. For example, the prefecture element may be omitted. Although the above description is given of a case where the upper part of the destination information is printed on the label, it does not necessarily have to be printed.

[0062] Furthermore, the driver in charge of collection can read the waybill identification information attached to the waybill using the deliverer terminal 50a, inquire about the destination information stored in association with that waybill identification information to the delivery management server 30, and have the results displayed on the display screen of the deliverer terminal 50a. This allows the driver to check the address, name, telephone number, etc. of the destination information on the display screen even if part of the destination information has not been printed using the mobile printer 55a. The driver in charge of collection loads the packages into the vehicle and delivers them from the base such as a convenience store to a relay point.

[0063] At the relay point, the driver in charge of relaying can use his / her driver terminal to read the waybill identification information on the waybill of the package to be relayed, thereby confirming the destination of each package (FIG. 7; step S155). The driver in charge of relaying sorts the packages to the relay destination according to the destination address, and delivers the packages to the delivery base (FIG. 7; step S160). Delivery bases are bases set up in each region, and from the delivery bases, delivery drivers deliver packages to their respective destinations.

[0064] The destination user can check the scheduled delivery date on the user terminal 10b and, if necessary, change the scheduled delivery date by inputting an operation to change the scheduled delivery date. When the user terminal 10b receives an operation to change the scheduled delivery date (FIG. 11; step S540), it transmits the changed scheduled delivery date to the delivery management server 30 based on the operation content (FIG. 11; step S545). When the delivery management server 30 receives a request to change the scheduled delivery date, it registers the change to the scheduled delivery date by writing it in the storage unit 302 (FIG. 11; step S550). This notifies the delivery person's terminal 50b of the change to the scheduled delivery date. The delivery person then delivers the package based on the changed scheduled delivery date.

[0065] At the delivery base, the delivery driver receives the parcel to be delivered. Then, using the deliverer terminal 50b owned by the delivery driver, the driver reads the waybill identification information on the waybill of the parcel to be delivered. After reading the waybill identification information attached to the waybill, the deliverer terminal 50b transmits the waybill identification information to the delivery management server 30, receives the delivery destination information transmitted from the delivery management server 30, and displays it on the display screen (FIG. 7; step S170). This allows the delivery driver to visually confirm the delivery destination information displayed on the display screen using the deliverer terminal 50a, and confirm the address, name, telephone number, etc. of the delivery destination. The delivery driver confirms the address, name, etc. of the delivery destination, and delivers the parcel to the delivery destination (FIG. 7; step S175). The delivery driver visits the address of the destination user and hands over the package to the destination user (FIG. 10; step S401). At that time, the delivery driver reads the waybill identification information of the waybill attached to the package to be handed over using the deliverer terminal 50b and inputs the instruction "Delivery complete" (FIG. 12; step S601).

[0066] When the delivery management server 30 receives the waybill identification information and the instruction "Delivery Completed" from the deliverer terminal 50b, it rewrites the status corresponding to the received waybill identification information stored in the storage unit 302 to "Delivery Completed" (FIG. 12; step S610). Then, when certain conditions are met, such as the passage of a predetermined period of time (e.g., several months), the delivery management server 30 performs processing such as registering the received waybill identification information in a waybill usage number range. This makes it possible to reuse waybill identification information for which delivery management has been completed, even if there is a finite number of character strings that can be used as waybill identification information.

[0067] The delivery management server 30 calculates the CO2 emissions for the invoice identification information that has been rewritten to "delivery completed" based on the delivery route, etc., and stores the calculated CO2 emissions in association with the invoice identification information.

[0068] Meanwhile, when the destination user receives the package, he / she reads the waybill identification information printed on the waybill attached to the package using his / her own user terminal 10b (Figure 10; step S405), and sends the read waybill identification information and an inquiry request to the delivery management server 30. When the delivery management server 30 receives the waybill identification information and an inquiry request from the user terminal 10b, it reads out the delivery destination information and delivery request source information corresponding to the waybill identification information from the memory unit 302 and sends them to the user terminal 10b that made the inquiry. When user terminal 10b receives the delivery destination information and delivery requester information from delivery management server 30, it displays the delivery destination information and delivery requester information on the display screen. This allows the user (recipient) at the delivery destination to confirm the sender's address, name, telephone number, etc., and also the recipient's address, name, telephone number, etc. (FIG. 7; step S180). The recipient user confirms the delivery requester and delivery destination, and if there are no problems, touches the "Receive" button on the display screen. Based on the notification of "received," the delivery management server 30 updates the status in the storage unit 302 to "received," and sends a notification of "delivery completed" to the user terminal 10a that made the delivery request (FIG. 10; step S410, FIG. 12; step S620). This notification may be sent by sending an email to the email address of the user terminal 10a, or by using SMS.

[0069] Here, if the user at the destination does not input the operation for "receiving" (for example, when the package is delivered without meeting the recipient, such as when the recipient does not have the user terminal 10b at hand, or when it is difficult for the recipient to input the operation for "receiving"), the delivery driver may read the waybill identification information printed on the waybill attached to the package using his / her own deliverer terminal 50b, and input the instruction for "delivery complete" from the deliverer terminal 50b.

[0070] The user terminal 10a also receives the notification of "delivery completed" sent from the delivery management server 30 and displays it on the display screen (FIG. 10; step S410, FIG. 12; step S625). This notification may be sent by sending an e-mail to the e-mail address of the user terminal 10a, or by using SMS. Furthermore, for example, when a delivery completion notification is sent by email, the body of the email may include a URL for a web page that can display the date and time when the delivery of the package was completed, and when the user touches the URL, the web page regarding the delivery completion may be displayed on the display screen of the user terminal 10a. This allows the user who requested the delivery to know the details regarding the delivery completion. Furthermore, when the user terminal 10a accesses the URL described in the delivery completion notification email (FIG. 12; step S630), the delivery management server 30 transmits data for displaying a web page regarding the delivery completion to the user terminal 10a and causes the user terminal 10a to display it. Furthermore, the delivery management server 30 may store data indicating that the delivery completion notification has been received and confirmed by the user terminal 10a as status information corresponding to the waybill identification information (FIG. 12; step S635).

[0071] Next, FIG. 13 is a flowchart illustrating the operation of the delivery management server 30. When the waybill placed at the collection point is received by the user who made the delivery request, and the user terminal 10a reads the waybill identification information on the waybill in response to the user's operation, the user terminal 10a transmits the read waybill identification information to the delivery management server 30. The user terminal 10a also transmits the delivery source information and the delivery destination information to the delivery management server 30 in response to the user's operation. Here, the user terminal 10a may transmit the delivery destination identification information, delivery source information, and delivery destination information all at once, or may transmit them one by one. When transmitting them one by one, the order may be arbitrary. In the delivery management server 30, the first acquisition unit 303 acquires the waybill identification information by receiving it, and the second acquisition unit 304 acquires the delivery destination information and the delivery request source information (step S701).

[0072] When the waybill identification information, delivery destination information, and delivery requester information are acquired, the first processing unit 305 stores the acquired waybill identification information, delivery destination information, and delivery requester information in the memory unit 302 in association with each other (step S702). Next, when the package is handed over from the delivery requester to the person in charge at the collection point and the waybill identification information is read by the POS terminal 20, the POS terminal 20 transmits the read waybill identification information to the delivery management server 30. When the control unit 308 of the delivery management server 30 acquires the waybill identification information from the POS terminal 20 (step S703), it registers the fact that the parcel to be delivered has been stored (delivered) by writing the status information associated with the waybill identification information into the memory unit 302. This activates the invoice identification information (step S704).

[0073] Next, when the waybill identification information on the waybill attached to the package to be delivered is read by the delivery person's delivery terminal 50a and sent from the delivery terminal 50a, the second processing unit 306 obtains the waybill identification information by receiving it from the delivery terminal 50a (step S705). Then, after the waybill identification information and destination information are stored in association with each other in step S704, if the second processing unit 306 acquires the waybill identification information from the deliverer terminal, it determines that the package to be delivered has been accepted by the delivery person, and stores the acceptance information in association with the waybill identification information in the storage unit 302 (step S706). Here, the second processing unit 306 may be configured to determine that the package to be delivered has been accepted by the delivery person if it receives the waybill identification information from the deliverer terminal 50a together with data indicating that the package has been collected.

[0074] Next, when the control unit 308 receives an inquiry request together with the waybill identification information from the deliverer terminal 50 or the user terminal 10 (step S707), it reads out the destination information corresponding to the received waybill identification information from the memory unit 302 and sends it to the terminal device that made the request (the deliverer terminal 50 or the user terminal 10) (step S708). This allows the delivery person carrying the deliverer terminal 50 to check the destination information and continue delivery work according to the destination. Alternatively, the user who owns the user terminal 10 can check the destination information. That is, when the user at the destination receives the delivered package, the user can have the waybill identification information read by the user terminal 10 and check whether the destination is for them before opening the package, etc.

[0075] Next, when the control unit 308 receives a "received" notification from the user terminal 10b or a "delivery completed" notification from the deliverer terminal 50 (step S709), it updates the status corresponding to the waybill identification information stored in the storage unit 302 to "received" (step S710).The control unit 308 then notifies the user terminal 10a of the user who requested delivery that delivery has been completed (step S711).

[0076] Here, when the delivery requesting customer hands over the package to the person in charge at the base, and the waybill information is read by the POS terminal 20, waybill identification information is sent to the delivery management server 30. However, when a delivery request for a package is made using the entry form OP, the destination information is not registered at the time the waybill identification information is received from the POS terminal 20. In this case, the control unit 308 of the delivery management server 30 receives the waybill identification information sent from the POS terminal 20 (step S751). Then, the control unit 308 of the delivery management server 30 notifies the POS terminal 20 that the destination information is not registered for the waybill identification information (step S752).

[0077] After that, when the delivery form OP, on which the destination information, delivery requester information, etc. have been entered, and the waybill L are read by the deliverer terminal 50a, the delivery terminal 50a or the delivery management server 30 performs OCR processing on the captured image of the read form OP to obtain the destination information and delivery requester information. The delivery management server 30 associates the destination information and delivery requester information obtained by OCR processing with the waybill identification information and stores them in the storage unit 302 (step S753). Then, the delivery management server 30 executes the above-mentioned processing from step S706.

[0078] According to the embodiment described above, even in situations where information about the destination and the information about the delivery requester, as in a delivery slip, is not necessarily written, packages can be managed using the waybill identification information attached to the package, thereby providing a new delivery system.

[0079] According to the above-described embodiment, even if the waybill does not necessarily include destination information or delivery requester information, by reading the waybill identification information attached to the waybill, information about the destination, information about the delivery requester, and the status of the package can be obtained. This eliminates the need to include information about the destination or delivery requester on the waybill. A new delivery system can be provided. Furthermore, privacy protection can be improved by preventing the destination's address, name, telephone number, and the delivery requester's address, name, telephone number, etc. from being attached to the package in a visible state. Furthermore, there is no need to use a delivery slip consisting of multiple duplicate forms on which the address, name, telephone number, etc. are written. Instead, the waybill identification information attached to the package can be used to access information about the destination, information about the delivery requester, etc., using a terminal device. This allows delivery electronics to be digitized, and a new delivery system can be provided.

[0080] Furthermore, according to the above-described embodiment, even if the destination information is not printed on the waybill or is not written by hand, at least a portion of the waybill information can be printed on a label and affixed to the waybill as needed. Furthermore, when printing such a label, information including at least a portion of the destination information is printed as a machine-readable code. This allows the destination information to be obtained by reading the machine-readable code with the user terminal 10 or the deliverer terminal 50. This allows the destination information to be obtained based on the machine-readable code even in an environment where communication with the delivery management server 30 is not possible.

[0081] Furthermore, according to the above-described embodiment, the waybill identification information attached to the waybill is stored in association with acceptance information (for example, an acceptance flag), so by referring to the acceptance flag, it is possible to know whether the parcel left at the collection point has been handed over to the delivery company (whether the waybill identification information is active or not). Furthermore, it is possible to know whether the waybill identification information attached to the waybill has started to be used for delivery even if there is no handwritten note or the like on the waybill. Furthermore, even if a dedicated device for printing shipping labels is not available, the user can link the delivery destination to the shipping label digitally, and the delivery person can use the shipping label as is to make the delivery.

[0082] In the embodiment described above, the delivery management server 30 may be a physical server or a cloud server provided by a cloud computing service.

[0083] Furthermore, in the above-described embodiment, the case where the OCR processing unit 309 is provided in the delivery management server 30 and the OCR processing unit 504 is provided in the deliverer terminal 50a has been described, but the function for performing OCR processing does not necessarily have to be provided in both the delivery management server 30 and the deliverer terminal 50a, but it is sufficient that it is provided in either the delivery management server 30 or the deliverer terminal 50a and OCR processing is performed. Alternatively, the function of the OCR processing unit may be provided in the user terminal 10, and the user requesting delivery may use the user terminal 10a to capture images of the waybill L and the form OP for the package, and the user terminal 10a may perform OCR processing on the captured image of the form OP to generate delivery requester information and destination information, which may then be transmitted to the delivery management server 30 together with waybill identification information obtained from the waybill L. This allows the delivery management server 30 to store the delivery requester information, destination information, and waybill identification information in the storage unit 302.

[0084] Furthermore, in the above-described embodiment, the case where the image of the entry form OP is captured by the deliverer terminal 50a or the user terminal 10a has been described, but other aspects may also be used. For example, when the deliverer terminal 50a or the user terminal 10a captures an image of the form OP, the captured image may be captured in an unfavorable environment (such as insufficient brightness), making it difficult to analyze the written characters using OCR processing. In such cases, OCR processing may not be performed properly, or even if OCR processing is performed successfully, the character recognition results may include erroneous recognition. In such cases, at a center where packages are collected, a staff member at the center may use the deliverer terminal 50 to capture images of the form OP and the waybill L. If OCR processing is successfully performed on the captured image of the form OP, the results of the OCR processing (shipping destination information, delivery requester information) may be sent to the delivery management server 30 along with the waybill identification information on the waybill L, and the shipping destination information and delivery requester information may be registered. This allows more accurate shipping destination information and delivery requester information to be registered as a result of the OCR processing.

[0085] If the OCR process cannot be performed normally as a result of the image of the entry form OP being captured by the deliverer terminal 50a or the user terminal 10a, or if the entry form OP is collected without being captured for some reason, the package will arrive at the center without the destination information and delivery requester information being associated with the waybill identification information. Furthermore, the package arrives at the center with characters that are incorrectly recognized as a result of OCR processing performed on the deliverer terminal 50a or the user terminal 10a based on the captured image of the entry form OP. Here, the terminal that performed the OCR processing (the deliverer terminal 50a or the user terminal 10a) may store the character recognition rate, which indicates the degree to which the characters were accurately read when the OCR processing was performed, in association with the waybill identification information along with the results of the OCR processing. In this case, the package arrives at the center with the destination information and delivery requester information associated with the waybill identification information, but with a certain degree of possibility that the results of the OCR processing of the contents written on the entry form OP are incorrect.

[0086] The center reads the waybill identification information from the waybill L for each of the collected packages and transmits it to the delivery management server 30. The control unit 308 of the delivery management server 30 references the storage unit 302 based on the waybill identification information read at the center and determines whether the delivery destination information and the delivery requester information are stored in association with each other. If the determination result shows that the delivery destination information and the delivery requester information are not stored in association with the waybill identification information, an error is output along with the waybill identification information that is not associated. Here, data indicating an error indicating that the destination information and delivery requester information are not associated with the waybill identification information, along with the waybill identification information, may be displayed on a display or the like installed at the center. Based on this error display, the center staff member identifies the parcel for which the error occurred and captures an image of the entry form OP using the deliverer terminal 50. This allows the destination information and delivery requester information to be stored in association with the waybill identification information. Alternatively, the center may read the waybill identification information from the waybill L for each consolidated package, and the delivery management server 30 may determine whether the character recognition rate corresponding to this waybill identification information is equal to or greater than a reference value. If the character recognition rate is equal to or greater than the reference value, the registered destination information and delivery requester information are used as is. If the character recognition rate is less than the reference value, an error message is output to the center's display along with information indicating that the character recognition rate is less than the reference value and the waybill identification information for which the character recognition rate is less than the reference value. Based on this error message, the center staff member identifies the package for which the error occurred and captures an image of the entry form OP using the deliverer terminal 50. This allows the destination information and delivery requester information to be stored in association with the waybill identification information.

[0087] In addition, an error label indicating that the OCR process was not performed normally may be attached to the spare area Le of the waybill, and when an error label is detected at the center, a center staff member may register the destination information and delivery requester information on the entry form OP of the package to which the error label is attached.

[0088] Alternatively, the center staff may image the entry form OP using the deliverer terminal 50 and perform OCR processing, or the center staff may visually check the character string written on the entry form OP and, based on the visual check, input the destination information and delivery requester information into the deliverer terminal 50 by operating an input device such as a keyboard, mouse, or touch panel. The deliverer terminal 50 then transmits the input content (destination information and delivery requester information) input from this input device to the delivery management server 30 together with the waybill identification information. The delivery management server 30 may store the destination information and delivery requester information transmitted from the deliverer terminal 50 together with the waybill identification information in the memory unit 302. As a result, if the deliverer terminal 50a or the user terminal 10a is unable to capture an image of the form OP, or if an image can be captured but there is a possibility that the OCR processing results are erroneous, the center can associate accurate information corresponding to the information entered on the form OP (destination information and delivery requester information) with the waybill identification information and store it in the delivery management server 30. As a result, even when using the form OP, a registration operation can be performed to link the information entered on the form OP with the waybill identification information, and it can be registered in the delivery management server 30 as reliable information.

[0089] In this case, the second acquisition unit 304 of the delivery management server 30 may acquire the destination information from any one of the following: destination information generated based on an image of the entry form; destination information entered into a user terminal based on an operational input by a user who is the delivery requester requesting delivery of a package; and destination information entered into a terminal device based on the contents of the entry form based on an operational input by a center staff member. The destination information entered into the terminal device based on the contents of the entry form based on an operational input by a center staff member may be character information obtained by performing OCR processing on an image of the entry form captured by the center staff member using a terminal device, or character information entered by the center staff member visually checking the contents of the entry form and operating an input device (keyboard, mouse, touch panel, etc.) based on the visual checking results. In this case, the first processing unit 305 of the delivery management server 30 may store the destination information and waybill identification information acquired from either one of them by the second acquisition unit 304 in the memory unit 302.

[0090] Furthermore, in the above-described embodiment, the entry form OP may be peeled off from the package after OCR processing has been performed. Here, since the delivery destination information and delivery requester information are stored as data in the delivery management server 30 in relation to the waybill identification information, as long as the waybill identification information on the waybill L attached to the package is known, the delivery destination information and delivery requester information can be determined even if the entry form has been peeled off. In this case, the entry form may be removed by the collection or delivery person who captured the image of the entry form, or it may be removed at a center or the like where packages are collected. Removing the entry form prevents the delivery destination information and delivery requester information from being directly visually identified from the package's exterior. This reduces the risk of personal information and the like being obtained by third parties.

[0091] At least one of the user terminal 10, delivery management server 30, shipping label printing server 40, and deliverer terminal 50 in the above-described embodiment may be realized by a computer. In this case, the functions may be realized by recording a program for implementing the functions on a computer-readable recording medium and loading and executing the program on the recording medium into a computer system. Note that the term "computer system" as used herein includes hardware such as an operating system and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. Furthermore, "computer-readable recording medium" may also include devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs over networks such as the Internet or over communication lines such as telephone lines, or devices that store programs for a fixed period of time, such as volatile memory within a computer system that serves as a server or client. The program may also be a program that implements part of the functions described above, or may be a program that can realize the functions described above in combination with a program already stored in the computer system, or may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0092] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention. [Explanation of symbols]

[0093] 10, 10a, 10b User terminal 20 POS terminals 30 Delivery management server 40 Waybill Print Server 41 Invoice Printer 50, 50a, 50b Delivery terminal 55, 55a, 55b Mobile Printer 301 Communications Department 302 Storage section 303 First acquisition part 304 Second Acquisition Department 305 First Processing Section 306 Second Processing Section 307 Transmission Unit 308 Control Unit L Waybill NW Network OP Form S Delivery System

Claims

1. a first acquisition unit that acquires waybill identification information of a waybill attached to a package to be delivered; a second acquisition unit that acquires destination information based on a recognition result of a character string representing the destination information from an image of a form attached to the package, the form having destination information that can identify the destination filled in; a first processing unit that stores the invoice identification information acquired by the first acquisition unit and the destination information acquired by the second acquisition unit in a storage unit; A delivery system having:

2. The second acquisition unit The destination information is obtained from either one of destination information generated based on an image of the form captured, and destination information input to a user terminal based on an operation input by a user who is a delivery requester requesting delivery of the package, and The first processing unit The destination information and the waybill identification information acquired by the second acquisition unit from either one of the two are stored in the storage unit. The delivery system of claim 1 .

3. A computer-implemented delivery management method, comprising: Acquire the waybill identification information of the waybill attached to the package to be delivered, acquiring destination information based on a recognition result in which a character string representing the destination information is recognized from an image of a form attached to the package, on which destination information that can identify the destination is filled out; The acquired invoice identification information and the acquired destination information are stored in a storage unit. A delivery management method including:

Images