Information processing device, information processing program, and information processing method

Abstract

To acquire information on an update time from actual file data stored in a storage section while suppressing the storage section from reaching the end of its life prematurely.SOLUTION: An information processing device includes an execution section and a storage section. The storage section can store file data having metadata, which contains information on an update time and a data size, and actual file data by dividing the metadata and the actual file data into different data blocks. The execution section determines whether or not a data size of file data to be updated is the same as the data size of the file data already stored in the storage section. When the data size is the same, the execution section updates the actual file data without updating the metadata. The execution section updates by adding the information on the update time to the actual file data when updating the actual file data without updating the metadata.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing program, and an information processing method. [Background technology]

[0002] The information processing device of Patent Document 1 includes an execution unit and a storage unit. The execution unit stores, in the storage unit, metadata including information on the update time and data size of the data, and file data including actual file data. At this time, the execution unit divides the metadata and the actual file data into separate data blocks and stores them in the storage unit. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-197787 Summary of the Invention [Problem to be solved by the invention]

[0004] In an information processing device such as that disclosed in Patent Document 1, at least two data blocks are rewritten to store metadata and actual file data each time file data is updated. In an information processing device such as that disclosed in Patent Document 1, the minimum unit for rewriting is two data blocks, so the number of writes to the storage unit tends to be high. As a result, there is a risk that the storage unit will reach the end of its life prematurely. [Means for solving the problem]

[0005] An information processing device for solving the above problem comprises an execution unit and a memory unit, wherein the memory unit is capable of storing file data having metadata and actual file data including information on update time and data size by dividing the metadata and the actual file data into different data blocks, and the execution unit determines whether the data size of the file data to be updated is the same as the data size of the file data already stored in the memory unit, and if the data sizes are the same, updates the actual file data without updating the metadata, and when updating the actual file data without updating the metadata, updates the actual file data by inserting information on the update time into the actual file data.

[0006] An information processing program for solving the above problem is targeted at an information processing device having an execution unit and a memory unit, wherein the memory unit is capable of storing file data having metadata and actual file data including information on update time and data size by dividing the metadata and the actual file data into different data blocks, and causes the execution unit to determine whether the data size of the file data to be updated is the same as the data size of the file data already stored in the memory unit, and if the data sizes are the same, update the actual file data without updating the metadata, and when updating the actual file data without updating the metadata, update the actual file data by inserting information on the update time into the actual file data.

[0007] An information processing method for solving the above problem targets an information processing device having an execution unit and a memory unit, wherein the memory unit is capable of storing file data having metadata and actual file data including information on update time and data size by dividing the metadata and the actual file data into different data blocks, and the execution unit determines whether the data size of the file data to be updated is the same as the data size of the file data already stored in the memory unit, and if the data sizes are the same, updates the actual file data without updating the metadata, and when updating the actual file data without updating the metadata, updates the actual file data by inserting information on the update time into the actual file data. [Effects of the Invention]

[0008] According to the above configuration, it is possible to prevent the storage unit from reaching the end of its life prematurely, while obtaining update time information from the actual file data stored in the storage unit. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic configuration diagram of a vehicle. [Figure 2] 10 is a flowchart showing storage control. [Figure 3] 10 is a flowchart showing read control. DETAILED DESCRIPTION OF THE INVENTION

[0010] <Vehicle Overview> An embodiment of the present invention will now be described with reference to Figures 1 to 3. First, a schematic configuration of a vehicle 100 will be described.

[0011] 1, the vehicle 100 includes a central ECU 10, a meter ECU 20, a multimedia ECU 30, an advanced driving assistance ECU 40, and a DCM 50. The vehicle 100 also includes a first external bus 61, a second external bus 62, a third external bus 63, and a fourth external bus 64. "ECU" is an abbreviation for Electronic Control Unit. "DCM" is an abbreviation for Data Communication Module.

