VEHICLE CONTROL SYSTEM

The vehicle control system dynamically adjusts the roles of OS programs in electronic control units to facilitate efficient collaboration, addressing compatibility issues and enhancing adaptability across different vehicle grades and hardware configurations.

DE102017200286B4Active Publication Date: 2024-11-07DENSO CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
DE102017200286
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2016-01-22
Filing Date
2017-01-10
Publication Date
2024-11-07
Estimated Expiration
2037-01-10

AI Technical Summary

Technical Problem

Existing vehicle control systems face challenges in efficiently supporting collaborative processing between electronic control units due to fixed role assignments that do not align with the capabilities of individual units, leading to compatibility issues with variations in vehicle grade, model, or hardware changes.

Method used

A vehicle control system where first and second electronic control units include OS programs that dynamically adjust their roles based on the assigned roles of the second OS program, allowing efficient collaboration by acquiring and determining appropriate roles for the first OS program to work in conjunction with the second, even with variations in capabilities.

Benefits of technology

This approach enables flexible and efficient collaborative processing between electronic control units, supporting variations in vehicle functionality and hardware without requiring fixed role assignments, thus enhancing compatibility and adaptability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Vehicle control system comprising a first electronic control unit (40) and a second electronic control unit (60, 70, 80) which perform joint processing for controlling a vehicle-mounted device (31 to 33) mounted in a vehicle, wherein: the first electronic control unit is a master ECU and the second electronic control unit is a slave ECU; the first electronic control unit and the second electronic control unit each contain joint processing application programs (41a, 61a, 71a, 81a) for carrying out the joint processing; the first electronic control unit includes a first OS program (41b); the second electronic control unit includes a second OS program (61b, 71b, 81b); The first and second OS programs each support verification of communication data between the first and second electronic control units, data conversion, and a synchronization mechanism; The first OS program and the second OS program work together in cooperation under a predetermined role assignment and serve as basic software for the respective joint processing application programs that are to be executed in cooperation with each other; the second electronic control unit stores role pattern information that uniquely specifies a combination of roles of the second OS program, and transmits the role pattern information to the first electronic control unit according to a configuration of the vehicle control system or the capabilities of the second electronic control unit; the second OS program installed in the second electronic control unit has an assigned role that is selected from different roles; the first OS program installed in the first electronic control unit is designed such that the role assigned to the first OS program is changeable, so that the first OS program can perform an operation in conjunction with the second OS program, even if any of the various roles is assigned to the second OS program; and the first electronic control unit includes an acquisition unit (S100) which acquires the role pattern information as information about the role assigned to the second OS program from the second electronic control unit, and an investigation unit (S120) which, based on the information acquired by the acquisition unit and indicative of the role assigned to the second OS program, determines the role to be assigned to the first OS program so that the first OS program can work in cooperation with the second OS program.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to a vehicle control system in which a first electronic control unit and a second electronic control unit cooperate with each other to perform processing to control a vehicle-mounted device mounted in a vehicle.

[0002] For example, JP 2009-56817 A discloses a control system for a vehicle-mounted electronic device, which includes a plurality of control units arranged hierarchically. The control system for the vehicle-mounted electronic device is applied, for example, to the operation control of a rear window defogger and a defroster. The control system for the vehicle-mounted electronic device includes a control unit (ECU). 11 a basic control system for the rear window defogging device and an ECU control unit 21an automatic expansion function system, which is higher in the hierarchy than the control unit ECU 11 . In addition, the control system of the vehicle-mounted electronic device includes a control unit ECU 12 a basic control system for the de-icer and a control unit ECU 22 an automatic expansion function system, which is higher in the hierarchy than the control unit ECU 12 Furthermore, the control system for the vehicle-mounted electronic device comprises a common control unit ECU 31 , which is higher in the hierarchy than the control unit ECU 21 of the automatic expansion function system for the rear window defogger and the control unit ECU 22 of the automatic expansion function system for the de-icer.

[0003] In the above configuration, when a rear window defogger switch is turned on, the control unit ECU 11 of the basic control system performs a power supply control of the rear window defogging system. In this situation, the ECU measures 21 of the automatic expansion function system, an operating time of the rear window defogger by means of a timer and performs an automatic control to automatically switch off the rear window defogger when the time has elapsed.

[0004] When a windshield defogger switch is turned on, the ECU selects 12 of the basic control system, the defroster is activated as a blowing mode of an air conditioner. The control unit ECU 22The automatic expansion function system records outside air temperatures detected by an outside air temperature sensor and a history of user operation of the windshield defogger switch, and cumulatively learns windshield fogging conditions. Next time, the ECU executes 22 of the automatic expansion function system, the automatic control to automatically turn on the defroster when the detected outside air temperature meets the window defogging conditions, even if the windshield defogger switch is not operated.

[0005] Furthermore, the Community tax unit ECU 31The system records the operation histories of the rear window defogger and the defroster and learns a joint operation. For example, assume that the learning result is such that the frequency of the rear window defogger's operation while the defroster is operating is equal to or greater than a certain frequency. In this case, when the defroster starts operating, the joint control unit (ECU) 31 a command to automatically switch on the rear window anti-fogging system to the ECU control unit 21 of the automatic expansion function system for the rear window defogging system.

[0006] As in the control system for the vehicle-mounted electronic device disclosed in JP 2009-56817 A, the control system may include the plurality of electronic control units (ECUs), and the ECUs may perform collaborative control. For example, to perform collaborative control, assume that signals exchanged between the ECUs, processing steps, and the like are strictly predetermined, and collaborative processing application programs are generated accordingly. In this case, the control system results in a so-called dedicated product, making it difficult to be compatible with variations from low function to high function corresponding to, for example, a vehicle grade or vehicle model, or to be compatible with a change in ECU hardware.

[0007] In this regard, it is conceivable that for the joint processing performed by a first electronic control unit and a second electronic control unit, OS programs serving as basic software for jointly executing the joint processing application programs are installed in the respective first and second electronic control units in addition to the joint processing application programs.

[0008] For example, the OS program supports the verification of communication data between the respective electronic control units, data conversion, a synchronization mechanism, and resource allocation, among other things. As a result, the shared processing application programs in the first electronic control unit and the second electronic control unit can be created to be specialized in the respective control functions, and can easily cope with the addition, modification, and the like of the control functions. Furthermore, from this perspective, the deployment flexibility of the shared processing application programs can be increased because the respective OS programs can abstract the hardware of the respective electronic control units.

[0009] However, when OS programs that support collaborative processing in the first electronic control unit and the second electronic control unit are installed in the respective first electronic control unit and the respective second electronic control unit, these OS programs must operate in cooperation with each other under a given role allocation. However, if the role allocation is always kept constant, the roles do not always correspond to the capabilities of the respective electronic control units, for example, due to a difference in the capabilities between the electronic control units to be used or the like, and collaborative processing cannot be supported efficiently.

