Route determination device, program and route determination method

Abstract

To provide a route determination device, a program and a route determination method capable of reducing labor required to determine a route that goes around a plurality of points where luggage is to be unloaded.SOLUTION: A route determination device comprises an input unit and a determination unit. The input unit receives input for designating a range on a map. The determination unit identifies, from among a plurality of points at which luggage is to be unloaded during transport of the luggage, points that fall within the range, and determines a route that passes through all of the identified points. The route determination device may further include a grouping unit. The grouping unit groups, from among a plurality of cases for transporting the luggage, a plurality of cases in which points where the luggage is to be unloaded are on the route so that the cases belong to the same group.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a route determination device, a program, and a route determination method. [Background technology]

[0002] For logistics or transportation companies that receive transportation requests from shippers, designing order formats and delivery plans for individual orders, such as those that are specified by product and delivery destination, is a complex task, as it requires designing a single transport vehicle to allocate products to multiple delivery destinations. Furthermore, it is also necessary to determine a route that will travel between locations in a rational manner. However, allocating products to vehicles and determining routes like this is a time-consuming process. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-53922 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the embodiments of the present invention is to provide a route determination device, program, and route determination method that can reduce the effort required to determine a route that travels around multiple locations where luggage is to be dropped off. [Means for solving the problem]

[0005] According to an embodiment, a route determination device includes an input unit and a determination unit. The input unit receives an input specifying an area on a map. The determination unit identifies points within the area among a plurality of points at which luggage is to be dropped off during luggage transportation, and determines a route that passes through all of the identified points. [Brief explanation of the drawings]

[0006] [Figure 1]1 is a block diagram showing an example of a main configuration of a vehicle dispatch system according to an embodiment and components included in the vehicle dispatch system; [Figure 2] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 3] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 4] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 5] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 6] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Figure 7] FIG. 2 is a diagram showing an example of a delivery destination screen displayed on the display device in FIG. 1. [Figure 8] FIG. 2 is a diagram showing an example of a root screen displayed on the display device in FIG. 1. [Figure 9] FIG. 2 is a diagram showing an example of a case screen displayed on the display device in FIG. 1. [Figure 10] FIG. 2 is a diagram showing an example of a details screen displayed on the display device in FIG. 1. [Figure 11] FIG. 2 is a diagram showing an example of a vehicle dispatch screen displayed on the display device in FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0007] Below, a vehicle dispatch system according to an embodiment will be described with reference to the drawings. Note that the scale of each part in each drawing used in the following description of the embodiment may be changed as appropriate. Also, for the sake of explanation, each drawing used in the following description of the embodiment may omit the configuration. Also, in each drawing and in this specification, the same reference numerals indicate similar elements.

[0008] FIG. 1 is a block diagram illustrating an example of a vehicle dispatching system 1 according to an embodiment and a configuration of key components included in the vehicle dispatching system 1. Each component of the device may be built-in or external. The vehicle dispatching system 1 is a system that provides a vehicle dispatching service. Users of the vehicle dispatching system are primarily logistics or transportation companies that transport cargo using trucks and the like. The vehicle dispatching services provided by the vehicle dispatching system 1 include a route service and a grouping service. The route service is a service for determining delivery routes to destinations within a set range. The grouping service is a service for rationally allocating cargo to trucks for delivery, such as by delivery location address or delivery area, based on order information, such as a product-specific and delivery-specific list. The grouping service is a service for determining which cargoes to load together when there is space available in a truck already scheduled for delivery. The vehicle dispatching system 1 includes, for example, a server device 100 and a terminal device 200. The vehicle dispatching system 1 may include some of these.

[0009] The server device 100 and the terminal device 200 are connected to a network NW. The network NW is typically a communication network including the Internet. The network NW is typically a communication network including a WAN (wide area network). The network NW may be a communication network including a private network such as an intranet. The network NW may be a communication network including a LAN (local area network). The network NW may be a wireless line or a wired line, or may be a mixture of wireless and wired lines. The network NW may also be a communication network including a dedicated line or a public mobile phone network.

[0010] The server device 100 is a server that provides a vehicle dispatch service. The server device 100 includes, for example, a processor 110, a read-only memory (ROM) 120, a random-access memory (RAM) 130, an auxiliary storage device 140, and a communication interface 150. A bus 160 and the like connect these components. The server device 100 is an example of a route determination device.

[0011] The processor 110 is the central part of a computer that performs various calculations and processes, such as calculations and controls, necessary for the operation of the server device 100. The processor 110 may be, for example, a central processing unit (CPU), a microprocessing unit (MPU), a system on a chip (SoC), a digital signal processor (DSP), a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field-programmable gate array (FPGA). Alternatively, the processor 110 may be a combination of these. The processor 110 may also be a combination of these with a hardware accelerator or the like. The processor 110 controls each component to realize various functions of the server device 100 based on programs such as firmware, system software, and application software stored in the ROM 120 or the auxiliary storage device 140. The processor 110 also executes the processes described below based on the programs. Note that some or all of the programs may be incorporated into the circuitry of the processor 110.

[0012] The ROM 120 and RAM 130 are the main storage devices of the computer centered around the processor 110. The ROM 120 is a non-volatile memory used exclusively for reading data. The ROM 120 stores, for example, firmware among the above programs. The ROM 120 also stores data used by the processor 110 when it performs various processes.

[0013] The RAM 130 is a memory used for reading and writing data. The RAM 130 is used as a work area for storing data that is temporarily used when the processor 110 performs various processes. The RAM 130 is typically a volatile memory.

[0014] The auxiliary storage device 140 is an auxiliary storage device of a computer with the processor 110 as its central device. The auxiliary storage device 140 is, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), or a flash memory. The auxiliary storage device 140 stores, for example, system software and application software among the above programs. The auxiliary storage device 140 also stores data used by the processor 110 when performing various processes, data generated by the processes in the processor 110, and various setting values. The data stored in the auxiliary storage device 140 includes, for example, a user DB (database) 141.

[0015] The user DB 141 is a database that stores and manages information about users who use the vehicle dispatch service. For example, the user DB 141 stores, for each user, user information, vehicle information, driver information, delivery destination information, route information, project information, group information, and vehicle dispatch information in association with a user ID (identifier). The user ID is identification information that is uniquely assigned to each user.

[0016] User information is information about a user identified by an associated user ID. User information includes information about the user company, such as the company name, company address, information about each business location, and information about the driver who drives the vehicle.

[0017] Vehicle information is information about vehicles such as freight trucks operated by a user identified by an associated user ID. Vehicle information is stored for each freight truck by associating information about the freight truck with the vehicle ID. The vehicle ID is unique identification information for each vehicle. Information about freight trucks includes, for example, the name of the logistics company or transportation company (sign name), the vehicle model and shape, the vehicle number, information that can identify the driver, and contact information.

[0018] Driver information is information about the driver used by a user identified by an associated user ID. For each driver, information about the driver is stored in association with the driver ID. The driver ID is unique identification information for each driver. Driver information includes the driver's name, phone number, planned / actual information, and on-duty time information. Planned / actual information is information about the driver's scheduled work hours and actual working hours. On-duty time information is information indicating the driver's scheduled and actual on-duty time.

