JP5087502B2 - Operation log management apparatus and operation log management method - Google Patents

Description

  The present invention relates to an operation log management apparatus and an operation log management method for managing an operation log including an operation history in an information processing terminal.

  Conventionally, in an information processing terminal such as a mobile phone terminal, a personal digital assistant (PDA), and a personal computer (PC), an operation log including an operation history of the information processing terminal is sometimes stored. By storing the operation log, for example, when the user collects the information processing terminal after noticing the loss or theft of the information processing terminal, refer to the operation log to determine whether the information processing terminal has been illegally used. It can be confirmed with. However, in order to surely confirm the unauthorized use, it is necessary to ensure the reliability of the stored operation log against a failure such as a shortage of resources or an error in the information processing terminal. Further, the operation log increases according to the operation of the information processing terminal.

Therefore, techniques for preventing manipulation log falsification and techniques for reducing capacity have been proposed (for example, Patent Document 1 and Patent Document 2).
JP 2008-40745 A (page 8-9, FIG. 2) JP 2006-293834 A (pages 16-17, FIG. 11)

  In order to improve the reliability of saving operation logs against failures such as resource shortages and errors in information processing terminals, and to reliably save operation logs for a predetermined period (for example, 3 days) There is a problem like this.

  First, the operation log may be lost when the operation log storage fails due to a shortage of resources (memory, battery, storage, etc.), a function error, or a sudden power failure.

  Secondly, when a large amount of operation logs are generated, the storage capacity is limited, so there is a high possibility that the operation logs will overflow and the operation logs for a predetermined period cannot be saved. Although it is conceivable to delete an existing file in order to secure a storage area for the operation log, deleting an important system file or user data may lead to a system failure, data loss, and a decrease in convenience.

  Third, when the information processing terminal cannot secure a free space for the operation log, the operation log for a predetermined period cannot be stored. In addition, when the server always wants to know the operation log for a predetermined period and put the information processing terminal under control, the information processing terminal has a function of transferring the operation log to the server via the wireless communication network. If the information processing terminal is located outside the communication range for a long time or a failure occurs in the wireless communication network, it cannot be grasped.

  The present invention has been made in view of such a situation, and the information processing terminal having severe resource restrictions such as a memory, a storage capacity, or a battery is stored against a failure such as a resource shortage or an error. It is an object of the present invention to provide an operation log management apparatus and an operation log management method for improving the reliability of operation logs.

  In order to solve the problems described above, the present invention has the following features. First, the first feature of the present invention is that an operation log (operation log LG) including an operation history in the information processing terminal (terminal 10) is managed and a storage (storage 30) provided in the information processing terminal is provided. An operation log management device (operation log management device 100) that includes a log storage unit (log storage unit 113) that stores the operation log and is installed in the information processing terminal, and is stored in the storage as the operation log. An operation information holding unit (operation information holding unit 111) that holds one or more pieces of operation information (operation information OP) indicating the contents of the operation, and whether or not the operation information holding unit holds the operation information Is held in a non-volatile memory (memory 31), and the holding flag is set when the operation information holding unit holds the operation information. A holding flag setting unit (holding flag setting unit 112) for erasing the holding flag when saving to the storage is completed, and referring to the holding flag when the operation log management device is activated, holding the operation information A starting log unit (starting log unit 118) that stores a log indicating failure in storing the operation log in the storage and erases the retention flag.

  A second feature of the present invention relates to the first feature of the present invention, wherein the holding flag set by the holding flag setting unit is a time stamp indicating a time when the operation information is generated or a type of the operation information. The start-up log unit includes at least one of them, and stores the log including the content of the retention flag in the storage in addition to the failure to save the operation log.

  A third feature of the present invention relates to the first feature of the present invention, wherein the holding flag setting unit holds the holding information only when holding the type of operation information related to unauthorized use of the information processing terminal. The gist is to set a flag.

  A fourth feature of the present invention relates to the first feature of the present invention, wherein a failure flag indicating whether or not there is a failure in the processing of the operation information is maintained in a nonvolatile memory (memory 31), and the information processing terminal When a fatal fault that prevents the normal operation from being maintained in the processing of the operation information is detected, the fault flag includes at least one of a time stamp indicating the time when the fatal fault is detected and the type of the fatal fault. And a failure handling unit (failure handling unit 114) that executes restart of the information processing terminal after setting the failure flag, and the startup log unit is configured to start the operation log management device when the failure flag is If the failure flag is set, the gist is to save a log indicating the content of the failure flag and delete the failure flag.

  A fifth feature of the present invention relates to the fourth feature of the present invention, wherein the fault handling unit is unable to recover from a fault related to the processing of the operation information in the information processing terminal even by the restart, The gist is to execute a warning to the user of the information processing terminal or a restriction on operations on the information processing terminal.

  A sixth feature of the present invention relates to the first feature of the present invention, wherein when an operation log deletion command is received, it is authenticated whether the information processing terminal is a valid administrator, and the operation log The gist is to include a log deletion unit (log deletion unit 123) that executes deletion.

  A seventh feature of the present invention relates to the first feature of the present invention, wherein the log storage unit performs the operation according to a call executed before the information processing terminal is reset or power supply is stopped. The gist is to store the operation information held by the information holding unit in the storage before the resetting or the stop of the power supply.

  An eighth feature of the present invention relates to the first feature of the present invention, in which an erasable list (designating erasable information that is a file or folder that can be erased from the storage when the free space of the storage is insufficient). The erasable list holding unit (erasable list holding unit 101) that holds the erasable list L1) and the time stamp of the operation log when the free space of the storage is insufficient, When the operation log erasure unit (operation log erasure unit 103) for erasing the operation log and the erasure of the operation log by the operation log erasure unit do not solve the shortage of free space in the storage, the operation log erasure unit designates Of the erasable information, an information erasure unit (erasable file erasure unit 10) that erases the erasable information that is not being used in the information processing terminal. ) And is summarized in that comprises a.

  A ninth feature of the present invention relates to the eighth feature of the present invention, wherein the operation log is output to a first external device (for example, the server 20) of the information processing terminal, and the output operation log is output to the operation. The gist of the invention is that it includes an operation log output unit (operation log output unit 107) to be deleted by the log deletion unit.

  A tenth feature of the present invention relates to the eighth feature of the present invention, wherein the erasable list holding unit designates the file preinstalled from the time of shipment of the information processing terminal as the erasable information. The gist is to maintain the erasable list.

  An eleventh feature of the present invention relates to the eighth feature of the present invention, wherein the erasable list holding unit is deleted from the erasable list of the file being used in the information processing terminal, or the information processing The gist is to execute a list editing process including at least one of adding the file output to the second external device (for example, the external storage 41) of the terminal to the erasable list.

  A twelfth feature of the present invention relates to the eighth feature of the present invention, in which, even if the erasable information is erased by the operation log erasing unit, the free space of the storage falls below a predetermined value, the information processing terminal The gist of the invention is to provide an operation restriction unit (operation restriction unit 127) for releasing the restriction when the free space of the storage exceeds the predetermined value.

  A thirteenth feature of the present invention relates to the twelfth feature of the present invention, wherein the operation restriction unit is configured to perform the restriction when the operation log output unit fails to output the operation log to the first external device. And executing at least one of authentication of a user of the information processing terminal using biometrics and notification of failure of the output to the user.

  A fourteenth feature of the present invention relates to the eighth feature of the present invention, wherein the erasable list includes a priority of an order of erasing the erasable information, and the priority is given priority to the file. The gist of the information erasure unit is to erase the file according to the priority.

  A fifteenth feature of the present invention is according to the eighth feature of the present invention, wherein when the information erasure unit erases the erasable information, the dummy file indicating that the erasable information is temporarily erased. The gist is to generate.

  A sixteenth feature of the present invention relates to the eighth feature of the present invention, wherein when the free space of the storage exceeds a predetermined value, the information is erased outside the information processing terminal before being erased by the information erasing unit. A gist is provided with a restoration unit (repair unit 109) that repairs the file erased by the information erasure unit based on the file acquisition information indicating the output destination of the output file or the download source of the file. To do.

  A seventeenth feature of the present invention relates to the eighth feature of the present invention, wherein the log storage unit performs the erasing of the operation log by the operation log erasing unit and the erasing of the erasable information by the information erasing unit. The gist is to switch the storage destination of the operation log to an external storage (for example, the external storage 42) provided outside the information processing terminal when the shortage of free storage capacity is not solved.

  An eighteenth feature of the present invention is an operation log management method for managing an operation log including an operation history in an information processing terminal, wherein one or a plurality of operation information indicating contents of the operation stored as the operation log Are stored in a storage provided in the information processing terminal, and a holding flag indicating whether or not the operation information is held is maintained, and the holding flag is stored when the operation information is held in the storage. Is set, and the storage flag is deleted when the storage of the operation information in the storage is completed, and the operation information is stored by referring to the storage flag when the operation log management device is activated. The operation log is stored in the storage and the retention flag is erased. To.

  According to the features of the present invention, in an information processing terminal with severe resource constraints such as memory, storage capacity or battery, it is possible to improve the reliability of stored operation logs against failures such as resource shortage and errors. An operation log management apparatus and an operation log management method can be provided.

  Next, an embodiment of the present invention will be described. Specifically, (1) overall schematic configuration of information processing terminal, (2) details of functional block, (3) operation of operation log management device, (4) action / effect, and (5) other embodiments explain.

  In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, it should be noted that the drawings are schematic and ratios of dimensions and the like are different from actual ones.

  Accordingly, specific dimensions and the like should be determined in consideration of the following description. Moreover, it is a matter of course that portions having different dimensional relationships and ratios are included between the drawings.

