Resource reservation method for redundant paths, network device and storage medium

Abstract

The present application proposes a method for reserving resources for a redundant path, a network device and a storage medium, the method comprising: obtaining, from an attribute declaration message received from a source device, a time-sensitive network (TSN) service targeted by the attribute declaration message, and an indication of whether redundant propagation is required for the attribute declaration message; if the indication is that redundant propagation is required for the attribute declaration message, and the number of spanning tree instances maintained in the present bridge device is at least two, then copying the attribute declaration message; based on at least two spanning tree instances, propagating the received attribute declaration message and the copied attribute declaration message to establish a redundant path for the TSN service between the source device and the destination device; and in response to receiving a resource reservation request message for the TSN service from the destination device, reserving resources for the redundant path for the TSN service.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a redundant path resource reservation method, network equipment and storage medium. Background Art

[0002] The IEEE802.1Q Time Sensitive Networking (TSN) working group provides bounded latency, jitter, and extremely low packet loss rate services for TSN service flows through the proposed methods and mechanisms. In the TSN working group standard, when the packet duplication elimination mechanism is proposed to improve the reliability of the network, it is necessary to plan redundant service paths for TSN service flows that meet the bandwidth and latency requirements.

[0003] In the currently proposed TSN standard draft, the Stream Reservation Protocol (SRP) proposed by the IEEE802.1Qat standard is used to reserve resources and establish forwarding paths between the TSN service source (Talker) and the corresponding destination (Listeners). However, the existing SRP standard can only establish a unicast forwarding path that meets business requirements between the source and destination, so it cannot provide redundant path resource reservation for TSN service flows. Summary of the invention

[0004] The present application provides a redundant path resource reservation method, a network device, and a storage medium.

[0005] In a first aspect, an embodiment of the present application provides a method for reserving resources for a redundant path, which is applied to a bridge device, comprising: obtaining, from an attribute declaration message received from a source device, a time-sensitive network TSN service targeted by the attribute declaration message, and an indication of whether redundant propagation is required for the attribute declaration message; if the indication is that redundant propagation is required for the attribute declaration message, and the number of spanning tree instances maintained in the bridge device is at least two, copying the attribute declaration message; based on at least two spanning tree instances, propagating the received attribute declaration message and the copied attribute declaration message to establish a redundant path for the TSN service between the source device and the destination device; and in response to receiving a resource reservation request message for the TSN service from the destination device, reserving resources for a redundant path for the TSN service.

[0006] In the second aspect, an embodiment of the present application provides a method for reserving resources for a redundant path, which is applied to a source-end device, including: when it is determined that resources for a redundant path need to be reserved for a time-sensitive network TSN service, a first attribute declaration message is generated for the TSN service, the first attribute declaration message carrying an indication that redundant propagation needs to be provided for the attribute declaration message; the first attribute declaration message is sent to a bridge device connected to the source-end device, wherein at least two spanning tree instances are maintained in the bridge device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source-end device and a specified destination-end device according to the indication of the first attribute declaration message.

[0007] In a third aspect, an embodiment of the present application provides a resource reservation method for a redundant path, which is applied to a destination device, comprising: receiving at least two attribute declaration messages for the same time-sensitive network TSN service through a bridge device connected to the destination device; if the TSN service is a TSN service of interest to the destination device, and each received attribute declaration message is a message propagated based on different spanning tree instances, then for each received attribute declaration message, a resource reservation request message for the TSN service and corresponding to a different spanning tree instance is generated; wherein the different spanning tree instances are spanning tree instances among at least two spanning tree instances maintained in a bridge device connected to the source device, and at least two spanning tree instances are used to establish a redundant path for the TSN service between the source device and the destination device; based on the different spanning tree instances corresponding to each generated resource reservation request message, each resource reservation request message is sent to the bridge device connected to the destination device.

[0008] In a fourth aspect, an embodiment of the present application provides a network device, comprising: one or more processors; a memory, on which one or more programs are stored, and when the one or more programs are executed by one or more processors, the one or more processors implement the resource reservation method for redundant paths of any of the above aspects.

[0009] In a fifth aspect, an embodiment of the present application provides a storage medium, which stores a computer program. When the computer program is executed by a processor, it implements a resource reservation method for any redundant path in the embodiment of the present application.

[0010] According to the redundant path resource reservation method, network device and storage medium of the first aspect of the embodiment of the present application, the bridge device can provide redundant propagation between the source device and the destination device for the source attribute declaration message based on at least two spanning tree instances maintained by itself, thereby establishing a redundant spare path for the TSN service, and according to the resource reservation request message from the destination device, reserve resources for the redundant path for the TSN service.

[0011] According to the redundant path resource reservation method, network device and storage medium of the second aspect of the embodiment of the present application, the source-end device can indicate the need to provide redundant propagation for the attribute declaration message through an attribute declaration message, and send the attribute declaration message to the connected bridge device, so that the bridge device provides redundant propagation for the attribute declaration message based on at least two spanning tree instances maintained, thereby establishing a redundant path for the TSN service between the source-end device and the specified destination-end device.

[0012] According to the resource reservation method, network device and storage medium for redundant paths of the third aspect of the embodiment of the present application, when the destination device receives at least two attribute declaration messages for TSN services and propagated based on different spanning tree instances, the different spanning tree instances come from at least two spanning tree instances maintained in a bridge device connected to the source device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source device and the destination device. If the destination device is interested in the TSN service, a resource reservation request message can be constructed for each attribute declaration message received to initiate a resource reservation request for the redundant path of the TSN service.

[0013] With regard to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A schematic diagram showing a flow chart of a method for reserving resources for redundant paths according to an embodiment of the present application.

[0015] Figure 2 A schematic diagram showing the encoding format of an attribute declaration message based on the SRP protocol of an exemplary embodiment.

[0016] Figure 3 A schematic diagram showing the encoding format of an extended SRP-based attribute declaration message in an embodiment of the present application is shown.

[0017] Figure 4 A schematic diagram showing a flow chart of initializing the attribute declaration message by a source device according to an exemplary embodiment of the present application.

[0018] Figure 5 A schematic flow chart showing a method for reserving resources for redundant paths according to another embodiment of the present application is shown.

[0019] Figure 6 A schematic diagram showing the process flow of a bridge device processing an attribute declaration message according to an exemplary embodiment of the present application.

[0020] Figure 7 A schematic diagram showing a processing flow of a bridge device receiving an attribute declaration message according to an exemplary embodiment of the present application.

[0021] Figure 8 A schematic diagram showing a processing flow of a bridge device receiving a resource reservation cancellation message according to an exemplary embodiment of the present application.

[0022] Fig. 9 A schematic flow chart of a method for reserving resources for redundant paths according to yet another embodiment of the present application is shown.

[0023] Fig.10 It is a schematic diagram of the encoding format of the existing destination message based on the SRP protocol in an embodiment of the present application.

[0024] Fig.11 It is a schematic diagram of the encoding format of the destination message in the embodiment of the present application.

[0025] Fig.12 A schematic diagram showing a processing flow of a destination device receiving an attribute declaration message according to an exemplary embodiment of the present application.

[0026] Fig.13 A schematic diagram of the processing flow of redundant path resource reservation based on the SRP protocol according to an embodiment of the present application is shown.

[0027] Fig.14 A schematic diagram of the processing flow of canceling redundant path resource reservation based on the SRP protocol according to an embodiment of the present application is shown.

[0028] Fig.15 A schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention.

[0029] Fig.16 A schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention.

[0030] Fig.17 A schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention.

[0031] Fig.18 A structural diagram showing an exemplary hardware architecture of a computing device capable of implementing the method and apparatus for reserving resources for redundant paths according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present application more clear, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0033] In the TSN working group standard, the two service quality requirements of bounded latency and jitter are met through standards such as 802.1Qbv, 802.1Qch, and 802.1Qav; and the extremely low packet loss rate requires the network to have high reliability and availability, and to be able to cope with single node failures and single link failures that may occur in the network as much as possible.

[0034] In the TSN working group standard, IEEE802.1CB improves network reliability by proposing a packet duplication elimination mechanism. Specifically, the packets of the corresponding stream handle are duplicated at designated ports to achieve redundant transmission, and elimination and reordering operations are performed at traffic aggregation points or receiving points to avoid packet duplication and disorder. This requires the ability to plan redundant service paths that meet bandwidth and latency requirements for TSN service flows.

[0035] In the currently proposed TSN standard draft, the Stream Reservation Protocol (SRP) proposed by the IEEE802.1Qat standard is used to reserve resources and establish forwarding paths between the TSN service source end (Talker) and the corresponding destination end (Listeners). SRP protocol messages can be transmitted in a specified spanning tree.

[0036] As an example, the spanning tree may be generated by the Rapid Spanning Tree Protocol, or may be established by, for example, the Path Control and Reservation (PCR) proposed by IEEE802.1Qca. When the PCR protocol is used, all links included in the specified spanning tree may be displayed.

