Message processing, notification method, device, bridge node, source device and medium

Abstract

The present application provides a method, apparatus, bridge node, source device and medium for message processing and notification. The method includes: receiving a time-sensitive network (TSN) service message; querying a mapping relation table of a service flow identifier and TSN configuration according to a message header of the TSN service message, where the mapping relation table is established according to notification information of a source device; and processing the TSN service message according to a query result of the mapping relation table. The above method establishes and queries the mapping relation table according to the notification information, clarifies whether a bridge node has the ability of TSN configuration for the TSN service message, thereby improving the reliability of TSN service message processing.

Description

Technical Field

[0001] The present application relates to network communication, for example, to a method and apparatus for message processing and notification, a bridge node, a source device, and a medium. Background Art

[0002] The Time Sensitive Networking (TSN) standard defines a time-sensitive mechanism for Ethernet data transmission, adding determinism and reliability to standard Ethernet to ensure that Ethernet can provide a stable and consistent service level for the transmission of critical data. For TSN services, various policies and mechanisms used to provide consistent deterministic services are the TSN configuration (TSN-profile). In the standard, there can be multiple TSN-profile instances, and each bridge node (i.e., TSN node) may support the ability of 0, 1, or multiple TSN-profiles. Currently, there is a lack of an effective standard protocol or solution that can standardize the collection, judgment, and dissemination of the TSN-profile capabilities of each TSN node. Therefore, it is impossible to clarify whether each TSN node can provide consistent services for TSN traffic flows. If a TSN service message arrives at a TSN node that does not have the corresponding capabilities, it will also affect the processing efficiency. Therefore, the reliability of the processing process of TSN service messages is poor. Summary of the Invention

[0003] The present application provides a method and apparatus for message processing and notification, a bridge node, a source device, and a medium to improve the reliability of TSN service message processing.

[0004] An embodiment of the present application provides a message processing method applied to a bridge node, including:

[0005] Receiving a Time Sensitive Networking (TSN) service message;

[0006] Querying a mapping relationship table of a service flow identifier and a TSN configuration according to the message header of the TSN service message, where the mapping relationship table is established according to the notification information of a source device;

[0007] Processing the TSN service message according to the query result of the mapping relationship table.

[0008] An embodiment of the present application also provides a notification method applied to a source device, including:

[0009] Sending notification information, where the notification information includes a service flow identifier and a corresponding TSN configuration;

[0010] Sending a TSN service message, where the TSN service message is processed by a bridge node according to the notification information.

[0011] The embodiments of the present application also provide a bridge node, including:

[0012] One or more processors;

[0013] A storage device for storing one or more programs;

