Route determination method, route determination device, and program

The route determination method addresses inefficiencies in electric vehicle delivery by evaluating logistics quality and power availability, ensuring safe and efficient delivery routes through a software bill of materials assessment.

WO2025220656A1PCT designated stage Publication Date: 2025-10-23PANASONIC INTELLECTUAL PROPERTY MANAGEMENT CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/014737
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-15
Filing Date
2025-04-15
Publication Date
2025-10-23

AI Technical Summary

Technical Problem

Conventional route determination methods for electric vehicles do not account for logistics quality, such as tampered delivery vehicle information and potential power supply shortages, leading to inefficiencies in delivery route planning.

Method used

A route determination method that considers logistics quality by evaluating the reliability and power availability of delivery stations using a software bill of materials (SBOM) to determine a reliable and efficient delivery route for electric vehicles.

Benefits of technology

Ensures safe charging and efficient delivery routes by assessing the reliability and power availability of delivery stations, mitigating risks from tampered information and power supply issues.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025014737_23102025_PF_FP_ABST
    Figure JP2025014737_23102025_PF_FP_ABST
Patent Text Reader

Abstract

A route determination device (11) comprises: a travel request reception unit (110) that receives a travel request including one or more destinations and making a request for an electric vehicle to travel via the one or more destinations; and a route determination unit (117) that determines, for the electric vehicle, a route via the one or more destinations included in the travel request on the basis of physical distribution quality information indicating the level of quality pertaining to the physical distribution in an area to which the one or more destinations included in the travel request belong.
Need to check novelty before this filing date? Find Prior Art

Description

Route determination method, route determination device, and program

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

[0002] In recent years, there has been a shift to electric vehicles due to the high environmental impact of fossil fuel-powered vehicles. Electric vehicles have a shorter driving range than fossil fuel-powered vehicles, so they need to be charged while driving. For example, when determining a route (driving route, e.g., a package delivery route) for commercial electric vehicles that takes into account the charging time or the location of charging points, a technique is known for determining the route by taking into account the amount of power consumed by the electric vehicle.

[0003] International Publication No. 2022 / 018937

[0004] However, conventional technology does not take into account logistics quality, such as the possibility that accurate delivery vehicle information cannot be obtained due to information being tampered with by hacking the delivery station system or delivery vehicles, or the possibility that an increase in electric vehicles may lead to a shortage of power supply and make it impossible to charge EVs at EV charging stations, and there is a risk that it will not be possible to determine an efficient delivery route plan that takes into account the logistics quality in the actual delivery area.

[0005] The present disclosure aims to provide a route determination method, a route determination device, and a program that are capable of creating a route plan that ensures reliable and efficient delivery, taking into account the logistics quality of the area to which the destination included in the delivery request belongs.

[0006] In order to achieve the above object, the route determination method of the present disclosure includes a travel request receiving step of receiving a travel request that includes one or more destinations and requests that an electric vehicle travel via the one or more destinations, and a route determination step of determining a route for the electric vehicle that passes via the one or more destinations included in the travel request based on logistics quality information that indicates the degree of quality of logistics in an area to which the one or more destinations included in the travel request belong.

[0007] According to the present disclosure, it is possible to determine a route that allows safe charging of an electric vehicle. Note that the effects described herein are not necessarily limited to those described herein, and may be any of the effects described in this specification.

[0008] FIG. 1 is a diagram illustrating an example of a schematic configuration of a delivery system according to an embodiment. FIG. 2 is a diagram illustrating an example of the hardware configuration of a delivery management server. FIG. 3 is an explanatory diagram of the configuration of an example of a delivery station system. FIG. 4 is a diagram illustrating an example of functions possessed by the delivery management server. FIG. 5 is an explanatory diagram of a reliability determination table for the delivery station system. FIG. 6 is a diagram illustrating an example of the relationship between the reliability and weight of each of multiple evaluation items constituting an evaluation based on the SBOM according to an embodiment. FIG. 7 is a diagram illustrating an example of a correspondence relationship between a score (evaluation value) indicating an evaluation regarding risk and reliability. FIG. 8 is an explanatory diagram of levels and definitions of the levels. FIG. 9 is an explanatory diagram of a risk score calculation table. FIG. 10 is an explanatory diagram of the SBOM. FIG. 11 is a diagram illustrating an example of a correspondence relationship between a score (evaluation value) indicating an evaluation regarding vulnerability and reliability. FIG. 12 is a diagram illustrating an example of a correspondence relationship between a score (evaluation value) indicating an evaluation regarding a license and reliability. FIG. 13 is an explanatory diagram of a score calculation table for license issues. FIG. 14 is an explanatory diagram of license issue levels. FIG. 15 is a diagram illustrating an example of a correspondence relationship between a drivable distance of an EV vehicle and reliability. FIG. 16 is an explanatory diagram of the correspondence between the reliability of a delivery station system and the reliability rank. FIG. 17 is an explanatory diagram of the power pressure rank. FIG. 18 is an explanatory diagram of the correspondence between the reliability rank of a delivery station system and the power pressure rank, and the logistics quality of a region. FIG. 19 is an explanatory diagram of a specific example of logistics quality in a delivery region. FIG. 20 is a flowchart of a route determination process by a delivery management server. FIG. 21 is an explanatory diagram (part 1) of an example of a route determination process based on logistics quality in a delivery management server. FIG. 22 is an explanatory diagram (part 2) of an example of a route determination process based on logistics quality in a delivery management server. FIG. 23 is an explanatory diagram (part 3) of an example of a route determination process based on logistics quality in a delivery management server.

[0009] Hereinafter, a route determination method, a route determination device, and a program according to an embodiment of the present disclosure will be described in detail with reference to the accompanying drawings.

[0010] 1 is a diagram showing an example of the schematic configuration of a delivery system 10 that delivers packages using electric vehicles (hereinafter referred to as "EVs") according to this embodiment. As shown in FIG. 1, the delivery system 10 includes a delivery management server 11, multiple delivery station systems 12A to 12C, multiple EV vehicles 13A1, 13A2, 13B1 to 13B3, 13C1, and 13C2, and a network 14.

[0011] First, we will explain the delivery management server 11. When the delivery management server 11 receives a delivery request requesting delivery of a package by driving an electric vehicle to one or more delivery destinations, it determines a route for the electric vehicle that passes through the desired delivery points included in the delivery request based on logistics quality information that indicates the degree of quality of logistics in the area to which the desired delivery points included in the delivery request belong.

[0012] In this case, the delivery request is an example of a driving request, and the delivery destination is an example of a destination. In other words, the delivery request is an example of a "driving request" that includes one or more destinations and requests that an EV vehicle drive via the destinations. In this embodiment, the delivery request is information that includes one or more combinations of information indicating a package and information such as an address indicating a delivery destination of the package (corresponding to the destination), and requests that the package be delivered to the delivery destination. Furthermore, the delivery request can also be considered as information that requests that an EV vehicle drive via the delivery destination included in the delivery request.

[0013] The specific configuration of the delivery management server 11 will be described below. FIG. 2 is a diagram showing an example of the hardware configuration of the delivery management server 11. In this embodiment, the delivery management server 11 is configured as a computer device. As shown in FIG. 2, the delivery management server 11 includes a processor 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, and a communication I / F (interface) 204. Note that the hardware elements of the delivery management server 11 are not limited to the configuration shown in FIG. 2, and may include other hardware elements (e.g., a display device, an input device, an external storage device, etc.).

[0014] The processor 201 is, for example, an MPU (Micro Processing Unit). By executing a program, the processor 201 comprehensively controls the operation of the delivery management server 11 and realizes various functions of the delivery management server 11. The various functions of the delivery management server 11 will be described later.

[0015] The ROM 202 is a non-volatile memory that stores various types of information including programs executed by the processor 201. The RAM 203 is a volatile memory that has a working area for the processor 201. The communication I / F unit 204 is an interface for connecting to the network 14.

[0016] Next, the delivery station systems 12A to 12C will be described. In the following description, when there is no need to distinguish between the delivery station systems 12A to 12C, they will be simply referred to as "delivery station systems 12."

[0017] Although FIG. 1 illustrates three delivery station systems 12A to 12C, the number of delivery station systems 12 included in the delivery system 10 is not limited to this and can be changed arbitrarily.

[0018] Delivery station system 12A manages electric vehicles 13A1 and 13A2 and is primarily responsible for deliveries in delivery area AR1. Delivery station system 12B manages electric vehicles 13B1 to 13B3 and is primarily responsible for deliveries in delivery area AR2. Delivery station system 12C manages electric vehicles 13C1 and 13C2 and is primarily responsible for deliveries in delivery area AR3.

