Vehicle information management device, information management program, and information management method

Abstract

To provide a vehicle information management device and an information management method configured to extend the time until a maximum write cycle limit is reached.SOLUTION: A vehicle 100 includes an overall control apparatus 10. A CPU 11 equipped in the overall control apparatus performs: writing data to a storage 13 during execution of applications; executing a determination as to whether a remaining write cycles of the storage 13 have become equal to or lower than a predetermined prescribed value; and reducing, when the determination is affirmative, a frequency of writing data to the storage 13 during the execution of the applications, in the entire applications as compared with a case in which the determination is negative.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This invention relates to a vehicle information management device, an information management program, and an information management method.

Background Art

[0002] The information processing device disclosed in Patent Document 1 includes a CPU and a memory. The CPU executes various software. Also, as the software is executed, the CPU writes various data to the memory. The CPU counts the number of write operations to the memory for each software during a specific period. Then, when the total number of write operations by all software reaches a specific number, the CPU changes the setting of the software with the most write operations during this specific period. Thereby, the CPU reduces the frequency of writing by the software with the most write operations.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Even if, as in Patent Document 1, the writing frequency of a specific software to the memory is reduced, other software still continues to write to the memory. Therefore, when considering the entire plurality of software, the writing frequency to the memory may not necessarily decrease.

Means for Solving the Problems

[0005] A vehicle information management device for solving the above problems includes an execution unit and a storage unit, and the storage unit Multiple applications for controlling the acceleration or braking of a vehicle, and multiple applications not related to the control of the acceleration or braking of the vehicle,The execution unit stores data in the memory unit in accordance with the execution of each application, and determines whether the remaining number of writes to the memory unit has fallen below a predetermined value, and if the determination is affirmative, Each of the multiple applications unrelated to the aforementioned control The frequency of writing data to the storage unit associated with the execution of the above is reduced compared to when the determination is negative.

[0006] An information management program for solving the above problem comprises an execution unit and a storage unit, Multiple applications for controlling the acceleration or braking of a vehicle, and multiple applications not related to the control of the acceleration or braking of the vehicle, The storage unit The A program for a vehicle information management device, wherein the execution unit writes data to the storage unit in accordance with the execution of each application, and determines whether the remaining number of writeable times to the storage unit has fallen below a predetermined value, and if the determination is affirmative, Each of the multiple applications unrelated to the aforementioned control The frequency of writing data to the storage unit in conjunction with the execution of is reduced compared to when the determination is negative, and the execution is performed.

[0007] An information management method for solving the above problem comprises an execution unit and a storage unit, Multiple applications for controlling the acceleration or braking of a vehicle, and multiple applications not related to the control of the acceleration or braking of the vehicle, The storage unit The A method for managing information using a vehicle information management device, wherein the execution unit writes data to the storage unit in accordance with the execution of each application, determines whether the remaining number of writes to the storage unit has fallen below a predetermined value, and if the determination is affirmative, Each of the multiple applications unrelated to the aforementioned control The frequency of writing data to the storage unit associated with the execution of is reduced compared to when the determination is negative, and the following is performed.

[0008] In each of the above technical concepts, when the remaining number of write cycles to the memory unit becomes low, the number of write cycles to the memory unit is reduced not only for applications with a high number of write cycles, but also for multiple applications as a whole. This extends the time it takes for the number of write cycles to reach the upper limit, even when the remaining number of write cycles to the memory unit is low. [Brief explanation of the drawing]

[0009] [Figure 1] This is a schematic diagram of the vehicle's configuration. [Figure 2] This is a sequence diagram illustrating the flow of data writing. [Figure 3] This is a flowchart illustrating the processing steps for the configuration process. [Figure 4] This is a flowchart illustrating the processing steps for the selection process. [Modes for carrying out the invention]

[0010] Hereinafter, one embodiment of a vehicle information management device and information management method will be described with reference to the drawings. <Overall vehicle configuration> As shown in Figure 1, the vehicle 100 is equipped with a main control unit 10 and a plurality of specific control units 90. The main 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 of the plurality of on-board devices 92. The on-board devices 92 include devices for accelerating or braking the vehicle 100. One of the plurality of on-board devices 92 is the engine that is the power source for the vehicle 100. Another of the plurality of on-board devices 92 is a hydraulic brake system. There are many other on-board devices 92 as well. The main control unit 10 and the plurality of specific control units 90 can communicate with each other via an external bus 104.

