Relief Management Device

Abstract

Provided is a remedy management server capable of efficiently remedying a facility by means of a remedy vehicle. An EV data reception unit 103 receives EV data from each EV 200. A remedy facility determination unit 104 acquires a storage location of a remedy vehicle and the number of remedy vehicles. Further, a remedy facility information reception unit 102 receives remedy facility information from each of a plurality of remedy facilities 3200, and the remedy facility determination unit 104 acquires the remedy facility information. A power supply remedy schedule determination unit 105 functions as a derivation unit for deriving a remedy pattern, and derives, on the basis of the position of a remedy facility 300, a remedy pattern that indicates a movement path for the EV 200 as the remedy vehicle to remedy the remedy facility 300. A power supply remedy schedule transmission unit 106 transmits the remedy pattern to the driver of the EV 200.

Description

[Technical Field]

[0001] The present invention relates to a relief management device that performs power supply relief for a relief facility. [Background technology]

[0002] Electric vehicles (EVs) are generally viewed as simply automobiles, but in recent years, they have come to be viewed as distributed power sources and are expected to be used as a disaster prevention measure.

[0003] The main use is to rush an EV to a facility when a power outage occurs due to a disaster or other event, and supply power from the EV's battery (storage battery), thereby acting as a power backup. Conventionally, batteries (storage batteries) have also been used as emergency power sources in the event of a power outage.

[0004] Patent Document 1 describes that an electric vehicle (EV) ensures the discharge capacity required for the load device, then calculates the dischargeable capacity that can be discharged from the backup battery, and when there is a request for power supply from outside, discharges the backup battery by the dischargeable capacity. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2020-96416 Summary of the Invention [Problem to be solved by the invention]

[0006] When there are multiple EVs and multiple relief facilities, there are multiple combinations of EVs and relief facilities, and multiple relief routes, so it is necessary to consider combinations that enable appropriate relief to the relief facilities. The technology described in Patent Document 1 does not clarify how such multiple EVs can provide relief to multiple relief facilities.

[0007] In order to solve the above-mentioned problems, an object of the present invention is to provide a relief management device that can efficiently carry out facility relief using a relief vehicle. [Means for solving the problem]

[0008] The rescue management device according to the present disclosure comprises a rescue vehicle information acquisition unit that acquires the storage location of rescue vehicles and the number of rescue vehicles, a rescue information acquisition unit that acquires information on multiple rescue facilities, a derivation unit that derives a rescue pattern indicating the travel route that the rescue vehicle will take to rescue to the rescue facility based on the location of the rescue facility, and a notification unit that notifies the rescue pattern. [Effects of the Invention]

[0009] According to the present invention, the facility can be efficiently rescued by a rescue vehicle. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating a relief management system including a relief management server 100 according to a first embodiment of the present disclosure. [Figure 2] FIG. 1 is a schematic diagram illustrating a power supply rescue plan. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a relief management server 100. [Figure 4] 10 is a flowchart showing the operation of the relief management server 100. [Figure 5] 10 is a flowchart showing a process for calculating the shortest travel route in the EV 200. [Figure 6]10 is an explanatory diagram showing the determination of relief facilities 300, the determination of travel routes, and the allocation of EVs 200. FIG. [Figure 7] FIG. 2 is a block diagram showing a functional configuration of a relief management server 100a of the present disclosure. [Figure 8] 10 is a flowchart showing the operation of the relief management server 100a of the second embodiment. [Figure 9] 10 is a flowchart showing details of processing S106a. [Figure 10] FIG. 10 is a schematic diagram showing travel time and charging time. [Figure 11] 1 is a diagram illustrating an example of a hardware configuration of a relief management server 100 according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] The present disclosure will be described with reference to the accompanying drawings. Whenever possible, the same parts are designated by the same reference numerals and redundant description will be omitted.

