WO2016177229A1

WO2016177229A1 - Method and apparatus for processing operation, administration and maintenance oam messages

Info

Publication number: WO2016177229A1
Application number: PCT/CN2016/078168
Authority: WO
Inventors: 赵玉海
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-07-27
Filing date: 2016-03-31
Publication date: 2016-11-10
Also published as: CN106712983A; CN106712983B

Abstract

Provided in the present invention are a method and apparatus for processing operation, administration and maintenance OAM messages. The method comprises: acquiring an OAM message from a network side; determining whether the OAM message is a non-home line card OAM; and sending the OAM message to a switching network when determining that the OAM message is the non-home line card OAM. With the present invention, the problem of large cache overhead in line card OAM queues in related techniques is solved, and further the effect of lowering the cache overhead in line card OAM queues is achieved.

Description

Operation, management and maintenance OAM message processing method and device

Technical field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for processing, managing, and maintaining an OAM message.

Background technique

Explain a few concepts first:

Centralized architecture: When the management plane, control plane, and forwarding plane are concentrated on one board of the main control board, the architecture is called a centralized architecture. As shown in Figure 1.

Distributed architecture: The management plane and the control plane are completed on the main control board. The forwarding plane is exchanged by a separate line card through the switch line card, and the architecture of the downlink card to complete packet encapsulation and forwarding is called a distributed architecture. Figure 2 shows.

Distributed network side queue scheduling management architecture: In the distributed system architecture, the system in which the forwarding plane packets are encapsulated and managed after the downlink card is encapsulated is called the distributed network side scheduling management architecture, as shown in Figure 3. .

Distributed switching side queue scheduling management architecture: In the distributed architecture, the forwarding plane packet is enqueued before the uplink card enters the exchange, and the architecture of the downlink card queue scheduling manager for scheduling and forwarding is called the distributed switching side. The queue scheduling management architecture is shown in Figure 4.

In the distributed switching side queue scheduling management architecture, the TP OAM packet can be used in the distributed switching side queue scheduling management architecture. The online card is generated and terminated by the working path, and can also be generated and terminated by the online card of the protection path. When one of the line cards is designated to be responsible for OAM generation and termination, the line card is referred to as the OAM home line card, as shown in FIG.

The OAM packet burst problem exists on the TP OAM packet homepage line card in the distributed switching side queue scheduling architecture, as shown in Figure 6: When the T(t) time receives OAM packets from multiple ports at the end of the home line card When the line card sends the OAM rate of the TP OAM generator to the N* port rate instantaneously. If the line card is required to match the upload rate of the device sent by the message and the TP OAM generator port rate match, then their port rate will reach up to T or even dozens of T (of which 1T=1000Gbps), the current chip Certainly not satisfied. This requires that the OAM must have enough cache M to store these messages before being sent. The calculation formula of the cache M is as follows:

M=N×Speed×△t–S×△t (1)

Where Δt is the duration of receiving OAM, N is the number of ports on which the line card receives OAM messages, and S is the rate at which the line card is sent.

The above formula for calculating Δt is as follows:

△t=(OAM message length L+exchange head H)×3×fast OAM instance number M/line card number O×8bit/byte/S (2)

Wherein, O is the average of the transmitting side OAM allocated on the O block line card.

The protection switching is triggered because no fast OAM packet is detected between the Message Exchange Pattern (MEP) in 10ms. Therefore, only the OAM occupation buffer size within 10ms needs to be calculated. According to the 3.3ms fast OAM packet, 3 OAM packets will be generated in 10ms.

Substituting Δt into the above formula (1) yields:

M=(N×Speed–S)×3×(OAM message length L+exchange head H)×(fast OAM instance number M/line card number O)×8bit/byte/S (3)

Expand formula (3) to get:

M={(N×Speed–S)×3×(OAM message length L+exchange header H)×8bit/byte/(S×line card number O)}×(fast OAM instance number M) (4)

For a given rack and line card, {(N×Speed–S)×3×(OAM message length L+swapping head H)×8bit/byte/(S×line card number O)} is a constant K. Therefore, the M on the specified rack and line card is simplified to:

M=K× fast OAM instance number M (5)

It can be seen from the above formula (5) that the cache M is positively correlated with the number of OAM instances of the line card, and the more the number of OAM instances, the larger the cache M. The cache M will reach 10Mbytes or even tens of Mbytes.

Due to the existence of the home line card scene, in the extreme case, the line card ∑ M = the number of line cards N * M. If calculated according to the 32-line card, the overhead cache will need to reach several hundred MBytes or even several GBytes.

As can be seen from the above, the OAM queue cost calculation is complicated and the OAM queue cache overhead per line card is large.

Aiming at the problem that the line card OAM queue cache overhead is large in the related art, an effective solution has not been proposed yet.

Summary of the invention

The embodiment of the invention provides a method and a device for processing, managing and maintaining an OAM packet, so as to at least solve the problem that the line card OAM queue cache overhead is large in the related art.