[0019] Delivery destination information is information about the delivery destination of a user identified by the associated user ID. A delivery destination is a location where transported goods are delivered. For example, for each delivery destination, delivery destination information is stored in association with the delivery destination ID, the name of the delivery destination, address, telephone number, notes, delivery time slots, conditions such as the height of vehicles usable for delivery, the color to be displayed on the map, and registration information. The delivery destination ID is unique identification information for each delivery destination. Registration information is information indicating whether the delivery destination is registered as a valid delivery destination. A valid delivery destination indicates a delivery destination for which route setting is performed using a map. A delivery destination that is not registered as a valid delivery destination (hereinafter referred to as a "non-valid delivery destination") indicates a delivery destination for which route setting is not performed using a map.

[0020] The route information is information indicating the delivery route along which the user identified by the associated user ID will deliver goods to the delivery destination.

[0021] The case information is information about cases currently handled by a user identified by an associated user ID. In this embodiment, a case refers to a request for transporting a package to a logistics company or a transportation company. The case information stores information about each case, for example, in association with the case ID.

[0022] Group information is information about groups registered by a user identified by an associated user ID. Cases that a user is working on can belong to a group. For example, group information stores information about each group in association with a group ID. Details about groups will be provided later.

[0023] The dispatch information is information about dispatches for cases currently handled by a user identified by an associated user ID and for groups registered by that user. The dispatch information associates a case ID or group ID with a vehicle ID and a driver ID. As a result, the dispatch information indicates that a vehicle identified by the vehicle ID and a driver identified by the driver ID have been assigned to a case or group identified by the case ID or group ID.

[0024] The communication interface 150 is an interface for the server device 100 to communicate via a network NW or the like.

[0025] The bus 160 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged among the various components of the server device 100 .

[0026] The terminal device 200 is a device for using a vehicle dispatch service. The terminal device 200 is, for example, a general-purpose device such as a smartphone, a tablet terminal, or a PC (personal computer). Alternatively, the terminal device 200 may be a device dedicated to using a vehicle dispatch service. The terminal device 200 includes, for example, a processor 210, a ROM 202, a RAM 203, an auxiliary storage device 204, a communication interface 205, an input device 206, and a display device 207. A bus 208 and the like connect these components.

[0027] The processor 210 is the central part of a computer that performs various calculations and processes, such as calculations and controls, necessary for the operation of the terminal device 200. The processor 210 is, for example, a CPU, MPU, SoC, DSP, GPU, ASIC, PLD, or FPGA. Alternatively, the processor 210 may be a combination of several of these. The processor 210 may also be a combination of these with a hardware accelerator or the like. The processor 210 controls each component to realize various functions of the terminal device 200 based on programs such as firmware, system software, and application software stored in the ROM 202 or the auxiliary storage device 204. The processor 210 also executes the processes described below based on the programs. Note that some or all of the programs may be incorporated into the circuitry of the processor 210.

[0028] The ROM 202 and RAM 203 are main storage devices of the computer centered around the processor 210. The ROM 202 is a non-volatile memory used exclusively for reading data. The ROM 202 stores, for example, firmware among the above programs. The ROM 202 also stores data used by the processor 210 when performing various processes.

[0029] The RAM 203 is a memory used for reading and writing data. The RAM 203 is used as a work area for storing data that is temporarily used when the processor 210 performs various processes. The RAM 203 is typically a volatile memory.

[0030] The auxiliary storage device 204 is an auxiliary storage device of a computer with the processor 210 as its central device. The auxiliary storage device 204 is, for example, an EEPROM, a HDD, or a flash memory. The auxiliary storage device 204 stores, for example, system software and application software among the above programs. The auxiliary storage device 204 also stores data used by the processor 210 when performing various processes, data generated by the processes in the processor 210, various setting values, and the like.

[0031] The application software stored in the auxiliary storage device 204 includes application software for using a vehicle dispatch service (hereinafter referred to as a "terminal application"). The terminal application may be application software dedicated to the vehicle dispatch service, or general-purpose application software such as a web browser.

[0032] Note that the processor 210 needs to be logged in to the vehicle dispatch service for some or all of the vehicle dispatch service. The terminal device 200 logs in to the vehicle dispatch service using, for example, a user ID. The processor 210 may perform this login automatically, or may perform it based on an operation by the operator of the terminal device 200 (hereinafter simply referred to as the "operator"). When the terminal device 200 is currently logged in to the vehicle dispatch service, it stores the user ID used for logging in. This user ID will be referred to as the "login ID" below. Furthermore, the user identified by this login ID will be referred to as the "login user" below.

[0033] The communication interface 205 is an interface for the terminal device 200 to communicate via a network NW or the like.

[0034] The input device 206 accepts operations by an operator. The input device 206 is, for example, a keyboard, a keypad, a touchpad, a mouse, a controller, etc. The input device 206 may also be a device for voice input.

[0035] The display device 207 displays a screen for notifying an operator or the like of various pieces of information. The display device 207 is, for example, a display such as a liquid crystal display or an organic EL (electro-luminescence) display. A touch panel can also be used as the input device 206 and the display device 207. That is, a display panel included in the touch panel can be used as the display device 207, and a pointing device for touch input included in the touch panel can be used as the input device 206.

[0036] The bus 208 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged between the various components of the terminal device 200 .

[0037] The operation of the vehicle dispatch system 1 according to the embodiment will be described below with reference to Figures 2 to 6. Note that the processing content in the following operation description is an example, and various processing that can achieve similar results can be used as appropriate. Figures 2 to 5 are flowcharts showing an example of processing by the processor 210 of the terminal device 200. The processor 210 executes the processing of Figures 2 to 5 based on a program stored in, for example, the ROM 202 or the auxiliary storage device 204. Figure 6 is a flowchart showing an example of processing by the processor 110 of the server device 100. The processor 110 executes the processing of Figure 6 based on a program stored in, for example, the ROM 120 or the auxiliary storage device 140. The processor 110 of the server device 100 starts the processing shown in Figure 6, for example, when the server device 100 is started.

[0038] For example, when an operation is performed to instruct display of a delivery destination screen, the processor 210 of the terminal device 200 starts the processing shown in Fig. 2. The delivery destination screen will be described later.

[0039] In step ST11 of FIG. 2, the processor 210 of the terminal device 200 generates a delivery destination request. The delivery destination request includes, as an example, a login ID. The delivery destination request is information requesting the transmission of information indicating the delivery destination of the user identified by the login ID. After generating the delivery destination request, the processor 210 instructs the communication interface 205 to transmit the delivery destination request to the server device 100. Upon receiving this transmission instruction, the communication interface 205 transmits the delivery destination request to the server device 100. The transmitted delivery destination request is received by the communication interface 150 of the server device 100.

[0040] 6, the processor 110 of the server device 100 determines whether or not a delivery destination request has been received by the communication interface 150. If a delivery destination request has not been received, the processor 110 determines No in step ST61 and proceeds to step ST62.

[0041] In step ST62, processor 110 determines whether or not a delivery destination change request has been received by communication interface 150. If a delivery destination change request has not been received, processor 110 determines No in step ST62 and proceeds to step ST63.

