Dynamic bandwidth allocation method for mixed services and olt device

Abstract

This invention discloses a dynamic bandwidth allocation method for mixed services: The OLT slices services within the same ODN network according to service type, and configures DBA-related parameter vectors for the slices and the tcont / llids within each slice; a slice can contain multiple tcont / llids, and tcont / llids within a slice can belong to different ONUs; a first-level slice-based bandwidth calculation is performed; a valid window for the first-level slice-based bandwidth calculation is periodically generated, within which bandwidth calculation can be performed; a second-level tcont / llid-based bandwidth calculation is performed, obtaining the DBA-related parameter vector of the tcont / llid, obtaining the slice identifier to which the tcont / llid belongs, and calculating the tcont / llid based on the total bandwidth of the slice; and bandwidth authorization is issued based on the bandwidth authorization period configured for the tcont / llid. This invention improves the flexibility of the PON system and increases the efficiency of dynamic bandwidth allocation. This invention also provides corresponding OLT equipment.

Description

Technical Field

[0001] This invention belongs to the field of communication technology, and more specifically, relates to a dynamic bandwidth allocation method and OLT device for mixed services. Background Technology

[0002] In existing PON (Passive Optical Network) systems, services are based on tcont / llid mapping. DBA (Dynamic Bandwidth Assignment) uses tcont / llid as the basic unit for calculation and authorization allocation. The bandwidth calculation cycle for mixed services within the same ODN (Optical Distribution Network) must remain consistent. Mixed services with different latency requirements are achieved by changing the bandwidth delivery cycle of tcont / llid. For example, for services with low latency requirements, the bandwidth authorization delivery cycle is equal to the bandwidth calculation cycle, and delivery is performed after each calculation. For services with non-low latency requirements, the bandwidth authorization delivery cycle can be equal to a multiple of the bandwidth calculation cycle, with multiple calculations performed and the results accumulated before delivery. Therefore, the bandwidth authorization delivery cycle must be configured with the bandwidth calculation cycle as the granularity.

[0003] As the application scenarios of PON systems become more and more widespread, the demand for mixed services with different latency requirements to access the same ODN network is increasing. The following problems exist with the use of existing technologies: (1) The bandwidth authorization issuance cycle depends on the bandwidth calculation cycle, which has low flexibility and limits some latency requirements; (2) Non-low latency services need to be compatible with low latency services, which requires frequent calculations, resulting in high power consumption of the product. Summary of the Invention

[0004] In view of the above-mentioned defects or improvement needs of the existing technology, the present invention provides a dynamic bandwidth allocation scheme for mixed services to achieve a more flexible and efficient scheduling system.

[0005] To achieve the above objectives, according to one aspect of the present invention, a dynamic bandwidth allocation method for mixed services is provided, comprising the following steps:

[0006] S1: The OLT slices services under the same ODN network according to service type, and configures DBA-related parameter vectors for slices and tcont / llid within slices; a slice can contain multiple tcont / llid, and tcont / llid within a slice can belong to different ONUs;

[0007] S2: Perform the first-level slice-based bandwidth calculation; periodically generate an effective window for the first-level slice-based bandwidth calculation, within which bandwidth calculation can be performed;

[0008] S3: Perform the second-level bandwidth calculation based on tcont / llid, obtain the DBA-related parameter vector of tcont / llid, obtain the slice identifier to which tcont / llid belongs, and calculate tcont / llid in combination with the total bandwidth of the slice to which it belongs;

[0009] S4: Grants authorization based on the bandwidth authorization period configured in tcont / llid.

[0010] In one embodiment of the present invention, the DBA-related parameter vector of the slice includes bandwidth calculation period, bandwidth type and bandwidth resources; the DBA-related parameter vector of tcont / llid contained in the slice includes bandwidth calculation period, bandwidth type, bandwidth resources and bandwidth authorization issuance period.

[0011] In one embodiment of the present invention, step S1 specifically includes the following sub-steps:

[0012] S101: Configure the slice and the bandwidth type and bandwidth resources of tcont / llid within the slice; services with similar latency requirements belong to the same slice, configure the slice identifier for each tcont / llid according to the latency requirements; configure the bandwidth for each slice according to the service type.

[0013] S102: Configure the slice and the bandwidth calculation cycle of tcont / llid within the slice. The bandwidth calculation cycle based on the slice is configured according to the DBA convergence time required by the system.