According to an embodiment of the present invention, a method for processing, managing, and maintaining an OAM packet is provided, including: obtaining an OAM packet from a network side; determining whether the OAM packet is a non-destination line card OAM; and determining the OAM When the packet is OAM, the OAM packet is sent to the switching network.

In the embodiment of the present invention, determining whether the OAM message is a non-destination line card OAM includes: obtaining an identifier of the OAM message; and determining, according to the identifier, whether the OAM message is a non-home line card OAM.

In the embodiment of the present invention, before obtaining the OAM packet from the network side, the method further includes: assigning a queue number to each line card in the network element, wherein the queue number of the same line card is the same, and the queue numbers of different line cards are different. When the OAM packet is determined to be a non-destination line card OAM, sending the OAM packet to the switching network includes: sending the OAM packet according to the queue number. The OAM packet belongs to the queue corresponding to the line card; the queue number is written to the switching header; and the OAM packet is sent to the switching network.

In the embodiment of the present invention, after the OAM packet is sent to the switching network, the method further includes: acquiring the OAM packet from the switching side; and resending the OAM packet into the destination line of the OAM packet according to the queue number carried in the switching header. The card corresponds to the queue.

In the embodiment of the present invention, when the OAM packet is determined to be the home line card OAM, the method further includes: setting a buffer size of the queue corresponding to the home line card of the OAM packet to a preset value, wherein the preset value is The cached value calculated by the maximum number of OAM packets of the home line card of the OAM packet.

According to another embodiment of the present invention, an apparatus for processing, managing, and maintaining an OAM packet is provided, including: a first acquiring module, configured to acquire an OAM packet from a network side; and a determining module configured to determine an OAM packet Whether it is a non-destination line card OAM; and the first sending module is configured to send the OAM message to the switching network when it is determined that the OAM message is a non-destination line card OAM.

In the embodiment of the present invention, the determining module includes: an obtaining unit, configured to obtain an identifier of the OAM message; and a determining unit, configured to determine, according to the identifier, whether the OAM message is a non-destination line card OAM.

In the embodiment of the present invention, the device further includes: an allocation module, configured to allocate a queue number to each line card in the network element, wherein the queue numbers of the same line card are the same, and the queue numbers of different line cards are different, first The sending module includes: a first sending unit, configured to send the OAM packet to the queue corresponding to the destination line card of the OAM packet according to the queue number; the writing unit is configured to write the queue number to the switching header; and the second sending unit , set to send OAM packets to the switching network.

In the embodiment of the present invention, the device further includes: a second acquiring module, configured to acquire an OAM packet from the switching side; and a second sending module, configured to re-send the OAM packet into the OAM according to the queue number carried by the switching header The destination line of the message is in the queue corresponding to the line card.

In the embodiment of the present invention, when the OAM packet is determined to be the home line card OAM, the device further includes: a setting module, configured to set a cache size of the queue corresponding to the home line card of the OAM packet to a preset value, where The default value is the cached value calculated based on the maximum number of OAM packets of the home line card of the OAM packet.

In the embodiment of the present invention, a computer storage medium is further provided, and the computer storage medium may store an execution instruction, where the execution instruction is used to execute the OAM message processing method.

In the embodiment of the present invention, the OAM packet is obtained from the network side; the OAM packet is determined to be a non-destination line card OAM; and the OAM packet is sent to the switching network when the OAM packet is determined to be a non-destination line card OAM. The invention solves the problem that the line card OAM queue cache overhead is large in the related technology, thereby achieving the effect of reducing the line card OAM queue buffer overhead.

DRAWINGS

The drawings described herein are provided to provide a further understanding of the invention, which form a part of this application, The illustrative embodiments and the description thereof are illustrative of the invention and are not to be construed as limiting the invention. In the drawing:

1 is a schematic diagram of a centralized architecture according to the related art;

2 is a schematic diagram of a distributed architecture according to the related art;

3 is a schematic diagram of a distributed network side scheduling management architecture according to the related art;

4 is a schematic diagram of a distributed switching side scheduling management architecture according to the related art;

5 is a schematic diagram of a distributed switching side scheduling management TP OAM homeboard according to the related art;

6 is a schematic diagram of a distributed switching side scheduling management TP OAM traffic burst according to the related art;

7 is a flowchart of a method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a non-homed line card OAM message sent to an FPGA according to an embodiment of the present invention; FIG.

9 is a schematic diagram of sending a non-homed line card OAM message to an FPGA according to the prior art;

10 is a schematic diagram of a static queue number based on a line card slot according to an embodiment of the present invention;

11 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM message according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of a general linear PW protection scenario according to an embodiment of the present invention; FIG.

FIG. 13 is a schematic diagram of a 12K DNI PW protection scenario according to an embodiment of the present invention; FIG.

FIG. 14 is a schematic diagram of a general linear PW protection OAM aggregation scenario according to an embodiment of the present invention; FIG.

15 is a schematic diagram of a 12K DNI PW protection OAM aggregation scenario according to an embodiment of the present invention;