[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned message processing method.

[0015] The embodiments of the present application also provide a source device, including:

[0016] One or more processors;

[0017] A storage device for storing one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned announcement method.

[0019] The embodiments of the present application also provide a message processing system, including: a destination device, at least one of the above-mentioned bridge nodes, and the above-mentioned source device;

[0020] The source device sends announcement information to each of the bridge nodes;

[0021] The TSN service message sent by the source device is forwarded to the destination device after being processed by at least one of the bridge nodes according to the announcement information.

[0022] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the above-mentioned message processing method or announcement method.

[0023] A message processing and announcement method, device, bridge node, source device, and medium provided by the embodiments of the present application. The method includes: receiving a time-sensitive network (TSN) service message; querying a mapping relationship table of service flow identifiers and TSN configurations according to the message header of the TSN service message, where the mapping relationship table is established according to the announcement information of the source device; and processing the TSN service message according to the query result of the mapping relationship table. The above method establishes and queries the mapping relationship table according to the announcement information to clarify whether the bridge node has the ability to configure TSN for TSN service messages, thereby improving the reliability of TSN service message processing. Description of the Drawings

[0024] Figure 1 Is a schematic diagram of a time-sensitive network application scenario;

[0025] Figure 2Flowchart of the packet processing method provided for one embodiment;

[0026] Figure 3 Flowchart of the packet processing method provided for another embodiment;

[0027] Figure 4 Schematic diagram of the SRP extended packet provided for one embodiment;

[0028] Figure 5 Schematic diagram of a method for announcing TSN configuration provided for one embodiment;

[0029] Figure 6 Schematic diagram of the LLDP protocol extended packet provided for one embodiment;

[0030] Figure 7 Flowchart of a notification method provided for one embodiment;

[0031] Figure 8 Schematic diagram of the structure of a packet processing device provided for one embodiment;

[0032] Figure 9 Schematic diagram of the structure of a notification device provided for one embodiment;

[0033] Figure 10 Schematic diagram of the hardware structure of a bridge node provided for one embodiment;

[0034] Figure 11 Schematic diagram of the hardware structure of a source device provided for one embodiment;

[0035] Figure 12 Schematic diagram of the structure of a packet processing system provided for one embodiment. Detailed implementation manners

[0036] The present application will be described below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present application, rather than limiting the present application. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. Additionally, it should be noted that for the sake of description, only the parts related to the present application rather than all the structures are shown in the accompanying drawings.

[0037] In a TSN service packet processing system, there are usually multiple bridge nodes (i.e., TSN nodes), and each TSN node may support 0, 1, or multiple TSN-profile capabilities. When a TSN node receives a certain TSN service flow packet, if the TSN node has the TSN-profile capabilities required by the TSN service flow, it can provide services consistent with the TSN service requirements.

[0038] Figure 1 It is a schematic diagram of a time-sensitive network application scenario. As Figure 1 shown, there are 6 TSN nodes in the TSN simulation domain. The source device refers to the publishing node (Talker) in the TSN network; the destination device refers to the receiving node (Listener) in the TSN network. In each TSN node, the presence or absence of a hollow triangle or a hollow circle respectively indicates whether the TSN node supports the TSN-profile corresponding to the traffic flow of source device 1 (Talker 1) or source device 2 (Talker 2). The presence indicates support, and the absence indicates non-support. Among them, the destination nodes of the traffic flow of source device 1 are destination device 1 (Listener 1) and destination device 3 (Listener 3), and the destination nodes of the traffic flow of source device 2 are destination device 2 (Listener 2). Assume that a service path has been established from source device 1 to destination device 1: source device 1 -> TSN node 1 -> TSN node 4 -> TSN node 5 -> TSN / DetNet edge node, and a service path has been established from source device 1 to destination device 3: source device 1 -> TSN node 1 -> TSN node 2. 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, it processes the TSN service packet according to the corresponding policy. If the TSN node (TSN node 2) does not support the TSN-profile, the TSN service packet needs to be processed according to the original forwarding process.

[0039] Due to the lack of an effective standard protocol or solution that can standardize the collection, judgment, and dissemination of the TSN-profile capabilities of each TSN node, it is impossible to clarify whether each TSN node can provide consistent services for the TSN traffic flow. If a TSN service packet arrives at a TSN node that does not have the corresponding capabilities, it will also affect the processing efficiency. Therefore, the reliability of the processing process of TSN service packets is poor.

[0040] In an embodiment of the present application, a packet processing method is provided, which is applied to a bridge node. When the bridge node receives a TSN service packet, it determines whether the bridge node has the TSN configuration capabilities of the TSN service packet by querying the mapping relationship table established according to the advertisement information of the source device, so as to perform corresponding processing on the TSN service packet and improve the reliability of the TSN service packet processing.

[0041] Figure 2 It is a flowchart of the packet processing method provided in an embodiment. As Figure 2As shown in the figure, the method provided in this embodiment includes steps 110, 120, and 130.

[0042] In step 110, a time-sensitive network (TSN) service message is received.

[0043] In this embodiment, the TSN service message is a message sent by a source device, which is finally transmitted to a destination device after being processed by a bridge node. It should be noted that for a bridge node, the TSN service message it receives may be sent by the source device and directly reach this bridge node, or may be sent by the source device and reach this bridge node after being transmitted through other bridge nodes.

[0044] In step 120, a mapping relationship table of service flow identifiers and TSN configurations is queried according to the header of the TSN service message, and the mapping relationship table is established according to the advertisement information of the source device.

[0045] In this embodiment, the information carried in the header of the TSN service message can indicate which service flow the TSN service message belongs to, what kind of TSN configuration is required, etc. In the bridge node, a mapping relationship table of service flow identifiers and TSN configurations is established in advance according to the advertisement information sent by the source device. Therefore, when receiving a TSN service message, the bridge node can query the mapping relationship table according to the header of the TSN service message, so as to determine whether the bridge node has the TSN configuration for processing this TSN service message.

[0046] In step 130, the TSN service message is processed according to the query result of the mapping relationship table.

[0047] In this embodiment, the bridge node determines whether it has the TSN configuration for processing this TSN service message by querying the mapping relationship table. If so, it can provide services consistent with the requirements of this TSN service flow. Otherwise, it cannot effectively process this TSN service message.

[0048] In one embodiment, before querying the mapping relationship table of service flow identifiers and TSN configurations according to the header of the TSN service message, it further includes: in response to an advertisement trigger condition, obtaining the advertisement information of the source device, where the advertisement information includes service flow identifiers and corresponding TSN configurations; and under the condition of meeting the set conditions, extracting the service flow identifiers and TSN configurations supported by the bridge node from the advertisement information and writing them into the local mapping relationship table.

[0049] In this embodiment, when triggered to issue a notice, the source device can send notice information to the bridge node through protocols such as the Stream Reservation Protocol (SRP) and the Link Layer Discovery Protocol (LLDP), so as to notify the bridge node of the traffic flow identifier of the TSN service packet and the required TSN configuration. When the traffic flow identifier and the required TSN configuration are notified to the bridge node, the bridge node can extract key information from them and establish a mapping relationship table between the traffic flow identifier and the TSN configuration, so that when receiving a TSN service packet, it can query according to the packet header and perform corresponding processing.

[0050] In this embodiment, the bridge node needs to maintain the TSN configurations it supports, and also needs to establish a mapping relationship table between the traffic flow identifier and the TSN configuration according to the notice information.

[0051] Table 1 is the mapping relationship table between the traffic flow identifier and the TSN configuration. As shown in Table 1, each traffic flow identifier corresponds to a TSN configuration, and each TSN configuration can be represented by different configuration values. For example, for the traffic flow of {01:00:5e:01:01:01,2}, its corresponding TSN configuration is "1", that is, the bridge node needs to have the TSN configuration for the video system in P802.1DG. When the bridge node receives the notice information, it extracts the traffic flow identifier and the TSN configuration from it and writes them into the mapping relationship table as shown in Table 1.

[0052] Table 1 Mapping Relationship Table between Traffic Flow Identifier and TSN Configuration

[0053]

[0054] In one embodiment, the TSN configuration includes but is not limited to the following categories:

[0055] 1) P802.1CM-2018, the TSN configuration of the fronthaul TSN network;

