Vehicle memory management system, memory management program, and memory management method

Abstract

To reduce a potential for deletion of an application despite the intention.SOLUTION: A storage 20 includes a basic dynamic partition 30 which is allocated in advance as a storage region in which data is deleted when a prescribed time passes after the data is stored, and a basic static partition 21 which is allocated in advance as a storage region in which the data is not deleted even after the lapse of the prescribed time. A CPU is configured to: delete the data from the basic dynamic partition 30 when the prescribed time passes after the data is stored in the basic dynamic partition 30; allocate, when a request is made to install a new application, a part of the basic dynamic partition 30 as an additional static partition 31A in which data stored therein is not deleted even after the prescribed time passes; and store the new application in the additional static partition 31A.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] This invention relates to a memory management system for a vehicle, a memory management program, and a memory management method.

Background Art

[0002] Patent Document 1 discloses a management system for a storage device. In this management system, dedicated partitions for each user are set in the storage device so that a plurality of users can use the common storage device. Each partition is restricted from being accessed so that other users cannot change the stored content.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a storage device mounted on a vehicle, data that requires prohibition of deletion, such as various applications, is stored. In order to prevent accidental deletion of such data, it is conceivable to construct a dedicated partition with access restrictions in the storage device as in Patent Document 1. However, if there are only dedicated partitions with access restrictions, when new data is downloaded, the downloaded data cannot be written to the storage device. Therefore, it is conceivable to secure a shared partition that can be freely written without access restrictions separately from the dedicated partition with access restrictions. And in managing such a shared partition, it is conceivable to delete the stored data when a certain period of time has elapsed after storing the data so that the pre-allocated capacity can be efficiently reused.

[0005] At this point, applications may be downloaded as new data. As mentioned above, applications are essential data for them to perform their functions, and therefore their deletion should be prohibited. However, if these applications are stored on a shared partition, there is a risk that they may be deleted from the storage device after a certain period of time. [Means for solving the problem]

[0006] A vehicle memory management system for solving the above problems comprises an execution device and a memory device, the memory device having a dynamic partition pre-allocated as a memory area where data is erased after a predetermined time has elapsed since the data was stored, and a static partition pre-allocated as a memory area where the contents of the memory are not erased even after the predetermined time has elapsed, the execution device erases the data from the dynamic partition after the predetermined time has elapsed since the data was stored in the dynamic partition, and when there is a request to install a new application, it reallocates a part of the dynamic partition to the static partition and stores the new application in the static partition.

[0007] A memory management program for solving the above problems is a program for a vehicle memory management system comprising an execution device and a memory device, wherein the memory device has a dynamic partition pre-allocated as a memory area where data is erased when a predetermined time has elapsed since the data was stored, and a static partition pre-allocated as a memory area where the contents of the storage are not erased even after the predetermined time has elapsed, and the program causes the execution device to erase data from the dynamic partition when the predetermined time has elapsed since the data was stored in the dynamic partition, and, when there is a request to install a new application, to reallocate a part of the dynamic partition to the static partition and store the new application in the static partition.

[0008] A memory management method for solving the above problems is a memory management method for a vehicle, comprising an execution device and a storage device, wherein the storage device has a dynamic partition pre-allocated as a storage area where data is erased when a predetermined time has elapsed since the data was stored, and a static partition pre-allocated as a storage area where the contents of the storage are not erased even after the predetermined time has elapsed, wherein the execution device erases the data from the dynamic partition when the predetermined time has elapsed since the data was stored in the dynamic partition, and when there is a request to install a new application, it reallocates a part of the dynamic partition to the static partition and stores the new application in the static partition.

[0009] According to the technical concepts described above, by reallocating a portion of the dynamic partition to a static partition, it is possible to retain a dynamic partition that erases data at set intervals while continuously storing new applications. Therefore, the risk of newly installed applications being erased against the user's intentions can be reduced. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram of the vehicle's configuration. [Figure 2] This is a diagram showing the storage configuration. [Figure 3] This is a sequence diagram showing the storage management flow. [Figure 4] This is a sequence diagram showing the storage management flow. [Modes for carrying out the invention]

