electronic control device

Abstract

An electronic control device (2) is mounted on a vehicle, and outputs an instruction to a device mounted on the vehicle on the basis of data received from outside the vehicle. The electronic control device has a base unit (11) and an extension unit (12-16) which are configured to be physically separable from each other. A first base-mounted function (37) as a first function of a first domain and a second base-mounted function (38) as a first function of a second domain are mounted on the base unit. At least one of a first extension-mounted function (55) as a second function of the first domain and a second extension-mounted function (65) as a second function of the second domain is mounted on the extension unit.

Description

[0001] Cross-references to related applications

[0002] This international application claims the benefit of Japanese Patent Application No. 2024-060201, filed with the Japanese Patent Office on April 3, 2024, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to electronic control devices mounted on vehicles. Background Technology

[0004] Patent document 1 describes how the functions or performance of a vehicle-mounted machine can be expanded by installing an expansion unit on the main body of the vehicle-mounted machine.

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent Document 1: International Publication No. 2023 / 276815

[0008] As a result of the inventor's detailed investigation, the following issues were discovered.

[0009] In developing a vehicle control system where multiple domain ECUs, each configured as a functional domain within a vehicle and controlling multiple ECUs residing within a domain, cooperate with each other, it is easy to improve performance for each domain because the physical architecture is built on a domain-by-domain basis. However, when developing new applications by combining functions between domains, adjustments between domain ECUs are required, reducing the efficiency of application development. Summary of the Invention

[0010] This disclosure improves the efficiency of developing applications used in vehicles.

[0011] One aspect of this disclosure is an electronic control device mounted on a vehicle and connected to the vehicle-mounted device in a manner capable of data communication with the vehicle-mounted device, and configured to output instructions to the vehicle-mounted device based on data received from outside the vehicle.

[0012] The electronic control device disclosed herein comprises a basic unit that is physically separable from each other and one or more extension units.

[0013] The basic unit includes one or more basic processors that serve as one or more processors mounted on the basic unit, and basic memory that serves as memory mounted on the basic unit.

[0014] One or more expansion units each have an expansion processor as a processor mounted on the expansion unit and an expansion memory as a memory mounted on the expansion unit.

[0015] The basic unit is equipped with a first basic equipped function as a first function of a first domain and a second basic equipped function as a first function of a second domain. The first domain is one of multiple domains divided according to the functions of the vehicle, and the second domain is one of multiple domains that is different from the first domain.

[0016] In one or more extension units, at least one of a first extension carrying function as a second function of a first domain and a second extension carrying function as a second function of a second domain is carried.

[0017] The electronic control device of this disclosure, configured in this way, can extend functionality for each domain by connecting an extension unit equipped with a first extension function or a second extension function to a base unit. Furthermore, in the electronic control device of this disclosure, since multiple functions divided by each domain are integrated into one electronic control device, adjustments between multiple electronic control devices are not required when developing new applications, thus improving application development efficiency. Attached Figure Description

[0018] Figure 1 This is a block diagram showing the configuration of the vehicle control system according to the first embodiment.

[0019] Figure 2 This is a block diagram illustrating the software structure of the basic unit and the expansion unit of the first embodiment.

[0020] Figure 3 This is a block diagram showing a machine connected to a vehicle control system.

[0021] Figure 4 This is a flowchart illustrating the basic monitoring process of the first embodiment.

[0022] Figure 5 This is a flowchart illustrating the first part of the extended monitoring process of the first embodiment.

[0023] Figure 6 This is a flowchart illustrating the second part of the extended monitoring process of the first embodiment.

[0024] Figure 7 This is a diagram illustrating the transition of the power mode of the integrated ECU.

[0025] Figure 8 This is a diagram showing how to start a vehicle.

[0026] Figure 9This is a block diagram illustrating the software structure of the basic unit of the second embodiment.

[0027] Figure 10 This is a block diagram illustrating the software structure of the basic unit of the third embodiment.

[0028] Figure 11 This is a block diagram showing the configuration of the vehicle control system according to the fourth embodiment.

[0029] Figure 12 This is a block diagram showing the configuration of the vehicle control system according to the fifth embodiment.

[0030] Figure 13 This is a block diagram illustrating the software structure of the base unit and extension unit in the sixth embodiment.

[0031] Figure 14 This is a block diagram illustrating the software structure of the basic unit and the extension unit in the seventh embodiment.

[0032] Figure 15 This is a flowchart illustrating the basic monitoring process of the eighth embodiment.

[0033] Figure 16 This is a flowchart illustrating the first part of the extended monitoring process in the eighth embodiment. Detailed Implementation

[0034] [First Implementation Method]

[0035] Hereinafter, the first embodiment of this disclosure will be described with reference to the accompanying drawings.

[0036] In this embodiment, the vehicle control system 1 is mounted on a vehicle, such as... Figure 1 As shown, it includes integrated ECU2, TCU3, and regional ECUs 4, 5, 6, and 7. ECU is short for Electronic Control Unit. TCU is short for Telematics Control Unit.

[0037] The unified ECU2 governs ECUs 4 to 7, enabling coordinated control of the vehicle as a whole.

[0038] The integrated ECU2 has a basic unit 11 and an expansion unit 12.

[0039] The basic unit 11 and the expansion unit 12 are housed in a box-shaped shell formed into a cuboid.

[0040] An opening is formed on one of the six faces constituting the housing. The base unit 11 and the expansion unit 12 can be individually and detachably housed within the housing by inserting them into the opening. By housing the base unit 11 and the expansion unit 12, they are connected in a manner capable of data communication with each other.

[0041] The basic unit 11 includes a basic SoC 21, an Ethernet switch 22, a PCIe switch 23, and a storage device 24. SoC stands for System on a chip. PCIe stands for Peripheral Component Interconnect Express. Ethernet is a registered trademark. PCIe is a registered trademark.

[0042] The basic SoC21 has a CPU31, ROM32 and RAM33.

[0043] The various functions of the basic SoC 21 are implemented by the CPU 31 executing programs stored in a non-transitory physical recording medium. In this example, the ROM 32 is equivalent to the non-transitory physical recording medium storing the program. Furthermore, the execution of this program executes the corresponding methods. In addition, some or all of the functions executed by the CPU 31 can also be constructed in hardware by one or more ICs.

[0044] Ethernet switch 22 is a network switch that has the function of relaying communication between multiple devices connected to Ethernet switch 22 in accordance with Ethernet standard.

[0045] PCIe switch 23 is a network switch capable of relaying communication between multiple devices connected to PCIe switch 23 in accordance with the PCIe standard.

[0046] Storage device 24 is a memory device used to store various types of data.

[0047] The expansion unit 12 includes expansion SoC 41 and expansion SoC 42. Expansion SoC 41 and expansion SoC 42 are mounted on the circuit board 48.

[0048] The extended SoC 41 includes a CPU 51, ROM 52, and RAM 53. The various functions of the extended SoC 41 are implemented by the CPU 51 executing programs stored on a non-transitory physical recording medium. In this example, the ROM 52 is equivalent to the non-transitory physical recording medium storing the program. Furthermore, the execution of this program executes the methods corresponding to the program. In addition, some or all of the functions executed by the CPU 51 can also be constructed in hardware by one or more ICs.

