MESSAGE PROCESSING METHOD AND APPARATUS, NOTIFICATION METHOD AND APPARATUS, NETWORK BRIDGE NODE, SOURCE DEVICE, STORAGE MEDIUM AND MESSAGE PROCESSING SYSTEM

Abstract

The present application relates to the field of network communication technologies, and provides a message processing method and device, a notification method and device, a network bridge node, a source device, a message processing system, and a computer-readable storage medium. The message processing method includes: receiving a time-sensitive networking TSN service message; querying a mapping table between a service flow identifier and a TSN profile, which is established based on notification information of the source device, based on a message header of the TSN service message; and processing the TSN service message based on a query result to the mapping table between the service flow identifier and the TSN profile.

Description

[Technical field]

[0001] The present application relates to the field of network communication technologies. [Background technology]

[0002] The Time Sensitive Networking (TSN) standard defines time-sensitive mechanisms for Ethernet data transmission to add determinism and reliability to standard Ethernet, ensuring that Ethernet can provide stable and consistent service levels for the transmission of key data. For TSN services, various policies and mechanisms for providing consistent and deterministic services are TSN-profiles. A standard may have multiple types of TSN-profile instances, and each network bridge node (i.e., TSN node) can support zero, one, or more types of TSN-profile capabilities. Summary of the Invention

[0003] An aspect of an embodiment of the present application provides a message processing method applied to a network bridge node, the method including the steps of receiving a TSN service message; and the service flow identifiers and TSN profiles supported by the network bridge nodes. based on a message header of the TSN service message; ,Ma and processing the TSN service message based on a result of the query to a mapping table.

[0004] An aspect of an embodiment of the present application further provides a notification method applied to a source device, the method including: Time-Sensitive Networking ( TSN ) transmitting notification information including the profile; and processing the notification information by the network bridge node. T sending an SN service message. fruit , Here, the notification information is used by the network bridge node to establish a mapping table that records the service flow identifiers and TSN profiles supported by the network bridge node, and the network bridge node processes the TSN service message by querying the mapping table according to the message header of the TSN service message.

[0005] One aspect of an embodiment of the present application further provides a network bridge node including one or more processors and a storage device configured to store one or more programs, the one or more programs, when executed by the one or more processors, causing the one or more processors to implement a message processing method according to an embodiment of the present application.

[0006] One aspect of an embodiment of the present application provides a source device that includes one or more processors and a memory device configured to store one or more programs, the one or more programs, when executed by the one or more processors, causing the one or more processors to implement a notification method according to an embodiment of the present application.

[0007] An aspect of an embodiment of the present application further provides a message processing system, the system including: a destination device, at least one network bridge node, and a source device, the source device being configured to send notification information, including a service flow identifier and a corresponding time-sensitive networking (TSN) profile, to the at least one network bridge node; and Each of is configured to receive TSN service messages and establishes a service group based on the advertisement information of the source device. Recording the service flow identifiers and TSN profiles supported by the network bridge node. The mapping table is configured to be consulted based on a message header of the TSN service message, and the TSN service message is processed based on a result of the consultation to the mapping table, and the destination device is configured to receive the TSN service message processed by the at least one network bridge node.

[0008] One aspect of the embodiment of the present application further provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a message processing method or a notification method according to the embodiment of the present application. [Brief description of the drawings]

[0009] [Figure 1] Figure 1 is a schematic diagram of a TSN application scenario. [Diagram 2] FIG. 2 is a flow chart of a message processing method according to an embodiment of the present application. [Diagram 3] FIG. 3 is another flowchart of a message processing method according to an embodiment of the present application. [Figure 4] FIG. 4 is a schematic diagram of a Stream Reservation Protocol (SRP) extension message according to an embodiment of the present application. [Diagram 5] FIG. 5 is a schematic diagram of an advertisement TSN profile according to an embodiment of the present application. [Figure 6] FIG. 6 is a schematic diagram of a Link Layer Discovery Protocol (LLDP) extension message according to an embodiment of the present application. [Figure 7] FIG. 7 is a flow chart of a notification method according to an embodiment of the present application. [Figure 8] FIG. 8 is a structural schematic diagram of a message processing apparatus according to an embodiment of the present application. [Figure 9] FIG. 9 is a structural schematic diagram of a notification device according to an embodiment of the present application. [Figure 10] FIG. 10 is a schematic diagram of the hardware structure of a network bridge node according to an embodiment of the present application. [Figure 11] FIG. 11 is a schematic diagram of the hardware structure of a source device according to an embodiment of the present application. [Figure 12] FIG. 12 is a structural schematic diagram of a message processing system according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The present application will be described below in combination with drawings and examples. It should be understood that the specific examples described herein are merely for the purpose of explaining the present application and do not limit the present application. In addition, the possible implementations and features in the possible implementations in the embodiments of the present application can be arbitrarily combined with each other as long as they are not inconsistent. In addition, for the convenience of explanation, only parts related to the present application are shown in the drawings, and not all structures are shown.