[0011] Vehicle 100 is equipped with a sensor group 80 consisting of multiple sensors. Sensors are devices that acquire various types of information. This information includes surrounding monitoring information for vehicle 100, information regarding the driving status of vehicle 100, and information regarding the operating status of the on-board device 92. One of the multiple sensors is an image sensor 81 built into the on-board camera. The image sensor 81 detects light. The camera uses the function of the image sensor 81 to image the area around vehicle 100. That is, the image captured by the camera includes data detected by the image sensor 81. One of the multiple sensors is a wheel speed sensor 82 that detects the rotational speed of the vehicle 100's wheels. The wheel speed sensor 82 is also a sensor that detects the vehicle 100's driving speed. One of the multiple sensors is a brake pressure sensor 83 that detects the hydraulic pressure of the brake system. The sensors also include devices that receive radio waves from outside vehicle 100. That is, one of the multiple sensors is a first receiver 84 that receives traffic information, including congestion information, from an external server. Furthermore, one of the multiple sensors is a second receiver 85 that receives information regarding the current position coordinates of the vehicle 100 from global positioning satellites. In addition to the above, the sensor group 80 includes various other sensors. Each sensor is connected to the control unit 10 by wire or wireless. Each sensor repeatedly transmits a signal to the control unit 10 corresponding to the information it has detected or received.

[0012] Vehicle 100 has a start switch 70. The start switch 70 is a switch that the occupant uses to instruct the vehicle 100 to start. The start switch 70 turns on or off in response to the occupant's operation. The start switch 70 transmits a signal to the control unit 10 according to the occupant's operation status.

[0013] <Overall configuration of the central control system> The integrated control unit 10 comprises a CPU 11, storage 13, and RAM 15. The CPU 11 is the execution unit. The storage 13 is an electrically rewritable non-volatile memory. The storage 13 is a memory unit. The RAM 15 is a volatile memory that temporarily stores data when the CPU 11 performs processing. The CPU 11, storage 13, and RAM 15 can communicate with each other via an internal bus 17. The integrated control unit 10, including the CPU 11 and storage 13, is a vehicle information management device. Although not shown in the figures, each specific control unit 90 also includes a CPU and storage, similar to the integrated control unit 10.

[0014] Storage 13 pre-stores multiple applications. These applications are various programs, such as control or management programs. The CPU 11 executes the applications stored in storage 13. In this way, the CPU 11 performs various processes. Each application is assigned a unique identification number.

[0015] <About the application> The multiple applications stored in storage 13 can be broadly classified into three types: multiple Type 1 applications, multiple Type 2 applications, and multiple Type 3 applications. Type 1 applications are applications for controlling the acceleration or braking of vehicle 100. These Type 1 applications are also applications that need to sequentially write various types of data to storage. Multiple Type 1 applications include applications that realize the functions of advanced driver assistance systems. Specifically, one of the multiple Type 1 applications is an application for following a vehicle while maintaining a constant distance from the vehicle in front. Another of the multiple Type 1 applications is an application for automatically applying the brakes to mitigate damage from a collision with vehicle 100. In addition to these, there are multiple other Type 1 applications. When a Type 1 application is executed, the CPU 11 writes data acquired by various sensors, such as camera images, vehicle speed, and brake hydraulic pressure, as well as previously calculated control target values, to storage 13. Based on this data, the CPU 11 requests acceleration and deceleration from the engine and brake system. Furthermore, Type 1 applications correspond to specific applications.

[0016] The second type of application is an application that has nothing to do with the control of acceleration or braking of the vehicle 100, and it is necessary to repeatedly write the data detected or received by the sensor into the storage 13 at a certain time interval. One of the multiple second-type applications is a driving scoring application for scoring the driving skills of the occupant. When this driving scoring application is executed, the CPU 11 repeatedly writes the captured image of the camera into the storage 13. One of the multiple second-type applications is a roughness monitoring application for monitoring the roughness of the road surface on which the vehicle 100 is traveling. When this roughness monitoring application is executed, the CPU 11 repeatedly writes the rotational speed of the wheel into the storage 13. The rotational speed of the wheel is an index indicating the roughness of the road surface. One of the multiple second-type applications is an application for displaying traffic jam information around the current position of the vehicle 100 on the display in the vehicle interior. When this traffic jam application is executed, the CPU 11 repeatedly writes the traffic jam information into the storage 13. In addition to these, there are multiple second-type applications.

