Vehicle control device and vehicle control method
The vehicle control device addresses load contention by predicting resource availability and providing controlled access to vehicle functions, preventing resource conflicts and shortages through its equipment management and API sections, ensuring efficient and reliable access for multiple systems.
Patent Information
- Application Number
- PCT/JP2024/017688
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
Conventional technologies are unable to effectively manage and control load contention when multiple systems access vehicle functions simultaneously, leading to resource shortages and conflicts.
A vehicle control device and method that includes an equipment management section, API section, state prediction section, and information generation section to predict resource availability and provide reference information to application software, allowing for controlled access to vehicle functions and preventing resource conflicts.
The solution enables each application software to use vehicle functions within available time periods, suppressing conflicting requests and ensuring resources are not overutilized, thereby preventing resource shortages and ensuring reliable access.
Smart Images

Figure JP2024017688_21112024_PF_FP_ABST
Abstract
Description
Vehicle control device and vehicle control method CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This international application claims priority based on Japanese Patent Application No. 2023-080018, filed with the Japan Patent Office on May 15, 2023, the entire contents of which are incorporated herein by reference.
[0002] The present disclosure relates to a technique for processing requests from application software that realizes services using vehicle functions.
[0003] Patent Document 1 describes a technology for collecting information only under circumstances specified by the server in a vehicle data collection system that collects various vehicle data from multiple vehicles via sensors mounted on the vehicles, in order to make effective use of system resources.
[0004] Patent No. 7156091
[0005] In the future, it is expected that multiple systems will access the same vehicle due to the widespread use of vehicle APIs. A vehicle API is an interface that provides vehicle functions to application software, etc., installed inside or outside the vehicle.
[0006] When multiple systems exist inside and outside a vehicle and each system runs application software, each system accesses the vehicle at its own timing, resulting in contention for access to the same vehicle. Conventional technology controls the load within a single system, but has been found to have the problem of being unable to control the load when there is contention with other systems.
[0007] The present disclosure provides a technique for suppressing conflicts among requests for access to vehicle functions from multiple systems.
[0008] One aspect of the present disclosure is a vehicle control device mounted on a vehicle. The vehicle control device includes an equipment management unit, an API unit, a state prediction unit, an information generation unit, and an information provision unit. The equipment management unit is configured to execute control of vehicle equipment that is equipment possessed by the vehicle and manage the state of the vehicle equipment. The API unit has function APIs, which are interfaces provided for each function, to receive requests from application software and realize functions using the vehicle equipment managed by the equipment management unit. The state prediction unit is configured to predict the state of resources possessed by the vehicle within a specified time range. The information generation unit is configured to generate reference information for each function API based on the prediction result by the state prediction unit, including a time period during which the function API can be used. The information provision unit is configured to provide the reference information generated by the information generation unit for the function API specified in a request from the application software.
[0009] According to the vehicle control device, application software can ascertain, via the information providing unit, the time periods during which the desired function APIs are available. Each application software uses the function APIs according to the ascertained time periods, thereby preventing conflicts between requests for the same resource from multiple application software. In other words, access requests to vehicle functions from multiple application software can be controlled so as not to cause a shortage of vehicle resources.
[0010] One aspect of the present disclosure is a vehicle control method executed by a computer mounted on a vehicle. In the vehicle control method, an equipment management unit included in the computer controls vehicle equipment and manages the status of the vehicle equipment. An API unit included in the computer accepts requests from application software and provides function APIs, which are interfaces provided for each function, to realize functions using the vehicle equipment managed by the equipment management unit. A state prediction unit included in the computer predicts the status of resources owned by the vehicle within a specified time range. An information generation unit included in the computer generates reference information for each function API, including a time period during which the function API can be used, based on the prediction result by the state prediction unit. An information provision unit included in the computer then provides the reference information generated by the information generation unit for the function API specified in the request from the application software to the requesting application software.
[0011] According to this vehicle control method, it is possible to obtain the same effects as those of the above-mentioned vehicle control device.
[0012] FIG. 1 is a block diagram showing the configuration of a vehicle control system. FIG. 2 is a block diagram showing the configuration of an ECU. FIG. 3 is a block diagram showing the configuration of a center. FIG. 4 is a block diagram showing the functional configuration of a vehicle control system. FIG. 5 is an explanatory diagram illustrating an example of the contents of required resource information. FIG. 6 is a flowchart showing the processing executed by a reservation arbitration unit. FIG. 7 is a sequence diagram showing the basic processing flow when a request occurs via a confirmation API and a reservation API. FIG. 8 is a sequence diagram showing the processing flow when there is a reservation conflict.
[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[0014] 1 includes an electronic control unit (ECU) group 100 mounted on a vehicle such as an automobile, and a center 35. The ECU group 100 includes a plurality of ECUs. In this embodiment, the ECU group 100 includes a first ECU 10, a second ECU 15, a third ECU 20, a fourth ECU 25, a fifth ECU 30, and sixth to thirteenth ECUs 41 to 48. The ECUs belonging to the ECU group 100 are connected to each other via in-vehicle communication (i.e., wired communication or wireless communication). The center 35 is provided outside the vehicle and is connected to the ECU group 100 via out-of-vehicle communication (i.e., wireless communication).
[0015] The first ECU 10 has a relay function for in-vehicle communications and realizes coordinated control of the entire vehicle by controlling the second to fifth ECUs 15 to 30. The first ECU 10 also controls communications with the center 35, thereby realizing coordinated control of the entire system including the center 35.
[0016] The first ECU 10 and the third to fifth ECUs 20 to 30 are provided for each domain, which is divided according to the vehicle's function, and mainly control multiple ECUs (i.e., any of the sixth to thirteenth ECUs 41 to 48) that exist within that domain. The domains are, for example, the powertrain, the body, the chassis, and the cockpit.
[0017] The sixth to thirteenth ECUs 41 to 48 control vehicle equipment that is equipment mounted on the vehicle.
[0018] The vehicle equipment may include hardware such as sensors and actuators, as well as various storage devices for storing data and software for realizing certain functions.
[0019] The first ECU 10 and the third to fifth ECUs 20-30 are connected to the sixth to thirteenth ECUs 41-48 via lower-level networks (e.g., CAN) that are individually provided. CAN is an abbreviation for Controller Area Network and is a registered trademark. The first ECU 10 and the third to fifth ECUs 20-30 have the function of centrally managing access rights to the sixth to thirteenth ECUs 41-48 and authenticating users.
[0020] In another embodiment, the vehicle control system 1 may include the ECU group 100, and the center 35 may be omitted. In another embodiment, the number of ECUs belonging to the ECU group 100 may be 14 or more, or 13 or less. In another embodiment, there may be multiple centers 35.
[0021] [2. Hardware Configuration] Next, the hardware configuration of each ECU belonging to the ECU group 100 and the center 35 will be described. Each ECU belonging to the ECU group 100 has the same hardware configuration. Therefore, here, the configuration of the first ECU 10 will be described as a representative.
[0022] As shown in FIG. 2 , the first ECU 10 includes a microcomputer 11, a vehicle interface (hereinafter, I / F) 12, and a communication unit 13. The microcomputer 11 includes a CPU 11a, a ROM 11b, and a RAM 11c. The various functions of the first ECU 10 are realized by the CPU 11a executing a program stored in a non-transitory physical recording medium. In this embodiment, the ROM 11b corresponds to the non-transitory physical recording medium storing the program. Furthermore, the execution of this program causes a method corresponding to the program to be performed.
[0023] The vehicle I / F 12 connects to other ECUs and in-vehicle devices via an in-vehicle network or the like, and acquires various information from the other ECUs and in-vehicle devices. The in-vehicle network may include a Controller Area Network (hereinafter, CAN) and Ethernet. CAN is a registered trademark. Ethernet is a registered trademark.
[0024] The communication unit 13 performs data communication with the center 35 etc. via wireless communication over a wide area communication network. However, it is not necessary for all ECUs belonging to the ECU group 100 to have the communication unit 13, and it may be provided in only one or some of the ECUs.
[0025] The method of realizing the various functions of the first ECU 10 is not limited to software, and some or all of the functions may be realized using one or more hardware elements. For example, if the functions are realized by electronic circuits that are hardware, the electronic circuits may be digital circuits including multiple logic circuits, analog circuits, or a combination of digital and analog circuits.
[0026] As shown in Figure 3, the center 35 includes a microcomputer 36, a communication unit 37, and a storage unit 38. The microcomputer 36 includes a CPU 36a, a ROM 36b, and a RAM 36c. The various functions of the center 35 are realized by the CPU 36a executing a program stored in a non-transitory physical recording medium. In this embodiment, the ROM 36b corresponds to the non-transitory physical recording medium storing the program. Furthermore, by executing this program, a method corresponding to the program is performed.
[0027] The communication unit 37 performs data communication with the ECU group 100 via a wide area communication network. The storage unit 38 is a storage device for storing vehicle data and the like provided by the ECU group 100.
[0028] The method of realizing the various functions of the center 35 is not limited to software, and some or all of the elements may be realized using one or more pieces of hardware. For example, if the functions are realized by electronic circuits that are hardware, the electronic circuits may be realized by digital circuits including multiple logic circuits, or analog circuits, or a combination of digital and analog circuits.
[0029] 1 , various functions of the vehicle control system 1 will be described. The vehicle control system 1 has the functions of an equipment management unit 9 in a first layer, a status management unit 8 in a second layer, a vehicle service unit 7 in a third layer, and a service provision unit 6 in a fourth layer. In other words, the software architecture of the vehicle control system 1 is hierarchical in four layers. The above-mentioned functions of the vehicle control system 1 are shared by each ECU belonging to the ECU group 100 and the center 35.
[0030] The equipment management unit 9 includes a plurality of control units 91 to 99 corresponding to a plurality of types of vehicle equipment, such as an on-board camera, an on-board millimeter-wave radar, brakes, a steering wheel, a display, a speaker, various lights, an on-board air conditioner, and an electric power seat.
[0031] Specifically, the equipment management unit 9 includes a camera control unit 91, a millimeter wave control unit 92, a brake control unit 93, a steering control unit 94, a display control unit 95, a sound control unit 96, a light control unit 97, a Heating Ventilation and Air-Conditioning (hereinafter referred to as HVAC) control unit 98, and a seat control unit 99. The vehicle equipment is individually controlled by the corresponding control unit among the control units 91 to 99.
[0032] The camera control unit 91 controls the exposure of the vehicle-mounted camera and acquires images captured by the vehicle-mounted camera. In this embodiment, the sixth ECU 91 includes the camera control unit 91.
[0033] The millimeter wave control unit 92 controls the on-board millimeter wave radar and acquires the detection results detected by the millimeter wave radar. In this embodiment, the seventh ECU 92 includes the millimeter wave control unit 92.
[0034] The brake control unit 93 controls the brakes. In this embodiment, the eighth ECU 93 includes the brake control unit 93.
[0035] The steering control unit 94 controls the steering. In this embodiment, the ninth ECU 44 includes the steering control unit 94.
[0036] The display control unit 95 controls indicators (for example, meters, warning lights, etc.) In the present embodiment, the tenth ECU 45 includes the display control unit 95.
[0037] The sound control unit 96 controls the speaker to output sounds such as warning sounds, voices, etc. In this embodiment, the eleventh ECU 46 includes the sound control unit 96.
[0038] The light control unit 97 controls various lights mounted on the vehicle. In this embodiment, the fifth ECU 30 includes the light control unit 97.
[0039] The HAVC control unit 98 controls the in-vehicle air conditioner. In this embodiment, the twelfth ECU 47 includes the HAVC control unit 98.
[0040] The seat control unit 99 controls an electric power seat of the vehicle. In this embodiment, the 13th ECU 48 includes the seat control unit 99.
[0041] The equipment management unit 9 operates the vehicle equipment in accordance with the operation instruction from the status management unit 8 and notifies the status management unit 8 of the operation result. For example, if the vehicle equipment is an actuator, the operation result may indicate that the actuator has completed normally or abnormally. If the vehicle equipment is a sensor, the operation result may indicate data detected by the sensor. If the vehicle equipment is a storage device, the result notification may indicate data read from the storage device.
[0042] The equipment management unit 9 may be configured to operate the vehicle equipment in accordance with an operation instruction from the status management unit 8, as well as to autonomously detect the status of the vehicle equipment and notify the status management unit 8 of the status.
[0043] [3-2. Service Providing Unit] The service providing unit 6 executes application software (hereinafter, "apps") 61 to 64 to realize various functions, such as information collection, theft prevention, and remote control, by utilizing the vehicle equipment managed by the equipment management unit 9.
[0044] In this embodiment, the first ECU 10, the second ECU 15, and the center 35 each include a service providing unit 6. The ROM 11b of the first ECU 10 stores apps 61 and 62. The ROM 11b of the second ECU 15 stores an app 63. The ROM 36b of the center 35 stores an app 64.
[0045] The applications 61 to 64 are basically configured to realize the intended services by utilizing the functions of the vehicle equipment via the API unit 71 that constitutes the vehicle service unit 7 .
[0046] The apps 61 to 64 are not dedicated programs for executing processes suited to a specific vehicle model, a specific grade, or the like, but are general-purpose programs for executing processes suited to many vehicle models, grades, and the like. Therefore, the apps 61 to 64 are written using publicly available modeled vehicle functions so that they can be created without considering the vehicle equipment and performance of individual vehicles. In other words, the apps 61 to 64 can be easily developed by third parties, who are app providers other than OEMs, and the developed apps can be widely released. Therefore, a vehicle user who owns a vehicle equipped with the ECU group 100 can install an app released by a third party into any of the ECU group 100 via a wide-area communication network or the like. Furthermore, the vehicle user can add or modify the apps 61 to 64 as desired.
[0047] In the case of an app used to provide a service that acquires vehicle information from many vehicles and analyzes the vehicle behavior, the driver's driving operations, and the like, a service provider that provides the app may, with the permission of the vehicle user, install the app in one of the ECU group 100. Furthermore, access rights to individual APIs belonging to the API unit 71 from apps installed in the center 35 by the service provider or the like may be restricted by the vehicle user for each service provider or each app.
[0048] [3-3. Vehicle Service Unit] The vehicle service unit 7 includes an Application Programming Interface (hereinafter, API) unit 71. In this embodiment, the first ECU 10 includes the API unit 71. The API unit 71 includes a plurality of vehicle APIs. The vehicle APIs are interfaces provided to the apps 61 to 64 belonging to the service providing unit 6 for accessing subdivided vehicle functions.
[0049] The vehicle API has a standardized syntax that allows requests to be written without depending on a specific vehicle model or grade. When using a function provided by the vehicle, the applications 61 to 64 send a first command using the vehicle API. The first command is a command that indicates information required when using the vehicle API.
[0050] The first command may include a command indicating the request content, a command such as an argument, a function call, etc. The first command may also include priority information indicating which command should be given priority for processing. The priority may be set, for example, depending on whether the manufacturer of the application requesting the first command is an OEM or a third party other than the OEM. OEM stands for Original Equipment Manufacturer. Specifically, an OEM may be given a higher priority than a third party. Among OEMs, a vehicle manufacturer may be given a higher priority than a parts / application manufacturer. The priority may also be set according to the type of control.
[0051] The syntax of the vehicle API, i.e., the format of the first command, is written using publicly available modeled vehicle functions so that the first command can be created without considering the vehicle equipment and performance of each vehicle, similar to the apps 61 to 64. In other words, the first command describes the function to be realized abstractly without specifying the vehicle equipment or using expressions that depend on the performance of the vehicle equipment. For example, the first command describes the content to turn on the car finder, but does not specify specific matters that depend on each vehicle, such as how to control which vehicle equipment, such as specifying which lights to turn on out of multiple lights installed in the vehicle.
[0052] Upon receiving the first command, the API unit 71 determines whether the first command can be accepted from a formal standpoint, such as the format of the first command and the access rights held by the requester of the first command. If the API unit 71 determines that the first command can be accepted, it converts the first command into a second command written in a format suitable for the model and grade of the target vehicle, and transmits the second command to the status management unit 8. In other words, the API unit 71 has a function of converting the first command written in a standard format handled by the service providing unit 6 into a second command written in a format specific to the vehicle handled by the status management unit 8 and the equipment management unit 9. The second command is assigned an app ID that identifies the app that sent the first command (hereinafter, the requester app). The API unit 71 also has a function of transferring a result notification, which is a response from the status management unit 8 to the requester app, to the requester app.
[0053] The API unit 71 includes a function API 72 , a confirmation API 73 , and a reservation API 74 .
[0054] The function API 72 is a vehicle API that is used when requesting control of vehicle equipment.
[0055] The confirmation API 73 is a vehicle API used to confirm the available time periods, etc., for the specified function API 72.
[0056] The reservation API 74 is a vehicle API used when reserving the use of the specified function API 72 by specifying start conditions, end conditions, etc.
[0057] 3-4. State Management Unit As shown in FIG. 4, the state management unit 8 includes a process execution unit 80 and a reservation management unit 85.
[0058] The processing execution unit 80 processes requests from the service providing unit 6 via the function API 72 .
[0059] The reservation management unit 85 processes requests from the service providing unit 6 via the confirmation API 73 and reservation API 74 .
[0060] [3-4-1. Processing Execution Unit] The processing execution unit 80 includes a state recognition unit 81, a motor system equipment control unit 82, a human machine interface (hereinafter referred to as HMI) system state recognition unit 83, and a body system control unit 84.
[0061] The units 81 to 84 belonging to the process execution unit 80 are classified not by implementation means (for example, control units 91 to 99) that are likely to depend on variations in the vehicle, but by vehicle operations that are likely to be requested by the service providing unit 6. In this embodiment, the units 81 to 84 belonging to the process execution unit 80 are provided in either the first ECU 10 or the third to fifth ECUs 30 that manage the respective domains of the vehicle, as shown in FIG.
[0062] The state recognition unit 81 is responsible for recognizing the situation of the vehicle itself and its surroundings, such as the positions of the vehicle and pedestrians. The state recognition unit 81 controls, for example, vehicle equipment belonging to the camera control unit 91 and the millimeter wave control unit 92. In this embodiment, the third ECU 20 includes the state recognition unit 81.
[0063] The motion system equipment control unit 82 corresponds to the driving system operations of the vehicle, such as turning, running, stopping, etc. The motion system equipment control unit 82 controls, for example, vehicle equipment belonging to a brake control unit 93 and a steering control unit 94. In this embodiment, the first ECU 10 includes the motion system equipment control unit 82.
[0064] The HMI system status recognition unit 83 corresponds to vehicle operations related to the presentation of information to the user. The HMI system status recognition unit 83 controls, for example, vehicle equipment belonging to the display control unit 95 and the sound control unit 96. In this embodiment, the fourth ECU 25 includes the HMI system status recognition unit 83.
[0065] The body system control unit 84 controls the vehicle's body system operations related to the vehicle environment. For example, the body system control unit 84 controls vehicle equipment belonging to a light control unit 97, an HVAC control unit 98, and a seat control unit 99. In this embodiment, the fifth ECU 30 includes the body system control unit 84.
[0066] When the process execution unit 80 receives a request (i.e., the second command) from the vehicle service unit 7, it determines whether the state of the vehicle is suitable for executing the second command, and if so, instructs the equipment management unit 9 to operate the target equipment. The vehicle state suitable for executing the second command may include the target equipment being capable of realizing the function required by the second command, the execution of the second command not being prohibited in a scene estimated from the vehicle state, etc.
[0067] The processing execution unit 80 has a function of outputting an operation instruction for the target equipment to the equipment management unit 9 and providing the operation result returned from the equipment management unit 9 to the vehicle service unit 7 as a result notification for the second command. The result notification may use individual operation results as they are, or may be used after integrating multiple operation results and converting them into highly abstract data.
[0068] For example, the processing execution unit 80 may receive a request from the vehicle service unit 7 to collect information to understand the vehicle status, and may obtain data from a plurality of vehicle equipment as operation results from the equipment management unit 9. If data such as "vehicle speed 0 km / h," "shift position P," and "driver absent from the vehicle" are obtained as operation results, the processing execution unit 80 may convert the data into data indicating that "the vehicle is parked," and may transmit the converted data to the vehicle service unit 7 as a result notification.
[0069] Reservation Management Unit] The reservation management unit 85 is provided in the first ECU 10. However, the reservation management unit 85 may be provided in an ECU other than the first ECU 10. As shown in FIG. 4 , the reservation management unit 85 includes a reservation arbitration unit 851, a state prediction unit 852, and an information storage unit 853.
[0070] The information storage unit 853 stores required resource information and reservation information.
[0071] The required resource information is information that associates an API-ID that identifies a function API 72 with resources required to execute a process associated with that function API 72. Specifically, as shown in Fig. 5, the resources required to execute a process include information such as "equipment used," "processing content," "CPU processing load," "required data volume," "power consumption," "communication volume," and "execution time."
[0072] "Equipment in use" indicates the ECU that executes the process, the actuators and sensors that are the processing targets, etc. "Processing content" indicates the processing required for each piece of equipment in use. "CPU processing load" indicates the processing load on the ECU indicated in "Equipment in use". "Required data capacity" indicates the free memory capacity required for processing in the ECU indicated in "Equipment in use". "Power consumption" indicates the power consumption for each piece of equipment indicated in "Equipment in use". "Communication volume" indicates the communication volume required for uploading data and the communication volume required for downloading data when communication with an external server is required. "Execution time" indicates the average processing time for each process indicated in "Processing content".
[0073] The reservation information is information relating to a reservation for use of the function API 72. The reservation information is set in accordance with a request from the service providing unit 6 using the reservation API 74. The reservation information includes the function API 72 that identifies the function API 72 that is the target of the reservation, an application ID that identifies the application that made the reservation, the start time and end time of the reservation, etc.
[0074] The state prediction unit 852 responds with a predicted result of the usage state of vehicle equipment (i.e., resources) in response to an inquiry from the reservation arbitration unit 851. The period to be predicted may be a specified time range (e.g., 24 hours) from the current time point when the request is received, or may be a time range specified by an instruction from the reservation arbitration unit 851.
[0075] The resources to be predicted may include "power status," "CPU usage rate," "battery level," "free data capacity," "device availability," "communication availability," and the like.
[0076] The "power status" may include information indicating whether the IG is ON, ACC, or OFF, as well as information indicating the connection status of the charging plug. The "CPU usage rate" is information expressing, in percentage, the usage rate of the CPU installed in the first ECU 10, which executes the processes of the vehicle service unit 7 and the reservation management unit 85 of the status management unit 8. The "CPU usage rate" may also include information on the usage rate of the CPU installed in each ECU other than the first ECU 10. The "battery remaining capacity" is information expressing, in percentage, the remaining capacity of the vehicle battery. The "free data capacity" is information indicating the free memory capacity available for processing. The "equipment availability" is information indicating the results of a determination of whether the equipment is available, including whether the equipment is malfunctioning and whether the equipment is operating. The equipment indicated as "equipment availability" may include special image processing, which requires a high processing load. The "communication availability" is information indicating the communication status with an external server. For example, the occupancy rate of the communication channel used for communication with the external server for each application may be indicated.
[0077] The status prediction unit 852 repeatedly acquires the status of the in-vehicle equipment from the equipment management unit 9 and accumulates the results of the aggregation using a predetermined method. For example, the aggregation method uses the on / off timing of the vehicle's ignition switch as a starting point and aggregates the elapsed time from the starting point as an index. Furthermore, the aggregated values may be aggregated individually for each day of the week, each season, each driver, each route, or each destination, for example. The route may include, for example, a commuter route and other routes besides a commuter route.
[0078] When receiving an inquiry from the reservation arbitration unit 851, the state prediction unit 852 predicts the usage status of each resource and returns the prediction result to the reservation arbitration unit 851. The prediction of the usage status of each resource takes into consideration the aggregated value of past usage status and the reservation information stored in the information storage unit 853. Furthermore, the prediction of the usage status of each resource may use information such as whether each application has access authority to each API, the driving route set by the navigation device, and the estimated arrival time. Furthermore, the prediction of the usage status of each resource may use information such as a drop-off prediction extracted from an image captured by a camera showing the interior of the vehicle, and information about the driver's schedule obtained by linking with the calendar of a mobile terminal.
[0079] Here, a method for predicting the utilization status of a source in the status prediction unit 852 will be described.
[0080] For "power supply status," if the current power supply status is IG-ON or the charging plug is connected, the probability that the current power supply status is IG-ON is set to 100%, and the predicted value S1 is gradually reduced as time passes.
[0081] There are two methods for decreasing the predicted value S1: one is to decrease it simply in inverse proportion to the passage of time, as shown in equation (1), and the other is to decrease it in accordance with a preset first table value f1(t), as shown in equation (2), where t is time, and f1(t) is a value between 0 and 1, and is set so that the value changes with the passage of time.
[0082] S1[%]=100 / t (1) S1[%]=100×f1(t) (2) The first table value f1(t) may be set from past history. In this case, the first table value f1(t) may be set, for example, by calculating the average time from when the IG is turned on to when the IG is turned off from past history, and monotonically decreasing the value of the first table value f1(t) until it becomes approximately zero over the calculated average time.
[0083] Furthermore, when the current power supply state is IG-ON and the travel route has been set by the navigation device, the first table value f1(t) may be set as follows: That is, the first table value f1(t) may be set to a small value up to the estimated arrival time in the route guidance of the navigation device, and to a large value after the estimated arrival time.
[0084] Furthermore, when the current power supply state is that the charging plug is connected, the first table value f1(t) may be set to a small value until the scheduled charging completion time according to the charging plan, and to a large value after the scheduled charging completion time.
[0085] The predicted value S2 of "CPU usage" may be calculated according to equation (3) using a second table value f2(t) that represents the CPU usage predicted from the application usage record or application usage plan. The second table value f2(t) takes a value between 0 and 1.
[0086] S2 [%] = 100 × f2(t) (3) When setting the second table value f2(t) based on the application usage history, the application usage history is tallied on a time axis representing the elapsed time from the time when the IG was turned on, and the probability that each application will be used at each time is calculated. The second table value f2(t) is set based on this probability and the CPU usage rate when each application is used. The second table value f2(t) may be set individually for each application.
[0087] The second table value f2(t) may be set using an application usage plan instead of the application usage record.
[0088] The predicted value S3 of the "battery remaining capacity" may be calculated according to equation (4) using the current battery remaining capacity Qc [%] as a reference, and using a third table value f3(t) that is set based on the application usage history or application usage plan and the power consumption required by each application.
[0089] S3 [%] = Qc - 100 × f3(t) (4) The third table value f3(t) is set so that the attenuation amount increases as the probability that an app will be used at each time point increases or as the power consumption of the used app increases. Furthermore, when a driving route is set by a navigation device, the third table value f3(t) may be set taking into consideration the usage status of apps predicted from the driving route, etc.
[0090] The predicted value S4 of "data capacity" may be calculated according to equation (5) using a fourth table value f4(t) that is set based on the application usage history or usage plan and the data capacity required by each application when executing processing, with the maximum value of available data capacity being Dm.
[0091] S4[%]=Dm×f4(t) (5) The fourth table value f4(t) is set based on the probability of each app being used at each time, which is calculated from the results of aggregating app usage records on a time axis representing the elapsed time from the time when the IG is turned on, and the data capacity required to run each app. An app usage plan may be used instead of the app usage records.
[0092] The predicted values S5 and S6 of "equipment usability" may be calculated using a fifth table value f5(t) and a sixth table value f6(t) that are set based on the usage history or usage plan of equipment that may be accessed by multiple apps (e.g., a camera, special image processing, etc.). The predicted value S5 is the probability that the equipment is not in use but is available, and may be calculated according to formula (6). The predicted value S6 is the probability that the equipment is in use and is unavailable, and may be calculated according to formula (7).
[0093] S5[%] = 100 × f5(t) (6) S6[%] = 100 × f6(t) (7) The predicted value S7 of "communication availability" may be calculated using equation (8) with the current communication state as C[%], or may be calculated using equation (9) with a seventh table value f7(t) representing the communication state estimated from the vehicle's driving plan. The current communication state C may be, for example, the ratio of the measured actual communication speed to the maximum communication speed. The seventh table value f7(t) takes a value between 0 and 1.
[0094] S7[%] = C / t (8) S7[%] = 100 × f7(t) (9) When the driving route is set by the navigation device, the seventh table value f7(t) may be set to a smaller value depending on the surrounding environment of the driving route. For example, the seventh table value f7(t) may be set to a smaller value at the scheduled time of passing through a tunnel or a group of buildings because the communication conditions will deteriorate.
[0095] The first to seventh table values f1(t) to f7(t) may be prepared individually for each season, each time period, and each driver.
[0096] The reservation arbitration unit 851 executes a reservation arbitration process for processing a request from the service providing unit 6 via the confirmation API 73 or reservation API 74 of the API unit 71 .
[0097] 4. Processing The reservation arbitration processing executed by the reservation arbitration unit 851 will be described with reference to the flowchart of Fig. 6. The reservation arbitration processing is started upon receiving a second command from the vehicle service unit 7.
[0098] When the reservation arbitration process is started, in S110, the reservation arbitration unit 851 determines whether the received second command is a "resource confirmation" request. A "resource confirmation" request is a request input via the confirmation API 73. The "resource confirmation" request includes an application ID that identifies the requesting application and an API_ID that is identification information that identifies the function API 72 to be used (hereinafter, the API to be confirmed). The "resource confirmation" request may also include information that specifies the time period to be predicted.
[0099] If the reservation arbitration unit 851 determines that the received second command is a "resource confirmation" request, it proceeds to S120, and if it determines that the second command is not a "resource confirmation" request, it proceeds to S150.
[0100] In S120, the reservation arbitration unit 851 refers to the required resource information stored in the information storage unit 853 and acquires information about the resources required to execute the API to be confirmed (hereinafter, required resources).
[0101] In the next step S130, the reservation arbitration unit 851 queries the status prediction unit 852 to obtain a resource usage forecast. The resource usage forecast indicates, for example, fluctuations in resource usage forecasts for each resource within a specified time range. If a time period is specified in the "resource confirmation" request, the time range is determined in accordance with that specification. If no time period is specified, the usage forecast for a certain period of time (e.g., 24 hours) from the present time is displayed.
[0102] In the next step S140, the reservation arbitration unit 851 generates a "resource prediction answer" notification based on the information about the required resources acquired in S120 and the resource usage forecast acquired in S130, and sends the notification to the requesting application via the API unit 71, thereby completing the process. The "resource prediction answer" notification includes an API_ID, which is identification information for identifying the API to be checked, and the start and end times of a time period during which the API to be checked can be used (hereinafter referred to as the "available time period"). The available time period is a time period extracted based on the condition that the available amount of resources estimated from the resource usage forecast has a surplus of at least a predetermined lower limit compared to the required amount of resources for the API to be checked. There may be multiple available time periods. The "resource prediction answer" notification may also include the probability that the API to be checked can actually be used during the available time period (hereinafter referred to as the "available probability") and the resource usage forecast acquired in S130. The information indicating the available time slot, the availability probability, and the resource usage prediction added to the "resource prediction answer" notification correspond to the reference information of this disclosure.
[0103] In S150, the reservation arbitration unit 851 determines whether the received second command is an "API usage reservation" request. An "API usage reservation" request is a request input via the reservation API 74. The "API usage reservation" request includes an application ID (application ID) identifying the requesting application, an API ID identifying the functional API 72 to be reserved (hereinafter, the "reservation target API"), and usage information indicating the usage conditions of the reservation target API. The usage information includes at least usage time zone information specifying the usage time zone of the reservation target API. The usage time zone information includes a start condition for starting usage of the reservation target API and an end condition for ending usage. The start condition and end condition may be specific times or the occurrence of some event, such as ignition-on detection or arrival at a destination. The end condition may be the elapsed time since the start of usage. The usage information may optionally include information specifying the resource to be used (hereinafter, "designated resource"). The designated resource may include, for example, an upper limit of the time allowed for communication with an external server, such as the center 35.
[0104] If the reservation arbitration unit 851 determines that the second command is an "API usage reservation" request, it proceeds to S160, and if it determines that the second command is not an "API usage reservation" request, it terminates the process.
[0105] In S160, the reservation arbitration unit 851 acquires information about the resources required by the reservation target API in the same manner as in S120. At this time, if the start and end conditions of the usage time period information are not specified as specific times, the reservation arbitration unit 851 performs processing to convert them into a start time estimated from the start conditions and an end time estimated from the end conditions.
[0106] In the next step S170, the reservation arbitration unit 851 obtains a resource usage forecast in the same manner as in the previous step S130.
[0107] In the next step S180, the reservation arbitration unit 851 determines whether the resources required to execute the reserved API can be prepared during the usage time period indicated by the usage time period information, i.e., whether the resources are sufficient. Specifically, if the available amount of resources identified from the resource usage forecast obtained in S170 throughout the usage time period is greater than the required amount of resources for the reserved API obtained in S160, it is determined that the resources are sufficient. In other words, whether the reserved API can be executed is determined based on whether the resources are sufficient.
[0108] If the reservation arbitration unit 851 determines that there are sufficient resources to execute the reservation API during the usage time period, it proceeds to S190, and if it determines that there are insufficient resources, it proceeds to S200.
[0109] In S190, the reservation arbitration unit 851 sends a "reservation successful" notification indicating that the usage reservation based on the "API usage reservation" request (hereinafter referred to as "reservation acceptance") has been accepted to the application that requested the acceptance reservation via the API unit 71. Furthermore, the reservation arbitration unit 851 stores reservation information indicating the content of the accepted reservation in the information storage unit 853, and ends the processing. The "reservation successful" notification indicates the API-ID of the API to be reserved, the reservation start time, the reservation end time, etc. The reservation information stored in the information storage unit 853 is reflected in the resource usage status prediction by the status prediction unit 852.
[0110] In S200, the reservation arbitration unit 851 determines whether or not there is a conflicting reservation, which is a usage reservation with a lower priority than the accepted reservation, among the reservation information stored in the information storage unit 853. A conflicting reservation is another usage reservation that has already been confirmed and whose usage time period overlaps with the accepted reservation. Priority may be assigned to the requesting application, the API to be reserved, the application manufacturer, or whether the application is installed in the vehicle or an external server. The shorter the reservation time, the higher the priority. Priority may also be differentiated depending on whether or not there is a charge and the level of charge.
[0111] If there is a competing reservation with a lower priority than the accepted reservation, the reservation arbitration unit 851 shifts the process to S210, and if there is no competing reservation with a lower priority, the reservation arbitration unit 851 shifts the process to S240.
[0112] In S210, the reservation arbitration unit 851 sends a "reservation established" notification to the application that requested the accepted reservation via the API unit 71, and also sends a "reservation canceled" notification to the application that requested the conflicting reservation (hereinafter referred to as the conflicting application) via the API unit 71. The "reservation canceled" notification indicates the details of the canceled use reservation. The "reservation canceled" notification may also indicate the reason why the reservation was canceled. Furthermore, the reservation arbitration unit 851 stores reservation information indicating the details of the established reservation in the information storage unit 853, and erases the reservation information regarding the conflicting reservation from the information storage unit 853.
[0113] In the next S220, when the accepted reservation that has been confirmed is executed, the reservation arbitration unit 851 determines whether the conflicting reservation can be executed under conditions. If it can be executed under conditions, the process proceeds to S230. If it cannot be executed even under conditions, the process ends. If it is determined that the conflicting reservation can be executed under conditions, this may include cases where the conflicting reservation can be executed by changing the time period, or cases where the conflicting reservation can be executed by limiting the amount of resource usage per unit time, thereby allowing for an increase in the time required for processing. Note that the amount of resource usage may include CPU usage, communication volume with the center 35, etc.
[0114] In S230, the reservation arbitration unit 851 sends a "reservation change proposal" notification to the competing application via the API unit 71. The "reservation change proposal" notification indicates the API-ID of the API to be reserved, the application ID of the requesting application, and the proposed content of the reservation change. The proposed content indicates the time slots that can be changed, and the start and end times that will be changed by restricting resources, etc.
[0115] Based on the content of the received "reservation change proposal" notification, the competing application may send a new "API use reservation" request with content that accepts the proposal.
[0116] In S240, the reservation arbitration unit 851 determines whether the accepted reservation can be executed under conditions, and if it can be executed under conditions, the process proceeds to S250, and if it cannot be executed even under conditions, the process proceeds to S260. The determination of whether it can be executed under conditions is the same as that described in S220.
[0117] In S250, the reservation arbitration unit 851 transmits a "reservation change proposal" notification to the application that has made the reservation request, and ends the process.
[0118] In S260, the reservation arbitration unit 851 sends a "reservation not established" notification to the application that requested the reservation, and ends the process. The "reservation not established" notification includes the API-ID of the API that is the target of the reservation and the application ID of the application that requested the reservation. The "reservation not established" notification may also include information indicating the reason for the failure.
[0119] Here, we will provide an example of the contents of a reservation change proposal in the case where executing the reserved API under the conditions specified in the "API usage reservation" request from the requesting application may result in insufficient CPU usage, communication volume, or data capacity, making it impossible to execute as requested.
[0120] For example, if the conditions specified in the "API usage reservation" request are to take, process, and upload an image once per second for five consecutive minutes, it is proposed to change the capture interval to a longer interval (for example, once per two seconds). In this case, the length of the time period during which the reserved API is used may be changed in accordance with the change in the capture interval.
[0121] Furthermore, if the conditions indicated in the "API usage reservation" request are, for example, that data be downloaded via wireless communication (i.e., OTA) in five minutes, it is proposed to modify the request to extend the allowable download time (for example, to one hour).
[0122] 3. Operation 3-1. Basic Operation Next, the basic operation of the vehicle control system 1 will be described with reference to the sequence diagram of FIG.
[0123] As shown in FIG. 7, in S10, the application A belonging to the service providing unit 6 uses the confirmation API 73 to send a "resource confirmation" request in the form of a first command to the API unit 71 of the vehicle service unit 7.
[0124] The API unit 71 performs a format check and an authority check on the received "resource check" request, and if both are determined to be conforming, converts the "resource check" request from the first command format to the second command format. Then, in S11, the API unit 71 transmits the "resource check" request converted to the second command format to the reservation arbitration unit 851 of the status management unit 8.
[0125] When the reservation arbitration unit 851 receives the "resource confirmation" request converted into the second command, in S12 it acquires the required resources for the API to be confirmed, which is identified from the API_ID indicated in the "resource confirmation" request, from the information storage unit 853. The reservation arbitration unit 851 further transmits an "inquiry" to the state prediction unit 852 in S13.
[0126] When the status prediction unit 852 receives an "inquiry" from the reservation arbitration unit 851, it predicts the resource usage status in S14, and returns an "answer" indicating the prediction result to the reservation arbitration unit 851 in S15.
[0127] When the reservation arbitration unit 851 receives an "answer" to the "inquiry" from the state prediction unit 852, in S16, it extracts an available time slot, which is information to be sent to the requesting application, based on the prediction result indicated in the "answer" and the required resources acquired in S12. Furthermore, in S17, the reservation arbitration unit 851 transmits a "resource prediction answer" notification indicating the information extracted in S16 to the API unit 71.
[0128] In S18, the API unit 71 transmits the "resource prediction response" notification received from the reservation arbitration unit 851 to application A, which is the application that has made the "resource confirmation" request.
[0129] In S20, application A uses the reservation API 74 to send an "API usage reservation" request in the form of a first command to the API unit 71. The content of the "API usage reservation" request may be set in consideration of the information indicated in the "resource prediction answer" notification, or may be set independently of the "resource prediction answer" notification.
[0130] When the API unit 71 receives the "API usage reservation" request, it performs a format check and an authority check in S21, similar to the case of a "resource confirmation" request. If the check results in a match, it converts the "API usage reservation" request from the first command format to the second command format and sends it to the reservation arbitration unit 851.
[0131] When the reservation arbitration unit 851 receives the "API usage reservation" request, in S22 it obtains the necessary resources for the API to be reserved, which is identified from the API_ID indicated in the "API usage reservation" request, from the information storage unit 853. The reservation arbitration unit 851 further transmits an "inquiry" to the state prediction unit 852 in S23.
[0132] When the status prediction unit 852 receives an "inquiry" from the reservation arbitration unit 851, it predicts the resource usage status in S24, and returns an "answer" indicating the prediction result to the reservation arbitration unit 851 in S25.
[0133] When the reservation arbitration unit 851 receives an "answer" to the "inquiry" from the status prediction unit 852, it determines in S26 whether or not the reservation can be made. The determination of whether or not the reservation can be made is based on the prediction result indicated in the "answer," the start and end conditions indicated in the "API usage reservation" request, and the required resources acquired in S22.
[0134] If the result of determining whether the reservation can be made shows that the API to be reserved can be executed under the start and end conditions indicated in the "API usage reservation" request, the reservation arbitration unit 851 sends a "reservation successful" notification to the API unit 71. The reservation arbitration unit 851 further stores reservation information indicating the content of the successful reservation in the information storage unit 853.
[0135] In S29, the API unit 71 transmits the "reservation established" notification received from the reservation arbitration unit 851 to application A, which is the application that has made the "API usage reservation" request.
[0136] 8, the operation when a conflicting reservation exists during reservation availability determination will be described. Here, it is assumed that application A has a completed usage reservation, and application B has sent an "API usage reservation" request to API unit 71, which uses the same resource as application A's usage reservation.
[0137] First, a case where a reservation for use by application B can be executed regardless of a reservation for use by application A will be described.
[0138] 8, in S30, application B transmits an "API usage reservation" request. Thereafter, the processes in S32 to S38 performed by the API unit 71, reservation arbitration unit 851, and state prediction unit 852 are the same as the processes in S21 to S28 described above.
[0139] However, in S36, even if the competing application A is executed at the same time, it is determined that the reservation is possible because there is a surplus of resources to be used. Also, in S38, the reservation arbitration unit 851 stores reservation information indicating the contents of the reservation established by the "API usage reservation" request from application B in the information storage unit 853.
[0140] In S39, the API unit 71 transmits the "reservation established" notification received from the reservation arbitration unit 851 to application B, which is the application that has made the "API usage reservation" request.
[0141] Next, a case where a reservation for use by application A has a higher priority than a reservation for use by application B will be described.
[0142] The processes of S30 to S35 are the same as those explained above, so the explanation will be omitted and only the processes from S35 onwards will be explained.
[0143] When the reservation arbitration unit 851 receives an "answer" to the "inquiry" from the status prediction unit 852, it determines in S40 whether the reservation can be made. The determination of whether the reservation can be made is based on the prediction result indicated in the "answer," the start and end conditions indicated in the "API-use reservation" request, and the required resources acquired in S32. In this case, it is determined that the reservation cannot be made under the conditions indicated in the "API-use reservation" request from app B, and the reservation arbitration unit 851 sends a "reservation not successful" notification or a "reservation change proposal" notification to the API unit 71 in S41. A "reservation change proposal" notification is sent when the reservation can be made by changing the reservation details, and a "reservation not successful" notification is sent when the reservation cannot be made even if the reservation details are changed.
[0144] In S42, the API unit 71 transmits the "reservation not established" notice or the "reservation change proposal" notice received from the reservation arbitration unit 851 to application B, which is the application that has made the "API use reservation" request.
[0145] Next, a case where a reservation for use by application A has a lower priority than a reservation for use by application B will be described.
[0146] The processes of S30 to S35 are the same as those explained above, so the explanation will be omitted and only the processes from S35 onwards will be explained.
[0147] When the reservation arbitration unit 851 receives an "answer" to the "inquiry" from the state prediction unit 852, it determines whether the reservation can be made in S50. The determination of whether the reservation can be made is based on the prediction result indicated in the "answer," the start and end conditions indicated in the "API-use reservation" request, and the required resources acquired in S32. In this case, it is determined that the reservation can be made under the conditions indicated in the "API-use reservation" request from app B. Then, in S51, the reservation arbitration unit 851 sends a "reservation successful" notification to app B to the API unit 71, and in S52, sends a "reservation cancellation" notification to app A to the API unit 71. If the reservation can be made by app A if the conditions are changed, the "reservation cancellation" notification includes a "reservation change proposal" notification indicating the changes. Note that instead of sending the "reservation change proposal" notification, information regarding the changes indicated in the "reservation change proposal" notification may be added to the "reservation cancellation" notification.
[0148] In S53, the reservation arbitration unit 851 deletes the reservation information of the application A from the information storage unit 853, and stores the reservation information of the application B in the information storage unit 853.
[0149] In S54, the API unit 71 transmits the "reservation established" notification received from the reservation arbitration unit 851 to application B, which is the application that has sent the "API use reservation" request. In addition, in S55, the API unit 71 transmits a "reservation cancellation" notification and a "reservation change proposal" notification to application A, which is the competing application.
[0150] [5. Correspondence of Terms] In this embodiment, the reservation arbitration unit 851 that executes the processes of S120 to S140 corresponds to the information generation unit of this disclosure, the confirmation API 73 corresponds to the information provision unit of this disclosure, and the center 35 corresponds to the external device of this disclosure. In this embodiment, the reservation arbitration unit 851 that executes the process of S160 corresponds to the required amount acquisition unit, the reservation arbitration unit 851 that executes the processes of S170 to S260 corresponds to the reservation feasibility determination unit, and the reservation arbitration unit 851 that executes the processes of S220 and S250 corresponds to the change proposal unit.
[0151] 6. Effects According to the embodiment described above in detail, the following effects are achieved.
[0152] (1) The vehicle control system 1 includes a confirmation API 73 that each of the applications 61 to 64 belonging to the service providing unit 6 uses to confirm the time periods during which a specified API can be used. Therefore, each of the applications 61 to 64 can select a time period that does not conflict with other applications and execute control using the desired API. In other words, in a use case in which multiple applications 61 to 64 (i.e., multiple systems inside and outside the vehicle) each access resources at their own discretion, conflicts in access requests can be prevented. Furthermore, resource shortages due to conflicts in access requests can be prevented.
[0153] (2) The "resource prediction response" notification returned in response to a "resource confirmation" request using the confirmation API 73 indicates the probabilistic prediction results of the usage status of each resource. Therefore, the application can flexibly determine the timing of API execution according to the notified prediction results.
[0154] (3) The vehicle control system 1 includes a reservation API 74 that each of the applications 61 to 64 in the service providing unit 6 uses to reserve resources required to execute a specified API. Therefore, even if there are multiple applications that operate independently of each other, each application can execute processing as scheduled because it is guaranteed that it has the resources for the reserved time slot.
[0155] (4) The reservation details established by the reservation API 74 are reflected when predicting the resource usage status, thereby improving the accuracy of predicting the resource usage status.
[0156] (5) When processing an "API usage reservation" request, if there are conflicting usage reservations and executing both of them would result in a resource shortage, the system accepts the high-priority request and makes a reservation change proposal for the low-priority request. The reservation change proposal includes changes to the usage time slot and resource restrictions. Therefore, not only can high-priority requests be reliably executed, but the execution schedule of low-priority requests can also be easily and quickly changed in accordance with the reservation change proposal.
[0157] 7. Other Embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modifications.
[0158] (a) In the above embodiment, the vehicle service unit 7 converts the first command into the second command. However, the state management unit 8 may convert the first command into the second command.
[0159] (b) In the above embodiment, the reasons for incompatibility are exemplified as "format incompatibility," "authority incompatibility," "equipment incompatibility," and "scene incompatibility," but may also include, for example, "priority incompatibility," "communication timeout," etc. If the reason for incompatibility is "priority incompatibility," the suggestion information may indicate a priority level that is determined to be compatible.
[0160] (c) In the above embodiment, the reference information to be added to the "resource prediction answer" notification is generated each time a "resource confirmation" request is received. For example, in the above embodiment, the reference information may be prepared in advance by periodically generating the reference information, and the prepared reference information may be added to the "resource prediction answer" notification.
[0161] (d) In the above embodiment, each of the applications 61 to 64 is configured to acquire the reference information via the confirmation API 73, but the reference information may be provided by storing the reference information in a shared memory accessible from each of the applications 61 to 64. Furthermore, instead of using the confirmation API 73 belonging to the API unit 71, the reference information may be provided using an API provided by the applications 61 to 64.
[0162] (e) In the above embodiment, the first ECU 10, the second ECU 15, and the center 35 each include a service providing unit 6, the first ECU 10 includes a vehicle service unit 7, the first ECU 10 and the third to fifth ECUs 20 to 30 each include a status management unit 8, and the fifth to thirteenth ECUs 30 to 48 each include an equipment management unit 9. The number of ECUs belonging to the ECU group 100 and the allocation of the functions of the service providing unit 6, the vehicle service unit 7, the status management unit 8, and the equipment management unit 9 to each ECU are not limited to those exemplified in the embodiment, and may be arbitrarily determined.
[0163] (f) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.
[0164] (g) In addition to the vehicle control device described above, the present disclosure can also be realized in various forms, such as a program for causing a computer to function as a vehicle control device, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a vehicle control method.
[0165] [8. Technical Ideas Disclosed in the Present Specification] [Item 1] A vehicle control device mounted on a vehicle, comprising: an equipment management unit (9) configured to execute control over vehicle equipment that is equipment of the vehicle and manage the status of the vehicle equipment; an API unit (71) having function APIs (72) that are interfaces provided for each of the functions in order to receive requests from application software and realize functions that utilize the vehicle equipment managed by the equipment management unit; a state prediction unit (852) configured to predict the status of resources of the vehicle within a specified time range; an information generation unit (851: S120 to S140) configured to generate, for each of the function APIs, reference information including a time period during which the function API can be used, based on a prediction result by the state prediction unit; and an information provision unit (73) configured to provide the reference information generated by the information generation unit for the function API specified in a request from the application software.
[0166] [Item 2] The vehicle control device according to item 1, wherein the resources to be predicted by the state prediction unit include at least one of a power supply state of the vehicle, a usage rate of a CPU that executes processing related to the function API, a remaining capacity of a battery mounted on the vehicle, availability of the vehicle equipment to be controlled, and availability of communication with an external device provided outside the vehicle.
[0167] [Item 3] The vehicle control device according to item 1 or 2, wherein the reference information is expressed as a probability that availability of the function API changes over time.
[0168] [Item 4] A vehicle control device according to any one of items 1 to 3, wherein the API unit further comprises a reservation API (74) that accepts a reservation for use of the function API, wherein the usage reservation includes identification information that identifies a reservation target API, which is the function API that is the target of the reservation, and usage information that indicates usage conditions for the reservation target API, and further comprises: a required amount acquisition unit (851: S160) configured to acquire a required amount of the resources required to execute the usage reservation based on the identification information; and a reservation feasibility determination unit (851: S170 to S260) configured to determine whether the usage reservation can be executed under the usage conditions indicated in the usage information, in accordance with a prediction result by the state prediction unit and a result acquired by the required amount acquisition unit, and to notify a source of the request for the usage reservation of the determination result.
[0169] Vehicle control device.
[0170] [Item 5] The vehicle control device according to Item 4, wherein the usage conditions include at least one of a specification of a usage time period during which the reservation target API is used and a specification of an upper limit time required for processing using the reservation target API.
[0171] [Item 6] A vehicle control device according to item 4 or 5, wherein the usage reservation includes information indicating a priority of the reservation, and the reservation feasibility determination unit is configured to, when a low-priority competing reservation exists and the accepted reservation can be executed by canceling the low-priority competing reservation, cancel the low-priority competing reservation and determine that the accepted reservation can be executed, the accepted reservation is the usage reservation accepted by the reservation API, and the low-priority competing reservation is an already-confirmed usage reservation that uses the same resources as the accepted reservation and has a lower priority than the accepted reservation.
[0172] [Item 7] The vehicle control device according to any one of items 4 to 6, wherein the state prediction unit is configured to reflect, in the prediction result, a result of acquisition by the required amount acquisition unit for the utilization reservation for which the reservation has been established.
[0173] [Item 8] The vehicle control device according to any one of items 4 to 7, further comprising: a change proposal unit (851: S220, S250) configured to notify a source of a request for the use reservation of a reservation change proposal indicating the executable use conditions when the use reservation determined by the reservation feasibility determination unit to be unexecutable can be executed by changing the use conditions.
[0174] [Item 9] The vehicle control device according to any one of items 1 to 8, wherein the information providing unit is configured to provide the reference information to the application software via a confirmation API provided in the API unit.
Claims
1. A vehicle control device mounted on a vehicle, comprising: an equipment management unit (9) configured to execute control over vehicle equipment that is equipment of the vehicle and manage a state of the vehicle equipment; an API unit (71) having function APIs (72) that are interfaces provided for each of the functions in order to receive a request from application software and realize a function using the vehicle equipment managed by the equipment management unit; a state prediction unit (852) configured to predict a state of resources possessed by the vehicle within a specified time range; an information generation unit (851: S120 to S140) configured to generate, from a prediction result by the state prediction unit, reference information including a time period during which the function API can be used for each of the function APIs; and an information provision unit (73) configured to provide the reference information generated by the information generation unit for the function API specified by a request from the application software.
2. A vehicle control device as described in claim 1, wherein the resources to be predicted by the state prediction unit include at least one of the power supply state of the vehicle, the usage rate of the CPU executing the processing related to the function API, the remaining capacity of the battery installed in the vehicle, the availability of the vehicle equipment to be controlled, and the availability of communication with an external device installed outside the vehicle.
3. A vehicle control device according to claim 1, wherein the reference information is expressed as a probability that the availability of the function API changes over time.
4. A vehicle control device according to claim 1, wherein the API unit further comprises a reservation API (74) that accepts a reservation for use of the function API, the usage reservation includes identification information that identifies a reservation target API that is the function API to be reserved, and usage information indicating usage conditions of the reservation target API, and further comprises a required amount acquisition unit (851: S160) configured to acquire a required amount of the resources required for executing the usage reservation based on the identification information, and a reservation feasibility determination unit (851: S170 to S260) configured to determine whether the usage reservation can be executed under the usage conditions indicated in the usage information in accordance with the prediction result by the state prediction unit and the acquisition result by the required amount acquisition unit, and to notify a source of the request for the usage reservation of the determination result. A vehicle control device.
5. A vehicle control device as described in claim 4, wherein the usage conditions include at least one of a specification of a usage time period during which the reservation target API is used, and a specification of an upper limit time required for processing using the reservation target API.
6. A vehicle control device as described in claim 4, wherein the usage reservation includes information indicating the priority of the reservation, and the reservation feasibility determination unit is configured to cancel a low priority competing reservation and determine that the accepted reservation can be executed when a low priority competing reservation exists and the accepted reservation can be executed by canceling the low priority competing reservation, the accepted reservation is the usage reservation accepted by the reservation API, and the low priority competing reservation is an already-confirmed usage reservation that uses the same resources as the accepted reservation and has a lower priority than the accepted reservation.
7. A vehicle control device as described in claim 4, wherein the state prediction unit is configured to reflect the result of acquisition by the required amount acquisition unit in the prediction result for the utilization reservation for which the reservation has been established.
8. A vehicle control device as described in claim 4, further comprising a change proposal unit (851: S220, S250) configured to notify a requester of the usage reservation of a reservation change proposal indicating the executable usage conditions when the usage reservation determined to be unexecutable by the reservation feasibility determination unit can be executed by changing the usage conditions.
9. A vehicle control device according to claim 1, wherein the information providing unit is configured to provide the reference information to the application software via a confirmation API provided in the API unit.
10. A vehicle control method executed by a computer mounted on a vehicle, wherein an equipment management unit provided in the computer executes control over vehicle equipment, which is equipment possessed by the vehicle, and manages the status of the vehicle equipment; an API unit provided in the computer accepts requests from application software and provides function APIs, which are interfaces provided for each of the functions, in order to realize functions utilizing the vehicle equipment managed by the equipment management unit; a status prediction unit provided in the computer predicts the status of resources possessed by the vehicle within a specified time range; an information generation unit provided in the computer generates reference information for each of the function APIs, including a time period during which the function API can be used, from the prediction result by the status prediction unit; and an information provision unit provided in the computer provides the reference information generated by the information generation unit for the function API specified in the request from the application software.
Citation Information
Patent Citations
Method and system for interaction between vehicle operator and multiple applications
JP2007511414A
Vehicle control device, vehicle control program, and vehicle control system
WO2022260010A1
