Session Token Manager for Web Service Resource Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current session management in web services is inefficient, leading to excessive resource consumption in terms of time and memory, as new sessions are often established for each message exchange, particularly when users invoke multiple web services.
Innovation Solution
A session token manager system that allows clients to reuse previously established sessions by managing a pool of session tokens, where a check out message with user credentials determines an available session token from a pool, eliminating the need for repeated session establishment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new session is established for each message exchange, then security requirements are met, but processing time and memory consumption increase significantly
Solution Approach 1:
The system performs preliminary session establishment and token generation during the authentication phase. Once a session token is obtained, subsequent message exchanges can reuse the same session without re-establishing it, thereby reducing processing time while maintaining security through token-based identification
Solution Approach 2:
Instead of creating a new session for each message, the system copies the session state by using a session token that references the existing session. This allows multiple clients to access the same underlying session without duplicating the entire session state, reducing memory consumption and processing overhead
2Reliability
If a new session is established for each message exchange, then access control is ensured, but memory resources are consumed excessively
Solution Approach 1:
The system uses a session token as a reference copy that points to the actual session state stored on the server. This allows the client to store only the lightweight token rather than the complete session state, significantly reducing memory consumption while maintaining access control through token validation
Solution Approach 2:
The system extracts the essential session identification information into a separate session token that can be stored and transmitted independently. This separates the access control function from the session state, allowing memory-efficient storage of only the token rather than the entire session
3Measurement precision
If session management creates new tokens for each session, then user identification is accurate, but processing resources are wasted
Solution Approach 1:
The system performs the session token generation and user identification in advance during the authentication phase. Once identified, the same token can be reused for multiple operations, maintaining accurate user identification while eliminating redundant processing resources
Solution Approach 2:
The system discards the need to create new session tokens for each message exchange and recovers the existing token from the pool of available tokens. This allows accurate user identification through token validation while avoiding the processing resources that would be needed to create and manage multiple new tokens
Data Source
AI summary
A computer network for managing session tokens may include a client operable to run a client application; a web server hosting at least one web service; and a session token manager. The session token manager may be operable to receive a check out message along with user credentials from the client application, wherein the user credentials identify a user operating the client application; process the check out message to determine a session token from a pool of session tokens managed for the user; and send a token identifier (token ID) to the client application pointing to the determined session token, wherein the session token can be used by the client application to point to and/or to re-use a previously established session with the web service without re-establishing a new session.