Network Access Control via Liveness Testing and Fixed Requestor Limits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data processing networks face issues with connections remaining in a half-ended state due to lack of timely 'end of connection' signaling, leading to rejected reconnection attempts, and existing liveness checking mechanisms are infrequent, resulting in delayed re-establishment of connections.
Innovation Solution
Implementing a method that determines whether a fixed number of requestors is exceeded, and if so, performs liveness testing on current connections to either reject new requests or grant access, thereby minimizing bandwidth impact by only incurring liveness checks when necessary, and actively managing durable subscriptions in publish/subscribe systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If liveness checking is performed frequently to detect connection failures quickly, then reconnection can be established faster, but bandwidth is wasted due to unnecessary checks on healthy connections
Solution Approach 1:
The system performs preliminary actions by proactively closing connections that have exceeded their idle timeout threshold before attempting reconnection. This prevents the half-ended state from persisting and ensures that reconnection attempts are made only when necessary, avoiding wasted bandwidth on already-failed connections while maintaining reliable re-establishment.
2Adaptability or versatility
If the destination accepts unlimited requestors, then access flexibility is improved, but connection management complexity increases and resource exhaustion risk rises
Solution Approach 1:
The system implements dynamic connection management by maintaining a fixed pool of idle connections that can be reused. Instead of statically allocating connections or allowing unlimited new connections, the system dynamically reuses existing idle connections up to a maximum threshold, balancing access flexibility with manageable connection overhead and preventing resource exhaustion.
3Speed
If idle connections are kept open for reuse, then reconnection speed is improved, but bandwidth is consumed by maintaining inactive connections
Solution Approach 1:
The system changes the parameter of connection idle timeout by introducing a configurable threshold that determines when idle connections should be closed. Connections are maintained in an idle state only until they exceed this timeout parameter, at which point they are proactively closed. This optimizes the balance between keeping connections available for fast reuse and releasing bandwidth when connections remain idle too long.
Data Source
AI summary
A method and system of controlling access to a destination (17, 23, 24) in a data processing network where the destination is limited to a fixed number of requesters responds to a new request (50) for access from a given requestor (20) by determining whether the fixed number would be exceeded. If the fixed number would not be exceeded (51), the new request is granted by connecting (52) the given requester to the destination. If the fixed number would be exceeded, the liveness of the or each current connection to a respective requester is tested (55). If the liveness test succeeds, the new request is rejected but if the liveness test fails, the new request is granted (52).