[0049] The extended SoC 42 includes a CPU 61, ROM 62, and RAM 63. The various functions of the extended SoC 42 are implemented by the CPU 61 executing programs stored on a non-transitory physical recording medium. In this example, the ROM 62 is equivalent to the non-transitory physical recording medium storing the program. Furthermore, the execution of this program executes the methods corresponding to the program. In addition, some or all of the functions executed by the CPU 61 can also be constructed in hardware by one or more ICs.

[0050] The TCU3 communicates wirelessly with external communication devices located outside the vehicle. The base SoC21 and TCU3 communicate with each other, for example, according to the Ethernet standard.

[0051] Zone ECUs 4 to 7 are set up for each zone into which the vehicle is divided, and mainly perform control of the ECUs located in that zone.

[0052] The basic SoC21 communicates with ECUs 4, 5, 6, and 7, which are connected to the communication bus, by sending and receiving communication frames based on the CAN communication protocol. CAN is short for Controller Area Network.

[0053] Ethernet switch 22 is connected to basic SoC 21, extended SoCs 41 and 42, and regional ECUs 4, 5, 6, and 7.

[0054] The PCIe switch 23 is connected to the base SoC 21, the expansion SoCs 41 and 42, and the storage device 24.

[0055] like Figure 2 As shown, the base SoC21 includes a CPU31 and hardware IP34. IP stands for Intellectual Property.

[0056] The base SoC 21 includes a virtual machine monitor 35. The virtual machine monitor 35 manages various functions mounted on the base unit 11 to be executed in parallel on the CPU 31. In this embodiment, the virtual machine monitor 35 manages infrastructure basic functions 36, ADAS basic functions 37, and cockpit basic functions 38. ADAS is short for Advanced Driver Assistance System.

[0057] Infrastructure basic functions include, for example, OTA control. OTA stands for Over The Air. OTA control, for example, enables automatic updates of in-vehicle applications.

[0058] ADAS basic functions include adaptive cruise control and lane keeping assist, among others.

[0059] Basic cockpit functions 38 include, for example, the display of basic vehicle information (e.g., vehicle speed, engine speed, and remaining fuel) via the instrument panel, and voice recognition in the driver's seat.

[0060] Hardware IP34 refers to hardware that performs specified processing, such as ISP processing of image data captured by a vehicle camera. ISP stands for Image Signal Processing.

[0061] The extended SoC41 incorporates a CPU51 and hardware IP54.

[0062] The CPU 51 is equipped with ADAS extension function 55. ADAS extension function 55 is, for example, a function for performing Level 3 autonomous driving.

[0063] The hardware IP54 is the hardware that performs specified processing, such as ISP processing of image data captured by a vehicle camera.

[0064] The extended SoC42 features a CPU61 and hardware IP64.

[0065] The CPU 61 is equipped with a cockpit extension function 65. The cockpit extension function 65 includes, for example, voice recognition for all seats in the vehicle.

[0066] Hardware IP64 refers to hardware that performs specified processing, such as ISP processing of image data captured by a vehicle camera.

[0067] like Figure 3 As shown, the regional ECU4 communicates with the powertrain ECU71, brake ECU72 and steering ECU73 connected to the communication bus by sending and receiving communication frames based on the CAN communication protocol.

[0068] The area ECU7 communicates with the smart key ECU74, which is connected to the communication bus, by sending and receiving communication frames based on the CAN communication protocol. The smart key ECU74 communicates wirelessly with the smart key carried by the driver of the vehicle, and unlocks the vehicle doors when it detects the driver approaching the vehicle, or locks the vehicle doors when it detects the driver leaving the vehicle.

[0069] The front camera 75 outputs image data generated by capturing images of the front of the vehicle to the base SoC 21.

[0070] The front side camera 76 outputs image data generated by capturing images from the side of the front of the vehicle to the extended SoC 41.

[0071] The base SoC 21 communicates with the data link connector 77, which is connected to the communication bus, by sending and receiving communication frames based on the CAN communication protocol. The data link connector 77 is also connected to the Ethernet switch 22.

[0072] In order to realize the functions mounted on the expansion unit 12, the expansion unit 12 sends various instructions to the base unit 11. Based on the various instructions from the expansion unit 12, the base unit 11 controls the ECUs 4 to 7.

[0073] However, in the event of an anomaly preventing data communication between the base unit 11 and the regional ECUs 4-7, the expansion unit 12, unable to control the regional ECUs 4-7 via the base unit 11, directly sends various commands to the regional ECUs 4-7 to control them. For example, the expansion SoC 41 controls the powertrain ECU 71, brake ECU 72, and steering ECU 73 connected to the regional ECU 4 by directly sending various commands to the regional ECU 4 to implement the ADAS expansion function 55 mounted on the expansion SoC 41.

[0074] Furthermore, the extended SoC 41 is configured to replace and execute the ADAS basic function 37 of the base unit 11 when the base unit 11's ADAS basic function 37 is stopped, and to send various instructions from the extended unit 12 to the base unit 11. The extended SoC 41 is also configured to replace and execute the infrastructure basic function 36 or the cockpit basic function 38 of the base unit 11 when the infrastructure basic function 36 or the cockpit basic function 38 is stopped.

[0075] Next, the steps of the basic monitoring process performed by the basic SoC 21 of the basic unit 11 will be described. The basic monitoring process is a process that begins immediately after the basic SoC 21 is started.

[0076] During basic monitoring processing, the CPU31 of the basic SoC21, such as... Figure 4 As shown, in S10, data communication is performed with the extension unit 12 to perform processing to detect anomalies occurring in the extension unit 12 (hereinafter referred to as extension anomaly detection processing).

[0077] In S20, CPU31 determines whether an anomaly has been detected in the expansion unit 12 based on the detection result of the expansion anomaly detection processing in S10. If no anomaly is detected in the expansion unit 12, CPU31 proceeds to S10. Conversely, if an anomaly is detected in the expansion unit 12, in S30, CPU31 notifies the vehicle driver to stop the function of the expansion unit 12. For example, CPU31 causes the instrument cluster display, CID (Center Information Display), or HUD (Head-Up Display) to indicate that the function of the expansion unit 12 has been stopped.

[0078] In S40, CPU31 notifies the vehicle's driver whether a reset of the expansion unit 12 can be performed. For example, CPU31 causes the instrument cluster display, CID, or HUD to display a reset permission confirmation image indicating whether a reset of the expansion unit 12 can be performed.

[0079] In S50, CPU31 determines whether the driver has authorized the reset of extension unit 12. Specifically, CPU31 determines whether the driver has authorized the reset based, for example, on the driver's operation of the control switch set on the CID or the steering wheel.

[0080] Here, if the driver does not authorize the reset of the expansion unit 12, CPU 31 proceeds to S40. On the other hand, if the driver authorizes the reset of the expansion unit 12, CPU 31 resets the expansion unit 12 in S60.