[0011] Hereinafter, one embodiment of a vehicle memory management system will be described with reference to the drawings. <Overall vehicle configuration> As shown in Figure 1, the vehicle 100 comprises a central control unit 10, a plurality of specific control units 90, and a data communication module 102. The central control unit 10 is a control unit that comprehensively controls the entire vehicle 100. Each specific control unit 90 is a control unit that controls a specific on-board device among a plurality of on-board devices. An example of an on-board device is the engine, which is the power source for the vehicle 100. Another example of an on-board device is a hydraulic brake system. The central control unit 10 and the plurality of specific control units 90 can communicate with each other via an external bus 104. The data communication module 102 can communicate with an external server 200 via an external communication network 202. The central control unit 10 and the data communication module 102 can communicate with each other via an external bus 106. That is, the central control unit 10 can communicate with the external server 200 through the data communication module 102.

[0012] Vehicle 100 is equipped with a display 80. The display 80 is located inside the vehicle. The display 80 is connected to the control unit 10 by wire or wireless connection. The display 80 can communicate with the control unit 10. The display 80 displays various information based on command signals from the control unit 10. The display 80 is a so-called touch panel type. That is, the display 80 also functions as an input device that accepts information input from the outside. The display 80 transmits the input information to the control unit 10.

[0013] Vehicle 100 is equipped with multiple information acquisition devices 85. In Figure 1, one of the multiple information acquisition devices 85 is shown as a representative example. The information acquisition devices 85 are devices that acquire various types of information about vehicle 100. These types of information include information on the surroundings of vehicle 100, information on the driving status of vehicle 100, and information on the operating status of on-board devices. An example of an information acquisition device 85 is a camera that takes images of the area around vehicle 100. Another example of an information acquisition device 85 is a vehicle speed sensor that detects the driving speed of vehicle 100. Another example of an information acquisition device 85 is a brake pressure sensor that detects the hydraulic pressure of the brake system. Each information acquisition device 85 is connected to the control unit 10 by wire or wireless. Each information acquisition device 85 repeatedly transmits a signal to the control unit 10 corresponding to the information it has acquired.

[0014] <Overall configuration of the central control system> The integrated control unit 10 comprises a CPU 11, storage 20, RAM 12, and a real-time clock 13. The CPU 11 constitutes the execution unit. The storage 20 is a NAND-type non-volatile memory. The storage 20 constitutes a storage device. The storage 20 stores multiple applications. These applications are various programs, such as control or management programs. The CPU 11 executes the applications stored in the storage 20. In this way, the CPU 11 realizes various processes. The RAM 12 is a volatile storage medium that temporarily stores data when the CPU 11 is performing processing. The real-time clock 13 is a circuit that generates date and time information. The CPU 11, storage 20, RAM 12, and real-time clock 13 can communicate with each other via the internal bus 15. The integrated control unit 10, including the CPU 11 and storage 20, constitutes the storage management system of the vehicle 100. Although not shown in the diagram, each specific control unit 90 also includes a CPU and storage, similar to the integrated control unit 10.

[0015] <Storage> Storage 20 has two main types of partitions. One type of partition is a static partition, which is pre-allocated as a storage area whose contents will not be erased even after a predetermined time T has elapsed. The other type of partition is a dynamic partition, which is pre-allocated as a storage area where data will be erased after a predetermined time T has elapsed since the data was stored. The storage capacity occupied by these two types of partitions may change between the time vehicle 100 is shipped from the factory and after vehicle 100 has been shipped. This will be discussed later. Due to the nature of the static partition described above, data written to the static partition is basically permanently stored without being erased. However, the contents of the static partition may be erased by a dealer or other facility during maintenance or inspection of vehicle 100. The predetermined time T is set as the time during which the capacity of the dynamic partition can be efficiently reused. The predetermined time T is, for example, several days to several months.