[0011] In a TSN service message processing system, there are usually multiple network bridge nodes (i.e., TSN nodes), and each TSN node can support zero, one, or multiple TSN-profile capabilities. When a TSN node receives a TSN service flow message, if the TSN node has the TSN-profile capabilities required for the TSN service flow, it can provide a service that matches the TSN service demand.

[0012] FIG. 1 is a schematic diagram of a TSN application scenario. As shown in FIG. 1, there are six TSN nodes in the TSN simulation domain, and the source device refers to a distribution node (Talker) in the TSN network, and the destination device refers to a listening node (Listener) in the TSN network. In FIG. 1, the presence or absence of a white triangle and a white circle for each TSN node icon indicates whether the TSN node supports the TSN-profile corresponding to the service flow of source device 1 (Talker 1) and the service flow of source device 2 (Talker 2), respectively. If it is present, it indicates that it is supported, and if it is absent, it indicates that it is not supported. Here, the destination nodes of the source device 1 service flow are destination device 1 (Listener 1) and destination device 3 (Listener 3), and the destination node of the source device 2 service flow is destination device 2 (Listener 2). Assume that a service path from source device 1 to destination device 1, i.e., source device 1 → TSN node 1 → TSN node 4 → TSN node 5 → TSN / DetNet edge node, has been established, and a service path from source device 1 to destination device 3, i.e., source device 1 → TSN node 1 → TSN node 2, has been established. When TSN node 1, TSN node 2, TSN node 4, TSN node 5, or TSN / DetNet receives a TSN service message from source device 1, it needs to identify the TSN-profile corresponding to the service message. If the TSN node (TSN node 1, TSN node 4, TSN node 5, or TSN / DetNet) supports the TSN-profile, it processes the TSN service message according to the corresponding policy. If the TSN node (TSN node 2) does not support the TSN-profile, it needs to process the TSN service message according to the existing forwarding flow.

[0013] Due to the lack of an effective standard protocol or solution that can regulate the collection, determination and propagation of TSN-profile capabilities by each TSN node, it is not clear whether each TSN node can provide a service that matches the demand of the TSN service flow. If a 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 processing process of the TSN service message is low.

[0014] An embodiment of the present application provides a message processing method applicable to a network bridge node, in which when a network bridge node receives a TSN service message, the network bridge node consults a mapping table established according to notification information of a source device to determine whether the network bridge node has TSN profile capability of the TSN service message, and performs corresponding processing on the TSN service message, thereby improving the reliability of TSN service message processing.

[0015] 2 is a flow chart of a message processing method according to an embodiment of the present application. As shown in FIG. 2, the method includes steps 110, 120 and 130.

[0016] In step 110, a TSN service message is received.

[0017] According to an embodiment of the present application, the TSN service message may be a message sent by a source device, and is processed by a network bridge node and then finally sent to a destination device. Note that, for a network bridge node, the received TSN service message may be sent from the source device and directly reach the network bridge node, or may be sent from the source device and reach the network bridge node via another network bridge node.

[0018] In step 120, a mapping table between service flow identifiers and TSN profiles, which is established based on the advertisement information of the source device, is consulted based on the message header of the TSN service message.

[0019] According to an embodiment of the present application, the information carried in the message header of the TSN service message may indicate which service flow the TSN service message belongs to, what TSN profile it requires, etc. In the network bridge node, a mapping table between service flow identifiers and TSN profiles is pre-established based on the notification information sent by the source device, so that upon receiving a TSN service message, the network bridge node can query the mapping table based on the message header of the TSN service message to determine whether it has a TSN profile for processing the TSN service message.

[0020] In step 130, the TSN service message is processed based on the results of the lookup in the mapping table.

[0021] According to an embodiment of the present application, a network bridge node determines whether it has a TSN profile for processing the TSN service message by consulting a mapping table, and if so, the network bridge node can provide a service that meets the needs of the TSN service flow; otherwise, the network bridge node cannot effectively process the TSN service message.

[0022] In one embodiment, before querying the mapping table of service flow identifiers and TSN profiles based on a message header of the TSN service message, the method may further include: obtaining notification information of the source device, including a service flow identifier and a corresponding TSN profile, in response to a notification trigger condition; and extracting the service flow identifiers and TSN profiles supported by the network bridge node from the notification information and writing them into the local mapping table if the setting condition is met.

[0023] According to an embodiment of the present application, when a source device triggers a notification, the source device can send notification information to a network bridge node by extending SRP, LLDP, etc., thereby notifying the network bridge node of the service flow identifier and the required TSN profile of the TSN service message. After the service flow identifier and the required TSN profile are notified to the network bridge node, the network bridge node can extract key information therefrom and establish a mapping table between the service flow identifier and the TSN profile, so that when a TSN service message is received, it can query according to the message header and perform corresponding processing.

[0024] According to an embodiment of the present application, a network bridge node needs to maintain the TSN profiles it supports, and also needs to establish a mapping table between service flow identifiers and TSN profiles based on the advertisement information.

