CN111464886A - 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 PDF

Info

Publication number
CN111464886A
CN111464886A CN202010136735.2A CN202010136735A CN111464886A CN 111464886 A CN111464886 A CN 111464886A CN 202010136735 A CN202010136735 A CN 202010136735A CN 111464886 A CN111464886 A CN 111464886A
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.)
Granted
Application number
CN202010136735.2A
Other languages
Chinese (zh)
Other versions
CN111464886B (en
Inventor
左越
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Information And Communication Technology Group Co ltd
Fiberhome Telecommunication Technologies Co Ltd
Wuhan Fisilink Microelectronics Technology Co Ltd
Original Assignee
China Information And Communication Technology Group Co ltd
Fiberhome Telecommunication Technologies Co Ltd
Wuhan Fisilink Microelectronics Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Information And Communication Technology Group Co ltd, Fiberhome Telecommunication Technologies Co Ltd, Wuhan Fisilink Microelectronics Technology Co Ltd filed Critical China Information And Communication Technology Group Co ltd
Priority to CN202010136735.2A priority Critical patent/CN111464886B/en
Publication of CN111464886A publication Critical patent/CN111464886A/en
Application granted granted Critical
Publication of CN111464886B publication Critical patent/CN111464886B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q11/0067Provisions for optical access or distribution networks, e.g. Gigabit Ethernet Passive Optical Network (GE-PON), ATM-based Passive Optical Network (A-PON), PON-Ring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0079Operation or maintenance aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0086Network 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 delay requirements, relating to the technical field of PON, wherein an interactive interface is provided through O L T to transmit Co-DBA scheduling information, Co-DBA authorization information to be issued and fed back by CU/DU is obtained, meanwhile, the calculation function of SR/TM DBA authorization information through flow report analysis and flow monitoring between ONU is reserved, and a DBA mode compatible with two different delay requirements is provided.

Description

Co-DBA method and system compatible with different time delay requirements
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 (StateReport)/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-latency requirement of real-time services, ITU-T defines a Co-DBA (coordination DBA) manner to implement the upstream bandwidth allocation of PON system, as shown in fig. 1, this manner is to inform O L T, through CUs (centralized units)/DUs (distributed units), that one or more RUs (remote units) controlled by the CU (centralized units) expect bandwidth information in a specific time in the future, and O L T adjusts the upstream bandwidth to provide enough bandwidth to meet the required traffic of the RUs, so as to minimize transmission delay.
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 and O L T provide Co-DBA scheduling information to the CU/DU through the interactive interface, obtain Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, store the Co-DBA authorization information in a Co-DBA authorization cache, and enter the step S3;
s2, an SR/TM DBA generation module of O L T calculates SR/TM DBA authorization information to be issued according to a flow report provided by the ONU or flow monitoring of the ONU uplink service flow, stores the SR/TM DBA authorization information in an SR/TM DBA authorization cache, and enters step S3;
s3, O L T compares the authorization start time in the Co-DBA authorization information to be issued with the last authorized end time to calculate the authorization time interval with the last authorized time, and issues 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/LL ID.
On the basis of the technical scheme, the Co-DBA authorization information further comprises a TCONT/LL ID and an authorization size corresponding to the authorization, and the SR/TM DBA authorization information comprises a TCONT/LL ID and an authorization size corresponding to the authorization.
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 above technical solution, the method further comprises the steps of adding the Co-DBA authorization cut in the S304 into an authorization queue to be issued, and feeding back the authorization related information to the CU/DU after waiting for the issue at a fixed time, wherein the authorization related information comprises the current authorization TCONT/LL ID 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 CU/DU and O L T:
the CU/DU is used for obtaining Co-DBA scheduling information from O L T through an interactive interface and feeding back Co-DBA authorization information to be issued to O L T according to the Co-DBA scheduling information;
the O L T comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorized 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/LL ID.
On the basis of the technical scheme, the Co-DBA authorization information further comprises a TCONT/LL ID and an authorization size corresponding to the authorization, and the SR/TM DBA authorization information comprises a TCONT/LL ID and an authorization size corresponding to the authorization.
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 technical scheme, the authorization issuing module is also used for adding the Co-DBA authorization after cutting into an authorization queue to be issued, feeding back the authorization related information to the CU/DU after waiting for issuing at a fixed time, wherein the authorization related information comprises current authorization TCONT/LL ID information, sending state and 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 O L T to transmit Co-DBA scheduling information, obtains Co-DBA authorization information fed back by CU/DU, simultaneously reserves the calculation function of SR/TM DBA authorization information through flow report analysis and flow monitoring between ONU, and provides two DBA modes compatible with different delay requirements.
(2) According to the invention, the O L T carries out authorization sequence arbitration by combining DBA authorization information according to the principle of low-delay service priority, monitors two DBA authorizations in real time, dynamically adjusts out-of-order authorization, and ensures the bandwidth utilization rate while preferentially ensuring the 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: O L T provides an interactive interface for interacting with CU/DU Co-DBA scheduling information for generating authorization information of low-latency services.
As shown in FIG. 3, the scheduling information provided by the O L T for interacting with the CU/DU includes a calculation period of a DBA, an authorized issuing period, registration information of the ONU and a service type of each TCONT (Transmission CONT)/LL ID (L logical L ink Identifier), and at the same time, real-time residual bandwidth allocation information is provided periodically, and the current state of the bandwidth issued by the O L T of the CU/DU is notified in real time, so that the CU/DU can adjust and optimize bandwidth calculation.
The Co-DBA authorization information provided by the CU/DU in real time comprises TCONT/LL ID corresponding to the authorization, authorization starting time and authorization size, wherein the authorization starting time refers to the time when the ONU starts to transmit corresponding TCONT/LL ID data at the moment, and the authorization size refers to the time length when the ONU continuously transmits data, the information is obtained from the CU/DU through the interactive interface by the O L T and is stored in a Co-DBA authorization cache of the O L T.
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 O L T.
S2O L T retains authorization information that a conventional SR/TM DBA generation module uses 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.
The SR/TM DBA authorization information includes TCONT/LL ID corresponding to the authorization and authorization size, and these information are stored in SR/TM DBA authorization buffer of O L T.
In specific operation, steps S1 and S2 need to comply with the principle that the same TCONT/LL ID 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, judging whether the SR/TM DBA authorization buffer in the step S2 is empty, if so, jumping to an initial state S301 unconditionally, otherwise, the authorization enters an authorization queue to be issued and waits for being issued at a fixed time, according to a PON related protocol, O L T downlink authorization information needs to be issued in a fixed period, and the issuing time is fixed based on the period, so that the authorization queue to be issued needs to wait for being issued at the fixed time after the arbitration result of the authorization information comes out.
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 S303, judging the authorization interval, 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 buffer is not empty, jumping to the step S305, otherwise, entering the authorization queue to be issued and waiting for issuing at a fixed time, wherein the minimum issuing authorization size refers to the minimum time length for which O L T can issue 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 cutting the authorization, waiting for a fixed time to issue, feeding back the authorization related information to a CU/DU after issuing, wherein the authorization related information comprises the current authorization TCONT/LL ID information, sending state and authorization size, and if M is not larger than the minimum issued authorization size, discarding 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 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 a CU/DU and O L T:
the CU/DU is used for obtaining Co-DBA scheduling information from O L T through an interactive interface and feeding back Co-DBA authorization information to be issued to O L T according to the Co-DBA scheduling information;
the O L T comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorized 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/LL ID.
Preferably, the Co-DBA authorization information includes a TCONT/LL ID corresponding to the authorization, an authorization start time and an authorization size, and the SR/TM DBA authorization information includes a TCONT/LL ID corresponding to the authorization and an authorization size.
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, issuing at a fixed moment, keeping the rest of authorization in an SR/TMDBA 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 (12)

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 and O L T provide Co-DBA scheduling information to the CU/DU through the interactive interface, obtain Co-DBA authorization information to be issued fed back by the CU/DU through the interactive interface, store the Co-DBA authorization information in a Co-DBA authorization cache, and enter the step S3;
s2, an SR/TM DBA generation module of O L T calculates SR/TM DBA authorization information to be issued according to a flow report provided by the ONU or flow monitoring of the ONU uplink service flow, stores the SR/TM DBA authorization information in an SR/TM DBA authorization cache, and enters step S3;
s3, O L T compares the authorization start time in the Co-DBA authorization information to be issued with the last authorized end time to calculate the authorization time interval with the last authorized time interval, and issues the SR/TMDBA authorization or the Co-DBA authorization to be issued according to the size of the authorization time interval.
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/LL ID.
3. The method as claimed in claim 1, wherein the Co-DBA authorization information further includes a TCONT/LL ID and an authorization size corresponding to the authorization, and the SR/TM DBA authorization information includes a TCONT/LL ID and an authorization size corresponding to the authorization.
4. The method according to claim 1, wherein step S3 specifically comprises the steps of:
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.
5. The method as claimed in claim 4, wherein the method further comprises the steps of clipping the Co-DBA grant and adding the clipped Co-DBA grant to a pending grant queue in S304, and feeding back the grant related information to the CU/DU after waiting for a fixed time to be issued, wherein the grant related information includes the current grant TCONT/LL ID information, the sending status and the grant size.
6. The method of claim 4, wherein the Co-DBA authorization buffer is determined to be empty by setting a guard time if the Co-DBA authorization buffer is determined to be empty if no Co-DBA authorization is available within the guard time.
7. A system compatible with Co-DBAs with different delay requirements is characterized by comprising CU/DU and O L T:
the CU/DU is used for obtaining Co-DBA scheduling information from O L T through an interactive interface and feeding back Co-DBA authorization information to be issued to O L T according to the Co-DBA scheduling information;
the O L T comprises a Co-DBA generating module, an SR/TM DBA generating module and an authorized 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.
8. The system of claim 7, 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/LL ID.
9. The system of claim 7, wherein the Co-DBA authorization information further comprises a TCONT/LL ID and an authorization size corresponding to the authorization, and the SR/TM DBA authorization information comprises a TCONT/LL ID and an authorization size corresponding to the authorization.
10. The system of claim 7, wherein 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.
11. The system as claimed in claim 10, wherein the grant issuing module is further configured to add the Co-DBA grant after clipping into a pending issue grant queue, and feed back the grant related information to the CU/DU after waiting for issuing at a fixed time, the grant related information including current grant TCONT/LL ID information, sending status and grant size.
12. The system of claim 10, 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 is available within the protection time.
CN202010136735.2A 2020-03-02 2020-03-02 Co-DBA method and system compatible with different time delay requirements Active CN111464886B (en)

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 true CN111464886A (en) 2020-07-28
CN111464886B 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)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068145A (en) * 2007-07-05 2007-11-07 杭州华三通信技术有限公司 EPON network element configuration method and EPON
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
CN102017522A (en) * 2008-05-05 2011-04-13 诺基亚西门子通信公司 Two and three-stroke discovery process for 10G-EPONs
CN102395060A (en) * 2011-11-03 2012-03-28 北京邮电大学 Novel bandwidth allocation algorithm based on OFDM-PON
CN106921430A (en) * 2017-02-24 2017-07-04 烽火通信科技股份有限公司 The realization method and system of TYPE C optical link protection systems in EPON
CN110213679A (en) * 2016-12-02 2019-09-06 中兴通讯股份有限公司 A kind of passive optical network and its implementation
CN110224755A (en) * 2019-05-23 2019-09-10 电子科技大学 A kind of low time delay device and method of 5G forward pass
US20200014992A1 (en) * 2018-07-06 2020-01-09 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

