Method for protecting a service data stream based on a multi-medium channel

Abstract

The application discloses a service data flow protection method based on a multi-medium channel, and comprises the following steps: S1, forwarding plane multi-medium channel network topology sensing; S2, service multi-path planning of a control plane controller software based on the multi-medium channel; S3, switching of a protection path of a forwarding layer device based on the multi-medium channel; and S4, fault tunnel repairing of a control plane based on the multi-medium channel. The application can reduce the interruption risk of user service flow and improve the stability of a packet transmission network.

Description

Technical Field

[0001] This invention relates to optical communication technology, and more particularly to optical communication networks using PTN technology, specifically a service data stream protection method based on multi-media channels. Background Technology

[0002] PTN (Packet Transport Network) is a carrier-grade transport network based on packet switching technology. It employs the MPLS-TP protocol and utilizes key technologies such as hierarchical QoS mechanisms, OAM and protection switching, clock synchronization, and tagging and best path (LSP).

[0003] In PTN networks, while using multiple media channels (such as optical fiber, cable, microwave, etc.) to collaboratively transmit the same service data stream can improve network flexibility and redundancy, it also presents technical shortcomings and challenges, including the following issues: 1. Insufficient multi-media collaborative protection mechanisms pose a risk of service overflow. PTN typically employs a 1:1 protection mechanism. In multi-media scenarios, if the bandwidth planning of the primary channel (e.g., fiber optic) and the backup channel (e.g., microwave) does not consider the superimposed traffic, insufficient bandwidth in the backup channel may lead to service overflow.

[0004] 2. Differences in media characteristics can lead to protection failure. For example, microwave links are susceptible to interference, and electrical links have lower bandwidth. When the primary fiber optic cable is interrupted and the system switches to a lower bandwidth medium, high-priority services may experience packet loss.

[0005] 3. The PTN cross-media QoS guarantee mechanism is imperfect. Different media have significantly different transmission characteristics, making it difficult for PTN's hierarchical QoS strategy to coordinate priorities across media. In multi-media scenarios, traffic shaping strategies cannot dynamically adapt to bandwidth fluctuations across different media, potentially causing low-priority services to impact high-priority services during congestion.

[0006] 4. Business path optimization is difficult. Dynamic path calculation engines (such as SDN controllers) are rarely used in PTN, and manual configuration makes it difficult to achieve cross-media load balancing. Summary of the Invention

[0007] To overcome the aforementioned problems, this invention aims to provide a service data flow protection method based on multi-media channels. Through SDN controller software, it senses the network topology information of the multi-media channels, flexibly plans service paths based on the multi-media channels, repairs faulty paths, and reduces the risk of user service flow interruption. This method for protecting service data flows based on multi-media channels has the advantages of flexible configuration, fast switching speed, and strong service path optimization and repair capabilities.

[0008] To achieve the above objectives, the technical solution adopted by the present invention is as follows: A method for protecting service data streams based on multi-media channels includes the following steps: S1. Forwarding plane multi-media channel network topology awareness, including the following sub-steps: S1.1. Configure the basic physical ports of all forwarding plane devices for interconnection. Configure the medium channel type on each interconnected physical port so that ports with the same medium channel type can be physically interconnected. S1.2 All forwarding plane devices run the topology discovery protocol, which is used to build the network topology.

[0009] S1.3 Each forwarding plane device will propagate the direct link information of its directly connected devices to its surrounding directly connected devices; S1.4 After the link information is distributed throughout the network, each forwarding device has complete network topology information, and each link information uses a field to identify the medium channel type. S2. The controller plans multiple paths for services based on multi-media channels. These multiple paths are used to protect user service data streams, including the following sub-steps: S2.1 The controller obtains the network topology information from the forwarding plane device and identifies the link type between any two devices by using the medium channel type information contained in the network topology information. S2.2 The controller constructs a logical topology based on the link type. According to the medium channel type, a logical topology is constructed for each type of link. Any two logical topologies are logically isolated from each other. S2.3 The controller associates services and logical topologies of different priority levels. Services of different priorities use two logical topologies for path calculation. After association, when calculating service tunnel paths, the tunnel paths calculated by services of different priorities are only distributed on their associated logical topologies. S2.4 The controller calculates the tunnel path for the service based on the logical topology; S2.5 Before issuing tunnel configurations, the controller plans independent CIR / PIR, priority, and scheduling strategies for multiple bearer tunnels of the same service based on different medium channels. The controller assigns tunnel labels with different characteristics to each tunnel, which can be used by the device to identify the service flow and apply the corresponding QoS strategy.

