Local Log Repository Indexing for Visitor Access Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers face challenges in determining which content characteristics attract and retain viewers, and aggregating visitor data in a meaningful manner to track web content access effectively, while existing systems struggle with size constraints in local log repositories and high network delays.
Innovation Solution
A method and system for locally aggregating and indexing visitor data in a searchable and size-constrained local log repository, where visitor logs are indexed with a usage-tracking field to predict future usage and prune less frequently accessed data, reducing network delays and costs by allowing for efficient data retrieval and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If visitor data is stored in a local log repository for fast access, then response time is reduced, but the repository size becomes constrained
Solution Approach 1:
The patent extracts only the most frequently accessed visitor data from the central server and stores it locally in the log repository. This selective extraction allows the system to maintain fast local access for common queries while avoiding the storage overhead of keeping all possible data locally, thus resolving the contradiction between response time and repository size.
Solution Approach 2:
The system performs preliminary actions by pre-fetching and caching visitor data that is likely to be needed for future reports. The log repository is proactively populated with data before it is actually requested, which reduces response time when queries are made while controlling the amount of data stored through intelligent prediction of future needs.
2Adaptability or versatility
If indexing fields are added to enable future reports, then adaptability is improved, but the repository consumes more space
Solution Approach 1:
The patent implements a universal indexing scheme where a single set of index fields is designed to support multiple different report types and query patterns. Instead of creating separate storage structures for each possible report, the same indexed data can be reused across various reporting needs, achieving high adaptability without proportionally increasing repository size.
Solution Approach 2:
The system changes parameters by dynamically selecting which indexed fields to query based on the specific report requirements. Rather than storing all possible data attributes permanently, the indexing structure allows flexible parameter selection at query time, enabling diverse reports from a compact stored representation.
3Reliability
If data is frequently accessed from the central server, then data freshness is improved, but network costs and delays increase
Solution Approach 1:
The patent applies local quality by maintaining different data freshness levels in different locations. Frequently accessed data is kept fresh in the local log repository through selective updates, while less frequently accessed data can remain older in the central server. This localized optimization reduces network traffic compared to keeping all data uniformly fresh at the central server.
Solution Approach 2:
The system implements periodic updates where the local log repository is refreshed at intervals rather than continuously. This periodic synchronization maintains acceptable data freshness for local queries while significantly reducing network communication costs compared to real-time or continuous data retrieval from the central server.
Data Source
AI summary
A method and system for tracking visitors' access to web content using a searchable and size-constrained local log repository is disclosed. A repository indexer receives visitor logs from a remote source and indexes the logs to include a usage field indicating when or how frequently an associated visitor log was accessed from a local log repository by a report request manager. The local log repository stores the logs and is size constrained. A repository manager removes a subset of the logs in the local log repository based on parameters within the subset of the logs' usage field. The report request manager receives a request from a requestor for a report indicating visitors' access to a content object, searches for logs within the local log repository pertinent to the request, aggregates data across the logs responsive to the search, and generates a report presenting the aggregated data.