Service switching method, device and equipment and readable storage medium

Abstract

A service switching method, apparatus and device, and a readable storage medium, the service switching method comprising: in each protection period, for each disk, when the disk as an entrance disk receives multicast traffic from a self-contained root node, receiving multicast traffic from the entrance disk; judging whether a machine disc which is used as an entrance machine disc to receive the multicast flow from the main root node exists in the distributed equipment or not; if the machine disk which is used as the entrance machine disk to receive the multicast flow from the main root node exists, discarding the received multicast flow from the standby root node; and if the machine disk which is used as the entrance machine disk to receive the multicast traffic from the main root node does not exist, forwarding the received multicast traffic from the standby root node to an exchange network of the distributed equipment. Through the application, compared with switching after detecting the link state based on an IGP protocol, the service switching time can be greatly shortened, BFD for BIER does not need to be used, and the compatibility problem of equipment intercommunication is avoided.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a service switching method, apparatus, device, and readable storage medium. Background Art

[0002] Large video services such as short videos, TV live broadcasts, high-definition video on demand, and virtual reality are the main application scenarios of the carrier network of operators. One of the key technologies for these video services is the multicast technology of carrier network devices and the protection technology for multicast services. Only with sufficient efficient packet replication capabilities and sufficiently fast protection switching times can smooth high-definition video playback be supported.

[0003] BIER (Bit Index Explicit Replication) is a new type of multicast technology aimed at solving the problems of large network traffic consumption and low processing efficiency caused by the multicast tree state in traditional multicast technologies. Refer to Figure 1 , Figure 1 is a schematic diagram of a typical network model for BIER dual-root protection. As shown in Figure 1 , the multicast traffic is forwarded along both the primary and backup links simultaneously. When the link is normal, the leaf node PE1 will preferentially receive the traffic of the primary tunnel with the primary root node Root1 as the BFIR (Bit Forwarding Ingress Router) and discard the traffic of the backup tunnel with the backup root node Root2 as the BFIR. When the primary root node Root1 or the primary tunnel link fails, the leaf node PE1 will switch to receiving the traffic of the backup tunnel with the backup root node Root2 as the BFIR, thereby realizing the protection switching of the multicast service.

[0004] Currently, tunnel path failures are usually detected based on IGP (Internal Gateway Protocol) or BFD (Bidirectional Forwarding Detection) for BIER, and then service switching is performed when a failure is detected. However, when detecting the reachability of the service path based on IGP, the service switching time reaches the second level, and the service switching time in the scenario of root node failure is even up to half a minute. Although BFD for BIER can achieve millisecond-level fault detection, thus significantly shortening the service switching time, BFD for BIER is still in the draft stage, and there are interoperability problems among devices of different manufacturers.

[0005] In summary, in the current BIER dual-root protection network, the protection switching efficiency based on IGP is low, and there are application obstacles to the protection switching based on BFD for BIER. Summary of the Invention

[0006] The present application provides a service switching method, apparatus, device and readable storage medium, aiming to solve the technical problems that in the current BIER dual-root protection network, the protection switching efficiency based on IGP is low, and there are application obstacles for the protection switching based on BFD for BIER.

[0007] In a first aspect, an embodiment of the present application provides a service switching method, which is applied to a leaf node of a dual-root protection network. The leaf node is a distributed device, and the distributed device includes multiple chassis. The service switching method includes:

[0008] In each protection period, for each chassis, when the chassis receives multicast traffic from a standby root node as an ingress chassis, it is determined whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis;

[0009] If there is a chassis that receives multicast traffic from a primary root node as an ingress chassis, the received multicast traffic from the standby root node is discarded;

[0010] If there is no chassis that receives multicast traffic from a primary root node as an ingress chassis, the received multicast traffic from the standby root node is forwarded to the switching fabric of the distributed device.

[0011] Optionally, the step of when the chassis receives multicast traffic from a standby root node as an ingress chassis and determining whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis includes:

[0012] When the chassis receives multicast traffic from a standby root node as an ingress chassis, it is determined whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis according to the first traffic label and the second traffic label of the chassis;

[0013] Wherein, the first traffic label of each chassis is marked when the chassis receives multicast traffic from a primary root node as an ingress chassis, the second traffic label of each chassis is updated according to the first traffic label sent by other chassis when the chassis receives the first traffic label sent by other chassis, and after each chassis sends the first traffic label to other chassis, the first traffic label and the second traffic label of the chassis are unmarked.

[0014] Optionally, the duration of the protection period is determined according to the duration of canceling all traffic labels, the duration of setting the first traffic label, and the duration of updating the second traffic label.

[0015] Optionally, each circuit board includes a chip, and the protection period duration is determined according to the duration of canceling all traffic markings, the duration of setting the first traffic marking, and the duration of updating the second traffic marking, including:

[0016] Calculate the duration of canceling all traffic markings based on the number of all traffic markings, the chip processing performance, and the performance ratio allocated to canceling traffic markings;

