Method for increasing bandwidth, and device

Abstract

Provided in the present application are a method for increasing a bandwidth, and a device. The method comprises: increasing the length of a first transmission frame, wherein the first transmission frame carries a data frame with a first bit rate; and after the length of the first transmission frame is increased, mapping a data frame with a second bit rate to the first transmission frame with the length increased, wherein the data frame with the second bit rate is transmitted after the data frame with the first bit rate, and the second bit rate is higher than the first bit rate. The length of a transmission frame is first increased, the bit rate of a data frame carrying service data is then adjusted, and the data frame with the bit rate adjusted is mapped to the transmission frame with the length increased, such that the reliability of transmitting the service data can be ensured when the bandwidth of the service data needs to be increased.

Description

Methods and devices for increasing bandwidth

[0001] This application claims priority to Chinese patent applications filed on December 13, 2024, with application number 202411855357.8, entitled "Method and Apparatus for Increasing Bandwidth", and on January 13, 2025, with application number 202510053330.5, also entitled "Method and Apparatus for Increasing Bandwidth", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of optical communication technology, and in particular to a method and apparatus for increasing bandwidth. Background Technology

[0003] Passive optical network (PON) is a fiber optic access technology that uses passive optical splitters to share optical signals among multiple users. PON systems offer advantages such as high bandwidth, low latency, and low maintenance costs, and are widely used in broadband access scenarios. With technological advancements and the surge in data traffic, small-granular pipeline technologies, such as optical service units (OSUs) and fine-grained optical transport networks (fgOTNs), which evolved from optical transport network (OTN) technology, are gradually being integrated into PONs to support various service types, such as video and voice data transmission. In this scenario, how to achieve lossless bandwidth adjustment when the bandwidth required by service data changes is a problem that needs to be solved. Summary of the Invention

[0004] This application provides a method and device for increasing bandwidth, which can achieve lossless bandwidth increase when packet service traffic increases in a network system carrying fgOTN via PON, thereby ensuring the reliability of service data transmission.

[0005] Firstly, a method for increasing bandwidth is provided, which can be performed by a first device or by a component of the first device (e.g., a chip, circuit, or chip system). The following description assumes that the method is performed by the first device.

[0006] The method includes: increasing the length of a first transmission frame, the first transmission frame carrying a data frame at a first bit rate; and after the length of the first transmission frame is increased, mapping a data frame at a second bit rate onto the first transmission frame after the length increase, the data frame at the second bit rate being transmitted after the data frame at the first bit rate, the second bit rate being higher than the first bit rate.

[0007] Based on the above scheme, when the bandwidth of service data needs to be increased, the reliability of service data transmission can be guaranteed by first increasing the length of the transmission frame, then adjusting the bit rate of the data frame carrying the service data, and mapping the data frame with the adjusted bit rate onto the transmission frame with the increased length.

[0008] In some implementations of the first aspect, a first bandwidth increase request message is received from an upstream OTN device, the first bandwidth increase request message instructing the first device to increase bandwidth; a second bandwidth increase request message is sent to a customer premises equipment (CPE), the second bandwidth increase request message instructing the CPE to increase bandwidth.

[0009] In some implementations of the first aspect, the second bandwidth increase request message can be implemented via the optical network terminal management and control interface (OMCI) protocol.

[0010] In some implementations of the first aspect, a bandwidth increase response message is received from the CPE; the length of the first transmission frame is increased based on the bandwidth increase response message.

[0011] In some implementations of the first aspect, the bandwidth increase response message can be implemented via the OMCI protocol.

[0012] In some implementations of the first aspect, a bandwidth increase indication is detected; based on the bandwidth increase indication, an OTN frame received from the upstream OTN device is demapped to obtain a data frame with the second bit rate.

[0013] In some implementations of the first aspect, the first device is a convergence node.

[0014] Based on the above scheme, when the bandwidth of service data needs to be increased during downlink data transmission, the length of the transmission frame is increased by the aggregation node, the bit rate of the data frame carrying the service data is adjusted, and the data frame with the adjusted bit rate is mapped to the transmission frame with the increased length. This can ensure the reliability of downlink service data transmission.

[0015] In some implementations of the first aspect, a bandwidth allocation message is received from an OTN device, which instructs the first device to use new bandwidth resources; and the length of the first transmission frame is increased based on the bandwidth allocation message.

[0016] In some implementations of the first aspect, a third bandwidth increase request message is received from the OTN device; a bandwidth increase indication is sent based on the third bandwidth increase request message.

[0017] In some implementations of the first aspect, the third bandwidth increase request message can be implemented via the OMCI protocol.

[0018] In some implementations of the first aspect, after sending the bandwidth increase indication, the data frame with the second bit rate is mapped to the first transmission frame after the length increase.

[0019] In some implementations of the first aspect, the first device is an access node.

[0020] Based on the above scheme, when the bandwidth of the service data needs to be increased during uplink data transmission, the access node first increases the length of the transmission frame, then adjusts the bit rate of the data frame carrying the service data, and maps the data frame with the adjusted bit rate onto the transmission frame with the increased length. This can ensure the reliability of uplink service data transmission.

[0021] In some implementations of the first aspect, the data frame is an fgODUflex frame or an OSU frame, and the first transmission frame is a PON frame.

[0022] Secondly, a device for increasing bandwidth is provided. The device for increasing bandwidth can be a first device or a component of the first device (e.g., a chip, circuit, or chip system). The device can have the functions described in the first aspect. For example, the device includes modules, units, or means corresponding to the operations involved in the first aspect. The modules, units, or means can be implemented by software or hardware, or by a combination of software and hardware.

[0023] The device includes a processing module for increasing the length of a first transmission frame carrying a data frame at a first bit rate; the processing module is also configured to map a data frame at a second bit rate onto the first transmission frame after the length increase is completed, the data frame at the second bit rate being transmitted after the data frame at the first bit rate, the second bit rate being higher than the first bit rate.

[0024] In some implementations of the second aspect, the device further includes a transceiver module for receiving a first bandwidth increase request message from an upstream optical transport network (OTN) device, the first bandwidth increase request message instructing the first device to increase bandwidth; the transceiver module is also used to send a second bandwidth increase request message to a CPE, the second bandwidth increase request message instructing the CPE to increase bandwidth.

[0025] In some implementations of the second aspect, the second bandwidth increase request message can be implemented via the OMCI protocol.

[0026] In some implementations of the second aspect, the transceiver module is also used to receive a bandwidth increase response message from the CPE; the processing module is specifically used to increase the length of the first transmission frame based on the bandwidth increase response message.

[0027] In some implementations of the second aspect, the bandwidth increase response message can be implemented via the OMCI protocol.

[0028] In some implementations of the second aspect, the processing module is further configured to detect a bandwidth increase indication; specifically, the processing module is configured to demap the optical transport network OTN frame received from the upstream OTN device based on the bandwidth increase indication to obtain the data frame at the second bit rate.

[0029] In some implementations of the second aspect, the device is a convergence node.

[0030] In some implementations of the second aspect, the transceiver module is further configured to receive a bandwidth allocation message from an OTN device, the bandwidth allocation message instructing the first device to use new bandwidth resources; the processing module is specifically configured to increase the length of the first transmission frame based on the bandwidth allocation message.

[0031] In some implementations of the second aspect, the transceiver module is further configured to receive a third bandwidth increase request message from the OTN device; the processing module is specifically configured to send a bandwidth increase indication based on the third bandwidth increase request message.

[0032] In some implementations of the second aspect, the third bandwidth increase request message can be implemented via the OMCI protocol.

[0033] In some implementations of the second aspect, the processing module is specifically used to map the second bit rate data frame to the first transmission frame after the length increase following the transmission of the bandwidth increase indication.

[0034] In some implementations of the second aspect, the device is an access node.

[0035] In some implementations of the second aspect, the data frame is an fgODUflex frame or an OSU frame, and the first transmission frame is a PON frame.

[0036] Thirdly, an apparatus for increasing bandwidth is provided. This apparatus is used to perform the method provided in the first aspect. Specifically, the apparatus may include units and / or modules for performing the method provided in the first aspect or its implementations, such as a processing module and a transceiver module.

[0037] In one implementation, the device is a convergence node. The processing module can be at least one processor; the transceiver module can be a transceiver, or an input / output interface. The transceiver can be a transceiver circuit, and the input / output interface can be an input / output circuit.

[0038] In another implementation, the device is a chip, chip system, or circuit in the aggregation node. The transceiver module can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit. The processing module can be at least one processor, processing circuit, or logic circuit.

