Scheduling device, control method, and control program
By scheduling the functions of the vehicle control device through a scheduling device, optimizing the execution start time and cycle, the problem of power consumption caused by the parallel execution of multiple applications is solved, and efficient power management of the vehicle control device is achieved.
Patent Information
- Application Number
- CN202480021660.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-28
- Filing Date
- 2024-03-21
- Publication Date
- 2025-11-18
AI Technical Summary
Existing technologies shorten the sleep period when multiple applications are executed in parallel, making it impossible to effectively suppress the power consumption of vehicle control devices.
The scheduling device schedules the functions of multiple vehicle control devices, obtains and determines the execution start time and cycle with minimum power consumption, and sets the execution cycle and start time of each vehicle control device to optimize power consumption.
Even with the increase in parallel execution functions, the total power consumption of the vehicle control device can be effectively suppressed, achieving efficient utilization of power resources.
Smart Images

Figure CN120981795A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to a scheduling device, a control method, and a control program. This application claims priority based on Japanese Application No. 2023-051830 filed on March 28, 2023, and incorporates by reference the entire disclosure of the above-mentioned Japanese application. BACKGROUND
[0002] A vehicle is equipped with various in-vehicle devices such as a control system ECU (Electronic Control Unit) that controls an engine, a transmission, and the like, a vehicle system ECU that controls a headlamp, a power window, and the like, an information system ECU such as a navigation device, a multimedia device, and the like.
[0003] In Patent Literature 1, a sleep control system for a vehicle is disclosed, in which even in a case where sleep periods differ among a plurality of applications, information related to a requested sleep period is individually acquired from each application by a sleep control information acquisition unit, and further, a common period included in the acquired requested sleep periods is found as an effective sleep period by an effective sleep period calculation unit, and using the effective sleep period, control of sleep / wakeup of a hardware control subject is performed.
[0004] PRIOR ART DOCUMENTS PATENT LITERATURE Patent Literature 1: Japanese Patent Application Publication No. 2006-151007 SUMMARY
[0005] A scheduling device according to one embodiment of the present disclosure is a scheduling device that schedules functions performed by a plurality of in-vehicle control devices capable of communicating with each other via a communication bus, the scheduling device including: an acquisition unit that acquires first information and second information, the first information being used to determine a first execution start timing and a first execution period, the second information being used to determine a second execution start timing and a second execution period, the first execution start timing being a timing at which a first function performed by a first in-vehicle control device and a second in-vehicle control device is started, the first execution period being a period during which the first function is executed, the second execution start timing being a timing at which a second function performed by the first in-vehicle control device and a third in-vehicle control device is started, the second execution period being a period during which the second function is executed; and a determination unit that determines the first execution start timing, the first execution period, the second execution start timing, and the second execution period in which total consumed power of the first in-vehicle control device, the second in-vehicle control device, and the third in-vehicle control device becomes the smallest, based on the first information and the second information
[0006] This disclosure can be implemented not only as a scheduling device having the aforementioned characteristic structure, a control method that takes the characteristic processing in the scheduling device as a step, and a control program for causing the vehicle control device to execute the characteristic processing, but also as a part or all of the vehicle control device as a semiconductor integrated circuit. Attached Figure Description
[0007] Figure 1 This is a block diagram illustrating an example of the structure of an onboard system including the dispatching device of Embodiment 1. Figure 2 This is a block diagram illustrating an example of the structure of the GW in Implementation Method 1. Figure 3 This is a block diagram illustrating an example of the structure of the ECU in Embodiment 1. Figure 4 This is an example of a cluster table that indicates which cluster an ECU belongs to. Figure 5 This is a functional block diagram illustrating an example of the function of GW in Implementation Method 1. Figure 6 This is a diagram illustrating an example of the information used to determine the start time and execution cycle of execution. Figure 7 This is a diagram representing the actions when two functions are executed in parallel. Figure 8 It is a diagram that represents the actions when two functions are performed simultaneously in time. Figure 9 It is a diagram representing the actions of two functions executed in different execution cycles. Figure 10 It is a diagram that represents two functions executing simultaneously in time with the same execution cycle. Figure 11 This is a flowchart illustrating an example of the operation of the scheduling device in Implementation 1. Figure 12 It is a flowchart of an example of a routine whose execution start time and execution cycle are determined. Figure 13 This is a functional block diagram illustrating an example of the function of the scheduling device in Implementation 2. Figure 14 This is a flowchart illustrating an example of the operation of the scheduling device in Implementation Method 2. Figure 15 This is a diagram representing an example of execution condition information that includes limiting information. Figure 16 This is a diagram illustrating an example of the execution order of the first to third functions. Figure 17 This is a diagram illustrating an example of the execution order of the first to third functions. Figure 18 This is a flowchart illustrating an example of the operation of the scheduling device in Implementation Method 3. Detailed Implementation
[0008] [The problem the invention aims to solve]
[0009] However, the sleep control system for automobiles in Patent Document 1 sets the period shared by the sleep requests of each application as the effective sleep period. If more applications are executed in parallel, the sleep period becomes shorter, which leads to the problem that power consumption cannot be suppressed.
[0010] [Invention Effects]
[0011] According to this disclosure, even with an increase in the number of functions executed in parallel, it is possible to suppress the power consumption of the vehicle control device.
[0012] <Summary of embodiments of this disclosure>
[0013] The following is a summary description of the embodiments of this disclosure.
[0014] (1) The scheduling device of this embodiment schedules functions executed by multiple vehicle control devices capable of communicating with each other via a communication bus. The scheduling device includes: an acquisition unit that acquires first information and second information, wherein the first information is used to determine a first execution start time and a first execution period, and the second information is used to determine a second execution start time and a second execution period. The first execution start time is the time at which a first function is started to be executed by a first vehicle control device and a second vehicle control device, the first execution period is the period during which the first function is executed, the second execution start time is the time at which a second function is started to be executed by a first vehicle control device and a third vehicle control device, and the second execution period is the period during which the second function is executed; and a determination unit that, based on the first information and the second information, determines the first execution start time, the first execution period, the second execution start time, and the second execution period to minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device. Therefore, even if more functions are executed in parallel, the power consumption of the vehicle control devices can be suppressed.
[0015] (2) In (1) above, the scheduling device further includes a setting unit that sets the first execution start time and the first execution cycle determined by the decision unit to the first vehicle control device and the second vehicle control device, and sets the second execution start time and the second execution cycle determined by the decision unit to the first vehicle control device and the third vehicle control device. Therefore, even if more functions are executed in parallel, the power consumption of the vehicle control device can be suppressed.
[0016] (3) In (1) or (2) above, the decision-making unit determines a first setting range based on the first information, determines the first execution start time and the first execution cycle based on the first setting range, and determines a second setting range based on the second information, determines the second execution start time and the second execution cycle based on the second setting range. The first setting range is the range within which the first execution cycle should be limited, and the second setting range is the range within which the second execution cycle should be limited. Thus, the execution cycle can be determined within the range within which the execution cycle of the function should be limited, and the first and second functions can be executed in an overlapping manner. As a result, even if more functions are executed in parallel, the power consumption of the vehicle control device can be suppressed.
[0017] (4) In (3) above, the first setting range is determined based on the first cycle initial value and the first allowable range, and the second setting range is determined based on the second cycle initial value and the second allowable range. The first cycle initial value is the initial value of the cycle for executing the first function, the first allowable range is the range that can be changed from the first cycle initial value, the second cycle initial value is the initial value of the cycle for executing the second function, and the second allowable range is the range that can be changed from the second cycle initial value. Thus, the execution cycle can be determined based on the cycle initial value and the allowable range, and the first function and the second function can be executed in an overlapping manner. As a result, even if more functions are executed in parallel, the power consumption of the vehicle control device can be suppressed.
[0018] (5) In (4) above, the first information includes a first execution duration, which is the time from the start to the end of the first function in the first execution cycle, and the second information includes a second execution duration, which is the time from the start to the end of the second function in the second execution cycle. Thus, the first and second functions can be executed with a wide overlap, enabling flexible decision-making.
[0019] (6) In (5) above, the decision unit calculates the power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device based on the first execution duration and the second execution duration, and determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption. Thus, the total power consumption can be easily calculated.
[0020] (7) In any of (1) to (6) above, the first information includes information indicating a restriction condition limiting the execution of the first function, and the decision unit determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle by avoiding the restriction condition. Thus, even when there is a condition limiting the execution of the function, a schedule that can suppress the power consumption of the vehicle control device can be calculated.
[0021] (8) In (7) above, the limiting condition includes a condition that restricts the first function and the second function from being executed concurrently in time. Thus, even when the concurrent execution of the functions is restricted, a schedule that can suppress the power consumption of the vehicle control device can be calculated.
[0022] (9) In (6) above, the limiting conditions include at least one of the conditions related to the limitation of hardware resources used by the first function and the conditions related to the limitation of hardware resources used by the second function. Thus, even when there are limitations on the hardware resources used by the function, a scheduling table that can suppress the power consumption of the vehicle control device can be calculated.
[0023] (10) The control method of this embodiment is used by a scheduling device, which schedules the functions executed by multiple vehicle control devices that can communicate with each other via a communication bus. The control method includes the following steps: obtaining first information and second information, wherein the first information is used to determine a first execution start time and a first execution cycle, and the second information is used to determine a second execution start time and a second execution cycle, wherein the first execution start time is the time at which a first function is started by a first vehicle control device and a second vehicle control device, the first execution cycle is the cycle for executing the first function, the second execution start time is the time at which a second function is started by a first vehicle control device and a third vehicle control device, and the second execution cycle is the cycle for executing the second function; and, based on the first information and the second information, determining the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device. Thus, even if more functions are executed in parallel, the power consumption of the vehicle control devices can be suppressed.
[0024] (11) The control program of this embodiment is used by a scheduling device, which schedules the functions executed by multiple vehicle control devices that can communicate with each other via a communication bus. The control program causes a computer to perform the following steps: obtaining first information and second information, wherein the first information is used to determine a first execution start time and a first execution cycle, and the second information is used to determine a second execution start time and a second execution cycle. The first execution start time is the time at which a first function is started by a first vehicle control device and a second vehicle control device, the first execution cycle is the period during which the first function is executed, the second execution start time is the time at which a second function is started by a first vehicle control device and a third vehicle control device, and the second execution cycle is the period during which the second function is executed; and, based on the first information and the second information, determining the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device. Thus, even if more functions are executed in parallel, the power consumption of the vehicle control devices can be suppressed.
[0025] <Implementation Method 1>
[0026] [1. Details of Embodiment 1 of this disclosure]
[0027] Hereinafter, detailed descriptions of embodiments of the present disclosure will be provided with reference to the accompanying drawings. Furthermore, at least a portion of the embodiments described below may be combined in any manner.
[0028] [1-1. In-vehicle system]
[0029] Figure 1 This is a block diagram illustrating an example of the structure of an in-vehicle system including the scheduling device of Embodiment 1. The in-vehicle system 1 is mounted in a vehicle. The scheduling device schedules the execution timing of functions performed by multiple in-vehicle control devices capable of communicating with each other via a communication bus. The scheduling device is implemented, for example, as a gateway (hereinafter referred to as GW) that comprehensively controls individual in-vehicle control devices (hereinafter simply "ECUs") performing prescribed functions. A gateway is sometimes referred to as an integrated ECU, as a type of ECU. Alternatively, the scheduling device can also be implemented as an external server. Hereinafter, a gateway will be used as an example for explanation.
[0030] The vehicle system 1 in Embodiment 1 includes GW2, ECU3a, and ECU3b. The vehicle system 1 is a vehicle network consisting of ECU2, ECU3a, ECU3b, and communication cables (communication bus) connecting them. Sometimes, ECU3a and ECU3b are collectively referred to as "ECU3".
[0031] Multiple ECUs (Electronic Control Units) are located throughout the vehicle. Each ECU (Electronic Control Unit) individually controls or monitors the hardware of a particular part of the vehicle. For example, an ECU (Electronic Control Unit) may be used in the control system, body system, or information system.
[0032] GW2 is connected to each ECU3 via communication buses 12a and 12b, similar to a CAN (Controller Area Network) bus. Specifically, GW2 has communication interfaces (communication I / F) 11a and 11b. Communication I / F 11a is connected to communication bus 12a. ECU3a is connected to communication bus 12a. Communication I / F 11b is connected to communication bus 12b. ECU3b is connected to communication bus 12b. GW2 can communicate with each ECU3.
[0033] Each ECU3 has communication I / Fs 13a and 13b connected to the communication bus. Communication I / Fs 13a and 13b are corresponding I / Fs for local network functions. When using local network functions, GW2 and ECU3 use the communication protocol corresponding to the local network function. The communication protocol may be, for example, CAN, CAN FD (CAN with Flexible Data Rate), or CAN PN (CAN with Partial Networking).
[0034] The Partial Network Function (PNC) is a function in an in-vehicle system that connects various in-vehicle devices via a bus network. For each function (service), the in-vehicle devices are divided into clusters called PNCs. The PNCs used in the execution of the service wake up the in-vehicle devices and put the in-vehicle devices of other PNCs into sleep mode.
[0035] GW2 functions as a gateway to relay communication between ECUs 3. GW2 and ECUs 3 can send frames. GW2 relays frames between ECUs connected to different buses. For example, GW2 can relay frames between ECU 3a connected to communication bus 12a and ECU 3b connected to communication bus 12b. Thus, for example, frame transmission and reception can occur between ECU 3a connected to communication bus 12a and ECU 3b connected to communication bus 12b.
[0036] [1-2.GW Structure]
[0037] The hardware structure of GW2 will be described below.
[0038] Figure 2This is a block diagram illustrating an example of the structure of GW2 in Embodiment 1. GW2 has a microcontroller unit 21 (hereinafter referred to as "MCU21") and multiple communication I / Fs 11a, 11b. The microcontroller unit 21 includes a control unit 22 and a memory 23. The control unit 22, the memory 23, and the communication I / Fs 11a, 11b are electrically connected via an internal bus 24.
[0039] The control unit 22 may include circuit structures such as a processor. Specifically, the control unit 22 includes one or more CPUs (Central Processing Units). The processor included in the control unit 22 may be a GPU (Graphics Processing Unit). In this case, the control unit 22 reads the computer program stored in the memory 23 and performs various operations and controls.
[0040] The control unit 22 may also include a processor pre-programmed with a predetermined program. For example, the control unit 22 may also be an integrated circuit such as a CPLD (Complex Programmable Logic Device), FPGA (Field-Programmable Gate Array), or ASIC (Application Specific Integrated Circuit). In this case, the control unit 22 performs various operations and controls based on the pre-programmed program.
[0041] Memory 23 has volatile and non-volatile memory for storing various types of data. Volatile memory includes, for example, RAM (Random Access Memory). Non-volatile memory includes, for example, flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or ROM (Read Only Memory). A portion of this non-volatile memory may also be located outside of MCU 21.
[0042] Memory 23 may be a non-volatile memory storing computer programs, information on the timing of execution of functions performed by the ECU (described later), and various parameters. Memory 23 may also store computer programs downloaded from external devices (not shown) via a network (not shown) and a communication device (not shown).
[0043] Communication I / F11a and 11b receive signals flowing in communication buses 12a and 12b via ports (not shown) and convert them into signals that can be read in MCU21. Communication I / F11a and 11b are connected to communication buses 12a and 12b, respectively.
[0044] [1-3. ECU Structure]
[0045] The hardware structure of ECU3 will be described below.
[0046] Figure 3 This is a block diagram illustrating an example of the structure of the ECU in Embodiment 1. ECU 3a includes a microcontroller unit 31, a communication I / F 13a, and peripheral circuitry 34. ECU 3b has the same structure as ECU 3a.
[0047] The microcontroller unit 31 (hereinafter referred to as "MCU31") has the same structure as the MCU21 of GW2 described above. That is, MCU31 includes a control unit (processor) 32 and a memory 33, which includes non-volatile memory and volatile memory. MCU31 may also include peripheral circuitry 34 and communication I / F13a.
[0048] The memory 33 stores the control program, which is a computer program, and the data used in the execution of the control program. The control program can be stored on a recording medium such as flash memory, ROM, or CD-ROM. The processor 32 can utilize local network functions in the ECU 3a through the control program.
[0049] Peripheral circuitry 34 includes, for example, serial communication circuitry conforming to standards such as UART, I2C, and SPI. This serial communication circuitry of peripheral circuitry 34 is connected to the device or sensor controlled by ECU 3a, and can receive signals output from the sensor or send control signals to the controlled device.
[0050] Communication I / F13a is a communication interface based on the communication protocol used in the aforementioned vehicle network. Communication I / F13a is an I / F corresponding to the local network function.
[0051] [1-4. Cluster]
[0052] Figure 4 This is an example of a cluster table indicating which cluster each ECU belongs to when it belongs to a cluster. The following explains the concept of a cluster. In the above, a cluster is referred to as a PNC. Each ECU3 belongs to at least one cluster. The memory 23 of GW2 stores a cluster table 41, which associates each ECU3 with the cluster to which it belongs. The cluster table 41 can also be stored individually by each ECU3.
[0053] As an example of functions performed by multiple ECUs, there are peripheral monitoring functions (hereinafter referred to as "peripheral monitoring functions") performed by image sensors and vehicle information collection functions.
[0054] Surrounding area monitoring is performed by ECU3a and GW2. Therefore, the image ECU and GW2 belong to the same cluster. ECU3a performs the following functions (first function a): acquires images from image sensors that capture images of the vehicle's surroundings, and sends frames containing the acquired images to GW2. GW2 receives the frames containing the images sent from the image ECU and performs the function of identifying people based on the received images (first function b).
[0055] Vehicle information collection functions are performed, for example, by GW2 and ECU3b. Therefore, GW2 and ECU3b belong to the same cluster. In GW2, GW2 performs the following function (second function a): receiving specified vehicle information from designated ECUs via communication buses 12a and 12b, and sending frames containing the received vehicle information to ECU3b. ECU3b, acting as a TCU (Telematic control unit), performs the following function (second function b): receiving frames containing vehicle information sent from GW2 and uploading the received vehicle information to a server located outside the vehicle. The vehicle information collected here includes battery voltage, engine speed detected by the engine tachometer, etc.
[0056] exist Figure 4 The cluster table 41 shown indicates which GW and ECU belong to which clusters PNC1 and PNC2, respectively. Furthermore, Figure 4 The number of clusters shown is for illustrative purposes only; more than two clusters can also be prepared. In the table, "1" indicates that the GW and ECU belong to the cluster in that row, and "0" indicates that the GW and ECU do not belong to the cluster in that row.
[0057] For example, GW2 and ECU3a belong to cluster PNC1. GW2 and ECU3a, belonging to cluster PNC1, perform the first function, such as perimeter monitoring. GW2 and ECU3b belong to cluster PNC2. GW2 and ECU3b, belonging to cluster PNC2, perform the second function, such as vehicle information collection. In the following description, "wake up GW2 and 3a belonging to cluster PNC1" is also simply stated as "wake up cluster PNC1". The same statement is used for other cluster PNC2s.
[0058] [1-5. Action Patterns]
[0059] The operating modes and wake-up actions of GW2 and ECU3 are explained.
[0060] The operating modes of GW2 and ECU3 include normal mode and sleep mode. Normal mode is the working state of GW2 and ECU3, enabling them to control the controlled object and communicate with other GW2 and ECU3 devices. Sleep mode is the state in which GW2 and ECU3 are stopped, except for some functions of communication I / F11a, 11b, 13a, and 13b.
[0061] In CAN, when waking up a portion of the cluster via a local network function, a frame specifying the cluster to be woken up is sent to communication buses 12a and 12b. The wake-up request, i.e., the frame specifying the cluster to be woken up, is sent, for example, by ECU3a. In the case of ECU3a, the frame is generated using cluster table 41. However, the frame sending source is not limited to ECU3a; GW2 and ECU3b can also send frames.
[0062] When GW2 (in sleep mode) receives communication I / F11a, 11b and ECU3 (in communication I / F13a, 13b) frames, they determine whether the frame specifies the cluster to which their devices belong. If no cluster is specified, GW2 and ECU3 remain in sleep mode. If a cluster is specified, communication I / F11a, 11b, 13a, 13b interrupts the control unit (processor), instructing a switch from sleep mode to normal mode. This wakes up GW2 and ECU3, which belong to the specified cluster.
[0063] On the other hand, GW2 and ECU3 transition from normal mode to sleep mode when the processing related to their own device functions ends. That is, GW2 and ECU3, which receive frames and transition from sleep mode to normal mode, are configured to transition to sleep mode after a series of processes have ended. Therefore, when no frames are received, GW2 and ECU3 transition to sleep mode and maintain sleep mode. GW2 and ECU3 can also be configured to transition to sleep mode after a predetermined period of time after a series of processes have ended.
[0064] The transition of GW2 and ECU3 to sleep mode is not limited to the case where no more frames are received. For example, GW2 and ECU3 can also be configured to transition to sleep mode upon receiving a frame containing a command indicating a transition to sleep mode.
[0065] When transitioning from sleep mode to normal mode, GW2 and ECU3 operate according to a predetermined clock. In sleep mode, the clock stops, and GW2 and ECU3 cease operation. Therefore, in normal mode, the power consumption generated by GW2 and ECU3 is high. Conversely, in sleep mode, the power consumption generated by GW2 and ECU3 is low. Furthermore, in normal mode, communication I / Fs 11a, 11b, 13a, and 13b operate. In sleep mode, some functions of communication I / Fs 11a, 11b, 13a, and 13b are disabled.
[0066] [1-7. Functions of GW]
[0067] Figure 5 This is a functional block diagram illustrating an example of the function of GW in Implementation Method 1.
[0068] GW2 has the functions of the acquisition unit 51 and the decision unit 52. The acquisition unit 51 and the decision unit 52 are functions of MCU 21. The functions of the acquisition unit 51 and the decision unit 52 are implemented by MCU 21 executing a control program.
[0069] [1-7-1. Acquisition Section]
[0070] The acquisition unit 51 acquires first information and second information. The first information is used to determine a first execution start timing and a first execution cycle. The second information is used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing for starting a first function executed by the first vehicle control device and the second vehicle control device. The first execution cycle is the cycle for executing the first function. The second execution start timing is the timing for starting a second function executed by the first vehicle control device and the third vehicle control device. The second execution cycle is the cycle for executing the second function.
[0071] Specifically, the first function performed by the first and second vehicle control units is, for example, a perimeter monitoring function performed by an image ECU (ECU3a) that acquires images from an image sensor capturing images of the vehicle's surroundings and a GW2 that identifies people from the acquired images. The second function performed by the first and third vehicle control units is, for example, a vehicle information collection function where GW2 receives specified vehicle information from designated ECUs via communication buses 12a and 12b, and ECU3b, acting as a TCU, uploads this vehicle information to a server located outside the vehicle. The perimeter monitoring function (first function) and the vehicle information collection function (second function) are both performed by the shared GW2, which is the first vehicle control unit.
[0072] An execution cycle is, for example, the cycle in which a function such as a perimeter monitoring function is repeatedly executed. The perimeter monitoring function is executed by an image ECU that acquires images from an image sensor and a GW2 that identifies people from the acquired images. The image ECU 3a, acting as the image ECU, is woken up in each execution cycle to execute the perimeter monitoring function. The ECU 3a is woken up by applying an interrupt to itself through a timer. The timer is set to a value such as 3ms. The perimeter monitoring function is executed every 3ms; in this case, 3ms is a specific example of an execution cycle.
[0073] The execution start timing is the timing at which a function begins to be executed. The execution start timing is the timing from a reference time elapsed until the time indicated by the execution start timing. The reference time is, for example, a master clock in one of the GW, ECU, or an external server that manages the reference time for the entire vehicle. When the timers of each ECU are synchronized with this master clock, the reference time is the starting point of that master clock. Alternatively, in the case of executing multiple functions, it is the starting point of execution for any one of those functions, function A. Specifically, in the case of executing the perimeter monitoring function and the vehicle information collection function, for example, the timer of GW2, which executes the vehicle information collection function, is started synchronously with the starting point of execution of the perimeter monitoring function by ECU3a. An execution start timing for the vehicle information collection function is set on the timer of GW2. After the time indicated by the execution start timing has elapsed, the timer of GW2 interrupts itself, causing the vehicle information collection function to start. Thus, based on the starting point of the perimeter monitoring function's execution, after the time indicated by the timing for starting the vehicle information collection function's execution has elapsed, the vehicle information collection function begins to execute.
[0074] The first information is used to determine the first start timing and the first execution cycle. The first start timing is the timing at which the function begins, and the first execution cycle is the cycle during which the function is executed. The second information is used to determine the second start timing and the second execution cycle. The second start timing is the timing at which the function begins, and the second execution cycle is the cycle during which the function is executed.
[0075] Figure 6 This diagram illustrates an example of information used to determine the execution start timing and execution cycle. Hereinafter, the first information used to determine the first execution start timing and the first execution cycle, and the second information used to determine the second execution start timing and the second execution cycle, will sometimes be collectively referred to as "execution condition information." Additionally, the first execution start timing and the second execution start timing will sometimes be collectively referred to as "execution start timing," and the first execution cycle and the second execution cycle will sometimes be collectively referred to as "execution cycle."
[0076] The execution condition information is determined by considering each function, for example... Figure 6 The information is presented in tabular form. Execution condition information may include the following: an association with an identifier used to identify the function, used to determine the start time and execution cycle for each function. Examples of listed information include, for instance, the initial value of the execution cycle, the allowed range of execution cycle changes, the execution duration, and constraints.
[0077] The initial value of the execution cycle is the typical initial value of the execution cycle required to achieve the function. The initial value of the execution cycle is, for example, 2ms or 3ms. The allowed range of changes to the execution cycle is the range from the initial value. The execution cycle required to achieve the function has a width, and the allowed range of changes to the execution cycle indicates how far it can be changed from the initial value. The allowed range of changes to the execution cycle is, for example, ±1ms. Furthermore, while an initial value and its allowed range of changes have been described here, it is also possible to specify a minimum or maximum value for the execution cycle. The execution duration is the time from the start to the end of the function executed within the specified execution cycle. The execution duration is, for example, 0.2ms or 0.3ms.
[0078] Constraints are conditions that restrict the execution of a function. The conditions restricting a function's execution are specified according to the needs of that function, and sometimes they are not specified at all. For example, constraints may be specified as information indicating that actions cannot be performed in parallel, so that this function has high priority and is not executed concurrently with other functions. Alternatively, if the first function completes its execution, accepts the result of the first function, and the second function begins execution, the constraint for the second function may be specified as information indicating that it will execute after the first function completes. Furthermore, if no constraints are specified, the execution start timing and execution period are determined within the initial value of the execution cycle and within the allowed range of changes to the execution cycle.
[0079] The acquisition unit obtains execution condition information. This execution condition information is stored, for example, in the non-volatile memory of memory 23 in GW2. The control unit 22 reads the execution condition information stored in memory 23 and obtains the execution condition information. The execution condition information can also be stored by the ECU for each function. Specifically, if the execution condition information is for the perimeter monitoring function, it can be stored by ECU3a, which is an image ECU, and if it is for the vehicle information collection function, it can be stored by GW2. In this case, the acquisition unit 51 can also obtain the execution condition information for the perimeter monitoring function from ECU3a and the execution condition information for the vehicle information collection function from GW2. The execution condition information can also be stored by an external server. In this case, the acquisition unit 51 accesses the server via a communication network to obtain the necessary execution condition information. When the scheduling device is implemented as a server, the acquisition unit 51 obtains the execution condition information directly from its own device without using a communication network.
[0080] [1-7-2. Decision-Making Department]
[0081] Based on the first information and the second information, the decision unit 52 determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device.
[0082] The GW and each ECU consume a specified amount of power to perform their designated functions. For example, GW2 consumes 20W, ECU3a consumes 5W, and ECU3b consumes 10W. Here, power consumption may not be the actual power consumption, but rather a relative value of the power consumption of each ECU. This is because even relative values can be compared. For example, GW2 consumes 4W, ECU3a consumes 1W, and ECU3b consumes 2W.
[0083] Figure 7 This diagram illustrates the actions of two functions being executed in parallel. Surrounding area monitoring by the image sensor is performed by ECU3a and GW2. ECU3a performs the following functions: acquiring images from the image sensor that captures images of the vehicle's surroundings, and sending frames containing the acquired images to GW2. Figure 7 The 71a section is shown. GW2 receives frames including images sent from the image ECU; upon receiving the frames, GW2 is activated. The activated GW2 performs functions such as recognizing a person from the received images. Figure 7 The portion shown in 71b. (As shown in the image) Figure 7 As shown, the surrounding monitoring function executes for 0.2ms every 3ms.
[0084] On the other hand, the vehicle information collection function is performed by GW2 and ECU3b. GW2 performs the following functions: receiving specified vehicle information from designated ECUs via communication buses 12a and 12b, and sending frames containing the received vehicle information to ECU3b. Figure 7 Part 72a. ECU3a receives a frame containing vehicle information sent from GW2, and ECU3b, upon receiving the frame, is awakened. The awakened ECU3b performs the function of uploading the received frame containing vehicle information to a server located outside the vehicle. Figure 7 Part 72b. For example... Figure 7 As shown, the vehicle information collection function, for example, is executed every 3ms, with a 1ms delay after the execution of the surrounding monitoring function, for a period of 0.3ms.
[0085] The total power consumption is the sum of the power consumed by each ECU. Furthermore, based on the first and second execution durations, the decision unit calculates the power consumption of each of the first, second, and third vehicle control units, and determines the minimum execution start time and execution cycle for the total power consumption. Specifically, the power consumption of each ECU is multiplied by the execution duration, summed, and then divided by the execution cycle to obtain the total power consumption. When the execution cycles of the first and second functions differ, the calculation is performed using the least common multiple of their execution cycles. In this way, the power consumption can be easily calculated even without actually measuring the voltage and current of the ECUs.
[0086] For example, GW2 is 20W, ECU3a is 5W, and ECU3b is 10W. When performing the surrounding monitoring and vehicle information collection functions, the total power consumption of GW2, ECU3a, and ECU3b is 4.7W. Total electricity consumption = (0.2 × 5 + (0.2 + 0.3) × 20 + 0.3 × 10) / 3 =4.7W (watts)
[0087] Next, the decision unit 52 determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption.
[0088] Specifically, the decision unit 52, for example, sequentially changes the execution start timing of the vehicle information collection function within the execution cycle and calculates the total power consumption. Then, it determines the execution start timing as the period from the start of the perimeter monitoring function (which has the lowest total power consumption) to the start of the vehicle information collection function (which starts with a delay). For example, it calculates the total power consumption when the vehicle information collection function starts executing 0ms after the perimeter monitoring function. In this case, GW2 executes both the perimeter monitoring function and the vehicle information collection function simultaneously, so the execution duration of GW2 is 0.3ms. Furthermore, the total power consumption in this case is... Total electricity consumed = (0.2 × 5 + 0.3 × 20 + 0.3 × 10) / 3 =3.3W (watts)
[0089] Figure 8 This is a diagram representing the actions when two functions are executed simultaneously in time. For example... Figure 8 As shown, by overlapping the execution of the surrounding monitoring function and the vehicle information collection function, the duration of GW2's operation is reduced, thus decreasing the total power consumption. The minimum power consumption is achieved when the overlapping period of the two functions is minimized.
[0090] Additionally, the first information includes a first execution duration, which is the time from the start to the end of the first function within a first execution cycle. The second information includes a second execution duration, which is the time from the start to the end of the second function within a second execution cycle. Specifically, as follows... Figure 6 As shown, the execution condition information includes the execution duration, which is the time from the start to the end of a periodically executed function. For example, in the case of the perimeter monitoring function, the execution duration is, for example, 0.2 ms. In the case of the vehicle information collection function, the execution duration is, for example, 0.3 ms. Thus, the execution duration of the perimeter monitoring function is shorter than that of the vehicle information collection function. Therefore, there is a width in the overlap period between the shortest execution of the perimeter monitoring function and the vehicle information collection function. Specifically, the execution start timing of the vehicle information collection function, which starts from the start of the perimeter monitoring function, is between -0.1 ms and 0 ms. When the execution start timing of the vehicle information collection function is between -0.1 ms and 0 ms, the overlap period of the two functions is fixed at 0.3 ms. By having such an execution duration, the execution start timing can be flexibly determined.
[0091] The above explains the case where the execution cycle of the surrounding surveillance function and the vehicle information collection function are both 3ms. Next, the function of the decision unit 52 will be explained in the case where, for example, the execution cycle of the surrounding surveillance function is 2ms and the execution cycle of the vehicle information collection function is 3ms.
[0092] Figure 9 This is a diagram representing the actions of two functions executed in different execution cycles. For example... Figure 9 As shown, even if the start time of the vehicle information collection function is set to 0ms, the execution of the vehicle information collection function can overlap when the first peripheral monitoring function is executed. However, when the peripheral monitoring function is executed for the second time, the vehicle information collection function is not executed, and the power consumption cannot be suppressed.
[0093] Therefore, the decision unit 52 determines a first setting range based on the first information, and determines a first execution start time and a first execution cycle based on the first setting range. The decision unit 52 also determines a second setting range based on the second information, and determines a second execution start time and a second execution cycle based on the second setting range. The first setting range is the range within which the first execution cycle should be limited, and the second setting range is the range within which the second execution cycle should be limited. Alternatively, the first setting range can be determined based on a first cycle initial value and a first allowed range. The first cycle initial value is the initial value of the cycle for executing the first function, and the first allowed range is the range within which changes from the first cycle initial value are permitted. The second setting range can be determined based on a second cycle initial value and a second allowed range. The second cycle initial value is the initial value of the cycle for executing the second function, and the second allowed range is the range within which changes from the second cycle initial value are permitted. Furthermore, the first setting range and the second execution range are sometimes referred to as "setting range".
[0094] The first setting range is the range that should limit the first execution cycle. The first setting range is determined based on the first information. Furthermore, the first execution start time and the first execution cycle are determined based on the first setting range. Thus, if it is within the first setting range, the first execution start time and the first execution cycle can be flexibly determined. The same applies to the second setting range. As a result, when the perimeter monitoring function is executed for the first time, the execution of the vehicle information collection function can overlap, and when the perimeter monitoring function is executed for the second time or subsequent times, the vehicle information collection function can be executed, thereby suppressing power consumption.
[0095] Figure 6 This is a diagram illustrating an example of the conditions used to determine the start time and execution cycle. For example... Figure 6As shown, in the case of the perimeter monitoring function, the initial value of the execution cycle is 2ms, and the allowed range for changing the execution cycle (the range within which changes from the initial value are permitted) is ±1ms. Therefore, the setting range for the perimeter monitoring function is from 1ms to 3ms, allowing the execution cycle to be determined within this range. On the other hand, in the case of the vehicle information collection function, the initial value of the execution cycle is 3ms, and the allowed range for changing the execution cycle (the range within which changes from the initial value are permitted) is ±1ms. Therefore, the setting range for the vehicle information collection function is from 2ms to 4ms, allowing the execution cycle to be determined within this range. As a result, the allowed ranges for the perimeter monitoring function and the allowed ranges for the vehicle information collection function overlap within the 2ms to 3ms range.
[0096] Figure 10 This is a diagram representing two functions executing simultaneously over time with the same execution cycle. For example... Figure 10 As shown, by setting the execution cycle to, for example, 3ms, the execution of the vehicle information collection function can overlap when the surrounding monitoring function is executed for the first time, and the vehicle information collection function can be executed when the surrounding monitoring function is executed for the second time or subsequent times.
[0097] However, the total power consumption varies within the execution cycle range of 2ms to 3ms. For example, in the case of performing the surrounding surveillance and vehicle information collection functions, the total power consumption is 4.5W when the execution cycle is 2ms. Total electricity consumed = (0.2 × 5 + 0.3 × 20 + 0.2 × 10) / 2 =4.5W (watts)
[0098] With an execution cycle of 3ms, the total power consumption is 3.3W. Total electricity consumed = (0.2 × 5 + 0.3 × 20 + 0.2 × 10) / 3 =3.3W (watts)
[0099] Thus, the total power consumption changes depending on the execution cycle. Therefore, the decision unit 52 needs to determine the execution cycle and execution timing that minimize the total power consumption within the overlapping set range. To determine the execution cycle and execution timing that minimize the total power consumption, for example, the execution cycle is changed sequentially within the set range, and then the execution start timing is changed sequentially within the range of the changed execution cycle, each total power consumption is calculated, and a combination of the execution cycle and execution start timing that minimizes the total power consumption is adopted.
[0100] Furthermore, the methods for determining the execution cycle are not limited to this; for example, various methods such as steepest descent can be used.
[0101] [1-8. Operation of the Dispatching Device]
[0102] The operation of the scheduling device in Embodiment 1 will now be described. The scheduling device begins operation, for example, when a new function is introduced into the vehicle system 1. Additionally, the scheduling device also begins operation when a new ECU is added to the vehicle system 1, and a new function is introduced into the vehicle system 1 simultaneously. Alternatively, the scheduling device also begins operation when an existing function is updated.
[0103] Figure 11 This is a flowchart illustrating an example of the operation of the scheduling device in Implementation 1.
[0104] [1-8-1. Step S01]
[0105] The acquisition unit 51 acquires first information and second information (step S01). The first information is used to determine a first execution start timing and a first execution cycle. The second information is used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing at which a first function is started by the first vehicle control device and the second vehicle control device. The first execution cycle is the cycle for executing the first function. The second execution start timing is the timing at which a second function is started by the first vehicle control device and the third vehicle control device. The second execution cycle is the cycle for executing the second function. That is, the acquisition unit 51 acquires execution condition information.
[0106] Execution condition information is stored, for example, in the non-volatile memory of memory 23 of GW2. Control unit 22 reads the execution condition information stored in memory 23 to obtain the execution condition information. Execution condition information can also be stored by the ECU for each function, for example. Specifically, if the execution condition information is for the perimeter monitoring function, it can be stored by ECU 3a, which is the image ECU; if it is for the vehicle information collection function, it can be stored by GW2. In this case, acquisition unit 51 obtains the execution condition information for the perimeter monitoring function from ECU 3a and the execution condition information for the vehicle information collection function from GW2. Execution condition information can also be stored by an external server. In this case, acquisition unit 51 accesses the server via a communication network to obtain the necessary execution condition information. If the scheduling device is implemented as the server, acquisition unit 51 obtains the execution condition information directly from its own device without using a communication network. After acquisition unit 51 obtains the execution condition information, it proceeds to step S02.
[0107] [1-8-2. Step S02]
[0108] Based on the first information and the second information, the decision unit 52 determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device (step S02).
[0109] Specifically, for example, the decision unit 52 scans the execution cycle and execution start time within a set range, and makes a decision using the execution cycle and execution start time that minimize the total power consumption. After the decision unit 52 determines the execution start time and execution cycle, the scheduling device ends the operation.
[0110] Figure 12 This is a flowchart illustrating an example of a routine whose execution start time and cycle are determined. The following is a further explanation... Figure 12 The execution start time and execution cycle are explained in the example routines shown.
[0111] [Step S021]
[0112] In the execution start timing and execution cycle determination routine, the determination unit 52 first sets the execution cycle to the minimum value of the set range and stores it in the memory 23. After storage, the determination unit 52 proceeds to step S022.
[0113] [Step S022]
[0114] Next, the decision unit 52 sets a predetermined value, for example 0, for the start timing and stores it in the memory 23. After storage, the decision unit 52 proceeds to step S023.
[0115] [Step S023]
[0116] Next, the decision unit 52 calculates the total power consumption based on the set execution cycle and execution start timing, and stores it in the memory 23. After storage, the decision unit 52 proceeds to step S024.
[0117] [Step S024]
[0118] Next, the decision unit 52 changes only the prescribed values for the execution cycle and the execution start timing. The value change covers a set range by changing only the prescribed value for any one of the first execution cycle, the first execution start timing, the second execution cycle, and the second execution start timing. The prescribed value is, for example, the greatest common divisor of the first and second execution cycles. In the case where the first execution cycle is 2ms and the second execution cycle is 3ms, the prescribed step size is 1ms. The prescribed step size is not limited to this; for example, it can be shorter, such as 0.1ms. After changing the first execution cycle, the first execution start timing, the second execution cycle, and the second execution start timing, the decision unit 52 proceeds to step S025.
[0119] [Step S025]
[0120] Next, the decision unit 52 calculates the total power consumption based on the changed execution cycle and execution start timing. After calculating the total power consumption, the decision unit 52 proceeds to step S026.
[0121] [Step S026]
[0122] Next, the decision unit 52 compares the total power consumption stored in the memory 23 with the total power consumption calculated in this step (S025). If the total power consumption in this step is less than the total power consumption stored in the memory 23 (Yes in step S026), the decision unit 52 proceeds to step S027. On the other hand, if the total power consumption in this step is greater than or equal to the total power consumption stored in the memory 23 (No in step S026), the decision unit 52 proceeds to step S028.
[0123] [Step S027]
[0124] Next, the decision unit 52 stores the total power consumption (calculated in step S025), the current execution cycle, and the execution start timing in the memory 23. After storage, the decision unit 52 proceeds to step S028.
[0125] [Step S028]
[0126] Next, the decision unit 52 determines whether the execution cycle and execution start timing cover the set range. If it determines that there is no coverage, it returns to step S024 and calculates the total power consumption again while changing the execution cycle and execution start timing. On the other hand, if it determines that there is coverage, the decision unit 52 returns to the original routine.
[0127] [1-9. Summary]
[0128] When the decision unit 52 executes steps S021 to S028, it calculates the total power consumption while changing the execution cycle and execution start timing within a first and second set range. Whenever a total power consumption smaller than the total power consumption stored in the memory 23 is found, the total power consumption, the execution cycle at that time, and the execution start timing are stored in the memory 23. As a result, when steps S021 to S08 are completed, the memory 23 stores the minimum total power consumption and the execution start timing and execution cycle corresponding to that total power consumption.
[0129] Therefore, by executing steps S01 to S02, the scheduling device can determine the first execution start time and the first execution cycle that minimizes total power consumption. Thus, even if more functions are added to the vehicle system 1 and executed in parallel, a scheduling table that suppresses power consumption of the vehicle control device can be determined.
[0130] Furthermore, the above describes the implementation of the scheduling device within the GW. However, it is not limited to the GW and can also be implemented on an external server. When implemented within the GW, there is no need to transmit or receive execution condition information, the determined execution start time, and the execution period via a communication network, allowing the execution start time and execution period to be determined quickly. On the other hand, when implemented on an external server, the execution start time and execution period are determined by the external server, thus offering the advantage of not straining vehicle-side hardware resources such as the GW's storage area. Moreover, the external server can be an OTA (Over-the-Air) server where software is updated via a wireless network.
[0131] <Implementation Method 2>
[0132] [2. Details of Embodiment 2 of this disclosure]
[0133] Hereinafter, the details of Embodiment 2 of this disclosure will be described with reference to the accompanying drawings.
[0134] In Embodiment 2, the scheduling device also includes a setting unit as a functional block, but other parts are the same as in Embodiment 1. Structures identical to those in Embodiment 1 are labeled with the same reference numerals, and descriptions of identical structures, functions, and operations are omitted.
[0135] [2-1 Structure of the Dispatching Device]
[0136] The structure of the scheduling device in Embodiment 2 is the same as that in Embodiment 1.
[0137] [2-2 Problems to be solved by this implementation method]
[0138] In Implementation 2, it is desired to set a schedule in the vehicle system 1 that can suppress the power consumption of the vehicle control device.
[0139] [2-3 Functions of the Dispatching Device]
[0140] Figure 13 This is a functional block diagram illustrating an example of the function of the scheduling device in Embodiment 2. In Embodiment 2, the scheduling device 2 further includes a setting unit 53 as a functional block.
[0141] [2-3-1 Setting Department]
[0142] The setting unit sets the first execution start time and the first execution cycle determined by the decision unit for the first vehicle control device and the second vehicle control device, and sets the second execution start time and the second execution cycle determined by the decision unit for the first vehicle control device and the third vehicle control device.
[0143] Specifically, the first execution start timing, first execution cycle, second execution start timing, and second execution cycle determined by the decision unit 52 are stored, for example, in the memory 23. The setting unit 53 loads the first execution start timing, first execution cycle, second execution start timing, and second execution cycle stored in the memory 23 into a frame via communication I / Fs 13a and 13b and communication buses 12a and 12b, and sends this information, representing the first execution start timing, first execution cycle, second execution start timing, and second execution cycle, to the ECU executing the function. The ECU receiving the transmitted frame retrieves the information representing the execution cycle and execution start timing loaded in the frame and executes the function based on the retrieved execution cycle and execution start timing.
[0144] When the function is performed by its own device, information indicating a first execution start time, a first execution cycle, a second execution start time, and a second execution cycle is set to a designated location on the own device. Based on the set first execution start time, first execution cycle, second execution start time, and second execution cycle to the designated location, the own device performs the function. Thus, the setting unit 53 can set the execution cycle and execution start time to the vehicle control device.
[0145] [2-4 Operation of the Dispatching Device]
[0146] Figure 14This is a flowchart illustrating an example of the operation of the scheduling device according to Embodiment 2. The operation of the scheduling device according to Embodiment 2 will be described below. The operations of steps S01 to S02 are the same as in Embodiment 1, and therefore will be omitted from the description. The difference between Embodiment 2 and Embodiment 1 is that in step S03, the setting unit 53 sets the execution cycle and execution start timing to the ECU. After the determination unit 52 determines the first execution start timing, the first execution cycle, the second execution start timing, and the second execution cycle, the scheduling device proceeds to step S03.
[0147] [2-4-1. Step S03]
[0148] The setting unit 53 sets a first execution start time and a first execution cycle determined by the decision unit 52 to the first vehicle control device and the second vehicle control device, and sets a second execution start time and a second execution cycle determined by the decision unit to the first vehicle control device and the third vehicle control device.
[0149] Specifically, the setting unit 53 loads the first execution start timing, first execution cycle, second execution start timing, and second execution cycle stored in the memory 23 into a frame via communication I / F 13a, 13b and communication buses 12a, 12b, and sends the information indicating the execution start timing and execution cycle to the ECU performing the function. When the function is performed by its own device, the setting unit 53 sets the information indicating the execution start timing and execution cycle at a designated location of its own device.
[0150] In the case of both the surrounding area monitoring function and the vehicle information collection function, the setting unit 53 sets a first execution cycle and a first execution start time for GW2 and ECU3a, and sets a second execution start time and a second execution cycle for GW2 and ECU3b. ECU3a performs the surrounding area monitoring function based on the set first execution start time and the first execution cycle. ECU3b performs the vehicle information collection function based on the set second execution start time and the second execution cycle. GW2 performs the surrounding area monitoring function based on the first execution start time and the first execution cycle, and simultaneously performs the vehicle information collection function based on the second execution start time and the second execution cycle. After the setting unit 53 sets the execution cycle and the execution start time for GW2, ECU3a, and ECU3b, the dispatching device ends the operation.
[0151] [2-4-2. Summary]
[0152] Based on the first execution start time, first execution cycle, second execution start time, and second execution cycle determined by the decision unit 52 in a manner that minimizes total power consumption, GW2, ECU3a, and ECU3b execute the function. Therefore, even if more functions are added to the vehicle system 1 and executed in parallel, power consumption of the vehicle control device can be suppressed.
[0153] <Implementation Method 3>
[0154] [3. Details of Embodiment 3 of this disclosure]
[0155] Hereinafter, the details of Embodiment 3 of this disclosure will be described with reference to the accompanying drawings.
[0156] The scheduling device in Embodiment 3 has the same functional blocks as in Embodiment 1. However, the function and some of the operation of the decision unit 52 are different. The same reference numerals are used for structures that are the same as in Embodiment 1, and descriptions of the same structures, functions, and operations are omitted.
[0157] [3-1 Structure of the Dispatching Device]
[0158] The structure of the scheduling device in Embodiment 3 is the same as that in Embodiment 1.
[0159] [3-2 Problems to be solved by this implementation method]
[0160] For example, sometimes the first function has a high priority and needs to be executed separately from other functions. Additionally, after the first function is completed, it may be necessary to accept the result of the first function and begin executing the second function. In such cases, even if the total power consumption is minimized, it is impossible to execute the first and second functions simultaneously. In Implementation 3, even under such limitations, the power consumption of the vehicle control device is suppressed.
[0161] [3-3 Functions of the Dispatching Device]
[0162] The functional blocks of the scheduling device in Implementation Method 3 and Figure 5 The functional blocks of Embodiment 1 shown are the same. On the other hand, some of the functions of the decision unit 52 are different.
[0163] [3-3-1 Decision-Making Department]
[0164] The first information includes information indicating restrictive conditions limiting the execution of the first function, and the decision unit determines the first execution start timing, the first execution cycle, the second execution start timing, and the second execution cycle by circumventing the restrictive conditions. The restrictive conditions may also include conditions that restrict the first function and the second function from executing concurrently in time. Alternatively, the restrictive conditions may include at least one of conditions related to restrictions on the hardware resources used by the first function and conditions related to restrictions on the hardware resources used by the second function.
[0165] Figure 15 This is a diagram representing an example of execution condition information that includes limiting information. (And...) Figure 6 The differences include restrictions that limit the execution of the first and second functions to overlap in time. Specifically, a restriction is added to the first function that it cannot operate in parallel. Furthermore, although a third function is added, it comes with the restriction that it executes after the second function has completed.
[0166] Due to reasons such as not allowing delays, if the first function has a high priority and is not executed in parallel with other functions, a constraint is set that it cannot operate in parallel. In this case, the timing for starting the execution of the second function needs to be determined by whether the second function starts executing after the first function or ends executing before the first function.
[0167] Furthermore, the limitation of not being able to operate in parallel can be at least one of the conditions related to the limitation of hardware resources used by the first function and the limitation of hardware resources used by the second function. For example, in the case of very heavy processing, consider using the full processing power of the ECU's CPU or using more than 90% of the memory, in which case the execution of other functions is restricted. In addition, in the case of functions that send and receive large amounts of image data via the communication bus, the communication capacity of the communication bus is also used, making it more difficult to send and receive data on the communication bus, thus restricting the execution of other functions.
[0168] The condition that the third function begins execution after the second function is completed is set to require the result of the second function to be received before the third function begins execution. For example, the second function collects information about various parts of the vehicle, such as battery voltage and oil temperature, and the third function performs self-diagnosis of the vehicle based on the information collected by the second function. In this case, the timing for starting the execution of the third function needs to be determined so that it begins after the second function has finished executing.
[0169] In Embodiment 1, within a set range, while changing the execution start timing and execution period, the total power consumption is calculated sequentially, and the determination unit 52 determines the execution start timing and execution period within the set range that minimizes the total power consumption. In Embodiment 3, to avoid restrictions such as the inability to perform parallel operations or execution after the completion of the second function, when the determination unit 52 changes the execution start timing and execution period within the set range, it determines whether the execution start timing and execution period meet the restrictions. If the restrictions are met, the execution start timing and execution period are discarded to avoid the restrictions. Then, to proceed to the next candidate, the execution start timing and execution period are changed. On the other hand, if the restrictions are not met, the determination unit 52 continues to calculate the operation after the total power consumption.
[0170] Figure 16 This is a diagram illustrating an example of the execution order of the first to third functions. Figure 16 This refers to the state before the scheduling device of this disclosure begins operation, after the addition of the second and third functions. Figure 16 In this state, although a restriction such as "cannot be performed in parallel" is attached to the first function, the execution of the first function overlaps with the execution of the second function. Furthermore, although a restriction such as "execute after the completion of the second function" is attached to the third function, the third function is executed before the second function.
[0171] Figure 17 This is a diagram illustrating an example of the execution order of the first to third functions. Figure 17 This is the state after the operation of the scheduling device of this disclosure has ended, with the addition of the second and third functions. The decision unit 52 determines the execution start time and execution period of each function while avoiding limiting conditions. As a result, the execution start time of the second function is determined to be after the first function ends, the execution period is determined to be 3ms, and the execution start time of the third function is determined to be after the second function ends, with the execution period determined to be 3ms. Therefore, it is possible to avoid limiting conditions such as the inability to perform the first function in parallel and the limitation condition that the third function is executed after the second function is completed.
[0172] [Operation of the 3-4 Dispatching Device]
[0173] Figure 18This is a flowchart illustrating an example of the operation of the scheduling device in Embodiment 3. The operation of the scheduling device in Embodiment 3 will be described below. The operations of steps S021 to S028 are the same as in Embodiment 1, and therefore will be omitted from the description. Unlike Embodiment 1, Embodiment 3 differs in that it determines whether the execution start timing and execution period after the changes made in step S024 meet the limiting conditions (step S029). The determination unit 52 proceeds to step S029 after changing the execution start timing and execution period by a predetermined value.
[0174] [3-4-1. Step S029]
[0175] Determine whether the execution start timing and execution cycle after the changes in step S024 meet the constraints (step S029). For example, consider the case of determining the execution start timing of the second function. Figure 15 As shown, the execution duration of the first function is 0.2ms. The execution duration can be determined by referring to... Figure 15 The execution condition information is obtained by means of the execution condition information. Since this information includes details about the execution duration, even under constraints such as the inability to perform parallel operations, it is possible to set an execution start time that allows the second function to begin immediately after the first function ends. Therefore, when the first and second functions are executed by the same ECU, the ECU can continue executing the second function after the first function ends without needing to hibernate or wake up. As a result, processing time and power consumption can be reduced.
[0176] For example, since the surrounding surveillance function is subject to a restriction that it cannot operate in parallel, the decision unit 52 determines that the restriction condition is met (yes in step S029) if the execution start time of the vehicle information collection function falls within the range of 0.2ms from the start of the surrounding surveillance function, and proceeds to step S028. The decision unit 52 in step S028 then determines whether the total power consumption has been calculated within the entire permissible range. Since step S027 is not executed, the execution start time and execution period are not stored in memory 23 and are not determined as the minimum total power consumption execution start time and execution period.
[0177] On the other hand, if the execution start time of the second function is 0.2ms after the execution start time of the first function and, for example, 0.3ms after the end time of the first function, it is determined that the restriction condition is not met (No in step S029), and the process proceeds to step S025. The decision unit 52 in step S025 calculates the total power consumption.
[0178] [3-4-2. Summary]
[0179] Therefore, the decision unit 52 avoids the constraints and determines the execution start time and execution cycle that minimizes the total power consumption. As a result, even under the presence of constraints, it is possible to suppress the power consumption of the vehicle control device.
[0180] [4. Variations]
[0181] The above describes the operation of the scheduling device under local network functionality. The scheduling device of this disclosure does not necessarily require local network functionality. The following describes the operation modes and wake-up of GW2 and ECU3 without relying on local network functionality.
[0182] Even in this situation, the operating modes of GW2 and ECU3 include a normal mode and a sleep mode. The normal mode is the working state of GW2 and ECU3, enabling them to control the controlled object and communicate with other GW2 and ECU3 devices. The sleep mode is the state in which GW2 and ECU3 are stopped, except for some functions of communication I / F11a, 11b, 13a, and 13b.
[0183] When an ECU is woken up, a frame containing information specifying the ECU to be woken up is sent to communication buses 12a and 12b. For example, a frame containing a wake-up request, specifying the ECU to be woken up, is sent by ECU3a. ECU3a is configured, for example, to store information indicating that peripheral monitoring functions performed by ECU3a and GW2 are being executed. Based on this information, ECU3a sends a frame to GW2 containing information indicating that the frame is addressed to GW2, the ECU to be woken up. The frame sending source is not limited to ECU3a; it can also be sent by GW2 or ECU3b.
[0184] The communication I / F11a, 11b of GW2 and the communication I / F13a, 13b of ECU3, which are in sleep mode, constitute a receive frame. It is then determined whether the device itself is specified in this frame. If the device itself is not specified, GW2 and ECU3 directly maintain sleep mode. If the device itself is specified, the communication I / F11a, 11b, 13a, 13b apply an interrupt to the control unit (processor), instructing a switch from sleep mode to normal mode. This wakes up the specified GW2 and ECU3.
[0185] On the other hand, GW2 and ECU3 transition from normal mode to sleep mode when the execution of functions related to their own devices ends. That is, GW2 and ECU3, which receive frames and transition from sleep mode to normal mode, are configured to transition to sleep mode after a series of processes have ended. Therefore, when no frames are received, GW2 and ECU3 transition to sleep mode and remain in sleep mode. GW2 and ECU3 can also be configured to transition to sleep mode after a predetermined period of time after a series of processes have ended.
[0186] The transition of GW2 and ECU3 to sleep mode is not limited to the case where no more frames are received. For example, ECU3 can also be configured to transition to sleep mode upon receiving a frame containing a command instructing it to transition to sleep mode.
[0187] When transitioning from sleep mode to normal mode, GW2 and ECU3 operate according to a predetermined clock. In sleep mode, the clock stops, and GW2 and ECU3 cease functioning. Therefore, in normal mode, the power consumption generated by GW2 and ECU3 is high. Conversely, in sleep mode, the power consumption generated by GW2 and ECU3 is low.
[0188] Thus, the ECU is woken up and transitions to sleep mode via frame transmission and reception. Moreover, the ECU performing this action can also implement the scheduling device disclosed herein.
[0189] [5-1. Supplement 1]
[0190] In addition, this disclosure includes the following in-vehicle systems.
[0191] An in-vehicle system includes: a scheduling unit for scheduling functions executed by multiple in-vehicle control devices capable of communicating with each other via a communication bus; and the in-vehicle control devices connected to the communication bus. The scheduling unit includes: an acquisition unit for acquiring first information and second information, the first information being used to determine a first execution start time and a first execution period, and the second information being used to determine a second execution start time and a second execution period. The first execution start time is the timing at which a first function is started by a first in-vehicle control device and a second in-vehicle control device, the first execution period is the period during which the first function is executed, the second execution start time is the timing at which a second function is started by the first in-vehicle control device and a third in-vehicle control device, and the second execution period is the period during which the second function is executed; and a determination unit for determining, based on the first information and the second information, a first execution start time, a first execution period, a second execution start time, and a second execution period that minimize the total power consumption of the first in-vehicle control device, the second in-vehicle control device, and the third in-vehicle control device. Therefore, in this in-vehicle system, even with an increase in the number of functions executed in parallel, the power consumption of the in-vehicle control devices can be suppressed.
[0192] [5-2. Supplement 2]
[0193] In addition, this disclosure includes the following vehicles.
[0194] A vehicle includes: a scheduling device for scheduling functions executed by multiple vehicle control devices capable of communicating with each other via a communication bus; and the vehicle control devices connected to the communication bus. The vehicle further includes: an acquisition unit for acquiring first information and second information, the first information being used to determine a first execution start timing and a first execution cycle, and the second information being used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing at which a first function executed by a first vehicle control device and a second vehicle control device begins, the first execution cycle is the cycle for executing the first function, the second execution start timing is the timing at which a second function executed by the first vehicle control device and a third vehicle control device begins, and the second execution cycle is the cycle for executing the second function. A determination unit, based on the first information and the second information, determines the first execution start timing, the first execution cycle, the second execution start timing, and the second execution cycle that minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device. Thus, in this vehicle, even with an increase in the number of functions executed in parallel, the power consumption of the vehicle control devices can be suppressed.
[0195] [5-3. Supplement 3]
[0196] The embodiments disclosed herein are illustrative in all respects and are not intended to be restrictive. The scope of the invention is defined not by the above-described embodiments, but by the claims, including all modifications within the scope and equivalent meaning of the claims.
[0197] Label Explanation 1. Vehicle system 2 GW (Dispatch Unit) 3, 3a, 3b ECU (On-board Control Unit) 11a, 11b Communication I / F (Communication Interface) 12a and 12b communication buses 13a, 13b Communication I / F (Communication Interface) 21 MCU (Microcontroller Unit) 22 Control Department 23 Memory 24 Internal Bus 31 MCU (Microcontroller Unit) 32. Control Unit (Processor) 33 Memory 34 Peripheral Circuits 41 Cluster Table 51 Acquisition Department 52 Decision Department 53. Setting Department.
Claims
1. A scheduling device for scheduling functions performed by multiple vehicle-mounted control devices capable of communicating with each other via a communication bus, wherein, The scheduling device includes: The acquisition unit acquires first information and second information. The first information is used to determine a first execution start timing and a first execution cycle. The second information is used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing for starting a first function executed by a first vehicle control device and a second vehicle control device. The first execution cycle is the cycle for executing the first function. The second execution start timing is the timing for starting a second function executed by a first vehicle control device and a third vehicle control device. The second execution cycle is the cycle for executing the second function. The decision unit, based on the first information and the second information, determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle to minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device.
2. The scheduling device according to claim 1, wherein, The scheduling device further includes a setting unit, which sets the first execution start time and the first execution cycle determined by the decision unit to the first vehicle control device and the second vehicle control device, and sets the second execution start time and the second execution cycle determined by the decision unit to the first vehicle control device and the third vehicle control device.
3. The scheduling device according to claim 1 or claim 2, wherein, The decision unit determines a first setting range based on the first information, determines the first execution start time and the first execution cycle based on the first setting range, and determines a second setting range based on the second information, determines the second execution start time and the second execution cycle based on the second setting range. The first setting range is the range within which the first execution cycle should be limited, and the second setting range is the range within which the second execution cycle should be limited.
4. The scheduling device according to claim 3, wherein, The first setting range is determined based on the first cycle initial value and the first allowed range, and the second setting range is determined based on the second cycle initial value and the second allowed range. The first cycle initial value is the initial value of the cycle in which the first function is executed, the first allowed range is the range that is allowed to change from the first cycle initial value, the second cycle initial value is the initial value of the cycle in which the second function is executed, and the second allowed range is the range that is allowed to change from the second cycle initial value.
5. The scheduling device according to claim 4, wherein, The first information includes a first execution duration, which is the time from the start to the end of the first function in the first execution cycle. The second information includes a second execution duration, which is the time from the start to the end of the second function in the second execution cycle.
6. The scheduling device according to claim 5, wherein, Based on the first execution duration and the second execution duration, the decision unit calculates the power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device, and determines the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle that minimize the total power consumption.
7. The scheduling device according to any one of claims 1 to 6, wherein, The first information includes information indicating the restrictive conditions that limit the execution of the first function. The decision unit avoids the constraints to determine the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle.
8. The scheduling device according to claim 7, wherein, The constraints include conditions that restrict the first function and the second function from being executed concurrently in time.
9. The scheduling device according to claim 7, wherein, The constraints include at least one of the conditions related to the limitations on the hardware resources used by the first function and the conditions related to the limitations on the hardware resources used by the second function.
10. A control method used by a scheduling device, the scheduling device scheduling functions performed by multiple vehicle control devices capable of communicating with each other via a communication bus, wherein, The control method includes the following steps: Obtain first information and second information, wherein the first information is used to determine a first execution start timing and a first execution cycle, and the second information is used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing at which a first function is executed by a first vehicle control device and a second vehicle control device, and the first execution cycle is the cycle for executing the first function. The second execution start timing is the timing at which a second function is executed by a first vehicle control device and a third vehicle control device, and the second execution cycle is the cycle for executing the second function. Based on the first information and the second information, the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle are determined to minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device.
11. A control program used by a scheduling device, the scheduling device scheduling functions performed by a plurality of on-board control devices capable of communicating with each other via a communication bus, wherein, The control program is used to cause the computer to perform the following steps: Obtain first information and second information, wherein the first information is used to determine a first execution start timing and a first execution cycle, and the second information is used to determine a second execution start timing and a second execution cycle. The first execution start timing is the timing at which a first function is executed by a first vehicle control device and a second vehicle control device, and the first execution cycle is the cycle for executing the first function. The second execution start timing is the timing at which a second function is executed by a first vehicle control device and a third vehicle control device, and the second execution cycle is the cycle for executing the second function. Based on the first information and the second information, the first execution start time, the first execution cycle, the second execution start time, and the second execution cycle are determined to minimize the total power consumption of the first vehicle control device, the second vehicle control device, and the third vehicle control device.
Citation Information
Patent Citations
Sleep control system for automobile
JP2006151007A
Molding method of covered food and molding apparatus
JP2023051830A
