WO2020233430A1 - Tsn中控制器间通信的方法、装置及系统 - Google Patents

Tsn中控制器间通信的方法、装置及系统 Download PDF

Info

Publication number
WO2020233430A1
WO2020233430A1 PCT/CN2020/089476 CN2020089476W WO2020233430A1 WO 2020233430 A1 WO2020233430 A1 WO 2020233430A1 CN 2020089476 W CN2020089476 W CN 2020089476W WO 2020233430 A1 WO2020233430 A1 WO 2020233430A1
Authority
WO
WIPO (PCT)
Prior art keywords
controller
tsn
message
domain
identifier
Prior art date
Application number
PCT/CN2020/089476
Other languages
English (en)
French (fr)
Inventor
陈李昊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2021569191A priority Critical patent/JP7292427B2/ja
Priority to EP20810380.4A priority patent/EP3958509A4/en
Priority to MX2021014146A priority patent/MX2021014146A/es
Publication of WO2020233430A1 publication Critical patent/WO2020233430A1/zh
Priority to US17/531,122 priority patent/US11811511B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/30—Decision processes by autonomous network management units using voting and bidding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device and system for communication between controllers in a Time-Sensitive Networking (TSN).
  • TSN Time-Sensitive Networking
  • Time-Sensitive Networking is a standard developed by the TSN working group of the Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) 802.1. This standard mainly defines the mechanism of time-sensitive transmission on Ethernet. TSN technology pays special attention to the deterministic delay, low delay and high availability of transmission. TSN has a wide range of application scenarios. Among them, the industry generally believes that TSN related technologies are important enabling technologies for industrial automation, industrial Internet, and intelligent manufacturing.
  • TSN technology can be divided into four parts: data plane, control plane, time synchronization, and reliability.
  • the work of the control plane is that the controller in the TSN domain reserves resources for network devices according to user requirements, thereby supporting the forwarding of TSN data to data streams.
  • the controller obtains user requirement information through a User-to-Network Interface (UNI), and completes the configuration of network devices in the TSN domain to which it belongs according to the Network Configuration Protocol (NETCONF). Therefore, how to realize the communication and interaction between controllers in the same TSN domain or different TSN domains has become a problem to be solved.
  • UNI User-to-Network Interface
  • NETCONF Network Configuration Protocol
  • This application provides a method, device, and system for communication between controllers in TSN to realize communication and interaction between controllers in TSN.
  • a method of communication between controllers in TSN receives the first message that includes the domain identifier of the TSN of the second controller sent by the second controller, where the first message may be an Edge Control Protocol (ECP) message, or Transmission Control Protocol (Transport Control Protocol, TCP) messages.
  • ECP Edge Control Protocol
  • TCP Transmission Control Protocol
  • the first controller determines according to the TSN domain identifier of the second controller that the first controller and the second controller belong to the same TSN domain.
  • the first controller sends a second message carrying user information to the second controller, where the second message may be an ECP message or a TCP message.
  • the first controller and the second controller communicate through an inter-controller protocol (controller-controller protocol, CCP), which defines the message format of the communication between the controllers and the attribute information carried in the message.
  • CCP controller-controller protocol
  • the first message may also include the identification or address of the second controller.
  • the user information stored by the first controller includes the caller, stream identifier, stream ranking, terminal station device interface, interface identifier, data frame format, media access control (Media Access Control, MAC) address, virtual local area network (VLAN) label, Internet Protocol version 4 (IPv4) tuple, Internet Protocol version 6 (Internet Protocol version 6, IPv6) tuple, One or more of stream format, stream specification time perception, user-to-network requirements, interface function, listening terminal, status, status information, accumulated delay, interface configuration, time-aware offset, and invalid port.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • the user information may include all the above-mentioned information, or may only include one piece of information about the flow identifier, and the first controller may select from the above-mentioned information according to a preset rule.
  • the synchronization of user information between controllers in the TSN domain can be realized.
  • the active controller fails or fails, other controllers that store user information can implement resource configuration and management of the TSN domain.
  • the first controller obtains the effective value of the second controller, for example, obtains the effective value of the second controller from the first message, or obtains the effective value of the second controller from other messages.
  • Valid value The effective value is used to indicate whether the first controller is active. For example, a valid value of 0 indicates that the second controller is not an active controller; a valid value of 1 indicates that the second controller is in the election state and can become an active controller after election; a valid value of 2 indicates that the second controller is an active controller .
  • the first controller determines that the second controller is in the election state according to the effective value of the second controller.
  • the first controller determines, according to a preset rule, that a controller in the election state in the TSN domain is an active controller.
  • the preset rule may be that the controller with the smallest value of the controller identifier is the active controller.
  • the active state referred to in this application refers to the state of managing and configuring the controller in the TSN domain to which it belongs.
  • the election state refers to the state when the candidate may become the active controller.
  • the TSN domain to which the first controller and the second controller belong further includes a fourth controller.
  • the first controller receives the effective value of the fourth controller sent by the fourth controller.
  • the first controller determines that the fourth controller is in the election state according to the effective value of the fourth controller.
  • the first controller determines that the first controller is also in the election state according to the effective value of the first controller.
  • the first controller determines that one of the one or more controllers in the election state in the TSN domain is the active controller.
  • the elected active controller may be the first controller or the first controller. Four controllers. With this method, automatic election and switching of the active controller can be performed when the active controller fails, so as to avoid the interruption of management configuration due to the failure of the active controller.
  • the status information determined as the active controller is sent to other network devices within a set period.
  • the first controller when the first controller is determined to be the active controller after election, the first controller carries its own active state information in an ECP message or a TCP message and sends it to other network devices within a set period.
  • the network device in the TSN obtains the information of the active controller so that the network device can send information to the active controller.
  • the first controller includes but is not limited to a first port and a second port, where the first controller receives the first packet through the first port.
  • the first controller determines that the first port and the second port belong to the same TSN domain, the first controller forwards the first packet to the first network device through the second port.
  • the first message can be diffused in the same TSN domain, so that network devices in the same TSN learn about the attribute information of the second controller through the first message.
  • the first message may also include the identifier of the second controller or the MAC address of the second controller.
  • the first controller sends the second message to the second controller according to the identifier of the second controller or the MAC address of the second controller. In this way, the first controller can send messages to other controllers according to the identifier or MAC address of the controller to implement communication between the controllers.
  • a method of communication between controllers in TSN is provided.
  • the first controller receives the first message sent by the second controller, where the first message carries the TSN domain identifier to which the second controller belongs.
  • the first controller determines, according to the TSN domain identifier of the second controller, that the first controller and the second controller do not belong to the same TSN domain.
  • the first controller sends a second message to the second controller, the second message including the first TSN domain identifier to which the first controller belongs and the second TSN domain identifier adjacent to the first TSN domain .
  • the first controller and the second controller can exchange information according to the CCP protocol, for example, encapsulate the attribute information of the controller defined by the CCP protocol in a TCP or ECP message for sending or receiving.
  • the communication protocol between the controllers can be defined to realize the information exchange between the controllers of different TSN domains.
  • the first controller determines one or more TSN domains through which the data flow reaches the destination address according to the destination address of the data flow.
  • the first controller sends the attribute information of the data stream to the determined active controller of one or more TSN domains.
  • the attribute information of the data stream includes the caller, the stream identifier, the stream ranking, the terminal station device interface, the interface identifier, the data frame format, the media access control MAC address, and the virtual local area network VLAN tag.
  • the first controller receives the effective value of the second controller, and the effective value of the second controller is in an active state.
  • the first controller sends the effective value of the first controller to the second controller according to the effective value of the second controller, and the effective value of the first controller is active.
  • the first controller receives a third message sent by the second controller, and the third message includes the second TSN domain identifier to which the second controller belongs and the same as the second TSN domain.
  • the third TSN is different from the first TSN and the second TSN.
  • the embodiments of the present invention provide a controller in the TSN, which executes the method in the first aspect, any one of the possible implementations of the first aspect, and any one of the second or second aspects.
  • the method in the implementation mode the controller includes a unit for executing the method in the first aspect, any one of the possible implementation manners of the first aspect, the second face or the method in any one possible implementation manner of the second aspect.
  • a controller which includes a processor, a network interface, and a memory.
  • the memory may be used to store program code
  • the processor is used to call the program code in the memory to execute the method in any one of the foregoing first aspect, the second aspect, and any one of the second aspect or the second aspect.
  • the method in the implementation of refer to the detailed description in the method example for details, which will not be repeated here.
  • a controller in a fifth aspect, includes a main control board and an interface board.
  • the main control board includes: a first processor and a first memory.
  • the interface board includes: a second processor, a second memory, and an interface card.
  • the second memory may be used to store program code, and the second processor is used to call the program code in the second memory to perform the following operations: receive a first message carrying the TSN domain identifier of the second controller, and send a second message carrying user information .
  • the first memory may be used to store program code
  • the first processor is used to call the program code in the first memory to perform the following operations: determine the first controller and the second controller according to the TSN domain identifier of the second controller carried in the first message
  • the two controllers are in the same TSN domain.
  • a system for communication between controllers in TSN includes a first controller and a second controller.
  • the first controller is configured to receive the first message sent by the second controller, determine according to the TSN domain identifier of the second controller that it belongs to the same TSN domain as the second controller, and send the second message to the second controller.
  • the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the second message includes user information stored by the first controller.
  • the second controller is used to send the first message and receive the second message.
  • a system for communication between controllers in a TSN includes a first controller and a second controller.
  • the first controller is configured to receive the first message sent by the second controller, determine according to the TSN domain identifier of the second controller that it does not belong to the same TSN domain as the second controller, and send it to the second controller The second message.
  • the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the second message includes the first TSN domain identifier to which the first controller belongs and the second TSN domain identifier adjacent to the first TSN domain.
  • the second controller is used to send the first message and receive the second message.
  • a computer storage medium for storing computer software instructions used for the above-mentioned network device or controller, which includes the program designed for executing the above-mentioned aspect.
  • a computer program product includes computer code.
  • the computer program code runs on a computer, the computer executes the program in any of the above aspects.
  • FIG. 1 is a schematic diagram of a TSN scenario provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of another TSN scenario provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of another TSN scenario provided by an embodiment of the application.
  • FIG. 4 is a schematic structural diagram of a controller provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of a method for communication between controllers in a TSN according to an embodiment of this application;
  • FIG. 6 is a schematic diagram of the format of an ECP message sent between controllers in a TSN according to an embodiment of the application;
  • FIG. 7 is a schematic diagram of the format of a TCP packet sent between controllers in a TSN according to an embodiment of the application;
  • FIG. 8 is a schematic diagram of a communication scenario between controllers in a TSN according to an embodiment of the application.
  • FIG. 9 is a schematic flowchart of a method for electing an active controller among controllers in a TSN according to an embodiment of the application.
  • FIG. 10 is a schematic flowchart of a method for communication between controllers in a TSN according to an embodiment of the application;
  • FIG. 11 is a schematic flowchart of another method for controller communication in TSN according to an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of another controller provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of another controller provided by an embodiment of the application.
  • FIG. 14 is a schematic structural diagram of another controller provided by an embodiment of the application.
  • FIG. 15 is a schematic structural diagram of another system for communication between controllers according to an embodiment of the application.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • Time-Sensitive Networking can also be called a time-sensitive network, which is a standard researched by the Time-Sensitive Networking Task Group of the (Institute of Electrical and Electronics Engineers, IEEE) 802.1 working group. The standard emphasizes ultra-low latency and high availability of transmission. TSN is mainly used in various Ethernet protocols that support low-latency and time-based synchronization of data transmission. Possible applications include industrial automation, industrial Internet, intelligent manufacturing that requires real-time monitoring or real-time feedback, or in combination with real-time video and audio streaming and Real-time control streaming integrated network and other scenarios.
  • TSN can include different TSN domains.
  • the division of the TSN domain is determined according to the TSN domain (domain) identification (ID) configured on the network device port in the TSN. For example, if the TSN domain identifiers of two different ports are the same, it indicates that the above two ports belong to the same TSN domain; the TSN domain identifiers of two different ports are different, which indicates that the two ports belong to different TSN domains.
  • Ports of network devices can be configured with TSN domain IDs, and different ports can be configured with different TSN domain IDs.
  • the TSN domain identifier of the network device port can be configured through static configuration, or configured by sending configuration information from the controller, or configured through other methods. This application does not limit the configuration of the TSN domain.
  • the Link-local Registration Protocol is used to facilitate the distribution of applications among network devices in the system.
  • the system includes networks connected via IEEE 802 media.
  • the system may include End, the network of forwarding devices and controllers.
  • LRP can support multiple application protocols to distribute information in the network at the same time, including information announcement, transmission and registration, etc., and maintain an announcement database and registration database for each application protocol on each port of the network device. It can also be said that each port has an LRP entity, and the aforementioned data inventory resides in this LRP entity.
  • LRP completes the task of transferring applications by creating a point-to-point two-way association between systems. Each association consists of two one-way paths, one end of each path is a database, and the other end is a registrar database. LRP quickly and reliably replicates applications in the database to its neighbor's registrar database.
  • the transmission of these data can be transmitted through a Transmission Control Protocol (Transport Control Protocol, TCP) or an Edge Control Protocol (Edge Control Protocol, ECP
  • the IEEE 802.1Qcc-2018 defines three TSN configuration models. For specific descriptions of TSN configuration models, please refer to the relevant descriptions in section 46 "Time Sensitive Network (TSN) Configuration" of IEEE P802.1Qcc.
  • TSN Time Sensitive Network
  • this application provides one of the TSN centralized network models.
  • the TSN centralized network may include a talker 106, a listener 107, a network device 102-network device 105, and a controller 101.
  • the controller 101 can receive the demand information sent by the talker 106 and the listener 107 through the network device 102-network device 105, and can also receive the demand information through centralized user configuration (CUC), and then according to Request information for resource reservation.
  • CRC centralized user configuration
  • the controller 101 sends resource reservation information to the network devices 102-105.
  • the speaking end 106 can send the data stream to the listening end 107 through the network device 102-the network device 105, so as to realize the ultra-low delay and high availability of data stream transmission.
  • the following describes the network equipment in the TSN scenario shown in FIG. 1.
  • the speaking end 106 and the listening end 107 may be referred to as end stations in the TSN, which refer to devices at both ends that send and receive data streams end-to-end.
  • the originating end 106 may also be referred to as an ingress or an initiating node, and the receiving end 107 may also be referred to as an egress or an end node.
  • the network device 102-network device 105 may be referred to as a transmission device or a forwarding device in the TSN.
  • the network device 102-the network device 105 may include bridges.
  • the speaking end and the listening end may also be devices with a network bridge function.
  • the speaking end 106 is an end station for sending data streams
  • the listening end 107 is an end station for receiving data streams.
  • the network device 102-the network device 105 may include a bridge device or a switch, and the speaking end and the listening end may include sensors, actuators, or servers.
  • the network device 102-the network device 105 may be a router or a three-layer switch, and the speaking end and the listening end may include network devices such as a router, a three-layer switch, or a server.
  • a bridge refers to a network device that works on the second layer, such as the data link layer, that has the function of storing and forwarding data streams in the communication network, and meets all or part of the requirements defined by the IEEE 802.1 standard
  • the bridge can be a switch.
  • TSN data stream refers to the data stream from the sender to the receiver, or the data stream from the speaking end to the listening end. The characteristics of the data stream transmission meet all the requirements defined by the IEEE 802.1 TSN series of standards or a combination of some of the requirements.
  • the controller 101 may be referred to as a network controller or a centralized network configuration (Centralized Network Configuration) controller, which has the functions of collecting information in the TSN domain and centralized calculation, and can realize the optimal configuration of network resources.
  • a TSN domain can have one controller or multiple controllers.
  • the controller 101 may be an independent control device, or a module with controller functions integrated on other network devices. When the controller 101 is a functional module, it can be integrated on other network devices in the TSN.
  • the controller in Figure 1 is a functional module that can integrate the talking terminal 106, the listening terminal 107, or the network device 102-Network On any one of the devices 105, this application does not limit the specific form of the controller.
  • the node in this application can also be referred to as a network device.
  • the node can be a repeater, switch, bridge, gateway, or router, etc., or a logical or virtual device that can implement the function of forwarding data streams.
  • TSN technology can be divided into four parts: data plane, control plane, time synchronization and reliability.
  • the controller 101 can exchange configuration information with the talking terminal device 106 and the listening terminal device 107 through the network devices 102-105.
  • the network device 101 obtains the user requirement information of the caller 106 through a User-to-Network Interface (UNI).
  • the controller 101 can obtain the user demand information of the caller 106 from the network device 102 through the YANG model.
  • the controller 101 plans or reserves resources according to the obtained user demand information, and sends the reserved resource information to the network device 102.
  • the controller 101 may send the reserved resource information to the network device 102 through the YANG model, that is, the controller 101 performs network configuration on the network device 102.
  • the data plane can implement end-to-end transmission of the data stream according to the resource reservation information issued by the controller.
  • a TSN domain may include one or more controllers. As shown in FIG. 2, a TSN domain includes a controller 101 and a controller 108. The TSN may also include multiple different TSN domains. As shown in FIG. 3, TSN domain 1 includes a controller 301, and TSN domain 2 includes a controller 302. If the interactive communication between the controllers cannot be realized, the repeated configuration of network devices in the same TSN domain by multiple controllers cannot be avoided, and it is difficult to achieve information synchronization between the controllers and automatic switching between the active and standby controllers. Moreover, the data stream may traverse multiple TSN domains from the speaking end to the listening end.
  • the controller Since the controller only configures the network for devices in the TSN domain, the controller cannot implement a pathfinding mechanism for data streams leaving the TSN domain. Therefore, how to realize the interaction and communication between different controllers in a domain and between controllers in different domains has become an urgent technical problem to be solved.
  • this application provides a method, device, and system for communication between controllers in TSN to solve the communication and interaction between controllers in the same TSN domain or between different TSN domains.
  • the basic principle of this application is to define a protocol for communication between controllers, such as Controller-Controller Protocol (CCP), where CCP generally refers to a protocol with communication functions between controllers.
  • CCP Controller-Controller Protocol
  • Table 1 an attribute information defined by an inter-controller communication protocol is provided.
  • the type, length, and value of attribute information carried by CCP it is possible to realize communication between controllers in the TSN domain or between different TSN domains. Communication between controllers.
  • the values corresponding to the types in Table 1 are used to identify different types of attribute information, and the values corresponding to the types in Table 1 can also be distinguished by other values, and this application does not limit specific values.
  • the CCP protocol may be an application layer protocol or a protocol of other layers.
  • This application does not limit the protocol to belong to a certain layer of the open system interconnection (open system interconnection, OSI) standard layer.
  • the inter-controller communication protocol can include all the attribute information in Table 1, or part of the attribute information, and the attribute information included in the inter-controller communication protocol can be selected as required.
  • the controller can encapsulate one or more of the attribute information in Table 1 in a TCP packet or ECP packet and send it to other controllers.
  • the controllers in the TSN can be carried in TCP packets or ECP packets.
  • the attribute information in Table 1 realizes the communication between controllers.
  • the specific form of the encapsulation attribute information of the TCP packet or the ECP packet is specifically introduced in the following in conjunction with the communication process between controllers.
  • FIGS. 1 to 3 are only exemplary descriptions of TSN scenarios, and the number of nodes included in the network architecture can be configured according to actual requirements.
  • the actual product form of each network device in Figs. 1 to 3 can be configured according to actual needs.
  • Figs. 1 to 3 only illustrate the type of each network device by way of example, and do not specifically limit this.
  • an embodiment of the present application provides a schematic structural diagram of a network device with a controller entity.
  • the network device may be a forwarding device with a controller function, or an end station with a controller entity. ), that is, an independent controller device.
  • the controller 40 includes a determination module, a CCP application, an LRP entity, and a communication port.
  • the LRP entity may include a data synchronization module and a data transport module.
  • the determining module is used to determine whether the controller corresponding to the received attribute information and the controller 40 belong to the same TSN domain.
  • the CCP application may include attribute information of the controller 40.
  • the CCP application includes some or all of the attribute information shown in Table 1 above.
  • the LRP entity is used to synchronize and transmit data in CCP applications. Further, the data synchronization module in the LRP entity is used to maintain synchronization with the data in the CCP application.
  • the data synchronization module can obtain the attribute information in the CCP application, and can also transmit the received attribute information of other network devices to the CCP application by synchronization.
  • the data transmission module in the LRP entity is used to transmit the data in the data synchronization module. For example, the data transmission module encapsulates the attribute information into an LRP data unit and sends it to other network devices through the communication port, or receives data sent by other network devices. .
  • the communication port is used for interactive communication with other network devices, receiving or sending data.
  • the CCP application includes information corresponding to TLV 23 in Table 1.
  • the LRP entity obtains this information through the data synchronization module, and then the data transmission module sends it to other network devices through the communication port.
  • the communication port receives a message carrying attribute information sent by other controllers
  • the data transmission module processes the message to obtain attribute information, and transmits the attribute information to the data synchronization module, and the data synchronization module synchronizes the attribute information To CCP application. In this way, communication between controllers is realized.
  • the LRP data synchronization module may also include a data registration module and a data announcement module.
  • the data registration module is used to register the received attribute information of other controllers.
  • the data announcement module is used to send the attribute information that needs to be announced and transmitted to other network devices to the data transmission module.
  • the controller 101 or the controller 108 in FIG. 2 may include the structure shown in FIG. 4.
  • the communication port is used to receive the first message sent by the second controller, where the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the controller determines that it belongs to the same TSN domain as the second controller, and sends a second message including user information to the second controller.
  • the determining unit is used for determining that the controller 40 and the second controller belong to the same TSN domain according to the TSN domain identifier of the second controller.
  • the controller 301 or the controller 302 in FIG. 3 may have the structure shown in FIG. 4.
  • the communication port is used to receive the first message sent by the second controller, where the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the controller determines that it does not belong to the same TSN domain as the second controller, it sends to the second controller the second controller that includes the first TSN domain identifier to which the first controller belongs and the second TSN domain identifier adjacent to the first TSN domain.
  • the determining unit is used to determine that the controller 40 and the second controller do not belong to the same TSN domain.
  • the controller communication port forwards the attribute information of the controller through an ECP message or a TCP message.
  • each port of the network device in the TSN needs to be configured with a TSN domain identifier to realize the division of the TSN domain. All ports of each TSN domain are interconnected, and the connected path does not need to cross other domains.
  • the process of communication between controllers includes discovery between network controllers, election between controllers in the same TSN domain, announcement of active network controllers, failover of active controllers, and multiple controllers in the TSN domain Information synchronization, synchronization of information of active controllers in different TSN domains, and management of data flows across TSN domains by active controllers.
  • the interaction between the aforementioned controllers can be independent of each other or combined with each other.
  • this application provides a schematic flowchart of a method for communication between controllers.
  • the method includes a communication process of synchronizing data between a first controller and a second controller, where the first controller may be the controller 101 in FIG. 2 and the second controller may be the controller 108 in FIG. 2.
  • the first controller and the second controller may have the structure shown in FIG. 4.
  • the method includes:
  • a network device with a controller entity can be either an independent controller device or a forwarding device with a bridge function, that is, the forwarding device integrated controller has Function, the controller referred to in this application includes any one of the above two devices.
  • the controller may periodically send the first message, and may also send the first message when joining the TSN.
  • the period for sending the first packet of multiple controllers in the same TSN domain is set to the same value to improve the efficiency of discovery among controllers in the TSN domain.
  • the first message includes the status information of the first controller.
  • the status information can be part or all of the information corresponding to Type-Length-Value (TLV) 23 in Table 1. , As shown in Table 2 below.
  • the first controller may send part or all of the information corresponding to its own TLV 23 to other network devices in the same TSN domain when joining the TSN or periodically. Therefore, the second controller in the same TSN domain as the first controller learns the state of the first controller through the state information, and realizes communication and negotiation between controllers in the same TSN domain.
  • the first message includes the first controller domain identifier, or the first message includes the controller domain identifier of the first controller and the media access control (Media Access Control, MAC) address of the controller.
  • Media Access Control Media Access Control
  • the format of the first message may be the ECP message shown in FIG. 6.
  • the upper layer protocol data unit (ULPDU) in the ECP message includes but is not limited to the LRP data unit (DU).
  • the record field of the LRPDU includes but is not limited to one or more record fields, where application data (application data) in the record field may be used to carry attribute information of the first controller.
  • the information usage type-length-value format corresponding to the TLV 23 of the first controller is encapsulated in the recorded application data, and the application data is carried in the ULPDU of the ECP packet, and the first controller communicates with each other.
  • the port of a neighboring network device is sent.
  • the network device can be a controller or a forwarding device.
  • the format of the first message may be the TCP message format shown in FIG. 7, where the TCP data part of the TCP message includes but is not limited to the LRP DU field.
  • the record field of the LRPDU may include but is not limited to one or more records, where application data (application data) in the record field may be used to carry attribute information of the first controller.
  • application data application data
  • the information usage type-length-value format corresponding to the TLV 23 of the first controller is encapsulated in the recorded application data, and the application data is carried in the data of the TCP packet, which is sent from the port of the first controller to the The port of other network equipment is sent.
  • the state information of the first controller may be announced in the TSN domain to which the first controller belongs, and network devices in the same TSN domain may receive the state information of the first controller.
  • the network device in the TSN domain includes a first port and a second port. The network device receives the status information of the first controller through the first port. If the network device determines that the first port and the second port belong to the same TSN domain, the network device forwards the state information of the first controller to other adjacent network devices through the second port.
  • the network device determines that the first port and the second port do not belong to the same TSN domain, the network device will not continue to forward the state information of the first controller to other adjacent network devices to ensure that the state information of the first controller is in It is transmitted in the TSN domain to which the first controller belongs, so that the controllers in the same TSN domain know each other's status information.
  • the network device may be another controller in the TSN domain to which the first controller belongs, and may also be a forwarding device, a speaking end or a listening end in the TSN domain to which the first controller belongs.
  • S520 The second controller receives the first message sent by the first controller.
  • the second controller receives the first message through a communication protocol between the controllers, for example, the communication protocol is CCP.
  • the communication protocol is CCP.
  • FIG. 8 a schematic diagram of a scenario in which controllers communicate through CCP is provided.
  • the network device 801 in FIG. 8 is a forwarding device with a controller function
  • the network device 802 is a forwarding device
  • the network device 803 is an independent controller device.
  • the network device 801 can also be called a controller 801
  • the network device 802 is a forwarding device 802.
  • the network device 803 is the controller 803.
  • the network device 801 may be a network bridge integrated with a controller function module
  • the network device 802 may be a network bridge without a controller function module
  • the network device 803 is a controller end station.
  • Each of the network device 801-the network device 803 includes a CCP application and an LRP entity, where the network device 802 is directly connected to the network device 801 and the network device 803 respectively.
  • the CCP application includes the attribute information of the controller, for example, includes part or all of the attribute information of the controller shown in Table 1 above.
  • the LRP entity is used to synchronize and transmit attribute information in CCP applications. Further, the LRP entity may also include a data synchronization module and a data transmission module.
  • the data synchronization module is used to keep synchronized update with the data in the CCP application, and the data transmission module is used to perform the transmission of the CCP application.
  • Each of the network equipment 801-network equipment 803 may also include a logical link control layer (LLC) and a media access control layer (Media Access Control Layer, MAC Layer). LLC uses the MAC layer to run different types of programs to support protocol identification, multiplexing, and demultiplexing, thereby supporting the transmission and reception of data units of the Spanning Tree Protocol and other high-level protocols.
  • LLC uses the MAC layer to run different types of programs to support protocol identification, multiplexing, and demultiplexing, thereby supporting the transmission and reception of data units of the Spanning Tree Protocol and other high-level protocols.
  • Each of the network device 801-network device 803 also includes a port for receiving or sending data. If the network device 801 and the network device 802 are bridges, the network device 801 and the network device 802 may also include a MAC relay entity (MAC relay entity
  • the CCP application of the network device 801 synchronizes the attribute information of the network device 801, for example, the information corresponding to the TLV 23 of the network device 801 to the LRP entity through the data synchronization module and the data transmission module of the LRP entity.
  • the LRP entity encapsulates the attribute information into the LRPDU.
  • the network device 801 encapsulates the LRPDU into an ECP message and sends it to the network device 802, where the ECP can be used for data transmission between adjacent directly connected ports.
  • the network device 801 may also encapsulate the LRPDU into a TCP packet and send it to the network device 803.
  • the port of the network device 802 receives the ECP message sent by the network device 801, and transmits the data frame to the LRP entity of the network device 802 through the MAC layer and LLC.
  • the LRP entity of the network device 802 transmits the acquired information of the network device 801 to the CCP application of the network device 802 through the data synchronization module.
  • the port of the network device 803 receives the TCP message sent by the network device 801, and transmits the data frame to the LRP entity of the network device 803 through the MAC layer and LLC.
  • the LRP entity of the network device 803 transmits the acquired information of the controller 801 to the CCP application of the network device 803 through the data synchronization module. In this way, the network device 802 and the network device 803 can obtain the attribute information of the network device 801, and realize the announcement of the network device 801 of its attribute information and the communication between the controllers.
  • the network device 803 may also obtain the attribute information of the network device 801 through the forwarding of the network device 802.
  • the second controller determines that the first controller and the second controller belong to the same TSN domain according to the domain identifier of the first controller.
  • the domain identifier of the first controller is used to identify the identifier of the TSN domain to which the first controller belongs. If the TSN domain identifiers of the first controller and the second controller are the same, the first controller and the second controller belong to the same TSN domain.
  • S540 The second controller sends a second message to the first controller.
  • the second message includes user information saved by the first controller.
  • the second message may also include an identifier or an instruction for instructing the first controller to synchronize user information in the second message.
  • the synchronization of data information between controllers in the TSN domain can be realized.
  • the active controller fails, because other controllers in the TSN domain save synchronization information, the active controller in the TSN domain can be switched to ensure the management and configuration of network devices in the TSN domain, and to realize resource reservation.
  • the user information carried in the second packet includes Talker, Stream ID, Stream Rank, End Station Interfaces, and Interface ID (Interfaces ID), data frame format (Data Frame Specification), media access control (Media Access Control, MAC) address (IEEE802-Mac Addresses), virtual local area network (virtual local area network, VLAN) tag (IEEE802-Vlan Tag) , Internet Protocol version 4 (Internet Protocol version 4, IPv4) tuple (IPv4-tuple), Internet Protocol version 6 (Internet Protocol version 6, IPv6) tuple (IPv6-tuple), flow format (Traffic Specification), flow Standard time awareness (Traffic Specification Time Aware), User To Network Requirements (User To Network Requirements), Interface Capabilities, Listening End (Listener), Status (Status), Status Information (Status Information), Accumulated Delay (Accumulated Latency), one or more of interface configuration (Interface Configuration), time aware offset (Time Aware Offset), time aware offset (Time
  • the second controller may send the second packet to the first controller according to the MAC address of the first controller carried in the first packet.
  • the second message may be the ECP message shown in FIG. 6 or the TCP message shown in FIG. 7.
  • the first controller encapsulates the user information in the ECP message
  • the first controller encapsulates the user information in the TCP message
  • S550 The first controller receives a second message sent by the second controller.
  • the second message includes user information saved by the first controller.
  • the second message may further include an identifier or instruction, and the first controller synchronizes the user information in the second message according to the identifier or instruction.
  • the first controller and the second controller may also send or obtain information in the following 3 through ECP messages or TCP messages.
  • ECP messages or TCP messages For the specific format of the messages, refer to the related description of FIG. 6 or FIG. 7.
  • the method for communication between controllers described in Embodiment 1 may further include a process of electing an active controller between controls.
  • FIG. 9 a schematic flow diagram of another method for communication between controllers is provided.
  • the communication between controllers in this method can be based on CCP exchange information, and the method includes:
  • S910 The first controller sends the effective value of the first controller to the second controller.
  • the first controller encapsulates its effective value in a first message or other messages and sends it to the second controller.
  • the effective value of the first controller is used to indicate whether the first controller is in an active state. For example, a valid value of 0 means that the first controller is not an active controller; a valid value of 1 means that the first controller is in the election state and can become an active controller after election; a valid value of 2 means that the first controller is an active controller Device.
  • the active state referred to in this application refers to the state of managing and configuring the network equipment in the TSN domain to which it belongs.
  • the election state refers to the state when the candidate becomes the active controller.
  • the first controller determines that no active controller is found in the TSN domain to which it belongs within a predetermined time, and will The effective value of oneself is set to the corresponding value of the election state.
  • the controller 101 determines within a predetermined time that it has not received the state information of the Controller Active value of 2 in Table 1 from the controller 102 in the TSN domain, and the controller 101 sets its own effective value to 1. Declare the effective value of the election state to other network devices in the TSN domain.
  • the first controller uses CCP to send the content corresponding to the TLV 23 of the first controller (shown in Table 1) to the second controller, so that the second controller obtains the Valid value.
  • S920 The second controller obtains the effective value of the first controller.
  • the second controller obtains the effective value of the first controller from the first message.
  • S930 The second controller determines that the first controller is in an election state according to the effective value of the first controller.
  • the second controller is also in an election state, and the effective value of the second controller is the same as the effective value of the first controller.
  • the second controller determines, according to a preset rule, that one of the one or more controllers in the election state is the active controller.
  • the preset rule may be determined according to the size of the identifier of the controller in the election state, and may also be determined according to the size of the address of the controller in the election state, for example, the value of a specific bit of the MAC address.
  • the active controller sends its own active state to other network devices.
  • the controller whose valid value is in the active state announces to the network device in the TSN domain to which it belongs.
  • the controller in the active state can announce to other network devices within a predetermined period. Through the announcement, the active state of the controller will be registered in the database of the LRP entity of the port of the network device in the same TSN domain. Network equipment spreads between adjacent network equipment ports through ECP. As a result, the network devices in the domain can understand the information of the currently active controller.
  • the active controller can also announce its valid status to the controllers of the neighboring TSN domain through the TSN domain boundary device. In this way, it is possible to realize the declaration of the active state of the controllers between TSNs in different domains, and to realize the communication between the controllers between the TSNs.
  • the first controller sends the effective value of the active state of the first controller to other network devices by declaring the TLV 23.
  • the effective controller announces TLV 23 in a predetermined period, where the Controller Active value is 2, and the TLV 23 will be registered in the LRP database of each port in all network devices in the TSN domain , ECP is responsible for spreading TLV 23 among neighboring network devices one by one, and CCP is responsible for spreading TLV 23 among ports inside the device.
  • the effective controller 101 may announce the effective state information of the controller 301 to the controller 308 through the TSN domain border network device 303 and the border device of the adjacent TSN domain.
  • the above method further includes when the first controller fails or fails, performing controller election and electing a new active controller according to a predetermined rule.
  • controller election includes but is not limited to situations where the controller loses its ability to manage the TSN domain.
  • this application provides a schematic flowchart of another method for communication between controllers.
  • the method includes a process of a first controller and a second controller, where the first controller may be the controller 301 in FIG. 3 and the second controller may be the controller 308 in FIG. 3.
  • the first controller and the second controller may have the structure shown in FIG. 4.
  • the method includes:
  • S1010 The first controller sends the first packet.
  • step S510 in FIG. 5 for the implementation manner in which the first controller sends the first message, reference may be made to the related description of step S510 in FIG. 5, which will not be repeated here.
  • S1020 The second controller receives the first packet sent by the first controller.
  • the first controller and the second controller belong to different TSN domains, the first controller belongs to the first TSN domain, and the second controller belongs to the second TSN domain.
  • the first TSN domain may The second TSN domain is adjacent or not adjacent. If the first TSN domain is adjacent to the second TSN domain, the second controller may obtain the first packet through the border network device of the second TSN domain.
  • the first port of the network device belongs to the first TSN domain
  • the second port belongs to the second TSN domain
  • the network device is at the boundary of two adjacent TSN domains.
  • the network device obtains the first packet of the first controller in the first TSN domain through the first port, and the network device may forward the first packet to the active controller in the second TSN domain through the second port.
  • the first controller determines, according to the TSN domain identifier of the second controller, that the first controller and the second controller do not belong to the same TSN domain.
  • the domain identifier of the first controller is used to identify the identifier of the TSN domain to which the first controller belongs. If the TSN domain identifiers of the first controller and the second controller are the same, the first controller and the second controller belong to the same TSN domain.
  • S1040 The first controller sends a second message to the second controller.
  • the second message includes the first TSN domain identifier to which the first controller belongs and the second TSN domain identifier adjacent to the first TSN domain.
  • the second message includes part or all of the information corresponding to the TLV 25 shown in Table 4, that is, it may include the TSN domain identifier to which the first controller belongs, the adjacent TSN domain identifier, and the first control One or more information in the MAC address of the device.
  • the first controller can exchange information with the controllers of the neighboring TSN domains, and learn about TSN domain boundary information with each other.
  • the format of the second message may refer to the message format shown in FIG. 6 or FIG. 7 and related explanations of FIG. 6 and FIG. 7.
  • S1050 The second controller receives the second message sent by the first controller.
  • the foregoing method may further include the first controller receiving an effective value of the second controller, where the effective value of the second controller indicates that the second controller is in an active state.
  • the first controller sends the first controller effective value to the second controller according to the effective value of the second controller, where the effective value of the first controller indicates that the first controller is in an active state.
  • the second controller may send a message carrying a TLV 23 with a valid value to a neighboring network device, and the neighboring network device may further forward the first message.
  • the TLV 23 that the second controller announces can be transmitted across the TSN domain.
  • the border network device receives a TLV 23 sent by another TSN domain, it forwards the TLV 23 to the active controller in the TSN domain.
  • the TSN domain boundary may exist between devices.
  • B2 and B3 in TSN belong to different TSN domains.
  • the port P3 of B3 receives the TLV 23 sent by B2, and finds that the TSN domain ID of its controller is different from the TSN domain ID of P3, so P3 forwards the TLV 25 of the controller in the TSN domain to B2. Then, B2 forwards the TLV 25 to the active controller of the TSN domain to which B2 belongs.
  • the method for communication between controllers described in Embodiment 2 may further include the method steps shown in FIG. 11.
  • FIG. 11 a schematic flow diagram of another method for communication between controllers is provided.
  • the method shown in FIG. 11 can not only realize the communication between controllers, but also realize the configuration of data flows across different TSN domains by the controller.
  • the method includes:
  • the first controller determines, according to the destination address of the data flow, a third TSN domain through which the data flow reaches the destination address.
  • the first controller determines, according to the destination address of the data stream, that the next TSN domain through which the data stream needs to flow is an adjacent TSN domain.
  • the first controller determines, according to the IP or MAC address of the data flow, one or more TSN domains that the data flow will pass through on the path to the destination address.
  • the first controller saves the correspondence between the MAC address and the TSN domain identifier.
  • the first controller determines the corresponding TSN domain according to the MAC address of the data stream.
  • the first controller saves the TSN network topology information, and the first controller determines the path information of the data flow to the destination address according to the MAC address of the data flow.
  • the first controller further determines one or more TSN domains that the data stream needs to pass through according to the network devices that need to pass through the path.
  • S1120 The first controller sends the attribute information of the data stream to the active controller of the third TSN domain.
  • the attribute information of the data stream includes the originator, stream identifier, stream ranking, terminal station device interface, interface identifier, data frame format, media access control MAC address, virtual local area network VLAN tag, fourth Version Internet Protocol IPv4 Tuple, Version 6 Internet Protocol IPv6 Tuple, Stream Format, Stream Specification Time Perception, User-to-Network Requirements, Interface Function, Listening End, Status, Status Information, Cumulative Delay, Interface Configuration, Time Perception Offset And one or more information in the invalid port.
  • FIG. 12 shows a possible structural schematic diagram of the controller involved in the above embodiment, which can implement the first controller or the second control in the embodiments shown in FIGS. 5 and 8 to 11
  • the controller 1200 includes: a receiving unit 1201, a determining unit 1202, and a sending unit 1203. These units can perform the corresponding functions of the controller in the above method example.
  • the receiving unit 1201 is configured to support the controller 1200 to execute the processes S520 and S550 in FIG. 5, the processes S920 in FIG. 9, and the processes S1020 and S1050 in FIG. 10;
  • the determining unit 1202 is configured to support the controller 1200 to execute the processes in FIG.
  • the receiving unit 1201 is used to perform various information reception performed by the controller in the above method embodiment; the determining unit 1202 is used to perform the determining action performed by the controller in the above method embodiment; the sending unit 1203 is used to perform the above method implementation In the example, the controller performs various information transmission.
  • the receiving unit 1201 is configured to receive the first packet including the domain identifier of the TSN to which the second controller belongs.
  • the determining unit 1202 is configured to determine that the first controller and the second controller belong to the same TSN domain according to the TSN domain identifier of the second controller.
  • the sending unit 1203 is configured to send a second message including user information saved by the first controller to the second controller.
  • the receiving unit 1201 is configured to receive the first packet including the domain identifier of the TSN to which the second controller belongs.
  • the determining unit 1202 is configured to determine, according to the TSN domain identifier of the second controller, that the first controller and the second controller do not belong to the same TSN domain.
  • the sending unit 1203 is configured to send a second message including the first TSN domain identifier to which the controller belongs and the second TSN domain identifier adjacent to the first TSN domain to the second controller.
  • the division of units in the embodiment of the present invention is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the receiving unit and the sending unit may be the same unit or different units.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the controller 1300 includes a processor 1302, a transceiver 1303, a memory 1301, and a bus 1304. Among them, the transceiver 1303, the processor 1302, and the memory 1301 are connected to each other through a bus 1104; the bus 1304 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the controller 1300 can implement the functions of the controller in the embodiments shown in FIGS. 5 and 8 to 11.
  • the processor 1302 and the transceiver 1303 may perform the corresponding functions of the controller in the foregoing method example.
  • the transceiver 1303 is used to support the controller 1300 to execute the processes S510, S520, S540 and S550 in FIG. 5, the processes S910, S920 and S950 in FIG. 9, and the processes S1010, S1020, S1040 and S1050 in FIG. 10, as shown in FIG. 11. S1120 in the process.
  • the processor 1302 is configured to support the controller 1300 to execute the process S530 in FIG. 5, the processes S930 and S940 in FIG. 9, the process S1030 in FIG. 10, and the process S1110 in FIG.
  • the memory 1301 is used to store program codes and data of the controller 1300.
  • the memory 1301 may be a volatile memory (volatile memory), such as random-access memory (RAM); or a non-volatile memory (non-volatile memory), such as read-only memory (read-only memory).
  • volatile memory such as random-access memory (RAM); or a non-volatile memory (non-volatile memory), such as read-only memory (read-only memory).
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk
  • solid-state drive solid-state drive
  • the processor 1302 is the control center of the controller. It can be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or it can be configured to implement the embodiments of this application.
  • One or more integrated circuits for example: one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA).
  • the transceiver 1303 is used to communicate with other devices.
  • the controller may be configured as the controller 101 or the controller 108 in FIG. 2, the controller 101 may be referred to as the first controller, and the controller 108 may be referred to as the second controller.
  • the processor 1302 executes the following functions by running or executing software programs and/or modules stored in the memory 1301, and calling data stored in the memory 1301:
  • the first message carrying the domain identifier of the TSN to which the second controller belongs is received by the transceiver 1303, and the second message carrying user information is sent to the second controller.
  • the controller may be configured as the controller 301 or the controller 302 in FIG. 3, the controller 301 may be called the first controller, and the controller 302 may be the second controller.
  • the processor 1302 executes the following functions by running or executing software programs and/or modules stored in the memory 1301, and calling data stored in the memory 1301:
  • the transceiver 1303 receives the first message sent by the second controller and carries the domain identifier of the TSN to which the second controller belongs, and sends to the second controller the first message carrying the first TSN domain identifier to which the first controller belongs and the first message with the second controller.
  • an embodiment of the present application provides a schematic structural diagram of another device with a controller entity.
  • the controller 1400 is a router or a switch or a network device with a forwarding function.
  • the controller 1400 can implement the functions of the first controller or the second controller in the foregoing method embodiment.
  • the controller 1400 includes a main control board 1401 and an interface board 1402.
  • the main control board 1401 includes a processor 1403 and a memory 1404.
  • the interface board 1402 includes a processor 1405, a memory 1406, and an interface card 1407.
  • the main control board 1401 and the interface board 1402 are coupled.
  • the memory 1406 can be used to store the program code of the interface board 1402, and the processor 1405 is used to call the program code in the memory 1406 to trigger the interface card 1407 to execute the control in the above method embodiment.
  • the processor 1405 calls the program code in the memory 1406 to trigger the interface card 1407 to support the controller 1400 to execute the process S530 in FIG. 5 and the process S1030 in FIG. 10.
  • the processor 1405 is also configured to send the service identification to the main control board 1401.
  • the memory 1404 may be used to store the program code of the main control board 1401, and the processor 1403 is used to call the program code in the memory 1404 to perform other processing of the controller in the foregoing method embodiment except for information transmission and reception.
  • the processor 1403 is used to support the first controller 1400 to execute the processes S930 and S940 in FIG. 9 and the process S1110 in FIG. 11.
  • the memory 1404 is used to store the program code and data of the main control board 1401.
  • For the specific execution process please refer to the detailed description of the corresponding steps in the embodiments shown in FIG. 5 and FIG. 8 to FIG. 11, which will not be repeated here.
  • an IPC control channel is established between the main control board 1401 and the interface board 1402, and the main control board 1401 and the interface board 1402 use the IPC control channel for communication.
  • an embodiment of the invention provides a system 1500 for communication services between controllers in a TSN.
  • the system 1500 is used to implement the method for sending service packets in the foregoing method embodiment.
  • the system 1500 includes a first controller 1501 and a second controller 1502.
  • the first controller 1501 and the second controller 1502 can respectively implement the functions of the first controller and the second controller in the embodiments shown in FIGS. 5 and 8 to 11.
  • the first controller 1501 executes the processes S510, S530, and S550 in FIG. 5, the process S910 in FIG. 9, the processes S1010, S1030, and S1040 in FIG. 10, the processes S1110 and S1120 in FIG. 11, and/or Other processes performed by the first controller in the technology described herein.
  • the second controller 1502 executes the processes S520, S530, and S540 in FIG. 5, the processes S920 to S950 in FIG. 9, the processes S1020 and S1050 in FIG. 10, and/or the first controller used in the technology described herein Other processes performed.
  • the first controller is configured to receive the first message sent by the second controller, and determine according to the TSN domain identifier of the second controller that it belongs to the same TSN domain as the second controller, and send the message to the second controller
  • the device sends the second message.
  • the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the second message includes user information stored by the first controller.
  • the second controller is used to send the first message and receive the second message.
  • the first controller is configured to receive the first message sent by the second controller, and determine according to the TSN domain identifier of the second controller that it does not belong to the same TSN domain as the second controller , Sending a second message to the second controller.
  • the first message includes the domain identifier of the TSN to which the second controller belongs.
  • the second message includes the first TSN domain identifier to which the first controller belongs and the second TSN domain identifier adjacent to the first TSN domain.
  • the embodiment of the present application also provides a storage medium for storing the software instructions used in the foregoing embodiment, which includes a program for executing the method shown in the foregoing embodiment, and when it is executed on a computer or device, it causes The computer or device shown executes the methods in the foregoing method embodiments.
  • the embodiments of the present application also provide a computer program product.
  • the computer program product includes computer code.
  • the computer program code runs on a computer, the computer executes the method in the foregoing method embodiment.
  • any of the device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physically separate
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.
  • the steps of the method or algorithm described in the disclosure of the embodiment of the present invention may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (erasable programmable ROM (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory (EPROM, EEPROM), hard disk, mobile hard disk, optical disk, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described in the present invention can be implemented by hardware, software, firmware or any combination thereof.
  • these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了TSN中控制器之间通信的方法、装置及系统。具体方案包括：第一控制器接收第二控制器发送的包括第二控制器所属的TSN域标识的第一报文。第一控制器根据该TSN域标识确定第一控制器和第二控制器属于同一TSN域。第一控制器向第二控制器发送携带用户信息的第二报文。通过上述方法，可以实现控制器之间通信和交互，使得控制器之间协同配置TSN中的网络设备。

Description

TSN中控制器间通信的方法、装置及系统
本申请要求于2019年5月25日提交中国专利局、申请号为201910420783.1、申请名称为“TSN中控制器间通信的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及时间敏感网络(Time-Sensitive Networking,TSN)中控制器间通信的方法、装置及系统。
背景技术
时间敏感网络(Time-Sensitive Networking,TSN)是由电气和电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)802.1的TSN工作小组发展的标准。该标准主要定义以太网上的时间敏感传输的机制，TSN技术特别注重传输的确定性时延、低时延以及高可用性。TSN的应用场景十分广泛，其中，工业界普遍认为，TSN的相关技术是工业自动化、工业互联网、和智能制造的重要使能技术。
TSN技术可分为数据面、控制面、时间同步、可靠性四大部分。其中，控制面的工作是由TSN域内控制器根据用户需求，对网络设备进行资源预留，从而支持TSN数据面对数据流的转发。例如，控制器通过用户-网络接口(User-to-Network Interface,UNI)获取用户需求信息，根据网络配置协议(Network Configuration Protocol,NETCONF)完成对所属的TSN域中网络设备的配置。因此，如何实现同一TSN域内或不同TSN域的控制器间的通信和交互成为需要解决的问题。
发明内容
本申请提供TSN中控制器之间通信的方法、装置及系统，实现TSN中控制器之间的通信和交互。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种TSN中控制器间通信的方法。第一控制器接收第二控制器发送的包括第二控制器的TSN的域标识的第一报文，其中，第一报文可以是边缘控制协议(Edge Control Protocol，ECP)报文，还可以传输控制协议(Transport Control Protocol，TCP)报文。第一控制器根据第二控制器的TSN域标识确定所述第一控制器和所述第二控制器属于同一TSN域。第一控制器向第二控制器发送携带用户信息的第二报文，其中，第二报文可以是ECP报文，或是TCP报文。第一控制器和第二控制器之间通过控制器间的协议(controller-controller protocol,CCP)进行通信，该协议定义控制器间通信的报文格式，以及报文中所携带的属性信息。第一报文还可以包括第二控制器的标识或地址。通过上述方法，同一TSN域内的控制器之间可以通信和交互信息，实现控制器间协同管理TSN域内的网络设备。
结合第一方面，在一种可能的实现方式中，第一控制器保存的用户信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制(Media Access Control，MAC)地址，虚拟局域网(virtual local area network，VLAN)标签，第四版互联网协议(Internet Protocol version 4，IPv4)元组，第六版互联网协议(Internet Protocol version6，IPv6)元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。例如，用户信息可以包括上述全部信息，还可以仅包括流标识一个信息，第一控制器可根据预先设置的规则从上述信息中选取。通过上述方法，可以实现TSN域内控制器之间对用户信息的同步，当活跃控制器发生故障或者失效时，可以由其他保存有用户信息的控制器实现对该TSN域的资源配置和管理。
在一种可能的实现方式中，第一控制器获取第二控制器的有效值，例如从第一报文中获取第二控制器的有效值，或者从其他报文中获得第二控制器的有效值。有效值用于表示第一控制器的是否处于活跃状态。例如，有效值为0表示第二控制器不是活跃控制器；有效值为1表示第二控制器处于选举状态，经过选举可以成为活跃控制器；有效值为2表示第二控制器为活跃控制器。第一控制器根据第二控制器的有效值确定第二控制器处于选举状态。第一控制器根据预设规则确定该TSN域内处于选举状态中的一个控制器为活跃控制器。例如预设规则可以是根据控制器标识数值最小的控制器为活跃控制器。本申请所称的活跃(active)状态是指处于管理和配置所属TSN域中的控制器的状态。选举状态是指处于参选可能成为活跃控制器时的状态。通过上述方法，不仅可以实现控制器间的通信，使控制器之间了解相互状态，还可以实现有效控制器的选举和切换。
在一种可能的实现方式中，第一控制器和第二控制器所属的TSN域中还包括第四控制器。当活跃控制器的状态失效时，第一控制器接收所述第四控制器发送的第四控制器的有效值。第一控制器根据第四控制器的有效值确定第四控制器处于选举状态。第一控制器根据第一控制器的有效值确定第一控制器也处于选举状态。第一控制器根据预设规则确定该TSN域内处于选举状态中的一个或多个控制器中的一个控制器为活跃控制器，被选举的活跃控制器可以是第一控制器，还可以是第四控制器。通过该方法，可以在活跃控制器失效时，进行活跃控制器的自动选举和切换，避免因为活跃控制器失效出现管理配置的中断。
在一种可能的实现方式中，将确定为活跃控制器的状态信息在设定周期内发送给其他网络设备。例如，当经过选举确定第一控制器为活跃控制器时，第一控制器在设定周期内将自己处于活跃状态的状态信息携带在ECP报文或者TCP报文发送给其他网络设备。通过对活跃控制器的状态信息的宣告，使得TSN中的网络设备获得活跃控制器的信息，以便网络设备向活跃控制器发送信息。
在一种可能的实现方式中，第一控制器包括但不限于第一端口和第二端口，其中，第一控制器通过第一端口接收第一报文。当所述第一控制器确定所述第一端口和所述第二端口属于同一TSN域，第一控制器通过第二端口将第一报文转发到第一网络设备。通过该方法，可以在同一TSN域内扩散第一报文，使得同一TSN中的网络设备通过第一报文了解第二控制器属性信息。
在一种可能的实现方式中，第一报文还可以包括第二控制器的标识或第二控制器的MAC地址。第一控制器根据第二控制器的标识或第二控制器的MAC地址向第二控制器发送第二报文。由此，第一控制器可以根据控制器的标识或MAC地址向其他控制器发送报文，实现控制器间的通信。
第二方面，提供一种TSN中控制器间通信的方法。第一控制器接收第二控制器发送的第一报文，其中，第一报文携带第二控制器所属的TSN域标识。第一控制器根据第二控制器的TSN域标识确定第一控制器和第二控制器不属于同一TSN域。第一控制器向所述第二控制器发送第二报文，该第二报文包括所述第一控制器所属的第一TSN域标识以及与第一TSN域相邻的第二TSN域标识。第一控制器和第二控制器之间可以根据CCP协议进行信息的交互，例如将CCP协议所定义的控制器的属性信息封装在TCP或ECP报文中进行发送或者接收。通过上述方法，可以通过定义控制器间的通信协议，实现不同TSN域的控制器之间的信息交互。
在一种可能的实现方式中，所述第一控制器根据数据流目的地址确定该数据流到达目的地址经过的一个或多个TSN域。第一控制器向所确定的一个或多个TSN域的活跃控制器发送该数据流的属性信息。采用上述方法，使得不同TSN域的控制器协商管理，可以实现对数据流的跨TSN域的资源配置。
在一种可能的实现方式中，所述数据流的属性信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。
在一种可能的实现方式中，第一控制器接收第二控制器的有效值，第二控制器的有效值为活跃状态。第一控制器根据第二控制器的有效值向第二控制器发送所述第一控制器有效值，第一控制器的有效值为活跃状态。采用该方法，可以实现不同TSN域的活跃控制器之间的交互。
在一种可能的实现方式中，第一控制器接收第二控制器发送的第三报文，所述第三报文包括第二控制器所属的第二TSN域标识以及与第二TSN域相邻的第三TSN域标识。第三TSN不同于所述第一TSN和第二TSN。采用上述方法，可以实现控制器对所属TSN域边界信息的了解，使得控制器获取相邻TSN域的信息。
第三方面，本发明实施例提供了一种TSN中的控制器，执行第一方面，第一方面的任意一种可能的实现方式中的方法，第二方面或第二方面任意一种可能的实现方式中的方法。例如，该控制器包括用于执行第一方面，第一方面的任意一种可能的实现方式中的方法，第二当面或第二方面的任意一种可能的实现方式中的方法的单元。
第四方面，提供了一种控制器，该控制器包括：处理器、网络接口和存储器。存储器可以用于存储程序代码，处理器用于调用存储器中的程序代码执行前述第一方面，第二方面的任意一种可能的实现方式中的方法，第二当面或第二方面的任意一种可能的实现方式中的方法，具体参见方法示例中的详细描述，此处不再赘述。
第五方面，提供了一种控制器，该控制器包括：主控板和接口板。主控板包括：第一处理器和第一存储器。接口板包括：第二处理器、第二存储器和接口卡。第二存 储器可以用于存储程序代码，第二处理器用于调用第二存储器中的程序代码执行如下操作：接收携带第二控制器TSN域标识第一报文，发送携带用户信息的第二报文。
第一存储器可以用于存储程序代码，第一处理器用于调用第一存储器中的程序代码执行如下操作：根据第一报文中携带的第二控制器的TSN域标识确定第一控制器和第二控制器处于同一TSN域。
第六方面，提供了一种TSN中控制器间通信的系统，该系统包括第一控制器和第二控制器。
第一控制器用于接收第二控制器发送的第一报文，根据第二控制器的TSN域标识确定与第二控制器属于同一TSN域，向第二控制器发送第二报文。第一报文包括第二控制器所属的TSN的域标识。第二报文包括第一控制器保存的用户信息。
第二控制器用于发送第一报文，并接收第二报文。
第七方面，提供了一种TSN中控制器间通信的系统，该系统包括第一控制器和第二控制器。
第一控制器用于接收第二控制器发送的第一报文，根据所述第二控制器的TSN域标识确定与所述第二控制器不属于同一TSN域，向所述第二控制器发送第二报文。第一报文包括第二控制器所属的TSN的域标识。第二报文包括第一控制器所属的第一TSN域标识以及与第一TSN域相邻的第二TSN域标识。
第二控制器用于发送第一报文，并接收第二报文。
第八方面，提供了一种计算机存储介质，用于储存为上述网络设备或控制器所用的计算机软件指令，其包括用于执行上述方面所设计的程序。
第九方面，提供了一种计算机程序产品，该计算机程序产品包括计算机代码，当该计算机程序代码在计算机上运行时，使得计算机执行上述任一方面的程序。
附图说明
图1为本申请实施例提供的一种TSN场景示意图；
图2为本申请实施例提供的另一种TSN场景示意图；
图3为本申请实施例提供的又一种TSN场景示意图；
图4为本申请实施例提供的一种控制器的结构示意图；
图5为本申请实施例提供的一种TSN中控制器间通信的方法流程示意图；
图6为本申请实施例提供的一种TSN中控制器间发送的ECP报文的格式示意图；
图7为本申请实施例提供的一种TSN中控制器间发送的TCP报文的格式示意图；
图8为本申请实施例提供的一种TSN中控制器间通信的场景示意图；
图9为本申请实施例提供的一种TSN中控制器间选举活跃控制器的方法流程示意图；
图10为本申请实施例提供的一种TSN中控制器间通信的方法流程示意图；
图11为本申请实施例提供的又一种TSN中控制器通信的方法流程示意图；
图12为本申请实施例提供的又一种控制器的结构示意图；
图13为本申请实施例提供的又一种控制器的结构示意图；
图14为本申请实施例提供的又一种控制器的结构示意图；
图15为本申请实施例提供的又一种控制器间通信的系统结构示意图。
具体实施方式
本申请说明书和权利要求书及上述附图中的术语“第一”、“第二”和“第三”等是用于区别不同对象，而不是用于限定特定顺序、时序、优先级或者重要程度。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了下述各实施例的描述清楚简洁，首先对TSN技术进行简要介绍：
时间敏感网络(Time-Sensitive Networking,TSN)也可以称为时效性网络，是由(Institute of Electrical and Electronics Engineers,IEEE)802.1工作组的时间敏感网络任务组进行研究的标准。该标准强调传输的超低延迟以及高可用性。TSN主要应用于各种支持低延时及基于时间同步数据传输的以太网协议，可能的应用包括在需要实时监控或是实时反馈的工业自动化、工业互联网、智能制造，或者结合实时影音串流以及实时控制串流的整合性网络等场景。
TSN可以包括不同的TSN域。TSN域的划分是根据TSN中网络设备端口配置的TSN域(domain)标识(identification,ID)确定的。例如，两个不同的端口的TSN域标识相同，表明上述两个端口属于同一TSN域；两个不同端口的TSN域标识不同，表明所述两个端口分别属于不同的TSN域。网络设备的端口可以配置TSN域标识，不同的端口可以配置不同的TSN域标识。网络设备端口的TSN域标识可以通过静态配置，也可以通过控制器发送配置信息进行配置，还可以通过其他方式进行配置，本申请对TSN域的配置方式不作限制。
本地链路注册协议(Link-local Registration Protocol，LRP)用于促进系统中的网络设备之间分发应用程序，该系统包括通过IEEE 802媒体连接的网络，例如，该系统可以是包括发话端，收听端，转发设备和控制器的网络。LRP可同时支持多个应用协议在网络中分发信息，包括信息的宣告、传输和注册等，并为每个应用协议在网络设备的每个端口维护一个宣告数据库和注册数据库。也可以说，每个端口具有一个LRP实体，上述数据库存在于这个LRP实体中。LRP通过在系统之间创建点对点双向关联来完成传输应用程序的任务。每个关联由两个单向路径组成，每个路径一端是数据库，另一端是注册商数据库。LRP快速可靠地复制数据库中的应用程序到其邻居的注册商数据库。这些数据的传输可以通过传输控制协议(Transport Control Protocol，TCP)或边缘控制协议(Edge Control Protocol，ECP)传输。
为了下述各实施例的描述清楚简洁，首先对TSN场景模型进行简要介绍：
IEEE 802.1Qcc-2018定义了三种TSN配置模型，关于TSN配置模型的具体说明可参考IEEE P802.1Qcc的第46节“时间敏感网络(TSN)配置”中的相关说明。如图1所示，本申请提供了其中一种TSN集中式网络模型。TSN集中式网络中可以包括发话端(Talker)106，收听端(Listener)107，网络设备102-网络设备105，以及控制器 101。如图1所示，控制器101可以通过网络设备102-网络设备105接收发话端106和收听端107发送的需求信息，还可以通过集中用户配置(centralized user configuration,CUC)接收需求信息，然后根据需求信息进行资源预留。控制器101将资源预留信息发给网络设备102-105。由此，发话端106可以通过网络设备102-网络设备105发送数据流给收听端107，实现数据流传输的超低延迟以及高可用性。
下面对图1所示TSN场景中的网络设备进行说明。
发话端106和收听端107可以被称为TSN中的终端站(end station)，是指端到端发送和接收数据流的两端设备。发话端106还可以被称为入节点(ingress)或起始节点，接收端107还可以被称为出节点(egress)或尾端节点。网络设备102-网络设备105可以被称为TSN中的传输设备或转发设备。例如，在二层网络场景中，网络设备102-网络设备105可以包括网桥(bridges)。发话端和收听端也可以是具有网桥功能的设备，例如，发话端106是实现发送数据流的终端站(end station)，收听端107是实现接收数据流的终端站。网络设备102-网络设备105可以包括桥接设备或交换机等，发话端和收听端可以包括传感器、执行器或服务器等。例如，在三层网络场景中，网络设备102-网络设备105可以是路由器或三层交换机，发话端和收听端可以包括路由器或三层交换机或服务器等网络设备。
网桥(bridge)指一种工作在二层，如数据链路层的网络设备，具备在通信网络中完成数据流的存储与转发的功能，且符合IEEE 802.1标准所定义的全部要求或部分要求的组合，例如，网桥可以是交换机。TSN数据流是指从发送方到接收方的数据流，或者从发话端到收听端的数据流，该数据流传输的特性符合IEEE 802.1 TSN系列标准所定义的全部要求或部分要求的组合。
控制器101可以被称为网络控制器或者集中式网络配置(Centralized Network Configuration)控制器，具备收集TSN域内信息和集中计算的功能，能够实现对网络资源的优化配置。一个TSN域可以有一个控制器，也可以有多个控制器。控制器101可以是一个独立的控制设备，也可以是一个具备控制器功能的模块集成在其他网络设备上。当控制器101是一个功能模块时，可以集成在TSN中的其他网络设备上，例如，图1中的控制器是一个功能模块，可以集成发话端106，收听端107，或网络设备102-网络设备105中任意一个设备上，本申请对控制器的具体形式不做限制。
需要说明的是，本申请中的节点，也可以称为网络设备，该节点可以是转发器、交换机、网桥、网关或者路由器等，也可以是能够实现转发数据流的功能的逻辑或虚拟设备，在本申请实施例中不作限制。
TSN技术可分为数据面、控制面、时间同步和可靠性四部分。对于控制面来说，控制器101可以通过网络设备102-105与发话端设备106和收听端设备107交互配置信息。例如，网络设备101通过用户-网络接口(User-to-Network Interface,UNI)获取发话端106的用户需求信息。控制器101可以通过YANG模型从网络设备102获取发话端106的用户需求信息，控制器101根据获取的用户需求信息规划或预留资源，并将预留资源信息发送给网络设备102。控制器101可以通过YANG模型将预留资源信息发送给网络设备102，即控制器101对网络设备102进行网络配置。其中，关于通过YANG模型获取用户配置信息的方法可以参考因特网工程任务组(Internet  Engineering Task Force，IETF)的征求意见稿(Requirement For Comments，RFC)7950中的相关内容。然后，数据面可以根据控制器下发的资源预留信息实现数据流端到端的传输。
然而，一个TSN域中可能包括一个或者多个控制器，如图2所示，一个TSN域包括控制器101和控制器108。TSN中还可能包括多个不同的TSN域，如图3所示，TSN域1包括控制器301，TSN域2包括控制器302。如果不能实现控制器之间交互通信，就无法避免多个控制器对同一TSN域中网络设备的重复配置，难以实现控制器之间的信息同步以及主备控制器之间的自动切换。而且，数据流从发话端到收听端可能穿越多个TSN域，由于控制器只对本TSN域中的设备进行网络配置，因此，控制器无法实现对离开本TSN域的数据流的寻路机制。因此，如何实现一个域中不同控制器之间，以及不同域之间的控制器的交互和通信成为急需解决的技术问题。
基于上述技术问题，本申请提供TSN中控制器间通信的方法、装置及系统，以解决同一TSN域内或不同TSN域间控制器之间的通信和交互。本申请的基本原理是通过定义一种控制器之间通信的协议，例如控制器-控制器协议(Controller-Controller Protocol,CCP)，其中，CCP泛指具备控制器之间通信功能的协议。可选的，如下表1所示，提供一种控制器间通信协议所定义的属性信息，通过定义CCP携带的属性信息的类型、长度和值，实现TSN域内的控制器之间或不同TSN域的控制器之间的通信。需要说明的是，表1中类型(type)对应的数值用于标识属性信息的不同类型，表1中的类型对应的值还可以用其他值进行区分，本申请对具体数值不做限制。
Figure PCTCN2020089476-appb-000001
Figure PCTCN2020089476-appb-000002
表1
可选的，该CCP协议可以是应用层协议，也可以是其他层的协议，本申请并不限制该协议属于开放式系统互联(open system interconnection，OSI)标准层中的某一层。控制器间通信协议可以包括表1的全部属性信息，也可以包括部分属性信息，控制器间通信协议所包括的属性信息可以根据需要进行选择。
控制器可以将表1中的一个或多个属性信息封装在TCP报文或者ECP报文中发送给其他控制器，换句话说，TSN中控制器之间可以通过TCP报文或ECP报文携带表1中的属性信息，实现控制器之间的通信。关于对表1中属性信息的封装，可以参考对图6和图7的相关描述，下文中结合控制器间的通信过程具体介绍了TCP报文或者ECP报文封装属性信息的具体形式。
需要说明的是，图1至图3仅是对TSN场景的示例描述，该网络架构中包括的各个节点的数量可以根据实际需求配置。图1至图3中各个网络设备的实际产品形态可以根据实际需求配置，图1至图3中只是举例示意了各个网络设备的类型，并不是对此的具体限定。
下面结合附图，对本申请TSN中控制器之间通信的实施例进行进一步阐述。
如图4所示，本申请实施例提供一种具备控制器实体的网络设备的结构示意图，该网络设备可以是具备控制器功能的转发设备，还可以是具备控制器实体的终端站(end station)，即独立的控制器设备。控制器40包括确定模块，CCP应用，LRP实体以及通信端口，其中LRP实体可以包括数据同步(data synchronization)模块和数据传输(data transport)模块。
下面结合图4对控制器的各个部件进行具体的介绍：
其中，确定模块用于确定接收到的属性信息所对应的控制器是否与控制器40属于同一TSN域。
CCP应用中可以包括控制器40的属性信息，例如，CCP应用包括上表1中所示的部分或者全部属性信息。
LRP实体用于同步和传输CCP应用中的数据。进一步的，LRP实体中的数据同步模块用于与CCP应用中的数据保持同步。数据同步模块可以通过获取CCP应用中的属性信息，还可以通过同步将接收的其他网络设备的属性信息传输给CCP应用。LRP实体中的数据传输模块用于传输数据同步模块中的数据，例如数据传输模块将属性信息封装成LRP数据单元(data unit)由通信端口发送给其他网络设备，或者接收其他网络设备发送的数据。
通信端口用于与其他网络设备交互通信，接收或者发送数据。
举例来说，CCP应用包括表1中TLV 23对应的信息。LRP实体通过数据同步模块获取这些信息，然后由数据传输模块通过通信端口发送给其他网络设备。
举例来说，通信端口接收其他控制器发送的携带属性信息的报文，数据传输模块对报文进行处理获取属性信息，并将属性信息传输给数据同步模块，有数据同步模块将该属性信息同步给CCP应用。由此，实现控制器之间的通信。
在一种可能的实现方式中，LRP数据同步模块还可以包括数据注册模块和数据宣告模块。数据注册模块用于注册接收到的其他控制器的属性信息。数据宣告模块用于将需要宣告传输给其他网络设备的属性信息发送给数据传输模块。
一种可能的实现中，图2中的控制器101或控制器108可以包括图4所示的结构。通信端口用于接收第二控制器发送的第一报文，其中，第一报文包括第二控制器所属的TSN的域标识。控制器确定与第二控制器属于相同TSN域，向第二控制器发送包括用户信息的第二报文。确定单元用于根据第二控制器的TSN域标识确定控制器40与第二控制器属于同一TSN域。
一种可能的实现中，图3中的控制器301或控制器302可以具备图4所示的结构。通信端口用于接收第二控制器发送的第一报文，其中，第一报文包括第二控制器所属的TSN的域标识。当控制器确定与第二控制器不属于相同TSN域，向第二控制器发送包括第一控制器所属的第一TSN域标识以及与第一TSN域相邻的第二TSN域标识的第二报文。确定单元用于确定控制器40与第二控制器不属于同一TSN域。
在一种可能的实现方式中，控制器通信端口之间通过ECP报文或者TCP报文转发控制器的属性信息。
可选的，控制器间进行信息交互之前，需先对TSN中网络设备的每个端口配置TSN域标识，实现对TSN域的划分。每个TSN域的所有端口是互相连通的，且连通的路径不需要跨越其它域。
下面结合图2和图3描述TSN中控制器间进行信息交互的过程。可选的，控制器间通信的过程包括网络控制器之间的发现，同一TSN域内控制器之间的选举，活动网络控制器的宣告，活跃控制器的失效切换，TSN域内多个控制器间信息同步，不同TSN域的活跃控制器信息的同步和活跃控制器对跨TSN域的数据流的管理。上述控制器间的交互可以是相互独立，也可以相互结合。
实施例1：控制器之间的通信
如图5所示，为本申请提供一种控制器间通信的方法流程示意图。该方法包括第一控制器和第二控制器之间同步数据的通信过程，其中，第一控制器可以是图2中的控制器101，第二控制器可以图2中的控制器108。第一控制器和第二控制器可以具备图4所示的结构。该方法包括：
S510，第一控制器发送第一报文。
在一种可能的实现方式中，具有控制器实体(network controller entity)的网络设备既可以是独立的控制器设备，也可以是一个具备桥功能的转发设备，即转发设备集成控制器所具备的功能，本申请所称的控制器包括上述两种设备中的任意一个。
在一种可能的实现方式中，控制器可以周期性地发送第一报文，还可以在加入TSN时发送第一报文。可选的，将同一TSN域中多个控制器的发送第一报文的周期设置为相同值，以提高TSN域内控制器间发现的效率。
在一种可能的实现方式中，第一报文包括第一控制器的状态信息，例如状态信息可以为表1类型-长度-内容(Type-Length-Value,TLV)23对应的部分或者全部信息，如下表2所示。第一控制器可以在加入TSN时或者周期性的将自己的TLV 23所对应的部分或者全部信息向同一TSN域中的其他网络设备发送。由此，与第一控制器处于 同一TSN域中的第二控制器通过状态信息了解第一控制器的状态，实现同一TSN域内控制器之间的通信和协商。
举例来说，第一报文包括第一控制器域标识，或者第一报文包括第一控制器的控制器域标识和控制器的媒体接入控制(Media Access Control，MAC)地址。
Figure PCTCN2020089476-appb-000003
表2
在一种可能的实现方式中，如图6所示，提供了一种控制器间通信的报文格式示意图。第一报文的格式可以为图6所示的ECP报文。ECP报文中的上层协议数据单元(upper layer protocol data unit,ULPDU)包括但不限于LRP数据单元(data unit，DU)。LRPDU的记录字段中包括但不限于一个或多个记录字段，其中，记录字段中的应用数据(application data)可以用于携带第一控制器的属性信息。例如，将第一控制器的TLV 23对应的信息使用类型-长度-值的格式被封装在记录的应用数据中，该应用数据被携带在ECP报文的ULPDU中，由第一控制器向相邻的网络设备的端口发送，该网络设备可以是控制器，也可以是转发设备。
在一种可能的实现方式中，如图7所示，提供了另一种控制器间通信的报文格式示意图。第一报文的格式可以为图7所示的TCP报文格式，其中，TCP报文中TCP数据部分包括但不限于LRP DU字段。LRPDU的记录字段中可以包括但不限于一个或多个记录，其中，记录字段中的应用数据(application data)可以用于携带第一控制器的属性信息。例如，将第一控制器的TLV 23对应的信息使用类型-长度-值格式被封装在记录的应用数据中，该应用数据被携带在TCP报文的数据中，由第一控制器的端口向其他网络设备的端口发送。
在一种可能的实现方式中，第一控制器的状态信息可以在第一控制器所属的TSN域内宣告，同一TSN域内的网络设备可以收到第一控制器的状态信息。可选的，TSN域内的网络设备包括第一端口和第二端口。该网络设备通过第一端口接收第一控制器的状态信息。若该网络设备确定第一端口和第二端口属于同一TSN域，则该网络设备通过第二端口将第一控制器的状态信息转发到其他相邻的网络设备。若该网络设备确定第一端口和第二端口不属于同一TSN域，则该网络设备不会继续向其他相邻网络设备转发第一控制器的状态信息，以保证第一控制器的状态信息在第一控制器所属的 TSN域中传输，使得同TSN域中的控制器之间互相了解对方的状态信息。该网络设备可以是第一控制器所属的TSN域中其他控制器，也可以是第一控制器所属的TSN域中转发设备，发话端或者收听端。
S520，第二控制器接收第一控制器发送的第一报文。
在一种可能的实现方式中，第二控制器通过控制器间的通信协议接收第一报文，例如该通信协议为CCP。如图8所示，提供了一种控制器间通过CCP通信的场景示意图。图8中的网络设备801为具备控制器功能的转发设备，网络设备802为转发设备，网络设备803为独立控制器设备，还可以称网络设备801为控制器801，网络设备802为转发设备802，网络设备803为控制器803。例如，网络设备801可以是集成控制器功能模块的网桥，网络设备802可以是没有控制器功能模块的网桥，网络设备803为控制器终端站(end station)。网络设备801-网络设备803中的每个都包括CCP应用和LRP实体，其中网络设备802分别与网络设备801和网络设备803直连。CCP应用包括控制器的属性信息，例如，包括上表1中所示控制器的部分或者全部属性信息。LRP实体用于同步和传输CCP应用中的属性信息。进一步的，LRP实体还可以包括数据同步模块和数据传输模块。数据同步模块用于与CCP应用中的数据保持同步更新，数据传输模块用于执行对CCP应用的传输。网络设备801-网络设备803中的每个网络设备还可以包括逻辑链路控制层(logical link control layer，LLC)和媒体接入控制层(Media Access Control Layer，MAC Layer)。LLC利用MAC层，运行不同类型的程序，以支持协议识别、复用、解复用，从而支持生成树协议和其他高层协议的数据单元的传输和接收。网络设备801-网络设备803中的每个网络设备还包括端口，用于接收或者发送数据。若网络设备801和网络设备802为网桥，网络设备801和网络设备802还可以包括MAC中继实体(MAC relay entity)，MAC relay entity用于实现端口间的帧中继、帧过滤和学习过滤信息。
下面结合图8对控制器之间通过CCP交互信息的过程进行描述：
网络设备801的CCP应用将网络设备801的属性信息，例如将网络设备801的TLV 23对应的信息通过LRP实体的数据同步模块和数据传输模块同步到LRP实体中。LRP实体将该属性信息封装到LRPDU中。网络设备801的将该LRPDU封装成ECP报文发送给网络设备802，其中ECP可以用于相邻直连端口之间的数据传输。网络设备801还可以将该LRPDU封装成TCP报文发送给网络设备803。网络设备802的端口接收网络设备801发送的ECP报文，通过MAC layer和LLC将数据帧传输给网络设备802的LRP实体。网络设备802的LRP实体通过数据同步模块将获取的网络设备801的信息传输给网络设备802的CCP应用。网络设备803的端口接收网络设备801发送的TCP报文，通过MAC layer和LLC将数据帧传输给网络设备803的LRP实体。网络设备803的LRP实体通过数据同步模块将获取的控制器801的信息传输给网络设备803的CCP应用。由此，网络设备802和网络设备803可以获取网络设备801的属性信息，实现网络设备801对其属性信息的宣告和控制器之间的通信。
可选的，网络设备803还可以通过网络设备802的转发获取网络设备801的属性信息。
S530，第二控制器根据第一控制器的域标识确定第一控制器和第二控制器属于同 一TSN域。
在一种可能的实现方式中，第一控制器的域标识用于标识第一控制器所属的TSN域的标识。如果第一控制器和第二控制器的TSN域标识相同，则第一控制器和第二控制器属于同一TSN域。
S540，第二控制器向第一控制器发送第二报文。
在一种可能的实现方式中，第二报文包括第一控制器保存的用户信息。可选的，第二报文还可以包括标识或者指令，用于指示第一控制器同步第二报文中的用户信息。由此，可以实现TSN域内控制器间数据信息的同步。当活跃控制器出现故障时，由于TSN域内其他控制器保存有同步信息，因此可以进行TSN域中活跃控制器的切换，保证对TSN域中网络设备的管理和配置，实现资源预留。
在一种可能的实现方式中，第二报文携带的用户信息包括发话端(Talker)，流标识(Stream ID)，流排名(Stream Rank)，终端站设备接口(End Station Interfaces)，接口标识(Interfaces ID)，数据帧格式(Data Frame Specification)，媒体接入控制(Media Access Control，MAC)地址(IEEE802-Mac Addresses)，虚拟局域网(virtual local area network，VLAN)标签(IEEE802-Vlan Tag)，第四版互联网协议(Internet Protocol version 4，IPv4)元组(IPv4-tuple)，第六版互联网协议(Internet Protocol version6，IPv6)元组(IPv6-tuple)，流格式(Traffic Specification)，流规范时间感知(Traffic Specification Time Aware)，用户到网络需求(User To Network Requirements)，接口性能(Interface Capabilities)，收听端(Listener)，状态(Status)，状态信息(Status Information)，累计延迟(Accumulated Latency)，接口配置(Interface Configuration)，时间感知偏移(Time Aware Offset)和失效端口(Failed Interfaces)中的一个或多个。第二控制器可以根据需要从上述用户信息中选择一个或多个发送给第二控制器。
在一种可能的实现方式中，第二控制器可以根据第一报文中携带的第一控制器的MAC地址向第一控制器发送第二报文。
在一种可能的实现方式中，第二报文可以是图6所示的ECP报文或者图7所示的TCP报文。第一控制器将用户信息封装在ECP报文中的方式可以参考步骤S510中图6对第一报文格式的介绍。第一控制器将用户信息封装在TCP报文中的方式可以参考步骤S510中图7对第一报文的介绍。简单来说，就是将图6中的TLV 23对应的信息换成TLV 1-21中的部分或者全部信息，最终封装在ECP报文中，或者将图7中的TLV 23对应的信息换成TLV 1-21中的部分或者全部信息，最终封装在TCP报文中。
S550，第一控制器接收第二控制器发送的第二报文。
在一种可能的实现方式中，第二报文包括第一控制器保存的用户信息。可选的，第二报文还可以包括标识或者指令，第一控制器根据该标识或者指令同步第二报文中的用户信息。
可选的，第一控制器和第二控制器还可以通过ECP报文或TCP报文发送或者获取如下者3中的信息，报文具体格式可以参考图6或图7的相关描述。通过该方法，可以实现控制器间同步数据信息，以及控制器间的使能选举。
Figure PCTCN2020089476-appb-000004
Figure PCTCN2020089476-appb-000005
表3
可选的，实施例1所描述的控制器间通信的方法还可以包括控制之间选举活跃控制器的过程，如图9所示，提供了又一种控制器间通信的方法流程示意图。该方法中控制器间的通信可以根据CCP交互信息，该方法包括：
S910，第一控制器向第二控制器发送第一控制器的有效值。
在一种可能的实现方式中，第一控制器将其有效值封装在第一报文或其他报文中发送给第二控制器。第一控制器的有效值用于表示第一控制器的是否处于活跃状态。例如，等有效值为0表示第一控制器不是活跃控制器；有效值为1表示第一控制器处于选举状态，经过选举可以成为活跃控制器；有效值为2表示第一控制器为活跃控制器。本申请所称的活跃(active)状态是指处于管理和配置所属TSN域中的网络设备的状态。选举状态是指处于参选成为活跃控制器时的状态。
在一种可能的实现方式中，在第一控制器向第二控制器发送第一控制器的有效值之前，第一控制器确定在预定时间内未发现所属TSN域中存在活跃控制器，将自己的有效值设置为选举状态对应数值。
举例来说，结合图2，控制器101在预定时间中确定TSN域内未收到控制器102发送的上表1中的Controller Active值为2的状态信息，控制器101将自己的有效值设为1，并将自己处于选举状态的有效值宣告给TSN域内其他网络设备。
在一种可能的实现方式中，第一控制器使用CCP将第一控制器的TLV 23(表1所示)对应的内容发送给第二控制器，使得第二控制器获取第一控制器的有效值。
S920，第二控制器获取所述第一控制器的有效值。
在一种可能的实现方式中，第二控制器从第一报文中获取第一控制器的有效值。
S930，第二控制器根据所述第一控制器的有效值确定第一控制器处于选举状态。
在一种可能的实现方式中，第二控制器同样处于选举状态，第二控制器的有效值与第一控制器的有效值相同。
S940，第二控制器根据预设规则确定处于选举状态的一个或多个控制器中的一个为活跃控制器。
在一种可能的实现方式中，预设规则可以是根据处于选举状态的控制器标识的大小确定，还可以根据处于选举状态的控制器的地址大小确定，例如MAC地址特定比特位数值的大小。
S950，活跃控制器自己的活跃状态发送给其他网络设备。
在一种可能的实现方式中，有效值为活跃状态的控制器向所属TSN域中的网络设备宣告。处于活跃状态的控制器可以在预定周期内向其他网络设备宣告。通过宣告，控制器的活跃状态会被注册到同一TSN域内的网络设备的端口的LRP实体的数据库 中。网络设备通过ECP在相邻网络设备端口之间扩散。由此，该域中的网络设备都能了解当前有效控制器的信息。活跃控制器还可以通过TSN域边界设备向相邻TSN域的控制器宣告其有效状态。由此，可以实现不同域TSN间控制器对活跃状态的宣告，实现TSN域间控制器之间的通信。
在一种可能的实现方式中，第一控制器通过宣告TLV 23将第一控制器为活跃状态的有效值发送给其他网络设备。
举例来说，如图2所示，有效控制器在预定周期宣告TLV 23，其中，Controller Active值为2，该TLV 23会被注册到本TSN域中所有网络设备中的每个端口的LRP数据库，ECP负责在相邻网络设备之间逐条扩散TLV 23，CCP负责在设备内部的端口间扩散TLV 23。
举例来说，如图3所示，有效控制器101可以通过TSN域边界网络设备303和相邻TSN域的边界设备将控制器301的有效状态信息宣告给控制器308。
在一种可能的实现方式中，上述方法还包括当第一控制器出现故障或者失效时，进行控制器的选举并根据预定规则选举新的活跃控制器。对于控制器选举的具体方法可以参考步骤S610至S650的相关描述。控制器失效包括但不限于控制器失去管理TSN域的能力的情况。
实施例2：控制器之间的通信
如图10所示，为本申请提供又一种控制器间通信的方法流程示意图。该方法包括第一控制器和第二控制器的过程，其中，第一控制器可以是图3中的控制器301，第二控制器可以图3中的控制器308。第一控制器和第二控制器可以具备图4所示的结构。该方法包括：
S1010，第一控制器发送第一报文。
在一种可能的实现方式中，第一控制器发送第一报文的实现方式可以参考图5中的步骤S510的相关描述，此处不再赘述。
S1020，第二控制器接收第一控制器发送的第一报文。
在一种可能的实现方式中，第一控制器和第二控制器属于不同的TSN域，第一控制器属于第一TSN域，第二控制器属于第二TSN域，第一TSN域可以与第二TSN域相邻，也可以不相邻。如果第一TSN域与第二TSN域相邻，第二控制器可以通过第二TSN域的边界网络设备获得第一报文。例如，网络设备的第一端口属于第一TSN域，第二端口属于第二TSN域，网络设备处于两个相邻TSN域边界。网络设备通过第一端口获得第一TSN域中第一控制器的第一报文，网络设备可以通过第二端口将第一报文转发给第二TSN域中的活跃控制器。
S1030，第一控制器根据第二控制器的TSN域标识确定第一控制器和第二控制器不属于同一TSN域。
在一种可能的实现方式中，第一控制器的域标识用于标识第一控制器所属的TSN域的标识。如果第一控制器和第二控制器的TSN域标识相同，则第一控制器和第二控制器属于同一TSN域。
S1040，第一控制器向第二控制器发送第二报文。
在一种可能的实现方式中，第二报文包括第一控制器所属的第一TSN域标识以及 与第一TSN域相邻的第二TSN域标识。
在一种可能的实现方式中，第二报文包括表4中所示TLV 25对应的部分或者全部信息，即可以包括第一控制器所属的TSN域标识，相邻TSN域标识和第一控制器的MAC地址中的一个或多个信息。由此，第一控制器可以与相邻TSN域的控制器之间交互信息，相互了解TSN域边界信息。
Figure PCTCN2020089476-appb-000006
表4
在一种可能的实现方式中，第二报文的格式可以参考图6或图7所示报文格式以及对图6和图7的相关解释。
S1050，第二控制器接收第一控制器发送的第二报文。
在一种可能的实现方式中，上述方法还可以包括第一控制器接收第二控制器的有效值，其中，第二控制器的有效值表示第二控制器处于活跃状态。第一控制器根据第二控制器的有效值向第二控制器发送第一控制器有效值，其中，第一控制器的有效值表示第一控制器处于活跃状态。通过该方法使得不同TSN域中的活跃控制器之间了解彼此的活跃状态，实现不同TSN域中活跃控制器之间的通信。
例如，第二控制器可以将携带有效值的TLV 23的报文发送给相邻网络设备，相邻网络设备将第一报文进一步转发。第二控制器宣告产生的TLV 23可以跨越TSN域传输。可选的，边界网络设备接收到其他TSN域发送的TLV 23时，将该TLV 23转发给本TSN域中的活跃控制器。
在一种可能的实现方式中，TSN域边界可能存在于设备间。例如，TSN中的B2、B3属于不同的TSN域。B3的端口P3收到B2发送的TLV 23，发现其控制器所属的TSN域标识与P3所属的TSN域标识不同，则由P3将所属TSN域中的控制器的TLV 25转发给B2。然后，B2将该TLV 25转发给B2所属TSN域的活跃控制器。
可选的，实施例2所描述的控制器间通信的方法还可以包括图11中所示的方法步骤。如图11所示，提供了又一种控制器间通信的方法流程示意图。图11所示的方法不仅可以实现控制器之间的通信，还可以实现控制器对跨越不同TSN域的数据流的配置，该方法包括：
S1110，第一控制器根据数据流目的地址确定所述数据流到达所述目的地址经过的第三TSN域。
在一种可能的实现方式中，第一控制器根据数据流的目的地址，确定该数据流需要流经的下一个TSN域为相邻TSN域。
在一种可能的实现方式中，第一控制器根据数据流的IP或者MAC地址，确定数 据流到达该目的地址这条路径上要经过的一个或多个TSN域。
在一种可能的实现方式中，第一控制器保存了MAC地址与TSN域标识的对应关系。第一控制器根据数据流的MAC地址确定对应的TSN域。可选的，第一控制器保存了TSN网络拓扑信息，第一控制器根据数据流的MAC地址确定数据流到达目的地址的路径信息。第一控制器进一步根据路径中需要经过的网络设备来确定数据流需要经过的一个或多个TSN域。
S1120，第一控制器向所述第三TSN域的活跃控制器发送所述数据流的属性信息。
在一种可能的实现方式中，数据流的属性信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个信息。
通过上述方法，不仅可以实现控制器之间的交互，还可以对经过多个TSN域的数据流进行配置，从而支持多个TSN域控制器之间的协同配置。
图12示出了上述实施例中所涉及的控制器的一种可能的结构示意图，该控制器可以实现图5和图8至图11所示的实施例中的第一控制器或第二控制器的功能。参阅图12，该控制器1200包括：接收单元1201，确定单元1202和发送单元1203。这些单元可以执行上述方法示例中控制器的相应功能。接收单元1201，用于支持控制器1200执行图5中的过程S520和S550，图9中的过程S920，图10中的过程S1020和S1050；确定单元1202，用于支持控制器1200执行图5中的过程S530，图9中的过程S930和S940，图10中的过程S1030，图11中的过程S1110；发送单元1203，用于支持控制器1200执行图5中的过程S510和S540，图9中的过程S910和S950，图10中.的过程是S1010和S1040，图11中的过程S1120。
接收单元1201，用于执行上述方法实施例中控制器执行的各种信息接收；确定单元1202，用于执行上述方法实施例中控制器执行的确定动作；发送单元1203，用于执行上述方法实施例中控制器执行的各种信息发送。
在一种可能的实现方式中，接收单元1201用于接收包括所述第二控制器所属的TSN的域标识的第一报文。确定单元1202用于根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器属于同一TSN域。发送单元1203用于向所述第二控制器发送包括第一控制器保存的用户信息的第二报文。具体执行过程请参考上述图5和图8至图11所示实施例中相应步骤的详细描述，这里不再一一赘述。
在一种可能的实现方式中，接收单元1201用于接收包括所述第二控制器所属的TSN的域标识的第一报文。确定单元1202用于根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器不属于同一TSN域。发送单元1203用于向所述第二控制器发送包括该控制器所属的第一TSN域标识以及与所述第一TSN域相邻的第二TSN域标识的第二报文。具体执行过程请参考上述图5和图8至图11所示实施例中相应步骤的详细描述，这里不再一一赘述
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在 一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，接收单元和发送单元可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
参阅图13所示，为本申请实施例提供一种控制器的结构示意图，该控制器1300包括：处理器1302、收发器1303、存储器1301以及总线1304。其中，收发器1303、处理器1302以及存储器1301通过总线1104相互连接；总线1304可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。该控制器1300可以实现图5和图8至图11所示的实施例中的控制器的功能。处理器1302和收发器1303可以执行上述方法示例中控制器的相应功能。收发器1303用于支持第控制器1300执行图5中的过程S510，S520，S540和S550，图9中的过程S910，S920和S950，图10中的过程S1010，S1020，S1040和S1050，图11中的过程S1120。处理器1302用于支持控制器1300执行图5中的过程S530，图9中的过程S930和S940，图10中的过程S1030，图11中的过程S1110。存储器1301，用于存储控制器1300的程序代码和数据。
下面结合图1300对控制器的各个构成部件进行具体的介绍：
其中，存储器1301可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；或者非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；或者上述种类的存储器的组合，用于存储可实现本申请方法的程序代码、TSN域内网络设备的配置文件或其他内容。
处理器1302是控制器的控制中心，可以是一个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个数字信号处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
收发器1303用于与其他设备之间通信。
一种可能的实现中，控制器可以配置为图2中的控制器101或控制器108，控制器101可以称为第一控制器，控制器108可以称为第二控制器。处理器1302通过运行或执行存储在存储器1301内的软件程序和/或模块，以及调用存储在存储器1301内的数据，执行如下功能：
根据所述第二控制器的域标识确定所述第一控制器和所述第二控制器属于同一TSN域。
通过收发器1303接收第二控制器发送的携带第二控制器所属的TSN的域标识的第一报文，向第二控制器发送携带用户信息的第二报文。
一种可能的实现中，控制器可以配置为图3中的控制器301或控制器302，控制器301可以称为第一控制器，控制器302可以成为第二控制器。处理器1302通过运行 或执行存储在存储器1301内的软件程序和/或模块，以及调用存储在存储器1301内的数据，执行如下功能：
根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器不属于同一TSN域。
通过收发器1303接收第二控制器发送携带第二控制器所属的TSN的域标识的第一报文，向第二控制器发送携带第一控制器所属的第一TSN域标识以及与所述第一TSN域相邻的第二TSN域标识的第二报文。
具体执行过程请参考上述图5和图8至图11所示实施例中相应步骤的详细描述，这里不再一一赘述。
参阅图14所示，本申请实施例提供了另一种具备控制器实体的装置的结构示意图。该控制器1400为路由器或交换器或有转发功能的网络设备，控制器1400能够实现前述方法实施例中的第一控制器或第二控制器的功能。控制器1400包括：主控板1401和接口板1402。主控板1401包括：处理器1403和存储器1404。接口板1402包括：处理器1405、存储器1406和接口卡1407。主控板1401和接口板1402耦合。
这些硬件可以执行上述方法示例中的相应功能，例如，存储器1406可以用于存储接口板1402的程序代码，处理器1405用于调用存储器1406中的程序代码触发接口卡1407执行上述方法实施例中控制器执行的各种信息接收和发送，例如，处理器1405调用存储器1406中的程序代码触发接口卡1407支持控制器1400执行图5中的过程S530，图10中的过程S1030。处理器1405，还用于将业务标识向主控板1401发送。
存储器1404可以用于存储主控板1401的程序代码，处理器1403用于调用存储器1404中的程序代码执行上述方法实施例中控制器除了信息收发之外的其他处理。例如，处理器1403用于支持第一控制器1400执行，图9中的过程S930和S940和图11中的过程S1110。存储器1404用于存储主控板1401的程序代码和数据。具体执行过程请参考上述图5和图8至图11所示实施例中相应步骤的详细描述，这里不再一一赘述。
在一种可能的实现方式中，主控板1401和接口板1402之间建立IPC控制通道，主控板1401和接口板1402之间利用该IPC控制通道进行通信。
参阅图15所示，发明实施例提供了一种TSN中控制器间通信业务的系统1500，该系统1500用于实现前述方法实施例中的业务报文发送的方法。该系统1500包括第一控制器1501和第二控制器1502。该第一控制器1501和第二控制器1502可以分别实现图5和图8至图11所示的实施例中的第一控制器和第二控制器的功能。
例如，第一控制器1501执行图5中的过程S510、S530和S550，图9中的过程S910图10中的过程S1010、S1030和S1040，图11中的过程S1110和S1120，和/或用于本文所描述的技术中第一控制器执行的其它过程。第二控制器1502执行图5中的过程S520、S530和S540，图9中的过程S920至S950，图10中的过程S1020和S1050，和/或用于本文所描述的技术中第一控制器执行的其它过程。
在一种可能的实现方式中，第一控制器用于接收第二控制器发送的第一报文，根据第二控制器的TSN域标识确定与第二控制器属于同一TSN域，向第二控制器发送第二报文。第一报文包括第二控制器所属的TSN的域标识。第二报文包括第一控制器保存的用户信息。
第二控制器，用于发送第一报文，并接收第二报文。
在一种可能的实现方式中，第一控制器用于接收第二控制器发送的第一报文，根据所述第二控制器的TSN域标识确定与所述第二控制器不属于同一TSN域，向所述第二控制器发送第二报文。第一报文包括第二控制器所属的TSN的域标识。第二报文包括第一控制器所属的第一TSN域标识以及与第一TSN域相邻的第二TSN域标识。
本申请实施例还提供了一种存储介质，用于储存前述实施例中所用的软件指令，其包括用于执行前述实施例所示的方法的程序，当其在计算机或设备上执行时，使得所示计算机或设备执行前述方法实施例中的方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品包括计算机代码，当该计算机程序代码在计算机上运行时，使得计算机执行前述方法实施例中的方法。
需说明的是，以上描述的任意装置实施例都仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本发明提供的第一网络设备或控制器实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read only memory，ROM)、可擦除可编程只读存储器(erasable programmable ROM，EPROM)、电可擦可编程只读存储器(electrically EPROM，EEPROM)、硬盘、移动硬盘、光盘或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (27)

  1. 一种时间敏感网络TSN中控制器之间通信的方法，其特征在于，所述方法包括：
    第一控制器接收第二控制器发送的第一报文，所述第一报文包括所述第二控制器所属的TSN的域标识；
    所述第一控制器根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器属于同一TSN域；
    所述第一控制器向所述第二控制器发送第二报文，所述第二报文包括所述第一控制器保存的用户信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一控制器保存的用户信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一控制器获取所述第二控制器的有效值；
    所述第一控制器根据所述第二控制器的有效值确定所述第二控制器处于选举状态；
    所述第一控制器根据第一预设规则确定所述第一控制器所属的TSN域内处于选举状态中的一个或多个控制器中的一个控制器为活跃控制器。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述方法还包括：
    当活跃控制器失效时，所述第一控制器接收第四控制器发送的所述第四控制器的有效值，所述第四控制器与所述第一控制器属于同一TSN域；
    所述第一控制器根据所述第四控制器的有效值确定所述第四控制器处于选举状态；
    所述第一控制器根据第二预设规则确定所述第一控制器所属的TSN域内处于选举状态中的一个或多个控制器中的一个控制器为活跃控制器。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述第一控制器包括第一端口和第二端口，所述第一控制器通过所述第一端口接收所述第一报文，所述方法还包括：
    当所述第一控制器确定所述第一端口和所述第二端口属于同一TSN域，所述第一控制器通过所述第二端口将所述第一报文转发到第一网络设备。
  6. 根据权利要求1-5任一所述的方法，其特征在于，所述第一报文还包括所述第二控制器的标识或所述第二控制器的目的地址，所述第一控制器向所述第二控制器发送第二报文包括：
    所述第一控制器根据所述第二控制器的标识或所述第二控制器的目的地址向所述 第二控制器发送所述第二报文。
  7. 一种时间敏感网络TSN中控制器之间通信的方法，其特征在于，所述方法包括：
    第一控制器接收第二控制器发送的第一报文，所述第一报文包括所述第二控制器所属的TSN的域标识；
    所述第一控制器根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器不属于同一TSN域；
    所述第一控制器向所述第二控制器发送第二报文，所述第二报文包括所述第一控制器所属的第一TSN域标识以及与所述第一TSN域相邻的第二TSN域标识。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第一控制器根据数据流的目的地址确定所述数据流到达所述目的地址经过的第三TSN域，所述第三TSN域不同于所述第一TSN域和所述第二TSN域；
    所述第一控制器向所述第三TSN域的活跃控制器发送所述数据流的属性信息。
  9. 根据权利要求8所述的方法，其特征在于，所述数据流的属性信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。
  10. 根据权利要求7-9中任一所述的方法，其特征在于，所述方法还包括：
    所述第一控制器获取所述第二控制器的有效值；
    所述第一控制器根据所述有效值确定所述第二控制器处于活跃状态；
    所述第一控制器向所述第二控制器发送所述第一控制器有效值，所述第一控制器的有效值表示所述第一控制器处于活跃状态。
  11. 根据权利要求7-10中任一所述的方法，其特征在于，所述方法还包括：所述第一控制器接收所述第二控制器发送的第三报文，所述第三报文包括所述第二控制器所属的所述第二TSN域标识以及与所述第二TSN域相邻的第三TSN域标识。
  12. 一种时间敏感网络TSN中装置，其特征在于，所述装置包括：
    发送单元，用于接收第二控制器发送的第一报文，所述第一报文包括所述第二控制器所属的TSN的域标识；
    确定单元，用于根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器属于同一TSN域；
    发送单元，用于向所述第二控制器发送第二报文，所述第二报文包括第一控制器保存的用户信息。
  13. 根据权利要求12所述的装置，其特征在于，所述第一控制器保存的用户信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。
  14. 根据权利要求12或13所述的装置，其特征在于，所述装置还包括：
    获取单元，用于从所述第一报文中获取所述第二控制器的有效值；
    所述确定单元，还用于根据所述第二控制器的有效值确定第二控制器处于选举状态，并根据预设规则确定所述第一控制器所属的TSN域内处于选举状态中的一个或多个控制器中的一个控制器为活跃控制器。
  15. 根据权利要求12-14中任一所述的装置，其特征在于，当活跃控制器的状态失效时，所述接收单元还用于接收所述第四控制器发送的所述第四控制器的有效值，所述第四控制器与所述第一控制器属于同一TSN域；
    所述确定单元，还用于根据所述第四控制器的有效值确定所述第四控制器处于选举状态，并根据所述预设规则确定所述第一控制器所属的TSN域内处于选举状态中的一个或多个控制器中的一个控制器为活跃控制器。
  16. 根据权利要求12-15中任一所述的装置，其特征在于，所述装置还包括第一端口和第二端口，所述第一端口用于接收所述第一报文；
    当所述确定单元确定所述第一接收单元所在的端口与所述第二接收单元所在的端口属于同一TSN域时，所述第二端口用于将所述第一报文转发到第一网络设备。
  17. 根据权利要求12-16中任一所述的装置，其特征在于，所述第一报文还包括所述第二控制器的标识或所述第二控制器的目的地址，所述发送单元还用于根据所述第二控制器的标识或所述第二控制器的目的地址向所述第二控制器发送所述第二报文。
  18. 一种时间敏感网络TSN中的装置，其特征在于，所述装置包括：
    发送单元，用于接收第二控制器发送的第一报文，所述第一报文包括所述第二控制器所属的TSN的域标识；
    确定单元，用于根据所述第二控制器的TSN域标识确定所述第一控制器和所述第二控制器不属于同一TSN域；
    发送单元，用于向所述第二控制器发送第二报文，所述第二报文包括所述第一控制器所属的第一TSN域标识以及与所述第一TSN域相邻的第二TSN域标识。
  19. 根据权利要求18所述的装置，其特征在于，所述确定单元还用于根据数据流目的地址确定所述数据流到达所述目的地址经过的第三TSN域，所述第三TSN域不 同于所述第一TSN域和所述第二TSN域；
    所述发送单元，还用于向所述第三TSN域的活跃控制器发送所述数据流的属性信息。
  20. 根据权利要求19所述的装置，其特征在于，所述数据流的属性信息包括发话端，流标识，流排名，终端站设备接口，接口标识，数据帧格式，媒体接入控制MAC地址，虚拟局域网VLAN标签，第四版互联网协议IPv4元组，第六版互联网协议IPv6元组，流格式，流规范时间感知，用户到网络需求，接口功能，收听端，状态，状态信息，累计延迟，接口配置，时间感知偏移和失效端口中的一个或多个。
  21. 根据权利要求18-20任一所述的装置，其特征在于，
    所述接收单元，还用于接收所述第二控制器的有效值，所述第二控制器的有效值为活跃状态；
    所述发送单元，还用于根据所述第二控制器的有效值向所述第二控制器发送所述第一控制器有效值，所述第一控制器为所属TSN域中的活跃控制器。
  22. 根据权利要求18-21任一所述的装置，其特征在于，所述接收单元还用于接收所述第二控制器发送的第三报文，所述第三报文包括所述第二控制器所属的所述第二TSN域标识以及与所述第二TSN域相邻的第三TSN域标识。
  23. 一种时间敏感网络TSN中控制器之间通信的系统，其特征在于，所述系统包括：
    第一控制器，用于接收第二控制器发送的第一报文，根据所述第二控制器的TSN域标识确定与所述第二控制器属于同一TSN域，向所述第二控制器发送第二报文，所述第一报文包括所述第二控制器所属的TSN的域标识，所述第二报文包括所述第一控制器保存的用户信息；
    第二控制器，用于发送所述第一报文，并接收所述第二报文。
  24. 根据权利要求23所述的系统，其特征在于，该系统包括权利要求12至17所述的第一控制器。
  25. 一种时间敏感网络TSN中控制器之间通信的系统，其特征在于，所述系统包括：
    第一控制器，用于接收第二控制器发送的第一报文，根据所述第二控制器的TSN域标识确定与所述第二控制器不属于同一TSN域，向所述第二控制器发送第二报文，所述第一报文包括所述第二控制器所属的TSN的域标识，所述第二报文包括所述第一控制器所属的第一TSN域标识以及与所述第一TSN域相邻的第二TSN域标识；
    第二控制器，用于发送所述第一报文，并接收所述第二报文。
  26. 根据权利要求25所述的系统，其特征在于，该系统包括权利要求18至22所述的第一控制器。
  27. 一种计算机可读介质，其特征在于，包括计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行权利要求1至11中任一项所述的方法。
PCT/CN2020/089476 2019-05-20 2020-05-09 Tsn中控制器间通信的方法、装置及系统 WO2020233430A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2021569191A JP7292427B2 (ja) 2019-05-20 2020-05-09 Ｔｓｎ内のコントローラ間の通信のための方法、装置、およびシステム
EP20810380.4A EP3958509A4 (en) 2019-05-20 2020-05-09 METHOD, DEVICE AND SYSTEM FOR COMMUNICATION BETWEEN CONTROLLERS IN TSN
MX2021014146A MX2021014146A (es) 2019-05-20 2020-05-09 Metodo, aparato y sistema para comunicacion entre controladores en tsn.
US17/531,122 US11811511B2 (en) 2019-05-20 2021-11-19 Method, apparatus, and system for communication between controllers in TSN

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910420783.1A CN111970137B (zh) 2019-05-20 2019-05-20 Tsn中控制器间通信的方法、装置及系统
CN201910420783.1 2019-05-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/531,122 Continuation US11811511B2 (en) 2019-05-20 2021-11-19 Method, apparatus, and system for communication between controllers in TSN

Publications (1)

Publication Number Publication Date
WO2020233430A1 true WO2020233430A1 (zh) 2020-11-26

Family

ID=73357764

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/089476 WO2020233430A1 (zh) 2019-05-20 2020-05-09 Tsn中控制器间通信的方法、装置及系统

Country Status (6)

Country Link
US (1) US11811511B2 (zh)
EP (1) EP3958509A4 (zh)
JP (1) JP7292427B2 (zh)
CN (2) CN114826891A (zh)
MX (1) MX2021014146A (zh)
WO (1) WO2020233430A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117061439A (zh) * 2023-10-10 2023-11-14 长沙先度科技有限公司 一种tsn实时以太网交换机的数据处理方法

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112260923B (zh) * 2019-07-22 2023-05-02 中兴通讯股份有限公司 一种桥接网络信息通告方法和设备
CN111600754B (zh) * 2020-05-11 2022-02-25 重庆邮电大学 一种面向tsn和非tsn互联的工业异构网络调度方法
CN112491493B (zh) * 2020-11-23 2022-12-13 鹏城实验室 一种时间敏感网络时隙分配方法及报文转发方法
CN114567580B (zh) * 2020-11-27 2023-10-20 华为技术有限公司 一种消息发送方法、消息处理方法、装置及系统
CN112615930B (zh) * 2020-12-25 2022-08-23 北京东土科技股份有限公司 多节点数据同步分发方法、装置、设备及存储介质
WO2023067762A1 (ja) * 2021-10-21 2023-04-27 日本電信電話株式会社 信号転送システム、信号転送制御装置、信号転送制御方法及びプログラム
CN115801544B (zh) * 2023-01-29 2023-05-23 北京智芯微电子科技有限公司 网络监测方法、设备、系统及存储介质
CN115915098B (zh) * 2023-02-15 2023-06-06 鹏城实验室 一种5g与tsn跨域ptp中bmca实现方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209897A (zh) * 2016-07-28 2016-12-07 重庆邮电大学 一种基于代理的软件定义网络分布式多粒度控制器安全通信方法
US20180084055A1 (en) * 2016-09-19 2018-03-22 General Electric Company Vehicle control system
CN108965171A (zh) * 2018-07-19 2018-12-07 重庆邮电大学 工业无线wia-pa网络与时间敏感网络转换方法及装置
CN109691038A (zh) * 2016-07-19 2019-04-26 施耐德电器工业公司 时间敏感的软件定义的网络

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4448474B2 (ja) 2005-05-18 2010-04-07 日本電信電話株式会社 ノード装置およびノード機器
JP4598789B2 (ja) 2007-02-22 2010-12-15 日本電信電話株式会社 経路計算制御方法、経路計算制御プログラムおよび経路計算制御装置
JP4900101B2 (ja) 2007-07-18 2012-03-21 株式会社Ｊｖｃケンウッド ドメイン結合方法
US8897306B2 (en) 2007-08-22 2014-11-25 Nippon Telegraph And Telephone Corporation Path management control method, path management control program, path management controller and path management control system
CN101860474B (zh) * 2009-04-08 2015-07-22 中兴通讯股份有限公司 基于对等网络的资源信息处理方法及对等网络
JP5954827B2 (ja) 2012-12-26 2016-07-20 日本電気株式会社 ネットワーク装置
CN104754762B (zh) * 2013-12-30 2019-12-03 中兴通讯股份有限公司 软件自定义网络中自动发现控制器的方法、控制器及系统
KR20150094238A (ko) * 2014-02-11 2015-08-19 한국전자통신연구원 종단 시스템의 라이프 사이클에 따라 가상 확장 랜의 세그먼트를 위한 멀티캐스팅 터널을 자동적으로 구성하는 가상 확장 랜 네트워크 시스템 및 그 동작 방법
CN106302351B (zh) 2015-06-03 2019-10-15 华为技术有限公司 收集访问控制列表的方法、装置及系统
US10805222B2 (en) 2017-05-01 2020-10-13 General Electric Company Resilient network configuration for time sensitive traffic
JP2017175522A (ja) 2016-03-25 2017-09-28 日本電気株式会社 ネットワークシステム、制御装置、方法およびプログラム
CN106549873A (zh) * 2016-12-09 2017-03-29 北京邮电大学 一种异构控制器之间的通信方法及系统
CN108737003B (zh) * 2017-04-25 2021-10-26 是德科技新加坡(销售)私人有限公司 用于测试时间敏感网络(tsn)元件的方法、系统和计算机可读介质
US10439871B2 (en) * 2017-09-25 2019-10-08 Cisco Technology, Inc. Deterministic stitching of deterministic segments across distinct deterministic domains
US11115343B2 (en) * 2017-10-05 2021-09-07 Cisco Technology, Inc. Transport layer providing deterministic transport across multiple deterministic data links
US10461886B2 (en) * 2017-10-16 2019-10-29 Cisco Technology, Inc. Transport layer identifying failure cause and mitigation for deterministic transport across multiple deterministic data links
US10439940B2 (en) * 2017-10-19 2019-10-08 Cisco Technology, Inc. Latency correction between transport layer host and deterministic interface circuit
US10798012B2 (en) * 2017-10-30 2020-10-06 Cisco Technology, Inc. Jitter elimination and latency compensation at DetNet transport egress
US10897516B2 (en) * 2017-11-15 2021-01-19 Cisco Technology, Inc. Application buffering of packets by fog computing node for deterministic network transport
US10754816B2 (en) * 2018-12-21 2020-08-25 Intel Corporation Time sensitive networking device
EP3767899A1 (de) * 2019-07-17 2021-01-20 Siemens Aktiengesellschaft Verfahren zur datenkommunikation, netzwerk, computerprogramm und computerlesbares medium
US11038799B2 (en) * 2019-07-19 2021-06-15 Cisco Technology, Inc. Per-flow queue management in a deterministic network switch based on deterministically transmitting newest-received packet instead of queued packet
US11848176B2 (en) * 2020-07-31 2023-12-19 Applied Materials, Inc. Plasma processing using pulsed-voltage and radio-frequency power
US11948780B2 (en) * 2021-05-12 2024-04-02 Applied Materials, Inc. Automatic electrostatic chuck bias compensation during plasma processing
US11791138B2 (en) * 2021-05-12 2023-10-17 Applied Materials, Inc. Automatic electrostatic chuck bias compensation during plasma processing
US11476090B1 (en) * 2021-08-24 2022-10-18 Applied Materials, Inc. Voltage pulse time-domain multiplexing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109691038A (zh) * 2016-07-19 2019-04-26 施耐德电器工业公司 时间敏感的软件定义的网络
CN106209897A (zh) * 2016-07-28 2016-12-07 重庆邮电大学 一种基于代理的软件定义网络分布式多粒度控制器安全通信方法
US20180084055A1 (en) * 2016-09-19 2018-03-22 General Electric Company Vehicle control system
CN108965171A (zh) * 2018-07-19 2018-12-07 重庆邮电大学 工业无线wia-pa网络与时间敏感网络转换方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3GPP; Technical Specification Group Services and System Aspects; Study on enhancement of 5G System (5GS) for vertical and Local Area Network (LAN) services (Release 16)", 3GPP TR 23.734 V16.1.0, 31 March 2019 (2019-03-31), XP051722871 *
VARGA, B. ET AL.: "DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over MPLS", IETF DRAFT-IETF-DETNET-TSN-VPN-OVER-MPLS-00, 5 May 2019 (2019-05-05), pages 1 - 17, XP015132825 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117061439A (zh) * 2023-10-10 2023-11-14 长沙先度科技有限公司 一种tsn实时以太网交换机的数据处理方法
CN117061439B (zh) * 2023-10-10 2023-12-12 长沙先度科技有限公司 一种tsn实时以太网交换机的数据处理方法

Also Published As

Publication number Publication date
CN111970137A (zh) 2020-11-20
CN111970137B (zh) 2022-04-05
EP3958509A1 (en) 2022-02-23
US20220078076A1 (en) 2022-03-10
JP7292427B2 (ja) 2023-06-16
JP2022533238A (ja) 2022-07-21
MX2021014146A (es) 2022-01-04
US11811511B2 (en) 2023-11-07
CN114826891A (zh) 2022-07-29
EP3958509A4 (en) 2022-06-15

Similar Documents

Publication Publication Date Title
WO2020233430A1 (zh) Tsn中控制器间通信的方法、装置及系统
US10230577B2 (en) Packet broadcast mechanism in a split architecture network
CN105763359B (zh) 用于交织结构交换机集群的分布式双向转发检测协议(d-bfd)
CN102577277B (zh) 提供合并多点链路的逻辑聚合点对点数据链路
US9769054B2 (en) Network topology discovery method and system
US7233991B2 (en) Self-healing tree network
EP2533475B1 (en) Method and system for host route reachability in packet transport network access ring
CN102055665B (zh) 广播上或nbma上的ospf点到多点模式
US20080101362A1 (en) Method and device for making uplink standby
CN110891026A (zh) 一种流量调度方法、设备及系统
WO2020114017A1 (zh) 数据中心流量互通方法、装置、设备及存储介质
CN115426316A (zh) 一种fttr网关负载均衡的系统及方法
CN111083061A (zh) 一种确定组播流的df的方法、设备及系统
WO2013104279A1 (zh) Trill网络中设置cvlan的方法和装置
EP3068082B1 (en) Fault processing method and apparatus for edge route bridge in trill network
JP7127537B2 (ja) トランスポートネットワーク制御装置、通信システム、転送ノードの制御方法及びプログラム
WO2021098806A1 (zh) 报文传输路径的切换方法、设备和系统
WO2016086721A1 (zh) 在trill网络中传输组播数据的方法、装置和系统
CN112073203A (zh) 一种业务恢复方法、装置、电子设备及存储介质
WO2018108121A1 (zh) 设备堆叠建立
CN114172762B (zh) 一种通信方法、装置、系统及可读存储介质
WO2020177540A1 (zh) 基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质
CN117118912A (zh) 报文传输方法、网络设备和通信系统
CN111385182A (zh) 流量的传输方法及装置，物理拓扑结构
KR20100112140A (ko) 패킷 스위칭 네트워크에 대한 자원들이 예약을 돕는 방법, 연관된 관리 디바이스, 및 보조 디바이스

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20810380

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021569191

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020810380

Country of ref document: EP

Effective date: 20211116