[0039] Fourthly, a processor is provided for executing the methods provided in the above aspects.

[0040] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0041] Fifthly, a computer-readable storage medium is provided. This computer-readable storage medium stores program code for execution by a device, the program code including methods for performing the methods provided in the first aspect or its implementations described above.

[0042] Sixthly, a computer program product containing instructions is provided. When the computer program product is run on a computer, it causes the computer to perform the method provided in the first aspect or its implementation.

[0043] In a seventh aspect, a chip is provided, comprising a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided in the first aspect or its implementation thereof. The communication interface can be implemented in hardware or software.

[0044] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to perform the method provided by the first aspect or its implementation described above.

[0045] When the method provided in this application is executed by a chip, this application does not limit the specific number of chips implementing the method. For example, it can be executed by one chip, or by two or more chips. Furthermore, when the number of chips implementing the method is two or more, the chip manufacturers are not limited; they can be from the same manufacturer or different manufacturers.

[0046] Eighthly, a network device is provided, comprising: a processor and an input / output interface for performing the method provided in the first aspect or its implementation thereof, wherein the input / output interface is used to send and receive the data frame and the first transmission frame, and the processor is used to process the data frame and the first transmission frame.

[0047] A ninth aspect provides an optical module comprising: a signal processor and an optical transmitting component, wherein the signal processor executes the method provided in the first aspect or its implementation thereof; and the optical transmitting component is configured to convert a first transmission frame into an optical signal and transmit the optical signal.

[0048] In a tenth aspect, a communication system is provided, comprising at least one of the means described in the third and fourth aspects above.

[0049] The beneficial effects of the second to tenth aspects mentioned above can be referred to in the description of the beneficial effects in the first aspect, and will not be repeated here. Attached Figure Description

[0050] Figure 1 is a schematic diagram of the architecture of a PON system applicable to this application.

[0051] Figure 2 is a schematic diagram of a PON system applicable to this application.

[0052] Figure 3 is a structural schematic diagram of an OTN device 300 applicable to this application.

[0053] Figure 4 is a schematic flowchart of a bandwidth increase method 400 provided in this application.

[0054] Figure 5 is a schematic diagram of a process for increasing bandwidth provided in this application.

[0055] Figure 6 is a schematic flowchart of a bandwidth increase method 600 provided in this application.

[0056] Figure 7 is a schematic flowchart of a bandwidth increase method 700 provided in this application.

[0057] Figure 8 is a schematic block diagram of a device 1000 for processing service signals provided in this application.

[0058] Figure 9 is a structural schematic diagram of a device 2000 for processing service signals provided in this application.

[0059] Figure 10 is a schematic diagram of a chip system 3000 provided in this application.

[0060] Figure 11 is a structural schematic diagram of a system 4000 provided in this application.

[0061] Figure 12 is a schematic diagram of an XGEM frame carrying first information provided in this application. Detailed Implementation

[0062] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0063] The following description is provided to facilitate understanding of the embodiments of this application.

[0064] First, the first, second, and various numerical designations (e.g., "#1", "#2", etc.) shown in this application are merely for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages or different devices, rather than to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0065] Second, the terms “comprising” and “having” and any variations thereof in the embodiments of this application shown below are intended to cover non-exclusive inclusion, for example, a system, product or device that includes a series of units is not necessarily limited to those units that are explicitly listed, but may include other units that are not explicitly listed or that are inherent to such products or devices.

[0066] Third, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or descriptions. Embodiments or designs described as "exemplarily" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. The use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0067] Fourth, unless otherwise specified, all terms used in this application (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains.

[0068] Fifth, this application's embodiments use the mapping of fine-grained flexible optical data units (fgODUflex) to 10 Gigabit Passive Optical Network (XGSPON) encapsulation mode (XGEM) as an example for illustration, but the solution of this application is not limited to this. The fgODUflex frame can also be called fgODU or fgODU frame. The bandwidth increase method provided in this application can also be applied to PON systems such as 25GPON, 50GPON, and beyond 50GPON. The bandwidth increase method provided in this application can also be extended to frame structures of other small-grained protocols, such as OSU (also called OSU frame, OSU data frame, or flexible optical service unit, OSUflex), realizing the application of the bandwidth increase method provided in this application in OSU over PON systems.

[0069] Sixth, the technical solution of this application is applicable to PON systems, especially representative Gigabit Passive Optical Networks (GPON) and Ethernet Passive Optical Networks (EPON), XG(S)-PON (10G (symmetric) Passive Optical Network), 10G EPON (10G Ethernet Passive Optical Network), 25G EPON, 40G EPON, 50G EPON, and 100G EPON. Among these, XG(S)-PON, 10G EPON, 25G EPON, 40G EPON, 50G EPON, and 100G EPON can be collectively referred to as 10G PON, or XGPON. It should be understood that the solution provided in this application is not limited to PON systems; that is, the solution of this application can be applied to point-to-multipoint optical networks. This application only uses a PON network as an example for illustration.

[0070] Seventh, in this application, "instruction" may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0071] Figure 1 is a schematic diagram of the architecture of a PON system 100 provided for embodiments of this application. As shown in Figure 1, the PON system 100 includes an optical line termination (OLT) 104, an optical distribution network (ODN) 102, and an optical network unit (ONU) or optical network terminal (ONT) 101.

[0072] The OLT 104 provides network-side interfaces. It connects to upper-layer network-side devices (such as switches, routers, and optical transmission equipment) and lower-layer devices (such as ODN 102). The OLT 104 is typically located in the center office (CO).

[0073] The ONU / ONT 101 is located in or near the user's home. The ONU provides a user-side interface and is also connected to the ODN 102. If the ONU also provides user interface functionality, such as an Ethernet user interface or a plain old telephone service (POTS) user interface, it is called an ONT.

[0074] ODN 102 is a passive optical splitter. The ODN consists of three parts: a passive optical splitter (Splitter) 102-2, a trunk fiber 106, and branch fibers 107. In a PON system, ODN 102 splits a single fiber into multiple paths, with ONUs / ONTs sharing the bandwidth.

[0075] In the PON system 100, the transmission direction from OLT 104 to ONU / ONT 101 is called downlink, and the transmission direction from ONU / ONT 101 to OLT 104 is called uplink. During uplink service transmission, ONU / ONT 101 uses time division multiplexing (TDM) for access. The principle of TDM is to divide the uplink transmission time into several time slots Ti (i = 1, 2, 3, ..., 32, ...). Within each time slot, only one ONU / ONT 101 is scheduled to send data to OLT 104 in packets, and each ONU / ONT 101 sends data sequentially according to the order specified by OLT 104. TDM requires the OLT 104 to determine the distance to each ONU / ONT 101 and then strictly time the transmission of each ONU / ONT 101. Each ONU / ONT 101 obtains timing information from the downlink signal sent by the OLT 104 and transmits uplink packet data within the time slots specified by the OLT 104 to avoid conflicts between ONU / ONT 101. That is, each ONU / ONT 101 can only transmit its own uplink data in the time slots allocated by the OLT 104. During downlink service transmission, the OLT 104 broadcasts service data to each ONU / ONT 101. The ODN 102 transmits the downlink data from the OLT 104 to each ONU / ONT 101, and simultaneously aggregates the uplink data from multiple ONU / ONT 101s and transmits it to the OLT 104.

[0076] Figure 2 is a schematic diagram of a PON system applicable to this application. As shown in Figure 2, the ONU 210 (there may be multiple ONUs, but only one is shown in the figure) communicates with the optical splitter 220 and the OLT 230.

[0077] The ONU 210 includes an OTN Framer 216, an ONU media / medium access control (MAC) 211, an ONU physical layer (PHY) 212, a laser 213, and a photodetector 214.

[0078] In the transmission direction, the OTN Framer 216 can map (or encapsulate) service data to an OTN signal, and can also map the OTN signal to a PON signal (e.g., GEM or Gigabit Passive Optical Network transmission convergence (GTC)). For example, the OTN Framer 216 maps an OTN frame to a first transmission frame, which is a GEM frame. Optionally, the OTN Framer 216 maps the first transmission frame to a second transmission frame, which is a GTC frame. Alternatively, in some scenarios, when the OTN Framer 216 maps service data to an OTN signal, the ONU MAC 211 implements the mapping of the OTN signal to a PON signal. For example, the ONU MAC 211 maps the OTN frame to the first transmission frame. As another example, the ONU MAC 211 also maps the first transmission frame to the second transmission frame. For example, the OTN frame 216 can be used to map the OTN signal to the first transmission frame, and the ONU MAC 211 can be used to map the first transmission frame to the second transmission frame. Alternatively, in some scenarios, the ONU MAC 211 can also be used to map service data to the OTN signal and the OTN signal to the PON signal. The ONU MAC 211 can send service data to the ONU optical PHY 212. The ONU optical PHY 212, also known as the driver for the laser 213, can be used to drive the laser to generate optical signals according to the instructions of the ONU MAC 211. Under the control of the ONU optical PHY 212, the laser 213 modulates the service data into the optical signal and sends the uplink optical signal carrying the service data to the OLT 230 through the optical fiber.