16 is a schematic diagram of OAM transmission according to an embodiment of the present invention;

17 is a schematic diagram of a format of an OAM message sent by an FPGA according to an embodiment of the present invention;

FIG. 18 is a schematic diagram of a format of an OAM message sent by an NP to a switching network according to an embodiment of the present invention; FIG.

19 is a schematic diagram of a format of an OAM packet sent by an NP to an SA message according to an embodiment of the present invention;

20 is a schematic diagram of a format of an FPGA message sent by an NP in an OAM message according to an embodiment of the present invention;

21 is a schematic diagram of a process of entering an LSP/PW fast OAM according to an embodiment of the present invention;

22 is a schematic diagram of a process flow of a unicast outflow point module according to an embodiment of the present invention;

FIG. 23 is a schematic diagram of a process of sending an Egress MPLS-TP LSP/PW OAM packet according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that, in the absence of conflict, The embodiments in the present application and the features in the embodiments may be combined with each other.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

In this embodiment, a method for processing, managing, and maintaining an OAM packet is provided. FIG. 7 is a flowchart of a method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. The process includes the following steps:

Step S102: Obtain an OAM packet from the network side.

Step S104: Determine whether the OAM message is a non-destination line card OAM.

The non-destination line card OAM means that the home line card of the OAM message is not the line card that generates the OAM message, but other line cards. The home line card OAM is the line card of the OAM message, that is, the line card that generates the OAM message, that is, the home line card of the OAM message is the line card.

Specifically, whether the home line card is added to the OAM packet is the line card label. Optionally, determining whether the OAM message is a non-destination line card OAM includes: obtaining an identifier of the OAM message; and determining, according to the identifier, whether the OAM message is a non-home line card OAM.

The identifier is used to mark whether the home line card of the OAM message is the line card. For example, if the value of the identifier is 1, it indicates that the home line card of the OAM packet is the line card, that is, the OAM message is the home line card OAM. When the identifier value is 0, it indicates the destination line of the OAM message. The card is another line card, that is, the OAM message is a non-home line card OAM.

In step S106, when it is determined that the OAM packet is a non-destination line card OAM, the OAM packet is sent to the switching network.

In the embodiment of the present invention, when the OAM packet is determined to be a non-destination line card OAM, in order to reduce the buffering overhead of the line card queue, the OAM packet is sent to the switching network, and is exchanged and sent to the home line card through the switching network.

Specifically, FIG. 8 is a schematic diagram of a non-homed line card OAM message sent to an FPGA according to an embodiment of the invention. As shown in Figure 8, the inter-board OAM packet passes through the switching network and then reaches the network processor (Network Processer, NP for short). The NP sends the OAM packet that is not the trunk card to the switching network, and the switching network sends it to the NP. The NP then sends the OAM message to a Field Programmable Gate Array (FPGA). FIG. 9 is a schematic diagram of the non-homed line card OAM message sent to the FPGA according to the prior art. As shown in FIG. 9, the non-home line card OAM message is directly sent to the FPGA after being sent to the home line card. As can be seen from the above, the embodiment of the present invention significantly reduces the buffer overhead of the line card queue compared to the prior art.

The embodiment of the present invention obtains an OAM packet from the network side, determines whether the OAM packet is a non-destination line card OAM, and sends an OAM packet to the switching network when it is determined that the OAM packet is a non-destination line card OAM. The invention solves the problem that the line card OAM queue cache overhead is large in the related art, thereby achieving the effect of reducing the line card OAM queue buffer overhead.

Preferably, the method further includes: assigning a queue number to each line card in the network element, before the OAM message is obtained from the network side, in order to facilitate the rapid loading of the OAM message into the queue of the corresponding home line card. The queue numbers of the same line card are the same, and the queue numbers of different line cards are different.

The embodiment of the present invention allocates a queue number to each line card in the network element in advance. Specifically, the queue number of each line card may be assigned a number according to the slot number of each line card. FIG. 10 is a schematic diagram of a static queue number based on a line card slot according to an embodiment of the invention. As shown in Figure 10, the queue resource numbers assigned to each line card on line card A, line card B, and line card C are x, y, and z, that is, the queue mapping relationship is x--> line card A, y --> Line card B, z--> line card C. As can be seen from FIG. 10, the same line card corresponds to the same queue resource number (ie, number) in different queues, and the queue resource numbers of different line cards are different.

When the OAM packet is sent to the switching network, the OAM packet is sent to the queue corresponding to the destination line card of the OAM packet according to the queue number. The queue number is written to the switching header; and the OAM packet is sent to the switching network.

As the number of the line card queues is assigned in advance, the OAM packets can be sent to the queue corresponding to the home line card of the OAM packet according to the queue number, and the queue number is written into the switching header so that the subsequent The queue number sends the OAM packet to the queue corresponding to its destination line card.

Optionally, after the OAM packet is sent to the switching network, the method further includes: acquiring the OAM packet from the switching side; and correspondingly sending the OAM packet to the destination line card of the OAM packet according to the queue number carried by the switching header. In the queue.

