Communication method, communication node, and storage medium

Abstract

The present application discloses a communication method, a communication node, and a storage medium. The method comprises: allocating a downlink bandwidth carrier to a second communication node (401), wherein an identifier of the downlink bandwidth carrier and an identifier of an uplink bandwidth carrier share an identifier set of a bandwidth carrier; and, by means of a bandwidth allocation structure, sending to the second communication node a downlink bandwidth allocation result allocated to the downlink bandwidth carrier (402), wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

Description

Communication methods, communication nodes and storage media Technical Field

[0001] This application relates to the field of communication technology, such as a communication method, a communication node, and a storage medium. Background Technology

[0002] A Passive Optical Network (PON) system consists of an Optical Line Terminal (OLT) connected to multiple Optical Network Units (ONUs) via an Optical Distribution Network (ODN).

[0003] In the PON system of related technologies, the downlink OLT schedules different downlink services and services destined for different ONUs using a certain scheduling algorithm, and sends downlink frames containing downlink services to each ONU in a time-division multiplexing (TDM) manner. After receiving the downlink frame, each ONU needs to fully parse the downlink frame to obtain the service it needs to process.

[0004] The aforementioned communication method prevents each ONU from preprocessing the services it needs to handle before receiving them, resulting in high power consumption and other adverse effects for the ONU. Summary of the Invention

[0005] This application provides a communication method applied to a first communication node, the method comprising:

[0006] A downlink bandwidth carrier is allocated to the second communication node; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier;

[0007] The downlink bandwidth allocation result allocated to the downlink bandwidth carrier is sent to the second communication node through the bandwidth allocation structure; wherein, the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0008] This application provides a communication method applied to a second communication node, the method comprising:

[0009] Obtain the downlink bandwidth carrier allocated by the first communication node to the second communication node; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the identifier set of the bandwidth carrier;

[0010] The downlink bandwidth allocation result of the downlink bandwidth carrier is obtained from the bandwidth allocation structure; wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0011] This application provides a communication method applied to a first communication node, the method comprising:

[0012] Broadcast downlink bandwidth allocation capability;

[0013] Obtain a second communication node that supports downlink bandwidth processing capabilities.

[0014] This application provides a communication method applied to a second communication node, the method comprising:

[0015] When obtaining information about the downlink bandwidth allocation capability of the first communication node, the downlink bandwidth processing capability information is sent to the first communication node.

[0016] This application provides a communication node, including a processor; the processor is used to implement the communication method of any of the above embodiments when executing a computer program.

[0017] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the communication method of any of the above embodiments.

[0018] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0019] Figure 1 is a network diagram of a PON system provided in an embodiment;

[0020] Figure 2 is a schematic diagram of the first communication node transmitting downlink services in the related technology;

[0021] Figure 3 is a schematic diagram of downlink frames in related technologies;

[0022] Figure 4 is a flowchart illustrating a communication method provided in one embodiment;

[0023] Figure 5 is a schematic diagram of a bandwidth allocation structure provided in an embodiment;

[0024] Figure 6 is a schematic diagram of a first communication node transmitting downlink services according to an embodiment;

[0025] Figure 7 is a flowchart illustrating another communication method provided in one embodiment;

[0026] Figure 8 is a schematic diagram of the uplink bandwidth allocation structure in the XG-PON system;

[0027] Figure 9 is a schematic diagram of a downlink frame in a GPON system provided in an embodiment;

[0028] Figure 10 is a schematic diagram of a downlink frame in an XG-PON system provided in an embodiment;

[0029] Figure 11 is a schematic diagram of another downlink frame in an XG-PON system provided in one embodiment;

[0030] Figure 12 is a schematic diagram of another downlink frame in an XG-PON system provided in an embodiment;

[0031] Figure 13 is a schematic diagram of a downlink frame in an XGS-PON system provided in an embodiment;

[0032] Figure 14 is a schematic diagram of a downlink frame in a TWDM-PON system provided in an embodiment;

[0033] Figure 15 is a schematic diagram of a downlink frame in a 50G-PON system provided in an embodiment;

[0034] Figure 16 is a flowchart illustrating a communication method provided in one embodiment;

[0035] Figure 17 is a flowchart illustrating another communication method provided in one embodiment;

[0036] Figure 18 is a schematic diagram of a communication node provided in one embodiment. Detailed Implementation

[0037] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0038] Figure 1 is a network diagram of a PON system provided in one embodiment. As shown in Figure 1, the PON system consists of an OLT connected to multiple ONUs via an ODN. Figure 1 illustrates the example of the OLT connecting ONU1, ONU2, ..., ONUn via the ODN.

[0039] Figure 2 is a schematic diagram of the first communication node sending downlink services in related technologies. As shown in Figure 2, in related technologies, the OLT schedules different downlink services and services (also called service data) destined for different ONUs in the downlink direction using a certain scheduling algorithm. Figure 2 illustrates this by taking the OLT sending services to ONU1, ONU2, and ONU3 as an example. Services 1 and 4 are downlink services sent to ONU1, services 2 and 5 are downlink services sent to ONU2, and services 3 and 6 are downlink services sent to ONU3. The OLT sends downlink frames including each service to ONU1, ONU2, and ONU3 in TDM mode according to the scheduling algorithm.

[0040] Figure 3 is a schematic diagram of a downlink frame in related technologies. Figure 3 takes the transmission of downlink services in a 10-Gigabit-capable Passive Optical Network (XG-PON) as an example. The service is encapsulated in a series of XG-PON Encapsulation Method (XGEM) frames. An XGEM frame includes an XGEM header and an XGEM payload. The service data is placed in the XGEM payload of each XGEM frame.

[0041] Referring to Figures 2 and 3, each service in Figure 2 is carried within an XGEM frame. Multiple XGEM frames form an XGEM frame sequence carried within a superframe. Each ONU performs Forward Error Correction (FEC) and error correction on the superframe, then parses each XGEM frame sequentially, including verifying and correcting the XGEM header, extracting the XGEM port identifier (Port-ID) from the header, and determining whether to receive the XGEM payload by checking if the XGEM Port-ID belongs to its own ONU. This prevents ONUs from preprocessing services they need to handle before receiving them, resulting in higher power consumption for the ONUs. It also prevents ONUs and their downstream devices from reserving resources in advance. Furthermore, allocating multiple downlink bandwidth carriers to each ONU helps achieve better downlink service quality of service (QoS).

[0042] This application provides a communication method that can allocate downlink bandwidth carriers to a second communication node. The identifier of the downlink bandwidth carrier shares the same identifier set as the identifier of the uplink bandwidth carrier. Through a bandwidth allocation structure, the downlink bandwidth allocation result allocated to the downlink bandwidth carrier is sent to the second communication node. This bandwidth allocation structure is a reused uplink bandwidth allocation structure. On the one hand, this allows the second communication node to preprocess the downlink bandwidth allocation result, enabling it to shut down relevant components when data reception is not required, thereby reducing the power consumption of the second communication node and reserving resources in advance. On the other hand, since the identifier of the downlink bandwidth carrier shares the same identifier set as the uplink bandwidth carrier, and the bandwidth allocation structure is a reused uplink bandwidth allocation structure, the downlink bandwidth carrier and bandwidth allocation structure will not affect existing services, thus improving communication reliability.

[0043] The following describes the communication method, communication nodes, and their technical effects.

[0044] Figure 4 is a flowchart illustrating a communication method according to an embodiment. The method provided in this embodiment is applicable to a first communication node. In this embodiment, the first communication node may be an OLT. As shown in Figure 4, the method includes the following steps.

[0045] Step 401: Allocate downlink bandwidth carriers to the second communication node.

[0046] The identifiers of the downlink bandwidth carrier and the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier.

[0047] In this embodiment, the second communication node can be an ONU. The first communication node connects to multiple second communication nodes.

[0048] In this embodiment, the downlink bandwidth carrier identifier reuses the uplink bandwidth carrier identifier. That is, the downlink bandwidth carrier identifier and the uplink bandwidth carrier identifier share the same set of bandwidth carrier identifiers. This is to avoid introducing downlink bandwidth carriers and affecting existing services, thus achieving a smooth evolution.

[0049] In one embodiment, step 401 includes sending bandwidth carrier configuration information to the second communication node. The bandwidth carrier configuration information includes a downlink flag and an identifier of the downlink bandwidth carrier corresponding to the second communication node.

[0050] Optionally, the uplink bandwidth carrier in this embodiment can be a transmission container (T-CONT). The downlink bandwidth carrier in this embodiment can be a downlink T-CONT (T-CONT downstream, T-CONTd).

[0051] Optionally, the identifiers of the downlink bandwidth carrier and the uplink bandwidth carrier in this embodiment can be allocation identifiers (Alloc-ID).

[0052] Step 402: Send the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through the bandwidth allocation structure.

[0053] Among them, the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0054] In this embodiment, the uplink bandwidth allocation structure is used to carry the uplink bandwidth allocation result. To avoid conflicts with existing services, this embodiment reuses the uplink bandwidth allocation structure as the bandwidth allocation structure, and sends the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through the bandwidth allocation structure.

[0055] In this embodiment, reusing the uplink bandwidth allocation structure means that the uplink bandwidth allocation result and the downlink bandwidth allocation result share the same bandwidth allocation structure.

[0056] In one embodiment, the bandwidth allocation structure is a reused uplink bandwidth allocation structure, meaning that the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure remains unchanged. In other words, the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure is the same as the position of the uplink bandwidth carrier identifier in the uplink bandwidth allocation structure, so that the second communication node can determine whether the bandwidth carrier is the downlink bandwidth carrier or the uplink bandwidth carrier allocated to it.

[0057] In one embodiment, the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure remains unchanged, which can be achieved by keeping the position of the downlink bandwidth carrier identifier in the bandwidth allocation entry of the bandwidth allocation structure unchanged. That is, the position of the downlink bandwidth carrier identifier in the bandwidth allocation entry of the bandwidth allocation structure is the same as the position of the uplink bandwidth carrier identifier in the bandwidth allocation entry of the bandwidth allocation structure.

[0058] In one embodiment, the downlink bandwidth allocation result is the downlink bandwidth allocated to the downlink bandwidth carrier. The downlink bandwidth allocation result in this embodiment can also be referred to as the downlink scheduling result.

[0059] In one embodiment, a reused uplink bandwidth allocation structure can mean that the bandwidth allocation structure also includes an uplink bandwidth allocation result. The uplink bandwidth allocation result is the uplink bandwidth allocated to the uplink bandwidth carrier.

[0060] In one embodiment, in the bandwidth allocation structure, the uplink bandwidth allocation result is placed before the downlink bandwidth allocation result.

[0061] In one embodiment, in the bandwidth allocation structure, the uplink bandwidth allocation result is located after the downlink bandwidth allocation result.

[0062] In one embodiment, the communication method provided in this embodiment further includes the following step: indicating the number of bandwidth allocation entries in the bandwidth allocation structure to the second communication node, so that the second communication node can parse all bandwidth allocation entries, thereby improving the reliability of communication.

[0063] Optionally, the bandwidth allocation entry in this embodiment includes: the identifier of the downlink bandwidth carrier and downlink bandwidth information. Further, the bandwidth allocation entry in this embodiment also includes: the identifier of the uplink bandwidth carrier and uplink bandwidth information. That is, the bandwidth allocation entry includes: the identifier of the bandwidth carrier and bandwidth information.

[0064] Optionally, the bandwidth information in this embodiment includes at least one of the start time, length, and end time.

