Patent Description:
With a sharply increasing demand for user data, <NUM> passive optical networks (Passive Optical Network, PON) have entered a stage of large-scale deployment, and next-generation PON system standards are also being gradually formulated and improved. Next-generation mobile communications standards, namely, <NUM> standards have also been basically completed. As higher requirements for a rate and system latency are raised, <NUM> communications has higher requirements for bearer networks. With the development of base stations towards small cells (small cell), coverage density is increasing, and a demand for optical fiber resources is also increasing. Therefore, bearer networks at low costs and with in-depth coverage are required. In a wide context of optical network city construction, PON-based broadband access networks have been deployed on a large scale, and massive optical fibers have been extended to a user side, matching coverage of small cells. United States patent application <CIT> discloses an apparatus comprising a 64b66b encoder. It is disclosed that OAM information can be communicated by replacing padding bits or alternatively can be communicated by selecting a synchronisation sequence. United States patent application <CIT> discloses a method for sending overhead information.

<CIT> (<NUM>-<NUM>-<NUM>) discloses that an indicator can be sent from the encoder to the decoder indicating whether encoding has been performed and whether it is necessary to perform a decoding operation at the receiver.

Currently, China Telecom and China Unicom are promoting the formulation of standards and solutions of wavelength division multiplexing (Wavelength Division Multiplexing, WDM) PON for <NUM> bearer networks.

In view of this, this application provides a data processing method, a data processing apparatus, a communications device, and a communications system.

To make the invention objectives, features, and advantages of this application clearer and more comprehensible, the following clearly and completely describes the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the embodiments described in the following are merely a part rather than all of the embodiments of this application.

The technical solutions in the embodiments of this application may be applied to various communications systems, and for example, may be applied to various point-to-point and point-to-multipoint Ethernet communications systems.

<FIG> is a schematic architectural diagram of a communications system <NUM> that is applicable to the embodiments of this application. The communications system <NUM> includes two communications devices (<NUM> and <NUM>) that communicate with each other. The two communications devices (<NUM> and <NUM>) may be connected by using a physical medium such as an optical fiber. Data transmitted between the two communications devices (<NUM> and <NUM>) may be data on which FEC encoding is performed. It may be that either communications device in <FIG> performs FEC encoding to generate a code word structure, and sends the code word structure to the other communications device, and the other communications device performs FEC decoding on the code word structure.

<FIG> is another schematic architectural diagram of a communications system <NUM> that is applicable to the embodiments of this application. The communications system <NUM> includes a first communications device <NUM>, a PON optical line terminal (Optical Line Terminal, OLT) device <NUM>, a PON optical network unit (Optical Network Unit, ONU) device <NUM>, and a second communications device <NUM>.

Upstream transmission is used as an example. Data sent by the second communications device <NUM> to the PON ONU device <NUM> may be data on which forward error correction (Forward Error Correction, FEC) encoding is performed.

In an example, the PON ONU device <NUM> may not perform FEC encoding on data, and the PON OLT device <NUM> may not perform FEC decoding on the data either, but the first communications device <NUM> performs FEC decoding.

In another example, the PON ONU <NUM> may first perform FEC decoding, and then perform FEC encoding again, and send re-encoded data to the PON OLT device <NUM>. The PON OLT device <NUM> may first perform FEC decoding (a decoding manner is consistent with an FEC encoding manner of the PON ONU device <NUM>), and then send data generated after FEC decoding to the first communications device. Alternatively, FEC encoding may be first performed again on data generated after FEC decoding, and encoded data is sent to the first communications device <NUM>, so that the first communications device <NUM> performs FEC decoding.

Alternatively, data sent by the second communications device <NUM> to the PON ONU device <NUM> may be data on which FEC encoding is not performed. In this case, the PON ONU <NUM> performs FEC encoding on the received data, and sends encoded data to the PON OLT device <NUM>. The PON OLT device <NUM> performs FEC decoding on the received data, and then sends the data to the first communications device <NUM>.

Downstream transmission is similar to upstream transmission. The first communications device <NUM> may perform FEC encoding, the second communications device <NUM> performs FEC decoding, and the PON OLT <NUM> and the PON ONU <NUM> do not perform FEC encoding and decoding. Alternatively, the PON OLT <NUM> may perform FEC encoding, the PON ONU <NUM> performs FEC decoding, and the first communications device <NUM> and the second communications device <NUM> do not perform FEC encoding and decoding. Alternatively, the first communications device <NUM> may perform FEC encoding, the second communications device <NUM> performs FEC decoding, the PON OLT <NUM> performs decoding first and then performs FEC encoding again, and the PON ONU <NUM> performs FEC decoding or performs decoding first and then performs FEC encoding again.

