WO2019015462A1 - Method for sending detection block and method for receiving detection block, and network device and system - Google Patents

Abstract

The present application provides a method, network device, and system for detecting block transmission and reception, wherein a method for detecting a block transmission includes: a network device acquiring an original bit block data stream; generating at least one detection block, inserting the at least one detection block a location of at least one free block in the original bit block data stream; transmitting a bit block data stream comprising the at least one detected block. In the present application, the detection block transmission is performed by occupying the bandwidth resource of the free block in the bit block data stream, thereby solving the problem of loss of the bit block of the service.

Description

Method, network device and system for detecting block transmission and reception Technical field

The present application relates to the field of communications, and in particular, to a method, network device, and system for detecting block transmission and reception.

Background technique

The current Flex Ethernet implementation agreement 1.0 (FlexE IA 1.0) interface technology has been standardized in the optical internetworking forum (OIF). Flexible Ethernet (FlexE) interface technology can be applied to data center equipment interconnection, etc., by binding n 100G physical layer devices (PHYs) to transmit multiple FlexE client services of different speeds. Subsequently, FlexE will also define switching technology, L1.5 layer switching technology, also known as X-Ethernet switching technology or X-E switching technology. L1.5 layer switching technology (ie, X-Ethernet switching technology or XE switching technology) is a bit block (for example, 64B/66B bit block) switching technology based on Ethernet (Ethernet) physical layer, with deterministic ultra-low The technical characteristics of the delay.

FIG. 1 is a schematic diagram of a networking architecture of the prior art adopting the L1.5 layer switching technology. As shown in FIG. 1 , the dotted path is an end-to-end service forwarding path. In the prior art, a method of inserting a detection block in a fixed period is used, for example, a detection block is inserted every N bit blocks, and an L1.5 layer end-to-end failure detection is performed. First, the upstream client signal adaptation unit inserts a detection block, and the downstream network signal adaptation unit also inserts an overhead block. The insertion of the two bit blocks causes the watermark of the network signal adaptation unit to rise, which needs to be performed. Deletion of free blocks. The insertion of the detection block by the prior art technical solution may cause the downstream waterline fluctuation, thereby triggering the deletion of the free block to reduce the waterline fluctuation caused by the insertion of the detection block. Once the processing line is long, or there are many processing links, the water line will overflow, resulting in the loss of the bit block of the service.

Summary of the invention

In view of this, the present application provides a method, a network device, and a system for detecting block transmission and reception, which can solve the problem of detecting a bit block loss of a service during transmission.

In a first aspect, the application provides a method for detecting block transmission, comprising: acquiring, by a network device, a raw bit block data stream; generating at least one detection block, inserting the at least one detection block into at least the original bit block data stream a location of a free block; transmitting a block of bit data stream comprising the at least one detected block.

In the present application, the detection block transmission is performed by occupying the bandwidth resource of the free block in the bit block data stream, thereby solving the problem of loss of the bit block of the service.

In a possible implementation manner, the inserting the at least one detection block into a location of the at least one free block in the original bit block data stream comprises: inserting X detection blocks into the original bit block data stream The position of the X free blocks, X is a positive integer greater than or equal to 1. Optionally, according to the Institute of Electrical and Electronics Engineers (IEEE) 802.3 standard, the detection block is not inserted into the middle of the message, but inserted into the middle of the two messages to maintain the integrity of the message.

In the present application, the number of inserted detection blocks is equal to the number of free blocks to be replaced, and the detection block completely occupies the bandwidth resources of the free block for transmission, which has no impact on the bandwidth of the service, thereby solving the problem of loss of the bit block of the service.

In a possible implementation manner, the at least one detection block carries a flow identifier, where the flow identifier is used to indicate a connection identifier of the original bit block data stream, and a standard such as ITU-T G.709 is used to identify the connection. The information is a trail trace identifier (TTI, which is a meaning of the stream identifier and TTI. For the sake of brevity, this article refers to the stream identifier. In addition, the stream identifier can be defined according to user requirements, when the length is shorter. For a long time, it can be carried by multiple detection blocks sent in succession. That is, several detection blocks respectively carry a part of the flow identification, and the receiver receives multiple detection blocks, and then combines the multiple parts into one complete identification.

In the present application, carrying the flow identifier in the detection block may enable the receiving end to determine whether a connection misconnection occurs according to the flow identifier, and is also referred to as a trace tracking identifier TTI mismatch (TIM), and the flow identifier described herein is a TIM. When the flow identifier needs to be carried by multiple detection blocks that are sent in sequence, the receiver can only determine whether a misconnection occurs after receiving the multiple detection blocks and combining them into a complete flow identifier.

In a possible implementation manner, the at least one detection block further carries a type identifier, and the type identifier may indicate a type of function that the detection block has, for example, the detection block may be used for connectivity detection. The detection block can also be used for other OAM function detection, such as bit interleaved parity (BIP), far end error indication (REI), client signal indication (CS), synchronization (SYNC), service layer alarm indication (AIS). ), Protection Switching Protocol (APS), Time Delay Measurement (DM), etc.

In a possible implementation manner, the at least one detection block may flexibly select whether to carry a preset transmission reference period, where the preset transmission reference period is used to indicate a transmission period of the at least one detection block.

In a possible implementation, the sending period of the at least one detecting block is greater than or equal to a preset sending reference period carried by the at least one detecting block.