[0042] In step ST63, the processor 110 determines whether or not a route request has been received by the communication interface 150. If a route request has not been received, the processor 110 determines No in step ST63 and proceeds to step ST64.

[0043] In step ST64, the processor 110 determines whether or not a route change request has been received by the communication interface 150. If a route change request has not been received, the processor 110 determines No in step ST64 and proceeds to step ST65.

[0044] In step ST65, the processor 110 determines whether or not an object request has been received by the communication interface 150. If an object request has not been received, the processor 110 determines No in step ST65 and proceeds to step ST66.

[0045] In step ST66, the processor 110 determines whether or not a registration request has been received by the communication interface 150. If a registration request has not been received, the processor 110 determines No in step ST66 and proceeds to step ST67.

[0046] In step ST67, processor 110 determines whether or not a vehicle dispatch request has been received by communication interface 150. If processor 110 determines that a vehicle dispatch request has not been received, it determines No in step ST67 and proceeds to step ST68.

[0047] In step ST68, processor 110 determines whether or not a vehicle allocation change request has been received by communication interface 150. If processor 110 determines that a vehicle allocation change request has not been received, it determines No in step ST68 and returns to step ST61. Thus, processor 110 enters a standby state in which it repeats steps ST61 to ST68 until a delivery destination request, delivery destination change request, route request, route change request, case request, registration request, vehicle allocation request, or vehicle allocation change request is received.

[0048] If a delivery destination request is received while processor 110 is in a standby state where steps ST61 to ST68 are repeated, processor 110 determines "Yes" in step ST61 and proceeds to step ST69.

[0049] In step ST69, the processor 110 refers to the user DB 141 to acquire delivery destination information associated with the user ID. The user ID is the user ID included in the delivery destination request received in step ST61.

[0050] In step ST70, the processor 110 instructs the communication interface 150 to transmit the delivery destination information acquired in step ST69 to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the delivery destination information to the terminal device 200. The transmitted delivery destination information is received by the communication interface 205 of the terminal device 200. After processing step ST70, the processor 110 returns to step ST61.

[0051] 2, the processor 210 of the terminal device 200 waits for the delivery destination information to be received by the communication interface 205. If the delivery destination information is received, the processor 210 determines Yes in step ST12 and proceeds to step ST13.

[0052] In step ST13, the processor 210 generates an image corresponding to the delivery destination screen SC1 as shown in Fig. 7. Then, the processor 210 instructs the display device 270 to display the generated image. Upon receiving the display instruction, the display device 270 displays the delivery destination screen SC1.

[0053] 7 is a diagram showing an example of a delivery destination screen SC1 displayed on the display device 270. The delivery destination screen SC1 includes, as an example, an area AR11, an area AR12, a new registration button B11, an import button B12, a registration button B13, a deregistration button B14, a delete button B15, and a save button B16.

[0054] Areas AR11 and AR12 are areas that display a list of information about delivery destinations registered as delivery destinations for the logged-in user. Areas AR11 and AR12 display the information about delivery destinations in the form of a table, for example, as shown in FIG. 7. Note that areas AR11 and AR12 shown in FIG. 7 are partially omitted. Areas AR11 and AR12 can be changed for each item of each delivery destination.

[0055] Area AR11 is an area that displays a list of information about inactive delivery destinations. Area AR11 allows the operator to select an inactive delivery destination that they wish to change to an active delivery destination. Area AR11 also allows the operator to select an inactive delivery destination that they wish to delete from the delivery destination information. Area AR11 displays information for each item about each inactive delivery destination, for example. These items include, for example, the name, address, telephone number, notes, the opening and closing times of the delivery window as the time slot during which delivery is possible, the height limit for vehicles that can be used for delivery, and the color to be displayed on the map.

[0056] Area AR12 is an area that displays a list of information about valid delivery destinations. Area AR12 allows the operator to select a valid delivery destination that they wish to change to an inactive delivery destination. Area AR12 also allows the operator to select a valid delivery destination that they wish to delete from the delivery destination information. Area AR12 displays information for each item for each valid delivery destination. These items include, for example, the name of the delivery destination, the details indicated by the route information, optional settings, address, telephone number, notes, the opening and closing times for the delivery period, the height limit for vehicles that can be used for delivery, and the color to be displayed on the map. The optional settings will be described later.

[0057] The new registration button B11 is a button that the operator operates when registering a new delivery destination for the logged-in user. When the new registration button B11 is operated, the processor 210 displays a screen for inputting information necessary for newly registering a delivery destination. The operator inputs the information on the screen. Based on the information input on the screen, the processor 210 adds the delivery destination to the area AR11 as a newly registered delivery destination.

[0058] The import button B12 is a button that the operator operates when registering a new delivery destination for the logged-in user using the contents of a file. The processor 210 displays a screen for specifying the file. The processor 210 adds the newly registered delivery destination to the area AR11 based on the contents of the file specified on the screen. The file can contain information on multiple delivery destinations. Therefore, the processor 210 can register multiple new delivery destinations by importing from the file. One example of the file is a CSV (comma-separated values) file.

[0059] The register button B13 is a button that the operator operates when changing a selected non-valid delivery destination to a valid delivery destination. When the register button B13 is operated, the processor 210 moves the selected non-valid delivery destination from the area AR11 to the area AR12. In other words, the processor 210 deletes the selected non-valid delivery destination from the area AR11 and displays it in the area AR12.

[0060] The Cancel Registration button B14 is a button that the operator operates when changing the selected valid delivery destination to a non-valid delivery destination. When the Cancel Registration button B14 is operated, the processor 210 moves the selected valid delivery destination from area AR12 to area AR11. In other words, the processor 210 deletes the selected valid delivery destination from area AR12 and displays it in area AR11.

[0061] The Delete button B15 is a button that the operator operates when deleting a selected delivery destination from the delivery destinations of the logged-in user. When the Delete button B15 is operated, the processor 210 deletes the selected delivery destination from the areas AR11 and AR12.

[0062] The save button B16 is a button that the operator operates when instructing the dispatch system 1 to save changes to the delivery destination information based on operations performed on the delivery destination screen SC1. Here, changes to the delivery destination information include, for example, changing the contents of each item in areas AR11 and AR12, registering a new delivery destination, changing from an inactive delivery destination to an active delivery destination, changing from an active delivery destination to an inactive delivery destination, and deleting a delivery destination.

[0063] 2, processor 210 of terminal device 200 waits for an operation to instruct saving the changes to the delivery destination information. That is, processor 210 waits for a predetermined operation, such as operating save button B16. If an operation to instruct saving the changes to the delivery destination information is performed, processor 210 determines Yes in step ST14 and proceeds to step ST15.

[0064] In step ST15, the processor 210 generates a delivery destination change request. The delivery destination change request includes a login ID and change information. The delivery destination change request is information that instructs the delivery destination information associated with the login ID to be changed according to the change content indicated in the change information. The change information is information indicating the change content of the delivery destination information. Examples of change information include item change information, new registration information, registration change information, and deletion information. The item change information is information indicating the change content of each item changed in areas AR11 and AR12. The new registration information is information on each delivery destination that will be newly registered as a delivery destination for the logged-in user. The registration change information is information indicating which delivery destinations have been changed from non-valid delivery destinations to valid delivery destinations, and which delivery destinations have been changed from valid delivery destinations to non-valid delivery destinations. The deletion information is information indicating which delivery destinations will be deleted. After generating the delivery destination change request, the processor 210 instructs the communication interface 205 to send the delivery destination change request to the server device 100. Upon receiving this instruction to send, the communication interface 205 sends the delivery destination change request to the server device 100. The sent delivery destination change request is received by the communication interface 150 of the server device 100. After processing step ST15, the processor 210 returns to step ST14.

