Patent Description:
This section introduces aspects that may help facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is prior art or what is not prior art.

As demand grows for greater volumes of wireless data, the underlying infrastructure needs to be able to meet that demand.

<CIT> discloses an apparatus for performing integrated scheduling in a cloud-based virtualized radio access network (vRAN) architecture including one or more central units (CUs) configured to communicate with one or more remote units (RUs) over an x-haul transport network. The apparatus is configured to determine time-varying channel constraints based on a condition of an access link between the one or more RUs and one or more user equipment (UEs), the access link being in one of a wireless or wireline network, determine x-haul capacity constraints based on an amount of capacity available on an x-haul link between the one or more CUs and the one or more RUs, the x-haul link being in the x-haul transport network, and jointly schedule transmissions to the one or more UEs based on the time-varying channel constraints and the x-haul capacity constraints.

<CIT> discloses a method of controlling traffic flows in a radio communications network, the method comprising the steps of receiving at a remote node a plurality of traffic flows transmitted from a plurality of radio units, buffering the traffic flows in a common buffer of the remote node, and causing a control signal to be sent to a baseband unit when a fill level of the common buffer is predicted to go above a maximum fill level within a pre-set time interval, wherein the control signal is configured to cause an adjustment of a radio resource allocation of one of the plurality of radio units to cause a reduction in a data rate of the traffic flow transmitted from said radio unit.

<CIT> discloses an apparatus which is configured to control at least one fronthaul traffic stream via a fronthaul network to at least one radio unit, prepare a network resource reservation request for the at least one fronthaul traffic stream based on an expected traffic amount, send the network resource reservation request to a network control entity, receive a network resource reservation grant from the network control entity based on the network resource reservation request, and adapt scheduling decisions for the at least one fronthaul traffic stream based on the received grant.

Embodiments of the disclosure will become more fully apparent from the following detailed description, the appended claims, and the accompanying drawings in which like reference numerals identify similar or identical elements.

Detailed illustrative embodiments of the present disclosure are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing example embodiments of the present disclosure. Further, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments of the disclosure.

It further will be understood that the terms "comprises," "comprising," "includes," and/or "including," specify the presence of stated features, steps, or components, but do not preclude the presence or addition of one or more other features, steps, or components. It also should be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functions/acts involved.

<FIG> is a block diagram of a communication network <NUM> based on the <NUM> Radio Access Network (<NUM> RAN) architecture according to certain embodiments of the present disclosure. As shown in <FIG>, the <NUM> RAN network <NUM> comprises a <NUM> core <NUM> connected via back-haul link <NUM> to the central unit (CU) <NUM> of a <NUM> base station <NUM> (also known as a baseband unit or Next Generation Node B (gNB)), which also includes the distributed unit (DU) <NUM>, which may be co-located with and in communication with the CU <NUM> via link <NUM> (e.g., an F1 interface of the 3gpp standard). The DU <NUM> is connected via link <NUM> to the transport node <NUM> of a transport network (TN) <NUM>, which also includes one or more mobile front-haul (MFH) TN end points <NUM> and one or more non-MFH TN end points <NUM>, where each TN end point <NUM>/<NUM> is connected to the transport node <NUM> via a link <NUM>.

Each MFH TN end point <NUM> is connected via a corresponding link <NUM> to a <NUM> remote unit (RU, also known as a radio unit or remote radio head) <NUM> that communicates via wireless link(s) <NUM> with one or more user equipment (UE) devices <NUM>, such as mobile phones and the like. As used herein, the descriptions and solutions related to UE scheduling can also be applied similarly to dedicated radio bearer (DRB) scheduling. Similarly, each non-MFH TN end point <NUM> is connected via a corresponding link <NUM> to provide non-MFH services (e.g., enterprise or residential broadband services) to one or more particular end users <NUM>. As known to those skilled in the art, the CU <NUM>, the DU <NUM>, and the RUs <NUM> are part of a central radio access network (C-RAN) having the transport network <NUM>. As represented in <FIG>, the transport network <NUM> may also have one or more hybrid TN end points <NUM> that handle both traffic with one or more <NUM> RUs <NUM> as well as traffic for one or more non-MFH services. The TN scheduler <NUM> takes these two subsets of traffic into account when performing TN scheduling.

The DU <NUM> has a radio scheduler <NUM> that performs medium access control (MAC) scheduling for the <NUM> UE traffic over the air interface. In particular, the radio scheduler <NUM> schedules the <NUM> UE uplink (UL, i.e., upstream) traffic transmitted by the UEs <NUM> over the wireless links <NUM> towards the RUs <NUM> as well as the <NUM> UE downlink (DL, i.e., downstream) traffic transmitted by the RUs <NUM> over the wireless links <NUM> to the UEs <NUM>.

Similarly, the transport node <NUM> has a TN scheduler <NUM> that performs scheduling for the TN UL and DL traffic handled by the transport network <NUM>. In particular, the TN scheduler <NUM> schedules the MFH-related TN UL traffic transmitted from the MFH TN end points <NUM> to the transport node <NUM> as well as the non-MFH-related TN UL traffic transmitted from the non-MFH TN end points <NUM> to the transport node <NUM>. In addition, the TN scheduler <NUM> schedules the MFH-related TN DL traffic transmitted from the transport node <NUM> to the MFH TN end points <NUM> as well as the non-MFH-related TN DL traffic transmitted from the transport node to the non-MFH TN end points <NUM>.

As described further below, the transport network <NUM> may be a TDM-PON (time-division multiplexed, passive optical network), an Ethernet network, or other suitable type of transport network.

In certain implementations, depending on speed and distance, links <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are all bidirectional optical or electrical links that carry packetized data. In other implementations, one or more of those links may be wired or wireless links.

In the embodiment of <FIG>, the CU <NUM> and the DU <NUM> are co-located within the <NUM> base station <NUM>. In other embodiments, the CU <NUM> and DU <NUM> are not co-located. For example, the DU <NUM> can be remotely located from the CU <NUM>, in which case the CU <NUM> and the DU <NUM> are connected via a suitable (optical, wired, or wireless) mid-haul link.