[0025] Table 1 is a mapping table between service flow identifiers and TSN profiles. As shown in Table 1, each service flow identifier corresponds to one TSN profile, and each TSN profile can be represented by a different profile value. For example, for a service flow of {01:00:5e:01:01:01,2}, the corresponding TSN profile is "1", that is, the network bridge node needs to have a TSN profile for the video system in P802.1DG. When the network bridge node receives the notification information, it extracts the service flow identifier and the TSN profile from it and writes them into the mapping table as shown in Table 1.

[0026] [Table 1]

[0027] In one embodiment, the TSN profile may include, but is not limited to, the following types: 1) P802.1CM-2018, a TSN profile for Fronthaul TSN Networks; 2) IEC / IEEE 60802, a TSN profile for Industrial Automation; 3) P802.1DC, a TSN profile for Quality of Service (QoS) for Network Systems; 4) P802.1DF, a TSN profile for Service Provider Networks; 5) P802.1DG, a TSN profile for Automotive In-Vehicle Ethernet Communications; and / or 6) P802.1CMde, an extension of the Fronthaul profile to support new Fronthaul interfaces and synchronization standards.

[0028] When a different extension protocol message is used, the format, profile value, and meaning of the field carrying the TSN profile may be different, but the embodiments of the present application are not limited thereto.

[0029] In one embodiment, before querying the mapping table between the service flow identifier and the TSN profile based on the message header of the TSN service message, the method may further include reserving bandwidth resources for processing the TSN service message and establishing a forwarding table entry for the TSN service message if a setting condition is met.

[0030] According to an embodiment of the present application, if the setting conditions are met, the network bridge node can reserve bandwidth resources for the TSN service message and perform corresponding processing upon receiving the TSN service message by establishing a forwarding table entry.

[0031] In one embodiment, processing the TSN service message based on the query result may include forwarding the TSN service message to a destination device based on a forwarding table entry using reserved bandwidth resources if the message header matches a service flow identifier and a TSN profile supported by the network bridge node.

[0032] According to an embodiment of the present application, 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. When each network bridge node receives the TSN service message, it obtains a service flow identifier by analyzing the message header, and based on this, consults a mapping table to determine the TSN profile required for the service flow. If the network bridge node has a corresponding TSN profile, it can use the reserved bandwidth resources to perform processing and forward the message based on the forwarding table entry; otherwise, it cannot process the TSN service message.

[0033] 3 is another flowchart of a message processing method according to an embodiment of the present application. As shown in FIG. 3, the message processing method may include steps 101 to 106.

[0034] In step 101, in response to a notification trigger condition, notification information of a source device is obtained, including a service flow identifier and a corresponding TSN profile.

[0035] In one embodiment, the notification trigger condition may include at least one of receiving a notification trigger command, receiving a first TSN service message sent from the source device, or receiving a protocol extension message sent from the source device.

[0036] According to an embodiment of the present application, the notification trigger condition may include, but is not limited to, the following: 1) receiving a notification trigger command. The notification trigger command may be generated by any node in the TSN network, for example, a notification trigger command sent by a client connected to a node in the TSN network, and after the notification trigger command is received by the source device or the network bridge node, the source device is triggered to send notification information to each network bridge node, and each network bridge node receives the notification information and establishes a mapping table. 2) receiving the first TSN service message sent from the source device. That is, the source device can trigger the notification of the TSN profile through the TSN service message. For example, a network bridge node directly connected to the source device starts the notification process on its behalf when it receives the TSN service message of the first source device. 3) receiving a protocol extension message sent from the source device. That is, the source device can trigger the notification of the TSN profile through the protocol extension message. In this case, the source device is required to support the extension of the related protocol (for example, SRP or LLDP, etc.).

[0037] In step 102, if the setting condition is met, extract the service flow identifier and TSN profile supported by the network bridge node from the notification information and write them into a local mapping table.

[0038] In step 103, if the setting condition is met, reserve bandwidth resources for processing the TSN service message and establish a forwarding table entry for the TSN service message.

[0039] In one embodiment, the setting conditions include: a service flow identifier in the notification information matches a service flow identifier in a response message of the destination device, and the bandwidth resource of the network bridge node is greater than or equal to the bandwidth resource required for the TSN service corresponding to the service flow identifier.

[0040] According to an embodiment of the present application, taking the notification based on SRP as an example, the network bridge node matches the service flow identifier (Stream Id) field carrying the notification information in the broadcast message (i.e., Talker Advertise message) of the source device with the service flow identifier (Stream Id) field of the response message (i.e., Listener Ready message) of the destination device. If the matching is successful, the network bridge node can determine whether the bandwidth resource of the corresponding port queue of the network bridge node meets the demand of the service flow according to the value of the Data Frame Priority field in the Talker Advertise message. If yes, write the service flow identifier and the profile value of the TSN profile in the notification information into the mapping table, reserve the bandwidth resource for processing the TSN service message, and establish a forwarding table entry for the TSN service message. If not, the resource reservation is unsuccessful, and the forwarding table entry cannot be established.

[0041] In step 104, a TSN service message is received.

[0042] In step 105, a mapping table between a service flow identifier and a TSN profile is consulted based on the message header of the TSN service message.

