CFM up message carrying method and device in ODUK protection scenario

Abstract

The present invention provides a CFM up message carrying method and device for an ODUK protection scenario. The method comprises: discarding the CFM up message sent to the backup path; resetting the internal loopback port and configuring the internal loopback port; changing the target address of the CFM up message sent to the primary path, determining the target address as the internal loopback port; and establishing a CFM up message multicast service between the primary and backup exits and the internal loopback port. The present invention applies point-to-point packet CFM up message detection to the multipoint-to-multipoint ODUK 1+1 protection scenario, thereby realizing fault detection, delay monitoring, and packet loss rate detection of related links in the packet switching stage under relevant service scenarios, thereby improving network stability.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of L2 switching technology, and in particular to a method and device for carrying a CFM up message in an ODUK protection scenario. Background Art

[0002] With the rapid development of internet technology, telecom operators' networks are growing larger and more complex. POTN, a next-generation optical transport network (OTN), integrates OTN, TDM, and packet technologies, achieving widespread market adoption. Client signals are accessed by packet services, switched, and then sent to the ODUK timeslot on the line side via the ODU cross-connect unit (ODU) for transmission via OTN signals. Typically, OTN protection is implemented based on ODUK 1+1 protection. After client signals are connected to the system, ingress multicast is typically used during packet processing in the front-end PTN module to replicate messages. OAM messages, which perform fault detection within the link, are also replicated. However, the OAM standard specifies that CFM up can only be used in point-to-point services. Therefore, developing a method and device for carrying CFM up messages in ODUK protection scenarios can effectively overcome the shortcomings of the aforementioned related technologies and has become a pressing technical challenge for the industry. Summary of the Invention

[0003] In view of the above problems existing in the prior art, embodiments of the present invention provide a method and device for carrying CFM up messages in an ODUK protection scenario.

[0004] In a first aspect, an embodiment of the present invention provides a CFM up message carrying method for an ODUK protection scenario, comprising: discarding a CFM up message sent to a backup path; resetting an internal loopback interface and configuring the internal loopback interface; changing a destination address of a CFM up message sent to a primary path, determining the destination address to be the internal loopback interface; and establishing a CFM up message multicast service between a primary and backup egress port and the internal loopback interface.

[0005] Based on the above method embodiments, the CFM UP message carrying method for an ODUK protection scenario provided in an embodiment of the present invention includes discarding CFM UP messages sent to a backup path, including matching the target backup data output port of the CFM UP message, determining the Ethernet type and operation code, identifying CFM UP messages with error count stamps, and discarding the CFM UP messages with error count stamps.

[0006] Based on the content of the above method embodiment, the CFM up message carrying method for the ODUK protection scenario provided in the embodiment of the present invention, wherein the resetting of the internal loopback interface and the configuration of the internal loopback interface include: setting the input port and output port direction attributes of the internal loopback interface, and not performing any processing on messages entering and exiting the internal loopback interface.

[0007] Based on the above method embodiments, in an embodiment of the present invention, the CFM up message carrying method for an ODUK protection scenario, wherein the changing of the destination address of a CFM up message sent to a primary path and determining the destination address as the internal loopback interface includes: matching the target primary data output port of the CFM up message, determining the Ethernet type and operation code, identifying CFM up messages for which egress message editing actions have not taken effect, and changing the destination address of the CFM up messages for which egress message editing actions have not taken effect to the internal loopback interface.

[0008] Based on the above method embodiments, the CFM UP message carrying method for the ODUK protection scenario provided in the embodiments of the present invention establishes a CFM UP message multicast service between the primary and backup egresses and the internal loopback interface, including: changing the VLAN value in the original CFM UP message to ensure that the egress CFM UP message edit takes effect, and flooding the CFM UP message with a count stamp to the primary and backup paths via multicast, thereby implementing the CFM UP message multicast service.

[0009] In a second aspect, an embodiment of the present invention provides a CFM up message carrying device for an ODUK protection scenario, including: a first main module, configured to discard CFM up messages sent to a backup path; a second main module, configured to re-set an internal loopback interface and configure the internal loopback interface; a third main module, configured to change a target address of a CFM up message sent to a primary path and determine the target address as the internal loopback interface; and a fourth main module, configured to establish a CFM up message multicast service between the primary and backup egress ports and the internal loopback interface.

[0010] In a third aspect, an embodiment of the present invention provides an electronic device, including:

[0011] at least one processor; and