[0037] As an example, in the Multiple Registration Protocol (MRP), a spanning tree instance can be specified by a spanning tree identifier. Specifically, the SRP protocol message can run in the basic spanning tree instance specified by the default identifier. Since the SRP protocol message propagates in the spanning tree instance, there may be only one forwarding path between the source end and one destination end, so at most a unicast forwarding path that meets the service requirements can be established between the source end and one destination end. Therefore, based on the existing SRP standard, it is impossible to provide redundant path resource reservation for TSN service flows.

[0038] In addition, other TSN-related draft standards, such as IEEE802.1Qcc, currently only implement traffic shaping, service flow feature configuration, and configuration extensions to the basic SRP protocol, such as supporting up to 7 flow reservation categories, but have not yet proposed an extension method for resource collection, calculation, and path delivery for redundant paths. No clear solutions have been proposed in other draft standards and plans.

[0039] The embodiment of the present application provides a resource reservation method for a redundant path. The extended attribute declaration message based on the SRP protocol can carry a redundant field and a spanning tree identifier, and indicate through the value of the redundant field that the network needs to establish a redundant path for it, and indicate through the spanning tree identifier the spanning tree instance based on which the attribute declaration message is transmitted in the bridge device, and use the bridge port connected to the source end as an agent of the redundant path function, increase the parsing of the redundant field, and when it is determined that the value of the redundant field indicates that the network needs to establish a redundant path for it, copy and modify the source attribute declaration message, and propagate the message in two different spanning tree instances, thereby establishing a redundant service protection path for the TSN service.

[0040] Figure 1 A schematic diagram showing a flow chart of a redundant path resource reservation method according to an embodiment of the present application. Figure 1 As shown, the resource reservation method for redundant paths in the embodiment of the present application can be applied to a source-end device, and the method can include the following steps.

[0041] S110, when it is determined that redundant path resource reservation is required for a time sensitive network TSN service, a first attribute declaration message for the TSN service is generated, the first attribute declaration message carries an indication that redundant propagation needs to be provided for the attribute declaration message.

[0042] S120, sending a first attribute declaration message to a bridge device connected to the source end device, wherein at least two spanning tree instances are maintained in the bridge device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source end device and the specified destination end device according to the instructions of the first attribute declaration message.

[0043] In an embodiment of the present application, the source device, i.e., the TSN service source Talker, can indicate the need to provide redundant propagation for the attribute declaration message through an attribute declaration message, and send the attribute declaration message to the connected bridge device, so that the bridge device provides redundant propagation for the attribute declaration message based on at least two spanning tree instances maintained, thereby establishing a redundant path for the TSN service between the source device and the specified destination device.

[0044] In one embodiment, S110 may include: when it is determined that resources for a redundant path need to be reserved for a time-sensitive network TSN service, a first attribute declaration message for the TSN service is generated, wherein the first attribute declaration message carries a flow identifier for identifying the TSN service, redundant information having a first redundant information value, and a spanning tree identifier having an arbitrary identifier value; wherein the first redundant information value is used to indicate that redundant propagation needs to be provided for the attribute declaration message, and the arbitrary identifier value is used to indicate the spanning tree instance on which the propagation of the first attribute declaration message is based.

[0045] In one embodiment, if it is determined that there is no need to reserve resources for redundant paths for time-sensitive network TSN services, the method also includes: S130, generating a second attribute declaration message for the TSN service, carrying in the attribute declaration message a flow identifier for identifying the TSN service, redundant information having a second redundant information value, and a spanning tree identifier having a predetermined identifier value; wherein the second redundant information value is used to indicate that there is no need to provide redundant propagation for the attribute declaration message, and the predetermined identifier value is used to indicate the spanning tree instance on which the propagation of the second attribute declaration message is based.

[0046] In an embodiment of the present application, the source device can expand the source message based on the SRP protocol to carry a flow identifier, a redundancy field and a spanning tree identifier field, wherein the flow identifier is used to uniquely identify the TSN service, the redundant information in the redundant field is used to indicate the redundant propagation requirement of the attribute declaration message, and the spanning tree identifier in the spanning tree identifier field is used to indicate the spanning tree instance on which the propagation of the attribute declaration message in the bridge device is based. According to the spanning tree instance indicated by the spanning tree identifier, the attribute declaration message for the TSN service is sent to reserve redundant path resources for the time-sensitive network TSN service identified by the flow identifier.

[0047] In an embodiment of the present application, at least two spanning tree instances can be established in advance in the TSN network, one of the spanning tree instances is used as the main spanning tree instance, and the spanning tree instance other than the main spanning tree instance is used as the backup spanning tree instance. In order to establish a redundant path, the link set of the main and backup spanning trees corresponding to the main spanning tree instance and the backup spanning tree instance should contain as few duplicate links as possible. Exemplarily, a spanning tree link set can be established by reserving PCRs through path control, thereby establishing a spanning tree instance that meets the requirements. It should be understood that in an embodiment of the present application, other methods can also be used to establish the process of establishing the main spanning tree instance and the backup spanning tree instance, and the embodiment of the present application does not make specific limitations.

[0048] In one embodiment, for the established primary spanning tree instance and the backup spanning tree instance, the spanning tree identifier corresponding to the spanning tree instance can be maintained in the bridge through MRP. As an example, when the spanning tree identifier value corresponding to the spanning tree instance is set to 0, it is used to indicate forwarding according to the default or predetermined spanning tree instance.

[0049] In an embodiment of the present application, a main spanning tree instance and at least one backup spanning tree instance may be established. For the purpose of simplifying the description, the following multiple embodiments of this document take a main spanning tree instance and a backup spanning tree instance established through PCR as an example to illustrate the process of providing redundant propagation for attribute declaration messages and the process of reserving resources for redundant paths. However, this description cannot be interpreted as limiting the scope or implementation possibility of this solution. The processing method of a main spanning tree instance and more than one backup spanning tree instance is consistent with the processing method of a main spanning tree instance and one backup spanning tree instance.

[0050] Figure 2 FIG. 1 is a schematic diagram showing the encoding format of an attribute declaration message based on the SRP protocol of an exemplary embodiment. Figure 2 As shown, the existing attribute declaration message based on the SRP protocol may include the following fields: physical address (MACAddress), unique identifier (Unique ID), destination address (Destination Address), virtual local area network identifier (VLAN_ID), maximum frame size (Max Frame Size), maximum interval frame (Max Interval Frame), data frame priority (Data Frame Priority), rank (Rank), reserved field (Reserved) and accumulated delay (Accumulated Latency).

[0051] Among them, MAC Address and Unique ID can be used as the stream identifier (Stream ID) of the attribute declaration message, Destination Address and VLAN_ID can be used as the data frame parameters (Data FrameParameters) of the attribute declaration message, Max Frame Size and Max Interval Frame can be used as the flow specification (TSprc) of the attribute declaration message, and Data Frame Priority and Reserved can be used as the priority and ranking of the attribute declaration message.

[0052] Figure 3 FIG. 1 is a schematic diagram showing the encoding format of the extended attribute declaration message based on the SRP protocol in the embodiment of the present application. Figure 3As shown, the extended attribute declaration message based on the SRP protocol carries a redundancy field (Redundancy) and a spanning tree identifier (Identifier) ​​field.

[0053] exist Figure 3 In the example of the format of the SRP protocol attribute declaration message generated by the source device, the redundancy field may occupy 1 bit, for example. When the redundancy field value is 1, it indicates that redundancy protection is required, and vice versa, when the redundancy field value is 0, it indicates that redundancy protection is not required. The spanning tree identification field may occupy 7 bits, for example, and the maximum number of spanning tree instances supported is 128.

[0054] It should be understood that the embodiments of the present application can flexibly specify the length of the redundant field and the spanning tree identification field according to the actual application scenario requirements. The examples shown in this embodiment are only for explanation and are not intended to limit the content of the present invention.

[0055] In one embodiment, before step S120, the method further includes: S01, if it is determined that the attribute declaration message needs to be redundantly propagated, setting the redundant information to a first redundant information value, and setting the spanning tree identifier to an arbitrary identifier value; S02, if it is determined that the attribute declaration message does not need to be redundantly propagated, setting the redundant information to a second redundant information value, and setting the spanning tree identifier to a predetermined identifier value, wherein the second redundant information value is different from the first redundant information value.

[0056] As an example, the first redundant information value is TRUE, the second redundant information value is FALSE, and the predetermined identification value of the spanning tree identification may be set to 0 by default.

[0057] In an embodiment of the present application, the attribute declaration message generated by the source device is expanded to add two fields, namely, the redundancy field and the spanning tree identification field. The redundancy field is used to indicate the redundant propagation requirement for the attribute declaration message, that is, whether redundant propagation is required for the source attribute declaration message. Exemplarily, if the value of the redundancy field is TRUE, it means that redundant propagation is required, and if the value of the redundancy field is FALSE, it indicates that redundant propagation is not required; the spanning tree identification field is used to indicate which spanning tree instance the source attribute declaration message is based on to propagate in the bridge.