[0016] The configuration of the storage 20 at the time the vehicle 100 is shipped from the factory, i.e., in its initial state, will be described. As shown in Figure 2, at the time the vehicle 100 is shipped, the storage 20 has a basic static partition 21 and a basic dynamic partition 30.

[0017] The basic static partition 21 is a storage area that is allocated as a static partition at the time of shipment of the vehicle 100. The capacity of the basic static partition 21 is the first capacity. This first capacity remains unchanged over time. The first capacity is, for example, one-third of the total storage capacity of storage 20.

[0018] Applications installed before vehicle 100 is shipped are referred to as pre-shipment applications. At the time of vehicle 100's shipment, multiple pre-shipment applications are stored in the basic static partition 21. The basic static partition 21 is further divided into sections for each of these pre-shipment applications. The storage area for each pre-shipment application is a dedicated area for storing the pre-shipment application itself and the data generated as a result of the execution of that pre-shipment application. One example of a pre-shipment application is an application for following a vehicle while maintaining a constant distance from the vehicle in front. Another example of a pre-shipment application is an application for automatically applying the brakes to mitigate collision damage to vehicle 100. Some pre-shipment applications are recording applications, such as one that records the hydraulic pressure of the brake system when vehicle 100 brakes suddenly in storage 20. Each pre-shipment application stored in the basic static partition 21 has a unique identification number in its header.

[0019] The basic dynamic partition 30 is a storage area assigned as a dynamic partition at the time of shipment of the vehicle 100. The capacity of the basic dynamic partition 30 is the second capacity. This second capacity remains unchanged over time. The second capacity is, for example, two-thirds of the total storage capacity of the storage 20.

[0020] A part of the basic dynamic partition 30 is a variable area 31. This variable area 31 is an area that can be reassigned from a dynamic partition to a static partition. A predetermined capacity is assigned to the variable area 31. This capacity remains unchanged over time. Hereinafter, the static partition reassigned from the dynamic partition to the static partition is referred to as an additional static partition 31A. The part of the basic dynamic partition 30 excluding the variable area 31 is an invariant area 32. The invariant area 32 is an area that cannot be reassigned from a dynamic partition to a static partition. A predetermined specified capacity is assigned to the invariant area 32. This specified capacity remains unchanged over time. Therefore, even when a part or all of the variable area 31 is reassigned to the additional static partition 31A, the capacity of the entire dynamic partition after the assignment is not less than the specified capacity. The specified capacity is defined as the minimum capacity that needs to be left as a dynamic partition. The specified capacity is, for example, one-third of the total storage capacity of the storage 20.

[0021] [[ID=PR8]]<Management table> At the time of shipment of the vehicle 100, the storage 20 stores a management table in the basic static partition 21. The management table is a table that determines the storage destination of data generated in response to the execution of an application. Specifically, the management table is a table representing the correspondence between the identification number of the application and the storage destination of the data generated in response to the execution of the application.

[0022] At the time of vehicle 100's shipment, i.e., in its initial state, the only applications registered in the management table are pre-shipment applications. For most pre-shipment applications, the data generated in response to the execution of the application is stored in the basic static partition 21. However, for some pre-shipment applications, the data generated in response to the execution of the application is stored in a dynamic partition.

[0023] A new application may be installed after vehicle 100 has been shipped. In this case, as described below, the CPU 11 stores the new application in storage 20. When the CPU 11 stores the new application in storage 20, it updates the management table. At this time, the CPU 11 sets the storage location for the data generated in response to the execution of the new application to a dynamic partition. Each time the CPU 11 stores a new application in storage 20, the number of applications registered in the management table increases.

[0024] <Overview of Memory Management Processing> After the vehicle 100 is shipped, the CPU 11 is capable of executing memory management processing. Memory management processing is the process by which the CPU 11 manages the storage area of ​​the storage 20. The CPU 11 implements each of the memory management processes by executing a dedicated application for memory management processing that the storage 20 stores in the basic static partition 21.

[0025] Memory management processing includes basic processing, installation processing, post-shipment application processing, and pre-shipment application processing. In basic processing, CPU 11 stores certain data in a dynamic partition and then erases that data from the dynamic partition after a specified time T has elapsed.