[0019] Furthermore, delivery area AR1 is adjacent to delivery area AR2. As a result, electric vehicles 13A1 and 13A2 managed by delivery station system 12A are also able to make deliveries in delivery area AR2 if they satisfy certain conditions described below. Similarly, electric vehicles 13B1 to 13B3 managed by delivery station system 12B are also able to make deliveries in delivery area AR1 if they satisfy certain conditions described below.

[0020] Delivery area AR3 is also adjacent to delivery area AR2. As a result, electric vehicles 13C1 and 13C2 managed by delivery station system 12C are also able to make deliveries in delivery area AR2 if they satisfy certain conditions described below. Similarly, electric vehicles 13B1 to 13B3 managed by delivery station system 12B are also able to make deliveries in delivery area AR3 if they satisfy certain conditions described below.

[0021] 3 is a diagram illustrating the configuration of an example of a delivery station system. Since the configuration of any delivery station system is similar, the delivery station system 12B will be described here as an example.

[0022] The delivery station system 12B includes a station management device 121, a charging station 122, and an EV vehicle management device 123. In this example, the delivery station system 12B is provided with one charging station, but if there are a large number of EV vehicles under its management, it is possible to provide multiple charging stations.

[0023] The station management device 121 is a device (e.g., a site controller (SC)) that performs overall control of the delivery station system 12B. Under the management of the delivery management server 11, the station management device 121 also functions as a charging station management device and performs charging management at the charging station 122. Under the management of the delivery management server 11, the station management device 121 also controls the EV vehicle management device 123 and performs dispatch control of the EV vehicles under its management (EV vehicles 13B1 to 13B3 in the case of the delivery station system 12B).

[0024] The charging station 122 is a facility for charging (supplying power to) EV vehicles. The charging station 122 includes multiple EV chargers, a power meter, and a control unit. The EV chargers, the power meter, and the control unit are connected to a network such as a local area network (LAN) and can exchange data with each other.

[0025] The EV charger charges the battery of the EV vehicle using power transformed by a substation that transforms high-voltage power generated at a power plant or the like into power for charging the EV vehicle. The substation may be installed anywhere, and may be installed inside or outside the charging station 122.

[0026] A power meter (PM) is a device that measures the power supplied from a substation to an EV charger.

[0027] In the above configuration, the station management device 121 can acquire software configuration information for each of the EV charger, the power meter, and the control unit, and transmit the acquired software configuration information to the delivery management server 11. The software configuration information is information that indicates the software configuration, and in this embodiment, is a software bill of materials (SBOM) that includes the parts (components) that make up the software, the dependencies between the parts, versions, license information, etc. The specific contents of the SBOM will be described later.

[0028] Fig. 4 is a diagram showing an example of functions possessed by the delivery management server 11. Note that the example of Fig. 4 illustrates only functions necessary for explaining the main parts of this embodiment, but the functions possessed by the delivery management server 11 are not limited to these.

[0029] As shown in Figure 4, the delivery management server 11 has a delivery request receiving unit 110, an SBOM acquisition unit 111, a usage record acquisition unit 112, a review acquisition unit 113, a logistics quality determination unit 114, a logistics quality information database unit 115, a map information storage unit 116, a route determination unit 117, a route information output unit 118, a delivery station reliability storage unit 119, and a power tightness storage unit 120.

[0030] Here, the delivery request receiving unit 110 functions as a driving request receiving unit, the logistics quality information database unit 115 functions as a logistics quality information storage unit, and the route determining unit 117 functions as a route determining unit.

[0031] In this embodiment, the processor 201 executes a program stored in the ROM 202 to realize the functions of the delivery request receiving unit 110, the SBOM acquisition unit 111, the usage record acquisition unit 112, the review acquisition unit 113, the logistics quality determination unit 114, the route determination unit 117, the route information output unit 118, the delivery station reliability memory unit 119, and the power tightness memory unit 120.

[0032] However, without being limited to this, some or all of these functions may be realized by dedicated hardware circuits (semiconductor integrated circuits, etc.) Furthermore, the logistics quality information database unit 115 and the map information storage unit 116 are realized by, for example, the ROM 202, but are not limited to this and may be realized by, for example, an external storage device (SSD, hard disk, etc.) externally attached to the delivery management server 11.

[0033] The delivery request receiving unit 110 is an example of a "driving request receiving unit" and receives a delivery request for delivery of a package. As described above, the delivery request includes one or more combinations of information indicating the package and information indicating the delivery destination (corresponding to the destination) of the package, and is information requesting that the EV vehicle travel via the delivery destination of the package.

[0034] For example, in this embodiment, a delivery request input in response to a user's operation via a terminal (not shown) carried by the user is transmitted to the delivery management server 11 via the network 14. The delivery request receiving unit 110 can then receive the delivery request transmitted from the terminal via the network 14. The delivery request may also be a delivery request transmitted from a delivery management server of another delivery system similar to the delivery system 10.

[0035] SBOM acquisition unit 111 is an example of a "reliability acquisition unit" and acquires the SBOM of each of station management device 121, charging station 122, and EV vehicle management device 123 in delivery station system 12. In this embodiment, SBOM acquisition unit 111 accesses station management device 121 to acquire the SBOM. The timing of acquiring the SBOM is arbitrary; for example, SBOM acquisition unit 111 may periodically access station management device 121 to acquire the SBOM, or may acquire the SBOM when it receives a notification of an SBOM update from station management device 121.

[0036] Also, for example, the station management device 121 may send the updated SBOM to the delivery management server 11 (SBOM acquisition unit 111) every time the SBOM managed by the device is updated, or the station management device 121 may send the SBOMs of each device to the delivery management server 11 all at once at regular intervals.

[0037] Furthermore, for example, the SBOM acquisition unit 111 has the authority to access the network within the delivery station system 12, and can acquire the SBOM of each device included in the charging station 122 and the EV vehicle management device 123 directly from the charging station 122 and the EV vehicle management device 123 without going through the station management device 121.

[0038] The usage record acquisition unit 112 acquires the usage record of each charging station 122 in the delivery station system 12. In this embodiment, examples of the usage record are assumed to be the time required to charge an EV vehicle at the charging station 122 (charging time) and the time the EV vehicle waits at the charging station 122 until charging begins (waiting time).

[0039] In this embodiment, the EV vehicle measures the charging time and standby time, and transmits the measured time and information linking the charging station 122 to the station management device 121 via the charging station 122. The station management device 121 then manages the actual charging time and standby time of each charging station 122. For example, the EV vehicle management device 123 may manage the average values ​​of the actual charging time and standby time for each charging station 122, and can periodically update and manage this information.

[0040] In this embodiment, the usage record acquisition unit 112 acquires the usage record by accessing the station management device 121. The timing of acquiring the usage record is arbitrary, and for example, the usage record acquisition unit 112 may periodically access the station management device 121 to acquire the usage record, or may acquire the usage record when it receives a notification of an update of the usage record from the station management device 121. Note that this is not limited to this, and for example, the station management device 121 may update the usage record at regular intervals and transmit the updated usage record to the delivery management server 11.

[0041] The review acquisition unit 113 acquires user reviews (impressions, critiques) of the delivery station system 12. In this embodiment, a terminal carried by a user transmits reviews input in response to user operations to the delivery management server 11 via the network 14. The review acquisition unit 113 can acquire reviews transmitted from the terminal via the network 14.

[0042] The SBOM acquired by the SBOM acquisition unit 111, the usage record acquired by the usage record acquisition unit 112, and the reviews acquired by the review acquisition unit 113 are input to the logistics quality determination unit 114 and used to determine the reliability of each delivery station system 12. A specific method for determining the reliability will be described later.

[0043] The logistics quality determination unit 114 determines the logistics quality of the delivery area corresponding to the delivery station system 12. The logistics quality determination unit 114 determines the logistics quality according to the reliability and power tightness based on the evaluation of the delivery station system 12. A specific method for determining the logistics quality will also be described later.

[0044] First, the evaluation of the delivery station system will be described. The evaluation of the delivery station system 12 includes an evaluation based on the SBOM of each of the multiple devices included in the delivery station system 12 (the station management device 121, the charging station 122, and the EV vehicle management device 123), an evaluation related to the usage record, and an evaluation based on user reviews. For each of these evaluations, the logistics quality determination unit 114 calculates a reliability (individual reliability) according to the evaluation, and determines the reliability (overall reliability) of the delivery station system 12 based on the calculated reliability. Specific details will be described below.

[0045] 5 is an explanatory diagram of a reliability determination table for a delivery station system. In FIG. 5, the delivery station system 12B is used as an example. In this embodiment, the logistics quality determination unit 114 determines the reliability of the delivery station system 12 using a reliability determination table for determining reliability as shown in FIG.