[0010] Furthermore, the present invention also includes: when a fault occurs, step S3 is included after step S2: S3. The forwarding layer device performs protection path switching based on multi-media channels, including the following sub-steps: S3.1 If the forwarding layer equipment at both ends of the service tunnel continuously detects that the number of OAM alarm messages has reached a predetermined value, it is determined that a tunnel failure has occurred in the service. S3.2 The forwarding device on the service end performs tunnel path switching, switching from the working tunnel to the first priority protection tunnel. If the first priority protection tunnel fails, it switches to the second priority protection tunnel, and so on.

[0011] Preferably, in step S3, the working tunnel and each priority protection tunnel are distributed on different media channels, and the controller pre-plans and issues the tunnel's tag and QoS configuration.

[0012] Furthermore, when a fault occurs, step S4 is included after step S3: S4. The control plane repairs faulty tunnels based on multi-media channels, including the following sub-steps: S4.1 When a medium channel fails, the forwarding plane device associated with the failure updates its interconnection topology information with its neighboring devices and then spreads it to its neighboring devices, so that the updated network topology information is spread to every forwarding plane device. S4.2 The controller periodically queries the network topology data of the entire network. If it finds that a medium channel has been added, left, or its information has been updated, it generates a topology change event. At the same time, it updates all affected logical topologies to ensure that the updated logical topology is used when the tunnel path is repaired. S4.3 A topology change event or tunnel failure event triggers the controller to perform tunnel path repair. Tunnel path repair includes calculating a new tunnel to replace the faulty tunnel. The calculation of the new tunnel to replace the faulty tunnel includes one of the following two methods: Method 1: When all tunnels of the service fail, first calculate 1 tunnel, then delete the failed tunnel, and finally calculate the missing tunnels. Method 2: If normal tunnels exist, first delete the faulty tunnels, and then calculate the missing tunnels.

[0013] Preferably, in sub-step S2.3, the two logical topologies include one main logical topology and one sub-logical topology, and the main logical topology has a higher priority than the sub-logical topology.

[0014] Preferably, in sub-step S3.1, the preset value is 3.

[0015] Preferably, in Method 1, when performing tunnel calculations, the tunnels are still preferentially calculated on the main topology according to the priority of the services.

[0016] Preferably, in Method 2, the service is always protected by the initially planned number of tunnels and different media types.

[0017] Preferably, the medium channel type includes optical fiber link, electrical link and wireless link.

[0018] The beneficial effects of this invention are as follows: 1. This invention can reduce the risk of interruption of user service flow and improve the stability of packet transport network.

[0019] 2. This invention provides forwarding plane network topology awareness, which is based on the service data flow protection method of multi-media channels. The forwarding plane device collects the interconnection relationship between forwarding plane devices through the network topology discovery protocol, and identifies the physical links of different media between the devices. This information is encapsulated into topology information, and the subsequent control plane controller software uses this information to perform service multipath calculation.

[0020] 3. This invention provides control plane controller software for service multipath planning, which is the core of achieving service data flow protection across multiple media channels. By introducing channel factors into the port information of the device, corresponding logical topologies can be constructed based on the same physical topology and according to the media channel type. Calculating service tunnel paths based on the logical topology enables physical isolation of service flows.

[0021] 4. In the event of a fault, the forwarding layer devices switch protection paths. This multi-path protection switching by the forwarding layer devices is crucial for protecting service data streams across multiple media channels. Protection at the device level can achieve millisecond-level protection.

[0022] 5. In the event of a fault, the control plane repairs the faulty paths. The controller software performs fault repair based on the logical topology. It determines which logical topologies the service tunnel paths were created on and on which these tunnels repair is performed. Priority is given to repairing service flows with all faulty tunnels, and, where network link resources are available, as many tunnel paths as possible are restored. Attached Figure Description

[0023] Figure 1 The core flowchart of the service data flow protection method based on multi-media channels Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Example 1

[0025] This embodiment discloses a service data stream protection method based on multi-media channels, specifically as follows: Figure 1 As shown, it includes the following steps: (1) Forwarding plane multi-media channel network topology awareness, including the following steps: (1-1) Perform basic configuration on the interconnected physical ports of all forwarding plane devices. Configure the media channel type on each interconnected physical port, and only ports with the same media channel type are physically interconnected.