[0012] FIG. 1 is a diagram illustrating a relief management system including a relief management server 100 according to a first embodiment of the present disclosure. As shown in the figure, the relief management server 100 manages EVs 200 in EV storage locations and controls relief facilities 300 to be rescued. In the present disclosure, there are multiple EVs 200 and multiple relief facilities 300. The relief facilities 300 are, for example, base stations that constitute a mobile communication network.

[0013] The relief management server 100 acquires EV data from EVs 200 in an EV storage location, including the current location (EV storage location), power consumption, lower discharge limit SOC, vehicle battery capacity, and remaining battery power. The relief management server 100 also acquires relief facility information from the relief facility, including rated power consumption, battery information (SOC, battery capacity), and location information. While FIG. 1 illustrates one storage location, this is not a limitation. There may be multiple storage locations.

[0014] Based on the EV data and relief facility information, the relief management server 100 calculates the number of EVs 200, divides the relief facilities 300 into several groups, and transmits a power rescue schedule for each group to each EV 200. This power rescue schedule includes the group information, the rescue pattern (travel route) for each group, and the EVs 200 assigned to the group. The drivers of the EVs 200 view this power rescue schedule and rescue the relief facilities 300 according to the rescue route.

[0015] 2 is a schematic diagram showing a power supply rescue plan. As shown in the figure, this schematic diagram shows groups of rescue facilities, rescue patterns, and EVs 200 allocated to each group.

[0016] In the figure, the relief management server 100 divides the relief facilities 300 into three groups: relief facilities A, B, and C; relief facilities D, E, and F; and relief facilities G, H, I, and J. Then, a relief route is determined for each group. The relief management server 100 then assigns EVs 200 to each relief pattern. In FIG. 2, EV1 is assigned to the group of relief facilities A, B, and C, EV2 is assigned to relief facilities D, E, and F, and EV3 is assigned to relief facilities G, H, I, and J. In FIG. 2, a relief pattern indicating the travel route for EVs 200 to travel to the relief facilities indicates, for example, a travel route that passes through relief facility A, relief facility B, and relief facility C in that order.

[0017] As shown in FIG. 2, there are three EVs 200 and ten relief facilities 300, and the relief management server 100 derives three relief patterns.

[0018] 3 is a block diagram showing the functional configuration of the relief management server 100. As shown in the figure, the relief management server 100 includes a relief request receiving unit 101, a relief facility information receiving unit 102, an EV data receiving unit 103, a relief facility determining unit 104, a power relief schedule determining unit 105, and a power relief schedule transmitting unit 106.

[0019] The relief request receiving unit 101 is a part that receives relief requests from one or more relief facilities 300.

[0020] The relief facility information receiving unit 102 is a part that receives relief facility information from one or more relief facilities 300. The relief facility information includes identification information, rated power consumption, battery information (SOC and battery capacity), and location information of each relief facility 300. It may also include information on the priority of relief. Some of the relief facilities 300 are selected based on this priority. If relief cannot be provided for all relief facilities 300, the relief facilities 300 that cannot be rescued by the EV 200 are excluded.

[0021] EV data receiving unit 103 is a part that receives EV data from each EV 200. The EV data includes identification information of the EV 200, the current location (storage location), electricity consumption, the lower limit SOC of discharge, the vehicle storage battery capacity, and the remaining battery power.

[0022] The relief facility determination unit 104 acquires the EV storage location, the number of EVs, the battery capacity of each EV, etc. from the EV data and relief facility information, acquires information (battery information, etc.) for calculating the location and the amount of power required by the relief facility from the relief facility information, and determines groups (combinations) of multiple relief facilities 300. The number of EVs is determined by counting the identification information of the EVs 200 included in the EV data.

[0023] The power supply rescue schedule determination unit 105 determines a power supply rescue schedule based on the rescue facilities 300 of the determined group, the rescue facility information, and the EV data. The power supply rescue schedule includes groups of rescue facilities, rescue patterns (travel routes) for each group, and EVs 200 assigned to each group.