(1) Overall Schematic Configuration of Information Processing Terminal FIG. 1 is an overall schematic configuration diagram of an information processing terminal including an operation log management apparatus according to the present embodiment. As shown in FIG. 1, an operation log management device 100 is mounted on a terminal 10 constituting an information processing terminal in the present embodiment. The operation log management apparatus 100 manages an operation log LG including an operation history in the information processing terminal (terminal 10).

  The terminal 10 is a mobile phone terminal, a personal digital assistant (PDA), a notebook personal computer (PC), or the like. The operation log management apparatus 100 is mounted on the terminal 10 as an application or middleware that operates on an operating system (OS). Note that the operation log management apparatus 100 may be implemented as software included in the OS, such as a device driver, or may be implemented as hardware.

  The terminal 10 can be connected to the server 20 via a wired communication path or a wireless communication path. In addition, the terminal 10 can access the storage 30 or the memory 31 mounted inside the terminal 10 and the external storage 41 and the external storage 42 provided outside the terminal 10.

  The operation log management apparatus 100 includes an erasable list holding unit 101, an operation log erasing unit 103, an erasable file erasing unit 105, and an operation log output unit 107. Further, the operation log management apparatus 100 includes a restoration unit 109, an operation information holding unit 111, a holding flag setting unit 112, a log saving unit 113, a failure handling unit 114, a MAC saving unit 115, a log saving unit 117, and a startup log unit 118. , An operation information output unit 119, a system stop information output unit 121, a log deletion unit 123, a log transmission unit 125, and an operation restriction unit 127.

(2) Details of Functional Block Next, details of each functional block constituting the operation log management apparatus 100 will be described.

Specifically, (2.1) log storage unit 113, (2.2) operation information holding unit 111, (2.3) holding flag setting unit 112, (2.4) startup log unit 118, (2 .5) failure handling unit 114, (2.6) erasable list holding unit 101, (2.7) operation log erasing unit 103, (2.8) erasable file erasing unit 105, (2.9) operation log The output unit 107, (2.10) restoration unit 109, (2.11) log deletion unit 123, (2.12) log transmission unit 125, and (2.13) operation restriction unit 127 will be described in this order.

(2.1) Log storage unit 113
The log storage unit 113 stores the operation log LG in the storage 30 provided in the terminal 10. Specifically, the log storage unit 113 stores information obtained by adding a time stamp or the like to the operation information OP from the terminal 10 in the storage 30 as the operation log LG.

  The timing at which the log storage unit 113 stores the operation information OP (or the operation information group including a plurality of operation information OP) in the storage 30 is, for example, the number or capacity of the operation information OP held exceeds a predetermined threshold It can be the case. The timing may be when a predetermined time has elapsed from the previous storage timing or at a specific time. In addition, the timing may be when important operation information OP is input or when the remaining battery (not shown) of the terminal 10 is low. Or the timing which received the call before reset of the terminal 10 or supply of power was stopped may be sufficient.

  Also, the log storage unit 113 may create a new file each time the operation log LG is stored, and store the file in which the operation information OP is written as the operation log LG. May be separated. Alternatively, the log storage unit 113 may generate the operation log LG by writing the contents of the operation information OP, the time stamp, and the like in a database.

  In this embodiment, the storage 30 is a Flash ROM or a hard disk built in the terminal 10, but an external storage such as an SD card or UIM may be used. The memory 31 is configured by a non-volatile memory such as a Flash ROM.

  The log saving unit 113 saves the operation log LG when the lack of free space in the storage 30 is not solved by erasing the operation log LG by the operation log erasing unit 103 and erasing erasable information by the erasable file erasing unit 105. The destination can be switched to the external storage 42 provided outside the terminal 10. Alternatively, when the free space for the operation log LG allocated to the storage 30 is equal to or less than the threshold, the log storage unit 113 refers to the time stamp of the operation log LG and operates before a predetermined period (for example, 3 days). The log LG may be saved in an external storage (for example, the external storage 41) provided outside the terminal 10.

  In addition, the log storage unit 113 can store the encrypted operation log LG. The log storage unit 113 may store the operation log LG that has been compressed instead of being encrypted. That is, the log storage unit 113 can store the operation log LG that has been subjected to at least one of encryption and compression.