[0043] In step 106, if the message header matches a service flow identifier and a TSN profile supported by the network bridge node, the TSN service message is forwarded to the destination device based on the forwarding table entry using the reserved bandwidth resources.

[0044] In one embodiment, the notification information may be transmitted via a protocol extension message of the SRP, and the protocol extension message may include a service flow identifier field and a TSN profile field.

[0045] FIG. 4 is a schematic diagram of an SRP extension message (i.e., a protocol extension message of SRP) according to an embodiment of the present application. The embodiment of the present application takes SRP as an example to describe a protocol extension message for carrying notification information. When SRP is used, the notification information is carried by an extended Talker Advertise message of SRP, and the format of the extended Talker Advertise message is as shown in FIG. 4, and the TSN-profile field occupies 2 Octets and can represent up to 216 types of TSN profiles. The meanings of different profile values ​​of the TSN-profile field may be, for example, TSN-profile=1 indicates Profile for Audio Systems of P802.1DG, TSN-profile=2 indicates Profile for Vedio Systems of P802.1DG, TSN-profile=3 indicates Profile for Control Systems of P802.1DG, TSN-profile=4 indicates Profile1 of P802.1DF, and TSN-profile=5 indicates Profile2 of P802.1DF.

[0046] The profile values ​​and meanings of the TSN-profile field given in the embodiments of the present application are merely illustrative, and the embodiments of the present application are not limited thereto.

[0047] 5 is a schematic diagram of an advertisement TSN profile according to an embodiment of the present application. In FIG. 5, if any network bridge node identifier has a hollow triangle, it indicates that the network bridge node supports the TSN profile required for the service flow (Stream 1), and if any network bridge node identifier has a hollow circle, it indicates that the network bridge node supports the TSN profile required for the service flow (Stream 2).

[0048] For network bridge node 1, the table above represents the field contents of the Talker Advertise message header for Stream 1, indicating that the service flow ID for Stream 1 is {01:00:5e:01:01:01, 2}, with a profile value corresponding to the required TSN profile being 1. The SRP extension message below for network bridge node 1 further indicates that the Virtual Local Area Network (VLAN) ID is 2. Similarly, the table on the left for network bridge node 2 represents the field contents of the Talker Advertise message header for Stream 2, indicating that the service flow ID for Stream 2 is {01:00:5e:01:01:02, 3}, with a profile value corresponding to the required TSN profile being 2. The SRP extension message below for network bridge node 2 further indicates that the VLAN ID is 3.

[0049] In the SRP extended message transmission process, a route from network bridge node 1 to network bridge node 3 to network bridge node 4 is established for Stream 1, and a route from network bridge node 2 to network bridge node 3 to network bridge node 5 is established for Stream 2. The mapping table between the service flow identifier and the TSN profile established by each network bridge node is displayed in table form near the network bridge node icon. In network bridge node 1, network bridge node 3, and network bridge node 4, each network bridge node extracts the Stream 1 service flow identifier {01:00:5e:01:01:01, 2} and the TSN profile value "1" and writes it into the mapping table, and in network bridge node 2, network bridge node 3, and network bridge node 5, each network bridge node extracts the Stream 2 service flow ID {01:00:5e:01:01:02, 3} and the TSN profile value "2" and writes it into the mapping table.

[0050] In one embodiment, the notification information may be transmitted via an LLDP message, where a content field in the LLDP message carries the service flow identifier and the TSN profile.

[0051] FIG. 6 is a schematic diagram of an LLDP extension message (i.e., LLDP message) according to an embodiment of the present application. The extensible Type-length-value (TLV), i.e., Optional TLVs field in the LLDP message (LLDP Data Unit, LLDPDU), can be extended to carry notification information, and the meaning and format of the extended sub-TLV (sub-TLV) are specified as necessary. For example, in the Optional TLVs, a sub-TLV of one TSN-profile is carried. As shown in FIG. 6, the Type field represents the type (profile value) of the TSN-profile, occupies 7 bits, is uniformly assigned by a mechanism, and has a value range of 9 to 126. The Length field represents the length of the Value field, occupies 9 bits, and the field value is in units of an octet. The Value field includes two parts: a service flow identifier and a TSN-profile, where the service flow identifier further includes a Dest MAC occupying 6 octets and a VLAN ID occupying 2 octets, and can represent up to 216 types of TSN-profiles, and the profile value and meaning of the TSN-profile are not limited.

[0052] In Figure 6, the first 6 octets of the Value field represent Detst MAC, the next 2 octets represent VLAN ID, and the last 2 octets represent TSN-profile. After receiving the LLDP protocol extension message, the network bridge node can extract the DestMAC, VLAN ID, and TSN-profile values ​​carried in the Value field based on the sub-TLV carrying the TSN profile in the Optional TLVs, and write the {DestMAC, VlanID} and TSN-profile mapping into the mapping table.

[0053] In one embodiment, a protocol other than SRP or LLDP may be used to transmit the notification information, and the embodiments of this application are not limited to the specific protocol and message format used, and the contents of the service flow identifier field and the TSN profile field.