In the present application, the transmission period of the detection block may float within a certain range, which is a non-fixed period.

In a possible implementation manner, when a sending period of the at least one detecting block is greater than a preset sending reference period carried by the at least one detecting block, the method further includes: pre-processing the at least one detecting block The transmission reference period is updated to the transmission period of the at least one detection block.

In the present application, the preset transmission reference period may be dynamically changed according to the actual transmission period of the detection block.

In a possible implementation manner, the at least one detection block is an M/N bit block. The detection block may be an encoded bit block, for example, a 64B/66B bit block, an 8B/10B bit block, a 256B/257B bit block, or the like, or may be an uncoded bit block.

In a possible implementation, the free block is added and/or deleted in the bit block data stream, so that the rate of adding and/or deleting the bit block data stream after the free block is compatible with the port rate of the network device Match. For example, a free block may be added and/or deleted in the original bit block data stream, or a free block may be added and/or deleted in the bit block data stream after the insertion of the detection block.

In a second aspect, the application provides a method for receiving a service, comprising: receiving, by a network device, a bit block data stream including at least one detection block; identifying the at least one detection block, replacing the at least one detection block with at least one idle Block; transmitting a bit block data stream after replacing the at least one free block.

In the present application, the detection block reception is performed by occupying the bandwidth resource of the free block in the bit block data stream, thereby solving the problem of loss of the bit block of the service.

In a possible implementation manner, the replacing the at least one detection block with the at least one free block comprises: replacing X detection blocks with X free blocks, where X is a positive integer greater than or equal to 1.

In the present application, the number of received detection blocks is equal to the number of replacement free blocks, and the detection block completely occupies the bandwidth resources of the free block for reception, and has no impact on the bandwidth of the service, thereby solving the problem of loss of the bit block of the service.

In a possible implementation manner, the detecting block carries a flow identifier, where the flow identifier is used to indicate a connection identifier of the bit block data stream, and the method further includes: the network device fails according to the flow identifier Detection.

In this application, the flow identifier is carried in the detection block, and the network device at the receiving end can determine whether the connection is disconnected according to the flow identifier, and can quickly and effectively detect the connection failure. When the flow identifier needs to be carried by multiple detection blocks that are sent in succession, the receiver can only determine whether a misconnection occurs after receiving the multiple detection blocks and combining them into a complete flow identifier.

In a possible implementation manner, the at least one detection block further carries a type identifier, and the type identifier may indicate a type of function that the detection block has, for example, the detection block may be used for connectivity detection. The detection block can also be used for other OAM function detection, such as bit interleaved parity (BIP), far end error indication (REI), client signal indication (CS), synchronization (SYNC), service layer alarm indication (AIS). ), Protection Switching Protocol (APS), Time Delay Measurement (DM), etc. When the detection block carries the type identifier, the network device at the receiving end can also identify the function type of the detection block according to the type identifier.

In a possible implementation manner, the detecting block carries a preset sending reference period, and the method further includes: the network device identifying the at least one detecting block according to the sending reference period.

Carrying a preset transmission reference period in the detection block helps the network device at the receiving end to quickly locate the detection block. When the detection block does not carry the preset transmission reference period, the receiving network device quickly locates the detection block according to the preset period.

In a possible implementation manner, the at least one detection block is an M/N bit block. The detection block may be an encoded bit block, for example, a 64B/66B bit block, an 8B/10B bit block, a 256B/257B bit block, or the like, or may be an uncoded bit block.

In a third aspect, the present application provides a network device, which is used to implement the functions of the first aspect or any one of the possible implementations of the first aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, the application provides a network device, which is used to implement the functions of any of the possible implementations of the second aspect or the second aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present invention provides a network system, including the network device of the third aspect, and the network device of the fourth aspect or the fourth aspect.

Yet another aspect of the present application provides a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the methods described in the above aspects.

Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the prior art, the drawings used in the description of the background and the embodiments will be briefly described below.

1 is a schematic diagram of a networking architecture of a prior art using an L1.5 layer switching technology;

2 is a schematic diagram of a network architecture according to an embodiment of the present invention;

3a-3d are schematic structural diagrams of four network devices PE according to an embodiment of the present invention;

4a-4d are schematic structural diagrams of four network devices P according to an embodiment of the present invention;

5a and FIG. 5b are schematic structural diagrams of two types of packet bearer devices according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a logical structure of a monitoring unit according to an embodiment of the present invention;

7a, 7b, 7c, 7d, 7e, 7f, and 7g are respectively schematic diagrams of coding formats of detection blocks according to an embodiment of the present invention;

FIG. 8 is a flowchart of a method for sending a detection block according to an embodiment of the present invention;

9a, 9b, 9c, and 9d are schematic diagrams of four transmission detection blocks according to an embodiment of the present invention;

10 is a schematic diagram of a logical structure of a detection block sending module according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of a format of a free block according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of rate adaptation according to an embodiment of the present invention;

13a, 13b, 13c, and 13d are flowcharts of a method for receiving a detection block according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of two encoding formats of a detection block according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 16 is a flowchart of a method for sending a fault indication block according to an embodiment of the present invention;

17a, FIG. 17b, and FIG. 17c are flowcharts of three methods for receiving a fault indication block according to an embodiment of the present invention;

FIG. 18a and FIG. 18b are two schematic diagrams of sending multiple OAM function blocks according to an embodiment of the present invention.