(2.2) Operation information holding unit 111
The operation information holding unit 111 executes processing related to the operation information OP indicating the content of the operation on the terminal 10. Specifically, the operation information holding unit 111 holds one or a plurality of operation information OP indicating the content of the operation stored in the storage 30 as the operation log LG. In the present embodiment, the operation information holding unit 111 stores the operation information OP in a RAM (not shown).

  Further, the operation information holding unit 111 can store the operation information group and the authentication code in association with each other based on an authentication code (MAC value) used for authentication of the operation information group including the plurality of operation information OP. .

  For calculation of the Message Authentication Code (MAC) value, for example, a hashed message authentication code method with a key such as HMAC-MD5 or HMAC-SHA1 can be used. Alternatively, a message authentication code using block cipher such as CBC-MAC (Cipher Block Chaining-MAC) may be used.

(2.3) Holding flag setting unit 112
The holding flag setting unit 112 maintains a holding flag indicating whether or not the operation information holding unit 111 holds the operation information OP in the nonvolatile memory 31. The holding flag setting unit 112 sets a holding flag when the operation information holding unit 111 holds the operation information OP. The holding flag setting unit 112 erases, that is, resets the holding flag when the storage of the operation information OP in the storage 30 is completed.

  In the present embodiment, the operation information OP is stored in the RAM, but has not yet been written in the storage 30, so the holding flag setting unit 112 sets a holding flag indicating that there is a possibility of disappearance. It is assumed that the memory 31 in which the retention flag is maintained does not disappear even if the terminal 10 is suddenly reset or powered off.

  The holding flag set by the holding flag setting unit 112 can include a time stamp indicating the time when the operation information OP occurs or the type of the operation information OP. Further, the holding flag can include a time stamp corresponding to each of the plurality of operation information OP.

  Further, the holding flag setting unit 112 can set the holding flag only when holding the type of operation information OP related to unauthorized use of the terminal 10 in order to reduce processing overhead. Types related to unauthorized use include “opening / closing a folding mobile phone”, “input of a PIN”, “input of biometric authentication”, and the like.

(2.4) Start-up log unit 118
The startup log unit 118 refers to the holding flag when the operation log management apparatus 100 is started up and indicates that the operation information OP is held, and saves a log indicating the failure in saving the operation log LG in the storage 30. The holding flag is erased.

  In addition to the failure to save the operation log LG, the startup log unit 118 can save, in the storage, a log including the time stamp when the operation information OP occurred and the type of the operation information OP as the content of the holding flag. Furthermore, when the holding flag indicates that the operation information OP is not held, the startup log unit 118 can save a log indicating that there is no failure in saving the holding flag in the storage.

  The startup log unit 118 refers to a failure flag indicating whether there is a failure in the processing of the operation information OP when the operation log management device 100 is started. When the failure flag is set, the startup log unit 118 stores a log indicating the content of the failure flag and deletes the failure flag. Furthermore, when the failure flag is not set, a log indicating that there is no failure can be stored in the storage.

(2.5) Fault handling unit 114
The failure handling unit 114 maintains a failure flag in the memory 31 indicating whether or not there is a failure in the processing of the operation information OP. When a fatal failure that prevents the normal operation from being maintained in the processing of the operation information OP in the terminal 10 is detected, the failure handling unit 114 sets a time stamp indicating the time when the fatal failure is detected or the type of the fatal failure. Set the failure flag to include.

  The failure handling unit 114 restarts the terminal 10 after setting the failure flag. The type of failure is insufficient capacity of the memory 31 or an abnormality in the storage 30.

  In addition, the failure handling unit 114 can execute a warning to the user of the terminal 10 or a restriction on operations on the terminal 10 when the failure has not been recovered from the failure related to the processing of the operation information OP in the terminal 10 even after the terminal 10 is restarted.

(2.6) Erasable list holding unit 101
The erasable list holding unit 101 holds an erasable list L1 (not shown in FIG. 1, refer to FIG. 2) that designates a file or folder that can be erased from the storage 30 when the storage 30 has insufficient free space. Hereinafter, a file or folder that can be deleted from the storage 30 when the free space of the storage 30 is insufficient will be referred to as “erasable information” as appropriate.

  FIG. 2 shows an example of the erasable list L1. As shown in FIG. 2, the erasable list L <b> 1 can include the priority of the order of erasing erasable information. A file with a high priority is defined to be deleted preferentially.

  For example, since the preinstall video preinstall1.mp4 and the temporary file folder D: \ tmp are preferentially deleted, the priority is set to “1”. On the other hand, the preinstalled music preinstall2.wav and the backup file folder D: \ backup are set to “2” having a priority lower than “1”. Further, the photo preinstall3.jpg and the sample application D: \ sampleapp are set to “3” having a priority lower than “2”.

  The erasable list holding unit 101 can also add or delete a desired file to the erasable list L1 in accordance with a designation of a user of the terminal 10 or an administrator of a company that manages the terminal 10. For example, a desired file can be added to the erasable list L1 by providing a menu for setting an erasable list that can be presented to the user or by remotely controlling the operation log management apparatus 100. For example, in the erasable list L1, since the user likes preinstall1.mp4, the file may be deleted from the erasable list L1. Further, it is conceivable that, for example, the game-related file is not required by the administrator, and a folder d: \ games is added to the erasable list L1.

  The erasable list holding unit 101 can execute deletion of a file being used in the terminal 10 from the erasable list L1. Further, the erasable list holding unit 101 can output to any external storage, for example, the external storage 41, that is, add a backed up file to the erasable list. In the present embodiment, the external storage 41 constitutes a second external device. That is, the erasable list holding unit 101 can execute list editing processing such as addition or deletion of files.

  In the present embodiment, the external storage 41 and the external storage 42 may be any of an SD card, User Identity Module (UIM), USB, hard disk, and the like.

  For example, it is conceivable that a file having a problem due to deletion of the file (image) such as an image used in the standby screen of the terminal 10 is excluded from the deletion target. In the erasable list L1, for example, when preinstall3.jpg is used for the standby screen, the file is deleted from the erasable list L1. When the file is no longer used for the standby screen, the file may be added again to the erasable list L1.

  The file output (backed up) to the external storage 41 is recognized by notification from the file or database backup function or by inquiring the backup function. Further, the erasable list holding unit 101 may add the file that has been backed up to the server 20 or the external storage to the erasable list L1 together with the backup destination information. In the erasable list L1, preinstall3.jpg has been backed up in the server 20, and therefore the address of the server 20 is held in the “repair” entry. The address may be a URL, an IP address, a host name, or the like. Further, D: \ backup is recorded as being backed up in the external storage 41.

  The erasable list holding unit 101 can also hold an erasable list L1 that specifies files preinstalled from the time of shipment of the terminal 10 as erasable information. In addition, the erasable list holding unit 101 can add a preinstalled file that can be downloaded from the outside by the terminal 10 to the erasable list L1 together with the download destination information.

  In the erasable list L1, preinstall1.mp4 holds URL1 as a download destination in the repair entry. The server of URL1 can be, for example, the site of the manufacturer of the terminal 10 or the site of a content provider. By designating such a file, the influence on the terminal 10 and the user can be reduced even when the file is deleted.