[0012] The central ECU 10 controls the entire vehicle 100. The central ECU 10 includes a CPU 11, a ROM 12, a RAM 13, and a storage 14. The central ECU 10 also includes a communication I / F 15, an input / output I / F 16, and an internal bus 17. The internal bus 17 connects the CPU 11, the ROM 12, the RAM 13, the storage 14, the communication I / F 15, and the input / output I / F 16 so that they can communicate with each other. The ROM 12 stores various programs and various data in advance. The ROM 12 also stores an information processing program 12A in advance as one of the various programs. The RAM 13 is a volatile memory. The RAM 13 temporarily stores various programs and various data. The CPU 11 uses the RAM 13 as a work area and executes various processes by reading the programs in the ROM 12. The CPU 11 also executes various processes in the information processing method by reading the information processing program 12A. In this embodiment, the CPU 11 is an execution unit, and the central ECU 10 is an information processing device.

[0013] The storage 14 can store various programs and various data. The storage 14 is an electrically rewritable nonvolatile memory. The storage 14 is a NAND-type flash memory. An example of the storage 14 is an eMMC (embedded multi-media card). The storage 14 has a maximum number of writes. Here, the number of writes to the storage 14 corresponds to the number of times some data 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. The maximum number of writes to the storage 14 is the number of times data can be written to one memory cell. Therefore, the total capacity that can be written to the storage 14, including data overwrites, is the product of the memory cell capacity, the number of memory cells, and the number of writes that can be made. In this embodiment, the storage 14 is a memory unit.

[0014] The communication I / F 15 is an interface for connecting with the meter ECU 20, the multimedia ECU 30, the advanced driving assistance ECU 40, and the DCM 50. The communication I / F 15 also functions as an interface for connecting with an engine ECU, a transmission ECU, a body ECU, etc. (not shown). The input / output I / F 16 is an interface for connecting with a group of sensors and a group of devices provided in the vehicle 100.

[0015] The DCM 50 is connected to the communication I / F 15 of the central ECU 10 via a first external bus 61. The DCM 50 is capable of wireless communication with devices outside the vehicle 100 via a wireless communication network (not shown). Therefore, the central ECU 10 is capable of wireless communication with devices outside the vehicle 100 via the first external bus 61 and the DCM 50.

[0016] The meter ECU 20 executes processes related to various meters, including an odometer 71, which will be described later. The meter ECU 20 includes a CPU 21, a ROM 22, a RAM 23, and a storage 24. The meter ECU 20 also includes a communication I / F 25, an input / output I / F 26, and an internal bus 27. The internal bus 27 connects the CPU 21, the ROM 22, the RAM 23, the storage 24, the communication I / F 25, and the input / output I / F 26 so that they can communicate with each other. The ROM 22 stores various programs and various data in advance. The RAM 23 is a volatile memory. The RAM 23 temporarily stores various programs and various data. The CPU 21 executes various processes by reading out programs from the ROM 22, using the RAM 23 as a working area.

[0017] The storage 24 can store various programs and various data. The storage 24 is an electrically rewritable nonvolatile memory. The storage 24 is a NOR-type flash memory. Here, the above-mentioned storage 14 is a NAND-type flash memory. Therefore, the upper limit number of writes predetermined for the storage 24, which is a NOR-type flash memory, is one order of magnitude larger than the upper limit number of writes predetermined for the storage 14.

[0018] The communication I / F 25 is an interface for connecting to the central ECU 10. The communication I / F 25 is connected to the communication I / F 15 of the central ECU 10 via a second external bus 62. Therefore, the meter ECU 20 can communicate with the central ECU 10. The input / output I / F 26 is an interface for connecting to a group of sensors and a group of devices provided in the vehicle 100.

[0019] The multimedia ECU 30 controls a navigation device, an audio device, etc. (not shown). The multimedia ECU 30 is connected to the communication I / F 15 of the central ECU 10 via a third external bus 63. The internal configuration of the multimedia ECU 30 is generally similar to that of the meter ECU 20, and therefore a description thereof will be omitted. The advanced driving assistance ECU 40 executes various applications to realize various driving assistance functions. The various applications include an application for following a vehicle traveling ahead of the vehicle 100 while maintaining a constant distance from the vehicle ahead, and an application for automatically applying the brakes to mitigate damage caused by a collision with the vehicle 100. The advanced driving assistance ECU 40 is connected to the communication I / F 15 of the central ECU 10 via a fourth external bus 64. The internal configuration of the advanced driving assistance ECU 40 is generally similar to that of the meter ECU 20, and therefore a description thereof will be omitted.