[0010] DE 11 2009 001 818 T5 discloses a control device comprising: a first execution device for executing one or more application programs; and a second execution device for executing a platform program that controls an operation of a hardware resource in response to a request from the application program, wherein the first and second execution devices are each provided with a plurality of function execution devices, the function execution devices are each related to attribute information representing an attribute of a function, and the control device further comprises: a device for selecting attribute information; and a device for allocating function execution devices to which the attribute information is collectively related.

[0011] DE 41 11 023 A1 discloses an electronic system for a vehicle, which consists of elements for performing control tasks at least with regard to engine power, drive power, and braking, and elements that coordinate the interaction of the elements for performing control tasks in the sense of controlling the operating behavior of the vehicle in accordance with the driver's wishes. The elements are arranged in the form of a hierarchy, with at least one coordination element of a hierarchy level intervening in the implementation of the driver's wish into a corresponding operating behavior on the elements of the next hierarchy level and thus on a predetermined subsystem of the driver-vehicle system, providing the behavior required by the higher hierarchy level for this subsystem.

[0012] In view of the above difficulties, it is an object of the present invention to provide a vehicle control system capable of efficiently supporting joint processing of a first electronic control unit and a second electronic control unit through the aid of respective OS programs installed in the first electronic control unit and the second electronic control unit. This object is achieved by a vehicle control system having the features of claim 1. The dependent claims are directed to advantageous developments of the invention.

[0013] A vehicle control system according to one aspect of the present invention includes a first electronic control unit and a second electronic control unit that perform collaborative processing for controlling a vehicle-mounted device mounted in a vehicle. The first electronic control unit and the second electronic control unit each include collaborative processing application programs for performing the collaborative processing. The first electronic control unit includes a first OS program. The second electronic control unit includes a second OS program. The first OS program and the second OS program operate in cooperation with each other under a predetermined role assignment and serve as basic software for the respective collaborative processing application programs to be executed in cooperation with each other.The second OS program installed in the second electronic control unit has an assigned role selected from a plurality of different roles. The second OS program installed in the second electronic control unit has an assigned role selected from different roles. The first OS program installed in the first electronic control unit is configured such that the role assigned to the first OS program is changeable, so that the first OS program can perform an operation collaboratively with the second OS program even if any of the different roles is assigned to the second OS program. The first electronic control unit includes an acquisition unit and a determination unit. The acquisition unit acquires information about the role assigned to the second OS program from the second electronic control unit.Based on the information acquired by the acquisition unit indicative of the role assigned to the second OS program, the investigation unit determines the role to be assigned to the first OS program so that the first OS program can work in cooperation with the second OS program.

[0014] According to the vehicle control system, the first OS program installed in the first electronic control unit acquires the information about the role assigned to the second OS program and, based on the information indicating the role assigned to the second OS program, determines the role to be assigned to the first OS program so that the first OS program can operate in cooperation with the second OS program. Therefore, even if, for example, the role assignment to the second OS program varies due to the capability of the second electronic control unit, the assigned role can be automatically changed so that the first OS program can operate in cooperation with the second OS program according to the variation in the role assignment.As a result, the joint processing of the first electronic control unit and the second electronic control unit can be efficiently supported by the OS programs installed in the first electronic control unit and the second electronic control unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and other objects, features, and advantages of the present invention will become more apparent from the following detailed description made with reference to the accompanying drawings. In the drawings: Fig. 1 is a diagram illustrating a configuration of a vehicle control system according to an embodiment; Fig. 2 is a diagram illustrating an example in which a PTC of a motion domain control unit is implemented in an electronic control unit as a PTC application, and an OS program is installed as one of application software in the electronic control unit; Fig. 3 is a diagram showing an example of a list of services provided by the OS program; Fig. 4 is a flowchart showing specific processing content of a first OS program in a master ECU; Fig. 5 is a flowchart showing specific processing content of a second OS program in a slave ECU; Fig. 6 is a diagram illustrating an example in which a role of the first OS program in the master ECU is reduced and a role of the second OS program in the slave ECU is increased; Fig. 7 is a diagram illustrating an example in which the role of the first OS program in the master ECU is increased and the role of the second OS program in the slave ECU is reduced; Fig. 8 is a diagram illustrating several examples in which the first OS program in the master ECU determines that a change in the transmission information to the second OS program is required; and Fig. 9 is a diagram illustrating several examples in which the first OS program in the master ECU receives a request for a change of an operating condition from the second OS program in the slave ECU. DETAILED DESCRIPTION

[0016] Hereinafter, a vehicle control system according to an embodiment will be described with reference to the accompanying drawings. For example, as shown in Fig. As shown in Figure 1, a vehicle control system 1 according to the present embodiment is applied to a hybrid vehicle having an internal combustion engine 31 and an electric motor (motor generator) 33 as traction drive sources, and used to control a plurality of vehicle-mounted devices 31 to 35 mounted in the hybrid vehicle. However, the vehicle control system 1 according to the present embodiment is not limited to controlling the vehicle-mounted devices 31 to 35 in the hybrid vehicle and can be applied to controlling various types of vehicle-mounted devices in a normal vehicle having only an internal combustion engine as a traction drive source or in an electric vehicle having only an electric motor as a traction drive source.

[0017] Fig. Fig. 1 is a functional block diagram illustrating an example of various functions provided in the vehicle control system 1 for controlling the plurality of vehicle-mounted devices 31 to 35 in the hybrid vehicle described above. It is noted that Fig. 1 does not show all of the functions provided in the vehicle control system 1. Fig. 1 shows only one example of a configuration of the vehicle control system 1 according to the present embodiment for illustrative purposes.

[0018] Referring to Fig. 1, the vehicle control system 1 has functions for controlling the internal combustion engine 31, a transmission (TM) 32, a motor generator (MG) 33, a brake device 34, and a steering device 35, which are the vehicle-mounted devices. However, as described above, the vehicle control system 1 may further have functions for controlling other vehicle-mounted devices such as wheel suspensions, a high-voltage battery, and an air conditioning device.

[0019] As in Fig. 1, the vehicle control system 1 is configured such that functions for controlling the various vehicle-mounted devices 31 to 35 are divided in advance into a plurality of logic blocks (function blocks / functional blocks) 12 to 16 and 22 to 26, and a connection relationship is defined between these plurality of logic blocks 12 to 16 and 22 to 26. In other words, the logical structure for controlling the various vehicle-mounted devices 31 to 35 in the vehicle control system 1 is defined by the logic blocks 12 to 16 and 22 to 26 and the connection relationship between these logic blocks 12 to 16 and 22 to 26. The vehicle control system 1 controls the various vehicle-mounted devices 31 to 35 while the plurality of logic blocks 12 to 16 and 22 to 26 operate in cooperation with each other according to the defined connection relationship.

[0020] However, although not in Fig. As shown in Figure 1, each of the logic blocks 12 to 16 and 22 to 26 includes at least one, typically multiple, control blocks. Each of the logic blocks 12 to 16 and 22 to 26 appropriately combines arithmetic processing into these multiple control blocks to perform the respective functions (roles).