[0081] In S70, CPU31 determines whether the expansion unit 12 has been restored normally due to the reset in S60. If the expansion unit 12 has been restored normally, CPU31 proceeds to S100.

[0082] On the other hand, if the expansion unit 12 fails to recover normally, the CPU 31 determines in S80 whether the number of consecutive failures of the expansion unit 12 to recover normally (hereinafter referred to as the number of consecutive abnormal occurrences) is more than N. N is an integer greater than or equal to 1. Here, if the number of consecutive abnormal occurrences is less than N, the CPU 31 proceeds to S100. On the other hand, if the number of consecutive abnormal occurrences is more than N, the CPU 31 notifies the driver of the abnormality of the expansion unit 12 in S90 and proceeds to S110.

[0083] When the process moves to S100, CPU31 notifies the driver that the expansion unit 12 has been restored and then moves to S110.

[0084] When transitioning to S110, CPU31 determines whether vehicle control system 1 has become disconnected. Vehicle control system 1 transitions to disconnected state when the system is started and in the on state, for example, if a power switch located near the driver's seat is operated.

[0085] Here, if the vehicle control system 1 is not in a disconnected state, CPU 31 proceeds to S10. On the other hand, if the vehicle control system 1 is in a disconnected state, CPU 31 terminates the basic monitoring process.

[0086] Next, the steps of the extended monitoring process performed by the extended SoC41 of the extended unit 12 will be described. The extended monitoring process is a process that begins immediately after the extended SoC41 is started.

[0087] When performing extended monitoring processing, such as Figure 5 As shown, the CPU 51 of the extended SoC 41 performs processing in S210 to detect anomalies occurring in the base unit 11 by communicating data with the base unit 11 (hereinafter referred to as base anomaly detection processing).

[0088] In S220, CPU51 determines whether an anomaly has been detected in basic unit 11 based on the detection result of the basic anomaly detection process in S210. If no anomaly is detected in basic unit 11, CPU51 proceeds to S210.

[0089] On the other hand, if an anomaly is detected in the expansion unit 12, the CPU 51 determines in S230 whether the processing can be performed by the expansion unit 12 instead of the basic unit 11.

[0090] Here, if it cannot be replaced by the expansion unit 12, the CPU 51 moves to S320. On the other hand, if it can be replaced by the expansion unit 12, the CPU 51 determines in S240 whether it can be dealt with by resetting a part of the base unit 11 (hereinafter referred to as partial reset).

[0091] Here, if a partial reset is possible, CPU51 notifies the driver in S250 to perform a partial reset of the base unit 11.

[0092] In S260, CPU51 notifies the driver whether a partial reset of the base unit 11 can be performed.

[0093] In S270, CPU51 determines whether the driver has authorized a partial reset of the base unit 11.

[0094] Here, if the driver does not authorize a partial reset of the base unit 11, CPU 51 proceeds to S260. On the other hand, if the driver authorizes a partial reset of the base unit 11, CPU 51 partially resets the base unit 11 in S280.

[0095] In S290, CPU51 determines whether the base unit 11 has been restored normally due to the partial reset in S280. If the base unit 11 has been restored normally, CPU31 notifies the driver in S300 that the base unit 11 has been restored normally and then proceeds to S330.

[0096] On the other hand, if the basic unit 11 fails to recover normally, the CPU 51 determines in S310 whether the number of consecutive failures of the basic unit 11 to recover normally (hereinafter referred to as the abnormal consecutive count) is more than N. N is an integer greater than or equal to 1. Here, if the abnormal consecutive count is less than N, the CPU 51 proceeds to S280. On the other hand, if the abnormal consecutive count is more than N, the CPU 51 proceeds to S320.

[0097] When the transfer is initiated to S320, CPU51 notifies the driver of the abnormality in base unit 11 and then transfers to S330.

[0098] When the process transitions to S330, CPU 51 determines whether vehicle control system 1 has become disconnected. If vehicle control system 1 has not become disconnected, CPU 51 transitions to S210. Conversely, if vehicle control system 1 has become disconnected, CPU 51 terminates the extended monitoring process.

[0099] Additionally, in situations where a partial reset cannot be implemented in S240, such as... Figure 6 As shown, CPU51 notifies the driver in S340 that the vehicle needs to be stopped.

[0100] In S350, CPU51 determines whether the vehicle has stopped. Specifically, CPU51 determines that the vehicle has stopped, for example, when the vehicle is in park.

[0101] Here, if the vehicle is not stopped, CPU 51 proceeds to S340. On the other hand, if the vehicle has stopped, CPU 51, in S360, similarly to S260, notifies the driver whether a partial reset of the base unit 11 can be performed.

[0102] In S370, CPU51, similar to S270, determines whether the driver has authorized a partial reset of the base unit 11.

[0103] Here, if the driver does not authorize a partial reset of the base unit 11, the CPU 51 proceeds to S360. On the other hand, if the driver authorizes a partial reset of the base unit 11, the CPU 51 performs a partial reset of the base unit 11 in S380, similar to S280, and then proceeds to S290.

[0104] like Figure 7 As shown, the integrated ECU2, in power mode, has a power-off mode M1 and a power-on mode M2.

[0105] Power disconnection mode M1 is the power mode of the integrated ECU2 when the vehicle's IG power supply is disconnected (hereinafter referred to as IG disconnection). That is, power disconnection mode M1 is the power mode when the basic unit 11 and the expansion unit 12 are stopped.

[0106] Power-on mode M2 ​​is the power mode of the integrated ECU2 when the IG power is on (hereinafter referred to as IG on).

[0107] The power-on mode M2 ​​includes a first power-on mode M21, a second power-on mode M22, and a third power-on mode M23.

[0108] The first power-on mode M21 is the power mode when the basic unit 11 and the expansion unit 12 are started.

[0109] The second power-on mode M22 is the power mode when the basic unit 11 is in the powered-on state and the expansion unit 12 is in the powered-off state.

[0110] The third power-on mode M23 is the power mode when the basic unit 11 is in sleep mode and the expansion unit 12 is stopped. Sleep mode is an operating state in which available functions are limited and power consumption is low.

[0111] When switching from IG disconnect to IG on, the integrated ECU2, as shown by arrow L1, transitions from power disconnect mode M1 to power on mode M2.

[0112] When switching from IG on to IG off, the integrated ECU2, as shown by arrow L2, transitions from power on mode M2 ​​to power off mode M1.

[0113] When the first activation mode M21 is active, if the basic unit 11 determines that the extended function is not used, the integrated ECU2, as shown by arrow L3, migrates from the first activation mode M21 to the second activation mode M22.

[0114] When the second activation mode M22 is active, if the basic unit 11 determines that the extended function is to be used, the integrated ECU2, as shown by arrow L4, migrates from the second activation mode M22 to the first activation mode M21.

[0115] When the second activation mode M22 is active, if the basic unit 11 determines that the entire vehicle needs to be set to power saving mode, the integrated ECU2, as shown by arrow L5, migrates from the second activation mode M22 to the third activation mode M23.

[0116] When in the third activation mode M23, if the basic unit 11 determines that only the basic unit 11 needs to be activated, the integrated ECU2, as shown by arrow L6, migrates from the third activation mode M23 to the second activation mode M22.