Detailed ways

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present invention. As shown in FIG. 2, the network architecture includes network devices (ProviCnnM Edge, PE) XE1 and XE3 deployed on the edge side, and a network device (ProviCnnM, P) XE2 deployed in an intermediate position. The client device is connected to the network device PE of the sending end, and the generated client service (data stream) is transmitted to the network device PE of the receiving end through the network device PE of the sending end and one or more network devices P. In some cases, there may be no network device P in the network. The embodiments of the present invention can be applied to networking such as X-Ethernet, Ethernet, FlexE, IP network, and OTN. The embodiments of the present invention may perform fault detection based on the encoded bit block, such as 64B/66B bit block, 8B/10B bit block, 256B/257B bit block, and the like. Embodiments of the present invention may also perform fault detection based on uncoded bit blocks.

3a-3d are schematic structural diagrams of four network devices PE according to an embodiment of the present invention. As shown in FIG. 3a-3d, the network device PE may include a client signal adaptation unit (uAdpt) 301, a switching unit (for example, may be an L1.5 layer switching unit, or an XE switching unit, an X-Ethernet switching unit, 66). A bit block switching unit or the like) 303, a network signal adaptation unit (nAdpt for short) 304, and a monitoring unit (referred to as CnnM) 302 for implementing connection failure detection. Therein, as shown in FIGS. 3a and 3c, the monitoring unit 302 can be disposed between the client signal adaptation unit 301 and the switching unit 303. As shown in Figures 3b, 3d, the monitoring unit 302 can also be disposed between the switching unit 303 and the network signal adaptation unit 304. An interface connected to a client device by a network device is called a user-to-network interface (UNI). An interface connected to other network devices is called a network-to-network interface (NNI).

4a-4d are schematic structural diagrams of four network devices P according to an embodiment of the present invention. As shown in Figures 4a-4d, the network device P may include network signal adaptation units 401 and 405, and an exchange unit 403. As shown in Figures 4a, 4c, 4d, any one or both of the monitoring units 402 and 404 may also be included. Optionally, as shown in FIG. 4b, the monitoring unit may not be provided. An interface in which network device P is connected to other network devices is called an inter-network interface.

The network devices PE and P in the embodiment of the present invention may be implemented in a packet bearer device, for example, an IP radio access network (IP RAN) device, a packet transport network (PTN) device, or the like. . 5a and 5b are schematic structural diagrams of two types of packet bearer devices according to an embodiment of the present invention. As shown in FIG. 5a and FIG. 5b, the network device PE is used as an example. The packet bearer device may include two types of interface boards, one of which deploys a client-side interface chip, and the other of which has a network-side interface chip. . The packet bearer device may further include a master switch board that deploys the switch network chip. The client signal adaptation unit of Figures 3a-3d can be implemented by a client side interface chip. The network signal adaptation unit of Figures 3a-3d can be implemented by a network side interface chip. The switching unit of Figures 3a-3d can be implemented by a switching network chip. The monitoring unit in FIG. 3a and FIG. 3c may be disposed in the client side interface chip, or may be disposed in a separate field programmable gate array (FPGA) or a network processor (NP). The monitoring unit in FIG. 3b and FIG. 3d may be disposed in the network side interface chip, or may be disposed in a separate FPGA or NP. Alternatively, some functions of the monitoring unit are implemented by a client side interface chip or a network side interface chip, and some functions are implemented by a separate FPGA or NP.

The network device of the embodiment of the present invention adds a monitoring unit for fault detection based on the prior art. FIG. 6 is a schematic diagram of a logical structure of a monitoring unit according to an embodiment of the present invention. As shown in FIG. 6, the network device PE is taken as an example for description. The monitoring unit may include a detection block generation module, a detection block transmission module, a detection block reception module, and the like. The function of each module will be described in detail in the following embodiments.

Referring to the network architecture diagram shown in FIG. 2, it is assumed that the type of the UNI is 1 Gigabit Ethernet (GE), and the type of the NNI is 100 GE. The switching unit may be an L1.5 layer switching unit whose switching granularity is exemplified by a 64B/66B bit block (or 66 bit block). The data flow of the interface between the networks is also described by taking a 66-bit block data stream as an example. XE1 receives the data stream from the client device through the UNI, and is received by XE3 after passing through XE2. After the data stream of XE1-XE2-XE3 forms a connection (or is called a connection data stream, a connection bit block data stream, a bit block data stream, etc.), it is necessary to perform fault detection on the connection, that is, connectivity check (CC) ). The detection process can include the following steps:

Step 1: XE1 generates a detection block.