[0046] The reliability determination table shown in Figure 5 has three evaluation items: "Devices," "Usage Records," and "Reviews" included in the delivery station system 12, and each item is associated with a reliability and a weight according to the evaluation of that item. The method for determining the reliability according to the evaluation of each item will be described below.

[0047] First, a method for determining reliability according to an evaluation of an "equipment" will be described. In this embodiment, the evaluation of an "equipment" is an evaluation based on the SBOM of each of the multiple devices included in the delivery station system 12 (the station management device 121, the charging station 122, and the EV vehicle management device 123), an evaluation based on the SBOM of the EV vehicle, and an evaluation based on the driving range of the EV vehicle. The logistics quality determination unit 114 determines a reliability for each of the multiple devices included in the delivery station system 12 according to the evaluation based on the SBOM of the device.

[0048] In this embodiment, the SBOM-based evaluation is composed of three items: a risk evaluation, a vulnerability evaluation, and a license evaluation. However, the evaluation is not limited to these, and may be a combination of one or two of these. In short, the SBOM-based evaluation may be in any form as long as it includes at least one of a risk evaluation, a vulnerability evaluation, and a license evaluation. The logistics quality determination unit 114 obtains at least one of the risk evaluation, the vulnerability evaluation, and the license evaluation based on the SBOM, and determines the reliability based on the obtained evaluation.

[0049] Next, a method for determining reliability according to an SBOM-based evaluation will be described. FIG. 6 is a diagram showing an example of the relationship between the reliability and weight of each of a plurality of evaluation items constituting an SBOM-based evaluation according to an embodiment. As described above, in this embodiment, an SBOM-based evaluation is composed of three items: an evaluation related to risk, an evaluation related to vulnerability, and an evaluation related to licenses. In this embodiment, a weight is set for each of the above items, for example, as shown in FIG. 6.

[0050] The logistics quality determination unit 114 then calculates the reliability for each item according to the evaluation of that item, performs a weighted sum of the calculated reliability, and determines the result of the weighted sum as the reliability according to the evaluation based on the SBOM.

[0051] A method for determining the reliability of each of the three items will be described below. First, a method for determining the reliability according to the risk evaluation will be described. FIG. 7 is a diagram showing an example of the correspondence between the score (evaluation value) indicating the risk evaluation and the reliability. Here, risk means, for example, the possibility that a vulnerability will be exploited. Furthermore, vulnerability means a flaw in information security, for example, the possibility that the safety of information will be compromised.

[0052] In the example of Figure 7, the higher the score, the higher the possibility that the vulnerability will be exploited, and the lower the reliability of the operation of the station management device 121 or the operation of the EV vehicle.

[0053] 7, a reliability of "4" is associated with a score of "0," a reliability of "3" is associated with a score in the range of "0.1 to 3.9," a reliability of "1" is associated with a score in the range of "4.0 to 7.9," and a reliability of "0" is associated with a score in the range of "8.0 to 10.0." Note that, although the reliability is set to four levels in the example of FIG. 7, this is not limiting, and the number of reliability levels can be changed as desired depending on design conditions, etc.

[0054] In the example of FIG. 7, the risk level is divided into four levels according to the score: "None," "Low," "High," and "Critical," and the higher the score, the higher the risk level.

[0055] Fig. 8 is an explanatory diagram of levels and their definitions. In the example of Fig. 8, the risk level "None" indicates that there is no problem. "Low" indicates that although vulnerabilities may be exploited only through physical access, there is almost no impact on the system or business.

[0056] "High" indicates that the vulnerability is difficult to exploit. "Critical" indicates that the vulnerability is easy to exploit. If a vulnerability at the "High" or "Critical" level is exploited, it could result in escalation of access privileges, software tampering, execution of unauthorized software, data theft or data tampering, or system outage.

[0057] Next, a method for calculating a risk score will be described. Fig. 9 is an explanatory diagram of a risk score calculation table. In this embodiment, the logistics quality determination unit 114 calculates a risk score based on the calculation table shown in Fig. 9, but the method for calculating the score is not limited to this.

[0058] The score calculation table in Figure 9 has five judgment items: "Attacker's motive for attack (theft, impersonation)," "Possibility of zero-day attack," "Risk level of vulnerability," "Vulnerable component or library," and "Ease of access to the target of attack." For each item, a judgment criterion, a judgment value according to the judgment result, and a weight are set. The logistics quality determination unit 114 uses the SBOM of the device whose reliability is to be determined to determine the judgment value for each item in the judgment table shown in Figure 7, and performs a weighted addition of the obtained judgment values. The result of the weighted addition becomes the risk score. A specific description will be given below.

[0059] Fig. 10 is an explanatory diagram of SBOM. Prior to describing the determination method using the score calculation table shown in Fig. 9, the specific contents of SBOM will be described using Fig. 10. SBOM is information (software bill of materials) that indicates the configuration of software used in a device. In the example of Fig. 10, the items that make up the SBOM include, but are not limited to, package name / package version, dependent packages, package revision history, build information, license information, and security information.

[0060] In the package name / package version section, the specific package name / package version of the software used in the device is described in association with a functional description. For example, for the package name / package version "OS001 / 20.03", a functional description indicating that it is an operating system, which is the basic system that runs the software, is described in association with the package name / package version.

[0061] Similarly, "NC001 / 1.1.1f" is associated with a functional description describing it as network communication software that performs data communication via a network. Similarly, "OPC0001 / 3.24" is associated with a functional description describing it as operation panel control software that controls a panel operated by a user. Similarly, "WS0001 / 2.4" is associated with a functional description describing it as web server software that performs data communication with devices such as the station management device 121. Similarly, "DB001 / 8.0" is associated with a functional description describing it as database software that stores personal information such as IDs and used for payment.

[0062] In the "Dependent Packages" section, the package name and the library to be used are associated and described. For example, "NC001," which indicates the package name of network communication software, is associated with libraries A and B. This means that data communication is performed via the network using libraries A and B.

[0063] Similarly, "OS001", which indicates the package name of the operating system, corresponds to libraries C, D, and E. Similarly, "WS0001", which indicates the package name of the web server software, corresponds to libraries F, G, H, and K. Similarly, "DB0001", which indicates the package name of the database software, corresponds to libraries L and M.

[0064] The "Package Modification History" section describes the modification history for each package. The "Build Information" section describes the build date and update date. The update date includes the date of the most recent update and the date of the previous update.

[0065] The "license information" section describes the support period and expiration date. The "security information" section describes vulnerability information in association with a CVE number that identifies the vulnerability information, the registration date of the CVE number, a CVSS value that indicates the severity of the vulnerability, the degree of impact on confidentiality, the degree of impact on integrity, and the degree of impact on availability. In the example of Figure 10, the vulnerability information describes that library G of the web server software records a string crafted by a remote attacker in a log, which allows arbitrary Java code to be executed on the system.

[0066] The logistics quality determination unit 114 uses the SBOM described above to make a judgment for each judgment item in the score calculation table shown in Fig. 9, and calculates a judgment value according to the judgment result. Then, the judgment values ​​calculated for each judgment item are weighted and added, and the result of the weighted addition is determined as the risk score.

[0067] Hereinafter, a determination method using SBOM will be described for each determination item in the score calculation table shown in FIG.

[0068] First, we will explain how to determine "the attacker's motive for attacking" from the five determination items included in the score calculation table shown in FIG. 9 . The determination criterion for this determination item is the presence or absence of personal information, such as an ID or payment information, within the device. The logistics quality determination unit 114 determines the presence or absence of an ID or payment information within the device by referring to the SBOM. In the SBOM shown in FIG. 8 , the function description corresponding to the package name of the database software ("DB0001" in the example of FIG. 8 ) also describes whether personal information is stored. Therefore, the logistics quality determination unit 114 can determine the presence or absence of personal information by referring to this section. Then, a determination value corresponding to the determination result is calculated according to the score calculation table shown in FIG. 9 . In the example of FIG. 9 , if personal information is present, the determination value is "1," and if personal information is not present, the determination value is "0."

[0069] Next, a method for determining the "possibility of a zero-day attack" will be described. The determination criterion for this determination item is whether a remote update (update via remote operation) is possible. The logistics quality determination unit 114 determines whether a remote update is possible by referencing the SBOM. In this example, the conditions for a remote update being possible are that network communication is possible and that the device supports remote updates. The logistics quality determination unit 114 can determine whether network communication is possible by referencing the SBOM and determining whether network communication software is being used.

[0070] Furthermore, in the SBOM shown in FIG. 10, the function description corresponding to the package name indicating the operating system also describes whether or not the device supports remote updates, so the logistics quality determination unit 114 can determine whether or not the device supports remote updates by referring to this section.