[0058] In an embodiment of the present application, there may be a variety of triggering mechanisms for the resource reservation process of the redundant path of the TSN service flow. For example, as described in the above embodiment, the redundant path resource reservation process of the TSN service flow is triggered by sending an SRP protocol message through the source device, wherein the source device has SRP protocol capabilities. In other embodiments, for example, the bridge is configured to trigger the sending of an SRP protocol message through a configuration method; or, the resource reservation process can be started on the bridge port directly connected to the source device triggered by a specified service message, wherein the bridge port needs to be configured in advance whether it is in redundant mode.

[0059] Figure 4 The following is a schematic diagram showing the process of initializing the attribute declaration message by the source device of the exemplary embodiment of the present application. Figure 4 As shown, the source device may perform the following steps to initialize the attribute declaration message.

[0060] S11, the source device determines whether to perform redundant propagation of the attribute declaration message.

[0061] S12: If it is determined that redundant propagation is required, the redundant field of the source attribute declaration message is set to TRUE, and the spanning tree identifier value can be set to any value.

[0062] S13, if it is determined that a redundant path does not need to be established, the redundant field is set to FALSE and the spanning tree identification field is set to 0, indicating that the message is propagated based on a predetermined spanning tree instance.

[0063] Through the above steps S11-S13, the source-end device completes the initialization setting of the content carried by the attribute declaration message according to whether to perform redundant propagation of the attribute declaration message.

[0064] According to an embodiment of the present application, the source device can expand the source message based on the SRP protocol to carry a redundant field and a spanning tree identification field, indicate through the redundant field whether to redundantly propagate the attribute declaration message, and send the attribute declaration message of the TSN service to the bridge port directly connected to the source device according to the spanning tree instance indicated by the spanning tree identifier, so as to trigger the reservation of redundant path resources for the TSN service identified by the flow identifier.

[0065] Figure 5 A schematic diagram showing a flow chart of a method for reserving resources for redundant paths according to another embodiment of the present application is shown. Figure 5 As shown, the resource reservation method for redundant paths in the embodiment of the present application can be applied to a bridge device, and the method can include the following steps.

[0066] S210, obtaining, from the attribute declaration message received from the source device, a time-sensitive network TSN service targeted by the attribute declaration message, and an indication of whether redundant propagation needs to be provided for the attribute declaration message.

[0067] S220: If it is indicated that redundant propagation needs to be provided for the attribute declaration message, and the number of spanning tree instances maintained in the current bridge device is at least two, then the attribute declaration message is replicated.

[0068] S230, based on at least two spanning tree instances, propagate the received attribute declaration message and the copied attribute declaration message to establish a redundant path for the TSN service between the source end device and the destination end device.

[0069] S240 , in response to receiving a resource reservation request message for the TSN service from the destination device, reserving resources for a redundant path for the TSN service.

[0070] According to the resource reservation method for redundant paths in an embodiment of the present application, the bridge device obtains redundant information and spanning tree instances from the received attribute declaration message based on the SRP protocol. If the redundant information indicates that redundant propagation of the attribute declaration message is required and the number of corresponding spanning tree instances in the bridge device is greater than a predetermined value, the attribute declaration message is copied and the attribute declaration message is modified according to the corresponding spanning tree instance so that the attribute declaration message can be propagated in different spanning tree instances, thereby establishing a redundant service protection path for the TSN service.

[0071] In the above step S210, the spanning tree identifier can be used to identify a spanning tree instance, and the spanning tree topology information can be determined through the spanning tree instance, thereby determining the bridge forwarding link corresponding to the spanning tree topology information.

[0072] In one embodiment, the received attribute declaration message carries a flow identifier and redundant information; in this embodiment, step S210 may specifically include: S211, taking the TSN service indicated by the flow identifier carried in the received attribute declaration message as the TSN service targeted by the attribute declaration message; S212, if the redundant information value is the first redundant information value, determining that redundant propagation needs to be provided for the attribute declaration message; S213, if the redundant information value is the second redundant information value, determining that redundant propagation does not need to be provided for the attribute declaration message, and the second redundant information value is different from the first redundant information value.

[0073] In one embodiment, when it is determined that redundant propagation needs to be provided for an attribute declaration message, step S230 may specifically include: S231, based on the acquired spanning tree identifiers of at least two spanning tree instances, modifying the spanning tree identifier in the received attribute declaration message and the spanning tree identifier in the copied attribute declaration message to different spanning tree identifiers; S232, modifying the redundant information in the received attribute declaration message and the redundant information in the copied attribute declaration message to a second redundant information value; S233, propagating the received attribute declaration message and the copied attribute declaration message in different spanning tree instances according to the modified different spanning tree identifiers to establish a redundant path for the TSN service.

[0074] In this embodiment, when the redundant information has a first redundant information value, it is used to indicate that redundant propagation needs to be provided; when the redundant information has a second redundant information value, it is used to indicate that redundant propagation does not need to be provided.

[0075] Exemplarily, the spanning tree identifier values ​​corresponding to the primary and backup spanning tree instances established by PCR in the bridge device may be a and b. For example, in step S131, the spanning tree identifier in the received attribute declaration message may be set to a, and the spanning tree identifier in the copied attribute declaration message may be set to b.

[0076] In one embodiment, if the indication is that redundant propagation needs to be provided for the attribute declaration message, and the number of spanning tree instances maintained in the current bridge device is less than two, the method also includes: S250, setting an indication that redundant propagation does not need to be provided for the received attribute declaration message, and propagating the received attribute declaration message based on a predetermined spanning tree instance in the spanning tree instance maintained by the current bridge device.

[0077] In one embodiment, S250 may specifically include: S251, setting the spanning tree identifier carried in the received attribute declaration message to a predetermined identifier value, the predetermined identifier value is used to indicate a predetermined spanning tree instance; S252, setting the redundant information carried in the received attribute declaration message to a second redundant information value, the second redundant information value is used to indicate that there is no need to provide redundant propagation for the attribute declaration message; S253, based on the predetermined spanning tree instance, propagating the attribute declaration message carrying the second redundant information value and the predetermined identifier value.

[0078] Through the above steps S251-S253, if the redundant information in the attribute declaration message received by the bridge device indicates that redundant propagation of the attribute declaration message is required, but the number of corresponding spanning tree instances in the bridge device is insufficient to provide redundant propagation, the redundant information in the attribute declaration message can be modified to a second redundant information value to indicate that there is no need for redundant propagation of the attribute declaration message, and the attribute declaration message is forwarded according to the spanning tree instance indicated by the predetermined identification value (default spanning tree instance).

[0079] In one embodiment, if the received attribute declaration message indicates that redundant propagation of the attribute declaration message is not required, the method further includes: S260, forwarding the received attribute declaration message based on the spanning tree instance indicated by the spanning tree identifier carried in the received attribute declaration message.

[0080] In this embodiment, if the redundant information is the second redundant information value, it means that there is no need to provide redundant propagation for the attribute declaration message, that is, there is no need to copy and modify the attribute declaration message.

[0081] In one embodiment, after obtaining the redundant information and spanning tree identifier carried in the attribute declaration message, the method further includes: S10, registering the attribute information contained in the received attribute declaration message at the port of the bridge device that receives the attribute declaration message.

[0082] In this embodiment, by registering the message attributes of the attribute declaration message, the message attributes are dynamically forwarded and transferred between bridge devices, thereby achieving the purpose of reducing the manual configuration of the network administrator and ensuring the correct configuration of network attributes.

[0083] Figure 6 FIG. 1 is a schematic diagram showing a process flow of a bridge device processing an attribute declaration message according to an exemplary embodiment of the present application. Figure 6 As shown, in this embodiment, the processing of the attribute declaration message by the bridge device may include the following steps.

[0084] S21, the bridge device port receives a source attribute declaration message.

[0085] S22, parse the redundant field of the source attribute declaration message, and determine whether the redundant field of the message is TRUE. If it is TRUE, go to S23, otherwise go to S27.

[0086] S23, determine the number of spanning tree instances maintained in the current bridge, if it is greater than or equal to 2, go to S24, otherwise go to S25.

[0087] S24, copy a source end attribute declaration message, the original message is the main message, the copy message is the backup message, and set the spanning tree identifier of the main message and the spanning tree identifier of the backup message.

[0088] For example, the spanning tree identifier field of the primary message is set to a; the spanning tree identifier of the backup message is set to b, and the process goes to S26.

[0089] S25, set the spanning tree flag in the attribute declaration message to 0, and go to S26.

[0090] S26, set the redundant field value of the source attribute declaration message to FALSE.

[0091] S27, registering the source end attribute declaration message attribute at the port.

[0092] S28, transmitting the attribute declaration message in the corresponding spanning tree based on the spanning tree identification field value carried in the attribute declaration message of the source end.