<FIG> is a diagram representing the sequences of data processing steps for the <NUM> downlink and uplink signals in the <NUM> RAN network <NUM> of <FIG>. In general, the responsibility for performing these different steps may be shared between the DU <NUM> and the RUs <NUM>. <FIG> represent one possible split referred to as the <NUM>-2x lower-layer split with the DU <NUM> in the <NUM> base station <NUM> performing the upper steps above the beamforming step of <FIG>, and the <NUM> RUs <NUM> performing the lower steps of <FIG>. Those skilled in the art will understand that the <NUM>-2x split is just one possible distribution of the data processing steps between these different <NUM> nodes and that the location of the split will depend on the use case or specific deployment. In some implementations, the location of the split may vary over time as a function of the current operating conditions. In theory, the split may occur at different locations for the uplink and downlink processing. Splitting the data processing sequences balances the competing goals of (i) reducing transmission bandwidth through the transport network <NUM> on the one hand and (ii) sharing processing load between different <NUM> nodes to have computational resource-pooling gains on the other hand.

A split-processing architecture such as one shown in <FIG> leads to statistical traffic profiles for the digitized radio signals sent through the transport network <NUM> between the RUs <NUM> and the <NUM> base station <NUM> depending on the user-traffic statistics and channel conditions. As such, in certain implementations, the transport network <NUM> is implemented using a transport technology that employs statistical multiplexing over a shared medium, such as TDM-PON transport technology or Ethernet transport technology. Such split-processing architectures are promoted in the industry with specifications such as IEEE <NUM>, eCPRI group, and the ORAN consortium. Note that it is also possible to use (e.g., fiber or WDM (wavelength-division multiplex) based) point-to-point connections in other implementations.

In general, lower-layer processing splits, such as the <NUM>-2x split of <FIG>, and higher-layer processing splits will have different transport requirements in terms of data rate and latency as well as different benefits or advantages for centralized processing. Lower-layer splits are good candidates for implementation, leaving significantly lower processing requirements at the antenna sites, thereby reducing the costs of the RUs <NUM>. However, this split option requires a low-latency transport network <NUM> which becomes challenging for statistical multiplexing technologies (e.g., TDM-PON or Ethernet) since they can be congested in certain scenarios of oversubscription and hence incur additional delay and packet losses, which is difficult for conventional C-RAN networks to control.

These congestions may be due to unexpected, i.e., not provisioned, offered mobile traffic. This may happen for different reasons in a statistically multiplexed network. For instance, assume that the <NUM> RAN network <NUM> was provisioned based on a certain offered traffic profile, with some degree of "overbooking" (e.g., to have a guaranteed supported traffic equal to <NUM>% of the cumulative distribution function (CDF) of the traffic). If the non-MFH services subscribed to the network <NUM> are not fully using their shares of the allocated bandwidth, then some amount of unexpected MFH traffic can still be handled by the transport network <NUM>. However, if all of the non-MFH services are fully using their shares, then the shared transport network <NUM> will not be able to handle unexpected offered MFH traffic that exceeds the agreed Service Level Agreements (SLAs).

Conventional radio schedulers are agnostic of the C-RAN architectures and assume a perfect transport network (lossless with guaranteed latency and no jitter) between the RU and the DU/CU. In contrast to the Common Public Radio Interface (CPRI) standard, as C-RAN architectures evolve with split-processing base stations, the traffic between the RU and DU/CU becomes statistical depending on the cell load (due to low-layer/high-layer split options).

In this context, transport networks with statistical multiplexing technologies (e.g., TDM-PON, Ethernet) can be used to support cell densification cost effectively. However, shared statistical multiplexing transport networks can lead to uncontrolled delay or packet loss in certain high-congestion scenarios. If there is no feedback about transport network conditions to the radio scheduler, then the radio scheduler is not able to adapt scheduling decisions to guarantee flow quality of service (QoS) in terms of latency/reliability or bit rate. In this case, the overall radio system performance may suffer along with certain services that are sensitive to delays and packet loss (e.g., ultra-reliable low-latency communication (URLLC)).

The present disclosure describes mechanisms to provide feedback about transport network conditions to the radio scheduler and to adapt radio scheduler decisions based on the feedback from the transport network to preserve QoS, where needed and possible. In particular, with respect to the <NUM> RAN communication network <NUM> of <FIG>, some coordination between the radio scheduler <NUM> and the transport network scheduler <NUM> via the Cooperative Transport Interface (CTI) AV can improve system performance. Note that, in some implementations, the DU <NUM> may provide some or all of the feedback received from the TN scheduler <NUM> to the CU <NUM> via the interface <NUM>.

Using the CTI interface AV, the radio scheduler <NUM> requests a certain data rate on behalf of each RU <NUM>. This data rate is equivalent to the estimated or predicted MFH traffic demand from the RU <NUM> in the future depending on the RU load. The transport network <NUM> is shared between MFH services and non-MFH services. As such, MFH services are restricted to a fair share (depending on their SLAs). Without the knowledge of the current constraints of the transport network <NUM>, the decisions of the radio scheduler <NUM> may generate traffic beyond the front-haul capacity of the transport network <NUM>, which can lead to excessive delay and/or packet loss, ultimately causing performance issues for the <NUM> RAN communication network <NUM>.

With the diffusion of radio systems operating in unlicensed spectrum, a large amount of offered mobile traffic may need to be dealt with. Therefore, it is safe to assume that such traffic will be treated with the same priority as enterprise or residential broadband services. Moreover, in scenarios where the transport network <NUM> is shared between MFH and non-MFH services, these services' owners will negotiate TN costs and SLAs. As a result, the MFH services may be limited in priority after its SLAs are already satisfied. In particular, the TN scheduler <NUM> will likely provision the MFH services to have their TN share based on some traffic statistics profile.

The present disclosure proposes the following:.

The following discussion describes embodiments employing the TDM-PON transport technology, but similar techniques would be possible for other transport technologies using statistical multiplexing with dynamic bandwidth (or other resource) allocation, such as (without limitation) Ethernet transport technology. TDM-PON is a low-cost and resource-efficient transport technology based on statistical multiplexing of traffic over a single TDM wavelength channel. TDM-PON is currently used for residential or business broadband access. A goal of this disclosure is to use TDM-PON for the radio front-haul traffic to support cell densification using small cells.