[0079] In the receiving direction, photodetector 214 receives the downlink optical signal from OLT 230 and converts it into an electrical signal. ONU optical PHY 212 transmits the electrical signal.

[0080] The ONU MAC 211 parses the electrical signal to obtain the PON signal. The OTN Framer 216 demaps the PON signal to an OTN signal. For example, the ONU MAC 211 parses the electrical signal to obtain a first transmission frame; the OTN Framer 216 demaps the OTN frame from the first transmission frame. As another example, the ONU MAC 211 parses the electrical signal to obtain a second transmission frame; the OTN Framer 216 demaps the first transmission frame from the second transmission frame and demaps the OTN frame from the first transmission frame. Alternatively, in some scenarios, the ONU MAC 211 parses the electrical signal to obtain the PON signal and demaps the PON signal to an OTN signal. For example, the ONU MAC 211 parses the electrical signal to obtain the first transmission frame, and demaps the OTN frame from the first transmission frame. As another example, the ONU MAC 211 parses the electrical signal to obtain the second transmission frame, demaps the first transmission frame from the second transmission frame, and demaps the OTN frame from the first transmission frame; or, in some scenarios, the OTN framer 216 parses the electrical signal to obtain the PON signal, and demaps the PON signal to an OTN signal. The ONU 210 may also include a wavelength division multiplexer 215 for transmitting the uplink optical signal generated by the laser 213 into the optical fiber, and for transmitting the downlink optical signal received from the optical fiber into the photodetector 214.

[0081] The OLT 230 includes an OTN Framer 237, an OLT MAC 231, a signal processing module 232, an OLT optical PHY 233, a photodetector 234, and a laser 235.

[0082] In the receiving direction, photodetector 234 receives the uplink optical signal from ONU 210 and converts it into an electrical signal. This electrical signal can be an analog electrical signal or a digital electrical signal. Signal processing module 232 can be implemented using analog devices (such as amplifiers) or digital devices (such as digital signal processors), thus it can perform correlation processing on analog or digital electrical signals. OLT MAC 231 analyzes the electrical signal processed by signal processing module 232 to obtain the PON signal. OLT MAC 231 can also demap the PON signal to an OTN signal. For example, OLT MAC 231 analyzes the electrical signal to obtain a first transmission frame and demaps the OTN frame from the first transmission frame. For example, the OLT MAC 231 parses the electrical signal to obtain a second transmission frame, and demaps the first transmission frame from the second transmission frame, as well as demaps the OTN frame from the first transmission frame; or, in some scenarios, when the OLT MAC 231 parses the PON signal, the OTN Framer 237 demaps the PON signal into an OTN signal. For example, the OLT MAC 231 parses the first transmission frame, and the OTN Framer 237 demaps the OTN frame from the first transmission frame. For another example, the OLT MAC 231 parses the second transmission frame, and the OTN Framer 237 demaps the first transmission frame from the second transmission frame, as well as demaps the OTN frame from the first transmission frame. For example, the OLT MAC 231 parses the electrical signal to obtain the second transmission frame, and demaps the first transmission frame from the second transmission frame, and the OTN Framer 237 demaps the OTN frame from the first transmission frame; or, in some scenarios, the OTN Framer 237 parses the electrical signal passed through the signal processing module 232 to obtain the PON signal, and demaps the PON signal into an OTN signal.

[0083] In the transmission direction, the OTN Framer 237 can map (or encapsulate) service data to an OTN signal, and can also map (or encapsulate) an OTN signal to a PON signal (e.g., GEM or GTC). For example, the OTN Framer 237 maps an OTN frame into a first transmission frame. As another example, the OTN Framer 237 maps an OTN frame into a first transmission frame, and then maps that first transmission frame into a second transmission frame. Alternatively, in some scenarios, where the OTN Framer 237 maps (or encapsulates) service data to an OTN signal, the OLT MAC 231 performs the mapping (or encapsulation) of the OTN signal to a PON signal. The OLT MAC 231 generates service data. The signal processing module 232 performs analog or digital correlation processing on the service data. Under the control of the OLT optical PHY 233, the laser 235 modulates the service data into an optical signal and transmits the downlink optical signal carrying the service data to the ONU 210 via optical fiber. The OLT 230 may also include a wavelength division multiplexer 236 for transmitting downlink optical signals generated by the laser 235 into the optical fiber, and for transmitting uplink optical signals received from the optical fiber into the photodetector 234.

[0084] Figure 3 is a schematic diagram of a possible hardware structure of an OTN device 300 applicable to this application. The OTN device 300 shown in Figure 3 can communicate with an OLT device in a PON system. The OLT device can send messages from the ONU device to the OTN device 300, and then forward them to the ONU at the other end via another OTN device. The OLT device can also receive messages sent by the OTN device 300 and send the received messages to the ONU device through the ODN network. The OTN can serve as the bearer network for PON, which can improve the transmission distance of PON services or provide better service protection.

[0085] As shown in Figure 3, the OTN device 300 may include a tributary board 301, a cross-connect board 302, a line board 303, an optical layer processing board (not shown in the figure), and system control and communication boards 304. Depending on specific needs, the type and number of boards included in the OTN device 300 may vary. For example, an OTN device acting as a core node may not include the tributary board 301. Conversely, an OTN device acting as an edge node may have multiple tributary boards 301, or no optical cross-connect board 302. Furthermore, an OTN device that only supports electrical layer functions may not have an optical layer processing board.

[0086] Tributary board 301, cross-connect board 302, and line board 303 can be used to process OTN electrical layer signals. Tributary board 301 is used to receive and transmit various customer services, such as Synchronous Digital Hierarchy (SDH) services, packet services, Ethernet services, and fronthaul services. Further, tributary board 301 can be divided into a customer-side optical transceiver module and a signal processor. The customer-side optical transceiver module, also called an optical transceiver, is used to receive and / or transmit service data. The signal processor is used to perform mapping and demapping processing of service data to data frames. Cross-connect board 302 is used to switch data frames, completing the exchange of one or more types of data frames. Line board 303 is mainly used to process line-side data frames. Specifically, line board 303 can be divided into a line-side optical module and a signal processor. The line-side optical module, also called an optical transceiver, is used to receive and / or transmit data frames. The signal processor is used to perform multiplexing and demultiplexing, or mapping and demapping processing of line-side data frames. System control and communication board 304 is used to implement system control. Specifically, it can collect information from different boards or send control commands to the corresponding boards.

[0087] It should be noted that, unless otherwise specified, a specific component (such as a signal processor) may be one or more, and this application does not impose any restrictions. It should also be noted that this application does not impose any restrictions on the type of boards included in the OTN device, or on the functional design and number of those boards. In a specific implementation, the two boards mentioned above may also be designed as a single board. Furthermore, the OTN device may also include a backup power supply, a fan for heat dissipation, etc.

[0088] Currently, fgODUflex can support end-to-end transmission of small-granularity services at the 10 Mbps rate level. Combining fgODUflex with a PON system, within the PON system's ODN-based P2MP tree network structure, and utilizing the existing PON optical distribution network, allows for the application of fgODUflex in P2MP scenarios. In an fgOTN over PON system, when branch end nodes and central office nodes in the P2MP system transmit data, OTN frames carrying service data at different rates can be mapped to GEM frames of different lengths to achieve OTN frame transmission in the PON system. Taking OTN frames as fgODUflex frames and PON frames as XGEM frames as an example, Table 1 shows the correspondence between fgODUflex frames of different rates and XGEM frame lengths. An fgODUflex frame can also be represented as fgODUflex(p), which can be divided into p rate levels, for example, p = 119. When p=1, the rate of fgODUflex(1) is the minimum, which is 10.4092031 Mbit / s. This rate can also be regarded as the reference rate of the fgODUflex frame. When p=n, the rate of fgODUflex(n) is n×10.4092031 Mbit / s.