[0093] Through the above steps S21-S28, a port of the bridge device receives the source attribute declaration message and implements the registration and propagation process of modifying the attribute declaration message.

[0094] In one embodiment, step S240 may include: S241, receiving a resource reservation request message from a destination device through a first port, the resource reservation request message carrying a flow identifier and a spanning tree identifier, and the first port is any port among multiple ports of the present bridge device; S242, if the bandwidth of the first port meets the predetermined bandwidth requirement and the first resource reservation request number is zero, reserving bandwidth resources for the TSN service indicated by the flow identifier carried in the resource reservation request message and establishing a forwarding table entry. The first resource reservation request number is the number of resource reservation requests for the TSN service received through the first port and recorded in advance in the present bridge device.

[0095] Through the above steps S241-S242, when the bandwidth of the same port meets the predetermined bandwidth demand and the number of resource reservation requests of the port for a resource reservation request message of a certain flow identifier is zero, the bandwidth resources are reserved for the TSN service indicated by the flow identifier and a forwarding table entry is established. In other words, when the same port receives a resource reservation with the same flow identifier, multiple resources will not be reserved, and the duplicate message elimination function can be performed here.

[0096] Table 1 below shows the number of resource reservation requests corresponding to the service flows of each port recorded by the bridge device according to an exemplary embodiment of the present application.

[0097] Table 1 Number of resource reservation requests corresponding to service flows in each port of the bridge device

[0098] Port Number Flow ID Resource reservation request times fei-0 / 1 / 0 / 1 1 4 spi-0 / 2 / 0 / 2 2 2 fei-0 / 1 / 0 / 2 1 4 fei-0 / 1 / 0 / 3 4 1

[0099] As can be seen from Table 1, the bridge device can maintain the number of resource reservation requests corresponding to each service flow received at each port, thereby updating or revoking the resource reservation of the same S-ID under the same port. It should be noted that when the same port receives the resource reservation of the same flow identifier, the corresponding number of resource reservation requests is recorded, but multiple resources will not be reserved, and the duplicate message elimination function will be performed here.

[0100] In one embodiment, after step S242, or when the bandwidth of the first port meets the predetermined bandwidth requirement and the first resource reservation request number is greater than or equal to 1, the method further includes: S243, adding 1 to the record of the first resource reservation request number to obtain an updated first resource reservation request number; S244, forwarding the resource reservation request message based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

[0101] In this embodiment, the number of first resource reservation requests is greater than or equal to 1, indicating that the port has reserved resources and established forwarding table entries for the currently received service flow. Therefore, after updating the corresponding number of first resource reservation requests, no operations of reserving resources and establishing forwarding table entries are performed.

[0102] In one embodiment, if the bandwidth of the first port does not meet the predetermined bandwidth requirement, the method further includes: S270, forwarding the resource reservation request message based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

[0103] Figure 7 FIG. 1 is a schematic diagram showing a processing flow of a bridge device receiving an attribute declaration message according to an exemplary embodiment of the present application. Figure 7 As shown, the processing flow of the bridge device receiving the attribute declaration message may include the following steps.

[0104] S31, a bridge device port receives a resource reservation request message from a destination device.

[0105] S32, calculate the required bandwidth according to the source attribute declaration of the corresponding flow identifier on the port, and determine whether the bandwidth resources on the port meet the bandwidth demand. If so, go to S33, otherwise go to S37.

[0106] S33, searching for the number of resource reservation requests corresponding to the service flows in each port maintained by the bridge device.

[0107] S34, if the search result is not found or the corresponding number is 0, go to S35, otherwise go to S36.

[0108] S35, reserve bandwidth resources at the port and create a forwarding table entry.

[0109] S36, updating the number of resource reservation requests corresponding to the service flow in each port, so that the number of resource reservation requests corresponding to the destination end of the flow identifier is increased by 1.

[0110] S37, parsing the spanning tree identification field carried in the message, and continuing to propagate the destination message in the corresponding spanning tree.

[0111] Through the above steps S31-S35, when the port of the bridge device receives the destination resource reservation request message, the port can execute the above processing flow of reserving bandwidth and establishing forwarding table entries.

[0112] In one embodiment, the resource reservation method for a redundant path also includes: S280, receiving a resource reservation revocation message from a destination device through a first port, wherein the resource reservation revocation message carries a flow identifier and a spanning tree identifier of a TSN service; S281, reducing the number of first resource reservation requests by 1 to obtain an updated first resource reservation request number; S282, if the updated first resource reservation request number is zero, deleting the forwarding entry of the TSN service and releasing the reserved bandwidth resources of the TSN service, and forwarding the resource reservation revocation message according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation revocation message; S283, if the updated first resource reservation request number is greater than or equal to 1, forwarding the resource reservation revocation message according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation revocation message.

[0113] Figure 8 FIG. 1 is a schematic diagram showing a processing flow of a bridge device receiving a resource reservation cancellation message according to an exemplary embodiment of the present application. Figure 8 As shown, the processing flow of a bridge device receiving a resource reservation cancellation message may include the following steps.

[0114] S41, the bridge device port receives a resource reservation cancellation message from the destination device.

[0115] S42, reducing the number of resource reservation requests corresponding to the service flow in the port maintained by the bridge device by 1.

[0116] S43, determine whether the number of resource reservation requests corresponding to the service flow in the port in the bridge device is 0, if so, go to S44, if not, directly go to S45.

[0117] S44, deleting the forwarding table entry and releasing bandwidth resources.

[0118] S45, updating the number of resource reservation requests corresponding to the service flow maintained by the bridge device port.

[0119] S46: Based on the spanning tree instance indicated by the spanning tree identifier in the resource reservation cancellation request message, propagate the resource reservation cancellation request message in the corresponding spanning tree.

[0120] Through the above steps S41-S45, in this embodiment, when a port of the bridge device receives a flow reservation resource cancellation message sent by the destination end, it is necessary to find the number of resource reservation requests corresponding to the service flow in each port, and reduce the number of destination resource reservation requests corresponding to the flow identifier carried by the message in the table entry by 1. If and only if the number of destination attribute registrations corresponding to the flow identifier in the table is 0, the forwarding table entry is deleted and the corresponding bandwidth resources are released.

[0121] Fig. 9 A schematic diagram showing a flow chart of a method for reserving resources for redundant paths according to another embodiment of the present application is shown. Fig. 9 As shown, the redundant path resource reservation method can be applied to a destination device, and the method can include the following steps.

[0122] S510, receiving at least two attribute declaration messages for the same time sensitive network TSN service through a bridge device connected to the destination device.

[0123] After step S510, the method may further include: obtaining a flow identifier and a spanning tree identifier carried in each attribute declaration message, wherein the flow identifier is used to identify the TSN service, and the spanning tree identifier is used to indicate the spanning tree instance based on which the propagation of the attribute declaration message in the bridge device is based.

[0124] The attribute declaration message also carries redundant information, which is used to indicate the redundant propagation requirement of the attribute declaration message when the attribute declaration message is propagated in the bridge device.

[0125] S520, if the TSN service is a TSN service of interest to the destination device, and each received attribute declaration message is a message propagated based on a different spanning tree instance, then for each received attribute declaration message, a resource reservation request message corresponding to a different spanning tree instance of the TSN service is generated. In this step, the different spanning tree instance is a spanning tree instance in at least two spanning tree instances maintained in a bridge device connected to the source device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source device and the destination device.

[0126] In one embodiment, when generating resource reservation request messages corresponding to different spanning tree instances of a TSN service, the method may further include: carrying a flow identifier for identifying the TSN service and a spanning tree identifier corresponding to the different spanning tree instances in the resource reservation request message.

[0127] S530: Based on the different spanning tree instances corresponding to each generated resource reservation request message, each resource reservation request message is sent to a bridge device connected to the destination device.

[0128] According to the resource reservation method for redundant paths in the embodiment of the present application, the resource reservation request message based on the SRP protocol of the destination node device also needs to be extended to carry a spanning tree identification field, indicating which spanning tree instance the destination end message is based on to propagate in the bridge. When the destination end device receives the attribute declaration message corresponding to the flow identifier, it first extracts the spanning tree identification field value carried in the attribute declaration message, writes the spanning tree identification field value into the spanning tree identification field of the destination end message, and then makes a resource reservation request.

[0129] Fig.10 Schematic diagram of the encoding format of the destination end message based on the SRP protocol in the embodiment of the present application. Fig.10 As shown, in the existing destination message based on the SRP protocol, the physical address (MAC Address) and the unique identifier (Unique ID) form the stream ID (Stream ID) of the attribute revocation message, which is used to uniquely identify a TSN service flow.

[0130] In one embodiment, after step S530, the method further includes: S540, recording the flow identifier and the corresponding spanning tree identifier carried in each received attribute declaration message, where the spanning tree identifier is used to indicate the spanning tree instance based on which the propagation of the attribute declaration message in the bridge device is based.