[0012] at least one memory communicatively coupled to the processor, wherein:

[0013] The memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the CFM up message carrying method in the ODUK protection scenario provided by any one of the various implementations of the first aspect.

[0014] In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions cause a computer to execute the CFM up message carrying method for the ODUK protection scenario provided in any one of the various implementations of the first aspect.

[0015] The CFM UP message carrying method and device for ODUK protection scenarios provided in embodiments of the present invention apply point-to-point packet CFM UP message detection to multipoint-to-multipoint ODUK 1+1 protection scenarios. This implements fault detection, latency monitoring, and packet loss rate detection for relevant links in the packet switching phase in relevant service scenarios, thereby improving network stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0017] Figure 1 Flowchart of a CFM up message carrying method for an ODUK protection scenario provided by an embodiment of the present invention;

[0018] Figure 2 A schematic diagram of the structure of a CFM up message carrying device for an ODUK protection scenario provided by an embodiment of the present invention;

[0019] Figure 3 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention;

[0020] Figure 4 A schematic diagram of a CFM up message for discarding a backup path according to an embodiment of the present invention;

[0021] Figure 5 Schematic diagram of sending a CFM up message on the primary path to the loopback interface according to an embodiment of the present invention;

[0022] Figure 6 A schematic diagram of multicast service flooding of a CFM up message to a primary or backup path via a loopback interface according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention. In addition, the technical features in the various embodiments or single embodiments provided by the present invention can be arbitrarily combined with each other to form a feasible technical solution. This combination is not restricted by the sequence of steps and / or structural composition mode, but must be based on the ability of ordinary technicians in this field to implement it. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0024] The embodiment of the present invention provides a CFM up message carrying method for an ODUK protection scenario, see Figure 1 The method includes: discarding CFM up messages sent to a backup path; resetting an internal loopback interface and configuring the internal loopback interface; changing the destination address of CFM up messages sent to a primary path to set the destination address to the internal loopback interface; and establishing a CFM up message multicast service between the primary and backup egress ports and the internal loopback interface.

[0025] Based on the content of the above method embodiment, as an optional embodiment, the CFM UP message carrying method for the ODUK protection scenario provided in the embodiment of the present invention, wherein the CFM UP message sent to the backup path is discarded, includes: matching the target backup data output port of the CFM UP message, setting the VLAN value to 1, determining the Ethernet type and operation code, identifying the CFM UP message with an error count stamp, and discarding the CFM UP message with the error count stamp.

[0026] See Figure 4 , discard CFM up messages sent to the backup path. By matching the message's destination port (backup dstport), VLAN value 1, Ethernet type (0x8902), and operation code (0x1 / 0x2a / 0x2b / 0x2e / 0x2f), identify CFM up messages that are not correctly stamped with counts and discard them (drop).

[0027] Based on the content of the above method embodiment, as an optional embodiment, in the CFM up message carrying method for the ODUK protection scenario provided in the embodiment of the present invention, the resetting of the internal loopback interface and the configuration of the internal loopback interface include: setting the input port and output port direction attributes of the internal loopback interface, and not performing any processing on messages entering and exiting the internal loopback interface.

[0028] Based on the content of the above method embodiment, as an optional embodiment, the CFM up message carrying method for the ODUK protection scenario provided in the embodiment of the present invention, wherein the changing the destination address of the CFM up message sent to the primary path and determining the destination address as the internal loopback port includes: matching the target primary data output port of the CFM up message, setting the VLAN value to 2, determining the Ethernet type and operation code, identifying the CFM up message for which the egress message editing action has not taken effect, and changing the destination address of the CFM up message for which the egress message editing action has not taken effect to the internal loopback port.

[0029] See Figure 5 , changes the destination of CFM up messages sent to the primary path to the loopback interface. By matching the message's destination port (primary dstport), VLAN value 2, Ethernet type (0x8902), and operation code (0x1 / 0x2a / 0x2b / 0x2e / 0x2f), the system identifies CFM up messages for which the egress message edit action has not taken effect, and changes their destination to the loopback interface (trap).

[0030] Based on the content of the above method embodiment, as an optional embodiment, the CFM UP message carrying method for the ODUK protection scenario provided in the embodiments of the present invention, wherein the CFM UP message multicast service is established between the primary and backup egresses and the internal loopback interface, includes: changing the VLAN value in the original CFM UP message to ensure that the egress CFM UP message edit is effective, and flooding the CFM UP message with a count stamp to the primary and backup paths via multicast, thereby implementing the CFM UP message multicast service. It should be noted that the original CFM UP message includes CFM CCM, CFM LM, and CFM DM messages.

