WO2021017890A1 - 一种通信方法和通信设备 - Google Patents

一种通信方法和通信设备 Download PDF

Info

Publication number
WO2021017890A1
WO2021017890A1 PCT/CN2020/102591 CN2020102591W WO2021017890A1 WO 2021017890 A1 WO2021017890 A1 WO 2021017890A1 CN 2020102591 W CN2020102591 W CN 2020102591W WO 2021017890 A1 WO2021017890 A1 WO 2021017890A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
unit
restoration
bit
streams
Prior art date
Application number
PCT/CN2020/102591
Other languages
English (en)
French (fr)
Inventor
孙德胜
牛乐宏
何路友
Original Assignee
华为技术有限公司
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021017890A1 publication Critical patent/WO2021017890A1/zh

Links

Images

Classifications

    • 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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • 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/0071—Use of interleaving
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic

Definitions

  • This application relates to the field of communications, in particular to a communication method and communication equipment.
  • a protection path may be added between the first communication device and the second communication device.
  • the first communication device sends at least one service flow to the second communication device.
  • the second communication device determines that the service stream transmission fails and notifies the first communication device.
  • the first communication device sends a faulty part of the service flow in at least one service flow to the second communication device through the guaranteed path. It takes a certain time for the second communication device to perform fault detection and notification, which may cause the loss of service data.
  • the service flow may be copied, and the first communication device may send multiple copies of the same service flow to the second communication device through different paths.
  • the duplication of service flow occupies more transmission resources, and the network utilization rate is low.
  • the present application provides a communication method and communication device, which can protect at least one service flow transmitted between communication devices, avoid service data loss, and improve user experience.
  • a communication method including: a first communication device generates M recovery streams and N service streams, where M and N are positive integers; and the first communication device sends the M recovery streams to the second communication device.
  • the restoration flow and the N service flows, the jth service flow in the N service flows includes at least one service unit; the M restoration flows include at least one restoration unit, and the i-th service flow in the at least one restoration unit
  • the recovery unit is obtained according to the i-th service unit in each of the N service streams, and i and j are positive integers.
  • At least one of the transmitted N service streams is protected through the M recovery streams determined by the N service streams. It is possible to recover the service flow when at least one service flow is incorrectly received, avoiding the loss of service data and improving user experience.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th in the j-th service flow. The correctness of the business unit.
  • the service unit with the error code can be determined, and the service flow to be recovered can be determined.
  • the second communication device can send directly without waiting for the reception and verification of service units in other service streams, thereby improving transmission efficiency.
  • each of the M recovery streams includes an alignment identifier corresponding to the recovery stream
  • each of the N service streams includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the second communication device can determine the correspondence between the recovery unit and the business unit, and ensure the accuracy of the recovered business unit.
  • the i-th service unit includes at least one alignment identifier, wherein each alignment identifier is located at the end of a service package or a service frame, and is used to indicate the service package or The end of the business frame.
  • the second communication device can determine the end position of the service packet or the service frame when restoring the service unit, and accurately restore the service packet or the service frame.
  • the i-th restoration unit in the at least one restoration unit is to verify or correct the i-th service unit in each of the N service flows. Wrong encoding.
  • the check method is a bit interleaved parity check BIP.
  • the i-th restoration unit of the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each of the N service streams includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is the result of performing BIP on the kth service bit of at least one service bit in the i-th service unit of each of the N service streams
  • k is Positive integer
  • a check bit in the BIP check result can be used to recover a bit in a business unit.
  • the amount of data that needs to be transmitted to restore the stream is small, and the network utilization rate is high.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the business unit can be restored without relying on the detection identification of each business unit.
  • the error correction coding method is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the service unit can be restored without relying on the detection identifier of each service unit.
  • the redundant bits formed by encoding can recover up to half of the number of redundant bits in the business unit, and the amount of data to be transmitted for the recovery stream is small, and the network utilization rate is high.
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • a communication method including: a second communication device receives M recovery streams and N service streams sent by a first communication device, and the j-th service stream among the N service streams includes at least one service unit
  • the M recovery streams include at least one recovery unit, and the i-th recovery unit in the at least one recovery unit is obtained according to the i-th service unit in each of the N service streams, M, N, i, and j are positive integers; the second communication device determines the N service streams.
  • At least one of the transmitted N service streams is protected through the M recovery streams determined by the N service streams. It is possible to recover the service flow when at least one service flow is incorrectly received, avoiding the loss of service data and improving user experience.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th detection identifier in the j-th service flow.
  • the correctness of the business code block is used to detect the i-th detection identifier in the j-th service flow.
  • the service unit with the error code can be determined, and the service flow to be recovered can be determined.
  • the method further includes: the second communication device determines that the i-th service unit in the j-th service flow is correct according to the i-th detection identifier; The second communication device sends the i-th service unit.
  • the second communication device can directly send without waiting for the reception and verification of service units in other service streams, thereby improving transmission efficiency.
  • the determining of the N service flows by the second communication device includes: restoring the N service flows by the second communication device according to the i-th restoration unit The i-th business unit of each business flow in at least one business flow.
  • the restoration unit in the restoration flow the service unit corresponding to the restoration flow in the at least one service flow is restored, so as to realize the protection of the restoration flow for the at least one service flow.
  • each of the M recovery streams includes an alignment identifier corresponding to the recovery stream
  • each of the N service streams includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the second communication device can determine the correspondence between the recovery unit and the business unit, and ensure the accuracy of the recovered business unit.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service package or a service frame and is used to indicate the service package or The end of the business frame.
  • the second communication device can determine the end position of the service packet or the service frame when restoring the service unit, and accurately restore the service packet or the service frame.
  • the i-th recovery unit in the at least one recovery unit is to verify or correct the i-th service unit in each of the N service streams. Wrong encoding.
  • the check method is bit interleaving parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit in each of the N service flows includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is a bit interleaved parity check BIP on the kth service bit of at least one service bit in the i-th service unit of each of the N service streams
  • the result of k is a positive integer.
  • a check bit in the BIP check result can be used to recover a bit in a business unit.
  • the amount of data that needs to be transmitted to restore the stream is small, and the network utilization rate is high.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the business unit can be restored without relying on the detection identification of each business unit.
  • the error correction coding manner is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the service unit can be restored without relying on the detection identifier of each service unit.
  • the redundant bits formed by encoding can recover up to half of the number of redundant bits in the business unit, and the amount of data to be transmitted for the recovery stream is small, and the network utilization rate is high.
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • a communication device in the third aspect, includes a generating module and a sending module.
  • the generating module is used to generate M recovery streams and N service streams, where M and N are positive integers;
  • the sending module is used to send the M recovery streams and the N service streams to the second communication device, the N
  • the jth service stream in the service stream includes at least one service unit;
  • the M recovery streams include at least one recovery unit, and the i-th recovery unit in the at least one recovery unit is based on each of the N service streams Obtained from the i-th business unit in the business flow, i and j are positive integers.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th in the j-th service flow. The correctness of the business unit.
  • each of the M recovery streams includes an alignment identifier corresponding to the recovery stream
  • each of the N service streams includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the i-th service unit includes at least one alignment identifier, wherein each alignment identifier is located at the end of a service package or a service frame and is used to indicate the service package or The end of the business frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is to verify or correct the i-th service unit in each of the N service flows. Wrong encoding.
  • the verification method is a bit interleaved parity check BIP.
  • the i-th restoration unit of the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each of the N service streams includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is the result of performing BIP on the kth service bit of at least one service bit in the i-th service unit of each of the N service streams, and k is Positive integer.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the error correction coding manner is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • the communication device includes a transceiver module and a determination module.
  • the transceiver module is configured to receive M recovery streams and N service streams sent by the first communication device, where the j-th service stream among the N service streams includes at least one service unit; the M recovery streams include at least one recovery unit , The i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and M, N, i, and j are positive integers; the determining module is Determine the N service flows.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th detection identifier in the j-th service flow.
  • the correctness of the business code block is used to detect the i-th detection identifier in the j-th service flow.
  • the determining module is configured to determine that the i-th service unit in the j-th service flow is correct according to the i-th detection identifier; the transceiver module is also used to send the The i-th business unit.
  • the determining module includes a recovery sub-module, and the recovery sub-module is configured to recover each service flow in at least one of the N service flows according to the i-th restoration unit The i-th business unit.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service package or a service frame and is used to indicate the service package or The end of the business frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is to verify or correct the i-th service unit in each of the N service flows. Wrong encoding.
  • the check method is bit interleaved parity check BIP.
  • the i-th restoration unit of the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each of the N service flows includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is a bit interleaved parity check BIP on the kth service bit of at least one service bit in the i-th service unit of each service flow in the N service streams
  • the result of k is a positive integer.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the error correction coding manner is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the number of bits of the i-th recovery unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • a communication device in a fifth aspect, includes a processor and a communication interface.
  • the processor is used to generate M recovery streams and N service streams, where M and N are positive integers;
  • the communication interface is used to send the M recovery streams and the N service streams to the second communication device, and the N services
  • the j-th service stream in the stream includes at least one service unit;
  • the M recovery streams include at least one recovery unit, and the i-th recovery unit in the at least one recovery unit is based on each service in the N service streams Obtained from the i-th business unit in the stream, i and j are positive integers.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th in the j-th service flow. The correctness of the business unit.
  • each of the M recovery streams includes an alignment identifier corresponding to the recovery stream
  • each of the N service streams includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service package or a service frame, and is used to indicate the service package or The end of the business frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is to verify or correct the i-th service unit in each of the N service flows. Wrong encoding.
  • the verification method is a bit interleaved parity check BIP.
  • the i-th restoration unit of the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each of the N service streams includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is the result of performing BIP on the kth service bit of at least one service bit in the i-th service unit of each of the N service streams, and k is Positive integer.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the error correction coding manner is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the number of bits of the i-th recovery unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • a communication device including a processor and a communication interface.
  • the communication interface is configured to receive M recovery streams and N service streams sent by the first communication device, where the j-th service stream of the N service streams includes at least one service unit; the M recovery streams include at least one recovery unit , The i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and M, N, i, and j are positive integers; the processor is used for Determine the N service flows.
  • the jth service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the i-th detection identifier in the jth service flow.
  • the correctness of the business code block is used to detect the i-th detection identifier in the jth service flow.
  • the processor is configured to determine, according to the i-th detection identifier, that the i-th service unit in the j-th service flow is correct; the communication interface is also used to send the i business units.
  • the processor is configured to restore the i-th service unit of each service flow in at least one of the N service flows according to the i-th restoration unit.
  • each of the M recovery streams includes an alignment identifier corresponding to the recovery stream
  • each of the N service streams includes The alignment identifier corresponding to the service flow, where the alignment identifier is used to indicate the corresponding relationship between the i-th restoration unit and the i-th service unit in each of the N service flows.
  • the i-th service unit includes at least one alignment identifier, wherein each alignment identifier is located at the end of a service package or a service frame and is used to indicate the service package or The end of the business frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is to verify or correct the i-th service unit in each of the N service flows. Wrong encoding.
  • the check method is bit interleaved parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit in each of the N service flows includes at least one Service bits
  • the kth restoration bit in the at least one restoration bit is a bit interleaved parity check BIP on the kth service bit of at least one service bit in the i-th service unit of each service flow in the N service streams
  • the result of k is a positive integer.
  • the error correction encoding manner is forward error correction FEC encoding.
  • the error correction coding manner is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the N The i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes the i-th service stream for each of the N service streams. Redundant bits obtained by forward error correction FEC encoding of the k-th service bit group in at least one service bit group in the service unit, and the number of bits in each k-th service bit group is less than or equal to that of the redundant bits Half of the number of bits, and k is a positive integer.
  • the number of bits of the i-th recovery unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • an embodiment of the present application provides a communication system, including the first communication device and the second communication device described above.
  • a computer program storage medium has program instructions, and when the program instructions are executed, the above method is executed.
  • a chip in a ninth aspect, includes at least one processor, and when program instructions are executed in the at least one processor, the above method is executed.
  • Figure 1 is a schematic diagram of a communication method.
  • Figure 2 is a schematic diagram of another communication method.
  • Fig. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Fig. 4 is a schematic flow chart of an Ethernet data transmission method.
  • Fig. 5 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • Fig. 6 is a schematic diagram of the types of 64B/66B code blocks in the IEEE802.3 specification.
  • Fig. 7 is a schematic diagram of a control code block provided by an embodiment of the present application.
  • Fig. 8 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • Fig. 9 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of an RS codeword.
  • FIG. 13 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of still another communication device provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of yet another communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of still another communication device provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a communication method.
  • ITU-T International Telecommunication Union-Telecommunication Standardization Sector
  • a protection technology is standardized to protect N working services through one protection path.
  • the first communication device and the second communication device may send different service information through multiple working paths.
  • path 1, path 2, and path 3 are all working paths, which are used to transmit service data sent by device 1 to device 4, service data sent by device 2 to device 5, and service data sent by device 3 to device 6 respectively.
  • Both the first communication device and the second communication device are network devices.
  • Device 1-Device 6 can be user equipment or network equipment.
  • the data transmission path may be faulty.
  • path 4 can be added, and path 4 can be used as a protection path.
  • the service transmitted on the failed working path is switched to the protection path for transmission.
  • the sending end device sends the service of the faulty working path through the protection channel.
  • the receiving end device switches to receive services through the protection channel. There may be a failure of one path among the N working paths.
  • One protection path is used to protect the transmission of N working services.
  • the protection path does not transmit information, the resource consumption is small, and the network utilization rate is low. Through this method, it is necessary to monitor the alarm status of each path in real time, and find faults in time.
  • the switching of the service transmission path between the first communication device and the second communication device can be negotiated through the automatic protection switching (APS) protocol. It takes a certain time for the first communication device to determine that the working path is faulty. When the first communication device determines that the working path is faulty, part of the service data has been sent through the failed path, so there is a loss of service data.
  • APS automatic protection switching
  • Figure 2 is a schematic diagram of a communication method. Through this method, the loss of business data can be avoided.
  • Ethernet-related standards published by the Institute of Electrical and Electronics Engineers (IEEE) 802.3CB use packet replication to avoid frame loss caused by path failures.
  • the communication device 101 receives the service frame, copies the service frame, and adds the identification R-TAG to the service frame.
  • the service frame is the frame structure used to carry service information. Business information can also be called business data.
  • the same R-TAG is used to identify service frames that include the same service data.
  • the communication device 101 may send the copied service frame to the communication device 104 through different paths. For example, the service frame 1 is sent to the communication device 104 via the communication device 101 and the communication device 102; the service frame 2 is sent to the communication device 104 via the communication device 101 and the communication device 103. Service frame 1 and service frame 2 have the same tag (R-TAG).
  • the communication device 104 receives the same service frame 1 and service frame 2 of the R-TAG, and sends only one of them downstream. For each business frame, by copying and transmitting on multiple paths, the risk of path failure is resisted and the reliability of business transmission is improved.
  • the business data is copied, and the copied business data is transmitted through different paths, which occupies large protection resources and low network utilization.
  • the intermediate node on the service frame transmission path may also copy the data frame and send it through a different path.
  • the communication device 102 copies the service frame 1 again to generate the service frame 3, and the communication device 103 sends it, and the service frame 3 is forwarded by the communication device 103 and sent to the communication device 104.
  • Service frame 3 has the same tag R-TAG as service frame 1.
  • the replication and transmission of service frames by intermediate nodes further reduces network utilization.
  • Fig. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • step S301 the first communication device generates M recovery streams and N service streams, where M and N are positive integers.
  • the jth service flow among the N service flows includes at least one service unit; the M restoration flows include at least one restoration unit, and the i-th restoration unit in the at least one restoration unit is based on the N service flows Is obtained from the i-th business unit in each business flow in, i and j are positive integers.
  • the first communication device may receive one or more service streams.
  • the first communication device may generate the N service streams according to the received one or more service streams.
  • the first communication device may generate M recovery streams according to the generated N service streams.
  • the first communication device may encode or verify the i-th service unit of each of the N service streams, so as to generate the i-th recovery unit in the M recovery streams.
  • the i-th restoration unit in the at least one restoration unit is obtained by performing verification or error correction coding on the i-th service unit in each of the N service flows.
  • the check method may be a sum check, a cyclic redundancy check (cyclic redundancy check, CRC), and a bit interleaved parity (bit interleaved parity, BIP) odd check or even check.
  • CRC cyclic redundancy check
  • BIP bit interleaved parity
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each service flow in the N service flows includes at least one service bit
  • the at least The k-th restoration bit in one restoration bit is a result of performing BIP on the k-th service bit of at least one service bit in the i-th service unit of each of the N service streams, and k is a positive integer.
  • the BIP check method can check a bit in each service stream through a check bit, and the amount of data transmitted in the recovery stream is small, and the impact on the system is small.
  • error correction coding can be forward error correction (FEC) coding, for example, Reed-Solomon (Reed-Solomon, RS) coding, Bose-Chaudhuri (Bose-Chaudhuri) -Hocquenghem, BCH) coding, etc.
  • FEC forward error correction
  • RS Reed-Solomon
  • Bose-Chaudhuri Bose-Chaudhuri
  • BCH Hocquenghem
  • the error correction coding method can also be a hybrid error correction mode.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • the i-th service unit in each of the N service streams includes at least one service bit group
  • the k-th recovery bit group in the at least one bit group includes performing forward error correction FEC on the k-th service bit group in at least one service bit group in the i-th service unit of each of the N service streams
  • the number of bits in each of the k-th service bit group is less than or equal to half of the number of redundant bits, and k is a positive integer.
  • a larger number of bits can be corrected by RS coding and decoding, so that the amount of data transmitted in the recovery stream is small, and the impact on the system is small.
  • the i-th restoration unit may be carried in the M restoration streams. That is, each of the M recovery streams includes a part that may include the i-th recovery unit, and these parts together constitute the i-th recovery unit.
  • step S302 the first communication device sends the M recovery streams and the N service streams to the second communication device.
  • the M recovery streams may be sent through M recovery paths, and the N service streams may be sent through N service paths.
  • the M recovery streams correspond to the M recovery paths one-to-one.
  • the N service flows correspond to the N service paths one-to-one.
  • the path may be a physical link or a logical connection, which is not limited in the embodiment of the present application.
  • a service flow transmitted through a physical port may be regarded as a service flow transmitted through a path, that is, a service flow corresponds to a physical port.
  • a path only transmits service flow through one physical port, and the link where a physical port is located carries only one path to transmit service flow.
  • the service flow transmitted by one physical port is transmitted through multiple paths, and the link where a physical port is located carries multiple paths to transmit different service flows, and different service flows carry different labels.
  • the service flow carrying the same label may be a service flow transmitted through a path.
  • the M recovery streams and the N service streams can be sent through one or more physical links.
  • the physical link can also be called a link or a channel.
  • the M recovery streams may be sent through M recovery links
  • the N service streams may be sent through N service links.
  • the M recovery streams and the N service streams may be sent through different frequencies or times of a link. The embodiments of this application do not limit this.
  • step S303 the second communication device determines the N service flows.
  • the second communication device may determine the N service streams after receiving the M recovery streams and the N service streams.
  • the second communication device determines the N service streams, that is, determines that the N service streams are the same as the service streams sent by the first communication device, that is, determines the N service streams sent by the first communication device.
  • the second communication device may determine that the received N service streams are correct, and determine that the received N service streams are the N service streams sent by the first communication device.
  • the second communication device may restore the i-th service unit of each service flow in at least one of the N service flows according to the i-th restoration unit.
  • the second communication device may determine that the restored N service flows are the N service flows sent by the first communication device.
  • the j-th service flow may include at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the correctness of the i-th service unit in the j-th service flow.
  • the first communication device may perform verification on the i-th service unit in each service flow, and respectively generate the i-th detection identifier of each i-th service unit.
  • the i-th detection identifier can be sent before or after the i-th service unit.
  • Other fields or bits may be included or not included between the ith detection identifier and the corresponding ith service unit.
  • the second communication device After receiving the i-th detection identifier and the corresponding i-th service unit, the second communication device can immediately verify the i-th service unit.
  • the second communication device may send the i-th service unit. By detecting the identifier, the second communication device can immediately send the service unit after determining that the service unit is correct.
  • the second communication device can determine the service unit that needs to be restored.
  • the second communication device can send the service unit immediately, without waiting for the second communication device to determine the i-th service unit in all service flows and then send it uniformly. .
  • the impact on the system can be reduced, the transmission time of the service unit between the communication equipment and the equipment can be reduced, and the data transmission rate can be increased. Improve user experience.
  • the second communication device can detect the correctness of each service unit in the j-th service flow. Each service unit is correct, and the second communication device can determine that the received N service streams are the N service streams sent by the first communication device.
  • the second communication device saves and determines that the i-th service unit in the j-th service flow is correct, and the second communication device can save the i-th service unit. If all the i-th business units in the N business flows are correct, all the i-th business units stored can be deleted.
  • the second communication device may restore service units in other service streams according to the received restoration unit.
  • the second communication device may restore the service units in other service flows according to the stored service units and the received restoration units corresponding to them. If the i-th service unit in at least one of the N service flows is wrong, the second communication device may restore the i-th service unit of each service flow in the at least one service flow according to the i-th restoration unit. The second communication device may also restore the i-th service unit of each service flow in the at least one service flow according to the i-th restoration unit and the i-th service unit in other service flows.
  • each of the M recovery streams may include the i-th detection identifier.
  • the first communication device may verify the part of the i-th recovery unit sent through the j-th recovery stream among the M recovery streams to generate the i-th detection identifier.
  • the second communication device receives the i-th detection identifier in the j-th recovery stream, and checks the part of the i-th recovery unit in the j-th recovery stream according to the i-th detection identifier, so as to determine the correctness of the part.
  • a part of the recovery streams in the M recovery streams may include the i-th detection identifier.
  • the first communication device may verify the i-th recovery unit to generate the i-th detection identifier.
  • the first communication device may send the i-th detection identifier to the second communication device through one or more of the M recovery streams.
  • the second communication device can determine the correctness of the i-th recovery unit according to the i-th detection identifier.
  • the second communication device may restore the i-th service unit of at least one service flow among the N service flows according to the i-th restoration unit when it is determined that the i-th restoration unit is correct.
  • the service unit and recovery unit can be checked by means of code sum check, BIP or CRC, etc., to obtain the detection identification.
  • the second communication device may determine the received service flow or the restored service flow as the service flow sent by the first communication device, and perform subsequent processing. After determining the N service streams, the second communication device may send the N service streams to other communication devices, or the second communication device may process the N service streams and send the processing results to other communication devices.
  • the i-th detection identifier may include multiple parts, which are respectively used to detect different parts of the i-th service unit.
  • the second communication device may send the part, or may send the i-th service unit after confirming other parts.
  • the second communication device may restore the i-th service unit according to the i-th restoration unit.
  • the second communication device may also recover only the part where the i-th service unit confirms the error.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes an alignment identifier corresponding to the service flow
  • the alignment indicator is used to indicate the correspondence between the i-th restoration unit and the i-th service unit in each of the N service streams.
  • any one of the N service streams and M recovery streams may include one or more alignment markers (AM).
  • the multiple alignment marks may be the same or different.
  • the identification may be an identification number or the like.
  • path alignment is performed, and the AM corresponding to the path can be inserted in different paths. By inserting AM when the path starts to work, or periodically inserting AM, or inserting AM corresponding to each service unit or recovery unit, the i-th service unit in each service flow corresponding to the i-th recovery unit can be determined.
  • the i-th service unit and the i-th restoration unit in each service flow may correspond to the same or different alignment identifiers.
  • the alignment mark may be an identification number.
  • the i-th service unit and the i-th restoration unit in each service flow may correspond to the same alignment identifier.
  • a service unit may include at least one bit, at least one code block, or at least one service frame, service packet or service block. For a case where a service unit includes at least one service frame, service packet or service block, since the length of each service unit may not be equal, that is, the number of bits included in each service unit is not equal.
  • the first communication device may fill a fixed sequence after the shorter business unit, for example, add "0" or "1", or add a fixed sequence after at least one business unit according to the specific method of generating the recovery unit. Sequence, so as to verify or encode, determine the recovery unit.
  • the i-th restoration unit may also have at least one restoration bit group, where the k-th restoration bit group is based on the k-th service bit group in each i-th service unit in at least one of the N service streams. , And the padding bit groups in other service streams in the N service streams.
  • the k-th restoration bit group includes at least one bit
  • the k-th service bit group includes at least one bit.
  • the k-th service bit group includes at least one stuffing bit and/or at least one bit in the service unit.
  • the length of each business unit may not be equal.
  • the first communication device may perform verification in a manner of "0", "1" or other preset sequence of the bit value of the service unit to generate a recovery unit.
  • the second device needs to determine where the business unit ends when restoring the business unit.
  • a specific identifier can be added at the end of the service unit, that is, at the end of the service unit.
  • a specific character string can be added, or an alignment mark can be added at the end of the business unit to indicate the end of the business unit.
  • Business units can include business frames, business packages or business blocks.
  • the length of the service frame, service packet or service block is not the same. Take the business frame as an example.
  • Each business unit can include a different number of business frames.
  • the i-th service unit of each of the N service streams may include an alignment identifier for indicating the end of the service unit.
  • the i-th service unit of each of the N service streams includes at least one alignment identifier, where each alignment identifier is located at the end of a service packet or a service frame, and is used to indicate the service packet or The end of the business frame.
  • the i-th service unit in the j-th service stream can be restored: the second communication device does not receive the i-th detection identifier in the j-th service stream, and the second communication device does not After receiving the AM of the i-th service unit in the j-th service flow, the second communication device detects an error according to the i-th detection identifier in the j-th service flow.
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • the number of bits of the i-th restoration unit is the length of the i-th restoration unit.
  • the number of bits of the i-th service unit is the length of the i-th service unit.
  • the i-th restoration unit may only include at least one restoration bit group, or at least one restoration bit.
  • the number of bits of the i-th restoration unit may be a positive integer multiple of the number of bits of the i-th service unit. For example, for the i-th recovery unit determined by BIP, the number of bits of the i-th recovery unit may be equal to the number of bits of the i-th service unit; for the i-th recovery unit determined by the RS encoding method, the number of bits for the i-th recovery unit may be The number of bits of the i-th service unit is equal to twice.
  • the i-th restoration unit may also include fields corresponding to formats such as frames, code blocks, packets, and blocks.
  • the i-th restoration unit may include the synchronization header of the Ethernet 64B/66B code block, the encapsulation header in the frame format, and so on.
  • steps S301-S303 at least one service flow can be protected, and error detection and correction methods can be extended to network protection, and the service flow can be restored when all or part of the service flow is incorrectly received. Avoiding business data loss can reduce the impact of business data protection on the system and improve network utilization. Through the above method, there is no need to detect path failures.
  • the above-mentioned method can be applied to public networks and private networks, such as Ethernet, optical transport network (optical transport network, OTN), synchronous digital hierarchy (SDH), storage and other networks.
  • Ethernet frames, code blocks, IP packets, OTN frames, SDH frames, common public radio interface (CPRI) frames, FC (fibre channel) frames, and other services that are transmitted in bit stream mode, can all be implemented through this application.
  • CPRI common public radio interface
  • FC (fibre channel) frames and other services that are transmitted in bit stream mode
  • the method provided in the example for recovery will not cause data loss, the user will not perceive, and the user experience will be improved.
  • the first communication device and the second communication device may be operator edge devices (provider edge devices, PE) or operator (provider, P) devices.
  • the technical solutions provided by the embodiments of the present application can be applied to, for example, network devices supporting Ethernet interfaces.
  • the network device can be a switch, a router, etc.
  • the first communication device may be, for example, an ingress PE device, or may be called an ingress node (ingress unit), and the second communication device may be, for example, an egress PE device, or may also be called an egress node (egress unit).
  • the foregoing manner can be applied to a situation where the first communication device and the second communication device transmit service streams and recovery streams through or without intermediate nodes.
  • the embodiments of the present application can be applied to a point-to-point link, or can also be applied to an end-to-end network.
  • Intermediate nodes can be used for cross-over of streams at the code block level.
  • the intermediate node can also implement frame forwarding.
  • the intermediate node can be used to implement the function of an Ethernet switch and implement the layer 2 (L2) layer Ethernet switching function.
  • L2 layer 2
  • the intermediate node can be used for bit-level stream cross, and the intermediate node can be a device that implements SDH or OTN cross.
  • the intermediate node may only forward the service flow and the recovery flow.
  • the intermediate node may also use the method provided in the embodiment of the present application to restore the service flow.
  • the recovery of the service flow by the intermediate node can improve the accuracy of service data transmission.
  • the Ethernet interface can be used to perform all or part of the functions of the medium access control (MAC) layer, the reconciliation sublayer (RS), and the physical (PHY) layer.
  • the method of data transmission by the Ethernet interface can be implemented by a chip or a field-programmable gate array (FPGA).
  • Fig. 4 is a schematic flow chart of a method for Ethernet data transmission, which mainly describes related processing procedures of the physical layer.
  • the packet is checked and verified according to a certain medium independent interface (medium independent interface).
  • MII medium independent interface
  • the PCS sublayer receives xMII information sent by various MII (some kind of MII, xMII) interfaces, and performs bit code block coding and rate matching.
  • xMII is generally used between the MAC layer and the physical layer of Ethernet equipment. In some embodiments, the xMII interface exists within the integrated circuit.
  • the PCS sublayer is coded according to the 64-bit (bit, B)/66B rule to form a serial stream.
  • the PCS sublayer further encodes the 64B/66B code block into a 257B code block stream according to the 256B/257B coding rule.
  • an alignment marker (AM) group is inserted.
  • AM alignment marker
  • the 257B code block stream is distributed to 2 FEC codes according to 10-bit symbols, and check bits are added.
  • FEC coding it is distributed to 8 PCSLs according to 10 bits per symbol. It should be understood that the FEC encoding and decoding methods adopted by the 2-channel FEC are the same, and the encoding-decoding rate and the ability to resist burst errors can be improved through the 2-channel FEC.
  • PCSL physical coding sublayer lanes
  • the inserted AM will be distributed on each PCSL.
  • the symbols on the PCSL can be sent to the second communication device through a physical medium attachment (PMA) and a physical medium dependent (PMD).
  • PMA physical medium attachment
  • PMD physical medium dependent
  • the second communication device receives the symbols sent by the first communication device through PMD and PMA, uses the AM on each PCSL to lock the channel, and reorders each PCS channel to obtain a symbol stream, and then RS-decodes the symbol stream to form a string Line code block stream and remove the AM group in the serial code block stream, and then descramble and reverse transcode the serial code block stream after removing the AM group to obtain a 64B/66B serial code block stream.
  • the 64B/66B serial code block stream is decoded and rate-matched and sent to the RS sublayer and the MAC layer, and the data is transmitted to the data link layer through the MAC layer.
  • a bit is a bit in a binary number, a unit of measurement of the amount of information, and the smallest unit of the amount of information.
  • the 257B code block stream, the 66B code block stream, and the symbol stream distributed to the logical channel can all be understood as bit streams.
  • FIG. 4 only briefly describes the processing flow of the Ethernet interface. Specifically, other processing procedures may be added in the application, or some of the above-mentioned processing procedures may be reduced.
  • the above method is applicable to 200G and 400G Ethernet interfaces. For 40G and 100G Ethernet interfaces, the process of FEC encoding, FEC decoding and 257B transcoding may not be included.
  • the FEC encoding and decoding may be, for example, Reed-Solomon (RS) encoding.
  • RS Reed-Solomon
  • the purpose of RS encoding is to further improve the correct rate of the bit stream during transmission.
  • RS Reed-Solomon
  • the bits with errors can be corrected according to the inserted check bits.
  • RS coding it can be considered that without changing the original code block stream, some check bits are inserted every certain bit interval.
  • the check bits inserted in the RS code are calculated and recovered the bits that were in error during transmission. After the check is completed, these check bits are removed.
  • Fig. 5 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • the network element A and the network element Z can transmit service flows through at least one path.
  • the 1#-3# path is used to transmit the service flow sent by the network element A to the network element Z, and the bit interleaved parity (BIP) odd check is adopted between the network element A and the network element Z.
  • BIP bit interleaved parity
  • Network element A receives three user streams from S1 to S3 and encodes them to form a 64B/66B code block stream.
  • the 64B/66B code block stream formed by the data received from the S1 interface is sent to the Z network element through the 1# path.
  • the 64B/66B code block stream formed by the data received from the S2 interface is sent to the Z network element through the 2# path.
  • the 64B/66B code block stream formed by the data received from the S3 interface is sent to the Z network element through the 3# path.
  • the A network element may be the first communication device, and the Z network element may be the second communication device.
  • a service unit can include 64 consecutive 64B/66B code blocks used for service transmission, or consecutive 64B/66B code blocks that are integer multiples of 64. 66B code block.
  • the 64B/66B code blocks used for service transmission may also be referred to as 64B/66B service code blocks. Take a business unit including 64 64B/66B business code blocks as an example for description.
  • the A network element can perform CRC check on the business unit sent to the 1# path, generate the CRC information of the business unit, and send the CRC information through the 1# path.
  • the CRC information can be sent after the service unit.
  • the A network element can perform CRC check on the business unit sent to the 2# path, generate the CRC information of the business unit, and send the CRC information through the 2# path.
  • the CRC information can be sent after the service unit.
  • the A network element can perform CRC check on the service unit sent to the 3# path, generate the CRC information of the service unit, and send the CRC information through the 3# path.
  • the CRC information can be sent after the service unit. That is, the A network element sends the CRC information corresponding to the service unit through the path where the service unit is located.
  • the CRC information can be carried by the control code block.
  • the control code block that carries CRC information can be called a detection code block or a detection identifier.
  • the detection mark can also be CRC information.
  • the detection code block can be located after its corresponding service unit, that is, the A network element can send the detection code block corresponding to the service unit after sending the service unit.
  • the detection code block can be sent after the restoration unit.
  • the A network element performs BIP check on a bit in the same position in the corresponding service unit in the bit stream transmitted by the 1#-3# path to generate a bit in the BIP unit transmitted through the 4# path.
  • the BIP unit can also be called a recovery unit.
  • Each bit in the 64 ⁇ 66B in the service unit is a service bit
  • each bit in the 64 ⁇ 66B check information is a recovery bit.
  • every 64 bits is used as the data in a code block, and a 2-bit synchronization header 01 is added (that is, the code block type is data code block ), forming 66 64B/66B code blocks.
  • one recovery unit includes the 66 64B/66B code blocks.
  • the recovery unit may also be referred to as a BIP unit.
  • the CRC information can be carried in a control code block.
  • the type of the control code block can be 0x4B, 0x2D, 0x55, 0x00, etc.
  • the CRC information can be carried in one or more data bytes, and can also be carried in one or more control bytes.
  • the three paths 1# to 4# may be paths of the Ethernet physical layer.
  • the 1#-4# path can be aligned by adding an alignment marker (AM) to the 64B/66B code block stream. That is, the A network element can periodically insert the AM corresponding to the path in the code block stream transmitted by the path 1#-4#.
  • the AM in each path can be the same or different.
  • the alignment mark may also be called an alignment mark.
  • the transmission rate of the 4# path may be appropriately increased, so that the signal transmitted by the 4# path can be synchronized with the 1#-3# path.
  • the recovery unit can also be transmitted through two or more paths.
  • the transmission rate of the 1#-3# path is the same, and the transmission rate of the 4# path can be increased to that of the 1#-3# path.
  • the transmission rate is 66/64.
  • the transmission rate of path 4# can be increased to 67/65 of the transmission rate of path 1#-3#.
  • the recovery unit can also be transmitted through two or more paths.
  • a control code block filled with specific information can be inserted in the two or more paths, so that the Z network element can receive the recovery unit and the service unit corresponding to the recovery unit at the same time.
  • the transmission rate of the two or more paths can also be reduced, so that the Z network element can receive the recovery unit and the service unit corresponding to the recovery unit at the same time. It should be understood that the same time also includes approximately the same time.
  • the Z network element can recover the data transmitted on one path in the 1#-3# path according to the received data.
  • the Z network element can take one service unit and one detection code block from the bit stream transmitted by the 1#-3# path each time.
  • the business unit corresponds to the detection code block.
  • the detection code block is obtained by verifying the service unit.
  • a business unit is 64 64B/66B code blocks.
  • the Z network element takes a recovery unit and its corresponding detection code block from the code block stream transmitted by the 4# path.
  • the recovery unit corresponds to the business unit taken from the 1-3# path.
  • the recovery unit is 66 64B/66B code blocks.
  • the Z network element can restore the data of any path in the 1#-3# path according to the data received by the 4# path. Take the 3# path as an example.
  • the detection code block that the Z network element has not received from the 3# path can be a code block with a sync header of 10 that has not been received, or a code block with a sync header of 10 whose type is not 0x4B type code block, or the O0 field in the code block is not 0x06.
  • the data transmitted on the 3# path can be restored based on the data received by the 4# path and the data transmitted by the 1# and 2# paths.
  • the Z network element regards the restored result as the service unit sent by the A network element.
  • the detection code block can be used to detect the correctness of the service code block.
  • the Z network element can check the correctness of the service unit taken in the 1#-3# path according to the detection code block.
  • the Z network element receives the service unit and the detection code block corresponding to the service unit.
  • CRC calculation is performed on the business unit, and the calculation result CRC-24 is compared with the CRC-24 in the detection code block. If they are the same, the business unit is considered to be correct and no error has occurred. If the CRC calculation result of the business unit is consistent with the CRC-24 in the detection code block, that is, there is no error in the transmission process, a copy is saved and sent immediately.
  • the CRC-24 calculation result of the Z network element is consistent with the CRC-24 in the detection code block, that is, there is no error code in the transmission process, and a copy is saved and sent immediately.
  • the CRC-24 calculation result of the Z network element is consistent with the CRC-24 in the detection code block, that is, there is no error in the transmission process, and a copy is saved and sent immediately.
  • the Z network element can delete the copied business unit and recovery unit.
  • Path 4# receives a recovery unit including 66 64B/66B code blocks and a detection code block, each data code block carries BIP monitoring bits, and the detection code block carries CRC-24 code blocks. Since there are no errors from 1# to 3#, the BIP result received through the 4# path does not require error detection and correction, and can be discarded.
  • the correctness of the recovery unit can be detected through the detection code block corresponding to the recovery unit received from path 4#. If the CRC-24 calculation result of the recovery unit is consistent with the CRC-24 in the detection code block, that is, there is no error in the transmission process, and error correction is performed on the path with the error. Otherwise, no error correction is performed.
  • the Z network element uses the error correction result as the service unit sent by the A network element.
  • the Z network element After determining the i-th business unit transmitted by each path of the 1#-3# path, the Z network element can delete the saved i-th restoration unit.
  • the A network element divides the code block stream into multiple services by inserting control code blocks including CRC information Unit to send the service flow to the Z network element. Between A network element and Z network element, add a path to transmit BIP information. Based on the BIP information, the Z network element can restore any business unit based on the BIP error detection method. The recovery of the business unit also includes the error correction of the business unit.
  • the detection code block can also be used for the alignment of the 1#-4# path.
  • the detection code block can be used as an alignment mark.
  • the alignment information corresponding to each path can be carried by the detection code block, and the Z network element realizes the alignment of the path according to the detection code block.
  • the solution proposed by the embodiment of the present application can detect the fault of the line by detecting the inserted control code block, and can realize the recovery of the service flow without special setting of the APS protocol.
  • error detection and error correction can be performed on the transmitted signal.
  • the implementation is simple and easy to deploy.
  • one resource is occupied for transmission of the recovery unit, and data transmitted through multiple paths can be protected, the network utilization rate is high, and no packet loss occurs.
  • Fig. 6 is a schematic diagram of the types of 64B/66B code blocks in the IEEE802.3 specification.
  • 64B/66B encoding encodes 64bit data or control information into 66bit blocks for transmission.
  • the first two bits of the 66bit block represent the synchronization header, and the last 64bit can be called the data payload.
  • the sync header is "01”
  • the 64 bits after the sync header are all data.
  • the sync header is "10”
  • the 64 bits after the sync header include data and/or control information.
  • the first 8 bits in the data load that is, the 8 bits adjacent to the sync header, are the type domain, which can indicate the type of the control code block.
  • the last 56 bits in the data payload that is, the 56 bits after the type field are control information and/or data.
  • D represents data bytes, each data byte is 8 bits; C represents control bytes, each control byte is 7 bits; S represents the beginning of the data packet, and T represents the end of the data packet; O Represents the ordered set control code block (for example, the type is 0x4B, the value of O is different, and the usage scenarios are different). S can only appear in the 0th and 4th bytes of the 8 bytes, and T can appear in any byte.
  • a code block containing S can be called an S code block, and a code block containing T can be called a T code block.
  • Idle (IDLE) code blocks is C 0 ⁇ C 7 0, low power consumption (LPI) block code C 0 ⁇ C 7 to 6.
  • the data packet may be obtained based on an Ethernet frame, for example.
  • the control code block used to carry CRC information can be 0x4B, 0x2D, 0x55, 0x00, etc. Take the 0x4B code block as an example.
  • Fig. 7 is a schematic diagram of a control code block provided by an embodiment of the present application. This code block is used to carry CRC information.
  • the control code block of type 0x4B is used for description.
  • the information carried by O0 of the control code block can be used to indicate that the code block is a code block that carries CRC information, that is, a detection code block. That is, O0 can be used to identify the code block as a detection code block. For example, O0 is 0x6 indicating that the code block is a detection module.
  • the control byte of the 0x4B control code block can be 0x0, and can also be used to carry other information.
  • the detection code block can be used to detect path failures.
  • the Z network element does not detect the detection code block in the j-th service flow within the preset time interval, it can be considered that the j-th path used to transmit the j-th service flow is faulty.
  • the Z network element can notify the A network element, and can also output path failure indication information to indicate the jth path failure.
  • the detection code block can also be used for a code block that carries CRC information.
  • CRC information is carried through D1 to D3.
  • D1 to D3 are 24 bits in total, the CRC information may include 24 bits, and the CRC information carried by this field may also be called CRC-24.
  • Fig. 9 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • the communication method provided in the embodiments of the present application may also be used for service data transmission.
  • the A network element can add an alignment mark at any position of the service frame, for example, add an alignment mark at the end of the service frame, that is, the alignment mark may be located after the service frame or at the end of the service frame payload.
  • the A network element performs CRC check on the service frame and adds the CRC check information obtained by the check at any position of the service frame, for example, at the end of the service frame, before or after the alignment mark.
  • the A network element can perform a CRC check on the service frame and the alignment mark, and add the CRC check information obtained by the check at any position of the service frame.
  • the position for adding the alignment mark and the CRC check information may be agreed upon by the A network element and the Z network element, or configured in advance.
  • the Z network element receives the service frame, alignment identifier and CRC check information, performs CRC check on the service frame, or performs CRC check on the service frame and alignment identifier, and compares the check result with the CRC received by the CRC after the service frame. Empirical information for comparison. If the check result is the same as the CRC check information, the Z network element can determine that the service frame is correct; otherwise, the service frame has errors. After that, the Z network element can remove the CRC check information.
  • the Z network element may determine the recovery frame corresponding to the service frame according to the alignment identifier, and may also determine other service frames corresponding to the service frame according to the alignment identifier.
  • the Z network element can remove the alignment mark, and perform follow-up processing on the service frame from which the CRC check result and the alignment mark are removed.
  • the MAC layer can perform a CRC check on the sent Ethernet frame and append the check result CRC-32 information to the end of the Ethernet frame, and send it to the physical layer link, and the receiving end MAC layer can check the received frame CRC check calculation is performed and compared with the CRC-32 information sent by the opposite end to determine whether the Ethernet frame is correct. If the CRC check fails, the embodiment of this application can be used to provide a service data recovery solution.
  • the detection identifier may be CRC-32 information in the Ethernet frame.
  • the detection identifier includes the CRC-32 information of the multiple Ethernet frames, and the detection identifier may also be check information obtained by performing a CRC check on the service unit.
  • the detection identifier can also be added to the Ethernet frame in other ways. For example, if there is an intermediate node between the A network element and the Z network element, and the data transmitted by the 1#-4# path is forwarded by other network elements, the A network element can add CRC- to the Ethernet frame according to the IEEE802.3 specification. 32 information, the A network element can also add additional detection identifiers to the service flow and the recovery flow, which is used for the Z network element to check the correctness of the service unit and the recovery unit.
  • the intermediate node that forwards the service path and the recovery flow may only forward the service flow and the recovery flow. Alternatively, the intermediate node may also use the method provided in the embodiment of the present application to restore the service flow. The recovery of the service flow by the intermediate node can improve the accuracy of service data transmission.
  • the A network element and the Z network element can adopt similar processing as the service frame.
  • a 100Gbps Ethernet link is deployed between NE A and NE Z.
  • a total of three Layer 2 virtual private network (layer 2 virtual private network, L2VPN) services from S1 to S3 are transmitted to NE A and passed through 1
  • the path #-3# is sent to the network element Z, and the even parity of BIP is used between the network element A and the network element Z to form the recovery information transmitted on the 4# path.
  • the A network element forms the recovery unit of the 4# path according to the service frames transmitted by each path in the 1#-3# path.
  • Network element A receives data from S1, S2, and S3 and forms a service frame to be transmitted through any one of the 1#-3# paths.
  • the service frame is sent to the Z network element through the MAC layer and the physical layer of the A network element. Through the transmission of the physical layer and MAC layer of the Z network element, the Z network element receives the service frame.
  • the network element A fetches the service frames to be sent corresponding to each path in the 1#-3# path each time, that is, 3 service frames.
  • the network element A takes one bit at a time in the service frame acquired in each path to perform BIP verification, and forms a recovery frame according to the result of the BIP, that is, the BIP monitoring bit group.
  • the A network element can perform BIP verification on each bit in the service frame, that is, the header and payload of the service frame are both BIP verified.
  • Network element A can also perform BIP verification on some fields in the service frame.
  • the payload of the recovery frame includes the BIP check result.
  • the verification result may include the result of verifying all or part of the fields of the service frame header, or may not include the result of verifying the service frame header.
  • the service frame includes an alignment mark at the end of the service frame. Perform a BIP check on the first bit bit 0 of each service frame sent to the 1#-3# path to obtain BIP0 as the first bit of the payload of the recovery frame. Perform a BIP check on the first bit bit bit1 of each service frame sent to the 1#-3# path to obtain BIP1 as the second bit of the payload of the recovery frame. And so on. Before the payload, add the header of the recovery frame.
  • the header of the frame can also be called the encapsulation header of the frame.
  • the header of the recovery frame may include the destination MAC address and the source MAC address.
  • the destination MAC address and the source MAC address may be designated by the network element A, or agreed upon by the network elements A and Z, or configured by the network management.
  • the network element A when the network element A performs BIP verification, it can add a preset bit sequence after the shorter service frame for verification. For example, add "0" after a shorter service frame, perform BIP check, and generate a recovery frame. For example, among the business frames sent to 1#-3# to generate a recovery frame, the longest business frame includes bit0-bit n, and the shortest business frame includes bit0-bit m. The recovery frame is obtained by BIP inspection. BIP0-BIPn in the Netherlands, m ⁇ n.
  • bits 0-bit n in the service unit are respectively the 0th service bit to the nth service bit
  • BIP0-BIPm are respectively the 0th restoration bit to the nth restoration bit of the restoration unit.
  • the 0th restoration bit to the mth restoration bit are the result of bit interleaving parity check BIP on the kth service bit sent to the service unit of the 1#-3# path, and k ⁇ m.
  • One recovery unit may include all or part of the fields in one or more recovery frames.
  • a business unit can include all or part of the fields of one or more business frames.
  • Each service frame can include a CRC-32 information.
  • the detection identifier may include the multiple CRC-32 information.
  • the A network element performs BIP verification to generate a recovery unit, the multiple CRC-32 information may not be verified.
  • a network element can insert an alignment mark in the service frame.
  • the A network element can insert an alignment mark in the recovery frame.
  • the alignment mark can be located at the head of the frame or in the payload. For example, at the end of the payload of the frame, bytes are added to write the alignment mark.
  • the alignment identifiers in the service frames transmitted by the 1#-3# path used to form the same recovery frame correspond one-to-one with the alignment identifiers in the recovery frame. It should be understood that the identifier in the service frame is used to indicate the recovery frame and other service frames for recovering the frame.
  • the recovery frame 1 is formed based on the service frame 1 transmitted through the 1# path, the service frame 2 transmitted through the 2# path, and the service frame 3 transmitted through the 3# path.
  • the alignment identifier of the recovery frame 1, the alignment identifier of the service frame 1, the alignment identifier of the service frame 2, and the alignment identifier of the service frame 3 are in one-to-one correspondence.
  • the alignment identifier of recovery frame 1, the alignment identifier of service frame 1, the alignment identifier of service frame 2, and the alignment identifier of service frame 3 may be the same or different.
  • the alignment identifier in the service frame and the recovery frame can be a number, starting from 1, and the maximum is 65535. If it exceeds 65535, the numbering starts from 1. The description is given by assuming that the alignment identifiers of recovery frame 1, service frame 1 and service frame 3 are the same.
  • Recovery frame 1, service frame 1, service frame 2, and service frame 3 can form a 4 ⁇ n bit check matrix.
  • Recovery frame 1, service frame 1, service frame 2, and service frame 3 respectively correspond to the 4 columns in the check matrix, and n is the length of the longest frame among service frames 1-3.
  • the length of the frame can also be understood as the number of bits in the frame.
  • the A network element can insert an alignment mark in a business unit.
  • a service unit includes multiple service frames, and the A network element may add an alignment mark at the end of the last service frame.
  • the business unit may or may not include the alignment mark.
  • the A network element may also add check information corresponding to each recovery frame in the recovery stream.
  • the verification information is the detection identification.
  • the A network element can perform a CRC check on the recovery frame, and add the check information generated by the check to the recovery frame.
  • a recovery unit includes all or part of the data of a recovery frame.
  • the restoration unit may or may not include the header of the restoration frame, the alignment mark, and the verification mark.
  • Z network element takes one business unit from 1# ⁇ 3# path each time, and takes one recovery unit from 4# path.
  • a service unit can include all or part of the data of one or more service frames.
  • the Z network element For any path in the 1#-3# path, if the Z network element receives the expected business unit within the specified time window, it will perform a CRC check on the business unit. If the check result is correct, the business unit will be saved Send immediately after.
  • the Z network element can also verify the business frame after receiving each business frame, and if the verification result is correct, the business frame is saved and sent immediately. If the CRC check result of a certain service frame is wrong, only the service frame can be restored, which reduces the calculation amount of the Z network element and improves the transmission efficiency.
  • the Z network element receives the recovery unit on path 4#. At this time, if the service units with the same identifier are all verified correctly or have been sent, the recovery unit is discarded.
  • the Z network element does not receive the expected service frame from one of the paths 1 ⁇ 3#. For example, if the expected service frame is not received on the 2# path within the specified time window, then the 2# path The transmitted business unit is restored, and each bit of the business unit expected to be received by the 2# path is equal to the BIP calculation result of the corresponding bits of the 1#, 3# and 4# paths.
  • the result of the CRC check performed by the Z network element on the data frame received on the 2# path is wrong, and the CRC check result of the business units with the corresponding alignment marks on the 1#, 3# and 4# paths If it is correct, restore the business unit transmitted by the 2# path, and each bit of the business unit expected to be received by the 2# path is determined according to the business unit transmitted by the 1#, 3# path and the BIP check information transmitted by the 4# path.
  • the alignment mark can participate in the verification or not.
  • the network element A and the network element Z may agree on a field for performing BIP verification in the service frame.
  • the alignment mark When the alignment mark participates in the verification, the alignment mark can be located at the end of each service frame. Since the length of each frame is different, the alignment mark at the end of the frame can be used to determine whether the frame is restored. In other words, the length of the frame can be determined by the identifier at the end of the frame.
  • the alignment mark may be located at the end of the business unit. Since the length of the business unit is different, the alignment mark at the end of the business unit can be used to determine whether the business unit has been restored.
  • a business unit can include one or more business frames. Different business frames can be distinguished by the frame format. Or, the A network element inserts a specific sequence between different service frames to distinguish different service frames in the same service unit.
  • the alignment mark can also be located in other positions of the business unit.
  • the tail of the business unit may include a fixed sequence of fields. Through the fixed sequence of fields at the end of the business unit, it can be judged whether the business unit has been restored.
  • the communication method provided in this application is described.
  • a BIP check matrix is constructed according to the service frames and recovery frames transmitted by each path, and any lost or erroneous service frames are recovered based on the BIP error detection method.
  • the present invention does not need to specifically detect line faults, does not need to specifically set APS protocol, and only needs to judge the business frame, such as judging the correctness of the frame through the CRC-32 check result of the MAC, or whether the expected frame is received in the designated window. Can be implemented to restore the correct business data.
  • the implementation is simple and easy to deploy.
  • FIG. 11 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • a 200Gbps Ethernet link is also set up between the A network element and the Z network element as the 4# path.
  • Network element A receives Ethernet L2VPN services from the three interfaces S1-S3.
  • the rate of the 1#-3# path can be 100Gbps.
  • the service frames of path 1#-3# are coded using the forward error correction (FEC) method of RS (544,514) to form a recovery frame.
  • the recovery frame passes through the 4# path between A and Z, from A
  • the network element is transmitted to the Z network element.
  • FEC forward error correction
  • Each symbol has a length of 10 bits, that is, a symbol has a length of 10 bits.
  • Each RS codeword includes 514 symbols of data and 30 symbols of check information, which may also be called redundant bits.
  • the A network element performs RS (544,514) coding calculation for each 514 symbol length data to generate 30 symbol length redundant bits to form an RS codeword; the receiving end receives the RS codeword, and performs data on the 514 symbols of the data And 30 symbol-long redundant bits, perform RS (544,514) decoding calculation.
  • the RS codeword formed by the RS(544,514) method can correct errors of 15 symbols in the data of 514 symbols at most.
  • the network element A receives the services sent by the paths S1, S2, and S3. According to the received service, a service frame is generated.
  • a business unit can include one or more business frames. Take a business unit including a business frame as an example for description.
  • a network element transmits 3 business frames to Z network element through each path of 1#-3# path.
  • the 30-symbol-long parity information is a recovery bit group.
  • the information to be filled can be a preset value, or it can be agreed by the A network element and the Z network element, for example, 4690 "0"s are filled for RS (544,514) encoding.
  • the 15 symbols of each of the above 3 service frames, 30 symbols (300 bits) of the check information, and 469 filled symbols constitute an RS codeword.
  • RS (544,514) encoding 15 symbols in each service unit in the 1#-3# path are used as a service bit group, and a 30-symbol-long recovery bit group is generated.
  • the generated recovery bit group is used to determine the recovery unit.
  • One restoration unit may include one or more restoration frames.
  • the encapsulation header of the recovery frame includes the destination MAC address and the source MAC address.
  • the destination MAC address and the source MAC address can be specified by the A network element and the Z network element.
  • Each business unit or recovery unit transmitted through the 1#-4# path includes an alignment mark.
  • a network element sends a service flow to Z network element through 1# ⁇ 3# path, it inserts an alignment mark in each service unit, and when sending a recovery flow through 4# path, it inserts an alignment mark in each recovery unit.
  • the i-th restoration unit transmitted by the 4# path is generated according to the i-th service unit transmitted by each path in the 1#-3# path.
  • the i-th alignment identifier can be inserted in the i-th recovery unit transmitted by the 4# path, and the i-th alignment identifier in the i-th recovery unit can be inserted in the i-th service frame transmitted by each path in the 1#-3# path
  • the alignment identifier in each i-th business unit and the alignment identifier in the i-th restoration unit may be the same or different.
  • the alignment identifier in each i-th service unit and the alignment identifier in the i-th restoration unit may be the same number. For example, start counting from 1, the maximum is 65535, and when counting to 65535, start from 1.
  • the alignment mark can be located at the head of the frame or the frame payload. For example, it can be located at the end of the frame payload.
  • the A network element can check each frame and append the check result CRC-32 to the end of the service frame.
  • Both the service frame and the recovery frame can be called data frames.
  • a network element can add an alignment mark at the end of the data frame.
  • the A network element may perform a CRC check on the data frame including or not including the alignment mark, and add the obtained CRC check information to the end of the data frame, after the alignment mark.
  • the Z network element receives the stream transmitted by the 1#-4# path.
  • the expected business unit received within the specified time window may be a business unit including a preset alignment identifier received within the specified time window, or a business unit corresponding to the alignment identifier of the business unit or restoration unit of other paths or the recovery unit.
  • the Z network element receives the restoration unit on path 4#, and the restoration unit includes the i-th alignment identifier. At this time, if the service units transmitted by the path 1#-3# corresponding to the i-th unit identifier have all been CRC checked and are correct, then the restoration unit is discarded. If at least one of the service units transmitted by the path 1#-3# corresponding to the i-th unit identifier has not yet been CRC checked, or the check is incorrect, the restoration unit is saved.
  • the Z network element For path 1#-3#, if the Z network element does not receive the expected unit on a path within the specified time window, it can restore the service frame of the path based on the service frame and recovery frame received from other paths. Or, if the CRC check result of the service frame transmitted on one or more paths is wrong, the error can be corrected according to the service frame and the recovery frame on each path.
  • the Z network element receives service units or recovery units containing corresponding identifiers on paths 1#, 3#, and 4#. For example, these service units and recovery units contain the same number.
  • the Z network element did not receive the service unit including the corresponding identifier on the 2# path.
  • the corresponding business units on the 2# path can be restored based on the business units and recovery units received by the 1#, 3#, and 4# paths.
  • the service unit expected to be received on the 2# path every 15 symbols (150 bits) can correspond to the 15 symbols (150 bits) corresponding to 1# and 3#, and the corresponding 30 symbols (300 bits) in the recovery frame of the 4# path.
  • bit 0 ⁇ 149 of the service frame received by path 1# bit 0 ⁇ 149 of the service frame received by path 3#
  • bit 96 ⁇ 395 of the recovery frame received by path 4# (assuming that the frame encapsulation header of the recovery unit occupies 12 bytes, That is, bit0 ⁇ bit95)
  • the expected received service unit bits0 ⁇ 149 of path 2# can be completely recovered through RS(544,514) decoding. In this way, the entire business unit of path 2# can be restored and sent.
  • a frame containing a corresponding identifier is received on the path 1#-4#, and a CRC check is performed on each frame, and the result of all or part of the frames is incorrect.
  • RS RS decoding
  • a fixed sequence can be filled at the end of the service frame, such as filling "0", "1” Or their specific combination to meet RS codec requirements.
  • Each RS codeword requires 5140 bits of service information, and the number of service paths is small.
  • the number of bits to be encoded each time is less than 5140 bits, it can also be filled with a fixed sequence, such as filling "0", "1” or a specific combination , To construct the RS codeword. It should be understood that these filled fixed sequences may or may not be transmitted through a path, and are only used as an agreed format for RS encoding and decoding.
  • the alignment identification of the business unit can participate in the verification or not.
  • the business unit may include an alignment identifier, and the alignment identifier may be used to indicate a restoration business unit that restores the business unit.
  • the alignment identifier can also be used to indicate other business units that restore the business unit.
  • the alignment mark can be located at the end of the business unit. Since the length of each frame is different, through the identification at the end of the business unit, it can be judged whether the business unit has been restored. In other words, the length of the business unit can be determined by the identification at the end of the business unit.
  • the alignment mark can also be located in other positions of the service frame.
  • the tail of the business unit may include a fixed sequence of fields. Through the fixed sequence of fields at the end of the business unit, it can be judged whether the business unit has been restored.
  • the protection path can be used to carry the recovery unit, and the recovery unit can include redundant bits obtained by FEC encoding.
  • the 4# path may be twice the transmission rate of the 1#-3# service path.
  • the FEC check information can be sent through two protection paths 4# and 5#.
  • the 4# and 5# paths can be equal to the transmission rate of the 1#-3# service path, or slightly higher than the transmission rate of the 1#-3# service path. It should be understood that equality can be approximately equal.
  • the A network element When the A network element performs RS encoding, the number of symbols transmitted by each path in an RS code word is adjusted, and the Z network element can realize the recovery of multiple service streams. For example, the A network element adopts the RS (544, 514) coding mode, and the 1#-3# path takes 50 symbols long for RS coding, and the data transmitted by the 1#-3# path can be protected.
  • the FEC codeword is constructed from the service units transmitted by each path, the A network element at the transmitting end performs FEC encoding, and the Z network element at the receiving end performs FEC decoding, thereby recovering at least one lost service unit or performing error correction on the service unit transmitted by each path .
  • the present invention does not need to specifically detect line faults, and does not need to specifically set APS protocol. It only needs the Z network element of the receiving end to determine whether the service unit is receiving, or to determine the correctness of the frame according to the CRC check result, and then the service data in the Ethernet frame Perform recovery or error correction.
  • the implementation is simple and easy to deploy.
  • FIG. 13 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • One FEC codeword formed by FEC encoding can perform error correction on at most N bits, and no more than N bits are taken in each path to perform FEC encoding to form an FEC codeword.
  • the transmitting end A network element takes N bits from the bit stream to be transmitted on the 1#-3# path each time, and 3 channels and 3 groups of N-bit signals form a FEC codeword, and implement FEC encoding.
  • the remaining bit check information is transmitted by path 4#.
  • 2N redundant bits can perform error correction on N bits at most. If N bits are taken in each path for RS encoding to form an RS codeword, the transmission rate of path 4# can be twice that of each path in path 1#-3#.
  • the Z network element at the receiving end takes N bits from 1 to 3# paths and 2N bits from 4# path each time.
  • a FEC codeword is formed according to these bits, and the result of FEC decoding is sent to other communication devices.
  • the 1#-4# path is aligned during the initial operation (the path may be aligned in a certain cycle later), for example, a certain alignment bit is inserted, such as an alignment marker (alignment marker, AM).
  • an alignment marker such as an alignment marker (alignment marker, AM).
  • the technical solution of path alignment can refer to the situation of PCSL/FECL locking, de-jittering and reordering based on AM of 100G/200G/400G Ethernet link in IEEE802.3.
  • network element A at the sending end starts data transmission on path 1#-4#, it sends AM information through path 1#-4#.
  • the Z network element at the receiving end detects AM information, and according to the AM information, locks each path, removes jitter, and reorders the information transmitted in each path.
  • the Z network element removes and discards the AM information from the bit stream.
  • 1#-3#path every field between two AMs can be used as a business unit. 4# The field between every two AMs of the path can be used as a restoration unit.
  • FEC uses the RS (544,514) algorithm, the size of the symbol is 10 bits, and the maximum error correction capability is 150 bits.
  • the transmitting end A network element takes 150 bits to be transmitted each time. According to the 150-bit information of each of the 3 channels, RS coding is performed, and the 2 ⁇ 150-bit check information generated after RS coding is transmitted by the 4# path.
  • the transmission rate of path 4# can be twice that of path 1#-3#.
  • the receiving end Z network element starts from the first bit after the AM information, takes 150 bits of information from each path in the 1#-3# path, and takes 300 bits of information from the 4# path to determine The first RS codeword.
  • the error-corrected service data is sent to other network devices.
  • the receiving end Z network element starts from the 150 ⁇ (K-1)+1 bit after the AM information and takes 150 bits of information from each path in the 1 ⁇ 3# path.
  • the receiving end Z network element starts from the AM
  • the 300 ⁇ (K-1)+1th bit after the information starts to take 300 bits of information from the 4# path to determine the Kth RS codeword.
  • the error-corrected service data is sent to other network devices.
  • the 2N-bit check information generated after FEC encoding is transmitted by the 4#-5# path.
  • the transmission rate of each path in the 1#-5# path is equal. Equality can be approximately equal.
  • the receiving end Z network element protects the business data transmitted by the 1#-3# path according to the verification information transmitted by the 4#-5# path.
  • Each RS codeword requires 5140 bits of service information, and the number of service paths is small.
  • the number of bits to be encoded each time is less than 5140 bits, it can also be filled with a fixed sequence, such as filling "0", "1" or a specific combination , To construct the RS(544,514) codeword. It should be understood that these filled fixed sequences may or may not be transmitted through a path, and are only used as an agreed format for RS encoding and decoding.
  • the embodiments of this application can also be applied to the case where the transmission rates of paths 1#-3# are not equal.
  • the transmission rate of the 2# path is different from other service rates.
  • the transmission rate of the 2# path is 10Gbps
  • the transmission rate of the 1# and 3# paths is 15Gbps.
  • the padding information can be supplemented with "0" to perform RS coding to form an RS (544,514) codeword.
  • the recovery flow generated by the FEC method does not need to determine whether the CRC check result of each packet is correct when replying to the service flow.
  • the recovery of a business unit does not depend on the judgment of the correctness of the business unit or other business units. At least one service path can be protected. Aligning the paths at the beginning makes the implementation more concise and easy to deploy.
  • FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1400 includes a generating module 1410 and a sending module 1420.
  • the generating module 1410 is used to generate M recovery streams and N service streams, where M and N are positive integers;
  • the sending module 1420 is configured to send the M recovery streams and the N service streams to the second communication device, where the j-th service stream of the N service streams includes at least one service unit; the M recovery streams include At least one restoration unit, the i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and i and j are positive integers.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the correctness of the i-th service unit in the j-th service flow.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes an alignment identifier corresponding to the service flow
  • the alignment indicator is used to indicate the correspondence between the i-th restoration unit and the i-th service unit in each of the N service streams.
  • the i-th service unit includes at least one alignment identifier, wherein each alignment identifier is located at the end of a service packet or a service frame, and is used to indicate the end of the service packet or the service frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is obtained by performing verification or error correction coding on the i-th service unit in each of the N service flows.
  • the check method is bit interleaving parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each service flow in the N service streams includes at least one service bit
  • the at least one restoration bit The kth recovery bit in the N service streams is the result of performing BIP on the kth service bit of at least one service bit in the i-th service unit of each service stream, and k is a positive integer.
  • the error correction coding method is forward error correction FEC coding.
  • the error correction coding method is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • each of the N service streams The i-th service unit includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes at least one service bit group in the i-th service unit of each of the N service streams
  • the redundant bits obtained by performing forward error correction FEC encoding on the k-th service bit group in, the number of bits in each k-th service bit group is less than or equal to half of the number of redundant bits, and k is a positive integer .
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • FIG. 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1500 includes a transceiver module 1510 and a determination module 1520.
  • the transceiver module 1510 is configured to receive M recovery streams and N service streams sent by the first communication device.
  • the j-th service stream among the N service streams includes at least one service unit;
  • the M recovery streams include at least one recovery stream.
  • the i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and M, N, i, and j are positive integers;
  • the determining module 1520 is configured to determine the N service flows.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the correctness of the i-th service code block in the j-th service flow.
  • the determining module 1520 is configured to determine, according to the i-th detection identifier, that the i-th service unit in the j-th service flow is correct;
  • the transceiver module 1510 is further configured to send the i-th service unit.
  • the determining module 1520 includes a restoration sub-module configured to restore the i-th service unit of each service flow in at least one of the N service flows according to the i-th restoration unit.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes an alignment identifier corresponding to the service flow
  • the alignment indicator is used to indicate the correspondence between the i-th restoration unit and the i-th service unit in each of the N service streams.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service packet or a service frame, and is used to indicate the end of the service packet or the service frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is obtained by performing verification or error correction coding on the i-th service unit in each of the N service flows.
  • the check method is bit interleaving parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each service flow in the N service streams includes at least one service bit
  • the at least one restoration bit The kth recovery bit in the N service streams is the result of performing bit interleaving parity check BIP on the kth service bit of at least one service bit in the i-th service unit of each service stream, and k is a positive integer.
  • the error correction coding method is forward error correction FEC coding.
  • the error correction coding method is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • each of the N service streams The i-th service unit includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes at least one service bit group in the i-th service unit of each of the N service streams
  • the redundant bits obtained by performing forward error correction FEC encoding on the k-th service bit group in, the number of bits in each k-th service bit group is less than or equal to half of the number of redundant bits, and k is a positive integer .
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1600 includes a processor 1610 and a communication interface 1620.
  • the processor 1610 is configured to generate M recovery streams and N service streams, where M and N are positive integers;
  • the communication interface 1620 is configured to send the M recovery streams and the N service streams to a second communication device, where the j-th service stream of the N service streams includes at least one service unit; the M recovery streams include At least one restoration unit, the i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and i and j are positive integers.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the correctness of the i-th service unit in the j-th service flow.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes an alignment identifier corresponding to the service flow
  • the alignment indicator is used to indicate the correspondence between the i-th restoration unit and the i-th service unit in each of the N service streams.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service packet or a service frame, and is used to indicate the end of the service packet or the service frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is obtained by performing verification or error correction coding on the i-th service unit in each of the N service flows.
  • the check method is bit interleaving parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each service flow in the N service streams includes at least one service bit
  • the at least one restoration bit The kth recovery bit in the N service streams is the result of performing BIP on the kth service bit of at least one service bit in the i-th service unit of each service stream, and k is a positive integer.
  • the error correction coding method is forward error correction FEC coding.
  • the error correction coding method is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • each of the N service streams The i-th service unit includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes at least one service bit group in the i-th service unit of each of the N service streams
  • the redundant bits obtained by performing forward error correction FEC encoding on the k-th service bit group in, the number of bits in each k-th service bit group is less than or equal to half of the number of redundant bits, and k is a positive integer .
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • FIG. 17 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1700 includes a processor 1710 and a communication interface 1720.
  • the communication interface 1720 is configured to receive M recovery streams and N service streams sent by the first communication device.
  • the j-th service stream among the N service streams includes at least one service unit; the M recovery streams include at least one recovery stream.
  • the i-th restoration unit in the at least one restoration unit is obtained according to the i-th service unit in each of the N service flows, and M, N, i, and j are positive integers;
  • the processor 1710 is configured to determine the N service flows.
  • the j-th service flow includes at least one detection identifier, and the i-th detection identifier in the at least one detection identifier is used to detect the correctness of the i-th service code block in the j-th service flow.
  • the processor 1710 is configured to determine, according to the i-th detection identifier, that the i-th service unit in the j-th service flow is correct;
  • the communication interface 1720 is also used to send the i-th service unit.
  • the processor 1710 is configured to restore the i-th service unit of each service flow in at least one of the N service flows according to the i-th restoration unit.
  • each of the M restoration flows includes an alignment identifier corresponding to the restoration flow
  • each of the N service flows includes an alignment identifier corresponding to the service flow
  • the alignment indicator is used to indicate the correspondence between the i-th restoration unit and the i-th service unit in each of the N service streams.
  • the i-th service unit includes at least one alignment identifier, where each alignment identifier is located at the end of a service packet or a service frame, and is used to indicate the end of the service packet or the service frame.
  • the i-th business unit includes an alignment identifier, and the alignment identifier is located at the end of the i-th business unit and is used to indicate the end of the i-th business unit.
  • the i-th restoration unit in the at least one restoration unit is obtained by performing verification or error correction coding on the i-th service unit in each of the N service flows.
  • the check method is bit interleaving parity check BIP.
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit
  • the i-th service unit of each service flow in the N service streams includes at least one service bit
  • the at least one restoration bit The kth recovery bit in the N service streams is the result of performing bit interleaving parity check BIP on the kth service bit of at least one service bit in the i-th service unit of each service stream, and k is a positive integer.
  • the error correction coding method is forward error correction FEC coding.
  • the error correction coding method is Reed-Solomon RS coding
  • the i-th restoration unit in the at least one restoration unit includes at least one restoration bit group
  • each of the N service streams The i-th service unit includes at least one service bit group
  • the k-th restoration bit group in the at least one bit group includes at least one service bit group in the i-th service unit of each of the N service streams
  • the redundant bits obtained by performing forward error correction FEC encoding on the k-th service bit group in, the number of bits in each k-th service bit group is less than or equal to half of the number of redundant bits, and k is a positive integer .
  • the number of bits of the i-th restoration unit is greater than or equal to the number of bits of the i-th service unit in the j-th service stream.
  • the embodiment of the present application also provides a communication system including a first communication device and a second communication device.
  • An embodiment of the present application further provides a computer program storage medium, which is characterized in that the computer program storage medium has program instructions, and when the program instructions are executed, the foregoing method is executed.
  • An embodiment of the present application further provides a chip system, characterized in that the chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the method in the foregoing method is executed.
  • An embodiment of the present application also provides a communication system, which includes one or more of the aforementioned communication devices.
  • An embodiment of the present application further provides a computer program storage medium, which is characterized in that the computer program storage medium has program instructions, and when the program instructions are executed, the foregoing method is executed.
  • An embodiment of the present application further provides a chip system, characterized in that the chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the foregoing method is executed.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Abstract