[0026] (1-2) All forwarding plane devices run a topology discovery protocol, which is used to construct the whole network topology.

[0027] (1-3) Each forwarding plane device spreads the direct link information between itself and its directly connected devices to the directly connected devices around it.

[0028] After the link information spreads across the whole network, each forwarding device has the complete whole network topology information. A field is used in each link information to identify the media channel type.

[0029] (2) The control plane controller software performs service multi-path planning based on multi-media channels, including the following steps: The control plane controller software plans multiple paths for services based on multi-media channels to achieve the purpose of protecting user service data streams. The process is described as follows: (2-1) The controller software obtains the whole network topology information from the forwarding plane devices, and identifies the link types (including optical fiber, microwave, electrical link, etc.) between any two devices through the media channel type information contained in the whole network topology information; (2-2) The controller software constructs a logical topology according to the link types. Classified by the media channel type, all optical fiber links construct a logical topology, all electrical links construct a logical topology, and so on. Finally, the controller software constructs a logically isolated topology for each type of link.

[0030] (2-3) The controller software associates services with different priority levels with the logical topology, that is, services with different priorities use two logical topologies (one main topology and one secondary topology) for path calculation. After association, when calculating the service tunnel path, the tunnel paths calculated by services with different priorities are only distributed on their associated logical topologies.

[0031] (2-4) The controller software calculates the service tunnel path based on the logical topology. Assume that a total of N tunnels are calculated. In an ideal situation: N-1 tunnels are calculated on the main topology and 1 tunnel is calculated on the secondary topology. If M paths (M < N-1) are calculated on the main topology, then try to calculate the remaining N-M on the secondary topology.

[0032] (2-5) Before issuing tunnel configurations, the controller software plans independent CIR / PIR, priority, and scheduling strategies for multiple bearer tunnels of the same service based on different medium channels. The controller assigns tunnel labels with different characteristics to each tunnel, which can be used by the equipment to identify the service flow and apply the corresponding QoS strategy.

[0033] (3) In the event of a fault, the forwarding layer device switches the protection path based on the multi-media channel (at the millisecond level), including the following steps: (3-1) If the forwarding layer equipment at both ends of the service tunnel detects OAM alarm messages three times in a row, the tunnel of the service is identified as faulty. (3-2) If the working tunnel fails, the forwarding device on the service end will switch the tunnel path from the working tunnel to the first priority protection tunnel. If the first priority protection tunnel fails, it will switch to the second priority protection tunnel, and so on.

[0034] (3-3) At the physical level, multiple service bearer tunnels are distributed on different media channels. By pre-planning and issuing tunnel labels and QoS configurations through controller software, when a service tunnel fails, the service traffic can be switched on different media at the millisecond level based on the equipment.

[0035] (4) After a fault occurs, the control plane repairs the faulty tunnel based on the multi-media channel, including the following steps: (4-1) When a medium channel fails, the forwarding plane device associated with the failure updates its interconnection topology information with its neighboring devices and then propagates it to its neighboring devices. After a period of time, the latest network topology information is propagated to every forwarding plane device.

[0036] (4-2) The controller software periodically queries the network topology data of the entire network. If it finds that a medium channel has been added, left, or its information has been updated, it generates a topology change event. At the same time, it updates all affected logical topologies to ensure that the latest logical topology is used when repairing tunnel paths.

[0037] (4-3) Topology change events or tunnel failure events trigger the controller software to perform tunnel path repair. The core task of tunnel path repair is to calculate a new tunnel to replace the faulty tunnel.

[0038] (4-4) If all tunnels of a service fail (assuming a total of N tunnels), first calculate one tunnel, then delete the failed tunnels (N tunnels), and finally calculate the missing tunnels (N-1 tunnels). When calculating tunnels, based on the service priority, tunnels are still preferentially calculated on the main topology.

[0039] (4-5) If normal tunnels exist, delete the faulty tunnels first, and then calculate the missing tunnels to ensure that the service is always protected by the initial planned number of tunnels and different media types. Example 2