[0031] See Figure 6 , establish a multicast service between the loopback interface and the primary and backup egress, change the VLAN value in the original CFM up CCM / LM / DM message to solve the problem that the egress message edit does not take effect, and flood the CFM up message with the count stamp to the primary and backup paths through multicast to achieve dual sending of CFM up messages.

[0032] The CFM UP message carrying method for ODUK protection scenarios provided in embodiments of the present invention applies point-to-point packet CFM UP message detection to multipoint-to-multipoint ODUK 1+1 protection scenarios. This implements fault detection, latency monitoring, and packet loss rate detection for relevant links in the packet switching phase in relevant service scenarios, thereby improving network stability.

[0033] The implementation basis of each embodiment of the present invention is to implement programmed processing through a device with processor functions. Therefore, in engineering practice, the technical solutions and functions of each embodiment of the present invention can be encapsulated into various modules. Based on this reality, on the basis of the above embodiments, an embodiment of the present invention provides a CFM up message carrying device for an ODUK protection scenario, which is used to execute the CFM up message carrying method for an ODUK protection scenario in the above method embodiment. Figure 2 The device includes: a first main module, configured to discard CFM up messages sent to a backup path; a second main module, configured to reset an internal loopback interface and configure the internal loopback interface; a third main module, configured to change a destination address of CFM up messages sent to a primary path and set the destination address to the internal loopback interface; and a fourth main module, configured to establish a CFM up message multicast service between the primary and backup egress ports and the internal loopback interface.

[0034] The CFM up message carrying device for the ODUK protection scenario provided by the embodiment of the present invention adopts Figure 2 By applying point-to-point packet CFM up message detection to multipoint-to-multipoint ODUK1+1 protection scenarios, several modules in the system can implement fault detection, delay monitoring, and packet loss rate detection of related links in the packet switching phase in relevant business scenarios, thereby improving network stability.

[0035] It should be noted that the device in the device embodiment provided by the present invention can be used to implement the method in the above-mentioned method embodiment as well as the method in other method embodiments provided by the present invention. The only difference is that the corresponding functional modules are set. The principle is basically the same as the principle of the above-mentioned device embodiment provided by the present invention. As long as those skilled in the art refer to the specific technical solutions in other method embodiments on the basis of the above-mentioned device embodiment, obtain the corresponding technical means and the technical solutions composed of these technical means by combining technical features, and ensure the practicality of the technical solutions, they can improve the device in the above-mentioned device embodiment to obtain the corresponding device class embodiment, thereby obtaining the corresponding device class embodiment for implementing the methods in other method class embodiments. For example:

[0036] Based on the content of the above device embodiment, as an optional embodiment, the CFM UP message carrying device for the ODUK protection scenario provided in the embodiment of the present invention further includes: a first submodule, configured to implement the discarding of CFM UP messages sent to the backup path, including: matching the target backup data output port of the CFM UP message, setting the VLAN value to 1, determining the Ethernet type and operation code, identifying CFM UP messages with error count stamps, and discarding the CFM UP messages with error count stamps.

[0037] Based on the content of the above device embodiment, as an optional embodiment, the CFM up message carrying device for the ODUK protection scenario provided in the embodiment of the present invention further includes: a second submodule, configured to implement the resetting of the internal loopback interface and configure the internal loopback interface, including: setting the input port and output port direction attributes of the internal loopback interface and not performing any processing on messages entering and exiting the internal loopback interface.

[0038] Based on the content of the above device embodiment, as an optional embodiment, the CFM up message carrying device for the ODUK protection scenario provided in the embodiment of the present invention further includes: a third submodule, configured to implement the changing of the target address of the CFM up message sent to the primary path and determine the target address as the internal loopback interface, including: matching the target primary data output port of the CFM up message, setting the VLAN value to 2, determining the Ethernet type and operation code, identifying the CFM up message for which the egress message editing action has not taken effect, and changing the target address of the CFM up message for which the egress message editing action has not taken effect to the internal loopback interface.