[0065] On the other hand, if a delivery destination change request is received while processor 110 of server device 100 is in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, processor 110 determines "Yes" in step ST62 and proceeds to step ST71.

[0066] In step ST71, the processor 110 changes the delivery destination information based on the change information included in the delivery destination change request received in step ST62. The delivery destination information is the delivery destination information stored in the user DB 141 in association with the user ID included in the delivery destination change request. If there is a delivery destination to be newly registered based on the new registration information included in the change information, the processor 110 adds the delivery destination to the delivery destination information. The processor 110 changes the information of each delivery destination in the delivery destination information based on the item information included in the change information. The processor 110 changes the registration information of each delivery destination based on the registration change information included in the change information. The processor 110 deletes the delivery destination indicated by the deletion information included in the change information from the delivery destination information. After processing step ST71, the processor 110 returns to step ST61.

[0067] For example, when an operation is performed to instruct display of a root screen, the processor 210 of the terminal device 200 starts the processing shown in Fig. 3. The root screen will be described later.

[0068] In step ST21 of FIG. 3, the processor 210 of the terminal device 200 generates a route request. The route request includes, as an example, a login ID. The route request is information requesting the transmission of information indicating the delivery route along which the user identified by the login ID will make delivery. After generating the route request, the processor 210 instructs the communication interface 205 to transmit the route request to the server device 100. Upon receiving this transmission instruction, the communication interface 205 transmits the route request to the server device 100. The transmitted route request is received by the communication interface 150 of the server device 100.

[0069] On the other hand, if a route request is received while processor 110 of server device 100 is in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, processor 110 determines "Yes" in step ST63 and proceeds to step ST72.

[0070] In step ST72, the processor 110 refers to the user DB 141 to acquire route information associated with the user ID. The user ID is the user ID included in the delivery destination request received in step ST63.

[0071] In step ST73, the processor 110 instructs the communication interface 150 to transmit the route information acquired in step ST72 to the terminal device 200. In response to this transmission instruction, the communication interface 150 transmits the route information to the terminal device 200. The transmitted route information is received by the communication interface 205 of the terminal device 200. After processing step ST73, the processor 110 returns to step ST61.

[0072] 3, the processor 210 of the terminal device 200 waits for the route information to be received by the communication interface 205. If the route information is received, the processor 210 determines Yes in step ST22 and proceeds to step ST23.

[0073] In step ST23, the processor 210 generates an image corresponding to the root screen SC2 as shown in Fig. 8. Then, the processor 210 instructs the display device 270 to display this generated image. Upon receiving the display instruction, the display device 270 displays the root screen SC2.

[0074] 8 is a diagram showing an example of the root screen SC2 displayed on the display device 270. The root screen SC2 includes, as an example, areas AR21 to AR23.

[0075] Area AR21 is an area that displays a list of delivery destinations included in each delivery route. Area AR21 displays the delivery destinations for each delivery route so that the order in which the delivery destinations will be visited can be seen. Note that area AR21 shown in Figure 8 is partially omitted.

[0076] Area AR22 is an area where a map is displayed. It is preferable that the display range of the map can be changed. Processor 210 changes the display range of the map based on an operation by the operator. Area AR22 includes zero or more areas AR23.

[0077] The area AR23 indicates a delivery area. The delivery area is used to determine a delivery route. The operator can arbitrarily set the delivery area on the map. The operator can also arbitrarily change the delivery area. The shape of the delivery area is, for example, a rectangle, a polygon, or another shape surrounded by a closed curve. The shapes that can be set as a delivery area may be limited to specific shapes such as a rectangle. The processor 210 adds the area AR23 to a range specified by an operation by the operator. The area AR23 can also be deleted. The processor 210 deletes the area AR23 specified by an operation by the operator. One delivery route corresponds to one delivery area. Figure 8 shows five areas AR23 as an example. The five areas AR23 correspond to five delivery routes, routes R1 to R5, respectively. Note that a delivery route may be shown on the map for each area AR23.

[0078] In step ST24, the processor 210 determines whether to change the delivery route. The processor 210 determines to change the delivery route when, for example, the delivery area is changed. A change in the delivery area means that a new delivery area is set, the scope of the delivery area is changed, or a delivery area is deleted. If the processor 210 does not determine to change the delivery route, it determines No in step ST24 and repeats the processing of step ST24. On the other hand, if the processor 210 determines to change the delivery route, it determines Yes in step ST24 and proceeds to step ST25.

[0079] In step ST25, the processor 210 generates a route change request. The route change request is information requesting a change to the delivery route. The route change request includes, as an example, a login ID and area change information. The area change information is information indicating the details of the change to the delivery area made on the route screen SC2. After generating the route change request, the processor 210 instructs the communication interface 205 to send the route change request to the server device 100. Upon receiving this instruction to send, the communication interface 205 sends the route change request to the server device 100. The sent route change request is received by the communication interface 150 of the server device 100.

[0080] On the other hand, if a route change request is received while processor 110 of server device 100 is in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, processor 110 determines "Yes" in step ST64 and proceeds to step ST74.

[0081] The route change request includes information specifying an area on the map. Therefore, the processor 110, in cooperation with the communication interface 150, receives the route change request and functions as an example of an input unit that receives input specifying an area on the map.

[0082] In step ST74, processor 110 determines a delivery route based on the area change information received in step ST25. Processor 110 determines a delivery route for the newly set delivery area and the area whose range has been changed. Processor 110 determines a delivery route, for example, by performing the following processes (A1) to (A2) for each of the target delivery areas for which a delivery route is to be determined (hereinafter referred to as "target delivery areas").

[0083] (A1) Processor 110 identifies delivery destinations within the target delivery area. To do this, processor 110 references user DB 141 to obtain delivery destination information associated with the login ID included in the area change information received in step ST25. Processor 110 then identifies, from among the delivery destinations included in the delivery destination information, delivery destinations whose registration information indicates a valid delivery destination and whose addresses are within the target delivery area. The delivery destinations identified here are delivery destinations within the target delivery area.