[0065] Figure 5 is a schematic diagram of a bandwidth allocation structure provided in one embodiment. As shown in Figure 5, the bandwidth allocation structure includes bandwidth allocation entries. Figure 5 illustrates an example where the bandwidth allocation structure includes m bandwidth allocation entries. Each bandwidth allocation entry includes: the identifier of the downlink bandwidth carrier and downlink bandwidth information. Further, each bandwidth allocation entry may also include: the identifier of the uplink bandwidth carrier and uplink bandwidth information.

[0066] In one embodiment, step 402 can be implemented as follows: the first communication node sends a downlink frame to the second communication node. The downlink frame contains a downlink bandwidth allocation result, which is sent through a bandwidth allocation structure.

[0067] Figure 6 is a schematic diagram of a first communication node transmitting downlink services according to an embodiment. Please refer to Figure 2 and Figure 6 simultaneously. Compared with Figure 2, in Figure 6, the OLT can send the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the ONU through the bandwidth allocation structure.

[0068] The communication method provided in this embodiment includes: allocating a downlink bandwidth carrier to a second communication node, wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier; and sending the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through a bandwidth allocation structure, wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure. On the one hand, this allows the second communication node to preprocess according to the downlink bandwidth allocation result, enabling it to shut down relevant components when data reception is not required, thereby reducing the power consumption of the second communication node and reserving resources in advance. On the other hand, since the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier, and the bandwidth allocation structure is a reused uplink bandwidth allocation structure, the downlink bandwidth carrier and the bandwidth allocation structure will not affect existing services, thus improving communication reliability.

[0069] Figure 7 is a flowchart illustrating another communication method provided in one embodiment. The method provided in this embodiment is applicable to a second communication node. In this embodiment, the second communication node can be an ONU. As shown in Figure 7, the method includes the following steps.

[0070] Step 701: Obtain the downlink bandwidth carrier allocated by the first communication node to the second communication node.

[0071] The identifiers of the downlink bandwidth carrier and the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier.

[0072] In one embodiment, step 701 includes the following implementation: obtaining a downlink flag and the identifier of the downlink bandwidth carrier corresponding to the second communication node from the bandwidth carrier configuration information sent by the first communication node, wherein the downlink bandwidth carrier identifier is used to receive the downlink bandwidth allocation result allocated by the first communication node.

[0073] In one embodiment, the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure remains unchanged, so that the second communication node can determine whether the bandwidth carrier is a downlink bandwidth carrier or an uplink bandwidth carrier allocated to it. In other words, the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure is the same as the position of the uplink bandwidth carrier identifier in the uplink bandwidth allocation structure.

[0074] Furthermore, the identifier of the downlink bandwidth carrier is located in the same position as the identifier of the uplink bandwidth carrier in the uplink bandwidth allocation entry.

[0075] Step 702: Obtain the downlink bandwidth allocation result of the downlink bandwidth carrier from the bandwidth allocation structure.

[0076] Among them, the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0077] In one embodiment, the bandwidth allocation structure further includes an uplink bandwidth allocation result. The uplink bandwidth allocation result is the uplink bandwidth allocated to the uplink bandwidth carrier, enabling the second communication node to obtain the uplink bandwidth allocation result allocated to its own uplink bandwidth carrier.

[0078] In one embodiment, the communication method further includes the following steps: obtaining the number of bandwidth allocation entries in the bandwidth allocation structure sent by the first communication node, and parsing the number of bandwidth allocation entries in the bandwidth allocation result.

[0079] In this embodiment, the second communication node can parse all bandwidth entries in the bandwidth allocation structure according to the number of bandwidth allocation entries. The bandwidth entries include downlink bandwidth entries and uplink bandwidth entries, and obtain the downlink bandwidth allocation result corresponding to the second communication node to avoid missing the identification of downlink bandwidth allocation results or uplink bandwidth allocation results.

[0080] In one embodiment, parsing the aforementioned number of bandwidth allocation entries in the bandwidth allocation result includes: obtaining the downlink bandwidth carrier and the corresponding downlink bandwidth information, and the uplink bandwidth carrier and the corresponding uplink bandwidth information.

[0081] In one embodiment, the downlink bandwidth allocation result is the downlink bandwidth allocated to the downlink bandwidth carrier. The bandwidth allocation entry includes: the identifier of the downlink bandwidth carrier and downlink bandwidth information. Further, the bandwidth allocation entry may also include: the identifier of the uplink bandwidth carrier and uplink bandwidth information. That is, the bandwidth allocation entry includes: the identifier of the bandwidth carrier and bandwidth information.

[0082] In this embodiment, after obtaining the downlink bandwidth allocation result corresponding to the second communication node, the second communication node can perform preprocessing based on the downlink bandwidth allocation result, such as shutting down the corresponding components when data is not needed, or reserving resources.

[0083] In one embodiment, a first communication node sends a downlink frame to a second communication node. The downlink frame contains a downlink bandwidth allocation result. The downlink bandwidth allocation result is sent through a bandwidth allocation structure. In this implementation, step 702 may include: obtaining the downlink bandwidth allocation result corresponding to the second communication node from the bandwidth allocation structure by judging the bandwidth carrier identifier in the bandwidth entry; obtaining the downlink bandwidth of the downlink bandwidth carrier corresponding to the second communication node from the downlink bandwidth allocation result corresponding to the second communication node; performing preprocessing; and receiving the downlink data corresponding to the second communication node from the downlink bandwidth of the downlink bandwidth carrier corresponding to the second communication node.

[0084] In one embodiment, the bandwidth allocation structure is located in the frame header of the downlink frame. After verifying and correcting the frame header, the second communication node obtains the downlink bandwidth allocation result corresponding to the second communication node from the bandwidth allocation structure.

[0085] The communication method provided in this embodiment includes: obtaining a downlink bandwidth carrier allocated by a first communication node to a second communication node, wherein the identifier of the downlink bandwidth carrier shares the identifier set of the bandwidth carrier with the identifier of the uplink bandwidth carrier; obtaining the downlink bandwidth allocation result and downlink bandwidth information of the downlink bandwidth carrier from the bandwidth allocation structure, wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure. On the one hand, this allows the second communication node to preprocess according to the downlink bandwidth allocation result, thereby reducing the power consumption of the second communication node by shutting down relevant components when data reception is not required, and restoring relevant components in the obtained downlink bandwidth, as well as reserving resources in advance for the second communication node. On the other hand, since the identifier of the downlink bandwidth carrier shares the identifier set of the bandwidth carrier with the identifier of the uplink bandwidth carrier, and the bandwidth allocation structure is a reused uplink bandwidth allocation structure, the downlink bandwidth carrier and the bandwidth allocation structure will not affect existing services, thus improving communication reliability.

[0086] The communication method provided in the above embodiments can be used in standardized PON systems, such as Gigabit-capable Passive Optical Network (GPON), XG-PON, 10-Gigabit-capable Symmetric Passive Optical Networks (XGS-PON), Time and Wavelength Division Multiplexed Passive Optical Network (TWDM-PON), and 50-Gigabit-capable Passive Optical Networks (50G-PON). Of course, the method provided in this embodiment is also applicable to the Institute of Electrical and Electronics Engineers (IEEE) Ethernet Passive Optical Network (EPON), 10GEPON, N*25G EPON, and other standards.

[0087] In PON systems of related technologies, T-CONT is the uplink bandwidth allocation carrier, represented by an Alloc-ID value. The Alloc-ID field is 12 bits or 14 bits. If it is 14 bits, there are 16384 possible values. In actual deployments of PON systems of related technologies, only a small proportion of Alloc-IDs are allocated, while a large proportion remain unallocated, sufficient for downlink bandwidth allocation carriers. A portion of these Alloc-IDs can be used for downlink bandwidth allocation. The range of Alloc-ID values ​​is the set of identifiers for the bandwidth carriers. That is, the identifiers of the downlink bandwidth carriers and the uplink bandwidth carriers share the same set of identifiers.

[0088] In related technologies, the uplink bandwidth allocation structure in PON systems is an uplink bandwidth map (BWmap). The BWmap contains N bandwidth allocation entries. The value of N is indicated by the BWmap length field. Figure 8 is a schematic diagram of the uplink bandwidth allocation structure in an XG-PON system. As shown in Figure 8, the downlink XG-PON Transmission Convergence (XGTC) frame length is 135432 bytes. The XGTC frame includes an XGTC header and an XGTC payload. The XGTC header includes: Header Length and Error Detection (HLend), the BWmap, and the Physical Layer Operations, Administration and Maintenance Downstream (PLOAMd). The HLend includes: an 11-bit BWmap length, an 8-bit PLOAM count, and a 13-bit Header Error Control (HEC). The BWmap consists of N 8-byte bandwidth allocation entries: Bandwidth Allocation Entry 1, Bandwidth Allocation Entry 2, ..., Bandwidth Allocation Entry N. Each bandwidth allocation entry includes: a 14-bit Alloc-ID identifier, 2-bit flags, a 16-bit start time for the allocated uplink bandwidth to the Alloc-ID, a 16-bit GrantSize for the allocated uplink bandwidth, a 1-bit Forced Wake-up Indication (FWI), a 2-bit Burst Profile definition, and a 13-bit HEC. The start time and GrantSize represent the start time and bandwidth size of the uplink bandwidth allocated to the Alloc-ID, respectively. The flags include a 1-bit Dynamic Bandwidth Report Unit (DBRu) and a 1-bit PLOAM Upstream (PLOAMu).

[0089] In related technologies, the ONU can obtain the number of bandwidth allocation entries included in the BWmap by parsing the BWmap Length, and then parse each bandwidth allocation entry in the BWmap one by one. It checks whether the Alloc-ID in the bandwidth allocation entry is assigned to itself. If the Alloc-ID in the bandwidth allocation entry is assigned to itself, it receives the uplink bandwidth information (start time and bandwidth size) included in that bandwidth allocation entry and sends the corresponding uplink data of the ONU within the uplink bandwidth corresponding to that uplink bandwidth information. If the Alloc-ID in the bandwidth allocation entry is not assigned to itself, it does not receive the uplink bandwidth information included in that bandwidth allocation entry.

[0090] In this embodiment, the uplink bandwidth carrier can be reused as the downlink bandwidth carrier, and the uplink bandwidth allocation structure can be reused as the bandwidth allocation structure to send the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through the bandwidth allocation structure. The bandwidth allocation structure may also include the uplink bandwidth allocation result, and the position of the downlink bandwidth carrier's identifier in the bandwidth allocation structure is the same as the position of the uplink bandwidth carrier's identifier in the uplink bandwidth allocation structure. Furthermore, the position of the downlink bandwidth carrier's identifier in the bandwidth allocation entry of the bandwidth allocation structure is the same as the position of the uplink bandwidth carrier's identifier in the bandwidth allocation entry of the uplink bandwidth allocation structure.

[0091] In one embodiment, T-CONT is reused as the downlink bandwidth allocation carrier and configured with downlink attributes to become downlink bandwidth carrier T-CONTd. The OLT allocates downlink bandwidth carrier T-CONTd to the ONU. T-CONTd is still represented by Alloc-ID, and the OLT allocates downlink bandwidth through T-CONTd.

[0092] In one embodiment, the ONU parses each Allocation structure in the BWmap one by one, first calculates the HEC and performs verification and error correction to obtain the correct Allocation structure, and then determines whether the Alloc-ID is assigned to itself. If it is assigned to itself, the corresponding downlink bandwidth is received; otherwise, the downlink bandwidth of the downlink bandwidth allocation carrier T-CONTd is not processed.

