WO2021233327A1 - 报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统 - Google Patents

报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统 Download PDF

Info

Publication number
WO2021233327A1
WO2021233327A1 PCT/CN2021/094572 CN2021094572W WO2021233327A1 WO 2021233327 A1 WO2021233327 A1 WO 2021233327A1 CN 2021094572 W CN2021094572 W CN 2021094572W WO 2021233327 A1 WO2021233327 A1 WO 2021233327A1
Authority
WO
WIPO (PCT)
Prior art keywords
tsn
message
service
flow identifier
service flow
Prior art date
Application number
PCT/CN2021/094572
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 JP2022570216A priority Critical patent/JP2023525891A/ja
Priority to US17/924,390 priority patent/US20230145093A1/en
Priority to EP21808796.3A priority patent/EP4142219A4/en
Publication of WO2021233327A1 publication Critical patent/WO2021233327A1/zh

Links

Images

Classifications

    • 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
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • 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
    • 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/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/02—Topology update or discovery
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • 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/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • This application relates to the field of network communication technology.
  • TSN Time Sensitive Networking
  • One aspect of the embodiments of the present application provides a message processing method, applied to a bridge node, including: receiving a TSN service message; querying a service flow identifier and a TSN configuration mapping relationship table according to the header of the TSN service message, The mapping relationship table between the service flow identifier and the TSN configuration is established according to the notification information of the source device; and the TSN service message is processed according to the query result of the mapping relationship table between the service flow identifier and the TSN configuration.
  • An aspect of the embodiments of the present application also provides a notification method, which is applied to a source device, including: sending notification information, the notification information including a service flow identifier and corresponding TSN configuration; and sending a TSN service message, the TSN service message is sent by The bridge node performs processing according to the notification information.
  • An aspect of the embodiments of the present application also provides a network bridge node, including: one or more processors; and, a storage device configured to store one or more programs; when one or more programs are used by one or more The processor executes, so that one or more processors implement the message processing method provided in the embodiment of the present application.
  • An aspect of the embodiments of the present application provides a source device, including: one or more processors; and, a storage device configured to store one or more programs; when one or more programs are used by one or more processors Execution, so that one or more processors implement the notification method provided in the embodiment of the present application.
  • One aspect of the embodiments of the present application also provides a message processing system, including: a destination device, at least one bridge node, and a source device; wherein: the source device is configured to send notification information to at least one bridge node, the notification information Including the service flow identifier and the corresponding TSN configuration; at least one bridge node is configured to receive time-sensitive network TSN service messages; query the service flow identifier and the TSN configuration mapping relationship table according to the header of the TSN service message, the service The mapping relationship table between the flow identifier and the TSN configuration is established according to the notification information of the source device; and, the TSN service message is processed according to the query result of the mapping relationship table between the service flow identifier and the TSN configuration; and the destination device is configured to receive at least A TSN service message processed by a bridge node.
  • An aspect of the embodiments of the present application further provides a computer-readable storage medium on which a computer program is stored.
  • the computer program when executed by a processor, implements the message processing method or the notification method provided in the embodiment of the present application.
  • Figure 1 is a schematic diagram of an application scenario of TSN.
  • Fig. 2 is a flowchart of a message processing method provided by an embodiment of the application.
  • Fig. 3 is another flowchart of a message processing method provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of a Stream Reservation Protocol (SRP) extension message provided by an embodiment of the application.
  • SRP Stream Reservation Protocol
  • Fig. 5 is a schematic diagram of announcing TSN configuration provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a Link Layer Discovery Protocol (LLDP) extended message provided by an embodiment of the application.
  • LLDP Link Layer Discovery Protocol
  • FIG. 7 is a flowchart of the notification method provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a message processing apparatus provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of a structure of an announcement device provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of a hardware structure of a bridge node provided by an embodiment of the application.
  • FIG. 11 is a schematic diagram of a hardware structure of a source device provided by an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of a message processing system provided by an embodiment of this application.
  • each TSN node may support zero, one, or multiple TSN-profile capabilities.
  • TSN nodes receives a TSN service flow message, if the TSN node has the TSN-profile capability required by the TSN service flow, it can provide services consistent with the TSN service requirements.
  • FIG 1 is a schematic diagram of an application scenario of TSN.
  • the source device refers to the Talker in the TSN network; the destination device refers to the Listener in the TSN network.
  • the presence or absence of a hollow triangle and a hollow circle indicate whether the TSN node supports the service flow corresponding to the source device 1 (Talker 1) and the source device 2 (Talker 2). For the TSN-profile of the stream, if there is support, if there is no support, it is not supported.
  • the destination node of the service flow of source device 1 is destination device 1 (Listener 1) and destination device 3 (Listener 3), and the destination node of the service flow of source device 2 is destination device 2 (Listener 2).
  • a service path has been established for source device 1 to destination device 1: source device 1 -> TSN node 1 -> TSN node 4 -> TSN node 5 -> TSN/DetNet edge node; service is established for source device 1 to destination device 3 Path: source device 1->TSN node 1->TSN node 2.
  • TSN node 1 When TSN node 1, TSN node 2, TSN node 4, TSN node 5, or TSN/DetNet receives a TSN service packet from source device 1, it needs to identify the TSN-profile corresponding to the service packet; if the TSN node (TSN node 1. TSN node 4, TSN node 5 or TSN/DetNet) supports the TSN-profile, then the TSN service message is processed according to the corresponding strategy; if the TSN node (TSN node 2) does not support the TSN-profile, it needs to follow the original The forwarding process processes TSN service packets.
  • TSN node Due to the lack of effective standard protocols or schemes that can regulate the collection, judgment, and dissemination of TSN-profile capabilities of each TSN node, it is not clear whether each TSN node can provide services consistent with the requirements of the TSN service flow. If the TSN service message arrives at a TSN node that does not have the corresponding capability, it will also affect the processing efficiency of the TSN service message. Therefore, the reliability of the TSN service message processing process is poor.
  • the embodiment of the present application provides a message processing method, which can be applied to a bridge node.
  • the bridge node receives the TSN service message, it determines whether the bridge node has the TSN configuration capability of the TSN service message by querying the mapping relationship table established according to the notification information of the source device, and then processes the TSN service message accordingly , Improve the reliability of TSN service message processing.
  • FIG. 2 is a flowchart of a message processing method provided by an embodiment of the application. As shown in FIG. 2, the method may include steps 110, 120, and 130.
  • step 110 a TSN service message is received.
  • the TSN service message may be a message sent by the source device, and is finally transmitted to the destination device after being processed by the bridge node.
  • the received TSN service packet may be sent by the source device and directly reach the bridge node, or it may be sent by the source device and transmitted by other bridge nodes. After arriving at the bridge node.
  • step 120 the service flow identifier and the mapping relation table configured by the TSN are queried according to the header of the TSN service message, and the mapping relation table is established according to the notification information of the source device.
  • the information carried in the header of the TSN service message can indicate which service flow the TSN service message belongs to, what TSN configuration is required, etc., and in the bridge node, according to the source device in advance
  • the sent notification information establishes the mapping relationship table between the service flow identifier and the TSN configuration. Therefore, when receiving the TSN service message, the bridge node can query the mapping relationship table according to the header of the TSN service message to determine the bridge Whether the node has the TSN configuration for processing the TSN service message.
  • step 130 the TSN service message is processed according to the query result of the mapping relationship table.
  • the bridge node can determine whether it has the TSN configuration for processing the TSN service message by querying the mapping relationship table; if so, the bridge node can provide the TSN service flow that is consistent with the requirements of the TSN service flow. Service; otherwise, the bridge node cannot effectively process the TSN service message.
  • the method may further include: obtaining the notification information of the source device in response to the notification trigger condition,
  • the notification information includes the service flow identifier and the corresponding TSN configuration; when the set conditions are met, the service flow identifier and TSN configuration supported by the bridge node are extracted from the notification information and written into the local mapping relationship table.
  • the source device can send notification information to the bridge node by extending SRP, LLDP, etc., when the notification is triggered, thereby notifying the bridge node of the service flow identifier of the TSN service packet and the required TSN configuration.
  • the bridge node can extract key information from it, and establish a mapping relationship table between the service flow identifier and the TSN configuration, so that it can be based on the TSN service message received The message header is queried and processed accordingly.
  • the bridge node needs to maintain the TSN configuration supported by it, and also needs to establish a mapping relationship table between the service flow identifier and the TSN configuration according to the advertisement information.
  • Table 1 shows the mapping relationship between the service flow identifier and the TSN configuration.
  • each type of service flow identifier corresponds to a type of TSN configuration, and each type of TSN configuration can be represented by a different configuration value.
  • the corresponding TSN configuration is "1"
  • the bridge node receives the notification information, it extracts the service flow identifier and TSN configuration from it, and writes it into the mapping table shown in Table 1.
  • the TSN configuration may include but is not limited to the following categories: 1) P802.1CM-2018, TSN configuration of the fronthaul (Fronthaul) TSN network; 2) IEC/IEEE 60802, Industrial Automation (Industrial Automation) 3) P802.1DC, TSN configuration of Quality of Service (QoS) for network systems (Network Systems); 4) P802.1DF, TSN configuration of Service Provider Networks (Service Provider Networks); 5 ) P802.1DG, the TSN configuration of Automotive In-Vehicle Ethernet Communications; and/or, 6) P802.1CMde, which is used to support the new fronthaul interface and the enhanced TSN configuration of the fronthaul profile of the synchronization standard .
  • P802.1CM-2018 TSN configuration of the fronthaul (Fronthaul) TSN network
  • P802.1DC TSN configuration of Quality of Service (QoS) for network systems (Network Systems)
  • P802.1DF TSN configuration
  • the format, configuration value, and meaning of the fields used to carry the TSN configuration are different, which is not limited in the embodiment of the present application.
  • the method may further include: in the case where the set conditions are met, reserved for Process the bandwidth resources of TSN service messages, and establish forwarding entries for TSN service messages.
  • the bridge node when the set conditions are met, can reserve bandwidth resources for TSN service messages, establish forwarding entries, and perform corresponding processing when receiving TSN service messages.
  • processing the TSN service message according to the query result may include: if the message header is consistent with the service flow identifier supported by the bridge node and the TSN configuration, using the reserved bandwidth resources, according to the forwarding table entry The TSN service message is forwarded to the destination device.
  • the source device after successfully reserving bandwidth resources and establishing a forwarding path, the source device sends a TSN service message, and the TSN service message is transmitted along a certain service path.
  • the TSN service message is transmitted along a certain service path.
  • each bridge node receives the TSN service message , Obtain the service flow identifier by parsing the packet header, and query the mapping table based on this to determine the TSN configuration required for the service flow. If the bridge node has the corresponding TSN configuration, it can use the reserved bandwidth resources for processing and follow Forwarding the table entry forwards the message; otherwise, the TSN service message cannot be processed.
  • Fig. 3 is another flowchart of a message processing method provided by an embodiment of the application. As shown in Fig. 3, the message processing method may include steps 101-106.
  • step 101 in response to the notification trigger condition, the notification information of the source device is obtained, and the notification information includes the service flow identifier and the corresponding TSN configuration.
  • the notification trigger condition may include at least one of the following: receiving a notification trigger command, receiving the first TSN service message sent by the source device, or receiving a protocol extension message sent by the source device.
  • the notification trigger conditions may include but are not limited to the following: 1) The notification trigger command is received, where the notification trigger command may be generated by any node in the TSN network, for example, it may be connected to the TSN network A notification trigger command sent by a client connected to a certain node. After the notification trigger command is received by the source device or bridge node, the trigger source device sends notification information to each bridge node, and each bridge node receives the notification information and establishes a mapping Relationship table; 2) The first TSN service message sent by the source device is received, that is, the source device can trigger the notification of the TSN configuration through the TSN service message.
  • the bridge node directly connected to the source device receives the TSN service packet of the first source device, it starts the notification process as a proxy; 3) It receives the protocol extension packet sent by the source device, that is, the source device can The notification of TSN configuration is triggered by protocol extension messages.
  • the source device is required to support the extension of related protocols (such as SRP or LLDP, etc.).
  • step 102 when the set conditions are met, the service flow identifier and TSN configuration supported by the bridge node are extracted from the advertisement information, and written into the local mapping relationship table.
  • step 103 when the set conditions are met, bandwidth resources for processing the TSN service message are reserved, and a forwarding entry for the TSN service message is established.
  • the setting condition may include: the service flow identifier in the notification information matches the service flow identifier of the response message of the destination device, and the bandwidth resource of the bridge node is greater than or equal to the TSN corresponding to the service flow identifier Bandwidth resources required by the business.
  • the bridge node combines the service stream identifier (Stream Id) field of the advertisement information carried in the broadcast message of the source device (ie Talker Advertise message) with the destination device’s
  • the service stream identifier (Stream Id) field of the response message i.e. Listener Ready message
  • the match is successful, the value of the Data Frame Priority field in the Talker Advertise message can be used to determine whether the bridge node corresponds to the port queue.
  • bandwidth resource meets the requirements of the service flow; if it is satisfied, the service flow identifier in the notification information and the configuration value of the TSN configuration are written into the mapping relationship table, and bandwidth resources for processing TSN service packets are reserved and established The forwarding entry of the TSN service message; if it is not satisfied, the resource reservation fails and the forwarding entry cannot be established.
  • step 104 a TSN service message is received.
  • step 105 the mapping relationship between the service flow identifier and the TSN configuration is queried according to the header of the TSN service message.
  • step 106 when the message header is consistent with the service flow identifier supported by the bridge node and the TSN configuration, the reserved bandwidth resource is used to forward the TSN service message to the destination device according to the forwarding entry.
  • the notification information may be transmitted through an SRP protocol extension message; the protocol extension message may include a service flow identification field and a TSN configuration field.
  • FIG. 4 is a schematic diagram of an SRP extension message (that is, an SRP protocol extension message) provided by an embodiment of the application.
  • SRP is used as an example to describe a protocol extension message used to carry notification information.
  • the advertisement information is carried in the Talker Advertise message of the extended SRP.
  • the format of the extended Talker Advertise message is shown in Figure 4.
  • the TSN-profile field occupies 2 Octets, which can represent up to 216 TSN configurations.
  • Fig. 5 is a schematic diagram of announcing TSN configuration provided by an embodiment of the application.
  • a hollow triangle on the identification of any bridge node indicates that the bridge node supports the TSN configuration required for service flow (Stream 1)
  • a hollow circle on the identification of any bridge node indicates the bridge The node supports the TSN configuration required by the service stream (Stream 2).
  • the table above represents the field content of the Talker Advertise header of Stream 1, indicating that the service flow ID of Stream 1 is ⁇ 01:00:5e:01:01:01,2 ⁇ , which is required
  • the configuration value corresponding to the TSN configuration is 1; in addition, the SRP extension message under the bridge node 1 also indicates that the virtual local area network (VLAN) ID is 2.
  • VLAN virtual local area network
  • the table on the left of bridge node 2 represents the field content of the Talker Advertise header of Stream 2, indicating that the service flow ID of Stream 2 is ⁇ 01:00:5e:01:01:02,3 ⁇ , which is required
  • the configuration value corresponding to the TSN configuration is 2; in addition, the SRP extension message on the right side of the bridge node 2 also indicates that the VLAN ID is 3.
  • each bridge node extracts Stream 1 service flow identifier ⁇ 01:00:5e:01:01:01,2 ⁇ and TSN configuration value "1" Write the mapping relationship table; in bridge node 2, bridge node 3, and bridge node 5, each bridge node extracts Stream 2 service flow ID ⁇ 01:00:5e:01:01:02,3 ⁇ and The TSN configuration value "2" is written into the mapping table.
  • the notification information can be transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.
  • FIG. 6 is a schematic diagram of an LLDP extended message (ie, an LLDP message) provided by an embodiment of the application.
  • the extensible type-length-content (Type-length-valu, TLV) in the LLDP message (LLDP Data Unit, LLDPDU), that is, the Optional TLVs field, can be extended to carry advertisement information.
  • the extended secondary TLV (sub- The meaning and format of TLV) are specified on demand.
  • a sub-TLV of TSN-profile is carried.
  • the Type field represents the type (configuration value) of the TSN-profile, which occupies 7 bits and is uniformly allocated by the organization.
  • the value range is 9 to 126; the Length field represents the length of the Value field, which occupies 9 bits, and the field value is Octet
  • the value field contains two parts, namely the service flow identifier and TSN-profile.
  • the service flow identifier includes Dest MAC for 6 Octets and VLAN ID for 2 Octets; TSN-profile can occupy 2 Octets, which can represent up to 216 types
  • the configuration value and meaning of TSN-profile and TSN-profile are not limited.
  • the first 6 Octets of the Value field indicate Detst MAC
  • the following 2 Octets indicate VLAN ID
  • the last 2 Octets indicate TSN-profile.
  • the bridge node After the bridge node receives the LLDP protocol extension packet, it can extract the DestMAC, VLAN ID, and TSN-profile values carried in the Value field according to the sub-TLV configured by the TSN carried in the Optional TLVs, and combine ⁇ DestMAC, VlanID ⁇ and The TSN-profile mapping relationship is written into the mapping relationship table.
  • a protocol other than SRP or LLDP may also be used to send the notification information.
  • the embodiment of the present application does not limit the specific protocol and the message format, the content of the service flow identification field, and the TSN configuration field.
  • the source device can advertise the service flow identifier and the corresponding TSN configuration to each bridge node, so that the bridge node can establish a mapping relationship table, and query it when receiving a TSN service message
  • the mapping relationship table handles TSN service messages accordingly, clarifies the TSN configuration capabilities of the bridge node, and improves the reliability and efficiency of message processing.
  • the bridge node can also realize the resource reservation of the TSN service message and the establishment of forwarding entries, which further improves the reliability and efficiency of message processing.
  • the notification information can be transmitted through protocol extension messages of different protocols, and the notification can be triggered by different notification trigger conditions, which improves the flexibility of the notification.
  • the embodiment of the present application also provides a notification method, which can be applied to the source device.
  • the source device By sending notification information, the source device establishes a mapping relationship table for the bridge node, and provides a basis for clarifying whether the bridge node has the TSN configuration capability of the TSN service message. On this basis, the TSN service message is sent to facilitate the bridge node according to the mapping.
  • the relationship table performs corresponding processing on TSN service messages, which improves the reliability of TSN service message processing.
  • FIG. 7 is a flowchart of the notification method provided by an embodiment of the application. As shown in FIG. 7, the notification method may include step 210 and step 220. It should be noted that the operations performed by the source device in the embodiment of the present application correspond to the operations performed by the bridge node in the foregoing embodiment. For technical details not described in detail in the embodiments of the present application, please refer to any of the foregoing implementable manners.
  • step 210 the notification information is sent, and the notification information includes the service flow identifier and the corresponding TSN configuration.
  • step 220 the TSN service message is sent, and the TSN service message is processed by the bridge node according to the notification information.
  • the notification trigger condition for sending the notification information may include at least one of the following: receiving the notification trigger command, sending the first TSN service message, or sending the protocol extension message.
  • the notification information can be transmitted through an SRP protocol extension message;
  • the protocol extension message includes a service flow identification field and a TSN configuration field.
  • the notification information can be transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.
  • the source device can notify the service flow identifier and the corresponding TSN configuration to each bridge node for the bridge node to establish a mapping relationship table, and query the mapping relationship when receiving a TSN service message
  • the table handles TSN service messages accordingly, clarifies the TSN configuration capabilities of the bridge node, and improves the reliability and efficiency of message processing.
  • the notification information can be transmitted through protocol extension messages of different protocols, and the notification can be triggered by different notification trigger conditions, which improves the flexibility of the notification.
  • FIG. 8 is a schematic structural diagram of a message processing apparatus provided by an embodiment of the application.
  • the message processing apparatus may include: a message receiving module 310, a query module 320, and a message processing module 330.
  • the message receiving module 310 may be configured to receive TSN service messages.
  • the query module 320 may be configured to query the service flow identifier and the mapping relationship table configured by the TSN according to the header of the TSN service message, and the mapping relationship table is established according to the notification information of the source device.
  • the message processing module 330 may be configured to process the TSN service message according to the query result.
  • the message processing device provided by the embodiment of the present application can determine whether the bridge node has the TSN configuration capability of the TSN service message by querying the mapping relationship table established according to the notification information of the source device when the TSN service message is received , So that the TSN service message is processed accordingly, and the reliability of TSN service message processing is improved.
  • the message processing apparatus may further include: a notification information acquisition module, which may be configured to respond to the service flow identifier and the mapping relationship table configured by the TSN according to the header of the TSN service message
  • the notification trigger condition is to obtain the notification information of the source device.
  • the notification information includes the service flow identifier and the corresponding TSN configuration; and the mapping relationship establishment module can be configured to extract the network bridge from the notification information when the set conditions are met
  • the service flow identifier and TSN configuration supported by the node are written into the local mapping table.
  • the setting condition may include: the service flow identifier in the notification information matches the service flow identifier of the response message of the destination device, and the bandwidth resource of the bridge node is greater than or equal to the TSN corresponding to the service flow identifier Bandwidth resources required by the business.
  • the message processing device may further include: a preprocessing module, which may be configured to query the service flow identifier and the mapping relationship table configured by the TSN according to the message header of the TSN service message, before satisfying the requirements Under certain conditions, reserve bandwidth resources for processing TSN service messages, and establish forwarding entries for TSN service messages.
  • a preprocessing module which may be configured to query the service flow identifier and the mapping relationship table configured by the TSN according to the message header of the TSN service message, before satisfying the requirements Under certain conditions, reserve bandwidth resources for processing TSN service messages, and establish forwarding entries for TSN service messages.
  • the message processing module 330 can be specifically configured to: if the message header is consistent with the service flow identifier supported by the bridge node and the TSN configuration, use the reserved bandwidth resources according to the forwarding entry Forward the TSN service message to the destination device.
  • the notification trigger condition may include at least one of the following: receiving a notification trigger command, receiving the first TSN service message sent by the source device, or receiving a protocol extension message sent by the source device.
  • the notification information can be transmitted through an SRP protocol extension message;
  • the protocol extension message includes a service flow identification field and a TSN configuration field.
  • the notification information can be transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.
  • the message processing device provided in the embodiment of this application and the message processing method provided in the embodiment of this application belong to the same inventive concept.
  • For technical details not described in detail in the embodiment of this application please refer to any of the above-mentioned implementable modes, and the implementation of this application
  • the message processing device provided in the example has the same beneficial effects as the message processing method provided in the embodiments of the present application.
  • FIG. 9 is a schematic diagram of a structure of an announcement device provided by an embodiment of the application.
  • the notification device may include a notification module 410 and a message sending module 420.
  • the notification module 410 may be configured to send notification information, and the notification information includes a service flow identifier and a corresponding TSN configuration.
  • the message sending module 420 may be configured to send TSN service messages, and the TSN service messages are processed by the bridge node according to the notification information.
  • the notification device provided by the embodiment of the present application can send notification information to establish a mapping relationship table for bridge nodes and provide a basis for determining whether the bridge node has the TSN configuration capability of TSN service messages, and then send TSN service messages on this basis. It is convenient for the bridge node to process the TSN service message according to the mapping relationship table, which improves the reliability of TSN service message processing.
  • the notification trigger condition for sending the notification information may include at least one of the following: receiving the notification trigger command, sending the first TSN service message, or sending the protocol extension message.
  • the notification information can be transmitted through an SRP protocol extension message;
  • the protocol extension message includes a service flow identification field and a TSN configuration field.
  • the notification information can be transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.
  • the notification device provided by the embodiment of this application and the notification method provided by the embodiment of this application belong to the same inventive concept.
  • the notification provided by the embodiment of this application please refer to any of the above-mentioned implementable modes, and the notification provided by the embodiment of this application
  • the device has the same beneficial effects as the notification method provided in the embodiments of the present application.
  • the embodiment of the present application also provides a network bridge node.
  • the message processing method provided in the embodiments of the present application may be executed by a message processing apparatus, which may be implemented by software and/or hardware, and integrated in a network bridge node.
  • the bridge node may be a TSN node device.
  • FIG. 10 is a schematic diagram of a hardware structure of a bridge node provided by an embodiment of the application.
  • the bridge node may include: a processor 510 and a storage device 520.
  • the processor 510 and the storage device 520 in the device may be connected by a bus or in other ways. In FIG. 10, the connection by a bus is taken as an example.
  • the storage device 520 in the network bridge node is used as a computer-readable storage medium for storing one or more programs, and the one or more programs are executed by one or more processors 510, so that the one or more processing
  • the device 510 implements the message processing method provided in the embodiment of the present application.
  • the program may be a software program, a computer executable program, and a module, such as program instructions/modules corresponding to the message processing method in the embodiment of the present application (for example, the module in the message processing apparatus shown in FIG. 8 includes: The message receiving module 310, the query module 320, and the message processing module 330).
  • the processor 510 executes various functional applications and data processing of the bridge node by running the software programs, instructions, and modules stored in the storage device 520, that is, implements the message processing method provided in the embodiment of the present application.
  • the storage device 520 mainly includes a storage program area and a storage data area.
  • the storage program area can store an operating system and an application program required by at least one function; the storage data area can store data created according to the use of the device, etc. Announcement information, mapping relationship table, etc. in the implementation).
  • the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 520 may further include a memory provided remotely relative to the processor 510, and these remote memories may be connected to the bridge node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the following operations are implemented: receiving a TSN service message; querying the service flow identifier and TSN according to the header of the TSN service message
  • the configured mapping relationship table is established according to the notification information of the source device; and the TSN service message is processed according to the query result of the mapping relationship table.
  • the network bridge node provided in the embodiments of this application and the message processing method provided in the embodiments of this application belong to the same inventive concept.
  • the provided network bridge node has the same beneficial effects as the message processing method provided in the embodiment of the present application.
  • the embodiment of the present application also provides a source device.
  • the notification method may be executed by a notification device, which may be implemented by software and/or hardware, and integrated in the source device.
  • the source device may be a TSN node device.
  • FIG. 11 is a schematic diagram of a hardware structure of a source device provided by an embodiment of the application.
  • the source device may include: a processor 610 and a storage device 620. There may be one or more processors 610 in the source device.
  • One processor 610 is taken as an example in FIG. 11.
  • the processor 610 and the storage device 620 in the device may be connected through a bus or in other ways. In FIG. 11, the connection through a bus is taken as an example.
  • the storage device 620 in the source device serves as a computer-readable storage medium, which can be used to store one or more programs, and the one or more programs are executed by one or more processors 610, so that the one or more processors 610 implements the notification method provided in the embodiment of the present application.
  • the program can be a software program, a computer executable program, and a module, such as the program instruction/module corresponding to the notification method in the embodiment of the present application (for example, the module in the notification device shown in FIG. 9 includes: a notification module 410 and a message Sending module 420).
  • the processor 610 executes various functional applications and data processing of the source device by running the software programs, instructions, and modules stored in the storage device 620, that is, implements the notification method provided in the embodiment of the present application.
  • the storage device 620 mainly includes a storage program area and a storage data area.
  • the storage program area can store an operating system and an application program required by at least one function; the storage data area can store data created according to the use of the device, etc. Announcement information, TSN service message, etc. in the implementation).
  • the storage device 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 620 may further include a memory remotely provided with respect to the processor 610, and these remote memories may be connected to the source device via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the following operations are implemented: sending notification information, the notification information including the service flow identifier and the corresponding TSN configuration; and sending the TSN service report Arts.
  • the source device provided in the embodiment of this application and the notification method provided in the embodiment of this application belong to the same inventive concept.
  • the source provided in the embodiment of this application please refer to any of the above-mentioned implementable modes, and the source provided in the embodiment of this application
  • the device has the same beneficial effects as the notification method provided in the embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a message processing system provided by an embodiment of this application.
  • the system may include: a destination device 730, at least one bridge node 720, and a source device 710.
  • the source device 710 sends notification information to each bridge node 720; the TSN service message sent by the source device 710 is processed by at least one bridge node 720 according to the notification information and then forwarded to the destination device 730.
  • the information sent by the source device 710 needs to go through several bridging processes to reach the destination device 730.
  • Each bridge node 720 will have a distributed clock for time synchronization calculation, and The queue is used to process the priority of the data, including the fast channel method for high dynamic data, and the preemptive mechanism.
  • the source device 710 may be configured to send notification information, the notification information including a service flow identifier and a corresponding TSN configuration; and, to send a TSN service message.
  • the bridge node 720 can be configured to receive TSN service packets; according to the header of the TSN service packet, the service flow identifier and the mapping relationship table configured by the TSN are queried, and the mapping relationship table is based on the source device 710 The notification information is established; and the TSN service message is processed according to the query result of the mapping relationship table.
  • the bridge node 720 may be configured to obtain the source device 710 in response to the notification trigger condition before querying the service flow identifier and the mapping relationship table configured by the TSN according to the header of the TSN service message.
  • the notification information includes the service flow identifier and the corresponding TSN configuration; and, when the set conditions are met, the service flow identifier and TSN configuration supported by the bridge node 720 are extracted from the notification information and written to the local In the mapping table.
  • the setting conditions may include: the service flow identifier in the advertisement information matches the service flow identifier of the response message of the destination device 730, and the bandwidth resource of the bridge node 720 is greater than or equal to the corresponding service flow identifier The bandwidth resources required by the TSN service.
  • the bridge node 720 may be configured to perform a pre-setting before querying the service flow identifier and the mapping relationship table configured by the TSN according to the header of the TSN service message, and when the set conditions are met.
  • the bridge node 720 may be configured to perform the following operations to implement the processing of the TSN service message according to the query result, including: in response to determining the message header and the service flow identifier and TSN supported by the bridge node 720 The configuration is consistent, and the reserved bandwidth resources are used to forward the TSN service message to the destination device 730 according to the forwarding entry.
  • the notification trigger condition may include at least one of the following: receiving a notification trigger command, receiving the first TSN service message sent by the source device 710, or receiving a protocol extension message sent by the source device 710 .
  • the notification information can be transmitted through an SRP protocol extension message;
  • the protocol extension message includes a service flow identification field and a TSN configuration field.
  • the notification information can be transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.
  • the message processing system provided in the embodiment of this application belongs to the same inventive concept as the message processing method or notification method provided in the embodiment of this application.
  • the message processing system provided in the embodiment of the present application has the same beneficial effects as the message processing method or notification method provided in the embodiment of the present application.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are executed by a computer processor, they are used to execute the message processing method or the notification method provided in the embodiment of the present application.
  • the message processing method may include: receiving the TSN service message; querying the service flow identifier and the mapping relationship table configured by the TSN according to the message header of the TSN service message, the mapping relationship table being established according to the notification information of the source device; and, according to the mapping The query result of the relation table processes the TSN service message.
  • the notification method may include: sending notification information, the notification information including the service flow identifier and the corresponding TSN configuration; and, sending the TSN service message.
  • this application can be implemented by software and general hardware, or can be implemented by hardware.
  • the technical solution of the present application can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), Random Access Memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including multiple instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute any of this application
  • a computer device which can be a personal computer, server, or network device, etc.
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) DVD or CD) etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FGPA programmable logic devices