[0017] Calculate the duration of setting the first traffic marking based on the number of the first traffic markings on the circuit board and the multicast traffic ingress peak value;

[0018] Calculate the duration of updating the second traffic marking based on the number of the first traffic markings on the circuit board, the chip processing performance, and the performance ratio allocated to forwarding the first traffic marking;

[0019] Sum up the duration of canceling all traffic markings, the duration of setting the first traffic marking, and the duration of updating the second traffic marking to calculate the protection period duration.

[0020] Optionally, before calculating the duration of setting the first traffic marking based on the number of the first traffic markings on the circuit board and the multicast traffic ingress peak value, it includes:

[0021] Calculate the multicast traffic ingress peak value based on the circuit board slot bandwidth stability threshold, the chip processing performance, and the performance ratio allocated to canceling traffic markings.

[0022] Optionally, the sum of the performance ratio allocated to canceling traffic markings and the performance ratio allocated to forwarding the first traffic marking is 1. Before determining whether there is a circuit board that receives multicast traffic from the master root node as an ingress circuit board in the distributed device when each circuit board receives multicast traffic from the standby root node as an ingress circuit board in each protection period, it includes:

[0023] Conduct experiments on the dual-root protection network by adjusting the performance ratio allocated to canceling traffic markings and the performance ratio allocated to forwarding the first traffic marking to obtain the corresponding relationship between different protection period durations and performance ratios;

[0024] Determine the optimal value range of the performance ratio according to the corresponding relationship between different protection period durations and performance ratios.

[0025] Optionally, after the each circuit board sends the first traffic marking to other circuit boards, the operation of canceling the marking of the first traffic marking and the second traffic marking of the circuit board includes:

[0026] Count the number of cycles of the protection period. When the number of cycles is an even multiple, after each chassis sends the first traffic label to other chassis, it performs an unlabeling operation on the first traffic label and the second traffic label of the chassis.

[0027] In a second aspect, an embodiment of the present application provides a service switching device, which is applied to a leaf node of a dual-root protection network. The leaf node is a distributed device, and the distributed device includes multiple chassis. The service switching device includes:

[0028] A judgment module, configured to, in each protection period, for each chassis, when the chassis receives multicast traffic from a standby root node as an ingress chassis, judge whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis;

[0029] A discard module, configured to, if there is a chassis that receives multicast traffic from a primary root node as an ingress chassis, discard the received multicast traffic from the standby root node;

[0030] A switching module, configured to, if there is no chassis that receives multicast traffic from a primary root node as an ingress chassis, forward the received multicast traffic from the standby root node to the switching fabric of the distributed device.

[0031] In a third aspect, an embodiment of the present application provides a service switching device. The service switching device includes a processor, a memory, and a service switching program stored on the memory and executable by the processor. When the service switching program is executed by the processor, the steps of the service switching method as described above are implemented.

[0032] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a service switching program is stored. When the service switching program is executed by a processor, the steps of the service switching method as described above are implemented.

[0033] The beneficial effects brought by the technical solution provided by the embodiment of the present application include:

[0034] In the embodiments of the present application, in each protection period, for each chassis, when the chassis receives multicast traffic from the standby root node as an ingress chassis, it is determined whether there is a chassis in the distributed device that receives multicast traffic from the primary root node as an ingress chassis; if there is a chassis that receives multicast traffic from the primary root node as an ingress chassis, the received multicast traffic from the standby root node is discarded; if there is no chassis that receives multicast traffic from the primary root node as an ingress chassis, the received multicast traffic from the standby root node is forwarded to the switching fabric of the distributed device. Through the embodiments of the present application, for the case where the leaf nodes of the BIER dual-root protection network are distributed devices, each chassis of the distributed device can receive multicast traffic from the primary root and / or standby root nodes as an ingress chassis. When the multicast traffic link of the primary root node is normal, the primary root traffic is preferentially selected and the standby root traffic is discarded. When the multicast traffic link of the primary root node fails, the standby root traffic is selected. Therefore, for the case where each chassis receives multicast traffic from the standby root node as an ingress chassis, it is determined whether there is a chassis in the distributed device that receives multicast traffic from the primary root node as an ingress chassis, and then it is decided whether to discard the standby root traffic or forward the standby root traffic. Thus, for the case where the distributed device has multiple chassis, rapid detection of primary root traffic failures and rapid switching of standby root traffic can be performed within the protection period. Compared with the method of detecting the link state based on the IGP protocol and then performing a switchover, the service switchover duration can be greatly shortened, and there is no need to use BFD for BIER, avoiding the compatibility problem of device intercommunication. Description of the Drawings

[0035] Figure 1 It is a schematic diagram of a typical network model for BIER dual-root protection;

[0036] Figure 2 It is a schematic flowchart of an embodiment of the service switchover method of the present application;

[0037] Figure 3 It is a schematic diagram of the disk traffic marking of an embodiment of the service switchover method of the present application;

