Bandwidth allocation method

Abstract

Provided in the embodiments of the present disclosure is a bandwidth allocation method. The method comprises: acquiring traffic information of a transmission container of an optical network unit (ONU), wherein the traffic information is used for indicating whether the traffic in the transmission container is low-latency traffic and the bandwidth size of the low-latency traffic; and allocating a bandwidth to the transmission container on the basis of the traffic information.

Description

Bandwidth allocation method

[0001] Cross-reference to related applications

[0002] The present disclosure is based on and claims priority to Chinese patent application 2024112299164 filed on September 03, 2024, the disclosure of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates to the field of communications, and in particular, to a bandwidth allocation method. BACKGROUND

[0004] In the current optical access network meeting ITU-T standards, such as GPON, XG(S)PON, 50GPON technology, the upstream service bandwidth of users is dynamically allocated by the optical line terminal (OLT) uniformly. Except for basic services such as voice, which have fixed bandwidth for guarantee, the current standards do not distinguish whether specific services have low latency requirements, and various services use the traditional dynamic bandwidth allocation (DBA) method for upstream bandwidth allocation.

[0005] In the passive optical network (PON) technology, there are three kinds of dynamic bandwidth adjustment methods. One is the method of obtaining explicit buffer occupancy reports for DBA, that is, the status reporting dynamic bandwidth allocation (SR-DBA); one is the method of comparing the XGEM frame mode monitored by the OLT with the corresponding bandwidth mapping, that is, the traffic monitoring dynamic bandwidth allocation (TM-DBA); and one is the method based on the uplink scheduling information of the application layer of the external device on the OLT side, that is, the coordinated dynamic bandwidth allocation (CoDBA). No matter which bandwidth adjustment method, the low latency service scenario and the non-low latency service scenario are difficult to effectively distinguish, which may not be able to guarantee the bandwidth demand of the low latency service scenario, causing the delay to be too large, the quality of service (QoS) not to meet the service requirements, etc., and the transmission of low latency services cannot be efficiently performed.

[0006] In summary, there is no good solution to the above problems. SUMMARY

[0007] The bandwidth allocation method provided by the embodiments of the present disclosure can effectively distinguish low-latency service scenarios.

[0008] According to an embodiment of the present disclosure, a bandwidth allocation method is provided, which is applied to an optical line terminal (OLT), and the method comprises: obtaining traffic information of a transmission container of an optical network unit (ONU), wherein the traffic information is used to indicate whether traffic in the transmission container is low-latency traffic and a bandwidth size of the low-latency traffic.

[0009] According to another embodiment of the present disclosure, a bandwidth allocation method is also provided, which is applied to an optical network unit (ONU), and the method comprises: obtaining traffic information of a transmission container of the ONU, wherein the traffic information is used to indicate whether traffic in the transmission container is low-latency traffic and a bandwidth size of the low-latency traffic; and sending the traffic information to an optical line terminal (OLT) to enable the OLT to allocate bandwidth to the transmission container according to the traffic information.

[0010] According to still another embodiment of the present disclosure, an optical line terminal is provided, which comprises a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps of the method embodiments of the optical line terminal side in the present disclosure.

[0011] According to still another embodiment of the present disclosure, an optical network unit is provided, which comprises a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps of the method embodiments of the optical network unit side in the present disclosure.

[0012] According to still another embodiment of the present disclosure, a computer-readable storage medium is also provided, which stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are performed.

[0013] According to still another embodiment of the present disclosure, a computer program product is also provided, which comprises a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented. BRIEF DESCRIPTION OF DRAWINGS

[0014] FIG. 1 is a schematic diagram of a network architecture of a passive optical network according to an embodiment of the present disclosure;

[0015] FIG. 2 is a flowchart of dynamic bandwidth allocation of an optical line terminal according to an embodiment of the present disclosure;

[0016] Figure 3 is a flow chart of dynamic bandwidth allocation of an optical network unit according to an embodiment of the present disclosure;

[0017] Figure 4 is a schematic diagram of a flow of dynamic bandwidth allocation of low latency traffic according to an embodiment of the present disclosure (I);

[0018] Figure 5 is a schematic diagram of a flow of dynamic bandwidth allocation of low latency traffic according to an embodiment of the present disclosure (II);

[0019] Figure 6 is a schematic diagram of a flow of dynamic bandwidth allocation of low latency traffic according to an embodiment of the present disclosure (III);

[0020] Figure 7 is a flow chart of a transmission configuration method of an optical line terminal according to an embodiment of the present disclosure;

[0021] Figure 8 is a flow chart of a transmission configuration method of an optical network unit according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence.

[0024] Embodiments of the present disclosure can be run in a passive optical network. Figure 1 is a schematic diagram of a network architecture of a passive optical network according to an embodiment of the present disclosure, as shown in Figure 1, the passive optical network can include:

[0025] one optical line terminal 12 and a plurality of optical network units 14.

[0026] In the field of optical access, PON is a single-point-to-multipoint topology, and one OLT can connect multiple ONUs. The OLT is the central node of the PON network and can uniformly manage multiple ONUs and realize communication with multiple ONUs.

[0027] In the G.9804.2 ComTC standard, the OLT and the ONU communicate by Time-Division Multiplexing (TDM) mode, which is called Time-Division Multiplexing Passive Optical Network (TDM-PON) technology. In the TDM-PON technology, the minimum service unit is XGEM frame, which has a fixed length. All service data units SDU are encapsulated in the XGEM frame, and an XGEM port ID globally allocated by the OLT is added in the XGEM frame header to uniquely identify it. The XGEM port ID occupies 16 bits in the XGEM frame header, and can represent at most 65536 logical connection relationships between the OLT and the ONU user services. The XGEM frame header can also indicate whether the XGEM frame is unicast or broadcast through the Key index. If it is unicast, the XGEM Port ID can only be used by a certain specific ONU, and if it is broadcast, it can be used by all ONUs.

[0028] In the downstream transmission direction of the TDM-PON, the Service Data Unit (SDU) is generally transmitted based on the Hierarchical QoS queue scheduling. Therefore, the downlink transmission of low latency services can be realized by configuring a higher scheduling priority and appropriate queue centralized scheduling. In the upstream transmission direction of the TDM-PON, all XGEM service units must be carried by the transmission container (T-CONT), which is the basic control unit of the upstream service flow in the TDM-PON system. Therefore, all XGEM Port IDs also need to be mapped into the T-CONT of the corresponding ONU, and each T-CONU is uniquely identified by an OLT globally allocated allocation identifier (Alloc-ID). The Alloc-ID is a 14-bit binary number located in the bandwidth mapping (BWmap) data block in the downlink frame structure header, which can be used to identify the T-CONT of each ONU, and also can be used to identify the specific function competed by multiple qualified ONUs.

[0029] The bandwidth size that can be used by the T-CONT is uniformly scheduled by the OLT in a dynamic bandwidth assignment (DBA) manner. The ONU is responsible for XGEM traffic sensing and management of each T-CONT under the ONU, while the OLT is responsible for monitoring of the respective aggregated traffic of each T-CONT or obtaining of the buffer status report, and providing of QoS-aware management. Each T-CONT can carry multiple XGEM ports or only one XGEM port; each XGEM port can carry multiple services or only one service; each ONU can support only one T-CONT or multiple T-CONTs, and the T-CONTs can be configured to be of different service types.

[0030] The QoS at the access network side is part of an end-to-end QoS scheduling mechanism. In the optical access network under the G.9804.2 ComTC standard specification, the QoS capability is related to the available resource allocation manner of single or aggregated traffic between the OLT and the ONU, and the available resources include channel processing capability, buffer space size, uplink and downlink channel bandwidth, etc. The size of the traffic can be described by a traffic descriptor in the form of multiple bandwidth parameters.