In the embodiment of the present invention, since the uplink and downlink line cards have the same queue number assigned to the line card, it is ensured that the OAM message received by the line card from the switching side or the network side enters a queue.

Preferably, when determining that the OAM message is the home line card OAM, the method further includes: setting a buffer size of the queue corresponding to the home line card of the OAM message to a preset value, wherein the preset value is based on the OAM message. The cached value calculated from the maximum number of OAM packets of the home line card.

After determining that the OAM message is the home line card OAM, the embodiment of the present invention sends the home line card OAM directly to the switching network for scheduling management. Therefore, a larger buffer needs to be allocated for the queue of the home line card OAM. Specifically, the queue cache maximum value M (ie, a preset value) may be calculated according to the maximum number of OAM packet entries per line card in the current system. When the OAM packet is determined to be the home line card OAM, the OAM report is used. The queue corresponding to the destination line card of the text is set to M.

It can be seen that, in the embodiment of the present invention, the non-destination line card OAM message is sent back to the switching network and sent back to the home network, and the OAM message of the home line card is directly sent and sent through the switching network scheduling management, thereby making the non-destination The line card OAM packet only needs to occupy the default queue cache. Only the OAM packet of the home line card needs to occupy a larger queue cache, which reduces the OAM packet queue buffer overhead per line card, thus solving the OAM queue cost calculation complex and each line. The card OAM packet queue cache has a large overhead.

According to another embodiment of the present invention, in order to ensure that only one queue of the line card terminates the OAM, each line card occupies a larger cache, and the other line card OAM occupies a default queue cache. The OAM is operated, managed, and maintained in the embodiment of the present invention. The packet processing method includes the following steps:

Step 1: Assign each line card queue according to the line card slot number, as shown in Figure 10. The queue resource numbers assigned to each line card on line card A, line card B, and line card C are x, y, and z, that is, the queue mapping relationship is x--> line card A, y--> line card B , z--> line card C.

Step 2: Calculate the theoretical queue cache maximum value M according to the current system configurable maximum number of OAM message entries per line card.

Step 3: The default size of each line card initialization queue. When the queue mapping relationship is the line card, set the OAM queue size to M.

Step 4: After receiving the OAM from the network side, the uplink line card is enqueued according to the OAM home line card slot. When the home line card is not itself, the queue number is carried on the switch head, so that the downlink card can be sent to the static queue allocated for the line card after the OAM message is extracted from the switch network, thereby ensuring that only the line card is set for each line card. One queue of the line card terminating OAM occupies a larger cache, and other cross-line cards OAM occupy the default queue cache.

Specifically, on the uplink card, the queue number is assigned first, and then each queue cache is configured. After receiving the OAM packet, the enqueue management module processes the enrollment. If the OAM packet is the home line (that is, the OAM packet is the OAM packet), the OAM packet is scheduled and managed by the switching network. After the line card of the OAM packet is another line card (that is, the OAM message is a non-destination line card OAM message), the message is sent to the corresponding queue according to the queue number assigned by A, and Write the queue number to the exchange header. After the OAM packet is exchanged, the downlink card is re-entered by the queue number carried by the switching head after the OAM packet is extracted from the switching side. The subsequent process repeats the enqueue process and the extraction process. In the embodiment of the present invention, since the uplink and downlink line cards have the same queue number assigned to the line card, the OAM message received by the line card from the switching side or the network side is entered into a queue, thereby ensuring each line card. Only one queue of the line card termination OAM occupies a large cache, and other cross-line cards OAM occupy the default queue cache.

Compared with the prior art, the OAM packet processing method in the embodiment of the present invention reduces system complexity and saves exchange storage space.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

An apparatus for processing, managing, and maintaining an OAM packet is provided in this embodiment. The apparatus is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 11 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. As shown in FIG. 11, the apparatus includes: a first obtaining module 10, a determining module 20, and a first sending module 30.

The first obtaining module 10 is configured to obtain an OAM packet from the network side.

The determining module 20 is configured to determine whether the OAM message is a non-home line card OAM.

Optionally, the determining module 20 includes: an obtaining unit, configured to acquire an identifier of the OAM message; and a determining unit, configured to determine, according to the identifier, whether the OAM message is a non-home line card OAM.

The first sending module 30 is configured to send the OAM packet to the switching network when it is determined that the OAM packet is the non-home line card OAM.

In the embodiment of the present invention, when the OAM packet is determined to be a non-destination line card OAM, the OAM packet is sent to the switching network, and is re-sent to the destination line card after being exchanged via the switching network, in order to reduce the buffering overhead of the line card queue.

In the embodiment of the present invention, the first obtaining module 10 obtains an OAM packet from the network side; the determining module 20 determines whether the OAM packet is a non-destination line card OAM; and the first sending module 30 determines that the OAM packet is a non-destination line card. The OAM packet is sent to the switching network. The invention solves the problem that the line card OAM queue cache overhead is large in the related art, thereby achieving the effect of reducing the line card OAM queue buffer overhead.