(2.7) Operation log deletion unit 103
The operation log erasure unit 103 refers to the time stamp of the operation log LG when the free capacity of the storage 30 is insufficient, and erases the operation log LG before a predetermined period.

  Specifically, the operation log erasure unit 103 monitors the free capacity of the storage 30 allocated for the operation log LG by the fact that the operation log LG has insufficient free space. Alternatively, it may be recognized that the free space is insufficient by notification from another module in the operation log management apparatus 100, the OS of the terminal 10, the file system, or a database.

  For example, when the operation log deletion unit 103 itself monitors the free capacity of the storage 30, the operation log deletion unit 103 is activated by a periodic timer interrupt, and it is determined whether or not the free capacity is insufficient. The free capacity is determined to be insufficient, for example, when the capacity obtained by subtracting the capacity consumed by the operation log LG from the capacity of the storage 30 allocated for the operation log LG is below a predetermined value.

  For example, when 3 days is designated as the predetermined period, the operation log LG whose time stamp is earlier than 3 days is deleted. At that time, the operation log erasure unit 103 may erase all operation logs LG older than 3 days or only a part thereof.

  In the present embodiment, an operation priority according to the type of operation of the terminal 10 is assigned to the operation log LG. The operation log erasure unit 103 can determine the operation log LG to be erased based on the operation priority.

  FIG. 5 shows a specific example of the type and operation priority of the operation information OP (see FIG. 1). As shown in FIG. 5, browsing of the telephone book is designated with a high operation priority “1”, and web browsing is designated with a low operation priority “3”. When deleting the operation log LG, the operation log deletion unit 103 deletes the operation log LG related to Web browsing, or all the operation logs LG whose operation priority is designated as “3” (in the example of FIG. 5, Web browsing and setting changes) may be deleted.

  The operation log deletion unit 103 can store the type of the operation information OP of the deleted operation log LG when deleting the operation log LG. For example, the operation log erasure unit 103 can store the deletion of the operation log LG related to Web browsing.

  Further, when the operation log erasure unit 103 erases the operation log LG, the operation log OP is erased in units of operation information groups including a plurality of operation information OP associated with an authentication code, specifically, a MAC value. You can also. Further, when deleting the operation log LG, the operation log deleting unit 103 may display a dialog to request the user to confirm the deletion, or may perform user authentication using a password or biometric authentication.

(2.8) Erasable file erasure unit 105
The erasable file erasure unit 105 deletes the file or folder specified in the erasable list L1 when the deletion of the operation log LG by the previous operation log erasure unit 103 does not solve the shortage of free space in the storage 30. In the present embodiment, the erasable file erasure unit 105 constitutes an information erasure unit.

  Specifically, if the deletion of the operation log LG by the operation log deletion unit 103 does not solve the shortage of free space in the storage 30, the erasable file deletion unit 105 includes the erasable information specified by the erasable list L1. The erasable information that is not being used in the terminal 10 is erased.

  As shown in the erasable list L1, the erasable file erasure unit 105 marks a file or folder that has been erased in the erased entry, specifically by setting it to “1”, so that the next erasable file or folder Folders can be detected. The erasable file erasure unit 105 may display a dialog when erasing a file or the like to request confirmation of erasure from the user, or may perform user authentication using a personal identification number or biometric authentication.

  When a priority is designated for a file (or a folder, the same applies hereinafter), the erasable file erasure unit 105 can erase the file according to the priority. Specifically, the erasable file erasure unit 105 extracts a high-priority file (or folder) based on the erasable list L1, and deletes the extracted file. It should be noted that the erasable file erasure unit 105 does not extract an erased file when extracting a file. Further, the erasable file erasure unit 105 may extract a predetermined number, a predetermined capacity, or files from the highest priority to the predetermined priority.

  When the erasable file erasure unit 105 erases the file, that is, the erasable information, the erasable file erasure unit 105 can generate a dummy file indicating that the erasable information is temporarily erased. Alternatively, the erasable file erasure unit 105 may set a temporary erasure flag indicating that the file has been temporarily erased for the module that manages the file.

  Through this process, when a user tries to use a file such as a content or application that has been deleted to save the operation log LG, a dummy file or dialog indicating that the file has been temporarily deleted is displayed. can do.

  For example, in the case of an image file, save a dummy image file that indicates that it was temporarily deleted as the same file name as the deleted file name, or set a link from the deleted image file to the dummy image file As a result, display of the dummy image to the user is realized.

  For example, when a file is managed by a database, the erasable file erasure unit 105 may set a temporary erasure flag for the record of the file on the database. If the file is managed by a specific application, the erasable file erasure unit 105 may set a temporary erasure flag in the management table of the application.

(2.9) Operation log output unit 107
The operation log output unit 107 outputs the operation log LG to the server 20 and causes the operation log deletion unit 103 to delete the output operation log LG. In the present embodiment, the server 20 constitutes a first external device of the terminal 10.

  The operation log output unit 107 may cause the operation log deletion unit 103 to delete all the output operation logs LG, or the latest operation log LG among the output operation logs LG is stored in the storage 30 without being deleted. You may keep it. Note that the operation log output unit 107 avoids deleting the operation log LG whose output has failed by marking the operation log LG that has been successfully output.

  The operation log LG is output from the terminal 10 to the server 20 via a wired interface or a wireless interface, such as UART, USB, Bluetooth, wireless LAN, and mobile phone network. The operation log output unit 107 selects an output of the operation log LG by selecting a corresponding menu, when a communication path is established through a wired interface or a wireless interface, or when an output request is issued from the server 20 The operation log LG can be output in the case where it is done.

(2.10) Restoration unit 109
The restoration unit 109 indicates the output destination of the file output to the server 20 before being erased by the erasable file erasure unit 105 or the download source of the file when the free space in the storage 30 exceeds a predetermined value. Based on the file acquisition information, the file erased by the erasable file erasure unit 105 is repaired.

  Specifically, when the backup destination or the download source is the server 20, the restoration unit 109 downloads the file from the server 20 and rearranges the file on the storage 30 at the position before erasure. When the backup destination is an external storage, the restoration unit 109 reads the file from the external storage and rearranges it on the storage 30 at the position before erasure.

  The restoration unit 109 can select a file to be restored according to the priority. For example, the restoration unit 109 can preferentially restore a file whose priority is set to “3” in the erasable list L1.

  In addition, the repair unit 109 resets the erased entry (see the erasable list L1) of the repaired file to “0”. After the reset, the restoration unit 109 sets the file to be erasable when the free space in the storage 30 becomes insufficient.