[0017] <00​​​​​​​​​​The management unit 11B is capable of performing write operations. In a write operation, the management unit 11B writes data to the storage 13 in accordance with the execution of a Type 1 or Type 2 application by the request unit 11A. In a write operation, the management unit 11B also updates the write count for the storage 13. The write count corresponds to the number of times some kind of information, including data associated with the execution of an application, has been written to the same memory cell. Therefore, writing here includes not only writing information to an empty memory cell, but also overwriting the contents of a memory cell that already has information written to it. For example, if writes are performed to each memory cell sequentially, the write count will increase by one when all memory cells have been written to once. The management unit 11B stores the write count of the storage 13 from when it was new. The management unit 11B will update the value stored in the storage 13 as needed.

[0020] The management unit 11B can execute a setting process. The setting process is for setting a specified flag F. The specified flag F is a flag that specifies the generation mode when the request unit 11A generates data in conjunction with the execution of the application. As a prerequisite for setting the specified flag F, the management unit 11B performs a first determination and a second determination. In the first determination, the management unit 11B determines whether the remaining number of writes to the storage 13 (hereinafter simply referred to as the remaining number) KC has become less than or equal to a first specified value K1. In the second determination, the management unit 11B determines whether the remaining number KC has become less than or equal to a second specified value K2. The management unit 11B sets the specified flag F according to the results of these first and second determinations. The first specified value K1 is predetermined as the maximum value for which measures are required to increase the time until the number of writes to the storage 13 reaches the upper limit. The first specified value K1 is, for example, 20% of the upper limit. The second specified value K2 is a smaller value than the first specified value K1. The second specified value K2 is predetermined as the maximum value for which writing other than data necessary for the operation of the vehicle 100 is not permitted. The second specified value K2 is, for example, 10% of the maximum number of writes. Storage 13 stores the first specified value K1 and the second specified value K2 in advance. The maximum number of writes to storage 13 is the number of times that can be written to one memory cell or a predetermined memory frame. Therefore, the total capacity that can be written to storage 13, including data overwriting, is the number of memory cells or memory frames multiplied by the capacity of the memory cells or memory frames and the number of writes that can be performed. Storage 13 stores the maximum number of writes in advance.

[0021] The request unit 11A is capable of executing a selection process. The selection process is for selecting the data generation mode associated with the execution of an application. The management unit 11B specifies the generation mode to the request unit 11A by setting the designation flag F described above. In this way, if the first or second determination is affirmative, the management unit 11B reduces the frequency of data writing to the storage 13 by all applications stored in the storage 13 compared to the case where the first determination is negative. Specifically, if the first determination is affirmative and the second determination is negative, the management unit 11B lengthens the time interval between repeated data writings to the storage 13 associated with the execution of the application compared to the case where the first determination is negative. Furthermore, if the second determination is affirmative, the management unit 11B prohibits writing data to the storage 13 associated with the execution of the application. The management unit 11B imposes these write restrictions on applications other than Type 1 applications. In detail, the management unit 11B imposes write restrictions only on Type 2 applications.

[0022] <Specific processing steps for the writing process> The specific processing flow of the write operation will be explained. As a prerequisite, the request unit 11A generates data to be written to the storage 13 while the Type 1 or Type 2 application is running. Generating the data includes acquiring data detected or received by sensors mounted on the vehicle 100 at the required time intervals. Generating the data also includes calculating the control amount for the in-vehicle device 92.

[0023] As shown in Figure 2, in step S100, the request unit 11A generates one piece of data to be written to the storage 13, triggered, for example, by acquiring an image at a certain timing. After that, the request unit 11A performs the process in step S102. In step S102, the request unit 11A requests the management unit 11B to write the data. Upon receiving this request, the management unit 11B performs the write process. That is, in step S110, the management unit 11B writes the requested data to the storage 13. After that, in step S112, the management unit 11B updates the write count for the storage 13. Specifically, the management unit 11B calculates the new write count according to the process in step S112. Then, the management unit 11B adds the new write count to the previous value of the write count currently stored in the storage 13. Then, the management unit 11B overwrites the previous value with the new write count. The processes in steps S110 and S112 described above constitute the write process. The management unit 11B performs this write process once for each piece of data. Although only one cycle of the write process is shown here, the management unit 11B performs the write process every time there is a request to write data. In other words, if the request unit 11A repeatedly requests to write data, the management unit 11B repeats the write process. The request unit 11A may also run multiple applications in parallel. In this case as well, the management unit 11B sequentially performs the write process on each piece of data for which a write request has been made, so as to satisfy all write requests.