[0020] The vehicle 100 is equipped with a sensor group made up of a plurality of sensors. One of the sensors making up the sensor group is an odometer 71. The odometer 71 detects a total mileage TDD of the vehicle 100. The total mileage TDD is the total distance traveled by the vehicle 100 from the time of its manufacture to the present time. The odometer 71 is connected to the input / output I / F 26 of the meter ECU 20.

[0021] The CPU 11 of the central ECU 10 acquires various data from the meter ECU 20, the multimedia ECU 30, the advanced driving assistance ECU 40, the DCM 50, etc. at predetermined control cycles. The various data includes the total mileage (TDD) and the like.

[0022] <Memory Control> Next, the storage control executed by the CPU 11 of the central ECU 10 will be described with reference to Fig. 2. The CPU 11 of the central ECU 10 executes the storage control every time it acquires various types of data. At this time, the CPU 11 of the central ECU 10 executes the storage control for each of the same types of data. In this embodiment, the CPU 11 of the central ECU 10 executes the storage control by reading out the information processing program 12A. Note that, as an example, the storage control when the CPU 11 acquires the total mileage TDD via the meter ECU 20 will be described below.

[0023] 2, when the CPU 11 of the central ECU 10 starts storage control, it executes the process of step S11. In step S11, the CPU 11 determines whether or not this is the first storage control for the acquired data, for example, the total mileage TDD. For example, if the total mileage TDD is not stored in the storage 14, the CPU 11 determines that this is the first storage control for the acquired total mileage TDD. In step S11, if the CPU 11 determines that this is the first storage control (S11: YES), the CPU 11 proceeds to the process of step S21.

[0024] In step S21, the CPU 11 divides the acquired total mileage TDD into data blocks of a predetermined size as file data and stores the divided data in the storage 14. Here, the file data includes actual file data and metadata including information on the update time and data size. Specifically, the CPU 11 stores the actual file data including the acquired total mileage TDD in, for example, a first data block in the storage 14. The CPU 11 also stores metadata including information on the update time, which is the time when the total mileage TDD was stored, and information on the data size corresponding to the total mileage TDD, in a second data block in the storage 14. In other words, the storage 14 can divide and store the metadata and actual file data in different data blocks. After step S21, the CPU 11 ends the current storage control.

[0025] On the other hand, if the CPU 11 determines in step S11 that this is not the first storage control, that is, that this is the second or subsequent storage control (S11: NO), the CPU 11 advances the process to step S12.

[0026] In step S12, the CPU 11 determines whether the data size of the acquired file data of the total mileage TDD is the same as the data size of the file data of the total mileage TDD already stored in the storage 14. In other words, the processing of step S12 is processing to determine whether the data size of the file data to be updated is the same as the data size of the file data already stored in the storage unit. As a specific example, if the absolute value of the difference in data size between the two file data is equal to or less than a predetermined threshold, the CPU 11 determines that the data sizes of the two file data are the same. In step S12, if the CPU 11 determines that the data sizes of the two file data are the same (S12: YES), the CPU 11 proceeds to the processing of step S22.

[0027] In step S22, when updating the file data of the acquired total mileage TDD, the CPU 11 updates only the actual file data stored in the storage 14 without updating the metadata stored in the storage 14. When updating the actual file data in this way, the CPU 11 updates the actual file data stored in the storage 14 by adding information about the acquired total mileage TDD and information about the update time, which is the time when the total mileage TDD was stored. At this time, the CPU 11 updates the actual file data stored in the storage 14 by adding information about the update time to the end of the actual file data. After step S22, the CPU 11 ends the current storage control.

[0028] On the other hand, if the CPU 11 determines in step S12 that the data sizes of the two file data are different (S12: NO), the CPU 11 advances the process to step S23.

[0029] In step S23, when updating the file data of the acquired total mileage TDD, the CPU 11 updates both the metadata and the actual file data stored in the storage 14. That is, the CPU 11 updates the actual file data stored in the storage 14 by adding information about the acquired total mileage TDD. The CPU 11 also updates the metadata stored in the storage 14 by adding information about the update time, which is the time when the total mileage TDD was stored, and information about the data size corresponding to the total mileage TDD. After step S23, the CPU 11 ends the current storage control.