(2.11) Log deletion unit 123
When the log deletion unit 123 receives a command to delete the operation log LG, the log deletion unit 123 authenticates whether the user is a valid administrator of the information processing terminal, and deletes the operation log LG. The deletion command includes initialization for deleting all operation logs LG. For example, when the user of the terminal 10 is an employee, the administrator is an information system administrator of a company to which the employee belongs, and when the user is a child, the administrator is a parent. The administrator and the user may be the same, but are different in this embodiment.

  Specifically, the log deletion unit 123 authenticates whether it is a legitimate administrator when receiving a deletion command of the operation log LG locally, that is, from the menu of the terminal 10 or the like. Require authentication by metrics. The log deletion unit 123 deletes the operation log LG when it is determined as a deletion command from a legitimate administrator.

  Further, in the case of a remote operation log LG deletion command, the log deletion unit 123 deletes a command from an authorized authorized administrator based on verification of an electronic signature given to the deletion command, key verification, or the like. It is determined whether or not. The log deletion unit 123 deletes the operation log LG when it is determined as a deletion command from a legitimate administrator.

(2.12) Log transmission unit 125
The log transmission unit 125 transmits an unsent operation log LG to the server 20 according to conditions based on time and events. For example, the log transmission unit 125 can periodically transmit an unsent operation log LG at a predetermined interval, or can transmit at a specific time.

  In addition, the log transmission unit 125 transmits an operation log LG that has not yet been transmitted in response to a data deletion command or a deletion command from the server 20 or another server, or a security code input failure. An unsent operation log LG may be transmitted when the operation information OP is generated.

  Note that when the unsent operation log LG is transmitted to the server 20, the log transmission unit 125 does not include all unsent operation logs LG, but important operation logs LG, relatively new or old operation logs LG, etc. A part of the unsent operation log LG may be extracted and transmitted.

(2.13) Operation restriction unit 127
The operation restriction unit 127 performs operation restriction on the terminal 10 when the free space of the storage 30 falls below a predetermined value even when the operation log deletion unit 103 deletes erasable information such as a file. Further, the operation restriction unit 127 releases the restriction when the free capacity of the storage 30 exceeds a predetermined value.

  Specifically, even if the erasable information is erased, the operation restriction unit 127 restricts the use of the terminal 10 in the locked state when the free space of the operation log LG is less than a predetermined value. The operation restriction unit 127 releases the lock when the free capacity of the storage 30 exceeds a predetermined value.

  The operation restriction unit 127 also locks the terminal 10 or performs user authentication by biometric authentication even when transmission of the operation log LG to the server 20 fails for a predetermined time or a predetermined number of times. You may do. Alternatively, if the operation log output unit 107 fails to output the operation log LG to the server 20, the operation restriction unit 127 may notify the user of the output failure.

  Further, the operation restriction unit 127 may cause the erasable file erasure unit 105 to erase the erasable information when the operation log LG output by the operation log output unit 107 to the server 20 fails.

(3) Operation of Operation Log Management Device Next, the operation of the operation log management device 100 will be described. Specifically, (3.1) erasable information erasing procedure, (3.2) log saving procedure, (3.3) operation log saving procedure, (3.4) operation log saving destination switching procedure, (3 .5) Start-up flag check procedure, (3.6) Failure handling procedure, (3.7) Operation log deletion procedure, (3.8) Operation log transmission procedure, and (3.9) Repair procedure will be described.

(3.1) Erasing Procedure for Erasable Information First, an erasing procedure for erasable information such as a file will be described with reference to FIGS.

(3.1.1) Procedure 1
FIG. 3 is a flowchart according to the erasure procedure 1 of erasable information by the operation log management apparatus 100. This procedure is executed in response to a timer interrupt.

  As shown in FIG. 3, in step 31, the operation log erasure unit 103 first determines whether or not the free space of the operation log LG is insufficient. The operation log erasure unit 103 ends the procedure when the free space is not insufficient.

  In step 32, the operation log erasure unit 103 refers to the time stamp of the operation log LG stored in the storage 30 and erases the operation log before a predetermined period. At this time, the operation log erasure unit 103 may display a dialog to confirm the erasure to the user, or may perform user authentication using a password or biometric authentication.

  In step 33, the operation log erasure unit 103 determines again whether or not the free space of the operation log LG is insufficient. If the lack of free space is resolved by erasing the operation log LG in step S32, the operation log erasing unit 103 ends the procedure.

  If the lack of free space is not resolved in step 34, the erasable file erasure unit 105 deletes the file or folder specified in the erasable list L1. At this time, the erasable file erasure unit 105 marks an erased file or folder in the erasable list L1.

  The operation log erasure unit 103 may erase the operation log LG in units of operation information groups including a plurality of operation information OP when erasing the operation log LG in order to ensure the consistency of the MAC value.

(3.1.2) Procedure 2
FIG. 4 shows a flowchart according to the erasure procedure 2 for erasable information by the operation log management apparatus 100. In this procedure, the erasable information is erased according to the priority of the order of erasing the erasable information. This procedure is also executed in response to a timer interrupt in the same manner as procedure 1. Steps 41 to 43 are the same as steps 31 to 33, and a description thereof will be omitted.

  In step 44, the erasable file erasure unit 105 extracts a high priority file or folder from the erasable list L1.

  In step 45, the erasable file erasure unit 105 deletes the extracted file or folder.

(3.2) Log Saving Procedure FIG. 6 shows a flowchart according to the log saving procedure performed by the operation log management apparatus 100. As described above, there are various cases in which the operation log LG is stored. Here, the operation log LG is stored when a predetermined time (1 minute) has elapsed from the previous storage time, that is, A case where the operation log LG is periodically saved will be described.

  Regarding the method for saving the operation log LG, here, a case will be described in which a new file is created each time the operation log LG is saved, and the operation information OP is written to the file. Further, associating the MAC value with the operation information OP uses a method of embedding the MAC value in a file including the operation information OP.

  As shown in FIG. 6, this procedure is executed when the operation information OP is input to the operation log management apparatus 100.

  In step 61, the operation information holding unit 111 holds the operation information OP input from the terminal 10, and sets a time stamp in the holding flag.

  In step 62, the log storage unit 113 determines whether a predetermined time (1 minute) has elapsed since the previous log storage time. If the predetermined time has not elapsed, the log storage unit 113 ends the procedure.

  In step 63, the log saving unit 113 newly creates a file on the storage 30, writes one or more operation information OP to be held in the file, and saves the file. Further, the operation information holding unit 111 erases, that is, resets the holding flag.

  In step 64, the MAC storage unit 115 calculates the MAC value of the stored file.

  In step 65, the MAC storage unit 115 embeds the calculated MAC value in the file.

  In step 66, the log storage unit 113 determines whether the free space for the operation log LG allocated to the storage 30 is larger than the threshold value. When the free space is larger than the threshold value, the log storage unit 113 ends the procedure.

  In step 67, when the free space is equal to or smaller than the threshold value, the log storage unit 113 calls (3.3) an operation log saving procedure and ends this procedure.

