In-vehicle device, center device, vehicle control program, and vehicle control method

By designing a vehicle-mounted device and central device with request acceptance, storage, cancellation and deletion functions in the vehicle mediation system, the problem of inappropriate execution and user dissonance caused by the vehicle mediation system when processing a large number of requests is solved, and more efficient and user-friendly vehicle control is achieved.

CN119895389APending Publication Date: 2025-04-25DENSO CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202380064984.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-09-13
Filing Date
2023-09-06
Publication Date
2025-04-25

AI Technical Summary

Technical Problem

When the vehicle mediation system processes a large number of requests from outside the vehicle devices, it may lead to communication delays and additional requests to be processed, which in turn causes the execution of the request to be unsuitable for the current situation of the vehicle, bringing a sense of incongruity to the user.

Method used

A vehicle-mounted device and a central device are designed, which have components for request acceptance, storage, cancellation and deletion. By receiving the action request and canceling conditions, it is determined whether to cancel the action request stored in the queue, and delete the request if necessary, avoiding the execution of unwanted action requests.

Benefits of technology

It effectively avoids the execution of unnecessary action requests in the action request waiting state, reduces the sense of inconsistency in the user experience, and improves the adaptability of vehicle control.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119895389A_ABST
    Figure CN119895389A_ABST
Patent Text Reader

Abstract

An in-vehicle device (10, 20) according to one aspect of the present disclosure is mounted on a vehicle, and is provided with a request reception unit (71), a request storage unit (72), a storage request cancellation determination unit (74), and a storage request deletion unit (181). The storage request cancel determination unit determines whether or not to cancel the operation request stored in the first queue on the basis of the first cancel condition received by the request reception unit and a second cancel condition relating to the method of use of the vehicle. When it is determined that the operation request is cancelled, the storage request deletion unit deletes the operation request from the first queue.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present international application claims the priority based on Japanese Patent Application No. 2022-145318 filed with the Japan Patent Office on September 13, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to vehicle control. Background Art

[0004] The vehicle mediation system described in Patent Document 1 below performs mediation of allocation to the execution units of the plurality of requests and mediation in each execution unit in order to realize a plurality of requests from a plurality of application execution units.

[0005] Patent document 1: Japanese Patent Application Publication No. 2020-64489.

[0006] If the vehicle mediation system only responds to requests from the on-board device, there will be less duplication of requests and multiple requests can be mediated immediately. However, in the future, it is expected that the vehicle mediation system will not only accept requests from the on-board device, but also accept a large number of requests from off-board devices such as centers that utilize APIs. It can be considered that if the requests become large, the communication delay will increase and it will be necessary to store pending requests. However, as a result of detailed research by the inventors, the following problem was discovered: Since the condition of the vehicle changes at any time, when the pending state of the request ends, the execution of the request may not be suitable for the condition of the vehicle. Furthermore, as a result of detailed research by the inventors, the following problem was discovered: unnecessary requests may be executed, causing a sense of disharmony to the user. Summary of the invention

[0007] One aspect of the present disclosure provides a technology capable of realizing vehicle control without causing a user to feel uncomfortable.

[0008] An in-vehicle device according to one aspect of the present disclosure is mounted on a vehicle and comprises a request accepting unit, a request storage unit, a storage request cancellation determination unit, and a storage request deletion unit. The request accepting unit is configured to receive an action request of the vehicle and a first cancellation condition from an application execution unit, wherein the application execution unit is configured to execute application software, the action request of the vehicle is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request. The request storage unit is configured to store the action request received by the request accepting unit in a first queue. The storage request cancellation determination unit is configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request accepting unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle. The storage request deletion unit is configured to delete the action request from the first queue when the storage request cancellation determination unit determines that the action request is to be canceled.

[0009] The vehicle-mounted device of one aspect of the present disclosure receives an action request and a first cancellation condition from an application execution unit. Moreover, when the waiting state of the action request ends, the vehicle-mounted device determines whether to cancel the action request stored in the first queue based on the first cancellation received from the application execution unit and the second cancellation condition related to the method of using the vehicle. The action request determined to be canceled is deleted from the first queue. Therefore, it is possible to avoid executing unnecessary action requests in the waiting state of the action request. Furthermore, it is possible to achieve vehicle control that does not cause a sense of discomfort to the user.

[0010] A center device according to another aspect of the present disclosure is configured to wirelessly communicate with a vehicle, and is provided with a request accepting unit, a request storage unit, a storage request cancellation determination unit, and a storage request deletion unit. The request accepting unit is configured to receive an action request and a first cancellation condition of the vehicle from an application execution unit, wherein the application execution unit is configured to execute application software, the action request of the vehicle is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request. The request storage unit is configured to store the action request received by the request accepting unit in a first queue. The storage request cancellation determination unit is configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request accepting unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle. The storage request deletion unit is configured to delete the action request from the first queue when the storage request cancellation determination unit determines that the action request is to be canceled.

[0011] A center device according to another aspect of the present disclosure achieves the same effects as the above-mentioned vehicle-mounted device.

[0012] A vehicle control program according to another aspect of the present disclosure causes a processing device to perform the following processing: receiving a vehicle action request and a first cancellation condition from an application execution unit, wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; storing the received action request in a queue; determining whether to cancel the action request stored in the queue based on the first cancellation condition and the second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and deleting the action request from the queue if it is determined that the action request is canceled.

[0013] By executing the vehicle control program of the other aspect mentioned above through the above-mentioned processing device, the same effect as the above-mentioned vehicle-mounted device is achieved.

[0014] Another aspect of the present disclosure is a vehicle control method executed by a processing device. The vehicle control method comprises: receiving a vehicle action request and a first cancellation condition from an application execution unit, wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; storing the received action request in a queue; determining whether to cancel the action request stored in the queue based on the first cancellation condition and a second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and deleting the action request from the queue if it is determined that the action request is canceled.

[0015] By executing the vehicle control method of the other aspect mentioned above through the above-mentioned processing device, the same effect as the above-mentioned vehicle-mounted device is achieved.

[0016] A vehicle control program according to another aspect of the present disclosure causes a central device configured to wirelessly communicate with a vehicle to perform the following processing: receiving a vehicle action request and a first cancellation condition from an application execution unit, wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; storing the received action request in a queue; determining whether to cancel the action request stored in the queue based on the first cancellation condition and a second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and deleting the action request from the queue if it is determined that the action request is canceled.

[0017] By executing the vehicle control program of the above-mentioned further aspect through the above-mentioned central device, the same effect as the above-mentioned vehicle-mounted device is achieved.

[0018] Another aspect of the present disclosure is a vehicle control method executed by a central device configured to wirelessly communicate with a vehicle. The vehicle control method comprises: receiving a vehicle action request and a first cancellation condition from an application execution unit, wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; storing the received action request in a queue; determining whether to cancel the action request stored in the queue based on the first cancellation condition and a second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and deleting the action request from the queue if it is determined that the action request is canceled.

[0019] By executing the vehicle control method of the above-mentioned further aspect through the above-mentioned central device, the same effect as that of the above-mentioned vehicle-mounted device is achieved.

[0020] A vehicle control system according to another aspect of the present disclosure includes: a first vehicle-mounted device and a second vehicle-mounted device mounted on the vehicle, and a central device configured to wirelessly communicate with the first vehicle-mounted device. The central device includes a first request accepting unit, a first request storage unit, a first storage request canceling unit, and a first storage request deleting unit. The first request accepting unit is configured to receive an action request of the vehicle and a first cancellation condition from a first application execution unit, wherein the first application execution unit is configured to execute a first application software, the action request of the vehicle corresponds to the execution of the first application software, and the first cancellation condition is a condition for canceling the action request. The first request storage unit is configured to store the action request received by the first request accepting unit in a first queue. The first request canceling unit is configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the first request accepting unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle. The first storage request deleting unit is configured to delete the action request from the first queue when the first storage request cancellation determining unit determines that the action request is to be canceled.

[0021] The first vehicle-mounted device includes a second request accepting unit, a second request storage unit, a second storage request cancellation determination unit, and a second storage request deleting unit. The second request accepting unit is configured to receive an action request and a first cancellation condition that are determined not to be canceled by the first storage request cancellation determination unit. The second request storage unit is configured to store the action request received by the second request accepting unit in a second queue. The second storage request cancellation determination unit is configured to determine whether to cancel the action request stored in the second queue based on the first cancellation condition received by the second request accepting unit and a pre-set second cancellation condition. The second storage request deleting unit is configured to delete the action request from the second queue when the second storage request cancellation determination unit determines that the action request is to be canceled.

[0022] The second vehicle-mounted device includes a request mediation unit, a cancellation determination unit, and a request to be mediated deletion unit. The request mediation unit is configured to receive an action request determined by the second storage request cancellation determination unit as not to be cancelled and store it in a third queue, and mediate between the action request and competing requests stored in the third queue. The cancellation determination unit is configured to determine whether to cancel the action request based on a first cancellation condition and a second cancellation condition. The request to be mediated deletion unit is configured to delete the action request from the third queue when the request to be mediated cancellation determination unit determines that the action request is to be cancelled.