[0030] <Read Control> Next, the read control executed by the CPU 11 of the central ECU 10 will be described with reference to Fig. 3. The CPU 11 of the central ECU 10 executes the read control every time a request is made to acquire various file data stored in the storage 14. At this time, the CPU 11 of the central ECU 10 executes the read control for each file data of the same type. In this embodiment, the CPU 11 of the central ECU 10 executes the read control by reading out the information processing program 12A. Note that, as an example, the read control when acquiring file data of the total mileage TDD stored in the storage 14 will be described below.

[0031] 3, when the CPU 11 of the central ECU 10 starts read control, it executes the process of step S61. In step S61, the CPU 11 determines whether the file data acquired from the storage 14 has been stored with the same data size. For example, if the update time in the actual file data of the file data stored in the storage 14 is later than the update time in the metadata, the CPU 11 determines that the file data acquired from the storage 14 has been stored with the same data size. In step S61, if the CPU 11 determines that the file data has been stored with the same data size (S61: YES), the CPU 11 proceeds to the process of step S71.

[0032] In step S71, the CPU 11 accesses the actual file data of the file data stored in the storage 14, thereby obtaining information on the total mileage TDD and the update time from the actual file data. That is, the CPU 11 obtains the update time in the actual file data as the most recent update time. The CPU 11 also accesses the metadata of the file data stored in the storage 14, thereby obtaining information on the data size from the metadata. After step S71, the CPU 11 ends the current read control.

[0033] On the other hand, if the CPU 11 determines in step S61 that the file data has been stored as a different data size (S61: NO), the CPU 11 advances the process to step S72.

[0034] In step S72, the CPU 11 accesses the actual file data of the file data stored in the storage 14, thereby acquiring information on the total mileage TDD from the actual file data. The CPU 11 also accesses the metadata of the file data stored in the storage 14, thereby acquiring information on the update time and data size from the metadata. That is, the CPU 11 acquires the update time in the metadata as the most recent update time. After step S72, the CPU 11 ends the current read control.

[0035] <Operation of this embodiment> For example, it is assumed that the CPU 11 repeatedly acquires the total mileage TDD via the meter ECU 20, thereby repeatedly executing storage control for the total mileage TDD. At this time, if the data size of the file data of the repeatedly acquired total mileage TDD is the same, for example, an affirmative determination is made in step S12 of the storage control, and the process proceeds to step S22. Then, in step S22, when updating the file data of the acquired total mileage TDD, only the actual file data stored in the storage 14 is updated without updating the metadata stored in the storage 14. When the actual file data is updated as described above, information on the acquired total mileage TDD and information on the update time, which is the time when the total mileage TDD was stored, are inserted into the actual file data stored in the storage 14.

[0036] <Effects of this embodiment> (1) According to this embodiment, if it is determined in step S12 of the storage control that the data size of the file data is the same, only the actual file data stored in the storage 14 is updated in step S22. Therefore, the smallest unit of data blocks in the storage 14 that are rewritten when the file data is updated is one. This reduces the number of times the data blocks in the storage 14 are rewritten, thereby preventing the storage 14 from reaching the end of its life prematurely. Moreover, since the actual file data to be updated includes information about the update time, the information about the update time can be obtained from the actual file data stored in the storage 14 by read control.

[0037] (2) In step S22, when updating the real file data, the CPU 11 updates the real file data by adding update time information to the end of the real file data stored in the storage 14. As a result, the address of other data in the real file data, for example, the total mileage TDD, does not change depending on whether or not update time information is added to the real file data stored in the storage 14. As a result, adding update time information to the real file data and updating it does not involve a change in address designation for reading other data in the real file data.

[0038] (3) In the storage control, for example, if the data sizes of the file data of the total mileage TDD that are repeatedly acquired are different, a negative determination is made in step S12 of the storage control, and the process proceeds to step S23. Then, in step S23, when updating the acquired file data of the total mileage TDD, the CPU 11 updates both the metadata and the actual file data stored in the storage 14. Therefore, if it is determined in step S12 of the storage control that the data sizes of the file data are different, the update time information and data size information included in the metadata stored in the storage 14 are updated. As a result, the update time and data size information can be acquired from the metadata stored in the storage 14 by the read control.