[0093] The downlink direction reuses T-CONT as the downlink bandwidth allocation carrier, which needs to be distinguished from the uplink bandwidth allocation carrier. This can be achieved by adding a downlink flag to the T-CONT, for example, by adding a downlink flag field to the Assign_Alloc-ID message, or by adding a downlink flag attribute to the T-CONT ME. This will be explained in detail in subsequent implementations.

[0094] The following describes the specific implementation methods of the communication methods provided in the above embodiments in GPON systems, XG-PON systems, XGS-PON systems, TWDM-PON systems, and 50G-PON systems.

[0095] Implementation method 1A is applicable to GPON systems

[0096] Implementation Method 1A.1 Modification of Bandwidth Carrier Configuration Information

[0097] In a GPON system, the OLT sends bandwidth carrier configuration information to the ONU. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0098] In one embodiment, the bandwidth carrier configuration information can be the T-CONT configuration message Assign_Alloc-ID. A downlink flag is introduced in Assign_Alloc-ID. Of course, the following implementation can also be applied when defining the Assign_Alloc-ID message in future Very High Speed ​​PON (VHSP) networks.

[0099] The GPON Assign_Alloc-ID message is shown in Table 1 below. There are several ways to improve it.

[0100] Table 1. GPON Assign_Alloc-ID Message

[0101] The first improvement defines the last bit of byte 4 as bit d, where d=0 indicates uplink and d=1 indicates downlink.

[0102] The second improvement modifies the meaning of the value 1 in byte 5 to: GEM-encapsulated payload, used for uplink; and adds a new value 3, which means: GEM-encapsulated payload, used for downlink.

[0103] The third improvement involves redefining byte 6 as a direction attribute, where a value of 0 indicates uplink and a value of 1 indicates downlink.

[0104] In one embodiment, a downlink flag is introduced in the ONU Management and Control Interface (OMCI) and the Managed Entity (ME) of T-CONT. As shown below, a Direction attribute is added, with a value of 0 indicating that T-CONT is used for uplink and a value of 1 indicating that it is used for downlink.

[0105] Management Entity ID: This attribute uniquely identifies each instance of this management entity (ME). This 2-byte number represents the physical capability that implements the T-CONT. It can be represented as 0xSSBB, where SS represents the slot ID containing this T-CONT (0 if representing the entire ONU), and BB is the T-CONT ID, numbered by the ONU itself. T-CONTs are numbered in ascending order, with each slot ranging from 0 to 255. (Read-only) (Required) (2 bytes);

[0106] Alloc-ID: This attribute associates the T-CONT with the allocation identifier assigned by the OLT in the Assign_Alloc-ID PLOAM message. For valid values ​​for this system, refer to the relevant Transport Convergence (TC) layer specification. Prior to setting this attribute on the OLT, it has an explicitly unavailable initial value: 0x00FF or 0xFFFF for ITU-T G.984 systems, and 0xFFFF for all other PON systems based on ITU-T General Transport Convergence (GTC). (Readable, Writable) (Required) (2 bytes);

[0107] Deprecated: The ONU must set this attribute to the value 1, and the OLT must ignore this attribute. (Read-only) (Required) (1 byte);

[0108] Policy: This attribute represents the traffic scheduling policy of T-CONT. Valid values ​​are as follows: 0 indicates none (empty policy), 1 indicates strict priority, and 2 indicates weighted round robin (WRR) scheduling (readable and writable) (required) (1 byte).

[0109] Note: This attribute is read-only unless otherwise specified in the QoS configuration flexibility attribute of the ONU2-G management entity. If the ONU does not support flexible configuration, attempts to set this attribute should be rejected, and a result reason code indicating an incorrect parameter should be returned.

[0110] Direction: This attribute indicates the direction of T-CONT. A value of 0 indicates that T-CONT is used for uplink, and a value of 1 indicates that it is used for downlink (readable, writable) (optional) (1 byte).

[0111] Implementation Method 1A.2BWmap Related Domain Modification

[0112] Figure 9 is a schematic diagram of a downlink frame in a GPON system according to an embodiment. As shown in Figure 9, the BWmap Length field of the downlink frame in the GPON system indicates the number of BWmap entries, which includes the number of downlink bandwidth allocation entries and the number of uplink bandwidth allocation entries (i.e., the number of bandwidth allocation entries in the bandwidth allocation structure in the above embodiment). The BWmap is reused as a bandwidth allocation structure, including multiple bandwidth allocation entries, to carry downlink bandwidth allocation results and uplink bandwidth allocation results.

[0113] Implementation Method 1A.3BWmap Constraint Processing

[0114] The original BWmap had some constraints, and some of these constraints need to be modified after the addition of downlink bandwidth allocation to BWmap.

[0115] Regarding the maximum number of BWmap entries: GPON sets a limit on the maximum number of bandwidth allocation entries (hereinafter referred to as BWmap entries) in the BWmap. Adding downlink bandwidth allocation results to the BWmap will definitely increase the number of BWmap entries. This embodiment does not limit the maximum number of BWmap entries; it can be limited according to actual needs. It should be noted that in the standard, the number of BWmap entries is carried by a specific field. In GPON, the number of BWmap entries is carried by the BWmap Length field. This field has 12 bits, meaning the maximum number of BWmap entries can reach 4096. Therefore, under normal circumstances, even if downlink bandwidth allocation entries are added to the BWmap, the number of BWmap entries will still meet the requirements.

[0116] Regarding bandwidth time constraints in BWmap entries: GPON requires that the allocation structures in the BWmap be arranged in ascending order of StartTime (the specific content of the GPON allocation structure can be found in the bandwidth allocation entries in Figure 8). The advantage of this is that the ONU can determine whether adjacent allocation structures overlap. If they overlap, the uplink bandwidth in these allocation structures can be discarded, avoiding conflicts on the OLT side. In practice, the ONU does not need to determine bandwidth overlap, as long as the OLT side ensures that all bandwidth periods are non-overlapping. Therefore, in this embodiment, the OLT does not send BWmap entries in ascending order of StartTime. It is recommended that the ONU not determine the overlap relationship between allocation structures. This allows downlink bandwidth allocation to be placed before uplink bandwidth allocation. Both uplink and downlink bandwidth allocation start from 0, enabling the ONU to process downlink bandwidth allocation earlier and obtain more downlink bandwidth preprocessing time. That is, in this implementation, the downlink bandwidth allocation result in the bandwidth allocation structure is placed before the uplink bandwidth allocation result.

[0117] Table 2 shows some relevant parameters for various PON systems. As shown in Table 2, in the GPON system, the uplink rate is 1.24416 Gbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, the total number of bytes in this period is 19440 bytes, and the bandwidth allocation is in units of 1 byte. The values ​​of StartTime and StopTime range from 0 to 19439. The downlink rate is 2.48832 Gbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, the total number of bytes in this period is 38880 bytes, and the bandwidth allocation can be in units of 2 bytes. The values ​​of StartTime and StopTime also range from 0 to 19439.

[0118] Table 2. Relevant parameters for each PON system

[0119] Regarding the maximum time interval constraint in BWmap entries: In this implementation, the ascending order of StartTime is still retained. The downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result, and it is agreed that an additional 125μs will be added to the basic allocation period of 125μs as the downlink bandwidth allocation period. Placing the downlink bandwidth allocation result after the uplink bandwidth allocation result may affect the preprocessing of downlink bandwidth, but the problem is minor, with a difference of approximately a few microseconds.

[0120] Table 3 shows another set of relevant parameters for various PON systems. As shown in Table 3, in the GPON system, the uplink rate is 1244.16 Mbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, the total number of bytes in this period is 19440 bytes, and the bandwidth allocation is in units of 1 byte. The values ​​of StartTime and StopTime range from 0 to 19439. The downlink rate is 2488.32 Mbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, the total number of bytes in this period is 38880 bytes, and the bandwidth allocation can be in units of 2 bytes. The values ​​of StartTime and StopTime range from 19440 to 38879 (i.e., 0+19440 to 19439+19440).

[0121] Table 3. Another relevant parameter for each PON system

[0122] Implementation Method 2A XG-PON System

[0123] Implementation Method 2A.1 Modification of Bandwidth Carrier Configuration Information

[0124] In an XG-PON system, the OLT sends bandwidth carrier configuration information to the ONU. This bandwidth carrier configuration information includes a downlink flag and the identifier of the downlink bandwidth carrier corresponding to the ONU.

[0125] In one embodiment, the bandwidth carrier configuration information can be the T-CONT configuration message Assign_Alloc-ID. A downlink flag is introduced in Assign_Alloc-ID.

[0126] The Assign_Alloc-ID messages for XG-PON and XGS-PON are shown in Table 4 below. The following are some ways to improve them.

[0127] Table 4 XG-PON Assign_Alloc-ID Message

[0128] The first improvement method defines the highest bit of the Alloc-ID-value field of bytes 5-6 as d bits, where d=0 indicates uplink and d=1 indicates downlink.

[0129] The second improvement modifies the meaning of value 1 in the Alloc-ID-type field of byte 7 to XGEM-encapsulated payload, used for uplink; and adds a new value 2, which means XGEM-encapsulated payload, used for downlink.

[0130] The third improvement involves redefining byte 8 as a direction attribute, where a value of 0 indicates uplink and a value of 1 indicates downlink.

[0131] In one embodiment, a downlink flag is introduced in the OMCI T-CONT ME. A Direction attribute is added, with a value of 0 indicating that T-CONT is used for uplink and a value of 1 indicating that it is used for downlink. For details on the implementation, please refer to the corresponding content in Implementation Method 1A.1, which will not be repeated here.

[0132] Implementation Method 2A.2BWmap Related Domain Modification

[0133] Figure 10 is a schematic diagram of a downlink frame in an XG-PON system according to an embodiment. As shown in Figure 10, the BWmap Length field of the downlink frame in the XG-PON system indicates the number of BWmap entries, which includes: the number of downlink bandwidth allocation entries and the number of uplink bandwidth allocation entries (i.e., the number of bandwidth allocation entries in the bandwidth allocation structure in the above embodiment). The BWmap is reused as a bandwidth allocation structure, including multiple bandwidth allocation entries, to carry downlink bandwidth allocation results and uplink bandwidth allocation results.

[0134] Implementation Method 2A.3BWmap Constraint Processing

[0135] The original BWmap had some constraints, and some of these constraints need to be modified after the addition of downlink bandwidth allocation to BWmap.

[0136] Regarding the maximum number of BWmap entries: XG-PON imposes a limit on the number of BWmap entries. For example, XG-PON limits the maximum number of entries to 512. Adding downlink bandwidth allocation results to the BWmap will definitely increase the number of BWmap entries. This embodiment does not limit the maximum number of BWmap entries; it can be limited according to actual needs. It should be noted that in the standard, the number of BWmap entries is carried by a specific field. In XG-PON, the number of BWmap entries is carried by the BWmap Length field. This field has 11 bits, meaning the maximum number of BWmap entries can reach 2048. Therefore, under normal circumstances, even if downlink bandwidth allocation entries are added to the BWmap, the number of BWmap entries will still meet the requirements.

[0137] Regarding bandwidth time constraints in BWmap entries, XG-PON requires that the allocation structures in the BWmap be arranged in ascending order of StartTime. The advantage of this is that the ONU can determine whether adjacent allocation structures overlap. If they overlap, the uplink bandwidth in those allocation structures can be discarded, avoiding conflicts on the OLT side. In practice, the ONU does not need to determine bandwidth overlap, as long as the OLT side ensures that all bandwidth periods are non-overlapping. Therefore, in this embodiment, the OLT does not send BWmap entries in ascending order of StartTime. It is recommended that the ONU not determine the overlap relationship between allocation structures. This allows downlink bandwidth allocation to be placed before uplink bandwidth allocation. Both uplink and downlink bandwidth allocation start from 0, enabling the ONU to process downlink bandwidth allocation earlier and obtain more downlink bandwidth preprocessing time. That is, in this implementation, the downlink bandwidth allocation result in the bandwidth allocation structure precedes the uplink bandwidth allocation result.