[0021] For example, an engine control unit 24 acting as the logic block includes a control block that receives sensor signals from various sensors and converts the sensor signals into signals compatible with a logic block for detecting an operating state of the engine 31. Furthermore, the engine control unit 24 includes a control block for calculating a currently generated torque from the operating state of the engine 31 detected by the sensor signals. Furthermore, the engine control unit 24 includes a control block for calculating a target engine operating state to eliminate a difference between a command torque commanded by a higher-hierarchy logic block (powertrain coordinator (PTC) 22) and the currently generated torque, if such a difference exists.In addition, the engine control unit 24 includes a control block for calculating a throttle opening, a fuel injection amount, a fuel injection timing, and an ignition timing to achieve a target engine operating state. However, these control blocks are examples, and the engine control unit 24 may include a control block for performing other processing required to perform a function of the engine control unit 24. The control blocks in the engine control unit 24, including the illustrated control block, may be appropriately combined with each other and divided inversely.

[0022] The vehicle control system 1 is embodied by distributively implementing the respective logic blocks 12 to 16 and 22 to 26 in the plurality of electronic control units as control applications such as programs or databases. In this case, the plurality of electronic control units are connected to each other through individual communication lines, or the respective electronic control units are connected to a common network so that electronic control units that satisfy the connection relationship can communicate with each other to maintain the connection relationship of the logic blocks 12 to 16 and 22 to 26. Note that the respective logic blocks 12 to 16 and 22 to 26 do not always need to be implemented in the individual, different electronic control units, and some logic blocks may be implemented commonly in the electronic control units.

[0023] The vehicle control system 1 according to the present embodiment is preliminarily divided into a plurality of domains according to the functions of the plurality of vehicle-mounted devices 31 to 35. In other words, the vehicle control system 1 is preliminarily divided into a plurality of domains 10 and 20 according to a group of functions to be performed by the logic blocks 12 to 16 and 22 to 26, respectively.

[0024] The plurality of vehicle-mounted devices 31 to 35 are assigned to any one of the domains 10 and 20. Domain control units 11 and 21 belonging to the assigned domains 10 and 20 calculate control target values ​​of the respective vehicle-mounted devices 31 to 35 and output the calculated control target values ​​to vehicle-mounted device control units 15, 16, and 24 to 26 (vehicle-mounted device control units) that control the vehicle-mounted devices 31 to 35. As shown in Fig. 1, each of the domain control units 11 and 21 comprises at least one logic block.

[0025] In particular, Fig. 1, the control system 1 is divided into a motion domain 10 and a power domain 20. The motion domain 10 is equipped with a motion domain control unit 11, which performs a function of controlling the behavior of the vehicle in a front-rear direction and a lateral direction. Likewise, the power domain 20 is equipped with a power domain control unit 21, which performs a function of controlling the power of the vehicle to accelerate or decelerate the vehicle or to maintain it at a constant speed.

[0026] In the vehicle control system 1 according to the present embodiment, as shown in Fig. 1, the vehicle-mounted device control units 15, 16, and 24 to 26, which control the operating states of the vehicle-mounted devices 31 to 35 in response to commands (control target values) from the domain control units 11 and 21, are arranged to belong to the domain control units 11 and 21. These vehicle-mounted device control units 15, 16, and 24 to 26 generate control signals for bringing the operating states of the respective vehicle-mounted devices 31 to 35 closer to the control target values ​​from the domain control units 11 and 21, and output the generated control signals to the vehicle-mounted devices 31 to 35.

[0027] In particular, Fig. 1, a brake control unit 15 for controlling the brake device 34 and a steering control unit 16 for controlling the steering device 35 are arranged to belong to the motion domain control unit 11. Also arranged are the engine control unit 24 for controlling the engine 31, a transmission (TM) control unit 25 for controlling the transmission 32, and an MG control unit 26 for controlling the motor generator 33, belonging to the energy domain control unit 21.

[0028] The motor generator 33 generates regenerative energy during vehicle deceleration. A motor generator coordinator (MGC) 23, which is a logic block of a higher hierarchy than the MG control unit 26, also manages the generation of regenerative energy. The energy is subjected to DC conversion by an inverter and accumulated in the high-voltage battery (not shown).

[0029] Now, various functions provided in the vehicle control system 1, which are in Fig. 1 as the logic blocks 12 to 16 and 22 to 26, will be described in detail.

[0030] The vehicle control system 1 receives a variety of information required for the respective logic blocks 12 to 16 and 22 to 26 to perform the assigned functions. For example, the operation of various operation units (accelerator pedal, brake pedal, gear lever, steering wheel, etc.) operated by a driver to drive the hybrid vehicle is detected by various sensors (not shown), and detected operation detection signals are input to the vehicle control system 1. In addition, operation detection signals from sensors for detecting driving conditions (e.g., speed, acceleration, yaw rate, etc.) of the vehicle and operating conditions (e.g., engine temperature, engine speed, transmission gear ratio, inverter temperature, motor speed, brake pressure, steering angle, etc.) are input.) of the various vehicle-mounted devices 31 to 35 are input into the vehicle control system 1.

[0031] The above-described various signals are provided to the respective domain control units 11 and 21 and the control units 15, 16 and 24 to 26 of the vehicle-mounted devices in the vehicle control system 1.

[0032] For example, the motion domain control unit 11 receives the operation detection signals indicative of the driver's operation of the various operating units and the operation detection signals from the sensors for detecting the vehicle's driving conditions. The motion domain control unit 11 calculates the control target values ​​of the braking device 34 and the steering device 35 so that the vehicle behaves according to the driver's operation of the operating unit. Specifically, a vehicle behavior control unit 12 provides a target acceleration (target deceleration / target deceleration) in the front-rear direction to a front-rear behavior control unit 13 and provides the target acceleration in the lateral direction to a lateral behavior control unit 14 to control the vehicle's behavior to correspond to the driver's operation while stabilizing the vehicle's behavior.To achieve the provided target acceleration (deceleration) in the front-rear direction, the front-rear behavior control unit 13 outputs a target drive torque (acceleration torque or braking torque) to the powertrain coordinator (PTC) 22 of the energy domain control unit 21 and outputs a target braking torque, which is the control target value of the brake device 34, to the brake control unit 15. Furthermore, the lateral behavior control unit 14 outputs a target assist torque, which is the control target value of the steering device 35, to the steering control unit 16 to achieve the provided target acceleration in the lateral direction.

[0033] Information about the vehicle's external environment, such as detection information about lane lines defining a vehicle's travel lane, and information about a preceding vehicle or an obstacle, can be provided to the motion domain control unit 11. With the above configuration, the motion domain control unit 11 can calculate control target values ​​to adjust an assist force of the steering device 35 (lane keeping assist), for example, so as not to deviate from the travel lane defined by the lane lines. Furthermore, the motion domain control unit 11 can calculate control target values ​​of the braking device 34 and the steering device 35, for example, to avoid a collision with a preceding vehicle or the obstacle.

