A method of service transmission and related apparatus

Abstract

The application discloses a service transmission method and related device. The method is applied to a cross-device transmission system. The cross-device transmission system comprises a first master device, a first backup device, a second master device, a second backup device, a first slave device and a second slave device. The first slave device is connected with the first master device and the first backup device; the second slave device is connected with the second master device and the second backup device; and the first slave device is connected with the second slave device. In the case that the first master device originally serving as a working master device fails, the first backup device which is mutually backed up can perform master-backup switching based on the acquired first message, perform packet slicing processing on the acquired service packet, and send at least one processed packet slice to the second master device through a first path, thereby solving the problem of service transmission interruption caused by the failure of the first master device and the like, and guaranteeing service transmission.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology, in particular to a service transmission method and related apparatus. BACKGROUND

[0002] Super dual band (SDB) link aggregation technology is a physical link bundling technology that bundles a microwave conventional frequency band (7G-38G) and an E-band frequency band (78G-86G) together to provide a physical transmission link with large bandwidth and long distance. Figure 1 A transmission schematic diagram using SDB technology is shown. As shown in Figure 1 A protection group A is configured in the master device A, and the protection group A includes one air interface and one Ethernet interface. A protection group B is configured in the master device B, and the protection group B also includes one air interface and one Ethernet interface. The two microwave links of the microwave conventional frequency band and the E-band frequency band are respectively bound to the interfaces corresponding to the protection group A and the protection group B. After the master device A obtains a service packet through a service access port, the master device A can perform slice processing on the service packet, and distribute the obtained packet slices to the above-mentioned microwave links. After the master device B obtains the packet slices sent by the master device A through the microwave links, the master device B can perform packet reassembly on the packet slices, and then perform forwarding of the service packet after the reassembly is completed.

[0003] However, the current protection method can only realize link-level protection and cannot solve the protection of device failure. SUMMARY

[0004] Embodiments of the present application provide a service transmission method and related apparatus. In the case of failure of a first master device originally serving as a working master device, a first backup device that backs up each other can perform master-backup switching, perform packet slice processing on the obtained service packet, and send at least one processed packet slice to a second master device through a first path, thereby solving the problem of service transmission interruption caused by failure of the first master device and ensuring service transmission.

[0005] In a first aspect, an embodiment of the present application provides a service transmission method. The method is applied to a cross-device transmission system. The described cross-device transmission system includes a first master device, a first backup device, a second master device, a second backup device, a first slave device, and a second slave device. The first slave device is connected with the first master device and the first backup device. The second slave device is connected with the second master device and the second backup device. The first slave device is also connected with the second slave device. The described first master device and the first backup device are backup devices of each other, and the second master device and the second backup device are also backup devices of each other. In the method, the first backup device acquires a first message, which is used to instruct the first backup device to perform master-backup switching. Then, after the first backup device performs master-backup switching, the first backup device can perform slice processing on a service packet to obtain at least one packet slice. And the at least one packet slice is transmitted to the second master device through a first path. The described first path is a transmission path between the first backup device and the second master device. In this way, in the case of failure of the first master device originally serving as a working master device or failure of a service access port of the first master device, the first backup device which is a backup device can perform master-backup switching and perform packet slice processing on the acquired service packet. And the at least one processed packet slice is sent to the second master device through the first path. This solves the problem of service transmission interruption caused by failure of the first master device, avoids service transmission interruption, and ensures normal service transmission. Moreover, by providing the first backup device as a backup of the first master device and the second backup device as a backup of the second master device, an additional port can be added to each device, the port expansion capability of each device is increased, and multiple connection modes with other devices are provided.

[0006] In some possible implementation manners, the first path includes a first sub-path. The first sub-path is composed of a transmission path between the first backup device and the second backup device and a transmission path between the second backup device and the second master device. In this way, the second backup device forwards the at least one packet slice, and multiple possible paths are provided to transmit the packet slice to the second master device.

[0007] In other possible implementation manners, the first path further includes a second sub-path. The second sub-path is composed of a transmission path between the first backup device and the first master device and a transmission path between the first master device and the second master device. In this way, the first master device forwards the at least one packet slice, and multiple possible paths are provided to transmit the packet slice to the second master device.

[0008] In some possible implementation manners, the first path further includes a third sub-path. The third sub-path is composed of a transmission path between the first backup device and the first slave device, a transmission path between the first slave device and the second slave device, and a transmission path between the second slave device and the second master device. In this way, the first slave device and the second slave device are used to forward at least one message slice, and multiple possible paths are provided to transmit the message slice to the second master device.

[0009] In some possible implementation manners, the first backup device further acquires a first service message before performing slice processing on the service message to obtain at least one message slice. The first backup device acquires a second service message from the first master device through a service link between the first backup device and the first master device. The first service message and the second service message are different. The first backup device aggregates the first service message and the second service message to obtain the service message. In this way, the first master device acquires the second service message from the first interface device, and the first backup device acquires the corresponding second service message from the same first interface device, and the first backup device aggregates the service message. The service access capability is improved, and the number of service interfaces of the first interface device can be reduced in the same service bandwidth scenario.

[0010] In some possible implementation manners, the first backup device further acquires the service message from one output port of the optical splitter through a first optical fiber before performing slice processing on the service message to obtain at least one message slice. In this way, the service access capability is improved, and the number of service ports of the peripheral device can be reduced in the same service bandwidth scenario.

[0011] In some possible implementation manners, the first backup device further sends a service switching message before performing slice processing on the service message to obtain at least one message slice. The service switching message is used to instruct the first interface device to perform service switching. The first backup device receives the service message sent by the first interface device. In this way, multiple possible service acquisition manners are provided, and the service access capability is improved.

[0012] In some possible implementation manners, the service switching message comprises a link aggregation group (LAG) update message. The LAG update message indicates that a system priority of a first LAG group in the first backup device is higher than a system priority of a second LAG group in the first master device. The first backup device receives the service packet sent by the first interface device, comprising: the first backup device receives the service packet sent by the first interface device from a port of the first LAG group.

[0013] In some possible implementation manners, the first backup device performs the master-backup switching, which can be implemented in the following manner. First, the first backup device detects whether the detection packet sent by the first master device is continuously received within a preset time length. Second, when the detection packet sent by the first master device is not continuously received within the preset time length, the first backup device determines that the first master device fails. Finally, when the first master device fails, the first backup device performs the master-backup switching. In this way, when the first master device completely fails, the first backup device can actively detect whether the first master device fails, which is suitable for various possible failure scenarios and provides various failure determination manners.

[0014] In some possible implementation manners, the first backup device receives the first message sent by the first master device. The first message comprises a failure condition of the first master device. The first backup device performs the master-backup switching, comprising: the first backup device performs the master-backup switching based on the failure condition of the first master device. In this way, when the first master device does not completely fail, the first backup device can be actively notified by the first master device that the first master device has failed, which is suitable for various possible failure scenarios and provides various failure determination manners.

[0015] In some possible implementation manners, the first backup device further acquires bandwidth information of an air interface link on the first path, and adjusts a sending rate of the packet slice based on the bandwidth information. The first backup device transmits the at least one packet slice to the second master device through the first path, comprising: the first backup device transmits the at least one packet slice to the second master device through the first path based on the adjusted sending rate of the packet slice. In this way, not only can the situation that the packet slice of the corresponding bearer is lost due to the influence of weather and other factors on the air interface link be avoided, but also the congestion and other situations caused by too fast sending of the packet slice can be avoided by sending the packet slice at the adjusted sending rate.

[0016] In some possible implementation manners, the method further includes: detecting, by the first backup device, whether the first message is continuously received on the sub-transmission paths included in the first member link within a preset time length. The first message is sent by the second master device. If the first message is not continuously received on any sub-transmission path within the preset time length, the first backup device switches at least one slice message carried on the sub-transmission path on which the first message is not received to be transmitted in the sub-transmission path on which the first message is received within the preset time length. In this way, when any sub-path in the first path fails, the corresponding carried message slice can be switched to be transmitted in other non-failed sub-path, so that the service transmission does not appear abnormal interruption phenomenon.

[0017] In a second aspect, an embodiment of the present application provides another method for service transmission. The method can be applied in a cross-device transmission system, and the cross-device transmission system can be understood with reference to the cross-device transmission system mentioned in the first aspect, which will not be repeated here. In the method, a first master device sends a first message to a first backup device, and the first message includes a failure condition of the first master device. The failure condition of the first master device can instruct the first backup device to perform master-backup switching.

[0018] In some possible implementation manners, before the first backup device switches to the working state of the master device, the first master device can continue to perform slice processing operation on service messages. Specifically, before the first master device sends the first message to the first backup device, the first master device performs slice processing on the service messages to obtain at least one message slice. Then, the first master device transmits the at least one message slice to the second master device through a second path. The second path is a transmission path between the first master device and the second master device.