[0054] According to the message processing method provided by the embodiment of the present application, the source device can notify each network bridge node of the service flow identifier and the corresponding TSN profile, so that the network bridge node establishes a mapping table, and performs corresponding processing on the TSN service message by consulting the mapping table when receiving the TSN service message, thereby identifying the TSN profile capabilities of the network bridge node, and improving the reliability and efficiency of message processing. The network bridge node can realize resource reservation and forwarding table entry establishment for the TSN service message based on the notification information, and can further improve the reliability and efficiency of message processing. In addition, the notification information can be transmitted through protocol extension messages of different protocols, and the notification can be triggered according to different notification trigger conditions, thereby improving the flexibility of the notification.

[0055] The embodiment of the present application further provides a notification method applicable to a source device, in which the source device sends notification information to provide a basis for a network bridge node to establish a mapping table and clarify whether the network bridge node has the capability of the TSN profile of the TSN service message, and then sends the TSN service message to facilitate the network bridge node to perform corresponding processing on the TSN service message based on the mapping table, thereby improving the reliability of the TSN service message processing.

[0056] 7 is a flowchart of a notification method according to an embodiment of the present 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 network bridge node in the above embodiment, and technical details not detailed in the embodiment of the present application may refer to any of the above embodiments.

[0057] In step 210, notification information is sent that includes the service flow identifier and the corresponding TSN profile.

[0058] In step 220, a TSN service message is sent which is processed by the network bridge node based on the advertisement information.

[0059] In one embodiment, the notification trigger condition for sending notification information may include at least one of receiving a notification trigger command, sending an initial TSN service message, or sending a protocol extension message.

[0060] In one embodiment, the notification information may be transmitted via a protocol extension message of the SRP, where the protocol extension message includes a service flow identifier field and a TSN profile field.

[0061] In one embodiment, the notification information may be transmitted via an LLDP message, where a content field in the LLDP message carries the service flow identifier and the TSN profile.

[0062] According to the notification method provided by the embodiment of the present application, the source device can notify each network bridge node of the service flow identifier and the corresponding TSN profile, so that the network bridge node establishes a mapping table, and performs corresponding processing on the TSN service message by consulting the mapping table when receiving the TSN service message, thereby identifying the TSN profile capabilities of the network bridge node, and improving the reliability and efficiency of message processing. In addition, the notification information can be transmitted through protocol extension messages of different protocols, and the notification can be triggered according to different notification trigger conditions, thereby improving the flexibility of the notification.

[0063] The embodiment of the present application further provides a message processing device. Figure 8 is a structural schematic diagram of the message processing device according to the embodiment of the present application. As shown in Figure 8, the message processing device may include a message receiving module 310, a query module 320 and a message processing module 330.

[0064] The message receiving module 310 may be configured to receive a TSN service message.

[0065] The query module 320 may be configured to query a mapping table between service flow identifiers and TSN profiles, which is established based on advertisement information of the source device, based on a message header of the TSN service message.

[0066] The message processing module 330 may be configured to process the TSN service message based on the query result.

[0067] When a message processing device according to an embodiment of the present application receives a TSN service message, it can determine whether the network bridge node has the TSN profile capability of the TSN service message by consulting a mapping table established based on the notification information of the source device, and perform corresponding processing on the TSN service message, thereby improving the reliability of TSN service message processing.

[0068] In one embodiment, the message processing device may further include: a notification information acquisition module configured to acquire notification information of a source device including a service flow identifier and a corresponding TSN profile in response to a notification trigger condition before querying a mapping table of a service flow identifier and a TSN profile based on a message header of the TSN service message; and a mapping establishment module configured to extract a service flow identifier and a TSN profile supported by the network bridge node from the notification information and write them into a local mapping table when the setting condition is met.

[0069] In one embodiment, the setting conditions may include that the service flow identifier in the notification information matches the service flow identifier in the response message of the destination device, and the bandwidth resource of the network bridge node is greater than or equal to the bandwidth resource required for the TSN service corresponding to the service flow identifier.

[0070] In one embodiment, the message processing device may further include a pre-processing module configured to reserve bandwidth resources for processing the TSN service message and establish a forwarding table entry for the TSN service message if a setting condition is met before querying the mapping table between the service flow identifier and the TSN profile based on the message header of the TSN service message.

[0071] In one embodiment, the message processing module 330 may be specifically configured to forward the TSN service message to a destination device based on a forwarding table entry using reserved bandwidth resources in response to determining that the message header matches a service flow identifier and a TSN profile supported by the network bridge node.

[0072] In one embodiment, the notification trigger condition may include at least one of receiving a notification trigger command, receiving a first TSN service message sent from the source device, or receiving a protocol extension message sent from the source device.

[0073] In one embodiment, the notification information may be transmitted via a protocol extension message of the SRP, where the protocol extension message includes a service flow identifier field and a TSN profile field.

[0074] In one embodiment, the notification information may be transmitted via an LLDP message, where a content field in the LLDP message carries the service flow identifier and the TSN profile.