[0024] <Specific steps for the configuration process> The management unit 11B starts the setup process when the start switch 70 is switched from off to on. As shown in Figure 3, when the management unit 11B starts the setup process, it first performs the process in step S20. In step S20, the management unit 11B calculates the remaining number of writes KC. Specifically, the management unit 11B calculates the remaining number of writes KC as the value obtained by subtracting the number of writes currently stored by the storage 13 from the upper limit of writes stored by the storage 13. After this, the management unit 11B proceeds to step S22.

[0025] In step S22, the management unit 11B determines whether the remaining number of attempts KC is less than or equal to the second specified value K2. If the remaining number of attempts KC is greater than the second specified value K2 (step S22: NO), the management unit 11B proceeds to step S24.

[0026] In step S24, the management unit 11B determines whether the remaining number of operations KC is less than or equal to the first specified value K1. If the remaining number of operations KC is greater than the first specified value K1 (step S24: NO), the management unit 11B proceeds to step S30. In step S30, the management unit 11B sets the designation flag F to "1". A designation flag F of "1" means that there are no restrictions on writing data to the storage 13 in conjunction with the execution of the application. When the management unit 11B sets the designation flag F, it overwrites the value of the designation flag F currently stored in the storage 13. After executing the process in step S30, the management unit 11B terminates the series of settings processes.

[0027] On the other hand, in step S24, if the remaining number of operations KC is less than or equal to the first specified value K1 (step S24: YES), the management unit 11B proceeds to step S28. Then, in step S28, the management unit 11B sets the designation flag F to "2". A designation flag F of "2" means that it is necessary to reduce the frequency of data writing to the storage 13 associated with the execution of the application. After executing the process in step S28, the management unit 11B terminates the series of settings processes.

[0028] On the other hand, in step S22, if the remaining number of operations KC is less than or equal to the second specified value K2 (step S22: YES), the management unit 11B proceeds to step S26. In step S26, the management unit 11B sets the specified flag F to "3". A specified flag F of "3" means that writing data to the storage 13 in conjunction with the execution of the application is prohibited. After executing the process in step S26, the management unit 11B terminates the series of settings processes.

[0029] <Specific processing steps for selection> When the execution conditions for either a Type 1 application or a Type 2 application are met, the request unit 11A performs a selection process prior to the execution of the application whose execution conditions have been met.

[0030] As shown in Figure 4, when the request unit 11A starts the selection process, it first performs the process in step S70. In step S70, the request unit 11A determines whether the application whose execution conditions have been met is a Type 2 application. The request unit 11A makes this determination by referring to the management table stored in the storage 13. The management table is a table that shows the relationship between the application identification number and the type of application. As mentioned above, a Type 2 application is an application that is not related to the control of the acceleration or braking of the vehicle 100.

[0031] In step S70, if the application whose execution conditions have been met is a Type 2 application (step S70: YES), the request unit 11A proceeds to step S72. In step S72, the request unit 11A determines whether the specified flag F is "3". In step S72, if the specified flag F is not "3" (step S72: NO), the request unit 11A proceeds to step S74.

[0032] In step S74, the request unit 11A determines whether the specified flag F is "2". In step S72, if the specified flag F is not "2" (step S74: NO), the request unit 11A proceeds to step S80. In other words, the case in which the process proceeds to step S80 is when the specified flag F is "1".

[0033] In step S80, the request unit 11A selects normal mode as the data generation mode for the execution of the Type 2 application. As described above, the Type 2 application is an application that needs to repeatedly write data from the sensor to the storage 13 at regular time intervals. The normal mode described above is a mode that uses the base time as the specified time interval for writing to the storage 13. The base time is the writing time interval originally specified in the target application. Therefore, when normal mode is selected, the request unit 11A will execute the target application as usual when actually executing the application afterward. Note that the base time differs for each application. After executing the process in step S80, the request unit 11A terminates the selection process. Then, the request unit 11A executes the Type 2 application whose execution conditions have been met in normal mode.

[0034] On the other hand, in step S74, if the specified flag F is "2" (step S74: YES), the request unit 11A proceeds to step S78. In step S78, the request unit 11A selects reduction mode as the data generation mode for the execution of the application. Reduction mode is a mode in which the reduction time is used as the specified time mentioned above. When this reduction mode is selected, when the application is actually executed thereafter, the request unit 11A will replace the base time originally specified in the application with the reduction time and execute the application. In this embodiment, the request unit 11A sets the reduction time to a value obtained by multiplying the base time of the application in question by several times. That is, the reduction time is longer than the base time. After executing the process in step S78, the request unit 11A terminates the selection process. Then, the request unit 11A executes the Type 2 application whose execution conditions have been met in reduction mode.

