Example 1:
 An embodiment of the present application provides a data processing method, device and system. This embodiment is based on figure 2 As an example, assume that ONU1, ONU2, and OTN1 are devices on the service sending side, and OTN2, ONU4, and ONU3 are devices on the service receiving side. It should be noted that this embodiment assumes that there is no bearer network between the ONU device and the OTN device. In the actual application process, any ONU device can be a sending or receiving device, and the corresponding OTN device is a sending or receiving device. Generally, ONU equipment and OTN equipment usually have the functions of sending and receiving service data at the same time.
 Figure 5 The steps that need to be performed for the data processing of the above equipment are given. The specific description is as follows:
 S501: Send multiple passive optical network (PON) upstream data frames;
 Specifically, ONU devices (for example: ONU1 and ONU2) first encapsulate the received customer data (for example, wireless service 1, wireless service 2, etc.) into a data frame for upstream transmission on the PON network. For example, in Gigabit PON (GPON), when the ONU device sends upstream data, the encapsulation of the service data stipulated by the standard adopts the Gigabit-capable passive optical network encapsulation method (GEM). For another example, a custom PON upstream data frame can be used, and this data frame needs to support the upstream time division burst mechanism in the PON. Then, the ONU device sends these uplink data frames carrying client data through pre-configured time slots. In GPON, this pre-configured time slot constitutes a pipe resource, which is also called a transmitter (ie T-CONT). To simplify the description, the following explanation is limited to the GPON data frame specified by the standard. However, in actual applications, this application does not limit the upstream data transmission format used by the ONU device, but only requires that the ONU device can use dedicated pipe resources and the PON upstream data frame format to send data. In other words, this PON upstream data frame can be customized, but the mechanism for sending the data frame is based on the time-division burst mechanism.
 It should be noted that the PON upstream data frame sent in this step is received by the OTN1 device. Specifically, for the receiving action of the OTN1 device, see Figure 4 The description of step S401 is not repeated here. In other possible implementation manners, the object sent in this step may be other network devices. For details, refer to the description of Embodiment 2-3, which will not be repeated here. Correspondingly, the data frame received by the OTN1 device is not necessarily a PON upstream data frame, but may also be a data frame of other formats, but the data frame of the other format carries the PON upstream data frame. In this embodiment, it is taken as an example that the data frame received by OTN1 is a PON upstream data frame.
 S502: Obtain a first data frame group according to the multiple PON upstream data frames;
 The subject of this step is the OTN1 device. Specifically, after receiving the uplink data frames sent by one or more ONU devices, the OTN1 device needs to group these data frames and allocate corresponding ODU pipeline resources for these data frame groups, so that the data frames carry Customer data can be transmitted in an end-to-end pipeline with guaranteed bandwidth. The advantage of this is that the transmission quality of customer data can be guaranteed, such as packet loss rate, delay, and reliability.
 This step follows Figure 4 The step S402 is similar. The OTN1 device can perform data grouping according to the time division pipeline identifier corresponding to the received PON upstream data frame. Specifically, the uplink data frames with the same time division pipeline identifier are grouped into a group, thereby obtaining one or more data frame groups. For example, for the upstream data frame sent by the ONU device supporting GPON, the OTN1 device can use the allocation identifier (alloc-ID) to distinguish. For other types of PON networks, OTN1 devices can also group according to other pipe resource identification information of the PON to ensure that data frames carrying the same customer data can be divided into the same group.
 In a possible implementation, the OTN1 directly uses the one or more data frame groups obtained above as the first data frame group. In another possible implementation, the OTN1 may further analyze the one or more data frame groups obtained above to obtain the first data frame group. For example, in a GPON network, GEM frames can be parsed and obtained as the first data frame group. For another example, customer data can be parsed, and the customer data frame can be regarded as the first data frame group.
 S503: Encapsulate the first data frame group into an optical transport network (OTN) data frame;
 This step follows Figure 4 The step S403 is similar. Specifically, the OTN1 device selects a suitable ODU data frame for the first data frame group, and encapsulates the data frame in the first data frame group into the ODU data frame. For example, if the service is Fast Ethernet (FE), and the bandwidth of the first data frame group is 100M, then the OTN1 device can select an OTN container of the corresponding bandwidth to carry it. For another example, if the service is two 4.5G wireless services, and the bandwidth of the first data frame group is 9G, then the OTN1 device can select ODUflex with a bandwidth of 9G as the bearer container.
 Optionally, the OTN1 device may also cross the first data frame group before encapsulating the first data frame group into the OTN data frame, so that the data frame group can be switched to a suitable output port for output. Specifically, the crossover may be a time division crossover or a space division crossover.
 S504: Send the OTN data frame;
 Specifically, the OTN1 device converts the OTN data frame into an appropriate OTN frame format and sends it out, for example, it can be converted into an OTU data frame, or a flexible OTN interface data frame (FlexO data frame).
 It should be noted that the OTN1 device sends the OTN data frame to another OTN2 device. This OTN2 device can be a new OTN device explained in this application or a traditional OTN device. In this embodiment, the object sent by the OTN1 device is a new OTN device (ie, OTN2 device) as an example.
 Optionally, the OTN1 device also has the function of sending bandwidth allocation information, so that the bandwidth resource information used by the ONU device can be configured. For example, the OTN1 device can allocate the time slot (or pipe) information used in the uplink transmission of data to its corresponding ONU devices (that is, ONU1 and ONU2). Specifically, the information includes at least a time division pipeline identifier, and the start and end position of the byte of the uplink data frame of the time division pipeline indicated by the time division pipeline identifier. It should be noted that the start and end positions can also be in units of bits or other granularity, and this application does not make any restrictions. For example, in GPON, the overhead of a standard downlink data frame can be used to send this bandwidth allocation information. It should be noted that bandwidth resource information sometimes becomes a bandwidth map. Those skilled in the art can know that the bandwidth map received by each ONU device is the same, and through this bandwidth map, each ONU device can obtain information about the time slot (or bandwidth resource) that it can use.
 Optionally, the OTN1 device may also receive external bandwidth adjustment information, and adjust the used ODU data frame according to this information to change the bandwidth size of the ODU data frame carrying the first data frame group. Furthermore, the OTN1 device can also adjust the bandwidth information of the ONU device accordingly to achieve end-to-end pipe bandwidth adjustment. In a possible implementation, this external bandwidth adjustment information may come from the controller or management system. In another possible implementation, this bandwidth adjustment information may come from the ONU device. Specifically, the bandwidth adjustment information (the calendar of bandwidth usage, that is, the bandwidth used in different time periods) can be delivered to the ONU device in advance. When the bandwidth changes, the ONU device can actively send a request message to the OTN device to request bandwidth adjustment. By coordinating the ODU data frame and the bandwidth change of the ONU device, end-to-end lossless adjustment can be realized. Taking the lossless adjustment method for the adjustment of the OTN pipe bandwidth as an example, if the increase in the bandwidth of the ONU device does not exceed the bandwidth of its corresponding ODU pipe, there is no need to adjust the ODU pipe bandwidth, only the bandwidth of the ONU device. If the increased bandwidth of the ONU device is greater than the bandwidth of the corresponding ODU pipe, the bandwidth of the ODU pipe needs to be adjusted first, and then the bandwidth of the ONU device. Similarly, if the bandwidth reduction of the ONU device does not exceed the minimum adjustment granularity of its corresponding ODU pipe (for example: 1.25G or 2.5G, or smaller), there is no need to adjust the ODU pipe bandwidth, only the bandwidth of the ONU device. If the bandwidth reduction of the ONU device is greater than the minimum adjustment granularity of the bandwidth of the corresponding ODU pipe, the bandwidth of the ONU device is adjusted first, and then the ODU pipe bandwidth is optionally adjusted.
 It should be noted that the object sent in this step is the OTN2 device. In other words, the OTN2 device directly or indirectly receives the OTN data frame sent from the OTN1 device. If it is, the OTN2 device is directly connected to the OTN1 device, and the data reception is direct. If the OTN2 device is connected to the OTN1 device as a network through other devices, then the data reception is indirect.
 S505: Parse multiple second data frames from the OTN data frame carrying the first data frame group;
 This step and the following two steps are executed by the OTN2 device. Specifically, after receiving the OTN data frame that carries the first data frame group, the OTN2 device parses out multiple second data frames from these data frames. Depending on the processing mode of the OTN1 device as the transmitting end, the format of the second data frame is different. For example, the data frame may be a corresponding frame format when the time slot indicated by T-CONT is transmitted. Or, the data frame is in the GEM format or the original client data format.
 S506: Encapsulate the data frames sent to the same destination device among the multiple second data frames into a PON downlink data frame;
 Specifically, depending on the format of the second data frame, the processing of the OTN2 device is different. If the second data frame is a frame format corresponding to T-CONT, the OTN2 device needs to terminate these data frames, and parse out multiple GEM frames from these data frames. Then, the OTN2 device encapsulates the GEM frames that need to be sent to the same destination device among multiple GEM frames into a PON downstream data frame. If the second data frame is a GEM frame, the OTN2 device directly encapsulates the data frames sent to the same destination address in these frames into the PON downstream data frame. If the second data frame is customer data, the OTN2 device needs to encapsulate these data frames into GEM frames first, and then send the GEM frames carrying these data frames to the same destination device and encapsulate them into PON downstream data frames. In other words, the OTN2 device needs to distinguish between the destination device that should receive the data frame and the format of the data frame itself. Then proceed to the next step.
 S507: Send the PON downlink data frame.
 The OTN2 device sends the PON downstream data frame generated in step S506. First of all, depending on different networking structures, the objects sent may be different. In this embodiment, OTN2 is directly sent to ONU equipment (for example: ONU3, ONU4). In other scenarios, such as the scenario described in Embodiment 2-3, the OTN2 device may be sent to other bearer network devices, which will not be repeated here. Secondly, OTN2 also needs to distinguish the destination PON equipment of the PON downstream data frame. In a possible implementation, it can be distinguished by the PON port. For example, in figure 2 In the OTN1 device, there are two ports for connecting the ONU device, one port is connected to two ONU devices, and the other port is connected to one ONU device. Then, OTN1 can distinguish the destination device that should send the data frame through the port number. In another possible implementation manner, it can be distinguished by the ONU identifier, or the ONU identifier and the PON port together. For example, in figure 2 In the OTN2 device, there are two ONU devices connected to the ONU, so they can be distinguished by the ONU device identifier. Or something like Figure 4 The description of step S402 in S402 can also be configured externally, and the OTN1 indirectly determines the sending destination device through other parameters. This application does not make any restrictions on how to distinguish data frames from different destination devices.
 After the ONU device as the receiving side receives the downlink data frame sent by the OTN2 device, it parses out the corresponding service data and sends it to the service destination device connected to it, thus completing the service transmission from the source device through the intermediate transmission network. The process of final delivery to the destination device.
 It should be noted that, optionally, the new OTN device disclosed in this application also needs to have ONU device activation, support operation, management, and maintenance messages to support the normal operation and management of the ONU device.
 The method provided in this embodiment adopts OTN equipment with new functions, so that the network can use the current low-cost ONU equipment to implement customer service access, thereby reducing the cost of customer service network construction. Optionally, the new type of OTN equipment may have bandwidth adjustment capabilities, which can realize end-to-end service bandwidth adjustment, thereby being able to meet the needs of dynamic changes in service bandwidth.
 It should be noted, Figure 5 Take OTN equipment as an example, but Figure 5 The described process also applies to FlexE equipment. The difference is that the OTN data frame needs to be replaced with a FlexE data frame. That is to say, the frame format of the carrier container used is different, so the corresponding data frame processing may be different. For example, before the business data is encapsulated into the FlexE frame, code block conversion processing may be required. Unless otherwise specified, the execution subject of the OTN device embodiment or the FlexE device embodiment mentioned in the following embodiments can be replaced.