[0024] The power rescue schedule transmitting unit 106 transmits the power rescue schedule to each EV 200. For example, the driver of each EV 200 owns a mobile terminal, and the group (including the combination of rescue facilities) assigned to the driver (EV 200), the rescue pattern, and the identification information of the EV 200 for each rescue pattern are transmitted to each mobile terminal. Note that the identification information of the EV 200 is not required.

[0025] 4 is a flowchart showing the operation of the relief management server 100. When the relief request receiving unit 101 receives a relief request from each relief facility 300, it sends a request for relief facility information to each relief facility 300 that has made the relief request, and receives the relief facility information sent in response (S101). The EV data receiving unit 103 receives EV data from each EV 200 (S102). The relief facility determination unit 104 acquires the storage location and number of EVs for each EV 200 from the EV data (S103). The relief facility determination unit 104 also acquires the storage battery capacity, power cost, lower discharge limit SOC, and remaining battery power of each EV 200 from the EV data (S104). The relief facility determination unit 104 also acquires the rated power consumption of each relief facility 300 (S105).

[0026] The relief facility determination unit 104 determines the relief facilities to be provided as relief targets, and the power supply relief schedule determination unit 105 calculates the shortest route for the EV 200 to travel around the relief facilities 300 and determines the power supply relief schedule (S106).

[0027] The power rescue schedule transmitting unit 106 transmits the power rescue schedule to each EV 200 (S107).

[0028] Next, the process S106 will be described. FIG. 5 is a flowchart showing the process of calculating the shortest travel route for the EVs 200. The relief facility determination unit 104 derives groups of relief facilities 300 to be rescued, i.e., which EVs 200 will rescue which relief facilities 300 (S201). Then, the relief facility determination unit 104 derives rescue patterns indicating the travel routes of the EVs 200 for each group (S202). The relief facility determination unit 104 sorts the groups in order of the shortest travel routes for the EVs 200 (S203).

[0029] The relief facility determination unit 104 assigns EVs 200 to the group with the shortest travel route in order of the relief pattern and determines whether any of the EVs 200 will run out of power (S204). If the relief facility determination unit 104 determines that all groups contain EVs 200 that will run out of power (S205: YES), it removes one relief facility 300 according to a predetermined condition and regroups the relief facilities 300 (S206). For example, the number of relief facilities may be reduced based on priority, or the number of relief facilities that are just one away may be reduced based on their location. Furthermore, priority may be given to relief facilities that require excessive power, or conversely, such relief facilities may be removed.

[0030] If the relief facility determination unit 104 determines that there is a group in which none of the EVs 200 will run out of power (S205: NO), it determines a combination of the relief pattern for that group and the EVs 200, and determines a power relief schedule (S207). If there are multiple groups in which none of the EVs 200 will run out of power, it may determine any group, or it may use the first group determined.

[0031] FIG. 6 is an explanatory diagram showing the determination of relief facilities 300, the determination of travel routes, and the allocation of EVs 200. For ease of explanation, it is assumed that there are relief facilities A, B, C, and D. FIG. 6(a) is a diagram showing grouping of relief facilities 300. The relief facility determination unit 104 determines combination patterns of relief facilities and performs grouping. For example, it is assumed that the relief facility determination unit 104 has divided the combination patterns of relief facilities 300 into groups G1 to Gx.

[0032] 6(b) is a diagram showing rescue patterns (travel routes) derived for each combination (group) of rescue facilities 300. The power rescue schedule determination unit 105 derives travel routes that pass through multiple rescue facilities 300. For example, for a group of rescue facility A and rescue facility B, a route R1 that passes through both of them is derived. The power rescue schedule determination unit 105 also derives travel routes for the other rescue facilities 300.

[0033] Figure 6(c) is a diagram showing the travel distance L obtained by adding up the route R derived in Figure 6(b) for each facility group. Here, distance L101 is the sum of distances L1 to L3 for routes R1 to R3. Here, distance L101 is the shortest distance.