[0023] According to the above vehicle control system, even when the waiting time for the action request in the center device is prolonged, it is possible to avoid unnecessary action requests being executed in the waiting state, thereby achieving vehicle control that does not give the user a sense of discomfort.

[0024] Another vehicle control method disclosed herein is executed by a system including a first vehicle-mounted device and a second vehicle-mounted device mounted on a vehicle, and a central device configured to wirelessly communicate with the first vehicle-mounted device. The central device receives a vehicle action request and a first cancellation condition from a first application execution unit, wherein the first application execution unit is configured to execute a first application software, the vehicle action request is in response to the execution of the first application software, the first cancellation condition is a condition for canceling the action request, the received action request is stored in a first queue, and it is determined whether to cancel the action request stored in the first queue based on the received first cancellation condition and the second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle, and when it is determined that the action request is canceled, the action request is deleted from the above-mentioned first queue.

[0025] The first vehicle-mounted device receives an action request and a first cancellation condition determined by the central device to be not cancelable, stores the received action request in a second queue, determines whether to cancel the action request stored in the second queue based on the received first cancellation condition and a pre-set second cancellation condition, and deletes the action request from the above-mentioned second queue if it is determined that the action request is to be canceled.

[0026] The second vehicle-mounted device receives the action request determined by the first vehicle-mounted device to be not cancelable and stores it in the third queue, and performs mediation between the action request and competing requests stored in the third queue, and determines whether to cancel the action request based on the first cancellation condition and the second cancellation condition. If it is determined that the action request is to be canceled, the action request is deleted from the third queue.

[0027] By executing the vehicle control method of the above-mentioned further aspect through the above-mentioned system, the same effect as the above-mentioned vehicle control system is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 This is a block diagram showing a schematic configuration of a vehicle control system according to an embodiment.

[0029] Figure 2 This is a block diagram showing the structure of the ECU according to the embodiment.

[0030] Figure 3 It is a block diagram showing the core structure of the embodiment.

[0031] Figure 4 It is a block diagram showing some functions of a vehicle control system according to an embodiment.

[0032] Figure 5 It is a sequence diagram showing the flow of control processing executed in the vehicle control system according to the embodiment.

[0033] Figure 6 This is a diagram showing cancellation conditions set by an application execution unit and a vehicle API according to an embodiment.

[0034] Figure 7 This is a block diagram showing another example of the schematic configuration of the vehicle control system according to the embodiment.

[0035] Figure 8 This is a block diagram showing another example of a part of the functions of the vehicle control system according to the embodiment.

[0036] Fig. 9A This is a sequence diagram showing a part of another example of the flow of the control process executed in the vehicle control system according to the embodiment.

[0037] Fig. 9BIt is a sequence diagram showing the remaining part of another example of the flow of the control process executed in the vehicle control system of the embodiment. DETAILED DESCRIPTION

[0038] <1. Structure>

[0039] <1-1. System structure>

[0040] Reference Figure 1 The vehicle control system 1 of the present embodiment is described. The vehicle control system 1 includes an electronic control unit (hereinafter, ECU) group 100 and a center 35 mounted on a vehicle such as an automobile. The ECU group 100 includes a plurality of ECUs. In the present 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 a sixth ECU 41 to a thirteenth ECU 48. Each ECU in the ECU group 100 is connected to each other through in-vehicle communication (i.e., wired communication or wireless communication). The center 35 is arranged outside the vehicle and is connected to the ECU group 100 through out-vehicle communication (i.e., wireless communication).

[0041] Each ECU in the ECU group 100 and the center 35 controls a target device, which is a target of an operation request among devices mounted on the vehicle. Here, the so-called device includes not only hardware such as sensors and actuators, but also software that realizes a certain function.

[0042] In other embodiments, the vehicle control system 1 may include the ECU group 100 instead of the center 35. In other embodiments, the ECU group 100 may include fourteen or more ECUs, or may include only thirteen or less ECUs.

[0043] <1-2. Hardware structure>

[0044] Next, refer to Figure 2 and Figure 3 The hardware configuration of the ECU group 100 and the center 35 will be described.

[0045] Each ECU in the ECU group 100 has the same hardware structure as each other. Therefore, here, the structure of the first ECU 10 is described by taking the first ECU 10 as a representative. 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-transitional physical recording medium. In the present embodiment, ROM 11b is equivalent to a non-transitional physical recording medium storing a program. In addition, by executing the program, a method corresponding to the program is executed.

[0046] The vehicle I / F 12 is connected to other ECUs and vehicle-mounted devices via an in-vehicle network, etc., and obtains various information from other ECUs and vehicle-mounted devices. The in-vehicle network may include a Controller Area Network (hereinafter referred to as CAN) and Ethernet. CAN is a registered trademark. Ethernet is a registered trademark.

[0047] The communication unit 13 performs data communication with the center 35 and the like via the wide area communication network by wireless communication. In other embodiments, only the first ECU 10 in the ECU group 100 has the communication unit 13. In addition, the method of realizing the various functions of the first ECU 10 is not limited to software, and one or more hardware may be used to realize a part or all of its elements. For example, when the above functions are realized by an electronic circuit as hardware, the electronic circuit may be realized by a digital circuit or an analog circuit including a plurality of logic circuits, or a combination thereof.

[0048] 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-transitional physical recording medium. In the present embodiment, the ROM 36b is equivalent to a non-transitional physical recording medium storing a program. In addition, by executing the program, a method corresponding to the program is executed.

[0049] The communication unit 37 performs data communication with the ECU group 100 via the 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. In addition, the method for realizing the various functions of the center 35 is not limited to software, and one or more hardware may be used to realize a part or all of its elements. For example, when the above functions are realized by an electronic circuit as hardware, the electronic circuit may also be realized by a digital circuit or an analog circuit including a plurality of logic circuits, or a combination thereof.

[0050] <1-3. Overall system functional structure>

[0051] Return to Figure 1 , various functions of the vehicle control system 1 are described. The vehicle control system 1 has the functions of the equipment management unit 9 of the first layer, the state management unit 8 of the second layer, the vehicle service unit 7 of the third layer, and the service provider 6 of the fourth layer. The software architecture of the vehicle control system 1 is hierarchical into these four layers. These functions of the vehicle control system 1 are shared by each ECU in the ECU group 100 and the center 35.

[0052] The equipment management unit 9 includes a plurality of control units according to various vehicle equipment, such as vehicle-mounted cameras, vehicle-mounted millimeter-wave radars, brakes, steering gears, displays, speakers, various lights, vehicle-mounted air conditioners, and electric power seats.

[0053] 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 equipment of the vehicle is independently controlled by the corresponding control units among the control units 91 to 99.

[0054] The camera control unit 91 controls the exposure of the vehicle-mounted camera, etc., and obtains the captured image of the vehicle-mounted camera. The millimeter wave control unit 92 controls the vehicle-mounted millimeter wave radar, and obtains the detection results detected by the millimeter wave radar. The brake control unit 93 controls the brake. The steering control unit 94 controls the steering gear. The display control unit 95 controls the display (for example, instruments, warning lights, etc.). The sound control unit 96 controls the speaker, and outputs warning sounds, voices, etc. from the speaker. The light control unit 97 controls various lights installed in the vehicle. The HAVC control unit 98 controls the vehicle air conditioner. The seat control unit 99 controls the electric power seat of the vehicle.

[0055] In the present embodiment, the sixth ECU 41 includes a camera control unit 91, the seventh ECU 42 includes a millimeter wave control unit 92, and the eighth ECU 43 includes a brake control unit 93. The ninth ECU 44 includes a steering control unit 94, the tenth ECU 45 includes a display control unit 95, and the eleventh ECU 46 includes a sound control unit 96. The fifth ECU 30 includes a light control unit 97, the twelfth ECU 47 includes a HAVC control unit 98, and the thirteenth ECU 48 includes a seat control unit 99.

[0056] The service provider 6 includes a first application execution unit 61, 63, 65 and a second application execution unit 62, 64, 66. The first application execution unit 61, 63, 65 and the second application execution unit 62, 64, 66 respectively execute different or the same application software (hereinafter, application) to provide services to users. In detail, the service provider 6 indirectly sends instructions to the equipment of the vehicle and provides services such as operating the equipment of the vehicle to the user. The instructions include commands such as action requests, instructions such as parameters, function calls, etc. In addition, the instructions may include priority information indicating which instruction should be processed first.

[0057] In addition, since the applications executed by the first application execution unit 61, 63, 65 and the second application execution unit 62, 64, 66 are general-purpose programs, they can be developed by a third party and widely disclosed. The user can install the application disclosed by the third party to any ECU in the ECU group 100 via a wide area communication network, etc. In other words, the user can add or change the application.