This application may also be applied to a WDM PON system that carries <NUM> services. <FIG> is a schematic architectural diagram of a communications system that is applicable to the embodiments of this application and in which a WDM PON is used to carry <NUM> services. As shown in <FIG>, the communications system <NUM> includes a PON central office device <NUM> (for example, an OLT), a baseband unit (baseband unit, BBU) device <NUM> connected to the PON central office device <NUM>, a PON terminal device <NUM> (for example, an ONU), and a RRU device <NUM> connected to the PON terminal device <NUM>. An arrayed waveguide grating (Arrayed Waveguide Grating, AWG) <NUM> (or may be an optical splitter) is connected between the PON central office device <NUM> and the PON terminal device. It may be that the PON central office device <NUM> performs FEC encoding, and the PON terminal device <NUM> performs FEC decoding; or that the PON terminal device <NUM> performs FEC encoding, and the PON central office device <NUM> performs FEC decoding. Alternatively, the BBU device performs FEC encoding and decoding, and the PON central office device <NUM> and the PON ONU-end device <NUM> may not perform FEC encoding and decoding. Alternatively, the BBU device performs FEC encoding and decoding; the PON central office device <NUM> performs decoding first, and then performs FEC encoding; and the PON terminal device <NUM> performs FEC decoding, or performs decoding first, and then performs FEC encoding again. Alternatively, the BBU device performs FEC encoding and decoding; the PON terminal device <NUM> performs decoding first, and then performs FEC encoding; and the PON central office device <NUM> performs FEC decoding, or performs decoding and then performs FEC encoding again.

Thanks to its features, such as a low latency and a high bandwidth, the WDM PON can be used to carry eCRPI services. Operators have the following requirements for the WDM PON: <NUM>. a low latency for wireless services and transparent transmission of wireless services; <NUM>. the system can provide an OAM function and implement management and diagnosis of a PON network; <NUM>. a rate of <NUM> Gbit/s is supported.

It may be understood that the architectures shown in <FIG> are merely examples, and are not intended to limit the protection scope of this application. The communications system in this application may also use another architecture form.

A communication rate that can be supported by the communications system in this embodiment of this application may be <NUM> Gbit/s, <NUM> Gbit/s, or the like, or may be another rate, which is not limited herein.

The technical solutions of the embodiments of this application described in the following may be executed by either communications device in <FIG>, or may be executed by the PON OLT device and the PON ONU device in <FIG>. For ease of description, in the following, a device used as a sender is referred to as a source network device, and a device used as a receiver is referred to as a target network device.

The source network device and the target network device may include a processing module. The processing module may be a MAC (Media Access Control, media access control) chip, a processor, a DSP (digital signal processor, digital signal processor), or the like. The processing module performs an operation at a physical coding sublayer (Physical Coding Sublayer, PCS). The following uses an example in which the MAC chip performs an operation at the physical coding sublayer.

When the source network device performs FEC encoding and the target network device performs FEC decoding, <FIG> is a schematic flowchart of FEC encoding according to an embodiment of the present invention. User data from a MAC layer may be transcoded at the physical coding sublayer first, and then is scrambled; then an idle character in the user data is periodically deleted; and then a piece of first information (which may also be referred to as a code word marker, or a code marker) is periodically inserted. A length of the deleted idle character is the same as a length of the piece of first information to be inserted, which can ensure that a line rate does not change. FEC encoding is performed on the inserted first information and the user data together, to form a complete FEC code word.

It may be understood that the first information in this application may have another name, which does not limit the protection scope of the first information.

One FEC code word of every <NUM> FEC code words carries the first information.

When the source network device performs FEC encoding and the target network device performs FEC decoding, as shown in <FIG>, the following provides a data encoding and decoding method.

S200: The source network device receives S first data blocks at a physical coding sublayer, where S is a positive integer.

In an embodiment, the first data block may be a 256b/257b data block, which means that a total length of the data block is <NUM> bits, including <NUM>-bit data and <NUM>-bit indication information.

The first data block may be generated by transcoding four 64b/66b or 64b/65b data blocks. The source network device may perform transcoding to generate the first data block.