Patent Citations (10)

* Cited by examiner, † Cited by third party
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
DE69840546D1 (en) * 1998-12-28 2009-03-26 Italtel Spa Method and apparatus for bandwidth allocation in both a radio and a PON-ATM P-MP system
CN101068145A (en) * 2007-07-05 2007-11-07 杭州华三通信技术有限公司 EPON network element configuration method and EPON
CN102017522A (en) * 2008-05-05 2011-04-13 诺基亚西门子通信公司 Two and three-stroke discovery process for 10G-EPONs
CN102395060A (en) * 2011-11-03 2012-03-28 北京邮电大学 Novel bandwidth allocation algorithm based on OFDM-PON
CN110213679A (en) * 2016-12-02 2019-09-06 中兴通讯股份有限公司 A kind of passive optical network and its implementation
US20190327541A1 (en) * 2016-12-02 2019-10-24 Zte Corporation 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
US20200014992A1 (en) * 2018-07-06 2020-01-09 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
CN110224755A (en) * 2019-05-23 2019-09-10 电子科技大学 A kind of low time delay device and method of 5G forward pass

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HIROKO NOMURA;HIROTAKA UJIKAWA;HIROYUKI UZAWA;HIROTAKA NAKAMURA;: "Novel DBA scheme integrated with SR- and CO-DBA for multi-service accommodation toward 5G beyond", 《45TH EUROPEAN CONFERENCE ON OPTICAL COMMUNICATION (ECOC 2019)》 *
张宏熙: "5G时代大容量光接入网的安全技术", 《中兴通讯技术》 *