[0058] In the present embodiment, the first ECU 10, the second ECU 15, and the center 35 are provided with a service providing unit 6. The first ECU 10 is provided with a first application executing unit 61 and a second application executing unit 62. The second ECU 15 is provided with a first application executing unit 63 and a second application executing unit 64. The center 35 is provided with a first application executing unit 65 and a second application executing unit 66. In one embodiment, the first ECU 10 and the third ECU 20 are equivalent to the vehicle-mounted device of the present disclosure, the first ECU 10 is equivalent to the first device of the present disclosure, and the third ECU 20 is equivalent to the second device of the present disclosure. In other embodiments, the first ECU 10 is equivalent to the vehicle-mounted device of the present disclosure.

[0059] The vehicle service unit 7 includes a vehicle Application Programming Interface (hereinafter referred to as API) 85. The vehicle API 85 performs processing suitable for a specific vehicle model, a specific grade, etc. That is, the vehicle API 85 performs processing that absorbs differences in vehicle models, grades, etc., so that the service provider 6 does not need to be aware of the differences in vehicle models, grades, etc. The vehicle API 85 corresponds to an API that makes the instructions processed by the service provider 6 suitable for the instructions processed by the state management unit 8 and the equipment management unit 9 described later. In the present embodiment, the first ECU 10 is provided with the vehicle service unit 7.

[0060] The equipment management unit 9 controls the equipment of the vehicle. Specifically, the state management unit 8 receives a first instruction via the vehicle API 85, generates a second instruction that implements the first instruction, and sends the second instruction to the equipment management unit 9. For example, the state management unit 8 calculates the amount of movement of an actuator that is one of the equipment of the vehicle, and sends the second instruction including the amount of movement to the equipment management unit 9.

[0061] Specifically, the state management unit 8 selects the best control unit from the control units 91 to 99 provided in the equipment management unit 9 in order to implement the action request (i.e., the first instruction) from the service provider 6. Furthermore, the state management unit 8 converts the first instruction into a second instruction in a format suitable for the selected control unit, and distributes the second instruction to the selected control unit in consideration of the order of transmission.

[0062] For example, when the first instruction is "turn the vehicle left at R200 m and accelerate at 0.3 G", the state management unit 8 outputs (i) a second instruction requesting an output of 1000 Nm from the engine and (ii) a second instruction requesting an output of -0.1 rad from the steering.

[0063] In addition, when the first instruction is "move to parking state", the state management unit 8 outputs (i) a second instruction requesting to set the gear to P, (ii) a second instruction requesting to turn off the air conditioner, (iii) a second instruction requesting to completely close the windows, and (iv) a second instruction requesting to lock the doors and move to parking state when the requests (i) to (iii) are completed and there is no occupant.

[0064] The state management unit 8 corresponds to the type of vehicle action corresponding to the type of the first instruction, and includes a state recognition unit 81, a motion system equipment control unit 82, a Human Machine Interface (hereinafter, HMI) system state recognition unit 83, and a main system control unit 84. The state recognition unit 81 obtains information from the camera control unit 91 and the millimeter wave control unit 92, and converts the obtained information into information on the position of the vehicle and pedestrians, and outputs it to the vehicle API 85. The motion system equipment control unit 82 corresponds to the vehicle's actions of the driving system such as turning, driving, and stopping. The motion system equipment control unit 82 converts the vehicle's action request into the control amount of the brake control unit 93 and the steering control unit 94 and outputs it. The state management unit 8 is not classified by the implementation unit (for example, control units 91 to 99) that is easily dependent on the change of the vehicle, but is classified by the vehicle action that is easily requested by the service provider 6. For example, the state management unit 8 is set to correspond to each domain of the vehicle.

[0065] The HMI system state recognition unit 83 corresponds to the vehicle action associated with the information presentation to the user. The HMI system state recognition unit 83 receives an action request such as an alarm, determines whether to make a report using the display control unit 95 and the sound control unit 96, and outputs the control amount. The main body system control unit 84 receives a first instruction related to the vehicle environment, and determines which of the light control unit 97, the HVAC control unit 98, and the seat control unit 99 to operate. The main body system control unit 84 converts the first instruction into a second instruction suitable for the selected control unit and outputs it.

[0066] In the present embodiment, the third ECU 20 includes a state recognition unit 81 , and the first ECU 10 includes a motion system equipment control unit 82 . The fourth ECU 25 includes an HMI system state recognition unit 83 , and the fifth ECU 30 includes a main body system control unit 84 .

[0067] In addition, the state management unit 8 converts the sensor data obtained from the equipment management unit 9 into a format suitable for the vehicle service unit 7, and sends the converted data to the vehicle service unit 7. In detail, the state management unit 8 classifies each raw sensor data obtained from the vehicle sensor by the equipment management unit 9 into data distinguished by sensing object that can be easily used by the service provider 6. In addition, the state management unit 8 integrates the classified data, converts it into data with a higher degree of abstraction, and sends the converted data to the vehicle service unit 7.

[0068] For example, the state management unit 8 obtains various data such as the vehicle speed 0 km / h, the shift position P, and the driver is not in the vehicle from the equipment management unit 9, and generates data indicating that the vehicle is in a parked state based on the obtained data. The state management unit 8 sends the generated data to the service provider 6 via the vehicle service unit 7.

[0069] The functions of the vehicle control system 1 assigned to each ECU in the ECU group 100 and the center 35 may be changed appropriately. For example, the first ECU 10 may have the function of the state recognition unit 81 of the third ECU 20. That is, the first ECU 10 and the third ECU 20 may be constituted by one ECU.

[0070] <1-4. Functional structure of vehicle API and status recognition unit>

[0071] Next, refer to Figure 4 An example of detailed functions of the vehicle API 85 of the first ECU 10 and the state recognition unit 81 of the third ECU 20 will be described.

[0072] The vehicle API 85 has functions of a request accepting unit 71 , a request storing unit 72 , a vehicle state determining unit 73 , a storage request cancel determining unit 74 , a transmitting unit 75 , a storage request deleting unit 181 , and a first queue 88 .

[0073] The state recognition unit 81 has the functions of a receiving unit 76 , a request mediation unit 77 , a vehicle state determination unit 78 , a pending mediation request cancellation determination unit 79 , a pending mediation request deletion unit 182 , and a second queue 89 .

[0074] The request receiving unit 71 receives an action request and a first cancellation condition from the first application execution unit 63, 65 and the second application execution unit 64, 66. The action request includes identification information of the application execution unit of the request source. Whenever the request receiving unit 71 receives an action request, the request storage unit 72 stores the action request in the first queue 88. The action request stored in the first queue 88 becomes a pending state.

[0075] The first cancellation condition is a condition for canceling the action request, and is specified for each action request. The request storage unit 72 stores the first cancellation condition in correspondence with the action request. In addition, the request storage unit 72 stores the second cancellation condition in correspondence with the action request in advance. Therefore, the request storage unit 72 stores the first cancellation condition and the second cancellation condition in correspondence with the action request. The second cancellation condition is a condition pre-set by the vehicle API 85. The details of the second cancellation condition will be described later.

[0076] After the request storage unit 72 receives the action request, the state of the vehicle may change at any time. The state of the vehicle includes, for example, the power state, the battery state, the driving state, the driving setting, etc. The power state is whether the ignition is on or off. The battery state is whether there is a voltage drop. The driving state is any one of parked, driving, and parked. The driving setting is automatic driving or manual driving. Since the state of the vehicle may change at any time, there is a possibility that the state of the vehicle changes while the action request is in the pending state in the first queue 88, and the action request is not required or cannot be executed at the end of the pending state of the action request.

[0077] For example, in the case of a window opening and closing application that opens the window only when the ignition is on and closes the window when the ignition is off, there is a case where the action request of "open window" is stored in the first queue 88 and becomes a waiting state during the ignition is on. In such a case, if the ignition is off, the window opening and closing application issues an action request of "close window" in order to close the window. At this time, if the action request of "open window" issued previously remains in the first queue 88, the action request of "open window" is first accepted, and then the action request is overwritten by "close window". As a result, the window opens slightly and then closes. Therefore, the user feels inconsistent with the behavior of the window. Therefore, in such a case, it is desired that the action request of "open window" is canceled along with the disconnection of the ignition.

[0078] Therefore, a first cancellation condition is set so that the action request can be canceled when the action request is not necessary or cannot be performed. The first cancellation condition includes a condition related to the state of the vehicle. Specifically, when the state of the vehicle becomes such that the first cancellation condition is satisfied, the action request is canceled. The state of the vehicle for which the first cancellation condition is satisfied includes the state of the vehicle in which the method of use, action, or behavior of the application can be changed. That is, the state of the vehicle for which the first cancellation condition is satisfied includes the state of the vehicle in which the method of use or action of the equipment of the vehicle can be changed.

[0079] The first cancellation condition for the action request of "open the window" may also be, based on or instead of the above-mentioned disconnection of the ignition, that the speed is above 80 km / h and the wipers are turned on. When driving at a speed of above 80 km / h, in order to ensure safety, the first application execution unit 63, 65 and the second application execution unit 64, 66 set the cancellation of the action request of "open the window". When the wipers are turned on, the first application execution unit 63, 65 and the second application execution unit 64, 66 set the cancellation of the action request of "open the window" to prevent rain from entering the car. In addition, the first cancellation condition also includes conditions that are unrelated to the state of the vehicle. For example, the first cancellation condition may also be that 3 minutes have passed after the request storage unit 72 receives the action request.