[0019] In some possible implementation manners, the method further includes: detecting, by the first backup device, whether the first message is continuously received on the sub-transmission paths included in the first member link within a preset time length. The first message is sent by the second master device. If the first message is not continuously received on any sub-transmission path within the preset time length, the first backup device switches at least one slice message carried on the sub-transmission path on which the first message is not received to be transmitted in the sub-transmission path on which the first message is received within the preset time length. In this way, when any sub-path in the first path fails, the corresponding carried message slice can be switched to be transmitted in other non-failed sub-path, so that the service transmission does not appear abnormal interruption phenomenon.

[0020] In some possible implementation manners, the method further includes: detecting, by the first backup device, whether the first message is continuously received on the sub-transmission paths included in the first member link within a preset time length. The first message is sent by the second master device. If the first message is not continuously received on any sub-transmission path within the preset time length, the first backup device switches at least one slice message carried on the sub-transmission path on which the first message is not received to be transmitted in the sub-transmission path on which the first message is received within the preset time length. In this way, when any sub-path in the first path fails, the corresponding carried message slice can be switched to be transmitted in other non-failed sub-path, so that the service transmission does not appear abnormal interruption phenomenon.

[0021] In some possible implementation manners, the second path further comprises a sixth sub-path. The sixth sub-path is composed of a transmission path between the first master device and a first slave device, a transmission path between the first slave device and a second slave device, and a transmission path between the second slave device and the second master device.

[0022] In some possible implementation manners, before the first master device performs slice processing on the service packet to obtain at least one packet slice, the first master device further acquires a third service packet. The first master device acquires a fourth service packet from the first backup device through a service link between the first master device and the first backup device. The third service packet and the fourth service packet are different. The first master device aggregates the third service packet and the fourth service packet to obtain the service packet.

[0023] In some possible implementation manners, before the first master device performs slice processing on the service packet to obtain at least one packet slice, the first master device further acquires the service packet from one output port of the optical splitter through a second optical fiber.

[0024] In some possible implementation manners, before the first master device performs slice processing on the service packet to obtain at least one packet slice, the first master device further sends a service request message. The service request message is used to instruct a first docking device to send the service packet. The first master device receives the service packet sent by the first docking device.

[0025] In some possible implementation manners, the service request message comprises a LAG configuration message. The LAG configuration message indicates that a system priority of a second LAG group in the first master device is higher than a system priority of a first LAG group in the first backup device. The first master device receives the service packet sent by the first docking device, comprising: the first master device receives the service packet sent by the first docking device through a port of the second LAG group.

[0026] In some possible implementation manners, the method further comprises: the first master device receives bandwidth information of an air interface link on the second path, and adjusts a sending rate of the packet slice based on the bandwidth information. The first master device transmits the at least one packet slice to the second master device through the second path based on the adjusted sending rate of the packet slice.

[0027] In some possible implementation manners, the method further includes: detecting, by the first master device, whether the second message is continuously received on a sub-path included in the second path within a preset time length. The second message is sent by the second master device. If the second message is not continuously received on any sub-path within the preset time length, the first master device switches at least one message slice carried on the sub-path on which the second message is not received to be transmitted in the sub-path on which the second message is received within the preset time length.

[0028] In a third aspect, an embodiment of the present application provides a first backup device. The first backup device is included in a cross-device transmission system. It should be noted that the cross-device transmission system can be understood with reference to the cross-device transmission system described in the first aspect or the second aspect, and details are not described herein. The first backup device includes a processor, a memory, and a transceiver. The processor is interconnected with the memory and the transceiver through a line. The memory is configured to store computer readable instructions or programs. The transceiver is configured to obtain a first message. The first message is used to instruct the first backup device to perform master-backup switching. The processor invokes the computer readable instructions or programs stored in the memory to perform the following steps: performing slice processing on a service message to obtain at least one message slice; and transmitting the at least one message slice to a second master device through a first path. The first path is a transmission path between the first backup device and the second master device. The beneficial effects of the present aspect are described in the first aspect, and details are not described herein.

[0029] In some possible implementation manners, the processor is further specifically configured to perform the functions involved in the first aspect and any possible implementation manner of the first aspect.

[0030] In a fourth aspect, an embodiment of the present application provides a first master device. The first master device is included in a cross-device transmission system. It should be noted that the cross-device transmission system can be understood with reference to the cross-device transmission system described in any one of the first aspect to the third aspect, and details are not described herein. The first master device includes a processor, a memory, and a transceiver. The processor is interconnected with the memory and the transceiver through a line. The memory is configured to store computer readable instructions or programs. The transceiver is configured to send a first message to a first backup device. The first message includes a failure condition of the first master device. The failure condition of the first master device can instruct the first backup device to perform master-backup switching.

[0031] In some possible implementation manners, the processor invokes computer readable instructions or programs stored in the storage to perform the functions involved in the second aspect or any possible implementation manner of the second aspect.

[0032] In a fifth aspect, an embodiment of the present application provides a cross-device transmission system. The cross-device transmission system can be understood with reference to any of the cross-device transmission systems in the first aspect to the fourth aspect, and details are not described herein. The cross-device transmission system is configured to perform the method in the first aspect or the second aspect, and details are not described herein.

[0033] In some other possible implementation manners, the second slave device is configured to send the at least one message slice received from the first slave device to the second backup device.

[0034] In some other possible implementation manners, the second master device is configured to receive the at least one message slice sent by the first master device through the second path, and perform recombination processing on the at least one message slice to obtain the service message.

[0035] In a sixth aspect, an embodiment of the present application provides a transmission device. The transmission device is included in the cross-device transmission system. The transmission device described herein can be the first backup device in the first aspect, or the first master device in the second aspect. Alternatively, the transmission device can also be a second master device, and details are not described herein. The transmission device can include an obtaining unit, a processing unit and a sending unit. For example, if the transmission device is the first backup device, the obtaining unit is configured to perform the obtaining operation performed by the first backup device in the first aspect. The processing unit is configured to perform the processing operation performed by the first backup device in the first aspect. The sending unit is configured to perform the sending operation performed by the first backup device in the first aspect. Details can be understood with reference to the first aspect, and details are not described herein. If the transmission device is the first master device, the sending unit is configured to perform the sending operation performed by the first master device in the second aspect. The processing unit is configured to perform the processing operation performed by the first master device in the second aspect. The obtaining unit is configured to perform the obtaining operation performed by the first master device in the second aspect. Details can be understood with reference to the second aspect, and details are not described herein.

[0036] In a seventh aspect, an embodiment of the present application provides a computer readable storage medium, including instructions, when the instructions are executed on a computer, causing the computer to perform the method in the first aspect, any possible implementation manner of the first aspect, or the second aspect, or any possible implementation manner of the second aspect.

[0037] In an eighth aspect, the embodiments of the present application provide a computer program product containing instructions, which, when executed on a computer, cause the computer to perform the method of the first aspect, any one of the possible implementation manners of the first aspect, or the second aspect, any one of the possible implementation manners of the second aspect.

[0038] In a ninth aspect, the embodiments of the present application provide a chip system. The chip system can include a processor configured to support the functions involved in the method described in the first aspect, or any one of the possible implementation manners of the first aspect, by the first backup device; or support the functions involved in the method described in the second aspect, or any one of the possible implementation manners of the second aspect, by the first master device.

[0039] Optionally, in combination with the ninth aspect, in a first possible implementation manner, the chip system can further include a memory configured to store necessary program instructions and data of the first backup device, the first master device, and the like. The chip system can be composed of a chip, or can include the chip and other discrete devices. The chip system can include an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, and the like. Further, the chip system can further include an interface circuit, and the like.

[0040] From the above technical solutions, it can be seen that the embodiments of the present application have the following advantages:

[0041] In the embodiments of the present application, in the case that the first master device originally serving as a working master device fails, or a service access port of the first master device fails, the first backup device which is mutually backed up can perform master-backup switching, perform packet slicing processing on the obtained service packet, and send the at least one processed packet slice to the second master device through the first path. The problem of service transmission interruption caused by the failure of the first master device is solved, service transmission interruption is avoided, and normal service transmission is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiment description. Obviously, the drawings in the following description are only some of the embodiments of the present application.

[0043] Figure 1 A transmission schematic diagram using SDB technology is shown;

[0044] Figure 2A A first system architecture schematic diagram provided by the embodiments of the present application is shown;

[0045] Figure 2B A second system architecture diagram provided by the embodiment of the application is shown;

[0046] Figure 2C A third system architecture diagram provided by the embodiment of the application is shown;

[0047] Figure 3 A first flow diagram of a service transmission method provided by the embodiment of the application is shown;

[0048] Figure 4A A first scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0049] Figure 4B A second scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0050] Figure 4C A third scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0051] Figure 5 A second flow diagram of a service transmission method provided by the embodiment of the application is shown;

[0052] Figure 6A A fourth scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0053] Figure 6B A fifth scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0054] Figure 6C A sixth scenario diagram of obtaining a service packet provided by the embodiment of the application is shown;

[0055] Figure 7 A structure diagram of a transmission device provided by the embodiment of the application is shown;