[0056] 2) IEC / IEEE 60802, the TSN configuration for industrial automation;

[0057] 3) P802.1DC, the TSN configuration for Quality of Service (QoS) of network systems;

[0058] 4) P802.1DF, the TSN configuration for service provider networks;

[0059] 5) P802.1DG, TSN configuration for Automotive In-Vehicle Ethernet Communications;

[0060] 6) P802.1CMde, enhanced TSN configuration for a fronthaul configuration file that supports new fronthaul interfaces and synchronization standards.

[0061] In the case of using different extended protocol messages, the formats, configuration values, meanings, etc. of the fields used to carry TSN configurations are different, and this embodiment does not limit this.

[0062] In one embodiment, before querying the mapping relationship table of the service flow identifier and the TSN configuration according to the header of the TSN service message, it further includes: under the condition of meeting the set conditions, reserving bandwidth resources for processing the TSN service message and establishing a forwarding entry of the TSN service message.

[0063] In this embodiment, under the condition of meeting the set conditions, the bridge node can reserve bandwidth resources for the TSN service message and establish a forwarding entry, so that when receiving the TSN service message, corresponding processing can be performed.

[0064] In one embodiment, processing the TSN service message according to the query result includes: if the header is consistent with the service flow identifier and the TSN configuration supported by the bridge node, using the reserved bandwidth resources to forward the TSN service message to the destination device according to the forwarding entry.

[0065] In this embodiment, after successfully reserving bandwidth resources and establishing a forwarding path, the source device sends a TSN service message. The TSN service message is transmitted along a certain service path. When each bridge node receives the TSN service message, it obtains the service flow identifier by parsing the header, queries the mapping relationship table accordingly to determine the TSN configuration required by the service flow. If the bridge node has the corresponding TSN configuration, it can use the reserved bandwidth resources for processing and forward the message according to the forwarding entry; otherwise, it cannot process the TSN service message.

[0066] Figure 3 A flowchart of a message processing method provided for another embodiment. As Figure 3 shown, the message processing method of this embodiment includes steps 101-106.

[0067] In step 101, in response to the announcement trigger condition, obtain the announcement information of the source device, where the announcement information includes the service flow identifier and the corresponding TSN configuration.

[0068] In one embodiment, the announcement trigger condition includes at least one of the following: receiving an announcement trigger command; receiving the first TSN service packet sent by the source device; receiving a protocol extension packet sent by the source device.

[0069] In this embodiment, the announcement trigger condition includes but is not limited to the following:

[0070] 1) Receiving an announcement trigger command, where the announcement trigger command can be generated by any node in the TSN network. For example, it can be an announcement trigger command sent by a client connected to a certain node in the TSN network. After the source device or the bridge node receives the announcement trigger command, it triggers the source device to send announcement information to each bridge node, and each bridge node receives the announcement information and establishes a mapping relationship table;

[0071] 2) Receiving the first TSN service packet sent by the source device, that is, the source device can trigger the announcement of TSN configuration through the TSN service packet. For example, when the bridge node directly connected to the source device receives the first TSN service packet of the source device, it starts the announcement process as an agent;

[0072] 3) Receiving a protocol extension packet sent by the source device, that is, the source device can trigger the announcement of TSN configuration through the protocol extension packet. In this case, it is required that the source device supports the extension of relevant protocols (such as SRP or LLDP, etc.).

[0073] In step 102, when the set conditions are met, extract the service flow identifier and TSN configuration supported by the bridge node from the announcement information and write them into the local mapping relationship table.

[0074] In step 103, when the set conditions are met, reserve bandwidth resources for processing TSN service packets and establish a forwarding entry for TSN service packets.