[0131] Fig.11 Schematic diagram of the encoding format of the destination message in the embodiment of the present application. Fig.11 As shown, the destination message can carry a spanning tree identifier field. That is, a new byte is added to the existing destination message, and the byte content contains the spanning tree identifier field. The length of the spanning tree identifier field in the destination message is consistent with the length of the spanning tree identifier field in the attribute declaration message generated by the source end; for example, in the newly added byte, the spanning tree identifier field length is 7 bits, and another bit can be used as a reserved field.

[0132] It should be understood that the length of the spanning tree identification field carried in the destination message can be flexibly specified according to the requirements of the actual application scenario. The example shown in this embodiment is only for explanation and is not intended to limit the present invention.

[0133] Fig.12 The following is a schematic diagram showing the processing flow of the destination device receiving the attribute declaration message in the exemplary embodiment of the present application. Fig.12 As shown, in one embodiment, the processing flow of the attribute declaration message may include the following steps.

[0134] S61, the destination device receives an attribute declaration message.

[0135] S62, constructing and sending a resource reservation request message of the destination end by using the spanning tree identification information extracted from the attribute declaration message to make a resource reservation request.

[0136] S63: Record the flow identifier and spanning tree identifier in the resource reservation request.

[0137] Through the above steps S61-S63, the message generated by the destination device may be a resource reservation request message or a resource reservation cancellation message. The destination device sends a resource reservation request message carrying a flow identifier and a spanning tree identifier to request resource reservation for a specified TSN service.

[0138] In an embodiment of the present application, when the destination message is a resource reservation revocation message, a resource surplus attribute revocation message carrying spanning tree identification information can be generated by extending the encoding format of the resource reservation revocation message based on the SRP protocol in the destination node device to request the revocation of resources allocated to the redundant path.

[0139] Table 2 below shows the mapping relationship between the flow identifier and the spanning tree identifier in the destination node device according to an exemplary embodiment of the present application.

[0140] Table 2 Mapping relationship between flow ID and spanning tree ID in destination node device

[0141] Flow ID Resource reservation request times 1 {0} 2 {1，2} 1 {0} 4 {2，3}

[0142] It can be seen from Table 2 that the flow identifier and the corresponding spanning tree identifier information table can be maintained in the destination node, so that the destination node can release redundant path resources when actively canceling the flow reservation.

[0143] In one embodiment, the method for reserving resources for a redundant path may further include the following steps.

[0144] S551, when it is determined that resources of the TSN service need to be revoked, a flow identifier and a corresponding spanning tree identifier of the TSN service are obtained from pre-recorded flow identifiers and corresponding spanning tree identifiers.

[0145] S552: Generate a corresponding resource reservation cancellation message for each spanning tree identifier corresponding to the TSN service. The resource reservation cancellation message carries the flow identifier of the TSN service and a spanning tree identifier corresponding to the TSN service.

[0146] S553: ​​Send each resource reservation cancellation message based on the spanning tree instance indicated by the spanning tree identifier carried in each generated reservation cancellation message.

[0147] S554, deleting the predetermined information from the pre-recorded flow identifiers and the corresponding spanning tree identifiers, where the predetermined information is the flow identifier and the corresponding spanning tree identifier carried in the sent resource reservation cancellation message.

[0148] Through the above steps S551-S552, when the destination device makes a request to cancel the reserved resources of the flow, it is necessary to find the mapping relationship between the flow identifier and the spanning tree identifier, obtain the set of spanning tree identifier values ​​corresponding to a certain service flow of the destination, and then construct a flow reserved resource cancellation message for each spanning tree identifier value and send it out.

[0149] According to the resource reservation method for redundant paths in an embodiment of the present application, when the destination node device receives an attribute declaration message based on the SRP protocol for a TSN service, it extracts the flow identifier and spanning tree identifier carried in the attribute declaration message, and generates a resource reservation request message. The resource reservation request message carries the flow identifier and spanning tree identifier to make a resource reservation request, thereby establishing a redundant service protection path for the TSN service.

[0150] In order to better understand this application, Fig.13 and Fig.14 , describing a detailed flow chart of a method for reserving resources for redundant paths according to some other exemplary embodiments of the present application. Fig.13 A schematic diagram of a processing flow of redundant path resource reservation based on the SRP protocol according to an embodiment of the present application is shown; Fig.14 A schematic diagram of the processing flow of canceling redundant path resource reservation based on the SRP protocol according to an embodiment of the present application is shown.

[0151] exist Fig.13 In the figure, the TSN network may include five bridge devices (hereinafter referred to as bridges), such as TSN bridge 1, TSN bridge 2, TSN bridge 3, TSN bridge 4 and TSN bridge 5. Assume that a spanning tree corresponding to the primary spanning tree and a spanning tree corresponding to the backup spanning tree have been established in the TSN network, represented by line 1 and line 2, respectively, and the corresponding spanning tree identifiers are 1 and 2, respectively.

[0152] exist Fig.13 In the figure, Table 1 on the source (Talker) device shows the main fields of the source attribute declaration message, where the flow identifier is 1, indicating that resources are reserved for the service flow with the service flow identifier 1. As an example, the TSN service flow ID is {01:00:5e:01:01:01,2}, the redundancy field value is TRUE, indicating that the network needs to provide redundant propagation for it, and the spanning tree identifier field takes any value.

[0153] Talker sends a source attribute declaration message to TSN bridge 1. TSN bridge 1 receives the source attribute declaration message, extracts the message redundancy field as TRUE, copies a message, sets the spanning tree identification field of the original message to 1, sets the spanning tree identification field of the copied message to 2, sets the redundant fields of the two messages to FALSE, and registers the attribute information carried in the source attribute message at the port. Then, the original message is propagated along the spanning tree represented by line 1, and the copied message is propagated along the spanning tree represented by line 2.

[0154] When TSN bridges 2, 3, 4, and 5 receive the extended source attribute declaration message, they parse the message field content and find that the redundant field value is FALSE, then continue to extract the spanning tree identification field, and look up the spanning tree instance table shown in Table 2 according to the spanning tree identification field, and then propagate the message in the corresponding spanning tree.

[0155] The destination device (Listener) is interested in the service flow with flow ID 1, and receives two source attribute declaration messages with flow ID 1 successively. It extracts the spanning tree identification field of the message and constructs the corresponding destination resource reservation request messages respectively. The contents of the two destination resource reservation request messages are as follows: Fig.13 Table 3 and Fig.13 As shown in Table 4, and then sent out.

[0156] In this embodiment, the destination end needs to store the spanning tree identifier value corresponding to the received flow identifier in a table maintained by the node, such as the table next to the destination end device. Fig.13 As shown in Table 5 in , the spanning tree identifier set of the corresponding flow identifier maintained is obtained.

[0157] After receiving the destination resource reservation request message, each port of the bridge device starts to reserve bandwidth along the way and establish a forwarding table. If the same port receives two or more destination messages, it is necessary to avoid repeated resource reservation and forwarding table establishment.

[0158] For example, TSN bridge 4 and TSN bridge 5 both receive two destination messages, carrying spanning tree identifier 1 and spanning tree identifier 2 respectively. Taking port 2 of TSN bridge 4 as an example, when the first destination message is received, the message flow identifier is extracted to look up table 2. If the table entry is not hit, a forwarding table entry and reserved resources with {01:00:5e:01:01:01,2} as the key value are established, and then a table entry corresponding to port 2 and flow identifier is established in table 2, and the number of destination resource reservation requests is 1; when the second destination resource reservation request message is received, the message flow identifier is extracted, and it is found that the number of destination attribute registrations corresponding to port 2 and the flow identifier is greater than 0, then the resources are not reserved and the forwarding table entry is not established repeatedly, and only the number of corresponding destination resource reservation requests is increased by 1, and the number of resource reservation requests is 2.

[0159] In an embodiment of the present application, when the source device performs a flow cancellation operation, it is necessary to carry a redundant field and a spanning tree identification field in the attribute cancellation message. The processing flow of the bridge when receiving the source attribute cancellation message is similar to the processing flow of the redundant field and the spanning tree identification field when receiving the source attribute declaration message, and no further details are given.

[0160] exist Fig.14 In the example, the destination node maintains a spanning tree identification value corresponding to a flow identification of 1; each TSN bridge maintains the number of resource reservation requests corresponding to the flow identification received on each bridge port.

[0161] When the destination node device 1 initiates the cancellation of resource reservation corresponding to the flow ID 1, the destination node device 1 queries the flow ID and spanning tree ID mapping table and obtains that the spanning tree ID 1 and spanning tree ID 2 are included in the spanning tree ID value set. Fig.14 Table 1 in the figure is the spanning tree identifier corresponding to the flow identifier 1 maintained by the destination device. Fig.14 Table 2 is a spanning tree identifier corresponding to the flow identifier 2 maintained by the destination device. The destination device constructs a destination resource reservation cancellation message according to the spanning tree identifier 1 and the spanning tree identifier 2 in sequence.