[0080] Here, in the case where a third party creates an application, the third party specifies a first cancellation condition, and the first cancellation condition is set by the application execution unit that executes the application created by the third party. The third party may not be familiar with the vehicle. In this case, it is difficult for the third party to specify in detail the cancellation condition under the specified state of the vehicle. Therefore, the platform prompts multiple abstract vehicle states as options. The abstract vehicle state can be, for example: (i) ignition on / ignition off as a state after abstracting the power state, (ii) with / without battery voltage reduction as a state after abstracting the state of the battery voltage of the vehicle, (iii) automatic driving / manual driving as a state after abstracting the automation level, (iv) parked / driving / parked as a state after abstracting the drive state, (v) with / without a driver in the vehicle, etc. The third party selects the state of the vehicle from the multiple options prompted, and specifies the cancellation condition under the selected vehicle state as the first cancellation condition.

[0081] exist Figure 6 In the figure, conditions A to E are shown as examples of the first cancellation condition. Condition A is a cancellation condition based on the change in the power state (i.e., the change from ignition-on to ignition-off). Specifically, condition A is "when changing from ignition-on to ignition-off, cancel the action request to open the window, and pass the subsequent action request to close the window". The state of the vehicle for which condition A is satisfied is the ignition-off. Condition B is a cancellation condition based on the presence or absence of a battery voltage reduction. Specifically, condition B is "when multiple action requests are issued from itself, and information is obtained that the battery voltage of the vehicle has been reduced, cancel the pre-set low-priority action request among the multiple action requests". The state of the vehicle for which condition B is satisfied is that the battery voltage has been reduced. By canceling the low-priority action request based on condition B, the application execution unit can extend the high-priority action request among the multiple action requests.

[0082] Condition C is a cancellation condition based on the change of automation level. Specifically, condition C is "when changing from automatic driving to manual driving, cancel the action request for changing the seat position on standby in the first queue 88 or the second queue 89, by the action request to move the seat to the driving position". The state of the vehicle for which condition C is satisfied is the manual driving setting. Condition D is a cancellation condition based on the change of the driving state of the vehicle. Specifically, condition D is "when changing from parking to driving, cancel the action request for the entertainment application on standby in the first queue 88 or the second queue 89". The state of the vehicle for which condition D is satisfied is driving. Condition E is a cancellation condition based on the presence or absence of a driver. Specifically, condition E is "when changing from having a driver to having no driver, cancel the action request for the instrument display on standby in the first queue 88 or the second queue 89". The state of the vehicle for which condition E is satisfied is without a driver.

[0083] The vehicle state determination unit 73 determines the state of the vehicle.

[0084] The storage request cancellation determination unit 74 determines whether to cancel the action request based on the state of the vehicle determined by the vehicle state determination unit 73 and the first cancellation condition and the second cancellation condition corresponding to the action request stored in the first queue 88. The storage request cancellation determination unit 74 performs the cancellation determination at the moment when the pending state of the action request ends. Alternatively, the storage request cancellation determination unit 74 may also perform the cancellation determination in the pending state of the action request. When the cancellation determination is performed in the pending state of the action request, the storage request cancellation determination unit 74 may perform the cancellation determination only once or periodically.

[0085] The second cancellation condition includes a cancellation condition related to the state of the vehicle, and is set by the vehicle API 85. That is, the second cancellation condition sets the platform. The state of the vehicle for which the second cancellation condition is satisfied includes the state of the vehicle whose method of use of the vehicle can be changed. In detail, the state of the vehicle for which the second cancellation condition is satisfied includes the method of use of one or more of the vehicle's equipment, or the state of the vehicle whose action can be changed. The method of use of a vehicle's equipment, or the state of the vehicle whose action can be changed is the same as the state of the vehicle for which the first cancellation condition is satisfied. That is, the second cancellation condition includes the first cancellation condition, and includes the above-mentioned conditions A to E.

[0086] In addition, the above-mentioned multiple vehicle equipments are equivalent to a group of vehicle equipments that share the same vehicle resources. The vehicle resources are the vehicle power supply (i.e., battery power), the vehicle control amount, processing load, communication volume, etc. The vehicle state that can be changed by the usage method or action of the multiple vehicle equipments is a state in which the resource allocation to at least one of the multiple vehicle equipments is reduced in order to avoid the usage of the vehicle resources exceeding a threshold.

[0087] For example, the second cancellation condition is to cancel both operation requests when receiving an operation request to turn on a first device and an operation request to turn on a second device in a vehicle state where the battery voltage is reduced. The first device is, for example, an air conditioner using battery power, and the second device is, for example, a headlight using battery power.

[0088] In addition, the second cancellation condition is that when an action request to increase the accelerator opening and an action request to increase the steering angle are received while the vehicle is traveling on the road, and the drive control amount that satisfies the two action requests has the possibility of deviating from the road, the two action requests are canceled.

[0089] Furthermore, the second cancellation condition includes a cancellation condition in a situation where the application execution unit cannot set the cancellation condition. The situation where the application execution unit cannot set the cancellation condition is, for example, after the execution of the application is terminated.

[0090] exist Figure 6 Conditions F to H are shown as examples of the second cancellation condition. Condition F is a cancellation condition based on the reduction of the battery voltage of the vehicle. Specifically, condition F is "when the battery voltage is reduced, the action request that consumes more than the specified value among the action requests waiting in the first queue 88 or the second queue 89 is cancelled, and the action request that consumes less than the specified value is replaced". Condition F is a condition related to the state of the vehicle that can be changed by the use method or action of the equipment of multiple vehicles. The state of the vehicle for which condition F is satisfied is the state of reduced battery voltage.

[0091] Condition G is a cancellation condition from the perspective of the control occupied by a specific application. Specifically, condition G is "when remote automatic driving starts the control of the vehicle, end the action request of the related application waiting in the first queue 88 or the second queue 89". Condition G is a condition related to the state of the vehicle that can be changed by the use method or action of multiple vehicle equipment. The state of the vehicle when condition G is met is the state in which remote automatic driving occupies the control of the vehicle. In addition, another example of condition G is "while giving top priority to plug-in charging, cancel all action requests from the outside waiting in the first queue 88 or the second queue 89". Another example of condition G is a condition related to the state of the vehicle that can be changed by the use method or action of multiple vehicle equipment. The state of the vehicle when condition G is met is the state in which plug-in charging is given top priority.

[0092] Condition H is a cancellation condition based on the end of the application. Specifically, condition F is "even though the application has ended, if there is an action request waiting in the first queue 88 or the second queue 89, cancel the action request." In addition, conditions F, G, and H are used in the cancellation determination of the action request by the vehicle API 85 of the first ECU 10, and are also used in the cancellation determination of the action request by the state recognition unit 81 of the third ECU 20.

[0093] The storage request deleting unit 181 deletes the operation request determined to be cancelled by the storage request cancellation determining unit 74 from the first queue 88. Furthermore, the storage request deleting unit 181 notifies the application execution unit that requested the operation request that the operation request was cancelled based on the identification information included in the cancelled operation request.

[0094] The transmission unit 75 transmits the operation request determined not to be canceled by the storage request cancellation determination unit 74 to the third ECU 20 .

[0095] The receiving unit 76 receives an action request and a corresponding first cancellation condition from the sending unit 75. Whenever the receiving unit 76 receives an action request, the request mediation unit 77 stores the action request in the second queue 89. The action request stored in the second queue 89 becomes a pending mediation state (i.e., a pending execution state). Furthermore, when there are a plurality of competing action requests in the second queue 89, the request mediation unit 77 mediates the competing action requests. The competing action requests are action requests related to the same object equipment. The request mediation unit 77 stores the plurality of action requests in the second queue 89 according to the priority order set according to the mediation rule.

[0096] For example, one example of competing multiple action requests is multiple action requests related to a camera. The multiple action requests related to a camera include turning on high-resolution shooting, turning on low-resolution shooting, and turning off shooting. In addition, another example of competing multiple action requests is multiple action requests related to headlights. The multiple action requests related to headlights include turning on low beam, turning on high beam, flashing for 10 seconds, turning off, and the like.

[0097] The request mediation unit 77 stores the first cancellation condition in correspondence with the action request. The request mediation unit 77 acquires and stores the second cancellation condition in correspondence with the action request from the vehicle API 85 in advance. Therefore, the request mediation unit 77 stores the first cancellation condition and the second cancellation condition in correspondence with the action request.

[0098] The vehicle state determination unit 78 determines the state of the vehicle.

[0099] The request-to-be-adjusted cancellation determination unit 79 determines whether to cancel the action request based on the state of the vehicle determined by the vehicle state determination unit 78 and the first cancellation condition and the second cancellation condition corresponding to the action request stored in the second queue 89. The request-to-be-adjusted cancellation determination unit 79 performs the cancellation determination at the moment when the state of the request-to-be-adjusted ends. Alternatively, the request-to-be-adjusted cancellation determination unit 79 may perform the cancellation determination in the state of the action request of the ...