<FIG> is a block diagram of an instance <NUM> of the <NUM> RAN communication network <NUM> of <FIG> in which the transport network <NUM> of <FIG> is implemented as a TDM-PON transport network <NUM> in which:.

As shown in <FIG>, the TDM-PON <NUM> also has an optical splitter/combiner <NUM> that splits the downlink optical signal from the OLT <NUM> and combines the uplink optical signals from the ONUs <NUM> and <NUM>. All other elements of the <NUM> RAN network <NUM> of <FIG> are analogous to the similarly labeled elements of the <NUM> RAN network <NUM> of <FIG>. As represented in <FIG>, the TDM-PON transport network <NUM> may also have one or more hybrid TN ONUs <NUM> that handle both traffic with one or more <NUM> RUs <NUM> as well as traffic for one or more non-MFH services. The TN scheduler <NUM> takes these two subsets of traffic into account when performing TN scheduling.

According to certain embodiments of the disclosure, the radio scheduler <NUM> of <FIG> bases scheduling decisions on different information, such as, for example, the following conventional information:.

In addition, the scheduling decisions of the radio scheduler <NUM> are also based on front-haul transport network status or load-limit information received from the TN scheduler <NUM>. Service prioritization on the radio scheduler <NUM> is based on the knowledge of the above information to fit within radio resource limitations or constraints.

The MAC scheduling decisions of the radio scheduler <NUM> are translated into required front-haul data rates based on resource utilization of each cell and communicated to the TN scheduler <NUM> using specific control messages via the CTI interface <NUM>. One such example is the use of Cooperative-Dynamic Bandwidth Allocation (Co-DBA) messaging from the radio scheduler <NUM> to the OLT TN scheduler <NUM> in the case of PON transport networks as taught by <NPL>), paper Tu3F. However, that Co-DBA messaging is a one-way communication from a conventional radio scheduler to a conventional TN scheduler, and there is no feedback from the transport network about the provisioning of this required data rate. As such, in the case of oversubscription, the transport network will delay and/or drop radio data, thereby adversely affecting end-to-end services.

The present disclosure proposes a mechanism to convey information about the characteristics and/or status of the front-haul transport network <NUM> to the radio scheduler <NUM> and for the radio scheduler <NUM> to use that information in performing radio MAC scheduling.

<FIG> illustrates the main components and working principles of certain embodiments of this disclosure. The OLT TN scheduler <NUM> operates/allocates TN resources in the data-rate (DR) (or bps (bits per second)) dimension. The data rate of the TDM-PON transport network <NUM> can be translated into a "load" in the context of the radio scheduler <NUM>, depending on the type of signals transported between the DU <NUM> and the RUs <NUM>, which in turn depends on the particular type of split processing implemented within the <NUM> RAN network <NUM>.

During a configuration phase, the radio scheduler <NUM> initially asks for an allocation of certain data rate from the OLT <NUM>, which can support an equivalent uplink/downlink load. During the subsequent operational phase, if the TN scheduler <NUM> detects the need to change the default DR allocation / current DR allocation of the front-haul services, for example, due to a potential / current congestion situation, then the TN scheduler <NUM> transmits, via the CTI interface <NUM> to the radio scheduler <NUM>, a new maximum data rate sustainable by the transport network <NUM> and its overall condition. This data rate is translated into a maximum supported load for the radio scheduler <NUM>. The radio scheduler <NUM> updates its parameters and implements a radio scheduler strategy that can consider load conditions and transport bandwidth availability for real-time scheduling decisions.

The information conveyed via the CTI interface <NUM> can be periodic or on-demand through properly designed signaling. This information can be enhanced by other feedback information, e.g., the transport network delay, jitter, packet drops for front-haul traffic flows. This information can be used by non-real-time processing at the DU <NUM> and/or the CU <NUM> to react on transport-layer status, e.g., making some Radio Admission Control decisions for some QoS flows.

Referring to <FIG>, time flows from top to bottom with the TN scheduler <NUM> transmitting, via the CTI interface <NUM> to the radio scheduler <NUM> during the configuration phase, data rate limits for use in scheduling the initial uplink and downlink loads to be transmitted through the transport network <NUM>, and the radio scheduler <NUM> transmitting, via the CTI interface <NUM> to the TN scheduler <NUM>, an acknowledgement (ACK) message indicating receipt of that information. During the operational phase, either periodically or as needed (depending on the particular implementation), the TN scheduler <NUM> transmits current data rate limits to the radio scheduler <NUM> for use in scheduling subsequent uplink and downlink loads. Note that, depending on the implementation, the TN scheduler <NUM> may transmit a single data rate limit for both uplink and downlink traffic or independent data rate limits for uplink traffic and for downlink traffic with those limits updated at the same time or at different times. Note further that, in some implementations. Note further that, in other implementations, instead of transmitting explicit data rate limits, the TN scheduler <NUM> transmits to the radio scheduler <NUM> some other form of bandwidth-related information indicating that there is insufficient bandwidth for transmitting the MFH traffic through the transport network <NUM>.

<FIG> is a flow diagram of processing performed by the radio scheduler <NUM> (steps <NUM>-<NUM>) and the TN scheduler <NUM> (steps <NUM>-<NUM>) of <FIG> according to certain embodiments of the disclosure. In certain implementations, the processing shown in <FIG> is executed independently and in parallel for both the uplink and the downlink traffic. In other implementations, the processing of <FIG> is implemented for both the uplink and downlink traffic in a single aggregated algorithm. The following description refers to an independent execution for the uplink traffic. An analogous execution would apply for the downlink traffic.

In particular, for uplink traffic, the radio scheduler <NUM> executes steps <NUM>-<NUM> to perform MAC scheduling for the mobile UL traffic from the UEs <NUM>, while the TN scheduler <NUM> executes steps <NUM>-<NUM> to perform scheduling for both the MFH UL traffic and the non-MFH UL traffic handled by the transport network <NUM>.

Referring first to the steps executed by the radio scheduler <NUM>, step <NUM> refers to the provision of conventional inputs to the MAC scheduling performed by a prior-art radio scheduler (listed previously), while step <NUM> refers to the translation of data-rate information received via the CTI interface <NUM> from the TN scheduler <NUM>. As described further below, the TN scheduler <NUM> transmits an UL data-rate limit for the radio scheduler <NUM> to use as a constraint in scheduling the MFH UL traffic. In step <NUM>, the radio scheduler <NUM> reads the inputs from steps <NUM> and <NUM>.

