Telecommunication Network Traffic Control During Faults
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunications networks face congestion and increased waiting times during network faults due to an abnormally high influx of registration and subscription requests, as existing methods lack network operator control over terminal programming and fail to distinguish between different types of requests, leading to inefficient processing capacity.
Innovation Solution
The method involves prescribing a randomly selected registration and subscription refresh period within a defined range after a network fault, allowing the network to manage traffic peaks and prevent congestion by adjusting intervals based on normal operation values, thus enabling efficient spreading of requests and prioritizing registration over subscription requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If terminals send registration and subscription requests periodically after network faults, then user connectivity is maintained, but network congestion and processing capacity overload occur
Solution Approach 1:
The network operator prescribes refresh periods in advance for terminals during normal operation. When faults occur, terminals follow these pre-established periods to send refresh requests, preventing sudden traffic spikes while maintaining connectivity. This preliminary configuration of refresh timing resolves the contradiction by ensuring requests are spread out rather than concentrated.
Solution Approach 2:
The invention implements periodic refresh requests at predetermined intervals rather than continuous or random requests. By establishing regular periodic cycles for registration and subscription refresh, the network manages traffic flow predictably, preventing congestion while ensuring all terminals maintain their connections during and after faults.
2Adaptability or versatility
If the network processes all registration and subscription requests equally, then all services are maintained, but registration requests are delayed due to traffic peaks
Solution Approach 1:
The invention segments different types of requests (registration, subscription, refresh) and applies different processing strategies to each. By distinguishing between initial registration requests and subscription requests, and by managing them at different priorities, the network ensures registration is prioritized while still maintaining subscription services, thus resolving the time loss issue.
Solution Approach 2:
Different quality levels of service are applied to different request types. Registration requests receive higher priority and faster processing during traffic peaks, while subscription requests are handled with standard processing. This local differentiation of service quality allows the network to maintain all services while preventing registration delays.
3Stability of the object's composition
If terminals use fixed refresh periods, then request timing is predictable, but network traffic peaks occur during faults
Solution Approach 1:
The refresh period configuration is made dynamic rather than fixed. The network operator can adjust refresh periods based on network conditions and fault detection. During normal operation, standard refresh periods are used for predictability. When faults are detected, the system adapts by extending refresh periods or adjusting timing to prevent traffic peaks, thus resolving the contradiction between predictability and traffic distribution.
Data Source
AI summary
A method of regulating traffic in a telecommunications network, including the following steps: after the network receives an initial registration request, and if the network is capable of processing said initial registration request, it prescribes for the terminal that sent the request a registration refresh period randomly selected from a range defined by a predetermined minimum value (PREImin) and a predetermined maximum value (PREImax), and after the network receives a registration refresh request, it prescribes for the terminal that sent the request a registration refresh period equal to the value (PRE) provided for normal operation of the network.