本申请提供了一种通信方法，包括：第一通信设备生成M个恢复流和N个业务流，M、N为正整数；所述第一通信设备向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。通过由N个业务流确定的M个恢复流，对传输的N个业务流中的至少一个进行保护。能够在至少一个业务流未正确接收的情况下，对业务流进行恢复，避免业务数据丢失，提高用户体验。

Description

一种通信方法和通信设备
本申请要求于2019年7月29日提交中国专利局、申请号为201910689815.8、申请名称为“一种通信方法和通信设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，具体涉及一种通信方法和通信设备。
背景技术
第一通信设备与第二通信设备之间有至少一条业务流传输。由于路径故障、外界干扰等原因，可能导致传输错误。
为了保证业务流的传输，可以在第一通信设备与第二通信设备之间增加保护路径。当业务流传输出现故障时，通过保护路径进行业务流的传输。第一通信设备向第二通信设备发送至少一个业务流。第二通信设备确定业务流传输出现故障并向第一通信设备通告。第一通信设备将至少一个业务流中出现故障的部分业务流通过保障路径向第二通信设备发送。第二通信设备进行故障检测和通告需要一定时间，可能导致业务数据的丢失。
为了避免业务数据的丢失，可以将业务流进行复制，第一通信设备可以通过不同路径向第二通信设备发送多份相同的业务流。业务流的复制占用了较多的传输资源，网络利用率低。
发明内容
本申请提供一种通信方法和通信装置，能够对通信设备之间传输的至少一条业务流进行保护，避免业务数据丢失，提高用户体验。
第一方面，提供一种通信方法，包括：第一通信设备生成M个恢复流和N个业务流，M、N为正整数；所述第一通信设备向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
通过由N个业务流确定的M个恢复流，对传输的N个业务流中的至少一个进行保护。能够在至少一个业务流未正确接收的情况下，对业务流进行恢复，避免业务数据丢失，提高用户体验。
结合第一方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
通过检测标识，可以确定存在误码的业务单元，从而确定待恢复的业务流。另外，对 于不存在误码的业务流，第二通信设备可以直接发送，无需等待其他业务流中的业务单元的接收和验证，提高传输效率。
结合第一方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
通过对齐标识，第二通信设备可以确定恢复单元与业务单元之间的对应关系，保证恢复的业务单元的准确性。
结合第一方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
通过一个业务包或一个业务帧尾部的对齐标识，第二通信设备在恢复业务单元时，可以确定业务包或业务帧的结束的位置，准确恢复业务包或业务帧。
结合第一方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
通过将校验或纠错编码应用于网络保护，实现对业务流的恢复。
结合第一方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第一方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
通过BIP的方式，BIP校验结果中的一个校验比特，能够实现对一个业务单元中的一个比特进行恢复，恢复流需要传输的数据量较小，网络利用率高。
结合第一方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
通过FEC编解码方式，不依赖于每个业务单元的检测标识，能够对业务单元进行恢复。
结合第一方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
通过RS编解码方式，不依赖于每个业务单元的检测标识，能够对业务单元进行恢复。编码形成的冗余比特能够对业务单元中最多为冗余比特的比特数量一半的比特进行恢复，恢复流需要传输的数据量较小，网络利用率高。
结合第一方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第二方面，提供一种通信方法，包括：第二通信设备接收第一通信设备发送的M个 恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；所述第二通信设备确定所述N个业务流。
通过由N个业务流确定的M个恢复流，对传输的N个业务流中的至少一个进行保护。能够在至少一个业务流未正确接收的情况下，对业务流进行恢复，避免业务数据丢失，提高用户体验。
结合第二方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
通过检测标识，可以确定存在误码的业务单元，从而确定待恢复的业务流。
结合第二方面，在一些可能的实现方式中，所述方法还包括：所述第二通信设备根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；所述第二通信设备发送所述第i个业务单元。
对于不存在误码的业务流，第二通信设备可以直接发送，无需等待其他业务流中的业务单元的接收和验证，提高传输效率。
结合第二方面，在一些可能的实现方式中，所述第二通信设备确定所述N个业务流，包括：所述第二通信设备根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
根据恢复流中的恢复单元，恢复至少一个业务流中与该恢复流对应的业务单元，从而实现恢复流对该至少一个业务流的保护。
结合第二方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
通过对齐标识，第二通信设备可以确定恢复单元与业务单元之间的对应关系，保证恢复的业务单元的准确性。
结合第二方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
通过一个业务包或一个业务帧尾部的对齐标识，第二通信设备在恢复业务单元时，可以确定业务包或业务帧的结束的位置，准确恢复业务包或业务帧。
结合第二方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
通过将校验或纠错编码应用于网络保护，实现对业务流的恢复。
结合第二方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第二方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i 业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
通过BIP的方式，BIP校验结果中的一个校验比特，能够实现对一个业务单元中的一个比特进行恢复，恢复流需要传输的数据量较小，网络利用率高。
结合第二方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
通过FEC编解码方式，不依赖于每个业务单元的检测标识，能够对业务单元进行恢复。
结合第二方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
通过RS编解码方式，不依赖于每个业务单元的检测标识，能够对业务单元进行恢复。编码形成的冗余比特能够对业务单元中最多为冗余比特的比特数量一半的比特进行恢复，恢复流需要传输的数据量较小，网络利用率高。
结合第二方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第三方面，提供的一种通信设备。通信设备包括生成模块，发送模块。生成模块用于生成M个恢复流和N个业务流，M、N为正整数；发送模块用于向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
结合第三方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
结合第三方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
结合第三方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
结合第三方面，在一些可能的实现方式中，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
结合第三方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
结合第三方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第三方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
结合第三方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
结合第三方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
结合第三方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第四方面，提供一种通信设备的示意性结构图。通信设备包括收发模块，确定模块。
收发模块用于接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；确定模块于确定所述N个业务流。
结合第四方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
结合第四方面，在一些可能的实现方式中，确定模块用于根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；收发模块还用于，发送所述第i个业务单元。
结合第四方面，在一些可能的实现方式中，确定模块包括恢复子模块，恢复子模块用于根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
结合第四方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
结合第四方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
结合第四方面，在一些可能的实现方式中，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
结合第四方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
结合第四方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第四方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
结合第四方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
结合第四方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
结合第四方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第五方面，提供的一种通信设备。通信设备包括处理器和通信接口。处理器用于生成M个恢复流和N个业务流，M、N为正整数；通信接口用于向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
结合第五方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
结合第五方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
结合第五方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
结合第五方面，在一些可能的实现方式中，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
结合第五方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
结合第五方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第五方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
结合第五方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
结合第五方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
结合第五方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第六方面，提供的一种通信设备，包括处理器和通信接口。通信接口用于接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；处理器用于确定所述N个业务流。
结合第六方面，在一些可能的实现方式中，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
结合第六方面，在一些可能的实现方式中，处理器用于根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；通信接口还用于，发送所述第i个业务单元。
结合第六方面，在一些可能的实现方式中，处理器用于根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
结合第六方面，在一些可能的实现方式中，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
结合第六方面，在一些可能的实现方式中，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
结合第六方面，在一些可能的实现方式中，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
结合第六方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
结合第六方面，在一些可能的实现方式中，所述校验的方式为比特交织奇偶校验BIP。
结合第六方面，在一些可能的实现方式中，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
结合第六方面，在一些可能的实现方式中，所述纠错编码的方式为前向纠错FEC编码。
结合第六方面，在一些可能的实现方式中，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
结合第六方面，在一些可能的实现方式中，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
第七方面，本申请实施例提供一种通信系统，包括上文中的第一通信设备和第二通信设备。
第八方面，提供一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被执行时，使得上文中的方法被执行。
第九方面，提供一种芯片，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得上文中的方法被执行。
附图说明
图1是一种通信方法的示意图。
图2是另一种通信方法的示意图。
图3是本申请实施例提供的一种通信方法的示意性流程图。
图4是一种以太网数据传输方法的示意性流程图。
图5是本申请实施例提供的一种通信方法的示意图。
图6是IEEE802.3规范的64B/66B码块的类型的示意图。
图7是本申请实施例提供的一种控制码块的示意图。
图8是本申请实施例提供的一种通信方法的示意图。
图9是本申请实施例提供的另一种通信方法的示意图。
图10是本申请实施例提供的又一种通信方法的示意图。
图11是本申请实施例提供的又一种通信方法的示意图。
图12是一种RS码字的示意图。
图13是本申请实施例提供的又一种通信方法的示意图。
图14是本申请实施例提供的另一种通信设备的示意性结构图。
图15是本申请实施例提供的又一种通信设备的示意性结构图。
图16是本申请实施例提供的又一种通信设备的示意性结构图。
图17是本申请实施例提供的又一种通信设备的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是一种通信方法的示意图。根据国际电信联盟-电信标准部(international  telecommunication union telecommunication standardization sector，ITU-T)G.808.1规范了一种保护技术，通过一路保护路径，保护N路工作业务。
第一通信设备与第二通信设备可以通过多条工作路径发送不同的业务信息。例如，路径1、路径2、路径3均为工作路径，分别用于传输设备1向设备4发送的业务数据、设备2向设备5发送的业务数据、设备3向设备6发送的业务数据。第一通信设备与第二通信设备均为网络设备。设备1-设备6可以是用户设备，也可以是网络设备。
数据传输的路径可能出现故障。为了保证业务的传输，可以增加路径4，将路径4作保护路径。当任何一路工作路径故障时，故障工作路径上传输的业务切换到保护路径上进行传送。
通过该方法，发送端设备将故障工作路径的业务通过保护通道发送。接收端设备切换到通过保护通道接收业务。在N条工作路径中可能存在一条路径发生故障的情况，通过1路保护路径，保护N路工作业务的传输。
在工作路径正常工作的情况下，保护路径不进行信息传输，资源消耗较小，网络利用率低。通过该方法，需要实时监测各路径告警状态，以及时发现故障。可以通过自动保护倒换(automatic protection switching，APS)协议，协商第一通信设备与第二通信设备业务传输路径的切换。第一通信设备确定工作路径故障需要一定时间。在第一通信设备确定工作路径故障时，部分业务数据已经通过故障的路径发送，因此存在业务数据的丢失。
图2是一种通信方法的示意图。通过该方法，可以避免业务数据的丢失。
电气和电子工程师协会(institute of electrical and electronics engineers，IEEE)802.3CB发布的以太网相关标准，通过包复制方式，避免路径故障引发的丢帧问题。
通信设备101接收业务帧，将该业务帧进行复制，并在业务帧中添加标识R-TAG。业务帧即用于承载业务信息的帧结构。业务信息也可以称为业务数据。相同的R-TAG用于标识包括相同业务数据的业务帧。通信设备101可以通过不同的路径向通信设备104发送复制后的业务帧。例如，业务帧1经过通信设备101、通信设备102发送至通信设备104；业务帧2经过通信设备101、通信设备103发送至通信设备104。业务帧1和业务帧2具有相同的标签(R-TAG)。
通信设备104接收R-TAG相同的业务帧1和业务帧2，仅将其中的一个向下游发送。对于每一个业务帧，通过复制并在多路径传送，抵御路径故障的风险，提高业务传输的可靠性。
对业务数据进行复制，将复制后的业务数据通过不同的路径传输，占用保护资源较大，网络利用率低。
业务帧传输路径上的中间节点也可能对数据帧进行复制并通过不同的路径发送。例如，通信设备102对业务帧1再进行复制以生成业务帧3，并通信设备103发送，业务帧3经通信设备103转发后，发送至通信设备104。业务帧3具有与业务帧1相同的标签R-TAG。
中间节点对业务帧的复制和传输，进一步降低了网络利用率。
图3是本申请实施例提供的一种通信方法的示意性流程图。
在步骤S301，第一通信设备生成M个恢复流和N个业务流，M、N为正整数。
所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少 一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
在步骤S301之前，第一通信设备可以接收一个或多个业务流。第一通信设备可以根据接收的一个或多个业务流生成该N个业务流。
第一通信设备可以根据生成的该N个业务流生成M个恢复流。
第一通信设备可以对该N个业务流中的每个业务流的第i业务单元进行编码或校验，从而生成该M个恢复流中的第i恢复单元。所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
校验的方式可以是和校验、循环冗余校验(cyclic redundancy check，CRC)、比特交织奇偶校验(bit interleaved parity，BIP)的奇校验或偶校验。
以BIP校验为例，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
BIP校验方式能够通过一个校验比特对每个业务流中的一个比特进行校验，恢复流中传输的数据量较小，对系统的影响较小。
纠错编码的方式可以是前向纠错(forwarding error correction，FEC)编码，例如，里德-所罗门(Reed-Solomon，RS)编码，玻色-乔赫里-霍克文黑姆(Bose-Chaudhuri-Hocquenghem，BCH)编码等。以RS编码为例进行说明。在FEC编码的基础上，也可以引入重传机制。纠错编码的方式也可以是混合纠错模式。
以RS编码为例，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
对于相同数量的冗余比特，通过RS编解码方式能够对较多的比特数进行纠错，从而使得恢复流中传输的数据量较小，对系统的影响较小。
第i恢复单元可以承载在所述M个恢复流中。也就是说，该M个恢复流中的每个恢复流包括可以包括第i恢复单元的一部分，这些部分共同构成了第i恢复单元。
在步骤S302，第一通信设备向第二通信设备发送所述M个恢复流和所述N个业务流。
该M个恢复流可以通过M个恢复路径发送，该N个业务流可以通过N个业务路径发送。该M个恢复流与该M个恢复路径一一对应。该N个业务流与N个业务路径一一对应。
路径可以是物理链路，也可以是逻辑连接，本申请实施例对此不作限定。例如，在一些实施例中，通过一个物理端口传输的业务流可以认为是通过一条路径传输的一个业务流，即一个业务流对应一个物理端口。一条路径仅通过一个物理端口传输业务流，一个物理端口所在链路仅承载一个路径，传输业务流。在另一些实施例中，一个物理端口传输的业务流是通过多条路径传输的，一个物理端口所在链路承载多条路径，传输不同的业务流，不同的业务流携带不同的标签。携带同一标签的业务流可以是通过一条路径传输的一个业务流。
也就是说，该M个恢复流和该N个业务流可以通过一个或多个物理链路发送。物理链路也可以称为链路或通道。例如，该M个恢复流可以通过M个恢复链路发送，该N个业务流可以通过N个业务链路发送。或者，该M个恢复流、该N个业务流可以通过一条链路的不同频率或时间发送。本申请实施例对此不作限定。
在步骤S303，第二通信设备确定所述N个业务流。
第二通信设备可以在接收所述M个恢复流和所述N个业务流后，确定所述N个业务流。第二通信设备确定所述N个业务流，即确定N个业务流与第一通信设备发送的业务流相同，也就是说，确定第一通信设备发送的N个业务流。
第二通信设备可以确定接收的N个业务流正确，确定接收的N个业务流为第一通信设备发送的N个业务流。
第二通信设备可以根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。第二通信设备可以确定恢复后的N个业务流为第一通信设备发送的该N个业务流。
可选地，所述第j业务流可以包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
第一通信设备可以对每个业务流中的第i业务单元进行校验，分别生成每个第i业务单元的第i检测标识。
在同一业务流中，第i检测标识可以在第i业务单元之前或之后发送。在第i检测标识与其对应的第i业务单元之间可以包括或不包括其他字段或比特。
第二通信设备在接收第i检测标识以及对应的第i业务单元后，可以立即对第i业务单元进行校验。
如果第二通信设备根据第j业务流中的第i检测标识，确定第j业务流中的第i个业务单元正确，第二通信设备可以发送所述第i个业务单元。通过检测标识，第二通信设备可以在确定业务单元正确后，立即发送该业务单元。
通过检测标识，第二通信设备可确定需要进行恢复的业务单元。
另外，在某一业务流中的第i业务单元正确的情况下，第二通信设备可以将该业务单元立即发送，不需要等待第二通信设备确定所有业务流中的第i业务单元之后统一发送。通过该方式，可以降低对于系统的影响，减小该业务单元在通信设备在设备之间传输的时间，提高数据传输的速率。提高用户体验。
通过第j业务流中的检测标识，第二通信设备可以对第j业务流中每一个业务单元的正确性进行检测。每一个业务单元都正确，第二通信设备可以确定接收的N个业务流，为第一通信设备发送的N个业务流。
第二通信设备保存确定第j业务流中的第i业务单元正确，第二通信设备可以保存所述第i业务单元。如果N个业务流中的第i业务单元均正确，可以删除保存的所有第i业务单元。
第二通信设备可以根据接收的恢复单元，对其他业务流中的业务单元的进行恢复。
第二通信设备可以根据保存的业务单元，以及接收的与其对应的恢复单元，对其他业务流中的业务单元的进行恢复。如果N个业务流中至少一个业务流中的第i业务单元错误，第二通信设备可以根据第i恢复单元，恢复该至少一个业务流中每一个业务流的第i业务 单元。第二通信设备也可以根据第i恢复单元以及其他业务流中的第i业务单元，恢复该至少一个业务流中每一个业务流的第i业务单元。
可选地，所述M个恢复流中的每个恢复流可以包括第i检测标识。第一通信设备可以对通过M个恢复流中第j恢复流发送的第i恢复单元的部分进行校验，以生成第i检测标识。第二通信设备接收第j恢复流中的第i检测标识，根据第i检测标识对第j恢复流中的第i恢复单元的部分进行校验，从而确定该部分的正确性。
可选地，所述M个恢复流中的部分恢复流可以包括第i检测标识。第一通信设备可以对第i恢复单元进行校验，以生成第i检测标识。第一通信设备可以通过M个恢复流中的一个或多个流向第二通信设备发送第i检测标识。第二通信设备可以根据第i检测标识可以确定第i恢复单元的正确性。
第二通信设备可以在确定第i恢复单元正确的情况下，根据第i恢复单元，对该N个业务流中的至少一个业务流的第i业务单元进行恢复。
可以通过代码和校验、BIP或CRC等方式，对业务单元、恢复单元进行校验，以获取检测标识。
第二通信设备可以将接收的业务流或恢复的业务流确定为第一通信设备发送的业务流，进行后续的处理。第二通信设备在确定该N个业务流之后，可以将该N个业务流发送至其他通信设备，或者第二通信设备可以对该N个业务流进行处理，将处理结果发送至其他通信设备。
第i检测标识可以包括多个部分，分别用于检测第i业务单元的不同部分。第二通信设备在确定第i业务单元某个部分正确的情况下，可以发送该部分，也可以在确认其他部分之后，发送第i业务单元。
第二通信设备在确定第i业务单元某个部分错误的情况下，可以根据第i恢复单元，对第i业务单元进行恢复。或者，第二通信设备也可以仅对第i业务单元确认错误的部分进行恢复。
可选地，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
N个业务流、M个恢复流中的任一个流，可以包括一个或多个对齐标识(alignment marker，AM)。该多个对齐标识可以相同或不同。例如，该标识可以是标识号等。例如，在以太网物理层，进行路径对齐，可以在不同的路径中插入该路径对应的AM。通过在路径开始进行工作时插入AM，或者周期性插入AM，或者插入对应于每个业务单元或恢复单元的AM，可以确定第i恢复单元对应的每个业务流中的第i业务单元。
对于该N个业务流、该M个恢复流，其中每个业务流中的第i业务单元、第i恢复单元可以对应相同或不同的对齐标识。
例如，对齐标识可以是标识号。在一些情况下，对于该N个业务流、该M个恢复流，其中每个业务流中的第i业务单元、第i恢复单元可以对应相同的对齐标识。
一个业务单元可以包括至少一个比特(bit)，至少一个码块，或者至少一个业务帧、业务包或业务块。对于一个业务单元包括至少一个业务帧、业务包或业务块的情况，由于每个业务单元的长度可能不相等，也就是说，每个业务单元包括的比特数量不相等。为了 确定恢复单元，第一通信设备可以在较短的业务单元之后填充固定的序列，例如补充“0”或“1”，或者根据生成恢复单元的具体方式，在至少一个业务单元之后补充固定的序列，从而进行校验或编码，确定恢复单元。也就是说，第i恢复单元还可以至少一个恢复比特组，其中的第k恢复比特组是根据N个业务流中的至少一个业务流中的每个第i业务单元中的第k业务比特组，以及该N个业务流中其他业务流中的填充比特组确定的。第k恢复比特组包括至少一个比特，第k业务比特组包括至少一个比特。第k业务比特组包括至少一个填充比特和/或业务单元中的至少一个比特。
在对某一个业务流中的业务进行恢复时，由于每个业务单元的长度可能不相等。第一通信设备在较短的业务单元结束后，可以按照该业务单元的比特值为“0”、“1”或其他预设序列的方式进行校验以生成恢复单元。业务单元的长度不相等的情况下，第二设备在恢复业务单元时，需要确定业务单元结束的位置。为了确定业务帧结束的位置，可以在在业务单元的结束处，即业务单元的尾部添加特定的标识。例如，可以添加特定的字符串，或者，将对齐标识添加在业务单元的尾部，用于指示业务单元结束。通过对齐标识指示业务单元结束，可以减少添加的字符数量，减小对数据传输影响，减小系统负担。
业务单元可以包括业务帧、业务包或业务块。业务帧、业务包或业务块的长度不相同。以业务帧为例说明。每个业务单元可以包括不同数量的业务帧。
所述N个业务流中的每个业务流的第i业务单元可以包括一个对齐标识，用于指示业务单元结束。
或者，所述N个业务流中的每个业务流的第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
如果出现以下情况中的一种或多种，可以对第j业务流中的第i业务单元进行恢复：第二通信设备未接收到第j业务流中的第i检测标识，第二通信设备未接收到第j业务流中的第i业务单元的AM，第二通信设备根据第j业务流中的第i检测标识进行的检测出现错误等。
可选地，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。第i恢复单元的比特数量即第i恢复单元的长度。第i业务单元的比特数量即第i业务单元的长度。
第i恢复单元可以仅包括至少一个恢复比特组，或至少一个恢复比特。第i恢复单元的比特数量可以是第i业务单元的比特数量的正整数倍。例如，采用BIP方式确定的第i恢复单元，第i恢复单元的比特数量可以与第i业务单元的比特数量相等；采用RS编码方式确定的第i恢复单元，第i恢复单元的比特数量可以是第i业务单元的比特数量相等2倍。
第i恢复单元还可以包括对应于形成帧、码块、包、块等格式的字段。例如，第i恢复单元可以包括以太网64B/66B码块的同步头，帧格式中的封装头部等。
通过步骤S301-S303，可以对至少一条业务流进行保护，将检错、纠错的方法扩展应用在网络保护中，能够在全部或部分业务流未正确接收的情况下，对业务流进行恢复，避免业务数据丢失，可以减小业务数据保护对系统的影响，提高网络利用率。通过上述方式，无需对路径故障进行检测。
上述方法可以应用在公用网络和专用网络中，例如可以应用在以太网、光传输网(optical transport network，OTN)、同步数字体系(synchronous digital hierarchy，SDH)、存储等网络中。以太帧、码块、IP包、OTN帧、SDH帧、通用公共无线接口(common public radio interface，CPRI)帧、FC(fibre channel)帧等以比特流方式传输的业务，均可以通过本申请实施例提供的方法进行恢复，不会造成数据丢失，用户无感知，提高用户体验。在上述网络中，第一通信设备和第二通信设备可以是运营商边缘设备(provider edge device，PE)或运营商(provider，P)设备。
本申请实施例提供的技术方案例如可以应用于支持以太网接口的网络设备。网络设备可以是交换机、路由器等设备。第一通信设备例如可以是入口PE设备，也可以称为入口节点(ingress unit)，第二通信设备例如可以是出口PE设备，也可以称为出口节点(egress unit)。
应当理解，上述方式可以应用在第一通信设备与第二通信设备经过或不经过中间节点对业务流、恢复流进行传输的情况。也就是说，本申请实施例可以应用于点到点链路，或者，也可以应用于端到端网络。
转发也可以称为交叉或交换。在以太网中，中间节点可以用于码块级别的流的交叉。中间节点也可以实现对帧的转发，例如，在以太网中，中间节点可以用于实现以太网交换机的功能，实施二层(layer 2，L2)层以太网交换功能。中间节点可以用于比特级别的流的交叉，中间节点可以是实现SDH或OTN交叉的设备。
业务流、恢复流经过中间节点转发的情况下，中间节点可以仅仅进行业务流和恢复流的转发。或者，中间节点也可以采用本申请实施例提供的方式，对业务流进行恢复。中间节点对业务流的恢复，可以提高业务数据传输的准确性。
以太网接口对数据传输的流程可以参考图4。以太网接口可以用于执行媒体访问控制(medium access control，MAC)层、协调子层(reconciliation sublayer，RS)、物理(physical，PHY)层的全部或部分功能。以太网接口进行的数据传输的方法可以通过芯片或现场可编程门阵列(field－programmable gate array，FPGA)等实现。
图4是一种以太网数据传输的方法的示意性流程图，主要描述物理层的相关处理过程。
对于第一通信设备，一个以太网包进入媒体访问控制(medium access control，MAC)层/协调子层(reconciliation sublayer，RS)后，对包进行校验并按照某种介质独立接口(medium independent interface，MII)要求实施编码，通过xMII发送至物理编码子层(physical coding sublayer，PCS)。PCS子层接收各种MII(some kind of MII，xMII)接口发送的xMII信息，进行比特码块编码和速率匹配。xMII一般应用于以太网设备的MAC层和物理层之间。在一些实施例中，xMII接口存在于集成电路内。PCS子层按照64比特(bit，B)/66B规则编码，形成一条串行流。之后，PCS子层将64B/66B码块按照256B/257B编码规则进一步编码为257B的码块流。257B码块经过扰码处理后，插入对齐标识(alignment marker，AM)组。AM组的也是若干个257B。插入AM组之后，257B码块流按照10比特的符号分发到2路FEC编码，加入校验比特，FEC编码后再按照每个符号10比特分发至8条PCSL。应当理解，2路FEC采用的FEC编解码方式相同，通过2路FEC可以提高编解码速率和抗突发误码能力。然后通过分布和交织，按照符号(一个符号 为10比特)分发至8条物理编码子层通道(physical coding sublayer lane，PCSL)。插入的AM会分布在每一条PCSL上。PCSL上的符号可以通过物理媒介接入子层(physical medium attachment，PMA)和物理媒介相关子层(physical medium dependent，PMD)发送至第二通信设备。
第二通信设备通过PMD和PMA接收第一通信设备发送的符号，利用每个PCSL上的AM进行通道锁定，并对各个PCS通道重排序得到符号流，然后对符号流进行RS解码之后，形成串行码块流并移除串行码块流中的AM组，然后对移除AM组之后的串行码块流进行解扰和反向转码之后得到64B/66B的串行码块流，对64B/66B的串行码块流进行解码和速率匹配发送到RS子层和MAC层，通过MAC层将数据传送到数据链路层。
比特是二进制数字中的位，信息量的度量单位，为信息量的最小单位。257B的码块流、66B的码块流、以及分发至逻辑通道的符号流，均可以理解为比特流。
需要说明的是，为了方便理解，图4只是简述了以太网接口的处理流程，具体在应用中可以增加其他的处理过程，或者减少上述部分处理过程。上述方法适用于200G和400G以太网接口。对于40G和100G的以太网接口，可以不包括FEC编码、FEC解码和257B转码的过程。
FEC编解码，即采用编解码技术纠正传输过程中的比特错误。FEC编码例如可以是里德-所罗门(Reed-Solomon，RS)编码等。进行RS编码，目的是为了进一步提高比特流在传输过程中的正确率，RS解码时可以根据插入的校验比特纠正发生错误的比特。对于RS编码，可以认为在不改变原码块流的情况下，每间隔一定比特插入一些校验比特。RS解码时，根据RS编码插入的校验比特计算并恢复传送过程中出错的比特。校验完成之后，这些校验比特被移除。
图5是本申请实施例提供的一种通信方法的示意图。
以网元A和网元Z之间部署100Gbps以太网链路，网元A和网元Z可以通过至少一条路径传输业务流。例如，以1#-3#条路径用于传输网元A向网元Z发送的业务流，网元A和网元Z之间采用比特交织奇偶校验(bit interleaved parity，BIP)的奇校验为例，对本申请实施例的方案进行说明。
A网元接收S1至S3三条用户流并编码形成64B/66B码块流。从S1接口收到的数据形成的64B/66B码块流通过1#路径发送至Z网元。从S2接口收到的数据形成的64B/66B码块流通过2#路径发送至Z网元。从S3接口收到的数据形成的64B/66B码块流通过3#路径发送至Z网元。A网元可以是第一通信设备，Z网元可以是第二通信设备。
对于1#-3#路径中每个路径传送的64B/66B码块流，一个业务单元可以包括用于业务传输的连续的64个64B/66B码块，或者64的整数倍的连续的64B/66B码块。用于业务传输的64B/66B码块也可以称为64B/66B业务码块。以一个业务单元包括64个64B/66B业务码块为例进行说明。
A网元可以对发往1#路径的业务单元进行CRC校验，生成该业务单元的CRC信息，并通过1#路径发送该CRC信息。该CRC信息可以在该业务单元之后发送。A网元可以对发往2#路径的业务单元进行CRC校验，生成该业务单元的CRC信息，并通过2#路径发送该CRC信息。该CRC信息可以在该业务单元之后发送。A网元可以对发往3#路径的业务单元进行CRC校验，生成该业务单元的CRC信息，并通过3#路径发送该CRC信息。 该CRC信息可以在该业务单元之后发送。也就是说，A网元通过业务单元所在的路径发送对应于该业务单元的CRC信息。参见图7，可以通过控制码块承载CRC信息。承载CRC信息的控制码块可以称为检测码块或检测标识。检测标识也可以是CRC信息。对于1-3#路径，检测码块可以位于其对应的业务单元之后，也就是说，A网元可以在发送业务单元之后发送该业务单元对应的检测码块。对于4#路径，检测码块可以其对应的在恢复单元之后发送。
A网元对1#-3#路径传输的比特流中对应的业务单元中相同位置的一个比特进行BIP校验，以生成通过4#路径传输的BIP单元中的一个比特。BIP单元也可以称为恢复单元。
参见图8，对BIP单元进行说明。
对通过1#-3#路径传输的业务单元中每个64B/66B业务码块中的每个比特进行BIP校验，从而形成64×66B的校验信息。业务单元中64×66B中的每个比特即一个业务比特，64×66B的校验信息中的每个比特即一个恢复比特。
参见图6中64B/66B码块的格式，对于该64×66B的校验信息，每64比特作为一个码块中的数据，再增加一个2比特同步头01(即码块类型为数据码块)，形成66个64B/66B码块。也就是说，一个恢复单元包括该66个64B/66B码块。该恢复单元也可以称为BIP单元。
对BIP单元进行CRC校验，以生成该BIP单元的CRC信息。通过4#路径发送该CRC信息。参见图7，该CRC信息可以承载在控制码块中。该控制码块的类型可以是0x4B、0x2D、0x55、0x00等。该CRC信息可以承载在一个或多个数据字节，也可以承载在一个或多个控制字节。
应当理解，1#至4#三条路径可以是以太网物理层的路径。参见IEEE 802.3，可以通过在64B/66B码块流中添加对齐标记(alignment marker，AM)的方式，对1#-4#路径进行对齐。也就是说，A网元可以周期性在1#-4#路径传输的码块流中周期性插入对应于该路径的AM。每条路径中的AM可以相同或不同。对齐标记也可以称为对齐标识。
可选地，由于4#路径传输的比特流中的数据量较多，可以适当提高4#路径的传输速率，以使得4#路径的传输的信号能够与1#-3#路径同步。或者，也可以通过两条或多条路径传输该恢复单元。
例如，在1#-4#路径传输的码块不包括检测码块的情况下，1#-3#路径的传输速率相同，可以将4#路径的传输速率提升为1#-3#路径的传输速率的66/64。考虑承载CRC信息的控制码块，可以将4#路径的传输速率提升为1#-3#路径的传输速率的67/65。
或者，也可以通过两条或多条路径传输该恢复单元。可以在该两条或多条路径中插入填充特定信息的控制码块，以使得Z网元可以在相同的时间接收恢复单元以及该恢复单元对应的业务单元。也可以降低该两条或多条路径的传输速率，以使得Z网元可以在相同的时间接收恢复单元以及该恢复单元对应的业务单元。应当理解，相同的时间，也包括近似相同的时间。
Z网元可以根据接收的数据，恢复1#-3#路径中一条路径上传输的数据。
Z网元可以每次从1#-3#路径传输的比特流中分别取一个业务单元和一个检测码块。业务单元与检测码块对应。该检测码块是对该业务单元进行校验得到的。一个业务单元为64个64B/66B码块。
Z网元在4#路径传输的码块流中取一个恢复单元和与其对应的检测码块。恢复单元对应于该1-3#路径中取的业务单元。该恢复单元为66个64B/66B码块。
Z网元可以根据4#路径接收的数据恢复1#-3#路径中的任一路的数据。以3#路径为例进行说明。
从某个时刻，Z网元从3#路径未接收到的检测码块，未接收到检测码块可以是未接收到同步头为10的码块，或同步头为10的码块的类型不是0x4B类型的码块，或码块中的O0字段不是0x06。可以根据4#路径接收的数据以及1#和2#路径传输的数据，对3#路径传输上的数据进行恢复。
3#预期接收的64个码块的每个bit等于1#，2#和4#路径对应比特的BIP计算结果。比如1#的bit0＝0，2#的bit0＝1，4#携带的对应1#-3#路径的bit0的校验结果bit3＝1(BIP的码块bit0和bit1是同步头，不属于BIP校验比特)，则预期接收的3#路径的bit0＝～(1#的
Figure PCTCN2020102591-appb-000001
的
Figure PCTCN2020102591-appb-000002
的bit3)＝1。如此，可以将3#路径传输的业务单元，即64*66个比特全部恢复。Z网元将恢复后的结果作为A网元发送的业务单元。
另外，检测码块可以用于检测业务码块的正确性。Z网元可以根据检测码块对1#-3#路径中的取的业务单元进行正确性的检测。
对于1#路径，Z网元接收业务单元以及与业务单元对应的检测码块。对业务单元进行CRC计算，将计算结果CRC-24与检测码块中的CRC-24进行比较，如果相同，则认为业务单元正确，没有发生误码。如果业务单元的CRC计算结果与检测码块中的CRC-24一致，即传送过程中没有误码，则保存一份拷贝后立即发送。
对于2#路径，Z网元的CRC-24计算结果与检测码块中的CRC-24一致，即传送过程中没有误码，则保存一份拷贝后立即发送。
对于3#路径，Z网元的CRC-24计算结果与检测码块中的CRC-24一致，即传送过程中没有误码，则保存一份拷贝后立即发送。
如果1#-3#路径均没有误码，Z网元可以将拷贝的业务单元和恢复单元删除。
4#路径收到包括66个64B/66B码块的恢复单元和一个检测码块，每个数据码块携带BIP监视比特，检测码块携带CRC-24码块。由于1#～3#没有错误，则通过4#路径收到的BIP结果无需检错和纠错，可以丢弃。
如果1#-3#路径中的任一路径中对业务单元的CRC-24计算结果与检测码块中的CRC-24不一致，即业务单元不正确，存在误码，可以根据其他路径的业务单元以及4#路径与这些业务单元对应的恢复单元对存在误码的业务单元进行纠错。
在对业务单元进行纠错之前，可以通过从4#路径接收的与恢复单元对应的检测码块，对恢复单元的正确性进行检测。如果对恢复单元的CRC-24计算结果与检测码块中的CRC-24一致，即传送过程中没有误码，对存在误码的路径进行纠错。否则，不进行纠错。Z网元将纠错后的结果作为A网元发送的业务单元。
Z网元在确定1#-3#路径的每条路径传输的第i业务单元后，可以删除保存的第i恢复单元。
以在A网元和Z网元之间通过1#-3#路径传递的三路码块流为例，A网元通过插入包括CRC信息的控制码块，将码块流划分为多个业务单元，将业务流发送至Z网元。在A网元与Z网元之间，增加一条路径传输BIP信息。Z网元根据BIP信息，基于BIP检错方 法可以恢复任意一路的业务单元。业务单元的恢复也包括对业务单元的纠错。
检测码块还可以用于1#-4#路径的对齐。也就是说，检测码块可以作为对齐标识。例如，可以通过检测码块承载对应于每条路径的对齐信息，Z网元根据检测码块实现路径的对齐。
本申请实施例提出的方案通过检测插入的控制码块，可以检测线路的故障，无需专门设置APS协议，就可以实现对业务流的恢复。并且，可以对传输的信号进行误码检测和纠错。实施方式简洁，易部署。
通过本申请实施例提供的方案，占用一路资源进行恢复单元的传输，可以对多条路径传输的数据进行保护，网络利用率高，并且不会出现丢包。
图6是IEEE802.3规范的64B/66B码块的类型的示意图。
64B/66B编码将64bit数据或控制信息编码成66bit块传输，66bit块的前两位表示同步头，后64bit可以称为数据净荷。同步头有“01”和“10”两种。数据码块中，同步头为“01”，同步头后的64bit都是数据。控制码块中，同步头为“10”，同步头后的64bit包括数据和/或控制信息。控制码块中，数据负荷中的前8bit，即与同步头相邻的8bit是类型域，可以表示控制码块的类型。数据负载中的后56bit，即类型域之后的56bit是控制信息和/或数据。64B/66B码块中，D表示数据字节，每个数据字节为8bit；C表示控制字节，每个控制字节为7bit；S表示数据包的开始，T表示数据包的结束；O表示ordered set控制码块(例如，类型为0x4B，O的取值不同，使用场景不同)。S只会出现在8字节中的第0和第4字节，T能够出现在任意的字节。包含S的码块可以称为S码块，包含T的码块可以称为T码块。空闲(idle)码块中的C 0～C 7为0，低功耗(LPI)码块中的C 0～C 7为6。数据包例如可以是根据以太帧得到的。
用于承载CRC信息的控制码块，类型可以是0x4B、0x2D、0x55、0x00等。以0x4B码块为例进行说明。
图7是本申请实施例提供的一种控制码块的示意图。该码块用于承载CRC信息。
以类型为0x4B的控制码块进行说明。可以通过控制码块的O0承载的信息指示该码块为承载CRC信息的码块，即检测码块。即O0可以用于标识该码块为检测码块。例如，O0为0x6指示该码块为检测模块。该0x4B控制码块的控制字节可以为0x0，也可以用于承载其他信息。
可选地，检测码块可以用于检测路径故障。当Z网元在预设的时间间隔内未检测到第j业务流中的检测码块，可以认为用于传输第j业务流的第j路径故障。Z网元可以通告A网元，也可以输出路径故障指示信息，指示第j路径故障。
检测码块还可以用于承载CRC信息的码块。例如，通过D1～D3承载CRC信息。D1～D3共24比特，该CRC信息可以包括24个比特，该字段承载的CRC信息也可以称为CRC-24。
图9是本申请实施例提供的一种通信方法的示意图。
对于业务帧，也可以采用本申请实施例提供的通信方法进行业务数据传输。
A网元可以在业务帧的任意位置添加对齐标识，例如在业务帧的尾部添加对齐标识，也就是说，对齐标识可以位于业务帧之后或者业务帧净荷的最后。
A网元对业务帧进行CRC校验并将校验得到的CRC校验信息添加在业务帧的任意位置，例如，添加在业务帧的尾部，对齐标识之前或之后。
或者，A网元可以对业务帧和对齐标识进行CRC校验，并将校验得到的CRC校验信 息添加在业务帧的任意位置。
添加对齐标识、CRC校验信息的位置可以由A网元和Z网元约定，或者由预先配置。
Z网元接收业务帧、对齐标识和CRC校验信息，对业务帧进行CRC校验，或者对业务帧和对齐标识进行CRC校验，并将校验结果与业务帧之后的CRC接收的CRC校验信息进行比较。如果校验结果与CRC校验信息相同，Z网元可以确定该业务帧正确；反之，该业务帧存在误码。之后，Z网元可以将CRC校验信息去除。
Z网元可以根据对齐标识确定该业务帧对应的恢复帧，还可以根据对齐标识确定该业务帧对应的其他业务帧。Z网元可以去除对齐标识，并对去除CRC检验结果和对齐标识的业务帧进行后续处理。
根据IEEE802.3规范，MAC层可以对发送的以太网帧进行CRC校验并将校验结果CRC-32信息附加在以太帧尾部，发送至物理层链路，接收端MAC层对接收到的帧进行CRC校验计算并与对端发送的CRC-32信息比对，以判断以太帧是否正确。如果CRC校验失败，可以采用本申请实施例提供业务数据恢复方案。
在本申请实施例中，检测标识可以是太网帧中的CRC-32信息。对于一个业务单元包括多个以太帧的情况，检测标识包括该多个以太帧的CRC-32信息，检测标识也可以是对业务单元进行CRC校验得到的校验信息。
在业务流需要经过中间节点转发的情况，检测标识也可以通过其他方式添加在以太帧中。例如，在A网元与Z网元之间存在中间节点，1#-4#路径传输的数据经其他网元进行转发的情况，A网元可以根据IEEE802.3规范在以太帧中添加CRC-32信息，A网元也可以在业务流和恢复流中额外添加检测标识，用于Z网元对业务单元和恢复单元的正确性检测。对业务路和恢复流进行转发的中间节点可以仅仅进行业务流和恢复流的转发。或者，中间节点也可以采用本申请实施例提供的方式，对业务流进行恢复。中间节点对业务流的恢复，可以提高业务数据传输的准确性。
应当理解，对于恢复帧，A网元和Z网元可以采用与业务帧类似的处理。
网元A与网元Z之间部署100Gbps以太网链路，S1～S3共三路二层虚拟专用网络(layer 2 virtual private network，L2VPN)业务传输至网元A，并由网元A通过1#-3#路径向网元Z发送，网元A与网元Z之间采用BIP的偶校验，以形成4#路径上传输的恢复信息。
A网元根据1#-3#路径中的每一路径传输的业务帧，形成4#路径的恢复单元。
A网元从S1、S2和S3接收数据并形成通过1#-3#路径中的任一路径传输的业务帧。业务帧通过A网元的MAC层、物理层发送至Z网元。经Z网元的物理层、MAC层的传输，Z网元接收业务帧。
A网元每次取对应于1#-3#路径中的每一个路径的待发送业务帧，即3个业务帧。A网元对每个路径中获取的业务帧中每次取一个比特进行BIP校验，根据BIP的结果，即BIP监视比特组，形成恢复帧。A网元可以对业务帧中的每个比特进行BIP校验，即业务帧的头部和净荷均进行BIP校验。A网元也可以对业务帧中的部分字段进行BIP校验。
参考图10，恢复帧的净荷包括BIP校验结果。校验结果可以包括对业务帧头部全部或部分字段进行校验的结果，或不包括对业务帧头部进行校验的结果。例如，业务帧包括位于业务帧尾部的对齐标识。对发往1#-3#路径的每个业务帧第一个比特bit0进行BIP校验，得到BIP0，作为恢复帧的净荷的第一个比特。对发往1#-3#路径的每个业务帧第一个 比特bit1进行BIP校验，得到BIP1，作为恢复帧的净荷的第二个比特。以此类推。在净荷之前，添加恢复帧的头部，帧的头部也可以称为帧的封装头部。恢复帧的头部可以包括目的MAC地址和源MAC地址，目的MAC地址和源MAC地址可以由网元A指定，或者由网元A和Z约定，或者由网管进行配置。
对于1#-3#路径传输的业务帧长度不相等的情况，A网元在进行BIP校验时，可以在较短的业务帧之后添加预设比特序列，进行校验。例如，在较短的业务帧之后补“0”，进行BIP校验，从而生成恢复帧。例如，发往1#-3#路径用于生成一个恢复帧的业务帧中，最长的业务帧包括bit0-bit n，最短的业务帧包括bit0-bit m，进行BIP检验得到了恢复帧净荷中的BIP0-BIPn，m≤n。应当理解，业务单元中bit0-bit n分别为第0业务比特至第n业务比特，BIP0-BIPm分别为为恢复单元的第0恢复比特至第n恢复比特。其中，第0恢复比特至第m恢复比特是对发往1#-3#路径的业务单元的第k业务比特进行比特交织奇偶校验BIP的结果，k≤m。
一个恢复单元可以包括一个或多个恢复帧中的全部或部分字段。
一个业务单元可以包括一个或多个业务帧的全部或部分字段。每个业务帧可以包括一个CRC-32信息。检测标识可以包括该多个CRC-32信息。A网元在进行BIP校验以生成恢复单元时，可以不对该多个CRC-32信息进行校验。
A网元可以在业务帧内插入一个对齐标识。A网元可以在恢复帧内插入对齐标识。对齐标识可以位于帧的头部或净荷。例如，在帧的净荷尾部，增加字节，用于写入对齐标识。
用于形成同一个恢复帧的1#-3#路径传输的业务帧中的对齐标识，与恢复帧中的对齐标识一一对应。应当理解，业务帧中的标识用于指示对该帧进行恢复的恢复帧和其他业务帧。
例如，对于一个业务单元包括一个业务帧的情况，恢复帧1是根据通过1#路径传输的业务帧1、通过2#路径传输的业务帧2、通过3#路径传输的业务帧3形成的。通过恢复帧1的对齐标识、业务帧1的对齐标识、业务帧2的对齐标识、业务帧3的对齐标识一一对应。恢复帧1的对齐标识、业务帧1的对齐标识、业务帧2的对齐标识、业务帧3的对齐标识可以相同或不同。例如，业务帧、恢复帧中的对齐标识可以是编号，从1开始，最大65535，超过65535则再从1开始进行编号。以恢复帧1、业务帧1-业务帧3的对齐标识相同的情况进行说明。
恢复帧1、业务帧1、业务帧2、业务帧3可以形成一个4×n比特的校验矩阵。恢复帧1、业务帧1、业务帧2、业务帧3分别对应于校验矩阵中的4列，n为业务帧1-3中最长的一个帧的长度。帧的长度也可以理解为帧的比特数量。
或者，A网元可以在一个业务单元中插入一个对齐标识。例如，一个业务单元包括多个业务帧，A网元可以在最后一个业务帧的末尾添加对齐标识。
业务单元可以包括或不包括对齐标识。
A网元还可以在恢复流中添加对应于每个恢复帧的校验信息。该校验信息即为检测标识。A网元可以对恢复帧进行CRC校验，将校验产生的校验信息添加在恢复帧中。一个恢复单元包括一个恢复帧的全部或部分数据。恢复单元可以包括或不包括恢复帧的头部、对齐标识、校验标识。
Z网元每次从1#～3#路径各取一个业务单元，从4#路径取一个恢复单元。一个业务单 元可以包括一个或多个业务帧的全部或部分数据。
对于1#-3#路径中的任一路径，Z网元如果在指定时间窗内收到预期的业务单元，则对该业务单元进行CRC校验，校验结果正确，则将该业务单元保存后立即发送。
Z网元也可以在接收每个业务帧之后，对该业务帧进行校验，如果校验结果正确，则将该业务帧保存后立即发送。如果某个业务帧进行CRC校验的校验结果错误，可以仅对该业务帧进行恢复，减小Z网元的计算量，提高传输效率。
Z网元在4#路径收到恢复单元。此时如果标识相同的业务单元均校验正确或已经发送完成，则丢弃该恢复单元。
从某个时刻，Z网元未从1～3#路径中的某一路径接收到预期的业务帧，如在2#路径在指定时间窗内没有接收到预期的业务帧，则对2#路径传输的业务单元进行恢复，2#路径预期接收的业务单元的每个bit等于1#，3#和4#路径对应比特的BIP计算结果。或者，Z网元对在2#路径接收的数据帧进行CRC校验的校验结果错误，而1#，3#和4#路径上的具有相对应的对齐标识的业务单元的CRC校验结果正确，则对2#路径传输的业务单元进行恢复，2#路径预期接收的业务单元的每个bit根据1#，3#路径传输的业务单元和4#路径传输的BIP校验信息确定。
例如，恢复帧的封装头占用12个字节，即bit0～bit95，1#路径接收的业务帧中bit0＝0，3#路径接收的业务帧中bit0＝1，4#路径接收的恢复帧中对1#-3#路径中bit0的校验结果bit96＝1，则预期接收的3#路径接收的业务帧中bit0＝1#的
Figure PCTCN2020102591-appb-000003
的
Figure PCTCN2020102591-appb-000004
的bit96＝0。通过上述方式，可以对2#路径的业务帧进行恢复并发送。
对齐标识可以参与或不参与校验。A网元可以与Z网元约定业务帧中的进行BIP校验的字段。
对齐标识参与校验的情况，对齐标识可以位于每个业务帧的尾部。由于每个帧的长度不同，通过帧尾部的对齐标识，可以判断该帧是否恢复完成。也就是说，可以通过帧尾部的标识，确定帧的长度。
或者，对齐标识可以位于业务单元的尾部。由于业务单元的长度不同，通过业务单元尾部的对齐标识，可以判断该业务单元是否恢复完成。一个业务单元可以包括一个或多个业务帧。可以通过帧格式，对不同的业务帧进行区分。或者，A网元在不同的业务帧之间插入特定的序列，以区分同一个业务单元中的不同业务帧。
对齐标识也可以位于业务单元的其他位置。业务单元的尾部可以包括固定序列的字段。通过业务单元尾部的固定序列的字段，可以判断该业务单元是否恢复完成。
以A网元和Z网元之间传递的三路以太网L2VPN业务为例，对本申请提供的通信方法进行了说明。通过上述方法，根据各路径传递的业务帧和恢复帧构造BIP校验矩阵，基于BIP检错方法恢复任意一路丢失或出错的业务帧。本发明无需专门检测线路的故障，无需专门设置APS协议，只需要对业务帧进行判断，比如通过MAC的CRC-32校验结果判断帧的正确性，或指定窗口是否收到预期的帧，就可以实施恢复正确的业务数据。实施方式简洁，易部署。
图11是本申请实施例提供的一种通信方法的示意图。
A网元和Z网元之间设置有3条100Gbps以太网链路，分别为1#-3#路径。A网元和Z网元之间还设置有1条200Gbps以太网链路作为4#路径。A网元从S1-S3三个接口接收 以太网L2VPN业务。1#-3#路径的速率可以为100Gbps。对1#-3#路径的业务帧采用RS(544,514)的前向纠错(FEC)方式进行编码，形成恢复帧，恢复帧通过A网元与Z网元之间的4#路径，从A网元传输至Z网元。
通过RS编码，能够对最多冗余比特的比特数量一半的比特进行纠错。参见图12，对RS(544,514)进行简单说明。每个符号长度为10比特，也就是说，一个符号长为10比特。每个RS码字包括514个符号长的数据和30个符号长的校验信息，该校验信息也可以称为冗余比特。A网元对每514个符号长度的数据进行RS(544,514)编码计算，生成30个符号长的冗余比特，以形成RS码字；接收端接收RS码字，对其中的514个符号的数据和30个符号长的冗余比特，进行RS(544,514)解码计算。通过RS(544,514)方式形成的RS码字，最多可以对514个符号的数据中的15个符号的错误进行纠正。
A网元接收路径S1，S2，S3发送的业务。根据该接收的业务，生成业务帧。一个业务单元可以包括一个或多个业务帧。以一个业务单元包括一个业务帧为例进行说明。
A网元通过1#-3#路径每个路径分别向Z网元传输3个业务帧。在这3个业务帧中，在每个业务帧分别取15个符号长(15*10＝150)的比特，该15个符号长的比特即为一个业务比特组。在计算时填充469个符号的信息，进行RS(544,514)编码，形成30个符号长的校验信息。30个符号长的校验信息即为一个恢复比特组。填充的信息可以是预设值，也可以由A网元与Z网元约定，例如填充4690个“0”进行RS(544,514)编码。上述3个业务帧每个业务帧的15个符号，校验信息的30个符号(300比特)，以及填充的469个符号，构成一个RS码字。进行RS(544,514)编码时，1#-3#路径中的每个业务单元中的15个符号分别作为一个业务比特组，生成30个符号长的恢复比特组。根据对业务单元不同的业务比特组进行RS(544,514)编码，生成的恢复比特组，确定恢复单元。一个恢复单元可以包括一个或多个恢复帧。恢复帧的封装头包括目的MAC地址和源MAC地址，目的MAC地址和源MAC地址可以由A网元和Z网元指定。
通过1#-4#路径传输的每个业务单元或恢复单元均包括对齐标识。或者说，A网元在向Z网元通过1#～3#路径发送业务流时在每个业务单元中插入对齐标识，通过通过4#路径发送恢复流时在每个恢复单元中插入对齐标识。4#路径传输的第i恢复单元是根据1#-3#路径中的每个路径传输的第i业务单元生成的。可以在4#路径传输的第i恢复单元中插入第i对齐标识，可以在1#-3#路径中的每个路径传输的第i业务帧中插入与第i恢复单元中的第i对齐标识对应的对齐标识，每个第i业务单元中的对齐标识以及第i恢复单元中的对齐标识可以相同或不同。例如，每个第i业务单元中的对齐标识以及第i恢复单元中的对齐标识可以是相同的编号。比如从1开始计数，最大65535，计数至65535则再从1开始。
对齐标识可以位于帧的头部或帧净荷。例如可以位于帧净荷的最后。
A网元可以对每个帧进行校验并将校验结果CRC-32附加在业务帧尾部。
该业务帧、恢复帧均可以称为数据帧。参见图9，A网元可以在数据帧的尾部添加对齐标识。A网元可以对包括或不包括该对齐标识的数据帧进行CRC校验，将得到的CRC校验信息添加在该数据帧的尾部，对齐标识之后。
Z网元接收1#-4#路径传输的流。
对于在1#-3#路径，Z网元如果在指定时间窗内收到预期业务单元，并且校验结果正 确，则保存一份拷贝后立即发送。在指定时间窗内收到预期业务单元，可以是指定时间窗内接收到包括预设的对齐标识的业务单元，或者接收到与其他路径的业务单元或恢复单元的对齐标识相互对应的业务单元。
Z网元在4#路径收到恢复单元，恢复单元包括第i对齐标识。此时，如果第i单元标识对应的1#-3#路径传输的业务单元均已经过CRC校验且正确，则丢弃该恢复单元。如果第i单元标识对应的1#-3#路径传输的业务单元至少有一个业务单元尚未进行CRC校验，或校验有误，则保存该恢复单元。
对于1#-3#路径，Z网元如果在指定时间窗内，在某一路径没有收到预期单元，则可以根据从其他路径上接收的业务帧和恢复帧，恢复该路径的业务帧。或者，如果一条或多条路径上的传输的业务帧CRC校验结果错误，则可以根据各路径上的业务帧和恢复帧进行纠错。
例如，指定时间窗内，Z网元在1#、3#、4#路径上接收到包含相应标识的业务单元或恢复单元，例如，这些业务单元、恢复单元包含相同编号。Z网元在2#路径上没有接收到包括相应标识的业务单元。可以根据1#，3#和4#路径接收的业务单元、恢复单元，恢复2#路径上对应的业务单元。2#路径上预期接收的业务单元，每15个符号(150比特)可以与1#，3#对应的15个符号(150比特)、4#路径的恢复帧中对应的30个符号(300比特)，以及填充比特构成一个RS码字，进行RS(544,514)解码计算，从而进行恢复。比如1#路径接收的业务帧的bit0～149，3#路径接收的业务帧的bit0～149，4#路径接收的恢复帧的bit96～395(假设恢复单元的帧封装头占用12个字节，即bit0～bit95)，则预期接收的2#路径的业务单元bit0～149可以通过RS(544,514)解码完整恢复。通过此方式，可以将2#路径的整个业务单元恢复并发送。
再例如，指定时间窗内，在1#-4#路径上接收到包含相应标识的帧，对每个帧进行CRC校验，其中全部或部分帧的结果错误。根据1#-3#路径上的每个帧中相互对应的15个符号，和4#路径的恢复帧中对应的30个符号，进行RS(544,514)解码，对错误的比特进行纠正。
对于各路径业务帧的长度不相等的情况，或者业务帧不是15个符号的整数倍的情况，在RS编解码时，可以在业务帧的尾部填充固定序列，例如填充“0”、“1”或它们的特定组合，以满足RS编解码要求。每个RS码字需要5140比特的业务信息，业务路径的数量较少，每次进行编码的比特数量不足5140比特时，也可以通过填充固定序列，例如填充“0”、“1”或特定组合，以构造RS码字。应当理解，这些填充的固定序列，可以通过路径传输，也可以不进行传输，仅作为一种约定的格式，在RS编码和解码时使用。
业务单元的对齐标识可以参与或不参与校验。业务单元可以包括对齐标识，该对齐标识可以用于指示对该业务单元进行恢复的恢复业务单元。该对齐标识还可以用于指示对该业务单元进行恢复的其他业务单元。
对齐标识可以位于业务单元的尾部。由于每个帧的长度不同，通过业务单元尾部的标识，可以判断该业务单元是否恢复完成。也就是说，可以通过业务单元尾部的标识，确定业务单元的长度。
对齐标识也可以位于业务帧的其他位置。业务单元的尾部可以包括固定序列的字段。通过业务单元尾部的固定序列的字段，可以判断该业务单元是否恢复完成。
4#保护路径可以用于承载恢复单元，恢复单元可以包括FEC编码得到的冗余比特。 对于本申请实施例提供的方式，4#路径可以是1#-3#业务路径传输速率的两倍。或者，FEC校验信息可以通过4#和5#两路保护路径发送。4#和5#路径可以与1#-3#业务路径传输速率相等，或略高于1#-3#业务路径的传输速率。应当理解，相等可以是近似相等。
A网元进行RS编码时，调整一个RS码字中各个路径传输的符号的数量，Z网元可以实现对多条业务流的恢复。例如，A网元采用RS(544，514)编码方式，1#-3#路径分别取50个符号长以进行RS编码，则可以实现对1#-3#路径传输的数据的保护。
以在A和Z两端传递的三路以太网L2VPN业务为例，对本申请提供的通信方法进行了说明。通过上述方式，路径故障的情况下，不会发生数据的丢失。以各路径传递的业务单元构造FEC码字，发送端的A网元进行FEC编码，接收端的Z网元进行FEC解码，从而恢复至少一路丢失的业务单元，或对各路径传输的业务单元进行纠错。本发明无需专门检测线路的故障，无需专门设置APS协议，只需要接收端的Z网元判断业务单元是否接收，或根据CRC校验结果判断帧的正确性，就可以对以太帧的中的业务数据进行恢复或纠错。实施方式简洁，易部署。
图13是本申请实施例提供的一种通信方法的示意图。
以1#-3#路径传输为15Gbps的比特流为例进行说明。
FEC编码的形成的一个FEC码字最多可以对N个比特进行纠错，则在每条路径取不超过N个比特，进行FEC编码，以形成FEC码字。发送端A网元每次从1#-3#路径待传输的比特流中分别取N个比特，3路3组N比特的信号组成一个FEC码字，实施FEC编码，FEC编码后生成的冗余比特校验信息由4#路径传输。
以RS编码为例，2N个冗余比特最多可以对N个比特进行纠错。如果在每条路径取N个比特进行RS编码以形成一个RS码字，则4#路径的传输速率可以是1#-3#路径中每条路径的两倍。
接收端Z网元每次从1～3#路径分别取N个比特，从4#路径取2N个比特。根据这些比特形成一个FEC码字，将FEC解码后的结果发送至其他通信设备。
在每个路径传输的比特流中可以不进行标识的插入。对1#-4#路径在初始运行时实施对齐(后续可以再以一定周期进行路径的对齐)，比如插入一定对齐比特，例如对齐标识(alignment marker，AM)。通过通道对齐，可以确定对应于同一个FEC码字的业务比特和恢复比特。路径对齐的技术方案可以参考IEEE802.3中100G/200G/400G以太网链路基于AM的PCSL/FECL锁定，去抖和重排序的情况。
发送端A网元在1#-4#路径开始进行数据传输时，通过1#-4#路径发送AM信息。接收端Z网元检测AM信息，根据AM信息，进行各路径的锁定，去除抖动，各路径中传输的信息重排序等。Z网元将AM信息从比特流中去除并丢弃。1#-3#路径，每两个AM之间的字段可以作为一个业务单元。4#路径每两个AM之间的字段可以作为一个恢复单元。
FEC采用RS(544,514)算法，则符号的大小是10比特，最大纠错能力是150个比特。
对于1#-3#路径，发送端A网元每次分别取150个待发送的比特。根据该3路中每一路的150比特的信息，进行RS编码，RS编码后生成的2×150比特校验信息由4#路径传输。4#路径的传输速率可以是1#-3#路径的两倍。
T1时刻，接收端Z网元从AM信息之后的第1个比特开始，从1#-3#路径中的每个路 径取150比特的信息，从4#路径取300个比特的信息，从而确定第一个RS码字。对第一个RS码字进行RS(544,514)解码，从而对第一个RS码字中对应于1#-3#路径中每个路径的150比特和4#路径中的300比特进行纠错。在RS解码后，将经过纠错的业务数据发送至其它网络设备。
TK时刻，接收端Z网元从AM信息之后的第150×(K-1)+1个比特开始从1～3#路径中的每个路径取150比特的信息，接收端Z网元从AM信息之后的第300×(K-1)+1个比特开始从4#路径中取300比特的信息，从而确定第K个RS码字。对第K个RS码字进行RS解码，从而对第K个RS码字中对应于1#-3#路径中每个路径的150比特和于4#路径中的300比特进行纠错。在RS解码后，将经过纠错的业务数据发送至其它网络设备。
在另一种可能的实现方式中，FEC编码后生成的2N比特校验信息由4#-5#路径传输。1#-5#路径中每条路径的传输速率相等。相等可以是近似相等。接收端Z网元根据4#-5#路径传输的校验信息，对1#-3#路径传输的业务数据进行保护。
每个RS码字需要5140比特的业务信息，业务路径的数量较少，每次进行编码的比特数量不足5140比特时，也可以通过填充固定序列，例如填充“0”、“1”或特定组合，以构造RS(544,514)码字。应当理解，这些填充的固定序列，可以通过路径传输，也可以不进行传输，仅作为一种约定的格式，在RS编码和解码时使用。
本申请实施例也可以应用在1#-3#路径传输速率不相等的情况。例如，2#路径的传输速率与其他业务速率不同，比如2#路径的传输速率为10Gbps，1#和3#路径的传输速率为15Gbps，网元A可以每次取2#路径的待传输的10个符号(10*10＝100比特)的信息。那么，每个RS码字的中的业务信息为150+100+150＝400比特，填充信息为5140-400＝4740比特。填充信息例如可以补“0”，从而进行RS编码，形成RS(544,514)码字。
通过本申请实施例提供的通信方法，无需专门检测线路的故障，无需检测无需专门设置APS协议。通过FEC方式生成的恢复流，在对业务流进行回复时，无需判断每个包的CRC校验结果是否正确。业务单元的恢复，不依赖于对该业务单元或其他业务单元正确性的判断。可以对至少一条业务路径进行保护。在开始阶段对各个路径进行对齐，实施方式更简洁，易部署。
图14是本申请实施例提供的一种通信设备的示意性结构图。通信设备1400包括生成模块1410，发送模块1420。
生成模块1410用于生成M个恢复流和N个业务流，M、N为正整数；
发送模块1420用于向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
可选地，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
可选地，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
可选地，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务 包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
可选地，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
可选地，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
可选地，所述校验的方式为比特交织奇偶校验BIP。
可选地，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
可选地，所述纠错编码的方式为前向纠错FEC编码。
可选地，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
可选地，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
图15是本申请实施例提供的一种通信设备的示意性结构图。通信设备1500包括收发模块1510，确定模块1520。
收发模块1510用于接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；
确定模块1520用于确定所述N个业务流。
可选地，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
可选地，确定模块1520用于根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；
收发模块1510还用于，发送所述第i个业务单元。
可选地，确定模块1520包括恢复子模块，恢复子模块用于根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
可选地，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
可选地，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
可选地，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾 部，用于指示所述第i业务单元结束。
可选地，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
可选地，所述校验的方式为比特交织奇偶校验BIP。
可选地，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
可选地，所述纠错编码的方式为前向纠错FEC编码。
可选地，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
可选地，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
图16是本申请实施例提供的一种通信设备的示意性结构图。通信设备1600包括处理器1610和通信接口1620。
处理器1610用于生成M个恢复流和N个业务流，M、N为正整数；
通信接口1620用于向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
可选地，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
可选地，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
可选地，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
可选地，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
可选地，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
可选地，所述校验的方式为比特交织奇偶校验BIP。
可选地，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第 k业务比特进行BIP的结果，k为正整数。
可选地，所述纠错编码的方式为前向纠错FEC编码。
可选地，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
可选地，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
图17是本申请实施例提供的一种通信设备的示意性结构图。通信设备1700包括处理器1710和通信接口1720。
通信接口1720用于接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；
处理器1710用于确定所述N个业务流。
可选地，所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
可选地，处理器1710用于根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；
通信接口1720还用于，发送所述第i个业务单元。
可选地，处理器1710用于根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
可选地，所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
可选地，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
可选地，所述第i业务单元包括对齐标识，所述对齐标识位于所述第i业务单元的尾部，用于指示所述第i业务单元结束。
可选地，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
可选地，所述校验的方式为比特交织奇偶校验BIP。
可选地，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
可选地，所述纠错编码的方式为前向纠错FEC编码。
可选地，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
可选地，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
本申请实施例还提供一种通信系统，包括第一通信设备和第二通信设备。
本申请实施例还提供一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被执行时，使得前文中的方法被执行。
本申请实施例还提供一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得前文中的方法的方法被执行。本申请实施例还提供一种通信系统，其包括一个或多个前述的通信设备。
本申请实施例还提供一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被执行时，使得前文中的方法被执行。
本申请实施例还提供一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得前文中的方法被执行。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机 软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (46)

  1. 一种通信方法，其特征在于，包括：
    第一通信设备生成M个恢复流和N个业务流，M、N为正整数；
    所述第一通信设备向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
  6. 根据权利要求5所述的方法，其特征在于，所述校验的方式为比特交织奇偶校验BIP。
  7. 根据权利要求6所述的方法，其特征在于，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行BIP的结果，k为正整数。
  8. 根据权利要求5所述的方法，其特征在于，所述纠错编码的方式为前向纠错FEC编码。
  9. 根据权利要求8所述的方法，其特征在于，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
  11. 一种通信方法，其特征在于，包括：
    第二通信设备接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；
    所述第二通信设备确定所述N个业务流。
  12. 根据权利要求11所述的方法，其特征在于，
    所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第二通信设备根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；
    所述第二通信设备发送所述第i个业务单元。
  14. 根据权利要求11或12所述的方法，其特征在于，所述第二通信设备确定所述N个业务流，包括：
    所述第二通信设备根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
  15. 根据权利要求11-14中任一项所述的方法，其特征在于，
    所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
  16. 根据权利要求15所述的方法，其特征在于，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
  17. 根据权利要求11-16中任一项所述的方法，其特征在于，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
  18. 根据权利要求17所述的方法，其特征在于，所述校验的方式为比特交织奇偶校验BIP。
  19. 根据权利要求18所述的方法，其特征在于，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
  20. 根据权利要求17所述的方法，其特征在于，所述纠错编码的方式为前向纠错FEC编码。
  21. 根据权利要求20所述的方法，其特征在于，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务 比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
  22. 根据权利要求11-21中任一项所述的方法，其特征在于，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
  23. 一种通信设备，其特征在于，包括：
    处理器，用于生成M个恢复流和N个业务流，M、N为正整数；
    通信接口，用于向第二通信设备发送所述M个恢复流和所述N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，i、j为正整数。
  24. 根据权利要求23所述的设备，其特征在于，
    所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务单元的正确性。
  25. 根据权利要求23或24所述的设备，其特征在于，
    所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
  26. 根据权利要求25所述的设备，其特征在于，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
  27. 根据权利要求23-26中任一项所述的设备，其特征在于，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
  28. 根据权利要求27所述的设备，其特征在于，所述校验的方式为比特交织奇偶校验BIP。
  29. 根据权利要求28所述的设备，其特征在于，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
  30. 根据权利要求27所述的设备，其特征在于，所述纠错编码的方式为前向纠错FEC编码。
  31. 根据权利要求30所述的设备，其特征在于，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
  32. 根据权利要求23-31中任一项所述的设备，其特征在于，所述第i恢复单元的比 特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
  33. 一种通信设备，其特征在于，包括：
    通信接口，用于接收第一通信设备发送的M个恢复流和N个业务流，所述N个业务流中的第j业务流包括至少一个业务单元；所述M个恢复流包括至少一个恢复单元，所述至少一个恢复单元中的第i恢复单元是根据所述N个业务流中的每个业务流中的第i业务单元得到的，M、N、i、j为正整数；
    处理器，用于确定所述N个业务流。
  34. 根据权利要求33所述的设备，其特征在于，
    所述第j业务流包括至少一个检测标识，所述至少一个检测标识中的第i检测标识用于检测所述第j业务流中的第i业务码块的正确性。
  35. 根据权利要求34所述的设备，其特征在于，
    所述处理器还用于，根据所述第i检测标识，确定所述第j业务流中的第i个业务单元正确；
    所述通信接口还用于，发送所述第i个业务单元。
  36. 根据权利要求33或34所述的设备，其特征在于，
    所述处理器用于，根据所述第i恢复单元恢复所述N个业务流中的至少一个业务流中每个业务流的第i个业务单元。
  37. 根据权利要求33-36中任一项所述的设备，其特征在于，
    所述M个恢复流中的每个恢复流包括与所述恢复流对应的对齐标识，所述N个业务流中的每个业务流包括与所述业务流对应的对齐标识，所述对齐标识用于指示所述第i恢复单元与所述N个业务流中的每个业务流中的第i业务单元的对应关系。
  38. 根据权利要求37所述的设备，其特征在于，所述第i业务单元包括至少一个对齐标识，其中每个对齐标识位于一个业务包或一个业务帧的尾部，用于指示所述业务包或所述业务帧的结束。
  39. 根据权利要求33-38中任一项所述的设备，其特征在于，所述至少一个恢复单元中的第i恢复单元是对所述N个业务流中的每个业务流中的第i业务单元进行校验或纠错编码得到的。
  40. 根据权利要求39所述的设备，其特征在于，所述校验的方式为比特交织奇偶校验BIP。
  41. 根据权利要求40所述的设备，其特征在于，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特，所述N个业务流中每个业务流的第i业务单元包括至少一个业务比特，所述至少一个恢复比特中的第k恢复比特是对所述N个业务流中每个业务流的第i业务单元中至少一个业务比特的第k业务比特进行比特交织奇偶校验BIP的结果，k为正整数。
  42. 根据权利要求39所述的设备，其特征在于，所述纠错编码的方式为前向纠错FEC编码。
  43. 根据权利要求42所述的设备，其特征在于，所述纠错编码的方式为里德-所罗门RS编码，所述至少一个恢复单元中的第i恢复单元包括至少一个恢复比特组，所述N个业务流中每个业务流中的第i业务单元包括至少一个业务比特组，所述至少一个比特组中 的第k恢复比特组包括对所述N个业务流中每个业务流的第i业务单元中的至少一个业务比特组中的第k业务比特组进行前向纠错FEC编码得到的冗余比特，每个所述第k业务比特组的比特数量小于或等于所述冗余比特的比特数量的一半，k为正整数。
  44. 根据权利要求33-43中任一项所述的设备，其特征在于，所述第i恢复单元的比特数量大于或等于所述第j业务流中的所述第i业务单元的比特数量。
  45. 一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被执行时，使得权利要求1-22中任一项所述方法被执行。
  46. 一种芯片，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得权利要求1-22中任一项所述方法被执行。