[0162] When each bridge port receives a destination resource reservation cancellation message, it releases bandwidth resources along the way and deletes the corresponding forwarding table entries. In particular, when the number of destination resource reservation requests of the port is greater than or equal to 2, the reserved resources can be released only when the last cancellation message is received.

[0163] For example, when the spanning tree identification field value in the TSN bridge 4 port 2 received from the destination end message is 1, only Fig.14 In Table 3, the number of destination resource reservation requests corresponding to the flow identifier is reduced by 1; when the spanning tree identifier field value in the destination message is 2, the update Fig.14 In Table 3, the number of destination resource reservation requests corresponding to the flow identifier is reduced by 1. If it is found that the number of destination resource reservation requests corresponding to the S-ID is 0, the resources are released and the forwarding entry is deleted.

[0164] After the resource reservation is successfully revoked, Fig.14 As shown in Table 1 next to the destination node device 1, the flow identifier maintained in the destination node device 1 is 1 and the spanning tree identifier value set flow is NULL.

[0165] According to the resource reservation method for redundant paths in the embodiment of the present application, the source-end attribute declaration message is extended, and the redundant field and spanning tree identifier are carried in the extended attribute declaration message. The bridge port connected to the source end is used as an agent for the redundant path function, and the parsing of the redundant field is increased. When it is determined that the value of the redundant field indicates that the network needs to establish a redundant path for it, the source-end attribute declaration message is copied and modified, and the message is propagated in two different spanning tree instances according to the spanning tree identifiers carried by each, thereby establishing a redundant service protection path for the TSN service.

[0166] The following describes in detail a redundant path resource reservation device according to an embodiment of the present invention in conjunction with the accompanying drawings. Fig.15 FIG. 1 is a schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention. Fig.15 As shown, the resource reservation device for redundant paths can be applied to a source-end device and can include the following modules.

[0167] The attribute declaration message generation module 610 is used to generate a first attribute declaration message for the time sensitive network TSN service when it is determined that redundant path resource reservation is required for the TSN service. The first attribute declaration message carries an indication that redundant propagation needs to be provided for the attribute declaration message.

[0168] The attribute declaration message sending module 620 is used to send a first attribute declaration message to a bridge device connected to the source end device, wherein at least two spanning tree instances are maintained in the bridge device, and at least two spanning tree instances are used to establish a redundant path for the TSN service between the source end device and the specified destination end device according to the instructions of the first attribute declaration message.

[0169] In one embodiment, the attribute declaration message generation module 610 is further used to: generate a first attribute declaration message for a TSN service, wherein the first attribute declaration message carries a flow identifier for identifying the TSN service, redundant information having a first redundant information value, and a spanning tree identifier having an arbitrary identifier value. The first redundant information value is used to indicate that redundant propagation needs to be provided for the attribute declaration message, and the arbitrary identifier value is used to indicate the spanning tree instance on which the propagation of the first attribute declaration message is based.

[0170] In one embodiment, if it is determined that there is no need to reserve resources for redundant paths for the time-sensitive network TSN service, the attribute declaration message generation module 610 is also used to: generate a second attribute declaration message for the TSN service, carrying in the attribute declaration message a flow identifier for identifying the TSN service, redundant information having a second redundant information value, and a spanning tree identifier having a predetermined identifier value; wherein the second redundant information value is used to indicate that there is no need to provide redundant propagation for the attribute declaration message, and the predetermined identifier value is used to indicate the spanning tree instance on which the propagation of the second attribute declaration message is based.

[0171] According to the resource reservation module of the redundant path of the embodiment of the present application, the source-end device can parse the redundant information carried by the received attribute declaration message based on the SRP protocol. If the redundant information indicates that redundant propagation of the attribute declaration message is required and the number of corresponding spanning tree instances in the current bridge device is greater than a predetermined value, the attribute declaration message is copied and modified according to the corresponding spanning tree instance. The received attribute declaration message and the copied attribute generation message are propagated in the spanning tree instance indicated by the spanning tree identifier carried by each of them, thereby establishing a redundant service protection path for the TSN service.

[0172] Fig.16 FIG. 1 is a schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention. Fig.16 As shown, the resource reservation device for redundant paths can be applied to a bridge device and can include the following modules.

[0173] The attribute declaration message receiving module 710 is used to obtain, from the attribute declaration message received from the source device, the time-sensitive network TSN service targeted by the attribute declaration message, and an indication of whether redundant propagation needs to be provided for the attribute declaration message;

[0174] The attribute declaration message duplication module 720 is used to duplicate the attribute declaration message if it is indicated that redundant propagation needs to be provided for the attribute declaration message and the number of spanning tree instances maintained in the present bridge device is at least two;

[0175] The attribute declaration message propagation module 730 is used to propagate the received attribute declaration message and the copied attribute declaration message based on at least two spanning tree instances to establish a redundant path for the TSN service between the source end device and the destination end device;

[0176] The redundant path resource reservation module 740 is used to reserve redundant path resources for the TSN service in response to receiving a resource reservation request message for the TSN service from the destination device.

[0177] In one embodiment, the received attribute declaration message carries a flow identifier and redundant information; the attribute declaration message receiving module 710 is specifically used to: use the TSN service indicated by the flow identifier carried in the received attribute declaration message as the TSN service targeted by the attribute declaration message; if the redundant information value is the first redundant information value, it is determined that redundant propagation needs to be provided for the attribute declaration message; if the redundant information value is the second redundant information value, it is determined that redundant propagation does not need to be provided for the attribute declaration message, and the second redundant information value is different from the first redundant information value.

[0178] In one embodiment, the received attribute declaration message also carries a spanning tree identifier; the attribute declaration message propagation module 730 is specifically used to: modify the spanning tree identifier in the received attribute declaration message and the spanning tree identifier in the copied attribute declaration message to different spanning tree identifiers according to the spanning tree identifiers of at least two spanning tree instances obtained; modify the redundant information in the received attribute declaration message and the redundant information in the copied attribute declaration message to a second redundant information value; propagate the received attribute declaration message and the copied attribute declaration message in different spanning tree instances according to the modified different spanning tree identifiers to establish redundant paths for TSN services.

[0179] In one embodiment, if the indication is that redundant propagation needs to be provided for the attribute declaration message, and the number of spanning tree instances maintained in the current bridge device is less than two, then the attribute declaration message sending module 740 is specifically used to: set an indication that redundant propagation does not need to be provided for the received attribute declaration message, and propagate the received attribute declaration message based on a predetermined spanning tree instance in the spanning tree instance maintained by the current bridge device.

[0180] In this embodiment, the attribute declaration message sending module 740 is also specifically used to: set the spanning tree identifier carried in the received attribute declaration message to a predetermined identifier value, the predetermined identifier value is used to indicate a predetermined spanning tree instance; set the redundant information carried in the received attribute declaration message to a second redundant information value, the second redundant information value is used to indicate that there is no need to provide redundant propagation for the attribute declaration message; based on the predetermined spanning tree instance, propagate the attribute declaration message carrying the second redundant information value and the predetermined identifier value.

[0181] In one embodiment, if the indication is that redundant propagation of the attribute declaration message is not required, the attribute declaration message sending module 740 is further specifically used to: forward the received attribute declaration message based on the spanning tree instance indicated by the spanning tree identifier carried in the received attribute declaration message.

[0182] In one embodiment, the redundant path resource reservation device may further include: an attribute registration module, configured to register the attribute information included in the received attribute declaration message at the port of the bridge device receiving the attribute declaration message.

[0183] In one embodiment, the redundant path resource reservation module 740 is further used to receive a resource reservation request message from a destination device through a first port, the resource reservation request message carries a flow identifier and a spanning tree identifier, and the first port is any port among multiple ports of the present bridge device; if the bandwidth of the first port meets the predetermined bandwidth requirement and the first resource reservation request number is zero, bandwidth resources are reserved for the TSN service indicated by the flow identifier carried in the resource reservation request message and a forwarding table entry is established; wherein the first resource reservation request number is the number of resource reservation requests for the TSN service received through the first port and recorded in advance in the present bridge device.

[0184] In one embodiment, the resource reservation device of the redundant path may also include: a resource reservation request number updating module, which is used to add 1 to the record of the first resource reservation request number after reserving bandwidth resources for the TSN service indicated by the flow identifier and establishing a forwarding table entry, or when the bandwidth of the first port meets the predetermined bandwidth requirement and the first resource reservation request number is greater than or equal to 1, to obtain an updated first resource reservation request number; a resource reservation request message forwarding module, which is used to forward the resource reservation request message based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

[0185] In one embodiment, if the bandwidth of the first port does not meet the predetermined bandwidth requirement, the resource reservation request message forwarding module is further configured to forward the resource reservation request message based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

