DNS Server Stream Identifier Mapping for TSN Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Time-Sensitive Networking (TSN) networks, the short length of stream identifiers (64 bits) leads to 'shortage management' issues, requiring manual complex management and limiting the ability to add new applications without re-planning, especially in industrial automation settings where resources are scarce.
Innovation Solution
A method using two types of stream identifiers, where a longer 'first type' is used for applications and a shorter 'second type' for the control plane, with the DNS server storing entries linking these identifiers, allowing for automated management and 'plug and play' functionality without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual management of stream identifiers is used, then stream ID assignment can be controlled, but system complexity and management overhead increase significantly
Solution Approach 1:
The patent introduces a DNS server as an intermediary between stream subscribers and the TSN control plane. The DNS server stores mappings between human-readable stream names and 64-bit stream IDs, automatically resolving names to IDs without manual intervention. This mediator handles the complexity of stream ID management centrally, allowing individual subscribers to simply use meaningful names while the DNS infrastructure manages the actual ID assignments and conflicts.
2Quantity of substance
If short 64-bit stream identifiers are used in TSN control plane, then memory requirements in network nodes are reduced, but automatic management and plug-and-play capability are limited
Solution Approach 1:
The patent segments the stream identification function into two parts: (1) human-readable stream names that applications use for identification and configuration, and (2) 64-bit stream IDs that the TSN control plane uses for actual stream establishment and resource management. The DNS server maintains the mapping between these two identifier types, allowing applications to work with meaningful names while the network infrastructure uses compact binary IDs, thus enabling plug-and-play without increasing node memory requirements.
3Reliability
If manual stream ID planning is performed, then stream identifier conflicts are avoided, but the ability to add new applications dynamically is restricted
Solution Approach 1:
The patent enables stream subscribers to autonomously discover and resolve stream identifiers through DNS queries without requiring manual planning or coordination. When a new application needs a stream, it simply queries the DNS server with its desired stream name, and the DNS server automatically provides the corresponding stream ID or indicates if the name is already in use. This self-service mechanism eliminates the need for manual conflict resolution while maintaining unique stream identifiers throughout the network.
Data Source
AI summary
A method for establishing a stream in a Time-Sensitive Networking (TSN) network, wherein a request message is sent by a stream subscriber to a Domain Name System (DNS) server, upon which entries are stored that each comprise a stream identifier of a first type assigned to a stream, and a stream identifier of a second type that is different from the first type and is assigned to the respective stream, and the specification of a predefined type exclusively used for, or forms these types of entries, where the request message comprises a stream identifier of the first type and the predefined type known to the at least one stream subscriber, where the stream subscriber receives a response message from the DNS server, which contains a stream identifier of the second type belonging to the stream, and where the stream subscriber logs on to the stream using the stream identifier obtained.