[0038] Figure 4 It is a schematic diagram of cross-disk forwarding of the local primary root traffic marking table of an embodiment of the service switchover method of the present application;

[0039] Figure 5 It is a schematic diagram of the corresponding relationship between different protection period durations and performance ratios of an embodiment of the service switchover method of the present application;

[0040] Figure 6 It is a schematic diagram of the functional modules of an embodiment of the service switchover device of the present application;

[0041] Figure 7This is a schematic diagram of the hardware structure of the service switching device involved in the solution of the embodiment of the present application. Detailed implementation manners

[0042] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0043] To make the purpose, technical solution and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0044] In a first aspect, an embodiment of the present application provides a service switching method.

[0045] In one embodiment, it is applied to a leaf node of a dual-root protection network. The leaf node is a distributed device, and the distributed device includes multiple chassis. Refer to Figure 2 , Figure 2 This is a schematic flowchart of an embodiment of the service switching method of the present application. As Figure 2 shown, the service switching method includes:

[0046] Step S10, in each protection period, for each chassis, when the chassis receives multicast traffic from the standby root node as an ingress chassis, determine whether there is a chassis in the distributed device that receives multicast traffic from the primary root node as an ingress chassis.

[0047] In this embodiment, it is applied to the leaf nodes of a dual-root protection network. The leaf nodes are distributed devices. When the link is normal, the upstream multicast traffic is sent to the distributed devices through two links of the primary root node and the standby root node respectively, corresponding to the primary root traffic and the standby root traffic. The distributed device includes a chassis, and the chassis includes multiple slots. One disk is inserted into one slot. Any disk can be used as an ingress disk or an egress disk. The disk that receives the multicast traffic is the ingress disk, and the egress disk forwards the multicast traffic to the next network node. Taking the protection period duration as T as an example, that is, the failure detection of the primary root traffic is performed within each period of duration T. If the primary root traffic failure is detected, the standby root traffic is switched to; otherwise, the primary root traffic is preferentially forwarded and the standby root traffic is discarded. For each disk of the distributed device, when the disk receives the multicast traffic as an ingress disk, the BIER header of the multicast packet of the multicast traffic can be parsed to obtain the multicast traffic ID and determine whether the multicast traffic is from the primary root node or the standby root node. If the multicast traffic is from the primary root node, it means that the primary root traffic has no failure and no further detection and judgment are required. At this time, the primary root traffic is preferentially forwarded, that is, the multicast traffic from the primary root node is forwarded to the switching network of the distributed device. If the multicast traffic is from the standby root node, it is necessary to further determine whether there is a disk in the distributed device that receives the multicast traffic from the primary root node as an ingress disk to decide whether to discard the standby root traffic or forward the standby root traffic.

[0048] Step S20, if there is a disk that receives the multicast traffic from the primary root node as an ingress disk, then discard the received multicast traffic from the standby root node.

[0049] In this embodiment, when the disk receives the multicast traffic from the standby root node as an ingress disk, if there is another disk in the distributed device that receives the multicast traffic from the primary root node as an ingress disk, it means that the primary root traffic has no failure. At this time, the distributed device needs to preferentially select the multicast traffic from the primary root node, that is, the primary root traffic, and discard the received multicast traffic from the standby root node, that is, the standby root traffic.

[0050] Step S30, if there is no disk that receives the multicast traffic from the primary root node as an ingress disk, then forward the received multicast traffic from the standby root node to the switching network of the distributed device.

[0051] In this embodiment, when the chassis disk receives multicast traffic from the standby root node as the ingress chassis disk, if no other chassis disk in the distributed device receives multicast traffic from the primary root node as the ingress chassis disk, it indicates that a failure has occurred in the primary root traffic. At this time, the distributed device needs to switch to the standby root traffic, that is, forward the received multicast traffic from the standby root node to the switching fabric of the distributed device, thereby realizing the service switching of the multicast traffic. Therefore, for the case where the distributed device has multiple chassis disks, it is possible to quickly detect the failure of the primary root traffic and quickly switch to the standby root traffic within the protection period. Among them, the switching fabric of the distributed device refers to the physical connection between the chassis disks inside the distributed device, which is used to realize the mutual forwarding inside the chassis disks.