In step <NUM>, the radio scheduler <NUM> determines whether the data-rate limit received from the TN scheduler <NUM> warrants the performance of a non-conventional MAC scheduling algorithm. In some implementations, in step <NUM>, the radio scheduler <NUM> compares the received data-rate limit to a specified data-rate threshold (based on the configuration of the RU(s) resources scheduled by the radio scheduler <NUM>, the limitations given by the standardized modulation-coding schemes and/or the quantization of the complex symbols to be sent/received by the RUs). If the radio scheduler <NUM> determines that the received data-rate limit is greater than the specified data-rate threshold, then the radio scheduler <NUM> performs conventional (i.e., MFH-agnostic) MAC scheduling in step <NUM>. If, however, the radio scheduler <NUM> determines that the received data-rate limit is less than the specified data-rate threshold, then the radio scheduler <NUM> performs non-conventional (i.e., MFH-aware) MAC scheduling in step <NUM>. Different versions of the non-conventional MAC scheduling of step <NUM> are described further below. Note that, in alternative implementations, the radio scheduler <NUM> always performs the non-conventional MAC scheduling. In that case, steps <NUM> and <NUM> may be eliminated from <FIG>.

As part of either the conventional MAC scheduling of step <NUM> or the non-conventional MAC scheduling of step <NUM>, the radio scheduler <NUM> generates in step <NUM> an estimate of the transport network data rate required to support the upcoming MFH UL traffic through the transport network <NUM> and transmits that MFH UL DR estimate to the TN scheduler <NUM>, after which processing returns to step <NUM>.

Referring now to the steps executed by the TN scheduler <NUM>, step <NUM> refers to the provision of the estimated MFH UL data rate received from the radio scheduler <NUM>, while step <NUM> refers to the conventional provision of an estimate of the data rate required to support the upcoming non-MFH UL traffic through the transport network <NUM>. In step <NUM>, the TN scheduler <NUM> reads the inputs from steps <NUM> and FI.

In step <NUM>, the TN scheduler <NUM> performs conventional TN scheduling, such as, for example, priority plus fair scheduling, for the upcoming MFH and non-MFH UL traffic through the transport network <NUM>. During this TN scheduling, the TN scheduler <NUM> will determine the data rate allocated for the upcoming MFH UL traffic.

In step <NUM>, the TN scheduler <NUM> determines whether to transmit a data-rate limit to the radio scheduler <NUM>. In some implementations where the TN scheduler <NUM> periodically transmits DR limits, the TN scheduler <NUM> transmits the current MFH UL DR estimate as a DR UL limit to the radio scheduler <NUM> whenever the TN scheduler <NUM> determines that it is time to do so. In other implementations where the TN scheduler <NUM> transmits DR limits only when needed, the TN scheduler <NUM> compares the current MFH UL DR estimate to the previous MFH UL DR limit transmitted to the radio scheduler <NUM> to determine whether that MFH UL DR limit needs to be updated. In particular, the TN scheduler <NUM> will determine that the MFH UL DR limit will need to be updated when the current MFH UL DR estimate differs from the previous MFH UL DR limit by more than a specified magnitude threshold. If so, then, in step <NUM>, the TN scheduler <NUM> transmits the current MFH UL DR estimate to the radio scheduler <NUM> as the new MFH UL DR limit.

Whether or not step <NUM> is performed, according to conventional steps <NUM> and <NUM>, the TN scheduler <NUM> updates the DR allocation in step <NUM> for the current dynamic bandwidth allocation (DBA) cycle until the TN scheduler <NUM> determines in step <NUM> that the current DBA cycle has been completed, at which point processing returns to step <NUM>.

In the processing of <FIG>, the TN scheduler <NUM> monitors conditions that require limiting of the MFH data rate compared to what is requested by the radio scheduler <NUM>. This is done using a snapshot of the DR requests of MFH and non-MFH services and considering their respective SLAs. In a non-limited scenario, the TN scheduler <NUM> can allocate the requested MFH DR. However, depending on the service mix (e.g., enterprise or residential broadband, mobile back-haul, etc.) on the transport network <NUM> and their traffic statistics, the TN scheduler <NUM> may have to limit the MFH DR and provide a feedback to the radio scheduler <NUM>. The cooperative signaling function <NUM> at the DU <NUM> translates the DR limit into a load limit that is understood by the radio scheduler <NUM> depending on what signals are transported between the DU <NUM> and the RUs <NUM>. This load limit is then considered by the radio scheduler <NUM> in its MAC scheduling decisions. Depending on the MAC scheduling decisions of the radio scheduler <NUM>, the cooperative signaling function <NUM> can translate these decisions into an equivalent MFH DR request to be sent to the TN scheduler <NUM> via the CTI interface <NUM>.

For non-MFH applications, the TN scheduler <NUM> runs a DBA procedure periodically to calculate the TN DR allocations to different non-MFH services based on their usage of previous allocations and demands based on buffer reports. These non-MFH DR allocations stay the same for the duration of the DBA cycle and are updated every DBA cycle duration (typically a few milliseconds, e.g., <NUM>).

For MFH applications, the TN DR allocations for MFH services need to change ideally at the rate at which the radio scheduler <NUM> grants changes so that there is exact allocation for each MFH service and hence no buffering at the MFH ONUs <NUM>. In the case of the LTE (Long-Term Evolution) standard, this rate is <NUM> due to its scheduling granularity such that the radio scheduler <NUM> will transmit CTI DR request messages every <NUM> to the TN scheduler <NUM>. The TN scheduler <NUM> will allocate the exact DRs requested by the MFH services at the same time granularity (i.e., <NUM>) as long as the total DR is within the overall limit of the DR allocated to the MFH services in that DBA cycle.