PCT/CN2020/102591 2019-07-29 2020-07-17 一种通信方法和通信设备 WO2021017890A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910689815.8A CN112311497A (zh) 2019-07-29 2019-07-29 一种通信方法和通信设备
CN201910689815.8 2019-07-29

Publications (1)

Publication Number Publication Date
WO2021017890A1 true WO2021017890A1 (zh) 2021-02-04

Family

ID=74229479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/102591 WO2021017890A1 (zh) 2019-07-29 2020-07-17 一种通信方法和通信设备

Country Status (2)

Country Link
CN (1) CN112311497A (zh)
WO (1) WO2021017890A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115551019A (zh) * 2021-06-30 2022-12-30 华为技术有限公司 数据流的传输方法和传输装置

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1380780A (zh) * 2001-03-13 2002-11-20 皇家菲利浦电子有限公司 保护数据包以防差错的方法
JP2005012753A (ja) * 2003-05-29 2005-01-13 Nippon Telegr & Teleph Corp <Ntt> パケット中継装置及びその方法と、パケット受信装置及びその方法と、パケット中継プログラム及びそのプログラムを記録した記録媒体と、パケット受信プログラム及びそのプログラムを記録した記録媒体
US20100046549A1 (en) * 2008-08-22 2010-02-25 Infineon Technologies Ag Channel Bonding and Packet Fragment Retransmission Method and Apparatus
CN101674152A (zh) * 2008-09-08 2010-03-17 华为技术有限公司 基于前向纠错的数据传输方法、装置及系统
CN101753279A (zh) * 2008-12-09 2010-06-23 佳能株式会社 通信设备和通信方法
CN108763405A (zh) * 2018-05-22 2018-11-06 深信服网络科技（深圳）有限公司 一种业务数据迁移方法、装置、系统及可读存储介质
CN109962896A (zh) * 2017-12-26 2019-07-02 大唐移动通信设备有限公司 数据包的处理方法、基站、电子设备和存储介质
CN109982083A (zh) * 2017-12-28 2019-07-05 欧鹏斯泰克公司 用以重新排列数据包传输顺序的图像编码装置及其运行方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001061909A1 (en) * 2000-02-16 2001-08-23 Sycamore Networks, Inc. Method and apparatus for correcting data using a redundant path
CN101330369B (zh) * 2007-06-21 2014-07-09 华为技术有限公司 发送、接收方法及装置、通道保护方法及系统
US8787153B2 (en) * 2008-02-10 2014-07-22 Cisco Technology, Inc. Forward error correction based data recovery with path diversity

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1380780A (zh) * 2001-03-13 2002-11-20 皇家菲利浦电子有限公司 保护数据包以防差错的方法
JP2005012753A (ja) * 2003-05-29 2005-01-13 Nippon Telegr & Teleph Corp <Ntt> パケット中継装置及びその方法と、パケット受信装置及びその方法と、パケット中継プログラム及びそのプログラムを記録した記録媒体と、パケット受信プログラム及びそのプログラムを記録した記録媒体
US20100046549A1 (en) * 2008-08-22 2010-02-25 Infineon Technologies Ag Channel Bonding and Packet Fragment Retransmission Method and Apparatus
CN101674152A (zh) * 2008-09-08 2010-03-17 华为技术有限公司 基于前向纠错的数据传输方法、装置及系统
CN101753279A (zh) * 2008-12-09 2010-06-23 佳能株式会社 通信设备和通信方法
CN109962896A (zh) * 2017-12-26 2019-07-02 大唐移动通信设备有限公司 数据包的处理方法、基站、电子设备和存储介质
CN109982083A (zh) * 2017-12-28 2019-07-05 欧鹏斯泰克公司 用以重新排列数据包传输顺序的图像编码装置及其运行方法
CN108763405A (zh) * 2018-05-22 2018-11-06 深信服网络科技（深圳）有限公司 一种业务数据迁移方法、装置、系统及可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
J. ROSENBERG ET AL.: "An RTP Payload Format for Generic Forward Error Correction", RFC 2733, 1 December 1999 (1999-12-01), pages 1 - 27, XP055564777 *