This step can be implemented by a monitoring unit in XE1, for example, by detecting a block generation module. The detection block carries connectivity detection information, which may also be referred to as a connectivity check block (CCB). The detection block may be an uncoded block of bits or an encoded block of bits (also referred to as a block of code). In the embodiment of the present invention, the detection block is described by taking a 66-bit block as an example, and the coding format thereof can be implemented by extending the 66-bit control block of the prior art. FIG. 7a, FIG. 7b and FIG. 7c are respectively schematic diagrams showing coding formats of three detection blocks according to an embodiment of the present invention. As shown in Figure 7a, the Type field is set to 0x4B and the O code is set to 0x6. The detection block may include a flow identifier (identity, ID), and optionally, a transmission reference period (T). The flow identifier is used to indicate the connection identifier of the data stream of the XE1-XE2-XE3. The transmission reference period is used to indicate the transmission period of the detection block, or the transmission interval of two adjacent detection blocks. Figure 7b adds a stream identifier 0x023 and a transmit reference period 0x400 in the D1-D3 field. Then, the flow identifier indicates that the connection identifier of the data stream of XE1-XE2-XE3 is 0x023, and the transmission reference period indicates that one detection block is inserted every 1024 bit blocks. The transmitting reference period is carried in the detecting block, so that the receiving end detects the detecting block according to the sending reference period. Optionally, the sending reference period may also be directly configured on the receiving end, so that it does not need to be carried in the detecting block. A detection block may also carry only a part of the flow identifier, and the complete flow identifier needs to send n detection blocks to carry, as shown in FIG. 7c, the complete flow identifier is 0x88...4523, and the first detection block sends 0x23, the first The two detection blocks send 0x45 until the last nth detection block sends 0x88. Similarly, T can be sent. FIG. 7d, FIG. 7e and FIG. 7f are respectively schematic diagrams showing coding formats of three other detection blocks according to an embodiment of the present invention. As shown in Figure 7d, the Type field is set to 0x00. The detection block may include a flow identifier (identity, ID), and optionally, a transmission reference period (T). The flow identifier is used to indicate the connection identifier of the data stream of the XE1-XE2-XE3. The transmission reference period is used to indicate the transmission period of the detection block, or the transmission interval of two adjacent detection blocks. Figure 7e adds a stream identifier 0x023 and a transmit reference period 0x400 in the D1-D7 field. Then, the flow identifier indicates that the connection identifier of the data stream of XE1-XE2-XE3 is 0x023, and the transmission reference period indicates that one detection block is inserted every 1024 bit blocks. The transmitting reference period is carried in the detecting block, so that the receiving end detects the detecting block according to the sending reference period. Optionally, the sending reference period may also be directly configured on the receiving end, so that it does not need to be carried in the detecting block. A detection block may also carry only a part of the flow identifier, and the complete flow identifier needs to be sent by multiple detection blocks in succession, as shown in FIG. 7f, the complete flow identifier is 0x88...4523, and the first detection block sends 0x23, the first The two detection blocks send 0x45 until the last nth detection block sends 0x88. Similarly, T can be sent.

The detection block can also be used to implement other operations, administration and maintenance (OAM) functions of connection management, such as bit interleaved parity (BIP) and remote errors for error detection. Remote error indication (REI), customer signal indication (CS), synchronization (SYNC), service level alarm indication signal (AIS), protection switching protocol (APS), delay measurement (delay measurement, DM) and so on. When the detection block is used to implement multiple OAM functions, the detection block can also carry a type identifier for distinguishing different functions. For example, the type of the detection block may include a type of connectivity detection function, and may also include any one or more of the OAM function types described above. As shown in FIG. 7g, type 0x01 identifies the connection detection function, and 0 to 63 respectively identify the 0th to 63rd detection blocks, and each block carries only the 0th to 63rd parts of one flow identifier. Similarly, if the information carried by the other OAM functions needs to be carried by multiple detection blocks, for example, the time stamp carried by the unidirectional DM needs to send multiple detection block bearers in succession, each detection block only carries a part of the time stamp. An OAM information may be carried by one detection block or by at least two detection blocks.

Step 2: XE1 sends a detection block.

This step can be implemented by the monitoring unit of XE1, for example, by detecting the block sending module. Before sending the detection block, XE1 receives the data stream from the client device through the UNI. Optionally, XE1 may encode the received data stream or perform encoding format conversion. For example, the data stream is an 8B/10B encoded data stream. XE1 performs encoding format conversion through the client signal adaptation unit, for example, converting 8B/10B encoding to 64B/66B encoding. For example, 8 efficiently coded 1GE bit blocks (each bit block having a size of 8 bits) are sequentially formed into a 64-bit block, and then a 2-bit sync header is added to form one 66-bit block. A plurality of 66-bit blocks generate a 66-bit block data stream. While generating the 66-bit block data stream, XE1 starts counting according to the transmission reference period start counter, for example, the transmission reference period is "1024". When the counter count reaches 1024 bit blocks, the monitoring unit performs idle block (IDLE) detection. For example, when the counter count reaches 1029 bit blocks, the free block is detected, the detected free block is replaced with the detection block generated in step 1, and the transmission reference period of the detection block is updated to 1029. Then, reset the counter to 0. The bit block data stream enters the switching unit and is sent to the network side through the network signal adaptation unit.

FIG. 8 is a flowchart of a method for transmitting a detection block according to an embodiment of the present invention. As shown in FIG. 8, the method for transmitting a detection block may include the steps of: starting a counter to count the number of bit blocks of the bit block data stream; and starting to detect the bit block data stream when the counter value reaches a preset transmission reference period. When the free block in the bit block data stream is found, the free block is replaced with the detection block to be sent; at this time, if the counter value exceeds the preset transmission reference period, the transmission reference period T in the detection block is updated to The latest counter count value; the bit block data stream is sent.