[0084] (A2) The processor 110 determines a delivery route for delivering goods to delivery destinations within the delivery area using, for example, a predetermined algorithm. The algorithm is, for example, an algorithm for finding the shortest route. The algorithm may be, for example, an algorithm for solving the traveling salesman problem. This solution may be an exact solution or an approximate solution. Note that the starting point and the finishing point of this traveling salesman problem may be different. For example, the processor 110 sets one arbitrary delivery destination as the starting point and the finishing point. For example, the processor 110 sets two arbitrary delivery destinations as the starting point and the finishing point. Alternatively, the processor 110 sets a point preset by the user as the starting point and one arbitrary delivery destination as the finishing point. Alternatively, the processor 110 sets one arbitrary delivery destination as the starting point and a point preset by the user as the finishing point. Alternatively, the processor 110 sets two points preset by the user as the starting point and the finishing point. Alternatively, the processor 110 may set a location preset by the user as the start and finish points. The location preset by the user may be, for example, the address of the location where the delivery vehicle is parked or the address of an office managed by the user. The location preset by the user may be within or outside the target delivery area. The delivery route may pass only within the target area, or may pass outside the target area. Each delivery destination may have a set time slot during which deliveries are possible. In this case, the processor 110 calculates a route that arrives at each delivery destination during a set time slot during which deliveries are possible. The processor 110 may use a predetermined time as the start time of delivery. Alternatively, the processor 110 may calculate an optimal start time. A length of time required for delivery may be set for each delivery destination. In this case, the processor 110 calculates a route assuming that the delivery destination will be visited for that time.

[0085] (A3) Processor 110 stores the area range indicated by the area change information received in step ST25 and the delivery route determined in (A2) in the route information associated with the user ID. The user ID is the login ID included in the area change information received in step ST25.

[0086] Furthermore, for the deleted delivery area, processor 110 deletes the corresponding delivery route from the route information associated with the user ID. The user ID is the login ID included in the area change information received in step ST25.

[0087] As described above, by processing step ST74, processor 110 functions as an example of a determination unit that identifies points within a range among multiple points at which cargo is unloaded during cargo transportation, and determines a route that passes through all of the identified points.

[0088] In step ST75, the processor 110 generates route change information. The route change information is information indicating that the delivery route has been changed. The route change information is information notifying the changed delivery route. The route change information includes, for example, delivery destination information associated with a user ID. The user ID is the login ID included in the area change information received in step ST25. After generating the route change information, the processor 110 instructs the communication interface 150 to transmit the route change information to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the route change information to the terminal device 200. The transmitted route change information is received by the communication interface 205 of the terminal device 200. After processing step ST75, the processor 110 returns to step ST61.

[0089] 3, the processor 210 of the terminal device 200 waits for route change information to be received by the communication interface 205. If the route change information is received, the processor 210 determines "Yes" in step ST26 and proceeds to step ST27.

[0090] In step ST27, the processor 210 updates the display content of the route screen SC2 based on the route change information received in step ST26. This update includes updating the content displayed in area AR21 to the content indicated by the route change information. After processing step ST27, the processor 210 returns to step ST24.

[0091] For example, when an operation is performed to instruct display of a case screen, the processor 210 of the terminal device 200 starts the processing shown in Fig. 3. The case screen will be described later.

[0092] In step ST31 of FIG. 3, the processor 210 of the terminal device 200 generates a case request. The case request includes, as an example, a login ID. The case request is information requesting the transmission of information necessary for displaying a case screen. The information necessary for displaying the case screen includes, for example, a list of cases currently being handled by the user identified by the login ID and information about each case. After generating the case request, the processor 210 instructs the communication interface 205 to transmit the case request to the server device 100. Upon receiving this transmission instruction, the communication interface 205 transmits the case request to the server device 100. The transmitted case request is received by the communication interface 150 of the server device 100.

[0093] On the other hand, if the processor 110 of the server device 100 receives an item request while in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, the processor 110 determines "Yes" in step ST65 and proceeds to step ST76.

[0094] In step ST76, the processor 110 refers to the user DB 141 to acquire the case information associated with the user ID. The user ID is the user ID included in the case request received in step ST65.

[0095] In step ST77, the processor 110 generates case screen information. The case screen information includes information necessary for displaying the case screen. This information includes the case information acquired in step ST76. After generating the case screen information, the processor 110 instructs the communication interface 150 to transmit the case screen information to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the case screen information to the terminal device 200. The transmitted case screen information is received by the communication interface 205 of the terminal device 200. After processing step ST77, the processor 110 returns to step ST61.

[0096] 3, the processor 210 of the terminal device 200 waits for the receipt of item screen information via the communication interface 205. If the item screen information is received, the processor 210 determines Yes in step ST32 and proceeds to step ST33.

[0097] In step ST33, the processor 210 generates an image corresponding to the case screen SC3 as shown in Fig. 9. Then, the processor 210 instructs the display device 270 to display this generated image. Upon receiving the display instruction, the display device 270 displays the case screen SC3.

[0098] FIG. 9 is a diagram showing an example of the case screen SC3 displayed on the display device 270. The case screen SC3 is a screen for grouping cases. Case grouping involves dividing cases into groups. Typically, multiple cases belong to one group. However, there may be a group to which only one case belongs. There may also be a group to which no cases belong. It is preferable that one case can only belong to one group. Furthermore, a case does not have to belong to any group. The case screen includes, as an example, areas AR31 to AR34 and a register button B32.

[0099] Area AR31 is an area used when registering a new case. The operator can use area AR31 to register a new case.

[0100] Area AR32 is an area for setting grouping conditions. Area AR31 includes, for example, areas AR321 to AR323 and a grouping button B31.

[0101] Area AR321 is an area for setting the delivery period. Area AR321 includes controls such as an input field for inputting the delivery period. When a delivery period is set, the jobs to be grouped are narrowed down to those whose delivery date falls within the delivery period. When the delivery period is changed, processor 210 displays jobs whose delivery date falls within the delivery period in area AR33. Note that when the delivery period is changed, this also includes when a new delivery period is input.

[0102] Area AR32 may include an area where conditions other than the delivery period can be set to narrow down the jobs. Such an area includes controls for inputting the conditions. When the conditions are set, processor 210 displays jobs that meet the conditions in area AR33. When multiple conditions are set to narrow down the jobs, processor 210 displays jobs that meet all of the conditions in area AR33.

[0103] Area AR322 is an area for setting grouping rules. Area AR322 includes, for example, controls for setting grouping rules. The grouping rules indicate rules for performing grouping. For example, there are four types of grouping rules: delivery destination rules, route rules, area rules, and custom rules. Of these, the delivery destination rules, route rules, and area rules are rules for automatic grouping. The custom rules are rules for manual grouping. The custom rules are designed for cases where grouping cannot be performed using the delivery destination rules, route rules, and area rules described below, as well as irregular cases. By using the custom rules, it is possible to arbitrarily group delivery destinations with distant addresses. Multiple grouping rules can be set in area AR322. Alternatively, area AR322 may be able to set only one grouping rule. As an example, area AR322 in FIG. 9 shows a state in which a delivery destination rule and a route rule are set.

[0104] Area AR323 is an area for setting the type of truck that will deliver the group. The type is indicated by, for example, the vehicle type, size, or load capacity. Area AR323 includes, for example, a control for setting the type of truck. As an example, area AR323 in FIG. 9 shows a state in which a 10-ton truck is set as the type of truck.

[0105] The grouping button B31 is a button that the operator operates when instructing the terminal device 200 to perform grouping under the conditions set in the areas AR321 to AR323.

[0106] Area AR33 is an area that displays a list of cases included in the case information received in step ST32. Area AR33 also displays information about each case. If conditions for narrowing down cases are set in area AR321 or the like, area AR33 displays only cases that meet those conditions. Furthermore, each case displayed in area AR33 can be selected by the operator. Selected cases become targets for grouping.