[0026] When a user requests the installation of a new application, CPU 11 performs the installation process. During the installation process, CPU 11 reallocates a portion of the basic dynamic partition 30 to an additional static partition 31A. The variable area 31 is the target of this reallocation by CPU 11. In other words, CPU 11 ensures that the capacity of the dynamic partition after reallocation is equal to or greater than the specified capacity. When creating the additional static partition 31A, CPU 11 allocates only the capacity of the new application to the additional static partition 31A. After reallocating the storage area, CPU 11 stores the new application in the newly created additional static partition 31A. This new application is a post-shipment application, which is installed after the vehicle 100 is shipped.

[0027] After the installation of a new post-shipment application, the CPU 11 becomes capable of executing that application. The CPU 11 then performs post-shipment application processing in conjunction with the execution of the post-shipment application. During post-shipment application processing, the CPU 11 stores the data generated in response to the execution of the post-shipment application in the dynamic partition at that time. In other words, the CPU 11 stores the data generated in response to the execution of the post-shipment application in the immutable area 32, or in the variable area 31 that has not yet been allocated to the additional static partition 31A.

[0028] In response to this, CPU 11 performs pre-shipment application processing in conjunction with the execution of the pre-shipment application. During pre-shipment application processing, CPU 11 stores the data generated in accordance with the execution of the pre-shipment application in an area of ​​the basic static partition 21 that is dedicated to the pre-shipment application being executed. In addition, during pre-shipment application processing, CPU 11 may also store some of the generated data in the dynamic partition at that time, depending on the type of pre-shipment application.

[0029] <Specific details of the installation process> The operation of this embodiment will be explained by describing the management flow of the storage 20 associated with memory management processing. In the following description, it will be assumed that the vehicle 100 has been shipped.

[0030] As shown in Figure 3, when the CPU 11 receives a request from the user to install a new application via the display 80 (step S40), it performs the installation process. In the installation process, the CPU 11 performs the processes in steps S31, S32, S33, S34, S35, and S36. Following these processes, the storage 20 performs the functions in steps S51 and S52. The display 80 also performs the functions in steps S41 and S42.