Also Published As

Publication number Publication date
CN111464886B (en) 2022-02-01

Similar Documents

Publication Publication Date Title
KR100450771B1 (en) Method for controlling upstream data of Ethernet PON and apparatus thereof
US5615212A (en) Method, device and router for providing a contention-based reservation mechanism within a mini-slotted dynamic entry polling slot supporting multiple service classes
Han et al. Development of efficient dynamic bandwidth allocation algorithm for XGPON
EP2975810B1 (en) Method and system for improving bandwidth allocation efficiency
JP3795254B2 (en) Uplink transmission rate control method and communication system in ATM-PON
US20040252714A1 (en) Dynamic bandwidth allocation method considering multiple services in ethernet passive optical network system
KR101113338B1 (en) Method and apparatus for scheduling bandwidth in cable network
EP2378721B1 (en) Bandwidth allocation method and routing apparatus
US8326149B2 (en) Dynamic bandwidth allocation in a passive optical network in which different optical network units transmit at different rates
US20120087664A1 (en) Efficient mac protocol for ofdma passive optical networks (pons)
KR101403911B1 (en) A dynamic bandwidth allocation device for a passive optical network system and the method implemented
WO2012070127A1 (en) Communication apparatus
US7936765B2 (en) Method and apparatus for dynamically allocating bandwidth by hierarchical weight round robin
EP1416761B1 (en) OAM packet transmission control method and multiplexer for an Ethernet Passive Optical Network
JP2008270898A (en) Optical subscriber line terminal
EP4087271A1 (en) Service transmission method and apparatus, sending end and storage medium
JP2007243770A (en) Dynamic band allocation method, and station side apparatus and subscriber side apparatus
CN111464886B (en) Co-DBA method and system compatible with different time delay requirements
US20120254483A1 (en) Data transmission method, device and system
JP2000269970A (en) Atm cell multiplexer and method for multiplexing atm cell
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
JP2010114822A (en) Dynamic band allocation method and station-side apparatus
KR100758784B1 (en) MAC scheduling apparatus and method of OLT in PON

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