In the transport network <NUM>, where MFH and non-MFH services are multiplexed on the same TDM-PON, the DBA for MFH services can operate at the frequency of the radio scheduler <NUM> (equivalently the CTI DR message frequency of every <NUM>, in the case of the LTE standard) and update the DR allocations for MFH services. However, the DBA for non-MFH services can still operate at the frequency of the DBA cycle duration (for example, <NUM>). Therefore, during the DBA computation of the non-MFH services, it is possible for the TN scheduler <NUM> to detect that there is a need to limit MFH services to a certain data rate so that the non-MFH services can fulfill their SLAs. This limitation will be applicable until the end of the current DBA cycle, at the end of which, the non-MFH DBA can assign a new non-MFH DR limit. Since this information is available at the start of the DBA cycle, the TN scheduler <NUM> can communicated the information to the radio scheduler <NUM> to limit the MAC DR requests and perform scheduling accordingly. The DBA for non-MFH services can also make longer-term predictions (few <NUM> of ms) or estimations on the DR requirements of the non-MFH services and update the DR limits for MFH services more infrequently.

This procedure does not cause any issues for downlink mobile operations, since the radio scheduler <NUM> makes its decisions just before the DL mobile resources allocation. However, for LTE specifications, uplink scheduling decisions are made <NUM> before the actual UL transmission is to occur. This can lead to mismatches in the current supported UL DR by the MFH and the scheduled UL transmissions. Embodiments of the present disclosure avoid degraded UL and DL transmissions when the OLT <NUM> is congested by designing proper procedures for the few UL slots when a change in the MFH UL DR limit has occurred.

<FIG> presents an example timeline of the processing by the radio scheduler <NUM> and the TN scheduler <NUM> of <FIG> for UL transmissions, where time flows from left to right. In this example, every <NUM>, the radio scheduler <NUM> transmits CTI messages with DR requests corresponding to MFH UL transmissions happening <NUM> in the future. Therefore, at the start of every non-MFH DBA cycle, there are already <NUM> MAC-scheduled MFH DR requests in the OLT DBA engine that still need to be fulfilled by the TN scheduler <NUM>. However, if the TN scheduler <NUM> allocates more DR to non-MFH services to meet their SLAs, then the TN scheduler <NUM> may have to change the limit on the MFH DR for future allocations as soon as the DBA cycle allocation is made. This affects partially the current DBA cycle (e.g., the remaining <NUM> of the DBA cycle).

In particular, at time t', a set of MFH UL data transmissions occur that were previously scheduled by the radio scheduler <NUM> using an existing MFH UL DR limit. At that time t', the radio scheduler <NUM> transmits (arrow <NUM>) the MFH UL DR estimate for those transmissions to the TN scheduler <NUM>. At time t (i.e., the start of a new non-MFH DBA cycle), the TN scheduler <NUM> schedules the MFH and non-MFH UL transmissions from the ONUs <NUM> and <NUM> and transmits (arrow <NUM>) updated bandwidth (BW) maps to the ONUs <NUM> and <NUM>. In addition, at time t, the TN scheduler <NUM> determines that the existing MFH UL DR limit at the radio scheduler <NUM> needs to be updated, and the TN scheduler <NUM> transmits (arrow <NUM>) an updated MFH UL DR limit to the radio scheduler <NUM>.

The radio scheduler <NUM> starts using that updated MFH UL DR limit right away, but since the radio scheduler <NUM> schedules MFH UL transmission <NUM> in advance, there are already four MFH UL transmissions scheduled using the previous MFH UL DR limit. As such, at times t'+<NUM>, t'+<NUM>, t'+<NUM>, and t'+<NUM>, four more MFH UL transmissions occur that were already scheduled by the radio scheduler <NUM> using the previous MFH UL DR limit. In addition, at times t+<NUM> through t+<NUM>, the TN scheduler <NUM> updates the BW maps for the MFH ONUs <NUM>, but not for the non-MFH ONUs <NUM> since the DBA scheduling cycle occurs every <NUM>.

Eventually (i.e., starting at time t'+<NUM>), MFH UL transmissions start to occur that were scheduled by the radio scheduler starting at time t'+<NUM> using the updated MFH UL DR limit. The current non-MFH DBA cycles ends at time t+<NUM>, and the next non-MFH DBA cycle begins at time t+<NUM>, where another updated MFH UL DR limit may be needed.

Depending on how the load conditions are defined, three different non-conventional approaches for signaling and scheduling can be considered. The approach could be selected/set during the initialization of the <NUM> RAN network <NUM> of <FIG>, when the CU <NUM>, the DU <NUM>, and the RUs <NUM> are linked and initialized.

Depending on the DU-RU processing split, different types of information are conveyed through the transport network <NUM> corresponding to different possible "load" limits involved in the MAC scheduling operations of the radio scheduler <NUM>. Three of the different possible types of information are quantized complex symbols, encoded bits, and information bits.

When the DU-RU processing split occurs just below the beamforming steps of <FIG> such that forward and inverse fast Fourier transforms (FFT and iFFT) are performed at the RUs <NUM>, and all of the upper steps in <FIG> are performed at the DU CG, quantized complex symbols are transmitted through the transport network <NUM>. In that case, it is sufficient for the radio scheduler <NUM> to have a limitation in the maximum number (Max_PRBs) of physical resource blocks (PRBs) (Max_PRBs) that the radio scheduler <NUM> can schedule for each transmission time interval (TTI). In some implementations, this number can be substituted by (i) the maximum number (Max_SymRate) of time-frequency symbols that can be transmitted in a certain time window (TimeWindow) or (ii) the maximum bandwidth (Max_AllocatedBandwidth) that the radio scheduler <NUM> can allocate. The TN data rate limit can be translated by the DU <NUM> into a maximum number of PRBs of maximum allocated bandwidth, taking into account subcarrier spacing and slot duration. Therefore, the limit on the signal can be just a data-rate itself.

When the DU-RU processing split occurs just above the modulation / demodulation steps of <FIG>, such that the RUs <NUM> perform those modulation / demodulation steps and all of the lower steps in <FIG>, and the DU <NUM> performs all of the upper steps in <FIG>, encoded bits are transmitted through the transport network <NUM> in the downlink direction and log-likelihood ratio (LLR) values for the encoded bits are transmitted through the TN network <NUM> in the uplink direction. In that case, the transport network <NUM> could impose a limit on the radio scheduler <NUM> for (i) the number (Max_GrossTP) of scheduled encoded "gross" throughput or (ii) the number (Max_EncodedBits) of encoded bits to be transmitted in a given time window (TimeWindow). These limits can be better derived internally by the DU <NUM>, which knows its internal parameters, once the transport network <NUM> shares its data-rate limit.

When all of the processing steps below the MAC steps of <FIG> are performed at the RUs <NUM>, information bits are transmitted through the transport network <NUM>. In that case, the transport network <NUM> could impose a limit on the radio scheduler <NUM> for (i) the net throughput (Max_NetTP) or (ii) the maximum number (Max_InformationBits) of information bits to be transmitted in a given time window (TimeWindow).

The radio scheduler <NUM> can control the offered "load" to the transport network <NUM> using the DR limits received from the TN scheduler <NUM>. In general, the radio scheduler <NUM> executes a MAC scheduling algorithm that operates as follows to allocate time-frequency resources to its active UEs <NUM>:.

Known scheduling approaches, like Round Robin, Weighted Round Robin, Proportional Fair, Alpha-Fair, Maximum TP, Hard and Soft Token-based mechanisms, and all other metric-based scheduling, fall under this generic description. This formulation enables unique ways to modify existing scheduling procedures to consider the TN load limit, depending on the particular type of TN load.

When the transport network <NUM> conveys quantized complex symbols for every time-frequency slot, in case of TN congestions, the network <NUM> can properly react if the radio scheduler <NUM> adopts a different behavior than the previous solutions. In particular, the above point c) should be substituted by the following sentence:
c) Some UE limitations can be considered, such as one or more of minimum or maximum number of REs per allocated UE, the UE buffer condition / packet size, maximum total number of PRBs per time slot, maximum number of time-frequency symbols in a pre-defined time window, or maximum allocated bandwidth.

