Delivery system and delivery management method

Abstract

To provide a delivery system and a delivery management method that allow a user to associate a delivery address with a shipping label on data without using a dedicated device for printing the shipping label, the shipping label being used by a delivery person for delivery.SOLUTION: In a delivery system, a delivery management server includes: a first acquisition unit which acquires shipping label identification information of a shipping label transmitted from a user terminal, the shipping label identification information of a shipping label printed and placed in a delivery base being read by a user terminal of a user, who is a delivery request source; a second acquisition unit which acquires, from the user terminal, delivery address information that identifies a delivery address based on an operation input of the user; a first processing unit which causes a storage unit to store the acquired shipping label identification information and the delivery address information; and a second processing unit which stores, in response to a delivery person reading, with a delivery person terminal, the shipping label identification information of the shipping label attached to a package to be delivered, reception information in association with the delivery address information stored in the storage unit, the reception information indicating that a package has been received for the shipping label identification information transmitted by the delivery person terminal.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] When delivering a package from a delivery requester to a destination, the delivery requester describes the destination's address, name, phone number, etc. on a delivery slip, attaches it to the package, and brings it to a delivery base or has a delivery carrier pick it up. Also, when creating an invoice, there is a service that allows the invoice to be created by inputting the destination's address, etc. into the delivery requester's terminal device and printing the invoice using a printing device at the delivery requester. A user can select any of various invoice creation methods to create an invoice. In addition, there is also a system in which a user of a delivery requester pre-enters information such as the destination into a terminal device, and when the user of the delivery requester brings the package to a courier's base, a delivery label is printed based on the pre-entered information to create an invoice (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, although a user can create an invoice and request a delivery in various ways, it is desirable to be able to provide a new delivery mechanism.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a delivery system and a delivery management method that can provide a new delivery mechanism.

Means for Solving the Problems

[0006] In order to solve the above-described problems, one aspect of the present invention is a delivery system including: a first acquisition unit that acquires delivery slip identification information that is printed on a delivery slip placed at a base and read by a user terminal of a user who is a delivery requester and transmitted from the user terminal; a second acquisition unit that acquires delivery destination information capable of specifying a delivery destination based on an operation input of the user from the user terminal; a first processing unit that stores the acquired delivery slip identification information and the acquired delivery destination information in a storage unit; and a second processing unit that stores, in association with the delivery destination information in the storage unit, acceptance information indicating that the package has been accepted for the delivery slip identification information transmitted from the delivery person terminal in response to the delivery slip identification information of the delivery slip attached to the package to be delivered being read by the delivery person terminal of the delivery person.

[0007] Also, one aspect of the present invention is a delivery system including: a first acquisition unit that acquires delivery slip identification information that is printed on a delivery slip placed at a base and read by a user terminal of a user who is a delivery requester and transmitted from the user terminal; a second acquisition unit that acquires delivery destination information capable of specifying a delivery destination based on an operation input of the user from the user terminal; a first processing unit that stores the acquired delivery slip identification information and the acquired delivery destination information in a storage unit; and a transmission unit that transmits, to the terminal that has read the delivery slip identification information, the delivery destination information corresponding to the read delivery slip identification information in response to the delivery slip identification information of the delivery slip attached to the package to be delivered being read by the delivery person terminal of the delivery person or the user terminal of the user at the delivery destination of the package.

[0008] In addition, one aspect of the present invention is that the invoice identification information printed on the invoice placed at the base is read by the user terminal of the user who is the delivery requester, the invoice identification information transmitted from the user terminal is acquired, delivery destination information capable of specifying the delivery destination based on the operation input of the user is acquired from the user terminal, the acquired invoice identification information and the acquired delivery destination information are stored in a storage unit, and in response to the invoice identification information on the invoice attached to the package to be delivered being read by the delivery person's delivery terminal, acceptance information indicating that the package has been accepted for the invoice identification information transmitted from the delivery terminal is stored in association with the delivery destination information in the storage unit. This is a delivery management method.

[0009] In addition, one aspect of the present invention is that the invoice identification information printed on the invoice placed at the base is read by the user terminal of the user who is the delivery requester, the invoice identification information transmitted from the user terminal is acquired, delivery destination information capable of specifying the delivery destination based on the operation input of the user is acquired from the user terminal, the acquired invoice identification information and the acquired delivery destination information are stored in a storage unit, and in response to the invoice identification information on the invoice attached to the package to be delivered being read by the delivery person's delivery terminal or the user terminal of the user at the delivery destination of the package, the delivery destination information corresponding to the read invoice identification information is transmitted to the terminal that read the invoice identification information. This is a delivery management method.

Advantages of the Invention

[0010] As described above, according to this invention, a new delivery mechanism can be provided. Even without dedicated equipment for printing invoice labels, the user can link the delivery destination to the invoice in data, and the delivery person can directly use the invoice for delivery.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Mode for Carrying Out the Invention

[0012] Hereinafter, the delivery system S according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of the delivery system S according to an 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, a delivery note printing server 40, a delivery note printing device 41, a delivery person terminal 50 (50a, 50b), a mobile printer 55 (55a, 55b), and a network NW.

[0013] The user terminals 10 (10a, 10b) are terminal devices used by users. The user can be any of a general consumer, an employee of a company or an organization. When the user terminal 10 is used by a general consumer, it is used at the home or away from home of the general consumer. When the user terminal 10 is used by an employee of a company or an organization, it is used at a facility managed by the company or organization. For example, the user terminal 10a is used by the user who is the sender of the delivery request, and the user terminal 10b is used by the user (e.g., the recipient) at the delivery destination of the package. The user terminal 10 may be, for example, a smartphone, a tablet, a mobile phone, a PC (Personal Computer), or the like. If the user terminal 10 has a camera, it can read a machine-readable code. The machine-readable code represents the delivery note identification information for individually identifying a delivery note, and may be any of a one-dimensional barcode, a two-dimensional barcode, or the like. The machine-readable code is attached to the delivery note. In addition, the user terminal 10 has a display function for displaying various data on a display screen, an input function for inputting various data, and the like. The display screen may be a liquid crystal display panel provided in the delivery person terminal 50. The input of data is input via any input device such as a touch panel, a keyboard, a mouse, etc. based on an operation input from the user. The data to be input may be, for example, delivery destination information, sender information. Also, when the user terminal 10 does not have a camera or does not use a camera, the data to be input may be the delivery note identification information. The user terminal 10 is communicably connected to the delivery management server 30 via the network NW.

[0014] 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 delivery note by a scanner. Also, the POS terminal 20 performs a settlement regarding the payment of the delivery fee from the user who is the sender. The POS terminal 20 is installed at a base. The base is a base that manages packages in order to make deliveries in response to requests from users who are the delivery requesters. At the base, there are a collection base for collecting packages, a relay base for relaying until the collected packages are transported to the destination user, and the like. Among these, the POS terminal 20 is installed at the collection base. The collection base may be, for example, a base that performs the task of receiving packages from the delivery requester. For example, there are business offices of delivery companies, convenience stores, drugstores, individual stores, and the like.

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

[0016] The shipping note printing server 40 is communicably connected to the delivery management server 30 via the network NW and is communicably connected to the shipping note printing device 41. The shipping note printing server 40 receives number band data representing a shipping note usage number band from the delivery management server 30 and causes the shipping note printing device 41 to print a shipping note based on the number band data. The shipping note printing device 41 is communicably connected to the shipping note printing server 40. The shipping note printing device 41 prints a shipping note by printing on a printing medium based on the number band data output from the shipping note printing server 40. The printing medium used as a shipping note has one main surface as a printable surface, an adhesive layer is formed on the other main surface, and a release paper is attached. The user of the delivery requester or the package collection staff at the collection base can attach the shipping note to the package by peeling off the release paper and sticking the surface with the adhesive layer to the package. Such a shipping note can be used as a shipping label.

[0017] The delivery person terminal 50 (50a, 50b) is communicably connected to the delivery management server 30 via the network NW. Also, the delivery person terminal 50 is communicably connected to the mobile printer 55. The delivery person's terminal 50 is used by a person in charge of operations related to the delivery of goods. For example, it is carried by a collection driver, a delivery driver, a sorting person in charge of sorting goods, a goods reception person in charge of receiving goods, etc. The delivery person's terminal 50 has a camera and functions such as reading a machine-readable code attached to a shipping note and displaying various data on a display screen. The display screen may be a liquid crystal display panel provided on the delivery person's terminal 50. The delivery person's terminal 50 may be, for example, any of a smartphone, a tablet, a mobile phone, a PC, etc. The delivery person's terminal 50 can cause the mobile printer 55 to print print data by outputting the print data to the mobile printer 55. The print data may be, for example, delivery destination information or a part of the delivery destination information.

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

[0019] The mobile printer 55 (55a, 55b) is a printing device that is communicably connected to the delivery person's terminal 50 and prints the print data transmitted from the delivery person's terminal 50 on a printing medium. The mobile printer 55 may be a device separate from the delivery person's terminal 50, or the mobile printer 55 may be integrally provided on the delivery person's terminal 50.

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

[0021] FIG. 2 is a diagram showing an example of the appearance of the shipping note L. Various data can be printed on one main surface of the shipping note L. The delivery note L has a two-dimensional barcode La, delivery note identification information Lb, a one-dimensional barcode Lc, and a one-dimensional barcode Ld printed thereon, and a partial area of the delivery note is divided as a spare area Le. The two-dimensional barcode La is a two-dimensional barcode representing the delivery note identification information. Also, in the case of corporate use, corporate information may be described following the delivery note identification information. In this case, it may be a two-dimensional barcode including the delivery note identification information and the corporate information. The delivery note identification information Lb represents the delivery note identification information by a character string and is the same as the delivery note identification information represented by the two-dimensional barcode La. The one-dimensional barcode Lc and the one-dimensional barcode Ld can be used for various management purposes. The spare area Le is an area that can be used as needed to write necessary information by hand or attach labels, forms, etc. when delivering the package. This spare area Le may be delivered without writing anything or without attaching labels or forms.

[0022] Figure 3 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 storage 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, and a control unit 308. 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 storage unit 302 is composed of a storage medium, for example, an HDD (Hard Disk Drive), a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), a RAM (Random Access read / write Memory), a ROM (Read Only Memory), or an arbitrary combination of these storage media. This storage unit 302 can use, for example, a non-volatile memory.