(3.3) Operation Log Saving Procedure FIG. 7 shows a flowchart according to the operation log saving procedure by the operation log management apparatus 100. This procedure is executed when called from the log storage unit 113.

  In step 71, the log storage unit 113 refers to the time stamp of the operation log LG stored in the storage 30, and extracts the operation log LG before a predetermined period (for example, 3 days).

  In step 72, the log storage unit 113 saves the extracted operation log LG in the external storage 41, and ends the procedure. At this time, the MAC storage unit 115 also updates the association between the MAC value and the operation information OP.

(3.4) Operation Log Storage Destination Switching Procedure FIG. 8 shows a flowchart according to the operation log storage destination switching procedure by the operation log management apparatus 100. Steps 81 to 82 are the same as steps 71 to 72, and a description thereof will be omitted.

  In step 83, the log storage unit 113 determines whether the free space for the operation log LG in the storage 30 built in the terminal 10 exceeds a predetermined value, that is, whether the shortage has been resolved. When the shortage is resolved, the log storage unit 113 ends the procedure.

  In step 84, the log storage unit 113 switches the storage destination of the operation log LG to the external storage 42 because the shortage of free space has not been resolved.

(3.5) Startup Flag Checking Procedure FIG. 9 shows a flowchart according to the startup flag checking procedure by the operation log management apparatus 100. This procedure is executed when the terminal 10 is started and the operation log management apparatus 100 is started, or when only the operation log management apparatus 100 is restarted.

  In step 91, the startup log unit 118 refers to the retention flag when the operation log management apparatus 100 is started up. In step S92, the startup log unit 118 determines whether the retention flag is set.

  If the retention flag is set, in step 93, the start-up log unit 118 stores a log indicating failure in storing the operation log LG in the storage 30. In the present embodiment, the time stamp included in the retention flag and the type of operation information OP are stored as the operation log LG.

  In step 94, the startup log unit 118 refers to the failure flag. In step S95, the startup log unit 118 determines whether a failure flag is set.

  If the failure flag is set, in step 96, the startup log unit 118 stores a log indicating failure in saving the operation log LG in the storage 30. In the present embodiment, the time stamp included in the failure flag and the type of failure are stored as the operation log LG. The startup log unit 118 executes the process of step S96 and ends this procedure.

(3.6) Troubleshooting Procedure FIG. 10 is a flowchart according to the troubleshooting procedure by the operation log management apparatus 100. This procedure is executed when a fatal failure is detected in the processing of the operation information OP.

  In step 101, the failure handling unit 114 sets a failure flag including the current time or the time when a fatal failure is detected and the type of fatal failure as a time stamp.

  In step 102, the failure handling unit 114 ends this procedure by executing restart (reset) of the terminal 10.

(3.7) Operation Log Deletion Procedure FIG. 11 shows a flowchart according to the operation log deletion procedure by the operation log management apparatus 100. This procedure is executed when a log deletion command is received locally or remotely. Here, it is assumed that a log deletion command is received from the server 20.

  In step 111, the log deletion unit 123 verifies the electronic signature of the log deletion command.

  In step 112, the log deletion unit 123 determines whether the deletion instruction is from an authorized administrator based on the validity of the electronic signature.

  In step 113, the log deletion unit 123 deletes the operation log LG when the verification of the log deletion command is successful. On the other hand, when the verification of the log deletion command fails, the log deletion unit 123 ends this procedure because it is not a log deletion command from an authorized user.

(3.8) Operation Log Transmission Procedure FIG. 12 shows a flowchart according to the operation log transmission procedure by the operation log management apparatus 100. This procedure is executed based on a timer interrupt. Here, it is assumed that the log transmission unit 125 periodically transmits the operation log LG. In addition, when transmission of the operation log LG is not successful for a predetermined time, a predetermined file (a file including personal information, business information, etc. and a file designated in advance) is deleted.

  In step 121, the log transmission unit 125 determines whether a predetermined time has elapsed since the previous transmission of the operation log LG. When the predetermined time has not elapsed, the log transmission unit 125 ends the procedure.

  In step 122, the log transmission unit 125 transmits an untransmitted operation log LG to the server 20 because a predetermined time has elapsed.

  In step 123, the log transmission unit 125 determines whether transmission of the operation log LG has succeeded or failed. If the log transmission unit 125 is successful, the procedure ends.

  When transmission of the operation log LG fails, in step 124, the log transmission unit 125 determines whether transmission of the operation log LG has not succeeded for a predetermined time.

  If transmission of the operation log LG has not succeeded for a predetermined time, in step 125, the log transmission unit 125 deletes the predetermined file described above in the specified file, specifically, the erasable list L1. To do.

(3.9) Repair Procedure FIG. 13 shows a flowchart according to the repair procedure performed by the operation log management apparatus 100. Here, the case where this procedure is executed when the operation log output is called from the menu is shown. Here, it is assumed that the file preinstalled in the terminal 10 is restored by downloading.

  In step 131, the operation log output unit 107 outputs the operation log LG to the server 20. At that time, the operation log output unit 107 marks the operation log LG that has been successfully output.

  In step 132, the operation log output unit 107 calls the operation log deletion unit 103.

  In step 133, the operation log deletion unit 103 deletes the marked operation log LG.

  In step 134, the operation log erasing unit 103 determines whether the free capacity of the storage 30 exceeds a predetermined value. If the free space does not exceed the predetermined value, the operation log erasing unit 103 ends the procedure.

  When the free space exceeds the predetermined value, in step 125, the restoration unit 109 downloads a file from the URL with reference to the download destination information in the restoration entry of the erasable list L1. The restoration unit 109 rearranges the downloaded file to the original position, that is, the position before erasure on the storage 30.

  In step 126, the repair unit 109 resets the erased entry in the erasable list L1 for the repaired file.