[0107] Area AR34 displays a list of groups. Area AR34 also displays information about each group. Each group displayed in area AR34 can be selected. A selected group can be registered. Area AR34 also includes a details button B33 for each group.

[0108] The details button B33 is a button that the operator operates when instructing the terminal device 200 to display details of the corresponding group.

[0109] The registration button B32 is a button that the operator operates when instructing the terminal device 200 to register the group selected in the area AR34.

[0110] 3, the processor 210 of the terminal device 200 determines whether or not to perform grouping. For example, the processor 210 determines that grouping should be performed when the grouping button B31 is operated in a state where one or more grouping rules are set in the area AR322, the type of truck is set in the area AR323, and one or more cases are selected in the area AR33. However, when only an optional rule is set in the area AR322, the processor 210 determines that grouping should be performed even if the type of truck is not set in the area AR323. If the processor 210 does not determine that grouping should be performed, the processor 210 determines No in the step ST34 and proceeds to step ST35.

[0111] In step ST35, processor 210 determines whether to display group details. For example, processor 210 determines that group details are to be displayed when detail button B33 is operated. If processor 210 does not determine that group details are to be displayed, it determines No in step ST35 and proceeds to step ST36.

[0112] In step ST36, processor 210 determines whether or not to register a group. For example, when register button B32 is operated with one or more groups selected in area AR34, processor 210 determines that a group is to be registered. If processor 210 does not determine that a group is to be registered, it determines No in step ST36 and returns to step ST34. Thus, processor 210 enters a standby state in which it repeats steps ST34 to ST36 until it determines that grouping is to be performed, that group details are to be displayed, or that a group is to be registered.

[0113] If processor 210 determines to perform grouping during a standby state in which steps ST34 to ST36 are repeated, it determines Yes in step ST34 and proceeds to step ST37.

[0114] In step ST37, the processor 210 performs grouping based on the set grouping rule.

[0115] When multiple grouping rules are set, the processor 210 performs grouping in descending order of priority, for example, according to the grouping rule with the highest priority. In this case, the processor 210 repeatedly performs the following process (B1) by increasing the number of n by 1 from n=1 to n=(the number of set groupings). Note that n is an integer equal to or greater than 1. The priority of the grouping rules is set in advance, for example, by the designer or manager of the vehicle dispatch system 1. It is preferable that the arbitrarily set rules have the lowest priority.

[0116] (B1) Processor 210 performs grouping using the grouping rule with the nth highest priority among the set rules. Here, processor 210 performs grouping on the cases that are the grouping targets. When n=1, the grouping targets are the cases selected in area AR33. Processor 210 removes from the grouping targets any cases that have been determined to belong to any group. Therefore, when n is 2 or greater, the grouping targets are the cases selected in area AR33 excluding those that have been removed from the grouping targets up to that point.

[0117] Alternatively, when multiple grouping rules are set, processor 210 may perform grouping independently for each of the multiple grouping rules. In this case, processor 210, for example, repeatedly performs the following process (B2) by increasing the number of n by 1 from n=1 to n=(the number of set groupings).

[0118] (B2) Processor 210 performs grouping using the grouping rule with the nth highest priority among the set rules. Here, processor 210 performs grouping on the cases that are the grouping targets. The cases that are the grouping targets are the cases selected in area AR33, regardless of the value of n.

[0119] Grouping using each grouping rule will be described below. Note that if multiple groups that satisfy the conditions can be generated, the processor 210 generates multiple groups. Note that when the processor 210 generates a group, it determines the order of each job in the group using a predetermined method. This order will be referred to as the "group order" hereinafter. Note that if a group includes jobs with the same delivery destination, the processor 210 may use the same group order for the jobs with the same delivery destination. The processor 210 may also perform grouping so that the amount of cargo to be loaded onto a truck does not exceed the loadable range for the truck set in area AR323. If the loadable range is exceeded, the processor 210 may divide the group into multiple groups so that the loadable range is not exceeded. Exceeding the loadable range means that at least one of the volume and weight of the cargo exceeds the upper limit.

[0120] Delivery destination rules If there are two or more jobs with the same delivery destination, the processor 210 generates a group to which the jobs belong.

[0121] Route rules If there are two or more jobs with the same delivery destination on the same route, the processor 210 generates a group to which the jobs belong. The route may be a predetermined route, or the processor 210 may determine a new route. A delivery destination being on a route means that the delivery destination faces the route. Alternatively, a delivery destination being on a route means that the delivery destination is within a predetermined distance from the route. Alternatively, a delivery destination being on a route means that the delivery destination faces the route or is reachable from the route within a predetermined time. The predetermined route may be the delivery route determined in step ST74. When the processor 210 uses the delivery route as the predetermined route, the processor 210 may consider delivery destinations included in the delivery route as delivery destinations on the route. The processor 210 determines the order of passing through the route as the order of the jobs in the group.

[0122] Area rules When there are two or more jobs whose delivery destinations are in the same area, the processor 210 generates a group to which the jobs belong. The area may be a predetermined area, or the processor 210 may define a new area. The predetermined area may be a delivery area set on the route screen SC2.

[0123] - Arbitrary setting rules The processor 210 generates a group to which all of the cases to be grouped belong.

[0124] The processing of step ST37 may be performed by the processor 110 of the server device 100. By performing the processing of step ST37 using a route rule that uses the delivery route determined in step ST74, the processor 110 functions as an example of a grouping unit that groups, among multiple cases of transporting luggage, multiple cases whose unloading points are on the delivery route so that they belong to the same group.

[0125] Furthermore, by performing the process of step ST37, processor 110 functions as an example of a generating unit that generates a group to which a plurality of cases for transporting cargo belong.

[0126] In step ST38, the processor 210 adds the group generated in step ST37 to the area AR34. After processing step ST38, the processor 210 returns to step ST34.

[0127] If processor 210 determines that the group details are to be displayed while in a standby state in which steps ST34 to ST36 are repeated, it determines Yes in step ST35 and proceeds to step ST39.

[0128] In step ST39, the processor 210 generates an image corresponding to the details screen SC4 as shown in Fig. 10. Then, the processor 210 instructs the display device 270 to display this generated image. In response to the display instruction, the display device 270 displays the details screen SC4. When the processor 210 has finished displaying the details screen SC4, it ends the processing of step ST39 and returns to step ST34.

[0129] 10 is a diagram showing an example of a details screen SC4 displayed on the display device 270. The details screen SC4 is a screen that displays details of the group corresponding to the operated details button B33. The details screen SC4 includes, as an example, an area AR41 and an area AR42.

[0130] Area AR41 is an area that displays details of a group. Area AR41 displays the cases included in the group in group order. The group order of the cases displayed in area AR41 can be changed by operation by the operator. Furthermore, each case displayed in area AR41 can be selected by operation by the operator.

[0131] Area AR42 is an area that displays details of the case selected in area AR41. Area AR42 displays, for example, a list of products to be delivered in the case and details of each of the products.

[0132] If processor 210 determines to register a group while in a standby state in which steps ST34 to ST36 are repeated, it determines Yes in step ST36 and proceeds to step ST40. However, processor 210 does not have to determine to register if the same case is included in multiple groups among the groups selected in area AR34.