[0034] The energy domain control unit 21 receives, for example, a sensor signal for detecting a voltage or current of the high-voltage battery (not shown) or a sensor signal indicative of the driving state of the vehicle. The MGC 23 of the energy domain control unit 21 calculates a state of charge of the high-voltage battery based on these sensor signals. Furthermore, the MGC 23 primarily calculates a maximum MG torque that can be generated by the motor generator 33 based on the state of charge of the high-voltage battery and provides the calculated maximum MG torque to the PTC 22.To most efficiently realize the target drive torque (acceleration torque) provided by the motion domain control unit 11, the PTC 22 calculates a target engine torque to be generated by the engine 31, a target transmission gear ratio to be realized by the transmission 32, and a target MG torque to be generated by the motor generator 33, taking into account the maximum MG torque that can be generated by the motor generator 33 and the driving state of the vehicle, based on the sensor signals. The thus calculated target engine torque, the target transmission gear ratio, and the target MG torque are provided as control target values ​​to the engine control unit 24, the transmission (TM) control unit 25, and the MGC 23, respectively.The control target values ​​related to a clutch operation (clutch connection start time, time until a clutch engagement is completed, etc.) can also be provided to the TM control unit 25.

[0035] Furthermore, the MGC 23 of the energy domain control unit 21 mainly calculates the regenerative electrical energy that can be generated by the motor generator 33 based on the state of charge of the high-voltage battery during vehicle deceleration or the like. Information about a regenerative braking torque corresponding to the regenerative electrical energy is provided from the MGC 23 to the front-rear behavior control unit 13 of the motion domain control unit 11 through the PTC 22.

[0036] When the target deceleration is received from the vehicle behavior control unit 12, the front-rear behavior control unit 13 calculates the target braking torque to achieve the target deceleration. If the motor generator 33 can generate the regenerative braking torque, the front-rear behavior control unit 13 determines the target braking torque from the brake device 34 and a regenerative target braking torque from the regenerative brake to utilize as much regenerative braking torque as possible. The regenerative target braking torque is provided to the MGC 23 of the energy domain control unit 21 through the PTC 22 as the control target value.

[0037] The brake control unit 15 controls the brake device 34 according to the target braking torque, which is the control target value of the brake device 34, provided by the front-rear behavior control unit 13. Specifically, the brake control unit 15 outputs the control signal for controlling a brake fluid pressure so that the brake device 34 generates the target braking torque. Similarly, the steering control unit 16 outputs the control signal so that the steering device 35 generates the target assist torque provided by the lateral behavior control unit 14, and controls the assist torque in the steering device 35.

[0038] The engine control unit 24 outputs the control signal to the engine 31 to achieve the target engine torque provided by the PTC 22. Specifically, the engine control unit 24 receives sensor signals from various sensors (rotational speed, temperature, air flow rate, etc.) that detect the operating state of the engine 31. The engine control unit 24 calculates the currently generated torque from the operating state of the engine detected by the sensor signals.The engine control unit 24 calculates an engine operating condition to bring the currently generated torque closer to the target engine torque, obtains a fuel injection amount, a fuel injection timing, and an ignition timing to achieve the calculated engine operating condition, and outputs an injection control signal and an ignition control signal corresponding to these calculated results to the engine 31.

[0039] Similarly, the TM control unit 25 receives the target gear ratio from the PTC 22 and outputs the control signal for realizing the provided target gear ratio to the transmission 32. Additionally, when the gear ratio in the transmission 32 is changed, the TM control unit 25 outputs the control signal for controlling the operation of the clutch according to a control target value associated with the operation of the clutch.

[0040] When the target MG torque is received from the MGC 23, the MG control unit 26 outputs the control signal to the inverter of the motor generator 33 to generate the target MG torque. When the target regenerative braking torque is received from the MGC 23, the MG control unit 26 outputs the control signal to the inverter of the motor generator 33, so that the motor generator 33 provides a braking force corresponding to the target regenerative braking torque to an axle.

[0041] As described in FIG. 12, the respective logic blocks 12 to 16 and 22 to 26 constituting the vehicle control system 1 perform the joint control processing effected jointly by the plurality of logic blocks 12 to 16 and 22 to 26, thereby controlling the respective vehicle-mounted devices 31 to 35. For example, the PTC 22 performs inter-domain joint control effected jointly with the front-rear behavior control unit 13 in the motion domain 10, and intra-domain joint control effected jointly with the MGC 23, the engine control unit 24, and the TM control unit 25.

[0042] In the vehicle control system 1 described above, it is possible to strictly specify processing steps and signals exchanged between the electronic control units implemented with the respective logic blocks 12 to 16 and 22 to 26, and accordingly generate the shared processing application programs corresponding to the specified signals and processing steps. However, in this case, the vehicle control system 1 results in a so-called dedicated product, making it difficult to be compatible with variations from a low function to a high function corresponding to, for example, a vehicle grade or vehicle model, or to be compatible with a change in hardware of the electronic control unit.

[0043] In view of this, when the plurality of electronic control units implemented with the logic blocks 12 to 16 and 22 to 26 perform the collaborative processing, it is conceivable that OS programs serving as basic software to collaboratively execute the collaborative processing application programs are installed in the respective electronic control units in addition to the collaborative processing application programs.

[0044] For example, if the OS program supports the verification of communication data between the respective electronic control units, data conversion, a synchronization mechanism, and resource allocation, etc., it becomes possible to create shared processing application programs in the respective electronic control units so that they are specialized in the respective control functions, and it becomes easy to handle the addition, modification, and the like of the control functions. Furthermore, since the respective OS programs can abstract the hardware of the respective electronic control units, the deployment flexibility of the shared processing application can be increased from this perspective.

[0045] However, if OS programs that support collaborative processing are installed in the respective electronic control units, these OS programs must work in cooperation with each other with a given role allocation. In this regard, if the role allocation is always fixed, the roles are not always properly proportionate to the capabilities of the respective electronic control units, for example, due to a difference in capabilities between the electronic control units to be used, and collaborative processing cannot be supported efficiently.

[0046] Under the circumstances, the vehicle control system 1 according to the present embodiment is configured so that the roles of the OS programs that support collaborative processing by the respective electronic control units are changeable. Specifically, when it is assumed that, among at least two electronic control units that perform collaborative processing, one electronic control unit is a master ECU and the other electronic control unit is a slave ECU, the first OS program installed in the master ECU acquires information about the role assigned to the second OS program installed in the slave ECU. The first OS program determines the role to be assigned to the first OS program based on the information indicating the role assigned to the second OS program, so that the first OS program can operate in cooperation with the second OS program.Therefore, even if the role allocation to the second OS program changes / varies due to the capabilities of the slave ECU, the role to be allocated can be automatically changed, allowing the first OS program to work in cooperation with the second OS program according to the variation in the role allocation. As a result, the respective OS programs installed in the master ECU and the slave ECU can efficiently support the joint processing of the master ECU and the slave ECU.