[0039] Based on the content of the above-mentioned device embodiment, as an optional embodiment, the CFM up message carrying device for the ODUK protection scenario provided in the embodiment of the present invention further includes: a fourth submodule, configured to implement the establishment of the CFM up message multicast service between the primary and backup egresses and the internal loopback interface, including: changing the VLAN value in the original CFM up message to ensure that the egress CFM up message edit is effective, and flooding the CFM up message with the count stamp to the primary and backup paths via multicast, thereby implementing the CFM up message multicast service.

[0040] The method of the embodiment of the present invention is implemented by electronic devices, so it is necessary to introduce the relevant electronic devices. Based on this purpose, the embodiment of the present invention provides an electronic device, such as Figure 3As shown, the electronic device includes: at least one processor, a communications interface, at least one memory, and a communications bus, wherein the at least one processor, the communications interface, and the at least one memory communicate with each other via the communications bus. The at least one processor can call logic instructions in the at least one memory to execute all or part of the steps of the methods provided in the aforementioned method embodiments.

[0041] In addition, the logic instructions in the at least one memory mentioned above can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each method embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0042] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0043] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the existing technology can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiment.

[0044] The flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions and operations of the systems, methods and computer program products according to multiple embodiments of the present invention. Based on this understanding, each box in the flowchart or block diagram can represent a module, program segment or part of the code, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, or sometimes in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0045] It should be noted that the terms "comprise," "include," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, the elements defined by the phrase "comprise..." do not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising the elements.

[0046] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A CFM up message carrying method for an ODUK protection scenario, characterized in that: include: Discard CFM up messages sent to the backup path; reset the internal loopback interface and configure the internal loopback interface; The target address of the CFM up message sent to the primary path is changed to be the internal loopback interface; and a CFM up message multicast service is established between the primary and backup egresses and the internal loopback interface.

2. The CFM up message carrying method in the ODUK protection scenario according to claim 1, characterized in that: The discarding of the CFM up message sent to the backup path includes: matching the target backup data output port of the CFM up message, determining the Ethernet type and operation code, identifying the CFM up message with an error count stamp, and discarding the CFM up message with the error count stamp.

3. The CFM up message carrying method in the ODUK protection scenario according to claim 2, characterized in that: The resetting of the internal loopback interface and the configuration of the attributes of the internal loopback interface include: setting the input port and output port direction attributes of the internal loopback interface, and not performing any processing on the messages entering and leaving the internal loopback interface.

4. The CFM up message carrying method in the ODUK protection scenario according to claim 3, characterized in that: Changing the destination address of the CFM up message sent to the primary path and determining the destination address as the internal loopback interface includes: matching a destination primary data output port of the CFM up message, determining an Ethernet type and an operation code, identifying a CFM up message for which an egress message editing action has not taken effect, and changing the destination address of the CFM up message for which the egress message editing action has not taken effect to the internal loopback interface.

5. The CFM up message carrying method in the ODUK protection scenario according to claim 4, characterized in that: The target address of the original CFM up message sent to the primary path is changed to the internal loopback interface, while ensuring that the original bandwidth and priority of the CFM up message sent to the primary path are not affected.

6. The CFM up message carrying method in the ODUK protection scenario according to claim 5, characterized in that: The establishing of the CFM up message multicast service between the primary and backup egresses and the internal loopback interface includes: changing the vlan value in the original CFM up message sent to the primary path according to the relevant service configuration, and ensuring that the egress CFM up message editing takes effect.

7. The CFM up message carrying method in the ODUK protection scenario according to claim 6, characterized in that: The establishing of the CFM up message multicast service between the primary and backup egresses and the internal loopback interface includes: flooding the CFM up message with a count stamp that is sent to the primary path and has been correctly edited to the primary and backup paths through multicast, thereby realizing the multicast service of the CFM up message.

8. A CFM up message carrying device for an ODUK protection scenario, characterized in that: include: The first main module is used to discard CFM up messages sent to the backup path; The second main module is used to reset the internal loopback interface and configure the internal loopback interface. The third main module is used to change the destination address of the CFM up message sent to the primary path and determine the destination address as the internal loopback interface. The fourth main module is used to establish a CFM up message multicast service between the primary and backup egress ports and the internal loopback interface.

9. An electronic device, characterized in that: include: At least one processor, at least one memory and a communication interface; wherein, The processor, memory and communication interface communicate with each other; The memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the method according to any one of claims 1 to 5.

10. A non-transitory computer-readable storage medium, characterized in that The non-transitory computer-readable storage medium stores computer instructions, which cause the computer to execute the method of any one of claims 1 to 5.

Images