[0100] The arbitration pending request deleting unit 182 deletes the operation request determined to be cancelled by the arbitration pending request cancellation determining unit 79 from the second queue 89 .

[0101] Then, the mediation request cancellation determination unit 79 sends the operation request determined not to be cancelled to the operation control unit 80. In this embodiment, the camera control unit 91 of the sixth ECU 41 or the millimeter wave control unit 92 of the seventh ECU 42 includes the operation control unit 80. The operation control unit 80 receives the operation request and operates the target equipment.

[0102] As described above, in the vehicle control system 1 of an example of the present embodiment, the first ECU 10 determines whether to cancel the action request based on the first cancellation condition and the second cancellation condition. Furthermore, the third ECU 20 determines whether to cancel the action request determined by the first ECU 10 as not to be canceled based on the first cancellation condition and the second cancellation condition. The vehicle control system 1 of an example of the present embodiment described above performs the cancellation determination of the action request twice, but the number of cancellation determinations is not limited to two times.

[0103] Figure 7 The schematic structure of the vehicle control system 1 according to another example of the present embodiment is shown in FIG. Figure 7 In the vehicle control system 1 shown in FIG. 1 , the fourth ECU 25, the fifth ECU 30, and the sixth to thirteenth ECUs 41 to 48 are omitted from illustration. Figure 7 As shown, the vehicle control system 1 of another example of the present embodiment includes a first center 35 instead of the center 35, and additionally includes a second center 145. The first center 35 includes a center API 135, and the second center 145 includes a first application execution unit 110 and a second application execution unit 120. In addition, the second ECU 15 includes a third application execution unit 130.

[0104] like Figure 8As shown, in the vehicle control system 1 of another example of the present embodiment, the central API 135 has the functions of the request accepting unit 171, the request storage unit 172, the vehicle state determination unit 173, the storage request cancellation determination unit 174, the sending unit 175, the storage request deletion unit 281, the vehicle state DB 81, and the queue 188. The request accepting unit 171, the request storage unit 172, the vehicle state determination unit 173, the storage request cancellation determination unit 174, the sending unit 175, the storage request deletion unit 281, and the queue 188 have the same functions as the request accepting unit 71, the request storage unit 72, the vehicle state determination unit 73, the storage request cancellation determination unit 74, the sending unit 75, the storage request deletion unit 181, and the first queue 88, respectively.

[0105] In the vehicle control system 1 of another example of the present embodiment, the first ECU 10 further includes a vehicle state DB 83, and the third ECU 20 further includes a vehicle state DB 85. The vehicle state DB 81 of the first center 35 stores vehicle data received from a plurality of vehicles via the communication unit 37 in association with vehicle IDs. The vehicle state DBs 83 and 85 of the first ECU 10 and the third ECU 20 store vehicle data of the vehicles on which the first ECU 10 and the third ECU 20 are mounted.

[0106] The request receiving unit 171 of the first center 35 receives the action request and the first cancellation condition corresponding to the action request from the first application executing unit 65 and the second application executing unit 66 of the second center 140. The vehicle state determining unit 173 of the first center 35 acquires the vehicle data on which the first ECU 10 is mounted from the vehicle data stored in the vehicle state DB 81, and determines the vehicle state based on the acquired vehicle data. The sending unit 175 of the first center 35 sends the action request determined as not to be cancelled by the storage request cancellation determining unit 174 and the corresponding first cancellation condition to the first ECU 10.

[0107] The request receiving unit 71 of the first ECU 10 receives the action request determined as not to be canceled and the first cancel condition corresponding to the action request from the first center 35. In addition, the request receiving unit 71 receives the action request and the first cancel condition corresponding to the action request from the third application execution unit 130 of the second ECU 15. The vehicle state determination unit 73 determines the state of the vehicle based on the vehicle data stored in the vehicle state DB 83. The communication unit 75 transmits the action request determined as not to be canceled by the storage request cancellation determination unit 74 and the corresponding first cancel condition to the third ECU 20.

[0108] The receiving unit 76 of the third ECU 20 receives the action request determined not to be canceled and the first cancellation condition corresponding to the action request from the first ECU 10. The vehicle state determination unit 78 determines the state of the vehicle based on the vehicle data stored in the vehicle state DB 85. In addition, one of the vehicle state DBs 83 and 85 may be deleted, and the first ECU 10 and the third ECU 20 may refer to the vehicle data of the remaining one of the vehicle state DBs 83 and 85.

[0109] In the vehicle control system 1 of another example of the present embodiment, an action request is sent from the second center 140 to the third ECU 20 via the first center 35 and the first ECU 10. The first center 35 receives action requests from various application execution units other than the first application execution unit 110 and the second application execution unit 120. Therefore, a large number of action requests are stored in the queue 188, and the state of the vehicle may also change while the action requests received from the first application execution unit 110 and the second application execution unit 120 are pending. Therefore, before sending the action request from the first center 35 to the first ECU 10, the first center 35 determines whether to cancel the action request. That is, in the vehicle control system 1 of another example of the present embodiment, in addition to the first ECU 10 and the third ECU 20, the first center 35 also determines whether to cancel the action request. In the vehicle control system 1 of another example of the present embodiment, the cancellation determination is performed three times.

[0110] In addition, the functions of the receiving unit 76, the request mediation unit 77, the vehicle state determination unit 78, the request cancellation determination unit 79 to be mediated, and the second queue 89 may be provided by any one of the motion system equipment control unit 82, the HMI system state recognition unit 83, and the main body system control unit 84 instead of the state recognition unit 81. In the case where the motion system equipment control unit 82 has the above functions instead of the state recognition unit 81, the first ECU 10 has all the functions of the request receiving unit 71, the request storage unit 72, the vehicle state determination unit 73, the storage request cancellation determination unit 74, the transmission unit 75, the first queue 88, the receiving unit 76, the request mediation unit 77, the vehicle state determination unit 78, the request cancellation determination unit 79 to be mediated, and the second queue 89. Alternatively, the center 35 may have all the functions of a request accepting unit 71, a request storage unit 72, a vehicle state determination unit 73, a storage request cancellation determination unit 74, a sending unit 75, a first queue 88, a receiving unit 76, a request mediation unit 77, a vehicle state determination unit 78, a request cancellation determination unit to be mediated 79, and a second queue 89.

[0111] In addition, Figure 7In the vehicle control system 1 of another example of the present embodiment shown, the first center 35 may also include the functions of the receiving unit 76, the request mediation unit 77, the vehicle state determination unit 78, the pending mediation request cancellation determination unit 79, and the second queue 89 instead of the state recognition unit 81. In this case, the pending mediation request cancellation determination unit 79 of the first center 35 sends the action request determined not to be cancelled to the vehicle API 85.

[0112] <2. Processing>

[0113] Reference Figure 5 The sequence diagram of Figure 1 A control process executed by an example of the vehicle control system 1 according to the embodiment shown will be described.

[0114] In S10 , the first application execution unit 63 transmits the first cancellation condition corresponding to the first action request to the first ECU 10 . Next, in S20 , the request storage unit 72 stores the first cancellation condition in correspondence with the first action request and stores the first action request in the first queue 88 .

[0115] Next, in S30 , the second application execution unit 64 sends the first cancellation condition corresponding to the second action request to the first ECU 10 . Next, in S40 , the request storage unit 72 stores the first cancellation condition in correspondence with the second action request and stores the second action request in the first queue 88 .

[0116] Next, in S50, the vehicle state determination unit 73 determines the state of the vehicle, and transmits the determined vehicle state to the storage request cancellation determination unit 74. The storage request cancellation determination unit 74 stores the received vehicle state.

[0117] Next, in S60, the request storage unit 72 sends the first action request and the corresponding first cancellation condition after the pending state ends to the storage request cancellation determination unit 74. In addition, the request storage unit 72 may also send the first action request and the corresponding first cancellation condition to the storage request cancellation determination unit 74 at a set time (for example, at a time when X seconds have passed after reception) or periodically in the pending state.

[0118] Next, in S70 , the storage request cancellation determination unit 74 determines whether to cancel the first operation request based on the received vehicle state and the first cancellation condition and the second cancellation condition set and stored by the vehicle API 85 .

[0119] In S80, storage request cancellation determination unit 74 determines cancellation of the first action request based on whether the first cancellation condition or the second cancellation condition is satisfied. Storage request deletion unit 181 deletes the first action request from first queue 88 and notifies first application execution unit 63 of cancellation of the first action request.

[0120] Next, in S90, the request storage unit 72 sends the second action request and the corresponding first cancellation condition after the pending state ends to the storage request cancellation determination unit 74. In addition, the request storage unit 72 may also send the second action request and the corresponding first cancellation condition to the storage request cancellation determination unit 74 at a set time (for example, at a time when Y seconds have passed after reception) or periodically in the pending state.

