Time-Sensitive Network Segmentation for Deterministic Congestion Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The configuration of Time Sensitive Networks (TSN) is complex and time-consuming, and existing methods fail to adequately distinguish and prioritize critical data streams, leading to congestion and potential data loss.
Innovation Solution
A method for operating a TSN by dividing it into high-importance and low-importance segments, using priority labels and classes to preempt critical data streams, and coordinating these segments through a border network element to ensure deterministic forwarding, even in congested conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If TSN configuration is performed manually without segmentation, then comprehensive control over all data streams is achieved, but the configuration becomes complex and time-consuming
Solution Approach 1:
The TSN network is divided into multiple segments (first segment with first network elements and second segment with second network elements) that can be independently configured and managed. Each segment handles its own data streams locally, reducing the overall configuration complexity while maintaining comprehensive control through coordinated segment operation.
2Reliability
If all data streams are treated with equal priority handling, then simple forwarding rules are maintained, but critical data streams cannot be distinguished and are lost during congestion
Solution Approach 1:
Different network elements within the same segment are assigned different priority classes (first priority class for some data streams, second priority class for others) based on their specific requirements. This local differentiation allows critical data streams to be identified and prioritized without requiring complex global classification rules, enabling reliable delivery during congestion while maintaining manageable complexity.
3Reliability
If priority labels are not coordinated between segments, then independent segment operation is simplified, but congestion handling at segment boundaries becomes unpredictable and non-deterministic
Solution Approach 1:
Border network elements acting as intermediaries between segments coordinate priority label mappings to ensure deterministic congestion handling. These border elements translate and harmonize priority classifications from different segments, guaranteeing that critical data streams maintain their priority status across segment boundaries while allowing segments to operate independently with simplified internal coordination.
4Extent of automation
If manual engineering is required for TSN configuration, then precise control over network behavior is achieved, but automation and rapid deployment are prevented
Solution Approach 1:
Network elements automatically determine their own priority class based on pre-defined rules and characteristics of the data streams they handle, without requiring manual configuration. This self-service approach enables rapid automated deployment of TSN networks while maintaining precise control over network behavior through algorithmic priority assignment that adapts to specific network conditions and requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method (100) for operating a time-sensitive network, TSN (1), wherein this TSN comprises at least a first, high-importance segment (1a) and a second, low-importance segment (1b), such that traffic within the first segment (1a) on the one hand and traffic within the second segment (1b) on the other hand pass through different sets of physical links (2a-2b; 2c-2e) in the TSN (1), the first segment (1a) is connected to a first port (4a) of a border network element (4) that connects the first (1a) and second (1b) segments, and the second segment (1b) is connected to a second port (4b) of this border network element (4), the method (100) comprising the steps of: • splitting (110), on network elements (3a-3e) in the first (1a) and second segments (1b), data streams (5a-5g) into a "preempting" class (7a) and a "preemptable" class (7b) based on a mapping from priority labels (6a-6g) attached to these data streams (5a-5g) to classes (7a, 7b); • forwarding (120), by the network elements (3a-3e), the data streams (5a-5g) to respective next-hop network elements (3a-3e, 4) wherein, at least in case of congestion on a link (2a-2e) to the respective next-hop network element (3a-3e, 4), the forwarding of "preempting" data streams takes precedence over the forwarding of "preemptable" data streams; and • forwarding (130), by the border network element (4), the data streams (5a-5g) received from both segments (1a, 1b) based on the priority labels (6a-6g) and the classes (7a, 7b) of the data streams (5a-5g), to at least one next-hop network element (8), wherein, at least in case of congestion on a link (2f) to the next-hop network element (8), the forwarding of "preempting" data streams (5a-5g) takes precedence over the forwarding of "preemptable" data streams (5a-5g), wherein: • the priority label (6a-6g) attached to the data stream (5a-5g) that has the highest priority within the first segment (1a) is different (111) from the priority label (6a-6g) attached to the data stream (5a-5g) that has the highest priority within the second segment (1b); and/or • the mapping between priority labels (6a-6g) and classes (7a, 7b) in the second segment (1b) is different (112) from the mapping between priority labels (6a-6g) and classes (7a, 7b) in the first segment (1a).