[0034] 6(d) shows the allocation of EVs 200 to each route R. For example, the power supply recovery schedule determination unit 105 allocates EV1 to route R1, EV2 to route R2, and EV3 to route R3. Here, the power supply recovery schedule determination unit 105 determines the possibility that each EV 200 will run out of power.

[0035] For example, power supply rescue schedule determination unit 105 determines whether EV 200 will run out of power midway based on the travel distance of EV 200, the battery capacity of EV 200, the electricity cost of EV 200, and the charging power from EV 200 to rescue facility 300.

[0036] The power supply rescue schedule determination unit 105 determines whether the amount of power required for rescue to the rescue facility 300 and for travel is greater than the amount of power stored in the battery of the EV 200, thereby determining whether the EV 200 will run out of power midway.

[0037] The power supply rescue schedule determination unit 105 calculates the amount of power required for the EV 200 to travel by dividing the travel distance of the EV 200 by the power cost. The power supply rescue schedule determination unit 105 also acquires the SOCi and battery capacity Hi of the storage battery of the rescue facility from the rescue facility information. The amount of charged power is calculated as "battery capacity Hi x F - SOCi x battery capacity Hi". i indicates the rescue facility. F indicates the charging rate and is an arbitrary value, for example, 85%. The power supply rescue schedule determination unit 105 then calculates the power shortage determination condition, Remaining battery power stored in the EV200 battery > EV200's moving power amount + charging power amount Determine whether it will be.

[0038] If the power shortage determination condition is met (if the remaining battery charge of EV 200 > the amount of power used to move EV 200 + the amount of charging power), power supply recovery schedule determination unit 105 determines that EV 200 will not run out of power. On the other hand, if the power shortage determination condition is not met, it is determined that EV 200 will run out of power during movement, and as shown in Figure 6(e), power supply recovery schedule determination unit 105 swaps the travel route and EV 200 and determines the possibility of running out of power again.

[0039] If it is determined that the vehicle will run out of power in all patterns (S205: YES), the relief facility determination unit 104 removes one relief facility based on a predetermined priority or the like, and again derives a group of relief facilities (S201).

[0040] Next, a second embodiment will be described. In this second embodiment, a mechanism is disclosed in which an EV 200 rescues a relief facility 300 two or more times depending on the scale of a disaster. FIG. 7 is a block diagram showing the functional configuration of a relief management server 100a of the present disclosure. This differs from the relief management server 100a in the first embodiment in that it includes a disaster scale receiving unit 101a.

[0041] The disaster scale receiving unit 101a receives the disaster scale issued by the national or prefectural government. The national or prefectural government has a disaster scale management server, which transmits the disaster scale to the relief management server 100a when a disaster occurs.

[0042] 8 is a flowchart showing the operation of the relief management server 100a of the second embodiment. Processes S101 to S105 are the same as those of the first embodiment (FIG. 4), and the relief management server 100a receives relief facility information, EV data, etc. The disaster scale receiving unit 101a receives disaster scale information (S105a). Then, the power rescue schedule determination unit 105 determines a power rescue schedule according to the disaster scale (S106a). The power rescue schedule transmitting unit 106 transmits the power rescue schedule to the EV 200 (S106).

[0043] FIG. 9 shows details of step S106a. This flowchart differs from the flowchart in FIG. 5 in that steps S207a and S207b have been added. In step S207 of FIG. 5 in the first embodiment, an arbitrary combination of multiple travel routes and EV 200 assignments was determined. Here, however, the power supply rescue schedule determination unit 105 determines a combination of the determined combinations of EV 200 and rescue patterns (S207a) that will not deplete the storage batteries of the rescue facilities 300 in the second loop (S207b). If no combination exists that will not deplete the storage batteries of the rescue facilities 300, the number of rescue facilities may be reduced by one (S206). In this case, it is possible to reduce the number of rescue facilities that will be depleted.

[0044] That is, for each group, the power supply rescue schedule determination unit 105 determines whether the storage batteries of the rescue facilities 300 will be depleted in the time obtained by adding up the charging time for each rescue facility 300, the travel time of the EVs 200, and the charging time for the EVs 200 (for example, one hour).