[0117] When the third activation mode M23 is active, if the basic unit 11 determines that the entire vehicle needs to be started, the integrated ECU2, as shown by arrow L7, migrates from the third activation mode M23 to the first activation mode M21.

[0118] When the first activation mode M21 is active, if the basic unit 11 determines that the entire vehicle needs to be changed to power saving mode, the integrated ECU2, as shown by arrow L8, migrates from the first activation mode M21 to the third activation mode M23.

[0119] When transitioning from power off mode M1 to power on mode M2, the choice between the first on mode M21, the second on mode M22, and the third on mode M23 is determined by the content of the trigger that transitions to power on mode M2.

[0120] like Figure 8 As shown, when driver D, who is approaching the vehicle, operates the smart key SK or similar device to unlock the vehicle door, the smart key SK sends a wireless signal WS. Upon receiving the wireless signal WS, the smart key ECU74, as indicated by arrow L11, sends a door unlock instruction to the base unit 11 of the integrated ECU2 via the regional ECU7.

[0121] Upon receiving the door unlock instruction, the base unit 11 changes its power mode and, if necessary, activates the expansion unit 12. Therefore, the base unit 11 activates before the expansion unit 12. Subsequently, the integrated ECU 2, having received the door unlock instruction, instructs the regional ECUs 4 to 7, which control door unlocking, to unlock the doors.

[0122] Additionally, when driver D operates their smartphone SP to remotely start the vehicle's air conditioning, the smartphone SP sends an air conditioning start instruction to the central CT via wireless communication. The central CT then forwards the received air conditioning start instruction to the TCU3 via wireless communication. Upon receiving the air conditioning start instruction, the TCU3, as shown by arrow L12, sends the instruction to the base unit 11 of the integrated ECU2. The base unit 11, upon receiving the instruction, changes its power mode and, if necessary, activates the expansion unit 12. Therefore, the base unit 11 activates before the expansion unit 12. Furthermore, the integrated ECU2, having received the air conditioning start instruction, instructs the regional ECUs 4 to 7, which control the vehicle's air conditioning, to start the air conditioning.

[0123] The integrated ECU2 thus configured is mounted on the vehicle and is connected to the regional ECUs 4 to 7 in a manner that enables data communication with them. It is configured to output instructions to the regional ECUs 4 to 7 based on data received from outside the vehicle.

[0124] The integrated ECU2 has a base unit 11 and an expansion unit 12 that are physically separable from each other.

[0125] The basic unit 11 includes a CPU 31, a ROM 32, and a RAM 33.

[0126] The expansion unit 12 includes CPUs 51 and 61, ROMs 52 and 62, and RAMs 53 and 63.

[0127] The basic unit 11 is equipped with ADAS basic function 37, which is the first function of the ADAS domain, and cockpit basic function 38, which is the first function of the cockpit domain. A domain represents a category of vehicle functions. Examples of domains include ADAS domain, cockpit domain, body domain, powertrain domain, etc.

[0128] The expansion unit 12 is equipped with ADAS expansion function 55 as a second function of the ADAS domain and cockpit expansion function 65 as a second function of the cockpit domain.

[0129] This integrated ECU2, by connecting the expansion unit 12 equipped with ADAS expansion function 55 or cockpit expansion function 65 to the base unit 11, can expand functions for each domain. Furthermore, since the integrated ECU2 integrates multiple functions divided by each domain into one ECU, adjustments between multiple ECUs are not required when developing new applications, thus improving application development efficiency.

[0130] In addition, the expansion unit 12 is equipped with ADAS expansion function 55 and cockpit expansion function 65. Thus, by connecting the expansion unit 12 to the base unit 11 in one operation, two functions (i.e., functions in the ADAS domain and functions in the cockpit domain) can be expanded, which can improve the efficiency of function expansion operations.

[0131] Furthermore, the extension unit 12 is configured to perform the function in place of the stopped function if at least one of the ADAS basic function 37 and the cockpit basic function 38 of the base unit 11 is stopped. Thus, the integrated ECU2 can suppress situations where the ADAS basic function 37 or the cockpit basic function 38 cannot be used, thereby improving the reliability of the integrated ECU2.

[0132] Furthermore, the base unit 11 is configured to monitor for anomalies in the expansion unit 12. The expansion unit 12 is configured to monitor for anomalies in the base unit 11. Thus, in the event of an anomaly in either the base unit 11 or the expansion unit 12, the integrated ECU2 can detect the occurrence of the anomaly and perform processing to address it, thereby improving the reliability of the integrated ECU2.

[0133] Furthermore, the basic unit 11 is configured to start before the expansion unit 12. Thus, the basic unit 11 is able to manage the startup of the expansion unit 12.

[0134] The base unit 11 is configured to transition between at least a first power-on mode M21, a second power-on mode M22, and a power-off mode M1. The first power-on mode M21 is the power mode when both the base unit 11 and the expansion unit 12 are in the powered-on state. The second power-on mode M22 is the power mode when both the base unit 11 and the expansion unit 12 are in the powered-off state. The power-off mode M1 is the power mode when both the base unit 11 and the expansion unit 12 are in the powered-off state.

[0135] Furthermore, the CPU 31 is equipped with ADAS basic functions 37, cockpit basic functions 38, and a virtual machine monitor 35. The virtual machine monitor 35 is configured to manage the ADAS basic functions 37 and cockpit basic functions 38, enabling them to execute in parallel on the CPU 31. Thus, the integrated ECU 2 can maximize the use of the CPU 31's resources to implement the ADAS basic functions 37 and cockpit basic functions 38.

[0136] Additionally, the extended SoC 41 includes a CPU 51, ROM 52, and RAM 53. The extended SoC 42 includes a CPU 61, ROM 62, and RAM 63. The CPU 51, ROM 52, RAM 53, CPU 61, ROM 62, and RAM 63 are mounted on the same circuit board 48. Therefore, by connecting the circuit board 48 to the base unit 11 in a single operation, two functions (i.e., ADAS domain functions and cockpit domain functions) can be extended, improving the efficiency of function expansion operations.

[0137] In the embodiments described above, the integrated ECU2 is equivalent to an electronic control device, the regional ECUs 4 to 7 are equivalent to vehicle-mounted devices, the CPU 31 is equivalent to a basic processor, and the ROM 32 and RAM 33 are equivalent to basic memory.

[0138] In addition, CPU51 and 61 are equivalent to extended processors, ROM52 and 62 and RAM53 and 63 are equivalent to extended memory, ADAS is equivalent to the first domain, and the cockpit is equivalent to the second domain.

[0139] In addition, ADAS basic function 37 is equivalent to the first basic function, cockpit basic function 38 is equivalent to the second basic function, ADAS extended function 55 is equivalent to the first extended function, and cockpit extended function 65 is equivalent to the second extended function.

[0140] In addition, the first power-on mode M21 is equivalent to the first power mode, the second power-on mode M22 is equivalent to the second power mode, and the power-off mode M1 is equivalent to the third power mode.