[0075] In one embodiment, the set conditions include: the service flow identifier in the announcement information matches the service flow identifier of the response packet of the destination device, and the bandwidth resource of the bridge node is greater than or equal to the bandwidth resource required for the TSN service corresponding to the service flow identifier.

[0076] In this embodiment, taking the advertisement based on SRP as an example, the bridge node matches the service flow identifier (Stream Id) field carrying the advertisement information in the broadcast message (i.e., TalkerAdvertise 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 match is successful, it can be determined whether the bandwidth resources on the port queue corresponding to the bridge node meet the requirements of this service flow according to the value of the Data Frame Priority field in the Talker Advertise message. If they meet the requirements, the service flow identifier in the advertisement information and the configuration value of the TSN configuration are written into the mapping relationship table, and the bandwidth resources for processing TSN service messages are reserved and the forwarding entry for TSN service messages is established. If they do not meet the requirements, the resource reservation fails and the forwarding entry cannot be established.

[0077] In step 104, receive the TSN service message.

[0078] In step 105, query the mapping relationship table of the service flow identifier and the TSN configuration according to the message header of the TSN service message.

[0079] In step 106, when the message header is consistent with the service flow identifier and the TSN configuration supported by the bridge node, use the reserved bandwidth resources to forward the TSN service message to the destination device according to the forwarding entry.

[0080] In one embodiment, the advertisement information is transmitted through the protocol extension message of SRP; the protocol extension message includes a service flow identifier field and a TSN configuration field.

[0081] Figure 4 A schematic diagram of the SRP extension message provided for an embodiment. In this embodiment, SRP is taken as an example to illustrate the protocol extension message for carrying advertisement information. In the case of adopting SRP, the advertisement information is carried by extending the TalkerAdvertise message of SRP, and the format of the extended Talker Advertise message is as Figure 4 shown, where the TSN-profile field occupies 2 Octets and can represent up to 216 TSN configurations at most. The meanings of different configuration values of the TSN-profile field are, for example:

[0082] TSN-profile = 1 indicates the Profile for Audio Systems of P802.1DG;

[0083] TSN-profile = 2 indicates the Profile for Vedio Systems of P802.1DG;

[0084] TSN-profile = 3 indicates the Profile for Control Systems of P802.1DG;

[0085] TSN-profile = 4 indicates Profile1 of P802.1DF;

[0086] TSN-profile = 5 indicates Profile2 of P802.1DF, etc.

[0087] The configuration values and meanings of the TSN-profile fields listed in this embodiment are only for illustrative purposes, and this embodiment does not limit them.

[0088] Figure 5 It is a schematic diagram of notifying TSN configuration provided for an embodiment. Figure 5 In it, for each bridge node, a hollow triangle indicates the TSN configuration required for the bridge node to support traffic flow (Stream 1), and a hollow circle indicates the TSN configuration required for the bridge node to support traffic flow (Stream 2).

[0089] For bridge node 1, the table above it represents the field content of the Talker Advertise header of Stream 1, indicating that the traffic flow ID of Stream 1 is {01:00:5e:01:01:01,2}, and the corresponding configuration value of the required TSN configuration is 1. In addition, the SRP extension message also indicates that the Virtual Local Area Network (VLAN) ID is 2; similarly, the table on the left of bridge node 2 represents the field content of the Talker Advertise header of Stream 2, indicating that the traffic flow ID of Stream 2 is {01:00:5e:01:01:02,3}, and the corresponding configuration value of the required TSN configuration is 2. In addition, the SRP extension message also indicates that the VLAN ID is 3.

[0090] During the transmission of the SRP extended message, a path bridge node 1 -> bridge node 3 -> bridge node 4 is established for Stream 1, and a path bridge node 2 -> bridge node 3 -> bridge node 5 is established for Stream 2. The mapping relationship table between the service flow identifier established by each bridge node and the TSN configuration is displayed in tabular form beside the bridge node. Among them, in bridge node 1, bridge node 3, and bridge node 4, each bridge node extracts the service flow identifier {01:00:5e:01:01:01,2} of Stream 1 and the TSN configuration value "1" and writes them into the mapping relationship table. In bridge node 2, bridge node 3, and bridge node 5, each bridge node extracts the service flow ID {01:00:5e:01:01:02,3} of Stream 2 and the TSN configuration value "2" and writes them into the mapping relationship table.

[0091] In one embodiment, the advertisement information is transmitted through an LLDP message; the content field in the LLDP message carries the service flow identifier and the TSN configuration.

[0092] Figure 6 It is a schematic diagram of the LLDP protocol extended message provided for an embodiment. The extensible type-length-value (TLV) in the LLDP protocol message (LLDP DataUnit, LLDPDU), that is, the Optional TLVs field can be extended to carry the advertisement information, and the meaning and format of the extended secondary TLV (sub-TLV) are specified as needed. For example, in the Optional TLVs, a sub-TLV carrying a TSN-profile is included, as Figure 6 shown,

[0093] The Type field represents the type (configuration value) of the TSN-profile, occupying 7 bits, uniformly assigned by the organization, and the value range is 9 to 126;

[0094] The Length field represents the length of the Value field, occupying 9 bits, and the field value is in units of Octet;

[0095] The Value field contains two parts of content, namely the service flow identifier and the TSN-profile. Among them, the service flow identifier includes a Dest MAC occupying 6 Octets and a Vlan ID occupying 2 Octets; the TSN-profile can occupy 2 Octets and can represent up to 216 types of TSN-profiles at most, and the configuration value and meaning of the TSN-profile are not limited.

[0096] In Figure 6Among them, the first 6 Octets of the Value field represent the Dest MAC, the subsequent 2 Octets represent the Vlan ID, and the last 2 Octets represent the TSN-profile. After receiving the protocol extension message of LLDP, the bridge node can extract the Dest MAC, Vlan ID, and TSN-profile values carried in the Value field according to the sub-TLV carrying the TSN configuration in the Optional TLVs, and write the mapping relationship between {Dest MAC, Vlan ID} and the TSN-profile into the mapping relationship table.

[0097] In some embodiments, it is also possible to send the notification information using a protocol other than SRP or LLDP. This embodiment does not limit the specific protocol used, as well as the content of the message format, service flow identification field, and TSN configuration field.

[0098] In the message processing method of this embodiment, the source device can notify the service flow identification and the corresponding TSN configuration to each bridge node for the bridge node to establish a mapping relationship table, and perform corresponding processing on the TSN service message by querying the mapping relationship table when receiving the TSN service message, which clarifies the TSN configuration capabilities of the bridge node and improves the reliability and efficiency of message processing; according to the notification information, the bridge node can also implement resource reservation for the TSN service message and the establishment of forwarding table entries, further improving the reliability and efficiency of message processing; in addition, the notification information can be transmitted through protocol extension messages of different protocols and triggered by different notification trigger conditions, improving the flexibility of the notification.

[0099] In the embodiment of the present application, a notification method applied to the source device is also provided. The source device provides a basis for the bridge node to establish a mapping relationship table and clarify whether the bridge node has the TSN configuration ability of the TSN service message by sending the notification information, and on this basis, sends the TSN service message, facilitating the bridge node to perform corresponding processing on the TSN service message according to the mapping relationship table, and improving the reliability of the TSN service message processing.

[0100] Figure 7 It is a flowchart of a notification method provided for an embodiment, as Figure 7 shown, this notification method includes step 210 and step 220. It should be noted that the operations performed by the source device in this embodiment correspond to the operations performed by the bridge node in the above embodiment. For technical details not described in detail in this embodiment, reference can be made to any of the above embodiments.

[0101] In step 210, send the notification information, where the notification information includes the service flow identification and the corresponding TSN configuration.

[0102] In step 220, a TSN service packet is sent, and the TSN service packet is processed by a bridge node according to the announcement information.

[0103] In one embodiment, the announcement trigger conditions for sending the announcement information include at least one of the following: receiving an announcement trigger command; sending the first TSN service packet; sending a protocol extension packet.

[0104] In one embodiment, the announcement information is transmitted through a protocol extension packet of SRP; the protocol extension packet includes a service flow identification field and a TSN configuration field.

[0105] In one embodiment, the announcement information is transmitted through an LLDP packet; the content field in the LLDP packet carries a service flow identification and a TSN configuration.

[0106] In the method of this embodiment, the source device can announce the service flow identification and the corresponding TSN configuration to each bridge node for the bridge node to establish a mapping relation table, and when receiving a TSN service packet, query the mapping relation table to perform corresponding processing on the TSN service packet, which clarifies the TSN configuration capabilities of the bridge node and improves the reliability and efficiency of packet processing; in addition, the announcement information can be transmitted through protocol extension packets of different protocols and triggered by different announcement trigger conditions, which improves the flexibility of the announcement.

[0107] An embodiment of the present application further provides a packet processing device. Figure 8 The structural schematic diagram of a packet processing device provided for one embodiment. As Figure 8 shown, the packet processing device includes: a packet receiving module 310, a query module 320, and a packet processing module 330.

[0108] The packet receiving module 310 is configured to receive a TSN service packet;

[0109] The query module 320 is configured to query a mapping relation table of a service flow identification and a TSN configuration according to the packet header of the TSN service packet, and the mapping relation table is established according to the announcement information of the source device;

[0110] The packet processing module 330 is configured to process the TSN service packet according to the query result.

[0111] In the packet processing device of this embodiment, when receiving a TSN service packet, by querying the mapping relation table established according to the announcement information of the source device, it is determined whether the bridge node has the TSN configuration capabilities for the TSN service packet, so as to perform corresponding processing on the TSN service packet and improve the reliability of TSN service packet processing.

[0112] In one embodiment, it further includes:

[0113] The announcement information acquisition module is configured to obtain the announcement information of the source device in response to an announcement trigger condition before querying the mapping relationship table of the service flow identifier and the TSN configuration according to the header of the TSN service message. The announcement information includes the service flow identifier and the corresponding TSN configuration.

[0114] The mapping relationship establishment module is configured to extract the service flow identifier and the TSN configuration supported by the bridge node from the announcement information and write them into the local mapping relationship table when the set conditions are met.

[0115] In one embodiment, the set conditions include:

[0116] The service flow identifier in the announcement 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 bandwidth resource required for the TSN service corresponding to the service flow identifier.

[0117] In one embodiment, it further includes:

[0118] The preprocessing module is configured to reserve the bandwidth resource for processing the TSN service message and establish the forwarding entry of the TSN service message when the set conditions are met before querying the mapping relationship table of the service flow identifier and the TSN configuration according to the header of the TSN service message.

[0119] In one embodiment, the message processing module 330 is specifically configured to:

[0120] If the message header is consistent with the service flow identifier and the TSN configuration supported by the bridge node, forward the TSN service message to the destination device according to the forwarding entry by using the reserved bandwidth resource.

[0121] In one embodiment, the announcement trigger condition includes at least one of the following:

[0122] Receiving an announcement trigger command;

[0123] Receiving the first TSN service message sent by the source device;

[0124] Receiving the protocol extension message sent by the source device.

[0125] In one embodiment, the announcement information is transmitted through the protocol extension message of SRP;

[0126] The protocol extension message includes a service flow identifier field and a TSN configuration field.

[0127] In one embodiment, the announcement information is transmitted through the LLDP message;

[0128] The content field in the LLDP packet carries the service flow identifier and the TSN configuration.

[0129] The packet processing device proposed in this embodiment and the packet processing method proposed in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the packet processing method.

[0130] The embodiment of the present application further provides a notification device. Figure 9 It is a schematic structural diagram of a notification device provided in an embodiment. As Figure 9 shown, the notification device includes a notification module 410 and a packet sending module 420.

[0131] The notification module 410 is configured to send notification information, and the notification information includes a service flow identifier and a corresponding TSN configuration;

[0132] The packet sending module 420 is configured to send TSN service packets, and the TSN service packets are processed by the bridge node according to the notification information.

[0133] The notification device of this embodiment provides a basis for the bridge node to establish a mapping relationship table and clarify whether the bridge node has the ability to configure the TSN of the TSN service packet by sending notification information. On this basis, the TSN service packet is sent, which facilitates the bridge node to perform corresponding processing on the TSN service packet according to the mapping relationship table, and improves the reliability of the TSN service packet processing. In one embodiment, the notification trigger conditions for sending the notification information include at least one of the following:

[0134] Receiving a notification trigger command;

[0135] Sending the first TSN service packet;

[0136] Sending a protocol extension packet.

[0137] In one embodiment, the notification information is transmitted through the protocol extension packet of SRP; the protocol extension packet includes a service flow identifier field and a TSN configuration field.

[0138] In one embodiment, the notification information is transmitted through the LLDP packet; the content field in the LLDP packet carries the service flow identifier and the TSN configuration.

[0139] The notification device proposed in this embodiment and the notification method proposed in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the notification method.

[0140] The embodiment of the present application further provides a bridge node. The message processing method can be executed by a message processing device, which can be implemented in a software and / or hardware manner and integrated in the bridge node. The bridge node is a TSN node device.

[0141] Figure 10 FIG. is a schematic hardware structure diagram of a bridge node provided in an embodiment. As Figure 10 shown, a bridge node provided in this embodiment includes a processor 510 and a storage device 520. The processor in the bridge node can be one or more. Figure 10 Taking one processor 510 as an example, the processor 510 and the storage device 520 in the device can be connected through a bus or other means. Figure 10 Taking the connection through a bus as an example.

[0142] The one or more programs are executed by the one or more processors 510, so that the one or more processors implement the message processing method described in any of the above embodiments.

[0143] The storage device 520 in the bridge node, as a computer-readable storage medium, can be used to store one or more programs. The programs can be software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the message processing method in the embodiment of the present invention (for example, the modules in the message processing device shown in the appendix Figure 8 including: a message receiving module 310, a query module 320, and a 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 in the above method embodiment.

[0144] The storage device 520 mainly includes a storage program area and a storage data area. Among them, the storage program area can store an operating system and application programs required for at least one function; the storage data area can store data created according to the use of the device (such as the notification information, mapping relationship table, etc. in the above embodiment). In addition, the storage device 520 can include a high-speed random access memory, and can 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. In some instances, the storage device 520 can further include a memory remotely set relative to the processor 510, and these remote memories can be connected to the bridge node through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0145] Moreover, when one or more programs included in the above bridge node are executed by the one or more processors 510, the following operations are implemented: receiving time-sensitive network (TSN) service packets; querying a mapping relationship table of service flow identifiers and TSN configurations according to the packet header of the TSN service packet, where the mapping relationship table is established according to the advertisement information of the source device; and processing the TSN service packet according to the query result of the mapping relationship table.

[0146] The bridge node proposed in this embodiment and the packet processing method proposed in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to in any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the packet processing method.

[0147] An embodiment of the present application further provides a source device. The advertisement method can be executed by an advertisement device, which can be implemented in a software and / or hardware manner and integrated in the source device. The source device is a TSN node device.

[0148] Figure 11 FIG. is a schematic hardware structure diagram of a source device provided in an embodiment. As Figure 11 shown, a source device provided in this embodiment includes: a processor 610 and a storage device 620. The processor in the source device can be one or more. Figure 11 Taking one processor 610 as an example, the processor 610 and the storage device 620 in the device can be connected by a bus or other means. Figure 11 Taking the connection by bus as an example.

[0149] When the one or more programs are executed by the one or more processors 610, the one or more processors implement the advertisement method described in any of the above embodiments.

[0150] The storage device 620 in the source device, as a computer-readable storage medium, can be used to store one or more programs, and the programs can be software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the advertisement method in the embodiments of the present invention (for example, the modules in the advertisement device shown in Figure 9 include: an advertisement module 410 and a packet 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 advertisement method in the above method embodiments.

[0151] The storage device 620 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the device (such as the notification information, TSN service packets, etc. in the above embodiments). In addition, 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. In some instances, the storage device 620 may further include a memory remotely set relative to the processor 610, and these remote memories can be connected to the source device through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0152] Moreover, when one or more programs included in the above source device are executed by the one or more processors 610, the following operations are implemented: sending notification information, where the notification information includes a traffic flow identifier and a corresponding TSN configuration; sending TSN service packets.

[0153] The source device proposed in this embodiment and the notification method proposed in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to in any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the notification method.

[0154] In the embodiments of the present application, a message processing system is further provided. Figure 12 A schematic structural diagram of a message processing system provided for an embodiment. As Figure 12 shown, the system includes: 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 packets sent by the source device 710 pass through at least one bridge node 720, and the TSN service packets are processed by the bridge node according to the notification information and then forwarded to the destination device 730.

[0155] In the message processing system of this embodiment, for the information sent by the source device 710 to reach the destination device 730, several bridging processes are required. There are distributed clocks on each bridge node 720 for time synchronization calculation, and queues are used to process the priority of data, including a fast-channel mode and a preemptive mechanism for high-dynamic data.

[0156] In this embodiment, the source device 710 is used to send notification information, where the notification information includes a traffic flow identifier and a corresponding TSN configuration; it is also used to send TSN service packets.

[0157] In this embodiment, the bridge node 720 is used to receive TSN service packets; query the mapping relationship table of the service flow identifier and the TSN configuration according to the packet header of the TSN service packet, and the mapping relationship table is established according to the advertisement information of the source device; process the TSN service packet according to the query result of the mapping relationship table.

[0158] In one embodiment, before the bridge node 720 queries the mapping relationship table of the service flow identifier and the TSN configuration according to the packet header of the TSN service packet, it also responds to the advertisement trigger condition to obtain the advertisement information of the source device, and the advertisement information includes the service flow identifier and the corresponding TSN configuration; under the condition of meeting the set conditions, extract the service flow identifier and the TSN configuration supported by the bridge node from the advertisement information and write them into the local mapping relationship table.

[0159] In one embodiment, the set conditions include:

[0160] The service flow identifier in the advertisement information matches the service flow identifier of the response packet of the destination device, and the bandwidth resource of the bridge node is greater than or equal to the bandwidth resource required by the TSN service corresponding to the service flow identifier.

[0161] In one embodiment, before the bridge node 720 queries the mapping relationship table of the service flow identifier and the TSN configuration according to the packet header of the TSN service packet, it also reserves the bandwidth resource for processing the TSN service packet and establishes the forwarding table entry of the TSN service packet under the condition of meeting the set conditions.

[0162] In one embodiment, the bridge node 720 processes the TSN service packet according to the query result, including: if the packet header is consistent with the service flow identifier and the TSN configuration supported by the bridge node, use the reserved bandwidth resource to forward the TSN service packet to the destination device according to the forwarding table entry.

[0163] In one embodiment, the advertisement trigger conditions include at least one of the following: receiving an advertisement trigger command; receiving the first TSN service packet sent by the source device; receiving a protocol extension packet sent by the source device.

[0164] In one embodiment, the advertisement information is transmitted through a protocol extension packet of the flow reservation protocol SRP; the protocol extension packet includes a service flow identifier field and a TSN configuration field.

[0165] In one embodiment, the advertisement information is transmitted through a link layer discovery protocol LLDP packet; the content field in the LLDP packet carries the service flow identifier and the TSN configuration.

[0166] The message processing system proposed in this embodiment and the message processing method and notification method proposed in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the message processing method or notification method.

[0167] An embodiment of the present application further provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute a message processing method or a notification method when executed by a computer processor.

[0168] Among them, the message processing method includes: receiving a time-sensitive network (TSN) service message; querying a mapping relationship table of service flow identifiers and TSN configurations according to the message header of the TSN service message, and the mapping relationship table is established according to the notification information of the source device; processing the TSN service message according to the query result of the mapping relationship table.

[0169] Among them, the notification method includes: sending notification information, where the notification information includes a service flow identifier and a corresponding TSN configuration; sending a TSN service message.

[0170] From the above description of the embodiments, those skilled in the art can understand that the present application can be implemented by means of software and general-purpose hardware, or can also be implemented by hardware. Based on such an understanding, 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 floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disc of a computer, etc., including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method described in any embodiment of the present application.

[0171] The above is only an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

[0172] Any block diagram of a logical process in the accompanying drawings of the present application may represent a program step, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. A computer program may be stored in a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile disc DVD or CD optical disc), etc. The computer-readable medium may include a non-transitory storage medium. The data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FGPA), and a processor based on a multi-core processor architecture.