[0047] First, with reference to Fig. 2, an example of a configuration in which the OS programs are installed in the respective electronic control units will be described, and a specific example such as processing content to be implemented for the OS programs to support the collaborative processing will be described.

[0048] As in Fig. 2, the PTC 22 of the energy domain control unit 21 is implemented in an electronic control unit 40 as a PTC application 41a, and an OS program 41b is installed as an application in the electronic control unit 40. Fig. 2 illustrates a configuration of electronic control units 50, 60, 70, and 80 implementing applications 51a, 61a, 71a, and 81a, which function as logic blocks (front-rear behavior control unit 13, MGC 23, engine control unit 24, TM control unit 25) that directly communicate with the PTC 22 and respectively execute joint processing. Respective OS programs 51b, 61b, 71b, and 81b are installed in these electronic control units 50, 60, 70, and 80 as one of the applications.

[0049] The PTC application 41a, a front-rear behavior control application 51a, an MGC application 61a, a TM control application 71a, and an EMS control application 81a correspond to the respective community processing applications.

[0050] In the presentation of Fig. 2, the electronic control units 40, 50, 60, 70, and 80 are equipped with the OS programs 41b, 51b, 61b, 71b, and 81b, respectively. However, each of the electronic control units 40, 50, 60, 70, and 80 has a different OS program for each of the communication partners. This is because the service content to be provided to support collaborative processing differs when the communication partner is different.For example, the electronic control unit 40 in which the PTC application 41a is implemented includes: an OS program for supporting collaborative processing with the electronic control unit 50 serving as the front-rear behavior control unit 13, which is a higher-hierarchy domain control unit at a higher level; an OS program for supporting collaborative processing with the electronic control unit 60 serving as the MGC 23 belonging to the same power domain control unit 21; an OS program for supporting collaborative processing with the electronic control unit 70 serving as the TM control unit 25, which is a subordinate device control unit; and an OS program for supporting collaborative processing with the electronic control unit 80 serving as the engine control unit 24.

[0051] Alternatively, the electronic control unit 40 serving as the PTC 22 may share the OS programs for supporting collaborative processing with the electronic control unit 70 and the electronic control unit 80, in which the TM control unit 25 and the internal combustion engine control unit 24, respectively, classified as device control units, are implemented. In this case, even if there are differences in the role and operating condition of the OS programs between the electronic control unit 70 and the electronic control unit 80, the OS program of the electronic control unit 40 may be configured to provide data and services that cover such differences, thereby enabling the OS program to be shared.

[0052] In principle, an electronic control unit of a higher hierarchy (higher-hierarchy electronic control unit) acts as the master ECU, and an electronic control unit of a lower hierarchy (lower-hierarchy electronic control unit) acts as the slave ECU. For electronic control units in the same hierarchy, one electronic control unit acts as the master ECU, and the other electronic control unit acts as the slave ECU.

[0053] The electronic control units 40 to 80 each have a memory which stores the software which Fig. 2 shown structure. As shown in Fig. As shown in Figure 2, each of the electronic control units 40 to 80 has a software structure that conforms to a so-called AUTOSAR (automotive open system architecture). Therefore, the software structure of the respective electronic control units 40 to 80 will be described with reference to the electronic control unit 40 in which the PTC application 41a is implemented as a typical example.

[0054] As in Fig. As shown in Figure 2, in the electronic control unit 40, software is installed in a microcontroller 47, which is hardware. The software is roughly classified into basic software 43 to 46, a runtime environment (RTE) 42, and application software included in an application layer. Of the application software, the PTC application 41a is implemented in the application layer, and the PTC application 41a is executed, whereby the electronic control unit 40 functions as the PTC 42. In fact, the PTC application 41a is divided into several sub-applications on a function-by-function basis (functional basis) of the various functions of the PTC 42. The OS program 41b is implemented in the application layer as application software.

[0055] The basic software 43 to 46 is hierarchically organized into a microcontroller abstraction layer 43, an ECU abstraction layer 44, and a service layer 45. As the hierarchy increases, the degree of abstraction increases and the independence from a specific hardware type increases. The basic software 43 to 46 includes a composite driver 46.

[0056] The microcontroller abstraction layer 43 is positioned at the lowest layer of the base software 43 to 46 and includes a microcontroller driver, a memory driver, a communication driver, an I / O driver, etc. The microcontroller abstraction layer 43 depends on the hardware configuration of the microcontroller 47. However, because the microcontroller 47 and peripheral devices of the microcontroller 47 are abstracted by the microcontroller abstraction layer 43, layers higher than the microcontroller abstraction layer 43 are independent of the microcontroller 47 and the peripheral devices. The microcontroller abstraction layer 43 has several types of communication drivers (e.g., a CAN (registered trademark) driver, a LIN driver, a FlexRay (registered trademark) driver, etc.).The electronic control unit 40 carries out communications by means of different communication drivers, i.e. different communication networks, for example depending on whether the electronic control unit of the communication partner is located within the domain or outside the domain.

[0057] The ECU abstraction layer 44 is a higher layer than the microcontroller abstraction layer 43. The ECU abstraction layer 44 abstracts basic components of the electronic control unit 40 to make a higher software layer independent of the hardware of the electronic control unit 40. The ECU abstraction layer 44 includes a mounted device abstraction, a memory hardware abstraction, a communication hardware abstraction, an I / O hardware abstraction, etc.

[0058] Service layer 45 is partially higher in the hierarchy than ECU abstraction layer 44 and provides basic services for the application. Specifically, service layer 45 provides services such as an operating system, vehicle network communication and management, a storage service, a diagnostic service, and ECU health management. Most of service layer 45 is hardware-independent.

[0059] The complex driver 46 is used when a complex function is required. The complex function is a function not provided in the other layers and, for example, fulfills a special function or timing requirement for operating a complex sensor or actuator. The complex driver 46 is used, for example, when performing drive control of a fuel injector.

[0060] The RTE 42 is provided so that various applications 41a and 41b, which are higher in hierarchy than the basic software 43 to 46 constituting the above-mentioned respective layers and which are included in the application layer, do not depend on the electronic control unit 40. For this reason, the RTE 42 provides communication between the applications 41a and 41b and communication between the applications 41a, 41b and the basic software 43 to 46.

[0061] As described above, with the use of the AUTOSAR-compliant software structure, since the applications 41a and 41b do not depend on the hardware of the microcontroller 47 and the electronic control unit 40, the reusability of the applications 41a and 41b can be increased.

[0062] Next, the OS program 41b will be described in detail. As in Fig. 2, the OS program 41b is embodied as one of the application software. The OS program 41b provides a variety of services to support collaborative processing when the respective sub-applications of the PTC application 41a perform collaborative processing with the other electronic control units 50 to 80. In the Fig. In the example shown in Figure 2, assuming that the base software complies with the current AUTOSAR standard, the OS program that implements cooperation between the ECUs is embodied as the application software and is coupled to the base software via the RTE. However, the OS program can be incorporated into the base software instead of being embodied as the application software.