[0121] Next, in S100 , the storage request cancellation determination unit 74 determines whether to cancel the second operation request based on the received vehicle state and the first cancellation condition and the second cancellation condition.

[0122] In S110, based on the fact that the first cancellation condition and the second cancellation condition are not satisfied, the second action request and the corresponding first cancellation condition are sent from the storage request cancellation determination unit 74 to the request mediation unit 77. The request mediation unit 77 stores the first cancellation condition in correspondence with the second action request and stores the second action request in the second queue 89.

[0123] In S120, the request mediation unit 77 mediates between the second action request and the action request competing with the second action request stored in the second queue 89. Mediation here is a process of setting a priority sequence for a plurality of action requests competing with each other in the second queue 89 according to a mediation rule set in advance by the vehicle API 85 and / or a mediation rule set by the application execution unit. In the mediation rule, for example, a priority for each action request is set in correspondence with the state of the vehicle. The state to be mediated corresponds to the period before the action request that was not immediately executed due to the set priority sequence becomes executable.

[0124] In S130 , the request mediation unit 77 sends the second action request and the corresponding first cancellation condition to the pending mediation request cancellation determination unit 79 based on the termination of the pending mediation state of the second action request.

[0125] Next, in S140 , the mediation request cancellation determination unit 79 determines whether to cancel the second operation request based on the acquired vehicle state, the first cancellation condition, and the second cancellation condition.

[0126] Next, refer to Fig. 9A and 9B The sequence diagram of Figure 7A control process executed by another example of the vehicle control system 1 according to the present embodiment will be described.

[0127] In S210, the first application execution unit 110 of the second center 140 executes the same process as S10. Next, in S220, the request storage unit 172 of the first center 35 executes the same process as S20.

[0128] Next, in S230, the second application execution unit 120 of the second center 140 executes the same process as S30. Next, in S240, the request storage unit 172 of the first center 35 executes the same process as S40.

[0129] Next, in S250, the vehicle state determination unit 173 of the first center 35 performs the same process as S50. Next, in S260, the request storage unit 172 of the first center 35 performs the same process as S60. Next, in S270, the storage request cancellation determination unit 174 of the first center 35 performs the same process as S70.

[0130] Next, in S280, the storage request cancellation determination unit 174 of the first center 35 determines the cancellation of the first action request. Then, the storage request deletion unit 281 of the first center 35 deletes the first action request from the queue 18 and notifies the first application execution unit 110 of the second center 140 that the first action request has been cancelled.

[0131] Next, in S290, the request storage unit 172 of the first center 35 executes the same process as S90. Next, in S300, the storage request cancellation determination unit 174 of the first center 35 executes the same process as S100.

[0132] Next, in S310 , the storage request cancellation determination unit 174 of the first center 35 determines not to cancel the second operation request, and transmits the second operation request and the corresponding first cancellation condition to the first ECU 10 .

[0133] Next, in S320, the request storage unit 72 of the first ECU 10 performs the same process as S20. Next, in S330, the third application execution unit 130 of the second ECU 15 sends the third action request and the corresponding first cancellation condition to the first ECU 10. Next, in S340, the request storage unit 72 of the first ECU 10 performs the same process as S40.

[0134] Next, in S350, the vehicle state determination unit 73 of the first ECU 10 performs the same process as S50. Next, in S360, the request storage unit 72 of the first ECU 10 performs the same process as S60. Next, in S370, the storage request cancellation determination unit 74 of the first ECU 10 performs the same process as S70.

[0135] Next, in S380 , the storage request cancellation determination unit 74 of the first ECU 10 determines the cancellation of the second action request. The storage request deletion unit 181 of the first ECU 10 deletes the second action request from the first queue and notifies the second application execution unit 120 of the second center 140 of the cancellation of the second action request.

[0136] Next, in S390, the request storage unit 72 of the first ECU 10 performs the same process as S90. Next, in S400, the storage request cancellation determination unit 74 of the first ECU 10 performs the same process as S100. Next, in S410, the storage request cancellation determination unit 74 of the first ECU 10 determines not to cancel the third action request, and sends the third action request and the corresponding first cancellation condition to the third ECU 20. The request mediation unit 77 of the third ECU 20 stores the first cancellation condition in correspondence with the third action request, and stores the third action request in the second queue 89.

[0137] Next, in S420 and S430, the request mediation unit 77 of the third ECU 20 executes the same processing as S120 and S130. Next, in S440, the mediation request cancellation determination unit 79 of the third ECU 20 executes the same processing as S140.

[0138] In the vehicle control system 1 of another example of the present embodiment, the first center 35 has the functions of the receiving unit 76, the request mediation unit 77, the vehicle state determination unit 78, the pending mediation request cancellation determination unit 79, and the second queue 89. Figure 5 In the sequence diagram shown, the second center 140 executes the processes of S10 and S30, and the first center 35 executes the processes of S20 and S40 to S140.

[0139] <3. Effect>

[0140] According to the first embodiment described in detail above, the following effects are achieved.

[0141] (1) The request accepting unit 71 receives the action request and the first cancellation condition. Furthermore, when the waiting state of the action request in the first queue 88 ends, the storage request cancellation determination unit 74 determines whether to cancel the action request stored in the first queue 88 based on the vehicle state, the first cancellation condition, and the second cancellation condition. Therefore, it is possible to avoid executing unnecessary action requests during the waiting state of the action request. Furthermore, it is possible to realize vehicle control that does not give the user a sense of discomfort.

[0142] (2) The first cancellation condition is set by the application execution unit (i.e., the application creator including a third party, etc.) to ensure the convenience of the user. The second cancellation condition is set by the vehicle API 85 (i.e., the platform) to ensure the safety of the vehicle and to force the cancellation of the action request. By executing the cancellation determination of the action request based on the first cancellation condition, the action request that has missed the execution period is immediately canceled. In addition, by executing the cancellation determination of the action request based on the second cancellation condition, the action request is canceled even in the state of the vehicle where the application execution unit is not set as a cancellation condition. That is, by executing the cancellation determination of the action request based on two cancellation conditions set from the respective perspectives of the application creator and the platform, both convenience and safety can be guaranteed.

[0143] (3) Since the first cancellation condition includes a condition related to the state of the vehicle, whether to cancel the action request stored in the first queue 88 is determined according to the state of the vehicle. Therefore, it is possible to avoid executing an action request that is unnecessary for the state of the vehicle.

[0144] (4) There is a possibility that the state of the vehicle changes during the period when the action request is waiting for mediation. When the action request changes from the waiting for mediation state to the executable state, it is determined again whether to cancel the action request based on the state of the vehicle, the first cancellation condition, and the second cancellation condition. In this way, it is possible to appropriately avoid executing unnecessary action requests during the period when the action request is waiting for mediation.

[0145] (5) The cancellation determination of the action request is performed by both the storage request cancellation determination unit 74 and the request to be mediated cancellation determination unit 79. In the case where the cancellation determination of the action request is performed only by the storage request cancellation determination unit 74, the state of the vehicle changes during the period from when the cancellation determination is not to be cancelled to when the waiting for mediation is completed, and the action request may become unnecessary or impossible to perform. In other words, an action request that is unnecessary or impossible to perform may be performed. In the case where the cancellation determination of the action request is performed only by the request to be mediated cancellation determination unit 79, the action request that is no longer necessary or impossible to perform is stored in the second queue 89, and mediation with other action requests is performed. Therefore, unnecessary mediation is performed, and the processing load is increased. By having both the storage request cancellation determination unit 74 and the request to be mediated cancellation determination unit 79 perform the cancellation determination of the action request, it is possible to avoid the execution of action requests that are unnecessary or impossible to perform, and to suppress the processing load.

[0146] (6) The first and second application execution units 61 to 66 select from a plurality of pre-set abstract vehicle states and set the conditions under the selected vehicle state as the first cancellation condition. Therefore, a third party who is not familiar with vehicles can easily develop an application to specify the first cancellation condition.

[0147] (Other embodiments)

[0148] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, Various deformation|transformation and implementation are possible.

[0149] (a) The microcomputers 11, 36 and methods thereof described in the present disclosure may be implemented by a special-purpose computer, which is provided by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the microcomputers 11, 36 and methods thereof described in the present disclosure may be implemented by a special-purpose computer, which is provided by a processor composed of one or more special-purpose hardware logic circuits. Alternatively, the microcomputers 11, 36 and methods thereof described in the present disclosure may be implemented by one or more special-purpose computers, which are composed of a combination of a processor and a memory programmed to execute one or more functions and a processor composed of one or more hardware logic circuits. In addition, a computer program may also be stored as an instruction executed by a computer in a non-transitional tangible recording medium readable by a computer. The method for implementing the functions of each part included in the microcomputer 11, 36 does not necessarily need to include software, and all of its functions may be implemented using one or more hardware.

[0150] (b) It is also possible that multiple functions of one component in the above-mentioned embodiment are realized by multiple components, or that one function of one component is realized by multiple components. In addition, it is also possible that multiple functions of multiple components are realized by one component, or that one component realizes a function realized by multiple components. In addition, it is also possible to omit a part of the structure of the above-mentioned embodiment. In addition, it is also possible to add at least a part of the structure of the above-mentioned embodiment to the structure of other above-mentioned embodiments, or to replace at least a part of the structure of the above-mentioned embodiment.