9a, 9b, 9c, and 9d are schematic diagrams of a transmission detection block according to an embodiment of the present invention. As shown in FIG. 9a and FIG. 9b, the direction of the arrow in the figure is the transmission direction of the bitstream data stream, and the interval between the inserted two detection blocks is 1029 bit blocks, and the transmission reference period of the detection block is updated to 0x405. . Optionally, the sending reference period may be updated according to the actual sending period of the detecting block, that is, the sending reference period field is updated to 0x405. It is also possible not to update the transmission reference period, ie the transmit reference period field is still set to 0x400. In this example, it is possible to flexibly choose whether to carry the transmission reference period in the detection block and whether to refresh the reference period. Optionally, when the detection block does not carry the transmission reference period, the receiving network device detects and receives the detection block according to a preset period. Similarly, when the flow identifier is carried by multiple detection blocks, the detection block sent by FIG. 9a and FIG. 9b carries a part of the content of the flow identifier, as shown in FIG. 9d, the type is 0x01, the identifier is a connection detection block, and 63 is the block. The content of the 63rd part of the stream identifier is carried.

FIG. 10 is a schematic diagram of a logical structure of a detection block sending module according to an embodiment of the present invention. As shown in FIG. 10, when a bit block data stream is received, the start counter counts the number of bit blocks. The bit block data stream is sent to the buffer, and the detection block generated by the detection block generator is inserted into the bit block data stream according to a preset transmission policy. The preset sending policy may include sending a reference period and the like. The default sending policy can be configured by the network management or controller.

In the process of transmitting the detection block described above, it is necessary to detect and replace the free block. FIG. 11 is a schematic diagram of a format of a free block according to an embodiment of the present invention. As shown in FIG. 11, the free block may be a 66-bit block including a 2-bit sync header "10", a type field "0x1E", and 8 "/I/(0x00)". The method of detecting a free block may include matching the sync header "10" and the type field "0x1E", or matching all bits of the free block. In this example, multiple matching methods are used to find the free block, and the bandwidth resource that occupies the free block is transmitted, which has no impact on the service bandwidth.

The method for detecting block transmission by replacing a free block in the embodiment of the present invention is also applicable to transmitting a bit block having other OAM functions, such as bit interleaving parity (BIP) for bit error detection, and remote bit error indication. (REI), Customer Signal Indication (CS), Synchronization (SYNC), Service Layer Alarm Indication (AIS), Protection Switching Protocol (APS), Delay Measurement (DM), and the like. When the detection block is used to implement multiple OAM functions, the detection block may also carry a type identifier for distinguishing different functions. As shown in FIG. 9c, the TYPE identifies the OAM type, for example, 0x01 indicates that the detection block is a connection detection type, that is, different types. The type of the detection block is different.

Step 3: XE2 performs rate adaptation.

XE2 receives the bit block data stream from XE1 through the network signal adaptation unit. If the receiving clock frequency is slower than the system clock of XE2, the network signal adaptation unit of XE2 needs to insert one or more free blocks in the bit block data stream; if the receiving clock frequency is faster than the system clock of XE2, the network signal of XE2 The adaptation unit needs to delete one or more free blocks in the bit block data stream to accommodate transmission speed problems due to unsynchronized clock frequencies. After the network signal adaptation unit of XE2 performs rate adaptation, the bit block data stream is transmitted to the downstream network side through the switching unit. Optionally, if the receiving clock frequency is adapted to the system clock of the XE2, the XE2 may not need to perform rate adaptation.

FIG. 12 is a schematic diagram of rate adaptation according to an embodiment of the present invention. As shown in FIG. 12, the direction of the arrow in the figure is the transmission direction of the bit stream data stream, and the bit block data stream includes a start block "S", an end block "T", a data block "D", and a free block "I". For example, a free block can be inserted or deleted between a start block and an end block.

Step 4: XE3 receives the detection block.

This step can be implemented by a monitoring unit in XE3, for example, by detecting a block receiving module. After the network device XE3 located on the edge side receives the bit block data stream from the XE2, the bit block data stream passes through the network side adaptation unit and arrives at the monitoring unit. Optionally, if the monitoring unit is after the switching unit, the bit block data stream passes through the switching unit and reaches the monitoring unit. The monitoring unit runs the detection block discovery process: the detection block is detected according to the characteristics of the detection block, and the stream identifier 0x023 and the transmission reference period 0x405 are extracted. First, the flow identifier matching is performed. When the flow identifier is consistent with the locally configured flow identifier (0x023), the transmission reference period (0x405) is extracted, and the timeout period of the counter is set as the transmission reference period. For example, the timeout period is The time when 1029 bit blocks were received. Optionally, a counter may also be set, and the timeout period is greater than the sending reference period. For example, the timeout period is the time when 3*1029 bit blocks are received. When the flow identifier is inconsistent with the locally configured flow identifier that is expected to be received, the connection error alarm is set and the remote defect indication (RDI) is immediately sent back. When N (for example, 5) correctly detected detection blocks of the flow identifier are continuously received, the connection misconnection alarm disappears and the return of the RDI is stopped.

