Access Session Management via Trunk Branch Data Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In network management systems with web-based interfaces, concurrent access sessions from different devices or browsers using the same account lead to poor user experience and performance issues due to shared status data, either resulting in inconsistent settings or excessive data storage.

Innovation Solution

Creating separate branch status data for each access session, which is updated independently and merged with trunk status data upon session end, allowing for user preference maintenance while reducing data storage and avoiding resource contention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a single set of status data is shared across all concurrent access sessions, then system resource usage is reduced, but user experience deteriorates due to inconsistent settings across different devices and browsers

Engineering Contradiction:

Improvedata storageVSAvoiduser experience

Core Design Contradiction:

Quantity of substanceVSEase of operation

Solution Approach 1:

The patent segments status data into two distinct types: trunk status data (shared across all sessions) and branch status data (specific to each access session). This segmentation allows each session to have its own customized settings while sharing common configuration data, thereby improving user experience without excessive resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by making status data properties session-specific where needed. Branch status data contains session-local customizations (such as device-specific display settings or browser-specific configurations) while trunk status data contains universal settings, ensuring each session receives appropriate localized data.

Inventive Principle:

Principle #3Local quality

2Ease of operation

If separate status data is created for each access session, then user experience is improved with consistent settings, but data storage increases significantly

Engineering Contradiction:

Improveuser experienceVSAvoiddata storage

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

By dividing status data into trunk and branch components, the patent avoids duplicating entire status data sets for each session. Only session-specific branch data is stored separately, while common data resides in the shared trunk, significantly reducing total storage requirements compared to complete duplication.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent merges trunk status data with branch status data to form the complete status data for each session. This combining approach allows the system to store a single copy of common data in the trunk while adding only necessary session-specific additions, minimizing redundant storage.

Inventive Principle:

Principle #5Merging (Combining)

3Quantity of substance

If a single set of status data is used by all concurrent access sessions, then data storage is reduced, but system performance deteriorates due to resource contention during concurrent access

Engineering Contradiction:

Improvedata storageVSAvoidsystem performance

Core Design Contradiction:

Quantity of substanceVSProductivity

Solution Approach 1:

The patent segments status data access by providing separate branch status data for each concurrent session. This segmentation allows multiple sessions to access and modify their own branch data independently without locking or contention on shared resources, thereby maintaining system performance during concurrent operations.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The branch status data acts as an intermediary layer between the shared trunk status data and individual session operations. This intermediary allows sessions to work with their own isolated data copies for frequently accessed fields, reducing direct contention on the trunk data while maintaining data consistency through controlled updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If separate status data is created for each access session, then resource contention is avoided, but data management complexity increases

Engineering Contradiction:

Improvesystem performanceVSAvoiddata management

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments status data into a hierarchical structure with trunk and branch levels, each serving specific purposes. This structured segmentation simplifies data management by clearly defining which data is shared and which is session-specific, making it easier to track and manage compared to completely separate data sets for each session.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent combines trunk and branch status data to form complete session data, providing a unified data model that simplifies management operations. This merging approach allows the system to handle data as a cohesive structure rather than managing entirely separate data sets for each session, reducing operational complexity.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10516742B2Access session management

Publication Date: 2019.12.24 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

A method includes the following: creating trunk status data for each user account, in response to detecting a plurality of concurrent access sessions relating to a single user account, creating respective branch status data for each access session; updating the branch status data in accordance with user access operations; and when an access session relating to a user account ends, updating the trunk status data for said user account based on a comparison of the branch status data of the access session which has ended with the trunk status data for said user account.