[0151] (c) In addition to the above-mentioned vehicle-mounted device and central device, the present disclosure can also be implemented in various forms such as a system with the vehicle-mounted device and central device as components, a program for causing a computer to function as the vehicle-mounted device or central device, a non-transitional physical recording medium such as a semiconductor memory recording the program, and a vehicle control method.

[0152] [Technical idea disclosed in this specification]

[0153] [Project 1]

[0154] A vehicle-mounted device is a vehicle-mounted device (10, 20) mounted on a vehicle, comprising:

[0155] a request receiving unit (71) configured to receive the vehicle action request and a first cancellation condition from an application execution unit (63, 64, 65, 66), wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0156] a request storage unit (72) configured to store the action request received by the request receiving unit in a first queue (88);

[0157] a storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0158] A storage request deleting unit (181) deletes the action request from the first queue when the storage request cancellation determining unit determines that the action request is to be cancelled.

[0159] [Project 2]

[0160] The vehicle-mounted device according to item 1, wherein:

[0161] The first cancellation condition includes a condition related to the state of the vehicle.

[0162] [Item 3]

[0163] The vehicle-mounted device according to item 1 or 2, further comprising:

[0164] a request mediation unit (77) configured to receive the action request determined as not to be cancelled by the storage request cancellation determination unit (74) and store it in a second queue (89), and mediate between the action request and competing requests stored in the second queue;

[0165] a pending mediation request cancellation determination unit (78) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; and

[0166] The pending mediation request deleting unit (82) is configured to delete the action request from the second queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

[0167] [Item 4]

[0168] The vehicle-mounted device according to item 3, wherein:

[0169] The vehicle-mounted device (10, 20) comprises a first device (10) and a second device (20),

[0170] The first device comprises the request receiving unit (71), the request storage unit (72), the storage request cancellation determination unit (74) and the storage request deletion unit (181).

[0171] The second device comprises the request mediation unit (77), the pending mediation request cancellation determination unit (79), and the pending mediation request deletion unit (182).

[0172] [Item 5]

[0173] The vehicle-mounted device according to any one of items 1 to 4, wherein:

[0174] The application execution unit (63, 64, 65, 66) is configured to select a vehicle state from a plurality of pre-set abstract vehicle states and set a condition in the selected vehicle state as the first cancellation condition.

[0175] [Item 6]

[0176] A central device is a central device (35) configured to perform wireless communication with a vehicle, comprising:

[0177] a request receiving unit (71) configured to receive the vehicle action request and a first cancellation condition from an application execution unit (61, 62, 63, 64), wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0178] a request storage unit (72) configured to store the action request received by the request receiving unit in a first queue (88);

[0179] a storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0180] A storage request deleting unit (181) deletes the action request from the first queue when the storage request cancellation determining unit determines that the action request is to be cancelled.

[0181] [Item 7]

[0182] The central device according to item 6, wherein:

[0183] The first cancellation condition includes a condition related to the state of the vehicle.

[0184] [Item 8]

[0185] The central device according to item 6 or 7, further comprising:

[0186] a request mediation unit (77) configured to receive the action request determined as not to be cancelled by the storage request cancellation determination unit (74) and store it in a second queue (89), and mediate between the action request and competing requests stored in the second queue;

[0187] a pending mediation request cancellation determination unit (79) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; and

[0188] The pending mediation request deleting unit (182) is configured to delete the action request from the second queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

[0189] [Item 9]

[0190] The central device according to any one of items 6 to 8, wherein:

[0191] The application execution unit (61, 62, 63, 64) is configured to select a vehicle state from a plurality of pre-set abstract vehicle states and set a condition in the selected vehicle state as the first cancellation condition.

[0192] [Item 10]

[0193] A vehicle control program causes a processing device (11, 36) to perform the following processing:

[0194] receiving a vehicle action request and a first cancellation condition (S10, S30) from an application execution unit (61, 62, 63, 64, 65, 66), wherein the application execution unit is configured to execute application software, the vehicle action request is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0195] The received action request is stored in a queue (S20, S40);

[0196] determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S70, S100), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0197] When it is determined that the action request is to be canceled, the action request is deleted from the queue (S80).

[0198] [Item 11]

[0199] A vehicle control method is a vehicle control method executed by a processing device (11, 36), comprising:

[0200] receiving a vehicle action request and a first cancellation condition (S10, S30) from an application execution unit (61, 62, 63, 64, 65, 66), wherein the application execution unit is configured to execute application software, the vehicle action request corresponds to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0201] The received action request is stored in a queue (S20, S40);

[0202] determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S70, S100), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0203] When it is determined that the action request is to be canceled, the action request is deleted from the queue (S80).

[0204] [Item 12]

[0205] A vehicle control program causes a central device (35) configured to wirelessly communicate with a vehicle to execute the following processing:

[0206] receiving an action request of the vehicle and a first cancellation condition (S210, S230) from an application execution unit (61, 62, 63, 64, 65, 66), wherein the application execution unit is configured to execute application software, the action request of the vehicle is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0207] The received action request is stored in a queue (S220, S240);

[0208] determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S270, S300), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0209] When it is determined that the action request is to be canceled, the action request is deleted from the queue (S280).

[0210] [Item 13]

[0211] A vehicle control method is executed by a central device (35) configured to wirelessly communicate with a vehicle, comprising:

[0212] receiving an action request of the vehicle and a first cancellation condition (S210, S230) from an application execution unit (61, 62, 63, 64, 65, 66), wherein the application execution unit is configured to execute application software, the action request of the vehicle is responsive to the execution of the application software, and the first cancellation condition is a condition for canceling the action request;

[0213] The received action request is stored in a queue (S220, S240);

[0214] determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S270, S300), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0215] When it is determined that the action request is to be canceled, the action request is deleted from the queue (S280).

[0216] [Item 14]

[0217] A vehicle control system comprises a first vehicle-mounted device (10) and a second vehicle-mounted device (20) mounted on a vehicle, and a central device (35) configured to wirelessly communicate with the first vehicle-mounted device.

[0218] The above-mentioned central device has:

[0219] a first request receiving unit (171) configured to receive the vehicle action request and a first cancellation condition from a first application executing unit (110, 120), wherein the first application executing unit is configured to execute a first application software, the vehicle action request is in response to the execution of the first application software, and the first cancellation condition is a condition for canceling the action request;

[0220] a first request storage unit (172) configured to store the action request received by the first request receiving unit in a first queue (188);

[0221] a first storage request cancellation determination unit (174) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the first request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0222] A first storage request deletion unit (181) is configured to delete the action request from the first queue when the first storage request cancellation determination unit determines that the action request is to be cancelled.

[0223] The first vehicle-mounted device comprises:

[0224] a second request receiving unit (71) configured to receive the action request determined by the first storage request cancellation determination unit to be non-cancellable and the first cancellation condition;

[0225] a second request storage unit (72) configured to store the action request received by the second request receiving unit in a second queue (88);

[0226] a second storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the second queue based on the first cancellation condition received by the second request acceptance unit and the preset second cancellation condition; and

[0227] A second storage request deleting unit (81) is configured to delete the action request from the second queue when the second storage request cancellation determining unit determines that the action request is to be cancelled.

[0228] The second vehicle-mounted device comprises:

[0229] a request mediation unit (77) configured to receive the action request determined by the second storage request cancellation determination unit as not to be cancelled and store it in a third queue (89), and mediate between the action request and competing requests stored in the third queue;

[0230] a pending mediation request cancellation determination unit (79) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; and

[0231] The pending mediation request deleting unit (182) deletes the action request from the third queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

[0232] [Item 15]

[0233] The vehicle control system according to item 14, wherein:

[0234] The second request receiving unit (71) is configured to receive the vehicle's action request and the corresponding first cancellation condition from the second application execution unit (130), wherein the second application execution unit is configured to execute second application software, and the vehicle's action request responds to the execution of the second application software.

[0235] [Item 16]

[0236] A vehicle control method is performed by a system including a first vehicle-mounted device (10) and a second vehicle-mounted device (20) mounted on a vehicle, and a center device (35) configured to perform wireless communication with the first vehicle-mounted device.

[0237] The above central device performs the following steps:

[0238] receiving the vehicle action request and a first cancellation condition from a first application execution unit (110, 120), wherein the first application execution unit is configured to execute a first application software, the vehicle action request is sent in response to the first application and the software is executed, and the first cancellation condition is a condition for canceling the action request;

[0239] storing the received action request into a first queue;

[0240] determining whether to cancel the action request stored in the first queue according to the received first cancellation condition and second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and

[0241] If it is determined that the action request is to be cancelled, the action request is deleted from the first queue.

[0242] The first vehicle-mounted device performs the following steps:

[0243] receiving the action request and the first cancellation condition determined by the central device to be non-cancellable;