[0173] By way of illustrative and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adaptations of the above embodiments will be apparent to those skilled in the art upon consideration of the accompanying drawings and the claims, without departing from the scope of the invention. Accordingly, the proper scope of the invention will be determined in accordance with the claims.

Claims

1. A message processing method, applied to a bridge node, characterized in that Comprising: Receiving time-sensitive network (TSN) service packets; Querying a mapping relation table of service flow identifiers and TSN configurations according to the packet header of the TSN service packet to determine whether the bridge node has a TSN configuration for processing the TSN service packet, where the mapping relation table is established according to the advertisement information of the source device; the TSN configuration includes policies and mechanisms for providing consistent deterministic services for TSN services; Processing the TSN service packet according to the query result of the mapping relation table.

2. The method according to claim 1, wherein Before querying the mapping relation table of service flow identifiers and TSN configurations according to the packet header of the TSN service packet, further comprising: In response to an advertisement trigger condition, obtaining the advertisement information of the source device, where the advertisement information includes service flow identifiers and corresponding TSN configurations; Under a set condition, extracting the service flow identifiers and TSN configurations supported by the bridge node from the advertisement information and writing them into the local mapping relation table.

3. The method according to claim 2, wherein The set condition includes: The service flow identifier in the advertisement information matches the service flow identifier of the response packet of the destination device, and the bandwidth resource of the bridge node is greater than or equal to the bandwidth resource required by the TSN service corresponding to the service flow identifier.