[0075] The message processing device provided in the embodiments of the present application belongs to the same inventive idea as the message processing method provided in the embodiments of the present application, and for technical details not detailed in the embodiments of the present application, reference may be made to any of the above-mentioned embodiments, and the message processing device provided in the embodiments of the present application has the same beneficial effects as the message processing method provided in the embodiments of the present application.

[0076] The embodiment of the present application further provides a notification device. Figure 9 is a structural schematic diagram of the notification device according to the embodiment of the present application. As shown in Figure 9, the notification device may include a notification module 410 and a message sending module 420.

[0077] The notification module 410 can be configured to transmit notification information including the service flow identifier and the corresponding TSN profile.

[0078] The message sending module 420 can be configured to send a TSN service message that is processed by the network bridge node based on the notification information.

[0079] The notification device provided in the embodiments of the present application sends notification information to provide a basis for the network bridge node to establish a mapping table and clarify whether the network bridge node has the capability of the TSN profile of the TSN service message, and then sends the TSN service message to facilitate the network bridge node to perform corresponding processing on the TSN service message based on the mapping table, thereby improving the reliability of TSN service message processing.

[0080] In one embodiment, the notification trigger condition for sending notification information may include at least one of receiving a notification trigger command, sending an initial TSN service message, or sending a protocol extension message.

[0081] In one embodiment, the notification information may be transmitted via a protocol extension message of the SRP, where the protocol extension message includes a service flow identifier field and a TSN profile field.

[0082] In one embodiment, the notification information may be transmitted via an LLDP message, where a content field in the LLDP message carries the service flow identifier and the TSN profile.

[0083] The notification device provided in the embodiments of the present application belongs to the same inventive idea as the notification method provided in the embodiments of the present application, and for technical details not detailed in the embodiments of the present application, reference may be made to any of the above-mentioned embodiments, and the notification device provided in the embodiments of the present application has the same beneficial effects as the notification method provided in the embodiments of the present application.

[0084] The embodiment of the present application further provides a network bridge node. The message processing method provided by the embodiment of the present application may be performed by a message processing device, which is implemented in the form of software and / or hardware and integrated into the network bridge node. The network bridge node may be a TSN node device.

[0085] Fig. 10 is a schematic diagram of the hardware structure of a network bridge node according to an embodiment of the present application. As shown in Fig. 10, the network bridge node may include a processor 510 and a storage device 520. The processor 510 in the network bridge node may be one or more, and Fig. 10 takes one processor 510 as an example. The processor 510 and the storage device 520 in the device may be connected via a bus or in other ways, and Fig. 10 takes the case of being connected via a bus as an example.

[0086] The storage device 520 in the network bridge node can be used as a computer-readable storage medium to store one or more programs executed by the one or more processors 510, thereby causing the one or more processors 510 to realize the message processing method provided by the embodiments of the present application.

[0087] The programs may be software programs, computer executable programs, and modules, such as program commands / modules corresponding to the message processing method in the embodiments of the present application (for example, modules including the message receiving module 310, the inquiry module 320, and the message processing module 330 in the message processing device shown in FIG. 8). The processor 510 executes the software programs, commands, and modules stored in the storage device 520 to perform various functional applications and data processing of the network bridge node, that is, to realize the message processing method provided by the embodiments of the present application.

[0088] The storage device 520 mainly includes a storage program area and a storage data area, and the storage program area can store an operating system and an application required for at least one function, and the storage data area can store data created according to the usage status of the device (such as notification information and mapping tables in the above embodiment). The storage device 520 may also include a high-speed random access memory, and may also include a non-volatile memory such as at least one disk storage device, a flash memory device, or other non-volatile solid-state memory device. In one embodiment, the storage device 520 may further include a memory installed remotely with respect to the processor 510, and these remote memories may be connected to a network bridge node via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0089] In addition, when one or more programs included in the network bridge node are executed by one or more processors 510, the following operations are realized: receiving a TSN service message; querying a mapping table between a service flow identifier and a TSN profile, which is established based on notification information of the source device, based on a message header of the TSN service message; and processing the TSN service message based on a result of querying the mapping table.

[0090] The network bridge node provided in the embodiments of the present application belongs to the same inventive idea as the message processing method provided in the embodiments of the present application, and for technical details not detailed in the embodiments of the present application, reference may be made to any of the above-mentioned embodiments, and the network bridge node provided in the embodiments of the present application has the same beneficial effects as the message processing method provided in the embodiments of the present application.

[0091] An embodiment of the present application further provides a source device. The notification method may be implemented by a notification device, which may be implemented in the form of software and / or hardware and may be integrated into the source device. The source device may be a TSN node device.

[0092] Fig. 11 is a schematic diagram of the hardware structure of a source device according to an embodiment of the present application. As shown in Fig. 11, the source device may include a processor 610 and a storage device 620. The processor 610 in the source device may be one or more, and Fig. 11 takes one processor 610 as an example. The processor 610 and the storage device 620 in the device may be connected via a bus or in other ways, and Fig. 11 takes the case of being connected via a bus as an example.

[0093] The storage device 620 in the source device can be used as a computer-readable storage medium to store one or more programs executed by the one or more processors 610, thereby causing the one or more processors 610 to realize the notification method provided by the embodiments of the present application.