[0035] Now, in step S72, if the specified flag F is "3" (step S72: YES), the request unit 11A proceeds to step S76. In step S76, the request unit 11A selects the prohibit mode as the data generation mode for the execution of the Type 2 application. When this prohibit mode is selected, when the application is actually executed afterward, the request unit 11A will cancel the generation of data originally specified in the application and execute the application. After executing the process in step S76, the request unit 11A terminates the selection process. Then, the request unit 11A executes the Type 2 application for which the execution conditions have been met in prohibit mode. Note that if the Type 2 application for which the execution conditions have been met has no function other than data generation, the execution of that application will effectively be canceled.

[0036] By the way, in step S70, if the application whose execution conditions have been met is a Type 1 application, the request unit 11A terminates the selection process. Then, the request unit 11A executes the Type 1 application as usual. In other words, the request unit 11A executes the Type 1 application, which is an application for controlling the acceleration or braking of the vehicle 100, as usual, regardless of the mode specified by the designation flag F. Therefore, the request unit 11A and, by extension, the management unit 11B reduce the frequency of data writing to the storage 13 or prohibit data writing only for Type 2 applications.

[0037] <Operation of the Embodiment> Each time the start switch 70 is switched from off to on, the management unit 11B sets a designated flag F according to the remaining number of times KC at that time. Regardless of the value set to designated flag F, the request unit 11A executes the first type application as usual. The management unit 11B then writes data to the storage 13 in response to a request from the request unit 11A. Meanwhile, the request unit 11A changes the data generation mode for the second type application depending on the value of designated flag F. Consequently, the frequency with which the management unit 11B writes data to the storage 13 also changes. This point will be described in detail below.

[0038] Now, let's assume that the remaining number of attempts KC is greater than the first specified value K1 (step S22: NO, step S24: NO). In this case, the management unit 11B sets the specified flag F to "1" (step S30). If the driving scoring application, which is one of the Type 2 applications, is to be executed under these circumstances, the request unit 11A selects normal mode (step S80). In this case, the management unit 11B writes the captured images to the storage 13 at the basic time interval of the driving scoring application in response to the request unit 11A's request. When the request unit 11A executes any of the other Type 2 applications, the management unit 11B also writes the necessary data to the storage 13 at the basic time interval of each application.

[0039] Now, suppose the number of writes to storage 13 gradually increases, and eventually the remaining number of writes KC becomes less than or equal to the first specified value K1 and greater than the second specified value K2 (step S22: NO, step S24: YES). In this case, the management unit 11B sets the specified flag F to "2" (step S28). When the driving scoring application is executed under these circumstances, the request unit 11A selects the reduced mode (step S78). In this case, the management unit 11B writes the captured images to storage 13 at time intervals longer than the basic time of the driving scoring application, in response to the request unit 11A's request. When the request unit 11A executes any other Type 2 application, the management unit 11B also writes the necessary data to storage 13 at time intervals longer than the basic time of each application. In this way, the management unit 11B lengthens the time interval for writing data for all Type 2 applications stored in storage 13. In other words, if the first determination is affirmative and the second determination is negative, the management unit 11B reduces the frequency of data writing to the storage 13 associated with the execution of each individual Type 2 application for all Type 2 applications, compared to the case where the first determination is negative.

[0040] Now, suppose the number of writes to storage 13 increases further, and the remaining number KC becomes less than or equal to the second specified value K2 (step S22: YES). In this case, the management unit 11B sets the specified flag F to "3" (step S26). When the operation scoring application is executed under these circumstances, the request unit 11A selects the prohibit mode (step S76). In this case, the management unit 11B does not write data to storage 13. The management unit 11B also does not write data to storage 13 when the request unit 11A executes any other Type 2 application. In this way, the management unit 11B prohibits data writing for all Type 2 applications stored in storage 13. That is, if the second judgment is affirmative, the management unit 11B reduces the frequency of data writing to storage 13 to zero for all Type 2 applications.

[0041] <Effects of the Embodiment> (1) In this embodiment, when the remaining number of writes KC decreases, the write frequency to storage 13 is reduced for all Type II applications, not just applications with a high number of writes. This reduces the frequency of data writing to storage 13 associated with the execution of individual applications for all applications stored in storage 13, including both Type I and Type II applications. This extends the time until the number of writes reaches the upper limit, even when the remaining number of writes KC decreases.

