Information processing device, information processing method, information processing system, and program

Abstract

To improve usability. [Solution] The system comprises a storage means capable of storing information relating to the delivery of packages, and an update control means capable of updating the information stored in the storage means, and when updating the information stored in the storage means for one package, the update control means is capable of updating the information stored in the storage means for the other packages so that the updated specified information for the one package is the same as the updated specified information for the other packages.

Description

[Technical Field]

[0001] The present invention relates to an information processing device and an information processing method. , love Information Processing System , and programs Regarding. [Background technology]

[0002] BACKGROUND ART Conventionally, a system for managing a logistics process in which cargo provided by a shipper is delivered to a customer is known (see Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] In the course of thorough research into logistics management, the inventors came to the conclusion that there may be room for improving the usability of logistics operations.

[0005] The present invention has been made in view of the above-mentioned circumstances, and provides an information processing device and an information processing method that can improve usability. , love Information Processing System , and programs The purpose is to provide the following. [Means for solving the problem]

[0006] In order to achieve the above object, the present invention provides the following information processing device, information processing method, information processing system, and program. (I) a storage means capable of storing delivery timing information relating to the timing of delivery of a package and predetermined package-related information different from the delivery timing information; receiving means capable of receiving package identification information for identifying a package; update control means for updating the delivery timing information stored in the storage means; After the delivery timing information for one package and the delivery timing information for another package are stored in the storage means, when the predetermined package-related information stored in the storage means for the one package is the same as the predetermined package-related information stored in the storage means for the other package, the update control means: receiving the package identification information by the receiving means in response to a user's operation for designating package identification information corresponding to the package; When updating the delivery timing information stored in the storage means for the one package, By identifying the package identification information associated with the package identification information corresponding to the one package as package identification information corresponding to the other package, The delivery timing information stored in the storage means for the other parcels can be updated so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcels are the same. An information processing device characterized by 。 (II) 1. An information processing method for use in package delivery, the method being executed by at least one computer, comprising: receiving package identification information for identifying the package; After the delivery timing information for one package and the delivery timing information for another package are stored in the storage means, if the predetermined package-related information stored in the storage means for the one package is the same as the predetermined package-related information stored in the storage means for the other package, receiving the package identification information in response to a user's operation to designate package identification information corresponding to the package; When updating the delivery timing information stored in the storage means for the one package, By identifying the package identification information associated with the package identification information corresponding to the one package as package identification information corresponding to the other package, a step of updating the delivery timing information stored in the storage means for the other parcel so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcel become the same; and, Including, An information processing method characterized by 。 (III) a storage means capable of storing delivery timing information relating to delivery timing of a package and predetermined package-related information different from the delivery timing information; receiving means capable of receiving package identification information for identifying a package; update control means for updating the delivery timing information stored in the storage means; After the delivery timing information for one package and the delivery timing information for another package are stored in the storage means, when the predetermined package-related information stored in the storage means for the one package is the same as the predetermined package-related information stored in the storage means for the other package, the update control means: receiving the package identification information by the receiving means in response to a user's operation for designating package identification information corresponding to the package; When updating the delivery timing information stored in the storage means for the one package, By identifying the package identification information associated with the package identification information corresponding to the one package as package identification information corresponding to the other package, The delivery timing information stored in the storage means for the other parcels can be updated so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcels are the same. An information processing system characterized by 。 (IV) A system for delivering packages, comprising: receiving means capable of receiving package identification information for identifying the package; A program for functioning as an update control means capable of updating delivery timing information stored in a storage means, After the delivery timing information for one package and the delivery timing information for another package are stored in the storage means, when the predetermined package-related information stored in the storage means for the one package is the same as the predetermined package-related information stored in the storage means for the other package, the update control means receiving the package identification information by the receiving means in response to a user's operation for designating package identification information corresponding to the package; When updating the delivery timing information stored in the storage means for the one package, By identifying the package identification information associated with the package identification information corresponding to the one package as package identification information corresponding to the other package, The delivery timing information stored in the storage means for the other parcels can be updated so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcels are the same. A program characterized by 。

[0007] (1) A storage means (e.g., storage unit 111) capable of storing information related to package delivery; update control means for updating the information stored in the storage means; When updating information stored in the storage means for one parcel, the update control means is capable of updating information stored in the storage means for the other parcel so that the updated predetermined information (e.g., expected delivery date information and delivery status information) for the one parcel becomes the same as the updated predetermined information for the other parcel. 1. An information processing device comprising:

[0008] (2) When updating information stored in a storage means (e.g., storage unit 111) for one package, the method includes a step of updating information stored in the storage means for the other package so that the updated predetermined information (e.g., expected delivery date information and delivery status information) for the one package is the same as the updated predetermined information for the other package. An information processing method comprising:

[0009] (3) a storage means (e.g., storage unit 111) capable of storing information related to package delivery; update control means for updating the information stored in the storage means; When updating information stored in the storage means for one parcel, the update control means is capable of updating information stored in the storage means for the other parcel so that the updated predetermined information (e.g., expected delivery date information and delivery status information) for the one parcel becomes the same as the updated predetermined information for the other parcel. An information processing system comprising: [Effects of the Invention]

[0010] According to the present invention, usability can be improved. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an overview of a logistics management system. [Figure 2]FIG. 2 is a functional block diagram of a logistics management server. [Figure 3] FIG. 2 is a functional block diagram of an administrator terminal. [Figure 4] FIG. 2 is a functional block diagram of a driver terminal. [Figure 5] FIG. 2 is a functional block diagram of a shipper server. [Figure 6] 10 is a flowchart showing the processing performed by the logistics management server when receiving package information and the processing performed by the shipper server when transmitting package information. [Figure 7] 10 is a flowchart showing a delivery application execution process. [Figure 8] FIG. 10 is a diagram illustrating an example of a screen displayed when a delivery app is executed. [Figure 9] 10 is a flowchart showing a process at the time of scan selection on the driver terminal side and a process at the time of scan selection on the logistics management server side. [Figure 10] 10 is a flowchart showing a delivery status update related process when scan is selected on the driver's terminal side and a delivery status update related process when scan is selected on the logistics management server side. [Figure 11] 10 is a flowchart showing a process of accepting a transition destination status selection operation. [Figure 12] FIG. 10 is a diagram illustrating an example of an action selection screen when a product is not yet shipped. [Figure 13] FIG. 10 is a diagram showing an example of a screen for selecting an action when receipt of goods is confirmed. [Figure 14] FIG. 10 is a diagram showing an example of a takeout action selection screen. [Figure 15] 1A is a diagram showing an example of a transition process screen for a manager, and FIG. 1B is a diagram showing an example of a transition process screen for a shipper. [Figure 16] FIG. 10 is a diagram illustrating an example of an absence action selection screen. [Figure 17] 10 is a flowchart showing a continuous scan-related process on the driver terminal side and a continuous scan-related process on the logistics management server side. [Figure 18]10 is a flowchart showing a continuous scan-related process on the driver terminal side and a continuous scan-related process on the logistics management server side. [Figure 19] FIG. 10 is a diagram showing an example of a delivery status update completion screen. [Figure 20] FIG. 10 is a diagram showing an example of a delivery status update completion screen. [Figure 21] FIG. 10 is a diagram showing an example of a screen during a continuous scan mode. [Figure 22] FIG. 10 is a diagram showing an example of a screen during a continuous scan mode. [Figure 23] 10 is a flowchart showing a map selection process. [Figure 24] 10 is a flowchart showing pin display related processing. [Figure 25] FIG. 10 is a diagram showing an example of a screen displayed when a map selection instruction is input. [Figure 26] FIG. [Figure 27] 10 is a flowchart showing a pin information acquisition process. [Figure 28] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 29] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 30] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 31] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 32] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 33] FIG. 10 is a diagram showing an example of a screen displayed when a pin selection instruction is input. [Figure 34] 10 is a flowchart showing delivery route related processing. [Figure 35] 10 is a flowchart showing delivery-related processing. [Figure 36] 10 is a flowchart showing an unloading process. [Figure 37] FIG. 10 is a diagram showing an example of a screen during a delivery scan mode. [Figure 38] 10 is a flowchart showing a delivery completion related process on the driver terminal side and a delivery completion related process on the logistics management server side. [Figure 39] FIG. 10 is a diagram illustrating an example of a delivery action selection screen. [Figure 40] FIG. 10 is a diagram showing an example of a screen for inputting a receiving instruction. [Figure 41] FIG. 10 is a diagram illustrating an example of a receipt completion screen. [Figure 42] FIG. 10 is a diagram showing an example of a screen for inputting a bring-back instruction. [Figure 43] FIG. 10 is a diagram showing an example of a screen for inputting a bring-back instruction. [Figure 44] 10 is a flowchart showing remaining delivery processing. [Figure 45] 10 is a flowchart showing a process when receiving package information. [Figure 46] 10 is a flowchart showing a grouping process during data linkage. [Figure 47] 10 is a flowchart showing a process for transmitting information about luggage held on the driver terminal side. [Figure 48] 10 is a flowchart showing pin display related processing. [Figure 49] 10 is a flowchart showing a departure-related process. [Figure 50] FIG. 10 is a diagram showing an example of a screen displayed when a map selection instruction is input. [Figure 51] FIG. 10 is a diagram illustrating an example of a leftover confirmation message. [Figure 52] FIG. 10 is a diagram illustrating an example of a leftover confirmation message. [Figure 53] 10 is a flowchart showing a delivery date and time change process. [Figure 54] FIG. 10 is a diagram illustrating an example of a service menu top screen. [Figure 55] FIG. 10 is a diagram showing an example of a slip number input screen. [Figure 56] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 57] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 58] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 59] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 60] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 61] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 62] FIG. 10 is a diagram showing an example of a delivery date and time change screen. [Figure 63] FIG. 10 is a diagram illustrating an example of a date and time change completion screen. DETAILED DESCRIPTION OF THE INVENTION

[0012] First Embodiment The logistics management system 10 according to the first embodiment will be described below.

[0013] [Logistics Management System] FIG. 1 is a diagram showing an overview of a logistics management system.

[0014] 1, the logistics management system 10 includes a logistics management server 20, an administrator terminal 30, and a driver terminal 40. The logistics management system 10 manages the logistics process in which packages provided by shippers (e.g., products purchased at a store or an e-commerce site) are delivered to customers (e.g., product purchasers).

[0015] The logistics management server 20 is a server managed by an administrator. The administrator terminal 30 is a terminal device operated by the administrator. The administrator uses the administrator terminal 30 to perform various management tasks to ensure smooth operation of the logistics management system 10. The driver terminal 40 is a terminal device operated by a driver. In the logistics process managed by the logistics management system 10, the driver loads cargo onto a vehicle (e.g., a truck) at a logistics base (warehouse) and drives the vehicle to deliver the cargo to a customer (e.g., a delivery address such as a home or office). The shipper side server 50 is a server managed by the shipper.

[0016] The manager may be a person (e.g., an employee of company A) who belongs to the same business entity as the shipper (e.g., company A that sells the product), or a person (e.g., an employee of company A) who belongs to a business entity different from the shipper (e.g., company B that is outsourced by company A to perform delivery operations). The manager who manages the logistics management server 20 and the manager who operates the manager terminal 30 may be the same person or different people. The driver may be a person (e.g., an employee of company B) who belongs to the same business entity as the manager, or a person (e.g., an employee of company C that is outsourced by company B, or a sole proprietor) who belongs to a business entity different from the business entity.

[0017] For example, if the administrator belongs to the same business entity as the shipper, the shipper-side server 50 can be a component of the logistics management system 10, and if the administrator belongs to a business entity different from the shipper, the shipper-side server 50 can be a non-component of the logistics management system 10. Furthermore, the logistics management server 20 and the shipper-side server 50 may be configured as a single server, or may be configured as separate servers. The logistics management system 10 can basically be configured as a system having a function for managing the delivery process of packages (delivery management function), but it may also have a function for managing the processes within the warehouse from arrival to shipment in addition to the delivery management function (warehouse management function).

[0018] The delivery management function includes, for example, a function for generating a delivery plan (for example, optimizing the order in which packages are delivered and the allocation of packages to drivers, taking into consideration the specified delivery date and time, the delivery address, the amount of packages that can be loaded into a vehicle, etc.), a function for determining a delivery route (for example, calculating the shortest and most efficient route by using map information and traffic information), a function for visualizing the delivery status of packages (for example, the current location of the package, whether packages with specified delivery dates and times are being delivered smoothly, etc.), a function for updating and managing the delivery status of packages (for example, a state in which the driver is taking the package out of the warehouse (in transit), a state in which the package has already been delivered, etc.), a function for managing information about customers (package delivery destinations) (customer information (for example, information indicating name, address, and contact information)), a function for managing the distribution of packages, etc. These include the ability to notify customers of delivery status (e.g., estimated arrival time) and delivery status, generate documents (e.g., delivery slips, invoices, receipts, etc.), optimize the process of loading cargo onto vehicles (e.g., loading efficiency), optimize delivery costs (e.g., calculate the costs for each delivery route taking into account fuel costs and labor costs, etc.), analyze delivery data to visualize operational efficiency (e.g., quantify delivery costs, delay rates, customer satisfaction, etc.) and output them as reports, efficiently manage delivery schedules and staffing based on demand forecasts, manage driver attendance and vehicle maintenance, set access rights for each manager or driver according to their role and protect information, and monitor for unauthorized access.

[0019] Warehouse management functions include, for example, the ability to check whether packages received at the warehouse match the order details, the ability to optimize package storage locations (for example, by allocating storage locations according to the frequency of product shipments), the ability to grasp package storage locations and inventory levels, the ability to compare recorded inventory levels with actual inventory levels, the ability to create picking lists, the ability to pick efficiently, the ability to inspect products before shipping, the ability to manage the progress of each task (receiving, shipping, inventory, etc.), the ability to manage worker schedules and support appropriate personnel allocation, the ability to perform quality checks and manage expiration dates (for products with expiration dates or expiry dates), the ability to analyze incoming and outgoing data to visualize operational efficiency and output the results as a report, the ability to visualize and optimize warehouse work costs and inventory storage costs, the ability to set access rights for each worker according to their role to protect information, and the ability to monitor unauthorized access.

[0020] The cargo (goods) to be delivered are not particularly limited, and the logistics processes of general consumer goods (e.g., food, beverages, household goods, daily necessities, cleaning supplies, cosmetics, etc.), frozen and refrigerated goods (e.g., frozen foods, fresh foods, dairy products, medicines that require temperature control, etc.), medicines and medical equipment (e.g., prescription drugs, medical equipment, reagents, vaccines, etc.), hazardous materials (e.g., gasoline, chemicals, paint, flammable gas, etc.), high-value products (e.g., precious metals, jewelry, watches, electronic devices, etc.), heavy and large items (e.g., construction materials, heavy machinery, automobiles, furniture, large home appliances, etc.), parcels and home delivery (e.g., online shopping purchases, parcels delivered to private homes, etc.), agricultural products (e.g., vegetables, fruits, grains, fresh flowers, etc.), industrial products and parts (e.g., automobile parts, electronic parts, machine parts, etc.), and special delivery items (e.g., biological tissue, blood products, animals, plants, etc.) can be managed by the logistics management system 10.

[0021] The administrator terminal 30 can be configured with an information processing device such as a general personal computer, laptop computer, smartphone, tablet terminal, etc. The driver terminal 40 can be configured with an information processing device such as a general personal computer, laptop computer, smartphone, tablet terminal, etc., as well as a dedicated barcode reader, etc. The logistics management server 20 can be configured with an information processing device such as a general personal computer, laptop computer, smartphone, tablet terminal, etc., as well as an on-premise server or cloud server, or a combination thereof. The shipper's server 50 can be configured with an information processing device such as a general personal computer, laptop computer, smartphone, tablet terminal, etc., as well as an on-premise server or cloud server, or a combination thereof.

[0022] FIG. 1 shows an example in which a personal computer is used as the administrator terminal 30 and a smartphone is used as the driver terminal 40. The application used in the administrator terminal 30 may be a dedicated application installed in the administrator terminal 30, or may be a web application that runs on an internet browser (for example, an application configured with a program using HTML language, JavaScript (registered trademark), etc.). Furthermore, the application (delivery application) used in the driver terminal 40 may be a dedicated application installed in the driver terminal 40, or may be a web application that runs on an internet browser (for example, an application configured with a program using HTML language, JavaScript (registered trademark), etc.). Note that, in the figure, multiple driver terminals 40 are provided, and only one administrator terminal 30 is shown, but of course, multiple administrator terminals 30 may also be provided.

[0023] The logistics management server 20 is capable of communicating with the administrator terminal 30, the driver terminal 40, and the shipper server 50 via the network N. As the network N, for example, the Internet using the communication protocol IP, as well as networks (data communication networks) such as an intranet, an extranet, a mobile communication network, a wide area network (WAN), a local area network (LAN), a metropolitan area network (MAN), and a satellite communication network can be adopted.

[0024] [Logistics management server] FIG. 2 is a functional block diagram of the logistics management server.

[0025] As shown in FIG. 2, the logistics management server 20 includes a control unit 110, a memory unit 111, and a communication unit 112. The control unit 110 controls the entire logistics management server 20. The memory unit 111 stores programs and data used when the control unit 110 executes processing based on the programs. The memory unit 111 also stores a package information management database 120, which includes a package information table 121. The communication unit 112 (network I / F (interface)) connects the logistics management server 20 to a network N and establishes communication with external devices.

[0026] The control unit 110 is configured, for example, by a CPU (Central Processing Unit) etc. The storage unit 111 is configured, for example, by a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a combination of these. The control unit 110 executes processing based on the programs stored in the storage unit 111, thereby realizing the functional configuration of the logistics management server 20.

[0027] The OS (operating system) plays an important role as the basic software of the logistics management server 20. The OS efficiently manages hardware resources and provides an environment in which application software and control programs can run smoothly. Specifically, the OS mediates between hardware components and programs by allocating resources, managing processes, operating the file system, and processing network communications, thereby improving the stability and efficiency of the logistics management server 20 as a whole.