[0031] In the standard G.9804.2, the traffic descriptor is a tool for describing the traffic characteristics in the PON network, and the ONU and the OLT can obtain traffic information through the traffic descriptor. However, the traffic descriptor in G.9804.2 cannot realize identification and marking of low-latency service traffic.

[0032] In the embodiments of the present disclosure, a traffic descriptor is provided, which includes a low-latency bandwidth marker, wherein the low-latency bandwidth marker is used to indicate whether the traffic in the transmission container is low-latency traffic and the bandwidth size of the low-latency traffic.

[0033] In some embodiments, the low-latency bandwidth marker can be a low-latency bandwidth, wherein the low-latency bandwidth is a kind of ONU uplink exclusive bandwidth allocated by the OLT for the low-latency traffic, and is used to indicate the bandwidth size of the low-latency traffic. The low-latency bandwidth cannot be used for non-low-latency service. If the low-latency bandwidth is greater than 0, it indicates that the traffic in the transmission container is low-latency traffic. If the low-latency bandwidth is equal to 0, it indicates that the traffic in the transmission container is non-low-latency traffic.

[0034] In other embodiments, the low-latency bandwidth marker can also be realized by a bandwidth marker in the traffic descriptor, wherein the type of the bandwidth marker includes low-latency and non-low-latency, and the bandwidth marker can be used to indicate whether the traffic in the transmission container is low-latency traffic.

[0035] In this embodiment, the traffic descriptor is a tool used to describe traffic and can indicate the type of traffic information. The ONU or OLT can obtain traffic information of the corresponding type based on the traffic descriptor. For example, based on the improved traffic descriptor described above, the traffic information obtained by the ONU or OLT can include low-latency bandwidth and / or bandwidth markings. If the low-latency bandwidth is greater than 0, it indicates that the traffic is low-latency traffic; if the low-latency bandwidth is equal to 0, it indicates that the traffic is non-low-latency traffic. If the bandwidth marking is low-latency, the traffic is low-latency traffic; if the bandwidth marking is non-low-latency, the traffic is non-low-latency traffic.

[0036] In this embodiment, the transmission container (T-CONT) is the basic unit of bandwidth allocation, and can also be regarded as the basic unit of traffic scheduling. Each ONU can contain multiple T-CONTs, each with independent bandwidth allocation and priority settings. A T-CONT can contain one or more groups of traffic. The traffic carried in a T-CONT can be represented by multiple traffic parameters of the corresponding type based on a traffic descriptor. Therefore, a T-CONT can be regarded as a logical connection entity in the ONU composed of one or more groups of traffic represented by a traffic descriptor. Transmission containers can be divided into low-latency transmission containers and non-low-latency transmission containers. Low-latency transmission containers consist of one or more groups of low-latency traffic, while non-low-latency transmission containers consist of one or more groups of non-low-latency traffic.

[0037] In the embodiments of this disclosure, low latency and non-low latency are used to distinguish the requirements of user services in terms of transmission latency. For example, low latency services may include application scenarios that have strict requirements for network transmission latency, such as instant messaging, high-definition video transmission, and virtual reality (VR), but this disclosure is not limited to this.

[0038] In some embodiments, the bandwidth marker includes low latency and non-low latency; further, the non-low latency in the bandwidth marker includes at least one of the following: None, Non-Assured (NA), and Best-Effort (BE). Correspondingly, the low latency in the bandwidth marker can also be represented as LL (Low latency).

[0039] In some embodiments, a traffic descriptor can be represented as: D = <R F ,R L ,R A ,R M ,χ AB ,P,ω>;

[0040] Where D is the flow descriptor, R FR is a fixed bandwidth, L R is the low latency bandwidth, A R is a guaranteed bandwidth, M χ is a maximum bandwidth, AB P is a priority of allocation of the best effort bandwidth, ω is a weight of allocation of the best effort bandwidth, χ is the bandwidth marker, AB = {None, LL, NA, BE}.

[0041] In some embodiments, the traffic descriptor can be represented as: D = <R F , R L , R A , R M , χ AB , P, ω, T JT , T BDT , T PST >.

[0042] wherein D is the traffic descriptor, R F is a fixed bandwidth, L R is the low latency bandwidth, A R is a guaranteed bandwidth, M χ is a maximum bandwidth, AB P is a priority of allocation of the best effort bandwidth, ω is a weight of allocation of the best effort bandwidth, T JT is a jitter tolerance, BDT T is a bandwidth allocation latency tolerance, PST T is a protection switching latency tolerance, χ is the bandwidth marker, AB = {None, LL, NA, BE}.

[0043] In some embodiments, the traffic descriptor can further comprise: a fixed latency size or a maximum latency tolerance.

[0044] In some embodiments, when the bandwidth marker is the low latency, the low latency bandwidth is greater than 0, indicating that the low latency traffic is contained in the transmission container; or when the bandwidth marker is the non-low latency, the low latency bandwidth is equal to 0, indicating that the low latency traffic is not contained in the transmission container.

[0045] In some embodiments, the bandwidth marker is set according to the low latency service requirement of the OLT or the ONU.

[0046] In some embodiments, in the case that the OLT or the ONU needs to transmit the low-latency service, the bandwidth label is set to low-latency, and the low-latency bandwidth is set to a value greater than 0; or in the case that the OLT or the ONU does not need to transmit the low-latency service, the bandwidth label is set to the non-low-latency, and the low-latency bandwidth is set to 0.

[0047] In an exemplary embodiment, if χ AB = LL, then R L > 0, otherwise R L = 0.

[0048] In some embodiments, the traffic descriptor can only indicate whether there is low-latency traffic in the transmission container through the value of the low-latency bandwidth R L > 0 if there is low-latency traffic, and R L = 0 if there is no low-latency traffic. L

[0049] In the embodiments of the present disclosure, the OLT can obtain a traffic cache report or perform traffic monitoring based on the traffic descriptor with the low-latency characteristic, and thus can guarantee the bandwidth requirement of the low-latency service in dynamic bandwidth allocation, and improve the transmission quality of the low-latency service. In the non-low-latency service scenario, the existing technology can be compatible by setting the bandwidth label to the non-low-latency bandwidth label, and at the same time, the waste of network resources caused by setting a fixed low-latency bandwidth can be avoided.

[0050] The method embodiments provided in the embodiments of the present disclosure can be executed in the passive optical network described above.

[0051] In the present embodiment, a bandwidth allocation method is provided, which is applied to an optical line terminal.

[0052] FIG. 2 is a flowchart of dynamic bandwidth allocation of an optical line terminal according to an embodiment of the present disclosure. As shown in FIG. 2, the flow includes the following steps:

[0053] In step S202, traffic information of a transmission container of an optical network unit (ONU) is obtained.

[0054] In step S204, bandwidth is allocated to the transmission container according to the traffic information.

[0055] In the present embodiment, the traffic information is used to indicate whether the traffic in the transmission container is low-latency traffic and the bandwidth size of the low-latency traffic.

[0056] ​In the embodiment, the traffic information is acquired by the OLT through the traffic descriptor with low latency characteristics. The improved traffic descriptor includes a bandwidth label and / or a low latency bandwidth, and the corresponding traffic information also includes the bandwidth label of the traffic and the low latency bandwidth of the traffic. The bandwidth label is used to indicate whether the traffic in the transmission container is low latency traffic, and the low latency bandwidth is used to indicate the bandwidth size of the low latency traffic.