[0042] (2) In this embodiment, when the remaining number of KCs becomes somewhat small, the time interval between repeated data writings to the storage 13 is increased for Type 2 applications. This reduces the number of times data is written to the storage 13 over a certain period. In other words, the frequency of data writing to the storage 13 can be reduced.

[0043] (3) In this embodiment, when the remaining number of KCs becomes considerably low, data writing to storage 13 is prohibited for Type 2 applications. In this case, there will be no data writing to storage 13 associated with the execution of Type 2 applications. Therefore, the frequency of data writing when considering all applications stored in storage 13 can be effectively reduced. Note that Type 2 applications are applications that are not related to the control of acceleration or braking of the vehicle 100. Therefore, even if data writing to storage 13 associated with the execution of Type 2 applications is eliminated, there will be no effect on the basic motion performance of the vehicle 100, such as driving and stopping.

[0044] (4) In this embodiment, no data writing restrictions are imposed on Type 1 applications. That is, even when the number of remaining KCs decreases, data necessary for the operation of the vehicle 100 can be written to the storage 13 as usual. On top of that, data writing restrictions are imposed on Type 2 applications. By adopting this configuration, the overall data writing frequency for all applications stored in the storage 13 can be reduced without reducing the writing frequency of data necessary for the operation of the vehicle 100.

[0045] <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.

[0046] The timing of the configuration process is not limited to when the start switch 70 is turned on. For example, the configuration process may be performed at predetermined time intervals. The configuration process should be performed at an appropriate time so that appropriate write restrictions can be imposed while minimizing the number of times the configuration process is executed. In addition, minimizing the number of times the configuration process is executed contributes to reducing the processing load on the CPU 11.

[0047] The information to be set in the specified flag F is not limited to the example of the above embodiment. Any information that allows the specified generation mode to be identified is sufficient. The method for determining the reduction time is not limited to the examples of the above embodiments. The reduction time only needs to be longer than the base time of the application in question. The method for determining the reduction time may be changed for each application. For example, the shorter the base time of an application, the larger the amount of change from the base time may be.

[0048] The method of reducing the data writing frequency using the reduced mode is not limited to lengthening the time interval between data writings, as in the above embodiment. For example, the data capacity per data item written to the storage 13 in conjunction with the execution of the application may be reduced compared to the normal mode. The data capacity written to the storage 13 when the application is executed in normal mode is called the basic capacity. In reduced mode, for example, it is conceivable to generate data with a capacity of several tens of percent of this basic capacity and write it to the storage 13. If the data to be written is, for example, an image, the data capacity can be reduced by lowering the image quality. Here, reducing the data capacity per data item means reducing the number of memory cells that are written to. If the number of memory cells targeted for writing at one time is small, the data writing frequency for a given memory cell is reduced. Reducing the data writing frequency at the memory cell level in this way is also effective in reducing the data writing frequency to the storage 13. Note that the modified version of this example of reducing data capacity is effective not only for applications where the time interval between data writings to the storage 13 is constant, but also for applications where the time interval is not constant.

[0049] • The method of increasing the time interval between data writing, as in the above embodiment, is referred to as the first method. • The method of reducing the data capacity per data item, as in the above modification example, is referred to as the second method. When executing a certain application in reduced mode, both the first method and the second method may be applied to that application. That is, the time interval between data writing may be increased, and the data capacity per data item may be reduced. The application may be configured to select which of the first and second methods to use. An appropriate method should be implemented considering the type of data generated during the execution of the application.

[0050] In the above embodiment, a two-stage write restriction was set using a first and a second determination. Alternatively, the write restriction may be set in three or more stages. Furthermore, the frequency of data writing to the storage 13 may be gradually reduced. The contents of the setting process and selection process may be appropriately modified to realize such configurations.

[0051] • Write restrictions may be limited to a single level. In other words, the second check and the prohibit mode may be eliminated. • When limiting write access to only one level, a prohibit mode may be used instead of a reduction mode. That is, when the first judgment is positive, data writing to storage 13 may be prohibited. In other words, when the first judgment is positive, the frequency of writing to storage 13 may be reduced to zero.

[0052] The number of stages in which write restrictions are set may vary depending on the application. For example, consider the case where two stages of write restrictions are set, as in the embodiment described above. In this case, two stages of write restrictions may be set for one of the multiple Type II applications, and only one stage of write restrictions may be set for the remaining Type II applications. Furthermore, the generation mode may be switched from reduction mode to prohibition mode for only one application, depending on the second determination.