[0014] In one embodiment of the present invention, in step S101, fixed bandwidth resources are allocated to the slices to which services with high latency requirements belong, and best-effort bandwidth resources are allocated to the slices to which services with low latency requirements belong; fixed bandwidth has the highest priority and is satisfied to the fullest extent according to the configuration size, while best-effort bandwidth has the lowest priority.

[0015] In one embodiment of the present invention, step S2 specifically includes the following sub-steps:

[0016] S201: Maintain a timer T1 to periodically generate the first-level effective window based on slice bandwidth calculation;

[0017] S202: Periodically obtain the bandwidth requirements based on slices. The bandwidth requirements based on slices are the sum of the bandwidth requirements M1 of tcont / llid contained in each slice. i , where i is the slice identifier;

[0018] S203: Based on the slice and the calculation cycle configuration information of tcont / llid within the slice, modify M1 obtained in step S202. i A second calculation is performed to obtain the result M2.i This refers to the bandwidth that can be allocated within a single cycle; M2 stores the secondary calculation results of each slice. i Used for S3 operations.

[0019] In one embodiment of the present invention, in step S202, at the beginning of each bandwidth calculation cycle, the bandwidth required for each slice is calculated based on the slice bandwidth configuration information and traffic requirements; wherein, the total bandwidth is the total system bandwidth of an ODN network, and the granularity of the slice bandwidth calculation can be configured according to requirements, and is not related to the granularity of the tcont / llid bandwidth calculation, and can be configured independently.

[0020] In one embodiment of the present invention, step S3 specifically includes the following sub-steps:

[0021] S301: Each slice maintains a timer T2 i This is used to periodically generate a second-level effective window based on tcont / llid bandwidth calculation;

[0022] S302: Sequentially obtain the bandwidth calculation related parameter vector for each tcont / llid. If the current time is within the calculation effective window of the slice to which the tcont / llid belongs and the remaining bandwidth that can be allocated to the slice is not 0, then the tcont / llid enters the bandwidth calculation process; otherwise, skip obtaining the related parameters of the next tcont / llid until all tcont / llid calculations are completed.

[0023] S303: Perform tcont / llid bandwidth calculation; the tcont / llid bandwidth calculation is performed in multiple rounds in the order of fixed bandwidth, guaranteed bandwidth, and non-guaranteed bandwidth.

[0024] In one embodiment of the present invention, in step S303, when the first tcont / llid within a slice is calculated in the first round, the total bandwidth M2 of each slice obtained in step S2 is... i The upper limit of the currently allocable bandwidth for tcont / llid is used as the basis for the first round of bandwidth calculation; after each round of calculation, the bandwidth allocated to each slice in the current round is obtained. Where i is the slice identifier and j is the calculation round, the remaining bandwidth N of each slice is obtained based on this. i Where i is the slice identifier, and the calculation formula is: Within a slice, when the first tcont / llid is not in the first round of calculation, the remaining bandwidth N of each slice is... i This is the upper limit of the bandwidth that can be allocated to the current tcont / llid. Bandwidth calculations are then performed based on this limit until all rounds have been calculated. The bandwidth calculation result G for each tcont / llid is stored. kUsed for S4 operations, where k is the tcont / llid identifier.

[0025] In one embodiment of the present invention, step S4 specifically includes the following sub-steps:

[0026] S401: Each tcont / llid maintains a timer Where i is the slice identifier and k is the tcont / llid identifier, used to periodically generate bandwidth authorization distribution instructions. With T2 i The counting is performed at the granular level within a given period.

[0027] S402: Sequentially obtain the bandwidth grant distribution parameter vector for each tcont / llid. When the first calculation of tcont / llid ends, if the current timer matches the bandwidth grant distribution cycle configuration, then distribute the bandwidth grant for that tcont / llid. The bandwidth size is equal to G obtained in step S3. k If they do not match, then the G obtained in step S3 will be... k Accumulation; when a non-first calculation of tcont / llid ends, if the current timer matches the bandwidth grant issuance cycle configuration, then the bandwidth grant for tcont / llid is issued, and the bandwidth size is equal to G calculated in the previous n calculations. k Accumulated value Where n>=1, if there is no match, then continue to accumulate G. k value;

[0028] Repeat step S402 to periodically issue bandwidth authorizations.