In another embodiment, the first data block may alternatively be a data block of another length. For example, the first data block may be a 64b/66b or 64b/65b data block. The 64b/66b data block means that a total length of the data block is <NUM> bits, including <NUM>-bit data and <NUM>-bit indication information. The 64b/65b data block means that a total length of the data block is <NUM> bits, including <NUM>-bit data and <NUM>-bit indication information.

S201: The source network device performs FEC encoding on the S first data blocks and first information at the physical coding sublayer to generate a check part, where the first information includes code word synchronization information and operation, administration and maintenance (operation, administration and maintenance, OAM) information, and the S first data blocks and the first information form valid data.

S202: The source network device generates a code word structure at the physical coding sublayer, where the code word structure includes the S first data blocks, the first information, and the check part.

An FEC code type used by the source network device and the target network device is correspondingly provided with an FEC code word length and an FEC payload length, which indicates that in a code word structure generated after encoding is performed by using the FEC code type, a length of a check part is equal to the FEC code word length minus the FEC payload length. The FEC code type may be, for example, a Reed-Solomon (Reed-Solomon, RS) code type. For example, the code type may be an RS (<NUM>, <NUM>) code type, and a granularity is <NUM> bits, indicating that the FEC code word length is <NUM>×<NUM> bits, the FEC payload length is <NUM>×<NUM> bits, and the length of the check part is (<NUM>-<NUM>)×<NUM> bits. For the RS (<NUM>, <NUM>) code type, after FEC encoding is performed on <NUM>-bit valid data, a <NUM>-bit check part is generated, and the FEC code word length of a generated code word structure is <NUM> bits. It may be understood that the FEC code type may also be another code type, which is not limited herein.

It may be understood that the FEC code type may also be expressed in another manner, provided that the FEC code word length and the FEC payload length are indirectly indicated.

The source network device may perform an operation of adding or inserting the first information. To ensure that a line rate does not change, in an embodiment according to the claimed invention, an idle character whose length is the same as a length of the first information is deleted, and the first information is added. Specifically, the source network device may periodically add the first information. For example, the first information may be added once every <NUM> code words.

The code word synchronization information is used by the target network device to perform code word synchronization. The OAM information is used for operation, administration, and maintenance of a PON network, and further management and diagnosis of the PON network are implemented.

S203: The source network device sends the code word structure to the target network device.

S204: The target network device receives the code word structure.

S205: The target network device synchronizes the code word structure at the physical coding sublayer based on the code word synchronization information.

S206: The target network device performs FEC decoding on the code word structure.

S207: The target network device obtains the OAM information. Specifically, the OAM information is obtained from the first information. Further, between the source network device and the target network device, functions such as operation, administration, and maintenance of the PON network, and management and diagnosis of the PON network are implemented by using the OAM information.

In an embodiment, the first information further includes first indication information, and the first indication information is used to indicate whether the code word structure includes the OAM information. In code word structures sent by the source network device to the target network device, even if first information is included in some of the code word structures, there may be no OAM information. Therefore, by using the first indication information, a receive end may be notified whether the first information in the current code word structure includes the OAM information.

In an embodiment, the first information further includes second indication information, and the second indication information is used to indicate whether the receive end (that is, the target network device) performs FEC decoding on the code word structure. When the source network device performs FEC encoding, the second indication information instructs the target network device to perform FEC decoding on the code word structure, and the target network device may learn, based on the second indication information, that FEC decoding may be performed on the code word structure. When the source network device does not perform FEC encoding, the second indication information instructs the target network device not to perform FEC decoding on the code word structure, and the target network device may learn, based on the second indication information, that FEC decoding may not be performed on the code word structure.

In an embodiment, a length of the first information may be, for example, <NUM> bits. It may be understood that the first information may alternatively be of another length. This is not limited herein. Lengths of the code word synchronization information, the OAM information, the first indication information, and the second indication information may be allocated according to an actual requirement.

The following uses an example in which the length of the first information is <NUM> bits. The first information includes four second data blocks, and a length of each second data block is <NUM> bits. It may be understood that the second data block herein is defined for ease of the following description, or may be understood as a set of a preset quantity of bits. A length of the first information in the existing 25GE standards is <NUM> bits, including four alignment markers (alignment marker). A length of each alignment marker is <NUM> bits. It may be understood that the second data block herein may also be referred to as the alignment marker.

A quantity of second data blocks occupied by the code word synchronization information and the OAM information may be flexibly set according to an actual requirement. For example, one second data block carries the code word synchronization information, and at least one second data block carries the OAM information.