[0133] In step ST40, the processor 210 generates a registration request. The registration request includes, for example, a login ID and group registration information. The group registration information indicates, for each group selected in area AR34, which cases are included and the group order of each case. The registration request is information requesting that each group be registered. After generating the registration request, the processor 210 instructs the communication interface 250 to transmit the registration request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the registration request to the server device 100. The transmitted registration request is received by the communication interface 150 of the server device 100. After processing step ST40, the processor 210 returns to step ST34.

[0134] On the other hand, if processor 110 of server device 100 receives a registration request while in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, it determines "Yes" in step ST66 and proceeds to step ST78.

[0135] In step ST78, the processor 110 registers a group based on the registration request received in step ST68. That is, the processor 110 updates the group information associated with the user ID included in the registration request based on the group registration information included in the registration request information. Note that, as an example, the group information stores, for each group, the case IDs of the cases to which the group belongs and the group order of each case. After processing step ST78, the processor 110 returns to step ST61.

[0136] For example, when an operation is performed to instruct display of a vehicle dispatch screen, the processor 210 of the terminal device 200 starts the processing shown in Fig. 5. The vehicle dispatch screen will be described later.

[0137] Meanwhile, in step ST51 of FIG. 3, the processor 210 of the terminal device 200 generates a vehicle dispatch request. The vehicle dispatch request includes, as an example, a login ID. The vehicle dispatch request is information requesting the transmission of information necessary for displaying a vehicle dispatch screen. The information necessary for displaying the vehicle dispatch screen includes, for example, a list of cases currently being handled by the user identified by the login ID and information about each case. The information necessary for displaying the vehicle dispatch screen also includes a list of groups registered by the user and information about each group. After generating the vehicle dispatch request, the processor 210 instructs the communication interface 250 to transmit the vehicle dispatch request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the vehicle dispatch request to the server device 100. The transmitted vehicle dispatch request is received by the communication interface 150 of the server device 100.

[0138] On the other hand, if a vehicle dispatch request is received while processor 110 of server device 100 is in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, processor 110 determines "Yes" in step ST67 and proceeds to step ST79.

[0139] In step ST79, the processor 110 refers to the user DB 141 to acquire the vehicle information, driver information, case information, group information, and dispatch information associated with the user ID. The user ID is the user ID included in the dispatch request received in step ST67.

[0140] In step ST80, the processor 110 generates vehicle dispatch screen information. The vehicle dispatch screen information includes information necessary for displaying the vehicle dispatch screen. This information includes, for example, the vehicle information, driver information, job information, group information, and vehicle dispatch information acquired in step ST79. After generating the vehicle dispatch screen information, the processor 110 instructs the communication interface 150 to transmit the vehicle dispatch screen information to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the vehicle dispatch screen information to the terminal device 200. The transmitted vehicle dispatch screen information is received by the communication interface 250 of the terminal device 200. After processing step ST80, the processor 110 returns to step ST61.

[0141] 3, the processor 210 of the terminal device 200 waits for vehicle allocation screen information to be received by the communication interface 250. If the vehicle allocation screen information is received, the processor 210 determines "Yes" in step ST52 and proceeds to step ST53.

[0142] In step ST53, the processor 210 generates an image corresponding to the vehicle allocation screen SC5 as shown in Fig. 11 based on the vehicle allocation screen information received in step ST52. Then, the processor 210 instructs the display device 270 to display the generated image. Upon receiving the display instruction, the display device 270 displays the vehicle allocation screen SC5.

[0143] FIG. 11 is a diagram showing an example of the vehicle allocation screen SC5 displayed on the display device 270. The vehicle allocation screen SC5 is a screen on which vehicles can be allocated for cases and groups. That is, the vehicle allocation screen SC5 is a screen on which trucks and drivers who will transport for a case or group can be assigned to the case and group. The trucks and drivers assigned to a group and transporting for that group transport all of the cases included in that group. The trucks transport a mixture of cargo for each case included in the group. The vehicle allocation screen SC5 includes, as an example, areas AR51 to AR53 and a confirmation button B51.

[0144] Area AR51 is an area that displays a list of cases and groups. The cases and groups displayed in area AR51 are the cases and groups included in the case information and group information received in step ST52. However, it is preferable that the cases displayed in area AR51 are only cases that do not belong to any group. This is to prevent duplicate vehicle dispatches for the same case.

[0145] Each of the jobs and groups displayed in area AR51 can be selected by the operator. The job or group selected in area AR51 will be referred to as the "selected target" hereinafter. The selected target will be the target for dispatch. For each job and group, area AR51 displays the planned period for that job or group using a band. Area AR51 displays information about that job or group within that band. This information is, for example, the weight of the cargo to be transported and the location of the initial loading point and the final unloading point.

[0146] Area AR52 is an area that displays a list of freight trucks. The freight trucks displayed in area AR52 are freight trucks included in the vehicle information received in step ST52. Each freight truck displayed in area AR52 can be selected by the operator. For each freight truck, area AR52 displays the scheduled period of transportation for that freight truck using a band. Area AR52 displays information about the transportation within the band. This information includes, for example, the weight of the cargo to be transported, the location of the initial loading point, and the location of the final unloading point. Processor 210 displays this band based on the dispatch information received in step ST52.

[0147] Each freight vehicle displayed in the area AR52 can be selected by the operator. The selected freight vehicle becomes a target for dispatch. In other words, the freight vehicle selected in the area AR52 is assigned to the selected object and transports the selected object.

[0148] Area AR53 is an area that displays a list of drivers. The drivers displayed in area AR53 are the drivers included in the driver information received in step ST52. Each driver displayed in area AR53 can be selected by the operator. For each driver, area AR53 displays the scheduled period for the driver to transport using a band. Area AR53 displays information about the transport within the band. This information includes, for example, the weight of the cargo to be transported, the location of the initial loading point, and the location of the final unloading point. Processor 210 displays this band based on the dispatch information received in step ST52.

[0149] The Confirm button B51 is a button that can be operated when a case or group is selected in the area AR51, a freight vehicle is selected in the area AR52, and a driver is selected in the area AR53. The Confirm button B51 is a button that the operator operates when instructing the terminal device 200 to dispatch a vehicle for the combination of the selected object, the freight vehicle, and the driver.

[0150] In step ST54, processor 210 determines whether or not a case has been selected in area AR51. If a case has not been selected in area AR51, processor 210 determines No in step ST54 and proceeds to step ST55.

[0151] In step ST55, processor 210 determines whether or not the Confirm button B51 has been operated. If the Confirm button B51 has not been operated, processor 210 determines No in step ST55 and returns to step ST54. Thus, processor 210 enters a standby state in which it repeats steps ST54 and ST55 until a case is selected in area AR51 or the Confirm button B51 is operated.

[0152] If an item is selected in area AR51 while processor 210 is in a standby state in which steps ST54 and ST55 are repeated, processor 210 determines "Yes" in step ST54 and proceeds to step ST56.

[0153] In step ST56, the processor 210 searches for a suitable truck to be selected. For example, the processor 210 determines that a truck that satisfies the weight and geographical conditions shown below is a suitable truck to be selected.