Optionally, the device further includes: an allocating module, configured to allocate a queue number to each line card in the network element, wherein the same line card has the same queue number, and different line cards have different queue numbers, and the first sending module includes The first sending unit is configured to send the OAM packet to the queue corresponding to the destination line card of the OAM packet according to the queue number; the writing unit is configured to write the queue number to the switching header; and the second sending unit is set to Send the OAM packet to the switching network.

Optionally, the device further includes: a second acquiring module, configured to obtain an OAM packet from the switching side; and a second sending module, configured to re-deliver the OAM packet into the OAM packet according to the queue number carried by the switching header The destination line card corresponds to the queue.

Optionally, when determining that the OAM message is the home line card OAM, the device further includes: a setting module, configured to set a cache size of the queue corresponding to the home line card of the OAM message to a preset value, where the preset The value is the cached value calculated based on the maximum number of OAM packets of the home line card of the OAM packet.

According to another embodiment of the present invention, in order to ensure that only one queue of the line card terminates the OAM, each line card occupies a larger cache, and the other line card OAM occupies a default queue cache. The OAM report is operated, managed, and maintained in the embodiment of the present invention. The text processing device includes the following modules: a queue number pre-allocation module A, a queue size configuration module B, an enqueue management module C, an OAM message extraction module D, an E module, an F module, and a G module, wherein the E module is set to make the whole The pre-allocated OAM packet queue number is the same on each line card in the NE. The F module is set so that the uplink card is enqueued according to the queue number assigned by A, and the queue number is written to the switch header. The G module is set to make the downlink line. The OAM packet extracted by the card from the switching side is carried by the exchange header. The queue number is entered into the queue.

Specifically, in the uplink card, the queue number is first allocated according to the queue number pre-allocation module A, and then each queue cache is configured by the queue size configuration module B. After receiving the OAM packet, the enqueue management module C processes the enqueue. If the OAM packet is the home line (that is, the OAM packet is the OAM packet of the home line card), the OAM packet is scheduled by the switching network. After the management, the OAM packet extraction module D is sent and sent; if the home line card of the OAM packet is another line card (that is, the OAM message is a non-destination line card OAM message), it is processed by the F module. Specifically, the F module sends the message to the corresponding queue according to the queue number assigned by A, and writes the queue number to the exchange header. After the OAM packet is exchanged, the G-module is processed by the G-module. Specifically, the OAM packet extracted from the switching-side line is re-entered by the queue number carried in the switching header. The subsequent process repeats the C module and The D module performs processing. In the embodiment of the present invention, the queue number assigned by the E-module to the line card is the same, and the OAM packet received by the line card from the switching side or the network side is entered into a queue. Each line card only sets the line card to terminate the OAM. One queue occupies a larger cache, and the other line card OAM occupies the default queue cache.

Several application scenarios of the embodiments of the present invention are described below.

scene 1

A normal linear pseudowire (Pseudo Wire, PW for short) protects the environment (point-to-point), as shown in Figure 12. The 12K common linear PW protection group, the working OAM and the protection OAM are respectively configured on four boards. The Continuity Check (CC) packet transmission period is 10 ms. The Auto Protect Switch (APS) packet transmission rule is: When there is a change, each OAM ID immediately sends 3 APSs. Packets, when there is no change, send 3 APS packets for each OAM ID at 5s.

Scene 2

Dual Node Interconnection Pseudo Wire (DNI PW) environment (point-to-point), as shown in Figure 13. The 12K DNI PW protection group is also configured. There is also a burst of communication messages between the active and standby nodes, which is larger than the normal linear protection burst. The period in which CC packets are sent is 10 ms. The master node needs to send the PW alarm and the STM (ETH) port alarm to the standby node. The standby node needs to send the PW protection group decision and the MSP protection group decision/this point ETH port alarm to the master node. The information transmitted by the active and standby nodes is in the format of APS packets, but the opcode is different. We call it an APS packet. The packet is sent in the same format as the APS packet. When there is a change, each OAM ID immediately sends three packets. When there is no change, each OAM ID sends 3 APS packets.

Scene 3

Ordinary linear PW environment (OAM convergence), as shown in Figure 14. Configure the normal linear PW protection group 8K. The working OAM of the network element 1 is configured on two line cards. Each line card is configured with 4K, and the protection OAM is also configured. The CC transmission period is 10ms, the network element 2 works 8K OAM is configured on one line card, and the protection 8K OAM is also configured on one line card. The APS packet sending rule is that each OAM ID immediately sends three APS packets when there is a change. When there is no change, each OAM ID sends three APS packets at the 5s timing.

Scene 4

DNI PW environment (OAM aggregation), as shown in Figure 15. As in scenario 2, the DNI PW sends 8K OAMs respectively configured on two line cards, and the receiving part 8K OAM is configured on one line card.

The following describes the OAM delivery process:

The OAM message is generated and terminated by the FPGA, and the transmission process passes through the NP and the switching network. Figure 4 shows four points to illustrate the change of OAM packet length during transmission.