[0053] The applications subject to write restrictions are not limited to Type 2 applications. For example, write restrictions may be imposed on some of several Type 1 applications. Write restrictions can also be imposed on Type 1 applications as long as they do not affect the basic dynamic performance of the vehicle 100. For example, if a Type 1 application subject to write restrictions repeatedly writes data from sensors or other data to the storage 13, the above-described first or second method can be applied. Write restrictions may also be imposed on Type 3 applications. For example, if there is a Type 3 application that writes data from sensors to the storage 13 at inconsistent time intervals, the above-described second method may be applied to that Type 3 application. Also, for example, if there is a Type 3 application that repeatedly generates some kind of data, even if it is not data obtained from sensors, the above-described first or second method may be applied to that Type 3 application. Furthermore, any means other than the first and second methods that can reduce the frequency of writing to the storage 13 may be adopted as appropriate.

[0054] It is not mandatory to impose write restrictions on all Type II applications. Even if write restrictions are not imposed on all Type II applications, imposing write restrictions on multiple applications, including Type I and Type III applications, is preferable in order to achieve the following: The above is to reduce the frequency of data writing to storage 13 by all the multiple applications stored on storage 13.

[0055] When setting multiple levels of write restrictions, instead of switching the data generation mode, the number of applications subject to write restrictions may be increased. For example, when the first judgment is positive, only some of the multiple Type 2 applications may be subject to reduced mode, and when the second judgment is positive, all Type 2 applications may be subject to reduced mode. In this way, the number of applications subject to write restrictions may be increased while using the same generation mode.

[0056] The definition of the first specified value K1 is not limited to the example of the embodiment described above. An appropriate value may be defined as the threshold at which write restrictions need to be applied. The same applies to the second specified value K2. Even when write restrictions are applied in three or more stages, the threshold for each stage may be set as appropriate.

[0057] • The Type 2 application is not limited to the examples of the above embodiments. Any application that satisfies the following conditions may be treated as a Type 2 application. That is, a Type 2 application is an application that is not related to the control of the acceleration or braking of the vehicle 100 and that needs to repeatedly write data detected or received by the sensor to the storage 13 at a certain time interval. Other Type 2 applications may be used in place of, or in addition to, the Type 2 applications exemplified in the above embodiments.

[0058] • The first type of application is not limited to the examples of the embodiments described above. Any application that controls the acceleration or braking of the vehicle 100 may be treated as a first type of application. Other first type of applications may be used in place of, or in addition to, the first type of applications exemplified in the embodiments described above.

[0059] Multiple partitions may be provided in storage 13. Furthermore, write restrictions similar to those in the above embodiment may be imposed based on the remaining number of KCs relative to the maximum number of writes per partition.

[0060] • When making the first determination, instead of using the remaining number of turns KC itself, an indicator representing the remaining number of turns KC may be used. An example of such an indicator is the value obtained by dividing the remaining number of turns KC by the upper limit. When using such an indicator, the first specified value K1 should be converted to a value corresponding to that indicator. Using such an indicator and converted value, it may be determined whether the remaining number of turns KC has become less than or equal to the first specified value K1. Thus, the form of the first determination is not limited to the example of the above embodiment, and is acceptable as long as it can determine whether the remaining number of turns KC has become less than or equal to the first specified value K1. The same applies to the second determination.

[0061] The sensor is not limited to the examples of the above embodiments. The sensor can be any device that acquires information. Other sensors may be used in place of, or in addition to, the sensors exemplified in the above embodiments. A sound sensor that detects sound may be used as the sensor. A radar that uses the reflection of radio waves to detect obstacles may be used as the sensor.

[0062] The vehicle 100 may have a motor generator as an on-board device 92 that serves as the drive source for the vehicle 100, either in place of or in addition to the engine. The same setting and selection processes as in the above embodiment may be performed in the specific control device 90.

[0063] 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 unit that functions in the same manner as in the above embodiment and an execution unit that functions in the same manner as in the above embodiment, and may have any of the following configurations (a) to (c).

[0064] (a) The integrated 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.