[0186] In one embodiment, the resource reservation device of the redundant path may further include: a resource reservation revocation message receiving module, which is used to receive a resource reservation revocation message from a destination device through a first port, wherein the resource reservation revocation message carries a flow identifier and a spanning tree identifier of a TSN service; a resource reservation request number updating module, which is also used to reduce the number of first resource reservation requests by 1 to obtain an updated first resource reservation request number; a resource reservation revocation message forwarding module, which is used to delete the forwarding entry of the TSN service and release the reserved bandwidth resources of the TSN service if the updated first resource reservation request number is zero, and forward the resource reservation revocation message according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation revocation message; and, if the updated first resource reservation request number is greater than or equal to 1, forward the resource reservation revocation message according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation revocation message.

[0187] According to the resource reservation module of the redundant path of the embodiment of the present application, the bridge device can parse the redundant information carried by the received attribute declaration message based on the SRP protocol. If the redundant information indicates that redundant propagation of the attribute declaration message is required and the number of corresponding spanning tree instances in the bridge device is greater than a predetermined value, the attribute declaration message is copied and modified according to the corresponding spanning tree instance. The received attribute declaration message and the copied attribute generation message are propagated in the spanning tree instance indicated by the spanning tree identifier carried by each, thereby establishing a redundant service protection path for the TSN service.

[0188] Fig.17 FIG. 1 is a schematic diagram showing the structure of a redundant path resource reservation device provided by an embodiment of the present invention. Fig.17 As shown, the redundant path resource reservation device can be applied to a destination device and can include the following modules.

[0189] The attribute declaration message receiving module 810 is used to receive at least two attribute declaration messages for the same time sensitive network TSN service through a bridge device connected to the destination device.

[0190] The resource reservation request generation module 820 is used to generate a resource reservation request message corresponding to a different spanning tree instance for each attribute declaration message received if the TSN service is a TSN service of interest to the destination device and each attribute declaration message received is a message propagated based on a different spanning tree instance.

[0191] The different spanning tree instances are spanning tree instances in at least two spanning tree instances maintained in a bridge device connected to the source device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source device and the destination device.

[0192] The resource reservation request sending module 830 is used to send each resource reservation request message to a bridge device connected to the destination device based on different spanning tree instances corresponding to each generated resource reservation request message.

[0193] In one embodiment, the resource reservation device for the redundant path may also include: an identification information acquisition module, which is used to obtain the flow identifier and spanning tree identifier carried in each attribute declaration message after receiving at least two attribute declaration messages for the same time-sensitive network TSN service, wherein the flow identifier is used to identify the TSN service, and the spanning tree identifier is used to indicate the spanning tree instance on which the propagation of the attribute declaration message in the bridge device is based.

[0194] In one embodiment, the resource reservation device for the redundant path may further include: an identification information adding module, which is used to carry a flow identifier for identifying the TSN service and a spanning tree identifier corresponding to different spanning tree instances in the resource reservation request message when generating a resource reservation request message corresponding to different spanning tree instances for the TSN service.

[0195] In one embodiment, the resource reservation device for the redundant path may also include: an identification information recording module, used to record the flow identifier and the corresponding spanning tree identifier carried in each received attribute declaration message, and the spanning tree identifier is used to indicate the spanning tree instance based on which the propagation of the attribute declaration message in the bridge device is based.

[0196] In one embodiment, the identification information adding module is further used to obtain the flow identification and the corresponding spanning tree identification of the TSN service from the pre-recorded flow identification and the corresponding spanning tree identification when determining that resources need to be revoked for the TSN service; the resource reservation device of the redundant path may also include: a resource revocation request generating module, used to generate a corresponding resource reservation revocation message for each spanning tree identification corresponding to the TSN service, the resource reservation revocation message carrying the flow identification of the TSN service and a spanning tree identification corresponding to the TSN service; a resource reservation revocation message sending module, used to send each resource reservation revocation message based on the spanning tree instance indicated by the spanning tree identification carried in each generated reservation revocation message; an information record updating module, used to delete predetermined information from the pre-recorded flow identification and the corresponding spanning tree identification, the predetermined information being the flow identification and the corresponding spanning tree identification carried in the sent resource reservation revocation message.

[0197] According to the resource reservation module of the redundant path of the embodiment of the present application, the destination device can extract the flow identifier and spanning tree identifier carried in the attribute declaration message based on the SRP protocol for the TSN service when receiving the attribute declaration message for the TSN service according to the resource reservation method of the redundant path, the destination node device and the storage medium of the embodiment of the present application, and generate a resource reservation request message, which carries the flow identifier and the spanning tree identifier to make a resource reservation request, thereby establishing a redundant service protection path for the TSN service.

[0198] It should be clear that the present invention is not limited to the specific configurations and processes described in the above embodiments and shown in the figures. For the convenience and brevity of description, a detailed description of the known methods is omitted here, and the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, which will not be repeated here.

[0199] Fig.18 It is a structural diagram showing an exemplary hardware architecture of a computing device capable of implementing the resource reservation method and apparatus for redundant paths according to an embodiment of the present invention.

[0200] like Fig.18 As shown, the computing device 900 includes an input device 901, an input interface 902, a central processing unit 903, a memory 904, an output interface 905, and an output device 906. The input interface 902, the central processing unit 903, the memory 904, and the output interface 905 are connected to each other via a bus 910, and the input device 901 and the output device 906 are connected to the bus 910 via the input interface 902 and the output interface 905, respectively, and then connected to other components of the computing device 900.

[0201] Specifically, the input device 901 receives input information from the outside and transmits the input information to the central processing unit 903 through the input interface 902; the central processing unit 903 processes the input information based on the computer executable instructions stored in the memory 904 to generate output information, temporarily or permanently stores the output information in the memory 904, and then transmits the output information to the output device 906 through the output interface 905; the output device 906 outputs the output information to the outside of the computing device 900 for user use.

[0202] In one embodiment, Fig.18 The computing device shown can be implemented as a source node device, which may include: a memory configured to store a program; a processor configured to run the program stored in the memory to execute the resource reservation method for redundant paths applied to the source node device described in the above embodiment.

[0203] In one embodiment, Fig.18 The computing device shown can be implemented as a bridge device, which may include: a memory configured to store a program; a processor configured to run the program stored in the memory to execute the resource reservation method for redundant paths applied to the bridge device described in the above embodiment.

[0204] In one embodiment, Fig.18 The computing device shown can be implemented as a destination node device, which may include: a memory configured to store a program; a processor configured to run the program stored in the memory to execute the resource reservation method for redundant paths applied to the destination node device described in the above embodiment.

[0205] The above is only an exemplary embodiment of the present application and is not intended to limit the scope of protection of the present application. In general, various embodiments of the present application can be implemented in hardware or special circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, a microprocessor or other computing device, although the present application is not limited thereto.

[0206] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0207] The block diagram of any logic flow in the accompanying drawings of the present application can represent program steps, or can represent interconnected logic circuits, modules and functions, or can represent a combination of program steps and logic circuits, modules and functions. The computer program can be stored on a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory device and system (digital versatile disc DVD or CD disc), etc. Computer-readable media may include non-transient storage media. The data processor can be 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.

[0208] By way of exemplary and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, but will not depart from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

1. A method for reserving resources for redundant paths, characterized in that: Applied to a network bridge device, the method comprises: Obtaining, from an attribute declaration message received from a source device, a time-sensitive network TSN service targeted by the attribute declaration message, and an indication of whether redundant propagation needs to be provided for the attribute declaration message; the attribute declaration message carries redundant information, and a redundant field value corresponding to the redundant information indicates whether redundant propagation needs to be provided for the attribute declaration message; If the indication is that redundant propagation needs to be provided for the attribute declaration message, and the number of spanning tree instances maintained in the present bridge device is at least two, then duplicating the attribute declaration message; Based on the at least two spanning tree instances, propagate the received attribute declaration message and the copied attribute declaration message to establish a redundant path for the TSN service between the source device and the destination device; In response to receiving a resource reservation request message for the TSN service from the destination device, resources of a redundant path are reserved for the TSN service.

2. The method according to claim 1, characterized in that The received attribute declaration message carries a flow identifier and redundant information; the step of obtaining, from the received attribute declaration message, a time-sensitive network TSN service targeted by the attribute declaration message and an indication of whether redundant propagation needs to be provided for the attribute declaration message includes: Using the TSN service indicated by the flow identifier carried in the received attribute declaration message as the TSN service targeted by the attribute declaration message; If the redundant information value is the first redundant information value, it is determined that redundant propagation needs to be provided for the attribute declaration message; If the redundant information value is a second redundant information value, it is determined that there is no need to provide redundant propagation for the attribute declaration message, and the second redundant information value is different from the first redundant information value.