[0138] Figure 11 is a schematic diagram of another downlink frame in an XG-PON system provided by an embodiment. As shown in Figure 11, the downlink bandwidth allocation result in the bandwidth allocation structure is located before the uplink bandwidth allocation result.

[0139] Please refer to Table 2. In the XG-PON system, the uplink rate is 2.48832 Gbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, the total number of bytes in this period is 38880 bytes, and the bandwidth allocation is in units of 4 bytes. The values ​​of StartTime and GrantSize range from 0 to 9719. The downlink rate is 9.95328 Gbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, the total number of bytes in this period is 155520 bytes, and the bandwidth allocation can be in units of 16 bytes. The values ​​of StartTime and GrantSize also range from 0 to 9719.

[0140] Regarding the maximum time interval constraint in BWmap entries: In this implementation, the ascending order of StartTime is still retained. The downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result, and it is agreed that the allocation period will be extended by another 125μs based on the 125μs allocation period. Placing the downlink bandwidth allocation result after the uplink bandwidth allocation result may affect the preprocessing of downlink bandwidth, but the problem is minor, with a difference of only a few microseconds.

[0141] Figure 12 is a schematic diagram of another downlink frame in an XG-PON system provided by an embodiment. As shown in Figure 12, the downlink bandwidth allocation result in the bandwidth allocation structure is placed after the uplink bandwidth allocation result.

[0142] Please refer to Table 3. In the XG-PON system, the uplink rate is 2488.32 Mbit / s; uplink bandwidth allocation: the uplink frame period is 125 μs, and the total number of bytes within this period is 38880 bytes. Bandwidth allocation is in units of 4 bytes, and the values ​​of StartTime and GrantSize range from 0 to 9719. The downlink rate is 9.95328 Gbit / s; downlink bandwidth allocation: the downlink frame period is 125 μs, and the total number of bytes within this period is 155520 bytes. Bandwidth allocation can be in units of 16 bytes, and the values ​​of StartTime and GrantSize range from 9720 to 19439 (i.e., 0+9720 to 9719+9720).

[0143] Implementation Method 3A XGS-PON System

[0144] Implementation Method 3A.1 Modification of Bandwidth Carrier Configuration Information

[0145] In an XGS-PON system, the OLT sends bandwidth carrier configuration information to the ONU. This bandwidth carrier configuration information includes a downlink flag and the identifier of the downlink bandwidth carrier corresponding to the ONU.

[0146] In one embodiment, the bandwidth carrier configuration information can be the T-CONT configuration message Assign_Alloc-ID. A downlink flag is introduced into Assign_Alloc-ID. The XGS-PON Assign_Alloc-ID message is shown in Table 4, and the following are some ways to improve it.

[0147] The first improvement method defines the highest bit of the Alloc-ID-value field of bytes 5-6 as d bits, where d=0 indicates uplink and d=1 indicates downlink.

[0148] The second improvement modifies the meaning of the Alloc-ID-type value 1 in byte 7 to: XGEM-encapsulated payload, used for uplink; and adds a new value 2, which means: XGEM-encapsulated payload, used for downlink.

[0149] The third improvement involves redefining byte 8 as a direction attribute, where a value of 0 indicates uplink and a value of 1 indicates downlink.

[0150] In one embodiment, a downlink flag is introduced in the OMCI T-CONT ME. A Direction attribute is added, with a value of 0 indicating that T-CONT is used for uplink and a value of 1 indicating that it is used for downlink. For details on the implementation, please refer to the corresponding content in Implementation Method 1A.1, which will not be repeated here.

[0151] Implementation method 3A.2BWmap related domain modification

[0152] Figure 13 is a schematic diagram of a downlink frame in an XGS-PON system according to an embodiment. As shown in Figure 13, the BWmap Length field of the downlink frame in the XGS-PON system indicates the number of BWmap entries, which includes: the number of downlink bandwidth allocation entries and the number of uplink bandwidth allocation entries (i.e., the number of bandwidth allocation entries in the bandwidth allocation structure in the above embodiment). The BWmap is reused as a bandwidth allocation structure, including multiple bandwidth allocation entries, to carry downlink bandwidth allocation results and uplink bandwidth allocation results.

[0153] Implementation Method 3A.3B: Wmap Constraint Processing

[0154] The original BWmap had some constraints, and some of these constraints need to be modified after the addition of downlink bandwidth allocation to BWmap.

[0155] Regarding the maximum number of BWmap entries: XGS-PON limits the number of BWmap entries. For example, XGS-PON limits the maximum number of entries to 512. Adding downlink bandwidth allocation results to the BWmap will definitely increase the number of BWmap entries. This embodiment does not limit the maximum number of BWmap entries; it can be limited according to actual needs. It should be noted that in the standard, the number of BWmap entries is carried by a specific field. In XGS-PON, the number of BWmap entries is carried by the BWmap Length field. This field has 11 bits, meaning the maximum number of BWmap entries can reach 2048. Therefore, under normal circumstances, even if downlink bandwidth allocation entries are added to the BWmap, the number of BWmap entries will still meet the requirements.

[0156] Regarding bandwidth time constraints in BWmap entries, XGS-PON requires that the allocation structures in the BWmap be arranged in ascending order of StartTime. The advantage of this is that the ONU can determine whether adjacent allocation structures overlap. If they overlap, the uplink bandwidth in these allocation structures can be discarded, avoiding conflicts on the OLT side. In practice, the ONU does not need to determine bandwidth overlap, as long as the OLT side ensures that all bandwidth periods are non-overlapping. Therefore, in this embodiment, the OLT does not send BWmap entries in ascending order of StartTime. It is recommended that the ONU not determine the overlap relationship between allocation structures. This allows downlink bandwidth allocation to be placed before uplink bandwidth allocation. Both uplink and downlink bandwidth allocation start from 0, enabling the ONU to process downlink bandwidth allocation earlier and obtain more downlink bandwidth preprocessing time. That is, in this implementation, the downlink bandwidth allocation result in the bandwidth allocation structure precedes the uplink bandwidth allocation result.

[0157] Please refer to Table 2. In the XGS-PON system, the uplink rate is 9.95328 Gbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, the total number of bytes in this period is 155520 bytes, and the bandwidth allocation is in units of 16 bytes. The values ​​of StartTime and GrantSize range from 0 to 9719. The downlink rate is 9.95328 Gbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, the total number of bytes in this period is 155520 bytes, and the bandwidth allocation can be in units of 16 bytes. The values ​​of StartTime and GrantSize also range from 0 to 9719.

[0158] Regarding the maximum time interval constraint in BWmap entries: In this implementation, the ascending order of StartTime is still retained. The downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result, and it is agreed that the downlink bandwidth allocation period will be extended by another 125μs based on the 125μs allocation period. Placing the downlink bandwidth allocation result after the uplink bandwidth allocation result may affect the preprocessing of downlink bandwidth, but the problem is minor, with a difference of only a few microseconds.

[0159] Please refer to Table 3. In the XGS-PON system, the uplink rate is 9.95328 Gbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, the total number of bytes in this period is 155520 bytes, and the bandwidth allocation is in units of 16 bytes. The values ​​of StartTime and GrantSize range from 0 to 9719. The downlink rate is 9.95328 Gbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, the total number of bytes in this period is 155520 bytes, and the bandwidth allocation can be in units of 16 bytes. The values ​​of StartTime and GrantSize range from 9720 to 19439 (i.e., 0+9720 to 9719+9720).

[0160] Implementation Method 4A TWDM-PON System

[0161] Implementation Method 4A.1 Modification of Bandwidth Carrier Configuration Information

[0162] In a TWDM-PON system, the OLT sends bandwidth carrier configuration information to the ONU. This bandwidth carrier configuration information includes a downlink flag and the identifier of the downlink bandwidth carrier corresponding to the ONU.

[0163] In one embodiment, the bandwidth carrier configuration information can be the T-CONT configuration message Assign_Alloc-ID. A downlink flag is introduced into Assign_Alloc-ID. The TWDM-PON Assign_Alloc-ID message is shown in Table 5, and the following are some ways to improve it.

[0164] Table 5. TWDM-PON Assign_Alloc-ID Message

[0165] The first improvement method defines the highest bit of the Alloc-ID-value field of bytes 5-6 as d bits, where d=0 indicates uplink and d=1 indicates downlink.

[0166] The second improvement modifies the meaning of the Alloc-ID-type value 0x01 in byte 7 to: XGEM-encapsulated payload, used for uplink; and adds a new value 0x02, which means: XGEM-encapsulated payload, used for downlink.

[0167] The third improvement involves redefining byte 10 as a direction attribute, where a value of 0 indicates uplink and a value of 1 indicates downlink.

[0168] In one embodiment, a downlink flag is introduced in the OMCI T-CONT ME. A Direction attribute is added, with a value of 0 indicating that T-CONT is used for uplink and a value of 1 indicating that it is used for downlink. For details on the implementation, please refer to the corresponding content in Implementation Method 1A.1, which will not be repeated here.

[0169] Implementation method 4A.2BWmap related domain modification

[0170] Figure 14 is a schematic diagram of a downlink frame in a TWDM-PON system according to an embodiment. As shown in Figure 14, the BWmap Length field of the downlink frame in the TWDM-PON system indicates the number of BWmap entries, which includes: the number of downlink bandwidth allocation entries and the number of uplink bandwidth allocation entries (i.e., the number of bandwidth allocation entries corresponding to the bandwidth allocation structure in the above embodiment). The BWmap is reused as a bandwidth allocation structure, including multiple bandwidth allocation entries, to carry downlink bandwidth allocation results and uplink bandwidth allocation results.

[0171] Implementation Method 4A.3BWmap Constraint Processing

[0172] The original BWmap had some constraints, and some of these constraints need to be modified after the addition of downlink bandwidth allocation to BWmap.

[0173] Regarding the maximum number of BWmap entries: TWDM-PON sets a limit on the number of BWmap entries. Adding downlink bandwidth allocation results to the BWmap will definitely increase the number of BWmap entries. This embodiment does not limit the maximum number of BWmap entries; it can be limited according to actual needs. It should be noted that in the standard, the number of BWmap entries is carried by a specific field. In TWDM-PON, the number of BWmap entries is carried by the BWmap Length field. This field has 11 bits, meaning the maximum number of BWmap entries can reach 2048. Therefore, under normal circumstances, even if downlink bandwidth allocation entries are added to the BWmap, the number of BWmap entries will still meet the requirements.

[0174] Regarding bandwidth time constraints in BWmap entries, TWDM-PON requires that the allocation structures in the BWmap be arranged in ascending order of StartTime. The advantage of this is that the ONU can determine whether adjacent allocation structures overlap. If they overlap, the uplink bandwidth in those allocation structures can be discarded, avoiding conflicts on the OLT side. In practice, the ONU does not need to determine bandwidth overlap, as long as the OLT side ensures that all bandwidth periods are non-overlapping. Therefore, in this embodiment, the OLT does not send BWmap entries in ascending order of StartTime. It is recommended that the ONU not determine the overlap relationship between allocation structures. This allows downlink bandwidth allocation to be placed before uplink bandwidth allocation. Both uplink and downlink bandwidth allocation start from 0, enabling the ONU to process downlink bandwidth allocation earlier and obtain more downlink bandwidth preprocessing time. That is, in this implementation, the downlink bandwidth allocation result in the bandwidth allocation structure precedes the uplink bandwidth allocation result.