[0063] Fig. Figure 3 shows an example of a list of services provided by the OS program 41b. Meanwhile, in Fig. Three different services provided by the OS program 41b are classified into three hierarchies (hierarchical levels) of a DVFB (domain virtual function bus), a domain system OS, and a domain system abstraction. The OS program 41b can provide a portion of the Fig. 3. The services described in Fig. 3 are exemplary, and the OS program 41b may provide other services than those shown in Fig. 3 include the services shown.

[0064] For example, when data (control target data, sensor detection data, etc.) is transferred from the master ECU to the slave ECU for joint processing, a domain-external-internal abstraction service classified in the DVFB establishes a processing order in which the master ECU and the domain ECU execute the respective services of the OS programs and aligns the times at which the services are executed. A semantic gateway service (semantic interface service) classified in the DVFB translates data into corresponding data when data differs between a domain external and a domain internal.

[0065] For example, when the master ECU and the slave ECU are implemented in the same electronic control unit and share resources such as memory and a core, a resource arbitration service classified in a domain system OS allocates and sets the resources. A system mode service performs mode management to realize a control mode in which the control mode in the master ECU and the control mode in the slave ECU are coordinated. An event manager service, for example, generates and delivers an event that triggers the master ECU and the slave ECU to execute synchronized processing. A scheduler service determines a shared processing schedule in the slave ECU based on a shared processing schedule in the master ECU. A synchronized mechanism service synchronizes control at the event or time.A clock service generates a shared time in the master ECU and the slave ECU and timestamp data as required. A security service, for example, authenticates a correct communication partner based on ID data and confirms the normality of communication data through a parity check or similar. A diagnostic service, for example, performs abnormality diagnosis of the master ECU and the slave ECU and executes a fail-safe process as required. A safety function mechanism service stops a shared function between the master ECU and the slave ECU when an abnormality is severe.

[0066] A function distribution abstraction service classified into the domain system abstraction manages role assignment to the first OS program of the master and the second OS program of the slave in a sequence to realize the various services described above. In other words, in the present embodiment, the first OS program of the master and the second OS program of the slave cooperate with each other to thereby realize the various services described above. In this situation, in the present embodiment, the roles of the first OS program of the master and the second OS program of the slave are changeable. For this reason, there is a need to manage which role each of the first OS program of the master and the second OS program of the slave plays.An ownership abstraction service manages the allocation of control responsibilities with respect to the control target devices and the sensor devices between the first OS program of the master and the second OS program of the slave. In the above, the control responsibility refers to the role of outputting control signals to the control target devices, receiving detection signals from the sensor devices, and monitoring whether the control target devices or the sensor devices are operating normally.

[0067] Next, a setting procedure for enabling the first OS program of the master and the second OS program of the slave to work in cooperation with each other will be described with reference to flowcharts of Fig. 4 and Fig. 5. The setting (configuration) of the first OS program and the second OS program is implemented at a stage where the vehicle control system is constructed / structured on a vehicle production line. Furthermore, the setting of the first OS program and the second OS program is also implemented when the application software of the master ECU and the slave ECU is updated to improve function.

[0068] The flowchart of Fig. 4 represents a process to be executed by the first OS program of the master, and the flowchart of Fig. 5 represents a process to be executed by the second OS program of the slave.

[0069] First, in step S100 of the flowchart in Fig. 4. Role information about the role assigned to the second OS program installed in the slave ECU is acquired from the slave ECU. As the role information, the master ECU may acquire corresponding information indicating the role assigned to the second OS program of the slave ECU for the various services described above. Alternatively, the second OS program may possess role pattern information that clearly indicates the combination / composition of the roles of the second OS program for the various services in advance, and the master ECU may acquire the role pattern information.

[0070] As described above, the second OS program installed in the slave ECU has an assigned role selected from the several different role patterns for the various services described above. Therefore, the role of the second OS program can be appropriately configured depending on the configuration of the vehicle control system, the capabilities of the slave ECU, etc.

[0071] In the subsequent step S110, it is determined whether the acquired role of the second OS program for the various services is consistent with the current role of the first OS program in the master ECU. In this regard, the first OS program of the master ECU is preset to be consistent with the role of the average second OS program. In step S110, it is determined whether the default role of the first OS program is consistent with the role of the second OS program. With the above configuration, a change amount of the first OS program can be suppressed in the subsequent step S120. Alternatively, the first OS program may be preset in the above manner, but the first OS program may be set so that the first OS program becomes consistent with the acquired second OS program for all the service items. In this case, the process in step S110 can be omitted.

[0072] In step S120, the role of the first OS program is changed so that the role of the first OS program becomes consistent with the role of the second OS program for the various services. In the above, the role of the first OS program can be changed only for the service elements for which the role of the first OS program is inconsistent with the role of the second OS program, and accordingly, a process of changing the first OS program can be easily performed.

[0073] Now, two typical examples will be given of how the roles of the first OS program and the second OS program are changed for the respective service elements.

[0074] Fig. 6 illustrates an example in which the role of the first OS program in the master ECU is reduced and the role of the second OS program in the slave ECU is increased.

[0075] In this case, in the domain-external-internal abstraction service, the first OS program of the master ECU does not involve setting the processing order and processing time of the respective services from the second OS program of the slave ECU, and the second OS program of the slave ECU performs the setting of the processing order and processing time of the services from the second OS program. Furthermore, in the semantic gateway service, the semantic translation of data transmitted from the master ECU is performed in the second OS program.

[0076] In the resource brokering service, since the shared processing is preferentially executed in the master ECU, the first OS program performs a process of committing resources for shared processing, and the setting of usage of the remaining resources is performed in the second OS program. In the system mode service, the first OS program generates a shared processing mode, and the second OS program receives the shared processing mode, converts the received shared processing mode into a corresponding local mode, and sets the control mode of the slave ECU to the converted local mode.

[0077] In the event manager service, the first OS program generates a shared event used for shared processing and delivers the generated shared event to the slave ECU. The second OS program converts the delivered shared event into a local event that can be handled in the slave ECU. In the scheduler service, the first OS program generates the shared processing schedule, and the second OS program converts the shared processing schedule into the local schedule in the slave ECU. In the synchronization mechanism service, when the first OS program selects a synchronization instruction by a predetermined event as the synchronization means, the second OS program selects an implementation function for implementing synchronization by the predetermined event.For example, when the event manager service generates the local event, the second OS program selects the generated local event as the synchronization means.

[0078] In the clock service, the first OS program generates a shared time, and the second OS program converts the shared time into a local time in the slave ECU. In the security service, the first OS program performs authentication of the communication partner of the master ECU and confirmation of the normality of the received data, and the second OS program performs authentication of the communication partner of the slave ECU and confirmation of the normality of the received data. In the diagnostic service, the first OS program performs abnormality detection of the shared processing in the master ECU and the fail-safe process during an abnormality, and the second OS program performs abnormality detection of the shared processing in the slave ECU and the fail-safe process during the abnormality.In the safety function mechanism service, the first OS program controls the stop of a shared function in the master ECU, and the second OS program controls the stop of a local function in the slave ECU.