[0057] In the embodiment, through the steps S202 to S204, the low latency traffic can be identified through the traffic information, and the bandwidth allocation requirement of the low latency service is acquired, so as to guarantee the transmission requirement of the low latency service in bandwidth allocation, solve the technical problem that the bandwidth allocation method in the related art cannot effectively distinguish the low latency service scenario, and improve the user experience.

[0058] In the embodiment, the traffic descriptor can be implemented through the traffic descriptor with the low latency attribute in any one of the above-mentioned embodiments. The low latency attribute includes but is not limited to: low latency bandwidth, low latency (LL) in the bandwidth label, etc.

[0059] In the embodiment, the transmission container is a logical connection entity composed of one or more groups of traffic represented by the traffic descriptor in the ONU. The transmission container can be divided into a low latency transmission container and a non-low latency transmission container. The low latency transmission container is composed of one or more groups of low latency traffic, and the non-low latency transmission container is composed of one or more groups of non-low latency traffic.

[0060] In the embodiment, the traffic information in the step S202 can include attribute values corresponding to each attribute in the traffic descriptor. For example, if the traffic descriptor includes a low latency bandwidth, the traffic information includes a numerical value of the low latency bandwidth.

[0061] In some embodiments, the traffic descriptor includes a bandwidth label, and the traffic information also includes a value of the bandwidth label. For example, if the transmission container is a low latency transmission container, the bandwidth label is low latency (LL), and if the transmission container is a non-low latency transmission container, the bandwidth label is non-low latency (None, NA or BE). The OLT can confirm whether the user service has a low latency transmission requirement according to the bandwidth label.

[0062] In some embodiments, the method further includes: a step S206 of configuring, by the OLT, a transmission container of the ONU, wherein the transmission container includes: a low latency transmission container or a non-low latency transmission container, the low latency transmission container is used to transmit the low latency traffic, and the non-low latency transmission container is used to transmit non-low latency traffic.

[0063] In the embodiment, the step S206 is used to activate the transmission container, and can also be used to adjust the attribute of the activated transmission container. The step S206 can occur at any time before or after the step S202 / step S204 described above, can be sent when the ONU is online, or can be sent after running for a period of time, for example, when the service requirement changes, and the present disclosure does not make any limitation in this regard.

[0064] In some embodiments, the step S206 can include a step S2062 of sending a first control message to the optical network unit ONU.

[0065] In some embodiments, the first control message carries an allocation identifier and a first allocation identifier type, wherein the first allocation identifier type is determined by the OLT according to the service requirement, and the first control message is used to instruct the ONU to adjust the transmission container associated with the allocation identifier according to the first allocation identifier type.

[0066] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a low-latency transmission container, which is used to instruct the ONU to add a low-latency transmission container and associate the added low-latency transmission container with the allocation identifier, or is used to instruct the ONU to adjust a non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container.

[0067] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a non-low-latency transmission container, which is used to instruct the ONU to add a non-low-latency transmission container and associate the added non-low-latency transmission container with the allocation identifier, or is used to instruct the ONU to adjust a low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

[0068] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a release of a transmission container, which is used to instruct the ONU to release the transmission container associated with the allocation identifier.

[0069] In some embodiments, the first control message can be implemented by a Physical Layer Operations, Administration, and Maintenance (PLOAM) message in the downlink direction.

[0070] In an example embodiment, the message type of the PLOAM message can be Assign_Alloc-ID PLOAMd message, which is used to deliver the Alloc-ID assigned by the OLT to the ONU to the ONU. The message can be used to activate or release the T-CONT of the ONU, or to adjust the T-CONT attribute of the ONU.

[0071] In an example embodiment, the structure of the Assign_Alloc-ID PLOAMd message is shown in Table 1.

[0072] Table 1:

[0073] As shown in Table 1, the Assign_Alloc-ID PLOAMd message carries the assignment identification type (i.e. the first assignment identification type described above), which includes: low latency transmission container, non-low latency transmission container, and release assignment identification, which respectively represent the type of the transmission container corresponding to the Alloc-ID assigned by the OLT to the ONU.

[0074] In some embodiments, before step S2062, the method can further include step S2061 of assigning Alloc-ID, specifically, step S2061 can include at least one of the following:

[0075] allocating the assignment identification corresponding to the low latency transmission container to the ONU;

[0076] allocating the assignment identification corresponding to the non-low latency transmission container to the ONU;

[0077] allocating the assignment identification corresponding to the release transmission container to the ONU.

[0078] In the present embodiment, the first control message in step S2062 can carry the special assignment identification or the general assignment identification assigned by the OLT to the ONU in the above step S2061.

[0079] In some embodiments, before step S206, the method can further include step S205 of receiving, by the OLT, a second control message from the ONU.

[0080] In some embodiments, the second control message carries a second assignment identification type, which is determined by the ONU according to the service requirement, and the second control message is used to instruct the OLT to adjust the assignment identification corresponding to the transmission container according to the second assignment identification type.

[0081] In some embodiments, the second allocation identifier type comprises at least one of:

[0082] an allocation identifier type corresponding to a low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the low-latency transmission container;

[0083] an allocation identifier type corresponding to a non-low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the non-low-latency transmission container;

[0084] an allocation identifier type corresponding to a release transmission container, used to instruct the OLT to release an allocation identifier corresponding to the transmission container.

[0085] In some embodiments, the second control message can be an uplink PLOAM message, and an exemplary message type can be a newly added request Alloc-ID, denoted as "Request_Alloc-ID PLOAMu message", which is used to request a specified type of Alloc-ID from the OLT.

[0086] In an exemplary embodiment, the structure of the Request_Alloc-ID PLOAMu message is shown in Table 2 below.

[0087] Table 2:

[0088] As shown in Table 2, the Request_Alloc-ID PLOAMu message carries an allocation identifier type (i.e., the second allocation identifier type described above), which includes a low-latency transmission container, a non-low-latency transmission container, and a release allocation identifier, respectively indicating the type of transmission container to which the Alloc-ID requested by the ONU corresponds.

[0089] In some embodiments, the traffic information comprises a bandwidth label and / or a low-latency bandwidth.

[0090] In an exemplary embodiment, in the case where the traffic in the transmission container is low-latency traffic, the bandwidth label of the traffic is low-latency (LL), and / or the low-latency bandwidth of the traffic is greater than 0.

[0091] In an exemplary embodiment, in the case where the traffic in the transmission container is non-low-latency traffic, the bandwidth label of the traffic is non-low-latency (None, NA, or BE), and / or the low-latency bandwidth of the traffic is equal to 0.

[0092] In some embodiments, steps S202 and S204 can be implemented using any of the following dynamic bandwidth allocation methods: dynamic bandwidth allocation based on traffic monitoring, dynamic bandwidth allocation based on status reporting.

[0093] In an example embodiment, step S202 can include: obtaining the traffic information of at least one transmission container by performing traffic monitoring on the ONU; or obtaining the traffic information of at least one transmission container by receiving a status report from the ONU, wherein the type of information contained in the traffic information is determined by the traffic descriptor.

[0094] In an example embodiment, step S204 can include: in the case where the bandwidth is marked as low latency and the low latency bandwidth is greater than 0, allocating bandwidth to the low latency traffic according to the low latency bandwidth, wherein the low latency bandwidth is the bandwidth size of the low latency traffic, and the bandwidth allocation priority of the low latency traffic is higher than that of other traffic, so that the OLT preferentially allocates bandwidth to the low latency traffic to ensure that the data transmission needs of the low latency service are met, and then allocates bandwidth to other non-low latency traffic. For a specific bandwidth allocation process, refer to the dynamic bandwidth allocation scheme in the related art, such as Status Reporting DBA (SR-DBA) and Traffic Monitoring DBA (TM-DBA), which are not limited by the present disclosure.