More practically, the MAC scheduling procedure will allocate PRBs or, more generally, resources as was done before, until the scheduling reaches the limit on one or more of the number of PRBs per time slot, the maximum number of time-frequency symbols in a pre-defined time window, or the maximum allocated bandwidth. In some implementations, only one of these candidates is used to terminate scheduling.

When the transport network <NUM> conveys encoded information (i.e., encoded bits in DL, LLRs of encoded bits in UL), in case of TN congestions, the network <NUM> can properly react if the radio scheduler <NUM> adopts a different behavior than the previous solutions. In particular, the above point c) should be substituted by the following sentence:
c) Some UE limitations can be considered, such as one or more of minimum or maximum number of REs per allocated UE, the UE buffer condition / packet size, maximum encoded throughput, or maximum number of encoded bits to be transmitted / received in a certain configurable time window.

More practically, the modification is similar to the modification for quantized complex symbols, but with different "bit-rate throttling rules. " In some implementations, only one of these candidates is used to terminate scheduling.

When the transport network <NUM> conveys information bits, in case of TN congestions, the network <NUM> can properly react if the radio scheduler <NUM> adopts a different behavior than the previous solutions. In particular, the above point c) should be substituted by the following sentence:
c) Some UE limitations can be considered, such as one or more of minimum or maximum number of REs per allocated UE, the UE buffer condition / packet size, maximum net throughput, or maximum number of information bits to be transmitted / received in a certain configurable time window.

In some implementations, only one of these candidates is used to terminate scheduling. Here, too, the modification is similar to the modifications for quantized complex symbols and encoded information, but with different "throttling rules. " In this case, an optional procedure can be triggered to increase the number of allocated PRBs/REs while conveying the same amount of information bits that constitutes the bottleneck. This procedure could allow a better reliability to be achieved by the network, since spreading the available power of a transmission over more frequency resources is typically beneficial. This is not done in normal operations, because of the tradeoff between reliability and spectral efficiency. However, in this case, the tradeoff is removed due to the limited amount of information that must be transmitted in a time slot / window.

One can obtain this increased reliability effect by applying one of the following methods, after the MAC scheduling procedure has been run by the radio scheduler <NUM>, meaning after link adaptation (LA) has already been performed. Thus, the MCS index MCSi for every allocated UE i ∈ U has already been chosen, and there are still some free PRBs or REs FP that can be allocated, where FP is the number of unallocated free PRBs or REs. Note that the possible MCS indexes are sorted from the lowest rate (MCS = <NUM>) to the highest rate, thus with descending reliability. The current resources allocated to a UE i ∈ U are UE Ri. Note that, if only a subset of users is to have increased reliability, then the set U can include only the users matching a certain "eligibility" requirement, e.g., on the QoS flag or slice flag.

The following is an example of the MCS step with prioritization for the MAC scheduling performed by the radio scheduler <NUM>.

The following is an example of the MCS adaption with fair prioritization for the MAC scheduling performed by the radio scheduler <NUM>, where ρ(MCS) is the equivalent rate of MCS with index MCS, and TP is the total number of PRBs/REs that the radio scheduler <NUM> can allocate. <IMG>
<IMG>.

As the example described in <FIG> suggests, UL scheduling decisions are made some time (e.g., <NUM>) before the actual MFH transmission by the RUs <NUM>. Therefore, if there is a change in the load limit, then the radio scheduler <NUM> should know that for the remainder of the current <NUM>-ms DBA cycle window. The limit to be adopted by the radio scheduler <NUM> may be different from the communicated limit from the TN scheduler <NUM>. In particular, the radio scheduler <NUM> considers the number (A) of MFH UL transmissions already allocated during the current DBA cycle and adjusts the remaining transmissions to achieve the specified limit for the entire DBA cycle, which has a total of B (e.g., <NUM>) slots. The temporary load limit L' used by the radio scheduler <NUM> for the remaining (B-A) slots of the DBA cycle is given by the following equation: <MAT> where Lnew is the newly communicated load limit for each radio scheduler time slot, Si is the already scheduled load for the i-th time slot of the DBA cycle, and the square brackets with the plus sign means that the temporary load limit L' is set to zero if the value inside the brackets is negative. Note that, at the start of the next DBA cycle, assuming that the load limit has not be updated again, the load limit for each time slot will be Lnew. In alternative implementations, instead of the DBA cycle, the radio scheduler <NUM> scales the temporary load limit L' for the remaining time slots in a different specified time period, which may be explicitly communicated from the TN scheduler <NUM> to the radio scheduler <NUM>.