[0056] Figure 8 A hardware structure diagram of a communication device provided by the embodiment of the application is shown. DETAILED DESCRIPTION

[0057] The embodiment of the application provides a service transmission method and related device, in the case of failure of a first master device originally serving as a working master device, a first backup device which is mutually backed up can perform master-backup switching, process a service packet obtained by packet slicing, and send at least one packet slice obtained by processing to a second master device through a first path, thereby solving the problem of service transmission interruption caused by failure of the first master device, and ensuring service transmission.

[0058] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by a person of ordinary skill in the art without creative effort belong to the scope of protection of the present application.

[0059] The terms "first", "second", "third", "fourth" and the like (if any) in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in other than the order illustrated or described herein. In addition, the terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusion. In the present application, "one or more" means one or more, and "multiple" means two or more. The term "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of the following" or the like means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b or c can mean a, b, c, a and b, a and c, b and c, or a and b and c, where a, b and c can be singular or plural. It should be noted that "at least one" can also be interpreted as "one or more".

[0060] The super dual band (SDB) link aggregation technology is a physical link bundling technology that bundles a microwave conventional frequency band (for example: 7G-38G) and an E-band frequency band (for example: 78G-86G) together to provide a physical transmission link with large bandwidth and long distance. The microwave conventional frequency band and the E-band frequency band can be understood as two microwave links, which are used to provide a physical transmission link for communication between double-end communication devices.

[0061] To solve the technical problems mentioned in the background, the present application provides a service transmission method. The method can be applied in Figure 2A The system structure is shown. As Figure 2AAs shown, the system architecture includes at least two master devices, at least two backup devices, and at least two slave devices. Among them, at least two master devices include at least a first master device and a second master device, at least two backup devices include at least a first backup device and a second backup device, and at least two slave devices also include at least a first slave device and a second slave device.

[0062] As shown, the first slave device is connected with the first master device and the first backup device. The second slave device is connected with the second master device and the second backup device. The first slave device is also connected with the second slave device. In addition, the first master device can also be connected with the second master device, and can also be connected with the first backup device. Similarly, the first backup device can also be connected with the second backup device. The second master device can also be connected with the second backup device. Figure 2A

[0063] In this application, the first backup device and the first master device can be backup for each other. When the first master device does not fail, the first master device performs slicing on the service packet or recombines at least one packet slice, etc. At this time, the first backup device in the backup state can transmit the service packet or at least one packet slice to the first master device. When the first master device fails, the first backup device can switch from the backup state to the working state, and then perform slicing on the service packet or recombine at least one packet slice, etc. At this time, the first master device that fails can transmit the service packet or at least one packet slice to the first backup device. In addition, the second backup device and the second master device can also be backup for each other, which can be understood with reference to the first master device and the first backup device described above, and will not be repeated here. It should be noted that the slicing or recombination functions mentioned in this application can also be understood with reference to the slicing / recombination shown in the foregoing Figure 1

[0064] In some possible examples, in the first master device, the second master device, the first backup device, the second backup device, the first slave device, and the second slave device, a corresponding protection group can be configured respectively. It can be understood with reference to Table 1 as follows:

[0065] Table 1

[0066]

[0067] As can be seen from Table 1, through the air interface or Ethernet interface in the protection group of each device, the connection between devices can be realized, and the interface expansion capability of the device can be enhanced. For example, in combination with Figure 2A ​​To achieve communication between the first master device and the second master device, at least three possible connection methods can be used: Method ①: Connect air interface 1 in protection group 1 to air interface 3 in protection group 3; Method ②: Sequentially connect one Ethernet interface 1, one Ethernet interface 2 and air interface 2 of protection group 1, air interface 4 and one Ethernet interface 4 of protection group 4, and one Ethernet interface 2 of protection group 2; Method ③: Sequentially connect another Ethernet interface 1 of protection group 1, one Ethernet interface 5 and air interface 5 of protection group 5, air interface 6 and one Ethernet interface 6 of protection group 6, and another Ethernet interface 2 of protection group 2. It should be noted that communication between other devices can also be understood by referring to the connection methods between the first master device and the second master device described above, and will not be elaborated upon here.

[0068] It should be understood that Table 1 above only describes the direct connection between the first master device and the second master device from the perspective of the air interface link. In practical applications, the first master device and the second master device can also be directly connected via an Ethernet interface. Regarding the direct connection between the first backup device and the second backup device, in addition to the air interface connection shown in Table 1, they can also be connected via an Ethernet interface, etc., without further explanation here. Furthermore, the direct connection between the first slave device and the second slave device can be understood in the same way as the direct connection between the first master device and the second master device, and will not be elaborated upon here. The described direct connection can be understood as the two directly connected devices not requiring any other devices to pass through.

[0069] In other examples, it is also possible to use the above... Figure 2A Based on the illustrated system architecture, one or more master control units are configured in each master device and each backup device. These master control units can further perform operations such as slicing or reassembling service packets. The number of master control units configured in each device can be determined according to service requirements. It should be noted that the number of master control units configured in the first master device, the second master device, the first backup device, and the second backup device does not necessarily have to be equal. For example, one master control unit can be configured in the first master device, and two master control units can be configured in the second master device. This application does not impose any limitations on this.

[0070] It should be understood that the above Figure 2A This only shows a first backup device configured with one backup for the first primary device and a second backup device configured with one backup for the second primary device. In practical applications, it is not limited to equipping only the first primary device with one backup device, nor is it limited to configuring only the second primary device with one backup device. For example, Figure 2B A schematic diagram of a second system architecture provided in an embodiment of this application is shown. For example... Figure 2BAs shown, two first backup devices (e.g., first backup device A and first backup device B) can be configured for the first primary device, and two second backup devices (e.g., second backup device A and second backup device B) can be configured for the second primary device. It should be noted that the first primary device can also be equipped with three, four, or an unlimited number of first backup devices, and the second primary device can also be equipped with three, four, or an unlimited number of second backup devices; this application does not impose any limitations.

[0071] In addition, the above Figures 2A-2B The system architecture shown depicts only one first slave device and one second slave device. In practical applications, the first master device and the first backup device are not limited to connecting to only one first slave device, nor are the second master device and the second backup device limited to connecting to only one second slave device. For example, Figure 2C A schematic diagram of a third system architecture provided in an embodiment of this application is shown. Figure 2C As shown, the first master device and the first backup device can connect to two first slave devices, such as first slave device A1 and first slave device A2. The second master device and the second backup device can also connect to two second slave devices, such as second slave device B1 and second slave device B2. Furthermore, first slave device A1 is connected to second slave device B1, and first slave device A2 is connected to second slave device B2. It should be noted that an unlimited number of first slave devices, such as three or four, can be configured to connect to the first master device and the first backup device, and an unlimited number of second slave devices, such as three or four, can be configured to connect to the second master device and the second backup device; this application does not impose any limitations on this.

[0072] Furthermore, the first master device and the second master device mentioned above may include, but are not limited to, microwave equipment such as radio transmission nodes (RTNs), terminals, optical transport networks (OTNs), etc. The first backup device and the second backup device may also include, but are not limited to, RTN equipment, terminals, OTNs, etc. The first slave device and the second slave device may also include, but are not limited to, RTN equipment, terminals, OTNs, etc., without limitation here. The first docking device and the second docking device may be routers, switches, packet transport networks (PTNs), etc., without limitation in this application.

[0073] It should be understood that the above Figures 2A-2C The system architectures shown in any of the examples are merely illustrative, and the application scenarios of the system architectures provided in this application are not limited to those described above. Figures 2A-2CThe microwave field shown in the above-mentioned embodiments. In practical applications, it can also be applied to, for example, the OTN field, or the subsequent fine-grained OTN+ physical link aggregation field, and the like, which are not limited here. In addition, the above-mentioned Figures 2A-2C The system architecture shown in any of the above-mentioned embodiments can be applied in other link aggregation cross-device protection scenarios in addition to the above-mentioned cross-band link aggregation transmission protection scenarios, such as microwave physical link aggregation (PLA), enhanced physical link aggregation (EPLA), and the like, which are not limited here. In addition, the above-mentioned Figures 2A-2C The system architecture shown in the above-mentioned embodiments can be applied in cross-device transmission scenarios through Ethernet transmission only in addition to the cross-band transmission scenarios of air interface links, thereby enhancing the protection of the entire cross-device transmission system. Subsequently, only the Figure 2A The system architecture shown in the above-mentioned embodiments is taken as an example to describe in detail the method for transmitting services provided by the present application.

[0074] In addition, from the Figures 2A-2C It can be seen from the system architecture shown that only the forward transmission of the service flow from the first backup device to the second master device is shown. In practical applications, the flow direction of the service flow can also be reverse transmission, that is, it can be transmitted from the working state of the second master device or the working state of the second backup device to the working state of the first backup device or the working state of the first master device, and the like, which are not limited here. In the present application, only the forward transmission of the service flow is taken as an example for description.

[0075] Figure 3 A method for transmitting services provided by the present application is shown. As shown in Figure 3 The method for transmitting services can include the following steps.