[0029] According to another aspect of the present invention, an OLT device is also provided, including at least one processor and a memory, wherein the at least one processor and the memory are connected via a data bus, and the memory stores instructions executable by the at least one processor, wherein the instructions, after being executed by the processor, are used to complete the dynamic bandwidth allocation method for the mixed services.

[0030] In summary, the technical solutions conceived by this invention have the following beneficial effects compared with the prior art:

[0031] (1) In this invention, the entire system can be sliced ​​based on the dimension of bandwidth calculation cycle, and independent bandwidth calculation can be realized within the slice. The bandwidth and authorization issuance cycle can be configured in multiple levels to meet different service requirements, which greatly improves the flexibility of the PON system.

[0032] (2) In this invention, for application scenarios that combine low-latency services and non-low-latency services, the number of bandwidth calculations is reduced, power consumption is greatly reduced, and the efficiency of dynamic bandwidth allocation is improved. Attached Figure Description

[0033] Figure 1 This is a flowchart illustrating the dynamic bandwidth allocation method in an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram illustrating the logical relationship for implementing hybrid slicing in an embodiment of the present invention;

[0035] Figure 3 This is a detailed operational diagram of the dynamic bandwidth allocation method in an embodiment of the present invention;

[0036] Figure 4 This is a schematic diagram of the structure of an OLT device according to an embodiment of the present invention. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. Furthermore, the technical features involved in the various embodiments of this invention described below can be combined with each other as long as they do not conflict with each other.

[0038] This invention provides a dynamic bandwidth allocation method for mixed services, applied to PON systems encompassing PON / 10G EPON / XGSPON / NGPON2 / 50G PON, suitable for multi-service mixed scheduling scenarios with varying latency requirements. The aim is to provide a slice-based dynamic bandwidth allocation method based on latency requirements, achieving a more flexible and efficient scheduling system. The method includes the following steps:

[0039] S1: The OLT slices services under the same ODN network according to the service type, and configures DBA-related parameter vectors for the slice and the tcont / llid within the slice; a slice can contain multiple tcont / llid, and the tcont / llid within a slice can belong to different ONUs.

[0040] The DBA-related parameter vector for a slice includes bandwidth calculation cycle, bandwidth type, and bandwidth resource configuration. The DBA-related parameter vector for tcont / llid contained in a slice includes bandwidth calculation cycle, bandwidth type, bandwidth resource configuration, and bandwidth license allocation cycle.

[0041] In actual operation, step S1 specifically includes the following steps:

[0042] S101: Configure the slice and the tcont / llid bandwidth type and bandwidth resources within the slice.

[0043] Services with similar latency requirements belong to the same slice. Slice identifiers are configured for each tcont / llid according to latency requirements, and bandwidth is configured for each slice according to service type.

[0044] Preferably, fixed bandwidth resources are allocated to slices belonging to services with high latency requirements, while best-effort bandwidth resources are allocated to slices belonging to services with low latency requirements. Specifically, fixed bandwidth has the highest priority and is satisfied to the fullest extent of the configuration, while best-effort bandwidth has the lowest priority and can be allocated only when there is remaining bandwidth in the current system.

[0045] Furthermore, the bandwidth type can be flexibly configured for each slice and tcont / llid according to system requirements.

[0046] S102: Configure the slice and the bandwidth calculation cycle of tcont / llid within the slice. The bandwidth calculation cycle based on the slice is configured according to the DBA convergence time required by the system.

[0047] The tcont / llid bandwidth calculation period for different slices can be configured independently, while the tcont / llid bandwidth calculation period within the same slice remains consistent. For example, the bandwidth calculation period for a slice can be configured to 10µs, 100µs, 1ms, etc., according to latency requirements.

[0048] Furthermore, the bandwidth calculation cycle can be configured to be on a smaller or larger time scale depending on the system's computing power and processing speed.

[0049] The bandwidth calculation cycle parameter based on the slice is not related to the tcont / llid bandwidth calculation parameter within the slice and can be configured independently.

[0050] S2: Perform the first-level slice bandwidth calculation.

[0051] S201: Maintain a timer T1 to periodically generate the first-level effective window based on slice bandwidth calculation.

[0052] Preferably, the start and end markers of the effective bandwidth calculation window are generated according to the slice-based bandwidth calculation cycle configuration. Bandwidth calculation can be performed within the effective window, and the bandwidth calculation uses a dedicated algorithm module.