Specifically, in an embodiment, one second data block may be used to carry the code word synchronization information, and one second data block is used as a reserved field. The other two of the second data blocks are used to carry the OAM information. In this case, a valid rate of a management channel is: <NUM> Gbps×<NUM>/(<NUM>×<NUM>)=<NUM> kbps.

In another embodiment, one second data block may be used to carry the code word synchronization information. In one data block, some bits are used as a reserved field, and some bits are used as an OAM field. A length of the OAM field may be, for example, <NUM> bits, a length of the reserved field may be, for example, <NUM> bits, and the other <NUM> bits may be used as a BIP field. The OAM field and the other two of the data blocks (one is referred to as block0 and the other is referred to as block1) are used to jointly carry the OAM information. The OAM field may be alternatively divided into two parts: part0 and part1, both of which are <NUM> bits in length. Part0 and block0 may form an OAM message, and part1 and block1 may form another OAM message. A length of each OAM message is <NUM> bytes. The reserved field may be used to carry the first indication information and the second indication information. Some bits or all bits of the reserved field are used to carry at least one of the first indication information and the second indication information.

In the preceding solution, an FEC synchronization state machine as a whole does not need to be modified, a determination condition for generating cwm_valid is that <NUM> bits are determined, and other data is not processed. A synchronization solution is consistent with a common 25GE synchronization process, and is therefore compatible with standard 25GE interfaces.

On a basis of an FEC coding scheme that is based on the 25GE standards, this solution implements establishment of an OAM management channel without increasing complexity or introducing an extra power penalty. In addition, the OAM management channel is protected by FEC and has the same performance as a service channel. The service channel is transparently transmitted, and service data is not affected. The OAM management channel is implemented based on FEC coding and can be used to collect service performance statistics.

A format of the OAM information may be, for example, shown in the following table.

Message Type indicates a message type. A message type may correspond to a plurality of OPcodes. The OPcode indicates a more detailed message type under this message type. Message Word indicates message content. FCS indicates a frame check sequence (frame check sequence).

Specifically, the OAM information may be, for example, a channel configuration message.

The OAM information may be, for example, a channel indication message.

The OAM information may be, for example, a channel confirmation message.

The message types of the foregoing three types of OAM information are channel type messages, and the OPcode is 0x01 (indicating a channel configuration message), 0x02 (indicating a channel indication message), and 0x01 (indicating a channel confirmation message) separately. Channel No. indicates a channel number.

The OAM information may be, for example, a status query message.

Module Status Request indicates a module status information request, which indicates that a peer end is requested to send a current module status.

The OAM information may be, for example, a status recovery message.

Module Status Report indicates a module status information report, which indicates that a current module status is reported to the peer end.

The OAM information may be, for example, a link performance query message.

Request indicates a link bit error request, which indicates that the peer end is requested to send information about a current bit error rate.

The OAM information may be, for example, a performance recovery message.

Report indicates a link bit error report, which indicates that information about a current bit error rate is reported to the peer end.

It may be understood that the foregoing OAM message formats are examples, and are not intended to limit the protection scope of this application. The OAM message format may also be another format. Specific values of the foregoing Message Type and Opcode may also be other values, which are not limited herein. The foregoing tables are examples.

The first communications device and the second communications device do not perform FEC encoding and decoding. FEC encoding and decoding is uniformly performed at a WDM PON layer, and the code word synchronization information and the OAM information are inserted, which does not affect a link rate. Considering interworking, a reserved field in the first information is used for indication, to notify an ONU or an OLT whether the first communications device or the second communications device has performed FEC. If FEC is not performed on 25GE of the first communications device and 25GE of the second communications device, the ONU side or the OLT side needs to restore the original <NUM>-bit stream after terminating OAM, and then forward the original <NUM>-bit stream to the first communications device or the second communications device.

When the source network device does not need to perform FEC encoding, as shown in <FIG>, for example, when the OLT is the source network device, and the first communications device performs FEC encoding, and sends a code word structure generated after FEC encoding to the source network device, then the OLT does not need to perform FEC encoding, and the ONU does not need to perform FEC decoding either. The second communications device performs FEC decoding. The following provides a data processing method.

S301: The source network device receives a code word structure at a physical coding sublayer, where the code word structure includes S first data blocks, first information, and a check part, and the first information includes code word synchronization information.

S302: The source network device updates the first information at the physical coding sublayer, where updated first information includes OAM information.

S303: The source network device sends the code word structure to the target network device.

S304: The target network device receives the code word structure.

S305: The target network device synchronizes the code word structure at the physical coding sublayer based on the code word synchronization information.