[0039] <Example of change> This embodiment can be modified as follows: This embodiment and the following modifications can be combined and implemented within the scope of technical compatibility.

[0040] In the above embodiment, the storage control may be changed. For example, the method of updating the file data may be changed in step S22. As a specific example, when updating only the actual file data without updating the metadata stored in the storage 14, the CPU 11 may update the actual file data by inserting information about the update time at the beginning of the sentence in the actual file data stored in the storage 14.

[0041] For example, in step S23, the way in which the file data is updated may be changed. As a specific example, similar to step S22, when updating the file data of the acquired total mileage TDD, the CPU 11 may update only the actual file data stored in the storage 14 without updating the metadata stored in the storage 14. Even in this case, in read control, the CPU 11 can access the actual file data of the file data stored in the storage 14 and acquire information on the total mileage TDD and the update time from the actual file data. Furthermore, the CPU 11 may acquire the data size of the file data by analyzing the file data acquired as described above.

[0042] In the above embodiment, the configuration of the vehicle 100 may be changed. For example, the information processing device is not limited to the central ECU 10. As a specific example, instead of the central ECU 10, the CPU 21 of the meter ECU 20 may execute various processes in the information processing method by executing the information processing program 12A stored in the ROM 22. That is, the central ECU 10, the meter ECU 20, the multimedia ECU 30, the advanced driving assistance ECU 40, etc. may be adopted as the information processing device.

[0043] For example, the execution unit and the storage unit may be located in different ECUs. As a specific example, the CPU 11 of the central ECU 10 may be the execution unit, and the storage 24 of the meter ECU 20 may be the storage unit. In this case, the central ECU 10 and the meter ECU 20 are the information processing devices. [Explanation of symbols]

[0044] 10...Central ECU, 11...CPU, 12...ROM, 12A...Information processing program, 13...RAM, 14...Storage, 15...Communication I / F, 16...Input / output I / F, 17...Internal bus, 20...Meter ECU, 21...CPU, 22...ROM, 23...RAM, 24...Storage, 25...Communication I / F, 26...Input / output I / F, 27...Internal bus, 30...Multimedia ECU, 40...Advanced driving assistance ECU, 50...DCM, 61...First external bus, 62...Second external bus, 63...Third external bus, 64...Fourth external bus, 71...Odometer, 100...Vehicle.

Claims

1. An execution unit and a storage unit, the storage unit is capable of storing file data having metadata including information on update time and data size and actual file data by dividing the metadata and the actual file data into different data blocks; The execution unit: determining whether the data size of the file data to be updated is the same as the data size of the file data already stored in the storage unit; If the data size is the same, updating the actual file data without updating the metadata; When updating the actual file data without updating the metadata, updating the actual file data by inserting information about the update time into the actual file data; Run Information processing device.

2. The execution unit: When updating the actual file data without updating the metadata, the update time information is added to the end of the actual file data. Run The information processing device according to claim 1 .

3. The execution unit: If the data sizes are different, updating both the metadata and the actual file data; Run 3. The information processing device according to claim 1.

4. The present invention is directed to an information processing device including an execution unit and a storage unit, the storage unit is capable of storing file data having metadata including information on update time and data size and actual file data by dividing the metadata and the actual file data into different data blocks; The execution unit, determining whether the data size of the file data to be updated is the same as the data size of the file data already stored in the storage unit; If the data size is the same, updating the actual file data without updating the metadata; When updating the actual file data without updating the metadata, updating the actual file data by inserting information about the update time into the actual file data; Run Information processing program.

5. The present invention is directed to an information processing device including an execution unit and a storage unit, the storage unit is capable of storing file data having metadata including information on update time and data size and actual file data by dividing the metadata and the actual file data into different data blocks; The execution unit: determining whether the data size of the file data to be updated is the same as the data size of the file data already stored in the storage unit; If the data size is the same, updating the actual file data without updating the metadata; When updating the actual file data without updating the metadata, updating the actual file data by inserting information about the update time into the actual file data; Run Information processing methods.

Images