[0040] Building upon Example 1, this example discloses an application instance in a multi-media channel PTN network. Protecting service data flows based on multi-media channels may encounter issues such as slow handover speeds, difficulties in QoS scheduling, service path optimization, and repair. By using SDN controller software to perceive the network topology information of the multi-media channels, service paths can be flexibly planned and tunnel faults repaired based on the multi-media channels. QoS policy management and scheduling are performed at the tunnel level, reducing the risk of user service flow interruption. Specifically: (1) Forwarding plane multi-media channel network topology awareness, including the following steps: (1-1) Configure the medium channel type for the NNI ports of all devices in the PTN network. For example, for fiber optic links (where the eth-0-1 ports of device A and device B are connected), if the channel medium type (channel_type) is defined as 1, then configure the medium channel type as 1 on the eth-0-1 ports of both device A and device B. For other types of links, configure the medium channel type according to this rule.

[0041] (1-2) Run the topd process for all devices in the PTN network. This process implements the topology discovery protocol and provides a topology query interface for the controller software.

[0042] (1-3) Link Information Diffusion. For example, devices A are directly connected to B and F; B is directly connected to A, C, and E; C is directly connected to B and D; D is directly connected to C and E; E is directly connected to B, D, and F; and F is directly connected to A and E. Then A will send the link information of AB and AF to devices B and F, and B will send the link information of BA, BC, and BE to devices A, E, and C. And so on.

[0043] (1-4) Link Information Integration. Based on the device interconnection relationships in (1-3), each device integrates the information received from the directly connected devices, ultimately obtaining the network-wide connection relationships as follows: AB, BC, CD, DE, EF, AF, and BE. For each of the above links, the link information includes a channel_type field, which is only reflected on the source device.