[0071] A judgment value corresponding to the judgment result is then calculated according to the score calculation table shown in Fig. 9. In the example of Fig. 9, if a remote update is not possible, the judgment value is "1", and if a remote update is possible, the judgment value is "0". If a remote update is not possible, it is more likely that the update will take longer than if a remote update is possible, and therefore the risk increases accordingly.

[0072] Next, we will explain how to determine the "risk level of vulnerability." The criteria for these assessment items are "possibility of information leakage," "possibility of information tampering," and "possibility of business suspension," and a judgment value and weight are set according to the assessment result for each.

[0073] The logistics quality determination unit 114 determines the "possibility of information leakage" by referring to the SBOM. As described with reference to FIG. 10 , the security information section of the SBOM also describes the degree of impact on confidentiality. Therefore, the logistics quality determination unit 114 can determine the possibility of information leakage by referring to this section. For example, if the impact on confidentiality is large, it can be determined that the possibility of information leakage is also high. The logistics quality determination unit 114 then calculates a judgment value according to the judgment result in accordance with the score calculation table shown in FIG. 9 . In the example of FIG. 9 , if there is a high possibility of information leakage, the judgment value is "2." If there is a low possibility of information leakage, the judgment value is "1." If there is no possibility of information leakage, the judgment value is "0." For example, a case where there is a high possibility of information leakage is assumed to be a case where confidential information or important files are accessible. Furthermore, a case where there is a low possibility of information leakage is assumed to be a case where the impact, even if an information leakage occurs, is limited.

[0074] The logistics quality determination unit 114 also references the SBOM to determine the "possibility of information tampering." As described with reference to FIG. 10 , the security information section of the SBOM also describes the degree of impact on integrity. Therefore, the logistics quality determination unit 114 can determine the possibility of information tampering by referencing this section. For example, if the impact on integrity is large, it can be determined that the possibility of information tampering is also high. The logistics quality determination unit 114 then calculates a judgment value according to the judgment result in accordance with the score calculation table shown in FIG. 9 . In the example of FIG. 9 , if the possibility of information tampering is high, the judgment value is "2." If the possibility of information tampering is low, the judgment value is "1." If there is no possibility of information tampering, the judgment value is "0." For example, a case where there is a high possibility of information tampering is assumed to be a case where confidential information or important files can be tampered with. Furthermore, a case where there is a low possibility of information tampering is assumed to be a case where information tampering is possible but confidential information or important files cannot be tampered with.

[0075] The logistics quality determination unit 114 also references the SBOM to determine the "possibility of business outage." As described with reference to FIG. 10, the security information section of the SBOM also describes the degree of impact on availability, so the logistics quality determination unit 114 can determine the possibility of business outage by referencing this section. For example, if the impact on availability is large, it can be determined that the possibility of business outage is also high. The logistics quality determination unit 114 then calculates a determination value according to the determination result in accordance with the score calculation table shown in FIG. 9.

[0076] In the example of Figure 9, when there is a high possibility of business interruption, the judgment value is "2", when there is a low possibility of business interruption, the judgment value is "1", and when there is no possibility of business interruption, the judgment value is "0". For example, when there is a high possibility of business interruption, it is assumed that resources are completely depleted or that business can be completely stopped. Also, when there is a low possibility of business interruption, it is assumed that resources are temporarily depleted or that business can be delayed or temporarily suspended.

[0077] Next, a method for determining "vulnerable components or libraries" among the five determination items included in the score calculation table shown in FIG. 9 will be described. The determination criterion for this determination item is whether or not a vulnerable component or library is used. The logistics quality determination unit 114 refers to the SBOM to determine whether or not a vulnerable component or library is used. As explained using FIG. 10 , the security information in the SBOM also includes information about vulnerabilities, and in the example of FIG. 10 , library G is identified as a vulnerable library. Then, referring to the dependent package item in the SBOM shown in FIG. 10 , library G is described in association with "WS0001," which indicates the package name of the Web server software.

[0078] In other words, since it is known that the Web server software uses library G to perform data communication with devices such as the station management device 121, in this case the logistics quality determination unit 114 can determine that a vulnerable library G is being used. Then, the logistics quality determination unit 114 calculates a judgment value according to the judgment result in accordance with the score calculation table shown in Fig. 9. In the example of Fig. 9, if a vulnerable component or library is being used, the judgment value is "2", if it is being used but can be disabled, the judgment value is "1", and if it is not being used, the judgment value is "0".

[0079] Next, we will explain how to determine the "access difficulty of the attack target." The criteria for this determination item are whether the attack source category is the Internet, a local network or Bluetooth®, or physical access. The access difficulty decreases (the determination value increases) in the order of Internet, local network or Bluetooth, and physical access. The logistics quality determination unit 114 references the SBOM to determine whether the data communication method is the Internet, local network or Bluetooth, or physical access. The SBOM shown in FIG. 10 describes a package name (NC001) indicating network communication software that performs data communication via the network, and the corresponding function description also describes whether data communication is performed via the Internet, a local network, or Bluetooth. By referencing this section, the logistics quality determination unit 114 can determine the data communication method. The logistics quality determination unit 114 then calculates a determination value corresponding to the determination result according to the score calculation table shown in FIG. 9. In the example of FIG. 7, if the means of data communication is the Internet, the judgment value is "2", if it is a local network or Bluetooth, the judgment value is "1", and if it is physical access, the judgment value is "0".

[0080] The logistics quality determination unit 114 performs a weighted addition of the judgment values ​​obtained from each of the above judgment results using the weights set in the score calculation table shown in Fig. 9, and determines the result of the weighted addition as the risk score. Then, the logistics quality determination unit 114 determines the reliability corresponding to the risk score by referring to the correspondence relationship shown in Fig. 6.

[0081] Next, a method for determining the reliability according to the evaluation of vulnerability among the three items shown in Fig. 6 will be described. Fig. 11 is a diagram showing an example of the correspondence between the score (evaluation value) indicating the evaluation of vulnerability and the reliability.

[0082] As described above, vulnerability refers to, for example, the possibility of compromising the security of information. In the example of FIG. 11 , the higher the score, the greater the vulnerability and the lower the reliability. In the example of FIG. 11 , a reliability of "4" is associated with a score of "0," a reliability of "3" is associated with a score in the range of "0.1 to 3.9," a reliability of "2" is associated with a score in the range of "4.0 to 6.9," a reliability of "1" is associated with a score in the range of "7.0 to 8.9," and a reliability of "0" is associated with a score in the range of "9.0 to 10.0." Note that, in the example of FIG. 11 , the reliability is set to five levels, but this is not limiting, and the number of reliability levels can be changed as desired depending on design conditions, etc.

[0083] 11, the vulnerability level is divided into five levels according to the score: "None," "Low," "Medium," "High," and "Critical," and the higher the score, the higher the vulnerability level. Note that the number of levels according to the score is not limited to this and can be set arbitrarily.

[0084] Next, a method for calculating a vulnerability score will be described. In this embodiment, the logistics quality determination unit 114 calculates a vulnerability score by referring to the SBOM shown in FIG. 10. More specifically, in the security information section of the SBOM shown in FIG. 10, information about a vulnerability is described in association with a CVSS value indicating the severity of the vulnerability. The logistics quality determination unit 114 determines this CVSS value as the vulnerability score. Then, the logistics quality determination unit 114 determines the reliability corresponding to the vulnerability score by referring to the correspondence relationship shown in FIG. 11.

[0085] Next, a method for determining the reliability according to the evaluation of the license among the three items shown in Fig. 6 will be described. Fig. 12 is a diagram showing an example of the correspondence between the score (evaluation value) indicating the evaluation of the license and the reliability.

[0086] The license evaluation can also be thought of as representing the degree of license-related problems (license issues). In the example of FIG. 10, the higher the score, the greater the degree of license issues and the lower the reliability. In the example of FIG. 10, a reliability of "2" is associated with a score of "0," a reliability of "1" is associated with a score in the range of "0.1 to 5.9," and a reliability of "2" is associated with a score in the range of "6.0 to 10.0." Note that in the example of FIG. 10, the reliability is set to three levels, but this is not limiting, and the number of reliability levels can be changed as desired depending on design conditions, etc.

[0087] In the example of FIG. 12, the license issue level is divided into three levels according to the score: "None," "Low," and "High," with a higher score indicating a higher license issue level. In this example, the license issue level "None" indicates that there are no problems. "Low" indicates that the service can continue, but that measures such as license renewal are required. "High" indicates that there is a possibility that the service will be stopped, and that the quality of the service will be reduced due to malfunctions or the like, which is equivalent to a license violation. Note that the number of levels according to the score is not limited to this and can be changed as desired according to design conditions, etc.