[0141] In addition, the extended SoC41 is equivalent to the first extended unit, the CPU51 is equivalent to the first extended processor, the ROM52 and RAM53 are equivalent to the first extended memory, the extended SoC42 is equivalent to the second extended unit, the CPU61 is equivalent to the second extended processor, and the ROM62 and RAM63 are equivalent to the second extended memory.

[0142] [Second Implementation]

[0143] The second embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the second embodiment, the parts that differ from the first embodiment will be described. Common configurations will be given the same reference numerals.

[0144] The vehicle control system 1 of the second embodiment differs from that of the first embodiment in that the configuration of the integrated ECU 2 has been changed.

[0145] like Figure 9As shown, the second embodiment differs from the first embodiment in that the SoC 21 based on the integrated ECU 2 is equipped with CPU 31a, CPU 31b, and CPU 31c instead of CPU 31. Furthermore, the second embodiment differs from the first embodiment in that the virtual machine monitor 35 is omitted from the SoC 21 based on the second embodiment.

[0146] Furthermore, CPU31a, CPU31b, and CPU31c respectively perform processing to implement basic infrastructure functions 36, basic ADAS functions 37, and basic cockpit functions 38.

[0147] In the integrated ECU2 configured in this way, among the multiple CPUs 31a, 31b, and 31c, CPU 31b is equipped with ADAS basic functions 37, and CPU 31c is equipped with cockpit basic functions 38. Therefore, because the ADAS basic functions 37 and cockpit basic functions 38 are hardware-separated, changes to the functions of ADAS basic functions 37 and cockpit basic functions 38 can be made so that the effects of such changes do not affect each other.

[0148] In the embodiments described above, CPUs 31a, 31b, and 31c are equivalent to basic processors, with CPU 31b being equivalent to the first basic processor and CPU 31c being equivalent to the second basic processor.

[0149] [Third Implementation Method]

[0150] The third embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the third embodiment, the parts that differ from the first embodiment will be described. Common configurations will be given the same reference numerals.

[0151] The vehicle control system 1 of the third embodiment differs from that of the first embodiment in that the configuration of the integrated ECU 2 is changed.

[0152] like Figure 10 As shown, in the integrated ECU2, the SoC21 includes CPUs 31a, 31b, and 31c instead of CPU 31, which differs from the first embodiment. Additionally, CPU 31b includes a virtual machine monitor 35, which also differs from the first embodiment.

[0153] CPU31a performs processing to implement basic infrastructure functions 36.

[0154] The virtual machine monitor 35, mounted on CPU 31b, manages basic ADAS functions 37 and basic cockpit functions 38.

[0155] CPU 31c performs processing to implement ADAS basic function 39. ADAS basic function 39 is obtained by extracting functions that request a high safety benchmark (e.g., functions with ASIL level C or D) from ADAS basic function 37. ASIL is short for Automotive Safety Integrity Level. That is, ADAS basic function 37 in the second embodiment does not request a high safety benchmark.

[0156] In this integrated ECU2 configuration, the CPU 31b houses ADAS basic functions 37, cockpit basic functions 38, and a virtual machine monitor 35. The virtual machine monitor 35 is configured to manage ADAS basic functions 37 and cockpit basic functions 38, enabling them to execute in parallel on the CPU 31. Furthermore, the CPU 31c houses ADAS basic functions 39. Thus, the integrated ECU2 can maximize the utilization of CPU 31b's resources to implement ADAS basic functions 37 and cockpit basic functions 38. Moreover, because ADAS basic functions 37 and cockpit basic functions 38 are hardware-separated from ADAS basic functions 39, changes to the functionality of ADAS basic functions 37 and 38 can prevent the impact of those changes on ADAS basic functions 39.

[0157] In the above-described implementation, CPU31b is equivalent to the first basic processor, CPU31c is equivalent to the second basic processor, and ADAS basic function 39 is equivalent to the third basic onboard function.

[0158] [Fourth Implementation Method]

[0159] The fourth embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the fourth embodiment, the parts that differ from the first embodiment will be described. Common configurations will be given the same reference numerals.

[0160] The vehicle control system 1 of the fourth embodiment differs from that of the first embodiment in that the configuration of the integrated ECU 2 is changed.

[0161] like Figure 11 As shown, the integrated ECU2 of the fourth embodiment differs from the first embodiment in that it has expansion units 13, 14, 15, and 16 instead of expansion unit 12.

[0162] The expansion units 13, 14, 15, and 16 respectively have expansion SoCs 43, 44, 45, and 46.

[0163] The extended SoC43 includes CPU111, ROM112, and RAM113.

[0164] The extended SoC44 includes CPU121, ROM122, and RAM123.

[0165] The extended SoC45 features a CPU131, ROM132, and RAM133.

[0166] The extended SoC46 features a CPU141, ROM142, and RAM143.

[0167] Extended SoCs 43, 44, 45, and 46 are mounted on circuit boards 115, 125, 135, and 145, respectively.

[0168] The expansion unit 13 is equipped with extended functions such as ADAS. The expansion unit 14 is equipped with functions such as those for achieving Level 4 autonomous driving. The expansion unit 15 is equipped with functions such as those for acting as an edge computer that mediates between the vehicle and a cloud server. The expansion unit 15 is equipped with extended functions such as those for the cockpit.

[0169] Ethernet switch 22 is connected to basic SoC 21, extended SoCs 43, 44, 45, 46 and regional ECUs 4, 5, 6, 7.

[0170] The PCIe switch 23 is connected to the base SoC 21, expansion SoCs 43, 44, 45, 46, and storage device 24.

[0171] The integrated ECU2 thus configured includes expansion unit 13 and expansion unit 14. Expansion unit 13 incorporates ADAS extension functions, while expansion unit 14 incorporates functions for achieving Level 4 autonomous driving. The functions for achieving Level 4 autonomous driving differ from the ADAS extension functions in both domain and function. Therefore, because the functions in expansion unit 13 and expansion unit 14 are hardware-separated, changes to the functions in expansion units 13 and 14 can be made independent of each other.

[0172] Furthermore, expansion unit 13 includes CPU 111, ROM 112, and RAM 113. Expansion unit 14 includes CPU 121, ROM 122, and RAM 123. CPU 111, ROM 112, and RAM 113 are mounted on circuit board 115. CPU 121, ROM 122, and RAM 123 are mounted on circuit board 125. Therefore, since the functions of expansion units 13 and 14 are hardware-separated, changes to the functions of expansion units 13 and 14 can be made independent of each other.

[0173] In the embodiments described above, the expansion unit 13 is equivalent to the first expansion unit, the CPU 111 is equivalent to the first extended processor, and the ROM 112 and RAM 113 are equivalent to the first extended memory.

[0174] In addition, expansion unit 14 is equivalent to a second expansion unit, CPU 121 is equivalent to a second extended processor, and ROM 122 and RAM 123 are equivalent to a second extended memory.

[0175] In addition, circuit board 115 is equivalent to the first circuit board, and circuit board 125 is equivalent to the second circuit board.

[0176] [Fifth Implementation]