[0031] When CPU 11 starts the installation process, it first performs the process in step S31. In step S31, CPU 11 confirms the amount of storage space required to store the new application desired by the user in storage 20 (hereinafter referred to as the new application's capacity). At this time, CPU 11 obtains information about the new application's capacity from the external server 200. After this, CPU 11 proceeds to step S32.

[0032] In step S32, the CPU 11 sends a command signal to the display 80 to display capacity information. The capacity information includes the capacity of the new application, the remaining capacity of the variable area 31 at the time of execution of step S32, and an icon asking whether the final installation is necessary. The remaining portion is the part of the variable area 31 that has not yet been changed to the additional static partition 31A at the time of execution of step S32. Since the CPU 11 manages the partition configuration of the storage 20, it is always aware of the remaining capacity of the variable area 31. Regarding the processing in step S32, if the capacity of the new application is larger than the remaining capacity of the variable area 31, the CPU 11 will include information in the capacity information indicating that the new application cannot be installed due to insufficient capacity. In this case, the installation of the new application will be canceled.

[0033] Following the processing in step S32 described above, the display 80 displays capacity information in step S41. If the user then requests installation, the display 80 sends a signal to the CPU 11 instructing it to start the installation in step S42. If the user does not request installation, the CPU 11 cancels the subsequent processing.

[0034] When the CPU 11 receives a signal to start the installation, it performs the process in step S33. In step S33, the CPU 11 sends a command signal to the storage 20 instructing it to rebuild the basic dynamic partition 30. Rebuilding the basic dynamic partition 30 involves reallocating the storage area of ​​the variable area 31 that corresponds to the capacity of the new application to the additional static partition 31A. Upon receiving this command signal, in step S51, the storage 20 reallocates part or all of the remaining portion of the variable area 31 to the additional static partition 31A. As a result, the storage area of ​​the basic dynamic partition 30 that is actually a dynamic partition becomes smaller than before the reallocation.

[0035] After the processing in step S33, the CPU 11 performs the processing in step S34. In step S34, the CPU 11 obtains a new application from the external server 200. After this, in step S35, the CPU 11 sends the new application and a command signal to the storage 20 to store the application in the additional static partition 31A created by the instruction in step S33. At this time, the CPU 11 adds an identification number specific to the new application to the header of the new application.

[0036] Following the processing in step S35 described above, in step S52, the storage 20 stores the new application, the post-shipment application, in the additional static partition 31A. After this, the CPU 11 performs the processing in step S36. In step S36, the CPU 11 updates the management table. That is, the CPU 11 sets a dynamic partition as the storage location for data generated as a result of the execution of the post-shipment application stored in the additional static partition 31A.

[0037] Although Figure 3 illustrates only one cycle of the installation process, the CPU 11 executes the above installation process whenever there is a request to install a new application. As a result, if there is any remaining space in the variable area 31 that is needed for installation, the number of post-shipment applications will increase each time the CPU 11 performs the installation process.

[0038] <Specific details of basic processing> The CPU 11 performs basic processing when data to be stored in the dynamic partition of the storage 20 is generated as a result of executing one of the various applications. As shown in Figure 4, the CPU 11 performs the processes in steps S11 and S12 in the basic processing. Following these processes, the storage 20 performs the functions in steps S21 and S22.

[0039] When the CPU 11 starts basic processing, it first performs the process in step S11. Specifically, in step S11, the CPU 11 sends the data to be stored and a command signal to store the data in the dynamic partition at that time to the storage 20. At this time, the CPU 11 adds the date and time at that time to the data to be stored. In response to the processing in step S11, the storage 20 stores the above data in the dynamic partition at that time in step S21. After a specified time T has elapsed since the above data was stored in the storage 20, the CPU 11 performs the process in step S12. In step S12, the CPU 11 sends a command signal to the storage 20 to erase the above data. In response to this command signal, the storage 20 erases the stored data from the dynamic partition in step S22. The CPU 11 can determine that the specified time T has elapsed by, for example, referring to the date and time contained in the data. Although Figure 4 illustrates only one cycle of the basic processing, the CPU 11 executes the above basic processing each time data to be stored in the dynamic partition of the storage 20 is generated.

[0040] <Specific details of post-shipment application processing> When the CPU 11 detects that any of the execution conditions for post-shipment applications stored in the storage 20 have been met, it performs post-shipment application processing on the post-shipment application for which the execution conditions have been met. In post-shipment application processing, the CPU 11 performs the processes in steps S61 and S62. Following the processing in step S62, the storage 20 performs the function in step S71.

[0041] When CPU 11 starts processing post-shipment applications, it first performs the process in step S61. In step S61, CPU 11 executes the post-shipment application whose execution conditions have been met. When data is generated as a result of the execution of this post-shipment application, CPU 11 performs the process in step S62. In step S62, CPU 11 determines that the storage location for the generated data is the dynamic partition at that time by referring to the management table. Then, CPU 11 sends the generated data and a command signal to the storage 20 to store that data in the dynamic partition at that time. In response to the process in step S62, storage 20 stores the data generated as a result of the execution of the post-shipment application in the dynamic partition at that time in step S71. Note that the process in step S62 described above is an example of step S11 of the basic processing. Also, the process in step S71 described above is an example of step S21. Figure 4 shows only one cycle of post-shipment application processing, but CPU 11 executes the above post-shipment application processing each time the execution conditions for the post-shipment application are met.

[0042] <Specific details of pre-shipment application processing> When the CPU 11 detects that any of the pre-shipment applications stored in the storage 20 has met the execution conditions, it performs pre-shipment application processing on the pre-shipment application whose execution conditions have been met. In pre-shipment application processing, the CPU 11 performs the processes in steps S81 and S82. Following the processing in step S82, the storage 20 performs the function in step S91.

[0043] When CPU 11 starts processing a pre-shipment application, it first performs the process in step S81. In step S81, CPU 11 executes the pre-shipment application whose execution conditions have been met. When data is generated as a result of the execution of this pre-shipment application, CPU 11 performs the process in step S82. In step S82, CPU 11 sends the generated data and a command signal to the storage 20 to store the data in a predetermined partition. CPU 11 selects either the basic static partition 21 or the dynamic partition at that time as the predetermined partition by referring to the management table. Following the process in step S82, in step S91, storage 20 stores the data generated as a result of the execution of the pre-shipment application in the predetermined partition. Note that the process in step S82 when CPU 11 selects a dynamic partition as the predetermined partition is an example of step S11 in the basic processing. Also, in that case, step S91 is an example of step S21. Although Figure 4 illustrates only one cycle of pre-shipment application processing, the CPU 11 executes the above pre-shipment application processing each time the execution conditions for the pre-shipment application are met.

[0044] <Effects of the Embodiment> (1) When a request is made to install a new application, the CPU 11 reconfigures the storage area of ​​the storage 20. Specifically, the CPU 11 reallocates a portion of the variable area 31 of the basic dynamic partition 30 to an additional static partition 31A. The CPU 11 then stores the new application, the post-shipment application, in the additional static partition 31A. This allows the storage 20 to continue storing the post-shipment application while retaining a dynamic partition in the storage 20 that erases data every specified time T. Therefore, the risk of the post-shipment application being erased against the user's intentions is reduced.

[0045] (2) When the CPU 11 creates an additional static partition 31A on the basic dynamic partition 30, it allocates only the capacity of the newly installed application to the additional static partition 31A. Therefore, the capacity of each additional static partition 31A can be made small. Consequently, even if a certain number of additional static partitions 31A are created, a large amount of space can be secured for the dynamic partition after allocation.

[0046] (3) When the CPU 11 reallocates a portion of the basic dynamic partition 30 to an additional static partition 31A, it targets only the variable area 31. In other words, the CPU 11 ensures that the capacity of the dynamic partition after allocation is equal to or greater than the specified capacity. Therefore, if the specified capacity is set to a reasonably large amount as in this embodiment, it is possible to prevent the dynamic partition from becoming excessively small after the partition allocation.

[0047] <Example of changes> The above embodiment can be modified as follows. The above embodiment and the following modifications can be combined and implemented to the extent that they do not contradict each other technically.

[0048] The sizes of the first capacity, second capacity, and specified capacity are not limited to the examples of the above embodiments. The above capacities can be appropriately determined to ensure that the necessary capacity is secured for each partition, according to the content of the data to be stored in each partition.

[0049] The capacity allocated to the additional static partition 31A may be greater than the capacity of the post-shipment application to be stored in the additional static partition 31A. Furthermore, data generated in response to the execution of the post-shipment application may be stored in the additional static partition 31A. In this case, the management table should be configured to enable this configuration.

[0050] The immutable area 32 may be abolished. The entire area of ​​the basic dynamic partition 30 may be made into the variable area 31. In this case, no specified capacity will be set. Even when this configuration is adopted, if the capacity allocated to the additional static partition 31A is limited to the capacity of the application, there is little risk that the dynamic partition will become excessively small after the allocation of the additional static partition 31A. Furthermore, even if the basic dynamic partition 30 is allocated to the additional static partition 31A, each application can be executed if the following condition is met. The above condition is that a dedicated area for storing data generated in accordance with the execution of the application is reserved in the additional static partition 31A or the basic static partition 21.

[0051] For example, the capacity allocated to the additional static partition 31A may be changed for each post-shipment application according to user instructions. Furthermore, both an additional static partition 31A allocated only to the capacity of the post-shipment application and an additional static partition 31A allocated with a capacity greater than that of the post-shipment application may exist in the variable area 31. In this case, the capacity information displayed on the display 80 in step S41 should include an icon for setting the capacity. Then, according to user instructions, the user's desired capacity should be allocated to the additional static partition 31A for each post-shipment application.

[0052] The input device that receives input from the user is not limited to the display 80. Buttons or the like may be provided on the vehicle 100 as input devices. The storage of the specific control device 90 may be provided with static partitions and dynamic partitions similar to those in the above embodiment. The CPU of the specific control device 90 may then perform memory management processing.

[0053] The dynamic partition of storage 20 may be used as a temporary storage area when the CPU 11 performs processing. In this case, RAM 12 can be eliminated from the control unit 10. The storage 20 is not limited to the above embodiment, which consists of NAND-type non-volatile memory. For example, the entire storage medium, which combines non-volatile memory and other types of memory, may be treated as storage 20. Other types of memory include, for example, RAM and ROM. Even when such an embodiment is adopted, storage 20 only needs to include the static partitions and dynamic partitions defined in the above embodiment.

[0054] The configuration of the integrated control unit 10 is not limited to the examples of the above embodiment. The integrated control unit 10 comprises a storage device that functions similarly to the storage 20 of the above embodiment and an execution device that functions similarly to the above embodiment, and may have any of the following configurations (a) to (c).

[0055] (a) The central control unit 10 comprises one or more processors that perform various processes according to a computer program. The processors include a CPU and memory such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to perform the processes. The memory, i.e., computer-readable media, includes any available media that can be accessed by a general-purpose or dedicated computer.

[0056] (b) The central control unit 10 includes one or more dedicated hardware circuits that perform various processes. Examples of dedicated hardware circuits include application-specific integrated circuits, i.e., ASICs or FPGAs.

[0057] (c) The integrated control unit 10 includes a processor that executes a portion of the various processes according to a computer program, and dedicated hardware circuits that execute the remaining processes among the various processes. [Explanation of Symbols]

[0058] 11…CPU 20…Storage 21…Basic static partition 30…Basic Dynamic Partitioning 31... Variable region 32…Invariant domain 31A... Additional static partition

Claims

1. It comprises an execution device and a storage device, The storage device has a dynamic partition pre-allocated as a storage area where data is erased after a predetermined period of time has elapsed since the data was stored, and a static partition pre-allocated as a storage area where the contents of the storage are not erased even after the predetermined period of time has elapsed. The execution device is The data is stored in the dynamic partition and then deleted from the dynamic partition after a specified time has elapsed. When a request is made to install a new application, a portion of the dynamic partition is reallocated to the static partition, The new application is stored in the static partition, and the following is done: A vehicle memory management system.

2. The execution device is If such a request is made, the static partition shall be allocated with the capacity of the new application and the new application shall be stored in the static partition. When the aforementioned new application is executed, the data generated in response to the execution of the new application is stored in the dynamic partition. A vehicle memory management system according to claim 1.

3. When the execution device reallocates a portion of the dynamic partition to the static partition, it ensures that the capacity of the dynamic partition after reallocation is equal to or greater than a predetermined specified capacity. A vehicle memory management system according to claim 1 or 2.

4. A program for a vehicle memory management system comprising an execution device and a memory device, wherein the memory device has a dynamic partition pre-allocated as a memory area where data is erased after a predetermined period of time has elapsed since the data was stored, and a static partition pre-allocated as a memory area where the contents of the memory are not erased even after the predetermined period of time has elapsed, The execution device, The data is stored in the dynamic partition and then deleted from the dynamic partition after a specified time has elapsed. When a request is made to install a new application, a portion of the dynamic partition is reallocated to the static partition, To store the new application in the static partition and to execute it. Memory management program.

5. A storage management method for a vehicle storage management system comprising an execution device and a storage device, wherein the storage device has a dynamic partition pre-allocated as a storage area where data is erased when a predetermined time has elapsed since the data was stored, and a static partition pre-allocated as a storage area where the contents of the storage are not erased even after the predetermined time has elapsed, The execution device, The data is stored in the dynamic partition and then deleted from the dynamic partition after a specified time has elapsed. When a request is made to install a new application, a portion of the dynamic partition is reallocated to the static partition, To store the new application in the static partition and to execute Memory management methods.

Images