[0023] The first acquisition unit 303 acquires the invoice identification information that is printed on the invoice and placed at the base, and is read by the user terminal of the user who is the delivery requester, and is transmitted from the user terminal.

[0024] The second acquisition unit 304 acquires destination information that can identify the destination based on the user's operation input from the user terminal.

[0025] The first processing unit 305 stores the acquired invoice identification information and the acquired destination information in the storage unit.

[0026] The second processing unit 306 stores, in association with the destination information in the storage unit 302, acceptance information indicating that the package has been accepted for the invoice identification information transmitted from the delivery person terminal in response to the invoice identification information of the invoice attached to the package to be delivered being read by the delivery person terminal of the delivery person.

[0027] The transmission unit 307 transmits the destination information corresponding to the read invoice identification information to the terminal (delivery person terminal 50 or user terminal 10) that has read the invoice identification information in response to the invoice identification information of the invoice attached to the package to be delivered being read by the delivery person terminal 50 of the delivery person or the user terminal 10 of the user of the destination of the package.

[0028] The control unit 308 controls each unit of the delivery management server 30. Further, the control unit 308 performs writing and reading processes of each data stored in the storage unit 302 according to the delivery status.

[0029] FIG. 4 is a diagram showing an example of delivery data stored in the storage unit 302. The delivery data includes invoice identification information, delivery requester information, destination information, package information, and status. The invoice identification information is information that individually identifies the invoice. The delivery requester information is information regarding the delivery requester, and includes, for example, the address, name, phone number, etc. of the user who is the delivery requester. The destination information is information about the destination source, for example, the address, name, phone number, etc. of the destination user. The package information is information about the package, for example, it includes the size of the package, whether it is refrigerated, whether it is frozen, the delivery fee, etc. The status is information representing the delivery status of the package. For example, there are a receiving flag, a delivery flag, a delivery completion flag, an absence flag, etc. The receiving flag is information indicating whether the package has been received by the collection staff. For example, the receiving flag "0" represents the state of not being received, and the receiving flag "1" represents the state of being received.

[0030] The delivery flag is information indicating whether the package is in the process of being delivered. For example, the delivery flag "0" represents the state of not being delivered (before the package is received, after delivery is completed, etc.), and the delivery flag "1" represents the state of being in the process of being delivered (the state from the time of being received until before delivery to the destination user is completed). The delivery completion flag is information indicating whether the package has been received by the destination user. For example, the delivery completion flag "0" represents the state of not being delivered (for example, the state from the time the package is deposited at the collection point until before delivery to the destination user is completed), and the delivery completion flag "1" represents the state of the package being delivered to the destination user. The absence flag is information indicating whether the driver of the delivery staff visited the destination address but the user was absent and the package was taken back. For example, the absence flag "0" represents the state where the driver of the delivery staff has not visited the destination address yet, and the absence flag "1" represents the state where the driver of the delivery staff visited the destination address but the user was absent and the package was taken back.

[0031] 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 composed of a processing device such as a CPU (Central Processing Unit) or a dedicated electronic circuit.

[0032] Next, the operation of the above-described delivery system S will be described with reference to FIGS. 5 to 11. FIG. 5 is a diagram for explaining the operation of the delivery system S, FIG. 6 is a conceptual diagram for explaining the flow of the registration process, FIG. 7 is a diagram for explaining the operation of the delivery system S, FIG. 8 is a conceptual diagram for explaining the flow of receiving a package, FIG. 9 is a diagram for explaining the operation of the delivery system S, and FIG. 10 is a diagram for explaining the operation of the delivery system S.

[0033] The delivery management server 30 assigns an available invoice use number band (FIG. 7; step S301). The invoice use number band is data representing invoice identification information that can be used as the invoice identification information to be attached to the invoice. For example, the invoice identification information can be represented by a character string. When the character string is represented by a number, the invoice use number band represents the range of available numbers. For example, the invoice use number band may be specified as a range of numbers from number 1 to number n (consecutive numbers), or may individually specify available character strings (not necessarily consecutive numbers). Further, the invoice identification information may be a character string in which a plurality of numbers are arranged, but may also be a character string in which alphabets or symbols are arranged, or a character string in which at least two of numbers, alphabets, and symbols are combined. After the invoice number is issued, printed on the invoice, attached to the package, and after a certain period has elapsed after the delivery is completed and other conditions are satisfied, it may be made reusable again. In this way, available numbers are assigned as the invoice use number band. The delivery management server 30 transmits the number band data representing the invoice use number band to the invoice printing server 40 (FIG. 5; step S101, FIG. 7 step S305).

[0034] When the invoice printing server 40 receives the numbered strip data from the delivery management server 30, it causes the invoice printing device 41 to print an invoice according to the invoice use numbered strip indicated by the received numbered strip data (FIG. 5; step S105, FIG. 7; step S315). For example, the invoice printing server 40 generates a two-dimensional barcode representing the invoice identification information included in the invoice use numbered strip (FIG. 7; step S310), and prints one two-dimensional barcode on each different invoice. Here, a two-dimensional barcode representing the invoice identification information may be printed on the invoice, or the string itself representing the invoice identification information may be printed on the invoice. Also, both the two-dimensional barcode and the string representing the invoice identification information may be printed. In this embodiment, the case where the invoice identification information is printed as a two-dimensional barcode will be described, but it may also be a one-dimensional barcode.

[0035] The invoice printing device 41 prints one invoice identification information on one invoice according to an instruction from the invoice printing server 40 (FIG. 7; step S320). Here, when a plurality of invoice identification information is included in the invoice use numbered strip, each invoice identification information is printed on a different invoice.