[0177] The fifth embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the fifth embodiment, the parts that differ from the fourth embodiment will be described. Common configurations will be given the same reference numerals.

[0178] The vehicle control system 1 of the fifth embodiment differs from that of the fourth embodiment in terms of the connection between the basic unit 11 and the expansion units 13, 14, 15, and 16.

[0179] like Figure 12 As shown, the base unit 11 of the fifth embodiment differs from that of the fourth embodiment in that the PCIe switch 23 is omitted.

[0180] Furthermore, the basic unit 11 and the expansion unit 13 are connected by an LVDS communication line 18, which differs from the fourth embodiment. Similarly, the basic unit 11 is connected to the expansion units 14, 15, and 16 by an LVDS communication line 18, which also differs from the fourth embodiment. LVDS is short for Low Voltage Differential Signaling.

[0181] [Sixth Implementation Method]

[0182] The sixth embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the sixth embodiment, the parts that differ from the first embodiment will be described. Common configurations will be given the same reference numerals.

[0183] The vehicle control system 1 of the sixth embodiment differs from the first embodiment in that the configuration of the basic unit 11 and the expansion unit 12 is changed.

[0184] like Figure 13As shown, in the basic unit 11 of the sixth embodiment, the hardware IP34 is equipped with an ISP processing function 81. Additionally, the CPU31 is equipped with an ADAS image recognition function 82 and an ADAS application 83. The ADAS image recognition function 82 and the ADAS application 83 are functions included in the basic ADAS functions 37.

[0185] The ISP processing function 81 is a function that performs ISP processing on the image data generated by the front camera 75.

[0186] ADAS image recognition function 82 is a function that performs image recognition processing using image data that has been processed by ISP by ISP processing function 81.

[0187] ADAS application 83 utilizes the recognition results of ADAS image recognition function 82 to perform adaptive cruise control and lane keeping assist, etc.

[0188] In the expansion unit 12 of the sixth embodiment, the hardware IP54 is equipped with an ISP processing function 84. Additionally, the CPU 31 is equipped with an autonomous driving image recognition function 85, an autonomous driving object recognition function 86, and an autonomous driving application 87. The autonomous driving image recognition function 85, the autonomous driving object recognition function 86, and the autonomous driving application 87 are functions included in the ADAS expansion function 55.

[0189] The ISP processing function 84 is a function that performs ISP processing on the image data generated by the front side camera 76.

[0190] The autonomous driving image recognition function 85 is a function that performs image recognition processing using image data processed by the ISP processing function 84.

[0191] The autonomous driving object recognition function 86 is a function that uses the recognition results of the autonomous driving image recognition function 85 to perform object recognition processing.

[0192] The autonomous driving application 87 uses the recognition results of the autonomous driving object recognition function 86 to perform autonomous driving.

[0193] The base unit 11 and the expansion unit 12 monitor each other. That is, the base unit 11 detects anomalies occurring in the expansion unit 12 by communicating with the expansion unit 12. Similarly, the expansion unit 12 detects anomalies occurring in the base unit 11 by communicating with the base unit 11.

[0194] When the base unit 11 detects an anomaly in the ISP processing function 84 in the expansion unit 12, as indicated by arrow L21, it sends the image data that has undergone ISP processing by the ISP processing function 81 to the expansion unit 12. If the image data is, for example, digital data in RGB or YUV format, it needs to be sent via LVDS or PCIe.

[0195] Furthermore, the autonomous driving image recognition function 85 performs image recognition processing using image data that has undergone ISP processing by the ISP processing function 81.

[0196] Therefore, even if the vehicle control system 1 becomes unable to utilize the image data generated by the front side camera 76, it can still continue autonomous driving by utilizing the image data generated by the front camera 75.

[0197] [Seventh Implementation Method]

[0198] The seventh embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the seventh embodiment, the parts that differ from the sixth embodiment will be described. Common configurations will be given the same reference numerals.

[0199] like Figure 14 As shown, the vehicle control system 1 of the seventh embodiment differs from the sixth embodiment in that the processing when an abnormality is detected in the ISP processing function 84 is changed.

[0200] When the base unit 11 detects an anomaly in the ISP processing function 84 of the expansion unit 12, as indicated by arrow L22, it sends the recognition result of the ADAS image recognition function 82 to the expansion unit 12. If the recognition result of the ADAS image recognition function 82 is, for example, digital data in RGB or YUV format, the recognition result needs to be sent via LVDS or PCIe. On the other hand, if the recognition result of the ADAS image recognition function 82 is, for example, text data, the recognition result can also be sent via Ethernet.

[0201] Furthermore, the autonomous driving image recognition function 85 utilizes the recognition results of the ADAS image recognition function 82 to perform image recognition processing.

[0202] Therefore, even if the vehicle control system 1 becomes unable to utilize the image data generated by the front side camera 76, it can still continue autonomous driving by utilizing the image data generated by the front camera 75.

[0203] In the integrated ECU2 configured in this way, the base unit 11 enables the basic ADAS function 37 in the base unit 11 to operate in cooperation with the ADAS extended function 55 in the extension unit 12. As a result, the integrated ECU2 allows the extension unit 12 to utilize the resources of the base unit 11, thereby reducing the processing load of the extension unit 12.

[0204] [Eighth Implementation Method]

[0205] The eighth embodiment of this disclosure will now be described with reference to the accompanying drawings. Furthermore, in the eighth embodiment, the parts that differ from the first embodiment will be described. Common configurations will be given the same reference numerals.

[0206] The vehicle control system 1 of the eighth embodiment differs from the first embodiment in that the basic monitoring processing and the extended monitoring processing are modified.

[0207] Next, the steps of the basic monitoring process in the eighth embodiment will be explained.

[0208] like Figure 15 As shown, the basic monitoring process in the eighth embodiment differs from that in the first embodiment in that it omits the processing in S30. That is, if an anomaly is detected in the expansion unit 12 in S20, the CPU 31 switches to S40.

[0209] The extended monitoring process in the eighth embodiment differs from that in the first embodiment in that it is performed by the base SoC 21 of the base unit 11 instead of the extended SoC 41 of the extended unit 12.

[0210] Furthermore, the extended monitoring process in the eighth embodiment differs from the first embodiment in that it performs the process of S212 instead of S210, and omits the process of S230.

[0211] That is, when the extended monitoring process of the eighth embodiment is executed, such as Figure 16 As shown, the CPU 31 of the base SoC 21 performs the processing of detecting the abnormality that occurred in the base unit 11 in S212, and then transfers to S220.

[0212] In addition, if an anomaly is detected in the expansion unit 12 in S220, the CPU 31 switches to S240.

[0213] In the integrated ECU2 configured in this way, the base unit 11 is configured to monitor for anomalies in both the base unit 11 and the expansion unit 12. Therefore, the integrated ECU2 can identify the occurrence of an anomaly in either the base unit 11 or the expansion unit 12, and can perform appropriate actions to address the anomaly, thus improving the reliability of the integrated ECU2.

[0214] While one embodiment of this disclosure has been described above, this disclosure is not limited to the above embodiment and can be implemented in various modifications.

[0215] [Variation Example 1]