[0088] Next, a method for calculating the license score (score of the license issue) will be described. FIG. 13 is an explanatory diagram of a license issue score calculation table. In this embodiment, the logistics quality determination unit 114 calculates the license score based on the score calculation table shown in FIG. 13, but the method for calculating the score is not limited to this. The score calculation table in FIG. 13 has two license issue items, "software support period" and "software update," and for each item, a judgment criterion, a judgment value corresponding to the judgment result, and a weight are set.

[0089] The logistics quality determination unit 114 uses the SBOM described with reference to Fig. 10 to make a determination for each determination item in the score calculation table shown in Fig. 13 and calculates a determination value according to the determination result. The determination values ​​calculated for each determination item are then weighted and added together, and the result of the weighted addition is determined as the score for the license. The determination method using the SBOM is described below for each determination item in the score calculation table shown in Fig. 13.

[0090] First, we will explain how to determine the "software support period" of the two determination items included in the score calculation table shown in Figure 13. The determination criterion for this determination item is whether or not the software is within its support period. As described above, the support period is described in the license information item of the SBOM shown in Figure 10. By referring to this section, the logistics quality determination unit 114 can determine whether or not the software is within its support period.

[0091] Then, the logistics quality determination unit 114 calculates a judgment value according to the judgment result in accordance with the score calculation table shown in Fig. 13. In the example of Fig. 13, if the support period for the software has expired, the judgment value is "2", if the period has expired but the software can still be used, the judgment value is "1", and if the period is still valid, the judgment value is "0".

[0092] Next, a method for determining whether or not software updates have been performed will be described. The determination criterion for this determination item is whether or not software updates have been performed appropriately. In the example of Fig. 13, five determination criteria are provided: no updates, yearly updates, semi-annual updates, monthly updates, and updates when security information is updated.

[0093] As described above, the build information field in the SBOM shown in FIG. 10 describes the update dates, including the date of the most recent update and the date of the previous update. The logistics quality determination unit 114 can determine the frequency of software updates by referencing this field. The logistics quality determination unit 114 then calculates a judgment value corresponding to the judgment result, in accordance with the score calculation table shown in FIG. 13 . In the example of FIG. 13 , if there is no update, the judgment value is "4." If there is an update every year, the judgment value is "3." If there is an update every six months, the judgment value is "2." If there is an update every month, the judgment value is "1." If there is an update every time security information is updated, the judgment value is "0."

[0094] The logistics quality determination unit 114 performs weighted addition on the judgment values ​​obtained from the above judgment results using the weights set in the score calculation table shown in Fig. 13, and determines the result of the weighted addition as the score of the license. Then, the logistics quality determination unit 114 determines the reliability corresponding to the license score by referring to the correspondence relationship shown in Fig. 12.

[0095] In this way, the logistics quality determination unit 114 determines the reliability of each of the three items (risk assessment, vulnerability assessment, and license assessment) shown in Figure 6 and performs a weighted sum using the weights set for each item. The logistics quality determination unit 114 determines the result of this weighted sum as the reliability corresponding to the assessment based on the SBOM. In this way, the logistics quality determination unit 114 determines the reliability of each device included in the delivery station system 12 according to the assessment based on the SBOM of that device.

[0096] FIG. 14 is an explanatory diagram of license issue levels. In the example of FIG. 13, license issue scores are divided into three levels: "None," "Low," and "High." The higher the score, the higher the license issue level. As shown in FIG. 14, the license issue score "None" indicates that there are no problems with the license issue. The license issue level "Low" indicates that the service can continue, but that measures such as license renewal are required. The license issue score "High" indicates that there is a possibility of service interruption, which may result in a deterioration in service quality due to malfunctions or other reasons, and is equivalent to a license violation. Note that the number of levels corresponding to the score is not limited to this and can be changed as desired depending on design conditions, etc.

[0097] Next, an evaluation based on the driving range of an EV vehicle will be described. Fig. 15 is a diagram showing an example of the correspondence relationship between the driving range of an EV vehicle and its reliability. The reliability of the driving range of an EV vehicle can be considered as how long a distance the vehicle can travel.

[0098] In the example of Fig. 15, the reliability is set to be higher as the driving distance is longer. In the example of Fig. 15, when the driving distance of the EV vehicle is 300 km or more, the reliability is associated with "3", when the driving distance of the EV vehicle is 150 km to 299 km, the reliability is associated with "2", when the driving distance of the EV vehicle is 50 km to 149 km, the reliability is associated with "1", and when the driving distance of the EV vehicle is 0 km to 49 km, the reliability is associated with "0".

[0099] In the example of FIG. 15, the reliability is set to three levels, but the number of levels can be arbitrarily changed depending on the design conditions and the like.

[0100] Next, a method for determining the reliability according to the evaluation of the "usage record" out of the three items shown in FIG. 5 will be described. The evaluation of the "usage record" includes an evaluation regarding the charging time and an evaluation regarding the waiting time. The logistics quality determination unit 114 determines the reliability according to the evaluation regarding the charging time and the reliability according to the evaluation regarding the waiting time. In this embodiment, the logistics quality determination unit 114 determines the reliability such that the smaller the difference between the actual charging time and the expected charging time at the charging station 122, the higher the evaluation regarding the charging time at the charging station 122 and the higher the reliability, and the smaller the difference between the actual waiting time and the expected waiting time at the charging station 122, the higher the evaluation regarding the waiting time at the charging station 122 and the higher the reliability.

[0101] Next, a method for determining the reliability according to the evaluation based on the "review" of the three items shown in FIG. 5 will be described. Evaluation based on reviews includes evaluation based on reviews by registered members and evaluation based on reviews by non-registered members. The logistics quality determination unit 114 determines the reliability according to the evaluation based on reviews by registered members and the reliability according to the evaluation based on reviews by non-registered members. In this embodiment, the logistics quality determination unit 114 determines the reliability such that the higher the evaluation based on reviews, the higher the reliability.

[0102] Next, a method for determining the local logistics quality in a delivery area will be described. The logistics quality is determined by the logistics quality determination unit 114 based on the reliability and power tightness of the delivery station system.

[0103] First, the reliability rank of the delivery station system will be described. Fig. 16 is a diagram illustrating the correspondence between the reliability of the delivery station system and the reliability rank.

[0104] The reliability of the delivery station system 12 is calculated by adding up reliability points for whether or not a delivery corresponding to a delivery request was actually made and whether or not the delivery was made without delay according to a predetermined delivery schedule, and then totaling the reliability points for a predetermined period. In this case, it is also possible to weight the delivery requests based on the content of the delivery requests (whether or not a date or time was specified, whether or not a re-delivery was requested), etc.

[0105] For example, if the reliability of the delivery station system 12 is found to be 100 or higher, delivery is deemed to be possible reliably and without delay, and the reliability is ranked as A. If the reliability of the delivery station system 12 is found to be 50 or higher but less than 100, delivery is deemed to be possible, and the reliability is ranked as B. If the reliability of the delivery station system 12 is less than 50, delivery may not be possible, and the reliability is ranked as C.

[0106] Next, the power pressure level ranking will be explained. Fig. 17 is an explanatory diagram of the power pressure level ranking. The power pressure level is determined based on whether or not an EV vehicle can be charged at a charging station 122 within a delivery station supported by the delivery station system 12, whether or not an EV charging station provided outside the delivery station is available, and whether or not charging is possible in a short time (shorter than a predetermined time) at a charging station 122 within the delivery station or an EV charging station provided outside the delivery station.

[0107] For example, if there is a possibility that an EV vehicle cannot be charged at the charging station 122 within the delivery station, and if there is a possibility that an EV charging station located outside the delivery station is unavailable, the power tightness rank is set to "High." Furthermore, if an EV vehicle can be charged at the charging station 122 within the delivery station, and if an EV charging station located outside the delivery station is available, the power tightness rank is set to "Mid."

[0108] In addition, if an EV vehicle can be charged in a specified short time at the charging station 122 within the delivery station, or if an EV charging station located outside the delivery station is available and can be charged in a specified short time, the power tightness rank is set to "Low."

[0109] Next, the correspondence between the reliability rank and power pressure rank of the delivery station system and the logistics quality of the area will be explained. Figure 18 is an explanatory diagram of the correspondence between the reliability rank and power pressure rank of the delivery station system and the logistics quality of the area.

[0110] For example, if the reliability rank of the delivery station system is "A" and the power tightness rank is "Low," the regional logistics quality will be ranked "A." Also, if the reliability rank of the delivery station system is "B" and the power tightness rank is "Mid," the regional logistics quality will be ranked "B."

[0111] Furthermore, if the reliability of the delivery station system is ranked "B" and the power shortage is ranked "High", the logistics quality of the area will be ranked "C".