[0052] In this embodiment, it is applied to the leaf nodes of the dual-root protection network. The leaf nodes are distributed devices. When the link is normal, the upstream multicast traffic will be sent to the distributed device through two links of the primary root node and the standby root node respectively, corresponding to the primary root traffic and the standby root traffic. In each protection period, for each chassis disk of the distributed device, when the chassis disk receives multicast traffic as the ingress chassis disk, parsing the BIER header of the multicast packet of the multicast traffic can obtain the multicast traffic ID and determine whether the multicast traffic is from the primary root node or the standby root node. If the multicast traffic is from the primary root node, it indicates that there is no failure in the primary root traffic and no further detection and judgment are required. If the multicast traffic is from the standby root node, it is necessary to further determine whether there is a chassis disk in the distributed device that receives multicast traffic from the primary root node as the ingress chassis disk. If there is another chassis disk in the distributed device that receives multicast traffic from the primary root node as the ingress chassis disk, it indicates that the primary root traffic is fault-free. At this time, the distributed device needs to preferentially select the multicast traffic from the primary root node, that is, the primary root traffic, and discard the received multicast traffic from the standby root node, that is, the standby root traffic. If no other chassis disk in the distributed device receives multicast traffic from the primary root node as the ingress chassis disk, it indicates that a failure has occurred in the primary root traffic. At this time, the distributed device needs to switch to the standby root traffic, that is, forward the received multicast traffic from the standby root node to the switching fabric of the distributed device, thereby realizing the service switching of the multicast traffic. Therefore, for the case where the distributed device has multiple chassis disks, it is possible to quickly detect the failure of the primary root traffic and quickly switch to the standby root traffic within the protection period. Compared with the switching after detecting the link state based on the IGP protocol, it can greatly shorten the service switching duration and does not require the use of BFD for BIER, avoiding the compatibility problem of device interoperability.

[0053] Further, in one embodiment, when the chassis disk receives multicast traffic from the standby root node as the ingress chassis disk, determining whether there is a chassis disk in the distributed device that receives multicast traffic from the primary root node as the ingress chassis disk includes:

[0054] When the faulty disk receives multicast traffic from the standby root node as the ingress disk, it determines whether there is a disk in the distributed device that has received multicast traffic from the primary root node as the ingress disk according to the first traffic label and the second traffic label of the disk;

[0055] Among them, the first traffic label of each disk is marked when the disk receives multicast traffic from the primary root node as the ingress disk, the second traffic label of each disk is updated according to the first traffic label sent by other disks when the disk receives the first traffic label sent by other disks, and each disk cancels the first traffic label and the second traffic label of the disk after sending the first traffic label to other disks.

[0056] In this embodiment, specifically, refer to Figure 3 , Figure 3 which is the schematic diagram of disk traffic labeling for an embodiment of the service switching method of this application. As shown in Figure 3 , each disk stores three traffic label tables, such as the local primary root traffic label table, the local standby root traffic label table, and the cross-disk primary root traffic label table. For each multicast traffic ID (i.e., the MCID in Figure 3 ), 1 / 0 can be used to mark the presence or absence of traffic respectively, and each mark occupies 1 bit (bit). Among them, the local primary root traffic label table stores the first traffic label correspondingly, which is used to mark when the disk receives multicast traffic from the primary root node as the ingress disk, and marks the multicast ID corresponding to the multicast traffic as 1. The local standby root traffic label table is used to mark when the disk receives multicast traffic from the standby root node as the ingress disk, and marks the multicast traffic ID corresponding to the multicast traffic as 1. The cross-disk primary root traffic label table stores the second traffic label correspondingly, which is used for the disk to update according to the local primary root traffic label sent by other disks in combination with its own cross-disk primary root traffic label when the disk receives the local primary root traffic label sent by other disks. In the case of using 1 / 0 to mark the presence or absence of traffic, the update can be performed in the way of bitwise OR operation. For example, for a certain multicast traffic ID, the cross-disk primary root traffic label is 0, and the local primary root traffic label received from other disks is 1. After performing bitwise OR operation on 0 and 1, 1 is obtained, and the traffic label corresponding to the multicast traffic ID in the cross-disk primary root traffic label table is updated with the obtained 1.

[0057] Furthermore, based on the first traffic label and the second traffic label of the chassis, it is determined whether there is a chassis in the distributed device that receives multicast traffic from the main root node as the ingress chassis. For example, the specific implementation method is that for a certain multicast traffic ID, if the corresponding traffic labels in the local main root traffic label table and the cross-chassis main root traffic label table are both 0, it is determined that there is no chassis in the distributed device that receives multicast traffic from the main root node as the ingress chassis. If any one of the corresponding traffic labels in the local main root traffic label table and the cross-chassis main root traffic label table is 1, it is determined that there is a chassis in the distributed device that receives multicast traffic from the main root node as the ingress chassis.

[0058] Further, referring to Figure 4 , Figure 4 is the cross-chassis forwarding schematic diagram of the local main root traffic label table for an embodiment of the service switching method of the present application. As Figure 4 shown, to achieve the rapid detection of the main root traffic failure and the rapid switching of the standby root traffic during the protection period, after each chassis sends the first traffic label to other chassis, the first traffic label and the second traffic label of the chassis are unlabeled. Specifically, all traffic labels in the local main root traffic label table, the local standby root traffic label table, and the cross-chassis main root traffic label table can be set to 0.

[0059] Furthermore, in one embodiment, the duration of the protection period is determined according to the duration of canceling all traffic labels, the duration of setting the first traffic label, and the duration of updating the second traffic label.