[0154] The weight condition is that the loadable weight of the truck must be equal to or less than the weight of the cargo to be transported by the selected object.

[0155] The geographical condition is that the departure point of the truck for the selected transport must be within a predetermined distance from the loading point. The predetermined distance is, for example, 30 km. The departure point is, for example, the location where the transport of the project or group to be transported before the selected transport ends.

[0156] In step ST57, the processor 210 notifies the operator of the trucks suitable for selection determined in step ST56. The processor 210 performs this notification by, for example, changing the display method of the trucks suitable for selection in the area AR52. The change in the display method may be, for example, surrounding them with a frame, changing the color, changing the font, or displaying a predetermined mark. The processor 210 may also perform this notification by changing the display position of the trucks suitable for selection. For example, the processor 210 displays the trucks suitable for selection in the display order so that they are displayed before other trucks. After processing step ST57, the processor 210 returns to step ST54.

[0157] If the confirm button B51 is operated while in a standby state in which step ST54 and step ST55 are repeated, processor 210 determines Yes in step ST55 and proceeds to step ST58.

[0158] In step ST58, the processor 210 generates a vehicle allocation change request. The vehicle allocation change request includes, for example, a login ID, a case ID or group ID of the selected object, the vehicle ID of the freight truck selected in area AR52, and the driver ID of the driver selected in area AR53. The vehicle allocation change request is information requesting that a vehicle be registered to assign the freight truck and the driver to the selected object. After generating the vehicle allocation change request, the processor 210 instructs the communication interface 250 to transmit the vehicle allocation change request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the vehicle allocation change request to the server device 100. The transmitted vehicle allocation change request is received by the communication interface 150 of the server device 100. After processing step ST58, the processor 210 returns to step ST54.

[0159] On the other hand, if a vehicle allocation change request is received while processor 110 of server device 100 is in a standby state where steps ST61 to ST68 in FIG. 6 are repeated, processor 110 determines "Yes" in step ST68 and proceeds to step ST81.

[0160] In step ST81, the processor 110 updates the dispatch information associated with the user ID included in the dispatch request based on the dispatch change request received in step ST68. That is, the processor 110 associates the case ID or group ID included in the dispatch request with the vehicle ID and the driver ID included in the dispatch request and stores them in the dispatch information. After processing step ST81, the processor 110 returns to step ST61.

[0161] As described above, by performing the process of step ST81, the processor 110 functions as an example of an allocation unit that allocates trucks and drivers to transport cargo for jobs belonging to a group.

[0162] The vehicle dispatch system 1 of the embodiment receives an input specifying a delivery area, which indicates an area on a map. Then, the vehicle dispatch system 1 of the embodiment identifies delivery destinations within the delivery area. Furthermore, the vehicle dispatch system 1 of the embodiment determines a delivery route that travels around the identified delivery destinations. Therefore, the vehicle dispatch system 1 of the embodiment can reduce the effort required to determine a route that travels around multiple drop-off locations. Route determination by the vehicle dispatch system 1 of the embodiment is particularly useful in cases where orders are specified by product and delivery destination, such as individual orders.

[0163] Furthermore, the vehicle dispatch system 1 of the embodiment groups jobs on the determined delivery route so that they belong to the same group, thereby enabling the vehicle dispatch system 1 of the embodiment to generate groups that can carry out transportation efficiently.

[0164] Furthermore, the vehicle dispatch system 1 of the embodiment allocates trucks to multiple jobs that are on the same route and belong to the same group, thereby reducing the effort required for allocating trucks.

[0165] Furthermore, the vehicle dispatch system 1 of the embodiment assigns a driver to multiple jobs that are on the same route and belong to the same group, thereby reducing the effort required for driver assignment.

[0166] Furthermore, the vehicle dispatching system 1 of the embodiment generates a group to which a plurality of jobs for transporting cargo belong. Then, the vehicle dispatching system 1 of the embodiment dispatches vehicles for the group. That is, the vehicle dispatching system 1 of the embodiment assigns freight trucks and drivers to the group. This reduces the effort required for the vehicle dispatching system 1 of the embodiment to determine groups that are combinations of jobs for transporting cargo at one time.

[0167] Furthermore, the vehicle dispatch system 1 of the embodiment performs grouping based on delivery destination rules, which allows the vehicle dispatch system 1 of the embodiment to generate groups that can perform transportation efficiently.

[0168] Furthermore, the vehicle dispatch system 1 of the embodiment performs grouping using an area rule, which allows the vehicle dispatch system 1 of the embodiment to generate groups that can perform transportation efficiently.

[0169] Furthermore, the vehicle dispatch system 1 of the embodiment performs grouping using a route rule, which allows the vehicle dispatch system 1 of the embodiment to generate groups that can perform transportation efficiently.

[0170] The above embodiment can be modified as follows. In the above embodiment, a part or all of the processing performed by the terminal device 200 may be performed by the server device 100. In the above embodiment, a part or all of the processing performed by the server device 100 may be performed by the terminal device 200.

[0171] Each device in the embodiment may be made up of multiple devices.

[0172] The processor 110 and the processor 210 may implement part or all of the processing that is implemented by a program in the above-described embodiments by a hardware circuit configuration.

[0173] A program for implementing the processes of the embodiments may be transferred in a state where it is stored in a non-transitory computer-readable storage medium within the device. However, the device may also be transferred without the program stored therein. The program may then be transferred separately and written to the device. In this case, the program may be transferred by, for example, recording it on a removable non-transitory computer-readable storage medium or by downloading it via a network such as the Internet or a LAN.

[0174] Although the embodiments of the present invention have been described above, they are merely examples and are not intended to limit the scope of the present invention. The embodiments of the present invention can be implemented in various forms without departing from the spirit of the present invention. [Explanation of symbols]

[0175] 1. Vehicle dispatch system 100 Server Devices 110,210 processors 120,220 ROM 130,230 RAM 140,240 Auxiliary storage 141 User DB 150,250 communication interface 160,280 bus 200 Terminal Device 260 Input Devices 270 Display Devices

Claims

1. an input unit for receiving an input specifying a range on the map; A route determination device comprising: a determination unit that identifies points that are included within the range among multiple points at which luggage is to be unloaded during luggage transportation, and determines a route that passes through all of the identified points.

2. 2. The route determination device according to claim 1, further comprising a grouping unit that groups a plurality of cases of transporting luggage such that a plurality of cases having points where the luggage is to be dropped off on the route belong to the same group.

3. 3. The route determination device according to claim 2, further comprising an allocation unit that allocates freight trucks to transport the cargo of the plurality of jobs belonging to the same group.

4. The route determination device according to claim 2 , further comprising an allocation unit that allocates drivers to transport the luggage of the plurality of jobs that belong to the same group.

5. A processor included in the route determination device, an input unit for receiving an input specifying a range on the map; A program that functions as a determination unit that identifies points within the range among multiple points at which cargo is to be unloaded during cargo transportation, and determines a route that passes through all of the identified points.

6. Accepts input specifying the area on the map, A route determination method for determining a route that passes through all of the specified points among a plurality of points at which cargo is to be unloaded during cargo transportation, the points being included within the range.

Images