[0095] In an example embodiment, step S204 can include: in the case where the low latency bandwidth is greater than 0, first allocating bandwidth to the low latency transmission container according to the low latency bandwidth, and then allocating bandwidth to the non-low latency transmission container. That is, the traffic information can also only use the low latency bandwidth as the type of information to mark the latency characteristics of the traffic and the bandwidth demand of the low latency traffic.

[0096] Through the embodiments of the present disclosure, the latency attribute of the traffic in the transmission container can be obtained based on the traffic descriptor with the low latency characteristic, and the bandwidth of the low latency service can be effectively guaranteed according to the low latency demand of the user service. The quality of the low latency service is guaranteed, thereby solving the technical problem that the bandwidth allocation method in the related art cannot effectively distinguish the low latency service scenario. The embodiments of the present disclosure can also consider the bandwidth allocation demand of the low latency service when allocating bandwidth, which can guarantee the low latency service demand and avoid the bandwidth waste caused by allocating fixed bandwidth to the low latency traffic, thereby achieving full utilization of network resources.

[0097] In another embodiment of the present disclosure, a bandwidth allocation method is also provided, which is applied to an optical network unit ONU.

[0098] FIG. 3 is a flowchart of dynamic bandwidth allocation of an optical network unit according to an embodiment of the present disclosure, as shown in FIG. 3, the flowchart includes the following steps:

[0099] Step S302: Obtain the traffic information of the transmission container of the ONU.

[0100] In step S304, the traffic information is sent to an optical line terminal (OLT) so that the OLT allocates bandwidth to the transmission container according to the traffic information.

[0101] In this embodiment, the traffic information is used to indicate whether the traffic in the transmission container is low-latency traffic and the bandwidth size of the low-latency traffic.

[0102] In this embodiment, the traffic information is obtained by the ONU through a traffic descriptor with a low-latency feature. The improved traffic descriptor includes a bandwidth mark and / or a low-latency bandwidth, and the corresponding traffic information also contains the bandwidth mark of the traffic and the low-latency bandwidth of the traffic. The bandwidth mark is used to indicate whether the traffic in the transmission container is low-latency traffic, and the low-latency bandwidth is used to indicate the bandwidth size of the low-latency traffic.

[0103] In this embodiment, through the above steps S302 to S304, the low-latency traffic can be identified through the traffic information, and the bandwidth allocation requirement of the low-latency service is obtained, so as to guarantee the transmission requirement of the low-latency service in bandwidth allocation, solve the technical problem that the bandwidth allocation method in the related art cannot effectively distinguish the low-latency service scenario, and improve the user experience.

[0104] In this embodiment, the traffic descriptor can be implemented by the traffic descriptor with a low-latency attribute in any one of the above embodiments. The low-latency attribute includes but is not limited to a low-latency bandwidth, a low-latency (LL) in a bandwidth mark, etc.

[0105] In this embodiment, the transmission container is a logical connection entity composed of one or more groups of traffic represented by the traffic descriptor in the ONU. The transmission container can be divided into a low-latency transmission container and a non-low-latency transmission container, wherein the low-latency transmission container is composed of one or more groups of low-latency traffic, and the non-low-latency transmission container is composed of one or more groups of non-low-latency traffic.

[0106] In this embodiment, the traffic information in step S302 can contain attribute values corresponding to each attribute in the traffic descriptor. For example, if the traffic descriptor contains a low-latency bandwidth, the traffic information contains the numerical value of the low-latency bandwidth.

[0107] In some embodiments, the traffic descriptor contains a bandwidth mark, and the traffic information also contains the value corresponding to the bandwidth mark. For example, if the transmission container is a low-latency transmission container, the bandwidth mark is low-latency (LL), and if the transmission container is a non-low-latency transmission container, the bandwidth mark is non-low-latency (None, NA, or BE). The OLT can determine whether the user service has a low-latency transmission requirement according to this bandwidth mark.

[0108] In some embodiments, the method further comprises: step S306, accepting configuration of the OLT to the transmission container, wherein the transmission container comprises: a low-latency transmission container for transmitting the low-latency traffic, or a non-low-latency transmission container for transmitting non-low-latency traffic.

[0109] In the present embodiment, step S306 is used to activate the transmission container, and can also be used to adjust the attributes of the activated transmission container. Step S306 can occur at any time before or after step S302 / step S304 described above, can be sent when the ONU is online, or can be sent after a period of operation, for example, when the service demand changes, and the present disclosure does not limit this.

[0110] In some embodiments, step S306 can comprise the following steps:

[0111] Step S3062, receiving a first control message carrying an allocation identifier and a first allocation identifier type from the OLT;

[0112] Step S3064, adjusting the transmission container associated with the allocation identifier according to the first allocation identifier type.

[0113] In the present embodiment, the first allocation identifier type is determined by the OLT according to the service demand, and the first control message is used to instruct the ONU to adjust the transmission container associated with the allocation identifier. Since the OLT is the superior control unit of the ONU, the ONU needs to obtain the authorization of the OLT when adjusting the transmission container, and in the present embodiment, the OLT sending the first control message to the ONU can be regarded as the process of the OLT authorizing the ONU to adjust the transmission container.

[0114] In some embodiments, the first control message can be implemented through a downlink physical layer operation, administration, and maintenance (PLOAM) message.

[0115] In an exemplary embodiment, the message type of the PLOAM message can be allocation Alloc-ID, denoted as “Assign_Alloc-ID PLOAMd message”, which is used to issue the Alloc-ID allocated by the OLT to the ONU.

[0116] In some embodiments, the first allocation identifier type comprises at least one of: an allocation identifier type corresponding to a low-latency transmission container, an allocation identifier type corresponding to a non-low-latency transmission container, and an allocation identifier type corresponding to a release transmission container.

[0117] In some embodiments, step S3064 can include: in the case that the first allocation identifier type is an allocation identifier type corresponding to a low-latency transmission container and the allocation identifier is not associated with a transmission container, adding a low-latency transmission container and associating the added low-latency transmission container with the allocation identifier; or in the case that the first allocation identifier type is an allocation identifier type corresponding to a low-latency transmission container and the allocation identifier is associated with a non-low-latency transmission container, adjusting the non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container.

[0118] In some embodiments, step S3064 can include: in the case that the first allocation identifier type is an allocation identifier type corresponding to a non-low-latency transmission container and the allocation identifier is not associated with a transmission container, adding a non-low-latency transmission container and associating the added non-low-latency transmission container with the allocation identifier; or in the case that the first allocation identifier type is an allocation identifier type corresponding to a non-low-latency transmission container and the allocation identifier is associated with a low-latency transmission container, adjusting the low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

[0119] In some embodiments, step S3064 can include: in the case that the first allocation identifier type is an allocation identifier type corresponding to a release transmission container, releasing the transmission container associated with the allocation identifier.

[0120] In some embodiments, before step S306, there can further be included a step S305 of sending a second control message carrying a second allocation identifier type to the OLT. This step is that the ONU initiatively applies to the OLT for adjusting the transmission container, and then the OLT authorizes the ONU to perform the adjustment operation, but the present disclosure is not limited thereto.

[0121] In the present embodiment, the second allocation identifier type is determined by the ONU according to service requirements, and the second control message is used to instruct the OLT to adjust the allocation identifier corresponding to the transmission container according to the second allocation identifier type.