[0036] When the invoice is printed, the printed invoice is sent to and placed at the base. For example, the printed invoice is delivered to and placed in a convenience store (FIG. 5; step S110). The invoice placed in the convenience store can be distributed to the user who is the delivery requester.

[0037] When the user who is the delivery requester wishes to have a package delivered, the user can register with the delivery management server 30 in advance. By registering in advance, the address, name, telephone number, etc. of the user who is the delivery requester can be specified as the address, name, telephone number, etc. of the user who is the delivery requester without directly inputting them from the user terminal 10a etc. each time of delivery, using the address, name, telephone number, etc. of the user who has registered. When the user who is the delivery requester wants to register, the user terminal 10a accesses the web page for user registration published 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, phone number, etc. of the user who is the delivery requester. Based on the operation input from this user, the user terminal 10a performs user registration processing (FIG. 7; step S325). The user terminal 10a transmits various data input by the user to the delivery management server 30 and also transmits a user registration request (FIG. 7; step S330).

[0038] Based on the user registration request transmitted from the user terminal 10a, the delivery management server 30 assigns user identification information for individually identifying the user, associates the various data transmitted from the user terminal 10a with the user identification information, and stores them in the storage unit 302 (FIG. 7; step S335). In this way, user processing in the delivery management server 30 is executed.

[0039] Also, when the user who is the delivery requester wishes to have a package delivered, the user brings the package to a base such as a convenience store. And at the base, the user receives a shipping note (FIG. 5; step S115). When the user who is the delivery requester receives the invoice, the user reads the invoice identification information printed on the invoice by taking a picture with the camera of the user terminal 10a (FIG. 6; step 201, FIG. 7; S340), and inputs the delivery destination address, name, telephone number, etc. as delivery destination information using the input device of the user terminal 10a, and transmits the invoice identification information and the delivery destination address to the delivery management server (FIG. 5; step S120, FIG. 6; step S205, FIG. 7; step S345). Thereby, the registration procedure of various information for the invoice identification information is performed. Here, if the user who is the delivery requester has previously registered, by logging in from the web service or application program of the delivery service, the delivery requester's address, paper, telephone number, etc. can be set as the delivery requester information without manual input of the registered user data. Also, if the user who is the delivery requester has not previously registered, the user may input their own address, name, telephone number, etc. from the user terminal 10a as the delivery requester information. In this case, the delivery management server 30 may assign a guest account to a user who has not been registered, and manage the user who is the delivery requester using the guest account for a certain period of time.

[0040] Here, after the user terminal 10a reads the invoice identification information with the camera and transmits the invoice identification information to the delivery management server 30, the user may be asked to input the delivery destination information and the delivery destination information may be transmitted to the delivery management server 30. Also, after the user terminal 10a asks the user to input the delivery destination information and transmits the delivery destination information to the delivery management server 30, the user may be asked to read the invoice identification information of the invoice with the camera and transmit the invoice identification information to the delivery management server 30. In addition, the user terminal 10a may read the invoice identification information by means of a camera, temporarily store the read invoice identification information in a storage area within the user terminal 10a, and after obtaining the destination information from the user, transmit the invoice identification information together with the destination information to the delivery management server 30. Alternatively, after obtaining the destination information from the user, the user terminal 10a may temporarily store the input destination information in a storage area within the user terminal 10a, read the invoice identification information by means of a camera, and transmit the invoice identification information together with the destination information to the delivery management server 30. In addition, the invoice identification information can be extracted from the two-dimensional barcode attached to the invoice by the user terminal 10a reading the two-dimensional barcode. However, if the invoice identification information is not a two-dimensional barcode but is printed on the invoice as a character string, the user terminal 10a may capture the character string with its camera and perform OCR (Optical Character Reader) processing on the captured image to extract the character string. Also, when the character string representing the invoice identification information is printed on the invoice, the user of the delivery requester may register it by directly entering the character string manually into the user terminal 10a.

[0041] When the user of the delivery requester transmits the invoice identification information and the destination information to the delivery management server 30, the user attaches the invoice with the invoice identification information to the package to be delivered (FIG. 6; step S210) and hands it over to the person in charge at the base (FIG. 5; step S125). Here, when handing over the package, the user of the delivery requester may, if necessary, write by hand the address, name, telephone number of the user of the delivery requester, the address, name, telephone number of the destination user, etc. in the preliminary area Le of the invoice, or may not write them. Here, since the destination information and the delivery requester information have already been registered for the invoice identification information, it is not necessary to describe or print the information regarding the destination or the delivery requester as a character string directly on the invoice.

[0042] When the delivery management server 30 receives the bill identification information, the delivery request source information, and the delivery destination information from the user terminal 10a, it stores them in the storage unit 302. Further, the delivery management server 30 uses the address included in the received delivery request source information and the address included in the delivery destination information as temporary data, and based on this temporary data, determines a delivery route (FIG. 7; step S350), and stores the delivery route in the storage unit 302 in association with the bill identification information. Also, the delivery management server 30 may transmit a temporary delivery schedule corresponding to the delivery route based on the temporary data to the user terminal 10a and cause it to be displayed on the user terminal 10a.

[0043] When the person in charge at a base (for example, a convenience store) (for example, a store clerk) receives the luggage from the user who is the delivery request source, the bill identification information printed on the bill attached to the luggage is read by the scanner of the POS terminal 20 (FIG. 6; step S215, FIG. 9 step S501), and the luggage is stored in the storage location (FIG. 5; step S130). Here, when the bill identification information is normally read by the scanner of the POS terminal 20 (FIG. 9; step S505), the POS terminal 20 transmits the read bill identification information to the delivery management server 30. As a result, in the delivery management server 30, it is registered that the luggage to be delivered has been stored (delivered) at the base where the POS terminal 20 is installed. The delivery management server 30 may transmit a receipt notice including which luggage has been received and the receipt date and time, etc. to the user terminal 10a in response to the registration that the luggage to be delivered has been stored.

[0044] In addition, based on receiving the invoice identification information from the POS terminal 20, the delivery management server 30 determines the delivery route corresponding to the invoice identification information stored in the storage unit 302 (FIG. 9; step S510). When the delivery route is determined, the delivery management server 30 transmits instructions for vehicle allocation to the center, loading, and collection to the relevant parties. For example, the delivery management server 30 transmits a collection instruction to the delivery person terminal 50 of the person in charge of collecting the goods at the collection point (FIG. 9; step S525). When the delivery person terminal 50 receives this instruction, it displays the instruction on the display screen. As a result, the driver in charge of collection can recognize that collection is to be carried out. Also, based on the delivery route, the delivery management server 30 may extract the delivery destination information of the goods corresponding to the delivery area assigned to the delivery person and transmit it to the delivery person terminal 50 of the delivery person as a delivery destination list. Thereby, the delivery person terminal 50 can grasp the delivery destinations based on the delivery destination list. Here, by transmitting the delivery destination list to the delivery person terminal 50 in advance, the delivery person can know which goods need to be delivered. Further, the delivery management server 30 may transmit the delivery destination list to the delivery person terminal 50 including the delivery destination information, the delivery request source information, and the invoice identification information. Thereby, various information regarding the goods can be obtained without the delivery person terminal 50 reading the invoice identification information attached to the invoice and querying the delivery management server 30. For example, even in a situation where the delivery management server 30 and the delivery person terminal 50 cannot communicate, various information regarding the goods can be grasped based on the delivery destination list of the delivery person terminal 50. Here, the invoice identification information is represented by characters and printed separately from the two-dimensional barcode on the invoice, so that the correspondence between the goods and the data included in the delivery destination list can be grasped based on the invoice identification information.

[0045] In addition, the delivery management server 30 transmits a notification indicating that the package has been collected to the user terminal 10b of the destination user (FIG. 9; step S515). This transmission may be made using SMS (Short Message Service) with the phone number included in the destination information as the destination. Also, this message may include the scheduled delivery date based on the delivery route and the collection date and time. The user terminal 10b receives this notification and displays on the display screen a message indicating that the package has been shipped and the scheduled delivery date (FIG. 9; step S520).