[0089] Table 1

[0090] When the service data is packet-based, the traffic volume is unpredictable, requiring bandwidth adjustments at different times to accommodate varying traffic levels. Therefore, in an fgOTN over PON system, a key challenge is how to increase bandwidth to ensure reliable data transmission as packet traffic increases.

[0091] In view of this, this application provides a method and device for increasing bandwidth, which can achieve lossless bandwidth increase in an fgOTN over PON system and ensure the reliability of service data transmission.

[0092] Figure 4 is a schematic flowchart of a bandwidth enhancement method 400 provided in this application. Method 400 can be executed by a first device, or by a module or unit within the first device, such as a chip, chip system, or processor that supports the methods implemented by the first device. The method may include the following steps.

[0093] S410, increase the length of the first transmission frame, which carries a data frame at the first bit rate.

[0094] S420, after the length of the first transmission frame has been increased, the data frame with the second bit rate is mapped to the first transmission frame after the length has been increased.

[0095] In this application, the data frame can be used to carry business data.

[0096] The service data can be packet (PKT) service, which can also be called OTN service, Ethernet service, packet service, or Internet Protocol (IP) service, without limitation.

[0097] The data frame can be an OTN frame. For example, an OTN frame can be fgODUflex or OSU, etc. fgODUflex can also be called fgODUflex frame, fgODUflex data frame, fgODUflex signal, etc. Similarly, OSU can also be called OSU frame, OSU data frame, OSU signal, etc.

[0098] OTN frames can correspond to different bit rate levels. Taking the OTN frame as an example, the fgODUflex frame can also be represented as fgODUflex(p), indicating that the fgODUflex frame can be divided into p bit rate levels. This application does not limit the value of p; for example, referring to Table 1, p can take any value from 1 to 119. For example, when p = n, the bit rate of fgODUflex(n) can be n × 10.4092031 Mbit / s.

[0099] In this application, "bit rate" can be replaced with "bit rate" or "rate" without limitation. The bit rate of a data frame can sometimes also be understood as the bandwidth of the data frame.

[0100] The first transmission frame can refer to a data frame in the transport layer. This data frame in the transport layer can be a PON frame.

[0101] In this application, the PON frame can be an XGEM frame, a GEM frame of other rates, or a transmission frame that has the same or similar function as a GEM frame in a future PON system, etc., without limitation.

[0102] This PON frame can be used to carry OTN frames. It can be understood that OTN frames are used to carry service data. After the service data is mapped into the OTN frame, the OTN frame still needs to be mapped to the transport layer. For example, in an fgOTN over PON system, the OTN frame used to carry service data is fgODUflex. After the service data is mapped to fgODUflex, fgODUflex is then mapped to an XGEM frame.

[0103] In this application, the length (or size) of the transmission frame can be characterized by the number of bytes (or bits) of a specific length included in the transmission frame (or the payload area of ​​the transmission frame); or, the length of the transmission frame is related to the value of M, which can be understood as the number of bytes (or bits) of a specific length included in the transmission frame when the transmission frame is divided into bytes (or bits) of a specific length, and M is a positive integer.

[0104] The specified length of bytes (or bits) can be represented as X bytes or Y bits, where X and Y are positive integers. The specific values ​​of X and Y are not limited; for example, when the specified length is X bytes, X can be 8, 16, 32, etc.; Y = 8 * X, or the value of Y corresponds to a non-integer number of bytes. The unit of this specified length being bytes or bits is merely an example; the unit can also be multiple bytes or multiple bits, without limitation.

[0105] Taking a specific length of 16 bytes as an example, before increasing the length of the first transmission frame, the first transmission frame can contain m1 16-byte segments, or in other words, the length of the first transmission frame can be represented by m1, where m1 is a positive integer. These m1 16-byte segments are used to map the data frame at the first bit rate. After increasing the length of the first transmission frame, the first transmission frame can contain m2 16-byte segments, or in other words, the increased length of the first transmission frame can be represented by m2, where m2 is a positive integer, and m2 is greater than m1. For ease of explanation, the length of the first transmission frame before the length increase will be referred to as the first length, and the length of the first transmission frame after the length increase will be referred to as the second length.

[0106] In S410, the first transmission frame carrying the data frame at the first bit rate can be understood as the first transmission frame of the first length carrying the data frame at the first bit rate. That is, before increasing the length of the first transmission frame, the first device maps the data frame at the first bit rate to the first transmission frame of the first length; when bandwidth needs to be increased, the length of the first transmission frame is first increased from the first length to the second length; after the length of the first transmission frame is increased, the data frame at the second bit rate is then mapped to the data frame of the second length.

[0107] The first length can correspond to the first bit rate, and the second length can correspond to the second bit rate. For example, the correspondence between the first length and the first bit rate, and the correspondence between the second length and the second bit rate are each any row in Table 1.

[0108] Figure 5 shows a specific example of the process of increasing bandwidth in this application. As shown in Figure 5, taking the data frame as fgODUflex, the first transmission frame as XGEM, and the bandwidth increasing from 50Mbps to 100Mbps as an example, before increasing the bandwidth, fgODUflex(5) is mapped to an XGEM with a length of 8*16 bytes, that is, the first bit rate is the bit rate corresponding to fgODUflex(5); when it is necessary to increase the bandwidth, the length of the XGEM is first increased to 14*16 bytes; then fgODUflex(10) is mapped to the XGEM with a length of 14*16 bytes, that is, the second bit rate is the bit rate corresponding to fgODUflex(10). The bit rates corresponding to fgODUflex(5) and fgODUflex(10) can be referred to Table 1.

[0109] This application does not limit the specific method of mapping a data frame of a specific bit rate to a transmission frame of a specific length. For example, a data frame of a specific bit rate can be mapped to the payload of a transmission frame of a specific length using a generic mapping procedure (GMP). The transmission frame of a specific length may also include justification control (JC) overhead (OH) and header (HD) (i.e., the overhead of the transmission frame) generated during the mapping process.

[0110] In one example, method 400 is applied to downlink data transmission. In downlink data transmission, the first device can be a central office node in a point-to-multipoint (P2MP) system, such as an OLT device (also called an aggregation node) in a PON system. The following uses the example of the first device being an aggregation node to illustrate the application of method 400 in downlink data transmission.

[0111] For example, when it is determined that the bandwidth of the service data needs to be increased, the aggregation node increases the length of the first transmission frame. In one possible implementation, when the upstream OTN device determines that the bandwidth of the service data needs to be increased, the upstream OTN device sends a bandwidth increase request message #1 (an example of a first bandwidth increase request message) to the aggregation node to request the aggregation node to increase the bandwidth; accordingly, the aggregation node receives the bandwidth increase request message #1, and after receiving the bandwidth increase request message #1, increases the length of the first transmission frame, that is, sets the length of the first transmission frame to the second length. For example, the bandwidth increase request message #1 is a fine-grained link connection resizing (fgLCR) request message.

[0112] Optionally, after receiving the bandwidth increase request message #1, the aggregation node sends a bandwidth increase request message #2 (second bandwidth increase request message) to the second device. This bandwidth increase request message #2 instructs the second device to increase bandwidth, or in other words, instructs the second device to process (e.g., demap) the first transmission frame with an increased length. Correspondingly, the aggregation node receives a bandwidth increase response message #2 from the second device. The aggregation node can increase the length of the first transmission frame after receiving the bandwidth increase response message #1. The second device can be a branch end node in a P2MP system, for example, an ONU device in a PON system or an internal component of an ONU device, such as a customer premises equipment (CPE).

[0113] In other words, during downlink data transmission, the aggregation node can increase the length of the first transmission frame after receiving the bandwidth increase request message #1 or the bandwidth increase response message #2. At this time, the bit rate of the data frame carrying the service data can remain unchanged, for example, the first bit rate.

[0114] For example, this second length corresponds to the increased bandwidth of the service data bandwidth. That is, the aggregation node can determine the length of the second transmission frame through the increased bandwidth of the service data bandwidth. For example, the bandwidth required by the service data is indicated by the bandwidth increase request message #1.

[0115] Optionally, after receiving the bandwidth increase response message #2, the aggregation node sends a bandwidth increase response message #1 to the upstream OTN device. For example, the bandwidth increase response message #1 is an fgLCR response message. This application does not limit the execution order of the aggregation node sending the bandwidth increase response message #1 and increasing the length of the first transmission frame. For example, the aggregation node can first increase the length of the first transmission frame and then send the bandwidth increase response message #2, or the two steps can be performed simultaneously.