[0122] In some embodiments, the second allocation identifier type includes at least one of:

[0123] an allocation identifier type corresponding to a low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the low-latency transmission container;

[0124] an allocation identifier type corresponding to a non-low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the non-low-latency transmission container;

[0125] The allocation identifier type corresponding to the release of the transmission container is used to indicate that the OLT releases the allocation identifier corresponding to the transmission container.

[0126] In some embodiments, the second control message can be a PLOAM message in the uplink direction, and an exemplary message type can be a newly added request Alloc-ID, denoted as "Request_Alloc-ID PLOAMu message". The message is used to request the OLT for an Alloc-ID of a specified type.

[0127] Further, through the second control message, the ONU can request the OLT for an Alloc-ID dedicated to a low-latency transmission container or an Alloc-ID not dedicated to a low-latency transmission container according to whether the ONU has a low-latency transmission requirement. The ONU can also request the OLT to release the corresponding Alloc-ID when the ONU has no transmission requirement.

[0128] In some embodiments, the traffic information includes a bandwidth label and / or a low-latency bandwidth.

[0129] In an exemplary embodiment, when the traffic in the transmission container is low-latency traffic, the bandwidth label is low-latency, and / or the value of the low-latency bandwidth is greater than 0.

[0130] In an exemplary embodiment, when the traffic in the transmission container is non-low-latency traffic, the bandwidth label is non-low-latency, and / or the value of the low-latency bandwidth is equal to 0.

[0131] According to the embodiments of the present disclosure, the latency attribute of the traffic in the transmission container can be obtained based on the traffic descriptor with the low-latency characteristic, and the low-latency service bandwidth can be effectively guaranteed according to the low-latency requirement of the user service. The low-latency service quality is guaranteed, and thus the technical problem that the bandwidth allocation method in the related art cannot effectively distinguish the low-latency service scenario is solved. The embodiments of the present disclosure can also consider the bandwidth allocation requirement of the low-latency service when allocating the bandwidth, which can guarantee the low-latency service requirement and avoid the bandwidth waste caused by allocating a fixed bandwidth for the low-latency traffic, and thus the network resources can be fully utilized.

[0132] In this embodiment, the OLT can proactively modify or configure the T-CONT attribute of the ONU according to service requirements. The ONU can also dynamically request an Alloc-ID from the OLT according to service requirements, thereby triggering the OLT to modify or configure the T-CONT attribute of the ONU. For example, service requirement scenarios include, but are not limited to: existing T-CONTs not meeting the current low-latency service traffic transmission requirements, necessitating the temporary addition of a low-latency Alloc-ID; or, the ONU itself being a low-latency service ONU, requiring continuous use of low-latency bandwidth allocation; or, after all low-latency services have been processed, the low-latency Alloc-ID needs to be released. The dynamic bandwidth allocation method for low-latency service traffic will be described in detail below with reference to specific embodiments.

[0133] Figure 4 is a schematic diagram (I) of a dynamic bandwidth allocation process for low-latency service traffic according to an embodiment of this disclosure. As shown in Figure 4, the process includes the following steps:

[0134] In step S401, the ONU goes online, is activated, and registers according to the standard procedure. The OLT assigns several Alloc-IDs to each ONU and establishes a logical cache for each Alloc-ID for traffic monitoring or obtaining cache reports. Furthermore, the Alloc-ID here can be an Alloc-ID dedicated to non-low latency services.

[0135] In step S402, the OLT uses a traffic descriptor with low latency to obtain a traffic cache report or perform traffic monitoring.

[0136] For example, the traffic descriptor is D= <R F ,R L ,R A ,R M ,χ AB ,P,ω>;where,R F For fixed bandwidth, R L For low latency bandwidth, R A To ensure bandwidth, R M For maximum bandwidth, χ AB Let χ be the bandwidth label, P be the best-effort bandwidth allocation priority, and ω be the best-effort bandwidth allocation weight; where χ is the bandwidth label. AB ={None,LL,NA,BE};

[0137] Alternatively, the flow descriptor is D= <R F ,R L ,R A ,R M ,χ AB ,P,ω,T JT ,T BDT ,T PST >; where RF For fixed bandwidth, R L For low latency bandwidth, R A To ensure bandwidth, R M For maximum bandwidth, χ AB Here, P represents the best-effort bandwidth allocation priority, ω represents the best-effort bandwidth allocation weight, and T represents the bandwidth allocation priority. JT For jitter tolerance, T BDT To allocate latency tolerance for bandwidth, T PST To protect the handover delay tolerance; where, the bandwidth is marked χ AB ={None,LL,NA,BE};

[0138] Step S403: For non-low-latency service transmissions, the uplink bandwidth allocation is the same as the existing standard specifications. Therefore, the bandwidth marker χ... AB The value of is one of {None, NA, BE}, and the low latency bandwidth R L =0;

[0139] Step S404: When the ONU needs to transmit low-latency services, the bandwidth flag in the traffic descriptor needs to be modified, setting χ... AB =LL, and low latency bandwidth R L >0; The modification method can be that the OLT actively modifies this attribute of T-CONT, or the ONU notifies the OLT to modify it through PLOAM message, OMCI message, etc., thereby increasing the support of T-CONT for low-latency service bandwidth allocation;

[0140] In step S405, during the DBA phase, the OLT performs global bandwidth allocation by obtaining cache reports or traffic monitoring data from each T-CONT. For bandwidth assurance of low-latency services during the DBA phase, fixed bandwidth assurance methods can be referenced, or bandwidth allocation can be assigned with high priority.

[0141] Step S406: When low-latency service transmission is completed and low-latency bandwidth guarantee needs to be turned off, the bandwidth flag in the traffic descriptor can be modified again, setting χ... AB = {None, NA, BE} (Non-low latency flag) One of these can be modified by the OLT actively modifying this attribute of T-CONT, or by the ONU notifying the OLT to modify it through PLOAM messages, OMCI messages, etc., thereby avoiding bandwidth allocation waste during non-low latency service transmission.

[0142] Figure 5 is a schematic diagram (II) of a dynamic bandwidth allocation process for low-latency service traffic according to an embodiment of this disclosure. As shown in Figure 5, the process includes the following steps:

[0143] In this embodiment, the dynamic bandwidth allocation method for low-latency service traffic includes the following steps:

[0144] Step S501, the ONU indicates its low-latency ONU attribute to the OLT in its online activation and registration process, the OLT registers it as a low-latency ONU, configures its T-CONT as a low-latency attribute, and assigns a corresponding Alloc-ID, the low-latency T-CONT attribute has a guaranteed bandwidth R L , i.e., the low-latency bandwidth in the traffic descriptor is greater than 0;

[0145] Step S502, the OLT performs global bandwidth allocation in the DBA stage by obtaining the buffer report or traffic monitoring of each T-CONT. In the DBA stage, the bandwidth guarantee for low-latency services can refer to the fixed bandwidth guarantee method or give high priority for bandwidth allocation.

[0146] Step S503, since the ONU is registered as a low-latency ONU, all services of this ONU are guaranteed and transmitted according to the low-latency service bandwidth requirements.