[0112] Next, a specific example of logistics quality in a delivery area will be described. Figure 19 is an explanatory diagram of a specific example of logistics quality in a delivery area. In the delivery area AR1 of the delivery station system 12A, the reliability rank of the delivery station system is "B" and the power tightness rank is "Mid", so based on Figure 18, the logistics quality of the delivery area AR1 of the delivery station system 12A is "B". In other words, the logistics quality of the delivery area AR1 is determined to be such that delivery is possible.

[0113] In the delivery area AR2 of the delivery station system 12B, the reliability rank of the delivery station system is "A" and the power tightness rank is "Low", so based on Figure 18, the logistics quality of the delivery area AR2 of the delivery station system 12B is "A". In other words, the logistics quality of the delivery area AR2 is determined to be reliable and capable of delivery without delay, and collection and delivery to neighboring areas is possible.

[0114] In the delivery area AR3 of the delivery station system 12C, the reliability rank of the delivery station system is "B" and the power tightness rank is "High", so based on Figure 18, the logistics quality of the delivery area AR3 of the delivery station system 12C is "C". In other words, the logistics quality of the delivery area AR3 is determined to be such that delivery is only possible within the area.

[0115] Here, an example of calculating the reliability of the entire delivery station system 12 will be described. For example, in the reliability determination table for the delivery station system shown in Figure 5, the maximum reliability of each device according to the evaluation based on the SBOM of the "device" is 9.6, the maximum reliability of each EV vehicle according to the evaluation of the EV vehicle's driving range is 3, the maximum reliability according to the evaluation regarding charging time included in the evaluation of the "usage history" is 2.0, the maximum reliability according to the evaluation regarding standby time is 2.0, the maximum reliability according to the evaluation based on reviews of registered members included in the evaluation of the "reviews" is 2.0, and the maximum reliability according to the evaluation based on reviews of non-registered members is 2.0. Considering a case where the reliability of each item in the reliability determination table shown in Figure 5 is set to the maximum value and weighted addition is performed, the result of the weighted addition is as follows:

[0116] Overall reliability = (station management device 121: 9.6 x 1.0 + charging station 122: 6.6 x 1.0 + EV vehicle management device 123: 7.6 x 1.0 + EV vehicle 13B1: 7.6 x 0.8 + EV vehicle 13B2: 9.6 x 0.8 + EV vehicle 13B3: 7.6 x 0.8 + EV vehicle 13B1 driving range: 2 x 1.0 + EV vehicle 13B2 driving range: 2 x 1.0 + EV vehicle 13B3 driving range: 3 x 1.0 + (charging time: 3 x 0.5 + standby time: 4 x 0.5) + (registered member reviews: 4 x 0.3 + non-registered member reviews: 3 x 0.4) = 119.54.

[0117] The logistics quality determination unit 114 can also determine a rank corresponding to the reliability of the delivery station system 12 obtained as described above, using correspondence information indicating the correspondence between rank and reliability, such as that shown in Figure 16.

[0118] In the example of Fig. 16, the ranks are divided into three levels: "A", "B", and "C", where a reliability of 100 or more is classified as "A" rank, a reliability of 50 or more and less than 100 is classified as "B" rank, and a reliability of less than 50 is classified as "C" rank. As described above, a reliability of 119.54 corresponds to "A" rank.

[0119] Here, the route determination process of the delivery management server 11 will be described in the situation shown in Fig. 19. Fig. 20 is a flowchart of the route determination process of the delivery management server. Fig. 21 is an explanatory diagram (part 1) of an example of the route determination process based on logistics quality in the delivery management server.

[0120] In the following, with reference to FIG. 4, a process will be described in which the delivery management server 11 receives a delivery request for delivery to a plurality of delivery destinations DP3-1 to DP3-3 in delivery area AR3.

[0121] When the delivery request receiving unit 110 receives a delivery request for delivery area AR3, it outputs the received delivery request to the route determination unit 117. As a result, the route determination unit 117 performs a process of determining the shortest delivery route SR using the delivery station system 12C and the electric vehicle 13C2 corresponding to the delivery area AR3 (step S11).

[0122] In this case, the shortest delivery route SR is composed of a route SR1 that travels from the delivery station corresponding to the delivery station system 12C to delivery destination DP3-1, a route SR2 that travels from delivery destination DP3-1 to delivery destination DP3-2, a route SR3 that travels from delivery destination DP3-2 to delivery destination DP3-3, and a route SR4 that returns from delivery destination DP3-3 to the delivery station corresponding to the delivery station system 12C.

[0123] Next, the route determination unit 117 refers to the logistics quality information database unit 115, reads the delivery station reliability from the delivery station reliability memory unit 119 corresponding to the delivery station system 12C, and determines whether the delivery station reliability of the delivery station corresponding to the delivery station system 12C is rank "B" or higher (step S12).

[0124] In the judgment of step S12, if the delivery station reliability of the delivery station corresponding to the delivery station system 12C is rank "B" or higher (step S12; Yes), there is no problem with the route determined in step S11, so the delivery route is determined and no changes are made to the delivery plan, and the route determination unit 117 notifies the station management device 121 of the delivery station system 12C of the determined delivery route via the route information output unit 118.

[0125] As a result, the station management device 121 notifies the electric vehicle 13C1 of the determined delivery route via the electric vehicle management device 123, and manages delivery so that delivery is made according to the shortest delivery route SR.

[0126] If, in the judgment of step S12, the delivery station reliability of the delivery station corresponding to the delivery station system 12C is below the "B" rank (step S12; No), the route determination unit 117 determines in step S12 whether the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "High" (step S13) in order to determine whether delivery can be reliably carried out according to the shortest delivery route SR.

[0127] In the judgment of step S13, if the power pressure level of the delivery area AR3 corresponding to the delivery station system 12C is not "High", that is, if the power pressure level of the delivery area AR3 corresponding to the delivery station system 12C is "Mid" or "Low", then there is no problem with the route determined in step S11, so the delivery route is determined and no changes are made to the delivery plan, and the route determination unit 117 notifies the station management device 121 of the delivery station system 12C of the determined delivery route via the route information output unit 118.

[0128] As a result, the station management device 121 notifies the electric vehicle 13C1 of the determined delivery route via the electric vehicle management device 123, and manages delivery so that delivery is made according to the shortest delivery route SR.

[0129] If the judgment in step S13 is that the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "High" (step S13; Yes), the route determination unit 117 determines that it is not desirable to carry out delivery according to the shortest delivery route SR, and searches for a nearby delivery station whose delivery station reliability is "B" rank or higher (preferably, "A" rank) (step S14).

[0130] In the process of step S14, referring to the logistics quality in the delivery areas in Fig. 19, the delivery station reliability of the delivery station corresponding to delivery area AR2 adjacent to delivery area AR3 is ranked "A", so the route determination unit 117 determines to use the delivery station corresponding to delivery station system 12C for delivery (step S15). As a result, the route determination unit 117 performs a process of determining a delivery route DR using delivery station system 12B and EV vehicle 13B1 corresponding to delivery area AR2 adjacent to delivery area AR3 (step S16), as shown in Fig. 21.

[0131] In this case, the delivery route DR is composed of a route DR1 that travels from the delivery station corresponding to delivery station system 12B to the delivery station corresponding to delivery station system 12C, a route DR2 that travels from the delivery station corresponding to delivery station system 12C to delivery destination DP3-1, a route DR3 that travels from delivery destination DP3-1 to delivery destination DP3-2, a route DR4 that travels from delivery destination DP3-2 to delivery destination DP3-3, and a route DR5 that returns from delivery destination DP3-3 to the delivery station corresponding to delivery station system 12B.

[0132] As a result, the route determination unit 117 notifies the station management device 121 of the delivery station system 12B of the determined delivery route via the route information output unit 118. As a result, the station management device 121 notifies the electric vehicle 13B1 of the determined delivery route DR via the electric vehicle management device 123, and manages the electric vehicle 13B1 so that delivery is made according to the route DR.

[0133] Figure 22 is an explanatory diagram (part 2) of an example of a route determination process based on logistics quality in the delivery management server. Figure 22 differs from Figure 21 in that the delivery management server 11 has previously arranged for the delivery item to be delivered to delivery station DSTB of delivery station 12B, rather than delivery station DSTC of delivery station 12C. Below, with reference to Figure 4, we will explain the process when the delivery management server 11 receives a delivery request to deliver to multiple delivery destinations DP3-1 to DP3-3 in delivery area AR3.

[0134] When the delivery request receiving unit 110 receives a delivery request for delivery area AR3, it outputs the received delivery request to the route determination unit 117. As a result, the route determination unit 117 performs a process of determining the shortest delivery route SR using the delivery station system 12C and the electric vehicle 13C2 corresponding to the delivery area AR3 (step S11).

[0135] In this case, the shortest delivery route SR is composed of a route SR1 that travels from the delivery station corresponding to the delivery station system 12C to delivery destination DP3-1, a route SR2 that travels from delivery destination DP3-1 to delivery destination DP3-2, a route SR3 that travels from delivery destination DP3-2 to delivery destination DP3-3, and a route SR4 that returns from delivery destination DP3-3 to the delivery station corresponding to the delivery station system 12C.

[0136] Next, the route determination unit 117 refers to the logistics quality information database unit 115, reads the reliability from the delivery station reliability memory unit 119 corresponding to the delivery station system 12C, and determines whether the delivery station reliability of the delivery station corresponding to the delivery station system 12C is rank "B" or higher (step S12).

[0137] In this example, in the judgment of step S12, the delivery station reliability of the delivery station corresponding to the delivery station system 12C is below the "B" rank (step S12; No), so in order to determine whether delivery can be reliably carried out according to the shortest delivery route SR, the route determination unit 117 judges in step S12 whether the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "High" (step S13).

[0138] In this example, in the judgment of step S13, the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "High" (step S13; Yes), so the route determination unit 117 determines that it is not desirable to carry out delivery according to the shortest delivery route SR, and searches for a nearby delivery station whose delivery station reliability is "B" rank or higher (preferably, "A" rank) (step S14).

[0139] In the processing of step S14, when referring to the logistics quality in the delivery area of ​​Figure 19, the delivery station reliability of delivery station DSTB corresponding to delivery area AR2, which is close to delivery area AR3, is ranked "A", so the route determination unit 117 decides to use the delivery station corresponding to delivery station system 12C for delivery (step S15).

[0140] At the same time, the delivery management server 11 arranges in advance for delivery of deliveries corresponding to the received delivery request for delivery to a plurality of delivery destinations DP3-1 to DP3-3 in the delivery area AR3 to the delivery station DSTB.

[0141] Then, the route determination unit 117 takes into consideration the scheduled delivery date of the delivery item to the delivery station DSTB and performs a process to determine a delivery route DR10 using a delivery station system 12B and an EV vehicle 13B1 corresponding to a delivery area AR2 adjacent to the delivery area AR3, as shown in Figure 22 (step S16).

[0142] In this case, delivery route DR10 is composed of a route DR11 that travels from delivery station DSTB corresponding to delivery station system 12B to delivery destination DP3-1, a route DR12 that travels from delivery destination DP3-1 to delivery destination DP3-2, a route DR13 that travels from delivery destination DP3-2 to delivery destination DP3-3, and a route DR14 that returns from delivery destination DP3-3 to the delivery station corresponding to delivery station system 12B.

[0143] As a result, the route determination unit 117 notifies the determined delivery route to the station management device 121 of the delivery station system 12B via the route information output unit 118.

[0144] As a result, the station management device 121 notifies the electric vehicle 13B1 of the determined delivery route DR10 via the electric vehicle management device 123, and manages the electric vehicle 13B1 so that delivery is made according to the route DR10. As a result, delivery can be made more reliably than when delivery is made using the delivery station system 12C.

[0145] 23 is an explanatory diagram (part 3) of an example of a route determination process based on logistics quality in the delivery management server. The route determination process in FIG. 23 differs from the above-described route determination processes in that the power shortage level in delivery area AR3 is determined to be "Low" because an external charging station can be used.

[0146] 4, the process when the delivery management server 11 receives a delivery request for delivery to multiple delivery destinations DP3-1 to DP3-3 in the delivery area AR3 will be described. When the delivery request receiving unit 110 receives a delivery request for the delivery area AR3, it outputs the received delivery request to the route determination unit 117.

[0147] As a result, the route determination unit 117 performs a process of determining the shortest delivery route SR using the delivery station system 12C and the electric vehicle 13C2 corresponding to the delivery area AR3 (step S11).

[0148] In this case, the shortest delivery route SR is composed of a route SR1 that travels from the delivery station corresponding to the delivery station system 12C to delivery destination DP3-1, a route SR2 that travels from delivery destination DP3-1 to delivery destination DP3-2, a route SR3 that travels from delivery destination DP3-2 to delivery destination DP3-3, and a route SR4 that returns from delivery destination DP3-3 to the delivery station corresponding to the delivery station system 12C.

[0149] Next, the route determination unit 117 refers to the logistics quality information database unit 115, reads the delivery station reliability from the delivery station reliability memory unit 119 corresponding to the delivery station system 12C, and determines whether the delivery station reliability of the delivery station corresponding to the delivery station system 12C is rank "B" or higher (step S12).

[0150] In this case, in the judgment of step S12, the delivery station reliability of the delivery station corresponding to the delivery station system 12C is rank "C" and less than rank "B" (step S12; No), so in order to determine whether delivery can be reliably carried out according to the shortest delivery route SR, the route determination unit 117 judges in step S12 whether the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "High" (step S13).

[0151] In this case, in the judgment of step S13, the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is not "High", that is, the power shortage level in the delivery area AR3 corresponding to the delivery station system 12C is "Low", so it is possible to use a delivery route using an external charging station EVCHG, but the route determination unit 117 determines that it is not desirable to carry out delivery according to the shortest delivery route SR.

[0152] Then, the route determination unit 117 determines a delivery route DR20 for delivering to a plurality of delivery destinations DP3-1 to DP3-3 in the delivery area AR3 via an external charging station EVCHG, as shown in FIG.

[0153] As shown in FIG. 23, the delivery route DR20 determined by the route determination unit 117 is composed of a route DR21 for moving from the delivery station DSTC corresponding to the delivery station system 12C to the charging station EVCHG to charge the EV vehicle 13C2, a route DR22 for moving from the charging station EVCHG to the delivery destination DP3-1 after the EV vehicle 13C2 has been charged, a route DR23 for moving from the delivery destination DP3-1 to the delivery destination DP3-2, a route DR24 for moving from the delivery destination DP3-2 to the delivery destination DP3-3, and a route DR25 for returning from the delivery destination DP3-3 to the delivery station corresponding to the delivery station system 12B.

[0154] As a result, the route determination unit 117 notifies the station management device 121 of the delivery station system 12C of the determined delivery route via the route information output unit 118. As a result, the station management device 121 notifies the electric vehicle 13C2 of the determined delivery route DR via the electric vehicle management device 123, and manages the electric vehicle 13C2 so that delivery is made according to the route DR.

[0155] As explained above, according to this example, even if the reliability of the delivery station system does not meet the reliability corresponding to the delivery request, a more suitable delivery route can be determined according to the power shortage level, and delivery can be carried out reliably and efficiently.

[0156] Although the embodiments of the present disclosure have been described above, the above-described embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These novel embodiments and modifications thereof are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims.

[0157] Furthermore, the effects of the embodiments described in this specification are merely examples and are not limiting, and other effects may also be obtained.

[0158] Modifications will be described below.

[0159] (1) Modification 1 Although not described in detail in the above embodiment, by updating the drivable distance of the EV vehicle as needed, it is also possible to determine the shortest route depending on the actual charge level (not necessarily a full charge) of the EV vehicle used for delivery. For example, in a configuration in which the delivery management server 11 specifies the EV vehicle to be used for delivery, the route determination unit 117 can determine the shortest route from among delivery routes that pass through charging stations EVCHG or delivery station systems 12 that have charging stations within a driving range depending on the charge level of the EV vehicle used for delivery.

[0160] The method of specifying the EV vehicles to be used for delivery is arbitrary, and for example, the delivery management server 11 may specify EV vehicles in order so that their frequency of use is equal, or may specify EV vehicles so that their mileage is equal, or the delivery request received from outside may include information specifying the EV vehicle to be used (for example, vehicle size, whether the vehicle is equipped with a refrigerator or freezer, etc.).

[0161] (2) Variation 2 In the above-described embodiment, it is assumed that the EV vehicle is fully charged at a charging station EVCHG on the route or at a delivery station system 12 that has a charging station. However, depending on the distance to the next delivery station system 12 or warehouse, for example, there may be cases where it is not necessary to fully charge the EV vehicle at the delivery station system 12 or charging station EVCHG that has a charging station just before that.

[0162] Therefore, the route determination unit 117 can also determine the amount of charge to be applied to the EV vehicle at the charging station EVCHGG or the delivery station system 12 that has the charging station, based on the location of the charging station EVCHGG or the delivery station system 12 that has the charging station on the determined route of the EV vehicle. In this case, the delivery management server 11 can output, in addition to the above-mentioned route information, information indicating the amount of charge to be applied to the EV vehicle at the charging station EVCHGG or the delivery station system 12 that has the charging station on the route indicated by the route information to the EV vehicle management device 123.

[0163] (3) Modification 3 In the above-described embodiment, the logistics quality information database unit 115 and the map information storage unit 116 are provided within the delivery management server 11, but this is not limiting, and the logistics quality information database unit 115 and the map information storage unit 116 may be stored in any location, and may be provided, for example, in a device outside the delivery management server 11 (an external device such as a server or storage device).

[0164] (4) Variation 4 The delivery management server 11 described above is applied to a delivery system 10 that delivers packages using electric vehicles, but is not limited to this and can be applied to systems for various purposes. For example, the delivery management server 11 can also be applied to a system that uses electric vehicles to collect and deliver packages, provide door-to-door sales, and provide door-to-door repair services. In short, the delivery management server 11 of the present disclosure may be a device that, when it receives a travel request that includes one or more destinations and requests that an electric vehicle travel via the destinations, determines a route for the electric vehicle that passes via the destinations included in the travel request based on the logistics quality of the travel area.

[0165] The above-described embodiment can be arbitrarily combined with the above-described modified examples, and the above-described modified examples can also be arbitrarily combined with each other.

[0166] 10 Delivery system 11 Delivery management server 12, 12A, 12B, 12C Delivery station system 14 Network 110 Delivery request receiving unit 111 SBOM acquisition unit 112 Usage record acquisition unit 113 Review acquisition unit 114 Logistics quality determination unit 115 Logistics quality information database unit 116 Map information storage unit 117 Route determination unit 118 Route information output unit 119 Delivery station reliability storage unit 120 Power tightness storage unit 121 Station management device 122 Charging station 123 EV vehicle management device 13A1, 13A2 EV vehicles 13B1 to 13B3 EV vehicles 13C1, 13C2 EV vehicles 201 Processor 202 ROM 203 RAM 204 Communication I / F unit AR1 to AR3 Delivery area DP3-1 to DP3-3 Delivery destination DR, DR10, DR20 Delivery route DR1 to DR5 Route DR11 to DR14 Route DR21 to DR25 Route DSTB, DSTC Delivery station EVCHG Charging station SR Shortest delivery route

Claims

1. A route determination method comprising: a travel request receiving step of receiving a travel request that includes one or more destinations and requests that an electric vehicle travel via the one or more destinations; and a route determination step of determining a route for the electric vehicle that passes via the one or more destinations included in the travel request based on logistics quality information that indicates the degree of quality of logistics in an area to which the one or more destinations included in the travel request belong.

2. The route determination method according to claim 1, wherein the route determination step, when the degree of quality indicated by the logistics quality information of a first area indicating the area to which the one or more destinations included in the travel request belong is equal to or greater than a reference value, determines a route for the electric vehicle that passes through a traveling station that manages the travel of the electric vehicle in the first area and the destination included in the travel request; and when the degree of quality indicated by the logistics quality information of the first area is less than a reference value, selects a second area from areas adjacent to the first area, the degree of quality indicated by the logistics quality information of which is equal to or greater than the reference value, and determines a route for the electric vehicle that passes through the traveling station that manages the travel of the electric vehicle in the second area and the destination included in the travel request.

3. The route determination method according to claim 2, further comprising an acquisition step of acquiring the logistics quality information from a storage unit that stores the logistics quality information for each region.

4. The route determination method described in claim 2, wherein the logistics quality information includes traveling station reliability information indicating the reliability of the traveling station and pressure level information indicating the degree of pressure on electricity demand in the area, and the route determination step determines whether the level of quality indicated by the logistics quality information is equal to or higher than the reference value depending on a combination of the traveling station reliability information and the pressure level information.

5. The route determination method according to claim 1, wherein the logistics quality information includes traveling station reliability information indicating the reliability of a traveling station and pressure level information indicating the degree of pressure in demand for electricity in a region, and when the degree of quality indicated by the logistics quality information of a first region indicating the region to which the destination included in the traveling request belongs is equal to or greater than a reference value, a route for the electric vehicle is determined that passes through a traveling station that manages the traveling of the electric vehicle in the first region and the one or more destinations included in the traveling request, and when the pressure level information exceeds the reference value corresponding to the pressure level information, even if the traveling station reliability information is less than the reference value corresponding to the traveling station reliability information, based on the logistics quality information of the first region.

6. The route determination method according to claim 1, further comprising a route information output step of outputting route information indicating the route of the electric vehicle determined by the route determination step.

7. The route determination method according to claim 1, wherein the route determination step determines a shorter route from among the candidate routes as the route for the electric vehicle.

8. A route determination device comprising: a travel request receiving unit that receives a travel request that includes one or more destinations and requests that an electric vehicle travel via said one or more destinations; and a route determination unit that determines a route for said electric vehicle that passes via said one or more destinations included in said travel request based on logistics quality information that indicates the degree of quality of logistics in the area to which said one or more destinations included in said travel request belong.

9. The route determination device according to claim 8, wherein, when the degree of quality indicated by the logistics quality information of a first area indicating an area to which the one or more destinations included in the travel request belong is equal to or greater than a reference value, the route determination unit determines a route for the electric vehicle that passes through a traveling station that manages the travel of the electric vehicle in the first area and the destination included in the travel request; and when the degree of quality indicated by the logistics quality information of the first area is less than a reference value, selects a second area from areas adjacent to the first area in which the degree of quality indicated by the logistics quality information is equal to or greater than the reference value, and determines a route for the electric vehicle that passes through the traveling station that manages the travel of the electric vehicle in the second area and the destination included in the travel request.

10. The route determination device described in claim 9, wherein the logistics quality information includes traveling station reliability information indicating the reliability of a traveling station and pressure level information indicating the degree of pressure on electricity demand in the area, and the route determination unit determines whether the level of quality indicated by the logistics quality information is equal to or higher than the reference value depending on the combination of the traveling station reliability information and the pressure level information.

11. The route determination device described in claim 8, wherein the logistics quality information includes traveling station reliability information indicating the reliability of a traveling station and pressure level information indicating the degree of pressure in demand for electricity in an area, and the route determination unit determines a route for the electric vehicle that passes through a traveling station that manages the traveling of the electric vehicle in the first area and the one or more destinations included in the traveling request when the degree of quality indicated by the logistics quality information of a first area indicating the area to which the destination included in the traveling request belongs is equal to or greater than a reference value, and determines a route for the electric vehicle that passes through a charging station in the first area and the one or more destinations included in the traveling request based on the logistics quality information of the first area when the pressure level information exceeds the reference value corresponding to the pressure level information even if the traveling station reliability information is less than the reference value corresponding to the traveling station reliability information.

12. A program for controlling a route determination device that determines the route of an electric vehicle by a computer, the program causing the computer to function as: a travel request receiving unit that receives a travel request that includes one or more destinations and requests that an electric vehicle travel via said one or more destinations; and a route determination unit that determines the route of the electric vehicle that passes through said one or more destinations included in said travel request based on logistics quality information that indicates the degree of quality of logistics in the area to which said one or more destinations included in said travel request belong.

13. The program described in claim 12, wherein the route determination unit determines a route for the electric vehicle that passes through a traveling station that manages the traveling of the electric vehicle in the first area and the destination included in the traveling request when the degree of quality indicated by the logistics quality information of a first area indicating the area to which the one or more destinations included in the traveling request belong is equal to or greater than a reference value, and selects a second area from areas adjacent to the first area where the degree of quality indicated by the logistics quality information is equal to or greater than the reference value, and determines a route for the electric vehicle that passes through the traveling station that manages the traveling of the electric vehicle in the second area and the destination included in the traveling request when the degree of quality indicated by the logistics quality information of the first area is less than a reference value.

14. The program described in claim 12, wherein the logistics quality information includes traveling station reliability information indicating the reliability of a traveling station and pressure level information indicating the degree of pressure in demand for electricity in a region, and causes the route determination unit to determine a route for the electric vehicle that passes through a traveling station that manages the traveling of the electric vehicle in the first region and the one or more destinations included in the traveling request when the degree of quality indicated by the logistics quality information of a first region indicating the region to which the destination included in the traveling request belongs is equal to or greater than a reference value, and determines a route for the electric vehicle that passes through a charging station in the first region and the one or more destinations included in the traveling request when the pressure level information exceeds the reference value corresponding to the pressure level information even if the traveling station reliability information is less than the reference value corresponding to the traveling station reliability information, based on the logistics quality information of the first region.

Citation Information

Patent Citations

  • Route search device and computer program

    JP2013242198A

  • search system

    JP5903129B2

  • Route guidance device, route guidance method, and program

    JP6894575B2

  • Autonomous driving control system and method of vehicle

    US20210370974A1