[0094] The program may be a software program, a computer executable program, and a module, for example, a program command / module corresponding to the notification method in the embodiment of the present application (for example, a module including the notification module 410 and the message sending module 420 in the notification device shown in FIG. 9). The processor 610 executes the software programs, commands, and modules stored in the storage device 620 to execute various functional applications and data processing of the source device, that is, to realize the notification method provided by the embodiment of the present application.

[0095] The storage device 620 mainly includes a storage program area and a storage data area, and the storage program area can store an operating system and an application required for at least one function, and the storage data area can store data created according to the usage status of the device (such as notification information and TSN service messages in the above embodiment). The storage device 620 may also include a high-speed random access memory, and may also include a non-volatile memory such as at least one disk storage device, a flash memory device, or other non-volatile solid-state memory device. In one embodiment, the storage device 620 may further include a memory installed remotely with respect to the processor 610, and these remote memories may be connected to the source device via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0096] In addition, when one or more programs included in the source device are executed by one or more processors 610, an operation of sending notification information including a service flow identifier and a corresponding TSN profile, and an operation of sending a TSN service message are realized.

[0097] The source device provided in the embodiments of the present application belongs to the same inventive idea as the notification method provided in the embodiments of the present application, and for technical details not detailed in the embodiments of the present application, reference may be made to any of the above-mentioned embodiments, and the source device provided in the embodiments of the present application has the same beneficial effects as the notification method provided in the embodiments of the present application.

[0098] An embodiment of the present application further provides a message processing system. Figure 12 is a structural schematic diagram of a message processing system according to an embodiment of the present application. As shown in Figure 12, the system may include a destination device 730, at least one network bridge node 720, and a source device 710. The source device 710 sends notification information to each network bridge node 720, and the TSN service message sent from the source device 710 is processed by the at least one network bridge node 720 according to the notification information, and then forwarded to the destination device 730.

[0099] According to the message processing system provided by an embodiment of the present application, information sent from a source device 710 needs to go through several bridge processes to reach a destination device 730, each network bridge node 720 has a distributed clock to perform synchronized calculation of time, a queue is used to handle data priority, and includes a fast channel mode and a preemption mechanism for highly dynamic data.

[0100] In one embodiment, the source device 710 may be configured to send notification information including a service flow identifier and a corresponding TSN profile and to send a TSN service message.

[0101] In one embodiment, the network bridge node 720 may be configured to receive a TSN service message, query a mapping table of service flow identifiers and TSN profiles established based on notification information of the source device 710 based on a message header of the TSN service message, and process the TSN service message based on a query result to the mapping table.

[0102] In one embodiment, the network bridge node 720 may be configured to obtain notification information of the source device 710 including the service flow identifier and the corresponding TSN profile in response to a notification trigger condition before querying a mapping table of service flow identifiers and TSN profiles based on a message header of the TSN service message, and if a set condition is met, extract from the notification information the service flow identifiers and TSN profiles supported by the network bridge node 720 and write them into the local mapping table.

[0103] In one embodiment, the setting conditions may include that the service flow identifier in the notification information matches the service flow identifier in the response message of the destination device 730, and the bandwidth resources of the network bridge node 720 are greater than or equal to the bandwidth resources required for the TSN service corresponding to the service flow identifier.

[0104] In one embodiment, the network bridge node 720 may be configured to reserve bandwidth resources for processing the TSN service message and establish a forwarding table entry for the TSN service message if a set condition is met before querying a mapping table between a service flow identifier and a TSN profile based on a message header of the TSN service message.

[0105] In one embodiment, the network bridge node 720 may be configured to process the TSN service message based on the query result, and in response to determining that the message header matches a service flow identifier and a TSN profile supported by the network bridge node 720, perform the operation of forwarding the TSN service message to the destination device 730 based on the forwarding table entry using the reserved bandwidth resources.

[0106] In one embodiment, the notification trigger condition may include at least one of receiving a notification trigger command, receiving an initial TSN service message sent from the source device 710, or receiving a protocol extension message sent from the source device 710.

[0107] In one embodiment, the notification information may be transmitted via a protocol extension message of the SRP, where the protocol extension message includes a service flow identifier field and a TSN profile field.

[0108] In one embodiment, the notification information may be transmitted via an LLDP message, where a content field in the LLDP message carries the service flow identifier and the TSN profile.

[0109] The message processing system provided in the embodiments of the present application belongs to the same inventive idea as the message processing method or notification method provided in the embodiments of the present application, and for technical details not detailed in the embodiments of the present application, reference may be made to any of the above-mentioned embodiments, and the message processing system provided in the embodiments of the present application has the same beneficial effects as the message processing method or notification method provided in the embodiments of the present application.

[0110] An embodiment of the present application further provides a storage medium containing computer-executable instructions for, when executed by a computer processor, performing a message processing method or a notification method provided by an embodiment of the present application.

[0111] The message processing method may include the steps of receiving a TSN service message, querying a mapping table between a service flow identifier and a TSN profile, the mapping table being established based on notification information of the source device, based on a message header of the TSN service message, and processing the TSN service message based on a query result to the mapping table.