[0175] Please refer to Table 2. In the TWDM-PON system, the uplink rates are 2.48832 and 9.95328 Gbit / s, respectively. Uplink bandwidth allocation: the uplink frame period is 125 μs, and the total number of bytes in the period corresponding to different rates is 38880 and 155520 bytes, respectively. The bandwidth allocation is in units of 4 and 16 bytes, respectively. The values ​​of StartTime and GrantSize range from 0 to 9719. Downlink rate: 9.95328 Gbit / s. Downlink bandwidth allocation: the downlink frame period is 125 μs, and the total number of bytes in this period is 155520 bytes. The bandwidth allocation can be in units of 16 bytes, and the values ​​of StartTime and StopTime also range from 0 to 9719.

[0176] Regarding the maximum time interval constraint in BWmap entries: In this implementation, the ascending order of StartTime is still retained. The downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result, and it is agreed that the downlink bandwidth allocation period will be extended by another 125μs based on the 125μs allocation period. Placing the downlink bandwidth allocation result after the uplink bandwidth allocation result may affect the preprocessing of downlink bandwidth, but the problem is minor, with a difference of only a few microseconds.

[0177] Please refer to Table 3. In the TWDM-PON system, the uplink rates are 2.48832 and 9.95328 Gbit / s; the uplink bandwidth allocation is as follows: the uplink frame period is 125 μs, and the total number of bytes in the period corresponding to different rates is 38880 and 155520 bytes respectively. The bandwidth allocation is in units of 4 and 16 bytes respectively, and the values ​​of StartTime and GrantSize range from 0 to 9719; the downlink rate is 9.95328 Gbit / s; the downlink bandwidth allocation is as follows: the downlink frame period is 125 μs, and the total number of bytes in this period is 155520 bytes. The bandwidth allocation can be in units of 16 bytes, and the values ​​of StartTime and StopTime range from 9720 to 19439 (i.e., 0+9720 to 9719+9720).

[0178] Implementation Method 5A 50G-PON System

[0179] Implementation Method 5A.1 Modification of Bandwidth Carrier Configuration Information

[0180] In a 50G-PON system, the OLT sends bandwidth carrier configuration information to the ONU. This bandwidth carrier configuration information includes a downlink flag and the identifier of the downlink bandwidth carrier corresponding to the ONU.

[0181] In one embodiment, the bandwidth carrier configuration information can be the T-CONT configuration message Assign_Alloc-ID. A downlink flag is introduced in Assign_Alloc-ID. Of course, the following implementation can also be applied when defining the Assign_Alloc-ID message in future Very High Speed ​​PON (VHSP) networks.

[0182] The Assign_Alloc-ID message of 50G-PON is shown in Table 6 below. The improvement methods are similar to those of XG-PON / XGS-PON, and there are several ways to improve it.

[0183] Table 6. Assign_Alloc-ID messages for 50G-PON

[0184] The first improvement method defines the highest bit of the Alloc-ID-value field of bytes 5-6 as d bits, where d=0 indicates uplink and d=1 indicates downlink.

[0185] The second improvement modifies the meaning of the Alloc-ID-type value 1 in byte 7 to: XGEM-encapsulated payload, used for uplink; and adds a new value 2, which means: XGEM-encapsulated payload, used for downlink.

[0186] The third improvement involves redefining byte 19 as a direction attribute, with a value of 0 indicating uplink and a value of 1 indicating downlink.

[0187] In one embodiment, a downlink flag is introduced in the OMCI T-CONT ME. A Direction attribute is added, with a value of 0 indicating that T-CONT is used for uplink and a value of 1 indicating that it is used for downlink. For details on the implementation, please refer to the corresponding content in Implementation Method 1A.1, which will not be repeated here.

[0188] Implementation method 5A.2BWmap related domain modification

[0189] Figure 15 is a schematic diagram of a downlink frame in a 50G-PON system according to an embodiment. As shown in Figure 15, the BWmap Length field of the downlink frame in the 50G-PON system indicates the number of BWmap entries, which includes: the number of downlink bandwidth allocation entries and the number of uplink bandwidth allocation entries (i.e., the number of bandwidth allocation entries corresponding to the bandwidth allocation structure in the above embodiment). The BWmap is reused as a bandwidth allocation structure, including multiple bandwidth allocation entries, to carry downlink bandwidth allocation results and uplink bandwidth allocation results.

[0190] Implementation Method 5A.3BWmap Constraint Processing

[0191] The original BWmap had some constraints, and some of these constraints need to be modified after the addition of downlink bandwidth allocation to BWmap.

[0192] Regarding the maximum number of BWmap entries: 50G-PON sets a limit on the number of BWmap entries. For example, the maximum number of entries in 50G-PON is limited to 512. Adding downlink bandwidth allocation results to the BWmap will definitely increase the number of BWmap entries. This embodiment does not limit the maximum number of BWmap entries; it can be limited according to actual needs. It should be noted that the number of BWmap entries in the standard is carried by a specific field. In 50G-PON, the number of BWmap entries is carried by the BWmap Length field. This field has 11 bits, meaning the maximum number of BWmap entries can reach 2048. Therefore, under normal circumstances, even if downlink bandwidth allocation entries are added to the BWmap, the number of BWmap entries will still meet the requirements.

[0193] Regarding bandwidth time constraints in BWmap entries: 50G-PON requires that the allocation structures in the BWmap be arranged in ascending order of StartTime. The advantage of this is that the ONU can determine whether adjacent allocation structures overlap. If they overlap, the uplink bandwidth in these allocation structures can be discarded, avoiding conflicts on the OLT side. In practice, the ONU does not need to determine bandwidth overlap, as long as the OLT side ensures that all bandwidth periods are non-overlapping. Therefore, in this embodiment, the OLT does not send BWmap entries in ascending order of StartTime. It is recommended that the ONU not determine the overlap relationship between allocation structures. This allows downlink bandwidth allocation to precede uplink bandwidth allocation. Both uplink and downlink bandwidth allocation start from 0, enabling the ONU to process downlink bandwidth allocation earlier and obtain more downlink bandwidth preprocessing time. That is, in this implementation, the downlink bandwidth allocation result in the bandwidth allocation structure precedes the uplink bandwidth allocation result.

[0194] Please refer to Table 2. In the 50G-PON system, the uplink rates are 12.4416, 24.8832, and 49.7664 Gbit / s; uplink bandwidth allocation: the uplink frame period is 125 μs, and the total number of bytes in the period corresponding to different rates are 194400, 388800, and 777600 bytes respectively. The bandwidth allocation is in units of 16, 32, and 64 bytes respectively, and the values ​​of StartTime and GrantSize range from 0 to 12149; downlink rate: 49.7664 Gbit / s; downlink bandwidth allocation: the downlink frame period is 125 μs, and the total number of bytes in this period is 777600 bytes. The bandwidth allocation can be in units of 16 bytes, and the values ​​of StartTime and GrantSize also range from 0 to 12149.

[0195] Regarding the maximum time interval constraint in BWmap entries: In this implementation, the ascending order of StartTime is still retained. The downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result, and it is agreed that the downlink bandwidth allocation period will be extended by another 125μs based on the 125μs allocation period. Placing the downlink bandwidth allocation result after the uplink bandwidth allocation result may affect the preprocessing of downlink bandwidth, but the problem is minor, with a difference of only a few microseconds.

[0196] Please refer to Table 3. In the 50G-PON system, the uplink rates are 12.4416, 24.8832, and 49.7664 Gbit / s; uplink bandwidth allocation: the uplink frame period is 125 μs, and the total number of bytes in the period corresponding to different rates are 194400, 388800, and 777600 bytes respectively. The bandwidth allocation is in units of 16, 32, and 64 bytes respectively, and the values ​​of StartTime and GrantSize range from 0 to 12149; downlink rate: 49.7664 Gbit / s; downlink bandwidth allocation: the downlink frame period is 125 μs, and the total number of bytes in this period is 777600 bytes. The bandwidth allocation can be in units of 16 bytes, and the values ​​of StartTime and GrantSize range from 12150 to 24299 (0+12150 to 12149+12150).

[0197] Implementation Method 6A VHSP System

[0198] Implementation method 6A.1 Modification of bandwidth carrier configuration information can refer to implementation method 5A.1 in the 50G-PON system; Implementation method 6A.2 Modification of BWmap related fields can refer to implementation method 5A.2 in the 50G-PON system; Implementation method 6A.3 BWmap constraint processing can refer to implementation method 5A.3 in the 50G-PON system. The specific implementation process will not be described here.

[0199] It should be noted that the specific implementation details in the above embodiments are also applicable to IEEE EPON, 10GEPON, N*25G EPON, and the VHSP system that will be standardized in the future.

[0200] The following describes another implementation of the communication method provided in this embodiment. Its difference from the embodiments shown in Figures 4 to 15 and various optional implementations is that: in the embodiments shown in Figures 4 to 15, the second communication node is always a second communication node that supports downlink bandwidth processing capability; in the scenario involved in this other communication method, the second communication node can be either a node that supports downlink bandwidth processing capability (referred to as a first type of second communication node) or a node that does not support downlink bandwidth processing capability. In this embodiment, the second communication node that does not support downlink bandwidth processing capability can include two types: a second communication node that has downlink bandwidth processing capability but reports that it is not supported (referred to as a second type of second communication node), and a node that does not have downlink bandwidth processing capability (referred to as a third type of second communication node). When the second communication node is an ONU, the ONU in this other communication method can include both first type ONUs and second type ONUs.

[0201] Adding downlink bandwidth carriers and bandwidth allocation structures to these standardized PON systems (PON systems with added downlink bandwidth carriers and bandwidth allocation structures are referred to as Type I PON systems) significantly modifies the standards, potentially leading to incompatibility with existing systems (which can be called Type II PON systems, including systems with Type II ONUs) and hindering smooth upgrades and evolution. For example, typically, the OLT side is upgraded first to support downlink bandwidth allocation, and Type II ONUs are replaced one by one as needed with Type I ONUs that support downlink bandwidth allocation. However, because Type II ONUs cannot parse the bandwidth allocation structure in the above embodiments, this can cause downlink parsing errors and downlink service anomalies related to Type II ONUs. Therefore, the following alternative communication method addresses how to add downlink bandwidth carriers and bandwidth allocation structures to standardized PON systems to achieve downlink bandwidth allocation and ensure compatibility and smooth evolution between Type I and Type II PON systems.

[0202] Figure 16 is a flowchart illustrating a communication method according to an embodiment. This method is applicable to a first communication node. In this embodiment, the first communication node may be an OLT. As shown in Figure 16, the method includes the following steps.

[0203] Step 1601: Broadcast downlink bandwidth allocation capability.

[0204] In one embodiment, the first communication node broadcasts its downlink bandwidth allocation capability to the second communication node.

[0205] In one embodiment, when the second communication node determines that the first communication node supports downlink bandwidth allocation capability, it sends downlink bandwidth processing capability information to the first communication node. Optionally, the second communication node here can be a first type of second communication node.

[0206] Step 1602: Obtain a second communication node that supports downlink bandwidth processing capabilities.

[0207] In one embodiment, step 1602 is implemented as follows: receiving downlink bandwidth processing capability information sent by the second communication node, wherein the downlink bandwidth processing capability information includes those that support downlink bandwidth processing capability and those that do not support downlink bandwidth processing capability; and obtaining the second communication node that supports downlink bandwidth processing capability based on the downlink bandwidth processing capability information.

