WO2019015462A1 - Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système - Google Patents

Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système Download PDF

Info

Publication number
WO2019015462A1
WO2019015462A1 PCT/CN2018/093563 CN2018093563W WO2019015462A1 WO 2019015462 A1 WO2019015462 A1 WO 2019015462A1 CN 2018093563 W CN2018093563 W CN 2018093563W WO 2019015462 A1 WO2019015462 A1 WO 2019015462A1
Authority
WO
WIPO (PCT)
Prior art keywords
block
detection
detection block
data stream
network device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/093563
Other languages
English (en)
Chinese (zh)
Inventor
张小俊
牛乐宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201710687162.0A external-priority patent/CN109274600B/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP18835529.1A priority Critical patent/EP3648402B1/fr
Priority to KR1020207004387A priority patent/KR102324923B1/ko
Priority to JP2020502384A priority patent/JP6985492B2/ja
Priority to EP25199529.6A priority patent/EP4679796A3/fr
Publication of WO2019015462A1 publication Critical patent/WO2019015462A1/fr
Priority to US16/745,937 priority patent/US11082317B2/en
Anticipated expiration legal-status Critical
Priority to US17/391,731 priority patent/US11539607B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0847—Transmission error
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays

Definitions

  • 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.
  • FlexE 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 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
  • 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.
  • the dotted path is an end-to-end service forwarding path.
  • 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.
  • the upstream client signal adaptation unit inserts a detection block
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • TTI trail trace identifier
  • 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.
  • 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.
  • TTI mismatch TIM
  • the receiver can only determine whether a misconnection occurs after receiving the multiple detection blocks and combining them into a complete flow identifier.
  • 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.
  • BIP bit interleaved parity
  • REI far end error indication
  • CS client signal indication
  • SYNC synchronization
  • AIS service layer alarm indication
  • APS Protection Switching Protocol
  • DM Time Delay Measurement
  • 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.
  • 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.
  • the transmission period of the detection block may float within a certain range, which is a non-fixed period.
  • 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.
  • the preset transmission reference period may be dynamically changed according to the actual transmission period of the detection block.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the receiver can only determine whether a misconnection occurs after receiving the multiple detection blocks and combining them into a complete flow identifier.
  • 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.
  • BIP bit interleaved parity
  • REI far end error indication
  • CS client signal indication
  • SYNC synchronization
  • AIS service layer alarm indication
  • APS Protection Switching Protocol
  • DM Time Delay Measurement
  • the detecting block carries a preset sending reference period
  • 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.
  • the receiving network device quickly locates the detection block according to the preset period.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of a networking architecture of a prior art using an L1.5 layer switching technology
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • 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.
  • 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.
  • the monitoring unit 302 can be disposed between the client signal adaptation unit 301 and the switching unit 303.
  • 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).
  • UNI user-to-network interface
  • NNI network-to-network interface
  • FIGS. 4a-4d are schematic structural diagrams of four network devices P according to an embodiment of the present invention.
  • the network device P may include network signal adaptation units 401 and 405, and an exchange unit 403.
  • any one or both of the monitoring units 402 and 404 may also be included.
  • 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.
  • IP RAN IP radio access network
  • PDN packet transport network
  • . 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • OAM operations, administration and maintenance
  • BIP bit interleaved parity
  • REI Remote error indication
  • CS customer signal indication
  • SYNC synchronization
  • AIS service level alarm indication signal
  • APS protection switching protocol
  • delay measurement delay measurement, DM
  • the detection block can also carry a type identifier for distinguishing different functions.
  • 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.
  • 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.
  • 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.
  • XE1 receives the data stream from the client device through the UNI.
  • XE1 may encode the received data stream or perform encoding format conversion.
  • 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.
  • 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.
  • IDLE idle block
  • 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.
  • 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.
  • 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.
  • FIG. 9a, 9b, 9c, and 9d are schematic diagrams of a transmission detection block according to an embodiment of the present invention.
  • 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.
  • 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.
  • the receiving network device detects and receives the detection block according to a preset period.
  • 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.
  • 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.
  • FIG. 11 is a schematic diagram of a format of a free block according to an embodiment of the present invention.
  • 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.
  • BIP bit interleaving parity
  • REI bit interleaving parity
  • CS Customer Signal Indication
  • SYNC Synchronization
  • AIS Service Layer Alarm Indication
  • APS Protection Switching Protocol
  • DM Delay Measurement
  • 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.
  • 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.
  • 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.
  • the transmission reference period (0x405) is extracted, and the timeout period of the counter is set as the transmission reference period.
  • the timeout period is The time when 1029 bit blocks were received.
  • a counter may also be set, and the timeout period is greater than the sending reference period.
  • the timeout period is the time when 3*1029 bit blocks are received.
  • FIG. 13 is a flowchart of a method for receiving a detection block according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the XE1 configuration sends a reference period of 0x400
  • the XE3 configuration receives a reference period of 0x400.
  • the timeout period of the counters 1, 2 can be set according to the configured reception reference period 0x400.
  • the counting period of the counter 1 may be N times the transmission reference period T.
  • 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.
  • 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.
  • the counter 2 times out it may not determine whether a valid bit block is received, but directly connects the connectivity loss alarm.
  • each detection block only carries a part of the flow identifier.
  • 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.
  • the connection connection is not detected by the default connection, and the connectivity of the connection is directly detected, as shown in Figure 13c.
  • 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.
  • FIG. 14 is a schematic diagram of an encoding format of a detection block according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • BIP bit interleaving parity
  • REI remote error indication
  • CS Signal indication
  • SYNC synchronization
  • AIS service layer alarm indication
  • APS protection switching protocol
  • DM delay measurement
  • FIG. 15 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • the RDI bit block may further include a type identifier, where the RDI bit block has a fault alarm indication function.
  • 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.
  • the LOC alarm is set and the return RDI is generated.
  • 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.
  • the RDI bit block may further include a type identifier, where the RDI bit block has a fault alarm indication function.
  • XE1 can also receive the detection block generated by XE3.
  • the monitoring unit of XE1 receives the detection block in a manner similar to step 4, and performs connection failure detection.
  • 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.
  • APS local automatic protection switching
  • SDN software-defined networking
  • FIG. 16 is a flowchart of a method for sending a fault indication block according to an embodiment of the present invention.
  • 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.
  • the fault indication block needs to be sent, the bit block data stream is started to be detected.
  • 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.
  • 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.
  • 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.
  • the local remote defect indication (RDI) flag is updated according to the remote defect indication field in the fault indication block.
  • the fault indication block does not carry the flow identifier, as shown in FIG.
  • 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.
  • 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.
  • the fault indication block is discarded, and the detection starts again.
  • the local remote defect indication (RDI) flag is updated according to the remote defect indication field in the fault indication block.
  • OAM function blocks show an encoding format of a 66-bit block.
  • OAM function 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).
  • FIG. 18a is a schematic diagram of sending multiple OAM function blocks according to an embodiment of the present invention.
  • 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).
  • 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.
  • the detection block in the above embodiment may also carry the type identifier.
  • 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.
  • 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.
  • the continuity check/Verification (CC/CV for short)
  • 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;
  • D1[6:7] is 0x00, 0x11, each time the 12 bits of the timestamp are transmitted, a total of 8 frames are transmitted.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • the computer program 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)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé d'envoi d'un bloc de détection, un procédé de réception d'un bloc de détection, un dispositif de réseau, et un système. Le procédé d'envoi d'un bloc de détection comprend les étapes suivantes : un dispositif de réseau acquiert un flux de données de bloc de bits d'origine; génère au moins un bloc de détection et insère le ou les blocs de détection à la position d'au moins un bloc inactif dans le flux de données de bloc de bits d'origine; et envoie un flux de données de bloc de bits contenant le ou les blocs de détection. Selon la présente invention, le bloc de détection envoyé est inséré à la position d'une ressource de bande passante du bloc inactif dans le flux de données de bloc de bits, ce qui résout le problème de perte de bloc de bits dans un service.