[0044] (2) The control plane controller software performs service multipath planning based on multi-media channels, including the following steps: The control plane controller software, based on multi-media channels, plans multiple paths for services. These multiple paths aim to protect user service data flows. The process is described below: (2-1) The controller software acquires topology information and identifies link types. For example, the link information queried by the controller is: {"src":{"device_ip":10.5.0.1,"interface":"eth-0-1","channel_type":1},"dest":{"device_ip":10.6.0.1,"interface":"eth-0-1"}, {"src":{"device_ip":10.5.0.1,"interface":"eth-0-2","channel_type":2},"dest":{"device_ip":10.6.0.1,"interface":"eth-0-2"} {"src":{"device_ip":10.5.0.1,"interface":"eth-0-3","channel_type":3},"dest":{"device_ip":10.6.0.1,"interface":"eth-0-3"} {"src":{"device_ip":10.6.0.1,"interface":"eth-0-4","channel_type":1},"dest":{"device_ip":10.7.0.1,"interface":"eth-0-4"}, {"src":{"device_ip":10.6.0.1,"interface":"eth-0-5","channel_type":2},"dest":{"device_ip":10.7.0.1,"interface":"eth-0-5"} {"src":{"device_ip":10.6.0.1,"interface":"eth-0-6","channel_type":3},"dest":{"device_ip":10.7.0.1,"interface":"eth-0-6"} The controller identifies the link between the eth-0-1 interfaces of devices 10.5.0.1 and 10.6.0.1 as a fiber optic link, the link between the eth-0-2 interfaces as an electrical link (channel_type is defined as 2), and the link between the eth-0-3 interfaces as a wireless link (channel_type is defined as 3). Similarly, the link between the eth-0-4 interfaces of devices 10.6.0.1 and 10.7.0.1 is a fiber optic link, the link between the eth-0-5 interfaces is an electrical link, and the link between the eth-0-6 interfaces is a wireless link.

[0045] (2-2) Constructing the logical topology. Based on the link information identified by the controller in step (2-1), the controller constructs logical topology 1: 10.5.0.1 / eth-0-1 to 10.6.0.1 / eth-0-1, 10.6.0.1 / eth-0-4 to 10.7.0.1 / eth-0-4; logical topology 2: 10.5.0.1 / eth-0-2 to 10.6.0.1 / eth-0-2, 10.6.0.1 / eth-0-5 to 10.7.0.1 / eth-0-5; logical topology 3: 10.5.0.1 / eth-0-3 to 10.6.0.1 / eth-0-3, 10.6.0.1 / eth-0-6 to 10.7.0.1 / eth-0-6.

[0046] (2-3) Business and logical topology association. Business 1 (high priority) is associated with logical topology 1 (primary topology) and logical topology 3 (secondary topology), and business 2 (low priority) is associated with logical topology 2 (primary topology) and topology 3 (secondary topology). When business 1 calculates the tunnel path, the path is distributed on logical topology 1 and logical topology 3; when business 2 calculates the tunnel path, the path is distributed on logical topology 1 and logical topology 3.

[0047] (2-4) Calculation of service tunnel paths. If three tunnels are to be calculated, for service 1, the controller should calculate two tunnels on logical topology 1 and one on logical topology 3. For service 2, the controller should calculate two tunnels on logical topology 2 and one on logical topology 3. If only one tunnel can be calculated on logical topology 1 or logical topology 2, then the controller should calculate two tunnels on logical topology 3.

[0048] (2-5) QoS policy planning. For tunnels calculated on logical topology 1, configure a larger CIR / PIR value (e.g., CIR=300M), higher priority, and a label range assigned to the tunnel (e.g., 50-2000); for tunnels calculated on logical topology 3, configure a smaller CIR / PIR value (e.g., CIR=3M), lower priority, and a label range assigned to the tunnel (e.g., 4001-6000).

[0049] (3) In the event of a fault, the forwarding layer device switches the protection path based on the multi-media channel (at the millisecond level), including the following steps: (3-1) Tunnel Fault Detection. For example, if service A is device 10.1.0.1 and service Z is device 10.2.0.1, device 10.1.0.1 periodically sends CV frames. If device 10.2.0.1 does not receive them for 3 periods, it triggers a LOC alarm, indicating a tunnel fault.

[0050] (3-2) Tunnel switching. For example, the working tunnel between service A and service Z is LSP1, and LSP2 and LSP3 are the first and second protection tunnels. When the working tunnel fails, the device at service A sends an APS data frame to the device at service Z, the status of service A and service Z is synchronized, the service traffic is switched to LSP2, and the QoS policy of LSP2 tunnel is used.

[0051] (3-3) Physical Layer Medium Channel Switching. For example, the three tunnels between service A and service Z are LSP1 (working tunnel), LSP2 (first protection tunnel), and LSP3 (second protection tunnel). LSP1 is carried on an optical physical channel, LSP2 on an electrical physical channel, and LSP3 on a wireless physical channel. When a service tunnel fails, the service A and Z devices synchronize APS data frames, and the devices automatically switch service traffic at the millisecond level.

[0052] (4) After a fault occurs, the control plane repairs the faulty tunnel based on the multi-media channel, including the following steps: (4-1) Network Topology Information Update. For example, the current normal network connections are as follows: devices A and B, F are directly connected; B and A, C, E are directly connected; C and B, D are directly connected; D and C, E are directly connected; E and B, D, F are directly connected; and F and A, E are directly connected. Any two directly connected devices are connected via three types of media channels: optical, electrical, and wireless. If the optical link between A and B is broken, the electrical link between C and B fails, and a wireless link is added between D and C, then all devices will update their topology information: the optical link between A and B will disappear, the electrical link between C and B will disappear, and a new wireless link will be added between D and C.

[0053] (4-2) Controller updates logical topology. For the link changes in step (4-1), the controller software detects them after one polling cycle. The controller software updates logical topology 1 (mapping optical link), and the edge between devices A and B is removed from logical topology 1; updates logical topology 2 (mapping electrical link), and the edge between devices C and B is removed from logical topology 2; updates logical topology 3 (mapping wireless link), and adds the edge between D and C in logical topology 3.

[0054] (4-3) Fault Tunnel Repair. For the link changes mentioned in step (4-1), step (4-2) describes the process of controller awareness and logical topology update. The controller initiates the tunnel repair process. The service between devices A and C has a faulty working tunnel, requiring repair; the first protection tunnel also has a fault, requiring repair.

[0055] (4-4) Tunnel Repair (Full Failure). If there are 3 tunnels for services between devices A and C, and all 3 tunnels fail, in the first stage of tunnel repair, calculate 1 tunnel first (preferably in the optical logical topology). In the second stage, delete the failed tunnel. In the third stage, calculate a new tunnel (preferably in the optical logical topology). If a normal tunnel exists, delete the failed tunnel in the second stage and calculate the missing tunnel in the third stage, still prioritizing the calculation of the tunnel in the main topology.

[0056] (4-5) Tunnel Repair (Partial Failure). If the number of tunnels for the service between devices A and C is 3, when 2 tunnels fail, in the second stage, the 2 failed tunnels are deleted first, and in the third stage, the 2 missing tunnels are calculated.

[0057] Of course, the present invention may have other various embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various corresponding changes and modifications according to the present invention, but these corresponding changes and modifications should all fall within the protection scope of the appended claims.

Claims

1. A method for protecting service data streams based on multi-media channels, characterized in that, Includes the following steps: S1. Forwarding plane multi-media channel network topology awareness, including the following sub-steps: S1.

1. Configure the basic physical ports of all forwarding plane devices for interconnection. Configure the medium channel type on each interconnected physical port so that ports with the same medium channel type can be physically interconnected. S1.2 All forwarding plane devices run the topology discovery protocol, which is used to build the network topology. S1.3 Each forwarding plane device will propagate the direct link information of its directly connected devices to its surrounding directly connected devices; S1.4 After the link information is distributed throughout the network, each forwarding device has complete network topology information, and each link information uses a field to identify the medium channel type. S2. The controller plans multiple paths for services based on multi-media channels. These multiple paths are used to protect user service data streams, including the following sub-steps: S2.1 The controller obtains the network topology information from the forwarding plane device and identifies the link type between any two devices by using the medium channel type information contained in the network topology information. S2.2 The controller constructs a logical topology based on the link type. According to the medium channel type, a logical topology is constructed for each type of link. Any two logical topologies are logically isolated from each other. S2.3 The controller associates services and logical topologies of different priority levels. Services of different priorities use two logical topologies for path calculation. After association, when calculating service tunnel paths, the tunnel paths calculated by services of different priorities are only distributed on their associated logical topologies. S2.4 The controller calculates the tunnel path for the service based on the logical topology; S2.5 Before issuing tunnel configurations, the controller plans independent CIR / PIR, priority, and scheduling strategies for multiple bearer tunnels based on different media channels for the same service. The controller assigns tunnel labels with different characteristics to each tunnel, which allows the device to identify service flows and apply the corresponding QoS policies.

2. The service data stream protection method based on multi-media channels according to claim 1, characterized in that, When a fault occurs, step S3 is included after step S2: S3. The forwarding layer device performs protection path switching based on multi-media channels, including the following sub-steps: S3.1 If the forwarding layer equipment at both ends of the service tunnel continuously detects that the number of OAM alarm messages has reached a predetermined value, it is determined that a tunnel failure has occurred in the service. S3.2 The forwarding device on the service end performs tunnel path switching, switching from the working tunnel to the first priority protection tunnel. If the first priority protection tunnel fails, it switches to the second priority protection tunnel, and so on.

3. The service data stream protection method based on multi-media channels according to claim 2, characterized in that, In step S3, the working tunnel and each priority protection tunnel are distributed on different media channels, and the controller pre-plans and issues the tunnel's tag and QoS configuration.

4. The service data stream protection method based on multi-media channels according to claim 2 or 3, characterized in that, When a fault occurs, step S4 is included after step S3: S4. The control plane repairs faulty tunnels based on multi-media channels, including the following sub-steps: S4.1 When a medium channel fails, the forwarding plane device associated with the failure updates its interconnection topology information with its neighboring devices and then spreads it to its neighboring devices, so that the updated network topology information is spread to every forwarding plane device. S4.2 The controller periodically queries the network topology data of the entire network. If it finds that a medium channel has been added, left, or its information has been updated, it generates a topology change event. At the same time, it updates all affected logical topologies to ensure that the updated logical topology is used when the tunnel path is repaired. S4.3 A topology change event or tunnel failure event triggers the controller to perform tunnel path repair. Tunnel path repair includes calculating a new tunnel to replace the faulty tunnel. The calculation of the new tunnel to replace the faulty tunnel includes one of the following two methods: Method 1: When all tunnels of the service fail, first calculate 1 tunnel, then delete the failed tunnel, and finally calculate the missing tunnels. Method 2: If normal tunnels exist, first delete the faulty tunnels, and then calculate the missing tunnels.

5. The service data stream protection method based on multi-media channels according to claim 1, characterized in that, In sub-step S2.3, the two logical topologies include one main logical topology and one sub-logical topology, with the main logical topology having a higher priority than the sub-logical topology.

6. The service data stream protection method based on multi-media channels according to claim 2, characterized in that, In sub-step S3.1, the preset value is 3.

7. The service data stream protection method based on multi-media channels according to claim 4, characterized in that, In Method 1, when calculating tunnels, the tunnels are still preferentially calculated on the main topology based on the priority of the services.

8. The service data stream protection method based on multi-media channels according to claim 4, characterized in that, In Method 2, the service is always protected by the initially planned number of tunnels and different media types.

9. The service data stream protection method based on multi-media channel according to claim 1, characterized in that, The media channel types include fiber optic links, electrical links, and wireless links.

Images