[0208] In one embodiment, the communication method further includes the following steps: allocating a downlink bandwidth carrier to a second communication node that supports downlink bandwidth processing capability, wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the same set of identifiers of the bandwidth carrier; and sending the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through a bandwidth allocation structure, wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0209] It should be noted that the second communication node that "sends the downlink bandwidth allocation result allocated to the downlink bandwidth carrier to the second communication node through the bandwidth allocation structure" may include at least one of the following: a first type of second communication node and a second type of second communication node.

[0210] To achieve compatibility with both the first and second type of second communication nodes, this embodiment reuses the uplink bandwidth allocation structure to transmit the downlink bandwidth carrier's downlink bandwidth allocation result. Furthermore, this embodiment reuses the uplink bandwidth carrier as the downlink bandwidth carrier.

[0211] In one embodiment, the bandwidth allocation structure is a reused uplink bandwidth allocation structure, meaning that the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure remains unchanged, so that a second communication node that supports downlink bandwidth processing capability can determine whether the downlink bandwidth carrier is the downlink bandwidth carrier allocated to it, and so that a second communication node that does not support downlink bandwidth processing capability can determine that the bandwidth carrier is not the bandwidth carrier allocated to it.

[0212] In one embodiment, the bandwidth allocation structure is a reused uplink bandwidth allocation structure, meaning that the bandwidth allocation structure also includes uplink bandwidth allocation results. The uplink bandwidth allocation results are the uplink bandwidth allocated to the uplink bandwidth carrier.

[0213] In one embodiment, the communication method further includes the step of indicating the number of bandwidth allocation entries in the bandwidth allocation structure to a second communication node that supports downlink bandwidth processing capability.

[0214] In one embodiment, the downlink bandwidth allocation result is the downlink bandwidth allocated to the downlink bandwidth carrier.

[0215] In one embodiment, the bandwidth allocation entry includes: the correspondence between the identifier of the bandwidth carrier and the bandwidth information.

[0216] In one embodiment, allocating a downlink bandwidth carrier to a second communication node that supports downlink bandwidth processing capability includes: sending bandwidth carrier configuration information to the second communication node that supports downlink bandwidth processing capability. The bandwidth carrier configuration information includes a downlink flag and an identifier of the downlink bandwidth carrier corresponding to the second communication node that supports downlink bandwidth processing capability.

[0217] This embodiment uses concepts similar to those in the embodiments shown in Figures 4 to 15 and various optional implementations, such as downlink bandwidth carriers and bandwidth allocation structures. The implementation methods and technical principles are described in the embodiments shown in Figures 4 to 15 and various optional implementations, and will not be repeated here.

[0218] The communication method provided in this embodiment obtains a second communication node that supports downlink bandwidth processing capability by broadcasting downlink bandwidth allocation capability, which facilitates the subsequent sending of downlink bandwidth allocation results to the second communication node that supports downlink bandwidth processing capability. This achieves compatibility with both second communication nodes that support downlink bandwidth processing capability and those that do not, thus realizing a smooth evolution.

[0219] Figure 17 is a flowchart illustrating another communication method provided in one embodiment. The method provided in this embodiment is applicable to a second communication node. In this embodiment, the second communication node can be an ONU. As shown in Figure 17, the method includes the following steps.

[0220] Step 1701: When the downlink bandwidth allocation capability of the first communication node is obtained, send the downlink bandwidth processing capability information to the first communication node.

[0221] In one embodiment, if the downlink bandwidth processing capability of the second communication node is supported, the method further includes the following steps: obtaining the downlink bandwidth carrier allocated by the first communication node to the second communication node, wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the identifier set of the bandwidth carrier; obtaining the downlink bandwidth allocation result of the downlink bandwidth carrier from the bandwidth allocation structure, wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

[0222] In one embodiment, the bandwidth allocation structure is a reused uplink bandwidth allocation structure, meaning that the position of the downlink bandwidth carrier identifier in the bandwidth allocation structure remains unchanged, so that a second communication node that supports downlink bandwidth processing capability can determine whether the downlink bandwidth carrier is the downlink bandwidth carrier allocated to it, and so that a second communication node that does not support downlink bandwidth processing capability can determine whether the bandwidth carrier is not the bandwidth carrier allocated to it.

[0223] In one embodiment, the bandwidth allocation structure is a reused uplink bandwidth allocation structure, indicating that the bandwidth allocation structure also includes an uplink bandwidth allocation result, wherein the uplink bandwidth allocation result is the uplink bandwidth allocated to the uplink bandwidth carrier, so that the second communication node obtains the uplink bandwidth allocation result allocated to its own uplink bandwidth carrier.

[0224] In one embodiment, the method further includes the following steps: obtaining the number of bandwidth allocation entries in the bandwidth allocation structure sent by the first communication node, and parsing the number of bandwidth allocation entries in the bandwidth allocation result.

[0225] In one embodiment, parsing the aforementioned number of bandwidth allocation entries in the bandwidth allocation result includes: obtaining the downlink bandwidth carrier and the corresponding downlink bandwidth information, and the uplink bandwidth carrier and the corresponding uplink bandwidth information.

[0226] In one embodiment, the downlink bandwidth allocation result is used to indicate the downlink bandwidth allocated to the downlink bandwidth carrier.

[0227] In one embodiment, the bandwidth allocation entry includes: the identifier of the bandwidth carrier and bandwidth information.

[0228] In one embodiment, if the downlink bandwidth processing capability of the second communication node is supported, obtaining the downlink bandwidth carrier allocated by the first communication node to the second communication node includes: obtaining the downlink flag and the identifier of the downlink bandwidth carrier corresponding to the second communication node from the bandwidth carrier configuration information sent by the first communication node. The downlink bandwidth carrier identifier is used to receive the downlink bandwidth allocation result allocated by the first communication node.

[0229] This embodiment uses concepts similar to those in the embodiments shown in Figures 4 to 15 and various optional implementations, such as downlink bandwidth carriers and bandwidth allocation structures. The implementation methods and technical principles are described in the embodiments shown in Figures 4 to 15 and various optional implementations, and will not be repeated here.

[0230] The communication method provided in this embodiment achieves smooth evolution by sending downlink bandwidth processing capability information to the first communication node when the first communication node is found to support downlink bandwidth allocation capability. This enables compatibility with both second communication nodes that support downlink bandwidth processing capability and second communication nodes that do not support downlink bandwidth processing capability.

[0231] Based on the embodiments shown in Figures 4 to 15 and various optional implementation methods, the following describes the specific implementation methods of the communication methods provided in the above embodiments in GPON systems, XG-PON systems, XGS-PON systems, TWDM-PON systems and 50G-PON systems.

[0232] In one embodiment, the ONU parses each Allocation structure in the BWmap one by one, first calculating the HEC and performing verification and error correction to obtain the correct Allocation structure, and then determining the Alloc-ID. For ONUs that do not support downlink bandwidth processing capabilities, since the T-CONTd, which serves as the downlink bandwidth allocation carrier, is allocated to other ONUs, these ONUs will directly ignore the Allocation structure. For ONUs that support downlink bandwidth processing capabilities, they can identify whether the T-CONTd of the downlink bandwidth allocation carrier is allocated to themselves. If it is allocated to themselves, they receive the corresponding downlink bandwidth; otherwise, they do not process the T-CONTd of that downlink bandwidth allocation carrier.

[0233] In one embodiment, the downlink direction reuses the T-CONT as the downlink bandwidth allocation carrier, which needs to be distinguished from the uplink bandwidth allocation carrier. This can be achieved by adding a downlink flag to the T-CONT, for example, by adding a downlink flag to the Assign_Alloc-ID message or to the T-CONT ME. ONUs that do not support downlink bandwidth processing capabilities are unaware of the downlink flag, while ONUs that do support downlink bandwidth processing capabilities are aware of the downlink flag, parse it, and further store it. For newly added ONUs that support downlink bandwidth processing capabilities, the downlink bandwidth allocation result can be identified. ONUs that do not support downlink bandwidth processing capabilities treat these T-CONTs as T-CONTs allocated to other ONUs and do not process them, thus achieving backward compatibility.

[0234] In this embodiment, by reusing the uplink bandwidth allocation carrier and uplink bandwidth allocation structure, the OLT can allocate downlink bandwidth to some or all ONUs that support downlink bandwidth processing capabilities, thereby achieving compatibility and smooth evolution between the first type of PON system and the second type of PON system.

[0235] Implementation Method 1B GPON System

[0236] Implementation Method 1B.1 Modification of Bandwidth Carrier Configuration Information

[0237] In a GPON system, the OLT sends bandwidth carrier configuration information to the ONU that supports downlink bandwidth processing capabilities. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0238] Implementation method 1B.1 is similar to implementation method 1A.1, except that in the first improvement, the last bit of byte 4 is changed to bit d. For ONUs that do not support downlink bandwidth processing capabilities, this bit d needs to be set to 0. Other implementation methods of implementation method 1B.1 are similar to implementation method 1A.1, and will not be described in detail here.

[0239] Implementation method 1B.2BWmap related domain modification

[0240] The implementation method of Implementation Method 1B.2 is similar to that of Implementation Method 1A.2, and will not be described again here.

[0241] Implementation Method 1B.3BWmap Constraint Processing

[0242] Implementation method 1B.3 is similar to implementation method 1A.3, except that while retaining the ascending order of StartTime, the downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result. It is agreed that the downlink bandwidth allocation period is extended by another 125μs based on the 125μs allocation period, resulting in a maximum bandwidth allocation range exceeding the original limit. However, ONUs that do not support downlink bandwidth processing capabilities are unaware of this out-of-range bandwidth allocation time configuration because they determine that the T-CONTd Alloc-ID does not meet the reception requirements when parsing it. Only ONUs that support downlink bandwidth processing capabilities will be aware of this out-of-range time configuration.

[0243] Other implementations of Implementation Method 1B.3 are similar to Implementation Method 1A.3 and will not be described in detail here.

[0244] Implementation method 1B.4 ONU reports downlink bandwidth processing capacity.

[0245] In scenarios where both Type 1 and Type 2 ONUs coexist, the OLT needs to know which ONUs support downlink bandwidth processing capabilities in order to allocate downlink bandwidth carriers and send downlink bandwidth allocation results to these ONUs. The ONU can inform the OLT of its downlink bandwidth processing capabilities when it first sends a message to the OLT. In the current standard, when an ONU transitions from an inactive state to an active state, the first message it sends to the OLT is the Serial_Number_ONU message, which allows the ONU to report its downlink bandwidth processing capabilities.

[0246] The Serial_Number_ONU message in the GPON system is shown in Table 7. During the activation process, if the ONU supports downlink bandwidth processing capability, bit A is set to 1 in the 12th byte of the Serial_Number_ONU message sent to the OLT; otherwise, bit A remains 0.

[0247] Table 7 Serial_Number_ONU Messages in GPON Systems

[0248] Implementation 1B.5 OLT Broadcast Downlink Bandwidth Allocation Capability

[0249] Of course, the ONU also needs to know whether the OLT supports downlink bandwidth allocation and downlink carrier allocation functions. Only if the OLT supports downlink bandwidth allocation and downlink carrier allocation functions will the ONU inform the OLT of its downlink bandwidth processing capacity. Therefore, the OLT needs to inform the OLT of its downlink bandwidth allocation and downlink carrier (i.e., downlink bandwidth carrier) allocation capabilities, which can be carried in downlink broadcast messages. For example, downlink bandwidth allocation and downlink carrier allocation capabilities can be carried in uplink burst configuration messages. Of course, the timing of the capability notification between the OLT and ONU can be selected as needed. The specific method of carrying downlink bandwidth allocation and processing capabilities, as well as downlink bandwidth carrier allocation and processing capabilities, can be achieved through PLOAM messages, OMCI, etc.

