Multi-Tiered Session Lifecycle Management via Reference Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional two-tiered client-server architectures are inefficient for large enterprises due to the tight coupling of business logic, presentation logic, and user interface, making it difficult to maintain and scale, especially in dynamic environments where frequent changes are required.

Innovation Solution

A multi-tiered enterprise network architecture is implemented, where presentation logic, business logic, and database are logically separated, with session management layer managing session lifecycles across different layers using session objects with strong, weak, and soft references, and sharing objects in a shared memory environment to improve scalability and response time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a two-tiered client-server architecture is used, then the system structure is simple, but the coupling between business logic, presentation logic, and user interface is tight, making maintenance and scaling difficult

Engineering Contradiction:
Improvesystem structureVSAvoidmaintainability and scalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent divides the monolithic client application into separate logical layers: presentation logic (UI), business logic, and data access logic. Each layer is independently manageable, allowing the business logic to be updated without affecting the user interface, thus improving maintainability and scalability while keeping the overall system structure relatively simple

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If client-side applications are updated frequently to adapt to changing business rules, then adaptability improves, but the difficulty of installing and maintaining client-side applications increases

Engineering Contradiction:
Improveresponse to business rule changesVSAvoidclient installation and maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent extracts the business logic from the client-side application and places it in a separate, centrally-managed component that can be updated independently. This allows business rules to be changed on the server side without requiring client updates, eliminating the maintenance burden while maintaining adaptability

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If session objects are managed independently at each layer, then layer independence is maintained, but session lifecycle consistency across layers becomes difficult to manage

Engineering Contradiction:
Improvelayer independenceVSAvoidsession lifecycle consistency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a session management mechanism where session objects are created at one layer and tracked across layers through reference passing. When a session object is created at the presentation layer, it generates corresponding session objects at the business logic layer, which in turn generate session objects at the data access layer. The system monitors these relationships and ensures that when a parent session is invalidated, all dependent sessions are also invalidated, maintaining lifecycle consistency while preserving layer independence

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8281014B2Session lifecycle management within a multi-tiered enterprise network
Publication Date: 2012.10.02 SAP SE
  • US8281014B2 patent drawing
  • US8281014B2 patent drawing
  • US8281014B2 patent drawing

AI summary

A system and method are described for managing session lifecycles within a multi-tiered enterprise network. In one embodiment, a plurality of session objects are generated at different layers of the enterprise network in response to a client request. Each of the session objects store session data defining a state of interaction with the client. In addition, one embodiment of the invention manages the lifecycle of a first session object based on corresponding lifecycles of one or more related session objects and also the type of relationship existing between the first session object and the one or more related session objects. In one embodiment, the defined relationship types include strong references, weak references, and soft references.