[0076] 301, the first backup device acquires a first message, and the first message is used to instruct the first backup device to perform master-slave switching.

[0077] In this example, when the first master device currently in the working state fails, the first master device cannot continue to slice the service packet, nor can it transmit the at least one packet slice obtained after the slicing; or, in the case of failure of the service access port of the first master device, the first master device currently in the working state cannot obtain the service packet; or, in the case where a user wants to slice the service packet through the backup device (i.e., the first backup device) originally configured as the first master device, the first backup device can obtain the first message. Then, the first backup device switches to the working device according to the indication of the first message, and the first master device becomes the backup device. It should be noted that the switching of the first backup device from the backup state to the working state is not limited to the three possible cases described above. In actual applications, other failure conditions may also be included, such as: failure of the master control unit, hard reset of the master device, power failure, etc., which are not limited here.

[0078] For example, the first backup device can first determine whether the first master device fails, and perform master-backup switching when the first master device fails. It should be noted that the first backup device can use different ways to determine whether the first master device fails when the first master device fails to different degrees. For example, in the case of complete failure of the first master device, the first backup device can determine whether the first master device fails from the perspective of active detection. Or, in the case of incomplete failure of the first master device, the first backup device can determine whether the first master device fails from the perspective of active detection or from the perspective of passive learning. The complete failure mentioned refers to that the first master device cannot perform slicing or recombination operations, nor can it perform simple message acquisition, sending, and other functions. The incomplete failure mentioned can be understood as that the first master device cannot perform slicing or recombination operations, but can perform simple message acquisition, sending, and other functions.

[0079] For the active detection manner, the first backup device detects whether the detection packet sent by the first master device is continuously received within a preset time length. If the detection packet sent by the first master device is not continuously received within the preset time length, the first backup device determines that the first master device fails. In this way, the first backup device switches from the backup state to the working state when the first master device fails. For example, if the detection is performed once every 3.3 milliseconds, if the first backup device does not detect the detection packet sent by the first master device for 3 times continuously within 10 milliseconds. At this time, the first backup device can determine that the first master device fails. It should be noted that the above-mentioned 10 milliseconds or other preset time lengths are not limited in the embodiments of the present application. In addition, the detection packet can be replaced by a state notification message, a state message, or the like, which is not limited in the present application. The detection packet can include, but is not limited to, an enhanced connectivity detection message (ECDM) or the like, which is not limited in the present application.

[0080] For the passive learning manner, the first master device can learn the failure condition of the first master device after monitoring the device state of the first master device. Then, the first master device carries the failure condition of the first master device in the first message and sends the first message to the first backup device. In this way, the first backup device acquires the first message, and performs master-backup switching based on the failure condition of the first master device carried in the first message.

[0081] For example, the first message can also be a command line message. The command line message can be a message set by a terminal or the like to indicate master-backup switching when a user wants to perform packet slicing, recombination, or the like through the first backup device. In this way, the first backup device can perform master-backup switching based on the command line message after acquiring the command line message.

[0082] It should be noted that the first master device and the first backup device of the present application can also send handshake messages (HSM) or the like to each other in real time to perform message handshake. Through the message handshake, the configuration data and the SDB state data between the first master device and the first backup device can be synchronized to achieve consistency of the configuration information between the two devices, thereby ensuring the normality of the functions such as slicing and recombination after device switching. In addition, the sending of HSM or the like can be distinguished from packet slicing through virtual local area network (VLAN) information or the like on the corresponding interface. It should be understood that the message handshake between the second master device and the second backup device can also be understood with reference to the message handshake between the first master device and the first backup device, which is not described herein.

[0083] 302. The first backup device performs slicing processing on the service packets to obtain at least one packet slice.

[0084] In this example, after the first backup device switches from backup mode to active master mode, it can slice the acquired service packets to obtain at least one packet slice. For instance, the first backup device can determine how many packet slices to divide the service packet into based on its packet length. For example, if the service packet length is 200 bytes, it can be divided into two packet slices. One packet slice includes 128 bytes, and the other includes 72 bytes. It should be noted that this example only uses a 200-byte packet length divided into two packet slices; in actual applications, the packet length is not limited.

[0085] In some examples, before the first backup device performs segmentation processing on the service packet to obtain at least one packet slice, it can also obtain the service packet in different ways. For example, the following will describe in detail how the first backup device obtains the service packet using three different embodiments.

[0086] Method 1: Acquisition via dual-active protection

[0087] In other examples, the first backup device may obtain service packets in the following manner: The first backup device obtains a first service packet, and through the service link between the first backup device and the first primary device, obtains a second service packet from the first primary device. The first and second service packets are then aggregated to obtain the service packet. Note that the first and second service packets mentioned are not the same.

[0088] Figure 4A This is a schematic diagram illustrating the first scenario of obtaining service messages provided in this application embodiment. For example... Figure 4A As shown above, in the above Figure 2A Based on the illustrated system architecture, this cross-device transmission system can obtain service packets from the first docking device and forward them to the second docking device. Specifically, the first master device and the first backup device are connected to the first docking device, and the second master device and the second backup device are connected to the second docking device. Furthermore, a service link is configured between the first master device and the first backup device, which can be used to transmit service packets.

[0089] Therefore, the first master device can obtain the second service packet from the first docking device, and send the second service packet to the first backup device through the service link. The first backup device can also obtain the first service packet from the first docking device. Then, the first backup device aggregates the obtained first service packet and the second service packet, and obtains the service packet. In the embodiment of the present application, since the first master device and the first backup device can access the service, the corresponding service packet is obtained from the first docking device through the first master device and the first backup device, which not only improves the access capability of the whole service, but also improves the service capacity; and at the same time, the Ethernet data interface of the first docking device is saved.

[0090] It should be noted that, in the above Figure 4A In the scenario shown, the second master device and the second backup device are also configured with a service link. After the second backup device switches from the backup state to the working master device, the second backup device can also obtain the packet obtained by the second master device from the second docking device through the service link. The specific process can be understood with reference to the transmission process between the first master device and the first backup device, which will not be described here.

[0091] In addition, Figure 4A Only one service link is taken as an example for description. In actual application, the number of service links mentioned can be one or more. The relationship between the service access port and the service link can be one-to-one or many-to-one, as long as the sum of the bandwidths of all service access ports is less than or equal to the bandwidth of the service link, which is not limited in the present application.

[0092] Mode 2: Obtained through a splitter

[0093] In some other possible examples, the first backup device can also obtain the service packet in the following manner. That is, the first backup device obtains the service packet from one output port of the splitter through the first optical fiber.

[0094] Figure 4B A second scenario for obtaining a service packet provided by an embodiment of the present application is shown. As Figure 4B shown, on the basis of the system architecture shown in the above Figure 2A On the basis of the system architecture shown in the above

[0095] The first interface device can send the service message to the first optical splitter. When the first master device fails, the first master device cannot obtain the service message from another output port of the first optical splitter through the second optical fiber, but the first backup device switched to the working state can obtain the service message from one output port of the first optical splitter through the first optical fiber. In the above manner, the service can be accessed from the first backup device when the first master device fails or the service access port of the first master device fails, the overall service access capability is improved, and the phenomenon that the service cannot be accessed due to the failure of the first master device and cannot be transmitted to the second interface device is avoided.

[0096] It should be noted that in the above Figure 4B The second master device and the second backup device can also be connected with the second interface device through the second optical splitter in the scenario shown. Specifically, the second interface device is connected with the second optical splitter. Moreover, one input port of the second optical splitter is connected with the service output port of the second backup device, and another input port is connected with the service output port of the second master device. The specific implementation process can be understood with reference to the first optical splitter connected with the first master device and the first backup device, which will not be described herein.

[0097] Method 3: A method of obtaining through a service switching message

[0098] In some other possible implementation manners, the first backup device can also obtain the service message in the following manner. That is, the first backup device sends a service switching message. The service switching message is used to instruct the first interface device to perform service switching. The first backup device receives the service message sent by the first interface device.

[0099] Figure 4C A third scenario for obtaining a service message provided by an embodiment of the application is shown. As Figure 4C shown, on the basis of the system architecture shown Figure 2A above, the cross-device transmission system can obtain the service message from the first interface device and forward the service message to the second interface device. Specifically, the first master device and the first backup device are connected with the first interface device respectively, and the second master device and the second backup device are connected with the second interface device respectively. When the first master device fails, the first backup device switched to the working state can send a service switching message to the first interface device, instructing the first interface device to send the service message to the first backup device instead of the first master device. In this way, after the first interface device receives the service switching message, the first interface device can send the service message to the first backup device under the instruction of the service switching message. The service access capability is improved, and multiple possible service access methods are provided.

[0100] In other examples, the service switchover message mentioned above can be a LAG update message. This LAG update message indicates that the system priority of the first LAG group in the first backup device is higher than the system priority of the second LAG group in the first master device. Therefore, the first backup device can also receive service packets sent by the first docked device in the following way: the first backup device receives service packets sent by the first docked device from the port of the first LAG group.

