Information processing device, information processing method, and information processing program
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- NEC PLATFROMS LTD
- Filing Date
- 2025-02-26
- Publication Date
- 2026-06-30
Smart Images
Figure 0007882559000001_ABST
Abstract
Description
Technical Field
[0004] , ,
[0005] , ,
[0001] The present invention relates to an information processing apparatus, an information processing method, and an information processing program. In particular, it relates to an information processing apparatus, an information processing method, and an information processing program that have a memory and perform self-fault diagnosis.
Background Art
[0002] Patent Document 1 discloses a technique for performing railway vehicle control by transferring fixed data stored in a ROM (Read Only Memory) to a RAM (Random Access Memory) and executing a program on the RAM. And Patent Document 1 also discloses a technique for detecting and correcting an error that occurs during data transfer from the ROM to the RAM.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] The following analysis is made from the perspective of the present invention. It is assumed that each disclosure of the above prior art documents is incorporated herein by reference.
[0005] <0000Patent Document 1 has a problem in that it cannot detect errors even if there are errors in the fixed data on the ROM itself. That is, since the ROM is read-only, if there are no problems with the initial operation of railway vehicle control using the fixed data on the ROM, it can be assumed that the fixed data on the ROM remains correct and fixed. However, due to physical shock to the ROM, the fixed data on the ROM may be rewritten and may contain errors. If the fixed data on the ROM has been rewritten in the first place, even if there are no problems with the data transfer of the fixed data, the data on the RAM will also be rewritten. In this case, even if the rewritten fixed data on the ROM and the rewritten data on the RAM are compared using the technology of Patent Document 1, no errors are detected.
[0006] Therefore, the present invention aims to provide an information processing device, an information processing method, and an information processing program that contribute to fault diagnosis, including the rewriting of fixed data stored in memory. [Means for solving the problem]
[0007] According to the first aspect of the present invention, A memory section for storing fixed data, A memory control unit that controls the memory unit, A test data calculation unit calculates and stores first test data from the fixed data when storing fixed data, and calculates second test data from the fixed data read by the memory control unit from the memory unit when fault diagnosis is performed. A fault determination unit compares the first inspection data with the second inspection data and reports a fault if the two do not match. An information processing device having the following is provided.
[0008] According to a second aspect of the present invention, The steps include: when storing fixed data in the memory section, calculating and saving first inspection data from said fixed data; The steps include calculating second test data from fixed data read from the memory unit during fault diagnosis, A step of comparing the first test data with the second test data and reporting a failure if the two do not match, An information processing method including this is provided.
[0009] According to a third aspect of the present invention, As an information processing device, the computer The process involves calculating and saving first inspection data from the fixed data when storing the fixed data in the memory section, The process involves calculating second test data from fixed data read from the memory unit during fault diagnosis, A process that compares the first test data with the second test data and reports a failure if the two do not match. An information processing program is provided to execute this. [Effects of the Invention]
[0010] According to each aspect of the present invention, an information processing device, an information processing method, and an information processing program are provided that contribute to fault diagnosis, including the rewriting of fixed data stored in memory. [Brief explanation of the drawing]
[0011] [Figure 1] This is a diagram to explain the general overview. [Figure 2] This figure shows an example of how fixed data is stored in the memory section. [Figure 3] This figure shows an example of data provision. [Figure 4] This figure shows an example of data provision under circumstances where fixed data has been overwritten and contains errors. [Figure 5] This figure shows an example of a fault diagnosis process. [Figure 6] This figure shows an example of the processing flow by an information processing device. [Figure 7] This figure shows an example of the processing flow by an information processing device. [Figure 8] This is a diagram showing a model for identifying the location of a fault. [Figure 9] This is a diagram showing an example of the configuration of the memory unit. [Figure 10] This is a diagram showing an example of a computer as an information processing apparatus.
Embodiments for Carrying out the Invention
[0012] Preferred embodiments of the present invention will be described in detail with reference to the drawings. Note that the reference numerals attached to the following description are for convenience of each element as an example to assist understanding, and are not intended to limit the present invention to the illustrated embodiments. Also, the connection lines between blocks in each figure include both bidirectional and unidirectional ones. Further, in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc. shown in the present application disclosure, although not explicitly shown, input ports and output ports exist at the input ends and output ends of each connection line respectively. The same applies to input / output interfaces.
[0013] [General Outline] First, the general outline of the present invention will be described. As shown in FIG. 1, the information processing apparatus 100 includes a memory unit 10, a memory control unit 20, an inspection data calculation unit 30, and a failure determination unit 40. The memory unit 10 stores fixed data. The memory control unit 20 controls the memory unit 10. The inspection data calculation unit 30 calculates and stores first inspection data from the fixed data when the fixed data is stored, and calculates second inspection data from the fixed data read by the memory control unit 20 from the memory unit 10 during failure diagnosis. The failure determination unit 40 compares the first inspection data and the second inspection data, and reports a failure when the two do not match.
[0014] According to the information processing device 100, fault diagnosis including rewriting of fixed data stored in the memory unit 10 is possible. That is, suppose that at the time of fault diagnosis, the fixed data stored in the memory unit 10 has been rewritten from the original data and contains errors. In this case, as part of the fault diagnosis, the information processing device 100 compares a first test data calculated and saved at the time the fixed data was stored with a second test data calculated from the fixed data read from the memory unit 10. Since the first test data calculated from the fixed data before rewriting is compared with the second test data calculated from the fixed data after rewriting, the two will no longer match. Therefore, the information processing device 100 will report a fault including rewriting of the fixed data stored in the memory unit 10.
[0015] It should be noted that the discrepancy between the first and second test data is not limited to cases where the fixed data has been rewritten. For example, if the memory control unit 20 fails to read the fixed data, the fixed data read by the memory control unit 20 may be rewritten even if the fixed data stored in the memory unit 10 has not been rewritten. In this case as well, the first and second test data will not match. However, whether the fixed data stored in the memory unit 10 has been rewritten (i.e., the memory unit 10 has failed) or the reading process by the memory control unit 20 has failed (i.e., the memory control unit 20 has failed), the information processing device 100 is still considered to have failed. At this point, some users may think that it is better to replace the information processing device 100 itself with a new one rather than spending time and money analyzing the failure in the information processing device 100 and repairing the faulty parts. For such users, it is unnecessary to determine whether the failure is in the memory unit 10 or the memory control unit 20. In other words, for some users, it may be sufficient if a failure of the information processing device 100 is reported.
[0016] On the other hand, in the conventional technology, for example, the technology described in Patent Document 1, it can be said that the fixed data on the ROM is compared with the data on the RAM read from the ROM. In this case, if the fixed data on the ROM has been overwritten, the data on the RAM will naturally also have been overwritten. Therefore, in the conventional technology, no errors are detected when comparing the fixed data on the ROM with the data on the RAM.
[0017] [Embodiment 1] The information processing device 100 described above will be explained in more detail below, using an example.
[0018] Regarding fixed data, we assume that it is an application downloaded by a user's terminal device (user terminal) and used for service operation. In other words, the information processing device 100 is assumed to be a device that stores the original data of the application and provides a copy of the data in response to a request from the user terminal. Here, the original data of the application stored by the information processing device 100 is not usually rewritten unless there is a version upgrade or something similar. In other words, the data stored in the memory unit 10 can be said to be fixed. For this reason, the data stored in the memory unit 10 is referred to as "fixed data".
[0019] The memory unit 10 stores fixed data, assuming a physical storage medium such as a ROM (Read-Only Memory). The memory control unit 20 controls the memory unit 10 to write and read the fixed data. The test data calculation unit 30 calculates and stores first test data from the fixed data when the fixed data is stored, and calculates second test data from the fixed data read by the memory control unit 20 from the memory unit 10 during fault diagnosis. The fault determination unit 40 compares the first test data and the second test data and reports a fault if they do not match. The cache 50 temporarily stores copy data obtained by reading the fixed data.
[0020] Specifically, as shown in Figure 2, the memory unit 20 stores applications (fixed data) developed by the application vendor in the memory unit 10. At the same time, the test data calculation unit 30 calculates and stores first test data from the fixed data. The storage location for the first test data may be the memory unit 10 or a separate storage medium.
[0021] Under the conditions shown in Figure 2, the fixed data stored in the memory unit 10 is assumed to be correct and not overwritten. Whether or not the fixed data stored in the memory unit 10 is correct can be verified, for example, by comparing it with master data held by the application vendor or by conducting service operation tests.
[0022] Figure 3 shows an example of data provision. When an application request is received from a user terminal, as shown in Figure 3, the information processing device 100 has its memory control unit 20 read fixed data from the memory unit 10 and store it in the cache 50 as copy data. The information processing device 100 then processes the copy data stored in the cache 50, such as by packetizing it, and sends it to user A's terminal. User A's terminal then deploys the received copy data as an application. It should be assumed that, under the circumstances shown in Figure 3, the application is correctly deployed on user A's terminal and there is no hindrance to user A's service operation.
[0023] Figure 4 shows an example of data provision under circumstances where fixed data has been overwritten and contains errors. As shown in Figure 4, suppose user B also requests an application in order to operate a service using the application. However, suppose user B's terminal has problems such as being unable to properly deploy the application and is unable to use it for user B's service operation. When the information processing device 100 receives an error report from user B's terminal, it performs a self-fault diagnosis.
[0024] Specifically, as shown in Figure 5, the memory control unit 20 reads new fixed data from the memory unit 10, and the test data calculation unit 30 calculates second test data from the newly read fixed data. Then, the fault determination unit 40 compares the first test data and the second test data. Here, the fault determination unit 40 reports a fault if the two do not match.
[0025] The test data only needs to be capable of verifying the accuracy of the fixed data. For example, error detection codes such as CRC-16 (Cyclic Redundancy Check) can be used as test data. If CRC-16 is used, only 2 bytes of test data are needed for every 4KB of fixed data. Therefore, if CRC-16 is used, the memory area occupied by the test data can be kept to approximately 2 bytes / 4KB ≈ 0.05% for the memory section 10, whose essential role is to store the fixed data. In contrast, a typical DIMM (Dual Inline Memory Module) that supports ECC (Error Correcting Code) adds 8 bits for ECC to the 64 bits of data. If this is used as 8 bits of test data, the memory area occupied by the test data becomes 8 bits / 64 bits = 12.5%. However, this does not mean that using 8 bits for ECC as test data is not advisable. In other words, it is possible to select the type of test data to use according to the level of confidence required for verifying the accuracy of the fixed data. Regarding the calculation of the inspection data, since it uses existing technology, we will omit the explanation.
[0026] The following describes the processing flow by the information processing device 100. <When storing fixed data> The information processing device 100 receives fixed data to be stored in the memory unit 10 from an application vendor or the like, for example, as shown in Figure 6 (Step S01, Yes). Here, the information processing device 100 stores the received fixed data in the memory unit 10 (Step S02) and also calculates and stores first test data from the received fixed data (Step S03).
[0027] <During fault diagnosis> The information processing device 100 receives an error report from a user terminal, such as the inability to properly deploy an application, as shown in Figure 7 (Step S11, Yes). Upon receiving the error report, the information processing device 100 reads fixed data from the memory unit 10 and calculates second test data from the read fixed data (Step S12). The information processing device 100 then compares the first test data with the second test data (Step S13). If the first test data and the second test data do not match (Step S13, No), the information processing device 100 reports a failure (Step S14).
[0028] As described above, when the information processing device 100 receives an abnormality report from a user terminal of an application provider, it performs a fault diagnosis and reports a fault of its own if the first test data and the second test data do not match. Although this fault report does not definitively state that fixed data has been rewritten, it is useful for isolating the location of the fault. In other words, at the time an abnormality report is received from the user terminal, as shown in Figure 8, the following are possible causes: 1. a fault in the user terminal, 2. a communication failure, and 3. a fault on the information processing device 100 side. Here, the fault report from the information processing device 100 suggests that 3. a fault on the information processing device 100 side is the cause.
[0029] Furthermore, as mentioned above, the storage location for the first test data may be the memory unit 10. However, if the fixed data stored in the memory unit 10 is overwritten due to physical shock or the like, the first test data stored in the memory unit 10 may also be overwritten. Even if the first test data is overwritten, the information processing device 100 will still issue a failure report. However, from the perspective of the failure report of the information processing device 100, there is no problem. That is, whether the overwritten data is fixed data or the first test data, the data stored in the memory unit 10 has been overwritten, and therefore it can be said that the memory unit 10 has failed.
[0030] Furthermore, if the fixed data has not been rewritten and only the first test data has been rewritten, the application should deploy normally on user B's terminal, provided there are no problems with reading the fixed data or the communication process of the copied data. Therefore, one possible case in which the information processing device 100 reports a failure when only the first test data has been rewritten is, for example, when the information processing device 100 performs a self-check. In other words, the trigger for the failure diagnosis performed by the information processing device 100 is not limited to abnormality reports from the user terminal, but may also be periodic.
[0031] [Embodiment 2] With the following configuration, it becomes possible to identify failures in the read operation performed by the memory control unit 20.
[0032] As shown in Figure 9, the memory unit 10 has multiple memory spaces, each serving as an area for storing individual fixed data. The memory spaces can be managed by a page table and may have a capacity of 4KB, which is a typical page size. The test data calculation unit 30 calculates and stores a first test data for each fixed data stored in each memory space when storing fixed data, and calculates a second test data from each of the fixed data stored in each memory space during fault diagnosis. If the fault determination unit 40 obtains a comparison result in which the first test data and the second test data do not match for the fixed data stored in all memory spaces, it reports a fault indicating that a problem has occurred in the fixed data reading process by the memory control unit 20.
[0033] For example, suppose the fault detection unit 40 determines that the first test data and the second test data do not match with respect to the fixed data in memory space 1. On the other hand, suppose the fault detection unit 40 determines that the first test data and the second test data match with respect to the fixed data in memory space 2. In other words, the fault detection unit 40 determines that the fixed data in memory space 1 contains errors, but the fixed data in memory space 2 is correct.
[0034] Here, if a chronic anomaly were occurring in the reading of fixed data, the result should also be that the first test data and the second test data do not match for the fixed data in memory space 2. In other words, the result that the fixed data in memory space 1 contains errors, but the fixed data in memory space 2 is correct, negates the possibility of a chronic anomaly occurring in the reading of fixed data.
[0035] On the other hand, the fault detection unit 40 determines that the first test data and the second test data do not match with respect to the fixed data in all memory spaces. Here, it is unlikely that all the fixed data stored in each memory space will contain errors at once; rather, it is considered more likely that chronic abnormalities occur during the reading of the fixed data. Therefore, if the first test data and the second test data do not match with respect to all the fixed data, the fault detection unit 40 reports a fault indicating that a problem has occurred in the fixed data reading process by the memory control unit 20.
[0036] [Embodiment 3] With the following configuration, it becomes possible to identify that the anomaly occurred unexpectedly in the data provided to user B's terminal.
[0037] First, as a premise, the information processing device 100 packets the copy data stored in the cache 50 and sends it to the user terminal, but the copy data remains in the cache 50 even after packetization. That is, the copy data remaining in the cache 50 is identical to the one provided to the user terminal. Furthermore, the copy data remaining in the cache 50 will be replaced when the next fixed data is copied and stored in the cache 50.
[0038] The inspection data calculation unit 30 calculates third inspection data from the copy data remaining in the cache 50.
[0039] The fault detection unit 40 performs a comparison between the first test data and the second test data, and also performs a comparison between the first test data and the third test data. If the comparison results show that the first and third test data match, the fault detection unit 40 reports that the abnormality occurred during the communication process until the copy data reached the user terminal. Alternatively, if the comparison results show that the first and second test data do not match, and the first and third test data do not match, the fault detection unit 40 reports a fault in the information processing device 100. Alternatively, if the comparison results show that the first and second test data match, and the first and third test data do not match, the fault detection unit 40 reports that the abnormality occurred suddenly in the copy data provided to the user terminal.
[0040] [Regarding cases where the first and third test data match] As described above, the copy data remaining in the cache 50 is identical to the data provided to the user terminal, and the third test data is calculated from the copy data remaining in the cache 50. In other words, excluding errors in packetization, the data provided to the user terminal is considered to be free of abnormalities until it leaves the information processing device 100. To put it another way, the cause of the problem at the user terminal is most likely to be either 1. a malfunction at the user terminal or 2. a communication failure. Therefore, the fault detection unit 40 reports that the abnormality occurred during the communication process until the copy data reached the user terminal.
[0041] [In the case where the first and second test data do not match, and the first and third test data do not match.] First, since the first and third test data do not match, it is thought that an anomaly occurred in the data provided to the user terminal before it left the information processing device 100. Furthermore, as mentioned above, since the first and second test data do not match, a malfunction of the information processing device 100 is suspected.
[0042] [Regarding cases where the first and second test data match, but the first and third test data do not match.] Since the first and third test data do not match, it is thought that an anomaly occurred in the data provided to the user terminal before it left the information processing device 100. On the other hand, the second test data was calculated from fixed data newly read from the memory unit 10 by the memory control unit 20 during fault diagnosis. Here, the comparison result that the first and second test data match negates the possibility of chronic anomalies in the rewriting or reading of fixed data. In other words, it is thought that an anomaly of unknown cause occurred. Even though the cause is unknown, the comparison result that the first and second test data match suggests that the fixed data read by the memory control unit 20 and which was the basis for the second test data is correct. In other words, it is thought that the fixed data stored in the memory unit 10 has not been rewritten, and that there was no failure in the reading process by the memory control unit 20, and there is a possibility that no problems will occur in subsequent data provision. For this reason, the fault judgment unit 40 reports that the anomaly occurred suddenly in the copy data provided to the user terminal.
[0043] [Regarding cases where the first and second test data do not match, but the first and third test data match] Since the first and third test data match, it is assumed that, excluding errors in packetization, the copy data provided to the user terminal is free of abnormalities until it leaves the information processing device 100. In other words, it is presumed that the fixed data stored in the memory unit 10 is correct and that the correct copy data is stored in the cache 50. However, it is possible that the fixed data may be overwritten after the copy data is stored. Also, even if the fixed data stored in the memory unit 10 is correct, it is possible that an abnormality may occur in the process of reading the fixed data to calculate the second test data. These cases fall under the category of "the first and second test data do not match, and the first and third test data match." However, overwriting of the fixed data after the copy data is stored is not the direct cause of the abnormality report. Therefore, the failure determination unit 40 reports that the abnormality report is an abnormality that occurred during the communication process, and separately reports a failure of the information processing device 100.
[0044] [Embodiment 4] It is possible that the capacity of the cache 50 is small compared to the amount of fixed data. In this case, the information processing device 100 will divide the fixed data into multiple parts, store them in the cache 50 in multiple steps, and provide the copied data to the user terminal.
[0045] In such cases, the copy data remaining in cache 50 corresponds only to a portion of the fixed data and can be considered partial copy data. If a third test data is calculated from this partial copy data alone, it will not match the first test data calculated from the entire fixed data because the data sizes are different. Therefore, it is necessary to modify the partial copy data so that it corresponds to the entire fixed data.
[0046] Specifically, the inspection data calculation unit 30 reads partial fixed data corresponding to the portion other than the partial copy data from the memory unit 10, combines it with the partial copy data to construct combined fixed data, and calculates a third inspection data from the combined fixed data. The third inspection data calculated here partially includes elements of the fixed data newly read from the memory unit 10, but this poses no problem from the standpoint of detecting an anomaly that suddenly occurred in the copy data provided to the user terminal. In other words, if the first and second inspection data match, but the third inspection data calculated from the combined fixed data does not match the first inspection data, the possibility of chronic anomalies occurring in the rewriting of fixed data or in the reading of fixed data is ruled out.
[0047] [Variant form] The following describes various forms of modification of the information processing device 100. Note that the application of existing technologies to the information processing device 100, such as the format for providing data to other devices, will be done as necessary by those skilled in the art, and therefore, no further explanation is provided.
[0048] For example, fixed data is not limited to application data. In other words, the information processing device 100 can be said to be essentially a storage device. If the information processing device 100 can detect its own failure, including the rewriting of fixed data stored in the memory unit 10, then the information processing device 100 can perform the same processing regardless of the content of the fixed data.
[0049] Furthermore, when the memory unit 10 stores multiple fixed data, it is possible to arbitrarily configure which fixed data to prioritize for processing. For example, when an anomaly report is received from a user terminal, it is conceivable to prioritize processing the fixed data that was the source of the copy data provided to that user terminal.
[0050] Furthermore, when the information processing device 100 performs a self-check, it is conceivable that it calculates second inspection data (Figure 7, step S12) and compares it with the first inspection data (Figure 7, step S13) for all fixed data stored in the memory unit 10. However, if the memory unit 10 stores applications that have been discontinued as fixed data, the processing related to that fixed data may be skipped.
[0051] Furthermore, the present invention can also be developed as a program that causes a computer, acting as an information processing device 100, to execute processing. For example, as shown in Figure 10, the computer acting as the information processing device 100 includes memory, a CPU (Central Processing Unit), and an interface. The memory also functions as a memory unit 10 and a cache 50. The CPU reads the program of the present invention from the memory and executes it, thereby realizing processing modules corresponding to the memory control unit 20, the inspection data calculation unit 30, and the fault determination unit 40.
[0052] Furthermore, some or all of the above embodiments may also be described as follows, but are not limited to these.
[0053] (Note 1) A memory section for storing fixed data, A memory control unit that controls the memory unit, A test data calculation unit calculates and stores first test data from the fixed data when storing fixed data, and calculates second test data from the fixed data read by the memory control unit from the memory unit when fault diagnosis is performed. A fault determination unit compares the first inspection data with the second inspection data and reports a fault if the two do not match. An information processing device having
[0054] (Note 2) The memory unit has multiple memory spaces, each of which stores individual fixed data. The aforementioned inspection data calculation unit calculates and stores a first inspection data for each of the fixed data stored in each memory space when storing fixed data, and calculates a second inspection data from each of the fixed data stored in each memory space when diagnosing a fault. If the fault detection unit obtains a comparison result in which the first test data and the second test data do not match with respect to the fixed data stored in all memory spaces, it reports a fault indicating that a failure has occurred in the fixed data reading process by the memory control unit. The information processing device described in Appendix 1.
[0055] (Note 3) It includes a cache unit that temporarily stores copy data obtained by reading fixed data, When an anomaly report is received from the user terminal to which the copied data is provided, fault diagnosis is performed. The information processing device described in Appendix 1 or 2.
[0056] (Note 4) The aforementioned inspection data calculation unit calculates third inspection data from the copy data, The aforementioned fault determination unit, A comparison is performed between the first set of test data and the second set of test data, and also between the first set of test data and the third set of test data. If a comparison result is obtained in which the first test data and the third test data match, it will be reported that the anomaly occurred during the communication process until the copied data reached the user terminal. If a comparison result is obtained in which the first test data and the second test data match, and a comparison result is obtained in which the first test data and the third test data do not match, the system will report to the user terminal that an anomaly has occurred in the copy data provided to the user terminal. The information processing device described in Appendix 3.
[0057] (Note 5) When the copied data is a partial copy of the fixed data, The inspection data calculation unit reads from the memory unit the partially fixed data corresponding to the portion other than the partially copied data, combines it with the partially copied data to construct combined fixed data, and calculates third inspection data from the combined fixed data. The information processing device described in Appendix 4.
[0058] (Note 6) The steps include: when storing fixed data in the memory section, calculating and saving first inspection data from said fixed data; The steps include calculating second test data from fixed data read from the memory unit during fault diagnosis, A step of comparing the first test data with the second test data and reporting a failure if the two do not match, An information processing method using an information processing device.
[0059] (Note 7) As an information processing device, the computer The process involves calculating and saving first inspection data from the fixed data when storing the fixed data in the memory section, The process involves calculating second test data from fixed data read from the memory unit during fault diagnosis, A process that compares the first test data with the second test data and reports a failure if the two do not match. An information processing program that executes [something].
[0060] Furthermore, the features described in Appendix 2-5 can also be applied to information processing methods and information processing programs.
[0061] Furthermore, each disclosure of the above-mentioned cited patent documents, etc., shall be incorporated into this document by reference and may be used as the basis or part of the present invention as necessary. Within the framework of the entire disclosure of the present invention (including the claims), further modifications and adjustments to the embodiments or examples are possible based on the basic technical concept. Also, within the framework of the entire disclosure of the present invention, various combinations or selections (including partial deletions) of various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes the entire disclosure, including the claims, and various modifications and alterations that a person skilled in the art could make in accordance with the technical concept. In particular, with respect to the numerical ranges described in this document, any numerical value or sub-range included within that range should be interpreted as being specifically described even if not otherwise stated. Furthermore, each disclosure of the above-mentioned cited documents may, as necessary, be used in part or in whole as part of the disclosure of the present invention, in accordance with the spirit of the present invention, and this is also considered to be included in the disclosure of this application. [Explanation of Symbols]
[0062] 10 Memory section 20 Memory Control Unit 30. Data calculation unit for inspection 40 Failure determination section 50 Cache 100 Information Processing Devices
Claims
1. A memory section for storing fixed data, A memory control unit that controls the memory unit, A test data calculation unit calculates and stores first test data from the fixed data when storing fixed data, and calculates second test data from the fixed data read by the memory control unit from the memory unit when fault diagnosis is performed. A fault determination unit compares the first inspection data with the second inspection data and reports a fault if the two do not match. It has, The memory unit has multiple memory spaces, each of which stores individual fixed data. The aforementioned inspection data calculation unit calculates and stores a first inspection data for each of the fixed data stored in each memory space when storing fixed data, and calculates a second inspection data from each of the fixed data stored in each memory space when diagnosing a fault. If the fault detection unit obtains a comparison result in which the first test data and the second test data do not match with respect to the fixed data stored in all memory spaces, it reports a fault indicating that a failure has occurred in the fixed data reading process by the memory control unit. Information processing device.
2. It includes a cache unit that temporarily stores copy data obtained by reading fixed data, The information processing apparatus according to claim 1, which performs fault diagnosis when it receives an abnormality report from a user terminal that is the recipient of the copied data.
3. The aforementioned inspection data calculation unit calculates third inspection data from the copy data, The aforementioned fault determination unit, A comparison is performed between the first set of test data and the second set of test data, and also between the first set of test data and the third set of test data. If a comparison result is obtained in which the first test data and the third test data match, it will be reported that the anomaly occurred during the communication process until the copied data reached the user terminal. If a comparison result is obtained in which the first test data and the second test data match, and a comparison result is obtained in which the first test data and the third test data do not match, the system will report to the user terminal that an anomaly has occurred in the copy data provided to the user terminal. The information processing apparatus according to claim 2.
4. When the copied data is a partial copy of the fixed data, The inspection data calculation unit reads from the memory unit the partially fixed data corresponding to the portion other than the partially copied data, combines it with the partially copied data to construct combined fixed data, and calculates third inspection data from the combined fixed data. The information processing apparatus according to claim 3.
5. The steps include: when storing fixed data in the memory section, calculating and saving first inspection data from said fixed data; The steps include calculating second test data from fixed data read from the memory unit during fault diagnosis, A step of comparing the first test data with the second test data and reporting a failure if the two do not match, Includes, The memory unit has multiple memory spaces, each of which stores individual fixed data. When storing fixed data, a first test data is calculated and saved for each of the fixed data stored in each memory space, and during fault diagnosis, a second test data is calculated from each of the fixed data stored in each memory space. If the comparison results show that the first and second test data do not match for fixed data stored in all memory spaces, a failure is reported indicating that a problem has occurred in the fixed data reading process. Information processing method using information processing equipment.
6. As an information processing device, the computer The process involves calculating and saving first inspection data from the fixed data when storing the fixed data in the memory section, The process involves calculating second test data from fixed data read from the memory unit during fault diagnosis, A process that compares the first test data with the second test data and reports a failure if the two do not match. Make it run, The memory unit has multiple memory spaces, each of which stores individual fixed data. When storing fixed data, a first test data is calculated and saved for each of the fixed data stored in each memory space, and during fault diagnosis, a second test data is calculated from each of the fixed data stored in each memory space. If the comparison results show that the first and second test data do not match for fixed data stored in all memory spaces, a failure is reported indicating that a problem has occurred in the fixed data reading process. Information processing program.