FlexE Overhead Frame Route Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In FlexE networks, existing route tracking mechanisms are ineffective due to the lack of support for multicast in the 1.5 layer network, making it difficult to identify and parse Ethernet frames for route detection, and the absence of a forwarding table for IP packets, which hinders the identification of specific packets and routes.
Innovation Solution
A method is introduced to use FlexE overhead frames to carry route detection messages, including a sequence number, message type, source client information, and route information entries, which are encapsulated and extracted to dynamically discover and record transmission routes, allowing for real-time identification of segment-to-segment routes and fault detection without occupying data channel bandwidth.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP routing and forwarding table search is used for route tracking, then route detection can be implemented, but it is not applicable to FlexE 1.5 layer network which does not use forwarding tables
Solution Approach 1:
The patent introduces a route detection message as an intermediary carrier that transports route query information through FlexE overhead frames. This message structure enables route tracking functionality in FlexE networks without requiring traditional IP forwarding tables, as the message itself carries all necessary route identification information through slot and client mapping relationships.
2Reliability
If multicast forwarding is used for route detection packets in Ethernet network, then route tracing can be achieved, but multicast is not supported in FlexE 1.5 layer network
Solution Approach 1:
Instead of using multicast forwarding to achieve route detection, the patent inverts the approach by embedding route detection messages directly within the FlexE overhead frame structure. This allows route detection to function unicast-style through the existing FlexE point-to-point connectivity, eliminating the need for multicast support while maintaining route tracing capability.
3Reliability
If specific Ethernet frame types are used for route tracing, then route detection packets can be identified, but Ethernet frames in FlexE data stream cannot be parsed and identified
Solution Approach 1:
The patent extracts the route detection functionality from traditional Ethernet frame structures and relocates it to FlexE overhead frames. By placing route detection messages in the overhead section rather than within the data payload, the system enables easy identification and parsing without disrupting the FlexE data stream, as overhead frames are separately processed from client data.
4Loss of information
If route detection messages are transmitted through data channel, then route information can be obtained, but data channel bandwidth is occupied
Solution Approach 1:
The patent segments the FlexE frame structure into distinct overhead and data payload sections. Route detection messages are transmitted exclusively through the overhead section, which is separately processed from the client data channels. This segmentation allows route information acquisition without consuming data channel bandwidth, as the overhead and data portions are independently handled.
Data Source
Figure 1
Figure 2
Figure 3~5
AI summary
Embodiments of this application provide a method for obtaining a target transmission route, a related device, and a system. The method is applied to a flexible Ethernet FlexE networking network and includes: receiving a first message that is sent by a second node for requesting to query for a transmission route of a first FlexE client; and sending a second message to the second node, where a route information entry in the second message includes route information of the FlexE client on each node. Ingress information and egress information that are of a FlexE client on a route node are recorded as a transmission route of each hop. A segment-to-segment transmission route in the FlexE network can be dynamically found in real time, a planned and deployed transmission route is compared with an actually found route, to evaluate a network running status, connection connectivity of the transmission route can be further detected, and a fault node on a transmission route in the FlexE network can be located.