[0250] The OLT capabilities of GPON are broadcast, see Table 8. When the 8th bit of byte 10 is set to 1, it indicates that the OLT supports downlink bandwidth allocation and downlink carrier allocation capabilities.

[0251] Table 8 GPON OLT Capability Broadcasting

[0252] Implementation Method 2B XG-PON System

[0253] Implementation Method 2B.1 Modification of Bandwidth Carrier Configuration Information

[0254] In an XG-PON system, the OLT sends bandwidth carrier configuration information to the ONU that supports downlink bandwidth processing capabilities. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0255] Implementation method 2B.1 is similar to implementation method 2A.1, except that in the first improvement, the highest bit of the Alloc-ID-value field of bytes 5-6 is changed to the d bit. For ONUs that do not support downlink bandwidth processing capabilities, the d bit is set to 0. Other implementation methods of implementation method 2B.1 are similar to implementation method 2A.1, and will not be described in detail here.

[0256] Implementation Method 2B.2BWmap Related Domain Modification

[0257] The implementation method of Implementation Method 2B.2 is similar to that of Implementation Method 2A.2, and will not be described again here.

[0258] Implementation Method 2B.3BWmap Constraint Processing

[0259] Implementation method 2B.3 is similar to implementation method 2A.3, except that while retaining the ascending order of StartTime, the downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result. It is agreed that the downlink bandwidth allocation period is extended by another 125μs based on the 125μs allocation period, and its maximum allocation range will exceed the original limit. However, ONUs that do not support downlink bandwidth processing capabilities are unaware of this out-of-range bandwidth allocation time configuration because they determine that the T-CONTd Alloc-ID does not meet the reception requirements when parsing it. Only ONUs that support downlink bandwidth processing capabilities will be aware of this out-of-range time configuration.

[0260] Other implementations of Implementation Method 2B.3 are similar to those of Implementation Method 2A.3, and will not be described in detail here.

[0261] Implementation Method 2B.4 ONU Report Downlink Bandwidth Processing Capacity

[0262] In scenarios where both Type 1 and Type 2 ONUs coexist, the OLT needs to know which ONUs support downlink bandwidth processing capabilities in order to allocate downlink bandwidth carriers and send downlink bandwidth allocation results to these ONUs. The ONU can inform the OLT of its downlink bandwidth processing capabilities when it first sends a message to the OLT. In the current standard, when an ONU transitions from an inactive state to an active state, the first message it sends to the OLT is the Serial_Number_ONU message, which allows the ONU to report its downlink bandwidth processing capabilities.

[0263] The Serial_Number_ONU message in the XG-PON system is shown in Table 9. During the activation process, if the ONU supports downlink bandwidth processing capability, the corresponding bit in the 17 bytes of the Serial_Number_ONU message sent to the OLT is set to 1; otherwise, it remains 0.

[0264] Table 9 Serial_Number_ONU Messages in the XG-PON System

[0265] Implementation 2B.5 OLT Broadcast Downlink Bandwidth Allocation Capability

[0266] The OLT capabilities of XG-PON are broadcast in Table 10. When the 4th bit of the 5th byte is set to 1, it indicates that the OLT supports downlink bandwidth allocation and downlink carrier allocation capabilities.

[0267] Table 10 OLT Broadcast Capabilities of XG-PON

[0268] Implementation Method 3B XGS-PON System

[0269] Implementation Method 3B.1 Modification of Bandwidth Carrier Configuration Information

[0270] In an XGS-PON system, the OLT sends bandwidth carrier configuration information to the ONU that supports downlink bandwidth processing capabilities. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0271] Implementation method 3B.1 is similar to implementation method 3A.1, except that in the first improvement, the highest bit of the Alloc-ID-value field of bytes 5-6 is changed to the d bit. For ONUs that do not support downlink bandwidth processing capabilities, the d bit is set to 0. Other implementation methods of implementation method 3B.1 are similar to implementation method 3A.1, and will not be described in detail here.

[0272] Implementation method 3B.2BWmap related domain modification

[0273] The implementation method of Implementation Method 3B.2 is similar to that of Implementation Method 3A.2, and will not be described again here.

[0274] Implementation Method 3B.3BWmap Constraint Processing

[0275] Implementation method 3B.3 is similar to implementation method 3A.3, except that while retaining the ascending order of StartTime, the downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result. It is agreed that the downlink bandwidth allocation period is extended by another 125μs based on the 125μs allocation period, and its maximum allocation range will exceed the original limit. However, the second type of ONU is unaware of this out-of-range bandwidth allocation time configuration because it determines that the T-CONTd Alloc-ID does not meet the reception requirements when parsing it. Only the first type of ONU or an ONU within the first type that supports downlink bandwidth processing capabilities will be aware of this out-of-range time configuration.

[0276] Other implementations of Implementation Method 3B.3 are similar to Implementation Method 3A.3 and will not be described in detail here.

[0277] Implementation method 3B.4 ONU reports downlink bandwidth processing capacity.

[0278] In scenarios where both Type 1 and Type 2 ONUs coexist, the OLT needs to know which ONUs support downlink bandwidth processing capabilities in order to allocate downlink bandwidth carriers and send downlink bandwidth allocation results to these ONUs. The ONU can inform the OLT of its downlink bandwidth processing capabilities when it first sends a message to the OLT. In the current standard, when an ONU transitions from an inactive state to an active state, the first message it sends to the OLT is the Serial_Number_ONU message, which allows the ONU to report its downlink bandwidth processing capabilities.

[0279] The Serial_Number_ONU message in the XGS-PON system is shown in Table 11. During the activation process, if the ONU supports downlink bandwidth processing, the corresponding bit in the 40 bytes of the Serial_Number_ONU message sent to the OLT is set to 1; otherwise, it remains 0.

[0280] Table 11 Serial_Number_ONU Messages in XGS-PON Systems

[0281] Implementation 3B.5 OLT Broadcast Downlink Bandwidth Allocation Capability

[0282] The OLT capabilities of XGS-PON are broadcast in Table 12. When bit 4 of byte 5 is set to 1, it indicates that the OLT supports downlink bandwidth allocation and downlink carrier allocation capabilities.

[0283] Table 12 OLT Broadcast Capabilities of XGS-PON

[0284] Implementation Method 4B TWDM-PON System

[0285] In a TWDM-PON system, the OLT sends bandwidth carrier configuration information to the ONU that supports downlink bandwidth processing capabilities. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0286] Implementation method 4B.1 is similar to implementation method 4A.1, except that in the first improvement, the highest bit of the Alloc-ID-value field of bytes 5-6 is changed to the d bit. For ONUs that do not support downlink bandwidth processing capabilities, the d bit is set to 0. Other implementation methods of implementation method 4B.1 are similar to implementation method 4A.1, and will not be described in detail here.

[0287] Implementation method 4B.2BWmap related domain modification

[0288] The implementation method of Implementation Method 4B.2 is similar to that of Implementation Method 4A.2, and will not be described again here.

[0289] Implementation Method 4B.3BWmap Constraint Processing

[0290] Implementation method 4B.3 is similar to implementation method 4A.3, except that while retaining the ascending order of StartTime, the downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result. It is agreed that the downlink bandwidth allocation period is extended by another 125μs based on the 125μs allocation period, and its maximum allocation range will exceed the original limit. However, ONUs that do not support downlink bandwidth processing capabilities are unaware of this out-of-range bandwidth allocation time configuration because they determine that the T-CONTd Alloc-ID does not meet the reception requirements when parsing it. Only ONUs that support downlink bandwidth processing capabilities will be aware of this out-of-range time configuration.

[0291] Other implementations of Implementation 4B.3 are similar to Implementation 4A.3 and will not be described in detail here.

[0292] Implementation method 4B.4 ONU reports downlink bandwidth processing capacity.

[0293] In scenarios where both Type 1 and Type 2 ONUs coexist, the OLT needs to know which ONUs support downlink bandwidth processing capabilities in order to allocate downlink bandwidth carriers and send downlink bandwidth allocation results to these ONUs. The ONU can inform the OLT of its downlink bandwidth processing capabilities when it first sends a message to the OLT. In the current standard, when an ONU transitions from an inactive state to an active state, the first message it sends to the OLT is the Serial_Number_ONU message, which allows the ONU to report its downlink bandwidth processing capabilities.

[0294] The Serial_Number_ONU message in a TWDM-PON system is shown in Table 13. During the activation process, if the ONU supports downlink bandwidth processing, the highest bit of the 39th byte of the Serial_Number_ONU message sent to the OLT is set to 1; otherwise, it remains 0.

[0295] Table 13 Serial_Number_ONU Messages in TWDM-PON Systems

[0296] Implementation 4B.5 OLT Broadcast Downlink Bandwidth Allocation Capability

[0297] The OLT capabilities broadcast for TWDM-PON are shown in Table 14. Setting the R bit in byte 5 to 1 indicates that the OLT supports downlink bandwidth allocation and downlink carrier allocation capabilities.

[0298] Table 14 Broadcast Capabilities of TWDM-PON OLTs

[0299] Implementation Method 5B 50G-PON System

[0300] In a 50G-PON system, the OLT sends bandwidth carrier configuration information to the ONU that supports downlink bandwidth processing capabilities. This bandwidth carrier configuration information includes a downlink flag and the identifier of the corresponding downlink bandwidth carrier for the ONU.

[0301] Implementation method 5B.1 is similar to implementation method 5A.1, except that in the first improvement, the highest bit of the Alloc-ID-value field of bytes 5-6 is changed to the d bit. For ONUs that do not support downlink bandwidth processing capabilities, the d bit is set to 0. Other implementation methods of implementation method 5B.1 are similar to implementation method 5A.1, and will not be described in detail here.

[0302] Implementation method 5B.2BWmap related domain modification

[0303] The implementation method of Implementation Method 5B.2 is similar to that of Implementation Method 5A.2, and will not be described again here.

[0304] Implementation method 5B.3BWmap constraint handling

[0305] Implementation method 5B.3 is similar to implementation method 5A.3, except that while retaining the ascending order of StartTime, the downlink bandwidth allocation result can be placed after the uplink bandwidth allocation result. It is agreed that the downlink bandwidth allocation period is extended by another 125μs based on the 125μs allocation period, and its maximum allocation range will exceed the original limit. However, ONUs that do not support downlink bandwidth processing capabilities are unaware of this out-of-range bandwidth allocation time configuration because they determine that the T-CONTd Alloc-ID does not meet the reception requirements when parsing it. Only ONUs that support downlink bandwidth processing capabilities will be aware of this out-of-range time configuration.

[0306] Other implementations of Implementation 5B.3 are similar to Implementation 5A.3 and will not be described in detail here.

[0307] Implementation method 5B.4 ONU reports downlink bandwidth processing capacity.

[0308] In scenarios where both Type 1 and Type 2 ONUs coexist, the OLT needs to know which ONUs support downlink bandwidth processing capabilities in order to allocate downlink bandwidth carriers and send downlink bandwidth allocation results to these ONUs. The ONU can inform the OLT of its downlink bandwidth processing capabilities when it first sends a message to the OLT. In the current standard, when an ONU transitions from an inactive state to an active state, the first message it sends to the OLT is the Serial_Number_ONU message, which allows the ONU to report its downlink bandwidth processing capabilities.

[0309] The Serial_Number_ONU message in a 50G-PON system is shown in Table 15. During the activation process, if the ONU supports downlink bandwidth processing, the highest bit of the 39th byte of the Serial_Number_ONU message sent to the OLT is set to 1; otherwise, it remains 0.