[0079] In the function allocation abstraction service, the first OS program of the master ECU does not include the management of function allocation between the master and the slave, and the second OS program of the slave ECU manages the function allocation. Similarly, in the owner abstraction service, the first OS program of the master ECU does not include responsibility allocation management, and the second OS program of the slave ECU manages the responsibility allocation.

[0080] Fig. 7 illustrates an example in which the role of the first OS program in the master ECU is increased and the role of the second OS program in the slave ECU is reduced.

[0081] In this case, in the domain external-internal abstraction service, the first OS program of the master ECU sets the processing order and processing time of the respective services of the second OS program of the slave ECU and transmits data indicative of the setting contents. The second OS program of the slave ECU receives the data indicative of the setting contents and executes the various services according to the received data. In the semantic gateway service, the first OS program of the master ECU performs semantic translation of the data and transmits the translated data to the slave ECU. The second OS program of the slave ECU receives the translated data and uses the data for processing.

[0082] In the resource brokering service, the first OS program performs a process of securing the resource for shared processing to the master ECU and an allocation process of the remaining resources. The second OS program performs resource management to utilize the allocated resource. In the system mode service, the first OS program generates the shared processing mode, converts its shared event into a corresponding local mode, and transmits the local mode to the slave ECU. The second OS program receives the converted local mode and sets the control mode of the slave ECU to the received local mode.

[0083] In the event manager service, the first OS program generates the shared event used for shared processing and converts the shared event into a local event manageable in the slave ECU. The second OS program receives the local event and performs processing based on the local event. In the scheduler service, the first OS program generates a shared processing schedule, converts the shared processing schedule into a local schedule in the slave ECU, and transmits the converted local schedule. The second OS program receives the local schedule and performs schedule management based on the local schedule. In the synchronized mechanism service, the first OS program selects local synchronization means corresponding to synchronization means in the shared processing and transmits the selected local synchronization means.The second OS program receives the local synchronization resources and uses the received local synchronization resources for subsequent processes.

[0084] In the clock service, the first OS program generates a shared time and further converts the shared time to the local time in the slave ECU and transmits the converted local time. The second OS program receives the local time and uses the local time for processing. In the safety service, the first OS program collectively manages the master ECU and the slave ECU. For example, the first OS program authenticates the communication partner of the master ECU and the slave ECU and confirms the normality of the data transmitted and received between the master and the slave. In this case, the second OS program does not handle the safety service. In the diagnostic service, the first OS program performs abnormality detection of the shared processing in the master ECU and the fail-safe process during an abnormality, and notifies the slave ECU of the abnormality detection result.The second OS program receives the abnormality detection notification. In the safety function mechanism service, the first OS program controls the stop of the shared function in the master ECU and instructs the second OS program to stop the local function as needed. The second OS program stops the local function in the slave ECU according to a local function stop instruction from the first OS program.

[0085] In the function allocation abstraction service, the first OS program of the master ECU manages the function allocation between the master and the slave, while the second OS program of the slave ECU does not include function allocation management. Similarly, in the owner abstraction service, the first OS program of the master ECU performs responsibility allocation management, while the second OS program of the slave ECU does not include responsibility allocation management.

[0086] The role assignment examples of the first OS program and the second OS program have been described above. Apart from the two examples described above, there are different role assignments because the role assignment for each of the services can be changed due to various factors, such as a difference between a processing response of the shared processing in the master ECU and a processing response in the local process in the slave ECU, and the capabilities of the master ECU and the slave ECU.

[0087] The description returns to the flowchart of Fig. 4. Through the processing up to step S120, the first OS program is set so that the first OS program and the second OS program can support collaborative processing in cooperation with each other. However, in some cases, the processing associated between the first OS program and the second OS program can be smoothly performed by performing fine adjustment such as changing the type of information transmitted from the master to the slave or correcting an operating condition of the master.

[0088] For this reason, in step S130 of the flowchart in Fig. 4 determines whether or not it is necessary to change the information to be transmitted to the second OS program. If it is determined that the change in the transmission information is necessary, a change in the transmission information is notified to the second OS program in step S140. Further, in step S150, the change in the transmission information corresponding to the notification content in step S140 is reflected in the first OS program.

[0089] Some examples in which the first OS program of the master ECU determines that the change in the transmission information to the second OS program is necessary will be described with reference to Fig. 8 are described.

[0090] As in Fig. As shown in Figure 8, target services that are likely to be required to change the transmission information conceivably include several services such as a system mode service, an event manager service, a scheduler service, and a security function mechanism service.

[0091] For example, in the system mode service, if the slave ECU is changed due to a version update of the application software in the slave ECU, the local mode associated with the shared processing mode of the master ECU can be changed. In this case, a purpose (startup, normal control, stop, etc.) of the corresponding mode is transmitted from the first OS program of the master ECU instead of transmitting the local mode itself. As a result, the second OS program of the slave ECU can select an appropriate mode corresponding to the shared control mode.

[0092] Additionally, as with the system mode service, in the event manager service, when the slave ECU is changed, the local event corresponding to the shared event of the master ECU can be changed. Therefore, in this case, the purpose (interruption, regular period, abnormality detection, etc.) of the corresponding event is transmitted from the first OS program of the master ECU instead of transmitting the local event itself. As a result, the second OS program of the slave ECU can generate an appropriate local event corresponding to the shared event.

[0093] Additionally, as with the system mode service, in the scheduler service, when the slave ECU is changed, the local schedule corresponding to the shared schedule of the master ECU can be changed. Therefore, in this case, the purpose (post-process of XX, etc.) of the corresponding schedule is transferred from the first OS program of the master ECU instead of transferring the local schedule itself. As a result, the second OS program of the slave ECU can generate an appropriate local schedule corresponding to the shared schedule.

[0094] In addition, in the safety function mechanism service, if the master executes a slave stop instruction and the slave also has a function independent of the master, there is a possibility that a situation will be ignored by the slave when the stop instruction is provided by the master to the slave. Therefore, the first OS program of the master ECU transmits the stop instruction to the slave via its purpose (control termination, abnormal stop, etc.). As a result, the second OS program of the slave ECU can execute processing that corresponds to the stop purpose, taking into account the processing situation of the second OS program itself.

[0095] In step S160 of the flowchart in Fig. 4, it is determined whether or not a change request has been received from the second OS program of the slave ECU. If it is determined that the change request has been received, control proceeds to step S170, and the operating condition of the first OS program is corrected in response to the change request from the second OS program of the slave ECU.

[0096] Several examples in which the first OS program of the master ECU receives the change request for the operating condition from the second OS program of the slave ECU will be described with reference to Fig. 9 are described.

