Operation Log Classification for Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The reliability of operation logs collected by a server is impaired due to network connection problems or client terminal malfunctions, leading to incomplete or missing log data.

Innovation Solution

An information processing apparatus that obtains and classifies operation logs from both the server and client devices based on recording and retrieval times, distinguishing chronologically fixed and not chronologically fixed logs to ensure accurate data collection and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the server collects operation logs from client terminals, then the quantity of log data increases, but the reliability of collected logs deteriorates due to network connection problems or client terminal malfunctions

Engineering Contradiction:
Improvequantity of log dataVSAvoidreliability of collected logs
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments operation logs into two distinct categories: chronologically fixed logs (recorded in chronological order with reliable timestamps) and chronologically unfixed logs (logs that may not reflect true chronological order due to collection issues). This segmentation allows the system to maintain high quantity of collected logs while identifying and handling unreliable logs separately, thus resolving the contradiction between quantity and reliability.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If the server collects operation logs centrally from multiple client terminals, then the comprehensiveness of log management improves, but the difficulty of detecting and measuring log reliability increases

Engineering Contradiction:
Improvecompleteness of log managementVSAvoiddifficulty of detecting log reliability
Core Design Contradiction:
Loss of informationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies preliminary action by recording the collection timing of operation logs from each client terminal before proceeding with log analysis. This preliminary timestamp recording enables the server to later determine whether logs were collected in proper chronological order, making it easier to detect reliability issues without adding complex verification mechanisms during the log collection process itself.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the server attempts to verify the chronological accuracy of each operation log, then the reliability assessment improves, but the processing time increases

Engineering Contradiction:
Improvereliability assessment accuracyVSAvoidlog processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements partial action by verifying chronological accuracy only for logs that are suspected to be unreliable (chronologically unfixed logs), rather than verifying every single log entry. The server uses the recorded collection timing to identify logs that may not be in chronological order and focuses verification efforts on these specific cases, thereby maintaining reliable assessment without excessive processing time for all logs.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240070119A1Information processing apparatus and non-transitory computer readable medium
Publication Date: 2024.02.29 FUJIFILM BUSINESS INNOVATION CORP
  • US20240070119A1 patent drawing
  • US20240070119A1 patent drawing
  • US20240070119A1 patent drawing

AI summary

An information processing apparatus includes a processor configured to: obtain, as log information of an operation performed on a digital file stored in a common region of the information processing apparatus, a first operation log recorded in the information processing apparatus and a second operation log recorded in a client device which has downloaded the digital file; and classify each of the obtained first operation log and second operation log as an operation log which is chronologically fixed or as an operation log which is not chronologically fixed, based on a recording time at which each of the first and second operation logs is recorded and a time at which the second operation log is obtained.