[0116] After the length of the first transmission frame is increased, the aggregation node maps the second bit rate data frame to the first transmission frame after the length increase.

[0117] In one possible implementation, the aggregation node detects a bandwidth increase indication sent by the upstream OTN device and, upon detecting the bandwidth increase indication, maps the second bit rate data frame onto the second length first transmission frame. For example, after receiving the bandwidth increase response message #1, the upstream OTN device sends the bandwidth increase indication to instruct the aggregation node to increase bandwidth.

[0118] For example, the bandwidth increase indication can indicate the location where the bit rate of the data frame is increased. The bandwidth increase indication can be carried within the data frame carrying service data, for example, in the overhead area of ​​data frame #1. That is, before the specific location of data frame #1, the bit rate of the data frame carrying service data is a first bit rate, and the aggregation node maps this first bit rate data frame to the second length of the first transmission frame; after the specific location of data frame #1, the bit rate of the data frame carrying service data is a second bit rate, and the aggregation node maps this second bit rate data frame to the second length of the first transmission frame. For example, if the data frame is fgODUflex, the specific location is the boundary between the 1904th and 1905th bytes of the 3rd row of the fgODUflex frame structure. That is, before the 1904th byte of the 3rd row, the bit rate of fgODUflex is the first bit rate, and starting from the 1905th byte of the 3rd row, the bit rate of fgODUflex is the second bit rate.

[0119] In another possible implementation, the aggregation node adaptively maps data frames with a second bit rate to the first transmission frame of the second length based on changes in the bit rate of the buffered data frames. That is, the upstream OTN device adjusts the bit rate of the data frame from the first bit rate to the second bit rate. The aggregation node receives and buffers the data frames sent by the upstream OTN device and adaptively maps data frames with different bit rates to the first transmission frame of the second length. For example, after receiving the bandwidth increase response message #1, the upstream OTN device sends the bandwidth increase indication, and after sending the bandwidth increase indication, adjusts the bit rate of the data frame from the first bit rate to the second bit rate at the specific position indicated by the bandwidth increase indication.

[0120] In another example, method 400 is applied to uplink data transmission. In uplink data transmission, the first device can be a branch end node (also called an access node) in a P2MP system, such as an ONU device in a PON system or an internal component of an ONU device, for example, a CPE. The following uses the example of the first device as the end node to illustrate the application of method 400 in uplink data transmission.

[0121] For example, if it is determined that the bandwidth of the business data needs to be increased, the end node increases the length of the first transmission frame.

[0122] In a first possible implementation, the aggregation node determines that the bandwidth for the service data needs to be increased and sends a bandwidth allocation message to the end nodes. This bandwidth allocation message instructs the end nodes to use the new bandwidth resources. Accordingly, the end nodes receive the bandwidth allocation message and, based on the message, increase the length of the first transmission frame, setting it to a second length. Here, the bandwidth allocation message is a bandwidth map (BWMAP), indicating the bandwidth resources allocated to multiple end nodes, including the aforementioned end nodes.

[0123] That is, during uplink data transmission, upon receiving the bandwidth allocation message, the end node increases the length of the first transmission frame. At this time, the bit rate of the data frame carrying the service data may remain unchanged, for example, it may remain at the first bit rate.

[0124] Optionally, after sending the bandwidth allocation message, the aggregation node sends a bandwidth request message #3 (an example of a third bandwidth increase request message) to the end node to instruct the end node to increase the bandwidth. Accordingly, the end node receives the bandwidth increase request message #3 and, upon receiving the bandwidth increase request message #3, maps the second bit rate data frame onto the first transmission frame after the length increase.

[0125] For example, when it is determined that the bandwidth of the service data needs to be increased, the aggregation node sends a bandwidth increase request message #4 to the upstream OTN device to instruct the upstream OTN device to increase the bandwidth. The aggregation node receives a bandwidth increase response message #4 from the upstream OTN device, and after receiving the bandwidth increase response message #4, sends the bandwidth increase request message #3 to the end node. For example, the bandwidth increase request message #4 is an fgLCR request message, and the bandwidth increase response message #4 is an fgLCR response message.

[0126] In one possible implementation, after receiving the bandwidth increase request message #3, the end node sends a bandwidth increase indication and adjusts the bit rate of the data frame to a second bit rate at a specific location indicated by the bandwidth increase indication. The end node then maps this second bit rate data frame onto the first transmission frame of the second length. The bandwidth increase indication can be referred to in the description above.

[0127] That is, in uplink data transmission, after receiving the bandwidth increase request message #3, the end node can map the second bit rate data frame onto the first transmission frame with the increased length.

[0128] In the second possible implementation, the end node determines that the bandwidth of the service data needs to be increased, i.e., the end node triggers the bandwidth increase. The end node sends a bandwidth increase request message #5 to the aggregation node to request an increase in the bandwidth of the service data. Upon receiving the bandwidth increase request message #5, the aggregation node sends a bandwidth allocation message to the end node. This bandwidth allocation message instructs the end node to use new bandwidth resources; the details of this bandwidth allocation message can be found in the description of the first implementation. Accordingly, the end node receives the bandwidth allocation message and increases the length of the first transmission frame based on it, i.e., sets the length of the first transmission frame to a second length.

[0129] Optionally, after receiving the bandwidth increase request message #5, the aggregation node sends a bandwidth increase request message #4 to the upstream OTN device to instruct the upstream OTN device to increase bandwidth. The aggregation node receives the bandwidth increase response message #4 from the upstream OTN device, and after receiving the bandwidth increase response message #4, sends the bandwidth increase response message #5 to the end node to indicate acceptance or rejection of the bandwidth increase request message #5. Here, the bandwidth increase request message #5 can be an fgLCR request message, and the bandwidth increase response message #5 can be an fgLCR response message.

[0130] Further, after receiving the bandwidth increase response message #5, the end node maps the data frame with the second bit rate onto the first transmission frame with the increased length. For example, if the bandwidth increase response message #5 indicates acceptance of the bandwidth increase request message #5, the end node sends a bandwidth increase indication and adjusts the bit rate of the data frame from the first bit rate to a second bit rate, which is greater than the first bit rate, at a specific position indicated by the bandwidth increase indication. The end node then maps the data frame with the second bit rate onto the first transmission frame of the second length. This bandwidth increase indication can be referred to in the description above.