[0097] As in Fig. 9, target services that may require the change in the operating condition include several services such as the domain external-internal abstraction service, the resource mediation service, the synchronized mechanism service, the function distribution abstraction service, the owner abstraction service (ownership abstraction service), and the security function mechanism service.

[0098] Furthermore, if there are control target devices and sensor devices for which control responsibilities are assigned to the slave ECU, data for monitoring the abnormal state of the control target device and sensor device with respect to a safety-related requirement may be different from the data to be handled by the slave ECU. In such a case, in the resource brokering service, the slave requires the master to secure a storage area for all safety-related data used in the slave ECU, for example, in a shared memory. As a result, data handling can be easily performed in accordance with the safety-related requirement.

[0099] Furthermore, in the synchronized mechanism service, when the slave cannot select the realization function for realizing the synchronization, a condition for issuing the synchronization instruction can be designated / designated by the slave.

[0100] Furthermore, when multiple slaves exist, the master is capable of performing function allocation management and responsibility allocation management between the master and the slave. In such a situation, in the function distribution abstraction service and the owner abstraction service, the slave may require the master to perform function allocation management and responsibility allocation management.

[0101] In addition, when multiple slaves are present, there may be a situation where it is unknown which procedure is appropriate for performing stop processing in each slave. In this situation, with regard to the safety function service, the slave may require the master to provide a message about the local function stop processing procedure, a condition for the processing procedure, etc., to each slave.

[0102] As described above, the flowchart in Fig. 5 represents the process to be executed by the second OS program of the slave, and in step S200, the information about the role assigned to the second OS program installed in the slave ECU is provided to the master ECU.

[0103] In the subsequent step S210, it is determined whether or not the change request for the transmission information has been issued from the master ECU. If it is determined that the change request has been issued, control proceeds to step S220, and the information to be acquired by the second OS program is changed in response to the change request from the master ECU. Furthermore, a processing procedure for the changed information is determined in advance as needed.

[0104] In step S230, it is determined whether a change in the operating condition of the first OS program of the master ECU is necessary. If it is determined that the change in the operating condition is necessary, a change request for the operating condition of the first OS program is issued to the master ECU in step S240. Then, in step S250, the second program is corrected so that the requested change content of the operating condition of the first OS program is reflected in the second OS program.

[0105] The embodiment has been shown above, but the present embodiment may be modified in various ways.

[0106] For example, in the above-described embodiment, the multiple slave ECUs are provided for the master ECU. If it is difficult to adjust the processing time of the slave through the individual setting of the slave, the domain external-internal abstraction service of the slave requires the master to change a data notification timing. Alternatively, if the respective slave ECUs can communicate with each other, the processing times of the slaves can be coordinated through the communication of the respective second OS programs of the slave ECUs. For example, the processing procedure and processing time in the second OS program of one slave ECU are set to match those of the other slave ECUs based on the information about the processing procedure and processing time in the second OS programs of the other slave ECUs.In this way, when the respective slave ECUs cooperate with each other, the timing of the respective processing can also be easily performed.

Claims

[1] A vehicle control system comprising a first electronic control unit (40) and a second electronic control unit (60, 70, 80) which perform joint processing for controlling a vehicle-mounted device (31 to 33) mounted in a vehicle, wherein: the first electronic control unit is a master ECU and the second electronic control unit is a slave ECU; the first electronic control unit and the second electronic control unit each include collaborative processing application programs (41a, 61a, 71a, 81a) for performing collaborative processing; the first electronic control unit includes a first OS program (41b); the second electronic control unit includes a second OS program (61b, 71b, 81b); the first and second OS programs each support verification of communication data between the first and second electronic control units, conversion of the data, and a synchronization mechanism; the first OS program and the second OS program work in cooperation with each other under a predetermined role allocation and serve as basic software for the respective joint processing application programs to be executed in cooperation with each other; the second electronic control unit stores role pattern information uniquely indicating a combination of roles of the second OS program, and transmits the role pattern information to the first electronic control unit according to a configuration of the vehicle control system or the capability of the second electronic control unit; the second OS program installed in the second electronic control unit has an assigned role selected from different roles; the first OS program installed in the first electronic control unit is designed such that the role assigned to the first OS program is changeable, so that the first OS program can perform an operation cooperatively with the second OS program even if any of the different roles is assigned to the second OS program; and the first electronic control unit comprises an acquisition unit (S100) which acquires the role pattern information as information about the role assigned to the second OS program from the second electronic control unit, and a determination unit (S120) which, based on the information acquired by the acquisition unit and indicative of the role assigned to the second OS program, determines the role to be assigned to the first OS program so that the first OS program can work in cooperation with the second OS program. [2] A vehicle control system according to claim 1, wherein: a variety of elements for operating system roles are available; for the plurality of elements, the roles are assigned to the first OS program and the second OS program; the first electronic control unit comprises a change notification unit (S140) which notifies the second electronic control unit that there is a change in information transmitted from the first OS program regarding a specific element of the plurality of elements, and a change unit (S150) which, in accordance with a change instruction of the change notification unit, implements the changes in the information transmitted from the first OS program with respect to the specific element. [3] A vehicle control system according to claim 1, wherein: a variety of elements exist as roles of operating systems; for the plurality of elements, the roles are assigned to the first OS program and the second OS program; the second electronic control unit comprises a change instruction unit (S240) which requests the first electronic control unit to change an operating condition for a specific element of the plurality of elements; the first electronic control unit comprises an operating condition changing unit (S170) that changes the operating condition of the first OS program for the specific element in response to a change instruction from the change instruction unit. [4] A vehicle control system according to any one of claims 1 to 3, wherein: the vehicle control system is hierarchically organized into a plurality of device control units (24 to 26) for controlling a plurality of vehicle-mounted devices and a domain control unit (21 to 23) for supervisory control of the plurality of device control units; the domain control unit is implemented in the first electronic control unit; and the device control units are implemented in the second electronic control unit. [5] Vehicle control system according to one of claims 1 to 3, wherein the vehicle control system is hierarchically organized into a plurality of device control units (24 to 26) for controlling a plurality of vehicle-mounted devices and a domain control unit (21 to 23) for supervisory control of the plurality of device control units; at least two electronic control units form the domain control unit; and the first electronic control unit and the second electronic control unit are included in the at least two electronic control units constituting the domain control unit. [6] Vehicle control system according to one of claims 1 to 3, wherein the vehicle control system is hierarchically arranged in a plurality of device control units (24 to 26) for controlling a plurality of vehicle-mounted devices and a domain control unit (21 to 23) for supervisory control of the plurality of device control units, the vehicle control system further comprising: a high-hierarchy control unit (13) which is a higher hierarchy than the domain control unit and which instructs the domain control unit to perform control, where: the high-hierarchy control unit is implemented in the first electronic control unit; and the domain control unit is implemented in the second electronic control unit.

Citation Information

Patent Citations

  • In-vehicle electronic equipment control system

    JP2009056817A

  • Control device, control procedure and computer program

    DE112009001818T5

  • electronic system for a vehicle

    DE4111023A1