[0046] Among the delivery companies, the driver in charge of collection carries the delivery person terminal 50a and makes rounds of each base for collection (FIG. 5; step S135). Here, the driver also makes a round to the base where the package was stored in FIG. 5; step S130 and picks up the package stored at the base. The driver in charge of collection who has received the package reads the waybill identification information attached to the received package using the delivery person terminal 50a (FIG. 9; step S530) and presses the "Collection Button" indicating that the collection has been made. When the delivery person terminal 50a reads the waybill identification information and the collection button is pressed, it transmits the waybill identification information, the data indicating "collection", and the delivery management server 30.

[0047] When the delivery management server 30 receives data indicating collection from the delivery person terminal 50a and the bill of lading identification information, it refers to the storage unit 302 and checks whether it matches the bill of lading identification information transmitted from the POS terminal 20 and registered (FIG. 9; step S530). Then, as a result of the check, if the bill of lading identification information matches, the delivery management server 30 rewrites the status corresponding to the bill of lading 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 can be grasped from the status that the goods deposited at the collection base have been delivered to the delivery company. Here, when delivering goods using a handwritten delivery note, if the delivery destination address, name, phone number, the delivery requester's address, name, phone number, the name of the goods, etc. are written by hand or the like, it can be grasped that the use of the delivery note has started. However, in the bill of lading in the above-described embodiment, since it is used in a state where a two-dimensional barcode or the like is printed, the delivery destination information and the delivery requester information are not necessarily described on the bill of lading. Therefore, it is difficult to grasp whether the bill of lading has started to be used, for example, whether it has been accepted by the delivery company, only from the face of the bill of lading. However, by reading the bill of lading identification information of the bill of lading by the user terminal 10 or the delivery person terminal 50 and accessing the delivery management server 30 and referring to the acceptance flag, it is possible to grasp whether the bill of lading has started to be used and whether the goods have been accepted by the delivery company.

[0048] Here, the driver in charge of collection can perform an operation input to print a part of the delivery destination information on the delivery person terminal 50a. When the delivery person terminal 50a reads the bill of lading of the goods for which a part of the delivery destination information is to be printed and an operation input for printing a part of the bill of lading information is made, a part of the information of the read bill of lading is printed by the mobile printer 55a connected to the delivery person terminal 50a (FIG. 5; step S145, FIG. 9; S535). The mobile printer 55a prints a part of the delivery destination information on a printing medium based on an instruction from the delivery person terminal 50a. Part of the recipient information may be information including at least part of the recipient's address, the recipient's name, and the telephone number. Further, the delivery person terminal 50a may cause the mobile printer 55a to print a character string representing part of the recipient information, or may generate a two-dimensional barcode corresponding to part of the recipient information and cause the generated two-dimensional barcode to be printed by the mobile printer 55a.

[0049] The printing medium may be a label that can be pasted as a sticker. When part of the recipient information is printed on such a label, the driver in charge of cargo collection may paste the label on which part of the recipient information is printed on the preliminary area Le of the shipping document. When a character string representing part of the recipient information is printed on a label and attached to the shipping document, the delivery company or the recipient's user can, by looking at the shipping document, grasp the address, name, telephone number, etc. of the user who placed the delivery request, the address, name, telephone number, etc. of the recipient's user. Further, when a two-dimensional barcode representing part of the name of the delivery requester and part of the recipient's address (for example, an address in a section smaller than the city, ward, town, or village in the address) is printed on the label and attached to the shipping document, the two-dimensional barcode on the label is read by the delivery person terminal 50 or the recipient's user terminal 10b, and by interpreting the two-dimensional barcode, even without sending an online inquiry to the delivery management server 30, in an offline state, part of the address and the name can be extracted from the two-dimensional barcode. Thereby, for example, when the delivery person reads the two-dimensional barcode on the label, even if an environment occurs where the delivery person terminal 50 cannot communicate with the delivery management server 30 (outside the range of the network NW, communication error, etc.), the recipient can be grasped and the delivery operation can be continued. Here, all of the address may be included in the two-dimensional barcode, but as long as it is an address belonging to the delivery area, it does not necessarily have to include all of the address. For example, the element of the prefecture may be omitted. Although the case of printing above part of the recipient information on the label has been described, it does not necessarily have to be printed.

[0050] In addition, the driver in charge of cargo collection can inquire the delivery management server 30 about the delivery destination information associated with the bill of lading identification information by reading the bill of lading identification information attached to the bill of lading by the delivery person terminal 50a, and display the result on the display screen of the delivery person terminal 50a. Thereby, even if a part of the delivery destination information or the like is not printed by the mobile printer 55a, the address, name, telephone number, etc. of the delivery destination information can be confirmed on the display screen. The driver in charge of cargo collection loads the goods onto the vehicle and delivers the goods from a base such as a convenience store to a relay base.

[0051] At the relay base, the relay driver can confirm the delivery destination of each piece of cargo by reading the bill of lading identification information of the bill of lading of the cargo to be relayed using the driver terminal he / she owns (FIG. 5; step S155). The relay driver sorts according to the delivery destination address, etc., and delivers the goods to the base for delivery (FIG. 5; step S160). The delivery bases are bases installed in each region, and the goods are delivered to each delivery destination by the delivery driver from the delivery bases.

[0052] The recipient user can also confirm the scheduled delivery date by the user terminal 10b and, if necessary, change the scheduled delivery date by performing an operation input to change the scheduled delivery date. When the user terminal 10b receives an operation input to change the scheduled delivery date (FIG. 9; step S540), it transmits the changed scheduled delivery date to the delivery management server 30 based on the operation content (FIG. 9; step S545). When the delivery management server 30 receives a request to change the scheduled delivery date, it registers the change content regarding the scheduled delivery date by writing it into the storage unit 302 (FIG. 9; step S550). Thereby, the change content of the scheduled delivery date is notified to the delivery person terminal 50b of the delivery person. Thereby, the delivery person delivers the goods based on the changed scheduled delivery date.

[0053] At the delivery base, the driver in charge of delivery receives the packages to be delivered at the delivery base. Then, using the delivery terminal 50b that the driver owns, the driver causes the delivery note identification information of the packages to be delivered to be read. When the delivery terminal 50b reads the delivery note identification information attached to the delivery note, it transmits the delivery note 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 (Figure 5; Step S170). As a result, the delivery driver in charge can confirm the delivery destination address, name, phone number, etc. on the delivery terminal 50a by visually recognizing the delivery destination information displayed on the display screen. The delivery driver in charge confirms the delivery destination address, name, etc. and delivers the packages to the delivery destination (Figure 5; Step S175). The delivery driver in charge visits the address of the recipient user and delivers the packages to the recipient user (Figure 8; Step S401). At that time, the delivery driver in charge reads the delivery note identification information of the delivery note attached to the package to be handed over by the delivery terminal 50b and inputs an instruction of "delivery completed" (Figure 10; Step S601).

[0054] When the delivery management server 30 receives the delivery note identification information and the instruction of "delivery completed" from the delivery terminal 50b, it rewrites the status corresponding to the received delivery note identification information among the information stored in the storage unit 302 to "delivery completed" (Figure 10; Step S610). Then, for the received delivery note identification information, when certain conditions such as the elapse of a predetermined period (for example, several months, etc.) are satisfied, the delivery management server 30 performs processes such as registering it in the delivery note usage number band. As a result, even if the character string that can be handled as the delivery note identification information is limited, the delivery note identification information for which the delivery management has ended can be reused.

[0055] The delivery management server 30 calculates the CO2 emission amount based on the delivery route, etc. for the delivery note identification information rewritten to "delivery completed", and stores the calculated CO2 emission amount in association with the delivery note identification information.