[0060] In this embodiment, from the above-mentioned related operations and judgment logics of the traffic labels, it can be seen that to achieve the rapid detection of the main root traffic failure and the rapid switching of the standby root traffic, it is necessary to complete the setting of the traffic labels, the cross-chassis forwarding of the traffic labels between different chassis, and the cancellation operation of the traffic labels within a protection period. Therefore, the duration of the protection period is determined according to the duration of canceling all traffic labels, the duration of setting the first traffic label, and the duration of updating the second traffic label.

[0061] Furthermore, in one embodiment, each chassis includes a chip. The determination of the duration of the protection period according to the duration of canceling all traffic labels, the duration of setting the first traffic label, and the duration of updating the second traffic label includes:

[0062] Calculating the duration of canceling all traffic labels based on the number of all traffic labels, the chip processing performance, and the performance ratio allocated to canceling the traffic labels;

[0063] Calculating the duration of setting the first traffic label based on the number of the first traffic labels of the chassis and the peak value of the multicast traffic ingress;

[0064] Calculate the duration for updating the second traffic label based on the number of the first traffic labels of the chassis, the chip processing performance, and the performance ratio allocated for forwarding the first traffic labels.

[0065] Sum up the duration for canceling all traffic labels, the duration for setting the first traffic labels, and the duration for updating the second traffic labels to calculate the protection period duration.

[0066] In this embodiment, each chassis is configured with a chip, and the duration for canceling all traffic labels, the duration for setting the first traffic labels, and the duration for updating the second traffic labels are closely related to the chip processing performance and the performance allocation ratio. Specifically, the protection period duration can be set as T, the chip processing performance (only considering the processing performance involved in forwarding and canceling labels) is set as K pps (Packets Per Second, abbreviated as pps, representing the number of multicast data packets transmitted per second), where the performance ratio allocated for canceling traffic labels is X%, and the performance ratio allocated for forwarding the first traffic labels is 1 - X%. The chip's rate for canceling traffic labels is: K * X% entries per second. Set the number of data entries in the traffic label table as N, then the duration T1 for the chip to cancel all traffic labels is T1 = 3N / (K * X%). Set the multicast traffic as L pps, then the duration T2 for the chip to set the first traffic labels (the main root traffic label table of this chassis) is T2 = N / L. Considering the duration for setting the backup root traffic label table of this chassis, T2 can be updated to T2 = 2N / L. The duration for updating the second traffic labels involves the cross-chassis forwarding of the first traffic labels. Since the cross-chassis forwarding of traffic labels uses the internal switching network of the distributed device and the port rate is much greater than the chip performance, the duration T3 for updating the second traffic labels is T3 = N / K(1 - X%). Sum up the duration for canceling all traffic labels, the duration for setting the first traffic labels, and the duration for updating the second traffic labels to calculate the protection period duration T = T1 + T2 + T3. Further, to avoid repeated service switching caused by refreshing the traffic label table, an empirical coefficient of 20% can be added to correct the protection period duration to: T = (T1 + T2 + T3) * (1 + 20%).

[0067] Further, in one embodiment, before calculating the duration for setting the first traffic labels based on the number of the first traffic labels of the chassis and the peak value of the multicast traffic entry, it includes:

[0068] Calculate the peak value of the multicast traffic entry based on the chassis slot bandwidth stability threshold, the chip processing performance, and the performance ratio allocated for canceling traffic labels.

[0069] In this embodiment, under normal circumstances, the multicast ingress traffic of a single slot in the distributed device does not exceed 5% of the slot bandwidth, and the average replication factor of the multicast traffic is 8 (source: laboratory test parameters formulated by the operator based on the traffic data of the existing network. 8 means that each multicast packet entering the system will be distributed to 8 different receiving points on average). If the stable two-way traffic of any port of the distributed device exceeds 45%, a bandwidth warning needs to be reported (considering that when the device loses power, the traffic of the protection device will double). Therefore, according to the stable threshold of the chassis slot bandwidth, the chip processing performance, and the performance ratio allocated to cancel the traffic marking, the peak value L of the multicast traffic ingress can be calculated by the formula L = K * (1 * 5% * 45% - X%). It should be noted that the peak value L of the multicast traffic ingress here is the ingress packet rate calculated under the scenario where the packet length of the multicast traffic is at the limit of the chip processing capacity.

[0070] Further, in one embodiment, the sum of the performance ratio allocated to cancel the traffic marking and the performance ratio allocated to forward the first traffic marking is 1. Before step S10, it includes:

[0071] Experiment on the dual-root protection network by adjusting the performance ratio allocated to cancel the traffic marking and the performance ratio allocated to forward the first traffic marking to obtain the corresponding relationship between different protection cycle durations and performance ratios;

[0072] Determine the optimal value range of the performance ratio according to the corresponding relationship between different protection cycle durations and performance ratios.