[0028] The package information table 121 stores information (package information) about packages to be delivered. For example, the package information table 121 stores information (package number information) indicating a "slip number" (for example, 12 half-width characters corresponding to one package), information (customer management number information) indicating a "customer control number" (for example, 20 or less half-width alphanumeric characters corresponding to one package), information (waybill type information) indicating a "waybill type" (for example, one half-width character corresponding to one of "payment on delivery," "cash on delivery," "mail delivery," "cash on delivery," "delivery to a designated location," and "delivery by post"), information (waybill type information) indicating a "cool classification" (for example, "normal," "cool frozen," "frozen," "refrigerated," "freezer ... ", "Cool refrigerated", "Chilled" and "Security" (other than "Normal", it can only be specified if the "Way type" is either "Payment on delivery", "Cash on delivery" or "Payment on delivery") (Cool classification type information), "Scheduled shipping date" (for example, 10 half-width alphabetical characters in "YYYY / MM / DD") (Scheduled shipping date information), "Scheduled delivery date" (for example, 10 half-width alphabetical characters in "YYYY / MM / DD") (Scheduled delivery date information), Information indicating the delivery time slot (for example, four half-width digits corresponding to one of "No specification", "8:00-12:00", "12:00-14:00", "14:00-16:00", "16:00-18:00", "18:00-20:00", and "19:00-21:00") (delivery time slot information), information indicating the "delivery destination code" (for example, half-width alphanumeric characters of 20 characters or less) (delivery destination code information), information indicating the "delivery destination telephone number" (for example, half-width alphanumeric characters of 15 characters or less including hyphens) (delivery destination telephone number information), information indicating the "delivery destination postal code" (for example, eight characters including hyphens), Information indicating "shipping address" (for example, 100 characters or less of full-width or half-width characters indicating "prefecture," "city, ward, county, town, village," "block number, number") (shipping address information), information indicating "shipping apartment / condominium name" (for example, 100 characters or less of full-width or half-width characters indicating "apartment name" or "building name") (shipping apartment / condominium name information), information indicating "shipping name" (for example, 100 characters or less of full-width or half-width characters) (shipping name information), information indicating "shipping name (kana)" (for example,Information indicating "recipient name (kana) information" (100 characters or less, full-width or half-width characters), information indicating "title" (e.g., 4 characters or less, full-width or half-width characters) (title information), information indicating "sender code" (e.g., 20 characters or less, half-width alphanumeric characters) (sender code information), information indicating "sender phone number" (e.g., 15 characters or less, half-width numbers including hyphens) (sender phone number information), information indicating "sender postal code" (e.g., 8 characters, half-width numbers including hyphens) (sender postal code information), information indicating "sender address" (e.g., "prefecture", "city, ward, county, town, village", "block number", "number", "number", "number", "number", "address", "address information ... "Requester address information" (64 characters or less, full-width or half-width characters indicating "·number"), information indicating "Requester apartment / condominium" (for example, 32 characters or less, full-width or half-width characters indicating "apartment name" or "building name") (Requester apartment / condominium information), information indicating "Requester name" (for example, 32 characters or less, full-width or half-width characters) (Requester name information), information indicating "Requester name (kana)" (for example, 50 characters or less, full-width or half-width characters) (Requester name (kana) information), information indicating "Product name" (for example, 50 characters or less, full-width or half-width characters) (Product name information), "Article ( For example, information indicating "full-width or half-width characters of 200 characters or less" (article information), information indicating "redelivery deadline" (for example, 10 half-width alphabetic characters indicated in "YYYY / MM / DD") (redelivery deadline information), information indicating "package size" (for example, half-width numbers of 2 characters or less) (package size information), information indicating "number of parcels" (for example, half-width numbers of 2 characters or less) (number of parcels information), information indicating "delivery status" (for example, half-width numbers of 2 characters or less) (delivery status information), information indicating "geotag" (for example, latitude and longitude corresponding to "delivery address") (geotag information), information), "status update date and time" (for example, information indicating the date and time when the delivery status was updated) (status update date and time information), information indicating the "delivery center" (for example, a warehouse that receives packages shipped from the shipper and is responsible for storing and delivering said packages) (delivery center information), information indicating the "confirmed receipt date and time" (for example, the date and time when the delivery status was updated to "confirmed receipt") (confirmed receipt date and time information), information indicating the "final delivery date and time" (for example, the date and time when the delivery status was updated to "delivery completed") (final delivery date and time information), "final delivery location" (for example,The table is configured to be able to store, in association with one another, information indicating the location (latitude and longitude) of the driver terminal 40 when the delivery status was updated to "delivery completed" (final delivery location information), information indicating the "final delivery person" (e.g., the name of the driver who completed delivery of the package) (final delivery person information), information indicating the "final delivery company" (e.g., the name of the company to which the driver who completed delivery of the package belongs) (final delivery company information), information indicating the "update date and time" (e.g., the date and time when the information stored in the package information table 121 was last updated) (update date and time information), etc.

[0029] A "requester" is a party that requests a delivery company to deliver a package, and a typical requester is a shipper. For example, a shipper (e.g., Company A selling a product) manages each package by assigning a "customer management number" as an identification number (package ID) to uniquely identify each package, and a delivery company (e.g., Company B entrusted with delivery operations by Company A) manages each package by assigning a "slip number" as an identification number (package ID) to uniquely identify each package. A "delivery status" corresponds to the progress of the package delivery and is updated as the delivery process progresses. In this embodiment, the delivery statuses include "not shipped," "confirmed receipt," "warehouse storage," "specified date storage," "take-out," "delivery completed," "absent," "rejected receipt," "return," "under investigation," "warehouse storage (return)," "specified date storage (return)," "package accident," "handover," and "return instruction." These delivery statuses will be described in detail later. When the delivery process progresses for a package to be delivered due to a change in the status of the package, the control unit 110 updates the delivery status information corresponding to the package's slip number information in the package information table 121 from information indicating one delivery status to information indicating another delivery status. In this specification, an "update" of the delivery status (delivery status information) may be expressed as a "transition" or "shift" of the "delivery status."

[0030] The configuration of the package information management database 120 is not particularly limited, and may be configured, for example, to include multiple tables (package information table 121 and other tables) and store the above-mentioned package information in separate tables. For example, delivery status information may be stored in a table separate from package information table 121 in association with slip number information. The package information management database 120 may also be a data server connected to an information communication network such as network N, separate from the logistics management server 20.

[0031] The logistics management server 20 can be configured as a physical server, a virtual server, or a combination of these, and its specifications are not limited to specific hardware or software. A dedicated server installed in an on-premises environment can be used as the physical server, and can be configured with an emphasis on fault tolerance and high performance. A virtual server can be configured with flexible scalability using a cloud environment, enabling efficient operation through dynamic resource allocation. Furthermore, a hybrid configuration (combining on-premises physical servers with virtual servers on the cloud) or a multi-cloud configuration (using multiple cloud service providers) can also be adopted. This allows for an optimal design based on the user's operational, cost, and performance requirements. The logistics management server 20 can also change the type of operating system and middleware supported depending on the selected environment.

[0032] The logistics management server 20 can serve as a web server, an application server, a database server, and so on. These roles can be integrated into a single physical or virtual server, or they can be distributed across multiple dedicated servers. In either case, the basic functions of the logistics management server 20 remain the same, enabling stable and efficient logistics management regardless of the selected infrastructure environment. Such a logistics management server 20 can be called an "information processing device." In this context, the information processing device refers to the entire system in which a web server, application server, database server, and so on work together to achieve a specific information processing function. In this specification, the term "device" is used to refer to the physical hardware, virtual environment, or a combination thereof that constitutes the entire system or part of it.

[0033] [Administrator's terminal] FIG. 3 is a functional block diagram of the administrator terminal.

[0034] 3, the administrator terminal 30 includes a control unit 130, a storage unit 131, a display unit 132, an operation input unit 133, and a communication unit 134. The control unit 130 is configured, for example, by a CPU or the like, and controls the entire administrator terminal 30. The storage unit 131 is configured, for example, by a ROM, RAM, HDD, or SSD, or a combination of these, and stores programs and data used when the control unit 130 executes processing based on the programs. The control unit 130 executes processing based on the programs stored in the storage unit 131, thereby realizing the functional configuration of the administrator terminal 30.

[0035] The display unit 132 is configured, for example, by a display (such as a liquid crystal display or an organic EL display) and displays various information. The operation input unit 133 is configured, for example, by a keyboard, a mouse, a capacitive touch panel, etc. and accepts operation inputs from the administrator. For example, if a smartphone is used as the administrator terminal 30, the display unit 132 and the operation input unit 133 can be configured by a touch panel LCD. The communication unit 134 (network I / F (interface)) connects the administrator terminal 30 to the network N and establishes communication with external devices.

[0036] [Driver's terminal] FIG. 4 is a functional block diagram of the driver terminal.

[0037] 4, the driver terminal 40 includes a control unit 140, a storage unit 141, a display unit 142, an operation input unit 143, an imaging unit 144, and a communication unit 145. The control unit 140 is configured, for example, by a CPU or the like, and controls the entire driver terminal 40. The storage unit 141 is configured, for example, by a ROM, a RAM, an HDD, an SSD, or a combination of these, and stores programs and data used when the control unit 140 executes processing based on the programs. The control unit 140 executes processing based on the programs stored in the storage unit 141, thereby realizing the functional configuration of the driver terminal 40.

[0038] The display unit 142 is configured, for example, by a display (such as a liquid crystal display or an organic EL display) and displays various information. The operation input unit 143 is configured, for example, by a keyboard, a mouse, a capacitive touch panel, or the like, and accepts operation inputs from participants. For example, if a smartphone is used as the driver terminal 40, the display unit 142 and the operation input unit 143 can be configured by a touch panel LCD. The imaging unit 144 is configured, for example, by a camera (such as a CMOS camera or a CCD camera) and captures images of the surrounding environment of the driver terminal 40. The communication unit 145 (network I / F (interface)) connects the driver terminal 40 to the network N and establishes communication with external devices.

[0039] By bringing driver terminal 40 close to the package to be delivered, the driver can capture an image of any area included in the delivery label using imaging unit 144. The delivery label is a label (sticker) that is affixed to the package, and is printed with information necessary for the driver to deliver the package (e.g., "slip number," "waybill type," "refrigerated classification," "expected delivery date," "delivery time zone," "redelivery deadline," "number of units," "item name," "name of item," "name, address, and contact information of the recipient (delivery destination) (e.g., "recipient name," "recipient postal code," "recipient address," "recipient phone number," etc.)," ​​name, address, and contact information of the "sender" (shipper) (e.g., "sender name," "sender postal code," "sender address," "sender phone number," etc.), two-dimensional code, etc.).

[0040] The two-dimensional code is an encoded version of package information (e.g., a QR code (registered trademark)). In this embodiment, the two-dimensional code includes a "slip number." However, the two-dimensional code can be configured to include any package information (e.g., a "shipping address" or "shipping name" in addition to the "slip number"). A barcode may be printed on the shipping label in addition to (or instead of) the two-dimensional code. Any package information can also be included in the barcode. The barcode may include the same information as the two-dimensional code (e.g., a "slip number"), or it may include information different from the information included in the two-dimensional code (e.g., a "serial number"). For example, a two-dimensional code including the "slip number," a barcode including the "slip number," and a barcode including the "serial number" (three types of codes) can be printed on the shipping label. For example, the "numbering" corresponds to the area to which the "delivery address" belongs, and the "city, ward, county, town, or village" can be divided into multiple areas, and a four-digit number can be assigned to each area as the "numbering." For example, it is possible to use a grouping of multiple "chome" (blocks), and it is possible to assign numbering to 1-chome to 3-chome in XX town, and assign another numbering to 4-chome and 5-chome in the same town. In this specification, a one-dimensional barcode will simply be called a "barcode," and a two-dimensional barcode will be called a "two-dimensional code," and these will be collectively referred to as "two-dimensional codes, etc."

[0041] When a two-dimensional code or the like is photographed by the imaging unit 144, the control unit 140 executes processing for image data corresponding to the photographed image to decode the two-dimensional code or the like contained in the image, and extracts package information (e.g., "slip number") contained in the two-dimensional code or the like. This enables the control unit 140 to recognize the slip number (package ID) of the package to which the photographed delivery label is affixed. Alternatively, when a two-dimensional code or the like is photographed by the imaging unit 144, the control unit 140 may be configured to transmit image data corresponding to the photographed image to the logistics management server 20, and the control unit 110 of the logistics management server 20 may execute processing to decode the two-dimensional code or the like.

[0042] [Shipper's server] FIG. 5 is a functional block diagram of the shipper's server.

[0043] As shown in FIG. 5, the shipper server 50 includes a control unit 150, a memory unit 151, and a communication unit 152. The control unit 150 is configured, for example, by a CPU or the like, and controls the entire shipper server 50. The memory unit 151 is configured, for example, by a ROM, RAM, HDD, or SSD, or a combination thereof, and stores programs and data used when the control unit 150 executes processing based on the programs. The control unit 150 executes processing based on the programs stored in the memory unit 151, thereby realizing the functional configuration of the shipper server 50. The communication unit 152 (network I / F (interface)) connects the shipper server 50 to the network N and establishes communication with external devices.

[0044] <Getting package information> FIG. 6 is a flowchart showing the processing performed by the logistics management server when receiving package information and the processing performed by the shipper server when sending package information.

[0045] The logistics management server 20 acquires package information from the shipper's server 50 at a predetermined timing (for example, a predetermined time on the day before the scheduled delivery date (for example, 8:00 PM to midnight)). The logistics management server's package information reception process is a process performed by the logistics management server 20 at that time, and the shipper's server's package information transmission process is a process performed by the shipper's server 50 at that time.

[0046] In the process of sending package information on the shipper's server side, the control unit 150 of the shipper's server 50 executes the process of step S101 shown in Fig. 6. In the process of receiving package information on the logistics management server side, the control unit 110 of the logistics management server 20 executes the processes of steps S201 to S203 shown in Fig. 6. Note that here, an example will be described in which the delivery company and the shipper are different business entities (the logistics management server 20 and the shipper's server 50 are provided separately).

[0047] The package information (shipper-originated package information) that the logistics management server 20 acquires from the shipper-side server 50 corresponds to some of the information stored in the package information table 121. Examples of the shipper-originated package information include customer management number information, waybill type information, cool classification type information, scheduled shipping date information, scheduled delivery date information, delivery time zone information, recipient code information, recipient phone number information, recipient postal code information, recipient address information, recipient apartment / condominium name information, recipient name information, recipient name (kana) information, title information, sender code information, sender phone number information, sender postal code information, sender address information, sender apartment / condominium information, sender name information, sender name (kana) information, item name information, article information, redelivery deadline information, package size information, and number of parcels information. Of the information stored in the package information table 121, the shipper-originated package information is derived from information received from the shipper-side server 50, whereas other package information (e.g., delivery status information, geotag information, status update date and time information, delivery center information, package receipt confirmation date and time information, final delivery date and time information, final delivery location information, final delivery person information, final delivery company information, update date and time information, etc.) is information generated independently by the logistics management server 20. For example, the other package information is generated by an application (program) executed on the application server, and the generated information is stored in the database server. At that time, transaction control ensures that data updates are performed reliably and maintains the consistency of the entire system.

[0048] In the process of sending package information on the shipper's server side, the control unit 150 of the shipper's server 50 sends delivery list data for multiple packages to be delivered to the logistics management server 20 via the communication unit 152 (step S101). In this process, the control unit 150 of the shipper's server 50 sends delivery list data (e.g., a CSV file) including package information derived from the shipper corresponding to each package to the logistics management server 20. Thereafter, the control unit 150 of the shipper's server 50 ends the process of sending package information on the shipper's server side.

[0049] In the logistics management server-side parcel information reception process, the control unit 110 of the logistics management server 20 receives the delivery list data transmitted from the shipper-side server 50 via the communication unit 112 (step S201). Next, based on the received delivery list data, the control unit 110 of the logistics management server 20 associates the slip number information with the shipper-origin parcel information in the storage unit 111 and stores the information in the parcel information table 121 (step S202). Although not shown, the control unit 110 of the logistics management server 20 reserves slip number information (a quota for each shipper) for the number of parcels to be delivered (e.g., 10,000 parcels), and sequentially assigns slip numbers to the shipper-origin parcel information within that quota. The delivery list data received from the shipper-side server 50 is not directly written to the parcel information management database 120, but is received by the Web server, and after data verification and format conversion by the application server, is stored in the database server. Then, the control unit 110 of the logistics management server 20 sets "unshipped" to the delivery status corresponding to each slip number information in the package information table 121 (step S203). "Unshipped" corresponds to the state before a package is shipped from the shipper, and the state after the package is shipped from the shipper until the delivery company receives the package.

[0050] Furthermore, the control unit 110 of the logistics management server 20 acquires geotag information corresponding to the delivery address information based on the delivery address information included in the delivery list data received from the shipper's server 50 (step S204). The geotag information is latitude and longitude information corresponding to the delivery address. In the processing of step S204, the control unit 110 of the logistics management server 20 acquires geotag information corresponding to each delivery address information by, for example, calling a geocoding API (e.g., Google Maps API), and stores the acquired geotag information in the package information table 121 in association with each slip number information. After executing the processing of step S204, the control unit 110 of the logistics management server 20 terminates the logistics management server-side package information reception processing.

[0051] In addition, when the delivery company and the shipper are the same business entity, it is assumed that the logistics process of goods purchased on an e-commerce site (sales app) operated by the shipper is managed by the logistics management system 10. In this case, it is possible to configure the e-commerce site and the logistics management server 20 to be linked (for example, when a new order is placed on the e-commerce site, information about the order is sent to the logistics management server 20). In this case, data can be synchronized using API communication or batch processing. Also, for example, when customer information (e.g., recipient telephone number, recipient postal code, recipient address, recipient apartment / condominium name, recipient name, recipient name (kana), title, etc.) is managed as a customer management number on the e-commerce site, in the processing of step S202, the control unit 110 of the logistics management server 20 may convert the customer management number information into this customer information and store it in the package information table 121 in association with the slip number information.

[0052] <Delivery app execution process> Fig. 7 is a flowchart showing a delivery application execution process Fig. 8 is a diagram showing an example of a screen displayed when the delivery application is executed.

[0053] The delivery app execution process shown in Figure 7 is a process that is performed at a predetermined timing (for example, at a cycle of about 10 to 100 ms) on driver terminal 40 while the delivery app is logged in. For example, it is assumed that driver terminal 40 is owned by a delivery company and is lent to the driver by an administrator. The driver can log in to the delivery app by inputting the driver ID and password notified by the delivery company into operation input unit 143.

[0054] As shown in FIG. 8, when the delivery app is logged in, the screen displayed on display unit 142 of driver terminal 40 has a map display area 200, a map selection area 201, a talk selection area 202, a scan selection area 203, a package selection area 204, and a my page selection area 205. Map display area 200 is an area where an image corresponding to a map (map image) is displayed. Map selection area 201 is an area where an image corresponding to a button (map selection instruction button) including the word "map" and a corresponding image is displayed. Talk selection area 202 is an area where an image corresponding to a button (talk selection instruction button) including the word "talk" and a corresponding image is displayed. Scan selection area 203 is an area where an image corresponding to a button (scan selection instruction button) including the word "scan" and a corresponding image is displayed. Package selection area 204 is an area where an image corresponding to a button (package selection instruction button) including the word "package" and a corresponding image is displayed. The My Page selection area 205 is an area where an image corresponding to a button (My Page selection instruction button) including the characters "My Page" and a corresponding picture is displayed.

[0055] By operating the operation input unit 143, the driver can input an instruction to select the map selection instruction button in the map selection area 201 (map selection instruction input), an instruction to select the talk selection instruction button in the talk selection area 202 (talk selection instruction input), an instruction to select the scan selection instruction button in the scan selection area 203 (scan selection instruction input), an input to select the baggage selection instruction button in the baggage selection area 204 (baggage selection instruction input), or an input to select the my page selection instruction button in the my page selection area 205 (my page selection instruction input). In this embodiment, for example, if the display unit 142 and the operation input unit 143 are configured with a touch panel LCD, the driver can input an instruction to select a desired object by tapping an area on the touch panel corresponding to the display location of the desired object when the object is displayed on the display unit 142.

[0056] In the delivery application execution process, first, the control unit 140 of the driver terminal 40 determines whether a map selection instruction has been input (step S401). If it is determined that a map selection instruction has been input, the control unit 140 of the driver terminal 40 executes map selection processing (step S402). In the map selection processing, the control unit 140 of the driver terminal 40 displays a map image (map) on the display unit 142 and performs processing such as displaying a pin on the map at a position corresponding to the delivery address. The map selection processing will be described later using FIG. 23.

[0057] If it is determined in step S401 that a map selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a talk selection instruction has been input (step S403). If it is determined that a talk selection instruction has been input, the control unit 140 of the driver terminal 40 executes a talk selection process (step S404). In the talk selection process, the control unit 140 of the driver terminal 40 performs a process such as displaying a talk screen on the display unit 142. The talk screen is a screen for exchanging messages with the administrator terminal 30.

[0058] If it is determined in step S403 that a talk selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a scan selection instruction has been input (step S405). If it is determined that a scan selection instruction has been input, the control unit 140 of the driver terminal 40 executes a scan selection process (step S406). In the scan selection process, the control unit 140 of the driver terminal 40 performs processes such as activating the imaging unit 144 (camera) so that the imaging unit 144 can capture a two-dimensional code or the like printed on the delivery label, and, if the delivery status of a package is updated to "take-out" upon capturing a two-dimensional code or the like, storing package information corresponding to the package (package information held on the driver terminal, described below) in the memory unit 141. The scan selection process will be described later with reference to FIG. 9.

[0059] If it is determined in step S405 that a scan selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a luggage selection instruction has been input (step S407). If it is determined that a luggage selection instruction has been input, the control unit 140 of the driver terminal 40 executes luggage selection processing (step S408). In the luggage selection processing, the control unit 140 of the driver terminal 40 performs processing such as displaying a luggage list screen on the display unit 142 based on the luggage information stored in the memory unit 141. The luggage list screen is a screen that shows a list of luggage that has been taken out of the warehouse.

[0060] If it is determined in step S407 that a package selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a My Page selection instruction has been input (step S409). If it is determined that a My Page selection instruction has been input, the control unit 140 of the driver terminal 40 executes a My Page selection process (step S410). In the My Page selection process, the control unit 140 of the driver terminal 40 performs a process such as displaying a My Page screen on the display unit 142. The My Page screen is a screen for changing various settings (e.g., password) related to the delivery app.

[0061] If it is determined in step S409 that a My Page selection instruction has not been input, or after executing the processing of step S402, step S404, step S406, step S408, or step S410, the control unit 140 of the driver terminal 40 terminates the delivery app execution processing.

[0062] <Processing when scanning is selected> FIG. 9 is a flowchart showing the process at the time of scan selection on the driver terminal side and the process at the time of scan selection on the logistics management server side.

[0063] The driver terminal-side scan selection process is a process performed in the driver terminal 40 when a scan selection instruction is input (step S406 in FIG. 7 (delivery application execution process)). The logistics management server-side scan selection process is a process performed in the logistics management server 20 when a scan selection instruction is input.

[0064] In the driver terminal side scan selection process, the control unit 140 of the driver terminal 40 executes the processes of steps S421 to S426 shown in Fig. 9. In the logistics management server side scan selection process, the control unit 110 of the logistics management server 20 executes the processes of steps S221 to S224 shown in Fig. 9.

[0065] Specifically, in the driver terminal side scan selection process, first, the control unit 140 of the driver terminal 40 activates the imaging unit 144 (camera) (step S421). In this process, the control unit 140 of the driver terminal 40 activates the camera (makes the camera available for use by the delivery app) and displays the camera view (image captured by the camera) and a frame (guideline) for accommodating a two-dimensional code or the like on the display unit 142.

[0066] Next, the control unit 140 of the driver terminal 40 acquires image data corresponding to an image (two-dimensional code image) of a captured two-dimensional code or the like (step S422). In this process, the control unit 140 of the driver terminal 40 causes the imaging unit 144 to capture a two-dimensional code image when the two-dimensional code or the like fits within a frame on the display unit 142 (for example, when a two-dimensional code is detected from the stream data of the camera image, when the driver taps the scan completion button, etc.).

[0067] Next, the control unit 140 of the driver terminal 40 extracts the "invoice number" contained in the two-dimensional code or the like (step S423). In this process, the control unit 140 of the driver terminal 40 detects the two-dimensional code or the like from the image data corresponding to the two-dimensional code image based on a predetermined image processing algorithm, and obtains information indicating the invoice number by decoding (for example, decoding based on the QR Code (registered trademark) standard). Then, the control unit 140 of the driver terminal 40 transmits the obtained information indicating the invoice number (invoice number information) to the logistics management server 20 via the communication unit 145 (step S424).

[0068] In the logistics management server-side scan selection process, the control unit 110 of the logistics management server 20 receives the slip number information transmitted from the driver terminal 40 via the communication unit 112 (step S221). Next, the control unit 110 of the logistics management server 20 identifies the delivery status corresponding to the received slip number information (step S222). In this process, the control unit 110 of the logistics management server 20 searches the package information table 121 using the slip number information as a key, and extracts the delivery status information stored in the package information table 121 in association with the slip number information. Then, the control unit 110 of the logistics management server 20 transmits the identified delivery status information to the driver terminal 40 via the communication unit 112 (step S223).

[0069] In the driver terminal-side scan selection processing, after executing the processing of step S424, the control unit 140 of the driver terminal 40 receives the delivery status information transmitted from the logistics management server 20 via the communication unit 145 (step S425). Next, the control unit 140 of the driver terminal 40 executes a scan selection-time delivery status update-related processing (step S426). The scan selection-time delivery status update-related processing will be described later with reference to FIG. 10. After executing the processing of step S426, the control unit 140 of the driver terminal 40 ends the driver terminal-side scan selection processing.

[0070] In the scan selection process on the logistics management server side, after executing the process of step S223, the control unit 110 of the logistics management server 20 executes the scan selection time delivery status update related process (step S224). The scan selection time delivery status update related process will be described later with reference to Fig. 10. After executing the process of step S224, the control unit 110 of the logistics management server 20 ends the scan selection time process on the logistics management server side.

[0071] <Delivery status update related processing when scanning is selected> FIG. 10 is a flowchart showing the delivery status update related process when scan is selected on the driver's terminal side and the delivery status update related process when scan is selected on the logistics management server side.

[0072] The process related to updating the delivery status when scanning is selected on the driver terminal side is a process performed on the driver terminal 40 in step S426 in Fig. 9 (processing when scanning is selected on the driver terminal side). The process related to updating the delivery status when scanning is selected on the logistics management server side is a process performed on the logistics management server 20 in step S224 in Fig. 9 (processing when scanning is selected on the logistics management server side).

[0073] In the delivery status update related process when scan is selected on the driver terminal side, the control unit 140 of the driver terminal 40 executes the processes of steps S441 to S446 shown in Fig. 10. In the delivery status update related process when scan is selected on the logistics management server side, the control unit 110 of the logistics management server 20 executes the processes of steps S241 to S244 shown in Fig. 10.

[0074] Specifically, in the driver terminal-side scan selection delivery status update-related process, first, the control unit 140 of the driver terminal 40 determines whether the delivery status of the parcel being processed is an updatable delivery status (step S441). The parcel being processed is the parcel photographed in step S422 of FIG. 9 and having a delivery label with a printed two-dimensional code or the like attached. The updatable delivery status is a delivery status other than the final status. The final statuses are "Delivery Complete," "Rejection," "Return," and "Parcel Accident." If the delivery status information received in step S425 of FIG. 9 corresponds to any of the delivery statuses "Delivery Complete," "Rejection," "Return," and "Parcel Accident," the determination result in step S441 is "NO." On the other hand, if the delivery status information received in step S425 of FIG. 9 corresponds to a delivery status other than "Delivery Complete," "Rejection," "Return," and "Parcel Accident," the determination result in step S441 is "YES."

[0075] If it is determined in step S441 that the delivery status of the package is not an updatable delivery status, the control unit 140 of the driver terminal 40 performs error processing (step S442). In this processing, the control unit 140 of the driver terminal 40 pops up an error image (for example, a text image indicating that the delivery status cannot be updated) on the display unit 142 and disables the camera (the delivery app disables the camera). The pop-up display is displayed as a window in a portion of the screen of the display unit 142, and the display ends when the cancel button is tapped (the window corresponding to the error image is closed). As a result of this error processing, the image capture unit 144 is no longer able to capture a two-dimensional code image. When the window corresponding to the error image is closed, the control unit 140 of the driver terminal 40 proceeds to step S421 in FIG. 9. This makes it possible to capture a two-dimensional code image again. In addition, if a predetermined time has passed without the cancel button being tapped, the control unit 140 of the driver terminal 40 may terminate the delivery status update related processing when scan is selected on the driver terminal side and may also terminate the processing when scan is selected on the driver terminal side (see Figure 9).

[0076] If it is determined in step S441 that the delivery status of the package is an updatable delivery status, the control unit 140 of the driver terminal 40 executes a process for accepting a destination status selection operation (step S443). In the process for accepting a destination status selection operation, the control unit 140 of the driver terminal 40 performs a process for accepting an operation to select a destination status. The process for accepting a destination status selection operation will be described later with reference to FIG. 11. After executing the process of step S443, the control unit 140 of the driver terminal 40 transmits information indicating the destination status selected in the process for accepting a destination status selection operation (destination status information) to the logistics management server 20 via the communication unit 145 (step S444).

[0077] In the delivery status update process for when scanning is selected on the logistics management server side, the control unit 110 of the logistics management server 20 receives the destination status information transmitted from the driver terminal 40 via the communication unit 112 (step S241). Next, the control unit 110 of the logistics management server 20 updates the delivery status based on the received destination status information (step S242). In this process, if the destination status information corresponds to "confirmed receipt," the control unit 110 of the logistics management server 20 sets "confirmed receipt" to the delivery status corresponding to the slip number information received in step S221 of FIG. 9 in the package information table 121. "Confirmed receipt" corresponds to a state in which the delivery company has confirmed receipt of a package shipped by a shipper. Furthermore, if the destination status information corresponds to "take-out," the control unit 110 of the logistics management server 20 sets "take-out" to the delivery status corresponding to the slip number information received in step S221 of FIG. 9 in the package information table 121. "Taking out" corresponds to the state in which the driver is taking the goods out of the warehouse (in transit).

[0078] Furthermore, when the destination status information corresponds to "warehouse storage," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information received in step S221 of FIG. 9 to "warehouse storage" or "stored on a specified date" in the package information table 121. Specifically, when the destination status information corresponds to "warehouse storage," if the expected delivery date corresponding to the slip number information is today, the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information to "warehouse storage." Conversely, if the expected delivery date corresponding to the slip number information is the next day or later, the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information to "stored on a specified date." Furthermore, when the destination status information corresponds to "warehouse storage," if no expected delivery date is specified for the slip number information, the control unit 110 of the logistics management server 20 may set the expected delivery date corresponding to the slip number information to today (e.g., the consignment receipt confirmation date) and then set the delivery status corresponding to the slip number information to "warehouse storage." "Warehouse storage" or "designated date storage" corresponds to a state in which the cargo received from the shipper is stored in the warehouse (without being taken out of the warehouse).

[0079] Furthermore, if the destination status information corresponds to "returned goods," the control unit 110 of the logistics management server 20 sets "returned goods" to the delivery status corresponding to the slip number information received in step S221 of FIG. 9 in the package information table 121. "Returned goods" corresponds to a state in which the procedure for returning the package to the shipper has begun. Furthermore, if the destination status information corresponds to "handover," the control unit 110 of the logistics management server 20 sets "handover" to the delivery status corresponding to the slip number information received in step S221 of FIG. 9 in the package information table 121. "Handover" corresponds to a state in which the delivery person for the package has been handed over from one driver to another.

[0080] Furthermore, when the destination status information corresponds to "warehouse storage (return)," the control unit 110 of the logistics management server 20 sets "warehouse storage (return)" or "designated date storage (return)" to the delivery status corresponding to the slip number information received in step S221 of FIG. 9 in the package information table 121. Specifically, when the destination status information corresponds to "warehouse storage (return)," if the expected delivery date corresponding to the slip number information is the current day, the control unit 110 of the logistics management server 20 sets "warehouse storage (return)" to the delivery status corresponding to the slip number information, but if the expected delivery date corresponding to the slip number information is the next day or later, the control unit 110 sets "designated date storage (return)" to the delivery status corresponding to the slip number information. "Warehouse storage (return)" or "designated date storage (return)" corresponds to a state in which a package that has been taken out of a warehouse is stored back in the warehouse.

[0081] After executing the process of step S242, the control unit 110 of the logistics management server 20 transmits some of the package information to the driver terminal 40 via the communication unit 112 (step S243). In this process, the control unit 110 of the logistics management server 20 transmits information indicating the delivery status after the update in step S242 (delivery status information) to the driver terminal 40. Furthermore, if the control unit 110 of the logistics management server 20 sets the delivery status to "take-out" in step S242, it transmits various package information (package information held on the driver terminal side) stored in association with the delivery status information in the package information table 121 to the driver terminal 40. The luggage information held on the driver terminal corresponds to luggage information that can be displayed as a luggage details screen on the display unit 142 of the driver terminal 40, and can include, for example, slip number information, waybill type information, cool classification type information, expected delivery date information, delivery time zone information, recipient telephone number information, recipient address information, recipient apartment / condominium name information, recipient name information, recipient name (kana) information, title information, article information, luggage size information, number of items information, delivery status information, geotag information, etc.

[0082] In the driver terminal side scan selection delivery status update related process, after executing the process of step S444, the control unit 140 of the driver terminal 40 receives the package information transmitted from the logistics management server 20 via the communication unit 145 (step S445). At that time, if the delivery status information included in the received package information corresponds to "take-out," the control unit 140 of the driver terminal 40 stores the package information to be held on the driver terminal side in a predetermined area (delivery destination information storage area) provided in the memory unit 141 (for example, RAM). The package information to be held on the driver terminal side is held in the delivery destination information storage area, and can be displayed as a package details screen without the need to receive the information again from the logistics management server 20 (for example, even offline). In the above, it has been explained that the control unit 110 of the logistics management server 20 obtains geotag information corresponding to each delivery address information by calling the geocoding API (see step S204 in Figure 6), but if the delivery status information included in the package information received from the logistics management server 20 in step S445 corresponds to "take-out", the control unit 140 of the driver terminal 40 may obtain geotag information corresponding to each delivery address information by calling the geocoding API.

[0083] After executing the process of step S445, the control unit 140 of the driver terminal 40 executes continuous scan-related processing (step S446). The continuous scan-related processing will be described later using Figures 17 and 18. After executing the process of step S446, the control unit 140 of the driver terminal 40 ends the driver terminal-side delivery status update-related processing when scan is selected. In the logistics management server-side delivery status update-related processing when scan is selected, after executing the process of step S243, the control unit 110 of the logistics management server 20 executes continuous scan-related processing (step S244). The continuous scan-related processing will be described later using Figures 17 and 18. After executing the process of step S244, the control unit 110 of the logistics management server 20 ends the logistics management server-side delivery status update-related processing when scan is selected.

[0084] <Transition destination status selection operation acceptance process> Fig. 11 is a flowchart showing the destination status selection operation reception process. Fig. 12 is a diagram showing an example of an action selection screen when shipment has not yet been made. Fig. 13 is a diagram showing an example of an action selection screen when receipt has been confirmed. Fig. 14 is a diagram showing an example of an action selection screen when removal has been made. Fig. 15(a) is a diagram showing an example of a transition process screen for a manager. Fig. 15(b) is a diagram showing an example of a transition process screen for a shipper. Fig. 16 is a diagram showing an example of an action selection screen when the shipper is absent.

[0085] The destination status selection operation reception process shown in FIG. 11 is a process carried out in the driver terminal 40 in step S443 of FIG. 10 (delivery status update related process when scan is selected on the driver terminal side).

[0086] In the destination status selection operation reception process, first, the control unit 140 of the driver terminal 40 determines whether the delivery status of the package being processed is "not shipped" (step S461). In this process, the control unit 140 of the driver terminal 40 determines whether the delivery status information received in step S425 of Fig. 9 corresponds to "not shipped." As described above, the package being processed is the package that was photographed in step S422 of Fig. 9 and has a delivery label affixed to it on which a two-dimensional code or the like is printed.

[0087] If it is determined in step S461 that the delivery status of the package is "unshipped," the control unit 140 of the driver terminal 40 executes an unshipped transition destination status selection operation reception process (step S462). In this process, the control unit 140 of the driver terminal 40 displays an unshipped action selection screen on the display unit 142, and waits for either a receipt confirmation transition instruction input or a takeout transition instruction input via the operation input unit 143.

[0088] As shown in FIG. 12, the unshipped action selection screen has a package information display area 211, a package receipt confirmation transition instruction input area 212, and a take-out transition instruction input area 213. The package information display area 211 is an area where an image showing characters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time slot, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. The package receipt confirmation transition instruction input area 212 is an area where an image corresponding to a button containing the characters "receive and store package" (package receipt confirmation transition instruction button) is displayed. The take-out transition instruction input area 213 is an area where an image corresponding to a button containing the characters "take-out" (take-out transition instruction button) is displayed.

[0089] When the unshipped action selection screen is displayed, the driver can operate the operation input unit 143 to input an instruction to select the receipt confirmation transition instruction button in the receipt confirmation transition instruction input area 212 (receipt confirmation transition instruction input), or to input an instruction to select the take-out transition instruction button in the take-out transition instruction input area 213 (take-out transition instruction input). Inputting an instruction to receive confirmation transition corresponds to an operation to select "receipt confirmed" as the destination status, and inputting an instruction to take-out transition corresponds to an operation to select "take-out" as the destination status. When an instruction to receive confirmation transition is input, the delivery status of the package transitions from "unshipped" to "receipt confirmed," and when an instruction to take-out transition is input, the delivery status of the package transitions from "unshipped" to "take-out" (see step S242 in FIG. 10).

[0090] Generally, once the delivery status of a package to be delivered becomes "confirmed delivery," the delivery company assumes responsibility for the package, so if the driver is not an employee of the delivery company, it is desirable for the manager to input the instruction to transition to confirmed delivery. For example, as described above, the driver terminal 40 is the property of the delivery company, and it is assumed that the manager will lend the driver terminal 40 to the driver when the delivery status of the package to be delivered becomes "confirmed delivery."

[0091] The package information (delivery destination summary information) displayed in package information display area 211 is made up of less information than the package information (package information held on the driver terminal) that can be displayed as a package details screen. Examples of the delivery destination summary information include slip number information, estimated delivery date information, delivery time zone information, delivery address information, delivery destination name information, delivery destination name (kana) information, title information, package size information, and number of packages information. For example, in step S425 of FIG. 9, control unit 140 of driver terminal 40 can receive delivery destination summary information together with delivery status information from logistics management server 20, thereby displaying the delivery destination summary information in package information display area 211.

[0092] If it is determined in step S461 that the delivery status of the package is not "unshipped," the control unit 140 of the driver terminal 40 determines whether the delivery status of the package is "confirmed receipt" (step S463). In this process, the control unit 140 of the driver terminal 40 determines whether the delivery status information received in step S425 of Figure 9 is information corresponding to "confirmed receipt."

[0093] If it is determined in step S463 that the delivery status of the package is "confirmed receipt," the control unit 140 of the driver terminal 40 executes a process for accepting an operation to select a transition status when receipt is confirmed (step S464). In this process, the control unit 140 of the driver terminal 40 displays an action selection screen when receipt is confirmed on the display unit 142, and waits for any of an instruction to transfer to takeout, an instruction to transfer to warehouse storage, or an instruction to transfer to returned goods to be input via the operation input unit 143.

[0094] As shown in FIG. 13, the receipt confirmation action selection screen has a package information display area 221, a takeout transition instruction input area 222, a warehouse storage transition instruction input area 223, and a return transition instruction input area 224. The package information display area 221 is an area where an image showing characters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time zone, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. The takeout transition instruction input area 222 is an area where an image corresponding to a button containing the characters "takeout" (takeout transition instruction button) is displayed. The warehouse storage transition instruction input area 223 is an area where an image corresponding to a button containing the characters "warehouse storage" (warehouse storage transition instruction button) is displayed. The return transition instruction input area 224 is an area where an image corresponding to a button containing the characters "return" (return transition instruction button) is displayed.

[0095] When the receipt confirmation action selection screen is displayed, the driver can operate the operation input unit 143 to input an input to select the takeout transition instruction button in the takeout transition instruction input area 222 (takeout transition instruction input), an input to select the warehouse storage transition instruction button in the warehouse storage transition instruction input area 223 (warehouse storage transition instruction input), or an input to select the return transition instruction button in the return transition instruction input area 224 (return transition instruction input). The takeout transition instruction input corresponds to an operation to select "takeout" as the transition destination status, the warehouse storage transition instruction input corresponds to an operation to select "warehouse storage" as the transition destination status, and the return transition instruction input corresponds to an operation to select "return" as the transition destination status. When an instruction to move to take-out is input, the delivery status of the package will change from "confirmed receipt" to "take-out", when an instruction to move to warehouse storage is input, the delivery status of the package will change from "confirmed receipt" to "warehouse storage" or "stored on specified date", and when an instruction to move to return is input, the delivery status of the package will change from "confirmed receipt" to "return" (see step S242 in Figure 10).

[0096] The luggage information displayed in the luggage information display area 221 is the same as the luggage information (delivery destination summary information) displayed in the luggage information display area 211 (see FIG. 12). For example, the control unit 140 of the driver terminal 40 can display the delivery destination summary information in the luggage information display area 221 by receiving the delivery destination summary information together with the delivery status information from the logistics management server 20 in step S425 of FIG.

[0097] If it is determined in step S463 that the delivery status of the package is not "confirmed receipt," the control unit 140 of the driver terminal 40 determines whether the delivery status of the package is "take-out" (step S465). In this process, the control unit 140 of the driver terminal 40 determines whether the delivery status information received in step S425 of Fig. 9 corresponds to "take-out."

[0098] If it is determined in step S465 that the delivery status of the package is "take-out," the control unit 140 of the driver terminal 40 executes a take-out transition destination status selection operation reception process (step S466). In this process, the control unit 140 of the driver terminal 40 causes the display unit 142 to display a take-out action selection screen, and waits for any of a take-out cancellation instruction input, a warehouse storage (take-back) transition instruction input, and a handover transition instruction input via the operation input unit 143.

[0099] As shown in FIG. 14, the takeout action selection screen has a package information display area 231, a takeout cancellation instruction input area 232, a warehouse storage (return) transition instruction input area 233, and a handover transition instruction input area 234. The package information display area 231 is an area where an image showing characters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time zone, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. The takeout cancellation instruction input area 232 is an area where an image corresponding to a button containing the characters "cancel takeout" (takeout cancellation instruction button) is displayed. The warehouse storage (return) transition instruction input area 233 is an area where an image corresponding to a button containing the characters "warehouse storage (return)" (warehouse storage (return) transition instruction button) is displayed. The handover transition instruction input area 234 is an area where an image corresponding to a button containing the characters "handover" (handover transition instruction button) is displayed.

[0100] When the take-out action selection screen is displayed, the driver can operate the operation input unit 143 to make an input to select the take-out cancellation instruction button in the take-out cancellation instruction input area 232 (take-out cancellation instruction input), an input to select the warehouse storage (take-back) transition instruction button in the warehouse storage (take-back) transition instruction input area 233 (warehousing storage (take-back) transition instruction input), or an input to select the take-over transition instruction button in the handover transition instruction input area 234 (handover transition instruction input). The warehouse storage (take-back) transition instruction input corresponds to an operation to select "warehousing storage (take-back)" as the transition destination status, and the handover transition instruction input corresponds to an operation to select "handover" as the transition destination status. When a transition instruction to warehouse storage (return) is input, the delivery status of the package will transition from "taken out" to "warehouse storage (return)" or "designated date storage (return)", and when a transition instruction to handover is input, the delivery status of the package will transition from "taken out" to "handover" (see step S242 in Figure 10).

[0101] The luggage information displayed in luggage information display area 231 is the same as the luggage information (delivery destination summary information) displayed in luggage information display area 211 (see FIG. 12). For example, control unit 140 of driver terminal 40 can display the delivery destination summary information in luggage information display area 231 based on the driver terminal-side luggage information held in the delivery destination information storage area (see step S445 in FIG. 10). Alternatively, control unit 140 of driver terminal 40 may receive delivery destination summary information together with delivery status information from logistics management server 20 in step S425 in FIG. 9, and thereby display the delivery destination summary information in luggage information display area 231.

[0102] The following describes the takeout cancellation instruction input. The takeout cancellation instruction input corresponds to an operation to cancel the most recent takeout transition instruction input. When a takeout cancellation instruction is input, in the process of step S444 of FIG. 10, the control unit 140 of the driver terminal 40 transmits information indicating that a takeout cancellation instruction has been input (takeout cancellation information) to the logistics management server 20 via the communication unit 145. Upon receiving the takeout cancellation information, in the process of step S242 of FIG. 10, the control unit 110 of the logistics management server 20 changes the delivery status corresponding to the slip number information received in step S221 of FIG. 9 from the current delivery status ("takeout") to the previous delivery status. The package information table 121 stores information (transition process information) indicating the delivery status transition process (the current delivery status corresponding to the slip number information and the change history including the delivery status from which the delivery status transitioned when it transitioned to the current delivery status) in association with the slip number information.

[0103] The control unit 110 of the logistics management server 20 can recognize the previous delivery status (the delivery status at the transition source) by referring to the transition process information. As a result, when the take-out cancellation information is received, for example, if the delivery status at the transition source when the delivery status transitioned to the current delivery status ("take-out") was "receipt confirmed," the control unit 110 of the logistics management server 20 sets "receipt confirmed" to the delivery status corresponding to the slip number information received in step S221 of Fig. 9, and if the delivery status at the transition source when the delivery status transitioned to the current delivery status ("take-out") was "warehouse storage (return)," the control unit 110 sets "warehouse storage (return)" to the delivery status corresponding to the slip number information. As a result, the transition of the delivery status to "take-out" is canceled.

[0104] Here, when a slip number is input into the operation input unit 133 of the manager terminal 30, a screen (manager transition process screen) showing the transition process of the delivery status corresponding to that slip number is displayed on the display unit 132. Also, when a slip number is input into the operation input unit of the shipper terminal (terminal device operated by the shipper), a screen (shipper transition process screen) showing the transition process of the delivery status corresponding to that slip number is displayed on the display unit. Also, when a slip number is input into the operation input unit of the customer terminal (terminal device operated by the customer), a screen (customer transition process screen) showing the transition process of the delivery status corresponding to that slip number is displayed on the display unit. The shipper terminal and the customer terminal are information processing devices such as general personal computers, laptop computers, smartphones, and tablet terminals. The manager terminal 30, the shipper terminal, and the customer terminal can each communicate with the logistics management server 20 via the network N, and display a manager transition process screen, a shipper transition process screen, and a customer transition process screen based on the transition process information stored in the cargo information table 121 of the logistics management server 20.

[0105] The example shown in Figure 15(a) shows a transition process screen for the manager when the delivery status of one package (slip number) has changed through the processes (i) to (v) below. The example shown in Figure 15(b) shows a transition process screen for the shipper when the delivery status of one package (slip number) has changed through the processes (i) to (v) below. The transition process screen for the customer is the same as the transition process screen for the shipper. (i) Delivery status changes from "Absent" to "Warehouse Storage (Return)" (ii) After (i) above, a take-out transition instruction is entered, and the delivery status changes from "warehouse storage (take-out)" to "take-out." (iii) After (ii) above, a take-out cancellation instruction is entered, causing the delivery status to change from "take-out" to "warehouse storage (take-back)" (cancellation of the delivery status change in (ii) above). (iv) After (iii) above, a take-out transition instruction is entered, and the delivery status changes from "warehouse storage (take-out)" to "take-out." (v) After (iv) above, the delivery status changes from "taken out" to "warehouse storage (taken back)" by inputting a take-out cancellation instruction (cancellation of the delivery status change in (iv) above).

[0106] As shown in Figure 15(a), the manager transition process screen displays the change history of the delivery status in a manner that allows all of the transition processes (i) to (v) above to be visually recognized. In contrast, as shown in Figure 15(b), the shipper transition process screen and the customer transition process screen display the change history of the delivery status in a manner that allows only the transition process (i) above to be visually recognized. In this embodiment, if the take-out transition instruction input is canceled (the transition of the delivery status to "take-out" is canceled) due to the take-out cancellation instruction input, the shipper transition process screen and the customer transition process screen do not display the change history for the delivery status transition due to the take-out cancellation instruction input (the above (iii) and (v) in the example shown in Figure 15) and the delivery status transition due to the take-out transition instruction input (the above (ii) and (iv) in the example shown in Figure 15).

[0107] In delivery operations, situations may arise where a package that was intended to be removed from a warehouse must be canceled (for example, if the package is too large to be loaded onto a vehicle). By providing a removal cancellation instruction input function, in such situations, the delivery status of the package can be easily restored to the delivery status before "removal," simplifying the process of canceling shipments and improving usability. On the other hand, if a shipper or customer were to see a change history in which the package was stored in the warehouse immediately after being removed from the warehouse, this could raise suspicions among the shipper or customer, leading to the shipper or customer contacting the delivery company with complaints or other inquiries. Delivery companies want to avoid situations where they have to frequently respond to such inquiries, which could reduce their operational efficiency. In this regard, by controlling the logistics management server 20 so as not to transmit information indicating the change history to the shipper's terminal or the customer's terminal, while recording a log (transition process information) of the change in delivery status due to the input of a take-out cancellation instruction and the change in delivery status due to the input of a take-out transition instruction (which is canceled by the input of the take-out cancellation instruction), it is possible to prevent unnecessary misunderstandings from occurring among the shipper or the customer regarding the cancellation of take-out, and business efficiency can be maintained.

[0108] As shown in Figure 15(a), on the manager transition process screen, the transition of delivery status due to the input of a take-out cancellation instruction and the transition of delivery status due to the input of a take-out transition instruction (which is canceled by the input of the take-out cancellation instruction) (i.e., the change history that is not displayed on the shipper transition process screen or the customer transition process screen) may be displayed in a different manner (for example, a background color) from other change history. Also, Figure 15(a) shows that the change history of delivery status for (iii) and (v) above is displayed as "cancelled," but the delivery status of the transition destination ("warehouse storage (return)") may also be displayed.

[0109] As explained above, when a take-out cancellation instruction is input, the transition of the delivery status to "take-out" is canceled. However, if the delivery status from which the transition occurred when the delivery status transitioned to "take-out" was "not shipped," the input of the take-out cancellation instruction will cause the delivery status to revert to "not shipped." Since "not shipped" means that the delivery company has not received the package shipped by the shipper, it is recommended to avoid this situation from occurring. In light of this, it is preferable to input a consignment receipt confirmation transition instruction on the not-shipped action selection screen whenever possible. Alternatively, the not-shipped action selection screen may be configured so that it is not possible to input a take-out transition instruction in the first place (the image corresponding to the take-out transition instruction button is not displayed).

[0110] Returning to the explanation of Figure 11, if it is determined in step S465 that the delivery status of the package is not "taken out," the control unit 140 of the driver terminal 40 determines whether the delivery status of the package is "absent" (step S467). In this process, the control unit 140 of the driver terminal 40 determines whether the delivery status information received in step S425 of Figure 9 is information corresponding to "absent."

[0111] If it is determined in step S467 that the delivery status of the package is "absent," the control unit 140 of the driver terminal 40 executes an absence-time transition destination status selection operation reception process (step S468). In this process, the control unit 140 of the driver terminal 40 causes the display unit 142 to display an absence-time action selection screen, and waits for either a warehouse storage (return) transition instruction input or a handover transition instruction input via the operation input unit 143.

[0112] As shown in FIG. 16, the absence action selection screen has a package information display area 241, a warehouse storage (return) transition instruction input area 242, and a handover transition instruction input area 243. The package information display area 241 is an area where an image showing characters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time slot, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. The warehouse storage (return) transition instruction input area 242 is an area where an image corresponding to a button containing the characters "warehouse storage (return)" (warehouse storage (return) transition instruction button) is displayed. The handover transition instruction input area 243 is an area where an image corresponding to a button containing the characters "handover" (handover transition instruction button) is displayed.

[0113] When the absence action selection screen is displayed, the driver can operate the operation input unit 143 to input an instruction to select the warehouse storage (bring back) transition instruction button in the warehouse storage (bring back) transition instruction input area 242 (warehousing storage (bring back) transition instruction input), or to input an instruction to select the handover transition instruction button in the handover transition instruction input area 243 (handover transition instruction input). The warehouse storage (bring back) transition instruction input corresponds to an operation to select "warehousing storage (bring back)" as the transition destination status, and the handover transition instruction input corresponds to an operation to select "handover" as the transition destination status. When the warehouse storage (bring back) transition instruction input is performed, the delivery status of the package is transitioned from "absent" to "warehousing storage (bring back)" or "designated date storage (bring back)", and when the handover transition instruction input is performed, the delivery status of the package is transitioned from "absent" to "handover" (see step S242 in FIG. 10).

[0114] The luggage information displayed in luggage information display area 241 is the same as the luggage information (delivery destination summary information) displayed in luggage information display area 211 (see FIG. 12). For example, control unit 140 of driver terminal 40 can display the delivery destination summary information in luggage information display area 241 based on the driver terminal-side luggage information held in the delivery destination information storage area (see step S445 in FIG. 10). Alternatively, control unit 140 of driver terminal 40 may receive delivery destination summary information together with delivery status information from logistics management server 20 in step S425 in FIG. 9, and thereby display the delivery destination summary information in luggage information display area 241.

[0115] If it is determined in step S467 that the delivery status of the package is not "absent," the control unit 140 of the driver terminal 40 executes a process for accepting an operation to select a transition destination status according to the delivery status (step S469). For example, if the delivery status of the package is one of "warehouse storage," "stored for a specified date," "warehouse storage (return)," and "stored for a specified date (return)," the control unit 140 of the driver terminal 40 displays a warehousing action selection screen (not shown) on the display unit 142 and waits for an input of a transfer instruction to take out, a transfer instruction to return, or the like, via the operation input unit 143. Furthermore, if the delivery status of the package is "under investigation," the control unit 140 of the driver terminal 40 displays an investigation action selection screen (not shown) on the display unit 142 and waits for an input of a transfer instruction to warehouse storage (return), a transfer instruction to take over, or the like, via the operation input unit 143. Furthermore, when the delivery status of the package is "handover," the control unit 140 of the driver terminal 40 displays a handover action selection screen (not shown) on the display unit 142, and waits for input of instructions to transfer the package to warehouse storage (return) or the like via the operation input unit 143. These inputs have been described above, and therefore will not be described here.

[0116] After executing the processing of step S462, step S464, step S466, step S468, or step S469, the control unit 140 of the driver terminal 40 ends the process of accepting the operation to select the destination status. When an input is made on the various action selection screen, the control unit 140 of the driver terminal 40 ends the process of accepting the operation to select the destination status and proceeds to step S444 in Fig. 10. On the other hand, when a predetermined time has elapsed without an input being made on the various action selection screen, the control unit 140 of the driver terminal 40 may end the process of accepting the operation to select the destination status and end the driver terminal-side process at the time of scan selection (see Fig. 9).

[0117] <Continuous scan related processing> Figures 17 and 18 are flowcharts showing the continuous scan-related processing on the driver's terminal and the continuous scan-related processing on the logistics management server. Figures 19 and 20 are diagrams showing an example of a delivery status update completion screen. Figures 21 and 22 are diagrams showing an example of a continuous scan mode screen.

[0118] The continuous scan-related process on the driver terminal side is a process performed on the driver terminal 40 in step S446 of Fig. 10 (processing related to updating delivery status when scan is selected on the driver terminal side). The continuous scan-related process on the logistics management server side is a process performed on the logistics management server 20 in step S244 of Fig. 10 (processing related to updating delivery status when scan is selected on the logistics management server side).

[0119] In the driver terminal-side continuous scan-related process, the control unit 140 of the driver terminal 40 executes the processes of steps S481 to S492 shown in Figures 17 and 18. In the logistics management server-side continuous scan-related process, the control unit 110 of the logistics management server 20 executes the processes of steps S261 to S266 shown in Figures 17 and 18.

[0120] First, as a premise, the control unit 140 of the driver terminal 40 executes the process of step S445 in FIG. 10, and then displays a delivery status update completion screen on the display unit 142. The delivery status update completion screen is a screen indicating that the update of the delivery status has been completed as a result of input (selection of an action) being made on the various action selection screens described above. FIG. 19 shows, as an example, the delivery status update completion screen that is displayed when a takeout transfer instruction is input on the action selection screen at the time of receipt confirmation (see FIG. 13). The basic configuration of the delivery status update completion screen is the same regardless of the input content on the various action selection screens.

[0121] As shown in FIG. 19 , the delivery status update completion screen includes a package information display area 251, an action result display area 252, and a close instruction input area 253. The package information display area 251 is an area where an image showing characters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time zone, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. The action result display area 252 is an area where an image corresponding to the result of selecting an action on the action selection screen (in this example, the characters "Taken out" and a check mark) is displayed. The close instruction input area 253 is an area where an image corresponding to a button containing the characters "Close" (a "Close" button) is displayed. When the delivery status update completion screen is displayed, the driver (or manager) can operate the operation input unit 143 to input an instruction to select the "Close" button in the close instruction input area 253 (a "Close" instruction input).

[0122] Here, in the destination status selection operation reception process (see Figure 11), when any of the following is input: receipt confirmation transition instruction input, take-out transition instruction input, warehouse storage transition instruction input, return transition instruction input, warehouse storage (take-back) transition instruction input, or take-out cancellation instruction input, a delivery status update completion screen is displayed, and when the instruction to "close" is input on the delivery status update completion screen, the control unit 140 of the driver terminal 40 pops up a continuous reading confirmation image on the delivery status update completion screen.

[0123] FIG. 20 shows a continuous reading confirmation image 254 that is displayed when a "close" instruction is input on the delivery status update completion screen shown in FIG. 19. The continuous reading confirmation image 254 is displayed as a window (dialog) in the center of the delivery status update completion screen, and the dialog displays a message that reads "Do you want to perform continuous reading of takeout?" along with text images corresponding to "Yes" and "No." The area where "Yes" is displayed (YES instruction input area) corresponds to the YES instruction button, and the area where "No" is displayed (NO instruction input area) corresponds to the NO instruction button. When the continuous reading confirmation image is displayed, the driver (or manager) can operate the operation input unit 143 to input an instruction to select the YES instruction button in the YES instruction input area (YES instruction input) or an instruction to select the NO instruction button in the NO instruction input area (NO instruction input).

[0124] 17 and 18, first, the control unit 140 of the driver terminal 40 determines whether or not to perform continuous scanning (step S481). When a YES instruction is input in a situation where a continuous scanning confirmation image is displayed as a pop-up on the delivery status update completion screen, the determination result in step S481 is "YES." On the other hand, when a NO instruction is input, the determination result in step S481 is "NO." Furthermore, if the input (action selection) made in the transition destination status selection operation acceptance process is not any of the following: a consignment receipt confirmation transition instruction input, a take-out transition instruction input, a warehouse storage transition instruction input, a return transition instruction input, a warehouse storage (take-back) transition instruction input, or a take-out cancellation instruction input, even if a "close" instruction is input on the delivery status update completion screen, the continuous scanning confirmation image is not displayed in the first place, and in this case, the determination result in step S481 is also "NO."

[0125] Note that Figure 20 shows the continuous reading confirmation image that is displayed when a take-out transition instruction is input, but the basic configuration is the same for the continuous reading confirmation image that is displayed when other inputs are input (confirmed receipt transition instruction input, warehouse storage transition instruction input, return transition instruction input, warehouse storage (take-back) transition instruction input, or take-out cancellation instruction input). Specifically, in the continuous reading confirmation image that is displayed when an instruction to transition to confirmed receipt is input, the message displayed in the dialog is "Do you want to perform continuous reading to confirm receipt?"; in the continuous reading confirmation image that is displayed when an instruction to transition to warehouse storage is input, the message displayed in the dialog is "Do you want to perform continuous reading for warehouse storage?"; in the continuous reading confirmation image that is displayed when an instruction to transition to returned goods is input, the message displayed in the dialog is "Do you want to perform continuous reading for returned goods?"; in the continuous reading confirmation image that is displayed when an instruction to transition to warehouse storage (return) is input, the message displayed in the dialog is "Do you want to perform continuous reading for warehouse storage (return)?"; and in the continuous reading confirmation image that is displayed when an instruction to cancel take-out is input, the message displayed in the dialog is "Do you want to perform continuous reading to cancel take-out?"; these continuous reading confirmation images are the same as the continuous reading confirmation image shown in Figure 20 except for the content of the messages.

[0126] If it is determined in step S481 that continuous scanning will not be performed, the control unit 140 of the driver terminal 40 ends the driver terminal-side continuous scanning-related process. On the other hand, if it is determined that continuous scanning will be performed, the control unit 140 of the driver terminal 40 sets the updated delivery status (step S482). In this process, the control unit 140 of the driver terminal 40 stores the delivery status information received in step S445 of FIG. 10 in a predetermined area (an updated status information storage area) provided in the memory unit 141 (e.g., RAM). The updated status information storage area is a storage area provided separately from the delivery destination information storage area. Note that even if a takeout cancellation instruction is input in the destination status selection operation reception process (the transition of the delivery status to "takeout" is canceled in step S242 of FIG. 10), the control unit 140 of the driver terminal 40 may also store the delivery status information. In this case, however, the takeout cancellation information is stored in the updated status information storage area.

[0127] Next, the control unit 140 of the driver terminal 40 activates the imaging unit 144 (camera) (step S483). The camera enabled in step S421 of FIG. 9 is disabled when the processing of step S422 is performed. However, in the processing of step S483, the control unit 140 of the driver terminal 40 re-enables the camera (makes the camera available for use by the delivery app) and displays a continuous scan mode screen on the display unit 142. In this embodiment, a single scan mode and a continuous scan mode are provided as modes (scan modes) for capturing images of two-dimensional codes and the like. When the camera is enabled in step S421 of FIG. 9, it is controlled to the single scan mode, whereas when the camera is enabled in step S483, it is controlled to the continuous scan mode. The continuous scan mode screen is a screen displayed in the continuous scan mode.

[0128] As shown in FIG. 21 , the continuous scan mode screen has a shooting target display area 261, a scan mode display area 262, a cancel instruction input area 263, and a slip number display area 264. The shooting target display area 261 is an area where the camera view (image captured by the camera) is displayed, and includes a frame (guideline) for accommodating a two-dimensional code or the like. The scan mode display area 262 is an area where images corresponding to the words "single shooting" and "continuous shooting" are displayed. The cancel instruction input area 263 is an area where an image corresponding to a button containing an "x" mark (cancel button) is displayed. The slip number display area 264 is an area where the slip number extracted from the two-dimensional code image is displayed. When having the driver terminal 40 recognize the slip number, it is also possible to directly input the slip number in the slip number display area 264 via the operation input unit 143, instead of capturing an image of the two-dimensional code or the like.

[0129] The driver (or manager) can operate the operation input unit 143 to input an instruction to select the cancel button in the cancel instruction input area 263 (input a cancel instruction). The driver (or manager) can also operate the operation input unit 143 to directly input the slip number (without scanning) in the slip number input area 264. The only difference between the continuous scan mode screen and the single scan mode screen (the screen displayed in single scan mode) is the display format of the scan mode display area 262; otherwise, the screen configuration is the same. Specifically, in single scan mode, the text image "Single Shooting" is highlighted, while in continuous scan mode, the text image "Continuous Shooting" is highlighted.

[0130] After executing the process of step S483, the control unit 140 of the driver terminal 40 determines whether a cancel instruction has been input (step S484). If it is determined that a cancel instruction has been input, the control unit 140 of the driver terminal 40 ends the driver terminal-side continuous scan-related process. On the other hand, if it is determined that a cancel instruction has not been input, the control unit 140 of the driver terminal 40 executes the processes of steps S485 to S487. However, since these processes are similar to the processes of steps S422 to S424 in FIG. 9, their description will be omitted here. In the logistics management server-side continuous scan-related process, the control unit 110 of the logistics management server 20 executes the processes of steps S261 to S263. However, since these processes are similar to the processes of steps S221 to S223 in FIG. 9, their description will be omitted here.

[0131] In the driver terminal side continuous scan related processing, after executing the processing of step S487, the control unit 140 of the driver terminal 40 receives the delivery status information transmitted from the logistics management server 20 via the communication unit 145 (step S488). Next, the control unit 140 of the driver terminal 40 determines whether the delivery status of the package to be processed can be updated (step S489). The package to be processed is the package to which the photograph was taken in step S485 and which has a delivery label affixed on which a two-dimensional code or the like is printed.

[0132] In the process of step S489, the control unit 140 of the driver terminal 40 compares the delivery status (current status) indicated by the delivery status information received in step S488 with the delivery status (updated status) indicated by the delivery status information stored in the updated status information storage area in step S482. For example, if the current status is the final status, the determination result in step S489 will be "NO." As described above, the final statuses are "Delivery Complete," "Rejected," "Return," and "Parcel Accident." Furthermore, if the current status and the updated status are the same delivery status, the determination result in step S489 will be "NO." If the current status is not the final status and the current status and the updated status are different delivery statuses, the determination result in step S489 will be "YES" or "NO." The control unit 140 of the driver terminal 40 can make this determination depending on the combination (comparison result) of the current status and the updated status. When take-out cancellation information is stored in the updated status information storage area, the updated status is the delivery status ("status before take-out") from when the delivery status transitioned to "take-out".

[0133] For example, when control is exercised to the continuous scan mode based on the input of a receipt confirmation transition instruction, the updated status is "receipt confirmed." When the delivery status transitions to "receipt confirmed," the source delivery status is expected to be "not shipped." If the updated status is "receipt confirmed," if the current status is "not shipped," the determination result in step S489 can be "YES," and if the current status is not "not shipped," the determination result in step S489 can be "NO." Also, for example, when control is exercised to the continuous scan mode based on the input of a takeout transition instruction, the updated status is "takeout." When the delivery status changes to "take out", the delivery status from which the change is made is expected to be "confirmed receipt", "warehouse storage", "storage on specified date", "warehouse storage (return)", "storage on specified date (return)", etc. If the updated status is "take out", and the current status is one of these delivery statuses, the judgment result in step S489 can be "YES", and if the current status is not one of these delivery statuses, the judgment result in step S489 can be "NO".

[0134] Also, for example, when control is exercised to the continuous scan mode based on the input of a transition instruction to warehouse storage, the updated status is "warehouse storage" (no distinction is made between "warehouse storage" and "designated date storage," and these are treated as "warehouse storage"). When the delivery status transitions from "warehouse storage" to "designated date storage," the delivery status from which the transition occurs is assumed to be "confirmed receipt." If the updated status is "warehouse storage," if the current status is "confirmed receipt," the determination result in step S489 can be "YES," and if the current status is not "confirmed receipt," the determination result in step S489 can be "NO." Also, for example, when control is exercised to the continuous scan mode based on the input of a transition instruction to returns, the updated status is "returned." When the delivery status changes to "returned", the delivery status from which the transition occurs is expected to be "confirmed receipt". If the updated status is "returned", if the current status is "confirmed receipt", the judgment result in step S489 can be "YES", and if the current status is not "confirmed receipt", the judgment result in step S489 can be "NO".

[0135] Also, for example, when control is exercised in continuous scan mode based on the input of a warehouse storage (return) transition instruction, the updated status is "warehouse storage (return)" ("warehouse storage (return)" and "designated date storage (return)" are not distinguished from each other, and are treated as "warehouse storage (return)"). When the delivery status transitions from "warehouse storage (return)" to "designated date storage (return)," possible delivery statuses are "taken out," "absent," "under investigation," "handover," etc. When the updated status is "warehouse storage (return)," if the current status is one of these delivery statuses, the determination result in step S489 can be "YES," and if the current status is none of these delivery statuses, the determination result in step S489 can be "NO." Also, for example, when control is exercised in continuous scan mode based on the input of a takeout cancellation instruction, the updated status is "pre-takeout status." When the delivery status transitions to the "pre-take-out status", the delivery status from which the transition occurs is expected to be "taken out". If the updated status is the "pre-take-out status", if the current status is "taken out", the judgment result in step S489 can be "YES", and if the current status is not "taken out", the judgment result in step S489 can be "NO".

[0136] If it is determined in step S489 that the delivery status of the package can be updated, the control unit 140 of the driver terminal 40 transmits information indicating the updated status as destination status information to the logistics management server 20 via the communication unit 145 (step S490). In the logistics management server-side continuous scan-related process, after executing the process of step S263, the control unit 110 of the logistics management server 20 executes the processes of steps S264 to S266. However, since these processes are similar to the processes of steps S241 to S243 in FIG. 10, their description will be omitted here. After executing the process of step S266, the control unit 110 of the logistics management server 20 terminates the logistics management server-side continuous scan-related process. In the driver terminal-side continuous scan-related process, after executing the process of step S490, the control unit 140 of the driver terminal 40 executes the process of step S491. However, since this process is similar to the process of step S445 in FIG. 10, its description will be omitted here.

[0137] If it is determined in step S489 that the delivery status of the package cannot be updated, the control unit 140 of the driver terminal 40 performs error processing (step S492). In this processing, the control unit 140 of the driver terminal 40 causes an error image (for example, a text image indicating that the delivery status cannot be updated) to be toast-displayed on the display unit 142. The toast display is displayed for only a short time as a window in a part of the screen of the display unit 142. While a pop-up display ends when a predetermined operation is performed on the operation input unit 143, the toast display automatically ends after a predetermined time (for example, about 1 to 3 seconds) has elapsed without requiring any operation on the operation input unit 143. While the camera is disabled while a pop-up display is being displayed, the camera remains enabled (a state in which the delivery app can use the camera) while a toast display is being displayed.

[0138] FIG. 22 shows an error image 265 being displayed as a toast while the continuous scan mode screen shown in FIG. 21 is displayed. In this example, it is assumed that the continuous scan mode is controlled based on the input of a takeout transition instruction, and the delivery status corresponding to the slip number extracted from the two-dimensional code or the like that is the subject of the image capture is "takeout." In the figure, the error image 265 displays a message saying "Already changed to takeout." Even if such a toast display is displayed (even during the period when the toast display is being displayed), it is possible to continue to have the imaging unit 144 capture two-dimensional code images.

[0139] After executing the process of step S491 or step S492, the control unit 140 of the driver terminal 40 proceeds to step S484. As a result, steps S485 to S491 are repeated until a cancel command is input. During this time, the imaging unit 144 (camera) remains activated (a state in which a two-dimensional code image can be captured as long as the two-dimensional code or the like is within the guidelines). Therefore, in continuous scan mode, after capturing an image of a two-dimensional code or the like printed on a shipping label affixed to one package (updating the delivery status corresponding to the slip number extracted from the two-dimensional code or the like), it is possible to capture an image of a two-dimensional code or the like printed on a shipping label affixed to another package without having to reactivate the imaging unit 144 (camera), allowing for continuous capture of two-dimensional codes or the like for multiple packages. Furthermore, even if a two-dimensional code or the like printed on a shipping label affixed to a package whose delivery status cannot be updated is captured during this process, continuous capture of two-dimensional codes or the like can be continued without having to reactivate the imaging unit 144 (camera).

[0140] In the above, when the determination result in step S489 is "NO", an error image is uniformly displayed as a toast, but the method of displaying the error image is not limited to this example. For example, when the determination result in step S489 is "NO", an error image is basically displayed as a toast, but in some cases when the determination result in step S489 is "NO" (for example, when the current status is the final status), an error image may be displayed as a pop-up (the camera is disabled while the error image is displayed, and when the display of the error image ends by tapping the cancel button, it becomes possible to capture the two-dimensional code image again).

[0141] Whether or not a transition from one delivery status to another delivery status is permitted can be appropriately designed, and the program can be configured so that the determination result ("YES" or "NO") in step S489 is preset in accordance with the combination of the current status and the updated status. Here, the determination in step S489 is made by comparing the current status with the updated status, but the method for determining whether or not to update the delivery status is not limited to this example. For example, the determination in step S489 may be made by comparing the specific action (input of a receipt confirmation transition instruction, input of a take-out transition instruction, input of a warehouse storage transition instruction, input of a return transition instruction, input of a warehouse storage (take-back) transition instruction, or input of a take-out cancellation instruction) that triggered control to the continuous scan mode with the current status. In this case, in step S490, information indicating the type of the specific action may be transmitted from the driver terminal 40 to the logistics management server 20 as the transition destination status information. The actions allowed for each delivery status can be designed as appropriate, and the program can be configured so that the judgment result of step S489 ("YES" or "NO") is preset in accordance with the combination of the current status and a specific action.

[0142] <Processing when selecting a map> Fig. 23 is a flowchart showing map selection processing. Fig. 24 is a flowchart showing pin display related processing. Fig. 25 is a diagram showing an example of a screen displayed when a map selection instruction is input. Fig. 26 is an enlarged view of a pin.

[0143] The map selection process shown in FIG. 23 is a process that is performed in the driver terminal 40 in step S402 of FIG. 7 (delivery application execution process).

[0144] In the map selection process, first, the control unit 140 of the driver terminal 40 executes pin display related processing (step S501). Here, the pin display related processing will be described with reference to FIG.

[0145] Although not shown, in the pin display-related processing, first, the control unit 140 of the driver terminal 40 calls a map API (for example, Google Maps API) to generate a map object corresponding to the map image (map) to be displayed in the map display area 200 (see FIG. 8), and sets the current location (the location of the driver terminal 40) as the center position of the map. The control unit 140 of the driver terminal 40 can acquire information indicating the current location using a GPS sensor built into the driver terminal 40.

[0146] Then, the control unit 140 of the driver terminal 40 reads out geotag information (location information) corresponding to all slip number information stored in the delivery destination information storage area of ​​the memory unit 141 (see step S445 in FIG. 10) (step S521). The control unit 140 of the driver terminal 40 also generates pins (markers) corresponding to each piece of read geotag information and places the generated pins on a map. At this time, the control unit 140 of the driver terminal 40 associates each pin with various types of driver terminal-held package information (including slip number information) corresponding to the geotag information. As described above, geotag information is latitude and longitude information corresponding to a delivery address, and the delivery address (also referred to as "Address 1") indicates "prefecture," "city, ward, county, town, village," "block number," etc. (excluding "apartment name" or "building name"). In addition, in the delivery destination information storage area, geotag information and various driver terminal-held package information are stored in association with each slip number information (package identification number).

[0147] Note that if the delivery address information corresponding to one slip number information (identification number of package X) is the same as the delivery address information corresponding to another slip number information (identification number of package Y), the geotag information corresponding to package X and the geotag information corresponding to package Y will match. In this way, if the geotag information for multiple packages matches, the control unit 140 of the driver terminal 40 associates the driver terminal-side package information corresponding to the multiple packages with one PIN. That is, in this case, the PINs corresponding to each package are integrated, and only one PIN is generated for multiple packages (slip numbers).

[0148] After executing the process of step S521, the control unit 140 of the driver terminal 40 counts the number of packages (package count) corresponding to each pin (step S522). The number of packages is the number of slip numbers (package IDs) associated with each pin. In this process, the control unit 140 of the driver terminal 40 performs grouping for each package using geotag information (latitude and longitude) as the criterion (matching condition). Specifically, for each slip number, the control unit 140 of the driver terminal 40 assigns packages with matching latitude and longitude (indicated by the geotag information associated with the slip number) to the same group, while assigning packages with mismatching latitude or longitude to a different group, and identifies the number of slip numbers belonging to each group as the number of packages.

[0149] After executing the process of step S522, the control unit 140 of the driver terminal 40 adds conditions and performs grouping (step S523). In this process, the control unit 140 of the driver terminal 40 performs grouping for each package based on the geotag information (latitude and longitude), as well as the destination apartment / condominium name, the recipient's name, and the current delivery status (current status) as criteria (matching conditions). As described above, the destination apartment / condominium name (also referred to as "Address 2") indicates the "apartment name" or "building name." The delivery address is composed of "Address 1" and "Address 2," and "Address 2" is information following "Address 1" to specify the delivery address in more detail. The destination name indicates the name of the customer (the delivery destination of the package) (written mainly in kanji). The current status is transmitted from the logistics management server 20 to the driver terminal 40 when the delivery status is updated and is stored in the driver terminal 40 as package information to be held on the driver terminal side.

[0150] In the processing of step S523, the control unit 140 of the driver terminal 40 can perform a match determination for each group classified in step S522, using the delivery destination apartment / condominium name, delivery recipient name, and current status as conditions (applying additional conditions to each group classified in step S522). For convenience, the groups classified in step S522 will be referred to as geotag-matching groups, and the groups classified in step S523 will be referred to as additional-condition-matching groups. Specifically, in the processing of step S523, for each geotag-matching group, the control unit 140 of the driver terminal 40 assigns to the same additional-condition-matching group those slip numbers belonging to the geotag-matching group that match the delivery destination apartment / condominium name, delivery recipient name, and current status, while assigning to a different additional-condition-matching group those slip numbers that do not match in at least one of these.

[0151] For example, in the process of step S523, the control unit 140 of the driver terminal 40 converts the destination apartment / condominium name, destination name, and current status into character strings for each slip number belonging to each geotag matching group, sorts the character strings arranged in each row, and checks whether the character string corresponding to the current row matches the character string corresponding to the row immediately above. If the character strings match, the control unit 140 assigns the same ID (identification number of the additional condition matching group) to the current row (slip number) as the row immediately above. If the character strings do not match, the control unit 140 assigns an ID to the current row (slip number) that is a value incremented by one from the row immediately above. Alternatively, the control unit 140 of the driver terminal 40 may set a flag for packages (slip numbers) for which the destination apartment / condominium name, destination name, and current status all match, and perform subsequent processing by referencing the flag (clearing the flag each time the processing is performed).

[0152] The grouping method can be designed as appropriate. For example, grouping can be performed based on a key using a hash map, or adjustments can be made to ensure consistency even when a certain amount of error exists (for example, normalization can be performed to standardize data variations (for example, trimming spaces between the recipient's last name and first name), or differences in geotags that are less than a predetermined threshold can be ignored). The grouping criteria (matching conditions) in step S523 are not limited to the above example. For example, matching conditions can be selected arbitrarily from the recipient apartment name, recipient name, current status, expected delivery date, delivery time zone, recipient telephone number, recipient name (kana) (customer's name in kana), data import date (the date data was received from the shipper's server 50), etc. For example, you can select from the following options as appropriate: recipient name only (one condition), recipient apartment name and recipient name (two conditions), recipient name and expected delivery date (two conditions), recipient apartment name, recipient name and expected delivery date (three conditions), recipient name, expected delivery date and delivery time zone (three conditions), recipient apartment name, recipient name, expected delivery date and delivery time zone (four conditions), recipient name, current status, expected delivery date and delivery time zone (four conditions), recipient apartment name, recipient name, current status, expected delivery date and delivery time zone (five conditions), etc.

[0153] Of course, the grouping criteria (matching conditions) are not limited to the above items (geotag information (latitude and longitude), recipient apartment / condominium name, recipient name, current status, expected delivery date, delivery time slot, recipient telephone number, recipient name (kana), data import date, etc.), and it is possible to adopt matching conditions arbitrarily selected from each item corresponding to the package information stored in package information table 121 (for example, in addition to the above, customer management number, waybill type, cool classification, etc.). Here, in the case where one customer management number is assigned to customers who share the same recipient telephone number, recipient postal code, recipient address, recipient apartment / condominium name, recipient name, recipient name (kana), title, etc. (basic customer information), when using the customer management number as the matching condition, this customer information can be considered to have been grouped in advance as a customer management number, so it is possible to configure the system so that this customer information is not included in the matching conditions.

[0154] After executing the process of step S523, the control unit 140 of the driver terminal 40 counts the number of parcel delivery destinations (number of doorsteps) for each pin (step S524). Each pin corresponds to one geotag matching group, and the number of doorsteps is the number of additional condition matching groups that belong to that geotag matching group. In other words, if one geotag matching group is classified into N additional condition matching groups, the number of doorsteps corresponding to that geotag matching group (pin) is N. Then, the control unit 140 of the driver terminal 40 determines whether the number of doorsteps is two or more for each pin, and associates multiple doorstep information with pins that have two or more doorsteps (step S525).

[0155] Next, the control unit 140 of the driver terminal 40 determines the color of each pin (step S526). In this process, the control unit 140 of the driver terminal 40 compares the expected delivery date and delivery time slot (expected delivery date and time) of the package corresponding to each pin with the current time, and determines the color of the pin based on the comparison result. The delivery time slot is one of several categories ("No Specification," "8:00 AM - 12:00 PM," "12:00 PM - 2:00 PM," "2:00 PM - 4:00 PM," "4:00 PM - 6:00 PM," "6:00 PM - 8:00 PM," and "7:00 PM - 9:00 PM"). The driver terminal 40 is equipped with a software-controlled system clock that functions equivalent to a real-time clock, allowing the control unit 140 of the driver terminal 40 to recognize the current time.

[0156] Specifically, in the processing of step S526, the control unit 140 of the driver terminal 40 determines as the comparison result one of the following: (a) the scheduled delivery date is the next day or later, (b) the scheduled delivery date is today and the current time is past the delivery time zone classification, (c) the scheduled delivery date is today and the current time is within the delivery time zone classification, (d) the scheduled delivery date is today and the current time is within the classification immediately before the delivery time zone classification, (e) the scheduled delivery date is today and the current time is within the classification two or more before the delivery time zone classification, and (f) the scheduled delivery date is today and no delivery time zone is specified. Then, the control unit 140 of the driver terminal 40 determines the color of the pin to be purple if the comparison result is (a) above, determines the color of the pin to be red if the comparison result is (b) above, determines the color of the pin to be pink if the comparison result is (c) above, determines the color of the pin to be yellow if the comparison result is (d) above, determines the color of the pin to be green if the comparison result is (e) above, and determines the color of the pin to be blue if the comparison result is (f) above.

[0157] Furthermore, if the current status of the package corresponding to the pin is "absent" or "under investigation," the control unit 140 of the driver terminal 40 determines the color of the pin to be gray. Note that if the number of eaves corresponding to the pin is two or more, two or more colors may be applicable, and the control unit 140 of the driver terminal 40 determines the color of the pin based on a predetermined priority. Alternatively, if the number of eaves corresponding to the pin is two or more, the control unit 140 of the driver terminal 40 may determine the color of the pin to be a color different from any of the above. After executing the process of step S526, the control unit 140 of the driver terminal 40 ends the pin display-related process.

[0158] The pin display-related processing performed in step S501 of Fig. 23 (map selection processing) has been described above using Fig. 24. In the map selection processing, the control unit 140 of the driver terminal 40 executes the pin display-related processing, and then causes the display unit 142 to display a map and a pin at a position on the map that corresponds to the delivery address.

[0159] 25 and 26 show examples of such maps and pins. Pin 300 is composed of a round main body 301 and a wedge-shaped lower portion 302. A number is displayed on main body 301, and this number is called the pin center number. The pin center number corresponds to the order in which the driver terminal-side luggage information corresponding to that pin 300 was stored in the delivery destination information storage area (the delivery status of the luggage corresponding to that pin 300 was updated to "take out"). Pin 300a displays "21" as the pin center number, pin 300b displays "3" as the pin center number, and pin 300c displays "2" as the pin center number.

[0160] Furthermore, the pin 300 may include an upper left addition portion 303 and / or an upper right addition portion 304 that are smaller than the main body portion 301. The upper left addition portion 303 is a round portion located at the upper left of the main body portion 301. A number is displayed in the upper left addition portion 303, and this number is referred to as the upper left number of the pin. The upper left number of the pin corresponds to the number of slip numbers (package IDs) associated with the pin (number of packages). Pins 300b and 300c each include the upper left addition portion 303, and "5" is displayed as the number of packages in the upper left of pin 300b, and "10" is displayed as the number of packages in the upper left of pin 300c. In this example, the number of packages associated with pin 300b is 5, and the number of packages associated with pin 300c is 10. That is, there are 5 packages whose destination is the geotag associated with pin 300b, and there are 10 packages whose destination is the geotag associated with pin 300c. For each pin 300, if the number of packages is two or more, the upper left addition section 303 is displayed, whereas if the number of packages is one, the upper left addition section 303 is not displayed.

[0161] The upper right addition section 304 is a round-shaped section located at the upper right of the main body 301. No numbers are displayed in the upper right addition section 304. For each pin 300, if the driver terminal-side luggage information corresponding to that pin 300 contains article information, the upper right addition section 304 is displayed. However, if the driver terminal-side luggage information corresponding to that pin 300 does not contain article information, the upper right addition section 304 is not displayed. That is, the display of the upper right addition section 304 indicates that the driver terminal-side luggage information corresponding to that pin 300 contains article information. Article information is information indicating an article (a matter of special note). An example of an article is a customer's comment regarding the delivery of a package (e.g., a request such as "Please put it in the delivery box"). When a customer provides a comment to a shipper when purchasing a product, such article information is transmitted from the shipper server 50 to the logistics management server 20 as shipper-originated package information, and is then transmitted from the logistics management server 20 to the driver terminal 40 as driver terminal-side luggage information. In addition, when the manager receives a call from a customer, the manager can enter an article into the operation input unit 133 of the manager terminal 30, and the article information is also sent from the logistics management server 20 to the driver terminal 40 as luggage information to be held on the driver terminal side.

[0162] Pin 300c includes an upper right additional portion 304, which indicates that an article (comment) is associated with pin 300c. On the other hand, pins 300a and 300b do not include an upper right additional portion 304, and therefore no article (comment) is associated with pins 300a and 300b. Pin 300b also includes a ring portion 305. The ring portion 305 is a portion corresponding to a ring located on the outer edge of the main body 301. For each pin 300, if the number of ends is two or more, the ring portion 305 is displayed, whereas if the number of ends is one, the ring portion 305 is not displayed. In other words, the display of the ring portion 305 indicates that the number of destinations (number of ends) for the package corresponding to that pin 300 is multiple. In this example, the number of ends corresponding to pin 300b is two or more, and the number of ends corresponding to pins 300a and 300c is one.

[0163] 24, the upper left additional portion 303 is displayed in a color corresponding to the color (similar color) (for example, if the main body portion 301 is displayed in pink, the upper left additional portion 303 is displayed in magenta), and the upper right additional portion 304 is displayed in a predetermined color (for example, orange). For convenience, these colors are omitted from the illustration.

[0164] Returning to the explanation of FIG. 23, after executing the process of step S501 and displaying the map and pins on the display unit 142, the control unit 140 of the driver terminal 40 determines whether a pin selection instruction has been input (step S502). When the map and pins are displayed in the map display area 200, the driver can input an instruction to select one of the pins displayed on the map (pin selection instruction input) by operating the operation input unit 143. For example, the driver can select the desired pin by tapping the area on the touch panel corresponding to the display location of the pin.

[0165] If it is determined that a pin selection instruction has not been input, the control unit 140 of the driver terminal 40 ends the map selection processing. On the other hand, if it is determined that a pin selection instruction has been input, the control unit 140 of the driver terminal 40 executes pin information acquisition processing (step S503). The pin information acquisition processing will be described later using FIG. 27. After executing the processing of step S503, the control unit 140 of the driver terminal 40 executes delivery route related processing (step S504). The delivery route related processing will be described later using FIG. 34. After executing the processing of step S504, the control unit 140 of the driver terminal 40 executes delivery related processing (step S505). The delivery related processing will be described later using FIG. 35. After executing the processing of step S505, the control unit 140 of the driver terminal 40 ends the map selection processing.

[0166] <Pin information acquisition process> Fig. 27 is a flowchart showing the pin information acquisition process Fig. 28 to Fig. 33 are diagrams showing examples of screens that are displayed when a pin selection instruction is input.

[0167] The pin information acquisition process shown in FIG. 27 is a process that is performed in the driver terminal 40 in step S503 of FIG. 23 (processing at the time of map selection).

[0168] In the pin information acquisition process, first, the control unit 140 of the driver terminal 40 reads the package information held on the driver terminal side associated with the selected pin from the delivery destination information storage area of ​​the memory unit 141 (step S541). Next, the control unit 140 of the driver terminal 40 determines whether multiple doorstep information is associated with the pin (step S542).

[0169] If it is determined that multiple doorstep information is not associated with the pin, the control unit 140 of the driver terminal 40 identifies the package corresponding to the pin as a package to be delivered (step S543). In this process, if package information held on the driver terminal corresponding to one package is associated with the pin, the control unit 140 of the driver terminal 40 identifies the one package as a package to be delivered, and if package information held on the driver terminal corresponding to multiple packages is associated with the pin, the control unit 140 identifies all of the multiple packages as packages to be delivered. If multiple doorstep information is not associated with the pin, the number of doors corresponding to the pin is 1, and at the time the pin is selected, the packages corresponding to the pin (regardless of the number of packages) are determined to be packages to be delivered.

[0170] After executing the process of step S543, the control unit 140 of the driver terminal 40 determines the display mode of the luggage card to be the upper display mode (step S544). Then, the control unit 140 of the driver terminal 40 activates the delivery selection instruction button (step S545). On the other hand, if it is determined in step S542 that multiple doorstep information is associated with the pin, the control unit 140 of the driver terminal 40 determines the display mode of the luggage card to be the lower display mode (step S546). After executing the process of step S545 or step S546, the control unit 140 of the driver terminal 40 ends the pin information acquisition process.

[0171] Here, when a pin selection instruction is input for one pin, an image corresponding to the driver terminal-side luggage information read out in step S541 is displayed on the display unit 142 as a luggage card. The luggage card can be configured as an image resembling a card (card image) and is intended to visually display information associated with the pin. The luggage card is a UI component including a card image, but for convenience, the UI component may be referred to simply as an "image" in this specification. The information displayed on the luggage card is a portion of the driver terminal-side luggage information stored in the delivery destination information storage area (for example, the delivery destination summary information described above). The luggage card can be displayed in two different display modes: one in the upper part of the screen of the display unit 142 (upper display mode), and the other in the lower part to the center of the screen of the display unit 142 (lower display mode).

[0172] Figure 28 shows the screen that is displayed when pin 300a (see Figure 26(a)) is selected. Since multiple doorstep information is not associated with pin 300a, the processing of steps S543 to S545 is executed. At this time, as shown in Figure 28, the luggage card 310 is displayed fixedly at the top of the screen of the display unit 142, and an image (delivery selection instruction button image) corresponding to a button (delivery selection instruction button) containing the word "delivery" (instead of the word "scan") is displayed in the scan selection area 203.

[0173] The number of packages corresponding to pin 300a is one, and package information held on the driver terminal corresponding to that one package is associated with pin 300a. Package card 310 is an image (an image corresponding to one card) corresponding to the package information held on the driver terminal corresponding to that one package. Furthermore, when the delivery selection instruction button is enabled, a delivery selection instruction button image is displayed. While the delivery selection instruction button image is displayed, the driver can operate operation input unit 143 to input an instruction to select the delivery selection instruction button in scan selection area 203 (delivery selection instruction input). Note that the change in the display mode in scan selection area 203 upon enabling the delivery selection instruction button is not limited to this example. For example, instead of a text image of "Delivery," a text image of "Scan" may be displayed, and its color may be changed, or the image displayed with the text may be changed to a different image (icon). Alternatively, the delivery selection instruction button image may be configured as a button image provided separately from the image corresponding to the scan selection instruction button (scan selection instruction button image). For example, when the delivery selection instruction button is enabled, the delivery selection instruction button image may be made to appear in an area other than the scan selection area 203, so that both the scan selection instruction button image and the delivery selection instruction button image are displayed.

[0174] 29 to 31 show the screen that is displayed when pin 300b (see FIG. 26(b)) is selected. Since multiple pieces of doorstep information are associated with pin 300b, the processing of step S546 is executed. At this time, as shown in FIG. 29, luggage cards 320 are displayed from the bottom to the center of the screen on display unit 142. The number of pieces of luggage corresponding to pin 300b is five, and luggage information held on the driver terminal side corresponding to these five pieces of luggage is associated with pin 300b. The luggage card 320 is an image corresponding to the luggage information held on the driver terminal side corresponding to these five pieces of luggage, and is made up of luggage card 320a, luggage card 320b, luggage card 320c, luggage card 320d, and luggage card 320e (images corresponding to the five cards).

[0175] Also, in this example, the number of eaves corresponding to pin 300b is assumed to be three. The five packages (geotag-matching groups) are classified into three additional condition-matching groups. These three additional condition-matching groups will be referred to as the first additional condition-matching group, the second additional condition-matching group, and the third additional condition-matching group. Also, in this example, the number of slip numbers belonging to the first additional condition-matching group is assumed to be three, the number of slip numbers belonging to the second additional condition-matching group is assumed to be one, and the number of slip numbers belonging to the third additional condition-matching group is assumed to be one. In other words, of the five packages (slip numbers) belonging to this geotag-matching group, three are classified into the first additional condition-matching group, one is classified into the second additional condition-matching group, and one is classified into the third additional condition-matching group.

[0176] Here, the three packages classified into the first additional condition-matching group will be referred to as package A, package B, and package C, the one package classified into the second additional condition-matching group will be referred to as package D, and the one package classified into the third additional condition-matching group will be referred to as package E. Package card 320a is an image corresponding to the package information to be held on the driver terminal corresponding to package A, package card 320b is an image corresponding to the package information to be held on the driver terminal corresponding to package B, package card 320c is an image corresponding to the package information to be held on the driver terminal corresponding to package C, package card 320d is an image corresponding to the package information to be held on the driver terminal corresponding to package D, and package card 320e is an image corresponding to the package information to be held on the driver terminal corresponding to package E. The recipient name corresponding to the slip number belonging to the first additional condition-matching group is "Natsui Akio," the recipient name corresponding to the slip number belonging to the second additional condition-matching group is "Akikawa Fuyuhiko," and the recipient name corresponding to the slip number belonging to the third additional condition-matching group is "Fuyuno Koharu."

[0177] 29, luggage card 320a is displayed at the top of the luggage cards 320, luggage card 320d is displayed below luggage card 320a, and luggage card 320e is displayed below luggage card 320d. As a preliminary step to the state shown in FIG. 29, when a pin selection instruction is input for pin 300b, the upper end of luggage card 320a first appears at the lower end of the screen on display unit 142. Then, luggage card 320a is displayed so as to move upward until the entire luggage card 320a is displayed within the screen, and then the upper end of luggage card 320d appears at the lower end of the screen on display unit 142. Then, similar to luggage card 320a, luggage card 320d is displayed so as to move upward until the entire luggage card 320d is displayed within the screen, and then the upper end of luggage card 320e appears at the lower end of the screen on display unit 142. The luggage card 320e is also displayed moving upward, but before the entire luggage card 320e is displayed on the screen, the movement of the luggage card 320e stops, resulting in the state shown in Figure 29. The luggage card 320 moves at high speed, and it takes a very short time (for example, about 0.3 to 1 second) from when a pin selection instruction is input to the pin 300b until it reaches the state shown in Figure 29. This gives the driver the impression that the luggage card 320 is jumping out onto the screen.

[0178] In the state shown in FIG. 29, only the luggage card 320a is visible among the luggage cards 320 (luggage card 320a, luggage card 320b, and luggage card 320c) corresponding to the slip numbers belonging to the first additional condition-matching group. The luggage cards 320b and 320c are arranged behind the luggage card 320a so as to overlap with the luggage card 320a. In the state shown in FIG. 29, the driver can display the luggage card 320b by touching the area on the touch panel corresponding to the luggage card 320a with his / her finger and sliding his / her finger to the right (performing a rightward swipe operation). FIG. 30 shows the state in which the luggage card 320b has become visible in this manner. In the state shown in FIG. 29, the luggage card 320a displays the driver terminal-side luggage information corresponding to the slip number represented by 12 digits, "1000-0000-0491." In contrast, in the state shown in Fig. 30, the driver terminal-side luggage information corresponding to the slip number indicated by 12 digits, "1000-0000-0492," is displayed as luggage card 320b. Similarly, in the state shown in Fig. 30, the driver can also display luggage card 320c by swiping right.

[0179] In this way, when there are multiple slip numbers belonging to one additional condition-matching group, only the luggage card corresponding to one of the multiple slip numbers (the first luggage card) is displayed in a visible manner, while the luggage cards corresponding to the other slip numbers (the second and subsequent luggage cards) are hidden (or only partially displayed). As a swipe operation in a predetermined direction (e.g., left or right) is detected, the second and subsequent luggage cards are sequentially displayed. In this case, the driver terminal-held luggage information displayed on each luggage card may be read from the delivery destination information storage area when the luggage card is displayed (or, for the second and subsequent luggage cards, when a swipe operation is detected). Note that when there are multiple slip numbers belonging to one additional condition-matching group, a number corresponding to the number of slip numbers is displayed on the luggage card. For example, in FIG. 29, "3 units" is displayed in the upper right corner of luggage card 320a, corresponding to the number of slip numbers belonging to the first additional condition-matching group being three. This allows the driver to know the number of luggage cards (three in this example) that correspond to the additional condition-matching group.

[0180] Furthermore, if there are multiple additional condition-matching groups, the luggage cards corresponding to each additional condition-matching group are displayed in a vertical row within a predetermined area (luggage card display area) on the screen of the display unit 142. Due to display space limitations, only two luggage cards can be displayed in the luggage card display area (in a manner where the entire card is visible). Therefore, in the initial state where the luggage cards are displayed, if there are three or more additional condition-matching groups, only a portion of the third luggage card from the top is displayed, and if there are four or more additional condition-matching groups, none of the luggage cards from the fourth top onward are displayed. Accordingly, in the state shown in Figures 29 and 30, only a portion of the luggage card 320e is displayed. In this state, the driver can move luggage card 320a (luggage cards 320b to 320c), luggage card 320d, and luggage card 320e upward by touching the area on the touch panel corresponding to the luggage card display area with their finger and sliding their finger upward (performing an upward swipe operation). This allows the entire luggage card 320e (the third luggage card from the top) to be displayed. FIG. 31 shows a state in which luggage card 320e becomes visible as a result of an upward swipe operation in the state shown in FIG. 29. Similarly, if there are luggage cards fourth or later from the top, the driver can display those luggage cards by swiping upward. In this way, if the luggage cards corresponding to each additional condition-matching group do not fit within the luggage card display area, the luggage cards outside the luggage card display area can be displayed by scrolling in a predetermined direction (e.g., up or down) when a swipe operation in a predetermined direction is detected.

[0181] The swipe direction (first direction) required to display luggage cards outside the luggage card display area when there are multiple additional condition-matching groups, and the swipe direction (second direction) required to display the second and subsequent luggage cards when there are multiple slip numbers belonging to one additional condition-matching group, can be any direction as long as the first direction and the second direction are different. Furthermore, when there are multiple additional condition-matching groups, the range of luggage cards corresponding to each of the multiple additional condition-matching groups that can be displayed within the luggage card display area in the initial state is not limited. For example, the second luggage card from the top may be displayed halfway, or the boundary between the top and second luggage cards may be displayed. In this way, when a predetermined operation is required to display at least some luggage cards, it is desirable to display a message that indicates to the driver that there are luggage cards that are not yet displayed when the luggage cards are hidden. For example, when there are multiple additional condition-matching groups, a scroll bar may be displayed. In addition, if there are multiple slip numbers that belong to one additional condition matching group, the display position of the luggage card placed on the back side may be slightly shifted from the display position of the luggage card displayed in front, thereby suggesting that a luggage card is present on the back side.

[0182] Furthermore, if there are multiple additional condition-matching groups, a radio button is displayed to the left of the luggage card corresponding to each additional condition-matching group. The radio button can be configured as an image resembling a button (button image), and is used to select one additional condition-matching group from multiple additional condition-matching groups. The driver can input an instruction to select one radio button (radio button selection instruction input) by operating the operation input unit 143. There is a one-to-one correspondence between the radio buttons and the additional condition-matching groups, and selecting one radio button is equivalent to selecting the additional condition-matching group to which the luggage card located to the right of the radio button belongs.

[0183] 29 to 31, radio button 350a is displayed to the left of the luggage cards 320 (luggage cards 320a, 320b, and 320c) corresponding to slip numbers belonging to the first additional condition-matching group, radio button 350b is displayed to the left of the luggage card 320 (luggage card 320d) corresponding to slip numbers belonging to the second additional condition-matching group, and radio button 350c is displayed to the left of the luggage card 320 (luggage card 320e) corresponding to slip numbers belonging to the third additional condition-matching group, showing that radio button 350c has been selected. In FIG. 31, upon selection of radio button 350c, the display mode of radio button 350c (e.g., button color) changes, and the display mode of luggage card 320e changes (e.g., card color changes, card edge is highlighted). This indicates that the additional condition-matching group (third additional condition-matching group) to which the slip number corresponding to luggage card 320e belongs has been selected.

[0184] FIG. 32 also shows a screen that is displayed when pin 300c (see FIG. 26(c)) is selected. Since multiple doorstep information is not associated with pin 300c, the processes of steps S543 to S545 are executed. At this time, as shown in FIG. 32, a luggage card 330 is fixedly displayed at the top of the screen on display unit 142. The number of luggage items corresponding to pin 300c is 10, and luggage information held on the driver terminal side corresponding to these 10 luggage items is associated with pin 300c. The luggage card 330 is an image corresponding to the luggage information held on the driver terminal side corresponding to these 10 luggage items, and is made up of 10 luggage cards (images corresponding to the 10 cards).

[0185] In the state shown in FIG. 32, only one of the ten luggage cards (luggage card 330a) is visible. The other nine luggage cards are arranged behind luggage card 330a so as to overlap with it. As in FIGS. 29 and 30, the driver can display the nine luggage cards by swiping right. Also, in FIG. 32, as in FIG. 28, the delivery selection instruction button is enabled, and a delivery selection instruction button image is displayed in the scan selection area 203. This allows the driver to input a delivery selection instruction.

[0186] When a luggage card (or an area on the touch panel corresponding to the display location) is tapped in the states shown in Figures 28 to 32, a luggage details screen is displayed. The luggage details screen displays more detailed information than the luggage card (for example, slip number information, waybill type information, cool classification type information, expected delivery date information, delivery time zone information, recipient phone number information, recipient address information, recipient apartment / condominium name information, recipient name information, recipient name (kana), title information, article information, luggage size information, number of parcels information, delivery status information, etc.). Here, when a tap operation on one luggage card is detected, if the additional condition-matching group to which the slip number corresponding to that luggage card belongs contains multiple slip numbers, it is possible to display a list of slip numbers belonging to that additional condition-matching group on the luggage details screen.

[0187] As an example, Figure 33 shows a luggage details screen that is displayed when luggage card 330a is tapped in the state shown in Figure 32. This luggage details screen has a slip number list display area 360, in which eight slip numbers are displayed. The additional condition-matching group to which the slip number corresponding to luggage card 330a belongs contains ten slip numbers, but due to display space limitations, only a maximum of eight slip numbers can be displayed in slip number list display area 360. In this case, the driver can display all ten slip numbers by tapping the area on the touch panel that corresponds to slip number list display area 360.

[0188] The above describes the display modes of luggage cards, but these are merely examples, and luggage cards can be configured appropriately to be displayed in any manner. For example, although it has been described that when there are multiple slip numbers belonging to one additional condition-matching group, the second and subsequent luggage cards are hidden, it is not necessary to distinguish between the first and subsequent luggage cards. For example, it may be configured so that only one luggage card is displayed, and all of the multiple slip numbers are displayed in a list on that luggage card (without requiring a swipe or tap operation) (allowing the driver to understand the multiple slip numbers without sliding the luggage card or displaying a luggage details screen).

[0189] In the above description, when multiple additional condition-matching groups exist, one additional condition-matching group can be selected by selecting a radio button. The display location of the radio button is not limited, and the radio button can be positioned on the left, right, bottom right, top right, or other location on the luggage card. The operation for selecting one additional condition-matching group is not limited to inputting a radio button selection instruction (radio buttons are not required), and a specific operation can be performed to select one additional condition-matching group. Examples of the specific operation include tapping or long-pressing the luggage card. It is desirable to use an operation that clearly indicates the driver's intention to select the additional condition-matching group. Furthermore, if the specific operation is an operation for displaying a luggage details screen (e.g., a tap), a delivery selection instruction button image can be displayed when the luggage details screen is displayed (allowing the driver to input a delivery selection instruction from the luggage details screen).

[0190] <Delivery route related processing> FIG. 34 is a flowchart showing delivery route related processing.

[0191] The delivery route-related processing shown in FIG. 34 is processing carried out in the driver terminal 40 in step S504 of FIG. 23 (processing at the time of map selection).

[0192] As shown in FIGS. 28 to 32, when a pin selection instruction input is made, the screen displayed on the display unit 142 of the driver terminal 40 has an AI router selection area 371, a home map selection area 372, and a route guidance selection area 373. The AI ​​router selection area 371 is an area where an image corresponding to a button containing the characters "AI Router" (AI router selection instruction button) is displayed. The home map selection area 372 is an area where an image corresponding to a button containing the characters "home map" (home map selection instruction button) is displayed. The route guidance selection area 373 is an area where an image corresponding to a button containing a symbol indicating a right turn arrow (route guidance selection instruction button) is displayed. By operating the operation input unit 143, the driver can make an input to select the AI ​​router selection instruction button in the AI ​​router selection area 371 (AI router selection instruction input), an input to select the home map selection instruction button in the home map selection area 372 (home map selection instruction input), or an input to select the route guidance selection instruction button in the route guidance selection area 373 (route guidance selection instruction input).

[0193] In the delivery route-related processing, the control unit 140 of the driver terminal 40 first determines whether an AI router selection instruction has been input (step S561). If it determines that an AI router selection instruction has been input, the control unit 140 of the driver terminal 40 executes AI router processing (step S562). In this processing, the control unit 140 of the driver terminal 40 transmits information indicating the current location (the location of the driver terminal 40), a list of delivery destinations (geotags associated with each pin), delivery conditions (delivery time slots associated with each pin), etc. to an external server (e.g., a Google server). The external server executes a predetermined route optimization algorithm based on the information received from the driver terminal 40 and real-time traffic information, etc., to optimize the delivery route when delivering packages to all delivery destinations, calculate the estimated time of arrival at each delivery destination (geotag), and transmits information indicating the optimized delivery route and estimated arrival time to the driver terminal 40. Based on the information received from the external server, the control unit 140 of the driver terminal 40 changes the number in the center of each pin in the map display area 200 to a number corresponding to the delivery order on the optimized delivery route, and displays the estimated arrival time above each pin.

[0194] If it is determined in step S561 that an AI router selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a home map selection instruction has been input (step S563). If it is determined that a home map selection instruction has been input, the control unit 140 of the driver terminal 40 executes home map linking processing (step S564). In this processing, the control unit 140 of the driver terminal 40 links with an external application (for example, a residential map application) to display building names, nameplates, tenant names, etc. on the map in the map display area 200.

[0195] If it is determined in step S563 that a home map selection instruction has not been input, the control unit 140 of the driver terminal 40 determines whether a route guidance selection instruction has been input (step S565). If it is determined that a route guidance selection instruction has been input, the control unit 140 of the driver terminal 40 executes route guidance processing (step S566). In this processing, the control unit 140 of the driver terminal 40 starts an external application (e.g., Google Maps) and transmits information indicating the current location (the location of the driver terminal 40), the destination (the geotag associated with the pin selected in step S502 of FIG. 23), etc. to an external server (e.g., a Google server). The external server calculates an optimal route from the current location to the destination based on the information received from the driver terminal 40, real-time traffic information, etc., and transmits information indicating the calculation result to the driver terminal 40. Based on the information received from the external server, the control unit 140 of the driver terminal 40 displays the route from the current location to the destination on a map in the map display area 200.

[0196] If it is determined in step S565 that a route guidance selection instruction has not been input, the control unit 140 of the driver terminal 40 ends the delivery route-related processing. After executing the processing of step S562, step S564, or step S566, the control unit 140 of the driver terminal 40 ends the delivery route-related processing and also ends the map selection processing.

[0197] <Delivery-related processing> FIG. 35 is a flowchart showing the delivery-related processing.

[0198] The delivery-related processing shown in FIG. 35 is processing carried out in the driver terminal 40 in step S505 of FIG. 23 (processing at the time of map selection).

[0199] In the delivery-related processing, first, the control unit 140 of the driver terminal 40 determines whether the package to be delivered has been identified (step S581). In this processing, the control unit 140 of the driver terminal 40 determines whether the delivery target identified flag is set to ON. The delivery target identified flag is a flag that is set to ON when the package to be delivered has been identified (see step S543 in FIG. 27 and step S583 in FIG. 35). In other words, if the processing of step S543 has been executed (when multiple doorstep information is not associated with the pin selected in step S502 in FIG. 23), the determination result of step S581 will be "YES," whereas if the processing of step S543 has not been executed (when multiple doorstep information is associated with the pin selected in step S502 in FIG. 23), the determination result of step S581 will be "NO."

[0200] If it is determined that the parcel to be delivered has not been identified, the control unit 140 of the driver terminal 40 executes a radio button selection instruction input reception process (step S582). In this process, the control unit 140 of the driver terminal 40 waits for a radio button selection instruction input. When a radio button selection instruction input is made, the control unit 140 of the driver terminal 40 transitions the process to step S583. On the other hand, if a predetermined time has passed without a radio button selection instruction input, the control unit 140 of the driver terminal 40 may end the delivery-related process and also end the map selection process (see FIG. 23).

[0201] Next, the control unit 140 of the driver terminal 40 identifies the package corresponding to the selected radio button as the package to be delivered (step S583). In this process, if the number of packages classified into the additional condition-matching group corresponding to the selected radio button (i.e., the additional condition-matching group to which the package card placed to the right of the radio button belongs) is one, the control unit 140 of the driver terminal 40 identifies that one package as the package to be delivered, and if the number of packages classified into the additional condition-matching group corresponding to the selected radio button is two or more, the control unit 140 identifies all of the multiple packages as the package to be delivered. As a result, when a radio button is selected, the packages corresponding to that radio button (all of them regardless of the number of packages) are confirmed as the packages to be delivered.

[0202] Next, the control unit 140 of the driver terminal 40 enables the delivery selection instruction button (step S584). In this process, the control unit 140 of the driver terminal 40 displays a delivery selection instruction button image in the scan selection area 203 of the display unit 142. As described above, in the example shown in FIG. 31, the radio button 350c is selected, thereby selecting the additional condition-matching group (third additional condition-matching group) to which the slip number corresponding to the package card 320e belongs. As a result, the delivery selection instruction button is enabled, and the delivery selection instruction button image is displayed in the scan selection area 203. In this state, the driver can input a delivery selection instruction by operating the operation input unit 143.

[0203] If it is determined in step S581 that the package to be delivered has been identified, or after executing the processing of step S584, the control unit 140 of the driver terminal 40 executes the unloading processing (step S585). The unloading processing will be described later using Figure 36. After executing the processing of step S585, the control unit 140 of the driver terminal 40 ends the delivery-related processing.

[0204] <Unloading process> Fig. 36 is a flowchart showing the unloading process Fig. 37 is a diagram showing an example of a screen during the delivery scan mode.

[0205] The unloading process shown in FIG. 36 is a process carried out by the driver terminal 40 in step S585 of FIG. 35 (delivery-related process).

[0206] In the unloading process, first, the control unit 140 of the driver terminal 40 sets the invoice number of the package identified as the package to be delivered (step S601). In this process, the control unit 140 of the driver terminal 40 stores the invoice number information corresponding to the package identified in step S543 of FIG. 27 or step S583 of FIG. 35 in a predetermined area (checklist information storage area) provided in the memory unit 141 (e.g., RAM). At this time, if there are multiple packages identified in step S543 of FIG. 27 or step S583 of FIG. 35, the control unit 140 of the driver terminal 40 stores the invoice number information for all of the packages in the checklist information storage area. The checklist information storage area is a storage area provided separately from the delivery destination information storage area.

[0207] Next, the control unit 140 of the driver terminal 40 sets the number of unscanned packages D to D=M (initial value) (step S602). Here, M is the number of packages identified in step S543 of FIG. 27 or step S583 of FIG. 35, and is the number of slip numbers set in step S601. When the number of packages identified in step S543 of FIG. 27 or step S583 of FIG. 35 is M, slip number information indicating the slip numbers corresponding to each of the M packages is stored in the checklist information storage area. In other words, the number of slip numbers matches the number of packages.

[0208] Next, the control unit 140 of the driver terminal 40 executes a delivery selection instruction input reception process (step S603). In this process, the control unit 140 of the driver terminal 40 waits for a delivery selection instruction to be input. For example, the driver can input a delivery selection instruction by tapping an area on the touch panel corresponding to the display location of the delivery selection instruction button. When a delivery selection instruction is input, the control unit 140 of the driver terminal 40 transitions the process to step S604. On the other hand, if a predetermined time has passed without a delivery selection instruction being input, the control unit 140 of the driver terminal 40 may end the unloading process and also end the map selection process (see FIG. 23).

[0209] When a delivery selection instruction is input, the control unit 140 of the driver terminal 40 executes the processes of steps S604 to S606, but these processes are similar to the processes of steps S421 to S423 in Figure 9, so a description thereof will be omitted here. After executing the process of step S606, the control unit 140 of the driver terminal 40 determines whether the slip number extracted in step S606 matches the slip number set in step S601 (step S607).

[0210] In the processing of step S607, the control unit 140 of the driver's terminal 40 compares the document number (document number to be unloaded) indicated by the document number information acquired in step S606 with the document number (document number to be checked) indicated by the document number information stored in the checklist information storage area in step S601. There are M document numbers to be checked. If the document number to be unloaded matches any of the M document numbers to be checked, the determination result in step S607 will be "YES." On the other hand, if the document number to be unloaded does not match any of the M document numbers to be checked, the determination result in step S607 will be "NO."

[0211] If it is determined that the unloading target slip number matches any of the check target slip numbers, the control unit 140 of the driver terminal 40 sets the number of unscanned packages D to D = D - 1 (step S608). In this process, the control unit 140 of the driver terminal 40 subtracts 1 from the number of unscanned packages D. Then, the control unit 140 of the driver terminal 40 determines whether the number of unscanned packages D is 0 (step S609). If it is determined that the number of unscanned packages D is not 0, the control unit 140 of the driver terminal 40 proceeds to step S605. On the other hand, if it is determined that the number of unscanned packages D is 0, the control unit 140 of the driver terminal 40 executes delivery completion-related processing (step S610). The delivery completion-related processing will be described later with reference to FIG. 38. After executing the processing of step S610, the control unit 140 of the driver terminal 40 ends the unloading processing.

[0212] If it is determined in step S607 that the unloading target form number does not match any of the check target form numbers, the control unit 140 of the driver terminal 40 performs error processing (step S611). In this processing, the control unit 140 of the driver terminal 40 displays a pop-up error image (e.g., a text image indicating that the unloading target form number and the check target form number do not match) on the display unit 142 and disables the camera (the delivery app disables the camera). As described above, the pop-up display is displayed as a window in a portion of the screen of the display unit 142, and the display ends when the cancel button is tapped (the window corresponding to the error image is closed). Performing this error processing disables the imaging unit 144 from capturing a two-dimensional code image. When the window corresponding to the error image is closed, the control unit 140 of the driver terminal 40 proceeds to step S604. This enables the two-dimensional code image to be captured again.

[0213] As described above, the processing of steps S605 to S609 is repeated until the number of unscanned packages D becomes 0. Here, the processing of steps S605 to S609 will be referred to as the delivery scan processing. Figure 37 shows a delivery scan mode screen that is displayed on the display unit 142 when radio button 350a is selected in the state shown in Figure 29 (the additional condition matching group (first additional condition matching group) to which the slip number corresponding to package card 320a belongs is selected). When the camera is enabled in step S604, the system is controlled to the delivery scan mode. The delivery scan mode screen is the screen that is displayed in the delivery scan mode.

[0214] As described above, the number of slip numbers belonging to the first additional condition-matching group is three. The three slip numbers are "1000-0000-0491," "1000-0000-0492," and "1000-0000-0493." In this example, slip number information indicating these three slip numbers is stored in the checklist information storage area (see step S601), which essentially results in the delivery scan process being performed three times. Figure 37 shows the delivery scan mode screen when the determination result in step S607 during the first delivery scan process is "YES."

[0215] As shown in Fig. 37, the delivery scan mode screen has a photographing target display area 261, a cancel instruction input area 263, a slip number display area 264, a checklist display area 266, and a delivery scan completion instruction input area 267. The photographing target display area 261, the cancel instruction input area 263, and the slip number display area 264 have been described above (see Fig. 21), so their description will be omitted here. The checklist display area 266 is an area where the slip number set in step S601 is displayed. In this example, the slip numbers "1000-0000-0491," "1000-0000-0492," and "1000-0000-0493" are displayed. Since the slip number extracted in step S606 in the first delivery scanning process is "1000-0000-0491", the display mode of "1000-0000-0491" displayed in the checklist display area 266 has changed.

[0216] The delivery scan completion instruction input area 267 is an area where an image corresponding to a button containing the words "Next" (delivery scan completion instruction button) is displayed. Although not shown, when the determination result in step S609 is "YES," the driver can operate the operation input unit 143 to input an instruction to select the delivery scan completion instruction button in the delivery scan completion instruction input area 267 (delivery scan completion instruction input). In the state shown in FIG. 37, the number of unscanned packages D has not yet reached 0, and the driver cannot input a delivery scan completion instruction. In the figure, the outer edge of the delivery scan completion instruction input area 267 is displayed with a dotted line, indicating that operations on the delivery scan completion instruction input area 267 are invalid. When the number of unscanned packages D reaches 0, operations on the delivery scan completion instruction input area 267 become valid. Note that the number of unscanned packages D may be displayed on the screen during delivery scan mode so that the driver can visually confirm the number.

[0217] While the processes of steps S605 to S609 are repeated, the imaging unit 144 (camera) remains activated (a state in which a two-dimensional code image can be captured as long as the two-dimensional code or the like is within the guidelines). Therefore, in delivery scan mode, if there are multiple slip numbers to be checked, after capturing a two-dimensional code or the like printed on a shipping label affixed to one package, it is possible to capture a two-dimensional code or the like printed on a shipping label affixed to another package without having to reactivate the imaging unit 144 (camera), and two-dimensional codes or the like can be captured continuously for multiple packages. However, this is not a limitation. For example, a specific message (window) may be popped up each time a two-dimensional code or the like for one package is captured, and the driver may close the window, allowing the driver to capture a two-dimensional code or the like for the next package. Alternatively, a specific message (window) may be displayed as a toast each time a two-dimensional code or the like for one package is captured. As described above, when the toast display is configured to be displayed in this manner, the continuous capturing of two-dimensional codes, etc., is not interrupted by the toast display, and the imaging unit 144 can continue to capture two-dimensional code images.

[0218] Note that if the slip number extracted in step S606 in one delivery scanning process is the same as the slip number extracted in step S606 in a previous delivery scanning process, the determination result in step S607 may be "NO." The error image displayed in this case (for example, a message such as "This slip number is the same as the slip number already scanned") may be a pop-up display or a toast display. Alternatively, if the slip number extracted in step S606 in one delivery scanning process is the same as the slip number extracted in step S606 in a previous delivery scanning process, the determination result in step S607 may be "YES," and the process of step S609 may be performed without performing the process of step S608.

[0219] Furthermore, the checklist display area 266 may be configured so that, of the slip numbers set in step S601, only those that have not yet been extracted in step S606 are displayed, and slip numbers that have already been extracted in step S606 are not displayed. In this case, for example, slip number information indicating slip numbers that have already been extracted in step S606 may be deleted from the checklist information storage area. When such a configuration is adopted, if the slip number extracted in step S606 in one delivery scanning process is the same as the slip number extracted in step S606 in an already performed delivery scanning process, the determination result in step S607 can be set to "NO."

[0220] FIG. 37 also illustrates a case where there are multiple document numbers to be checked. It is possible to configure the system so that a delivery scan mode screen similar to that shown in FIG. 37 is displayed even when there is only one document number to be checked. Alternatively, the system may be configured so that a single scan mode screen is displayed when there is only one document number to be checked. As described above, the single scan mode screen is essentially the same as the continuous scan mode screen shown in FIG. 21, with the text image "Single Shooting" highlighted in the scan mode display area 262. For example, when the camera is enabled in step S604, the system may be controlled to delivery scan mode if there are multiple document numbers to be checked, but may be controlled to single scan mode if there is only one document number to be checked.

[0221] <Delivery completion related processing> Fig. 38 is a flowchart showing delivery completion-related processing on the driver terminal side and delivery completion-related processing on the logistics management server side. Fig. 39 is a diagram showing an example of a delivery action selection screen. Fig. 40 is a diagram showing an example of a screen when inputting a receiving instruction. Fig. 41 is a diagram showing an example of a receiving completion screen. Figs. 42 and 43 are diagrams showing examples of a screen when inputting a return instruction.

[0222] The delivery completion related processing on the driver terminal side is processing performed on the driver terminal 40 when the number of unscanned packages D becomes 0 (step S610 in Figure 36 (unloading processing)). The delivery completion related processing on the logistics management server side is processing performed on the logistics management server 20 when the number of unscanned packages D becomes 0. Note that Figure 37 assumes that the transition to the delivery completion related processing on the driver terminal side is made on the condition that a delivery scan completion instruction is input. However, when the judgment result in step S609 is "YES", the delivery completion related processing on the driver terminal side may also be performed without the need to input a delivery scan completion instruction.

[0223] In the delivery completion related processing on the driver terminal side, the control unit 140 of the driver terminal 40 executes the processing of steps S621 to S624 shown in Figure 38. In the delivery completion related processing on the logistics management server side, the control unit 110 of the logistics management server 20 executes the processing of steps S301 to S303 shown in Figure 38.

[0224] Specifically, in the driver terminal-side delivery completion-related processing, first, the control unit 140 of the driver terminal 40 executes a delivery action selection operation reception process (step S621). In this process, the control unit 140 of the driver terminal 40 displays a delivery action selection screen, a screen for inputting a receipt instruction, a screen for inputting a return instruction, etc. on the display unit 142, and waits for any of the following to be input via the operation input unit 143: a delivery completion transition instruction, an absence transition instruction, a receipt refusal transition instruction, an under investigation transition instruction, or a warehouse storage (return) transition instruction.

[0225] As shown in FIG. 39, the delivery action selection screen has a package information display area 401, a receipt instruction input area 402, a return instruction input area 403, a drop-off instruction input area 404, a postbox instruction input area 405, and a delivery box instruction input area 406. Package information display area 401 is an area where an image showing letters or numbers corresponding to package information (e.g., slip number, expected delivery date, delivery time zone, number of parcels, package size, delivery address, delivery name, delivery name (kana), title, etc.) is displayed. Package instruction input area 402 is an area where an image corresponding to a button containing the character "RECEIVE" (receive instruction button) is displayed. Package return instruction input area 403 is an area where an image corresponding to a button containing the character "RETURN" (drop-off instruction button) is displayed. Package delivery instruction input area 404 is an area where an image corresponding to a button containing the character "LEAVED" (LEAVED instruction button) is displayed. Postbox instruction input area 405 is an area where an image corresponding to a button containing the characters "Postbox" (postbox instruction button) is displayed. Delivery box instruction input area 406 is an area where an image corresponding to a button containing the characters "Delivery box" (delivery box instruction button) is displayed.

[0226] When the delivery action selection screen is displayed, the driver can operate the operation input unit 143 to input an input to select the reception instruction button in the reception instruction input area 402 (reception instruction input), an input to select the return instruction button in the return instruction input area 403 (return instruction input), an input to select the leave instruction button in the drop-off instruction input area 404 (drop-off instruction input), an input to select the post delivery instruction button in the post delivery instruction input area 405 (post delivery instruction input), or an input to select the delivery box instruction button in the delivery box instruction input area 406 (delivery box instruction input). Note that the package information displayed in the package information display area 401 is the same information (for example, delivery destination summary information) as that displayed on the package card.

[0227] When a receiving instruction is input on the delivery action selection screen, the receiving instruction input screen shown in FIG. 40 is displayed. The receiving instruction input screen has a signature input area 411 and a delivery completion transition instruction input area 412. The signature input area 411 is an area for inputting a signature. The delivery completion transition instruction input area 412 is an area for displaying an image corresponding to a button containing the word "Complete" (delivery completion transition instruction button). When the receiving instruction input screen is displayed, the driver can have the customer input a receipt signature in the signature input area 411 by handing the driver terminal 40 to the customer. Furthermore, on the condition that a signature has been input in the signature input area 411, the driver can operate the operation input unit 143 to input an input indicating that the delivery completion transition instruction button is selected in the delivery completion transition instruction input area 412 (delivery completion transition instruction input).

[0228] In the state shown in FIG. 40, a signature has not yet been entered, and the driver cannot input a delivery completion transition instruction. In the figure, the outer edge of the delivery completion transition instruction input area 412 is displayed with a dotted line, indicating that operations in the delivery completion transition instruction input area 412 are invalid. When a signature is entered in the signature input area 411, operations in the delivery completion transition instruction input area 412 become valid. When a delivery completion transition instruction is input on the receipt instruction input screen, the receipt completion screen shown in FIG. 41 is displayed. The receipt completion screen displays a receipt completion mark 415 and a text image stating "Package receipt has been completed." Inputting a delivery completion transition instruction corresponds to an operation of selecting "Delivery Completed" as the transition status. When a delivery completion transition instruction is input, the delivery status of the package transitions to "Delivery Completed" (see step S302 in FIG. 38). The receipt completion screen also includes a close instruction input area 416. The close instruction input area 416 is an area where an image corresponding to a button containing the word "close" (the "Close" button) is displayed. When the receipt completion screen is displayed, the driver can input an instruction to select the "close" button (input a "close" instruction) in the close instruction input area 416 by operating the operation input unit 143. However, even if the "close" instruction is input on the receipt completion screen, the continuous reading confirmation image (see FIG. 20) is not displayed, and in this case, the device is not controlled to the continuous scan mode.

[0229] When a return instruction is input on the delivery action selection screen, the return instruction input screen shown in FIG. 42 is displayed. The return instruction input screen has a return reason selection area 421, a return reason detail input area 422, and a return reason confirmation input area 423. As shown in FIG. 43, on the return instruction input screen, the return reason selection area 421 can display a pull-down menu of "absent," "delivery box full / oversized," "refused to receive," "under investigation," "address / customer name unknown," and "other." The return reason detail input area 422 is an area for entering details of the return reason. The return reason confirmation input area 423 is an area for displaying an image corresponding to a button containing the word "complete" (return reason confirmation button).

[0230] When the screen for inputting instructions to bring back is displayed, the driver can operate the operation input unit 143 to select one of "absent," "delivery box full / oversize," "refused to receive," "under investigation," "address / customer name unknown," and "other" in the reason for bringing back selection area 421. In addition, the driver can operate the operation input unit 143 to input an instruction to select the reason for bringing back confirmation button in the reason for bringing back confirmation input area 423 (input of reason for bringing back confirmation).

[0231] When the reason for return is confirmed and "absent" or "delivery box full / oversize" is selected in the reason for return selection area 421, inputting the reason for return means that an instruction to switch to "absent" will be input; when the reason for return is confirmed and "refusal to receive" is selected in the reason for return selection area 421, inputting the reason for return means that an instruction to switch to "refusal to receive" will be input; when the reason for return is confirmed and "under investigation" or "address and customer name unknown" is selected in the reason for return selection area 421, inputting the reason for return means that an instruction to switch to "under investigation" will be input; and when the reason for return is confirmed and "other" is selected in the reason for return selection area 421, inputting the reason for return means that an instruction to switch to warehouse storage (return) will be input.

[0232] Inputting an instruction to transition to "absent" corresponds to an operation of selecting "absent" as the destination status, inputting an instruction to transition to "rejected receipt" corresponds to an operation of selecting "rejected receipt" as the destination status, inputting an instruction to transition to "under investigation" corresponds to an operation of selecting "under investigation" as the destination status, and inputting an instruction to transition to warehouse storage (return) corresponds to an operation of selecting "warehouse storage (return)" as the destination status. When an instruction to transition to "absent" is input, the delivery status of the package is transitioned to "absent", when an instruction to transition to "rejected receipt" is input, the delivery status of the package is transitioned to "rejected receipt", when an instruction to transition to "under investigation" is input, the delivery status of the package is transitioned to "under investigation", and when an instruction to transition to warehouse storage (return) is input, the delivery status of the package is transitioned to "warehouse storage (return)" or "designated date storage (return)" (see step S302 in FIG. 38).

[0233] Furthermore, when the delivery action selection screen is displayed, if a drop-off instruction is input, a drop-off instruction input screen is displayed; if a postbox instruction is input, a postbox instruction input screen is displayed; and if a delivery box instruction is input, a delivery box instruction input screen is displayed. Although not shown, the drop-off instruction input screen, postbox instruction input screen, and delivery box instruction input screen each have a delivery completion transition instruction input area 412, similar to the receipt instruction input screen. When the drop-off instruction input screen, postbox instruction input screen, or delivery box instruction input screen is displayed, the driver can input a delivery completion transition instruction by operating the operation input unit 143. Note that, on these screens, it is desirable to configure the screen so that operations on the delivery completion transition instruction input area 412 are enabled on the condition that predetermined inputs are made (for example, on the delivery box instruction input screen, input of the delivery box box number and PIN number, and input of an image obtained by taking a photograph of the package placed in the delivery box). Alternatively, operations on the drop-off instruction input area 404, post-mail instruction input area 405, or delivery box instruction input area 406 may be made valid on the condition that article information indicating an article (comment) stating that drop-off, postage, or delivery to a delivery box is permitted is included in the luggage information held on the driver's terminal.

[0234] On the above screens, when an instruction to transition to delivery completion, absence, refusal, investigation, or warehouse storage (return) is input, the control unit 140 of the driver terminal 40 ends the delivery action selection operation reception process and proceeds to step S622 in Figure 38. On the other hand, when a predetermined time has passed without any of these inputs being made, the control unit 140 of the driver terminal 40 may end the delivery action selection operation reception process and terminate the driver terminal-side delivery completion-related process.

[0235] In the above description, it has been explained that when the number of unscanned packages D becomes 0, a delivery action selection screen, a screen for inputting receipt instructions, a screen for inputting return instructions, etc. are displayed. However, even when the number of unscanned packages D is 1 or more, these screens may be displayed by performing a predetermined operation (accepting input of a delivery completion transition instruction, an absence transition instruction, a receipt refusal transition instruction, an investigation transition instruction, or a warehouse storage (return) transition instruction). For example, even when the determination result of step S609 in FIG. 36 is "NO," it may be possible to input a delivery scan completion instruction in the delivery scan completion instruction input area 267 (see FIG. 37), and when the delivery scan completion instruction is input when the determination result of step S609 is "NO," error processing may be performed (for example, an error image indicating that the number of unscanned packages D is 1 or more may be displayed as a pop-up). The error image is displayed as a window (dialog), and the dialog displays a message such as "Do you want to proceed with delivery?" along with text images corresponding to "Yes" and "No." When "Yes" is selected, a delivery action selection screen may be displayed. A screen for the driver to input notes may be displayed, and the delivery action selection screen may be displayed only if the note (e.g., the packages are too large to be transported together) is entered. Alternatively, the driver may report the situation to a manager, and the manager may perform a predetermined operation on the manager terminal 30. Error resolution information for allowing delivery to proceed even if the number of unscanned packages D is one or more may be transmitted from the manager terminal 30 to the driver terminal 40 (via the logistics management server 20). The delivery action selection screen may be displayed when the error resolution information is received. This allows for flexible operation when there are multiple packages classified into a single additional condition-matching group, and even if it is not possible to photograph the two-dimensional codes or the like for some of the packages, it is possible to leave room for completing the delivery of the remaining packages, thereby achieving flexible operation.

[0236] After executing the process of step S621, the control unit 140 of the driver terminal 40 transmits information indicating the destination status selected in the delivery action selection operation reception process (destination status information) to the logistics management server 20 via the communication unit 145 (step S622). The control unit 140 of the driver terminal 40 also transmits information indicating the slip number obtained in step S606 of FIG. 36 (slip number information) to the logistics management server 20 via the communication unit 145. Specifically, if the delivery scanning process is performed only once, the control unit 140 of the driver terminal 40 transmits to the logistics management server 20 information indicating the slip number to be unloaded (which was compared with the slip number to be checked) when the determination result in step S607 is "YES". If the delivery scanning process is performed multiple times, the control unit 140 transmits to the logistics management server 20 information indicating all slip numbers to be unloaded (which were compared with the slip number to be checked) when the determination result in step S607 is "YES". Alternatively, the control unit 140 of the driver terminal 40 may transmit the slip number information stored in the checklist information storage area in step S601 to the logistics management server 20. As a result, when the number of packages identified in step S543 of FIG. 27 or step S583 of FIG. 35 is M, slip number information indicating the slip numbers corresponding to the M packages (all M slip numbers) is transmitted to the logistics management server 20.

[0237] In the delivery completion-related process on the logistics management server side, the control unit 110 of the logistics management server 20 receives the destination status information and slip number information transmitted from the driver terminal 40 via the communication unit 112 (step S301). Next, the control unit 110 of the logistics management server 20 updates the delivery status based on the received destination status information and slip number information (step S302). In this process, if the destination status information corresponds to "Delivery Completed," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information (all M slip numbers) to "Delivery Completed" in the package information table 121. "Delivery Completed" corresponds to a state in which delivery of the package has been successfully completed. Furthermore, if the destination status information corresponds to "Absent," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information (all M slip numbers) to "Absent" in the package information table 121. "Not at Home" corresponds to a situation where the driver arrived at the delivery destination but the customer was not there.

[0238] Furthermore, if the destination status information corresponds to "rejected receipt," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information (all M slip numbers) to "rejected receipt" in the package information table 121. "Rejected receipt" corresponds to a state in which the driver has arrived at the delivery destination but the recipient has refused to receive the package. Furthermore, if the destination status information corresponds to "under investigation," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information (all M slip numbers) to "under investigation" in the package information table 121. "Under investigation" corresponds to a state in which some kind of problem has occurred and an investigation is being conducted. Furthermore, if the destination status information corresponds to "warehouse storage (return)," the control unit 110 of the logistics management server 20 sets the delivery status corresponding to the slip number information (all M slip numbers) to "warehouse storage (return)" or "designated date storage (return)" in the package information table 121. The "warehouse storage (return)" to "designated date storage (return)" are as described above, so a description thereof will be omitted here.

[0239] In this way, if there are multiple parcels identified in step S543 of FIG. 27 or step S583 of FIG. 35, the delivery statuses of these parcels are updated collectively, and the updated delivery statuses of all of these parcels become the same. Furthermore, although not shown, if the destination status information corresponds to "delivery completed," data corresponding to the customer's receipt signature (receipt signature data) is also transmitted from the driver terminal 40 to the logistics management server 20 along with the destination status information. If there are multiple parcels identified in step S543 of FIG. 27 or step S583 of FIG. 35, the customer's receipt signature for these parcels also becomes the same, and the same receipt signature data is registered and stored for each parcel. After executing the process of step S302, the control unit 110 of the logistics management server 20 transmits information indicating the delivery status after the update in step S302 (delivery status information) to the driver terminal 40 via the communication unit 112 (step S303). After executing the process of step S303, the control unit 110 of the logistics management server 20 ends the delivery completion related process on the logistics management server side.

[0240] In the driver terminal-side delivery completion-related processing, after executing the processing of step S622, the control unit 140 of the driver terminal 40 receives delivery status information transmitted from the logistics management server 20 via the communication unit 145 (step S623). Then, the control unit 140 of the driver terminal 40 determines whether the delivery status of the parcel to be processed is a final status (step S624). The parcel to be processed is the parcel identified in step S543 of FIG. 27 or step S583 of FIG. 35. As described above, the final statuses are "Delivery Complete," "Rejection," "Return," and "Parcel Accident." If the delivery status information received in step S623 corresponds to any of the delivery statuses "Delivery Complete," "Rejection," "Return," and "Parcel Accident," the determination result in step S624 is "YES." On the other hand, if the delivery status information received in step S623 corresponds to a delivery status other than "Delivery Complete," "Rejection," "Return," and "Parcel Accident," the determination result in step S624 is "NO."

[0241] If it is determined in step S624 that the delivery status of the package is final, the control unit 140 of the driver terminal 40 erases the package information held on the driver terminal side corresponding to the package (step S625). In this process, the control unit 140 of the driver terminal 40 deletes the package information held on the driver terminal side that is stored in association with the package's shipping slip number information in the delivery destination information storage area of ​​the memory unit 141. If it is determined in step S624 that the delivery status of the package is not final, or after executing the process of step S625, the control unit 140 of the driver terminal 40 executes a delivery remaining process (step S626). The delivery remaining process will be described later using FIG. 44. After executing the process of step S626, the control unit 140 of the driver terminal 40 terminates the driver terminal side delivery completion related process.

[0242] <Remaining delivery processing> FIG. 44 is a flowchart showing the remaining delivery process.

[0243] The remaining delivery process shown in FIG. 44 is a process carried out in the driver terminal 40 in step S626 of FIG. 38 (delivery completion related process on the driver terminal side).

[0244] Although not explained above, if it is determined in step S581 of Figure 35 that the package to be delivered has already been identified, the control unit 140 of the driver terminal 40 sets H=1 (initial value) as the remaining number of doorsteps H before executing the processing of step S585. On the other hand, if it is determined in step S581 of Figure 35 that the package to be delivered has not already been identified, the control unit 140 of the driver terminal 40 sets H=N (initial value) as the remaining number of doorsteps H before executing the processing of step S582. N is the number of additional condition-matching groups that belong to the geotag-matching group corresponding to the pin selected in step S502 of Figure 23, and is the number of doorsteps counted in step S524 of Figure 24.

[0245] In the remaining delivery processing, first, the control unit 140 of the driver terminal 40 sets the remaining number of doorsteps H to H=H-1 (step S641). In this processing, the control unit 140 of the driver terminal 40 subtracts 1 from the remaining number of doorsteps H. Then, the control unit 140 of the driver terminal 40 determines whether the remaining number of doorsteps H is 0 (step S642). If it is determined that the remaining number of doorsteps H is 0, the control unit 140 of the driver terminal 40 determines whether all of the package information held on the driver terminal side associated with the pin being processed has been deleted (step S643). The pin being processed is the pin selected in step S502 of FIG. 23.

[0246] When the process of step S625 in FIG. 38 is executed and all of the driver terminal-held package information associated with the pin is deleted from the delivery destination information storage area, the determination result of step S643 is "YES." On the other hand, when some of the driver terminal-held package information associated with the pin remains stored in the delivery destination information storage area, the determination result of step S643 is "NO." When the determination result of step S643 is "YES," the control unit 140 of the driver terminal 40 ends the display of the pin in the map display area 200 (step S644). This erases the pin from the map. After executing the process of step S644, the control unit 140 of the driver terminal 40 ends the remaining delivery process. On the other hand, when the determination result of step S643 is "NO," the control unit 140 of the driver terminal 40 maintains the display of the pin in the map display area 200 and ends the remaining delivery process.

[0247] If it is determined in step S642 that the remaining number of doors H is not 0, the control unit 140 of the driver terminal 40 determines whether the remaining number of doors H is 1 (step S645). If it is determined that the remaining number of doors H is 1, the control unit 140 of the driver terminal 40 identifies the package corresponding to that one door as the package to be delivered (step S646). In this process, if there is one package classified into an additional condition-matching group that has not yet been subject to the unloading process (see FIG. 36), the control unit 140 of the driver terminal 40 identifies that one package as the package to be delivered. If there are two or more packages classified into that additional condition-matching group, the control unit 140 identifies all of the multiple packages as the packages to be delivered. After executing the process of step S646, the control unit 140 of the driver terminal 40 proceeds to step S584 of FIG. 35. On the other hand, if it is determined in step S645 that the remaining number of eaves ends H is not 1, the control unit 140 of the driver terminal 40 moves the process to step S582 in FIG.

[0248] For example, assume that there are five packages corresponding to the pin (geotag-matching group) being processed, three packages classified into the first additional condition-matching group, one package classified into the second additional condition-matching group, and one package classified into the third additional condition-matching group (see FIG. 29). In this example, when radio button 350a is selected, the three packages classified into the first additional condition-matching group are identified as packages to be delivered (see step S583 in FIG. 35), and unloading processing is performed for the first additional condition-matching group. Thereafter, when radio button 350b is selected, one package classified into the second additional condition-matching group is identified as a package to be delivered (see step S583 in FIG. 35), and unloading processing is performed for the second additional condition-matching group. Then, when the unloading processing for the second additional condition-matching group is completed, one package classified into the third additional condition-matching group is identified as a package to be delivered (see step S646 in FIG. 44), and unloading processing is performed for the third additional condition-matching group. When the unloading process for the third additional condition matching group is completed, if the delivery status of all five packages corresponding to the pin is final, the pin will disappear from the map.

[0249] As described above, the driver can use the driver terminal 40 to enter various inputs to update the delivery status of a package. The delivery statuses "Confirmed receipt," "Warehouse storage," "Storage for a specified date," "Removal," "Return," "Under investigation," "Warehouse storage (return)," "Storage for a specified date (return)," and "Handover" can be changed to these statuses by inputting a scan selection instruction (see step S405 in FIG. 7). On the other hand, the delivery statuses "Delivery completed," "Absent," and "Rejected delivery" can be changed to these statuses by inputting a delivery selection instruction (see step S603 in FIG. 36). The delivery statuses "Package accident" and "Return instruction" cannot be changed to these statuses using the driver terminal 40. "Package accident" corresponds to a state in which a problem such as damage has occurred with the package. "Return instruction" corresponds to a state in which an instruction has been given to return the package to the shipper (a preparation stage for the procedure to return the package to the shipper).

[0250] On the other hand, the administrator can input one slip number into the operation input unit 133 of the administrator terminal 30 at any timing (delivery status) after receipt is confirmed, to display a screen (delivery status update screen) for updating the delivery status corresponding to that slip number on the display unit 132, and while the delivery status update screen is displayed, various inputs can be made to update the delivery status of the package for that slip number. By using the administrator terminal 30, it is possible to transition to all delivery statuses.

[0251] If a package is delivered to the destination but the customer is not at home, the driver returns the package to the warehouse, and the package's delivery status changes to "warehouse storage (returned)" or "designated date storage (returned)." The package is then stored in the warehouse, but the manager or driver may voluntarily pick the package and remove it, taking into account the delivery route for that day, and attempt redelivery. At that time, the package's delivery status changes to "returned." In this process, the series of events in which the package's delivery status changes from "returned" to "warehouse storage (returned)" or "designated date storage (returned)" (due to the customer's absence) is called an "attack." If a package has been "attacked" a predetermined number of times (e.g., three times) within a week, but the package's delivery status does not change to "delivered," the manager reports the situation to the shipper and, based on the shipper's instructions, changes the package's delivery status to "returned." This actually initiates the process of returning the package to the shipper.

[0252] The number of "attacks" (attack count) can be calculated by counting the number of times the delivery status of a parcel changes from "absent" to "warehouse storage (returned)" or "designated date storage (returned)." For example, the logistics management server 20 can be configured to count the number of attacks for each parcel, and the display unit 132 of the manager terminal 30 can display the number of attacks along with the parcel's shipping slip number. Furthermore, if the number of attacks for a parcel reaches a predetermined number (e.g., three), the driver may be prevented from changing the parcel's delivery status to "taken out" by scanning the parcel's two-dimensional code. In this case, an alert message such as "This parcel has already been redelivered three times" can be displayed on the driver terminal 40, improving operational safety and efficiency. This alert function immediately notifies the driver of the redelivery status and ensures that the parcel can be properly processed (e.g., returned to the shipper) after proper manager confirmation.

[0253] In the first embodiment, the above-mentioned processes are described as being performed in the logistics management server 20, the manager terminal 30, the driver terminal 40, and the shipper server 50. However, each process according to the first embodiment is merely an example, and appropriate design changes can be made to realize the functions (logistics management) of the logistics management system 10. For example, a process described as being performed by one device can naturally be configured to be performed by another device.

[0254] For example, in the first embodiment, the grouping process (see, for example, steps S522 and S523 in FIG. 24) is described as being performed by the driver terminal 40, but similar processes may be performed by the logistics management server 20. For example, the control unit 110 of the logistics management server 20 may be configured to perform grouping for each package based on geotag information (latitude and longitude) as a criterion (matching condition), and further perform grouping based on the name of the delivery destination apartment / condominium and the delivery destination name as criteria (matching conditions) in addition to the geotag information (latitude and longitude). By transmitting information indicating the resulting geotag-matching groups or additional-condition-matching groups from the logistics management server 20 to the driver terminal 40, it is possible to perform processes similar to those shown in FIG. 27 (pin information acquisition process) and FIG. 35 (delivery-related process) described in the first embodiment on the driver terminal 40.

[0255] In the cases where the grouping process is performed by the driver terminal 40 and where the grouping process is performed by the logistics management server 20, there are no particular limitations on the timing at which the process is performed. For example, the grouping process may be performed by the logistics management server 20 when delivery list data is received from the shipper server 50 (see step S201 in FIG. 6), or at a predetermined time every day, or when a predetermined operation (e.g., input of an instruction to perform grouping) is performed by the administrator terminal 30, or when an operation to change the scheduled delivery date or delivery time slot is performed by the administrator terminal 30 or the customer terminal, or when the driver departs from the warehouse (under circumstances where it can be determined that the driver has departed from the warehouse), the grouping process may be performed by the logistics management server 20 or the driver terminal 40. The method for determining that the driver has departed from the warehouse is not particularly limited. For example, the logistics management server 20 or the driver terminal 40 may determine this when the current location (the location of the driver terminal 40) moves a predetermined distance away from the warehouse, or the logistics management server 20 or the driver terminal 40 may determine this when a predetermined operation (departure operation) is performed on the driver terminal 40. Examples of the departure operation include pressing a departure button (not shown) or inputting a cancel instruction for the continuous scan to change the delivery status to "take-out" (see step S484 in FIG. 17). The grouping process may be performed on all packages included in the delivery list data, or on some of the packages (for example, packages handled by a single warehouse).

[0256] If the grouping process has already been performed when the driver departs from the warehouse, for example, when the driver performs a predetermined operation (for example, inputting a cancel instruction for the continuous scan to change the delivery status to "take-out") when departing from the warehouse, the following processes (x) and (y) can be configured to be executed. Alternatively, the following process (z) can be configured to be executed. (x) When there are multiple packages classified into one additional condition matching group, it is determined whether the delivery status of all of the multiple packages has been updated to "take out." (y) In the above (x), if it is determined that the delivery status of some of the multiple packages has not been updated to "take-out", a message indicating this is displayed on the display unit 142 of the driver terminal 40. (z) In the above (x), if it is determined that the delivery status of all of the multiple packages has been updated to "take-out", a departure button is displayed on the display unit 142 of the driver terminal 40.

[0257] The departure button can be configured as an image corresponding to a button containing the word "departure," for example. When the determination result of (x) above is "YES," the departure button is enabled (the departure button thereby serves as a sign indicating that the driver is permitted to depart), and the driver can input to select the departure button by operating the operation input unit 143. The processing of (x) above may be performed in the logistics management server 20 or in the driver terminal 40. When the processing of (x) above is performed in the driver terminal 40, the control unit 140 of the driver terminal 40 can recognize that the delivery status of each package has been updated to "take-out" by referring to the package information held on the driver terminal side that is stored in the delivery destination information storage area.

[0258] Although various types of errors have been described above, the manner in which an error is notified is not particularly limited. For example, in addition to displaying an error image as a pop-up or a toast message, sound may be output from a speaker or vibration may be generated. The output manner of images, sounds, and vibrations can be varied depending on the type of error, and it is desirable to configure the system so that the driver can recognize the presence or absence of an error and its type through the senses of sight, hearing, and touch by combining images, sounds, and vibrations. For example, from the perspective of preventing erroneous delivery of luggage, an error may be notified using images, sounds, and vibrations in error processing during unloading (see FIG. 36). Furthermore, the sound output when an error occurs may be different from the sound output when no error occurs. For example, if the judgment result of step S489 in Figure 18 is "YES", a predetermined sound (for example, a sound corresponding to the delivery status of the package being updated to "take out") is output, whereas if the judgment result of step S489 is "NO", a different sound (an error sound) can be output.

[0259] Second Embodiment The first embodiment has been described above. The second embodiment will now be described. The basic configuration of the logistics management system 10 according to the second embodiment is the same as that of the logistics management system 10 according to the first embodiment. In the following, components that are the same as those of the logistics management system 10 according to the first embodiment will be basically described using the same reference numerals. Furthermore, explanations of parts that apply to the second embodiment as well as the first embodiment will be omitted.

[0260] In the above description, even if there is a statement that is limited to the logistics management system 10 according to the first embodiment, such as "in the first embodiment...", it can also be applied to the logistics management system 10 according to the second embodiment within the scope of the second embodiment. Therefore, each configuration shown in the first embodiment (including each configuration shown in the modified example) can be partially replaced with or combined with the configuration shown in the second embodiment.

[0261] Furthermore, even if the configuration is different from that of the logistics management system 10 according to the first embodiment, the same reference numerals may be used for convenience to designate components having similar functions. Furthermore, even if the configuration is the same as that of the logistics management system 10 according to the first embodiment, different reference numerals may be used for convenience to designate components having similar functions.

[0262] In the first embodiment, an example was described in which processing related to grouping (see, for example, step S523 in FIG. 24) is performed on the driver terminal 40. In contrast, in the second embodiment, an example is described in which processing related to grouping is performed on the logistics management server 20. Note that, in the first embodiment, the description mainly focuses on the logistics process in which packages provided by one shipper are delivered to a customer, but the number of shippers that provide the packages is not particularly limited. The logistics management system 10 may also manage a logistics process in which packages provided by multiple shippers are delivered to a customer. A shipper-side server 50 can be provided for each shipper. Delivery efficiency can be improved by grouping packages from different shippers.

[0263] Of course, whether the grouping process is performed on the driver terminal 40 or the logistics management server 20 has no logical relationship with the number of shippers. The entity that performs the grouping process can be appropriately designed regardless of the number of shippers. As described in the first embodiment, the delivery company and the shipper may be the same business entity. In this case, the logistics management server 20 and the shipper-side server 50 may be configured as a single server. When the logistics management system 10 includes multiple driver terminals 40, the driver terminals 40 may be managed by the same business entity or by different business entities. For example, if the driver terminal 40p is managed by delivery company P and the driver terminal 40q is managed by delivery company Q, delivery company P and delivery company Q may each have their own logistics management system. In this case, for example, the same delivery app developed by a single business entity (e.g., the shipper) is installed on the driver terminal 40p and the driver terminal 40q. The delivery app can be linked to the logistics management systems of delivery company P and delivery company Q by dynamically applying settings (for example, API endpoints, authentication information, etc.) according to the delivery company when logging in. This allows the delivery app to respond to the business requirements of each delivery company while uniformly operating the logistics management system 10.

[0264] <Processing when receiving package information> FIG. 45 is a flowchart showing the process when package information is received.

[0265] The logistics management server 20 acquires package information from a shipper server 50x managed by one shipper (shipper X) at a predetermined timing (for example, a predetermined time on the day before the scheduled delivery date (for example, 8:00 p.m. to midnight)), and acquires package information from a shipper server 50y managed by another shipper (shipper Y) at a different timing (for example, at a non-predetermined date and time (not limited to nighttime, but including daytime hours)). The package information reception process shown in Figure 45 is a process performed by the logistics management server 20 when acquiring package information from each shipper server 50.

[0266] In addition, when there are multiple shippers who provide packages and multiple delivery companies that manage driver terminal 40, the multiple shippers and the multiple delivery companies may be different business entities, or some of the shippers (e.g., shipper X) and some of the delivery companies (e.g., delivery company P) may be the same business entity. When some of the shippers (e.g., shipper X) and some of the delivery companies (e.g., delivery company P) are the same business entity (common business entity), the business entity that manages logistics management server 20 may be the same business entity as the common business entity, or may be a business entity different from the common business entity.

[0267] In the package information reception process, first, the control unit 110 of the logistics management server 20 executes the processes of steps S1001 to S1004, but these processes are basically the same as the processes of steps S201 to S204 in Fig. 6, so a description thereof will be omitted here. Note that the data format of the delivery list data may differ depending on the shipper server 50 that is the sender of the package information, and it is possible to configure the logistics management server 20 (application server) to perform format conversion according to the data format.

[0268] Furthermore, the control unit 110 of the logistics management server 20 transmits the acquired geotag information to the administrator terminal 30, and the control unit 130 of the administrator terminal 30 generates pins (markers) corresponding to each piece of geotag information and places the generated pins on the map displayed on the display unit 132. Here, pins may not be generated properly due to variations in the spelling of the delivery address, etc. In this case, the delivery status corresponding to the relevant slip number information may be configured to be set to "under investigation."

[0269] After executing the process of step S1004, the control unit 110 of the logistics management server 20 executes grouping processing at the time of data linkage (step S1005). The grouping processing at the time of data linkage will be described later with reference to Fig. 46. After executing the process of step S1005, the control unit 110 of the logistics management server 20 ends the processing at the time of receiving package information.

[0270] <Grouping process during data integration> FIG. 46 is a flowchart showing the grouping process at the time of data linkage.

[0271] The grouping process at the time of data linkage shown in FIG. 46 is a process performed by the logistics management server 20 in step S1005 of FIG. 45 (processing at the time of receiving package information).

[0272] In the data linkage grouping process, the control unit 110 of the logistics management server 20 first filters the data (step S1021). In this process, the control unit 110 of the logistics management server 20 excludes new and existing packages that do not satisfy the grouping conditions from grouping. A new package is a package corresponding to package information stored (data linked) in the package information table 121 during the current package information reception process (see step S1002 in FIG. 45). An existing package is a package corresponding to package information that was linked during the previous package information reception process. While any grouping condition can be set, the condition adopted here is that the delivery status must be a grouping target status. The grouping target status is a delivery status other than "taken out," "delivered," "absent," "rejected," "returned," "under investigation," "package accident," and "return instruction." An additional condition may be that the package must not be held (a delivery method in which the package is not delivered but is stored at a specified location (such as a sales office) and the customer picks it up at that location). The filtering results may be cached. The cache key may include the delivery status and whether or not the hold option is used. The cache should be cleared each time the package information reception process is completed.

[0273] After executing the process of step S1021, the control unit 110 of the logistics management server 20 performs preprocessing on the expected delivery date (step S1022). In this process, if the expected delivery date for each package is a past date (before today), the control unit 110 of the logistics management server 20 converts the expected delivery date to today. In this case, the control unit 110 of the logistics management server 20 does not convert the expected delivery date itself in the original data (package information), but stores the converted expected delivery date as the expected delivery date for grouping (for example, creates a new auxiliary column and corrects a date before today to today). Note that, instead of performing such preprocessing, a logical condition may be added to consider a past date as today for the expected delivery date when grouping.

[0274] After executing the process of step S1022, the control unit 110 of the logistics management server 20 groups new packages and existing packages (step S1023). The grouping method and grouping criteria (matching conditions) are basically the same as those in the first embodiment (see step S523 in FIG. 24). For example, in the process of step S1023, the control unit 110 of the logistics management server 20 compares new packages that were not set as excluded from grouping in step S1021 with existing packages that were not set as excluded from grouping in step S1021, and performs grouping based on geotag information (latitude and longitude), delivery destination apartment / condominium name, delivery destination name, and expected delivery date for grouping as criteria (matching conditions). By using the expected delivery date for grouping, it is possible to configure the system to ignore differences between past dates and the current date. Furthermore, by performing self-comparison (self-join) within new packages, multiple packages included in the new packages can also be grouped. In addition, an index (for example, a composite index including geotag information (latitude and longitude), destination apartment name, destination name, and expected delivery date for grouping) may be appropriately designed to enable efficient processing of matching conditions in a database query. Furthermore, multiple threads may be utilized to parallelize the processing of step S1023 while avoiding conflicts between threads (for example, dividing the processing into threads according to the range of slip numbers).

[0275] After executing the process of step S1023, the control unit 110 of the logistics management server 20 assigns a group ID to the new package (step S1024). A group ID is an identification number for uniquely identifying a group of packages that meet the grouping criteria (matching conditions). For each group ID, the contents of the multiple items (grouping items) used as the grouping criteria are consistent for all packages belonging to that group ID. For example, in the process of step S1024, when the control unit 110 of the logistics management server 20 compares the multiple grouping items of a new package with the multiple grouping items of a group ID (each package belonging to that group ID), if all of the multiple grouping items match, the control unit 110 assigns the new package a group ID. On the other hand, when the control unit 110 of the logistics management server 20 compares the multiple grouping items of a new package with the multiple grouping items of each group ID, if there is no group ID in which all of the multiple grouping items match, the control unit 110 assigns a new group ID to the new package.

[0276] As described above, the multiple grouping items (matching conditions) are not particularly limited, but may include, for example, geotag information (latitude and longitude), the name of the apartment / condominium to which the package is delivered, the name of the recipient, and the expected delivery date (the difference between the current date and the past date is ignored for the expected delivery date). If no other packages satisfy the matching conditions for a package, a group ID may not be assigned to the package. For example, a system may be configured to identify groups of packages that satisfy the matching conditions and list the groups of packages. If no other packages satisfy the matching conditions for a package, the package is managed as not included in the list (a single package that does not belong to any group), and the package is excluded from being assigned a group ID.

[0277] After executing the process of step S1024, the control unit 110 of the logistics management server 20 associates multiple package information with each package if there is another package that satisfies the matching condition (step S1025). In this process, the control unit 110 of the logistics management server 20 determines, for each group ID, whether the number of packages belonging to that group ID is two or more, and stores the multiple package information in association with each package (slip number information) belonging to a group ID with the number of packages being two or more in the package information table 121. In other words, the multiple package information is information indicating that there is another package that satisfies the matching condition for the package (it is not a single package that does not belong to any group). Note that, in a configuration in which group IDs are not assigned to single packages, the assignment of a group ID and the association of multiple package information with each package are synonymous.

[0278] After executing the process of step S1025, the control unit 110 of the logistics management server 20 ends the grouping process at the time of data linkage. Note that the control unit 110 of the logistics management server 20 can be configured to end the grouping process at the time of data linkage on the condition that all new packages have been assigned a group ID (or managed as a single package) or have been set as not being subject to grouping.

[0279] As described above, for example, when the delivery status of one package is "taken out" and data linkage is performed for another package, the package is set as not being subject to grouping (see step S1021), and the same group ID is not assigned to the package and the other package (even if all grouping items for these packages match). As explained in the first embodiment, the timing for executing the grouping process is not particularly limited, and for example, the grouping process may be executed when the delivery status of one package is updated to a predetermined delivery status.

[0280] For example, when the delivery status of a package is updated (after executing the processing of step S242 in FIG. 10, step S265 in FIG. 18, or step S302 in FIG. 38), if the updated delivery status is either "warehouse storage (return)" or "designated date storage (return)," the control unit 110 of the logistics management server 20 can be configured to perform processing similar to that shown in FIG. 46. In this case, the grouping may be performed by regarding any day prior to today (including today) as the next day for the expected delivery date. In this way, if a package that has been removed from the warehouse is stored again (due to reasons such as the customer's absence), the same group ID can be assigned to the package and a package whose expected delivery date is the next day (assuming all grouping items for these packages match). Alternatively, from a similar perspective, the processing similar to that shown in FIG. 46 may be performed at a predetermined time (e.g., 2:00 a.m.). In this case, by grouping past days (excluding today) as today for the expected delivery date, the same group ID can be assigned to a package that has been taken out and then stored again in the warehouse and a package whose expected delivery date is now today (which becomes the delivery day at 2 a.m. (because the date has changed to the next day)). Alternatively, when the expected delivery date or delivery time zone for one package is updated (after executing the processing of step S1089 or step S1090 in FIG. 53), the control unit 110 of the logistics management server 20 may be configured to perform the same processing as in FIG. 46.

[0281] <Transmission process of luggage information held on the driver's terminal> FIG. 47 is a flowchart showing the driver terminal-side held baggage information transmission process.

[0282] The process of sending package information held on the driver's terminal shown in Figure 47 is a process performed by the logistics management server 20 when the delivery status of the package being processed is updated (after the process of step S242 in Figure 10 (processing related to updating delivery status when scanning is selected on the logistics management server side) or the process of step S265 in Figure 18 (processing related to continuous scanning on the logistics management server side) is executed). The package being processed is the package identified by the slip number information received in step S221 in Figure 9 or step S261 in Figure 17.

[0283] In the driver terminal side package information transmission process, first, the control unit 110 of the logistics management server 20 determines whether the updated delivery status of the package is "taken out" (step S801). If it is determined that the updated delivery status of the package is "taken out", the control unit 110 of the logistics management server 20 determines whether multiple package information is associated with the package (step S802).

[0284] If it is determined that multiple parcel information is associated with the parcel, the control unit 110 of the logistics management server 20 acquires the group ID assigned to the parcel (step S803). Next, the control unit 110 of the logistics management server 20 determines whether a group parcel information transmission flag is set to ON in association with the acquired group ID (step S804). The group parcel information transmission flag is a flag indicating that group parcel information has already been transmitted for the corresponding group ID (see steps S805 to S807).

[0285] If it is determined that the group package information transmission completion flag associated with the group ID is not set to ON, the control unit 110 of the logistics management server 20 generates group package information (step S805). The group package information includes package information to be held on the driver terminal for all packages belonging to the group ID. For example, if three packages (package A, package B, and package C) belong to the group ID acquired in step S803, in the processing of step S805, the control unit 110 of the logistics management server 20 generates group package information including package information to be held on the driver terminal corresponding to package A, package information to be held on the driver terminal corresponding to package B, and package information to be held on the driver terminal corresponding to package C.

[0286] Next, the control unit 110 of the logistics management server 20 transmits the generated group package information together with information indicating the group ID (group ID information) to the driver terminal 40 via the communication unit 112 (step S806). Then, the control unit 110 of the logistics management server 20 sets the group package information transmission completion flag to ON in association with the group ID (step S807). Although not shown, the control unit 140 of the driver terminal 40 stores the group package information received from the logistics management server 20 in the delivery destination information storage area of ​​the memory unit 141 (see step S445 of FIG. 10 and step S491 of FIG. 18). At that time, the control unit 140 of the driver terminal 40 associates multiple package information with each package (slip number information) belonging to the group ID. In addition, by storing the group package information using the group ID as a key, it becomes possible to efficiently search for the group package information.

[0287] The group package information includes information (delivery status information) indicating the updated delivery status ("taken out") of the package being processed. For example, if, of the three packages (package A, package B, and package C) belonging to the group ID acquired in step S803, the package being processed is package A, and the delivery status of packages B and C is not "taken out," the delivery status information corresponding to package A is included in the group package information, but the delivery status information corresponding to package B and package C is not included in the group package information. The control unit 140 of the driver terminal 40 stores the delivery status information corresponding to the package being processed in the delivery destination information storage area.

[0288] If it is determined in step S804 that the group package information transmission flag associated with the group ID is set to ON, the control unit 110 of the logistics management server 20 transmits delivery status information corresponding to the package being processed to the driver terminal 40 via the communication unit 112 (step S808). The control unit 140 of the driver terminal 40 stores the delivery status information received from the logistics management server 20 in the delivery destination information storage area. As a result, when the delivery status of three packages (package A, package B, and package C) belonging to the group ID acquired in step S803 is updated to "take out" in the order of package A → package B → package C, first the delivery status information corresponding to package A is stored in the delivery destination information storage area, then the delivery status information corresponding to package B is stored in the delivery destination information storage area, and then the delivery status information corresponding to package C is stored in the delivery destination information storage area.

[0289] If it is determined in step S802 that multiple package information is not associated with the package, the control unit 110 of the logistics management server 20 transmits the package information to be held on the driver terminal side corresponding to the package to the driver terminal 40 via the communication unit 112 (step S809). The control unit 140 of the driver terminal 40 stores the received package information to be held on the driver terminal side in the delivery destination information storage area of ​​the memory unit 141 (see step S445 in FIG. 10 and step S491 in FIG. 18).

[0290] If it is determined in step S801 that the updated delivery status of the parcel is not "take-out," or after executing the processing of step S807, step S808, or step S809, the control unit 110 of the logistics management server 20 terminates the processing of sending parcel information held on the driver terminal side.

[0291] <Pin display related processing> FIG. 48 is a flowchart showing the pin display related processing.

[0292] The pin display related processing shown in FIG. 48 is processing carried out in the driver terminal 40 in step S501 of FIG. 23 (processing at the time of map selection).

[0293] In the pin display related processing, first, the control unit 140 of the driver terminal 40 executes the processing of steps S1041 and S1042. However, since these processings are basically the same as the processings of steps S521 and S522 in FIG. 24, the explanation thereof will be omitted here.

[0294] After executing the process of step S1042, the control unit 140 of the driver terminal 40 reads out, for each pin, the package information held on the driver terminal side that is associated with that pin (step S1043). Then, the control unit 140 of the driver terminal 40 counts the number of package delivery destinations (number of doorsteps) for each pin (step S1044). In this process, if the number of packages (package count) corresponding to each pin is two or more, the control unit 140 of the driver terminal 40 identifies the group ID assigned to the package for packages associated with multiple package information.

[0295] The processing of step S1044 is the same as the processing of step S524 in FIG. 24. For one pin, if the number of group IDs identified in this manner is K (there are K types of group IDs assigned to each package corresponding to the pin), and the number of packages (single packages) not associated with multiple-item information is L, the number of parcels N corresponding to the pin (geotag-matching group) is expressed as N = K + L. In the example shown in FIGS. 29 to 31, one pin (pin 300b) is associated with driver terminal-side stored package information corresponding to five packages, but there is one type of group ID assigned to three packages corresponding to the first additional condition-matching group, and one package corresponding to the second additional condition-matching group and one package corresponding to the third additional condition-matching group are each single packages. That is, K = 1 and L = 2. In this way, the group IDs and single packages each correspond to additional condition-matching groups.

[0296] After executing the process of step S1044, the control unit 140 of the driver terminal 40 executes the processes of steps S1045 and S1046. However, since these processes are basically the same as the processes of steps S525 and S526 in FIG. 24, their description will be omitted here. After executing the process of step S1046, the control unit 140 of the driver terminal 40 executes departure-related processing (step S1047). The departure-related processing will be described later with reference to FIG. 49. After executing the process of step S1047, the control unit 140 of the driver terminal 40 ends the pin display-related processing.

[0297] <Departure-related processing> Fig. 49 is a flowchart showing departure-related processing. Fig. 50 is a diagram showing an example of a screen displayed when a map selection instruction is input. Figs. 51 and 52 are diagrams showing examples of a left-behind confirmation message.

[0298] The departure-related processing shown in FIG. 49 is processing carried out in the driver terminal 40 in step S1047 of FIG. 48 (pin display-related processing).

[0299] In the departure-related processing, first, the control unit 140 of the driver terminal 40 determines whether the departure flag is set to on (step S1061). The departure flag is a flag that is (recommended to be) set when the driver departs from the warehouse (see step S1068). If it is determined that the departure flag is not set to on, the control unit 140 of the driver terminal 40 activates the departure selection instruction button (step S1062). In this processing, the control unit 140 of the driver terminal 40 causes the display unit 142 to display a departure selection instruction button image 1001.

[0300] 50, the departure selection instruction button image 1001 is an image corresponding to a button (departure selection instruction button) including the character "departure", and is displayed near the lower right corner of the map display area 200. When the departure selection instruction button image 1001 is displayed, the driver can operate the operation input unit 143 to input (departure selection instruction input) the intention to select the departure selection instruction button (departure button).

[0301] The departure selection instruction button image 1001 can be configured to be displayed when the map drawing conditions are met in a state where the driver terminal-side luggage information corresponding to at least one luggage is stored in the delivery destination information storage area (see steps S806 and S809 in FIG. 47). The map drawing conditions coincide with the trigger for displaying the map in the map display area 200 (the trigger for executing the pin display related process (see FIGS. 24 and 48)). For example, the pin display related process may be executed when a map selection instruction is input, or when a cancel instruction is input for the continuous scan to change the delivery status to "take out" (see step S484 in FIG. 17).

[0302] After executing the process of step S1062, the control unit 140 of the driver terminal 40 executes a departure selection instruction input reception process (step S1063). In this process, the control unit 140 of the driver terminal 40 waits for a departure selection instruction input. For example, the driver can input a departure selection instruction by tapping an area on the touch panel corresponding to the display location of the departure selection instruction button. When a departure selection instruction input is performed, the control unit 140 of the driver terminal 40 shifts the process to step S1064. On the other hand, when a predetermined time has elapsed without a departure selection instruction input being performed, the control unit 140 of the driver terminal 40 may end the departure-related process.

[0303] After executing the process of step S1063, the control unit 140 of the driver terminal 40 determines whether or not there is a package associated with multiple package information (step S1064). If there is package information (slip number information) to be held on the driver terminal side that is associated with multiple package information among the package information to be held on the driver terminal side stored in the delivery destination information storage area, the determination result of step S1064 will be "YES". On the other hand, if there is no package information (slip number information) to be held on the driver terminal side that is associated with multiple package information among the package information to be held on the driver terminal side stored in the delivery destination information storage area, the determination result of step S1064 will be "NO".

[0304] If it is determined that there is a package associated with multiple package information, the control unit 140 of the driver terminal 40 determines whether the delivery status of all packages belonging to the group ID assigned to the package is "taken out" (step S1065). In this process, the control unit 140 of the driver terminal 40 identifies the group ID assigned to the package for all packages associated with multiple package information, and for each identified group ID, determines whether delivery status information (information indicating "taken out") is stored in the delivery destination information storage area for all packages belonging to that group ID. If delivery status information (information indicating "taken out") is stored in the delivery destination information storage area for all packages belonging to each identified group ID, the determination result in step S1065 is "YES." On the other hand, if delivery status information (information indicating "taken out") is not stored in the delivery destination information storage area for at least one package belonging to at least one of the identified group IDs, the determination result in step S1065 is "NO."

[0305] If it is determined in step S1065 that the delivery status of at least one of the packages belonging to the group ID assigned to the package is not "taken out," the control unit 140 of the driver terminal 40 displays a left-behind confirmation message on the display unit 142 (step S1066). The left-behind confirmation message can be configured as a window (dialog) that pops up in the map display area 200. As an example of a left-behind confirmation message, FIG. 51 shows a left-behind confirmation message 1002a being displayed, and FIG. 52 shows a left-behind confirmation message 1002b being displayed.

[0306] In this example, two group IDs are specified as group IDs assigned to packages with multiple package information associated therewith. Here, these two group IDs will be referred to as the first group ID and the second group ID. The recipient name corresponding to the package (slip number) belonging to the first group ID is "Urawa Minami," and the recipient name corresponding to the package (slip number) belonging to the second group ID is "Noda Sakura." Also, in this example, the number of slip numbers belonging to the first group ID is 3, and the number of slip numbers belonging to the second group ID is 2.

[0307] The left-behind confirmation message 1002a shown in Figure 51 indicates that the delivery status of the package corresponding to one slip number ("5005-0407-5945") of the three slip numbers ("5005-0407-5840," "5005-0407-5841," and "5005-0407-5945") belonging to the first group ID is not "taken out." The left-behind confirmation message 1002b shown in Figure 52 indicates that the delivery status of the package corresponding to one slip number ("5005-0407-8864") of the two slip numbers ("5005-0407-8756" and "5005-0407-8864") belonging to the second group ID is not "taken out."

[0308] The left-behind confirmation message 1002a and the left-behind confirmation message 1002b include a text image of "May I leave?" and text images corresponding to "Yes" and "No." The area where "Yes" is displayed (departure OK instruction input area) corresponds to the departure OK instruction button, and the area where "No" is displayed (departure NG instruction input area) corresponds to the departure NG instruction button. When the left-behind confirmation message is displayed, the driver can operate the operation input unit 143 to input an input to select the departure OK instruction button in the departure OK instruction input area (departure OK instruction input) or an input to select the departure NG instruction button in the departure NG instruction input area (departure NG instruction input).

[0309] The left-behind confirmation message 1002a includes a character image corresponding to "Next." The driver can display the left-behind confirmation message 1002b by inputting via the operation input unit 143 an instruction to select the button corresponding to "Next." The left-behind confirmation message 1002b includes a character image corresponding to "Previous." The driver can display the left-behind confirmation message 1002a by inputting via the operation input unit 143 an instruction to select the button corresponding to "Previous." The left-behind confirmation message 1002a and the left-behind confirmation message 1002b include a character image corresponding to "Details." The driver can display more detailed information (baggage details screen) about the luggage belonging to the group ID by inputting via the operation input unit 143 an instruction to select the button corresponding to "Details." In addition, in FIGS. 51 and 52, the outer edge of the departure selection instruction button image 1001 is displayed with a dotted line, indicating that operation on the departure selection instruction button is invalid.

[0310] After executing the process of step S1066, the control unit 140 of the driver terminal 40 determines whether a departure OK instruction has been input for all the left-behind confirmation messages (step S1067). Here, if there are multiple (P) group IDs (two group IDs in the example shown in FIGS. 51 and 52) as group IDs for which the delivery status of at least one package is not set to "take-out," a left-behind confirmation message corresponding to each of the P group IDs is displayed. If a departure OK instruction (or a departure NG instruction) is input while one left-behind confirmation message is displayed, the next left-behind confirmation message is displayed. If a departure OK instruction has been input for all of the P left-behind confirmation messages corresponding to each of the P group IDs, the determination result of step S1067 is "YES." On the other hand, if a departure OK instruction has not been input for at least one of the P left-behind confirmation messages corresponding to each of the P group IDs, the determination result of step S1067 is "NO."

[0311] Note that, when a predetermined time has elapsed without a departure OK instruction input (or a departure NG instruction input) while a first left-behind confirmation message is displayed, the control unit 140 of the driver's terminal 40 may terminate the departure-related processing. Furthermore, a configuration may be adopted in which a scan selection instruction input is possible while a first left-behind confirmation message is displayed. In this case, for example, when a scan selection instruction input is made, the processing may proceed to step S482 in FIG. 17, where the updated delivery status may be set to "take-out" in step S482, and the processing from step S483 onward may be performed. Then, when the processing of step S491 in FIG. 18 is performed, it may be considered that a departure OK instruction has been input in the left-behind confirmation message. Furthermore, when the camera is enabled in step S483 and the continuous scan mode is entered, the slip numbers of packages whose delivery status is not set to "take-out" may be displayed in an area corresponding to the checklist display area 266 (see FIG. 37). The scan selection instruction input may be made in the scan selection area 203, or may be made on the luggage details screen, and the departure NG instruction input may be considered the same as the scan selection instruction input.

[0312] If it is determined in step S1064 that there is no package associated with multiple package information, if it is determined in step S1065 that the delivery status of all packages belonging to the group ID assigned to the package is "taken out", or if it is determined in step S1067 that a departure OK instruction has been entered in all left-behind confirmation messages, control unit 140 of driver terminal 40 sets the departure flag to ON (step S1068). Also, although not shown, at this time, control unit 140 of driver terminal 40 causes display unit 142 to display a message stating that "the situation is such that there is no problem with departure."

[0313] If it is determined in step S1061 that the departure flag is set to on, if it is determined in step S1067 that a departure OK instruction has not been entered in at least one left-behind confirmation message, or after executing the processing of step S1068, the control unit 140 of the driver terminal 40 terminates the departure-related processing.

[0314] When the departure flag is not set to on and the current location (the location of the driver terminal 40) moves a predetermined distance away from the warehouse, the control unit 140 of the driver terminal 40 may transmit information indicating this (departure possibility confirmation information) to the logistics management server 20 or the manager terminal 30. When the departure possibility confirmation information is transmitted to the logistics management server 20, the control unit 110 of the logistics management server 20 may also transmit the information to the manager terminal 30. Furthermore, when the departure flag is not set to on and the current location (the location of the driver terminal 40) moves a predetermined distance away from the warehouse, the control unit 140 of the driver terminal 40 may issue a notification that the driver should confirm whether or not to depart. The notification may be in the same manner as the error notification described in the first embodiment.

[0315] <Change delivery date and time> Fig. 53 is a flowchart showing delivery date and time change processing. Fig. 54 is a diagram showing an example of a service menu top screen. Fig. 55 is a diagram showing an example of a slip number input screen. Figs. 56 to 62 are diagrams showing examples of delivery date and time change screens. Fig. 63 is a diagram showing an example of a date and time change completion screen.

[0316] The delivery date and time change process shown in Figure 53 is a process performed in the logistics management server 20 when accessed from the customer terminal 80. As described in the first embodiment, the customer terminal 80 is a terminal device operated by a customer. Like the driver terminal 40, the customer terminal 80 includes a display unit 81, as well as a control unit, a memory unit, an operation input unit, an imaging unit, a communication unit, etc. For example, the information sheet that the customer receives when purchasing a product or when the customer is not at home contains a two-dimensional code that encodes address information for a service provided by the logistics management server 20. By photographing the two-dimensional code with the imaging unit of the customer terminal 80, a request can be sent to the logistics management server 20 and the service can be used.

[0317] When a request is sent to the logistics management server 20, a service menu top screen is displayed on the display unit 81 of the customer terminal 80. As shown in FIG. 54, the service menu top screen displays icons (menu selection icons) corresponding to a plurality of service menu items, including a delivery date / time change icon 82, a cargo tracking icon 83, and an inquiry icon 84. The customer can select and confirm one of the delivery date / time change icon 82, the cargo tracking icon 83, and the inquiry icon 84 (the service menu item corresponding to the menu selection icon) by operating the operation input unit (for example, by tapping an area on the touch panel corresponding to the display location of one of the menu selection icons).

[0318] The following describes the case where the delivery date and time change icon 82 is selected and confirmed as a service menu item (menu selection icon) on the service menu top screen. By selecting and confirming the cargo tracking icon 83 as a service menu item (menu selection icon), the customer can view the customer transition process screen (see Figure 15(b)).

[0319] When the delivery date and time change icon 82 is selected and confirmed, a slip number input screen is displayed on the display unit 81 of the customer terminal 80. As shown in FIG. 55, the slip number input screen has a slip number input area 85 and a delivery date and time change screen display instruction input area 86. The slip number input area 85 is an area for inputting a slip number. The delivery date and time change screen display instruction input area 86 is an area where an image corresponding to a button containing the word "display" (delivery date and time change screen display instruction button) is displayed. By operating the operation input unit, the customer can input the slip number notified on a guide sheet or the like in the slip number input area 85. Furthermore, by operating the operation input unit, the customer can input an instruction to select the delivery date and time change screen display instruction button in the delivery date and time change screen display instruction input area 86 (delivery date and time change screen display instruction input). When a delivery date and time change screen display instruction is input while a slip number has been entered in the slip number input area 85, information indicating the slip number (slip number information) is transmitted to the logistics management server 20.

[0320] In the delivery date and time change process, first, the control unit 110 of the logistics management server 20 receives the slip number information transmitted from the customer terminal 80 via the communication unit 112 (step S1081). Next, the control unit 110 of the logistics management server 20 determines whether multiple package information is associated with the package corresponding to the received slip number information (step S1082). If it determines that multiple package information is not associated with the package, the control unit 110 of the logistics management server 20 generates display data for a delivery date and time change screen based on the package information corresponding to the package (single package) and transmits the display data to the customer terminal 80 via the communication unit 112 (step S1083). Then, the control unit 110 of the logistics management server 20 receives the delivery date and time change information transmitted from the customer terminal 80 via the communication unit 112 (step S1084).

[0321] If it is determined in step S1082 that multiple parcel information is associated with the parcel, the control unit 110 of the logistics management server 20 acquires the group ID assigned to the parcel (step S1085). Next, the control unit 110 of the logistics management server 20 generates display data for a delivery date and time change screen based on the parcel information corresponding to all parcels belonging to the acquired group ID, and transmits the display data to the customer terminal 80 via the communication unit 112 (step S1086). Then, the control unit 110 of the logistics management server 20 receives the delivery date and time change information transmitted from the customer terminal 80 via the communication unit 112 (step S1087).

[0322] Here, when the display data transmitted from the logistics management server 20 is received in step S1083 or step S1086, a delivery date and time change screen is displayed on the display unit 81 of the customer terminal 80. Figures 56 to 62 show the delivery date and time change screen (delivery date and time change screen for multiple packages) that is displayed when the customer terminal 80 receives the display data transmitted from the logistics management server 20 in step S1086. In the example shown in Figure 56, the delivery date and time change screen displays "5006-0518-9921" as the "slip number" and "receiving" as the "current status." The "slip number" is the slip number entered on the slip number input screen, and the "current status" is the delivery status of the package corresponding to the slip number. "Receiving" means "confirmed receipt."

[0323] FIG. 57 shows the delivery date and time change screen that is displayed when the screen is scrolled downward from the state shown in FIG. 56. In the example shown in FIG. 57, the delivery date and time change screen displays "5006-0518-9922" and "5006-0518-9923" as the "slip number." These slip numbers are the slip numbers of other packages belonging to the group ID acquired in step S1085 (assigned to the package identified by the slip number "5006-0518-9921"). The display data generated in step S1086 includes slip number information corresponding to all packages belonging to the group ID. In contrast, the display data generated in step S1083 includes only the slip number information received in step S1081, and the delivery date and time change screen (delivery date and time change screen for a single package) that is displayed when the display data is received by customer terminal 80 displays only the slip number entered on the slip number input screen.

[0324] Figure 58 shows the delivery date and time change screen that is displayed when scrolling downward from the state shown in Figure 57. In the example shown in Figure 58, the delivery date and time change screen has a date input area 87 and a phone number input area 89. The date input area 87 is an area for inputting the changed scheduled delivery date. The phone number input area 89 is an area for inputting a phone number. By operating the operation input unit, the customer can input the scheduled delivery date in the date input area 87 and can input a phone number in the phone number input area 89. The date input area 87 can display a calendar in response to operation of the operation input unit.

[0325] FIG. 59 shows a delivery date and time change screen that is displayed when an expected delivery date is entered in the date input field 87 in the state shown in FIG. 58. In the example shown in FIG. 59, the delivery date and time change screen has a delivery time slot input field 88 in addition to the date input field 87 and phone number input field 89. The delivery time slot input field 88 is an area for inputting a changed delivery time slot. The customer can input a delivery time slot in the delivery time slot input field 88 by operating the operation input unit. The delivery time slot input field 88 can display candidate delivery time slots (e.g., "No Specification," "8:00 AM - 12:00 PM," "12:00 PM - 2:00 PM," "2:00 PM - 4:00 PM," "4:00 PM - 6:00 PM," "6:00 PM - 8:00 PM," and "7:00 PM - 9:00 PM") in a pull-down menu in response to operation of the operation input unit. In this example, "2024 / 10 / 11" is entered as the expected delivery date in the date input field 87, and "2:00 PM - 4:00 PM" is entered as the delivery time slot in the delivery time slot input field 88.

[0326] FIG. 60 shows a delivery date and time change screen that is displayed when the screen is scrolled downward from the state shown in FIG. 59. In the example shown in FIG. 60, the delivery date and time change screen has a bulk change instruction input area 91. The bulk change instruction input area 91 includes text images corresponding to "Yes" and "No." The area where "Yes" is displayed (the bulk change permission instruction input area) corresponds to the bulk change permission instruction button, and the area where "No" is displayed (the bulk change disallowance instruction input area) corresponds to the bulk change disallowance instruction button. By operating the operation input unit, the customer can input an instruction to select the bulk change permission instruction button in the bulk change instruction input area 91 (bulk change permission instruction input) or an instruction to select the bulk change disallowance instruction button in the bulk change disallowance instruction input area (bulk change disallowance instruction input). When an instruction to allow bulk changes is input, information indicating that (bulk change permission information) is sent to the logistics management server 20. When an instruction to disallow bulk changes is input, information indicating that (bulk change disallowance information) is sent to the logistics management server 20.

[0327] Figure 61 shows a delivery date and time change screen that is displayed when a bulk change permission instruction is input in bulk change instruction input area 91 in the state shown in Figure 60. In the example shown in Figure 61, the delivery date and time change screen displays "5006-0518-9921," "5006-0518-9922," and "5006-0518-9923" as the "slip numbers," and "October 11, 2024," "14:00-16:00" as the "desired delivery date and time." "5006-0518-9921" is the slip number entered on the slip number input screen (see Figure 56), and "5006-0518-9922" and "5006-0518-9923" are the slip numbers of other packages that belong to the group ID assigned to the package identified by the slip number "5006-0518-9921" (see Figure 57). "October 11, 2024" is the expected delivery date entered in the date input area 87, and "2:00 PM to 4:00 PM" is the delivery time slot entered in the delivery time slot input area 88 (see FIG. 59). In this example, the delivery date and time change screen also has a date and time change confirmation message display instruction input area 90. The date and time change confirmation message display instruction input area 90 is an area where an image corresponding to a button containing the word "Confirm" (date and time change confirmation message display instruction button) is displayed. By operating the operation input unit, the customer can input an instruction to select the date and time change confirmation message display instruction button in the date and time change confirmation message display instruction input area 90 (date and time change confirmation message display instruction input).

[0328] FIG. 62 shows a delivery date and time change screen that is displayed when a date and time change confirmation message display instruction is input in the state shown in FIG. 61. In the example shown in FIG. 62, the delivery date and time change screen includes a date and time change confirmation message 93. The date and time change confirmation message 93 can be configured as a window (dialog) that pops up in the center of the screen of the display unit 81 and includes a character image corresponding to "Close." In this example, the delivery date and time change screen also has a date and time change confirmation instruction input area 92. The date and time change confirmation instruction input area 92 is an area where an image corresponding to a button containing the character "Register" (date and time change confirmation instruction button) is displayed. By operating the operation input unit, the customer can input an instruction to select the button corresponding to "Close" in the date and time change confirmation message 93, and then input an instruction to select the date and time change confirmation instruction button in the date and time change confirmation instruction input area 92 (date and time change confirmation instruction input). When the date and time change confirmation instruction is input, delivery date and time change information is sent to the logistics management server 20. The delivery date and time change information includes information indicating the scheduled delivery date entered in the date input field 87 (changed scheduled delivery date information) and information indicating the delivery time zone entered in the delivery time zone input field 88 (changed delivery time zone information).

[0329] Returning to Fig. 53, in the processing of step S1084 or step S1087, the control unit 110 of the logistics management server 20 receives the delivery date and time change information transmitted from the customer terminal 80. After executing the processing of step S1087, the control unit 110 of the logistics management server 20 determines whether or not a bulk change permission instruction has been input at the customer terminal 80 (step S1088). By receiving the bulk change permission information from the customer terminal 80, the control unit 110 of the logistics management server 20 can recognize that a bulk change permission instruction has been input at the customer terminal 80.

[0330] After executing the process of step S1084, or if it is determined in step S1088 that a bulk change permission instruction has not been input, the control unit 110 of the logistics management server 20 updates the delivery date and time for one package (step S1089). In this process, the control unit 110 of the logistics management server 20 changes the expected delivery date and delivery time slot corresponding to the slip number received in step S1081 for the package (one package) based on the changed expected delivery date information and changed delivery time slot information included in the delivery date and time change information to the expected delivery date input in the date input field 87 and the delivery time slot input in the delivery time slot input field 88, respectively.

[0331] If it is determined in step S1088 that a bulk change permission instruction has been input, the control unit 110 of the logistics management server 20 updates the delivery dates and times for multiple packages (step S1090). In this process, the control unit 110 of the logistics management server 20...

Claims

1. a storage means capable of storing delivery timing information relating to delivery timing of a package and predetermined package-related information different from the delivery timing information; receiving means capable of receiving package identification information for identifying a package; update control means for updating the delivery timing information stored in the storage means; the update control means, after the delivery timing information for one parcel and the delivery timing information for another parcel are stored in the storage means, receives the parcel identification information by the receiving means in response to a user's operation to specify parcel identification information corresponding to the one parcel when the specified parcel-related information stored in the storage means for the one parcel is the same as the specified parcel-related information stored in the storage means for the other parcel, and when updating the delivery timing information stored in the storage means for the one parcel, identifies the parcel identification information associated with the parcel identification information corresponding to the one parcel as the parcel identification information corresponding to the other parcel, thereby updating the delivery timing information stored in the storage means for the other parcel so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcel become the same; 1. An information processing device comprising:

2. 1. An information processing method for use in package delivery, the method being executed by at least one computer, comprising: receiving package identification information for identifying the package; and after delivery timing information for one package and delivery timing information for another package are stored in a storage means, if predetermined package-related information for the one package stored in the storage means is the same as the predetermined package-related information for the other package stored in the storage means, receiving the package identification information in response to a user performing an operation to specify package identification information corresponding to the one package, and when updating the delivery timing information for the one package stored in the storage means, specifying the package identification information associated with the package identification information corresponding to the one package as package identification information corresponding to the other package, thereby updating the delivery timing information stored in the storage means for the other package so that the updated delivery timing information for the one package and the updated delivery timing information for the other package are the same. An information processing method comprising:

3. a storage means capable of storing delivery timing information relating to delivery timing of a package and predetermined package-related information different from the delivery timing information; receiving means capable of receiving package identification information for identifying a package; update control means for updating the delivery timing information stored in the storage means; the update control means, after the delivery timing information for one parcel and the delivery timing information for another parcel are stored in the storage means, receives the parcel identification information by the receiving means in response to a user's operation to specify parcel identification information corresponding to the one parcel when the specified parcel-related information stored in the storage means for the one parcel is the same as the specified parcel-related information stored in the storage means for the other parcel, and when updating the delivery timing information stored in the storage means for the one parcel, identifies the parcel identification information associated with the parcel identification information corresponding to the one parcel as the parcel identification information corresponding to the other parcel, thereby updating the delivery timing information stored in the storage means for the other parcel so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcel become the same; An information processing system comprising:

4. A program used for delivering packages, causing at least one computer to function as receiving means capable of receiving package identification information for identifying packages, and update control means capable of updating delivery timing information stored in storage means, the update control means, after the delivery timing information for one parcel and the delivery timing information for another parcel are stored in the storage means, receives the parcel identification information by the receiving means in response to a user's operation to specify parcel identification information corresponding to the one parcel when the predetermined parcel-related information stored in the storage means for the one parcel is the same as the predetermined parcel-related information stored in the storage means for the other parcel, and when updating the delivery timing information stored in the storage means for the one parcel, identifies the parcel identification information associated with the parcel identification information corresponding to the one parcel as the parcel identification information corresponding to the other parcel, thereby updating the delivery timing information stored in the storage means for the other parcel so that the updated delivery timing information for the one parcel and the updated delivery timing information for the other parcel become the same; A program characterized by:

Images