E-MTA Stale Connection Detection and Resource Release
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication networks, particularly those following the PacketCable standard, face challenges in detecting and removing stale connections due to system glitches or disabled features, leading to continued bandwidth allocation for unused connections.
Innovation Solution
A method is implemented at the user device, using a timer and management information base values to detect on-hook events, designate connections as potentially abandoned, and send messages to the CMTS and CMS to release resources and delete connections, ensuring efficient bandwidth reuse.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the CMS is used to detect and remove stale connections, then connection management follows the PacketCable standard, but system glitches or disabled features cause stale connections to persist and bandwidth to be wasted
Solution Approach 1:
The E-MTA performs self-service by autonomously detecting stale connections and initiating their removal without requiring CMS intervention. The device monitors its own connection states, determines when connections are stale based on local criteria, and sends disconnect messages to the CMTS, making the system self-sufficient and independent of CMS reliability
Solution Approach 2:
The system implements feedback mechanisms where the E-MTA continuously monitors connection states and receives status information from the CMTS. This feedback loop allows the E-MTA to detect when connections have become stale and trigger appropriate removal actions, creating a closed-loop control system that adapts to actual connection states
2Reliability
If the CMS maintains connections for extended periods after on-hook conditions, then emergency calls can be preserved, but stale connections accumulate and consume bandwidth
Solution Approach 1:
The connection management system dynamically adjusts connection retention based on real-time conditions. The E-MTA monitors connection activity and automatically initiates removal of inactive connections while allowing the CMS to maintain emergency connections when needed, creating a flexible system that adapts to different operational requirements
Solution Approach 2:
The system changes the parameter of connection timeout duration based on connection type and activity. Normal connections are terminated after a short idle period, while emergency connections can be maintained longer. The E-MTA uses local timing parameters to distinguish between temporary idle states and truly stale connections, optimizing bandwidth usage
3Productivity
If the E-MTA independently manages connection removal, then bandwidth is released promptly, but the device complexity increases
Solution Approach 1:
The patent extracts the stale connection detection and removal functionality from the centralized CMS and places it directly in the E-MTA. This decentralization allows the E-MTA to independently manage its own connections, releasing bandwidth promptly without waiting for CMS processing, while keeping the added complexity localized to the E-MTA software
Data Source
AI summary
A device containing an MTA, executing a connection deletion method, determines that a connection at one of its endpoints may be abandoned after a predetermined amount of time after an on-hook event following a first call. If the MTA determines that the CMS it is coupled to has begun managing a new, or second, call, the MTA, sends a message to the CMTS it is coupled to requesting deletion of the first call, and the resources associated with it. The MTA also sends a message to the CMS requesting deletion of the connection at the endpoint of the MTA device.