TSN Controller Communication for Cross-Domain Configuration Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing TSN technologies face challenges in implementing communication and exchange between controllers within the same or different TSN domains, leading to repeated network device configuration and lack of information synchronization, which hinders efficient data flow management across multiple domains.
Innovation Solution
A controller-controller protocol (CCP) is defined to facilitate communication between controllers, encapsulating attribute information in TCP or ECP packets to enable cross-domain resource configuration and synchronization, allowing controllers to manage data flows across multiple TSN domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If controllers in different TSN domains independently configure network devices without communication, then each controller can manage its own domain, but configuration information is repeated and not synchronized across domains
Solution Approach 1:
The patent introduces a controller-controller protocol (CCP) as an intermediary communication mechanism between controllers in different TSN domains. This mediator enables controllers to exchange configuration information and coordinate resource allocation, thereby achieving synchronized configuration management across domains without requiring direct complex inter-controller communication infrastructure
Solution Approach 2:
The patent segments the control function into domain-specific controllers that can independently manage local devices while participating in inter-domain coordination through the CCP protocol. This segmentation allows each controller to maintain simplicity for local management while enabling collective synchronization through standardized message exchange mechanisms
2Productivity
If a standardized controller communication protocol is implemented, then information exchange between controllers is efficient, but protocol design and implementation complexity increases
Solution Approach 1:
The CCP protocol employs parameter-based message structures where controllers exchange configuration information through standardized parameters such as domain identifiers, device identifiers, and resource allocation parameters. This parameterized approach enables efficient information exchange while keeping implementation complexity manageable through consistent parameter handling across different controller interactions
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application discloses a method, an apparatus, and a system for communication between controllers in TSN. A specific solution includes: A first controller receives a first packet that is sent by a second controller and that includes an identifier of a TSN domain to which the second controller belongs. The first controller determines, based on the TSN domain identifier, that the first controller and the second controller belong to a same TSN domain. The first controller sends, to the second controller, a second packet that carries user information. According to the foregoing method, communication and exchange between the controllers may be implemented, so that the controllers cooperatively configure a network device in the TSN.