[0147] In this embodiment, the OLT in step S502 obtains the buffer report or traffic monitoring based on the traffic descriptor with low-latency characteristics. For example, the traffic descriptor is D = <R F , R L , R A , R M , χ AB , P, ω>; where R F is the fixed bandwidth, R L is the low-latency bandwidth, R A is the guaranteed bandwidth, R M is the maximum bandwidth, χ AB is the bandwidth mark, P is the allocation priority of the best-effort bandwidth, and ω is the allocation weight of the best-effort bandwidth; where the bandwidth mark χ AB = {None, LL, NA, BE}; or the traffic descriptor is D = <R F , R L , R A , R M , χ AB , P, ω, T JT , T BDT , T PST >; where R F is the fixed bandwidth, R L is the low-latency bandwidth, R A is the guaranteed bandwidth, R M is the maximum bandwidth, χ AB is the bandwidth mark, P is the allocation priority of the best-effort bandwidth, ω is the allocation weight of the best-effort bandwidth, T JT is the jitter tolerance, TBDT bandwidth allocation latency tolerance, T PST to protect the switching latency tolerance; wherein the bandwidth marker χ AB ={None, LL, NA, BE}.

[0148] In this embodiment, since the T-CONT of the ONU is of low latency attribute, the value of the bandwidth marker χ AB is the low latency bandwidth marker LL, and the low latency bandwidth R L >0.

[0149] Through the embodiments of the present disclosure, the low latency service scenario can be identified by the newly added low latency bandwidth marker in the traffic descriptor, and a dedicated low latency transmission container and a dedicated allocation marker are allocated for the low latency service, thereby guaranteeing the transmission quality of the low latency service.

[0150] Fig. 6 is a schematic diagram of a dynamic bandwidth allocation process of low latency service traffic according to an embodiment of the present disclosure (III), as shown in Fig. 6, the process includes the following steps:

[0151] In step S601, the ONU is online, activated and registered according to the standard process, the OLT allocates several Alloc-ID for each ONU, and establishes a logical buffer for each Alloc-ID for traffic monitoring or buffer report acquisition.

[0152] In step S602, the OLT acquires the traffic buffer report or performs traffic monitoring by using the traffic descriptor with low latency characteristics. For example, the traffic descriptor is D=<R F , R L , R A , R M , χ AB , P, ω>; wherein R F is the fixed bandwidth, R L is the low latency bandwidth, R A is the guaranteed bandwidth, R M is the maximum bandwidth, χ AB is the bandwidth marker, P is the allocation priority of the best effort bandwidth, and ω is the allocation weight of the best effort bandwidth; wherein the bandwidth marker χ AB ={None, LL, NA, BE}; or the traffic descriptor is D=<R F , R L , R A , R M , χ AB , P, ω, T JT , T BDT , T PST >; wherein R F is the fixed bandwidth, R L is the low latency bandwidth, RA R is the guaranteed bandwidth M χ is the maximum bandwidth AB P is the allocation priority of the best effort bandwidth, ω is the allocation weight of the best effort bandwidth, T JT T is the jitter tolerance BDT T is the bandwidth allocation delay tolerance PST T is the protection switching delay tolerance; wherein the bandwidth marker χ AB ={None, LL, NA, BE}.

[0153] In step S603, for non-low latency service transmission, the uplink bandwidth allocation is the same as the existing standard specification. Therefore, the bandwidth marker χ AB takes one of the values {None, NA, BE}, and the low latency bandwidth R L =0.

[0154] In step S604, when the ONU needs to add low latency service transmission, the ONU dynamically applies for low latency Alloc-ID to the OLT through OMCI or PLOAM message. For example, the PLOAM message can be used to achieve this, for example, a newly defined Request_Alloc-ID PLOAMu message is used, through which the ONU initiates a new Alloc-ID assignment application to the OLT; taking Table 2 above as an example, the value of the allocation identifier type should be the value of the category corresponding to the low latency transmission container, 0x0F.

[0155] In step S605, when the OLT receives the low latency dynamic Alloc-ID allocation application of the ONU, the OLT assigns a new Alloc-ID to the ONU, creates a new XGEM port ID related to the T-CONT logical entity of the Alloc-ID, and sends an allocation Alloc-ID message to the ONU. For example, step S605 can be achieved by sending an Assign_Alloc-ID PLOAMd message from the OLT to the ONU, taking Table 1 above as an example, the value of the allocation identifier type should be the value of the category corresponding to the low latency transmission container, 0x02, thereby activating the current low latency transmission container of the ONU;

[0156] In step S606, the OLT performs global bandwidth allocation by obtaining the buffer report or traffic monitoring of each active T-CONT in the DBA stage. In the DBA stage, the bandwidth guarantee for low latency service can refer to the fixed bandwidth guarantee method or be given a high priority for bandwidth allocation. Thereafter, the low latency service will transmit uplink service data according to the obtained low latency service guarantee bandwidth.

[0157] Step S607, when the low latency service transmission is completed and the low latency bandwidth guarantee needs to be closed, the ONU needs to initiate an Alloc-ID release application to the OLT. For example, the ONU can send a Request_Alloc-ID PLOAMu message to the OLT again. For example, referring to Table 2, the value of the allocation identification type should be the value of the category corresponding to the release of the allocation identification, 0xFF.

[0158] Step S608, after the OLT receives the application, the OLT destroys the Alloc-ID and the corresponding XGEM port ID, and sends a confirmation message to the ONU after the destruction. For example, the confirmation message can be an Assign_Alloc-ID PLOAMd message sent by the OLT to the ONU. For example, referring to Table 1, the value of the allocation identification type should be the value of the category corresponding to the release of the allocation identification, 0xFF.

[0159] Step S609, after the ONU receives the Assign_Alloc-ID PLOAMd message, the ONU performs corresponding cleaning of the T-CONT and the XGEM port ID on the ONU side; thereafter, the DBA updates the currently active Alloc-ID and performs new bandwidth allocation to the T-CONT, thereby avoiding waste of bandwidth allocation when non-low latency service transmission is performed.

[0160] According to the embodiments of the present disclosure, the low latency service scenario and the non-low latency service scenario can be distinguished, and the transmission container category can be dynamically adjusted according to the service demand, and the Alloc-ID that is no longer needed can be released in time, so that the transmission quality of the low latency service is guaranteed, and the network resources can be fully utilized to avoid waste of network resources.

[0161] In one embodiment of the present disclosure, a transmission configuration method is also provided, which is applied to an optical line terminal.

[0162] FIG. 7 is a flowchart of a transmission configuration method of an optical line terminal according to an embodiment of the present disclosure. As shown in FIG. 7, the flowchart includes the following steps:

[0163] Step S704, a first control message is sent to an optical network unit (ONU).

[0164] In the present embodiment, the first control message carries an allocation identification and a first allocation identification type. The first control message can instruct the ONU to adjust a transmission container associated with the allocation identification according to the first allocation identification type. Through the first control message, the OLT can configure the transmission container of the ONU.

[0165] In some embodiments, by assigning the allocation identifier and the first allocation identifier type, the first control message can instruct the ONU to perform at least one of the following transmission container configuration operations: add a transmission container, change a transmission container type, release a transmission container.

[0166] In the present embodiment, the transmission containers include low-latency transmission containers and non-low-latency transmission containers, wherein the low-latency transmission containers are used only for transmitting low-latency traffic, and the non-low-latency transmission containers are used only for transmitting non-low-latency traffic.

[0167] In an exemplary embodiment, adding a transmission container includes adding a low-latency transmission container or adding a non-low-latency transmission container; changing a transmission container type includes adjusting a low-latency transmission container to a non-low-latency transmission container or adjusting a non-low-latency transmission container to a low-latency transmission container; and releasing a transmission container includes releasing a low-latency transmission container or releasing a non-low-latency transmission container.

[0168] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a low-latency transmission container, which is used to instruct the ONU to add a low-latency transmission container and associate the added low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container.

[0169] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a non-low-latency transmission container, which is used to instruct the ONU to add a non-low-latency transmission container and associate the added non-low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

