CN111464886B - Co-DBA method and system compatible with different time delay requirements - Google Patents
Co-DBA method and system compatible with different time delay requirements Download PDFInfo
- Publication number
- CN111464886B CN111464886B CN202010136735.2A CN202010136735A CN111464886B CN 111464886 B CN111464886 B CN 111464886B CN 202010136735 A CN202010136735 A CN 202010136735A CN 111464886 B CN111464886 B CN 111464886B
- Authority
- CN
- China
- Prior art keywords
- authorization
- dba
- issued
- time
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q11/0067—Provisions for optical access or distribution networks, e.g. Gigabit Ethernet Passive Optical Network (GE-PON), ATM-based Passive Optical Network (A-PON), PON-Ring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0079—Operation or maintenance aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0086—Network resource allocation, dimensioning or optimisation
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method and a system for Co-DBA compatible with different time delay requirements, relating to the technical field of PON (passive optical network). the invention provides an interactive interface through an OLT (optical line terminal) for transmitting Co-DBA scheduling information and acquiring Co-DBA authorization information to be issued and fed back by a CU/DU (Central Unit/data Unit); meanwhile, the calculation function of SR/TM DBA authorization information through flow report analysis and flow monitoring between the ONU is reserved, and two DBA modes compatible with different delay requirements are provided. The OLT carries out authorization sequence arbitration according to a low-delay service priority principle and in combination with DBA authorization information, monitors two DBA authorizations in real time, dynamically adjusts out-of-order authorization, and guarantees bandwidth utilization rate while guaranteeing real-time performance to the maximum extent.
Description
Technical Field
The invention relates to the technical field of PON (passive optical network), in particular to a Co-DBA (Co-DBA) method and system compatible with different time delay requirements.
Background
The traditional DBA (Dynamic bandwidth allocation) is implemented by using an SR (State Report)/TM (Traffic Monitoring) mode or a Fixed bandwidth mode, and uplink allocation of the PON system by using the traditional DBA always performs a tradeoff between bandwidth efficiency and delay.
SR/TM DBA: the bandwidth is preferably multiplexed to a certain extent, but the bandwidth allocation is performed passively by feeding back the traffic information through the ONU in this manner, so that the delay is too large to meet the requirement of the 5G eccri interface.
Fixed DBA: the bandwidth is fixedly transmitted, response time is not needed, delay is only dependent on burst rate, but due to periodic transmission, line data flow is not considered, and bandwidth waste is too large.
In order to meet the low-delay requirement of real-time services, ITU-T defines a Co-DBA (collaboration DBA) mode to realize the uplink bandwidth allocation of the PON system. As shown in fig. 1, this way is to inform the OLT about the desired bandwidth information of one or more RUs (remote units) controlled by the OLT in a specific time in the future through a central unit/DU (distributed units), and the OLT adjusts the upstream bandwidth to provide enough bandwidth to satisfy the traffic required by the RUs, so as to minimize the transmission delay. The Co-DBA method is suitable for low-latency services, and in the same network, the low-latency services often occupy only a part of the uplink bandwidth, which may cause a large amount of bandwidth waste if the system only supports the low-latency services.
In the prior art, when a SR/TM mode DBA and Co-DBA are supported in the same PON to be used in a mixed manner, the mixed application is simple time division multiplexing or single selection, and dynamic adjustment and authorization sequencing cannot be flexibly performed according to the real-time bandwidth use condition and bandwidth requirement of a network.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a Co-DBA method and a Co-DBA system compatible with different time delay requirements, which can monitor two DBA authorizations of SR/TM and Co-DBA in real time, and ensure the bandwidth utilization rate while preferentially ensuring the real-time performance.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows: a method for compatible Co-DBA with different time delay requirements comprises a step S1 and a step S2 which are not separated in sequence, and further comprises a step S3:
s1, the OLT provides Co-DBA scheduling information to the CU/DU through the interactive interface, obtains Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, stores the Co-DBA authorization information in a Co-DBA authorization cache, and enters step S3;
s2, an SR/TM DBA generation module of the OLT carries out flow monitoring on ONU uplink service flow according to a flow report provided by the ONU, calculates SR/TM DBA authorization information to be issued, stores the SR/TM DBA authorization information in an SR/TM DBA authorization cache, and enters step S3;
s3, the OLT calculates the authorization time interval with the last authorized according to the comparison between the authorization starting time in the Co-DBA authorization information to be issued and the finish time of the last authorized; and issuing the SR/TM DBA authorization or the Co-DBA authorization to be issued according to the size of the authorization time interval.
On the basis of the technical scheme, the Co-DBA scheduling information comprises a calculation period of the DBA, an authorized issuing period, registration information of the ONU and the service type of each TCONT/LLID.
On the basis of the above technical solution, the Co-DBA authorization information further includes: TCONT/LLID and authorization size corresponding to the authorization; the SR/TM DBA authorization information comprises: the TCONT/LLID and grant size for which the grant corresponds.
On the basis of the above technical solution, step S3 specifically includes the following steps:
s301: judging whether the Co-DBA authorization cache is empty or not, if so, jumping to the step S302, if not, performing authorization sequence arbitration, if the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, jumping to the step S303, otherwise, jumping to the step S304;
s302: judging whether the SR/TM DBA authorized cache is empty, and jumping to an initial state S301 if the SR/TM DBA authorized cache is empty; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s303: calculating a difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise adding the Co-DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s304: calculating the authorization starting time + authorization size-last authorized ending time of Co-DBA to be issued to obtain a result M, if M is larger than the minimum issuing authorization size, cutting the Co-DBA authorization, correcting the authorization starting time to last authorized ending time, wherein the authorization size is M, adding the Co-DBA authorization cut into an authorization queue to be issued, and waiting for issuing at a fixed time; if M is not larger than the minimum issuing authorization size, discarding the authorization;
s305: judging whether the size of the SR/TM DBA authorization to be issued is larger than the difference G ' between the SR/TM DBA authorization start time to be issued and the last authorization finish time, if so, cutting the SR/TM DBA authorization size into G ', adding the G ' into an authorization queue to be issued, issuing at a fixed moment, keeping the rest of the authorization in an SR/TM DBA authorization cache, and waiting for the next authorization sequence arbitration; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
in the above process, when adding the grant into the grant queue to be issued, the end time information of the grant is stored as the end time of the last grant, and is used for performing the next grant sequence arbitration.
On the basis of the technical scheme, the method further comprises the following steps: in S304, the Co-DBA authorization is cut and added into an authorization queue to be issued, after a fixed time is issued, the authorization related information is fed back to the CU/DU, the authorization related information comprises the current authorization TCONT/LLID information, the sending state and the authorization size.
On the basis of the technical scheme, whether the Co-DBA authorized cache is empty is judged, protection time is set, and the Co-DBA authorized cache is judged to be empty if no Co-DBA authorization exists in the protection time.
The invention also provides a Co-DBA system compatible with different time delay requirements, which comprises the following units:
a CU/DU to: obtaining Co-DBA scheduling information from the OLT through an interactive interface, and feeding back Co-DBA authorization information to be issued to the OLT according to the Co-DBA scheduling information;
the OLT comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorization issuing module, wherein:
a Co-DBA generation module to: providing Co-DBA scheduling information to a CU/DU through an interactive interface, obtaining Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, and storing the Co-DBA authorization information in a Co-DBA authorization cache;
an SR/TM DBA generation module to: according to a flow report provided by the ONU or flow monitoring is carried out on the ONU upstream service flow, SR/TM DBA authorization information to be issued is calculated and stored in SR/TM DBA authorization cache;
an authorization issuing module for: according to the comparison between the authorization starting time in the Co-DBA authorization information and the last authorized ending time, calculating the authorization time interval with the last authorized; and issuing the SR/TM DBA authorization or the Co-DBA authorization to be issued according to the size of the authorization time interval.
On the basis of the technical scheme, the Co-DBA scheduling information comprises a calculation period of the DBA, an authorized issuing period, registration information of the ONU and the service type of each TCONT/LLID.
On the basis of the above technical solution, the Co-DBA authorization information further includes: TCONT/LLID and authorization size corresponding to the authorization; the SR/TM DBA authorization information comprises: the TCONT/LLID and grant size for which the grant corresponds.
On the basis of the technical scheme, the authorization issuing module is specifically configured to:
s301: judging whether the Co-DBA authorization cache is empty or not, if so, jumping to the step S302, if not, performing authorization sequence arbitration, if the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, jumping to the step S303, otherwise, jumping to the step S304;
s302: judging whether the SR/TM DBA authorized cache is empty, and jumping to an initial state S301 if the SR/TM DBA authorized cache is empty; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s303: calculating a difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise adding the Co-DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s304: calculating the authorization starting time + authorization size-last authorized ending time of Co-DBA to be issued to obtain a result M, if M is larger than the minimum issuing authorization size, cutting the Co-DBA authorization, correcting the authorization starting time to last authorized ending time, wherein the authorization size is M, adding the Co-DBA authorization cut into an authorization queue to be issued, and waiting for issuing at a fixed time; if M is not larger than the minimum issuing authorization size, discarding the authorization;
s305: judging whether the size of the SR/TM DBA authorization to be issued is larger than the difference G 'between the SR/TM DBA authorization start time to be issued and the last authorized end time, if so, cutting the SR/TM DBA authorization size into G', entering an authorization queue to be issued, issuing at a fixed time, keeping the rest of authorization in an SR/TM DBA authorization cache, and waiting for the next authorization sequence arbitration; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
in the above process, when adding the grant into the grant queue to be issued, the end time information of the grant is stored as the end time of the last grant, and is used for performing the next grant sequence arbitration.
On the basis of the above technical solution, the authorization issuing module is further configured to: and adding the Co-DBA authorization after cutting into an authorization queue to be issued, and feeding back authorization related information to the CU/DU after waiting for issuing at a fixed time, wherein the authorization related information comprises current authorization TCONT/LLID information, a sending state and an authorization size.
On the basis of the technical scheme, the authorization issuing module judges whether the Co-DBA authorization cache is empty or not, protection time is set, and if no Co-DBA authorization exists in the protection time, the Co-DBA authorization cache is judged to be empty.
Compared with the prior art, the invention has the advantages that:
(1) the invention provides an interactive interface through OLT to transmit Co-DBA scheduling information and obtain Co-DBA authorization information fed back by CU/DU; meanwhile, the calculation function of SR/TM DBA authorization information through flow report analysis and flow monitoring between the ONU is reserved, and two DBA modes compatible with different delay requirements are provided.
(2) The OLT carries out authorization sequence arbitration according to a low-delay service priority principle and in combination with DBA authorization information, monitors two DBA authorizations in real time, dynamically adjusts out-of-order authorization, and guarantees bandwidth utilization rate while guaranteeing real-time performance to the maximum extent.
Drawings
FIG. 1 is a schematic diagram of an application scenario of a Co-DBA method in the background art;
FIG. 2 is a flow chart illustrating a method for implementing a Co-DBA with different latency requirements according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of modules of a method for implementing compatibility between Co-DBAs with different latency requirements according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating the process of grant sequence arbitration and grant issue of the Co-DBA method compatible with different latency requirements according to the embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.
The embodiment of the invention provides a Co-DBA method compatible with different delay requirements, which is applied to an XGSPON/NGPON2 or PON system with higher speed, and aims to preferentially ensure real-time and effectively improve the bandwidth utilization rate on the basis of realizing the support of different delay service requirements. Referring to fig. 2, the method includes steps S1 and S2 in no order, and further includes step S3:
s1: the OLT provides an interactive interface for interacting Co-DBA scheduling information with the CU/DU to generate authorization information of low-delay service. The interactive interface can adopt a hardware interactive interface or a software interactive interface.
As shown in fig. 3, the providing, by the OLT, scheduling information interacting with the CUs/DUs includes: a calculation period of the DBA, an authorized issuing period, registration information of the ONU, and a service type of each TCONT (Transmission CONT, Transmission container)/LLID (Logical Link Identifier). While periodically providing real-time remaining bandwidth allocation information. And informing the current OLT bandwidth issuing state of the CU/DU in real time for the CU/DU to adjust and optimize the bandwidth calculation.
The Co-DBA authorization information provided by the CU/DU in real time comprises: TCONT/LLID corresponding to the authorization, authorization starting time and authorization size. The authorization starting time refers to that the ONU starts to transmit corresponding TCONT/LLID data at the moment, and the authorization size refers to the duration of the ONU continuously transmitting the data. The OLT obtains the information from the CU/DU through the interactive interface and stores the information into a Co-DBA authorization cache of the OLT.
And the CU/DU calculates the Co-DBA authorization information through a fairness algorithm according to the hierarchy, type and real-time service requirement of the service and the real-time allocable bandwidth information of the OLT.
S2: the OLT maintains authorization information for the conventional SR/TM DBA generation module to generate non-low latency traffic.
The module calculates the authorization information of the non-low-delay service through a flow report provided by the ONU or flow monitoring on the ONU uplink service flow.
Wherein, SR/TM DBA authorization information includes: TCONT/LLID, grant size, to which the grant corresponds. This information is stored in the SR/TM DBA authorization buffer of the OLT.
In specific operation, steps S1 and S2 need to comply with the principle that the same TCONT/LLID cannot simultaneously carry low-latency and non-low-latency traffic.
S3: and performing authorization issuing arbitration according to the information obtained in the step S1 and the step S2.
The basic principle is that the Co-DBA authorization information obtained in step S1 includes the authorization issue time, so that the time interval between the Co-DBA authorization information and the last issued time can be calculated by comparing the authorization issue time with the last issued time; the insertion of the SR/TM DBA grant obtained in step S2 or the insertion of the Co-DBA out-of-order grant obtained in step S1 is performed according to the size of the interval.
In actual operation, as shown in fig. 4, step S3 specifically includes the following steps:
s301: and waiting for authorization information, including waiting for Co-DBA authorization information and SR/TM DBA authorization information. Judging whether the Co-DBA authorization cache in the current step S1 is empty, if so, jumping to the step S302, otherwise, carrying out authorization sequence arbitration, namely judging whether the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, if so, jumping to the step S303, otherwise, jumping to the step S304. Wherein the last issued grant end time does not distinguish between the Co-DBA grant and the SR/TM DBA grant. The last issued authorization end time of S303, S304, S305 below does not distinguish between Co-DBA authorization and SR/TM DBA authorization.
Where a guard time (guard time) is defined for protecting the priority of non-delayed traffic in case of bandwidth conflicts. If there is no Co-DBA authorization within the guard time length, the current Co-DBA authorization is determined to be null, and the next step is executed.
S302: and judging whether the SR/TM DBA authorization buffer in the step S2 is empty, if so, unconditionally jumping to an initial state S301, otherwise, entering an authorization queue to be issued for issuing at a fixed time. According to the PON related protocol, the OLT downlink authorization information needs to be issued in a fixed period, and the issuing time is fixed based on the period, so that the OLT downlink authorization information needs to enter an authorization queue to be issued to wait for issuing at a fixed time after the arbitration result of the authorization information is obtained.
Wherein, when adding the authorization into the authorization queue to be issued, the end time information of the authorization is fed back as the end time of the last authorization, and the step S301 is returned for performing the arbitration of the authorization sequence of the next time.
S303: and judging the size of the authorization interval. And calculating the difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise, entering an authorization queue to be issued and waiting for issuing at a fixed time. The minimum issuing authorization size refers to the minimum time length for which the OLT can issue the authorization.
Wherein, when adding the authorization into the authorization queue to be issued, the end time information of the authorization is fed back as the end time of the last authorization, and the step S301 is returned for performing the arbitration of the authorization sequence of the next time. And simultaneously feeding back the authorization sending state to the CU as a normal state.
S304: calculating the current authorization starting time + the authorization size-the last authorized ending time to obtain a result M, if M is larger than the minimum issued authorization size, cutting the authorization, correcting the authorization starting time to the last authorized ending time, wherein the authorization size is M, entering an authorization queue to be issued after the authorization is cut, and waiting for issuing at a fixed time. And after the information is transmitted, feeding back the authorization related information to the CU/DU, wherein the authorization related information comprises current authorization TCONT/LLID information, a sending state and an authorization size. If M is not greater than the minimum issued grant size, then the grant is discarded. Therefore, each authorization can be ensured to be continuous in time, and the bandwidth is ensured not to be wasted to the maximum extent.
Wherein, when adding the authorization into the authorization queue to be issued, the end time information of the authorization is fed back as the end time of the last authorization, and the step S301 is returned for performing the arbitration of the authorization sequence of the next time. And simultaneously feeding back the authorized sending state as a clipping state and a clipping size to the CU/DU.
And feeding back the CU/DU to the authorization sending state as a discarding state while the authorization is discarded.
S305: and judging whether the authorization size of the SR/TM DBA is larger than the difference G 'between the authorization starting time of the SR/TM DBA and the last authorized ending time, if so, cutting the authorization size of the SR/TM DBA into G', entering an authorization queue to be issued, and waiting for issuing at a fixed time. And the remaining grants are retained SR/TM DBA, waiting for the next grant sequence arbitration. If not, the SR/TM DBA authorization directly enters an authorization queue to be issued, and the SR/TM DBA authorization waits for being issued at a fixed time.
Wherein, when adding the authorization into the authorization queue to be issued, the end time information of the authorization is fed back as the end time of the last authorization, and the step S301 is returned for performing the arbitration of the authorization sequence of the next time.
In the above process, since the SR/TM DBA is a non-low-latency service, and can be directly issued without a low-latency service carried by the Co-DBA, the authorization information of the SR/TM DBA does not have an "authorization start time". However, if there is a low-latency service, it needs to be preferentially guaranteed that the low-latency service with the authorization start time mark is issued first, and then SR/TM DBA authorization is issued in an idle time slot. Therefore, in S302, the pending grant queue is added, and the pending grant queue is waited for a fixed time to be issued again.
The embodiment of the invention also provides a Co-DBA system compatible with different time delay requirements, which comprises the following units:
a CU/DU to: obtaining Co-DBA scheduling information from the OLT through an interactive interface, and feeding back Co-DBA authorization information to be issued to the OLT according to the Co-DBA scheduling information;
the OLT comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorization issuing module, wherein:
a Co-DBA generation module to: obtaining Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, and storing the Co-DBA authorization information in a Co-DBA authorization cache;
an SR/TM DBA generation module to: according to a flow report provided by the ONU or flow monitoring is carried out on the ONU upstream service flow, SR/TM DBA authorization information to be issued is calculated and stored in SR/TM DBA authorization cache;
an authorization issuing module for: according to the comparison between the authorization starting time in the Co-DBA scheduling information and the last authorized ending time, calculating the authorization time interval with the last authorized; and issuing the SR/TM DBA authorization or the Co-DBA authorization to be issued according to the size of the authorization time interval.
Preferably, the Co-DBA scheduling information includes a calculation period of the DBA, an authorization delivery period, and registration information of the ONU, and a service type of each TCONT/LLID.
Preferably, the Co-DBA authorization information includes: TCONT/LLID corresponding to the authorization, authorization starting time and authorization size; the SR/TM DBA authorization information comprises: the TCONT/LLID and grant size for which the grant corresponds.
As a preferred embodiment, the authorization issuing module is specifically configured to:
s301: judging whether the Co-DBA authorization cache is empty or not, if so, jumping to the step S302, if not, performing authorization sequence arbitration, if the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, jumping to the step S303, otherwise, jumping to the step S304;
s302: judging whether the SR/TM DBA authorized cache is empty, and jumping to an initial state S301 if the SR/TM DBA authorized cache is empty; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s303: calculating a difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise adding the Co-DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s304: calculating the authorization starting time + authorization size-last authorized ending time of Co-DBA to be issued to obtain a result M, if M is larger than the minimum issuing authorization size, cutting the Co-DBA authorization, correcting the authorization starting time to last authorized ending time, wherein the authorization size is M, adding the Co-DBA authorization cut into an authorization queue to be issued, and waiting for issuing at a fixed time; if M is not larger than the minimum issuing authorization size, discarding the authorization;
s305: judging whether the authorization size of the SR/TM DBA to be issued is larger than G ', if so, cutting the authorization size of the SR/TM DBA into G', entering an authorization queue to be issued, waiting for issuing at a fixed time, keeping the rest of authorization in an SR/TM DBA authorization cache, and waiting for next authorization sequence arbitration; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
in the above process, when adding the grant into the grant queue to be issued, the end time information of the grant is stored as the end time of the last grant, and the process returns to step S301 for performing the next grant sequence arbitration.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method for compatible Co-DBA with different time delay requirements is characterized by comprising steps S1 and S2 which are not in sequence, and further comprising the step S3:
s1, the OLT provides Co-DBA scheduling information to the CU/DU through the interactive interface, obtains Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, stores the Co-DBA authorization information in a Co-DBA authorization cache, and enters step S3;
s2, an SR/TM DBA generation module of the OLT carries out flow monitoring on ONU uplink service flow according to a flow report provided by the ONU, calculates SR/TM DBA authorization information to be issued, stores the SR/TM DBA authorization information in an SR/TM DBA authorization cache, and enters step S3;
s3, the OLT calculates the authorization time interval with the last authorized according to the comparison between the authorization starting time in the Co-DBA authorization information to be issued and the finish time of the last authorized; issuing SR/TM DBA authorization or Co-DBA authorization to be issued according to the size of the authorization time interval;
step S3 specifically includes the following steps:
s301: judging whether the Co-DBA authorization cache is empty or not, if so, jumping to the step S302, if not, performing authorization sequence arbitration, if the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, jumping to the step S303, otherwise, jumping to the step S304;
s302: judging whether the SR/TM DBA authorized cache is empty, and jumping to an initial state S301 if the SR/TM DBA authorized cache is empty; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s303: calculating a difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise adding the Co-DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s304: calculating the authorization starting time + authorization size-last authorized ending time of Co-DBA to be issued to obtain a result M, if M is larger than the minimum issuing authorization size, cutting the Co-DBA authorization, correcting the authorization starting time to last authorized ending time, wherein the authorization size is M, adding the Co-DBA authorization cut into an authorization queue to be issued, and waiting for issuing at a fixed time; if M is not larger than the minimum issuing authorization size, discarding the authorization;
s305: judging whether the size of the SR/TM DBA authorization to be issued is larger than the difference G ' between the SR/TM DBA authorization start time to be issued and the last authorization finish time, if so, cutting the SR/TM DBA authorization size into G ', adding the G ' into an authorization queue to be issued, issuing at a fixed moment, keeping the rest of the authorization in an SR/TM DBA authorization cache, and waiting for the next authorization sequence arbitration; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
in the above process, when adding the grant into the grant queue to be issued, the end time information of the grant is stored as the end time of the last grant, and is used for performing the next grant sequence arbitration.
2. The method of claim 1, wherein the Co-DBA scheduling information includes a calculation period of the DBA, an authorization delivery period, and registration information of the ONU and a traffic type of each TCONT/LLID.
3. The method of claim 1, wherein the Co-DBA authorization information further comprises: TCONT/LLID and authorization size corresponding to the authorization; the SR/TM DBA authorization information comprises: the TCONT/LLID and grant size for which the grant corresponds.
4. The method of claim 1, further comprising the steps of: in S304, the Co-DBA authorization is cut and added into an authorization queue to be issued, after a fixed time is issued, the authorization related information is fed back to the CU/DU, the authorization related information comprises the current authorization TCONT/LLID information, the sending state and the authorization size.
5. The method of claim 1, wherein determining whether the Co-DBA grant buffer is empty sets a guard time, and determines that the Co-DBA grant buffer is empty if no Co-DBA grant buffer is available within the guard time.
6. A system compatible with Co-DBAs with different delay requirements is characterized by comprising a CU/DU and an OLT:
a CU/DU to: obtaining Co-DBA scheduling information from the OLT through an interactive interface, and feeding back Co-DBA authorization information to be issued to the OLT according to the Co-DBA scheduling information;
the OLT comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorization issuing module, wherein:
a Co-DBA generation module to: providing Co-DBA scheduling information to a CU/DU through an interactive interface, obtaining Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, and storing the Co-DBA authorization information in a Co-DBA authorization cache;
an SR/TM DBA generation module to: according to a flow report provided by the ONU or flow monitoring is carried out on the ONU upstream service flow, SR/TM DBA authorization information to be issued is calculated and stored in SR/TM DBA authorization cache;
an authorization issuing module for: according to the comparison between the authorization starting time in the Co-DBA authorization information and the last authorized ending time, calculating the authorization time interval with the last authorized; issuing SR/TM DBA authorization or Co-DBA authorization to be issued according to the size of the authorization time interval;
the authorization issuing module is specifically configured to:
s301: judging whether the Co-DBA authorization cache is empty or not, if so, jumping to the step S302, if not, performing authorization sequence arbitration, if the last authorized ending time is earlier than the Co-DBA authorization starting time to be issued, jumping to the step S303, otherwise, jumping to the step S304;
s302: judging whether the SR/TM DBA authorized cache is empty, and jumping to an initial state S301 if the SR/TM DBA authorized cache is empty; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s303: calculating a difference G between the authorization starting time of the Co-DBA to be issued and the last authorized ending time, if G is larger than the minimum issuing authorization size and the SR/TM DBA authorization cache is not empty, jumping to the step S305, otherwise adding the Co-DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
s304: calculating the authorization starting time + authorization size-last authorized ending time of Co-DBA to be issued to obtain a result M, if M is larger than the minimum issuing authorization size, cutting the Co-DBA authorization, correcting the authorization starting time to last authorized ending time, wherein the authorization size is M, adding the Co-DBA authorization cut into an authorization queue to be issued, and waiting for issuing at a fixed time; if M is not larger than the minimum issuing authorization size, discarding the authorization;
s305: judging whether the size of the SR/TM DBA authorization to be issued is larger than the difference G 'between the SR/TM DBA authorization start time to be issued and the last authorized end time, if so, cutting the SR/TM DBA authorization size into G', entering an authorization queue to be issued, issuing at a fixed time, keeping the rest of authorization in an SR/TM DBA authorization cache, and waiting for the next authorization sequence arbitration; if not, adding the SR/TM DBA authorization into an authorization queue to be issued, and waiting for issuing at a fixed time;
in the above process, when adding the grant into the grant queue to be issued, the end time information of the grant is stored as the end time of the last grant, and is used for performing the next grant sequence arbitration.
7. The system of claim 6, wherein the Co-DBA scheduling information includes a calculation period of the DBA, an authorization issuance period, and registration information of the ONU and a traffic type of each TCONT/LLID.
8. The system of claim 6, wherein the Co-DBA authorization information further comprises: TCONT/LLID and authorization size corresponding to the authorization; the SR/TM DBA authorization information comprises: the TCONT/LLID and grant size for which the grant corresponds.
9. The system of claim 6, wherein the authorization issuance module is further configured to: and adding the Co-DBA authorization after cutting into an authorization queue to be issued, and feeding back authorization related information to the CU/DU after waiting for issuing at a fixed time, wherein the authorization related information comprises current authorization TCONT/LLID information, a sending state and an authorization size.
10. The system of claim 6, wherein the authorization issuing module determines whether the Co-DBA authorization buffer is empty, sets a protection time, and determines that the Co-DBA authorization buffer is empty if no Co-DBA authorization exists in the protection time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010136735.2A CN111464886B (en) | 2020-03-02 | 2020-03-02 | Co-DBA method and system compatible with different time delay requirements |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010136735.2A CN111464886B (en) | 2020-03-02 | 2020-03-02 | Co-DBA method and system compatible with different time delay requirements |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111464886A CN111464886A (en) | 2020-07-28 |
| CN111464886B true CN111464886B (en) | 2022-02-01 |
Family
ID=71682453
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010136735.2A Active CN111464886B (en) | 2020-03-02 | 2020-03-02 | Co-DBA method and system compatible with different time delay requirements |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111464886B (en) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ATE422788T1 (en) * | 1998-12-28 | 2009-02-15 | Italtel Spa | METHOD AND DEVICE FOR BANDWIDTH ALLOCATION IN BOTH A RADIO AND A PON-ATM P-MP SYSTEM |
| CN101068145B (en) * | 2007-07-05 | 2010-06-02 | 杭州华三通信技术有限公司 | EPON network element configuration method and EPON |
| ATE545993T1 (en) * | 2008-05-05 | 2012-03-15 | Nokia Siemens Networks Oy | TWO- AND THREE-STROKE DISCOVERY PROCEDURE FOR 10G EPON |
| CN102395060A (en) * | 2011-11-03 | 2012-03-28 | 北京邮电大学 | Novel bandwidth allocation algorithm based on OFDM-PON |
| CN110213679B (en) * | 2016-12-02 | 2021-09-10 | 中兴通讯股份有限公司 | Passive optical network system and implementation method thereof |
| CN106921430A (en) * | 2017-02-24 | 2017-07-04 | 烽火通信科技股份有限公司 | The realization method and system of TYPE C optical link protection systems in EPON |
| US10827240B2 (en) * | 2018-07-06 | 2020-11-03 | Electronics And Telecommunications Research Institute | Cooperatiave dynamic bandwidth allocation method in mobile network with optical network, and device of performing the cooperatiave dynamic bandwidth allocation method |
| CN110224755B (en) * | 2019-05-23 | 2021-08-17 | 电子科技大学 | Low-delay device and method for 5G forward transmission |
-
2020
- 2020-03-02 CN CN202010136735.2A patent/CN111464886B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN111464886A (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100450771B1 (en) | Method for controlling upstream data of Ethernet PON and apparatus thereof | |
| US6546014B1 (en) | Method and system for dynamic bandwidth allocation in an optical access network | |
| JP3795254B2 (en) | Uplink transmission rate control method and communication system in ATM-PON | |
| Han et al. | Development of efficient dynamic bandwidth allocation algorithm for XGPON | |
| EP2975810B1 (en) | Method and system for improving bandwidth allocation efficiency | |
| JP5094664B2 (en) | Passive optical network system and operation method thereof | |
| US20040252714A1 (en) | Dynamic bandwidth allocation method considering multiple services in ethernet passive optical network system | |
| JP5404936B2 (en) | Communication device | |
| EP2815528B1 (en) | Method and apparatus for dynamically allocating bandwidth to a client in a passive optical network | |
| US7936765B2 (en) | Method and apparatus for dynamically allocating bandwidth by hierarchical weight round robin | |
| JP2010233136A (en) | Passive optical network system and method of operating the same | |
| KR20100058169A (en) | Method and apparatus for scheduling bandwidth in cable network | |
| JP2008270898A (en) | Optical subscriber line terminal | |
| US20040085905A1 (en) | OAM packet data transmission method and ethernet passive optical network including control multiplexer for the same | |
| US7403518B2 (en) | Packet transmission system, packet transmission method, packet transmission program, and recording medium on which the recorded program is recorded | |
| JP3725724B2 (en) | ATM cell multiplexing apparatus and ATM cell multiplexing method | |
| EP4087271A1 (en) | Service transmission method and apparatus, sending end and storage medium | |
| CN111464886B (en) | Co-DBA method and system compatible with different time delay requirements | |
| US7653080B2 (en) | Station side communication device | |
| CN100452681C (en) | Control method and system used for dispatching multiclass business in passive optical network | |
| CN116634313A (en) | Single-frame multi-burst allocation method and burst frame uplink method in optical forwarding network | |
| JP2010193130A (en) | Dynamic band allocation method and station side apparatus | |
| JP5365874B2 (en) | PON optical communication system, station side apparatus, and power consumption control method | |
| KR100758784B1 (en) | MAC scheduling apparatus and method of OLT in PON | |
| JP2007019647A (en) | Transmission system and its terminal device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |