Transportation management device, transportation management system, and transportation management method

Abstract

To transport a package properly.SOLUTION: A transportation management apparatus (1) acquires location information (811) of a terminal device, a transportation company ID (812) for identifying a transportation company, and a container ID (813) for identifying a container, from the terminal device (2[i]) corresponding to a vehicle for transporting a package. A management unit in the transportation management apparatus manages a transportation management state (system state) relating to transportation of the package. The management unit changes the transportation management state between multiple states, the multiple states including a ready-for-start state which allows a vehicle with a container mounted thereon to start. The management unit is configured to change the transportation management state to the ready-for-start state, on the basis of, the location information, the transportation company ID and the container ID acquired from the terminal device, a current time and date, schedule data including a transportation schedule, and a current transportation management state.SELECTED DRAWING: Figure 10

Description

[Technical field]

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

[0002] One type of transportation using vehicles uses a vehicle with a prime mover and a storage unit (such as a container) that can be connected (placed or mounted) to the vehicle, and the storage unit loaded with luggage is connected to the vehicle and transported to the destination. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-50150 A Summary of the Invention [Problem to be solved by the invention]

[0004] In this type of transportation, if a container different from the container to be transported is connected to the vehicle, the correct transportation will not be realized (the wrong cargo will arrive at the destination). This situation should be taken into special care when relay transportation is performed using multiple vehicles.

[0005] An object of the present invention is to provide a transportation management device, a transportation management system, and a transportation management method that contribute to the accurate transportation of luggage. [Means for solving the problem]

[0006] The transportation management device of the present invention comprises a terminal transmission information acquisition unit that acquires, based on transmission information of a terminal device corresponding to a target vehicle for transporting luggage, location information representing the current location of the terminal device, carrier identification information for identifying the carrier to which the target vehicle belongs, and storage unit identification information for identifying the storage unit that stores the luggage, a storage unit that stores schedule data related to the transportation of the luggage, and a management unit that manages the transportation management state related to the transportation of the luggage, wherein the management unit transitions the transportation management state between a plurality of states including a departure ready state that permits the departure of the target vehicle in which the storage unit is located, and the management unit is configured to be able to transition the transportation management state to the departure ready state based on the location information, the carrier identification information, and the storage unit identification information based on the transmission information of the terminal device, the current date and time, the schedule data, and the current transportation management state (first configuration).

[0007] In the transportation management device of the above-mentioned first configuration, the management unit may have an access request receiving unit that receives an access request from the terminal device to a specified transportation management website, and when the access request is received from the terminal device, it may allow or prohibit access to the transportation management website by the terminal device based on the location information and the shipping company identification information based on the transmission information of the terminal device, the current date and time, the schedule data, and the current transportation management status, and may be configured to transition the transportation management status to the departure ready state after the access is permitted (second configuration).

[0008] In the transportation management device according to the second configuration, the schedule data represents a schedule for transporting the luggage from a first base to a second base via one or more relay bases by relay transportation using a plurality of target vehicles, the schedule data includes, after setting each of the first base and the one or more relay bases as a departure point, a scheduled departure date and time of a vehicle to be transported with the storage unit arranged and a carrier identification information for identifying a carrier to which the vehicle to be transported belongs, for each of the departure points, the management unit permits the departure of the target vehicle with the storage unit arranged from the departure point by transitioning the transportation management state for each of the departure points from a state before the departure from the departure point is permitted to a state in which the departure from the departure point is permitted, and the terminal transmission information acquisition unit acquires the location information, the carrier identification information, and the like for each of the terminal devices based on transmission information of a plurality of terminal devices corresponding to the plurality of target vehicles. the management unit may be configured to, when receiving the access request from a target terminal device which is one of the plurality of terminal devices when the transportation management status is a state before departure from the target departure point is permitted for a target departure point which is one of the first base and the one or more relay bases, permit or prohibit access to the transportation management website by the target terminal device based on a relationship between a current location of the target terminal device and the target departure point, a relationship between the carrier identification information based on transmitted information of the target terminal device and the carrier identification information corresponding to the target departure point in the schedule data, a relationship between the current date and time and the scheduled departure date and time corresponding to the target departure point in the schedule data, and the current transportation management status, and to transition the transportation management status to a state in which departure from the target departure point is permitted after the access is permitted (third configuration).

[0009] In the transportation management device according to the third configuration, the plurality of target vehicles include a first target vehicle that transports the luggage from the first base to a predetermined relay base, and a second target vehicle that transports the luggage from the predetermined relay base to another relay base or the second base, The schedule data may store the storage unit identification information based on transmission information of a first terminal device corresponding to the first target vehicle, or may store the storage unit identification information that is specified in advance regardless of the transmission information of the first terminal device, and the management unit permits departure of the second target vehicle in which the storage unit is located from the specified relay base by transitioning the transportation management state for the specified relay base from a state before departure from the specified relay base is permitted to a state in which departure from the specified relay base is permitted, and when the transportation management state for the specified relay base is a state before departure from the specified relay base is permitted, the management unit permits access to the transportation management website by the second terminal device in response to the access request from the second terminal device corresponding to the second target vehicle, and then transitions the transportation management state to a state in which departure from the specified relay base is permitted if a specified departure permission condition is established, and the departure permission condition may include a condition in which the storage unit identification information based on the transmission information of the second terminal device and the storage unit identification information stored in the schedule data match (fourth configuration).

[0010] In the transportation management device of the above-mentioned fourth configuration, the terminal transmission information acquisition unit may acquire loading information relating to the loading status of the luggage in the storage unit from the first terminal device, and the management unit may be configured to transmit the loading information to the second terminal device after allowing the second terminal device to access the transportation management website (fifth configuration).

[0011] In the transportation management device of the third configuration, the terminal transmission information acquisition unit acquires vehicle identification information associated with each target vehicle based on the transmission information of the multiple terminal devices, the schedule data includes vehicle identification information of the transportation vehicles scheduled to depart with the storage unit deployed for each departure point, and the management unit, when the transportation management state for the noted departure point is in a state before departure from the noted departure point is permitted, permits the noted terminal device to access the transportation management website in response to the access request from the noted terminal device, and then transitions the transportation management state to a state in which departure from the noted departure point is permitted if a predetermined departure permission condition is met, and the departure permission condition may include a condition that the vehicle identification information based on the transmission information of the noted terminal device matches the vehicle identification information stored in the schedule data associated with the noted departure point (sixth configuration).

[0012] In the transportation management device of any of the above-mentioned first to sixth configurations, the access request receiving unit may be configured (seventh configuration) to receive the access request issued from the terminal device by photographing a code corresponding to the schedule data with the terminal device.

[0013] The transportation management system according to the present invention has a configuration (eighth configuration) including the transportation management device according to the first or second configuration and the terminal device.

[0014] Another transportation management system according to the present invention has a configuration (ninth configuration) including a transportation management device according to any one of the third to sixth configurations and the plurality of terminal devices.

[0015] The transportation management method of the present invention includes an acquisition step of acquiring location information representing the current location of a terminal device corresponding to a target vehicle for transporting luggage, carrier identification information for identifying the carrier to which the target vehicle belongs, and storage unit identification information for identifying the storage unit for storing the luggage, based on transmitted information from the terminal device, and a management step of managing a transportation management state related to the transportation of the luggage, wherein the management step transitions the transportation management state between a plurality of states including a departure ready state that permits the departure of the target vehicle in which the storage unit is located, and the management step is configured to be capable of transitioning the transportation management state to the departure ready state based on the location information, the carrier identification information, and the storage unit identification information based on the transmitted information from the terminal device, the current date and time, schedule data related to the transportation of the luggage, and the current transportation management state (tenth configuration). Effect of the Invention

[0016] According to the present invention, it is possible to provide a transportation management device, a transportation management system, and a transportation management method that contribute to the accurate transportation of luggage. [Brief description of the drawings]

[0017] [Figure 1] 1 is an overall configuration diagram of a transportation management system according to an embodiment of the present invention; [Diagram 2] FIG. 2A is an external side view of a vehicle in a state where the storage unit is not connected, and FIG. 2B is an external side view of a vehicle in a state where the storage unit is connected, according to an embodiment of the present invention. [Diagram 3] 1 is an overall configuration diagram of a transportation management system according to an embodiment of the present invention; [Figure 4] 1 is a configuration diagram of a transportation management device according to an embodiment of the present invention. [Diagram 5] FIG. 2 is a configuration diagram of a terminal device according to an embodiment of the present invention. [Figure 6] FIG. 1A is a diagram showing a vehicle code being applied to a vehicle body, and FIG. 1B is a diagram showing a container code being applied to the outer wall of a container, according to an embodiment of the present invention. [Figure 7] FIG. 2 is an explanatory diagram of relay transportation mainly assumed in an embodiment of the present invention. [Figure 8] FIG. 2 is a diagram showing the configuration of schedule data according to the embodiment of the present invention. [Figure 9] 10A to 10C are diagrams illustrating how two-dimensional codes are photographed by a terminal device according to an embodiment of the present invention. [Figure 10] 1 is a diagram for explaining the contents of information transmitted by a terminal device according to an embodiment of the present invention. FIG. [Figure 11] 11 is a diagram showing how an access request is issued from a terminal device to a transportation management device according to an embodiment of the present invention. FIG. [Figure 12] FIG. 2 is a diagram showing a flow of work etc. of a driver at a first base and two relay bases in an embodiment of the present invention. [Figure 13] 11 is a flowchart of a process related to an access request according to an embodiment of the present invention. [Figure 14] 5 is a flowchart of a process involving a vehicle from a first base in the embodiment of the present invention. [Figure 15] 5 is a flowchart of a process involving a vehicle from a relay point according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, examples of the embodiments of the present invention will be described in detail with reference to the drawings. In each of the drawings, the same parts are given the same reference numerals, and duplicated descriptions of the same parts are omitted as a rule. In this specification, for the sake of simplicity, a symbol or a code referring to information, a signal, a physical quantity, or a member may be written, and the name of the information, signal, physical quantity, or member corresponding to the symbol or code may be omitted or abbreviated. For example, the terminal transmission information acquisition unit referred to by "112" described later (see FIG. 4) may be written as the terminal transmission information acquisition unit 112 or may be abbreviated as the acquisition unit 112, but they all refer to the same thing. In this specification, the terms "transportation" and "transportation" are synonymous with each other, and may be read interchangeably.

[0019] Fig. 1 shows an overall configuration diagram of a transportation management system SYS according to an embodiment of the present invention. The transportation management system SYS is configured with a transportation management device 1 and multiple terminal devices 2. The transportation management device 1 and each terminal device 2 are wirelessly connected via a network NET in a manner that enables two-way communication. The network NET includes a mobile communication network, the Internet, and the like.

[0020] The transportation management system SYS functions effectively when a plurality of vehicles PP are used to transport cargo from one base to another, and ensures accurate transportation of the cargo. In this embodiment, the vehicle PP refers to a vehicle having a prime mover, and includes vehicles generally classified as tractors. A storage unit that stores cargo can be connected to each vehicle PP.

[0021] Please refer to Figs. 2(a) and (b). The storage unit is referred to by the symbol "QQ". Fig. 2(a) is an external side view of the vehicle PP in a state where the storage unit QQ is not connected, and Fig. 2(b) is a schematic side view of the vehicle PP in a state where the storage unit QQ is connected. The connection of the storage unit QQ to the vehicle PP does not only mean that the storage unit QQ is physically connected to the vehicle PP, but may also mean that the storage unit QQ is disposed or mounted on the platform of the vehicle PP. The storage unit QQ can be freely connected or disconnected to the vehicle PP. The connection of the storage unit QQ to the vehicle PP and the placement or mounting of the storage unit QQ to the vehicle PP may be understood to be synonymous with each other. Therefore, for example, in this specification, the expression "connection of the storage unit QQ to the vehicle PP" may be read as "placement of the storage unit QQ on the vehicle PP (specifically, placement of the storage unit QQ on the platform of the vehicle PP)" and vice versa.

[0022] The storage unit QQ may be any storage unit capable of storing luggage and being connected (placed or mounted) to the vehicle PP. For example, the storage unit QQ is a container that can be mounted on the bed of the vehicle PP. The storage unit QQ is, for example, a 20-foot container (ISO container). The storage unit QQ may be a swap body container, in which case the vehicle PP may also be referred to as a swap body truck. The storage unit QQ may be a trailer having wheels. If the storage unit QQ is a trailer, the vehicle PP is a tractor that tows the trailer. In the following, it is assumed that the storage unit QQ is a container such as a swap body container, and the storage unit QQ is referred to as a container QQ.

[0023] Each terminal device 2 is, for example, a smartphone, a tablet, or a portable information terminal. Each terminal device 2 may be a terminal device carried by a driver who drives a vehicle PP, or may be a terminal device installed in the vehicle PP. In the following, unless otherwise specified, each terminal device 2 is assumed to be a terminal device (such as a smartphone) carried by a driver who drives a vehicle PP, and the terminal device 2 and the vehicle PP are considered to correspond one-to-one. The transportation management system SYS includes n terminal devices 2, and when it is necessary to distinguish the multiple terminal devices 2 from each other, the multiple terminal devices 2 may be referred to as terminal devices 2[1] to 2[n] (see FIG. 3). Similarly, when it is necessary to distinguish the multiple vehicle PPs from each other, the multiple vehicle PPs may be referred to as vehicle PP[1] to PP[n] (see FIG. 3). n has an arbitrary integer value of 2 or more. The driver of the vehicle PP[i] carries the terminal device 2[i], so the terminal device 2[i] corresponds to the vehicle PP[i]. i represents an arbitrary integer.

[0024] Here, an overview of the mechanism of the transportation management system SYS will be explained. In relay transportation in which many transport companies participate, it is important that the driver does not load a container different from the container specified in the schedule onto the vehicle PP and transport it, or unload the container at a location that does not follow the schedule. The transportation management system SYS manages relay transportation to be performed correctly using a two-dimensional code consisting of a QR code (registered trademark). The details will be described later, but to summarize (see FIG. 9), the driver reads the two-dimensional code (AC_CD) on the schedule table into the terminal device 2[i] before operating, and then reads the two-dimensional code (QQ_CD) of the container QQ and the two-dimensional code (PP_CD) of the vehicle PP. This read information is sent to the transportation management device 1, and the transportation management device 1 checks whether the correct container QQ and the correct vehicle PP are being used for operation.

[0025] In the transportation management system SYS, a mechanism is introduced whereby when the terminal device 2[i] reads the two-dimensional code (AC_CD) on the schedule, a request to access a specified transportation management website is issued from the terminal device 2[i]. At this time, if the read location, the carrier ID entered into the terminal device 2[i], the current date and time, and the relay transportation status (corresponding to the system status described below) managed by the transportation management device 1 are not appropriate in light of the schedule, access is prohibited. The departure of vehicle PP[i] is not permitted until access has been made to the transportation management website. This ensures correct operation. The functions and operations of each component are explained in detail below.

[0026] Fig. 4 shows an internal configuration diagram of the transportation management device 1. The transportation management device 1 includes a control unit 11, a storage unit 12, a communication unit 13, an interface unit 14, and a date and time information acquisition unit 15. The transportation management device 1 is configured by one or more computer devices. The transportation management device 1 may be a server device. The transportation management device 1 may be configured using cloud computing.

[0027] The control unit 11 is configured to include a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), etc., and comprehensively controls the overall operation of the transportation management device 1. The memory unit 12 is composed of a magnetic disk, semiconductor memory, etc., or a combination of these, and stores and keeps track of various programs and data. Various functions are realized by the CPU of the control unit 11 executing the programs in the memory unit 12. The communication unit 13 is connected to the network NET by wire or wirelessly, and performs two-way communication with the other device of the transportation management device 1 via the network NET. The other device of the transportation management device 1 includes the multiple terminal devices 2 described above.

[0028] The interface unit 14 is a man-machine interface between the transportation management device 1 and a user of the transportation management device 1, and includes a display unit 141, an operation unit 142, a microphone 143, and a speaker 144. The user of the transportation management device 1 is the administrator of the transportation management system SYS (hereinafter simply referred to as the administrator).

[0029] Display unit 141 is a display device configured with a liquid crystal display panel or the like, and displays any image under the control of control unit 11. Operation unit 142 accepts any operation input from the administrator. Display unit 141 and operation unit 142 may configure a touch panel, and operations on operation unit 142 may be operations on the touch panel. Microphone 143 picks up ambient sounds around microphone 143 and converts the picked up sounds into electrical signals. The target of the sound picked up by microphone 143 is mainly the voice uttered by the administrator. Speaker 144 outputs any sound under the control of control unit 11.

[0030] Incidentally, all or part of the interface unit 14 may be provided outside the transportation management device 1 and externally connected to the transportation management device 1. The control unit 11 may be provided with an artificial intelligence having a voice recognition function and capable of having a voice conversation with a person, in which case communication between the manager and the transportation management device 1 may be realized using the microphone 143 and the speaker 144. However, the speaker 143 and the microphone 144 may be omitted.

[0031] The date and time information acquisition unit 15 acquires date and time information indicating the current date and time. The date and time information acquisition unit 15 may acquire date and time information from another device (not shown) via the network NET. The date and time information acquisition unit 15 may be omitted.

[0032] The control unit 11 includes a schedule data creation unit 111, a terminal transmission information acquisition unit 112, a schedule data storage unit 113, and a management unit 114, and the management unit 114 includes an access request reception unit 115. The creation unit 111, the acquisition unit 112, the storage unit 113, the management unit 114, and the reception unit 115 are functional blocks formed by the CPU (computer processing unit) of the control unit 11 executing a program stored in the memory unit 12. The reception unit 115 may be considered to be a functional block provided outside the management unit 114. The functions of these functional blocks (111 to 115) will be described later.

[0033] 5 shows an internal configuration diagram of the terminal device 2. The terminal device 2 includes a control unit 21, a storage unit 22, a communication unit 23, an interface unit 24, a date and time information acquisition unit 25, a GPS processing unit 26, and a camera unit 27.

[0034] The control unit 21 is configured to include a CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), etc., and comprehensively controls the overall operation within the terminal device 2. The memory unit 22 is composed of a magnetic disk, a semiconductor memory, etc., or a combination of these, and stores and keeps track of various programs and data. The various functions of the control unit 21 are realized by the CPU of the control unit 21 executing the programs in the memory unit 22. The communication unit 23 is connected to the network NET by wire or wirelessly, and performs two-way communication with the other device of the terminal device 2 via the network NET. The other device of the terminal device 2 includes the transportation management device 1.

[0035] The interface unit 24 is a man-machine interface between the terminal device 2 and a user of the terminal device 2, and includes a display unit 241, an operation unit 242, a microphone 243, and a speaker 244. The user of a certain terminal device 2 is the driver of a vehicle PP, which corresponds to the owner of the terminal device 2.

[0036] The display unit 241 is a display device configured with a liquid crystal display panel or the like, and displays any image under the control of the control unit 21. The operation unit 242 accepts input of any operation from the user of the terminal device 2. The display unit 241 and the operation unit 242 may configure a touch panel, and the operation on the operation unit 242 may be an operation on the touch panel. The microphone 243 picks up sounds around the microphone 243 and converts the picked up sounds into electrical signals. The target of the sound picked up by the microphone 243 is mainly the voice uttered by the user of the terminal device 2. The speaker 244 outputs any sound under the control of the control unit 21.

[0037] Incidentally, the control unit 21 may be provided with an artificial intelligence having a voice recognition function and capable of having a voice conversation with a person, in which case communication between the user and the terminal device 2 may be realized using the microphone 243 and the speaker 244. In the following description, any operation on the terminal device 2 means an operation input to the terminal device 2 by the user of the terminal device 2 via the interface unit 24.

[0038] The date and time information acquiring unit 25 acquires date and time information indicating the current date and time. The date and time information acquiring unit 25 may acquire date and time information from another device (not shown) via the network NET.

[0039] The GPS processing unit 26 detects the position of the terminal device 2 (the current location of the terminal device 2) by receiving signals from multiple GPS satellites that form the GPS (Global Positioning System), and generates location information indicating the detected position. In relay transportation, the terminal device 2[i] is located inside the vehicle PP[i], or the terminal device 2[i] is carried by the driver of the vehicle PP[i] and is located near the vehicle PP[i]. Therefore, it can be said that the location information generated by the GPS processing unit 26 of the terminal device 2[i] represents the current location of the vehicle PP[i].

[0040] The camera unit 27 captures an image of a subject within its field of view and generates image data representing the captured image. The generated image data is sent to the control unit 21.

[0041] In the relay transportation of the transportation management system SYS, a plurality of vehicles PP and a plurality of containers QQ are operated. A vehicle ID is assigned to each vehicle PP. The vehicle ID is identification information unique to each vehicle PP, and is vehicle identification information for identifying which vehicle among the plurality of vehicles PP each vehicle PP is. Therefore, the vehicle IDs in the plurality of vehicles PP are different from each other. A container ID is assigned to each container QQ. The container ID is identification information unique to each container QQ, and is container identification information (container identification information) for identifying which container among the plurality of containers QQ each container QQ is. Therefore, the container IDs in the plurality of containers QQ are different from each other. Furthermore, as shown in FIG. 6(a), a vehicle code PP_CD is assigned to a predetermined location on the body of each vehicle PP. The vehicle code PP_CD assigned to the body of the vehicle PP[i] is information for identifying the vehicle ID of the vehicle PP[i], and is composed of a two-dimensional code. Similarly, as shown in FIG. 6(b), a container code QQ_CD is assigned to a predetermined location on the outer wall of each container QQ. The container code QQ_CD attached to the outer wall of the container QQ[i] is information that identifies the container ID of the container QQ[i] and is composed of a two-dimensional code.

[0042] A vehicle code PP_CD is affixed to the body of each vehicle PP by printing or sticking a sticker, etc., and a container code QQ_CD is affixed to the outer wall of each container QQ by printing or sticking a sticker, etc., in a position where the driver can easily photograph the codes PP_CD and QQ_CD using the terminal device 2 (camera unit 27). A QR code (registered trademark) can be used as the vehicle code PP_CD and the container code QQ_CD.

[0043] Fig. 7 is a conceptual diagram of relay transportation assumed in this embodiment. In this embodiment, it is assumed that a cargo to be transported (hereinafter, specifically referred to as a target cargo) is relay transported from a first base 610 to a second base 650. In relay transportation, a container QQ containing the target cargo is transported from the first base 610 to the second base 650 while passing through one or more relay bases and while switching the vehicle PP transporting the container QQ between two or more vehicles PP. In the example of Fig. 7, three relay bases 620, 630, and 640 are passed through as the first, second, and third relay bases.

[0044] 7, the container QQ containing the target baggage is transported from the first base 610 to the relay base 620 by the vehicle PP [1], then the container QQ containing the target baggage is transported from the relay base 620 to the relay base 630 by the vehicle PP [2], then the container QQ containing the target baggage is transported from the relay base 630 to the relay base 640 by the vehicle PP [3], and then the container QQ containing the target baggage is transported from the relay base 640 to the second base 650 by the vehicle PP [4]. In this case, the first base 610 is the base of the sender of the target baggage (the shipper who sends the target baggage), and the second base 650 is the base of the receiver of the target baggage (the shipper who receives the target baggage). In reality, relay transportation of other packages from the second location 650 to the first location 610 may also be carried out, but here we focus only on relay transportation of the target package from the first location 610 to the second location 650.

[0045] Furthermore, each of the base stations described in this specification, such as the first base station, the second base station, and the relay base station, is capable of parking multiple vehicles PP and has space to enable operations such as connecting or disconnecting the container QQ to the vehicle PP and loading and unloading the container QQ from the vehicle PP.

[0046] 8 shows schedule data 700 that defines a schedule for relay transport of a target package from a first base 610 to a second base 650. The schedule data 700 defines a schedule for realizing the relay transport of FIG. 7. Unless otherwise specified, the following relay transport in this embodiment may be considered to refer to relay transport according to the schedule according to the schedule data 700. Note that dates in this embodiment and in each of the drawings referred to are assumed to be dates in the year 2021, and times are expressed in 24-hour format.

[0047] The schedule data 700 includes departure data 710 that defines the schedule at the departure point (first point 610) of the target baggage, relay data 720 that defines the schedule at the relay point 620, relay data 730 that defines the schedule at the relay point 630 (second relay point), relay data 740 that defines the schedule at the relay point 640 (third relay point), arrival data 750 that defines the schedule at the arrival point (second point 650) of the target baggage, and management data 760.

[0048] The dispatch data 710 includes information 711 indicating the sender of the target package, information 712 indicating the departure point of the target package, information 713 indicating the container ID of the container QQ that contains the target package, and information 714 indicating the scheduled departure date and time of the target package from the departure point. Hereinafter, the information 713 will be referred to as container use information 713.

[0049] The departure point of the target cargo is the first base 610. The scheduled departure date and time in the information 714 indicates the date and time when the container QQ containing the target cargo is scheduled to depart from the first base 610, in other words, the date and time when the vehicle PP[1] to which the container QQ is connected (loaded) is scheduled to depart from the first base 610. When the schedule data 700 is created, the container use information 713 is blank (the container ID is not included in the container use information 713), and after the container ID of the container QQ containing the target cargo is determined, the determined container ID is stored in the schedule data 700 as the container use information 713. The container containing the target cargo (the container in which the target cargo is loaded) is hereinafter particularly referred to as the target container.

[0050] The dispatch data 710 further includes information 715 and 716. The information 715 and 716 respectively indicate the name and carrier ID of the carrier responsible for transporting the target container QQ from the first base 610 to the relay base 620. The carrier ID is information unique to the carrier and is carrier identification information for identifying which carrier each carrier is among multiple carriers. Therefore, the multiple carrier IDs for multiple carriers are different from each other. The dispatch data 710 further includes information 717. The information 717 indicates the vehicle ID of the vehicle scheduled to transport the target container QQ from the first base 610 to the relay base 620, i.e., the vehicle ID of vehicle PP[1] (see FIG. 7).

[0051] The relay data 720 includes information 721 to 727. Information 721 and 723 indicate the arrival location and parking location when the vehicle PP [1] to which the target container QQ is connected (loaded) arrives at the relay point 620. The arrival location indicates a rough location, and the parking location indicates a detailed location where the vehicle PP [1] is scheduled to park. Information 722 indicates the scheduled arrival date and time of the vehicle PP [1] at the relay point 620. At the relay point 620, an operation is performed to switch the connection destination of the target container QQ from the vehicle PP [1] to the vehicle PP [2]. Information 724 indicates the scheduled departure date and time from the relay point 620 of the vehicle PP [2] to which the target container QQ is connected. Information 725 and 726 respectively indicate the name and carrier ID of the carrier responsible for transporting the target container QQ from the relay point 620 to the relay point 630. Information 727 indicates the vehicle ID of the vehicle scheduled to transport the target container QQ from the relay point 620 to the relay point 630, i.e., the vehicle ID of vehicle PP[2] (see FIG. 7).

[0052] The relay data 730 includes information 731 to 737. Information 731 and 733 indicate the arrival location and parking location of the vehicle PP [2] to which the target container QQ is connected (loaded) when it arrives at the relay point 630. The arrival location indicates a rough location, and the parking location indicates a detailed location where the vehicle PP [2] is scheduled to park. Information 732 indicates the scheduled arrival date and time of the vehicle PP [2] at the relay point 630. At the relay point 630, an operation is performed to switch the connection destination of the target container QQ from the vehicle PP [2] to the vehicle PP [3]. Information 734 indicates the scheduled departure date and time from the relay point 630 of the vehicle PP [3] to which the target container QQ is connected. Information 735 and 736 respectively indicate the name and carrier ID of the carrier responsible for transporting the target container QQ from the relay point 630 to the relay point 640. Information 737 indicates the vehicle ID of the vehicle scheduled to transport the target container QQ from the relay point 630 to the relay point 640, i.e., the vehicle ID of vehicle PP[3] (see FIG. 7).

[0053] The relay data 740 includes information 741 to 747. Information 741 and 743 indicate the arrival location and parking location of the vehicle PP [3] to which the target container QQ is connected (loaded) when it arrives at the relay point 640. The arrival location indicates a rough location, and the parking location indicates a detailed location where the vehicle PP [3] is scheduled to park. Information 742 indicates the scheduled arrival date and time of the vehicle PP [3] at the relay point 640. At the relay point 640, an operation is performed to switch the connection destination of the target container QQ from the vehicle PP [3] to the vehicle PP [4]. Information 744 indicates the scheduled departure date and time from the relay point 640 of the vehicle PP [4] to which the target container QQ is connected. Information 745 and 746 respectively indicate the name and carrier ID of the carrier responsible for transporting the target container QQ from the relay point 640 to the second base 650. Information 747 indicates the vehicle ID of the vehicle scheduled to transport the target container QQ from the relay point 640 to the second point 650, i.e., the vehicle ID of vehicle PP[4] (see FIG. 7).

[0054] The arrival data 750 includes information 751 indicating the consignee of the target cargo, information 752 indicating the final arrival point (i.e., the second base 650) of the target cargo in the relay transport, and information 753 indicating the scheduled arrival date and time of the target cargo at the final arrival point (i.e., the second base 650). The scheduled arrival date and time in the information 753 indicates the scheduled date and time when the target container QQ is to arrive at the second base 650, in other words, the scheduled date and time when the vehicle PP[4] to which the target container QQ is connected (loaded) is to arrive at the second base 650.

[0055] The management data 760 represents an access code AC_CD, which is a two-dimensional code for allowing the terminal device 2 to access a specific transportation management website, and a QR code (registered trademark) can be used as the access code AC_CD. Additional data 770 can be added to the schedule data 700, and the additional data 770 will be described later.

[0056] In relay transportation, the vehicle PP (vehicle PP with the target container QQ attached) departs from each base until the final arrival base. Therefore, in the schedule data 700, each of the bases 610 to 640 is set as a departure point (each of the bases 610 to 640 is treated as a departure point). Based on the information 714, 724, 734, and 744, the scheduled departure date and time of the vehicle to be transported that should depart from the departure point with the target container QQ attached is determined for each departure point. In the schedule data 700, the vehicles to be transported that should depart from the bases 610, 620, 630, and 640 with the target container QQ attached are vehicles PP[1], PP[2], PP[3], and PP[4], respectively. In addition, information on the carrier ID (716, 726, 736, and 746) that identifies the carrier to which the vehicle to be transported belongs is included in the schedule data 700 for each departure point. Furthermore, the schedule data 700 includes vehicle ID information (717, 727, 737, 747) that identifies the vehicle scheduled for transportation for each departure point.

[0057] In addition, in the relay transportation related to schedule data 700, bases 620, 630, 640, and 650 are bases (arrival points) where the vehicles scheduled for transportation (PP[1], PP[2], PP[3], PP[4]) departing from bases 610, 620, 630, 640 should arrive, and the scheduled arrival dates and times of the vehicles scheduled for transportation (PP[1], PP[2], PP[3], PP[4]) for each arrival point are determined from information 722, 732, 742, and 753.

[0058] The functional blocks (111 to 115; see FIG. 4) of the control unit 11 will be described.

[0059] The schedule data creation unit 111 creates schedule data that represents a schedule of relay transportation. Schedule data 700 in Fig. 8 is an example of schedule data created by the creation unit 111. The creation unit 111 receives input of information representing the wishes and plans of the consignor, consignee, and each carrier through the interface unit 14 or the network NET, and creates data 710, 720, 730, 740, and 750 in the schedule data 700 based on the input information. It is also possible for an administrator to manually input all or part of the data 710 to 750 through the operation unit 142. The creation unit 111 determines an access code AC_CD in association with the data 710 to 750, and includes management data 760 indicating the access code AC_CD in the schedule data 700.

[0060] The schedule data 700 is created by the date and time when the relay transportation starts (for example, by the day before the relay transportation starts), and a schedule table showing all or a part of the schedule data 700 is distributed to each transport company in charge of the relay transportation. The schedule table may be a printed matter or an image that each driver can freely refer to. At least the access code AC_CD is shown in the schedule table.

[0061] As described above, the access code AC_CD is a two-dimensional code for allowing the terminal device 2 to access a specific transportation management website, and the URL (Uniform Resource Locator) of the transportation management website is embedded in the access code AC_CD. The transportation management website is a website operated by the transportation management device 1 (e.g., the management unit 114). By photographing any two-dimensional code with the camera unit 27, the two-dimensional code is read into the terminal device 2.

[0062] 9, a user of a terminal device 2[i] (i.e., a driver of a vehicle PP[i]) of an arbitrary terminal device 2 performs an operation to photograph an access code AC_CD, a container code QQ_CD, and a vehicle code PP_CD with a camera unit 27 of the terminal device 2[i]. As a result, the codes AC_CD, QQ_CD, and PP_CD are read by the terminal device 2[i].

[0063] Each terminal device 2 is assumed to have an application program pre-installed therein that operates to access the website indicated by the read two-dimensional code. Therefore, when the access code AC_CD is read in any terminal device 2[i], the control unit 21 issues an access request to the transportation management website based on the access code AC_CD. The issued access request is accepted by the access request acceptance unit 115 via the network NET. When the management unit 114 receives the access request, it permits or prohibits the terminal device 2[i] from accessing the transportation management website based on the information acquired by the terminal transmission information acquisition unit 112, etc. In the following, the access request refers to an access request to the transportation management website, unless otherwise specified.

[0064] The terminal transmission information acquisition unit 112 receives the transmission information of each terminal device 2 (information transmitted from each terminal device 2) through the network NET and the communication unit 13. As shown in FIG. 10, the transmission information 810 of the terminal device 2[i] includes location information 811 indicating the current location of the terminal device 2[i], carrier information 812 indicating the carrier ID of the carrier to which the vehicle PP[i] belongs, container information 813 indicating the container ID of the container QQ connected to the vehicle PP[i] or to be connected to the vehicle PP[i], and vehicle information 814 indicating the vehicle ID of the vehicle PP[i]. These pieces of information 811-814 may be transmitted from the terminal device 2[i] to the transportation management device 1 at the same time, or may be transmitted from the terminal device 2[i] to the transportation management device 1 in multiple periods. Any information transmitted from each terminal device 2 to the transportation management device 1 (for example, loading information and container inspection result information described later) other than the information 811-814 may also be acquired by the acquisition unit 112.