4. The method according to claim 3, characterized in that Before querying the mapping relation table of service flow identifiers and TSN configurations according to the packet header of the TSN service packet, further comprising: Under a set condition, reserving a bandwidth resource for processing the TSN service packet and establishing a forwarding table entry for the TSN service packet.

5. The method according to claim 4, characterized in that, The processing the TSN service packet according to the query result of the mapping relation table includes: If the packet header is consistent with the service flow identifiers and TSN configurations supported by the bridge node, using the reserved bandwidth resource to forward the TSN service packet to the destination device according to the forwarding table entry.

6. The method according to claim 2, wherein The advertisement trigger condition includes at least one of the following: Receiving an advertisement trigger command; Receiving the first TSN service packet sent by the source device; Receiving a protocol extension packet sent by the source device.

7. The method according to any one of claims 1 to 6, characterized in that, The advertisement information is transmitted through a protocol extension packet of the flow reservation protocol (SRP); The protocol extension packet includes a service flow identifier field and a TSN configuration field.

8. The method according to any one of claims 1-6, characterized in that, The advertisement information is transmitted through a link layer discovery protocol (LLDP) packet; The content field in the LLDP packet carries service flow identifiers and TSN configurations.

9. A notification method, applied to a source device, characterized in that, Comprising: Sending advertisement information, where the advertisement information includes service flow identifiers and corresponding TSN configurations; Sending a TSN service packet, where the TSN service packet is processed by a bridge node executing any one of the packet processing methods in claims 1-8 according to the advertisement information.

10. The method according to claim 9, wherein The advertisement trigger condition for sending the advertisement information includes at least one of the following: Receiving an advertisement trigger command; Sending the first TSN service packet; Sending a protocol extension packet.

11. A bridge node, characterized in that, Comprising: [[ID=2S]]One or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, enabling the one or more processors to implement any one of the packet processing methods in claims 1-8.

12. A source device, characterized in that, Comprising: One or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the advertisement method according to any one of claims 9-10.

13. A message processing system, characterized in that, Comprising: A destination device, at least one bridge node according to claim 11, and a source device according to claim 12; The source device sends advertisement information to each of the bridge nodes; The TSN service packet sent by the source device is forwarded to the destination device after being processed by at least one of the bridge nodes according to the advertisement information.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the packet processing method according to any one of claims 1-8 or the advertisement method according to any one of claims 9-10.

Images