[0045] Fig. 10 is a schematic diagram showing the travel time and charging time of EV1. As shown in Fig. 10(a), EV1 travels to relief facilities A to C while charging. It takes time T10, which is the sum of travel times T11 to T14, for EV1 to return to the storage location, and time T0, which is the sum of charging times T1 to T3 for charging at each relief facility 300. Furthermore, it takes time T4 to charge EV1 at the storage location.

[0046] Then, it is determined whether or not a power outage will occur for the time calculated by adding up the charging times T2 and T3, the travel times T11 to T13, and the travel time T14 (see FIG. 10(b)). A similar determination is made for the other relief facilities B and C. The determination of whether or not a power outage will occur is made based on the rated power consumption and storage battery capacity of each relief facility. That is, the operating time of the storage battery at the relief facility 300 is calculated from the rated power consumption and the remaining capacity of the storage battery, and it is determined whether or not the relief facility 300 will continue to operate based on the operating time and the time when the EV200 returns to the relief facility 300.

[0047] The charge amount of the storage batteries at the relief facilities 300 is set to, for example, 85% of the total capacity of each storage battery, but other values ​​are also acceptable. The batteries of the EVs 200 are fully charged at the storage locations. To prevent the EVs 200 from running out of power on the second and subsequent loops, the batteries of the EVs 200 must be charged to a power exceeding the charge amount for the relief facilities 300, based on the travel time, charging time at each relief facility, charging time for the EVs 200 at the storage locations, and the rated power consumption of each relief facility 300.

[0048] Next, the effects of the relief management server 100 and the relief management server 100a functioning as the relief management device of the present disclosure will be described. The EV data receiving unit 103 receives EV data from each of the EVs 200, and the relief facility determination unit 104 (relief vehicle information acquisition unit) acquires the storage locations of the multiple relief vehicles and the number of relief vehicles. The relief facility information receiving unit 102 receives relief facility information from each of the multiple relief facilities 3200, and the relief facility determination unit 104 (relief information acquisition unit) acquires the relief facility information. The power rescue schedule determination unit 105 functions as a derivation unit that derives a rescue pattern, and derives a rescue pattern indicating a travel route for the EV 200, which is the relief vehicle, to rescue the EV 200 to the relief facility 300 based on the location of the multiple relief facilities 300. The power rescue schedule transmission unit 106 (notification unit) transmits the rescue pattern to the driver of the EV 200.

[0049] This configuration makes it possible to determine rescue patterns for multiple EVs 200 and multiple rescue facilities. In this disclosure, the rescue vehicle is an electric vehicle with a battery, and the rescue facility 300 receives rescue by being charged by the battery of the EV 200. Note that this system can also be applied to other vehicles, such as PHEVs (plug-in hybrids) or HEVs, using their batteries. In addition to electric power supply, this system can also be applied to rescue using fuels such as gasoline, which are commonly known as energy sources.

[0050] In the present disclosure, the rescue pattern is defined so that at least one EV 200 rescues one rescue facility 300 .

[0051] The power supply rescue schedule determination unit 105 classifies the multiple rescue facilities 300 according to the number of EVs 200 to be rescued (number of rescue vehicles), derives multiple combinations of the rescue facilities 300, and derives a rescue pattern for each combination. Then, from among the multiple rescue patterns determined for each combination of the rescue facilities 300, the power supply rescue schedule determination unit 105 determines one rescue pattern that provides the shortest travel route for all EVs 200.

[0052] According to this configuration, a rescue pattern that shortens the time can be determined, allowing for efficient rescue and reducing the possibility that the operation of the rescue facility 300 will be stopped.

[0053] Furthermore, the power supply rescue schedule determination unit 105 assigns one EV 200 to each of a plurality of travel routes of one rescue pattern, and if there is a possibility that the EV 200 assigned to the travel route will stop midway due to a lack of power or the like, the power supply rescue schedule determination unit 105 reallocates the EV 200 in another rescue pattern.