<FIG> is a block diagram of an instance <NUM> of the <NUM> RAN communication network <NUM> of <FIG> in which the transport network <NUM> of <FIG> is implemented as an Ethernet transport network <NUM> in which the TN scheduler <NUM> performs dynamic bandwidth allocation for a network of Ethernet switches <NUM>, <NUM>, and <NUM> interconnected by links <NUM>, where the MFH Ethernet switches <NUM> correspond to the MFH end points <NUM> of <FIG> and the non-MFH Ethernet switches <NUM> correspond to the non-MFH end points <NUM> of FIG. All other elements of the <NUM> RAN network <NUM> of <FIG> are analogous to the similarly labeled elements of the <NUM> RAN network <NUM> of <FIG>.

Although embodiments of this disclosure have been described in the context of <NUM> RAN networks, other embodiments of the disclosure may be in the context of other suitable types of existing radio access networks with simplified radio or split-processing architecture such as (without limitation) <NUM> LTE with split-processing eNB architecture, WiFi, WiMax, Bluetooth, etc. or future radio access networks.

Some embodiments of the disclosure are apparatus for a radio access network (RAN), the apparatus comprising a distributed unit (DU); a transport network (TN); and at least one remote unit (RU) connected to the DU via the transport network and configured to communicate via wireless communications traffic with one or more user equipment (UE) or dedicated radio bearer (DRB) devices. The DU comprises a radio scheduler configured to perform medium access control (MAC) scheduling for the wireless communications traffic. The transport network is configured to handle TN traffic comprising both (i) mobile front haul (MFH) traffic corresponding to the wireless communications traffic and (ii) non-MFH traffic corresponding to other traffic. The transport network comprises a TN scheduler configured to schedule the TN traffic. The TN scheduler is configured to transmit bandwidth-related information regarding the TN traffic to the radio scheduler. The radio scheduler is configured to perform subsequent MAC scheduling based on the bandwidth-related information received from the TN scheduler.

In some of the above embodiments, the radio scheduler is configured to determine an MFH data rate estimate for the MFH traffic between the DU and the at least one RU; the TN scheduler is configured to schedule the MFH traffic and non-MFH traffic based on (i) the MFH data rate estimate received from the radio scheduler and (ii) a non-MFH data rate estimate; the TN scheduler is configured to determine whether to transmit a current MFH data rate limit to the radio scheduler and, if so, transmit the current MFH data rate limit to the radio scheduler; and the radio scheduler is configured to perform the subsequent MAC scheduling based on the current MFH data rate limit received from the TN scheduler.

In some or all of the above embodiments, the radio scheduler is configured to perform MFH-aware MAC scheduling based on the current MFH data rate limit.

In some or all of the above embodiments, the radio scheduler is configured to perform MFH-agnostic MAC scheduling, if the radio scheduler determines that the current MFH data rate limit is more than a specified MFH data rate threshold; and the radio scheduler is configured to perform the MFH-aware MAC scheduling, if the radio scheduler determines that the current MFH data rate limit is less than the specified MFH data rate threshold.

In some or all of the above embodiments, the MFH-aware MAC scheduling depends on one or more of (a) whether the TN is configured to transport quantized complex symbols, in which case, the MFH-aware MAC scheduling is configured to take into account one or more of (i) a specified maximum total number of process resource blocks (PRBs) per time slot, (ii) a specified maximum number of time-frequency symbols in a pre-defined time window, (iii) and a specified maximum allocated bandwidth; (b) whether the TN is configured to transport encoded bits, in which case, the MFH-aware MAC scheduling is configured to take into account one or more of (i) a specified maximum encoded throughput and (ii) a specified maximum number of encoded bits to be transmitted / received in a certain configurable time window; and (c) whether the TN is configured to transport information bits, in which case, the MFH-aware MAC scheduling is configured to take into account one or more of (i) a specified maximum net throughput and (ii) a specified maximum number of information bits to be transmitted / received in a certain configurable time window.

In some or all of the above embodiments, the radio scheduler is configured to scale the current MFH data rate limit based on a number of remaining MFH time slots in a specified time period to achieve a desired average MFH data rate for the specified time period.

In some or all of the above embodiments, the transport network is configured to employ a statistical multiplexing technique to transport data.

In some or all of the above embodiments, the transport network is configured to employ either time-division multiplexed, passive optical network (TDM-PON) transport technology or Ethernet transport technology.

In some or all of the above embodiments, the radio scheduler is configured to perform MAC scheduling for UE and DRB uplink traffic that is independent of MAC scheduling for UE and DRB downlink traffic.

In some or all of the above embodiments, the bandwidth-related information comprises combined bandwidth-related information for both uplink TN traffic and downlink TN traffic.

In some or all of the above embodiments, the bandwidth-related information comprises independent bandwidth-related information for the uplink TN traffic and independent bandwidth-related information for the downlink TN traffic.

In some or all of the above embodiments, the DU is configured to transmit at least some of the bandwidth-related information to a central unit CU of the RAN.

Some embodiments of the disclosure are a distributed unit for a radio access network further comprising (i) a transport network and (ii) at least one remote unit connected to the DU via the transport network and configured to communicate via wireless communications traffic with one or more user equipment or dedicated radio bearer devices. The DU comprises a radio scheduler configured to perform medium access control MAC scheduling for the wireless communications traffic. The transport network is configured to handle TN traffic comprising both (i) MFH traffic corresponding to the wireless communications traffic and (ii) non-MFH traffic corresponding to other traffic. The transport network comprises a TN scheduler configured to schedule the TN traffic. The TN scheduler is configured to transmit bandwidth-related information regarding the TN traffic to the radio scheduler. The radio scheduler is configured to perform subsequent MAC scheduling based on the bandwidth-related information received from the TN scheduler.

Some embodiments of the disclosure are a TN scheduler for a transport network for a radio access network further comprising (i) a distributed unit and (ii) at least one remote unit connected to the DU via the transport network and configured to communicate via wireless communications traffic with one or more user equipment or dedicated radio bearer devices. The DU comprises a radio scheduler configured to perform medium access control scheduling for the wireless communications traffic. The transport network is configured to handle TN traffic comprising both (i) MFH traffic corresponding to the wireless communications traffic and (ii) non-MFH traffic corresponding to other traffic. The TN scheduler is configured to schedule the TN traffic. The TN scheduler is configured to transmit bandwidth-related information regarding the TN traffic to the radio scheduler. The radio scheduler is configured to perform subsequent MAC scheduling based on the bandwidth-related information received from the TN scheduler.