[0056] On the one hand, when the recipient user receives the package, they use their user terminal 10b to read the waybill identification information printed on the waybill attached to the package (Fig. 8; step S405), and send a query request together with the read waybill identification information to the delivery management server 30. When the delivery management server 30 receives the waybill identification information and the query request from the user terminal 10b, it reads out the recipient information and the delivery request source information corresponding to the waybill identification information from the storage unit 302, and sends them to the querying user terminal 10b. When the user terminal 10b receives the recipient information and the delivery request source information from the delivery management server 30, it displays the recipient information and the delivery request source information on the display screen. As a result, the recipient user can confirm the sender's address, name, phone number, etc., and can also confirm the recipient's address, name, phone number, etc. (Fig. 5; step S180). The recipient user checks the delivery request source and the recipient. If there is no problem, they perform a touch input on the "Receive" button on the display screen. Based on the "Receive" notification, the delivery management server 30 updates the status in the storage unit 302 to "Received", and sends a "Delivery Completed" notification to the user terminal 10a of the delivery request source (Fig. 8; step S410, Fig. 10 step S620). This notification can be sent by sending an email to the email address of the user terminal 10a, or by using SMS for notification.

[0057] Here, when the recipient user does not perform an operation input regarding "Receive" (when delivering the package non-face-to-face such as leaving it for delivery, when the user terminal 10b is not available at the recipient user's place, when it is difficult for the recipient user to perform an operation input for "Receive", etc.), the delivery driver of the delivery staff can read the waybill identification information printed on the waybill attached to the package with their delivery person terminal 50b, and input an instruction of "Delivery Completed" from the delivery person terminal 50b.

[0058] In addition, the user terminal 10a receives the "delivery completed" notification sent from the delivery management server 30 and displays it on the display screen (FIG. 8; step S410, FIG. 10 step S625). This notification may be sent by sending an email to the email address of the user terminal 10a, or may be sent using SMS. Also, for example, when sending a delivery completion notification by email, a URL (uniform resource locator) of a web page capable of displaying the date and time when the delivery of the package was completed, etc. is described in the body of the email. When a touch input is made to the URL by the user, a web page related to the delivery completion may be displayed on the display screen of the user terminal 10a. Thereby, the user who placed the delivery request can grasp the details regarding the delivery completion. In addition, when there is an access from the user terminal 10a to the URL described in the delivery completion notification email (FIG. 10; step S630), the delivery management server 30 transmits data for displaying a web page related to the delivery completion to the user terminal 10a and causes it to be displayed. Also, the delivery management server 30 may store data indicating that the user terminal 10a has received and confirmed the delivery completion notification as status information corresponding to the bill identification information (FIG. 10; step S635).

[0059] Next, FIG. 11 is a flowchart for explaining the operation of the delivery management server 30. When the bill placed at the collection point is received by the user who placed the delivery request, and the bill identification information of the bill is read by the user terminal 10a according to the operation of this user, the read bill identification information is transmitted to the delivery management server 30. In addition, the user terminal 10a transmits the delivery source information and the delivery destination information to the delivery management server 30 according to the operation of the user. Here, for the delivery destination identification information, the delivery source information, and the delivery destination information, the user terminal 10a may transmit them together 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 by receiving the invoice identification information, and the second acquisition unit 304 acquires the delivery destination information and the delivery request source information (step S701).

[0060] When the invoice identification information, the delivery destination information, and the delivery request source information are acquired, the first processing unit 305 stores the acquired invoice identification information, the delivery destination information, and the delivery request source information in the storage unit 302 in association with each other (step S702). Next, when the goods are delivered from the delivery request source to the person in charge at the collection base and the invoice identification information is read by the POS terminal 20, the POS terminal 20 transmits the read invoice identification information to the delivery management server 30. When the control unit 308 of the delivery management server 30 acquires the invoice identification information from the POS terminal 20 (step S703), it registers by associating, as status information, that the goods to be delivered are stored (delivered) in the invoice identification information and writing it to the storage unit 302. Thereby, the invoice identification information becomes active (step S704).

[0061] Next, when the invoice identification information of the invoice attached to the goods to be delivered is read by the delivery person terminal 50a of the delivery person and the invoice identification information is transmitted from the delivery person terminal 50a, the second processing unit 306 acquires it by receiving the invoice identification information from the delivery person terminal 50a (step S705). Then, after the invoice identification information and the delivery destination information in step S704 are stored in association with each other, when the invoice identification information is acquired from the delivery person terminal, the second processing unit 306 determines that the goods to be delivered have been accepted by the delivery person, and stores the acceptance information in the storage unit 302 in association with the invoice identification information (step S706). Here, the second processing unit 306 may determine that the goods to be delivered have been accepted by the delivery person when receiving the invoice identification information together with the data indicating that the goods have been collected from the delivery person terminal 50a.

[0062] Next, when the control unit 308 receives an inquiry request together with the bill of lading identification information from the delivery person terminal 50 or the user terminal 10 (step S707), it reads out the delivery destination information corresponding to the received bill of lading identification information from the storage unit 302 and transmits it to the terminal device of the request source (the delivery person terminal 50 or the user terminal 10) (step S708). As a result, the delivery person carrying the delivery person terminal 50 can confirm the delivery destination information and continue the delivery service according to the delivery destination. Alternatively, the user who owns the user terminal 10 can confirm the delivery destination information. That is, when receiving the delivered goods, the user at the delivery destination can have the user terminal 10 read the bill of lading identification information to confirm whether the delivery destination is for himself / herself, and then can open the package, etc.

[0063] Next, when the control unit 308 receives a "received" notification from the user terminal 10b or a "delivery completed" notification from the delivery person terminal 50 (step S709), it updates the status corresponding to the bill of lading identification information stored in the storage unit 302 to "received" (step S710). Then, the control unit 308 notifies the user terminal 10a of the delivery source user that the delivery is completed (step S711).

[0064] According to the embodiment described above, even in a situation where information regarding the delivery destination and the delivery request source such as a delivery note is not necessarily written, the goods can be managed using the bill of lading identification information attached to the goods, and a new delivery mechanism can be provided.

[0065] According to the embodiments described above, in the invoice, without necessarily describing the destination information or the consignor information, by reading the invoice identification information attached to the invoice, information regarding the destination, information regarding the consignor, the status of the package, etc. can be grasped. As a result, it is not always necessary to describe information regarding the destination or the consignor in the invoice. A new delivery mechanism can be provided. Also, since it is possible to avoid the situation where the address, name, phone number of the destination, the address, name, phone number of the consignor, etc. are attached to the package and delivered in a visible state, the protection of privacy can be improved. Further, there is no need to use a delivery note in which multiple copies of a form are stacked and the address, name, phone number, etc. are written. By using the invoice identification information attached to the package, information regarding the destination, information regarding the consignor, etc. can be referred to using a terminal device, so that the delivery slip can be digitized and a new delivery mechanism can be provided.

[0066] Also, according to the embodiments described above, even if the destination information is not printed on the invoice or not written by handwriting or the like, at least a part of the invoice information can be printed on a label as needed and can be pasted on the invoice. Further, when printing such a label, information including at least a part of the destination information is represented by a machine-readable code and printed. As a result, the destination information can be obtained by reading the machine-readable code with the user terminal 10 or the delivery person terminal 50. Thus, even in an environment where communication with the delivery management server 30 is not possible, the destination information can be obtained based on the machine-readable code.

[0067] Further, according to the above-described embodiment, since the acceptance information (for example, acceptance flag) is associated with and stored in the invoice identification information attached to the invoice, by referring to the acceptance flag, it is possible to grasp whether the goods deposited at the consolidation base have been delivered to the delivery carrier (whether the invoice identification information is active). Further, even if there is no handwritten writing or the like on the invoice regarding whether the invoice identification information attached to the invoice has been started to be used for delivery, it can be grasped. Also, even without dedicated equipment for printing invoice labels, the user can link the delivery destination to the invoice in data, and the delivery staff can use the invoice as it is for delivery.

[0068] ≪Another Embodiment (Part 1)≫ In the above-described embodiment, the case where the invoice identification information is included in the two-dimensional barcode La attached to the invoice and the case where the invoice identification information and the corporate information are included have been described. In another embodiment described below, the case where the two-dimensional barcode La attached to the invoice includes the invoice identification information and additional information will be described. The additional information may be, for example, connection destination information. The connection destination information is, for example, a URL representing an access destination. The invoice identification information and the connection destination information may be separate information, or the delivery destination identification information may be included in a part of the connection destination information.

[0069] FIG. 12 is a diagram showing an example of the connection destination information 100 obtained by interpreting the two-dimensional barcode attached to the invoice. Among the entire character string indicating the connection destination information 100, a part of the character string from the beginning to the middle is general information 110. The general information 110 is information that can be interpreted when the two-dimensional barcode La is read by any one of the user terminals 10a of the user who is the delivery requester, the user terminal 10b of the user at the delivery destination, and the user terminal of a user different from the user who is the delivery requester and the user at the delivery destination. Thereby, the user terminal 10a and the user terminal 10b can connect to the connection destination indicated by the connection destination information based on the general information 110. This general information 110 may include shipping identification information.

[0070] Among the entire character string indicating the destination information 100, the character string described after the general information is the concealed information 120. The concealed information 120 is a character string that neither the user terminal 10a of the delivery requester nor the user terminal 10b of the recipient can interpret. The concealed information 120 is a character string that the delivery person terminal 50 can interpret. The delivery person terminal 50 can interpret the general information 110, and can also interpret the overall information 130 indicated by the entire character string combining the general information 110 and the concealed information 120. Thereby, the delivery person terminal 50 can connect to the connection destination indicated by the connection destination information based on the overall information 130. The server indicated by the connection destination indicated by the general information 110 and the server indicated by the connection destination indicated by the overall information 130 are both the same delivery management server 30, but the response content from the delivery management server 30 differs depending on the connection destination.

[0071] When accessed at the URL based on the general information 110, the delivery management server 30 makes a response corresponding to the user terminal 10a of the delivery requester or the user terminal 10b of the recipient that is the access source, and when accessed at the URL based on the overall information 130, it has a response distribution function that makes a response corresponding to the delivery person terminal 50 that is the access source. By having the response distribution function, the delivery management server 30 can distribute the response content according to whether the electronic device that reads the same two-dimensional barcode La is the user terminal 10 or the delivery person terminal 50.

[0072] Here, for the two-dimensional barcode La, the case where general information 110 and hidden information 120 are included has been described. However, a two-dimensional barcode La including a plurality of different URLs is generated in advance, and depending on the terminal environment (for example, the OS (operating system) environment) of the electronic device that reads the two-dimensional barcode La, it is determined which URL should be accessed, and access may be made to the determined URL. For example, the OS environments of the user terminal 10 and the delivery person terminal 50 may be different, and due to the difference in the OS environment, the extracted URLs may be different. Thereby, the URL to be accessed can be allocated according to the OS environment. In this way, even when the URL is allocated according to the terminal environment, the server to be connected to is the same delivery management server 30. Also, for the two-dimensional barcode La, instead of including both general information 110 and hidden information 120, it may include only general information 110 without including hidden information 120. In this case, when the two-dimensional barcode La is read by the delivery person terminal 50, information that can be provided from the original reading delivery person terminal 50 may be added as a parameter to the general information 110, and access may be made from the delivery person terminal 50 to the delivery management server 30. The information that can be provided from the original reading delivery person terminal 50 may use, for example, at least any one of the IP address used when the delivery person terminal 50 accesses the delivery management server 30, the location information indicating the current location of the delivery person terminal 50, the terminal identification information of the delivery person terminal 50 assigned to the delivery person terminal 50, and the person-in-charge identification information assigned to the person-in-charge of the delivery company using the delivery person terminal 50. In this case, the delivery management server 30 can identify that the access source is the delivery person terminal 50 rather than the user terminal by referring to the parameters added to the general information 110, and can display a response screen corresponding to the delivery person terminal 50 on the delivery person terminal 50. For example, the delivery person terminal 50 adds information that can be provided from the reading source delivery person terminal 50 to the general information 110 as a parameter and accesses the delivery management server 30. The delivery management server 30 may read the hidden information corresponding to the parameters added to the general information 110 from the storage unit 302 and transmit it to the delivery person terminal 50. Then, the delivery person terminal 50 may add the acquired hidden information to the general information 110 and access the delivery management server 30.

[0073] FIG. 13 is a conceptual diagram for explaining the flow when the delivery note L is read by the user terminal 10 or the delivery person terminal 50. When the two-dimensional barcode La is read by the user terminal 10a of the delivery requester (step S800), the user terminal 10a extracts the delivery note identification information and the general information 110 by interpreting the two-dimensional barcode La, and accesses the URL indicated by the extracted general information 110 by specifying the delivery note identification information as a parameter. Here, the access destination indicated by the general information 110 is the delivery management server 30.

[0074] When the delivery management server 30 is accessed via the URL based on the general information 110 with the delivery note identification information specified as a parameter from the user terminal 10a, it determines by referring to the storage unit 302 whether the delivery destination information is associated with the delivery note identification information. If the delivery destination information is not registered for the delivery note identification information (at the stage before the delivery note identification information is acquired from the user terminal 10a of the delivery requester by the first acquisition unit 303 of the delivery management server 30), it transmits the registration content input screen data for registering the delivery destination information to the user terminal 10a (step S801).

[0075] The user terminal 10a receives the registration content input screen data and displays a registration content input screen G1 according to the registration content input screen data. The user of the delivery requester inputs delivery destination information such as the address, name, and phone number of the delivery destination based on the registration content input screen, and presses the send button. When the send button is pressed, the user terminal 10a transmits the input delivery destination information and the delivery note identification information to the delivery management server 30.

[0076] When the delivery destination information is acquired by the second acquisition unit 304 and the delivery note identification information is acquired by the first acquisition unit 303, the first processing unit 305 of the delivery management server 30 associates the delivery destination information with the delivery note identification information and stores it in the storage unit 302. The delivery management server 30 transmits a message indicating that the delivery destination information has been registered to the user terminal 10a and displays it on the display screen of the user terminal 10a.

[0077] After the delivery note identification information is acquired from the user terminal 10a, when the two-dimensional barcode La is read by either the user terminal 10a of the delivery requester or the user terminal 10b of the delivery destination and accessed according to the interpretation of the general information 110 (step S802), the delivery management server 30 displays a response screen corresponding to the delivery note identification information registered according to the registration status of the package according to the general information 110. Here, as the registration status of the package, since the delivery destination information is registered for the delivery note identification information, a registered screen G2 indicating that the delivery information has been registered is displayed as the response screen (step S803). Here, even if the two-dimensional barcode La is read by a third-party user terminal other than the user terminal 10a of the delivery requester and the user terminal 10b of the delivery destination, the registered screen G2 may be displayed. Also, if the two-dimensional barcode La is read by the user terminal when the delivery destination information has not been registered, since the delivery destination information is not registered for the delivery note identification information, an unregistered screen indicating that the delivery destination information has not been registered may be displayed as the response screen.

[0078] On the registered screen G2, a message such as "The destination has already been registered for this invoice identification information." may be displayed. This makes it possible to check whether the invoice L is unused or has already started being used. Also, such a message screen notifying that the destination has already been registered may be displayed when a request is made from any of the user terminals 10a, 10b, or a third-party user terminal during the period after the destination information has been registered for the invoice identification information and before the acceptance information has been registered for the invoice identification information. As a case where the two-dimensional barcode La is read by the destination user terminal 10b before the acceptance information is registered, for example, there is a case where the user who requests the delivery and the destination user are the same.

[0079] Also, after the acceptance information is registered, when the two-dimensional barcode La is read by the user terminal 10b and the URL based on the general information 110 is accessed (step S804), the registered screen G3 is displayed. The registered screen G3 is a registration content confirmation screen that includes the destination information and the delivery request source information. The registration content confirmation screen may also be displayed including a message such as "The destination has already been registered for this invoice identification information."

[0080] After the acceptance information is registered, when the goods are delivered to the destination user by the delivery company, the destination user receives the goods and reads the two-dimensional barcode La of the invoice L attached to the goods using the user terminal 10b. As a result, the registration content confirmation screen is displayed on the display screen of the user terminal 10b. If the recipient user has previously registered, they can log in from the web service or application program of the delivery service, refer to the status screen where the list of packages addressed to them is displayed, and perform an operation input indicating the completion of receipt for the received package, thereby notifying the core system of the delivery company of the receipt completion. When the fact of receipt completion is notified from the user terminal 10b to the core system of the delivery company, a "received" notification may be sent from the core system of the delivery company to the delivery management server 30, and the status stored in the storage unit 302 of the delivery management server 30 may be updated to "received".

[0081] On the other hand, when the two-dimensional barcode La is read by the delivery person terminal 50 (step S850), the delivery person terminal 50a extracts the shipping note identification information and the overall information 130 by interpreting the two-dimensional barcode La, and accesses the URL indicated by the extracted overall information 130 by specifying the shipping note identification information as a parameter. Here, the access destination indicated by the overall information 130 is the delivery management server 30. In addition, although the above general information 110 has been described in the case of being information indicating the connection destination, the general information 110 may also include encryption information for encrypting the recipient information in addition to the information indicating the connection destination. The user terminal 10 reads the two-dimensional barcode La, extracts the URL and the encryption information, which are the connection destination information included in the general information 110, encrypts the shipping note identification information using the encryption information, and then specifies it as a parameter and accesses the extracted URL. The delivery management server 30 may obtain the recipient identification information by decrypting the encrypted parameter added to the URL when accessed from the user terminal 10. The encryption information may be any information that can encrypt the shipping note identification information, such as information for hashing the shipping note identification information, information specifying the encryption method for encrypting the shipping note identification information, key information for encrypting the shipping note identification information, etc. Thereby, it is possible to prevent the shipping note identification information from being peeked at on the communication path, and it is possible to improve security.

[0082] When the delivery management server 30 is accessed to the URL based on the overall information 130 with the bill identification information specified as a parameter from the delivery person terminal 50, it transmits the data of the response screen based on the response corresponding to this access to the delivery person terminal 50 (step S851), and causes the response screen (reference G4) to be displayed on the display screen of the delivery person terminal 50.

[0083] Here, the response corresponding to the access may be, for example, either a response for connecting to another system or a response based on the information stored in the delivery management server 30.

[0084] The response for connecting to another system may be content for specifying the connection destination for accessing the server of the core system provided by the delivery company to which the delivery person in charge belongs. In this case, when the connection destination for accessing the server of the core system is specified, the delivery person terminal 50 can access the core system by accessing the specified connection destination. Also, when accessing the core system, the delivery person terminal 50 can also cause any process in the various management menus provided by the core system to be executed by specifying the bill identification information.

[0085] On the other hand, the response based on the information stored in the delivery management server 30 may be content for displaying a screen including the delivery destination information registered for the delivery destination identification information and the status indicating the delivery status of the package. In this case, the delivery person terminal 50 can confirm the delivery destination, status, etc. of the package with the bill L by reading the two-dimensional barcode La of the bill L.

[0086] According to the above-described other embodiment (Part 1), by using one two-dimensional barcode, different display screens can be respectively displayed on the user terminals 10a and 10b, third-party user terminals, and the delivery terminals 50 such as the collection driver, delivery driver, sorting staff, and luggage reception staff. As a result, since the user terminal 10 and the delivery terminal 50 can use a common two-dimensional barcode, the number of two-dimensional barcodes attached to the delivery note L can be prevented from increasing, and thus the area for attaching the two-dimensional barcode on the main surface of the delivery note L can be prevented from increasing.

[0087] ≪Other Embodiment (Part 2)≫ In the above-described other embodiment (Part 1), the case where one two-dimensional barcode La is attached to one delivery note L and the one two-dimensional barcode La can be read and interpreted from either the user terminal 10 or the delivery terminal 50 was described. In this other embodiment (Part 2), a plurality of two-dimensional barcodes are provided on one delivery note L. Among the plurality of two-dimensional barcodes, the first two-dimensional barcode can be read and interpreted by the user terminal 10, and the second two-dimensional barcode can be read and interpreted by the delivery terminal 50.

[0088] FIG. 14 is a diagram showing an example of the appearance of a delivery note L1 with a plurality of two-dimensional barcodes attached. This delivery note L1 has a part common to the delivery note L shown in FIG. 2, but a two-dimensional barcode Lf is added. When a plurality of two-dimensional barcodes are attached to one delivery note L1, for example, the two-dimensional barcode La may be used as the first two-dimensional barcode, and the two-dimensional barcode Lf may be used as the second two-dimensional barcode.

[0089] The two-dimensional barcode La can be read by any of the user terminals 10a of the delivery requester, the user terminal 10b of the delivery destination, or the user terminal of a user different from the delivery requester user and the delivery destination user, and the read two-dimensional barcode La can be interpreted. The two-dimensional barcode La may or may not be readable and interpretable by the delivery person terminal 50.

[0090] The two-dimensional barcode Lf can be read by the delivery person terminal 50, and the read two-dimensional barcode Lf can be interpreted. Even if the two-dimensional barcode Lf can be photographed by the user terminal 10, it will not be interpreted.

[0091] Here, the URL included in the two-dimensional barcode La may be a URL based on the general information 110 as in the above-described other embodiment (No. 1). In addition to the URL based on the general information 110, it may also include encrypted information. Also, the URL included in the two-dimensional barcode Lf may be a URL based on the overall information 130 as in the above-described other embodiment (No. 1). In this case, the delivery note L and the delivery note L1 differ in whether the two-dimensional barcode is one or plural, but the operation of the delivery management server 30 can be the same as that of the above-described other embodiment (No. 1). Also, although the URLs indicated by the two-dimensional barcode La and the two-dimensional barcode Lf are different, the servers to be connected are both the same delivery management server 30.

[0092] When the shipping note L1 is used in this way, when the user of the delivery requester sends a package, among the two-dimensional barcode La and the two-dimensional barcode Lf attached to the shipping note L1, the user terminal 10a reads the two-dimensional barcode La. If the user terminal 10a reads the two-dimensional barcode Lf, the two-dimensional barcode Lf is not interpreted. When the two-dimensional barcode Lf is read by the user terminal 10a, the two-dimensional barcode Lf may not be interpreted and a message such as "Please read the two-dimensional barcode for the customer" may be displayed.

[0093] When the two-dimensional barcode La is read by the user terminal 10a, the user terminal 10a interprets the two-dimensional barcode La, extracts the shipping note identification information and the URL corresponding to the two-dimensional barcode La, specifies the extracted shipping note identification information as a parameter for the extracted URL, and transmits it to the delivery management server 30. The first acquisition unit 303 of the delivery management server 30 acquires the shipping note identification information based on the access from the user terminal 10a. Then, the delivery management server 30 transmits the registration screen data to the user terminal 10a. As a result, it becomes possible to register the delivery destination information in the user terminal 10a, and the delivery management server 30 stores the delivery destination information and the shipping note identification information in association with each other in the storage unit 302.

[0094] When the delivery destination information is registered, the package is handed over to the delivery company, and the two-dimensional barcode Lf attached to the shipping note L1 is read by the delivery person terminal 50, the delivery person terminal 50 extracts the shipping note identification information and the URL from the two-dimensional barcode Lf, specifies the extracted shipping note identification information as a parameter, and accesses the extracted URL to connect to the delivery management server 30. As a result, the delivery management server 30 stores the acceptance information in association with the delivery destination identification information and the delivery destination information in the storage unit 302. Then, the delivery management server 30 causes the delivery person terminal 50 to display a response screen based on a response corresponding to the access by the delivery person terminal 50.

[0095] After the delivery management server 30 acquires the invoice identification information by the first acquisition unit 303, when the two-dimensional barcode La is read by the user terminal 10a of the delivery requester, a registered screen is displayed as in the above-described other embodiment (Part 1). Also, when it is read by the user terminal 10b of the delivery destination, a registration content confirmation screen may be displayed on the user terminal 10b as in the above-described other embodiment (Part 1). Also, when the two-dimensional barcode Lf is read by the delivery person terminal 50, the delivery management server 30 displays a response screen based on a response according to the access to the delivery management server 30. The response according to the access may be either a response for connecting to another system or a response based on the information stored in the delivery management server 30, as in the above-described other embodiment (Part 1).

[0096] According to the above-described other embodiment (Part 2), the two-dimensional barcode that can be interpreted by the user terminal 10 and the two-dimensional barcode that can be interpreted by the delivery person terminal 50 are separately attached to the invoice L1. As a result, the user of the user terminal 10 and the delivery person of the delivery person terminal 50 can use the two-dimensional barcodes separately.

[0097] Also, according to the above-described other embodiments (Part 1) and (Part 2), the user terminal 10 and the delivery person terminal 50 access the same delivery management server 30 by interpreting the two-dimensional barcode. As a result, either the user terminal 10 or the delivery person terminal 50 can be made to access the delivery management server 30 once after reading the two-dimensional barcode. Thus, regarding which screen to transition to for the user terminal 10 and the delivery person terminal 50, it can be aggregated and managed in the delivery management server 30. Therefore, even if the screen to transition to changes, it can be managed collectively in the delivery management server 30, so that it is possible to flexibly respond to the change in the transition destination.

[0098] 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.

[0099] At least one of the user terminal 10, the delivery management server 30, the invoice printing server 40, and the deliverer terminal 50 in the above-described embodiment may be implemented by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize it. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable recording medium" also includes, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, a medium that dynamically holds a program for a short time, and a volatile memory inside a computer system that becomes a server or a client in that case, which holds a program for a certain period of time. Also, the above program may be for realizing a part of the aforementioned functions, and may further be realizable in combination with a program already recorded in the computer system for the aforementioned functions, or may be realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0100] As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and designs and the like within the scope not departing from the gist of the present invention are also included.

Explanation of Reference Numerals

[0101] 10, 10a, 10b User terminal 20 POS terminal 30 Delivery management server 40 Invoice printing server 41 Invoice printing device 50, 50a, 50b Delivery person terminal 55, 55a, 55b Mobile printer 301 Communication unit 302 Storage unit 303 First acquisition unit 304 Second acquisition unit 305 First processing unit 306 Second processing unit 307 Transmission unit 308 Control unit NW Network S Delivery system

Claims

1. A first acquisition unit that acquires the invoice identification information transmitted from the user terminal, where the invoice identification information printed on the invoice placed at the base is read by the user terminal of the user who is the delivery requester; A second acquisition unit that acquires destination information capable of specifying a destination based on an operation input of the user from the user terminal; A first processing unit that stores the acquired invoice identification information and the acquired destination information in a storage unit; A second processing unit that, in response to the invoice identification information on the invoice attached to the package to be delivered being read by the delivery person terminal of the delivery person, stores, in association with the destination information in the storage unit, acceptance information indicating that the package has been accepted for the invoice identification information transmitted from the delivery person terminal A delivery system having the above.

2. A first acquisition unit that acquires the invoice identification information transmitted from the user terminal, where the invoice identification information printed on the invoice placed at the base is read by the user terminal of the user who is the delivery requester; A second acquisition unit that acquires destination information capable of specifying a destination based on an operation input of the user from the user terminal; A first processing unit that stores the acquired invoice identification information and the acquired destination information in a storage unit; A transmission unit that transmits, to the terminal that read the invoice identification information, the destination information corresponding to the read invoice identification information, in response to the invoice identification information on the invoice attached to the package to be delivered being read by the delivery person terminal of the delivery person or the user terminal of the user at the destination of the package A delivery system having the above.

3. Causing information based on the destination information to be printed by a printing device connected to the delivery person terminal The delivery system according to Claim 1 or Claim 2.

4. The user who is the delivery requester is an ordinary consumer. The delivery system according to Claim 1 or Claim 2.

5. The invoice is attached with a two-dimensional barcode, The two-dimensional barcode Includes the invoice identification information and connection destination information, The connection destination information Includes general information that can be interpreted by both the user terminal of any one of the user of the delivery requester, the user at the destination, and a user different from the delivery requester and the user at the destination, and the delivery person terminal, The second processing unit is provided in a delivery management server, The delivery system After the sending document identification information is acquired by the first acquisition unit, when the two-dimensional barcode is read by the user terminal, by accessing the connection destination based on the result of interpreting the general information, a response screen corresponding to the registration status registered for the sending document identification information is displayed on the user terminal that is the reading source. when the two-dimensional barcode is read by the delivery person terminal, a response screen based on the response corresponding to accessing the delivery management server using the concealed information that can be acquired according to the fact that the reading terminal is the delivery person terminal is displayed on the delivery person terminal that is the reading source. The delivery system according to claim 1.

6. The concealed information is included in the connection destination information of the two-dimensional barcode or can be acquired from the delivery management server based on information that can be provided from the delivery person terminal. The delivery system according to claim 5.

7. When the first two-dimensional barcode attached to the sending document is read by the user terminal, the sending document identification information corresponding to the first two-dimensional barcode is extracted. After the extracted sending document identification information is transmitted from the user terminal to the delivery management server having the second processing unit, in response to the delivery destination identification information extracted in response to the second two-dimensional barcode attached to the sending document and readable only by the delivery person terminal being transmitted from the delivery person terminal to the delivery management server, acceptance information indicating that the package has been accepted for the sending document identification information is stored in association with the delivery destination information in the storage unit. The connection destination for transmitting the sending document identification information indicated by the first two-dimensional barcode and the second two-dimensional barcode is the same delivery management server. When the first two-dimensional barcode is read by the user terminal, a response screen indicating the registration status according to whether the sending document identification information and the delivery destination information are stored in the storage unit is displayed on the user terminal based on whether the sending document identification information has been acquired by the first acquisition unit. When the second two-dimensional barcode is read by the delivery person terminal, a response screen based on the response corresponding to accessing the delivery management server is displayed. The delivery system according to claim 1.

8. A response screen based on a response corresponding to accessing the delivery management server includes content for specifying a connection destination for accessing a server of a core system provided by a delivery company to which the delivery person belongs, or includes delivery destination information registered for the delivery destination identification information and a status indicating the delivery status of the package The delivery system according to any one of claims 5 to 7.

9. The delivery note identification information printed on the delivery note placed at the base is read by a user terminal of a user who is the delivery requester, and the delivery note identification information transmitted from the user terminal is acquired. Delivery destination information capable of specifying a delivery destination based on the operation input of the user is acquired from the user terminal. The acquired delivery note identification information and the acquired delivery destination information are stored in a storage unit. In response to the delivery note identification information of the delivery note attached to the package to be delivered being read by the delivery person's delivery terminal, acceptance information indicating that the package has been accepted is stored in association with the delivery destination information in the storage unit for the delivery note identification information transmitted from the delivery terminal. Delivery management method.

10. The delivery note identification information printed on the delivery note placed at the base is read by a user terminal of a user who is the delivery requester, and the delivery note identification information transmitted from the user terminal is acquired. Delivery destination information capable of specifying a delivery destination based on the operation input of the user is acquired from the user terminal. The acquired delivery note identification information and the acquired delivery destination information are stored in a storage unit. In response to the delivery note identification information of the delivery note attached to the package to be delivered being read by the delivery person's delivery terminal or the user terminal of the delivery destination of the package, the delivery destination information corresponding to the read delivery note identification information is transmitted to the terminal that read the delivery note identification information. Delivery management method.

Images