[0065] (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.

[0066] (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.

[0067] <Note> The above embodiments and their modifications include the configurations described in the following appendix. [Note 1] A vehicle information management device comprising an execution unit and a storage unit, wherein the storage unit stores a plurality of applications, and the execution unit writes data to the storage unit in conjunction with the execution of each application, determines whether the remaining number of writeable times to the storage unit has fallen below a predetermined value, and if the determination is affirmative, reduces the frequency of data writing to the storage unit in conjunction with the execution of each application across the plurality of applications compared to when the determination is negative.

[0068] [Note 2] The vehicle information management device according to [Note 1], wherein one of the multiple applications repeatedly writes data acquired by a sensor mounted on the vehicle in connection with the execution of the application to the storage unit at predetermined time intervals, and the execution unit makes the predetermined time longer than when the determination is negative if the determination is positive.

[0069] [Note 3] The vehicle information management device according to [Note 1] or [Note 2], wherein one of the plurality of applications repeatedly writes data acquired by a sensor mounted on the vehicle to the storage unit in connection with the execution of the application, and the execution unit reduces the data capacity per piece of data written to the storage unit in connection with the execution of the application compared to when the determination is negative.

[0070] [Note 4] The vehicle information management device according to any one of [Note 1] to [Note 3], wherein one of the plurality of applications is a specific application that controls the acceleration or braking of the vehicle in conjunction with the execution of the application, and the execution unit reduces the frequency of writing data to the storage unit in conjunction with the execution of applications other than the case in which the determination is negative, for applications other than the specific application.

[0071] [Note 5] When the specified value is set as the first specified value, the execution unit prohibits writing data to the storage unit in connection with the execution of at least one application if the remaining number of writeable times to the storage unit falls below a second specified value which is a value smaller than the first specified value. This is the vehicle information management device according to any one of [Note 1] to [Note 4]. [Explanation of symbols]

[0072] 10... Control System 11…CPU 13…Storage 80... Sensor group 100...vehicles

Claims

1. It comprises an execution unit and a storage unit, The aforementioned storage unit is It stores multiple applications for controlling the acceleration or braking of a vehicle, and multiple applications that are not related to the control of the acceleration or braking of the vehicle. The execution unit is, The process involves writing data to the storage unit in conjunction with the execution of individual applications, The process involves determining whether the remaining number of write cycles to the memory unit has fallen below a predetermined value, If the above determination is positive, the frequency of writing data to the storage unit associated with the execution of each of the multiple applications unrelated to the above control is reduced compared to when the above determination is negative. Vehicle information management device.

2. An application unrelated to the aforementioned control repeatedly writes data acquired by sensors mounted on the vehicle to the storage unit at predetermined time intervals in conjunction with the execution of the application. The execution unit, if the determination is positive, extends the specified time to be longer than when the determination is negative. The vehicle information management device according to claim 1.

3. An application unrelated to the aforementioned control repeatedly writes data acquired by sensors mounted on the vehicle to the storage unit in conjunction with the execution of the application. If the determination is positive, the execution unit reduces the data capacity per data item written to the storage unit in connection with the execution of the application compared to when the determination is negative. The vehicle information management device according to claim 1.

4. When the aforementioned specified value is set as the first specified value, If the remaining number of write cycles to the storage unit falls below a predetermined second value, which is smaller than the first predetermined value, the execution unit prohibits writing data to the storage unit for applications unrelated to the control, in connection with the execution of said applications. The vehicle information management device according to claim 1.

5. A program for a vehicle information management device comprising an execution unit and a storage unit, wherein the storage unit stores a plurality of applications for controlling the acceleration or braking of a vehicle and a plurality of applications unrelated to the control of the acceleration or braking of the vehicle, The execution unit, The process involves writing data to the storage unit in conjunction with the execution of individual applications, The process involves determining whether the remaining number of write cycles to the memory unit has fallen below a predetermined value, If the above determination is positive, the frequency of writing data to the storage unit associated with the execution of each of the multiple applications unrelated to the above control will be reduced compared to when the above determination is negative, and the following will be performed. Information management program.

6. An information management method using a vehicle information management device comprising an execution unit and a storage unit, wherein the storage unit stores a plurality of applications for controlling the acceleration or braking of a vehicle and a plurality of applications unrelated to the control of the acceleration or braking of the vehicle, The execution unit, The process involves writing data to the storage unit in conjunction with the execution of individual applications, The process involves determining whether the remaining number of write cycles to the memory unit has fallen below a predetermined value, If the above determination is positive, the frequency of writing data to the storage unit associated with the execution of each of the multiple applications unrelated to the above control is reduced compared to when the above determination is negative, and the following is performed: Information management method.

Images