(4) Operation / Effect According to the operation log management device 100, the retention flag setting unit 112 maintains the retention flag on the memory 31, and the activation log unit 118 sets the retention flag after the terminal 10 is restarted. If it is, the log indicating the failure to save the operation log LG is saved in the storage 30. For this reason, even if there is a sudden power interruption such as failure of the terminal 10 or removal of a battery (not shown), at least the presence or absence of a log that has failed to be saved can be confirmed.

  In the present embodiment, when the failure handling unit 114 maintains a failure flag on the memory 31 and the startup log unit 118 is set with a failure flag after the terminal 10 is restarted, the failure occurrence time or fatal failure is set. Save the log including the type of. For this reason, even if a failure occurs in the processing of the operation information OP, the failure occurrence time is stored by means other than the log storage unit 113 and the storage 30, and the time is recorded after recovery. That is, in the terminal 10, the time zone in which the log function is operating normally and the time zone in which the log function is abnormal can be confirmed from the log.

  In the present embodiment, an operation log LG deletion command is accepted only from an authorized user of the terminal 10, and the operation log LG is deleted. For this reason, for example, when the terminal 10 is for business use, an administrator of the terminal 10 in the company can delete the operation log LG, but deletion of the operation log LG by an employee using the terminal 10 can be prohibited. Can improve the reliability.

  In this embodiment, when the lack of free space in the storage 30 is not resolved by erasing the operation log LG before a predetermined period (3 days), the terminal 10 uses the erasable information specified by the erasable list L1. Erasable information that is not in the middle is erased. For this reason, by erasing the erasable information, the free space of the storage 30 can be secured for the operation log LG.

  In other words, according to the operation log management apparatus 100, it is possible to more reliably store the operation log LG for a predetermined period in the terminal 10 that has severe resource restrictions such as the capacity of the storage 30 and the battery.

  In the present embodiment, the operation log LG output to the server 20 is deleted by the operation log deletion unit 103. For this reason, it is possible to increase the free capacity of the storage 30 while saving the operation log LG in the server 20. In the present embodiment, since only the operation log LG that has been successfully output is marked, it is possible to prevent the operation log LG from being lost due to an output failure.

  In this embodiment, a pre-installed file that can be downloaded from the time of shipment is designated as erasable information. Since the file is relatively easy to repair, the influence of the deletion of the file by the erasable file erasure unit 105 on the terminal 10 and the user can be reduced.

  In the present embodiment, a list editing process including deleting a file being used in the terminal 10 from the erasable list L1 or adding the file output to the external storage 41 to the erasable list L1 is executed. For this reason, files that cause problems when deleted, such as images set on the standby screen of the terminal 10, can be excluded from the deletion target. Further, by adding the file output to the external storage 41, that is, backed up to the erasable list L1, the free capacity of the storage 30 can be increased.

  In the present embodiment, even if the erasable information such as a file is erased, if the free capacity of the storage 30 falls below a predetermined value, the operation of the terminal 10 is restricted. For this reason, when the operation log LG cannot be reliably stored in the storage 30, the safety of the terminal 10 can be ensured by restricting the use of the terminal 10.

  In the present embodiment, when the output of the operation log LG to the server 20 fails, the erasable information erasure unit 105 deletes the erasable information. In addition, when the output of the operation log LG to the server 20 fails, execution of use restriction of the terminal 10, authentication of the user of the terminal 10 using biometrics, or notification of failure of the output to the user of the terminal 10 is executed. can do.

  For this reason, even when the server 20 falls into a state where the operation log LG of the terminal 10 cannot be grasped, the possibility that the operation log LG for a predetermined period cannot be saved can be reduced. Further, according to the failure notification of the output to the user, the user can recognize in advance the possibility that the terminal 10 will execute usage restrictions or file deletion. Therefore, the user can take measures such as manually transmitting the operation log LG to the server 20 when, for example, the terminal 10 moves into a wireless communication executable range.

  In the present embodiment, the erasable file erasure unit 105 erases the file according to the priority of the order of erasing the erasable information. Therefore, it is possible to sequentially delete files with relatively few problems even if they are deleted.

  In the present embodiment, when the erasable file erasure unit 105 erases the erasable information, the erasable file erasure unit 105 generates a dummy file indicating that the erasable information is temporarily erased. For this reason, when a user of the terminal 10 tries to use a file such as a deleted content or application, a dummy file or dialog indicating that the file has been temporarily deleted can be displayed. Further, in this embodiment, in a fixed case, the deleted file is repaired by the repairing unit 109 downloading the file erased by the erasable file erasing unit 105. In other words, it is possible to alleviate a decrease in user convenience associated with erasing a file.

  In the present embodiment, the operation log deletion unit 103 determines the operation log LG to be deleted based on the operation priority according to the type of operation of the terminal 10. For this reason, the operation log LG including the operation information OP with a high priority can be stored as much as possible.

  In the present embodiment, a holding flag for determining operation information held (stored) in the RAM without being stored in the storage 30 is used. For this reason, even when a sudden power interruption occurs in the terminal 10, it is possible to determine whether or not there is operation information OP that has been lost because only the RAM is retained.

  In the present embodiment, the operation log deletion unit 103 deletes the operation information OP in units of operation information groups associated with the MAC values when deleting the operation log LG. For this reason, it is easy to detect falsification of the operation log LG. In addition, since processing is executed in units of operation information groups including a plurality of operation information OP, processing overhead and battery consumption can be suppressed.

  In this embodiment, when the free space of the storage is insufficient, the operation log LG before the predetermined period is saved in the external storage 41 by referring to the time stamp of the operation log LG. Therefore, it is possible to leave an operation log LG in an amount exceeding the capacity of the storage 30 allocated for the operation log LG. Further, if the external storage 41 is removed from the terminal 10, there is a risk that the operation log LG is lost or the operation log LG is failed to be written. However, since the operation log LG for a predetermined period (for example, 3 days) is stored in the storage 30 that is relatively safer and more reliable than the external storage 41, that is, the storage built in the terminal 10, the manipulation log LG is altered. A certain level of safety can be secured.

  In this embodiment, when the deletion of the operation log LG by the operation log deletion unit 103 and the deletion of the erasable information by the erasable file deletion unit 105 does not solve the shortage of free space in the storage 30, the storage destination of the operation log LG is The external storage 42 is switched. Therefore, it is possible to leave an operation log LG in an amount exceeding the capacity of the storage 30 allocated for the operation log LG.

  In the present embodiment, the log storage unit 113 stores an operation log LG that has been subjected to at least one of encryption and compression. For this reason, when the terminal 10 is stolen or lost, the risk that the operation log LG is stolen can be reduced.

(5) Other Embodiments As described above, the content of the present invention has been disclosed through one embodiment of the present invention. However, it is understood that the description and drawings constituting a part of this disclosure limit the present invention. should not do. From this disclosure, various alternative embodiments will be apparent to those skilled in the art.

  For example, in the embodiment of the present invention described above, the terminal 10 is connected to the server 20, the external storage 41, and the external storage 42. However, the terminal 10 may not necessarily be connected to all these external devices. Absent. For example, only the external storage 41 may be used without using the external storage 42.

  In the embodiment described above, the erasable list L1 includes an entry such as a priority, but the entry may not necessarily be included.

  As described above, the present invention naturally includes various embodiments that are not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