3. The method according to claim 2, characterized in that The received attribute declaration message also carries a spanning tree identifier; the propagating the received attribute declaration message and the copied attribute declaration message based on the at least two spanning tree instances to establish a redundant path for the TSN service between the source device and the destination device includes: According to the obtained spanning tree identifiers of the at least two spanning tree instances, modifying the spanning tree identifier in the received attribute declaration message and the spanning tree identifier in the copied attribute declaration message to different spanning tree identifiers; modifying the redundant information in the received attribute declaration message and the redundant information in the copied attribute declaration message to the second redundant information value; The received attribute declaration message and the copied attribute declaration message are propagated in different spanning tree instances according to the modified different spanning tree identifiers to establish a redundant path for the TSN service.

4. The method according to claim 1, characterized in that: If the indication is that redundant propagation needs to be provided for the attribute declaration message, and the number of spanning tree instances maintained in the present bridge device is less than two, the method further includes: An indication that no redundant propagation is required for the received attribute declaration message is set, and the received attribute declaration message is propagated based on a predetermined spanning tree instance in the spanning tree instance maintained by the present bridge device.

5. The method according to claim 4, characterized in that The setting does not need to provide an indication of redundant propagation for the received attribute declaration message, and propagates the received attribute declaration message based on a predetermined spanning tree instance in the spanning tree instance maintained by the present bridge device, including: Setting the spanning tree identifier carried in the received attribute declaration message to a predetermined identifier value, wherein the predetermined identifier value is used to indicate the predetermined spanning tree instance; Setting the redundant information carried in the received attribute declaration message as a second redundant information value, where the second redundant information value is used to indicate that redundant propagation does not need to be provided for the attribute declaration message; Based on the predetermined spanning tree instance, an attribute declaration message carrying the second redundant information value and the predetermined identification value is propagated.

6. The method according to claim 1, characterized in that If the indication is that redundant propagation of the attribute declaration message is not required, the method further includes: The received attribute declaration message is forwarded based on the spanning tree instance indicated by the spanning tree identifier carried in the received attribute declaration message.

7. The method according to any one of claims 1 to 6, characterized in that Before propagating the received attribute declaration message and the copied attribute declaration message, the method further comprises: At the port where the attribute declaration message is received by the present bridge device, the attribute information contained in the received attribute declaration message is registered.

8. The method according to claim 1, characterized in that The step of reserving resources for a redundant path for the TSN service in response to receiving a resource reservation request message for the TSN service from a destination device includes: receiving a resource reservation request message from the destination device through a first port, wherein the resource reservation request message carries a flow identifier and a spanning tree identifier, and the first port is any port among multiple ports of the present bridge device; If the bandwidth of the first port meets the predetermined bandwidth requirement and the number of first resource reservation requests is zero, bandwidth resources are reserved for the TSN service indicated by the flow identifier carried in the resource reservation request message and a forwarding table entry is established; The first number of resource reservation requests is the number of resource reservation requests for the TSN service received through the first port and recorded in advance in the network bridge device.

9. The method according to claim 8, characterized in that After reserving bandwidth resources for the TSN service indicated by the flow identifier carried in the resource reservation request message and establishing a forwarding table entry, or when the bandwidth of the first port meets the predetermined bandwidth requirement and the number of first resource reservation requests is greater than or equal to 1, the method further includes: Add 1 to the record of the first resource reservation request number to obtain an updated first resource reservation request number; The resource reservation request message is forwarded based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

10. The method according to claim 8, characterized in that If the bandwidth of the first port does not meet the predetermined bandwidth requirement, the method further includes: The resource reservation request message is forwarded based on the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation request message.

11. The method according to any one of claims 8 to 10, characterized in that: The method further comprises: receiving a resource reservation cancellation message from the destination device through the first port, wherein the resource reservation cancellation message carries a flow identifier and a spanning tree identifier of the TSN service; Subtract 1 from the number of the first resource reservation requests to obtain an updated number of the first resource reservation requests; If the updated number of first resource reservation requests is zero, deleting the forwarding entry of the TSN service and releasing the reserved bandwidth resources of the TSN service, and forwarding the resource reservation cancellation message according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation cancellation message; If the updated first resource reservation request number is greater than or equal to 1, the resource reservation cancellation message is forwarded according to the spanning tree instance indicated by the spanning tree identifier carried in the resource reservation cancellation message.

12. A method for reserving resources for a redundant path, characterized in that: Applied to a source device, the method comprises: When it is determined that resources for a redundant path need to be reserved for a time-sensitive network TSN service, a first attribute declaration message for the TSN service is generated, wherein the first attribute declaration message carries an indication that redundant propagation needs to be provided for the attribute declaration message; the first attribute declaration message carries redundant information, and a redundant field value corresponding to the redundant information indicates whether redundant propagation needs to be provided for the first attribute declaration message; The first attribute declaration message is sent to a bridge device connected to the source end device, wherein at least two spanning tree instances are maintained in the bridge device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source end device and a specified destination end device according to the instructions of the first attribute declaration message.

13. The method according to claim 12, characterized in that The generating a first attribute declaration message for the TSN service, wherein the first attribute declaration message carries an indication that redundant propagation needs to be provided for the attribute declaration message, includes: Generate a first attribute declaration message for the TSN service, wherein the first attribute declaration message carries a flow identifier for identifying the TSN service, redundant information having a value of a first redundant information value, and a spanning tree identifier having a value of an arbitrary identifier value; wherein, The first redundant information value is used to indicate that redundant propagation needs to be provided for the attribute declaration message, and the arbitrary identification value is used to indicate a spanning tree instance on which propagation of the first attribute declaration message is based.

14. The method according to claim 12, characterized in that If it is determined that there is no need to reserve resources for redundant paths for the time sensitive network TSN service, the method further includes: Generate a second attribute declaration message for the TSN service, wherein the second attribute declaration message carries a flow identifier for identifying the TSN service, redundant information whose value is a second redundant information value, and a spanning tree identifier whose value is a predetermined identifier value; wherein, The second redundant information value is used to indicate that there is no need to provide redundant propagation for the second attribute declaration message, and the predetermined identification value is used to indicate the spanning tree instance on which the propagation of the second attribute declaration message is based.

15. A method for reserving resources for redundant paths, characterized in that: Applied to the destination device, the method further includes: At least two attribute declaration messages for the same time-sensitive network TSN service are received through a bridge device connected to the destination device; the attribute declaration message carries redundant information, and the redundant field value corresponding to the redundant information indicates whether redundant propagation needs to be provided for the attribute declaration message; If the TSN service is a TSN service of interest to the destination device, and each received attribute declaration message is a message propagated based on a different spanning tree instance, then for each received attribute declaration message, a resource reservation request message corresponding to the different spanning tree instance of the TSN service is generated; wherein the different spanning tree instance is a spanning tree instance in at least two spanning tree instances maintained in a bridge device connected to the source device, and the at least two spanning tree instances are used to establish a redundant path for the TSN service between the source device and the destination device; Based on different spanning tree instances corresponding to each generated resource reservation request message, each resource reservation request message is sent to the bridge device connected to the destination device.

16. The method according to claim 15, wherein: After receiving at least two attribute declaration messages for the same time-sensitive network TSN service, the method further includes: Obtaining a flow identifier and a spanning tree identifier carried in each of the attribute declaration messages, wherein the flow identifier is used to identify the TSN service, and the spanning tree identifier is used to indicate a spanning tree instance based on which the propagation of the attribute declaration message in the bridge device is based; And wherein, when generating a resource reservation request message corresponding to the different spanning tree instances for the TSN service, the method further comprises: carrying a flow identifier for identifying the TSN service and a spanning tree identifier corresponding to the different spanning tree instances in the resource reservation request message.

17. The method according to claim 15, characterized in that After sending the resource reservation request message to the bridge device connected to the destination device, the method further includes: The flow identifier and the corresponding spanning tree identifier carried in each received attribute declaration message are recorded, wherein the spanning tree identifier is used to indicate the spanning tree instance based on which the attribute declaration message is propagated in the bridge device.

18. The method according to any one of claims 15 to 17, characterized in that The method further comprises: When it is determined that resources of the TSN service need to be revoked, the flow identifier and the corresponding spanning tree identifier of the TSN service are obtained from pre-recorded flow identifiers and corresponding spanning tree identifiers; For each spanning tree identifier corresponding to the TSN service, a corresponding resource reservation cancellation message is generated respectively, wherein the resource reservation cancellation message carries the flow identifier of the TSN service and a spanning tree identifier corresponding to the TSN service; Send each resource reservation cancellation message based on the spanning tree instance indicated by the spanning tree identifier carried in each generated reservation cancellation message; The predetermined information is deleted from the pre-recorded flow identifier and the corresponding spanning tree identifier, where the predetermined information is the flow identifier and the corresponding spanning tree identifier carried in the sent resource reservation cancellation message.

19. A network device comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-11, any one of claims 12-14, or any one of claims 15-18.

20. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method of any one of claims 1 to 11, any one of claims 12 to 14, or any one of claims 15 to 18 is implemented.

Images