[0131] In one possible implementation of the above example, the transmission of bandwidth increase request messages (e.g., bandwidth increase request message #2, bandwidth increase request message #3, and bandwidth increase request message #5) and bandwidth increase response messages (e.g., bandwidth increase response message #2 and bandwidth increase response message #5) between the aggregation node and the end node can be implemented by the optical network terminal management and control interface (OMCI) protocol, or other interface protocols used to manage and control communication between the optical network terminal and the optical line terminal, without limitation.

[0132] For example, when OMCI implements bandwidth increase request message #2 or bandwidth increase request message #3, the OMCI message format is shown in Table 2. When OMCI implements the bandwidth increase response message #2, the OMCI message format is the same as the OMCI response message format. This OMCI response message can include two types of indications: acknowledge (ACK) and non-acknowledge (NACK), which can respectively indicate whether the previous request is accepted.

[0133] Table 2

[0134] It should be understood that the message format of the OMCI message in Table 2 is only an example. Other fields can be defined in this OMCI message. Please refer to the existing relevant descriptions for details.

[0135] In this application, the bandwidth increase request message may also be called bandwidth increase request information or bandwidth increase indication information, and the bandwidth increase response message may also be called bandwidth increase response information. The specific name of the information indicating bandwidth increase or the response information indicating bandwidth increase is not limited.

[0136] In another possible implementation of the above example, the bandwidth increase request messages (e.g., bandwidth increase request message #2, bandwidth increase request message #3, and bandwidth increase request message #5) and bandwidth increase response messages (e.g., bandwidth increase response message #2 and bandwidth increase response message #5) sent between the aggregation node and the endpoint node can be carried in the overhead area of ​​the first transmission frame or intermediate frame, or in the header field of the first transmission frame. For ease of explanation, the bandwidth increase request information and bandwidth increase response information will be referred to as the first information below without distinguishing the specific information.

[0137] The intermediate frame is an intermediate frame in the process of mapping an OTN frame to a first transmission frame. That is, when an OTN frame is mapped to a first transmission frame, the OTN frame is first mapped to this intermediate frame, and then the intermediate frame is mapped to the first transmission frame. This application does not specifically limit the intermediate frame. For example, the intermediate frame can be a service data unit (SDU) frame, or other intermediate frames in the process of mapping an OTN frame to a first transmission frame.

[0138] In one example, the first information is carried in the overhead area of ​​the intermediate frame. For instance, if, during the mapping process from the OTN frame to the first transport frame, the OTN frame is first mapped to the intermediate frame, and then the intermediate frame is mapped to the first transport frame, the first information can be carried in the overhead area of ​​the intermediate frame. Specifically, the payload area of ​​the intermediate frame is mapped from the OTN frame, and the bit rate of the payload area can be greater than or equal to the bit rate of the OTN frame; the overhead generated during the mapping process from the OTN frame to the payload area of ​​the intermediate frame is carried in the overhead area of ​​the intermediate frame, and the overhead area of ​​the intermediate frame also carries the first information. In other words, the payload area of ​​the intermediate frame carries all the valid data of the OTN frame, and the overhead area of ​​the intermediate frame carries the overhead generated when the OTN frame is mapped to the intermediate frame, as well as the first information. After the intermediate frame is generated after the OTN frame mapping is completed, all bytes of the intermediate frame are mapped to the payload area of ​​the first transport frame, and the overhead area of ​​the first transport frame carries the overhead generated when the intermediate frame is mapped to the first transport frame. Since the overhead area of ​​the intermediate frame carries the first information, and all bytes of the intermediate frame are mapped to the payload area of ​​the first transmission frame, the first information carried in the overhead area of ​​the intermediate frame can also be understood as the first information carried in the payload area of ​​the first transmission frame.

[0139] In another example, the first information is carried in the overhead or header field of the first transport frame. Exemplarily, when the OTN frame is directly mapped to the first transport frame, the first information is carried in the overhead or header field of the first transport frame. Specifically, the OTN frame is mapped to the payload area of ​​the first transport frame, where the bit rate of the payload area can be greater than the bit rate of the OTN frame. The overhead incurred during the mapping of the OTN frame to the payload area of ​​the first transport frame is carried in the payload header field or overhead area of ​​the first transport frame. The header or overhead area of ​​the first transport frame can carry the first information.

[0140] The following description uses the example of the first information being carried in the overhead area of ​​the first transmission frame or intermediate frame (such as the adjustment control overhead JCOH).

[0141] For example, the JCOH carries indication information for bandwidth adjustment (denoted as indication information #1). Indication information #1 can indicate a bandwidth increase; that is, it can be a bandwidth increase request message (such as bandwidth increase request message #2, bandwidth increase request message #3, or bandwidth increase request message #5). As an example, indication information #1 is carried by a control (CTRL) field. Specifically, a CTRL field is added to the JCOH of the first transmission frame or intermediate frame to carry indication information #1, and different values ​​of the CTRL field indicate bandwidth adjustment. For example, the CTRL field is 2 bits in size. When the value of these 2 bits is "01", it indicates a bandwidth increase; alternatively, when the value of these 2 bits is "10", it indicates a bandwidth decrease. The meaning of other values ​​for these 2 bits is not limited; for example, when the value of these 2 bits is "00", it indicates no adjustment request, and the meaning of other values ​​for these 2 bits can be found in relevant descriptions in existing protocols. It should be understood that the meanings of the different values ​​of the CTRL field mentioned above are merely examples and do not constitute a limitation on this application. As long as the bandwidth adjustment can be represented by the specific value of the CTRL field, it is acceptable.

[0142] It should be understood that the indication information for bandwidth adjustment carried by the CTRL field in this application is merely an example. This indication information can also be carried by other fields, such as newly defined fields for indicating bandwidth adjustment. Specifically, a newly defined field for indicating bandwidth adjustment can be added to the JCOH of the first transmission frame or intermediate frame. Furthermore, there is no limitation on the size of the field for indicating bandwidth adjustment; for example, the size of this field may be 1 bit.

[0143] Optionally, the JCOH also carries indication information (denoted as indication information #2) to indicate the status of the bandwidth adjustment protocol. As an example, this indication information #1 is carried by the resizing protocol (RP) field. That is, the RP field is added to the JCOH of the first transmission frame or intermediate frame to carry the indication information #2, and the status of the bandwidth adjustment protocol is indicated by different values ​​of the RP field. For example, the RP field is 1 bit in size; when the value of this 1 bit is "1", it indicates that the bandwidth adjustment protocol is in an active (or enabled) state; when the value of this 1 bit is "0", it indicates that the bandwidth adjustment protocol is in a deactivated (or disabled) state.

[0144] Optionally, the JCOH of the first transmission frame or intermediate frame also carries m bits to indicate the target bandwidth value to be adjusted, i.e., the size of the target bandwidth to be adjusted, where m is an integer greater than 1. For example, the m bits indicate the size of the target bandwidth by indicating the amount of the base bandwidth (e.g., 10.4 Mbit / s) (denoted as N, where N is a positive integer, such as N taking any value from 1 to 119), i.e., the size of the target bandwidth is n times the base bandwidth, such as the target bandwidth being from 10.4 Mbit / s to 119 * 10.4 Mbit / s.

[0145] It should be understood that this application does not limit the value of m, and can set it according to the range of the target bandwidth value (or the range of N). For example, the value of m can be 7 or 8. In addition, this application does not limit the field name of the m bits. For example, the m bits can be the target bandwidth (Target_BW) field (an example of the first field).

[0146] For example, the JCOH also carries information indicating a response to the bandwidth adjustment request (denoted as indication information #3), which can be bandwidth adjustment response information (such as bandwidth increase response message #2 or bandwidth increase response message #5). As an example, this bandwidth adjustment response information is carried by the tributary slot group status (TSGS) field. That is, a TSGS field is added to the JCOH of the first transmission frame or intermediate frame to carry this bandwidth adjustment response information, and different values ​​of the TSGS field indicate the response to the bandwidth adjustment request. For example, the TSGS field is 2 bits in size. When the 2 bits are "01", it indicates TSGS = "accept", i.e., responding to the bandwidth adjustment request; when the 2 bits are "10", it indicates TSGS = "reject", i.e., rejecting the bandwidth increase request. The meaning of other values ​​of these 2 bits can be found in the relevant descriptions in existing protocols. It should be understood that the meanings of the different values ​​of the TSGS field mentioned above are merely examples and do not constitute a limitation on this application. As long as the specific value of the TSGS field can be used to represent the response to the bandwidth adjustment request information, it is acceptable.

[0147] It should be understood that, in this application, the bandwidth adjustment response information being carried by the CTRL field is merely an example. This bandwidth adjustment response information can also be carried by other fields, such as a newly defined field indicating a response to a bandwidth adjustment request. That is, a newly defined field for carrying this bandwidth adjustment response information can be added to the JCOH of the first transmission frame or intermediate frame. Furthermore, there is no limitation on the size of the field carrying this bandwidth adjustment response information. For example, the field size can be 1 bit, where the value of "1" or "0" indicates a response to or rejection of the bandwidth adjustment request, respectively.

[0148] Figure 12 is a schematic diagram of an XGEM frame (an example of a first transmission frame) carrying first information provided in this application. As shown in Figure 12, the XGEM frame includes an XGEM frame header field (HD), a JCOH (the JOCH can be in the payload area of ​​the XGEM, that is, the JOCH is the overhead area of ​​the SDU, and the JOCH can also be the overhead of the XGEM) and an XGEM payload area, and the first information is carried in the JCOH.

[0149] As shown in Figure 12, this first information can occupy 14 bits in the JCOH, for example, the first information is carried in bits 33 to 46 of the JCOH. These 14 bits can be understood as the control protocol overhead for bandwidth adjustment. Among them, the first bit of these 14 bits is the RP bit, which can indicate the status of the bandwidth adjustment protocol; the second bit is the tributary slot connectivity check (TSCC) bit, which indicates the connectivity status of the tributary slot. For example, when the value of the second bit is "1", it indicates that the slot connectivity check is enabled, and when the value of the second bit is "0", it indicates that the slot connectivity check is disabled; the third and fourth bits are the CTRL field, which can indicate the bandwidth adjustment request information; the fifth and sixth bits are the TSGS field, which can indicate the bandwidth adjustment response information; and the seventh to fourteenth bits are the Target_BW field, which can indicate the size of the target bandwidth to be adjusted. It is understood that when the JOCH is the overhead area of ​​an XGEM frame, the JOCH also includes other overheads generated during the mapping of the OTN frame to the payload area of ​​the XGEM frame, such as the sequence indicator (SQ) overhead, the data volume indicator (Plen) overhead, and the data volume accumulation indicator (Sumlen) overhead. The meaning of each overhead and the number of bytes or bits it occupies can be found in the description in the protocol.

[0150] It should be understood that the use of the JCOH to carry the first information is merely an example; the first information can also be carried in the XGEM frame header field. When the first information is carried in the XGEM frame header field, it can occupy 14 bits of the XGEM frame header field, and the information indicated by these 14 bits refers to the aforementioned 14 bits. Furthermore, the position of these 14 bits in the XGEM frame header field is not limited.

[0151] Based on the bandwidth increase method provided in this application, in an fgOTN over PON system, when the bandwidth of service data needs to be increased, the reliability of service data transmission can be guaranteed by first increasing the length of the transmission frame, then adjusting the bit rate of the data frame carrying the service data, and mapping the data frame with the adjusted bit rate onto the transmission frame with the increased length.

[0152] It should be understood that in the above scheme, after the first device completes the mapping of the OTN frame to the first transmission frame, the first device sends the first transmission frame. Sending the first transmission frame may include sending the first transmission frame to a module within the first device. Optionally, this internal module may further map the first transmission frame to a second transmission frame; for example, in a GPON system, the second transmission frame may be a GTC frame (also called an XGTC frame). This internal module may also perform modulation, photoelectric conversion, or other processing on the first or second transmission frame, without limitation. Alternatively, the first device may send the first transmission frame to a corresponding receiving device, that is, convert the first transmission frame into an optical signal (which may include the conversion performed after mapping the first transmission frame to the second transmission frame) and send it to the corresponding receiving device.

[0153] Figures 6 and 7 are schematic flowcharts of the bandwidth increase methods 600 and 700 provided in this application, respectively. Methods 600 and 700 are illustrated using fgOTN Agg NE and fgOTN CPE#1 as the first devices, fgODU as the data frame, and XGEM as the transmission frame, respectively, to illustrate the application of method 600 in downlink and uplink data transmission.

[0154] As shown in Figure 6, method 600 includes the following steps. In this method, the traffic of service data increases, the length of XGEM changes from a first length to a second length, and the rate of fgODU changes from a first bit rate to a second bit rate.

[0155] S601, fgOTN Agg NE receives an fgLCR request message from the upstream fgOTN NE (an example of an upstream OTN device).

[0156] For example, when business data traffic increases, the upstream fgOTN NE triggers an increase in bandwidth by sending an fgLCR request message to the fgOTN Agg NE. This fgLCR request message can be referenced in the description of bandwidth increase request message #1 above.

[0157] S602, OMCI control message sent by fgOTN Agg NE to fgOTN CEP#1.

[0158] Upon receiving the fgLCR request message, the fgOTN Agg NE sends this OMCI control message to fgOTN CEP#1. This OMCI control message can be referenced in the description of the bandwidth increase request message #2 above.

[0159] S603, fgOTN Agg NE receives the OMCI response message sent by fgOTN CEP#1.

[0160] Upon receiving an OMCI control message, fgOTN CEP#1 replies with an OMCI response message to fgOTN Agg NE. This OMCI response message is similar to the description of bandwidth increase response message #2 above.

[0161] S604, in the downlink data transmission direction, fgOTN Agg NE sets the length of XGEM to the second length (i.e., the length of XGEM changes from the first length to the second length), and maps fgODU to the second-length XGEM according to the actual bit rate of fgODU (i.e., the first bit rate before the fgODU rate is adjusted).

[0162] Upon receiving an OMCI response message, fgOTN Agg NE increases the length of the XGEM and maps the fgODU onto the increased-length XGEM according to the actual bit rate of the fgODU. For example, this actual bit rate is the first bit rate.

[0163] S605, fgOTN Agg NE sends an fgLCR response message to the upstream fgOTN NE.

[0164] The execution order of S605 and S604 is not limited. For example, fgOTN Agg NE can set the length of XGEM to the second length after receiving the OMCI response message from fgOTN CEP#1, and send the fgLCR response message at the same time. Alternatively, fgOTN Agg NE can set the length of XGEM to the second length first, and then send the fgLCR response message.

[0165] S606, upstream fgOTN NE sends BWR_IND (an example of a bandwidth increase indication).

[0166] For example, after receiving the fgLCR response message, the upstream fgOTN NE sends BWR_IND.

[0167] S607, upstream fgOTN NE adjusts the bit rate of fgODU to the second bit rate at the position indicated by BWR_IND.

[0168] S608, the fgOTN Agg NE maps the received fgODU from the upstream fgOTN NE into an XGEM of the second length.

[0169] That is, after receiving the fgODU from the upstream fgOTN NE, the fgOTN Agg NE maps the fgODU of the second bit rate to the XGEM of the second length after the position indicated by BWR_IND.

[0170] As shown in Figure 7, method 700 includes the following steps. In this method, the traffic of service data increases, the length of XGEM changes from a first length to a second length, and the rate of fgODU changes from a first bit rate to a second bit rate.

[0171] S701, fgOTN Agg NE sends BWMAP to fgOTN CEP#1.

[0172] The BWBAP can be referenced in the description of the bandwidth allocation message above.

[0173] S702, fgOTN Agg NE sends an fgLCR request message to the upstream fgOTN NE.

[0174] The fgLCR request message can be referenced in the description of bandwidth increase request message #4 above.

[0175] For example, when the traffic of business data increases, the fgOTN Agg NE can trigger an increase in bandwidth by sending an fgLCR request message to the upstream fgOTN NE and sending a BWMAP to fgOTN CEP#1.

[0176] There is no restriction on the execution order of S701 and S702. For example, they can be executed simultaneously, or S701 can be executed first and then S702, or S702 can be executed first and then S701.

[0177] S703, in the uplink data transmission direction, fgOTN CEP#1 sets the length of XGEM to the second length and maps fgODU to the second-length XGEM according to the actual bit rate of fgODU.

[0178] Upon receiving a BWMAP, fgOTN CEP#1 increases the length of the XGEM and maps the fgODU onto the increased-length XGEM based on the actual bit rate of the fgODU. For example, this actual bit rate is the first bit rate.

[0179] S704, fgOTN Agg NE receives the fgLCR response message sent by the upstream fgOTN NE.

[0180] S705, fgOTN Agg NE sends an OMCI message to fgOTN CEP#1.

[0181] Upon receiving the fgLCR response message, the fgOTN Agg NE sends the OMCI message to fgOTN CEP#1 to instruct fgOTN CEP#1 to increase bandwidth. This OMCI message can be referenced in the description of bandwidth increase request message #3 above.

[0182] S706, fgOTN CEP#1 sends BWR_IND (an example of a bandwidth increase indication).

[0183] S707, fgOTN CEP#1 adjusts the bit rate of fgODU to the second bit rate at the position indicated by BWR_IND, and maps the fgODU of the second bit rate to an XGEM of the second length.

[0184] That is, fgOTN Agg NE receives an XGEM from fgOTN CEP#1 with a length of the second length, fgOTN Agg NE demaps the XGEM, and after the position indicated by BWR_IND, demaps to obtain fgODU with the second bit rate.

[0185] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 7. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 8 and 11. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0186] Figure 8 is a schematic block diagram of a bandwidth-enhancing device 1000 provided in an embodiment of this application. The device 1000 includes a receiving module 1010, which can be used to implement corresponding receiving functions. The receiving module 1010 can also be referred to as a receiving unit.

[0187] The device 1000 also includes a processing module 1020, which can be used to implement corresponding processing functions.

[0188] The device 1000 also includes a transmitting module 1030, which can be used to implement the corresponding transmitting function. The transmitting module 1030 can also be called a transmitting unit.

[0189] Optionally, the device 1000 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 1020 can read the instructions and / or data in the storage unit so that the device can implement the actions of the relevant nodes in the foregoing method embodiments.

[0190] The device 1000 can be used to perform the actions performed by the first device in the above method embodiments. In this case, the device 1000 can be a component of the first device. The receiving module 1010 is used to perform receiving-related operations of the first device in the above method embodiments. The processing module 1020 is used to perform processing-related operations of the first device in the above method embodiments. The sending module 1030 is used to perform sending-related operations of the first device in the above method embodiments.

[0191] When device 1000 is used to implement the function of the first device in the method embodiment shown in FIG4: processing module 1020 is used to increase the length of the first transmission frame, the first transmission frame carrying a data frame with a first bit rate; the processing module is also used to map a data frame with a second bit rate to the first transmission frame after the length of the first transmission frame is increased, the data frame with the second bit rate is transmitted after the data frame with the first bit rate, and the second bit rate is higher than the first bit rate.

[0192] It should be understood that the specific process of each module performing the above-mentioned corresponding steps can be referred to the relevant descriptions in the above method embodiments.

[0193] In addition, the receiving module 1010, processing module 1020 and transmitting module 1030 in device 1000 can also implement other operations or functions of the first device in the above method, which will not be described in detail here.

[0194] Figure 9 is a schematic diagram of a bandwidth-enhanced communication device 2000 provided in an embodiment of this application. This communication device can be an aggregation node or an end node (or access node). As shown in Figure 11, the communication device 2000 includes a processor 2010, an optical transceiver 2020, and a memory 2030. The memory 2030 is optional.

[0195] The processor 2010 and optical transceiver 2020 are used to implement the methods executed by the aggregation node or end node shown in Figure 4. During implementation, each step of the processing flow can be completed by the integrated logic circuitry in the processor 2010 or by software instructions, fulfilling the methods executed by the aggregation node or end node in the above figures. The optical transceiver 2020 is used to receive and process transmitted data frames for transmission to the peer node.

[0196] Memory 2030 can be used to store instructions so that processor 2010 can perform the steps mentioned in the above figure. Alternatively, memory 2030 can also be used to store other instructions to configure parameters of processor 2010 to achieve corresponding functions.

[0197] It should be noted that, in the network device hardware structure diagram shown in Figure 3, the processor 2010 and memory 2030 may be located in a tributary board or in a single board that combines tributary and line circuitry. Alternatively, multiple processors 2010 and memory 2030 may be included, located on the tributary board and line circuitry respectively, with the two boards working together to complete the aforementioned method steps.

[0198] It should be understood that the apparatus shown in FIG9 can also be used to perform the method steps involved in the aforementioned variations of the embodiments shown in the figures, which will not be described again.

[0199] Figure 10 is a schematic diagram of a chip system 3000 provided in an embodiment of this application. The chip system 3000 (or may also be called a processing system) includes logic circuitry 3010 and input / output interface 3020.

[0200] The logic circuit 3010 can be a processing circuit in the chip system 3000. The logic circuit 3010 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 3000 to implement the methods and functions of the embodiments of this application. The input / output interface 3020 can be an input / output circuit in the chip system 3000, outputting processed information from the chip system 3000, or inputting data or signaling information to be processed into the chip system 3000 for processing.

[0201] Optionally, the logic circuit 3010 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0202] Optionally, the input / output interface 3020 may include transceiver circuitry, a transceiver, input / output circuitry, or a communication interface.

[0203] As one approach, the chip system 3000 is used to implement the operations performed by the aggregation node or the endpoint node in the various method embodiments described above.

[0204] Specifically, the logic circuit 3010 is used to implement the processing-related operations performed by the aggregation node or the end node in the above method embodiment; the input / output interface 3020 is used to implement the sending and / or receiving-related operations performed by the aggregation node or the end node in the above method embodiment.

[0205] Figure 11 is a schematic diagram of the structure of a system 4000 provided in this application. The system includes the aforementioned OLT 134 and ONU 131. The ONU 131 can perform any step executed by the end node in Figure 4 of the above embodiment. The OLT 134 can perform any step executed by the aggregation node in Figure 4 of the above embodiment.

[0206] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first device in the above-described method embodiments.

[0207] For example, when the computer program is executed by the computer, it enables the computer to implement the methods executed by the first device in the various embodiments of the above methods.

[0208] Based on the above embodiments, this application also provides a computer-readable storage medium. This storage medium stores a software program, which, when read and executed by one or more processors, can implement the methods provided in any one or more of the above embodiments. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0209] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

[0210] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0211] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM can include a variety of forms, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0212] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0213] Those skilled in the art will recognize that the units and steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application; such implementations should not be considered beyond the scope of protection of this application.