FIG. 13 is a flowchart of a method for receiving a detection block according to an embodiment of the present invention. As shown in FIG. 13a, the method of receiving a detection block may include the steps of: detecting a bit block data stream, and determining whether a detection block is received according to a characteristic of the detection block. After determining that the detection block is received, a. If the flow identifier carried in the detection block is inconsistent with the expected flow identifier, the local connection misconnection alarm flag is updated. And, a fault alarm indication is generated, for example, an RDI is generated. b. If the flow identifier carried in the detection block is consistent with the expected flow identifier, the transmission reference period is extracted. Set counter 1, the timeout period is 1 times to send the reference period T, and start counting; set counter 2, the timeout period is 3 times the transmission reference period T, and start counting. When the counter 1 counts up to 1 times the transmission reference period, it starts detecting the block type of the bit block data stream. When the counter 2 counts up to 3 times the transmission reference period, no valid bit block is detected (for example, any combination of the start block "S", the end block "T", and the data block "D"), then the connection connectivity is lost ( Loss of connectivity, LOC) alarm. And, a fault alarm indication is generated, for example, an RDI is generated. FIG. 13b is a flowchart of another method for receiving a detection block according to an embodiment of the present invention. As shown in FIG. 13b, the difference from FIG. 13a is that only one counter can be set, and the timeout period can be 1 times the transmission reference period or any other length of time. The block type of the bit block data stream is detected when the counter starts counting. When the counter counts to the preset timeout period, if no valid bit block is detected, the connection connectivity loss alarm is set. Set two counters with different timeout periods. The detection block is not received from time 0 to long counter (counter 2), and no valid block is detected from the short counter (counter 1) timeout to the long counter timeout period. It is accurately determined that the connection connectivity is lost. In this example, by flexibly setting two counters of counter 1 and counter 2, combined with whether or not a valid bit block is received, the connection failure decision is accurate and reliable. It can also be flexibly simplified, and only the counter 2 is set, further reducing the implementation difficulty.

Optionally, the sending reference period can be directly configured in the network device, so that it does not need to be carried in the detecting block. For example, the XE1 configuration sends a reference period of 0x400, and the XE3 configuration receives a reference period of 0x400. In step 4, the timeout period of the counters 1, 2 can be set according to the configured reception reference period 0x400. Optionally, the counting period of the counter 1 may be N times the transmission reference period T. For example, N is set to 1, and may be 1.5 or other user-defined values. The counter 2 may be M times the counting period of the counter 1, for example, M is set to 3, and may be a user-defined value. Optionally, only one counter, such as the counter 2, may be set, and after the counter 2 times out, it is determined whether a valid bit block is received, thereby performing a connection failure decision. Optionally, after the counter 2 times out, it may not determine whether a valid bit block is received, but directly connects the connectivity loss alarm.

Optionally, when the length of the flow identifier is long and multiple test block bearers are to be sent, each detection block only carries a part of the flow identifier. As shown in FIG. 9d, the receiver XE3 needs to receive multiple times. After detecting the block, a complete stream identifier can be recovered, and then it is determined whether a connection error has occurred. When the detection block is received but the complete stream identifier has not been recovered, the connection connection is not detected by the default connection, and the connectivity of the connection is directly detected, as shown in Figure 13c. As shown in Fig. 13d, the difference from Fig. 13c is that only one counter can be set, and the timeout period can be 1 times the transmission reference period or any other length of time.

In the above process of receiving the detection block, it is necessary to identify the detection block according to the characteristics of the detection block. FIG. 14 is a schematic diagram of an encoding format of a detection block according to an embodiment of the present invention. As shown in FIG. 14a, the field A+B+O can be matched, the field A+B+O+C can be matched, or other field combinations can be matched to identify the detection block. The block type of the above-mentioned detected bit block data stream may be a detection sync header and a type field, and the like. Optionally, if the type identifier is included in the detection block, the type identifier field may also be matched, and the type of the function indicated by the detection block is identified by the type identifier field. When a new control code block is defined, for example, a code block of type 0x00 reserved by a 66-bit block and 8 bits of data of the other 56 bits, the matching mode is A+B, as shown in FIG. 14b.

The method for receiving a detection block in the embodiment of the present invention is also applicable to a bit block that receives other OAM functions, such as bit interleaving parity (BIP), remote error indication (REI), and client for error detection. Signal indication (CS), synchronization (SYNC), service layer alarm indication (AIS), protection switching protocol (APS), delay measurement (DM), etc.

The processing steps after a network failure will be described below. FIG. 15 is a schematic diagram of a network architecture according to an embodiment of the present invention. As shown in Figure 15, if the switching unit of XE2 fails. XE1 generates and sends a detection block. The XE3 enters the detection block reception, and the reception method of FIG. 13a is taken as an example for description. When the counter 1 times out, it begins to detect the block type of the bit block data stream until the counter 2 times out. If counter 1 times out until the desired detection block is received during counter 2 timeout, both counters are reset. If the counter 1 times out until the desired detection block has not been received during the counter 2 timeout period, the counter 1 timeout moment begins to detect the block type of the bit block data stream. If a valid bit block is detected (eg, any combination of start block "S", end block "T", data block "D"), then both counters are reset, and counters 1, 2 are reset. If a valid bit block is not detected, the LOC alarm is set and a backhaul RDI is generated. When N (such as 5) expected correct detection blocks are continuously received, the LOC alarm is cleared and the return of the RDI is stopped. The XE3 sets the LOC alarm and notifies the sender XE1 of the fault condition by sending back a fault alarm indication (for example, a fault alarm indication block). The fault alert indication block may be an RDI bit block, for example, may include a flow identification, a remote defect indication (RDI), and the like. Optionally, the RDI bit block may further include a type identifier, where the RDI bit block has a fault alarm indication function.