[0073] In this embodiment, the chip processing performance (only considering the processing performance involved in forwarding and canceling the marking) is set to Kpps, where the performance ratio allocated to cancel the traffic marking is X%, and the performance ratio allocated to forward the first traffic marking is 1 - X%. Substitute L = K * (1 * 5% * 45% - X%) into the formula T = T1 + T2 + T3, and we can get T = 3N / (K * X%) + 2N / K * (1 * 5% * 45% - X%) + N / K * (1 - X%). It can be seen that there is a functional relationship between the protection cycle duration T and the performance ratio X% allocated to cancel the traffic marking. When the number N of multicast traffic and the chip processing performance K are fixed (set N = 1000, K = 100 Mpps), experiment on the dual-root protection network by adjusting the performance ratio allocated to cancel the traffic marking and the performance ratio allocated to forward the first traffic marking to obtain the corresponding relationship between different protection cycle durations and performance ratios. Refer to Figure 5 , Figure 5 is a schematic diagram of the corresponding relationship between different protection cycle durations and performance ratios in an embodiment of the service switching method of this application. As Figure 5As shown, when the value of X ranges from 1 to 1.5, the protection period duration remains basically unchanged and is optimal. The smaller the value of X%, the larger 1 - X% is, that is, the higher the performance of the chip in processing service packet forwarding. Through analysis, it can be known that the optimal value range of X is between 1 and 1.5.

[0074] Further, in one embodiment, the operation of unmarking the first traffic mark and the second traffic mark of the chassis after the chassis sends the first traffic mark to other chassis includes:

[0075] Count the number of cycles of the protection period. When the number of cycles is an even multiple, each chassis unmarks the first traffic mark and the second traffic mark of the chassis after sending the first traffic mark to other chassis.

[0076] In this embodiment, to avoid the repeated switching of services caused by continuously refreshing the traffic mark table within the protection period, count the number of cycles of the protection period. When the number of cycles is an even multiple, that is, at every even multiple of the protection period cycle, each chassis unmarks the first traffic mark and the second traffic mark of the chassis after sending the first traffic mark to other chassis.

[0077] In this embodiment, for the usage scenario of the operator's ultra - clear IPTV, within 1000 channels, the traffic per single slot is about 5 Gb / s, the average packet length is about 1200 bytes, set the chip processing performance K = 100 M pps, the number of multicast traffic N = 1000, X = 1, calculate the multicast traffic ingress peak value L = 5 * 10 5 pps (the traffic per single slot is 5 Gb / s = 5 * 10 9 b / s, and the length of each packet is 1200 bytes, that is 1200 * 8 = 9600 b. The calculated packet rate pps is (5 * 10 9 b) / 9600 b ≈ 5 * 10 5 ). It should be noted that the multicast traffic ingress peak value L here is the ingress packet rate calculated according to the packet length in the actual scenario and the byte rate of the port. The average length of multicast packets in the actual application scenario is uncertain, but generally less than the ingress packet rate calculated in the scenario where the chip processing capacity limit is reached. According to the aforementioned formula, it is calculated that: T1 = 3N / (K * X%) = 3 ms, T2 = 2N / L = 4 ms, T3 = N / K(1 - X%) ≈ 0.03 ms, T = (T1 + T2 + T3) * (1 + 20%) ≈ 9 ms. The corresponding configurable protection period duration T is 10 ms, and the service switching duration T0 = 2T can reach about 20 ms (unmarking operation is performed at every even multiple of the protection period cycle, that is, 2 times the protection period duration). Compared with the switching duration of the IGP protocol detection method which is at the second level, the switching duration of this method is increased by nearly 50 times (1 second / 20 ms = 50 times).

[0078] In a second aspect, an embodiment of the present application further provides a service switching device.

[0079] In one embodiment, it is applied to a leaf node of a dual-root protection network. The leaf node is a distributed device, and the distributed device includes multiple chassis. Refer to Figure 6 , Figure 6 is a schematic diagram of the functional modules of an embodiment of the service switching device of the present application. As Figure 6 shown, the service switching device includes:

[0080] A judgment module 10, configured to, in each protection period, for each chassis, when the chassis receives multicast traffic from a standby root node as an ingress chassis, determine whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis;

[0081] A discard module 20, configured to, if there is a chassis that receives multicast traffic from a primary root node as an ingress chassis, discard the received multicast traffic from the standby root node;

[0082] A switching module 30, configured to, if there is no chassis that receives multicast traffic from a primary root node as an ingress chassis, forward the received multicast traffic from the standby root node to the switching fabric of the distributed device.

[0083] Further, in one embodiment, the judgment module 10 is configured to:

[0084] When the chassis receives multicast traffic from a standby root node as an ingress chassis, determine whether there is a chassis in the distributed device that receives multicast traffic from a primary root node as an ingress chassis according to the first traffic mark and the second traffic mark of the chassis;

[0085] Wherein, the first traffic mark of each chassis is marked when the chassis receives multicast traffic from a primary root node as an ingress chassis. The second traffic mark of each chassis is updated according to the first traffic mark sent by other chassis when the chassis receives the first traffic mark sent by other chassis. After each chassis sends the first traffic mark to other chassis, the first traffic mark and the second traffic mark of the chassis are unmarked.