[0214] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0215] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media may include, but are not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0216] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for increasing bandwidth, characterized in that, Applied to a first device, the method includes: Increase the length of the first transmission frame, which carries a data frame at a first bit rate; After the length of the first transmission frame is increased, a data frame with a second bit rate is mapped to the first transmission frame after the length increase. The data frame with the second bit rate is transmitted after the data frame with the first bit rate, and the second bit rate is higher than the first bit rate.

2. The method according to claim 1, characterized in that, The method further includes: Receive the first bandwidth increase request message from the upstream optical transport network (OTN) equipment; Send a second bandwidth increase request message to the user's front-end device (CPE).

3. The method according to claim 2, characterized in that, The method further includes: Receive a bandwidth increase response message from the CPE; Increasing the length of the first transmission frame includes: The length of the first transmission frame is increased based on the bandwidth increase response message.

4. The method according to claim 2 or 3, characterized in that, The method further includes: Detect increased bandwidth indication; Demap the optical transport network OTN frames received from the upstream OTN device to obtain data frames at the second bit rate.

5. The method according to claim 3, characterized in that, The second bandwidth increase request message or the bandwidth increase response message is implemented through the Optical Network Terminal Management and Control Interface (OMCI) protocol.

6. The method according to claim 3, characterized in that, The second bandwidth increase request message or the bandwidth increase response message is carried in the first transmission frame or an intermediate frame, wherein the intermediate frame is an intermediate frame in the process of mapping the data frame to the first transmission frame.

