HTTP Header Event Counting for Network Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for tracking event counts in computer networks, such as cookies and unique IDs, face increasing legal and technical restrictions, making it difficult to reliably and efficiently determine event frequencies, especially in third-party scenarios like marketing or fraud detection.
Innovation Solution
A method and system that utilize timestamp parameters in HTTP responses to store and increment event counts, allowing event frequency determination by replacing time stamp parameters with counting parameters, which can be stored on both client and server devices, enabling efficient tracking of event occurrences across a computer network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional unique ID tracking methods are used, then event counting capability is achieved, but reliability deteriorates due to legal and technical restrictions on user tracking
Solution Approach 1:
The patent extracts the event counting function from the unique ID tracking system. Instead of relying on unique IDs that are subject to legal and technical restrictions, the invention uses HTTP response headers (specifically Cache-Control and Last-Modified headers) to carry event count information. This separation allows event counting to continue while avoiding the restrictions imposed on traditional tracking methods.
Solution Approach 2:
The patent introduces HTTP response headers as an intermediary mechanism for event counting. The Cache-Control and Last-Modified headers serve as mediators that carry event count information between server and client without requiring unique ID assignment. This intermediary approach bypasses the restrictions on traditional tracking while maintaining the ability to count events reliably.
2Reliability
If cookies are used for event tracking, then event count storage is possible, but ease of operation deteriorates due to browser technology restrictions
Solution Approach 1:
The patent extracts the event count storage function from cookies. Instead of storing event counts in cookies which are heavily restricted by browser technology, the invention uses HTTP response headers (Cache-Control and Last-Modified) to encode and transmit event count information. This extraction allows event counting to function without relying on cookie storage capabilities.
Solution Approach 2:
The patent makes HTTP response headers serve multiple functions: they not only control caching behavior (original purpose) but also carry event count information (new function). The Cache-Control and Last-Modified headers are used both for their traditional caching purposes and as vehicles for transmitting event counting data, eliminating the need for separate cookie storage mechanisms.
3Adaptability or versatility
If unique ID assignment is implemented, then user tracking capability is achieved, but device complexity increases due to consistent ID management requirements
Solution Approach 1:
The patent extracts the event counting function from the unique ID management system. By using HTTP response headers to carry event count information, the invention eliminates the need for unique ID assignment and management infrastructure. This extraction simplifies the system by removing the complex unique ID management requirements while maintaining event tracking capability.
Solution Approach 2:
The patent enables the HTTP protocol itself to serve the event counting function through its existing header mechanisms. The Cache-Control and Last-Modified headers automatically carry event count information as part of the standard HTTP response flow, without requiring additional unique ID management systems. The system uses existing protocol elements to provide the tracking function, eliminating the need for separate complex management infrastructure.
Data Source
Figure 1
Figure 2
AI summary
The present disclosure refers to a method for determining an event repeatedly conducted in a computer network (1), the method comprising: providing a computer network (1) having a client device (2) and a server device (3); receiving a first request for request data in the server device (3), wherein the first request comprises a network address indicative of a network resource configured to provide the request data in response to a request for the request data and a location of the network resource in the computer network (1); in response to receiving the first request, providing first response data in the server device (3), wherein the first response data comprise time stamp data indicative of one or more time stamp parameters selected from the following group: year, month, day, hour, minute, second, and a fraction of a second, at least one time stamp parameter is replaced by a counting parameter, and the counting parameter is assigned an initial value; receiving the first response data in the client device (2) from the server device (3); receiving a second request for the request data in the server device (3), wherein the second request comprises the network address indicative of the network resource configured to provide the request data and the location of the network resource in the computer network (1), and the first time stamp data with the at least one time stamp parameter assigned the initial value; in response to receiving the second request, providing second response data in the server device (3), wherein the second response data comprise the second time stamp data with the at least one time stamp parameter assigned the initial value being adjusted to a first counting value; receiving the second response data in the client device (2) from the server device (3); and determining event counting information from the first counting value, the event counting information being indicative of an event frequency of requesting the request data. Further, a system for determining an event repeatedly conducted in a computer network (1) having a client device (2) and a server device (3), and a computer program are disclosed.