[0170] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to releasing a transmission container, which is used to instruct the ONU to release a transmission container associated with the allocation identifier.

[0171] In some embodiments, the first control message can be implemented by a PLOAM message in the downstream direction. For example, the message type of the PLOAM message can be an allocation Alloc-ID, denoted as "Assign_Alloc-ID PLOAMd message", and the structure of the message can refer to the content in Table 1.

[0172] In some embodiments, before step S704, the method further includes: step S703, assigning an allocation identifier (Alloc-ID) corresponding to the transmission container to be adjusted to the ONU.

[0173] Exemplarily, step S703 can include one of the following:

[0174] allocating an allocation identifier corresponding to the low-latency transmission container for the ONU;

[0175] allocating an allocation identifier corresponding to the non-low-latency transmission container for the ONU;

[0176] allocating an allocation identifier corresponding to the release transmission container for the ONU.

[0177] In some embodiments, before step S704, the method further includes: step S702, receiving a second control message sent by the ONU. Through the second control message, the ONU can actively request the OLT to configure the transmission container.

[0178] In the embodiment, the second control message carries a second allocation identifier type. The second control message can instruct the OLT to adjust the allocation identifier corresponding to the transmission container according to the second allocation identifier type.

[0179] In some embodiments, the second allocation identifier type includes at least one of the following:

[0180] an allocation identifier type corresponding to the low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the low-latency transmission container;

[0181] an allocation identifier type corresponding to the non-low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the non-low-latency transmission container;

[0182] an allocation identifier type corresponding to the release transmission container, used to instruct the OLT to release the allocation identifier corresponding to the transmission container.

[0183] In some embodiments, the second control message can be a PLOAM message in the uplink direction. Exemplarily, the message type of the message can be a newly added request Alloc-ID, denoted as “Request_Alloc-ID PLOAMu message”, which is used to request the OLT for an Alloc-ID of a specified type. The structure of the message can refer to the content in Table 2.

[0184] Through the embodiments of the present disclosure, the OLT can modify the latency attribute of the transmission container according to the service demand, and realize dynamic adjustment of the latency attribute of the transmission container. When a low-latency service is added, the OLT can add a low-latency transmission container to guarantee the bandwidth allocation and transmission performance of the low-latency service. After the low-latency service is completed, the OLT can also release the low-latency transmission container, or adjust the low-latency transmission container to a non-low-latency transmission container, to avoid bandwidth waste.

[0185] In another embodiment of the present disclosure, a transmission configuration method is also provided, which is applied to an optical network unit.

[0186] FIG. 8 is a flowchart of a transmission configuration method of an optical network unit in an embodiment of the present disclosure. As shown in FIG. 8, the flowchart includes the following steps:

[0187] In step S804, a first control message sent by an optical line terminal (OLT) is received.

[0188] In this embodiment, the first control message carries an allocation identifier and a first allocation identifier type. The first control message can instruct the ONU to adjust a transmission container associated with the allocation identifier according to the first allocation identifier type. Through the first control message, the OLT can configure the transmission container of the ONU.

[0189] In some embodiments, through the allocation identifier and the first allocation identifier type, the first control message can instruct the ONU to perform at least one of the following transmission container configuration operations: adding a transmission container, changing a transmission container type, and releasing a transmission container.

[0190] In this embodiment, the transmission container includes a low-latency transmission container and a non-low-latency transmission container, wherein the low-latency transmission container is used only for transmitting low-latency traffic, and the non-low-latency transmission container is used only for transmitting non-low-latency traffic.

[0191] In an exemplary embodiment, adding a transmission container includes adding a low-latency transmission container or adding a non-low-latency transmission container; changing a transmission container type includes adjusting a low-latency transmission container to a non-low-latency transmission container or adjusting a non-low-latency transmission container to a low-latency transmission container; and releasing a transmission container includes releasing a low-latency transmission container or releasing a non-low-latency transmission container.

[0192] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a low-latency transmission container, which is used to instruct the ONU to add a low-latency transmission container and associate the added low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container.

[0193] In some embodiments, the first allocation identifier type includes an allocation identifier type corresponding to a non-low-latency transmission container, which is used to instruct the ONU to add a non-low-latency transmission container and associate the added non-low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

[0194] In some embodiments, the first allocation identifier type comprises: an allocation identifier type corresponding to a release transmission container, used to instruct the ONU to release the transmission container associated with the allocation identifier.

[0195] In some embodiments, before step S804, the method further comprises: step S802, sending a second control message to the OLT. Through the second control message, the ONU can actively request the OLT to configure the transmission container.

[0196] In the embodiment, the second control message carries a second allocation identifier type. The second control message can instruct the OLT to adjust the allocation identifier corresponding to the transmission container according to the second allocation identifier type.

[0197] In some embodiments, the second allocation identifier type comprises at least one of:

[0198] an allocation identifier type corresponding to a low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the low-latency transmission container;

[0199] an allocation identifier type corresponding to a non-low-latency transmission container, used to instruct the OLT to add an allocation identifier corresponding to the non-low-latency transmission container;

[0200] an allocation identifier type corresponding to a release transmission container, used to instruct the OLT to release the allocation identifier corresponding to the transmission container.

[0201] Through the embodiments of the present disclosure, the ONU can also modify the latency attribute of the transmission container according to the service demand, to realize dynamic adjustment of the latency attribute of the transmission container. When a low-latency service is added, the ONU can request to add a low-latency transmission container to guarantee the bandwidth allocation and transmission performance of the low-latency service. After the low-latency service is completed, the ONU can also request to release the low-latency transmission container, or adjust the low-latency transmission container to a non-low-latency transmission container, to avoid bandwidth waste.

[0202] Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk), and includes a plurality of instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in various embodiments of the present disclosure.

[0203] Embodiments of the present disclosure further provide an optical line terminal comprising a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps in the above method embodiments.

[0204] Embodiments of the present disclosure further provide an optical network unit comprising a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps in the above method embodiments.

[0205] In an example embodiment, the processor can include, but is not limited to, a processing device such as a microprocessor (MCU) or a programmable logic device (FPGA), and a memory for storing data, and can further include a transmission device for communication function and an input / output device.

[0206] In an example embodiment, the memory can be configured to store a computer program, for example, a software program of an application software and a module, such as a computer program corresponding to the bandwidth allocation method in the embodiments of the present disclosure. The processor can execute various function applications and the bandwidth allocation method by running the computer program stored in the memory, i.e., implement the above method. The memory can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memories. In some examples, the memory can further include a memory remotely arranged with respect to the processor.

[0207] Embodiments of the present disclosure further provide a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is configured to be run by a processor to implement the steps in any of the above method embodiments.

[0208] In an example embodiment, the above computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic or optical disk, and various media capable of storing a computer program.

[0209] Embodiments of the present disclosure further provide an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the steps in any of the above method embodiments.

[0210] In an example embodiment, the above electronic device can further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0211] Embodiments of the present disclosure also provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method described in various embodiments of the present disclosure.

[0212] The specific examples in the present embodiments can refer to the examples described in the above embodiments and exemplary embodiments, which will not be repeated here.

[0213] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be realized by general computing devices, which can be concentrated on a single computing device or distributed on a network composed of multiple computing devices, which can be realized by program codes executable by the computing devices, so that they can be stored in storage devices and executed by the computing devices, and in some cases, the steps shown or described can be executed in different order, or they can be made into individual integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module. Thus, the present disclosure is not limited to any specific combination of hardware and software.