PCT/CN2018/093563 2017-07-18 2018-06-29 Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système Ceased WO2019015462A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP18835529.1A EP3648402B1 (fr) 2017-07-18 2018-06-29 Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système
KR1020207004387A KR102324923B1 (ko) 2017-07-18 2018-06-29 검출 블록 발신 및 수신 방법과, 네트워크 디바이스와 시스템
JP2020502384A JP6985492B2 (ja) 2017-07-18 2018-06-29 検出ブロック送信及び受信方法並びにネットワークデバイス及びシステム
EP25199529.6A EP4679796A3 (fr) 2017-07-18 2018-06-29 Procédé d'envoi et de réception de bloc de détection, et dispositif et système de réseau
US16/745,937 US11082317B2 (en) 2017-07-18 2020-01-17 Detection block sending and receiving method, and network device and system
US17/391,731 US11539607B2 (en) 2017-07-18 2021-08-02 Detection block sending and receiving method, and network device and system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710586112 2017-07-18
CN201710586112.3 2017-07-18
CN201710687162.0 2017-08-11
CN201710687162.0A CN109274600B (zh) 2017-07-18 2017-08-11 一种检测块发送和接收的方法、网络设备和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/745,937 Continuation US11082317B2 (en) 2017-07-18 2020-01-17 Detection block sending and receiving method, and network device and system

Publications (1)

Publication Number Publication Date
WO2019015462A1 true WO2019015462A1 (fr) 2019-01-24

Family

ID=65015365

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093563 Ceased WO2019015462A1 (fr) 2017-07-18 2018-06-29 Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système

Country Status (1)

