Web Server Cookie Tracking for Printer Access History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network systems lack efficient mechanisms for managing printer status and user interaction data, particularly in recording access history and providing support for peripheral devices like printers, which limits vendor insights and user experience.
Innovation Solution
A communication system comprising a printer, a portable terminal, a web server, a log server, and a service server, where the portable terminal activates an installer, transmits device information, and records access history, enabling the web server to generate cookie files and virtual URLs for accessing support pages and log servers, while the service server manages printer status and consumables information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If a web server transmits web page data to terminal devices without tracking mechanisms, then user access patterns remain unrecorded, but implementing tracking requires additional system complexity and user data management infrastructure
Solution Approach 1:
The system pre-generates cookie files containing unique identifiers and transmits them to terminal devices during initial web page transmissions. This preliminary action enables automatic tracking of user access patterns without requiring complex real-time processing or additional user input, as the tracking mechanism is already in place before actual usage occurs
Solution Approach 2:
Cookie files serve as intermediary carriers that bridge the web server and log server. These files contain unique identifiers that enable the log server to track and record user access patterns without requiring direct complex communication protocols between the web server and log server, simplifying the overall system architecture
2Loss of information
If the system implements comprehensive access tracking and status management, then vendor insights into usage patterns improve, but the complexity of managing cookies, URLs, and server communications increases
Solution Approach 1:
The system divides the tracking functionality into separate modular components: the web server handles cookie generation and transmission, the log server manages access pattern recording and analysis, and the terminal device stores and transmits cookie information. This segmentation allows each component to perform its function independently, reducing overall system complexity while maintaining comprehensive tracking capabilities
Solution Approach 2:
The system uses virtual URLs as simplified copies or representations of actual resource locations. Instead of managing complex direct mappings between users and resources, the system creates virtual URL representations that can be easily tracked and analyzed by the log server, reducing data management complexity while preserving usage pattern information
3Measurement precision
If the web server generates and transmits cookie files with unique identifiers, then user access can be tracked accurately, but this requires additional processing time and server resources
Solution Approach 1:
The system implements tracking only for essential user access patterns rather than attempting to monitor all possible user interactions. The cookie files contain only the necessary unique identifiers and basic access information required for accurate tracking, avoiding excessive data collection and processing that would slow down web page transmission
Solution Approach 2:
The terminal device automatically stores and manages the received cookie files, and automatically transmits them back to the web server during subsequent requests. This self-service mechanism eliminates the need for the web server to actively manage or process tracking data for each user interaction, maintaining tracking accuracy while minimizing server processing overhead
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A web server (400) comprising: a server-side related-information receiving unit for, receiving from a terminal device (200), target-related information relating to a target peripheral device (100); a specific data transmitting unit for transmitting, after receiving the target-related information, specific data to the terminal device (200); a page request receiving unit for receiving a first page request from the terminal device (200) after transmitting the specific data; a first web page data transmitting unit for transmitting, after receiving the first page request, the first web page data to the terminal device (200); a process executing unit for executing, after receiving the first page request, a specific process for storing a first URL corresponding to the first web page data accessed by the terminal device (200) in response to the instruction of the user and the target-related information corresponding to the specific data included in the first page request, in association with each other in a first memory.