Shared Browser Event Database for Multi-Tab Sync Collisions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for browser event synchronization in multi-tab software engagement are computationally expensive, inefficient, and prone to network collisions and high latency due to independent event transmissions by each browser tab, leading to network inefficiency and increased memory usage.

Innovation Solution

Implementing an object-oriented event management database on the client device to store and asynchronously process browser events, allowing batch transmission and synchronization, with safeguards to prevent collisions by managing events with timestamps and namespace counters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each browser tab independently transmits events to the server, then event data is captured, but network traffic increases and collisions occur

Engineering Contradiction:

Improveevent data capture reliabilityVSAvoidnetwork traffic efficiency

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

Multiple browser tabs with the same origin share a common event management database instead of each tab maintaining separate databases. This merging approach consolidates event storage and transmission coordination, reducing redundant network traffic while ensuring all events are captured reliably.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The event management database acts as an intermediary between browser tabs and the server. It receives events from multiple tabs, manages their transmission timing, and coordinates with the server, thereby reducing direct network collisions while maintaining reliable event capture.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If events are processed synchronously on the primary execution thread, then event handling is straightforward, but processing speed decreases

Engineering Contradiction:

Improveevent handling simplicityVSAvoidevent processing speed

Core Design Contradiction:

Ease of operationVSSpeed

Solution Approach 1:

The event processing system is segmented into multiple asynchronous worker threads that operate independently from the primary execution thread. This segmentation allows event processing to occur in parallel without blocking the main thread, improving processing speed while maintaining operational simplicity through the event database interface.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Events are stored in the event management database in advance before being processed by worker threads. This preliminary storage action allows the primary execution thread to quickly log events without performing complex processing, while asynchronous workers handle the heavier processing tasks in the background.

Inventive Principle:

Principle #10Preliminary action

3Quantity of substance

If multiple tabs transmit events simultaneously, then event data is captured comprehensively, but network collisions and latency increase

Engineering Contradiction:

Improveevent data volumeVSAvoidnetwork latency

Core Design Contradiction:

Quantity of substanceVSLoss of time

Solution Approach 1:

Events are stored in the shared event management database in advance before transmission. This preliminary storage allows comprehensive event capture from multiple tabs without immediate transmission, and enables coordinated batch transmission that reduces network latency by avoiding simultaneous individual transmissions.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses periodic or triggered transmission of events from the database to the server, rather than immediate transmission upon event occurrence. This periodic action consolidates multiple events into efficient transmission batches, reducing network collisions and overall latency while capturing comprehensive event data.

Inventive Principle:

Principle #19Periodic action

4Reliability

If redundant event transmissions are allowed, then event data is ensured to be transmitted, but network efficiency decreases

Engineering Contradiction:

Improveevent transmission reliabilityVSAvoidnetwork efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The shared event management database merges event storage across multiple tabs, enabling the system to track which events have been transmitted. This consolidation allows the system to ensure reliable transmission of each unique event once, eliminating redundant transmissions while maintaining transmission reliability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system implements feedback mechanisms where the event management database tracks transmitted events and provides information to prevent retransmission. This feedback loop ensures that each event is transmitted reliably exactly once, improving network efficiency by eliminating redundant transmissions.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS20260104947A1Browser event synchronization management in a federated system

Publication Date: 2026.04.16 ATLASSIAN PTY LTD

AI summary

Various embodiments of the present invention provide methods, apparatuses, systems, computing devices, and/or the like that are configured to enable effective and efficient browser event synchronization management in a federated system. For example, certain embodiments of the present invention provide methods, apparatuses, systems, computing devices, and/or the like that are configured to manage browser event synchronization using techniques that utilize object-oriented event management database stored at client computing device and asynchronous browser event processing.