S306: The target network device obtains the OAM information at the physical coding sublayer. Further, between the source network device and the target network device, functions such as operation, administration, and maintenance of a PON network, and management and diagnosis of the PON network are implemented by using the OAM information.

To ensure that a line rate does not change, a manner of updating the code word structure, according to an embodiment of the claimed invention, is: deleting a reserved character in the first information, and then inserting the OAM information. A quantity of bits of the deleted character is the same as a quantity of bits inserted.

For example, in the system architecture shown in <FIG>, downstream transmission is used as an example, and a 25GE system is used as an example. The first communications device <NUM> sends a code word structure to the OLT. First information (which may be referred to as a code word marker in 25GE) in the code word structure includes four alignment markers, and only one of the alignment markers may be used to carry code word synchronization information. In this way, for the first communications device <NUM>, an original communications protocol may not be changed, and an original encoding manner may not be changed either.

The OLT may update OAM information to all or some of the other three alignment markers. For example, the OAM information may be updated to two of the alignment markers. For example, original characters in the last two alignment markers are deleted, and the OAM information is inserted into the two alignment markers.

After receiving the code word structure, the ONU obtains the OAM information in the code word structure.

The ONU may delete the OAM information in the code word structure, and replace the OAM information with an original reserved character (that is, a reserved character deleted when the OLT updates the code word structure). Alternatively, the second communications device <NUM> may delete the OAM information in the code word structure, and replace the OAM information with the original reserved character.

For the second communications device <NUM>, synchronization is still performed based on the code word synchronization information in one of the alignment markers, an original communications protocol is not changed, and an original decoding manner is not changed either. The second communications device <NUM> performs FEC decoding on an after-replacement code word structure.

Updated first information may further include first indication information, and the first indication information is used to indicate whether the code word structure includes the OAM information.

According to an embodiment of the claimed invention, the updated first information further includes second indication information, and the second indication information is used to indicate whether a receive end performs FEC decoding on the code word structure.

For specific details of the first information in this embodiment and other details in this embodiment, refer to the details of the embodiment shown in <FIG>.

In another embodiment, FEC enabling or FEC disabling of a WDM PON device remains consistent with 25GE of a wireless device. In a scenario without FEC, code word synchronization information and OAM information may be periodically inserted in a manner of deleting idle, but transcoding and FEC are not performed. An insertion period of the code word synchronization information and the OAM information is the same as that in the foregoing solution, and an FEC indication field is also reserved to notify an ONU whether to enable FEC. After receiving data, the ONU obtains the code word synchronization information and OAM information, and replaces the OAM information with Idle.

This application further provides a communications device <NUM>. The communications device <NUM> may be either of the communications devices (<NUM> and <NUM>) shown in <FIG>, may be the PON OLT device <NUM> or the PON ONU device <NUM> shown in <FIG>, or may be the PON central office device <NUM> or the PON terminal device <NUM> shown in <FIG>. As shown in <FIG>, the communications device <NUM> includes a processor <NUM>, a memory <NUM>, a medium access control (medium access control, MAC) chip <NUM>, and a transceiver <NUM>.

The processor <NUM> may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application-specific integrated circuit ASIC, or at least one integrated circuit, and is configured to execute a related program, to implement the technical solutions provided in the embodiments of this application.

The memory <NUM> may be a read only memory (Read Only Memory, ROM), a static storage device, a dynamic storage device, or a random access memory (Random Access Memory, RAM). The memory <NUM> may store an operating system and another application program. When the technical solutions provided in the embodiments of this application are implemented by using software or firmware, program code used to implement the technical solutions provided in the embodiments of this application is stored in the memory <NUM>, and is executed by the processor <NUM>.

In an embodiment, the processor <NUM> may internally include the memory <NUM>. In another embodiment, the processor <NUM> and the memory <NUM> are two independent structures.

In an embodiment, the processor <NUM> and the MAC chip <NUM> may be two independent structures. In another embodiment, the processor <NUM> may include the MAC chip <NUM>. The MAC chip <NUM> may include a physical coding sublayer and a MAC control sublayer.

The transceiver <NUM> may include an optical transmitter and/or an optical receiver. The optical transmitter may be configured to send an optical signal, and the optical receiver may be configured to receive an optical signal. The optical transmitter may be implemented by using a light emitting device, such as a gas laser, a solid state laser, a liquid laser, a semiconductor laser, or a direct modulated laser. The optical receiver may be implemented by using an optical detector, such as a photodetector or a photodiode (such as an avalanche photodiode). The transceiver <NUM> may further include a digital-to-analog converter and an analog-to-digital converter.

