Frame Loss Measurement in Multipoint E-LAN Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for measuring frame loss in multipoint E-LAN networks are inefficient and require significant computational resources, especially in networks with multiple endpoints, as they need to process a high volume of messages to achieve accurate frame loss ratio measurements.
Innovation Solution
The method involves enhanced continuity check messages exchanged between network interface devices to collect frame count data, allowing for the calculation of frame loss by comparing ingress and egress frames, reducing the computational burden by optimizing message exchanges and frame count collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If synthetic frame loss measurement messages are sent every 100ms to achieve accurate frame loss ratio detection, then measurement precision is improved, but device complexity and processing load increase significantly
Solution Approach 1:
The patent segments the frame loss measurement task by dividing the VLAN into multiple measurement domains or groups. Instead of requiring every endpoint to participate in all n(n-1)/2 point-to-point measurement sessions, the system divides the measurement responsibility across multiple segments or controllers, reducing the processing burden on individual CPUs while maintaining overall measurement accuracy.
Solution Approach 2:
The patent introduces an intermediary element (such as a network controller or measurement server) that centralizes the processing of frame loss measurements. This intermediary collects frame count data from multiple endpoints and performs the computational analysis, reducing the CPU processing requirements at individual network interface devices while maintaining measurement precision.
2Reliability
If n(n-1)/2 point to point loss measurement sessions are established in a VLAN with n endpoints, then measurement completeness is improved, but quantity of messages and processing load increase
Solution Approach 1:
The patent implements a universal measurement approach where a single measurement session or controller can serve multiple endpoints simultaneously. Instead of requiring dedicated point-to-point sessions for each endpoint pair, the system uses multi-functional measurement sessions that can monitor frame loss across multiple endpoints, reducing the total number of messages required while maintaining measurement completeness.
Solution Approach 2:
The patent merges multiple point-to-point measurement sessions into consolidated measurement sessions. By combining the measurement functions and sharing resources among multiple endpoint pairs, the system reduces the total quantity of measurement messages from n(n-1)/2 to a smaller number of consolidated sessions, while still achieving comprehensive frame loss detection.
3Reliability
If continuity check messages are exchanged at high rate to support deterministic processing, then reliability is improved, but use of energy and processing resources increase
Solution Approach 1:
The patent implements periodic continuity check message exchanges at optimized intervals rather than continuous high-rate exchanges. By carefully selecting the periodic interval and using efficient message formats, the system maintains deterministic processing guarantees while reducing the frequency of message exchanges and associated CPU energy consumption.
Solution Approach 2:
The patent changes key parameters of the measurement system, such as message exchange intervals, message size, and processing timing, to optimize the balance between reliability and energy consumption. By adjusting these parameters, the system achieves deterministic processing with reduced message rates and lower CPU energy requirements compared to the conventional high-rate approach.
Data Source
AI summary
Systems and methods for measuring frame loss in multipoint networks are provided. In one embodiment, a method for calculating frame loss comprises: performing a first continuity check message exchange between a first and a plurality of other devices, the first exchange comprises the first device collecting a first set of frame count data from each of the first and other devices, the first set of frame count data associated with a first instance of time by a first sequence identifier; performing a second continuity check message exchange between the first and plurality of other devices, the second exchange comprises the first device collecting a second set of frame count data from the first other devices, the second set of frame count data associated with a second instance of time by a second sequence identifier; and calculating a frame loss measurement by accounting for frame Ingress and frame Egress.