[0065] The location information 811 is generated using the GPS processing unit 26 of the terminal device 2[i].

[0066] The user of the terminal device 2[i] (i.e., the driver of the vehicle PP[i]) inputs the carrier ID of the carrier to which the user belongs to the terminal device 2[i] through the interface unit 14 of the terminal device 2[i]. The carrier information 812 is formed by the input carrier ID. However, the carrier information 812 may be information other than the carrier ID (but information associated with the carrier ID). For example, the information other than the carrier ID may be information unique to the terminal device 2[i]. In this case, it is assumed that first known information indicating that the unique information of the terminal device 2[i] corresponds to the carrier to which the vehicle PP[i] belongs is registered in advance in the transportation management device 1. Then, the transportation management device 1 can identify the carrier ID of the carrier to which the vehicle PP[i] belongs (in other words, the carrier associated with the terminal device 2[i]) based on the first known information and the unique information of the terminal device 2[i]. Alternatively, for example, the information other than the carrier ID may be unique information (such as a driver's license number) of the user of the terminal device 2[i] (i.e., the driver of the vehicle PP[i]). In this case, it is assumed that second known information indicating that the unique information of the user of the terminal device 2[i] corresponds to the carrier to which the vehicle PP[i] belongs is registered in advance in the transportation management device 1. Then, the transportation management device 1 can identify the carrier ID of the carrier to which the vehicle PP[i] belongs (in other words, the carrier associated with the terminal device 2[i]) based on the second known information and the unique information of the user of the terminal device 2[i].

[0067] In the following, it is assumed that the carrier information 812 is formed when the user of the terminal device 2[i] (i.e., the driver of the vehicle PP[i]) inputs the carrier ID of the carrier to which he or she belongs into the terminal device 2[i] via the interface unit 14 of the terminal device 2[i].

[0068] In the terminal device 2[i], by inputting the container code QQ_CD of the container QQ, container information 813 indicating the container ID of the container QQ is obtained. In the terminal device 2[i], by inputting the vehicle code PP_CD of the vehicle PP[i], vehicle information 814 indicating the vehicle ID of the vehicle PP[i] is obtained.

[0069] The schedule data storage unit 113 stores the schedule data 700 created by the schedule data creation unit 111. The additional data 770 in FIG.

[0070] The management unit 114 executes an access response process to respond to the access request. The access response process will be outlined with reference to Fig. 11. When the access code AC_CD is read by the terminal device 2[i], an access request 820 is issued from the terminal device 2[i] to the transportation management device 1, and in the access request 820, location information 811 indicating the current location of the terminal device 2[i] and carrier information 812 indicating the carrier ID of the carrier to which the vehicle PP[i] belongs are transmitted from the terminal device 2[i] to the transportation management device 1.

[0071] In the access response process, the management unit 114 accepts the access request 820 only when it is determined that the location where the terminal device 2[i] reads the access code AC_CD, the carrier ID entered into the terminal device 2[i], the current date and time, and the system status are valid in relation to the schedule data 700, and rejects the access request 820 otherwise (the system status will be described later). Only when the access request 820 is accepted, is the terminal device 2[i] permitted to access the transportation management website, and the web page of the transportation management website is displayed on the display unit 241 of the terminal device 2[i]. When the access request 820 is rejected, the terminal device 2[i] is prohibited from accessing the transportation management website, and the management unit 114 causes a predetermined error message to be displayed on the display unit 241 of the terminal device 2[i]. Furthermore, the current date and time referenced in approving or rejecting the access request 820 may be the current date and time acquired by the transportation management device 1, or it may be the current date and time acquired by the terminal device 2[i] and transmitted from the terminal device 2[i] to the transportation management device 1.

[0072] The management unit 114 also executes a state management process for managing the state of relay transportation. The state of relay transportation managed by the state management process is referred to here as the system state (transportation management state). The state of relay transportation is the state of relay transportation of the target cargo, and also the state of relay transportation of the target container QQ containing the target cargo. In the state management process, the management unit 114 transitions the system state between a plurality of states based on information transmitted from one or more terminal devices 2. The plurality of states includes a departure permitted state that permits the departure of the vehicle PP connected to the target container QQ.

[0073] In the status management process, the management unit 114 transitions the system state from another state to the departure permitted state (i.e., allows the departure of vehicle PP[i]) only when it is determined that vehicle PP[i] may be permitted to depart from the corresponding base based on the location where the terminal device 2[i] read the access code AC_CD, the carrier ID entered into the terminal device 2[i], the container ID read by the terminal device 2[i], the current date and time, the schedule data 700, and the current system status.

[0074] Below, several specific operation examples, application techniques, modified techniques, etc. related to the transportation management system SYS will be described in several embodiments. The matters described above in this embodiment are applied to each of the following embodiments unless otherwise specified and unless there is a contradiction. If there are matters in each embodiment that contradict the matters described above, the descriptions in each embodiment may take precedence. Furthermore, unless there is a contradiction, matters described in any of the embodiments shown below can also be applied to any of the other embodiments (i.e., any two or more of the embodiments can be combined).

[0075] <<First Example>> A first embodiment will be described below with reference to Fig. 12. The flow of operations of the driver at the first base 610 and the relay bases 620 and 630 in the relay transportation shown in Fig. 7 will be described.

[0076] At the first base 610, the driver of the vehicle PP [1] loads the target cargo into the container QQ, and then has the terminal device 2 [1] read the access code AC_CD. This puts the terminal device 2 [1] into a state of accessing the transportation management website. The state of accessing the transportation management website is hereinafter simply referred to as the access state. In the access state of the terminal device 2 [1], the driver of the vehicle PP [1] has the terminal device 2 [1] read the container code QQ_CD of the container QQ into which the target cargo has been loaded. The container ID embedded in the read container code QQ_CD is stored in the schedule data 700 as the container used information 713 by the management unit 114 (see FIG. 8). The container QQ into which the target cargo has been loaded at the first base 610 will function as the target container thereafter. There are multiple containers QQ into which cargo can be loaded at the first base 610, and the driver of the vehicle PP [1] can load the target cargo into any of the multiple containers QQ that is convenient for him. This allows for greater freedom of operation, as the containers used are not fixed and any available container can be used.

[0077] Furthermore, in the access state of the terminal device 2[1], the driver of the vehicle PP[1] reads the vehicle code PP_CD of the vehicle PP[1] into the terminal device 2[1]. The vehicle ID embedded in the read vehicle code PP_CD is sent to the transportation management device 1, and the management unit 114 checks whether the vehicle ID matches the information 717 in the schedule data 700.

[0078] When the driver of the vehicle PP [1] completes loading of the target cargo into the target container QQ, he / she inspects the target container QQ and then inputs a loading completion notification operation 1112 into the terminal device 2 [1]. This notification operation 1112 includes or is accompanied by an operation of inputting loading information and container inspection result information into the terminal device 2 [1].

[0079] The loading information is information that indicates the loading status of the target cargo in the target container QQ, and may include at least one of text information and image information. For example, the loading information may be text information that indicates how much or how the cargo is loaded in the target container QQ (whether it is loaded without any gaps, whether there are many gaps, etc.). The loading information may also include a photographed image (image taken by the camera unit 27) of the inside of the target container QQ that indicates the loading status of the cargo in the target container QQ.

[0080] The container inspection result information is information showing the results of the inspection performed on the target container QQ. During the inspection of the target container QQ, the target container QQ is checked for problems such as dents or scratches, and information showing the inspection results is included in the container inspection result information. If the target container QQ has problems such as dents or scratches, images captured by the camera unit 27 showing the dents, scratches, etc. can be included in the container inspection result information.

[0081] The loading information and container inspection result information input to the terminal device 2[1] are transmitted from the terminal device 2[1] to the transportation management device 1, and the management unit 114 stores the received loading information and container inspection result information in additional data 770 associated with the schedule data 700 (see FIG. 8). The additional data 770 including the loading information and container inspection result information is stored in the storage unit 113.

[0082] A signal based on the loading completion notification operation 1112 is transmitted from the terminal device 2 [1] to the transportation management device 1. Before receiving the signal based on the notification operation 1112, the system state is the initial state, the pre-departure state ST10. When the signal based on the notification operation 1112 is received by the transportation management device 1, the management unit 114 transitions the system state from the pre-departure state ST10 to the departure ready state ST11. In the access state of the terminal device 2 [1], the current system state is displayed on the transportation management website (therefore, the current system state is displayed on the display unit 241 of the terminal device 2 [1]). The departure ready state ST11 corresponds to a state in which the vehicle PP [1] is permitted to depart from the first base 610 with the target container QQ connected. When the driver of the vehicle PP [1] confirms that the current system state is the departure ready state ST11, he connects (loads) the target container QQ to the vehicle PP [1], and then departs the vehicle PP [1] from the first base 610 to the relay base 620. A message indicating that the system state has transitioned to the departure ready state ST11 may be displayed on the display unit 241 of the terminal device 2[1].

[0083] After confirming that the system status is in the departure ready state ST11, the driver of the vehicle PP[1] cancels the access status of the terminal device 2[1] by inputting a predetermined access blocking operation to the terminal device 2[1]. Even if the access blocking operation is not input, when a predetermined timeout period has elapsed after the terminal device 2[1] starts accessing the transportation management website, the access status of the terminal device 2[1] is canceled under the control of the management unit 114. The access status of the terminal device 2[1] is canceled at least before the vehicle PP[1] reaches the relay point 620.

[0084] The administrator checks whether the system state is switching according to the time determined by the schedule data 700. This check is performed not only at the first base 610 but also at each relay base. If there is a problem, the administrator takes necessary measures such as contacting the corresponding carrier (in the case of the first base 610, the carrier of the vehicle PP[1]).

[0085] For example, if the vehicle PP different from the vehicle PP indicated in the information 717 (see FIG. 8) in the schedule data 700 is used to load the target cargo, the management unit 114 generates an error (performs a predetermined error process) when the vehicle code PP_CD is read. In this case, the driver or the carrier must contact the manager by phone or the like to request a change to the schedule data 700. Such measures can also be taken at each relay point.

[0086] If the system state remains in the pre-departure state ST10 even when the scheduled departure date and time indicated by the information 714 (see FIG. 8) in the schedule data 700 arrives, or even when a certain time has passed since the scheduled departure date and time, the manager contacts the carrier indicated by the information 715 or the driver of the vehicle PP[1] by telephone or the like. Such a situation occurs when the work required for departure from the first base 610 is delayed due to some kind of trouble, or when the driver forgets to input the necessary operation. In the former case, the manager takes the necessary measures for the trouble. In the latter case, the manager can take measures such as manually switching the system state from the pre-departure state ST10 to the departure ready state ST11 after checking the status of the driver of the vehicle PP[1]. Such measures can also be taken at each relay base.

[0087] After the vehicle PP[1] departs from the first base 610 and arrives at the relay base 620, the driver of the vehicle PP[1] reads the access code AC_CD into the terminal device 2[1]. This causes the terminal device 2[1] to access the transportation management website again, and at this time, an arrival notification signal 1120 is sent from the terminal device 2[1] to the transportation management device 1. When the transportation management device 1 receives the arrival notification signal 1120, the management unit 114 transitions the system state from the departure ready state ST11 to the arrival state ST21.

[0088] The driver of the vehicle PP[1] detaches the target container QQ from the vehicle PP[1] and places the target container QQ at a predetermined position in the relay point 620, and then inputs a notification operation 1122 of the completion of the previous stage handover to the terminal device 2[1]. This notification operation 1122 includes or is accompanied by an operation of inputting container inspection result information to the terminal device 2[1]. The container inspection result information input to the terminal device 2[1] is transmitted from the terminal device 2[1] to the transportation management device 1, and the management unit 114 stores the received container inspection result information in the additional data 770 associated with the schedule data 700 (see FIG. 8).

[0089] A signal based on the previous stage handover completion notification operation 1122 is transmitted from the terminal device 2 [1] to the transportation management device 1. When the signal based on the notification operation 1122 is received by the transportation management device 1, the management unit 114 transitions the system state from the arrival state ST21 to the handover available state ST22.

[0090] Thereafter, when the vehicle PP[2] that is to take over and transport the target container QQ arrives at the relay point 620, the driver of the vehicle PP[2] reads the access code AC_CD into the terminal device 2[2]. This puts the terminal device 2[2] into a state in which it is accessing the transportation management website, and at this time, the terminal device 2[2] transmits an arrival notification signal 1124 to the transportation management device 1. When the transportation management device 1 receives the arrival notification signal 1124, the management unit 114 transitions the system state from the takeover ready state ST22 to the arrival state ST23.

[0091] In the access state of the terminal device 2 [2], the driver of the vehicle PP [2] reads the container code QQ_CD of the target container QQ and the vehicle code PP_CD of the vehicle PP [2] into the terminal device 2 [2]. The container ID embedded in the read container code QQ_CD and the vehicle ID embedded in the read vehicle code PP_CD are transmitted from the terminal device 2 [2] to the transportation management device 2. The management unit 114 checks the consistency between the container ID and vehicle ID received from the terminal device 2 [2] and the information 713 and 727 in the schedule data 700 (see FIG. 8). If there is a consistency, a predetermined OK message is displayed on the transportation management website (therefore, the OK message is displayed on the display unit 241 of the terminal device 2 [2]). If there is no consistency, a predetermined error message is displayed on the transportation management website (therefore, the error message is displayed on the display unit 241 of the terminal device 2 [2]). For example, if the container ID received from the terminal device 2 [2] differs from the container ID in the used container information 713, the above error message is displayed. This prevents the wrong container from being taken out.

[0092] After confirming the display of the OK message, the driver of the vehicle PP[2] inspects the target container QQ and then inputs a post-stage handover completion notification operation 1126 to the terminal device 2[2]. This notification operation 1126 includes or is accompanied by an operation of inputting container inspection result information to the terminal device 2[2]. The container inspection result information input to the terminal device 2[2] is transmitted from the terminal device 2[2] to the transportation management device 1, and the management unit 114 stores the received container inspection result information in the additional data 770 associated with the schedule data 700 (see FIG. 8).

[0093] A signal based on the post-stage handover completion notification operation 1126 is transmitted from the terminal device 2 [2] to the transportation management device 1. When the signal based on the notification operation 1126 is received by the transportation management device 1, the management unit 114 transitions the system state from the arrival state ST23 to the departure ready state ST24. In the access state of the terminal device 2 [2], the current system state is displayed on the transportation management website (therefore, the current system state is displayed on the display unit 241 of the terminal device 2 [2]). The departure ready state ST24 corresponds to a state in which the vehicle PP [2] is permitted to depart from the relay point 620 with the target container QQ connected. When the driver of the vehicle PP [2] confirms that the current system state is the departure ready state ST24, he connects (loads) the target container QQ to the vehicle PP [2], and then departs the vehicle PP [2] from the relay point 620 to the relay point 630.

[0094] In addition, in the access state of the terminal device 2[2], the management unit 114 can transmit the additional data 770 to the terminal device 2[2], and the contents of the additional data 770 can be displayed on the display unit 241 in the terminal device 2[2].

[0095] The driver of the vehicle PP[2] can know the loading status of the cargo in the target container QQ by referring to the loading information in the additional data 770, and can drive accordingly. For example, depending on the loading status, the cargo may easily fall off, so the driver can pay special attention to the driving speed and sharp curves.

[0096] After confirming that the system status is in the departure ready state ST24, the driver of the vehicle PP[2] cancels the access status of the terminal device 2[2] by inputting a predetermined access blocking operation into the terminal device 2[2]. Even if the access blocking operation is not input, when a predetermined timeout period has elapsed after the terminal device 2[2] starts accessing the transportation management website, the access status of the terminal device 2[2] is canceled under the control of the management unit 114. The access status of the terminal device 2[2] is canceled at least before the vehicle PP[2] reaches the relay point 630.

[0097] Thereafter, for each relay point, the same tasks, operations, and processes as those at the relay point 620 are executed, and the matters described above regarding the relay point 620 are also applied to the relay points 630 and 640. However, when the matters described above regarding the relay point 620 are applied to the relay point 630, among the matters described above regarding the relay point 620, the signs PP[1] and PP[2] are replaced with PP[2] and PP[3], respectively, and the signs 2[1] and 2[2] are replaced with 2[2] and 2[3], respectively, and the signs 1120, 1122, 1124, and 1126 are replaced with 1130, 1132, 1134, and 1136, respectively, and the signs ST11, ST21, ST22, ST23, and ST24 are replaced with the signs ST24, ST31, ST32, ST33, and ST34, respectively.

[0098] 12 shows the flow of operations from the first base 610 to the relay base 630 via the relay base 620, but the flow of operations at the relay base 640 and the second base 650 is similar. However, since the second base 650 is the final arrival base of the target cargo in the relay transportation, the relay transportation is completed when the vehicle PP[4] arrives at the second base 650 and the arrival notification signal from the terminal device 2[4] is received by the transportation management device 1. Therefore, when the arrival notification signal from the terminal device 2[4] is received by the transportation management device 1, the management unit 114 transitions the system state to the final arrival state and ends the series of processes related to the relay transportation.

[0099] The flow described above with reference to Figure 12 is basically the flow when work, operations and driving are performed according to the schedule data 700. The flow will be described in more detail with reference to Figure 13 and other figures.

[0100] FIG. 13 is a flow chart showing the flow of processing related to an access request, and the flow of the processing will be described with reference to FIG. An arbitrary vehicle PP that has been taken notice of is called a "vehicle of interest PP." It is assumed that the vehicle of interest PP has arrived at a certain point of interest. The point of interest can be any one of bases 610 to 650. First, in step S111, the vehicle of interest PP arrives at the point of interest, and the driver of the vehicle of interest PP has the terminal device 2 that he or she owns read the access code AC_CD. The terminal device 2 that reads the access code AC_CD in step S111 is called a terminal device of interest 2. In addition, the date and time when the access code AC_CD is read by the terminal device of interest 2 in step S111 is called a date and time of interest. The point where the access code AC_CD is read by the terminal device of interest 2 is the point of interest. Following the reading of the access code AC_CD by the terminal device of interest 2, the carrier ID of the carrier to which the vehicle of interest PP belongs is input to the terminal device of interest 2 through the interface unit 24. It is considered that the carrier ID is also input in step S111.

[0101] Then, in step S112 following step S111, the control unit 21 of the noted terminal device 2 issues an access request to the transportation management website based on the read access code AC_CD. This access request corresponds to the access request 820 shown in FIG. 11, and is sent to the transportation management device 1. In the access request 820 from the noted terminal device 2 (see FIG. 11), location information 811 indicating the current location of the noted terminal device 2 (hence the noted point), and company information 812 indicating the carrier ID of the carrier to which the noted vehicle PP belongs are transmitted from the noted terminal device 2 to the transportation management device 1. Hereinafter, it is considered that the access request 820 includes the location information 811 and the company information 812.

[0102] An access request 820 from the target terminal device 2 is accepted by the access request accepting section 115 via the network NET. When the management section 114 receives the access request 820, it executes an access response process for responding to the access request 820 in step S113.

[0103] In the access response process in step S113, the management unit 114 judges whether a predetermined access permission condition is satisfied or not based on the location information 811 and the company information 812 (i.e., the shipping company ID; see FIG. 11) from the noted terminal device 2, the current date and time, the schedule data 700, and the current system state. If the access permission condition is satisfied (Y in step S114), the management unit 114 approves the access request 820 (i.e., permits the noted terminal device 2 to access the shipping management website), and thus, in step S115, the access state of the noted terminal device 2 to the shipping management website is established. On the other hand, if the access permission condition is not satisfied (N in step S114), the management unit 114 rejects the access request 820 (i.e., prohibits the noted terminal device 2 from accessing the shipping management website), and executes a predetermined error process in step S141. The error process in step S141 includes a process of displaying a predetermined error message on the display unit 241 of the noted terminal device 2. Other error processes described later may be similar to the error process in step S141.

[0104] Assuming a case CASE1 in which the point of interest is a point within the first location 610, the success or failure of the access permission condition will be described.

[0105] In case CASE1 (see FIG. 8), it is valid in light of the schedule data 700 that the vehicle PP of the carrier indicated by the information 715 arrives at the first base 610 near the scheduled departure date and time indicated by the information 714 and that the access code AC_CD is read at the first base 610. In addition, since the access code AC_CD is read at the first base 610 in case CASE1, the system state at the target date and time should be the pre-departure state ST10 (see FIG. 12).

[0106] Therefore, in case CASE1 (see Figure 8), the access permission condition is met only if the carrier ID of the carrier to which the target vehicle PP belongs matches the carrier ID in information 716, and the difference between the current date and time and the scheduled departure date and time in information 714 is within a predetermined time (e.g., one hour), and the current system state is the pre-departure state ST10; otherwise, the access permission condition is not met.

[0107] Furthermore, even if the carrier ID of the carrier to which the noted vehicle PP belongs matches the carrier ID in information 716, and the difference between the current date and time and the scheduled departure date and time in information 714 is within a predetermined time (e.g., one hour), and the current system state is the pre-departure state ST10, if the location where the noted terminal device 2 read the access code AC_CD is different from the first location 610 (e.g., if it is the relay location 620), the access permission condition is not met.

[0108] Next, the success or failure of the access permission condition will be described assuming case CASE2 where the point of interest is a point within the relay point 620. Case CASE2 can be subdivided into case CASE2_A assuming a situation where a vehicle PP involved in transportation between the first location 610 and the relay point 620 arrives at the relay point 620, and case CASE2_B assuming a situation where a vehicle PP involved in transportation between the relay point 620 and the relay point 630 arrives at the relay point 620.

[0109] In case CASE2_A (see FIG. 8), it is valid in light of the schedule data 700 that the vehicle PP of the carrier indicated in the information 715 arrives at the relay point 620 near the scheduled arrival date and time indicated in the information 722 and that the access code AC_CD is read at the relay point 620. In addition, in case CASE2_A, the system state at the target date and time should be the departure ready state ST11 (see FIG. 12).

[0110] Therefore, in case CASE2_A (see Figure 8), the access permission condition is met only if the carrier ID of the carrier to which the target vehicle PP belongs matches the carrier ID in information 716, and the difference between the current date and time and the scheduled arrival date and time in information 722 is within a predetermined time (e.g., one hour), and the current system state is the departure permitted state ST11, and the access permission condition is not met in any other cases.

[0111] Furthermore, even if the carrier ID of the carrier to which the noted vehicle PP belongs matches the carrier ID in information 716, and the difference between the current date and time and the scheduled arrival date and time in information 722 is within a predetermined time (e.g., one hour), and the current system state is the departure-ready state ST11, if the point where the noted terminal device 2 read the access code AC_CD is different from the relay point 620 (e.g., if it is the relay point 630), the access permission condition is not met.

[0112] In case CASE2_B (see FIG. 8), it is valid in light of the schedule data 700 that the vehicle PP of the carrier indicated in the information 725 arrives at the relay point 620 near the scheduled departure date and time indicated in the information 724 and that the access code AC_CD is read at the relay point 620. In addition, in case CASE2_B, the system state at the target date and time should be the takeover ready state ST22 (see FIG. 12).

[0113] Therefore, in case CASE2_B (see Figure 8), the access permission condition is met only if the carrier ID of the carrier to which the target vehicle PP belongs matches the carrier ID in information 726, and the difference between the current date and time and the scheduled departure date and time in information 724 is within a predetermined time (e.g., one hour), and the current system state is the handover possible state ST22, and the access permission condition is not met in any other cases.

[0114] Furthermore, even if the carrier ID of the carrier to which the noted vehicle PP belongs matches the carrier ID in information 726, and the difference between the current date and time and the scheduled departure date and time in information 724 is within a predetermined time (e.g., one hour), and the current system state is the handover possible state ST22, if the point where the noted terminal device 2 read the access code AC_CD is different from the relay point 620 (e.g., if it is the relay point 630), the access permission condition is not met.

[0115] At the relay points 630 and 640 and the second point 650, whether the access permission condition is met is determined in the same manner as described above.

[0116] In this way, access to the transportation management website is permitted only when a person from a correct carrier reads the access code AC_CD at the correct date and time at the correct location in accordance with the schedule data 700, and the system status at that time is appropriate in accordance with the schedule data 700. This type of access management prohibits access when the carrier, operation date and time, etc. are incorrect. Since the system status transitions to a departure-ready state only after access is permitted (see FIG. 12), the implementation of relay transportation including errors is suppressed. In addition, it is not desirable to allow unconditional access to the transportation management website when a person not involved in relay transportation reads the access code AC_CD using any terminal device (because the contents of relay transportation may be leaked to unspecified persons). The method of this embodiment eliminates unauthorized access.

[0117] The flow chart of FIG. 14 shows the flow of processing related to the departure of the vehicle PP from the first base 610. The flow of the processing will be described with reference to FIG. 14. The processing of steps S211 to S215 and S241 is the same as the processing of steps S111 to S115 and S141 of FIG. 13, respectively. Here, the attention point, attention vehicle, and attention terminal device in step S211 are the first base 610, the vehicle PP [1], and the terminal device 2 [1], respectively, and the attention date and time in step S211 matches or is sufficiently close to the scheduled departure date and time in the information 714 (see FIG. 8), and the system state in step S211 is the pre-departure state ST10. Then, the access permission condition is established, so the process proceeds from step S211 to step S215 via steps S212, S213, and S214, and the access state of the terminal device 2 [1] to the transportation management website is established in step S215. The processing after step S215 will be described below.

[0118] After the access state is established in step S215, the process proceeds from step S215 to step S216. In step S216, the driver of the vehicle PP[1] has the terminal device 2[1] read the container code QQ_CD of the container QQ that has loaded the target cargo (hence the target container QQ). In step S216, the terminal device 2[1] transmits to the transportation management device 1 container information 1310 (corresponding to the container information 813 in FIG. 10) that indicates the container ID embedded in the read container code QQ_CD.

[0119] In step S217 following step S216, the container information 1310 is received by the transportation management device 1, and the management unit 114 stores the container ID based on the container information 1310 in the used container information 713 (see FIG. 8) of the schedule data 700. If the container ID indicated by the container information 1310 is an invalid ID (N in step S218), the process proceeds from step S217 to step S242, and the management unit 114 executes a predetermined error process. For example, if the container ID indicated by the container information 1310 represents a container that should not exist at the first base 610, or if it differs from any of a plurality of registered container IDs that have been determined in advance, it is determined to be an invalid ID. If the container ID indicated by the container information 1310 is not an invalid ID (Y in step S218), the management unit 114 transmits a predetermined normal signal 1312 to the terminal device 2 [1] to cause a transition to step S219.

[0120] When the terminal device 2[1] receives the normal signal 1312 in step S219, a message requesting the reading of the vehicle code PP_CD is displayed on the display unit 241 of the terminal device 2[1]. In response to this, the driver of the vehicle PP[1] has the terminal device 2[1] read the vehicle code PP_CD of the vehicle PP[1]. In step S219, the terminal device 2[1] transmits to the transportation management device 1 vehicle information 1320 (corresponding to the vehicle information 814 in FIG. 10) indicating the vehicle ID embedded in the read vehicle code PP_CD.

[0121] In step S220 following step S219, the transportation management device 1 receives the vehicle information 1320, and the management unit 114 executes a process of confirming the consistency of the vehicle ID. In the process of confirming the consistency of the vehicle ID in step S220, the management unit 114 determines whether the vehicle ID indicated in the vehicle information 1320 matches the vehicle ID indicated in the information 717 (see FIG. 8). If the vehicle IDs match (Y in step S221), the management unit 114 transmits a predetermined normal signal 1322 to the terminal device 2 [1] and causes a transition to step S222. If the vehicle IDs do not match (N in step S221), the management unit 114 causes a transition to step S243 and executes a predetermined error process in step S243.

[0122] When the normal signal 1322 is received by the terminal device 2 [1], a message is displayed on the display unit 241 of the terminal device 2 [1] indicating that the reading of the container code QQ_CD and the vehicle code PP_CD has been completed normally. In response to this, the driver of the vehicle PP [1] inputs a loading completion notification operation 1112 (see FIG. 12) to the terminal device 2 [1] in step S222 as soon as the loading of the target cargo and the inspection of the target container QQ are completed. In response to this input, a loading completion signal 1330 is transmitted from the terminal device 2 [1] to the transportation management device 1. The notification operation 1112 includes or is accompanied by an operation of inputting loading information and container inspection result information to the terminal device 2 [1], and the loading information and container inspection result information are included in the loading completion signal 1330.

[0123] In step S223 following step S222, the transportation management device 1 receives the loading completion signal 1330, and the management unit 114 executes a departure permission response process. In the departure permission response process, the management unit 114 stores the loading information and container inspection result information in the signal 1330 in the additional data 770 associated with the schedule data 700 (see FIG. 8). At this time, the management unit 114 checks whether there is any defect in the loading completion signal 1330, and if there is no defect (Y in S224), causes a transition to step S225. If there is a defect (N in step S224), causes a transition to step S244, and executes a predetermined error process in step S244.

[0124] Until step S225, the system state is maintained in the pre-departure state ST10, which is the initial state. In step S225, the management unit 114 transitions the system state from the pre-departure state ST10 to the departure ready state ST11. The result of this transition is transmitted to the terminal device 2[1], for example, by transmitting a departure permission signal 1332 from the transportation management device 1 to the terminal device 2[1], and in step S226 following step S225, the display unit 241 of the terminal device 2[1] displays that the system state has switched to the departure ready state ST11. When the driver of the vehicle PP[1] confirms that the current system state is the departure ready state ST11, he connects (loads) the target container QQ to the vehicle PP[1], and then departs the vehicle PP[1] from the first base 610 to the relay base 620.

[0125] The flowchart in FIG. 15 shows the flow of processing related to the departure of vehicle PP from relay point 620. The flow of the processing will be described with reference to FIG. 15. The processing of steps S311 to S315 and S341 is the same as the processing of steps S111 to S115 and S141 in FIG. 13, respectively. Here, the attention point, attention vehicle, and attention terminal device in step S311 are relay point 620, vehicle PP [2], and terminal device 2 [2], respectively, and the attention date and time in step S311 matches or is sufficiently close to the scheduled departure date and time in information 724 (see FIG. 8), and the system state in step S311 is the takeover possible state ST22. Then, the access permission condition is established, so the process proceeds from step S311 to step S315 via steps S312, S313, and S314, and the access state of terminal device 2 [2] to the transportation management website is established in step S315.

[0126] 15, when the access permission condition is satisfied, the management unit 114 assumes that the vehicle PP that is to take over and transport the target container QQ has arrived at the relay point 620, and transitions the system state from the takeover ready state ST22 to the arrival state ST23. The process after step S315 will be described below.

[0127] After the access state is established in step S315, the process proceeds from step S315 to step S316. In step S316, the driver of the vehicle PP[2] has the terminal device 2[2] read the container code QQ_CD of the container QQ that is to be taken over for transport. The container QQ that is to be taken over for transport is, to be precise, the target container QQ in which the target cargo has been loaded. In step S316, the terminal device 2[2] transmits container information 1410 (corresponding to the container information 813 in FIG. 10) indicating the container ID embedded in the read container code QQ_CD to the transportation management device 1.

[0128] In step S317 following step S316, the transportation management device 1 receives the container information 1410, and the management unit 114 executes a process of confirming the consistency of the container ID. In the process of confirming the consistency of the container ID in step S317, the management unit 114 judges whether or not the container ID indicated in the container information 1410 matches the container ID indicated in the used container information 713 (see FIG. 8). If the container IDs match (Y in step S318), the management unit 114 transmits a predetermined normal signal 1412 to the terminal device 2 [2] and causes a transition to step S319. If the container IDs do not match (N in step S318), the management unit 114 causes a transition to step S342 and executes a predetermined error process in step S342.

[0129] The container ID matching confirmation process prevents the transport of an incorrect container. In addition, by performing the container ID matching confirmation process before connecting the container QQ to the vehicle PP [2], even if an error occurs, almost no unnecessary work is generated. If an error is detected at the stage of departure from the relay point 620 after the container QQ is connected to the vehicle PP [2], the container QQ will need to be reconnected. When transition to step S319 occurs, the container QQ corresponding to the container code QQ_CD read in step S316 is the target container.

[0130] When the terminal device 2[2] receives the normal signal 1412 in step S319, a message requesting the reading of the vehicle code PP_CD is displayed on the display unit 241 of the terminal device 2[2]. In response to this, the driver of the vehicle PP[2] has the terminal device 2[2] read the vehicle code PP_CD of the vehicle PP[2]. In step S319, the terminal device 2[2] transmits to the transportation management device 1 vehicle information 1420 (corresponding to the vehicle information 814 in FIG. 10) indicating the vehicle ID embedded in the read vehicle code PP_CD.

[0131] In step S320 following step S319, the transportation management device 1 receives the vehicle information 1420, and the management unit 114 executes a process of confirming the consistency of the vehicle ID. In the process of confirming the consistency of the vehicle ID in step S320, the management unit 114 determines whether the vehicle ID indicated in the vehicle information 1420 matches the vehicle ID indicated in the information 727 (see FIG. 8). If the vehicle IDs match (Y in step S321), the management unit 114 transmits a predetermined normal signal 1422 to the terminal device 2 [2] and causes a transition to step S322. If the vehicle IDs do not match (N in step S321), the management unit 114 causes a transition to step S343 and executes a predetermined error process in step S343.

[0132] When the normal signal 1422 is received by the terminal device 2 [2], a message is displayed on the display unit 241 of the terminal device 2 [2] indicating that the reading of the container code QQ_CD and the vehicle code PP_CD has been completed normally. In response to this, the driver of the vehicle PP [2] inputs a post-stage handover completion notification operation 1126 (see FIG. 12) to the terminal device 2 [2] in step S322 as soon as the inspection work of the target container QQ is completed. In response to this input, a handover completion signal 1430 is transmitted from the terminal device 2 [2] to the transportation management device 1. The handover completion signal 1430 includes or is accompanied by an operation of inputting container inspection result information to the terminal device 2 [2], and the container inspection result information is included in the handover completion signal 1430.

[0133] In step S323 following step S322, the transportation management device 1 receives a handover completion signal 1430, and the management unit 114 executes a departure permission response process. In the departure permission response process, the container inspection result information in the signal 1430 is stored in the additional data 770 associated with the schedule data 700 (see FIG. 8). At this time, the management unit 114 checks whether there is any defect in the handover signal 1430, and if there is no defect (Y in S324), a transition to step S325 is initiated. If there is a defect (N in step S324), a transition to step S344 is initiated, and a predetermined error process is executed in step S344.

[0134] In step S325, the management unit 114 transitions the system state from the arrival state ST23 to the departure ready state ST24. The result of this transition is transmitted to the terminal device 2 [2], for example, by transmitting a departure permission signal 1432 from the transportation management device 1 to the terminal device 2 [2], and in step S326 following step S325, the display unit 241 of the terminal device 2 [2] displays that the system state has switched to the departure ready state ST24. When the driver of the vehicle PP [2] confirms that the current system state is the departure ready state ST24, he connects (loads) the target container QQ to the vehicle PP [2], and then departs the vehicle PP [2] from the relay point 620 to the relay point 630.

[0135] Although the process flow relating to the departure of vehicle PP from relay point 620 has been described with a focus on relay point 620, the same process is also applied to the other relay points (630, 640).

[0136] The main points of the technical content shown in this embodiment are summarized below.

[0137] The terminal transmission information acquisition unit 112 acquires location information indicating the current location of the terminal device 2[i], a carrier ID (carrier identification information) for identifying the carrier to which the vehicle PP[i] belongs, and a container ID (container identification information) for identifying the container QQ that contains the target baggage, based on the transmission information of the terminal device 2[i] corresponding to the vehicle PP[i] for transporting the target baggage. The management unit 114 transitions the system state (transportation management state) between a plurality of states including a departure possible state. The departure possible state corresponds to a state in which the departure of the vehicle PP[i] connected to the container QQ is permitted (a state in which the departure of the vehicle PP[i] is permitted with the container QQ placed). At this time, the management unit 114 is configured to be able to transition the system state to the departure possible state based on the location information, carrier ID, and container ID based on the transmission information of the terminal device 2[i], the current date and time, the schedule data 700, and the current system information.

[0138] This allows the departure of the vehicle only when the vehicle of the correct carrier according to the schedule data 700 is connected to the correct container at the correct date and time at the correct location, and erroneous transportation is avoided. For example, with regard to the relay point 620 (FIG. 15), the departure of the vehicle is only permitted when the vehicle of the correct carrier (S311), at the correct date and time (S311), at the correct location (S311), and connected to the correct container in relation to the schedule data 700 (S325 and S326 via Y in S316, S317, and S318), and transportation of an incorrect container is avoided. Furthermore, by making a transition to a departure-ready state of the system state with reference to the current system state, erroneous transportation that is not consistent with the current system state is avoided.

[0139] 13, when the management unit 114 receives an access request 820 from the terminal device 2[i], it determines whether the access permission conditions are met based on the location information and the carrier ID based on the transmitted information of the terminal device 2[i], the current date and time, the schedule data 700, and the current system information, and permits the terminal device 2[i] to access the transportation management website only if the access permission conditions are met. Then, it is configured to be able to update the system status to a departure ready status after the access is permitted (for example, in FIG. 14, steps S225 and S226 via step S215, and in FIG. 15, steps S325 and S326 via step S315).

[0140] This type of access management prohibits access with incorrect carrier or operation date and time, etc. And since the system state transitions to a departure ready state only after access has been permitted, the execution of transportation including errors is suppressed. It is also possible to eliminate unauthorized access.

[0141] More specifically, as shown in FIG. 8, the schedule data 700 sets the first base station (610) and each relay base station (620, 630, 640) as departure points, and includes, for each departure point, the scheduled departure date and time (714, 724, 734, 744) of the vehicle to which the container QQ is to be attached (placed) and depart, and a carrier ID (716, 726, 736, 746) for identifying the carrier to which the vehicle belongs.

[0142] The management unit 114 permits the departure of the vehicle PP[i] connected to the container QQ (vehicle PP[i] in which the container QQ is placed) from the departure point by transitioning the system state from the state before departure from the departure point is permitted (e.g., ST10, or ST21, ST22, or ST23) to a state in which departure from the departure point is permitted (e.g., ST11 or ST24).

[0143] The terminal transmission information acquisition unit 112 acquires location information (corresponding to the current location information of the vehicle PP corresponding to the terminal device 2), carrier ID (carrier ID of the carrier to which the vehicle PP corresponding to the terminal device 2 belongs), and container ID (container ID of the container QQ that is scheduled to be connected to the vehicle PP corresponding to the terminal device 2) for each terminal device 2 based on the transmission information of multiple terminal devices 2 corresponding to multiple vehicle PP.

[0144] When the management unit 114 receives an access request 820 from a target terminal device 2, which is one of the multiple terminal devices 2, while the system state is before departure from a target departure point (corresponding to the target point in Figure 13), which is one of the first base (610) and each relay point (620, 630, 640), is permitted (see Figure 13), the management unit 114 operates as follows. That is, the management unit 114 permits or prohibits the attention terminal device 2 from accessing the transportation management website based on the relationship between the current location of the attention terminal device 2 and the attention departure point (e.g., relay point 620), the relationship between the carrier ID based on the transmitted information of the attention terminal device 2 and the carrier ID corresponding to the attention departure point in the schedule data 700 (e.g., carrier ID in information 726: see FIG. 8), the relationship between the current date and time and the scheduled departure date and time corresponding to the attention departure point in the schedule data 700 (e.g., scheduled departure date and time in information 724: see FIG. 8), and the current system state (e.g., corresponding to the transition from step S314 to step S315 or S341 in FIG. 15).The management unit 114 is configured to be able to transition the system state to a state in which departure from the attention departure point is permitted (e.g., departure permitted state ST24) after the access is permitted.

[0145] This type of access management prohibits access to relay transport with incorrect carrier or operation date and time, etc. Furthermore, since the system state transitions to a departure ready state only after access has been permitted, the execution of relay transport including errors is suppressed. It is also possible to eliminate unauthorized access.

[0146] After permitting access to the target terminal device 2, the management unit 114 transitions the system state to a state in which departure from the target departure point is permitted when a predetermined departure permission condition is satisfied. For example, in the flowchart of Fig. 14, the departure permission conditions include conditions that should be satisfied after reaching step S215 and before reaching step S225 or S226. Similarly, in the flowchart of Fig. 15, the departure permission conditions include conditions that should be satisfied after reaching step S315 and before reaching step S325 or S326.

[0147] The relay transportation from the first base 610 to the second base 650 is realized using a plurality of vehicles PP, and in this embodiment, the plurality of vehicles PP are composed of vehicles PP[1] to PP[5]. Now, the vehicle PP[1] that transports the target luggage from the first base 610 to the relay base 620 is called the first target vehicle, and the vehicle PP[2] that transports the target luggage from the relay base 620 to the relay base 630 is called the second target vehicle. However, the second target vehicle may be the vehicle PP that transports the target luggage from the relay base 620 to the second base 650 (in this case, the relay bases 630 and 640 are considered not to exist, and the relay transportation is realized without using the vehicles PP[3] to PP[5]).

[0148] The container ID based on the transmission information of the first terminal device 2[1] corresponding to the first target vehicle PP[1] is stored in the schedule data 700 as the container-to-be-used information 713 (see FIG. 8). However, as will be described later in a second embodiment, a container ID that is specified in advance, regardless of the transmission information of the first terminal device 2[1], may be stored in the container-to-be-used information 713 in the schedule data 700.

[0149] The management unit 114 permits the departure of the second target vehicle PP[2] to which the container QQ is connected, from the relay point 620 by transitioning the system state for the relay point 620 from the state before departure from the relay point 620 was permitted to a state in which departure from the relay point 620 is permitted (departure permitted state ST24) (steps S325 and S326 in Figure 15).

[0150] With regard to the relay point 620, when the system state is before departure from the relay point 620 is permitted, the management unit 114 responds to an access request 820 from the second terminal device 2[2] corresponding to the second target vehicle PP[2] by permitting access to the transportation management website by the second terminal device 2[2] (Y in step S314 and step S315), and then transitions the system state to a state in which departure from the relay point 620 is permitted (departure permitted state ST24) if a specified departure permission condition is met.

[0151] The departure permission condition here includes a container matching condition that the container ID based on the transmission information of the second terminal device 2 [2] matches the container ID (container ID in the container use information 713) stored in the schedule data 700. For example, in the flowchart of Figure 15, the process proceeds from step S317 to step S319 via step S318 only when the container matching condition is met.

[0152] By including a container matching condition in the departure permission conditions, the occurrence of a situation in which the second target vehicle PP[2] departs from the relay point 620 with an incorrect container connected to the second target vehicle PP[2] is prevented.

[0153] In addition, the terminal transmission information acquisition unit 112 can acquire loading information related to the loading status of cargo into the container QQ from the first terminal device 2[1]. Then, the management unit 114 can transmit the loading information to the second terminal device 2[2] after permitting the second terminal device 2[2] to access the transportation management website.

[0154] This allows the driver of the second target vehicle PP[2] to know the loading status of the cargo in the container QQ that he is to take over and transport, and can drive accordingly. For example, since the cargo is more likely to fall off depending on the loading status, the driver can pay special attention to the driving speed and sharp curves.

[0155] In addition, for the above-mentioned noted departure point and noted terminal device 2, when the system state is in a state before departure from the noted departure point is permitted, the management unit 114 permits the noted terminal device 2 to access the transportation management website in response to an access request 820 from the noted terminal device 2, and then, if a specified departure permission condition is met, transitions the system state to a state in which departure from the noted departure point is permitted (e.g., departure permitted state ST24).

[0156] In this case, the departure permission condition includes a vehicle matching condition that the vehicle ID based on the transmitted information of the target terminal device 2 (e.g., the vehicle ID of vehicle PP[2]) matches the vehicle ID stored in the schedule data 700 in correspondence with the target departure point (e.g., the relay point 620) (e.g., the vehicle ID in information 727).

[0157] By including the vehicle matching condition in the departure permission condition, it is possible to prevent the occurrence of a situation in which cargo is transported while a vehicle PP that does not conform to the schedule is participating in relay transportation.

[0158] The access request receiving unit 114 is configured to receive an access request 820 issued from the terminal device 2 by photographing a two-dimensional code (AC_CD) associated with the schedule data 700 with the terminal device 2 .

[0159] This makes it possible to implement access management to ensure correct relay transportation in a simple manner by simply photographing a two-dimensional code, which is highly convenient.

[0160] <<Second Example>> A second embodiment will be described. The container QQ used in the relay transportation from the first base 610 to the second base 650 may be designated in advance by the transportation management device 1. In this case, the schedule data creation unit 111 creates schedule data 700 in which a predetermined container ID is stored in the container use information 713 of FIG. 8. The container ID in the container use information 713 is clearly indicated in the schedule table distributed to each transport company. The container QQ having the container ID indicated in the container use information 713 in the schedule table is referred to as the designated container QQ. It is assumed that the designated container QQ is present at the first base 610 before the start of the relay transportation.

[0161] The driver of the vehicle PP[1] loads the target cargo into the designated container QQ at the first base 610. Therefore, the designated container QQ becomes the target container QQ.

[0162] In the second embodiment, a container ID matching confirmation process is executed in step S217 of FIG. 14. The contents of this process are the same as those of step S317 of FIG. 15. That is, in the container ID matching confirmation process in step S217, the management unit 114 judges whether or not the container ID indicated in the container information 1310 matches the container ID indicated in the used container information 713 (see FIG. 8) (the container ID of the designated container QQ in the second embodiment). If the container IDs match (Y in step S218), the management unit 114 transmits a predetermined normal signal 1312 to the terminal device 2 [1] to cause a transition to step S219. If the container IDs do not match (N in step S218), the management unit 114 causes a transition to step S242 and executes a predetermined error process in step S242.

[0163] <<Third Example>> A third embodiment will be described. The departure permission condition may not include the vehicle matching condition. In this case, steps S219 to S221 and S243 are deleted from the flowchart of FIG. 14, and steps S319 to S321 and S343 are deleted from the flowchart of FIG. 15. That is, in the flowchart of FIG. 14, when the normal signal 1312 is transmitted to the terminal device 2 [1] via steps S217 to S218, the process may directly proceed to step S222 instead of proceeding to step S219. Similarly, in the flowchart of FIG. 15, when the normal signal 1412 is transmitted to the terminal device 2 [2] via steps S317 to S318, the process may directly proceed to step S322 instead of proceeding to step S319.

[0164] <<Fourth Example>> A fourth embodiment will be described. When the system state transitions from a state other than the departure permission state to the departure permission state at any of the first base 610 and the relay bases 620 to 640, the management unit 114 may transmit a predetermined departure permission signal to an on-board device (not shown) mounted on the corresponding vehicle PP. In this case, the on-board device that receives the departure permission signal displays a departure permission image based on the departure permission signal on a display device provided in or connected to the on-board device. It is assumed that measures have been taken in advance to establish a wireless communication channel between the on-board device of each vehicle used in the relay transportation and the transportation management device 1.

[0165] That is, for example, when the system state at the first base 610 transitions from the pre-departure state ST10 to the departure permission state ST11, the management unit 114 transmits a predetermined first departure permission signal to the first on-board device (not shown) mounted on the vehicle PP [1]. The first on-board device that receives the first departure permission signal displays a first departure permission image based on the first departure permission signal on a display device (not shown) provided in or connected to the first on-board device. The first departure permission image is an image indicating that permission has been given for the vehicle PP [1] to depart from the first base 610 with the target container QQ connected, and includes a message indicating that the departure has been permitted. Note that in the management unit 114, the first on-board device and the vehicle ID in the information 717 (see FIG. 8) are associated with each other, and the management unit 114 transmits the first departure permission signal to the first on-board device based on the vehicle ID in the information 717.

[0166] Similarly, for example, when the system state transitions from the arrival state ST23 to the departure permission state ST24 at the relay point 620, the management unit 114 transmits a predetermined second departure permission signal to the second on-board device (not shown) mounted on the vehicle PP [2]. The second on-board device that receives the second departure permission signal displays a second departure permission image based on the second departure permission signal on a display device (not shown) provided in or connected to the second on-board device. The second departure permission image is an image indicating that permission has been given for the vehicle PP [2] to depart from the relay point 620 with the target container QQ connected, and includes a message indicating that the departure has been permitted. Note that in the management unit 114, the second on-board device and the vehicle ID in the information 727 (see FIG. 8) are associated with each other, and the management unit 114 transmits the second departure permission signal to the second on-board device based on the vehicle ID in the information 727.

[0167] <<Fifth Example>> A fifth embodiment will be described. An entry / exit gate (not shown) may be provided at each base. At each base, the entry / exit gate is provided between a space inside the base and a space outside the base (including a general roadway), and each vehicle PP passes through the entry / exit gate to move from the former space to the latter space, or from the latter space to the former space. However, this movement is only possible when the entry / exit gate is in an open state. The entry / exit gate is in either a closed state or an open state, and the above movement is prohibited when the entry / exit gate is in a closed state.

[0168] The management unit 114 may have a gate control function for controlling the state of the entrance / exit gates at each base (610 to 650). In this case, when the system state transitions from a state other than the departure permitted state to the departure permitted state at any base among the first base 610 and the relay bases 620 to 640, the management unit 114 may switch the entrance / exit gate at the base from a closed state to an open state to permit the departure of the corresponding vehicle PP.

[0169] That is, for example, when the system state at the first base 610 transitions from the pre-departure state ST10 to the departure ready state ST11, the management unit 114 may switch the entry / exit gate (not shown) of the first base 610 from a closed state to an open state, thereby giving permission for the vehicle PP [1] to depart from the first base 610 with the target container QQ connected. Similarly, for example, when the system state at the relay base 620 transitions from the arrival state ST23 to the departure ready state ST24, the management unit 114 may give permission for the vehicle PP [2] to depart from the relay base 620 with the target container QQ connected, by switching the entry / exit gate (not shown) of the relay base 620 from a closed state to an open state.

[0170] <<Sixth Example>> A sixth embodiment will be described. An example has been given in which three relay points 620, 630, and 640 are passed through on the way from the first base 610 to the second base 650. However, the number of relay points passed through on the way from the first base 610 to the second base 650 in the relay transportation is arbitrary as long as it is one or more. When the number is one, it may be considered that the vehicle PP[2] departing from the relay point 620 carries the target container QQ directly to the second base 650 without passing through the relay points 630 and 640, or that the relay point 630 coincides with the second base 650.

[0171] <<Seventh Example>> A seventh embodiment will now be described.

[0172] In the above-described embodiments, a two-dimensional code such as a QR code (registered trademark) is assumed as the code (AC_CD, QQ_CD, PP_CD) to be read by the terminal device 2. However, the code (AC_CD, QQ_CD, PP_CD) to be read may be a one-dimensional code, or an arbitrary pattern code that is not classified as a one-dimensional code or a two-dimensional code.

[0173] Any device according to the present invention (e.g., the transportation management device 1 or the terminal device 2) is referred to as a target device for convenience. The target device can be configured by hardware such as an integrated circuit, or a combination of hardware and software. Any specific function that is all or part of the functions realized by the target device may be described as a program and the program may be recorded on a recording medium. The specific function may be realized by executing the program on a program execution device (e.g., a microcomputer that can be mounted on the target device). The recording medium may be mounted on or connected to the target device, or may be mounted on or connected to a device (such as a server device) different from the target device. The recording medium is a non-volatile recording medium, and may be configured by, for example, any magnetic disk, optical disk, magneto-optical disk, or semiconductor memory.

[0174] The embodiments of the present invention can be modified in various ways as appropriate within the scope of the technical ideas set forth in the claims. The above embodiments are merely examples of the present invention, and the meanings of the terms of the present invention and each component are not limited to those described in the above embodiments. The specific numerical values ​​shown in the above description are merely examples, and can be changed to various numerical values ​​as a matter of course. [Explanation of symbols]

[0175] SYS Transportation Management System PP Vehicle QQ Container NET Network 1 Transportation management device 11 Control section 12 Storage section 13. Communications Department 14 Interface section 15 Date and time information acquisition section 111 Schedule Data Creation Department 112 Terminal call information acquisition unit 113 Schedule data storage unit 114 Management Department 115 Access Request Reception Department 2 Terminal Equipment 21 Control section 22 Memory section 23 Communications Department 24 Interface section 25 Date and time information acquisition section 26 GPS processing unit 27 Camera Division 700 Schedule Data AC_CD Access Code PP_CD Vehicle Code QQ_CD container code

Claims

1. A transportation management device used for relay transportation of luggage, comprising: A terminal call information acquisition unit; A storage unit for storing schedule data relating to the transportation of the luggage; A management unit that manages a transportation management status related to the transportation of the luggage, In the relay transportation, the luggage is transported from a first base to a second base via one or more relay bases while being accommodated in a storage section using a plurality of target vehicles; The plurality of target vehicles include a first target vehicle that transports the luggage from the first base to a predetermined relay base, and a second target vehicle that transports the luggage from the predetermined relay base to another relay base or the second base, A first terminal device is associated with the first target vehicle, and a second terminal device is associated with the second target vehicle; The schedule data includes: The information includes a first scheduled departure date and time of a first transportation scheduled vehicle that should depart from the first base toward the predetermined relay base with the storage unit arranged, and first scheduled transportation company identification information for identifying a transportation company to which the first transportation scheduled vehicle belongs, and The first transportation scheduled vehicle includes a scheduled arrival date and time at the predetermined relay point, and The information includes a second scheduled departure date and time of a second transportation scheduled vehicle that should depart from the predetermined relay base toward the other relay base or the second base with the storage unit arranged, and second scheduled carrier identification information for identifying a carrier to which the second transportation scheduled vehicle belongs, the terminal transmission information acquisition unit receives first transmission information from the first terminal device and receives second transmission information from the second terminal device; The first transmission information includes location information representing a current location of the first terminal device, first carrier identification information for identifying a carrier to which the first target vehicle belongs, and first storage unit identification information which is identification information of the storage unit acquired by the first terminal device, The second transmission information includes location information representing a current location of the second terminal device, second carrier identification information for identifying a carrier to which the second target vehicle belongs, and second storage unit identification information which is identification information of the storage unit acquired by the second terminal device, The schedule data stores the first storage unit identification information based on the first transmission information, or stores the first storage unit identification information that is specified in advance regardless of the first transmission information, The management unit sets the transportation management state to any one of a plurality of states including a first state, a second state, a third state, a fourth state, a fifth state, and a sixth state, The management unit sets the transportation management state to the first state in an initial state, the management unit has an access request receiving unit that receives an access request from the first terminal device or the second terminal device to a predetermined transportation management website, when the management unit receives the access request from the first terminal device when the transportation management state is the first state, on the premise that the current location of the first terminal device indicated in the first transmission information is a point within the first base, the management unit permits the first terminal device to access the transportation management website on the condition that the first carrier identification information in the first transmission information matches the first scheduled carrier identification information, the magnitude of the difference between the current date and time and the first scheduled departure date and time is within a first predetermined time, and the transportation management state is in the first state, and then transitions the transportation management state from the first state to the second state; After the transition to the second state, access to the transportation management website by the first terminal device is blocked; Thereafter, when the management unit receives the access request from the first terminal device, on the premise that the current location of the first terminal device indicated in the first transmission information is a point within the predetermined relay base, the management unit permits the first terminal device to access the transportation management website on the condition that the first carrier identification information in the first transmission information matches the first scheduled carrier identification information, the magnitude of the difference between the current date and time and the scheduled arrival date and time is within a second predetermined time, and the transportation management status is in the second status, and then transitions the transportation management status from the second status to the third status, and thereafter, upon receiving a first specified signal from the first terminal device, transitions the transportation management status from the third status to the fourth status; Thereafter, when the management unit receives the access request from the second terminal device, on the premise that the current location of the second terminal device indicated in the second transmission information is a point within the predetermined relay base, the management unit permits the second terminal device to access the transportation management website on the condition that the second carrier identification information in the second transmission information matches the second scheduled carrier identification information, the magnitude of the difference between the current date and time and the second scheduled departure date and time is within a third predetermined time, and the transportation management status is in the fourth state, and then transitions the transportation management status from the fourth state to the fifth state, and thereafter, when the second storage unit identification information in the second transmission information matches the first storage unit identification information in the schedule data, upon receiving a second identification signal from the second terminal device, transitions the transportation management status from the fifth state to the sixth state; the second state is a state in which the first target vehicle is permitted to depart from the first base with the storage unit placed, and the sixth state is a state in which the second target vehicle is permitted to depart from the predetermined relay base with the storage unit placed, the terminal transmission information acquisition unit acquires loading information relating to a loading state of the luggage in the storage unit from the first terminal device, The management unit is capable of transmitting the loading information to the second terminal device after permitting the second terminal device to access the transportation management website, The loading information includes a photographed image of the interior of the storage unit. , transportation management equipment.

2. A transportation management device according to claim 1, The first terminal device and the second terminal device , transportation management system.

Images