[0053] Furthermore, within the effective window of the slice-based bandwidth calculation, the algorithm module for the second level of step S3 based on tcont / llid bandwidth calculation is monitored to see if it is in an idle state. If it is in an idle state, the current bandwidth calculation is performed; if it is in a busy state, the current bandwidth calculation is stopped. This method can share the bandwidth calculation algorithm module.

[0054] S202: Preferably, the bandwidth requirement based on slices is acquired periodically. The bandwidth requirement can be obtained from the bandwidth requirement report submitted by tcont / llid, or from monitoring uplink traffic. The bandwidth requirement based on slices is the sum of the bandwidth requirements M1 of the tcont / llids contained in each slice. i , where i is the slice identifier.

[0055] Furthermore, at the start of each bandwidth calculation cycle, the bandwidth required for each slice is calculated based on the slice bandwidth configuration information and traffic requirements. The total bandwidth refers to the total system bandwidth of an ODN network. The granularity of the slice bandwidth calculation can be configured according to requirements and is independent of the granularity of the tcont / llid bandwidth calculation.

[0056] The bandwidth calculation algorithm is a general algorithm and is not involved in this invention. The calculation result M1 is obtained after the calculation is completed. i , where i is the slice identifier, and the same applies below. M1 i The unit can be bps (bits per second) or gs (grant size) / tq (time quantum).

[0057] S203: Based on the slice and the calculation cycle configuration information of tcont / llid within the slice, modify M1 obtained in step S202. i A second calculation is performed to obtain the result M2. i The calculation formula is: M2 i＝ M1 i / P i , where P i The bandwidth is calculated as (the bandwidth calculation cycle of tcont / llid within the slice) / (the bandwidth calculation cycle based on the slice), which represents the allocatable bandwidth within a single cycle. The secondary calculation results M2 for each slice are stored. i Used for S3 operations.

[0058] S3: Perform the second-level bandwidth calculation based on tcont / llid.

[0059] Obtain the DBA-related parameter vector of tcont / llid to get the slice identifier to which tcont / llid belongs. Calculate tcont / llid based on the total bandwidth of the slice to which it belongs.

[0060] In actual operation, step S3 specifically includes the following steps:

[0061] S301: Each slice maintains a timer T2 iWhere 'i' is the slice identifier, used to periodically generate the second-level effective window for bandwidth calculation based on tcont / llid. The start and end identifiers of the effective bandwidth calculation window are generated according to the bandwidth calculation parameters configured for the slice, and are generated once per cycle. A start identifier is generated at the beginning of the current calculation cycle, and an end identifier is generated when all tcont / llid calculations within that slice are completed. The bandwidth calculation windows of all slices are monitored in real time. If there is an effective window equal to or greater than that of one slice, the next step is performed; otherwise, monitoring continues.

[0062] S302: Sequentially obtain the bandwidth calculation related parameter vector for each tcont / llid. If the current time is within the calculation effective window of the slice to which the tcont / llid belongs and the remaining bandwidth that can be allocated to the slice is not 0, then the tcont / llid enters the bandwidth calculation process; otherwise, skip obtaining the related parameters of the next tcont / llid until all tcont / llid calculations are completed.

[0063] S303: Perform tcont / llid bandwidth calculation. The tcont / llid bandwidth calculation is performed in multiple rounds, following the order of fixed bandwidth, guaranteed bandwidth, and non-guaranteed bandwidth. The specific bandwidth calculation algorithm is not covered in this invention. When the first tcont / llid within a slice is calculated in the first round, the total bandwidth M2 of all slices obtained in step S2 is... i The first round of bandwidth calculation is based on the upper limit of the currently allocable bandwidth for tcont / llid. After each round of calculation, the bandwidth allocated to each slice in the current round is obtained. Where i is the slice identifier and j is the calculation round, the remaining bandwidth N of each slice is obtained based on this. i Where i is the slice identifier, and the calculation formula is: Within a slice, when the first tcont / llid is not in the first round of calculation, the remaining bandwidth N of each slice is... i This sets the upper limit of allocable bandwidth for the current tcont / llid, and continues bandwidth calculation based on this limit until all rounds have been calculated. The bandwidth calculation result G for each tcont / llid is stored. k Used for S4 operations, where k is the tcont / llid identifier.

[0064] S4: Grants authorization based on the bandwidth authorization period configured in tcont / llid.

[0065] In practice, the following steps are included:

[0066] S401: Each tcont / llid maintains a timer Where i is the slice identifier and k is the tcont / llid identifier, used to periodically generate bandwidth authorization distribution instructions. With T2 i Count the particle size.

[0067] S402: Sequentially obtain the bandwidth grant distribution parameter vector for each tcont / llid. When the first calculation of tcont / llid ends, if the current timer matches the bandwidth grant distribution cycle configuration, then distribute the bandwidth grant for that tcont / llid. The bandwidth size is equal to G obtained in step S3. k If they do not match, then the G obtained in step S3 will be... k Accumulation. When a non-first calculation of tcont / llid ends, if the current timer matches the bandwidth grant issuance cycle configuration, then the bandwidth grant for tcont / llid is issued, and the bandwidth size is equal to G calculated in the previous n calculations. k Accumulated value Where n>=1, if there is no match, then continue to accumulate G. k value.

[0068] Repeat step S402 to periodically issue bandwidth authorizations.

[0069] Furthermore, the present invention also provides an OLT device, including at least one processor and a memory, wherein the at least one processor and the memory are connected via a data bus, and the memory stores instructions that can be executed by the at least one processor, wherein the instructions, after being executed by the processor, are used to complete the dynamic bandwidth allocation method for the mixed services.

[0070] This invention also provides an OLT device for more flexible and efficient dynamic bandwidth allocation for mixed services. For example... Figure 4 As shown, the main computational function for dynamic bandwidth allocation in the OLT device is the bandwidth calculation module. Both the first-level slice-based and second-level tcont / llid-based bandwidth calculations are performed by the bandwidth calculation module. Timers T1 and T2 generate valid calculation windows, and the corresponding calculation functions are performed within each valid window. When the first-level and second-level calculation windows conflict, the second-level calculation window has higher priority.

[0071] The parameters required by the bandwidth calculation module are provided by the DBA-related configuration modules, including those based on slices and those based on tcont / llid. These DBA-related parameters include the bandwidth calculation cycle, bandwidth type, and bandwidth resource allocation.

[0072] The bandwidth calculation module also needs to collect the traffic demand of the ONU. The traffic demand is obtained by the ONU by sending a traffic report or by the OLT self-detecting the uplink traffic status of the ONU and then performing secondary calculations and predictions. This function is implemented in the traffic demand calculation module, including slicing-based and tcont / llid-based methods.

[0073] After the bandwidth calculation module completes the calculation, it outputs the result to the bandwidth authorization distribution module. The bandwidth authorization distribution module completes the final bandwidth authorization distribution according to the T3 timer control instruction and the bandwidth authorization distribution cycle based on tcont / llid in the DBA parameter vector.

[0074] Those skilled in the art will readily understand that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A dynamic bandwidth allocation method for mixed services, characterized in that, Includes the following steps: S1: The OLT slices services under the same ODN network according to service type, and configures DBA-related parameter vectors for the slice and the tcont / llid within the slice; a slice can contain multiple tcont / llids, and the tcont / llids within a slice can belong to different ONUs; in step S1, the DBA-related parameter vector of the slice includes bandwidth calculation period, bandwidth type, and bandwidth resources; the DBA-related parameter vector of the tcont / llids contained in the slice includes bandwidth calculation period, bandwidth type, bandwidth resources, and bandwidth authorization distribution period; S2: Perform the first-level slice-based bandwidth calculation; periodically generate an effective window for the first-level slice-based bandwidth calculation, within which bandwidth calculation can be performed; step S2 specifically includes the following sub-steps: S201: Maintain a timer T1 to periodically generate the first-level effective window based on slice bandwidth calculation; S202: Periodically obtain the bandwidth requirements based on slices. The bandwidth requirements based on slices are the sum of the bandwidth requirements M1 of tcont / llid contained in each slice. i , where i is the slice identifier; S203: Based on the slice and the calculation cycle configuration information of tcont / llid within the slice, modify M1 obtained in step S202. i A second calculation is performed to obtain the result M2. i This refers to the bandwidth that can be allocated within a single cycle; M2 stores the secondary calculation results of each slice. i Used for S3 operations; S3: Perform the second-level bandwidth calculation based on tcont / llid, obtain the DBA-related parameter vector of tcont / llid, obtain the slice identifier to which tcont / llid belongs, and calculate tcont / llid in conjunction with the total bandwidth of the slice to which it belongs; step S3 specifically includes the following sub-steps: S301: Each slice maintains a timer T2 i This is used to periodically generate a second-level effective window based on tcont / llid bandwidth calculation; S302: Sequentially obtain the bandwidth calculation related parameter vector for each tcont / llid. If the current time is within the calculation effective window of the slice to which the tcont / llid belongs and the remaining bandwidth that can be allocated to the slice is not 0, then the tcont / llid enters the bandwidth calculation process; otherwise, skip obtaining the related parameters of the next tcont / llid until all tcont / llid calculations are completed. S303: Perform tcont / llid bandwidth calculation; the tcont / llid bandwidth calculation is performed in multiple rounds in the order of fixed bandwidth, guaranteed bandwidth, and non-guaranteed bandwidth. S4: Grant authorization based on the bandwidth authorization period configured in tcont / llid; step S4 specifically includes the following sub-steps: S401: Each tcont / llid maintains a timer Where i is the slice identifier and k is the tcont / llid identifier, used to periodically generate bandwidth grant distribution instructions. With T2 i The counting is performed at the granular level within a given period. S402: Sequentially obtain the bandwidth grant distribution parameter vector for each tcont / llid. When the first calculation of tcont / llid ends, if the current timer matches the bandwidth grant distribution cycle configuration, then distribute the bandwidth grant for that tcont / llid. The bandwidth size is equal to G obtained in step S3. k If they do not match, then the G obtained in step S3 will be... k Accumulation; when a non-first calculation of tcont / llid ends, if the current timer matches the bandwidth grant issuance cycle configuration, then the bandwidth grant for tcont / llid is issued, and the bandwidth size is equal to G calculated in the previous n calculations. k Accumulated value Where n>=1, if no match is found, the sum continues to accumulate. value; Repeat step S402 to periodically issue bandwidth authorizations.