Similarly, the above embodiment may not detect a valid block, and the specific processing steps are simplified as follows: as shown in FIG. 15, if the switching unit of XE2 fails. XE1 generates and sends a detection block. The XE3 enters the detection block reception, and the reception method of FIG. 13d is taken as an example for description. When the counter 2 times out, the LOC alarm is set and the return RDI is generated. When N (such as 5) expected correct detection blocks are continuously received, the LOC alarm is cleared and the return of the RDI is stopped. The XE3 sets the LOC alarm and notifies the sender XE1 of the fault condition by sending back a fault alarm indication (for example, a fault alarm indication block). The fault alert indication block may be an RDI bit block, for example, may include a flow identifier, a remote defect indication (RDI), and the like. Optionally, the RDI bit block may further include a type identifier, where the RDI bit block has a fault alarm indication function.

For a two-way connection, that is, the direction of XE1 to XE3 and the direction of XE3 to XE1, XE1 can also receive the detection block generated by XE3. For example, the monitoring unit of XE1 receives the detection block in a manner similar to step 4, and performs connection failure detection.

In the embodiment of the present invention, the detected fault type may include any one or more of connection disconnection, connection connectivity loss, and remote defect. The network device can pass the fault condition to the local automatic protection switching (APS) function unit, implement the corresponding self-healing strategy, or pass to a software-defined networking (SDN) controller to implement the corresponding connection recovery strategy. Or pass to the network management to perform the corresponding alarm management and early warning functions.