On the 1st point, the OAM message is sent by the FPGA. The format of the OAM message is the longest. The TC indicates the forwarding level, the LSP Label indicates the tunnel label, the PW Label indicates the pseudo line label, and the Channel Type indicates the channel. Type, ITMH indicates the incoming TM header, and NPH indicates the NP header.

The length of the packet sent by the CC is: 12byte(NPH)+12byte(label)+75byte(PDU)+4byte(FCS)=103byte

Length of APS packet sent: 12byte(NPH)+12byte(label)+9byte(PDU)+4byte(FCS)=64byte (fill padding)

For scenario 1:

CC message traffic = 103 × 100 × 8000 × 8 = 659200000bit / s

APS packet traffic = 64 × 3 × 8000 × 8 = 12288000 bit / s

The sum of the two = 671488000 bit / s, about 691Mbps.

For scenario 2:

CC message traffic = 103 × 100 × 8000 × 8 = 659200000bit / s

APS packet traffic = 64 × 3 × 2 × 8000 × 8 = 24576000bit / s

The sum of the two = 683,776,000 bits / s, about 683 Mbps.

The format of the packet sent by the NP on the OAM packet is shown in Figure 18. The DA indicates the destination MAC address, the SA indicates the source MAC address, the TC indicates the forwarding level, the LSP Label indicates the tunnel label, and the PW Label indicates the pseudowire label. Type indicates the channel type.

The length of the packet sending CC is: 18byte (MAC+VLAN+TYPE)+12byte(label)+75byte(PDU)+4byte(FCS)=109byte;

Length of APS packet sent: 18byte (MAC+VLAN+TYPE)+12byte(label)+9byte(PDU)+4byte(FCS)=64byte (fill padding).

For scenario 1:

CC message traffic = 109 × 100 × 8000 × 8 = 697,600,000 bits / s

APS packet traffic = 64 × 3 × 8000 × 8 = 12288000 bit / s

The sum of the two = 709888000bit /, about 710Mbps.

For scenario 2:

CC message traffic = 109 × 100 × 8000 × 8 = 697,600,000 bits / s

APS packet traffic = 64 × 3 × 2 × 8000 × 8 = 24576000bit / s

The sum of the two = 722176000 bit / s, about 722 Mbps.

The format of the packet sent by the NP to the switch chip SA is shown in Figure 19. The DA indicates the destination MAC, the SA indicates the source MAC address, the TC indicates the forwarding level, the LSP Label indicates the tunnel label, and the PW Label indicates the pseudo line label. Type indicates the channel type.

The length of the message sent by the CC is: 4byte(ITMH)+16byte(NPH)+20byte(NFH)+18byte(MAC+VLAN+TYPE)+12byte(label)+75byte(PDU)+4byte(FCS)=149byte

Length of APS message sent: 4byte(ITMH)+16byte(NPH)+20byte(NFH)+18byte(MAC+VLAN+TYPE)+12byte(label)+9byte(PDU)+4byte(FCS)=106byte (with padding) byte)

For scenario 1:

CC message traffic = 149 × 100 × 8000 × 8 = 95,360,000 bit / s

APS packet traffic = 106 × 3 × 8000 × 8 = 16896000 bit / s

The sum of the two = 973952000 bit / s, about 974Mbps.

For scenario 2:

CC message traffic = 149 × 100 × 8000 × 8 = 95,360,000 bit / s

APS packet traffic = 106 × 3 × 2 × 8000 × 8 = 33792000bit / s

The sum of the two =994304000bit/s, about 994Mbps.

The packet format of the FPGA sent by the NP on the 4th point is shown in Figure 20.

It can be seen from the comparison that the FPGA reception has 8 bytes more than the transmission compared with the FPGA transmission. If you want to ensure that this port does not lose packets, the bandwidth on the transmitting side of the FPGA cannot exceed 1GE × (103/111) = 928Mbps.

The following describes the OAM emergencies:

The traffic values as described above are calculated assuming OAM is evenly transmitted. In fact, the implementation of the FPGA is that the 8K CC message and the APS message are sent at a full bandwidth rate in a short period of time. In the worst case, the 8K CC message and the 8K APS message need to be sent at the same time.

For scenario 1 and scenario 2, since the bandwidth of the receiving port and the sending port of the FPGA are basically equal to 1GE, there is no sudden situation.

For scenario 3, the extreme case is that the CC packets of the line card 3 and the line card 4 are simultaneously sent by the APS, and the line card 6 receives 2GE packets from different ports in the same time period, and aggregates them to the SA40, and then sends them. To NP, the NP is sent to the FPGA. During this period, the ingress message is 2 GE and the egress is 1GE. Then the SA40 needs to cache the time packet.

Cache size M=2×1024000000×T–1×1024000000×T (T is the OAM message continuous packet sending time)

For CC messages: T = ((109 + 8 + 12) × 4000 × 8) / 1024000000 = 0.00403125s

109 is the length of the packet, 8 is the preamble, and 12 is the frame gap.

