Storage management device for vehicle
The storage management device segregates vehicle data into dedicated partitions based on functional safety levels, preventing interference and ensuring reliable storage for all data types by addressing the database write limit issues in existing vehicle control devices.
Patent Information
- Application Number
- JP2023077114
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-05-09
AI Technical Summary
The existing vehicle control devices face issues with the upper limit of database writes due to differing frequencies of data with varying functional safety levels, where high-frequency low-safety-level data interferes with low-frequency high-safety-level data, preventing the latter from being written to the database.
A storage management device for vehicles that includes an execution unit and storage unit, segregating data into dedicated partitions based on predefined functional safety levels, ensuring each partition can handle data independently without interference.
This configuration prevents interference between data writes of different safety levels, ensuring reliable storage for all data types by allocating specific partitions for each safety level, thereby maintaining the integrity of high-importance data.
Smart Images

Figure 2024161997000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a storage management device for a vehicle. [Background technology]
[0002] The control device for a vehicle disclosed in Patent Document 1 includes a database and a cache as storage areas. The control device executes a plurality of applications. A functional safety level, which is an index of functional safety for automobiles, is set for each application. When executing an application, the control device changes the manner in which the execution result of the application is stored according to the functional safety level of the application. For the execution result of an application with a low functional safety level, the control device temporarily stores the execution result in the cache. The control device then moves the execution result to the database. On the other hand, the control device directly stores the execution result of an application with a high functional safety level in the database. As a result of these, the control device finally writes the execution result of the application with a low functional safety level and the execution result of the application with a high functional safety level in the same database. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2022-065218 Summary of the Invention [Problem to be solved by the invention]
[0004] There is an upper limit to the number of times data can be written to a database. Therefore, when data of different functional safety levels are written to the same database as in Patent Document 1, the following problem occurs. Suppose that the writing frequency of data of the first functional safety level is high, while the writing frequency of data of the second functional safety level is low. In this case, even if not much data of the second functional safety level is written to the database, the number of times the database can be written may reach the upper limit due to the high writing frequency of data of the first functional safety level. In other words, writing data of the first functional safety level becomes a hindrance, and it becomes impossible to write data of the second functional safety level. [Means for solving the problem]
[0005] A memory management device for a vehicle to solve the above problem comprises an execution unit and a memory unit, wherein the execution unit stores in the memory unit data corresponding to the operation of each in-vehicle system to which one of a plurality of functional safety levels is pre-set, and the memory unit has a first partition and a second partition which are pre-assigned, wherein the first partition is capable of storing data corresponding to the operation of an in-vehicle system to which a functional safety level lower than a predetermined specific level is set, and the second partition is capable of storing data corresponding to the operation of an in-vehicle system to which a functional safety level equal to or higher than the specific level is set. Effect of the Invention
[0006] The above configuration can prevent the writing of data at one functional safety level from interfering with the writing of data at another functional safety level. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 is a schematic diagram of a vehicle. [Diagram 2] FIG. 2 is a schematic diagram showing the partition settings of the first memory. [Diagram 3] FIG. 3 is a sequence diagram showing a flow of storing data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Hereinafter, an embodiment of a storage management device for a vehicle will be described with reference to the drawings. <Overall vehicle configuration> As shown in FIG. 1, the vehicle 100 includes a central ECU 10. The central ECU 10 is a control device that controls the entire vehicle 100. The central ECU 10 includes a processing circuit 12. The processing circuit 12 includes a CPU 20, a first memory 21, a second memory 22, and a third memory 23. The first memory 21 is a non-volatile memory. The first memory 21 functions as a storage. The second memory 22 is a non-volatile memory. The second memory 22 stores in advance various programs in which processes to be executed by the CPU 20 are described. The third memory 23 is a volatile memory. The CPU 20, the first memory 21, the second memory 22, and the third memory 23 can communicate with each other. The CPU 20 is an execution unit. The first memory 21 is a storage unit. The central ECU 10 is a storage management device for the vehicle. ECU is an abbreviation for "Electronic Control Unit."
[0009] The vehicle 100 is equipped with a plurality of information acquisition devices 30. In FIG. 1, one of the plurality of information acquisition devices 30 is shown as a representative. The information acquisition device 30 is a device that acquires various information related to the vehicle 100. The various information includes peripheral monitoring information of the vehicle 100, information related to the running state of the vehicle 100, and information on the operating state of an in-vehicle device 90 described later. An example of the information acquisition device 30 is a camera that captures an image of the surroundings of the vehicle 100. An example of the information acquisition device 30 is a sensor that detects the running speed of the vehicle 100. An example of the information acquisition device 30 is a sensor that detects the hydraulic pressure of a brake device mounted on the vehicle 100. Each information acquisition device 30 outputs a signal according to the information acquired by itself.
[0010] <In-vehicle systems> The vehicle 100 is equipped with a plurality of in-vehicle systems 60. The in-vehicle systems 60 are equipped with an in-vehicle device 90 and a base ECU 70 that controls the in-vehicle device 90. The in-vehicle device 90 operates in response to electrical signals from the base ECU 70 to realize various functions. The various functions include functions necessary for the vehicle 100 to travel. The various functions include functions that enhance the safety and comfort of the occupants. Examples of the in-vehicle device 90 include an engine, a brake device, a power steering device, an airbag device, a suspension device, and a car navigation device.
[0011] The base ECU 70 includes a processing circuit 72. The processing circuit 72 includes a CPU 80, a nonvolatile memory 81, and a volatile memory 82. The nonvolatile memory 81 stores in advance various programs in which processes to be executed by the CPU 80 are described. An example of the various programs is an application A for operating the in-vehicle device 90 to be controlled. In this embodiment, it is assumed that one application A is stored in the nonvolatile memory 81 for one base ECU 70. The CPU 80, the nonvolatile memory 81, and the nonvolatile memory 82 can communicate with each other. The processing circuit 72 may include a nonvolatile memory for storage in addition to the nonvolatile memory 81. FIG. 1 shows the details of the processing circuit 72 for only one base ECU 70. The base ECU 70 is connected to the central ECU 10 via a bus 102. The base ECU 70 can communicate with the central ECU 10.
[0012] Basically, one base ECU 70 controls one in-vehicle device 90. Depending on the contents of application A, one base ECU 70 may control several in-vehicle devices 90 in a composite manner. In this case, a group of these constitutes one in-vehicle system 60. In short, the in-vehicle system 60 is a group of application A for realizing a specific function, the base ECU 70 that executes the application A, and one or more in-vehicle devices 90 that operate in response to the base ECU 70 executing application A.
[0013] In each in-vehicle system 60, the base ECU 70 generates various data when operating the in-vehicle device 90. Generating data includes acquiring information from the information acquisition device 30 and making the information a target for handling by the base ECU 70. Generating data includes calculating a control amount for the in-vehicle device 90. Generating data includes generating failure information when a failure occurs in the in-vehicle device 90. Hereinafter, data generated by the base ECU 70 in response to the operation of the in-vehicle device 90 by the base ECU 70 with respect to a certain in-vehicle system 60 is referred to as data corresponding to the operation of the in-vehicle system 60.
[0014] Each in-vehicle system 60 is preset with one of multiple functional safety levels. The functional safety levels are defined as indicators of functional safety in ISO26262, an international standard for automobiles. In other words, the functional safety levels are classified into five levels: QM and ASIL-A to D. The functional safety levels increase in the following order: "QM" < "ASIL-A" < "ASIL-B" < "ASIL-C" < "ASIL-D". QM is an abbreviation for "Quality Management". ASIL is an abbreviation for "Automotive Safety Integrity Level".
[0015] The in-vehicle systems 60 can be roughly divided into three types according to the functional safety level set for each. One of the three types of in-vehicle systems 60 is called a first system 61. The first system 61 is an in-vehicle system 60 for which "QM" is set. One of the three types of in-vehicle systems 60 is called a second system 62. The second system 62 is an in-vehicle system 60 for which any of "ASIL-A", "ASIL-B", and "ASIL-C" is set. One of the three types of in-vehicle systems 60 is called a third system 63. The third system 63 is an in-vehicle system 60 for which "ASIL-D" is set. There are a plurality of the first systems 61, the second systems 62, and the third systems 63. In FIG. 1, one of the plurality of first systems 61 is shown as a representative. This is also true for the second system 62 and the third system 63. In the following, when the three types of in-vehicle systems 60 are individually described, their individual names will be described. When the three types of in-vehicle systems 60 are collectively described, they will be referred to as in-vehicle systems 60.
[0016] <Details of the first memory of the central ECU> 2, the first memory 21 of the central ECU 10 includes three pre-allocated partitions P. That is, the first memory 21 includes a first partition P1, a second partition P2, and a third partition P3. These three partitions P are storage areas that are already allocated to the first memory 21 when the vehicle 100 is shipped from the factory. In the following, when the three partitions P are individually described, their individual names will be used. When the three partitions P are collectively described, they will be referred to as partition P.
[0017] The first partition P1 is capable of storing data corresponding to the operation of the first system 61. The first partition P1 stores only data corresponding to the operation of the first system 61. In other words, the first partition P1 is a storage area dedicated to data corresponding to the operation of the in-vehicle system 60 to which the lowest functional safety level is set. The first partition P1 is assigned the number "1" as a dedicated number for designating the first partition P1.
[0018] The second partition P2 is capable of storing data corresponding to the operation of the second system 62. The second partition P2 stores only data corresponding to the operation of the second system 62. In other words, the second partition P2 is a storage area dedicated to data corresponding to the operation of the in-vehicle system 60 excluding the first system 61 and the third system 63. The second partition P2 is assigned the number "2" as a dedicated number for designating the second partition P2.
[0019] The third partition P3 is capable of storing data corresponding to the operation of the third system 63. The third partition P3 stores only data corresponding to the operation of the third system 63. In other words, the third partition P3 is a storage area dedicated to data corresponding to the operation of the in-vehicle system 60 to which the highest functional safety level is set. The third partition P3 is assigned the number "3" as a dedicated number for designating the third partition P3.
[0020] The second memory 22 of the central ECU 10 stores in advance a correspondence relationship between the designated numbers assigned to each partition P and the actual storage areas. This correspondence relationship is called memory information.
[0021] It can be said that the three partitions P are set as follows. The first partition P1 is a storage area intended for the in-vehicle system 60 to which a functional safety level lower than the first specified level is set. The second partition P2 is a storage area intended for the in-vehicle system 60 to which a functional safety level equal to or higher than the first specified level and lower than the second specified level is set. The third partition P3 is a storage area intended for the in-vehicle system 60 to which a functional safety level equal to or higher than the second specified level is set. The first specified level is predetermined as "ASIL-A". The second specified level is predetermined as "ASIL-D".
[0022] <specific identifier> With regard to each in-vehicle system 60, the base ECU 70 stores data generated in response to the operation of the in-vehicle device 90 in the first memory 21 of the central ECU 10 as necessary. At this time, the base ECU 70 performs the following operations on the central ECU 10. That is, the base ECU 70 specifies the destination partition P. The base ECU 70 uses a specific identifier to specify the destination partition P. This specific identifier will be described.
[0023] The specific identifier is pre-stored in the base ECU 70. The specific identifier is pre-assigned to each in-vehicle system 60. The specific identifier is a combination of three pieces of information.
[0024] The first information is information indicating the target in-vehicle system 60. This first information is an individual number for each in-vehicle system 60 for distinguishing the target in-vehicle system 60 from other in-vehicle systems 60.
[0025] The second information is information indicating the functional safety level set for the target in-vehicle system 60. That is, the second information indicates either QM or ASIL-A to ASIL-D. For example, the second information is a numerical representation of the functional safety level in ascending order. For example, the lowest functional safety level is set to "1". Then, the numerical value is increased by one as the functional safety level becomes higher.
[0026] The third information is information indicating the partition P in which the data is to be saved. The information indicating the partition P is the number of the partition P. That is, when the target in-vehicle system 60 is the first system 61, the information indicating the partition P is "1". When the target in-vehicle system 60 is the second system 62, the information indicating the partition P is "2". When the target in-vehicle system 60 is the third system 63, the information indicating the partition P is "3".
[0027] <Data storage flow> Data corresponding to the operation of a certain in-vehicle system 60 is referred to as first data. The central ECU 10 stores the first data in the first memory 21 in the following manner. As shown in step S100 of FIG. 3, it is assumed that the base ECU 70 has generated the first data. After generating the first data, the base ECU 70 performs processing in step S102. In step S102, the base ECU 70 transmits a write request to the central ECU 10. The write request includes the first data, a specific identifier, and a command signal to store the first data.
[0028] When the central ECU 10 receives the write request, the central ECU 10 performs the process of step S110. In step S110, the CPU 20 of the central ECU 10 performs the write process. Specifically, the CPU 20 refers to the specific identifier among the information included in the write request. Then, the CPU 20 identifies the number of the partition P in which the first data is to be stored based on the specific identifier. Then, the CPU 20 writes the first data to the partition P with the identified number in the first memory 21. At this time, the CPU 20 refers to the above memory information. In this way, the CPU 20 grasps the actual storage area to be written. In this manner, the CPU 20 stores the first data requested to be written in the first memory 21.
[0029] The above describes the flow of storing data in the first memory 21 of the central ECU 10, taking one piece of data as an example. The CPU 20 of the central ECU 10 repeats the above-mentioned write process in response to write requests sequentially sent from each in-vehicle system 60. Accordingly, the number of write operations in each partition P increases.
[0030] <Operation of the embodiment> Now, assume that the base ECU 70 of one of the third systems 63 generates data. For example, the base ECU 70 acquires an image captured by a camera. When the base ECU 70 stores the captured image in the first memory 21 of the central ECU 10, the base ECU 70 performs the following. That is, the base ECU 70 transmits a write request to the central ECU 10. In the specific identifier included in this write request, the number of the partition P that specifies the storage destination of the data is "3". In response to this write request, the CPU 20 of the central ECU 10 stores the captured image in the third partition P3 of the first memory 21.
[0031] <Effects of the embodiment> (1) Each partition P has an upper limit on the number of times data can be written. If data from three types of in-vehicle systems 60 are written to a common partition, the following problem may occur. That is, assume that data from the first system 61 is written more frequently than data from the third system 63. In this case, even if data from the third system 63 is not written to the common partition very often, the number of times the common partition can be written may reach its upper limit due to the high frequency at which data from the first system 61 is written to the common partition.
[0032] In this regard, the first memory 21 of the central ECU 10 has dedicated partitions P for the first system 61, the second system 62, and the third system 63, respectively. The number of times data is written to each partition P is independent of the other partitions P. Therefore, by providing a dedicated partition P for each type of in-vehicle system 60, the following becomes possible. That is, with regard to the three types of in-vehicle systems 60, it is possible to prevent data writing for one type of in-vehicle system 60 from interfering with data writing for another type of in-vehicle system 60.
[0033] (2) Data of an in-vehicle system 60 with a high functional safety level tends to be more important than data of an in-vehicle system 60 with a low functional safety level. In this embodiment, the first memory 21 of the central ECU 10 includes a first partition P1 dedicated to the first system 61. Therefore, writing of data with a low level of importance can be prevented from interfering with writing of data with a high level of importance.
[0034] (3) In addition to (2), the first memory 21 of the central ECU 10 includes a third partition P3 dedicated to the third system 63. In this embodiment, it is possible to reliably secure a write area for data of particularly high importance.
[0035] <Example of change> The above embodiment can be modified as follows: The above embodiment and the following modified examples can be implemented in combination with each other to the extent that there is no technical contradiction.
[0036] The base ECU 70 may store multiple applications A. In this case, even if the combination of the base ECU 70 and the in-vehicle device 90 is the same, the in-vehicle device 90 may realize different functions depending on the content of the application A executed by the specific ECU. In such a case, each realized function may be treated as constituting an individual in-vehicle system 60. Note that, when the base ECU 70 stores multiple applications A, it is sufficient for the base ECU 70 to store a specific identifier for each stored application A, and therefore for each in-vehicle system 60.
[0037] When the base ECU 70 stores multiple applications A, the following may occur: the base ECU 70 controls a different in-vehicle device 90 for each application A. In this case, the in-vehicle system 60 may be determined for each combination of the base ECU 70 and the in-vehicle device 90 based on the application A.
[0038] Regarding the specific identifier, the information indicating the in-vehicle system 60 is not limited to the example of the above embodiment. That is, the information indicating the in-vehicle system 60 does not have to be a number. The information indicating the in-vehicle system 60 may be any information that can distinguish one in-vehicle system 60 from another in-vehicle system 60. The same applies to the information indicating the functional safety level and the information indicating the partition P. That is, the information indicating the functional safety level and the information indicating the partition P are not limited to those using numbers.
[0039] In the above embodiment, when the CPU 20 of the central ECU 10 stores data in the first memory 21, the CPU 20 selects the partition P in which to store the data based on the specific identifier. However, the manner of processing by which the CPU 20 selects a partition P is not limited to the example of the above embodiment. As long as a partition P that is predetermined in correspondence with the functional safety level can be appropriately selected, the manner of processing by which a partition P is selected may be changed from the example of the above embodiment. For example, the following manner may be adopted.
[0040] As a premise, the specific identifier included in the write request by the base ECU 70 reflects only the first information in the above embodiment. That is, the specific identifier is an individual number for each in-vehicle system 60. Meanwhile, the second memory 22 of the central ECU 10 stores a management list in advance. The management list is a table that associates the following two pieces of information. One piece of information is an individual number for each in-vehicle system 60. The other piece of information is the number of the partition P in which data from each in-vehicle system 60 should be saved.
[0041] Under these conditions, when the CPU 20 of the central ECU 10 receives a write request from the in-vehicle system 60, it selects a partition P in which to store data as follows. First, the CPU 20 refers to the specific identifier and the management list transmitted from the in-vehicle system 60. Then, the CPU 20 identifies the partition P in the management list that corresponds to the specific identifier. After that, the CPU 20 stores the data for which there is a write request in the identified partition P. Such a processing method may be adopted.
[0042] The method of setting the partitions P in the first memory 21 is not limited to the example of the embodiment. The method of setting the partitions P may be any method that satisfies the following specified conditions. The specified conditions are as follows. The first memory 21 includes at least two partitions P. One of the two partitions P is capable of storing data corresponding to the operation of the in-vehicle system 60 to which a functional safety level lower than a predetermined specific level is set. The other of the two partitions P is capable of storing data corresponding to the operation of the in-vehicle system 60 to which a functional safety level equal to or higher than a specific level is set. The specific level is a level higher than the lowest functional safety level. If these specified conditions are satisfied, the method of assigning the functional safety level to be stored in each partition P may be changed from the example of the embodiment. In addition, if the specified conditions are satisfied, the number of partitions P set in the first memory 21 may be changed from the example of the embodiment.
[0043] As described above, the number of partitions P set in the first memory 21 is not limited to the example of the above embodiment. For example, five partitions P may be provided corresponding to the five functional safety levels. That is, a partition P may be provided for each functional safety level. In this case, in addition to the first partition P1, the second partition P2, and the third partition P3, a first additional partition and a second additional partition are provided in the first memory 21. The first partition P1 is a storage area dedicated to the in-vehicle system 60 set to the lowest functional safety level. The third partition P3 is a storage area dedicated to the in-vehicle system 60 set to the highest functional safety level. The remaining three partitions P are storage areas dedicated to the in-vehicle systems 60 with different functional safety levels. Even when five partitions P are set in this way, a specific identifier or a management list may be configured so that each partition P can be distinguished from each other.
[0044] The method of allocating the functional safety level to be stored in each partition P is not limited to the example of the above embodiment. For example, in the case where three partitions P are provided as in the above embodiment, the functional safety level to be stored in the third partition P3 may be set to "ASIL-C" in addition to "ASIL-D". That is, it is not essential to dedicate the third partition P3 to the in-vehicle system 60 having the highest functional safety level. For example, if the number of times that the in-vehicle system 60 of "ASIL-C" writes data is considerably small, the following situation is unlikely to occur. That situation is that the writing of data by the in-vehicle system 60 of "ASIL-C" becomes a hindrance to the writing of data by the in-vehicle system 60 of "ASIL-D". Therefore, if it is known in advance that the number of times that the in-vehicle system 60 of "ASIL-C" writes data is considerably small, both the data of "ASIL-C" and the data of "ASIL-D" may be set to be stored in the same partition P.
[0045] It is not essential that the first partition P1 is dedicated to the in-vehicle system 60 with the lowest functional safety level. For example, in addition to "QM," "ASIL-A" may be set as the functional safety level to be stored in the first partition P1. As described in the above modification, such a setting is possible if it is known in advance that the number of times data is written by the in-vehicle system 60 with "QM" is significantly small.
[0046] The number and method of defining the functional safety levels are not limited to those in the above embodiment. It is sufficient that two or more functional safety levels are defined. The central ECU 10 may store an application A that operates the in-vehicle device 90. The central ECU 10 itself may constitute an in-vehicle system 60 together with the in-vehicle device 90 to be controlled. In this case, the CPU 20 of the central ECU 10 may store data generated in response to the operation of the in-vehicle device 90 in an appropriate partition P in the first memory 21.
[0047] In the central ECU 10, a single memory may serve as both the first memory 21 and the second memory 22. In this case, the single memory may be provided with an area for storing various programs describing the processes to be executed by the CPU 20, in addition to an area for storing data from each in-vehicle system 60.
[0048] The configuration of the processing circuit 12 in the central ECU 10 is not limited to the example of the above embodiment. The processing circuit 12 may have any of the following configurations (a) to (c), provided that it is provided with a storage unit and an execution unit as described below. The storage unit satisfies the above-mentioned predetermined conditions. The execution unit stores data in accordance with the operation of the in-vehicle system 60 in a partition P. At this time, the execution unit selects a partition P that is predetermined in correspondence with a functional safety level as the target for storing data.
[0049] (a) The processing circuitry 12 includes one or more processors that execute various processes according to a computer program. The processor includes a CPU and memory such as RAM and ROM. The memory stores program codes or instructions configured to cause the CPU to execute processes. Memory, i.e., computer-readable media, includes any available media that can be accessed by a general-purpose or special-purpose computer.
[0050] (b) The processing circuit 12 includes one or more dedicated hardware circuits for executing various processes. Examples of the dedicated hardware circuits include application specific integrated circuits, i.e., ASIC and FPGA. ASIC is an abbreviation for "Application Specific Integrated Circuit." FPGA is an abbreviation for "Field Programmable Gate Array."
[0051] (c) The processing circuitry 12 includes a processor that executes some of the various processes in accordance with a computer program, and a dedicated hardware circuit that executes the remaining processes among the various processes.
[0052] The processing circuit 72 of each base ECU 70 may have any of the above configurations (a) to (c), provided that the processing circuit 72 can appropriately control the in-vehicle device 90 to be controlled and can transmit a data write request to the central ECU 10. [Explanation of symbols]
[0053] P…Partition P1: First partition P2: Second partition P3: Third partition 10…Central ECU 20…CPU 21…First memory 60…In-vehicle systems 61…First system 62…Second system 63…Third System 100…Vehicle
Claims
1. An execution unit and a storage unit, The execution unit stores in the storage unit data corresponding to an operation of each in-vehicle system for which one of a plurality of functional safety levels is preset; the storage unit has a first partition and a second partition that are assigned in advance; the first partition is capable of storing data corresponding to an operation of an in-vehicle system to which a functional safety level lower than a predetermined specific level is set; The second partition is capable of storing data according to the operation of an in-vehicle system for which a functional safety level equal to or higher than the specific level is set. A storage management device for a vehicle.
2. There are three or more functional safety levels: the first partition is an area dedicated to data corresponding to the operation of an in-vehicle system to which the lowest functional safety level is set; The second partition is an area dedicated to data corresponding to the operation of any of the in-vehicle systems except for the in-vehicle system having the lowest functional safety level.
2. The vehicle storage management device according to claim 1.
3. There are three or more functional safety levels: the storage unit further includes a third partition that is pre-allocated; The third partition is an area dedicated to data corresponding to the operation of an in-vehicle system having the highest functional safety level.
3. The vehicle storage management device according to claim 1 or 2.
Citation Information
Patent Citations
Vehicle controller
JP2014193690A
Electronic control device and stack area use monitoring method
JP2017016410A
Method for the coexistence of software having different safety levels in a multicore processor system
US20150212952A1
In-vehicle control device
WO2017056725A1
Vehicle control device
JP2022065218A