[0086] Further, in one embodiment, the duration of the protection period is determined according to the duration of canceling all traffic marks, the duration of setting the first traffic mark, and the duration of updating the second traffic mark.

[0087] Further, in one embodiment, each chassis includes a chip. The duration of the protection period is determined according to the duration of canceling all traffic marks, the duration of setting the first traffic mark, and the duration of updating the second traffic mark for:

[0088] Calculate the duration for canceling all traffic markings based on the quantity of all traffic markings, the chip processing performance, and the performance ratio allocated to canceling traffic markings.

[0089] Calculate the duration for setting the first traffic marking based on the quantity of the first traffic marking on the chassis and the peak multicast traffic entry.

[0090] Calculate the duration for updating the second traffic marking based on the quantity of the first traffic marking on the chassis, the chip processing performance, and the performance ratio allocated to forwarding the first traffic marking.

[0091] Sum up the duration for canceling all traffic markings, the duration for setting the first traffic marking, and the duration for updating the second traffic marking to calculate the protection period duration.

[0092] Furthermore, in one embodiment, the service switching device further includes a peak multicast traffic entry calculation module for:

[0093] Calculate the peak multicast traffic entry based on the chassis slot bandwidth stability threshold, the chip processing performance, and the performance ratio allocated to canceling traffic markings.

[0094] Furthermore, in one embodiment, the sum of the performance ratio allocated to canceling traffic markings and the performance ratio allocated to forwarding the first traffic marking is 1. The service switching device further includes an optimal ratio determination module for:

[0095] Conduct experiments on the dual-root protection network by adjusting the performance ratio allocated to canceling traffic markings and the performance ratio allocated to forwarding the first traffic marking to obtain the corresponding relationship between different protection period durations and performance ratios;

[0096] Determine the optimal value range of the performance ratio according to the corresponding relationship between different protection period durations and performance ratios.

[0097] Furthermore, in one embodiment, after each chassis sends the first traffic marking to other chassis, it cancels the first traffic marking and the second traffic marking of the chassis for:

[0098] Count the number of cycles of the protection period. When the number of cycles is an even multiple, after each chassis sends the first traffic marking to other chassis, it cancels the first traffic marking and the second traffic marking of the chassis.

[0099] Wherein, the function implementation of each module in the above service switching device corresponds to each step in the above service switching method embodiment, and its function and implementation process will not be elaborated here one by one.

[0100] In a third aspect, an embodiment of the present application provides a service switching device.

[0101] In the embodiments of the present application, the service switching device is an NP (networking processor) chip, which integrates a microprocessor and a memory inside. The microprocessor can call the service switching program stored in the memory and execute the service switching method provided in the embodiments of the present application. Among them, the method executed when the service switching program is called can refer to the various embodiments of the service switching method of the present application, which will not be elaborated here.

[0102] Refer to Figure 7 , Figure 7 which is a schematic diagram of the hardware structure of the service switching device involved in the solution of the embodiments of the present application. In the embodiments of the present application, the service switching device may include a processor, a memory, a communication interface, and a communication bus.

[0103] Among them, the communication bus can be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0104] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces, etc., which are used to implement the interconnection of components inside the service switching device, as well as interfaces for implementing the interconnection between the service switching device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, an optical fiber interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0105] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical memory, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0106] The processor can be a general-purpose processor, which can call the service switching program stored in the memory and execute the service switching method provided in the embodiments of the present application. For example, the general-purpose processor can be a central processing unit (CPU). Among them, the method executed when the service switching program is called can refer to the various embodiments of the service switching method of the present application, which will not be elaborated here.

[0107] Those skilled in the art can understand,Figure 7 The hardware structure shown does not constitute a limitation on this application. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0108] Fourthly, an embodiment of this application also provides a readable storage medium.

[0109] A service switching program is stored on the readable storage medium of this application. When the service switching program is executed by a processor, the steps of the service switching method as described above are implemented.

[0110] Among them, for the method implemented when the service switching program is executed, reference can be made to the various embodiments of the service switching method of this application, which will not be elaborated here.

[0111] It should be noted that the serial numbers of the above embodiments of this application are only for description and do not represent the superiority or inferiority of the embodiments.

[0112] The terms "including" and "having" and any variations thereof in the description of the specification, claims and drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices. The descriptions of terms such as "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit that "first", "second" and "third" are of different types.

[0113] In the description of the embodiments of this application, "exemplary", "for example" or "for instance" etc. are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary", "for example" or "for instance" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary", "for example" or "for instance" is intended to present relevant concepts in a specific manner.

[0114] In the description of the embodiments of this application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "a plurality of" means two or more than two.

[0115] In some processes described in the embodiments of the present application, multiple operations or steps appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0116] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above and includes several instructions for causing a terminal device to execute the methods described in the various embodiments of the present application.