The MAC chip <NUM> or the processor <NUM> may perform steps of the physical coding sublayer.

It can be learned from the foregoing embodiments that when the communications device <NUM> is used as a source network device, the MAC chip <NUM> or the processor <NUM> is configured to perform steps S200, S201, S202, S203, S301, S302, and S303.

When the communications device <NUM> is used as a target network device, the MAC chip <NUM> or the processor <NUM> is configured to perform steps S204, S205, S206, S207, S304, S305, and S306.

For more details about the processor <NUM> and the MAC chip <NUM> performing the foregoing steps at the physical coding sublayer, refer to related descriptions of the embodiments of the foregoing method and the accompanying drawings.

This embodiment of this application also has various beneficial effects described in the foregoing method embodiments, and details are not described herein again.

This application further provides a data processing apparatus. The apparatus may be integrated into the communications device <NUM> in the foregoing embodiment. For example, the apparatus may be integrated into the MAC chip of the communications device <NUM>, integrated into the processor, or integrated into a DSP chip. As shown in <FIG>, the apparatus includes a receiving module <NUM>, an FEC encoding and decoding module <NUM>, and a generation module <NUM>.

It can be learned from the foregoing embodiments that the receiving module <NUM> is configured to perform step S200, the FEC encoding and decoding module <NUM> is configured to perform step S201, and the generation module <NUM> is configured to perform step S202.

The apparatus further includes a sending module, configured to perform step S203.

The apparatus further includes a transcoding module, and the transcoding module is configured to perform a transcoding operation.

For more details about the modules of the apparatus performing the foregoing steps, refer to related descriptions of the embodiments of the foregoing method and the accompanying drawings.

This application further provides a data processing apparatus. The apparatus may be integrated into the communications device <NUM> in the foregoing embodiment. For example, the apparatus may be integrated into the MAC chip of the communications device <NUM>, integrated into the processor, or integrated into a DSP chip. As shown in <FIG>, the apparatus includes a receiving module <NUM> and an updating module <NUM>.

It can be learned from the foregoing embodiments that the receiving module <NUM> is configured to perform step S301, and the updating module <NUM> is configured to perform step S302.

The apparatus further includes a sending module, configured to perform step S303.

This application further provides a data processing apparatus. The apparatus may be integrated into the communications device <NUM> in the foregoing embodiment. For example, the apparatus may be integrated into the MAC chip of the communications device <NUM>, integrated into the processor, or integrated into a DSP chip. As shown in <FIG>, the apparatus includes a receiving module <NUM>, a synchronization module <NUM>, and an obtaining module <NUM>.

It can be learned from the foregoing embodiments that the receiving module <NUM> is configured to perform steps S204 and S304, the synchronization module <NUM> is configured to perform steps S205 and S305, and the obtaining module <NUM> is configured to perform steps S207 and S306.

The apparatus further includes an FEC encoding and decoding module <NUM>, configured to perform step S206.

This application further provides an optical line terminal. The optical line terminal includes the data processing apparatus in any one of the foregoing embodiments.

This application further provides an optical network unit. The optical network unit includes the data processing apparatus in any one of the foregoing embodiments.

This application further provides a PON system. The system includes the foregoing optical line terminal and optical network unit.

This application further provides a communications system. The system includes the foregoing communications devices. For example, the system includes the foregoing communications device used as the source network device and the communications device used as the target network device.

This application further provides a communications system. The system includes the first communications device, the OLT, the ONU, and the second communications device.

All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedure or functions according to the embodiments of this application are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, microwave, or the like) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), a semiconductor medium (for example, a solid-state drive Solid State Disk (SSD)), or the like.

Claim 1:
A data processing method, wherein the method comprises:
receiving S first data blocks at a physical coding sublayer, wherein S is a positive integer;
performing, at the physical coding sublayer, FEC encoding on the S first data blocks and first information to generate a check part, wherein the first information comprises code word synchronization information and operation, administration and maintenance, OAM, information;
generating a code word structure at the physical coding sublayer, wherein the code word structure comprises the S first data blocks, the first information, and the check part; and
sending the code word structure,
wherein
the first information further comprises second indication information, and the second indication information is used to indicate whether a receive end performs FEC decoding on the code word structure, and
the step of performing FEC encoding further comprises deleting an idle character being comprised in the first data blocks, wherein a length of the deleted idle character is the same as a length of the piece of first information.