Country Link
WO (1) WO2019015462A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112350897A (zh) * 2020-11-06 2021-02-09 中国人民解放军国防科技大学 基于动态连接端到端可靠传输协议的网络测试装置
CN113890787A (zh) * 2020-07-03 2022-01-04 中兴通讯股份有限公司 灵活以太网环网保护方法、装置、计算机设备和介质
WO2023035776A1 (fr) * 2021-09-13 2023-03-16 华为技术有限公司 Procédé de communication, appareil correspondant et support de stockage
US12341653B2 (en) 2020-04-03 2025-06-24 Huawei Technologies Co., Ltd Service flow adjustment method and communication apparatus
US12567923B2 (en) * 2020-07-13 2026-03-03 Huawei Technologies Co., Ltd. Rate adaptation method and apparatus

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101552687A (zh) * 2008-04-01 2009-10-07 大唐移动通信设备有限公司 提高用户设备信道估计准确性的方法、系统和装置
US20090323722A1 (en) * 2008-06-25 2009-12-31 Debendra Das Sharma Link and lane level packetization scheme of encoding in serial links
CN102057729A (zh) * 2008-06-09 2011-05-11 爱立信电话股份有限公司 用于if/irat测量分配的方法和系统和设备
CN106484323A (zh) * 2016-09-13 2017-03-08 郑州云海信息技术有限公司 一种固态存储的损耗均衡方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101552687A (zh) * 2008-04-01 2009-10-07 大唐移动通信设备有限公司 提高用户设备信道估计准确性的方法、系统和装置
CN102057729A (zh) * 2008-06-09 2011-05-11 爱立信电话股份有限公司 用于if/irat测量分配的方法和系统和设备
US20090323722A1 (en) * 2008-06-25 2009-12-31 Debendra Das Sharma Link and lane level packetization scheme of encoding in serial links
CN106484323A (zh) * 2016-09-13 2017-03-08 郑州云海信息技术有限公司 一种固态存储的损耗均衡方法及系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12341653B2 (en) 2020-04-03 2025-06-24 Huawei Technologies Co., Ltd Service flow adjustment method and communication apparatus
CN113890787A (zh) * 2020-07-03 2022-01-04 中兴通讯股份有限公司 灵活以太网环网保护方法、装置、计算机设备和介质
US12567923B2 (en) * 2020-07-13 2026-03-03 Huawei Technologies Co., Ltd. Rate adaptation method and apparatus
CN112350897A (zh) * 2020-11-06 2021-02-09 中国人民解放军国防科技大学 基于动态连接端到端可靠传输协议的网络测试装置
CN112350897B (zh) * 2020-11-06 2022-08-12 中国人民解放军国防科技大学 基于动态连接端到端可靠传输协议的网络测试装置
WO2023035776A1 (fr) * 2021-09-13 2023-03-16 华为技术有限公司 Procédé de communication, appareil correspondant et support de stockage

Similar Documents

Publication Publication Date Title
CN114726479B (zh) 一种检测块发送和接收的方法、网络设备和系统
CN102224702B (zh) 借助信号编码的时间传送技术
WO2019015462A1 (fr) Procédé d'envoi de bloc de détection, procédé de réception de bloc de détection, dispositif de réseau, et système
US7949782B2 (en) Extended link monitoring channel for 10 Gb/s Ethernet
WO2019056899A1 (fr) Procédé et dispositif de transmission de message oam, et support de stockage
CN106612220A (zh) 灵活以太网的通道管理方法和装置
WO2018059604A1 (fr) Procédé de transmission d'informations, dispositif et support de stockage informatique
CN113765619B (zh) 64b/66b码流发送方法、64b/66b码流接收方法及设备
CN102035718A (zh) 一种分组传送网保护倒换的方法、装置和系统
WO2019029286A1 (fr) Procédé et dispositif de communication, et support de stockage
WO2021254508A1 (fr) Procédé et appareil destinés à déterminer une perte de bloc de code
WO2020133897A1 (fr) Procédé et dispositif de traitement d'informations d'opération, d'administration et de gestion (oam)
WO2023197770A1 (fr) Procédé et appareil de notification de défaut
WO2022001124A1 (fr) Procédé de transmission, procédé et appareil de détection, procédé d'acquisition, dispositif de réseau et système
CN117579220A (zh) 一种故障码块处理方法及装置
US20260121780A1 (en) Code block identification method and apparatus
CN101035028A (zh) 接错检测的方法和网络设备
CN112511328A (zh) 发送和处理信息的方法、以太网设备、计算机可读介质
WO2021238791A1 (fr) Procédé et dispositif de traitement de bloc de code
CN112311497B (zh) 一种通信方法和通信设备
CN116962145A (zh) 一种故障通告方法及装置
CN121664612A (zh) 故障信息传递方法、存储介质、电子装置及计算机程序产品
CN121603430A (zh) 一种数据处理方法及相关设备
CN119211060A (zh) 业务码块流的传输方法、服务质量监控方法及系统
JP3295834B2 (ja) 時分割多重データ受信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18835529

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020502384

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018835529

Country of ref document: EP

Effective date: 20200130

ENP Entry into the national phase

Ref document number: 20207004387

Country of ref document: KR

Kind code of ref document: A

WWG Wipo information: grant in national office

Ref document number: 2018835529

Country of ref document: EP