2. The dynamic bandwidth allocation method for hybrid services as described in claim 1, characterized in that, Step S1 specifically includes the following sub-steps: S101: Configure the slice and the bandwidth type and bandwidth resources of tcont / llid within the slice; services with similar latency requirements belong to the same slice, configure the slice identifier for each tcont / llid according to the latency requirements; configure the bandwidth for each slice according to the service type; S102: Configure the slice and the bandwidth calculation cycle of tcont / llid within the slice. The bandwidth calculation cycle based on the slice is configured according to the DBA convergence time required by the system.

3. The dynamic bandwidth allocation method for hybrid services as described in claim 1, characterized in that, In step S101, fixed bandwidth resources are allocated to the slices of services with high latency requirements, and best-effort bandwidth resources are allocated to the slices of services with low latency requirements. Fixed bandwidth has the highest priority and is satisfied to the fullest extent according to the configuration size, while best-effort bandwidth has the lowest priority.

4. The dynamic bandwidth allocation method for hybrid services as described in claim 1, characterized in that, In step S202, at the beginning of each bandwidth calculation cycle, the bandwidth required for each slice is calculated based on the slice bandwidth configuration information and traffic requirements. The total bandwidth is the total system bandwidth of an ODN network. The granularity of the slice bandwidth calculation can be configured according to requirements and is not related to the granularity of the tcont / llid bandwidth calculation. It can be configured independently.

5. The dynamic bandwidth allocation method for hybrid services as described in claim 1, characterized in that, In step S303, when the first tcont / llid within a slice is calculated in the first round, the total bandwidth M2 of each slice obtained in step S2 is... i The upper limit of the currently allocable bandwidth for tcont / llid is used as the basis for the first round of bandwidth calculation; after each round of calculation, the bandwidth allocated to each slice in the current round is obtained. Where i is the slice identifier and j is the calculation round, the remaining bandwidth N of each slice is obtained based on this. i Where i is the slice identifier, and the calculation formula is N. i =M i - ; Within a slice, when the first tcont / llid is not in the first round of calculation, the remaining bandwidth N of each slice is... i This is the upper limit of the bandwidth that can be allocated to the current tcont / llid. Bandwidth calculations are then performed based on this limit until all rounds have been calculated. The bandwidth calculation result G for each tcont / llid is stored. k Used for S4 operations, where k is the tcont / llid identifier.

6. An OLT device, characterized in that: It includes at least one processor and a memory, which are connected via a data bus. The memory stores instructions that can be executed by the at least one processor. After being executed by the processor, the instructions are used to complete the dynamic bandwidth allocation method for hybrid services according to any one of claims 1-5.

Images