The buffer size M = 2 × 1024000000 × T - 1 × 1024000000 × T = 1024000000 × 0.00403125 = 4128000bit = 0.49 Mbytes.

The above is the case where two ports are aggregated. In theory, there are a maximum of 32 ports aggregated.

Then from the above calculation method, a general formula can be introduced:

Assume that the 8K OAM is evenly distributed on the N boards, and then the receivers are aggregated by the N ports of a single board.

T=((Message length +8+12)×(8000/N)×8)/1024000000

Substituting the above T into the buffer size gives: M = N × 1024000000 × T - 1 × 1024000000 × T

=(N-1)×1024000000×((Message length +8+12)×(8000/N)×8)/1024000000

=((N-1)/N)×(message length +8+12)×8000/(1024×1024) Mbytes

The length of the CC packet is 109 bytes, and the length of the APS packet is 64 bytes. Three packets need to be sent consecutively.

Substituting the above formulas separately, the calculated sum is: 2.9MByte.

For scenario 4:

The amount of CC packets sent is the same, and the amount of APS packets sent is twice that of Scene 3. Also calculate the sum of the two according to the formula: 4.8MBytes.

The following describes the storage:

The switch chip SA has a total of 1024 blocks, and each block has a default size of 1024 bytes. A packet smaller than 1024 bytes occupies one block. The OAM packet sent by the NP to the switching chip SA is 129 bytes long, and actually occupies 1024 bytes, and the usage rate is 129/1024=1.2.6%, that is, the actual overhead is nearly 8 times larger than the theoretical amplification.

The following describes the queue allocation:

Each line card reserves a queue according to the slot number in the rack diagram. The number of OAM queues reserved for each slot line card is equal to the slot number.

The following describes the OAM bypass of the non-home line card:

The poor implementation is shown in Figure 9. The inter-board OAM passes through the switching network and reaches the NP, and the NP is directly transferred to the FPGA.

In this scenario, to prevent an emergency, the cache needs to be set on line card 1. Then the line size of the line card 1 needs to be set to:

4.8MByte×8×32=1228.8Mbyte (8 is about 8 times the space for SA storage and 32 is the slot number).

In order to save the cache, the process can be changed as shown in Figure 8. After the inter-board OAM passes through the switching network, it reaches the NP. The NP is sent back to the switching network by the OAM of the home board on the local board, and the switching network is sent to the NP, and the NP is sent to the FPGA. In this case, the processing flow is the same as that of the OAM homeboard on the board. The buffer size required for each line card is: 4.8 MByte×8=38.4 Mbyte.

To support the wraparound solution, the NP label entry of the NP increases whether the OAM packet attribution line card is the line card label.

No_local_card_end: 0, the home line card is the line card; 1, the home line card is not the line card.

The unicast NPH adds the LSP/PW fast OAM packet to the non-line card termination identifier.

No_local_card_end (abbreviated as N_C_E): 0, the home line card is the line card; 1, the home line card is not the line card.

Flow_id: Query the queue_map table to get.

FIG. 21 is a schematic diagram of an Inges LSP/PW fast OAM processing process according to an embodiment of the present invention. As shown in FIG. 21, the ingress LSP/PW fast OAM processing process includes the following steps:

Step S202: No_local_card_end=1?

The No_local_card_end is a board termination identifier, where step S206 is performed when the board is terminated (ie, No_local_card_end=1), otherwise step S204 is performed.

Step S204: NFH.U_CPU.F_S=1; NPH.U_CPU.N_C_E=0.

The above NFH.U_CPU.F_S is the uplink logical fast OAM channel identifier, and NPH.U_CPU.N_C_E is the home line identifier of the home line card, wherein the uplink logical fast OAM channel is true (ie NFH.U_CPU.F_S=1) When the home line card is not the board (ie, NPH.U_CPU.N_C_E=0), step S208 is performed.

Step S206: NFH.U_CPU.F_S=1; NPH.U_CPU.N_C_E=1.

Step S208: The original processing flow is sent to the unicast outflow point module.

FIG. 22 is a schematic flowchart of a unicast outflow point module processing process according to an embodiment of the present invention. As shown in FIG. 22, the unicast outflow point module processing flow includes the following steps:

Step S302: Query out_fp table.

The above out_fp table is used to represent the flow point table.

Step S304: Out_fp.type=CPU flow point?

In the above step S304, it is determined whether the flow point is sent to the CPU.

Step S306: Query the fwd_ctrl table.

The above fwd_ctrl table is used to represent the forwarding control table.

Step S308: Query the queue_map table to obtain the flow_id.

The above step S308 is to check the queue mapping table to obtain the flow queue number, wherein the queue_map table represents the queue mapping table, and the flow_id represents the flow queue number.

Step S310: Other unicast outflow point type processing flow.

Step S312: NFH.U_CPU.F_S=1 and NPH.U_CPU.N_C_E=1?

When the uplink logical fast OAM channel is true (ie, NFH.U_CPU.F_S=1) and the home line card is the current board (ie, NPH.U_CPU.N_C_E=1), step S314 is performed, otherwise step S316 is performed.