1 is an overall schematic configuration diagram of an information processing terminal including an operation log management apparatus according to an embodiment of the present invention. It is a figure which shows an example of the erasable list | wrist L1 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the deletion procedure 1 of the erasable information by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the deletion procedure 2 of the erasable information by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the specific example of the classification and operation priority of the operation information OP which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the log preservation | save procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the operation log saving procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the operation log preservation | save destination switching procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the starting flag test | inspection procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the troubleshooting procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the operation log deletion procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the operation log transmission procedure by the operation log management apparatus 100 which concerns on embodiment of this invention. It is a figure which shows the flowchart according to the repair procedure by the operation log management apparatus 100 which concerns on embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Terminal, 20 ... Server, 30 ... Storage, 31 ... Memory, 41, 42 ... External storage, 100 ... Operation log management apparatus, 101 ... Erasable list holding unit, 103 ... Operation log erasure unit, 105 ... Erasable file Eraser, 107 ... Operation log output unit, 109 ... Repair unit, 111 ... Operation information holding unit, 112 ... Hold flag setting unit, 113 ... Log storage unit, 114 ... Failure handling unit, 115 ... MAC storage unit, 117 ... Log Saving unit, 119 ... operation information output unit, 121 ... system stop information output unit, 123 ... log deletion unit, 125 ... log transmission unit, 127 ... operation restriction unit, L1 ... erasable list, LG ... operation log, OP ... operation information

Claims (17)

An operation log management apparatus implemented in the information processing terminal, including a log storage unit that manages an operation log including an operation history in the information processing terminal and stores the operation log in a storage provided in the information processing terminal Because
An operation information holding unit that holds one or more pieces of operation information indicating the content of the operation stored in the storage as the operation log;
A holding flag indicating whether or not the operation information holding unit holds the operation information is maintained in a non-volatile memory, and the holding flag is set when the operation information holding unit holds the operation information. A holding flag setting unit for erasing the holding flag when the operation information is completely stored in the storage;
When the operation log management device is activated, the retention flag is referred to, and if the operation information is retained, a log indicating that the operation log is not stored is stored in the storage and the retention flag is deleted. With a startup log part ,
The holding flag set by the holding flag setting unit includes at least one of a time stamp indicating a time when the operation information is generated and a type of the operation information,
The startup log unit is an operation log management device that stores, in the storage, a log including the content of the retention flag in addition to the failure to save the operation log.   The operation log management apparatus according to claim 1, wherein the holding flag setting unit sets the holding flag only when holding the type of operation information related to unauthorized use of the information processing terminal. When a failure flag indicating whether or not there is a failure in the processing of the operation information is maintained in a non-volatile memory, and a fatal failure that prevents normal operation in the operation information processing in the information processing terminal is detected, the fatal Trouble handling unit that sets the failure flag including at least one of a time stamp indicating a time when a global failure is detected and the type of the fatal failure, and restarts the information processing terminal after setting the failure flag With
The startup log unit refers to the failure flag when the operation log management device is started up, and saves a log indicating the content of the failure flag and erases the failure flag when the failure flag is set. The operation log management apparatus according to claim 1. The failure handling unit executes a warning to the user of the information processing terminal or restriction of an operation on the information processing terminal when the failure cannot be recovered from the failure related to the processing of the operation information in the information processing terminal even after the restart The operation log management apparatus according to claim 3 .   The operation log management device according to claim 1, further comprising: a log deletion unit that authenticates whether or not the information processing terminal is a valid administrator when the operation log deletion command is received, and executes deletion of the operation log. .   In response to a call executed before the information processing terminal is reset or the power supply is stopped, the log storage unit resets the operation information held by the operation information holding unit. The operation log management apparatus according to claim 1, wherein the operation log management apparatus stores the information in the storage before stopping. An erasable list holding unit that holds an erasable list that specifies erasable information that is a file or folder that can be erased from the storage when the storage has insufficient free space;
An operation log erasure unit for erasing the operation log before a predetermined period with reference to the time stamp of the operation log when the free space of the storage is insufficient;
When the operation log erasure by the operation log erasure unit does not solve the shortage of free space in the storage, the erasable information that is not being used in the information processing terminal among the erasable information specified by the erasable list The operation log management apparatus according to claim 1, further comprising an information erasing unit that erases information. The operation log management apparatus according to claim 7 , further comprising: an operation log output unit that outputs the operation log to a first external device of the information processing terminal and causes the operation log deletion unit to delete the output operation log. The operation log management apparatus according to claim 7 , wherein the erasable list holding unit holds the erasable list that specifies the file preinstalled from the time of shipment of the information processing terminal as the erasable information. The erasable list holding unit deletes the file being used in the information processing terminal from the erasable list or outputs the file output to the second external device of the information processing terminal to the erasable list. The operation log management apparatus according to claim 7 , wherein a list editing process including at least one of additions is executed. Even if the erasable information is erased by the operation log erasure unit, if the free space of the storage falls below a predetermined value, the operation of the information processing terminal is restricted, and the free space of the storage becomes equal to or greater than the predetermined value. The operation log management apparatus according to claim 7 , further comprising an operation restriction unit that cancels the restriction when the restriction occurs. When the operation log output unit fails to output the operation log to the first external device, the operation restriction unit executes the restriction, authenticates a user of the information processing terminal using biometrics, or the The operation log management apparatus according to claim 11 , wherein at least one of the output failure notifications to a user is executed. The erasable list includes a priority of an order of erasing the erasable information,
The priority is defined to preferentially erase the file,
The operation log management device according to claim 7 , wherein the information erasure unit erases the file according to the priority. The operation log management device according to claim 7 , wherein when the erasable information is erased, the information erasure unit generates a dummy file indicating that the erasable information is temporarily erased. File acquisition indicating the output destination of the file output to the outside of the information processing terminal or the download source of the file before being erased by the information erasure unit when the free space of the storage exceeds a predetermined value The operation log management device according to claim 7 , further comprising a restoration unit that restores the file erased by the information erasure unit based on information. The log storage unit determines the storage destination of the operation log when the deletion of the operation log by the operation log deletion unit and the deletion of the erasable information by the information deletion unit does not solve the shortage of free space in the storage. The operation log management device according to claim 7 , wherein the operation log management device is switched to an external storage provided outside the information processing terminal. An operation log management method for managing an operation log including an operation history in an information processing terminal,
Holding one or more pieces of operation information indicating the contents of the operation stored as the operation log in a storage provided in the information processing terminal;
When a holding flag indicating whether or not the operation information is held is maintained, the holding flag is set when the operation information is held in the storage, and the storage of the operation information in the storage is completed Erasing the retention flag in
When the operation log management device is activated, the retention flag is referred to, and if the operation information is retained, a log indicating that the operation log is not stored is stored in the storage and the retention flag is deleted. With steps ,
The holding flag includes at least one of a time stamp indicating a time when the operation information is generated and a type of the operation information,
An operation log management method for storing a log including the content of the retention flag in addition to a failure to save the operation log when the log is stored in the storage .

Images