FIG. 16 is a flowchart of a method for sending a fault indication block according to an embodiment of the present invention. As shown in FIG. 16, the method for transmitting the fault indication block is similar to the method for transmitting the detection block, and may include the following steps: when the receiving end detects the fault (for example, after the preset reference period is exceeded, the detection block is not received, It can be determined that the connection is interrupted at this time. When the fault indication block needs to be sent, the bit block data stream is started to be detected. When the free block in the bit block data stream is found, the free block is replaced with the fault indication block; the bit block data stream is transmitted. When the flow identifier needs to be carried, a part of the flow identifier or the flow identifier is sent in the fault indication block.

FIG. 17 is a flowchart of a method for receiving a fault indication block according to an embodiment of the present invention. As shown in FIG. 17a, the method for receiving a fault indication block is similar to the method for receiving a detection block, and may include the steps of: detecting a received bit block data stream, and discovering a fault indication block, when the fault indication block carries a stream identifier and an expected When the flow identifiers are inconsistent, the fault indication block is discarded. When the flow identifier carried by the fault indication block is consistent with the desired flow identifier, the local remote defect indication (RDI) flag is updated according to the remote defect indication field in the fault indication block. When the fault indication block does not carry the flow identifier, as shown in FIG. 17b, the method for receiving the fault indication block is similar to the method for receiving the detection block, and may include the following steps: detecting the received bit block data stream, and finding the fault indication block, according to The remote defect indication field in the fault indication block updates the local remote defect indication (RDI) flag. When the fault indication block carries a part of the flow identifier, as shown in FIG. 17c, the method for receiving the fault indication block is similar to the method for receiving the detection block, and may include the following steps: detecting the received bit block data stream, and finding the fault indication block, When the flow identifier carried by the fault indication block is only part of the flow identifier, it waits to receive the next fault indication block, and only recovers the complete flow identifier from each part of the collected flow identifier. When the flow identifier is inconsistent with the expected flow identifier, the fault indication block is discarded, and the detection starts again. When the flow identifier carried by the fault indication block is consistent with the desired flow identifier, the local remote defect indication (RDI) flag is updated according to the remote defect indication field in the fault indication block.

Optionally, the steps of generating, transmitting, receiving, and processing the detection block in the embodiment of the present invention are also applicable to other OAM functions (referred to as OAM function blocks). Table 1 shows an encoding format of a 66-bit block. When the OAM function block is a 66-bit block, it may have an encoding format as in Table 1. The coding format of the D1 to D3 fields of the OAM function block may include: Type: 6 bits, which identifies different OAM functions or combinations of several OAM functions; Value: 14 bits, message content of one or several types of OAM; CRC: 4bit, CRC-4 or CRC-8 check is used for the entire 60bit (except CRC 4bit).

Table 1

FIG. 18a is a schematic diagram of sending multiple OAM function blocks according to an embodiment of the present invention. As shown in Figure 18a, different OAM functions can be represented by the Data field, such as error detection (BIP), remote error indication (REI), client signal indication (CS), synchronization (SYNC), service layer alarm. OAM functions such as indication (AIS), protection switching protocol (APS), and delay measurement (DM). When multiple OAM function blocks exist at the same time, the OAM function block may carry a type identifier (such as the Type field of D1 in Table 1 or the type field of the table in the lower right corner of FIG. 18a) for distinguishing different OAM function blocks. Similarly, the detection block in the above embodiment may also carry the type identifier. The table in the lower right corner of the figure shows the encoding format of the Data fields of various OAM function blocks. In the bit block data stream in the figure, overhead (OH) 1 is an OAM that is immediately returned on demand, such as RDI, REI, DM, APS; periodic OH2, periodic OH3 are respectively transmitted in respective cycles, for example OAM functions such as CCB, BIP, and CS.

When the value of Table 1 can only carry a part of the OAM function, the Value can be flexibly defined and carried by multiple OAM blocks, that is, each of the OAM function blocks only carries a part of the function information. As shown in the table of Figure 18b, the continuity check/Verification (CC/CV for short), when the stream identifier requires 64 bytes, the 14-bit Value of each detection block is divided into two parts, Value[0,5] Identify the sequence number, Value[6,13] identifies one of the 64 bytes of the stream identifier, as shown in Figure 7g; When the unidirectional delay is measured, that is, the DM in the table, D1[6:7] is 0x00, 0x11, each time the 12 bits of the timestamp are transmitted, a total of 8 frames are transmitted.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Claims (37)

A method for detecting block transmission, characterized in that the method comprises: The network device acquires the original bit block data stream; Generating at least one detection block, inserting the at least one detection block into a position of at least one free block in the original bit block data stream; Transmitting a block of bit data containing the at least one detected block. The method of claim 1, wherein the inserting the at least one detection block into the location of the at least one free block in the original bit block data stream comprises: The X detection blocks are inserted into the positions of the X free blocks in the original bit block data stream, and X is a positive integer greater than or equal to 1. The method according to claim 1 or 2, wherein the at least one detection block carries a flow identifier, the flow identifier being used to indicate a connection identifier of the original bit block data stream. The method according to any one of claims 1-3, wherein the at least one detection block carries a preset transmission reference period, and the preset transmission reference period is used to indicate transmission of the at least one detection block. cycle. The method according to claim 4, wherein the transmission period of the at least one detection block is greater than or equal to a preset transmission reference period carried by the at least one detection block. The method according to claim 5, wherein when the transmission period of the at least one detection block is greater than a preset transmission reference period carried by the at least one detection block, the method further includes: Updating a preset transmission reference period of the at least one detection block to a transmission period of the at least one detection block. Method according to claim 1 or 2, characterized in that the type fields of the different types of detection blocks are different. The method of claim 1 or 2, wherein one of the operational management and maintenance OAM information is carried by at least two detection blocks. The method of any of claims 1-8, wherein the at least one detection block is an M/N bit block. A method for detecting block reception, characterized in that the method comprises: The network device receives a bit block data stream including at least one detection block; Identifying the at least one detection block, replacing the at least one detection block with at least one free block; Sending a bit block data stream after replacing the at least one free block. The method of claim 10, wherein the replacing the at least one detection block with the at least one free block comprises: Replace X detection blocks with X free blocks, and X is a positive integer greater than or equal to 1. The method according to claim 10 or 11, wherein the detection block carries a flow identifier, the flow identifier is used to indicate a connection identifier of the bit block data stream, and the method further includes: The network device performs fault detection according to the flow identifier. The method according to any one of claims 10 to 12, wherein the detection block carries a preset transmission reference period, the method further comprising: The network device identifies the at least one detection block according to the transmission reference period. Method according to claim 10 or 11, characterized in that the type fields of the different types of detection blocks are different. The method of claim 10 or 11, wherein one of the operational management and maintenance OAM information is carried by at least two detection blocks. A method according to any of claims 10-15, wherein said at least one detection block is an M/N bit block. A network device, where the network device includes: An obtaining module, configured to obtain a raw bit block data stream; a processing module, configured to generate at least one detection block, and insert the at least one detection block into a location of at least one free block in the original bit block data stream; And a sending module, configured to send a bit block data stream including the at least one detection block. The network device according to claim 17, wherein the processing module is configured to: The X detection blocks are inserted into the positions of the X free blocks in the original bit block data stream, N being a positive integer greater than or equal to one. The network device according to claim 17 or 18, wherein the at least one detection block carries a flow identifier, and the flow identifier is used to indicate a connection identifier of the bit block data stream. The network device according to any one of claims 17 to 19, wherein the at least one detection block carries a preset transmission reference period, and the preset transmission reference period is used to indicate the at least one detection block. Send cycle. The network device according to claim 20, wherein the transmission period of the at least one detection block is greater than or equal to a preset transmission reference period carried by the at least one detection block. The network device according to claim 21, wherein when the transmission period of the at least one detection block is greater than a preset transmission reference period carried by the at least one detection block, the processing module is further configured to: Updating a preset transmission reference period of the at least one detection block to a transmission period of the at least one detection block. Method according to claim 17 or 18, characterized in that the type fields of the different types of detection blocks are different. The method of claim 17 or 18, wherein one of the operational management and maintenance OAM information is carried by at least two detection blocks. A network device according to any of claims 17-24, wherein said at least one detection block is an M/N bit block. A network device, where the network device includes: a receiving module, configured to receive a bit block data stream including at least one detection block; a processing module, configured to identify the at least one detection block, and replace the at least one detection block with at least one free block; Sending a bit block data stream after replacing the at least one free block. The network device according to claim 26, wherein the processing module is configured to: Replace X detection blocks with X free blocks, and X is a positive integer greater than or equal to 1. The network device according to claim 26 or 27, wherein the detection block carries a flow identifier, the flow identifier is used to indicate a connection identifier of the bit block data stream, and the processing module is further configured to: The fault detection is performed according to the flow identifier. The network device according to any one of claims 26-28, wherein the detection block carries a preset transmission reference period, and the processing module is further configured to: Identifying the at least one detection block according to the transmission reference period. Method according to claim 26 or 27, characterized in that the type fields of the different types of detection blocks are different. The method of claim 26 or 27, wherein one of the operational management and maintenance OAM information is carried by at least two detection blocks. A network device according to any of claims 26-31, wherein said at least one detection block is an M/N bit block. A network system, characterized in that the system comprises a transmitting device according to any one of claims 17-25, and a receiving device according to any of claims 26-32. A computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1-9. A computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any of claims 10-14. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1-7. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 8-12.

Images