[0216] In the first embodiment described above, an arrangement is shown in which both ADAS extension function 55 and cockpit extension function 65 are mounted in the extension unit 12. However, the extension unit 12 may also mount only one of ADAS extension function 55 and cockpit extension function 65.

[0217] [Variation Example 2]

[0218] In the first embodiment described above, the execution is shown. Figure 4 Basic monitoring and processing Figure 5 The way to extend monitoring processing. However, Figure 4 The processing of S40 and S50, and Figure 5 The processing of S260 and S270 can also be omitted.

[0219] The SoCs 21 and 41 and their methods described in this disclosure can be implemented by a special-purpose computer comprising a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the SoCs 21 and 41 and their methods described in this disclosure can be implemented by a special-purpose computer comprising a processor composed of one or more special-purpose hardware logic circuits. Alternatively, the SoCs 21 and 41 and their methods described in this disclosure can be implemented by one or more special-purpose computers comprising a combination of a processor and memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits. Furthermore, the computer program, as instructions executed by a computer, can also be stored in a computer-readable, non-transitory tangible recording medium. The methods for implementing the functions of the various parts contained in the SoCs 21 and 41 do not necessarily require software; all functions can be implemented using one or more hardware components.

[0220] Multiple functions of a single component in the above embodiments can be achieved through multiple components, or a single function of a single component can be achieved through multiple components. Furthermore, multiple functions of multiple components can be achieved through a single component, or a single function achieved by multiple components can be achieved through a single component. Additionally, a portion of the configuration in the above embodiments can be omitted. Furthermore, at least a portion of the configuration in the above embodiments can be added to or substituted relative to other configurations of the above embodiments.

[0221] In addition to the integrated ECU2 described above, this disclosure can also be implemented in various ways, such as a system incorporating the integrated ECU2, a program for enabling a computer to function as the integrated ECU2, a non-transitory physical recording medium such as a semiconductor memory that records the program, and a function expansion method.

[0222] [The technical concepts disclosed in this specification]

[0223] [Project 1]

[0224] An electronic control device (2) is mounted on a vehicle and connected to an on-board unit (4, 5, 6, 7) mounted on the vehicle in a manner capable of data communication with the on-board unit, and is configured to output instructions to the on-board unit based on data received from outside the vehicle, wherein,

[0225] It has a basic unit (11) that can be physically separated from each other and one or more extended units (12, 13, 14, 15, 16).

[0226] The basic unit includes one or more basic processors (31, 31a, 31b, 31c) that serve as one or more processors mounted on the basic unit, and a basic memory (32, 33) that serves as a memory mounted on the basic unit.

[0227] One or more of the expansion units each have an expansion processor (51, 61, 111, 121, 131, 141) as a processor mounted on the expansion unit, and an expansion memory (52, 53, 62, 63, 112, 113, 122, 123, 132, 133, 142, 143) as a memory mounted on the expansion unit.

[0228] The basic unit is equipped with a first basic equipped function (37) as a first function of a first domain and a second basic equipped function (38) as a first function of a second domain. The first domain is one of a plurality of domains divided according to the functions of the vehicle, and the second domain is one of the plurality of domains that is different from the first domain.

[0229] One or more of the extended units are equipped with at least one of a first extended mounting function (55) as a second function of the first domain and a second extended mounting function (65) as a second function of the second domain.

[0230] [Project 2]

[0231] The electronic control device as described in Project 1, wherein...

[0232] One or more of the expansion units are equipped with the first expansion function and the second expansion function.

[0233] [Project 3]

[0234] The electronic control device as described in Project 1 or Project 2, wherein...

[0235] One or more of the expansion units are configured to perform, in place of the stopped function, if at least one of the first basic mounting function and the second basic mounting function of the base unit is stopped.

[0236] [Project 4]

[0237] The electronic control device as described in any one of Items 1 to 3, wherein...

[0238] The basic unit is configured to monitor anomalies in one or more of the extended units.

[0239] One or more of the extended units are configured to monitor anomalies in the base unit.

[0240] [Project 5]

[0241] The electronic control device as described in any one of Items 1 to 3, wherein...

[0242] The base unit is configured to monitor anomalies of the base unit and anomalies of one or more of the extended units.

[0243] [Project 6]

[0244] The electronic control device as described in any one of items 1 to 5, wherein...

[0245] The basic unit is configured to start before one or more of the expansion units.

[0246] [Project 7]

[0247] The electronic control device as described in any one of items 1 to 6, wherein...

[0248] The state where operation ceases due to power supply interruption is defined as the "stopped state," and the state where operation begins due to power supply is defined as the "started state."

[0249] The basic unit is configured to migrate between at least a first power mode, a second power mode, and a third power mode.

[0250] The first power mode is a mode in which the basic unit is in the startup state, and one or more of the expansion units are in the startup state.

[0251] The second power mode is a mode in which the basic unit is in the startup state and one or more of the expansion units are in the shutdown state.

[0252] The third power mode is a mode in which the basic unit is in the stopped state and one or more of the expansion units are in the stopped state.

[0253] [Project 8]

[0254] The electronic control device as described in any one of items 1 to 7, wherein...

[0255] One or more of the basic processors are multiple basic processors (31a, 31b, 31c).

[0256] The first base processor (31b), which is one of the multiple base processors, is equipped with the first base-equipped function.

[0257] The second base processor (31c), which is one of the multiple base processors and is different from the first base processor, is equipped with the second base-equipped function.

[0258] [Project 9]

[0259] The electronic control device as described in any one of items 1 to 7, wherein...

[0260] One or more of the aforementioned basic processors constitute one of the aforementioned basic processors (31).

[0261] A base processor is equipped with a first base functionality, a second base functionality, and a virtual machine monitor (35), the virtual machine monitor being configured to manage the first base functionality and the second base functionality so that the first base functionality and the second base functionality can be executed in parallel on a base processor.

[0262] [Project 10]

[0263] The electronic control device as described in any one of items 1 to 7, wherein...

[0264] One or more of the base processors are multiple base processors (31a, 31b, 31c). A first base processor (31b), which is one of the multiple base processors, carries a first base functionality, a second base functionality, and a virtual machine monitor (35). The virtual machine monitor is configured to manage the first base functionality and the second base functionality so that the first base functionality and the second base functionality can be executed in parallel on a single first base processor.

[0265] The second base processor (31c), which is one of the multiple base processors and is different from the first base processor, is equipped with a third base function (39) that is different from the first base function and the second base function.

[0266] [Project 11]

[0267] The electronic control device as described in any one of items 1 to 10, wherein...

[0268] One or more of the extension units are multiple extension units (13, 14, 15, 16).

[0269] The plurality of expansion units include: a first expansion unit (13, 41) as one of the plurality of expansion units; and a second expansion unit (14, 42) as one of the plurality of expansion units that is different from the first expansion unit.

[0270] The function carried on one or more of the expansion units is defined as an extended carrying function, wherein the first expansion unit and the second expansion unit are equipped with an extended carrying function that is different from at least one of the domains and functions.

[0271] [Project 12]

[0272] The electronic control device as described in Project 11, wherein...