7. The method according to claim 6, characterized in that, The first transmission frame or the intermediate frame also includes a first field, which indicates the target bandwidth that the CPE needs to increase.

8. The method according to any one of claims 1 to 7, characterized in that, The first device is a aggregation node.

9. The method according to claim 1, characterized in that, The method further includes: Receive a bandwidth allocation message from an OTN device, the bandwidth allocation message instructing the first device to use new bandwidth resources; Increasing the length of the first transmission frame includes: The length of the first transmission frame is increased based on the bandwidth allocation message.

10. The method according to claim 9, characterized in that, The method further includes: Receive a third bandwidth increase request message from the OTN device; Based on the aforementioned third bandwidth increase request message, a bandwidth increase indication is sent.

11. The method according to claim 10, characterized in that, The step of mapping the second bit rate data frame to the first transmission frame after the length increase includes: Based on the bandwidth increase indication, the data frame at the second bit rate is mapped to the first transmission frame after the length increase.

12. The method according to claim 9, characterized in that, The method further includes: Send a fourth bandwidth increase request message to the OTN device, the fourth bandwidth increase request message indicating a bandwidth increase; Receive a fourth bandwidth increase response message from the OTN device.

13. The method according to claim 12, characterized in that, The step of mapping the second bit rate data frame to the first transmission frame after the length increase includes: Based on the fourth bandwidth increase response message, the data frame with the second bit rate is mapped to the first transmission frame after the length increase.

14. The method according to claim 10 or 11, characterized in that, The third bandwidth increase request message is implemented through the Optical Network Terminal Management and Control Interface (OMCI) protocol, or the third bandwidth increase request message is carried in the first transmission frame or an intermediate frame, wherein the intermediate frame is an intermediate frame in the process of mapping the data frame to the first transmission frame.

15. The method according to claim 12 or 13, characterized in that, The fourth bandwidth increase request message is implemented through the Optical Network Terminal Management and Control Interface (OMCI) protocol, or the fourth bandwidth increase request message is carried in the first transmission frame or an intermediate frame, wherein the intermediate frame is an intermediate frame in the process of mapping the data frame to the first transmission frame.

16. The method according to any one of claims 1, 9 to 15, characterized in that, The first device is an access node.

17. The method according to any one of claims 1 to 16, characterized in that, The data frame is a fine-grained flexible optical data unit (fgODUflex) frame or an optical service unit (OSU) frame, and the first transmission frame is a passive optical network (PON) frame.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: after the length of the first transmission frame is increased, mapping the data frame with the first bit rate to the first transmission frame after the length increase.

19. A bandwidth-enhancing device, characterized in that, include: A module or unit for performing the method as described in any one of claims 1 to 18.

20. A chip, characterized in that, include: A processor and a communication interface, the communication interface being used to receive data frames and transmit the data frames to the processor or other communication devices other than the communication device including the chip, the processor being used to perform the method as described in any one of claims 1 to 18.

21. A system, characterized in that, include: A convergence node and an access node, wherein the convergence node is configured to perform the method as described in any one of claims 1 to 8, 17, and 18, and the access node is configured to perform the method as described in any one of claims 1, 9 to 18.

Images