Abstract

本申请涉及网络通信技术领域，并提供一种报文处理方法及装置、通告方法及装置、网桥节点、源设备、报文处理系统，以及计算机可读存储介质。报文处理方法包括：接收时间敏感网络TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，业务流标识和TSN配置的映射关系表根据源设备的通告信息建立；以及，根据对业务流标识和TSN配置的映射关系表的查询结果处理TSN业务报文。

Description

报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统 技术领域
本申请涉及网络通信技术领域。
背景技术
时间敏感网络(Time Sensitive Networking，TSN)标准定义了以太网数据传输的时间敏感机制，为标准以太网增加了确定性和可靠性，以确保以太网能够为关键数据的传输提供稳定一致的服务级别。对于TSN业务，用以提供一致的确定性服务的各种策略和机制即TSN配置(TSN-profile)。在标准中可以具有多种TSN-profile实例，每个网桥节点(即TSN节点)可能支持0种、1种或多种TSN-profile能力。
发明内容
本申请实施例的一个方面提供一种报文处理方法，应用于网桥节点，包括：接收TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，业务流标识和TSN配置的映射关系表根据源设备的通告信息建立；以及，根据对业务流标识和TSN配置的映射关系表的查询结果处理TSN业务报文。
本申请实施例的一个方面还提供一种通告方法，应用于源设备，包括：发送通告信息，通告信息包括业务流标识和对应的TSN配置；以及，发送TSN业务报文，TSN业务报文由网桥节点根据通告信息进行处理。
本申请实施例的一个方面还提供一种网桥节点，包括：一个或多个处理器；以及，存储装置，被配置为存储一个或多个程序；当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现本申请实施例提供的报文处理方法。
本申请实施例的一个方面提供一种源设备，包括：一个或多个 处理器；以及，存储装置，被配置为存储一个或多个程序；当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现本申请实施例提供的通告方法。
本申请实施例的一个方面还提供一种报文处理系统，包括：目的设备、至少一个网桥节点以及源设备；其中：源设备，被配置为向至少一个网桥节点发送通告信息，通告信息包括业务流标识和对应的TSN配置；至少一个网桥节点，被配置为接收时间敏感网络TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，业务流标识和TSN配置的映射关系表根据源设备的通告信息建立；以及，根据对业务流标识和TSN配置的映射关系表的查询结果处理TSN业务报文；以及，目的设备，被配置为接收至少一个网桥节点处理后的TSN业务报文。
本申请实施例的一个方面还提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现本申请实施例提供的报文处理方法或通告方法。
附图说明
图1为TSN的应用场景的一种示意图。
图2为本申请实施例提供的报文处理方法的一种流程图。
图3为本申请实施例提供的报文处理方法的另一种流程图。
图4为本申请实施例提供的流预留协议(Stream Reservation Protocol，SRP)扩展报文的一种示意图。
图5为本申请实施例提供的通告TSN配置的一种示意图。
图6为本申请实施例提供的链路层发现协议(Link Layer Discovery Protocol，LLDP)扩展报文的一种示意图。
图7为本申请实施例提供的通告方法的一种流程图。
图8为本申请实施例提供的报文处理装置的一种结构示意图。
图9为本申请实施例提供的通告装置的一种结构示意图。
图10为本申请实施例提供的网桥节点的一种硬件结构示意图。
图11为本申请实施例提供的源设备的一种硬件结构示意图。
图12为本申请实施例提供的报文处理系统的一种结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。需要说明的是，在不冲突的情况下，本申请实施例中的可实施方式及可实施方式中的特征可以相互任意组合。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
在TSN业务报文处理系统中，通常存在多个网桥节点(即TSN节点)，每个TSN节点可能支持0种、1种或多种TSN-profile能力。当TSN节点接收到某个TSN业务流报文时，若该TSN节点具备该TSN业务流所需要的TSN-profile能力，则能够提供与该TSN业务需求相一致的服务。
图1为TSN的应用场景的一种示意图。如图1所示，TSN仿真域内有6个TSN节点，源设备是指TSN网络中的发布节点(Talker)；目的设备是指TSN网络中的接听节点(Listener)。图1中，在每个TSN节点的图标上，以空心三角形和空心圆的有无，分别表示该TSN节点是否支持对应于源设备1(Talker 1)业务流和源设备2(Talker 2)业务流的TSN-profile，有表示支持，无表示不支持。其中，源设备1业务流的目的节点是目的设备1(Listener 1)和目的设备3(Listener 3)，源设备2业务流的目的节点是目的设备2(Listener 2)。假设已经为源设备1到目的设备1建立业务路径：源设备1->TSN节点1->TSN节点4->TSN节点5->TSN/DetNet边缘节点；为源设备1到目的设备3建立业务路径：源设备1->TSN节点1->TSN节点2。当TSN节点1、TSN节点2、TSN节点4、TSN节点5或TSN/DetNet收到源设备1的TSN业务报文时，需识别该业务报文对应的TSN-profile；若TSN节点(TSN节点1、TSN节点4、TSN节点5或TSN/DetNet)支持该TSN-profile，则按照相应策略处理TSN业务报文；若TSN节点(TSN节点2)不支持该TSN-profile，则需按照原有转发流程处理TSN业务报文。
由于缺乏有效的标准协议或方案能够规范各TSN节点对TSN-profile能力的收集、判断和传播，因此无法明确各TSN节点是否能够提供与TSN业务流的需求相一致的服务。如果TSN业务报文到达不具备相应能力的TSN节点，还会影响TSN业务报文的处理效率。因此，TSN业务报文的处理过程的可靠性较差。
本申请实施例提供一种报文处理方法，可应用于网桥节点。网桥节点在接收到TSN业务报文时，通过查询根据源设备的通告信息建立的映射关系表，确定网桥节点是否具备TSN业务报文的TSN配置能力，从而对TSN业务报文进行相应处理，提高TSN业务报文处理的可靠性。
图2为本申请实施例提供的报文处理方法的一种流程图，如图2所示，该方法可包括步骤110、120和130。
在步骤110中，接收TSN业务报文。
根据本申请提供的实施例，TSN业务报文可以是由源设备发出的报文，经过网桥节点处理后最终传输至目的设备。需要说明的是，对于一个网桥节点，其接收到的TSN业务报文可能是由源设备发出并直接到达该网桥节点的，也可能是由源设备发出并经过了其他网桥节点的传输后到达该网桥节点的。
在步骤120中，根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，映射关系表根据源设备的通告信息建立。
根据本申请提供的实施例，TSN业务报文的报文头中携带的信息可表明该TSN业务报文属于哪个业务流、需要何种TSN配置等，而在网桥节点中，预先根据源设备发出的通告信息建立了业务流标识和TSN配置的映射关系表，因此在接收到TSN业务报文时，网桥节点可以根据TSN业务报文的报文头查询映射关系表，从而确定该网桥节点是否具备处理该TSN业务报文的TSN配置。
在步骤130中，根据对映射关系表的查询结果处理TSN业务报文。
根据本申请提供的实施例，网桥节点可通过查询映射关系表确定是否具备处理该TSN业务报文的TSN配置；如果是，则该网桥节点 能够提供与该TSN业务流的需求相一致的服务；否则该网桥节点无法对该TSN业务报文进行有效处理。
在一种可实施方式中，在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，该方法还可包括：响应于通告触发条件，获取源设备的通告信息，通告信息包括业务流标识和对应的TSN配置；在满足设定条件的情况下，从通告信息中提取网桥节点支持的业务流标识和TSN配置，并写入本地的映射关系表中。
根据本申请提供的实施例，源设备可以在触发通告的情况下，通过扩展SRP、LLDP等，向网桥节点发送通告信息，从而向网桥节点通告TSN业务报文的业务流标识以及所需的TSN配置。当业务流标识以及所需的TSN配置通告到网桥节点时，网桥节点可以从中提取关键的信息，建立业务流标识和TSN配置的映射关系表，从而在接收到TSN业务报文时能够根据报文头查询并进行相应处理。
根据本申请提供的实施例，网桥节点需要维护其支持的TSN配置，还需要根据通告信息建立业务流标识和TSN配置的映射关系表。
表1为业务流标识和TSN配置的映射关系表。如表1所示，每种业务流标识分别对应于一种TSN配置，每种TSN配置可以用不同的配置值表示。例如，对于{01:00:5e:01:01:01,2}的业务流，其对应的TSN配置为“1”，即需要网桥节点具备P802.1DG中对视频系统的TSN配置。网桥节点在接收到通告信息时，从中提取业务流标识和TSN配置，并写入如表1所示的映射关系表中。
表1 业务流标识和TSN配置的映射关系表
Figure PCTCN2021094572-appb-000001
在一种可实施方式中，TSN配置可包括但不限于以下几类：1)P802.1CM-2018，前传(Fronthaul)TSN网络的TSN配置；2)IEC/IEEE 60802，工业自动化(Industrial Automation)的TSN配置；3)P802.1DC，网络系统(Network Systems)的服务质量(Quality of Service，QoS)的TSN配置；4)P802.1DF，服务提供商网络(Service Provider Networks)的TSN配置；5)P802.1DG，车内以太网通信(Automotive In-Vehicle Ethernet Communications)的TSN配置；和/或，6)P802.1CMde，用于支持新的前传界面和同步标准的前传配置文件的增强TSN配置。
在采用不同的扩展协议报文的情况下，用于携带TSN配置的字段的格式、配置值和含义等有所区别，本申请实施例对此不作限定。
在一种可实施方式中，在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，该方法还可包括：在满足设定条件的情况下，预留用于处理TSN业务报文的带宽资源，并建立TSN业务报文的转发表项。
根据本申请提供的实施例，在满足设定条件的情况下，网桥节点可通过为TSN业务报文预留带宽资源、建立转发表项，在接收到TSN业务报文时，进行相应处理。
在一种可实施方式中，根据查询结果处理TSN业务报文可包括：若报文头与网桥节点支持的业务流标识和TSN配置一致，则利用预留的带宽资源，根据转发表项将TSN业务报文转发至目的设备。
根据本申请提供的实施例，在成功预留带宽资源和建立转发路径后，源设备发送TSN业务报文，TSN业务报文沿一定的业务路径传输，各网桥节点接收到TSN业务报文时，通过解析报文头得到业务流标识，据此查询映射关系表，确定该业务流需要的TSN配置，如果该网桥节点具备相应的TSN配置，则可以使用预留的带宽资源进行处理并按照转发表项转发报文；否则无法处理该TSN业务报文。
图3为本申请实施例提供的报文处理方法的另一种流程图。如图3所示，该报文处理方法可包括步骤101-106。
在步骤101中，响应于通告触发条件，获取源设备的通告信息， 通告信息包括业务流标识和对应的TSN配置。
在一种可实施方式中，通告触发条件可包括以下至少之一：接收到通告触发命令，接收到源设备发出的首个TSN业务报文，或接收到源设备发出的协议扩展报文。
根据本申请提供的实施例，通告触发条件可包括但不限于以下几种：1)接收到通告触发命令，其中，通告触发命令可以由TSN网络中的任意节点生成，例如可以是与TSN网络中的某个节点连接的客户端发出的通告触发命令，该通告触发命令被源设备或网桥节点接收后，触发源设备向各网桥节点发送通告信息，各网桥节点接收通告信息并建立映射关系表；2)接收到源设备发出的首个TSN业务报文，即，源设备可以通过TSN业务报文触发TSN配置的通告。例如，与源设备直连的网桥节点在接收到第一个源设备的TSN业务报文时，作为代理开启通告过程；3)接收到源设备发出的协议扩展报文，即，源设备可以通过协议扩展报文触发TSN配置的通告，这种情况下，要求源设备支持相关协议(例如SRP或LLDP等)的扩展。
在步骤102中，在满足设定条件的情况下，从通告信息中提取网桥节点支持的业务流标识和TSN配置，并写入本地的映射关系表中。
在步骤103中，在满足设定条件的情况下，预留用于处理TSN业务报文的带宽资源，并建立TSN业务报文的转发表项。
在一种可实施方式中，设定条件可包括：通告信息中的业务流标识和目的设备的响应报文的业务流标识匹配，且网桥节点的带宽资源大于或等于业务流标识对应的TSN业务所需带宽资源。
根据本申请提供的实施例，以基于SRP进行通告为例，网桥节点将源设备的广播报文(即Talker Advertise报文)中携带通告信息的业务流标识(Stream Id)字段与目的设备的响应报文(即Listener Ready报文)的业务流标识(Stream Id)字段进行匹配，如果匹配成功，则可以根据Talker Advertise报文中的Data Frame Priority字段的值判断网桥节点对应端口队列上的带宽资源是否满足该业务流的需求；若满足，则将通告信息中的业务流标识和TSN配置的配置值写入映射关系表中，并预留用于处理TSN业务报文的带 宽资源、建立TSN业务报文的转发表项；若不满足，则资源预留失败，无法建立转发表项。
在步骤104中，接收TSN业务报文。
在步骤105中，根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表。
在步骤106中，在报文头与网桥节点支持的业务流标识和TSN配置一致的情况下，利用预留的带宽资源，根据转发表项将TSN业务报文转发至目的设备。
在一种可实施方式中，通告信息可通过SRP的协议扩展报文传输；协议扩展报文可包括业务流标识字段和TSN配置字段。
图4为本申请实施例提供的SRP扩展报文(即，SRP的协议扩展报文)的一种示意图。本申请实施例以SRP为例对用于携带通告信息的协议扩展报文进行说明。在采用SRP的情况下，通告信息通过扩展SRP的Talker Advertise报文携带，扩展的Talker Advertise报文的格式如图4所示，其中，TSN-profile字段占2Octets，最多可表示216种TSN配置。TSN-profile字段的不同配置值含义例如可为：TSN-profile＝1，表示P802.1DG的Profile for Audio Systems；TSN-profile＝2，表示P802.1DG的Profile for Vedio Systems；TSN-profile＝3，表示P802.1DG的Profile for Control Systems；TSN-profile＝4，表示P802.1DF的Profile1；以及，TSN-profile＝5，表示P802.1DF的Profile2等。
本申请实施例中所列举的TSN-profile字段的配置值和含义，均仅作为举例说明，本申请实施例对此不作限定。
图5为本申请实施例提供的通告TSN配置的一种示意图。图5中，在任一网桥节点的标识上有空心三角形则表示该网桥节点支持业务流(Stream 1)所需的TSN配置，在任一网桥节点的标识上有空心圆则表示该网桥节点支持业务流(Stream 2)所需的TSN配置。
对于网桥节点1，其上方的表格表示Stream 1的Talker Advertise报文头的字段内容，表明Stream 1的业务流ID为{01:00:5e:01:01:01,2}，所需的TSN配置对应的配置值为1；此外， 在网桥节点1下方的SRP扩展报文中还表明虚拟局域网(Virtual Local Area Network，VLAN)ID为2。同理，网桥节点2左侧的表格表示Stream 2的Talker Advertise报文头的字段内容，表明Stream2的业务流ID为{01:00:5e:01:01:02,3}，所需的TSN配置对应的配置值为2；此外，在网桥节点2右侧的SRP扩展报文中还表明VLAN ID为3。
在SRP扩展报文传输过程中，为Stream 1建立路径网桥节点1->网桥节点3->网桥节点4，为Stream 2建立路径网桥节点2->网桥节点3->网桥节点5，各网桥节点建立的业务流标识和TSN配置的映射关系表以表格形式显示在网桥节点图标的附近。在网桥节点1、网桥节点3和网桥节点4中，各网桥节点分别提取Stream 1业务流标识{01:00:5e:01:01:01,2}和TSN配置值“1”写入映射关系表；在网桥节点2、网桥节点3和网桥节点5中，各网桥节点分别提取Stream 2业务流ID{01:00:5e:01:01:02,3}和TSN配置值“2”写入映射关系表。
在一种可实施方式中，通告信息可通过LLDP报文传输；LLDP报文中的内容字段携带业务流标识和TSN配置。
图6为本申请实施例提供的LLDP扩展报文(即，LLDP报文)的一种示意图。LLDP报文(LLDP Data Unit，LLDPDU)中的可扩展类型-长度-内容(Type-length-valu，TLV)，即Optional TLVs字段，可扩展用于携带通告信息，扩展的次级TLV(sub-TLV)的含义和格式按需指定。例如，在Optional TLVs中，携带一个TSN-profile的sub-TLV。如图6所示，Type字段表示TSN-profile的类型(配置值)，占7bits，由机构统一分配，取值范围为9～126；Length字段表示Value字段的长度，占9bits，字段值以Octet为单位；Value字段中包含两部分内容，分别为业务流标识和TSN-profile，其中，业务流标识又包括Dest MAC占6Octets、VLAN ID占2Octets；TSN-profile可占用2Octets，最多可表示216种TSN-profile，TSN-profile的配置值和含义不作限定。
在图6中，Value字段的前6个Octets表示Detst MAC，随后 的2Octets表示VLAN ID，最后2Octets表示TSN-profile。网桥节点接收到LLDP的协议扩展报文后，根据Optional TLVs中携带TSN配置的sub-TLV，可以提取Value字段中携带的DestMAC、VLAN ID和TSN-profile值，并将{DestMAC,VlanID}和TSN-profile映射关系写入映射关系表中。
在一种可实施方式中，也可以采用除SRP或LLDP以外的协议发送通告信息，本申请实施例对于具体采用的协议以及报文格式、业务流标识字段和TSN配置字段的内容不作限定。
根据本申请实施例提供的报文处理方法，源设备可以将业务流标识和对应的TSN配置通告至各网桥节点，供网桥节点建立映射关系表，在接收到TSN业务报文时通过查询映射关系表对TSN业务报文进行相应的处理，明确了网桥节点具备的TSN配置能力，提高报文处理的可靠性和效率。网桥节点根据通告信息，还可以实现TSN业务报文的资源预留和转发表项的建立，进一步提高报文处理的可靠性和效率。此外，通告信息可以通过不同协议的协议扩展报文传输，并通过不同的通告触发条件触发通告，提高了通告的灵活性。
本申请实施例还提供一种通告方法，可应用于源设备。源设备通过发送通告信息，为网桥节点建立映射关系表、明确网桥节点是否具备TSN业务报文的TSN配置的能力提供依据，在此基础上发送TSN业务报文，便于网桥节点根据映射关系表对TSN业务报文进行相应处理，提高了TSN业务报文处理的可靠性。
图7为本申请实施例提供的通告方法的一种流程图。如图7所示，该通报方法可包括步骤210和步骤220。需要说明的是，本申请实施例中源设备执行的操作与上述实施例中网桥节点执行的操作相对应，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式。
在步骤210中，发送通告信息，通告信息包括业务流标识和对应的TSN配置。
在步骤220中，发送TSN业务报文，TSN业务报文由网桥节点根据通告信息进行处理。
在一种可实施方式中，发送通告信息的通告触发条件可包括以下至少之一：接收到通告触发命令，发送首个TSN业务报文，或发送协议扩展报文。
在一种可实施方式中，通告信息可通过SRP的协议扩展报文传输；协议扩展报文包括业务流标识字段和TSN配置字段。
在一种可实施方式中，通告信息可通过LLDP报文传输；LLDP报文中的内容字段携带业务流标识和TSN配置。
根据本申请实施例提供的通告方法，源设备可以将业务流标识和对应的TSN配置通告至各网桥节点，供网桥节点建立映射关系表，在接收到TSN业务报文时通过查询映射关系表对TSN业务报文进行相应的处理，明确了网桥节点具备的TSN配置能力，提高报文处理的可靠性和效率。此外，通告信息可以通过不同协议的协议扩展报文传输，并通过不同的通告触发条件触发通告，提高了通告的灵活性。
本申请实施例还提供一种报文处理装置。图8为本申请实施例提供的报文处理装置的一种结构示意图。如图8所示，报文处理装置可包括：报文接收模块310、查询模块320和报文处理模块330。
报文接收模块310，可被配置为接收TSN业务报文。
查询模块320，可被配置为根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，映射关系表根据源设备的通告信息建立。
报文处理模块330，可被配置为根据查询结果处理TSN业务报文。
本申请实施例提供的报文处理装置，可在接收到TSN业务报文时，通过查询根据源设备的通告信息建立的映射关系表，确定网桥节点是否具备TSN业务报文的TSN配置的能力，从而对TSN业务报文进行相应处理，提高TSN业务报文处理的可靠性。
在一种可实施方式中，报文处理装置还可包括：通告信息获取模块，可被配置为在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，响应于通告触发条件，获取源设备的通告信息，通告信息包括业务流标识和对应的TSN配置；以及，映射关系建立模块，可被配置为在满足设定条件的情况下，从通告信息中提 取网桥节点支持的业务流标识和TSN配置，并写入本地的映射关系表中。
在一种可实施方式中，设定条件可包括：通告信息中的业务流标识和目的设备的响应报文的业务流标识匹配，且网桥节点的带宽资源大于或等于业务流标识对应的TSN业务所需带宽资源。
在一种可实施方式中，报文处理装置还可包括：预处理模块，可被配置为在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，在满足设定条件的情况下，预留用于处理TSN业务报文的带宽资源，并建立TSN业务报文的转发表项。
在一种可实施方式中，报文处理模块330，具体可被配置为：若报文头与网桥节点支持的业务流标识和TSN配置一致，则利用预留的带宽资源，根据转发表项将TSN业务报文转发至目的设备。
在一种可实施方式中，通告触发条件可包括以下至少之一：接收到通告触发命令，接收到源设备发出的首个TSN业务报文，或接收到源设备发出的协议扩展报文。
在一种可实施方式中，通告信息可通过SRP的协议扩展报文传输；协议扩展报文包括业务流标识字段和TSN配置字段。
在一种可实施方式中，通告信息可通过LLDP报文传输；LLDP报文中的内容字段携带业务流标识和TSN配置。
本申请实施例提供的报文处理装置与本申请实施例提供的报文处理方法属于同一发明构思，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式，并且本申请实施例提供的报文处理装置具备与本申请实施例提供的报文处理方法相同的有益效果。
本申请实施例还提供一种通告装置。图9为本申请实施例提供的通告装置的一种结构示意图。如图9所示，通告装置可包括通告模块410和报文发送模块420。
通告模块410，可被配置为发送通告信息，通告信息包括业务流标识和对应的TSN配置。
报文发送模块420，可被配置为发送TSN业务报文，TSN业务报文由网桥节点根据通告信息进行处理。
本申请实施例提供的通告装置，可通过发送通告信息，为网桥节点建立映射关系表、明确网桥节点是否具备TSN业务报文的TSN配置的能力提供依据，在此基础上发送TSN业务报文，便于网桥节点根据映射关系表对TSN业务报文进行相应处理，提高了TSN业务报文处理的可靠性。
在一种可实施方式中，发送通告信息的通告触发条件可包括以下至少之一：接收到通告触发命令，发送首个TSN业务报文，或发送协议扩展报文。
在一种可实施方式中，通告信息可通过SRP的协议扩展报文传输；协议扩展报文包括业务流标识字段和TSN配置字段。
在一种可实施方式中，通告信息可通过LLDP报文传输；LLDP报文中的内容字段携带业务流标识和TSN配置。
本申请实施例提供的通告装置与本申请实施例提供的通告方法属于同一发明构思，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式，并且本申请实施例提供的通告装置具备与本申请实施例提供的通告方法相同的有益效果。
本申请实施例还提供一种网桥节点。本申请实施例提供的报文处理方法可以由报文处理装置执行，该报文处理装置可以通过软件和/或硬件的方式实现，并集成在网桥节点中。网桥节点可为TSN节点设备。
图10为本申请实施例提供的网桥节点的一种硬件结构示意图。如图10所示，网桥节点可包括：处理器510和存储装置520。该网桥节点中的处理器510可以是一个或多个，图10中以一个处理器510为例。设备中的处理器510和存储装置520可以通过总线或其他方式连接，图10中以通过总线连接为例。
该网桥节点中的存储装置520作为一种计算机可读存储介质，可用于存储一个或多个程序，该一个或多个程序被一个或多个处理器510执行，使得该一个或多个处理器510实现本申请实施例提供的报文处理方法。
程序可以是软件程序、计算机可执行程序以及模块，如本申请 实施例中的报文处理方法对应的程序指令/模块(例如，附图8所示的报文处理装置中的模块，包括：报文接收模块310、查询模块320和报文处理模块330)。处理器510通过运行存储在存储装置520中的软件程序、指令以及模块，从而执行网桥节点的各种功能应用以及数据处理，即实现本申请实施例提供的报文处理方法。
存储装置520主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等(如上述可实施方式中的通告信息、映射关系表等)。此外，存储装置520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一种可实施方式中，存储装置520可进一步包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至网桥节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
并且，当上述网桥节点包括的一个或多个程序被一个或多个处理器510执行时，实现如下操作：接收TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，映射关系表根据源设备的通告信息建立；以及，根据对映射关系表的查询结果处理TSN业务报文。
本申请实施例提供的网桥节点与本申请实施例提供的报文处理方法属于同一发明构思，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式，并且本申请实施例提供的网桥节点具备与本申请实施例提供的报文处理方法相同的有益效果。
本申请实施例还提供一种源设备。通告方法可以由通告装置执行，该通告装置可以通过软件和/或硬件的方式实现，并集成在源设备中。源设备可为TSN节点设备。
图11为本申请实施例提供的源设备的一种硬件结构示意图。如图11所示，源设备可包括：处理器610和存储装置620。该源设备中的处理器610可以是一个或多个，图11中以一个处理器610为例。设备中的处理器610和存储装置620可以通过总线或其他方式连接， 图11中以通过总线连接为例。
该源设备中的存储装置620作为一种计算机可读存储介质，可用于存储一个或多个程序，该一个或多个程序被一个或多个处理器610执行，使得该一个或多个处理器610实现本申请实施例提供的通告方法。
程序可以是软件程序、计算机可执行程序以及模块，如本申请实施例中通告方法对应的程序指令/模块(例如，附图9所示的通告装置中的模块，包括：通告模块410和报文发送模块420)。处理器610通过运行存储在存储装置620中的软件程序、指令以及模块，从而执行源设备的各种功能应用以及数据处理，即实现本申请实施例提供的通告方法。
存储装置620主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等(如上述可实施方式中的通告信息、TSN业务报文等)。此外，存储装置620可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一种可实施方式中，存储装置620可进一步包括相对于处理器610远程设置的存储器，这些远程存储器可以通过网络连接至源设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
并且，当上述源设备包括的一个或多个程序被一个或者多个处理器610执行时，实现如下操作：发送通告信息，通告信息包括业务流标识和对应的TSN配置；以及，发送TSN业务报文。
本申请实施例提供的源设备与本申请实施例提供的通告方法属于同一发明构思，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式，并且本申请实施例提供的源设备具备与本申请实施例提供的通告方法相同的有益效果。
本申请实施例还提供一种报文处理系统。图12为本申请实施例提供的报文处理系统的一种结构示意图。如图12所示，该系统可包括：目的设备730、至少一个网桥节点720以及源设备710。源设备 710向各网桥节点720发送通告信息；源设备710发送的TSN业务报文经过至少一个网桥节点720根据通告信息进行处理后被转发至目的设备730。
根据本申请实施例提供的报文处理系统，源设备710发送的信息要抵达目的设备730，需要经过几个桥接过程，每个网桥节点720上都会有分布式时钟进行时间的同步计算，而队列用于处理数据的优先级、包括为了高动态数据的快速通道方式、抢占式机制。
在一种可实施方式中，源设备710可被配置为发送通告信息，通告信息包括业务流标识和对应的TSN配置；以及，发送TSN业务报文。
在一种可实施方式中，网桥节点720可被配置为接收TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，映射关系表根据源设备710的通告信息建立；以及，根据对映射关系表的查询结果处理TSN业务报文。
在一种可实施方式中，网桥节点720可被配置为在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，还响应于通告触发条件，获取源设备710的通告信息，通告信息包括业务流标识和对应的TSN配置；以及，在满足设定条件的情况下，从通告信息中提取网桥节点720支持的业务流标识和TSN配置，并写入本地的映射关系表中。
在一种可实施方式中，设定条件可包括：通告信息中的业务流标识和目的设备730的响应报文的业务流标识匹配，且网桥节点720的带宽资源大于或等于业务流标识对应的TSN业务所需带宽资源。
在一种可实施方式中，网桥节点720可被配置为在根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表之前，且在满足设定条件的情况下，预留用于处理TSN业务报文的带宽资源，并建立TSN业务报文的转发表项。
在一种可实施方式中，网桥节点720可被配置为执行以下操作以实现根据查询结果处理TSN业务报文，包括：响应于确定报文头与网桥节点720支持的业务流标识和TSN配置一致，利用预留的带宽资 源，根据转发表项将TSN业务报文转发至目的设备730。
在一种可实施方式中，通告触发条件可包括以下至少之一：接收到通告触发命令，接收到源设备710发出的首个TSN业务报文，或接收到源设备710发出的协议扩展报文。
在一种可实施方式中，通告信息可通过SRP的协议扩展报文传输；协议扩展报文包括业务流标识字段和TSN配置字段。
在一种可实施方式中，通告信息可通过LLDP报文传输；LLDP报文中的内容字段携带业务流标识和TSN配置。
本申请实施例提供的报文处理系统与本申请实施例提供的报文处理方法或通告方法属于同一发明构思，未在本申请实施例中详尽描述的技术细节可参见上述任意可实施方式，并且本申请实施例提供的报文处理系统具备与本申请实施例提供的报文处理方法或通告方法相同的有益效果。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行本申请实施例提供的报文处理方法或者通告方法。
报文处理方法可包括：接收TSN业务报文；根据TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，映射关系表根据源设备的通告信息建立；以及，根据对映射关系表的查询结果处理TSN业务报文。
通告方法可包括：发送通告信息，通告信息包括业务流标识和对应的TSN配置；以及，发送TSN业务报文。
通过以上关于实施方式的描述，所属领域的技术人员可以了解到，本申请可借助软件及通用硬件来实现，也可以通过硬件实现。基于这样的理解，本申请的技术方案可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、闪存(FLASH)、硬盘或光盘等，包括多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请任意可实施方式中所述的方法。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和系统(数码多功能光碟DVD或CD光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、可编程逻辑器件(FGPA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本申请的范围。因此，本申请的恰当范围将根据权利要求确定。

Claims (14)

  1. 一种报文处理方法，应用于网桥节点，包括：
    接收时间敏感网络TSN业务报文；
    根据所述TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，所述业务流标识和TSN配置的映射关系表根据源设备的通告信息建立；以及
    根据对所述业务流标识和TSN配置的映射关系表的查询结果处理所述TSN业务报文。
  2. 根据权利要求1所述的方法，在根据所述TSN业务报文的所述报文头查询所述业务流标识和TSN配置的映射关系表之前，还包括：
    响应于触发条件，获取所述源设备的所述通告信息，所述通告信息包括业务流标识和对应的TSN配置；以及
    在满足设定条件的情况下，从所述通告信息中提取所述网桥节点支持的所述业务流标识和所述TSN配置，并写入本地的映射关系表中。
  3. 根据权利要求2所述的方法，所述设定条件包括：
    所述通告信息中的所述业务流标识和目的设备的响应报文的业务流标识匹配，且所述网桥节点的带宽资源大于或等于所述业务流标识对应的TSN业务所需带宽资源。
  4. 根据权利要求3所述的方法，在根据所述TSN业务报文的所述报文头查询所述业务流标识和TSN配置的映射关系表之前，还包括：
    在满足设定条件的情况下，预留用于处理所述TSN业务报文的带宽资源，并建立所述TSN业务报文的转发表项。
  5. 根据权利要求4所述的方法，其中，根据所述查询结果处理所述TSN业务报文，包括：
    响应于确定所述报文头与所述网桥节点支持的所述业务流标识 和所述TSN配置一致，利用所述预留的带宽资源，根据所述转发表项将所述TSN业务报文转发至所述目的设备。
  6. 根据权利要求2所述的方法，其中，所述触发条件包括以下至少之一：
    接收到通告触发命令；
    接收到所述源设备发出的首个TSN业务报文；或
    接收到所述源设备发出的协议扩展报文。
  7. 根据权利要求1-6任一项所述的方法，其中，所述通告信息通过流预留协议SRP的协议扩展报文传输；且
    所述协议扩展报文包括业务流标识字段和TSN配置字段。
  8. 根据权利要求1-6任一项所述的方法，其中，所述通告信息通过链路层发现协议LLDP报文传输；且
    所述LLDP报文中的内容字段携带所述业务流标识和所述TSN配置。
  9. 一种通告方法，应用于源设备，包括：
    发送通告信息，所述通告信息包括业务流标识和对应的TSN配置；以及
    发送时间敏感网络TSN业务报文，所述TSN业务报文由网桥节点根据所述通告信息进行处理。
  10. 根据权利要求9所述的方法，其中，发送所述通告信息的触发条件包括以下至少之一：
    接收到通告触发命令；
    发送首个TSN业务报文；或
    发送协议扩展报文。
  11. 一种网桥节点，包括：
    一个或多个处理器；以及
    存储装置，被配置为存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-8中任一所述的报文处理方法。
  12. 一种源设备，包括：
    一个或多个处理器；以及
    存储装置，被配置为存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求9-10中任一所述的通告方法。
  13. 一种报文处理系统，包括：目的设备、至少一个网桥节点以及源设备；其中：
    所述源设备，被配置为向所述至少一个网桥节点发送通告信息，所述通告信息包括业务流标识和对应的TSN配置；
    所述至少一个网桥节点，被配置为接收时间敏感网络TSN业务报文；根据所述TSN业务报文的报文头查询业务流标识和TSN配置的映射关系表，所述业务流标识和TSN配置的映射关系表根据所述源设备的所述通告信息建立；以及，根据对所述业务流标识和TSN配置的映射关系表的查询结果处理所述TSN业务报文；以及
    目的设备，被配置为接收所述至少一个网桥节点处理后的所述TSN业务报文。
  14. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-8中任一所述的报文处理方法或如权利要求9-10中任一所述的通告方法。
PCT/CN2021/094572 2020-05-19 2021-05-19 报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统 WO2021233327A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2022570216A JP2023525891A (ja) 2020-05-19 2021-05-19 メッセージ処理方法及び装置、通告方法及び装置、ネットワークブリッジノード、ソースデバイス、記憶媒体及びメッセージ処理システム
US17/924,390 US20230145093A1 (en) 2020-05-19 2021-05-19 Packet processing method and device, advertisement method and device, bridge node, source apparatus, storage medium, and packet processing system
EP21808796.3A EP4142219A4 (en) 2020-05-19 2021-05-19 MESSAGE PROCESSING METHOD AND APPARATUS, ANNOUNCEMENT METHOD AND APPARATUS, NETWORK BRIDGE NODE, SOURCE DEVICE, STORAGE MEDIUM AND MESSAGE PROCESSING SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010425664.8 2020-05-19
CN202010425664.8A CN113691385A (zh) 2020-05-19 2020-05-19 报文处理、通告方法、装置、网桥节点、源设备及介质

Publications (1)

Publication Number Publication Date
WO2021233327A1 true WO2021233327A1 (zh) 2021-11-25

Family

ID=78576127

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094572 WO2021233327A1 (zh) 2020-05-19 2021-05-19 报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统

Country Status (5)

Country Link
US (1) US20230145093A1 (zh)
EP (1) EP4142219A4 (zh)
JP (1) JP2023525891A (zh)
CN (1) CN113691385A (zh)
WO (1) WO2021233327A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115514806A (zh) * 2022-11-16 2022-12-23 江苏曼荼罗软件股份有限公司 一种离散服务集群的感知发现方法及系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852644B (zh) * 2021-11-26 2022-03-01 之江实验室 一种确定性网络设备识别认证装置及方法
JP2024000591A (ja) * 2022-06-21 2024-01-09 オムロン株式会社 制御システム、中継装置および通信方法
CN115297072A (zh) * 2022-07-27 2022-11-04 苏州思萃工业互联网技术研究所有限公司 一种系统内部模块间调用的实现方法及系统
CN117278891B (zh) * 2023-11-21 2024-04-12 北京智芯微电子科技有限公司 数据传输系统、数据传输方法及芯片

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639470A (zh) * 2013-11-14 2015-05-20 中兴通讯股份有限公司 流标识封装方法及系统
US20190058668A1 (en) * 2016-02-24 2019-02-21 Harman International Industries, Incorporated Data streaming with layer 2 and layer 3 reservations
CN109639493A (zh) * 2018-12-20 2019-04-16 新华三技术有限公司 网络设备、状态控制装置及tsn配置方法
US20200137615A1 (en) * 2018-10-24 2020-04-30 Qualcomm Incorporated Quality of service mapping for time-sensitive network traffic in a wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639470A (zh) * 2013-11-14 2015-05-20 中兴通讯股份有限公司 流标识封装方法及系统
US20190058668A1 (en) * 2016-02-24 2019-02-21 Harman International Industries, Incorporated Data streaming with layer 2 and layer 3 reservations
US20200137615A1 (en) * 2018-10-24 2020-04-30 Qualcomm Incorporated Quality of service mapping for time-sensitive network traffic in a wireless communication system
CN109639493A (zh) * 2018-12-20 2019-04-16 新华三技术有限公司 网络设备、状态控制装置及tsn配置方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4142219A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115514806A (zh) * 2022-11-16 2022-12-23 江苏曼荼罗软件股份有限公司 一种离散服务集群的感知发现方法及系统
CN115514806B (zh) * 2022-11-16 2023-03-03 江苏曼荼罗软件股份有限公司 一种离散服务集群的感知发现方法及系统

Also Published As

Publication number Publication date
JP2023525891A (ja) 2023-06-19
CN113691385A (zh) 2021-11-23
US20230145093A1 (en) 2023-05-11
EP4142219A1 (en) 2023-03-01
EP4142219A4 (en) 2024-04-24

Similar Documents

Publication Publication Date Title
WO2021233327A1 (zh) 报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统
CN107204867B (zh) 一种信息传输方法、装置和系统
WO2017215401A1 (zh) 报文处理的方法及设备
CN110891026B (zh) 一种流量调度方法、设备及系统
JP5653912B2 (ja) マルチキャスト・グループ管理のための方法及び装置
JP5656137B2 (ja) ボーダ・ゲートウェイ・プロトコル・ルートの更新方法およびシステム
WO2021174958A1 (zh) 报文转发方法、设备、系统、网络设备和存储介质
WO2019134383A1 (zh) 控制网络拥塞的方法、接入设备和计算机可读存储介质
WO2019165900A1 (zh) 一种处理组播数据报文的方法及装置
US20230156523A1 (en) Message interaction method and apparatus, and device and storage medium
WO2020063338A1 (zh) 一种实现数据传输的方法、装置和系统
WO2022007828A1 (zh) 冗余路径的资源预留方法、网络设备和存储介质
WO2022021818A1 (zh) 数据报文的处理方法及装置、存储介质、电子装置
WO2023061061A1 (zh) 报文处理方法、线卡、设备及存储介质
WO2021073377A1 (zh) 一种组播流检测方法、设备及系统
WO2011015102A1 (zh) 关联通道能力协商方法和网络设备
WO2020010998A1 (zh) 一种收发消息的方法、装置和系统
WO2019174552A1 (zh) 组播路由处理方法、网络设备以及路由反射器
US20150249550A1 (en) Method and Apparatus for Sending Transparent Interconnection of Lots of Links Data Frame
WO2012146139A1 (zh) 一种报文的过滤方法和接入设备
WO2015180560A1 (zh) 一种对业务路由报文进行处理的方法和业务节点
WO2015032261A1 (zh) 路由更新方法和路由设备
US10193941B2 (en) Interworking between first protocol entity of stream reservation protocol and second protocol entity of routing protocol
CN115473812A (zh) 流量报文转发方法、客户端、控制器及存储介质
WO2012016471A1 (zh) 一种拓扑收敛方法和服务提供商边缘设备

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: 21808796

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022570216

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021808796

Country of ref document: EP

Effective date: 20221122

NENP Non-entry into the national phase

Ref country code: DE