[0273] The first expansion unit (13) includes a first expansion processor (111) as a processor mounted on the first expansion unit and a first expansion memory (112, 113) as a memory mounted on the first expansion unit.

[0274] The second expansion unit (14) includes a second expansion processor (121) as a processor mounted on the second expansion unit and a second expansion memory (122, 123) as a memory mounted on the second expansion unit.

[0275] The first extended processor and the first extended memory are mounted on the first circuit board (115).

[0276] The second extended processor and the second extended memory are mounted on a second circuit board (125) that is different from the first circuit board.

[0277] [Project 13]

[0278] The electronic control device as described in Project 11, wherein...

[0279] The first expansion unit (41) includes a first expansion processor (51) as a processor mounted on the first expansion unit and a first expansion memory (52, 53) as a memory mounted on the first expansion unit.

[0280] The second expansion unit (42) includes a second expansion processor (61) as a processor mounted on the second expansion unit and a second expansion memory (62, 63) as a memory mounted on the second expansion unit.

[0281] The first extended processor, the first extended memory, the second extended processor, and the second extended memory are mounted on the same circuit board (48).

[0282] [Project 14]

[0283] The electronic control device as described in any one of items 1 to 13, wherein...

[0284] The expansion unit (12) is equipped with the first expansion function.

[0285] The base unit enables the first basic mounted function in the base unit to operate in cooperation with the first extended mounted function in the extended unit.

Claims

1. An electronic control device (2) mounted on a vehicle and connected to an on-board unit (4, 5, 6, 7) mounted on the vehicle in a manner capable of data communication with the on-board unit, and configured to output instructions to the on-board unit based on data received from outside the vehicle, characterized in that... , It has a basic unit (11) that can be physically separated from each other and one or more extended units (12, 13, 14, 15, 16). The basic unit includes one or more basic processors (31, 31a, 31b, 31c) that serve as one or more processors mounted on the basic unit, and a basic memory (32, 33) that serves as a memory mounted on the basic unit. One or more of the expansion units each have an expansion processor (51, 61, 111, 121, 131, 141) as a processor mounted on the expansion unit, and an expansion memory (52, 53, 62, 63, 112, 113, 122, 123, 132, 133, 142, 143) as a memory mounted on the expansion unit. The basic unit is equipped with a first basic equipped function (37) as a first function of a first domain and a second basic equipped function (38) as a first function of a second domain. The first domain is one of a plurality of domains divided according to the functions of the vehicle, and the second domain is one of the plurality of domains that is different from the first domain. One or more of the extended units are equipped with at least one of a first extended mounting function (55) as a second function of the first domain and a second extended mounting function (65) as a second function of the second domain.

2. The electronic control device as described in claim 1, characterized in that, One or more of the expansion units are equipped with the first expansion function and the second expansion function.

3. The electronic control device as described in claim 1 or 2, characterized in that, One or more of the expansion units are configured to perform, in place of the stopped function, if at least one of the first basic mounting function and the second basic mounting function of the base unit is stopped.

4. The electronic control device as described in claim 1 or 2, characterized in that, The basic unit is configured to monitor anomalies in one or more of the extended units. One or more of the extended units are configured to monitor anomalies in the base unit.

5. The electronic control device as described in claim 1 or 2, characterized in that, The base unit is configured to monitor anomalies of the base unit and anomalies of one or more of the extended units.

6. The electronic control device as described in claim 1 or 2, characterized in that, The basic unit is configured to start prior to one or more of the expansion units.

7. The electronic control device as described in claim 1 or 2, characterized in that, The state where operation ceases due to power supply interruption is defined as the "stopped state," and the state where operation begins due to power supply is defined as the "started state." The basic unit is configured to migrate between at least a first power mode, a second power mode, and a third power mode. The first power mode is a mode in which the basic unit is in the startup state and one or more of the expansion units are in the startup state. The second power mode is a mode in which the basic unit is in the startup state and one or more of the expansion units are in the shutdown state. The third power mode is a mode in which the basic unit is in the stopped state and one or more of the expansion units are in the stopped state.

8. The electronic control device as described in claim 1 or 2, characterized in that, One or more of the basic processors are multiple basic processors (31a, 31b, 31c). The first base processor (31b), which is one of the multiple base processors, is equipped with the first base-equipped function. The second base processor (31c), which is one of the multiple base processors and is different from the first base processor, is equipped with the second base-equipped function.

9. The electronic control device as described in claim 1 or 2, characterized in that, One or more of the aforementioned basic processors constitute one of the aforementioned basic processors (31). A base processor is equipped with a first base functionality, a second base functionality, and a virtual machine monitor (35), the virtual machine monitor being configured to manage the first base functionality and the second base functionality so that the first base functionality and the second base functionality can be executed in parallel on a base processor.

10. The electronic control device as described in claim 1 or 2, characterized in that, One or more of the basic processors are multiple basic processors (31a, 31b, 31c). The first base processor (31b), which is one of the plurality of base processors, is equipped with a first base functionality, a second base functionality, and a virtual machine monitor (35). The virtual machine monitor is configured to manage the first base functionality and the second base functionality so that the first base functionality and the second base functionality can be executed in parallel on the first base processor. The second base processor (31c), which is one of the multiple base processors and is different from the first base processor, is equipped with a third base function (39) that is different from the first base function and the second base function.

11. The electronic control device as described in claim 1 or 2, characterized in that, One or more of the extension units are multiple extension units (13, 14, 15, 16). The plurality of expansion units include: a first expansion unit (13, 41) as one of the plurality of expansion units; and a second expansion unit (14, 42) as one of the plurality of expansion units that is different from the first expansion unit. The function carried on one or more of the expansion units is defined as an extended carrying function, wherein the first expansion unit and the second expansion unit are equipped with an extended carrying function that is different from at least one of the domains and functions.

12. The electronic control device as claimed in claim 11, characterized in that, The first expansion unit (13) includes a first expansion processor (111) as a processor mounted on the first expansion unit and a first expansion memory (112, 113) as a memory mounted on the first expansion unit. The second expansion unit (14) includes a second expansion processor (121) as a processor mounted on the second expansion unit and a second expansion memory (122, 123) as a memory mounted on the second expansion unit. The first extended processor and the first extended memory are mounted on the first circuit board (115). The second extended processor and the second extended memory are mounted on a second circuit board (125) that is different from the first circuit board.

13. The electronic control device as claimed in claim 11, characterized in that, The first expansion unit (41) includes a first expansion processor (51) as a processor mounted on the first expansion unit and a first expansion memory (52, 53) as a memory mounted on the first expansion unit. The second expansion unit (42) includes a second expansion processor (61) as a processor mounted on the second expansion unit and a second expansion memory (62, 63) as a memory mounted on the second expansion unit. The first extended processor, the first extended memory, the second extended processor, and the second extended memory are mounted on the same circuit board (48).

14. The electronic control device as described in claim 1 or 2, characterized in that, The expansion unit (12) is equipped with the first expansion function. The base unit enables the first basic mounted function in the base unit to operate in cooperation with the first extended mounted function in the extended unit.

Images