[0054] Furthermore, if the power supply rescue schedule determination unit 105 cannot allocate EVs 200 to all of the rescue patterns, it excludes certain rescue facilities based on priorities from the multiple rescue facilities 300. These priorities are set in advance and are included in the rescue facility information.

[0055] In the relief management server 100a in the second embodiment, the disaster scale receiving unit 101a receives the scale of the disaster that occurred at the time of relief, and the power relief schedule determining unit 105 determines a relief pattern based on the disaster scale.

[0056] This makes it possible to determine an appropriate relief pattern based on the scale of the disaster announced by the government or other organizations.

[0057] In addition, in the relief management server 100a, the power relief schedule determination unit 105 calculates the number of relief loops based on the scale of the disaster.

[0058] Therefore, for example, in the case of a major disaster, the relief facility 300 restoration Since there may be delays in the delivery of the relief facility, the EV 200 can be dispatched to the relief facility more than once, thereby keeping the relief facility 300 operational.

[0059] Furthermore, in the relief management server 100a of the present disclosure, the power relief schedule determination unit 105 determines a relief pattern that does not stop the operation of the relief facility 300. The phrase "not stopping the operation of the relief facility" means, for example, that the relief facility 300 is operating until the EV 200 returns to the same relief facility 300 again.

[0060] This will prevent situations where relief through EV200 cannot be provided in time. The rescue management device of the present disclosure has the following configuration. [1] a relief vehicle information acquisition unit that acquires storage locations of relief vehicles and the number of relief vehicles; a relief information acquisition unit that acquires information on a plurality of relief facilities; a derivation unit that derives a rescue pattern indicating a travel route for the rescue vehicle to take to the rescue facility based on the location of the rescue facility; a notification unit that notifies the relief pattern; A relief management device comprising: [2] the rescue vehicle is an electric vehicle having a battery, The relief facility receives relief by receiving charge from the battery of the relief vehicle. [1] The relief management device according to [1]. [3] The rescue pattern is defined so that at least one rescue vehicle rescues from one rescue facility. A relief management device according to [1] or [2]. [4] The lead-out portion is classifying the plurality of relief facilities into groups according to the number of relief vehicles required for the relief; deriving a plurality of combinations of relief facilities; and deriving a relief pattern for each combination; determining one rescue pattern that provides the shortest travel route for all rescue vehicles from among a plurality of rescue patterns defined for each combination of the rescue facilities; A relief management device according to any one of [1] to [3]. [5] the derivation unit assigns one relief vehicle to each of a plurality of movement routes of the one relief pattern; If there is a possibility that the relief vehicle assigned to the travel route will stop along the way, the relief vehicle is reallocated in another relief pattern. [4] The relief management device according to [4]. [6] and when the deriving unit cannot assign rescue vehicles to all of the rescue patterns, excluding a predetermined rescue facility from the plurality of rescue facilities. [5] The relief management device according to [5]. [7] A receiving unit is further provided to receive the scale of the disaster that has occurred at the time of relief, the derivation unit determines a relief pattern based on the disaster scale. A relief management device according to any one of [1] to [6]. [8] the derivation unit calculates the number of rescue loops based on the disaster scale. [7] The relief management device according to [7]. [9] The lead-out portion is determining a relief pattern that will not result in the suspension of operation of the relief facility; [8] The relief management device according to [8].

[10] The operation of the relief facility is not stopped if the relief facility is in operation until the relief vehicle returns to the same relief facility. [9] The relief management device according to [9].

[0061] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0062] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0063] For example, the relief management server 100 and the relief management server 100a (hereinafter referred to as the relief management server 100 unless otherwise specified) according to an embodiment of the present disclosure may function as a computer that performs processing of the relief management method of the present disclosure. Fig. 11 is a diagram showing an example of the hardware configuration of the relief management server 100 according to an embodiment of the present disclosure. The relief management server 100 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0064] In the following description, the term "device" can be read as a circuit, a device, a unit, etc. The hardware configuration of the relief management server 100 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