Step S314: NFH.U_CPU.flow_id=queue_map.flow_id.

The above step S314 indicates that the queue number of the uplink logic is equal to the queue number obtained by the queue mapping table query.

Step S316: The CPU unicasts the other processing flow of the flow point.

FIG. 23 is a schematic diagram of a process of sending an MPLS-TP LSP/PW OAM packet according to an embodiment of the present invention. As shown in FIG. 23, the process of sending an MPLS-TP LSP/PW OAM packet is as follows: step:

Egress entry processing.

Step S402: NPH.main_type=CPU(2)?

The above step S402 is to determine whether the NPH header type is a CPU. When the NPH header type is the CPU, step S406 is performed, otherwise step S404 is performed.

Step S404: Other process processing.

Step S406: NFH.U_CPU.F_S=1 and NPH.U_CPU.N_C_E=1?

When the uplink logical fast OAM channel is true (ie, NFH.U_CPU.F_S=1) and the home line card is the local board (ie, NPH.U_CPU.N_C_E=1), step S410 is performed, otherwise step S408 is performed.

Step S408: Normally uploading the process.

Step S410: NPH.U_CPU.N_C_E=0.

Step S410 means that the home line card is not the board.

Step S412: Obtain a flow_id from the NPH.U_CPU, encapsulate the ITMH, and send the LSP/PW fast OAM message again. Send to SA for processing.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.

Embodiments of the present invention also provide a storage medium. Optionally, in this embodiment, the foregoing storage medium may be configured to store program code for performing the method steps of the above embodiment:

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

The foregoing technical solution provided by the embodiment of the present invention can be applied to the OAM packet processing process, and the OAM packet is obtained from the network side; the OAM packet is determined to be a non-destination line card OAM; and the OAM packet is determined to be non- When the OAM packet is sent to the switching network, the OAM packet buffering overhead is solved in the related art, and the OAM queue buffering overhead of the line card is reduced.

Claims

A method for processing, managing, and maintaining OAM packets, including:

Obtain an OAM packet from the network side.

Determining whether the OAM packet is a non-destination line card OAM;

When it is determined that the OAM packet is the non-home line card OAM, the OAM packet is sent to the switching network.
The method of claim 1, wherein determining whether the OAM message is a non-home line card OAM comprises:

Obtaining an identifier of the OAM message;

Determining, according to the identifier, whether the OAM message is the non-home line card OAM.
The method of claim 1 wherein

Before the OAM packet is obtained from the network side, the method further includes: assigning a queue number to each line card in the network element, where the queue numbers of the same line card are the same, and the queue numbers of different line cards are different.

When it is determined that the OAM packet is the non-home line card OAM, sending the OAM packet to the switching network includes:

Sending the OAM packet to the queue corresponding to the destination line card of the OAM packet according to the queue number;

Writing the queue number to the swap header;

Send the OAM packet to the switching network.
The method of claim 3, wherein after the sending the OAM message to the switching network, the method further comprises:

Obtaining the OAM message from the switching side;

And sending the OAM packet to the queue corresponding to the destination line card of the OAM packet according to the queue number carried by the switching header.
The method of claim 1, wherein when the OAM message is determined to be a home line card OAM, the method further includes:

The buffer size of the queue corresponding to the home line card of the OAM packet is set to a preset value, where the preset value is a cache value calculated according to the maximum number of OAM packets of the home line card of the OAM packet. .
An OAM packet processing device that operates, manages, and maintains, including:

The first obtaining module is configured to obtain an OAM packet from the network side;

a judging module, configured to determine whether the OAM packet is a non-destination line card OAM;

The first sending module is configured to send the OAM packet to the switching network when it is determined that the OAM packet is the non-home line card OAM.
The apparatus of claim 6, wherein the determining module comprises:

An obtaining unit, configured to obtain an identifier of the OAM message;

The determining unit is configured to determine, according to the identifier, whether the OAM message is the non-home line card OAM.
The apparatus according to claim 6, wherein

The device further includes: an allocation module, configured to allocate a queue number to each line card in the network element, wherein the same line card has the same queue number, and different line cards have different queue numbers.

The first sending module includes:

The first sending unit is configured to send the OAM packet to the queue corresponding to the destination line card of the OAM packet according to the queue number;

a write unit configured to write the queue number to the swap header;

The second sending unit is configured to send the OAM packet to the switching network.
The apparatus of claim 8 wherein said apparatus further comprises:

a second acquiring module, configured to acquire the OAM packet from the switching side;

The second sending module is configured to re-send the OAM packet into the queue corresponding to the destination line card of the OAM packet according to the queue number carried by the switching header.
The device according to claim 6, wherein, when it is determined that the OAM message is a home line card OAM, the device further includes:

The setting module is configured to set a buffer size of a queue corresponding to the home line card of the OAM packet to a preset value, where the preset value is a maximum number of OAM packets according to a destination line card of the OAM packet. Calculated cached value.