[0244] storing the received action request into a second queue;

[0245] determining whether to cancel the action request stored in the second queue according to the received first cancellation condition and the preset second cancellation condition; and

[0246] If it is determined that the action request is to be cancelled, the action request is deleted from the second queue.

[0247] The second vehicle-mounted device performs the following steps:

[0248] receiving the action request determined by the first vehicle-mounted device to be not cancelable and storing it in a third queue;

[0249] performing mediation between the action request and competing requests stored in the third queue;

[0250] determining whether to cancel the action request according to the first cancellation condition and the second cancellation condition; and

[0251] If it is determined that the action request is to be canceled, the action request is deleted from the third queue.

Claims

1. A vehicle-mounted device, which is a vehicle-mounted device (10, 20) mounted on a vehicle, comprising: A request receiving unit (71) is configured to receive the vehicle operation request and the first cancellation condition from the application execution unit (63, 64, 65, 66), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; a request storage unit (72) configured to store the action request received by the request receiving unit in a first queue (88); a storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and A storage request deleting unit (181) deletes the action request from the first queue when the storage request cancellation determining unit determines that the action request is to be cancelled.

2. The vehicle-mounted device according to claim 1, wherein: The first cancellation condition includes a condition related to the state of the vehicle.

3. The vehicle-mounted device according to claim 1 or 2, wherein: Also available: a request mediation unit (77) configured to receive the action request determined as not to be cancelled by the storage request cancellation determination unit (74) and store it in a second queue (89), and mediate between the action request and competing requests stored in the second queue; a pending mediation request cancellation determination unit (79) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; as well as The pending mediation request deleting unit (182) is configured to delete the action request from the second queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

4. The vehicle-mounted device according to claim 3, wherein: The application execution unit (63, 64, 65, 66) is configured to select a vehicle state from a plurality of pre-set abstract vehicle states and set a condition in the selected vehicle state as the first cancellation condition.

5. The vehicle-mounted device according to claim 3, wherein: The vehicle-mounted device (10, 20) comprises a first device (10) and a second device (20), The first device comprises the request receiving unit (71), the request storage unit (72), the storage request cancellation determination unit (74) and the storage request deletion unit (181). The second device comprises the request mediation unit (77), the pending mediation request cancellation determination unit (79), and the pending mediation request deletion unit (182).

6. A central device, which is a central device (35) configured to perform wireless communication with a vehicle, comprising: A request receiving unit (71) is configured to receive the vehicle operation request and the first cancellation condition from the application execution unit (61, 62, 63, 64), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; a request storage unit (72) configured to store the action request received by the request receiving unit in a first queue (88); a storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and A storage request deleting unit (181) deletes the action request from the first queue when the storage request cancellation determining unit determines that the action request is to be cancelled.

7. The central device according to claim 6, wherein: The first cancellation condition includes a condition related to the state of the vehicle.

8. The central device according to claim 6 or 7, wherein: Also available: a request mediation unit (77) configured to receive the action request determined as not to be cancelled by the storage request cancellation determination unit (74) and store it in a second queue (89), and mediate between the action request and competing requests stored in the second queue; a pending mediation request cancellation determination unit (79) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; as well as The pending mediation request deleting unit (182) is configured to delete the action request from the second queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

9. The central device according to claim 8, wherein: The application execution unit (61, 62, 63, 64) is configured to select a vehicle state from a plurality of pre-set abstract vehicle states and set a condition in the selected vehicle state as the first cancellation condition.

10. A vehicle control program causing a processing device (11, 36) to execute the following processing: A vehicle operation request and a first cancellation condition (S10, S30) are received from an application execution unit (61, 62, 63, 64, 65, 66), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; The received action request is stored in a queue (S20, S40); determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S70, S100), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and When it is determined that the action request is to be canceled, the action request is deleted from the queue (S80).

11. A vehicle control method, the vehicle control method being executed by a processing device (11, 36), comprising: A vehicle operation request and a first cancellation condition (S10, S30) are received from an application execution unit (61, 62, 63, 64, 65, 66), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; The received action request is stored in a queue (S20, S40); determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S70, S100), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and When it is determined that the action request is to be canceled, the action request is deleted from the queue (S80).

12. A vehicle control program causing a center device (35) configured to wirelessly communicate with a vehicle to execute the following processing: The application execution unit (61, 62, 63, 64, 65, 66) receives the vehicle operation request and the first cancellation condition (S210, S230), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; The received action request is stored in a queue (S220, S240); determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S270, S300), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and When it is determined that the action request is to be canceled, the action request is deleted from the queue (S280).

13. A vehicle control method, the method being executed by a central device (35) configured to wirelessly communicate with a vehicle, comprising: The application execution unit (61, 62, 63, 64, 65, 66) receives the vehicle operation request and the first cancellation condition (S210, S230), wherein: The application execution unit is configured to execute application software, the vehicle action request is in response to the execution of the application software, and the first cancellation condition is a condition for canceling the action request; The received action request is stored in a queue (S220, S240); determining whether to cancel the action request stored in the queue according to the first cancellation condition and the second cancellation condition (S270, S300), wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and When it is determined that the action request is to be canceled, the action request is deleted from the queue (S280).

14. A vehicle control system comprising a first vehicle-mounted device (10) and a second vehicle-mounted device (20) mounted on a vehicle, and a central device (35) configured to wirelessly communicate with the first vehicle-mounted device, The above-mentioned central device has: The first request receiving unit (171) is configured to receive the vehicle operation request and the first cancellation condition from the first application executing unit (110, 120), wherein: The first application execution unit is configured to execute a first application software, the vehicle action request is in response to the execution of the first application software, and the first cancellation condition is a condition for canceling the action request; a first request storage unit (172) configured to store the action request received by the first request receiving unit in a first queue (188); a first storage request cancellation determination unit (174) configured to determine whether to cancel the action request stored in the first queue based on the first cancellation condition and the second cancellation condition, wherein the first cancellation condition is a condition received by the first request receiving unit, and the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and A first storage request deletion unit (181) is configured to delete the action request from the first queue when the first storage request cancellation determination unit determines that the action request is to be cancelled. The first vehicle-mounted device comprises: a second request receiving unit (71) configured to receive the action request determined by the first storage request cancellation determination unit to be non-cancellable and the first cancellation condition; a second request storage unit (72) configured to store the action request received by the second request receiving unit in a second queue (88); a second storage request cancellation determination unit (74) configured to determine whether to cancel the action request stored in the second queue based on the first cancellation condition received by the second request acceptance unit and the preset second cancellation condition; and A second storage request deleting unit (81) is configured to delete the action request from the second queue when the second storage request cancellation determining unit determines that the action request is to be cancelled. The second vehicle-mounted device comprises: a request mediation unit (77) configured to receive the action request determined by the second storage request cancellation determination unit as not to be cancelled and store it in a third queue (89), and mediate between the action request and competing requests stored in the third queue; a pending mediation request cancellation determination unit (79) configured to determine whether to cancel the action request based on the first cancellation condition and the second cancellation condition; and The pending mediation request deleting unit (182) deletes the action request from the third queue when the pending mediation request cancellation determining unit determines that the action request is to be cancelled.

15. The vehicle control system according to claim 14, wherein: The second request receiving unit (71) is configured to receive the vehicle's action request and the corresponding first cancellation condition from the second application execution unit (130), wherein the second application execution unit is configured to execute second application software, and the vehicle's action request responds to the execution of the second application software.

16. A vehicle control method, the vehicle control method being executed by a system comprising a first vehicle-mounted device (10) and a second vehicle-mounted device (20) mounted on a vehicle, and a central device (35) configured to perform wireless communication with the first vehicle-mounted device, The above central device performs the following steps: The first application execution unit (110, 120) receives the vehicle action request and the first cancellation condition, wherein: The first application execution unit is configured to execute a first application software, the vehicle action request is in response to the execution of the first application software, and the first cancellation condition is a condition for canceling the action request; storing the received action request into a first queue; determining whether to cancel the action request stored in the first queue according to the received first cancellation condition and second cancellation condition, wherein the second cancellation condition is a condition for canceling the action request and is a pre-set condition related to the method of using the vehicle; and If it is determined that the action request is to be cancelled, the action request is deleted from the first queue. The first vehicle-mounted device performs the following steps: receiving the action request and the first cancellation condition determined by the central device to be non-cancellable; storing the received action request into a second queue; determining whether to cancel the action request stored in the second queue according to the received first cancellation condition and the preset second cancellation condition; and If it is determined that the action request is to be cancelled, the action request is deleted from the second queue. The second vehicle-mounted device performs the following steps: receiving the action request determined by the first vehicle-mounted device to be not cancelable and storing it in a third queue; performing mediation between the action request and competing requests stored in the third queue; determining whether to cancel the action request according to the first cancellation condition and the second cancellation condition; and If it is determined that the action request is to be canceled, the action request is deleted from the third queue.

Citation Information

Patent Citations

  • Arbitration system for vehicle

    JP2020064489A

  • Semiconductor device and semiconductor circuit

    JP2022145318A