[0214] The above only describes the preferred embodiments of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art can make various modifications and changes to the present disclosure. Any modification, equivalent replacement, improvement, etc. within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A bandwidth allocation method applied to an optical line terminal (OLT), the method comprising: obtaining traffic information of a transmission container of an optical network unit (ONU), wherein the traffic information is used to indicate whether traffic in the transmission container is low-latency traffic and a bandwidth size of the low-latency traffic; and allocating bandwidth for the transmission container according to the traffic information. The method further comprises: configuring the transmission container of the ONU, wherein the transmission container comprises a low-latency transmission container or a non-low-latency transmission container. The configuring the transmission container of the ONU comprises: sending a first control message carrying an allocation identifier and a first allocation identifier type to the ONU, wherein the first control message is used to instruct the ONU to adjust a transmission container associated with the allocation identifier according to the first allocation identifier type.

2. The method of claim 1, wherein, The first allocation identifier type comprises: an allocation identifier type corresponding to a low-latency transmission container, which is used to instruct the ONU to add a low-latency transmission container and associate the added low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container. The first allocation identifier type comprises: an allocation identifier type corresponding to a non-low-latency transmission container, which is used to instruct the ONU to add a non-low-latency transmission container and associate the added non-low-latency transmission container with the allocation identifier, or which is used to instruct the ONU to adjust a low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

3. The method of claim 2, wherein, The first allocation identifier type comprises: an allocation identifier type corresponding to a release of a transmission container, which is used to instruct the ONU to release a transmission container associated with the allocation identifier. Before the sending the first control message carrying the allocation identifier and the first allocation identifier type to the ONU, the method further comprises at least one of the following: allocating an allocation identifier corresponding to the low-latency transmission container for the ONU; allocating an allocation identifier corresponding to the non-low-latency transmission container for the ONU; and allocating an allocation identifier corresponding to the release of the transmission container for the ONU.

4. The method of claim 3, wherein, Before the configuring the transmission container of the ONU, the method further comprises: receiving a second control message carrying a second allocation identifier type from the ONU, wherein the second control message is used to instruct the OLT to adjust an allocation identifier corresponding to the transmission container according to the second allocation identifier type. The second allocation identifier type comprises at least one of the following: an allocation identifier type corresponding to a low-latency transmission container, which is used to instruct the OLT to add an allocation identifier corresponding to the low-latency transmission container; an allocation identifier type corresponding to a non-low-latency transmission container, which is used to instruct the OLT to add an allocation identifier corresponding to the non-low-latency transmission container; and an allocation identifier type corresponding to a release of a transmission container, which is used to instruct the OLT to release an allocation identifier corresponding to the transmission container.

5. The method of claim 3, wherein, The traffic information comprises a bandwidth label and / or a low-latency bandwidth, wherein, ​ 6. The method of claim 3, wherein, ​ ​ 7. The method of claim 3, wherein, ​ ​ ​ ​ 8. The method of claim 2, wherein, ​ ​ 9. The method of claim 8, wherein, ​ ​ ​ ​ 10. The method of claim 1, wherein, ​ In a case where the traffic in the transmission container is the low-latency traffic, the bandwidth label is a low-latency bandwidth label, and / or the low-latency bandwidth is greater than 0; or In a case where the traffic in the transmission container is non-low-latency traffic, the bandwidth label is a non-low-latency bandwidth label, and / or the low-latency bandwidth is equal to 0.

11. The method of claim 10, wherein, Allocating bandwidth to the transmission container according to the traffic information comprises: In a case where the bandwidth label is the low-latency bandwidth label and the low-latency bandwidth is greater than 0, allocating bandwidth to the low-latency traffic according to the low-latency bandwidth, wherein the bandwidth allocation priority of the low-latency traffic is higher than that of non-low-latency traffic.

12. A bandwidth allocation method applied to an optical network unit (ONU), the method comprising: obtaining traffic information of a transmission container of the ONU, wherein the traffic information is used to indicate whether traffic in the transmission container is low-latency traffic and a bandwidth size of the low-latency traffic; sending the traffic information to an optical line terminal (OLT) to enable the OLT to allocate bandwidth to the transmission container according to the traffic information.

13. The method of claim 12, wherein, The method further comprises: accepting configuration of the transmission container by the OLT, wherein the transmission container comprises a low-latency transmission container or a non-low-latency transmission container.

14. The method of claim 13, wherein, The accepting the configuration of the transmission container by the OLT comprises: receiving a first control message carrying an allocation identifier and a first allocation identifier type from the OLT; adjusting a transmission container associated with the allocation identifier according to the first allocation identifier type.

15. The method of claim 14, wherein, The adjusting the transmission container associated with the allocation identifier according to the first allocation identifier type comprises: in a case where the first allocation identifier type is an allocation identifier type corresponding to a low-latency transmission container and the allocation identifier is not associated with a transmission container, adding a low-latency transmission container and associating the added low-latency transmission container with the allocation identifier; or in a case where the first allocation identifier type is an allocation identifier type corresponding to a low-latency transmission container and the allocation identifier is associated with a non-low-latency transmission container, adjusting the non-low-latency transmission container associated with the allocation identifier to the low-latency transmission container.

16. The method of claim 14, wherein, The adjusting the transmission container associated with the allocation identifier according to the first allocation identifier type comprises: in a case where the first allocation identifier type is an allocation identifier type corresponding to a non-low-latency transmission container and the allocation identifier is not associated with a transmission container, adding a non-low-latency transmission container and associating the added non-low-latency transmission container with the allocation identifier; or in a case where the first allocation identifier type is an allocation identifier type corresponding to a non-low-latency transmission container and the allocation identifier is associated with a low-latency transmission container, adjusting the low-latency transmission container associated with the allocation identifier to the non-low-latency transmission container.

17. The method of claim 14, wherein, The adjusting the transmission container associated with the allocation identifier according to the first allocation identifier type comprises: in a case where the first allocation identifier type is an allocation identifier type corresponding to a release of a transmission container, releasing the transmission container associated with the allocation identifier.

18. The method of claim 13, wherein, Before the receiving of the configuration of the transmission container by the OLT, the method further comprises: sending a second control message carrying a second allocation identifier type to the OLT, wherein the second control message is used to instruct the OLT to adjust the allocation identifier corresponding to the transmission container according to the second allocation identifier type.

19. The method of claim 18, wherein, The second allocation identifier type comprises at least one of: an allocation identifier type corresponding to a low latency transmission container, used to instruct the OLT to add the allocation identifier corresponding to the low latency transmission container; an allocation identifier type corresponding to a non-low latency transmission container, used to instruct the OLT to add the allocation identifier corresponding to the non-low latency transmission container; an allocation identifier type corresponding to a release transmission container, used to instruct the OLT to release the allocation identifier corresponding to the transmission container.

20. The method of claim 12, wherein, The traffic information comprises a bandwidth label and / or a low latency bandwidth, wherein, in the case that the traffic in the transmission container is the low latency traffic, the bandwidth label is a low latency bandwidth label, and / or the low latency bandwidth is greater than 0; or in the case that the traffic in the transmission container is the non-low latency traffic, the bandwidth label is a non-low latency bandwidth label, and / or the low latency bandwidth is equal to 0. 21.An optical line terminal comprising a memory, a processor and a computer program stored on the memory, wherein the processor executes the computer program to implement the steps of the method in any one of claims 1 to 11. 22.An optical network unit comprising a memory, a processor and a computer program stored on the memory, wherein the processor executes the computer program to implement the steps of the method in any one of claims 12 to 20.

23. A computer-readable storage medium having stored therein a computer program, wherein, The computer program is executed by the processor to implement the method in any one of claims 1 to 20. 24.A computer program product comprising a computer program, wherein the computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 20.

Images