[0310] Table 15 Serial Number ONU Messages in 50G-PON Systems

[0311] Implementation 5B.5 OLT Broadcast Downlink Bandwidth Allocation Capability

[0312] The OLT capabilities of 50G-PON are broadcast in Table 16. Setting the R bit of byte 5 to 1 indicates support for downlink bandwidth allocation and downlink carrier allocation capabilities.

[0313] Table 16 Broadcast Capabilities of 50G-PON OLTs

[0314] Implementation Method 6B VHSP System

[0315] The various implementation methods in the VHSP system can be referenced from the various implementation methods in the 50G-PON system. The specific implementation process will not be elaborated here.

[0316] Of course, the embodiments shown in Figures 16 and 17, and various optional implementations, are also applicable to standards such as IEEE EPON, 10GEPON, and N*25G EPON. ONUs can report their downlink bandwidth processing capabilities via the REGISTER_REQ message. OLTs can add additional Logical Link Identifier (LLID) configuration commands and downlink attributes. OLTs allocate downlink bandwidth to these LLIDs via Grant Assignment Transmission Element (GATE) messages. ONUs that do not support downlink bandwidth processing capabilities discard these GATE messages via LLIDs. ONUs that support downlink bandwidth processing capabilities can parse these GATE messages and accept or reject them according to the downlink LLID configuration; this will not be elaborated further here. In the IEEE EPON series standards, each bandwidth entry is a separate GATE message, and they are independent of each other; therefore, there is no constraint similar to the ITU-T GPON series standards where bandwidth allocation entries are grouped together.

[0317] It should be noted again that although the above embodiments and various optional implementations reuse T-CONT as the downlink bandwidth carrier and reuse the uplink bandwidth allocation structure to send downlink bandwidth allocation results based on the standardized PON standard, future new standardized PON systems (such as VHSP) can also adopt this scheme. Even existing IEEE PON standards or future PON standards that are planned to be standardized can complete the configuration of downlink bandwidth carrier and downlink bandwidth allocation functions according to the methods and various optional implementations provided in this embodiment.

[0318] This application also provides a communication node, including a processor, which is configured to implement the method provided in any embodiment of this application when executing a computer program. Specifically, the communication node may be the first communication node or the second communication node described in the above embodiments.

[0319] Figure 18 is a schematic diagram of a communication node provided in one embodiment. As shown in Figure 18, the communication node includes a processor 60, a memory 61, and a communication interface 62. The number of processors 60 in the communication node can be one or more; Figure 18 shows an example of one processor 60. The processor 60, memory 61, and communication interface 62 in the communication node can be connected via a bus or other means; Figure 18 shows an example of connection via a bus. The bus can represent a collection of one or more types of bus structures, including a memory bus, a memory controller bus, a peripheral bus, a graphics acceleration port bus, a processor bus, or a local bus using any bus structure, etc.

[0320] The memory 61, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the embodiments of this application. The processor 60 executes at least one functional application and data processing of the communication node by running the software programs, instructions, and modules stored in the memory 61, thereby implementing the methods described above.

[0321] The memory 61 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on terminal usage. Furthermore, the memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 61 may include storage units remotely deployed relative to the processor 60, such remote storage units being connected to communication nodes via a network. These networks include, but are not limited to, the Internet, corporate intranets, mobile communication networks, and combinations thereof.

[0322] Communication interface 62 can be configured to receive and send data.

[0323] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0324] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, a system, apparatus, or device based on electrical, magnetic, optical, electromagnetic, infrared, or semiconductor technology, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0325] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0326] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0327] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the communication method provided in any embodiment of this application.

[0328] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0329] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0330] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0331] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0332] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A communication method applied to a first communication node, the method comprising: A downlink bandwidth carrier is allocated to the second communication node; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the same set of identifiers for the bandwidth carrier; The downlink bandwidth allocation result allocated to the downlink bandwidth carrier is sent to the second communication node through the bandwidth allocation structure; wherein, the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

2. The method according to claim 1, wherein, The identifier of the downlink bandwidth carrier remains in the same position in the bandwidth allocation structure, so that the second communication node can determine whether the bandwidth carrier is the downlink bandwidth carrier or the uplink bandwidth carrier allocated to it.

3. The method according to claim 1, wherein, The bandwidth allocation structure also includes uplink bandwidth allocation results; the uplink bandwidth allocation results are the uplink bandwidth allocated to the uplink bandwidth carrier.

4. The method according to claim 1, further comprising: Indicate the number of bandwidth allocation entries in the bandwidth allocation structure to the second communication node.

5. The method according to claim 1, wherein, The downlink bandwidth allocation result is the downlink bandwidth allocated to the downlink bandwidth carrier.

6. The method according to claim 4, wherein, The bandwidth allocation entries include: the identifier of the bandwidth carrier and bandwidth information.

7. The method according to claim 1, wherein, The allocation of downlink bandwidth carrier to the second communication node includes: The bandwidth carrier configuration information is sent to the second communication node; wherein the bandwidth carrier configuration information includes a downlink flag and an identifier of the downlink bandwidth carrier corresponding to the second communication node.

8. A communication method applied to a second communication node, the method comprising: Obtain the downlink bandwidth carrier allocated by the first communication node to the second communication node; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the identifier set of the bandwidth carrier; The downlink bandwidth allocation result of the downlink bandwidth carrier is obtained from the bandwidth allocation structure; wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

9. The method according to claim 8, wherein, The identifier of the downlink bandwidth carrier remains in the same position in the bandwidth allocation structure, so that the second communication node can determine whether the bandwidth carrier is the downlink bandwidth carrier or the uplink bandwidth carrier allocated to it.

10. The method according to claim 8, wherein, The bandwidth allocation structure also includes an uplink bandwidth allocation result; the uplink bandwidth allocation result is the uplink bandwidth allocated to the uplink bandwidth carrier, so that the second communication node can obtain the uplink bandwidth allocation result allocated to its own uplink bandwidth carrier.

11. The method of claim 8, further comprising: Obtain the number of bandwidth allocation entries in the bandwidth allocation structure sent by the first communication node, and parse the number of bandwidth allocation entries in the bandwidth allocation result.

12. The method according to claim 11, wherein, The parsing of the number of bandwidth allocation entries in the bandwidth allocation result includes: Obtain the downlink bandwidth carrier and its corresponding downlink bandwidth information, and the uplink bandwidth carrier and its corresponding uplink bandwidth information.

13. The method according to claim 8, wherein, The step of obtaining the downlink bandwidth carrier allocated by the first communication node to the second communication node includes: The downlink flag and the identifier of the downlink bandwidth carrier corresponding to the second communication node are obtained from the bandwidth carrier configuration information sent by the first communication node. The downlink bandwidth carrier identifier is used to receive the downlink bandwidth allocation result allocated by the first communication node.

14. A communication method applied to a first communication node, the method comprising: Broadcast downlink bandwidth allocation capability; Obtain a second communication node that supports downlink bandwidth processing capabilities.

15. The method of claim 14, further comprising: A downlink bandwidth carrier is allocated to the second communication node that supports downlink bandwidth processing capability; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the identifier set of the bandwidth carrier; The downlink bandwidth allocation result allocated to the downlink bandwidth carrier is sent to the second communication node that supports downlink bandwidth processing capability through the bandwidth allocation structure; wherein, the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

16. The method according to claim 15, wherein, The position of the identifier of the downlink bandwidth carrier in the bandwidth allocation structure remains unchanged, so that the second communication node that supports downlink bandwidth processing capability can determine whether the downlink bandwidth carrier is the downlink bandwidth carrier allocated to it, and the second communication node that does not support downlink bandwidth processing capability can determine that the bandwidth carrier is not the bandwidth carrier allocated to it.

17. The method according to claim 15, wherein, The bandwidth allocation structure also includes uplink bandwidth allocation results; the uplink bandwidth allocation results are the uplink bandwidth allocated to the uplink bandwidth carrier.

18. The method of claim 15, further comprising: The second communication node that supports downlink bandwidth processing capability is instructed on the number of bandwidth allocation entries in the bandwidth allocation structure.

19. The method according to claim 15, wherein, The downlink bandwidth allocation result is the downlink bandwidth allocated to the downlink bandwidth carrier.

20. The method according to claim 18, wherein, The bandwidth allocation entry includes: the identifier of the bandwidth carrier and bandwidth information.

21. The method according to claim 15, wherein, The allocation of downlink bandwidth carriers to the second communication node supporting downlink bandwidth processing capability includes: The bandwidth carrier configuration information is sent to the second communication node that supports downlink bandwidth processing capability; wherein, the bandwidth carrier configuration information includes a downlink flag and an identifier of the downlink bandwidth carrier corresponding to the second communication node that supports downlink bandwidth processing capability.

22. The method according to claim 14, wherein, The second communication node that acquires downlink bandwidth processing capability includes: Receive downlink bandwidth processing capability information sent by the second communication node: wherein the downlink bandwidth processing capability information includes those that support downlink bandwidth processing capability and those that do not support downlink bandwidth processing capability; Based on the downlink bandwidth processing capability, a second communication node that supports downlink bandwidth processing capability is obtained.

23. An information transmission method applied to a second communication node, the method comprising: When obtaining information about the downlink bandwidth allocation capability of the first communication node, the downlink bandwidth processing capability information is sent to the first communication node.

24. The method according to claim 23, wherein, In response to determining that the downlink bandwidth processing capability of the second communication node supports downlink bandwidth processing capability, the method further includes: Obtain the downlink bandwidth carrier allocated by the first communication node to the second communication node; wherein the identifier of the downlink bandwidth carrier and the identifier of the uplink bandwidth carrier share the identifier set of the bandwidth carrier; The downlink bandwidth allocation result of the downlink bandwidth carrier is obtained from the bandwidth allocation structure; wherein the bandwidth allocation structure is a reused uplink bandwidth allocation structure.

25. The method according to claim 24, wherein, The position of the identifier of the downlink bandwidth carrier in the bandwidth allocation structure remains unchanged, so that the second communication node that supports downlink bandwidth processing capability can determine whether the downlink bandwidth carrier is the downlink bandwidth carrier allocated to it, and the second communication node that does not support downlink bandwidth processing capability can determine that the bandwidth carrier is not the bandwidth carrier allocated to it.

26. The method of claim 24, wherein, The bandwidth allocation structure also includes an uplink bandwidth allocation result; the uplink bandwidth allocation result is the uplink bandwidth allocated to the uplink bandwidth carrier, so that the second communication node can obtain the uplink bandwidth allocation result allocated to its own uplink bandwidth carrier.

27. The method of claim 24, further comprising: Obtain the number of bandwidth allocation entries in the bandwidth allocation structure sent by the first communication node, and parse the number of bandwidth allocation entries in the bandwidth allocation result.

28. The method according to claim 27, wherein, The parsing of the number of bandwidth allocation entries in the bandwidth allocation result includes: Obtain the downlink bandwidth carrier and its corresponding downlink bandwidth information, and the uplink bandwidth carrier and its corresponding uplink bandwidth information.

29. The method according to claim 24, wherein, The step of obtaining the downlink bandwidth carrier allocated by the first communication node to the second communication node includes: The downlink flag and the identifier of the downlink bandwidth carrier corresponding to the second communication node are obtained from the bandwidth carrier configuration information sent by the first communication node. The downlink bandwidth carrier identifier is used to receive the downlink bandwidth allocation result allocated by the first communication node.

30. A communication node, comprising: processor; The processor is used to implement the communication method as described in any one of claims 1 to 29 when executing a computer program.

31. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the communication method as described in any one of claims 1 to 29.

Images