Also Published As

Publication number Publication date
CN112311497A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
US6823470B2 (en) Method and apparatus for correcting data
US7296211B2 (en) System and method for transferring data on a data link
JP5522547B2 (ja) データエラー報告を実現するための方法およびデバイス
US7152199B2 (en) Method and apparatus for delineating data in an FEC-coded Ethernet frame
US20150046775A1 (en) Encoding and Decoding Schemes to Achieve Standard Compliant Mean Time to False Packet Acceptance
US11936475B2 (en) Method, apparatus, and system for improving reliability of data transmission involving an ethernet device
WO2014106319A1 (zh) 以太网中处理数据的方法、物理层芯片和以太网设备
EP2692080B1 (en) Error handling in a passive optical network
CN109274600B (zh) 一种检测块发送和接收的方法、网络设备和系统
US20230119339A1 (en) Block group loss determining method and apparatus
WO2021017890A1 (zh) 一种通信方法和通信设备
CN112350798A (zh) 分组传输方法和装置
WO2019015462A1 (zh) 一种检测块发送和接收的方法、网络设备和系统
US7257759B2 (en) Accounting for error carryover in error correction on M-bit encoded links
CN113078980A (zh) 一种数据传输的方法以及装置
US8787151B2 (en) N+N protection switching
CN1770765A (zh) 一种gfp数据性能监控方法及gfp设备
Dai et al. An adaptive forward error correction method for TDM over Ethernet
CN116260553A (zh) 数据重传的方法、装置及系统
CN115766047A (zh) 一种数据传输方法、设备、可读存储介质和芯片系统

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: 20847912

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20847912

Country of ref document: EP

Kind code of ref document: A1