Client Device Counter Information Consistency via Reacquisition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In device management systems, acquiring accurate counter information is challenging due to inconsistencies when events increment related counts, leading to incorrect data, especially since information processing devices are always operational and generate varied data for users, departments, and functions, making it inconvenient for users.
Innovation Solution
A client device that communicates with a server via a network, acquires and reacquires counter information, determines if jobs have been performed, and transmits the reacquired data to ensure consistency, using a multifunctional device with a CPU, RAM, and storage units to manage and analyze event logs, counter information, and power states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If counter information is acquired continuously while the device is operational, then the device remains always available for user operations, but the counter information becomes inconsistent when events increment counts during acquisition
Solution Approach 1:
The system performs preliminary actions by recording event logs and counter information in local storage before transmission, and uses preliminary checks to determine if jobs were executed during acquisition. This allows the system to prepare data in advance and validate its consistency before sending to the server, resolving the contradiction between continuous availability and data accuracy.
Solution Approach 2:
The system implements feedback mechanisms by transmitting both counter information and associated event logs to the server, which then validates the data consistency. The server can request retransmission or correction if inconsistencies are detected, creating a feedback loop that ensures accurate counter information while maintaining continuous device operation.
2Quantity of substance
If multiple counter information items are acquired simultaneously for different users and functions, then comprehensive billing data is collected, but consistency between the acquired counter information cannot be maintained
Solution Approach 1:
The system segments counter information acquisition by organizing data into separate event logs and counter records for different users, departments, and functions. Each segment is independently recorded with timestamps and associated event identifiers, allowing comprehensive collection while maintaining the ability to validate consistency within each segment separately.
Solution Approach 2:
The system introduces event logs as an intermediary between counter information acquisition and validation. These logs record all events that increment counters, serving as proof of accuracy. The intermediary allows the system to collect comprehensive counter data while providing a mechanism to verify consistency through the associated event records.
3Measurement precision
If job exclusion is implemented during counter information acquisition, then counter data consistency is ensured, but user convenience is significantly reduced
Solution Approach 1:
Instead of excluding jobs during acquisition, the system performs preliminary recording of all counter information and event logs to local storage. This preliminary action allows continuous job execution while capturing accurate data, eliminating the need to interrupt user operations to ensure consistency.
Solution Approach 2:
The system uses feedback validation after acquisition by checking whether jobs were executed during the acquisition period and adjusting or retransmitting data as needed. This feedback mechanism ensures counter information consistency without requiring job exclusion, thereby maintaining user convenience.
Data Source
AI summary
Provided is a client device configured to communicate with a server via a network, the client device comprising: one or more memories; and one or more processors that execute a set of instructions to: acquire counter information which is totaled according to performing a job by the client device and is stored in the one or more memories; determine whether the client device has been performed at least one job during acquiring the counter information; reacquire counter information in a case where it is determined that the client device has been performed at least one job during acquiring the counter information; and transmit the reacquired counter information to the server.