[0112] The notification method may include the steps of sending notification information including a service flow identifier and a corresponding TSN profile, and sending a TSN service message.

[0113] From the description of the above embodiments, those skilled in the art will understand that the present application may be realized by software and general-purpose hardware, or may be realized by hardware. Based on this understanding, the technical solution of the present application may be embodied in the form of a software product, and the computer software product may be stored in a computer-readable storage medium such as a computer flexible disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (FLASH (registered trademark)), a hard disk, or an optical disk, and includes a plurality of commands for making a computer device (which may be a personal computer, a server, or a network device, etc.) execute the method according to any embodiment of the present application.

[0114] The above descriptions are only exemplary embodiments of the present application, and are not intended to limit the protection scope of the present application.

[0115] Any logic flow block diagrams in the drawings of this 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. Computer programs may be stored in memory. The memory may be of any type suitable for the local technology environment and may be implemented using any suitable data storage technology, including but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile disks DVD or CD disks). Computer-readable media may include non-transitory storage media. Data processors may be of any type suitable for the local technology environment, including but not limited to general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), programmable logic devices (FPGAs), and processors based on multi-core processor architectures.

[0116] By way of illustrative and non-limiting examples, detailed descriptions of exemplary embodiments of the present application have been provided above. When considered in combination with the drawings and claims, various modifications and adjustments to the above embodiments will be obvious to those skilled in the art, but do not depart from the scope of the present application. Thus, the appropriate scope of the present application is determined based on the claims.

Claims

1. A message processing method applied to a network bridge node, comprising: receiving a time sensitive networking (TSN) service message; Querying a mapping table based on a message header of the TSN service message, the mapping table being established based on advertisement information of a source device and a service flow identifier and a TSN profile supported by the network bridge node; and processing the TSN service message based on a result of the lookup in the mapping table. Message processing methods.

2. before querying the mapping table based on the message header of the TSN service message; obtaining the notification information of the source device, the notification information including a service flow identifier and a corresponding TSN profile, in response to a trigger condition; If the setting condition is satisfied, extracting the service flow identifier and the TSN profile supported by the network bridge node from the notification information and writing them into the mapping table. The method of claim 1.

3. The setting condition includes: the service flow identifier in the notification information matches with the service flow identifier in the response message of the destination device, and the bandwidth resource of the network bridge node is equal to or greater than the bandwidth resource required for the TSN service corresponding to the service flow identifier. The method of claim 2.

4. before querying the mapping table based on the message header of the TSN service message; If a set condition is met, reserving bandwidth resources for processing the TSN service message and establishing a forwarding table entry for the TSN service message. The method according to claim 3.

5. The step of processing the TSN service message based on the query result includes: and in response to determining that the message header matches the service flow identifier and the TSN profile supported by the network bridge node, forwarding the TSN service message to the destination device using the reserved bandwidth resources based on the forwarding table entry. The method according to claim 4.

6. The trigger condition is: receiving a notification trigger command; receiving a first TSN service message sent from the source device; or receiving a protocol extension message transmitted from the source device. The method of claim 2.

7. The notification information is transmitted via a protocol extension message of a stream reservation protocol (SRP), The protocol extension message includes a service flow identifier field and a TSN profile field. The method according to any one of claims 1 to 6.

8. The notification information is transmitted via a Link Layer Discovery Protocol (LLDP) message; A content field in the LLDP message carries the service flow identifier and the TSN profile. The method according to any one of claims 1 to 6.

9. A notification method applied to a source device, comprising: sending notification information including a service flow identifier and a corresponding time sensitive networking (TSN) profile; sending a TSN service message, the TSN service message being processed by a network bridge node based on the notification information; wherein the notification information is used by the network bridge node to establish a mapping table recording service flow identifiers and TSN profiles supported by the network bridge node; The network bridge node processes the TSN service message by consulting the mapping table according to a message header of the TSN service message. Method of notification.

10. The trigger condition for transmitting the notification information is: receiving a notification trigger command; Sending the first TSN service message; or transmitting a protocol extension message.

10. The method of claim 9.

11. one or more processors; a storage device configured to store one or more programs; The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the message processing method according to any one of claims 1 to 8. A network bridge node.

12. one or more processors; a storage device configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors are caused to realize the notification method according to any one of claims 9 and 10. Source device.

13. a destination device, at least one network bridge node, and a source device; The source device is configured to send notification information to the at least one network bridge node, the notification information including a service flow identifier and a corresponding time sensitive networking (TSN) profile; Each of the at least one network bridge node is configured to receive a TSN service message, query a mapping table, which is established based on the notification information of the source device and records a service flow identifier and a TSN profile supported by the network bridge node, based on a message header of the TSN service message, and process the TSN service message based on a query result to the mapping table; A destination device is configured to receive the TSN service message processed by the at least one network bridge node. Message processing system.

14. A computer program is stored which, when executed by a processor, realizes the message processing method according to any one of claims 1 to 8 or the notification method according to any one of claims 9 and 10. A computer-readable storage medium.

Images