[0065] Each function of the rescue management server 100 is realized by loading specified software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and storage 1003.

[0066] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned relief facility determination unit 104 and power relief schedule determination unit 105 may be realized by the processor 1001.

[0067] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the relief facility determination unit 104 and the power relief schedule determination unit 105 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0068] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a rescue management method according to an embodiment of the present disclosure.

[0069] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0070] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, or communication module. The communication device 1004 may include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the relief request receiving unit 101, the relief facility information receiving unit 102, the EV data receiving unit 103, the power relief schedule determining unit 105, and the disaster scale receiving unit 101a may be implemented by the communication device 1004. The transmission unit and the reception unit of the communication device 1004 may be physically or logically separated.

[0071] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0072] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0073] The relief management server 100 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0074] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0075] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0076] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0077] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0078] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0079] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0080] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0081] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0082] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0083] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0084] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0085] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0086] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0087] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0088] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0089] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0090] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0091] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0092] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0093] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0094] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Explanation of symbols]

[0095] 100...relief management server, 100a...relief management server, 101...relief request receiving unit, 101a...disaster scale receiving unit, 102...relief facility information receiving unit, 103...EV data receiving unit, 104...relief facility determination unit, 105...power relief schedule determination unit, 106...power relief schedule transmitting unit.

Claims

1. a relief vehicle information acquisition unit that acquires storage locations of relief vehicles and the number of relief vehicles; a relief information acquisition unit that acquires information on a plurality of relief facilities; a derivation unit that derives a rescue pattern indicating a travel route for the rescue vehicle to take to the rescue facility based on the location of the rescue facility; a notification unit that notifies the relief pattern; Equipped with The lead-out portion is classifying the plurality of relief facilities indicated in the plurality of relief facility information into the number of relief vehicles to be used for relief, deriving a plurality of combinations of relief facilities, and deriving a relief pattern for each combination; determining one rescue pattern that provides the shortest travel route for all rescue vehicles from among a plurality of rescue patterns defined for each combination of the rescue facilities; Relief management device.

2. the rescue vehicle is an electric vehicle having a battery, The relief facility receives relief by receiving charge from the battery of the relief vehicle. The rescue management device according to claim 1 .

3. The rescue pattern is defined so that at least one rescue vehicle rescues from one rescue facility. The rescue management device according to claim 1 .

4. the derivation unit assigns one relief vehicle to each of a plurality of movement routes of the one relief pattern; If there is a possibility that the relief vehicle assigned to the travel route will stop along the way, the relief vehicle is reallocated in another relief pattern. The rescue management device according to claim 1 .

5. and when the deriving unit cannot assign rescue vehicles to all of the rescue patterns, excluding a predetermined rescue facility from the plurality of rescue facilities. The rescue management device according to claim 4 .

6. A rescue vehicle information acquisition unit that acquires the storage locations of rescue vehicles and the number of rescue vehicles; a relief information acquisition unit that acquires information on a plurality of relief facilities; a derivation unit that derives a rescue pattern indicating a travel route for the rescue vehicle to take to the rescue facility based on the location of the rescue facility; a notification unit that notifies the relief pattern; a receiving unit that receives the scale of the disaster that has occurred at the time of relief, the derivation unit determines a relief pattern based on the locations of the relief facilities and the scale of the disaster. Relief management device.

7. The derivation unit calculates the number of rescue loops based on the disaster scale, The number of rescue loops indicates the number of times rescue has been repeated, where one rescue loop is defined as a trip in which the rescue vehicle has gone to all or some of the rescue facilities to rescue and returned to the storage location for charging. The rescue management device according to claim 6.

8. The lead-out portion is determining a relief pattern that will not result in the suspension of operation of the relief facility; The rescue management device according to claim 7.

9. The operation of the relief facility is not stopped if the relief facility is in operation until the relief vehicle returns to the same relief facility. The rescue management device according to claim 8 .

Images