TWAMP Configuration Controller for X2 Service Flow Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G IP RAN networks, TWAMP detection for X2 service flows is inaccurately configured, leading to redundant and invalid configurations, which challenges device capacity and efficiency.
Innovation Solution
A method and controller that determine X2 service flows based on destination IP addresses, using packet formats with role, message type, response value, source, and destination IP address fields to automatically send configuration information for TWAMP detection to ingress and egress network devices, improving detection efficiency and enabling batch deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If TWAMP detection is deployed for any two CSGs, then detection coverage is improved, but redundant and invalid configurations increase
Solution Approach 1:
The patent extracts and removes invalid TWAMP detection configurations by identifying configurations where the egress CSG does not have an X2 service relationship with the ingress CSG. The controller filters out these redundant configurations, keeping only valid X2 service flow detections, thereby reducing the quantity of redundant configurations while maintaining necessary detection coverage.
Solution Approach 2:
The patent implements a feedback mechanism where the controller receives service flow information from CSGs, analyzes the X2 service relationships, and sends back precise TWAMP detection configuration instructions. This feedback loop ensures that only necessary and valid configurations are deployed, avoiding redundant configurations while maintaining comprehensive detection coverage for actual X2 services.
2Measurement precision
If TWAMP detection is configured manually for X2 services, then configuration accuracy is improved, but deployment complexity increases
Solution Approach 1:
The patent enables the system to self-configure TWAMP detection for X2 services. The controller automatically receives service flow information, identifies X2 service relationships between CSGs, and generates appropriate TWAMP detection configurations without manual intervention. This self-service approach maintains configuration accuracy while significantly reducing deployment complexity.
Solution Approach 2:
The patent performs preliminary analysis of service flow information and X2 service relationships before generating TWAMP detection configurations. The controller pre-identifies valid X2 service flows and prepares configuration instructions in advance, ensuring configuration accuracy is maintained while automating the deployment process and reducing complexity.
3Reliability
If TWAMP detection is deployed broadly across all CSG pairs, then detection completeness is improved, but device capacity is challenged
Solution Approach 1:
The patent extracts and removes invalid TWAMP detection configurations by identifying configurations where the egress CSG does not have an X2 service relationship with the ingress CSG. This filtering process reduces the number of active TWAMP detections to only those necessary for actual X2 services, thereby challenging device capacity less while maintaining detection completeness for valid services.
Solution Approach 2:
The patent changes the configuration parameter from deploying TWAMP detection for all possible CSG pairs to deploying only for CSG pairs with confirmed X2 service relationships. This parameter change reduces the scale of TWAMP detection deployment, lowering device capacity requirements while maintaining completeness for actual X2 services through automated service flow analysis.
Data Source
AI summary
A configuration method and a controller are provided. The configuration method is applied to a network on which detection is performed by using the two-way active measurement protocol (TWAMP), and may include: receiving, by a controller, a request packet sent by an ingress network device, where the ingress network device is a network device through which a service flow flows into the network, and the request packet includes a destination IP address of the service flow; and determining, by the controller, based on the destination IP address, that the service flow is an X2 service flow, and sending configuration information for TWAMP detection to the ingress network device and an egress network device, where the egress network device is a network device through which the service flow flows out of the network.