[0117] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structural or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A service switching method, characterized in that: The leaf node is applied to a dual-root protection network, the leaf node is a distributed device, the distributed device includes multiple disks, and the service switching method includes: In each protection cycle, for each disk, when the disk receives multicast traffic from the backup root node as an entry disk, it is determined whether there is a disk in the distributed device that receives multicast traffic from the primary root node as an entry disk; If there is a disk that receives multicast traffic from the primary root node as an entry disk, the multicast traffic received from the backup root node will be discarded; If there is no disk that receives the multicast traffic from the primary root node as an entry disk, the multicast traffic received from the backup root node is forwarded to the switching network of the distributed device.

2. The service switching method according to claim 1, characterized in that: When the server disk receives multicast traffic from the backup root node as an entry server disk, determining whether there is a server disk in the distributed device that receives multicast traffic from the primary root node as an entry server disk includes: When the machine disk receives multicast traffic from the backup root node as an entry machine disk, it is determined whether there is a machine disk in the distributed device that receives multicast traffic from the primary root node as an entry machine disk according to the first traffic mark and the second traffic mark of the machine disk; Among them, the first traffic mark of each machine disk is marked when the machine disk receives multicast traffic from the main root node as an entry machine disk, and the second traffic mark of each machine disk is updated according to the first traffic marks sent by other machine disks when the machine disk receives the first traffic marks sent by other machine disks. After sending the first traffic mark to other machine disks, each machine disk cancels the marking operation of the first traffic mark and the second traffic mark of the machine disk.

3. The service switching method according to claim 2, characterized in that: The protection period duration is determined according to the duration of canceling all traffic marks, the duration of setting the first traffic mark, and the duration of updating the second traffic mark.

4. The service switching method according to claim 3, characterized in that: Each disk includes a chip, and the protection period duration is determined according to the duration of canceling all traffic marks, the duration of setting the first traffic mark, and the duration of updating the second traffic mark, including: The time duration for canceling all traffic markings is calculated based on the number of all traffic markings, the chip processing performance, and the performance ratio allocated to canceling traffic markings. The duration of setting the first traffic mark is calculated according to the number of the first traffic marks of the disk and the peak value of the multicast traffic inlet; The duration of updating the second traffic mark is calculated according to the number of first traffic marks of the disk, the processing performance of the chip, and the performance ratio allocated to forwarding the first traffic mark; The duration of canceling all traffic marks, the duration of setting the first traffic mark, and the duration of updating the second traffic mark are summed to calculate the protection period duration.

5. The service switching method according to claim 4, characterized in that: Before calculating the duration of setting the first traffic mark according to the number of the first traffic marks of the disk and the peak value of the multicast traffic inlet, the method includes: The ingress peak value of multicast traffic is calculated based on the disk slot bandwidth stability threshold, chip processing performance, and the performance ratio allocated to canceling traffic marking.

6. The service switching method according to claim 4, characterized in that: The sum of the performance ratio allocated to canceling the traffic mark and the performance ratio allocated to forwarding the first traffic mark is 1. In each protection period, for each disk, when the disk receives multicast traffic from the standby root node as an entry disk, before determining whether there is a disk in the distributed device that receives multicast traffic from the primary root node as an entry disk, the method includes: By adjusting the performance ratio allocated to canceling the traffic mark and the performance ratio allocated to forwarding the first traffic mark, the dual-root protection network was tested to obtain the corresponding relationship between different protection cycle durations and performance ratios; According to the corresponding relationship between different protection period durations and performance ratios, the optimal value range of the performance ratio is determined.

7. The service switching method according to claim 2, characterized in that: The operation of cancelling the first flow mark and the second flow mark of each disk after sending the first flow mark to other disks includes: The number of cycles of the protection period is counted. When the number of cycles is an even multiple, each disk cancels the first flow mark and the second flow mark of the disk after sending the first flow mark to other disks.

8. A service switching device, characterized in that: The leaf node is applied to a dual-root protection network, the leaf node is a distributed device, the distributed device includes multiple disks, and the service switching device includes: A judgment module is used to judge whether there is a disk in the distributed device that receives multicast traffic from the primary root node as an entry disk for each disk in each protection period when the disk receives multicast traffic from the backup root node as an entry disk; A discarding module, configured to discard the multicast traffic received from the backup root node if there is a disk that receives the multicast traffic from the primary root node as an ingress disk; The switching module is used to forward the multicast traffic received from the backup root node to the switching network of the distributed device if there is no disk that receives the multicast traffic from the primary root node as an inlet disk.

9. A service switching device, characterized in that: The service switching device includes a processor, a memory, and a service switching program stored in the memory and executable by the processor, wherein when the service switching program is executed by the processor, the steps of the service switching method according to any one of claims 1 to 7 are implemented.

10. A readable storage medium, characterized in that: The readable storage medium stores a service switching program, wherein when the service switching program is executed by the processor, the steps of the service switching method according to any one of claims 1 to 7 are implemented.

Images