[0101] In the above Figure 4C In the illustrated scenario, a first LAG group can be configured in the first backup device, a second LAG group can be configured in the first master device, and a third LAG group can be configured in the first docking device. The aforementioned first LAG group includes at least one port ( Figure 4C (This example uses only one port, a). The second LAG group also includes at least one port, b. Figure 4C (This example uses only one port, b). The third LAG group includes at least two ports ( Figure 4C Only ports c1 and c2 are shown in the diagram. Port c1 is connected to port a, and port c2 is connected to port b.

[0102] When the primary device is functioning correctly, the system priority of the second LAG group can be set higher than that of the first LAG group. Then, the functioning primary device informs the first connected device that it needs to send service packets from port c2 in the third LAG group to the primary device. At this time, the primary device can receive the service packets from port b. However, if the primary device fails and continues to receive service packets through port b, an access failure will occur.

[0103] Therefore, by adjusting the system priorities of the first LAG group and the second LAG group, the adjusted system priority of the first LAG group is made higher than that of the second LAG group. In this way, the first backup device sends an LAG update message to the first connected device, informing it that the service packets need to be switched from port c2 to port c1 for transmission. Upon receiving the LAG update message, the first connected device sends the service packets to the first backup device through port c1, enabling the first backup device to receive the service packets through port a connected to port c1. Through this method, service access capabilities are improved in the event of a failure in the service access point of the first primary device, and the overall system protection capability is enhanced.

[0104] It should be noted that the above Figure 4CEach port in a LAG group can be understood as a service port of the corresponding device, that is, the port used by the device to receive or send services. Furthermore, when both the first and second LAG groups contain multiple ports, the system priority of the first LAG group is higher than that of the second LAG group. This also reflects that the port priority of each port in the first LAG group is higher than that of each port in the second LAG group.

[0105] In addition, in the above Figure 4C In the scenario shown, corresponding LAG groups can also be configured in the second master device, the second backup device, and the second docking device respectively. For details, please refer to the above for configuring corresponding LAG groups in the first master device, the first backup device, and the first docking device. It will not be elaborated here.

[0106] It should be noted that the embodiments of this application mainly describe the process of the first backup device obtaining service messages through methods 1 to 3. In practical applications, the first backup device may also obtain service messages through other methods, and this application is not limited to the three methods mentioned above.

[0107] 303. The first backup device transmits at least one packet slice to the second master device through a first path, wherein the first path is the transmission path between the first backup device and the second master device.

[0108] In this example, after the first backup device slices the service packets to obtain at least one packet slice, it can transmit this at least one packet slice to the second primary device via a first path. The first path can consist of transmission paths between different devices. Alternatively, at least one packet slice can be transmitted from the first backup device to the second primary device after being forwarded by different devices. The first path mentioned can include, but is not limited to, the following three possible scenarios:

[0109] Case 1: The first path includes the first subpath.

[0110] The first sub-path mentioned consists of the transmission path between the first backup device and the second backup device, and the transmission path between the second backup device and the second master device.

[0111] Scenario 2: The first path also includes a second sub-path.

[0112] The second sub-path mentioned consists of the transmission path between the first backup device and the first master device, and the transmission path between the first master device and the second master device.

[0113] Scenario 3: The first path also includes a third sub-path.

[0114] The third sub-path mentioned is composed of the transmission path between the first backup device and the first slave device, the transmission path between the first slave device and the second slave device, and the transmission path between the second slave device and the second master device.

[0115] After obtaining the at least one message slice, the first backup device can distribute the at least one message slice to one or more of the first sub-path, the second sub-path, and the third sub-path mentioned above. For example, the at least one message slice can be transmitted only through the first sub-path, only through the second sub-path, or only through the third sub-path. Alternatively, the at least one message slice can be transmitted through the first sub-path and the second sub-path, through the first sub-path and the third sub-path, or through the second sub-path and the third sub-path. Alternatively, the at least one message slice can be transmitted through the first sub-path, the second sub-path, and the third sub-path. The sub-path through which the at least one message slice is transmitted is not limited in the embodiments of the present application.

[0116] In the foregoing Figure 2A On the basis of the system architecture shown, in order to facilitate understanding of the transmission paths between different devices, different labels (such as ①-⑨) can be used to represent the transmission paths between different devices. For a detailed understanding, refer to Table 2 below:

[0117] Table 2

[0118] Reference Meaning ① Transmission path between the first backup device and the second backup device ② Transmission path between the second backup device and the second primary device ③ Transmission path between the first backup device and the first primary device ④ Transmission path between the first primary device and the second primary device ⑤ Transmission path between the first backup device and the first secondary device ⑥ Transmission path between the first secondary device and the second secondary device ⑦ Transmission path between the second secondary device and the second primary device ⑧ Transmission path between the first primary device and the first secondary device ⑨ Transmission path between the second secondary device and the second backup device

[0119] As can be seen from Table 2 above, label ① can represent the transmission path between the first backup device and the second backup device, and label ② can represent the transmission path between the second backup device and the second master device. The remaining labels can be understood with reference to labels ① and ②, which will not be described here.

[0120] Therefore, the first sub-path in case one described above can be understood as being composed of ①+②. The second sub-path in case two can be understood as being composed of ③+④. Similarly, the third sub-path in case three can be understood as being composed of ⑤+⑥+⑦.

[0121] It should be understood that the labels ①-⑨ shown in Table 2 above are only a schematic description, and in actual applications, other ways can be used to represent the transmission paths between devices, which will not be limited here.

[0122] Based on this, in any of the scenarios described above Figures 4A-4C the specific transmission direction of the service message and the message slice can be transmitted with reference to the sub-paths shown in Figure 2A , which will not be described here.

[0123] In some possible examples, the method for transmitting a service can further include: the first backup device obtaining bandwidth information of an air interface link on the first path. The first backup device adjusts a sending rate of the message slices based on the bandwidth information. The first backup device transmits the at least one message slice to the second master device through the first path, including: the first backup device transmits the at least one message slice to the second master device through the first path based on the adjusted sending rate of the message slices.

[0124] In this example, in the case of connecting between devices through an air interface link, the bandwidth of the air interface of each device can be affected by weather changes, which can easily cause message slices to be discarded on the air interface link. Moreover, once a message slice is discarded, the entire service message will be randomly discarded. Therefore, in order to avoid the message slices being discarded on the air interface link, the bandwidth of the message slices distributed to the air interface link should be less than or equal to the real-time bandwidth of the air interface link at this time.

[0125] Therefore, in order for the first backup device to be able to perceive the bandwidth change of the air interface link on the first path in real time, the first backup device also needs to obtain the bandwidth information of the air interface link on the first path. It should be understood that the air interface link on the first path mentioned above can be understood with reference to the transmission path shown by reference numerals ①, ④, and ⑥ in the foregoing Figure 2A For example, the first master device obtains the bandwidth information of the air interface link shown by reference numeral ④, and sends the bandwidth information of the air interface link shown by reference numeral ④ to the first backup device. Similarly, the first slave device obtains the bandwidth information of the air interface link shown by reference numeral ⑥, and sends the bandwidth information of the air interface link shown by reference numeral ⑥ to the first backup device. The first backup device can also obtain the bandwidth information of the air interface link shown by reference numeral ①. In this way, the first backup device can obtain the bandwidth information of the air interface link shown by reference numerals ①, ④, and ⑥.

[0126] The first backup device adjusts the sending rate of the message slices based on the bandwidth information of the air interface link on the first path, and transmits the at least one message slice to the second master device through the first path based on the adjusted sending rate of the message slices. For example, after obtaining the bandwidth information of the air interface link shown by reference numeral ①, the first backup device can adjust the sending rate of the message slices transmitted on the air interface link shown by reference numeral ①. In this example, transmitting the at least one message slice at the adjusted sending rate of the message slices can achieve the purpose of rate-limiting transmission on the air interface link, and can prevent congestion transmission, loss, and the like of the message slices.

[0127] It should be noted that the bandwidth information of each air interface link mentioned above can be sent to the first backup device through a corresponding bandwidth notification message (BNM). In actual application, other messages can also be sent to the first backup device, which is not limited by the present application. Exemplarily, the BNM message and the message slice can be distinguished by VLAN information and the like.

[0128] In some other possible examples, after obtaining the bandwidth information of the air interface link shown by the label ⑥, the first slave device can also send a copy of the bandwidth information of the air interface link to the first master device through the path shown by ⑧ in synchronization, so that the first slave device does not perceive the switching process during the master-slave switching between the first backup device and the first master device, and fast switching is realized.

[0129] In some other possible examples, for the third sub-path shown in the third case, after obtaining the at least one message slice sent by the first slave device, the second slave device can send the at least one message slice to the second backup device through the path shown by ⑨ in addition to sending the at least one message slice to the second master device according to the transmission path between the second slave device and the second master device (i.e., the path shown by the label ⑦). The specific understanding can be made with reference to the foregoing Figures 4A-4C diagram. Not only can the double sending of the message slice be realized, but also the second slave device does not perceive the switching process during the master-slave switching between the second master device and the second backup device, and fast switching and master-slave switching are realized.

[0130] It should be noted that after the second backup device obtains the at least one message slice from the second slave device, the at least one message slice will not be subjected to recombination processing or the like, and the at least one message slice can be discarded.

[0131] In some other possible examples, since the sub-paths in the first path span different devices, once some sub-paths fail, the message slices transmitted on the sub-paths that fail will not be normally transmitted. Therefore, in order to ensure that the message slices are normally transmitted in the sub-paths, the method for transmitting the service can further include that the first backup device detects whether a first message is continuously received on the sub-paths included in the first path within a preset time length, the first message being sent by the second master device; and if the first message is not continuously received on any sub-path within the preset time length, the first backup device switches at least one message slice carried on the sub-path on which the first message is not received to be transmitted in the sub-path on which the first message is received within the preset time length.

[0132] For example, in the foregoing Figure 2AThe system architecture shown is an example. It is assumed that the second master device sends a first packet to the first backup device through the first sub-path, the second sub-path, and the third sub-path, respectively. If the first backup device does not continuously receive the first packet in the first sub-path within 10 milliseconds, but continuously receives the first packet in the second sub-path and the third sub-path, the first backup device can determine that the first sub-path has failed, and determine that the second sub-path and the third sub-path have not abnormally occurred. At this time, the first backup device can switch at least one packet slice carried in the first sub-path to the second sub-path and / or the third sub-path for transmission.

[0133] It should be understood that the first packet described above can include, but is not limited to, an ECDM packet. Through the ECDM packet, not only can end-to-end connectivity detection be performed on the dual-end devices on the sub-paths, but also packet slice problems such as packet loss, out-of-order, and bit error can be detected. In addition, when the first packet and the packet slice are transmitted on the sub-paths in the first path, they can also be distinguished by the VLAN information carried in each packet.

[0134] 304、The second master device performs recombination processing on the at least one packet slice to obtain a service packet.

[0135] In this example, after the second master device obtains the at least one packet slice sent by the first backup device through the first path, the second master device can perform recombination processing on the at least one packet slice to obtain a service packet.

[0136] In other examples, after the second master device obtains the service packet, the second master device can also send the service packet to the second interface device. For example, the second master device can directly send the service packet to the second interface device, or send the service packet to the second interface device through the second backup device. For details, reference can be made to the packet flow direction shown in the foregoing Figure 4A , and details are not repeated here. Alternatively, the second master device can also send the service packet to the second interface device through the second optical splitter. For details, reference can be made to the packet flow direction shown in the foregoing Figure 4B , and details are not repeated here. Alternatively, the second master device can also send the service packet to the second interface device by configuring a LAG group. For details, reference can be made to the packet flow direction shown in the foregoing Figure 4C , and details are not repeated here.

[0137] It should be understood that the foregoing Figures 3-4CIn any of the above-described embodiments, only the method of performing the service transmission by the first backup device switched to the working state from the perspective of the first primary device failing, the second primary device not failing, and the service transmission being performed by the first backup device switched to the working state and the second primary device is described. In actual applications, it is also possible that the first primary device does not fail, the second primary device fails, and the service transmission is performed between the first primary device and the second backup device switched to the working state. The specific implementation process can be understood with reference to the foregoing Figures 3-4C In any of the above-described embodiments, only the method of performing the service transmission by the first backup device switched to the working state from the perspective of the first primary device failing, the second primary device not failing, and the service transmission being performed by the first backup device switched to the working state and the second primary device is described. In actual applications, it is also possible that the first primary device does not fail, the second primary device fails, and the service transmission is performed between the first primary device and the second backup device switched to the working state. The specific implementation process can be understood with reference to the foregoing Figures 3-4C In any of the above-described embodiments, only the method of performing the service transmission by the first backup device switched to the working state from the perspective of the first primary device failing, the second primary device not failing, and the service transmission being performed by the first backup device switched to the working state and the second primary device is described. In actual applications, it is also possible that the first primary device does not fail, the second primary device fails, and the service transmission is performed between the first primary device and the second backup device switched to the working state. The specific implementation process can be understood with reference to the foregoing

[0138] In addition, the above-described Figures 3-4C In any of the above-described embodiments, only the method of performing the service transmission by the first backup device switched to the working state from the perspective of the first primary device failing, the second primary device not failing, and the service transmission being performed by the first backup device switched to the working state and the second primary device is described. In actual applications, it is also possible that the first primary device does not fail, the second primary device fails, and the service transmission is performed between the first primary device and the second backup device switched to the working state. The specific implementation process can be understood with reference to the foregoing

[0139] In the embodiments of the present application, in the case that the first primary device originally in the working state fails or the service access port of the first primary device fails, the first backup device which backs up each other can perform primary backup switching, perform packet slicing processing on the obtained service packet, and send at least one packet slice obtained after the processing to the second primary device through the first path. The problem of service transmission interruption caused by the failure of the first primary device is solved, the service transmission interruption is avoided, and the normal transmission of the service is ensured. In addition, by providing the first backup device which backs up the first primary device and the second backup device which backs up the second primary device, additional ports can be added in each device, the port expansion capability of each device is increased, and multiple connection modes with other devices are provided.

[0140] The above-described Figures 3-4C In any of the above-described embodiments, only the method of performing the service transmission by the first backup device switched to the working state from the perspective of the first primary device failing, the second primary device not failing, and the service transmission being performed by the first backup device switched to the working state and the second primary device is described. In actual applications, it is also possible that the first primary device does not fail, the second primary device fails, and the service transmission is performed between the first primary device and the second backup device switched to the working state. The specific implementation process can be understood with reference to the foregoing Figure 5 A second flowchart of the method of performing the service transmission provided in the embodiments of the present application is provided. As shown in Figure 5 The method of performing the service transmission can include the following steps.

[0141] 501. The first primary device performs slicing processing on the service packet to obtain at least one packet slice.

[0142] In the example, in the case that the first primary device does not fail, the service access port of the first primary device does not fail, or the user still continues to hope that the packet slicing processing is performed by the working first primary device, the first backup device does not need to perform the primary-backup switching operation shown in step 301 in the foregoing Figure 3 , but can continue to perform the slicing processing of the service packet and the like by the first primary device as the working device.

[0143] Therefore, before the first backup device performs step 301 in the foregoing Figure 3 , the first primary device can perform the slicing processing of the service packet to obtain at least one packet slice. In the example, the first primary device can determine how many packet slices are divided from the service packet according to the packet length of the service packet, and the specific understanding can be performed with reference to the content described in step 302 in the foregoing Figure 3 , which is not repeated here.

[0144] In some possible examples, before the first primary device performs the slicing processing of the service packet to obtain at least one packet slice, the first primary device can also obtain the service packet in different manners. In the example, the following will be described in detail how the first primary device obtains the service packet in combination with the manner 1 to the manner 3 described in the foregoing step 302.

[0145] Figure 6A A fourth scenario for obtaining a service packet provided in the embodiments of the present application is shown.

[0146] As shown in the foregoing Figure 6A , for the manner 1, the first backup device can obtain the fourth service packet from the first docking device and send the fourth service packet to the first primary device through the service link. The first primary device can also obtain the third service packet from the first docking device. Then, the first primary device aggregates the obtained third service packet and the fourth service packet to obtain the service packet. The technical effects achieved in the embodiments of the present application can be understood with reference to the effects of the foregoing manner 1, which is not repeated here.

[0147] It should be noted that Figure 6A the connection manner between the cross-device transmission system, the first docking device, and the second docking device shown in the foregoing Figure 4A can be understood with reference to the connection manner shown in the foregoing Figure 4A , which is not repeated here. The first backup device, the first primary device, the service link, and the like described here can also be understood with reference to the content shown in the foregoing , which is not repeated here.

[0148] Figure 6B A fifth scenario for obtaining a service packet provided in the embodiments of the present application is shown.

[0149] As shown in Figure 6B , for mode 2, in the case that the first backup device does not perform the master-backup switching, the first backup device does not acquire the service message from the one output port of the first optical splitter through the first optical fiber, but continues to acquire the service message from the other output port of the first optical splitter through the second optical fiber by the first master device in the working state. Through the above mode, the service is accessed by the first master device through the second optical fiber, and the access capability of the overall service is improved. It should be understood that the Figure 6B connection mode between the devices shown in the cross-device transmission system, the first docking device, the second docking device, the first optical splitter, the second optical splitter, etc. can be understood with reference to the foregoing Figure 4B connection mode, which will not be described here. In addition, the first optical fiber, the second optical fiber, etc. described above can be understood with reference to the foregoing Figure 4B content shown in the foregoing

[0150] Figure 6C Another scenario for acquiring a service message is shown.

[0151] As shown in Figure 6C , for mode 3, in the case that the first backup device does not perform the master-backup switching, the first master device in the working state can still send a service request message to the first docking device. The service request message can instruct the first docking device not to send the service message to the first backup device, but to send the service message to the first master device. In this way, after the first docking device receives the service request message, the first docking device can send the service message to the first master device under the instruction of the service request message. Both the access capability of the service and the multiple possible service access modes are provided.

[0152] In other examples, the service request message mentioned above can be a LAG configuration message. The LAG configuration message indicates that the system priority of the second LAG group in the first master device is higher than the system priority of the first LAG group in the first backup device. Therefore, the first master device receives the service message sent by the first docking device, which can also be achieved by the following mode, i.e., the first master device receives the service message sent by the first docking device from the port of the second LAG group.

[0153] In the scenario shown above Figure 6C , the first LAG group is configured in the first backup device, the second LAG group is configured in the first master device, and the third LAG group is configured in the first docking device, which can be understood with reference to the foregoing Figure 4C content, which will not be described here.

[0154] Since the LAG configuration message indicates that the system priority of the second LAG group is set higher than that of the first LAG group, the first master device, in its operational state, can use this LAG configuration message to inform the first connected device that it needs to send service packets from port c2 in the third LAG group to the first master device. At this time, the first master device can receive the service packets from port b.

[0155] It should be noted that the above Figure 6C The ports for each LAG group can be found in the previous section. Figure 4C The content shown is for your understanding and will not be elaborated upon here. Furthermore, Figure 6C The connection methods between the cross-device transmission system, the first docking device, the second docking device, etc., shown can be referred to the foregoing for details. Figure 4C The connection method shown is for reference only and will not be elaborated upon here.

[0156] 502. The first master device transmits the at least one message slice to the second master device through the second path, wherein the second path is the transmission path between the first master device and the second master device.

[0157] In this example, the second path can consist of transmission paths between different devices. Alternatively, at least one packet slice can be transmitted from the first master device to the second master device after being forwarded by different devices. The mentioned second path may include one or more of a fourth sub-path, a fifth sub-path, and a sixth sub-path. The described fourth sub-path is the transmission path between the first master device and the second master device. The described fifth sub-path consists of the transmission paths between the first master device and the first backup device, the first backup device and the second backup device, and the second backup device and the second master device. The described third sub-path consists of the transmission paths between the first master device and the first slave device, the first slave device and the second slave device, and the second slave device and the second master device.

[0158] After obtaining at least one packet slice, the first primary device can distribute the at least one packet slice to one or more of the aforementioned fourth, fifth, and sixth sub-paths. Specifically, this can be understood by referring to the description in step 303 above of the first backup device distributing at least one packet slice to one or more of the first, second, and third sub-paths; further details will not be provided here.

[0159] The second path mentioned can be found in the following references. Figure 2AThe fourth sub-path can be understood as consisting of 4. The fifth sub-path can be understood as consisting of 3+1+2. Similarly, the sixth sub-path can be understood as consisting of 7+6+8.

[0160] In addition, compared with the first path and the second path, it can be seen that part of the links in the first path overlap with part of the links in the second path. For example, the second sub-path and the fifth sub-path both have the transmission path shown by the number 3, the third sub-path and the sixth sub-path both have the transmission paths shown by the numbers 6 and 8, and the like, which are not limited here.

[0161] Based on this, in any of the scenarios described above, Figures 6A-6C The transmission direction of the specific service message and message slice can be transmitted by referring to the sub-paths shown in Figure 2A here.

[0162] In some possible examples, the method for service transmission can further include: the first master device receiving bandwidth information of the air interface link on the second path. The first master device adjusts the sending rate of the message slice based on the bandwidth information. The first master device transmits the at least one message slice to the second master device through the second path, including: the first master device transmits the at least one message slice to the second master device through the second path based on the adjusted sending rate of the message slice.

[0163] It should be noted that the bandwidth information of the air interface link on the second path described above can be understood with reference to the bandwidth information of the air interface link on the first path described in the foregoing step 303, which is not repeated here. In addition, how the first master device adjusts the sending rate of the message slice can also be understood with reference to the content of how the first backup device adjusts the sending rate of the message slice in the foregoing step 303, which is not repeated here.

[0164] In some possible examples, after the first slave device obtains the bandwidth information of the air interface link shown by the number 6, it can also synchronously send a copy of the bandwidth information of the air interface link to the first backup device, so that the first slave device does not perceive the switching process during subsequent master-slave switching between the first backup device and the first master device, and fast switching is achieved.

[0165] In another possible example, for the aforementioned sixth sub-path, after obtaining the at least one message slice sent by the first slave device, the second slave device can send the at least one message slice to the second backup device through the path shown by reference numeral 9 in addition to sending the at least one message slice to the second master device along the transmission path between the second slave device and the second master device (i.e., the path shown by reference numeral 7), thereby not only achieving double sending of the message slice, but also realizing fast switching and device switching without the second slave device perceiving the switching process during master-slave switching between the second master device and the second backup device.

[0166] It should be noted that, at this time, the second backup device does not perform reassembly processing or other operations on the at least one message slice obtained from the second slave device, and can discard the at least one message slice.

[0167] In another possible example, since the sub-paths in the second path span different devices, once some sub-paths fail, the message slices transmitted on the failed sub-paths cannot be normally transmitted. Therefore, to ensure normal transmission of the message slices in the sub-paths, the method for transmitting a service can further include: detecting, by the first master device, whether a second message is continuously received on the sub-paths included in the second path within a preset time length, the second message being sent by the second master device; and if the second message is not continuously received on any sub-path within the preset time length, switching, by the first master device, at least one message slice carried on the sub-path on which the second message is not received, to be transmitted in the sub-path on which the second message is received within the preset time length.

[0168] It should be noted that the second message and how the first master device judges whether the second message is received can be understood with reference to the first message and how the first backup device judges whether the first message is received, which are described in the foregoing step 303, and details are not repeated here.

[0169] 503. Reassembling, by the second master device, the at least one message slice to obtain a service message.

[0170] In this example, step 503 can be understood with reference to the content described in the foregoing step 304, and details are not repeated here.

[0171] Optionally, in another example, in the case that the first master device fails, a service access port of the first master device fails, or a user wants to process the message slice by the first backup device, the method for transmitting a service can further include the following steps:

[0172] 504. The first backup device acquires the first message, and the first message is used to instruct the first backup device to perform master-backup switching.

[0173] 505. The first backup device performs slice processing on the service packet to obtain at least one packet slice.

[0174] 506. The first backup device transmits the at least one packet slice to the second master device through a first path, and the first path is a transmission path between the first backup device and the second master device.

[0175] 507. The second master device performs recombination processing on the at least one packet slice to obtain the service packet.

[0176] It should be noted that steps 504-507 can be understood with reference to the content of steps 301-303 in the foregoing Figure 3 , and details are not described herein.

[0177] In the embodiments of the present application, before the master-backup switching performed by the first backup device which backs up each other, the first master device can still perform packet slice processing on the acquired service packet, and transmit the at least one packet slice obtained after the processing to the second master device through a second path. In the case of failure of the first master device, the service packet can also be switched to the first backup device, and the first backup device can perform slice processing on the service packet and transmit the packet slice to the second master device. The problem of service transmission interruption caused by failure of the first master device is solved, the service transmission interruption is avoided, and the normal transmission of the service is ensured. Moreover, by providing the first backup device for the first master device, the second backup device for the second master device, and the like, additional ports can be added to each device, the port expansion capability of each device is increased, and multiple connection modes with other devices are provided.

[0178] The above mainly introduces the scheme provided by the embodiments of the present application from the perspective of the method. It can be understood that the first backup device, the first master device, and the like described above include the corresponding hardware structure and / or software module for executing each function in order to implement the above functions. Those skilled in the art should easily realize that, in combination with the functions described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is implemented in hardware or computer software driven hardware depends on the specific application and design constraints of the technical scheme. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0179] From the perspective of functional units, this application can divide the first backup device into functional units according to the above method embodiments. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one functional unit. The integrated functional unit can be implemented in hardware or in software.

[0180] For example, when dividing the functional units using an integrated approach. Figure 7 This application provides a schematic diagram of the structure of a transmission device. For example... Figure 7 As shown, the transmission device includes an acquisition unit 701, a processing unit 702, and a transmission unit 703.

[0181] If the transmission device is Figure 3 In the corresponding embodiment, the first backup device, the acquisition unit 701 executes... Figure 3 Step 301 in the process. Processing unit 702 executes. Figure 3 Step 302. The sending unit 703 executes. Figure 3 Step 303. If the transmission device is Figure 5 In the corresponding embodiment, the first backup device, the acquisition unit 701 executes... Figure 5 Step 504 in the process. Processing unit 702 executes. Figure 5 Step 505. The sending unit 703 executes... Figure 5 Step 506 in the process.

[0182] If the transmission device is Figure 5 In the corresponding embodiment, the first master device, processing unit 702, executes... Figure 5 Step 501. The sending unit 703 executes. Figure 5 Step 502 in the process. The acquisition unit 701 is used to acquire the service message before the processing unit 702 executes step 501, as detailed above. Figures 4A-4C The content will be understood in detail here, and will not be elaborated upon further.

[0183] If the transmission device is Figure 3 In the corresponding embodiment, the second master device, processing unit 702, executes... Figure 3 Step 304. The acquisition unit 701 is used to receive... Figure 3 Message slicing in step 303. If the transmission device is... Figure 5 In the corresponding embodiment, the second master device, processing unit 702, executes... Figure 5 Steps 503 and 507 in the process. The acquisition unit 701 is used to receive... Figure 5 Message slicing in step 502 or step 506.

[0184] This application also provides a cross-device transmission system. This cross-device transmission system is described above. Figures 2A-2C , Figures 4A-4C or Figures 6A-6C As shown above, please refer to the detailed explanation. Figures 2A-4C , Figures 4A-4C or Figures 6A-6C As shown, the specifics will not be elaborated further.

[0185] The aforementioned first backup device, first primary device, and second primary device can be provided by Figure 8 It is implemented using communication devices. Figure 8 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application. The communication device includes a processor 801, a memory 802, and a transceiver 803. The processor 801 is interconnected with the memory 802 and the transceiver 803 via lines.

[0186] If the communication device is Figure 3 The first backup device in the corresponding embodiment. The transceiver 803 is used to execute steps 301 and 303. The processor 801 calls the program code in the memory 802 to execute step 302. If the communication device is Figure 5 The first backup device in the corresponding embodiment. The transceiver 803 is used to execute steps 504 and 506. The processor 801 calls the program code in the memory 802 to execute step 505.

[0187] If the communication device is Figure 5 The first master device in the corresponding embodiment. The transceiver 803 is used to execute step 502. The processor 801 calls the program code in the memory 802 to execute step 501.

[0188] If the communication device is Figure 3 The second master device in the corresponding embodiment. The transceiver 803 is used to process the message slice received in step 303. The processor 801 calls the program code in memory 802 to execute step 304. If the communication device is... Figure 5 The second master device in the corresponding embodiment. The transceiver 803 is used to execute the message slice received from step 502 or step 506. The processor 801 calls the program code in the memory 802 to execute steps 502 and 507.

[0189] The above, the above examples are only used to illustrate the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing examples, those skilled in the art should understand that the technical solutions recorded in the foregoing examples can still be modified, or some technical features therein can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of service transmission, characterized by, The method is applied to a cross-device transmission system, the cross-device transmission system comprising a first master device, a first backup device, a second master device, a second backup device, a first slave device and a second slave device; wherein the first slave device is connected with the first master device and the first backup device; the second slave device is connected with the second master device and the second backup device; the first slave device is connected with the second slave device; the first master device and the first backup device are backup for each other, and the second master device and the second backup device are backup for each other; the method comprises: The first backup device acquires a first message, the first message being used for instructing the first backup device to perform master-backup switching and switch from a backup state to a working state; The first backup device performs slice processing on a service packet to obtain at least one packet slice; The first backup device transmits the at least one packet slice to the second master device through a first path, the first path being a transmission path between the first backup device and the second master device; After the first slave device acquires bandwidth information of an air interface link on the first path, the first slave device synchronously sends the bandwidth information to the first backup device; After the second slave device acquires the at least one packet slice sent by the first slave device, the second slave device sends the at least one packet slice to the second backup device in addition to sending the at least one packet slice to the second master device.

2. The method of claim 1, wherein, The first path comprises a first sub-path, the first sub-path being composed of a transmission path between the first backup device and the second backup device and a transmission path between the second backup device and the second master device.

3. The method of claim 2, wherein, The first path further comprises a second sub-path, the second sub-path being composed of a transmission path between the first backup device and the first master device and a transmission path between the first master device and the second master device.

4. The method of claim 3, wherein, The first path further comprises a third sub-path, the third sub-path being composed of a transmission path between the first backup device and the first slave device, a transmission path between the first slave device and the second slave device, and a transmission path between the second slave device and the second master device.

5. The method according to any one of claims 1-4, characterized in that, Before the first backup device performs slice processing on a service packet to obtain at least one packet slice, the method further comprises: The first backup device acquires a first service packet; The first backup device acquires a second service packet from the first master device through a service link between the first backup device and the first master device, the first service packet and the second service packet being different; The first backup device aggregates the first service packet and the second service packet to obtain the service packet.

6. The method according to any one of claims 1-4, characterized in that, Before the first backup device performs slice processing on a service packet to obtain at least one packet slice, the method further comprises: The first backup device acquires the service packet from one output port of a splitter through a first optical fiber.

7. The method according to any one of claims 1 to 4, characterized in that, Before the first backup device performs slice processing on a service packet to obtain at least one packet slice, the method further comprises: The first backup device sends a service switching message, the service switching message being used to instruct the first interface device to perform service switching; The first backup device receives the service message sent by the first interface device.

8. The method of claim 7, wherein, The service switching message comprises a link aggregation group (LAG) update message, and the LAG update message indicates that the system priority of a first LAG group in the first backup device is higher than the system priority of a second LAG group in the first master device. The first backup device receives the service message sent by the first interface device, comprising: The first backup device receives the service message sent by the first interface device from a port of the first LAG group.

9. The method according to any one of claims 1-4, characterized in that, The first backup device performs master-backup switching, comprising: The first backup device detects whether the detection message sent by the first master device is continuously received within a preset time length; If the detection message sent by the first master device is not continuously received within the preset time length, the first backup device determines that the first master device has a failure; The first backup device performs master-backup switching when the first master device has a failure.

10. The method of any one of claims 1-4, wherein, The first backup device obtains a first message, comprising: The first backup device receives the first message sent by the first master device, and the first message comprises a failure condition of the first master device; The first backup device performs master-backup switching, comprising: The first backup device performs master-backup switching based on the failure condition of the first master device.

11. The method according to any one of claims 1-4, characterized in that, The method further comprises: The first backup device obtains bandwidth information of an air interface link on the first path; The first backup device adjusts the sending rate of the message slice based on the bandwidth information; The first backup device transmits the at least one message slice to the second master device through the first path, comprising: The first backup device transmits the at least one message slice to the second master device through the first path based on the adjusted sending rate of the message slice.

12. A first backup device, characterized by The first backup device is included in a cross-device transmission system, the cross-device transmission system comprising a first master device, the first backup device, a second master device, a second backup device, a first slave device, and a second slave device; wherein the first slave device is connected with the first master device and the first backup device; the second slave device is connected with the second master device and the second backup device; the first slave device is connected with the second slave device; the first master device and the first backup device are backup for each other, and the second master device and the second backup device are backup for each other; the first backup device comprises a processor, a memory, and a transceiver, the processor is interconnected with the memory and the transceiver through a line respectively; wherein The memory is used to store computer readable instructions or programs; The processor invokes the computer readable instructions or the programs to be executed for performing the method in any one of claims 1-11.

13. A cross-device transfer system, comprising: The cross-device transmission system comprises a first master device, a second master device, a first backup device, a second backup device, a first slave device and a second slave device; wherein the first slave device is connected with the first master device and the first backup device; the second slave device is connected with the second master device and the second backup device; the first slave device is connected with the second slave device; the first master device and the first backup device are backup for each other, and the second master device and the second backup device are backup for each other; wherein, The first backup device is configured to: acquire a first message, the first message being used to instruct the first backup device to perform master-backup switching and switch from a backup state to an active state; perform slice processing on a service packet to obtain at least one packet slice; transmit the at least one packet slice to the second master device through a first path, the first path being a transmission path between the first backup device and the second master device; after the first slave device acquires bandwidth information of an air interface link on the first path, the first slave device synchronously sends the bandwidth information to the first backup device; after the second slave device acquires the at least one packet slice sent by the first slave device, the second slave device sends the at least one packet slice to the second backup device in addition to sending the at least one packet slice to the second master device.

14. The cross-device transfer system of claim 13, wherein, The first path comprises a first sub-path, and the first sub-path is composed of a transmission path between the first backup device and the second backup device and a transmission path between the second backup device and the second master device.

15. The cross-device transfer system of claim 14, wherein, The first path further comprises a second sub-path, and the second sub-path is composed of a transmission path between the first backup device and the first master device and a transmission path between the first master device and the second master device.

16. The cross-device transfer system of claim 15, wherein, The first path further comprises a third sub-path, and the third sub-path is composed of a transmission path between the first backup device and the first slave device, a transmission path between the first slave device and the second slave device, and a transmission path between the second slave device and the second master device.

17. The cross-device transmission system according to any one of claims 13-16, wherein, The first backup device is configured to: acquire bandwidth information of an air interface link on the first path; adjust a sending rate of the at least one packet slice based on the bandwidth information; transmit the at least one packet slice to the second master device through the first path based on the adjusted sending rate of the packet slice.

18. The cross-device transfer system of claim 16, wherein, The second slave device is configured to: send the at least one packet slice received from the first slave device to the second backup device.

Images