Some embodiments of the disclosure are a method for handling traffic in a radio access network comprising (i) a distributed unit, (ii) a transport network, and (iii) at least one remote unit connected to the DU via the transport network and configured to communicate via wireless communications traffic with one or more user equipment or dedicated radio bearer devices. The DU comprises a radio scheduler that performs medium access control MAC scheduling for the wireless communications traffic. The transport network handles TN traffic comprising both (i) MFH traffic corresponding to the wireless communications traffic and (ii) non-MFH traffic corresponding to other traffic. The transport network comprises a TN scheduler that schedules the TN traffic. The TN scheduler transmits bandwidth-related information regarding the TN traffic to the radio scheduler. The radio scheduler performs subsequent MAC scheduling based on the bandwidth-related information received from the TN scheduler.

Also for purposes of this description, the terms "couple," "coupling," "coupled," "connect," "connecting," or "connected" refer to any manner known in the art or later developed in which energy is allowed to be transferred between two or more elements, and the interposition of one or more additional elements is contemplated, although not required. Conversely, the terms "directly coupled," "directly connected," etc., imply the absence of such additional elements.

Signals and corresponding terminals, nodes, ports, or paths may be referred to by the same name and are interchangeable for purposes here.

As used herein in reference to an element and a standard, the term "compatible" means that the element communicates with other elements in a manner wholly or partially specified by the standard, and would be recognized by other elements as sufficiently capable of communicating with the other elements in the manner specified by the standard. The compatible element does not need to operate internally in a manner specified by the standard.

Embodiments of the disclosure can be manifest in the form of methods and apparatuses for practicing those methods. Embodiments of the disclosure can also be manifest in the form of program code embodied in tangible media, such as magnetic recording media, optical recording media, solid state memory, floppy diskettes, CD-ROMs, hard drives, or any other non-transitory machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the disclosure. Embodiments of the disclosure can also be manifest in the form of program code, for example, stored in a non-transitory machine-readable storage medium including being loaded into and/or executed by a machine, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the disclosure. When implemented on a general-purpose processor, the program code segments combine with the processor to provide a unique device that operates analogously to specific logic circuits.

Any suitable processor-usable/readable or computer-usable/readable storage medium may be utilized. The storage medium may be (without limitation) an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. A more-specific, non-exhaustive list of possible storage media include a magnetic tape, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM) or Flash memory, a portable compact disc read-only memory (CD-ROM), an optical storage device, and a magnetic storage device. Note that the storage medium could even be paper or another suitable medium upon which the program is printed, since the program can be electronically captured via, for instance, optical scanning of the printing, then compiled, interpreted, or otherwise processed in a suitable manner including but not limited to optical character recognition, if necessary, and then stored in a processor or computer memory. In the context of this disclosure, a suitable storage medium may be any medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

It should be appreciated by those of ordinary skill in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the disclosure.

It will be further understood that various changes in the details, materials, and arrangements of the parts which have been described and illustrated in order to explain embodiments of this disclosure may be made by those skilled in the art without departing from embodiments of the disclosure encompassed by the following claims.

In this specification including any claims, the term "each" may be used to refer to one or more specified characteristics of a plurality of previously recited elements or steps. When used with the open-ended term "comprising," the recitation of the term "each" does not exclude additional, unrecited elements or steps. Thus, it will be understood that an apparatus may have additional, unrecited elements and a method may have additional, unrecited steps, where the additional, unrecited elements or steps do not have the one or more specified characteristics.

It should be understood that the steps of the exemplary methods set forth herein are not necessarily required to be performed in the order described, and the order of the steps of such methods should be understood to be merely exemplary. Likewise, additional steps may be included in such methods, and certain steps may be omitted or combined, in methods consistent with various embodiments of the disclosure.

The embodiments covered by the claims in this application are limited to embodiments that (<NUM>) are enabled by this specification and (<NUM>) correspond to statutory subject matter, as defined by the appended claims. Non-enabled embodiments and embodiments that correspond to non-statutory subject matter are explicitly disclaimed even if they fall within the scope of the claims.

As used herein and in the claims, the term "provide" with respect to an apparatus or with respect to a system, device, or component encompasses designing or fabricating the apparatus, system, device, or component; causing the apparatus, system, device, or component to be designed or fabricated; and/or obtaining the apparatus, system, device, or component by purchase, lease, rental, or other contractual arrangement.

Claim 1:
Radio access network, RAN, (<NUM>, <NUM>) comprising:
a distributed unit, DU, (<NUM>);
a transport network, TN, (<NUM>, <NUM>); and
at least one remote unit, RU, (<NUM>, <NUM>) connected to the DU via the transport network and configured to communicate via wireless communications (<NUM>-<NUM>, <NUM>-<NUM>) traffic with one or more user equipment, UE, (<NUM>, <NUM>), wherein:
the DU comprises a radio scheduler (<NUM>, <NUM>) configured to perform medium access control, MAC, scheduling for the wireless communications traffic;
the transport network is configured to handle TN traffic comprising both (i) mobile front haul, MFH, traffic corresponding to the wireless communications traffic and (ii) non-MFH traffic corresponding to other traffic than the wireless communications traffic;
the transport network comprises a TN scheduler (<NUM>, <NUM>) configured to schedule the TN traffic;
the TN scheduler is configured to transmit (<NUM>) bandwidth-related information regarding the TN traffic to the radio scheduler; and
the radio scheduler is configured to perform subsequent MAC scheduling (<NUM>) based on the bandwidth-related information received (<NUM>) from the TN scheduler;
wherein:
the radio scheduler is configured to determine an MFH data rate estimate for the MFH traffic between the DU and the at least one RU;
the TN scheduler is configured to schedule the MFH traffic and non-MFH traffic based on (i) the MFH data rate estimate received from the radio scheduler and (ii) a non-MFH data rate estimate;
the TN scheduler is configured to determine whether to transmit a current MFH data rate limit to the radio scheduler and, if so, transmit the current MFH data rate limit to the radio scheduler; and
the radio scheduler is configured to perform the subsequent MAC scheduling based on the current MFH data rate limit received from the TN scheduler.